Login or Register to Ask a Question and Join Our Community


Solaris

MPxIO Multipathing Problem

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris MPxIO Multipathing Problem
# 1  
Old 02-27-2013
MPxIO Multipathing Problem
Hi,

I believe this is an OS multipathing issue - Solaris 10

We have x2 Dual port 8GB Qlogic HBA's installed in our SOlaris 10 host.

HBA0 (IOU0) Port WWN's - 09f4 (pci@3,700000/SUNW,qlc@0)
09f5 (pci@3,700000/SUNW,qlc@0,1)

HBA1 (IOU1) Port WWN's - 09fc (pci@13,700000/SUNW,qlc@0)
09fd (pci@13,700000/SUNW,qlc@0,1)

HBA0 goes to FABRIC A (Fibre channel switch ports 60 and 12)
HBA1 goes to FABRIC B (Fibre channel switch ports 60 and 12)

The zoning on both fabrics has been checked and is correct. The zoning configuration allows:

HBA0 to see EMC array ports a0 - 50:06:01:60:3b:20:f3:83
a2 - 62:3b
b1 - 69:3b
b3 - 6b:3b

HBA1 to see EMC array ports a1 - 50:06:01:61:3b:20:f3:83
a3 - 63:3b
b0 - 68:3b
b2 - 6a:3b


MPxIO was enabled using stmsboot -e when the server was originally built. ALUA configured on the EMC SAN.

The problem that I have is that only x4 paths from HBA0 (IOU0) are detected and have paths enabled to the SAN disks See output below, I would expect to also see the other paths from HBA1(IOU1) for initiator port name and its target ports (61:3b, 63:3b, 68:3b, 6a:3b) The target port groups for failover are mapped from the same HBA

Where is the other HBA and why is is not detected through the mpath
daemon ?

Code:
 
# mpathadm show lu /dev/rdsk/c6t600601606519250060CCBED4F6B1E011d0s2
Logical Unit:  /dev/rdsk/c6t600601606519250060CCBED4F6B1E011d0s2
        mpath-support:  libmpscsi_vhci.so
        Vendor:  DGC
        Product:  RAID 5
        Revision:  0430
        Name Type:  unknown type
        Name:  600601606519250060ccbed4f6b1e011
        Asymmetric:  yes
        Current Load Balance:  round-robin
        Logical Unit Group ID:  NA
        Auto Failback:  on
        Auto Probing:  NA
        Paths:
                Initiator Port Name:  21000024ff3209f4
                Target Port Name:  500601603b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff3209f4
                Target Port Name:  500601623b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff3209f4
                Target Port Name:  5006016b3b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff3209f4
                Target Port Name:  500601693b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
        Target Port Groups:
                ID:  1
                Explicit Failover:  yes
                Access State:  active not optimized
                Target Ports:
                        Name:  500601603b202f83
                        Relative ID:  1
                        Name:  500601623b202f83
                        Relative ID:  3
                ID:  2
                Explicit Failover:  yes
                Access State:  active optimized
                Target Ports:
                        Name:  5006016b3b202f83
                        Relative ID:  10
                        Name:  500601693b202f83
                        Relative ID:  8


Some additional information.


Code:
 
# mpathadm list lu | grep -i "Operational Path Count:"
Operational Path Count: 4 <--- for every SAN disk
 
