Boot from san

[san2]

Hi,

I am going to migrate boot from san devices which are on dmx-2 to clariion using san copy.
After doing migration using san copy , do we need to change any settings to make clariion devices bootable.

OS : HP UX 11.11
HBA: HP 6795A

Doing migration from dmx-2 to cx-4 clariion.

Please help me.

Vikas

[Patrick Wallek]

I would not use san copy functions to do this. Your device files will change which could cause you sever grief with your boot devices.

What I would do instead is set up the new LUNs on the Clariion array and make sure that you can see them on your server.

I would the mirror your boot devices to the new SAN following standard mirroring procedures. Once the mirroring to the new SAN is complete and you verify that they work, then you can reduce the mirrors from the old DMX array.

[san2]

The copy of data and boot LUNs has to be done using SAN Copy solution then how do we boot the HP-UX server from Clariion boot device. Once the copy is done using san copy and once the device number changed (clariion) which was intially dmx devices. What setting has to be done so that hp-ux server can boot from clariion devices.

Appreciate your reply

[Torsten.]

See

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1140093

You need to change

EFI Variable EFIFCScanLevel

for the FC HBA at EFI level.

[Duncan Edmonstone]

Torsten,

>You need to change
>
>EFI Variable EFIFCScanLevel
>
>for the FC HBA at EFI level.

No he doesn't - this is PA-RISC (he mentions 11.11)

Vikas,

Not an easy task but do-able... I'd approach it this way.

1) Make sure you have an Ignite Backup (nice to have a fall-back position for re-installing if possible.)

2) Run SAN copy. And present new boot disks to HP-UX host.

3) Now you need to identify the hardware path of your new boot device. If you still have the host up and both the DMX and Clariion devices attached and presented you can just use ioscan to identify them. However If you've taken the DMX devices away, then you can't just boot up to an OS until you know the new hardware paths -you'll find that you can't scan for boot devices out of FC cards at the PDC prompt on HP-UX, so unless you're a dab hand at figuring out FC hardware paths from FC switch and disk array configurations you'll find the easiest thing to do will be to use a DVD/CD and boot the system to a recovery shell, then use ioscan to identify the hardware path of your new primary boot path (presumably to your primary controller on the clariion)

4. Reboot again and at PDC prompt enter the new hardware path to boot from and then boot to LVM maintenance mode.

5. In LVM maintenance mode vgexport the root VG and then vgimport it again with the new primary boot path. Remember to update boot/swap/dump links using lvlnboot and to set the new primary boot path using setboot.

6. This should now get you back to being able to boot from your primary path. What you do with your alternate path depends on what failover settings you're using on the Clariion and whether you are using PV links or PowerPath, I'd suggest you talk to EMC about how to configure that.

HTH

Duncan

[Torsten.]

You are right Duncan, I did not noticed that for any reason.

IMHO the easiest way to find the path is just booting an install media (DVD/CD/IGNITE), then all available disks including path are displayed in the installer window (in details view).

[Steven E. Protter]

Shalom,

Booting HP-UX from any disk array introduces reliability problems. It would be better to migrate boot back to local disk and use the disk array as a backup.

SEP

[Torsten.]

"Booting HP-UX from any disk array introduces reliability problems."

I don't think so.

Let's take a vPar system. You need several (pairs) of boot disks. You cannot use more than 1 or maybe 2 local internal disk pairs. Others must be external. If you have a big iron with let's say 20 vPars, you need 40 external enclosures to be on a safe side - overkill!

On the other hand if you want to have a secure environment you can use 2 independent arrays and mirror them.

If you have no access from the server(s) to both arrays through 2 HBAs and 2 switches and usually redundant array controllers you have a much bigger problem than an unbootable server ...

;-)

[san2]

Reboot again and at PDC prompt enter the new hardware path to boot from and then boot to LVM maintenance mode.

Please let me know how to find boot path with command syntax.

5. In LVM maintenance mode vgexport the root VG and then vgimport it again with the new primary boot path. Remember to update boot/swap/dump links using lvlnboot and to set the new primary boot path using setboot

How to update boot/swap/dump links using lvlnboot and to set the new primary boot path using setboot?

[Eric SAUBIGNAC]

Bonsoir,

"Please let me know how to find boot path with command syntax"

At PDC enter "SEARCH". To boot, choose the right boot path from previous output then enter BO followed by this path. Then interrupt automatic boot process with any key to start manually an lvm maintenance boot (HPUX -lm)

"How to update boot/swap/dump links using lvlnboot .../..."

Activate the root VG you have just imported and use command "lvlnboot -R"

".../... and to set the new primary boot path using setboot?

use command "setboot -p" followed by the path you used to boot the system from PDC.

Also "man" is really usefull ;-)

Eric

[Torsten.]

>>"At PDC enter "SEARCH"."

This will not find any SAN LUNs - only local connected devices.

Follow the advices from the earlier posts.

[Eric SAUBIGNAC]

You are probably right Torsten, but it seemed to me that on PA-RISC command SEARCH was able to scan SAN devices, unlike Itanium if you don't modify FC card setting. Shame on me :-( I would say that I have not seen a PA-RISC for a while ...

[Torsten.]

It finds something


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
----- ----------------- ----------- ----
P0 1/0/0/3/0.6 Random access media 4
P1 1/0/0/3/1.2 Random access media 4
P2 1/0/1/1/0/1/1.6 Random access media 4
1/0/4/1/0/4/0.0 Fibre Channel Protocol 14


This is the adapter only.

fc 1 1/0/4/1/0/4/0 fcd CLAIMED INTERFACE HP A9784-60002
PCI/PCI-X Fibre Channel FC/GigE Combo Adapter (FC Port 1)
/dev/fcd1


I get nothing else.

[Eric SAUBIGNAC]

You pointed it Torsten and now I remember : SEARCH shows only the FC card. But if you know in adavance the whole path of the LUN in the SAN (I mean HP-UX like path), you will be able to boot if search has correctly shown the card.

Anyway, you was perfectly right : beginning an install process, with whatever method, is the simplest way to find the path when you have few knowledge of what you are playing with ...