vCenter Operations Manager – Adding Additional vCenters to Monitor
When it comes to vCenter, most companies I’ve worked with can easily utilize a single vCenter to manage all datacenters across their environment. However, when you add VMware’s SRM product into the mix, multiple vCenter servers become a requirement in defining protected and failover sites. On the flip side, when it comes to gathering and monitoring metrics with vCOps, a single vCOps deployment can encompass both environments. A typical vCOps deployment is only registered with a single vCenter, however, the Administration page allows you to add additional vCenters when needed. The process is pretty simple and works like a charm.
It should also be noted that when the environments are split among vCenters, it presents a great opportunity to utilize Super Metrics within vCOps. Super Metrics allow you to create your own custom metrics that are not included by default. For example, you can create a Super Metric to create a sum of total running VMs across all vCenters , total RAM available to VMs, and more.
To add a secondary vCenter server to vCOps, follow the steps below:
1. Determine what user/service account will be used to access vCenter and grant appropriate permissions.
2. Access the vCOps Administration page at https://<IP Address>/admin. Log in with “admin” using the password configured when vCOps was initially deployed.
3. Click on the New Registration button.
4. Enter pertinent information for the secondary vCenter server. Use the “Test Connection” option to ensure that appropriate credentials are used and that appropriate permissions have been configured on vCenter itself in step 1. After the test is successful, Apply the configuration. Usually takes around 5 minutes to complete.
After completed, you can now see the secondary vCenter listed on the Administration page.
To prove that it works, log into the normal UI and you should be able to view both vCenters.