WindowsAdminGuru BLOG

In some disaster recovery scenarios or part of project requirements we may need to rename existing VCS nodes, please find the steps for completing the activity - 1. Stop the Veritas Cluster Server (VCS) engine on all nodes in the cluster. Open a command prompt and type @ command prompt: hastop -all -force 2. Stop VCS communications on all nodes in the cluster. Open a command prompt and execute net stop llt. When prompted to stop VCSComm and GAB, answer Y. This needs to be done on each node in the cluster. 3. Modify the llthosts.txt file in a text editor on all nodes to replace the node names with the new ones. The default location of the file is in C:\Program Files\Veritas\comms\llt . This needs to be done on each node in the cluster. 4. Modify the llttab.txt file in a text editor on all nodes to replace the node name on the set-node line with the new one. The default location of the file is in C:\Program Files\Veritas\comms\llt . This needs to be done on each node in the clus...

Problem: The MountV resources failed to online on Cluster Node1 Cause: The MountV resources failed to probe on node1 because the volumes did not import successfully in VEA. This is due to a PnP timeout as the volumes take long time to arrive PS- Note that there are several fixes in SFW 5.1 SP2 addressing volume arrival timeout Resolution :  1- Symantec recycled the VM services (Vxob, actionagent, Vxvm and Vxgn)- However, VxVM was taking a long time to restart so we rebooted the node 2- Symantec Recommends that please upgrade Cluster nodes to SFW 5.1 SP2 for long term solution