The BOOTP boot server for the OpenVMS Integrity servers InfoServer utility can be on the same system or on any system in the same LAN as the InfoServer application for OpenVMS Integrity servers Version 8.3-1H1 and lower. For OpenVMS Version 8.4 onwards, when booting via memory disk, make sure that the BOOTP server and LAN server is the same system. 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. | |
IMPORTANT: You do not have to perform steps 2 and 3 when booting an OpenVMS Integrity servers Version 8.4 or later if boot flags are set to 0,200400. | |
Make sure TCP/IP Services for OpenVMS is installed and that:
At least one IP interface is defined.
The BOOTP server and TFTP server are configured and started.
Optionally, make sure TELNET and FTP are configured and started.
To display IP interface information, use the TCPIP SHOW INTERFACE command.
To verify that the BOOTP and TFTP servers are configured and started, use the HP TCP/IP Services for OpenVMS SYS$MANAGER:TCPIP$CONFIG.COM configuration procedure. From the Main Configuration menu, select option 3 (Server components). If a BOOTP or TFTP service is not enabled and started, select the appropriate server option, and then enable and start the service accordingly. 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. | |
Set up a location for 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:[V831H1]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. | |
Copy the following two files from the DVD to the TCPIP$TFTP_ROOT:[V831H1] directory:
[SYS0.SYSCOMMON.SYSEXE]VMS_LOADER.EFI
[SYS0.SYSCOMMON.SYSEXE]IPB.EXE
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 servers core I/O card):
IP address
MAC address
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=ipaddressThe 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 and verify the assigned IP address, use the TCPIP SHOW HOST command.
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:”, if steps 2 and 3 were performed and VMS_LOADER.EFI and IPB.EXE are copied to the newly created directory. Otherwise, the boot file specification is the complete path for VMS_LOADER.EFI and in the below example, it is in the DVD identified by device DQA0:.
$TCPIP SET BOOTP(For Version 8.3-1H1 and lower)hostname/HARDWARE=ADDRESS=MACaddress-_$/FILE=[V831H1]VMS_LOADER.EFI$TCPIP SET BOOTP(For Version 8.4 and higher)hostname/HARDWARE=ADDRESS=MACaddress-_$/FILE=DQA0:[SYS0.SYSCOMMON.SYSEXE]VMS_LOADER.EFI
You might need to specify a gateway (/GATEWAYS) and network mask (/NETWORK_MASK). To determine the names of the gateways and the subnet information, consult your network administrator. For more information about this command, see the TCP/IP Services for OpenVMS documentation. To display and verify your BOOTP server configuration, use the TCPIP SHOW BOOTP/FULL command.
IMPORTANT: For each new version of OpenVMS Integrity servers, you must modify the client entry in the BOOTP database to point to the new, version-specific boot file. | |
Example 2 shows the commands for setting up a boot server for a client named MOZART. An explanation of each command follows the example.
Setting Up the Boot Server and Client (for Version 8.3-1H1 and Lower)
$(1)CREATE/DIRECTORY TCPIP$TFTP_ROOT:[V831H1]$COPY DQA0:[SYS0.SYSCOMMON.SYSEXE]VMS_LOADER.EFI TCPIP$TFTP_ROOT:[V831H1]VMS_LOADER.EFI(2)$COPY DQA0:[SYS0.SYSCOMMON.SYSEXE]IPB.EXE TCPIP$TFTP_ROOT:[V831H1]IPB.EXE(3)$TCPIP SET HOST MOZART/ADDRESS=1.1.110.117(4)$TCPIP SET BOOTP MOZART/HARDWARE=ADDRESS=00-13-21-5B-85-E4 -_TCPIP>/FILE=[V831H1]VMS_LOADER.EFI(5)$TCPIP SHOW HOST MOZART(6)BIND Database Server: 1.1.128.41 Host address Host name 16.32.110.117 MOZART...$TCPIP SHOW BOOTP MOZART/FULL(7)Host: 1.1.110.117 mozart Hardware Address: 00-13-21-5B-85-E4 Network mask: 255.0.0.0 Type: Ethernet File: [V831H1]VMS_LOADER.EFI Time offset: 0 Vendor: ACME, Inc. Gateways: not defined Servers: . . .
| (1) | Creates the directory TCPIP$TFTP_ROOT:[V831H1] on the system to be the TFTP and BOOTP server. |
| (2) | Copies [SYS0.SYSCOMMON.SYSEXE]VMS_LOADER.EFI from the DVD to TCPIP$TFTP_ROOT:[V831H1]. |
| (3) | Copies [SYS0.SYSCOMMON.SYSEXE]IPB.EXE from the DVD to TCPIP$TFTP_ROOT:[V831H1]. |
| (4) | Adds the boot client host MOZART to the TCP/IP hosts database, specifying MOZART’s IP address as 1.1.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 Section ) and the boot file for the client is [V831H1]VMS_LOADER.EFI. |
| (6) | Displays information about the boot client MOZART as stored in the local host database (use this command to verify that the client has been configured appropriately). |
| (7) | Displays information about the boot client MOZART as stored in the BOOTP database (use this command to verify that the client has been configured appropriately). |
Setting Up the Boot Server and Client (for Version 8.4)
$(1)TCPIP SET HOST MOZART/ADDRESS=1.1.110.117$TCPIP SET BOOTP MOZART/HARDWARE=ADDRESS=00-13-21-5B-85-E4 -$_TCPIP> /FILE=DQA0:[SYS0.SYSCOMMON.SYSEXE ]VMS_LOADER.EFI(2)$$ TCPIP SHOW HOST MOZART(3)BIND Database Server: 1.1.128.41 Host address Host name 16.32.110.117 MOZART...$TCPIP SHOW BOOTP MOZART/FULL(4)Host: 1.1.110.117 mozart Hardware Address: 00-13-21-5B-85-E4 Network mask: 255.0.0.0 Type: Ethernet File: [DQA0: [SYS0.SYSCOMMON.SYSEXE ]VMS_LOADER.EFI Time offset: 0 Vendor: ACME, Inc. Gateways: not defined Servers: . . .
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 on performing the InfoServer boot are in Section . A troubleshooting section is included in Section .