It wasn’t so long ago that I had some login issues when trying to connect to one of the VNX boxes I manage via Unisphere.
A similar issue surfaced this week, this time when attempting to access a VNXe 3150, when I was greeted with the following message;
Tests from multiple hosts and browser versions all turned out the same.
Searches on support.emc.com and google-fu turned up zilch.
As usual, I turned to CLI, or in the case of VNXe UEMCLI.
The general ‘status’ check syntax uses the “/sys/general show” command like this;
uemcli -d arrayhostname -u scope/user -p password /sys/general show
This failed with the following;
Most unusual, but like a good little MacGuyver, I had another option to access over ssh, connecting to another management space.
This needs to be accessed using a service user…..and we’re in the game.
First task is to restart the Management service which uses the svc_restart_service cmdlet adding the “restart MGMT” options. (This is the vnxe equivalent to restarting the CIMOM server on VNX via the https://spaddress/setup.html interface)
svc_restart_service restart MGMT
The message “Found ECOM on spa” is returned if the cmd is sent successfully. Wait 5 or 10 minutes for this to complete.
Check the status again with UEMCLI;
You’ll see a progression in the Health State value as the server come up. At (15) it’s close !
…and again in a few minutes, we’re good to go and browser logins to the Unisphere Interface are working as expected.
My message here is simple. Before you put kit into Production, make sure you have configured and tested alternate access methods that you can rely on when your back is against the wall.
This VNXe is in another country, and is now scheduled to get some TLC by way of OE upgrades 🙂 [long overdue thanks to Change Control]