Installing vPars with Ignite-UX on Integrity




	NOTE: LAN Cards are Used for Boot During Installation on Integrity Systems Unlike vPars on PA-RISC, vPars on Integrity uses the lan card of the target virtual partition for lanboot. Check that your LAN card is supported for boot on 11.23 Integrity systems. For more information, see the HP-UX Virtual Partitions Ordering and Configuration Guide. Also, the I/O card and diagnostic utilities, such as FCFUPDATE and IODIAG.efi, will not operate in `vPars` mode; you must be in `nPars` mode. If you need to update firmware, it will be easier if you do so before booting in vPars mode. For information on modes, see “Modes: Switching between `nPars` and `vPars` Modes (Integrity Only)”.

Prepare the nPartition for Installation of HP-UX by setting the nPartition’s acpiconfig setting to default (for install of HP-UX) and verifying the hardware path of the first virtual partition.
Example:
1. acpiconfig
  Shell> acpiconfig Acpiconfig settings: default
  If you must change the acpiconfig setting from windows to default, you must first enter the acpiconfig default command, and then immediately enter reset to reboot using the new setting.
2. hardware path
  fs0: Acpi(000222F0,915)/Pci(0|0)/Scsi(Pun6,Lun0)/HD(Part1,SigF4250000)

From EFI, boot your system using the Ignite-UX server.

Example:

Shell> lanboot select
   01  Acpi(000222F0,0)/Pci(1|0)/Mac(00306E0E5268)

Select Desired LAN: 1
Selected Acpi(000222F0,0)/Pci(1|0)/Mac(00306E0E5268)
Running LoadFile()
CLIENT MAC ADDR: 00 30 6e 0e 52 68
DHCP
...

NOTE: lanboot information

Note that lanboot will show only the LAN cards that are supported for boot with your existing configuration. If the card(s) you expect to see are not displayed, it may be necessary to issue a reconnect -r at the EFI prompt. Then try lanboot select again.

Example:

Shell> reconnect -r
Shell> map -r

Using the Ignite-UX server, install the necessary bundles.
This includes HP-UX OE, any desired patches, the Quality Pack bundle, the vPars bundle, and any desired vPars-related bundles onto the disk that will be the boot disk of the first virtual partition.
Use ioscan to verify the hardware addresses in your virtual partition plan. You can also save this output since once within a vPars environment, ioscan will only show the hardware that can be seen from the local partition.
# ioscan

Create the virtual partitions using the information you prepared in the virtual partition plan.

Example:

# vparcreate -p keira1 -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 keira2 -a cpu::1 -a cell:1:cpu::1 -a 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 keira3 -a cpu::1 -a mem::1024 -a io:0.0.2 -a io:0.0.0 -a io:0/0/0/3/0.6.0:BOOT

NOTE: If you need to set your ILM or CLM granularity to values different from the defaults, you must do this using the first vparcreate command. For example, the first vparcreate command which creates the vPars database (/stand/vpmon) would be:

# vparcreate -p keira1 -g ILM:1024:y -g CLM:1024:y -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

For more information on granularity values, see “Memory: Granularity Concepts”.

Set the nPartition to boot into vPars mode.
# vparenv -m vPars
Reboot the system and from the EFI Boot Manager, run the EFI shell.
# shutdown -ry 0
From the EFI shell, boot the vPars Monitor and the first virtual partition.
Shell> fs0: fs0:\> hpux HPUX> boot /stand/vpmon vparload -p keira1
From the console of the running virtual partition, if the TERM environment variable is set to unknown, change the TERM environment variable to hpterm. For example, in the POSIX shell the command is.
keira1# export TERM=hpterm
Continuing on the console of the running virtual partition (keira1), perform the following for each remaining virtual partition.
1. Boot the target virtual partition from the running virtual partition using vparboot.
  The syntax for vPars A.05.04 or later versions is:
  # vparboot -p <target_partition> -I [ [-d dbprofile_name]| [-s ignite_ux_server_ip [-c client_ip -g gateway_ip -m subnet_mask] -b boot_file [-o optional_data]]]
  For our example, if the target partition is keira2, execute the following command from keira1:
  # vparboot -p keira2 -I
  or
  vparboot -p keira2 -I -s 17.2.165.152 -c 17.2.163.92 -g 17.2.165.240 -m 255.255.248.0 -b /opt/ignite/boot/nbp.efi -o IINSTALL
  The syntax for vPars A.05.03 or earlier versions is:
  # vparboot -p <target_partition> -I
  For our example, if the target partition is keira2, execute the following command from keira1:
  # vparboot -p keira2 -I
  You will see messages similar to the following:
  <MON> keira2 loaded
2. Type Ctrl-A until you see the console of the target partition.
  [keira2]
3. Select a MAC address from the list to perform a LAN boot.
  01 Acpi(000222F0,0)/Pci(1|0)/Mac(00306E0E5268) Select Desired LAN: 1 Selected Acpi(000222F0,0)/Pci(1|0)/Mac(00306E0E5268) Running LoadFile() CLIENT MAC ADDR: 00 30 6e 0e 52 68 DHCP ...
4. Using the Ignite-UX server, install the necessary bundles.
  This includes HP-UX OE, any desired patches, the Quality Pack bundle, the vPars bundle, and any desired vPars-related bundles.

Your system should now be booted with all virtual partitions up.

Installing vPars with Ignite-UX on Integrity

Technical documentation

» Table of Contents

» Glossary

» Index