Operating System - HP-UX
1831929 Members
3762 Online
110031 Solutions
New Discussion

How does HP allocate device names for disk devices?

 
SOLVED
Go to solution
Todd McDaniel_1
Honored Contributor

How does HP allocate device names for disk devices?

Okay, I have been having a problem with EMC attachedc storage...

My EMC folks allocated me 120 new LUNS with a single alt path for a total of 240 devices...

Now, We have gone around on this for over a week now. My EMC folks are 99% sure their is no issue on their side. I think I can believe them on this.

My issue is this. When I do my ioscan/insf to bring in the devices for me to use for VGs, I have one group of devices that line up great and the PRI and ALT devices have diff C# but the same T# And D# as you would expect.

However, on the other HBA, although the devices seem to be paired as I look at them in the /dev/dsk and rdsk dirs, when I run my inq -sortsymm > file, they DONT match up properly.

Here is what I mean...

On the pair that does match this is what it looks like:

/dev/rdsk/c67t0d1 :EMC :SYMMETRIX :5568 :690D6000 :8838721
/dev/rdsk/c69t0d1 :EMC :SYMMETRIX :5568 :690D6000 :8838721
/dev/rdsk/c69t0d2 :EMC :SYMMETRIX :5568 :690D7000 :8838721
/dev/rdsk/c67t0d2 :EMC :SYMMETRIX :5568 :690D7000 :8838721



However, on the other HBA pair I have this mess:

/dev/rdsk/c82t0d2 :EMC :SYMMETRIX :5568 :69235000 :8838721
/dev/rdsk/c74t6d5 :EMC :SYMMETRIX :5568 :69236000 :8838721
/dev/rdsk/c82t0d3 :EMC :SYMMETRIX :5568 :69236000 :8838721
/dev/rdsk/c82t0d4 :EMC :SYMMETRIX :5568 :69237000 :8838721
/dev/rdsk/c74t6d6 :EMC :SYMMETRIX :5568 :69237000 :8838721


What in HPUX manages how devices are assigned to LUNS? Is there anything I can do on the Host side? MY EMC folks assure me they have everything kosher and that it looks good from their point of view.

Signed,
Desperate in Dallas.
Unix, the other white meat.
11 REPLIES 11
Todd McDaniel_1
Honored Contributor

Re: How does HP allocate device names for disk devices?

To be fair 1 device does line up, the first one of the HBA group...


/dev/rdsk/c82t0d1 :EMC :SYMMETRIX :5568 :691EB000 :8838721
/dev/rdsk/c74t0d1 :EMC :SYMMETRIX :5568 :691EB000 :8838721

but all the following ones dont.... Im very stumped.

/dev/rdsk/c74t6d4 :EMC :SYMMETRIX :5568 :69235000 :8838721
/dev/rdsk/c82t0d2 :EMC :SYMMETRIX :5568 :69235000 :8838721
/dev/rdsk/c74t6d5 :EMC :SYMMETRIX :5568 :69236000 :8838721
/dev/rdsk/c82t0d3 :EMC :SYMMETRIX :5568 :69236000 :8838721
Unix, the other white meat.
Sridhar Bhaskarla
Honored Contributor

Re: How does HP allocate device names for disk devices?

Todd,


/dev/rdsk/c67t0d1 :EMC :SYMMETRIX :5568 :690D6000 :8838721
/dev/rdsk/c69t0d1 :EMC :SYMMETRIX :5568 :690D6000 :8838721

The above is correct and legal.


dev/rdsk/c74t6d5 :EMC :SYMMETRIX :5568 :69236000 :8838721
/dev/rdsk/c82t0d3 :EMC :SYMMETRIX :5568 :69236000 :8838721

The above is not correct.

While I can't answer from the EMC's perspective, you should be seeing the same target and device numbers for alternate links on the system. It is perfectly possible (and ofcourse valid) on the storage side to configure a different target and LUN number for the same device on different FAs. It will be recognized as an alternate link by the VG. However, it can confuse you to the hell and make a mess out of your system because you cannot identify them with your human eyes.

HP creates the devices as it sees based on the controller - target - LUN. You cannot really do anything on the system side. It is to be fixed by your EMC engineer.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
James A. Donovan
Honored Contributor
Solution

Re: How does HP allocate device names for disk devices?

I'm assuming that you are attaching directly to the back of the Symmetrix and not thru a switch....that said you need some new EMC folks. The problem is clearly on the EMC side. The issue is that the bin file is what controls the target and lun information for each device seen thru each director.

