sylvertech
Contributor
Contributor

3PAR - Add vendor provider problem

Hi,

We have a 3PAR F200 and we try to Add a vendor provider in our Vcenter but we encourt a problem. I followed the following procedure: see image1.image1.jpg

Went I try to follow this procedure "HP 3PAR Management Plug-in and Recovery Manager 2.4.0 Software for VMware vSphere User Guide", it dosn't work. The error message is: " A problem was encountered while registering the provider". The port 9997 was configured both on my vCenter "Add Vendor Provider" and the software "HP 3PAR Management Plug-in and Recovery Manager" on my vCenter host.

What is the problem?

SAN 3PAR F200 with OS version 3.1.1

HP 3PAR Management Plug-In and Recovery Manager v 2.3

Vcenter 5.1

Thank you

0 Kudos
6 Replies
gajuambi
Enthusiast
Enthusiast

0 Kudos
sylvertech
Contributor
Contributor

Hi,

I've read these articles but as the base, it has not solved my problem.

thank you

0 Kudos
regnak2012
Enthusiast
Enthusiast

Hi,

I had to do this last month and my notes were as follows:

VASA - register an account in the storage system credential section (on the 3PAR Recovery Manager Server) and then you can use it in the vasa storage system mapping section in vCenter.

Mike

0 Kudos
Sreejesh_D
Virtuoso
Virtuoso

try the following solution from the thread  http://communities.vmware.com/thread/336511 .

This can happen if you are using the C# vSphere Client on a non-domain machine.  Try logging into the vCenter server (RDP/vSphere Console) and add the VASA provider through the vSphere Client on the vCenter Server.  You could also try to use the new vSphere Web Client.  See here for more info: http://vmtoday.com/2013/03/configuring-vmware-vasa-for-emc-vnx/.

0 Kudos
sylvertech
Contributor
Contributor

Hi,

We tried the solutions listed here, but it does not work. Another idea?

0 Kudos
klwood2000
Contributor
Contributor

I found this corrected my issue with registering the provider.

Microsoft released patch 931125 in December.  This patch was only meant for clients, not servers.  Apparently it was still released to servers.  It installs 330 root trust certificates.  This ends up filling up the certificate memory on the server (16K).  When the VASA provider authenticates against the server, the list of certs is truncated and it doesn't receive the certificate that it is expecting.

  

The fix is to delete the certificate registry key in Windows and then re-register the VASA certificate.  Once done, the VASA provider snapped right in.  I was able to pull the volume statistics when looking at a VM or a host, etc.  I backed up the Certificate registry key.

I have included the Microsoft link for your reference.

 

http://support.microsoft.com/kb/2801679

0 Kudos