Cannot see the LUN with "ioscan -fnC disk"

[yyghp]

Hi there,

I just installed a new HP-UX server and presented one LUN from EVA5000 to this server, I think the server can detect the LUN because:

# ioscan -fn | grep HSV110
ctl 6 0/2/1/0.7.1.255.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 7 0/2/1/0.7.2.255.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 12 0/2/1/0.11.1.0.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
hsx 2 0/2/1/0.11.1.0.0.0.1 hsx CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 4 0/2/1/0.11.1.255.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 13 0/2/1/0.11.2.0.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
hsx 3 0/2/1/0.11.2.0.0.0.1 hsx CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 5 0/2/1/0.11.2.255.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 10 0/6/1/0.9.1.255.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 11 0/6/1/0.9.2.255.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 15 0/6/1/0.10.1.0.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
hsx 0 0/6/1/0.10.1.0.0.0.1 hsx CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 8 0/6/1/0.10.1.255.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 14 0/6/1/0.10.2.0.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
hsx 1 0/6/1/0.10.2.0.0.0.1 hsx CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
ctl 9 0/6/1/0.10.2.255.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ

But if I use "ioscan -fnC disk", I cannot see that:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0

It should show one LUN like:
disk 3 255/255/3/0.0 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c20t0d0 /dev/rdsk/c20t0d0
( I got this from another server which is working fine. )

Why? Thanks a lot !

[RAC_1]

insf -ev -Cdisk
Then ioscan -fnCdisk

[yyghp]

# insf -ev -Cdisk
insf: Installing special files for sdisk instance 0 address 0/0/2/0.0.0.0
insf: Installing special files for sdisk instance 1 address 0/1/1/0.0.0
insf: Installing special files for sdisk instance 2 address 0/1/1/0.1.0
insf: Installing special files for sdisk instance 3 address 255/255/4/0.0

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0

