How to modify the VMwareDisks resource attributes to reflect changes within the vSphere environment due to removal or addition of ESX servers within Veritas Cluster Server (VCS) configuration.

book

Article ID: 100010017

calendar_today

Updated On:

Resolution

This article provides the steps needed to modify the configuration from the command line to reflect changes when adding or removing ESX servers from the vSphere farm.
 
Step 1 - Addition or removal of ESX servers
Place configuration into maintenance mode (freeze persistent) either through selecting “Enter Maintenance Mode” within the Veritas HA tab within the vSphere management UI or via VCS command line from with one of the virtual machines that is a member of the VCS that is needed to be modified.
Execute command within a terminal or command window
 
haconf –makerw
hagrp -freeze -persistent
 
*replace with the service group that you are modifying – use hagrp –list to display the available service groups.
 
Step 2 – Modify VCS configuration with the addition or removal of ESX servers
Retrieve and modify the ESXDetails attribute value to reflect the ESX server changes being made.
From within a virtual machine that is part of the VCS, execute the command.
 
hares –display –attribute ESXDetails
 
*replace with the VMwareDisks resource type that you are modifying. use hares –list to display the resources within the service group.
 
Command output displays the current values being used. The ESXDetails attribute requires that existing values are passed back into the configuration along with changes being made.
 
#Resource                                    Attribute                 System       Value
SQLServer2008-SG-VMwareDisks  ESXDetails           global       
192.168.1.101 root=FTFrGTiTItMRuTHrJ
192.168.1.104 root=FTFrGTiTItMRuTHrJ
 
Modify the resource attributes with the new ESX details or remove the ESX details required with the command replacing SQLServer2008-SG-VMwareDisks with the resource within the service group being modified.
 
For example to add ESX server 192.168.1.106
 
hares -modify SQLServer2008-SG-VMwareDisks ESXDetails 192.168.1.101 root=FTFrGTiTItMRuTHrJ 192.168.1.104 root=FTFrGTiTItMRuTHrJ 192.168.1.106 root=FTFrGTiTItMRuTHrJ
 
or to remove ESX server 192.168.1.104
 
hares -modify SQLServer2008-SG-VMwareDisks ESXDetails 192.168.1.101 root=FTFrGTiTItMRuTHrJ
 
The letter values after the “root=” value are the encrypted password of the user which has the ability to modify the disk configuration. The example above uses “root” replace this user with the corresponding user as designated within your configuration.
 
If this user credentials are not unique across the ESX servers in the configuration then to apply the corresponding value needed use the “vcsencrypt –agent” command and type the password for the user required and the value needed will be displayed once encryption has been applied.
 
Step 3 – Modify ESX farm configuration with the addition or removal of ESX servers
Add or remove ESX server from the ESX Farm as recommended by VMware. Be aware that if adding ESX servers into the farm that the configuration must reflect the ability to host virtual machines that are part of a VCS cluster in that any storage or network configuration must be consistent between member servers hosting VCS nodes.
 
Step 4 – Exit from maintenance mode or unfreeze application service group.
To exit from maintenance mode (unfreeze persistent) either by “Maintenance Mode” in vSphere UI or via CLI from with one of the virtual machines that is part of the Veritas Cluster
 
hagrp -unfreeze -persistent
haconf –dump –makero
 
*replace with the service group that you are modifying – use hagrp –list to display the available service groups.
 
With the modifications made the configuration is complete and the systems continue to operate as expected.
 

Note: The VMwareDisks agent has been modified to be able to use the vCenter details instead of ESXi details in the ESXDetails attribute of the VMwareDisks resource.  This removes the need to have the individual ESXi hosts added to the attribute.

Issue/Introduction

During the configuration of using the vCenter application wizard with Veritas Cluster Server (VCS) a request is made to provide ESX Server details for which the virtual machines will be running within. If the ESX Server environment is added to or removed then these changes need to be reflected in the VCS configuration. At this time it is not possible to modify a configuration from with the vSphere UI once the wizard has completed. Any changes to the configuration have to be made via Veritas Operations Manager, VCS Java UI or command line from with the virtual machine.

Attachments

VCS VMDisk modify due to DRS.docx get_app