How to get WWID's

[Mark Fisher_4]

We are purchasing a brand new Itanium based Superdome and plan on building the OS and booting from SAN based disks. Absolutely no locally attached disks. We will be working with our SAN folks to get EMC DCX700 disks carved into storage groups and presented to multiple vPars in the dome. In the past, we build and booted the OS on a locally attached disk and then used EMC Navisphere or the fcdutil command to get the wwid's for each hba conected to the system.

Now we will not have these utilities available. So the question is, how do you get the wwid's for each hba on a Superdome Complex without using these utilities? No nPars or vPars created yet. Just a brand new box with console access. I cannot find anything in the EFI shell that provides this.

Worst case, which I find completely unacceptable, would be to attach a local disk, build an OS on it, and attach all the hw to this nPAR. Then use HP/UX fcdutil command to get the wwid's for all the hba's. Then tear it all down and start building.

Also, this whole thing will be vPared as well. So we'll have to build vPar's on top of nPar's, while building multiple copies of HP/UX on all the SAN boot disks for each vpar.

Anybody been down this road before?

[Torsten.]

Hi Mark,

on a booted system, run

ioscan -fnCfc

to get the FC HBAs and now run

fcmsutil /dev/td0 (and so on)

to get the port wwn, or have a look on the switch port information.

[Ranjith_5]

Hi Mark,

A simple script to achieve this. Run this in your system.

WWN detail will be colected in tmp/WWN.txt


#!/usr/bin/sh
#Syam
>/tmp/WWN.txt
touch /tmp/WWN.txt
for i in `ioscan -funCfc|grep dev`
do
echo "">>/tmp/WWN.txt
echo " WWN for $i">>/tmp/WWN.txt
echo "-----------------------">>/tmp/WWN.txt
fcmsutil $i|grep -i "World Wide Name">>/tmp/WWN.txt
done


Hope this helps.

Regards,
Syam

[Andy Torres]

Personally, I prefer my OS on local internal disk for best OS IO, especially if mirroring. But to each their own.

To start, check the "Finding Bootable Devices (EFI Shell)" section in the HP System Partitions Guide: Administration for nPartitions at http://docs.hp.com/en/5991-1132/index.html

You may not have bootable devices on the SAN yet, but from EFI you may be able to see the WWIDs from the "map" command there.

Good luck!

[Mark Fisher_4]

remember, I have no OS loaded to run OS commands. All I have is a brand new box full of I/O chassis and HBA cards. I have to get the wwid's off of these cards so that the SAN folks can configure the switch and associate storage groups to wwid's.

EFI search command does not provide wwid's of the hba's.

[curt larson_1]

first of all are you going to create the genesis partition yourself or is the complex already going to have a complex profile created when it comes from hp?

if hp is going to create more then one partition, they will need to have an OS installed to do so. In which case, you'd think for the money your paying it wouldn't be to much trouble for them to run a couple of commands and tell you the wwid's

[Ranjith_5]

Hi mark,

Yes HP will always help you to find out the info. As a Superdome indtallation HP themselves will be interested to keep such datya with them. So no hard trys required. HP will get it for you.

Regards,
Syam

[curt larson_1]

of course your also going to need to know the hardware path for your lan card if your going to be doing the installation from an ignite server

and i don't know if this applies to EFI but in the BCH you can get the io information which does provide the device id. I don't know how helpful that will be

[curt larson_1]

and you would think all this information would be available on your SMS (support management station).

[Andy Torres]

Not sure how hardcore you want to get to find out the WWID of each card, but...

Aren't the WWIDs printed on a sticker on each card? Maybe you could look on the card itself. Or, maybe the WWIDs were on the shipping invoice or the receiving paperwork when the dome was delivered?

If you haven't received it yet, have HP provide the WWIDs.

Short of this, I'd say load a quickie technical load of HP-UX on local disk and boot it up just to run fcmsutil.

[AwadheshPandey]

visit this link:
http://docs.hp.com/en/A6826-96007/A6826-96007.pdf

Awadhesh

[USS Operations]

I'm hoping you have an answer by now but if not then yes the WWN's can be obtained from the EFI shell

Shell> reconnect -r

Shell> drivers
-- find the fc driver number

