Examining Software and Hardware Components

If both a Table of Contents and Search form are not displayed in separate frames along with this one, you may wish to redisplay this book in a frameset, beginning with the first page.

HP OpenVMS Version 8.2 Upgrade and Installation...

Getting Started

Key Terms

Using the Operating System CD or DVD Menu

Examining Software and Hardware Components

Before beginning an installation or upgrade, be sure you have all the required hardware and software components, as described in the following sections.

Hardware Components

Before you begin an installation or upgrade, do the following:

Be sure the hardware has been installed and checked for proper operation. For detailed information, refer to the hardware manuals you received with your Alpha or Integrity server system.

For initial installations on an Integrity server system, some information is also provided in this manual; see Setting Up, Booting, and Shutting Down HP Integrity Server Systems. For your console terminal, you will need a standard PC-to-PC file transfer cable (also known as a null modem cable; 9-pin female connectors at each end) to connect a PC, laptop, or similar device that includes terminal emulation software.

Be sure you know how to turn on and operate the components of your system, including the system unit, console, monitor, drives, terminals, and printers. If necessary, read the hardware manuals that came with these components.

Make sure you record the installation procedure. You will need a transcript if a problem occurs during installation. If you are using terminal emulation software, set the software to log the session. Otherwise, set up your system to record the installation procedure on either a hardcopy terminal or a printer attached to the console terminal. (Refer to your hardware manuals for more details about connecting those components to your system.)

Software Components

Before you begin an installation or upgrade, do the following:

Be sure you have all the items listed on the bill of materials contained in the distribution kit. If your distribution kit is incomplete, notify your HP support representative and request priority shipment of any missing items.

Before installing the OpenVMS operating system software, review all cover letters and release notes.

OpenVMS Alpha Operating System CD

Included in your OpenVMS Alpha kit is the OpenVMS Alpha operating system CD, which you use to install or upgrade the operating system, or to perform operations such as backing up the system disk. The CD is labeled similar to the following:

CD Label:
HP OpenVMS Alpha Version 8.2 Operating System

Volume Label:
ALPHA082

The volume label is the machine-readable name that the OpenVMS Alpha operating system and InfoServer systems use to access the CD.

OpenVMS I64 Operating Environment DVD

Included in your OpenVMS I64 kit is the OpenVMS I64 Operating Environment DVD, which you use to install the operating system or to perform operations such as backing up the system disk. The DVD is labeled similar to the following:

DVD Label:
HP OpenVMS Industry Standard 64 Version 8.2 Operating Environment

Volume Label:
I64082

The volume label is the machine-readable name that the OpenVMS I64 operating system uses to access the DVD.

Firmware Revision Checking on Alpha Systems

OpenVMS Alpha Version 8.2 provides firmware checking for systems during each boot operation. When you boot the OpenVMS Alpha operating system CD, the system automatically checks the version of console firmware that is running on your computer. The system also provides information about how to update the firmware.

If you do not have the required version of console firmware, the system displays a message similar to the following:

%SYSBOOT-F-FIRMREV, Firmware rev.nnn is below the absolute minimum of nnn.
          Please update your firmware to the recommended revision nnn,            
            Alpha Systems Firmware Update Vn.n.

If you do not have the recommended version of console firmware, the system displays a message similar to the following:

%SYSBOOT-W-FIRMREV, Firmware rev.nnn is below the recommended minimum of nn.
          Please update your firmware to the recommended revision,
          which can be found on the firmware CD labeled:   
            Alpha Systems Firmware Update Vn.n.

The latest firmware CD is included with your OpenVMS Alpha media kit. It includes system firmware for current and recent Alpha systems and some I/O adapters. Firmware for older hardware might not be included on the current CD but can be found on previous CDs or at the following Web site:

 http://h18002.www1.hp.com/alphaserver/firmware/

HP recommends updating to the latest released firmware for all systems and I/O adapters. Firmware is released more often than the OpenVMS Alpha operating system. The firmware version recommendations included in OpenVMS Alpha V8.2 might be superseded before the next version of the OpenVMS Alpha operating system is released.

