Please enter search query.
Search <product_name> all support & community content...
How to rename a node that is part of a Veritas InfoScale High Availability cluster (VCS) for Windows
Article: 100016220
Last Published: 2020-08-26
Ratings: 0 0
Product(s): InfoScale & Storage Foundation
Description
How to rename a node that is part of a Veritas InfoScale High Availability cluster (VCS) for Windows
Important!
Create backups of original cluster files from all nodes in the cluster before you begin:
- %vcs_home%/conf/config/main.cf
- %vcs_root%/comms/llt/llttab.txt
- %vcs_root%/comms/llt/llthosts.txt
Procedure to rename VCS node:
- Stop the VCS engine on all nodes in the cluster with command: hastop -all -force
- Run once per cluster
- Stop VCS communication services on all nodes in the cluster with command: net stop llt /y
- Run on every node in the cluster
- Update llthosts.txt file in a text editor on all nodes to replace the node names with the updated names on every node in the cluster
- Default location: C:\ProgramFiles\Veritas\comms\llt
- Note: VCS communication services will not be able to restart if the files are not properly updated on all nodes
- Update llttab.txt file in a text editor on all nodes to replace the node name for the set-node line with the new name on every node in the cluster
- Default location: C:\ProgramFiles\Veritas\comms\llt
- Note: VCS communication services will not be able to restart if the files are not properly updated on all nodes
- Update sysname file in a text editor on all nodes to replace the node name with the new one
- Default location: C:\Program Files\Veritas\Cluster Server\conf
- Update VCS cluster configuration
- Perform these steps on one node in the cluster
- Open main.cf file in a text editor and perform "find and replace" to replace the old node names with the new ones for all occurrences
- Default location: C:\Program Files\Veritas\cluster server\conf\config
- Open main.cf file in a text editor and perform "find and replace" to replace the old node names with the new ones for all occurrences
- Perform these steps on one node in the cluster
- Rename the node updated in step 6 following Microsoft guidelines and reboot
- Once node in step 7 is back online, then proceed with rename/reboot for other nodes as required
- If there is only one server to update, then run command hastart -all on the renamed server to bring the cluster services back online after reboot
The cluster should be able to come online with updated names if all steps are followed as directed. Please contact Veritas Support if any errors are returned or if the service cannot start after reboot.