- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- how do we determine I/O channel seperation is poss...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
01-13-2002 01:28 AM
01-13-2002 01:28 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2002 01:33 AM
01-13-2002 01:33 AM
Re: how do we determine I/O channel seperation is possible
0/0/1/1.15.0 & 0/0/2/1.15.0
can any one explain in more depth about reading the hw path
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2002 07:48 AM
01-13-2002 07:48 AM
Re: how do we determine I/O channel seperation is possible
Two flags in ioscan will help you in understanding the paths.
ioscan -f > ioscan.out
ioscan -fnC disk > disk.out
ioscan -f will give you detailed description of each component, You will find like
ext_bus 2 0/0/2/0 c720
875 Ultra Wide Single-Ended
target 4 0/0/2/0.2 tgt
disk 1 0/0/2/0.2.0 sdisk
0/0/2/0 is the controller address - c
2 is the target - t
0 is the LUN (Scsiid of the disk) - d
So the combined address
SO this will make the device file c2t2d0
You can also do an lssf on /dev/dsk/c2t2d0 to find the information.
Look for the corresponding device in ioscan -fnC disk output.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2002 09:47 AM
01-13-2002 09:47 AM
Re: how do we determine I/O channel seperation is possible
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2002 12:29 PM
01-13-2002 12:29 PM
Re: how do we determine I/O channel seperation is possible
In ur server:
1) 0/0/1/1.15.0 - '0/0/1/1' is the controller address, '15' is the SCSI id of the disk, '0' is the LUN number.
2) 0/0/2/1.15.0 - '0/0/2/1' is the controller address, '15' is the SCSI id of the disk, '0' is the LUN number.
See this for some information about hardware addressing:
http://us-support.external.hp.com/cki/bin/doc.pl/sid=d3223f600c564ffc9d/screen=ckiDisplayDocument?docId=200000009825652
Also check 'man ioscan' and Hardware addressing topic in www.docs.hp.com
HTH,
Shiju
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2002 11:23 PM
01-13-2002 11:23 PM
Re: how do we determine I/O channel seperation is possible
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2002 12:49 AM
01-14-2002 12:49 AM
Re: how do we determine I/O channel seperation is possible
the c#t#d#[s#] syntax used in default device special files derives from ioscan output: c# is the card instance for the ext_bus class of
interface card to which the device is attached, t# is the target (SCSI address) of the disk device on the interface, d# is the device unit number.s# specifies section number and is provided for backward compatibility;
the device file addresses the entire disk (s0) when s# is unspecified. (See the disk (7) manpage.)
thinphony.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2002 01:22 AM
01-14-2002 01:22 AM
SolutionConfirmed. The number associated with C determines the instance number that is unique to each controller. So, in your case, there are two controllers and Yes channel seperation is possible.
-Sri