This guide provides help with diagnosing and resolving issues that are specific to VMware Tanzu Operations Manager (Ops Manager) deployments on VMware vSphere.

For infrastructure-agnostic troubleshooting help, see Diagnosing Deployment Problems.

Common Issues

The following sections list common issues that you might encounter with Ops Manager and possible resolutions.

Ops Manager Installation Fails

If you modify the vCenter Statistics Interval Duration setting from its default setting of five minutes, the Ops Manager installation might fail at the MicroBOSH deployment stage, and the logs might contain the following error message:

The specified parameter is not correct, interval

This failure happens because Ops Manager expects a default value of five minutes, and the call to this method fails when the retrieved value does not match the expected default value.

To resolve this issue, launch vCenter, navigate to Administration > vCenter Server Settings > Statistics, and reset the vCenter Statistics Interval Duration setting to five minutes.

BOSH Automated Installation Fails

Before starting an VMware Tanzu Application Service for VMs (TAS for VMs) deployment, you must set up and configure a vSphere cluster.

If you enable vSphere DRS (Distributed Resource Scheduler) for the cluster, you must set the Automation level to Partially automated or Fully automated.

If you set the Automation level to Manual, the BOSH automated installation will fail with a power_on_vm error when BOSH attempts to create virtual VMs.

alt-text=On the New Cluster Wizard, the Automation Level page shows the Partially Automated button selected.

Ops Manager Loses IP Address After HA or Reboot

Ops Manager can lose its IP address and use DHCP due to an issue in the open source version of VMware Tools. For more information to troubleshoot this issue, see IP is not Getting Assigned in vSphere after Ops Manager Restart in the Knowledge Base.

Cannot Connect to the OVF in a Browser

If you deployed the OVF file but cannot connect to it in a browser, check that the network settings you entered in the wizard are correct.

  1. Access the Ops Manager installation VM using the vSphere Console. If your network settings are configured incorrectly, you cannot SSH into the installation VM.

  2. Log in using the private SSH key associated with the public SSH key that you provided when you imported the Ops Manager .ova in vCenter.

  3. Confirm that the network settings are correct by checking that the ADDRESS, NETMASK, GATEWAY, and DNS-NAMESERVERS entries are correct in /etc/network/interfaces.

  4. If any of the settings are incorrect, run sudo vi /etc/network/interfaces and correct the incorrect entries.

  5. In vSphere, navigate to the Summary tab for the VM and confirm that the network name is correct.

    alt-text=The Summary tab has two sections: General and Resources.

  6. If the network name is incorrect, right click the VM, select Edit Settings > Network adapter 1, and select the correct network.

  7. Reboot the installation VM.

Installation Fails with Failed Network Connection

If you experience a communication error while installing Ops Manager or MicroBOSH Director, check the following:

  • Ops Manager requires that the NSX firewall routes are not blocked. All communication between Ops Manager VMs and vCenter or ESXi hosts route through the NSX firewall and are blocked by default. For more information on which ports to allow, see VMware Ports and Protocols for vSphere.

  • Open port 443. Ops Manager and MicroBOSH Director VMs require access to vCenter and all ESX through port 443.

  • Allocate more IP addresses. BOSH requires that you allocate a sufficient number of additional dynamic IP addresses when configuring a reserved IP address range during installation. BOSH uses these IP addresses during installation to compile and deploy VMs, install TAS for VMs, and connect to services. VMware recommends that you allocate at least 36 dynamic IP addresses when deploying Ops Manager and TAS for VMs.

Insufficient External Database Permissions

Upgrade issues can be caused when the external database user used for the network policy database is given insufficient permissions. To avoid this upgrade issue, ensure that the networkpolicyserver database user has the ALL PRIVILEGES permission.

check-circle-line exclamation-circle-line close-line
Scroll to top icon