Share This:

In this post, I will share configuration steps which can help you configure your existing BMC Cloud Lifecycle Management stack when you introduce a new vCenter server while keeping the naming convention, for Clusters and Data-stores the same.


There can be multiple scenarios, example: vCenter server crash, scaling hardware, moving your Datacentre where you would like to introduce a new vCenter.


Introducing new vCenters creates configuration issues in your existing BMC Cloud Lifecycle Management stack because underlying GUID’s of different attributes, example: Clusters, Data-stores etc. are changed and it doesn’t match the ID’s present in Cloud DB.


Let me walk you through the configuration steps:


Retrieving “OLD VC GUID” provided that old vCenter server is still enrolled in Bladelogic Server Automation.


Open the following URL from a web browser:


https://<BSA-hostname>:<port>/type/PropertySetClasses/SystemObject/Server/?name=<Old VCname>&username=<user>&password=<password>&role=<role>


Replace following attributes with its actual values:




<Old VC Name>





This will return the GUID of the old vCenter. Example:





<PropertySetInstances totalCount="1">

<PropertySetInstance name="<BSA-Hostname>" description="" type="/type/PropertySetClasses/SystemObject/Server"dbKey="DBKey:SDeviceModelKeyImpl:2000100-2005700" objectId="e5d36224-cbca-44e3-83ae-d778ae27768f" uri="/id/SystemObject/Server/e5d36224-cbca-44e3-83ae-d778ae27768f" modelType="SERVER" modelTypeId="5004"/>






You can refer to the values (highlighted) of “objectID” and “URI” attribute as the GUID of the vCenter.


In the BSA console, select the old vCenter from the server list. Change the Name property of that to the new vCenter and run a USP job. Confirm the IP address etc. For example:




Once done, open Configuration – Property Dictionary view. Expand Built-in Property Classes. Select Connection and then click the Instances Tab. Select the connection to the old vCenter and edit the entry.


Change the Name, Description, CONNECTION_URL, CONNECTION_USER and CONNECTION_PASSWORD to that of the new vCenter. For example:





In the Virtualization built-in property class select the Instances tab. Find the entry of the old vCenter and select edit.


Change the Name and VIRTUAL_ENTITY_CONNECTION entries to that of the new vCenter:




In the properties of the vCenter, confirm the VIRTUALIZATION property (expand the “extended” property) is using the property specified previously (reference to new vCenter name). For example:




After that, open the following URL from a web browser:




Replace following attributes with its actual values:




<Old VC Name>




Confirm the GUID is the same as the old vCenter. This will mean, the GUID in the backend forms will not need to be replaced, if the GUID is different because the VC was re-enrolled in BSA, or the old vCenter was removed and new one added (effectively the same as re-enrolling), please follow the steps mention in KA365301 ( along with following steps:


Modifying the Cluster information:


Live browse the vCenter, select the cluster, right mouse click and select properties. Make a note of the domain-cxxx value:




Open the BMC.CORE:BMC_Cluster form (http://<MidTierServerName>:<Port>/arsys/forms/<EnterpriseARServerName>/BMC.CORE%3ABMC_Cluster) at Cloud DB, find the BMC.ASSET entry for the cluster, select the Custom tab and view the entry for the ExternalID. Correct the domain-cxxx value, make a note of the old domain-cxxx value so you can search for this in the BMC.CORE:BMC_StorageVolume form in later stage:




Change the highlighted fields to the correct value of the vCenter name and domain-cxxx:






Open the BMC.CORE:BMC_StorageVolume form (http://<MidTierServerName>:<Port>/arsys/forms/<EnterpriseARServerName>/BMC.CORE:BMC_StorageVolume) do a search with %domain-cxxx% in the ExternalID field (where domain-cxxx is the old ID from previous steps above). Replace (if necessary) all of the old domain-cxxx values with the new value:




Repeat the steps for all clusters onboarded to CLM.


Check if already enrolled servers in BSA are using the new VC in their Virtualization instance by opening the Virtualization built-in property class, select the Instances tab, find the instance and select Edit. Make sure the VIRTUAL_ENTITY_MANAGER matches the new vCenter.


I hope this article helps to understand good ways to reconfigure the BMC Cloud Lifecycle Management (CLM) stack when you introduce new vCenter, please share you experiences or feedback on this use case with comments below.


Visit my other blogs. You can share the links with others if you find these useful.


Please rate this blog, if shared information is useful, by clicking below option.


PS: At BMC we always strive to make our customers realize more value from our Products and be successful.

As you all know that we have introduced a new communication channel-“CHAT”. This gave our customers an additional option to contact us. For details, please refer Connect with BMC Support Team over Chat sessions.


You can also join the Customer Support Community to learn about and provide feedback on ways Customer Support can enable your success.