UNSOLVED

errevi_mancio

updated

12 years ago

E

errevi_mancio

1 Rookie

•

106 Posts

0

4428

September 29th, 2014 02:00

Vasa problem on vnx5200 block

Hello

I'm trying to configure vasa on vSphere 5.5 and vnx 5200block 5.33.000.5.052.

I'm using these parameters

VASA VNX Provider

https://SPa_IP/vasa/services/vasaService

user: global\vCenteradmin

pass: XXX

but I always receive the following error (vsphere client and Web client)

The "Register new storage provider" operation failed for the entity with the following error message.

A problem was encountered while registering the provider

I've collected SP collect and found many entries like these into cimonlog.txt during my tests.

29-Sep-2014 08:00:17.717 -20308-E- NAVSSLSocket::sslAccept: NAVNetException at SSL_accept(): Error accepting connection. Error details: An error occurred as a result of an SSL protocol failure (error=140890B2).

I've tried to open the above vasa url and unisphere return this

Navi Error. Access Denied.

Please check the typed URL.

thanks

Matteo

  • errevi_mancio

    1 Rookie

    •

    106 Posts

    1374

    0

    Posted September 30th, 2014 07:00

    Hi Rainer

    I've just followed the Kb and restarted SP's management server, and the problem persist.

    Matteo

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    1374

    0

    Posted September 30th, 2014 07:00

    See https://community.emc.com/message/819097?et=watches.email.thread#819097

  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    1374

    0

    Posted September 30th, 2014 07:00

    Any firewalls in between?

    Try just entering „A problem was encountered while registering the provider” in the search field on support.emc.com

    That points to a number of KB entries

    If none of them help I would suggest to open a service reqeust

  • errevi_mancio

    1 Rookie

    •

    106 Posts

    1379

    0

    Posted September 30th, 2014 09:00

    I've just followed the KBs but the problem persist..I'm going to open a SR

    190681

    190140

    emc297057


    thanks


    matteo

  • mikko1

    19 Posts

    1379

    0

    Posted October 2nd, 2014 12:00

    Hi,

    Have you checked the following VMware kb article: VMware KB: Registering a VASA provider with vCenter Server fails and reports the error: InvalidCertificate on the expired Vcenter storage provider certificates? If this is an older installation this might be the fault. If this does not fix the issue could you check if you see following "Received fatal alert: unknown_ca" in the vcenter sotrage provider log: C:\ProgramData\VMware\Infrastructure\Profile-Driven Storage\Logs\sps.log . If this is the case this is probably the same problem that I have an open ticket for EMC andVMware. (no resolution yet)

  • errevi_mancio

    1 Rookie

    •

    106 Posts

    906

    0

    Posted October 3rd, 2014 08:00

    Hi all

    I've just solved the problem using administrator@vsphere.local.

    Before that I used another account (vcenter administrator role) and it always goes on error

    thanks to all

    Matteo

  • c_hacker

    2 Posts

    906

    0

    Posted November 16th, 2014 07:00

    Hi all,

    i have the same problem that mikko descibes:

    Received fatal alert: unknown_ca

    Any news if there is a solution yet?

    Thanks,

    Christian

  • bwaggs

    1 Message

    906

    0

    Posted November 26th, 2014 09:00

    VNX_5800 Block-only, registration was failing, I restarted SP A Management server and was successful.

  • acraiger2

    4 Posts

    1379

    0

    Posted January 20th, 2015 10:00

    Mikko, did you ever get a solution?

    I'm having the exact same issue, no resolution.

    Have ticket open with both EMC and VMWare

    VNX 5500 FLARE 5.32.000.5.209

    Vcenter 5.5

    What I've tried so far:

    Regenerated cert on Vcenter server

    Restarted Vcenter server

    Restarted Management service on both SP's

  • intermedia1

    1 Message

    975

    0

    Posted July 1st, 2015 05:00

    Miko, acraiger2,

    Have you managed to solve the issue? The same for me.