setboot, alternate boot path

[silusan]

it is a vm host, 11.31

primary boot path is disk

need to set a LAN interface, lan0 as the alternate boot path.

please suggest, how.

used this this LAN interface (lan0) for installing / restoring the image from ignite.

#> setboot

Primary bootpath : 0/0/0/1/0/0/0.0x0.0x6000000000000000 (/dev/rdisk/disk8)

HA Alternate bootpath :

Alternate bootpath :

Autoboot is ON (enabled)

Hyperthreading : ON :

ON (next boot)

#

#> setboot -a 0/0/0/3/0/0/0
setboot: error accessing boot path - Invalid argument
setboot: Check if boot path is to a valid boot device
#

#> setboot -a 0/0/0/3/0/0/0:ALTBOOT

setboot: "0/0/0/3/0/0/0:ALTBOOT" is not a valid bootpath. Bootpaths should be specified with a persistent dsf, lunpath hardware path or a legacy hardware path.

#>

 #> ioscan -fnC lan
Class     I  H/W Path       Driver S/W State   H/W Type     Description
========================================================================
lan       0  0/0/0/3/0/0/0  iexgbe   CLAIMED     INTERFACE    HP  PCIe 2-p 10GbE Built-in

P.S. This thread has been moved from HP-UX > General to HP-UX > virtualization. - Hp Forum Moderator

[Torsten.]

It may be better to use "lanboot select" and use a boot profile, depending on your environment.

[silusan]

do you mean. while installing etc?

yes we did that while restoring a backup image from ignite recently dbprofile name IGNITE

Shell> lanboot select -dn IGNITE

but now what we need is... to have an alternate boot path set as it is in our rest of the vmhosts in our enviroment.

for example...

in another vmhost it is like this

another vmhost > # setboot

Primary bootpath : 0/0/0/1/0/0/0.0x0.0x7000000000000000 (/dev/rdisk/disk8)

HA Alternate bootpath :

Alternate bootpath : 0/0/0/3/0/0/0 (LAN Interface)

Autoboot is ON (enabled)

Hyperthreading : ON               

                                 : ON (next boot

we need it like the above output.

[Robert_Jewell]

While you cannot use the setboot command to set a LAN interface as a boot path, you can use the EFI Boot Manager to arrange the order of the boot options so that the LAN interface is next in line after the primary boot device.

-Bob

[silusan]

yes, when setboot -a 0/0/0/3/0/0/0 didnt work, then I rebooted the vmhost...

interrupted boot

Press:  ENTER  -  Start boot entry execution
        B / b  -  Launch Boot Manager (menu interface)
        D / d  -  Launch Device Manager (menu interface)
        M / m  -  Launch Boot Maintenance Manager (menu interface)
        S / s  -  Launch UEFI Shell (command line interface)
        I / i  -  Launch iLO Setup Tool (command line interface)

boot options, add a boot option and selected 'other device', selected lan0 with its MAC address as another boot option.. (attached a picture)

save and commited changes...

and booted with the primary boot disk as usual.

but setboot didnt show alt boot path...not even after another normal reboot!

Any help would be greatly appreciated..pls

regards

[Robert_Jewell]

I just performed the same task and was able to acheive what you are looking for.

Before I made the change my setboot output looked like the following:

# setboot
Primary bootpath : 0/0/0/2/0/0/0.0x0.0x4000000000000000 (/dev/rdisk/disk3)
HA Alternate bootpath :
Alternate bootpath :

Autoboot is ON (enabled)
Hyperthreading : OFF
               : OFF (next boot)

I rebooted the host, went into the Boot Maintenance Manager menu, selected Boot Options and changed the Boot Order so that "Core LAN 1" was second in the list.  After booting back up, I run setboot and show the following:

# setboot
Primary bootpath : 0/0/0/2/0/0/0.0x0.0x4000000000000000 (/dev/rdisk/disk3)
HA Alternate bootpath : 0/0/0/3/0/0/0 (LAN Interface)
Alternate bootpath :

Autoboot is OFF (disabled)
Hyperthreading : OFF
               : OFF (next boot)

Perhaps you did not save the changes?  I would try it again.

-Bob

[silusan]

Thanks Bob, thats encouraging, really.

I remember I commited the changes though.

No harm in trying it once again...will try once again tomorrow.

Noticed a difference in yours

autoboot was ON earlier, now it is OFF

also,.

yours: hyperthreading :off

mine: hyperthreading :on

[silusan]

Bob

While installing OS in this vm host, I used lan0 ( 0/0/0/3/0/0/0 ), I saved that boot option as "test"

recently used this same boot option while restoring a complete backup.

Now inorder to set 0/0/0/3/0/0/0 as alt boot path , when I selected this path again...it got saved as "boot004"

it was like this when I checked

primary boot - (boot disk path)

iLO virtual Flash

iLO DVD

test

boot004

I deleted test and boot004

Then I added a boot option with the same MAC ID (as 0/0/0/3/0/0/0), it got saved as boot002 this time.

Also, I changed the boot order and it looked like this

primary boot - (boot disk path)

boot002

iLO virtual Flash

iLO DVD

then booted

then it turned up like this...

#> setboot

Primary bootpath : 0/0/0/2/0/0/0.0x0.0x4000000000000000 (/dev/rdisk/disk1)

HA Alternate bootpath : 0/0/0/3/0/0/0 (LAN Interface)

Alternate bootpath :

Autoboot is ON (enabled)

Hyperthreading : ON

               : ON (next boot)

#>

This is wrong as far my environment is concerned.. that LAN should be at ALT BOOT PATH not at HA ALT BOOT PATH.

But thats encouraging as I some how got LAN interface to be published in setboot command :-)

Do you think any reason why this is at HA ALT BOOT PATH...not at ALT BOOT PATH?

Can we fix this?

[silusan · Accepted solution]

earlier

primary boot - (boot disk path)

boot002

iLO virtual Flash

iLO DVD

changed the boot order as

primary boot - (boot disk path)

iLO virtual Flash

boot002

iLO DVD

then setboot was set as per my requirement

Nothing against HA Alternate Bootpath

LAN interface showed up @ Alternagte bootpath

Hence solved

Many thanks for those who read, replied and those who tried to reply

cheers