The bin file is saying that device 036 will have a target=6 and a lun=5 when presented from the director attached to your c74 HBA, but will have a target=0 and a lun=3 when presented through the director attached to your c82 HBA. So on, and so forth for the other devices presented over these two directors.

Technically, from EMC's perspective there is nothing wrong with this. From your's, there is everything wrong with this. You need to tell your EMC SE that you want devices to have identical target/lun configurations no matter what director they are presented over.

You could fix the issue yourself if you have the ability to use the symconfigure utility. The problem is that
Remember, wherever you go, there you are...
Stuart Abramson_2
Honored Contributor

Re: How does HP allocate device names for disk devices?

Jim Donovan is on the right track.

In "CxTxDx" the "C" number is determined by the HBA and the "vbus" of the logical path that the HyperVolume is presented on. You can see "vbus" by doing (excuse spacing):

# symcfg -sa 3a -address list


Symmetrix ID: 000184500421 (Local)

Director Device Name Attr Address
---------------------- ----------------------------- ---- --------------
Ident Symbolic Port Sym Physical VBUS TID LUN
------ -------- ---- ---- ----------------------- ---- --- ---

FA-3A 03A 0 0000 /dev/rdsk/c16t0d0 VCM 0 0 000
...................0001 /dev/rdsk/c16t0d1 0 0 001
..................0002 /dev/rdsk/c16t0d2 0 0 002
..................0003 /dev/rdsk/c16t0d3 0 0 003
..................0005 Not Visible 0 0 004

The HP-UX "t" number comes from the "TID" in the above listing. The HP-UX "d" number is the "LUN" number in the above listing.

What happened to you is that the TID and LUN numbers on the two SA/FA paths don't line up equally. One path has more/less HVs than the other. This could be perfectly acceptable, or it could mean that they left out 1 alternate path.

If you have all of your alternate paths, then you don't have a big problem. You're not really missing anything. It's just not "neat".

What I do is, for alternate paths, I try to put the new HVs at a new "vbus" and present them both exactly the same. You have to do this with "symconfigure".
R Madhavan
Frequent Advisor

Re: How does HP allocate device names for disk devices?

Hi Todd,

Both Donavan and Sturat are on right track.

It is perfectly legal and acceptable from both Symmetrix and HP-UX point of view to have a same symm. device with two different target and LUN numbers if presented to differenct FA at symm side. This is fully controlled at EMC side. So do not trust what your EMC guy is saying to you now.

In your case, it is absolutely no problem, with only difference is that you can not see which is the second link w/o looking at the syminq output.
I do have the same configuration, and rely on syminq output to get the alternate link for the VG. I have this config. because i do not have the same target and LUN free on the other FA at symmetrix and hence i got to choose different number.
In fact this target and LUB number is controlled by us, using the SDDR software. If you are familiar in using SDDR and have the same target and LUN number free, then i suggest you go and change for the alternate link, which make less confusion in indentifying the alternate link devices.

Madhavan
Todd McDaniel_1
Honored Contributor

Re: How does HP allocate device names for disk devices?

Thanks all for your help.

I do have some understanding of EMCs frame management since I took the ECC 5.1 course, but I dont manage my symm frames. I have no experience with SDDR or any disk management other than my training... We have a separate Storage Manangement group who does that work.


----------------------------------------
Madhavan:

Your quote:

"If you are familiar in using SDDR and have the same target and LUN number free, then i suggest you go and change for the alternate link, which make less confusion in indentifying the alternate link devices."



In fact, all the cxtxdx numbers line up when I pull them out of /dev/dsk dir in sort order... yes, they do line up by cXtXdX... but when I sort them using inq -sortsymm... However, they were assigned incorrectly as I showed in my original post, as you and others have stated that the target and lun were assigned incorrectly...


I have asked them yet again to look at it...

Thanks again for your info, it is greatly appreciated.
Unix, the other white meat.
Todd McDaniel_1
Honored Contributor

Re: How does HP allocate device names for disk devices?

One more thing, I dont necessarily NEED the alt path to be the same, except for the controller, but it would be nice for it all to line up as all my other hosts and symms do, as well as all my other disk on this symm.

I have POWERPATH installed which is able to see the alt path whether or not I even defined it as my ALT in pvlinks, which I usu do just so I can see the ALT...

My only concern is now, that I am adding 12TB in a few months and dont want them to have this same problem with those disks.

