1: Ans

:

How do check the status of VERITAS Cluster Server aka VCS? hastatus –sum

2: Which is the main config file for VCS and where it is located? Ans: main.cf is the main configuration file for VCS and it is located in /etc/VRTSvcs/conf/config. 3: Ans: 9: Ans: 10: Ans: 11: Ans: 12: Ans: 13: Ans: 14: Ans: 15: Ans: Which command you will use to check the syntax of the main.cf? hacf -verify /etc/VRTSvcs/conf/config How to switchover the service group in VCS? # hagrp –switch -to How to online the service groups in VCS? # hagrp –online -sys How to set the VCS configuration Read-Only? # haconf –dump -makero How to set the VCS configuration Read-Write? # haconf -makerw How to display the list of all snapshots? # hasnap –display –list How to add a user with cluster administrator/Operator access? # hauser –add <user> -priv Administrator/Operator How to add a user with group administrator/Operator access? # hauser –add <user> -priv Administrator/Operator –group <service group>

Querying Service Groups, & Resources
16: Ans: 17: Ans: 18: Ans: 19: Ans: 20: Ans: 21: How to display the status of a service group on a system? # hagrp –state <service group> -sys <system> How to display the resources for a specific service group? # hagrp –resources <service group> How to display the service group dependencies? # hagrp –dep <service group> How to display information about a service group on a system? # hagrp –display <service group> -sys <system name> How to display resource dependencies? # hares –dep <resource name> How to display information about a resource?

AutoStartList. parallel etc? (A) How to populate the SystemList attribute of service group groupX with SystemA and B. # hagrp –modfy groupX SystemList –add SystemA 1 SystemB 2 (B) How to populate the AutoStartList attribute of service group groupX with SystemA and B. systems.Ans: 22: Ans: 23: Ans: 24: Ans: 25: Ans: 26: Ans: 27: Ans: 28: Ans: 29: Ans: 30: Ans: # hares –display <resource name> How to display resources of a service group? # hares –display –group <service group> How to display resources of a resource type? # hares –display –type <resource type> How to display attributes of a system? # hares –display –sys <system name> How to display all resources type? # hatype –list How to list the systems in the cluster? # hasys –list How to display information about a particular system? # hasys –list <system name> How to display information about the cluster? # haclus –display How to display the status of all service groups including resources in cluster? # hastatus How to display the status of cluster faults. # hagrp –modify groupX AutoStartList –add SystemA SystemB (C) How to define the service group as a parallel? . including faulted service groups. links and agents? # hastatus –summary Administering Service Group 31: Ans: 32: Ans: 33: Ans: How to add a service group in a cluster? # hagrp –add <service group> How to delete a service group from a cluster? # hagrp –delete <service group> How to modify a service group attribute such as SystemList.

non-persistent resources in a service group? # hagrp –clear <service group> -sys <system name> How to clear resources in ADMIN_WAIT state in a service group? # hagrp –clearadminwait <service group> -sys <system name> How to flush a service group? # hagrp –flush <service group> -sys <system name> How to link a service group with another? # hagrp –link <parent service group> <child service group> <gd_category> <gd_location> <gd_type> gd_category = gd_location = gd_type = Category of group dependency (online/offline) The scope of dependency (local/global/remote) type of group dependency (soft/firm/hard) 48: Ans: How to unlink a service group with another? # hagrp –unlink <parent service group> <child service group> .34: Ans: 35: Ans: 36: Ans: 37: Ans: 38: Ans: 39: Ans: 40: Ans: 41: Ans: 42: Ans: 43: Ans: 44: Ans: 45: Ans: 46: Ans: 47: Ans: # hagrp –modify <service group> Parallel 1 How to bring a service group online? # hagrp –online <service group> -sys <system name> How to take a service group offline? # hagrp –offline <service group> -sys <system name> How to take a service group offline if all resources are probed? # hagrp –offline <service group> -ifprobed –sys <system name> How to switch a service group from one system to another system? # hagrp –switch <service group> -to <system name> How to freeze a service group? # hagrp –freeze <service group> -persistent How to unfreeze a frozen service group? # hagrp –unfreeze <service group> -persistent How to disable a service group? # hagrp –disable <service group> -sys <system name> How to enable a service group? # hagrp –enable < service group> -sys <system name> How to enable all resources in a service group? # hagrp –enableresources <service group> How to disable all resources in a service group? # hagrp –disableresources <service group> How to clear faulted.

