vparmodify questions

[KPS]

Hi vPar Folks,

I have an rx8640 and I have one active vPar with an OS on it and then I just created a second vPar that was just created that I need to build via Ignite by pointing the new vPar to my Ignite-UX server over the network.

To do this, I attempted to remove the
"Built-In" LAN Interface (LAN 0) from the active vPar with and OS that originally owned it and then add it via vparmodify to the second vPar just created. I did all this by putting this by changing the mode to NPAR Mode. vparenv -m nPars

It seems the vparmodify command I used to remove the built-in device:

vparmodify -p -d io:1.0.0.1.0

and the vparmodify command i used to add it:

vparmodify -p -a io:1.0.0.1.0

didn't take. I got no errors when I did these vparmodify commands.

Could someone tell met if any of this is possibe and if so, give me any clues as to why this may not have worked?

Thanks,
KPS

[Torsten.]

Hi,

assigning resources works on the LBA level only. Run "ioscan -fn" and locate the LBA entries.

I assume this is in your case "1.0.0" only.


BTW, you don't need to use the core I/O card with this machine - any other NIC may work too.

[KPS]

Okay, now i have another issue then. It seems I have inconsistent information about booting over LAN to go and get an Ignite Image on HP-UX 11.23.

I have tried using other LAN ports to go fetch the Ignite Image on the IGnite server and it doesn't seem to be working. After researching, I found all kinds of threads saying that this can only be accomplished by using the "Built-In" Interface (LAN 0).

Can you or anyone confirm this?

Thanks,
KPS

[Torsten.]

The built-in is recommended in general for PA-RISC systems. You have an Integrity.

But it may depend on other points like subnets.

[KPS]

I have everything in the same subnet.

(Everything meaning Ignite-UX server my new vPar that I plan to install a Golden Image on).

Again, I've tried all available LAN Interfaces to leverage LAN boot to fetch the Ignite Image from our Ignite server.

/etc/bootptab was setup correctly in every attempt with my new client to be ignited listed with the respective MAC Address to the LAN Interface. Since none of this worked, it made me feel that the LAN 0 was my only option.

All of the above is why I'm trying to move the LAN 0 from one vPar to another and that for some reason is not working. Is there any way to refresh the Vpar Database and make it reread the configuration?

Thanks
KPS

[Torsten.]

I installed many many vPars on the same and similar systems all using different NICs - there was never a problem.
Check your ignite servers logs. I assume there is something wrong with the configured IP given to the client?

[KPS]

I think I'm going to stick to my original question about the vparmodify not letting me move the "Built-In" interface from one vPar to another. I can specify 1.0.0 because my boot drives are on that path as well. If I ran vparmodify -p -d io:1.0.0 , that would remove my BOOT and ALT drive that I'm booting from too and I don't want that. Can't I go after just the hardware path of the LAN 0 Built-in Interface on HW Path 1.0.0.1.0??????

BTW, I have no Ignite Logs on my client that I'm trying to image as the OS isn't installed on it yet. I'm trying to initiate the Ignite from the Client. In order to do this, the LAN Interface needs to be bootable. My understanding from what I've read in previous threads and from what I've seen is that the LAN interfaces on LAN PCI Adapters are not bootable.

Looks like I'm still in need if you or anyone else can chime on this ?

[Torsten. · Accepted solution]

Don't read too much other threads but YOURs!

I wrote
Check your ignite _servers_ logs!

You cannot assign resources below the LBA level as you know already.

Did you adjust

/etc/opt/ignite/instl_boottab ?

[Torsten.]

This is the LBA level (example) from ioscan:

ba 0 3/0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (1054)

[IT_2007]

since you are trying to boot second vpar issue the following command:

vpar1::> vparboot -p vpar2 -I

Above command only works to push image from Ignite server to clients for Itanium.

Logon to console and select proper MAC address to boot for client.

You can continue Ignite recovery from Ignite server.

[KPS]

Torsten,

Thanks for your persistence to show me the way here. You are absolutely correct with not needing lan0 to boot over to go get the Ignite-UX Image on the ignite server and this is now working great for me.

My issue, as you suggested to look at was in the /etc/opt/ignite/boot/instl_boottab that was preventing me from igniting over the network.

Thanks very much, I learned alot through this!

KPS

[Torsten.]

You are welcome - have fun!