Inquiry failed on FCP device with device id

[Pradep]

Hi,

server is repeatedly giving this error:

Feb 22 04:03:07 Wending vmunix: 0/2/1/0/4/0: Inquiry failed on FCP device with device id 0xb90a01
Feb 22 04:03:07 Wending vmunix: device id = loop id, for private loop devices
Feb 22 04:03:07 Wending vmunix: device id = nport ID, for fabric/public-loop devices
Feb 22 04:03:07 Wending vmunix:
Feb 22 04:03:07 Wending vmunix: 0/6/1/0/4/0: Inquiry failed on FCP device with device id 0xbc0102
Feb 22 04:03:07 Wending vmunix: 0/6/1/0/4/0: Inquiry failed on FCP device with device id 0xbc0b01
Feb 22 04:03:56 Wending sshd[18254]: Did not receive identification string from 3.77.50.102
Feb 22 04:03:07 Wending vmunix: device id = loop id, for private loop devices
Feb 22 04:06:10 Wending above message repeats 2 times
Feb 22 04:06:10 Wending vmunix: 0/2/1/0/4/0: Inquiry failed on FCP device with device id 0xb90a01
Feb 22 04:03:07 Wending vmunix: device id = nport ID, for fabric/public-loop devices
Feb 22 04:06:10 Wending above message repeats 2 times
Feb 22 04:06:10 Wending vmunix: device id = loop id, for private loop devices
Feb 22 04:03:07 Wending vmunix:
Feb 22 04:06:10 Wending above message repeats 2 times
Feb 22 04:06:10 Wending vmunix: device id = nport ID, for fabric/public-loop devices
Feb 22 04:06:10 Wending vmunix:
Feb 22 04:06:10 Wending vmunix: 0/6/1/0/4/0: Inquiry failed on FCP device with device id 0xbc0102
Feb 22 04:06:10 Wending vmunix: 0/6/1/0/4/0: Inquiry failed on FCP device with device id 0xbc0b01
Feb 22 04:06:10 Wending EMS [21000]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/ql_adapter/0_6_1_0_4_0"
(Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 1376256012 -r /adapters/events/ql_adapter/0_6_1_
0_4_0 -n 1376256044 -a
Feb 22 04:06:10 Wending vmunix: device id = loop id, for private loop devices
Feb 22 04:06:24 Wending above message repeats 2 times
Feb 22 04:06:10 Wending vmunix: device id = nport ID, for fabric/public-loop devices
Feb 22 04:06:24 Wending above message repeats 2 times
Feb 22 04:06:24 Wending sshd[18441]: Accepted keyboard-interactive/pam for gxsftp from 3.77.64.35 port 56934 ssh2
Feb 22 04:06:10 Wending vmunix:
Feb 22 04:06:25 Wending above message repeats 2 times

but, not such things in unclaimed in search below.

$ /opt/fcms/bin/fcdlist | grep -v CLAIMED

/dev/fcd0 0/2/1/0/4/0.152.0.255.0.15.0 fcd_vbus 0x98000f

/dev/fcd0 0/2/1/0/4/0.152.0.255.1.1.0 fcd_vbus 0x980011

/dev/fcd0 0/2/1/0/4/0.152.0.255.1.2.0 fcd_vbus 0x980012

/dev/fcd0 0/2/1/0/4/0.152.0.255.1.11.0 fcd_vbus 0x98001b

/dev/fcd0 0/2/1/0/4/0.185.9.255.0.2.0 fcd_vbus 0xb90902

/dev/fcd0 0/2/1/0/4/0.152.0.15.0 fcd_vbus 0x98000f

/dev/fcd0 0/2/1/0/4/0.152.0.17.0 fcd_vbus 0x980011

/dev/fcd0 0/2/1/0/4/0.152.0.18.0 fcd_vbus 0x980012

/dev/fcd0 0/2/1/0/4/0.152.0.27.0 fcd_vbus 0x98001b

/dev/fcd0 0/2/1/0/4/0.152.0.27.1 fcd_vbus 0x98001b

/dev/fcd0 0/2/1/0/4/0.152.0.27.2 fcd_vbus 0x98001b

/dev/fcd0 0/2/1/0/4/0.152.0.27.4 fcd_vbus 0x98001b

/dev/fcd0 0/2/1/0/4/0.185.9.2.0 fcd_vbus 0xb90902

/dev/fcd2 0/6/1/0/4/0.93.0.255.0.15.0 fcd_vbus 0x5d000f

/dev/fcd2 0/6/1/0/4/0.93.0.255.1.1.0 fcd_vbus 0x5d0011

/dev/fcd2 0/6/1/0/4/0.93.0.255.1.2.0 fcd_vbus 0x5d0012

/dev/fcd2 0/6/1/0/4/0.93.0.255.1.9.0 fcd_vbus 0x5d0019

/dev/fcd2 0/6/1/0/4/0.93.0.15.0 fcd_vbus 0x5d000f

/dev/fcd2 0/6/1/0/4/0.93.0.17.0 fcd_vbus 0x5d0011

/dev/fcd2 0/6/1/0/4/0.93.0.18.0 fcd_vbus 0x5d0012

/dev/fcd2 0/6/1/0/4/0.93.0.25.0 fcd_vbus 0x5d0019

/dev/fcd2 0/6/1/0/4/0.93.0.25.1 fcd_vbus 0x5d0019

/dev/fcd2 0/6/1/0/4/0.93.0.25.2 fcd_vbus 0x5d0019

/dev/fcd2 0/6/1/0/4/0.93.0.25.4 fcd_vbus 0x5d0019
$

What can i do to get rid of this error.

thanks.

[Pradep]

Any replies pls ?

[Pieter 't Hart]

what output gives the in the report suggested
"Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 1376256012 -r /adapters/events/ql_adapter/0_6_1_0_4_0 -n 1376256044 -a"

Are there other hosts accessing these devices?

[Pradep]

Hi ,,,thanks for your reply. here is the output of the commands. Basically i wanted to to know how to find the actually device which is shown above as device id 0xb90a01

how to map a device id to a device.. is it tape or disk ? or FC card ?


# /opt/resmon/bin/resdata -R 1376256012 -r /adapters/events/ql_adapter/0_6_1_
USAGE: resdata -r resource_name -R request_id -a|-m|-u
[-n notify_id] [-h host_name] -M monitor_key

Please specify the -r and -R options, and one of -a,-m,-u.
Optionally, specify the -n options if the notify id is known
Otherwise, to get the restarted resource list, specify -M.

-n Prints specific monitor return data associated
with notify_id
-m Prints monitor return data for specified resource and request id
-u Prints user data for specified resource and request id
-a Prints user & monitor data for specified resource and request id
host_name corresponds to the host where the resource is registered
-M Prints the restarted resource list
# 0_4_0 -n 1376256046 -a
sh: 0_4_0: not found.
# /adapters/events/ql_adapter/0_6_1_
# /opt/resmon/bin/resdata -R 1376256012 -r /adapters/events/ql_adapter/0_6_1_0_4_0 -n 1376256046 -a

CURRENT MONITOR DATA:

Event Time..........: Mon Feb 23 04:06:11 2009
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 54
System..............: Wending

Summary:
Adapter at hardware path 0/6/1/0/4/0 : Inquiry failed on FCP device



Description of Error:


lbolt value: 856135316

Inquiry failed on FCP device with device id 0xbc0102
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices


Probable Cause / Recommended Action:

SCSI command INQUIRY to the device failed, even after retries.

Please check the following:
1. Verify that the fiber optic cable is functional and securely
attached to the Fibre Channel Mass Storage Adapter.
2. Verify that the device which is connected to the adapter port is
functioning correctly.


Additional Event Data:
System IP Address...: 3.77.49.169
Event Id............: 0x49a2670300000000
Monitor Version.....: B.02.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_ql_adapter.clcfg
Client Configuration File Version...: A.04.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x49a2670300000001
Additional System Data:
System Model Number.............: 9000/800/rp4440
OS Version......................: B.11.11
EMS Version.....................: A.04.20
STM Version.....................: A.57.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_ql_adapter.htm#54

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path....: 0/6/1/0/4/0

I/O Log Event Data:

Driver Status Code..................: 0x00000036
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 65 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000001 33079694 00000001 00000001 00BC0102 2F75782F 6B65726E 2F6B6973
752F4643 442F7372 632F636F 6D6D6F6E 2F777369 6F2F6663 645F7072 6F62652E
63