InfoServer network booting for OpenVMS I64 upgrades is supported
only from the following Integrity servers, which were supported
with OpenVMS Version 8.2. InfoServer network booting is supported
only on certain core I/O LAN cards (also
referred to as LAN devices) on these systems.
rx1600
rx1620
rx2600
rx2620
rx4640
Booting from the InfoServer for OpenVMS I64 on Integrity servers
differs significantly from InfoServer booting for OpenVMS Alpha
systems. For example, while Alpha systems use the Maintenance Operations Protocol
(MOP) to request the primary bootstrap file (APB.EXE) to start the
boot, the Integrity server console uses the Intel® Preboot Execution Environment
(PXE) bootstrap protocol in conjunction with the TCP/IP Services
for OpenVMS BOOTP server and TFTP. The Integrity server EFI console
first loads the primary bootstrap file VMS_LOADER.EFI, which is
formatted for EFI compatibility. VMS_LOADER.EFI then uses TFTP to
request the primary bootstrap IPB.EXE from the boot server.
IPB.EXE is formatted in OpenVMS ODS file structure and is needed
for booting the OpenVMS I64 operating system.
Another major difference between Alpha and I64 InfoServer
booting is that the InfoServer for booting an OpenVMS I64 system
kit is a software application that runs on an OpenVMS system--it
is not an independent hardware system like that used for OpenVMS
Alpha systems. The InfoServer hardware systems are not equipped
to handle DVD drives, so HP designed the InfoServer software application
to perform network boot services for OpenVMS I64 systems.
InfoServer Booting: Differences Between Alpha and I64 Systems summarizes the major differences
between Alpha and I64 InfoServer booting.
Table 1 InfoServer Booting: Differences Between Alpha and I64 Systems
Component
Alpha
I64
Downline load protocol
MOP
PXE (DHCP/BOOTP/TFTP)
Boot file
APB_version (for example,
APB_0821)
VMS_LOADER.EFI and IPB.EXE (both files are
version specific)
Boot server
Any MOP-enabled system with the specified file
Only those BOOTP servers having the network device
MAC address defined in the BOOTP database
LAN server
InfoServer hardware, or InfoServer software application
running on OpenVMS I64 Version 8.2-1 or higher
InfoServer application running on OpenVMS I64
Version 8.2-1 or higher
Because of these differences, any procedures for setting up
InfoServer booting for Alpha systems are not valid for OpenVMS
I64 systems. You must set up your system as an InfoServer client.
In addition, the network administrator must designate and configure
an OpenVMS I64 Version 8.2-1 system in the same LAN to function
as the InfoServer server. The network administrator must also configure
an IP boot server (BOOTP) in the LAN and, with each new version
of OpenVMS I64, update the BOOTP database to point to the newest
version-specific OpenVMS boot files.
Procedure for Enabling InfoServer Network Booting lists the various steps that need to be performed
to enable InfoServer network booting.
Most of these steps need be performed only once. Steps
2 through 4 are usually the responsibility of the network administrator.
Because the OpenVMS I64 boot files are unique for each version
of the operating system, the network administrator must ensure that
the latest boot files are available and referenced in the BOOTP
server database.
Table 2 Procedure for Enabling InfoServer Network Booting
Step
Action
Section
1
Set up your local system as an InfoServer client.
(This procedure can be repeated on any other system in the LAN that
will use the InfoServer server for network booting.)
Set up the TCP/IP Services for OpenVMS BOOTP
server. (For each new release of OpenVMS I64, update the client
entries in the BOOTP database to point to the new version-specific
boot file.) The person responsible for setting up the boot server
needs information about your InfoServer client.
The discussion of InfoServer booting in this manual
pertains to environments where the boot clients and servers are
located in the same LAN. For more complex circumstances, consult
HP Customer Support.
HP OpenVMS Version 8.2-1 for Integrity Servers... 
Setting Up and Performing Network Booting
