VPAR Ignite (boot) Install on PA-RISC and Itanium Systems (HP-UX)

VPARS --- are called the Virtual Partitions.
==============================

Ignite boot of VPARs on PARISC

The VPARs can be installed using an Ignite server on PA-RISC as well as on the Integrity platform.

For this the Basic requirement as on PARISC platform is that of a VPAR that is installed and we can give the command “vparboot –I command”. VPAR MON command vparload can not however cannot be used to install OS on A VPAR.

On PARISC Server while booting from an Ignite-UX server, following is the sequence of steps that take place.

1) The ignite server is contacted via the LAN card of the VPAR from the source VPAR which makes a tftp connection to download WINSTALL and WINSTALLFS from the ignite server and passes the same to the VPMON. VPMON then puts this in the target VPAR Memory.

2) The Target VPAR then boots using the WINSTALL and the WINSTALLFS in the memory and then contacts the Ignite server using its own LAN card for the rest of the Installation.

On an Integrity Server this is Sequence of Steps.

1) On the source VPAR the command vparboot –I is given.

2) This information is passed on to the VPMON.

3) This makes necessary configurations in the EFI of the target VPAR and modifies the variables for the lanboot select.

4) The target VPAR has to be specified with the LAN CARD selection for booting.

5) Once the LAN CARD is selected, the target VPAR makes a tftp to the Ignite server to get the IINSTALL and IINSTALLFS and the rest part of the installation of the OS.

How do we install the VPARS with IgniteUX on the PA-RISC platform? ON PARISC PLATFORM (HP-UX)

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs



ON PARISC PLATFORM:

1) Boot the main NPAR server with the IGNITE server and install the OS onto that.

BCH> boot lan.xx.yy.zz.ww install , where xx.yy.zz.ww is the IP address of the Ignite server.

2) we create the VPAR as per our VPARS data sheet.

#vparcreate –p vpar1 –a cpu::2 –a cpu:::2 –a mem::1024 –a io:0.0.1 –a io:1.0.0 –a io:1/0/0/3/0.6.0:BOOT

#vparcreate –p vpar2 –a cpu::1 –a cell:1::1 – mem::1024 –a io:1.0.1 –a io:1.0.4 –a io:1/0/4/1/0/4/0.1.0.0.0.0.1:BOOT

#vparcreate –p vpar3 –a cpu::1 –a mem::1024 –a io:0.0.2 –a io:0.0.1 –a io:0/0/0/3/0.6.0:BOOT

NOTE: If we have to specify the memory in terms of GLM or CLM then we need to specify this at the time of creating the FIRST VPAR only.

#vparcreate –p vpar1 –G CLM:1024 –g ILM:1024 –a cpu::2 –a mem::1024 –a io:0.0.1 –a io:1.0.0 –a io:1/0/0/3/0.6.0:BOOT'

3) Reboot the system:

#shutdown –r 00

4) Interrupt the booting and from the BCH go to the ISL.

ISL> hpux /stand/vpmon vparload –p vpar1

5) Using the VPAR vpar1 in the booted mode from there Ignite Install all the remaining VPARs one by one. Keep the fact in mind that once we give the vparboot –I command for a VPAR, the source VPAR contacts the Ignite server and tftp downloads the WINSTALL and WINSTALLFS, and the VPMON loads the same into the memory of the target VPAR, which then connects to the IGNITE server for the remaining part of the installation.


vpar1#vparboot –p vpar2 –I xx.yy.zz.ww,/opt/ignite/boot/Rel_B.11.11/WINSTALL

VPMON shows that vpar2 is loaded, go to the Install screen of vpar2 using the CTRL-A and follow the rest part of the installation of the client.

HOW to install the VPARs using the IGNITE server on the INTEGRITY systems (HP-UX)

HOW to install the VPARs using the IGNITE server on the INTEGRITY systems

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs

NOTE: During the Ignite install on a VPAR in the Integrity server the LAN card of the target VPAR is used to boot the VPAR from the IGNITE server.

1) in the EFI shell configure the NPAR for the acpiconfig defaults

SHELL> acpiconfig default

SHELL> reset

To reboot the NPAR with the acpiconfig default setting as such reset has to be given.

Also make a note of the first boot path for the server.

2) Install the OS on the NPAR from an IGNITE server.

SHELL>lanboot select --- select the LAN card to boot over network from the IGNITE server and install the OS on the same. Make sure that VPARs Products also gets installed along with the OS on the system.

Also make a note of the first boot path for the server.

2) Install the OS on the NPAR from an IGNITE server.

