vCenter Operations Manager (vcops) installation steps
4) Deploy the vApp:
Note: These steps may be necessary for distributed vSwitch communication issues. Skip these steps unless you experience difficulties with initialization.
1) Download the vApp from VMware.com.
2) Using the vSphere Client, connect to the vCenter Server with the cluster where you are installing the vApp.
3) Set up the IP Pool:
2) Using the vSphere Client, connect to the vCenter Server with the cluster where you are installing the vApp.
3) Set up the IP Pool:
- Select the DataCenter which has the cluster where the vApp is to be hosted, and click the IP Pools tab.
- Click Add... at the top of the page. A dialog box opens.
- Enter a name for the IP Pool. (For example, vCOps.)
- Enter the subnet (not the subnet mask) that the vCenter Server resides on.
- Enter the subnet mask as a bit. (For example, a mask of 255.255.255.0 is equivalent to a /24 network.)
- Enter the Gateway IP.
- Do not enable the IP Pool, as this is not required for proper use.
- Click the DNS tab and enter the appropriate DNS information for this network.
Note: You can enter multiple DNS servers by separating them with a comma.
- Click the Associations tab and select the Port Group the vCenter Server is attached to, or one that can easily reach vCenter.
- Click OK.
- In the vSphere Client, click File > Deploy OVF Template...
- Follow the prompts in the Deploy OVF Template wizard.
Note: When specifying a disk format, VMware recommends using Thick Provisioned Eager Zeroed in vSphere 5.
- When specifying an IP allocation scheme, select Fixed (recommended) or DHCP.
Note: Fixed IP allocation requires you to provide two IP addresses for the two virtual machines in the vApp. DHCP allocation requires that you enable DHCP in your IP pool. Transient is not supported at this time. - Click Finish and wait for the deployment process to complete.
Note: These steps may be necessary for distributed vSwitch communication issues. Skip these steps unless you experience difficulties with initialization.
- Right-click the cluster which will host the vApp, and select Edit Settings.
- Click Rules.
- Click Add.
- Enter a name for the Rule. (For example, vCOps.)
- Select Keep Virtual Machines Together.
- Click Add.
- Select the UI VM and Analytics VM virtual machines.
- Click OK.
7) Set up vCenter monitoring:
8) After the installation is complete, browse to http://IP_address, where IP_address is the IP address or fully qualified domain name (FQDN) of the vApp.
- Browse to http://IP_address/admin, where IP_address is the IP address or fully qualified domain name (FQDN) of the vApp.
Note: You can confirm this address on the console of the UI virtual machine.
- Update the administrator password ("admin") which provides access to the Administration Portal and SSH access to the vApp.
Note: The password requires a minimum of eight characters that include at least one letter and one digit or special character. - Update the root password ("root") for the operation system of the vApp.
Note: The admin password and root password are different. Please document your root password.
- Enter a human-friendly name for the vCenter Server system.
- Enter the FQDN (recommended) or IP address of the vCenter Server system to collect information from and monitor.
- Enter the registration credentials for vCenter Operations Manager to use when connecting to the vCenter Server.
Note: The user credentials you provide must have administrator privileges within vCenter. VMware recommends the use of a service account. - (Optional) Enter the collection credentials for vCenter Operations Manager to use for collecting data from vCenter Server.
Note: Using separate collection credentials can be used to increase security, and only require read-only privileges within vCenter.
- Click Test to verify that vCenter Operations Manager can connect to the vCenter Server.
Note: If this step fails, verify that you are able to log into the vCenter Server using the credentials used in step f. - (Optional) If you have linked vCenter Server systems, select the appropriate members of the linked group to register with, and provide a name for each system. Each vCenter Server must be registered individually.
Note: You can register vCenter Operations Manager with a subset of vCenter Server systems for scalability or inventory management purposes. - (Optional) If vCenter Operations detects that you have vCenter Operations 1.x or Capacity IQ 1.x installed, provide the appropriate credentials to import the data from the older installations.
Note: This can only be performed during installation, and will not be presented in the Admin page after the installation. If this information must be imported post-installation, you must deploy a new vApp to do so.
9) To license vCenter Operations Manager:
- Using the vSphere Client, connect to the vCenter Server with the cluster where you are installing the vApp.
- Go to Home > Licensing.
- Verify that a vCenter Operations asset is listed.
- Click Manage vSphere Licenses.
- Enter the License in the top field and click Next.
- Click the Solutions tab and select vCenter Operations.
Note: If the solution is not visible, toggle Show all at the top of the list. - Click Next.
- Click Next.
- Click Finish.