HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Inquiry failed on FCP device
Operating System - HP-UX
1832891
Members
2424
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2009 09:08 AM
02-23-2009 09:08 AM
Inquiry failed on FCP device
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.
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.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2009 10:51 AM
02-23-2009 10:51 AM
Re: Inquiry failed on FCP device
Please run as suggested:
opt/resmon/bin/resdata -R 1376256012 -r /adapters/events/ql_adapter/0_6_1_
0_4_0 -n 1376256044 -a
(one liner)
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
opt/resmon/bin/resdata -R 1376256012 -r /adapters/events/ql_adapter/0_6_1_
0_4_0 -n 1376256044 -a
(one liner)
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP