|
HP OpenVMS Version 8.2 Upgrade and Installation... |
Setting Up, Booting, and Shutting Down HP Integrity... |
|
|
|
| |
Configuration/Management Tools on HP Integrity Server Systems
Overview
and Comparison of the Tools and Console Options
Three interfaces are available to configure and manage your
HP Integrity server environment on HP Itanium-based systems: the
Extensible Firmware Interface (EFI), the Baseboard Management Controller (BMC),
and the Management Processor (MP).
EFI is the main boot and preboot interface; it is the core interface to the system firmware and console commands. BMC is available on all HP Integrity servers (although on a few systems the interface itself is hidden). BMC provides basic management capabilities and access to EFI. MP is available on most systems. On some systems it is available only if the necessary console hardware has been installed and configured. MP provides advanced management functionality beyond that which is available through BMC and the BMC access into EFI, including remote management, network console and web-based access, and enhanced diagnostic capabilities.
You can interact with EFI and the EFI Shell and menus through either BMC or, when present, the MP interface. In hierarchical terms, MP is connected to BMC, and BMC itself connects to EFI. EFI is the base console environment, and you can interact with the capabilities of the console interface you are using or with EFI itself, as required.
To set up your Integrity server system and boot the system for the first time, you use EFI as explained later in this appendix. If your system includes MP, you can set it up to provide your console interface, as explained in Setting MP as the Console Interface (Optional).
The following briefly describes the main features of EFI, MP, and BMC.
 | 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 and takes into account the special hardware features that HP offers. |
 | Console connectivity As a console interface, it allows you to interact with EFI and to boot the OpenVMS operating system; ultimately, it can function as the OPA0: terminal port in OpenVMS. |
| Virtual front panel 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 of commands and command-line interface, including such commands as HE (help), PC (power control), RS (system reset), PR (power restore policy), LC (LAN and web connection configuration), and DF (display FRU information). |
| Availability/standby power MP is available whenever the system is connected to a power source, even if the system's main power switch is in the off position. |
| Accessibility MP is accessible in several ways: by direct monitor connection using a terminal, PC, laptop or any desktop computer connected to the MP serial port; by modem through an EIA-232 port; or by Telnet or web browser on the LAN. |
| 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. In most cases, OpenVMS automatically clears event logs. If you see a message indicating the event log is full, HP recommends that you clear the event log frequently. You can clear the system event log by selecting SL from the MP main menu and then selecting the C option. For more information about clearing event logs, refer to the hardware documentation. You can also clear the system event log at the EFI Shell prompt, as explained in Booting Operations. |
| MP provides much more functionality than BMC and may be more appropriate for your use. On some systems, MP is an optional component and on others it is built into the system. Some systems do not include MP. |
The following table compares the EFI, MP, and BMC tools.
| Feature/Function | EFI Interface | MP Interface | BMC Interface |
|---|---|---|---|
|
Main Function
|
Interface between operating systems and the
Integrity server firmware |
Control of system console and power management |
Simple hardware and firmware configuration and
management
|
|
Availability
|
All systems; primary interface to firmware |
Depending on the system, either embedded, a standard
plug-in card, or optional |
Most systems; on some systems such as the rx4640
it is hidden and unavailable to the user |
|
Interface when system is turned on first
time, before customization?
|
Yes, depending on the system and type
of connection
|
Yes, depending ont he system and type of connection |
No |
|
Main prompt
|
Shell>
|
MP> |
cli>
|
|
Configure and manage boot environment |
Yes, extensive functionality |
Yes (after initial boot only) |
Limited (after initial boot only) |
|
Status displays |
System date/time System Devices and drivers Memory |
LAN Modem Power management System power Locator LED Processor |
Power management System power Locator LED |
|
Ways it can alter server state
|
Reset system
|
Reset modem Control remote power Reset BMC System reset Transfer of control |
Control system power Locator LED System reset Transfer of control |
|
Configuration capabilities
|
Boot environment System date/time Security passwords Processors Devices and drivers SCSI parameters Memory |
Power restore policy Default configuration Diagnostics Upgrade firmware Security options Inactivity timeout User configuration Serial, LAN, and remote/modem access Make or change connections |
Power restore policy Security options BMC password |
|
Remote manageability
|
Yes, depending on MP or BMC connectivity
|
Yes
|
Yes, through modem or remote serial connection
|
|
Access |
Depends on MP or BMC connectivity (EFI behavior
is independent of the connection type) |
Local EIA-232 serial with terminal emulation software, remote (modem)
EIA-232 serial, LAN/Telnet (also allows access through web browser) |
Local EIA-232 serial only, with terminal emulation software |
|
Default access settings
|
Not applicable |
Serial: Baud rate: 9600 Bits: 8 Parity: None Stop Bits: 1 (one) Flow Control: None Modem: Baud rate: Input and output rates same Flow Ctrl: Hardware: RTS/CTS Software: XON/XOFF Terminal type: HPterm For other settings, refer to the hardware documentation |
Serial: Baud rate: 9600 Bits: 8 Parity: None Stop Bits: 1 (one) Flow Ctrl: XON/XOFF |
|
Interface
|
Command line and menu mode
|
Command line and menu mode |
Command line mode
|
|
User support |
Single user |
Multiple users: one entering commands, others
viewing1 |
Single user |
|
Security/password |
User and administrator passwords |
Security options and access control |
User password |
|
Functionality (diversity of functions) |
Medium |
High |
Low |
|
Power dependency |
Dependent on server power status |
Standby, independent of server power status |
Standby, independent of server power status |
The Delete or Backspace
Key
The EFI environment and the MP and BMC console interfaces
on Integrity server systems interpret the Delete (or Backspace)
key as do UNIX systems, which is much different than the way OpenVMS
Alpha systems or Microsoft Windows computers interpret them. While
the OpenVMS operating system uses the ASCII DEL/RUBOUT character
(7F hexadecimal) to delete the last character typed in a command
line, the Integrity server facilities use Ctrl/H. When entering
commands for the Integrity server, if you press the Delete key on
a VTxxx terminal (or press the key you have
mapped to send the DEL/RUBOUT character code in your terminal emulator),
the last character typed is not deleted.
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:
Alternatively, you can set up your terminal emulator so that the Backspace key deletes the last character typed. However, to have the key work properly on OpenVMS, you must still issue the SET TERMINAL command described above.
1 Command mode and console mode are mirrored. Thus, only one user can have write access to the shared console at a time.
( Number takes you back )
|
|
|
