Pivotal Knowledge Base

Follow

IP not getting assigned in vSphere after Ops Manager restart

Environment

Product Version
Pivotal Cloud Foundry® (PCF) Ops Manager 1.6 and later

Cause

The purpose of this article is to demonstrate how to troubleshoot networking issues with the Ops Manager VM when the virtual data center (vCenter) is migrated.

One example of this is when Ops Manager is migrated between virtual data centers in vSphere, an operation that can sometimes cause the Ops Manager VM to not be assigned an IP address.

There is also a known issue where Ops Manager will revert to DHCP following a vSphere HA Failover.

Resolution

  1. Using vSphere client, right-click on Ops Manager, navigate to Edit Settings > Options > Advanced(under vApp Options). Check if the Summary shows as "Configured". Click on Properties and ensure that all the Properties - admin_password, DNS, gateway, ip0, netmask0, ntps_servers are present. If not, you would need to add all of them as per your configuration.

  2. Ensure that the vApp Options are set to "Enable". This can be found by right-clicking on Ops Manager, navigating to Edit Settings > Options > vApp Options.

  3. Verify that the VMware Tools option is checked. It can be found by right-clicking on Ops Manager, navigating to Edit Settings > Options > vApp Options.

  4. To ensure the properties are accessible from inside the VM, perform a power-off and power-on of the VM from vSphere.
    Note: It is critical to perform the power-on from vSphere otherwise the vApp Options will not be exposed to the VM

 

Comments

Powered by Zendesk