09-14-2013 02:43 AM
Moved from post "vcs upgrade" as a separate issue:
When a resource is added from one vcs node with: haconf -makerw hagrp -add groupw hares -add diskgroup haconf -dump -makero Then all the above commands are executed on all vcs nodes.right?had from every vcs nodes using gab knows that now should to execute the above commands. when a new node join to an vcs then all the information regarding nodes,resource group so on are loaded into memory from the remote vcs nodes.right? tnx so much, marius
09-14-2013 02:47 AM
The command issued on one node will result in the config copy held in memory being updated on all nodes, so that all nodes have the same in-memory config containing the newly added resource.
When a new node joins, the config is read from memory from the other nodes.
09-15-2013 01:51 AM
09-15-2013 05:19 AM
When you run" hares -modify", the main.cf on local system disk is not updated, even on the node you run it on. When you run "haconf -makerw" - the in-memory contents of the VCS config is written to local disk - i.e main.cf and *types.cf.
09-15-2013 11:50 PM
09-16-2013 12:01 AM
09-16-2013 06:46 AM
correction to post above ( https://www-secure.symantec.com/connect/forums/are-vcs-commands-executed-all-nodes#comment-9226331 )
haconf -makerw only changes the config to read-write mode.
The config is only written to disk once you issue haconf -dump [-makero]
per man page: https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/manualpages/html/manpages/cluster_server/html/man1m/haconf.1m.html
Change VCS to read-write mode, after which changes to the configuration can be made while VCS is running. The configuration must be written back to disk by specifying the -dump option. Otherwise, when VCS stops and restarts later the configuration changes are not effective.
09-16-2013 06:14 PM
You are right Lee