XCC Book
XCC Book
Gen)
User's Guide
Note: Before using this information, read the general information in Appendix B “Notices” on page 203.
It is the follow-on to the Integrated Management Module II (IMM2) service processor that consolidates the
service processor functionality, Super I/O, video controller, and remote presence capabilities into a single
chip on the server system board. It provides features such as the following:
• Choice of a dedicated or shared Ethernet connection for systems management
• Support for HTML5
• Support for access via XClarity Mobile
• XClarity Provisioning Manager
• Remote configuration using XClarity Essentials or XClarity Controller CLI.
• Capability for applications and tools to access the XClarity Controller either locally or remotely
• Enhanced remote-presence capabilities.
• REST API (Redfish schema) support for additional web-related services and software applications.
Note: The XClarity Controller currently supports Redfish Scalable Platforms Management API
Specification 1.0.2 and schema 2016.2
Notes:
• In the XClarity Controller web interface, BMC is used in referring to the XCC.
• A dedicated systems-management network port may not be available on some ThinkSystem servers; for
these servers access to the XClarity Controller is only available through a network port that is shared with
the server operating system.
• For Flex servers, the Chassis Management Module (CMM) is the primary management module for
systems-management functions. Access to the XClarity Controller is available through the network port on
the CMM.
This document explains how to use the functions of the XClarity Controller in a ThinkSystem server. The
XClarity Controller works with the XClarity Provisioning Manager and UEFI to provide systems-management
capability for ThinkSystem servers.
Note: The first time you access the Support Portal, you must choose the product category, product family,
and model numbers for your server. The next time you access the Support Portal, the products you selected
initially are preloaded by the website, and only the links for your products are displayed. To change or add to
your product list, click the Manage my product lists link. Changes are made periodically to the website.
Procedures for locating firmware and documentation might vary slightly from what is described in this
document.
1. Go to http://datacentersupport.lenovo.com.
2. Under Support, select Data Center.
3. When the content is loaded, select Servers.
4. Under Select Series, first select the particular server hardware series, then under Select SubSeries,
select the particular server product subseries, and finally, under Select Machine Type select the
particular machine type.
Event Logs
• IPMI SEL
• Human Readable Log
• Audit Log
Environmental Monitoring
• Agent Free Monitoring
• Sensor Monitoring
RAS
• Virtual NMI
• Automatic Firmware Recovery
• Automated promotion of backup firmware
• POST Watchdog
• OS Loader Watchdog
• Blue Screen Capture (OS Failure)
• Embedded Diagnostic Tools
Network Configuration
• IPv4
• IPv6
• IP Address, Subnet Mask, Gateway
• IP Address Assignment Modes
• Host name
• Programmable MAC address
• Dual MAC Selection (if supported by server hardware)
• Network Port Reassignments
• VLAN Tagging
Network Protocols
• DHCP
• DNS
• DDNS
• HTTP/HTTPS
• SNMPv3
• SNMPv1 (Traps only)
• SSL
• SSH
• SMTP
• LDAP client
• NTP
• SLP
• SSDP
Chapter 1. Introduction 3
Alerts
• PET Traps
• CIM Indication
• SNMP TRAPs
• E-mail
• Redfish events
Serial Redirection
• IPMI SOL
• Serial port configuration
Security
• XClarity Controller Core Root of Trust for Measurement (CRTM)
• Digitally signed firmware updates
• Role Based Access Control (RBAC)
• Local User Accounts
• LDAP/AD User Accounts
• Secure Rollback of Firmware
• Chassis intrusion detection (only available on some server models)
• XCC remote assertion of UEFI TPM Physical Presence
• Audit logging of configuration changes and server actions
• Public-key (PK) Authentication
• System Retire/Repurpose
Remote Presence
• Remote Disk on Card (RDOC): Virtual Media mounting of remote ISO/IMG files via CIFS, NFS, HTTP,
HTTPS, FTP, SFTP, and LOCAL
Power Management
• Real time Power Meter
License Management
• Activation Key Validation and Repository
Firmware Updates
• Agent Free Update
• Remote Update
Alerts
• Syslog
Remote Presence
• Remote KVM
Serial Redirection
• Serial Redirection via SSH
Security
• Security Key Lifecycle Manager (SKLM)
• IP address blocking
Power Management
• Real time Power Graphics
• Historical Power Counters
• Temperature Graphics
All of the XClarity Controller Standard and Advanced Level features plus:
RAS
• Boot Capture
Remote Presence
• Quality/Bandwidth Control
• Virtual Console Collaboration (six users)
• Virtual Console Chat
• Virtual Media
– Mounting of remote ISO/IMG files via remote console
– Mounting file from Network: - Mount an ISO or IMG image file from a file server ( HTTPS, CIFS, NFS ) to
the host as a DVD or USB drive
Power Management
• Power Capping
Chapter 1. Introduction 5
• OOB Performance Monitoring - System Performance metrics
The XClarity Controller web interface requires one of the following web browsers:
Note: Support for the remote console feature is not available through the browser on mobile device
operating systems.
The browsers listed above match those currently supported by the XClarity Controller firmware. The XClarity
Controller firmware may be enhanced periodically to include support for other browsers.
Depending upon the version of the firmware in the XClarity Controller, web browser support can vary from
the browsers listed in this section. To see the list of supported browsers for the firmware that is currently on
the XClarity Controller, click the Supported Browsers menu list from the XClarity Controller login page.
For increased security, only high strength ciphers are now supported when using HTTPS. When using
HTTPS, the combination of your client operating system and browser must support one of the following
cipher suites:
• ECDHE-ECDSA-AES256-GCM-SHA384
• ECDHE-ECDSA-AES256-SHA384
• ECDHE-ECDSA-AES256-SHA
• ECDHE-ECDSA-AES128-GCM-SHA256
• ECDHE-ECDSA-AES128-SHA256
• ECDHE-ECDSA-AES128-SHA
• ECDHE-RSA-AES256-GCM-SHA384
• ECDHE-RSA-AES256-SHA384
• ECDHE-RSA-AES128-GCM-SHA256
• ECDHE-RSA-AES128-SHA256
By default, the chosen language for the XClarity Controller web interface is English. The interface is capable
of displaying multiple languages. These include the following:
• French
• German
• Italian
• Japanese
• Korean
• Portuguese (Brazil)
• Russian
• Simplified Chinese
• Spanish (international)
• Traditional Chinese
To choose the language of your preference, click the arrow beside the currently selected language. A drop-
down menu will appear to let you choose your preferred language.
Text strings that are generated by the XClarity Controller firmware are displayed in the language dictated by
the browser. If the browser specifies a language other than one of the translated languages listed above, the
text is displayed in English. In addition, any text string that is displayed by the XClarity Controller firmware,
but is not generated by the XClarity Controller (for example messages generated by UEFI, PCIe adapters,
etc…) are displayed in English.
The input of language-specific text other than English, such as the Trespass message is currently not
supported. Only text typed in English is supported.
MIBs Introduction
Use the information in this topic to access Management Information Base.
The SNMP MIBs can be downloaded from the https://support.lenovo.com/ (Search by machine type on the
portal). It includes the following four MIBs.
• The SMI MIB describes the Structure of Management Information for the Lenovo Data Center Group.
• The Product MIB describes the object identifier for Lenovo Products.
• The XCC MIB provides the inventory and monitoring information for Lenovo XClarity Controller.
• The XCC Alert MIB defines traps for alert conditions detected by Lenovo XClarity Controller.
Note: The import order for the four MIBs is SMI MIB → Product MIB → XCC MIB → XCC Alert MIB.
Chapter 1. Introduction 7
Notices used in this document
Use this information to understand the notices that are used in this document.
The XClarity Controller combines service processor functions, a video controller, and remote presence
function in a single chip. To access the XClarity Controller remotely by using the XClarity Controller web
interface, you must first log in. This chapter describes the login procedures and the actions that you can
perform from the XClarity Controller web interface.
The XClarity Controller supports static and Dynamic Host Configuration Protocol (DHCP) IPv4 addressing.
The default static IPv4 address assigned to the XClarity Controller is 192.168.70.125. The XClarity Controller
is initially configured to attempt to obtain an address from a DHCP server, and if it cannot, it uses the static
IPv4 address.
The XClarity Controller also supports IPv6, but it does not have a fixed static IPv6 IP address by default. For
initial access to the XClarity Controller in an IPv6 environment, you can either use the IPv4 IP address or the
IPv6 link-local address. The XClarity Controller generates a unique link-local IPv6 address, using the IEEE
802 MAC address by inserting two octets, with hexadecimal values of 0xFF and 0xFE in the middle of the 48-
bit MAC as described in RFC4291 and flipping the 2nd bit from the right in the first octet of the MAC address.
For example if the MAC address is 08-94-ef-2f-28-af, the link-local address would be as follows:
fe80::0a94:efff:fe2f:28af
When you access the XClarity Controller, the following IPv6 conditions are set as default:
• Automatic IPv6 address configuration is enabled.
• IPv6 static IP address configuration is disabled.
• DHCPv6 is enabled.
• Stateless auto-configuration is enabled.
The XClarity Controller provides the choice of using a dedicated systems-management network connection
(if applicable) or one that is shared with the server. The default connection for rack-mounted and tower
servers is to use the dedicated systems-management network connector.
The dedicated systems-management network connection on most servers is provided using a separate
1Gbit network interface controller. However, on some systems the dedicated systems-management network
connection may be provided using the Network Controller Sideband Interface (NCSI) to one of the network
ports of a multi-port network interface controller. In this case, the dedicated systems-management network
connection is limited to the 10/100 speed of the sideband interface. For information and any limitations on
the implementation of the management port on your system, see your system documentation.
Note: A dedicated systems-management network port might not be available on your server. If your
hardware does not have a dedicated network port, the shared setting is the only XClarity Controller setting
available.
After you start the server, you can use the XClarity Provisioning Manager to configure the XClarity Controller
network connection. The server with the XClarity Controller must be connected to a DHCP server, or the
server network must be configured to use the XClarity Controller static IP address. To set up the XClarity
Controller network connection through the Setup utility, complete the following steps:
Note: It may take up to 40 seconds after the server is connected to AC power for the power-
control button to become active.
Step 2. When the prompt <F1> System Setup is displayed, press F1. If you have set both a power-on
password and an administrator password, you must type the administrator password to access the
XClarity Provisioning Manager.
Step 3. From the XClarity Provisioning Manager main menu, select UEFI Setup.
Step 4. On the next screen, select BMC Settings; then, click Network Settings.
Step 5. There are three XClarity Controller network connection choices in the DHCP Control field:
• Static IP
• DHCP Enabled
• DHCP with Fallback
Notes:
• A dedicated systems-management network port might not be available on your server. If your
hardware does not have a dedicated network port, the shared setting is the only XClarity
Controller setting available. On the Network Configuration screen, select Dedicated (if
applicable) or Shared in the Network Interface Port field.
• To find the locations of the Ethernet connectors on your server that are used by the XClarity
Controller, see the documentation that came with your server.
Step 9. Click Save.
Step 10. Exit from the XClarity Provisioning Manager.
Notes:
• You must wait approximately 1 minute for changes to take effect before the server firmware is functional
again.
• You can also configure the XClarity Controller network connection through the XClarity Controller web
interface or command-line interface (CLI). In the XClarity Controller web interface, network connections
can be configured by clicking BMC Configuration from the left navigation panel , and then selecting
Network. In the XClarity Controller CLI, network connections are configured using several commands that
depend on the configuration of your installation.
Important: The XClarity Controller is set initially with a user name of USERID and password of PASSW0RD (with
a zero, not the letter O). This default user setting has Supervisor access. Change this user name and
password during your initial configuration for enhanced security. After making the change, you are unable to
set PASSW0RD as the login password again.
Note: In a Flex System, the XClarity Controller user accounts can be managed by a Flex System Chassis
Management Module (CMM) and might be different than the USERID/PASSW0RD combination described
above.
To access the XClarity Controller through the XClarity Controller web interface, complete the following steps:
Step 1. Open a web browser. In the address or URL field, type the IP address or host name of the XClarity
Controller to which you want to connect.
Step 2. Select the desired language from the language drop-down list.
Step 3. Type your user name and password in the XClarity Controller Login window. If you are using the
XClarity Controller for the first time, you can obtain your user name and password from your system
administrator. All login attempts are documented in the event log. Depending on how your system
administrator configured the user ID, you might need to enter a new password after logging in.
Step 4. Click Log In to start the session. The browser opens the XClarity Controller home page, as shown
in the following illustration. The home page displays information about the system that the XClarity
Controller manages plus icons indicating how many critical errors and how many warnings
are currently present in the system.
Note: When navigating the web interface, you can also click the question mark icon for online help.
Health Summary/Active Shows the current status of the major hardware components in
System Events the system.
Control the server at the operating system level. You can view
and operate the server console from your computer. The
remote console section in the XClarity Controller home page
displays a screen image with a Launch button. The right tool
bar includes the following quick actions:
Remote Console Preview
• Capture Screen
• Settings
• Recorded Videos
• Latest Failure Screen
• Select the boot device for one-time boot during next server
Boot Options restart.
• Change boot mode and boot order settings.
When configuring the XClarity Controller, the following key options are available:
• Backup and Restore
• License
• Network
• Security
• User/LDAP
Click User/LDAP under BMC Configuration to create, modify, and view user accounts, and to configure
LDAP settings.
The Local User tab shows the user accounts that are configured in the XClarity Controller, and which are
currently logged in to the XClarity Controller.
The LDAP tab shows the LDAP configuration for accessing user accounts that are kept on an LDAP server.
Click Allow logons from to select how user login attempts are authenticated. You can select one of the
following authentication methods:
• Local only: Users are authenticated by a search of the local user account configured in the XClarity
Controller. If there is no match of the user ID and password, access is denied.
• LDAP only: The XClarity Controller attempts to authenticate the user with credentials kept on an LDAP
server. The local user accounts in the XClarity Controller are not searched with this authentication method.
• Local first, then LDAP: Local authentication is attempted first. If local authentication fails; then, LDAP
authentication is attempted.
• LDAP first, then local user: LDAP authentication is attempted first. If LDAP authentication fails; then,
local authentication is attempted.
Notes:
• Only locally administered accounts are shared with the IPMI and SNMP interfaces. These interfaces do
not support LDAP authentication.
• IPMI and SNMP users can login using the locally administered accounts when the Allow logons from
field is set to LDAP only.
Complete the following fields: User name, Password, Confirm Password, and Authority Level. For further
details on the authority level, see the following section.
Supervisor
The Supervisor user authority level has no restrictions.
Read only
The Read only user authority level has read-only access and cannot perform actions such as file
transfers, power and restart actions, or remote presence functions.
Custom
The Custom user authority level allows a more customized profile for user authority with settings for the
actions that the user is allowed to perform.
When a user sets the authority level of an XClarity Controller login ID, the resulting IPMI privilege level of the
corresponding IPMI User ID is set according to the following priorities:
• If a user sets the XClarity Controller login ID authority level to Supervisor, the IPMI privilege level is set to
Administrator.
• If a user sets the XClarity Controller login ID authority level to Read Only, the IPMI privilege level is set to
User.
SNMPv3 Settings
To enable SNMPv3 access for a user, select the check box next to the SNMPv3 Settings. The following user
access options are explained:
Access type
Only GET operations are supported. The XClarity Controller does not support SNMPv3 SET operations.
SNMP3 can only perform query operations.
Address for traps
Specify the trap destination for the user. This can be an IP address or hostname. Using traps, the SNMP
agent notifies the management station about events, (for example, when a processor temperature
exceeds the limit).
Authentication protocol
Only HMAC-SHA is supported as the authentication protocol. This algorithm is used by the SNMPv3
security model for authentication.
Privacy protocol
The data transfer between the SNMP client and the agent can be protected using encryption. The
supported methods are CBC-DES and AES.
Notes: Even if repetitive strings of a password is used by an SNMPv3 user, access will still be allowed to the
XClarity Controller. Two examples are shown for your reference.
• If the password is set to “11111111” (eight-digit number containing eight 1's), the user can still access the
XClarity Controller if the password is accidentally inputted with more than eight 1’s. For example, if the
password is inputted as “1111111111 (ten-digit number containing ten 1's), access will still be granted.
The repetitive string will be considered having the same key.
• If the password is set to “bertbert”, the user can still access the XClarity Controller if the password is
accidentally inputted as “bertbertbert”. Both passwords are considered to have the same key.
For further details, refer to page 72 in the Internet Standard of RFC 3414 document (https://tools.ietf.org/html/
rfc3414).
SSH Key
The XClarity Controller supports SSH Public Key Authentication (RSA key type). To add a SSH key to the
local user account, select the check box next to the SSH Key. The following two options are provided:
Notes:
• Some of Lenovo’s tools may create a temporary user account for accessing the XClarity Controller when
the tool is run on the server operating system. This temporary account is not viewable and does not use
any of the 12 local user account positions. The account is created with a random user name (for example,
“20luN4SB”) and password. The account can only be used to access the XClarity Controller on the
internal Ethernet over USB interface, and only for the CIM-XML and SFTP interfaces. The creation and
removal of this temporary account is recorded in the audit log as well as any actions performed by the tool
with these credentials.
• For the SNMPv3 Engine ID, the XClarity Controller uses a HEX string to denote the ID. This HEX string is
converted from the default XClarity Controller host name. See the example below:
The host name "XCC-7X06-S4AHJ300" is first converted into ASCII format: 88 67 67 45 55 88 48 54 45 83
52 65 72 74 51 48 48
The HEX string is built using the ASCII format (ignore the spaces in between): 58 43 43 2d 37 58 30 36 2d
53 34 41 48 4a 33 30 30
To delete a local user account, click the trash can icon on the row of the account that you wish to remove. If
you are authorized, you can remove your own account or the account of other users, even if they are
currently logged in, unless it is the only account remaining with User Account Management privileges.
Sessions that are already in progress when user accounts are deleted will not be automatically terminated.
Aside from the use of passwords and LDAP/AD user accounts, the XClarity Controller also supports third-
party hashed passwords for authentication. The special password uses a one-way hash (SHA256) format
and is supported by the XClarity Controller web, OneCLI, and CLI interfaces. However, please note that
authentication of XCC SNMP, IPMI and CIM interfaces do not support third-party hashed passwords. Only
the OneCLI tool and XCC CLI interface can create a new account with a hashed password or perform a
hashed password update. The XClarity Controller also allows the OneCLI tool and XClarity Controller CLI
interface to retrieve the hashed password if the capability of reading hashed password is enabled.
Click Security under BMC Configuration, and scroll to the Security Password Manager section to enable
or disable the Third-party Password function. If enabled, a third-party hashed password is employed for log-
in authentication. Retrieval of the third-party hashed password from the XClarity Controller can also be
enabled of disabled.
Note: By default, the Third-party Password and Allow Third-party Password Retrieval functions are disabled.
To check if the user password is Native or a Third-party Password, click User/LDAP under BMC
Configuration for details. The information will be under the Advanced Attribute column.
Notes:
Note: While the hashed password is being set, this password will immediately take effect. The original
standard password will no longer be effective. In this example, the original standard password
Passw0rd123abc cannot be used anymore until the hashed password is deleted.
Note: While the hashed password is being set, this password will immediately take effect. The original
standard password will no longer be effective. In this example, the original standard password
Passw0rd123abc cannot be used anymore until the hashed password is deleted.
After the hashed password has been set up, remember you do not used this to login to the XClarity
Controller. When logging in, you will need to use the plaintext password. In the example shown below, the
plaintext password is “password123”.
5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
In the Web inactivity session timeout field, you can specify how long, in minutes, the XClarity Controller
waits before it disconnects an inactive web session. The maximum wait time is 1,440 minutes. If set to 0, the
web session never expires.
Note: If you leave the browser open on an XClarity Controller web page that automatically refreshes, your
web session will not automatically close due to inactivity.
Notes: In a Flex System, the account security policy settings are managed by the Flex System Chassis
Management Module (CMM) and cannot be modified through the XCC. When the CMM is used to configure
the account security policy, make note of the following:
• Unlike the XCC, the CMM does not have the Password expiration warning period (days) setting. When the
Password expiration period is configured to be longer than 5 days in the CMM, the XCC will set the
password expiration warning period to be 5 days. Conversely, if the setting is shorter than 5 days, the
password expiration warning period will be the same as the value inputted in the Password expiration
period.
• For the Maximum number of login failures (times) setting, the range set forth in the CMM is 0-100 times.
However, the range defined in the XCC is 0-10 times. Thus, when the user selects a value that exceeds 10
times in the CMM, the XCC will still set the maximum number of login failures as 10 times.
• For the Minimum password change interval (hours) setting, the range set forth in the CMM is 0-1440 hours.
However, the range defined in the XCC is 0-240 hours. Thus, when the user selects a value that exceeds
240 hours in the CMM, the XCC will still set the minimum password change interval to be 240 hours.
The following information is a description of the fields for the security settings.
Configuring LDAP
Use the information in this topic to view or change XClarity Controller LDAP settings.
Click the LDAP tab to view or modify XClarity Controller LDAP settings.
Note: The LDAP servers to be used for authentication can either be configured manually or discovered
dynamically via DNS SRV records.
• Use Pre-Configured Servers: You can configure up to four LDAP servers by entering each server's
IP address or host name if DNS is enabled. The port number for each server is optional. If this field is
left blank, the default value of 389 is used for non-secured LDAP connections. For secured
connections, the default port value is 636. You must configure at least one LDAP server.
• Use DNS to Find Servers: You can choose to discover the LDAP server(s) dynamically. The
mechanisms described in RFC2782 (A DNS RR for specifying the location of services) are used to
locate the LDAP server(s). This is known as DNS SRV. You need to specify a fully qualified domain
name (FQDN) to be used as the domain name in the DNS SRV request.
– AD Forest: In an environment with universal groups in cross domains, the forest name (set of
domains) must be configured to discover the required Global Catalogs (GC). In an environment
where cross-domain group membership does not apply, this field can be left blank.
– AD Domain: You will need to specify a fully qualified domain name (FQDN) to be used as the
domain name in the DNS SRV request.
If you wish to enable secure LDAP, click the Enable Secure LDAP check box. In order to support
secure LDAP, a valid SSL certificate must be in place and at least one SSL client trusted certificate must
be imported into the XClarity Controller. Your LDAP server must support Transport Layer Security (TLS)
version 1.2 to be compatible with the XClarity Controller secure LDAP client. For more information about
certificate handling, see “SSL certificate handling” on page 37.
2. Fill in information under Additional Parameters. Below are explanations of the parameters.
Binding method
Before you can search or query the LDAP server, you must send a bind request. This field controls
how this initial bind to the LDAP server is performed. The following bind methods are available:
• No Credentials Required
Use this method to bind without a Distinguished Name (DN) or password. This method is strongly
discouraged because most servers are configured to not allow search requests on specific user
records.
• Use Configured Credentials
Use this method to bind with the configured client DN and password.
If the initial bind is successful, a search is performed to find an entry on the LDAP server that belongs to
the user who is logging in. If necessary, a second attempt to bind is made, this time with the DN that is
retrieved from the user's LDAP record and the password that was entered during the login process. If
the second attempt to bind fails, the user is denied access. The second bind is performed only when the
No Credentials Required or Use Configured Credentials binding methods are used.
Group Filter
The Group Filter field is used for group authentication. Group authentication is attempted after the
user's credentials are successfully verified. If group authentication fails, the user's attempt to log on
is denied. When the group filter is configured, it is used to specify to which groups the XClarity
Controller belongs. This means that to succeed the user must belong to at least one of the groups
that are configured for group authentication. If the Group Filter field is left blank, group
authentication automatically succeeds. If the group filter is configured, an attempt is made to match
at least one group in the list to a group that the user belongs. If there is no match, the user fails
authentication and is denied access. If there is at least one match, group authentication is
successful.
The comparisons are case sensitive. The filter is limited to 511 characters and can consist of one or
more group names. The colon (:) character must be used to delimit multiple group names. Leading
and trailing spaces are ignored, but any other space is treated as part of the group name.
Note: The wildcard character (*) is no longer treated as a wildcard. The wildcard concept has been
discontinued to prevent security exposures. A group name can be specified as a full DN or by using
only the cn portion. For example, a group with a DN of cn=adminGroup, dc=mycompany, dc=com
can be specified using the actual DN or with adminGroup.
Nested group membership is supported only in Active Directory environments. For example, if a
user is a member of GroupA and GroupB, and GroupA is also a member of GroupC, the user is said
to be a member of GroupC also. Nested searches stop if 128 groups have been searched. Groups
in one level are searched before groups in a lower level. Loops are not detected.
Bit
position Function Explanation
0 Deny Always A user will always fail authentication. This function can be used to
block a particular user or users associated with a particular group.
1 Supervisor Access A user is given administrator privileges. The user has read/write
access to every function. If you set this bit, you do not have to
individually set the other bits.
2 Read Only Access A user has read-only access, and cannot perform any maintenance
procedures (for example, restart, remote actions, or firmware updates)
or make modifications (for example, the save, clear, or restore
functions. Bit position 2 and all other bits are mutually exclusive, with
bit position 2 having the lowest precedence. When any other bit is set,
this bit will be ignored.
3 Networking and Security A user can modify the Security, Network Protocols, Network Interface,
Port Assignments, and Serial Port configurations.
4 User Account A user can add, modify, or delete users and change the Global Login
Management Settings in the Login Profiles window.
5 Remote Console Access A user can access the remote server console.
6 Remote Console and A user can access the remote server console and the remote disk
Remote Disk Access functions for the remote server.
7 Remote Server Power/ A user can access the power on and restart functions for the remote
Restart Access server.
Bit
position Function Explanation
8 Basic Adapter A user can modify configuration parameters in the System Settings
Configuration and Alerts windows.
9 Ability to Clear Event Logs A user can clear the event logs.
Note: All users can view the event logs; but, to clear the event logs
the user is required to have this level of permission.
10 Advanced Adapter A user has no restrictions when configuring the XClarity Controller. In
Configuration addition the user has administrative access to the XClarity Controller.
The user can perform the following advanced functions: firmware
upgrades, PXE network boot, restore XClarity Controller factory
defaults, modify and restore adapter configuration from a
configuration file, and restart/reset the XClarity Controller.
11 Reserved This bit position is reserved for future use. If none of the bits are set,
the user has read-only authority. Priority is given to login permissions
that are retrieved directly from the user record.
The Read Only Access bit (position 2) is set only if all other bits are set
to zero. If the Deny Always bit (position 0) is set for any of the groups,
the user is refused access. The Deny Always bit (position 0) always has
precedence over all other bits.
If none of the bits are set, the default will be set to Read Only for the user.
Note that priority is given to login permissions retrieved directly from the user record. If the user does not
have the login permission attribute in its record, an attempt will be made to retrieve the permissions from
the group(s) that the user belongs to, and, if configured, that match the group filter. In this case the user
will be assigned the inclusive OR of all the bits for all of the groups. Similarly, the Read Only Access bit
will only be set if all the other bits are zero. Moreover, note that if the Deny Always bit is set for any of
the groups, the user will be refused access. The Deny Always bit always has precedence over every
other bit.
Note: If you give a user the ability to modify basic, networking, and/or security related adapter
configuration parameters, you should consider giving this same user the ability to restart the XClarity
Controller (bit position 10). Otherwise, without this ability, a user might be able to change parameters (for
example, IP address of the adapter), but will not be able to have them take effect.
3. Choose whether or not to Enable enhanced role-based security for Active Directory Users under
Active Directory Settings (if Use LDAP server for Authentication and Authorization mode is used),
or configure the Groups for Local Authorization (if Use LDAP server for Authentication only (with
local authorization) mode is used).
• Enable enhanced role-based security for Active Directory Users
If enhanced role-based security setting is enabled, a free-formatted server name must be configured
to act as the target name for this particular XClarity Controller. The target name can be associated
with one or more roles on the Active Directory server through a Role Based Security (RBS) Snap-In.
This is accomplished by creating managed targets, giving them specific names, and then associating
them to the appropriate roles. If a name is configured in this field, it provides the ability to define
specific roles for users and XClarity Controllers (targets) who are members of the same role. When a
The XClarity Controller uses two network controllers. One network controller is connected to the dedicated
management port and the other network controller is connected to the shared port. Each of the network
controllers is assigned its own burned in MAC address. If DHCP is being used to assign an IP address to the
XClarity Controller, when a user switches between network ports or when a failover from the dedicated
network port to the shared network port occurs, a different IP address may be assigned to the XClarity
Controller by the DHCP server. It is recommended that when using DHCP, users should use the host name
to access the XClarity Controller rather than relying on an IP address. Even if the XClarity Controller network
ports are not changed, the DHCP server could possibly assign a different IP address to the XClarity
Controller when the DHCP lease expires, or when the XClarity Controller reboots. If a user needs to access
the XClarity Controller using an IP address that will not change, the XClarity Controller should be configured
for a static IP address rather than DHCP.
Click Network under BMC Configuration to modify XClarity Controller Ethernet settings.
Ethernet Ports
This setting controls the enablement of Ethernet ports used by management controller, including the shared
and dedicated ports.
Once disabled, all Ethernet ports will not be assigned any IPv4 or IPv6 addresses, and prevents any further
changes to any Ethernet configurations.
Note: This setting does not affect the USBLAN interface or the USB management port at the front of the
server. Those interfaces have their own dedicated enablement settings.
Note: Disabling the Ethernet interface prevents access to the XClarity Controller from the external
network.
2. From the Method field, select one of the following options:
• Obtain IP from DHCP: The XClarity Controller will obtain its IPv4 address from a DHCP server.
• Use static IP address: The XClarity Controller will use the user specified value for its IPv4 address.
• First DHCP, then static IP address: The XClarity Controller will attempt to obtain its IPv4 address
from a DHCP server, but if that attempt fails, the XClarity Controller will use user specified value for its
IPv4 address.
3. In the Static address field, type the IP address that you want to assign to the XClarity Controller.
Note: The IP address must contain four integers from 0 to 255 with no spaces and separated by
periods. This field will not be configurable if the method is set to Obtain IP from DHCP.
4. In the Network mask field, type the subnet mask that is used by the XClarity Controller.
Note: The subnet mask must contain four integers from 0 to 255 with no spaces or consecutive periods
and separated by periods. The default setting is 255.255.255.0. This field will not be configurable if the
method is set to Obtain IP from DHCP.
5. In the Default Gateway field, type your network gateway router.
Note: The gateway address must contain four integers from 0 to 255 with no spaces or consecutive
periods and separated by periods. This field will not be configurable if the method is set to Obtain IP
from DHCP.
Note: In a Flex System, the VLAN settings are managed by a Flex System CMM and cannot be modified on
the XClarity Controller.
To enable Virtual LAN (VLAN) tagging select the Enable VLAN check box. When VLAN is enabled and a
VLAN ID is configured, the XClarity Controller only accepts packets with the specified VLAN IDs. The VLAN
IDs can be configured with numeric values between 1 and 4094.
From the MAC selection list choose one of the following selections:
• Use burned in MAC address
The Burned-in MAC address option is a unique physical address that is assigned to this XClarity
Controller by the manufacturer. The address is a read-only field.
• Use custom MAC address
If a value is specified, the locally administered address overrides the burned-in MAC address. The locally
administered address must be a hexadecimal value from 000000000000 through FFFFFFFFFFFF. This value
must be in the form xx:xx:xx:xx:xx:xx where x is a hexadecimal number from 0 to 9 or “a” through “f”. The
XClarity Controller does not support the use of a multicast address. The first byte of a multicast address is
an odd number (the least significant bit is set to 1); therefore, the first byte must be an even number.
Notes: When the Use statically assigned IP addres is chosen, you will be asked to type the
following information:
– IPv6 Address
– Prefix length
– Gateway
Configuring DNS
Use the information in this topic to view or change XClarity Controller Domain Name System (DNS) settings.
Note: In a Flex System, DNS settings cannot be modified on the XClarity Controller. DNS settings are
managed by the CMM.
Click Network under BMC Configuration to view or modify XClarity Controller DNS settings.
If you click the Use additional DNS address servers check box, specify the IP addresses of up to three
Domain Name System servers on your network. Each IP address must contain integers from 0 to 255,
separated by periods. These DNS server addresses are added to the top of the search list, so a host name
lookup is done on these servers before one that is automatically assigned by a DHCP server.
Configuring DDNS
Use the information in this topic to enable or disable Dynamic Domain Name System (DDNS) protocol on the
XClarity Controller.
Click Network under BMC Configuration to view or modify XClarity Controller DDNS settings.
Click the Enable DDNS check box, to enable DDNS. When DDNS is enabled, the XClarity Controller notifies
a domain name server to change in real time, the active domain name server configuration of the XClarity
Controller configured host names, addresses or other information that is stored in the domain name server.
Choose an option from the item list to decide how you want the domain name of the XClarity Controller to be
selected.
• Use custom domain name: You can specify the domain name to which the XClarity Controller belongs.
• Use domain name obtained from the DHCP server: The domain name to which the XClarity Controller
belongs is specified by the DHCP server.
Click Network under BMC Configuration to view or modify the XClarity Controller Ethernet over USB
settings.
The Ethernet over USB is used for in-band communications to the XClarity Controller. Click the check box to
enable or disable the Ethernet over USB interface.
Important: If you disable the Ethernet over USB, you cannot perform an in-band update of the XClarity
Controller firmware or server firmware using the Linux or Windows flash utilities.
Select the method that The XClarity Controller uses to assign addresses to the endpoints of the Ethernet
over USB interface.
• Use IPv6 link-local address for Ethernet over USB: This method uses IPv6 addresses based off the
MAC address that have been allocated to the endpoints of the Ethernet over USB interface. Normally, the
IPv6 link local address is generated using the MAC address (RFC 4862) but Windows 2008 and newer
2016 operating systems do not support a static link local IPv6 address on the host end of the interface.
Instead the default Windows behavior regenerates random link local addresses while running. If the
XClarity Controller Ethernet over USB interface is configured to use the IPv6 link local address mode,
various functions that make use of this interface will not work because the XClarity Controller does not
know what address Windows has assigned to the interface. If the server is running Windows use one of
the other Ethernet over USB address configuration methods, or disable the default Windows behavior by
using this command: netsh interface ipv6 set global randomizeidentifiers=disabled
• Use IPv4 link-local address for Ethernet over USB: An IP address in the 169.254.0.0/16 range is
assigned to the XClarity Controller and server side of the network.
• Configure IPv4 setting for Ethernet over USB: With this method, it specifies the IP addresses and
network mask that are assigned to the XClarity Controller and the server side of the Ethernet over USB
interface.
Notes:
1. The OS IP configuration settings is not used to set the OS IP address of Ethernet Over USB interface,
but is used to notify BMC that OS IP address of Ethernet over USB has changed.
2. Before you configure three IP settings for Ethernet over USB, you need to manually configure the OS IP
address of Ethernet over USB interface in your local operating system.
Mapping of external Ethernet port numbers to Ethernet over USB port numbers is controlled by clicking the
Enable external Ethernet to Ethernet over USB port forwarding checkbox and completing the mapping
information for ports you wish to have forwarded from the management network interface to the server.
Configuring SNMP
Use the information in this topic to configure SNMP agents.
Complete the following steps to configure the XClarity Controller SNMP alert settings.
1. Click Network under BMC Configuration.
2. Check the corresponding check box to enable the SNMPv1 Trap, SNMPv2 Trap and/or SNMPv3 Trap.
3. If enabling the SNMPv1 Trap or SNMPv2 Trap, complete the following fields:
a. In the Community Name field, enter the community name; Name cannot be empty.
b. In the Host field, enter host address.
Note: Click on each major category to further select their sub-category event types you wish to be
alerted.
Click Network under BMC Configuration to view or modify XClarity Controller IPMI settings. Complete the
following fields to view or modify IPMI settings:
Important:
• If you are not using any tools or applications that access the XClarity Controller through the network using
the IPMI protocol, it is highly recommended that you disable IPMI network access for improved security.
• IPMI over LAN access to the XClarity Controller is disabled by default.
Because each BMC network setting is configured using separate IPMI requests and in no particular order,
the BMC does not have the complete view of all of the network settings until the BMC is restarted to apply
the pending network changes. The request to change a network setting may succeed at the time that the
request is made, but later be determined to be invalid when additional changes are requested. If the pending
network settings are incompatible when the BMC is restarted, the new settings will not be applied. After
restarting the BMC, you should attempt to access the BMC using the new settings to ensure that they have
been applied as expected.
Click Network under BMC Configuration to view or modify XClarity Controller port assignments. Complete
the following fields to view or modify port assignments:
Web
The port number is 80. This field is not user-configurable.
Remote Presence
In this field specify the port number for Remote Presence. The default value is 3900.
SFTP
In this field specify the port number that is used for the SSH File Transfer Protocol (SFTP). The port
number is 22. This field is not user-configurable.
SLP
In this field specify the port number that is used for the SLP. The port number is 427. This field is not
user-configurable.
Notes: There are two service types that XClarity Controller reports:
• service: management-hardware.Lenovo:lenovo-xclarity-controller
• service: wbem
SSDP
The port number is 1900. This field is not user-configurable.
SSH
In this field specify the port number that is configured to access the command line interface through the
SSH protocol. The default value is 22.
SNMP Agent
In this field specify the port number for the SNMP agent that runs on the XClarity Controller. The default
value is 161. Valid port number values are from 1 to 65535.
SNMP Traps
In this field specify the port number that is used for SNMP traps. The default value is 162. Valid port
number values are from 1 to 65535.
Click Network under BMC Configuration to view or modify XClarity Controller access control settings.
Automatic blocking will dynamically determines when excessive login failures occur from a particular IP
address and blocks that address from accessing XClarity Controller for a predetermined amount of time.
• Maximum number of login failures from a particular IP
– The maximum number of times indicates the number of login failures allowed for a user with an
incorrect password from a specific IP address before it becomes locked-out.
– If set to 0, IP address will never be locked due to login failures.
– The failed login counter for the specific IP address will be reset to zero after successful login from that
IP address.
• Lockout period for blocking an IP
– The minimum amount of time (in minutes) that must pass before a user can attempt to log back in again
from a locked IP address.
– If set to 0, access from the locked IP address remains blocked-out until the administrator explicitly
unlocks it.
• Block List
– The table Block List displays all locked IP addresses. You can unlock one or all IP addresses from the
Block List.
On some servers the front panel USB port can be switched to attach either to the server or to the XClarity
Controller. Connection to the XClarity Controller is primarily intended for use with a mobile device running the
Click Network under BMC Configuration to view or modify XClarity Controller front panel USB port to
management settings.
There are four types of settings that you can choose from:
For additional information about the Mobile app, see the following site:
http://sysmgt.lenovofiles.com/help/topic/com.lenovo.lxca.doc/lxca_usemobileapp.html
Notes:
• If the front panel USB port is configured for Shared Mode, the port is connected to the XClarity Controller
when there is no power, and is connected to the server when there is power. When there is power, the
control of the front panel USB port can be switched back and forth between the server and the XClarity
Controller. In shared mode, the port can also be switched between the host and the XClarity Controller by
pressing and holding the front panel Identification button (for compute nodes it may be the USB
management button) for more than 3 seconds.
• When configured in Shared Mode and the USB port is currently connected to the server, the XClarity
Controller can support a request to switch the front panel USB port back to the XClarity Controller. When
this request is executed, the front panel USB port will remain connected to the XClarity Controller until
there is no USB activity to the XClarity Controller for the period specified by the inactivity timeout.
Note: The default minimum TLS version setting is TLS 1.2, but you can configure the XClarity Controller to
use other TLS versions if needed by your browser or management applications. For more information, see
“tls command” on page 147.
Click Security under BMC Configuration to access and configure security properties, status, and settings
for your XClarity Controller.
SSL overview
This topic is an overview of the SSL security protocol.
You can use SSL with a self-signed certificate or with a certificate that is signed by a third-party certificate
authority. Using a self-signed certificate is the simplest method for using SSL; but, it does create a small
security risk. The risk arises because the SSL client has no way of validating the identity of the SSL server for
the first connection that is attempted between the client and server. For example, it is possible that a third
party might impersonate the XClarity Controller web server and intercept data that is flowing between the
actual XClarity Controller web server and the user’s web browser. If, at the time of the initial connection
between the browser and the XClarity Controller, the self-signed certificate is imported into the certificate
store of the browser, all future communications will be secure for that browser (assuming that the initial
connection was not compromised by an attack).
For more complete security, you can use a certificate that is signed by a certificate authority (CA). To obtain a
signed certificate, you will need to select Generate Certificate Signing Request (CSR). Select Download
Certificate Signing Request (CSR) and send the Certificate-Signing Request (CSR) to a CA to obtain a
signed certificate. When the signed certificate is received, select Import Signed Certificate to import it into
the XClarity Controller.
The function of the CA is to verify the identity of the XClarity Controller. A certificate contains digital
signatures for the CA and the XClarity Controller. If a well-known CA issues the certificate or if the certificate
of the CA has already been imported into the web browser, the browser can validate the certificate and
positively identify the XClarity Controller web server.
The XClarity Controller requires a certificate for use with HTTPS Server, CIM over HTTPS, and the secure
LDAP client. In addition the secure LDAP client also requires one or more trusted certificates to be imported.
The trusted certificate is used by the secure LDAP client to positively identify the LDAP server. The trusted
certificate is the certificate of the CA that signed the certificate of the LDAP server. If the LDAP server uses
self-signed certificates, the trusted certificate can be the certificate of the LDAP server itself. Additional
trusted certificates must be imported if more than one LDAP server is used in your configuration.
Click Security under BMC Configuration to configure the SSL certificate management.
When managing XClarity Controller certificates, you are presented with the following actions:
Note: When performing the Generate Signed Certificate action, a Generate self-signed certificate for
HTTPS window opens. You will be prompted to complete the required and optional fields. You must
complete the required fields. Once you have entered your information, click Generate to complete the
task.
Note: When performing the Generate Certificate Signing Request (CSR) action, a Generate
Certificate Signing Request for HTTPS window opens. You will be prompted to complete the required
and optional fields. You must complete the required fields. Once you have entered your information,
click Generate to complete the task.
Click Network under BMC Configuration to configure the Secure Shell server.
To use the SSH protocol, a key needs to be generated first to enable the SSH server.
Notes:
• No certificate management is required to use this option.
• The XClarity Controller will initially create a SSH server key. If you wish to generate a new SSH server key,
click Network under BMC Configuration; then, click Regenerate key.
• After you complete the action, you must restart the XClarity Controller for your changes to take effect.
The XClarity Controller provides an IPMI interface via the KCS channel that does not require authentication.
Click Security under BMC Configuration to enable or disable IPMI over KCS access.
Note: After you change the settings, you must restart the XClarity Controller for your changes to take effect.
Important: If you are not running any tools or applications on the server that access the XClarity Controller
through the IPMI protocol, it is highly recommended that you disable the IPMI KCS access for improved
security. XClarity Essentials does use the IPMI over KCS interface to the XClarity Controller. If you disabled
This feature allows you to decide whether or not to allow the system firmware to return to an older firmware
level.
To enable of disable this feature, click Network under BMC Configuration. Any changes that are made will
take effect immediately without the XClarity Controller requiring a restart.
This feature is only available if the Physical Presence Policy is enabled through UEFI. Once enabled, you
can access the physical presence feature by clicking Security under BMC Configuration.
This feature uses centralized Key Management server to provide keys that unlock storage hardware, to gain
access to data stored on SEDs in a ThinkSystem server. The Key Management server includes SKLM - IBM
SED Key Management server, and KMIP - Thales/Gemalto SED Key Management servers (KeySecure and
CipherTrust).
The XClarity Controller uses the network to retrieve keys from the Key Management server, the Key
Management server must be accessible to the the XClarity Controller. The XClarity Controller provides the
communication channel between the Key Management server and the requesting ThinkSystem server. The
XClarity Controller firmware attempts to connect with each configured Key Management server, stopping
when a successful connection is established.
The XClarity Controller establishes communication with the Key Management server if the following
conditions are met:
• One or more Key Management server host name/IP addresses are configured in the XClarity Controller.
• Two certificates (client and server) for communication with the Key Management server are installed in the
XClarity Controller.
Note: Configure at least two (a primary and a secondary) Key Management servers with the same protocol
for your device. If the primary Key Management server does not respond to the connection attempt from the
XClarity Controller; connection attempts are initiated with the additional Key Management servers until a
successful connection is established.
A Transport Layer Security (TLS) connection must be established between the XClarity Controller and the
Key Management server. The XClarity Controller authenticates the Key Management server by comparing
the server certificate submitted by the Key Management server, with the Key management server certificate
previously imported into the XClarity Controller's trust store. The Key Management server authenticates each
XClarity Controller that communicates with it and checks to verify that the XClarity Controller is permitted to
access the Key Management server. This authentication is accomplished by comparing the client certificate
At least one Key Management server will be connected, and the device group is considered optional. The
Key Management server certificate will need to be imported, while the client certificate needs to be specified.
By default, the HTTPS certificate is used. If you wish to replace it, you can generate a new one.
Note: To connect the KMIP server(KeySecure and CipherTrust), must generate a certificate signing request
(CSR), and its common name must be matched with the user name defined in the KMIP server, then import a
certificate that has been signed by the Certificate Authority (CA) trusted by the KMIP server for the CSR.
The Key Management Server(s) configure section consists of the following fields:
Port
Type the port number for the Key Management server in this field. If this field is left blank, the default
value of 5696 is used. Valid port number values are 1 to 65535.
In the SKLM server, a device group allows users to manage the self-encrypting drive (SED) keys on multiple
servers as a group. A device group with the same name must also be created on the SKLM server.
Device Group
A device group allows users to manage the keys for SEDs on multiple servers as a group. A device
group with the same name must also be created on the SKLM server. The default value for this field is
IBM_SYSTEM_X_SED.
Client and server certificates are used to authenticate the communication between the SKLM server and the
XClarity Controller located in the ThinkSystem server. Client and server certificate management are
discussed in this section.
Notes:
• Certificates are preserved across firmware updates.
• If a client certificate is not created for communication with the SKLM server, the XClarity Controller HTTPS
server certificate is used.
• The function of the CA is to verify the identity of the XClarity Controller.
To create a client certificate, click the plus icon ( ) and select one of the following items:
• Generate a New Key and a Self-Signed Certificate
• Generate a New Key and a Certificate Signing Request (CSR)
The Generate a New Key and a Self-Signed Certificate action item generates a new encryption key and a
self-signed certificate. In the Generate New Key and Self-Signed Certificate window, type or select the
information in the required fields and any optional fields that apply to your configuration, (see the following
table). Click OK to generate your encryption key and certificate. A progress window displays while the self-
signed certificate is being generated. A confirmation window is displayed when the certificate is successfully
installed.
Note: The new encryption key and certificate replace any existing key and certificate.
Two column table with headers documenting the required and optional fields for the Generate a new key and
a self-signed certificate action. The bottom row spans across both columns.
Field Description
Country1 From the list item, select the country where the BMC physically resides.
State or Providence1 Type the state or providence where the BMC physically resides.
City or Locality1 Type the city or locality where the BMC physically resides.
Organization Name1 Type the company or organization name that owns the BMC.
BMC Host Name1 Type the BMC host name that appears in the web address bar.
Contact Person Type the name of the contact person that is responsible for the BMC.
Email address Type the email address of the contact person responsible for the BMC.
Organization Unit Type the unit within the company that owns the BMC.
Surname Type the surname of the person responsible for the BMC. This field can contain a
maximum of 60 characters.
Given Name Type the given name of the person responsible for the BMC. This field can contain a
maximum of 60 characters.
Initials Type the initials of the person responsible for the BMC. This field can contain a maximum
of 20 characters.
DN Qualifier Type the Distinguished Name Qualifier for the BMC. This field can contain a maximum of
60 characters.
1. This is a required field.
The Generate a New Key and a Certificate Signing Request (CSR) action item generates a new
encryption key and a CSR. In the Generate a New Key and a Certificate Signing Request window, type or
select the information in the required fields and any optional fields that apply to your configuration, (see the
following table). Click OK to generate your new encryption key and CSR.
A progress window displays while the CSR is being generated and a confirmation window is displayed upon
successful completion. After generation of the CSR, you must send the CSR to a CA for digital signing.
Select the Download Certificate Signing Request (CSR) action item and click OK to save the CSR to your
server. You can then submit the CSR to your CA for signing.
Field Description
Country1 From the list item, select the country where the BMC
physically resides.
State or Providence1 Type the state or providence where the BMC physically
resides.
City or Locality1 Type the city or locality where the BMC physically
resides.
Organization Name1 Type the company or organization name that owns the
BMC.
BMC Host Name1 Type the BMC host name that appears in the web
address bar.
Contact Person Type the name of the contact person that is responsible
for the BMC.
Email address Type the email address of the contact person responsible
for the BMC.
Organization Unit Type the unit within the company that owns the BMC.
Surname Type the surname of the person responsible for the BMC.
This field can contain a maximum of 60 characters.
Given Name Type the given name of the person responsible for the
BMC. This field can contain a maximum of 60 characters.
Initials Type the initials of the person responsible for the BMC.
This field can contain a maximum of 20 characters.
DN Qualifier Type the Distinguished Name Qualifier for the BMC. This
field can contain a maximum of 60 characters.
Challenge Password Type the password to the CSR. This field can contain a
maximum of 30 characters.
Unstructured Name Type additional information, such as an unstructured
name that is assigned to the BMC. This field can contain a
maximum of 60 characters.
1. This is a required field.
After the certificate has been signed by the CA you must import it into the BMC. Select the Import a Signed
Certificate action item and select the file to upload as the client certificate; then, click OK. A progress
window displays while the CA-signed certificate is being uploaded. A Certificate Upload window is displayed
if the upload process is successful. A Certificate Upload Error window is displayed if the upload process is
not successful.
Notes:
• For increased security, use a certificate that is digitally signed by a CA.
• The certificate that is imported into the XClarity Controller must correspond to the CSR that was
previously generated.
After a CA-signed certificate is imported into the BMC, select the Download Certificate action item. When
you select this action item, the CA-signed certificate is downloaded from the XClarity Controller to store on
your system.
The server certificate is generated in the SKLM server and must be imported into the XClarity Controller
before the secure drive access functionality will work. To import the certificate that authenticates the SKLM
server to the BMC, click Import a Certificate from the Server Certificate Status section of the Drive Access
page. A progress indicator is displayed as the file is transferred to storage on the XClarity Controller.
After the server certificate is successfully transferred to the XClarity Controller, the Server Certificate Status
area displays the following content: A server certificate is installed.
If you want to remove a trusted certificate, click the corresponding Remove button.
This feature allows you to decide whether or not to include the log entries of IPMI set command (raw data)
from LAN and KCS channels into the audit log.
Click Security under BMC Configuration on XCC web to enable/disable extended audit log.
Note: If the IPMI set command is from LAN channel, user name and source IP address will be included in the
log message. And all IPMI commands with sensitive security information (e.g. password) are excluded.
Cryptography Setting
Use the information in this topic to understand different cryptography settings.
The TLS Cryptography Setting is to restrict the supported TLS cipher suites against BMC services.
Please refer to the following table for different setting TLS Cipher suites are supported
High • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Security TLS 1.2 • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
Mode
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
NIST
• TLS_AES_256_GCM_SHA384
Compliant TLS 1.3
Mode • TLS_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
NIST • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Compliant TLS 1.2 • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Mode
• TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_CBC_SHA256
• TLS_RSA_WITH_AES_128_CBC_SHA256
• TLS_AES_256_GCM_SHA384
Compatibility
TLS 1.3 • TLS_AES_128_GCM_SHA256
Mode
• TLS_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Compatibility
TLS 1.2 • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Mode
• TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
• TLS_RSA_WITH_AES_256_GCM_SHA384
• TLS_RSA_WITH_AES_128_GCM_SHA256
• TLS_RSA_WITH_AES_256_CBC_SHA256
• TLS_RSA_WITH_AES_128_CBC_SHA256
TLS 1.1
Compatibility • TLS_RSA_WITH_AES_256_CBC_SHA256
Mode • TLS_RSA_WITH_AES_128_CBC_SHA256
TLS 1.0
Select Backup and Restore under BMC Configuration to perform the following actions:
• View management controller configuration summary
• Backup or restore the management controller configuration
• View backup or restore status
• Reset the management controller configuration to its factory default settings
• Access the management controller initial setup wizard
Select Backup and Restore under BMC Configuration. At the very top is the Backup BMC configuration
section.
If a backup was previously made, you will see the details in the Last backup field.
To backup the current BMC configuration, follow the steps shown below:
1. Specify the password for the BMC backup file.
Note: When the user sets up a new XClarity Controller user/password and performs a backup of the
configuration, the default account/password (USERID/PASSW0RD) is included as well. Subsequently deleting
the default account/password from the backup will result in the system showing a message notifying the user
that there is a failure in restoring the XClarity Controller account/password. Users can ignore this message.
Select Backup and Restore under BMC Configuration. Located below Backup BMC Configuration is the
Restore BMC from Configuration File section.
To restore the BMC to a previously saved configuration, follow the steps shown below:
1. Browse to select the backup file and input the password when prompted.
2. Verify the file by clicking View content to view the details.
3. After verifying the content, click Start Restore.
Select Backup and Restore under BMC Configuration. Located below Restore BMC from Configuration
File is the Reset BMC to factory default section.
To reset the BMC to factory defaults, follow the steps shown below:
1. Click Start to Reset BMC to Factory Defaults.
Notes:
• Only users with Supervisor user authority level can perform this action.
• The Ethernet connection is temporarily disconnected. You must log in the XClarity Controller web
interface again after the reset operation is completed.
• Once you click Start to Reset BMC to Factory Defaults, all previous configuration changes will be
lost. If you wish to enable LDAP when restoring the BMC configuration, you will need to first import a
trusted security certificate before doing so.
• After the process is completed, the XClarity Controller will be restarted. If this is a local server, your
TCP/IP connection will be lost and you may need to reconfigure the network interface to restore
connectivity.
• Resetting the BMC to Factory Default is not affecting UEFI settings.
For details on how to restart the XClarity Controller, see “Power actions” on page 58
Once you log into the XClarity Controller, a system status page will be displayed. From this page, you can
view the server hardware status, event and audit logs, system status, maintenance history and alert
recipients.
When you access the XClarity Controller homepage, the Health Summary is shown by default. A graphical
representation is given, which shows the number of hardware components that have been installed and their
respective health status. The hardware components that are being monitored include the following:
• Processor (CPU)
• Memory
• Local Storage
• PCI Adapters
• Power Supply
• Fan
• System Board
• Others
Note: Local Storage may show "not available" on the Status Icon on systems with a simple swap back-
plane configuration.
To view the other events, click the Active System Events tab. A window will appear showing the events that
are currently active in the system. Click View all event logs to view the entire event history.
If the hardware component is marked by a green check mark, it is operating normally, and there are no active
events.
The text underneath the hardware component states the number of components installed. If you click the
text, you will be directed to the Inventory page.
The System Information and Settings pane located to the left of the home page provides a summary of
common server information, which includes the following:
• Machine name, power and operating system state
The server can be in one of the system states listed in the following table.
State Description
System on/starting UEFI The server is powered on; but, UEFI is not running.
System stopped in UEFI The server is powered on; UEFI has detected a problem
and has stopped running.
Booting operating system or in unsupported operating The server might be in this state for one of the following
system reasons:
• The operating system loader has started; but, the
operating system is not running
• The BMC Ethernet over USB interface is disabled.
• The operating system does not have the drivers loaded
that support the Ethernet over USB interface.
Suspend to RAM The server has been placed in standby or sleep state.
System running in memory test The server is powered on and running memory diagnostic
tools.
System running in Setup The server is powered on and the system has booted into
UEFI F1 setup menu or LXPM menu.
System running in LXPM maintenance mode The server is powered on and the system has booted into
the LXPM maintenance mode under which users can’t
navigate through the LXPM menu.
If you wish to change the system name, click the pencil icon. Type the system name you wish to use; then,
click the green checkmark.
If you wish to change the front USB ownership, click the pencil icon and select the Front USB Ownership
mode that you wish from the drop-down menu. Then, click the green checkmark.
To change the relevant settings for the BMC IP address, BMC host name, UEFI version, BMC version and
location items, click the right-ward pointing arrow.
• For the IP address and host name, you will be led to the Ethernet Configuration section under Network.
• For the UEFI and BMC version items, you will be led to the Firmware Update page.
• For the location item, you will be led to the Server Properties section on the Server Configuration page.
System utilization is a composite metric based on the real-time utilization of processor, memory, and I/O
subsystems. The utilization data are all coming from the ME(Node manager) side, which includes the
following:
• CPU Utilization
– Aggregated C-State Residency
– Measured time in C0 as a percentage of the used and max C0 residency (per second).
• Memory Utilization
– Aggregated R/W volume of all Memory Channels.
– Measured bandwidth calculated as a percentage of the used and max memory bandwidth available
(per second).
• I/O Utilization
– Aggregated R/W volume of Root Ports in the PCIe* Bus.
– Measured bandwidth calculated as a percentage of the used and max I/O bandwidth available (per
second).
Select the Event Log tab in Events to display the Event Log page. All events in the log are time stamped,
using the XClarity Controller date and time settings. Some events also generate alerts when they occur, if
they are configured to do so in Alert Recipients. You can sort and filter events in the event log.
The following is a description of the actions that can be performed in the Event Log page.
• Customize table: Select this action item to choose the type of information you wish to display in the
table. A sequence number can be displayed to assist in determining the order of events when more than
one event has the same timestamp.
Note: Some sequence numbers are used by internal BMC processes, so it is normal that there may be
gaps in the sequence numbers when the events are sorted by sequence number.
• Clear logs: Select this action item to delete the event logs.
• Refresh: Select this action item to update the display with any event log entries that may have occurred
since the page was last displayed.
• Type: Select which event types to show. The event types include the following:
Note: The maximum number of event log records is 1024. When the event logs are full, the new log entry will
automatically overwrite the oldest one.
You can use the audit log to track and document authentication, changes, and system actions.
Notes:
• After running Lenovo’s tools on your server operating system, the Audit Log may contain records showing
actions performed by a username (for example user “20luN4SB”) that you may not recognize. When some
of the tools are run on the server operating system, they may create a temporary user account for
accessing the XClarity Controller. The account is created with a random username and password and can
only be used to access the XClarity Controller on the internal Ethernet over USB interface. The account
can only be used to access the XClarity Controller CIM-XML and SFTP interfaces. The creation and
removal of this temporary account is recorded in the audit log as well any actions performed by the tool
with these credentials.
• The maximum number of audit log records is 1024. When the audit logs are full, the new log entry will
automatically overwrite the oldest one.
The contents of the maintenance history can be filtered to display certain types of events or certain intervals
of time.
Note: The maximum number of maintenance history records is 250. When the maintenance history logs are
full, the new log entry will automatically overwrite the oldest one.
The following is a description of the actions that can be performed in the Alert Recipients tab.
The following actions items can be performed in the Email/Syslog recipients section.
• Create: Select this action item to create additional new Email recipients and Syslog recipients. Up to 12
Email and Syslog recipients can be configured.
– Create Email Recipient: Select this action item to create an Email recipient.
– Enter the name and email address of the recipient.
– Select to enable or disable the event notification. If disable is selected, the account will remain
configured, but no emails will be sent.
– Select the types of events that the recipient will be notified of. If you click the drop-down next to the
Critical, Attention, or System category labels you can select or deselect notifications for specific
components in the category.
– You can choose whether or not to have the event log contents included in the email alert.
– The index specifies which of the 12 recipient slots is assigned.
– You can configure the email server to which the events will be forwarded here or by clicking the
SMTP Server action at the top of the section. See SMTP Server below for configuration details.
– Create Syslog Recipient: Select this action item to create syslog recipients.
– Enter the name and IP address or host name of the Syslog server.
Note: Data transfer between the SNMP client and the agent can be protected using encryption. The
supported methods for privacy protocol are CBC-DES and AES.
• If SNMPv3 TRAP recipients have been created, they will be listed in this section.
– To edit the settings for a SNMPv3 recipient, click the pencil icon below the action header on the row
next of the recipient that you wish to configure.
– To delete a SNMPv3 recipient, click the trash can icon.
The operating system screen is automatically captured when the OS Watchdog timeout occurs. If an event
occurs that causes the OS to stop running, the OS Watchdog feature is triggered and the screen contents
are captured. The XClarity Controller stores only one screen capture. When the OS Watchdog timeout
occurs, a new screen capture overwrites the previous screen capture. The OS Watchdog feature must be
enabled to capture the OS failure screen. To set the OS Watchdog Time, see “Setting server timeouts” on
page 76 for more information. The OS failure screen capture feature is available only with the XClarity
Controller Advanced or Enterprise Level of functionality. See the documentation for your server for
information about the level of XClarity Controller functionality that is installed in your server.
Click the Latest Failure Screen action in the Remote Console section of the XClarity Controller home page
to view an image of the operating system display that was captured when the OS Watchdog timeout
occurred. The capture can also be viewed by clicking Service, then Latest Failure Screen in the Quick
Action section of the home page. If the system has not experienced an OS Watchdog timeout and captured
the OS screen, a message indicating that the failure screen has not been created is displayed.
Click Adapters under Server Configuration to view information about the adapters installed in the server.
Notes:
• If the adapter does not support status monitoring, it will not be visible for monitoring or configuration. For
inventory related information of all the installed PCI adapters, refer to the Inventory page.
When you select Boot Options under Server Configuration , you can configure the system boot mode and
order.
Note: No unauthenticated in-band method is allowed to change security related system settings. For
example, Secure Boot must NOT be able to configure over unauthenticated in-band APIs from the OS or
UEFI shell. This includes OneCLI running in-band and obtaining temporary credentials using IPMI, or any
tools and APIs to configure Secure Boot, TPM, UEFI Setup password related settings. All security related
settings must require proper authentication with sufficient privilege.
For the system boot mode, the following two options are available:
UEFI Boot
Select this option to configure a server that supports Unified Extensible Firmware Interface (UEFI). If you
are booting UEFI-enabled operating systems, this option might shorten boot time by disabling legacy
option ROMs.
Legacy Boot
Select this option if you are configuring a server to boot an operating system that requires legacy (BIOS)
firmware. Select this option only if you are booting non-UEFI enabled operating systems.
To configure the system boot order, select a device from the list of Available devices and click the right
arrow to add the device to the boot order. To remove a device from the boot order, select a device from the
boot order list and click the left arrow to move the device back to the list of available devices. To change the
boot order, select a device and click the up or down arrow to move the device up or down in priority.
When you make a change to the boot order, you must select a restart option before applying the change. The
following options are available:
Click Boot Options under Server Configuration and select a device from the drop-down menu to configure
the device that the system will boot to one-time on the next server restart. The following choices are
available:
PXE network
Sets up your server to attempt a Preboot Execution Environment network boot.
Primary removable media
The server is booted from the default USB device.
Default CD/DVD
The server is booted from the default CD/DVD drive.
F1 system setup
The server is booted into the Lenovo XClarity Provisioning Manager.
Diagnostic Partition
The server is booted into the Diagnostics section of the Lenovo XClarity Provisioning Manager.
Default Hard Disk
The server is booted from the default disk drive.
Primary remote media
The server is booted from the mounted virtual media.
No one-time boot
The configured boot order is used. There is no one-time boot override of the configured boot order.
When you change the type of boot to be performed with the one-time boot device, you can also specify the
boot to be a legacy boot or a UEFI boot. Click the Prefer Legacy Boot check box if you would like the boot
to be a legacy BIOS boot. Uncheck the box if would like a UEFI boot. When you select a one-time change to
the boot order, you must select a restart option before applying the change.
• Restart server immediately: The boot order change is saved and the server is restarted immediately
without shutting down the operating system.
• Restart server normally: The boot order change is saved and the operating system is shutdown before
restarting the server.
• Manually restart later: The boot order change is saved, but will not take effect until the next time the
server is rebooted.
Note: In a chassis containing blade or high-density server nodes, the chassis cooling and power is
controlled by the chassis management controller instead of the XClarity Controller.
• Redundant (N+N): There are two or more independent power sources that are capable of supplying
power to the system simultaneously. This means that if one or more power sources fails, the other source
(s) can continue to supply power to the system without any interruption. N+N redundancy provides a high
level of fault tolerance and ensures that the system remains operational even in the event of multiple
failures.
– Zero Output Mode: Once enabled under Redundant configuration, some PSUs will automatically enter
into standby state under light load conditions. In this manner, the remaining PSU delivers the entire
power load to increase efficiency.
• Redundant (N+1): There is one primary power source that is capable of supplying power to the system.
Additionally, there is at least one backup power source that is available to take over if the primary source
fails. The backup source is designed to provide enough power to keep the system running until the
primary source can be repaired or replaced. N+1 redundancy provides a lower level of fault tolerance
compared to N+N redundancy.
• Non-redundant mode: In this mode, the server is not guaranteed to remain operational if a power supply
is lost. The server will throttle if a power supply fails in an attempt to remain running.
You can choose to enable or disable the power capping function. If power capping is enabled, a selection
can be made to limit the amount of power used by the server. If power capping is disabled, the maximum
power used by the server is determined by the Power Redundancy policy. To change the setting, first click
Reset. Choose your preferred setting; then, click Apply.
Power capping can be enabled using AC power consumption measurements or DC power consumption
measurements. From the drop-down menu, select the type of measurements that will be used to determine
the power capping limit. When switching between AC and DC, the number on the slider will change
accordingly.
Note: The Power Policies option is not available when the XClarity Controller is in a chassis containing
blade or high-density server nodes. The power policy is controlled by the chassis management controller
instead of the XClarity Controller.
When configuring the power restore policy, the following three options are available:
Always Off
The server will remain powered off even when power is restored.
Restore
The server will automatically be powered on when power is restored if the server was powered on at the
time that the power failure occurred. Otherwise, the server power will remain off when power is restored.
Always On
The server will automatically power on when power is restored.
Note: The Power Restore Policies option is not available in a chassis containing blade or high-density
server nodes. The power restore policy is controlled by the chassis management controller instead of the
XClarity Controller.
Power actions
See the information in this topic to understand the power actions that can be made to the server.
Click Power Action in the Quick Action section of the XClarity Controller homepage.
The following table contains a description of the power and restart actions that can be performed on the
server.
Power on server Select this action item to power on the server and boot
the operating system.
Power off server normally Select this action item to shut down the operating system
and power off the server.
Power off server immediately Select this action item to power off the server without first
shutting down the operating system.
Restart server normally Select this action item to shut down the operating system
and power cycle the server.
Restart server immediately Select this action item to power cycle the server
immediately without first shutting down the operating
system.
Boot server to system setup Select this item to power on or reboot the server and
automatically boot into system setup without needing to
press F1 during boot.
Trigger non-maskable interrupt (NMI) Select this action item to force a Non-maskable Interrupt
(NMI) on a “hung” system. Selection of this action item
allows the platform operating system to perform a
memory dump that can be used for debug purposes of
the system hang condition. The auto reboot on NMI
setting from the F1 system setup menu determines
whether or not the XClarity Controller will reboot the
server after the NMI.
Schedule power actions Select this action item to schedule daily and weekly
power and restart actions for the server.
Restart management controller Select this action item to restart the XClarity Controller
AC Power Cycle Server Select this action to power cycle the server.
Note: If the operating system is in the screen saver or locked mode when a shutdown of the operating system is
attempted, the XClarity Controller might not be able to initiate a normal shutdown. The XClarity Controller will perform
a hard reset or shutdown after the power off delay interval expires, while the operating system might still be running.
This topic describes how the Intel Intelligent Power Node Manager and the Data Center Manageability
Interface (DCMI) can be used to provide power and thermal monitoring and policy-based power
management for a server using Intelligent Platform Management Interface (IPMI) power management
commands.
For servers using Intel Node Manager SPS 3.0, XClarity Controller users can use IPMI power management
commands provided by Intel's Management Engine (ME) to control the Node Manager features and to
monitor server power consumption. Server power management can also be accomplished using DCMI
power management commands. Example Node Manager and DCMI power management commands are
provided in this topic.
The Intel Node Manager firmware does not have an external interface; therefore, the Node Manager
commands must first be received by the XClarity Controller and then sent to the Intel Node Manager. The
XClarity Controller functions as a relay and a transport device for the IPMI commands using standard IPMI
bridging.
Note: Changing Node manager policies using Node Manager IPMI commands might create conflicts with
the XClarity Controller power management functionality. By default, bridging of the Node Manager
commands is disabled to prevent any conflict.
For users who want to manage the server power using the Node Manager instead of the XClarity Controller,
an OEM IPMI command consisting of (network function: 0x3A) and (command: 0xC7) is available for use.
The following information are examples of Node Manager power management commands.
Notes:
• By specifying IPMI channel 0 and a target address of 0x2c, you can use the IPMITOOL to send commands
to the Intel Node Manager for processing. A request message is used to initiate an action and a response
message is returned to the requester.
• Commands are displayed in the following format due to space limitations.
Power monitoring using the Get Global System Power Statistics, (command code 0xC8): Request:
ipmitool -H <$XClarity_Controller_IP> -U <USERID> -P <PASSW0RD> -b 0x00 -t 0x2c raw 0x2E 0xC8 0x57
0x01 0x00 0x01 0x00 0x00 Response:57 01 00 38 00 04 00 41 00 39 00 ec 56 f7 53 5a 86 00 00 50
Power capping using the Set Intel Node Manager Policy, (command code 0xC1): Request:ipmitool -H <
$XClarity_Controller_IP> -U <USERID> -P <PASSW0RD> -b 0x00 -t 0x2c raw 0x2e 0xC1 0x57 0x01 0x00
0x10 0x01 0xA0 0x00 0x00 0x00 0x60 0xea 0x00 0x00 0x00 0x00 0x1e 0x00Response:57 01 00
Power savings using the Set Intel Node Manager Policy, (command code 0xC1): Request:ipmitool -H <
$XClarity_Controller_IP> -U <USERID> -P <PASSW0RD> -b 0x00 -t 0x2c raw 0x2e 0xC1 0x57 0x01 0x00
0x10 0x01 0x00 0x00 0x00 0x00 0x60 0xea 0x00 0x00 0x00 0x00 0x1e 0x00
Get device ID function using the Get Intel Management Engine Device ID:Request:ipmitool -H <
$XClarity_Controller_IP> -U <USERID> -P <PASSW0RD> -b 0x00 -t 0x2c raw 0x06 0x01Response:50 01 03
05 02 21 57 01 00 05 0b 03 40 20 01
For additional Intel Node Manager commands, see the latest release of the Intel Intelligent Power Node
Manager External Interface Specification Using IPMI at https://businessportal.intel.com.
The DCMI provides monitoring and control functions that can be exposed through standard management
software interfaces. Server power management functions can also be accomplished using DCMI commands.
The following information are examples of commonly used DCMI power management functions and
commands. A request message is used to initiate an action and a response message is returned to the
requester.
Note: Commands are displayed in the following formats due to space limitations.
Note: On some servers, the Exception Actions for the Set Power Limit command might not be supported.
For example, the Hard Power Off system and log events to SEL parameter might not be supported.
For the complete list of commands that are supported by the DCMI specification, see the latest release of the
Data Center Manageability Interface Specification at https://www.intel.com/content/dam/www/public/us/en/
documents/technical-specifications/dcmi-v1-5-rev-spec.pdf.
You can use the remote console functionality in the XClarity Controller web interface to view and interact with
the server console. You can assign a disk image (ISO or IMG file) as a virtual drive on the server. The remote
console functionality is available with the XClarity Controller Advanced and XClarity Controller Enterprise
features and is only available through the web interface. You must log in to the XClarity Controller with a user
ID that has Supervisor access or Remote Console Access privileges to use the remote console features. For
more information about upgrading from XClarity Controller Standard to XClarity Controller Advanced or
XClarity Controller Enterprise, see “Upgrading XClarity Controller” on page 6.
Notes:
• When the remote console feature is started in multi-user mode, (the XClarity Controller with the XClarity
Controller Enterprise feature set supports up to six simultaneous sessions), the remote disk feature can be
exercised by only one session at a time.
• The remote console is able to display only the video that is generated by the video controller on the
system board. If a separate video controller adapter is installed and is used in place of the system's video
controller, the XClarity Controller remote console cannot display the video content from the added
adapter.
• If you have firewalls in your network, a network port must be opened to support the remote console
feature. To view or change the network port number used by the remote console feature, see “Service
Enablement and Port Assignment” on page 33.
• The remote console feature uses HTML5 for displaying the server video on web pages. To use this feature
your browser must support displaying video content using HTML5 elements.
• If you are using self-signed certificates and an IPv6 address to access the BMC with the Internet Explorer
browser, the remote console session may fail to start due to a certificate error. To avoid this issue, the
self-signed certificate can be added to the Internet Explorer Trust Root certificate Authorities:
– Select Security under BMC Configuration and download the self-signed certificate.
– Change certificate file extension to *.crt and double-click the Web certificate file.
As mentioned earlier, the XClarity Controller remote console functionality is available only in the XClarity
Controller Advanced and XClarity Controller Enterprise features. If you do not have the privilege to operate
the remote console, you will see a lock icon.
After you have purchased and obtained the activation key for the XClarity Controller Advanced upgrade
install it using the instructions under “Installing an activation key” on page 85.
Note: The XClarity Controller with XClarity Controller Enterprise feature set supports up to six
simultaneous video sessions in the multiuser mode.
3. Select whether or not to allow others to request to send a disconnection request to a remote console
user when someone wishes to use the remote console feature and the feature is already in use in Single
User Mode, or when the maximum number of users are using the remote console feature in Multi User
Mode. The No response time interval specifies how long the XClarity Controller will wait before
automatically disconnecting the user if no response is received to the disconnection request.
4. Select whether or not to allow record the latest three server boot videos.
5. Select whether or not to allow record the latest three server crash videos.
6. Select whether or not to allow OS failure screen capture with HW error.
7. Click Launch Remote Console to open the remote console page in another tab. When all possible
remote console sessions are in use, a dialog box will pop up. From this dialog box, the user can send a
disconnection request to a remote console user who has enabled the setting to Allow others to request
my remote session disconnect. The user can accept or deny the request to disconnect. If the user
does not respond within the interval specified by the No response time interval setting, the user
session will automatically be ended by the XClarity Controller.
You can send server power and restart commands from the remote console window without returning to the
main web page. To control the server power with the remote console, click Power and select one of the
following commands:
Power On Server
Select this action item to power on the server and boot the operating system.
Power Off Server Normally
Select this action item to shut down the operating system and power off the server.
The screen capture feature in the remote console window captures the video display contents of the server.
To capture and save a screen image, complete the following steps:
• Click Virtual Keyboard to launch the virtual keyboard. This feature is useful if you are using a tablet
device that does not have a physical keyboard. The following options can be used to create macros and
key combinations that can be sent to the server. The operating system on the client system that you are
using may trap certain key combinations (for example Ctrl+Alt+Del) instead of transmitting them to the
server. Other keys, such as F1 or Esc, may be intercepted by the program or browser that you are using.
Macros provides a mechanism to send keystrokes to the server that the user might not be able to send.
• Click Server Macros to use server defined macros. Some server macros are predefined by the XClarity
Controller firmware. Other server defined macros can be defined using Lenovo XClarity Essentials and
downloaded from the XClarity Controller. These macros are defined for all users of the remote console
feature.
• Click Configure to add or remove user defined macros. The user defined macros are defined only for the
current remote console user. Other remote console users will not see each other’s user defined macros.
– Click the Add Macros icon and press the key sequences that you desire; then, click Add to add a new
macro.
– To remove a user defined macro, select the macro from the list and click the trash can icon.
– To send a user defined macro to the server select the User Defined Macros option, and click on the
macro that you want to send.
The remote console window offers several options for mouse control, including absolute mouse control,
relative mouse control (no acceleration), and mouse control (RHEL, older Linux).
To access the absolute and relative options for controlling the mouse, complete the following steps:
The XClarity Controller web interface provides a DVR-like feature to support recording and playback remote
presence screen videos. This function only supports video recording to a network folder. Currently, NFS and
CIFS protocols are supported. Below are the steps in using the record and replay function.
1. On the remote console web page, click Screen Recording to open the settings window.
2. In the settings window, the following information may need to be specified.
• If the “CIFS” mount type is selected, specify the Remote Folder, User Name, and Password
parameters. The format for the CIFS remote folder is “//<remote IP address>/<folder name>”. For
example: //xxx.xxx.xxx.xxx/folder.
• If the “NFS” mount type is selected, specify the Remote Folder parameter. The format for the NFS
remote folder is “<remote IP address>:/<folder name>”. For example: xxx.xxx.xxx.xxx:/folder.
• Specify the video file name if necessary. If a file name has already been provided, an error message
box will shown. To overwrite the existing file name, choose “Overwrite File Name”. If the “Auto” box is
ticked, the video file name will be automatically generated.
• “Max File Size” denotes the maximum video file size before the video recording will automatically
stop.
• “Max Recording Duration” denotes the maximum video recording duration before the recording will
automatically stop.
3. Click Start Recording to start the video recording.
4. Click Stop Recording to stop the video recording. A popup window saying “Video Recording
Completed” will appear, showing relevant video recording information.
5. Download the recorded videos from NFS or CIFS to your local folder. In the Remote Console Preview
section of the XClarity Controller homepage, click Recorded Videos and select the video file to replay.
Full Screen
This mode fills the client desktop with the video display. Pressing the Esc key in this mode will exit full
screen mode. Because the remote console menu is not visible in full screen mode, you will have to exit
full screen mode to use any of the features provided by the remote console menu such as the keyboard
macros.
Fit Screen
This is the default setting when the remote console is launched. In this setting, the target desktop is
completely displayed without scroll bars. The aspect ratio is maintained.
Scaling Screen
With scaling enabled, the video image is sized so that the complete image is scaled to fill the console
window.
Origin Screen
The video image has the same dimensions as the server end. Scroll bars are displayed if needed to allow
viewing of video image areas that do not fit within the window.
Color Mode
Adjusts the color depth of the remote console window. There are two color-mode choices:
• Color: 7, 9, 12, 15, and 23 bit
• Grayscale: 16, 32, 64, and 128 shades
Note: Color mode adjustments are usually made if your connection to the remote server has limited
bandwidth and you wish to reduce the bandwidth demand.
Three mechanisms are provided to mount ISO and IMG files as virtual drives.
• Virtual drives can be added to the server from the remote console session by clicking Media.
• Directly from the remote console web page, without establishing a remote console session.
• Standalone tool
Users need Remote Console and Remote Disk Access privileges to use the virtual media features.
Files can be mounted as virtual media from your local system or from a remote server, and can be accessed
over the network or uploaded into the XClarity Controller memory using the RDOC feature. These
mechanisms are described below.
• Local media are ISO or IMG files that are located on the system that you are using to access the XClarity
Controller. This mechanism is only available through the remote console session, not directly from the
remote console web page and is only available with the XClarity Controller Enterprise features. To mount
local media, click Activate in the Mount Local Media section. Up to four files can be concurrently
mounted to the server.
Notes:
– When using the Google Chrome browser, an additional mounting option called Mount files/folders is
available to let you drag and drop the file(s)/folder.
Note: The XClarity Controller does not support spaces in the user name, password, or URL. Make
sure that the CIFS server does not have login credentials configured with a space in the user name
or password and that the URL does not contain a space.
– Mount options are optional and defined by the CIFS protocol.
– If the remote server belongs to a collection of servers, where the security is centrally handled, enter
the domain name to which the remote server belongs.
– NFS - Network File System:
– Enter the URL that locates the file on the remote system.
– If you want the file to be presented to the server as read-only virtual media, tick the checkbox.
– Mount options are optional and defined by the NFS protocol. Both NFSv3 and NFSv4 are supported.
For example, to use NFSv3, you need to specify option ‘nfsvers=3’. If the NFS server uses AUTH_
SYS security flavor to authenticate NFS operations, you need to specify option ‘sec=sys’.
– HTTPFS – HTTP Fuse-based File System:
– Enter the URL that locates the file on the remote system
– If you want the file to be presented to the server as read-only virtual media, tick the check box.
Note: Errors may occur during the mounting process for security certificates generated by Microsoft
IIS. If this occurs, see “Media mount error issues” on page 73.
Click Mount all remote media to mount the file as virtual media. To remove virtual media, click the trash
can icon to the right of the mounted media.
• Up to two files can be uploaded in the XClarity Controller memory and mounted as virtual media using the
XClarity Controller RDOC feature. The total size for both files must not exceed 50 MB. These files will
remain in the XClarity Controller memory until they are removed, even if the remote console session has
ended. The RDOC feature supports the following mechanisms when uploading the files:
– CIFS - Common Internet File System: See the description above for details.
Example:
To mount an ISO file named account_backup.iso that is located on the backup_2016 directory of a
CIFS server at the 192.168.0.100 IP address as a read-only virtual drive on the server, you would fill in
the fields as shown in the figure below. In this example, the server located at 192.168.0.100 is a
member of a collection of servers under the domain “accounting”. The domain name is optional. If your
CIFS server is not part of a domain, leave the Domain field blank. The CIFS “nocase” mount option is
specified in the Mount Options field in this example indicating to the CIFS server that the uppercase/
lowercase checking of the file name should be ignored. The Mount Options field is optional. The
information entered by the user in this field is not used by the BMC and is simply passed on to the CIFS
server when the mount request is made. Refer to the documentation for your CIFS server
implementation to determine which options are supported by your CIFS server.
– NFS - Network File System: See the description above for details.
Example:
To mount an ISO file named US_team.iso that is located on the “personnel” directory of an NFS server
at the 10.243.28.77 IP address as a read-only virtual drive on the server, you would fill in the fields as
shown in the figure below. The NFS “port=2049” mount option specifies that network port 2049 should
be used to transfer the data. The Mount Options field is optional. The information entered by the user
in this field is passed on to the NFS server when the mount request is made. Refer to the
documentation for your NFS server implementation to determine which options are supported by your
NFS server.
The BMC provides guidance when specifying the URL. If the URL being entered is not valid, the mount
button will be greyed out and red text will be displayed under the URL field showing the expected
format for the URL.
Notes:
– Errors may occur during the mounting process for security certificates generated by Microsoft IIS. If
this occurs, see “Media mount error issues” on page 73.
– The XClarity Controller does not support spaces in the user name, password, or URL. Make sure
that the CIFS server does not have login credentials configured with a space in the user name or
password and that the URL does not contain a space. Example:
To mount an ISO file named EthernetDrivers.ISO that is located on the “newdrivers” directory of a
HTTPS server with the domain name “mycompany.com” using network port 8080 as a read-only
virtual drive on the server, you would fill in the fields as shown in the figure below.
The BMC provides guidance when specifying the URL. If the URL being entered is not valid, the
mount button will be greyed out and red text will be displayed under the URL field showing the
expected format for the URL.
Notes:
– The XClarity Controller does not support spaces in the user name, password, or URL. Make sure
that the CIFS server does not have login credentials configured with a space in the user name or
password and that the URL does not contain a space.
– When the XClarity Controller connects to a HTTPS server, a pop-up window will appear showing
information of the security certificate used by the HTTPS sever. The XClarity Controller is unable to
verify the authentic of the security certificate.
– LOCAL - Common Internet File System:
– Browse your system for the ISO or IMG file that you want to mount.
– If you want the file to be presented to the server as read-only virtual media, check the check box.
Click Mount all RDOC files to mount the file as virtual media. To remove the virtual media, click the trash
can icon to the right of the mounted media.
Standalone tool
you can use Java client to assign to the server a CD or DVD drive, a diskette drive, USB flash drive that is on
your computer, or you can specify a disk image on your computer for the server to use. You can use the drive
for functions such as restarting (booting) the server, updating code, installing new software on the server,
and installing or updating the operating system on the server. You can access the remote disk. Drives and
disk images are displayed as USB drives on the server.
Notes: The Remote Console Java supports one of the following Java environment, and it can be opened
only if the HTML5 client is not running.
1. Oracle Java Runtime Environment 1.8/Java SE 8 or newer versions
2. OpenJDK 8. Distribution of AdoptOpenJDK with HotSpot JVM is supported.
If you use AdoptOpenJDK, you must use https://openwebstart.com/ under OSX, Windows, and Linux.
Click the Select Devices to Mount option under the Virtual Media tab in the Virtual Media Java Client
window. The Select Devices to Mount window is displayed.
You can mount local image, folder and CD/DVD/USB drive by performing the following steps:
• Mount Local Image:
1. Click the Add Image button to select the image you want to mount.
2. Check the Mapped option.
Below is an example showing how the new security certificate is generated via openssl in the Linux operating
system.
$ openssl
OpenSSL>
$ ls
server.csr server.key
$ openssl req -x509 -days 3650 -key server.key -in server.csr > server.crt
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:CN
State or Province Name (full name) [Some-State]:BJ
Locality Name (eg, city) []:BJ
Organization Name (eg, company) [Internet Widgits Pty Ltd]:LNV
Organizational Unit Name (eg, section) []:LNV
Common Name (e.g. server FQDN or YOUR name) []:10.245.18.66
Email Address []:[email protected]
$ ls
server.crt server.csr server.key
$ ls
server.crt server.csr server.key server.pfx
To exit your remote console session, close the remote console and the virtual media session windows.
In the XClarity Controller home page, click the Service option in the Quick Action section and select
Download Service Data. Click OK to download the service data.
The process of collecting the service and support data takes a few minutes to generate the service data. The
file will be saved to your default download folder. The naming convention for the service data file follows this
convention:<machine type and model>_<serial number>_xcc_<date>-<time>.tgz
In addition to the tgz format, the service data can also be downloaded using the tzz format. Tzz uses a
different compression algorithm and can be extracted with a utility such as “lzop”.
Server Properties
Use the information in this topic to change or view relevant server properties.
Select Server Properties under Server Configuration, to configure the Location and Contact information.
Contact
Allows you to specify the name and phone number of the person who should be contacted if the system
experiences a problem.
Note: This field is the same as the Contact field in the SNMPv3 configuration and is required to enable
SNMPv3.
Rack Name
Allows you to locate the server more easily by specifying which rack it is in.
Room Number
Allows you to locate the server more easily by specifying which room it is in.
Building
Allows you to locate the server more easily by specifying which building it is in.
Lowest U
Allows you to locate the server more easily by specifying the position in the rack.
Note: When the relevant information has been inputted, it will appear as a single line in the Location field in
the SNMPv3 section and XClarity Controller home page.
These timeouts are used to restore operation to a server that has hung.
Select Server Properties under Server Configuration, to configure the server timeouts. The following
server timeout selections are provided:
OS Watchdog
The OS watchdog is used to monitor the operating system to ensure that it is not hung. The Ethernet
over USB interface must be enabled for this feature. See “Configuring Ethernet over USB” on page 32
for details. The XClarity Controller contacts the operating system at an interval configured in the OS
Watchdog Time selection. If the operating system does not respond before it is time for the next check,
the XClarity Controller assumes that the operating system has hung. The XClarity Controller will capture
the contents of the server display and then reboot the server in an attempt to restore operation. The
XClarity Controller will reboot the server only once. If the operating system continues to hang after the
reboot, instead of continually rebooting the server, the server will be left in the hung state so that the
problem can be investigated and corrected. To rearm the OS watchdog, power the server off and back
on. To enable the OS watchdog, select an interval from the OS Watchdog Time drop-down and click
Apply. To disable the OS watchdog, select None on the OS Watchdog Time drop-down menu.
Loader Watchdog
The loader watchdog monitors the interval between the completion of POST and when the operating
system begins running. The Ethernet over USB interface must be enabled for this feature. See
“Configuring Ethernet over USB” on page 32 for details. When POST is completed, the XClarity
Controller starts a timer and begins to contact the operating system. If the operating system does not
respond with the time configured in the Loader Watchdog selection, the XClarity Controller assumes that
the operating system boot has hung. The XClarity Controller will then reboot the server in an attempt to
restore operation. The XClarity Controller will reboot the server only once. If the operating system boot
continues to hang after the reboot, instead of continually rebooting the server, the server will be left in
the hung state so that the problem can be investigated and corrected. The loader watchdog is rearmed
when server is switched off and back on or when the server successfully boots into the operating
system. To enable the loader watchdog, select an interval from the Loader Watchdog drop-down and
click Apply. To disable the loader watchdog select None on the Loader Watchdog drop-down.
Trespass message
To create a message that is displayed when a user logs in to the XClarity Controller, use the information in
this topic.
Select Server Properties under Server Configuration. Use the Trespass Message option to configure a
message that you want displayed to the user. When you are finished, click Apply.
At the XClarity Controller home page, click the clock icon on the upper right-hand corner to view or change
the XClarity Controller date and time. The XClarity Controller does not have its own real-time clock. You can
configure the XClarity Controller to sync its time and date with a Network Time Protocol server or with the
server’s real-time clock hardware.
Notes:
• When daylight saving occurs, any actions that were scheduled for the XClarity Controller to perform
during the interval when the clock jumps forward will not be performed. For example, if the US daylight
start time is 2:00 am on March 12th, and a power action is scheduled for 2:10 am on March 12th, this
action will not occur. Once the time reaches 2:00 am, the XClarity Controller will instead read the time as
3:00 am.
• XClarity Controller Date and Time settings cannot be modified in a Flex System.
RAID Detail
For using RAID detail function, use the information in this topic.
This function displays the storage devices’ physical structure and storage configuration along with details
like their location, manufacturer, product name, status, capacity, interface, media, form factor and other info.
RAID Setup
To perform RAID setup functions, use the information in this topic.
Use the information in this topic to view and configure storage pools, associated virtual disks and drives for
the RAID adapter. If the system is powered off, power it on in order to view the RAID information.
When you select RAID Setup under Server Configuration, the Array Configuration tab will be chosen and
the existing virtual disks will be displayed by default. The logical drives are sorted by disk arrays and
controllers. Detailed information about the virtual disk, such as the virtual disk strip size and bootable
information is displayed.
In edit mode, you can click the controller action menu, view the current RAID virtual disks and create new
RAID virtual disks.
From the Controller Actions menu, you can perform the following actions:
Information of the current RAID virtual disks for a particular controller are shown as respective “virtual disk
cards”. Each card displays information such as the virtual disk name, status, capacity and actions. The
pencil icon allows you to edit the information, and the trash can icon enables you to delete the “virtual disk
card”.
If you click the virtual disk name, a virtual disk properties window will appear.
To create a new RAID virtual disk, follow the steps shown below:
Note: If there is no remaining storage capacity, you are unable to create a new virtual disk.
1. Select drives or a disk array which has free storage capacity
a. When creating a virtual disk in a new disk array, you need to specify the RAID level. If there are not
enough drives to select, and you click Next, an error message will appear under the RAID level field.
For some RAID levels, span is required . There is also a minimum amount of drives that need to be
present in the span.
1) For these types of situations, the web interface will display Span 1 by default.
2) Select the drives and click Add member to add the drives to Span 1. When Span 1 does not
have enough drives, disable the Add Span link.
3) Click Add Span to add Span 2. Select the drives and click Add member to add to Span 2.
4) Click Add member to add drives to the last span. If you want to add drives to Span 1 again, you
need to click Span 1 and select the drives to add to Span 1.
5) If the number of spans reaches the maximum amount, disable Add span.
b. To create virtual disks in an existing disk array, you need to select a disk array that has free capacity.
2. Creating a virtual disk
a. By default, create a virtual disk that uses all the storage capacity. The Add icon is disabled when all
of the storage is used. You can click the pencil icon to change the capacity or other properties.
b. When you edit the first virtual disk to use only some of the storage capacity, the Add icon will be
enabled. Click the icon to show the Add Virtual Disk window.
c. If there is more than one virtual disk, the Remove icon will be enabled. This icon will not be shown if
there is only one virtual disk. When you click the Remove icon, the selected row will be immediately
deleted. There will be no confirmation window as the virtual disk has not been created yet.
d. Click Start Creating Virtual Disk to start the process.
Under the Storage Inventory tab , you can view and configure disk arrays, associated virtual drives and
drives for the RAID controller.
• For storage devices that support RAID configuration:
1. If the controller includes configured disk arrays, it will display the installed drives based on the disk
array. The following describes the items that appear in the window.
– Table title: Shows the disk array ID, RAID level and the total number of drives.
– Table content: Lists the basic properties - drive name, RAID state, type, serial number, part
number, FRU number and actions. You can go to the Inventory page to view all the properties that
the XClarity Controller can detect.
– Actions: The following shows the action items that can be performed. Some actions will not be
available when the drive is in a different state.
– Assign hot spare: Specifies the drive as global hot spare or a dedicated hot spare.
– Remove hot spare: Removes the drive from the hot spare.
For storage devices that do not support RAID configuration: The XClarity Controller may not be able to
detect the properties of some drives.
Overview
General Information about updating server firmware.
The current status and versions of firmware for the BMC, UEFI, LXPM, LXPM drivers, and adapters are
displayed, including the BMC primary and backup versions. There are four categories for the firmware status:
• Active: The firmware is active.
• Inactive: The firmware is not active.
• Pending: The firmware is waiting to become active.
• N/A: No firmware has been installed for this component.
Attention:
• XCC and IMM must be updated to the latest version before updating uEFI. Updating in different order may
result in strange or incorrect behavior.
• Installing the wrong firmware update might cause the server to malfunction. Before you install a firmware
or device-driver update, read any readme and change history files that are provided with the downloaded
update. These files contain important information about the update and the procedure for installing the
update, including any special procedure for updating from an early firmware or device-driver version to the
latest version. As the web browser may contain XCC cache data, it is recommended to reload the web
page after the XCC firmware has been upgraded.
• Some firmware updates require system restarting, which performs firmware activation or internal update.
This process in system booting is called “system maintenance mode”, that does not allow user power
actions temporarily. The mode is also enabled during firmware update. User shall not disconnect AC
power when the system enters maintenance mode.
To manually apply update for System Firmware, Adapter Firmware and PSU Firmware, complete the
following steps:
1. Click Update Firmware within each feature. The Update Server Firmware window opens.
2. Click Browse to select the firmware update file that you want to use.
3. Navigate to the file you want to select and click Open. You are returned to the Update Server Firmware
window with the selected file displayed.
There are multiple levels of XClarity Controller firmware functionality and features available for your server.
The level of the firmware features installed on your server vary based on hardware type.
You can upgrade the XClarity Controller functionality by purchasing and installing an activation key.
Use the XClarity Controller web interface or the XClarity Controller CLI to manually install an activation key
that lets you use an optional feature you have purchased. Before activating a key:
• The activation key must be on the system that you are using to login to the XClarity Controller.
• You must have ordered the license key and received its authorization code via mail or email.
See “Installing an activation key” on page 85, “Removing an activation key” on page 86 or “Exporting an
activation key” on page 86 for information about managing an activation key using the XClarity Controller
web interface. See “keycfg command” on page 122 for information about managing an activation key using
the XClarity Controller CLI.
To register an ID in administering your XClarity Controller license, click the following link: http://
thinksystem.lenovofiles.com/help/index.jsp
Additional information about license management for Lenovo servers is available at the following Lenovo
Press website:
https://lenovopress.com/redp4895-using-lenovo-features-on-demand
Attention: You cannot directly upgrade from Standard XClarity Controller to Enterprise Level functionality.
You will need to first upgrade to Advanced Level before the Enterprise Level functionality can be activated.
Notes:
• If the activation key is not valid, an error window will appear.
Step 4. Click OK to close the Success window.
This allows for easy integration of Lenovo XClarity Controller capabilities into other software, whether the
software is running on the same system as the Lenovo XClarity Controller server, or on a remote system
within the same network. These APIs are based on the industry standard Redfish REST API and are
accessed via the HTTPS protocol.
The XClarity Controller Redfish REST API user guide can be found here: https://sysmgt.lenovofiles.com/help/
topic/com.lenovo.systems.management.xcc.restapi.doc/xcc_restapi_book.pdf.
Lenovo provides open source sample Redfish scripts that can be used as reference for developing software
that communicates with Lenovo Redfish REST API. These sample scripts can be found here:
• Python: https://github.com/lenovo/python-redfish-lenovo
• PowerShell: https://github.com/lenovo/powershell-redfish-lenovo
DMTF specifications related to the Redfish API are available at: https://redfish.dmtf.org/. This website
provides general specifications and other reference material on the Redfish REST API.
Use the XClarity Controller command line interface (CLI) to access the XClarity Controller without having to
use the web interface. It provides a subset of the management functions that are provided by the web
interface.
You can access the CLI through a SSH session. You must be authenticated by the XClarity Controller before
you can issue any CLI commands.
To access the CLI, start an SSH session to the XClarity Controller IP address (see “Configuring serial-to-SSH
redirection” on page 89 for more information).
You are logged in to the command line. The command-line prompt is system>. The command-line
session continues until you type exit at the command line. You are logged off and the session is
ended.
Serial-to-SSH redirection enables a system administrator to use the XClarity Controller as a serial terminal
server. A server serial port can be accessed from a SSH connection when serial redirection is enabled.
Note: The CLI console 1 command is used to start a serial redirection session with the COM port.
Example session
$ ssh [email protected]
Password:
system>
ESC (
system>
Command syntax
Review the guidelines in this topic to understand how to enter commands in the CLI.
The complete list of all XClarity Controller CLI commands, in alphabetical order, is as follows:
• “accseccfg command” on page 107
• “adapter command” on page 168
• “alertcfg command” on page 108
• “alertentries command” on page 154
• “asu command” on page 109
• “backup command” on page 112
• “batch command” on page 156
• “clearcfg command” on page 157
• “clearlog command” on page 94
• “clock command” on page 157
• “console command” on page 107
• “dbgshimm command” on page 171
• “dhcpinfo command” on page 113
Utility commands
This topic provides an alphabetic list of utility CLI commands.
exit command
Use this command to log off the CLI session,
Use the exit command to log off and end the CLI session.
help command
This command displays a list of all commands.
Use the help command to display a list of all commands with a short description for each. You can also type
? at the command prompt.
history command
This command provides a list of previously issued commands.
Use the history command to display an indexed history list of the last eight commands that were issued. The
indexes can then be used as shortcuts (preceded by !) to reissue commands from this history list.
Example:
system> history
0 ifconfig eth0
1 readlog
2 readlog
3 readlog
Monitor commands
This topic provides an alphabetic list of monitor CLI commands.
clearlog command
This command is used to clear the IMM event log.
Use the clearlog command to clear the event log of the IMM. You must have the authority to clear event logs
to use this command.
Option Description
-t <all | platform | audit> Event type, choose which type of event to clear. If not specified, all
event types will be selected.
Example:
system> clearlog
All event log cleared successfully
system> clearlog -t all
All event log cleared successfully
system> clearlog -t platform
Platform event log cleared successfully
system> clearlog -t audit
Audit event log cleared successfully
Use the fans command to display the speed for each of the server fans.
Example:
system> fans
fan1 75%
fan2 80%
fan3 90%
system>
ffdc command
This command is used to generate a new service data file.
Use the first failure data capture (ffdc) command to generate and transfer service data to Support.
The following list consist of commands to be used with the ffdc command:
• generate, create a new service data file
• status, check status of service data file
• copy, copy existing service data
• delete, delete existing service data
-f 1 Remote filename or sftp For sftp, use full path or trailing / on directory name (~/ or /tmp/). The
target directory. default value is the system generated name.
Syntax:
ffdc [options]
option:
-t 1 or 4
-f
-ip ip_address
Example:
system> ffdc generate
Generating ffdc...
system> ffdc status
Type 1 ffdc: in progress
system> ffdc copy -t 1 -ip 192.168.70.230 -u User2 -pw Passw0rd -f /tmp/
Waiting for ffdc.....
Copying ffdc...
ok
system> ffdc status
Type 1 ffdc: completed
8737AC1_DSY0123_xcc_120317-153327.tgz
hreport command
Use this command to show embedded health report.
The following table is a multi-row two column table consisting of the different hreport command descriptions.
Option Description
generate Create new health report
status Check status
copy Copy existing health report
The following table shows the arguments for the generate and copy options.
Option Description
-f Remote filename or sftp target directory (default is system generated name ((for sftp,
use full path or trailing / on directory name (~/ or /tmp/))
mhlog command
Use this command to display maintenance history activity log entries.
Option Description
-c <count> Display 'count' entries (1-250)
Example
Display will look something like this:
led command
Use this command to display and set LED states.
The led command displays and sets the server LED states.
• Running the led command with no options displays the status of the front panel LEDs.
Syntax:
led [options]
option:
-l
-chklog off
-identify state
-d time
Example:
system> led
Fault Off
Identify On Blue
Chklog Off
Power Off
system> led -l
Label Location State Color
Battery Planar Off
BMC Heartbeat Planar Blink Green
BRD Lightpath Card Off
Channel A Planar Off
Channel B Planar Off
Channel C Planar Off
Channel D Planar Off
Channel E Planar Off
Chklog Front Panel Off
CNFG Lightpath Card Off
CPU Lightpath Card Off
CPU 1 Planar Off
CPU 2 Planar Off
DASD Lightpath Card Off
DIMM Lightpath Card Off
DIMM 1 Planar Off
DIMM 10 Planar Off
DIMM 11 Planar Off
DIMM 12 Planar Off
DIMM 13 Planar Off
DIMM 14 Planar Off
DIMM 15 Planar Off
DIMM 16 Planar Off
readlog command
This command displays the IMM event logs.
Use the readlog command to display the IMM event log entries. Five event logs are displayed at a time. The
entries are displayed from the most recent to the oldest.
readlog displays the first five entries in the event log, starting with the most recent, on its first execution,
and then the next five for each subsequent call.
readlog -a displays all entries in the event log, starting with the most recent.
readlog -f resets the counter and displays the first 5 entries in the event log, starting with the most recent.
readlog -date date displays event log entries for the specified date, specified in mm/dd/yy format. It can
be a pipe (|) separated list of dates.
readlog -sev severity displays event log entries for the specified severity level (E, W, I). It can be a pipe (|)
separated list of severity levels.
readlog -i ip_address sets the IPv4 or IPv6 IP address of the TFTP or SFTP server where the event log is
saved. The -i and -l command options are used together to specify the location.
readlog -l filename sets the file name of the event log file. The -i and -l command options are used
together to specify the location.
readlog -pn port_number displays or sets the port number of the TFTP or SFTP server (default 69/22).
readlog -u username specifies the user name for the SFTP server.
Syntax:
readlog [options]
option:
-a
-f
-date date
-sev severity
-i ip_address
-l filename
-pn port_number
-u username
-pw password
Example:
system> readlog -f
1 I 2017-06-17T09:31:59.217 Remote Login Successful. Login ID: USERID
from SSH at IP address 10.134.78.180
2 I 2017-06-17T07:23:04.685 Remote Login Successful. Login ID: USERID
from webguis at IP address 10.134.78.180.
3 I 2017-06-16T11:00:35.581 Login ID: USERID from webguis at IP address 10.134.78.180 has logged off.
4 I 2017-06-16T11:00:15.174 Login ID: USERID from webguis at IP address 10.104.209.144 has logged off.
5 I 2017-06-16T10:40:14.352 Login ID: USERID from webguis at IP address 10.104.209.144 has logged off.
system> readlog
6 E SERVPROC 12/18/03 10:09:31 Fan 2 Fault. Multiple fan failures
7 E SERVPROC 12/18/03 10:09:31 Fan 1 Fault. Single fan failure
8 I SERVPROC 12/18/03 10:09:25 Ethernet[0] Link Established at 100Mb, Full Duplex.
9 I SERVPROC 12/18/03 10:09:24 Ethernet[0] configured to do Auto Speed/Auto Duplex.
10 I SERVPROC 12/18/03 10:09:24 Ethernet[0] MAC Address currently
being used: 0x00-09-6B-CA-0C-80
system>
syshealth command
This command provides a summary of the health or active events.
Use the syshealth command to display a summary of the health or active events of the server. The power
state, system state, hardware state (includes fan, power supply, storage, processor, memory), restart count,
and IMM software status are displayed.
Syntax:
syshealth [argument]
argument:
summary -display the system health summary
activeevents -display active events
cooling - display cooling devices health status
power - display power modules health status
storage - display local storage health status
processors - display processors health status
memory - display memory health status
Example:
system> syshealth summary
Power On
State OS booted
Restarts 29
100 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
temps command
This command displays all temperature and temperature threshold information.
Use the temps command to display all the temperatures and temperature thresholds. The same set of
temperatures are displayed as in the web interface.
Notes:
1. The output has the following column headings:
WR: warning reset (Positive-going Threshold Hysteresis value)
W: warning (Upper non-critical Threshold)
T: temperature (Current value)
SS: soft shutdown (Upper critical Threshold)
HS: hard shutdown (Upper non-recoverable Threshold)
2. All temperature values are in degrees Fahrenheit/Celsius.
3. N/A represents not applicable.
volts command
Use this command to display the server voltage information.
Use the volts command to display all the voltages and voltage thresholds. The same set of voltages are
displayed as in the web interface.
vpd command
This command displays configuration and informational data (vital product data) associated with the
hardware and software of the server.
Use the vpd command to display vital product data for the system (sys), IMM (bmc), server BIOS (uefi),
Lenovo XClarity Provisioning Manager (lxpm), server firmware (fw), server components (comp) and PCIe
devices (pcie). The same information is displayed as in the web interface.
Syntax:
vpd sys - displays Vital Product Data for the system
vpd bmc - displays Vital Product Data for the management controller
vpd uefi - displays Vital Product Data for system BIOS
vpd lxpm - displays Vital Product Data for system LXPM
vpd fw - displays Vital Product Data for the system firmware
vpd comp - displays Vital Product Data for the system components
vpd pmem - displays Vital Product Data for Intel Optane PMem
vpd pcie - displays Vital Product Data for PCIe devices
Example:
system> vpd bmc
Type Status Version Build ReleaseDate
---- ------- ----- ------
BMC (Primary) Active 0.00 DVI399T 2017/06/06
BMC (Backup) Inactive 1.00 TEI305J 2017/04/13
system>
power command
This command describes how to control the server power.
Use the power command to control the server power. To issue power commands, you must have the
Remote Server Power/Restart Access authority level.
The following table contains a subset of commands that can be used with the power command.
102 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 13. power command
The following table is a multi-row three column table consisting of the power commands, command
descriptions, and associated values for the commands.
power off Use this command to turn off the server power. on, off
Note: The -s option shuts down the operating system
before the server is turned off.
power cycle Use this command to turn off the server power and then
turn on the server power.
Note: The -s option shuts down the operating system
before the server is turned off.
power enterS3 Use this command to place the operating system into the
S3 (sleep) mode.
Note: This command is used only when the operating
system is on. The S3 mode is not supported on all servers.
power rp Use this option to specify the host power restore policy. alwayson|alwaysoff|restore
power Use this command to wake up the operating system from
S3resume the S3 (sleep) mode.
Note: This command is used only when the operating
system is on. The S3 mode is not supported on all servers.
power state Use this command to display the server power state and on, off
the current state of the server.
The following table contains the options for the power on, power off, and power cycle commands.
Syntax:
power on
power off [-s]
power state
power cycle [-s]
To shut down the operating system and power off the server every Sunday at 1:30, enter the following
command:
system> power off
-every Sun -t 01:30
To shut down the operating system and restart the server every day at 1:30, enter the following command:
system> power cycle
-every Day -t 01:30
To power on the server every Monday at 1:30, enter the following command:
system> power on
-every Mon -t 13:00
To power on the server on Dec 31 2013 at 11:30 PM, enter the following command:
system> power on
-d 12/31/2013 -t 23:30
reset command
This command describes how to reset the server.
Use the reset command to restart the server. To use this command, you must have power and restart
access authority.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
104 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 15. reset command (continued)
Syntax:
reset [option]
option:
-s
-d
-nmi
fuelg command
This command displays information about the server power.
Use the fuelg command to display information about server power usage and configure server power
management. This command also configures policies for power redundancy loss. The following table shows
the arguments for the options.
-period A numeric value to display history (1, 6, 12, 24 hours) numeric value in hours
-pm Set the policy mode for loss of redundant power.
• bt- basic with throttling
• rt- redundant with throttling (default)
• ort- N_1 redundant with throttling
-zm Enable or disable zero output mode. This setting can only on, off
be set when the policy mode is set to redundant with
throttling.
Syntax:
fuelg [options]
option:
-pme on|off
-pcapmode input|output
-pcap
-history
-period
-pm bt|r|rt
-zm on|off
-perf
-pc input|output
Example:
system> fuelg
-pme: on
system>
pxeboot command
This command displays and sets the condition of the Preboot eXecution Environment.
Running pxeboot with no options, returns the current Preboot eXecution Environment setting. The following
table shows the arguments for the options.
Syntax:
pxeboot [options]
option:
-en state
106 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Example:
system> pxeboot
-en disabled
system>
There is only one serial redirect command: the “console command” on page 107.
console command
This command is used to start a serial redirect console session.
Use the console command to start a serial redirect console session to the designated serial port of the IMM.
Syntax:
console 1
Configuration commands
This topic provides an alphabetic list of configuration CLI commands.
accseccfg command
Use this command to display and configure account security settings.
Running the accseccfg command with no options displays all account security information. The following
table shows the arguments for the options.
-lp Lockout period after maximum login Between 0 and 2880, 0 = lockout period does not
failures (minutes). expire
-pe Password expiration time period Between 0 and 365, 0 = never expire
(days).
-pew Password expiration warning time Between 0 and 30, 0 = never warn
period
Note: The Password expiration
warning time period must be less than
Password expiration time period.
-pc Password complexity rules enabled. on, off
-pl Password length. If password complexity rules are enabled, the password
length is between 8 and 32. Otherwise, it is between 0
and 32.
-lf Maximum number of login failures. Between 0 and 10, 0 = never locked
Example:
system> accseccfg
-legacy
-am local
-lp 2
-pe 0
-pr off
-pd 1
-pl 4
-ci 0
-lf 0
-chgdft off
-chgnew off
-rc 0
-wt user
system>
alertcfg command
Use this command to display and configure the IMM global remote alert parameters.
108 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Running the alertcfg command with no options displays all global remote alert parameters. The following
table shows the arguments for the options.
Syntax:
alertcfg [options]
options:
-rl retry_limit
-dr retry_delay
-da agent_delay
Example:
system>alertcfg
-dr 1.0
-da 2.5
-rl 5
system>
asu command
This command is used to configure UEFI settings.
Advanced Settings Utility commands (ASU) are used to configure UEFI settings. The host system must be
rebooted for any UEFI setting changes to take effect.
The following table contains a subset of commands that can be used with the asu command.
help Use this command to display help information for one or setting
more settings.
showvalues Use this command to display all possible values for one or setting
more settings.
Notes:
• This command will display information about the
allowable values for the setting.
• The minimum and maximum number of instances
allowed for the setting is displayed.
• The default value will be displayed if available.
• The default value is enclosed with opening and closing
angle brackets (< and >).
• Text values show the minimum and maximum length
and regular expression.
Notes:
• In the command syntax, setting is the name of a setting that you want to view or change, and value is the value that
you are placing on the setting.
• Setting can be more than one name, except when using the set command.
• Setting can contain wildcards, for example an asterisk (*) or a question mark (?).
• Setting can be a group, a setting name, or all.
Examples of the syntax for the asu command are presented in the following list:
• To display all of the asu command options enter asu --help.
• To display verbose help for all commands enter asu -v --help.
• To display verbose help for one command enter asu -v set --help.
• To change a value enter asu set setting value.
• To display the current value enter asu show setting.
• To display settings in long batch format enter asu show -l -b all
• To display all possible values for a setting enter asu showvalues setting. Example show values command:
system> asu showvalues S*.POST*
110 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
SystemRecovery.POSTWatchdogTimer==<Disable>=Enable
SystemRecovery.POSTWatchdogTimerValue=numeric min=5 max=20 step=1 default=5
system>
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
Syntax:
asu [options] command [cmdopts]
options:
-v verbose output
--help display main help
cmdopts:
--help help for the command
Use the asu transaction commands to set multiple UEFI settings and create and execute batch mode
commands. Use the tropen and trset commands to create a transaction file containing multiple settings to
be applied. A transaction with a given id is opened using the tropen command. Settings are added to the set
using the trset command. The completed transaction is committed using the trcommit command. When
you are finished with the transaction, it can be deleted with the trrm command.
Note: The UEFI settings restore operation will create a transaction with an id using a random three digit
number.
The following table contains transaction commands that can be used with the asu command.
The following table is a multi-row three column table consisting of the transactions commands, the
command descriptions, and associated values for the commands.
trset id This command adds one or more settings or value pairs to Id is the identifying string, 1 - 3
a transaction. alphanumeric characters.
trlist id This command displays the contents of the transaction file Id is the identifying string, 1 - 3
first. This can be useful when the transaction file is created alphanumeric characters.
in the CLI shell.
trcommit id This command commits and executes the contents of the Id is the identifying string, 1 - 3
transaction file. The results of the execution and any errors alphanumeric characters.
will be displayed.
trrm id This command removes the transaction file after it has Id is the identifying string, 1 - 3
been committed. alphanumeric characters.
backup command
Use this command to create a backup file containing the current system security settings.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
112 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Syntax:
Example:
system> backup f xcc-back.cli pp xxxxxx ip 192.168.70.200
ok
system>
dhcpinfo command
Use this command to view the DHCP server-assigned IP configuration for eth0.
Use the dhcpinfo command to view the DHCP server-assigned IP configuration for eth0, if the interface is
configured automatically by a DHCP server. You can use the ifconfig command to enable or disable DHCP.
Syntax:
dhcpinfo eth0
Option Description
-server DHCP server that assigned the configuration
-n Assigned host name
Option Description
dns command
Use this command to view and set the DNS configuration of the IMM.
Note: In a Flex System, DNS settings cannot be modified on the IMM. DNS settings are managed by the
CMM.
Running the dns command with no options displays all DNS configuration information. The following table
shows the arguments for the options.
-i2 Secondary IPv4 DNS IP address IP address in dotted decimal IP address format.
-i3 Tertiary IPv4 DNS server IP address IP address in dotted decimal IP address format.
Syntax:
dns [options]
114 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
option:
-state state
-ddns state
-i1 first_ipv4_ip_address
-i2 second_ipv4_ip_address
-i3 third_ipv4_ip_address
-i61 first_ipv6_ip_address
-i62 second_ipv6_ip_address
-i63 third_ipv6_ip_address
-p priority
Note: The following example shows an IMM configuration where DNS is disabled.
Example:
system> dns
-state : disabled
-i1 : 0.0.0.0
-i2 : 0.0.0.0
-i3 : 0.0.0.0
-i61 : ::
-i62 : ::
-i63 : ::
-ddns : enabled
-dnsrc : DHCP
-ddn :
-ddncur : labs.lenovo.com
-p : ipv6
-dscvry : enabled
system>
The following table describes the options used in the previous example.
Option Description
-state State of DNS (on or off)
Option Description
lite off Let BMC quit encapsulation mode and open global access to all users
ethtousb command
Use the ethtousb command to display and configure Ethernet to Ethernet-over-USB port mapping.
The command allows you to map an external Ethernet port number to a different port number for Ethernet-
over-USB.
Running the ethtousb command with no options displays Ethernet-over-USB information. The following
table shows the arguments for the options.
Syntax:
ethtousb [options]
option:
-en state
-mxport_pair
-rm map_index
Example:
system> ethtousb -en enabled -m1 100:200 -m2 101:201
system> ethtousb
-en enabled
-m1 100:200
-m2 101:201
system> ethtousb -rm 1
116 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
system>
firewall command
Use this command to configure the firewall to restrict access from certain addresses and optionally limits
access time frame. If no option is specified, the current settings will be displayed.
-clr Clear the firewall rule for a given type ip, mac, datetime, interval, all
-iplp IP address lockout period in minutes. Numeric value between 0 and 2880, 0 =
never expire
-iplf Maximum number of login failures before Numeric value between 0 and 32, 0 = never
IP address is locked out. lock
Note: If this value is not 0, then it must be
greater than or equal to <Maximum
number of login failures> that is set by
<accseccfg -lf>
Example:
· “firewall”: Show all options’ value and IP addresses blocking list.
· “firewall -bips 192.168.1.1,192.168.1.0/24,192.168.1.1-192.168.1.5”: Block the access from multi IPs
· “firewall -bti 01:00-02:00,05:05-10:30,14:15-20:00”: Block all access during 01:00-02:00,05:05-10:30,14:15-20:00 every day.
gprofile command
Use this command to display and configure group profiles for the IMM.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
Syntax:
gprofile [1 - 16 group_profile_slot_number] [options]
options:
-clear state
-n group_name
-a authority level:
-nsc network and security
-am user account management
-rca remote console access
-rcvma remote console and remote disk access
-pr remote server power/restart access
-bc basic adapter configuration
-cel ability to clear event logs
-ac advanced adapter configuration
-h help
hashpw command
Use this command with the -sw option to enable/disable the third-party password function or with the -re
option to enable/disable the allowance of retrieving third-party password.
118 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 31. hashpw command
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
Example:
system> hashpw –sw enabled –re enabled
system> users -5 –n guest5 –shp ef92b778bafe771e89245b89ecbc08a44a4e166c06659911881f383d4473e94f –a super
system> users -5 ghp
ef92b778bafe771e89245b89ecbc08a44a4e166c06659911881f383d4473e94f
system> users
Account Login ID Advanced Attribute Role Password Expires
------- -------- ------------------ ------ ----------------
1 USERID Native Administrator Password doesn't expire
5 guest5 Third-party Password Administrator 90 day(s)
ifconfig command
Use this command to configure the Ethernet interface.
Type ifconfig eth0 to display the current Ethernet interface configuration. To change the Ethernet interface
configuration, type the options, followed by the values. To change the interface configuration, you must have
at least Adapter Networking and Security Configuration authority.
Note: In a Flex System, the VLAN settings are managed by a Flex System CMM and cannot be modified on
the IMM.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
-g6 Gateway or default route IP address for the gateway or default route for
Ethernet channel 0 in IPv6.
-dhcp6 DHCPv6 state enabled, disabled
120 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 32. ifconfig command (continued)
Syntax:
ifconfig eth0 [options]
options:
-state interface_state
-c config_method
-i static_ipv4_ip_address
-g ipv4_gateway_address
-s subnet_mask
-n hostname
-r data_rate
-d duplex_mode
-m max_transmission_unit
-l locally_administered_MAC
-b burned_in_MAC_address
-dn domain_name
-auto state
-nic state
-failover mode
-nssync state
-address_table
-lla ipv6_link_local_addr
-dhcp6 state
-ipv6 state
-ipv6static state
-sa6 state
-i6 static_ipv6_ip_address
-g6 ipv6_gateway_address
-p6 length
-vlan state
-vlanid VLAN ID
Example:
system> ifconfig eth0
-state : enabled
-c : dthens
-ghn : disabled
-i : 192.168.70.125
keycfg command
Use this command to display, add, or delete activation keys.
Notes:
• When the keycfg command is run without any options, the list of installed activation keys is displayed.
Key information displayed includes an index number for each activation key, the type of activation key, the
date through which the key is valid, the number of uses remaining, the key status, and a key description.
• Add new activation keys through file transfer.
• Delete old keys by specifying the number of the key or the type of key. When deleting keys by type, only
the first key of a given type is deleted.
122 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 33. keycfg command (continued)
-f File name for activation key Valid file name for activation key file
to add
-del Delete activation key by Valid activation key index number from keycfg listing
index number
-deltype Delete activation key by key Valid key type value
type
Syntax:
keycfg [options]
option:
-add
-ip tftp/sftp server ip address
-pn pn port number of tftp/sftp server (default 69/22)
-u username for sftp server
-pw password for sftp server
-f filename
-del n ( where n is a valid ID number from listing)
-deltype x ( where x is a Type value)
Example:
system> keycfg
ID Type Valid Uses Status Description
1 4 10/10/2010 5 "valid" "IMM remote presence"
2 3 10/20/2010 2 "valid" "IMM feature
3 32796 NO CONSTRAINTS NO CONSTRAINTS "valid" "IBM Security Key Lifecycle Manager for SEDs FoD"
system>
Note: The Description field for ID number 3 is displayed on separate lines due to space limitations.
ldap command
Use this command to display and configure the LDAP protocol configuration parameters.
-fn Forest name For active directory environments. String of up to 127 characters.
-g Group search attribute String of up to 63 characters for group_search_attr
-s2pn Server 2 port number A numeric port number up to 5 digits for port_number
-s3pn Server 3 port number A numeric port number up to 5 digits for port_number
-s4pn Server 4 port number A numeric port number up to 5 digits for port_number
-t Server target name When the rbs option is enabled, this field specifies a target name that
can be associated with one or more roles on the Active Directory server
through the Role-Based Security (RBS) Snap-In tool.
-u UID search attribute String of up to 63 characters for search_attrib
-v Get LDAP server address off, on
through DNS
124 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Syntax:
ldap [options]
options:
-a loc|ldap|locld|ldloc
-aom enable/disabled
-b anon|client|login
-c client_dn
-d search_domain
-f group_filter
-fn forest_name
-g group_search_attr
-l string
-p client_pw
-pc confirm_pw
-ep encrypted_pw
-r root_dn
-rbs enable|disabled
-s1ip host name/ip_addr
-s2ip host name/ip_addr
-s3ip host name/ip_addr
-s4ip host name/ip_addr
-s1pn port_number
-s2pn port_number
-s3pn port_number
-s4pn port_number
-t name
-u search_attrib
-v off|on
-h
ntp command
Use this command to display and configure the Network Time Protocol (NTP).
Example:
system> ntp
-en: disabled
-f: 3 minutes
-i: not set
portcfg command
Use this command to configure the IMM for the serial redirection feature.
The IMM must be configured to match the server internal serial port settings. To change the serial port
configuration, type the options, followed by the values. To change the serial port configuration, you must
have at least Adapter Networking and Security Configuration authority.
Note: The server external serial port can only be used by the IMM for IPMI functionality. The CLI is not
supported through the serial port. The serred and cliauth options that were present in the Remote
Supervisor Adapter II CLI are not supported.
Running the portcfg command with no options displays serial port configuration. The following table shows
the arguments for the options.
Note: The number of data bits (8) is set in the hardware and cannot be changed.
Syntax:
portcfg [options]
options:
-b baud_rate
-p parity
-s stopbits
126 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
-climode mode
Example:
system> portcfg
-b: 57600
-climode: 2 (CLI with user defined keystroke sequence)
-p: even
-s: 1
system> portcfg -b 38400
ok
system>
portcontrol command
Use this command to turn a network service port on or off.
Currently this command only supports control of the port for the IPMI protocol. Type portcontrol to display
the IPMI port state. To enable or disable the IPMI network port, type the -ipmi option followed by the on or
off values.
Syntax:
portcontrol [options]
options:
-ipmi on/off
ports command
Use this command to display and configure IMM ports.
Running the ports command with no options displays information for all IMM ports. The following table
shows the arguments for the options.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
-cimhp CIM over HTTP port number Default port number: 5988
-cimhsp CIM over HTTPS port number Default port number: 5989
Syntax:
ports [options]
option:
-open
-reset
-httpp port_number
-httpsp port_number
-sshp port_number
-snmpap port_number
-snmptp port_number
-rpp port_number
-cimhp port_number
-cimhsp port_number
Example:
system> ports
128 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
-httpp 80
-httpsp 443
-rpp 3900
-snmpap 161
-snmptp 162
-sshp 22
-cimhp 5988
-cimhsp 5989
system>
rdmount command
Use this command to mount remote disk images or network shares
Notes:
• Up to two files can be uploaded in the XClarity Controller memory and mounted as virtual media using the
XClarity Controller RDOC feature. The total size for both files must not exceed 50 MB. The uploaded
images are read only unless the –rw option is used.
• When using the HTTP, SFTP, or FTP protocols to mount or map the images, the total size for all the
images must not exceed 50 MB. There is no size limit if the NFS or SAMBA protocols are used.
Option Description
-r rdoc operation (if used, must be first option)
-r -map: mount the RDOC images
-rw read-write
-u user
-p password
Syntax:
restore [options]
option:
-f filename
-pp password
-ip ip_address
-pn port_number
-u
username
-pw password
Example:
system> restore f xcc-back.cli pp xxxxxx ip 192.168.70.200
ok
system>
restoredefaults command
Use this command to restore all IMM settings to the factory default.
Syntax:
restoredefaults
Example:
system> restoredefaults
This action will cause all IMM settings to be set to factory defaults.
If this is the local system, you will lose your TCP/IP connection as a result.
You will need to reconfigure the IMM network interface to restore connectivity.
After the IMM configuration is cleared, the IMM will be restarted.
130 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Proceed? (y/n)
Y
Restoring defaults
roles command
Use this command to display or configure roles.
d Delete a row
Syntax
roles [-options] - display/configure roles
- role_account -role number[3-31]
options:
-n - role name (limited to 32 characters)
-p - privilege (custom:am|rca|rcvma|pr|cel|bc|nsc|ac|us)
am - User account management access
rca - Remote console access
rcvma - Remote console and remote disk (virtual media) access
pr - Remote server power/restart access
cel - Ability to clear event logs
bc - Adapter Configuration (basic)
nsc - Adapter Configuration (network and security)
ac - Adapter Configuration (advanced)
us - UEFI Security
Note: the above custom permission flags can be used in any combination
-d - delete a row
system> roles
Account Role Privilege Assigned To
------- ---------------------------------- ------------------------- -------------------------------
0 Administrator all USERID
1 ReadOnly none
2 Operator custom:pr|cel|bc|nsc
3 test1 custom:am|rca|rcvma
seccfg command
Use this command to perform firmware rollback.
set command
Use this command to change some IMM settings.
The following table is a single-row three column table consisting of the command description and associated
information.
Syntax:
set [options]
option:
value
132 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
smtp command
Use this command to display and configure settings for the SMTP interface.
Running the smtp command with no options displays all SMTP interface information. The following table
shows the arguments for the options.
Syntax:
smtp [options]
option:
-auth enabled|disabled
-authepw password
-authmd CRAM-MD5|LOGIN
-authn username
-authpw password
-s ip_address_or_hostname
-pn port_number
Example:
system> smtp
-s test.com
-pn 25
system>
snmp command
Use this command to display and configure SNMP interface information.
Running the snmp command with no options displays all SNMP interface information. The following table
shows the arguments for the options.
134 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 45. snmp command (continued)
Syntax:
snmp [options]
option:
-a3 state
-t state
-l location
-cn contact_name
-t1 state
-c community name
-ci community IP address/hostname
-t2 state
-ct community name
-cti community IP address/hostname
-eid engine id
Example:
system> snmp
-t enabled
-a3 enabled
-l ZhangjiangMansion
-cn Kelvin
-t1 enabled
-c community1
-ci host1
-t2 enabled
-ct community2
-cti host2
-eid XCC-7Z70-DSYM09X
system>
snmpalerts command
Use this command to manage alerts sent via the SNMP.
Running snmpalerts with no options displays all SNMP alert settings. The following table shows the
arguments for the options.
136 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 46. snmpalerts command (continued)
Syntax:
snmpalerts [options]
options:
-status status
-crt event_type
-crten state
-wrn event_type
-wrnen state
-sys event_type
-sysen state
srcfg command
Use this command to indicate the key sequence to enter the CLI from the serial redirection mode.
To change the serial redirect configuration, type the options, followed by the values. To change the serial
redirect configuration, you must have at least Adapter Networking and Security Configuration authority.
Note: The IMM hardware does not provide for a serial port to serial port pass-through capability. Therefore
the -passthru and entercliseq options which are present in the Remote Supervisor Adapter II CLI are not
supported.
Running the srcfg command with no options displays the current serial redirection keystroke sequence. The
following table shows the arguments for the srcfg -entercliseq command option.
Syntax:
srcfg [options]
options:
-entercliseq entercli_keyseq
Example:
system> srcfg
-entercliseq ^[Q
system>
sshcfg command
Use this command to display and configure SSH parameters.
Running the sshcfg command with no options displays all SSH parameters. The following table shows the
arguments for the options.
Syntax:
sshcfg [options]
option:
-cstatus state
-hk gen
-hk rsa
Example:
system> sshcfg
-cstatus enabled
CLI SSH port 22
ssh-rsa 2048 bit fingerprint: b4:a3:5d:df:0f:87:0a:95:f4:d4:7d:c1:8c:27:51:61
1 SSH public keys installed
system>
138 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
ssl command
Use this command to display and configure the SSL parameters.
To enable an SSL client, a client certificate must be installed. Running the ssl command with no options
displays SSL parameters. The following table shows the arguments for the options.
Syntax:
portcfg [options]
options:
-ce state
-se state
-cime state
Parameters: The following parameters are presented in the option status display for the ssl command and
are output only from the CLI:
sslcfg command
Use this command to display and configure the SSL for the IMM and manage certificates.
Running the sslcfg command with no options displays all SSL configuration information. The sslcfg
command is used to generate a new encryption key and self-signed certificate or certificate signing request
(CSR). The following table shows the arguments for the options.
140 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 50. sslcfg command (continued)
-dnld Download certificate file This option takes no arguments; but, must also specify values for the
-cert or -csr command option (depending on the certificate type being
downloaded). This option takes no arguments; but, must also specify
values for the -i command option, and -l (optional) command option.
-upld Imports certificate file This option takes no arguments, but must also specify values for the
-cert, -i, and -l command options.
-tcx Trusted certificate x for SSL import, download, remove
client Note: The trusted certificate number, x, is specified as an integer from 1
to 3 in the command option.
-c Country Country code (2 letters)
Note: Required when generating a self-signed certificate or CSR.
-sp State or province Quote-delimited string (maximum 60 characters)
Note: Required when generating a self-signed certificate or CSR.
Syntax:
sslcfg [options]
option:
-server state
-client state
-cim state
-cert certificate_type
-csr certificate_type
-i ip_address
-pn
port_number
-u
username
-pw password
-l filename
-dnld
-upld
-tc xaction
-c country_code
-sp state_or_province
-cl city_or_locality
-on organization_name
-hn bmc_hostname
-cp contact_person
-ea email_address
-ou organizational_unit
-s surname
-gn given_name
-in initials
-dq dn_qualifier
-cpwd challenge_password
-un unstructured_name
Examples:
system> sslcfg
-server enabled
-client disabled
-sysdir enabled
SSL Server Certificate status:
A self-signed certificate is installed
SSL Client Certificate status:
A self-signed certificate is installed
SSL CIM Certificate status:
A self-signed certificate is installed
SSL Client Trusted Certificate status:
Trusted Certificate 1: Not available
Trusted Certificate 2: Not available
Trusted Certificate 3: Not available
Trusted Certificate 4: Not available
142 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
• To generate a CSR for a storage key, enter the following command:
system> sslcfg
-csr storekey -c US -sp NC -cl rtp -on Lenovo -hn XCC-5cf3fc6e0c9d
-cp Contact -ea "" -ou""
ok
The above example is displayed on multiple lines due to space limitations.
• To download a certificate from the IMM to another server, enter the following command:
system> sslcfg
-csr storekey -dnld -i 192.168.70.230 -l storekey.csr
ok
• To upload the certificate processed by the Certificate Authority (CA), enter the following command:
system> sslcfg
-cert storekey -upld -i 192.168.70.230 -l tklm.der
• To generate a self-signed certificate, enter the following command:
system> sslcfg
-cert storekey -c US -sp NC -cl rtp -on Lenovo -hn XCC-5cf3fc6e0c9d
-cp Contact -ea "" -ou "
ok
The above example is displayed on multiple lines due to space limitations.
storekeycfg command
Use this command to configure the host name or IP address and network port for a SKLM server.
You can configure up to four SKLM server targets. The storekeycfg command is also used to install and
remove the certificates that are used by the IMM for authentication to the SKLM server.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
-ip Host name or IP address for Valid host name or IP address for TFTP/SFTP server
the TFTP/SFTP server
-pn Port number of the TFTP or Valid port number for TFTP/SFTP server (default value is 69/22)
SFTP server
-u User name for SFTP server Valid user name for SFTP server
-pw Password for SFTP server Valid password for SFTP server
-f File name for activation key Valid file name for activation key file name
-sxip Add the host name or IP Valid host name or IP address for SKLM server. Numeric value of 1, 2,
address for the SKLM server 3, or 4.
-sxpn Add the port number of the Valid port number for SKLM server. Numeric value of 1, 2, 3, or 4.
SKLM server
-testx Test the configuration and Numeric value of 1, 2, 3, or 4
connection to the SKLM
server
-h Display the command usage
and options
Syntax:
storekeycfg [options]
options:
-add state
-ip ip_address
-pn port_number
-u username
-pw password
-f filename
-del key_index
-dgrp device_group_name
-sxip ip_address
-sxpn port_number
-testx numeric value of SKLM server
-h
Examples:
To configure the SKLM server address and port number, enter the following command:
system> storekeycfg
-s1ip 192.168.70.249
system> ok
syncrep command
Use this command to launch firmware sync from remote repository.
144 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 52. syncrep command
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
Syntax
syncrep [options] Launch firmware sync from remote repository
options:
-t <samba|nfs> protocol to connect repository
-l location of remote repository (URL format)
-u User
-p Password
-o option (extra option string for samba and nfs mounts)
-d domain (domain for samba mount)
-q query current update status
-c cancel the sync process
Example
(1) start sync with repository
system> syncrep -t samba -l url -u user -p password
(2) query current update status
system> syncrep -q
(3)cancel the sync process
system> syncrep -c
thermal command
Use this command to display and configure the thermal mode policy of the host system.
Running the thermal command with no options displays the thermal mode policy. The following table shows
the arguments for the options.
Example:
system> thermal
-mode normal
-table 80860126 1 10DE0DFA 3
system>
timeouts command
Use this command to display or change the timeout values.
The following table shows the arguments for the timeout values. These values match the graduated scale
pull-down options for server timeouts on the web interface.
Syntax:
timeouts [options]
options:
-f power_off_delay_watchdog_option
-o OS_watchdog_option
-l loader_watchdog_option
-s OS failure screen capture with HW error
Example:
system> timeouts
-o disabled
-l 3.5
-f disabled
-s disabled
system> timeouts -o 2.5
ok
system> timeouts
146 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
-o 2.5
-l 3.5
-f disabled
-s disabled
tls command
Use this command to set the minimum TLS level.
Notes:
1. When the cryptography mode is set to the NIST-800-131A Compliance mode, the TLS version must be set to 1.2.
Usage:
tls [-options] - configures the minimum TLS level
-min <1.0 | 1.1 | 1.2 | 1.3> - Selects the minimum TLS level
-h - Lists usage and options
Examples:
To get the usage for the tls command, issue the following command:
system> tls
-h
system>
To change the current tls version to 1.2, issue the following command:
system> tls
-min 1.2
ok
system>
trespass command
Use this command to configure and display the trespass messages.
The trespass command can be used to configure and display the trespass messages. The trespass
messages will be displayed to any user logging in through the WEB or CLI interface.
Option Description
-s Configure trespass messages
Syntax:
usage:
trespass display the trespass message
-s <trespass message> configure trespass message
-h - Lists usage and options
Example:
uefipw command
Use this command to configure UEFI admin passwords. The password is write-only.
The uefipw command can be used with the “-p” option to configure the UEFI admin password for XCC or
with the “-ep” option for LXCA to configure the UEFI admin password by CLI interface. The password is
write-only.
The following table is a multi-row two column table consisting of the options and option descriptions.
Option Description
-cp Current password (limited to 20 characters)
-p New password (limited to 20 characters)
-cep Current password encrypted
-ep New password encrypted
Syntax:
usage:
uefipw [-options] - Configure the UEFI admin password
options:
-cp - current password (limited to 20 characters)
148 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
-p - new password (limited to 20 characters)
-cep - current password encrypted
-ep - new password encrypted
usbeth command
Use this command to enable or disable the in-band LAN over USB interface.
Syntax:
usbeth [options]
options:
-en <enabled|disabled>
Example:
system>usbeth
-en : disabled
system>usbeth -en enabled
ok
system>usbeth
-en : disabled
usbfp command
Use this command to control the BMC use of the front panel USB port
The following table is a multi-row two column table consisting of the options and option descriptions.
Option Description
-mode <bmc | server | shared> Set usage mode to BMC, server, or shared
-btn <on | off> Enable using id button to toggle owner (shared mode)
-own <bmc | server > Set owner to bmc or server (shared mode)
users command
Use this command to access all user accounts and their authority levels.
The users command is also used to create new user accounts and modify existing accounts. Running the
users command with no options displays a list of users and some basic user information. The following table
shows the arguments for the options.
-clear Erase specified user User account index number to erase must be specified, following the
account form:
If you are authorized, you users -clear -user_index
can remove your own
account or the account of
other users, even if they are
currently logged in, unless it
is the only account
remaining with User
Account Management
privileges. Sessions that are
already in progress when
user accounts are deleted
will not be automatically
terminated.
-curr Display users currently
logged in
150 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 59. users command (continued)
-add Add SSH public key for user Quote-delimited key in OpenSSH format
(SSH public key option) Notes:
• The -add option is used exclusive of all other users -pk command
options.
• When using the SSH public key options, the -pk option must be
used after the user index (-userindex option), of the form: users -2
-pk -add "AAAAB3NzC1yc2EAAAABIwAAA QEAvfnTUzRF7pdBuaBy4dO/
aIFasa/Gtc+o/wlZnuC4aD
HMA1UmnMyLOCiIaNOy4OOICEKCqjKEhrYymtAoVtfKApv Y39GpnSGRC/
qcLGWLM4cmirKL5kxHNOqIcwbT1NPceoKH j46X7E
+mqlfWnAhhjDpcVFjagM3Ek2y7w/tBGrwGgN7DP
HJU1tzcJy68mEAnIrzjUoR98Q3/B9cJD77ydGKe8rPdI2
hIEpXR5dNUiupA1Yd8PSSMgdukASKEd3eRRZTBl3SAtMu
cUsTkYjlXcqex1OQz4+N50R6MbNcwlsx+mTEAvvcpJhug
a70UNPGhLJMl6k7jeJiQ8Xd2p XbOZQ=="
• For Flex nodes, the users commands are limited to only local IPMI
and SNMP accounts. The option -add is not supported for Flex
Systems.
-dnld Download the specified Requires a -key_index to specify the key to download and the -i and -l
SSH public key options to specify the download location on another computer running
(SSH public key option) a TFTP server.
Notes:
• The -dnld option is used exclusive of all other users -pk command
options (except for -i, -l, and -key_index).
• When using the SSH public key options, the -pk option must be
used after the user index (-userindex option), of the form: users -2
-pk -dnld -1 -i tftp://9.72.216.40/ -l file.key.
-i IP address of TFTP/SFTP Valid IP address
server for uploading or Note: The -i option is required by the users -pk -upld and users -pk
downloading a key file -dnld command options.
(SSH public key option)
-pn Port number of TFTP/SFTP Valid port number (default 69/22)
server Note: An optional parameter for the users -pk -upld and users -pk
(SSH public key option) -dnld command options.
-u User name for SFTP server Valid user name
(SSH public key option) Note: An optional parameter for the users -pk -upld and users -pk
-dnld command options.
-pw Password for SFTP server Valid password
(SSH public key option) Note: An optional parameter for the users -pk -upld and users -pk
-dnld command options.
-af Accept connections from A comma-separated list of hostnames and IP addresses, limited to 511
host characters. Valid characters include: alphanumeric, comma, asterisk,
(SSH public key option) question mark, exclamation point, period, hyphen, colon and percent
sign.
-cm Comment Quote-delimited string of up to 255 characters.
(SSH public key option) Note: When using the SSH public key options, the -pk option must be
used after the user index (-userindex option), of the form: users -2 -pk
-cm "This is my comment.".
152 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Syntax:
users [-options] - display/configure user accounts
options:
-[1-12] - user account number
-l - display password expiration days
-n - username (limited to 16 characters)
-p - password (limited to 32 characters)
-shp - set hashpassword (total 64 characters)
-ssalt - set salt (limited to 64 characters)
-ghp - get hashpassword
-gsalt - get salt
-ep - encrypted password (used with backup/restore )
Example:
system> users
Account Login ID Advanced Attribute Role Password Expires
------- -------- ------------------ ------ ----------------
1 USERID Native Administrator 89 day(s)
system> users -2 -n sptest -p Passw0rd12 -a super
The user is required to change the password when the user logs in to the management server for the first time
ok
system> users
Account Login ID Advanced Attribute Role Password Expires
------- -------- ------------------ ------ ----------------
alertentries command
Use this command to manage alert recipients.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
154 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 60. alertentries command (continued)
Example:
system> alertentries
1. test
2. <not used>
3. <not used>
4. <not used>
5. <not used>
6. <not used>
7. <not used>
8. <not used>
9. <not used>
10. <not used>
11. <not used>
12. <not used>
system> alertentries -1
-status off
-log off
-n test
-e [email protected]
-crt all
-wrn all
-sys none
system>
batch command
Use this command to execute one or more CLI commands that are contained in a file.
156 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 61. batch command (continued)
Syntax:
batch [options]
option:
-f filename
-ip ip_address
-pn port_number
-u
username
-pw password
Example:
system> batch -f sslcfg.cli -ip 192.168.70.200
1 : sslcfg client dnld ip 192.168.70.20
Command total/errors/warnings: 8 / 1 / 0
system>
clearcfg command
Use this command to set the IMM configuration to its factory defaults.
You must have at least Advanced Adapter Configuration authority to issue this command. After the
configuration of the IMM is cleared, the IMM is restarted.
clock command
Use this command to display the current date and time. You can set the UTC offset and daylight saving time
settings
The BMC obtains the time from the host server or NTP server.
The time obtained from the host may be local time or UTC time. The host option should be set to UTC if NTP
is not used and the host uses UTC format. UTC offset can be in the format of +0200, +2:00, +2, or 2, for
positive offsets, and -0500, -5:00 or -5, for negative offsets. UTC offset and daylight savings times are used
with NTP or when the host mode is UTC.
For a UTC offset of +2, -7, -6, -5, -4 and -3 special daylight saving time settings are required.
• For +2, the daylight saving time options are as follows: off, ee (Eastern Europe), tky (Turkey), bei (Beirut),
amm (Amman), jem (Jerusalem).
• For -7, the daylight saving time settings are as follows: off, mtn (Mountain), maz (Mazatlan).
• For -6, the daylight saving time settings are as follows: off, mex (Mexico), cna (Central North America).
• For -5, the daylight saving time settings are as follows: off, cub (Cuba), ena (Eastern North America).
• For -4, the daylight saving time settings are as follows: off, asu (Asuncion), cui (Cuiaba), san (Santiago), cat
(Canada - Atlantic).
• For -3, the daylight saving time settings are as follows: off, gtb (Godthab), bre (Brazil - East).
Example:
system> clock
12/12/2011 13:15:23 GMT-5:00 dst on
identify command
Use this command to turn the chassis identification LED on or off, or to have it flash.
The -d option can be used with the -s on option to turn the LED on for only the number of seconds specified
with the -d option. The LED turns off after the number of seconds elapses.
Syntax:
identify [options]
options:
-s on/off/blink
-d seconds
Example:
system> identify
-s off
system> identify -s on -d 30
ok
system>
info command
Use this command to display and configure information about the IMM.
Running the info command with no options displays all IMM location and contact information. The following
table shows the arguments for the options.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
158 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 62. info command (continued)
1. Value is read only and cannot be reset if the IMM resides in a Flex System.
Syntax:
info [options]
option:
-name xcc_name
-contact contact_name
-location xcc_location
-room room_id
-rack rack_id
-rup rack_unit_position
-ruh rack_unit_height
-bbay blade_bay
spreset command
Use this command to restart the IMM.
You must have at least Advanced Adapter Configuration authority to issue this command.
Agent-less commands
This topic provides an alphabetic list of Agent-less commands.
storage command
Use this command to display and configure (if supported by the platform) information about the server's
storage devices that are managed by the IMM.
-show target_id info Display detailed information for the Where target_id is:
selected target that is managed by ctrl[x]|vol[x]|disk[x]|pool[x]
the IMM.
|flashdimm[x]
3
-show target_id firmware3 Display the firmware information Where target_id is:
for the selected target that is ctrl[x]|disk[x]|flashdimm[x]2
managed by the IMM.
-showlog target_id<m:n| Display the event logs of the Where target_id is: ctrl[x]4
all>3 selected target that is managed by m:n|all
the IMM.
Where m:n is one to the maximum number of event
logs
-config ctrl -scanforgn Detect the foreign RAID Where target_id is: ctrl[x]5
-target target_id3 configuration.
160 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 63. storage command (continued)
-config ctrl -clrforgn Clear the foreign RAID Where target_id is: ctrl[x]5
-target target_id3 configuration.
-config ctrl -clrcfg -target Clear the RAID configuration. Where target_id is: ctrl[x]5
target_id3
-config drv -mkoffline Change the drive state from online Where target_id is: disk[x]5
-target target_id3 to offline.
-config drv -mkonline Change the drive state from offline Where target_id is: disk[x]5
-target target_id3 to online.
-config drv -mkmissing Mark the offline drive as an Where target_id is: disk[x]5
-target target_id3 unconfigured good drive.
-config drv -prprm -target Prepare an unconfigured good Where target_id is: disk[x]5
target_id3 drive for removal.
-config drv -undoprprm Cancel the prepare an Where target_id is: disk[x]5
-target target_id3 unconfigured good drive for
removal operation.
-config drv -mkbad Change the unconfigured good Where target_id is: disk[x]5
-target target_id3 drive to a unconfigured bad drive.
-config drv -mkgood Change an unconfigured bad drive Where target_id is: disk[x]5
-target target_id3 to a unconfigured good drive.
or
-config drv -addhsp Assign the selected drive as a hot Where target_id is: disk[x]5
-[dedicated pools] -target spare to one controller or to
target_id3 existing storage pools.
-config drv -rmhsp -target Remove the hot spare. Where target_id is: disk[x]5
target_id3
-config vol -remove Remove one volume. Where target_id is: vol[x]5
-target target_id3
162 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 63. storage command (continued)
-config vol -add[-i] [-a] [-d] Create one volume for a new
• [-i <0|1>] is the cache I/O policy:
[-f] [-S] [-P] -target target_ storage pool when the target is a
id3 controller. – Type 0 for the Direct I/O policy
or
– Type 1 for the Cached I/O policy
Create one volume with an existing • [-a <0|2|3>] is the access policy:
storage pool when the target is a – Type 0 for the Read Write policy
storage pool.
– Type 2 for the Read Only policy
– Type 3 for the Blocked policy
• [-d <0|1|2>] is the disk cache policy:
– Type 0 if the policy remains unchanged
– Type 1 to enable the policy6
– Type 2 to disable the policy
• [-f <0/1/2>] is the type of initialization:
– Type 0 for no initialization
– Type 1 for quick initialization
– Type 2 for full initialization
• [-S volume_size] is the size of the new volume in
MB
• [-P strip_size] is the volume strip size for
example, 128K or 1M
• -target target_id is:
– ctrl[x] (new storage pool)5
– pool[x] (existing storage pool)5
Notes:
1. This command is only supported on servers where the IMM can access the RAID controller.
2. Firmware information is displayed only for associated controllers, disks, and Flash DIMMs. Firmware information
for associated pools and volumes are not displayed.
3. Information is displayed on multiple lines due to space limitations.
4. This command is only supported on servers that support RAID logs.
5. This command is only supported on servers that support RAID configurations.
6. The Enable value does not support RAID level 1 configurations.
7. A partial list of available options are listed here. The remaining options for the storage -config vol -add command
are listed in the following row.
Syntax:
storage [options]
option:
-config ctrl|drv|vol -option [-options] -target target_id
-list controllers|pools|volumes|drives
-list pools -target ctrl[x]
-list volumes -target ctrl[x]|pool[x]
-list drives -target ctrl[x]|pool[x]
-list devices
-list flashdimms
-show target_id
-show {ctrl[x]|pool[x]|disk[x]|vol[x]|flashdimm[x]} info
-show {ctrl[x]|disk[x]|flashdimm[x]}firmware
-showlog ctrl[x]m:n|all
-h help
Examples:
system> storage
-config ctrl -clrcfg -target ctrl[0]
ok
system>
system> storage
-config ctrl -clrforgn -target ctrl[0]
ok
system>
system> storage
-config ctrl -imptforgn -target ctrl[0]
ok
system>
system> storage
-config ctrl -scanforgn -target ctrl[0]
Detect 1 foreign configuration(s) on controller ctrl[0]
system>
system> storage
-config drv -addhsp -dedicated pool[0-1] -target disk[0-0]
ok
system>
system> storage
-config drv -addhsp -target disk[0-0]
ok
system>
system> storage
-config drv -mkbad -target disk[0-0]
164 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
ok
system>
system> storage
-config drv -mkgood -target disk[0-0]
ok
system>
system> storage
-config drv -mkmissing -target disk[0-0]
ok
system>
system> storage
-config drv -mkoffline -target disk[0-0]
ok
system>
system> storage
-config drv -mkonline -target disk[0-0]
ok
system>
system> storage
-config drv -prprm -target disk[0-0]
ok
system>
system> storage
-config drv -rmhsp -target disk[0-0]
ok
system>
system> storage
-config drv -undoprprm -target disk[0-0]
ok
system>
system> storage
-config vol -add -1 1 -target pool[0-1]
ok
system>
system> storage
-config vol -add -R 1 -D disk[0-0]:disk[0-1] -w 1 -r 2 -i 0 -a 0 -d 0 -f 0
-N LD_volume -S 100000 -P 64K -H disk[0-2] -target ctrl[0]
ok
system>
system> storage
-config vol -getfreecap -R 1 -D disk[0-0]:disk[0-1] -H disk[0-2] -target ctrl[0]
The drive group configuration is good with free capacity 500000MB
system>
system> storage
-config vol -remove -target vol[0-1]
ok
system>
system> storage
-config vol -set -N LD_volume -w 0 -target vol[0-0]
ok
system>
system> storage
-list controllers
ctrl[0] ServerRAID M5110e(Slot No. 0)
ctrl[1] ServerRAID M5110f(Slot No. 1)
system>
system> storage
-list drives
disk[0-0] Drive 0
disk[0-1] Drive 1
disk[0-2] Drive 2
166 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
UUID: 1234567890123456
Model Type / Model: 1234AHH
Serial No.: 12345678901
FRU No.: 5005076049CC4
Part No.: LSI2004
Cache Model Status: Unknown
Cache Model Memory Size: 300MB
Cache Model Serial No.: PBKUD0XTA0P04Y
PCI Slot Number: 0
PCI Bus Number: 2
PCI Device Number: 2
PCI Function Number: 10
PCI Device ID: 0x1000
PCI Subsystem Device ID: 0x1413
Ports: 2
Port 1: 12345678901234
Port 2: 12345678901235
Storage Pools: 2
pool[0-0]
Storage Pool 0
pool[0-1]
Storage Pool 1
Drives: 3
disk[0-0] Drive 0
disk[0-1] Drive 1
disk[0-2] Drive 2
system>
system> storage
-show disk[0-0] firmware
Total Firmware number: 1
Name: Drive
Description:
Manufacture:
Version: BE24
Release Date:
system>
system> storage
-show disk[0-0] info
Product Name: ST98394893
State: Online
Slot No.: 0
Disk Type: SATA
Media Type: HHD
Health Status: Normal
Capacity: 100.000GB
Speed: 6.0Gb/s
Current Temperature: 33C
Manufacture: ATA
Device ID: 5
Enclusure ID: 0x00FC
Machine Type:
Model:
Serial No.: 9XKJKL
FRU No.:
Part No.:
system>
system> storage
-show flashdimm[15]
Name: CPU1 DIMM 15
Health Status: Normal
Operational Status: Online
Capacity(GB): 400GB
Model Type: DDR3
Drives: 2
disk[0-1] Drive 1
disk[0-2] Drive 2
Volume: 1
vol[0-1] LD_volume
system>
system> storage
-show vol[0-0]
Name: Volume 0
Stripe Size: 64KB
Status: Offline
Capacity: 100.000GB
system>
system> storage
-show vol[0-0] info
Name: LD_volume
Status: Optimal
Stripe Size: 64KB
Bootable: Not Bootable
Capacity: 231.898GB
Read Policy: No Read Ahead
Write Policy: Write Through
I/O Policy: Direct I/O
Access Policy: Read Write
Disk Cache Policy: Unchanged
Background Initialization: Enable
system>
adapter command
This command is used to display PCIe adapter inventory information.
168 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
If the adapter command is not supported, the server responds with the following message when the
command is issued:
Your platform does not support this command.
If you remove, replace, or configure any adapters, you must restart the server (at least once) to view the
updated adapter information.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
-show target_id Show the detailed information for the target target_id [info|firmware|ports|chips]
PCIe adapter Where:
• info: display the hardware information for
the adapter
• firmware: display all firmware information
for the adapter
• ports: display all Ethernet port
information for the adapter
• chips: display all GPU chip information
for the adapter
Syntax:
adapter [options]
option:
-list
-show target_id [info|firmware|ports|chips]
-h help
Examples:
system> adapter
list
ob-1 Flex System CN4054 10Gbps Virtual Fabric Adapter
ob-2 GPU Card 1
slot-1 Raid Controller 1
slot-2 Adapter 01:02:03
system> adapter
show ob-1 info
Product Name: Flex System CN4054 10Gbps Virtual Fabric Adapter
Card Interface: PCIe x 16
Function Count: 2
m2raid command
Use this command to get M.2 related inventory information and manage the virtual volumes.
The following table is a multi-row two column table consisting of the options and option descriptions.
170 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Table 65. m2raid command (continued)
Option Description
Usage
m2raid [-options] - raid configuration for M.2 adapter with Mirroring Enablem
options:
-version - displays controller firmware version.
-disks - displays information of media disks.
-volumes - displays information of virtual volumes
-create -VD_Name <nameStr> -RaidLevel <0|1> -StripeSize <32|64> - create virt
-delete -VD_ID <0|1> - delete the virtual volume
-import -VD_ID <0|1> - import a foreign virtual volume
Example
system> m2raid -version
ThinkSystem M.2 with Mirroring Enablement Kit
Firmware Version = 2.3.10.1193
Support commands
This topic provides an alphabetic list of Support commands.
There is only one support command: the “dbgshimm command” on page 171.
dbgshimm command
Use this command to unlock network access to the secure debug shell.
Option Description
status Display status
172 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Chapter 11. IPMI interface
This chapter describes the IPMI interface supported by the XClarity Controller.
For details of the standard IPMI commands, refer to the Intelligent Platform Management Interface (IPMI)
Specification document (version 2.0 or above). This document provides descriptions on the OEM parameters
used with the standard IPMI and OEM IPMI commands supported by the XClarity Controller firmware.
The XClarity Controller comes with a user ID set initially to a user name of USERID and password of
PASSW0RD (with a zero, not the letter O). This user has Supervisor access.
Important: Change this user name and password during your initial configuration for enhanced security.
In a Flex System, a user can configure a Flex System CMM to centrally manage the XClarity Controller IPMI
user accounts. In this circumstance, you might not be able to access the XClarity Controller using the IPMI
until the CMM has configured the IPMI user IDs.
Note: The user ID credentials configured by the CMM might be different than the USERID/PASSW0RD
combination described above. If no IPMI user IDs have been configured by the CMM, the network port
associated with the IPMI protocol will be closed.
The XClarity Controller also provides the following IPMI remote server management capabilities:
Using IPMItool
Use the information in this topic to access information about the IPMItool.
The IPMItool provides various tools that you can use to manage and configure an IPMI system. You can use
the IPMItool in-band or out-of-band to manage and configure the XClarity Controller.
For more information about the IPMItool, or to download the IPMItool, go to https://github.com/ipmitool/
ipmitool.
DHCP
In addition to the usual methods of obtaining an IP address, the XCC provides a mode where it attempts
to obtain an IP address from a DHCP server for a given period of time and if unsuccessful fails over to
using a static IP address.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
The XCC uses the value 4h to indicate the address mode of DHCP
with failover to static.
The XCC hardware contains dual 10/100 Ethernet MACs with RMII interfaces. The XCC hardware also
contains dual 1Gbps Ethernet MACs with RGMII interfaces. One of the MACs is usually connected to the
shared server NIC and the other MAC is used as a dedicated system management port. Only one
Ethernet port on a server is active at a given time. Both ports will not be simultaneously enabled.
On some servers, the system designers may choose to connect up only one or the other of these
Ethernet interfaces on the system planar. In those systems, only the Ethernet interface that is connected
on the planar is supported by the XCC. A request to use the unconnected port returns a CCh completion
code.
The package IDS for all optional network cards are numbered as follows:
• optional card #1, package ID = 03h (eth2),
• optional card #2, package ID = 04h (eth3),
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
174 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Parameter # Parameter Data
OEM Parameter C0h data1
The data1 byte is used to specify the logical package. It may be a dedicated systems management NIC
or an NCSI interface into the NIC shared with the server.
The data2 byte is used to specify the channel for logical package, if the package is an NCSI device. If the
data2 is not specified in the request and the logical package is an NCSI device, channel, 0 is assumed. I
data2 is specified in the request but the logical package is not an NCSI device, the channel information
is ignored.
Examples:
Appendix A. If channel 2 of the shared NIC on the planar (package ID = 0, eth0) is to be used as the
management port , the input data would be: 0xC0 0x00 0x02
Appendix B: If the first channel of the first network mezzanine card is to be used, the input would be:
0xC0 0x02 0x0
The parameter below is used to enable or disable the XCC inband interface.
The following table is a multi-row three column table consisting of the options, option descriptions, and
associated values for the options.
The data1 byte is used to specify the logical package. It may be a dedicated systems management NIC
or an NCSI interface into the NIC shared with the server.
The data2 byte is used to specify the channel for logical package, if the package is an NCSI device. If the
data2 is not specified in the request and the logical package is an NCSI device, channel, 0 is assumed. I
data2 is specified in the request but the logical package is not an NCSI device, the channel information
is ignored.
Examples:
Appendix A. If channel 2 of the shared NIC on the planar (package ID = 0, eth0) is to be used as the
management port , the input data would be: 0xC0 0x00 0x02
Appendix B: If the first channel of the first network mezzanine card is to be used, the input would be:
0xC0 0x02 0x0
An additional read-only value that needs to be exposed via IPMI is the DUID. According to RFC3315,
this format of DUID is based on the Link Layer Address Plus Time.
176 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Parameter # Parameter Data
OEM Parameter C2h
178 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Parameter # Parameter Data
OEM Parameter C8h
The parameter below is used to configure the Ethernet-over-USB to external Ethernet pass-through.
The Get response data will return the Ethernet over USB Port number, LSByte first
following:
data 4:5
Byte 1 = completion code
Byte 2 = revision External Ethernet Port number, LSByte first
Byte 3 = reserved (00h)
The number of bytes to follow can vary (1, 4, or
Bytes 4:5 = Ethernet-over-USB Port 16 bytes) depending upon the addressing mode:
number (LSByte first)
Bytes 6:7 = External Ethernet Port data 6
number (LSByte first)
00h = disable the pass-through
The number of bytes to follow can vary
(1, 4, or 16 bytes) depending upon the 01h = use the CMM’s IP address
addressing mode:
data 6:9
• Byte 8 = pre-defined modes:
00h = the pass-through is IPv4 external network IP address in binary form
disabled
data 6:21
01h = the CMM’s IP address is
used IPv6 external network IP address in binary form
Bytes 8:11 = IPv4 external network
IP address in binary form
Bytes 8:23 = IPv6 external network
IP address in binary form
Completion codes:
00h – success
This parameter is used to set and get IP address of XCC -side lan over usb interface.
the lan over usb ip address and netmask
of the XCC: Data 5:8
The response data will return the Netmask of XCC -side lan over usb interface
following:
Byte 1 = completion code
Byte 2 = Parameter Revision (as in
IPMI spec)
180 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Parameter # Parameter Data
This parameter is used to set and get IP address of Host-side lan over usb interface.
the lan over usb ip address of the Host
OS:
Response
The parameter below is used to read and to set the priority assigned to each package.
182 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Parameter # Parameter Data
OEM Parameter D4 Get/Set LAN Configuration Parameters:
This parameter in the Get/Set LAN Bit [7-4] = priority of the logical package (1 = highest,
Configuration Parameters 15 = lowest)
command does not use a Set
Selector or a require Block Bit [3-0] = logical package number
Selector, so these fields should be
set to 00h.
Response
Response:
The byte is used to config to synchronize networking setting between dedicated and shared nic mode ,
the default value was 0h here, it mean XCC will automatically update networking setting between mode
change and use shared nic (on board) as major reference , if set as 1h , each networking setting will be
independent here , which is we can configure different networking setting between mode, such as VLAN
enable on Dedicated and set VLAN disable on Shared NIC mode.
184 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Parameter # Parameter Data
OEM Parameter D6h Set LAN Configuration Parameters:
Netfn 0x2E
Code Commands Privilege
Netfn 0x3A
Code Commands Privilege
This command resets the XCC configuration setting to the default values.
Byte 3 – 0x00
Byte 6 – 0xFF
Byte 9 – 0x00
Response:
Byte 4 – 0x00
This section lists the commands for querying the board and firmware information.
186 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Net Function = 0x3A
0x0D Query Board Request: N/A This command returns the Board
Information ID and planar revision.
Response:
Byte 1 – System ID
0x50 Query Build Request: N/A This command returns the build
Information name, build date, and build time.
Response: The build name and build date
strings have a zero termination.
Byte 1 – Completion Code.
The format of the build date is
Bytes 2:10 – ASCIIZ Build Name YYYY-MM-DD.
Response:
Byte 2 – bin#
Byte 3 – APID
Byte 4 – Rev
188 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Net Function = 0x3A
The IPMI specification provides basic power and reset control. Lenovo adds additional control functions.
0x02 - 0xFF
Reserved
Response:
This section is for commands that do not fit into any other section.
190 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Net Function = 0x3A
ASCIIZ, Null
terminated
string.
ASCIIZ
Terminate with
00h
00h: Disabled
01h: Enabled
Response:
192 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Net Function = 0x3A
Response:
Byte 1
05h: Enable/
Disable the
front panel
USB port
Byte 2
00h: Disable
01h: Enable
Response:
Request:
Byte 1
Response:
Byte 2
Byte 1 Completion
Code
Bytes 2 Current
Enable/
Disable Status
Request Length= 1:
Byte 1 Native NM
IPMI Interface
Enable/
Disable
attribute
00h – Disable
01h – Enable
Response:
Byte 1 Completion
Code
194 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Chapter 12. Edge servers
This topic describes specific functions for Edge servers.
Notes:
1. The system requires you to change the XCC password on you first login.
2. The IPMI-over-LAN is disabled by default.
3. The IPMI-over-KCS is disabled by default.
Note: System Lockdown Mode is only available for SE350 with Security Pack but not SE350 standard.
Version can be checked at Home tab under System Information and Settings.
Click Security under BMC Configuration and scroll to System Lockdown Mode.
Note: When System Lockdown Mode is in active state, any access to system secrets is denied, such
as SED Authentication Keys.
To force the system to enter System Lockdown Mode, complete the following steps.
1. Click Active button.
2. Click OK button and then Click Apply.
Motion Detection
You can enable this function to protect your server by detecting any physical movement of your server.
If Motion Detection is enabled, you can set the following items depending on your preference and
configuration.
• Sensitivity Level: Select the sensitivity level from Low, Medium and High according to your
preference
• Orientation: Select your configuration from Stand Desktop, Wall Mount (Horizontal), Wall Mount
(Vertical), Bookshelf and Ceiling Mount.
Note: Motion Detection would be disabled automatically when the system entering the lockdown mode.
Chassis Intrusion Detection
You can enable this function to protect your server by detecting any physical movement of the top
cover.
Note: This operation is not allowed when the system is not activated (System Lockdown Mode is asserted)
or current user does not have the authority to manage SED Authentication Key.
Note: System Lockdown Mode is only available for SE350 with Security Pack but not SE350 standard.
Version can be checked at Home tab under System Information and Settings.
Note: The SE350 also supports an auto backup feature as long as the either ThinkSystem M.2 Enablement
Kit or ThinkSystem M.2 Mirroring Enablement Kit is healthy. If hardware is damaged, but both SED and M.2
Kit are healthy, they can be installed into another SE350 and the SED AK can then be restored. However, in
order to be prepared for a full hardware crash, Lenovo recommends making a SED AK backup.
Click Security under BMC Configuration and scroll to SED Authentication Key (AK) Manager.
Note: If you use the backup SED AK file to restore a configuration, the system will ask for the password
that you set here.
Recover the SED AK: You can only perform this task while the SED is not functioning properly. There
are two ways to recover the SED AK:
• Recover SED AK using Passphrase: Use the password that set in Generate SED AK from
Passphrase mode to recover the SED AK.
• Recover SED AK from Backup file: Upload the backup file generated in Backup the SED AK mode
and enter the corresponding backup file password to recover the SED AK.
Edge Networking
This function page only supported while the Wireless enabled LOM Package is installed.
Wi-Fi Connectivity
Click Enabled and you can configure settings according to your Wi-Fi configuration.
LTE Connectivity
This allows you to control LTE connectivity for the Edgenetwork board.
196 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Edge Network Board Address
On the World Wide Web, up-to-date information about Lenovo systems, optional devices, services, and
support are available at:
http://datacentersupport.lenovo.com
Note: This section includes references to IBM web sites and information about obtaining service. IBM is
Lenovo's preferred service provider for ThinkSystem.
You can find the product documentation for your ThinkSystem products at the following location:
http://thinksystem.lenovofiles.com/help/index.jsp
You can take these steps to try to solve the problem yourself:
• Check all cables to make sure that they are connected.
• Check the power switches to make sure that the system and any optional devices are turned on.
• Check for updated software, firmware, and operating-system device drivers for your Lenovo product. The
Lenovo Warranty terms and conditions state that you, the owner of the Lenovo product, are responsible
for maintaining and updating all software and firmware for the product (unless it is covered by an
additional maintenance contract). Your service technician will request that you upgrade your software and
firmware if the problem has a documented solution within a software upgrade.
• If you have installed new hardware or software in your environment, check http://www.lenovo.com/
serverproven/ to make sure that the hardware and software is supported by your product.
• Go to http://datacentersupport.lenovo.com and check for information to help you solve the problem.
– Check the Lenovo forums at https://forums.lenovo.com/t5/Datacenter-Systems/ct-p/sv_eg to see if
someone else has encountered a similar problem.
You can solve many problems without outside assistance by following the troubleshooting procedures that
Lenovo provides in the online help or in the Lenovo product documentation. The Lenovo product
documentation also describes the diagnostic tests that you can perform. The documentation for most
systems, operating systems, and programs contains troubleshooting procedures and explanations of error
Gather the following information to provide to the service technician. This data will help the service
technician quickly provide a solution to your problem and ensure that you receive the level of service for
which you might have contracted.
• Hardware and Software Maintenance agreement contract numbers, if applicable
• Machine type number (Lenovo 4-digit machine identifier)
• Model number
• Serial number
• Current system UEFI and firmware levels
• Other pertinent information such as error messages and logs
200 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Use the Collect Service Data function of Lenovo XClarity Provisioning Manager to collect system service
data. You can collect existing system log data or run a new diagnostic to collect new data.
• Lenovo XClarity Essentials
Lenovo XClarity Essentials can be run in-band from the operating system. In addition to the hardware
service data, Lenovo XClarity Essentials can collect information about the operating system, such as the
operating system event log.
To obtain service data, you can run the getinfor command. For more information about running the
getinfor, see http://sysmgt.lenovofiles.com/help/topic/toolsctr_cli_lenovo/onecli_r_getinfor_command.html.
Contacting Support
You can contact Support to obtain help for your issue.
You can receive hardware service through a Lenovo Authorized Service Provider. To locate a service
provider authorized by Lenovo to provide warranty service, go to https://datacentersupport.lenovo.com/us/en/
serviceprovider and use filter searching for different countries. For Lenovo support telephone numbers, see
https://datacentersupport.lenovo.com/us/en/supportphonelist for your region support details.
Any reference to a Lenovo product, program, or service is not intended to state or imply that only that
Lenovo product, program, or service may be used. Any functionally equivalent product, program, or service
that does not infringe any Lenovo intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any other product, program, or service.
Lenovo may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document is not an offer and does not provide a license under any patents
or patent applications. You can send inquiries in writing to the following:
Lenovo (United States), Inc.
1009 Think Place
Morrisville, NC 27560
U.S.A.
Attention: Lenovo VP of Intellectual Property
LENOVO PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow
disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to
you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. Lenovo may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.
The products described in this document are not intended for use in implantation or other life support
applications where malfunction may result in injury or death to persons. The information contained in this
document does not affect or change Lenovo product specifications or warranties. Nothing in this document
shall operate as an express or implied license or indemnity under the intellectual property rights of Lenovo or
third parties. All information contained in this document was obtained in specific environments and is
presented as an illustration. The result obtained in other operating environments may vary.
Lenovo may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Any references in this publication to non-Lenovo Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this Lenovo product, and use of those Web sites is at your own risk.
Any performance data contained herein was determined in a controlled environment. Therefore, the result
obtained in other operating environments may vary significantly. Some measurements may have been made
on development-level systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.
Intel and Intel Xeon are trademarks of Intel Corporation in the United States, other countries, or both.
Internet Explorer, Microsoft, and Windows are trademarks of the Microsoft group of companies.
Other company, product, or service names may be trademarks or service marks of others.
Important notes
Processor speed indicates the internal clock speed of the microprocessor; other factors also affect
application performance.
CD or DVD drive speed is the variable read rate. Actual speeds vary and are often less than the possible
maximum.
When referring to processor storage, real and virtual storage, or channel volume, KB stands for 1 024 bytes,
MB stands for 1 048 576 bytes, and GB stands for 1 073 741 824 bytes.
When referring to hard disk drive capacity or communications volume, MB stands for 1 000 000 bytes, and
GB stands for 1 000 000 000 bytes. Total user-accessible capacity can vary depending on operating
environments.
Maximum internal hard disk drive capacities assume the replacement of any standard hard disk drives and
population of all hard-disk-drive bays with the largest currently supported drives that are available from
Lenovo.
Maximum memory might require replacement of the standard memory with an optional memory module.
Each solid-state memory cell has an intrinsic, finite number of write cycles that the cell can incur. Therefore, a
solid-state device has a maximum number of write cycles that it can be subjected to, expressed as total
bytes written (TBW). A device that has exceeded this limit might fail to respond to system-generated
commands or might be incapable of being written to. Lenovo is not responsible for replacement of a device
that has exceeded its maximum guaranteed number of program/erase cycles, as documented in the Official
Published Specifications for the device.
Lenovo makes no representations or warranties with respect to non-Lenovo products. Support (if any) for the
non-Lenovo products is provided by the third party, not Lenovo.
Some software might differ from its retail version (if available) and might not include user manuals or all
program functionality.
Particulate contamination
Attention: Airborne particulates (including metal flakes or particles) and reactive gases acting alone or in
combination with other environmental factors such as humidity or temperature might pose a risk to the
device that is described in this document.
204 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Risks that are posed by the presence of excessive particulate levels or concentrations of harmful gases
include damage that might cause the device to malfunction or cease functioning altogether. This
specification sets forth limits for particulates and gases that are intended to avoid such damage. The limits
must not be viewed or used as definitive limits, because numerous other factors, such as temperature or
moisture content of the air, can influence the impact of particulates or environmental corrosives and gaseous
contaminant transfer. In the absence of specific limits that are set forth in this document, you must
implement practices that maintain particulate and gas levels that are consistent with the protection of human
health and safety. If Lenovo determines that the levels of particulates or gases in your environment have
caused damage to the device, Lenovo may condition provision of repair or replacement of devices or parts
on implementation of appropriate remedial measures to mitigate such environmental contamination.
Implementation of such remedial measures is a customer responsibility.
Contaminant Limits
Particulate
• The room air must be continuously filtered with 40% atmospheric dust spot efficiency (MERV
9) according to ASHRAE Standard 52.21.
• Air that enters a data center must be filtered to 99.97% efficiency or greater, using high-
efficiency particulate air (HEPA) filters that meet MIL-STD-282.
• The deliquescent relative humidity of the particulate contamination must be more than 60%2.
• The room must be free of conductive contamination such as zinc whiskers.
Gaseous
• Copper: Class G1 as per ANSI/ISA 71.04-19853
• Silver: Corrosion rate of less than 300 Å in 30 days
1ASHRAE 52.2-2008 - Method of Testing General Ventilation Air-Cleaning Devices for Removal Efficiency by
Particle Size. Atlanta: American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc.
2The deliquescent relative humidity of particulate contamination is the relative humidity at which the dust absorbs
enough water to become wet and promote ionic conduction.
3ANSI/ISA-71.04-1985. Environmental conditions for process measurement and control systems: Airborne
contaminants. Instrument Society of America, Research Triangle Park, North Carolina, U.S.A.
http://thinksystem.lenovofiles.com/help/index.jsp
206 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Appendix B. Notices 207
208 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
Index
A certificate signing request
BMC 40
absolute mouse control 64 CIM over HTTP port
accseccfg command 107 set 128
activation key CIM over HTTPS
export 86 certificate management 139–140
install 85, 122 security 139–140
manage 122 CIM over HTTPS port
remove 86, 122 set 128
Active Directory Users clearcfg command 157
LDAP 149 clearlog command 94
active system events CLI key sequence
overview 47 set 126
adapter command 168 client
adapter information certificate management 40
Server Configuration 55 client certificate management
advanced Ethernet CA-signed 40
settings 29, 174 self-assigned 40
advanced management module 1 client distinguished name
Agent-less commands 159 LDAP server 123
alertcfg command 108 clock command 157
alertentries command 154 collecting service data 75, 200
alphabetical command list 91 command-line interface (CLI)
asu command 109 accessing 89
audit log 51 command syntax 90
autonegotiation description 89
set 119 features and limitations 90
logging in 89
commands
accseccfg 107
B adapter 168
backup command 112 alertcfg 108
baseboard management controller (BMC) 1 alertentries 154
batch command 156 asu 109
binding method backup 112
LDAP server 123 batch 156
BIOS (basic input/output system) 1 clearcfg 157
block list and time restriction clearlog 94
settings 34 clock 157
blue screen capture 63 console 107
BMC dbgshimm 171
certificate signing request 40 dhcpinfo 113
BMC management dns 114
BMC configuration encaps 116
back up BMC configuration 45 ethtousb 116
backup and restore BMC configuration 45 exit 93
restore BMC configuration 46 fans 95
restore to factory default 46 ffdc 95
browser requirements 6 firewall 117
fuelg 105
gprofile 118
hashpw 118
C help 93
history 93
CA-signed hreport 96
certificate 40 identify 158
centralized management ifconfig 119
encryption keys 39 info 158
certificate classifications keycfg 122
CA-signed 40 ldap 123
self-assigned 40 led 97
certificate management m2raid 170
CIM over HTTPS 139–140 mhlog 97
client 40 ntp 125
Drive Access 143 portcfg 126
HTTPS server 139–140 portcontrol 127
LDAP 139–140 ports 128
server 43 power 102
SSH server 138 pxeboot 106
210 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
device group 40 H
key management servers 40
SKLM certificate management 40 hardware health 47
Drive Access tab hardware service and support telephone numbers 201
security option 39–40 hash password 20
hashpw command 118
help 199
help command 93
E history command 93
host name
email and syslog notifications 52 LDAP server 123
encaps command 116 set 119
encryption keys SMTP server 133
centralized management 39 hreport command 96
enhanced role-based security HTTP port
LDAP 149 set 128
enterprise level features 5 HTTPS port
Ethernet set 128
configure 119 HTTPS server
Ethernet over USB certificate management 139–140
configure 116 security 139–140
port forwarding 116
ethtousb command 116
event log 51
event window I
log 51
exit command 93 identify command 158
exiting the remote console session 75 ifconfig command 119
export IMM
activation key 86 configuration restore 130
Extended Audit Log default configuration 130
extended audit log 43 reset 159
reset configuration 130
restore configuration 130
spreset 159
F IMM control commands 154
important notices 204
fans command 95 info command 158
features of XClarity Controller 2 install
Features on Demand activation key 85, 122
install feature 122 install feature
manage 122 Features on Demand 122
remove feature 122 FoD 122
ffdc command 95 IP address
firewall command 117 configuring 9
firmware IPv4 9
view server 102 IPv6 9
firmware, server LDAP server 123
updating 83 SMTP server 133
Flex servers 1 IP address, default static 10
Flex System 1 IPMI
FoD configure 33
install feature 122 remote server management 173
manage 122 ipmi bridging
remove feature 122 power management 59
fuelg command 105 through XClarity Controller 59
functions and commands ipmi commands
dcmi 60 power consumption 59
node manager 59 IPMI interface
description 173
IPMI over KCS Access
configure 38
G IPMItool 173
gaseous contamination 204 IPv4
Getting help 199 configure 119
global login IPv4 addressing
settings 22 DNS 114
global login settings IPv6 9
account security policy settings 23 configure 119
gprofile command 118 IPv6 addressing
group filter DNS 114
LDAP 123
group search attribute
LDAP 123
M O
OEM IPMI Commands 185
m2raid command 170 one-time
MAC address setting up 56
manage 119 OneCLI 1
maintenance history 52 online publications
manage documentation update information 1
activation key 122 error code information 1
DDNS 114 firmware update information 1
Features on Demand 122 operating-system requirements 6
FoD 122 operating-system screen capture 63
MAC address 119 option
SNMPv1 communities 133 SKM 39
user 149 OS failure screen data
management capture 54
server certificate 43 overview 47
SKLM certificate 40 ssl 36
managing power
using IPMI commands 59
maximum transmission unit
set 119 P
media mount error issues 73
media mount methods 65 particulate contamination 204
mhlog command 97 password
MIBs Introduction 7 LDAP server 123
minimum, levels user 149
TLS 147 port assignments
212 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
configure 33 operating system 6
settings 33 web browser 6
port forwarding reset
Ethernet over USB 116 IMM 159
port number reset command 104
LDAP server 123 reset configuration
SMTP server 133 IMM 130
port numbers restart XClarity Controller 46
set 128 restore command 130
portcfg command 126 restore configuration
portcontrol command 127 IMM 130
ports restoredefaults command 130
configure 128 role-based levels
set numbers 128 operator 118
view open 128 rbs 118
ports command 128 supervisor 118
power role-based security, enhanced
managing using IPMI commands 59 LDAP 149
monitoring using IPMI commands 59 roles command 131
power command 102 root distinguished name
power consumption LDAP server 123
ipmi commands 59
power management
dcmi 60
ipmi bridging 59 S
power management option
screen video record/replay
power actions 58
server management 64
power capping policy 57
search domain
power redundancy 57
LDAP server 123
power restore policy 58
seccfg command 132
Server Management tab 56
security
pre-configured
CIM over HTTPS 139–140
LDAP server 123
Drive Access 143
prevent system firmware down-level
HTTPS server 139–140
configure 39
LDAP 139–140
pxeboot command 106
SSH server 38, 138
ssl certificate handling 37
SSL certificate management 37
R ssl overview 36
security option
RAID detail Drive Access tab 39–40
Server Configuration 79 Security option
RAID setup Drive Access tab 40
Server Configuration 79 self-assigned
rdmount command 129 certificate 40
readlog command 99 Serial over LAN 173
relative mouse control 64 serial port
relative mouse control for Linux (default Linux acceleration) 64 configure 126
remote access 2 serial redirect command 107
remote console serial-to-SSH redirection 89
absolute mouse control 64 server
keyboard support 63 certificate management 43
mouse support 63 configuration options 55
power and restart commands 62 server addressing
relative mouse control 64 DNS 114
relative mouse control for Linux (default Linux server certificate
acceleration) 64 management 43
screen capture 63 server configuration
video viewer 61 server properties 75
virtual media session 61 Server Configuration
remote console feature 61 adapter information 55
remote console functionality 61 RAID detail 79
enabling 62 RAID setup 79
remote console mouse support 63 server firmware
remote console port updating 83
set 128 server management
remote console screen modes 64 one-time 56
remote power control 62 OS failure screen data 54
remove screen video record/replay 64
activation key 86, 122 server firmware 83
remove feature server timeouts, setting 76
Features on Demand 122 system boot mode 55
FoD 122 system boot order 55
requirements Server Management tab
214 XClarity Controller with Intel Xeon SP (1st, 2nd Gen)User's Guide
set 157 view current
timeouts command 146 users 149
TLS view firmware information
minimum level 147 server 102
TLS command 147 view open ports 128
tools volts command 101
IPMItool 173 vpd command 102
trademarks 204
trespass command 147
trespass message option 76
W
Web browser requirements 6
U web inactivity session timeout 22
web inactivity timeout
uefipw command 148 set 107
UID search attribute web interface
LDAP server 123 logging in to web interface 12
USB web interface, opening and using 9
configure 116 working with
usbeth command 149 events in the audit log 51
usbfp command 149 events in the event log 51
user
delete 149
manage 149
password 149 X
SNMPv3 settings 149
XClarity Controller
SSH keys 149
configuration options 17
user account
configure network protocol 29
create 149
description 1
deleting 20
features 2
user account security levels
ipmi bridging 59
configure 107
network connection 10
user authentication method 17
new functions 1
set 107
serial redirection 89
users
web interface 9
view current 149
XClarity Controller advanced level 2
users command 149
XClarity Controller enterprise level 2
using
XClarity Controller standard level 2
remote console feature 61
XClarity Controller features
remote console function 61
enterprise level 5
utility commands 93
standard level 2
XClarity Controller features advanced level features
advanced level 5
V XClarity Controller functions
on web interface 13
Video Viewer XClarity Controller management
absolute mouse control 64 configuring LDAP 17
mouse support 63 configuring user accounts 17
power and restart commands 62 creating a new local user 17
relative mouse control 64 deleting a user account 20
relative mouse control for Linux (default Linux security settings 36
acceleration) 64 XClarity Controller properties
screen capture 63 date and time 77
video color mode 63 XClarity Provisioning Manager
view and configure the virtual drives 79 Setup utility 10
Printed in China
*1PSP47A30085*