HELP: vpar0 running / vpar1 not--need mac address from LAN on vpar1--HOW?

[Craig A. Sharp]

I have two vpars...vpar0 is up and running. vpar1 is not loaded yet, but it is configured. I need to get the mac address from the nic on vpar1 so I can ignite the partition. I see no way to do this from vpar0. I have also looked in the MP, but also see no way to get the MAC that I need.
I am running a two cell 7420.

The MAC addresses are not listed on the physical cards.

Oh ya, vpar0 is in production :-)

[Pete Randall]

If you boot the machine without VPARs, you'll be able to see all the hardware. At the ISL prompt, instead of loading vparmon, do a normal "hp-ux -is" and you'll come up without the partitions blocking your view of the other hardware. Do a full ioscan and print it out so you can save it.


Pete

[IT_2007]

Don't worry about MAC address. you just initiate boot process using vparboot pointing to Ignite server to load image. As soon as you see a list of MAC addresses for vpar2 then chose first one and then link that MAC on ignite server to load. If it fails go for second one and test it and so on.

[Craig A. Sharp]

I need to boot from a helper...so how am I going to do this from the MP?

[Craig A. Sharp]

Better yet, can I point vparboot to the helper and if so how?

[IT_2007]

Don't ahve to reboot whole Npar. Since vpar0 is up and running and also vapr1 configured. Then you can proceed what I said in my earlier post. I have done this many times.

[Craig A. Sharp]

What is the command to vparboot vpar1 from the helper?

[IT_2007]

You can't boot vpar1 with boot helper unless you have latest Vpar software which supports Tape. do you?

you said vpar0 is up and running, correct?

where is your Ignite image?

do this way.

vpar0: # vparboot -p vpar1 -I :/opt/ignite/boot/WINSTALL

which will initiate booting vpar1 and trying to contact Ignite server to get image of vpar1.

[Craig A. Sharp]

Yes I have the latest...the ignite is on a different subnet so I have a helper server...

[IT_2007]

Yes I have the latest...the ignite is on a different subnet so I have a helper server...
========================

You are initiating boot from vpar0 so it should work for your case. Go ahead and initiate boot and then login to GSP and do CTRL-A to access vpar1 ignite installation menu.

[Craig A. Sharp]

Sorry vpar0 is running....vpar1 is not loaded

[IT_2007]

So did you run this way or not? Also did you check on the console?

vpar0: # vparboot -p vpar1 -I :/opt/ignite/boot/WINSTALL

Please post output.

do you have hardware in place and assigned to vpar1? Please post vparstatus -v output.

[Craig A. Sharp]

yup all hardware is in place and ready to go...I just need to boot the thing through the helper. Do I put the IP of the actual ignite server or the IP of the helper into the command?

[IT_2007]

You need to specify Ignite server IP address. Please see the syntax and also you need to put : after IP address in the vparboot command.

[Kevin Wright]

if you IP of the ignite server is on a different subnet, you need to boot off of your bootp server on the local LAN.

[Craig A. Sharp]

Quite right...this is where I am lost...I need to vparboot vpar1 from the boot helper...how do I correctly format the vparboot command to pickup the helper?

vparboot -p vpar1 -I :/opt/ignite....???

This does not work.

[IT_2007]

ok. If you have latest and greatest Vpar software installed then vparboot should support boot helper. Do you know hardware address for it? Did you assign tape drive to vpar1? If yes, then it may be something like:

vparboot -p vpar1 -B

[Craig A. Sharp]

the boot helper is a different server on the same lan...there is no hardware address.

[IT_2007]

Ok. If it is on the same subnet then you just boot as

vparboot -p vpar1 -I :/opt/ignite/bin/WINSTALL

once you get gui, you can point to real Ignite server name.

[Craig A. Sharp]

I ended up calling HP....the : is supposed to be a ,

I changed it and it worked perfectly!

Thanks to all for your help...I will.assign points..

[Craig A. Sharp]

We are loaded! Thanks to all for your answers