same... :(

[RAC_1]

ioscan -fnH255/255/3

Does it list the devices?? Did you create it properly?? What array is this?? Does array command show that the LUN is created??

ls -ltr /dev/dsk
Does it show latest dates for the last files??

[yyghp]

Hi RAC,

It doesn't list the device.
I presented the LUN from Command View EAV, and it worked fine 3 hours ago:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 3 255/255/0/0.0 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c16t0d0 /dev/rdsk/c16t0d0

# diskinfo /dev/rdsk/c16t0d0
SCSI describe of /dev/rdsk/c16t0d0:
vendor: COMPAQ
product id: HSV110 (C)COMPAQ
type: direct access
size: 52428800 Kbytes
bytes per sector: 512

But after several reboots, the LUN was gone:

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GMAT3147NC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0

And the device file was created 3 hours ago when it worked fine.
# ls -ltr /dev/dsk
total 0
brw-r----- 1 bin sys 31 0x000000 Mar 28 15:23 c0t0d0
brw-r----- 1 bin sys 31 0x020000 Mar 28 15:23 c2t0d0
brw-r----- 1 bin sys 31 0x021000 Mar 28 15:23 c2t1d0
brw-r----- 1 bin sys 31 0x100000 Mar 30 13:09 c16t0d0

[yyghp]

here's what I just got from the root mail:

X-Generated-Message-From: Secure Path Notification Event Daemon

Active path for LUN 600508B4001010640000B00000AF0000 changed to c12t0d1. (hba:controller) td0:P5849E1AAQF00E
Active path for LUN 600508B4001010640000B00000AF0000 changed to c13t0d1. (hba:controller) td0:P5849E1AAQE04J
Active path for LUN 600508B4001010640000B00000AF0000 changed to c15t0d1. (hba:controller) td1:P5849E1AAQF00E
Active path for LUN 600508B4001010640000B00000AF0000 changed to c14t0d1. (hba:controller) td1:P5849E1AAQE04J
Configuration error. Invalid or missing target/lun wwlid entry for * on array DON'T CARE
Active path for LUN 600508B4001010640000B00000AF0000 changed to c12t0d1. (hba:controller) *:P5849E1AAQF00E
Active path for LUN 600508B4001010640000B00000AF0000 changed to c14t0d1. (hba:controller) *:P5849E1AAQE04J
Active path for LUN 600508B4001010640000B00000AF0000 changed to c13t0d1. (hba:controller) *:P5849E1AAQE04J
Active path for LUN 600508B4001010640000B00000AF0000 changed to c15t0d1. (hba:controller) *:P5849E1AAQF00E

[yyghp]

Here's what I got from syslog.log:

Mar 30 16:10:31 srs136 vmunix: 0/2/1/0.11.2.0.0.0.1 hsx
Mar 30 16:10:31 srs136 vmunix: 0/2/1/0.11.1.0.0.0.1 hsx
Mar 30 16:10:31 srs136 vmunix: 0/6/1/0.10.2.0.0.0.1 hsx
Mar 30 16:10:31 srs136 vmunix: 0/6/1/0.10.1.0.0.0.1 hsx
Mar 30 16:10:32 srs136 vmunix: CPQswsp: Availability for LUN 600508B4001010640000B00000AF0000 chan
ged to Alive

It looks the Secure Path is working...

[yyghp]

# fcmsutil /dev/td0

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x0b0600
N_Port Node World Wide Name = 0x50060b0000256459
N_Port Port World Wide Name = 0x50060b0000256458
Driver state = ONLINE
Hardware Path is = 0/2/1/0
Number of Assisted IOs = 4348
Number of Active Login Sessions = 2
Dino Present on Card = NO
Maximum Frame Size = 2048
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 (AR1204) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Oct 11 2004, 14:45:41

# fcmsutil /dev/td1

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x0a0600
N_Port Node World Wide Name = 0x50060b0000253e3b
N_Port Port World Wide Name = 0x50060b0000253e3a
Driver state = ONLINE
Hardware Path is = 0/6/1/0
Number of Assisted IOs = 4348
Number of Active Login Sessions = 2
Dino Present on Card = NO
Maximum Frame Size = 2048
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 (AR1204) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Oct 11 2004, 14:45:41

[RAC_1]

When you say LUN is gone after several reboots, does it exists now??

The messages from secure path are about path changes. How many of laternate paths you have?? Are all controllers working fine?? For all those PVs being reported, are those PVs still visibal from OS and are laternate paths OK for them??

Anil

[yyghp]

Hi RAC,

The server could see that LUN around 1:00pm, but after several reboots, I couldn't see the LUN by using "ioscan".
There are 4 alternate paths for this LUN, it looks ok.
I haven't created PVs yet.

[Hoang Chi Cong_1]

Did you install all of the patch require?

[Thayanidhi]

Based on the HW path 255/255 you have securepath installed. Check the SAN configuration whether the LUN exists and still assigned to this host. (also verify WWN). Run

#spmgr display

And find out about the links to the disks and it's statuses.

255/255 is virtual HW path created by securepath.

Post the output of spmgr -display

regds
TT

[Peyman Javaheri]

also try "fcmsutil /dev/td1 replace_dsk" for that device if you see lines your older syslogs that compain about loosing these disks (or disks going ofile).

regards,
peyman;

[Nguyen Anh Tien]

IT IS CHANGING DEVICE FILE NAME BECAUSE YOU RE-PRESENT VDISK.
REMEMBER THAT YOUR DEVICE FILE OF PV IS CHANGE AT EACH PRESENT VDISK. FOR EG:
YOU CREATE
VDISK1, VDISK2, VDISK3
BUT YOU PRESENT
VDISK1 THEN VDISK3 AND VDISK2 IS LAST PRESEND. YOU HOST WILL NAMING LIKE
VDISK1--->C1T0D0
VDISK3---->C1T0D1
VDISK2---->C1T0D2
THAT'S ALL
TIENNA

[yyghp]

Found out the problem myself:
Patchset problem.
Have to apply both patchsets for SP 3.0E and patchset from ITRC.
Thanks!