Appendix C Using HP SIM and vMedia to Install and Upgrade OpenVMS

At least one system in the LAN must be designated as the InfoServer server. This is the system that hosts the DVD drive from which network booting is performed. It must be running OpenVMS Alpha Version 8.3 or later, or OpenVMS I64 Version 8.2–1 or later. Perform these basic steps to set up the InfoServer server:

1. Copy the SYS$STARTUP:ESS$LAD_STARTUP.TEMPLATE file to the SYS$STARTUP:ESS$LAD_STARTUP.DAT file. If any changes are necessary for your environment (typically none are required), modify the SYS$STARTUP:ESS$LAD_STARTUP.DAT file.

2. Copy the SYS$STARTUP:ESS$LAST_STARTUP.TEMPLATE file to the SYS$STARTUP:ESS$LAST_STARTUP.DAT file. Modify the SYS$STARTUP:ESS$LAST_STARTUP.DAT file as follows, along with any other changes necessary for your environment:

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

3. Optionally, add the following two lines to the SYS$MANAGER:SYSTARTUP_VMS.COM system startup file:

   @SYS$STARTUP:ESS$LAD_STARTUP.COM @SYS$STARTUP:LD$STARTUP

Set up the BOOTP server and TFTP server on the InfoServer server system:

	IMPORTANT: For HP SIM provisioning, the BOOTP and TFTP server must be set up on the same system as the InfoServer. TFTP is required on the boot server for supplying the boot files to the client systems.

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

   • At least one IP interface is defined.

   • The BOOTP server and TFTP server are configured and started.

   • Optionally, make sure TELNET and FTP are configured and started.

   To display IP interface information, use the TCPIP SHOW INTERFACE command.

   	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.

2. 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. To make subsequent upgrades easier, you can use systemwide or clusterwide logical names.

3. Copy the following two files from the DVD to the TCPIP$TFTP_ROOT:[V831H1] directory:

   • [SYS0.SYSCOMMON.SYSEXE]VMS_LOADER.EFI

   • [SYS0.SYSCOMMON.SYSEXE]IPB.EXE

4. Gather data for each boot client (each node that is going to be provisioned, hereafter referred to as a provisioning/boot client), including the IP address of the network device (the Integrity server core I/O card).

5. Define each provisioning/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 provisioning/boot client and ipaddress is its IP address:

   $ TCPIP SET HOST hostname/ADDRESS=ipaddress

6. For each provisioning/boot client, you might need to add an entry in the BOOTP database to specify a gateway and network mask. To do so, use the SET BOOTP command in the following format, where hostname specifies the host name of the boot client, hosts specifies gateways used for routing, and ip-host-field specifies the part of the host field of an IP address identified as the subnet. To determine the names of the gateways and the subnet information, consult your network administrator. For more information on this command, see the TCP/IP Services for OpenVMS documentation.

   $ TCPIP SET BOOTP hostname /GATEWAY=hosts- _$ /NETWORK_MASK=ip-host-field /FILE=[V831H1]VMS_LOADER.EFI

   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. As shown in the previous example, the boot file for OpenVMS Version 8.3-1H1 is [V831H1]VMS_LOADER.EFI.

Create a copy of the OpenVMS OE DVD on an LD device (logical disk or virtual drive) that is accessible to the InfoServer utility. The following example shows how to establish an LD device and copy the OpenVMS DVD (DNA0:) to the device on an OpenVMS system that is the InfoServer server:

$ @SYS$STARTUP:LD$STARTUP
$ LD CREATE I640831H1.DSK/SIZE=6005000
$ LD CONNECT I640831H1.DSK
$ MOUNT/FOREIGN/NOASSIST LDA1:
$ MOUNT/OVERRIDE=IDENTIFICATION DNA0:
$ BACKUP/IMAGE/VERIFY DNA0: LDA1:
$ DISMOUNT DNA0:
$ DISMOUNT LDA1:

For more information about InfoServer commands, including how to work with LD devices, see the HP OpenVMS Version 8.3 New Features and Documentation Overview manual.

Start the InfoServer client on your Integrity server, and on any other systems that are to be provisioned, by entering the following command:

$ @SYS$STARTUP:ESS$STARTUP DISK

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

Enable the LD device as the InfoServer service, as in the following example:

