Appendix B Setting Up and Performing Network Booting

Determine the LAN I/O card to be used on your local Integrity server for the network boot. Report the associated OpenVMS device name and its IP address and MAC address to the network administrator responsible for setting up the BOOTP server.

Optionally (and recommended), add the network device as a boot option in the EFI Boot Manager menu.

Verify that the network device is supported by EFI as a bootable device.

Copy SYS$STARTUP:ESS$LAD_STARTUP.TEMPLATE to ESS$LAD_STARTUP.DAT (save the ESS$LAD_STARTUP.TEMPLATE file as a backup).

Edit SYS$STARTUP:ESS$LAD_STARTUP.DAT to modify parameters as needed. This file configures InfoServer parameters affecting the OpenVMS LASTport/Disk™ (LAD) server, which allows access to the DVD drive. The following is an example of the configuration file (with default settings):

!++
! ESS$LAD_STARTUP.TEMPLATE
!
! Copy this file to SYS$STARTUP:ESS$LAD_STARTUP.DAT and edit it
! to suit your local situation.
!
! This file is used by SYS$STARTUP:ESS$LAD_STARTUP.COM to set up
! the parameters for the InfoServer Application on OpenVMS
! LASTport/Disk (LAD) server.
!
! Note:
! The LAD disk block cache is structured as a number of fixed-size
! buckets.  You must specify both the bucket size and the number of
! buckets for the cache.
!
! The LAD cache is allocated from non-paged pool and is in no way
! associated with the XFC cache. The total LAD cache size in bytes
! may be determined by the formula:
!
! cache-bytes = bucket-size-in-blocks * number-of-buckets * 512
!
! Be sure the SYSGEN parameters NPAGDYN/NPAGEVIR are sized appropriately.
!
! The following keywords with values are accepted by this procedure:
!
!       BUFFER_SIZE -   A number between 3 and 8 denoting the
!                       bucket size in blocks as follows:
!                       3 -   8 blocks
!                       4 -  16 blocks
!                       5 -  32 blocks
!                       6 -  64 blocks
!                       7 - 128 blocks
!                       8 - 256 blocks
!       CACHE_BUCKETS - Number of buckets
!       MAXIMUM_SERVICES - Maximum number of services (max=1024)
!       WRITE_LIMIT -   Server wide count of asynchronous writes
!--

BUFFER_SIZE = 3         ! default (8 block buckets)
CACHE_BUCKETS = 512     ! Default setting
WRITE_LIMIT = 0         ! No async writes
MAXIMUM_SERVICES = 256  ! default (typically more than enough)

The following table provides a short description of each of the parameters:

	NOTE: As indicated in the file comments, the LAD cache comes out of nonpaged pool. If you increase the cache significantly, you might need to increase the nonpaged pool SYSGEN parameters (NPAGEDYN and NPAGEVIR).

Determine which network device will be used for InfoServer LAD operations. You can use any network device that is visible to OpenVMS. Typically, any network device that works with DECnet or TCP/IP Services for OpenVMS should work. Use the LANCP command SHOW CONFIGURATION to determine which device to use, as described in Section B.2.1.

For this release of OpenVMS, the LASTport protocol runs on only a single network device. To enable this device, copy the SYS$STARTUP:ESS$LAST_STARTUP.TEMPLATE file to the SYS$STARTUP:ESS$LAST_STARTUP.DAT file, and then open the SYS$STARTUP:ESS$LAST_STARTUP.DAT file and make the following changes:

1. Remove the comment character (!) from the line that has the following text: DEVICE = (). Within the parentheses, specify the device name. For example: DEVICE = (EIA).

2. Comment out the line that specifies ALL_CONTROLLERS = ON (comment out a line by inserting an exclamation point (!) at the beginning of the line).

The following example shows the SYS$STARTUP:ESS$LAST_STARTUP.DAT file with the suggested changes made (shown in bold):

