• EFI is the standard console for all IA64 systems,
regardless of hardware vendor
• Each vendor can provide unique customizations
• Used to boot the system
• Interfaces with the operation system via PAL, SAL and
EFI runtime services
• Provides both a menu and command line interface
• Code is stored in flash ROM and optional FAT partition
• EFI console is an open programming environment
– Intel publishes the source code and tool kit
– Intel transitioning EFI to SIG group, similar to PCI
SIG
• EFI will eventfully replace BIOS on IA32 systems
RX2600 consoles
page 34/22/04
VMS_LOADER.EFI
• EFI application, built using MS Visual Studio with:
– IA-64 cross compilers
– EFI tool kit provided my Intel
– MS linker produces P/COFF image format
• Runs in Physical Address mode as a console command
• Implements functionality of SRM BOOT command:
– Initializes HWRPB structure
– Creates bootstrap Virtual Address using translation
registers
– Loads IPB.EXE (ELF-format image)
– Shuts down the EFI console with ExitBootServices()
– Transfers to IPB in Virtual Address mode, via RFI
instruction
RX2600 consoles
page 44/22/04
Hybrid Disk Format
• EFI requires GUID Partition Table (GPT) disk format
• EFI requires one FAT32 partition
• VMS requires ODS Files-11 disk format
• VMS does not support partition disks
• Both format co-exist, independent of each other
• EFI console view
– GPT format with one 48Mb FAT32 partition
– Remaining space unallocated
• VMS view
– ODS Files-11 format disk
– 48Mb container file allocated for FAT32 partition
• CD-ROMs use ISO9660 format instead of GPT
RX2600 consoles
Selecting EFI console terminal
• New systems are shipped with multiple devices
selected as the console terminal
• VMS requires only one serial port for the console
terminal
• Be sure USB keyboard is unplugged for now,
support for USB keyboard and VGA console
planned for the future
page 54/22/04
• Use the Boot Option Maintenance Menu to select
only serial port and deselect other device
• Can select ANSI, VT100 and VT100+ terminal types,
based on your terminal emulator
• Reset the system
RX2600 consoles
page 64/22/04
Booting VMS from the EFI Shell
• Select EFI Shell from the boot menu
• Set Boot flags environment variable, stored in
NVRAM
– IA64 flag values are generally the same as Alpha
and VAX
– Shell> set vms_flags “0,0”
• Select disk and directory
– Shell> fs0:
– fs0:> cd efi\vms
•EFI console requires ^H (ASCII 0x08) for backspace
•VMS traditionally uses DEL (ASCII 0x7F) for backspace
•Two methods for using the backspace key
–Set terminal emulator to send DEL for backspace key
–Use ^H in EFI Shell and Backspace key in VMS
–Set terminal emulator to always send ^H for backspace
key
page 74/22/04
–Available in upcoming VMS for IA64 and Alpha
–In LOGIN.COM:
–$ SET TERM/BACKSPACE=DELETE
–Backspace key sends ^H and works for EFI Shell and
VMS
–Use ^V ^H ^H for beginning of line
RX2600 consoles
page 84/22/04
Booting VMS from the EFI menu
• Create new menu item
– Select Boot Option Maintenance Menu
– Select Add Boot Option
– Select volume
– Select efi\vms\vms_loader
– Add name, “HP OpenVMS Industry Standard 64”
– No boot options are needed, since it uses
VMS_FLAGS stored in NVRAM
– Save settings to NVRAM
RX2600 consoles
Boot Example
EFI version 1.10 [14.61]
EFI64 Running on Intel(R) Itanium Processor Family
EFI 1.10 IPF zx6000/rx2600/zx2000 1.22 [Wed Jul 23 16:43:12 2003] - H P
– Replace 1.1.1.1 with IP address
– Replace 2.2.2.2 with Netmask
– Replace 3.3.3.3 with Gateway
• Hint: Use a script file to perform this task
RX2600 consoles
Obtaining EFI firmware update
• Use FTP to copy over firmware update program
Shell> ftp 4.4.4.4
Connected to 4.4.4.4
220 foo.bar.com FTP Server (Version 5.3) Ready.
Name (4.4.4.4): HUBER
331 Username HUBER requires a Password
Password:
page 174/22/04
230 User logged in.
Remote system type is VMS.
ftp> bin
ftp> get fwupdate220.efi
ftp> bye
RX2600 consoles
page 184/22/04
Installing the EFI firmware update
• Execute the firmware update program
– Shell> fwupdate220
• Warning: Do not power-off the system while
flash ROM update is in progress
• Alternate update method
– Download ISO file, Burn CD-ROM and execute
update program from CD-ROM
RX2600 consoles
Remote Console Interface
• Independent support system
• Available when the system is connected to a
power source, even if the main power switch is
set to “off”
• Vendor and system-specific functionality
• Two different remote consoles for the RX2600
– Baseboard Management Controller (BMC) with
basic functionality
page 194/22/04
– Management Process (MP) with more extensive
features
• Optional on RX2600, standard on larger system
(RX4640)
RX2600 consoles
page 204/22/04
Baseboard Management Controller
(BMC)
• Available only on COM1 serial port of RX2600, ZX200, ZX6000
• Has it’s own processor
• Password protected
• Entered by “ESC (“ and exited by “ESC )” or “ESC Q”
• Power ON/OFF and system reset
• TOC command can be used to force a crash on hung system
cli>help
CLI Commands:
C [<passwordstring>]- Change Password
CON - Display Console selection
FPL - Read Forward Progress Log
H - Help (this text)
INFO - Display BMC FW Revision
LOC [0,1] - Locator LED Control
P [0,1] - Power Control
Q - Quit/Logout
RS [s] - Reset System [and switch to sys console]
SE - Read System Event Log
TOC [s] - Send an INIT/TOC [and switch to sys console]
RX2600 consoles
Management Processor (MP)
• Optional on RX2600, standard on RX4640 and up
• Minimum MP firmware for VMS is E2.22
• Uses it own processor with private ethernet adapter
• Username/Password protected
• Snoop EFI serial line and send out characters over
serial line, TELNET or WWW (requires IP address)
• Supports multiple session, but only one controls
input
page 214/22/04
• ^B used to enter remote console
• Can control power and reset system
• TC command can force a crash dump
• All console terminal I/O stored in NVRAM
RX2600 consoles
page 224/22/04
MP Command Set
RX2600 consoles
Forcing a system crash
• History
– On VAX and early Alpha system, ^P was detected by
special hardware and handled by the console
– Commodity serial ports pushed ^P detection in
console firmware, if IPL < DEVICE_IPL
• EFI console ignores ^P, no way to return to EFI Shell
• IA64 VMS console terminal driver handles ^P
page 234/22/04
– Calls XDELTA, if loaded
– Prompts for forced crash, if IPL < DEVICE_IPL
• Remote console command generates Transfer of
Control signal (BMC:TOC, MP:TC)
– Handled by IA64 VMS as a non-maskable exception
and results in a crash dump regardless of IPL
RX2600 consoles
page 244/22/04
Future bootstrap options
• Fibre Channel
– Similar to SCSI boot, but new vendor-specific setup
program to replaces the common SRM WIDMGR tool
• Network boot
– Uses PXE (pixie) instead of MOP
– LAD/LAST booting scheduled for 8.2
– Cluster NISCS boot is post 8.2
• Partition system support for Superdome
– VMS demo on Hard partition, Galaxy support in the
future
• Memory disk boot under investigation
– Use container file to eliminate boot drivers
– Used by HP-UX and Linux and VAX/VMS to boot TK50
Ctrl/H and the Delete Key .................................................................................................................................5
Console Input, Output, and Error ...................................................................................................................... 5
Setting the Console Device.......................................................................................................................... 6
BMC System Console.......................................................................................................................................... 10
Powering System On/Off from the BMC........................................................................................................ 11
Booting OpenVMS from the BMC ................................................................................................................. 11
Forcing a Crash ................................................................................................................................................ 12
Connect to Service Processor ................................................................................................................... 18
Date .............................................................................................................................................................. 18
Disconnect Remote or LAN Console ....................................................................................................... 19
Front Panel Process ................................................................................................................................... 19
Display System ID...................................................................................................................................... 20
Configure LAN Console............................................................................................................................ 21
LAN Status.................................................................................................................................................. 21
Return to Main Menu................................................................................................................................21
Power Control ............................................................................................................................................ 22
PC: Power Control—turn system power on and off................................................................................... 22
Power Status ............................................................................................................................................... 22
PS: Power status—display the status of the power management module. ................................................ 22
Reset System ............................................................................................................................................... 23
Set Access .................................................................................................................................................... 23
Create Local Session.................................................................................................................................. 23
System Status.............................................................................................................................................. 24
Transfer Of Control .................................................................................................................................. 25
User Configuration .................................................................................................................................... 25
Virtual Front Panel.................................................................................................................................... 25
Exit from MP.............................................................................................................................................. 26
Gaining Control of the Console................................................................................................................ 26
Management Processor Help System ...................................................................................................... 26
Powering System On/Off from the MP Console ............................................................................................ 27
Booting OpenVMS from the MP Console...................................................................................................... 30
Forcing a Crash ................................................................................................................................................ 33
help command ............................................................................................................................................ 47
info ............................................................................................................................................................... 52
The HP Integrity Server system provides two console options: the Baseboard Management Console (BMC)
and the Management Processor (MP) console. Both consoles can be used to power-cycle the systems and
perform hardware-related operations. In addition to the low-level console functions, the Integrity Server
system has a replacement for the SRM console in the Alpha processors, Extensible Firmware Interface
(EFI). This document provides command summaries and examples of commonly used commands for both
the BMC and the MP.
Ctrl/H and the Delete Key
Unlike OpenVMS, which uses the character 0X7F DEL/RUBOUT, the BMC and the MP consoles and the
EFI environment use Ctrl/H. If you press the Delete key on a VTxxx terminal or the key you have mapped
to send 0X7F in your terminal emulator, the character is not deleted.
This occurrence has triggered a new SYSGEN parameter, TTY_DEFCHAR3, and a new SET TERMINAL
COMMAND to tell the terminal driver to re-map Ctrl/H to DEL. If you want the re-mapping to be system
wide for all terminals, you need to OR 0x10 into the current value stored in TTY_DEFCHAR3. If you
want to re-map a single terminal, issue the command:
$ set terminal/backspace=delete
Doing this allows you to change your terminal or terminal emulator to send Ctrl/H instead of DEL. When
using command-line editing, you can still return to the start of the line by pressing the F12 key on a VTxxx
terminal, or you can enter Ctrl/V Ctrl/H Ctrl/H.
If you set your terminal to re-map Ctrl/H to DEL, the driver does not perform the re-mapping operation if
the terminal is in one of the following states:
o
Terminal attribute is set to PASSALL
o Terminal attribute is set to PASTHRU
o IO$_READALL
o IO$_READPBLK
o Entering Ctrl/V tells the driver to pass the next character and skip the re-map check.
Console Input, Output, and Error
Currently, OpenVMS has two console restrictions for both the BMC and MP consoles:
1. The input, output, and error devices of these must point to a serial line console.
2. They must all be the same serial device.
If these conditions are not met you receive a warning out to the VMS_LOADER, and you may see other
errors in later parts of the boot. Additionally, you may lose output that you would normally expect to see
when booting.
Version 1.2Page 64/22/04
Setting the Console Device
Step 1Power on the system. You should initially hook up to the console line on the
management processor.
******************************************************************
Only default users are configured.
Use one of the following user/password pairs to login:
(c) Copyright Hewlett-Packard Development Company, L.P. 1999-2003. All
Rights Reserved.
MP Host Name: kthulu
Revision E.02.22
******************************************************************
MP ACCESS IS NOT SECURE
Default MP users are currently configured and remote access is enabled.
Modify default users passwords or delete default users (see UC command)
OR
Disable all types of remote access (see SA command)
******************************************************************
MP MAIN MENU:
CO: Console
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Log
SL: Show Event Logs
CSP: Connect to Service Processor
SE: Enter OS Session
HE: Main Help Menu
X: Exit Connection
MP Host Name: kthulu
MP> cm
(Use Ctrl-B to return to MP main menu.)
MP Host Name: kthulu
MP:CM> pc -on -nc
Version 1.2Page 74/22/04
PC -on -nc
System will be powered on.
-> System is being powered on.
-> Command successful.
MP Host Name: kthulu
MP:CM> exit
MP MAIN MENU:
CO: Console
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Log
SL: Show Event Logs
CSP: Connect to Service Processor
SE: Enter OS Session
HE: Main Help Menu
X: Exit Connection
MP Host Name: kthulu
MP> co
You will now get lots of output from the system powering up. Eventually, you will get to this menu.
EFI Boot Manager ver 1.10 [14.61] Firmware ver 2.20 [4331]
Please select a boot option
EFI Shell [Built-in]
Boot Option Maintenance Menu
System Configuration Menu
Use ^ and v to change option(s). Use Enter to select an
option.
Step 2
Select the "Boot Option Maintenance Menu" using either "v" "^" or ! "
EFI Boot Maintenance Manager ver 1.10 [14.61]
Main Menu. Select an Operation
Boot from a File
Add a Boot Option
Delete Boot Option(s)
Change Boot Order
Manage BootNext setting
Set Auto Boot TimeOut
Select Active Console Output Devices
Select Active Console Input Devices
Select each of the consoles and set the active console device. Use either "v" "^" or !
". For this example, we will change only the console output device. When you select
the output device, you receive a display something like the one below:
Using either the "v" "^" or ! ", move to the device you want to select or deselect.
Pressing the Space bar changes the state, and the asterisk (*) indicates what is
selected. In the above list, the Management Processor is selected and set to emulate a
VT100. If you select Acpi(PNP0501,0)/Uart(9600 N81)/VenMsg(Vt100), the
console is the BMC console labeled as console/serial A on the back of the system.
Step 5After making your changes, select the "Save Setting to NVRAM" and then exit.
Step 6Repeat Steps 4 and 5 for the output and error devices.
Step 7Finally, perform a cold reset of the system. If you changed the console from MP to
the BMC or vice versa, you may need to move the serial cable to the appropriate
connector on the system.
Version 1.2Page 94/22/04
Console Comparison
The following lists provide the advantages and disadvantages of the BMC and MP consoles.
BMC Console
Advantages
o Simple to use.
o Small command set.
o Mode-less. You are either at its command prompt or you are not.
Disadvantages
o
Single user.
o
Limited features.
o Not available on many of the systems.
MP Console
Advantages
o Can be multi user. One user can issue commands to the EFI layer or the operating system, and
multiple users can view it.
o
Accessible by way of telnet or the web.
o Feature rich.
o Keeps log of last ~58 lines of display on the console. Now you can see what was really entered
instead of getting it second hand.
o
Can manipulate the server event logs.
o Supports dial-in access.
o Supports UPCs.
Disadvantages
o
Not on all systems.
o More complex to perform simple operations like power cycling the system.
o Command menu and non-command menu commands, and you have to flip back and forth.
Version 1.2Page 104/22/04
BMC System Console
On the RX2600, the Baseboard Management Console (BMC) is accessible through the serial port on the
back of the system labeled Console/Serial A. This port is set to 9600 baud 8 bit no parity and one stop bit.
Entering Console Mode
To get the console processors attention and enter command mode, enter <ESC>(. You receive the cli>
prompt, at which point you can enter commands.
Exiting Console Mode
To exit the console processor command mode, enter <ESC>Q. If OpenVMS is running, you are returned
to the operating system prompt.
Command Summary
CommandDescription
C [<passwordstring>]Change Password
CONDisplay console selection
FPLRead forward progress log
HHelp
I <ipmi command data>Send any IPMI message
resp fmt: ccode [data]
LOC [0,1]Locator LED control
P [0,1]Power control
QQuit/Logout
RS [s]Reset system [and switch to sys console]
SDRead SDR repository
SERead System Event Log
TOC [s]Send an INIT/TOC [and switch to sys console]
Version 1.2Page 114/22/04
Powering System On/Off from the BMC
To power a system on, enter the following commands:
<ESC>(
cli>p 1
System Power set to ON
To power the system off, enter the following commands:
<ESC>(
cli>P 0
System Power set to OFF
Booting OpenVMS from the BMC
Step 1Get the consoles attention by entering <ECS>(
<ESC>(
cli>
Step 2Power the system on.
cli>p 1
System Power set to ON
cli>
Step 3Exit console mode <ESC>Q, and wait for the EFI command menu. (Note that some
systems may have been set to time out after a small number of seconds.) You see the
Shell> prompt.
EFI Boot Manager ver 1.10 [14.61] Firmware ver 2.20 [4331]
Please select a boot option
EFI Shell [Built-in]
Boot Option Maintenance Menu
System Configuration Menu
Use ^ and v to change option(s). Use Enter to select an option
Step 4Use "v", or "^", ! " to select the "EFI Shell [Built-in]". You then get the Shell>
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 3-NOV-2003 12:32:35.45
Accounting information:
Buffered I/O count: 2114 Peak working set size: 13424
Direct I/O count: 1601 Peak virtual size: 220384
Page faults: 2899 Mounted volumes: 0
Charged CPU time: 0 00:00:05.96 Elapsed time: 0 00:00:36.44
Forcing a Crash
To force a crash of OpenVMS, first try entering Ctrl/P. If the system is booted with XDelta, you can then
enter the ;c command to force a crash. If the system is not booted with XDelta, you see the following:
Crash (y/n): y
**** OpenVMS I64 Operating System XA0K-J2S - BUGCHECK ****
** Bugcheck code = 00000965: DEBUGCRASH, Debugger forced system crash
** Crash CPU: 00 Primary CPU: 00 Active CPUs: 00000003
** Current Process = NULL
** Current PSB ID = 00000001
** Image Name =
**** Starting compressed selective memory dump at 30-OCT-2003 17:34...
Loading...
+ 58 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.