HP Integrity Superdome 2 Command Line Interface Onboard Administrator User Guide
HP Integrity Superdome 2 Onboard Command Line Interface is a powerful tool for managing the Integrity Superdome 2 server. This guide will help you to get started with the HP Integrity Superdome 2 Onboard Command Line Interface and learn how to use its many features.
Advertisement
Advertisement
HP Integrity Superdome 2 Onboard
Administrator Command Line Interface User
Guide
Abstract
This document contains specific information that is intended for users of this HP product.
HP Part Number: AH337-9002H
Published: August 2013
Edition: 8
© Copyright 2011 – 2013 Hewlett-Packard Development Company, L.P.
Notices
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Microsoft®, Windows®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation. Java® is a registered trademark of Oracle and/or its affiliates. UNIX® is a registered trademark of the Open Group.
Revision History
HP Part Number
AH337-9002A
AH337-9002B
AH337-9002C
AH337-9002D
AH337-9002E
AH337-9002F
AH337-9002G
AH337-9002H
Edition
First
Second
Third
Fourth
Fifth
Sixth
Seventh
Eighth
Publication Date
August 2010
April 2011
August 2011
December 2011
May 2012
December 2012
May 2013
August 2013
Contents
5 User account commands...........................................................................22
6 Two-Factor Authentication commands..........................................................31
Contents 3
9 General management commands...............................................................44
10 Enclosure Bay IP Addressing commands....................................................51
4 Contents
11 Enclosure network configuration commands................................................55
12 Enclosure management commands............................................................71
Contents 5
13 Complex management commands............................................................92
14 Blade management commands.................................................................97
6 Contents
15 IOX enclosure management commands...................................................104
16 Interconnect management commands......................................................108
17 Enclosure DVD commands......................................................................119
18 Remote syslog commands......................................................................121
19 USB support commands.........................................................................123
Contents 7
22 Log viewer commands...........................................................................152
23 Health Repository commands.................................................................155
24 Core Analysis Engine commands............................................................164
25 Error Logging Services commands..........................................................168
26 Debug commands................................................................................169
27 Firmware update commands..................................................................170
8 Contents
Serviceguard Manager performance degradation and proxy errors...................................182
setboot and related commands are unable to display or modify boot variables...................182
29 Archive Storage commands....................................................................185
30 Legacy console commands....................................................................189
Contents 9
32 Support and other resources..................................................................194
Standard terms, abbreviations, and acronyms...............................................212
10 Contents
1 Accessing the CLI
Remotely accessing the Onboard Administrator
The Onboard Administrator CLI can be accessed remotely through any Telnet or Secure Shell session.
Telnet session
1.
From a network-connected client, open a command-line window
2.
At the prompt, open a Telnet session to the IP address of the Onboard Administrator, and then press Enter.
For example, telnet 192.168.100.130, where the IP address is the address of your
Onboard Administrator.
3.
Enter a valid user name, and then press Enter.
4.
Enter a valid password, and then press Enter. The CLI command prompt appears.
5.
Enter commands for the Onboard Administrator.
6.
To end the remote access Telnet session, enter Exit, Logout, or Quit at the CLI command prompt.
Secure Shell session
1.
Using any Secure Shell client application, start a Secure Shell session to the Onboard
Administrator.
2.
When prompted, enter the assigned IP address or DNS name of the Onboard Administrator, and then press Enter.
3.
Enter a valid user name, and then press Enter.
4.
Enter a valid password, and then press Enter. The CLI command prompt appears.
5.
Enter commands for the Onboard Administrator.
6.
To end the remote access Secure Shell session, close the communication software or enter
Exit
, Logout, or Quit at the CLI command prompt.
Locally accessing the Onboard Administrator
IMPORTANT: Only use the serial port during the initial setup of the OA network. Disconnect after setup and do not use the serial port as a console interface.
You can access the Onboard Administrator locally through a serial port connector on the rear of the Onboard Administrator module during the initial set up of the OA network. Use a laptop or desktop computer as a serial console to communicate with the Onboard Administrator. A laptop or desktop connected to the Onboard Administrator serial port requires a null-modem cable. The minimum connection to an external console is pins 2, 3, and 5.
Remotely accessing the Onboard Administrator 11
4
5
2
3
Pin
1
8
9
6
7
1.
Connect a serial cable between the serial port on the computer and the corresponding serial port on the Onboard Administrator module. The following table is for the DB9 serial (RS232) port and shows the pinout and signals for the RS232 connector. The signal direction is DTE
(computer) relative to the DCE (modem).
DSR
RTS
CTS
RI
Name
CD
RXD
TXD
DTR
GND
<<--
-->>
<<--
<<--
Signal direction
<<--
<<--
-->>
-->>
Description
Carrier detect
Receive data
Transmit data
Data terminal ready
System ground
Data set ready
Request to send
Clear to send
Ring indicator
2.
Use any standard communication software to launch a terminal emulation session with the following parameters:
Parameter
Transmission rate
Data bits
Parity
Stop bits
Protocol
Value
9600 bps
8
None
1
None
3.
When prompted, enter a valid user name, and then press Enter.
4.
Enter a valid password, and press Enter. The CLI command prompt appears.
5.
Enter commands for the Onboard Administrator.
6.
To end the terminal session, enter Exit at the prompt.
12 Accessing the CLI
2 Command line
Command line overview
You can also use the CLI to manage the Onboard Administrator. The following are some reasons to use the CLI:
•
HP Management Applications (for example, Systems Insight Manager, Insight Control tools, and so on) can query the Onboard Administrator for information that these tools must present for a complete management view of HP Integrity Superdome 2 enclosures and the devices contained within and connected IOX enclosures. This interface is also used by the Management tools to execute provisioning and configuration tasks to devices within the enclosure and connected IOX enclosures.
•
Users can develop tools that utilize Onboard Administrator functions for data collection and for executing provisioning and configuration tasks.
•
Users can also use the CLI when no browser is available or prefer to use a command line interface to access management data and perform configuration tasks.
HP Integrity Superdome 2 Server Blade and Integrity server blade restrictions
HP Integrity Superdome 2 Server Blades and Integrity server blades do not support all commands.
The following commands are not applicable to HP Integrity Superdome 2 Server Blades:
•
HPONCFG
•
POWERON SERVER
•
POWEROFF SERVER
•
SET SERVER BOOT
•
SET SERVER BOOT ONCE
•
SHOW SERVER BOOT
•
SHOW SERVER DVD
•
SHOW SYSLOG SERVER
•
UPDATE ILO
Access level and privileges
Onboard Administrator accounts and privileges
Onboard Administrator accounts are created with a user name, password, privilege level, and permissions to device bays, partition administration rights, and partitions on the Onboard
Administrator. You cannot delete or modify the privileges of the default Administrator account, on
Command line overview 13
the Onboard Administrator. You can only change the password for the Administrator account. The following table indicates the capabilities of the user based on their privileges and permitted bays.
Account classification
Administrator
OA Administrator administrator
OA Operator operator
OA user user
Capabilities Account name/privilege level
Bays selected for this account
•
All commands
•
Local account, not LDAP
•
Only account remaining after a reset
Onboard Administrator to factory defaults (account retains configured
Administrator password)
•
Administrator account password can be reset to factory default through the
Onboard Administrator serial port using the L lost password recovery option
•
Can download, add, and clear Secure
Shell key. This key works only with the
Administrator account.
Administrator/administrator All
OA bays (all bays automatically selected)
•
All commands
•
Enables access to all aspects of the HP
Integrity Superdome 2 complex and
Onboard Administrator including configuration, firmware updates, user management, and resetting default settings.
user name/administrator
•
Can perform all operations to permitted device bays and interconnect bays including virtual power and console access.
user name/administrator No OA bays and only selected device bays and interconnect bays
OA bays and can have other bays selected, but the capabilities for the other bays are defined in operator
•
Set rack name
•
EBIPA enable/disable permitted bays
•
Change OA network settings
•
Perform enclosure management commands user name/operator
•
Can perform all operations to permitted device bays and interconnect bays including virtual power and console access.
user name/operator
•
Can view status and information of selected OA, device and interconnect bays
•
Can view CLI history
•
Can set password for own account
•
Can set user contact information for own account
•
Can 'show' CLI commands user name/user
Selected device bays and interconnect bays
Selected OA bays and some device bays and interconnect bays
•
Can view status and information of selected bays
•
Can view CLI history
•
Can set password for own account
•
Can set user contact information for user name/user No OA bays and some device bays and interconnect bays
14 Command line
Account classification Capabilities Account name/privilege level
Bays selected for this account own account
•
Can 'show' CLI commands
Partition management capabilities
User access to commands for managing the partition configuration and the partitions themselves can be controlled through the Parcon_Admin access right and partition access assignments using the ASSIGN PARCON_ADMIN and ASSIGN PARTITION commands. Access to ALL (current and future) or individual partitions by partition ID may be assigned. The following table identifies the operations accounts may use on assigned partitions based on privilege level.
Account classification Partition capabilities
Administrator
Parcon Administrator
•
All commands available to Parcon
Administrator accounts
•
Manage the partition configuration
(create, modify, delete partitions)
•
All partition operations available to
Partition Administrator accounts
•
Access is always available to ALL partitions
Partition Administrator •
Restart the complex
•
Update partition firmware
•
All partition operations available to
Partition Operator accounts
Partition Operator
Partition User
•
Partition power and reset commands
•
Clear console logs
•
All partition operations available to
Partition User accounts
•
View partition and event logs
•
Connect to partition consoles
•
View partition status and info
Account name/privilege level
Parcon_Admin assigned
Administrator/administrator Yes user name/administrator user name/administrator user name/operator user name/user
Yes
No
No
No
Account authentication
Local users
•
This is the default setting. Local user accounts are directly authenticated against a password for each account stored on the active Onboard Administrator.
•
Account modifications are automatically synchronized between both Onboard Administrator modules if two are present.
•
Local users might be disabled if LDAP is enabled, leaving the Administrator account as the only local account that cannot be disabled.
Access level and privileges 15
LDAP users
•
The Enable/Disable LDAP is an optional setting. LDAP enabled can be used with local users enabled or disabled.
•
The Onboard Administrator uses configured LDAP server and search context to request account authentication.
•
Configuration of the LDAP group determines the privileges instead of the user name.
•
If a user is configured for multiple groups with different privileges and bay permissions, then the user has the highest privileges and the combination of all permitted bays.
16 Command line
3 General commands
CLEAR SCREEN
•
Command:
CLEAR SCREEN
NOTE:
CLS
is also a valid command.
•
Description:
Clears the terminal screen
•
Access level:
All
EXIT
•
Command:
EXIT
•
Description:
Exits the CLI
•
Access level:
All
HELP
•
Command:
HELP <command>
•
Description:
If you supply a command, the usage and help text for the command appears. If no argument is given, all base commands appear.
•
Access level:
All
•
Example:
OA-0018FE27577F> HELP
ADD ASSIGN BO CL CLEAR CLS CO CONNECT DISABLE DOWNLOAD ENABLE EXIT FORCE FPL
GENERATE HELP HISTORY HPONCFG INIT LOGOUT PARCREATE PARDEFAULT PARMODIFY PARPERM
PARREMOVE PARSTATUS PC PE PING POWEROFF POWERON QUIT REBOOT REMOVE RESTART RS
SEL SET SHOW SLEEP TC TEST TOC UNASSIGN UPDATE UPLOAD VPARBOOT VPARCREATE
VPARMODIFY VPARREMOVE VPARRESET VPARSTATUS
CLEAR SCREEN 17
LOGOUT
•
Command:
LOGOUT
•
Description:
Exits the command line interface
•
Access level:
All
QUIT
•
Command:
QUIT
•
Description:
Exits the command line interface
•
Access level:
All
18 General commands
4 Rack commands
SET RACK NAME
•
Command:
SET RACK NAME <rack name>
•
Description:
Sets the rack name
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <rack name> must be a maximum of 32 characters long and includes all alphanumeric, the dash, and the underscore characters.
UnnamedRack is the default rack name.
SHOW RACK NAME
•
Command:
SHOW RACK NAME
•
Description:
Displays the user-defined rack name setting for the enclosure
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW RACK NAME
Rack Name: UnnamedRack
SHOW TOPOLOGY
•
Command:
SHOW TOPOLOGY
•
Description:
◦
Displays the complexes connected by the complex link
◦
Displays the enclosures connected by the enclosure link in each complex
◦
Displays a table with the enclosure name, overall health of the enclosure, and the IP address by complex
•
Access level/Bay level
OA Administrator, OA Operator, OA user
SET RACK NAME 19
•
Restrictions:
You must be logged on to the monarch OA to perform this command.
•
Example:
The output for this command will depend on how the enclosures are linked.
SHOW TOPOLOGY
Detecting linked enclosures ..
Complex Topology
Complex UUID: 09USE7332000
Complex Name: ComplexOne
Rack Name: MyRack
Enc# Enclosure Name Status Local IP Address UUID
---- --------------- ------- ------- -------------- ----------------
1 Enclosure11 OK Yes 15.255.99.100 09O977MU2000
Other linked enclosures which are not part of this complex
Foreign Complex UUID: 09USE7334000
Enc# Enclosure Name Status Local IP Address UUID
---- --------------- ------- ------- -------------- ----------------
1 Enclosure21 OK No 15. 255.99.110 54O999MU2001
CONNECT ENCLOSURE
•
Command:
CONNECT ENCLOSURE [ ACTIVE | STANDBY ] { <enclosure number> } [ RUN
<command...> ]
•
Description:
Creates an SSH connection to the designated OA in a remote enclosure over the internal management network. This command is valid from any Active OA.
This command the accepts the following arguments: an optional OA role, active (the default) or standby, the target enclosure ID and an optional remote command.
•
Access level/Bay level:
Any active OA
•
Restrictions:
None
•
Example: oa_host_name> connect enclosure 2 run show blade list
Connecting to OA 1 in enclosure 2 …
HP Superdome Onboard Administrator
… oa2_host_name> show blade list
Bay iLO Name iLO IP Address Status Power UID Partner
--- ---------------- --------------- ------ ------- ----------
1 iLO-002264fd6b66 16.119.111.8 OK Off Off
2 iLO-00237dd51582 16.119.110.98 OK Off Off
3 iLO-002481bc8114 16.119.111.61 OK Off Off
20 Rack commands
UPLOAD DEBUG
•
Command:
UPLOAD DEBUG { <URL> | ARCHIVE <"directory"> | USB <"directory"> }
•
Description:
This command collects relevant system logs and files from the Complex and uploads them to a URL, a USB connected to the enclosure, or Archive Storage.
•
Access level/Bay level:
Monarch OA
•
Restrictions:
◦
If your FTP server does not support anonymous logins, you can specify a username and password within the url formatted as: ftp://username:password@host/path/filename.
◦
The USB directory is the directory in the USB key where the logs will be placed.
◦
To upload to Archive Storage, use the URI shown by the SHOW ARCHIVE command.
•
Example: oa_host_name> upload debug ftp://festival:[email protected]/
This command can take a while (up to 30 minutes)
Entering anything other than 'YES' will result in the command not executing.
Are you sure you want to collect all logs of the Complex? yes
Collecting logs, please wait...
Logs collected!
Uploading file enclosure_1-lighthouse.tar.gz to ftp://festival:[email protected]/ ...
The upload to the specified URL failed.
Uploading file enclosure_2-lighthouse.tar.gz to ftp://festival:[email protected]/ ...
File uploaded with success.
UPLOAD SYSLOG
•
Command:
UPLOAD SYSLOG {“<URL>”}
•
Description:
This command uploads the OA syslog history to a <URL> or USB connected to the enclosure.
•
Access level/Bay level:
Monarch OA
•
Restrictions:
◦
If your FTP server does not support anonymous logins, you can specify a username and password within the url formatted as: ftp://username:password@host/path/filename.
◦ upload syslog tftp://192.168.0.1/log1 will upload the syslog history to filename log1 on the specified server.
◦
To upload using FTP use upload syslog
ftp://username:[email protected]/home/username/log1
<ftp://192.168.0.1/home/username/log1>
.
◦
To upload to the enclosure connected USB drive use upload syslog usb://d1/log1.
UPLOAD DEBUG 21
5 User account commands
ADD USER
•
Command:
ADD USER "<user name>" ["<password>"]
•
Description:
Adds a user to the system. If you do not provide a password, you are prompted for one. If
SCRIPT MODE is enabled and the password is not provided, the password is assigned an unmatched string. This unmatched string requires an enclosure administrator to change the password to enable the new user to access the system.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
User accounts are managed from the Monarch OA.
◦
You can add a maximum of 26 users, including the reserved accounts.
◦
The <user name> is case-sensitive and must be unique to all other user names and group names. The <user name> must be 1 to 40 characters long and can include all alphanumeric characters, the dash, and the underscore.
◦
The <user name> must begin with a letter.
◦
The <password> must be 3 to 40 characters long. The character set includes all printable characters. If you do not enter a password, you are prompted to enter one.
◦
Reserved user names are: ALL (case-insensitive), ADMINISTRATOR (case-insensitive), switch1, switch2, switch3, switch4, switch5, switch6, switch7, switch8, ldapuser, nobody, and vcmuser.
ASSIGN
•
Command:
ASSIGN {BLADE | INTERCONNECT} {<bay number> | ALL | <bay number>-<bay number>}
{"<user name>" | LDAP GROUP "<LDAP group name>"}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Assigns one or more bays to a user or group
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The <user name> is case-sensitive. If a bay is presently assigned to a user, you must unassign the bay first.
22 User account commands
ASSIGN OA
•
Command:
ASSIGN OA {"<user name>" | LDAP GROUP "<LDAP group name>"}
•
Description:
Assigns the Onboard Administrators specified to an existing user or group
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The <user name> is case-sensitive.
DISABLE USER
•
Command:
DISABLE USER "<user name>"
•
Description:
Disables a user account. The system immediately logs out the user and prevents the user from logging in until the account is enabled. CLI sessions are terminated and all future SOAP web accesses fail.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
The <user name> is case-sensitive.
◦
You cannot disable the built-in Administrator account
DISABLE STRONG PASSWORDS
•
Command:
DISABLE STRONG PASSWORDS
•
Description:
Removes strong password requirements for user passwords
•
Access level/Bay level:
OA Administrator
•
Restrictions:
Only Administrators with Onboard Administrator permission are permitted to manage strong passwords.
ASSIGN OA 23
ENABLE STRONG PASSWORDS
•
Command:
ENABLE STRONG PASSWORDS
•
Description:
When enabled, this command requires that a user's password contain at least one character from three of the four categories:
◦
Uppercase
◦
Lowercase
◦
Numeric
◦
Nonalphanumeric
•
Access level/Bay level:
OA Administrator
•
Restrictions:
Only Administrators with Onboard Administrator permission are permitted to manage strong passwords.
ENABLE USER
•
Command:
ENABLE USER "<user name>"
•
Description:
Enables a user account that was previously disabled by the DISABLE USER command
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The <user name> is case-sensitive.
HISTORY
•
Command:
HISTORY
•
Description:
Shows the history of commands for the current session
•
Access level/Bay level:
All
•
Restrictions:
None
24 User account commands
REMOVE USER
•
Command:
REMOVE USER {ALL | "<user name>" | CERTIFICATE "<user name>"}
•
Description:
Removes a user from the system or any certificate mapped to the user or both. If you specify
ALL
, then the command is run for all users except the default system accounts.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
The <user name> is case-sensitive.
◦
You cannot remove the Administrator account.
SET MINIMUM PASSWORD LENGTH
•
Command:
SET MINIMUM PASSWORD LENGTH <length>
•
Description:
Sets a minimum length for passwords. When set, a user's password must contain at least the number of characters specified.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The minimum password length can be set between 3 and 40 characters.
SET PASSWORD
•
Command:
SET PASSWORD ["<password>"]
•
Description:
Sets the password of the user that executed the command. If you do not provide a password on the command line, you are prompted for one.
•
Access level/Bay level:
All
•
Restrictions:
◦
The <password> must be 3 to 40 characters long. The character set includes all printable characters.
◦
You must specify the password when in SCRIPT MODE.
REMOVE USER 25
SET SESSION TIMEOUT
IMPORTANT: On Superdome 2 systems, the following long-running commands are not immediately subject to the session timeout defined by the SET SESSION TIMEOUT command:
•
SHOW {HR | FPL | LIVELOGS | SEL | SYSLOG | PARTITION CONSOLELOG}
•
CONNECT {BLADE | INTERCONNECT | PARTITION }
•
CO
•
FPL
•
SEL
If a user has one of these commands active, their session will not be removed when a session timeout occurs; instead it will be removed once they exit the long-running command and interact with the CLI. Furthermore, the SHOW USER SESSIONS command will not display the active session after a session timeout occurs.
•
Command:
SET SESSION TIMEOUT <timeout>
•
Description:
Sets the number of minutes before inactive sessions are removed. The default setting is 1440.
The session timeout can be disabled by setting the timeout value to zero.
NOTE: If the session timeout value is lowered, currently inactive sessions may be removed.
•
Access level/ Bay level:
OA Administrator
•
Restriction:
Valid session timeout values range from 10 to 1440 minutes (24 hours).
SET USER ACCESS
•
Command:
SET USER ACCESS "<user name>" {ADMINISTRATOR | OPERATOR | USER}
•
Description:
Sets the user access level. Additionally, use the ASSIGN command to give the user access rights to the Onboard Administrator, server bays, and interconnect bays.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
SET USER CONTACT
•
Command:
SET USER CONTACT ["<user name>"] "<contact info>"
•
Description:
Sets the contact information field for the user. If there is no <user name>, the command modifies the contact information of the user who executed the command.
26 User account commands
•
Access level/Bay level:
◦
All users can modify their own contact information.
◦
The OA Administrator can modify all users.
•
Restrictions:
◦
The <user name> is case-sensitive. The <contact info> must be a maximum of 20 characters long and includes all alphanumeric characters, the dash, the underscore, and spaces.
◦
The default contact information is blank.
◦
You must use double quotes if the contact information contains any spaces.
SET USER FULLNAME
•
Command:
SET USER FULLNAME ["<user name>"] "<full name>"
•
Description:
Sets the full name of a user. If you do not specify a <user name>, the command modifies the full name of the user who is currently logged in.
•
Access level/Bay level:
◦
OA Administrator, OA Operator
◦
All users can modify their own full name.
•
Restrictions:
◦
The <user name> is case-sensitive. The <full name> must be a maximum of 20 characters long and includes all alphanumeric, the dash, the underscore, and the space characters.
◦
The default full name is blank.
SET USER PASSWORD
•
Command:
SET USER PASSWORD "<user name>" ["<new password>"]
•
Description:
Sets a user's password. If you do not supply a password on the command line, you are prompted for one.
•
Access level/Bay level
◦
OA Administrator
◦
OA Operator and User access level users can change their own passwords.
•
Restrictions:
◦
Only OA Administrators can modify another user's password. Only the Administrator account can modify the password of the Administrator account.
◦
The <user name> is case-sensitive.
◦
The <new password> must be 3 to 40 characters long.
SET USER FULLNAME 27
◦
The character set includes all printable characters.
◦
You must specify the password when in SCRIPT MODE.
SHOW PASSWORD SETTINGS
•
Command:
SHOW PASSWORD SETTINGS
•
Description:
Displays the current minimum password length and strong password settings
•
Access level/Bay level:
All users
•
Restrictions:
None
•
Example:
OA-0018FE27577F>SHOW PASSWORD SETTINGS
Strong Passwords: Disabled
Minimum Password Length: 3
SHOW SESSION TIMEOUT
•
Command:
SHOW SESSION TIMEOUT
•
Description:
Displays the current Onboard Administrator user session timeout. The session timeout is the number of minutes before inactive sessions are removed.
•
Access level/Bay level:
All
•
Restriction:
None
•
Example:
OA-0018FE27577F> SHOW SESSION TIMEOUT
Session Timeout: 1440 minutes
SHOW USER
•
Command:
SHOW USER [LIST | "<user name>"]
•
Description:
Displays the full name of the user, contact information, whether the user has administrator rights, whether the account is enabled, the access level, whether the user has access to the
Onboard Administrator, and the bays the user can access.
If you enter LIST and you are an OA Administrator, the information for every user is listed.
An asterisk before a user name denotes the current user.
28 User account commands
•
Access level/Bay level:
All
•
Restrictions:
The <user name> is case-sensitive. Users who do not have OA Administrator or OA Operator access levels can view only their user information.
•
Example:
OA-0018FE27577F> SHOW USER
Local User "Administrator" Information:
Full name: System Administrator
Contact Info:
User Rights: Admin
Account Status: Enabled
Server Bay Access List: 1 1A 1B 2 2A 2B 3 3A 3B 4 4A 4B 5 5A 5B 6 6A 6B
7 7A 7B 8 8A 8B
Interconnect Bay Access List: 1 2 3 4
OA Access: Yes
SLEEP
•
Command:
SLEEP <seconds>
•
Description:
Pauses the sessions for a fixed period of time. This command is useful for adding delays to scripts.
After the pause begins, you cannot continue the session before time runs out. However, you can end the session and start another session.
•
Access level/Bay level:
All
•
Restrictions:
The <seconds> argument must be a whole number from 1 to 86400.
UNASSIGN
•
Command:
UNASSIGN {BLADE | INTERCONNECT} {<bay number> | ALL | <bay number>-<bay number>}
{"<user name>" | LDAP GROUP "<LDAP group name>"}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Removes a bay from the user
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The <user name> is case-sensitive.
SLEEP 29
UNASSIGN OA
•
Command:
UNASSIGN OA {"<user name>" | LDAP GROUP "<LDAP group name>"}
•
Description:
Removes the Onboard Administrator from the control of the user that it is currently assigned
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The <user name> is case-sensitive.
30 User account commands
6 Two-Factor Authentication commands
DISABLE CRL
•
Command:
DISABLE CRL
•
Description:
Disables certificate revocation checks
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
DISABLE TWOFACTOR
•
Command:
DISABLE TWOFACTOR
•
Description:
Disables Two-Factor Authentication
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
DOWNLOAD CA CERTIFICATE
•
Command:
DOWNLOAD CA CERTIFICATE "<url>"
•
Description:
Downloads a CA certificate to act as the trusted certification authority to validate user certificates when using Two-Factor Authentication.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
Enables the download of up to five different certificates
DISABLE CRL 31
DOWNLOAD USER CERTIFICATE
•
Command:
DOWNLOAD USER CERTIFICATE "<user name>" <url>
•
Description:
◦
Downloads an x.509 certificate for the user from <url>. The file at <url> must be a
Base64 PEM encoded file.
◦
Downloads a CA certificate used in Two-Factor Authentication.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
REMOVE CA CERTIFICATE
•
Command:
REMOVE CA CERTIFICATE "<certificate name>"
•
Description:
Removes the trust certificate corresponding to the SHA1 <certificate name>. Any users having their certificates issued by this CA can no longer login if Two-Factor Authentication is enabled.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
REMOVE USER CERTIFICATE
•
Command:
REMOVE USER CERTIFICATE "<user name>"
•
Description:
Removes the user certificate. If Two-Factor Authentication is enabled, this user no longer has access through HTTPS.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
SHOW CA CERTIFICATE
•
Command:
SHOW CA CERTIFICATE
•
Description:
Displays a list of installed CA certificates
32 Two-Factor Authentication commands
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0016355E560A> SHOW CA CERTIFICATE
Details for ca certificate 1 certificateVersion = 3 issuerOrganization = ca.com
issuerOrganizationalUnit = IT Infrastructure issuerCommonName = Hewlett-Packard Primary Class 2 Certification Authority subjectOrganization = hp.com
subjectOrganizationalUnit = IT Infrastructure subjectCommonName = Hewlett-Packard Primary Class 2 Certification Authority validFrom = 1997-12-30T00:00:00Z validTo = 2012-12-29T23:59:59Z serialNumber =83:B7:1B:E9:27:AB:5C:61:F8:8F:90:30:E:0D:17:DE:C6 extensionCount = 7 md5Fingerprint = B6:22:5B:B8:43:CD:1A:66:64:19:33:B:3:C1:80:BF:B6 sha1Fingerprint = CF:5C:89:7B:84:7B:73:C4:C5:3E:3F:E:7:93:09:53:EB:C4:28:BE:CF
SHOW TWOFACTOR INFO
•
Command:
SHOW TWOFACTOR INFO
•
Description:
Displays the configuration details for Two-Factor Authentication
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW TWOFACTOR INFO
Two Factor Authentication:
Enabled : Disabled
Certificate Revocation : Disabled
Certificate Owner Field : Subject
SHOW TWOFACTOR INFO 33
7 Directory commands
ADD LDAP CERTIFICATE
•
Command:
ADD LDAP CERTIFICATE <end marker> <certificate> <end marker>
•
Description:
Adds an LDAP certificate on the command line. To add the certificate:
1.
Start with a string that does not appear within the certificate (the end marker).
2.
Paste the certificate.
3.
Terminate the command with the end marker.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The certificate text cannot exceed 3071 characters.
ADD LDAP GROUP
•
Command:
ADD LDAP GROUP "<group name>"
•
Description:
Adds an LDAP group to the group. This group must match a group in the directory server.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
The maximum number of LDAP groups is 30.
◦
Group name must be 1 to 255 characters in length.
◦
Character set includes all printable characters, except quotation marks and new lines.
◦
The group name must start with an alpha character.
ASSIGN for LDAP
•
Command:
ASSIGN {BLADE | INTERCONNECT} {<bay number> | ALL | <bay number>-<bay number>}
{"<user name>" | LDAP GROUP "<LDAP group name>"}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Assigns the bay to a specified LDAP group, providing access to the bay at the access level of the group
34 Directory commands
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
ASSIGN OA LDAP GROUP
•
Command:
ASSIGN OA {"<user name>" | LDAP GROUP "<LDAP group name>"}
•
Description:
Assigns the specified group access to the Onboard Administrator.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
DISABLE LDAP
NOTE: If LDAP is enabled, local accounts are disabled, and the LDAP server becomes unavailable, you can recover by booting into Lost Password mode.
When booting in Lost Password mode, the local Administrator password is reset, LDAP is disabled, and Local Logins are re-enabled.
•
Command:
DISABLE LDAP
•
Description:
•
Disables directory authentication
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
DOWNLOAD LDAP CERTIFICATE
•
Command:
DOWNLOAD LDAP CERTIFICATE "<url>"
•
Description:
Downloads an LDAP certificate to establish a trusted relationship with the LDAP server. Specify the <url> where the certificate is located.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
ASSIGN OA LDAP GROUP 35
ENABLE LDAP
NOTE: If LDAP is enabled, local accounts are disabled, and the LDAP server becomes unavailable, you can recover by booting into Lost Password mode.
When booting in Lost Password mode, the local Administrator password will be reset, LDAP is disabled, and Local Logins are re-enabled.
•
Command:
ENABLE LDAP [NOLOCAL]
•
Description:
Enables directory authentication. If you use the NOLOCAL option, local users are not enabled.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
To enable LDAP, you must first complete the configuration.
REMOVE LDAP CERTIFICATE
•
Command:
REMOVE LDAP CERTIFICATE "<certificate name>"
•
Description:
◦
Removes the trust certificate corresponding to the MD5 <certificate name>.
◦
This command revokes trust in the LDAP server associated with the certificate.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
REMOVE LDAP GROUP
•
Command:
REMOVE LDAP GROUP {ALL | "<group name>"}
•
Description:
Removes the LDAP group from the system. If you specify ALL, then all LDAP groups are removed from the system.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
To enable LDAP, you must first complete the configuration.
36 Directory commands
SET LDAP GROUP ACCESS
•
Command
SET LDAP GROUP ACCESS "<group name>" {ADMINISTRATOR | OPERATOR | USER}
•
Description:
◦
Sets the LDAP group access level.
◦
Additionally, use the ASSIGN OA command to give a user or group rights to the Onboard
Administrator.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
SET LDAP GROUP DESCRIPTION
•
Command:
SET LDAP GROUP DESCRIPTION "<group name>" "<description>"
•
Description:
Sets the LDAP group description field
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
Must be 0 to 58 characters in length.
◦
Valid characters are all alphanumeric, the underscore (_), the dash (-), and spaces.
◦
If the group name or description field contains spaces or zero characters, use double quotes.
SET LDAP NAME MAP
•
Command:
SET LDAP NAME MAP {ON|OFF}
•
Description:
Turns on NT name mapping to enable the user to enter their NT domain\user name
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
SET LDAP GROUP ACCESS 37
SET LDAP PORT
•
Command:
SET LDAP PORT <port number>
•
Description:
Sets the TCP port number of the LDAP SSL service. Port 636 is the standard value.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The valid port number range is 1 to 65535.
SET LDAP SEARCH
•
Command:
SET LDAP SEARCH {1|2|3} "<search content>"
•
Description:
Sets up to three search contexts in priority order
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
SET LDAP SERVER
•
Command:
SET LDAP SERVER {<ip address> | <dns name>}
•
Description:
Sets the <ip address> or the <dns name> of the directory server
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The <ip address> is in the form ###.###.###.###, where each ### is in the range 0 to
255.
SHOW LDAP CERTIFICATE
•
Command:
SHOW LDAP CERTIFICATE
•
Description:
Displays all LDAP certificates that are in effect on the Onboard Administrator
•
Access level/Bay level:
All
38 Directory commands
•
Restrictions:
None
•
Example:
OA-0016355E560A> SHOW LDAP CERTIFICATE
1 Certificate name: 17D6A5ECBF51A1A47D44C1CDD29D19EE.pem
-----BEGIN CERTIFICATE-----
MIIHIzCCBgugAwIBAgIKFTKZbQAAAFx1EDANBgkqhkiG9w0BAQUFADB4MRMwEQYK
CZImiZPyLGQBGRYDbmV0MRcwFQYKCZImiZPyLGQBGRYHY3BxY29ycDEbMBkGCgmS
JomT8ixkARkWC2FzaWFwYWNpZmljMSswKQYDVQQDEyJIUFEgSXNzdWluZyBDQSBB c2lhLVBhY2lmaWMgUmVnaW9uMB4XDTA3MTAyMDIyMzU0M1oXDTA5MTAxOTIyMzU0
M1owKTEnMCUGA1UEAxMeY2NlZ2NhbTAxLmFtZXJpY2FzLmhwcWNvcnAubmV0MIGf
MA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDNYsB8T6rJhJQXbKvM5JLi6EXNAtFL ayV11QVyrtjRtOjRGySwFCk9KNzRS7PIP/p9gH20Ic+ZvgX0fRPnnU/2imMeTGr2 raIYGRSFBJ4sCpAP87m/7Hzk0kiyZ+7KJq92Q61Pipkea...................
-----END CERTIFICATE-----
SHOW LDAP GROUP
•
Command:
SHOW LDAP GROUP {LIST | "<group name>"}
•
Description:
This command displays the LDAP group information. If you specify LIST, then a list of all the
LDAP groups appears.
•
Access level/Bay level:
OA Administrator, operator
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW LDAP GROUP LIST
Privilege LDAP Group /
Level Description
----------- ----------------
Operator [email protected]
Widget operators
SHOW LDAP INFO
•
Command:
SHOW LDAP INFO
•
Description:
Displays the LDAP settings, including enabled or disabled status, LDAP server, LDAP port, search contexts, and NT mapping state
•
Access level/Bay level:
All
SHOW LDAP GROUP 39
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW LDAP INFO
Directory Services (LDAP)
Enabled : Disabled
Local Users Enabled : Enabled
NT Name Mapping : Disabled
Directory Server :
Directory Server SSL Port : 0
Search Context #1 :
Search Context #2 :
Search Context #3 :
TEST LDAP
•
Command:
TEST LDAP ["<user name>"] ["<password>"]
•
Description:
Run LDAP tests and optionally attempt to login to the LDAP server using the user name and password. If no user name and password is specified, only basic Directory Server connection tests are performed.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
UNASSIGN for LDAP
•
Command:
UNASSIGN {BLADE | INTERCONNECT} {<bay number> | ALL | <bay number>-<bay number>}
{"<user name>" | LDAP GROUP "<LDAP group name>"}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Disables access to the bays for the group specified
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
40 Directory commands
UNASSIGN OA LDAP GROUP
•
Command:
UNASSIGN OA {"<user name>" | LDAP GROUP "<LDAP group name>"}
•
Description:
Disables access to the Onboard Administrator for the group specified
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
UNASSIGN OA LDAP GROUP 41
8 HP SIM commands
ADD HPSIM CERTIFICATE
•
Command:
ADD HPSIM CERTIFICATE <end marker> <certificate> <end marker>
•
Description:
Adds an HP SIM certificate on the command line:
1.
Start with a string that does not appear within the certificate (the end marker).
2.
Paste the certificate.
3.
Terminate the command with the end marker.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
This command is only available in SCRIPT MODE.
◦
The certificate text cannot exceed 3071 characters.
DOWNLOAD HPSIM CERTIFICATE
•
Command:
DOWNLOAD HPSIM CERTIFICATE {<IP address> | "<DNS Name>}
•
Description:
Downloads an HP SIM SSO certificate from the specified IP address
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The <IP address> must be in the form ###.###.###.###, where each ### ranges from
0 to 255.
REMOVE HPSIM CERTIFICATE
•
Command:
REMOVE HPSIM CERTIFICATE "<certificate name>"
•
Description:
Removes the trust certificate corresponding to the <certificate name>. Disables HP SIM
SSO through the application (for example HP SIM) that provided the certificate without disabling other HP SIM applications.
The <certificate name> can be obtained by using the SHOW HPSIM INFO command.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
42 HP SIM commands
SET HPSIM TRUST MODE
•
Command:
SET HPSIM TRUST MODE {CERTIFICATE [ON] | DISABLED [OFF]}
•
Description:
Enables or disables the HP SIM SSO mode. When enabled, the trusted applications can access the Onboard Administrator GUI data without requiring additional authentication.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
The CERTIFICATE (On) mode trusts only applications with certificates that have been uploaded to the Onboard Administrator.
SHOW HPSIM INFO
•
Command:
SHOW HPSIM INFO
•
Description:
Displays the current HP SIM SSO configuration for the Onboard Administrator.
The data includes the current HP SIM SSO Trust Mode. (See
.) and a list of names that the Onboard Administrator is configured to trust, using a trust certificate.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW HPSIM INFO
HPSIM Trust Mode: Disabled
Trusted Server Certificates
No certificates were found.
SET HPSIM TRUST MODE 43
9 General management commands
DOWNLOAD OA CERTIFICATE
•
Command:
DOWNLOAD OA CERTIFICATE [<bay number>] <url>
•
Description:
◦
Downloads a CA supplied pkcs#7 file to replace the current security certificate on Onboard
Administrator specified by <bay number>. If you omit <bay number>, then the current
Onboard Administrator is targeted.
◦
Supported protocols are HTTP, FTP, and TFTP.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
You must format the <url> as protocol://host/path/file. If your FTP server does not support anonymous connections, then you can specify a user name and password by replacing host in the previous format with username:password@host.
FORCE TAKEOVER
•
Command:
FORCE TAKEOVER
•
Description:
Forces the redundant Onboard Administrator to become the active Onboard Administrator.
The active becomes the standby and the standby becomes the active.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
GENERATE CERTIFICATE
•
Command:
GENERATE CERTIFICATE [REQUEST | SELFSIGNED]
•
Description:
Generates a pkcs#10 certificate request or a self-signed certificate. For information on the fields you will be directed to populate, see
“Generate certificate prompts” (page 45) .
•
Access level/Bay level:
OA Administrator
•
Restrictions:
This command is not valid in SCRIPT MODE.
44 General management commands
Generate certificate prompts
Prompt Description Restrictions
OA Host Name (CN) This is the most important field. This is the
Onboard Administrator name that appears in the browser web address box. This certificate attribute is generally referred to as the common name.
Must be 1 to 60 characters long. To prevent security alerts, the value of this field must match the host name exactly as it is known by the web browser. The browser compares the host name in the resolved web address to the name that appears in the certificate. For example, if the web address in the address field is https://oa-001635.xyz.com, then the value must be oa-001635.xyz.com
Organization Name
(O)
The company or organization that owns this
Onboard Administrator. When this information is used to generate a certificate signing request, the issuing certificate authority can verify that the organization requesting the certificate is legally entitled to claim ownership of the given company name or organization name.
Must be 1 to 60 characters long
City or Locality (L)
State or Province (ST) The state or province where the Onboard
Administrator is located.
Country (C)
The city or locality where the Onboard
Administrator is located.
The two-character country code that identifies the country where the Onboard Administrator is located.
Must be 1 to 50 characters long
Must be 1 to 30 characters long
Must be a two-character country code
Organizational Unit
Contact Person
The unit within the company or organization that owns the Onboard Administrator.
The person responsible for the Onboard
Administrator.
(Optional) Must be 0 to 60 characters long
(Optional) Must be 0 to 60 characters in length
Email Address
Surname
Given Name
Initials
The email address of the contact person responsible for the Onboard Administrator.
(Optional) Must be 0 to 60 characters long
The surname of the person responsible for the
Onboard Administrator.
(Optional) Must be 0 to 60 characters long
(Optional) Must be 0 to 60 characters long The given name of the person responsible for the Onboard Administrator.
The initials of the person responsible for the
Onboard Administrator.
(Optional) Must be 0 to 20 characters long
DN Qualifier
Challenge Password
The distinguished name qualifier of the
Onboard Administrator.
(Optional) Must be 0 to 60 characters long
The password to the certificate-signing request.
(Optional) Must be 0 to 20 characters long
Unstructured Name This is for additional information, for example, an unstructured name that is assigned to the
Onboard Administrator.
(Optional) Must be 0 to 60 characters long
PING
•
Command:
PING [<number>] {ip address> | "<server name>"}
•
Description:
Sends ICMP echo messages to a remote IP device. If you omit <number>, then only four packets are sent. Packets are sent at one-second intervals to prevent strain on the network.
PING 45
•
Access level/Bay level:
All
•
Restrictions:
The <ip address> must be in the form ###.###.###.###, where each ### ranges from
0 to 255.
SET DEVICE SERIAL_NUMBER BLADE
•
Command:
SET DEVICE SERIAL_NUMBER BLADE <bay number> "<serial number>"
•
Description:
Sets the serial number of the specified Storage, Tape, or I/O expansion blade.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
Length must be 10 characters. All printable characters are permitted.
◦
This operation cannot be performed on server blades.
SET FACTORY
•
Command:
SET FACTORY
•
Description:
◦
Restores the Onboard Administrator to its factory defaults. The Administrator account password does not change.
◦
The Onboard Administrator restarts after all changes are made.
◦
All existing settings will be lost when this operation is run.
◦
Settings synchronization will always copy settings from the Monarch OA to other Active
OAs in a multi-enclosure complex.
◦
If SET FACTORY is run on a non-Monarch Active OA only the settings which are not maintained by the Monarch OA will remain at factory default.
◦
If SET FACTORY is run on the Monarch OA the Monarch OA factory settings that are managed by enclosure synchronization (including Administrative account settings) will be copied to all OAs. The Administrator account password for all OAs in the complex will be the default password identified on the Monarch OA toe tag.
◦
If the SET FACTORY command is run on each Active OA, including the Monarch OA, in any order will result in the same final configuration with all settings at defaults and matching the Monarch OA.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
46 General management commands
SET SCRIPT MODE
•
Command:
SET SCRIPT [MODE] {ON | OFF}
•
Description:
◦
Ceases all prompting and verifying of entries when SCRIPT MODE is on.
◦
The ADD USER command must have a password argument if executed in SCRIPT MODE.
◦
Default values are used for any parameters that would normally require user interaction.
•
Access level/Bay level:
All
•
Restrictions:
None
SHOW ALL
•
Command:
SHOW ALL
•
Description:
Executes all SHOW commands in succession. The SHOW commands that appear are:
SHOW CONFIG
SHOW DATE
SHOW DISPLAY EVENT
SHOW EBIPA
SHOW ENCLOSURE FAN ALL
SHOW ENCLOSURE INFO
SHOW ENCLOSURE LCD
SHOW ENCLOSURE POWERSUPPLY ALL
SHOW ENCLOSURE POWER_SUMMARY
SHOW ENCLOSURE STATUS
SHOW ENCLOSURE TEMP
SHOW ENCRYPTION
SHOW OA INFO
SHOW OA NETWORK
SHOW OA STATUS ALL
SHOW OA UPTIME ALL
SHOW OA CERTIFICATE
SHOW SYSLOG OA
SHOW NETWORK
SHOW POWER
SHOW RACK NAME
SHOW SNMP
SHOW SSHFINGERPRINT
SHOW SSHKEY
SHOW HPSIM INFO
SHOW INTERCONNECT INFO ALL
SHOW INTERCONNECT LIST
SHOW INTERCONNECT SESSION
SHOW INTERCONNECT STATUS ALL
SHOW INTERCONNECT PORT MAP ALL
SHOW INTERCONNECT POWERDELAY ALL
SHOW SERVER LIST
SHOW SERVER NAMES
SHOW FRU
SHOW SERVER INFO ALL
SHOW SERVER PORT MAP ALL
SET SCRIPT MODE 47
SHOW SERVER STATUS ALL
SHOW SERVER TEMP ALL
SHOW PARTITION DVD
SHOW SERVER POWERDELAY ALL
SHOW SERVER BOOT ALL
SHOW SYSLOG SERVER ALL
SHOW SYSLOG ILO ALL
SHOW TOPOLOGY
SHOW USBKEY
SHOW USER(current user)
SHOW USER SESSIONS
SHOW USER LIST
SHOW LDAP INFO
SHOW LDAP CERTIFICATE
SHOW LDAP GROUP LIST
SHOW CA CERTIFICATE
SHOW TWOFACTOR INFO
SHOW PASSWORD SETTINGS
SHOW UPDATE
SHOW SYSLOG SETTINGS
SHOW VCMODE
SHOW SESSION TIMEOUT
SHOW VLAN
SHOW URB
SHOW DEVICE SERIAL_NUMBER BLADE ALL
SHOW SOLUTIONSID
SHOW UPDATE
SHOW DVD INFO
SHOW DVD STATUS
SHOW GPSM INFO ALL
SHOW GPSM STATUS
SHOW XFM STATUS ALL
SHOW XFM INFO ALL
SHOW XFM LIST
If you are connected to the monarch OA when you run the SHOW ALL command, these commands also appear:
SHOW IOX INFO ALL
SHOW IOX STATUS ALL
SHOW IOX POWER ALL
SHOW IOX LIST
SHOW COMPLEX INFO
SHOW COMPLEX STATUS
•
Access level/Bay level:
All
•
Restrictions:
◦
This command displays only the bays for which you have privileges.
◦
To save the output, you must configure your telnet software to log the session to a file or increase the history buffer size so that the output can be copied and pasted into another file.
SHOW DEVICE SERIAL_NUMBER BLADE
•
Command:
SHOW DEVICE SERIAL_NUMBER BLADE <bay number>
•
Description:
Shows the specified direct attached blade device serial number
48 General management commands
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
Dependent on bay privileges
•
Example:
OA-0016355E560A> SHOW DEVICE SERIAL_NUMBER BLADE
Serial number: USM81500RP
SHOW INTERCONNECT SESSIONS
•
Command:
SHOW INTERCONNECT SESSIONS
•
Description:
Displays which users have serial console sessions in progress for each interconnect
•
Access level/Bay level:
◦
OA Administrator, OA Operator
◦
Bay specific
•
Restrictions:
You must have access to the specified bay.
•
Example:
OA-0018FE27577F> SHOW INTERCONNECT SESSION
Interconnect Bay User
------------------ --------------
No Interconnect remote console sessions were detected.
SHOW USER SESSIONS
IMPORTANT: On Superdome 2 systems, the following long-running commands are not immediately subject to the session timeout defined by the SET SESSION TIMEOUT command:
•
SHOW {HR | FPL | LIVELOGS | SEL | SYSLOG | PARTITION CONSOLELOG}
•
CONNECT {BLADE | INTERCONNECT | PARTITION }
•
CO
•
FPL
•
SEL
If a user has one of these commands active, their session will not be removed when a session timeout occurs; instead it will be removed once they exit the long-running command and interact with the CLI. The SHOW USER SESSIONS command will not display the active session after a session timeout occurs.
•
Command:
SHOW USER SESSIONS
•
Description:
Displays a list of authenticated sessions on the OA, including CLI and WebGUI sessions.
SHOW INTERCONNECT SESSIONS 49
•
Access level/Bay level:
◦
OA Administrator, OA Operator
•
Restrictions:
None
•
Example:
[MFG Shell Enabled]iduno-oa> show user sessions
Username Age Idle Type IP Address
-------- ----------- ---------- ----- ----------------
Administrator 3s 0s Local 16.127.73.207
Administrator 2h 53m 56s 2h 53m 52s Local 16.191.144.136
Administrator 6h 24m 30s 3m 45s Local 16.119.117.151
[MFG Shell Enabled]iduno-oa> help show user sessions
SHOW USER SESSIONS: Display a list of authenticated sessions on the Onboard
Administrator. It includes CLI and WebGUI sessions.
50 General management commands
10 Enclosure Bay IP Addressing commands
ADD EBIPA
•
Command:
ADD EBIPA { BLADE | INTERCONNECT } DNS <ip address> [ { , | - } <bay
number> ]
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Adds a DNS server IP address to the list of DNS servers for either BLADE bays or
INTERCONNECT
bays
•
Access Level/Bay level:
Administrator, Operator
•
Restrictions:
◦
A maximum of three DNS servers can be added for EBIPA.
◦
The <ip address> must be in the form ###.###.###.###, where each ### ranges from 0 to 255.
DISABLE EBIPA
CAUTION: This command cycles power to the interconnect and causes a loss of connectivity.
•
Command:
DISABLE EBIPA {BLADE|INTERCONNECT} [ALL | <bay number> [{ , | - }
<bay number>]]
•
Description:
Disables the ability of the Onboard Administrator to give devices in the bays IP addresses using DHCP.
If no bay numbers are specified, then EBIPA is disabled for all bays. Devices in bays receive
IP addresses from an external server.
This causes a reset of the iLO, which causes it to attempt to get an IP address from an external
DHCP server. The interconnect is power-cycled.
•
Access level/Bay level:
Administrator, Operator
•
Restrictions:
None
ENABLE EBIPA
CAUTION: This command cycles power to the interconnect and causes a loss of connectivity.
•
Command:
ENABLE EBIPA {BLADE|INTERCONNECT} [ALL | <bay number> [{ , | - }
<bay number>]]
ADD EBIPA 51
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Enables the Onboard Administrator to provide IP addresses to the devices in the bays using
DHCP.
If you do not specify any bay numbers, then EBIPA is enabled for all bays.
DHCP traffic from iLO and the switch modules can no longer go outside the enclosure.
This causes a reset of the iLO, which causes it to attempt to get an IP address. The interconnect is power-cycled.
•
Access level/Bay level:
Administrator, Operator
•
Restrictions:
Before using this command you must set up the EBIPA settings. This includes setting the initial
IP address, the netmask, and the default gateway.
REMOVE EBIPA
•
Command:
REMOVE EBIPA {BLADE|INTERCONNECT} DNS <ip address>
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Removes the DNS server specified by the <ip address> from the list of DNS servers for either
BLADE
bays or INTERCONNECT bays
•
Access level/Bay level:
Administrator, Operator
•
Restrictions:
The <ip address> and must be in the form ###.###.###.###, where each ### ranges from 0 to 255.
SET EBIPA
•
Command:
SET EBIPA BLADE { <IP address> <netmask> } | { NETMASK <netmask> }
| { GATEWAY <gateway> } | { DOMAIN <domain> } | { LOCAL } [ ALL |
<bay number> [{- | ,} <bay number>] ]
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Sets EBIPA settings, including:
◦
Starting IP address
◦
Netmask
◦
Default gateway, primary or secondary NTP server (interconnects only)
◦
Domain name for the specified bay type
52 Enclosure Bay IP Addressing commands
If no bays are specified when setting the <ip address>, then all the bays are assigned an
IP address in the range starting from the <ip address>.
The keyword NONE can be used in the place of <ip address>, <netmask>, or <gateway> to clear the IP address.
NOTE: Link-local IP addresses can be assigned to blades, iLOs, and interconnect bays within an enclosure. Link-local addresses are intended only for use within a segment of a network and can be used for network configurations that do not required allocated IP addresses on the network.
The firewall rules on the OA will prevent these addresses from being visible outside of the local management subnet within an enclosure.
•
Access level/Bay level:
Administrator, Operator
•
Restrictions:
◦
The <ip address> and <netmask> must be in the form ###.###.###.###, where each ### ranges from 0 to 255.
◦
The <domain name> is a string containing letters (a-z, A-Z), digits (0-9), or a dash (-).
SHOW EBIPA
•
Command:
SHOW EBIPA [INTERCONNECT | BLADE]
•
Description:
Displays EBIPA information.
◦
The INTERCONNECT argument displays EBIPA information for interconnects only.
◦
The BLADE argument displays EBIPA information for blades only.
◦
The local keyword will appear in the EBIPA Address column if link-local addressing is enabled for the bay.
◦
The command will display an additional row for each bay showing the IP address, port, and protocol of each proxied protocol if the optional requirement to provide access to the blade iLOs using proxy ports on the active OA is implemented
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: fugu-oa> show ebipa
EBIPA Device Server Settings
Bay Enabled EBIPA/Current Netmask Gateway DNS Domain
--- ------- ------------- ------- --------------- --------------- ------
1 No 0.0.0.0 0.0.0.0 16.119.107.163
1A No 0.0.0.0
1B No 0.0.0.0
2 No 0.0.0.0 0.0.0.0 16.119.106.131
2A No 0.0.0.0
2B No 0.0.0.0
3 No 0.0.0.0 1.2.3.4 16.119.108.217
3A No 0.0.0.0
3B No 0.0.0.0
4 No 0.0.0.0 0.0.0.0 16.119.107.119
SHOW EBIPA 53
4A No 0.0.0.0
4B No 0.0.0.0
5 No 0.0.0.0 0.0.0.0
5A No 0.0.0.0
5B No 0.0.0.0
6 No 0.0.0.0 0.0.0.0
6A No 0.0.0.0
6B No 0.0.0.0
7 No 0.0.0.0 0.0.0.0
7A No 0.0.0.0
7B No 0.0.0.0
8 No 0.0.0.0 0.0.0.0
8A No 0.0.0.0
8B No 0.0.0.0
9 No 0.0.0.0 0.0.0.0
9A No 0.0.0.0
9B No 0.0.0.0
10 No 0.0.0.0 0.0.0.0
10A No 0.0.0.0
10B No 0.0.0.0
11 No 0.0.0.0 0.0.0.0
11A No 0.0.0.0
11B No 0.0.0.0
12 No 0.0.0.0 0.0.0.0
12A No 0.0.0.0
12B No 0.0.0.0
13 No 0.0.0.0 0.0.0.0
13A No 0.0.0.0
13B No 0.0.0.0
14 No 0.0.0.0 0.0.0.0
14A No 0.0.0.0
14B No 0.0.0.0
15 No 0.0.0.0 0.0.0.0
15A No 0.0.0.0
15B No 0.0.0.0
16 No 0.0.0.0 0.0.0.0
16A No 0.0.0.0
16B No 0.0.0.0
EBIPA Device Interconnect Settings
Bay Enabled EBIPA/Current Netmask Gateway DNS NTP Domain
--- ------- ------------- --------------- ------- ------- --------------- ------
1 No 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
2 No 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
3 No 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
4 No 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
5 No 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
6 No 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
7 No 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
8 No 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
54 Enclosure Bay IP Addressing commands
11 Enclosure network configuration commands
ADD OA DNS
•
Command:
ADD OA DNS [<bay number>] <ip address>
•
Description:
Adds an IP address of a DNS server to the list. DNS servers are used if the system is configured to use a static IP address.
If a bay number is not specified, the command defaults to the active Onboard Administrator.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
A maximum of two DNS servers can be added.
The <ip address> must be in the form ###.###.###.###, where each ### ranges from
0 to 255.
ADD SNMP TRAPRECEIVER
•
Command:
ADD SNMP TRAPRECEIVER <ip address> ["<community name>"]
•
Description:
Adds an IP address to receive SNMP traps. Traps are directed to the SNMP default port 162.
The default trap community string is public.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
◦
A maximum of eight IP addresses can be added to receive SNMP traps.
◦
Only v1 traps are supported.
◦
The <ip address> must be in the form ###.###.###.###, where each ### ranges from 0 to 255.
ADD SSHKEY
•
Command:
ADD SSHKEY <end marker> <certificate> <end marker>
•
Description:
Adds an SSH key or keys to the Administrator local account. Multiple SSHKEYs can be concatenated in the string.
1.
Locate a string that does not appear in the key, to use as the end marker.
2.
Paste in the SSHKEY string.
3.
Finish the command with the end marker.
Failure to give a proper end marker before and after the certificate might cause the interface to wait for the appropriate end marker indefinitely.
ADD OA DNS 55
•
Access level/Bay level:
Administrator
•
Restrictions:
◦
SSHKEY is only available for the Administrator local account.
◦
The SSHKEY string is limited to 8 KB.
ADD TRUSTED HOST
•
Command:
ADD TRUSTED HOST <ip address>
•
Description:
Adds an IP address to the list of systems permitted connectivity with the Onboard Administrator.
•
Access level /Bay level:
OA Administrator, OA Operator
•
Restrictions:
You can add a maximum of five IP addresses to the IP Manager.
The <ip address> must be in the form ###.###.###.### or ###.###.###.###/##, where each ### ranges from 0 to 255 and each ## ranges from 0 to 32. ## is used to specify a subnet (for example, 192.168.1.0/24).
NOTE: 0.0.0.0 and 255.255.255.255 are not valid values for <ip address>.
CLEAR SSHKEY
•
Command:
CLEAR SSHKEY
•
Description:
Removes the authorized key file used for SSH login
•
Access level/Bay level:
Administrator
•
Restrictions:
None
CLEAR VCMODE
•
Command:
CLEAR VCMODE
•
Description:
Clears Virtual Connect Mode settings.
•
Access level/Bay level:
OA Administrator
56 Enclosure network configuration commands
OA Bays
•
Restrictions:
◦
All blades in the enclosure must be powered off before clearing the VCMODE.
◦
The enclosure is no longer managed by Virtual Connect, and blades revert to default
Ethernet MAC and Fibre Channel WWN assignments. Virtual Connect might disconnect the servers from Ethernet networks and Fibre Channel fabrics.
DISABLE ALERTMAIL
•
Command:
DISABLE ALERTMAIL
•
Description:
Disables the sending of emails when events occur
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
DISABLE ENCLOSURE_IP_MODE
•
Command:
DISABLE ENCLOSURE_IP_MODE
•
Description:
◦
Disables Enclosure IP Mode.
◦
Active and Standby Onboard Administrators retain current IP addresses.
◦
After disabling Enclosure IP Mode and a takeover occurs, the enclosure no longer has a single IP address only.
•
Access level/Bay level:
OA Administrator, Operator
•
Restrictions:
None
DISABLE HTTPS
•
Command:
DISABLE HTTPS
•
Description:
Disables HTTPS access to the Onboard Administrator, which prevents access to the web-based user interface
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
DISABLE ALERTMAIL 57
DISABLE SECURESH
•
Command:
DISABLE SECURESH
•
Description:
Disables SSH access to the Onboard Administrator.
Disabling SSH prevents access to the web-based user interface and the SSH terminal interface until a terminal session re-enables the SSH protocol.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
DISABLE SNMP
•
Command:
DISABLE SNMP
•
Description:
◦
Disables SNMP support for the Onboard Administrator.
◦
Does not clear the SNMP trap receivers that have been configured.
◦
SNMP trap receivers can still be added and removed.
◦
If you disable SNMP, then Insight Manager Agents do not work properly.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
DISABLE TELNET
•
Command:
DISABLE TELNET
•
Description:
Disables Telnet access to the Onboard Administrator
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
58 Enclosure network configuration commands
DISABLE TRUSTED HOST
•
Command:
DISABLE TRUSTED HOST
•
Description:
Disables the host-based access to the Onboard Administrator. Disabling TRUSTED HOSTS allows all hosts to connect to the Onboard Administrator.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
DISABLE XMLREPLY
•
Command:
DISABLE XMLREPLY
•
Description:
Disables XML reply data return over the HTTP port
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
DISABLE WSMANAGEMENT
•
Command:
DISABLE WSMANAGEMENT
•
Description:
Disables the WS-Management service on the enclosure.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
DOWNLOAD CONFIG
•
Command:
DOWNLOAD CONFIG <url>
•
Description:
Downloads a saved configuration file from a specific IP host. The file is not verified for errors but is automatically executed in SCRIPT MODE. Supported protocols are HTTP, FTP, TFTP,
USB, and archive storage. If your FTP server does not support anonymous connections, then you can specify a user name and password by replacing the host part in the previous format with username:password@host.
DISABLE TRUSTED HOST 59
To execute a configuration script from a USB key, use usb://<directory name>/<script
file name>
.
To execute a configuration script from archive storage, use the URI shown by the SHOW
ARCHIVE command.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
You must format the <url> as protocol://host/path/file.
◦
The file cannot change the Administrator account password.
◦
The user password is not saved or restored by the DOWNLOAD CONFIG command.
DOWNLOAD SSHKEY
•
Command:
DOWNLOAD SSHKEY <url>
•
Description:
◦
Downloads an authorized key file to use for SSH logins. The file contains the public keys for users.
◦
Supported protocols are HTTP, FTP, and TFTP.
◦
Format the <url> as protocol://host/path/file.
•
Access level/Bay level:
Administrator
•
Restrictions:
None
ENABLE ALERTMAIL
•
Command:
ENABLE ALERTMAIL
•
Description:
Enables the sending of alert emails when an event occurs
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You can issue this command only if the configuration has been set up.
ENABLE ENCLOSURE_IP_MODE
•
Command:
ENABLE ENCLOSURE_IP_MODE
•
Description:
Enables Enclosure IP Mode
60 Enclosure network configuration commands
•
Access level/Bay level:
OA Administrator, Operator
•
Restrictions:
When using enclosure IP mode, only replace the standby OA module while the enclosure is powered on to ensure persistence of Enclosure IP Mode settings.
ENABLE HTTPS
•
Command:
ENABLE HTTPS
•
Description:
Enables HTTPS access to the Onboard Administrator
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
ENABLE SECURESH
•
Command:
ENABLE SECURESH
•
Description:
Enables SSH support for the Onboard Administrator
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
ENABLE SNMP
•
Command:
ENABLE SNMP
•
Description:
Enables SNMP Trap support for the Onboard Administrator
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
ENABLE HTTPS 61
ENABLE TELNET
•
Command:
ENABLE TELNET
•
Description:
Enables Telnet access to the Onboard Administrator
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
ENABLE TRUSTED HOST
•
Command:
ENABLE TRUSTED HOST
•
Description:
Enables IP security for the Onboard Administrator
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
ENABLE XMLREPLY
•
Command:
ENABLE XMLREPLY
•
Description:
Enables XML reply data over an HTTP connection
•
Access Level/Bay Level:
OA Administrator, OA Operator
•
Restrictions:
None
ENABLE WSMANAGEMENT
•
Command:
ENABLE WSMANAGEMENT
•
Description:
Enables the WS-Management service on the enclosure.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
62 Enclosure network configuration commands
TEST WSMAN
•
Command:
TEST WSMAN
•
Description:
Sends a test WS-Management notification to subscribed clients.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
REMOVE OA DNS
•
Command:
REMOVE OA DNS [<OA bay number>] <ip address>
•
Description:
◦
Removes the IP address of a DNS server from the list for the specified Onboard
Administrator.
◦
The DNS servers are used only if the system is configured to use a static IP address.
◦
If no bay number is provided, then the command default to the active Onboard
Administrator.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <ip address> must be in the form ###.###.###.###, where each ### ranges from
0 to 255.
REMOVE SNMP TRAPRECEIVER
•
Command:
REMOVE SNMP TRAPRECEIVER <ip address> [<community>]
•
Description:
Removes an IP address from the list of systems that receive SNMP traps. If the same IP address is listed multiple times with different communities, then all instances of the IP address disappear unless <community> specifies which one to remove.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <ip address> must be in the form ###.###.###.###, where each ### ranges from
0 to 255.
TEST WSMAN 63
REMOVE TRUSTED HOST
•
Command:
REMOVE TRUSTED HOST <ip address>
•
Description:
Removes an IP address from the list of systems permitted to connect to the Onboard
Administrator
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <ip address> must be in the form ###.###.###.### or ###.###.###.###/##, where each ### ranges from 0 to 255 and each ## from 0 to 32. Use the ## to specify a subnet
(for example, 192.168.1.0/24).
NOTE: 0.0.0.0 and 255.255.255.255 are not valid values for <ip address>.
SET ALERTMAIL MAILBOX
•
Command:
SET ALERTMAIL MAILBOX "<email address>"
•
Description:
Sets the email address where events are sent
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SET ALERTMAIL SENDERDOMAIN
•
Command:
SET ALERTMAIL SENDERDOMAIN "<domain>"
•
Description:
Sets the AlertMail domain. This is the DNS domain where the Onboard Administrator is located
(for example, AB.com).
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SET ALERTMAIL SMTPSERVER
•
Command:
SET ALERTMAIL SMTPSERVER <ip address>
•
Description:
Sets the AlertMaill SMTP server. This is the mail server where the Onboard Administrator delivers email-based events.
64 Enclosure network configuration commands
•
Access level/Bay level
Administrator, OA Operator
•
Restrictions:
The <ip address> must be in the form ###.###.###.###, where each ### ranges from
0 to 255.
SET OA GATEWAY
•
Command:
SET OA GATEWAY [<bay number>] <ip address>
•
Description:
◦
Sets the network default gateway.
◦
This command is used if the system is configured to use a static IP address.
◦
If you do not specify a bay number, the command defaults to the active Onboard
Administrator.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <ip address> must be in the form ###.###.###.###, where each ### ranges from 0 to
255.
SET OA NAME
•
Command:
SET OA NAME [<bay number>] "<OA name>"
•
Description:
Sets the Onboard Administrator name. If a bay number is not specified, the command defaults to the active Onboard Administrator.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The Onboard Administrator name is 1 to 32 characters long including all alphanumeric characters and the dash (-). The name cannot begin or end with a dash and cannot be entirely numeric.
SET OA UID
•
Command:
SET OA UID [<bay number>] {ON | OFF}
•
Description:
Sets the Onboard Administrator UID on or off.
If you do not specify a bay number, the command defaults to the active Onboard Administrator.
SET OA GATEWAY 65
•
Access level/Bay level:
All
•
Restrictions:
None
SET IPCONFIG
•
Command:
SET IPCONFIG {DHCP | STATIC} [<OA bay number>] [DYNAMICDNS] <ip address>
<netmask> [<gateway> [<DNS1address> [<DNS2 address>]]]
•
Description:
◦
Configures IP settings for the Onboard Administrator to DHCP mode or static mode.
◦
In STATIC mode, the IP address and Netmask are set to <ip address> and <netmask> respectively. These settings take effect immediately. If the Gateway address or DNS address or both are cleared, they are omitted. The Gateway and DNS addresses can also be set by using the SET OA GATEWAY and ADD OA DNS commands.
◦
To configure in STATIC mode, use the following command format:
SET IPCONFIG STATIC [<OA bay number>] <ip address> <netmask> [<gateway> [<DNS1address> [<DNS2
address>]]]
◦
In DHCP mode, the IP address, Netmask, Gateway address, and DNS addresses are obtained from the DHCP. This setting immediately takes effect. If DYNAMICDNS is specified, then the DNS server is notified of the new IP address of the system when it is received from the DHCP server.
◦
To configure in DHCP mode, use the following command format:
SET IPCONFIG DHCP [<OA bay number>] [DYNAMICDNS]
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SET SNMP COMMUNITY
•
Command:
SET SNMP COMMUNITY {READ | WRITE} "<community name>"
•
Description:
Sets the community name for the read or write SNMP community. If a blank write community name is given, then SNMP set commands are disabled until a non-empty community name is given.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
◦
The write <community name> must be no more than 20 characters long, and the read
<community name> must be must be no more than 20 characters long.
◦
All printable characters are valid.
66 Enclosure network configuration commands
◦
The default read community name is public.
◦
The default write community name is public.
SET SNMP CONTACT
•
Command:
SET SNMP CONTACT "<contact>"
•
Description:
Configures the name of the system contact. The default contact is blank.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <contact> must be no more than 20 characters long. Valid characters are all alphanumeric, the underscore (_), the dash (-), and spaces.
SET SNMP LOCATION
•
Command:
SET SNMP LOCATION "<location>"
•
Description:
Configures the SNMP location of the enclosure. The default location is blank.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <location> must be no more than 20 characters long. Valid characters are all alphanumeric, the underscore (_), the dash (-), and spaces.
SHOW NETWORK
•
Command:
SHOW NETWORK
•
Description:
Displays:
◦
DHCP state
◦
Dynamic DNS state
◦
IP address subnet mask
◦
Gateway address
◦
Primary and secondary DNS addresses
◦
MAC address
◦
HTTP and HTTPS server status
◦
SNMP status
SET SNMP CONTACT 67
◦
SSH status
◦
Telnet status
◦
NTP status
◦
Trusted Host status
◦
HPSIM Trust Mode status
◦
AlertMail status
◦
XML Reply status
◦
WSMan status
◦
Link Loss Failover status
◦
GUI Login Detail status
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW NETWORK
Onboard Administrator Network Settings:
DHCP: Disabled
IP Address: 15.255.98.2
Netmask: 255.255.248.0
Gateway Address: 15.255.96.1
Primary DNS: 16.110.135.51
Secondary DNS: 16.110.135.52
MAC Address: 00:21:5A:B1:B5:C7
Network Link Settings: Link Auto-negotiation
Onboard Administrator Protocol Status:
Web (HTTP/HTTPS): Enabled
SNMP: Disabled
SecureSH: Enabled
Trusted Hosts: Disabled
HPSIM Trust Mode: Disabled
Telnet: Enabled
AlertMail: Disabled
Mailbox: Not Set
SMTP Server: Not Set
Sender Domain: Not Set
XML Reply: Enabled
NTP: Disabled
Primary NTP server: 16.110.135.123
Secondary NTP server: Not Set
WSMan: Enabled
Link Loss Failover: Disabled
Link Loss Interval: 60 seconds
Enclosure IP Mode: Disabled
GUI Login Detail: Enabled
68 Enclosure network configuration commands
SHOW SNMP
•
Command:
SHOW SNMP
•
Description:
Displays:
◦
Status
◦
SNMP system name
◦
Location
◦
Contact
◦
Read community name
◦
Write community name
◦
List of the trap destinations
•
Access level/Bay level:
OA Administrator, OA Operator, OA user
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW SNMP
SNMP Configuration:
Status: Disabled
System Name: Shorty
System Location:
System Contact:
Read Community Name: public
Write Community Name:
No trap receivers specified.
SHOW SSHFINGERPRINT
•
Command:
SHOW SSHFINGERPRINT
•
Description:
Displays the key fingerprint of the Onboard Administrator host public key
•
Access level/Bay level:
OA Administrator, OA Operator, user
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW SSHFINGERPRINT
1024 3f:5c:33:0a:a1:2e:9b:2c:da:eb:fe:90:87:34:13:b7 /etc/ssh/id_dsa.pub
SHOW SNMP 69
SHOW SSHKEY
•
Command:
SHOW SSHKEY
•
Description:
Displays the contents of the existing SSH authorized key files
•
Access level/Bay level:
Administrator
•
Restrictions:
None
•
Example:
Firmware Version: 2.20
Built: 04/14/2008 @ 14:04
OA Bay Number: 1
OA Role: Active
Authenticating with public key "rsa-key-123456789"
TEST ALERTMAIL
•
Command:
TEST ALERTMAIL
•
Description:
Sends a test AlertMail message to the configured email address
•
Access level/Bay level:
Administrator, operator
Restrictions:
You must have OA permission to perform this command.
TEST SNMP
•
Command:
TEST SNMP
•
Description:
Sends a test SNMP trap to all of the configured trap destinations
•
Access level/Bay level:
OA Administrator
•
Restrictions:
You must enable SNMP to use this function.
70 Enclosure network configuration commands
12 Enclosure management commands
CLEAR SYSLOG
CAUTION: You cannot restore this information after you delete it.
•
Command:
CLEAR SYSLOG {ENCLOSURE | OA <bay number>}
•
Description:
Clears the Onboard Administrator system log. If you do not specify a bay number, the Active
Onboard Administrator system log is cleared.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
DISABLE GUI_LOGIN_DETAIL
•
Command:
DISABLE GUI_LOGIN_DETAIL
•
Description:
Disables extended enclosure information available in the GUI on the login page
•
Access level/Bay level:
OA Administrator
•
Restriction:
None
DISABLE LLF
•
Command:
DISABLE LLF INTERVAL
•
Description:
Disables Link Loss Failover for Onboard Administrator Redundancy.
•
Access level/Bay level::
Operator, Administrator
•
Restrictions:
You must have OA permission to perform this command.
ENABLE GUI_LOGIN_DETAIL
•
Command:
ENABLE GUI_LOGIN_DETAIL
•
Description:
Enables extended enclosure information available in the GUI on the login page
CLEAR SYSLOG 71
•
Access level/Bay level:
OA Administrator
•
Restriction:
None
ENABLE LLF
•
Command:
ENABLE LLF
•
Description:
Enables Link Loss Failover for Onboard Administrator Redundancy.
•
Access level/Bay level:
Operator, Administrator
•
Restrictions:
You must have OA permission to perform this command.
POWEROFF XFABRIC
•
Command:
POWEROFF XFABRIC
•
Description:
Powers off all Xbar Fabric modules
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
◦
You must be logged on to the monarch OA to perform this command.
◦
The POWEROFF XFABRIC command fails if all partitions are not shut down.
POWERON XFABRIC
•
Command:
POWERON XFABRIC
•
Description:
Powers on all Xbar Fabric modules
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be logged on to the monarch OA to perform this command.
72 Enclosure management commands
RESTART OA
•
Command:
RESTART OA [<bay number>]
•
Description:
Resets the Onboard Administrator module specified by <bay number>. If no bay number is given, then the Onboard Administrator the user is logged in to is restarted.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SET DISPLAY EVENTS
•
Command:
SET DISPLAY EVENTS {ON | OFF}
•
Description:
◦
Turns the displaying of events that are triggered by status changes in the system on or off.
◦
This command is specific to the CLI session, and must be issued for every CLI session to display events in that session.
•
Access level/Bay level:
All
•
Restrictions:
Only for bays for which you have privileges
SET ENCLOSURE ASSET
•
Command:
SET ENCLOSURE ASSET [TAG] "<asset tag>"
•
Description:
◦
Sets the enclosure asset tag
◦
The default enclosure asset tag is blank
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <asset tag> must be 0 to 32 characters long and includes all alphanumeric, underscore
(_), and dash (-) characters.
RESTART OA 73
SET ENCLOSURE NAME
•
Command:
SET ENCLOSURE NAME "<enclosure name>"
•
Description:
◦
Changes the enclosure name.
◦
The default enclosure name is the mid-plane serial number.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The <enclosure name> must be 1 to 32 characters long and includes all alphanumeric, underscore (_), and dash (-) characters.
SET ENCLOSURE PART_NUMBER
•
Command:
SET ENCLOSURE PART_NUMBER "<part number>"
•
Description:
Sets the part number of the enclosure
•
Access level/Bay level:
OA Administrator
•
Restrictions:
Must be 10 characters in length and the first character must be a digit. Acceptable characters are all alphanumeric and the dash (-).
SET ENCLOSURE PDU_TYPE
•
Command:
SET ENCLOSURE PDU_TYPE {1|2|3|4}
•
Description:
Sets the enclosure PDU type to:
◦
1 = Single-phase
◦
2 = Three-phase
◦
3 = Three-phase, international
◦
4 = DC Power Input Module
•
Access level/Bay level:
OA Administrator
•
Restrictions:
Only 1, 2, 3, 4 are valid PDU types.
74 Enclosure management commands
SET ENCLOSURE SERIAL_NUMBER
•
Command:
SET ENCLOSURE SERIAL_NUMBER "<serial number>"
•
Description:
Sets the enclosure serial number.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
Must be 10 characters in length and includes all alphanumeric, underscore (_), and dash (-) characters.
SET ENCLOSURE UID
•
Command:
SET ENCLOSURE UID {ON | OFF}
•
Description:
Turns the UID LED of the enclosure on or off.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SET IOX UID
•
Command:
SET IOX UID { ALL | <iox number> [{-|,}] <iox number>]} {ON | OFF}
•
Description:
Turns the UID LED of the specified IOX enclosures on or off.
•
Access level/Bay level:
OA Administrator, OA Operator, OA user
•
Restrictions:
You must be logged on to the monarch OA to perform this command.
SET LLF INTERVAL
•
Command:
SET LLF INTERVAL <seconds>
•
Description:
Set the Link Loss Failure Interval
•
Access level/Bay level:
Operator, Administrator
•
Restrictions:
Must have OA permission to perform this command.
SET ENCLOSURE SERIAL_NUMBER 75
SET POWER MODE
•
Command:
SET POWER MODE {NOTREDUNDANT | REDUNDANT | POWERSUPPLY}
•
Description:
◦
Configures power settings to ensure a specified level of redundancy.
◦
The NOTREDUNDANT setting includes all healthy power supplies in the enclosure power capacity. The loss of even a single power supply might result in oversubscription.
CAUTION: HP does not recommend the NOTREDUNDANT setting for production systems.
◦
The POWERSUPPLY setting enables one lower (1–6) and one upper (7–12) power supply to fail without being over committed on power.
◦
The REDUNDANT setting enables all power supplies on one side of the compute enclosure to fail without being over committed on power. For example, this would enable power supplies 1–3 and 7–9 to fail (or 4–6 and 10–12) while the remaining power supplies still function.
•
Power mode is established at the complex level and is managed from the Monarch OA. A change in Dynamic Power Savings mode is propagated to all OAs in the complex.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SET POWER LIMIT
•
Command:
SET POWER LIMIT {<number> | OFF}
•
Description:
Sets or removes a limit on how much input power can be consumed by the enclosure. This setting is useful when the enclosure receives power from a PDU with a limited power rating.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SET POWER SAVINGS
•
Command:
SET POWER SAVINGS {ON | OFF}
•
Description:
◦
Turns power savings mode on or off. Power savings mode turns unneeded power supplies off.
◦
The increased load on the remaining power supplies increases efficiency, resulting in less power consumption.
76 Enclosure management commands
◦
The Dynamic Power Savings mode is established at the complex level and is managed from the Monarch OA. A change in Dynamic Power Savings mode is propagated to all
OAs in the complex.
◦
Automatically turns on additional supplies as needed in response to rapid increases in load.
NOTE: This setting does not impact the power mode or redundancy settings.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SET TIMEZONE
•
Command:
SET TIMEZONE "<timezone>"
•
Description:
Sets the time zone
See Time zone settings ( “Time zone settings” (page 207)
) for appropriate time zones. Some that are commonly used include: CET, CST6CDT, EET, EST, EST5EDT, GB, GMT, HST, MET,
MST, MST7MDT, NZ, PRC, PST8PDT, UCT, and UTC.
•
Access level/Bay level
OA Administrator, OA Operator
•
Restrictions:
None
SHOW CONFIG
•
Command:
SHOW CONFIG
•
Description:
Displays the script required to recreate the settings of the enclosure. Passwords are not included for any user.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
•
Example: sphere-oa> show all
>SHOW CONFIG
#Script Generated by Administrator
#Generated on: Tue May 4 15:16:06 2010
#Set Enclosure Time
SET TIMEZONE 77
SET TIMEZONE CST6CDT
#SET DATE MMDDhhmm{{CC}YY}
#Set Enclosure Information
SET ENCLOSURE ASSET TAG ""
SET ENCLOSURE NAME "sphere"
SET RACK NAME "UnnamedRack"
SET POWER MODE REDUNDANT
SET POWER SAVINGS ON
#Power limit must be within the range of 5400-32800
SET POWER LIMIT OFF
#Enclosure Dynamic Power Cap must be within the range of 1353-15644
SET ENCLOSURE POWER_CAP OFF
SET ENCLOSURE POWER_CAP_BAYS_TO_EXCLUDE None
#Set PowerDelay Information
SET INTERCONNECT POWERDELAY 1 0
SET INTERCONNECT POWERDELAY 2 0
SET INTERCONNECT POWERDELAY 3 0
SET INTERCONNECT POWERDELAY 4 0
SET INTERCONNECT POWERDELAY 5 0
SET INTERCONNECT POWERDELAY 6 0
SET INTERCONNECT POWERDELAY 7 0
SET INTERCONNECT POWERDELAY 8 0
SET SERVER POWERDELAY 1 0
SET SERVER POWERDELAY 2 0
SET SERVER POWERDELAY 3 0
SET SERVER POWERDELAY 4 0
--More-- (20% of 4709 bytes)
SHOW DATE
•
Command:
SHOW DATE
•
Description:
Displays the current date, time, and time zone of the internal clock of the enclosure
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW DATE
Date: 2008-04-15T10:36:46-05:00 Time Zone: CST6CDT
SHOW DISPLAY EVENTS
•
Command:
SHOW DISPLAY EVENTS
•
Description:
Displays whether event notification is on or off
•
Access level/Bay level:
All
78 Enclosure management commands
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW DISPLAY EVENTS
Display Events is set to OFF.
SHOW ENCLOSURE FAN
•
Command:
SHOW ENCLOSURE FAN {<fan number> | ALL}
•
Description:
Displays information about, and current status of the specified enclosure fan
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> show enclosure fan 1
Fan #1 information:
Status: OK
Speed: 48 percent of Maximum speed
Maximum speed: 18000
Minimum speed: 10
Power consumed: 21
Product Name: Active Cool 200 Fan
Part Number: 412140-B21
Spare Part Number: 413996-001
Version: 2.7
Diagnostic Status:
Internal Data OK
Location OK
Device Failure OK
Device Degraded OK
Missing Device OK
SHOW ENCLOSURE INFO
•
Command:
SHOW ENCLOSURE INFO
•
Description:
Displays:
◦
Enclosure name
◦
Enclosure type
◦
Onboard Administrator hardware version
SHOW ENCLOSURE FAN 79
◦
Enclosure part number
◦
Serial number
◦
UUID
◦
Asset tag
◦
Midplane spare part number
◦
Solutions ID
◦
Power Distribution Unit information
◦
Onboard Administrator Tray information
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: oa_hostname> show enclosure info
Enclosure Information:
Enclosure Number: 1
Enclosure Name: OA-00A1B2C3D4E5
Enclosure Type: Superdome Gen2 Enclosure
Onboard Administrator Hardware Version: 1.00
Part Number:
Serial Number: 1Z34AB7890
UUID: 091Z34AB7890
Asset Tag:
Midplane Spare Part Number: 414050-001
Solutions ID: 0000000000000000
Power Distribution Unit:
PDU Type: [Unknown]
PDU Spare Part Number:
Onboard Administrator Tray Information:
Type: HP BladeSystem c7000 Onboard Administrator Tray
Spare Part Number: 416000-001
Serial Number: 12345678901234
SHOW ENCLOSURE LCD
•
Command:
SHOW ENCLOSURE LCD
•
Description:
Displays information about the Insight Display screen
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW ENCLOSURE LCD
80 Enclosure management commands
Status: OK
Display: On
Name: BladeSystem c7000 Insight Display
Spare Part Number: 441203-001
Manufacturer: HP
Fw Version: 2.2.2
Diagnostic Status:
Internal Data OK
SHOW ENCLOSURE POWERSUPPLY
IMPORTANT: In a complex with one or more failed power supplies it is possible for attempts to power on servers to fail if the resulting power allocation would result in the Power Redundancy
Status becoming Failed. The administrator must explicitly reduce the redundancy setting to enable powering on servers prior to the failed power supplies being serviced. This applies to AC Redundant and Power Supply Redundant power modes.
•
Command:
SHOW ENCLOSURE POWERSUPPLY {ALL | <power supply number> [{ , | - }
<power supply number>]}
•
Description:
Displays:
◦
Power supply status
◦ ac input status
◦
Capacity
◦
Current power output
◦
Serial number
◦
Product name
◦
Part number
◦
Spare part number
◦
Hardware revision for the specified power supply (if one is specified)
◦
Diagnostic status
◦
Range of power supplies, or for all power supplies (if ALL is specified).
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
SHOW ENCLOSURE POWERSUPPLY 81
sphere-oa2> show enclosure powersupply 1
Power Supply #1 Information:
Status: OK
AC Input Status: OK
Capacity: 2400 Watts
Current Power Output: 275 Watts
Serial Number: 5AGUD0AHLWW1V2
Product Name: HP 2400W HE PSU
Part Number: 499253-B21
Spare Part Number: 500242-001
Product Ver: 01
Diagnostic Status:
Internal Data OK
Device Failure OK
Power Cord OK
Indicted OK
SHOW ENCLOSURE STATUS
•
Command:
SHOW ENCLOSURE STATUS
•
Description:
Displays the basic health and status of the enclosure subsystem
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-001CC414F34F> show enclosure status
Enclosure 1:
Status: OK
Enclosure ID: OK
Unit Identification LED: Off
Diagnostic Status:
Internal Data OK
Thermal Danger OK
Device Failure OK
Device Degraded OK
Redundancy OK
Blades OK
Indicted OK
Onboard Administrator:
Status: OK
Power Subsystem:
Status: OK
Power Mode: Redundant
Redundancy State: Redundant
Power Capacity: 13500 Watts DC
Power Available: 12750 Watts DC
Present Power: 24900 Watts AC
Cooling Subsystem:
Status: OK
Fans Good/Wanted/Needed: 15/6/5
Fan 1: 14000 RPM (78%)
Fan 2: 14000 RPM (78%)
82 Enclosure management commands
Fan 3: 14000 RPM (78%)
Fan 4: 14000 RPM (78%)
Fan 5: 14000 RPM (78%)
Fan 6: 14000 RPM (78%)
Fan 7: 14000 RPM (78%)
Fan 8: 14000 RPM (78%)
Fan 9: 14000 RPM (78%)
Fan 10: 14000 RPM (78%)
Fan 11: 14000 RPM (78%)
Fan 12: 14000 RPM (78%)
Fan 13: 14000 RPM (78%)
Fan 14: 14000 RPM (78%)
Fan 15: 14000 RPM (78%)
SHOW ENCLOSURE TEMP
•
Command:
SHOW ENCLOSURE TEMP
•
Description:
Displays:
◦
Locale
◦
Status (OK, warm, degraded, or failed)
◦
Temperature in degrees Fahrenheit
◦
Temperature in degrees Celsius for all temperature sensors
NOTE: Interconnect modules and GPSMs only display temperature status.
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
◦
There is no temperature display provided for Interconnect Modules or GPSMs. Those modules will show only Status and Limits.
•
Example:
Locale Bay # Temp Status Temp Caution Critical
---------------------- ----- ----------- -------- ------- --------
Enclosure N/A 26C/ 78F --- ---
Onboard Administrator 1 OK 35C/ 95F 75C 80C
Blade Bay 3 Unknown 25C/ 77F 38C 43C
Blade Bay 4 Unknown 26C/ 78F 45C 60C
Blade Bay 8 Unknown 26C/ 78F 35C 38C
Interconnect Module 1 OK ---- --- ---
Interconnect Module 2 OK ---- --- ---
XFM 3 Unknown 26C/ 78F 35C 38C
GPSM 1 OK ---- --- ---
SHOW ENCLOSURE TEMP 83
SHOW FRU
•
Command:
SHOW FRU
•
Description:
◦
The FRU Summary section provides information on all field replaceable units within the enclosure.
◦
Information provided in this section can quickly aid the administrator in contacting HP
Customer Service for troubleshooting, repair, and ordering replacements.
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have access to the specified bay.
•
Example:
OA_hostname> show fru
Enclosure
Model: Superdome Gen2 Enclosure
Manufacturer: HP
Serial Number: 1Z34AB7890
Part Number:
Spare Part Number: 414050-001
Upper Midplane PCB version: 1
AC Input Module
Model: HP AC Module
Manufacturer: HP
Spare Part Number: 413495-001
Onboard Administrator Tray
Model: BladeSystem c7000 Onboard Administrator Tray
Manufacturer: HP
Serial Number: 12345678901234
Spare Part Number: 416000-001
Onboard Administrator 1
Model: BladeSystem c7000 Onboard Administrator
Manufacturer: HP
Serial Number: 12345678901234
Part Number: 412142-B21
Spare Part Number: 414055-001
Firmware Version: 2.10
HwVersion: A0
Engineering Date Code (EDC): XA01
Blade 01
Model: [Unknown]
Manufacturer: [Unknown]
Serial Number: [Unknown]
Part Number: [Unknown]
Spare Part Number: [Unknown]
Engineering Date Code (EDC): XA01
Mezz 2
Model: InfiniBand FDR/Ethernet 10Gb/40Gb 2P 544M Adapter
84 Enclosure management commands
Manufacturer: HP
Serial Number: IL21300010
PCA Serial Number: IL21300010
Part Number: 661692-001
Spare Part Number: 656088-001
Product Ver: B1
Adaptive Fabric Adapter 1
Model: HP FlexFabric 10Gb 2-port 554FLB Adapter
Manufacturer: HP
Serial Number: N/A
PCA Serial Number: WD15BK0831
Part Number: 647586-B21
Spare Part Number: 649940-001
Product Ver: X2
Interconnect 1
Model: 4X DDR IB Switch Module for HP c-Class BladeSystem
Manufacturer: HP
Serial Number: IL2YWWZZZZ
Part Number: 410398-B21
Spare Part Number: 410408-001
...
Fan 1
Model: BladeSystem c-Class fan
Part Number: 412140-B21
Spare Part Number: 413996-001
...
Power Supply 1
Model: 412138-B21
Serial Number: 5A22B0AHLXXXXX
Spare Part Number: 411099-001
...
Insight Display
Model: BladeSystem c7000 Insight Display
Manufacturer: HP
Spare Part Number: 441203-001
Firmware Version: 2.00
XFM 1
Model: [Unknown]
Manufacturer: HP
Part Number: AD323A
Spare Part Number: AD217-60001
Serial Number: USE7335P51
Firmware Bundle Revision: 2.9
Engineering Date Code (EDC): XA01
...
IOX 6
Model: IOX
Manufacturer: HP
Part Number: 412140-B21
Spare Part Number: AD217-60005
Serial Number: 543543861
Asset Tag: IOX123
Firmware Bundle Revision: 2.9
Engineering Date Code (EDC): XA01
...
GPSM 1
Model: GPSM
Manufacturer: HP
Part Number: 412140-B21
Spare Part Number: AD217-60009
SHOW FRU 85
Serial Number: 543543861
Firmware Bundle Revision: 2.5
Engineering Date Code (EDC): XA01
SHOW OA
•
Command:
SHOW OA {CERTIFICATE | INFO | NETWORK | STATUS | USB} [ALL | <bay number> [{ , | - }
<bay number>]]
•
Description:
Displays the certificate information, network configuration, status, or USB mode of the Onboard
Administrator. You can use the alias ACTIVE or STANDBY for the <bay number>. The command SHOW OA without any further arguments displays the HELP list for all SHOW OA arguments.
•
Access level/Bay level:
All
•
Restrictions:
None
SHOW OA CERTIFICATE
•
Command:
SHOW OA CERTIFICATE [ALL | <bay number> [{ , | - } <bay number> ]]
•
Description:
Shows the certificate information for the Onboard Administrator
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW OA CERTIFICATE
Onboard Administrator #1 Certificate Information:
Issued by: OA-0018FE27577F
Valid from: 2007-02-01T09:54:30Z
Valid until: 2017-01-29T09:54:30Z
Serial Number: 1A:TT:66:77:FF:2D
Version: 1
MD5 Fingerprint: F08:87:33:89:D9:E1:W3:BC:6D:88:C1:77:A4:KI:DC:AA
SHA1 Fingerprint: 78:B8:14:09:ED:98:66:3D:58:ED:C2:U5:80:AB:78:4L:4B:4F:12:34
Subject:
Common Name (CN): OA-1234FE27577F
Country (C):
State or Province (ST):
City or Locality (L):
Organization Name (0): Hewlett-Packard
Organizational Unit: Onboard Administrator
86 Enclosure management commands
SHOW OA INFO
•
Command:
SHOW OA INFO [ALL | <bay number> [{ , | - } <bay number>]]
•
Description:
Displays information about the Onboard Administrator. If the Onboard Administrator is not specified, the command defaults to the Active Onboard Administrator.
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show oa info 1
Onboard Administrator #1 information:
Model: Superdome 2 Onboard Administrator
Part Number: AH389-60001
Spare Part Number: AH389-60001
Serial Number: OA8CBK0069
UUID: 02OA8CBK0069
Manufacturer: HP
Firmware Bundle Revision: 0.6.35
Hw Version: A01
SHOW OA NETWORK
•
Command:
SHOW OA NETWORK [ALL | <bay number> [{ , | - } <bay number>]]
•
Description:
Shows the network configuration for the specified Onboard Administrator. If you do not specify the Onboard Administrator, the command defaults to the Active Onboard Administrator.
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW OA NETWORK
Onboard Administrator #1 Network Information:
Name: OA-1234E2124L7F
DHCP: Enabled - Dynamic DNS
IP Address: 16.84.190.253
Netmask: 123.456.78.9
Gateway Address: 123.58.36.44
Primary DNS: 12.345.65.78
Secondary DNS: 12.345.67.88
MAC Address: 00:18:FE:27:57:7F
Link settings: Forced 100 Mbit - Full Duplex
Link Status: Active
SHOW OA INFO 87
Enclosure IP Mode: Not Supported
SHOW OA STATUS
•
Command:
SHOW OA STATUS [ALL | <bay number> [{ , | - } <bay number>]]
•
Description:
Displays health status for the Onboard Administrator. If you do not specify the Onboard
Administrator, the command defaults to the Active Onboard Administrator.
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show oa status
Onboard Administrator #2 Status:
Name: sphere-oa2
Role: Active
UID: Off
Status: OK
Diagnostic Status:
Internal Data OK
Firmware Mismatch OK
SHOW POWER
•
Command:
SHOW POWER
•
Description:
Displays the current power configuration
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show power
Power Mode: Redundant
Dynamic Power: Enabled
Set Power Limit: Not Set
Power Capacity: 14400 Watts DC
Power Available: 12775 Watts DC
Power Allocated: 1625 Watts DC
Present Power: 1161 Watts AC
Power Limit: 17510 Watts AC
88 Enclosure management commands
SHOW SYSLOG
•
Command:
SHOW SYSLOG {BLADE <bay number> | ENCLOSURE | OA <bay number>
| SETTINGS}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Displays the syslog of the enclosure with 22 lines per screen. To quit the command, enter Q.
Any other key shows the next screen, when there is more information to display.
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
◦
You must have access to the specified bay.
◦
The SHOW SYSLOG BLADE command does not apply to HP Integrity Superdome 2 server blades or HP Integrity server blades.
•
Examples:
OA-0016355E560A> SHOW SYSLOG SERVER 1
Retrieving Server syslogs ...
Server 1 Syslog:
<
EVENT_LOG DESCRIPTION="Integrated Management Log">
<
EVENT
SEVERITY="Informational"
CLASS="Maintenance"
LAST_UPDATE="02/12/2007 18:01"
INITIAL_UPDATE="02/12/2007 18:01"
COUNT="1"
DESCRIPTION="IML Cleared (iLO 3 user:Administrator)"
OA-0016355E560A> SHOW SYSLOG ENCLOSURE 2
Apr 23 12:25:03 OA: Authentication failure for user larry from 18.84.33.55, requesting authenticate_user
Apr 23 12:25:13 OA: Authentication failure for user larry from 18.84.33.55, requesting authenticate_user
Apr 23 12:25:33 OA: Authentication failure for user larry from 18.84.33.55, requesting authenticate_user
Apr 23 12:26:36 OA: Authentication failure for user larry from 18.84.33.55, requesting authenticate_user
Apr 23 12:26:50 OA: demo logged into the Onboard Administrator
Apr 23 13:18:43 OA: [email protected] logged into the Onboard Administrator
OA-0018FE27577F> SHOW SYSLOG SETTINGS
Remote log: Disabled
Address:
Port: 514
SHOW SYSLOG 89
SHOW SYSLOG OA
•
Command:
SHOW SYSLOG OA [<bay number>]
•
Description:
Displays the syslog for the Onboard Administrator. If no bay number is given, then the Active
Onboard Administrator syslog appears.
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW SYSLOG OA
Apr 2 16:21:22 in.ftpd[25446]: connection from 12.34.567.890
Apr 2 16:21:24 in.ftpd[25446]: exiting due to EOF from client
Apr 2 16:21:35 in.ftpd[25451]: connection from 12.34.567.890
Apr 2 16:21:36 in.ftpd[25451]: exiting due to EOF from client
Apr 2 16:24:29 in.ftpd[25222]: exiting due to EOF from client
Apr 2 16:25:01 in.ftpd[25558]: connection from 12.34.567.890
Apr 2 16:25:02 in.ftpd[25558]: udog logged in
Apr 2 16:25:03 in.ftpd[25559]: connection from 12.34.567.890
Apr 2 16:25:05 in.ftpd[25559]: udog logged in
Apr 2 16:25:13 in.ftpd[25559]: //ramdisk/www/js/global.js uploaded
Apr 2 16:31:44 in.ftpd[25559]: //ramdisk/www/js/global.js uploaded
Apr 2 16:32:58 OA: Administrator logged into the Onboard Administrator
Apr 2 16:34:27 in.ftpd[25559]: exiting due to EOF from client
Apr 2 16:55:02 in.ftpd[25558]: exiting due to timeout (idle time 1800)
Apr 2 16:59:12 OA: Administrator logged out of the Onboard Administrator
Apr 2 19:30:05 in.ftpd[31241]: connection from 12.34.567.890
Apr 2 19:30:07 in.ftpd[31241]: guest logged in
Apr 2 19:30:12 in.ftpd[31245]: connection from 12.34.567.890
Apr 2 19:30:13 in.ftpd[31245]: udog logged in
Apr 2 19:30:27 in.ftpd[31245]: Can't change directory to standby.xml: No such file or directory
Apr 2 19:30:29 in.ftpd[31241]: Can't change directory to standby.xml: No such file or directory
Apr 2 19:31:09 in.ftpd[31245]: //ramdisk/www/js/global.js uploaded
Apr 2 19:33:55 in.ftpd[31245]: //ramdisk/www/js/global.js uploaded
Apr 2 19:37:40 in.ftpd[31245]: //ramdisk/www/js/global.js uploaded
Apr 2 19:40:07 in.ftpd[31241]: exiting due to read error from client: Connecti on reset by peer
90 Enclosure management commands
SHOW VCMODE
•
Command:
SHOW VCMODE
•
Description:
Displays Virtual Connect Mode settings
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW VCMODE
Virtual Connect Mode: Disabled
UPLOAD CONFIG
•
Command:
UPLOAD CONFIG { "<url>" | ARCHIVE "<filename>" | USB "<filename>"
}
•
Description:
Uploads a script to the specified URL or URI, which duplicates the current runtime configuration.
Supported protocols are FTP, TFTP, USB, and Archive Storage. The URL must be formatted as:
protocol://host/path/filename
.
If your FTP server does not support anonymous logins, you can specify a user name and password within the URL formatted as:
ftp://username:password@host/path/filename
.
To save a configuration file to a USB key, use the USB command and provide a file name.
To save to Archive Storage, use the URI shown by the SHOW ARCHIVE command.
If this is a non-monarch OA and an Archive Storage destination is provided, the file will be uploaded to the Archive Storage thumb drive in the monarch OA.
NOTE: This can also be done by using the archive command and providing a file name.
•
Access level/Bay level:
OA Administrator
•
Restriction:
The user password is not saved or restored by the UPLOAD CONFIG command.
SHOW VCMODE 91
13 Complex management commands
CLEAR NTP
•
Command:
CLEAR NTP {PRIMARY | SECONDARY}
•
Description:
Disables access to the Primary or Secondary NTP server
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
You must be connected to the monarch OA.
◦
Clearing the Primary NTP server disables NTP.
DISABLE NTP
•
Command:
DISABLE NTP
•
Description:
◦
Disables the synchronizing of time and date with a remote server using the NTP protocol
◦
Does not clear any NTP servers that have been configured
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
ENABLE NTP
•
Command:
ENABLE NTP
•
Description:
Enables NTP support for the Onboard Administrator
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
92 Complex management commands
RESTART COMPLEX
CAUTION: This command ungracefully halts all processing across the HP Integrity Superdome 2 complex. This can cause partitions in the complex to lose data and possibly become unstable. Do not use this command unless you have tried the following recovery methods:
•
Restarting the OA with the RESTART OA command.
•
Restarting partitions.
•
Restarting the Xbar Fabric by the following method:
1.
Shut down all partitions.
2.
Power off the Xbar Fabric with the POWEROFF XFABRIC command.
3.
Power on the Xbar Fabric with the POWERON XFABRIC command.
4.
Restart partitions.
•
Command:
RESTART COMPLEX [FORCE]
•
Description:
Restarts the complex by the following method:
1.
Powers off all system blades, XFMs, IOX enclosures, interconnect modules, and GPSMs.
2.
Restarts the active OA.
3.
Powers on XFMs.
4.
Restarts partitions that were active when the command was run.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
The command does not run unless the FORCE argument is used. The command will print a warning message and then exit if the FORCE argument is not used.
◦
You must be connected to the monarch OA.
SET COMPLEX NAME
•
Command:
SET COMPLEX NAME {<complex_name>}
•
Description:
◦
Changes the complex name.
◦
The default complex name is Complex1.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
◦
The <complex_name> must be 1 to 20 characters long and includes all alphanumeric, underscore (_), dash (-), dot (.) and space characters.
◦
You must be connected to the monarch OA.
RESTART COMPLEX 93
SET DATE
•
Command:
SET DATE MMDDhhmm [[CC]YY][TZ]
•
Description:
Sets the date of the complex with the following definitions:
◦
MM: Month
◦
DD: Day
◦ hh: Hour (24-hour time)
◦ mm: Minute
◦
CC: Century
◦
YY: Year
◦
TZ: Time zone
If you leave the time zone variable blank, then the current time zone is left in effect.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
◦
You must be connected to the monarch OA.
◦
Date and time can only be set if NTP is disabled.
◦
MM is an integer from 01 to 12.
◦
DD is an integer from 01 to 31.
◦ hh is an integer from 00 to 24.
◦ mm is an integer from 00 to 60.
◦
For valid time zones, see
“Time zone settings” (page 207) .
SET NTP PRIMARY
•
Command:
SET NTP PRIMARY <ip address>
•
Description:
Sets the primary server used for synchronizing time and date using the NTP protocol
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
◦
You must be connected to the monarch OA.
◦
The <ip address> must be in the form ###.###.###.###, where each ### ranges from 0 to 255.
94 Complex management commands
SET NTP SECONDARY
•
Command:
SET NTP SECONDARY <ip address>>
•
Description:
Sets the secondary server used for synchronizing time and date using the NTP protocol
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
◦
You must be connected to the monarch OA.
◦
The <ip address> must be in the form ###.###.###.###, where each ### ranges from 0 to 255.
SHOW COMPLEX INFO
•
Command:
SHOW COMPLEX INFO
•
Description:
Displays the following fields:
◦
Product name
◦
Complex name
◦
Original product number
◦
Current product number
◦
UUID
◦
Manufacturer
◦
Serial number
◦
Complex type
◦
Configured complex firmware version
During the initialization phase, string values can be set to “Unknown”, “[Unknown]”, or
“None”. If this occurs, try the command again after a few minutes.
•
Access level/Bay level:
OA Administrator, OA Operator, OA user
•
Restrictions:
You must be connected to the monarch OA.
•
Example: oa_hostname> show complex info
Product Name: Superdome2 16s
Complex Name: Complex1
Original Product Number: AH337A
Current Product Number: AH337A
UUID: Unset
Manufacturer: hp
SET NTP SECONDARY 95
Serial Number: Unset
Complex Type: 03000102
Configured Complex FW Revision: 0.6.35
SHOW COMPLEX STATUS
•
Command:
SHOW COMPLEX STATUS
•
Description:
Displays complex operational status information:
◦
Overall complex status
◦
Complex enclosure ID status
◦
Complex enclosure status
◦
Complex robust store status
◦
Complex CAMNET status
◦
Complex Product ID status
◦
Complex cooling status
◦
Complex thermal status
◦
Diagnostics of specific faults
◦
Detailed diagnostic message of faults found
•
Access level/Bay level:
All
•
Restrictions:
You must be connected to the monarch OA.
•
Example: sphere-oa2> show complex status
Status: OK
Enclosure ID: OK
Enclosure: OK
Robust Store: OK
CAMNET: OK
Product ID: OK
Xfabric: OK
Diagnostic Status:
Thermal Danger OK
Cooling OK
Firmware Mismatch OK
IOX OK
96 Complex management commands
14 Blade management commands
SET NIC
•
Command:
SET NIC {AUTO | FORCED}
•
Description:
Configures the external NIC for auto-negotiation or forced link settings.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
SET BLADE POWERDELAY
•
Command:
SET BLADE POWERDELAY {ALL | <bay number> [{ - | , } <bay number>]}
{number of seconds to delay power | NOPOWERON}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Set the PowerDelay status of the specified server or range of servers. If the delay is zero, the delay has no effect on the device. If the delay is NOPOWERON, then the device cannot power on until all devices have completed the delays.
•
Access level/Bay level:
◦
Administrator
◦
Bay specific
•
Restrictions:
You must have access to the specified bay number.
SET BLADE UID
•
Command:
SET BLADE UID {ALL | <bay number> [{ - | , } <bay number>]} {ON | OFF}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Turns a server blade UID LED on or off
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have access to the specified bay number.
SET NIC 97
SHOW BLADE INFO
•
Command:
SHOW BLADE INFO {ALL | <bay number> [{ , | - } <bay number>]}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Displays the following fields:
◦
Type
◦
Manufacturer
◦
Product name
◦
Part number
◦
Spare part number
◦
Serial number
◦
UUID
◦
Server name
◦
Asset tag
◦
Firmware bundle revision
◦ nPartition revision
◦
All CPU types and associated maximum speeds
◦
Memory
◦
NIC MAC addresses
◦ iLO type, name, iLO IP address, and iLO MAC address
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have access to the specified bay numbers.
•
Example: sphere-oa2> show blade info 1
Server Blade #1 Information:
Type: Server Blade
Manufacturer: HP
Product Name: CB900s i2
Part Number: AH342-60003
System Board Spare Part Number: AH342-60003
Serial Number: MYJ84901ZG
UUID: 33343230-3033-4D59-4A38-343930315A47
Server Name: [Unknown]
Asset Tag: [Unknown]
98 Blade management commands
Firmware Bundle Revision: 0.6.35
nPartition Revision: Unknown
cpusocket-1/1/0: Intel Itanium 9300 series 1330 MHz
Board Product Name: TUK_C0_1316
Serial Number: SGH848413K
Assembly Part Number: AH339-2006A
EDC: XA01
dimm-1/1/0/1: 1024 MB
dimm-1/1/0/2: empty
dimm-1/1/0/3: empty
dimm-1/1/0/4: empty
dimm-1/1/0/5: empty
dimm-1/1/0/6: empty
dimm-1/1/0/7: empty
dimm-1/1/0/8: 1024 MB
dimm-1/1/0/9: 1024 MB
dimm-1/1/0/10: empty
dimm-1/1/0/11: empty
dimm-1/1/0/12: empty
dimm-1/1/0/13: empty
dimm-1/1/0/14: empty
dimm-1/1/0/15: empty
dimm-1/1/0/16: 1024 MB
Total Memory: 4096 MB
Total Memory: 4096 MB
Embedded Ethernet
NIC 1 MAC Address: 00:24:81:D2:05:70
NIC 2 MAC Address: 00:24:81:D2:05:74
NIC 3 MAC Address: 00:24:81:D2:05:78
NIC 4 MAC Address: 00:24:81:D2:05:7C
Management Processor Information:
Type: Integrity iLO 3
Name: iLO-00237dd565f4
IP Address: 16.93.73.240
MAC Address: 00:23:7D:D5:65:F4
SHOW BLADE LIST
•
Command:
SHOW BLADE LIST
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Displays a brief description of all server blades to which the current user has access
•
Access level/Bay level:
Any
•
Restrictions:
You must have access to the specified bay number.
•
Example: sphere-oa2> show blade list
Bay iLO Name iLO IP Address Status Power UID Partner
--- ----------------------------- --------------- -------- ------- --- -------
SHOW BLADE LIST 99
1 iLO-00237dd565f4 16.93.73.240 OK On Off
2 iLO-00237dd55598 15.255.103.130 OK On Off
3 iLO-00237dd56500 16.93.73.86 OK Off Off
4 iLO-00237dd56584 16.93.73.121 OK Off Off
5 iLO-002264fddbec 16.93.73.73 OK Off Off
6 iLO-00237dd5651a 16.93.73.15 OK Off Off
7 iLO-00237dd5556e 16.93.72.122 OK Off Off
8 [Absent]
9 [Subsumed]
10 [Subsumed]
11 [Subsumed]
12 [Subsumed]
13 [Subsumed]
14 [Subsumed]
15 [Subsumed]
16 [Absent]
Totals: 7 server blades installed, 2 powered on.
SHOW BLADE NAMES
•
Command:
SHOW BLADE NAMES
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Displays a brief description of all blades to which the current user has access
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have access to the specified bay number.
•
Example:
OA-0018FE27577F> show blade names
Bay Server Name Serial Number Status Power UID Partner
--- ----------------------------- --------------- -------- ------- --- -------
1 First89123HostNameInILO USM64204B1 OK On Off
2 Integrity BL860c CSJ0634214 OK On Off
3 [Absent]
4 [Absent]
5 [Subsumed]
6 [Subsumed]
7 YOUR-EYZCGYAYBB USM62401EP OK On On
8 [Absent]
Totals: 3 server blades installed, 3 powered on.
SHOW BLADE PORT MAP
•
Command:
SHOW BLADE PORT MAP {ALL | <bay number> [{ , | - } <bay number>]}
100 Blade management commands
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Displays the port mapping for the blade specified by the bay number
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
◦
You must have access to the specified bay number.
◦
This command is not applicable to storage blades.
•
Example:
OA-0018FE27577F> SHOW SERVER PORT MAP
Mezz
Mezz Mezz Device Port Interconnect Interconnect
Slot Device Port Status Bay Bay Port Device ID
------------------------------- Blade 001 ---------
< absent>
------------------------------- Blade 02A ---------
1 Not Present
Embed Embedded Ethernet
Port 1 OK Bay 1 Port 2 55:1E:0B:91:8F:02
Port 2 No Connect Bay 2 Port 2 55:1E:0B:91:8F:03
------------------------------- Blade 02B ---------
1 Not Present
Embed Embedded Ethernet
Port 1 OK Bay 1 Port 10 00:1E:0B:92:20:6E
Port 2 No Connect Bay 2 Port 10 00:1E:0B:92:20:6F
SHOW BLADE POWERDELAY
•
Command:
SHOW BLADE POWERDELAY {ALL | <bay number> [{ - | , } <bay number>]}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Displays the PowerDelay status for the specified server blade or range of server blades
•
Access level/Bay level:
◦
All
◦
Bay specific
SHOW BLADE POWERDELAY 101
•
Restrictions:
You must have access to the specified bay number.
•
Example:
OA-0018FE27577F> SHOW SERVER POWERDELAY ALL
Current PowerDelay Status: Not in Progress
Bay Device PowerDelay State Delay (seconds)
--- -------------------------------- ------------
1 Absent Disabled
1A Absent Disabled
1B Absent Disabled
2 Subsumed Disabled
2A ProLiant BL2x220c G5 Disabled
2B ProLiant BL2x220c G5 Disabled
3 Absent Disabled
3A Absent Disabled
3B Absent Disabled
4 Absent Disabled
4A Absent Disabled
4B Absent Disabled
5 Absent Disabled
5A Absent Disabled
5B Absent Disabled
6 Absent Disabled
6A Absent Disabled
6B Absent Disabled
7 ProLiant BL460c G1 Disabled
7A Absent Disabled
7B Absent Disabled
8 AiO SB600c Storage Disabled
8A Absent Disabled
8B Absent Disabled
SHOW BLADE STATUS
•
Command:
SHOW BLADE STATUS {ALL | <bay number> [{ , | - } <bay number>]}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Displays the following settings of server blade:
◦
Power (OK or off)
◦
Health (OK, CPU failure, or power module failure)
◦
Thermal (OK, warm, caution, or critical)
◦
UID LED
102 Blade management commands
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show blade status 1
Blade #1 Status:
Power: On
Current Wattage used: 1325 Watts
Health: OK
Unit Identification LED: Off
Diagnostic Status:
Internal Data OK
Management Processor OK
I/O Configuration OK
Power OK
Cooling OK
Device Failure OK
Device Degraded OK
Device Info OK
Firmware Mismatch OK
PDHC OK
Indicted OK
SHOW BLADE TEMP
•
Command:
SHOW BLADE TEMP {ALL | <bay number> [{ , | - } <bay number>]}
NOTE:
SERVER
is a valid alias for BLADE.
•
Description:
Displays the temperature sensor information for a specified blade or range of blades
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have access to the specified bay number.
•
Example: sphere-oa2> show blade temp 1
Device Bay #1 Temperature Information
Locale Status Temp Caution Critical
----------------------------------- ------ -------- ------- --------
Memory Zone OK 25C/ 77F 40C 50C
Memory Zone OK 25C/ 77F 40C 50C
Memory Zone OK 26C/ 78F 40C 50C
Memory Zone OK 24C/ 75F 40C 50C
Ambient Zone OK 23C/ 73F 32C 37C
System Zone OK 29C/ 84F 65C 70C
System Zone OK 27C/ 80F 65C 70C
System Zone OK 26C/ 78F 65C 70C
SHOW BLADE TEMP 103
15 IOX enclosure management commands
SHOW IOX INFO
•
Command:
SHOW IOX INFO { ALL | <iox_number> {[ - | , ] <iox_number>} }
•
Description:
Displays the following fields:
◦
Model
◦
Manufacturer
◦
Part number
◦
Serial number
◦
Power supply bays
◦
Power supply information:
–
Model
– Serial number
–
Spare part number
◦
Firmware bundle revision
•
Access level/Bay level:
OA Administrator, OA Operator, OA User
•
Restrictions:
You must be connected to the monarch OA.
•
Example: grog-oa> show iox info 9
IOX 9
Model: IOX
Manufacturer: HP
Part Number: AH338-60301
Serial Number: MYJ94102Y0
Power Supply Bays: 2
Power Supply Bay 1
Model: 512327-B21
Serial Number: 5AQXF0BLLXW53Q
Spare Part Number: 511778-001
Power Supply Bay 2
Model: 512327-B21
Serial Number: 5AQNB0A4DYE7T1
Spare Part Number: 511778-001
Firmware Bundle Revision: 0.6.40
104 IOX enclosure management commands
SHOW IOX LIST
•
Command:
SHOW IOX LIST
•
Description:
Displays the IOX enclosure list.
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: oa-hostname> show iox list
Bay IOX Type Power: Bay 1 Power: Bay 2 Health UID
--- --------------------- ------------ ------------ ----------------- -------
5 Superdome IOX On Off OK On
6 [Absent]
7 [Absent]
8 [Absent]
9 Superdome IOX Off Off OK Off
10 Superdome IOX Off Off OK Off
11 [Absent]
12 [Absent]
SHOW IOX POWER
•
Command:
SHOW IOX POWER { ALL | <iox_number> {[ - | , ] <iox_number>} }
•
Description:
Displays power information for specified IOX enclosures.
•
Access level/Bay level:
OA Administrator, OA Operator, OA User
•
Restrictions:
You must be connected to the monarch OA.
•
Example: oa_hostname> show iox power all
IOX Bay 5
Present Power: 245 Watts AC
IOX Bay 6
Present Power: 245 Watts AC
…
…
SHOW IOX LIST 105
SHOW IOX STATUS
•
Command:
SHOW IOX STATUS { ALL | <iox_number> {[ - | , ] <iox_number> }}
•
Description:
Displays IO expansion enclosure status information:
◦
Status
◦
Power state of I/O bays
◦
UID state
◦
Diagnostic status
◦
Power subsystem status
◦
Cooling subsystem status
◦
Xbar Fabric status
◦
I/O slots state
◦
Thermal sensor status
•
Access level/Bay level:
OA Administrator, OA Operator, OA User
•
Restrictions:
You must be connected to the monarch OA.
•
Example:
OA-001CC414F34F> show iox status 6
IOX 6:
Health: OK
Power:
Bay 1: On
Bay 2: Off
Unit Identification LED: Off
Diagnostic Status:
Internal Data OK
Redundancy OK
Power Subsystem:
Status: OK
Redundancy State: Redundant
Power Capacity: 4500 Watts DC
Power Available: 4500 Watts DC
Present Power: 247 Watts AC
PS 1: OK
PS 2: OK
Cooling Subsystem:
Status: OK
Fans Good/Wanted/Needed: 4/4/3
Fan 1: 5486 RPM (30%)
Fan 2: 5479 RPM (30%)
Fan 3: 0 RPM (0%)
Fan 4: 5488 RPM (30%)
Xfabric Link Status:
Link 1: OK
106 IOX enclosure management commands
Link 2: OK
...
Link N: FAILED
IO Slots Status:
Bay Slot Status
---- ---- -----------------
1 1 OK
1 2 OK
...
SHOW IOX STATUS 107
16 Interconnect management commands
ASSIGN INTERCONNECT
•
Command:
ASSIGN INTERCONNECT {ALL | <bay number> [{ , | - } <bay number>]}
{"<user name> | LDAP GROUP <LDAP group name>"}
•
Description:
Assigns interconnects specified to an existing user or group
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
CLEAR INTERCONNECT SESSION
•
Command:
CLEAR INTERCONNECT SESSION <bay number>
•
Description:
Terminates a serial console session of a user on an interconnect. The termination is not graceful and the user loses any unsaved work.
•
Access level/Bay level:
◦
Administrator, operator
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
CONNECT INTERCONNECT
•
Command:
CONNECT INTERCONNECT <bay number>
•
Description:
Connects the user to the serial console of the interconnect present in the interconnect module bay
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
108 Interconnect management commands
POWEROFF INTERCONNECT
•
Command:
POWEROFF INTERCONNECT {ALL | <bay number> [{ - | , } <bay number>]}
•
Description:
Sends a request to power off the interconnect module
•
Access level/Bay level:
◦
Administrator, operator
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
POWERON INTERCONNECT
•
Command:
POWERON INTERCONNECT {ALL | <bay number> [{ - | , } <bay number>]}
•
Description:
Powers on the specified interconnect
•
Access level/Bay level:
◦
Administrator, operator
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
RESTART INTERCONNECT
•
Command:
RESTART INTERCONNECT <bay number>
•
Description:
Resets the interconnect tray in the specified bay
•
Access level/Bay level:
◦
Administrator, operator
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
POWEROFF INTERCONNECT 109
SET INTERCONNECT POWERDELAY
•
Command:
SET INTERCONNECT POWERDELAY {ALL | <bay number> [{ - | , } <bay number>]}
{number of seconds to delay power | NOPOWERON}
•
Description:
Sets the PowerDelay status for the specified interconnect or range of interconnects. If the delay is zero, the delay has no effect on the device. If the delay is NOPOWERON, the device cannot power on until all devices have completed their delays.
•
Access level/Bay level:
◦
Administrator
◦
Bay specific
•
Restrictions:
You must have access to the specified bay number.
SET INTERCONNECT UID
•
Command:
SET INTERCONNECT UID {ALL | <bay number> [{ , | - } <bay number>]}
{ON | OFF}
•
Description:
Turns an interconnect UID on or off
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
SET XFM UID
•
Command:
SET XFM UID { ALL | <xfm_number> {[ - | , ] <xfm_number>}} {ON | OFF}
•
Description:
Turns the UID LED of the specified Xbar Fabric modules on or off.
•
Access level/Bay level:
OA Administrator, OA Operator, OA user
•
Restrictions:
You must be logged on to the monarch OA to perform this command.
110 Interconnect management commands
SHOW GPSM INFO
•
Command:
SHOW GPSM INFO { ALL | <gpsm_number> {[ - | , ] <gpsm_number>} }
•
Description:
Displays:
◦
Model
◦
Manufacturer
◦
Part Number
◦
Spare Part Number
◦
Serial Number
◦
Engineering Date Code
◦
Firmware Bundle Revision
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show gpsm info 1
Bay 1 GPSM Information:
Model: GPSM Board
Manufacturer: HP
Part Number: AH337-60304
Spare Part Number: AH337-60304
Serial Number: MYJ847044E
Engineering Date Code (EDC): XC05
Firmware Bundle Revision: 0.6.35
SHOW GPSM STATUS
•
Command:
SHOW GPSM STATUS { ALL | <gpsm_number> {[ - | , ] <gpsm_number> }}
•
Description:
Displays GPSM status information; UID state and health state.
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show gpsm status 1
Bay 1 GPSM Status:
Health: OK
SHOW GPSM INFO 111
Unit Identification LED: Off
Diagnostic Status:
Internal Data OK
Management Processor OK
Firmware Mismatch OK
Indicted OK
SHOW INTERCONNECT INFO
•
Command:
SHOW INTERCONNECT INFO [ALL | <bay number> | <bay number>-<bay number>]
•
Description:
Displays:
◦
Interconnect type
◦
Product name
◦
Width
◦
Part number
◦
Spare part number
◦
Serial number
◦
Temperature sensor
◦
JS2 Connector
◦
Ethernet information
◦
Serial information
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
•
Example:
OA-0018FE27577F> show interconnect info all
1. Ethernet
Product Name: GbE2c Ethernet Blade Switch
Width: Single
URL to Management interface:
In-Band IPv4 Address: 16.84.189.81
User Assigned Name:
Part Number: 410917-B21
Spare Part Number: 414037-001
Serial Number: MY36290EMT
Temperature Sensor: Present
JS2 Connector: Absent
Internal Ethernet Interface to OA: Present
112 Interconnect management commands
Internal Ethernet Route to OA: Enabled
Internal Serial Interface to OA: Absent
Internal Serial Route to OA: Disabled
External Serial Port Interface: Present
External Ethernet Interface: Present
2. Ethernet
Product Name: HP 1/10Gb VC-Enet Module
Width: Single
URL to Management interface: http://16.84.189.186/
In-Band IPv4 Address: 16.84.189.186
User Assigned Name:
Part Number: 399593-B22
Spare Part Number: 399725-001
Serial Number: TW2702004K
Temperature Sensor: Present
JS2 Connector: Absent
Internal Ethernet Interface to OA: Present
Internal Ethernet Route to OA: Enabled
Internal Serial Interface to OA: Present
Internal Serial Route to OA: Enabled
Serial Port Baud Rate: 115200
External Serial Port Interface: Absent
External Ethernet Interface: Absent
Firmware Version: 2.00
3. <absent>
4. <absent>
SHOW INTERCONNECT LIST
•
Command:
SHOW INTERCONNECT LIST
•
Description:
Displays the interconnect list
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW INTERCONNECT LIST
Bay Interconnect Type Manufacturer Power Health UID Management IP
--- ----------------- -------------------- ----- --
1 Ethernet Cisco Systems, Inc. On OK Off 16.84.189.31
2 [Absent]
3 [Absent]
4 [Absent]
Totals: 1 interconnect modules installed, 1 powered on.
SHOW INTERCONNECT LIST 113
SHOW INTERCONNECT PORT MAP
•
Command:
SHOW INTERCONNECT PORT MAP {ALL | <bay number>
| <bay number>-<bay number>}
•
Description:
Displays the port mapping for the interconnect specified by the bay number
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
•
Example:
OA-0018FE27577F> SHOW INTERCONNECT PORT MAP ALL
1: Cisco Catalyst Blade Switch 3120X for HP w/ IP Base
Type: Ethernet
Width: Single
Status: OK
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Status OK OK OK OK
Blade 2A 7 2B 7
Mezz/Nic NI NI NI NI
Port 1 1 1 2
2. <absent>
3. <absent>
4. <absent>
SHOW INTERCONNECT POWERDELAY
•
Command:
SHOW INTERCONNECT POWERDELAY {ALL | <bay number> [{ - | , }
<bay number>]}
•
Description:
Displays the PowerDelay status for the specified interconnects or range of interconnects
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
None
•
Example:
OA-0018FE27577F> SHOW INTERCONNECT POWERDELAY ALL
Current PowerDelay Status: Not in Progress
Bay Device PowerDelay State Delay (seconds)
--- -------------------------------- ------------
114 Interconnect management commands
1 Cisco Catalyst Blade Switch 3120 Disabled
2 Absent Disabled
3 Absent Disabled
4 Absent Disabled
SHOW INTERCONNECT STATUS
•
Command:
SHOW INTERCONNECT STATUS {ALL | <bay number>
| <bay number>-<bay number>}
•
Description:
Displays interconnect status information; UID state and health state
•
Access level/Bay level:
◦
All
◦
Bay specific
•
Restrictions:
You must have explicit access to a bay given by the ASSIGN INTERCONNECT command.
•
Example:
OA-0018FE27577F> SHOW INTERCONNECT STATUS ALL
Interconnect Module #1 Status:
Status : OK
Thermal: OK
CPU Fault: OK
Health LED: OK
UID: Off
Powered: On
Diagnostic Status:
Internal Data OK
Management Processor OK
Thermal Warning OK
Thermal Danger OK
I/O Configuration OK
Device Failure OK
Device Degraded OK
Interconnect Module #2 Status:
Interconnect Module Type: No Interconnect Module Installed
Interconnect Module #3 Status:
Interconnect Module Type: No Interconnect Module Installed
Interconnect Module #4 Status:
Interconnect Module Type: No Interconnect Module Installed
SHOW XFM INFO
•
Command:
SHOW XFM INFO { ALL | <xfm_number> {[ - | , ] <xfm_number>} }
SHOW INTERCONNECT STATUS 115
•
Description:
Displays:
◦
Model
◦
Manufacturer
◦
Part Number
◦
Spare Part Number
◦
Serial Number
◦
Engineering Date Code
◦
Firmware Bundle Revision
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show xfm info all
Bay 1 XFM Information:
Model: XFM
Manufacturer: HP
Part Number: AH341-60101
Spare Part Number: AH341-60101
Serial Number: MYJ852008A
Engineering Date Code (EDC): XB03
Firmware Bundle Revision: 0.6.35
Bay 2 XFM Information:
Model: XFM
Manufacturer: HP
Part Number: AH341-60101
Spare Part Number: AH341-60101
Serial Number: MYJ85002NM
Engineering Date Code (EDC): XB03
Firmware Bundle Revision: 0.6.35
Bay 3 XFM Information:
Model: XFM
Manufacturer: HP
Part Number: AH341-60101
Spare Part Number: AH341-60101
Serial Number: MYJ85301CV
Engineering Date Code (EDC): XB03
Firmware Bundle Revision: 0.6.35
Bay 4 XFM Information:
Model: XFM
Manufacturer: HP
Part Number: AH341-60101
Spare Part Number: AH341-60101
Serial Number: MYJ905000N
Engineering Date Code (EDC): XB03
Firmware Bundle Revision: 0.6.35
116 Interconnect management commands
SHOW XFM LIST
•
Command:
SHOW XFM LIST
•
Description:
Displays the Xbar Fabric module list.
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show xfm list
Bay XFM Type Power Health UID
--- ----------------------------- --------- ------------------- ---------
1 XFM On OK Off
2 XFM On OK Off
3 XFM On OK Off
4 XFM On OK Off
SHOW XFM STATUS
•
Command:
SHOW XFM STATUS { ALL | <xfm_number> {[ - | , ] <xfm_number> }}
•
Description:
Displays Xbar Fabric module status information; UID state, health state, and link health states.
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show xfm status 1
OA-001CC414F34F> show xfm status 1
Bay 1 XFM Status:
Health: OK
Power: On
Unit Identification LED: Off
Diagnostic Status:
Internal Data OK
Management Processor OK
Thermal Warning OK
Thermal Danger OK
Power OK
Firmware Mismatch OK
Indicted OK
Link 1: OK
Link 2: Unknown
Link 3: Unknown
Link 4: Unknown
Link 5: Unknown
Link 6: Unknown
SHOW XFM LIST 117
Link 7: Unknown
Link 8: Unknown
118 Interconnect management commands
17 Enclosure DVD commands
SHOW DVD INFO
•
Command:
SHOW DVD INFO
•
Description:
Displays:
◦
Model
◦
Manufacturer
◦
Part Number
◦
Spare Part Number
◦
Serial Number
◦
Engineering Date Code
•
Access level/Bay level:
Any
•
Restrictions:
None
•
Example: sphere-oa2> show dvd info
DVD Information:
Model: DVD module
Manufacturer: HP
Part Number: AH337-60105
Spare Part Number: AH337-60105
Serial Number: MYJ85005TS
Engineering Date Code (EDC): XA06
SHOW DVD STATUS
•
Command:
SHOW DVD STATUS
•
Description:
Displays DVD drive status information; UID state and health state
•
Access level/Bay level:
All
•
Restrictions:
None
•
Example: sphere-oa2> show dvd status
DVD Status:
Health: OK
SHOW DVD INFO 119
Unit Identification LED: Off
Diagnostic Status:
Internal Data OK
Power OK
Missing Device OK
SET DVD UID
•
Command:
SET DVD UID {ON | OFF}
•
Description:
Sets the DVD UID.
•
Access level/Bay level
◦
All
•
Restrictions:
None
•
Example: festival-oa> help set dvd uid on
SET DVD UID { ON | OFF }: Toggle the UID (Unit Identification LED) on the DVD.
festival-oa> help set dvd uid off
SET DVD UID { ON | OFF }: Toggle the UID (Unit Identification LED) on the DVD.
120 Enclosure DVD commands
18 Remote syslog commands
DISABLE SYSLOG REMOTE
•
Command:
DISABLE SYSLOG REMOTE
•
Description:
Disables remote system logging
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be operator or administrator with OA permission to perform this command.
ENABLE SYSLOG REMOTE
•
Command:
ENABLE SYSLOG REMOTE
•
Description:
Enables remote system logging
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be operator or administrator with OA permission to perform this command.
SET REMOTE SYSLOG PORT
•
Command:
SET REMOTE SYSLOG PORT <port>
•
Description:
Set the IP port number for remote system log. Setting the remote port is optional. If it is not set, then the default UDP port 514 is used to send system log messages.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
The remote port must be an integer between 1 and 65535 inclusive.
SET REMOTE SYSLOG SERVER
•
Command:
SET REMOTE SYSLOG SERVER <server>
•
Description:
Sets the IP address or DNS name for remote system log messages.
DISABLE SYSLOG REMOTE 121
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
None
SHOW SYSLOG SETTINGS
•
Command:
SHOW SYSLOG SETTINGS
•
Description:
Displays the remote syslog settings for the Onboard Administrator
•
Access level/Bay level:
Operator, Administrator
•
Restrictions:
You must have OA permission to perform this command.
•
Example:
OA-0018FE27577F> SHOW SYSLOG SETTINGS
Remote log: Disabled
Address:
Port: 514
TEST SYSLOG
•
Command:
TEST SYSLOG
•
Description:
Tests the remote system log settings by logging a test message to the syslog.
The test message also appears in the local OA Administrator system log.
•
Access level/Bay level:
Operator, Administrator
•
Restriction:
You must have OA permission to perform this command.
Remote syslog example
The remote syslog consists of a date and time stamp, the Onboard Administrator IP address, text, and a priority number. The date and time stamp, and the text match the Onboard Administrator syslog entry.
Sep 9 16:00:28 10.128.126.204 OA: Remote system logging enabled to server 16.83.33.81,
port 514 (priority 13)
122 Remote syslog commands
19 USB support commands
DOWNLOAD CONFIG using USB key
•
Command:
DOWNLOAD CONFIG <url>
•
Description:
Downloads a saved configuration file from a specific IP host. The file is not checked for errors but is automatically executed in SCRIPT MODE. Supported protocols are HTTP, FTP, TFTP, and
USB. Format the <url> as protocol://host/path/file. If your FTP server does not support anonymous connections, then you can specify a user name and password by replacing the host part in the previous format with username:password@host. To execute a configuration script from a USB key, use usb://<directory name>/<script file
name>
.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
◦
The file cannot change the Administrator account password.
◦
The user password is not saved or restored by the DOWNLOAD CONFIG command.
SHOW USBKEY
•
Command:
SHOW USBKEY
•
Description:
Displays a list of firmware images, configuration scripts, and ISO images present on the USB media connected to the enclosure DVD module.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
None
•
Example: st10a> show usbkey
Firmware Image Files Image Version
--------------------------------------- ------------usb://d2/hpsd2fw.bundle 0.80.001
Configuration Script Files
---------------------------------------
No configuration files found (*.cfg).
ISO Image Files
---------------------------------------
No ISO image files found (*.iso).
DOWNLOAD CONFIG using USB key 123
UPLOAD CONFIG using USB key
•
Command:
UPLOAD CONFIG { "<url>" | ARCHIVE "<filename>" | USB "<filename>"
}
•
Description:
Uploads a script to the specified url which duplicates the current runtime configuration.
Supported protocols are ftp, tftp, usb and archive. The url should be formatted as
protocol://host/path/filename
. The url syntax for IPv6 addresses is
protocol://[<ipv6 address>]/path/file.
If your FTP server does not support anonymous logins, you can specify a username and password within the url formatted as:
ftp://username:password@host/path/filename
.
The file will be uploaded to a relative file path with a single slash between host and path. To upload the file to an absolute file path, use a double slash between host and path.
To save a configuration file to a USB key or to the Archive Storage, use the USB or ARCHIVE command and provide a filename. If this is a non-monarch OA and an Archive Storage destination is provided, the file will be uploaded to the Archive Storage thumb drive in the monarch OA.
Uploads a script to the specified URL, which duplicates the current runtime configuration.
Supported protocols are FTP, TFTP, and USB. The URL should be formatted as:
protocol://host/path/filename
. If your FTP server does not support anonymous logins, you can specify a user name and password within the URL formatted as:
ftp://username:password@host/path/filename
. To save a configuration file to a
USB key, use the USB command and provide a file name.
•
Access level/Bay level:
OA Administrator
•
Restriction:
The user password is not saved or restored by the UPLOAD CONFIG command.
The TFTP server will not create new files, the destination file must exist on the server side and must have sufficient permissions (a+w).
124 USB support commands
20 iCAP commands
For more information on using iCAP commands, see the HP Instant Capacity user guide for Version
10.x.
ICAPSTATUS
•
Command:
ICAPSTATUS
•
Description:
Allows a display of the Superdome 2 system iCAP status in a format similar to an HP UX-based icapstatus
. By default, the OA icapstatus command will display information on all nPars and vPars that are active.
The options for the command:
Option
-s
-p n[:v]
-a
-I | -i
-r
-t
-z
-M
Long option
--audit-snapshot
--partition n[:v]
--active-cores
--inactive-cores
--revision
--total-cores
--hardware-support
--format f
Meaning
Generate an audit snapshot codeword. This encrypts a summary of the complex iCAP state, and must be presented at the HP iCAP portal in order to acquire codewords to modify iCAP state.
Specify the nPar and vPar, separated by “:”. If omitted when executed on the OA, no “local partition” information is shown. When invoked through IPMI from an OS, defaults to the originating partition.
Display the current number of active cores in the nPar specified by -p.
Display the current number of inactive cores in the nPar specified by -p.
Report iCAP software version.
Display the total number of cores in the nPar specified by -p.
Return 0, 0 means that the hardware is supported by iCAP.
Generate machine-readable status.
Format keywords would include
delimited, the traditional format of data separated by “:” characters.
•
Access level/Bay level:
All
•
Restriction:
You must be connected to the monarch OA.
ICAPSTATUS 125
ICAPMODIFY
•
Command:
ICAPMODIFY
•
Description:
◦
Allows setting some configuration options, including notification email address and iCAP system ID.
◦
Allows activation and deactivation of cores in an nPar, or assignment and deassignment of cores in a vPar.
◦
Defers activation/deactivation of cores in an nPar.
◦
Provides a mechanism for applying iCAP codewords to securely affect the complex iCAP contract terms.
The options for the command:
Option
-a n
-p n[:v]
-s n
-d n
-D
-C c
-c c
-f f
-i i
-w w
-r [system_startup]
-T on|off
Long option
--activate n
--partition n[:v]
--set-active n
--deactivate n
--defer
--codeword c
--contact c
--from-email
--system-identifier i
--warning w
--reconcile
Meaning
Activate <n> cores in nPar specified by -p and -v
Specify the nPar and vPar ID, separated by “:”. Each ID may be either a number or a name. When invoked through IPMI from an OS, defaults to the originating partition.
Set the number of active cores in partition to n; activate or deactivate as necessary.
Deactivate n cores in p/v
Instead of immediately initiating an
OLA/D operation for -a/-d/-s, modify the partition IA to take effect on the next OS boot.
Apply a codeword to the complex.
Set contact email address, mostly for use by GiCAP.
Set from-email address. A single complex-wide from-address will be supported.
Set iCAP system identification.
NOTE: May differ from complex name.
Warning period for temporary capacity expiration.
Reconcile the number of active cores in the partition to the parspec
IA.
Pre-authorize Ticap. If on is used, all further activations are now implicitly authorized to use TiCAP if required. Off ceases the pre-authorization.
126 iCAP commands
•
Access level/Bay level:
Operator or Admin
•
Restriction:
You must be connected to the monarch OA.
ICAPMODIFY 127
21 Partition commands
For more information on using Partition commands, see the HP Integrity Superdome 2 Partitioning
Administrator Guide.
ASSIGN PARCON_ADMIN
•
Command:
ASSIGN PARCON_ADMIN { "<user name>" | LDAP GROUP "<LDAP group name>" }
•
Description:
Assigns partition configuration Administration privileges to an existing user or group.
•
Access level/Bay level:
OA Administrator
•
Restriction:
You must be connected to the monarch OA.
UNASSIGN PARCON_ADMIN
•
Command:
UNASSIGN PARCON_ADMIN { "<user name>" | LDAP GROUP "<LDAP group name>" }
•
Description:
Removes Partion Configuration Administration privileges from the specified user or group.
•
Access level/Bay level:
OA Administrator
•
Restriction:
You must be connected to the monarch OA.
ASSIGN PARTITION
•
Command:
ASSIGN PARTITION { ALL | <nPartition Number>[:<vPartition Number>] [ , <nPartition Number:<vPartition
Number> ] } { "<user name>" | LDAP GROUP "<LDAP group name>" }
•
Description:
Assigns all or enumerated partition privilege rights to an existing user or group. Assignment of all partitions will allow the given user or group to access all current existing partitions and any future partitions.
•
Access level/Bay level:
OA Administrator
•
Restriction:
You must be connected to the monarch OA.
128 Partition commands
UNASSIGN PARTITION
•
Command:
UNASSIGN PARTITION { ALL | <nPartition Number>[:<vPartition Number>] [ , <nPartition Number:<vPartition
Number> ] } { "<user name>" | LDAP GROUP "<LDAP group name>" }
•
Description:
Unassign all or enumerated partition privilege rights to an existing user or group.
•
Access level/Bay level:
OA Administrator
•
Restriction:
You must be connected to the monarch OA.
PARCREATE
•
Command:
parcreate
[-a blade:blade_path:[blade_type]:[use_on_next_boot]:
[failure_usage]:[slm_value]]...
[-a io:iobay_path:[use_on_next_boot][:failure_usage]]...
[-c blade_path:[blade_type]:[use_on_next_boot]:[failure_usage]:
[slm_value]]...
[-n res_type:ia_value]
[-p nPartition_id]
[-B]
[-C parspec_name[:create_partition_flag]]
[-G memory_granularity_type:size]
[-L slm_value]
[-M type:max_value]
[-N next_boot_mode]
[-O os_name]
[-P partition_name]
[-T hyper_threading_flag]
[-V vga_flag]
[-X parspec:change_policy_flag]
[-Z parspec_name]
•
Description:
Creates a new nPartition on the local complex. The command takes the specified blades and
I/O bays and assigns them to the new nPartition. If an nPartition number is not specified, the command finds an available nPartition number and assigns it to the new nPartition. If an nPartition name is not specified, a default name of the format nParNNNN is given to the new nPartition (where NNNN is a 4 digit nPartition number).
The options for the command:
Option
[-c blade]
[-a [blade:blade | io:io_bay]]
[-B]
Meaning
Specify blade(s) to be assigned to the nPartition.
Specify blade or I/O resource for the nPartition. An nPartition can be created without assigning any resources to it.
Specify that the new nPartition be booted. The nPartition is booted until the UEFI prompt.
UNASSIGN PARTITION 129
Option
[-P name]
[-L slm_value]
[-Z parspecname]
[-O osname]
[-C parspecname[:[create_nPar_flag]]]
Meaning
Specify an optional name for the new nPartition. If a name is not specified, a default name of Par <4 digit nPartition number> is given to the nPar.
A partition name should have at least one of the following non-numeric characters:
◦ a-z
◦
A-Z
◦
- (dash)
◦
_ (underscore)
◦
. (period)
Any other non-numeric character is not allowed in a partition name. The name for the nPar should be specified either using –p or –P option.
IMPORTANT: Attempts to specify a name using both the –p and –P options in the same command line will be considered invalid.
A partition name with the same format as the default name can only be specified if the specified name matches the nPar number.
Specifies the amount of non-interleaved memory per socket for all blades in the nPartition. The slm value specified with –c or –a option takes precedence over the –L option. The default memory settings depends on the OS type specified by the user through –o option.
Creates an nPartition from a partition specification. On successful nPartition creation, a parspec specified with
-z option is made the current parspec for the nPartition.
When the -z option is not specified, a default parspec in the format ps<4digit nPartition number> is created and made the current parspec. If a parspec with the same name exists, it is overwritten.
A parspec name with the same format as the default name can only be specified if the specified name matches the nPar number. When this option is specified, any other option specifying resource assignments or nPartition attributes is not allowed.
Specify the OS to be used in the nPartition. This is used to determine the default values for certain firmware settings and memory settings.
IMPORTANT: Booting a different OS than the one specified could result in the OS failing to boot or in the
OS not behaving properly once booted.
The valid strings for OS names are the following:
◦
HPUX_11iV3 (default)
Creates an partition specification only. The create_nPar_flag can have y or n values. If y is used, the corresponding nPar itself is created. The default value of create_nPar_flag is n and no nPar is created.
NOTE:
-Z and -C are mutually exclusive.
130 Partition commands
Option
[-T flag]
[-G memory_granularity_type]
[-n res_type:IA_value]
[-p nPartitionId]
[-M type:max_value]
[-N mode]
[-X parspec:[change_policy]]
Meaning
Specifies whether Hyper-Threading should be enabled or not. The valid values for flag are:
◦ y — enables Hyper-Threading, which allows multiple threads to run concurrently on each CPU.
◦ n — disables Hyper-Threading, this is the default value.
Specifies the memory granularity (ILM or SLM) in MB for the nPartition. If this option is not specified, the default granularity chosen will be 1024 MB. The minimum memory granularity supported is 256 MB
Specifies the Intended Active value of the resource type for the nPartition. The valid value for res_type is case-insensitive core. The ia_value has to be a positive number which will be passed to the iCAP software as a hint requested by the user as the Intended Active value for activation in the nPartition.
Specify an optional nPartition number or name for the nPartition. The nParition id can be specified as an nParition number or an nPartition name. If the specified nPartitionId has only numeric characters, it is considered an nPartition number. If an nPartition name is provided, it should have at least one of the following non-numberic characters
◦ a-z
◦
A-Z
◦
- (dash)
◦
_ (underscore)
◦
. (period)
Any other non-numeric character is not allowed in a partition name.
If the –p option is not specified, an nPar number is automatically assigned to the created nPartition. If –P
<name> is also not specified, a default name in the format nPartition<4 digit nPartition num> is given to the nPar.
User specified max value for blades or vPars in an nPar.
The nPar will not be allowed to have more than the max_value for the type specified.
Specifies whether the hard partition has to be booted as a single nPar or as one or more vPars as defined in the vpdb in the parspec. The valid values for mode are case-insensitive vPars and nPars. By default, a hard partition is booted as a single nPar.
Sets the parspec change policy. The change policy has values of enable and disable. By default, the policy is enable. If the policy is set to enable, partition management software modifies parspecs to reflect the resource assignment changes done to the partition at boot time. If policy is set to disable, partition management software fails the boot if any of the
PARCREATE 131
Option
[-V flag]
Meaning requested resources specified in the parspec is not available for assignment to the partition at boot time.
Enable/Disable VGA in an nPartition. The flag value can be either enable or disable. By default, VGA is enabled in an nPartition. VGA is always disabled when running vPars in an nPar.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
PARMODIFY
•
Command: parmodify -p nPartition_id | -Z parspec_name
{[-a blade:blade_path:[blade_type]:[use_on_next_boot]:
[failure_usage]:[slm_value]]...
[-a io:iobay_path:[use_on_next_boot][:failure_usage]]...
[-c new_parspec_name]
[-d blade:blade_path]...
[-d io:iobay_path]...
[-m blade:blade_path:[blade_type]:[use_on_next_boot]:
[failure_usage]:[slm_value]]...
[-m io:iobay_path:[use_on_next_boot][:failure_usage]]...
[-n res_type:ia_value]
[-B ]
[-G memory_granularity_type:size]
[-L slm_value]
[-M type:max_value]
[-N next_boot_mode]
[-O os_name]
[-P new_nPartition_name]
[-T hyper_threading_flag]
[-V vga_flag]
[-X parspec:change_policy_flag]}
•
Description:
Modifies the attributes of an existing nPartition or a partition specification. This command can modify the following attributes:
◦ nPartition name
◦
VGA assignment
◦
Next boot mode
◦
Partition Specification
◦
Blade assignment
◦
Attributes of existing blades
◦
IO bay assignment
◦
Attributes of existing IO bays
132 Partition commands
The options for the command:
Option
[-p nPartitionId]
[-a [blade:blade | io:io_bay]]
[-m [blade:blade | io: io_bay]]
[-d [blade:blade | io: io_bay]]
[-B]
[-P name
]
[-L slm_value
]
[-Z parspecname]
Meaning
The nPartition to modify. The nPartition id can be specified as an nPartition number or an nPartition name.
If the specified nPartitionId has only numeric characters, it is considered as an nPartition number. If an nPartition name is provided, it should have at least one of the following non-numeric characters
◦ a-z
◦
A-Z
◦
- (dash)
◦
_ (underscore)
◦
. (period)
Any other non-numeric character is not allowed in an nPartition name.
Add a blade or I/O resource to the nPartition.
Modify the attributes of the blade(s) or I/O resource(s) in the specified nPartition.
Delete the specified blade(s) or I/O resources from the nPartition. If the blade which is being deleted is an active blade then after the execution of the parmodify command the user must reboot the nPartition for the change to take place. If the nPartition is running vPars, individual vPars have to be shutdown and the nPartition rebooted for the change to take effect.
If the partition is inactive, specify that the nPartition be booted.
Specifies a new name for the nPartition. An nPartition name, should have at least one of the following non-numeric characters:
◦ a-z
◦
A-Z
◦
- (dash)
◦
_ (underscore)
◦
. (period)
Any other non-numeric character is not allowed in an nPartition name.
Specifies the amount of non-interleaved memory per socket
The partition specification to modify. When this option is specified all other command options are applied to the specified parspec and not to any nPartition. The –p and –z options are mutually exclusive. The –z option applies only to alternate parspecs. When –p option is specified, the current parspec for the nPartition gets modified.
PARMODIFY 133
Option
[-O osname]
[-T flag]
[-a res_type:ia_value]
[-G memory_granularity_type]
[-A parspecname]
[-M type:max_value]
[-N mode]
[-X parspec:[change_policy]]
[-V flag]
[-c copy_parspec_name]
Meaning
Specify the OS to be used in the nPartition. This is used to determine the default values for certain firmware and memory settings. The valid strings for OS names are:
◦
HPUX_11iV3 (default)
Specifies whether Hyper-Threading should be enabled or not. The valid values for flag are:
◦ y — Enables Hyper-Threading, which allows multiple threads to run concurrently on each CPU.
◦ n — Disables Hyper-Threading, this is the default value.
Changes the Intended Active value of the resource type for the nPartition. The valid value for res_type is case-insensitive core. The ia_value has to be a positive number which will be passed to the iCAP software as a hint requested by the user as the Intended
Active value for activation in the nPartition.
Specifies the memory granularity (ILM or SLM) for the nPartition
The partition specification to switch to at the next boot.
This option can be specified for a nPartition and will result in the configuration (assigned resources and other attributes) of the nPartition being changed to match what is specified in this parspec when the nPartition is activated after a reset.
IMPORTANT: No other option except –p is allowed when –A is specified.
The max value for blades or vPars in an nPar. The nPar will not be allowed to have more than the max_value for the type specified.
Specifies whether the hard partition has to be booted as a single nPar or as one or more vPars as defined in the vpdb in the parspec. The valid values for mode are case-insensitive vPars and nPars. By default, a hard partition is booted as a single nPar.
Sets the parspec change policy. The change policy has values of enable and disable. By default, the policy is enable. If the policy is set to enable, partition management software modifies parspecs to reflect the resource assignment changes done to the partition at boot time. If policy is set to disable, partition management software fails the boot if any of the requested resources specified in the parspec is not available for assignment to the partition at boot time.
Enable/Disable VGA in an nPartition. The flag value can be either enable or disable. By default, VGA is enabled in an nPartition. VGA is always disabled when running vPars in an nPar.
Create a copy of an existing parspec. The source parspec can be specified using the –z or –p options.
If the –p option is specified, the current parspec of the nPartition specified by –p is selected as the source. The copy is given the name specified by
copy_parspec_name
and is marked as an alternate parspec.
134 Partition commands
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
◦
You must be connected to the monarch OA.
PARREMOVE
•
Command: parremove
{-p nPartitionId }
[-F]
[-Z [parspecname]]
•
Description:
Deletes a partition on a local or remote complex. If the partition is active, you must shut down the OS after executing parremove. All cells and I/O chassis that had been assigned to the nPartition become free resources available for assignment to other nPartitions.
The options for the command:
Option
{-p PartitionNumber}
-F
[-Z [parspecname]]
Meaning
The partition to remove. The nPartition id can be specified as an nPartition number or an nPartition name.
Forcibly remove a partition.
This option is required in the following instances:
◦
You are removing your own local partition.
◦
You have vPars defined (active or inactive) in your nPartition independent of the mode (nPars or vPars) in which the nPartition is.
Removes the current parspec associated with the nPar. If a parspecname is specified along with –z, the specified parspec is removed. If you attempt to remove a current parspec, an error is returned.
IMPORTANT:
–z parspecname and –p are mutually exclusive options.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
◦
You must be connected to the monarch OA.
PARSTATUS
•
Command: parstatus parstatus {-C }
[-A]
[-M] parstatus {-E}
[-M] parstatus {-I}
PARREMOVE 135
[-A]
[-M] parstatus {-P}
[-Z]
[-v]
[-M] parstatus {-i IOresource}...
[-M] [-V] parstatus {-c blade }} ...
[-M] [-V] parstatus {-e enclosure }}...
[-M] [-V] parstatus {-p nPartitionId}…
[-v]
[-z]
[-Z]
[-M]
[-V]
[-T] parstatus {-Z parspecName}… parstatus {–s } parstatus {-w
[-M] } parstatus {-S} parstatus {–X} parstatus {-r} parstatus {-L} parstatus {-T}
[-M]
•
Description:
Displays information about a system complex. If no arguments are supplied, all major components that are physically present in the system complex are listed. A specific component
(blade, I/O bay, enclosure, or nPartition) can be specified in order to restrict the output information about that component.
NOTE: parstatus output is limited to 80 columns, and as a result, some output may be truncated. Use the verbose option in such cases to view the detailed information if necessary.
The options for the command:
Option
{-p nPartitionId}
-P
{-c blade}
-C
{-e enclosure}
-E
136 Partition commands
Meaning
Displays information about the specified nPartition(s). The nPartition id can be specified as an nPartition number or an nPartition name.
Displays information for all nPartitions in the complex.
Displays information about the specified blade(s).
Displays information for all blades in the complex.
Displays information about the specified enclosures(s).
Displays information for all enclosures in the complex
Option
{-i IOresource]
-I
[-s]
[-w]
[-X]
[-A]
[-M]
[-V]
[-T]
[-z]
[-Z]
[-V]
[-r]
[-t]
Meaning
Displays information for specified I/O resource.
Displays information for all I/O resources in the complex including I/O on blades.
Quiet mode. Returns a success or failure status indicating if the hardware supports partitioning
Displays the local nPartition number and name in a verbose fashion. The -M option restricts the display to just the nPartition number.
Displays the attributes of the complex
Only display the available resources in the complex.
Displays a machine readable/parsable output. The machine readable output will have the columns separated by a single colon character (:) and will not have a column header.
NOTE: The -M and -V options are mutually exclusive.
Verbose mode.
Displays the Hyper-Threading information.
Used with –p to display the current partition specification name associated with the nPartition
Displays the contents of the specified partition specification.
NOTE: When a current parspec is examined with the
-Z option, the information provided will be what is stored in the parspec. It should not be expected to be identical to information gathered from the associated nPartition.
Used with –p to display the vPar names associated with the nPartition.
Displays the revisions of partition management tools.
Displays physical location, status, and resource path information for all resources in an nPar as a tree.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
◦
You must be connected to the monarch OA.
•
Example: parstatus
Note: No action specified. Default behavior is display all.
[Complex]
Complex Name: Complex1
Complex UUID: Unset
Complex Capacity
Compute Enclosure: 1
IO Enclosure: 1
Monarch OA Location: 1
Model: N/A
Original Serial Number: Unset
PARSTATUS 137
Current Product Order Number: AH337A
OEM Manufacturer: N/A
Total number of partitions present: 1
[Enclosure]
Enclosure Enclosure Num Num Bay Enclosure
Num Type Blades IOBays Slots Name
========= ========= ====== ====== ===== =========
1 Compute 8 0 8 -
5 IO 0 2 2 -
[Blade]
Hardware Usage/ CPU Memory Use Par
Location Status OK/ (GB) On Num
Indicted/ OK/ Next
Deconf/ Indicted/ Boot
Max Deconf
======== ======================= ========= =============== ==== ===
1/1 Inactive Base /OK 8/0/0/8 16.0/0.0/0.0 yes 4
1/2 Absent /Invalid 0/0/0/0 0.0/0.0/0.0 yes -
1/3 Absent /Invalid 0/0/0/0 0.0/0.0/0.0 yes -
1/4 Absent /Invalid 0/0/0/0 0.0/0.0/0.0 yes -
1/5 Absent /Invalid 0/0/0/0 0.0/0.0/0.0 yes -
1/6 Absent /Invalid 0/0/0/0 0.0/0.0/0.0 yes -
1/7 Absent /Invalid 0/0/0/0 0.0/0.0/0.0 yes -
1/8 Absent /Invalid 0/0/0/0 0.0/0.0/0.0 yes -
* D-Deconfigured I-Indicted PD-Parent Deconfigured PI-Parent Indicted
[IOBay]
Hardware Usage/ Par
Location Status Num
======== ======================= ===
5/1 Inactive /OK 4
5/2 Inactive /OK -
6/1 Absent /Invalid -
6/2 Absent /Invalid -
7/1 Absent /Invalid -
7/2 Absent /Invalid -
8/1 Absent /Invalid -
8/2 Absent /Invalid -
9/1 Absent /Invalid -
9/2 Absent /Invalid -
10/1 Absent /Invalid -
10/2 Absent /Invalid -
11/1 Absent /Invalid -
11/2 Absent /Invalid -
12/1 Absent /Invalid -
12/2 Absent /Invalid -
* D-Deconfigured I-Indicted PD-Parent Deconfigured PI-Parent Indicted
[Partition]
Par State/ Status* # of # of ILM/ Partition Name
Num RunState Blades IOBays SLM
(GB)**
=== ======================= ======= ====== ====== =========== =================
4 Inactive /DOWN OK 1 1 11.2/3.8 -
* D-Degraded
** Actual allocated for Active and User requested for Inactive partitions
138 Partition commands
POWEROFF PARTITION
•
Command:
POWEROFF PARTITION {{<nPar ID>} [:<vPar ID>] [FORCE] [OVERRIDE]
| ALL [FORCE] }
•
Description:
◦
Gracefully shuts down any OS running on the specified nPartition or virtual partition and brings it to an inactive state. The active blades and IO interconnects in the nPartition are powered off if the target specified is an nPartition.
◦
The OVERRIDE argument shuts down all virtual partitions in the specified nPartition.
◦
The FORCE argument shuts down the specified partition ungracefully. If an OS is running in the partition, then the FORCE argument is required to power off the partition without trying to bring down the OS gracefully.
CAUTION: The POWEROFF PARTITION ALL command requires the FORCE argument and ungracefully shuts down all partitions. This can cause a partition to lose data and possibly become unstable.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
◦
nPar ID
and vPar ID can either be the name or number of the nPartition or virtual partition.
◦
You must be connected to the monarch OA.
POWERON PARTITION
•
Command:
POWERON PARTITION {{<nPar ID>} [:<vPar ID>]} [OVERRIDE]
•
Description:
◦
If an nPartition is specified, then this command powers on the blades and I/O interconnects in the nPartition and boots the nPartition to UEFI. If the nPartition is in vPars mode and has vPars defined, then all the defined vPars in the nPartition are booted to UEFI. If an individual vPar is specified, it is booted to UEFI.
◦
If the nPartition is in nPars mode and a vPar is specified to be powered on, then the
OVERRIDE
argument changes the mode of the nPartition to vPars, powers on the nPartition and boots the specified vPar.
◦
If the nPartition is in vPars mode and has no vPars defined, then the nPartition is powered on to reach an active state. After the nPartition is active, new vPars can be created and individually powered on to reach UEFI.
POWEROFF PARTITION 139
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
◦
nPar ID
and vPar ID can either be the name or number of the nPartition or virtual partition.
◦
You must be connected to the monarch OA.
REBOOT PARTITION
•
Command:
REBOOT PARTITION {{<nPar ID>} [:<vPar ID>]} [FORCE] [OVERRIDE]
•
Description:
◦
Reboots the OS on the specified nPartition or virtual partition.
◦
The FORCE argument ungracefully reboots the OS in the specified partition.
◦
The OVERRIDE argument reboots all virtual partitions on the specified nPartition.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
SET PARTITION DVD
•
Command:
SET PARTITION DVD { CONNECT | DISCONNECT } { nPartition number or name } [ :vPartition number or name ]
[ ENCLOSURE { enclosure number } ]
•
Description:
Connect or disconnect the DVD module to the specified partition.
The DVD module of the compute enclosure containing the primary blade of the partition is the
DVD module that is connected to the partition.
IMPORTANT: Before connecting a DVD to a virtual partition, the iLO rootport (or ioslot) from any of the blades in the nPartition must be assigned to the target virtual partition.
For information on partition management, see the HP Integrity Superdome 2 Partitioning
Administrator Guide.
NOTE: The DVD module is disconnected from a partition when the partition or the OA is shut down or rebooted.
•
Access level/Bay level:
OA Administrator, OA Operator
140 Partition commands
•
Restriction:
◦
You must be connected to the monarch OA.
◦
In multi-enclosure systems, the enclosure number the DVD drive is installed can be specified as an optional argument. If no enclosure number is specified, the DVD drive from the local enclosure is used.
•
Example:
CLI> set partition dvd connect 1
Partition 1 has been connected to the DVD drive in enclosure 1.
CLI> set partition dvd connect 1:1
Partition 1:1 has been connected to the DVD drive in enclosure 1.
CLI> set partition dvd connect nPar001 enclosure 2
Partition 1 has been connected to the DVD drive in enclosure 2.
CLI> set partition dvd disconnect 1
Partition 1 has been disconnected from the DVD drive in enclosure 1.
CLI> set partition dvd disconnect 1:1
Partition 1:1 has been disconnected to the DVD drive in enclosure 1.
CLI> set partition dvd disconnect nPar001 enclosure 2
Partition 1 has been disconnected from the DVD drive in enclosure 2.
NOTE: The SET PARTITION DVD command is not applicable to HP Integrity Superdome 2 server blades. It can only be issued against partitions
SHOW PARTITION DVD
•
Command:
SHOW PARTITION DVD { nPartition number or name [ :vPartition name or number ] | ALL }
•
Description:
Displays information about the DVD drive attached to the specified partition.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
•
Example:
CLI> show partition dvd all
Enclosure 1 DVD Drive: Present DVD Media: Present
Enclosure 2 DVD Drive: Present DVD Media: Absent
Partition DVD connections:
ParNum Partition Name Connected Enclosure
------ -------------- --------- ---------
1 Npar001 Yes 1
1 Npar001 No 2
CLI> show partition dvd all
Enclosure 1 DVD Drive: Present DVD Media: Present
Enclosure 2 DVD Drive: Present DVD Media: Absent
Partition DVD connections:
ParNum Partition Name Connected Enclosure
------ -------------- --------- ---------
SHOW PARTITION DVD 141
1 Npar001 Yes 1
1 Npar001 No 2
2 Backup No 1
3:1 vpar0301 - No iLO available
3:2 vpar0302 - [Virtual Media Applet is in use.]
3:3 vpar0303 - Partition is not Active
4 money_maker Yes 2
NOTE: The SET PARTITION DVD command is not applicable to HP Integrity Superdome 2 server blades. It can only be issued against partitions
SHOW PARTITION INFO
•
Command:
SHOW PARTITION INFO { nPartition name or number [ :vPartition name or number ] | ALL }
•
Description:
Displays information about the specified partitions.
NOTE: Use Verbose mode (–v option) for additional partition information
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
•
Example: festival-oa> show partition info all
[Partition]
Par Status/ Health* # of # of ILM/ Partition Name
Num RunState Blades IOBays SLM
(GB)**
=== ======================= ======= ====== ====== =========== =================
1 Active /EFI OK 1 0 7.0/0.0 -
2 Active /EFI OK 1 0 7.0/0.0 -
* D-Degraded
** Actual allocated for Active and User requested for Inactive partitions
[Partition]
Partition Number : 1
Partition Name : vPar Num vPar Name
========= ==============================
1 partition1
[Partition]
Partition Number : 2
Partition Name : vPar Num vPar Name
========= ==============================
1 partition2
142 Partition commands
TOC PARTITION
•
Command:
TOC PARTITION {<nPar ID>} [:<vPar ID>]} [OVERRIDE]
•
Description:
◦
Performs a transfer-of-control reset of the specified nPartition or virtual partition.
◦
The OVERRIDE argument TOC resets all virtual partitions on the specified nPartition.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
PARDEFAULT
•
Command: pardefault [–t target_os]
[–O osname]
[–L slm_value]
[–G memtype:size]
[–T hyper_thread_flag]
[–V flag]
[-R target_os]
•
Description:
Changes the current default values of certain generic nPartition attributes or attributes specific to an OS type.
◦
Pardefault without any options will display the original and current default settings.
◦
Pardefault with only –t option will display the original and current default settings for the target_os.
The options for the command:
Option
[-t target_os]
[-O osname]
[-L slm_value]
Meaning
Specify the OS type for which the default has to be changed. Valid strings for target_os are same as that for parcreate command The defaults specified using the remaining options (except –O) of this command will be applied to any nPartition created subsequently with this
OS type. If the -t option is not specified, the default value is changed for all subsequently created nPartitions independent of the OS type. The –t and –O options are mutually exclusive.
Specify the value for OS type that needs to be the default OS type when nPartitions are created. This is applied to any subsequent nPartition that is created. The
–t and –O options are mutually exclusive. Note that –t is used as a target OS type for which the defaults are to be set whereas –O is used to set the default OS type to be used when any partition is created.
Specifies the default value for the amount of non-interleaved memory per socket for all blades in an nPartition.
TOC PARTITION 143
Option
[-T flag]
[-G memtype:size]
[-V flag]
[-R target_os]
Meaning
Specifies the default setting for Hyper-Threading in an nPartition. The valid values for flag are:
◦ y — enables Hyper-Threading, which allows multiple threads to run concurrently on each CPU.
◦ n — disables Hyper-Threading, this is the default value.
Specifies the default value for memory granularity (ILM or SLM) for an nPartition.
Specifies the default of VGA. The flag value can be either “enable” or “disable”.
Target_os is the name of the OS type whose defaults are to reset. If no target_os is provided, all defaults will be reset to their original default.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
PARPERM
•
Command: parperm scope {ON|OFF} nParId[:vParId]
•
Description:
Changes the authorizations for an OS running in an nPar or vPar.
◦
Off — An OS can only request information using status commands (unrestricted) and can perform operations that only affect the partition that the OS is running in. This is the default option.
◦
On — An OS has authorization to perform partition configuration operations affecting other partitions.
Scope can be set to either npar or vpar. When the scope specified is vpar, the target partition has authorization to perform vpar operations within the npar to which it belongs.
When the scope specified is npar, the target partition has authorization to perform any npar operations within the complex.
NOTE:
vpar
scope is only applicable to a vpar partition. For npar scope, the target partition can be either an nPartition or a vPar.
Parperm without any options will display the current permission specified on the OA.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
144 Partition commands
VPARCREATE
•
Command: vparcreate [-p vparidentstr] [-a rsrc]... [-Z parspecname] [-N nparidentstr] [-P vp_name]
•
Description:
Creates a new virtual partition using the specified hardware resources. If a virtual partition number is not specified, the command finds an available virtual partition number and assigns it to the new virtual partition. Likewise, if a virtual partition name is not specified, a default name of the format vParNNNN is given to the new virtual partition.
The options for the command:
Option
-p vparidentstr
-a rsrc
-Z parspecname
-N nparidentstr
Meaning
Specifies the virtual partition to be created in ASCII format either as a name or number. The vparidentstr can also be specified in the format nparidentstr:vparidentstr
. When specified in the format of nparidentstr:vparidentstr, nparidentstr and vparidentstr can either be a name or number. When specified from the OA, the vPar should be identified using the format nparidentstr:vparidentstr or used along with the –N option. A partition name should at least have one of the following non-numeric characters:
◦ a-z
◦
A-Z
◦
- (dash)
◦
_ (underscore)
◦
. (period)
If a -p <number> option is not specified, a vPar number is automatically assigned to the created virtual partition. If both and –p <name> and –P are not specified, a vPar name in the format <vPar.vPar_num> is automatically assigned to the created virtual partition.
NOTE: The name for the vPar should be specified either using –p <name> or –P . Attempts to specify the vPar name using both options in the same command line will be considered invalid.
Specifies resources to be added to the virtual partition.
Specifies the parspec of the nPar in which the vPar will be created. When this option is specified all other command options are applied to the specified parspec and not to the nPartition itself. The –n and –z options are mutually exclusive.
NOTE: When the command is invoked from the OA with –z option, there is no need of a –n option, since the operation is being applied to a vPar in the parspec and not to an existing nPar.
Specifies the nPar to which the vPar belongs to in ASCII format either as a name or number. This option is mandatory for a command invoked from OA which that not specify –z. For commands invoked from the partition, behavior is to create the vPar in that nPar, if
VPARCREATE 145
Option
-P vp_name
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
VPARBOOT
•
Command:
vparboot { -p vpar_id -N npar_id | -p npar_id:vpar_id }
•
Description:
The vparboot command boots the specified virtual partition. The virtual partition must exist and be in the DOWN run-state. The nPartition containing the virtual partition to be booted must either be booted in vPars mode or inactive with the next boot mode as vPars.
No boot related options other than virtual partition name/number and nPar name/number are supported.
The options for the command:
Option
-p vparidentstr
Meaning
Specifies the virtual partition to be created in ASCII format either as a name or number. It can also be specified in the format nparidentstr:vparidentstr
. When specified in the format of nparidentstr:vparidentstr, nparidentstr and vparidentstr can either be a name or number. When specified from the OA, the vPar should be identified using the format nparidentstr:vparidentstr or used along with the –N option. A partition name should at least have one of the following non-numeric characters:
◦ a-z
◦
A-Z
◦
- (dash)
◦
_ (underscore)
◦
. (period)
If a -p <number> option is not specified, a vPar number is automatically assigned to the created virtual partition. If both and –p <name> and –P are not
146 Partition commands
Meaning
–n is not specified. –z and –n are mutually exclusive.
The default parspec is modified with the –n option.
Specifies a name for the new virtual partition. The name for the vPar should be specified either using the –p
<name>
or –P options. Attempts to specify the vPar name using both the –p <name> and –p options in the same command line will be considered invalid.
A partition name with the same format as the default name can only be specified if the specified name matches the vPar number.
Option
-N nparidentstr
Meaning specified, a vPar name in the format <vPar.vPar_num> is automatically assigned to the created virtual partition.
NOTE: The name for the vPar should be specified either using –p <name> or –P . Attempts to specify the vPar name using both options in the same command line will be considered invalid.
Specifies the nPar to which the vPar belongs to in ASCII format either as a name or number. This option is mandatory for a command invoked from OA which that not specify –z. For commands invoked from the partition, behavior is to create the vPar in that nPar, if
–n is not specified. –z and –n are mutually exclusive.
The default parspec is modified with the –n option.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
VPARMODIFY
•
Command: vparmodify { -p vpar_id -N npar_id | -p npar_id:vpar_id }
[-a rsrc]...
[-d rsrc]...
[-m rsrc]...
[-P new_vpname]
•
Description:
Modifies the resources of the specified virtual partition. The command can also rename the virtual partition.
The options for the command:
Option
-p vparidentstr
-a rsrc
-m rsrc
-d rsrc
-P new_vp_name
Meaning
Specifies the target virtual partition. The vparidentstr can be specified in ASCII format as a vPar number or a vPar name, or in the format
nparidentstr:vparidentstr
. When specified in the format nparidentstr:vparidentstr,
nparidentstr
and vparidentstr can either be a name or number.
NOTE: When executed from the OA, the vPar should be identified using the format
nparidentstr:vparidentstr
or used along with the –N option.
Specifies resources to be added to the virtual partition.
Specifies resources to be modified in the virtual partition.
Specifies resources to be deleted from the virtual partition.
Specifies a new name for the virtual partition.
VPARMODIFY 147
Option
-Z parspecname
-N nparidentstr
Meaning
Specifies the parspec of the nPar in which the vPar is to be modified. When this option is specified all other command options are applied to the specified parspec and not to any partition.
NOTE: The –N and –Z options are mutually exclusive.
Specifies the nPar to which the target vPar belongs. This option is mandatory if the command invoked from OA.
For commands invoked from the partition, the command will modify the vPar in that nPar if –n is not specified.
The nparidentstr can be specified as an nPar name or nPar number.
NOTE: The –N and –Z options are mutually exclusive.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
VPARRESET
•
Command: vparreset -p vparidentstr[-h|-t]] [-f] [-N nparidentstr]
IMPORTANT: The -N option is mandatory when the command is invoked from the OA, it is optional when the command is invoked from the OS running on the nPar
•
Description:
The vparreset command simulates, at the virtual partition level, the hard reset (ReSet, RS) and soft reset (Transfer Of Control, TOC) operations supported by server management processor commands.
IMPORTANT: Unintentional use of the vparreset command has serious consequences.
Therefore, the operation must be confirmed using the -f (force) option.
The options for the command:
Option
-p vparidentstr
-t
-h
Meaning
Specifies the target virtual partition. The vparidentstr can be specified in ASCII format as a vPar number or a vPar name, or in the format
nparidentstr:vparidentstr
. When specified in the format nparidentstr:vparidentstr,
nparidentstr
and vparidentstr can either be a name or number.
NOTE: When executed from the OA, the vPar should be identified using the format
nparidentstr:vparidentstr
or used along with the –N option.
Simulates a TOC reset
Simulates a hard (RS) reset.
148 Partition commands
Option
-f
-N nparidentstr
Meaning
The force option, this option is required and is used as confirmation before resetting the virtual partition.
NOTE: On Superdome 2, the force option is mandatory.
Specifies the nPar to which the target vPar belongs. This option is mandatory for a command invoked from OA.
If the command is invoked from the partition, it will reset the vPar in that nPar. If the –N option is not specified.
nparidentstr
can be specified as an nPar name or nPar number.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
VPARREMOVE
•
Command: vparremove -p vparidentstr [-f] [-N nparidentstr] [-Z parspecname]
IMPORTANT: The -N option is mandatory when the command is invoked from the OA. It is optional when the command is invoked from the OS running on the nPar
•
Description:
Deletes a virtual partition previously created using the vparcreate command. All resources associated with the virtual partition are made available for allocation to other partitions.
The options for the command:
Option
-p vparidentstr
-f
-Z parspecname
-N nparidentstr
Meaning
Specifies the target virtual partition. The vparidentstr can be specified in ASCII format as a vPar number or a vPar name, or in the format
nparidentstr:vparidentstr
. When specified in the format nparidentstr:vparidentstr,
nparidentstr
and vparidentstr can either be a name or number.
NOTE: When executed from the OA, the vPar should be identified using the format
nparidentstr:vparidentstr
or used along with the –n option.
The force option, this option is required and is used as confirmation before removing the virtual partition.
Specifies the parspec of the nPar in which the vPar is to be removed. When this option is specified all other command options are applied to the specified parspec and not to any partition.
NOTE: The –n and –z options are mutually exclusive.
Specifies the nPar to which the target vPar belongs. This option is mandatory for a command invoked from OA.
If the command is invoked from the partition, it will
VPARREMOVE 149
Option Meaning remove the vPar in that nPar. If the –n option is not specified. nparidentstr can be specified as an nPar name or nPar number.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
VPARSTATUS
•
Command: vparstatus [-v | -M] [-p vparidentstr]...
[-N nparidentstr] vparstatus [-N nparidentstr] vparstatus [-Z parspecname] vparstatus -A [-M] [-p vparidentstr] [-N nparidentstr] vparstatus {-d [cpu_path]}... [-v | -M] [-N nparidentstr] vparstatus -w [-M] vparstatus –r [-M]
IMPORTANT: The -N option is mandatory when the command is invoked from the OA. It is optional when the command is invoked from the OS running on the nPar
•
Description:
Displays information about one or more virtual partitions.
The options for the command:
Option
-p vparidentstr
-d [cpu_path]
-v
-A
-M
Meaning
Specifies the target virtual partition. The vparidentstr can be specified in ASCII format as a vPar number or a vPar name, or in the format
nparidentstr:vparidentstr
. When specified in the format nparidentstr:vparidentstr,
nparidentstr
and vparidentstr can either be a name or number.
NOTE: When executed from the OA, the vPar should be identified using the format
nparidentstr:vparidentstr
or used along with the –n option.
Displays configuration information for CPUs in the nPar.
Detailed display of information.
Displays information about available resources
Displays attribute and resource information in a machine-readable format.
Displays the local virtual partition name.
-w
150 Partition commands
Option
-Z parspecname
-N nparidentstr
-r
Meaning
Specifies the partition specification from which the virtual partition database has to be chosen.
NOTE: When a current parspec is examined with the
-Z option, the information provided will be what is stored in the parspec. It should not be expected to be identical to information gathered from the associated nPartition.
NOTE: The –N and –Z options are mutually exclusive.
Specifies the nPar to which the target vPar belongs. This option is mandatory for a command invoked from OA.
If the command is invoked from the partition, it will remove the vPar in that nPar. If the –n option is not specified. nparidentstr can be specified as an nPar name or nPar number.
Displays the revisions of partition management tools.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restriction:
You must be connected to the monarch OA.
•
Example: vparstatus
Note: No action specified. Default behavior is to display all.
[Virtual Partition]
Num Name RunState State
=== ========================== ========= =========
1 vpolya01 EFI Active
[Virtual Partition Resource Summary]
Virtual Partition CPU Num Num Granularity Total MB
Num Name Min/Max CPUs IO ILM LM ILM LM
=== ========================== ======= ==== ==== ===== ===== ===== =====
1 vpolya01 1/ 8 6 4 1024 1024 4096 1024
VPARSTATUS 151
22 Log viewer commands
CLEAR FPL
CAUTION: You cannot restore this information after you delete it.
•
Command:
CLEAR FPL
•
Description:
Clears the Forward Progress Log.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
CLEAR SEL
CAUTION: You cannot restore this information after you delete it.
•
Command:
CLEAR SEL
•
Description:
Clears the System Event Log.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
CLEAR PARTITION CONSOLELOG
CAUTION: You cannot restore this information after you delete it.
•
Command:
CLEAR PARTITION CONSOLELOG {<nPar ID>[:<vPar ID>]}
•
Description:
Clears the console log for the specified partition.
For information on partition management, see the HP Integrity Superdome 2 Partitioning
Administrator Guide.
•
Access level/Bay level:
Administrator, Operator
•
Restrictions:
You must be connected to the monarch OA.
152 Log viewer commands
CONNECT PARTITION
•
Command:
CONNECT PARTITION [VIEWONLY] {<nPar ID>[:<vPar ID>]}
•
Description:
Connects to the text console for the specified partition.
The VIEWONLY argument connects as a user with read-only access.
•
Access level/Bay level:
Administrator, Operator
•
Restrictions:
◦
The nPar ID and vPar ID values can either be the name or number of the nPartition or virtual partition.
◦
You must be connected to the monarch OA.
SHOW FPL
•
Command:
SHOW FPL
•
Description:
Launches the Forward Progress Log viewer.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
SHOW LIVELOGS
•
Command:
SHOW LIVELOGS
•
Description:
Launches the live Event Log Viewer.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
SHOW PARTITION CONSOLELOG
•
Command:
SHOW PARTITION CONSOLELOG {<nPar ID>[:<vPar ID>]}
•
Description:
◦
Launches the Console Log Viewer for the specified partition.
◦
For information on partition management, see the HP Integrity Superdome 2 Partitioning
Administrator Guide.
CONNECT PARTITION 153
NOTE: To view the entire Console Log while in the Console Log Viewer, first enter g followed by 2200000 (the maximum size of a Console Log).
•
Access level/Bay level:
All
•
Restrictions:
◦
The nPar ID and vPar ID values can either be the name or number of the nPartition or virtual partition.
◦
You must be connected to the monarch OA.
SHOW SEL
•
Command:
SHOW SEL
NOTE: The legacy command SEL is a valid alias for SHOW SEL.
•
Description:
Launches the System Event Log viewer.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA.
154 Log viewer commands
23 Health Repository commands
HP Integrity Superdome 2 complexes use the HP Integrity Superdome 2 Analysis Engine to provide error handling, logging, analysis and reporting. The Health Repository is one component of the
Analysis Engine that you use to access current state and history of error events and service events for components in the complex.
The Health Repository viewer is a separate user interface that you launch with the SHOW HR command that remains active until closed by the QUIT or EXIT commands.
The Health Repository viewer presents a specific prompt in the format:
<date><time><hostname>HR>
The following information is available in the Health Repository viewer:
•
Descriptions of each component failure event (called indictments) in the complex
•
History of components installed in the complex, listed by date/time of installation and identity of the component
ACQUIT
•
Command:
ACQUIT <physical location>
•
Description:
Manually acquits a specified component.
•
Access level/Bay level:
All
•
Restrictions:
◦
The <physical location> must be formatted as either an 8-byte hexadecimal integer, or a long or medium hardware resource path string (short form strings are not supported).
◦
Must be in the Health Repository viewer.
DECONFIGURE
•
Command:
DECONFIGURE <physical location>
•
Description:
Manually deconfigures a specified component. The deconfigured component is not used when the nPartition containing the component is restarted.
•
Access level/Bay level:
All
•
Restrictions:
◦
The <physical location> value must be formatted as either an 8–byte hexadecimal integer, or a long or medium hardware resource path string (short form strings are not supported).
◦
Must be in the Health Repository viewer.
ACQUIT 155
DIMMERR
•
Command:
DIMMERR <physical location>
•
Description:
Displays all errors experienced by DIMMs on a specified blade or all errors for a specified
DIMM.
•
Access level/Bay level:
All
•
Restrictions:
◦
The <physical location> must correspond to a DIMM slot or a blade and must be formatted as either an 8–byte hexadecimal integer, or a long or medium hardware resource path string (short form strings are not supported).
◦
Must be in the Health Repository viewer.
•
Example: myhost-HR> dimmerr blade-1/1
DIMM INFO for Cabinet: 1 Board Slot: 1 dimm-1/1/0/1 Location: 1A
Status: OK No Errors Logged.
dimm-1/1/0/2 Location: 2C
Status: OK No Errors Logged.
dimm-1/1/0/3 Location: 3B
Row Bank Col Type Errors First Detected Last Detected
---- ---- --- ---- ------ --------------------- -----------------------------
0 256 0 0 1 Fri Feb 11 18:10:51 2011 Fri Feb 11 18:10:51 2011
dimm-1/1/0/4 Location: 4D
Status: OK No Errors Logged.
dimm-1/1/0/5 Location: 5D myhost-HR>
156 Health Repository commands
NOTE: The DIMM error table for indicted DIMMs is also displayed as part of the output from the show <memory_location> command.
Location Installation/Health History - Mon Feb 14 14:51:46 2011
--------------------------------------------------
FRU Type: Blade DIMM
Location: 0x0100FF0800090A74 enclosure1/blade8/cpusocket0/dimm9
Timestamp: Thu Dec 16 15:20:16 2010
Indictment State: Not Indicted
Requested Deconfig State: Configured
Current Deconfig State: Not available
dimm-1/8/0/9 Location: 9A
Status: OK No Errors Logged.
-- Install History 1 ---
Discovery: Discovery
Timestamp: Thu Feb 10 15:31:11 2011
Serial Num: EA0DB9BF
Parent Serial: MYJ84901ZH
Part Num: 9JSF12872PY
Spare Part Num: 9JSF12872PY
Manufacturer: 2C
Product Name: DDR3 DIMM
DIMM size: 1024 MB myhost-HR>
INDICT
•
Command:
INDICT <physical location>
•
Description:
Manually indicts a specified component
•
Access level/Bay level:
All
•
Restrictions:
◦
The <physical location> value must be formatted as either an 8–byte hexadecimal integer, or a long or medium hardware resource path string (short form strings are not supported).
◦
Must be in the Health Repository viewer.
SHOW ACQUIT
•
Command:
INDICT 157
SHOW ACQUIT
•
Description:
Lists all recently acquitted indicted components for the complex, with the following information:
◦
Component Type
◦
Physical Location
◦
Timestamp of the indictment
◦
Reason for the indictment
◦
State of the component
•
Access level/Bay level:
All
•
Restrictions:
Must be in the Health Repository viewer.
•
Example: myhost HR> show acquit
System Acquittal History - Mon May 18 16:11:28 2009
--------------------------------------------------
FRU Type: Blade DIMM
Location: 0x0100FF0200160A74 enclosure1/blade2/socket0/dimm16
Timestamp: Mon May 18 16:11:19 2009
Reason: 0x0000000000000001
State: Acquitted
FRU Type: CPU Socket
Location: 0x0100FF01FF00FF11 enclosure1/blade1/socket0
Timestamp: Mon May 18 16:11:19 2009
Reason: 0x0000000000000001
State: Acquitted
--- end report --- 2 records shown
SHOW DECONFIG
•
Command:
SHOW DECONFIG
•
Description:
Lists all components that are currently deconfigured or have a pending deconfiguration request, with the following information:
◦
Component Type
◦
Physical Location
◦
Timestamp of the deconfiguration
◦
Indictment state
◦
State of the component
158 Health Repository commands
•
Access level/Bay level:
All
•
Restrictions:
Must be in the Health Repository viewer.
•
Example: myhost HR> show deconfig
System Acquittal History - Mon May 18 16:11:28 2009
--------------------------------------------------
FRU Type: Blade DIMM
Location: 0x0100FF0200160A74
Timestamp: Mon May 18 16:11:19 2009
Indictment State: Indicted
Requested Deconfig State: Configured
Current Deconfig State: Deconfigured
FRU Type: CPU Socket
Location: 0x0100FF01FF00FF11 enclosure1/blade1/socket0
Timestamp: Mon May 18 16:11:19 2009
Indictment State: Indicted
Requested Deconfig State: Configured
Current Deconfig State: Deconfigured enclosure1/blade2/socket0/dimm16
--- end report --- 2 records shown
NOTE: DIMMs may be deconfigured without being indicted. Some faults isolated to CPU sockets or blades may require deconfiguration of whole or portions of memory subsystems. This is accomplished by physically deconfiguring the DIMMs supported by that resource.
SHOW HR
•
Command:
SHOW HR
•
Description:
Launches the Health Repository viewer
•
Access level/Bay level:
All
•
Restrictions:
You must be logged on to the monarch OA to perform this command.
SHOW INDICT
•
Command:
SHOW INDICT
•
Description:
Lists all currently indicted components for the complex, with the following information:
◦
Component Type
◦
Physical Location
◦
Timestamp of the indictment
SHOW HR 159
◦
Reason for the indictment
◦
State of the component
•
Access level/Bay level:
All
•
Restrictions:
Must be in the Health Repository viewer.
•
Example: myhost HR> show indict
System Indictment List - Mon May 18 16:06:03 2009
--------------------------------------------------
FRU Type: Blade DIMM
Location: 0x0100FF0200160A74 enclosure1/blade2/socket0/dimm16
Timestamp: Mon May 18 15:51:12 2009
Reason: 0x0000000000000001
State: Indicted
FRU Type: CPU Socket
Location: 0x0100FF01FF00FF11 enclosure1/blade1/socket0
Timestamp: Mon May 18 16:05:57 2009
Reason: 0x0000000000000001
State: Indicted
--- end report --- 2 records shown
SHOW for the HR
•
Command:
SHOW [FRU] <physical location>
•
Description:
Lists the entire installation and health history of the specified physical location for up to two previous components installed at the specified physical location.
The following information is displayed:
◦
Component Type
◦
Physical Location
◦
Timestamp of the indictment
◦
Reason for the indictment
◦
State of the component
◦
Install history
◦
Indictment/Acquittal history
The FRU argument displays the history of the component installed at the specified physical location, including previous installations of the component, if any. Not all components have information available or only have partial information when using the SHOW FRU command.
•
Access level/Bay level:
All
160 Health Repository commands
•
Restrictions:
◦
The <physical location> value must be formatted as either an 8–byte hexadecimal integer, or a long or medium hardware resource path string (short form strings are not supported).
◦
Must be in the Health Repository viewer.
•
Example: myhost HR> show 0x0100FF01FF00FF11
Location Installation/Health History - Mon May 18 16:15:45 2009
--------------------------------------------------
FRU Type: CPU Socket
Location: 0x0100FF01FF00FF11 enclosure1/blade1/socket0
Timestamp: Mon May 18 16:11:19 2009
Reason: 0x7FE1E7B03000B0C8
State: Acquitted
--- Install History 1 ---
How Found: Indictment
Timestamp: Mon May 18 16:10:38 2009
Serial Num: N/A
Parent Serial: N/A
Part Num: N/A
Who Deconfig: N/A
--- Action - Indict ---
Event No: 0x0000000000000000
Bundle ID: 0
Alert ID:
BOE Section: N/A
BOE Symptoms: 00000001
- Indicted / Acquitted -
Type Timestamp Entity Reason
Ind Mon May 18 16:10:38 2009 Human 0x0000000000000001
Acq Mon May 18 16:11:19 2009 Human User request
---
- Supporting Symptoms - No symptoms flagged.
- SubFru Isolation - Entire FRU indicted.
- SubFru Deconfiguration - No flags set.
- Related Locations - None.
- Acquittal Policy -
CAE User FRU Powr Svc FRU MFW CFW CAE Coh
req req chg cycl cycl OK unc unc unc acq
0 1 1 0 1 0 0 0 0 0
---
--- end report --- 1 records shown
TEST CAMNET
•
Command:
TEST CAMNET <physical location>
•
Description:
Performs an active test of the CAMNet manageability fabric. This test detects problems resulting from malfunctioning hardware, missing or broken cables, or from incorrect cabling. Any test failures results in a series of hardware indictments referencing specific hardware elements encountering problems. To view the generated indictments, see
.
TEST CAMNET 161
The test camnet all command will execute the global CAMNet test after first checking that there are no partitions active.
•
Access level/Bay level:
All
•
Restrictions:
◦
The <physical location> value must be formatted as either an 8–byte hexadecimal integer, or a long or medium hardware resource path string (short form strings are not supported).
◦
Must be in the Health Repository viewer.
TEST FABRIC
•
Command:
TEST FABRIC
•
Description:
Performs an active test of the complex interconnect fabric, the CAMNet manageability fabric, the global clock distribution, and the OA links. This test detects problems resulting from malfunctioning hardware, missing or broken cables, or from incorrect cabling. Any test failures results in a series of hardware indictments referencing specific hardware elements encountering problems. To view the generated indictments, see
NOTE:
TEST FABRIC
cannot be run on an active complex. You must shut down all partitions before using the TEST FABRIC command.
•
Access level/Bay level:
All
•
Restrictions:
Must be in the Health Repository viewer.
TEST CLOCKS
•
Command:
TEST CLOCKS <physical location>
•
Description:
◦
The command verifies the following:
Global clock distribution to ensure that GPSM clock control registers are set appropriately for the complex type
◦
If there are no partitions active, the test will also actively manipulate clock generators to ensure that the cabling is correct on multi-enclosure systems.
◦
This test is also run as part of the test fabric command, which requires that no partitions are active.
◦
All clock sources are working
◦
Each blade is receiving both complex global clock signals
•
Access level/Bay level:
All
162 Health Repository commands
•
Restrictions:
◦
Must be in the Health Repository viewer.
•
Example: myhost-HR> test clocks
Clocks test started...
Blade Sys Clk 0 Sys Clk 1
========== ========== ==========
Blade 1/1 OK OK
Blade 1/2 OK OK
Blade 1/3 OK OK
Blade 1/4 OK OK
Blade 1/5 OK OK
Blade 1/6 ---- ----
Blade 1/7 ---- ----
Blade 1/8 ---- ----
GPSM Int Clk Ext Clk
========== ========== ==========
GPSM 1/1 * OK ----
GPSM 1/2 * OK ----
Clocks test complete.
TEST FABRIC 163
24 Core Analysis Engine commands
The Core Analysis Engine is a component of the HP Integrity Superdome 2 Analysis Engine that enables users to review all generated events logged by the Analysis Engine.
SHOW CAE
•
Command:
SHOW CAE {-L <arguments> | -E <arguments> | -C <arguments>}
•
Description:
Displays or clears the Core Analysis Engine event log based on parameters specified by -L
, -E or -C and modified by <arguments>.
◦
-E
: Displays event details based on event number.
◦
-L
: Displays a summary list of events based on specified <arguments>.
◦
-C
: Clears the event data for the specified events.
IMPORTANT: You cannot recover event data once it has been cleared.
NOTE: All arguments are case-sensitive.
Table 1 List of <arguments>
Argument
-n <Serial Number>
-a <Alert ID>
Description
Displays the event specified by
<Serial Number>
Displays the event specified by
<Alert ID>
Examples
-n 123
— Displays the data for event
123.
-a 2
— Displays the data for alert 2.
-e [eq:|ne:|le:|ge:]
<Severity Level>
-e bw:<Severity Level
1>,<Severity Level 2>
Displays events based on severity level.
•
eq
: Displays events equal to the specified severity level.
This is the default if no argument is specified.
•
ne
: Displays events not equal to the specified severity level.
•
le
: Displays events less than or equal to the specified severity level.
•
ge
: Displays events greater than or equal to the specified severity level.
See
severity level values.
•
-e ne:2
: Displays events with severity level not equal to 2.
•
-e 4
: Displays events with severity level equal to 4.
Displays events between the specified severity levels.
See
for the severity level values.
-e bw:2,5
: Displays events with severity levels between 2 and 5.
Can be used with:
-E
-E
-L
-L
164 Core Analysis Engine commands
Table 1 List of <arguments> (continued)
Argument Description Examples
Can be used with:
-v <Event category
name>[,<Event category
name> ... ]
Displays specified events by event category names.
NOTE: To see a list of possible event category names use
-vall
.
-v Processor,Memory
: Displays all events in the categories Processor and
Memory
-L
-i <Event ID>[,<Event
ID> ... ]
-r "[%]<string>[%]"
Display specified events by event
IDs.
-i 123,124,125
: Displays event IDs
123, 124 and 125.
-L
Searches event descriptions and displays events based on the specified case-sensitive string.
•
<string>
: Event description is exactly the same as the string.
•
<string>%
: Event description begins with the string.
•
%<string>
: Event description ends with the string.
•
%<string>%
: Event description contains the string. This is the default if no operator is specified.
•
-r "device not configured."
:
Displays all events containing the description “device not configured.”
•
-r "%driver not%"
: Displays all events containing the description
“driver not”.
•
-r "The event%" -r "%event occurred"
: Displays all events with descriptions starting with “The event” or ending with “event occurred”.
-L
NOTE: This argument can be used more than once.
-t [eq|le|ge]
<mm:dd:yyyy:hh:mi:ss>
Used to specify date and time as part of the search criteria.
•
eq
: Displays events on the specified date/time. This is the default if no argument is specified.
•
le
: Displays events prior to and on the specified date/time.
•
ge
: Displays events on and after the specified date/time.
•
–t 10:22:2004
: Displays all events on 10/22/2004
•
–t gt 10:22:2004
: Displays all events on and after 10/22/2004.
-t [<Time and date
1>-<Time and date 2>]
Displays events between the specified date/times in the format
<mm:dd:yyyy:hh:mi:ss>
.
-t [10:22:2004-10:29:2004]
:
Displays all events between
10/22/2004 and 10/29/2004.
NOTE:
<Time and date 1>
and <Time and date 2> must be enclosed by [ ].
-L
-L
SHOW CAE 165
Table 1 List of <arguments> (continued)
Argument Description Examples
Can be used with:
-s [asc:|desc:]<Column
name>
Sorts the displayed list of results by the specified column name.
•
asc
: Ascending order. This is the default if no argument is specified.
•
desc
: Decending order.
•
-s asc:id
: Sorts ascending based on ID.
•
-s desc:time
: Sorts descending based on time.
-L
-o <Offset> -c <# of
events>
Displays events based on the specified offset and number of events. The offset specifies the number of the first event to be displayed, and the number of events specifies how many events are displayed.
•
-o 0 -c 20
: Displays the first twenty events.
•
-o 20 -c 20
: Displays the next twenty events after the first twenty.
-L
-p <nPar ID>[:vPar ID]
| complex
Searches for events based on the specified partition ID or complex-wide events.
•
If used with -L, the specified events are displayed.
•
If used with -C, the specified events are cleared.
•
-p 1:1
: Searches for events in nPar
1, vPar 1.
•
-p 3
: Searches for events in nPar 3.
•
-p complex
: Searches for all complex-wide events.
-L
-C
-h
Displays the help information for the command.
-L
-E
-C
Table 2 Severity levels
4
5
2
3
6
7
Value
0
1
•
Access level/Bay level:
All
•
Restrictions:
You must be logged on to the monarch OA to perform this command.
•
Example: hostname> show cae –E –n 2
Alert Number : 2
Event Identification :
Event ID : 100831
Event Time : Fri Sep 15 12:10:23 2006
Indication Identifier : 510083120060915121023
166 Core Analysis Engine commands
Description
Unknown
Other
Information
Degraded/Warning
Minor
Major
Critical
Fatal/Non-recoverable
Managed Entity :
OA Name : Not Available
System Type : 0
System Serial No. : Not Available
OA IP Address : Not Available
Affected Domain :
Enclosure Name : Not Available
RackName : Not Available
RackUID : Not Available
Impacted Domain : Partition
Complex Name : Not Available
Partition ID : 1:2
Summary :
A core failed to rendezvous processing an MCA
Full Description :
While processing an MCA, a core failed to rendezvous with the other processors. This is an
indication of a possible latent defect in the core and the core should be deconfigured. Memory dumps and
Operating System crash dumps could not be retrieved due to the failure to rendezvous.
Probable Cause 1 :
The processor is not functioning properly - failed to rendezvous.
Recommended Action 1 :
Replace the processor, processors or blade as indicated in the replaceable units.
Replaceable Units:
Part Manufacturer : Not Available
Spare Part No. : Not Available
Part Serial No. : Not Available
Part Location : 0x0100ff01ff00ff11 enclosure1/blade1/socket0
Additional Info : Core ID:0 , Core ID:1 , Core ID:2
Part Manufacturer : Not Available
Spare Part No. : Not Available
Part Serial No. : Not Available
Part Location : 0x0100ff01ff01ff11 enclosure1/blade1/socket1
Additional Info : Core ID:0 , Core ID:1 , Core ID:2 , Core ID:3
Additional Data :
Severity : Fatal/NonRecoverable
Alert Type : Device Alert
Event Category : Processor
Event Subcategory : Processor
Probable Cause : Processor Problem (Internal Machine Error)
Event Threshold : 1
Event Time Window : 0
Actual Event Threshold : 1
Actual Event Time Window : 0
Blade Physical Location : 100ff01ffffff94
Blade Serial Number : [Unknown]
Version Info :
SFW Version : Not Available
OA FW Version : Not Available
Provider Version : A.1.0.1
Error Log Data :
Error Log Bundle : 1
SHOW CAE 167
25 Error Logging Services commands
SHOW ERRDUMP
•
Command:
SHOW ERRDUMP {<logtype> [nPar:<nPar #>] | dir <logtype>
| bundle_id <bundleID> | pdhc <logtype>
[<enclosure #>:<blade #>]}
•
Description:
Displays the raw error logs generated by the Error Logging Services for use in troubleshooting of the specified <logtype> for all partitions, or for the specified nPartition.
◦
The dir argument lists the available log bundle IDs of the specified <logtype>.
◦
The bundle_id argument displays the logs of the specified <bundleID>.
◦
The pdhc argument displays the logs of the specified <logtype> in PDHC storage for all blades, or for the specified target.
•
Access level/Bay level:
All
•
Restrictions:
The <logtype> must be one of the following:
◦
mca
◦
init
◦
cmc
◦
cpe
◦
hr
◦
all
: does not include init.
You must be logged on to the monarch OA to perform this command.
168 Error Logging Services commands
26 Debug commands
DISABLE OSDEBUGGER
•
Command:
DISABLE OSDEBUGGER
•
Description:
Disables debugger ports on all complex partitions.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
ENABLE OSDEBUGGER
•
Command:
ENABLE OSDEBUGGER
•
Description:
Enables debugger ports on all complex partitions for 5 minutes. Debugger ports you have connected to continue to function after 5 minutes or after the DISABLE OSDEBUGGER command is executed, but no further connections are permitted.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
DISABLE OSDEBUGGER 169
27 Firmware update commands
For information on online firmware update using the OA GUI, see the HP Integrity Superdome 2
Onboard Administrator User Guide.
UPDATE SHOW
•
Command:
UPDATE SHOW { ALL | BLADE [ ALL | <location> [ { , | - } <location>
] ] | CONFIG | FAN [ ALL | <location> [ { , | - } <location> ] ] |
FIRMWARE | ICBAY [ ALL | <location> [ { , | - } <location> ] ] |
LCD | NPARTITION { nPartition name or number | ALL } | TRAY }
•
Description:
This command will display the firmware version installed on the following FRUs in the enclosure on which the command is run:
◦
Non-Superdome-blade devices in device bays
◦
Interconnect modules
◦
Fans
◦
Trays (PIC on OA tray)
◦
PIC on GPSM boards
◦
LCDs
The firmware version of the following FRUs will not be displayed using the update show command.
◦
Superdome 2 blades
◦
XFM
◦
IOX
◦
OA
◦
GPSM
•
Access level/Bay level:
Any
•
Restrictions:
This command must be run on the enclosure containing the component.
•
Example:
Oa_host_name> update show
Device Name Location Version NewVersion
-----------------------------------------------------------------------------------
TRAY | BladeSystem c7000 Onboard Administrator Tray | - | 1.2.0 | 1.2.0
GPSMPWR | GPSM power management device | 1 | 1.2.0 | 1.2.0
GPSMPWR | GPSM power management device | 2 | 1.2.0 | 1.2.0
LCD | BladeSystem c7000 Insight Display | - | 2.2.2 | 2.2.2
BLADE | HP StorageWorks SB40c | 4 | 1.20.0 | 1.20.0
ICBAY | GbE2c Ethernet Blade Switch | 1 | 1.02.0 | 1.02.0
ICBAY | GbE2c Ethernet Blade Switch | 2 | 1.02.0 | 1.02.0
FAN | BladeSystem c-Class fan | 1 | 2.7.4 | 2.7.4
FAN | BladeSystem c-Class fan | 2 | 2.7.4 | 2.7.4
170 Firmware update commands
UPDATE SHOW FIRMWARE
•
Command:
UPDATE SHOW FIRMWARE
•
Description:
Displays the firmware versions of the complex bundle last installed in the complex and lists devices in the complex which do not share the current firmware version.
IMPORTANT: You will be instructed to reapply the complex bundle to update FRUs which do not share the current firmware version.
•
Access level/Bay level:
Any
•
Restrictions:
You must be connected to the monarch OA to perform this command.
•
Example: If the component does not match the configured complex version, the system prints: oa_host_name> update show firmware
Configured complex firmware bundle version: 2.4.0
=================================================
The FRU(s) listed below contain installed FW versions which do not match the configured bundle. Please update the complex with bundle version 2.4.0.
Device Enc Location Version
XFM | 1 | 1 | 1.0.0
OA | 2 | 2 | Invalid
OA | 1 | 2 | 2.3.0
IOX | 5 | - | 2.3.0
GPSM | 1 | 1 | 2.3.0
If all components match the configured complex version, the system prints:
Firmware on all devices matches the complex configured bundle version.
UPDATE SHOW NPARTITION
•
Command:
UPDATE SHOW NPARTITION {nPartition name or number | ALL}
•
Description:
Displays the current partition firmware version and lists any blades in the partition that do not match the configured partition firmware version.
IMPORTANT: You will be instructed to reapply the complex bundle to update blades which do not share the current partition firmware version.
•
Access level/Bay level:
Any
•
Restrictions:
You must be connected to the monarch OA to perform this command.
•
Example: If any blade does not match the configured partition version, the system prints: oa_host_name> update show npartition 2 nPartition firmware version applied to partition 2, “par_name”.
==========================
Configured nPartition Firmware Version: 1.1.0
Active nPartition Firmware Version: 1.0.0 *MISMATCH AGAINST CONFIGURED VERSION*
The blade(s) listed below contain installed nPartition FW versions which do not match the configured version(s). Please update the partition from a matching bundle.
UPDATE SHOW FIRMWARE 171
nPartition Enc Bay Version
2 | 2 | 3 | 1.0.0
2 | 2 | 4 | Invalid
◦
Partition — The nPartition number the row is referring to.
◦
Enc — The enclosure number.
◦
Location — The bay number within the enclosure.
◦
Version — The version of the firmware bundle which is currently installed in the FRU.
Invalid will be displayed if the current firmware image on the FRU is corrupt or unknown.
If all blades match the configured partition version, the system prints: nPartition firmware on all blades matches the partition’s configured version.
SHOW INFO
•
Command:
SHOW <boardname> info
•
Description:
Lists the bundle revision and displays any mismatches against the configured firmware or npartition versions.
•
Access level/Bay level:
Any
•
Restrictions:
You must be connected to the monarch OA to perform this command.
•
Example:
OA-001CC414F34F> show blade info 1
Server Blade #1 Information:
Type: Server Blade
.
.
.
Firmware Bundle Revision: 2.5.0 *MISMATCH AGAINST CONFIGURED REVISION*
nPartition Revision: 1.0.0 *MISMATCH AGAINST PARTITION 1*
UPDATE FIRMWARE
•
Command:
UPDATE FIRMWARE {<uri>}[FORCE][REINSTALL][ALL][NOEXECUTE]
•
Description:
Executes the firmware upgrade process on one or more available enclosure devices.
<uri>
is the path to the image, which can be accessed using:
◦ ftp
◦ http
◦
Local CD
◦
A thumbdrive plugged into the DVD module in enclosure 1.
◦
Archive Storage
172 Firmware update commands
The <uri> can be any of the following:
◦ http://host/path
◦ ftp://host/path
◦ ftp://username:password@host/path
◦ tftp://host/path
◦
For the USB thumbdrive, use the <uri> for the desired image shown by the SHOW USBKEY command.
◦
For the Archive Storage, use the <uri> for the desired image shown by the SHOW
ARCHIVE command.
Supported protocols are:
◦ http
◦ ftp
◦ tftp
◦
An image on an attached USB thumbdrive.
◦
An image from Archive Storage.
The FORCE option is required to install a bundle which is at a lower revision level than what is currently installed on the complex or partition.
The REINSTALL option forces to system to update all firmware in the complex including those which already match that contained in the target bundle. It also reinstalls all FPGA ROM images.
IMPORTANT: The REINSTALL option can only be used if xfabric is powered off, and will exit if the xfabric is powered on.
The ALL option updates the partition firmware on all blades regardless of partition assignment.
IMPORTANT: The UPDATE FIRMWARE command will only change partition firmware if ALL is specified.
•
Access level/Bay level:
Any
•
Restrictions:
You must be connected to the monarch OA.
•
Example: oa_host_name> update firmware ftp://server/complex_bundle2.3.0
The URI you provided points to firmware bundle version 2.3.0.
The following components will be updated:
Device Enc Location Installed Version
------------------------------------------
BLADE | 2 | 3 | 2.2.0
BLADE | 2 | 4 | 2.2.0
XFM | 2 | 2 | INVALID
GPSM | 2 | 2 | 2.1.0
IOX | 5 | - | INVALID
Applying this bundle will have the following affect(s) on the complex.
Results of the upgrade will be available in the system log.
Warning: The XFMs listed below contain components which will not be updated until you shut down all partitions and run the “POWEROFF XFM ALL” command from the command-line interface and reapply this update.
Device Enc Location Installed Version
------------------------------------------
UPDATE FIRMWARE 173
XFM | 1 | 1 | 1.1.0
You can abort this update by pressing ^C within 10 seconds.
Updating devices... DO NOT remove or power cycle device(s)!
This process may take several minutes.
Updated blade 2/3: Success, complete
Updated blade 2/4: Failure
Updated SIOX 5: Success, INCOMPLETE – component(s) on this device cannot be updated while the partition this device is assigned to is active
Firmware update SUCCESSFUL.
IMPORTANT: If an IOX FPGA needs to be updated and 2 partitions are affected, both will be listed. They must both be shut down at the same time in order for the FPGA update to take place.
NOTE: If the system is unable to determine the bundle version applied to the device,
Installed Version will be reported as Invalid.
If the update is unable to start the system prints:
Firmware update CANCELLED by system, no firmware modified.
If the update fails, system prints:
Firmware update FAILED, firmware may be modified
.
If the firmware update fails, a message that describes the cause of the error and the state of each affected FRU will print.
CLI UPDATE NPARTITION
•
Command:
UPDATE NPARTITION [ALL | <npar name or number> | BLADE <blade_resource_path>] <uri> [FORCE] [REINSTALL]
[NOEXECUTE]
•
Description:
Installs partition firmware from a bundle <uri> to the targeted partitions or blades.
The REINSTALL option forces the system to update the partition firmware on the targeted partition or blade, including images that already match the firmware version in the target bundle.
IMPORTANT: The command will exit with if any targeted partitions are powered on.
•
Access level/Bay level:
Any
•
Restrictions:
You must be connected to the monarch OA to perform this command.
•
Example: oa_host_name> update npartition 2 ftp://server/complex_bundle2.3
The URI you provided points to firmware bundle version 2.3.
The following blades will be updated in partition 2 “par2_name”:
Enc Location |Installed Version
--------------------------------
2 | 3 | 2.2.0
2 | 4 | 2.1.0
2 | 5 | 2.2.0
Applying this bundle will have the following affect(s) on the npartition(s).
Results of the upgrade will be available in the system log.
You can abort this update by pressing ^C within 10 seconds.
Updating devices... DO NOT remove or power cycle device(s)!
This process may take several minutes.
Updated blade 2/3: Success, complete
Updated blade 2/4: Failure
Updated blade 2/5: Success, INCOMPLETE – the nPartition is active. Restart the nPartition to activate the
newly installed partition firmware.
174 Firmware update commands
Firmware update SUCCESSFUL.
If the update is unable to start the system prints:
Firmware update CANCELLED by system, no firmware modified.
If the update fails, system prints:
Firmware update FAILED, firmware may be modified
.
If the firmware update fails, a message that describes the cause of the error and the state of each affected FRU will print.
Effects messages
This section contains the messages that can be displayed when the system reports the effects of applying the requested update:
•
Error: New bundle version is lower and FORCE option was not selected.
•
Warning: New bundle version is lower and FORCE option was selected.
•
Ok: A FRU will be completely updated.
•
Warning: A FRU will be partially updated.
•
Warning: A FRU will not be updated, because the bundle does not support it.
•
Error: Updating Complex Firmware would result in an active partition being unbootable due to incompatible Partition Firmware.
•
Warning: Updating Complex Firmware will result in an inactive partition being unbootable due to incompatible Partition Firmware
•
Error: Updating Partition Firmware will result in an active partition being unbootable due to incompatible Complex Firmware.
•
Warning: Updating Partition Firmware will result in an inactive partition being unbootable due to incompatible Complex Firmware.
•
Critical: Update of a device has failed. Reapply firmware update without attempting to restart the system.
Effects messages 175
28 Updating Firmware
Introduction
Superdome 2 firmware update uses a smart analysis algorithm to assist and prevent disabling a
Superdome 2 through bad firmware update application.
Because there are still limitations in changing out firmware underneath a running partition (online
OS instance), it is important to understand these limitations to minimize downtime in any given firmware update scenario.
Superdome 2 firmware can, at the topmost level, be applied in two different manners; partition or complex. A variety of modifications can be made to both these applications to alter the firmware update in offline and online situations.
Firmware update bundles
All Superdome 2 platform firmware is contained in a single bundle.
Firmware update commands for Superdome 2 generally process bundle updates targeted at the complex or a partition, but will also support updating IOXs and Server blades in situations where these components need to be updated so they can be added to a partition.
Smart analysis
Firmware update in Superdome 2 will not overwrite images that are already at the same revision as in the bundle being applied unless the REINSTALL flag is used.
Mandates
Superdome 2 firmware updates operate under two mandates which are implemented in an ‘analysis’ phase at the time of update. By understanding these mandates, downtime can be minimized for firmware update actions. The mandates are:
•
Never damage a running partition – any update action that could harm a partition either currently running (online) or prevent partition reboot will abort the update.
•
Never install firmware that is not intended for the hardware [board/FRU] – any update action that will incapacitate a board/FRU.
Offline partition update
Single partition update
To target a firmware update to a single offline partition, use one of the following commands.
Updating to a higher bundle revision
oa> UPDATE NPARTITION <nPar name or number> <uri>
Updating to a lower bundle revision
oa> UPDATE NPARTITION <nPar name or number> <uri> FORCE
Checking the Status of Bundle, no update occurs
oa> UPDATE NPARTITION <nPar name or number> <uri> NOEXECUTE
Overwriting a bundle of the same revision
oa> UPDATE NPARTITION <nPar name or number> <uri> REINSTALL
176 Updating Firmware
All partitions update
Use the following command to update all partitions present in the system as well as any blades that are not currently assigned to any partition: oa> UPDATE NPARTITION ALL <nPar name or number> <uri>
NOTE: The [FORCE], [REINSTALL], and [NOEXECUTE] command modifiers still apply.
Blade update
Use the following command to update a single blade that is not currently assigned to a partition.
oa> UPDATE NPARTITION BLADE <X/Y> <URI>
NOTE: The blade resource path is entered as CHASSIS/SLOT [X/Y].
For example: oa> UPDATE NPARTITION BLADE 1/3 ftp://<bundlepath>
Warnings during update
•
Partition Update - If analysis detects the applied partition firmware is incompatible with the complex firmware already installed on the system, a warning will be issued and the update will proceed. You will need to rectify the situation before any partition is allowed to boot.
•
Blade Update - If analysis detects the applied partition firmware is incompatible with the complex firmware already installed on the system, a warning will be issued and the update will proceed.
Errors during update
If the firmware update analysis detects the applied partition firmware does not meet the hardware mandate, the update will print an error message to the user and abort/cancel the update.
Online complex firmware update on Superdome 2
Introduction
Superdome 2 firmware release bundle 2.2.27 (web released in August 2011, factory enabled in
September 2011), brings an exciting capability to Superdome 2 customers. The ability to support online complex firmware updates can dramatically reduce the amount of partition downtime required for a customer to update their Superdome 2 systems to future firmware bundles. Under certain conditions, partition downtime needed to apply a new firmware bundle can even be eliminated entirely. However, there may also be other partition maintenance activities (OS patch installations, for example) to complete during a maintenance window that will involve a partition reboot in order to take effect. Also, it should be understood that firmware updates which include new partition firmware packages (system firmware) will require a partition reboot to activate, but the timing of such an operation can be done on an individual nPartition basis as determined by the operator to best fit their individual needs.
When performing an online complex firmware update, Superdome 2 server management capabilities are inactive, and this is something which operators should keep in mind. It should not be surprising that server management entities throughout the Superdome 2 complex will bear responsibility to update their own firmware Flash ROMs, reboot updated firmware images, and reestablish internal communications with each other, but it is important to remind operators what kinds of management services will become temporarily unavailable at the server level during an online complex firmware update operation. This information is being provided to inform the user of such server management limitations, but will not be a complete listing of all possible consequences which may be encountered during an online complex firmware update.
Online complex firmware update on Superdome 2 177
Please note that Superdome 2 systems running a firmware bundle released prior to (numbered lower than) 2.2.27 do not possess the capability to perform an online complex firmware update, so it should be understood that updating to a future firmware bundle from firmware release 1.3.1, for example, must be performed with all partitions taken offline, and the xfabric powered off.
Services unavailable
Superdome 2 server management features are unavailable during the process of an online complex firmware update. System firmware will continue to operate and support the OS running on partitions in the complex, however, certain activities may require system firmware to interact with server management firmware, and these operations will not work during the actual process of executing an online complex firmware update. These partition/complex firmware interactions may either be delayed until after the complex firmware update operation has completed, or may be dropped or only partially used. Legacy sx2000 Superdome systems also supported online update of server management entities (MP, ED, PDHC, CLU), and performing such updates held similar consequences for that platform.
The following table shows the major classes of server management services which the OS and applications use during normal runtime and details their Availability or Unavailability during the online complex firmware update process:
Service Status during online complex firmware update
Management processor access (for example: poweron/off, restart, TOC, console, logs)
Unavailable
IPMI services
Console service to OS
Unavailable
Unavailable, and some character loss is possible if the buffer fills up
Available System firmware services during boot, shutdown, MCA,
INIT and CMC logging operations
Network management services (SD2 has additional services). OS-debugger, HP-SIM XML query, HP-SUM SOAP query, WEBES ws-manage events and query.
Unavailable
Management Processor access
When an online complex firmware update is initiated, all current users are disconnected from the
OA for the duration of the complex firmware update process. This includes all OA CLI and GUI sessions, with one possible exception: If the operator initiates the firmware update from the CLI, then this session will remain active to allow for tracking the progress of the update for all but the last few minutes. The time it takes for a complex firmware update to complete is highly variable based on system size and complexity (bigger systems take longer), and the number of firmware packages in the bundle which must be updated, but is not expected to exceed 150 minutes under any conditions. Typical firmware updates will take less time to complete.
IPMI
During the process of an online complex firmware update, no IPMI requests can be serviced until the update completes. This means that partition configuration changes, including iCAP changes, will not be allowed. For reference purposes the following IPMI CLI commands are unavailable:
• parcreate
• pardefault
• pardbmgr
• parremove
178 Updating Firmware
• parmodify
• parstatus
• cplxmodify
• vparcreate
• vparremove
• vparmodify
• vparboot
• vparreset
• vparstatus
• icapmodify
• icapstatus
• plg9hlth
• seedGlobalMca
• perf-mode
•
MPEventGen (Intel Itanium 9500 Series processors).
Event logs
Forward Progress Logs and System Event Logs normally captured by the server management system will not be updated during the firmware update process.
IPMI Watchdog
During the online complex firmware update process, the IPMI watchdog timeout will be disabled.
It will be re-enabled when the system wakes up. The OS will discover the watchdog timer has disappeared after the firmware update process has completed, and will recreate it by design.
Partition ID
The # getconf _CS_PARTITION_IDENT command (which returns HP-UX partition ID), is used for licensing. It is a concatenation of UUID + nPartition # + vPar #. UUID is continuously available from the SMBIOS table. The latter two (nPartition, vPar #s) are obtained using an IPMI call which may fail during the firmware update process. HP-UX caches this information after the very first call to getconf _CS_PARTITION_IDENT, so this command would only fail if it had never been run before the firmware update process began.
Console
When the firmware update is in progress, the OS console cannot be serviced on the server management side. Since all active sessions to the OA CLI and GUI interfaces are closed at the beginning of the firmware update process, the OS console cannot be actively viewed during this process. The OS console is normally a quiet interface with little character traffic; however there are conditions (OS panics, for example) where the character buffer could potentially fill up during the firmware update process. If the console character buffer is full during an active online complex firmware update, new incoming characters will be dropped so the console does not hang on the
OS side. This potential for console character loss does not extend to kernel memory (dmesg) or impact the OS syslog or crashdump area in any way, so this should not inhibit OS problem diagnosis in the unlikely event something unexpected occurs at the OS level. The characters captured in the buffer will be drained once the firmware update process completes, and console operation will return to normal.
Online complex firmware update on Superdome 2 179
System Firmware Services During Boot, Shutdown, etc.
Certain partition events which occur while the OS is running may not be handled if they occur while management firmware is unavailable:
•
OS-requested restart (for example: TOC, shutdown –r)
•
MCA
•
HP-UX boot may hang until firmware update completes
In the cases above, the OS shutdown or restart may not complete. The system design does not make any guarantees about successful handling of OS restart, MCA, or boot that occurs during the online complex firmware update process, so HP recommends that the operator not attempt to initiate operations like an OS shutdown, boot/reboot, cold installation, patch update, or a
Serviceguard cluster reconfiguration request during the online complex firmware update process.
Such actions should be performed serially to avoid potential conflict consequences.
All PAL and SAL calls do work during an online complex firmware update, as these commands execute at the partition level and do not access server management resources. The following services are not affected by the online complex firmware update process, and will remain operational:
Get/SET EFI Variables
Calls to get/set EFI variables will work for the OS.
HPET Timer
The HPET timer will not be re-initialized, and this partition resource will remain available throughout the firmware update process.
EFI_SetTime
System firmware will continue to maintain the correct time during an online firmware update.
Error Records
Error records can be generated as a result of INIT, CMC/CPE, and MCA.
•
INITs are stored by system firmware in NVRAM, so these records will be available to the OS after restart. They will be also be available to CLI errdump once the firmware update completes.
•
Logging of CMC/CPE error records are unaffected by a PDHC or OA restart – errors not logged before a restart are saved in hardware and will be logged after the restart
•
MCA logs may be lost during this period, however system firmware will alert server management that an MCA has occurred once the firmware update completes, and server management will ensure the partition is reset and data integrity maintained.
Affected OS Commands
The machinfo command can print the firmware versions. This command may malfunction during an active online complex firmware update operation when it attempts to print the BMC firmware version, which is sourced via IPMI.
Network Services to OA
All network services provided by the OA are interrupted by the firmware update process. These services include:
•
XML inventory query from HP-SIM
•
WS-MAN partition query from HP-SIM and plugins
•
User interface (ssh, web, telnet) for all OA services
180 Updating Firmware
•
SOAP request from GiCAP Group Manager, HP-SUM
•
Kernel debugger connection through OA network port
•
Console access through the OA
•
Ping, SNMP queries
This is the same as legacy MP or C7000 OA (depending on the protocol) behavior during an update.
Frequently asked questions:
Some sample questions are included below to aid the operator wishing to perform an online complex firmware update.
1.
Can Oracle use IPMI to reset a partition?
•
Answer: Not during the online complex firmware update process.
2.
Do virtual partition reboots proceed during online complex firmware update?
•
Answer: HP can not guarantee completion of a reboot during this time, so the operator should avoid initiating this action while in process. Reboot requests from an OS that occur during an online complex firmware update will be queued and completed after the firmware update process finishes.
3.
GWLM asks for dynamic resource change (for example, Vparmodify), what happens when it can not execute for an hour?
•
Answer: GWLM tries a number of times and gives up, logs an error, will come back and retry later. Changes won’t happen until it eventually tries later when the firmware update process has completed.
4.
How does field support debug if something happened during an online complex firmware update?
•
Answer: Kernel memory (dmesg), the OS syslog, and crashdump memory is unaffected, so this will not inhibit debug for OS-related events. The loss of event logs during the firmware update process is unavoidable (as it was on legacy sx2000 Superdome systems), but the SEL will indicate start and finish times for the update process.
5.
What happens if Serviceguard or other cluster software tries to TOC during an online complex firmware update?
•
Answer: If a node tries to TOC itself from an app running on the partition, the partition
OS will shut down to a point where it is ready to talk to server management. From an application viewpoint, the system is down. It may or may not automatically restart when the firmware update process completes. The service processor is unavailable during online complex firmware update, so a node cannot successfully TOC another node.
6.
Will agents that require licensing or UUID find that information available during an online complex firmware update?
•
Answer:
◦
See the description under
for details
◦
System firmware services are largely available during online firmware update
◦
Machinfo reports system firmware revision, BMC revision, FPSW revision
Known issues:
The following observations are included to help the operator understand how the loss of server management features might be visible from the OS perspective.
Online complex firmware update on Superdome 2 181
hpvminfo command qualifiers fail
The use of certain hpvminfo command qualifiers will return an ioctl error when executed during
Superdome 2 Online Firmware Update. This may also result in a delay before the results of the command are displayed.
The affected commands include: hpvminfo, hpvminfo -V, and hpvminfo -v.
Newly created HPVM guests cannot be started
Any newly created HPVM guest cannot be started during Superdome 2 Online Firmware Update.
When you attempt to start the guest, the hpvmstart command will hang at "Initializing Forward
Progress Log." The hpvmstart command will complete successfully after the Online Firmware
Update has completed.
NOTE: This issue only pertains to newly created guests that have never been started. Guests that have been started at least once prior to the Online Firmware Update will start without any problems.
Serviceguard Manager performance degradation and proxy errors
Serviceguard Manager may experience some performance degradation or report proxy errors during Superdome 2 Online Firmware Update. These issues do not adversely affect the Serviceguard cluster or applications being managed by Serviceguard. If you do receive a message about a proxy error, you can resolve the issue by reloading the page. Performance returns to normal once the Online Firmware Update has completed.
cimserver shutdown and startup fail
The cimserver command will timeout when attempting to shutdown or startup during Superdome
2 Online Firmware Update. Stopping or starting the cimserver process should be performed before or after the Superdome 2 Online Firmware Update.
The affected commands include: cimserver -s and cimserver.
cimauth is unable to add authorizations
cimauth will fail to add authorizations during Superdome 2 Online Firmware Update. These operations should be performed before or after the Superdome 2 Online Firmware Update.
Example of a cimauth command: cimauth -a -u wbem -n root -R -W
cprop command qualifiers fail
The use of certain cprop command qualifiers will report “Connection timed out” when executed during Superdome 2 Online Firmware Update.
The affected commands include: cprop -summary -a and cprop -summary -Memory.
SMH is unable to query memory or enclosure information
The SMH is unable to query memory or enclosure information during Superdome 2 Online Firmware
Update. This information is properly reported before and after the Superdome 2 Online Firmware
Update.
setboot and related commands are unable to display or modify boot variables
The setboot command is unable to display or modify boot variables during Superdome 2 Online
Firmware Update. This also impacts any command that calls setboot.
The affected commands include: setboot, drd activate, drd status, vxbrk_rootmir, and vxrootmir.
wbemassist namespace error
wbemassist reports a namespace error when checking the WBEM Server response.
182 Updating Firmware
par* and vpar* commands fail
Parcon services are not available during Superdome 2 Online Firmware Update. Due to this unavailability, all par* and vpar* commands will fail.
The affected commands include, but are not limited to: parcreate, parmodify, parperm, parstatus
, vparcreate, vparmodify, vparstatus, and others.
Online partition update
IMPORTANT:
Guidelines for online firmware updates
Online complex firmware updates should be coordinated with partition and application operations, so as not to coincide with other administrative activities. Partition or application maintenance, configuration changes, or other actions which rely on platform management capabilities should not be conducted simultaneously with online complex firmware updates. This coordination will largely avoid impact from services which are unavailable during online updates.
During online partition updates, the partition firmware is installed but does not become active until the nPar reboots. This enables rolling upgrades, where nPars are updated one at a time as downtime to reboot becomes available.
Single partition update
To target a firmware update to a single online partition, use one of the following commands.
IMPORTANT: More than one command line modifier can be applied in a given situation. However the modifiers however must be applied in the following order:
1.
[FORCE]
2.
[REINSTALL]
3.
[NOEXECUTE]
Updating to a higher bundle revision oa> UPDATE NPARTITION <nPar name or number> <uri>
Updating to a lower bundle revision oa> UPDATE NPARTITION <nPar name or number> <uri> FORCE
Checking the Status of Bundle, no update occurs oa> UPDATE NPARTITION <nPar name or number> <uri> NOEXECUTE
Overwriting a bundle of the same revision oa> UPDATE NPARTITION <nPar name or number> <uri> REINSTALL
All partitions update
Use the following command to update all partitions present in the system as well as any blades that are not currently assigned to any partition: oa> UPDATE NPARTITION ALL <nPar name or number> <uri>
NOTE: The [FORCE], [REINSTALL], and [NOEXECUTE] command modifiers still apply.
Blade update
This is not possible as a blade unassigned to a partition cannot boot an OS instance.
Online complex firmware update on Superdome 2 183
Errors during update
If the firmware update analysis detects that the applied partition firmware does not meet both mandates, the update will print an error message and abort/cancel the update.
184 Updating Firmware
29 Archive Storage commands
These commands implement the archive storage feature.
Archive Storage provides direct access to the local internal thumbdrive with the purpose of backing up data and storing firmware bundles.
SHOW ARCHIVE
•
Command: show archive
•
Description:
Lists files on the archive storage.
•
Access level/Bay level:
Any active OA
•
Restrictions:
None
•
Example: oa-host-name> show archive
Firmware Image Files Image Version
--------------------------------------- ------------archive://hpsd2fw.bundle 3.4.4
Configuration Script Files
--------------------------------------archive://config.cfg
Partition Configuration Files
---------------------------------------
No partition configuration files found (*.pmc).
Console Logs Partition
--------------------------------------- ---------
No console log files found (*.dat).
Debug Logs Time
--------------------------------------- ----
No debug log files found (*.log or *-logs.tar.gz).
CLEAR ARCHIVE
•
Command: clear archive <”filename”>
•
Description:
Removes either individual or all files from the archive store.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
Any active OA
•
Example:
SHOW ARCHIVE 185
oa-host-name> clear archive
This command will erase ALL files from the Archive Storage.
Entering anything other than 'YES' will result in the command not executing.
Are you sure you want to proceed? yes
The files above have been successfully removed from the Archive Storage.
COPY
•
Command:
COPY <url_source> { <url_target> | ARCHIVE <"filename"> | USB <"filename"> }
•
Description:
Copies a config, parconfig, debug log, or firmware bundle file from the specified source to the specified destination. Valid sources and destinations are:
◦
Archive Storage
◦
The external USB
◦
The network using http, ftp or tftp protocols.
A copy request between two remote URLs, or using http protocol at the destination file is not permitted.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
None
•
Example: oa-host-name> copy ftp://server/hpsd2fw.bundle archive
The file was successfully copied.
oa-host-name > copy archive://hpsd2fw.bundle usb
The file was successfully copied.
oa-host-name > copy archive://storage/config.cfg ftp://server/config.cfg
The file was successfully copied.
oa-host-name > copy archive://storage/debug.log tftp://server/debug.log
The file was successfully copied.
DOWNLOAD PARCONFIG
•
Command:
DOWNLOAD PARCONFIG { ARCHIVE <file> | USB <file> | <URL> }
•
Description:
Downloads a previously saved partition specification file from an archive, specific IP host, or
USB connected to the enclosure.
Supported protocols are:
◦ http
◦ ftp
◦ tftp
◦ usb
◦
Archive Storage
186 Archive Storage commands
The url should be formatted as protocol://host/path/<file>. If your ftp server does not support anonymous connections then you can specify a username and password within the url formatted as ftp://username:password@host/path/<file>.
IMPORTANT: HP recommends keeping an off-complex copy of configuration backup files to ensure that complete loss of saved state on the complex does not also result in the loss of the backup data.
•
Access level/Bay level:
OA Administrator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
•
Example: oa-host-name> DOWNLOAD PARCONFIG ARCHIVE parconf.pmc
File downloaded successfully.
UPLOAD PARCONFIG
•
Command:
UPLOAD PARCONFIG { ARCHIVE <file> | USB <file> | <URL> }
•
Description:
Uploads the complex partition configuration to an archive, URL, or USB connected to the enclosure.
Supported protocols are:
◦ http
◦ ftp
◦ tftp
◦ usb
◦
Archive Storage
The path is the location where the file will be placed. The url should be formatted as protocol://host/path/<file>. If your ftp server does not support anonymous connections then you can specify a username and password within the url formatted as ftp://username:password@host/path/<file>.
IMPORTANT: HP recommends keeping an off-complex copy of configuration backup files to ensure that complete loss of saved state on the complex does not also result in the loss of the backup data.
NOTE: If multiple USB keys are found, the configuration file will be saved to the first USB key that was inserted into the Onboard Administrator.
•
Access level/Bay level:
OA Administrator
CLEAR ARCHIVE 187
•
Restrictions:
◦
The filename parameter must not contain any spaces and must have a .pmc extension.
◦
You must be connected to the monarch OA to perform this command.
•
Example: oa-host-name> UPLOAD PARCONFIG ARCHIVE parconf.pmc
File uploaded successfully.
188 Archive Storage commands
30 Legacy console commands
These commands are carried forward from previous systems to provide additional functionality for users. These commands function for both nPartitions and virtual partitions.
BO
•
Command: bo [<nPar #>]
•
Description:
Enables users to power on nPartitions.
If <nPar #> is specified, this command is equivalent to
“POWERON PARTITION” (page 139)
, however the OVERRIDE argument is not accepted.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
CL
•
Command: cl [<nPar #>]
•
Description:
Displays the Console Log viewer.
If <nPar #> is specified, then this command is equivalent to
.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
CO
•
Command: co [<nPar #>]
•
Description:
Accesses the nPartition text console.
If <nPar #> is specified, then this command is equivalent to
.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
BO 189
FPL
•
Command: fpl
•
Description:
Equivalent to
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
PC/PE
•
Command: pc | pe
•
Description:
Enables users to control the power state of nPartitions in the complex.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
RS
•
Command: rs [<nPar #>]
•
Description:
Enables users to reset a partition.
If <nPar #> is specified, then this command is equivalent to
.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
SEL
•
Command: sel
•
Description:
Equivalent to
.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
190 Legacy console commands
TC
•
Command: tc [<nPar #>]
•
Description:
Enables users to TOC reset a partition.
If <nPar #> is specified, then this command is equivalent to
.
•
Access level/Bay level:
OA Administrator, OA Operator
•
Restrictions:
You must be connected to the monarch OA to perform this command.
TC 191
31 Event notifications
Enclosure event notifications
Enclosure events produce screen messages with the SHOW DISPLAY EVENTS option enabled. If you are directly affected by an event, then a message displays whether the SHOW DISPLAY
EVENTS
option is enabled or disabled.
Event messages include the device affected, the device name, and the date and time of the event.
Some examples of event messages are:
•
The enclosure is in a degraded state.
•
Blade X has experienced a failure.
•
The temperature on blade X has exceeded the failed threshold.
•
Fan X has experienced a failure.
•
The power supplies are no longer redundant.
•
Power supply X is in a degraded state.
•
The enclosure temperature has exceeded the degraded threshold.
Command line event notifications
When the SET DISPLAY EVENTS option is turned ON, the terminal interface displays error, warning, and status messages, depending on the behavior of the enclosure and its components.
The syntax for these messages are:
•
<error>
: Description of error
•
<warning>
: Description of warning
•
<status>
: Description of status
Causes of the error, warning, or status events that display are listed in the following table.
Event
Bay Event
Blade Inserted
Blade Thermal Status Changed
Blade Removed
Blade Port Map Info
DVD Inserted
DVD Removed
Enclosure Status Change
Enclosure Name Change
Fan Status Change
Fan Inserted
Fan Removed
GPSM Inserted
GPSM Removed
192 Event notifications
Cause
A bay was assigned or unassigned from a group.
A blade was inserted into the enclosure.
The thermal status of a blade changed
A blade was removed from the enclosure.
The port mapping information of a blade was updated.
A DVD module was inserted in the monarch enclosure.
A DVD module was removed from the monarch enclosure.
A change in status has occurred because of a change in the state of one or more hardware components or server readings.
The name of an enclosure was changed.
The status of a fan has changed.
A fan has been inserted.
A fan has been removed.
A GPSM has been inserted.
A GPSM has been removed.
Event
Interconnect Inserted
Cause
An interconnect module was inserted into an enclosure.
Interconnect Thermal Status Changed The thermal status of an interconnect module changed.
Interconnect Removed
Interconnect Power Reset
Interconnect Port Map Info
IOX Inserted
IOX Removed
IOX Fan State Changed
IOX Power Supply Inserted
IOX Power Supply Removed
LDAP Group Removed
OA System Log Cleared
OA Name Changed
OA Inserted
OA Removed
OA Takeover nPartition State Changed
Power Supply Status Change
Power Supply Inserted
Power Supply Removed
Power Supply Redundancy Change
Power Supply Overload
Restart Event
Rack Name Change
Rack Topology
Thermal Status Change
User Removed
An interconnect module was removed from an enclosure.
The power of an interconnect module was reset.
The port mapping information of an interconnect module was updated.
An IOX enclosure has been connected to the complex.
An IOX enclosure has been disconnected from the complex.
The status of an IOX fan has changed.
A power supply has been inserted into an IOX enclosure.
A power supply has been removed from an IOX enclosure.
A LDAP group was removed from the Onboard Administrator. If you are logged on to the Onboard Administrator under this LDAP group, you are disconnected.
The Onboard Administrator system log was cleared.
The Onboard Administrator DNS name was changed.
A redundant Onboard Administrator was inserted into an enclosure.
A redundant Onboard Administrator was removed from an enclosure.
A redundant and active Onboard Administrator are switching roles. The Active
Onboard Administrator reboots into Standby Mode and the redundant Onboard
Administrator transitions to Active Mode.
The status of an nPartition has changed.
The status of a power supply has changed.
A power supply has been inserted.
A power supply has been removed.
The power supplies are either now redundant or are no longer redundant.
The power supplies are being asked to draw more current than they are able.
The Onboard Administrator is about to start.
User Disabled
User Rights vPar State Changed
Xbar Inserted
Xbar Removed
Xbar Power Status Change
The rack name stored on the enclosure was changed.
Enclosures were connected or disconnected from the enclosure link.
A thermal sensor has changed state.
A user was removed from the Onboard Administrator. If you are logged in as this user, you are disconnected from the Onboard Administrator.
A user was disabled. If you are logged in as this user, you are disconnected from the Onboard Administrator.
The privilege level of a user on the Onboard Administrator was changed. If you are logged in as this user, you are disconnected from the Onboard Administrator.
You can login again with your new privilege level.
The status of a virtual partition has changed.
A Xbar Fabric module has been inserted.
A Xbar Fabric module has been removed.
The power status of an Xbar Fabric module has changed.
Command line event notifications 193
32 Support and other resources
Before you contact HP
Be sure to have the following information available before you call HP:
•
Technical support registration number (if applicable)
•
Product serial number
•
Product model name and number
•
Product identification number
•
Applicable error messages
•
Add-on boards or hardware
•
Third-party hardware or software
•
Operating system type and revision level
HP contact information
For the name of the nearest HP authorized reseller:
•
See the Contact HP worldwide (in English) webpage ( http://welcome.hp.com/country/us/ en/wwcontact.html
).
For HP technical support:
•
In the United States, for contact options see the Contact HP United States webpage ( http:// welcome.hp.com/country/us/en/contact_us.html
). To contact HP by phone:
◦
Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored.
◦
If you have purchased a Care Pack (service upgrade), call 1-800-633-3600.
•
In other locations, see the Contact HP worldwide (in English) webpage ( http:// welcome.hp.com/country/us/en/wwcontact.html
).
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/country/us/en/contact_us.html
After registering, you will receive email notification of product improvements, new driver versions, firmware updates, and other product resources.
Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to [email protected]
.
Include the document title and manufacturing part number. All submissions become the property of HP.
Installing HP Insight Remote Support Software
HP strongly recommends that you install HP Insight Remote Support software to complete the installation or upgrade of your product and to enable improved delivery of your HP Warranty, HP
Care Pack Service or HP contractual support agreement. HP Insight Remote Support supplements your monitoring, 24x7 to ensure maximum system availability by providing intelligent event diagnosis, and automatic, secure submission of hardware event notifications to HP, which will
194 Support and other resources
initiate a fast and accurate resolution, based on your product’s service level. Notifications may be sent to your authorized HP Channel Partner for on-site service, if configured and available in your country. The software is available in two variants:
•
HP Insight Remote Support Standard: This software supports server and storage devices and is optimized for environments with 1-50 servers. Ideal for customers who can benefit from proactive notification, but do not need proactive service delivery and integration with a management platform.
•
HP Insight Remote Support Advanced: This software provides comprehensive remote monitoring and proactive service support for nearly all HP servers, storage, network, and SAN environments, plus selected non HP servers that have a support obligation with HP. The software is integrated with HP Systems Insight Manager. A dedicated server is recommended to host both HP Systems Insight Manager and HP Insight Remote Support Advanced.
Details for both versions are available at: http://www.hp.com/go/insightremotesupport
To download the software, go to Software Depot: http://www.software.hp.com
Select Insight Remote Support from the menu on the right.
New and changed information in this edition
The following additions and changes have been made for this edition:
•
The following information has been updated:
◦
revised to include additional information regarding link-local addresses.
Related information
The following documents provide related information:
•
HP Integrity Superdome 2 Partitioning Administrator Guide
You can find these documents from the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals
Typographic conventions
This document uses the following typographical conventions:
Command
A command name or qualified command phrase.
Computer output
Text displayed by the computer.
Ctrl-X A key sequence. A sequence such as Ctrl-X indicates that you must hold down the key labeled Ctrl while you press another key or mouse button.
Key
User input
The name of a keyboard key. Return and Enter both refer to the same key.
Commands and other text that you type.
Variable
[ ]
{ }
...
The name of a placeholder in a command, function, or other syntax display that you replace with an actual value.
The contents are optional in syntax. If the contents are a list separated by
|, you must choose one of the items.
The contents are required in syntax. If the contents are a list separated by |, you must choose one of the items.
The preceding element can be repeated an arbitrary number of times.
New and changed information in this edition 195
| Separates items in a list of choices.
WARNING!
A warning calls attention to important information that if not understood or followed will result in personal injury or nonrecoverable system problems.
CAUTION: A caution calls attention to important information that if not understood or followed will result in data loss, data corruption, or damage to hardware or software.
IMPORTANT: This alert provides essential information to explain a concept or to complete a task
NOTE: A note contains additional information to emphasize or supplement important points of the main text.
196 Support and other resources
A Using event logs
Event logs are generated by software or firmware when an event is detected. Some events that cause event records to be generated are:
•
Hardware-related.
◦
Example: fan or power supply failure.
•
Software-related.
◦
Example: indicating that software reached a certain point in the code, or that a certain amount of time has passed.
The OA can timestamp and filter events, then store and transfer them to event log readers. Log entries can be read by management applications in:
•
Operating Systems
•
OAs
•
SEL viewers
•
FPL viewers
•
Live Event viewers
•
EAE
Log entries can be cleared by OS management applications or by the OA itself.
Events are classified into a number of severity levels, ranging from critical failure to non-error forward progress notification. The severity level is encoded in the alert level data field on an event record. Different system actions may result from generation of an event record, depending on alert level.
Text search
You can search the FPL and SEL event log viewers using text strings. Text search capability includes the ability to search using regular expressions.
Live viewer
The live event viewer provides a way for you to see records as they occur. The OA supports multiple simultaneous live event viewers that are created and destroyed dynamically when requested. The maximum number of simultaneous live event viewers is limited by the number of connections supported by the OA.
Each live event viewer works independently from any other event viewer, meaning that each live event viewer can select its own filter and format options without affecting other live event viewers.
The log can be filtered using the following items:
• blade number
• cabinet number
• partition number
• alert level
The following format options are also available:
•
Keyword – This is the default format for all viewers. The keyword format supplies the following information about an event:
◦ log number
◦ reporting entity type
◦ reporting entity ID
Text search 197
◦ alert level
◦ hexadecimal dump of event records
◦ event ID keyword
•
Raw hex – The raw hex format supplies following information about an event:
◦ hexadecimal dump of event records
•
Text – The text format supplies the following information about an event:
◦ log number
◦ timestamp
◦ alert level
◦ event ID keyword
◦ brief text description
◦ reporting entity type
◦ reporting entity ID
◦ hexadecimal dump of event records
•
Problem/Cause/Action - The Problem/Cause/Action format displays a problem/cause/action statement in addition to the summary and other fields displayed by the text formatter.
To connect to the live log viewer, enter the SHOW LIVELOGS command on the monarch OA.
NOTE: The option C can be used to display column header information at any point in time while in the Live viewer. The column header corresponding to the event viewer format currently active will be displayed
Welcome to the Live Event Viewer
WARNING: Due to connection speed and/or to the number
of events being generated and/or to the format
option selected, the live event viewer may
silently drop events.
The following event format options are available:
K: Keyword
E: Extended Keyword
R: Raw hex
T: Text
S: Cause/Action
The following alert filter options are available:
Alert filter will cause events at the selected alert filter
and below to be shown
0: Minor Forward Progress
1: Major Forward Progress
2: Informational
3: Warning
5: Critical
7: Fatal
The following event filter options are available:
B: Blade
P: Partition
V: Virtual Partition
U: Unfiltered
Current alert threshold: Alert threshold 0
Current filter option: Unfiltered
Current format option: Extended Keyword
Select new filter/format option, or <ctrl-b> to exit or <cr> to
resume display of live events, or H/? for help or 'C' to
display column header information
Location: Enclosure, Device Bay, Socket, Core, Thread AL: Alert Level
198 Using event logs
Rep Location nPar: AL Encoded Field Data Field Keyword
Ent vPar Timestamp
SFW 1,1,0,1,0 255:255 1 23000ba105e10000 0000000000000004 PAL_EXIT_SELFTEST_STATUS
PDHC 1,2 14:3 1 27801ed800e10000 0000000000000001 POWERING_NPAR
04/24/2012 06:39:05
OA 1,1 None 2 4480201a00e10000 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_WAITING
04/24/2012 06:39:05
ILO 1,2 None 2 4b00260300e10000 010000004f96acf9 OA_REQUESTS_POWER_CHANGE
04/24/2012 06:39:05
ILO 1,2 None 1 2980256100e10000 20202020494d5049 SYS_CTL_REQ_MOMENT_BTN
04/24/2012 06:39:05
SFW 1,1,0,1,1 255:255 1 23000ba107e10000 0000000000000004 PAL_EXIT_SELFTEST_STATUS
SFW 1,1,0,2,0 255:255 1 23000ba109e10000 0000000000000004 PAL_EXIT_SELFTEST_STATUS
SFW 1,1,0,2,1 255:255 1 23000ba10be10000 0000000000000004 PAL_EXIT_SELFTEST_STATUS
FPL viewer
The FPL viewer provides a way for OA users to view the event records stored in the FPL. The OA supports multiple simultaneous FPL viewers. The maximum number of FPL viewers is limited by the number of connections supported by the OA. Each FPL viewer works independently from any other viewer, meaning each FPL viewer can select its own filter options without affecting other FPL viewers.
The log can be filtered using the following items:
• blade number
• cabinet number
• partition number
• alert level
The following format options are also available:
•
Keyword – This is the default format for all viewers. The keyword format supplies the following information about an event:
◦ log number
◦ reporting entity type
◦ reporting entity ID
◦ alert level
◦ hexadecimal dump of event records
◦ event ID keyword
•
Raw hex – The raw hex format supplies following information about an event:
◦ hexadecimal dump of event records
•
Text – The text format supplies the following information about an event:
◦ log number
◦ timestamp
◦ alert level
◦ event ID keyword
◦ brief text description
◦ reporting entity type
◦ reporting entity ID
◦ hexadecimal dump of event records
•
Problem/Cause/Action - The Problem/Cause/Action format displays the problem/cause/action statement in addition to the summary and other fields displayed by the text format.
FPL viewer 199
NOTE: The display of column headers can be turned on or off using toggle option C. By default, the column header will be on.
To connect to the FPL viewer, enter the SHOW FPL command on the monarch OA .
Welcome to the Forward Progress Log (FPL) Viewer
The following FPL navigation commands are available:
D: Dump log starting at current block for capture and analysis
F: Display first (oldest) block
L: Display last (newest) block
J: Jump to specified entry and display previous block
+: Display next (forward in time) block
-: Display previous (backward in time) block
<cr>: Repeat previous +/- command
<sp>: Repeat previous +/- command
/: Search forward for input string
\: Search backwards for input string
I: Changes between case sensitive and insensitive search
N: Perform previous search using last input string
?/H: Display help
C: Toggle display of column header
<Ctrl-b>: Exit viewer
The following event format options are available:
K: Keyword
E: Extended Keyword
R: Raw hex
T: Text
S: Cause/Action
The following alert threshold options are available:
Alert thresholds will cause events at the selected threshold
and below to be shown
0: Minor Forward Progress
1: Major Forward Progress
2: Informational
3: Warning
5: Critical
7: Fatal
The following event filter options are available:
B: Blade
P: Partition
V: Virtual Partition
U: Unfiltered
Current alert threshold: Alert threshold 0
Current filter option: Unfiltered
Current format option: Extended Keyword
MP:VWR (<cr>,<sp>,+,-,?,H,C,F,I,L,J,D,K,E,R,T,B,P,V,U,/,\,N,0,1,2,3,5,7,<Ctrl-b>) >
Location: Enclosure, Device Bay, Socket, Core, Thread AL: Alert Level
Event# Rep Location nPar: AL Encoded Field Data Field Keyword
Ent vPar Timestamp
848 SFW 1,1,0,0,0 255:255 0 030026a701e10000 0000000000050014 EFI_DRIVER_VERSION
847 SFW 1,1,0,0,0 255:255 0 03001af101e10000 01010000165014e4 EFI_DRIVER_LOCATION
846 SFW 1,1,0,0,0 255:255 0 0300232501e10000 00001041ba552000 BOOT_LOAD_FW_ADDR
845 SFW 1,1,0,0,0 255:255 0 0300232401e10000 652e69646e757665 BOOT_LOAD_FW_MODULE
844 OA 1,1 1 1 368022ef00e10000 199b000000000000 PARCON_VPAR_POWERON_COMPLETE
844 04/24/2012 06:29:50
843 OA 1,1 1 0 1680264000e10000 199b000200010000 PARCON_VPAR_OPERATION
843 04/24/2012 06:29:50
842 OA 1,1 1 1 34801f4400e10000 0610000000000000 PARCON_NPAR_STATE_CHANGE
842 04/24/2012 06:29:45
841 OA 1,1 1 0 1680264000e10000 1998000200160000 PARCON_VPAR_OPERATION
841 04/24/2012 06:29:44
840 OA 1,1 1 0 1680263f00e10000 19980007002f0000 PARCON_NPAR_OPERATION
840 04/24/2012 06:29:44
839 PDHC 1,2 14:3 0 07801eb800e10000 0000000019000000 FHW_NOTIFY_CFW
839 04/24/2012 06:29:42
838 SFW 1,1,0,0,0 1 1 3480020b01e10000 0000000000000006 EFI_LAUNCH_BOOT_MANAGER
838 04/24/2012 06:29:42
837 SFW 1,1,0,0,0 1 0 000025db01e10000 0000000000000000 VC_HANDOFF_TO_BOOTMGR
836 SFW 1,1,0,0,0 1 0 0300232501e10000 00001041ba696000 BOOT_LOAD_FW_ADDR
835 SFW 1,1,0,0,0 1 0 0300232401e10000 66652e6177737066 BOOT_LOAD_FW_MODULE
834 SFW 1,1,0,0,0 1 0 0300232501e10000 00001041ba8ba000 BOOT_LOAD_FW_ADDR
SEL viewer
The SEL viewer provides a way for OA users to view the event records stored in the SEL. The OA supports multiple simultaneous SEL viewers. The maximum number of SEL viewers is limited by the
200 Using event logs
number of connections supported by the OA. Each SEL viewer works independently from any other viewer, meaning that each SEL viewer can select its own filter options without affecting other SEL viewers.
The log can be filtered by alert level.
The following format options are also available:
•
Keyword – This is the default format for all viewers. The keyword format supplies the following information about an event:
◦ log number
◦ reporting entity type
◦ reporting entity ID
◦ alert level
◦ hexadecimal dump of event records
◦ event ID keyword
•
Raw hex – The raw hex format supplies following information about an event:
◦ hexadecimal dump of event records
•
Text – The text format supplies the following information about an event:
◦ log number
◦ timestamp
◦ alert level
◦ event ID keyword
◦ brief text description
◦ reporting entity type
◦ reporting entity ID
◦ hexadecimal dump of event records
NOTE: The display of column headers can be turned on or off using toggle option C. By default, the column header will be on.
Enter the show SEL to connect to the SEL viewer.
Welcome to the System Event Log (SEL) Viewer
The following SEL navigation commands are available:
D: Dump log starting at current block for capture and analysis
F: Display first (oldest) block
L: Display last (newest) block
J: Jump to specified entry and display previous block
+: Display next (forward in time) block
-: Display previous (backward in time) block
<cr>: Repeat previous +/- command
<sp>: Repeat previous +/- command
/: Search forward for input string
\: Search backwards for input string
I: Changes between case sensitive and insensitive search
N: Perform previous search using last input string
?/H: Display help
C: Toggle display of column header
<Ctrl-b>: Exit viewer
The following event format options are available:
K: Keyword
E: Extended Keyword
R: Raw hex
T: Text
SEL viewer 201
S: Cause/Action
The following alert threshold options are available:
Alert thresholds will cause events at the selected threshold
and below to be shown
2: Informational
3: Warning
5: Critical
7: Fatal
The following event filter options are available:
B: Blade
P: Partition
V: Virtual Partition
U: Unfiltered
Current alert threshold: Alert threshold 2
Current filter option: Unfiltered
Current format option: Extended Keyword
MP:VWR (<cr>,<sp>,+,-,?,H,C,F,I,L,J,D,K,E,R,T,B,P,V,U,/,\,N,2,3,5,7,<Ctrl-b>) >
Location: Enclosure, Device Bay, Socket, Core, Thread AL: Alert Level
Event# Rep Location nPar: AL Encoded Field Data Field Keyword
Ent vPar Timestamp
21 SFW 1,1,0,0,0 255:255 2 43801f4f01e10029 0000000000000000 SET_SECURE_MODE
21 04/24/2012 06:29:23
20 SFW 1,1,0,0,0 255:255 2 4480223a01e10027 0100ff01ffffff94 MEM_DIMM_ENABLE_DONE
20 04/24/2012 06:28:54
19 PDHC 1,2 14:3 2 4480223800e10025 0100ff01ffffff94 DIMM_LOADING_ORDER_DONE
19 04/24/2012 06:28:03
18 OA 1,1 None 2 4480201f00e10023 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_SUCCESS
18 04/24/2012 06:27:51
17 PDHC 1,2 14:3 2 438028d300e10021 0000000000000150 BLADE_DIMM_VOLTAGE
17 04/24/2012 06:27:49
16 OA 1,1 None 2 4480201d00e1001f 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_CONTINUE
16 04/24/2012 06:27:49
15 ILO 1,1 None 2 4b00260300e1001e 010000004f96aa53 OA_REQUESTS_POWER_CHANGE
15 04/24/2012 06:27:47
14 OA 1,1 None 2 4480201a00e1001c 0100ff01ffffff94 OA_HWMGR_DAEMON_BLADE_POWER_ON_WAITING
14 04/24/2012 06:27:47
13 OA 1,1 1 2 448025a900e1001a 0100ff03ffffff94 PARCON_NPAR_RSRC_ACTIVATION_SKIPPED
13 04/24/2012 06:27:45
12 OA 1,1 None 2 44801ff800e10018 0100ff01ffffff94 BLADE_STATUS_DEGRADED
12 04/24/2012 06:26:56
11 ILO 1,1 None 2 4b00260300e10017 010000004f96aa1e OA_REQUESTS_POWER_CHANGE
11 04/24/2012 06:26:54
Health Repository viewer
The Health Repository User Interface displays the information from the HR database. The HR database contains current state and history covering both service events and the results of error events analysis.
The following information is available in the HR display:
•
Description of each failure event on the system that results in a service request, even after a component is removed or replaced.
•
History of component identities installed in the system.
Information in the HR database is stored as installation and action records. These records are organized with component physical location as the key.
Indictment Records
Indictment refers to a record specifying that a component requires service. The component or a subcomponent may or may not be deconfigured as a result. Each indictment record contains the following information:
•
The time of the error.
•
The cause of the error.
•
The subcomponent location of the error (when analysis allows).
In cases when the failing component cannot be identified with certainty, analysis indicts the most probable component that will need to be replaced to solve the problem.
202 Using event logs
Deconfiguration is the act of disabling a component in the system. This happens when analysis finds that a component has a serious fault. A components deconfiguration status is composed of two parts:
•
“requested state” – What the user or Analysis Engine would like to have the component set to.
•
“current state” – How the component is actually configured in the system.
IMPORTANT: Deconfiguration requests for components in active nPars can not be acted on until the nPar experiences a power-off/power-on cycle.
Acquitting indictments
Acquitting refers to clearing the component indictment and deconfiguration statuses, and is done when the part is serviced. Acquittals happen automatically in the following situations:
•
Component insertion — HR will assume that a component inserted into the system has received any required service. This applies to any components contained within the inserted unit as well. For example, DIMMs and CPU sockets on an inserted blade will be acquitted. Any deconfigurations will be reversed.
•
AC power cycle or CLI poweron xfabric command — HR will assume that the required service has been accomplished for the entire complex. All FRUs and sub-FRUs will be acquitted and reconfigured.
•
Cohort acquittal — When analysis of a single fault event results in indictment or suspicion records against multiple components, the records are linked together. If one is acquitted, the acquittal will be passed to the cohort FRUs as well.
For example, if a cabled fabric link between the XFM and IOX has failed, the analysis engine will indict the cable connectors physical locations (representing the cable as the most likely component failure). Acquittal of the fabric cable connectors after cable service will acquit all for records.
•
HR test commands — The test camnet and test clocks commands will acquit all indictments specific to the test to be executed. Resources that fail the test will be re-indicted as the test completes. The test fabric command acquits each type (fabric, CAMNet,
Global Clock) of indictment before initiating the test.
NOTE: Indictments indicating faults in subcomponents not targeted by the tests will not be acquitted. For example, a blade indictment for CPU fault will not be acquitted by any of these test commands.
•
Start Link — Attempting to service a cabled link while in use will result in an indictment. The stop link command prevents these indictments and alerts caused by service actions and lights the appropriate LINK health LEDs to help identify the physical cable needing service.
The start link command clears the link health LEDs, acquits, and attempts link retraining.
•
Manual Acquittal – The HR UI includes an acquit command that uses the component physical location or resource path as a parameter. Like other acquittals, the acquittal will act on all indictments for that component.
•
Component resumes normal function.
Health Repository viewer 203
IMPORTANT: In most cases resumption of function will not cause automatic acquittal.
Component replacement, complex AC power cycle or manual acquittal is required. Examples are:
◦
BPS indicted for loss of AC input regains power input.
◦
Environmental temperature returns to within acceptable bounds.
◦
Enclosure regains sufficient power due to BPS replacement.
◦
Enclosure regains sufficient cooling due to fan replacement.
Viewing the list of indicted components
The show indict command will list the currently indicted components for the complex describing the type, physical location, indication of the cause for indictment, and timestamp.
myhost HR> show indict
System Indictment List - Mon May 18 16:06:03 2009
--------------------------------------------------
FRU Type: Blade DIMM
Location: 0x0100FF0200160A74 enclosure1/blade2/socket0/dimm16
Timestamp: Mon May 18 15:51:12 2009
Indictment State: Indicted
Requested Deconfig State: Configured
Current Deconfig State: Configured
FRU Type: CPU Socket
Location: 0x0100FF01FF00FF11 enclosure1/blade1/socket0
Timestamp: Mon May 18 16:05:57 2009
Indictment State: Indicted
Requested Deconfig State: Configured
Current Deconfig State: Configured
--- end report --- 2 records shown
Viewing deconfigured components
The show deconfig will list all components in the complex which are deconfigured or have a pending request to be deconfigured. The output includes the type, physical location, indication of the cause for indictment, and timestamp.
myhost HR> show deconfig
System Acquittal History - Mon May 18 16:11:28 2009
--------------------------------------------------
FRU Type: Blade DIMM
Location: 0x0100FF0200160A74 enclosure1/blade2/socket0/dimm16
Timestamp: Mon May 18 16:11:19 2009
Indictment State: Indicted
Requested Deconfig State: Configured
Current Deconfig State: Deconfigured
FRU Type: CPU Socket
Location: 0x0100FF01FF00FF11 enclosure1/blade1/socket0
Timestamp: Mon May 18 16:11:19 2009
Indictment State: Indicted
Requested Deconfig State: Configured
Current Deconfig State: Deconfigured
204 Using event logs
--- end report --- 2 records shown
NOTE: The requested and current deconfiguration states shown in the examples above are not the same. This can happen when requested deconfiguration changes are not be acted on until the n-Par containing the component in question is rebooted.
NOTE: DIMMs may be deconfigured without being indicted. Some faults isolated to CPU sockets or blades may require deconfiguration of whole or portions of memory subsystems by physically deconfiguring the DIMMs supported by that resource.
Viewing indictment acquittals
The show aquit command will list all components in the complex which have had indictments acquitted. The output includes the type, physical location, indication of the cause for indictment, and timestamp.
System Acquittal History - Mon May 18 16:11:28 2009
--------------------------------------------------
FRU Type: Blade DIMM
Location: 0x0100FF0200160A74 enclosure1/blade2/socket0/dimm16
Timestamp: Mon May 18 16:11:19 2009
Indictment State: Acquitted
Requested Deconfig State: Configured
Current Deconfig State: Deconfigured
FRU Type: CPU Socket
Location: 0x0100FF01FF00FF11 enclosure1/blade1/socket0
Timestamp: Mon May 18 16:11:19 2009
Indictment State: Acquitted
Requested Deconfig State: Configured
Current Deconfig State: Deconfigured
--- end report --- 2 records shown
NOTE: The requested and current deconfiguration states shown in the examples above are not the same. This can happen when requested deconfiguration changes are not be acted on until the n-Par containing the component in question is rebooted.
Viewing recent service history
You can view the recent service history using the show acquit command. To view the installation history for the acquitted locations, enter show <physical location>|<resource path>
Physical Location installation and health history
The show <physical location>|<resource path> command returns the entire stored installation and health history of a physical location. This includes up to two previous components installed at this location. The history will include previous indictments, with or without acquittals, rather than just the indictments.
2009-11-18 21:50 hpsl18-4 HR> show 0x0B00FFFF01FFFF69
Location Installation/Health History - Sat Nov 18 21:51:04 2009
--------------------------------------------------
FRU Type: IO Expander Midplane
Location: 0x0B00FFFF01FFFF69 enclosure11/midplane0
Timestamp: Thu Sep 10 18:34:11 2009
Indictment State: Indicted
Requested Deconfig State: Configured
Current Deconfig State: Configured
--- Install History 1 ---
Discovery: Startup (| Runtime Insertion | Indictment)
Health Repository viewer 205
Timestamp: Thu Sep 10 18:34:12 2009
Serial Num: MYJ84901ZH
Parent Serial: 1Z34AB7890
Part Num: AH342-60003
Spare Part Num: AH342-60003
Manufacturer: HP
Product Name: CB900s i2
Board Serial Num: MYJ84901ZH
- FRU Data Extension -
Name: value
Name2: Value2
(Detailed info about FRU is provided here if it exists. E.g. For CPUs max freq will be provided here. If no data, entire section omitted.)
--- Action - Indict ---
Event No: 4000
Provider: some_provider_name
Reason: Text reason of problem from WS-Man alert.
Reason: 3:1
Description: Text description of problem from ws-man Alert.
Bundle ID: 0x400000000000010D
Alert ID: 7400020091023220043
- Indicted / Acquitted -
Type Timestamp Entity Reason
Ind Thu Sep 10 18:34:11 2009 CAE See reason above.
Acq Thu Sep 10 18:34:11 2009 User User request
---
- Supporting Symptoms -
Reason: Text reason of supporting symptom** (not from ws-man).
- SubFru Isolation -
SubFRUs requiring service shown here. If none, section omitted.
- SubFru Deconfiguration -
Deconfig’ed subFRUs shown here. If none, section omitted.
- Related Locations -
0x0B00FFFF03FFFF54 (Cohorts. If none, section omitted.)
Subcomponent isolation and deconfiguration displays
Subcomponent isolation refers to the subcomponents of a part that can require service. In these cases, the component is indicted because the only way the subcomponent can be serviced is by removing and servicing the entire component.
Subcomponent deconfigurations are also possible. These are indications of subcomponent failures.
The show <location> and show fru command output may contain “SubFru Isolation” and
“SubFru Deconfiguration” sections to communicate subcomponent health information. If a subcomponent deconfiguration event occurs, the corresponding subcomponent Isolation will also be set, which triggers an indictment of the parent component.
206 Using event logs
B Time zone settings
Universal time zone settings
NOTE: Time zones must be entered exactly as they appear.
The following table provides the Universal time zone settings that are supported by the Onboard
Administrator.
CET
CST6CDT
EET
EST
EST5EDT
Etc/GMT
Etc/GMT0
Etc/GMT-0
Etc/GMT+0
Etc/GMT-1
Etc/GMT+1
Etc/GMT-2
Etc/GMT+2
Etc/GMT-3
Etc/GMT+3
Etc/GMT-4
Etc/GMT+4
Etc/GMT-5
Etc/GMT+5
Etc/GMT-6
Etc/GMT+6
Etc/GMT-7
Etc/GMT+7
Etc/GMT-8
Etc/GMT+8
Etc/GMT-9
Etc/GMT+9
Etc/GMT-10
Etc/GMT+10
Etc/GMT-11
Etc/GMT+11
Etc/GMT-12
Etc/GMT+12
Etc/GMT-13
Etc/GMT-14
Etc/Greenwich
Etc/UCT
Etc/Universal
Etc/UTC
Etc/Zulu
GMT
Greenwich
HST
MET
MST
MST7MDT
Navajo
PST8PDT
UCT
Universal
UTC
WET
W-SU
Zulu
Africa time zone settings
NOTE: Time zones must be entered exactly as they appear.
The following table provides the African time zone settings that are supported by the Onboard
Administrator.
Africa/Abidjan
Africa/Accra
Africa/Addis_Ababa
Africa/Algiers
Africa/Asmera
Africa/Bamako
Africa/Bangui
Africa/Banjul
Africa/Bissau
Africa/Blantyre
Africa/Brazzaville
Africa/Bujumbura
Africa/Cairo
Africa/Casablanca
Africa/Ceuta
Africa/Conakry
Africa/Dakar
Africa/Dar_es_Salaam
Africa/Djibouti
Africa/Douala
Africa/El_Aaiun
Africa/Freetown
Africa/Gaborone
Africa/Harare
Africa/Johannesburg
Africa/Kampala
Africa/Khartoum
Africa/Kigali
Africa/Kinshasa
Africa/Lagos
Africa/Libreville
Africa/Lome
Africa/Luanda
Africa/Lubumbashi
Africa/Lusaka
Africa/Malabo
Africa/Maputo
Africa/Maseru
Africa/Mbabane
Africa/Mogadishu
Africa/Monrovia
Africa/Nairobi
Africa/Ndjamena
Africa/Niamey
Africa/Nouakchott
Africa/Ouagadougou
Africa/Porto-Novo
Africa/Sao_Tome
Africa/Timbuktu
Africa/Tripoli
Africa/Tunis
Africa/Wjndhoek
Egypt
Libya
Universal time zone settings 207
Americas time zone settings
NOTE: Time zones must be entered exactly as they appear.
The following table provides the Americas time zone settings that are supported by the Onboard
Administrator.
America/Adak
America/Anchorage
America/Anguilla
America/Antigua
America/Araguaina
America/Aruba
America/Asuncion
America/Atka
America/Barbados
America/Belem
America/Belize
America/Boa_Vista
America/Bogota
America/Boise
America/Buenos_Aires
America/Cambridge_Bay
America/Cancun
America/Caracas
America/Catamarca
America/Cayenne
America/Cayman
America/Chicago
America/Chihuahua
America/Cordoba
America/Costa_Rica
America/Cuiaba
America/Curacao
America/Dawson
America/Dawson_Creek
America/Denver
America/Detroit
America/Dominica
America/Edmonton
America/Indiana/Knox
America/Indiana/Marengo
America/Indianapolis
America/Indiana/Vevay
America/Inuvik
America/Iqaluit
America/Jamaica
America/Jujuy
America/Juneau
America/Kentucky/Louisville
America/Kentucky/Monticello
America/Knox_IN
America/La_Paz
America/Lima
America/Los_Angeles
America/Louisville
America/Maceio
America/Managua
America/Manaus
America/Martinique
America/Mazatlan
America/Mendoza
America/Menominee
America/Merida
America/Mexico_City
America/Miquelon
America/Monterrey
America/Montevideo
America/Montreal
America/Montserrat
America/Nassau
America/New_York
America/Nipigon
America/Santo_Domingo
America/Sao_Paulo
America/Scoresbysund
America/Shiprock
America/St_Johns
America/St_Kitts
America/St_Lucia
America/St_Thomas
America/St_Vincent
America/Swift_Current
America/Tegucigalpa
America/Thule
America/Thunder_Bay
America/Tijuana
America/Tortola
America/Vancouver
America/Virgin
America/Whitehorse
America/Winnipeg
America/Yakutat
America/Yellowknife
Brazil/Acre
Brazil/DeNoronha
Brazil/East
Brazil/West
Canada/Atlantic
Canada/Central
Canada/Eastern
Canada/East-Saskatchewan
Canada/Mountain
Canada/Newfoundland
Canada/Pacific
Canada/Saskatchewan
208 Time zone settings
America/Eirunepe
America/El_Salvador
America/Ensenada
America/Fortaleza
America/Fort_Wayne
America/Glace_Bay
America/Godthab
America/Goose_Bay
America/Grand_Turk
America/Grenada
America/Guadeloupe
America/Guatemala
America/Guayaquil
America/Guyana
America/Halifax
America/Havana
America/Hermosillo
America/Indiana/Indianapolis
America/Nome
America/Noronha
America/Panama
America/Pangnirtung
America/Paramaribo
America/Phoenix
America/Port-au-Prince
America/Porto_Acre
America/Port_of_Spain
America/Porto_Velho
America/Puerto_Rico
America/Rainy_River
America/Rankin_Inlet
America/Recife
America/Regina
America/Rio_Branco
America/Rosario
America/Santiago
Canada/Yukon
Chile/Continenta
Chile/EasterIsland
Cuba
Jamaica
Mexico/BajaNorte
Mexico/BajaSur
Mexico/General
US/Alaska
US/Aleutian
US/Arizona
US/Central
US/Eastern
US/East-Indiana
US/Indiana-Starke
US/Michigan
US/Mountain
US/Pacific
Asia time zone settings
NOTE: Time zones must be entered exactly as they appear.
The following table provides the Asian time zone settings that are supported by the Onboard
Administrator.
Asia/Aden
Asia/Almaty
Asia/Amman
Asia/Anadyr
Asia/Aqtau
Asia/Aqtobe
Asia/Ashgabat
Asia/Ashkhabad
Asia/Baghdad
Asia/Bahrain
Asia/Baku
Asia/Bangkok
Asia/Beirut
Asia/Bishkek
Asia/Damascus
Asia/Dhaka
Asia/Dili
Asia/Dubai
Asia/Dushanbe
Asia/Gaza
Asia/Harbin
Asia/Hong_Kong
Asia/Hovd
Asia/Irkutsk
Asia/Istanbul
Asia/Jakarta
Asia/Jayapura
Asia/Jerusalem
Asia/Krasnoyarsk
Asia/Kuala_Lumpur
Asia/Kuching
Asia/Kuwait
Asia/Macao
Asia/Magadan
Asia/Manila
Asia/Muscat
Asia/Nicosia
Asia/Novosibirsk
Asia/Omsk
Asia/Phom_Penh
Asia/Pyongyang
Asia/Qatar
Asia/Saigon
Asia/Samarkand
Asia/Seoul
Asia/Shanghai
Asia/Singapore
Asia/Taipei
Asia/Tashkent
Asia/Yakutsk
Asia/Yekaterinburg
Asia/Yerevan
Hongkong
Iran
Israel
Japan
Asia/Tbilisi
Asia/Tehran
Asia/Tel_Aviv
Asia/Thimbu
Mideast/Riyadh87
Mideast/Riyadh88
Mideast/Riyadh89
PRC
Asia/Thimphu
Asia/Tokyo
ROC
ROK
Asia/Ujung_Pandang Singapore
Asia time zone settings 209
Asia/Brunei
Asia/Calcutta
Asia/Chungking
Asia/Colombo
Asia/Dacca
Asia/Kabul
Asia/Kamchatka
Asia/Karachi
Asia/Kashgar
Asia/Katmandu
Asia/Rangoon
Asia/Riyadh
Asia/Riyadh87
Asia/Riyadh88
Asia/Riyadh89
Asia/Ulaanbaatar
Asia/Ulan_Bator
Asia/Urumqi
Asia/Vientiane
Asia/Vladivostok
Turkey
Oceanic time zone settings
NOTE: Time zones must be entered exactly as they appear.
The following table provides the Oceanic time zone settings that are supported by the Onboard
Administrator.
Atlantic/Azores
Atlantic/Bermuda
Atlantic/Canary
Atlantic/Cape_Verde
Atlantic/Faeroe
Atlantic/Jan_Mayen
Atlantic/Madeira
Atlantic/Reykjavik
Atlantic/South_Georgia
Atlantic/Stanley
Atlantic/St_Helena
Australia/ACT
Australia/Adelaide
Australia/Brisbane
Australia/Broken_Hill
Australia/Canberra
Australia/Darwin
Australia/Hobart
Australia/LHI
Australia/Lindeman
Australia/Lord_Howe
Australia/Melbourne
Australia/North
Australia/NSW
Australia/Perth
Australia/Queensland
Australia/South
Australia/Sydney
Australia/Tasmania
Australia/Victoria
Australia/West
Australia/Yancowina
Iceland
Indian/Antananarivo
Indian/Chagos
Indian/Christmas
Indian/Cocos
Indian/Comoro
Indian/Kerguelen
Indian/Mahe
Indian/Maldives
Indian/Mauritius
Indian/Mayotte
Indian/Reunion
Kwajalein
NZ
NZ-CHAT
Pacific/Apia
Pacific/Auckland
Pacific/Chatham
Pacific/Easter
Pacific/Efate
Pacific/Enderbury
Pacific/Fakaofo
Pacific/Fiji
Pacific/Funafuti
Pacific/Galapagos
Pacific/Gambier
Pacific/Guadalcanal
Pacific/Guam
Pacific/Honolulu
Pacific/Johnston
Pacific/Kiritimati
Pacific/Kosrae
Pacific/Kwajalein
Pacific/Majuro
Pacific/Marquesas
Pacific/Midway
Pacific/Nauru
Europe time zone settings
NOTE: Time zones must be entered exactly as they appear.
Pacific/Niue
Pacific/Norfolk
Pacific/Noumea
Pacific/Pago_Pago
Pacific/Palau
Pacific/Pitcairn
Pacific/Ponape
Pacific/Port_Moresby
Pacific/Rarotonga
Pacific/Saipan
Pacific/Samoa
Pacific/Tahiti
Pacific/Tarawa
Pacific/Tongatapu
Pacific/Truk
Pacific/Wake
Pacific/Wallis
Pacific/Yap
US/Hawaii
US/Samoa
210 Time zone settings
The following table provides the European time zone settings that are supported by the Onboard
Administrator.
Eire
Europe/Amsterdam
Europe/Andorra
Europe/Athens
Europe/Belfast
Europe/Belgrade
Europe/Berlin
Europe/Bratislava
Europe/Brussels
Europe/Bucharest
Europe/Budapest
Europe/Chisinau
Europe/Copenhagen
Europe/Dublin
Europe/Gibraltar
Europe/Helsinki
Europe/Istanbul
Europe/Kaliningrad
Europe/Kiev
Europe/Lisbon
Europe/Ljubljana
Europe/London
Europe/Luxembourg
Europe/Madrid
Europe/Malta
Europe/Minsk
Europe/Monaco
Europe/Moscow
Europe/Nicosia
Europe/Oslo
Europe/Paris
Europe/Prague
Europe/Riga
Europe/Rome
Europe/Samara
Europe/San_Marino
Europe/Sarajevo
Europe/Simferopol
Europe/Skopje
Europe/Sofia
Europe/Stockholm
Europe/Tallinn
Europe/Tirane
Europe/Tiraspol
Europe/Uzhgorod
Europe/Vaduz
Europe/Vatican
Europe/Vienna
Europe/Vilnius
Europe/Warsaw
Europe/Zagreb
Europe/Zaporozhye
Europe/Zurich
GB
GB-Eire
Poland
Portugal
Polar time zone settings
NOTE: Time zones must be entered exactly as they appear.
The following table provides the Polar time zone settings that are supported by the Onboard
Administrator.
Antarctica/Casey
Antarctica/Davis
Antarctica/DumontDUrville
Antarctica/Mawson
Antarctica/McMurdo
Antarctica/Palmer
Antarctica/South_Pole
Antarctica/Syowa
Antarctica/Vostok
Arctic/Longyearbyen
Polar time zone settings 211
Standard terms, abbreviations, and acronyms
MAC
NIC
NTP
OS
PDU
PKCS
PXE
RBSU
HTTPS
IA
ICMP iLO 3
IOX
IP
LDAP
LED
RIBCL
SNMP
SOAP
SSH
SSO
TFTP
UEFI
UID
URI
URL
ELS
FRU
FTP
GPSM
GUI
HP SIM
HR
HTTP
BIOS
CA
CAE
CPU
DDNS
DHCP
DNS
EBIPA
Basic input/output system.
certificate authority.
Core Analysis Engine.
Central processing unit.
Dynamic domain name system.
Dynamic host configuration protocol.
Domain name system.
Enclosure bay IP addressing.
Error Logging Services.
Field replaceable unit.
File transfer protocol.
Global partition services module.
Graphical user interface.
HP Systems Insight Manager.
Health Repository.
Hypertext transfer protocol.
Hypertext transfer protocol secure sockets.
Interface adapter.
Internet control message protocol.
Integrated Lights-Out 3.
I/O expansion enclosure.
Internet protocol.
Lightweight directory access protocol.
Light-emitting diode
Media access control.
Network interface controller.
Network time protocol.
Operating system.
Power distribution unit.
Public-key cryptography standards.
Preboot execution environment.
ROM-based setup utility.
Remote Insight board command language.
Simple network management protocol.
Simple object access protocol.
Secure Shell.
Single sign-on.
Trivial file transfer protocol.
Universal extensible firmware interface.
unit identification.
Uniform resource identifier.
uniform resource locator.
212 Standard terms, abbreviations, and acronyms
Xbar
XFM
XML
Crossbar.
Xbar Fabric module.
Extensible markup language.
213
Index
A
account authentication,
account level,
ACQUIT,
ADD EBIPA,
ADD HPSIM CERTIFICATE,
ADD LDAP CERTIFICATE,
ADD LDAP GROUP,
ADD OA DNS,
ADD SNMP TRAPRECEIVER,
ADD SSHKEY,
ADD TRUSTED HOST,
ADD USER,
adding a user account,
Africa time zone,
Americas time zone,
Archive storage commands,
Asia time zone,
ASSIGN,
ASSIGN FOR LDAP,
ASSIGN INTERCONNECT,
ASSIGN OA,
ASSIGN OA LDAP GROUP,
ASSIGN PARCON_ADMIN,
ASSIGN PARTITION ,
authorized reseller
HP contact information,
Technical support,
B
Blade management commands,
BO,
C
CL,
CLEAR ARCHIVE,
CLEAR FPL,
CLEAR INTERCONNECT SESSION,
CLEAR NTP,
CLEAR PARTITION CONSOLELOG,
CLEAR SCREEN,
CLEAR SEL,
CLEAR SSHKEY,
CLEAR SYSLOG,
CLEAR VC MODE,
CLI (Command Line Interface)
Command line overview,
CLI UPDATE NPARTITION,
CO,
Complex management commands,
CONNECT ENCLOSURE,
CONNECT INTERCONNECT,
CONNECT PARTITION,
COPY,
Core Analysis Engine commands,
214 Index
D
Debug commands,
DECONFIGURE,
DIMMERR,
Directory (LDAP) commands,
DISABLE ALERTMAIL,
DISABLE CRL,
DISABLE EBIPA,
DISABLE ENCLOSURE_IP_MODE,
DISABLE GUI_LOGIN_DETAIL,
DISABLE HTTPS,
DISABLE LDAP,
DISABLE LLF,
DISABLE NTP,
DISABLE OSDEBUGGER,
DISABLE SECURESH,
DISABLE SNMP,
DISABLE STRONG PASSWORDS,
DISABLE SYSLOG REMOTE,
DISABLE TELNET,
DISABLE TRUSTED HOST,
DISABLE TWOFACTOR,
DISABLE USER,
DISABLE WSMANAGEMENT,
DISABLE XMLREPLY,
document related documentation,
documentation
HP website,
DOWNLOAD CA CERTIFICATE,
DOWNLOAD CONFIG,
DOWNLOAD CONFIG using USB key,
DOWNLOAD HPSIM CERTIFICATE,
DOWNLOAD LDAP CERTIFICATE,
DOWNLOAD OA CERTIFICATE,
DOWNLOAD PARCONFIG,
DOWNLOAD SSHKEY,
DOWNLOAD USER CERTIFICATE,
E
ENABLE ALERTMAIL,
ENABLE EBIPA,
ENABLE ENCLOSURE_IP_MODE,
ENABLE GUI_LOGIN_DETAIL,
ENABLE HTTPS,
ENABLE LDAP,
ENABLE LLF,
ENABLE NTP,
ENABLE OSDEBUGGER,
ENABLE SECURESH,
ENABLE SNMP,
ENABLE STRONG PASSWORDS,
ENABLE SYSLOG REMOTE,
ENABLE TELNET,
ENABLE TRUSTED HOST,
ENABLE USER,
ENABLE XMLPREPLY,
Enclosure Bay IP Addressing (EBIPA) commands,
enclosure DVD commands,
enclosure information,
enclosure management commands,
Enclosure network configuration commands,
ENSABLE WSMANAGEMENT,
Error Logging Services commands,
error messages,
errors, fan,
errors, power supply failure,
errors, server blade failure,
Europe time zone,
event notifications, defining,
EXIT,
F
Firmware effects messages,
Firmware update bundles,
commands,
firmware update
Affected OS commands,
FAQ,
introduction,
known issues,
services unavailable,
FORCE TAKEOVER,
FPL,
G
general commands,
General management commands,
GENERATE CERTIFICATE,
Generate certificate prompts,
Group Administration,
H
Health Repository commands,
Health Repository viewer,
acquitting,
history,
indicted list,
indictment acquittals,
indictment records,
subcomponent isolation,
viewing defconfigured,
HELP,
help resources,
HISTORY,
HP SIM commands,
I
ICAPMODIFY,
ICAPSTATUS,
INDICT,
Integrity blade restrictions,
Interconnect management commands,
IOX enclosure management commands,
L
LDAP accounts,
Legacy console commands,
local access,
local user accounts,
Log viewer commands,
LOGOUT,
O
Oceanic time zone,
P
PARCREATE,
PARDEFAULT,
PARMODIFY,
PARPERM,
PARREMOVE,
PARSTATUS,
Partition creation commands,
Partition management commands,
PC/PE,
PING,
polar time zone,
POWEROFF INTERCONNECT,
POWEROFF PARTITION,
POWEROFF XFABRIC,
POWERON INTERCONNECT,
POWERON PARTITION,
POWERON XFABRIC,
privilege levels,
Q
QUIT,
R
rack commands,
rack settings,
REBOOT PARTITION,
related documentation,
remote access,
remote syslog commands,
remote system logging,
REMOVE CA CERTIFICATE,
REMOVE EBIPA,
REMOVE HPSIM CERTIFICATE,
REMOVE LDAP CERTIFICATE,
REMOVE LDAP GROUP,
REMOVE OA DNS,
REMOVE SNMP TRAPRECEIVER,
REMOVE TRUSTED HOST,
REMOVE USER,
REMOVE USER CERTIFICATE,
RESTART COMPLEX,
RESTART INTERCONNECT,
RESTART OA ,
restrictions, Integrity blade,
215
restrictions, Server blade,
RS,
S
Secure Shell session,
SEL,
serial port,
server blade failure errors,
Server blade restrictions,
SET ALERTMAIL MAILBOX,
SET ALERTMAIL SENDERDOMAIN,
SET ALERTMAIL SM,
SET BLADE POWERDELAY,
SET BLADE UID,
SET COMPLEX NAME,
SET DATE,
SET DEVICE SERIAL_NUMBER BLADE,
SET DISPLAY,
SET DVD UID,
SET EBIPA,
SET ENCLOSURE ASSET,
SET ENCLOSURE NAME,
SET ENCLOSURE PART NUMBER,
SET ENCLOSURE PDU TYPE,
SET ENCLOSURE SERIAL_NUMBER,
SET ENCLOSURE UID,
SET FACTORY,
SET HPSIM TRUST MODE,
SET INTERCONNECT POWERDELAY,
SET INTERCONNECT UID,
SET IOX UID,
SET IPCONFIG,
SET LDAP GROUP ACCESS,
SET LDAP GROUP DESCRIPTION,
SET LDAP NAME MAP,
SET LDAP PORT,
SET LDAP SEARCH,
SET LDAP SERVER,
SET LLF INTERVAL,
SET MINIMUM PASSWORD LENGTH,
SET NIC,
SET NTP PRIMARY,
SET NTP SECONDARY,
SET OA GATEWAY,
SET OA NAME,
SET OA UID,
SET PARTITION DVD,
SET PASSWORD,
SET POWER LIMIT,
SET POWER MODE,
SET POWER SAVINGS,
SET RACK NAME,
SET REMOTE SYSLOG PORT,
SET REMOTE SYSLOG SERVER,
SET SCRIPT MODE,
SET SESSION TIMEOUT,
SET SNMP COMMUNITY,
SET SNMP CONTACT,
SET SNMP LOCATION,
216 Index
SET TIME ZONE,
SET USER ACCESS,
SET USER CONTACT,
SET USER FULLNAME,
SET USER PASSWORD,
SET XFM UID,
SHOW ACQUIT,
SHOW ALL,
SHOW ARCHIVE,
SHOW BLADE INFO,
SHOW BLADE LIST,
SHOW BLADE NAMES,
SHOW BLADE PORT MAP,
SHOW BLADE POWERDELAY,
SHOW BLADE STATUS,
SHOW BLADE TEMP,
SHOW CA CERTIFICATE,
SHOW CAE,
SHOW COMPLEX INFO,
SHOW COMPLEX STATUS,
SHOW CONFIG,
SHOW DATE,
SHOW DECONFIG,
SHOW DEVICE SERIAL_NUMBER BLADE,
SHOW DISPLAY EVENTS,
SHOW DVD INFO,
SHOW DVD STATUS,
SHOW EBIPA,
SHOW ENCLOSURE FAN,
SHOW ENCLOSURE INFO,
SHOW ENCLOSURE LCD,
SHOW ENCLOSURE POWERSUPPLY,
SHOW ENCLOSURE STATUS,
SHOW ENCLOUSRE TEMP,
SHOW ERRDUMP,
SHOW for the HR,
SHOW FPL,
SHOW FRU,
SHOW GPSM INFO,
SHOW GPSM STATUS,
SHOW HPSIM INFO,
SHOW HR,
SHOW INDICT,
SHOW INFO,
SHOW INTERCONNECT INFO,
SHOW INTERCONNECT LIST,
SHOW INTERCONNECT PORT MAP,
SHOW INTERCONNECT POWERDELAY,
SHOW INTERCONNECT SESSION,
SHOW INTERCONNECT STATUS,
SHOW IOX INFO,
SHOW IOX LIST,
SHOW IOX POWER,
SHOW IOX STATUS,
SHOW LDAP CERTIFICATE,
SHOW LDAP GROUP,
SHOW LDAP INFO,
SHOW LIVELOGS,
SHOW NETWORK,
SHOW OA ,
SHOW OA CERTIFICATE,
SHOW OA INFO,
SHOW OA NETWORK,
SHOW OA STATUS,
SHOW PARTITION CONSOLELOG,
SHOW PARTITION DVD,
SHOW PARTITION INFO,
SHOW PASSWORD SETTINGS,
SHOW POWER,
SHOW RACK NAME,
SHOW SEL,
SHOW SESSION TIMEOUT,
SHOW SNMP,
SHOW SSHFINGERPRINT,
SHOW SSHKEY,
SHOW SYSLOG,
SHOW SYSLOG OA,
SHOW SYSLOG SETTINGS,
SHOW TOPOLOGY,
SHOW TWOFACTOR INFO,
SHOW USBKEY,
SHOW USER,
SHOW USER SESSIONS,
SHOW VCMODE,
SHOW XFM INFO,
SHOW XFM LIST,
SHOW XFM STATUS,
SLEEP,
syntax,
system event log,
T
TC,
technical support
Before you contact HP,
HP contact information,
Technical support,
Telnet session,
terminal emulator session,
TEST ALERTMAIL,
TEST CAMNET,
TEST CLOCKS,
TEST FABRIC,
TEST LDAP,
TEST SNMP,
TEST SYSLOG,
TEST WSMAN,
time zones,
TOC PARTITION,
Two-Factor Authentication commands,
typographic conventions,
U
UNASSIGN,
UNASSIGN FOR LDAP,
UNASSIGN OA,
UNASSIGN OA LDAP GROUP,
UNASSIGN PARCON_ADMIN ,
UNASSIGN PARTITION ,
universal time zone,
UPDATE FIRMWARE,
UPDATE SHOW ,
UPDATE SHOW FIRMWARE,
UPDATE SHOW NPARTITION,
UPLOAD CONFIG,
UPLOAD CONFIG using USB key,
UPLOAD DEBUG,
UPLOAD PARCONFIG,
UPLOAD SYSLOG,
USB key command
DOWNLOAD CONFIG using USB key,
UPLOAD CONFIG using USB key,
User account commands,
V
VPARBOOT,
VPARMODIFY,
VPARREMOVE,
VPARRESET,
VPARSTATUS,
W
warnings,
websites product manuals,
217
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
Onboard Administrator Command Line Interface
Remote and local access
User account management
Two-factor authentication
Directory services integration
Enclosure management
Blade management
Interconnect management
USB support
Health Repository
Frequently asked questions
You can access the CLI remotely by using an SSH client, such as PuTTY, to connect to the Onboard Administrator's IP address. See page 11 in the viewed document for more information on remote access.
The Onboard Administrator supports different access levels and privileges for users, including Administrator, Operator, and User. Refer to page 13 of the viewed document for details.
You can enable strong passwords by using the 'ENABLE STRONG PASSWORDS' command. See page 24 of the viewed document.
You can enable two-factor authentication by using the 'ENABLE TWOFACTOR' command. Refer to page 31 in the viewed document.
You can configure the enclosure network settings using commands such as 'SET OA GATEWAY', 'SET OA NAME', and 'SET OA UID'. See page 65 of the viewed document.
