HP OpenVMS Systems Documentation

Content starts here
HP OpenVMS Version 8.3 Upgrade and Installation Manual > Appendix C Setting Up and Performing Network Booting

Setting Up the BOOTP Boot Server (I64 Only)

  Table of Contents

  Glossary

  Index

The BOOTP boot server for use with the OpenVMS I64 InfoServer utility can be on the same system or on any system in the same LAN as the InfoServer application. TFTP is required on the boot server for supplying the boot files to the client systems.

The steps necessary to set up the boot server and boot files are as follows:

NOTE: All instructions and examples assume the use of TCP/IP Services for OpenVMS. Other IP products might work but have not been tested and are not supported at this time.
  1. Make sure TCP/IP Services for OpenVMS is installed and that:

    • The BOOTP server and TFTP server are configured and started.

    • At least one IP interface is defined.

    • Optionally, make sure TELNET and FTP are configured and started.

    Use the TCPIP SHOW SERVICES command to verify the servers are started (enabled), and the TCPIP SHOW INTERFACE command to display IP interface information. For more information about configuring and starting TCP/IP Services for OpenVMS components, see the HP TCP/IP Services for OpenVMS Installation and Configuration and HP TCP/IP Services for OpenVMS Management manuals.

    NOTE: If you are currently using the DHCP service, you must disable it. The BOOTP service must be enabled instead. For information about disabling or enabling services, see the HP TCP/IP Services for OpenVMS Management manual.
  2. Set up a location for the OpenVMS I64 Version 8.3 boot files by creating the directory accessible by TFTP, as in the following example. (HP recommends that you create a separate boot file directory for each version of the operating system.)

       $ CREATE/DIRECTORY TCPIP$TFTP_ROOT:[V83]
    IMPORTANT: For each subsequent upgrade of OpenVMS, you must create a separate directory for the boot files specific to the OpenVMS version and, where appropriate, modify the path specified for each client’s boot files (as in step 6). To make subsequent upgrades easier, you can use systemwide or clusterwide logical names.
  3. Copy the following two files from the DVD to the TCPIP$TFTP_ROOT:[V083] directory:

    • [SYSEXE]VMS_LOADER.EFI

    • [SYSEXE]IPB.EXE

  4. Gather data for each boot client (that is, each node that is going to boot the DVD over the network), including the following information for the client’s network device (the client Integrity server core I/O card):

    • IP address

    • MAC address

  5. Define each boot client’s host name in the TCP/IP Services for OpenVMS local host database using the TCPIP SET HOST command. In the following example, hostname is the host name of the boot client and ipaddress is its IP address.

             $ TCPIP SET HOST hostname/ADDRESS=ipaddress

    The IP address does not have to be the actual address you plan to use for the boot client host; it must be in the same LAN as the BOOTP server and must not be currently in use. However, if you use statically assigned IP addresses, HP recommends (for simplicity) using the assigned address of the boot client’s network device. (To display the assigned IP address, use the TCPIP SHOW HOST command.)

  6. For each boot client, add an entry in the BOOTP database to associate the MAC address of the client’s LAN device with the boot file to be loaded from the boot server, as in the following example. In this example, hostname is the host name of the boot client, and MACaddress is the client’s MAC address in the format xx-xx-xx-xx-xx; the boot file specification need not include “TCPIP$TFTP_ROOT:”.

            $ TCPIP SET BOOTP hostname /HARDWARE=ADDRESS=MACaddress- 
    _TCPIP> /FILE=[V083]VMSLOADER.EFI

    You might need to specify a gateway (/GATEWAYS) and network mask (/NETWORK_MASK). Consult your network administrator or see the TCP/IP Services for OpenVMS documentation.

    IMPORTANT: For each new version of OpenVMS I64, you must modify the client entry in the BOOTP database to point to the new, version-specific boot file.

Example C-1 “Setting Up the Boot Server MOZART and Client” shows the commands for setting up a boot server for a client named MOZART.

Example C-1 Setting Up the Boot Server MOZART and Client

   [1] $ CREATE/DIRECTORY TCPIP$TFTP_ROOT:[V083]
[2] $ COPY DQA0:[SYSEXE]VMS_LOADER.EFI TCPIP$TFTP_ROOT:[V83]VMS_LOADER.EFI
[3] $
COPY DQA0:[SYSEXE]IPB.EXE TCPIP$TFTP_ROOT:[V83]IPB.EXE
[4] $
TCPIP SET HOST MOZART/ADDRESS=16.32.110.117
[5] $
TCPIP SET BOOTP MOZART/HARDWARE=ADDRESS=00-13-21-5B-85-E4-
_TCPIP> /FILE=[V83]VMSLOADER.EFI

[6] $
TCPIP SHOW HOST MOZART/FULL

Host: 16.32.110.117 MOZART
Hardware Address: 00-13-21-5B-85-E4
Network Mask: 255.0.0.0
File: [V83]VMS_LOADER.EFI
.
.
.

The commands shown in Example C-1 “Setting Up the Boot Server MOZART and Client” perform the following functions:

  1. Creates the directory TCPIP$TFTP_ROOT:[V83] on the system to be the TFTP and BOOTP server.

  2. Copies [SYSEXE]VMS_LOADER.EFI from the DVD to TCPIP$TFTP_ROOT:[V83].

  3. Copies [SYSEXE]IPB.EXE from the DVD to TCPIP$TFTP_ROOT:[V83].

  4. Adds the boot client host MOZART to the TCP/IP hosts database, specifying MOZART’s IP address as 16.32.110.117.

  5. Adds host MOZART as a client entry in the BOOTP database, where the MAC address of the client’s LAN device is 00-13-21-5B-85-E4 (as was determined in the example for the client in “Determining the Local Network I/O Card to Be Used ”) and the boot file for the client is [V83]VMS_LOADER.EFI.

  6. Displays information about the client MOZART (use this command to verify that the client has been configured appropriately).

After you complete these steps, in addition to the required steps in the preceding sections, you can boot a client over the network using the InfoServer application. Instructions for performing the InfoServer boot are in “Booting from the InfoServer”. A troubleshooting section is included in “Troubleshooting InfoServer Boot Problems”.