WWID

[Mulder_1]

How to find a WWID of a SAN disk mounted on VMS ?
VMS v7.3-1

This is what I get when I type sh dev dgaxxx/fu :


Disk $1$DGA560: (sedfu), device type HITACHI OPEN-E, is online, mounted, file-
oriented device, shareable, device has multiple I/O paths, served to cluster
via MSCP Server, error logging is enabled.

Error count 0 Operations completed 129785
Owner process "" Owner UIC [SYS,SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 1 Default buffer size 512
Current preferred CPU Id 0 Fastpath 1
WWID 02000010:
Total blocks 28452960 Sectors per track 96
Total cylinders 19759 Tracks per cylinder 15
Host name "SEDFU" Host type, avail AlphaServer ES45 Model 2B, yes
Alternate host name "PEDFU" Alt. type, avail AlphaServer ES45 Model 2B, yes
Allocation class 1

Volume label "RPTS01" Relative volume number 0
Cluster size 28 Transaction count 1
Free blocks 19957140 Maximum files allowed 490568
Extend quantity 12 Mount count 5
Mount status System Cache name "_$1$DGA100:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 1995714
File ID cache size 64 Blocks in extent cache 144256
Quota cache size 0 Maximum buffers in FCP cache 2470
Volume owner UIC [1,1] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

Thanks

[Jur van der Burg]

write sys$output f$getdvi("$1$dga1","wwid")

Or upgrade to a more recent version where 'show device' will show it.

Jur.

[Wim Van den Wyngaert]

f$getdvi with "WWID" ?

Wim

[Richard W Hunt]

RHSC04>wwid = f$getdvi( "SYS$SYSDEVICE","WWID" )
RHSC04>show symbol wwid
WWID = "01000010:6006-0160-0231-1900-D41B-F1F7-BA05-DD11"

Wim, from your response, it appears that for once, I knew something before you did. It made my day. (Then my boss walked into the cube with more work and it went down the toilet again...)

[Uwe Zessin]

Wow, the Clariion supports OpenVMS?

[Ian Miller.]

(insert usual comments about upgrading to a supported version, at least V7.3-2, its so much better etc)

[Richard W Hunt]

Uwe, yes the Clariion supports OVMS if you are willing to waste a smallish volume. For some reason that my storage management team and I haven't quite resolved, you cannot have a DGA0 on a Clariion. If you try to get the console to recognize it with WWIDMGR and the appropriate commands, it looks like DGA(-1). However, DGA1 and higher are OK. So we created a tiny DGA0 and don't even bother to mount it.

[Uwe Zessin]

Well, you cannot have a "DGA0" on EVA (and maybe HSG - the CLI command uses "NOIDENTIFIER", but "IDENTIFIER=0" might work, too) either - "0" means something like: "don't present a unit identifier"

A SCSI LUN without such an identifier is indeed shown as "-1" from WWIDMGR.

Do you have to use the trick to create a 'small disk' at LUN address 0 so OpenVMS can recognize the remaining disks? (I guess you make the LUN address and IDENTIFIER number the same? although there is no need to do)

[Richard W Hunt]

Uwe, yes we had to create it. Whatever is the first drive presented by the Clariion is the troublesome drive. We created DGA0 just to absorb the troubles into a drive we weren't going to use.

Unlike its big brother, Symmetrix, a Clariion determines the presented unit number (UDID) in some oddball way. I would have to call in our top data storage engineer to tell you more than that.