HP OpenVMS Version 8.2 Upgrade and Installation...

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

Accessing the Baseboard Management Controller (BMC)

Configuring and Managing Booting of Your Integrity server

Booting Operations  

Note that HP Integrity servers maintain a System Event Log (SEL) within system console storage, and OpenVMS I64 automatically transfers the contents of the SEL into the OpenVMS error log. During a successful boot operation while using a console, you might see a message indicating that the Baseboard Management Controller (BMC) 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, enter the clearlogs SEL command at the EFI Shell prompt as in the following example: Shell> clearlogs sel This command deletes the contents of the SEL. The command is available with current system firmware versions. If your Integrity server is configured with a Management Processor (MP) and you see a BMC event log warning while connected to the MP console, you can also clear the BMC event log by using MP. Press Ctrl/B to revert to the MP> prompt. At the MP> prompt, enter SL (from the main menu) and use the C option to clear the log. 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.

Booting the OpenVMS I64 Operating Environment DVD  

After powering on your system and performing any other tasks to set up the system, you can boot the OpenVMS I64 Operating Environment DVD.

1. Insert the OpenVMS software DVD into the DVD/CD drive on the front panel of the server.
2. To ensure that EFI can access the DVD, enter the following command at the EFI Shell prompt:

   Shell> map -r

3. To boot the Operating Environment DVD, type the following command at the EFI Shell prompt, where fs0: is the Integrity server DVD drive. For a new Integrity server, the DVD drive is normally fs0:. If installations have been performed already on your server, then the DVD drive might be at another location.

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

   If this command does not work or you have doubts about which device maps to the DVD drive, you can use the EFI Boot Manager menu system to boot the Operating Environment DVD, as explained in steps a through f:
   
   
   1. To use the EFI Boot Manager menu system to boot the Operating Environment DVD, go to the EFI Boot Maintenance Manager menu. If you have just powered up your system and are at the EFI prompt, do the following to get to the EFI Boot Maintenance Manager screen:
      
      
      1. Enter the Exit command at the EFI Shell prompt. This takes you to the main EFI Boot Manager screen.
      2. From the Boot Manager menu, select the Boot Option Maintenance Menu option.
   2. From the EFI Boot Maintenance Manager menu, select the Boot from a File option, as shown in the following example. To navigate up or down, use either the letter v or the caret (^) on your keyboard, or the up or downarrow keys, and press Return to toggle your selection.
      
   3. A menu similar to the following appears. Select the "CDROM (Entry0)" line, as in the following example, and press Return.
      
      
   4. A screen appears that shows the top-level directory structure of the DVD, similar to the screen in the following example. Select the efi directory, as in the following example.
      
   5. The next screen to appear shows the first level of subdirectories below the top level, similar to the following example. Select the boot" directory (contains the boot file) as in the following example:
      
   6. The following screen displays the files within the boot directory. Select the file named bootia64.efi, as in the following example:
      

You can now install your OpenVMS I64 operating system onto the target disk; see Installing the OpenVMS Operating System onto a System Disk.

Booting Manually from the System Disk  

Boot the OpenVMS I64 operating system disk manually as follows:

IF ...	THEN GO TO...
The OpenVMS I64 operating system is running	Step 1.
The OpenVMS I64 operating system is not running	Step 4.

On Integrity server systems, HP recommends setting up your system with a boot option for your system disk (preferrably, so that it boots automatically on powering on or reboot). Add your system disk as a boot option in the EFI Boot Manager menu by using the OpenVMS I64 Boot Manager (BOOT_OPTIONS.COM) utility, as explained in Setting Automatic Booting and Boot Flags for Your System Disk. Another method for setting up your system disk to boot automatically is described in Manually Setting Automatic Booting of Your System Disk.

1. Log in to the SYSTEM account.
2. Enter the following command and press Return:

   $ @SYS$SYSTEM:SHUTDOWN

3. Answer the questions displayed by the system. When the procedure asks whether an automatic reboot should be performed, press Return for NO. When the procedure is finished, it displays the following message:

   SYSTEM SHUTDOWN COMPLETE

4. Halt the system. (See Halt and Shutdown Procedures for more information about how to halt your Integrity server).
5. Boot the system disk manually by entering the following command at the EFI Shell prompt, where fsn: (such as fs1:) is the device associated with the system disk:

   Shell>fsn:\efi\vms\vms_loader.efi

