# lltstat -nvv | more - verbose output, check for OPEN status. Runing some status commands: # lltstat -n - on sys1 The Cluster Web Console and Java Web Console are options while running the installvcs script.Ĭheck files /etc/llthosts, /etc/llttab, /etc/gabtab, the /etc/VRTS/conf/config/main.cf file Make sure all previous packages have been removed./installvcs - follow prompts. Make sure you have root rsh setup on each node using /.rhosts Device names of the NICs in the private network.The host names of the systems in the cluster.
VCS DISPLAY MASTER NODE INSTALL
When installing VCS the system you install from does not need toĮach system must be on the public network with a unique host name. If licensing isĭone after use licensevcs.
VCS DISPLAY MASTER NODE LICENSE
A site license can be installed on each node in the cluster. Install the VCS via installvcs, installvcs does not install the GUIs.
The nodes in the cluster must have a shared storage device via Fibre Channel I/O.Įach node has the solaris environment with a Fibre HBA attached.
Resources and Service Groups for the CFS.ĬVM: CVMCluster, CVMDiskGroup, CVMMultiNIC, and CVMVolume MANPATH=/opt/VRTS/man:$MANPATH export MANPATH usr/lib/vxvm/bin:/usr/sbin:/etc/fs/vxfs:/etc/vx/bin PATH=$PATH:/opt/VRTSvxfs/sbin:/opt/VRTSvxfs/lib/vcs:/opt/VRTSvmsa/bin:/usr/lib/fs/vxfs: Installvcs - Adds and configures the nodes.Ĭfsdeinstall - removes CFS based packages. VRTScscm - Veritas cluster server cluster manager VRTScavf - Veritas Cluster server Enterprise agents for Volume manager VRTSvmman - Veritas volume manager man pages VRTSvmdev - Veritas volume manager header and library files VRTSvxfs - Veritas Fiel system with CFS software. The following packages are Cluster File system and Volume Manager VRTSvcsw - Veritas Cluster Manager Web Console VRTSgab - Veritas Group Membership and Atomic Broadcast
The following packages are Cluster Server: The CFS is part of the functionality of the VxFS. Installed to license CFS via the vxlicense command. You need to have both VCS license and one license for all other packages.
To configure the cluster UUID manually, the following command needs to be executed to copy the cluster UUID from the existing VCS cluster system node/(s) to the required nodes which encounter the issue of UUID not matching.The Veritas Cluster File System is a licensed product. The error messages are caused by the VCS UUID not matching between different servers in the cluster: Manually restart VCS after configuring correct CID in the cluster. Manually Restart VCS after configuring Cluster UUID.ĥ 17:46:51 VCS ERROR V-16-1-10651 Cluster UUID received from snapshot is not matching with one existing on HOSTNAME. An error will be encountered in the VCS engine_A.log (/opt/VRTSvcs/log/engine_A.log) upon issuing the VCS 'hastart' command to start the VCS cluster services.ĥ 17:46:51 VCS ERROR V-16-1-10614 Cluster UUID is not configured or it is empty, on system - VCS Stopping. If a cluster is being manually configured or a new node is being joined into an existing cluster, then it may be required to configure the VCS cluster UUID manually, else that particular system node will not be able to join into the cluster by starting the VCS cluster services. This feature is introduced to prevent system nodes from different clusters to mistakenly join into incorrect VCS clusters that they do not belong to. VCS cluster, then VCS services will not be able to start on that system node. If a Cluster UUID is not present or does not match with that of other system nodes in the Veritas Cluster Server (VCS) 5.1 onwards has introduced a new feature of cluster UUID (Universally Unique ID).
0 kommentar(er)