After you install this version of the OpenVMS Alpha operating system, the firmware check will occur each time you reboot the system.

Firmware on Integrity Server Systems

HP Integrity servers include several firmware components (varying with system type), any of which might need updating. For the minimum versions required for system, BMC, and MP firmware, refer to the HP OpenVMS Version 8.2 Release Notes . To update Integrity server firmware, follow the instructions provided in this section. For instructions on setting up a console on your Integrity server, see Setting Up, Booting, and Shutting Down HP Integrity Server Systems and the hardware documentation that comes with the server.

The HP Integrity server firmware and utilities can differ significantly across models. They can even differ across versions of the same model. The information about hardware and firmware presented in this and other sections of this manual is often based on the HP Integrity rx2600 server. The information is not intended to replace the hardware documentation included with your Integrity server system. Refer to your hardware documentation for the most up-to-date information specific to your particular model and version. Note that the hardware documentation includes model-specific illustrations to guide you. The latest version of documentation for your server can be found online at the following Web sites:


 
http://docs.hp.com
 
http://www.hp.com/support/itaniumservers

Refer also to the HP OpenVMS Version 8.2 Release Notes for the latest information about firmware and software requirements and considerations for your Integrity server.

Note also that when entering commands for the Integrity server, if you press the Delete key on a VTxxx terminal (or press the key you have mapped to send the DEL/RUBOUT character code in your terminal emulator), the last character typed is not deleted, as would be expected on an OpenVMS Alpha system. Integrity server facilities use Ctrl/H to delete the last character typed. For information about how to remap a terminal from Ctrl/H to the DEL/RUBOUT, see The Delete or Backspace Key.

To update your system and BMC firmware, you must do the following:

Determine the current firmware version on your Integrity server (see Checking Firmware Version).

Create a firmware update CD on any system equipped with a CD-recordable drive (see Creating a Firmware Update CD).

Update the firmware on your Integrity server (see Updating Your Firmware from the Firmware Update CD).

To update your MP firmware, follow the steps provided in Updating MP Firmware.

Checking Firmware Version

To determine the firmware version in place on your Integrity server, use the Extensible Firmware Interface (EFI) info fw command at the EFI Shell prompt. (To get to the EFI Shell prompt, select EFI Shell [Built in] from the main EFI Boot Manager menu. More information about the use of EFI is included in Using the Extensible Firmware Interface (EFI).) For example:

Shell> info fw

An annotated sample display follows:
InfoFW

The info fw command at the EFI> shell prompt cannot be used while OpenVMS is running. You can use the Management Processor (MP) interface to check firmware on your system while OpenVMS is running. Use the sysrev command at the MP:CM> prompt. (The EFI info fw command displays more detail.) For more information about using MP, see Using the Management Processor (MP) Interface

For basic information about EFI, see Configuration/Management Tools on HP Integrity Server Systems. For more information about using EFI, refer to the hardware documentation supplied with your server system.

EFI shell commands are not case sensitive. However, in this manual, EFI and other Integrity server interface commands are displayed in lowercase to help distinguish them from OpenVMS DCL commands displayed in uppercase.

Creating a Firmware Update CD

To create a firmware update CD for your Integrity server, you need a CD-recordable drive (CD-R, CD-W, or CD-RW) and software, plus a blank CD-R disk.

The instructions in this step are for recording a CD on an OpenVMS system. You can record the CD on any system or PC, such as a Microsoft® Windows® computer, a Linux® system, or an HP-UX system.

Go to the following Web site:

http://www.hp.com/support/itaniumservers

Click on the appropriate server in the list provided on this web page (a new web page appears at this and each of the next steps).

Click on the "Download drivers and software" link.

Click on the "Cross operating system (BIOS, Firmware, Diagnostics, etc)" link.

Locate the appropriate ISO-image firmware file, read the instructions for the file, and then download the ISO-image firmware (zip-compressed) file to your system.

