Decoding HDS LUN presented to Linux

WORK IN PROGRESS - the more rocks I overturn, the more data I find that I am missing :-(

I'm gathering information from a number of sources and I have not found a source that covers this entire topic. You can find additional information elsewhere, if you need more detailed info.
I anticipate this post will contain quite a bit of data at some point.

This... is an example of the multipath device you would see from Red Hat. Notice it is similar to your standard WWN, but not absolutely the same.

# multipath -ll -v2 | tail -5
360060e800571c900000071c9000005f7 dm-5 HITACHI,OPEN-V
size=200G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 5:0:0:0 sdb 8:16 active ready running
`- 6:0:0:0 sdh 8:112 active ready running

Let's break this down.

36 0060e8 00 5 71c9 00 000071c9000005f7
36 - Vendor Code (For some reason this is NOT 50, as expected)
0060e8 - HDS OUI
00
5 - Front End Port (FEP) - in this case 'F'
71c9 - HDS Array Serial Number (in Hex)

http://en.wikipedia.org/wiki/World_Wide_Name

500060E8WWXXXXYZ

50: the first 4 bits from the WWN are 0101 (5 hex), and show which is the organization responsible for the name assignment (NAA). 5 means - (format 5 of NAA) means that the Vendor (e.g. Hitachi) is responsible for uniquely use the whole address.
0060E8: next in the WWN is the unique ID of the Vendor. It is assigned by ieee to different organizations. Each vendor has unique ID, and some vendors may have more than than one ID. On web address http://standards.ieee.org/regauth/oui/index.shtml you may check them. For 0060e8 you will find
HITACHI COMPUTER PRODUCTS (AMERICA), INC.
3101 TASMAN DRIVE
SANTA CLARA CA 95054
UNITED STATES
From here on is the interesting part. VSID - Vendor Specific ID
WW: is the family of the hardware. If it’s “01″ then it’s a 7700/”Thunder”. “02″ is a 9900/”Lightning”.
XXXX: is the serial number. It’s a hex value, convert it to decimal and that’s the box serial number.
Y: is the cluster. 0=Cluster 1 (Left hand side) and 1=Cluster 2 (Right hand side).
Z: is the port. Note there is no Port I. Use this table:

9K
AL
BM
CN
DO
EP
FQ

WW value - model	HP model
01	XP 256
02	XP 512/48
03	XP1024/128
04	XP12000/10000
??	XP24000

HP XP Port WWN = 50:00:60:E8:01:12:34:0A
0A - CHIP Port
0 - means 1
A - means L (see table)

Description	WWN	Serial	model	CHIP
XP 12000, disk system 5004, FRHA043981	50:06:0e:80:04:ab:cd:00	hex: abcd dec: 43981	04 => XP12000	1A
XP 12000, disk system 5005, FRHA012345	50:06:0e:80:04:30:39:04	hex: 3039 dec: 12345	04 => XP12000	1D

example 1:

12:34 - Serial#

example 2

This information was retrieved from http://brionetka.com/linux/?p=38 and I am certain that person put quite a bit of effort into documenting this information and deserves credit.

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them. If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid. The USS is simply a box.. running Solaris .. with IPMP and ZFS. Great. If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun. After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit. Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things. Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor. (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb). I'm not sure how to proceed. This procedure worked for RHEVh, because it is quite a bit smaller. Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

Unix Revolution

Search This Blog