Deploying Ops Manager with NSX-T for Enterprise PKS

Page last updated:

Warning: Pivotal Container Service (PKS) v1.5 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy.
To stay up to date with the latest software and security updates, upgrade to a supported version.

This topic provides instructions for deploying Ops Manager on VMware vSphere with NSX-T integration for use with Enterprise Pivotal Container Service (Enterprise PKS).


Before deploying Ops Manager with NSX-T for Enterprise PKS, you must have completed the following tasks:

In addition, review the supported Ops Manager versions for Enterprise PKS. See Enterprise PKS Release Notes or the Product Compatibility Matrix.

Review to the known issues for your version of Ops Manager. See one of the following:

SSH Key Requirements for Ops Manager v2.6

Beginning with Ops Manager v2.6 for vSphere, password authentication is replaced with SSL/TLS authentication. If you are installing Ops Manager v2.6 on vSphere, you cannot deploy Ops Manager successfully without adding a public SSH key in the appropriate field of the Customize Template screen. If you do not add a public SSH key, Ops Manager shuts down automatically because it cannot find a key and may enter a reboot loop. For more information, see Passwords Not Supported for Ops Manager VM on vSphere in the Ops Manager v2.6 release notes. For installation instructions specific to Ops Manager v2.6, see Deploy Ops Manager in Deploying Ops Manager on vSphere.

When you add the key value to the Public SSH Key field, you must enter the entire public key similar to the format required for authorized_keys. For example, the format required is similar to the following:

ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAnZBapWsER/EO1hLYvV/rkZe78mUBueZGHx1kw+ByfNbLoA385Cm72L+6qq40yOIH6R42nHN/bynbeHOD4Ptes4/s2lrLJtTzEWgH9XYnId4sE5f+QTFd2kRtTzZcu8WvFudEIyCIWjO+o9yvPETs05dEl/3KDn+t9uXxiszrG9Ycb2uNNpmDES+ohm9BQQFmpwFnao+UuQbRXLCcQ3SoE3Ai5Z9O+3PBwm0IByx87/dUuqvVISAJ8yGu2hJobx9PPStFERtUsfx5x+WIu9XIkrl5tzxgH9hBDsOS9cVUYJ7kKUUf1yyro6ocHyu6TWHJHSJLt8Z2FULxMPpqdn+8Xw== my-key

For additional information, refer to the following KB article: Generate an SSH key pair for installing Ops Manager v2.6 on vSphere.

