Different device links for LUN in clustered nodes

[Shibu George P]

I am having a clustered nodes (rx 8640)with LUNs are allocated from XP storage. There are 2 separate storages, LUNs are from each storage is attached to each node and these LUNs are mirrord in OS level. There are 2 links for each LUNs.

For my one link the device file is matching in /dev/rdsk or /dev/dsk.

But for other link the device file is not matching.
Can Anybody help me on this issue.

Attached fcdlist output will give you more information.
nodenames: D, T

Red marked in â node_Dâ is not showing in T

Red marked in â node_Tâ are not showing in D.

[Shibu George P]

attached next file

[Duncan Edmonstone]

Actually I suspect you'll find that *none* of the paths match between the two hosts:

e.g. You think that c56t0d0 matches between hosts, but if you actually look at the hardware path you'll see that is actually presented out another port on the XP (it might be the same LUN, but its certainly not the same PATH to the LUN)

Next question is - why do you care - it's not a must for these things to match in a cluster.

HTH

Duncan

[Shibu George P]

Thanks Duncan for your quick response.

you mentioned that
"it's not a must for these things to match in a cluster.".

Can you please provide me how I can expand the existing filesystem in clustered environment with this device links.

Eg:- If I expand filesystem /abc
with /dev/dsk/c32t0d0 "T" and how I can configure for switching because this device is not appearing in "D"

Thanks in advance for your help

[Duncan Edmonstone]

Well what do your filesystems hosted on?

LVM Volumes?

VxVM volumes?

Straight on to raw disk?

What sort of cluster are we talking about?

Serviceguard?
VCS?
Oracle CRS?

More info required!

HTH

Duncan

[Duncan Edmonstone]

You do have a copy of xpinfo don't you?

This should make the task of matching LUNs across hosts a whole lot easier (you can match them by CU:LDEV reference)

HTH

Duncan