$ MOUNT/SYSTEM/NOWRITE LDA1: I640831H1
$ INFOSERVER :== $ESS$INFOSERVER
$ INFOSERVER
INFOSERVER> CREATE SERVICE I640831H1 LDA1:
INFOSERVER> EXIT

Insert the OpenVMS OE DVD into the DVD drive on your PC or Windows server.

Make sure your Integrity server iLO 2 MP and vMedia are set up as documented in your Integrity server hardware documentation (for example, see the HP Integrity iLO 2 MP Operations Guide). Enable the right to use the vMedia applet.

Make sure your Integrity server is powered on. Once you connect to your server's iLO 2 MP and log in, you can check the status and power on your Integrity server from your browser. Select the Virtual Devices tab and access the Power & Reset screen by selecting Power Management (on the left of the screen).

From a browser on a Windows-based PC or server in the same network as your Integrity server, access your Integrity server's iLO 2 MP by specifying the DNS name or IP address. Then log in as shown in the following example (in this example, the IP address is entered):

Select the Virtual Devices tab and then select Virtual Media from the list on the left. If your Integrity server is not a cell-based system, skip to the next step. If your server is a cell-based system, you must select the partition before launching the vMedia application, as in the following example:

Click Launch in the upper right corner of the Virtual Media screen, as shown in the following example:

You might see the following warning or similar warnings or informational messages regarding security. In the security warning shown here, you can check the box to always trust content, and then click Yes. (To avoid certification warnings, install valid certificates for the iLO 2 MP. For more information, see the HP Integrity iLO 2 MP Operations Guide. In addition, see the online help provided by your browser.)

A screen similar to the following might appear next. Check the box to always trust content, and then click Run.

From the Virtual CD/DVD-ROM dialog box that appears next, make sure the Local Media Drive option is selected, and then click Create Disk Image, as in the following example:

The Create Disk Image dialog box appears, as in the following example. Specify a path or file name for the image to be created, and then click Create.

	NOTE: As noted previously, HP recommends that you do not install or upgrade directly from a DVD (on your local Windows-based management workstation) with vMedia. Creating a disk image on the local drive (or a network drive) will make the installation or upgrade much faster. This assumes the local or network drive is accessible to your Integrity server over a high-speed network link.

This brings up the Virtual CD/DVD-ROM dialog box, as in the following example. Select the Local Image File option, browse for the created ISO image file that you want vMedia to access, and then click Connect.

The screen should then indicate the image is connected to vMedia, as in the following example. Now the targeted Integrity server is ready to be booted using the ISO image file.

Insert the OpenVMS OE DVD into the DVD drive of your PC or Windows server.

Make sure your Integrity server iLO 2 MP and vMedia are set up as documented in your Integrity server hardware documentation (for example, see the HP Integrity iLO 2 MP Operations Guide). Enable the right to use the vMedia applet.

Make sure your Integrity server is powered on. Once you connect to your server's iLO 2 MP and log in, you can check the status and power on your Integrity server from your browser. Select the Virtual Devices tab and access the Power & Reset screen by selecting Power Management (on the left of the screen).

From a browser on a Windows-based PC or server in the same network as your Integrity server, access your Integrity server's iLO 2 MP by specifying the DNS name or IP address. Then log in as shown in the following example:

Select the Virtual Devices tab, then select Virtual Media from the list on the left. If your Integrity server is not a cell-based system, skip to the next step. If your server is a cell-based system, select the partition before launching the vMedia application, as shown:

Now launch the vMedia application by clicking Launch, as shown in the following example:

At this point, you might see popup security warnings, such as the one shown in Section C.1.4. In this case, you can check the box to always trust content, and then click Yes. (To avoid certification warnings, install valid certificates for the iLO 2 MP hardware. For more information, see the HP Integrity iLO 2 MP Operations Guide. In addition, see the online help provided by your browser.)

From the Virtual CD/DVD-ROM dialog box shown in the following example, make sure the Local Media Drive option is selected, and then click Create Disk Image:

The Create Disk Image dialog box appears, as in the following example. Specify a path or file name for the image to be created, and then click Create.

	NOTE: As noted previously, HP recommends that you do not install or upgrade directly from a DVD (on your local Windows-based management workstation) with vMedia. Creating a disk image on the local drive (or a network drive) will make the installation or upgrade much faster. This assumes the local or network drive is accessible to your Integrity server over a high-speed network link.

