Highlighted
2 Bronze

Error creating VASA Provider for File - VNX OE 7.1.65 vSphere 5.1

HI folks,

My VASA Provider for Block configured OK but I'm having problems with the File side of the config.

Configuring the VASA Provider in the VI Client or the Web Client errors out with: A problem was encountered while registering the provider.

Settings are:

URL: https://10.0.186.240:5989/vasa/services/vasaService

Login: local\vasa-file

The cimlog.txt on the Control Station shows this in the log:

08-Jul-2013 09:08:17.274 -82766736-I- ECOM WebServer: Performing SSL handshake with incoming connection

08-Jul-2013 09:08:17.283 -82766736-I- ECOM Webserver: Secure connection has been established with incoming client

08-Jul-2013 09:08:17.354 -82766736-I- ECOM WebServer: Performing SSL handshake with incoming connection

08-Jul-2013 09:08:17.363 -82766736-I- ECOM Webserver: Secure connection has been established with incoming client

08-Jul-2013 09:08:17.368 -82766736-C- Celerra_SecurityManager: Entering Celerra_SecurityManager::getAuthenticator

08-Jul-2013 09:08:17.371 -82766736-C- Celerra_SecurityManager: Exiting Celerra_SecurityManager::getAuthenticator

08-Jul-2013 09:08:17.374 -82766736-C- Celerra_SecurityManager: Entering Celerra_SecurityManager::getUserManager

08-Jul-2013 09:08:17.376 -82766736-C- Celerra_SecurityManager: Exiting Celerra_SecurityManager::getUserManager

08-Jul-2013 09:08:17.392 -82766736-C- Celerra_SecurityManager: Entering Celerra_Authenticator::authenticate

08-Jul-2013 09:08:17.496 -82766736-C- Celerra_SecurityManager: Entering Celerra_SecurityManager::getUserECOMRole userNamevasa-file

08-Jul-2013 09:08:17.499 -82766736-C- Celerra_SecurityManager: Celerra_SecurityManager::getUserECOMRole adding role[vmadmin] for group[vmadmin]

08-Jul-2013 09:08:17.502 -82766736-C- Celerra_SecurityManager: Celerra_SecurityManager::getUserECOMRole adding role[operator] for group[nasadmin]

08-Jul-2013 09:08:17.505 -82766736-C- Celerra_SecurityManager: Celerra_SecurityManager::getUserECOMRole adding role[nasadmin] for group[nasadmin]

08-Jul-2013 09:08:17.507 -82766736-C- Celerra_SecurityManager: Exiting Celerra_SecurityManager::getUserECOMRole, the role is vmadmin,operator,nasadmin,

08-Jul-2013 09:08:17.510 -82766736-C- Celerra_SecurityManager: Celerra_Authenticator::authenticate. Created Celerra Security Token [User[vasa-file] mappedUserName[vasa-file] userHost[0:0:0:0:0:FFFF:A00:BA6E] timeStamp[1.3733e+09] roleList[vmadmin,operator,nasadmin,] ]

08-Jul-2013 09:08:17.513 -82766736-C- Celerra_SecurityManager: Celerra_Authenticator::authenticate. Created Security Token is [User[vasa-file] mappedUserName[vasa-file] userHost[0:0:0:0:0:FFFF:A00:BA6E] timeStamp[1.3733e+09] roleList[vmadmin,operator,nasadmin,] ]

08-Jul-2013 09:08:17.516 -82766736-C- Celerra_SecurityManager: Exiting Celerra_Authenticator::authenticate

08-Jul-2013 09:08:17.519 -82766736-C- Celerra_SecurityManager: Celerra_UserManager::registerCertificate. userName [vasa-file] certificateObject [vmCertificate] action [register]

08-Jul-2013 09:08:17.651 -82766736-E- ECOM WebServer: Certificate already exists in the certificate store.

08-Jul-2013 09:08:17.654 -82766736-C- Celerra_SecurityManager: Entering Celerra_SecurityManager::getAuthenticator

08-Jul-2013 09:08:17.657 -82766736-C- Celerra_SecurityManager: Exiting Celerra_SecurityManager::getAuthenticator

