Solaris 10 : mpathadm vs luxadm – manage multipathing in solaris 10
Other Learning Articles that you may like to read
Free Courses We Offer
Paid Training Courses we Offer
Solaris Multipathing software MPXIO operate now with new arrays using other protocols like SAS or iscsi, . The old Solaris luxadm command still manage FC arrays, but mpathadm command has been developed to work on all the arrays using FC, SAS, and Iscsi connections.
- mpathadm is included since s10u3 for SPARC and x86 platform with SUNWmpathadm SUNWmpathadmr packages.
- At this time few patch exist, but many CR are open against mpathadm. Hence check for any new released patch if you encounter any wrong result.
- Check all device drivers used by MPXIO are well patched
| look up | luxadm | mpathadm | |
| 1 | help | man | man or mpathadm -? |
| 2 | WWPN of the connected and available arrays | luxadm -e dump_map | mpathadm list initiator-port |
| 3 | physical path of the HBA and its state | luxadm -e port | mpathadm show initiator-port WWPN |
| 4 | List the LUNs | NA | mpathadm list LU |
| 5 | volume multipathing configuration | luxadm display | mpathadm show LU /dev/rdsk/c4t6… |
| 6 | failover path | luxadm failover | mpathadm failover LU /dev/rdsk/c4t6… |
| 7 | list registered multipathing support libraries | NA | mpathadm list mpath-support |
| 8 | array compatibility list | NA | mpathadm show mpath-support libmpscsi_vhci.so |
- mpathadm -?
Usage: mpathadm -?,-V,–help
….
For more information, please see mpathadm(1M) - mpathadm list initiator-port
Initiator Port: 5080020000002999
Initiator Port: 500605b000256120
Initiator Port: 10000000c94c0d72
Initiator Port: 10000000c94c0d71
Initiator Port: iqn.1986-03.com.sun:01:00144f71caae.46aa0c5f,4000002a00ff - mpathadm show initiator-port 10000000c94c0d71
Initiator Port: 10000000c94c0d71
Transport Type: Fibre Channel
OS Device File: devices/pci@1e,600000/pci@0/pci@2/SUNW,emlxs@0,1/fp@0,0 - mpathadm list LU
…
/dev/rdsk/c4t600A0B800034D7E9000002D346E7848Cd0s2
Total Path Count: 2
Operational Path Count: 2
… - mpathadm show LU /dev/rdsk/c4t600A0B800034D7E9000002D346E7848Cd0s2
Logical Unit: /dev/rdsk/c4t600A0B800034D7E9000002D346E7848Cd0s2
mpath-support: libmpscsi_vhci.so
Vendor: SUN
Product: LCSM100_S
Revision: 0670
Name Type: unknown type
Name: 600a0b800034d7e9000002d346e7848c
Asymmetric: yes
Current Load Balance: round-robin
Logical Unit Group ID: NA
Auto Failback: on
Auto Probing: NA
Paths:
Initiator Port Name: 500605b000256120
Target Port Name: 500a0b82f754800c
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 500605b000256120
Target Port Name: 500a0b834d7e900c
Override Path: NA
Path State: OK
Disabled: no
Target Port Groups:
ID: 1
Explicit Failover: yes
Access State: standby
Target Ports:
Name: 500a0b82f754800c
Relative ID: 0
ID: 3
Explicit Failover: yes
Access State: active
Target Ports:
Name: 500a0b834d7e900c
Relative ID: 0 - mpathadm failover LU /dev/rdsk/c4t600A0B800034D7E9000002D346E7848Cd0s2
mpathadm show LU /dev/rdsk/c4t600A0B800034D7E9000002D346E7848Cd0s2
…snip…
Target Port Groups:
ID: 1
Explicit Failover: yes
Access State: active
Target Ports:
Name: 500a0b82f754800c
Relative ID: 0
ID: 3
Explicit Failover: yes
Access State: standby
Target Ports:
Name: 500a0b834d7e900c
Relative ID: 0
…snip… - mpathadm list mpath-support
mpath-support: libmpscsi_vhci.so - mpathadm show mpath-support libmpscsi_vhci.so
mpath-support: libmpscsi_vhci.so
Vendor: Sun Microsystems
Driver Name: scsi_vhci
Default Load Balance: round-robin
Supported Load Balance Types:
round-robin
logical-block
Allows To Activate Target Port Group Access: yes
Allows Path Override: no
Supported Auto Failback Config: 1
Auto Failback: on
Failback Polling Rate (current/max): 0/0
Supported Auto Probing Config: 0
Auto Probing: NA
Probing Polling Rate (current/max): NA/NA
Supported Devices:
Vendor: SUN
Product: T300
Revision:
Supported Load Balance Types:
round-robin
Vendor: SUN
Product: T4
Revision:
Supported Load Balance Types:
round-robin
….snip….
Vendor: SUN Â Â Â Product: LCSM100_S , is a JBOD or SAN ?Â
Logical Unit: /dev/rdsk/c4t600A0B800034D7E9000002D346E7848Cd0s2
mpath-support: libmpscsi_vhci.so
Vendor: SUN
Product: LCSM100_S
Revision: 0670
Hi All,Â
I have also facing the same doubt can some one please clarify us..
How can we judge that this device is SAN or JBOD (Local disk)?
@musthaq and @basha — what path it does show in format output is key here. The path clearly says the devices either by using HBA or iscsi path.
JBOD usually configures using iscsi, whereas SAN using the Fibre connections.
From the about output, the mpath module loaded for mpath is scsi , hence I can guess it is a jbod. Incase if the module loaded is anything like fp based my guess will be SAN disk.
@musthaq – can you get the echo|format output for this disk.
Hi,Â
I can see the controllers internal to the system  `ls -l /dev/cfg/
c0 Â Â c1 Â Â c4 Â Â c5 Â Â c6 Â Â c7 Â Â usb0/
when i echo formatÂ
c8t6001437890DEFF330001555551680000d0
The server has mpxio enabled but i am confuse over the controller 8 is not showing as other controllers in the list.Â
Please advise thanks.
Hi Mushtaq, do you able to print the partition table for the c8 disk. Can you run cfgadm -al and devfsadm -Cv once , to check if there is any difference?
And also refer /etc/path_to_install if the disk had any customized path.