Wednesday, March 19, 2014

Part 4 - Configuring vCenter Operations Manager Post Deployment!

In my last post, I gave you step by step instructions on deploying the vCenter Operations Manager vAPP. Once the vAPP is powered on after deployment, you need to do the initial configuration on the vCOps Admin UI to have the vAPP integrated with your vCenter environment.

Without further ado let's start the configuration.

1- Click on the vCOps vAPP in the vCenter and click on the summary tab. Under summary tab click on the hyperlink highlighted below. This will re-direct you to the vCOps admin page. 

Alternatively, you can also open a web browser and give the IP of the UI VM with "/admin" and you will get on the admin page.

2- You can see the URL which I spoke about in the previous step here in this screenshot. Use the following credentials to Login to the Admin UI.

username - admin
password - admin

3- Provide the details of the vCenter where the vCOps vAPP has been deployed. This is just to keep a track of vCOps vAPP demographics and is an optional step. Verify the Analytics VM IP address and click on Next.

4- Click on Yes to accept the self generated certificate.

5- On the next screen you can reset the admin account and root account password. With vCOps 5.8 onward this password has to be a special password. for e.g. Dashboard@123

The default password for the root account is vmware

The root account here can be used to login to the UI VM or Analytics VM via ssh or console for troubleshooting, advanced customization etc.

6- Now comes the part where the vCenter which you need to monitor needs to be specified. We will pause here to discuss the Registration User and Collector User.

Registration User - If you plan to monitor ALL the resources of a vCenter Server then you can just use the registration user which has atleast Read Only rights on the root level of the vCenter. In such a situation collector user is not required.

Collector User - If you plan to monitor only a subset of your vCenter environment, then you should use the Collector user along with the Registration user. While the the Registration User is used for registering the vCenter Server, the Collector user will enable vCOps to only populate and monitor the Objects on which the collector user has atleast Read Only rights. Their is a VMware KB on this topic.

I will not enter the Collector User as I need to monitor everything and click on Next.

7- If you upgrade from VMware Capacity IQ to vCOps you will get an option to import the old data from your previous install. (This is a rare sight though).

8- On the Next screen , vCOps will automatically find all the Linked vCenter Servers if there are any. You would have the option to register the Linked VCs here. 

In case you have a non Linked VC which you want to register with your vCOps, you can finish this wizard and  register additional VCs on the Admin UI. On the other hand if you want to avoid a Linked VC from registration, you can leave it as it is and click on Finish.

It will take around 2 to 5 minutes for this registration to complete and you are done.

I will close this post now. Stay tuned for the next part where I will give you a tour of vCenter Operations Manager Admin User Interface. Stay tuned :-)

Share & Spread the Knowledge!!

No comments:

Post a Comment