The Virtual CD/DVD-ROM dialog box appears, as in the following example. Select the Local Image File option, and then browse for the created ISO image file that you want vMedia to access. Then click Connect.

The following screen indicates that the image is connected to vMedia. Now the targeted Integrity server is ready to be booted using the ISO image file.

At this point, access the Integrity server's console from a browser or terminal emulator, log in to the MP, and enter the co command at the MP main menu:

   MP MAIN MENU:

         CO: Console
        VFP: Virtual Front Panel
         CM: Command Menu
      SMCLP: Server Management Command Line Protocol
         CL: Console Log
         SL: Show Event Logs
         HE: Main Help Menu
          X: Exit Connection

[usb2mp] MP> co

At the EFI Shell prompt, enter the reconnect -r command to make sure all devices are discovered:

Shell> reconnect -r

When the EFI Shell prompt next appears, enter the map -r command to remap and rebuild the list of known devices that have a bootable EFI system partition:

Shell> map -r

The following example shows the boot mapping table displayed by the map -r command. The significant lines in the table are those that include both USB and CDROM information. Thus, in this example, fs0 is the file-structured logical partition on the physical disk to be booted from; it includes the bootable partition, and blk2 is the block device that has the bootable partition.

Device mapping table
fs0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|0)/Usb(0, 2)/CDROM(Entry0)
fs1 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr500000E014887A22,Lun0)/HD(Part1,...FF)
fs2 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr500000E014887A22,Lun0)/HD(Part4,...FF)
blk0 : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)
blk1 : Acpi(HWP0002,PNP0A03,0)/Pci(2|0)/Usb(0, 2)
blk2 : Acpi(HWP0002,PNP0A03,0)/Pci(2|0)/Usb(0, 2)/CDROM(Entry0)
blk3 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr5000C50000A7B30D,Lun0)
blk4 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr500000E014887A22,Lun0)
blk5 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr500000E014887A22,Lun0)/HD(Part1,...FF)
blk6 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr500000E014887A22,Lun0)/HD(Part2,...FF)
blk7 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr500000E014887A22,Lun0)/HD(Part3,...FF)
blk8 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr500000E014887A22,Lun0)/HD(Part4,...FF)
blk9 : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr500000E014887A22,Lun0)/HD(Part5,...FF)

Now you can boot the OpenVMS I64 image, either using the EFI boot menu or the following command at the EFI Shell prompt:

Shell> fs0:\efi\boot\bootia64.efi

As shown in the following example, the OpenVMS displays several messages followed by the operating system menu. You can now begin the installation or upgrade of OpenVMS on the Integrity server.

	NOTE: The %SYSTEM-I-MOUNTVER messages and the Universal Serial Bus Configuration Manager message are new to OpenVMS Version 8.3-1H1 and are seen only when using USB or vMedia devices for booting the Integrity rx2660, rx3600, and rx6600 servers.

   .
   .
   .
    HP OpenVMS Industry Standard 64 Operating System, Version XBO8-O3N
    © Copyright 1976-2007 Hewlett-Packard Development Company, L.P.
   .
   .
   .
    Installing required known files...
%RUN-S-PROC_ID, identification of created process is 00000024
  %SYSTEM-I-MOUNTVER, DNA0: is offline.  Mount verification in progress.

  %SYSTEM-I-MOUNTVER, DNA0: has completed mount verification.

Universal Serial Bus Configuration Manager, Version V2.1 Reset Unconfigured devices

    Configuring devices...

%PKA0, Copyright (c) 2001 LSI Logic, PKM V1.1.01  Chip LSISAS1068
%PKA0, LSISAS1068 firmware version is 1.16.0.0 
%EWA0, Auto-negotiation mode assumed set by console 
%EWA0, Merl5704 located in 64-bit, 66-mhz PCI-X slot 
%EWA0, Device type is BCM5704C (UTP) Rev B0 (21000000) 
%EWB0, Auto-negotiation mode assumed set by console 
%EWB0, Merl5704 located in 64-bit, 66-mhz PCI-X slot 
%EWB0, Device type is BCM5704C (UTP) Rev B0 (21000000) 
%EWA0, Link up: 100 mbit, full duplex, flow control (txrx) 
%EWB0, Link up: 100 mbit, full duplex, flow control (txrx) 

    ****************************************************************

    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 X8.3-BO8
        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/?)