# haconf –dump –makero 2: 3: 4: 4: 5: 5: Start VCS and verify the cluster 1: Start VCS on the new node # hastart 2: Run the GAB configuration command on each node to verify that port a and port h include the new node in the membership.Adding and removing cluster node Q-1 How to add a node in an existing cluster? Ans: Adding a node into an existing cluster is a multi steps process. /etc/llttab and /etc/gabtab) in the new node and update the files on the existing node.orig . node must be physically connected with the cluster.cf. Configure LLT and GAB Create the LLT & GAB configuration files (/etc/llthosts. which are given below: 1: Backup the configuration file # cp /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main. Add the node to an existing cluster We have to perform below given tasks in any of the existing node of a cluster 1: Make to cluster configuration R/W # haconf –makerw 2: 3: Add the new node to the cluster # hasys –add <new node name> Copy main. 1: Set up the hardware Before adding a node to an existing cluster. # /sbin/gabconfig -a Q-2 How to remove a node from an existing cluster? Ans: Removing a node from a cluster includes many steps.cf Start vcs on the new node # hastart Now make the configuration again read only. 1: Connect the VCS private Ethernet controllers 2: Connect the node to the shared storage Install the VCS software in the node Install the VCS software and install the license.cf file from an existing node to new node # scp /etc/VRTSvcs/conf/config/main.cf new_node:/ /etc/VRTSvcs/conf/config/main.

d/S99vcs /etc/rc3.d/S92gab /etc/rc2. # hagrp –modify <group> SystemList –delete <node> Delete the node from the cluster # hasys –delete <node> Now again make the cluster configuration Read Only.2: 3: 4: Check the status of the nodes and the service groups # hastatus –summary Switch service group which is online on the node leaving the cluster # hagrp –switch <service group> to <node name> Delete the node from the VCS configuration 1: Make the cluster configuration R/W # haconf –makerw 2: 3: 4: 5: Stop the cluster on leaving node # hastop –sys <node> Delete the leaving node from the service group’s SystemList attribute. # mv /etc/rc2.d/s99vcs Remove VCS package from the node 6: 3: 4: Some General Questions Q-1 Ans: How to shutdown a node in VCS cluster? Shutting down a VCS node is multi step process. 1) Make the cluster configuration Read/Write # haconf –makerw .d/s92gab # mv /etc/rc3. GAB and VCS from starting up in future. Remove VCS configuration on the node leaving the cluster 1: Unconfigure and unload LLT and GAB # /sbin/gabconfig –U # /sbin/lltconfig –U 2: Unload the LLT and GAB modules # modunload –i <gab_module> # modunload –I <llt_module> Rename the startup files to prevent LLT.d/S70llt /etc/rc2.d/s70llt # mv /etc/rc2. # haconf –dump –makero 5: Modify the LLT and GAB configuration files to reflect changes Modify /etc/llthosts. /etc/llttab and /etc/gabtab files on the remining node on the cluster.

# hagrp –freeze <service group> -persistent 4) Stop the cluster on the node that is going to be down. # hastop –local –force 5) Rename the VCS startup script # cd /etc/rc3. 1) Start the VCS on this node # hastart –force 2) Make the service group online if they were made offline before the system down.2) Either Switchover or failover all the service group which are online on shutting down node to remaining node # hagrp –switch <service group> -to <node name> 3) Freeze all the service group which are online in the cluster.d # mv s99vcs S99vcs Q-2 Ans: How do check the status of VERITAS Cluster Server? hastatus –sum Q-3 Which is the main config file for VCS and where it is located? Ans: main.d # mv S99vcs s99vcs 6) Now reboot the box. Q-7 What is the use of halink command? . # hagrp –online <service group> -sys <node name> 3) Unfreeze all the service groups which are frozen. Q-4 Ans: Q-5 Ans: Which command you will use to check the syntax of the main. # hagrp -unfreeze <service group> -persistent 4) Now make the cluster configuration Read-Only # haconf -dump –makero 5) Now again move back the VCS startup script # cd /etc/rc3.cf? hacf -verify /etc/VRTSvcs/conf/config How will you check the status of individual resource of VCS cluster? hares –state <resource> Q-6 What is the service group in VCS? Ans: Service group is made up of resources and their links which you normally requires to maintain the HA of application. Follow the below given instructions. Once the system will come up after reboot.cf is the main configuration file for VCS and it is located in /etc/VRTSvcs/conf/config.

