How to obtain LUN Hardware Path on PA-RISC

[Daniel A]

Hi!

I have a Superdome PA-RISC with two hard partitions (npars), one of them is booting since SAN.

I did a LUN replication of the disk with the EVA and I want to present it to the other npar. When It's in the other npar I type the command "sea" to obtain the hardware path, I see the following:

Main Menu: Enter command or menu > sea

Searching for potential boot device(s) on the core cell
This may take several minutes.

To discontinue search, press any key (termination may not be immediate).


IODC
Path# Device Path (dec) Device Type Rev
----- ----------------- ----------- ----
0/0/3/1/0.0 Fibre Channel Protocol 13
0/0/3/1/1.0 Fibre Channel Protocol 13

No Devices Found


And I can't boot since them.

If I put the CD installtion of HP-UX I can see the hardware path of the disk but I want to know if there are another way to obtain it since BCH.

Thanks.

[Duncan Edmonstone]

Is there a way to obtain a hardware path to a bootable disk out of a FC interface at BCH?

No there isn't. The BCH SEA utility isn't capable of searching out of a FC interface (probably with good reason - there could be literally *thousands* of LUNs to check for boot images), so you need to tell it the full path to boot to.

As you have already discovered you can do this by booting off DVD/CD and noting the HW path - or if you're smart you can normally work out the hardware path yourself as long as you know what sort of FC switch you're plugged in to and what bus/target/LUN your boot disk is presented at...

On Integrity (IA64) systems, EFI is a little more intelligent in that you can define scan levels for your FC LUNs to keep them short during normal boots, or to enumarate all boot LUNs when configuring new boot paths.

HTH

Duncan

[Steven E. Protter]

Shalom,

I would check the disk replication procedure and see if its supported.

Check the zoning on the SAN and see that the LUN is properly assigned to the WWN of the fiber channel card involved.

SEP

[Torsten.]

As said before, the system at BCH level is not clever enough to find it.

Booting the install media (DVD) is a good way to get this information.

[Daniel A]

Hi Steven,

The replication was between two EVA's 5000 and the zone configuration is dedicated for EVA's and the npars using wwwn's of EVA's and port numbers of card fibre of PA-RISC.

I verify the boot from SAN with this infrastructure and It's supported.

When the LUN replication is finished asign it to the second npar and I force a fail over process, after that I power on the npar and I access to the BCH to try boot.