SHELL>lanboot select --- select the LAN card to boot over network from the IGNITE server and install the OS on the same. Make sure that VPARs Products also gets installed along with the OS on the system.

3) Now create the VPARs on the server.

Create the FIRST VPAR first, say this one is vpar1.

#vparcreate –p vpar1 –a cpu::2 –a cpu:::2 –a mem::1024 –a io:0.0.1 –a io:1.0.0 –a io:1/0/0/3/0.6.0:BOOT

#vparcreate –p vpar2 –a cpu::1 –a cell:1::1 – mem::1024 –a io:1.0.1 –a io:1.0.4 –a io:1/0/4/1/0/4/0.1.0.0.0.0.1:BOOT

#vparcreate –p vpar3 –a cpu::1 –a mem::1024 –a io:0.0.2 –a io:0.0.1 –a io:0/0/0/3/0.6.0:BOOT

4) Set the system to be booted into the VPARs mode.

#vparenv –m vPars

#shutdown –ry 00

5) As the system comes in the EFI shell, we need to boot the same in the VPARs mode.

SHELL> fs0:

Fs0:>boot /stand/vpmon –p vpar1

vpar1 boots as a VPAR.

6) Install the Other VPARs from the Ignite server.

vpar1#vparboot –p vpar2 –I

This will lead to modify the EFI shell settings for vpar2 and shall execute the lanboot select for the same.

Go to the console of the vpar2 using CTRL-A.

The vparboot command uses the LAN card of the target VPAR vpar2 to contact the ignite server and boot the same from the IGNITE server.

IINSTALL and IINSTALLFS are tftp downloaded from the IGNITE server by the target VPAR LAN card only. 

The booting VPAR connects the IGNITE server using the same LAN card as specified and rest of the installation takes place from there.

Repeat the same steps for the other VPARs also.

How to check and fix the lanboot select or lanboot with a profile fails (HP-UX) | How to Troubleshoot Ignite-UX lanboot problems

 lanboot select or lanboot with a profile fails

1) In the /etc/bootptab file when you enter the clients MAC Address for ha: there is no leading 0x required.

Check the server response from a client in the same network with bootpquery command.

See more on man bootpquery.



2) If TFTP is running in the Ignite-UX sevrer, try to get a file using TFTP from a client in the same network 

make tftp to the Ignite server and try getting the file that is /opt/ignite/boot/nbp.efi and also for /opt/ignite/boot/Rel_B.11.31/IINSTALL and /opt/ignite/boot/Rel_B.11.23/IINSTALLFS --- note well --If i remember the paths correctly.

basically on the ignite server in /etc/inted.conf make sure

tftp 
bootps
instl_boots are uncommented.

make sure that you run #inted -c after you make any changes to /etc/inetd.conf



3) in /etc/services on the ignite server, make sure that you are having ports open for

tftp 69
instl_boots 1067
instl_bootc 1068
bootps 67
bootpc 68 

are free and reachable.


4) also please note that 


/opt/ignite/boot/nbp.efi is intact on the server and also /etc/bootptab can show you that this entry is there as 

bf=/opt/ignite/boot/nbp.efi:\


Also make sure that there is no other competing DHCP server racing with the Ignite server on the network.

How to check and fix the lanboot select or lanboot with a profile fails (HP-UX) | How to Troubleshoot Ignite-UX lanboot problems

 lanboot select or lanboot with a profile fails

1) In the /etc/bootptab file when you enter the clients MAC Address for ha: there is no leading 0x required.

Check the server response from a client in the same network with bootpquery command.

See more on man bootpquery.



2) If TFTP is running in the Ignite-UX sevrer, try to get a file using TFTP from a client in the same network 

make tftp to the Ignite server and try getting the file that is /opt/ignite/boot/nbp.efi and also for /opt/ignite/boot/Rel_B.11.31/IINSTALL and /opt/ignite/boot/Rel_B.11.23/IINSTALLFS --- note well --If i remember the paths correctly.

basically on the ignite server in /etc/inted.conf make sure

tftp 
bootps
instl_boots are uncommented.

make sure that you run #inted -c after you make any changes to /etc/inetd.conf



3) in /etc/services on the ignite server, make sure that you are having ports open for

tftp 69
instl_boots 1067
instl_bootc 1068
bootps 67
bootpc 68 

are free and reachable.


4) also please note that 


/opt/ignite/boot/nbp.efi is intact on the server and also /etc/bootptab can show you that this entry is there as 

bf=/opt/ignite/boot/nbp.efi:\


Also make sure that there is no other competing DHCP server racing with the Ignite server on the network.