HBA0
----
# fcinfo remote-port -sl -p 21000024ff3209f4 | more  
Remote Port WWN: 500601603b202f83
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 50060160bb202f83
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 3
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250060CCBED4F6B1E011d0s2
        LUN: 1
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250061CCBED4F6B1E011d0s2
        LUN: 2
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250062CCBED4F6B1E011d0s2
        LUN: 3
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925002464C1DF3446E111d0s2
        LUN: 4
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250036A2EE174346E111d0s2
        LUN: 5
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250088A10035B84BE111d0s2
        LUN: 6
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500AA8A0F382195DF11d0s2
        LUN: 7
          Vendor: DGC
          Product: RAID 5
        OS Device Name: /dev/rdsk/c6t6006016065192500842F1A702395DF11d0s2
        LUN: 8
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500724AB0ED5C79E111d0s2
        LUN: 9
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925000CB72E0E5D79E111d0s2
        LUN: 10
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250018D58D2C626FDF11d0s2
        LUN: 11
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500C8C883375FA0DF11d0s2
        LUN: 12
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925005A1ADB9D5EA0DF11d0s2
Remote Port WWN: 500601623b202f83
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 50060160bb202f83
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 3
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250060CCBED4F6B1E011d0s2
        LUN: 1
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250061CCBED4F6B1E011d0s2
        LUN: 2
          Vendor: DGC
        Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250062CCBED4F6B1E011d0s2
        LUN: 3
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925002464C1DF3446E111d0s2
        LUN: 4
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250036A2EE174346E111d0s2
        LUN: 5
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250088A10035B84BE111d0s2
        LUN: 6
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500AA8A0F382195DF11d0s2
        LUN: 7
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500842F1A702395DF11d0s2
        LUN: 8
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500724AB0ED5C79E111d0s2
        LUN: 9
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925000CB72E0E5D79E111d0s2
        LUN: 10
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250018D58D2C626FDF11d0s2
        LUN: 11
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500C8C883375FA0DF11d0s2
        LUN: 12
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925005A1ADB9D5EA0DF11d0s2
Remote Port WWN: 500601693b202f83
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 50060160bb202f83
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250060CCBED4F6B1E011d0s2
        LUN: 1
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250061CCBED4F6B1E011d0s2
        LUN: 2
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250062CCBED4F6B1E011d0s2
        LUN: 3
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925002464C1DF3446E111d0s2
        LUN: 4
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250036A2EE174346E111d0s2
        LUN: 5
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250088A10035B84BE111d0s2
        LUN: 6
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500AA8A0F382195DF11d0s2
        LUN: 7
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500842F1A702395DF11d0s2
        LUN: 8
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500724AB0ED5C79E111d0s2
        LUN: 9
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925000CB72E0E5D79E111d0s2
        LUN: 10
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250018D58D2C626FDF11d0s2
        LUN: 11
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500C8C883375FA0DF11d0s2
        LUN: 12
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925005A1ADB9D5EA0DF11d0s2
Remote Port WWN: 5006016b3b202f83
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 50060160bb202f83
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 6
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 0
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250060CCBED4F6B1E011d0s2
        LUN: 1
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250061CCBED4F6B1E011d0s2
        LUN: 2
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250062CCBED4F6B1E011d0s2
        LUN: 3
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925002464C1DF3446E111d0s2
        LUN: 4
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250036A2EE174346E111d0s2
        LUN: 5
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250088A10035B84BE111d0s2
        LUN: 6
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500AA8A0F382195DF11d0s2
        LUN: 7
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500842F1A702395DF11d0s2
        LUN: 8
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500724AB0ED5C79E111d0s2
        LUN: 9
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925000CB72E0E5D79E111d0s2
        LUN: 10
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t600601606519250018D58D2C626FDF11d0s2
        LUN: 11
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t6006016065192500C8C883375FA0DF11d0s2
        LUN: 12
          Vendor: DGC
          Product: RAID 5
          OS Device Name: /dev/rdsk/c6t60060160651925005A1ADB9D5EA0DF11d0s2

HBA1 - unable to detect SAN disks but can see SAN ports 61:3b, 63:3b, 68:3b, 6a:3b

root@oradb1 # fcinfo remote-port -sl -p 21000024ff3209fc
Remote Port WWN: 500601613b202f83
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 50060160bb202f83
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 3
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: LUNZ
          OS Device Name: /dev/rdsk/c3t500601613B202F83d0s2
Remote Port WWN: 500601633b202f83
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 50060160bb202f83
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 1
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: LUNZ
          OS Device Name: /dev/rdsk/c3t500601633B202F83d0s2
Remote Port WWN: 500601683b202f83
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 50060160bb202f83
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 1
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: LUNZ
          OS Device Name: /dev/rdsk/c3t500601683B202F83d0s2
Remote Port WWN: 5006016a3b202f83
        Active FC4 Types: SCSI
        SCSI Target: yes
        Node WWN: 50060160bb202f83
        Link Error Statistics:
                Link Failure Count: 0
                Loss of Sync Count: 0
                Loss of Signal Count: 0
                Primitive Seq Protocol Error Count: 0
                Invalid Tx Word Count: 2
                Invalid CRC Count: 0
        LUN: 0
          Vendor: DGC
          Product: LUNZ
          OS Device Name: /dev/rdsk/c3t5006016A3B202F83d0s2


Just for comparison below output is from another Solaris server only this is running Solaris 11. Zoning configuration is the same as above albeit the HBA's are single port. Both HBA's and all paths to SAN detected.

Code:
 
# mpathadm list lu | grep -i "Operational Path Count:"
Operational Path Count: 8
 
 
# mpathadm show lu /dev/rdsk/c0t60060160651925008AAA53E34C22E211d0s2
Logical Unit:  /dev/rdsk/c0t60060160651925008AAA53E34C22E211d0s2
        mpath-support:  libmpscsi_vhci.so
        Vendor:  DGC
        Product:  VRAID
        Revision:  0430
        Name Type:  unknown type
        Name:  60060160651925008aaa53e34c22e211
        Asymmetric:  yes
        Current Load Balance:  round-robin
        Logical Unit Group ID:  NA
        Auto Failback:  on
        Auto Probing:  NA
        Paths:
                Initiator Port Name:  21000024ff27c1d6
                Target Port Name:  5006016b3b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff27c1d6
                Target Port Name:  500601693b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff277a62
                Target Port Name:  500601683b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff277a62
                Target Port Name:  5006016a3b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff27c1d6
                Target Port Name:  500601603b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff27c1d6
                Target Port Name:  500601623b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff277a62
                Target Port Name:  500601613b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
                Initiator Port Name:  21000024ff277a62
                Target Port Name:  500601633b202f83
                Override Path:  NA
                Path State:  OK
                Disabled:  no
        Target Port Groups:
                ID:  2
                Explicit Failover:  yes
                Access State:  active not optimized
                Target Ports:
                        Name:  5006016b3b202f83
                        Relative ID:  10
                        Name:  500601693b202f83
                        Relative ID:  8
                        Name:  500601683b202f83
                        Relative ID:  7
                        Name:  5006016a3b202f83
                        Relative ID:  9
                ID:  1
                Explicit Failover:  yes
                Access State:  active optimized
                Target Ports:
                        Name:  500601603b202f83
                        Relative ID:  1
                        Name:  500601623b202f83
                        Relative ID:  3
                        Name:  500601613b202f83
                        Relative ID:  2
                        Name:  500601633b202f83
                        Relative ID:  4