08-Jul-2013 09:08:17.659 -82766736-C- Celerra_SecurityManager:  Celerra_Authenticator::authorize. Got resourceName[root/emc/vmware:EMC_VASA_ServiceLeaf.RegisterVASACertificate],ResoureType[method]

08-Jul-2013 09:08:17.662 -82766736-C- Celerra_SecurityManager:  Celerra_Authenticator::authorize. Calling canRoleAcess with role[vmadmin],resourceName[root/emc/vmware:EMC_VASA_ServiceLeaf.RegisterVASACertificate],ResoureType[method]

08-Jul-2013 09:08:17.665 -82766736-I- ECOM: method root/emc/vmware:EMC_VASA_ServiceLeaf.RegisterVASACertificate exists in the table and accessible to vmadmin. Access granted.

08-Jul-2013 09:08:17.667 -82766736-C- Celerra_SecurityManager: Authorized

08-Jul-2013 09:08:17.670 -82766736-E- OperationHandler: CIMOM: All providers that service the class EMC_VASA_ServiceLeaf could not be loaded by the CIMOM.

08-Jul-2013 09:08:17.672 -82766736-I- VASAProtocolAdapter: VASASOAPRequestBase::streamFault: objList is NULL.

08-Jul-2013 09:08:17.673 -82766736-E- VASAProtocolAdapter: InvokeMethodOperation::writeResponse streamFault with errorCode: 1

08-Jul-2013 09:08:26.694 -51755920-I- ECOM WebServer: Performing SSL handshake with incoming connection

08-Jul-2013 09:08:26.702 -51755920-I- ECOM Webserver: Secure connection has been established with incoming client

08-Jul-2013 09:08:26.770 -51755920-I- ECOM WebServer: Performing SSL handshake with incoming connection

08-Jul-2013 09:08:26.779 -51755920-I- ECOM Webserver: Secure connection has been established with incoming client

08-Jul-2013 09:08:26.784 -51755920-C- Celerra_SecurityManager: Entering Celerra_SecurityManager::getAuthenticator

08-Jul-2013 09:08:26.787 -51755920-C- Celerra_SecurityManager: Exiting Celerra_SecurityManager::getAuthenticator

08-Jul-2013 09:08:26.790 -51755920-C- Celerra_SecurityManager: Entering Celerra_SecurityManager::getUserManager

08-Jul-2013 09:08:26.792 -51755920-C- Celerra_SecurityManager: Exiting Celerra_SecurityManager::getUserManager

08-Jul-2013 09:08:26.808 -51755920-C- Celerra_SecurityManager: Entering Celerra_Authenticator::authenticate

08-Jul-2013 09:08:29.424 -51755920-C- Celerra_SecurityManager: Celerra_Authenticator::authenticate. Invalid Parameter

08-Jul-2013 09:08:29.427 -51755920-E- local\vasa-file:Celerra_Authenticator::authenticate: Authenticated failed!

08-Jul-2013 09:08:29.430 -51755920-E- processOperation: <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"><s:Header/><s:Body><s:Fault><s:Code><s:Value>s:Sender</s:Value></s:Code><s:Reason><s:Text xml:lang="en-US">authentication failed</s:Text></s:Reason><s:Detail><ns1:InvalidSession xmlns:ns1="http://com.vmware.vim.vasa/1.0/xsd"><ns1:InvalidSession xmlns:ns3="http://fault.vasa.vim.vmware.com/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns3:InvalidSession"/></ns1:InvalidSession></s:Detail></s:Fault></s:Body></s:Envelope>(/disks/ixeng03/brm-builds/buildforge/ECOM/2.7.1/2/linux_gcc_4.1.0-x86-32/debug/smarts/ecom-addons/ProtocolAdapters/SOAPAdapter/VASA/VASAProtocolAdapter.cpp:178)

Labels (2)
0 Kudos
7 Replies
Highlighted
4 Ruthenium

Re: Error creating VASA Provider for File - VNX OE 7.1.65 vSphere 5.1

Chris,

