 |
» |
|
|
|
This appendix briefly describes the configuration
and management tools that might be available on HP Integrity servers,
and explains how to set up the system console, configure boot options,
boot the OpenVMS I64 operating system, and shut down the operating
system. The appendix also includes brief troubleshooting procedures. Specifically, this appendix contains the following
information: Hardware/firmware configuration
and management interfaces and their features Setting up your system
console Overview of using the
Extensible Firmware Interface (EFI) Enabling or disabling Hyper-Threading on nPartitions that have dual-core processors
that support it Configuring and managing
boot operations such as the following: Setting the system for
automatic booting Setting and showing boot
devices
Booting operations, including
the following: Performing a conversational
(interactive) boot Booting with minimum startup Booting with the XDelta
utility (XDELTA) Booting from a different
root directory
Halting and shutting down
operations Troubleshooting procedures
This section provides a brief overview of the
configuration and management utilities that are typically available
for your Integrity server system. For more information, see the
appropriate hardware documentation. A.1.1 Overview of Utilities and Console Options | |
The main interfaces that are typically available
for configuring and managing your HP Integrity server environment
are the Extensible Firmware Interface (EFI) and the Management Processor
(MP). On entry-class Integrity servers, MP has been replaced by the
Integrated Lights Out (iLO) Management Processor, which includes all
the functionality of MP plus additional features. On some models,
the Baseboard Management Control (BMC) utility is provided. Cell-based
servers include additional management tools. EFI is the main boot and preboot interface; it
is the core interface to the system firmware and console commands
on all models. BMC is provided on entry-class HP Integrity servers
(although on a few systems the interface itself is hidden). BMC provides
basic management capabilities and access to EFI. MP (or iLO) is available
on most systems; on some systems it is available only if the necessary
console hardware has been installed and configured. In addition to
providing access to EFI, MP provides advanced management functionality
(beyond that which is available through BMC), including remote management,
network console and Web-based access, and enhanced diagnostic capabilities.
Both BMC and MP (iLO) can operate on standby power—even when
the Integrity server’s main power switch is turned to the off
position. EFI is the base console environment. You can either
use MP (iLO) or BMC to interact with the capabilities of the console
interface. The OpenVMS I64 installation and upgrade procedures
assist you in adding a boot option for your newly installed or upgraded
system disk. Before you can boot your OpenVMS system, your console
must be configured correctly, as explained in Section A.2. The following briefly describes some of the main
features of EFI, MP, and BMC.
Extensible Firmware Interface (EFI) EFI is a menu and command-line interface
between the operating system and the system firmware. The EFI interface
is available only when the operating system is not booted; on cell-based
servers, the interface is available from an nPartition console when
the nPartition is in an active state but has not booted an operating
system. To configure EFI boot options while the operating system
is running, OpenVMS provides the OpenVMS I64 Boot Manager utility
(SYS$MANAGER:BOOT_OPTIONS.COM). Changes made by this utility do not
take effect until the system is rebooted. The EFI Boot Manager, like the OpenVMS I64 Boot Manager, provides
support for operating system loaders and enables you to configure
the firmware and control the booting environment for your OpenVMS
operating system. A FAT partition on the boot disk stores the system
loader. The Boot Configuration menu (or in some versions of EFI,
the Boot Option Maintenance Menu) enables you to add or delete a boot
option, change the boot order, select the active console, and more.
After you power up the server, the EFI boot manager presents different
ways to bring up the system, depending on how you have set up the
boot options. For example, you can boot to the EFI Shell. When you
select the EFI Shell command-line interface option, you can enter
commands at the EFI Shell prompt. For more information about EFI
options and commands, see Section A.3 and the appropriate hardware documentation. | | | |  | NOTE: In some HP documents, you might see the acronym POSSE used in place of or in combination with EFI. EFI is an Intel® specification of an interface between
firmware and the operating system. POSSE (Pre-OS System Environment)
is the HP implementation of EFI that extends the EFI Shell and EFI
Boot Manager to include additional features for managing hardware
and system boot options. | | | | |
Management Processor (MP) Management Processor
(or, on entry-class Integrity servers, iLO) provides both local and
remote access for controlling the system console, reset/power management,
and transfer of control (TOC) capabilities. It also enables you to
monitor tasks and display detailed information about various internal
subsystems. On cell-based servers, MP is a complex-wide tool and
is always available, even if nPartitions are not configured or booted
in the server complex. In contrast, EFI does not operate as a complex-wide
tool and is only available when the nPartition is in an active state
but has not booted an operating system; each nPartition has its own
EFI interface. Using MP, you can select the partition for which you
want EFI access. You can access all hardware and nPartitions in the
complex. The following is a brief summary of MP’s main features: Console connectivity As a console interface,
MP enables you to interact with EFI and to power the server on or
off; ultimately, it can function as the OPA0: terminal port on OpenVMS. Virtual Front Panel (VFP) MP provides
a virtual front panel that you can use to monitor the front panel
LEDs from a remote location. Command interface MP provides an extensive
menu system and a command-line interface. Multiple, simultaneous viewers Multiple
users can access the MP console or a particular nPartition console.
Only one user at a time is allowed interactive access. All other
users have read-only access. (Output from the interactive user is
reflected to the read-only users currently accessing the console.)
Access to MP can be restricted by password-protected user accounts. Availability/standby power MP is available
whenever the system is connected to a power source, even if the server’s
main power switch is in the off position. Accessibility MP is accessible in several
ways, including by direct monitor connection using a terminal, PC,
laptop or desktop computer connected to the MP serial port (with certain
Integrity servers, you can also use a VGA monitor and USB keyboard
and mouse); by modem through an EIA-232 port; or by Telnet or Web
browser on the LAN. MP is accessible through Secure Shell (SSH),
which is provided by TCP/IP Services for OpenVMS. This method of
access is more secure than any of the other methods. Console log MP records recent output from
the system console. The cl command enables you
to view the recorded information. Event logs MP includes event logs that
include information about system events and booting. The sl command displays the contents of system status logs.
On some systems, such as the rx1600, MP is optional.
For more information about MP options and commands, see the appropriate
hardware documentation. | | | | | NOTE: MP provides much more functionality than BMC and might be more
appropriate for your needs. On some systems, MP is an optional component
and on others it is built into the system. | | | | |
Baseboard Management Controller (BMC) BMC is more limited in functionality than MP. BMC enables you to
control some management features built into the system board, such
as diagnostics, configuration, and hardware management. BMC provides
a console connection on some systems. As with MP, BMC enables you
to interact with EFI; it can function as the OPA0: terminal port
on OpenVMS. BMC also operates on standby power. However, BMC is
accessible only through the serial port on the back of the system.
BMC commands enable you to control the BMC interface, view logs,
get help, display firmware revisions, reset the system, turn the system
locator LED on or off, and change the BMC password.BMC is not provided
on cell-based Integrity servers. On some systems, such as the rx4640,
the BMC user interface is hidden but is still present and functional.
For more information about BMC commands, see the appropriate hardware
documentation.
A.1.2 Configuration and Management Utilities on Cell-Based Servers | |
For the more complex environments provided by
cell-based Integrity servers, a wider variety of tools is provided.
Systems with multiple nPartitions provide a separate EFI interface
for each nPartition. MP provides access to, and allows management
across, the complex and each nPartition EFI interface. In addition to MP and EFI (cell-based servers
do not provide BMC), these systems offer Partition Manager and other
tools that vary from system to system and operating system to operating
system. The Partition Manager (parmgr) utility provides a graphical
interface for managing nPartitions and complex hardware. It centralizes
all nPartition management functions in one place, providing the system
manager with the tools to dynamically reconfigure, power on, power
off, create, delete, and modify nPartitions to ensure smooth and well-controlled
operation. Partition Manager can be run on HP-UX or Microsoft Windows
systems. You can use either version of Partition Manager to manage
nPartitions for OpenVMS Version 8.3-1H1. Partition Manager is a
free product that you can download from the following website (PARMGR
must be uppercase as shown): http://www.docs.hp.com/en/PARMGR2/download.html For more information about Partition Manager,
see the nPartition Administrator's Guide (previously titled HP System Partitions Guide: Administration
for nPartitions). For more information about these and other tools
available for configuring or managing Integrity servers, see the appropriate
hardware documentation. A.1.3 Using the Delete or Backspace Key with Integrity Server Utilities | |
Some versions of the EFI environment and the MP
and BMC console interfaces on Integrity server systems still interpret
the Delete (or Backspace) key as
do UNIX systems, which is different from the way OpenVMS Alpha systems
or Microsoft Windows systems interpret it. Whereas the OpenVMS operating
system uses the ASCII DEL/RUBOUT character (7F hexadecimal) to delete
the last character typed in a command line, these Integrity server
facilities use Ctrl/H. When you
enter commands for these Integrity servers, if you press Delete at 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. You can remap a terminal so that the Delete key removes the last character typed by adding the following command
to your login command procedure (generally, LOGIN.COM): $ SET TERMINAL/BACKSPACE=DELETE |
This command remaps Ctrl/H to DEL. The driver does not remap these keys if the terminal
is in one of the following states: Terminal attribute is set to PASSALL Terminal attribute is set to PASTHRU Ctrl/V is entered,
which tells the driver to pass the next character and skip the remap
check.
Alternatively, you can set up your terminal emulator
so that the Backspace key deletes the last character
typed. However, for the key to work properly on OpenVMS, you must
still enter the SET TERMINAL command described earlier. You must set up the firmware console as described
in the hardware or firmware documentation provided with your Integrity
server. When first powered on, Integrity servers interact with the
firmware interface and accept input from one or more console devices.
These devices include the Integrity iLO MP (or simply MP on some servers;
for simplicity, this section refers to MP for both firmware interfaces),
serial ports, and if present, local graphics monitor and keyboard.
The default console devices enabled for use by the firmware depend
on the Integrity server hardware model and associated firmware (see
your hardware documentation). The MP port is typically used by the
OpenVMS operating system on an Integrity server (recommended by HP).
This port provides serial access as well as networked access to the
firmware console. If using the serial port, use a VT100–capable
terminal or emulator device. On Integrity servers that do not have
an MP port, the console serial port (generally on the back of the
server) is enabled. With the exception of some older Integrity server
models, such as the HP Integrity rx2600 server, the current firmware
available for Integrity servers provides a text menu-based interface
by default. The current firmware also includes the concept of console
interfaces that are “Primary,”“Secondary,”and “Not Configured.” The Primary console is the console
enabled for interacting with the operating system as well as with
the firmware. Although the firmware can interact with multiple console
devices, OpenVMS uses only one of these devices as its console and
requires that one device be selected. You select one device to serve
as the Primary console, as explained in Section A.2.1 where more details are also given about
the Primary, Secondary, and Not Configured console selections. When an Integrity server is powered up, the firmware
displays information to the Primary and Secondary console devices.
If you do not see output within a few seconds of powering up, your
console device is probably not selected as a Primary or Secondary
device; you will need to connect your console terminal cable to the
appropriate device. When connected to the correct device, the firmware
displays the EFI Boot Manager screen, from where you can begin to
navigate to select the Primary console for use by OpenVMS, as explained
later in this section. When using the firmware to boot OpenVMS, if
you do not see OpenVMS console output and the system appears hung,
your console terminal device might be connected to a Secondary console
device instead of the Primary console device. If you are already using the system console,
you can disregard the remainder of this section. If you have ordered
a machine with OpenVMS preinstalled, your console selections have
been chosen for you, but you might want to change these default console
selections. If you have changed your system configuration, or if
you are installing OpenVMS on a new (uninstalled) Integrity server,
or if you are reinstalling OpenVMS using the INITIALIZE option (removing
all the software and data files that were previously installed on
the target system disk), you might need to select the correct console.
If the correct console is not selected, OpenVMS might use an unexpected
device as the console, causing your system to appear to be hanging;
or OpenVMS either will fail to boot or will boot with output sent
to the wrong location. You can use MP to establish remote console
access, such as through the TELNET utility provided with HP TCP/IP
Services for OpenVMS. Alternatively, you can access the MP console
interface through the Internet using an Internet browser.If you intend to set up LAN or remote access for an MP console interface,
you must initially use the serial port for console operations when
you set up the Integrity server for the first time. (See your hardware
documentation for instructions on setting LAN or remote access for
the MP console interface.) Your first step is to decide what console to use.
Depending on your hardware/firmware configuration, OpenVMS can use
one of the following types of consoles: MP (or iLO MP) serial port The MP interface
is not visible to OpenVMS unless the MP serial port is selected as
the Primary console. Graphics (VGA) device Graphics console
support is introduced with OpenVMS Version 8.3–1H1. This allows
you to use a monitor and a USB keyboard and mouse connected directly
to the Integrity server ports available for such purposes. Certain
older (legacy) Integrity servers, such as the rx2600, do not support
a graphics console because they lack the required firmware capabilities.
On some Integrity servers, a VGA device might not be built into the
system, in which case a graphics option card is required for VGA console
support. Most Integrity servers support multiple graphics options; the exceptions
are the rx1600 and rx1620 servers. A graphics option consists of a
graphics card and a graphics display interface (monitor). When multiple
graphics devices are present, you can select only one device for use
by the firmware as a console device. The other graphics devices must
be set to Not Configured (NC). When DECwindows is used on a system
booted using the VGA as the OpenVMS console, DECwindows selects the
VGA console as the default screen. When enabling multihead DECwindows
graphics operation, the VGA console defaults to screen 0. If no VGA
device is configured as a console, DECwindows selects a default screen
based on the Integrity server model and device bus ordering. For details
about enabling multihead DECwindows graphics operation, see Section 7.7.3. Note the following restrictions: OpenVMS supports up to four add-on graphics devices
plus any built-in graphics, depending on the Integrity server and
available slots. The firmware available on some Integrity servers
might limit which devices can be used as a VGA console device. For
information about your specific configuration's platform and graphics
configuration rules, see your hardware documentation . For correct operation of the VGA console, OpenVMS
requires that at least one other non-VGA device be configured as the
Secondary console. XDELTA is not available when using the VGA console;
it is disabled when requested. Conversational (interactive) boot (SYSBOOT>) is not
supported with the VGA console. To change SYSGEN parameters, use SYSGEN
from OpenVMS, or boot OpenVMS from a non-VGA console for conversational
boot. When
using a VGA console and installing from vMedia or a USB DVD drive
with the keyboard plugged into a USB hub, the keyboard might not be
operational initially. To enable keyboard operation, simply unplug
the hub and plug it back in.
For more information, platform-specific details, and the firmware
required for VGA support, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes and the hardware documentation for your Integrity server. The procedure for selecting the correct console
varies according to the Integrity server model and firmware. For Integrity
servers other than the rx2600, follow the steps in Section A.2.1. For rx2600 Integrity
servers and servers for which you cannot obtain the required firmware,
follow the steps in Section A.2.2. | | | | | NOTE: Make sure your Integrity server has the latest firmware updates
installed. | | | | |
A.2.1 Selecting Your OpenVMS Console (Not Applicable to rx2600 Integrity
Servers) | |
On Integrity servers other than the rx2600 (or
on servers with outdated firmware), console devices can be configured
as one of the following three types: Primary console—The device enabled as a console
for the firmware interface and used as the OpenVMS console (OPA0).
If a VGA device (device path) is selected as the Primary console,
at least one serial device path must be set as a Secondary console
in order to use the VGA device to boot OpenVMS. Secondary console—A device enabled as a console
for the firmware but not used as the OpenVMS console during or after
booting. The device is configured as a normal serial port device.
Note that if you specify an MP port as the Secondary console, it will
not be visible to OpenVMS. The MP port is visible to OpenVMS only
when selected as a Primary console. If multiple serial ports are available
as a console on your Integrity server and you select one for a Secondary
console, do not use that console for transmission of binary data. Not Configured—A device that is not enabled
as a console for the firmware or operating system.
Your system can be booted from any Primary or Secondary
console but OpenVMS output displays only on the primary console. For
information about serial devices that can be selected as the console
and the serial device port enumeration, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes. You can select a console in one of two ways: The examples in the following two subsections
show how to select a VGA device for the OpenVMS console. A.2.1.1 Using the EFI Boot Manager to Select the OpenVMS ConsoleTo select the device for your OpenVMS console
using the EFI Boot Manager, follow these steps. Depending on the firmware
version and configuration, menu selections displayed on your screen
might differ from those seen in the examples . Note that with this
EFI firmware, you no longer have to select a console input device,
console output device, and console error device. The firmware automatically
sets the Primary console device to be the console input, console output,
and console error device. From the EFI Boot Manager
screen, use the up or down arrow key to select the Boot Configuration
menu and press Enter: From the Boot Configuration
menu, select the Console Configuration menu and press Enter: If the Console Configuration
menu shows that your preferred device is already configured as the
Primary console, you need not continue; otherwise, select the device
that you want as the OpenVMS Primary console. In the following screen,
the VGA device is selected: Enter P to
configure the selected device as the Primary console. You then see
the selected device as the Primary console: Press the Esc key to return to the previous menu. When prompted whether to save
changes to NVRAM, enter Y: When prompted whether to reset
the system, enter Y to make the changes take effect:
A.2.1.2 Using the EFI Shell to Select the OpenVMS ConsoleTo select the device for your OpenVMS console
using the EFI shell, follow these steps: At the EFI Shell prompt, enter
the conconfig command to view the index number
for the available console devices, as in the following example (the
column titled “Primary” displays how the device is configured
(P for Primary, S for Secondary, NC for Not Configured): Shell>conconfig
CONSOLE CONFIGURATION
Index Primary Type Device Path
----- ------- ----- ----------
1 P Serial Acpi (PNP0501,0)
2 S Serial Acpi (HWP0002,700)/Pci (1|1)
3 S VGA Acpi (HWP0002,700)/Pci (2|0) |
If your preferred device is
already configured as the Primary console, you need not continue.
If your preferred device is not currently configured as the Primary
console, enter the conconfig command in the following
format: conconfig index primary where index is the
index number of the device preferred for the OpenVMS console. In the
following example, the VGA device is selected as the Primary console,
and the resulting display reflects the configuration change: Shell>conconfig 3 primary
CONSOLE CONFIGURATION
Index Primary Type Device Path
----- ------- ----- ----------
1 S Serial Acpi (PNP0501,0)
2 S Serial Acpi (HWP0002,700)/Pci (1|1)
3 P VGA Acpi (HWP0002,700)/Pci (2|0) |
Enter the reset command to
make the changes active, as in the following example:
A.2.2 Selecting Your OpenVMS Console on rx2600 Integrity Servers | |
This section describes how to select a console
on rx2600 Integrity servers or other servers with outdated firmware.
On such servers, you must configure a Console Input, Console Output,
and Console Error Device for your OpenVMS console. There is no concept
of the Primary console that automatically configures these devices
for the OpenVMS console. In addition, on such servers OpenVMS does
not support graphics consoles. | | | | | NOTE: The following instructions assume that OpenVMS
is not installed on your Integrity server and that boot options are
not defined. | | | | |
Decide what console you want to use. Power on the system. If using an MP serial port, log in
to MP and access EFI. If you are setting the system serial
port as your system console, go to the next step now. If you are
setting the MP serial port as your system consoleand you have just
powered on your Integrity server, the MP console interface prompts
you to log in. (By default, both user name and password are set to
Admin. For security purposes, change the password immediately. See
your hardware documentation for more information.) | | | | | NOTE: To see the MP login user name and password prompts, you might
need to press Enter one or more times on your console
keyboard. If this does not work, try pressing Ctrl/B. If you see only the MP password prompt, press Enter 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.) If you see a message similar to the following, another user
has the console (only one user can write to the console, although
multiple users can view it). [Read only - use Ctrl-Ecf for console write access] |
To gain control of the console from the other user, press Ctrl/E, release the key combination, and
then immediately type the letters cf. Alternatively,
you can have the other user log off. Note that the system does not work if it is running MP firmware
older than version E02.22. For information about updating the MP
firmware, see Section 1.3.4. | | | | |
When the MP> prompt is displayed,
move to the EFI interface by entering the co (console
mode) command. If the power or initialization sequence has not completed,
you will see that and must wait until the menu reappears, at which
point reenter the co command to get to the EFI
Boot Manager menu. At the EFI Boot Manager menu, select the EFI Shell
interface. On Integrity servers without nPartitions, the co command brings you directly to the EFI Boot Manager
screen. If you do not enter a command before the EFI countdown timer
expires, the EFI Shell prompt is displayed. (On some servers, the
countdown timer is 10 seconds by default; on others, such as Server
Blades, it might be even less.) Note that when the operating system
is running, the co command brings you to the console
port of the operating system. On cell-based servers, unless you are using a
single-partition user account, the co command
first brings you to a console menu that lists the available nPartitions.
Select the appropriate nPartition to access the EFI Boot Manager
console for that nPartition. The following example shows a console
menu (menus and displays such as this might vary from system to system):
Partitions available:
# Name
--- ----
1) MIA1
2) MIA2
3) TESTING
4) LAN
5) AMYS
6) ACCNTS
Q) Quit
Please select partition number: |
If the co command results in
a screen that is unexpected or difficult to interpret, pressing Enter might help. If you are at an EFI submenu instead
of the main menu, navigate to the main menu by exiting from the submenu
and any subsequent submenus until you return to the EFI main menu. For more information about determining which nPartition
to access, see the nPartition Administrator's Guide (previously titled HP System Partitions Guide: Administration
for nPartitions) or the appropriate hardware documentation. Access the EFI Boot Configuration menu. The
EFI Boot Manager screen includes a boot menu. The default menu option
is highlighted, as shown in the following example: | | | | | NOTE: The appearance of EFI Boot Manager screens and menus differs
from version to version of the firmware. | | | | |
From the EFI
boot menu, select the Boot Configuration option (or, in some versions
of EFI, the Boot Option Maintenance Menu). To move to an option,
use the up or down arrow key. (With some terminal emulators, you might
have to use the letter v to scroll down or the caret (^) to scroll
up.) Press Enter to toggle the selection. If
you do not select an option within the countdown period, EFI moves
to the default option—the EFI Shell in the boot menu example,
in which case the EFI Shell prompt is displayed. Exit the EFI Shell
to return to the Boot Configuration menu. If lines from the preceding
screen linger and obscure the EFI Shell prompt, press Enter to bring the EFI Shell prompt into view. Configure the Console Input, Console Output, and Console
Error Devices. If you have the latest EFI firmware, select
the Console Configuration option from the Boot Configuration menu
to list the console input, console output, and console error device
options. Some versions of EFI list the three console device options
directly in the Boot Option Maintenance Menu. Configure each console
option one at a time, as follows: Select the console input device. EFI displays
a list of devices (device paths) available for console input. Select
only one device from this list, and deselect any unused devices.
The following is a sample list of devices, annotated with explanatory
text below the list. This example shows the devices for an entry-class
Integrity server; the procedure and display differ on cell-based servers.
For more information about the EFI paths used for console selection,
see the Intel Extensible Firmware Interface (EFI) documents available
from the Intel website.
| System Serial Port | These four lines indicate any of the valid devices
that you can define for the console using the system serial port.
Any line that has the notation Uart but not the notation Pci is
one of the system serial ports. Notice that the lines are almost
identical except for the text following the VenMsg portion indicating
the terminal emulation protocol such as VT100. Thus, each of the
four entries is the same device with different emulation protocols. | | MP Console | These four lines appear only on systems that have
an MP port. Any lines that include both Uart and Pci are MP serial
port devices. As with the serial port devices, these four lines refer
to the same device with different emulation protocols. | | VGA Device | This is the graphic console device. Do not select
this. OpenVMS does not support VGA graphics as a console output device
for booting on rx2600 Integrity servers. |
Select a device using the protocol appropriate
for your terminal emulator (in most cases, VT100+ is the best choice).
Select only one device line. OpenVMS does not operate if more than
one device is selected. Save your settings to NVRAM. Select the console output device. Repeat steps
a and b to configure the console output device. Select the same device
you selected for the console input device. Select the console error device. Repeat steps
a and b to configure the console error device (also referred to as
the standard error device). Select the same device you selected for
the console input and output devices.
Perform a cold reset if required. Your system
might require a cold reset. Newer versions of EFI do not require
a cold reset. For more information, see your hardware documentation.
At this point, you can boot the OpenVMS I64 DVD
to install the operating system onto a system disk. Follow the instructions
in Chapter 3 (specifics
for booting are provided in this appendix). | | | | | NOTE: Any time new potential console devices are added to a system,
or anytime NVRAM on a system is cleared, review your console selections.
When you change serial devices, you must also make changes to the
input, output, and error console device options to ensure proper operation. | | | | |
EFI is the basic interface
between the operating system and firmware on all Integrity server
systems; it is similar to SRM on Alpha systems. EFI provides a boot
option menu and the ability to configure boot options. EFI is accessible
when the operating system is not booted. On cell-based servers, EFI
is available when the nPartition is in an active state but has not
booted an operating system. Each nPartition has its own EFI interface
and system boot environment that enables you to interact with the
nPartition before an operating system has booted on it. When you first power on a new Integrity server
system, you see a series of diagnostic messages followed by the EFI
Boot Manager screen (unless MP is available, in which case you see
the MP login screen). However, if your Integrity server came with
the OpenVMS I64 operating system installed, then the OpenVMS I64 operating
system is the first option and it boots automatically. | | | | | NOTE: On some systems that include MP, you might first see the MP
login screen. In addition, on cell-based servers, you initially must
select the console for the nPartition you want to access. As noted
previously, the behavior of Integrity server systems can vary significantly
from model to model as well as from version to version of the firmware. | | | | |
To select an option from the EFI Boot Manager menu, use the
up or down arrow key to highlight an item (or for some (with some
terminal emulators, you might have to use the letter v to scroll down
and the caret (^) to scroll up), and then press Enter to activate the selection. You can use EFI to configure numerous
options for your Integrity server and OpenVMS operating system. For the first boot of a system on which OpenVMS
is not preinstalled, you probably need to use EFI to get started.
When you select the EFI Shell, the console displays much activity
before the EFI Shell prompt is displayed. If you do not see the EFI
Shell prompt, press Enter. (Note also that the EFI
Shell prompt might change, as explained in Section A.3.1.) The EFI boot menu lists boot options. Each item
in the boot options list references a specific boot device and provides
a specific set of boot options or arguments to be used when booting
the device. You can add boot options to the boot menu. The OpenVMS
installation procedure (as well as the upgrade procedure) can assist
you in adding and validating a boot option for your newly installed
system disk. The procedure uses the OpenVMS I64 Boot Manager utility
(SYS$MANAGER:BOOT_OPTIONS.COM) to add and validate boot options. You
can use this utility directly at the OpenVMS DCL prompt. HP recommends
using either of these methods for configuring boot options rather
than using EFI. The OpenVMS I64 Boot Manager utility is easier to
use than EFI and enables you to configure the most pertinent options
for your system (while OpenVMS is running), including the following: Display boot options known to the EFI Boot Manager. Add a boot option to the EFI Boot Manager so that
your system disk boots automatically when the system is powered on
or rebooted. Remove or change the position of a boot option in
the EFI Boot Manager list. Validate and fix the boot option list. Change how long EFI pauses before booting or rebooting.
Use of this utility is optional for most devices
but is required for configuring boot options on Fibre Channel devices.
HP recommends using this utility to add members of a multiple-member
shadow set to the boot list and dump device list. (Be sure to add
all members to both lists.) For instructions on how to use the utility,
see Section A.5. For more
information about configuring Fibre Channel devices with this utility,
see Appendix D. For information
about using the OpenVMS I64 Boot Manager utility to display boot options,
see Section A.5.2.2. For information
about setting the pause length, see Section A.5.2.3. The OpenVMS I64 Boot Manager utility
also enables you to configure dump off the system disk (DOSD) devices
and debug devices; for more information about this, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems. A.3.1 General Notes About Using EFI | |
Note the following: Using EFI on cell-based servers: On an Integrity server with nPartition support, a separate EFI
interface exists for each nPartition. Be sure to access the appropriate
nPartition console. To determine which nPartition EFI
interface you are using, use the info sys command
at the EFI Shell prompt. This lists the local nPartition number and
details about active cells. For processor details, use the info cpu command. (You can also use MP to provide information
about the nPartition you are using, as described in the nPartition Administrator's Guide (previously titled HP System Partitions Guide: Administration for nPartitions).) You can use the MP console interface to access any nPartition’s
EFI console. Press Ctrl/B to move
from EFI (or from your OpenVMS session) to the MP interface. Log
in to MP if you are prompted. A menu then displays the names of all
available nPartitions. Select from this list the nPartition that
you want to access. To gain console write access for an nPartition
console, press Ctrl/E and enter
the letters cf. You can use the MP pdcommand to set a default nPartition for MP login; this helps to ensure
you are brought to the intended nPartition (for example, to help prevent
you from accidentally reconfiguring an nPartition you do not own). To return to the EFI console (when OpenVMS is not booted), enter
the co command at the MP> prompt. Navigating EFI file system directories: To switch to a different file system, enter the file system name.
The following example shows how to switch to fs3: from the current
location (top level of the EFI Shell): Note
that the prompt is now fs3:\. The EFI Shell prompt changes to reflect
the file system currently accessed. The Shell prompt is displayed
again if you reset the system. Also note that the file system number
might change when remapped after hardware changes are made to the
server (for example, after an I/O drive is added to the server and
the nPartition boots or the map -r command is issued). File structure of EFI file systems: The file structure of an fs disk is identical to MS-DOS and the
commands to move around the structure are similar to MS-DOS commands.
For example, to move to directory efi on disk fs0:, enter the cdcommand: To
display the contents of the efi directory, use
the dircommand. Boot device list: Any changes in storage configuration after the system
is booted to EFI (such as inserting a DVD into a DVD removable drive
or adding SCSI drives on storage enclosures) is not automatically
detected by the EFI Shell environment. To have the EFI Shell recognize
the device, you must reconnect the device driver (on cell-based servers,
use the EFI search command; on other servers, use
the EFI reconnect command). The EFI
shell environment creates default mappings for all the device handles
that support a recognized file system. After you change the system
configuration or add a new device, you must regenerate these mappings.
For information about reconnecting devices and regenerating mappings,
see Section A.6.2.1 and your hardware
documentation or the website listed at the end of this section. Moving between EFI and MP: To move from MP interface to EFI, type co(for
Console) at the MP> prompt. If you are in command mode (at the MP:CM>
prompt), first press Ctrl/B to return
to the MP> prompt. When you move to EFI from MP, confirm
that you are at the main EFI main menu. If you are at a submenu,
to access the main menu exit from the submenu and any subsequent submenus
until you return to the main menu. To move from the EFI to MP, press Ctrl/B (this assumes MP is present and configured).
For more information about using EFI, see the
documentation provided for your Integrity server. Extensive information
can also be found online at: http://developer.intel.com/technology/efi/help/efidocs.htm Systems that have Intel Itanium® Dual-Core processors can support Hyper-Threading.
Hyper-Threading provides the ability for processors to create an additional logical CPU that might allow additional efficiencies
of processing. For example, a dual-core processor with Hyper-Threading
active provides four logical CPUs, two on each core. The effect that
Hyper-Threading has on performance depends heavily on the applications
running on your system. HP recommends that you start with Hyper-Threading
disabled and experiment later, if you wish. You can enable or disable Hyper-Threading for
a system whose processors support it. To display the Hyper-Threading
state for a system, use the EFI info cpu or cpuconfig command. (The display indicates that “CPU
threads” are turned on or off.) For example: Shell> cpuconfig
PROCESSOR MODULE INFORMATION
# of L3 L4 Family/
CPU Logical Cache Cache Model Processor
Module CPUs Speed Size Size (hex.) Rev State
----- ------- ------ ------ ------ --------- --- -----
0 4 1.4 GHz 6 MB None 20/00 CO Active
CPU threads are turned on. |
To enable or disable Hyper-Threading, use the
EFI cpuconfig threads on or cpuconfig
threads off command. For more information, enter help cpuconfig at the EFI Shell prompt or see the appropriate
hardware documentation. The recent release of the Partition Manager
also supports Hyper-Threading. After enabling or disabling Hyper-Threading, the
system must be reset for the change to take effect. Use the EFI Shell reset command. When Hyper-Threading is enabled, it remains
active on the next reboot of the system. This section explains how to configure and manage
the booting behavior of your Integrity server. You can use the EFI
Boot Manager (while the operating system is not running) or the OpenVMS
I64 Boot Manager (while the operating system is running) to configure
boot options. HP recommends using the latter. You can configure multiple boot entries for a
single operating system. On a cell-based Integrity server running
multiple operating systems, you can configure boot options for all
currently installed operating systems. On cell-based servers, each
nPartition has a local instance of EFI that is specific to that partition.
Each partition can be booted and stopped independently of other nPartitions
in the system, and each partition executes its own operating system
image. On cell-based servers, to successfully boot an
operating system you must first ensure that the ACPI configuration
is correct for the operating system being booted, as explained in Section A.5.1. Each nPartition has
its own ACPI configuration value. | | | |  | IMPORTANT: To configure booting on a Fibre Channel storage
device, you must use the OpenVMS I64 Boot Manager utility. (For information
about configuring Fibre Channel devices, see Appendix D.) HP also recommends using this utility
to add members of a multiple-member shadow set to the boot device
list and dump device list. Be sure to add all members to both lists. | | | | |
If you have just completed the initial setup of
your Integrity server, perform the following steps before continuing: Power
up your server system, as explained in the hardware documentation
for your server. If you use the power button on the front panel,
press it only once. If
you have a cell-based server, check that the ACPI configuration is
correct for the OpenVMS operating system. For more information, see Section A.5.1. 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.
This section discusses the following topics: Checking the ACPI configuration for nPartition booting
(Section A.5.1) Setting automatic booting and boot flags for your
system disk (Section A.5.2)
(also includes how to set automatic booting using EFI commands) Displaying EFI boot entries and mapped OpenVMS devices,
using the OpenVMS I64 Boot Manager utility (Section A.5.2.2) (also includes how to display boot entries
using EFI commands) Setting the EFI boot option timeout value, using the
OpenVMS I64 Boot Manager utility (Section A.5.2.3) Writing a new boot block, using the OpenVMS I64 SET
BOOTBLOCK command (Section A.5.3) Comparing Alpha and Integrity server system boot commands
(Section A.5.4)
A.5.1 Checking the ACPI Configuration for Booting OpenVMS in an nPartition | |
To boot your OpenVMS I64 operating system on a
cell-based server, the ACPI configuration must be set correctly.
The ACPI configuration value determines, among other things, the EFI
Path format used when referencing devices. If your Integrity server
was factory installed, the ACPI configuration is set correctly. If
the nPartition on which you want to boot your OpenVMS system had previously
been running a Windows or Linux system, then enter the following command
at the EFI Shell prompt to set the partition to boot correctly with
OpenVMS: To make this new value take effect, you must reset
the nPartition by using the EFI Shell reset command: If the ACPI configuration value is not set properly,
when the operating system boots, it fails with bugcheck code INCONSTATE. You cannot modify the ACPI configuration value
for Integrity servers that do not support nPartitions (for example,
the rx2600 server). To display the current configuration value, enter
the acpiconfig command with no arguments: EFI> acpiconfig
Acpiconfig settings: default |
| | | | | NOTE: The acpiconfig command does not necessarily
report the setting that was used on the current nPartition boot stage.
It reports only the current setting, which is used for the next boot
of the nPartition. | | | | |
A.5.2 Setting Boot Options for Your System Disk | |
You can establish and manage boot options for
your system disk in any of three ways: During installation or upgrade, allowing the OpenVMS
I64 installation/upgrade procedure to automatically establish an EFI
boot option for your system disk Using the OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM)
while the operating system is running Using EFI (after the system disk has been created
or updated and only while the operating system is not running)
HP recommends that you allow the OpenVMS I64 installation
or upgrade procedure to establish a boot option for your system disk.
However, you still have the option of modifying the boot option or
adding other boot options for your system disk by using the OpenVMS
I64 Boot Manager utility from the OpenVMS DCL prompt (or by using
EFI itself). The OpenVMS I64 Boot Manager utility is a menu-based
utility that enables you to configure EFI boot options for your Integrity
server. It is easier to use than EFI. With this OpenVMS utility,
you can perform actions such as the following: Add your system disk as an EFI boot option (you can
optionally configure it to boot automatically on hardware startup
and reboot). Manage multiple system disks. Display the EFI boot options. Add, move, and remove boot options in the EFI Boot
Manager menu. Enable or disable the EFI boot countdown timer (timeout)
and set the countdown value.
This section explains how to perform most of these
operations (except moving and removing boot options). For more information
about the OpenVMS Boot Manager utility, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. This section also explains how to use EFI to add a boot option
for automatic booting. 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 (countdown) occurs,
your system disk boots automatically. | | | | | NOTE: To configure booting on Fibre Channel devices,
you must use the OpenVMS I64 Boot Manager utility. (Use of this utility
is optional for other devices but mandatory for Fibre Channel devices.)
HP also recommends using this utility to add members of a multiple-member
shadow set to the boot device list and dump device list. Be sure
to add all members to both lists. For more information about the
utility, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. For more
information about configuring and booting Fibre Channel devices, see Appendix D. | | | | |
A.5.2.1 Adding a Boot Option and Setting Boot Flags To add a boot option and set boot flags using
the OpenVMS I64 Boot Manager utility, follow these steps: At
the DCL prompt, enter the following command to start the OpenVMS I64
Boot Manager utility: $ @SYS$MANAGER:BOOT_OPTIONS.COM |
When
the utility starts, the main menu is displayed. To add your system
disk as a boot option, enter 1 at the prompt, as 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 |
| | | | | NOTE: While using this utility, you can change a response made to
an earlier prompt by entering the caret (^) character as many times
as needed. To end and return to the DCL prompt, press Ctrl/Y. | | | | |
The
utility prompts you for the device name. Enter the system disk device
you are using for this installation. In the following example, the
device name is DKA0:. Enter the device name (enter "?" for a list of devices): DKA0: |
The
utility prompts you for the position you want your entry to take in
the EFI boot option list. To see a list of the current boot options,
enter a question mark (?): Enter the desired position number (1,2,3,,,) of the entry.
To display the Boot Options list, enter "?" and press Return.
Position [1]: ? |
The
list in the following example includes only one boot option. To add
your boot option entry to the top of the list (the default) so that
your system disk boots automatically when the server starts or the
EFI countdown timer expires, enter 1: EFI Boot Options list: Timeout = 0 secs.
-----------------------------------------------------------------
01. VenHw(d65a6b8c-71e5-4df0-d2f009a9) "EFI Shell [Built-in]"
-----------------------------------------------------------------
1 entries found.
Enter the desired position number (1,2,3,...) of the entry.
To display the Boot Options list, enter "?" and press Return.
Position [1]: 1 |
The
utility prompts you for OpenVMS boot flags. By default, no flags
are set. Enter the OpenVMS flags (for example, 0,1), or press Enter 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: Flags | Description |
|---|
| 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. |
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.3-1H1 for PLMs System
efi$bcfg: DKA0: (BOOT003) Option successfully added |
When
you have successfully added your boot option, exit the utility by
entering E at the prompt:
A.5.2.1.1 Using EFI to Set Automatic Booting of Your System DiskHP recommends allowing the OpenVMS installation
or upgrade procedure to set your system disk to boot automatically.
Or, use the OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM).
However, you can use EFI. This section explains how to use EFI to
set up your Integrity server firmware to automatically boot your OpenVMS
I64 system from your system disk. (HP also recommends using the OpenVMS
I64 Boot Manager utility to set boot flags. Optionally, you can use
the vms_loader.efi -flags n,n command at the EFI
prompt to set any of the standard OpenVMS boot flags, as documented
earlier in this appendix.) Access the EFI Shell and enter 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 displayed at position
1 in the EFI boot menu. You can enter any text that helps you identify
the operating system disk. During system power up, the position 1
item is automatically executed after the countdown. Alternatively, you can add an EFI boot menu option
by using the EFI menu interface: Still another method to add a boot entry to the
EFI Boot Manager menu is to use the EFI Utilities for OpenVMS vms_bcfg command,
which accepts OpenVMS device names and also enables you to set flags.
However, note that this command has limited capabilities; for example,
it cannot handle Fibre Channel paths as can the OpenVMS I64 Boot Manager
utility. In the following example, 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" |
For more information about EFI utilities for OpenVMS,
see the HP OpenVMS System Management Utilities Reference Manual. A.5.2.2 Displaying EFI Boot Entries and Mapped OpenVMS DevicesThe Integrity server EFI Boot Manager shows the
various paths to the boot device. You can use the OpenVMS I64 Boot
Manager 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 on the main menu (the main menu is shown in Section A.5.2). 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, see the HP OpenVMS System Management Utilities Reference Manual. A.5.2.3 Setting EFI Boot Option Countdown Timer (Timeout)Whenever the EFI Boot Manager menu displays, it waits for you to
select an option. The wait depends on the current setting of the
EFI countdown timer. On some servers, the countdown timer
is 10 seconds by default; on others, such as Server Blades, it might
be even less. After the timer expires, 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 utility (SYS$MANAGER:BOOT_OPTIONS.COM) allows
you to change this timeout value and also to disable the countdown
(so that there is no wait) and enable it. Select option 6 on the OpenVMS I64 Boot Options
main menu (the main menu is shown in Section A.5.2). 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 |
To disable the timer so that automatic booting
occurs instantaneously, enter 0 as the value, as in the following
example: Please enter the Timeout value in seconds: 0
efi$bcfg: Boot Timeout is Disabled |
A.5.2.4 Saving and Restoring EFI SettingsCertain EFI settings, such as the Hyper-Threading
setting supported on Intel Itanium Dual-Core processors, cannot be restored if lost. HP recommends that you write down your
customized EFI settings in case they are lost in a system hardware
or firmware failure. You can use the EFI info cpu command or the EFI cpuconfig command to display
current settings, such as the setting of the Hyper-Threading feature. You might need to restore boot options, such as
if they get lost during a firmware upgrade. You can save and restore
your EFI boot path settings on Integrity servers by using the OpenVMS
I64 Boot Manager (SYS$MANAGER:BOOT_OPTIONS.COM) utility. You can also
use the EFI variable -s command to save boot option
variables and the variable -r command to restore
them. After using the variable command to restore
boot options, a reset might be required. Use the EFI Shell reset comand. You can use the OpenVMS-specific EFI utility vms_bcfg (\efi\vms\vms_bcfg) to set boot options, and the vms_showutility (\efi\vms\vms_show) to display them; however,
these utilities are more limited in scope than the OpenVMS I64 Boot
Manager utility. For example, they cannot work with Fibre Channel
boot paths as can the OpenVMS I64 Boot Manager utility. You can use
the EFI variable command to restore the boot options
list from a previously saved file. You could also use the EFI Shell variable command to restore variables such as boot path options; you must
have first saved them in a known location by using the variable
-save command. For more information, see the service manual
provided for your Integrity server. A.5.3 Writing a New Boot Block | |
The boot block structures on the system disk contain
the size and location of the boot partition and other details relevant
to the bootstrap of OpenVMS I64. The size and location of the boot
partition stored within the boot block structures must be maintained
and must reference the current location of the OpenVMS file SYS$EFI.SYS. Current versions of BACKUP maintain the boot block
structures as well as the size and location of the boot partition
during image operations (analogous to the similar BACKUP/IMAGE operations
that maintain the boot block on OpenVMS Alpha disks). Older versions
of BACKUP do not maintain these structures and do not correctly locate
core OpenVMS I64 bootstrap files. If the boot partition file SYS$EFI.SYS is manually
replaced or relocated, you must use the DCL command SET BOOTBLOCK
or the SYS$SETBOOT image to rewrite the boot block structures. The
SET BOOTBLOCK command and SYS$SETBOOT are analogous to the OpenVMS
Alpha Writeboot utility; they provide OpenVMS I64 with the equivalent
of what the Writeboot utility provides on OpenVMS Alpha. | | | | | NOTE: Do not use the OpenVMS Alpha Writeboot utility to rewrite boot
block structures on an OpenVMS I64 system disk. | | | | |
The SET BOOTBLOCK command enables you to establish
the boot block pointers necessary for the EFI console to find and
bootstrap an OpenVMS I64 system disk. You must use this command if
the target OpenVMS I64 system disk was originally created by one of
the following methods: A version of BACKUP that
does not support the OpenVMS I64 system disk structure. HP recommends
that you do not use these versions of BACKUP
for archiving or restoring an OpenVMS I64 system disk. A nonimage backup of an
OpenVMS I64 system disk (possibly corrupting the boot block and various
directory backlinks that must be manually reset). HP recommends that
you do not use nonimage backups. A nonimage restore of
an OpenVMS I64 system disk from an image save set. HP recommends
that you do not use a nonimage restoration.
To write the boot block structures onto an OpenVMS
I64 system disk, enter the SET BOOTBLOCK command using the following
format: $ SET BOOTBLOCK [/PRESERVE=SIGNATURES] [/I64] [boot-partition-name] |
You can specify the file name for the boot partition
(boot-partition-name). If you do not specify
a file or device name, the command defaults to the following file
for the boot partition: SYS$SYSDEVICE:[VMS$COMMON.SYS$LDR]SYS$EFI.SYS The command also assumes the current architecture.
To specify OpenVMS I64, include /I64 in the command line. Use the /PRESERVE=SIGNATURES qualifier to preserve
the existing GUID disk signature value and the associated root aliases.
Note that using the OpenVMS Backup utility creates a new disk signature
when restoring a bootable disk image. If you reset the boot block structures, you might
need to remove any EFI boot aliases that reference the disk, and then
add them back again. You can use the EFI alias command to remove and add aliases; HP recommends using the OpenVMS
I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM) to maintain
EFI console boot aliases.
| | | | | NOTE: The boot partition file must be contiguous and movefile operations
on the file must be disabled. If the file is not contiguous, use
the DCL command COPY/CONTIGUOUS (or equivalent) to re-create a contiguous
version of the file. To disable movefile operations, use the DCL
command SET FILE/NOMOVE. This prevents bootstrap failures that could
result from the normal and expected operations of disk defragmentation
tools. | | | | |
Alternatively, you can write a boot block by entering
the following command: $ RUN SYS$SYSTEM:SYS$SETBOOT |
The utility prompts you for the required input
(in a way similar to the operation of the OpenVMS Alpha Writeboot
utility). A.5.4 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 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 that some of the commands listed might
not be available on certain hardware systems. Table A-1 Alpha and Integrity Server EFI Command Equivalents | Task | 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)[1] |
| | Display all system information | SHOW FRU | | Display memory information | SHOW MEMORY | info mem | | Display volume information of the
file system | SHOW DEV DKA0 | vol fs0 | Display hardware information
about CPU resources | SHOW CONFIGURATION | info cpu | Display power status | SHOW POWER | info all[2] | | Set system dump disk | SET DUMP_DEV disk1, disk2... | vms_set dump_dev disk1, disk2, ... (from \efi\vms)[1] | | Set boot flags | SET BOOT_OSFLAGS 0,0 | set vms_flags "0,0"[1] | | Set boot behavior to automatic
boot | SET AUTO_ACTION BOOT | bcfg boot add 1 fsx:\efi\vms\vms_loader.efi "I64"[1] | | Change the current boot option | SET AUTO_ACTION HALT | bcfg boot mv 1 2[1] |
This section describes various methods for booting
your OpenVMS I64 operating system. A.6.1 Overview of Booting on a Cell-Based Server | |
This section gives an overview of booting the
nPartition hardware and booting OpenVMS on an nPartition. A.6.1.1 Booting the nPartition HardwareEach nPartition runs its own firmware and has
its own system boot environment. You can boot an nPartition independently
of any other nPartitions in the same server complex. The nPartition boot process includes two phases:
the cell boot phase and the nPartition boot phase. Note that these
phases occur only as part of the hardware boot process, not as part
of the operating system boot. Cell boot phase—This phase occurs when cells
are powered on or reset. The main activities during this phase are
the power-on-self-test activities. During this phase, cells operate
independently of other cells in the complex. Cells do not necessarily
proceed through this phase at the same pace, because each cell may
have a different amount of hardware to discover and test, or cells
might be reset or powered on at different times. nPartition boot phase—This phase occurs when
an nPartition has been booted, after its cells have completed their
self tests. During this phase, “nPartition rendezvous” occurs, in which each cell contacts the other active cells in the
nPartition and selects a core cell that is responsible for managing
the rest of the nPartition boot process. A processor on the core
cell runs the nPartition EFI system boot environment. When the operating
system boot process is initiated, the core cell passes control to
the operating system loader.
You can view progress of these phases by using
the Virtual Front Panel (VFP) to check the nPartition boot state.
Access VFP from the MP main menu. For information about how to boot the nPartition
hardware, see your hardware documentation. A.6.1.2 Booting OpenVMS I64 on an nPartitionAs with all Integrity servers that run OpenVMS,
you can boot OpenVMS I64 either by selecting a boot entry from the
EFI Boot Manager or by starting the system loader (VMS_LOADER.EFI)
from the EFI Shell. To boot OpenVMS I64, access the nPartition console
and use either of these two methods: From the EFI Boot Manager, select the OpenVMS I64
boot entry from the boot options list and press Enter. From the EFI Shell, start the OpenVMS system loader
by entering the following command at the EFI Shell prompt, where fsn: (such as fs1:) is the device associated with the OpenVMS
I64 system disk: Shell> fsn:\efi\vms\vms_loader.efi |
When starting the VMS_LOADER.EFI system loader,
you must either specify its full path (as shown in this example) or
start it from the \efi\vms directory. For more
information, see Section A.3.1. For booting the OpenVMS I64 OE DVD, the path is different. Enter
the following command instead: Shell> fsn:efi\boot\bootia64.efi |
| | | | | NOTE: The nPartition must be at EFI before beginning the OpenVMS I64
boot process. If the nPartition is not at EFI, you can use VFP to
check the nPartition boot state. An nPartition might be inactive
or cells might be powered off. If VFP indicates that all cells in
the nPartition are in the boot-is-blocked (BIB) state, the nPartition is inactive and you must use the MP bo command to boot the nPartition past BIB and make it
active. For more information, see your hardware documentation. | | | | |
A.6.2 Booting the OpenVMS I64 OE DVD from the Local Drive | |
To boot the OpenVMS I64 OE DVD, follow these steps.
To boot the DVD on a cell-based server, a DVD device must be accessible
for the nPartition that OpenVMS is being installed on. Make
sure your Integrity server is powered on. If your system has an attached
external device, make sure it is turned on and operational. Insert
the DVD into the drive. Cycle
power. From
the main EFI boot menu (for cell-based servers, this must be the EFI
boot menu for the nPartition on which OpenVMS is to be booted), select
the appropriate item from the boot options list. Note that the EFI
boot menu is timed; press any key to stop the countdown timer. For some systems, the boot option to select is
the Internal Bootable DVD option. If that option is not listed in
your EFI boot menu, move to the Boot From a File menu and select the
Removable Media Boot option, if present. Alternatively (and this method is recommended
for cell-based servers), boot the DVD drive from the EFI Shell prompt
by entering the command shown in the following example, where fsn: corresponds to the Integrity server DVD drive (such
as fs0:). Note that if you have navigated to a particular file system,
the EFI Shell prompt would reflect that file system; for example,
if the current file system is fs0:, the EFI Shell prompt would be
fs0:>. Shell> fsn:\efi\boot\bootia64.efi |
To determine which device is the bootable DVD
drive, examine the list of mapped devices and look for an fs device
listing that includes the text CDROM, as in the following example,
where fsn is the file system associated with
the drive, which is usually fs0: (instead of fsn, you might see something like V8.3-1H1; instead of Ata, you might
see Scsi, depending on the server model): fsn : Acpi(HWP0002,400)/Pci(4|1)/Ata(Primary,Master)/CDROM(Entry0) Use the vms_show dev command
to display the mapping of various EFI device names to OpenVMS device
names, as in the following example where fsn is
the device you want to check (such as fs0:): Shell> fsn:\efi\vms\vms_show dev -fs |
For more information about the vms_show command, see the HP OpenVMS System Management Utilities Reference Manual.
| | | | | NOTE: By default, certain versions of EFI might interpret the Delete (or Backspace) key differently than
do OpenVMS Alpha systems or Microsoft Windows computers. In such cases,
press Ctrl/H to delete the last
character entered. For more information, see Section A.1.3. | | | | |
When the DVD boots properly, the OpenVMS operating system banner
is displayed, followed by the operating system menu. You can now install
your OpenVMS I64 operating system onto the target disk; see Section 3.3. If the DVD fails to
boot properly use the alternate method of booting described in Section A.6.2.1. | | | | | NOTE: When booting OpenVMS from the installation DVD for the first
time on any OpenVMS I64 system with a SAN storage device, you might
experience a delay in EFI initialization because the entire SAN is
scanned. Depending on the size of the SAN, this delay might range
from several seconds to several minutes. | | | | |
A.6.2.1 Alternate Method of Using EFI to Boot the DVDIf the DVD does not boot using the methods described
above, follow these steps: To
ensure that EFI can access the DVD, enter the following commands at
the EFI Shell prompt of a entry-class or single-cell Integrity server.
Enter the commands in the order shown. (The EFI Shell prompt may
not necessarily be Shell> as in this example; it could be a prompt
that reflects the current file system, such as fs0:>.) Shell> reconnect -r
Shell> map -r |
For a multiple-cell nPartition
on a cell-based server, use the search allcommand
instead of the reconnect -r command, followed by
the map -r command. See your hardware documentation
for more information about EFI commands. The reconnect -r command discovers
any devices added after booting the server. The search all command discovers all devices including any that were not in the
boot options list or connected to the core cell’s I/O chassis.
(On large server systems, the search all command
could take significant time to complete. You can reduce the search
time by specifying a more directed search, such as for a specific
I/O chassis connected to a cell or a specific PCI card in a chassis.
For more information, see the help information provided for the search command.) The map -r command remaps and
rebuilds the list of known devices that have a bootable EFI system
partition. For a multiple-cell nPartition on a cell-based server,
if you insert the DVD after EFI is loaded, you must use the search
command to allow EFI to detect the inserted DVD; otherwise, EFI would
not recognize the DVD in the DVD drive. When EFI detects a valid,
bootable DVD in the DVD drive, it maps an fs device to it and lists
that device in the mapping table displayed by the map -r command. To
boot the DVD, enter the following command at the EFI Shell prompt,
where fsn: is the Integrity server DVD drive
(such as fs0:). Shell> fsn:\efi\boot\bootia64.efi |
If this command does not work, or if you have
doubts about which device maps to the DVD drive, you can use the EFI
Boot Manager menu system to boot the OE DVD, as described in the following
steps: From
the main EFI boot menu, select the Boot Configuration option (or in
some versions of EFI, the Boot Option Maintenance Menu). From
the Boot Configuration menu, select the Boot From a File option. From
the Boot From a File menu, select the menu item that includes the
text CDROM, as in the following example, and press Enter. | | | | | NOTE: The contents of the screens shown in the following
examples vary according to the firmware and devices installed on your
Integrity server. | | | | |
A screen
is displayed that shows the top-level directory structure of the DVD,
similar to the screen in the following example. Select the efi directory. The
next screen to appear shows the first level of subdirectories below
the top level, similar to the following example. Select the boot
directory (it contains the boot file). The
next screen displays the files within the boot directory. Select
the file named bootia64.efi.
A.6.3 Booting the OpenVMS I64 OE DVD from the InfoServer | |
To boot from a virtual DVD drive on the LAN using
OpenVMS I64 InfoServer software, you must initially perform certain
configuration steps (one time only). These steps and the instructions
on performing the network boot are described in Appendix B. A.6.4 Booting an Image of the OpenVMS I64 OE DVD Using HP SIM Provisioning | |
To use HP SIM provisioning to boot an image of
the OpenVMS OE DVD, certain configuration steps are required initially
(one time only). For these steps and the booting instructions, see Appendix C. For upgrades, your
OpenVMS boot flags must be set to (0,0). A.6.5 Booting an Image of the OpenVMS I64 OE DVD Using vMedia | |
To use vMedia to boot an image of the OpenVMS
OE DVD, certain configuration steps are required initially (one time
only); see Section C.1.4.
For instructions on booting with vMedia, see Section C.2. A.6.6 Booting from a Fibre Channel Device | |
For instructions on booting from a Fibre Channel
(FC) storage device, see Appendix D. A.6.7 Booting Manually from the Local System Disk | |
HP recommends setting up your Integrity server
EFI console with a boot option for your OpenVMS I64 operating system
disk. In this way, booting the system disk simply requires selecting
the boot option from the EFI Boot Manager boot options list. You
can set the EFI boot option to boot automatically on powering on or
rebooting. The OpenVMS installation and upgrade procedures can assist
you in adding and validating a boot option for your system disk;
you can also use the OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM),
as explained in Section A.5.2. The steps that follow explain how to boot the
OpenVMS I64 operating system disk manually. You can also use
vMedia to boot an OpenVMS system disk; see Section C.2. If
OpenVMS is not running, skip to the next step. If OpenVMS is running,
access the EFI console by shutting down the operating system (see
the instructions in Section A.7). 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 |
You must either specify the full path (as shown in this example)
or start the system loader from the \efi\vms directory.
For more information, see Section A.3.1.
A.6.8 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 |
Log
in to the SYSTEM account. Enter
the following command: Answer
the questions displayed by the system. When the procedure asks whether
an automatic reboot should be performed, press Enter for NO. When the procedure is finished, it displays the following
message: Halt
the system or nPartition. (See Section A.7 for more information about how to halt
your Integrity server). 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 |
At
the SYSBOOT> prompt, you can enter any of the SYSGEN commands listed
in Table A-2. For
more information about these SYSGEN commands, see the HP OpenVMS System Management Utilities Reference Manual: M-Z. When
you finish using the SYSGEN commands, enter the CONTINUE command to
complete the boot process.
Table A-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 conversational booting, see Section A.6.9 and Section A.6.12. A.6.9 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. | | | | | NOTE: Because this procedure bypasses specific startup
operations, it does not autoconfigure the system's peripheral
devices. | | | | |
Boot the system with minimum startup as follows: 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 and the system root is [SYS0...]: Shell> fsn:\efi\vms\vms_loader.efi -flags 0,1 |
Enter
the following command: SYSBOOT> SET STARTUP_P1 "MIN" |
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 |
Enter
the following command to continue booting:
A.6.10 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 |
For more information about using XDELTA, see the HP OpenVMS Delta/XDelta Debugger Manual. A.6.11 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_LAN.COM
procedure to add a copy of the operating system to a different root
directory. (For more information about using the SYS$MANAGER:CLUSTER_CONFIG_LAN.COM
procedure, see the HP OpenVMS System Manager's Manual .) 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 |
A.6.12 Emergency Booting | |
If a system problem prevents your system from
booting, you might need to perform an emergency boot operation. Table A-3 summarizes these emergency
boot operations, and the sections that follow describe each boot operation
in more detail. Table A-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 |
A.6.12.1 Booting with Default System ParametersIf 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,
see 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 TaskBegin
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 |
At
the SYSBOOT> prompt, enter the following command: The USE DEFAULT command specifies that default
values should be used for all parameters. 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" |
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 |
Enter
the following command to continue booting: 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, see
the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems. After
your system runs for at least 24 hours, run AUTOGEN in feedback mode,
following the steps described in Section 7.22. Be sure to examine the AGEN$PARAMS.REPORT,
as recommended. If necessary, modify system parameters as instructed
in Section 7.23.
If you need assistance, contact your software support representative.
Once you feel confident that the problem is corrected, and AUTOGEN
has been run through the SETPARAMS phase, reboot the system.
ExampleSYSBOOT> 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)]
.
.
. |
A.6.12.2 Booting Without Startup and Login ProceduresIf 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 you
modify the startup or login procedure, you could accidentally lock
yourself out of the system. How to Perform This Task 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 |
Enter
the following command at the SYSBOOT> prompt: SYSBOOT> SET/STARTUP OPA0: |
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 |
Enter
the following command to continue booting: When
the system is booted, the operator console displays the DCL command
prompt ($). You are now logged in. Enter
the following two DCL commands: The SPAWN command enables you to stay connected
to the console, and the second command instructs the operating system
to ignore any errors that might occur. If you do not enter these
commands and you invoke an error, the system logs you out. Without
the SPAWN command, you are logged out when the startup procedure completes
in step 8. 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.) Use a text editor to correct
the startup or login file. Note that some system displays might not
support a screen-mode editor. You can also copy a corrected file
and delete the incorrect version by using the RENAME and DELETE commands. Perform
a normal startup by entering the following command:
Example
SYSBOOT> SET/STARTUP OPA0:
SYSBOOT> SET WRITESYSPARAMS 0
SYSBOOT> CONTINUE
$ SPAWN
$ SET NOON
$ SET DEFAULT SYS$SYSROOT:[SYSEXE]
$ @SYS$SYSTEM:STARTUP |
A.6.12.3 Booting Without a User Authorization FileOrdinarily, the startup and login procedures provided
by HP 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 performing the steps given in this
section. How to Perform This Task Halt
the system or nPartition. (See Section A.7 for more information about how to halt
your Integrity server.) 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. 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 the following: OpenVMS read the system startup commands directly
from the system console. The windowing system (if any) not start. OpenVMS not record the parameter changes for subsequent
system reboots.
The last command causes the booting to continue. At
the DCL prompt, the system now accepts startup commands directly from
the console. Enter the following two commands. These commands allow
a normal system startup while you are left logged in on the console.
Without the SPAWN command, you are logged out when the startup completes. $ SPAWN
$ @SYS$SYSTEM:STARTUP |
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.
Example
SYSBOOT> SET/STARTUP OPA0:
SYSBOOT> SET WINDOW_SYSTEM 0
SYSBOOT> SET WRITESYSPARAMS 0
SYSBOOT> CONTINUE
$ SPAWN
$ @SYS$SYSTEM:STARTUP
$ |
The following sections describe halt and shutdown
procedures for Integrity servers and OpenVMS I64. A.7.1 Halting the Integrity Server to Recover from Hangs and Crashes | |
If your system hangs and you want to force a crash,
you can use MP, if available. Use the tccommand. Confirm your intention when prompted. The tc command forces a crash dump. You can reset the machine
(without forcing a crash) by using the MP rscommand. For cell-based servers, when you enter the tc or rs command, you are first prompted
to select the partition for which you want the operating system shut
down. Alternatively, when the operating system controls
the console, press Ctrl/P. The
next step taken by the system depends on whether XDELTA is loaded: If XDELTA is loaded, the
system enters XDELTA after you press Ctrl/P. The system displays the instruction pointer and current
instructions. You can force a crash from XDELTA by entering ;C, as
in the following example: $
Console Brk at 8068AD40
8068AD40! add r16 = r24, r16 ;; (New IPL = 3)
;C |
If XDELTA is not loaded,
pressing Ctrl/P causes the system
to enter the IPC facility. Pressing Ctrl/P within the utility brings the “Crash? (Y/N)”
prompt. Enter Y to cause the system to crash and to bring you eventually
to EFI. If you enter any other character, the system returns back
to the IPC facility.
A.7.2 Shutting Down the System | |
Before you shut down the operating system, decide
if you want it to reboot automatically or if you want to enter console-mode
commands after the shutdown completes. If you want the system to
reboot automatically after the shutdown, first set up automatic booting,
as described in Section A.5.2. You can perform the following two types of shutdown
operations, as discussed in the indicated sections: The SHUTDOWN.COM procedure shuts down the operating system
while performing maintenance functions such as disabling future logins,
stopping the batch and printer queues, dismounting volumes, and stopping
user processes. To use the SHUTDOWN.COM command procedure, log in
to the SYSTEM account, enter the following command: For more information about the SHUTDOWN.COM command
procedure, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. On cell-based Integrity servers, two special types
of nPartition reboot are supported: reboot for reconfiguration, which
reboots an nPartition and enables cell configuration changes to occur,
and shutdown for reconfiguration, which puts an nPartition into an
inactive state. To perform a reboot for reconfiguration from OpenVMS
I64 running on an nPartition, enter the OpenVMS @SYS$SYSTEM:SHUTDOWN
command, and then answer YES to the prompt that asks whether to perform
an automatic system reboot. On cell-based Integrity servers,
an operating system reboot is equivalent to a reboot for reconfiguration.
Performing a reboot for reconfiguration enables any cell assignment
changes for the nPartition (for example, removing an active cell or
activating a newly added cell). The reboot for reconfiguration takes all cells assigned to the
nPartition through a cell boot phase. The cells with a Yes use-on-next-boot
attribute proceed through the nPartition boot phase to become active
cells whose resources are available to software running on the nPartition. To perform a shutdown for reconfiguration of an nPartition
running OpenVMS I64, first enter the OpenVMS @SYS$SYSTEM:SHUTDOWN
command and then answer NO to the prompt asking whether to perform
an automatic system reboot. Next, access MP and use the rr command (specify the OpenVMS nPartition to shut down
for reconfiguration). A shutdown for reconfiguration takes
all cells assigned to the nPartition through a cell boot phase and
then stops their boot progress at the boot-is-blocked (BIB) state.
When all cells assigned to the nPartition are at the BIB state, the
nPartition is inactive and no software can run on the nPartition until
it is manually booted past BIB. To boot an inactive nPartition past BIB, use the MP bo command and specify which nPartition to make active. Booting past
the BIB state involves all cells that are assigned to the nPartition
and that have a Yes use-on-next-boot attribute. The cells are taken
through the nPartition boot phase to become active cells whose resources
are available to software running on the nPartition.
For more information about shutting down an Integrity
server or an nPartition, see the appropriate hardware documentation. A.7.2.2 Emergency Shutdown with OPCCRASH.EXEIf you cannot perform an orderly shutdown with
the SHUTDOWN.COM procedure, run the OPCCRASH.EXE emergency
shutdown program. To run the OPCCRASH.EXE program, log in to the
SYSTEM account and enter the following command: $ RUN SYS$SYSTEM:OPCCRASH |
For more information about the OPCCRASH program,
see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. On cell-based Integrity servers, entering the
OpenVMS RUN SYS$SYSTEM:OPCCRASH command results in the system dumping
memory and then halting at the P00>>> prompt. To reset the nPartition
following OPCRASH, access the nPartition console and press any key
to reboot. Using the MP tc command to
reset an nPartition results in the system dumping memory and then
automatically resetting the nPartition. The following sections describe procedures that
you can follow if you encounter problems with your system. A.8.1 If the System Does Not Boot | |
If the system does not boot because a hardware
problem occurs, a question mark (?) usually precedes the error message
displayed on the console terminal. An example of a hardware problem
is a read error on a disk. Another is a BIB condition in an nPartition
on a cell-based server. You can use VFP to check the nPartition boot
state. If VFP indicates that all cells in the nPartition are at BIB,
the nPartition is inactive and you must use the MP bo command to boot the nPartition past BIB and make it active. One way to get to the EFI Boot Manager to attempt
to reboot is to use the MP rs command. For more information about using VFP and MP, see
your hardware documentation. A.8.1.1 For Hardware ProblemsIf you suspect a hardware problem, do the following: Consult
the hardware manual for your Integrity server. Contact
HP Customer Support.
A.8.1.2 For Software ProblemsWhen the operating system is loaded into memory,
a message similar to the following is displayed on the terminal screen: SYSTEM job terminated at 27-JUL-2007 15:05:03.17 |
If the system does not display this message, a
software problem has probably occurred. Do the following: Turn
off the system. Turn it back on and try to reboot. Perform
a conversational boot using the default system parameters or try one
of the emergency boot procedures described in Section A.6.12. If
the system boots, run the AUTOGEN procedure. For more information
about the AUTOGEN procedure, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.
A.8.2 Detecting and Responding to System Problems | |
If your system exhibits unexpected behavior, note
the following: If the system displays
a bugcheck message on the console terminal and shuts itself down,
it means the system encountered a problem that made further operation
impossible or dangerous. If the system does not reboot automatically,
reboot the system manually as described in Section A.6.7. If the system stops responding
to your commands (that is, if the system hangs), there is a possible
failure in a system software or hardware component or a possible power
failure. If the system exhibits
erratic behavior (it does not respond according to specifications),
it indicates a possible failure in a system software or hardware component.
To determine whether the failure is a system problem: Be sure that you did not
press F1 (Hold Screen). The Hold
Screen light turns on when you press either F1 or Ctrl/S. Press Ctrl/T to check the status of your process. A status
line should appear indicating the name of the program that is executing
and other information. If the status line does not appear, the program
you are executing might be stalled or hanging. (If you have disabled Ctrl/T by entering the command SET NOCONTROL=T,
or if you have set the terminal to NOBROADCAST mode by entering the
command SET TERMINAL/NOBROADCAST, this procedure does not work.) Make sure the cable connecting
the terminal or monitor to the system is secure.
If you determine that you have a system problem,
take the following steps: Force
an exit from a stalled or hanging program by pressing Ctrl/Y. Note that pressing Ctrl/Y causes any work performed by the program and not saved
on disk to be lost. If
the system is still unresponsive, halt it (see Section A.7.1 for more information.) Note
in detail the sequence of events that caused the problem and notify
HP Customer Support.
|
Printable version
