The following is a Quick-Start guide for installing vCenter Operations Manager. It is a very straightforward setup, but it does have a couple preliminary steps, which will make the installation go much smoother. This article is written for vC Ops version 5.8.2 using the vSphere Web Client.
Install the VMware Client Integration Plug-in 5.5.0
When using the Web Client, the VMware Client Integration Plug-in is required for both deploying OVF’s as well as accessing VM consoles. If you haven’t already installed this, do it now before proceeding. I found the easiest way is to click on the link in the Web Client logon screen below the username and password fields. Follow the prompts and accept all defaults. You will be instructed to close the browser window. Upon completion, launch the Web Client again and choose to allow the plug-ins when prompted. You might even need to close the browser once more after changing the security settings. Once the link to “Download and Install the VMware Client Integration Plug-in” is gone, you are ready to proceed.
Configure the IP Pool
vCenter Operations consists of two VM’s deployed as a vApp. In order to prepare for the network configuration of the vApp, we must first set up the IP Pool.
- In the Inventory pane of the Web Client, click on the Datacenter object and then click on the Manage tab in the Content pane, and then click on Network Protocol Profiles. Then click on the “+” icon in the Network Protocol Profiles content area.
- Enter a name for the IP Pool and choose the associated network. This will be the network that the VM’s of vC Ops will reside in.
- Enter the network address for the corresponding network along with the subnet mask, gateway and DNS server addresses. There is no need to enable the IP pool.
- At this point, you can configure IPv6 or other network configurations, but these settings are not necessary.
- Review the Summary information and then click Finish to complete. You will now see your Network Protocol policy in the Web Client window:
Deploy the OVF Template
- Initiating the Deploy OVF Template wizard for vC Ops can be done using either method below:
- From the home screen on the Web Client, click on the vCenter Operations Manager icon and then click “Deploy vCenter Operations Manager”.
- Right-click the host that you’ll be deploying the vApp to and click “Deploy OVF Template.” Note: I discovered it’s quicker to use this option if you already downloaded the OVF template from VMware’s website and have the file saved to a local folder easily accessible from the Web Client.
- If you get the following prompt, uncheck the “Always ask before allowing this site” checkbox and then click the “Allow” button.
- The Deploy OVF Template wizard will launch. If you initiated the deployment using the vC Ops icon, the Source will automatically be pre-populated with the URL of the download file on VMware’s website. You will just need to supply the credentials for your my.vmware.com profile. Note: If you opted to right-click the host and click “Deploy OVF Template” in Step 1, you will have the option at this point to either download the OVF straight from VMware’s site or browse to the location of the file if you already manually downloaded it.
- Review the details and click Next.
- Accept the EULA. Click the Accept button and then click Next.
- Type a name for the vApp and then choose a folder or datacenter object to deploy the template.
- Select the size of deployment.
- Select which host to deploy the template.
- Select which datastore and virtual disk format to install the template. Keep in mind that if you choose “Thick Provision” for the disk format, you will need 384GB of disk space. Thin provision only requires 3.8GB. If storage policies are enabled, you will also have the option to select the policy.
After clicking Next, you might get the following error: “A connection error occurred. Verify that your computer can connect to vCenter Server.“
This is likely caused by a DNS issue or firewall setting. I ended up running the deploy template wizard directly from the vCenter server to get around this error. I obviously had a network issue somewhere that would ideally need to be resolved. For our purpose, my workaround was sufficient.
- For IP allocation, choose Static or DHCP depending on your environment. Verify the destination network settings.
- The next screen will allow minor customization. You might get prompted for invalid settings. If so, just manually change the time zone and IP address settings to match your environment. The IP addresses will be the specific IP addresses you allocated each of the two VM’s that make up the vApp.
- Review the settings in the last screen and then click Finish. You will notice the task is running in the Recent Tasks pane on the right.
Tip… I had a problem deploying directly from VMware’s site. The Deploy OVF template task hung at 35%. I ended up having to cancel the task and then manually deploy after downloading the OVF template first (Option 1.b. above). I found it easier and faster to deploy after already downloading it – it took about 3 ½ minutes to deploy that way!
In the inventory pane, you will see the vApp with the two vCenter Operations VM’s: Analytics VM and UI VM.
Clicking on the vC Ops vApp will display the vApp properties in the Content pane.
Power on the vC Ops vApp
- Once the deploy task is completed, you will need to power on the vApp. Right-click the vApp and click Power-On. No need to manually power on each individual VM. The start-up of each VM is controlled by the vApp settings. It will take a few minutes to fully power on the entire VM. Once this has been completed, vC Ops will be ready for initial configuration, which is covered in the next post.
- While you are waiting for the VMs to start up, right click on the vApp and click Edit Settings. Note the start order. Since this is a vApp, it is configured with a very specific start up order and actions. This can of course, be customized to your environment.
Part 2 of this series will cover the initial configuration of vC Ops to allow it to integrate with vCenter.