Query: Cannot Access SAN MSA 2040

[Aitred]

Hi

With my colleague, we have some difficulty to access to our SAN MSA 2040. Ping work but impossible to connect to the web interface... We try with serial cable on both
controllers but without much success: on the first connection is refused and on the second, with the same login it seems to accept but at the time of connection it
displays bus error... We try to restore default parameters with restoredefaults and restoreusers and retry, nothing change. And on last, we try to reset the SAN by
disconnecting the power cables, disconnecting the controllers and wait several times before reboot, but nothing work...

[Prabha_Sengar]

Hi @Aitred,

Good day!

Before proceeding further I would like to know a few things:
What is the current LED status?
Did you try using a new pair of cables?
Is it a new installation or was there any scheduled activity that caused this issue?

Regards,
Prabha Singh

[Aitred]

- All led seems ok, just on the second controller one led is off (indicate ok) else nothing.

- which cabkles you talk ? serial cable ? If you talk about this, yes we try 2 cables.

We try to connect in serial with and without fiber cables plugged but don't work anymore.

- No it isn't new installation, it's an old install that was move.

[support_s]

System recommended content:

1. CUSTOMER BULLETIN: HP MSA 2040 SAN Storage - HTTP and HTTPS service access issue is identified

2. HPE MSA 2040 User Guide

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Aitred]

I've already found this two documentations. Effectively our actual version is GL210R004 and the last version is GL225. But how we can do the upgrade without any access to the SAN ? (not fault to try by another way)

[Prabha_Sengar]

Hi @Aitred,

Thank you for the information.

Looks like the system has been directly upgraded from version GL210R004 to version GL225. That is a large leap for the system to make.
It is recommended to follow the below pattern
GL200 -> GL220 -> GL225
It is recommended to install version GL220 and then go to version GL225, to ensure all the component gets properly upgraded.

Also, please try to clear your browser's cache log on both controllers and determine if the SMU's behavior is the same.

Regards,

Prabha Singh

[Aitred]

Hey @Prabha_Sengar 

We haven't do any upgrade, the version GL210R004 is what we have actualy and we want do the upgrade but we can't access to the SAN, by browser or by CLI so we are blocked...

[Prabha_Sengar]

Hi @Aitred,

Apology, My analysis wasn't in the right direction.

Here is the right document for your version of MSA firmware -  https://www.hpe.com/psnow/doc/c03792054

Please configure the SMU as instructed in the document.

Please ensure that your network and firewall system is not blocking the GUI connection.

If you face any challenges, please let us know at what step you are stuck.

Regards,

Prabha Singh

[Aitred]

Thanks for your answer. I have look the documentation, but the SAN refuse us the connection on SMU, it's even not possible to have the log page, it just refuse us (sorry it's in french).  And by CLI normally it's the default log manage and !manage) but when we enter that, it display us "Bus error".
Like i said in my first post, we already try restoredefaults and restoreusers, don't work, always the same message "Bus error". So i would like to know what causing this issue and the way to solve it.

Regards,

Aitred

[sbhat09]

Hello @Aitred,

In MSA 2040, fans in both the modules receive power through a common bus on the midplane. There are chances that it would have gone faulty. Can you please check that and confirm?

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[Aitred]

Hello @sbhat09 

Thanks for your answer. For now i haven't notice any problem with fans, but i will check more in detail and i'll let you know.

[JonPaul]

@Aitred 

Can you show an image of the serial connection?
What serial cable are you using?  the supported cable is the USB A to USB Mini
You may have to attempt connecting with one controller while the other is not installed.  It sounds like the system is currently not serving data is this correct?

[Shawn_K]

@Aitred 

You mentioned the following:

- We try to restore default parameters with restoredefaults and restoreusers and retry, nothing change

-  All led seems ok, just on the second controller one led is off (indicate ok) else nothing.

This sounds like at one time you had the Web GUI working on both controllers but now it does not. Nor is your CLI/serial access working. From what you are describing it sounds as if the two controllers are not in sync with each other.

Of big concern is your data access. Are the hosts connected to this system still able to access the data? If hosts are still actively connected, be sure to take action on the controllers only during a host downtime so that you don't get out of sync between the array and the hosts. If you have the ability to backup your data do so before removing controllers.

Also, what serial CLI cable are you using? What port on the back of the controller are you trying to access for the CLI connection?

You might want to try the following steps:

1. Disconnet the controller where one LED is off. You want to remove this controller from the enclousre backplane. You can leave it in the enclosure slot to help with air flow but it needs to be fully disconnected so it is not powered on.

2. Wait a few minutes (2-5) and try a serial cable to the other controller. If you can gain access, check the fw version, IP settings, etc. You may also want to check the overall health of your vdisks, drives, enclosures, etc to find why the two controllers are not happy. If you can pull a set of logs do so. You can run the logs through hte MSA Health Check to verify any issues or firmware upgrades you need.

Download your MSA Log File from your MSA array
Upload the MSA Log File into the MSA Health Check website
Review the results by clicking through the tabs and saving the PDF report
Links to array, enclosure, and drive firmware are provided for easy access

I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.

Cheers,
Shawn

[Aitred]

hey @Shawn_K, and @JonPaul

@sbhat09 we dissassembly all part we can, there was some dust but we don't see other visual problem.

One thing i forget to precise, we don't really care about our data because we were going to reset it and firewall can't block us cause we are in same network.

- GUI interface work effectively before we disconnect the SAN. But after moving it and reconnect, it display what i had send and by CLI display bus error (before it was reconnected, it remained off for several days)

- the serial cable is the mini usb to USB type A

We will try the step you advised and i'll keep you posted.

Regards,                                                                                                                                                                                              Aitred

[Aitred]

So @Shawn_K i have try steps, without success... I send you screen and photo (i know fiber not connected, but normally not impact CLI right ?)

[Moderator edit: Erased the confidential info.]

[Shawn_K]

@Aitred 

I apprecaite you letting us know the data is not important. The next steps I am suggesting should only be tried on a system that either has a valid backup or there is no data of value.

You do not need to have the FC cables connected. They are of no importance for regaining user access and I suggest leaving them removed for now.

One of the screenshots you provided shows you attempted to login but the password was incorrect.

Cheers,
Shawn

[Aitred]

I know on one screenshot login is incorrect, but it's the same than the other (user: manage manage and password: !manage)

[Kt_12]

This has happened to me as well recently, tried everything to get back into the SAN but it seems the firmware has been corrupted, oh well thanks HP