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 network pods

You can update a pod after it has been onboarded. This capability enables you to scale a pod when necessary.

For example, a pod might be running out of virtual ports for virtual machine (VM) provisioning, because the pod was originally configured with one vswitch and a maximum of 120 virtual ports. You can update the pod with an additional access switch, which will provide more virtual ports for any new network containers that are created for the pod.

Other scenarios for updating a pod include adding new load balancer nodes or firewalls into the pod.

This topic contains the following sections:

To update an onboarded pod

  1. In BMC Network Automation, update the pod. See Editing-a-pod. You can add components to the pod, or remove nodes (Switch, Firewall, or Loadbalancer) from the pod that are no longer being used. You must ensure that the node is not referenced in any network container prior to removal. 

    Note

    If you are removing a hypervisor switch node from a pod, if it is the only hypervisor switch being referenced by an onboarded cluster, then the pod synchronization operation will fail in BMC Cloud Lifecycle Management. To remove a hypervisor switch node from the pod, there must be one or more alternate switches common between the pod and the on-boarded cluster, otherwise the pod synchronization fails to remove the switch from BMC Cloud Lifecycle Management.

  2. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
  3. Under Quick Links on the left, click Pods under the General section.
  4. Select the pod you want to synchronize.
  5. Click the Synchronize Pod icon synch_pods.gifto synchronize the network pod with any changes to the pod since it was onboarded.
  6. After the pod is synchronized, the associated virtual cluster must also be synchronized, as described in the section below.

To update a virtual cluster

To update the virtual hosts, virtual resource pools, and virtual disk repositories associated with a virtual cluster, complete the following steps:

  1. Under Quick Links on the left, click Resources under the Compute section.
  2. Select the virtual cluster you want to refresh from the table.
  3. Click the Synchronize Virtual Cluster icon syncvirtcluster.gif.

After the activity is marked as complete, you can click the Refresh icon refreshbtn.gifin the upper-right corner of the window to refresh the Resources table so that the newly onboarded resources appear in the table.

Note

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.

 

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