!++
 ! This file will be used to set the appropriate LASTCP qualifiers. The following
 ! LASTCP qualifiers: ALL_CONTROLLERS, CHECKSUM, TRANSMIT_QUOTA, or SLOW_MODE
 ! can be set by using the following statement format:
 ! LASTCP qualifier = 1 to enable   e.g. SLOW_MODE = 1 enables  SLOW_MODE
 ! LASTCP qualifier = 0 to disable  e.g. SLOW_MODE = 0 disables SLOW_MODE
 ! The remaining LASTCP qualifiers will require the appropriate value settings.
 DEVICE          = (EIA)    ! Uncommented; device name specified
 ! TIMEOUT         = n                           minimum interval in seconds
 ! CIRCUIT_MAXIMUM = n                           maximum number of nodes
 ! GROUP           = n                           Group number
 ! NODE_NAME       = name                        Node name
 ! CONTROLLERS     = ([{controller letter,}...]) Controller list
 ! TRANSMIT_QUOTA  = n                           Number of transmit buffers
 !--
 !ALL_CONTROLLERS = ON      ! Commented out

Add the following line to the system startup file SYS$MANAGER:SYSTARTUP_VMS.COM:

@SYS$STARTUP:ESS$LAD_STARTUP.COM

If you changed any SYSGEN parameters, run AUTOGEN and reboot (for information about running AUTOGEN, see Section 7.22). If no SYSGEN parameters were changed, you can skip the reboot and execute the SYS$STARTUP:ESS$LAD_STARTUP.COM file manually.

After you complete these steps, the InfoServer server software is running and available to serve boot requests. Note that the network devices are LAD0 (the LAD Server Virtual Device) and LAST0 (the LAST Transport Layer Virtual Device).

The InfoServer server can run on the same system as the InfoServer client. You might want to start the InfoServer client on this system, allowing the system to mount InfoServer devices. To start the InfoServer on this system, enter the following command at the DCL prompt:

$$$ @SYS$STARTUP:ESS$STARTUP DISK

To have the InfoServer client start at system boot, include the command in SYS$MANAGER:SYSTARTUP_VMS.COM.

Now that you have set up and enabled the InfoServer server, you must use the InfoServer control program to create a service for the DVD drive. Follow these steps:

1. Mount the OpenVMS distribution media systemwide. In the following example, DQA0 is the DVD drive name (typically, DQA0 or DNA0 is the drive name) and I640831H1 is the volume label (for OpenVMS I64):

   $ MOUNT/SYSTEM DQA0 I640831H1

2. Enter the following command at the DCL prompt to define the InfoServer control program as a foreign command, or enter the line in a startup or login command file:

   $ INFOSERVER :== $ESS$INFOSERVER

   Alternatively, you can enter the following command to start the program:

   $ RUN SYS$SYSTEM:ESS$INFOSERVER

3. Start the InfoServer control program and create the service, as in the following example (the colon after the device name DQA0 is required):

   $ INFOSERVER INFOSERVER> CREATE SERVICE I640831H1 DQA0: INFOSERVER> EXIT

   The created service should now be available for any InfoServer clients in the same LAN (these clients broadcast service solicitations over the LAN).

   Started as in this example, the InfoServer control program accepts multiple commands until you exit by entering the EXIT command (or pressing Ctrl/Z). You can also enter a single command at the DCL prompt, returning you immediately to the DCL prompt again:

   $ INFOSERVER CREATE SERVICE I640831H1 DQA0: $

   The InfoServer control program commands are similar, though not identical, to those supported by the hardware InfoServer used traditionally by OpenVMS Alpha systems. For more information, see the INFOSERVER help (at the INFOSERVER prompt, type HELP) or the HP OpenVMS Version 8.3 New Features and Documentation Overview manual.

On OpenVMS Alpha systems only, you must perform the following steps:

1. Enable MOP to use LANACP or DECnet on the system on which the OpenVMS InfoServer utility is being used. For information about enabling MOP, see the LANCP chapter in the HP OpenVMS System Management Utilities Reference Manual: A-L.

2. Copy the APB_083.SYS file from the OpenVMS Alpha distribution media to the MOP download directory (LAN$DLL, which defaults to MOM$SYSTEM).

Make sure TCP/IP Services for OpenVMS is installed and that:

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 the OpenVMS I64 Version 8.3-1H1 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:

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):

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 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:”.

$ TCPIP SET BOOTP hostname /HARDWARE=ADDRESS=MACaddress-
_$ /FILE=[V831H1]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 I64, you must modify the client entry in the BOOTP database to point to the new, version-specific boot file.

