Installing Ops Manager on vSphere
Page last updated:
This guide describes how to install Ops Manager on vSphere.
If you experience a problem while following the steps below, see Diagnosing Deployment Problems or the Known Issues sections of the following topics:
Ops Manager v2.9 Release Notes in the Ops Manager documentation
VMware Tanzu Application Service for VMs v2.9 Release Notes in the TAS for VMs documentation
Isolation Segment v2.9 Release Notes in the TAS for VMs documentation
VMware Tanzu Application Service for VMs [Windows] v2.9 Release Notes in the TAS for VMs [Windows] documentation
- Release Notes in the TKGI documentation
This section describes the resource requirements for installing Ops Manager.
Note: If you are using the Cisco Nexus 1000v Switch, see the Using the Cisco Nexus 1000v Switch with Ops Manager for more information.
Note: When installing Ops Manager on a vSphere environment with multiple ESXi hosts, you must use network-attached or shared storage devices. Local storage devices do not support sharing across multiple ESXi hosts.
You can install Ops Manager with one of two runtimes. For more information about the requirements for each runtime, see the following:
- VMware Tanzu Application Service for VMs (TAS for VMs): TAS for VMs on vSphere Requirements. For information requirements when deploying with NSX-T, see the Requirements section of Deploying TAS for VMs with NSX-T Networking.
- VMware Tanzu Kubernetes Grid Integrated Edition (TKGI):
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.
Ops Manager requires read/write permissions to the data center level of the vSphere Inventory Hierarchy to successfully install. VMware recommends defining a custom role for the service account that has all privileges for all objects in the data center, including propagating privileges to children.
Since Ops Manager passes all required credentials through to BOSH, you only need one service account with the required vSphere privileges to complete the installation. Setting up separate service accounts for Ops Manager and BOSH is not necessary or recommended.
For more information about service account requirements, see the following topics:
- TAS for VMs: vSphere Service Account Requirements
- TKGI: Create the BOSH/Ops Manager Service Account in Preparing vSphere Before Deploying TKGI
Note: You can also apply the default VMware Administrator System Role to the service account to achieve the appropriate permission level.
The following guides contain best practices for securing and managing a vSphere installation:
This section describes the steps for installing Ops Manager.
Complete the following procedures to install Ops Manager on vSphere:
See the following topics for additional configuration options:
After completing the procedures above, configure a runtime.
For information about installing and configuring a runtime, see the following:
- TAS for VMs:
- Installing and Configuring TAS for VMs on Windows
- Installing Small Footprint TAS for VMs