The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
To activate CIMC firmware, use the activate command.
activate
This command has no arguments or keywords.
None
Firmware (/cimc/firmware)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to activate CIMC firmware:
server# scope cimc server /cimc # scope firmware server /cimc/firmware # activate server /cimc/firmware #
Command |
Description |
show cimc |
|
show version |
|
To stop the technical support process, use the cancel command.
cancel
This command has no arguments or keywords.
None
Technical support (/cimc/tech-support)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to stop the technical support process:
server # scope cimc server /cimc # scope tech-support server /cimc/tech-support # cancel This operation will cancel your current Tech Support upload. Continue?[y|N]y server /cimc/tech-support #
Command |
Description |
start |
|
To clear the CIMC log, use the clear command in log mode.
clear
This command has no arguments or keywords.
None
Log (/cimc/log)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to clear the CIMC log:
server# scope cimc server /cimc # scope log server /cimc/log # clear server /cimc/log #
Command |
Description |
show sel |
|
show sensor |
|
To clear the system event log, use the clear command in sel mode.
clear
This command has no arguments or keywords.
None
System event log (/sel)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to clear the system event log:
server# scope sel server /sel # clear server /sel #
Command |
Description |
show sel |
|
show sensor |
|
To clear the BIOS settings in CMOS memory, use the clear-cmos command.
clear-cmos
This command has no arguments or keywords.
None
BIOS (/bios)
Release | Modification |
---|---|
1.1(1) | This command was introduced. |
This example shows how to clear the BIOS settings in CMOS memory:
server# scope bios server /bios # clear-cmos This operation will clear the BIOS CMOS. Note: Server should be in powered off state to clear CMOS. Continue?[y|n] y server /bios #
Command |
Description |
show bios |
|
To save configuration changes, use the commit command.
commit
This command has no arguments or keywords.
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to save a configuration change:
server /http # set enabled yes server /http* # commit server http #
Command |
Description |
discard |
|
To connect to either the server CLI or the server shell, use the connectcommand.
connect { host | | shell }
host | Specifies the CLI on the server. |
shell | Specifies the GNU bash shell on the server. |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use the exitcommand to exit the GNU bash shell.
This example shows how to connect to the server shell:
server# connect shell bash-3.2
To discard all configurations, use the discard command.
discard
This command has no arguments or keywords.
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to discard all configurations:
server# discard server#
Command |
Description |
discard |
|
To leave any mode, use the exit command.
exit
This command has no arguments or keywords.
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to exit bios mode:
server /bios # exit server#
Command |
Description |
scope |
|
enter |
|
To export a CIMC configuration, use the import-config command.
import-config tftp-ip-address path-and-filename
tftp-ip-address | The IP address of a remote TFTP server hosting the CIMC configuration file. |
path-and-filename | Specifies the absolute path to the file on the remote server. |
None
Import-export (/cimc/import-export)
Release | Modification |
---|---|
1.1(2) | This command was introduced. |
Use this command to export the CIMC configuration as a file. The path-and-filename is a unique set of up to 128 characters that identifies the path and CIMC configuration file name on the remote server. Do not use characters that are not allowed in a URL.
To determine whether the export operation has completed successfully, use the show detail command. To abort the operation, type CTRL+C.
Note |
For security reasons, this operation does not export user accounts or the server certificate. |
This example shows how to export a CIMC configuration to a remote TFTP server:
server# scope cimc server /cimc # scope import-export server /cimc/import-export # export-config 192.0.2.34 /ucs/backups/cimc5.xml Export config started. Please check the status using "show detail". server /cimc/import-export # show detail Export Export: Operation: EXPORT Status: COMPLETED Error Code: 100 (No Error) Diagnostic Message: NONE server /cimc/import-export #
Command |
Description |
import-config |
|
To set the server to factory default, use the factory-default command.
factory-default
This command has no arguments or keywords.
None
Cisco Integrated Manangement Controller (/cimc)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to set the server to factory default:
server# scope cimc server /cimc # factory-default This operation will reset the CIMC configuration to factory default. All your configuration will be lost. Continue?[y|N] y
To generate a Certificate Request Signing (CSR), use the generate-csr command.
generate csr
This command has no arguments or keywords.
None
Certificate (/certificate)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to generate a CSR :
server# scope certificate server /certificate # generate-csr Common Name (CN): abcCertificate Organization Name (O): abcCo Organization Unit (OU): 01 Locality (L): west StateName (S): CA Country Code (CC): US Email: abcCo@abcCo.com Continue to generate CSR?[y|N] y -----BEGIN CERTIFICATE REQUEST----- MIIB0TCCAToCAQAwbDELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMQ0wCwYDVQQH EwRoZXJlMQwwCgYDVQQKEwN0aW0xCzAJBgNVBAsTAjAxMQwwCgYDVQQDEwNib2Ix GDAWBgkqhkiG9w0BCQEWCW1lQG1lLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAw gYkCgYEAw49pYuDXdOfHtXwBT7k5kX1set/I3e8TtkuO/EQ5HVd9HrPIy4Kpb3Oj 33CkqjysVWBpPSGzWAlEL6cZYs5p6JxR74+tqW5BYpNKRLNFawpsTZvCXhe/n/O2 WYsx1FnW1m6BgQnPKCBCp9R1ESmq9Np24r2c3PEStZEjeIVWbaUCAwEAAaAlMCMG CSqGSIb3DQEJBzEWExRBIGNoYWxsZW5nZSBwYXNzd29yZDANBgkqhkiG9w0BAQUF AAOBgQBosXif9feLXHBK19kqeVZ8uqRgoMIcM03aBTImjIO1RgwhRLuMrG2l+thA CT+fbYOYXJ4bHsn25XQjcSdG0uxsti3C2SnK83nKdulpEzBzj545rvH20QK+RtHN YUBEKvABCeqoIUu+ErMtGvryaQw7WQiQjWf+RTf8IXDGShIQwQ== -----END CERTIFICATE REQUEST----- server /certificate #
Command |
Description |
show certificate |
|
show ssh |
|
To import a CIMC configuration, use the import-config command.
import-config tftp-ip-address path-and-filename
tftp-ip-address | The IP address of a remote TFTP server hosting the CIMC configuration file. |
path-and-filename | Specifies the absolute path to the file on the remote server. |
None
Import-export (/cimc/import-export)
Release | Modification |
---|---|
1.1(2) | This command was introduced. |
Use this command to import a CIMC configuration file. The path-and-filename is a unique set of up to 128 characters that identifies the path and CIMC configuration file name on the remote server. Do not use characters that are not allowed in a URL.
To determine whether the import operation has completed successfully, use the show detail command. To abort the operation, type CTRL+C.
Note |
Some modifications caused by an import operation, such as IP address changes, can disrupt traffic or cause a server reboot. |
This example shows how to import a CIMC configuration from a remote TFTP server:
server# scope cimc server /cimc # scope import-export server /cimc/import-export # import-config 192.0.2.34 /ucs/backups/cimc5.xml Import config started. Please check the status using "show detail". server /cimc/import-export #
Command |
Description |
export-config |
|
To ping, use the ping command in network mode.
ping address
address | The IP address or the hostname. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to ping:
server# scope cimc server /cimc # scope network server /cimc/network # ping 209.165.200.225 Press CTRL+C to stop. PING 209.165.200.225 (209.165.200.225): 56 data bytes 64 bytes from 209.165.200.225: seq=0 ttl=122 time=2.000 ms 64 bytes from 209.165.200.225: seq=1 ttl=122 time=2.000 ms 64 bytes from 209.165.200.225: seq=2 ttl=122 time=2.000 ms 64 bytes from 209.165.200.225: seq=3 ttl=122 time=3.000 ms 64 bytes from 209.165.200.225: seq=4 ttl=122 time=2.000 ms --- 209.165.200.225 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 2.000/2.200/3.000 ms server /cimc/network #
To manage server power, use the power command.
power { cycle | hard-reset | off | on | shutdown}
cycle | Power cycles the server. |
hard-reset | Hard resets the server. |
off | Powers off the server. |
on | Powers on the server. |
shutdown | Shuts down the server. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to power off the server :
server# scope chassis server /chassis # power off This operation will change the server's power state. Continue?[y|n] y server /chassis #
Command |
Description |
show chassis |
|
show psu |
|
To reapply the boot order, use the reapplycommand in bios mode.
This command has no arguments or keywords.
None
BIOS (/bios)
Release | Modification |
---|---|
1.0(1x) | This command was introduced. |
This example shows how to reapply the boot order:
server# scope bios server /bios # re-apply Boot order has been successfully re-applied server /bios #
Command |
Description |
set boot-order (bios) |
|
show actual-boot-order |
|
To reboot the server, use the reboot command.
reboot
This command has no arguments or keywords.
None
Cisco Integrated Management Controller (/cimc)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.0(1X) | This command was deprecated. |
This example shows how to reboot the server:
server# scope cimc server /cimc # reboot This operation will reboot the BMC. Continue?[y|n] y
Command |
Description |
power |
|
To recover corrupted BIOS, use the recover command in firmware mode.
recover
This command has no arguments or keywords.
None
BIOS (/bios)
Release | Modification |
---|---|
1.0(1X) | This command was introduced. |
Before executing the recover command, perform the following tasks:
Ensure that the BIOS recovery ISO image is available for your use
Launch the KVM Console
Power off server
Map the BIOS recovery ISO image using vMedia
Executing the recover command automatically powers the server on. After the recovery is finished, power cycle or reset the server.
This example shows how to recover corrupted BIOS:
server# scope bios server /bios # recover This operation will automatically power on the server to perform BIOS FW recovery. Continue?[y|N]y server /bios #
Note |
You can use the CLI or the KVM console to monitor the progress of the recovery. |
Command |
Description |
show bios |
|
show version |
|
To enter bios mode, use the scope bios command.
scope bios
This command has no arguments or keywords.
None
BIOS (/bios)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use bios mode to set the server boot order:
This example shows how to enter BIOS mode:
server# scope bios server /bios #
Command |
Description |
show bios |
|
show firmware |
|
To enter certificate mode, use the scope certificate command.
scope certificate
This command has no arguments or keywords.
None
Certificate (/certificate)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use certificate mode to perform the following tasks:
This example shows how to enter certificate mode:
server# scope certificate server /certificate #
Command |
Description |
generate-csr |
|
show certificate |
|
To enter chassis mode, use the scope chassis command.
scope chassis
This command has no arguments or keywords.
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use chassis mode to set the following chassis properties:
This example shows how to enter chassis mode:
server# scope chassis server /chassis #
Command |
Description |
show chassis |
|
show led |
|
To enter cimc mode, use the scope cimc command.
scope cimc
This command has no arguments or keywords.
None
Cisco Integrated Management Controller (/cimc)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use cimc mode to perform the following actions:
This example shows how to enter cimc mode :
server# scope cimc server /cimc #
Command |
Description |
show cimc |
|
show log (cimc) |
|
To enter fault mode, use the scope fault command.
scope fault
This command has no arguments or keywords.
None
Fault (/fault)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use fault mode to set the following SNMP properties:
This example shows how to enter fault mode :
server# scope fault server /fault #
Command |
Description |
show fault |
|
show pef |
|
To enter firmware mode, use the scope firmware command in bios mode.
scope firmware
This command has no arguments or keywords.
None
Firmware (/bios/firmware)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use firmware mode to perform the following tasks:
This example shows how to enter BIOS mode:
server# scope bios server /bios # scope firmwware server /bios/firmware #
Command |
Description |
show bios |
|
show firmware |
|
To enter http mode, use the scope http command.
scope http
This command has no arguments or keywords.
None
HTTP (/http)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use http mode to set the following HTTP properties:
This example shows how to enter http mode :
server# scope http server /http #
Command |
Description |
show http |
|
show http-port |
|
To enter CIMC import-export mode, use the scope import-export command in CIMC mode.
scope import-export
This command has no arguments or keywords.
None
CIMC (/cimc)
Release | Modification |
---|---|
1.1(2) | This command was introduced. |
You can use import-export mode to import or export a CIMC configuration file.
This example shows how to enter import-export mode:
server# scope cimc server /cimc # scope import-export server /cimc/import-export #
Command |
Description |
export-config |
|
import-config |
|
To enter ipblocking mode, use the scope ipblocking command in network mode.
scope ipblocking
This command has no arguments or keywords.
None
IP blocking (/cimc/network/ipblocking)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use ipblocking mode to perform the following tasks:
This example shows how to enter ipblocking mode :
server# scope cimc server /cimc # scope network server /cimc/network # scope ipblocking server /cimc/network/ipblocking #
Command |
Description |
show ipblocking |
|
set penalty-time |
|
To enter ipmi mode, use the scope ipmi command.
scope ipmi
This command has no arguments or keywords.
None
Intelligent Platform Management Interface (/ipmi)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use ipmi mode to perform the following tasks:
This example shows how to enter ipmi mode :
server# scope ipmi server /ipmi #
Command |
Description |
show ipmi |
|
set encryption-key |
|
To enter kvm mode, use the scope kvm command.
scope kvm
This command has no arguments or keywords.
None
Keyboard, video and mouse (/kvm)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use kvm mode to set the following KVM properties:
This example shows how to enter kvm mode :
server# scope kvm server /kvm #
Command |
Description |
set max-sessions |
|
show kvm |
|
To enter ldap mode, use the scope ldap command.
scope ldap
This command has no arguments or keywords.
None
Lightweight Directory Access Protocol (/ldap)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use ldap mode to perform the following LDAP properties:
This example shows how to enter ldap mode :
server# scope ldap server /ldap #
Command |
Description |
set server-ip |
|
show ldap |
|
To enter log mode, use the scope log command in cimc mode.
scope log
This command has no arguments or keywords.
None
Log (/cimc/log)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use log mode to perform the following tasks:
This example shows how to enter log mode :
server# scope cimc server /cimc # scope log server /cimc/log #
Command |
Description |
show entries |
|
show log |
|
To enter network mode, use the scope network command in cimc mode.
scope network
This command has no arguments or keywords.
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use network mode to perform the following tasks:
This example shows how to enter network mode :
server# scope cimc server /cimc # scope network server /cimc/network #
Command |
Description |
set dhcp-enabled |
|
show network |
|
To enter pef mode, use the scope pef command in fault mode.
scope pef pef-index
pef-index | The index of a specific performance event filter. The range of valid values is 1 to 12. See Usage Guideline for a complete list of perfomance event filter indexes. |
None
Performance event filter (/fault/pef)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Following is a list of the performance event filter indexes:
1—Temperature Critical Assert Filter
2—Temperature Warning Assert Filter
3—Voltage Critical Assert Filter
4—Current Assert Filter
5—Fan Critical Assert Filter
6—Processor Assert Filter
7—Power Supply Critical Assert Filter
8—Power Supply Warning Assert Filter
9—Power Supply Redundancy Lost Filter
10—Discrete Power Supply Assert Filter
11—Memory Assert Filter
12—Drive Slot Assert Filter
This example shows how to enter pef mode:
server# scope fault server /fault # scope pef 3 server /fault/pef #
Command |
Description |
show pef |
|
To enter sel mode, use the scope sel command.
scope sel
This command has no arguments or keywords.
None
System event log (/sel)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use sel mode to perform the following tasks:
This example shows how to enter sel mode :
server# scope sel server /sel #
Command |
Description |
show entries |
|
show sel |
|
To enter sensor mode, use the scope sensor command.
scope sensor
This command has no arguments or keywords.
None
Sensor (/sensor)
Release | Modification |
---|---|
1.0(1X) | This command was introduced. |
You use sensor mode to display fan, psu, psu-redundancy, temperature, and voltage sensors information.
This example shows how to enter sensor mode :
server# scope sensor server /sensor #
Command |
Description |
show fan |
|
show voltage |
|
To enter CIMC log server mode, use the scope server command in CIMC log mode.
scope server { 1 | 2 }
1 or 2 | Selects one of two remote syslog server profiles. |
None
CIMC log (/cimc/log)
Release | Modification |
---|---|
1.1(2) | This command was introduced. |
You can use CIMC log server mode to configure and enable one or two remote syslog server profiles for sending CIMC log entries.
This example shows how to enter CIMC log server mode for the second server profile:
server# scope cimc server /cimc # scope log server /cimc/log # scope server 2 server /cimc/log/server # set server-ip 192.0.2.34 server /cimc/log/server *# set enabled yes server /cimc/log/server *# commit server /cimc/log/server #
Command |
Description |
set enabled (server) |
|
set server-ip |
|
To enter sol mode, use the scope sol command.
scope sol
This command has no arguments or keywords.
None
Serial over LAN (/sol)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use sol mode to perform the following tasks:
This example shows how to enter sol mode :
server# scope sol server /sol #
Command |
Description |
set baud-rate |
|
show sol |
|
To enter ssh mode, use the scope ssh command.
scope ssh
This command has no arguments or keywords.
None
Secure Shell (/ssh)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use ssh mode to perform the following tasks:
This example shows how to enter ssh mode :
server# scope ssh server /ssh #
Command |
Description |
set timeout (/ssh) |
|
show ssh |
|
To enter tech-support mode, use the scope tech-support command in cimc mode.
scope tech-support
This command has no arguments or keywords.
None
Technical support (/cimc/tech-support)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use tech-support mode to set up the TFTP path and server address.
This example shows how to enter tech-support mode :
server# scope cimc server /cimc # scope tech-support server /cimc/tech-support #
Command |
Description |
show tech-support |
|
start |
|
To enter trap-destination mode, use the scope trap-destination command in fault mode.
scope trap-destination trap-destination-index
trap-destination-index | The index of a specific trap destination. The range of valid values is 1 to 4. See Usage Guideline for a complete list of trap destination indexes. |
None
Trap destination (/fault/trap-destination)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
A trap destination index corresponds to a specific trap destination IP address. There are up to four possible trap destination indexes. You pair an index with an IP address using the set addr command in trap-destination mode.
This example shows how to enter trap-destination mode:
server# scope fault server /fault # scope trap-destination 4 server /fault/trap-destination #
Command |
Description |
show trap-destination |
|
To enter user mode, use the scope user command.
scope user { 1 | | 2 | | 3 | | 4 | | 5 | | 6 | | 7 | | 8 | | 9 | | 10 | | 11 | | 12 | | 13 | | 14 | | 15 }
1 through 15 |
Specifies users 1 through 15. |
None
User (/user)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use user mode to perform the following tasks:
This example shows how to enter user mode :
server# scope user 1 server /user #
Command |
Description |
set user-name |
|
show user |
|
To enter user-session mode, use the scope user-session command.
scope user-session index
index | The session ID of a specific user session. |
None
User session (/user-session)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use user-session mode to display details about user sessions.
This example shows how to enter user-session mode :
server# scope user-session 31 server /user-session #
Command |
Description |
show user |
|
show user-session |
|
To enter vmedia mode, use the scope vmedia command.
scope vmedia
This command has no arguments or keywords.
None
Virtual media (/vmedia)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You use vmedia mode to perform the following tasks:
This example shows how to enter vmedia mode :
server# scope vmedia server /vmedia #
Command |
Description |
set |
|
show vmedia |
|
To describe the chassis, use the set command in chassis mode. You can also toggle the chassis locater LED.
set { description chassis-description | | locator-led { on | | off } }
description | Specifies the description of the chassis. |
chassis-description | The description of the chassis. The range of valid values is 1 to 64. |
locator-led | Specifies whether the chassis locator LED. |
on | Turns the server locator LED on. |
off | Turns the server locator LED off. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
When you turn on the locator LED, it flashes. This allows you to easily locate the chassis.
This example shows how to turn on the locator LED:
server# scope chassis server /chassis # set locator-led on server /chassis* # commit server /chassis #
Command |
Description |
show chassis |
|
show led |
|
To create an SNMP community, use the set command in fault mode. You can also enable platform events.
set { community-str community-name | | platform-event-enabled { no | | yes } }
community-str | Specifies the SNMP community string (name). |
community-name | The name of the SNMP community. The range of valid values is 1 to 18. |
platform-event-enabled | Specifies whether platform event alerts are enabled or disabled. |
no | Sets platform event alerts to disabled. |
yes | Sets platform event alerts to enabled. |
None
Fault (/fault)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to create an SNMP community string:
server# scope fault server /fault # set community-str cs100 server /fault* # commit server /fault #
Command |
Description |
show fault |
|
show pef |
|
To set up Hyper Text Transfer Protocol (HTTP) services on the server, use the set command in http mode.
set { enabled { no | | yes } | | http-port port-number | | https-port port-number | | timeout time }
enabled | Specifies whether HTTP services are enabled or disabled. |
||
no | Specifies that HTTP is not enabled. |
||
yes | Specifies that HTTP is enabled. |
||
http-port | Sets the HTTP server port number. |
||
port-number | The HTTP port number of the server. The range of valid values is 1 to 65536.
|
||
https-port | Sets the HTTPS server port number. |
||
timeout | Sets the HTTP connection timeout time. |
||
time | The connection timeout time, in seconds. The range of valid values is 60 to 10800. |
None
HTTP (/http)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to set the HTTP port number:
server# scope http server /http # set http-port 80 server /http* # commit server /http #
Command |
Description |
show http-port |
|
show https-port |
|
To set up IP blocking on the server, use the set command in ipblocking mode.
set { enabled { no | | yes } | | fail-count fail-number | | fail-window fail-window | | penalty-time penalty-time }
enabled | Specifies whether IP blocking services are enabled or disabled. |
no | Specifies that IP blocking is not enabled. |
yes | Specifies that IP blocking is enabled. |
fail-count | Sets the failure count. |
fail-number | The failure number. The range of valid values is 3 to 10. |
fail-window | Sets the failure window. |
fail-window | The failure window. The range of valid values is 60 to 120. |
penalty-time | Sets the blocking time. |
penalty-time | The blocking time, in seconds. The range of valid values is 60 to 10800. |
None
IP blocking (/cimc/chassis/ipblocking)
Release | Modification |
---|---|
1.0(1X) | This command was introduced. |
This example shows how to enable IP blocking:
server# scope cimc server /cimc # scope network server /cimc/network # scope ipblocking server /cimc/network/ipblocking # set enabled yes server /cimc/network/ipblocking* # commit server /cimc/network/ipblocking #
Command |
Description |
show ipblocking |
|
To set up IPMI services on the server, use the set command in ipmi mode.
set { enabled { no | | yes } | | encryption-key encryption-key | | privilege-level { admin | | read-only | | user } }
enabled | Specifies whether IPMI is enabled or disabled. |
no | Specifies that IPMI is not enabled. |
yes | Specifies that IPMI is enabled. |
encryption-key | Specifies the IPMI encryption key. |
encryption-key | The IPMI encryption key. The valid value is 40 hex numbers. |
privilege-level | Specifies the IPMI privilege level. |
admin | Sets the IPMI privilege level to admin. |
read-only | Sets the IPMI privilege level to read-only. |
user | Sets the IPMI privilege level to user. |
None
Intelligent Platform Management Interface (/ipmi)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to set the IPMI encryption key:
server# scope ipmi server /ipmi # set encryption-key a9 62 b5 0a 68 6e e3 02 72 ce af f1 39 f8 1e 05 f5 19 d5 e1 7f f4 71 b9 9a 41 be e3 f5 06 4e cc 0f 63 67 2e a2 9c 74 d0 server /ipmi* # commit server /ipmi #
Command |
Description |
show ipmi |
|
To enable KVM on the server, use the set command in kvm mode.
set { enabled { no | | yes } | | encrypted { no | | yes } | | kvm-port port-number | | local- video { no | | yes } | | max-sessions number-of-sessions }
None
Keyboard Video Mouse (/kvm)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use the local-video command to display the KVM session on any monitor attached to the server.
This example shows how to enable KVM:
server# scope kvm server /kvm # set enabled yes server /kvm* # commit server /kvm #
Command |
Description |
show kvm |
|
To set up an LDAP (Lightweight Directory Access Protocol) directory on the server, use the set command in ldap mode.
set { attribute attribute-name | | base-dn base-dn-name | | enabled { no | | yes } | | encrypted { no | | yes } | | server-ip ip-address | | timeout time }
None
Lightweight Directory Access Protocol (/ldap)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You must be logged in as admin to set LDAP properties.
attribute —Specify an LDAP attribute that contains the role and locale information for the user. This property is always a name-value pair. The system queries the user record for the value that matches this attribute name. You can use the existing LDAP attribute that is mapped to CIMC user roles and locales. You can also create a custom attribute, such as the CiscoAVPair attribute, which has the following attribute ID:
1.3.6.1.4.1.9.287247.1
If you do not specify this property, user access is restricted to read-only.
enabled—When LDAP is enabled, user authentication and role authorization is performed by Active Directory for user accounts not found in the local user database.
This example shows how to set the Active Directory server timeout property:
server# scope ldap server /ldap # set timeout 100 server /ldap* # commit server /ldap #
Command |
Description |
show ldap |
|
To set up server network services on the server, use the set command in network mode.
set { alternate-dns-server ip-address | | dhcp-enabled { no | | yes } | | dns-use-dhcp { no | | yes } | | hostname host-name | | mode { dedicated | | shared_lom | | shipping } | | preferred-dns-server ip-address | | redundancy { none | | active-standby } | | v4-addr ip-address | | v4-gateway ip-address | | v4-netmask netmask | | vlan-enabled { no | | yes } | vlan-id vlan-id | | vlan-priority priority-number }
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.0(1x) | The shipping keyword was introduced. |
You must log in as a user with admin privileges to configure network properties.
mode — The CIMC network settings determine which ports can reach the CIMC. The following network mode options are available, depending on your platform:
Dedicated—A connection to the CIMC is available through the management Ethernet port or ports.
Shared LOM—A connection to the CIMC is available only through the LAN On Motherboard (LOM) Ethernet host ports.
Shipping—A connection to the CIMC is available through the management Ethernet port or ports using a limited factory default configuration.
Note |
In shared LOM mode, all host ports must belong to the same subnet. |
active-standby—Active/standby failover lets you use a standby security appliance to take over the functionality of a failed unit. When the active unit fails, it changes to the standby state, while the standby unit changes to the active state. The appliance that becomes active assumes the IP addresses and MAC addresses of the failed unit and begins to pass traffic.
This example shows how to enable DHCP:
server# scope cimc server /cimc # scope network server /cimc/network # set dhcp-enabled yes server /cimc/network* # commit server /cimc/network #
Command |
Description |
show dhcp |
|
show network |
|
To set up SoL (Serial over LAN) on the server, use the set command in sol mode.
set { baud-rate { 9600 | | 19200 | | 38400 | | 57600 | | 115200 } | enabled { no | | yes } }
baud-rate | Specifies the SoL baud rate. |
9600 | Sets baud rate to 9600 . |
19200 | Sets baud rate to 19200. |
38400 | Sets baud rate to 38400. |
57600 | Sets baud rate to 57600. |
115200 | Sets baud rate to 115200. |
enabled | Specifies whether SoL is enabled or disabled. |
no | Sets SoL to disabled. |
yes | Sets SoL to enabled. |
None
Serial over LAN (/sol)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You must log in as a user with admin privileges to configure serial over LAN.
Serial over LAN (SoL) is a mechanism that enables the input and output of the serial port of a managed system to be redirected via an SSH session over IP. SoL provides a means of reaching the host console via CIMC.
For redirection to SoL, the server console must have the following configuration:
The SoL session will display line-oriented information such as boot messages, and character-oriented screen menus such as BIOS setup menus. If the server boots an operating system or application with a bitmap-oriented display, such as Windows, the SoL session will no longer display. If the server boots a command-line-oriented operating system (OS), such as Linux, you may need to perform additional configuration of the OS in order to properly display in an SoL session.
In the SoL session, your keystrokes are transmitted to the console except for the function key F2. To send an F2 to the console, press the Escape key, then press 2.
This example shows how to set the baud rate:
server# scope sol server /sol # set baud-rate 115200 server /sol* # commit server /sol #
Command |
Description |
show sol |
|
To set up SSH (Secure Shell) services on the server, use the set command in ssh mode.
set { enabled { no | | yes } | ssh-port port-number | | timeout time }
enabled | Specifies whether SSH is enabled or disabled. |
no | Sets SSH to disabled. |
yes | Sets SSH to enabled. |
ssh-port | Specifies the SSH port. |
port-number | The SSH port number. The range of valid values is 1 to 65535. |
timeout | Specifies the SSH connection timeout. |
time | The wait time before a connection timeout, in seconds. The range of valid values is 60 to 10800. |
None
Secure Shell (/ssh)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You must log in as a user with admin privileges to configure SSH.
This example shows how to set the SSH port number:
server# scope ssh server /ssh # set ssh-port 22 server /ssh* # commit server /ssh #
Command |
Description |
show ssh |
|
To set up on the server, use the set command in user mode.
set { enabled { no | | yes } | | name user-name | | password password | | role { admin | | read-only | | user } }
enabled | Specifies whether user accounts are enabled or disabled. |
no | Specifies that user accounts are not enabled. |
yes | Specifies that user accounts are enabled. |
name | Sets the name of the user. |
user-name | The name of the user. The range of valid values is 1 to 70. |
password | Sets up the password. |
password | The password. The range of valid values is 1 to 80. |
role | Sets up the users role. |
admin | Sets the user role to admin. |
read-only | Sets the user role to read-only. |
user | Sets the user role to user. |
None
User (/user)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You must log in as a user with admin privileges to configure local users.
A user of the CLI will be one of three roles:
To recover from a lost admin password, see the Cisco UCS C-Series server installation and service guide for your platform.
This example shows how to enable user accounts:
server# scope user 1 server /user # set enabled yes server /user* # commit server /user #
Command |
Description |
show user |
|
show user-session |
|
To set up VMedia (virtual media) services on the server, use the set command in vmedia mode.
set { enabled { no | | yes } | | encrypted { no | | yes } }
None
Virtual media (/vmedia)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
You must log in as a user with admin privileges to configure virtual media.
This example shows how to enable VMedia:
server# scope vmedia server /vmedia # set enabled yes server /vmedia* # commit server /vmedia #
Command |
Description |
show vmedia |
|
To set up an action for a performance event filter, use the set action command in pef mode.
set action { none | | power-off | | reboot | | power-cycle }
none | Specifies no action. |
power-off | Specifies that the server power off. |
reboot | Specifies that the server reboots. |
power-cycle | Specifies that the server power cycle. |
None
Performance event filters (/fault/pef)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Following is a list of the performance event filter indexes:
1—Temperature Critical Assert Filter
2—Temperature Warning Assert Filter
3—Voltage Critical Assert Filter
4—Current Assert Filter
5—Fan Critical Assert Filter
6—Processor Assert Filter
7—Power Supply Critical Assert Filter
8—Power Supply Warning Assert Filter
9—Power Supply Redundancy Lost Filter
10—Discrete Power Supply Assert Filter
11—Memory Assert Filter
12—Drive Slot Assert Filter
This example shows how to set up an action for performance event filter 3:
server# scope fault server /fault # scope pef 3 server /fault/pef # set action power-cycle server /fault/pef* # commit server /fault/pef #
Command |
Description |
show pef |
|
To assign an IP address to a trap destination index, use the set addr command in trap-destination mode.
set addr ip-address
ip-address | The IP address of the trap destination. The format is x.x.x.x. |
None
Trap destination (/fault/trap-destination)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to assign an IP address to a trap destination index:
server# scope fault server /fault # scope trap-destination 3 server /fault/trap-destination # set addr 209.165.200.225 server /fault/trap-destination* # commit server /fault/trap-destination #
Command |
Description |
show trap-destination |
|
To set the boot order for the server, use the set boot-order command in bios mode.
set boot-order boot-order
boot-order | Sets the server boot order. |
boot-order | The server boot order. Use the following boot order arguments, arranging them in the order that you want: |
None
BIOS (/bios)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Type the boot order arguments using quotes and commas as delimiters. Following is an example:
"EFI","HDD","FDD","CDROM","PXE"
The arguments are not case sensitive.
This example shows how to set up the boot order for the server:
server# scope bios server /bios # set boot-order "EFI","HDD","FDD","CDROM","PXE" server /bios* # commit server /bios #
Command |
Description |
show bios |
|
show actual-boot-order |
|
To change the CLI output, use the set cli output command.
set cli output { default | | yaml }
cli output | Specifies server CLI output. |
default | Sets CLI output to default. |
yaml | Sets CLI ouput to YAML (Yet Another Markup Language). |
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to change the CLI output to YAML:
server# set cli output yaml CLI output format set to yaml server#
To set up a description for the chassis, use the set description command in chassis mode.
set description chassis-description
chassis-description | The description of the chassis. The range of valid values is 1 to 64. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to :
server# scope chassis server /chassis # set description testServer server /chassis* # commit server /chassis #
Command |
Description |
show chassis |
|
To enable or disable the sending of CIMC log entries to a remote syslog server, use the set enabled command in CIMC log server mode.
set enabled { no | yes }
no | Specifes that CIMC log entries are not sent to a remote syslog server. |
yes | Specifes that CIMC log entries are sent to a remote syslog server. |
CIMC log entries are not sent.
CIMC log server (/cimc/log/server)
Release | Modification |
---|---|
1.1(2) | This command was introduced. |
Use this command to enable or disable the sending of CIMC log entries to a remote syslog server.
This example shows how to configure a remote syslog server profile and enable the sending of CIMC log entries:
server# scope cimc server /cimc # scope log server /cimc/log # scope server 2 server /cimc/log/server # set server-ip 192.0.2.34 server /cimc/log/server *# set enabled yes server /cimc/log/server *# commit server /cimc/log/server #
Command |
Description |
set server-ip |
|
To enable or disable trap destinations on the server, use the set enabled command in trap-destination mode.
set enabled { no | | yes }
no | Specifies that trap destination services are disabled. |
yes | Specifies that trap destination services are enabled. |
None
Trap destination (/fault/trap-destination)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to enable trap destination services:
server# scope fault server /fault # scope trap-destination 2 server /fault/trap-destination # set enabled yes server /fault/trap-destination* # commit server /fault/trap-destination #
Command |
Description |
show trap-destination |
|
To turn the server locator LED on or off, use the set locator-led command in chassis mode.
set locator-led { off | | on }
off | Turns the loactor LED off. |
on | Turns the loactor LED on. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to turn on the locator LED:
server# scope chassis server /chassis # set locator-led on server /chassis* # commit server /chassis #
Command |
Description |
show chassis |
|
show led |
|
To set the TFTP path, use the set path command in tech-support mode.
set path tftp-path
tftp-path | The TFTP path. |
None
Technical support (/cimc/tech-support)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Specifies the path to the support data file should be stored.
Perform this task along with set tftp-ip when requested by the Cisco Technical Assistance Center (TAC). This utility creates a summary report containing configuration information, logs and diagnostic data that will help TAC in troubleshooting and resolving technical issues.
This example shows how to set the TFTP path:
server# scope cimc server /cimc # scope tech-support server /cimc/tech-support # set path /test/test.bin server /cimc/tech-support* # commit server /cimc/tech-support #
Command |
Description |
set tftp-ip |
|
show tech-support |
|
To enable performance event filter alerts on the server, use the set send-alert command in pef mode.
set send-alert { no | | yes }
no | Specifies that performance event filter alerts are not enabled. |
yes | Specifies that performance event filter alerts are enabled. |
None
Performance event filters (/fault/pef)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to enable performance event filter alerts on the server:
server# scope fault server /fault # scope pef 3 server /fault/pef # set send-alert yes server /fault/pef* # commit server /fault/pef #
Command |
Description |
show pef |
|
To configure the IP address of a remote syslog server, use the set server-ip command in CIMC log server mode.
set server-ip ip-address
ip-address | Specifies the IP address of a remote syslog server. |
None
CIMC log server (/cimc/log/server)
Release | Modification |
---|---|
1.1(2) | This command was introduced. |
Use this command to configure the IP address of a remote syslog server for sending CIMC log entries.
This example shows how to configure a remote syslog server profile and enable the sending of CIMC log entries:
server# scope cimc server /cimc # scope log server /cimc/log # scope server 2 server /cimc/log/server # set server-ip 192.0.2.34 server /cimc/log/server *# set enabled yes server /cimc/log/server *# commit server /cimc/log/server #
Command |
Description |
set enabled (server) |
|
To set the TFTP server IP address, use the set tftp-ip command in tech-support mode.
set tftp-ip ip-address
ip-address | The IP address of the TFTP server. The format is X.X.X.X. |
None
Technical support (/cimc/tech-support)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Specifies the IP address of the TFTP server on which the support data file should be stored.
Perform this task along with set path when requested by the Cisco Technical Assistance Center (TAC). This utility creates a summary report containing configuration information, logs and diagnostic data that will help TAC in troubleshooting and resolving technical issues.
This example shows how to set the TFTP server IP address:
server# scope cimc server /cimc # scope tech-support server /cimc/tech-support # set tftp-ip 209.165.200.225 server /cimc/tech-support* # commit server /cimc/tech-support #
Command |
Description |
set tftp-path |
|
show tech-support |
|
To display the actual boot order, use the show actual-boot-order command in bios mode.
show actual-boot-order [ detail ]
detail | (Optional) Displays detailed information about the actual boot order in list format. |
None
BIOS (/bios)
Release | Modification |
---|---|
1.0(1x) | This command was introduced. |
This example shows how to display the actual boot order:
server# scope bios server /bios # show actual-boot-order Boot Order Type Boot Device ------------ ------------------------- ----------------------------------- 1 CD/DVD CD-ROM 2 CD/DVD Cisco Virtual CD/DVD 1.18 3 Network Device (PXE) Cisco NIC 23:0.0 4 Network Device (PXE) MBA v5.0.5 Slot 0100 5 Network Device (PXE) MBA v5.0.5 Slot 0101 6 Network Device (PXE) MBA v5.0.5 Slot 0200 7 Network Device (PXE) MBA v5.0.5 Slot 0201 8 Network Device (PXE) Cisco NIC 22:0.0 9 Internal EFI Shell Internal EFI Shell 10 FDD Cisco Virtual HDD 1.18 11 FDD Cisco Virtual Floppy 1.18 server /bios #
Command |
Description |
set boot-order |
|
To display information about the BIOS, use the show bios command.
show bios [ detail ]
detail | (Optional) Displays detailed information about the bios, in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show bios displays the server boot order. show bios detail and show detail in bios mode displays the server boot order and firmware update/recovery information.
When you use the detail keyword, the boot order of the following available boot devices displays:
This example shows how to display the server boot order:
server# show bios BIOS Version Boot Order ---------------------------------------- ---------------------------- C250.1.1.0.6.031920100857 (none) server#
Command |
Description |
set boot-order |
|
recover |
|
To display informaion about the server certificate, use the show certificate command.
show certificate [ detail ]
detail | (Optional) Displays the whole certificate. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show certificate displays the serial number of the certificate, and the dates the certificate is valid for. show certificate detail in root mode and show detail in certificate mode displays the whole certificate.
This example shows how to display the serial number of the certificate, and the dates the certificate is valid for:
server# show certificate Serial Number Valid From Valid To ---------------- ------------------------ ------------------------ 001 Apr 13 13:49:00 2009 GMT Apr 11 13:49:00 2019 GMT server#
This example shows how to display the whole certificate:
server# show certificate detail Certificate Information: Serial Number: 00 Subject Country Code (CC): US Subject State (S): California Subject Locality (L): San Jose Subject Organization (O): ABC Inc. Subject Organizational Unit (OU): Subject Common Name (CN): abcinc.com Issuer Country Code (CC): US Issuer State (S): California Issuer Locality (L): San Jose Issuer Organization (O): Cisco Systems Inc. Issuer Organizational Unit (OU): Issuer Common Name (CN): cisco.com Valid From: Sep 8 22:53:59 2009 GMT Valid To: Sep 6 22:53:59 2019 GMT server#
Command |
Description |
generate-csr |
|
upload |
|
To display information about the chassis, use the show chassis command.
show chassis [ detail ]
detail | (Optional) Displays detailed information about the chassis, in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show chassis displays information about the chassis in table format. show chassis detail and show detail in chassis mode displays serial number, product name, PID, UUID, and description. Additionally, it displays chassis power state and the state of the locator LED.
This example shows how to display information about the chassis in table format:
server# show chassis Power Serial Number Product Name UUID ----- ------------- ------------- ------------------------------------ on QTF-0934-00 R100-1120402 208F4277020FBADBADBEA80000DEAD00 server#
Command |
Description |
set locator-led |
|
To display information about CIMC, use the show cimc command.
show cimc [ detail ]
detail | (Optional) Displays detailed information about CIMC, in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show cimc displays information about CIMC in table format. show cimc detail and show detail in cimc mode displays firmware version and boot loader version.
This example shows how to display information about CIMC in table format:
server# show cimc Firmware Version Current Time -------------------- ------------------------ 1.0(0.86) Fri Oct 2 12:19:17 2009 server#
Command |
Description |
show firmware |
|
show log (cimc) |
|
To display uncommitted configuration commands, use the show configuration pending command.
show configuration pending
This command has no arguments or keywords.
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example displays uncommitted configuration commands:
server /cimc/network *# show configuration pending Modify /cimc/network hostname SanJoseServer3 dhcp-enabled yes v4-addr 10.20.30.111 dns-use-dhcp yes server /cimc/network *#
Command |
Description |
commit |
|
discard |
|
To display information about the CPU, use the show cpu command in the chassis mode.
show cpu [ detail ]
detail | (Optional) Displays detailed information about the CPU, in list format. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show cpu displays a list of CPUs. show cpu detail displays information for each CPU .
This example shows how to display detailed information about the CPUs:
server# scope chassis server /chassis # show cpu detail Name CPU1: Manufacturer: Intel(R) Corporation Family: Xeon Thread Count : 8 Cores : 4 Serial No.: Not Specified Version: Intel(R) Xeon(R) CPU L5520 @ 2.27GHz Speed (Mhz) : 2266 Max. Speed (Mhz) : 4000 Signature: "Signature: Type 0, Family 6, Model 26, Stepping 5 Status: Enabled Name CPU2: Manufacturer: Intel(R) Corporation Family: Xeon Thread Count : 8 Cores : 4 Serial No.: Not Specified Version: Intel(R) Xeon(R) CPU L5520 @ 2.27GHz Speed (Mhz) : 2266 Max. Speed (Mhz) : 4000 Signature: "Signature: Type 0, Family 6, Model 26, Stepping 5 Status: Enabled server /chassis #
Command |
Description |
show dimm |
|
show psu |
|
To display information about the status of the current sensors, use the show current command in sensor mode.
show current [ detail ]
detail | (Optional) Displays detailed information about the status of the voltage sensors in list form. |
None
Sensor (/sensor)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the status of the current sensors:
server# scope sensor server /sensor # show current detail Name VR_CPU1_IOUT: Sensor Status: Normal Reading: 15.65 Units: AMP Min. Warning: N/A Max. Warning: 152.68 Min. Failure: N/A Max. Failure: 164.04 Name VR_CPU2_IOUT: Sensor Status: Normal Reading: 11.39 Units: AMP Min. Warning: N/A Max. Warning: 152.68 Min. Failure: N/A Max. Failure: 164.04 server /sensor #
To display information about the DIMMs (dual inline memory modules) in the chassis, use the show dimm command in chassis mode.
show dimm [ detail ]
detail | (Optional) Displays detailed information about the DIMMs, in list format. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show dimmdisplays a list of DIMMs. show dimm detaildisplays capacity, speed, and type for each DIMM .
This example shows how to display detailed information about the DIMMs:
server# scope chassis server /chassis # show dimm detail Name DIMM_A0: Capacity (MB): 4096 Speed (MHz): 1067 Type: Other Name DIMM_A1: Capacity (MB): 0 Speed (MHz): 1067 Type: Other Name DIMM_A2: Capacity (MB): 0 Speed (MHz): 1067 Type: Other Name DIMM_A3: Capacity (MB): 0 Speed (MHz): 1067 Type: Other Name DIMM_A4: Capacity (MB): 4096 Speed (MHz): 1067 Type: Other Name DIMM_A5: Capacity (MB): 0 Speed (MHz): 1067 --More--
Command |
Description |
show cpu |
|
To display the CIMC event log, use the show entries command in log mode.
show entries [ detail ]
detail | (Optional) Displays the CIMC event log in detail. |
None
Log (/cimc/log)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show entries displays trace log entries in continuous string format. show entries detail displays time, source, and description for each trace log entry, in list format.
This example shows how to display the detailed event log:
server# scope cimc server /cimc # scope log server /cimc/log # show entries detail Trace Log: Time: 2010 Jun 6 15:52:18 Source: BMC:AUDIT:- Description: Session open (user:admin, ip:10.21.115.69, id:45, type:CLI) Order: 0 Trace Log: Time: 2010 Jun 6 15:52:18 Source: BMC:dropbear:- Description: " pam_session_manager(sshd:session): session (45) opened for user admin from 10.21.115.69 by (uid=0) " Order: 1 Trace Log: Time: 2010 Jun 6 15:52:18 Source: BMC:AUDIT:- Description: Login success (user:admin, ip:10.21.115.69, service:sshd) Order: 2 Trace Log: Time: 2010 Jun 6 15:52:18 Source: BMC:dropbear:- Description: " pam_auth_status(sshd:session): Login Successfull for user=admin, host=10.21.115.69 " Order: 3 Trace Log: --More--
Command |
Description |
show entries (sel) |
|
To display the system event log, use the show entries command in sel mode.
show entries [ detail ]
detail | (Optional) Displays the system event log in detail. |
None
SEL (/sel )
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show entries displays system event log entries in continuous strings. show entries detail displays time, source, and description for each system event log entry, in list format.
This example shows how to display the system event log:
server# scope sel server /sel # show entries System Event Log: Time: 2010-06-05 22:19:55 Severity: Warning Description: " FRU_RAM P1V5_IOH: Voltage sensor for FRU_RAM, failure event was deasserted" System Event Log: Time: 2010-06-05 22:19:55 Severity: Critical Description: " FRU_RAM P1V5_IOH: Voltage sensor for FRU_RAM, non-recoverable event was deasserted" System Event Log: Time: 2010-06-05 22:19:49 Severity: Non-Recoverable Description: " FRU_RAM P1V5_IOH: Voltage sensor for FRU_RAM, non-recoverable event was asserted" System Event Log: Time: 2010-06-05 22:19:49 Severity: Critical Description: " FRU_RAM P1V5_IOH: Voltage sensor for FRU_RAM, failure event was asserted" System Event Log: Time: 2010-06-05 19:45:32 Severity: Warning --More--
Command |
Description |
show entries (log) |
|
To display information about the fan sensors, use the show fan command in sensor mode.
show fan [ detail ]
detail | (Optional) Displays . |
None
Sensor (/sensor)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the fan sensors:
Server# scope sensor Server /sensor # show fan Name Sensor Status Reading Units Min. Warning Max. Warning Min. Failure Max. Failure -------------------- -------------------- ---------- ---------- --------------- --------------- --------------- --------------- PSU1_FAN_1 Normal 6592 RPM N/A N/A N/A N/A PSU2_FAN_1 Normal 2560 RPM N/A N/A N/A N/A W793_FAN1_TACH1 Normal 5300 RPM N/A N/A 800 N/A W793_FAN1_TACH2 Normal 5400 RPM N/A N/A 800 N/A W793_FAN2_TACH1 Normal 5500 RPM N/A N/A 800 N/A W793_FAN2_TACH2 Normal 5400 RPM N/A N/A 800 N/A W793_FAN3_TACH1 Normal 5300 RPM N/A N/A 800 N/A W793_FAN3_TACH2 Normal 5500 RPM N/A N/A 800 N/A W793_FAN4_TACH1 Normal 5300 RPM N/A N/A 800 N/A W793_FAN4_TACH2 Normal 5500 RPM N/A N/A 800 N/A --More-- Server /sensor # show fan detail Name PSU1_FAN_1: Sensor Status: Normal Reading: 7872 Units: RPM Min. Warning: N/A Max. Warning: N/A Min. Failure: N/A Max. Failure: N/A Name PSU2_FAN_1: Sensor Status: Normal Reading: 2496 Units: RPM Min. Warning: N/A Max. Warning: N/A Min. Failure: N/A Max. Failure: N/A Name W793_FAN1_TACH1: Sensor Status: Normal Reading: 5300 Units: RPM Min. Warning: N/A Max. Warning: N/A Min. Failure: 800 Max. Failure: N/A Name W793_FAN1_TACH2: Sensor Status: Normal Reading: 5400 Units: RPM Min. Warning: N/A Max. Warning: N/A Min. Failure: 800 Max. Failure: N/A Name W793_FAN2_TACH1: Sensor Status: Normal Reading: 5500 Units: RPM Min. Warning: N/A Max. Warning: N/A Min. Failure: 800 Max. Failure: N/A Name W793_FAN2_TACH2: Sensor Status: Normal --More--
Command |
Description |
show cpu |
|
To display information about SNMP services on the server, use the show fault command.
show fault [ detail ]
detail | (Optional) Displays detailed information about SNMP services, in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show fault displays information about SNMP services in table format. show fault, show fault detail, and show detail in fault mode display information about community strings and platform enabled events.
This example shows how to display SNMP services information in table format:
server# show fault SNMP Community String Platform Event Enabled --------------------- ---------------------- 33West yes 34West no server#
Command |
Description |
show pef |
|
show trap-destination |
|
To display information about the firmware on the server, use the show firmware command in cimc mode.
show firmware [ detail ]
detail | (Optional) Displays detailed information about firmware, in list format. |
None
CIMC (/cimc)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show firmware displays information about firmware in table format. show firmware detail and show detail in firmware mode display information about updates, firmware version, and boot loader version.
This example shows how to display information about updates, firmware version, and boot loader version:
server# scope cimc server /cimc # show firmware detail Firmware Image Information: Update Stage: NONE Update Progress: 0 Current FW Version: 1.1(0.3) FW Image 1 Version: 1.1(0.3) FW Image 1 State: BACKUP INACTIVATED FW Image 2 Version: 1.1(0.3) FW Image 2 State: RUNNING ACTIVATED Boot-loader Version: 1.1(0.3) server /cimc #
Command |
Description |
show cimc |
|
show version |
|
To display information about installed hard disk drives (HDD) in the chassis, use the show hdd command in chassis mode.
show hdd [detail]
detail | (Optional) Displays detailed information about the HDDs in list form. |
None
Chassis (/chassis #)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about hard disk drives in the chassis:
Server# scope chassis Server /chassis # show hdd Name Status -------------------- -------------------- HDD_01_STATUS present HDD_02_STATUS present HDD_03_STATUS present HDD_04_STATUS present Server /chassis # show hdd detail Name HDD_01_STATUS: Status : present Name HDD_02_STATUS: Status : present Name HDD_03_STATUS: Status : present Name HDD_04_STATUS: Status : present Server /chassis #
Command |
Description |
show psu |
|
To display information about HTTP services on the server, use the show http command.
show http [ detail ]
detail | (Optional) Displays detailed information about HTTP services, in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
show http displays HTTP information in table format. show http detail and show detail in http mode display information about HTTP ports, session timeout, and session activity.
This example shows how to display information about HTTP services in table format:
server# show http HTTP Port HTTPS Port Timeout Active Sessions Enabled ---------- ---------- -------- --------------- ------- 80 443 1800 0 yes server#
Command |
Description |
set http-port |
|
set https-port |
|
To display information about the network IP blocking configuration, use the show ipblocking command in network mode.
show ipblocking [ detail ]
detail | (Optional) Displays detailed information about the IP blocking configuration in list format. |
None
IP blocking (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the IP blocking configuration:
server# scope cimc Server /cimc # scope network server /cimc/network # show ipblocking detail IP Blocking Setting: Enabled: no Fail Count: 5 Fail Window: 60 Blocking Time: 300 server /cimc/network #
Command |
Description |
show network |
|
To display information about the configuration and status of IPMI (Intelligent Platform Management Interface) on the server, use the show ipmi command.
show ipmi [detail]
detail | (Optional) Displays detailed iinformation about the configuration and status of IPMI on the server in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the configuration and status of IPMI:
server# show ipmi detail IPMI over LAN Settings: Enabled: yes Encryption Key: abcdef01234567890abcdef01234567890abcdef Privilege Level Limit: admin server#
Command |
Description |
set enabled (ipmi) |
|
set encryption-key (ipmi) |
|
To display information about the KVM, use the show kvm command.
show kvm [ detail ]
detail | (Optional) Displays detailed information about the KVM in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the KVM:
server# show kvm Encryption Enabled Local Video Active Sessions Enabled KVM Port ------------------ ---------------- --------------- ------- -------- no no 0 yes 2068 server#
Command |
Description |
set kvm-port |
|
set max-sessions (kvm) |
|
To display information about the configuration and status of the Active Directory, use the show ldap command.
show ldap [ detail ]
detail | (Optional) Displays detailed iinformation about the configuration and status of the Active Directory in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the configuration and status of the Active Directory:
server# show ldap detail LDAP Settings: Server IP: 10.20.30.136 BaseDN: example.com Encrypted: no Timeout: 60 Enabled: no Attribute: CiscoAvPair server#
Command |
Description |
set server-ip (ldap) |
|
set base-dn (ldap) |
|
To display information about the server LEDs, use the show led command in the chassis command mode.
show led [ detail ]
detail | (Optional) Displays detailed information about the server LEDs in list format. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the server LEDs:
server# scope chassis server /chassis # show led LED Name LED State LED Color ------------------------- ---------- -------- DDR3_P2_D1_INFO OFF AMBER DDR3_P1_A1_INFO OFF RED LED_HLTH_STATUS ON GREEN LED_FPID OFF BLUE LED_PSU_STATUS OFF AMBER LED_DIMM_STATUS ON GREEN LED_CPU_STATUS ON GREEN
Command |
Description |
set locator-led |
|
To display information about the server network configuration, use the show network command in cimc mode.
show network [ detail ]
detail | (Optional) Displays detailed information about the server network configuration in list format. |
None
CIMC (/cimc)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the server network configuration:
server# scope cimc server /cimc # show network DHCP Enabled VLAN Enabled ------------ ------------ no no server#
Command |
Description |
set dhcp-enabled |
|
show ipblocking |
|
To display information about the configuration and status of PEFs (Platform Event Filters), use the show pef command in fault mode.
show pef [ pef-number ] [ detail ]
pef-number | Displays information about the specified PEF. If the pef-number variable is omitted, the command displays information about all PEFs. |
detail | (Optional) Displays detailed information in list form. |
None
Fault (/fault)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the configuration and status of all PEFs:
Server# scope fault Server /fault # show pef Platform Event Filter Event Action Send Alert --------------------- ----------------------------------- ----------- ------------------ 1 Temperature Critical Assert Filter none no 2 Temperature Warning Assert Filter none no 3 Voltage Critical Assert Filter none no 4 Voltage Warning Assert Filter none no 5 Current Assert Filter none no 6 Fan Critical Assert Filter none no 7 Fan Warning Assert Filter none no 8 Processor Assert Filter none no 9 Power Supply Critical Assert Filter none no 10 Power Supply Warning Assert Filter none no 11 Power Supply Redundancy Lost Filter none no 12 Discrete Power Supply Assert Filter none no 13 Memory Assert Filter none no 14 Drive Slot Assert Filter none no server /fault #
Command |
Description |
set platform-event-enabled |
|
To display information about the PSUs (power supply units), use the show psu command in chassis mode.
show psu [ detail ]
detail | (Optional) Displays detailed information about the PSUs in list format. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the chassis PSUs:
server# scope chassis server /chassis # show psu detail Name PSU1: In. Power (Watts): 103 Out. Power (Watts): 0 Firmware : Status : Present server /chassis #
Command |
Description |
show voltage |
|
To display information about the status of the PSU (power supply unit) sensors, use the show psu command in sensor mode.
show psu [ detail ]
detail | (Optional) Displays detailed information about the PSU sensors in list format. |
None
Sensor (/sensor)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the status of the PSU sensors:
server# scope sensor server /sensor # show psu Name Sensor Status Reading Units Min. Warning Max. Warning Min. Failure Max. Failure -------------------- -------------------- ---------- ---------- --------------- --------------- --------------- --------------- PSU1_POUT Normal 68 Watts N/A 652 N/A 680 PSU1_PIN Normal 76 Watts N/A 652 N/A 680 PSU1_STATUS Normal present PSU2_STATUS Critical absent server /sensor #
Command |
Description |
show voltage |
|
To display information about the status of PSU (power supply unit) redundancy, use the show psu-redundancy command in sensor mode.
show psu-redundancy [ detail ]
detail | (Optional) Displays detailed information about the status of PSU redundancy in list format. |
None
Sensor (/sensor)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the status of PSU redundancy:
server# scope sensor server /sensor # show psu-redundancy detail Name PS_RDNDNT_MODE: Reading: full Sensor Status: Normal server /sensor #
Command |
Description |
show psu |
|
To display information about the SoL (Serial over LAN) configuration, use the show sol command.
show sol [ detail ]
detail | (Optional) Displays detailed information about the SoL (serial over LAN) configuration in list format. |
None
Root (/server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the SoL configuration:
server# show sol detail Serial Over LAN: Enabled: no Baud Rate(bps): 115200 server#
Command |
Description |
set baud-rate |
|
To display information about the SSH (Secure Shell) configuration on the server, use the show ssh command.
show ssh [ detail ]
detail | (Optional) Displays detailed information about the SSH configuration in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the SSH configuration:
server# show ssh detail SSH Settings: SSH Port: 22 Timeout: 10800 Max Sessions: 4 Active Sessions: 1 Enabled: yes server#
Command |
Description |
set enabled (ssh) |
|
set ssh-port (ssh) |
|
To display information about the configuration of the tech-support utility, use the show tech-support command in cimc mode.
show tech-support [ detail ]
detail | (Optional) Displays detailed information about the configuration of the tech-support utility in list format. |
None
CIMC (/cimc)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the configuration of the tech-support utility:
server# scope cimc server /cimc # show tech-support detail Tech Support: TFTP Server Address: 10.20.30.211 TFTP Path: /user/tech-support Progress(%): 100 Status: COMPLETED server /cimc #
Command |
Description |
set path (tech-support) |
|
set tftp-ip (tech-support) |
|
To display information about the status of the temperature sensors, use the show temperature command in sensor mode.
show temperature [ detail ]
detail | (Optional) Displays detailed information about the status of the temperature sensors in list format. |
None
Sensor (/sensor)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the status of the temperature sensors:
server# scope sensor server /sensor # show temperature Name Sensor Status Reading Units Min. Warning Max. Warning Min. Failure Max. Failure ------------------------- -------------- ---------- ---------- ------------ ------------ ------------ ------------ IOH_TEMP_SENS Normal 42.0 C N/A 80.0 N/A 85.0 P2_TEMP_SENS Normal 43.0 C N/A 80.0 N/A 81.0 P1_TEMP_SENS Normal 45.0 C N/A 80.0 N/A 81.0 DDR3_P2_D1_TMP Normal 28.0 C N/A 90.0 N/A 95.0 DDR3_P1_A1_TMP Normal 30.0 C N/A 90.0 N/A 95.0 PSU1_TEMP_1 Normal 40.0 C N/A 60.0 N/A 65.0 PSU2_TEMP_1 Normal 40.0 C N/A 60.0 N/A 65.0 FP_AMBIENT_TEMP Normal 22.0 C N/A 40.0 N/A 45.0 server /sensor #
To display information about SNMP trap destinations, use the show trap-destination command in fault mode.
show trap-destination [ trap-destination-number ] [ detail ]
trap-destination-number | Displays information about only the specified SNMP trap destination. If the trap-destination-number variable is omitted, displays information about all SNMP trap destinations. |
detail | (Optional) Displays detailed information about SNMP trap destinations in list format. |
None
Fault (/fault)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the SNMP trap destinations:
server# scope fault server /fault # show trap-destination Trap Destination IP Address Enabled ---------------- ---------------- -------- 1 209.165.200.225 yes 2 0.0.0.0 no 3 0.0.0.0 no 4 0.0.0.0 no server /fault #
Command |
Description |
set addr (trap-destination) |
|
To display information about user profiles on the server, use the show user command.
show user [ user-number ] [ detail ]
user-number | (Optional) Displays only the specified user profile. If the user-number variable is omitted, displays all user profiles. |
detail | (Optional) Displays detailed information in list form. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about all user profiles:
server# show user User Name Role Enabled ------ ---------------- -------- -------- 1 admin admin yes 2 jsmith admin yes 3 (n/a) (n/a) no 4 (n/a) (n/a) no 5 bjones readonly yes 6 (n/a) (n/a) no 7 (n/a) (n/a) no 8 (n/a) (n/a) no 9 (n/a) (n/a) no 10 (n/a) (n/a) no 11 (n/a) (n/a) no 12 (n/a) (n/a) no 13 (n/a) (n/a) no 14 (n/a) (n/a) no 15 (n/a) (n/a) no server#
Command |
Description |
set enabled (user) |
|
set name (user) |
|
To display information about current user sessions, use the show user-session command.
show user-session [ session-number ] [ detail ]
session-number | Displays information about a specific session. |
detail | (Optional) Displays detailed information about current user sessions in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display user session information for all current user sessions:
server# show user-session ID Name IP Address Type Killable ------ ---------------- ----------------- ------------ -------- 4 admin 10.20.30.123 CLI yes 2 admin 10.20.30.185 vKVM yes 5 read-only 10.20.30.187 CLI no server#
This example shows how to display user session information about a specific user session:
server# show user-session 2 ID Name IP Address Type Killable ------ ---------------- ----------------- ------------ -------- 2 admin 10.20.30.185 vKVM yes server#
Command |
Description |
show user |
|
To display the version number of the running firmware, use the show version command.
show version [ detail ]
detail | (Optional) Displays the version number of the running firmware in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display the version of the running firmware:
server# show version Firmware Version -------------------- 1.1(0.3) server#
Command |
Description |
activate (firmware) |
|
To display information about the status and configuration of virtual media, use the show vmedia command.
show vmedia [ detail ]
detail | (Optional) Displays detailed information about the status and configuration of virtual media in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the status and configuration of virtual media:
server# show vmedia Encryption Enabled Enabled Active Sessions ------------------ ------- --------------- no yes 0 server#
Command |
Description |
set encryption (vmedia) |
|
To display information about the status of the voltage sensors, use the show voltage command in sensor mode.
show voltage [ detail ]
detail | (Optional) Displays detailed information about the status of the voltage sensors in list form. |
None
Sensor (/sensor)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to display information about the status of the voltage sensors:
server# scope sensor server /sensor # show voltage Name Sensor Status Reading Units Min. Warning Max. Warning Min. Failure Max. Failure ------------------------- -------------- ---------- ---------- ------------ ------------ ------------ ------------ P3V_BAT_SCALED Normal 3.022 V N/A N/A 2.798 3.088 P12V_SCALED Normal 12.095 V N/A N/A 11.623 12.331 P5V_SCALED Normal 5.061 V N/A N/A 4.844 5.157 P3V3_SCALED Normal 3.318 V N/A N/A 3.191 3.381 P5V_STBY_SCALED Normal 4.988 V N/A N/A 4.844 5.157 PV_VCCP_CPU1 Normal 0.940 V N/A N/A 0.725 1.391 PV_VCCP_CPU2 Normal 0.891 V N/A N/A 0.725 1.391 P1V5_DDR3_CPU1 Normal 1.499 V N/A N/A 1.450 1.548 P1V5_DDR3_CPU2 Normal 1.499 V N/A N/A 1.450 1.548 P1V1_IOH Normal 1.087 V N/A N/A 1.068 1.136 P1V8_AUX Normal 1.773 V N/A N/A 1.744 1.852 PSU1_VOUT Normal 12.000 V N/A N/A N/A 13.000 PSU2_VOUT Normal 12.000 V N/A N/A N/A 13.000 server /sensor #
To start the technical support process, use the start command.
start
This command has no arguments or keywords.
None
Technical support (/cimc/tech-support)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to start the technical support process:
server# scope cimc server /cimc # scope tech-support server /cimc/tech-support # start Tech Support upload started. server /cimc/tech-support #
Command |
Description |
cancel |
|
To terminate a CLI session, use the terminate command in user-session mode.
terminate
This command has no arguments or keywords.
None
User session (/user-session)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to terminate a CLI session:
server# scope user-session 3 server /user-session # terminate
Command |
Description |
show user-session |
|
To return to root mode from any other mode, use the top command.
top
This command has no arguments or keywords.
None
Any command mode
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to enter root mode from log mode:
server /cimc/log # top server#
Command |
Description |
exit |
|
To update server firmware, use the update command.
update ip-address file-path
ip-address | The IP address of the TFTP server. The format is X.X.X.X. |
file-path | The path to the update file on the TFTP server. |
None
Firmware (/cimc/firmware)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to update server firmware:
server# scope cimc server /cimc # scope firmware server /cimc/firmware # update 209.165.200.225 //test/cimc66-78.bin <CR> Press Enter key Firmware update has started. Please check the status using "show detail" server /cimc/firmware #
Command |
Description |
show cimc |
|
show version |
|
To upload a certificate, use the upload command in certificate mode.
This command has no arguments or keywords.
None
Certificate (/certificate)
Release | Modification |
---|---|
1.0(1x) | This command was introduced. |
This example shows how to upload a certificate:
server# scope certificate server /certificate # upload Please paste your certificate here, when finished, press CTRL+D. MIIB0TCCAToCAQAwbDELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMQ0wCwYDVQQH EwRoZXJlMQwwCgYDVQQKEwN0aW0xCzAJBgNVBAsTAjAxMQwwCgYDVQQDEwNib2Ix GDAWBgkqhkiG9w0BCQEWCW1lQG1lLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAw gYkCgYEAw49pYuDXdOfHtXwBT7k5kX1set/I3e8TtkuO/EQ5HVd9HrPIy4Kpb3Oj 33CkqjysVWBpPSGzWAlEL6cZYs5p6JxR74+tqW5BYpNKRLNFawpsTZvCXhe/n/O2 WYsx1FnW1m6BgQnPKCBCp9R1ESmq9Np24r2c3PEStZEjeIVWbaUCAwEAAaAlMCMG CSqGSIb3DQEJBzEWExRBIGNoYWxsZW5nZSBwYXNzd29yZDANBgkqhkiG9w0BAQUF AAOBgQBosXif9feLXHBK19kqeVZ8uqRgoMIcM03aBTImjIO1RgwhRLuMrG2l+thA CT+fbYOYXJ4bHsn25XQjcSdG0uxsti3C2SnK83nKdulpEzBzj545rvH20QK+RtHN YUBEKvABCeqoIUu+ErMtGvryaQw7WQiQjWf+RTf8IXDGShIQwQ== server /certificate #
Command |
Description |
generate-csr (certificate) |
|
show certificate |
|