Make sure the CD or DVD is mounted systemwide on the OpenVMS system serving as the InfoServer, and make sure an InfoServer service for the DVD drive is available on the network and accessible from your client system (the system to be booted from the InfoServer). The service should point to the server DVD drive on which the OpenVMS CD or DVD is mounted. To ensure that the InfoServer service is available on the network, use the following command:

$ MC ESS$LADCP SHOW SERVICES

The following is a sample display:

Interrogating network for Disk services, please wait...
    .
    .
    .
Disk services offered by node MOOSIC (LAD V3.1, Address: AA-00-04-00-AB-4E)

                                                   Current       Writes
Service:                      Device:      Rating: Connects:     Allowed?:
I640831H1                     OpenVMS      65535       0          No
    .
    .
    .

In this example, the service I640831H1 is the virtual disk unit that corresponds to the DVD drive on the InfoServer server named MOOSIC. This is the drive from which the OpenVMS distribution media is booted. The display shows that this service is available and that a service binding to the InfoServer DVD drive is established.

Access EFI on your Integrity server. If you added a boot option for network (InfoServer) booting to the EFI Boot Manager options list, as described in Section B.2.2; then select the appropriate boot option from the list. To move to the option, use the up or down arrow key. (Depending on how your terminal emulator is set up, you might have to use the letter v to scroll down or the caret (^) to scroll up.) Press Enter to toggle the selection. After selecting the boot option, skip to step 3.

	NOTE: If you do not select an option within the default 10-second limit, the first option in the list is selected automatically.

If you did not add a boot option for InfoServer booting to the EFI Boot Manager options list, then initiate the boot by either following the steps in “Booting with the EFI Boot Manager” or, on some of the more recent Integrity servers, using the simpler method described in “Booting with EFI lanboot select command”.

Booting with the EFI Boot Manager

Booting with EFI lanboot select command

When you select the appropriate entry, you see several lines of messages and then the InfoServer boot menu (the same boot menu you would see on an Alpha system), as in the following example. The DHCP (Dynamic Host Communication Protocol) message indicates the loading of the loader image (VMS_LOADER.EFI) that uses the EFI console to load and start the OpenVMS bootstrap (IPB.EXE). The Trivial File Transfer Protocol (TFTP) loads the bootstrap. In this example, “I64 Upgrade VIA NET” is the boot option for the InfoServer service. It was selected from the EFI Boot Manager options list (not shown).

	NOTE: If the InfoServer boot menu does not appear, you have probably selected the wrong LAN device. Try selecting another device. Verify the BOOTP database (see the HP TCP/IP Services for OpenVMS Management manual). Make sure the Integrity server that serves the network drive is running.

   
Loading.: Network Boot, 10/100
Running LoadFile()
   
CLIENT MAC ADDR: 00 13 21 5H 85 E4
DHCP./
CLIENT IP: 16.32.24.219   MASK: 255.0.0.0   DHCP IP: 0.240.0.0
Running LoadFile()
  
Starting: I64 Upgrade VIA NET
%EIA-I-BOOTDRIVER, Starting auto-negotiation
%EIA-I-BOOTDRIVER, Auto-negotiation selected 100BaseTX FDX
   
 Network Initial System Load Function
 Version 1.2
 
 
   FUNCTION         FUNCTION
      ID
      1     -        Display Menu
      2     -        Help
      3     -        Choose Service
      4     -        Select Options
      5     -        Stop
 
 Enter a function ID value:

Respond to the prompts by pressing Enter after each entry; use the default service name indicated or one suggested by the system manager:

1. Enter 3 for the function ID.

2. Enter 2 for the option ID.

3. Enter the service name ( I640831H1 is the default service name for the OpenVMS I64 OE DVD; check with your system or network manager for the service name to specify).

A sample display follows:

  Enter a function ID value: 3
  OPTION          OPTION
    ID
    1     -       Find Services
    2     -       Enter known Service Name
   
 Enter an Option ID value: 2
 Enter a Known Service Name: I640831H1

When you attempt to boot over the network, check your console display for the following:

If the network boot succeeds but your attempt to choose a service or to display services at the InfoServer menu fails, a device might be filtering the LASTport/Disk (LAD) protocol. This protocol does not provide routing functions and only works within a LAN. If filtering devices are used in an extended LAN, the devices must allow this protocol (protocol type is 80-41) to pass through unfiltered so that clients can access the InfoServer across the filtering device.