Shell> drvcfg
-- this shows all fibre channel cards/ports and their associated controller number.

Shell> drvcfg -s
From this menu system you can retrieve your WWN's for each card/port.

[Mark Fisher_4]

Thanks for the response. I tried this out. I get the wwid just fine, but, I can't figure out which card is which. I have an nPar that has 6 HBA's in it. Eventually I will carve this up into vPars and will assign an HBA to each vPar. So I will need to know the hardware path for the HBA. Then provide the wwid to our san guys so they can present a boot disk to this vpar/HBA.

Here's my output:

Shell> drvcfg 39
Configurable Components
Drv[39] Ctrl[86] Lang[eng]
Drv[39] Ctrl[8A] Lang[eng]
Drv[39] Ctrl[8E] Lang[eng]
Drv[39] Ctrl[92] Lang[eng]
Drv[39] Ctrl[9C] Lang[eng]
Drv[39] Ctrl[A0] Lang[eng]


Shell> drvcfg -s 39 86
Set Configuration Options
Drv[39] Ctrl[86] Lang[eng]
NOTE: Redirecting console output may cause test failures and is not recommended

Adapter Path: Acpi(PNP0002,082A)/Pci(01|00)/Pci(04|00)


eficfg> info

Adapter Path: Acpi(PNP0002,082A)/Pci(01|00)/Pci(04|00)
Adapter WWN: 50060B00003C9342
Adapter SN: 3C9342
Adapter ID:


Shell> drvcfg -s 39 8A
Set Configuration Options
Drv[39] Ctrl[8A] Lang[eng]
NOTE: Redirecting console output may cause test failures and is not recommended

Adapter Path: Acpi(PNP0002,083F)/Pci(01|00)/Pci(04|00)

eficfg> info

Adapter Path: Acpi(PNP0002,083F)/Pci(01|00)/Pci(04|00)
Adapter WWN: 50060B00003C932E
Adapter SN: 3C932E
Adapter ID:

[Patrice Le Guyader]

hi Mark,

I've done it before. Two SD32 (2 Npars/12 Vpars) on an XP1024. No disk attached to servers.
What we have done is to planned our configuration before (WWN<-->HW PAth); give to each vpar these IO cards (lan,FC,SCSI) and after on the SAN put only the boot disks attached to the host group(array security mechanism with WWN). The servers in the hosts group can only see the disk which are in it, no other. The vpars were assigned by two in each group (MC/SG config) so each vpar would see only 4 disks. We installed the first on it's two disks. After we have installed vpar manager, created the vpars and restarted the Npar as an vpar. Boot the second on the last 2 disks and launch the installation process from an ignite server. This again and again...

Once all the servers were installed we have started to put the application's disks into hosts group (WWN security) and start the installations.

For me if all is in the preparation.

Hope this helps
Kenavo
Pat

[Kalim Jacobs]

These days WWN numbers can be seen at EFI
type 'search all' and 'map -r'

Shell> search all
HP 2Port 2Gb Fibre Channel Adapter (driver 1.49 Beta5, firmware 3.03.154)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
Scsi(Pun8,Lun0) HP 36.4GMAP3367NC HPC7 (160 MBytes/sec)

...

HP 2Port 2Gb Fibre Channel Adapter (driver 1.49 Beta5, firmware 3.03.154)
HP 2Port 2Gb Fibre Channel Adapter (driver 1.49 Beta5, firmware 3.03.154)
...

Shell> map -r
Device mapping table
fs0 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(4|0)/Fibre(WWN22000004CF36261A,Lun0)/HD(Part1,Sig57ED1214-27B8-11DB-8002-D6217B60E588)
fs1 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(4|0)/Fibre(WWN22000004CF36261A,Lun0)/HD(Part3,Sig57ED1278-27B8-11DB-8004-D6217B60E588)
blk0 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(4|0)/Fibre(WWN2200000C5073BFB2,Lun0)
blk1 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(4|0)/Fibre(WWN22000004CF36261A,Lun0)


You can also derive some of the path HPUX might assign. The last one looks like
0/0/1/1/0/4/0.?.?.?...

Haven't found a doc that can tell me how to do the conversion for fibre yet though.