The URL looks good.  Of course the assumption is that the IP is the Control Station (primary CS, or ideally IPalias in consideration of an installation with a pair of Control Stations).  I'll assume that you also received a message to verify the SHA1 thumbprint of the corresponding CS certificate.

Could you provide more information on the user: "local\vasa-file"


1) By specifying "local" it is an local user account (versus LDAP or Global scope)

FYI, you can leave off "local\" as local scope is assume for VNX for File


2) vasa-file

Can you confirm that the Local account you created meets the following requirements (as pasted from the KB article below):


a) Unisphere > Settings > Security > User Management > Local Users for File

b) Primary Group: "vmadmin"

c) Privilege: "vmadmin(VM Administrator)"



Here is a very good walk-through (ignore the fact for now that it specifies a specific error😞


emc297057: "Login to the VASA Provider on the VNX Control Station fails with "A problem was encountered while registering the provider"


There also are the "Virtualization for EMC VNX Release Notes for VNX OE for Block Release Notes Version <version> and VNX OE for File Version <version>" that have some details:

https://support.emc.com/search/?resource=DOC_LIB&AlloftheseWrds=Virtualization%20EMC%20VNX%20Release...

Just to mention it, you can use local "root" account also maybe for testing (as you'll read, the other default users: global account sysadmin nor local account nasadmin have the necessary privileges).

Highlighted
2 Bronze

Re: Error creating VASA Provider for File - VNX OE 7.1.65 vSphere 5.1

Hi Chris,

I get the error with or without the scope specified in the username and with the root account or other local NAS accounts.

I've been through the KB article and the Release Notes. I'm suspecting this might be an issue with the DNS in our lab at the moment. I'll be testing further once we get things stabilized.

0 Kudos
Highlighted
3 Argentum

Re: Error creating VASA Provider for File - VNX OE 7.1.65 vSphere 5.1

Did you find an answer to this as I have a customer with same problem?

0 Kudos
Highlighted
3 Argentum

Re: Error creating VASA Provider for File - VNX OE 7.1.65 vSphere 5.1

Found the answer to this after a frustrating waste of time today.

The release notes are wrong in that they have a typo,

The https string should be  all lower case (vasaservice) and not have "vasaService" with a capital S.

Wrong in

Virtualization for EMC® VNX®

VNX OE for Block 05.32.000.5.201

VNX OE for File 7.1.65.8

Release Notes

300-013-859

REV 02

February 22, 2013

Highlighted
4 Ruthenium

Re: Re: Error creating VASA Provider for File - VNX OE 7.1.65 vSphere 5.1

Firstly, let me mention that I'm glad to see you have it running.

Now I will quickly comment that vasaService (upper-case "S") is documented in more than just the Release Notes.

It is also stated as such in the KB article above:

emc297057: "Login to the VASA Provider on the VNX Control Station fails with "A problem was encountered while registering the provider"



The KB article above is also the same steps I followed several times for other clients.

Also, another EMC employee had blogged about it and used the same upper-case:


http://www.thulinaround.com/tag/vasa/



Therefore, I think there is more to it for your environment than the case of the "S".  Regardless, you have it running now so that is good news.

Highlighted
2 Bronze

Re: Re: Error creating VASA Provider for File - VNX OE 7.1.65 vSphere 5.1

I don't have the RFC in front of me, but I'm pretty sure that the URL specification dictates case-insensitive.

Something to take back to product management it would appear.

0 Kudos
Highlighted
Not applicable

Re: Error creating VASA Provider for File - VNX OE 7.1.65 vSphere 5.1

Hello Chris,

I think your problem is explained in this EMC KB:

https://support.emc.com/kb/190140


since you have the symptoms:


  • 08-Jul-2013 09:08:17.670 -82766736-E- OperationHandler: CIMOM: All providers that service the class EMC_VASA_ServiceLeaf could not be loaded by the CIMOM.


  • 08-Jul-2013 09:08:17.672 -82766736-I- VASAProtocolAdapter: VASASOAPRequestBase::streamFault: objList is NULL.


  • 08-Jul-2013 09:08:17.673 -82766736-E- VASAProtocolAdapter: InvokeMethodOperation::writeResponse streamFault with errorCode: 1

Regards.

0 Kudos