This document describes the Server Mangagement Command Line Interface
(CLI) to hp AlphaServer ES47/ES80/GS1280 systems.
The CLI provides access to the whole platform at the most fundamental level.
You can display information, such as the system configuration, cabling, and
environmental component status. You can update the firmware and power the
system or a hard partition on or off, as well as halt and reset. You can create
and delete partitions.
The CLI also provides one of the two ways you can access the SRM console or
operating system running within the system or a partition.
HP shall not be liable for technical or editorial errors or omissions contained herein. The information in this document
is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for HP
products are set forth in the express limited warranty statements accompanying such products. Nothing herein should
be construed as constituting an additional warranty.
Regulatory Notices for Series ET2003
FCC Notice
Part 15 of the Federal Communications Commission (FCC) Rules and Regulations has established Radio Frequency
(RF) emission limits to provide an interference-free radio frequency spectrum. Many electronic devices, including
computers, generate RF energy incidental to their intended function and are, therefore, covered by these rules. These
rules place computers and related peripheral devices into two classes, A and B, depending upon their intended
installation. Class A devices are those that may reasonably be expected to be installed in a business or commercial
environment. Class B devices are those that may reasonably be expected to be installed in a residential environment
(i.e., personal computers). The FCC requires devices in both classes to bear a label indicating the interference potential
of the device as well as additional operating instructions for the user. The rating label on the device shows which class
(A or B) the equipment falls into. Class B devices have an FCC ID on the label. Class A devices do not have an FCC
ID on the label. Once the class of the device is determined, refer to the following corresponding statement.
Class A Equipment
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of
the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case
the user will be required to correct the interference at personal expense.
Class B Equipment
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of
the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential
installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications. However, there is no
guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference
to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to
try to correct the interference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio or television technician for help.
Modifications
The FCC requires the user to be notified that any changes or modifications made to this device that are not expressly
approved by Hewlett-Packard Company may void the user's authority to operate the equipment.
Cables
Connections to this device must be made with shielded cables with metallic RFI/EMI connector hoods in order to
maintain compliance with FCC rules and regulations.
Declaration of Conformity for products marked with the FCC logo – United States only
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) This
device may not cause harmful interference, and (2) this device must accept any interference received, including
interference that may cause undesired operation.
Page 3
Taiwanese Notice
Japanese Notice
Canadian Notice (Avis Canadien)
Class A Equipment
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing
Equipment Regulations. Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur
du Canada.
Class B Equipment
This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.Cet
appareil numérique de la classe B respecte toutes les exigences du Règlement
sur le matériel brouilleur du Canada.
European Union Notice
Products with the CE marking comply with the EMC Directive (89/336/EEC) and the Low Voltage
Directive (73/23/EEC) issued by the Commission of the European Community and if this product has
telecommunication functionality, the R&TTE Directive (1999/5/EC).
Compliance with these directives implies conformity to the following European Norms (in parentheses
are the equivalent international standards and regulations):
Index .........................................................................................................................Index-1
iv
Page 7
How to Access the Server Management CLI
Chapter 1
How to Access the Server Management CLI
1.1 Access the CLI from the SPM
If your site has an AlphaServer Management Station (AMS) running the Server Platform
Management (SPM) software, and you have administrator or operator access to it, you can use
the SPM window to telnet into the Server Management CLI of a particular platform. You can do
this in three different ways:
1.1.1 From the SPM "Actions" Menu Item
Once you have logged in to the SPM as a valid user, you can left-click on a platform in either the
tree view or the right-hand view. Once you select a platform, you can left-click on the "Actions"
menu item to telnet to the Server Management CLI of the platform you selected.
1-1
Page 8
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
1.1.2 From the SPM Tree View
Once you have logged in as a valid SPM user, you can directly right-click on a platform in the tree
view to display a pulldown menu from which you can telnet to the Server Management CLI for
that system.
1-2
Page 9
How to Access the Server Management CLI
1.1.3 From the SPM Platform View
From the right pane of the SPM window, you can right-click on a platform to display a pulldown
menu that allows you to telnet to the Server Management CLI of that particular platform.
1-3
Page 10
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
1.2 Access the CLI from the AMU
You can access the Server Management CLI interface from the AlphaServer Management Utility
interface as follows:
1. Click on the "Platform" icon in the tree view. (Remember that the AMU is only attached
to a single platform at a time.)
2. Pull down the "Actions" menu and select "Open Telnet" from the options available, as
shown below.
1.3 Access the CLI from a PC Telnet session
You can access the Server Management CLI from a PC attached to the Corporate LAN or the
Multi-Server LAN by installing KEAterm or similar software on the PC.
Instructions for installing this software on your PC is given in the ES47/ES80/GS1280 Service Manual.
1-4
Page 11
How to Access the Server Management CLI
1.4 Access the CLI from the MBM Backplane
You can attach a serial terminal directly to an MBM backplane to access the Server Management
CLI.
Figure 1-1
Figure 1-1 8-P Drawer MBM Backplane Serial Connector
shows the serial connector for the MBM backplane on an 8P drawer.
1-5
Page 12
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
Figure 1-2 shows the serial connector for the MBM backplane on a 2P drawer.
Figure 1-2 2-P Drawer MBM Backplane Connector
1-6
Page 13
How to Access the Server Management CLI
1.5 Accessing the Server Management CLI from the SRM
Console
If you have accessed the SRM console or operating system for a platform (or for a partition or
subpartition within a platform), you can access the Server Management CLI for the platform by
entering the escape sequence <Esc><Esc>MBM.
1-7
Page 14
Page 15
Command Line Interface
Chapter 2
Command Line Interface
The server management command line interface (CLI) performs these tasks for the ES80 and
GS1280 servers:
• Displays system configuration information
• Updates firmware
• Powers on and off, halts, and resets the system or partition
• Provides system partitioning and cabling functions
• Shows the status of fans and power supplies, as well as temperatures
• Implements remote server management
• Connects to the virtual SRM console
Typically the CLI is used on smaller systems that do not use the graphical AlphaServer
Management Utility (AMU).
2.1 Component Addressing
Each component is addressed by its cabinet and drawer thumbwheel in hex. The qualifiers cabinet and -drawer are used throughout the server management CLI. For some commands, a
CPU can be specified by its mesh coordinates, -ew and -ns.
Type Address Note
8P drawer -cabinet <cabinet> -drawer <drawer> SBB cabinet = 0–7, drawer = 0–3
MBM -cabinet <cabinet> -drawer<drawer> MBM cabinet = 0–7, drawer = 0–3
DUO -cabinet <cabinet> -drawer<drawer> DUOnn = 0–3 in the 8P drawer
CMM -cabinet <cabinet> -drawer<drawer> CMMnn = 0–3 in the 8P drawer
CPU -cabinet <cabinet> -drawer<drawer> CPUnn = 0–7 in the 8P drawer
CPU -ew <ew_coord> -ns <ns_coord> CPU by mesh coordinate (ew, ns)
IOP -cabinet <cabinet> -drawer <drawer> IOPnn = 0–7 in the 8P drawer; for IO cabling
PCI drawer -cabinet <cabinet> -drawer <drawer> PCI cabinet = 0–F, drawer = 0–F
PBM -cabinet <cabinet> -drawer <drawer> PBM cabinet = 0–F , drawer = 0–F
IOR -cabinet <cabinet> -drawer <drawer> IORnn = 0–3 in the PCI drawer
2.2 Environment Variables
Server management environment variables are settings in the MBM, PBM, and CMM that tailor
their behaviors. They are analogous to SRM environment variables.
All SM variables are global and stored in the flash. The names are case insensitive ASCII strings
with maximum length of 32 characters including NULL. If the variable type is integer, please
specify the value in hex.
The command “show *” lists all variables, as shown in Example 2-1.
2-1
Page 16
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
Example 2-1 The “show *” Command Lists All Environment Variables
MBM> show *
cpu_enabled FFFFFFF
diag_mask 0
diag_min_flag off
esc_sequence ^[^[MBM
halt_on_error on
mfg_mode off
ocp_text GS1280
srm_auto_connect off
MBM>
part_force_striping Bool Off Modify force_striping On - All partitions are treated
Type
or
Range
int
int
On or
off
(15
chars)
On or
off
On or
off
(20
chars)
Default
Value
Actions
Description
32 F's Modify symbol
cpu_enabled
24 F's Modify symbol diag_maskSelective tests to be run
Off Modify symbol
min_diag_flag and
diag_mask
^[^[MBM Modify symbol
mbm_escape_string
On Modify symbol
halt_on_error
Off Modify symbols
envmon_shutdownEnable
envmon_intrusionEnable
envmon_overtempEnable
product
name
Modify the new string to
OCP.
Bit mask of cpus to configure
into the partition
When non-zero, only a
minimal set of diagnostics is
run. Remember, this is
required for semi-hard
partitions.
A sequence to go back to
MBM>
On - any failure in starting a
partition halts the startup
attempt and returns to the
prompt.
Off - the server manager
automatically maps out the
failing components and retries
starting the now degraded
partition.
On – under this mode, the
system will never be turned
off regardless of any
environmental events. Also
assume all covers are closed.
Text (usually system name) to
be displayed on all drawer
OCPs.
2-2
Page 17
Command Line Interface
on or
off
srm_auto_connect Bool
on or
off
Off Modify symbol
cli_autoconnect
2.3 Partition Naming and Addressing
as striped.
Off - The striping attributed
indicated from partition
creation is used. The
Default_HP is created nonstriped, so the force_striping
variable is handy to make that
partition behave as a striped
partition.
On - the output from the
SRM/OS automatically is
directed to the MBM session.
At the end of the diagnostic
tests, the MBM does a
connect command
automatically.
Off – Stay at the CLI after
system powers up
A key attribute of the ES80/GS1280 server is its ability to be divided into partitions, each of which
appears to be a separate computer. A partition contains CPU, memory, and I/O resources.
These servers can be:
• Hard partitioned, with no routing traffic between CPUs.
• Soft partitioned, with routing between all CPUs. All memory access is allowed, and
protection is accomplished through software.
The server management is responsible for creating, configuring, testing, saving, and deleting
partitions.
The partition name is limited to a maximum of 19 characters and restricted to alphanumeric,
underscore, and dash characters. Free_Pool is a reserved name for indicating the partition's pool
of resources that any partition can allocate. It is legal to have the same subpartition name as the
hard partition or to have the same subpartition names under different hard partitions.
A partition must be addressed by name in the format -hp <hard_partition_name> -sp <sub_partition_name>.
2-3
Page 18
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
2.4 Conventions
Convention Meaning
Fixedfont
Italic
Bold
<item> In command syntax descriptions, angle brackets indicate a placeholder for an
[item] In command syntax descriptions, square brackets enclose optional
{a, b, c} In command syntax descriptions, braces containing items separated by
{a | b | c} In command syntax descriptions, braces containing items separated by
Examples are shown in a fixed-width font for clarity and to preserve
alignment of output, as they would appear on the console terminal device.
Italic type is used to express emphasis.
Command and option keywords embedded in narrative text sections are
presented in bold type.
item that the user must specify.
parameters, qualifiers, or values.
commas imply mutually exclusive items. "{a, b, c}" indicates that you can
choose from a, b, or c.
vertical bars imply combinatorial items. "{a | b | c}" indicates that you can
choose any combination of a, b, and c.
2.5 Command Names and Qualifiers
The server management CLI interface is case insensitive.
Command names consist of a command verb and, in some cases, a keyword. Each comma nd
verb and keyword might have an abbreviation, which is determined by the CLI parser. For
example, the minimum match for show system is sh sys. If a user continues typing more than
the minimum, the optional characters must match the full name. This means that sh syst will
work, but sh sysa will not. The optional characters are displayed in square brackets ([ ]) under
the command name in the online help.
The character - introduces a qualifier. Qualifiers may be single characters ("flags") or multiple
characters. The exact match has the highest precedence. A multiple character qualifier can be
abbreviated as long as its partial match is unique within the command. For instance, -c is
sufficient for the qualifier -cabinet if the command has no other qualifiers starting with the letter
“c."
2-4
Page 19
Command Line Interface
2.6 Editing
The following keys can be used in editing Server Management CLI commands:
Key Function
Backspace Delete the character; the cursor moves to the left
Delete Delete the character; the cursor stays at its position
Down arrow Get next command
End key Moves the cursor to the end of the command line
Home key Moves the cursor to the beginning of the command line
Insert key Toggles to select "Insert" or "Overwrite" mode
Left arrow Move the cursor to the left within the command line
Page Up Reserved for future use
Page Down Reserved for future use
Right arrow Moves the cursor to the right within the command line
Ctrl A Toggle to select "insert" or "overwrite" mode
Ctrl B Recall the previous line
Ctrl C Abort the command
Ctrl D Cancel the current line
Ctrl E Move the cursor to the end of the command line
Ctrl F Move the cursor to the right within the command line
Ctrl H Move the cursor to the beginning of the command line
Ctrl R Reprint the command line
Ctrl U Clear the command line
Other rules include:
• Extra spaces are ignored.
• Everything between the "#" character and the end of the line is treated as a comment.
• The previous 16 commands in the current session can be recalled by using the up arrow
and down arrow keys.
•The use of double quotes is supported; everything inside the quotes is treated as-is. This
is helpful for arguments containing spaces or # (comments).
For example:
MBM> build fru CAB0.DRW0.MBM "partnumber" "serialnum" "mbm module"
MBM> sh fru
Fru Name E Part # Serial # Model/Other
CAB0.DRW0.MBM 00 partnumber serialnum mbm module
2-5
Page 20
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
•Command abort. If you get tired of a long and complicated command display or action,
type CTRL/C ( ^C). The command is aborted mid-stream.
For example:
MBM> sh fru
Fru Name E Part # Serial # Model/Other
CAB0.DRW0.DOCP 00 nightlyFri_0 Fri_43
CAB0.DRW0.MBM 00 partnumber serialnum mbm module
CAB0.DRW0.DUO0.CMM 10 nightlyFri_2 Fri_45
CAB0.DRW0.DUO0.DUO 00 nightlyFri_3 Fri_46
~CLI-E-(tCLImodem) command aborted by Ctrl-C
MBM>
•Invalid commands are echoed for easy identification.
For example:
The brief help for each command displays the syntax and a one-line description. The synopsis
line lists all possible options and arguments for the command.
By default, issuing the command help displays a list of supported commands, and help * lists all
commands with their descriptions and syntax. You can also specify a particular command for
help. For example:
MBM>help show cable
NAME
sh[ow] cab[le]
FUNCTION
Display the cable configuration.
SYNOPSIS
show cable [-ip | -io]
MBM>
In the name line, the characters in square brackets ([]) are considered optional. As shown above,
the minimum abbreviated form of show cable is sh cab.
2-6
Page 21
Command Line Interface
If you issue a command with syntactic errors, an error message followed by the correct command
usage is displayed, as shown here:
MBM>set time
~CLI-W-(tCLImodem): invalid parameters
Usage: set time <date> <time>
MBM>
2.8 MBM Failsafe Loader
If the main MBM firmware image becomes corrupt, the failsafe loader allows the user to recover
the system. It also allows the user to load a network-bootable MBM image over the network if
configured to do so.
Upon application of VAUX, the failsafe loader is the first piece of firmware to run. It performs
power-up diagnostics on the MBM hardware, and then loads/runs the main image. If the main
image is missing or corrupt, the failsafe loader will attempt to automatically install the update from
the PMU server. If the automatic updating fails, the failsafe loader will sit and wait at the FSL CLI
prompt. (“FSL> “)
2.8.1 Configuration & Booting Images
From the FSL CLI, two commands are available that are not available in the main MBM firmware
image. Bootline will configure the boot settings of MBM. Mbmboot will boot the MBM based on
the settings contained in the boot line. The bootline menu is shown below.
FSL> bootline
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : flash0
processor number : 0
host name : host
file name : vxWorks
inet on ethernet (e) : 10.250.250.250
inet on backplane (b):
host inet (h) : 10.253.0.254
gateway inet (g) :
user (u) : target
ftp password (pw) (blank = use rsh):
flags (f) : 0xa0
target name (tn) :
startup script (s) :
other (o) : fei
The bootline options allow control over the name of the file to boot, the server to get the file from,
and startup flags. To boot an image over the network, change the boot device from flash to fei.
(Type “fei” and hit enter) To advance to the next option, hit enter without typing anything.
In practice, the only needed options are the boot device, the filename, the host inet (host to
download from). The other settings should be left to their default values.
2-7
Page 22
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
2.8.2 Updating Firmware Images
The failsafe loader supports updating of firmware images. In order to update an image on a
micro running its failsafe loader, you must specify its cabinet, drawer, and micro type. For
example, to update the main MBM image from the failsafe loader (downloading from MBM1), type
the following command:
The failsafe loader supports online help like the normal CLI. Typing “help” at the FSL prompt will
produce a list of commands included in the failsafe loader. To get help on a specific command,
type “help <cmdname>”.
FSL> help
NAME
help
FUNCTION
Display information about CLI commands.
SYNOPSIS
help [<command>, *]
Command synopsis conventions:
<item> Implies a placeholder for user specified item.
<item>... Implies an item or list of items.
[] Implies optional keyword or item.
{a,b,c} Implies any one of a, b, c.
{a|b|c} Implies any combination of a, b, c.
The following help topics are available:
clear clear alert clear display clear error
clear log clear port d deposit
e el enable alert enable remote
enable test help logout reset
rlogin set set alert set baud
set dial set escape set flow set init
set password set time shell show
show cables show duo show error show fru
show log show memor show modem show network
show power show system show time show version
update uptime
FSL>
2-8
Page 23
Command Line Interface
2.9 CLI Output Messages
The server management CLI may display messages that are not the result of a user command.
The output messages consist of a general format:
~Facility-Severity-(taskName): detailed messages
Facility The area that detects the error
Severity I additional information
W warning messages
E error messages
F fatal operations
taskName tCLImodem
For example, an error occurred at the user interface
MBM> crete
~CLI-E-(tCLImodem) unrecognized command verb: crete
MBM> create prt
~CLI-E-(tCLImodem) unrecognized keyword: prt
Usage: create {partition}
MBM> show sys -blah
~CLI-W-(tCLImodem): unrecognized qualifiers
Usage: show system
MBM>
Some common CLI output messages are given in the table below.
Message Possible Cause
Common Messages
~CLI-E: input too long
The command line is longer than 80 characters.
~CLI-E: unrecognized command verb The first word of the command name is invalid.
~CLI-E: unrecognized keyword The second word of the command name is
invalid.
~CLI-E: unrecognized qualifiers A command switch qualifier either didn't exist,
or wasn't enough to be unique.
~CLI-E: conflicting qualifiers The command switches/qualifiers specified
were contradictory.
~CLI-E: too many parameters Too many command switches/qualifiers were
specified.
~CLI-E: insufficient parameters Not enough command switches/qualifiers were
specified.
~CLI-E: invalid parameters The command switch was invalid
~CLI-E: illegal digit for specified radix Characters other than 0–9 were used for integer
2-9
Page 24
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
and 0–F for hex
~CLI-E: numeric value too large The value is overflow.
Command-Specific Messages
~CLI-E: illegal target address
~CLI-E: illegal data
~CLI-E: deposit data too large for
specified type
~CLI-E: invalid device name
~CLI-E: string too long
~CLI-E: string too short
2-10
Page 25
Commands
Chapter 3
Commands
3.1 Command Summary
Command Function
assign {component, memory} Assign resources to a partition.
bootlineChange the bootline used in boot ROMs.
build fru Write FRU-specific information to a FRU’s
config cables Configure or assist cabling.
connect Connect to the system COM port of a partition.
create partition Create a hard or subpartition.
delete partition Delete a hard or subpartition.
deposit or d Write data to a memory location or CSR, IPR,
disable {
el Event log - show the history of CLI inputs and
enable {
examine or e Read a memory location or CSR, IPR, or I2C
halt {
hangup Terminate the modem or telnet connection.
help Display the entire list of CLI commands.
init modem Initialize the modem.
locateLocate the specified component (system
logout Log out of the remote host.
mbmboot or @ (Works only from the failsafe loader.) Boots the
modify partitionChanges the attributes of a hard partition.
power {
reset Reset a system, CPU, or partition.
save partition Save the partition data to the NVRAM.
alert, remote, test} Disable the sending of alerts, remote access, or
alert, remote, test} Enable the modem dial-out alert function,
in, out} Halt the entire system, CPU, or partition.
off, on} Power off or on a system, component, or
Clear the SPMU environment variable, the 'alert
pending’ flag, all error fields in the specified
FRU, the screen or serial port, or SRM
environment variables for all partitions, for a
specific hard partition, or for a specific
subpartition within a hard partition.
2
or I
C device
a diagnostic test
outputs.
remote access to the system, or a diagnostic
test.
device.
building block, PCI drawer, dynamic duo, or
power supply) by blinking its LEDs.
main MBM/PBM image from flash or from the
network.
partition.
3-1
Page 26
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
set {<envar>, alert, baud, dial, escape,
flow, init, membership, password, sys
serial num
show {<envar>, cables, duo, error, fru,
grid, log, membership, memory, modem,
network, partition, power, sys_serial_num,
system, time, version}
telnetLog in to a remote host.
test {<test_num>, alert, led} Start a diagnostic test, or test the modem setup
update Update the firmware.
uptimeShow the amount of time since initialization of
, time}
Modify the server management CLI
environment.
Show specified system information.
or cable LEDs.
all or specified MBMs and PBMs.
3-2
Page 27
Commands
3.2 assign component
Assigns CPU and IO resources to a partition.
Note: A CPU and its associated IOs cannot be separated across hard partitions. In order to move
the IOP to a different hard partition, move its associated CPU to the targeted partition, and the
IOP will automatically follow the CPU to the same destination. The IOP can be moved around
between subpartitions within the same hard partition.
~CLI-E-(tCLImodem) cannot move IOP across different HP
MBM> [2003/04/11 10:21:36]
~PCO-W-(pco)01) Command handler rtn failed for Id:5622 cmd:41a
See Also
show partition, show system, create partition, assign memory
3-4
Page 29
Commands
3.3 assign memory
Assigns a portion of the hard partition’s physical memory to a subpartition. Explicitly assigning
memory to a hard partition is unnecessary because the RIMM population associated with each
CPU determines the partition's memory size.
Users cannot assign memory to the Free_Pool.
The smallest memory chunk allowed is 8MB.
To deassign memory, specify 0MB as the memory size.
<memory_size> The memory size in units of GB or MB; must be
multiples of 8MB.
-hp <hard_partition> Hard partition name.
-sp <sub_partition> Subpartition name.
-com Assign the memory to community memory, accessible to
all subpartition within the hard partition.
Options
None
Examples
1. Assign 16GB of memory to the subpartition acct_usa.
MBM> assign mem 16GB –hp account_dept -sp acct_usa
MBM>
2. Assign 2GB of memory to the community.
MBM> assign mem 16GB -hp account_dept -com
MBM>
3. Deassign memory from the subpartition acct_usa. Memory for this subpartition becomes
unspecified.
MBM> assign mem 0MB -hp account_dept -sp acct_usa
MBM>
3-5
Page 30
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
See Also
show partition, create partition, assign component
3-6
Page 31
Commands
3.4 bootline
This command is usually used from the FSL. Changes the boot line used in the boot ROMs.
bootline determines the boot device, file name, and, if it is a network boot, the TFTP IP address.
If you are configuring to boot over a network and are booting multiple micros simultaneously,
configure each “inet on Ethernet” address to be unique among those micros. You can use the
micro IP address.
Syntax
bootline
Arguments
None
Options
None
Example
Change the method of booting to boot from the network by modifying the boot device to be fei
and “inet on Ethernet” to be 10.0.0.1. (Make sure that the "host inet" IP address matches the
TFTP server interface IP.)
FSL> bootline
'.' = clear field; '-' = go to previous field; ^D = quit
boot device : flash0 fei
processor number : 0
host name : host
file name : vxWorks
inet on ethernet (e) : 10.250.250.250 10.0.0.1
inet on backplane (b):
host inet (h) : 10.253.0.254
gateway inet (g) :
user (u) : target
ftp password (pw) (blank = use rsh):
flags (f) : 0xa0
target name (tn) :
startup script (s) :
other (o) : fei
FSL>
See Also
mbmboot, @
3-7
Page 32
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.5 build fru
Sets the part number and serial number of the FRU.
“Inaccessible” errors are usually due to IIC error.
FRU can be specified with qualifiers,
e.g. 'build fru -cab 0 -draw 2 -duo 1 VRM0.TERM'
or with the long format as listed in 'show fru' output,
e.g. 'build fru CAB0.DRW2.DUO1.VRM0.TERM'.
'build fru -rimm' for RIMM serialization.
RIMM serialization:
A unique RIMM FRU serial number in ASCII is based on the 12 character system serial number
concatenated with a 4 numeric alpha sequence number (0-9 then A-Z) determined by the RIMM’s
location. These 4-byte “CDSIs” are defined as the following:
C - Cabinet number represented by ASCII 0-7.
D - Duo number represented by ASCII hex 0-F within the cabinet.
It is calculated by (Drawer_num *4 + Duo_num). For example, 9 means drawer 2, duo 1. (Drawer
number ranges 0-3. So is Duo number within the drawer)
R - RIMM slot in Duo. ASCII 0-9 for CPU 0 RIMM 0-9.
ASCII A-J for CPU1 RIMM 0-9.
I - Insertion count (ASCII 0-9, then A-Z).
Firmware can't directly detect the RIMM insertion. A counter keeps track of how many times of
RIMM serialization done per Duo RIMMs and is stored in the DUO EEPROM.
RIMMs are usually serialized once. If the RIMMs are moved from one system to another, the
ones with mismatched sys_serial_num will be serialized upon request.
of SBB
PWRn.PSpPower supply of SBB
CLM Common Logic Module (of
Superdome PS subsysem)
DUO, CMM, VRM and RIMM require the additional
qualifier “-duo” to indicate the residency.
part_num FRU’s part number. This field contains the FRU revision.
(This is a 16-character ASCII string with no embedded
spaces.)
serial_num FRU’s serial number. This ASCII string must be 10
characters.
model The FRU’s model name or number or alias. This ASCII
string may be up to 10 characters. This field is optional and
does not apply to third-party FRUs.
offset The beginning byte offset inhex within this FRU's
EEPROM, where the following data bytes are written.
byte... Up to 16 data bytes to be written. At least one byte must
be supplied after the offset.
Commands
Options
-cabinet <cabinet> Cabinet number in hex. If not specified, defaults to 0.
-drawer <drawer> Drawer number in hex. If not specified, defaults to 0.
-duo <duo> Dual-CPU module number in decimal.
-s Write raw data to the EEPROM. Used to apply any
FRU-specific data. Checksum is automatically
updated after the raw data is written.
-rimm Build a unique serial number across all RIMMs. The
RIMM number is based on the 12-character system
serial number concatenated with a 4-digit sequence
number determined by the RIMM's location. These
four digits, CDSI, are defined as:
C - Cabinet number 0 - 7
D - Duo number 0 - F (ASCII hex). It is calculated by
(drawer_num * 4 + duo_num)
S - RIMM slot 0 - 9 for CPU0, RIMM0-9; and A - J for
CPU1, RIMM0-9>
I - Insertion count (ASCII 0-9, then A-Z)
3-9
Page 34
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
Examples
1. Write the manufacture data to the EEPROM of the MBM.
3. Deposit 0x9C to the location 0x1F of IOR0 EEPROM in cabinet 1, drawer 4.
MBM> build fru -ca 1 -dr 4 ior0 -s 1F 9C
or
MBM> build fru CAB1.DRW4.IOR0 –s 1F 9C
MBM>
4. Serialize the RIMMs. Unique RIMM serial numbers usually are not programmed by the
vendor.
MBM> sh fru
Fru Name E Part # Serial # Model/Other
CAB0.DRW0.DOCP 00 nightlyFri_0 Fri_43
CAB0.DRW0.MBM 00 partnumber serialnum mbm module
CAB0.DRW0.DUO0.CMM 10 nightlyFri_2 Fri_45
CAB0.DRW0.DUO0.DUO 00 nightlyFri_3 Fri_46
CAB0.DRW0.DUO0.RIMM00 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM10 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM20 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM30 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM50 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM60 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM70 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM80 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM01 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM11 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM21 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM31 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM51 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM61 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM71 40 20-1C872-01 CE
CAB0.DRW0.DUO0.RIMM81 40 20-1C872-01 CE
CAB0.DRW0.DUO0.VRM0.CPU 00 nightlyFri_4 Fri_47 7F7FF8
CAB0.DRW0.DUO0.VRM1.CPU 00 nightlyFri_5 Fri_48 7F7FF8
CAB0.DRW0.DUO0.VRM2.CPU 00 nightlyFri_6 Fri_49 7F7FF8
CAB0.DRW0.DUO0.VRM3.CPU 00 nightlyFri_7 Fri_50 7F7FF8
CAB0.DRW0.DUO0.VRM4.CPU 00 nightlyFri_8 Fri_51 7F7FF8
CAB0.DRW0.DUO0.VRM2.RIMM 00 nightlyFri_9 Fri_52 7F7FF8
CAB0.DRW0.DUO0.VRM3.RIMM 00 nightlyFri_10 Fri_53 7F7FF8
CAB0.DRW0.DUO0.VRM4.RIMM 00 nightlyFri_11 Fri_54 7F7FF8
CAB0.DRW0.DUO0.VRM0.TERM 00 nightlyFri_12 Fri_55 7F7FA2
CAB0.DRW0.DUO1.CMM 10 nightlyFri_13 Fri_56
CAB0.DRW0.DUO1.DUO 00 nightlyFri_14 Fri_57
~CLI-E-(tCLImodem) command aborted by Ctrl-C
MBM> show sys_serial_num
SYS_SERIAL_NUM GS1280-32P
3-10
Page 35
MBM> build fru -rimm
Building RIMM serial numbers....
MBM> sh fru
Fru Name E Part # Serial # Model/Other
CAB0.DRW0.DOCP 00 nightlyFri_0 Fri_43
CAB0.DRW0.MBM 00 partnumber serialnum mbm module
CAB0.DRW0.DUO0.CMM 10 nightlyFri_2 Fri_45
CAB0.DRW0.DUO0.DUO 10 nightlyFri_3 Fri_46
CAB0.DRW0.DUO0.RIMM00 06 20-1C872-01 GS1280-32P000L CE
CAB0.DRW0.DUO0.RIMM10 06 20-1C872-01 GS1280-32P001L CE
CAB0.DRW0.DUO0.RIMM20 06 20-1C872-01 GS1280-32P002L CE
CAB0.DRW0.DUO0.RIMM30 06 20-1C872-01 GS1280-32P003L CE
CAB0.DRW0.DUO0.RIMM50 06 20-1C872-01 GS1280-32P005L CE
CAB0.DRW0.DUO0.RIMM60 06 20-1C872-01 GS1280-32P006L CE
CAB0.DRW0.DUO0.RIMM70 06 20-1C872-01 GS1280-32P007L CE
CAB0.DRW0.DUO0.RIMM80 06 20-1C872-01 GS1280-32P008L CE
CAB0.DRW0.DUO0.RIMM01 06 20-1C872-01 GS1280-32P00AL CE
CAB0.DRW0.DUO0.RIMM11 06 20-1C872-01 GS1280-32P00BL CE
CAB0.DRW0.DUO0.RIMM21 06 20-1C872-01 GS1280-32P00CL CE
CAB0.DRW0.DUO0.RIMM31 06 20-1C872-01 GS1280-32P00DL CE
CAB0.DRW0.DUO0.RIMM51 06 20-1C872-01 GS1280-32P00FL CE
CAB0.DRW0.DUO0.RIMM61 06 20-1C872-01 GS1280-32P00GL CE
CAB0.DRW0.DUO0.RIMM71 06 20-1C872-01 GS1280-32P00HL CE
CAB0.DRW0.DUO0.RIMM81 06 20-1C872-01 GS1280-32P00IL CE
CAB0.DRW0.DUO0.VRM0.CPU 00 nightlyFri_4 Fri_47 7F7FF8
CAB0.DRW0.DUO0.VRM1.CPU 00 nightlyFri_5 Fri_48 7F7FF8
CAB0.DRW0.DUO0.VRM2.CPU 00 nightlyFri_6 Fri_49 7F7FF8
CAB0.DRW0.DUO0.VRM3.CPU 00 nightlyFri_7 Fri_50 7F7FF8
CAB0.DRW0.DUO0.VRM4.CPU 00 nightlyFri_8 Fri_51 7F7FF8
CAB0.DRW0.DUO0.VRM2.RIMM 00 nightlyFri_9 Fri_52 7F7FF8
CAB0.DRW0.DUO0.VRM3.RIMM 00 nightlyFri_10 Fri_53 7F7FF8
CAB0.DRW0.DUO0.VRM4.RIMM 00 nightlyFri_11 Fri_54 7F7FF8
CAB0.DRW0.DUO0.VRM0.TERM 00 nightlyFri_12 Fri_55 7F7FA2
CAB0.DRW0.DUO1.CMM 10 nightlyFri_13 Fri_56
CAB0.DRW0.DUO1.DUO 10 nightlyFri_14 Fri_57
CAB0.DRW0.DUO1.RIMM00 06 20-1C872-01 GS1280-32P010L CE
CAB0.DRW0.DUO1.RIMM10 06 20-1C872-01 GS1280-32P011L CE
CAB0.DRW0.DUO1.RIMM20 06 20-1C872-01 GS1280-32P012L CE
CAB0.DRW0.DUO1.RIMM30 06 20-1C872-01 GS1280-32P013L CE
CAB0.DRW0.DUO1.RIMM50 06 20-1C872-01 GS1280-32P015L CE
~CLI-E-(tCLImodem) command aborted by Ctrl-C
MBM>
Commands
Note: The part and serial numbers are made up in this document.
See Also
build fru, show error, clear error
3-11
Page 36
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.6 clear
Clears the value of a server management environment variable and restores the default value if
there is one.
Syntax
clear
<smv>,
*
Arguments
smv The server management environment variable.
* Wildcard for all server management environment variables.
Options
None
Example
Restore the default setting of the environment variable auto_connect_srm.
MBM> clear srm_auto_connect
MBM>
See Also
show, set
3-12
Page 37
Commands
3.7 clear alert
Clears the current alert condition for the modem dial-out.
This command will cause the Server Management CLI on this platform to stop paging the remote
operator through the modem. However, it does not prevent server management from issuing
alerts to other platform's. If the alert for modem dial-out is not cleared, the Server Management
CLI will continue to page the remote operator every 30 minutes. If the sending of alert messages
is disabled, the triggering of alerts continues to occur, but nothing will be sent over the modem.
Also, the most recent alert is logged as the alert type. If the system is in secure mode (via the
Operator Control Panel keyswitch), the sending of alerts is still allowed, even through remote
access into the system is not.
Syntax
clear alert
Arguments
None
Options
None
Examples
This command removes any pending interrupts and allows the capturing of subsequent alert
conditions. The command returns one of two messages depending on whether or not an ale rt
is currently pending.
1. With no alerts pending.
MBM> clear alert
No alert pending
MBM>
2. With alerts pending.
MBM> clear alert
Pending alert cleared
MBM>
See Also
enable alert, test alert
3-13
Page 38
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.8 clear display
Erases the current display screen on the console terminal.
Syntax
clear display
Arguments
None
Options
None
Example
Clear the terminal display.
MBM> clear display
MBM>
3-14
Page 39
Commands
3.9 clear error
Clears the TDD and SDD error log entries and checksum errors in the EEPROM located on the
specified FRU. "Inaccessible" are usually due to IIC error.
Syntax
clear error
Arguments
fru_nam
e
The FRUs are:
{{[-cabinet <cabinet> -drawer <drawer>
-duo <duo>] <fru_name>}, -all}
COCP Cabinet OCP
DOCP Drawer OCP
MBM MBM module
PCI PCI backplane
PBM PBM module
IOR PCI IO riser
SIO SIO
DUO Dual-CPU module
CMM CMM module
VRMn.CPU VRM (n = 0-5) for CPUs
VRMn.RIMM VRM (n = 0-4) for RIMMs
VRM0.TERM VRM for terminator
RIMMnc RIMMs (n = 0-9 for slot number, c = 0-1 for CPU
processor number)
PSnPCI power supply (n = 0-1)
PWRnPower supply tray (n = 0-1) of SBB
PWRn.PSpPower supply of SBB
CLM Common Logic Module (only exists with Superdome
Power Supply subsystem)
DUO, CMM, VRM and RIMM require the additional qualifier “-duo” to indicate the
residency.
Options
-cabinet <cabinet> Cabinet number in hex. If not specified,
defaults to 0.
-drawer <drawer> Drawer number in hex. If not specified,
defaults to 0.
-all All FRUs in the drawer.
3-15
Page 40
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
Examples
1. This command clears all TDD and SDD errors from a FRU’s EEPROM. Use the show error
command to find the proper FRU name and to verify that errors have been cleared.
MBM> show error
FRU Name E Symptoms
CAB0.COCP 70 FRU Checksum error between bytes 0-62
FRU Checksum error between bytes 64-126
FRU Checksum error between bytes 128-254
CAB0.DRW0.DOCP 70 FRU Checksum error between bytes 0-62
FRU Checksum error between bytes 64-126
FRU Checksum error between bytes 128-254
CAB0.DRW0.MBM 10 FRU Checksum error between bytes 0-62
CAB0.DRW0.DUO2.DUO 40 FRU checksum error between bytes 128-254
CAB0.DRW0.DUO2.RIMM00 40 FRU checksum error between bytes 128-254
CAB0.DRW0.DUO2.RIMM10 40 FRU checksum error between bytes 128-254
CAB0.DRW1.PCI 70 FRU Checksum error between bytes 0-62
FRU Checksum error between bytes 64-126
FRU Checksum error between bytes 128-254
CAB0.DRW1.IOR0 70 FRU Checksum error between bytes 0-62
FRU Checksum error between bytes 64-126
FRU Checksum error between bytes 128-254
MBM> clear error -ca 0 COCP
MBM> clear error -ca 0 -dr 0 DOCP
MBM> clear error -ca 0 -dr 1 IOR0
MBM> show error
FRU Name E Symptoms
CAB0.DRW0.MBM 10 FRU Checksum error between bytes 0-62
CAB0.DRW0.DUO2.DUO 40 FRU checksum error between bytes 128-254
CAB0.DRW0.DUO2.RIMM00 40 FRU checksum error between bytes 128-254
CAB0.DRW0.DUO2.RIMM10 40 FRU checksum error between bytes 128-254
CAB0.DRW1.PCI 70 FRU Checksum error between bytes 0-62
FRU Checksum error between bytes 64-126
FRU Checksum error between bytes 128-254
2. Clear errors of all FRUs.
MBM> clear error -all
MBM> show error
Cab Dwr Duo Fru E Symptoms
MBM>
See Also
show error, build fru, show fru
3-16
Page 41
Commands
3.10 clear log
Erases all error log entries in the MBM and PBM flash. (It takes a few seconds to erase each
flash.)
hp <hard partition> Clear SRM environment variables for the hard
partition named.
sp <subpartition> Clear the SRM environment variables for the
soft partition named. Clear all subparitions
within the hard partition if no explicit
subpartition is given.
all Clear the SRM environment variables for all
partitions.
Examples
1. Clear the SRM environment variables for all subpartitions within a
given hard partition.
MBM> clear srmenv -hp hp0
MBM>
2. Clear the SRM environment variables for a given subpartition.
MBM> clear srmenv -hp hp0 -sp default_sp
MBM>
3-19
Page 44
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.13 config cables
Adds a new cable or verifies the configuration of all cables. This command assists in locating the
proper connector pair to connect the cable. The LEDs at each connector are lit until the next
connection is issued. This command also tests all cable connections if no parameter is given.
-c1 <source_cabinet> Cabinet number of the source 8P in hex.
-d1 <source_drawer> Drawer number of the source 8P in hex.
-c2<dest_cabinet> Cabinet number of the destination 8P in hex.
-d2 <dest_drawer> Drawer number of the destination 8P or PCI drawer in
hex.
source_port Either the IP port or IOP. IP port is denoted by N02,
N46, S13, S57, E67, W01. IOP is denoted by IOP<n>
dest_port Either the IP port or PCI IOR. IP port is denoted by N02,
N46, S13, S57, E67, W01. PCI IOR is denoted by
IOR<n>
Options
-led {on, off} The options on or off turn the LEDs on or off. By default, the LEDs
are on.
Examples
1. Verify all cable connections and turn off the LEDs.
MBM> config cables}
Configuring all cables...
Completed. Please use 'show cable' to view the configuration.
MBM>
2. Configure the cable between the south IP port of 8P drawer 1 on cabinet 0 and the north
IP port of 8P drawer 0 in cabinet 1. The LEDs for both ports are lit.
3. Configure the cable of the south IP port of 8P drawer 1 in cabinet 0. Without providing the
destination port, the cabling function finds the matching destination cable according to the
mess configuration. The LEDs of both ports are lit.
MBM> config cables -c1 0 -d1 1 S13 #Turn on LEDs by default
MBM>
4. Configure the cable between IOP3 of 8P drawer 0 on cabinet 1 and IOR0 of PCI drawer 3
on cabinet 4.
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.14 connect
Establishes a system COM1 session to a partition. This command starts a virtual terminal session
to the primary CPU in the partition so that the user can access the SRM console or operating
system. Enter the escape sequence <ESC><ESC>MBM to return to the server management CLI.
–hp and –sp are not needed if the system has only one subpartition (excluding Free_Pool). -sp
is not needed if there is only one subpartition in a given hard partition.
Each session has the MBM's or PBM’s IP address and a unique port number.
The SM environment variable "srm auto_connect" will control the auto connect feature. If it is set
to be "on", "connect" is issued automatically upon resetting or powering on a non-partitioned
system. Also, the current implementation of the connect command only handles communicating
with the SRM on CPU0.
Syntax
connect
[-hp <hard_partition> [-sp <sub_partition>]]
Arguments
-hp <hard_partition> Hard partition name.
-sp <sub_partition> Subpartition name.
Options
None
Examples
1. Connect to a non-partitioned system.
MBM> connect
Connecting to partition. Use the sequence ^[^[MBM to return.
P00>>>
3-22
Page 47
Commands
2. Connect to the partition acct_usa and then return to the server management CLI by
typing the escape sequence.
MBM> connect -hp account_dept –sp acct_usa
P00>>>
.
Connecting to partition. Use the sequence ^[^[MBM to return.
.
P00>>>
.
.
.
P00>>> ^[^[MBM
MBM>
3. Connect to the only subpartition within the hard partition hr_dept.
MBM> connect -hp hr_dept
.
Connecting to partition. Use the sequence ^[^[MBM to return.
.
P00>>>
See Also
hangup
3-23
Page 48
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.15 create partition
Creates a partition. This command adds a new hard partition by providing the hard partition
name, maximum number of CPUs, subpartition type, and optional modifiers. It creates a
subpartition if the subpartition name is given. No attributes are necessary for a subpartition. (You
assign component or assign memory to define the components of a partition or subpartition.)
use
If no hard partitions are defined, a Default_HP and Default_SP are created with all CPUs and IOs
belonging to the Default_SP. The creation of the first user-created hard partition causes the
Default_HP to be deleted. The components of the deleted Default_HP go to the Global
Free_Pool. Whenever a hard partition is created, a Default_SP along with the Free_Pool is
created under that hard partition. When the first user-defined subpartition is created under a hard
partition, the Default_SP is deleted and its components go to the Global Free_Pool.
-hp <hard_partition> Hard partition name. The name is limited to 19 characters
(alphanumeric and underscore only) and it cannot be
Default_HP or Free_Pool.
-sp <sub_partition> Subpartition name. The name is limited to 19 characters
(alphanumeric and underscore only) and it cannot be
Default_SP or Free_Pool.) . A hard partition is created if no
subpartition name is given.
max_CPUs The maximum number of CPUs that can ever be placed in the
hard partition. This value is used to determine the proper routing
and memory algorithm.
sub_partition_type The type of subpartitions in this hard partition:
1. Create a hard partition account_dept with a maximum of 8 CPUs, define any
subsequently created subpartitions as soft partitions, and request memory striping.
show partition, modify partition, delete partition, assign component, assign memory
Commands
3-25
Page 50
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.16 delete partition
Destroys a partition. Returns all resources of the specified partition to the Free_Pool. The
partition(s) being destroyed must be in the halt or power-off state.
When the last user-defined subpartition within a hard partition is deleted, a Default_SP within that
hard partition is created with no components. When the last user-defined hard partition in the
system is deleted, a Default_HP and Default_SP are created with all CPUs and IOs belonging to
the Default_SP. The user cannot delete the Free_Pool.
MBM> delete part -hp account_dept -sp Free_Pool
~CLI-E-(tCLImodem) disallow deleting sub partition Free_Pool
Usage: delete partition {-hp <hard_partition> [-sp <sub_partition>],
-all}
MBM>
3. Delete the entire hard partition account_dept
MBM> delete partition –hp account_dept
MBM>
4. Delete all partitions. A Default_HP and Default_SP are created.
MBM> delete partition -all
MBM>
3-26
Page 51
Commands
See Also
show partition, save partition, create partition, modify partition
3-27
Page 52
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.17 deposit or d
Writes the contents of a storage location. This command enables users to write data to CPU
registers, micro memory, micro IO space, or any I
users must specify the I
2
C controller, sub bus, I2C address and the microprocessor it connects to.
* The set of arguments to the latest deposit or examine command is used.
device The supported devices are MBM, CMM, PBM, CPU<n>
address The address to be written to, in hex. The default is 0.
data The data to be written, in hex.
Options
-b Perform a byte transaction.
-w Perform a word transaction.
-l Perform a longword transaction.
-q Perform a quadword transaction. This is the default deposit size
and also the default for GPR and IPR accesses.
-n <count> The number of subsequent locations specified in hex. The address
is incremented by the address size qualifier each time. The default
is 0. This is not a sticky qualifier.
-ipr Specifies a CPU IPR.
-pmem Specifies the physical memory space of a device such as MBM,
PBM, CMM and CPU.
-io Specifies the IO space of a micro such as MBM, PBM and CMM.
-cabinet <cabinet> Cabinet number in hex. If not specified, the cabinet number from
the last deposit or examine command is used.
-drawer <drawer> Drawer number in hex. If not specified, the drawer number from the
last deposit or examine command is used.
-iic
<ctlr>/<bus>/<iicdev>
iic
ctlr
bus
iicdev
A qualifier that introduces an I
2
I
C controller.
2
I
C sub bus.
2
C device address in hex with read enable.
I
2
C device.
Examples
1. Write some value to IPR 0x11 of CPU3 in drawer 1 of cabinet 0. Then read it back.
2. Set up configuration register 0 of LM80 on the MBM I
C bus, PS controller 1, sub bus 0
with the iic address of 50 hex.
MBM> deposit -ca 0 -dr 3 pbm -iic 1/0/50 0 7
3. Write to the MBM memory space
MBM> e -ca 0 -dr 2 mbm 20 -n 3 –pmem # examine MBM memory space 0/2/mbm/pmem:
20 FC
0/2/mbm/pmem: 21 D3
0/2/mbm/pmem: 22 20
0/2/mbm/pmem: 23 00
MBM> deposit * e0 –n 3 # write to MBM memory space
MBM> e * -n 3
0/2/mbm/pmem: 20 E0
0/2/mbm/pmem: 21 E0
0/2/mbm/pmem: 22 E0
0/2/mbm/pmem: 23 E0
MBM>
Commands
See Also
examine, e
3-29
Page 54
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.18 disable alert
Turns off the modem dial-out function. This command will only disable the modem dial-out. It
does not prevent server management from issuing alerts to other platforms. Getting the remote
operator's attention is essential to insure the environmental conditions do not damage the
hardware.
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.20 disable test
Turns off a diagnostic test. This will disable certain SRM/XSROM tests from running for debug
purpses.
Syntax
disable test
<test_number>
Argument
test_number The number assigned to a diagnostic test in
hex.
Options
None
Example
Disable XSROM test 12, which is Data Pattern March read/write..
MBM> show diag_mask
diag_mask FFFFFFFFFFFFFFFFFFFFFFFF
MBM> disable test 12
MBM> show diag_mask
diag_mask FFFFFFFFFFFFFFFFFFFBFFFF
See Also
enable test, show
3-32
Page 57
Commands
3.21 el
Displays the current event log. Use this command to review recent command history. The event
log contains the most recent (up to 2 KB) events that have passed through the MBM and PBM.
Syntax
el
Arguments
None
Options
None
Example
Show the most recent activities.
MBM> el[2003/04/10 03:11:02]
~REC-W-(trecTask) Server management group is transitioning.
[2003/04/10 03:11:02]
~REC-W-(trecTask) Server management group is stable.
[2003/04/10 03:11:10]
~ENV-W-(envmon) PBM(cab:01, drw:2) Non Hot Plug Cover was opened
[2003/04/10 03:13:35]
~PCO-I-(pco_02) Preparing to power on partition. HP: HP0
[2003/04/10 03:13:35]
~PCO-I-(pco_03) Preparing to power on partition. HP: HP1
[2003/04/10 03:13:54]
~PCO-I-(pco_02) Running diagnostics on HP: HP0
[2003/04/10 03:13:58]
~PCO-I-(pco_03) Running diagnostics on HP: HP1
[2003/04/10 03:14:38]
~PCO-I-(pco_02) Diagnostics completed on HP: HP0
[2003/04/10 03:14:38]
~PCO-I-(pco_02) HP:HP0 SP:Default_SP Primary is NS:0 EW:0 which is cab:00 drw:0 cpu:0
[2003/04/10 03:14:39]
~PCO-I-(pco_02) Loading SRM on Primary for HP: HP0, SP: Default_SP.
[2003/04/10 03:14:43]
~PCO-I-(pco_02) Powered On HP:HP0
[2003/04/10 03:15:23]
~PCO-I-(pco_03) Diagnostics completed on HP: HP1
[2003/04/10 03:15:24]
~PCO-I-(pco_03) HP:HP1 SP:Default_SP Primary is NS:2 EW:0 which is cab:00 drw:1 cpu:0
[2003/04/10 03:15:24]
~PCO-I-(pco_03) Loading SRM on Primary for HP: HP1, SP: Default_SP.
[2003/04/10 03:15:28]
~PCO-I-(pco_03) Powered On HP:HP1
MBM>
See Also
clear display
3-33
Page 58
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.22 enable alert
Turns on the modem dial-out function. This command is triggered whenever an alert condition
occurs. An alert is sent every 30 minutes until either alerts are disabled or the alert is cleared.
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
Enable XSROM test 12, which is Data Pattern March read/write).
MBM> set diag_min_flag on
MBM> show diag_mask
diag_mask 000000010003000300030000
MBM> enable test 12
MBM> show diag_mask
diag_mask 000000010003000300070000
MBM>
See Also
disable test, show
3-36
Page 61
3.25 examine or e
Commands
Reads the contents of a storage location. This command enables users to read the data from
2
CPU registers, micro memory, micro IO space or any I
device, a user must specify the I
2
C controller, sub bus, I2C address, and the microprocessor it
C device. In order to access any I2C
connects to. Users can also write to any MBM/PBM symbol, mainly for debugging purposes.
* The latest set of arguments to the examine command is used.
device The supported devices are MBM, CMM, PBM, IIC, GPR, IPR
address The address to be read. The default is 0.
Options
-b Perform a byte transaction.
-w Perform a word transaction.
-l Perform a longword transaction.
-q Perform a quadword transaction. This is the default for GPR and
IPR accesses.
-n <count> The number of subsequent locations, in hex. The address is
incremented by the address size qualifier each time. The default
is 0.
-ipr Specifies a CPU IPR.
-pmem Specifies the physical memory space of a device such as MBM,
PBM, CMM, or CPU.
-io Specifies the IO space of a micro such as MBM, PBM or CMM.
-cabinet <cabinet> Rack number in hex. If not specified, the cabinet number from the
last deposit or examine command is used.
-drawer <drawer> Box number in hex. If not specified, the drawer number from the
last deposit or examine command is used.
-iic
<ctlr>/<bus>/<iicdev>
iic
ctlr
bus
iicdev
A qualifier that introduces an I
2
I
C controller.
2
I
C sub bus.
2
C device address in hex with read enable.
I
2
C device.
Examples
1. Write some value to IPR 0x11 of CPU3 in drawer 1 of cabinet 0. Then read it back.
-sp <subpartition> Subpartition name. Optional if there is only one
subpartition within the given hard partition.
MBM The micro MBM
PBM The micro PBM
port The port number that the MBM/PBM is
connected to. Port 23 is for CLI and port 322 for
Vxworks shell.
Options
-cabinet <cabinet> Cabinet number in hex. Defaults to 0 if not
specified.
-drawer <drawer> Drawer number in hex. Defaults to 0 if not
specified.
Examples
1. Terminate the console connection.
MBM> hangup -hp Default_HP
MBM>
2. Terminate a telnet session..
MBM> hangup -ca 1 -dr 0 PBM 23
MBM>
See Also
connect, telnet
3-43
Page 68
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.29 help
Displays information about server management CLI commands. Describes command
conventions and available commands by default; includes a detailed description and syntax for a
given command.
Syntax
help
[<command>, *]
Arguments
command The command to be displayed.
* Display all commands.
Options
None
Examples
1. List the help topics.
MBM> help
NAME
help
FUNCTION
Display information about CLI commands.
SYNOPSIS
help [<command>, *]
Command synopsis conventions:
<item> Implies a placeholder for user specified item.
<item>... Implies an item or list of items.
[] Implies optional keyword or item.
{a,b,c} Implies any one of a, b, c.
{a|b|c} Implies any combination of a, b, c.
The following help topics are available:
assign component assign memory bootline build fru
clear clear alert clear display clear error
clear log clear port clear srmenv config cables
connect create partition d delete partition
deposit disable alert disable remote disable test
e el enable alert enable remote
enable test examine halt in halt out
hangup help init modem locate
logout modify partition power off power on
reset save partition set set alert
set baud set dial set escape set flow
set init set membership set password set sys_serial_num
set time show show cables show duo
show error show fru show grid show log
show membership show memory show modem show network
show partition show power show system show sys_serial_num
show time show version telnet test
test alert test led update uptime
MBM
>
3-44
Page 69
2. Help on a particular command. The characters in square brackets ([]) are optional.
MBM> help show cable
NAME
sh[ow] cab[le]
FUNCTION
Display the cable configuration.
SYNOPSIS
show cable [-ip | -io]
MBM>
Commands
3-45
Page 70
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.30 init modem
Initializes the modem using the user-defined initialization string.
Syntax
init modem
Arguments
None
Options
None
Examples
Initialize the modem and allow remote access to the system if the initialization
succeeds.
1. A modem is present and the initialization completes.
Locate the specified component. This command will cause LEDs to blink in the specified cabinet
(blue and yellow LEDs), drawer (yellow LED), or module (yellow LED). The LEDs blink for 30
seconds at one-second intervals to help you locate the component of SBB, PCI, duo, and power.
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.35 power off
Turns off the power to a system, component, or partition. This command powers off a nonpartitioned system if no arguments are given, or it powers off a specific hard partition or
component.
Use the show power command to confirm the power state.
DUO<n> The dual-CPU module by cabinet and drawer number. n refers to the module
within the 8P drawer and ranges from 0 to 3.
IOR<n> IOR by cabinet and drawer number. n refers to the IO riser within the PCI
drawer and ranges from 0 to 3 for the Expanded I/O drawer.
PCI The PCI drawer by cabinet and drawer number.
SBB The entire system building block.
Options
-cabinet <cabinet> Cabinet number in hex. If not specified, the number
defaults to 0.
-drawer <drawer> Drawer number in hex. If not specified, the number
defaults to 0.
-hp <hard_partition> Hard partition name.
-all All partitions.
Examples
1. Power off a system with only one hard partition. This is the only case in which the power
off command can be used without arguments.
MBM> power off
[2003/04/10 03:09:43]
~PCO-I-(pco 04) Preparing to power off partition. HP: Default_HP
MBM>
2. Issuing the power off command without arguments returns an error if the system has
more than one hard partition.
MBM> p off
~CLI-E-(tCLImodem) need to specify partition or component
Usage: power off [{[-cabinet <cabinet> -drawer <drawer>] {DUO<n>, PCI, SBB}},
{-hp <hard_partition>}, {-all}]
MBM>
3-52
Page 77
3. Power off hard partition account_dept.
MBM> power off -hp account_dept
[2003/04/10 03:09:43]
~PCO-I- (pco 01) Preparing to power off partition. HP: account_dept
MBM>
4. Power off all partitions.
MBM> power off –all
[2003/04/10 03:09:43]
~PCO-I-(pco_04) Preparing to power off partition. HP: HP0
[2003/04/10 03:09:44]
~PCO-I-(pco_00) Preparing to power off partition. HP: HP1
[2003/04/10 03:09:44]
~PCO-I-(pco_03) Preparing to power off partition. HP: HP2
[2003/04/10 03:09:45]
~PCO-I-(pco_01) Preparing to power off partition. HP: HP3
MBM>
5. Power off dual-processor module 3 in drawer 2 of cabinet 0.
MBM> power off -ca 0 -dr 2 duo3
MBM>
Commands
6. Power off 8P drawer 2 of cabinet 0.
MBM> power off -ca 0 -dr 2 sbb
MBM>
7. Power off PCI drawer 2 of cabinet 0xA.
MBM> power off -ca 1 -dr 2 pci
MBM>
See Also
power on, show power
3-53
Page 78
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.36 power on
Turns on the power to a system, component, or partition.
If no arguments are given, this command powers on a system with one hard partition. By using
arguments, you can power on a specific hard partition or component.
When there is only one hard partition, the screen display shows the entire power up sequence
like the grid and diagnostics. However, if more then one hard partitions is defined in the
database, the hard partitions are powered on in parallel, a maximum of four hard partitions s at a
time. The detailed power up progress messages like the grid and the diagnostics messages, are
sent to the console session and do NOT come out on the MBM session.
Given two hard partitions (Yankees and RedSox) each with two sub-partitions (Jeter and Bernie
in Yankees, and Pedro and Noma in RedSox) issuing either “power on –all”, “power on –hp RedSox”, or “Power on –hp Yankees” will power up the partitions and send the output to
the console session. When a user connects to the console session (conn –hp RedSox –sp Pedro) the powerup messages (the grid and diagnostics) will be displayed. All of the subpartition console buffers will contain the grid and diagnostics power up messages.
Any diagnostic failures from any hard partition are delivered to the MBM session for high visibility.
They also are sent to the console session.
Use the show power command to confirm the power state.
DUO<n> The dual-processor module by cabinet and drawer number. n refers to the module
within the 8P drawer and ranges from 0 to 3.
IOR<n> IOR by cabinet and drawer number. n refers to the IO riser within the PCI drawer
and ranges from 0 to 3 for he Expanded I/O shelf. (Note: Do not leave the IOR
power on if its connected CPU is off.)
PCI The PCI drawer by cabinet and drawer number.
SBB The entire system building block.
Options
-cabinet <cabinet> Cabinet number in hex. If not specified, the number defaults to
0.
-drawer <drawer> Drawer number in hex. If not specified, the number defaults to
0.
-hp <hard_partition> Hard partition name.
-all All partitions.
-xsrom Power up until the level at which XROM tests complete.
3-54
Page 79
Commands
Examples
1. Power on a system with only one hard partition. This is the only case in which the power
on command can be used without arguments.
MBM> power on
[2003/04/16 00:06:30]
~PCO-I-(pco_01) Preparing to power on partition. HP: Default_HP
[2003/04/16 00:06:43]
~PCO-I-(pco_01)
Configuring for 22 CPUs for HP:0 Default_HP
0 1 2 3 4 5 6 7 8 9 A B C D E F
.w..w..w..w..w..w..w..w........................
0 wP--P--P--F--P--P--P--Fw.......................
.|..|..|..|..|..|..|..|........................ P Processor
.|..|..|..|..|..|..|..|........................ F Filler
............................................... S v (ns,ew)
4 ...............................................
...............................................
...............................................
5 ...............................................
...............................................
...............................................
6 ...............................................
...............................................
...............................................
7 ...............................................
...............................................
0 1 2 3 4 5 6 7 8 9 A B C D E F
[2003/04/16 00:06:54]
~PCO-I-(pco_01) Running diagnostics on HP: Default_HP
Running test 10, Initialize RAMBUS ... on 22 EV7s
Running test 11, Initialize Memory ... on 21 EV7s
Running test 12, Data Pattern March read/write ... on 21 EV7s
Running test 13, RAID channel Test ... on 11 EV7s
Running test 14, Single Bit Error ... on 21 EV7s
Running test 15, Double Bit Error ... on 21 EV7s
Running test 20, Init IO7 and Start Clocks ... on 4 EV7s
Running test 21, IO7 Data Path (Scratch CSR) ... on 4 EV7s
Running test 22, IO Single Bit Error checkers ... on 4 EV7s
Running test 23, IO Double Bit Error checkers ... on 4 EV7s
Running test 24, IO Timer Expirations ... on 4 EV7s
Running test 25, IO up-hose SBE checkers ... on 4 EV7s
Running test 26, IO up-hose DBE checkers ... on 4 EV7s
Running test 27, IO7 pass2 data mover test ... on 4 EV7s
Running test 30, Configure RBOX Routes ... on 22 EV7s
Running test 31, Clear Errors / Enable Routes ... on 22 EV7s
Running test 32, Route Test: N S E W ... on 22 EV7s (North)
Running test 32, Route Test: N S E W ... on 22 EV7s (South)
Running test 32, Route Test: N S E W ... on 22 EV7s (East )
Running test 32, Route Test: N S E W ... on 22 EV7s (West )
Running test 33, Inverse Route Setup ... on 22 EV7s
Running test 32, Route Test: N S E W ... on 22 EV7s (North)
Running test 32, Route Test: N S E W ... on 22 EV7s (South)
Running test 32, Route Test: N S E W ... on 22 EV7s (East )
Running test 32, Route Test: N S E W ... on 22 EV7s (West )
Running test 33, Inverse Route Setup ... on 22 EV7s
Running test 34, Single Bit Error checker ... on 22 EV7s
Running test 35, Double Bit Error checker ... on 22 EV7s
Running test 31, Clear Errors / Enable Routes ... on 22 EV7s
3-55
Page 80
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
Running test 16, Interprocessor Memory Access ... on 21 EV7s
Running test 40, Local I/O Device Interrupts ... on 22 EV7s
Running test 41, Local Interval Timer Interrupts ... on 22 EV7s
Running test 42, Local Interprocess Interrupts ... on 22 EV7s
Running test 43, Software Alerts ... on 1 EV7s
Running test 46, Other Local Interrupt Bits ... on 22 EV7s
[2003/04/16 00:08:40]
~PCO-I-(pco_01) Diagnostics completed on HP: Default_HP
[2003/04/16 00:08:40]
~PCO-I-(pco_01) HP:Default_HP SP:Default_SP Primary is NS:0 EW:0 which is
cab:00 drw:0 cpu:0
Running test 50, Loop on Secondary Routine ... on 21 EV7s (SP:Default_SP)
[2003/04/16 00:08:41]
~PCO-I-(pco_01) Loading SRM on Primary for HP: Default_HP, SP: Default_SP.
Running test 50, Loop on Secondary Routine ... on 0 EV7s
(SP:Free_Pool)[2003/04/16 00:08:45]
~PCO-I-(pco_01) Powered On HP:Default_HP
MBM>
2. Issuing the power on command without arguments returns an error if the system has
more than one hard partition.
MBM> p on
~CLI-E-(tCLImodem) need to specify partition or component
Usage: power on [{[-cabinet <cabinet> -drawer <drawer>] {DUO<n>, PCI, SBB}},
{{-hp <hard_partition>, -all} | [-xsrom]}]
MBM>
3. Power on hard partition account_dept in a multiple-partitioned system:
MBM> power on -hp account_dept
[2003/04/16 00:14:56]
~PCO-I-(pco_02) Preparing to power on partition. HP: account_dept
[2003/04/16 00:15:15]
~PCO-I-(pco_02) Running diagnostics on HP: account_dept
[2003/04/16 00:15:31]
~DIA-W-(pco_02) Test 17 [T12 with isolation info (MFG)] failed on cpu [NS: 0 EW:
1] which is cab:00 drw:0 cpu:2
[2003/04/16 00:16:21]
~PCO-I-(pco_02) Diagnostics completed on HP: account_dept
[2003/04/16 00:16:21]
~PCO-I-(pco_02) HP:account_dept SP:Default_SP Primary is NS:0 EW:0 which is
cab:00 drw:0 cpu:0
[2003/04/16 00:16:21]
~PCO-I-(pco_02) Loading SRM on Primary for HP: account_dept, SP: Default_SP.
[2003/04/16 00:16:25]
~PCO-I-(pco_02) Powered On HP:account_dept
MBM>
4. Power on all partitions.
MBM> power on –all
[2003/04/14 14:13:30]
~PCO-I-(pco_01) Preparing to power on partition. HP: hp0
[2003/04/14 14:13:31]
~PCO-I-(pco_02) Preparing to power on partition. HP: hp1
[2003/04/14 14:13:45]
~PCO-I-(pco_02) Running diagnostics on HP: hp1
[2003/04/14 14:13:48]
~PCO-I-(pco_01) Running diagnostics on HP: hp0
[2003/04/14 14:14:45]
~PCO-I-(pco_02) Diagnostics completed on HP: hp1
[2003/04/14 14:14:45]~PCO-I-(pco_02) HP:hp1 SP:Default_SP Primary is NS:2 EW:0
which is cab:00 drw:1 cpu:0
[2003/04/14 14:14:45]~PCO-I-(pco_02) Loading SRM on Primary for HP: hp1, SP:
Default_SP.
3-56
Page 81
Commands
[2003/04/14 14:14:48]
~PCO-I-(pco_01) Diagnostics completed on HP: hp0
[2003/04/14 14:14:48]
~PCO-I-(pco_01) HP:hp0 SP:Default_SP Primary is NS:0 EW:0 which is cab:00 drw:0
cpu:0
[2003/04/14 14:14:48]
~PCO-I-(pco_01) Loading SRM on Primary for HP: hp0, SP: Default_SP.
[2003/04/14 14:14:50]
~PCO-I-(pco_02) Powered On HP:hp1
[2003/04/14 14:14:53]
~PCO-I-(pco_01) Powered On HP:hp0
MBM>
MBM> conn -hp hp0 -sp default_sp
Connecting to partition. Use the sequence ^[^[MBM to return.
~PCO-I-(pco_01) Preparing to power on partition. HP: hp0
~PCO-I-(pco_01)
Configuring for 8 CPUs for HP:0 hp0
0 1 2 3 4 5 6 7 8 9 A B C D E F
...............................................
0 wP--P--P--Pw...................................
.|..|..|..|.................................... P Processor
.|..|..|..|.................................... F Filler
............................................... S v (ns,ew)
4 ...............................................
...............................................
...............................................
5 ...............................................
...............................................
...............................................
6 ...............................................
...............................................
...............................................
7 ...............................................
...............................................
0 1 2 3 4 5 6 7 8 9 A B C D E F
~PCO-I-(pco_01) Running diagnostics on HP: hp0
Running test 10, Initialize RAMBUS ... on 8 EV7s
Running test 11, Initialize Memory ... on 8 EV7s
. . . . (more progress messages)
P00>>>
5. Power on until xsrom completes.
MBM> power on -all -xsrom
MBM>
6. Power on dual-CPU module 3 in drawer 2 of cabinet 0.
MBM> power on -ca 0 -dr 2 duo3
MBM>
7. Power on 8P drawer 2 of cabinet 0.
MBM> power on -ca 0 -dr 2 ssb
MBM>
3-57
Page 82
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
8. Power on PCI drawer 2 of cabinet 1.
MBM> power on -ca 1 -dr 2 pci
MBM>
See Also
power off, show power, reset, connect
3-58
Page 83
Commands
3.37 reset
Resets a CPU or a partition. This command resets the entire system if it is not partitioned. For a
partitioned system, the user must specify which partition to reset. It also enables a user to
selectively reset a CPU.
When there is only one hard partition, the screen display shows the entire reset sequence like the
grid and diagnostics. However, if more then one hard partition is defined in the database, the
hard partitions are reset on in parallel, a maximum of four hard partitions at a time. The detailed
progress messages like the grid and the diagnostics are sent to the console session and do NOT
come out on the CLI session. When a user connects to the console session, the progress
messages will be displayed. Any diagnostic failures from any hard partition are delivered to the
CLI session for high visibility. They also are sent to the console session.
CPU<n> The CPU by cabinet and drawer number. n refers to the CPU number within the
8P drawer and ranges from 0 to 7.
CPU The CPU by mesh coordinate. The qualifiers -ew and -ns must be used.
micro The micro to be warm reset. It can be CMM<n>, MBM or PBM.
Options
-cabinet <cabinet> Cabinet number in hex. If not specified, the number defaults
to 0.
-drawer <drawer> Drawer number in hex. If not specified, the number defaults
to 0.
-ew <ew_coord> East-West coordinate of the CPU in hex.
-ns <ns_coord> North-South coordinate of the CPU in hex.
-hp <hard_partition>
-micro
-all All partitions or all micros.
-xsrom Reset the system or partition(s) to the level at which XROM
Hard partition name.
Specifies resetting micro.
tests complete.
3-59
Page 84
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
Examples
1. Reset a system with only one hard partition.
MBM> reset
[2003/04/16 00:06:30]
~PCO-I-(pco_01) Preparing to reset partition. HP: Default_HP
[2003/04/16 00:06:43]
~PCO-I-(pco_01) Configuring for 22 CPUs for HP:0 Default_HP
0 1 2 3 4 5 6 7 8 9 A B C D E F
.w..w..w..w..w..w..w..w........................
0 wP--P--P--F--P--P--P--Fw.......................
.|..|..|..|..|..|..|..|........................ P Processor
.|..|..|..|..|..|..|..|........................ F Filler
............................................... S v (ns,ew)
4 ...............................................
...............................................
...............................................
5 ...............................................
...............................................
...............................................
6 ...............................................
...............................................
...............................................
7 ...............................................
...............................................
0 1 2 3 4 5 6 7 8 9 A B C D E F
[2003/04/16 00:06:54]
~PCO-I-(pco_01) Running diagnostics on HP: Default_HP
Running test 10, Initialize RAMBUS ... on 22 EV7s
Running test 11, Initialize Memory ... on 21 EV7s
Running test 12, Data Pattern March read/write ... on 21 EV7s
Running test 13, RAID channel Test ... on 11 EV7s
Running test 14, Single Bit Error ... on 21 EV7s
Running test 15, Double Bit Error ... on 21 EV7s
Running test 20, Init IO7 and Start Clocks ... on 4 EV7s
Running test 21, IO7 Data Path (Scratch CSR) ... on 4 EV7s
Running test 22, IO Single Bit Error checkers ... on 4 EV7s
Running test 23, IO Double Bit Error checkers ... on 4 EV7s
Running test 24, IO Timer Expirations ... on 4 EV7s
Running test 25, IO up-hose SBE checkers ... on 4 EV7s
Running test 26, IO up-hose DBE checkers ... on 4 EV7s
Running test 27, IO7 pass2 data mover test ... on 4 EV7s
Running test 30, Configure RBOX Routes ... on 22 EV7s
Running test 31, Clear Errors / Enable Routes ... on 22 EV7s
Running test 32, Route Test: N S E W ... on 22 EV7s (North)
Running test 32, Route Test: N S E W ... on 22 EV7s (South)
Running test 32, Route Test: N S E W ... on 22 EV7s (East )
Running test 32, Route Test: N S E W ... on 22 EV7s (West )
Running test 33, Inverse Route Setup ... on 22 EV7s
Running test 32, Route Test: N S E W ... on 22 EV7s (North)
Running test 32, Route Test: N S E W ... on 22 EV7s (South)
Running test 32, Route Test: N S E W ... on 22 EV7s (East )
Running test 32, Route Test: N S E W ... on 22 EV7s (West )
Running test 33, Inverse Route Setup ... on 22 EV7s
Running test 34, Single Bit Error checker ... on 22 EV7s
Running test 35, Double Bit Error checker ... on 22 EV7s
Running test 31, Clear Errors / Enable Routes ... on 22 EV7s
Running test 16, Interprocessor Memory Access ... on 21 EV7s
Running test 40, Local I/O Device Interrupts ... on 22 EV7s
Running test 41, Local Interval Timer Interrupts ... on 22 EV7s
3-60
Page 85
Running test 42, Local Interprocess Interrupts ... on 22 EV7s
Running test 43, Software Alerts ... on 1 EV7s
Running test 46, Other Local Interrupt Bits ... on 22 EV7s
[2003/04/16 00:08:40]
~PCO-I-(pco_01) Diagnostics completed on HP: Default_HP
[2003/04/16 00:08:40]
~PCO-I-(pco_01) HP:Default_HP SP:Default_SP Primary is NS:0 EW:0 which is
cab:00 drw:0 cpu:0
Running test 50, Loop on Secondary Routine ... on 21 EV7s (SP:Default_SP)
[2003/04/16 00:08:41]
~PCO-I-(pco_01) Loading SRM on Primary for HP: Default_HP, SP: Default_SP.
Running test 50, Loop on Secondary Routine ... on 0 EV7s (SP:Free_Pool)
MBM>
2. Try to reset a system with more than one hard partition.
MBM> reset
~CLI-E-(tCLImodem) need to specify partition or component
Usage: reset [{[-cabinet <cabinet> -drawer <drawer>] CPU<n>},
{-ew <ew_coord> -ns <ns_coord> CPU},
{{-hp <hard_partition>, -all} [-xsrom]},
{-micro {[-cabinet <cabinet> -drawer <drawer>]CMM<n>,PBM,MBM},
-all}]
MBM>
3. Reset hard partition account_dept and stop after the XSROM tests.
Commands
MBM> reset -hp account_dept –xsrom
[2003/04/16 00:14:56]
~PCO-I-(pco_02) Preparing to reset partition. HP: account_dept
[2003/04/16 00:15:15]
~PCO-I-(pco_02) Running diagnostics on HP: account_dept
[2003/04/16 00:16:21]
~PCO-I-(pco_02) Diagnostics completed on HP: account_dept
[2003/04/16 00:16:21]
~PCO-I-(pco_02) HP:account_dept SP:Default_SP Primary is NS:0 EW:0 which is
cab:00 drw:0 cpu:0
[2003/04/16 00:16:21]
~PCO-I-(pco_02) Loading SRM on Primary for HP: account_dept, SP: Default_SP.
MBM>
4. Reset all partitions.
MBM> reset –all
[2003/04/14 14:13:30]
~PCO-I-(pco_01) Preparing to reset partition. HP: hp0
[2003/04/14 14:13:31]
~PCO-I-(pco_02) Preparing to reset partition. HP: hp1
[2003/04/14 14:13:45]
~PCO-I-(pco_02) Running diagnostics on HP: hp1
[2003/04/14 14:13:48]
~PCO-I-(pco_01) Running diagnostics on HP: hp0
[2003/04/14 14:14:45]
~PCO-I-(pco_02) Diagnostics completed on HP: hp1
[2003/04/14 14:14:45]
~PCO-I-(pco_02) HP:hp1 SP:Default_SP Primary is NS:2 EW:0 which is
cab:00 drw:1 cpu:0
[2003/04/14 14:14:45]
~PCO-I-(pco_02) Loading SRM on Primary for HP: hp1, SP: Default_SP.
[2003/04/14 14:14:48]
~PCO-I-(pco_01) Diagnostics completed on HP: hp0
[2003/04/14 14:14:48]
~PCO-I-(pco_01) HP:hp0 SP:Default_SP Primary is NS:0 EW:0 which is
cab:00 drw:0 cpu:0
3-61
Page 86
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
[2003/04/14 14:14:48]
~PCO-I-(pco_01) Loading SRM on Primary for HP: hp0, SP: Default_SP.
MBM>
MBM> conn -hp hp0 -sp default_sp
Connecting to partition. Use the sequence ^[^[MBM to return.
~PCO-I-(pco_01) Preparing to reset partition. HP: hp0
~PCO-I-(pco_01)
Configuring for 8 CPUs for HP:0 hp0
. . . . (more progress messages)
.
P00>>>
5. Reset CPU 3 in drawer 2 of cabinet 0.
MBM> reset -ca 0 -dr 2 cpu3
MBM>
6. Reset the CPU with mesh coordinate (2, 3).
MBM> reset -ew 2 -ns 3 cpu
MBM>
7. Reset micro CMM 0 of drawer 2 in cabinet 0.
MBM> reset -ca 0 -dr 2 cmm0 -micro
MBM>
8. Reset all micros.
MBM> reset -micro -all
Resetting all micros....
MBM>
See Also
power on, connect
3-62
Page 87
Commands
3.38 save partition
Saves the partition database. This command saves the volatile partition state to the non-volatile
storage NVRAM. All partition data is saved if no explicit partition is given. An entire hard partition
must be saved; a particular subpartition cannot.
Syntax
save partition
[-hp <hard_partition>, -all]
Arguments
None
Options
-hp <hard_partition> Hard partition name.
-all All partitions.
Examples
1. Save all subpartitions under the hard partition account_dept.
MBM>save partition -hp account_dept
MBM>
2. Save all partitions.
MBM>save partition
or
MBM>save partition -all
MBM>
See Also
show partition, create partition, delete partition
3-63
Page 88
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.39 set
Sets the value of a server management environment variable. This command is analogous to the
SRM set command; however, these settings are used to control the behavior of the Server
Management subsystem.
If the variable type is "integer", specify values in hex.
Note: See the section on
environment variables for details.
Syntax
set
<smv> <value>
Arguments
smv Variable name. Names are case insensitive and can consist of a
maximum of 32 characters including NULL.
value The value assigned to the variable. If the variable is of type integer,
specify values in hex.
Options
None
Example
Set the feature that automatically connects to the SRM during
power up.
MBM> set srm_auto_connect 1
MBM>
See Also
show, clear
3-64
Page 89
Commands
3.40 set alert
Sets the modem alert string. This string should be set to a meaningful value, such as the system
serial number or remote access phone number. The maximum string length is 63 characters. The
alert string is sent to the modem after the dial string.
Syntax
set alert
[<alert_string>]
Argument
alert_string The ASCII string that is sent to the modem when an alert condition is
triggered. It is sent after the dial string is sent. Issuing the set alert
command without an alert string causes the current alert string to be
erased.
Options
None
Example
Set up the alert string.
MBM> set alert 15085551212#;
MBM00
Note: The # and ; characters are required to terminate the alert string. Without them the alert
may not be sent to a numeric paging system and dial-in may be disabled.
See Also
set dial, enable alert, test alert, show modem
3-65
Page 90
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.41 set baud
Changes the serial port baud rate. This command enables users to change the baud rate of the
modem port. The baud rate is nonvolatile.
Syntax
set baud
or
set
<modem_baud> <baud_rate>
<baud_rate>
Argument
baud_rate The baud rate for the specified channel; one of 2400, 3600, 4800, 7200, 960 0,
19200, 38400, and 57600.
Options
None
Example
Set the baud rate of the modem port to 38.4k.
MBM> set baud 38400
MBM>
See Also
clear port, set flow, show modem
3-66
Page 91
Commands
3.42 set dial
Sets the modem dial string. The dial string is the target phone number and any appropriate
modem commands required by the target. It is nonvolatile across system resets and power
cycles. The maximum string length is 63 characters. The dial string is sent to the modem before
the alert string.
Because modem commands disallow mixed cases, all alphabetic characters in t he dial string are
converted to uppercase.
Syntax
set dial
[<dial_string>]
Argument
dial_string The ASCII string that is sent to the modem when an alert condition is
triggered. If no argument is given, the dial string is erased.
Options
None
Example
Set up the dial string to call a numeric paging service.
MBM> set dial atdt9,15085551212#;
MBM>
See Also
set alert, enable alert, test alert, show modem
3-67
Page 92
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.43 set escape
Changes the server management CLI escape sequence.
This command enables the user to change the escape sequence used for invoking the server
management CLI. The escape sequence can be any character string, not to exceed 15
characters, and it is case insensitive. A typical sequence consists of two or more control
characters. It is recommended that control characters be used in preference to ASCII characters.
The escape sequence is stored in the MBM's or PBM’s EEPROM. The default escape sequence
is ^[^[SPMU. The escape key on a PC keyboard is equivalent to ^[ (control left-bracket). Either
<esc> or ^[ is acceptable.
Use the show modem command to confirm the escape sequence before exiting the server
management CLI.
Syntax
set escape
[<esc_sequence>]
Argument
esc_sequence The escape sequence for entering the server management CLI. The
default escape sequence is restored if no argument is provided.
Options
None
Example
The following example consists of two instances of the Esc key and the letters FUN. The F is
not displayed when you set the escape sequence because it is preceded by the escape
character.
MBM> set escape un
MBM>
See Also
show modem
3-68
Page 93
3.44 set flow
Changes the flow control of the modem port. The flow control type is nonvolatile.
Syntax
Commands
set flow
set
<flow_control>
or
<modem_flow> <flow_control>
Where modem_flow is a server management environment
variable.
Argument
flow_control The supported flow control types for the modem port: none, software,
hardware, or both.
Options
None
Example
Set the flow control of the modem port.
MBM> set flow hardware
MBM>
See Also
set baud, clear port, show modem
3-69
Page 94
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.45 set init
Sets the initialization string that is sent to the modem when the enable remote command is
issued. The initialization string is stored in the MBM’s EEPROM and has a maximum length of 31
characters.
Because modem commands disallow mixed cases, all alphabetic characters entered in the ini t
string are converted to uppercase. It also automatically configures the modem’s flow control
according to the flow control setting and enables the modem carrier detect features to monitor the
modem connectivity.
Syntax
set init
[<init_string>]
Argument
init_string The ASCII string that is sent to the modem when the system management
CLI attempts to initialize it for remote access and sending of alerts. The
init string is erased if no parameter is given.
Options
None
Example
Set up the initialization string.
MBM> set init ate0v0&c1s0=3
MBM>
See Also
enable remote, show modem
3-70
Page 95
Commands
3.46 set membership
Set the membership for the MBM/PBM micros.
This command will allow the user to add, subtract, or auto detect the set of micros in the system
configuration. Use the set membership command to update the current set of micros found on
the private LAN.
MBM The micro MBM. This is required only if the add or subtract option is specified in
conjunction with the cabinet and drawer.
PBM The micro PBM. This is required only if the add or subtract option is specified in
conjunction with the cabinet and drawer.
Options
-add Add a micro to the membership. This option requires the cabinet, drawer,
and a micro argument (the micro does not have to be in the LAN for this
command to succeed).
-auto Auto detects the micros found in the private LAN.
-cabinet
<cabinet>
-drawer
<drawer>
-subtract Subtract a micro from the list of micros. This option requires the cabinet,
Cabinet number in hex. Cabinet number is required to identify the
component and defaults to 0 if it’s not specified.
Drawer number in hex. Drawer number is required to identify the
component and defaults to 0 if it’s not specified.
drawer, and a micro argument (the micro must be in the list of micros in
order for this command to succeed).
Examples
1. Example of the “-add” option
MBM> set membership -add -ca 0 -dr 2 PBM
~GRP-E-(grp_IAmAlive) MISSING NEIGHBOR timeout from Cab: 0, Drawer: 5
Cab Drw Module MicroID IP Address In Group
0 0 MBM 100000a 10.0.0.1 TRUE
0 1 MBM 100010a 10.1.0.1 TRUE
0 2 PBM 2fe0a 10.254.2.0 FALSE
0 5 PBM 5fe0a 10.254.5.0 TRUE
MBM> ~GRP-W-(grp_IAmAlive) Leaving Group ID: 100010a.a
~GRP-W-(grp_Create) Joined Group ID: 100000a.b
~GRP-W-(grp_Monitor) Leaving Group ID: 100000a.b
~GRP-W-(grp_Monitor) Joined Group ID: 100010a.c
[2003/04/17 15:51:27]
~REC-W-(trecTask) Server management group is transitioning.
~GRP-W-(grp_Monitor) Leaving Group ID: 100010a.c
~GRP-W-(grp_Monitor) Joined Group ID: 100010a.d
3-71
Page 96
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
interrupt: ~GRP-I-(interrupt), GROUP HAS FORMED ID:100010a.d
interrupt: ~GRP-I-(interrupt), GROUP IS STABLE ID:100010a.d
[2003/04/17 15:51:55]
~REC-W-(trecTask) Server management group is stable.
MBM>
2. Example of the “-sub” option
MBM> set member -sub -ca 0 -dr 2 pbm
~GRP-E-(grp_IAmAlive) MISSING NEIGHBOR timeout from Cab: 0, Drawer: 5
Cab Drw Module MicroID IP Address In Group
0 5 PBM 5fe0a 10.254.5.0 TRUE
0 1 MBM 100010a 10.1.0.1 TRUE
0 0 MBM 100000a 10.0.0.1 TRUE
MBM> ~GRP-W-(grp_IAmAlive) Leaving Group ID: 100010a.7
~GRP-W-(grp_Create) Joined Group ID: 100000a.8
~GRP-W-(grp_Monitor) Leaving Group ID: 100000a.8
~GRP-W-(grp_Monitor) Joined Group ID: 100010a.9
[2003/04/17 15:48:46]
~REC-W-(trecTask) Server management group is transitioning.
~GRP-W-(grp_Monitor) Leaving Group ID: 100010a.9
~GRP-W-(grp_Monitor) Joined Group ID: 100010a.a
interrupt: ~GRP-I-(interrupt), GROUP HAS FORMED ID:100010a.a
interrupt: ~GRP-I-(interrupt), GROUP IS STABLE ID:100010a.a
[2003/04/17 15:49:13]
~REC-W-(trecTask) Server management group is stable.
~GRP-W-(grp_Probe) MBM/PBM cab:00 drw:2 is not in the member list.
~GRP-W-(grp_Probe) Use Set Membership -add -ca 0 -dr 2 PBM
MBM>
3. Example of the “-auto” option (also the default if nothing is specified)
MBM> Set Membership -auto
~GRP-E-(grp_IAmAlive) MISSING NEIGHBOR timeout from Cab: 0, Drawer: 5
Cab Drw Module MicroID IP Address In Group
0 5 PBM 5fe0a 10.254.5.0 TRUE
0 2 PBM 2fe0a 10.254.2.0 TRUE
0 1 MBM 100010a 10.1.0.1 TRUE
0 0 MBM 100000a 10.0.0.1 TRUE
MBM> ~GRP-W-(grp_IAmAlive) Leaving Group ID: 100010a.d
~GRP-W-(grp_Create) Joined Group ID: 100000a.e
~GRP-W-(grp_Monitor) Leaving Group ID: 100000a.e
~GRP-W-(grp_Monitor) Joined Group ID: 100010a.f
[2003/04/17 15:54:40]
~REC-W-(trecTask) Server management group is transitioning.
~GRP-W-(grp_Monitor) Leaving Group ID: 100010a.f
~GRP-W-(grp_Monitor) Joined Group ID: 100010a.10
interrupt: ~GRP-I-(interrupt), GROUP HAS FORMED ID:100010a.10
interrupt: ~GRP-I-(interrupt), GROUP IS STABLE ID:100010a.10
[2003/04/17 15:55:08]
~REC-W-(trecTask) Server management group is stable.
MBM>
See Also
show membership
3-72
Page 97
Commands
3.47 set password
Sets the remote access password. The password has a maximum length of 15 characters. The
default password is mvfirmware. The password is nonvolatile and stored in the EEPROM of the
MBM or PBM.
Syntax
set password
<password>
Argument
password The password that must be entered by a remote session to gain
access to the system.
Options
None
Example
Change the remote access password.
MBM> set password mvfw
MBM>
See Also
show modem
3-73
Page 98
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.48 set sys_serial_num
Sets the system serial number. The serial number has a maximum length of 12 characters. This
command converts input to upper case and propagates the serial number to all EEPROMs except
RIMMs.
Syntax
set sys_serial_num
<serial_number>
Argument
serial_number The system serial number, limited to 12
characters.
Options
None
Example
Set the system serial number.
MBM> sh sys_serial
sys_serial_num is not set!
MBM> set sys_serial_num marvel_fw16P
Updating SYS_SERIAL_NUM in FRU EEPROMs....
MBM>
MBM> sh sys_serial
sys_serial_num MARVEL_FW16P
MBM>
See Also
show sys_serial_num
3-74
Page 99
Commands
3.49 set time
Sets the common base time. By default, this command sends the current base time to the primary
CPU’s MBM, which then sends out a time synchronizer message to all MBMs and PBMs to get
this new base time. This command enables the user to set up both date and time or just one of
them.
You can use show time to confirm your changes.
Warning: Changing the base time will affect the time on all existing partitions.
Syntax
set time
<date> | <time>
Arguments
date The format is yyyy/mm/dd.
time The format is hh:mm:ss.
Options
None
Examples
1. Change the date and time.
MBM> set time 2002/04/16 17:20:30
MBM> show time
Common base time: 2002/04/16 17:20:34
HP Name SP Name Delta Time (Days hh:mm:ss)
hp0 Default_SP +00 +00:+00:+00
hp1 Default_SP -01 -01:-01:-01
MBM>
2. Change the time only.
MBM> set time 14:45:00
MBM>
3. Change the date only.
MBM> set time 2003/08/16
MBM>
See Also
show time
3-75
Page 100
AlphaServer ES47/ES80/GS1280 Server Management CLI Reference
3.50 shell
Starts a vxworks shell.
Note: This command will be removed when the MBM/PBM firmware is not shipped with the
vxworks shell.
Syntax
shell
Arguments
None
Options
None
Example
Spawn a new shell task to go back to the shell prompt.
MBM> shell
10.0.0.1->
3-76
Loading...
+ 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.