MSA2060 Initiator UP/Down all time

[Trin_45]

Hello

We have a MSA 2060 FC connected to 2 ESXI 8.0.1 physical Server.  Both Server are connectet with 2 cable to the MSA:
MSA A1 -> Server 01 Port 01 (with fiber cable)
MSA A3 -> Server 02 Port 02 (with fiber cable)
MSA B1 -> Server 01 Port 02 (with fiber cable)
MSA B3 -> Server 02 Port 01 (with fiber cable)

The Firmware on both controller is IN110P002.

The Problem now is that the server loses connection to the MSA. On the MSA site under "All Initators" we can see that all connections are mapped and discoverd but the discoverd status is changing everytime. It goes from discoverd to not discoverd all the time and i don't get any error. Also on the Server site we don't get any errors. The server says everything is ok but loses the uplink to the MSA.

Othe curios problems with the MSA

- after a short time the MSA is getting very loud, but nothing is shown in the webinterface. No error or to high temp.
- When trying to change for example the Firmware Updatet URL the webinterface crashes and we have to restart it

Is there a problem with the MSA or can someone help us?

Thanks and best Regards
Trin

[venkat_y]

Hello@Trin_45,

Please check the physical connections from both sides of MSA and server (any loose connections or damaged cables and SFPs) and Check the Data center temperature range should be between 10° to 35° C.
Verify that the firmware for the MSA 2060 FC is compatible with the servers that you are using.
Check both the storage logs and the server logs for MSA 2060, and monitor the performance, such as I/O latency, throughput, error rates, etc.

Hope this helps!

Regards,
Venkat

[Trin_45]

Hello @venkat_y 

Thank you for your reply.

The physical connection is checked, everything looks good and cable already changed. The Data center temperature is between 10° and 35°.

i found the following error on my MSA today:

Error Code 235
An event was reported by an EMP. (channel: 0, ID: 127, enclosure: 1, module: A) (Key,Code,Qual,UEC:0x2,0x35,0x2,0x0000) (CDB:1d1000019000)(CmdSpc:0x0, FRU:0x0, SnsKeySpc:0x0)(Not Ready, enclosure services unavailable)

Error Code 235
An event was reported by an EMP. (channel: 1, ID: 127, enclosure: 1, module: B) (Key,Code,Qual,UEC:0x2,0x35,0x2,0x0000) (CDB:1d1000019000)(CmdSpc:0x0, FRU:0x0, SnsKeySpc:0x0)(Not Ready, enclosure services unavailable)

Maybe this helps?

[Sahana_S]

Hi @Trin_45 ,

Error 235 indicates an enclosure management processor (EMP) detected a serious error.

Recommended actions - Replace the indicated controller module or expansion module.

Info - An enclosure management processor (EMP) reported an event.

Hope this helps!

[Trin_45 · Accepted solution]

The problem is solved.
It was a firmware issue on the HBA contorller on the Server.

[Sunitha_Mod]

Hello @Trin_45, 

Perfect! 

We are extremely glad to know the problem has been resolved and we appreciate you for keeping us updated.