Deploy Ops Manager for Enterprise PKS

  1. Before starting, refer to the Enterprise PKS Release Notes for supported Ops Manager versions for Enterprise PKS. Or, download the Compatibility Matrix from the Ops Manager download page.
  2. Before starting, refer to the known issues in the PCF Ops Manager Release v2.5 Release Notes or the PCF Ops Manager Release v2.6 Release Notes.
  3. Download the Pivotal Ops Manager for vSphere installation file from the Pivotal Network.

    1. Open a browser to the Pivotal Operations Manager download page on the Pivotal Network.
    2. Use the dropdown menu to select the supported Pivotal Operations Manager release.
    3. Select the Pivotal Ops Manager for vSphere download option. This downloads the Pivotal Ops Manager for vSphere VM template as an OVA file.
  4. Log into vCenter using the vSphere Client (HTML5) to deploy the Ops Manager OVA. This can also be done using the using the OVFTool or the PowerCLI.

  5. Select the Resource Pool defined for the Enterprise PKS Management Plane. See Create Enterprise PKS Management Plane if you have not defined the Enterprise PKS Management Resource Pool.

  6. Right click the Enterprise PKS Management Plane Resource Pool and select Deploy OVF Template.

  7. At the Select an OVF template screen:

    • Click Browse.
    • Select the Ops Manager OVA file you downloaded and click Open.
    • Click Next. Om install 01
  8. At the Select Name and folder screen, enter a name for the Ops Manager VM (or use the default name), select the Datacenter, and click Next Om install 02

  9. At the Select a compute resource screen, select the Enterprise PKS Resource Pool or Cluster object and click Next. Om 03

  10. At the Review details screen, confirm the configuration up to this point and click Next. Om 04

  11. At the Select Storage screen, select the desired Datastore, and click Next. Om install 04

    Warning: Ops Manager requires a Director VM with at least 8 GB memory. For more information, see Provisioning a Virtual Disk in vSphere.

  12. At the Select Networks screen:

    • If you are using vSphere 6.7, select the Enterprise PKS Management T1 Logical Switch that you defined when Creating the Enterprise PKS Management Plane, and click Next.
    • If you are using vSphere 6.5, select a vSS or vDS port-group such as the standard VM Network, and click Next. Om install 05

    WARNING: With VMware vCenter Server 6.5, when initially deploying the Ops Manager OVA, you cannot connect to an NSX-T logical switch. You must first connect to a vSphere Standard (vSS) or vSphere Distributed Switch (vDS). After the OVA deployment is complete, before powering on the Ops Manager VM, connect the network interface to the NSX-T logical switch. The instructions below describe how to do this. This issue is resolved in VMware vCenter Server 6.7. For more information about this issue, see the VMware Knowledge Base.

  13. At the Customize template screen, enter the following information, and click Next.

    • IP Address: The IP address of the Ops Manager network interface, for example (assuming non-routable NAT-mode).
    • Netmask: The network mask for Ops Manager, for example,
    • Default Gateway: The default gateway for Ops Manager to use, for example (assuming non-routable NAT-mode).
    • DNS: One or more DNS servers for the Ops Manager VM to use, for example
    • NTP Servers: The IP address of one or more NTP servers for Ops Manager, for example
    • Admin Password: (Required for Ops Manager v2.5.) A default password for the “ubuntu” user. If you do not enter a password, Ops Manager will not boot up.
    • Public SSH Key: (Required for Ops Manager v2.6.) Enter the public SSH key to allow SSH access to the Ops Manager VM. You must enter the entire the public SSH key in the expected format. See SSH Key Requirements for Ops Manager v2.6.
    • Custom hostname: The hostname for the Ops Manager VM, for example ops-manager. Om install 06 Om install 07
  14. At the Ready to complete screen, review the configuration settings and click Finish. This action begins the OVA import and deployment process. Om install 08

  15. Use the Recent Tasks panel at the bottom of the vCenter dashboard to check the progress of the OVA import and deployment. IF the import or deployment is unsuccessful, check the configuration for errors. Om 10

  16. (vSphere 6.5 only) If you you initially selected a vDS or vSS network for the Virtual Hardware > Network adapter 1 setting, after the OVA deployment completes successfully, right-click the Ops Manager VM and select Edit Settings. Change the vNIC connection to use the nsx.LogicalSwitch that is defined for the PKS Management Plane, for example LS-MGMT-PKS. Deploy om 15

  17. Right-click the Ops Manager VM and click Power On. Deploy om 16

Configure Ops Manager for Enterprise PKS

The first time you start Ops Manager, you are required select an authentication system. These instructions use Internal Authentication. See Set Up Ops Manager Authentication in Configuring BOSH Director on vSphere in the PCF documentation for configuration details for the SAML and LDAP options.

  1. If you are using the NAT deployment topology, create a DNAT rule that maps the Ops Manager private IP to a routable IP. See Create Enterprise PKS Management Plane for instructions.

  2. If you are using the No-NAT deployment topology, create a DNS entry for the routable IP address that you set for Ops Manager. Use FQDN to log into Ops Manager.

    Note: Ops Manager security features require you to create a fully qualified domain name to access Ops Manager. See Installing Pivotal Cloud Foundry on vSphere.

  3. Navigate to the IP address (NAT mode) or FQDN (No-NAT mode) of your Ops Manager VM in a web browser. The “Welcome to Ops Manager” page should appear.

    Note: It is normal to experience a brief delay before the interface is accessible while the web server and VM start up.

    Om install 10

  4. Select Internal Authentication and provide the following information:

    • Username, Password, and Password confirmation to create a user with administrative privileges.
    • Decryption passphrase and the Decryption passphrase confirmation. This passphrase encrypts the Ops Manager datastore, and is not recoverable.
    • HTTP proxy or HTTPS proxy, follow the instructions in Configuring Proxy Settings for the BOSH CPI.
  5. Read the End User License Agreement, and select the checkbox to accept the terms.

  6. Click Setup Authentication. It takes a few minutes to initialize the database. Deploy om 19

  7. Log in to Ops Manager with the username and password that you created. Deploy om 20

  8. Verify success. You should be able to log in, and you should see the BOSH Director tile is present and ready for configuration, indicated by the orange color. Om install 11

Next Step

After you complete this procedure, follow the instructions in Generating and Registering the NSX Manager Certificate for Enterprise PKS.

Please send any feedback you have to