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.

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one. If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up. After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa. -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un

Unix Revolution

Search This Blog