HP OpenVMS Version 8.2 Upgrade and Installation...

Setting Up, Booting, and Shutting Down HP Integrity...

Booting Operations

Halt and Shutdown Procedures

Configuring and Managing Booting of Your Integrity server  

For configuring booting on a Fibre Channel storage device, you must use the OpenVMS I64 Boot Manager utility. (For information about configuring Fibre Channel devices, refer to the Guidelines for OpenVMS Cluster Configurations manual.)

If you have just completed the initial setup of your Integrity server, perform the following two steps before continuing:

1. Power up your server system using the MP pc -on command, as explained in Powering the Integrity Server On or Off from the MP Console Interface. If MP is not available, use the power button on the front panel, pressing it only once.

   ---

   If you see a warning that the BMC System Event Log (SEL) is full, you can safely continue when the BMC SEL is full by following the prompts; OpenVMS will process the contents of the SEL. If you want to clear the SEL manually, see the instructions in the first note of Booting Operations. HP recommends that you load and use the most current system firmware. For more information about updating the system firmware, see Firmware on Integrity Server Systems.

   ---

2. At the EFI Boot Manager menu, select the EFI Shell [Built-in] option. You can now boot your OpenVMS I64 system manually, or you can add a new entry to the EFI Boot Manager menu to have your system booted automatically whenever you power on your Integrity server or reboot.

Setting Automatic Booting and Boot Flags for Your System Disk  

The OpenVMS I64 Boot Manager (BOOT_OPTIONS.COM) is an easy-to-use, menu-based utility that allows you to configure EFI boot options for your Integrity server. With this OpenVMS utility, you can do such actions as the following:

• Set your system disk to boot automatically on hardware startup and reboot



• Set boot flags



• Display the EFI boot options



• Add, move, and remove boot options in the EFI Boot Manager menu



• Enable or disable the EFI boot timeout and set the timer

This section explains how to perform the first two operations. For more information about this utility, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials.

HP recommends that you configure your system with a boot option for your system disk. You can enable automatic reboot of the system disk by specifying your system disk as the first boot option in the EFI Boot Manager menu. When the EFI timeout occurs (after 10 seconds, by default), your system disk boots automatically. You can do this manually and set boot flags manually, as explained in Manually Setting Automatic Booting of Your System Disk and Manually Setting OpenVMS I64 Boot Flags (Optional, for Manual Boots Only); however, it is much simpler to use the OpenVMS I64 Boot Manager utility, which allows you to do both operations and much more. Follow these steps:

To configure booting on Fibre Channel devices, you must use the OpenVMS I64 Boot Manager utility. (Use of the utility is optional for other devices but mandatory for Fibre Channel devices.) For more information about the utility, refer to the HP OpenVMS System Manager's Manual, Volume 1: Essentials. For more information about configuring and booting Fibre Channel devices, refer to the Guidelines for OpenVMS Cluster Configurations.

1. At the DCL prompt, enter the following command to invoke the OpenVMS I64 Boot Manager utility:

   $ @SYS$MANAGER:BOOT_OPTIONS.COM

2. When the utility is invoked, the main menu displays. To add your system disk as a boot option, enter 1 at the prompt, as shown in the following example:

       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 utility
    
   Enter your choice: 1

   ---

   While using this utility, you can change a response made to an earlier prompt by typing the "^" character as many times as needed. To abort and return to the DCL prompt, enter Ctrl/Y.

   ---

3. The utility prompts you for the device name. Enter the system disk device you are using for this installation, as in the following example, where the device is DKA0::

   Enter the device name (enter "?" for a list of devices): DKA0:

4. The utility prompts you for the position you want your entry to take in the EFI boot option list. Enter 1, as in the following example:

   Enter the desired position number (1,2,3,,,) of the entry.
   To display the Boot Options list, enter "?" and press Return.
   Position [1]: 1

5. The utility prompts you for OpenVMS boot flags. By default, no flags are set. Enter the OpenVMS flags (for example, 0,1) followed by pressing Return, or press Return to set no flags, as in the following example:

   Enter the value for VMS_FLAGS in the form n,n.
   VMS_FLAGS [NONE]: 

   Optionally, you can use any of the standard OpenVMS boot flags such as the following:

   0,1	Enable SYSBOOT to change system parameters; enable conversational booting for debugging purposes.
   0,2	Load XDELTA.
   0,4	Take the initial EXEC_INIT breakpoint.
   0,20000	Print debug messages on boot.
   0,30000	Print more debug messages on boot.

   
   

6. The utility prompts you for a description to include with your boot option entry. By default, the device name is used as the description. You can enter more descriptive information as in the following example. This example shows a sample confirmation message (for devices with multiple paths, such as Fibre Channel devices, a separate confirmation message is displayed for each path). EFI$BCFG is the name of the executor file for the OpenVMS I64 Boot Manager utility.

   Enter a short description (do not include quotation marks).
   Description ["DKA0"]: DKA0: OpenVMS V8.2 for PLM's System
    
   efi$bcfg: DKA0: (BOOT003) Option successfully added

