C.2 Setting Up Your System as an InfoServer Client
To set up your local OpenVMS Integrity servers
system as an InfoServer client for network booting, you must perform
the following steps. Detailed instructions are provided in the subsections
that follow. For OpenVMS Alpha systems, no extra steps are required
for setting up an InfoServer client. You can boot the OpenVMS Alpha
InfoServer client from the >>> prompt.
the LAN I/O card to be used on your local Integrity servers 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.
(and recommended), add the network device as a boot option in the
EFI Boot Manager menu.
that the network device is supported by EFI as a bootable device.
NOTE: The ability to boot over the network requires
that the nearest switch or router be configured to autonegotiate.
C.2.1 Determining the Local Network I/O Card to Be Used
Select a LAN I/O card (also referred to as a LAN
I/O device or adapter) on your Integrity servers. This device must
be supported by your Integrity server’s EFI firmware. At minimum,
EFI supports the core I/O LAN cards installed
in the Integrity servers. On all Integrity servers, devices supported
by OpenVMS are either EI or EW devices (for example, EIA0 or EWA0).
The EFI firmware might also support variants of the core I/O cards,
such as additional network interface cards (NICs) of the same type.
It might also support other NICs that are installed in the system
but not classified as core I/O cards. In any case, you can verify
that the device you select is supported by EFI.
If multiple I/O cards are available on your system,
you can choose more than one to serve for network booting.
To list the installed LAN I/O devices known to
your OpenVMS Integrity servers system, follow these steps:
your operating system is not running, access the OpenVMS DCL triple
dollar sign prompt ($$$) from your OpenVMS Integrity servers OE DVD
by selecting option 8 (Execute DCL commands and procedures) on the
OpenVMS operating system main menu. Otherwise, skip to the next step.
the DCL prompt, enter the following command to start the OpenVMS Integrity
servers Boot Manager utility.
the LANCP utility and enter the LANCP command SHOW CONFIGURATION at
the LANCP prompt, as in the following example. The resulting display
lists four LAN devices, two of which are available (connected), as
indicated by the Link column (Up means the device is available; Down
means it is not). You can use a device that is in use by other protocols.
Decide which available devices you want to use for network booting
and record the device’s name, MAC address, and IP address.
(The MAC address should be labeled on the physical device.) Once
the LAN device is verified as bootable by EFI, you provide this information
to the person responsible for maintaining the BOOTP server database
(see Section C.4).
$$$ RUN SYS$SYSTEM:LANCPLANCP> SHOW CONFIGURATION
Device PrefCPU Medium/User Version Link Speed Duplex Auto BufSize MAC Address Type ...
------ ------- ----------- ------- ---- ----- ------ ---- ------- ---------------- ------------ ...
EIA0 0 Ethernet X-21 Up 1000 Full Yes 1500 AA-00-04-00-A5-38 UTP i82546 ...
00-13-21-5B-85-E4 (default) ...
EIB0 1 Ethernet X-21 Up 1000 Full Yes 1500 AA-00-04-00-A5-38 UTP i82546 ...
00-13-21-5B-85-E5 (default) ...
EWA0 0 Ethernet X-59 Down - - Yes 1500 00-11-0A-43-23-D8 UTP AB465A ...
EWB0 1 Ethernet X-59 Down - - Yes 1500 00-11-0A-43-23-D9 UTP AB465A ...
C.2.2 Adding the Network Boot Option to the EFI Boot Manager
To add the LAN device (virtual DVD drive) as a
network boot option, use the OpenVMS Integrity servers Boot Manager
utility, as follows:
the DCL prompt, enter the following command to start the OpenVMS Integrity
servers Boot Manager utility:
NOTE: When booting OpenVMS Integrity servers Version 8.4 or later,
you need to specify a special boot flag and the name of InfoServer
service name. The BOOT_OPTIONS.COM procedure now accepts InfoServer
service name in addition to the boot flags.
OpenVMS Integrity servers Boot Manager Boot Options main menu is displayed.
To add a network boot option, enter 1 at the prompt:
OpenVMS I64 Boot Manager Boot Options List Management Utility
(1) ADD an entry to the Boot Options list
(2) DISPLAY the Boot Options list
(3) REMOVE an entry from the Boot Options list
(4) MOVE the position of an entry in the Boot Options list
(5) VALIDATE boot options and fix them as necessary
(6) Modify Boot Options TIMEOUT setting
(B) Set to operate on the Boot Device Options list
(D) Set to operate on the Dump Device Options list
(G) Set to operate on the Debug Device Options list
(E) EXIT from the Boot Manager utility
You can also enter Ctrl-Y at any time to abort this utilityEnter your choice: 1
NOTE: While using this utility, you can change a response
made to an earlier prompt by entering the caret (^) character as many
times as needed. To end and return to the DCL prompt, press Ctrl/Y.
utility prompts you for the device name. Enter the device name.
In the following example, the device name is EIA0:.
Enter the device name (enter "?" for a list of devices): EIA0:
utility prompts you for the position you want your entry to take in
the EFI boot option list. Enter any position number other than 1.
(The number 1 position sets the device for automatic rebooting, which
is not desirable for upgrades.)
Enter the desired position number (1,2,3,,,) of the entry.
To display the Boot Options list, enter "?" and press Return.
Position : 4
utility prompts you for OpenVMS boot flags. By default, no flags are
set. Enter the OpenVMS flags (for example, 0,1), or accept the default
(NONE) to set no flags as in the following example:
Enter the value for VMS_FLAGS in the form n,n.
If you are
booting OpenVMS Integrity Version 8.4 onwards, HP recommends the value
of VMS_FLAGS be set to 0,200400.
The utility prompts you for the service name from OpenVMS
Integrity servers Version 8.4 onwards if you have entered 0,200400
as the boot flags. The service name is mandatory.
NOTE: The service name entered must be in uppercase.
utility asks whether the device will be used for cluster satellite
booting. Answer NO as in the following example:
Will EIA0 be used for cluster satellite boot? (Yes/No): NO
information about establishing a device for cluster satellite booting,
see the HP OpenVMS Cluster Systems manuals.)
utility prompts you for a description to include with your boot option
entry. By default, the device name and MAC address is used as the
description. You can enter more descriptive information, as in the
following example. As shown in the display of boot entries that follows,
the device name and MAC address (without dashes) are included anyway
in the boot entry line.
Enter a short description (do not include quotation marks).
Description ["EIA0"]: I64 UPGRADE VIA NET
efi$bcfg: eia0 (Boot0002) Option successfully added
Using the utility to display
the devices at this point (selecting 2 on the main menu), you see
your device listed, as in the following example:
Enter your choice: 2
To display all entries in the Boot Options list, press Return.
To display specific entries, enter the entry number or device name.
(Enter "?" for a list of devices):
EFI Boot Options list: Timeout = 10 secs.
01. DKB0 PCI(0|20|1|1) Scsi(Pun0,Lun0) "Boot VMS from DKB0" OPT
02. DKB200 PCI(0|20|1|1) Scsi(Pun2,Lun0) "Boot VMS from DKB200" OPT
03. VenHw(d65a6b8c-71e5-4df0-d2f009a9) "EFI Shell [Built-in]"
04. EIA0 PCI(0|0|2|0) Mac(0013215b85e4) "I64 Upgrade VIA NET"
4 entries found.
the utility by entering E at the prompt:
Enter your choice: E
NOTE: The Boot Configuration Menu provided by EFI or the EFI tool
VMS_BCFG are other alternatives for adding a boot entry. For more
information on EFI tools, see the System Management Utilities
C.2.3 Verifying the Network I/O Device Is Bootable by EFI
Finally, verify that the LAN device you selected
for your system’s InfoServer client is bootable by EFI. Verification
is recommended if the selected device is not one of the core I/O LAN
devices installed on your Integrity servers. To verify that the selected
LAN device is bootable by EFI, follow these steps:
the EFI console for your Integrity servers. If your operating system
is running, you must shut down your system to access EFI. (For details
about accessing and using EFI, see your hardware documentation.)
the EFI main menu, select the Boot Configuration option (or in some
versions of EFI, the Boot Option Maintenance Menu). Make a selection
before the EFI timeout expires; otherwise, the first entry of the
EFI Boot Manager is selected automatically. If you are brought to
the EFI Shell prompt, enter the exit command at
the prompt to move back to the EFI main menu. If an autoboot begins,
you can perform a cold reset of the Integrity servers to get back
to the EFI console. (For more information, see your hardware documentation.)
Otherwise, you must wait for your system to boot and shut it down
the EFI Boot Configuration menu, select the Boot From a File option.
In the Boot From a File list, look for the load file that corresponds
to the LAN device you selected for network booting. This is the load
file with a matching MAC address, as in the following example:
The MAC address of the EIA0 network
device selected earlier was 00-13-21-5B-85-E4, which matches the MAC
address shown (without dashes). This verifies that the selected device
is visible to the EFI console. If none of the Boot From a File options
listed matches your selected device, then try another available device
(as listed with the LANCP command SHOW CONFIGURATION in Section C.2.1).
the device name and its IP address and MAC address to the person responsible
for setting up the BOOTP server.