GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SAN/HBA failure in syslog
Operating System - HP-UX
1855764
Members
12418
Online
104103
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
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-19-2010 03:45 PM
02-19-2010 03:45 PM
SAN/HBA failure in syslog
I am receiving the following errors in the syslog file. The errors only last for a few minutes then come back.
Feb 18 18:17:09 gput49 vmunix: 3/0/6/1/0/4/0: Device at device id 0x30e00 has disappeared from Name Server GPN_FT
Feb 18 18:17:09 gput49 vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
Feb 18 18:17:09 gput49 vmunix: device id = loop id, for private loop devices
Feb 18 18:17:09 gput49 vmunix: device id = nport ID, for fabric/public-loop devices
Feb 18 18:17:09 gput49 vmunix: System won't be able to see LUNs behind this port.
Couple of questions:
1 - How do I translate the device id (device id 0x30e00 in this case) into something recognizable like a disk path or such?
2 - What does GPN_FT mean?
OS is 11.11
Server is a vpar on an RP8420
HBAs are A9784-60002 Qlogic adapters.
Feb 18 18:17:09 gput49 vmunix: 3/0/6/1/0/4/0: Device at device id 0x30e00 has disappeared from Name Server GPN_FT
Feb 18 18:17:09 gput49 vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
Feb 18 18:17:09 gput49 vmunix: device id = loop id, for private loop devices
Feb 18 18:17:09 gput49 vmunix: device id = nport ID, for fabric/public-loop devices
Feb 18 18:17:09 gput49 vmunix: System won't be able to see LUNs behind this port.
Couple of questions:
1 - How do I translate the device id (device id 0x30e00 in this case) into something recognizable like a disk path or such?
2 - What does GPN_FT mean?
OS is 11.11
Server is a vpar on an RP8420
HBAs are A9784-60002 Qlogic adapters.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 04:28 PM
02-19-2010 04:28 PM
Re: SAN/HBA failure in syslog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2010 03:08 AM
02-20-2010 03:08 AM
Re: SAN/HBA failure in syslog
Hi,
First you can find the fc card in the path 3/0/6/1/0/4/0, you can type ioscan -funC fc. And you should find a device path depends on you FC card, /dev/tdx , /dev/fcdx o something. You can use the floowing command to fine n_port_id of 0x30e00 by typing:
fcmsutil /dev/tdx get remote all
0x30e00 is N_PORT ID of the device on the SAN. N_port_ids are 24-bit numbers given by SAN fabric.
There error means, there is a problem to reach the device on the SAN with this n_port_id, possibly zoning/cable or device reset problem.
First you can find the fc card in the path 3/0/6/1/0/4/0, you can type ioscan -funC fc. And you should find a device path depends on you FC card, /dev/tdx , /dev/fcdx o something. You can use the floowing command to fine n_port_id of 0x30e00 by typing:
fcmsutil /dev/tdx get remote all
0x30e00 is N_PORT ID of the device on the SAN. N_port_ids are 24-bit numbers given by SAN fabric.
There error means, there is a problem to reach the device on the SAN with this n_port_id, possibly zoning/cable or device reset problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2010 06:04 PM
02-20-2010 06:04 PM
Re: SAN/HBA failure in syslog
You could also find it by longing into the switch and displaying the nameserver. That should so the nport IDs and ports as well and other info about the device.
However, The message says that the device disappeared for the name sever. If it didn't come back online you might not find it. But you could see what is missing if you know what is supposed to be there.
However, The message says that the device disappeared for the name sever. If it didn't come back online you might not find it. But you could see what is missing if you know what is supposed to be there.
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 2026 Hewlett Packard Enterprise Development LP