- Proactive Smart Alerts
- Intelligent Operations Groups
- vSphere Health Monitoring
- Self-learning Performance Analytics
vCenter Operations Foundation 5.6 Deployment
1. Download the vCenter Operations Manager 5.6 virtual appliance, in OVF format, from the vSphere product support site – http://www.vmware.com/support/product-support/vsphere/index.html
2. In the vSphere Client, click File > Deploy OVF Template.
3. On the Deploy OVF Template window, click Browse.
4. Browse to the vCenter Operations OVA package, then click Open.
5. Click Next.
6. Click Next.
7. Click Accept to accept the EULA, then click Next to proceed.
8. Name the vApp, choose its location in the VMs and Templates Inventory, then click Next.
9. Choose a Configuration, then click Next.
|vApp Configuration||vApp vCPUs/RAM||vApp Supported VMs|
|Small||4 vCPU/16GB RAM||up to 1500 VMs|
|Medium||8 vCPU/25GB RAM||1500 – 3000 VMs|
|Large||16 vCPU/34GB RAM||3000+ VMs|
10. Choose Host/Cluster, then click Next (Note: If you have a specific host or cluster selected in inventory, the vApp will automatically be deployed there.)
11. Choose the destination datastore, then click Next.
12. Choose the disk format (Thin, Eager Zeroed Thick, or Lazy Zeroed Thick), then click Next. Since my datastore is NFS, the disk will automatically be Thin.
13. Choose the network for your vApp, then click Next.
14. Choose your IP address allocation policy. Click Next.
15. Apply Timezone and IP addresses here if necessary. Click Next to proceed. As noted, you will need to have deployed an IP Pool within vCenter Server. If you haven’t done so, cancel and deploy the IP Pool per the vCenter Operations Manager Deployment and Configuration guide.
16. Optionally, check Power on after deployment to have the vApp automatically power on once deployed. Click Finish to complete the wizard.
vCenter Operations Foundation 5.6 Initial Configuration
1. Once the vApp is fully deployed, go to https://<UI VM IP Address>/admin in your web browser.
2. Log in as admin, with the default password listed below.
|vCenter Operations Manager User||Default Password|
3. Enter in the hosting vCenter Server details. These are the details for the vCenter Server in which the vCenter Operations vApp has been deployed. If you have multiple vCenter Servers to be monitored, those will be specified later.
If you are using self-signed SSL certificates, you will be prompted to proceed with connection since the cert will be unverified. Click Yes to trust the vCenter Server.
4. Set new admin and root passwords for both VMs in the vApp. Click Next to proceed.
5. Specify the information for the vCenter Server to be monitored. (Note: If you wish to use a vCenter user with limited rights to do data collection from your vCenter Servers, include that user here as the Collector User. Since the Registration User will need administrator rights, it can also be used to collect data.)
6. Since this is the first registration of a vCenter Operations Manager appliance, no previous registrations were detected. Click Next to proceed. For help on importing data into a new vCenter Operations Manager implementation, please refer to the vCenter Operations Manager documentation. https://www.vmware.com/support/pubs/vcops-pubs.html
7. If you have no linked vCenter Servers to register, click Finish to complete the initial configuration. If you have a linked vCenter Server to register, choose it from the drop down menu and click Register, then Finish to complete.
8. When the vCenter Server registration is complete, you should see a new Solutions and Applications icon for vCenter Operations Manager. Double-click it to open vCenter Operations Manager.
9. vCenter Operations Manager, without a license key, i.e., eval mode, automatically defaults to Foundation license mode. Click About, and you should see something very similar to this:
In Licensing, you should also see the vCenter Operations Manager asset without a license key. In Foundation license mode, there is none to apply.
You’re now ready to start using vCenter Operations Foundation 5.6!