

Technical Support’s primary role is to respond to specific queries about product features and functionality. Technical Support Symantec Technical Support maintains support centers globally. Symantec Corporation 350 Ellis Street Mountain View, CA 94043 Government shall be solely in accordance with the terms of this Agreement. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. Other names may be trademarks of their respective owners. Symantec, the Symantec logo, Veritas, Veritas Storage Foundation, CommandCentral, NetBackup, Enterprise Vault, and LiveUpdate are trademarks or registered trademarks of Symantec corporation or its affiliates in the U.S. Legal Notice Copyright © 2011 Symantec Corporation.

Product version: 5.1 SP1 PR2 Document version: 5.1SP1PR2.0

Veritas Storage Foundation™ Cluster File System Administrator's Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. If the Cluster Volume Manager (CVM) agent for Veritas Cluster Server (VCS) determines that the vxconfigd daemon is not running on a node during a cluster reconfiguration, vxconfigd is restarted automatically.Veritas Storage Foundation™ Cluster File System Administrator's Guide Linux If the vxconfigd daemon is stopped on both the master and slave nodes, the slave nodes do not display accurate configuration information until vxconfigd is restarted on the master and slave nodes, and the daemons have reconnected. For example, shared disk groups listed using the vxdg list command are marked as disabled when the rejoin completes successfully, they are marked as enabled. (Neither the kernel view of the shared configuration nor access to shared disks is affected.) Until the vxconfigd daemon on the slave node has successfully reconnected to the vxconfigd daemon on the master node, it has very little information about the shared configuration and any attempts to display or modify the shared configuration can fail. When the vxconfigd daemon is restarted on the slave, the slave vxconfigd daemon attempts to reconnect to the master daemon and to re-acquire the information about the shared configuration. If the vxconfigd daemon is stopped on a slave node, the master node takes no action. In this case, the vxconfigd daemons on the slave nodes have not lost information about the shared configuration, so that any displayed configuration information is correct. Such attempts do not succeed until the vxconfigd daemon is restarted on the master. If the vxconfigd daemon is stopped on the master node, the vxconfigd daemons on the slave nodes periodically attempt to rejoin to the master node. If the vxconfigd daemon stops, different actions are taken depending on which node this occurred:
