Booting from the InfoServer

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?:
  I64083                           OpenVMS      65535       0          No
      .
      .
      .

In this example, the service I64083 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 “Adding the Network Boot Option to the EFI Boot Manager”; 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.

	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 you have to perform the following steps; otherwise, skip to step 3.

1. From the EFI Boot Manager screen, select the Boot Configuration option (or in some versions of EFI, the Boot Option Maintenance Menu).

2. From the EFI Boot Configuration menu, select the Boot From a File option.

3. The Boot From a File menu lists the bootable devices (in EFI terminology, load files), including their MAC addresses. The composition of the list depends on how your Integrity server is set up. Select the appropriate device (search for the correct MAC address). For example, the following load file listed in the Boot From a File menu corresponds to the LAN device with MAC address 00-13-21-5B-85-E4:

   Load File [Acpi(HWP0002,0)/Pci(2|0)/Mac(0013215b85e4)]

   Note that each device is identified by the unique MAC address assigned to the device by the hardware vendor. Normally, the MAC address is labeled on the physical device. See your hardware documentation for more information.

   To further help you identify the LAN devices, you can use the EFI pci command, which displays all devices. Alternatively, you can try each of the LAN devices one at a time until you find the right one. Finally, you can make sure all LAN devices are connected to the appropriate network and are bootable using the InfoServer, in which case it does not matter which one you select. Note also that once you have OpenVMS running, you can display the devices and their corresponding MAC addresses by using the LANCP command SHOW CONFIG at the DCL prompt. The command lists the OpenVMS device names along with the MAC address and other characteristics. Likewise, with OpenVMS running, the EFI Utilities for OpenVMS vms_show command might provide additional information about any devices on the local system.

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, 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 (ALPHA083 is the default for service name for the InfoServer hardware; for an OpenVMS Alpha or OpenVMS I64 system using the InfoServer utility, ask your system or network manager for the service name).

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