After you set up the InfoServer software and boot server properly
and ensure that the InfoServer service is available, you can boot
the remote DVD served by the InfoServer by following these steps:
Make sure the DVD is mounted systemwide on the OpenVMS
I64 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
I64 OE 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?:
I640821 OpenVMS 65535 0 No
.
.
.
In this example, the service I640821 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 I64 OE DVD 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 recommended and 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.
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.
From the EFI
Boot Manager screen, select the Boot Configuration option (or in
some versions of EFI, the Boot Option Maintenance Menu).
From the EFI Boot Configuration menu, select the
Boot From a File option.
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:
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. Refer to 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).
If the InfoServer boot menu does not appear, you have
probably selected the wrong LAN device. Try selecting another device.
Verify the BOOTP database (refer to 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 (or Return)
after each entry; use the default service name indicated or one
suggested by the system manager:
Enter 3 for
the function ID.
Enter 2 for the option ID.
Enter the service name (I640821).
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: I640821
After you boot, the system displays the OpenVMS menu. Follow
the instructions in
Performing the Upgrade to upgrade your OpenVMS operating system.
If you boot
the OpenVMS I64 OE DVD from an InfoServer system but lose your connection during
the upgrade procedure (the system is unresponsive and pressing Ctrl/Y
does not return you to the menu), do the following:
Boot the OpenVMS
I64 OE DVD again from the network.
Enter the DCL environment by choosing option 7 from
the menu.
Mount the device containing your backup copy of
the target disk and the device that is your target disk.
Restore the backup copy of your target disk by entering
the appropriate BACKUP commands. (Refer to
Backing Up and Restoring the System Disk for complete information about using MOUNT and BACKUP
commands to restore a system disk.)
Log out from the DCL environment.
Perform the upgrade again by choosing the upgrade
option (1) from the menu and following the procedures described
in this chapter.