SAN storage lun online status

[John Guster]

ioscan -m lun shows Clariion LUNs are in limited health. the man page of ioscan states: limited
node is online but performance is degraded due to some links, paths, and connections being offline. I checked Links, paths, and connections, all of them seem normal. Wondering why it is in limited health. Any suggestions are appreciated.

[Michal Kapalka (mikap) · Accepted solution]

hi,

i think the clariion have active/standby configuration so this could be the reason why.

check this article :

http://konglingsong.itpub.net/post/41586/496801

clariion section : "Config for Clariion-side CX700"


mikap

[John Guster]

is this "limited" in health normal if the LUNs are under EMC powerpath control?

[chris huys_4]

Hi John,

Normally limited health is not "standard".

F.e.

On this 11.31 system connected to a eva5000, I have one of the eva luns in limited health.

ronin # ioscan -P health
Class I H/W Path health
======================================
[..]
disk 161 64000/0xfa00/0x41 online
disk 162 64000/0xfa00/0x42 online
disk 338 64000/0xfa00/0x88 limited

>> CONCLUSION -- disk338 is in limited health, while disk162 is in "online" health

ronin # ioscan -fnN
Class I H/W Path Driver S/W State H/W Type Description
===================================================================================
[..]
disk 162 64000/0xfa00/0x42 esdisk CLAIMED DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/disk/disk162 /dev/rdisk/disk162

disk 338 64000/0xfa00/0x88 esdisk CLAIMED DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/disk/disk338 /dev/rdisk/disk338

>> CONCLUSION -- both disk338 and disk162 are eva5000 luns.

ronin # ioscan -m lun
Class I Lun H/W Path Driver S/W State H/W Type Health Description
=======================================================================
[..]
disk 162 64000/0xfa00/0x42 esdisk CLAIMED DEVICE online COMPAQ HSV111 (C)COMPAQ
0/5/1/0/4/0.0x50001fe1500094fc.0x4002000000000000
0/5/1/0/4/0.0x50001fe1500094f8.0x4002000000000000
0/5/1/0/4/1.0x50001fe1500094fd.0x4002000000000000
0/5/1/0/4/1.0x50001fe1500094f9.0x4002000000000000
/dev/disk/disk162 /dev/rdisk/disk162
disk 338 64000/0xfa00/0x88 esdisk CLAIMED DEVICE limited COMPAQ HSV111 (C)COMPAQ
0/5/1/0/4/0.0x50001fe1500094fc.0x4004000000000000
0/5/1/0/4/1.0x50001fe1500094fd.0x4004000000000000
0/5/1/0/4/0.0x50001fe1500094f8.0x4004000000000000
0/5/1/0/4/1.0x50001fe1500094f9.0x4004000000000000
0/5/1/0/4/0.0x50001fe1500094fc.0x4003000000000000
0/5/1/0/4/0.0x50001fe1500094f8.0x4003000000000000
0/5/1/0/4/1.0x50001fe1500094fd.0x4003000000000000
0/5/1/0/4/1.0x50001fe1500094f9.0x4003000000000000
/dev/disk/disk338 /dev/rdisk/disk338


>> CONCLUSION -- but disk162 has 4 paths, while disk338 has 8 paths

which can also be seen from
ronin # ioscan -m dsf
Persistent DSF Legacy DSF(s)
========================================
[..]
/dev/rdisk/disk338 /dev/rdsk/c50t0d4
/dev/rdsk/c54t0d4
/dev/rdsk/c52t0d4
/dev/rdsk/c56t0d4
/dev/rdsk/c50t0d3
/dev/rdsk/c52t0d3
/dev/rdsk/c54t0d3
/dev/rdsk/c56t0d3
[..]
/dev/rdisk/disk162 /dev/rdsk/c50t0d2
/dev/rdsk/c52t0d2
/dev/rdsk/c54t0d2
/dev/rdsk/c56t0d2



And offcourse the eva5000 has only 4 paths, disk162 is clearly "binded" to eva5000 lun "2", while disk338 seems to have been "binded" with both lun "3" and lun "4", what offcourse is impossible .. so which lun is disk338 really "binded" to..


ronin # ioscan -fn
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================================

[..]
disk 339 0/5/1/0/4/0.1.20.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/dsk/c52t0d3 /dev/rdsk/c52t0d3
disk 345 0/5/1/0/4/0.1.20.0.0.0.4 sdisk NO_HW DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/dsk/c52t0d4 /dev/rdsk/c52t0d4

[..]
disk 337 0/5/1/0/4/0.74.46.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/dsk/c50t0d3 /dev/rdsk/c50t0d3
disk 342 0/5/1/0/4/0.74.46.0.0.0.4 sdisk NO_HW DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/dsk/c50t0d4 /dev/rdsk/c50t0d4

[..]
disk 341 0/5/1/0/4/1.34.19.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/dsk/c56t0d3 /dev/rdsk/c56t0d3
disk 346 0/5/1/0/4/1.34.19.0.0.0.4 sdisk NO_HW DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/dsk/c56t0d4 /dev/rdsk/c56t0d4
[..]
disk 340 0/5/1/0/4/1.42.46.0.0.0.3 sdisk CLAIMED DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/dsk/c54t0d3 /dev/rdsk/c54t0d3
disk 343 0/5/1/0/4/1.42.46.0.0.0.4 sdisk NO_HW DEVICE COMPAQ HSV111 (C)COMPAQ
/dev/dsk/c54t0d4 /dev/rdsk/c54t0d4


>> CONCLUSION -- disk338 is binded to "lun 3" , as all "lun 4" device files, give a NO_HW ioscan state


NOTE: Story behind this limited health, was that I was doing testing a eva snapshot procedure, which required using replace_wwid which made the above possible..

Probably if I would reboot now my system, the NO_HW paths would get removed, which means that disk338 would only keep 4 paths, and the health of disk338, would return to online..

Greetz,
Chris

[John Guster]

it is ALUA issue. The LUN has to be configured right at Clariion end.