Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to change the Site name of a Cloud Director instance (79349)

Last Updated: 8/17/2023Categories: How toTotal Views: 6421Language:
Chinese (Simplified)JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

When viewing objects in Cloud Director such as Organizations or Organization VDCs the Site name is listed.

Depending on the version of Cloud Director this could be an IP address or another unfriendly name.

In Cloud Director 10.2 and later the UI displays the Site with a name similar to the following:

Site name undefined (Site ID: <SITE_UUID>)

Cause

In Cloud Director the Site name is not set during the initial configuration and is left for the System Administrators to define as desired.
When unset the default value shown in Cloud Director versions prior to 10.2 may appear as a UUID, the hostname of the installation's API Public Address, or the IP address of a specific Cell.
When unset the default value shown in Cloud Director 10.2 may appear in a from similar to:

Site name undefined (Site ID: <SITE_UUID>)

Resolution

The Site name can be changed to a desired value for this Cloud Director instance to uniquely identify it.
This Site name of a Cloud Director instance can be updated via the Cloud Director API using the steps below.
If this Cloud Director instance has been registered with another Cloud Director instance for Multisite functionality the Site name change may take some minutes to reflect on the second Cloud Director instance.
Note: In the API calls below the version should match the API version of the Cloud Director instance in question. In the examples below 33.0 is used for a Cloud Director 10.0 instance. A full list of the API versions is available in the Cloud Director documentation here, VMware Cloud Director Documentation.

Log in as a System Administrator to the Cloud Director instance for which we wish to change the Site name using a REST API client such as Postman or Curl. Use the log in token as the Authorization:Bearer token in the subsequent API calls. For information on logging in to the Cloud Director API see the documentation here, Logging In.

Perform a GET against the localAssociationData URL for this Cloud Director instance:

Request:
GET https://cloud.example.com/api/site/associations/localAssociationData

Request Headers:
Accept: application/*+xml;version=33.0
Authorization: Bearer eyJ...Adw

In the response you will find a href URL for this Cloud Director Site similar to the following:

<Link rel="edit" href="https://cloud.example.com/api/site/associations/<ASSOCIATION_UUID>" type="application/vnd.vmware.admin.siteAssociation+xml"/>

Perform a GET Request against the href URL from step 3. to retrieve the configuration including the current Site name:

Request:
GET https://cloud.example.com/api/site/associations/<ASSOCIATION_UUID>

Request Headers:
Accept: application/*+xml;version=33.0
Authorization: Bearer eyJ...Adw

In the XML response you will see a <SiteName> entry with the current setting similar to the following:

<SiteName><SITE_NAME></SiteName>
Or
<SiteName>Site name undefined (Site ID: <SITE_UUID>)</SiteName>

To change the Site name to the desired friendly name, edit the XML response retrieved in step 4. and change the value address in the <SiteName> section to the desired value. For example:

Existing setting:
<SiteName>10.20.30.40</SiteName>
Or
<SiteName>Site name undefined (Site ID: <SITE_UUID>)</SiteName>

Updated setting:
<SiteName>cloud.example.com</SiteName>
Or
<SiteName>Example Cloud 1</SiteName>

Send the entire XML with the new Site name back to the href URL used in step 4. to retrieve the current setting. For example:

Request:
PUT https://cloud.example.com/api/site/associations/<ASSOCIATION_UUID>

Request Headers:
Accept: application/*+xml;version=33.0
Authorization: Bearer eyJ...Adw
Content-Type: application/vnd.vmware.admin.siteAssociation+xml

Request Body:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<SiteAssociationMember xmlns="http://www.vmware.com/vcloud/v1.5" xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1" xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:common="http://schemas.dmtf.org/wbem/wscim/1/common" xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vmw="http://www.vmware.com/schema/ovf" xmlns:ovfenv="http://schemas.dmtf.org/ovf/environment/1" xmlns:vmext="http://www.vmware.com/vcloud/extension/v1.5" xmlns:ns9="http://www.vmware.com/vcloud/versions" href="https://cloud.example.com/api/site/associations/<ASSOCIATION_UUID>" type="application/vnd.vmware.admin.siteAssociation+xml">
<Link rel="edit" href="https://cloud.example.com/api/site/associations/<ASSOCIATION_UUID>" type="application/vnd.vmware.admin.siteAssociation+xml"/>
<Link rel="edit" href="https://cloud.example.com/api/site/associations/<ASSOCIATION_UUID>" type="application/vnd.vmware.admin.siteAssociation+json"/>
<Link rel="remove" href="https://cloud.example.com/api/site/associations/<ASSOCIATION_UUID>" type="application/vnd.vmware.admin.siteAssociation+xml"/>
<Link rel="remove" href="https://cloud.example.com/api/site/associations/<ASSOCIATION_UUID>" type="application/vnd.vmware.admin.siteAssociation+json"/>
<Link rel="up" href="https://cloud.example.com/api/site/associations" type="application/vnd.vmware.admin.siteAssociations+xml"/>
<Link rel="up" href="https://cloud.example.com/api/site/associations" type="application/vnd.vmware.admin.siteAssociations+json"/>
<RestEndpoint>https://cloud.example.com</RestEndpoint>
<BaseUiEndpoint>https://cloud.example.com</BaseUiEndpoint>
<SiteId>urn:vcloud:site:<SITE_UUID></SiteId>
<SiteName>cloud.example.com</SiteName>
</SiteAssociationMember>

In the Cloud Director UI when logged in a System Administrator you should see an Updated Site task. Confirm that this task shows a Succeeded status.

Reload the Cloud Director UI to confirm that the Site name has changed as desired for example when viewing Organizations or Organization VDCs.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Android Enterprise の新しい EMM 登録が断続的に失敗する (79429)

KB
•
組織 VDC ネットワークの一覧表示または作成をする際に「プロパティ「remoteItems」の null を読み取ることができません」(Cannot read property 'remoteItems' of null) というエラーが表示される (79480)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director

Related Versions:

VMware Cloud Director 10.x

Take Our Survey

Support Assistant