7. When you have successfully added your boot option, exit the utility by entering E at the prompt.

   Enter your choice: E
   $ 

Manually Setting OpenVMS I64 Boot Flags (Optional, for Manual Boots Only)  

To set the OpenVMS boot flags, HP recommends using the OpenVMS I64 Boot Manager (BOOT_OPTIONS.COM) utility as you add a boot entry to the EFI Boot Manager menu (see the first note in Configuring and Managing Booting of Your Integrity server). You can also type the set vms_flag command at the EFI shell prompt, as shown. If you set up the OpenVMS boot flags manually as described, you must boot your system manually each time. If you want to have your OpenVMS system booted automatically, do not set up the OpenVMS boot flags manually.

Shell> set vms_flags 0,0

set vms_flags 0,1	Enable SYSBOOT to change system parameters; enable conversational booting for debugging purposes.
set vms_flags 0,2	Load XDELTA.
set vms_flags 0,4	Take the initial EXEC_INIT breakpoint.
set vms_flags 0,20000	Print debug messages on boot.
set vms_flags 0,30000	Print more debug messages on boot.

If you want to reset the boot flags (for example, if you used the SET VMS_FLAGS 0,1 command to enable SYSBOOT and now you no longer want SYSBOOT enabled), enter the SET VMS_FLAGS 0,0 command.

Manually Setting Automatic Booting of Your System Disk  

This section explains how to manually set up your Integrity server firmware to automatically boot your OpenVMS I64 system from disk.

To have your system boot automatically (instead of requiring you to enter a boot command at the EFI Shell prompt), add a new entry on the EFI Boot Manager menu that specifies the OpenVMS target disk and boot loader. To do so, HP recommends that you use the OpenVMS I64 Boot Manager (BOOT_OPTIONS.COM) utility, as explained in Setting Automatic Booting and Boot Flags for Your System Disk. The utility simplifies the task for you. However, if you want to perform the task manually without taking advantage of this utility, you can access the EFI shell and type the following line at the prompt, where fsn: (such as fs0: or fs1:) is the device associated with the system disk:

Shell> bcfg boot add 1 fsn:\efi\vms\vms_loader.efi "HP OpenVMS I64"

This command adds the OpenVMS I64 operating system to position 1 in the EFI Boot Manager menu. The quoted text in the command line ("HP OpenVMS I64") is what appears at position 1 in the menu, as in the following example. You can enter any text that helps you identify the operating system. During system power up, the position 1 item is automatically executed after the default pause of 10 seconds. To set flags, use the SET VMS_FLAGS command at the EFI Shell prompt, as explained in Manually Setting OpenVMS I64 Boot Flags (Optional, for Manual Boots Only). To change the amount of time that EFI pauses before automatically booting the boot option, see Setting EFI Boot Option Timeout.

To get to the EFI Boot Manager menu, enter EXIT at the EFI Shell prompt. The following EFI Boot Manager screen example shows the OpenVMS boot option added at position 1 in the menu:

Alternatively, you can add an EFI boot menu option by using the EFI menu interface:

1. Select the Boot Options Maintenance Menu option.
2. Select the Add a Boot Option.
3. Select the boot device and boot file.

   ---

   All EFI boot options embed the disk Globally Unique ID (GUID). Therefore, if you reinstall OpenVMS or restore a system disk from an image backup, you must first delete the old boot options, and then add a new boot option. To delete a boot option, use the Delete Boot Option(s) option in the EFI Boot Option Maintenance menu.

   ---

Still another method to add a boot entry to the EFI Boot Manager menu is to use the EFI Utilities for OpenVMS (I64 only) vms_bcfg command, which accepts OpenVMS device names and also allows you to set flags, as in the following example, where DKA0: is the OpenVMS system disk being added as the first boot option:

Shell> \efi\vms\vms_bcfg boot add 1 dka0: -fl 0,2 "HP OpenVMS I64"

Displaying EFI Boot Entries and Mapped OpenVMS Devices   

The Integrity server EFI Boot Manger shows the various paths to the boot device. You can use the OpenVMS I64 Boot Manager (BOOT_OPTIONS.COM) utility to display the OpenVMS boot device options known to EFI.

Start the utility at the DCL prompt (@SYS$MANAGER:BOOT_OPTIONS.COM) and select option 2 from the main menu (the main menu is shown in Setting Automatic Booting and Boot Flags for Your System Disk). The utility displays the following prompt. In this example, the listings for the DQA0: device are requested and displayed.

    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):DQA0
 
 EFI Boot Options list:   Timeout = 20 secs.
 -------------------------------------------------------------------------------
 04. DQA0 PCI(0|0|2|0) ATA(Primary,Master) "DVD-ROM "
 -------------------------------------------------------------------------------
 1 entries found.

