HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: HO_HW on FCP Array Interface
Operating System - HP-UX
1836653
Members
1977
Online
110102
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
09-25-2008 05:48 AM
09-25-2008 05:48 AM
HO_HW on FCP Array Interface
Hi Guys
A snip from an ioscan (which is dog slow btw.)
thosan@picard|pts/2:/dev/vx/dmp$ sudo ioscan -fun | grep -i 0/2/1/0/4/0.61
fcp 11 0/2/1/0/4/0.61 fcd_fcp CLAIMED INTERFACE FCP Domain
ext_bus 41 0/2/1/0/4/0.61.14.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
disk 51 0/2/1/0/4/0.61.14.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 56 0/2/1/0/4/0.61.14.0.0.2.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 59 0/2/1/0/4/0.61.14.0.0.2.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 60 0/2/1/0/4/0.61.14.0.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 63 0/2/1/0/4/0.61.14.0.0.3.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
ext_bus 37 0/2/1/0/4/0.61.14.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ctl 14 0/2/1/0/4/0.61.14.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
ext_bus 42 0/2/1/0/4/0.61.30.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
disk 50 0/2/1/0/4/0.61.30.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 53 0/2/1/0/4/0.61.30.0.0.2.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 55 0/2/1/0/4/0.61.30.0.0.2.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 58 0/2/1/0/4/0.61.30.0.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 64 0/2/1/0/4/0.61.30.0.0.3.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
ext_bus 38 0/2/1/0/4/0.61.30.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ctl 12 0/2/1/0/4/0.61.30.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
ext_bus 31 0/2/1/0/4/0.61.45.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
disk 39 0/2/1/0/4/0.61.45.0.0.2.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 40 0/2/1/0/4/0.61.45.0.0.2.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 41 0/2/1/0/4/0.61.45.0.0.2.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 42 0/2/1/0/4/0.61.45.0.0.3.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 43 0/2/1/0/4/0.61.45.0.0.5.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 44 0/2/1/0/4/0.61.45.0.0.5.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
ext_bus 32 0/2/1/0/4/0.61.45.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ctl 11 0/2/1/0/4/0.61.45.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
ext_bus 33 0/2/1/0/4/0.61.188.0.0 fcd_vbus NO_HW INTERFACE FCP Array Interface
ext_bus 34 0/2/1/0/4/0.61.188.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ctl 10 0/2/1/0/4/0.61.188.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
As you can see, one of the FCP Array Interfaces are in NO_HW, but an Device Interface and a sctl DEVICE is attached. Is this normal behaviour or? What casues this? And can you point me to a solution on how to fix this?
BR. Thomas
A snip from an ioscan (which is dog slow btw.)
thosan@picard|pts/2:/dev/vx/dmp$ sudo ioscan -fun | grep -i 0/2/1/0/4/0.61
fcp 11 0/2/1/0/4/0.61 fcd_fcp CLAIMED INTERFACE FCP Domain
ext_bus 41 0/2/1/0/4/0.61.14.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
disk 51 0/2/1/0/4/0.61.14.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 56 0/2/1/0/4/0.61.14.0.0.2.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 59 0/2/1/0/4/0.61.14.0.0.2.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 60 0/2/1/0/4/0.61.14.0.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 63 0/2/1/0/4/0.61.14.0.0.3.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
ext_bus 37 0/2/1/0/4/0.61.14.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ctl 14 0/2/1/0/4/0.61.14.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
ext_bus 42 0/2/1/0/4/0.61.30.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
disk 50 0/2/1/0/4/0.61.30.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 53 0/2/1/0/4/0.61.30.0.0.2.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 55 0/2/1/0/4/0.61.30.0.0.2.6 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 58 0/2/1/0/4/0.61.30.0.0.2.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 64 0/2/1/0/4/0.61.30.0.0.3.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
ext_bus 38 0/2/1/0/4/0.61.30.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ctl 12 0/2/1/0/4/0.61.30.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
ext_bus 31 0/2/1/0/4/0.61.45.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
disk 39 0/2/1/0/4/0.61.45.0.0.2.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 40 0/2/1/0/4/0.61.45.0.0.2.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 41 0/2/1/0/4/0.61.45.0.0.2.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 42 0/2/1/0/4/0.61.45.0.0.3.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 43 0/2/1/0/4/0.61.45.0.0.5.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
disk 44 0/2/1/0/4/0.61.45.0.0.5.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
ext_bus 32 0/2/1/0/4/0.61.45.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ctl 11 0/2/1/0/4/0.61.45.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
ext_bus 33 0/2/1/0/4/0.61.188.0.0 fcd_vbus NO_HW INTERFACE FCP Array Interface
ext_bus 34 0/2/1/0/4/0.61.188.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ctl 10 0/2/1/0/4/0.61.188.255.0.0.0 sctl CLAIMED DEVICE EMC SYMMETRIX
As you can see, one of the FCP Array Interfaces are in NO_HW, but an Device Interface and a sctl DEVICE is attached. Is this normal behaviour or? What casues this? And can you point me to a solution on how to fix this?
BR. Thomas
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2008 06:58 AM
09-25-2008 06:58 AM
Re: HO_HW on FCP Array Interface
Shalom,
No, this is not normal behavior.
Either the Fiber channel interface has gone bad or something has happened to fool the system into this state.
I would treat this as a hardware problem and try and solve it before you have symptoms.
Does anything on that bus function? Recent configuration changes?
SEP
No, this is not normal behavior.
Either the Fiber channel interface has gone bad or something has happened to fool the system into this state.
I would treat this as a hardware problem and try and solve it before you have symptoms.
Does anything on that bus function? Recent configuration changes?
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2008 02:28 PM
09-25-2008 02:28 PM
Re: HO_HW on FCP Array Interface
Your fibre channel card is having some hardware issue.
Check for
ioscan -fnC fc
fcmsutil /dev/.....
Contact HP for the replacement of Hardware.
Thanks
SKR
Check for
ioscan -fnC fc
fcmsutil /dev/.....
Contact HP for the replacement of Hardware.
Thanks
SKR
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