vCOPS For 3PAR Using HP StoreFront Analytics Pack

A little while ago I was working on a infrastructure design with a colleague who is a double HP Master ASE.  We where talking about the lack visibility of vCenter Operations Manager into the 3PAR layer and due to this we had to combine vCOPS with a HP tool to give a complete view of the stack.  Somewhat messy, but it achieved what the client wanted.

Whilst at HP Discover, David Scott gave a coffee talk to the bloggers and he mentioned a vCOPS plugin for 3PAR.  So Justin Vashisht @3cvguy, Bart Heungens @BartHeungens and I hit the show floor to find out more.

HP StoreFront Analytics Pack

In true HP form they have named the vCOPS plugin beginning with ‘Store’.  HP StoreFront Analytics provides an in depth view of all 3PAR components including CPG, storage systems, drive cages, drives, disk ports, fibre channel ports, fans and more.

  • HP StoreFront Analytics Pack for vCenter Operations Manager – Free Trial*
  • HP StoreFront Analytics Pack for vCenter Operations Manager – QuickSpecs
  • HP StoreFront Analytics Pack for vCenter Operations Manager – User Guide

*The free trial is for 60 days after which HP StoreFront Analytics will continue to run, however you will only have access to the HP Store Monitoring dashboard.

Enjoy the video below of vCOPS for 3PAR using HP StoreFront Analytics Pack

How To: Install vCenter Operations Manager

vCenter Operations Manager has been missing from the vmfocus.com lab for far to long!

With this in mind let’s walk through how to install vCenter Operations Manager.

IP Pools

VMware require IP Pools to be configured for most of their OVF’s nowadays.  Chris Wahl wrote a great blog post on Managing & Configuring IP Pools which is our first step.

Go into the Datacenter Object in vSphere and Select IP Pools Tab then Add

IP Pools 01

Give the IP Pool a name, Subnet Mask and Gateway

IP Pools 02

Note: We have specifically chosen not to enable the IP Pool

Then jump over to Associations and associate the IP Pool with a Port Group that your vCenter Operations Manager will reside on.

IP Pools 03

Once configured it should look something like this.

IP Pools 04

Install vCenter Operations Manager

The next step is to download vCenter Operations Manager which is located here. As of the time of this blog post the most recent version is VMware vCenter Operations Manager Standard 5.7.2.

I’m not going to talk you threw how to upload an OVF as it’s a simple case of going to File > Deploy OVF Template > Select Location and following the wizard.

When you get to the IP Address Allocation Policy select ‘Fixed’

VCOPS01

vCOPS is a vAPP which is made up of two VM’s the UI and Analytics VM both of which need an IP Address.

VCOPS02

The vAPP seems to take a large amount of time, so my suggestion is to make a cup of tea!

vCOPS Initial Configuration

Browse to your UI VM IP Address, in my case it is https://VMF-VCOPS01/admin as I thougth I would be clever and enter an A record.

Login with the following credentials:

U: admin

P: admin

The first task is to enter the Hosting vCenter Server details, in some scenarios for example a management cluster the vCenter the vCOPS resides in is different to the one that it monitors.

vCOPS03

Accept the Security Alert to trust your vCenter.

Next change the passwords for your admin account and root accounts, once done hit Next.

vCOPS04

TOP TIP: The root password is vmware

Enter your vCenter details, the collector has access to all the Objects within vCenter, so ideally you want to specify credentials for this as well.

If you receive an error ‘connecting to VC at https://vCenter/sdk failed’ see my blog post on this subject

vCOPS05

Click Next on the Import Data screen and then Finish on the Linked VC Registration page.

You will receive a security Warning on your vCenter Server stating that the vCOPS certificate is untrusted. Install the certificate and click Ignore

vCOPS06

If successful, you should be greeted with the vCenter Operations Manager Administration screen.

vCOPS07

You should be able to verify this by go to the Home Screen of your vSphere Client and you should have vCenter Operations Manager under Solutions and Appliances

