- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- device file naming on HP/UX and DMX2000 SAN
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
03-22-2007 12:35 AM
03-22-2007 12:35 AM
I have a server that I connected to a SAN (EMC DMX2000). When we zoned in the boot disks, the device files started off with C4txdx and c6txdx (primary / alt paths). After we installed the OS and made sure everything was ok, we zoned in the data disks and did an ioscan and an insf -e. After checking this, I noticed that in addition to the c4txdx and c6txdx, there were other device file names c12txdx , c13txdx, c14txdx and c15txdx.
I am new to the SAN environment and have a few questions:
1 - is this expected?
2 - There are only 2 controller cards on this server, what causes the Cx to change?
I have attached the ioscan output from this server. Any help would be appreciated.
Jay
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2007 12:53 AM
03-22-2007 12:53 AM
Solutionlooks pretty normal.
Due to the high Volume number in your "SAN" array the system (HP-UX) creates new busses to address them:
Volume Number (LUN): 3/0/4/1/0/4/0.1.8.0.2.2.4 => 276
Here you can see a point where it turns:
disk 58 3/0/4/1/0/4/0.1.8.0.0.15.7 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c4t15d7 /dev/rdsk/c4t15d7
disk 11 3/0/4/1/0/4/0.1.8.0.1.0.0 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c12t0d0 /dev/rdsk/c12t0d0
from ... 0.15.7 -> /dev/dsk/c4t15d7
to ... 1.0.0 -> /dev/dsk/c12t0d0
This is the address design.
in cxtydz
d goes from 0..7
t goes from 0..15
if reached, c will be increased.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2007 12:59 AM
03-22-2007 12:59 AM
Re: device file naming on HP/UX and DMX2000 SAN
1. Yes
2. I would surmise that the way things are wired there are alternate, in this case two pathes to every disk. This provides confusion and two ways to access the disk in the event of a partial failure of the SAN
SEP
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
03-28-2007 02:31 AM
03-28-2007 02:31 AM
Re: device file naming on HP/UX and DMX2000 SAN
Thank you for all the help. Just two more questions.
1. I am installing power path and would like to use pvlinks as well. Is this ok?
2. With pvlinks, the device used to create the volume group becomes the primary path and all i/o's go down this path. Is this limitation lifted with power path? Meaning, will all the paths to the device be used equally?
Thanks,
jay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2007 03:02 AM
03-28-2007 03:02 AM
Re: device file naming on HP/UX and DMX2000 SAN
1. I am installing power path and would like to use pvlinks as well. Is this ok?
- Yes thats fine - you can use both, although if PowerPath is working correctly you should never see LVM use its PVlinks
2. With pvlinks, the device used to create the volume group becomes the primary path and all i/o's go down this path. Is this limitation lifted with power path? Meaning, will all the paths to the device be used equally?
- Yes, PowerPath will load balance between the different paths automatically.
HTH
Duncan
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2007 02:35 AM
04-18-2007 02:35 AM