After you set up the InfoServer software and the 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:
NOTE: You can copy the DVD to an LD device and boot from the LD device. This process is faster than using a DVD. | |
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 SERVICESThe 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?:
I64084 OpenVMS 65535 0 No
.
.
.In this example, the service I64084 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 servers. If you added a boot option for network (InfoServer) booting to the EFI Boot Manager options list, as described in Section ; 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”.
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 servers 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)]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.
For OpenVMS Version 8.3-1H1 and lower:
For OpenVMS Version 8.4 and later:
From the EFI Boot Manager screen, select the EFI Shell [Built-in] option.
At the Shell prompt, enter the following commands to setup appropriate boot flags and service name:
Shell> SET VMS_FLAGS 0,200400Shell> SET INFOSERVER_SERVICE I64084
(where I64084 is the InfoServer service name to be used for booting/installation. The service name entered must be in uppercase.)
Now enter lanboot select at the shell prompt. When prompted, enter the number for the LAN devices that have the MAC address specified when you configured BOOTP in Section .
An alternate to this is to setup a Directed Boot profile by specifying the flags and InfoServer service name as part of optional data in the following manner.
dbprofile -dn <profile name> -sip <server IP address> -cip <Client IP address> -m <subnet mask> -gip <gateway IP> -b <full path to VMS_LOADER.EFI in the boot server> -od “-fl 0,200400 -service I64084”
For more information on the DBPROFILE command, see the EFI online help. Now execute the lanboot select command as follows:
lanboot select -dn <profile name>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 examples. 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 the first example, “Integrity servers Upgrade VIA NET” is the boot option for the InfoServer service. It was selected from the EFI Boot Manager options list (not shown). In the second example, you notice the loading of memory disk message prior to IPB load. Since the service name is pre-decided by setting the environment variable or have specified it through BOOT_OPTIONS.COM, the InfoServer service menu is not displayed in the second example.
DHCP Message
Loading.: Network Boot, 10/100
Running LoadFile()
CLIENT MAC ADDR: 00 13 21 5H 85 E4
DHCP./
CLIENT IP: 1.1.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:
Enter the service name (ALPHA084 is the default service name for the InfoServer hardware; I64084 is the default service name for the OpenVMS Integrity servers OE DVD; when using the InfoServer utility, check with your system or network manager for the service name to specify).
Enter a function ID value:3OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value:2Enter a Known Service Name:I64084
After you boot, the system displays the OpenVMS menu. To install your OpenVMS operating system, follow the instructions in Section . To upgrade your system, follow the instructions in Section .
Loading of Memory Disk Message
Loading.: Network Boot Mac(00-15-60-04-f4-1e)
Client MAC Address: 00 15 60 04 F4 1E .- Client IP Address: 1.1.238.63 Subnet Mask: 255.255.240.0 BOOTP Server IP Address: 1.1.238.239 DHCP Server IP Address: 0.240.0.0 Boot file name: LDA3:[VMS$COMMON.SYSEXE]VMS_LOADER.EFI
Retrieving File Size.|
Retrieving File (TFTP).Loading memory disk from IP 1.1.238.239 ................................................................................
Loading file: LDA3:[VMS$COMMON.SYSEXE]IPB.EXE from IP 1.1.238.239 %IPB-I-SUCCESS, HP OpenVMS IPB version E8.4 successfully loaded.
HP OpenVMS Industry Standard 64 Operating System, Version E8.4
© Copyright 1976-2009 Hewlett-Packard Development Company, L.P.
%SMP-I-CPUTRN, CPU #1 has joined the active set.
%SMP-I-CPUTRN, CPU #2 has joined the active set.
%SMP-I-CPUTRN, CPU #3 has joined the active set.
%EIA0, Link up: 100 mbit, full duplex, flow control (receive only)
Installing required known files...
Configuring devices...
%PKA0, Copyright (c) 1998 LSI Logic PKW V3.2.20 ROM 4.19 %PKA0, SCSI Chip is SYM53C1010/66, Operating mode is LVD Ultra3 SCSI %PKB0, Copyright (c) 1998 LSI Logic PKW V3.2.20 ROM 4.19 %PKB0, SCSI Chip is SYM53C1010/66, Operating mode is LVD Ultra3 SCSI %EIB0, Link up: 100 mbit, full duplex, flow control (receive only)
****************************************************************
You can install or upgrade the OpenVMS I64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS I64 distribution media (CD/DVD).
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Upgrade, install or reconfigure OpenVMS I64 Version E8.4
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install or Undo patches; Show or Delete Recovery Data
8) Execute DCL commands and procedures
9) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?)NOTE: If you boot the OpenVMS Alpha operating system CD or OpenVMS Integrity servers OE DVD from an InfoServer but lose your connection during the installation or upgrade procedure (the system is unresponsive and pressing Ctrl/Y does not return you to the menu), do the following:
| ||||||