Performing a Conversational (Interactive) Boot 

A conversational boot is most commonly used in research and development environments and during software upgrades. Perform a conversational boot to stop the boot process before it completes. The boot process stops after it loads SYS$SYSTEM:SYSBOOT.EXE and displays the SYSBOOT> prompt. At the SYSBOOT> prompt, you can enter specific OpenVMS System Generation utility (SYSGEN) commands to do the following:

• Examine system parameter values



• Change system parameter values



• Specify another parameter file



• Specify another system startup command procedure



• Select the default system parameter file (IA64VMSSYS.PAR) if you modified system parameters to values that render the system unbootable



• Specify a minimum startup

There are several ways to perform a conversational boot. The following procedure is the most direct:

IF ...	THEN GO TO...
The OpenVMS I64 operating system is running	Step 1.
The OpenVMS I64 operating system is not running,	Step 4.

1. Log in to the SYSTEM account.
2. Enter the following command and press Return:

   $ @SYS$SYSTEM:SHUTDOWN

3. Answer the questions displayed by the system. When the procedure asks whether an automatic reboot should be performed, press Return for NO. When the procedure is finished, it displays the following message:

   SYSTEM SHUTDOWN COMPLETE

4. Halt the system. (See Halt and Shutdown Procedures for more information about how to halt your Integrity server).
5. Begin the conversational boot by entering the following command at the EFI Shell prompt, where fsn: is the device (such as fs1:) associated with the system disk:

   Shell>fsn:\efi\vms\vms_loader.efi -flags 0,1

6. At the SYSBOOT> prompt, you can enter any of the SYSGEN commands listed in SYSGEN Commands Used in the SYSBOOT Procedure. For more information about these SYSGEN commands, refer to the HP OpenVMS System Management Utilities Reference Manual: M--Z.
7. When you finish using the SYSGEN commands, enter the CONTINUE command to complete the boot process.

Table 2   SYSGEN Commands Used in the SYSBOOT Procedure

Command	Description
CONTINUE	Resumes the boot procedure.
DISABLE CHECKS	Inhibits checking of parameter values specified with the SET command.
ENABLE CHECKS	Permits checking of parameter values specified with the SET command.
HELP	Displays a summary of the SYSBOOT commands on the terminal screen.
SET parameter-name	Establishes the value of a system parameter.
SET/STARTUP	Sets the name of the system startup command procedure.
SHOW [parameter]	Displays active, current, default, maximum, and minimum values for specific parameters. (Use qualifiers to display characteristics of parameters grouped by categories.)
USE [file-spec]	Specifies a parameter file to be used as a source of values. You must enter the entire file specification, including device and directory; you cannot specify a logical name.
USE DEFAULT	Specifies that default values be used for all parameters.

For examples of using conversational booting, see Booting with Minimum Startup and Booting in an Emergency.

Booting with Minimum Startup  

In certain cases, you might want to boot your system without performing the full sequence of startup events. For example, if a startup event prevents you from logging in, you might want to boot the system without executing the startup so that you can log in and fix the problem. You can use the conversational boot to specify a minimum startup.

Because this procedure bypasses specific startup operations, it does not autoconfigure the system's peripheral devices.

1. Begin the conversational boot by entering the following command at the EFI Shell prompt, where fsn: is the device (such as fs1:) associated with the system disk:

   Shell>fsn:\efi\vms\vms_loader.efi -flags 0,1

2. Enter the following command and press Return:

   SYSBOOT> SET STARTUP_P1 "MIN"

3. Enter the following command to ensure that the operating system does not record for subsequent system reboots the STARTUP_P1 parameter change you made in step 2:

   SYSBOOT> SET WRITESYSPARAMS 0

4. Enter the following command to continue booting:

   SYSBOOT> CONTINUE

Booting with the XDelta Utility (XDELTA) 

The XDelta utility (XDELTA) is a debugging tool that system programmers use. The procedure for booting all Integrity servers with XDELTA is the same.

The following table describes the valid values you can specify when booting with XDELTA:

Value	System Response
0	Normal, nonstop boot (default).
1	Begins a conversational boot and then displays the SYSBOOT prompt.
2	Includes XDELTA but does not take the initial breakpoint.
3	Displays the SYSBOOT prompt and includes XDELTA but does not take the initial breakpoint.
6	Includes XDELTA and takes the initial breakpoint.
7	Includes XDELTA, displays the SYSBOOT prompt, and takes the initial breakpoint at system initialization.