vCOPS08

That’t it all you need to do now is assign your license key and you are ready to rock ‘n’ roll.

How To: Replace vCenter Operations Manager Certificates

In the previous blog  post entitled How To: Replace vCenter 5 & VUM Certificates we had replaced out certificates for vCenter and VUM but had only refreshed out vCOPS and View administration portals to connect to the trusted vCenter certificate.

In this post we are going to walk threw the process of replacing the vCenter Operations Manager Certificate, we are assuming that the prerequisites in How To: Replace vCenter 5 & VUM Certificates are in place.

Step 1 – Certificate Request

On an Windows Server 2008 based VM that has rights to request and enroll a certificate from your Internal CA

Click Start > Run > MMC > File > Add/Remove Snap-in

Select Certificates > Add > Computer Account > Next

vCOPS01

Expand Personal > Certificates > Right Click > All Tasks > Request New Certificate

vCOPS02Click Next > Select Active Directory Enrollment Policy

vCOPS03

Select your Certificate Template (mines called HorizonView) then click on ‘More information is required to enroll for this certificate.  Click here to configure settings’.

vCOPS04

Change Subject Name to Common Value and enter the Fully Qualified Domain Name of your vCenter Operations Manager UI VM.  In my case it is VMF-VCOPS01.vmfocus.com and Add this to the certificate request.

Next change the Alternative Name to DNS and enter the NetBIOS name e.g. VMF-VCOPS01 and the Fully Qualified Domain Name e.g. VMF-VCOPS01.vmfocus.com and Add this to the certificate request

vCOPS20

Click Next and then Enroll

vCOPS21

Once enrolled you will see the new certificate is in your Personal folder

vCOPS07

Step 2 – Export Certificate

Well, it’s not much good to us here, so we need to export it.  Right Click the Certificate > All Tasks > Export

vCOPS08

Select Yes, export the private key and hit Next

vCOPS09

Select Personal Information Exchange – PKCS #12 (.PFX) and hit Next

vCOPS10

Enter the password for the Private Key (we will need this later so make sure you remember it)

vCOPS11

Choose a destination and name for the exported certificate

vCOPS12

If all has gone to plan, hit Finish

vCOPS13

Step 3 – Convert .PFX to .PEM

The kicker is that vCenter Operations Manager doesn’t accept .PFX certificates only .PEM so we need to convert it using OpenSSL

Copy the certificate to the C:\ on your OpenSSL VM and then drop into the CMD and cd to C:\OpenSS-Win32\bin

The command we need to run is:

openssl pkcs12 -in C:\vCPOSCert.pfx -out C:\vCOPSCert.pem -nodes

You will be prompted for your password, enter this and your certificate is now in .PEM format

vCOPS14

Step 4 – Import Certificate into vCenter Operations Manager

Launch the vCOPS Admin URL e.g. https://vcops01/admin and enter your credentials.

Select the SSL tab and then browse to your certificate location and hit Install

vCOPS15

Once done, click o the Status Tab and Restart Application Controls.

vCOPS16

If we have been successful, when you browse to your vCOPS URL you should see a Trusted Certificate

vCOPS17

vCOPS: Unable To Connect To vCenter Server. Details: Connecting to VC at https://vCenter/sdk failed

When installing and configuring vCenter Operations Manager you receive the error message ‘Unable To Connect To vCenter Server. Details: Connecting to VC at https://vCenter/sdk failed’ when trying to enter the FQDN of you vCenter Server

Error

Resolution

If you enter the IP Address of your vCenter then you are able to continue which means the issue is with DNS.

Go to your IP Pool > DNS and then enter the DNS Domain and an IPv4 DNS Server

vCOPS Fix

Unfortunately, we now have to power the vCOPS vAPP off and power it back again for the new IP Pool settings to take effect.  Once done, go back threw the initial configuration and you will be on the Import Data screen.

vCOPS Working