vcs node

Question

hii like to clarify.when a node join to vcs&nbsp;then in its memory all the information from the other nodes are filled.thus this node sees if there he should bring up the resource group that normally start on it.when he leave the cluster the information is updated on remaining cluster nodes and the service group fail over.right?tnx

frankgfan · Accepted Answer

Hello,In CVM configuration, any vx* commands which will lead to a vxvm configuration change (commjands like vxassist, vxmake, vxsd, vxplex etc) need to be executed on the CVM master (with new releases from 6.2, the command can be issued on any nodes as now there is a GAB port y which can ship commands to the cvm master for execution).VCS commands like hares, hagrp, haclus etc do not change VxVM metadata so can be executed on any nodes in the cluster, so long as the node is in online running state in the cluster.Frank

riaanbadenhorst · Answer

It works like this.There is a special network between the cluster nodes which is called llt. This network allows another protocol called gab to keep all cluster nodes up to date with the status of all cluster resources. Any status changes and configuration updates are distributed via gab.When a node starts up it joins network and check if anybody else is online. If there are enough nodes online it gets the configuration from them and decides based on the rules in the main.cf if it needs to online anything (based on the current state in cluster).If it finds that nobody is online it has to wait for enough nodes to join it. When they do, it distributes the configuration to the others and then again based on the rules, they online the resources.For nodes leaving, or resources failing, the state is again distributed to all nodes and based on the rules in the configuration they decide where to online resourcesThats it at a high level

frankgfan · Answer

Hello,&nbsp;when a node starts and if there is another node in running state, the node will take a snapshot of cvs configuration from the running node via llt network.&nbsp; you can see this info from engine_A.log.&nbsp; if there is not any node in running state, the node will read on disk vcs configuation (main,cf) and buid up the cluster.&nbsp;if a node is shutdown, hastop command will be executed as part of system shutdown,&nbsp; since a system shutdown is considered as a system admin action, not a true failure., vcs service groups may not be switched over.&nbsp;here are some hastop command options and their meanings:&nbsp;&nbsp;&nbsp; The -local option stops the VCS server on the system on which the command is issued. When the VCS server stops a system, the system’s service groups are also stopped.&nbsp;&nbsp; The -force option stops the VCS server, but allows the service groups to continue running.&nbsp;&nbsp; The -evacuate option migrates all groups to other systems, if possible.&nbsp;&nbsp; The -noautodisable option ensures that service groups that can run on the node for which hastop is invoked are not autodisabled while VCS is stopped. The -noautodisable option can also be used with -evacuate option, but not with -force option.please also read this technote https://support.symantec.com/en_US/article.TECH11477.htm to know some vcs behavior in a system restart.Frank&nbsp;

cliffordb · Answer

There have been good answers, but I want to make a few clarifications:
In VCS (outside of cluster file system), there is no "master" node.&nbsp; All servers that participate in the cluster have identical state status for all resources.&nbsp; All VCS commands are atomic.&nbsp; Either all servers get updated successfully, or the command falis.&nbsp; VCS is a state machine that works across mulitple separate operating system instances.&nbsp;&nbsp; Each OS has a complete picture of the state of all servers participating in the cluster.&nbsp;&nbsp;
As host enter and exit the cluster, all active nodes are updated.&nbsp; Every time a resoruce or service group is changed: turned on or off or moves, created or deleted, all nodes are notified.&nbsp; Again, either all nodes are updated, or the change fails.
&nbsp;
Regarding behavior of ServiceGroups when a node joins or leaves the cluster:&nbsp; the behavior is dictated by several paramenters.&nbsp; As a default, when a node fails, its ServiceGroups are moved to other existing cluster members.&nbsp; How the ServiceGroups are distributed is beyond this discussion.&nbsp; The Admin guide give very detailed examples on how to control behavior of ServiceGroups when a node leaves on purpose (admin shutsdown a server for maintenance) versus a hardware/softawre failure.
Cluster Volume Manager does have a master/slave system for lock managment only.&nbsp; If you are not using CFS, then you don't need to consider the idea of master/slave.

linuly · Answer

Hi,In vcs cluster an designated coordinator is elected.When the cluster is running every hagrp,hares including resource switch&nbsp; so on command will talk to DC.right?tnx&nbsp;

frankgfan · Answer

Hello,there are two types VCS configurations:&nbsp; failover and CVM (cluster volume manager, also known as parallel configuration).&nbsp; In CVM configuration there is one node elected as a CVM master.In failover configuration (a service group is onlined on one node at any given time) there is no master node.Can you please elaberate the followings?1. an designated coordinator&nbsp;2. DCis your cluster running on Windows platform or Unix?Frank

Forum Discussion

vcs node

10 Replies

Related Content

vcs less nodes

Unable to start VCS on one Node. Its two node cluster

Re: Command to check Primary Node in 4 node CFS Cluster

DB failures in VCS node

Active VCS node fails when reboting passive node

Recent Discussions

Configure two Mount type resources of nfs FStype attribute using the same share

order

key registration and reservation

Verifying that primary and dr clusters replication is synced

vcs can create logical nic