Routine Management of Symantec VCs (VERITAS Cluster Server)

1. view the VCs version and license information

PSDB01:~ # vxlicrep Symantec License Manager vxlicrep utility version 3.02.51.010Copyright (C) 1996-2010 Symantec Corporation. All rights reserved.Creating a report on all VERITAS products installed on this system -----------------***********************-----------------   License Key                         = XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-X   Product Name                        = VERITAS Cluster Server   Serial Number                       = XXXX   License Type                        = PERMANENT   OEM ID                              = 2006   Site License                        = YES   Editions Product                    = YES Features :=    Platform                            = Unused                               Version                             = 5.1                                   Tier                                = Unused                                Reserved                            = 0    Mode                                = VCS                                   CPU_TIER                            = 2   VXKEYLESS                           = Enabled

2. VCs cluster ID and heartbeat Nic settings

PSDB01:~ # lltstat -l LLT link information:link 0  eth10 on ether hipri        mtu 1500, sap 0xcafe, broadcast FF:FF:FF:FF:FF:FF, addrlen 6        txpkts 67688788  txbytes 1843243673        rxpkts 76679165  rxbytes 1360585331        latehb 0  badcksum 0  errors 0link 1  eth9 on ether hipri        mtu 1500, sap 0xcafe, broadcast FF:FF:FF:FF:FF:FF, addrlen 6        txpkts 67689522  txbytes 1843879628        rxpkts 276962155  rxbytes 1467872503        latehb 0  badcksum 0  errors 0link 2  eth8 on ether lowpri        mtu 1500, sap 0xcafe, broadcast FF:FF:FF:FF:FF:FF, addrlen 6        txpkts 21897078  txbytes 1072847300        rxpkts 222319811  rxbytes 1191109452        latehb 0  badcksum 0  errors 0PSDB01:~ # cat /etc/llttab set-node PSDB01set-cluster 117link eth10 eth-80:fb:06:35:b8:9f - ether - -link eth9 eth-80:fb:06:35:b8:a1 - ether - -link-lowpri eth8 eth-80:fb:06:35:b8:a0 - ether - -PSDB01:~ # lltstat -nLLT node information:    Node                 State    Links   * 0 PSDB01            OPEN        3     1 PSDB02            OPEN        3

Note: Three NICs are used for heartbeat. If the number of links is insufficient during lltstat viewing, it may be due to a network failure. Most of the problems I encountered were due to the network card being down and IFUP.

3. view the status of the VCs dual-host

RMCDB02:~ # hastatus -sum-- SYSTEM STATE-- System               State                Frozen              A  RMCDB01              RUNNING              0                    A  RMCDB02              RUNNING              0                    -- GROUP STATE-- Group           System               Probed     AutoDisabled    State          B  RCS_DB_SG       RMCDB01              Y          N               ONLINE         B  RCS_DB_SG       RMCDB02              Y          N               OFFLINE      

4. Start and Stop the VCs Cluster

(1) when starting a cluster with two nodes, run hastart as the root user on each node and use hastatus to view the status information of resources during the startup process.

(2) When stopping, you only need to use the root user to execute: hastop-all on one of the nodes, and also use hastatus to view the status, this requires that the VCs has been stopped on each node.

Note: You must check the VCs logs whether it is started or stopped, especially during startup, to help troubleshoot problems during startup. Default VCs log files:

/Var/vrtsvcs/log/engine_a.log

5. Freeze and unfreeze resource groups

This is often used by me. In general, it means that VCs does not manage clusters for the time being. Even if the status of the Resource Group on which nodes are monitored is incorrect, no switchover or re-pulling operations will occur. It is often used during maintenance, such as patching Oracle databases and restarting listening.

<Strong> freeze Dual Servers: </strong> rmcdb02 :~ # Hagrp-freeze rcs_db_sgrmcb02 :~ # Hastatus-sum -- system state frozen a rmcdb01 running 0 A rmcdb02 running 0 -- group state -- group system probed autodisabled State B rcs_db_sg rmcdb01 y n online B rcs_db_sg rmcdb02 y n offline -- groups frozen -- group C rcs_db_sg -- resources disabled -- group type resource H rcs_db_sg application ora_raw H rcs_db_sg application ora_vg H rcs_db_sg IP ora_ip H rcs_db_sg Nic ora_ni C h rcs_db_sg netlsnr ora_listener H rcs_db_sg Oracle ora_ora11g <strong> unfreeze dual HOST: </strong> rmcdb02 :~ # Hagrp-Unfreeze rcs_db_sg

6. VCs dual-host switch

This is also frequently used by me. It is mainly to monitor that the host in the cluster may fail, so the resource group is manually switched to another node, or hardware maintenance and system restart are performed.

Ndmcb04 :~ # Hastatus-sum -- system state frozen a ndmcb03 running 0 A ndmcb04 running 0 -- group state -- group system probed autodisabled State B rcs_ndmcb_rg ndmcb03 y n online B restart ndmcb04 y n offline ndmcb04: ~ # Hagrp-switch rcs_ndmcb_rg-to ndmcb04 # Switch resources from ndmcb03 to the ndmcb04 host

7. troubleshoot the dual-machine startup of VCs
After the hastart command is run to start the dual-host machine, run the hastatus-sum command to view the status of the dual-host machine. The following information is displayed:
Attempting to connect... connected
Group resource system message
---------------------------------------------------------------------------
Test-smc3 stale admin wait: All systems stale
Stale_admin_wait: the system has a stale configuration and no other system is in a running state.
Admin_wait: the system cannot build or obtain a valid configuration.
The dual-host status is either stale_admin_wait or admin_wait. The dual-host software cannot be started normally.
Procedure
Step 1 verify that the configuration file main. cf is correct.
Modify the main. cf configuration file according to your actual business application.
Step 2. Run the command hacf-verify config_dir to verify the correctness of the Configuration File Syntax. For example:
# Hacf-verify/etc/vrtsvcs/CONF/config
If an error message exists, modify the "Main. Cf" file as prompted.
Step 3 run the hasys-force node name command to start VCs.