Has anyone come across a similar issue or advise.

Thanks in advance
# 2  
Old 03-01-2013
I recall a recent chain about HBAs and MPIO that finally went into the direction of leveling the network connections they were on, as MPIO secifically did not do HBAs, at least for their version. All good questions come around regularly. Did you google the site?
# 3  
Old 03-10-2013
Turns out that the second HBA for some unknown reason had lost connectivity to the SAN and was not reporting on the usual connectivity status on the array. HBA had to be re-registered to pick up alternate paths.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Curious MPxIO problem

Hello folks, I have a newly installed Solaris 10 system running on a T6320 blade. I have set up LDM with the intent to move an ldom from another blade to this one. So far, so good. I had the SAN folks make the LUNs belonging to the ldom visible to my new blade and I can see them, all 4 paths.... (4 Replies)
Discussion started by: Ranck
4 Replies

2. Solaris

Multipathing - problem

Hello, I turned on the server multipathing: # uname -a SunOS caiman 5.10 Generic_141444-09 sun4v sparc SUNW,T5140 stmsboot -D fp -e And after a reboot the server, multipathing is not enable: # stmsboot -L stmsboot: MPxIO is not enabled stmsboot: MPxIO disabled # ls /dev/dsk... (4 Replies)
Discussion started by: bieszczaders
4 Replies

3. Solaris

MPXIO

Hi Kudo, I wanna to know that how can I do mpxio device name to os native name mapping without using stmsboot -L I tried everything still not able to got the solution till I able to get these o/p here is native disk info as well physical wat is the logical OS name of the disk ... (1 Reply)
Discussion started by: tarunn.dubeyy
1 Replies

4. UNIX for Advanced & Expert Users

mpxio in Solaris10 with NetApp FAS3140 problem

we have a v440 SUN machine with a NetApp FAS3140 SAN storage, the v440 got 2 HBA qlogic cards both connected to the switch side in NetApp 3140, zoning in netapp configured proberly and luns are adversitesed to the SUN machine, the problem i am facing is that when i try to configure the mpxio i am... (7 Replies)
Discussion started by: q8devilish
7 Replies

5. Filesystems, Disks and Memory

MPxIO question

Greetings Forumers!! I was given a T2000 with one, dual port, HBA card. The card had one fiber connection to the SAN and the former admin enabled MPxIO. Yesterday, I learned that the other port was connected to the same SAN. This system is in another city so I don't have physical access to... (1 Reply)
Discussion started by: bluescreen
1 Replies

6. Solaris

Veritas Multipathing problem.

Hi, Basically the original configuration on my Solaris 9 server was two LUNs configured as Veritas file systems that were connected to a NetApp filer (filer1). These two LUNs are still configured on the server - but are not being used. They are there as a backup just in case the new... (0 Replies)
Discussion started by: sparcman
0 Replies

7. Filesystems, Disks and Memory

VxVM and MPxIO

:confused: Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO. If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies

8. Solaris

Mpxio

Hi, I have a quick question. How can I see MPXIO statistics (like errors, how many I/O|throuput per path, ....) on Solaris 10? Does maybe a ready dtrace script exist (I do not have the knowledge to write one myself)? I would be happy if somebody knows some good documentation/links (with... (1 Reply)
Discussion started by: victorinox
1 Replies

9. Solaris

Mpxio

Hi All, I have one question. I found out that my system setting for mpxio-disable=yes. Sun recommend to change it to mpxio-disable=no and run stmsboot -e command. But no one can tell will it affect the system or not and the system is sol-10 and using veritas volume manager and attached... (3 Replies)
Discussion started by: mailbox80
3 Replies

10. Solaris

Strange Multipathing problem

We have loads of Sparc solaris 8 boxes. Each one has 2 physical interfaces and 2 virtuals set up for multipathing (See ifconfig below). Problem is that I cannot ping the qfe0 interface IP from the local machine. I can ping all other local interfaces, but not 10.161.19.5. I can ping it from... (3 Replies)
Discussion started by: tjlst15
3 Replies
Login or Register to Ask a Question