Veritas Cluster Installation and Management
Configuring Veritas Volume Manager and Veritas Cluster ▀
Cisco ASR 5000 Series External Storage Server Installation and Administration Guide ▄
#/etc/init.d/gab start
Step 11 Repeat Step 7 through Step 10 on second server.
Step 12 Verify that both servers‟ cluster communication modules see each other by typing the following command:
gabconfig a
If you see a line with membership “01”, then both nodes are talking. If you see the message as membership “;1” or “0;”
then the node that has the “;” (semi-colon) is misconfigured. Verify your configurations in the /etc/llttab, /etc/llthosts,
and /etc/gabtab files.
Step 13 Type hastart and then hastatus. When the last line reads “<system name> RUNNING”, VCS engine has started.
If you get “VCS ERROR V-16-1-10600 Cannot connect to VCS engine” repeatedly, the VCS engine has failed to start.
Refer to the /var/VRTSvcs/log/engine_A.log for possible problems.
Step 14 Execute the first VCS configuration script, /mnt/vcs_basic.sh, from the configuration DVD. Enter the data for
cluster node names, cluster name, virtual IP address and virtual netmask. A lot of warning messages will be displayed,
but there should be no errors.
Step 15 Stop the cluster by typing the following command:
root@less4 # hastop all
Then, copy the new types.cf from the /mnt directory to /etc/VRTSvcs/conf/config.
Step 16 Regenerate and populate the config on both the nodes by executing the following commands:
root@less4 # hacf verify /etc/VRTSvcs/conf/config/
root@less4 # hacf generate /etc/VRTSvcs/conf/config/
Then execute hastart on both the nodes.
Step 17 Validate that the cluster has probed all resources by waiting until the hastatus -sum command output looks similar
to the following:
root@less4 # hastatus -sum
-- SYSTEM STATE
-- System State Frozen
A less3 RUNNING 0
A less4 RUNNING 0
-- GROUP STATE
-- Group System Probed AutoDisabled State
B LAPP less3 Y N OFFLINE
B LAPP less4 Y N OFFLINE
To Next Page
Loading...
Need help?
General
