MSA 2062 secondary controller not connected

[lex4hex]

Dear Community,

I'm quite new on MSA installation and I have the following issue:

I have 2 Host (vsphere) HPE DL 380Gen 9 with H241 HBA 

2 Mini SAS cables each host connected in this way:

Host 1 Sas 1 > MSA Crt A DP1

Host 1 Sas 2 > MSA Crt B DP1

Host 2 Sas 1 > MSA Crt A DP3

Host 2 Sas 2 > MSA Crt B DP3

My problem is that Controller B has no link. Only Controllr A is apparently connected and on the MSA management page cable connected to Crt A show initiator discovered and cable on Crt B show not discovered,

On this way resterting Crt A I no failover reaction loosing the connection to the datastores.

Any help would be really appreciated

Thanks

[SUBHAJIT KHANBARMAN_1 · Accepted solution]

@lex4hex 

As this is new setup so you can shutdown the system and keep Controller A down or remove it. Then try using SAS cables which you have used for Controller A, use them for Controller B connectivity and see if this is cable issue.

Next swap controller position and then verify if this is Controller issue.

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

**********************************************************************

[Cali]

Should work.
In addition to Subhajit, cross-change the SAS Cables and Ports.
Sometimes the SAS did not fully Plug-In.

Connect with SSH (Putty) and use these commands to check for MSA problems:

show system
show controllers
show host-parameter
show ports detail

Post Output and we can check.

Armin

[lex4hex]

Hello

Thanks fro your answer, here the command line results:

HPE MSA Storage MSA 2060 SAS
System Name: OS-MSA-2062
System Location: Uninitialized Location
Version: IN100P003
# show system
System Information
------------------
System Name: OS-MSA-2062
System Contact: Uninitialized Contact
System Location: Uninitialized Location
System Information: Uninitialized Info
Midplane Serial Number: Confidential Information
Vendor Name: HPE
Product ID: MSA 2060 SAS
Product Brand: MSA Storage
Enclosure Count: 1
Health: OK
Health Reason:
Other MC Status: Operativo
PFU Status: Inattivo
Supported Locales: English (English), Spanish (español), French (français), German (Deutsch), Italian (italiano), Japanese (日本語), Korean (한국어), Dutch (Nederlands), Chinese-Simplified (简体中文), Chinese-Traditional (繁體中文)

Success: Comando completato. (2021-04-08 07:37:12)
# show controllers
Controller
----------
Controller ID: A
Serial Number: Confidential Information
Hardware Version: 5.0
CPLD Version: 2.5
MAC Address: 00:C0:FF:53:0B:C5
WWNN: 500C0FF52CA93000
IP Address: 192.168.37.30
IP Subnet Mask: 255.255.255.0
IP Gateway: 192.168.37.254
IP6 Link Local: fe80::2c0:ffff:fe53:bc5
IP6 Link Local GW: ::
Autoconfig: Attivato
DHCPv6: ::
SLAAC IP Address: ::
IP6 Auto Gateway: ::
Disks: 6
Virtual Pools: 1
Disk Groups: 1
System Cache Memory (MB): 12288
Host Ports: 4
Disk Channels: 2
Disk Bus Type: SAS
Status: Operativo
Failed Over to This Controller: No
Fail Over Reason: Non applicabile
Multi-core: Attivato
Health: OK
Health Reason:
Health Recommendation:
Position: In alto
Phy Isolation: Attivato
Controller Redundancy Mode: ULP attivo-attivo
Controller Redundancy Status: Ridondante

Controller
----------
Controller ID: B
Serial Number: Confidential Information
Hardware Version: 5.0
CPLD Version: 2.5
MAC Address: 00:C0:FF:53:0B:1A
WWNN: 500C0FF52CA93000
IP Address: 192.168.37.31
IP Subnet Mask: 255.255.255.0
IP Gateway: 192.168.37.254
IP6 Link Local: fe80::2c0:ffff:fe53:b1a
IP6 Link Local GW: ::
Autoconfig: Attivato
DHCPv6: ::
SLAAC IP Address: ::
IP6 Auto Gateway: ::
Disks: 6
Virtual Pools: 1
Disk Groups: 1
System Cache Memory (MB): 12288
Host Ports: 4
Disk Channels: 2
Disk Bus Type: SAS
Status: Operativo
Failed Over to This Controller: No
Fail Over Reason: Non applicabile
Multi-core: Attivato
Health: OK
Health Reason:
Health Recommendation:
Position: In basso
Phy Isolation: Attivato
Controller Redundancy Mode: ULP attivo-attivo
Controller Redundancy Status: Ridondante

Success: Comando completato. (2021-04-08 07:37:21)
# how host-parameter
Error: Il comando non è stato riconosciuto. (2021-04-08 07:37:29)
# show host-parameter
Error: Il comando non è stato riconosciuto. (2021-04-08 07:37:37)
# show ports detail
Ports Media Target ID Status Speed(A) Health Reason Action
---------------------------------------------------------------------------------
A1 SAS 500c0ff52ca93000 Attivo 12Gb OK

Topo(C) Lanes Expected Active Lanes Disabled Lanes
-----------------------------------------------------
Diretto 4 4 0

A2 SAS 500c0ff52ca93100 Disconnesso Auto OK

Topo(C) Lanes Expected Active Lanes Disabled Lanes
-----------------------------------------------------
Diretto 4 0 0

A3 SAS 500c0ff52ca93200 Attivo 12Gb OK

Topo(C) Lanes Expected Active Lanes Disabled Lanes
-----------------------------------------------------
Diretto 4 4 0

A4 SAS 500c0ff52ca93300 Disconnesso Auto OK

Topo(C) Lanes Expected Active Lanes Disabled Lanes
-----------------------------------------------------
Diretto 4 0 0

---------------------------------------------------------------------------------
Ports Media Target ID Status Speed(A) Health Reason Action
---------------------------------------------------------------------------------
B1 SAS 500c0ff52ca93400 Disconnesso Auto OK

Topo(C) Lanes Expected Active Lanes Disabled Lanes
-----------------------------------------------------
Diretto 4 0 0

B2 SAS 500c0ff52ca93500 Disconnesso Auto OK

Topo(C) Lanes Expected Active Lanes Disabled Lanes
-----------------------------------------------------
Diretto 4 0 0

B3 SAS 500c0ff52ca93600 Disconnesso Auto OK

Topo(C) Lanes Expected Active Lanes Disabled Lanes
-----------------------------------------------------
Diretto 4 0 0

B4 SAS 500c0ff52ca93700 Disconnesso Auto OK

Topo(C) Lanes Expected Active Lanes Disabled Lanes
-----------------------------------------------------
Diretto 4 0 0

I spend some time to understand the issues, cannot be a simple worng setup in our vshpere infrstructure? I mean when I checked the storage device in vmware I noticed the the polyci applied is VMW_SATP_LOCAL instead VMW_SATP_ALUA

I'll make some trial on that

Thanks

[lex4hex]

Hello,

I found the issue on cabling not correctly connected. 

Thanks

[SUBHAJIT KHANBARMAN_1]

@lex4hex 

Do you have any outstanding query on this topic?

If you have no further query and you are satisfied with the answer then kindly mark the forum as resolved so that everyone who are following this forum will get the update.

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

***************************************************************************

[2Exceed]

Just FYI, when plugging in SAS connectors, they should feel like they snap in a little.

You can check them by pulling lightly on them.. if they are snapped in correctly they will not pull out.

If you plugged them in upside down they will seem to go in all the way but they will pull out easily.

Good luck, I had review a teammates setup of the MSA and this was the first thing I found.