Start a Conversation

Unsolved

This post is more than 5 years old

4142

February 8th, 2016 11:00

powermt returns paths which map to multiple LUNs

Hello

We are running powermt command which displays the paths

e.g

Pseudo name=emcpoweraw

VPLEX ID=FNM00133700251

Logical device ID=6000144000000010F07C657BBC13D312

state=alive; policy=ADaptive; queued-IOs=0

==============================================================================

--------------- Host --------------- - Stor - -- I/O Path -- -- Stats ---

### HW Path I/O Paths Interf. Mode State Q-IOs Errors

==============================================================================

  4 qla2xxx sdla 04 active alive 0 1

  4 qla2xxx sdjx 04 active alive 0 1

  4 qla2xxx sdiu 04 active alive 0 1

  3 qla2xxx sdw 0D active alive 0 1

  3 qla2xxx sdbh 09 active alive 0 1

  4 qla2xxx sdci 04 active alive 0 2

  3 qla2xxx sddm 01 active alive 0 1

  4 qla2xxx sdep 0C active alive 0 2

  3 qla2xxx sdfs 05 active alive 0 1

  4 qla2xxx sdgo 00 active alive 0 2

  4 qla2xxx sdhr 08 active alive 0 2

If we trace back the LUNs for sdla, sdjx etc, we expect all the paths mapping to same LUN.

However we are getting multiple LUNs.

e.g

lrwxrwxrwx 1 root root 0 Jun 26 00:07

/sys/class/scsi_host/host4/device/rport-4:0-0/target4:0:0/fc_transport:target4:0:0/device/4:0:0:49173/block:sdla

-> ../../../../../../../../block/sdla

Similarly for others....

lrwxrwxrwx 1 root root 0 Jun 26 00:07

/sys/class/scsi_host/host4/device/rport-4:0-0/target4:0:0/fc_transport:target4:0:0/device/4:0:0:32789/block:sdjx

-> ../../../../../../../../block/sdjx

lrwxrwxrwx 1 root root 0 Jun 26 00:07

/sys/class/scsi_host/host4/device/rport-4:0-0/target4:0:0/fc_transport:target4:0:0/device/4:0:0:16404/block:sdiu

-> ../../../../../../../../block/sdiu

lrwxrwxrwx 1 root root 0 Feb 20 2015

/sys/class/scsi_host/host3/device/rport-3:0-0/target3:0:0/fc_transport:target3:0:0/device/3:0:0:22/block:sdw

-> ../../../../../../../../block/sdw

Why multiple paths pointing to different lun #  ? Is this possible and what does it indicate.

33 Posts

February 9th, 2016 06:00

This could indicate mismatched paths.

can you please run in the cli powermt check reconfig and see if issue persists, or if have powermt.custom file present please rename and reboot host and see if still reports as I'm also seeing a disordinate number of paths, 11 to be precise.

does the Powerpath GUI label the paths as mismatched at this time?

46 Posts

February 9th, 2016 09:00

Is there any command to check if the paths are mismatched? When you say disordinate number of paths, as I understand it needs to be even number, is that correct?

33 Posts

February 9th, 2016 12:00

looks to be accurate output from powerpath

looks to be managing only 1 lun

1 logical device id and 1 pseudo device name given

examples below from other hosts

Pseudo name=emcpowera

Symmetrix ID=000xxxxxxxxx

Logical device ID=01C2

state=alive; policy=SymmOpt; queued-IOs=0

==============================================================================

--------------- Host --------------- - Stor - -- I/O Path -- -- Stats ---

### HW Path I/O Paths Interf. Mode State Q-IOs Errors

==============================================================================

4 qla2xxx sdde FA 7gB active alive 0 0

4 qla2xxx sdbw FA 9gB active alive 0 0

3 qla2xxx sdao FA 9gB active alive 0 0

3 qla2xxx sdg FA 7gB active alive 0 0

and

powermt display dev=all

Pseudo name=emcpowere

CLARiiON ID=CK20XXXXXXXX [Host-a]

Logical device ID=6006016092861400D4AABXXXXXXX [LUN_44]

state=alive; policy=CLAROpt; priority=0; queued-IOs=0

Owner: default=SP A, current=SP A       Array failover mode: 1

=============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

###  HW Path                I/O Paths    Interf.   Mode    State  Q-IOs Errors =============================================================================

   2 lpfc                      sdg      SP B3     active  alive      0      0

   3 lpfc                      sdm      SP A3     active  alive      0      0

46 Posts

February 9th, 2016 13:00

Thanks for getting back. I did not understand when you said by

" looks to be accurate output from powerpath

looks to be managing only 1 lun

1 logical device id and 1 pseudo device name given"

46 Posts

February 10th, 2016 12:00

So the situation that for one pseudodevice name, all the paths that we see map to different LUNs in the native path, is that correct.

/sys/class/scsi_host/host4/device/rport-4:0-0/target4:0:0/fc_transport:target4:0:0/device/4:0:0:49173/block:sdla

-> ../../../../../../../../block/sdla

/sys/class/scsi_host/host4/device/rport-4:0-0/target4:0:0/fc_transport:target4:0:0/device/4:0:0:32789/block:sdjx

-> ../../../../../../../../block/sdjx

/sys/class/scsi_host/host4/device/rport-4:0-0/target4:0:0/fc_transport:target4:0:0/device/4:0:0:16404/block:sdiu

-> ../../../../../../../../block/sdiu

/sys/class/scsi_host/host3/device/rport-3:0-0/target3:0:0/fc_transport:target3:0:0/device/3:0:0:22/block:sdw

-> ../../../../../../../../block/sdw

So LUNs are 49173, 32789, 16404, 22 but all of these devices belong to Pseudo name=emcpoweraw. Is this possible?

February 10th, 2016 12:00

Hello Ran_aarti

The PP output is showing us the pseudodevice name and the lun information

We will still see the sys/class/scsi_host/host3/device/rport-3:0-0/target3:0:0/fc_transport:target3:0:0/device/3:0:0:22/block:sdw

-> ../../../../../../../../block/sdw for each of the native paths.

Unless Dustin and I are misunderstanding the situation everything looks to be correct.

No Events found!

Top