Unzip the firmware file into the corresponding .ISO file. The .ISO file is a block copy of the firmware disk for the Integrity server system. On OpenVMS systems, you can obtain the INFO-ZIP utility from the OpenVMS Freeware CD, and use the UnZip utility provided with INFO-ZIP. The following example shows the command used for unzipping an .ISO image of the latest system and BMC firmware for an rx2600 system (the file name changes with each update of the firmware available at the Web site):
```
$ UNZIP PF_CPEAKSYS0231.ZIP
Archive: SYS$SYSROOT:[SYSMGR]PF_CPEAKSYS0231.ZIP
 inflating: PF_CPEAKSYS0231.ISO
```

Record the data on the CD, specifying the .ISO file as the source for the CD.

OpenVMS software includes the CD recording tool CDRECORD. For help information, use the @SYS$MANAGER:CDRECORD HELP command at the OpenVMS DCL prompt. For source files, check the OpenVMS Open Source Tools CD supplied with your OpenVMS system kit. For more information about the software, visit the following Web site:

http://www.hp.com/go/openvms/freeware/

Updating Your Firmware from the Firmware Update CD

To update the firmware on your Integrity server from the firmware update CD, follow these steps:

Shut down the Integrity server to the EFI console level. If your OpenVMS I64 system is already running, you must shut down the operating system. Once you get the P00> prompt, press Return. In a few minutes, the main EFI Boot Manager screen appears. You can then select the EFI Shell option or wait a few seconds until the EFI Shell prompt appears automatically. For more information about EFI, refer to the appropriate hardware documentation or see Setting Up, Booting, and Shutting Down HP Integrity Server Systems.

Remove the recorded CD from the CD-R drive, label it, and load it into the CD/DVD drive on your Integrity server.