You can also display all bootable devices mapped by the EFI console and their equivalent OpenVMS device names by using the EFI Utilities for OpenVMS vms_show command at the EFI Shell prompt (from \efi\vms). For more information about EFI utilities for OpenVMS, refer to the HP OpenVMS System Management Utilities Reference Manual.

Setting EFI Boot Option Timeout  

Whenever the EFI Boot Manager menu displays, it waits for you to select an option. By default, it waits 10 seconds, after which EFI boots the first boot option. If the first option is not available or does not boot, EFI waits the same duration before booting the next option in the list. The OpenVMS I64 Boot Manager (BOOT_OPTIONS.COM) utility allows you to change the duration for this timeout value and also to disable the timeout (so that there is no wait) and enable it.

Start the utility at the DCL prompt (@SYS$MANAGER:BOOT_OPTIONS.COM) and select option 6 from the main menu (the main menu is shown in Setting Automatic Booting and Boot Flags for Your System Disk). The utility displays the following prompt. To change the value, enter YES and then enter the new value. In this example, the timeout value is changed to 20 seconds.

    efi$bcfg: Boot Timeout period is 10 secs
    
    Would you like to modify the Timeout value? (Yes/No) [NO] YES
 
    Please enter the Timeout value in seconds: 20
 
     efi$bcfg: Boot Timeout period is 20 secs

    Please enter the Timeout value in seconds: 0
 
      efi$bcfg: Boot Timeout is Disabled

Writing a New Boot Block 

The boot block is block 0 of the system disk. It contains the size and location of the primary bootstrap image (IPB.EXE) used to boot the system. If you suspect that the boot block on your system disk is invalid, you can use the DCL command SET BOOTBLOCK to write a new boot block (this command functions similarly to the Writeboot utility, WRITEBOOT.EXE, used on OpenVMS Alpha systems; however, do not use the Writeboot utility on OpenVMS I64 systems).

The SET BOOTBLOCK command allows you to create a bootable OpenVMS I64 system disk from one that was originally created by one of the following methods:

• A version of BACKUP that does not support the OpenVMS I64 system disk structure



• A nonimage backup of an OpenVMS I64 system disk (possibly corrupting the boot block and various directory backlinks that must be manually reset)



• A nonimage restore of an OpenVMS I64 system disk from an image save set

The SET BOOTBLOCK command also allows you to rewrite the boot block of an OpenVMS I64 system disk to point to a new version of the OpenVMS I64 primary bootstrap file (SYS$EFI.SYS) that you have previously copied to the disk.

To write a boot block onto a disk, enter the following command:

$ SET BOOTBLOCK [bootfile-name]

Alternatively, you can write a boot block by entering the following command:

$ RUN SYS$SYSTEM:SYS$SETBOOT

Alpha and Equivalent Integrity Server System Boot Commands 

The Extensible Firmware Interface (EFI) on Integrity servers performs most of the same functions that the SRM console (P00>) does on Alpha processors. If you are familiar with the Alpha tool, use the following table to find EFI commands equivalent to the Alpha commands you commonly use on Alpha systems. Note some of the commands listed might not be available on certain hardware systems.

Table 4  Alpha and Integrity Server EFI Command Equivalents

To perform the following:	Alpha SRM command at P00> prompt:	Integrity Server EFI command at Shell prompt:
Display help information	HELP	help
Display list and version of devices found on the most recently initialized system	SHOW CONFIGURATION or SHOW VERSION	info fw
Display devices and controllers in the system, including bootable devices and mappings	SHOW DEVICE	map, vms_show devices (from \efi\vms), or @SYS$MANAGER:BOOT_OPTIONS.COM1
Display all system information:	SHOW FRU	info all, or pci, or info io
Display memory information	SHOW MEMORY	info mem
Display volume information of the file system	SHOW DEV DKA0	vol fs0
Display hardware information about the CPU	SHOW CONFIGURATION	info cpu
Display power status	SHOW POWER	info all2
Set system dump disk	SET DUMP_DEV disk1, disk2...	vms_set dump_dev disk1, disk2, ... (from \efi\vms) or @SYS$MANAGER:BOOT_OPTIONS.COM
To set boot flags:	SET BOOT_OSFLAGS 0,0	set vms_flags "0,0" or @SYS$MANAGER:BOOT_OPTIONS.COM
To set boot behavior to automatic boot:	SET AUTO_ACTION BOOT	bcfg boot add 1 fsx:\efi\vms\vms_loader.efi "I64" or @SYS$MANAGER:BOOT_OPTIONS.COM
To change the current boot option:	SET AUTO_ACTION HALT	bcfg boot mv 1 2 or @SYS$MANAGER:BOOT_OPTIONS.COM

1	BOOT_OPTIONS.COM displays only the boot entries and also a selected dump device for DOSD and a debug device; vms_show can display all devices mapped by the EFI console and their equivalent OpenVMS device names. The map command shows all devices currently mapped on the EFI Shell.

2	Best source of information about power status is the MP PS command.

( Number takes you back )

Booting Operations

Halt and Shutdown Procedures