IOSCAN Takes too Long to complete

[Regina Mitchell]

When I do ioscan it takes at least 3 to 5 minutes to complete. I reboot and as server comes back up it takes longer than usual for server to isntal special device files. I get the follwoing error message in demsg:

0/3/1/0/4/0: Device at device id 0x42000d is back in Name Server GPN_FT (FCP type)
response, and its 'Port World-Wide Name' remains the same as
original.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices
System will be able to see LUNs behind this port
(might need to run 'ioscan' first).

0/3/1/0/4/0: Device at device id 0x42000d has disappeared from Name Server GPN_FT
(FCP type) response, or its 'Port World-Wide Name' has changed.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices
System won't be able to see LUNs behind this port.

0/3/1/0/4/0: Device at device id 0x42000d is back in Name Server GPN_FT (FCP type)
response, and its 'Port World-Wide Name' remains the same as
original.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices
System will be able to see LUNs behind this port
(might need to run 'ioscan' first).

0/3/1/0/4/0: Device at device id 0x42000d has disappeared from Name Server GPN_FT
(FCP type) response, or its 'Port World-Wide Name' has changed.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices
System won't be able to see LUNs behind this port.


All replies are appreciated. Server is HP rp 3600 running 11.23 IA.

[SKR_1]

Provide the output of

ioscan -fnH 0/3/1/0/4/0

Thanks

SKR

[Tim Nelson]

The symptom is "ioscan runs long" the problem is "you have a bunch of hw/IO issues".

Fix the missing devices and/or the FC naming service.

Supply:
Server HW model
Array HW model
Server OS version

What happened to these missing luns, should they be there ?
Were they removed on purpose ?
Is there a failed HBA, Switch port, or LUN somewhere ?

Need to fix the HW failure and the ioscan symptom will go away.

[TTr]

It is normal for ioscan to take that long when there are fiber devices attached to the server. Now for the 4 messages, it looks like disk at h/w path 0/3/1/0/4/1 comes and goes. Look in the syslog, the same messages should be there as well. Check their time stamp to see when exactly they take place. It could be a momentary one time thing during boot up or it could be a flaky fiber device. What kind of fiber device is at this location?

[Tim Nelson]

Never had a server that took 4-5 minutes for an ioscan unless there was something wrong.

4-5 seconds for ioscan -fnC disk
.04 seconds for ioscan -kfnC disk

has always been typical for me.

[Regina Mitchell]

Thanks for the replies. I opened a case with HP and also have EMC looking at the SAN allocation.

[skt_skt]

you may have a look at this my own thread

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1133750