Registering EqualLogic VASA Provider with VSM 4.5

Dell, VASA, VMware

Registering EqualLogic VASA Provider with VSM 4.5

I am in the process of configuring a new VMware cluster using vSphere 6 and a Dell EqualLogic PS4210. So that I can leverage the new virtual volumes from VMware I have installed the the Dell Virtual Storage Manager 4.5. Part of the installation process is to register the VASA provider in vCenter. To do this you log in to the VSM and select 1 for configuration:

VSM_Config_1

Then you select ‘4’ to register the VASA provider:

VSM_Config_2

After entering details for the provider service credentials (newly created by this process) you will get a message saying “Configuration of VASA was successful.” and then “Waiting 90 seconds for VMware vCenter to register with the VASA Provider…”.

At this point I was having troubles getting the provider to register in vCenter. The first time I waited about 15 minutes and still no provider so I cancelled and got an error saying to check ‘setup.sh-****.log’. Checking this log (to get the logs go to the main menu and press ‘3’ for Diagnostics and then ‘1’ for Gather support information and then go to ‘\\*ipaddressofVSM*\database’ to find the zip file of the support logs), I found that it was attempting to register the provider and then creating a tonne of lines saying error.

Excerpt from log setup.sh-****.log:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/local/asmve/webapps/ROOT.war/WEB-INF/lib/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/local/asmve/webapps/vasa1.war/WEB-INF/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
vCenter version: 6.0
VASA URL: https://10.10.2.203
Querying providers:
No providers found.
Registering provider: https://10.10.2.203:8443/vasa-version.xml
error
error
error
error
...

The above log was created after leaving the registration process running for 2 minutes and there were 270 lines with the word error.

I searched long and hard on Google and could not find any information relating to this version of VSM, I guess it is too new. I did find some error about the certificates not being updated after an upgrade, but this was a fresh install.

At the end of the day I kicked off a new registration and left it running over night. When I arrived this morning the VASA provider had registered successfully! I checked the logs again and the setup.sh log for the successful install had 3,873 lines with error, followed by 14 lines of running and then 1 line of success. I couldn’t find any time stamps that tell me how long the process took, but if it created 270 lines of error in 2 minutes, then it may have taken about 28 minutes to create 3,873 error lines.

This is the successful log file:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/local/asmve/webapps/ROOT.war/WEB-INF/lib/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/local/asmve/webapps/vasa1.war/WEB-INF/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
vCenter version: 6.0
VASA URL: https://10.10.2.203
Querying providers:
No providers found.
Registering provider: https://10.10.2.203:8443/vasa-version.xml
error
error
/***snip***/
error
error
running
running
running
running
running
running
running
running
running
running
running
running
running
running
success

The long and the short of it is, just be patient when registering the VASA provider.

Leave a Reply

Your email address will not be published. Required fields are marked *