Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Synchronizing a Logical Data Center

 

vCloud administrators plan for data center capacity and create the organization virtual data center (VDC) based on current requirements and some predictions for the future. With prolonged usage, the VDC might run out of compute, network, or storage capacities.

This topic discusses the benefits, procedure, and limitations of synchronizing a Logical Data Center (LDC).

Benefits

vCloud administrators then need to modify the VDC using the vCloud Director console to add more capacity, or to remove a network that is no longer required or has become obsolete. These changes made from the vCloud Director console result in an inaccurate representation of the corresponding Logical Hosting Environment (LHE) in BMC Cloud Lifecycle Management.

In BMC Cloud Lifecycle Management 4.5 and earlier, the organization VDC is onboarded as a LDC only once. The cloud administrator cannot refresh the information if the organization VDC is modified using the vCloud Director console. Therefore, those versions of BMC Cloud Lifecycle Management cannot use any of these new resources that have been added in the organization VDC.

Starting with BMC Cloud Lifecycle Management 4.6 and later, the cloud administrator can refresh the LDC information with new networks added or existing networks removed from the VDC.  

To synchronize an LDC

To update the compute, network, or storage information associated with a LDC, complete the following steps:

  1. Under Quick Links on the left, click Resources under the Compute section.
  2. Select the LDC that you want to refresh from the table.
  3. Click the Synchronize Logical Data Center icon Synchronize_LDC_icon.gif.

After the activity is marked as complete, you can click the Refresh icon refreshbtn.gif in the upper-right corner of the window to refresh the Resources table so that the resources changed in the vCloud Director console appear in the table.

Limitations

  • The Virtual Cluster onboard  or synchronization operation will fail unless there is at least one hypervisor switch that is common between the virtual cluster and the pod. In the case of a physical server, there should be at least one matching switch and switch port combination common between the pod and physical sever NIC in BMC Server Automation.
  • When the VDC is modified via the vCloud Director console, networks synchronize in the LHE correctly, however, the related Networks type tags in the blueprints are not updated. You need to create Networks type tags and then assign them to the blueprints manually.
  • Even if modified networks are available in BMC Cloud Lifecycle Management after synchronization, provisioning of servers on those modified networks fails because the updated networks are not in vApp templates. For successful provisioning, you must update the vApp templates with the modified networks.

  • LHE synchronization fails in the following scenarios:-    If it is run for the first time with the network name changed in the target vCloud environment.

    -    If one or more SOIs provisioned on the network have been renamed in the target vCloud environment.

Related topic

Registering-VMware-vCloud-providers

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*