Exit the EFI shell (enter the exit command at the EFI Shell prompt). From the EFI Boot Manager menu, select the Boot Option Maintenance Menu option, as shown in the following example. (To move to the option, use the up or down arrow keys (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 Return to toggle the selection.) The shading indicates the default or selected option.

The Boot Maintenance Manager menu appears, as in the following example. Use the Boot Maintenance Manager menu to select the Add a Boot Option.

A menu similar to the following appears. Select the "Removable Media Boot" line, as shown, and press Return.

When prompted, enter a new description for the Removable Media Boot option, enter N to select the No BootOption data type, and then answer YES to save your changes in NVRAM, as shown in the following example. In this example, the new description for the Removable Media Boot option is "DVD-ROM."

After the changes have been saved to NVRAM, select Exit. The Boot Maintenance Manager menu appears again. From that menu, select Exit to return to the EFI Boot Manager screen.

Boot the CD by selecting the new description line for theRemovable Media Boot option in the Boot Maintenance Manager menu.

When you boot the CD, the main screen of the EFI-based setup utility appears, similar to the following example, which is for an rx2600 Integrity server. (If you are familiar with Alpha systems, the EFI-based setup utility is functionally similar to the OpenVMS Alpha LFU utility.) This menu-based tool lets you read the firmware release notes, choose which firmware to update, and exit with or without a reboot. It allows you to update the Integrity server firmware and I/O card firmware. The firmware includes firmware for the system, MP, BMC, and other system components.

To update the firmware for your Integrity server, enter the letter "a" at the prompt. A screen similar to the following appears.

To view the release notes, enter the letter a. To update the firmware, enter the letter b.

After the firmware is updated, enter the letter x to exit, and then reboot. This option loads and runs the new firmware.

If you plan to use MP through a local area network (LAN) connection, set the MP network address (TCP/IP) (optional). For information about setting up MP through a LAN connection, see Configuring a Network Console Interface on MP.

Updating MP Firmware

The method for updating your MP firmware depends on the current version of the firmware. For updating MP firmware versions earlier than E.02.26, use method 1. You must update your firmware incrementally. For updating version E.02.26 to E.02.29, use method 2.

Method 1: Updating MP Firmware Versions Earlier Than E.02.26 If your MP firmware is earlier than E.02.26, you need the following information:

The IP adddress of a system running an FTP server from which you will download the firmware.

The path to the firmware files located on the FTP server.

The user name and password for the FTP server if anonymous access is not allowed.

Make sure other users are not using the system while you perform the firmware update. In addition, configure your FTP server so that it maintains sessions without easily timing out. For example, for TCP/IP Services for OpenVMS, the server's inactivity timer is determined by the value of the logical TCPIP$FTPD_IDLETIMEOUT. The default is 15 minutes. Set it to a larger value, as in the following example, which increases the inactivity timer to one hour:

$ DEFINE/SYSTEM/EXEC TCPIP$FTPD_IDLETIMEOUT 01:00:00

Stop and restart the FTP server for the new setting to take effect. For more information about configuring and managing the FTP server provided with TCP/IP Services for OpenVMS, refer to the HP TCP/IP Services for OpenVMS Management guide.

To update your MP firmware, follow these steps.

Versions of firmware earlier than E.02.26 must be updated incrementally. Specifically, if the current version of MP firmware is earlier than E.02.10, you must first update your firmware to E.02.10 before updating it further. If the current version is earlier than E.02.26, you must update the firmware to E.02.26 before updating it to E.02.29.

Configure the MP network, as explained in Configuring a Network Console Interface on MP.

Shut the Integrity server down to the EFI console level. If your OpenVMS I64 system is already running, you must shut down the operating system. Once you get the P00> prompt, press Return. In a few minutes, the main EFI Boot Manager screen appears, similar to the one shown in the following example:

Once you see the EFI Boot Manager screen, press Ctrl/B to get to MP, which should prompt you to log in. If you are at the EFI Shell prompt, enter Exit to get to the EFI Boot Manager screen, then press Ctrl/B.

To get the login user name and password prompts, you might need to press Return one or more times on your console keyboard. If this does not work, then try pressing Ctrl/B.

If you only see the MP password prompt, press Return to get to the MP login prompt.

If the login prompt still fails to appear, the system might be powered off. (When you powered on the system, you might have pressed the power button twice, which turns it on and then off again.)

If you see a message similar to the following, another user has the console. To gain control of the console from the other user, press and release Ctrl/E, then type the letters "cf." Alternatively, you can have the other user log off.

[Read only - use Ctrl-Ecf for console write access]

The system will be inoperative if it has MP firmware older than version E02.22.

To log in, use the Admin user name and Admin password (typed in the case shown). If this does not work, enter Return for the user name and also for the password. The following is an example of the login screen that you might see:

   HP Management Processor
   Firmware Revision E.02.29 Jul 1 2004,11:10:23
   (c) Copyright Hewlett-Packard Company 1999-2004. All Rights Reserved.
 
 
   MP login:Admin
   MP Password:*****

At the MP main menu that appears next as in the following example, enter the cm command for command mode, as shown.


 
             Hewlett-Packard Management Processor
 
(c) Copyright Hewlett-Packard Company 1999-2003. All Rights Reserved.
 
                MP Host Name: myhost
 
                 Revision E.02.29
 
   ******************************************************************
              MP ACCESS IS NOT SECURE
 
    Default MP users are currently configured and remote access is enabled.
    Modify default users passwords or delete default users (see UC command)
                  OR
         Disable all types of remote access (see SA command)
   ******************************************************************
 
     MP MAIN MENU:
 
        CO: Console
        VFP: Virtual Front Panel
        CM: Command Menu
        CL: Console Log
        SL: Show Event Logs
        CSP:Connect to Service Processor
        SE: Enter OS Session
        HE: Main Help Menu
        X: Exit Connection

   [uninitialized] MP> cm

At the MP> prompt, enter the xu command to activate upgrade mode. Messages similar to the following appear, warning you that you cannot upgrade the system firmware and MP firmware simultaneously, then prompting you to confirm that you want to activate upgrade mode:

MP> xu
 
XU
 
This command activates the upgrade mode. All connections will be closed,
the session will be aborted, and the modem connection will be dropped
immediately. Web and telnet connections will be dropped upon completion.
 
WARNING: Simultaneous upgrade of MP and System Firmware is not allowed
and will result in SFW corruption.
 
Please, confirm your intention to activate the upgrade mode (Y/[N]) : Y

The XU screen now prompts you to enter the source system IP address (the IP address of the system from which you will download the firmware) and the file path. The syntax for the file path depends on the operating system on which the FTP server resides. In the example that follows, the FTP server is on an OpenVMS system, so the file path is specified accordingly. You are also asked whether to use the default login, to which you should answer no and then enter the user name and password for FTP login to the source system.
```
Enter source system IP address (Q to quit): XX.XX.X.XX
 
Enter file path (Q to quit):DSA500:[MP_FW.222]
 
 
Do you wish to use the default login: anonymous / MP@hp.com (Y/[N]/Q) :N
 
Enter login: user-name
 
Enter password:        
```

After you enter the login information successfully, the XU upgrade mode screen displays the parameters you entered and asks you to confirm. When you enter Y to confirm, messages indicate the MP firmware upgrade is in progress, as in the following example. The upgrade might take 10 to 20 minutes, depending on the speed of the connection you are using and how busy the system is from which you are downloading.

MP Firmware Upgrade Parameters:
   Source IP: XX.XX.X.XX	( IP address of node for FTP login )
   File Path: dsa500:[mp_fw.222]
   Login:     firmwareupd
 
Confirm? (Y/[N]): Y
   -> MP firmware upgrade in progress....
 
      Retrieving upgrade file using FTP.
      Retrieved an upgrade file successfully.
      Programming ROM.  Percent Complete: 100.
 
      Retrieving upgrade file using FTP.
 
      Retrieved an upgrade file successfully.
      Programming ROM.  Percent Complete: 100.
 
      Retrieving upgrade file using FTP.
 
      Retrieved an upgrade file successfully.
      Programming ROM.  Percent Complete: 100.
 
   -> MP firmware upgrade complete - Web and telnet connections will
      be dropped.  MP will now reset....

Method 2: Updating MP Firmware to Version E.02.29 If your current MP firmware version is E.02.26, you can update it to E.02.29 using a firmware update CD. To create a firmware update CD and boot the update CD, following the steps described in Creating a Firmware Update CD and except the last two steps (steps 9 and 10) in Updating Your Firmware from the Firmware Update CD. The EFI-based setup utility screen examples in steps 9 and 10 in Updating Your Firmware from the Firmware Update CD differ significantly from the screens you see while updating firmware from the MP firmware update CD. Refer to the instructions and screen examples in steps 9 and 10 that follow:

9. When you boot the CD, the main screen of the EFI-based setup utility menu appears, similar to the one in the following example. (If you are familiar with Alpha systems, the EFI-based setup utility is functionally similar to the OpenVMS Alpha LFU utility.)
fw_1

10. To update the MP firmware for your Integrity server, enter the letter "a" at the prompt. A screen similar to the following appears.
FWUpdate2

Device Naming Conventions

When you perform specific operations, you are asked to specify a device name for the source drive and one for the target drive. When specifying those device names, note the following naming conventions:

When the source drive is a local CD/DVD drive, the device name is similar to the following:
```
DQA0
```

When the source drive is a CD drive connected to the InfoServer, the device name is always the following:
```
DAD1
```

When the target drive is a local disk, the device name is similar to the following:
```
DKA0:
```
Note the following conventions:

On OpenVMS systems configured in certain OpenVMS Cluster or HSx environments, the device naming convention is similar to the following:
```
DUA20.14.0.2.0
```
The values you specify identify components such as the boot device, controller, unit number of the boot device, HSx controller node number, and channel numbers. Because these values vary depending on your specific hardware configuration, refer to the owner, operator, and technical service manuals that came with your computer for detailed information.

Key Terms

Using the Operating System CD or DVD Menu

CD Label:	HP OpenVMS Alpha Version 8.2 Operating System
Volume Label:	ALPHA082

DVD Label:	HP OpenVMS Industry Standard 64 Version 8.2 Operating Environment
Volume Label:	I64082