Q-10 How to switchover the service group in VCS? Ans: hagrp –switch <service group> to <node> Q-11 How to online the service groups in VCS? Ans: hagrp –online <service group> -sys <node> Q-12 How to access the VCS cluster management console? Ans: VCS cluster management console can be accessed by the below given URLs: http://Servername:8181/cmc/ or https://Servername:8443/cmc Q-13 How to access the Cluster Manager Java Console? Ans: #/opt/VRTSvcs/bin/hagui Q-14 What is Jeopardy? Ans: When a node in the cluster is having only one interconnected link remaining. offline. called jeopardy membership. GAB has two major functions: 1: Cluster membership GAB maintains cluster membership by receiving heartbeat from LLT. then it’s very difficult for GAB to discriminate between system or network failure. 2: VCS operates the cluster as a single node cluster. Q-15 What is the main daemon of VCS? Ans: had (high availability daemon) which is started by hashadow daemon. two actions occur: 1: Service groups running on this node placed in auto disabled state. Other systems in the clusters are partitioned off in a separate cluster membership. switch etc. . schedule shutdown and reboot.Ans: halink is used to link the dependencies of the resources Q-8 What is the difference between switchover and failover? Ans: Switchover is an manual task where as failover is automatic. When a system no longer receives heartbeats from a cluster peer. Q-16 What is GAB? Ans: Group Membership Services/Atomic Broadcast (GAB) is responsible for cluster membership and reliable cluster communication. A service group in auto disabled state may failover on a resource or group fault but can’t failover on system fault. broken because of some disaster or system hung. This memebship prevent cluster from split brain condition. Q-9 What is the use of hagrp command? Ans: hagrp is used for doing administrative actions on service groups like online. You can switchover service group from online cluster node to offline cluster node in case of power outage. hardware failure. But the failover will failover the service group to the other node when VCS heartbeat link down. When a system is placed in jeopardy membership. damaged. GAB marks the node as down. A special membership category takes effect in this situation.

Q-19 How many nodes can join a Cluster? Ans: Maximum of 32 nodes is supported in VCS. Q-22 How do you shutdown a Veritas Cluster Server. If a link is failes. LLT distributes all inter communication across all configured network links. The atomic broadcast functionality is used by HAD to ensure that all systems within the cluster receive configuration change messages. Q-17 What is LLT? Ans: Low Latency Transport (LLT) is used for all cluster communication. leaving the applications running from the command line? Q-23 What is coordinator disk? Ans: Coordinator disks are three standard disks or LUNs set aside for I/O fencing during cluster reconfiguration. LLT has 2 major functions: 1: Traffic Distribution LLT works as a backbone for GAB. 2: Heartbeat LLT is responsible for sending and receiving heartbeat signals. These disks provide a lock mechanism to determine which nodes get to fence off data drives from other nodes. Heartbeat is used by GAB to determine cluster membership. Q-18 How many network links are supported in LLT? Ans: 8 links are supported. A node must eject a peer from the coordinator disks before it can fence the peer from the data drives.2: Cluster communication GAB provides the guranteed delivery of messages to all the systems. Q-20 What is heartbeat? Ans: Heartbeat is an Ethernet broadcast packet. This packet notifies all othe nodes that sender is functional. each of which doesn’t know about the other subcluster. it is possible for one cluster to separate into 2 subclusters. This is the only broadcast traffic generated by VCS. Q-24 What is IO fencing and how to configure IO fencing? Ans: IO fencing is a feature that prevents data corruption in the event of a communication breakdown in a cluster. traffic is directed to the remaining link. Coordinator disks do not serve any other storage purpose in the VCS configuration. This concept of racing for control of the coordinator disks to gain the ability to fence data disks is key to understanding prevention of split brain through fencing. Q-21 What is split brain condition? Ans: When all the cluster interconnected links fail. IO fencing is used to remove the risk . For example two systems could try to import the same storage and cause data corruption. The two subclusters could each carry out recovery actions for the departed system. Each node sends 2 hearbeat packets per second per interface.

Q-25 How to upgrade VCS? Ans: 1) Removing the deprecated resource type 2) 3) Q-26 How to perform minimal downtime upgradation in VCS? Q-27 How to upgrade Solaris OS in which VCS is running? Ans: To upgrade a Solaris OS in which VCS is running. Follow the below instruction: 1) Stop VCS on this node Make the VCS configuration R/W # haconf –makerw Move all service groups from this node to another node and freeze this node: # hasys –freeze –persistent –evacuate <node name> # Make the cluster configuration Read/Only? # haconf –dump –makero # Stop the cluster on this node # hastop –force –local 2) Stop. I/O fencing allows write access for members of the active cluster and blocks access to storage from nonmembers. even a node that is alive is unable to cause damage. VRTSgab VRTSllt Now switch to multi user mode and start VCS # init 3 # hastart Now unfreeze this node # hasys –unfreeze –persistent <node name> 6) . unconfigure and unsinstall LLT and GAB on this node Unconfigure GAB # gabconfig –U Unconfigure LLT # lltconfig –U Now remove GAB and LLT packages # pkgrm VRTSgab VRTSllt Start the installvcs program which is under the directory cluster_server 3) 4) 5) Now upgrade Solaris and switch to single user mode Now Install and configure LLT and GAB # pkgadd –d .associated with split brain condition.

# haconf –dump –makero .

Sign up to vote on this title
UsefulNot useful