vdisk h/w path is not detected

[S.S.]

Dear All,

I have create 7 vdisks at EVA and also presented the LUNS from the host and detected by ioscan command whereas for my 8th vdisk i have created with 500gb at EVA and presented the LUNS also but it is not detecting by ioscan command. I executed this command frequently and waited for 20min even also that h/w is not detected.

May i know what will be reason?

Thanks!

[Jupinder Bedi]

you can check at the storage end , there must be a problem on the storage end or san switch.

[Prasanth Thomas]

Hi,

please let me know update for the below queries.
please run the ioscan command

#ls -ltr /dev/dsk
#uname -a
please confirm from sorage end that the this lun is properly created and assigned.

Regards,
Prasanth Thomas.

[Prasanth Thomas]

what was the size of other vdisks?.

[S.S.]

Hi Prasanth,

The other vdisks are of size 200gb, 150gb, 60gb like that. I have created these vdisks under FATA disk group.
For all these vdisks i have detected the LUNS whereas only for 500gb disk.

Justnow, i tried to delete this 500gb and created with 200gb and presented the LUNS to the host at EVA level and i checked for these LUNS at O/S level by ioscan even though also the LUNS are not detected.

[Prasanth Thomas]

Hi,
whats the version of OS ?.
is it a production server?.

Regards,
PT

[S.S.]

Hi,

Now, i presented the LUNS to another host [test server] and tried to execute the ioscan command and it has been detected.

[bobsam]

Hi Dear,

Please check at your storage end, that the LUN presented properly to the host or not,

Your remaining 7 LUNS getting means hope there is no problem with your SAN zoning.

In sever before ioscan just execute

#insf -e
#insf -eC disk

then check ioscan, Hope the disk will detect.

thanks,

[Prasanth Thomas]

just want to update you that sometimes you have wait for 5-10 minutes.

After presenting the LUN please run the ioscan command and the verify whether the new lun is showing or not. If not please run the insf -C disk command ,in the o/p you can see the new device file.

Regards,
Prasanth Thomas

[Prasanth Thomas]

#uname -a

[S.S.]

# uname -a
HP-UX B.11.11 U 9000/800 2781561423 unlimited-user license

[Torsten.]

If you see 7 disks but not 8, there is most likely a problem with host mode.

Make sure you present vdisks in HP-UX mode in command view!!!

[S.S.]

HI,

I fount the following in the syslog:

Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc043100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc063100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc083100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc0a3100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc0c3100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc0e3100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc103100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc123100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc163100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc183100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc1a3100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc1c3100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc1e3100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc203100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc223100 failed! Rerouting to alternate path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH DEBUG: PPM Failing path
Feb 19 13:54:45 oradb1 vmunix: AUTOPATH : Path 0xbc243100 failed! Rerouting to alternate path

[AVV]

Hi,

Can you try by assigning one more 300GB LUN to the system and check it sees there. If so, please increase the size by 50Gb and represent. The lun to be there unless there is a LUN size limitation, not sure though.

#insf -eC disk

all the time and check.

[S.S.]

Hi All,

There is a autopath problem in the host level only because for testing again i created another vdisk of size 1gb at EVA and presented vdisk to this host. At this host end i executed ioscan command and it is not detecting. I don't now what is the problem.
Previous this was worked properly, i created device files, vg, lv and filesystem also.

Can anyone help me what will be the reason?

[Torsten.]

Read my post again.

[S.S.]

Hi Torsten,

Thank you!

Can you make me more clear to understand.

Also, again i recreated with 300gb of vdisk and executed ioscan and it is detected with no hardware (NO_HW)

Here is the output:

# ioscan -kfnC disk|grep -i NO_HW
disk 376 1/0/4/1/0/4/0.12.0.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 377 1/0/4/1/0/4/0.12.1.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 378 1/0/4/1/0/4/0.12.8.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 375 1/0/4/1/0/4/0.12.9.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 418 1/0/6/1/0/4/0.11.0.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 415 1/0/6/1/0/4/0.11.1.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 412 1/0/6/1/0/4/0.11.8.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 417 1/0/6/1/0/4/0.11.9.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 358 1/0/12/1/0.11.0.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 356 1/0/12/1/0.11.1.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 355 1/0/12/1/0.11.8.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 354 1/0/12/1/0.11.9.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 395 1/0/14/1/0/4/0.12.0.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 398 1/0/14/1/0/4/0.12.1.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 396 1/0/14/1/0/4/0.12.8.0.0.3.2 sdisk NO_HW DEVICE HP HSV210
disk 394 1/0/14/1/0/4/0.12.9.0.0.3.2 sdisk NO_HW DEVICE HP HSV210

[Torsten.]

Make sure all vdisks are presented in

"Hewlett-Packard HP-UX" mode!

[Prasanth Thomas]

please share o/p of
# ioscan -m dsf


Regards,
PT.

[Prasanth Thomas]

sorry above mentioned command is for v3. please run the below command.

ioscan -fnC disk

it its in NO_HW status just remove the device file by using rmsf command.

Regards,
Prasanth Thomas

[Johnson Punniyalingam]

Hi SS,

As mentioned by >>Torsten<< most likly the issue may from the "Host side" that is server side.

from server :- can you also confirm same..??

#ioscan -fn
#insf -e
#ioscan -fnC disk
# evainfo -> output
# autopath display ->

always take note "please remove " Dead path (ie.) NO_HW I remember I posted in one of your earlier thread.

Last Resort I would reboot the server "if still cannot see disk" i suspect it could be I/O sub system busy. due to multiple "ioscan"

[S.S.]

Hi,

Today i have deleted the older vdisk and re-created with new vdisk. I have checked at host level and it is detecting with CLAIMED status now.

Johnson,
As you said that may be I/O sub system was busy previously. May i know how can we check that? If suppose this issue happens later then we should have to wait like this or any possibility for troubleshooting rightway?

Thank you in advance.