MSA 2062 warning light - cannot access web management though

[timbo343]

Our MSA 2062 has an orange warning light on the front of it. Non of the drives have failed, the PSUs are up, the SAN is presenting to the hosts as expected and working however i am unable to access the the Web GUI on both controllers yet able to get a ping from both of them.

 

Any advice would we welcomed as to how to gain access to this thing.

 

Would it be a case of powering down all the VMs, powering down the SAN and the 2 Hosts and starting them all back up again?

[CrootUK]

Full power down is one option, we had this and resolved it live by plugging in the micro usb on back of san and puttying into it, you can then run “reboot mc” thats just the web interface, “sc” reboots the storage There is a guide for this if I find it il add it!

 

The web interface dying is a bug in one of the firmware versions, latest one fixes it.

[timbo343]

Full power down is one option, we had this and resolved it live by plugging in the micro usb on back of san and puttying into it, you can then run “reboot mc” thats just the web interface, “sc” reboots the storage There is a guide for this if I find it il add it!

 

The web interface dying is a bug in one of the firmware versions, latest one fixes it.

 

Ah Cheers! I was hoping not to do a full power down. Will grab a Micro USB and SSH on to it.

[timbo343]

So the default login account of the MSA doesn't work and the Admin account that has been setup on the MSA doesn't have access to login to the CLI.

[pete]

Google suggests (though I suspect it'll depend on the firmware)...

 

Username: manage

Password(default): !manage

 

https://support.hpe.com/hpesc/public/docDisplay?docId=a00101086en_us&docLocale=en_US

[CrootUK]

Yea if I recall it was some different login that worked no matter what and couldn’t be changed but could only be used when accessed via the micro usb.

[timbo343]

I tried the default usrname and password via the CLI, didnt work.

 

I ended up live pulling out one of the management cards (the one that isn't in use), the SAN screemed so much until it was plugged back in.

 

I can now get into the GUI / web interface of that card, just need to do the same on the card which is communicating with the hosts, Eek!

[CrootUK]

enable CLI for the user account on the web console you can get on, then ssh on and reboot just the management console of the controller thats down then you wont need to pull the controller or have downtime.

 

id recommend controller firmware asap tho, does require “Low I/O” on the SAN.. id check the notes on disk firmware too if you have any to see if its important… as they require NO I/O to upgrade.

 

don’t forget to turn CLI off after, better safe than sorry.

Edited August 21, 2024 by CrootUK

[timbo343]

Had to pull both controllers out at different times in the end. CLI did not work even though the account had full access to everything.

 

Firmware update done too once the errors had cleared.