Just trying to keep it all the same for sake of consistency.
Unix, the other white meat.
Sridhar Bhaskarla
Honored Contributor

Re: How does HP allocate device names for disk devices?

Hopefully, my message was completely read where I stated it was completely legal to have alterate links with different LUN and target numbers as looking at the other replies I was on wrong track :-)

If you have EMC, then you will definitely have syminq on the system which can be used to identify the alternate paths.

As long as you don't touch the disks on the other controller, then you should be ok as the alternate paths and load balancing are managed by powerpath. For ex., all your LVM operations are to be done on only c74*. But you may want to configure the alternate links in your VG as it wouldn't hurt. In this case, after creating|modifying the VGs, you can export and import the VGs with '-s' option that will take care of adding the alternate paths.

There is another way (other than xpinfo|syminq) to find out the alternate links. For ex., run the below on all the disks. The ones that have identical ouptuts are alternate to each other.

echo 0x2008?2X | adb /dev/dsk/cxtydz|awk '{print $3}'

-Sri

You may be disappointed if you fail, but you are doomed if you don't try
Todd McDaniel_1
Honored Contributor

Re: How does HP allocate device names for disk devices?

inq -sortsymm provides a similar output to syminq...

but sorts the devices by hypervolume number... which identifies the Pri and associated Alt devices.
Unix, the other white meat.
Sundar_7
Honored Contributor

Re: How does HP allocate device names for disk devices?

Hi,

OK.. there is a way to ensure that the disks you will be adding will have the same target and LUN number.

On the host where EMC control center software is loaded

1) Find out the channel directors your host is attached to

2) execute this command to find out the free vbus, lun and target that can be used to map the new EMC devices to the host

# symcfg list -SA 5B -address -available
# symcfg list -SA 6B -address -available

Here I assume your host is attached to the EMC channel directors 5B & 6B.

From the output of the above commands, pick the vbus,lun and target combination that are available in both the channel directors.

3) Now, to assign the EMC devs to the host you need to create a mapping config that will be used by symconfiure command

# vi /tmp/host.map
map dev 469 to dir 5B:0 target=8, LUN=2, vbus=3;
map dev 469 to dir 6B:0 target=8, LUN=2, vbus=3;
map dev 47A to dir 5B:0 target=0, LUN=3, vbus=4;
map dev 47A to dir 5B:0 target=0, LUN=3, vbus=4;
#

4) Preview and apply the configuration

# symconfigure -f /tmp/host.map preview

# symconfigure -f /tmp/host.map commit

5) Execute ioscan and insf from the host and you are done.

Now u should see the primary and alternate link have the same target and lun number but a different controller number, for obvious reasons :-)

hope this helps

-- Sundar.




Learn What to do ,How to do and more importantly When to do ?
Todd McDaniel_1
Honored Contributor

Re: How does HP allocate device names for disk devices?

Okay, this is a follow-up.

I still had this problem unresolved today, so I figured I would do a bit of trial and error with some powermt commands...

I had a set of commands I was given whenever I had dead or ghost disks on my box so I could remove them from the VCM database or at least so they would be disregarded by my inq/syminq commands.

Okay, I ran:

powermt check # to check for dead devices and to remove them which I did.
powermt config
powermt display

The result is this: My devices now line up as they should!!! It was a strange problem I had never seen before. I will have to think about how it happened.

The short version is that I now have my pri/alt devices that match as follows:

/dev/rdsk/c82t0d2 :EMC :SYMMETRIX :5568 :69235000 :8838721
/dev/rdsk/c74t0d2 :EMC :SYMMETRIX :5568 :69235000 :8838721
/dev/rdsk/c74t0d3 :EMC :SYMMETRIX :5568 :69236000 :8838721
/dev/rdsk/c82t0d3 :EMC :SYMMETRIX :5568 :69236000 :8838721
/dev/rdsk/c82t0d4 :EMC :SYMMETRIX :5568 :69237000 :8838721
/dev/rdsk/c74t0d4 :EMC :SYMMETRIX :5568 :69237000 :8838721
/dev/rdsk/c74t1d7 :EMC :SYMMETRIX :5568 :69238000 :8838721
/dev/rdsk/c82t1d7 :EMC :SYMMETRIX :5568 :69238000 :8838721
/dev/rdsk/c74t2d0 :EMC :SYMMETRIX :5568 :69239000 :8838721
/dev/rdsk/c82t2d0 :EMC :SYMMETRIX :5568 :69239000 :8838721


etc, etc, etc...

Unix, the other white meat.