- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Identify the Hardware Address of the SCSI card
Operating System - HP-UX
1784524
Members
1295
Online
109157
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
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
Go to solution
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
тАО04-09-2007 02:45 PM
тАО04-09-2007 02:45 PM
This is the "ioscan -fC ctl" output on the environment show on the attached file
I Know that "0/3/1" refer to controler from the node, but I don`t undestand about 0.133.18.0.0.0.0 H/W path (SAN environment)
Could everyone tell me about it?
Why there are 4 H/W Path by controler?
# ioscan -fC ctl
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
==========
ctl 0 0/0/2/0.0.7.0 sctl CLAIMED DEVICE Initiator
ctl 1 0/0/2/0.1.7.0 sctl CLAIMED DEVICE Initiator
ctl 2 0/1/1/0.7.0 sctl CLAIMED DEVICE Initiator
ctl 3 0/1/1/1.7.0 sctl CLAIMED DEVICE Initiator
ctl 26 0/3/1/0.133.18.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 25 0/3/1/0.133.18.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 27 0/3/1/0.133.19.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 24 0/3/1/0.133.19.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 23 0/3/1/0.134.34.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 21 0/3/1/0.134.34.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 22 0/3/1/0.134.35.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 20 0/3/1/0.134.35.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 30 0/4/1/0.133.18.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 29 0/4/1/0.133.18.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 31 0/4/1/0.133.19.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 28 0/4/1/0.133.19.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 34 0/4/1/0.134.34.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 35 0/4/1/0.134.34.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 33 0/4/1/0.134.35.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 32 0/4/1/0.134.35.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
I Know that "0/3/1" refer to controler from the node, but I don`t undestand about 0.133.18.0.0.0.0 H/W path (SAN environment)
Could everyone tell me about it?
Why there are 4 H/W Path by controler?
# ioscan -fC ctl
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
==========
ctl 0 0/0/2/0.0.7.0 sctl CLAIMED DEVICE Initiator
ctl 1 0/0/2/0.1.7.0 sctl CLAIMED DEVICE Initiator
ctl 2 0/1/1/0.7.0 sctl CLAIMED DEVICE Initiator
ctl 3 0/1/1/1.7.0 sctl CLAIMED DEVICE Initiator
ctl 26 0/3/1/0.133.18.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 25 0/3/1/0.133.18.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 27 0/3/1/0.133.19.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 24 0/3/1/0.133.19.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 23 0/3/1/0.134.34.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 21 0/3/1/0.134.34.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 22 0/3/1/0.134.35.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 20 0/3/1/0.134.35.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 30 0/4/1/0.133.18.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 29 0/4/1/0.133.18.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 31 0/4/1/0.133.19.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 28 0/4/1/0.133.19.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 34 0/4/1/0.134.34.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 35 0/4/1/0.134.34.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 33 0/4/1/0.134.35.0.0.0.0 sctl CLAIMED DEVICE HP HSV101
ctl 32 0/4/1/0.134.35.255.0.0.0 sctl CLAIMED DEVICE HP HSV101
Solved! Go to Solution.
- Tags:
- ioscan
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2007 06:02 PM
тАО04-09-2007 06:02 PM
Solution
A FibreChannel hardware path is a complex thing. The meaning of the path components depends on the topology of FC connection (Fabric, Public Loop or Private Loop) and the used LUN addressing method. Depending on the equipment used, there may or may not be a way to easily map HW path numbers to FC switch ports.
Here's a good description of the whole thing:
http://docs.hp.com/en/A6795-90006/ch01s11.html?btnNext=next%C3%82%C2%A0%C3%82%C2%BB
MK
Here's a good description of the whole thing:
http://docs.hp.com/en/A6795-90006/ch01s11.html?btnNext=next%C3%82%C2%A0%C3%82%C2%BB
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2007 01:21 PM
тАО04-10-2007 01:21 PM
Re: Identify the Hardware Address of the SCSI card
The docs was OK..
Thanks
Thanks
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