- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- dmesg error
Integrity Servers
1755721
Members
3247
Online
108837
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
Discussions
Discussions
Forums
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
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
тАО12-25-2009 01:06 AM
тАО12-25-2009 01:06 AM
dmesg error
I have a WARN in the dmesg and syslog on the Superdome box, as following:
FCD: h/w path conversion failed
What reasons,How do repair it.
FCD: h/w path conversion failed
What reasons,How do repair it.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-27-2009 09:31 PM
тАО12-27-2009 09:31 PM
Re: dmesg error
The warning message maybe related to a h/w path conversion ( legacy or new path formats ) based on WWN and Lun ID of a LUN on a fibre channel path. This conversation apparently seems to have failed for some reason.
I would expect some more messages popped up before this warning. The previous messages would be useful to understand what was going on.
Was there any changes on SAN? Do you see more messages/errors before this warning?
What HP-UX version, FC HBA and FC drivers are running on the partition?
I would expect some more messages popped up before this warning. The previous messages would be useful to understand what was going on.
Was there any changes on SAN? Do you see more messages/errors before this warning?
What HP-UX version, FC HBA and FC drivers are running on the partition?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-27-2009 11:34 PM
тАО12-27-2009 11:34 PM
Re: dmesg error
thank you for your reply,please refer to attatched the log file.other information is as following:
HPUXBaseOS B.11.23 HP-UX Base OS
HWEnable11i B.11.23.0712.070 Hardware Enablement Patches for HP-UX 11i v2, December 2007
QPKAPPS B.11.23.0712.070a Applications Patches for HP-UX 11i v2, December 2007
QPKBASE B.11.23.0712.070a Base Quality Pack Bundle for HP-UX 11i v2, December 2007
FibrChanl-00 B.11.23.0712 PCI FibreChannel;Supptd HW=A6795A,A5158A
FibrChanl-01 B.11.23.08.02 FibrChnl;SupptdHW=A6826A,A9782A,A9784A,AB378A,AB379A,AB465A,AD193A,AD194A,AD300A
FibrChanl-02 B.11.23.0712 PCIe FibreChannel;Supptd HW=AD299A,AD355A
HPUXBaseOS B.11.23 HP-UX Base OS
HWEnable11i B.11.23.0712.070 Hardware Enablement Patches for HP-UX 11i v2, December 2007
QPKAPPS B.11.23.0712.070a Applications Patches for HP-UX 11i v2, December 2007
QPKBASE B.11.23.0712.070a Base Quality Pack Bundle for HP-UX 11i v2, December 2007
FibrChanl-00 B.11.23.0712 PCI FibreChannel;Supptd HW=A6795A,A5158A
FibrChanl-01 B.11.23.08.02 FibrChnl;SupptdHW=A6826A,A9782A,A9784A,AB378A,AB379A,AB465A,AD193A,AD194A,AD300A
FibrChanl-02 B.11.23.0712 PCIe FibreChannel;Supptd HW=AD299A,AD355A
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2009 08:22 PM
тАО12-28-2009 08:22 PM
Re: dmesg error
I see no relevant messages to the FCD message. It's hard to pin point to possible cause but it's interesting...
I would run following commands
# ioscan -fn
# /opt/fcms/bin/fcddiag
# /opt/fcms/bin/fcdlist
I would check if the message pops up while running "ioscan -fn" command and check any NO_HW devices in the output. I would also run the given EMS "resdata" commands to check the reported entity in the FPL.
The problem may or maynot be related to the FCD driver installed which is dated 12/07. However installing the latest FCD driver version is a good idea to take advantages of the new features and have defects free version installed. This also helps in troubleshooting.
http://docs.hp.com/en/J6374-90083/index.html
I would run following commands
# ioscan -fn
# /opt/fcms/bin/fcddiag
# /opt/fcms/bin/fcdlist
I would check if the message pops up while running "ioscan -fn" command and check any NO_HW devices in the output. I would also run the given EMS "resdata" commands to check the reported entity in the FPL.
The problem may or maynot be related to the FCD driver installed which is dated 12/07. However installing the latest FCD driver version is a good idea to take advantages of the new features and have defects free version installed. This also helps in troubleshooting.
http://docs.hp.com/en/J6374-90083/index.html
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP