An HP ProLiant Essentials Rapid Deployment Pack (RDP) boot server
may be configured to act as an HP-UX boot helper. You can do this
by adding RDP MenuOptions for the initiation of HP-UX boot for install
and placing the Ignite install environment on
the RDP server. The RDP server may then be used to initiate an Ignite-UX
installation of HP-UX.
To set up boot for HP-UX installation, use the PXE Configuration
Utility to create the necessary MenuOptions and copy the Ignite install
environment content into the proper locations on the RDP server.
The PXE Configuration Utility program is typically located on
the RDP server at
C:\Program Files\Altiris\eXpress\Deployment Server\PXE\PxeConfig.exe |
 |
Setting up RDP MenuOptions via Windows Commands |
|
A Windows command line may
be used to automate Ignite support set up. To create a MenuOption
on an RDP server for HP-UX installation, or to update it with new
Ignite install environment content, the following
command line arguments may be used:
PxeConfig.exe -create -other "HP-UX Managed" -ia64 \
-pathia64 <ignite_content_dir> -save |
The ignite_content_dir directory needs to contain the following HP-UX boot and Ignite install
environment files:
.\MenuOption160.0 (nbp.efi renamed as required by the RDP server)
.\MenuOption161.0 (nbp.efi renamed as required by the RDP server)
.\MenuOption162.0 (nbp.efi renamed as required by the RDP server)
.\MenuOption163.0 (nbp.efi renamed as required by the RDP server)
The RDP server requires the file name of the initial boot loader
file and the name of the MenuOption to match. Normally, MenuOption160 will be used by the RDP server. However,
if there are existing custom MenuOptions, another file name might
be required. Copying the small nbp.efi boot loader
to the first few custom MenuOption names the PXE Configuration Utility
uses for MenuOptions should simplify the automatic set up of the RDP
server. For HP-UX, this file is actually the nbp.efi network boot loader.
The Ignite-UX version for this content on the RDP server must
be kept consistent with the Ignite-UX product version on the Ignite
server. Note that IINSTALLFS includes config file content typically modified
via use of instl_adm. Since these files will reside
on the RDP server, a data center administration process for updating
these files should be created to keep the RDP files consistent with
the Ignite server.
The Ignite install environment on the
RDP server needs to be updated when:
The IINSTALLFS config content
is changed
A new version of Ignite software is installed on the
Ignite server
Changes are made to the AUTO file boot menu
The HP-UX boot loader is patched
Setting up RDP MenuOptions via Interactive UI |
|
The RDP server
PXE Configuration Utility may be used to interactively create a MenuOption
for HP-UX boot and Ignite installation.
Before starting the interactive UI, put the Ignite-UX boot and install environment files in a directory as specified
in “Setting up RDP MenuOptions via Windows Commands”. Any convenient method may be used to transfer the required content
from the Ignite server to the RDP server (FTP, Samba share, key chain
drive, etc.). You should consider how this content will be updated
in the future to stay consistent with the Ignite server.
The Interactive UI may be started using the Windows Start Menu:
Start
All ProgramsAltirisPXE ServicesPXE Configuration Utility
It may also be started from the RDP Deployment Solutions Console.
Once started, the PXE Configuration Utility will display a window
similar to the following:
On the Boot Menu tab, select
the New... button to create a MenuOption
for HP-UX boot and installation.
You should validate that the selected MenuOption number in the
Final Location on PXE Server text box is consistent with the HP-UX
Ignite content provided.
Configure the MenuOption as follows:
Enter the name of the MenuOption to be created in
the Name: text box.
For HP-UX, the name “HP-UX
Managed” is recommended. If HP-UX release-specific MenuOptions
are created by using different AUTO content, a name such as “HP-UX 11.31 Managed”
is recommended.
Configure the Pre-boot Image Properties.
Select Operating System type Other.
Select only the ia64 Processor Option, since HP-UX
only supports ia64 systems. Make sure x86 and x64 are unselected.
Select User supplied for the Image Creation Method,
and then select Manual Boot Image. In the PXE Boot Files text box, enter the directory containing
the Ignite-UX boot and install environment files,
then select OK.
Select OK from the
New Shared Menu Option dialog box.
Select Save on the
Boot Menu tab of the PXE Configuration Utility – Shared Configuration
menu.
|
| |
|
 | IMPORTANT: You must select Save to enable
the new boot menu option before selecting OK to exit. |
|
| |
|
Once set up is complete, the PXE Configuration Utility will
show the new MenuOption for HP-UX.
Using an RDP MenuOption for HP-UX |
|
Once the HP-UX MenuOption is set up using either the PXE
Configuration Utility command or UI, the RDP PXE server will include
“HP-UX Managed” as an option during network boot of
ia64 client systems.
When a client system is booted from an RDP PXE server, the system
will prompt you to “Press [F8] to select a boot option.”
When booting on a serial console, function keys are typically not
available. The m key may be used to bring up the
boot menu instead of the F8 function key.
Loading.: Core LAN Gb A
Running LoadFile()
CLIENT MAC ADDR: 00 30 6E 4C AA A5
CLIENT IP: 10.1.1.100 MASK: 255.255.255.0
DHCP IP: 10.1.1.22 PROXY IP: 10.1.1.22
GATEWAY IP: 10.1.1.1
Press [F8] to Select a boot option: iuxrdp (9)
Linux Managed
Next Device (BIOS/EFI)
HP-UX Managed |
Printable version