The following is an example of booting with XDELTA from fs1: at the EFI> prompt:

EFI> fs1:\efi\vms\vms_loader.efi -flags 0,7

Booting from a Different Root Directory 

By default, the OpenVMS I64 operating system is installed in the system root directory [SYS0]. However, if you have created a cluster system disk, you can use the SYS$MANAGER:CLUSTER_CONFIG.COM procedure to add a copy of the operating system to a different root directory. (Refer to the HP OpenVMS System Manager's Manual for more information about using the SYS$MANAGER:CLUSTER_CONFIG.COM procedure.)

To boot from a different root (for example, [SYS3]), enter the following command at the EFI Shell prompt, where fsn: (such as fs1:) is the device associated with the system disk:

Shell>fsn:\efi\vms\vms_loader.efi -flags 3,0

Booting in an Emergency  

If a system problem prevents your system from booting, you might need to perform an emergency boot operation. Emergency Boot Procedures summarizes these emergency boot operations, and the sections that follow describe each boot operation in more detail.

Table 3   Emergency Boot Procedures

Operation	When to Use
Booting with default system parameters	When parameter values in the parameter file have been modified so that the system is unbootable
Booting without startup and login procedures	If an error in the startup or login procedure prevents you from logging in
Booting without the user authorization file	If you have forgotten the password and cannot log in to a privileged account

Booting with Default System Parameters 

If the current values stored in the parameter file have been incorrectly modified, these incorrect values might cause the system to become unbootable. With a conversational boot operation, you can reset the active values for all system parameters to the default value. (In most cases, HP recommends that you use AUTOGEN to modify system parameters. In certain cases, however, you can use a conversational boot to modify a parameter value temporarily. To change a parameter value permanently, you must edit MODPARAMS.DAT and run AUTOGEN. For instructions, refer to the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.) The default values allow you to boot the system temporarily so you can correct the problem.

How to Perform This Task

1. Begin the conversational boot by entering the following command at the EFI Shell prompt, where fsn: (such as fs1:) is the device associated with the system disk:

   Shell>fsn:\efi\vms\vms_loader.efi -flags 0,1

2. At the SYSBOOT> prompt, enter the following command:

   SYSBOOT> USE DEFAULT

   The USE DEFAULT command specifies that default values should be used for all parameters.
3. To avoid starting all layered products on a system that is not tuned for them, possibly causing the system to hang, set the STARTUP_P1 system parameter as follows:

   SYSBOOT>  SET STARTUP_P1 "MIN" 

4. Enter the following command to ensure that the operating system does not record for subsequent system reboots the STARTUP_P1 parameter change you made in step 3:

   SYSBOOT> SET WRITESYSPARAMS 0

5. Enter the following command to continue booting:

   SYSBOOT> CONTINUE

6. When the system finishes booting, determine which changed parameter caused the problem and reset the parameter value. If you specified the value for the parameter in the AUTOGEN parameter file MODPARAMS.DAT, fix the value in that file and run AUTOGEN. For more information, refer to the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.
7. Shut down and reboot the system.

Example

SYSBOOT> USE DEFAULT                        
SYSBOOT> SET STARTUP_P1 "MIN" 
SYSBOOT> SET WRITESYSPARAMS 0
SYSBOOT> CONTINUE 
Username: SYSTEM
Password:
$ EDIT SYS$SYSTEM:MODPARAMS.DAT
.
.
.
[Insert line(s) to reset parameter value(s)]
.
.
.
$ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT 

Booting without Startup and Login Procedures 

If the system does not complete the startup procedures or does not allow you to log in, you might need to bypass the startup and login procedures. The startup and login procedures provided by HP should always work. However, if you introduce an error when modifying the startup or login procedure, it is possible to accidentally lock yourself out of the system.

How to Perform This Task

1. Begin the conversational boot by entering entering the following command at the EFI Shell prompt, where fsn: (such as fs1:) is the device associated with the system disk:

   Shell>fsn:\efi\vms\vms_loader.efi -flags 0,1

2. Enter the following command at the SYSBOOT> prompt:

   SYSBOOT> SET/STARTUP OPA0:

3. Enter the following command to ensure that the operating system does not record for subsequent system reboots the STARTUP_P1 parameter change you made in step 2:

   SYSBOOT> SET WRITESYSPARAMS 0

4. Enter the following command to continue booting:

   SYSBOOT> CONTINUE

5. When the system is booted, the operator console displays the DCL command prompt ($). You are logged in.
6. Enter the following DCL command:

   $ SET NOON

   This command directs the operating system to ignore any errors that might occur. If you do not enter this command and you invoke an error, the system logs you out.
7. Correct the error condition that caused the login failure. (That is, make the necessary repairs to the startup or login procedure, or to the SYSUAF.DAT file.)
   
   Invoke a text editor to correct the startup or login file. Note that some system consoles might not supply a screen-mode editor. You can also copy a corrected file and delete the incorrect version by using the RENAME and DELETE commands.
8. Perform a normal startup by entering the following command:

   $ @SYS$SYSTEM:STARTUP

Example

SYSBOOT> SET/STARTUP OPA0:
SYSBOOT> SET WRITESYSPARAMS 0
SYSBOOT> CONTINUE
$ SET NOON
$ SET DEFAULT SYS$SYSROOT:[SYSEXE]
$ @SYS$SYSTEM:STARTUP

Booting without a User Authorization File 

Ordinarily, the startup and login procedures provided by HP always work; however, certain conditions can cause them to fail. A simple way to lock yourself out of the system is to set passwords to login accounts and forget them. Another way to be locked out is if one or more core system Product Authorization Key (PAK) software licenses are unavailable or expired. In such emergencies, perform a conversational emergency boot by following the steps given in this section.

How to Perform This Task

1. Halt the system. (See Halt and Shutdown Procedures for more information about how to halt your Integrity server.)
2. Begin the conversational boot by entering the following command at the EFI Shell prompt, where fsn: (such as fs1:) is the device associated with the system disk:

   Shell>fsn:\efi\vms\vms_loader.efi -flags 0,1

   
   
   You need your hardware system's password for logging in to the console. By default, both the user name and password are set to "Admin". If you do not have this password, contact HP customer support to reset the hardware console password.
3. Enter the following commands at the SYSBOOT> prompt:

   SYSBOOT> SET/STARTUP OPA0:
   SYSBOOT> SET WINDOW_SYSTEM 0
   SYSBOOT> SET WRITESYSPARAMS 0
   SYSBOOT> CONTINUE

   The first three commands request that:
   • OpenVMS read the system startup commands directly from the system console.
   
   
   
   • The Windows system (if any) not start.
   
   
   
   • OpenVMS not record the parameter changes for subsequent system reboots.
   
   
   The last command causes the booting to continue.
4. At the DCL prompt, the system now accepts startup commands directly from the console. Enter the following two commands as shown. These commands allow a normal system startup while you are left logged in on the console. Without the SPAWN command, you would be logged out when the startup completes.

   $ SPAWN
   $ @SYS$SYSTEM:STARTUP

5. Once you log out of this session, the system completes the startup and can be used normally. Optionally, you can choose to reboot the system.

Instead of using the SET/STARTUP OPA0: command, an alternative method of booting under these emergency conditions is to set the UAFALTERNATE system parameter to use the alternate authorization file rather than the standard user authorization file. Setting the system parameter UAFALTERNATE defines the logical name SYSUAF to refer to the file SYS$SYSTEM:SYSUAFALT.DAT. If this file is found during a normal login, the system uses it to validate the account and prompts you for the user name and password. HP does not recommend this method. If an alternate SYSUAFALT.DAT file has been configured on your system, the UAFALTERNATE method will likely fail (assuming you do not know the password for the privileged account stored within the SYSUAFALT.DAT file). In addition, the OPA0: system console is critical to system operations and system security and allows access when the SYSUAF system authorization database is unavailable or corrupted; when core product license PAKs are not registered, are expired, or are disabled; and in various system failures.

SYSBOOT> SET/STARTUP OPA0:
SYSBOOT> SET WINDOW_SYSTEM 0
SYSBOOT> SET WRITESYSPARAMS 0
SYSBOOT> CONTINUE
$ SPAWN
$ @SYS$SYSTEM:STARTUP
$ 

Accessing the Baseboard Management Controller (BMC)

Configuring and Managing Booting of Your Integrity server