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 commands:
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 activate an adapter firmware image, use the activate-adapter-fw command.
activate-adapter-fw pci-slot image
pci-slot | The PCI slot number of the adapter card. |
image | The number of the firmware image to be activated. This can be the number 1 or 2. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to select one of two adapter firmware images to be activated upon the next reboot of the server. Use the show adapter detail command to view the status and version information of the installed firmware images.
This example shows how to activate firmware image 2 in the adapter in PCI slot 1:
Server# scope chassis Server /chassis # activate-adapter-fw 1 2 Firmware image activation succeeded Please reset the server to run the activated image Server /chassis #
Command |
Description |
show adapter detail |
|
To reset the adapter to default setting, use the adapter-reset-defaults command.
adapter-reset-defaults index
index | The PCI slot number of the adapter to be reset to factory default settings. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to restore factory default settings for the adapter at the PCI slot number specified by the index argument.
This example shows how to reset the adapter in PCI slot 1 to its default setting:
Server# scope chassis Server /chassis # adapter-reset-defaults 1 Factory default has been successfully restored. Server /chassis #
Command |
Description |
show adapter detail |
|
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 connect command.
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 exit command to exit the GNU bash shell.
This example shows how to connect to the server shell:
server# connect shell bash-3.2
Command |
Description |
exit |
|
To create a boot entry in the host Fibre Channel interface, use the create-boot-entry command.
create-boot-entry wwpn lun-id
wwpn | The World Wide Port Name (WWPN) for the boot target. |
lun-id | The LUN ID of the boot LUN. |
None
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to create boot entry. The range of the lun-id is 0 to 255. The wwpn for the boot target should be in the form hh:hh:hh:hh:hh:hh:hh:hh.
This example shows how to create a boot entry in the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc1 Server /chassis/adapter/host-fc-if # create-boot-entry 20:00:00:11:22:33:44:55 3 Server /chassis/adapter/host-fc-if *# commit New boot table entry will take effect upon the next server reset Server /chassis/adapter/host-fc-if #
Command |
Description |
delete boot |
|
To create a virtual Ethernet interface, use the create host-eth-if command.
create host-eth-if name
name | The name of the vNIC. |
None
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to create the virtual host Ethernet network interface card (vNIC). The name argument can be up to 32 ASCII characters.
This example shows how to create a vNIC:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # create host-eth-if Vnic5 Server /chassis/adapter/host-eth-if* # commit New host-eth-if settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if #
Command |
Description |
delete host-eth-if |
|
To delete a boot entry, use the delete boot command.
delete boot entry
entry | The boot table entry. |
None
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to delete the boot table entry at the specified position. The range of entry is 0 to 3. The change takes effect upon the next server reset.
This example shows how to delete a boot entry in the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc1 Server /chassis/adapter/host-fc-if # show boot Boot Table Entry Boot Target WWPN Boot LUN ID ----------------- -------------------------- ------------ 0 20:00:00:11:22:33:44:55 3 1 20:00:00:11:22:33:44:56 5 Server /chassis/adapter/host-fc-if # delete boot 1 Server /chassis/adapter/host-fc-if *# commit New host-fc-if settings will take effect upon the next server reset Server /chassis/adapter/host-fc-if # show boot Boot Table Entry Boot Target WWPN Boot LUN ID ----------------- -------------------------- ------------ 0 20:00:00:11:22:33:44:55 3 Server /chassis/adapter/host-fc-if #
Command |
Description |
create-boot-entry |
|
show-boot |
|
To delete an Ethernet interface, use the delete host-eth-if command.
delete host-eth-if name
name | The name of the vNIC. |
None
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to delete the specified virtual host Ethernet network interface card (vNIC). You cannot delete either of the two default vNICs, eth0 or eth1.
This example shows how to delete a vNIC:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # delete host-eth-if Vnic5 Server /chassis/adapter *# commit New host-eth-if settings will take effect upon the next server reset Server /chassis/adapter #
Command |
Description |
create host-eth-if |
|
To discard all configurations, use the discardcommand.
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 |
show pending |
|
To leave any command 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 command mode:
server /bios # exit server#
Command |
Description |
scope |
|
enter |
|
To export a CIMC configuration, use the export-config command.
export-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 filename 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, press 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 export the adapter vNIC configuration, use the export-vnic command.
export-vnic tftp-address path/name
tftp-address | The IP address of a remote TFTP server hosting the adapter configuration file. |
path/name | The absolute path to the file on the remote server along with the name of the adapter configuration file to be exported. |
None
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to export the adapter vNIC configuration. The adapter configuration file is stored at the specified path and filename on the TFTP server at the specified IP address.
This example shows how to export the adapter vNIC configuration:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # export-vnic 192.0.2.34 /backup/P81E.cfg Server /chassis/adapter #
Command |
Description |
import-vnic |
|
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, press 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 import the adapter vNIC configuration, use the import-vnic command.
import-vnic tftp-address path/name
tftp-address | The TFTP address of the server. |
path/name | The absolute path to the file on the remote server along with the name of the adapter configuration file to be imported. |
None
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to import the adapter vNIC configuration. The adapter downloads and installs the configuration from the specified path and filename on the TFTP server at the specified IP address.
This example shows how to import the adapter vNIC configuration:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # import-vnic 192.0.2.34 /backup/P81E.cfg Server /chassis/adapter #
Command |
Description |
export-vnic |
|
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 reapply command 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 rebuild the persistent binding table for the vHBA, use the rebuild command.
rebuild
This command has no arguments or keywords.
None
Persistent binding (/chassis/adapter/host-fc-if/perbi)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
Persistent binding must be enabled in the vHBA properties. |
This example shows how to rebuild the persistent binding table for the vHBA on interface fc0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope perbi Server /chassis/adapter/host-fc-if/perbi # rebuild Server /chassis/adapter/host-fc-if/perbi #
Command |
Description |
show trans-queue |
|
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:
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 clear an incomplete firmware update condition, use the recover-adapter-update command.
recover-adapter-update [pci-slot] [pci-slot]
pci-slot | The PCI slot number of the adapter card to be cleared. You can specify one or two adapters. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to clear the firmware update status if an adapter firmware update has failed or if the adapter status is stuck in the updating state when no update is in progress. This command clears the adapter firmware update status on one or two specified adapters or, if no adapter is specified, on all adapters.
Use the show adapter detail command to view the adapter firmware update status.
This example shows how to clear the adapter firmware update status on the adapters in PCI slots 3 and 4:
Server# scope chassis Server /chassis # recover-adapter-update 3 4 Server /chassis #
Command |
Description |
show adapter |
|
update-adapter-fw |
|
To enter the adapter command mode, use the scope adapter command.
scope adapter pci-slot
pci-slot | The PCI slot number of the adapter card. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to enter the command mode for the adapter card at the specified PCI slot.
This example shows how to enter the adapter command mode for the adapter card in PCI slot 1.
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter #
Command |
Description |
show adapter |
|
To enter the advanced BIOS command mode, use the scope advanced command.
scope advanced
This command has no arguments or keywords.
None
BIOS (/bios)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example enters the advanced BIOS command mode:
Server# scope bios Server /bios # scope advanced Server /bios/advanced #
Command |
Description |
show advanced |
|
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 command 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 the completion queue command mode of the host Ethernet interface, use the scope comp-queue command.
scope comp-queue
This command has no arguments or keywords.
None
Ethernet host interface (/chassis/adapter/host-eth-if)
VM FEX (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added in the VM FEX command mode. |
This example shows how to enter the completion queue command mode of the host Ethernet interface:
Server# scope chassis Server/chassis # scope adapter 1 Server/chassis/adapter # scope host-eth-if eth0 Server/chassis/adapter/host-eth-if # scope comp-queue Server/chassis/adapter/host-eth-if/comp-queue #
Command |
Description |
set cq-count |
|
To enter the Fibre Channel error recovery command mode, use the scope error-recovery command.
scope error-recovery
This command has no arguments or keywords.
None
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enter the error recovery command mode of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope error-recovery Server /chassis/adapter/host-fc-if/error-recovery #
Command |
Description |
set fcp-error-recovery |
|
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 command mode, use the scope firmware command.
scope firmware
This command has no arguments or keywords.
None
BIOS (/bios)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use firmware command mode to perform the following tasks:
This example shows how to enter firmware command mode:
server# scope bios server /bios # scope firmware server /bios/firmware #
Command |
Description |
show bios |
|
show firmware |
|
To enter the Cisco Flexible Flash controller command mode, use the scope flexflash command.
scope flexflash index
index | The name of the Cisco Flexible Flash controller. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.3(3) | This command was introduced. |
Use this command to enter the Cisco Flexible Flash controller command mode.
This example shows how to enter the Cisco Flexible Flash controller command mode for the first flash device :
Server# scope chassis Server /chassis # scope flexflash FlexFlash-0 Server /chassis/flexflash #
Command |
Description |
scope operational-profile |
|
To enter the host Ethernet interface command mode, use the scope host-eth-if command.
scope host-eth-if { eth0 | eth1 | name }
eth0 | Specifies vNIC 0. |
eth1 | Specifies vNIC 1. |
name | Specifies the name of the vNIC. |
None
Ethernet host interface (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enter the host Ethernet interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if #
Command |
Description |
scope host-fc-if |
|
To enter the host Fibre Channel interface command mode, use the scope host-fc-if command.
scope host-fc-if { fc0 | fc1 | name }
fc0 | Specifies vHBA fc0. |
fc1 | Specifies vHBA fc1. |
name | Specifies the name of a user-defined vHBA. |
None
Fibre Channel host nterface (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was modified to add the name variable. |
This example shows how to enter the command mode of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc1 Server /chassis/adapter/host-fc-if #
Command |
Description |
create host-fc-if |
|
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.
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 interrupt command mode, use the scope interrupt command.
scope interrupt
This command has no arguments or keywords.
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
Host Ethernet interface (/chassis/adapter/host-eth-if)
VM FEX (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added in the VM FEX command mode. |
This example shows how to enter the interrupt command mode of the host Ethernet interface:
Server # scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if Server /chassis/adapter/host-eth-if # scope interrupt Server /chassis/adapter/host-eth-if/interrupt #
Command |
Description |
set interrupt-count |
|
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 the main BIOS command mode, use the scope main command.
scope main
This command has no arguments or keywords.
None
BIOS (/bios)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example enters the main BIOS command mode:
Server# scope bios Server /bios # scope main Server /bios/main #
Command |
Description |
show main |
|
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 the TCP offload command mode, use the scope offload command.
scope offload
This command has no arguments or keywords.
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
Host Ethernet interface (/chassis/adapter/host-eth-if)
VM FEX (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added in the VM FEX command mode. |
This example shows how to enter the TCP offload command mode:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope offload Server /chassis/adapter/host-eth-if/offload #
Command |
Description |
set tcp-segment-offload |
|
To enter the Cisco Flexible Flash operational profile command mode, use the scope operational-profile command.
scope operational-profile
This command has no arguments or keywords.
None
FlexFlash (/chassis/flexflash)
Release | Modification |
---|---|
1.3(3) | This command was introduced. |
Use this command to enter the Cisco Flexible Flash operational profile command mode.
This example shows how to enter the Cisco Flexible Flash operational profile command mode for the first flash device:
Server# scope chassis Server /chassis # scope flexflash FlexFlash-0 Server /chassis/flexflash # scope operational-profile Server /chassis/flexflash/operational-profile #
Command |
Description |
set error-count-threshold |
|
set raid-primary-member |
|
set virtual-drives-enabled |
|
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:
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 the persistent LUN binding command mode for the vHBA, use the scope perbi command.
scope perbi
This command has no arguments or keywords.
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if )
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enter the persistent LUN binding command mode of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope perbi Server /chassis/adapter/host-fc-if/perbi #
Command |
Description |
set persistent-lun-binding enable |
|
To enter the physical drive command mode, use the scope physical-drive command.
scope physical-drive drive-number
drive-number | The drive number of the physical drive. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
You can use the physical-drive command mode to display general, inquiry, and status information about a physical drive.
This example shows how to enter the physical drive command mode for physical drive number 1 on the storage adapter named SAS:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # scope physical-drive 1 server /chassis/storageadapter/physical-drive #
Command |
Description |
show physical-drive |
|
To enter the Fibre Channel port command mode, use the scope port command.
scope port
This command has no arguments or keywords.
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enter the Fibre Channel port command mode.
Server # scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope port Server /chassis/adapter/host-fc-if/port #
Command |
Description |
set max-target-luns |
|
set outstanding-io-count |
|
scope port-f-logi
This command has no arguments or keywords.
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enter the Fibre Channel fabric login command mode:
Server # scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope port-f-logi Server /chassis/adapter/host-fc-if/port-f-logi #
Command |
Description |
set flogi-retries |
|
set flogi-timeout |
|
To enter the Fibre Channel port login command mode, use the scope port-p-logi command.
scope port-p-logi
This command has no arguments or keywords.
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enter the Fibre Channel port login command mode:
Server # scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope port-p-logi Server /chassis/adapter/host-fc-if/port-p-logi #
Command |
Description |
set plogi-retries |
|
set plogi-timeout |
|
To enter the receive queue command mode, use the scope recv-queue command.
scope recv-queue
This command has no arguments or keywords.
None
Host Ethernet interface (/chassis/adapter/host-eth-if )
Host Fibre Channel interface (/chassis/adapter/host-fc-if )
VM FEX (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added in the VM FEX command mode. |
This example shows how to enter the Fibre Channel receive queue command mode:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope recv-queue Server /chassis/adapter/host-fc-if/recv-queue #
Command |
Description |
set rq-count |
|
set rq-ring-size |
|
To enter the Receive-Side Scaling (RSS) command mode, use the scope rss command.
scope rss
This command has no arguments or keywords.
None
Ethernet host interface (/chassis/adapter/host-eth-if)
VM FEX (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added in the VM FEX command mode. |
This example shows how to enter the Receive-Side Scaling (RSS) command mode:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope rss Server /chassis/adapter/host-eth-if/rss #
Command |
Description |
set rss |
|
To enter the SCSI I/O command mode, use the scope scsi-io command.
scope scsi-io
This command has no arguments or keywords.
None
SCSI-IO (/chassis/adapter/host-fc-if/scsi-io)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enter the the SCSI I/O command mode:
Server # scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope scsi-io Server /chassis/adapter/host-fc-if/scsi-io #
Command |
Description |
set cdb-wq-count |
|
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 the server management BIOS command mode, use the scope server-management command.
scope server-management
This command has no arguments or keywords.
None
BIOS (/bios)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example enters the server management BIOS command mode:
Server# scope bios Server /bios # scope server-management Server /bios/server-management #
Command |
Description |
show server-management |
|
To enter the command mode for a remote syslog server profile, use the scope server command.
scope server { 1 | 2 }
1 | Selects remote syslog server profile number 1. |
2 | Selects remote syslog server profile number 2. |
None
CIMC log (/cimc/log)
Release | Modification |
---|---|
1.1(2) | This command was introduced. |
You can configure two remote syslog server profiles for sending CIMC log entries to different destinations. Use this command to select a profile and enter the command mode for that profile.
This example shows how to access and configure syslog server profile number 2:
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 the storageadapter command mode, use the scope storageadapter command.
scope storageadapter slot
slot | The PCI slot name or number of the storage adapter. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to enter storage adapter command mode for the adapter in slot 2:
Server# scope chassis Server /chassis # scope storageadapter SLOT-2 Server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
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 the transmit queue command mode, use the scope trans-queue command.
scope trans-queue
This command has no arguments or keywords.
None
Ethernet host interface (/chassis/adapter/host-eth-if )
Fibre Channel host interface (/chassis/adapter/host-fc-if )
VM FEX (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added in the VM FEX command mode. |
This example shows how to enter the Ethernet transmit queue command mode:
Server # scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope trans-queue Server /chassis/adapter/host-eth-if/trans-queue #
Command |
Description |
set wq-count |
|
set wq-ring-size |
|
To enter trap-destination command mode, use the scope trap-destination command.
scope trap-destination trap-destination-index
trap-destination-index | The index of a specific trap destination profile. |
None
Trap destination (/snmp/trap-destination)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.4(1) | This command was moved from the fault command mode to the snmp command mode. |
Use this command to access the four configurable trap destination profiles, identified by index numbers 1 through 4.
This example shows how to enter trap-destination mode:
Server# scope fault Server /snmp # scope trap-destination 4 Server /snmp/trap-destination #
Command |
Description |
set addr (trap-destination) |
|
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 the virtual drive command mode, use the scope virtual-drive command.
scope virtual-drive drive-number
drive-number | The drive number of the virtual drive. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to enter the virtual drive command mode for virtual drive number 1 on the storage adapter named SAS:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # scope virtual-drive 1 server /chassis/storageadapter/virtual-drive #
Command |
Description |
show virtual-drive |
|
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 send a test message to the SNMP trap destination, use the sendSNMPtrap command.
sendSNMPtrap
This command has no arguments or keywords.
None
SNMP trap destination (/snmp/trap-destination)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
1.4(1) | This command was moved from the fault scope to the snmp scope. |
Use this command to send an SNMPv1 test trap to the SNMP trap destination. The trap must be configured and enabled in order to send a test message.
This example sends a test message to SNMP trap destination 1:
Server# scope snmp Server /snmp # scope trap-destination 1 Server /snmp/trap-destination # sendSNMPtrap SNMP Test Trap sent to Destination:1 Server /snmp/trap-destination #
Command |
Description |
scope trap-destination |
|
To specify whether the BIOS publishes the ACPI 1.0 version, use the set ACPI10Support command.
set ACPI10Support { Disabled | Enabled }
Disabled | The ACPI 1.0 version is not published. |
Enabled | The ACPI 1.0 version is published. |
The ACPI 1.0 version is not published.
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify whether the BIOS publishes the Advanced Configuration and Power Interface (ACPI) 1.0 version of the fixed ACPI description table (FADT) in the Root System Description table. This version may be required for compatibility with OS versions that support only ACPI 1.0.
This example configures the BIOS to publish the ACPI 1.0 version and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set ACPI10Support Enabled Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
show server-management |
|
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:
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 an SNMP 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
SNMP trap destination (/snmp/trap-destination)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.4(1) | This command was moved from the fault scope to the snmp scope. |
This example shows how to assign an IP address to a trap destination index:
server# scope snmp server /snmp # scope trap-destination 3 server /snmp/trap-destination # set addr 209.165.200.225 server /snmp/trap-destination* # commit server /snmp/trap-destination #
Command |
Description |
show trap-destination |
|
To specify whether the processor uses the Intel Adjacent Cache Line Prefetch mechanism, use the set AdjacentCacheLinePrefetch command.
set AdjacentCacheLinePrefetch { Disabled | Enabled }
Disabled | The Adjacent Cache Line Prefetch mechanism is not used. |
Enabled | The Adjacent Cache Line Prefetch mechanism is used when cache issues are detected. |
The Adjacent Cache Line Prefetch mechanism is used when cache issues are detected.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify whether the processor uses the Intel Adjacent Cache Line Prefetch mechanism to fetch data when necessary.
You must select the Custom option in the set CPUPerformance command in order to specify this value. For any value other than Custom, this setting is overridden by the setting in the selected CPU performance profile.
This example specifies that the processor uses the Adjacent Cache Line Prefetch mechanism when necessary and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set CPUPerformance Custom Server /bios/advanced # set AdjacentCacheLinePrefetch Enable Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set CPUPerformance |
|
show advanced |
|
To specify the IP address of the secondary DNS server, use the set alternate-dns-server command.
set alternate-dns-server dns2-ipv4-address
dns2-ipv4-address | The IP address of the secondary DNS server. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example specifies the IP address of the secondary DNS server:
server# scope cimc server /cimc # scope network server /cimc/network # set alternate-dns-server 192.0.20.2 server /cimc/network* # commit server /cimc/network #
Command |
Description |
set preferred-dns-server |
|
show network |
|
To specify whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a processor bus parity error (PERR) occurs, use the set AssertNMIOnPERR command.
set AssertNMIOnPERR { Disabled | Enabled }
Disabled | The BIOS does not generate an NMI or log an error when a PERR occurs. |
Enabled | The BIOS generates an NMI and logs an error when a PERR occurs. |
Enabled
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
If you enable an NMI when a PERR occurs, you must also enable an NMI when a SERR occurs, using the set AssertNMIonSERR command. |
This example configures the BIOS to not generate an NMI or log an error when a PERR occurs, and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set AssertNMIOnPERR Disabled Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
set AssertNMIOnSERR |
|
show server-management |
|
To specify whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a system error (SERR) occurs, use the set AssertNMIOnSERR command.
set AssertNMIOnSERR { Disabled | Enabled }
Disabled | The BIOS does not generate an NMI or log an error when a SERR occurs. |
Enabled | The BIOS generates an NMI and logs an error when a SERR occurs. |
Enabled
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
If you enable an NMI when a PERR occurs, using the set AssertNMIonPERR command, you must also enable an NMI when a SERR occurs, using this command. |
This example configures the BIOS to not generate an NMI or log an error when a SERR occurs, and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set AssertNMIOnSERR Disabled Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
set AssertNMIOnPERR |
|
show server-management |
|
To specify whether the processor supports Intel VT-d Address Translation Services (ATS), use the set ATS command.
set ATS { Disabled | Enabled }
Disabled | The processor does not support ATS. |
Enabled | The processor uses VT-d ATS as required. |
The processor uses VT-d ATS as required.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the processor does not support ATS and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set ATS Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the LDAP attribute, use the set attribute command.
set attribute attribute-name
attribute-name | The name of the attribute. The name can be up to 64 characters. |
None
LDAP (/ldap)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to 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 an existing LDAP attribute that is mapped to the CIMC user roles and locales or you can create a custom attribute, such as the CiscoAVPair attribute, which has the following attribute ID: 1.3.6.1.4.1.9.287247.1
Note |
If you do not specify this property, user access is restricted to read-only. |
This example specifies the attribute as the CiscoAVPair attribute:
server# scope ldap server /ldap # set enabled yes server /ldap* # set attribute CiscoAVPair server /ldap* # commit server /ldap #
Command |
Description |
show ldap |
|
To specify the top level domain name of the LDAP hierarchy, use the set base-dn command.
set base-dn base-dn-name
base-dn-name | The name of the LDAP Base DN. The name can contain up to 63 characters. |
None
LDAP (/ldap)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example specifies the base-dn as cisco.com:
server# scope ldap server /ldap # set enabled yes server /ldap* # set base-dn cisco.com server /ldap* # commit server /ldap #
Command |
Description |
show ldap |
|
To specify the baud rate for serial over LAN (SoL) communications, use the set baud-rate command.
set baud-rate { 9.6k | 19.2k | 38.4k | 57.6k | 115.2k }
9.6k | The baud rate is 9600 bps. |
19.2k | The baud rate is 19200 bps. |
38.4k | The baud rate is 38400 bps. |
57.6k | The baud rate is 57600 bps. |
115.2k | The baud rate is 115200 bps. |
The baud rate is 115200 bps.
Serial over LAN (/sol)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Note |
This setting must match the setting on the remote terminal application. |
This example configures a baud rate of 57600 bps on the serial port and commits the transaction:
Server# scope sol Server /sol # set baud-rate 57.6k Server /sol *# set enabled yes Server /sol *# commit Server /sol #
Command |
Description |
show sol |
|
To specify the baud rate for serial port communications, use the set BaudRate command.
set BaudRate { 9.6k | 19.2k | 38.4k | 57.6k | 115.2k }
9.6k | The baud rate is 9600 bps. |
19.2k | The baud rate is 19200 bps. |
38.4k | The baud rate is 38400 bps. |
57.6k | The baud rate is 57600 bps. |
115.2k | The baud rate is 115200 bps. |
The baud rate is 9600 bps.
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify the baud rate for serial port communications. If you disable Console Redirection, this option is not available.
Note |
This setting must match the setting on the remote terminal application. |
This example configures a baud rate of 115200 bps on the serial port and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set BaudRate 115.2k Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
show server-management |
|
To specify whether the system automatically detects the BMC in ACPI-compliant operating systems, use the set BMCPnP command.
set BMCPnP { Disabled | Enabled }
Disabled | The system never automatically detects the BMC. |
Enabled | The system automatically detects the BMC whenever possible. |
Disabled
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example configures the BIOS to automatically detect the BMC whenever possible and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set BMCPnP Enabled Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
show server-management |
|
To enable or disable remote boot for an adapter interface, use the set boot command.
set boot { disable | enable }
disable | Disables remote boot. |
enable | Enables remote boot. |
Remote boot is disabled for default vHBAs and user-created vNICs, and enabled for default vNICs.
Ethernet host interface (/chassis/adapter/host-eth-if)
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to specify whether a vNIC can boot from PXE or whether a vHBA can boot from SAN.
This example shows how to enable SAN boot for the host Fibre Channel interface fc0:
Server# scope chassis Server/chassis # scope adapter 1 Server/chassis/adapter # scope host-fc-if fc0 Server/chassis/adapter/host-fc-if # set boot enable Server/chassis/adapter/host-fc-if *# commit Server/chassis/adapter/host-fc-if #
Command |
Description |
create-boot-entry |
|
To set the boot order for the server, use the set boot-order command in BIOS mode.
set boot-order boot-list
boot-list | A comma-separated list of boot devices. |
None
BIOS (/bios)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
For the boot-list argument, type the boot devices in the desired boot order using commas as delimiters, with no spaces between devices. The device names are not case sensitive. Use one or more of the following boot device arguments:
Installed boot devices not listed in this command will be appended to the boot order. If a listed device is not present, it will be removed from the boot order configuration.
Do not disable boot options in the BIOS menus.
This example shows how to specify 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 specify whether the BIOS retries NON-EFI based boot options without waiting for user input, use the set BootOptionRetry command.
set BootOptionRetry { Disabled | Enabled }
Disabled | The BIOS waits for user input before retrying NON-EFI based boot options. |
Enabled | The BIOS continually retries NON-EFI based boot options without waiting for user input. |
The BIOS waits for user input before retrying NON-EFI based boot options.
Main BIOS (/bios/main)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example configures the BIOS to continually retry NON-EFI based boot options without waiting for user input and commits the transaction:
Server# scope bios Server /bios # scope main Server /bios/main # set BootOptionRetry Enabled Server /bios/main *# commit Server /bios/main *# show detail Set-up parameters: Boot option retry: Enabled POST Error Pause: Disabled Server /bios/main #
Command |
Description |
scope main |
|
show main |
|
To specify a device that will override the default boot priority the next time the server boots, use the set boot-override command.
set boot-override { None | SCU | HV | HUU }
None | The server uses the default boot order. |
SCU | The server boots from the Cisco UCS-Server Configuration Utility. |
HV | The server boots from the VMware Hypervisor. |
HUU | The server boots from the Cisco Host Upgrade Utility. |
None
BIOS (/bios)
Release | Modification |
---|---|
1.3(3) | This command was introduced. |
Use this command to specify a device that will override the default boot priority the next time the server is restarted, regardless of the default boot order defined for the server. The specified device is used only once. After the server has rebooted, this option is ignored. The available devices are virtual drives on the Cisco Flexible Flash card.
Note |
This function is available only on platforms that support the Cisco Flexible Flash controller. Before you reboot the server, ensure that the device you select is enabled on the Cisco Flexible Flash card. |
This example shows how to specify that the server boots from the Cisco UCS-Server Configuration Utility:
server# scope bios server /bios # set boot-override SCU server /bios* # commit server /bios #
Command |
Description |
show bios |
|
To set the number of command descriptor block (CDB) transmit queue resources to allocate, use the set cdb-wq-count command.
set cdb-wq-count count
count | The number of command descriptor block (CDB) transmit queue resources to allocate. The range is 1 to 8. The default count is 1. |
The default count is 1.
SCSI-IO (/chassis/adapter/host-fc-if/scsi-io )
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the command descriptor block (CDB) transmit queue resources of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 server /chassis/adapter/host-fc-if # scope scsi-io Server /chassis/adapter/host-fc-if/scsi-io # set cdb-wq-count 4 Server /chassis/adapter/host-fc-if/scsi-io *# commit Server /chassis/adapter/host-fc-if/scsi-io #
Command |
Description |
set cdb-wq-ring-size |
|
To set the number of descriptors in the command descriptor block (CDB) transmit queue, use the set cdb-wq-ring-size command.
set cdb-wq-ring-size size
size | The number of descriptors in the command descriptor block (CDB) transmit queue. The range is 64 to 512. |
The default descriptor number is 512.
SCSI-IO (/chassis/adapter/host-fc-if/scsi-io )
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the number of descriptors in the command descriptor block (CDB) transmit queue:
Server # scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope scsi-io Server /chassis/adapter/host-fc-if/scsi-io # set cdb-wq-ring-size 78 Server /chassis/adapter/host-fc-if/scsi-io *# commit Server /chassis/adapter/host-fc-if/scsi-io #
Command |
Description |
set cdb-wq-count |
|
To specify the Network Interface Virtualization (NIV) channel number, use the set channel-number command.
set channel-number number
number | The NIV channel number. Specify a number between 1 and 1000. |
None
Ethernet host interface (/chassis/adapter/host-eth-if)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
To use this command, you must enable NIV mode for the adapter. |
This example shows how to set the NIV channel number on interface eth0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # set niv-mode enabled Server /chassis/adapter *# scope host-eth-if eth0 Server /chassis/adapter/host-eth-if *# set channel-number 5 Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
set niv-mode |
|
show host-eth-if |
|
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 (YAML Ain't 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 the time to wait between interrupts or the idle period that must be encountered before an interrupt is sent, use the set coalescing-time command.
set coalescing-time usec
usec | The time to wait between interrupts or the idle period that must be countered before an interrupt is sent. The range is 1 to 65535 microseconds; the default is 125. To turn off coalescing enter 0 (zero). |
The default is 125.
Interrupt (/chassis/adapter/host-eth-if/interrupt)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the coalescing time:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope interrupt Server /chassis/adapter/host-eth-if/interrupt # set coalescing-time 65 Server /chassis/adapter/host-eth-if/interrupt *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset
Command |
Description |
set coalescing-type |
|
To set the coalescing type of the host Ethernet interface, use the set coalescing-type command.
set coalescing-type { idle | min }
idle | The system does not send an interrupt until there is a period of no activity lasting as least as long as the time specified in the coalescing time configuration. |
min | The system waits for the time specified in the coalescing time configuration before sending another interrupt event. |
The default is min.
Interrupt (/chassis/adapter/host-eth-if/interrupt)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the coalescing type:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Srver /chassis/adapter/host-eth-if scope interrupt Server /chassis/adapter/host-eth-if/interrupt # set coalescing-type idle Server /chassis/adapter/host-eth-if/interrupt *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/interrupt #
Command |
Description |
set coalescing-time |
|
To specify whether the processor supports Intel VT-d Coherency, use the set CoherencySupport command.
set CoherencySupport { Disabled | Enabled }
Disabled | The processor does not support coherency. |
Enabled | The processor uses Intel VT-d Coherency as required. |
The processor does not support Intel VT-d Coherency.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the processor supports VT-d Coherency and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set CoherencySupport Enabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the SNMP community name, use the set community-str command.
set community-str community
community | The SNMP v1 or v2c community name or SNMP v3 username. |
None
SNMP (/snmp)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
1.4(1) | This command was moved from the fault command mode. |
Use this command to specify the SNMP v1 or v2c community name or SNMP v3 username that CIMC includes on any trap messages it sends to the SNMP host. The name can be up to 18 characters.
SNMP must be enabled and saved before this command can be accepted.
This example configures the SNMP parameters and commits the transaction:
Server# scope snmp Server /snmp # set enabled yes Server /snmp *# commit Server /snmp # set community-str cimcpublic Server /snmp *# set sys-contact "User Name <username@example.com> +1-408-555-1212" Server /snmp *# set sys-location "San Jose, California" Server /snmp *# commit Server /snmp # show detail SNMP Settings: SNMP Port: 161 System Contact: User Name <username@example.com> +1-408-555-1212 System Location: San Jose, California SNMP Community: cimcpublic SNMP Trap community: 0 Enabled: yes SNMP Trap Version: 1 SNMP Inform Type: inform Server /snmp #
Command |
Description |
show snmp |
|
To specify the mode in which the SATA controller runs, use the set ConfigSATAMode command.
set ConfigSATAMode { AHCI | Compatibility | Enhanced | S/W_RAID }
AHCI | The controller enables the Advanced Host Controller Interface (AHCI) and disables RAID. |
Compatibility | The controller disables both AHCI and RAID and runs in IDE emulation mode. |
Enhanced | The controller enables both AHCI and RAID. |
S/W_RAID | The controller enables RAID and disables the AHCI. |
The controller enables both AHCI and RAID.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
This command is not available on all models and configurations. |
This example specifies that the controller disables both AHCI and RAID and runs in IDE emulation mode and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set ConfigSATAMode Compatibility Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To allow a serial port to be used for console redirection during POST and BIOS booting, use the set ConsoleRedir command.
set ConsoleRedir { Disabled | Serial_Port_A }
Disabled | No console redirection occurs during POST. |
Serial_Port_A | Enables serial port A for console redirection during POST. This option is valid for blade servers and rack-mount servers. |
Disabled
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to allow a serial port to be used for console redirection during POST and BIOS booting. After the BIOS has booted and the operating system is responsible for the server, console redirection is irrelevant and has no effect.
Note |
By enabling this option, you also disable the display of the Quiet Boot logo screen during POST. |
This example configures the BIOS to allow serial port A to be used for console redirection during POST and BIOS booting and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set ConsoleRedir Serial_Port_A Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
show server-management |
|
To set the state of logical processor cores in a package, use the set CoreMultiProcessing command.
set CoreMultiProcessing { All | number }
All | Enables multi processing on all logical processor cores. |
number | The number of logical processor cores that can run on the server. |
Multi processing is enabled on all logical processor cores.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
To disable multi processing and have only one logical processor core running on the server, set number to 1. When only one logical processor core is running on the server, Hyper Threading is also disabled.
Note |
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
This example specifies that two processor cores can be run on the server and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set CoreMultiProcessing 2 Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the CoS value to be marked by an interface, use the set cos command.
set cos cos-value
cos-value | Specifies a CoS value to be marked. |
None
Ethernet host interface (/chassis/adapter/host-eth-if)
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to specify the class of service (CoS) to be marked on received packets unless the interface is configured to trust host CoS. Valid CoS values are 0 to 6; the default is 0. Higher values indicate more important traffic.
This example shows how to specify a CoS value of 5 for the Ethernet host interface eth0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # set cos 5 Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
set trust-host-cos |
|
To set the CPU performance profile for the server, use the set CPUPerformance command.
set CPUPerformance { Custom | Enterprise | HPC | High_Throughput }
Custom | All performance profile options can be configured from the BIOS setup on the server. |
Enterprise | Only the DCU IP Prefetcher is enabled. All other options are disabled. |
HPC | Data Reuse Optimization is disabled and all other options are enabled. This setting is also known as high performance computing (HPC). |
High_Throughput | All options are enabled. |
The processor classifies memory areas.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
When the Custom option is selected, you can also configure the Hardware Prefetcher and Adjacent Cache-Line Prefetch options using the set HardwarePrefetch and set AdjacentCacheLinePrefetch commands.
This example specifies that the processor uses the Custom performance profile and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set CPUPerformance Custom Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To set the number of completion queue resources to allocate, use the set cq-count command.
set cq-count count
count | The number of completion queue resources to allocate. The range is 1 to 512. |
The default count is 5.
Completion queue (/chassis/adapter/host-eth-if/comp-queue)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
In general, the number of completion queues equals the number of transmit queues plus the number of receive queues.
This example shows how to set the number of completion queue resources to allocate:
Server # scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope comp-queue Server /chassis/adapter/host-eth-if/comp-queue # set cq-count 59 Server /chassis/adapter/host-eth-if/comp-queue *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/comp-queue #
Command |
Description |
show comp-queue |
|
To specify whether server power is restored after a fixed or random time, use the set delay command.
set delay { fixed | random }
fixed | Server power is restored after a fixed time. |
random | Server power is restored after a random time. |
Server power is restored after a fixed time.
Chassis (/chassis)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify whether server power is restored after a fixed or random time after an outage.
When the selected action is fixed, the delay time is configured by the set delay-value command.
This example sets the power restore policy to power-on with a fixed delay of 180 seconds (3 minutes) and commits the transaction:
Server# scope chassis Server /chassis # set policy power-on Server /chassis *# set delay fixed Server /chassis *# set delay-value 180 Server /chassis *# commit Server /chassis # show detail Chassis: Power: on Serial Number: QCI1404A1IT Product Name: UCS C200 M1 PID : R200-1120402 UUID: 01A6E738-D8FE-DE11-76AE-8843E138AE04 Locator LED: off Description: Testing power restore Power Restore Policy: power-on Power Delay Type: fixed Power Delay Value(sec): 180 Server /chassis #
Command |
Description |
set policy |
|
set delay-value |
|
To specify the delay time for restoring server power after an outage, use the set delay-value command.
set delay-value delay
delay | The delay time in seconds. |
The default delay is 0 seconds.
Chassis (/chassis)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify the delay time in seconds for restoring server power after an outage. The range is 0 to 240; the default is 0.
This command is operative only when the power restore policy is power-on with a fixed delay.
This example sets the power restore policy to power-on with a fixed delay of 180 seconds (3 minutes) and commits the transaction:
Server# scope chassis Server /chassis # set policy power-on Server /chassis *# set delay fixed Server /chassis *# set delay-value 180 Server /chassis *# commit Server /chassis # show detail Chassis: Power: on Serial Number: QCI1404A1IT Product Name: UCS C200 M1 PID : R200-1120402 UUID: 01A6E738-D8FE-DE11-76AE-8843E138AE04 Locator LED: off Description: Testing power restore Power Restore Policy: power-on Power Delay Type: fixed Power Delay Value(sec): 180 Server /chassis #
Command |
Description |
set policy |
|
set delay |
|
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 specify whether the CIMC uses DHCP to obtain an IP address, use the set dhcp-enabled command.
set dhcp-enabled { no | yes }
no | The CIMC does not use DHCP to obtain an IP address. |
yes | The CIMC uses DHCP to obtain an IP address. |
The CIMC does not use DHCP to obtain an IP address.
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Note |
If DHCP is enabled, we recommend that the DHCP server be configured to reserve a single IP address for the CIMC. If the CIMC is reachable through multiple ports on the server, the single IP address must be reserved for the full range of MAC addresses of those ports. |
This example specifies that the CIMC uses DHCP to obtain an IP address:
server# scope cimc server /cimc # scope network server /cimc/network # set dhcp-enabled yes server /cimc/network* # commit server /cimc/network #
Command |
Description |
show network |
|
To specify whether the processor can increase I/O performance by placing data from I/O devices directly into the processor cache, use the set DirectCacheAccess command.
set DirectCacheAccess { Disabled | Enabled }
Disabled | Data from I/O devices is not placed directly into the processor cache. |
Enabled | Data from I/O devices is placed directly into the processor cache. |
Data from I/O devices is placed directly into the processor cache.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the processor does not place data from I/O devices directly into the processor cache and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set DirectCacheAccess Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify whether the CIMC uses DHCP to obtain DNS server addresses, use the set dns-use-dhcp command.
set dns-use-dhcp { no | yes }
no | The CIMC does not use DHCP to obtain DNS server addresses. |
yes | The CIMC uses DHCP to obtain DNS server addresses. |
The CIMC does not use DHCP to obtain DNS server addresses.
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Note |
If DHCP is enabled, we recommend that the DHCP server be configured to reserve a single IP address for the CIMC. If the CIMC is reachable through multiple ports on the server, the single IP address must be reserved for the full range of MAC addresses of those ports. |
This example specifies that the CIMC uses DHCP to obtain DNS server addresses:
server# scope cimc server /cimc # scope network server /cimc/network # set dns-use-dhcp yes server /cimc/network* # commit server /cimc/network #
Command |
Description |
show network |
|
To enable or disable functions and actions on the server, use the set enabled command.
set enabled { no | yes }
no | Disables the function or action. |
yes | Enables the function or action. |
See the Usage Guidelines.
CIMC log server (/cimc/log/server)
HTTP (/http)
IP blocking (/cimc/chassis/ipblocking)
IPMI (/ipmi)
Keyboard Video Mouse (/kvm)
LDAP (/ldap)
Secure shell (/ssh)
Serial over LAN (/sol)
Trap destination (/fault/trap-destination)
User (/user)
Virtual media (/vmedia)
XML API (/xmlapi)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.1(2) | This command was introduced for the CIMC log server command mode. |
1.4(1) | This command was introduced for the XML API command mode. |
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 |
|
To enable or disable the encryption of information, use the set encrypted command.
set encrypted { no | | yes }
no | Information is not encrypted. |
yes | Information is encrypted. |
Video information sent through the KVM is not encrypted.
The Active Directory is not encrypted.
Virtual media data is not encrypted.
KVM (/kvm)
LDAP (/ldap)
Virtual media (/vmedia)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example enables the encryption of video information sent through the KVM:
server# scope kvm server /kvm # set enabled yes server /kvm* # set encrypted yes server /kvm* # commit server /kvm #
Command |
Description |
show kvm |
|
show ldap |
|
show vmedia |
|
To specify the encryption key for IPMI communications, use the set encryption-key command.
set encryption-key encryption-key
encryption-key | The encryption key for IPMI communications. The key value must be 40 hexadecimal numbers. |
None
IPMI (/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 enabled yes 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 specify whether the processor uses Enhanced Intel SpeedStep Technology, use the set EnhancedIntelSpeedStep command.
set EnhancedIntelSpeedStep { Disabled | Enabled }
Disabled | The processor never dynamically adjusts its voltage or frequency. |
Enabled | The processor uses Enhanced Intel SpeedStep Technology if required. |
The processor uses Enhanced Intel SpeedStep Technology if required.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Enhanced Intel SpeedStep Technology allows the system to dynamically adjust the processor voltage and core frequency. This technology can result in decreased average power consumption and decreased average heat production.
Note |
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
This example specifies that the processor never dynamically adjusts its voltage or frequency and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set EnhancedIntelSpeedStep Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the number of errors that can occur before CIMC decides that the Cisco Flexible Flash card has failed, use the set error-count-threshold command.
set error-count-threshold count
count | Enter a number between 0 and 255. |
FlexFlash operational profile (/chassis/flexflash/operational-profile)
Release | Modification |
---|---|
1.3(3) | This command was introduced. |
Use this command to specify the number of errors that can occur before CIMC decides that the Cisco Flexible Flash card has failed. Once this threshold has been reached, you must reset the Cisco Flexible Flash card before CIMC attempts to access it again.
Enter an integer between 1 and 255, or enter 0 (zero) if you want CIMC to continue using the card no matter how many errors it encounters.
This example shows how to set the error count threshold to 100 for the first flash device:
Server# scope chassis Server /chassis # scope flexflash FlexFlash-0 Server /chassis/flexflash # scope operational-profile Server /chassis/flexflash/operational-profile # set error-count-threshold 100 Server /chassis/flexflash/operational-profile *# commit Server /chassis/flexflash/operational-profile #
Command |
Description |
scope operational-profile |
|
To set the error detection timeout value (EDTOV), use the set error-detect-timeout command.
set error-detect-timeout msec
msec | Specifies the error detect timeout value (EDTOV), the number of milliseconds to wait before the system assumes that an error has occurred. The range is 1000 to 100000; the default is 2000 milliseconds. |
The default is 2000 milliseconds.
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the error detection timeout value to 5000 milliseconds:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # set error-detect-timeout 5000 Server /chassis/adapter/host-fc-if *# commit Server /chassis/adapter/host-fc-if #
Command |
Description |
set resource-allocation-timeout |
|
To classify memory areas on the server to specify where application code can execute, use the set ExecuteDisable command.
set ExecuteDisable { Disabled | Enabled }
Disabled | The processor does not classify memory areas. |
Enabled | The processor classifies memory areas. |
The processor classifies memory areas.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
By using memory classification, the processor disables code execution if a malicious worm attempts to insert code in the buffer. This setting helps to prevent damage, worm propagation, and certain classes of malicious buffer overflow attacks.
Note |
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
This example specifies that the processor does not classify memory and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set ExecuteDisable Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify a limit on the number of unsuccessful login attempts, use the set fail-count command.
set fail-count fail-count
fail-count | The number of times a user can attempt to log in unsuccessfully before the system locks that user out for a specified length of time. The range of valid values is 3 to 10. |
The default failure count is 5 attempts.
IP blocking (/cimc/network/ipblocking)
Release | Modification |
---|---|
1.0(1X) | This command was introduced. |
The number of unsuccessful login attempts must occur within the time frame specified in the IP Blocking Fail Window setting.
This example sets the IP blocking failure count to 3 attempts:
server# scope cimc server /cimc # scope network server /cimc/network # scope ipblocking server /cimc/network/ipblocking # set enable yes server /cimc/network/ipblocking* # set fail-count 3 server /cimc/network/ipblocking* # commit server /cimc/network/ipblocking #
Command |
Description |
set fail-window |
|
show ipblocking |
|
To specify a time window for unsuccessful login attempts, use the set fail-window command.
set fail-window fail-window
fail-window | The length of time, in seconds, in which the unsuccessful login attempts must occur in order for the user to be locked out. The range of valid values is 60 to 120. |
The default failure window is 60 seconds.
IP blocking (/cimc/network/ipblocking)
Release | Modification |
---|---|
1.0(1X) | This command was introduced. |
This example sets the IP blocking failure window to 90 seconds:
server# scope cimc server /cimc # scope network server /cimc/network # scope ipblocking server /cimc/network/ipblocking # set enable yes server /cimc/network/ipblocking* # set fail-window 90 server /cimc/network/ipblocking* # commit server /cimc/network/ipblocking #
Command |
Description |
set fail-count |
|
show ipblocking |
|
To specify the receive queue ring size for the Fibre Channel interface, use the set fc-rq-ring-size command.
set fc-rq-ring-size size
size | The Fibre Channel receive queue ring size. Specify a number between 64 and 128. |
The receive queue ring size is 64.
Fibre Channel receive queue (/chassis/adapter/host-fc-if/recv-queue)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to set the receive queue ring size to 128 on interface fc0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope recv-queue Server /chassis/adapter/host-fc-if/recv-queue # set fc-rq-ring-size 128 Server /chassis/adapter/host-fc-if/recv-queue *# commit Server /chassis/adapter/host-fc-if/recv-queue #
Command |
Description |
show recv-queue |
|
To specify the transmit queue ring size for the Fibre Channel interface, use the set fc-wq-ring-size command.
set fc-wq-ring-size size
size | The Fibre Channel transmit queue ring size. Specify a number between 64 and 128. |
The transmit queue ring size is 64.
Fibre Channel transmit queue (/chassis/adapter/host-fc-if/trans-queue)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to set the transmit queue ring size to 128 on interface fc0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope trans-queue Server /chassis/adapter/host-fc-if/trans-queue # set fc-wq-ring-size 128 Server /chassis/adapter/host-fc-if/trans-queue *# commit Server /chassis/adapter/host-fc-if/trans-queue #
Command |
Description |
show trans-queue |
|
To set the FCP Error Recovery, use the set fcp-error-recovery command.
set fcp-error-recovery { disable | enable }
disable | Disables FCP Error Recovery. |
enable | Enables FCP Error Recovery. |
The default is disable.
Error-recovery (/chassis/adapter/host-fc-if/error-recovery)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the FCP-error recovery:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope error-recovery Server /chassis/adapter/host-fc-if/error-recovery # set fcp-error-recovery enable Server /chassis/adapter/host-fc-if/error-recovery *# commit Committed host-fc-if fc0 settings will take effect upon the next server reset Server /chassis/adapter/host-fc-if/error-recovery #
Command |
Description |
set link-down-timeout |
|
set port-down-io-retry-count |
|
To enable or disable FCoE Initialization Protocol (FIP) on the adapter card, use the set fip-mode command.
set fip-mode { disabled | enabled }
disabled | Disables FIP mode on the card. |
enabled | Enables FIP mode on the card. |
FIP mode is enabled.
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Note |
Note: We recommend that you disable this option only when explicitly directed to do so by a technical support representative. |
This example shows how to enable FIP mode on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # set fip-mode enabled Server /chassis/adapter *# commit Server /chassis/adapter #
Command |
Description |
show adapter detail |
|
To specify the fabric login (FLOGI) retries value, use the set flogi-retries command.
set flogi-retries { infinite | count }
infinite | Specifies infinite FLOGI retries. |
count | Specifies the number of FLOGI retries. Enter a number between 0 and 4294967295. |
The default is infinite retries.
Port-f-logi (/chassis/adapter/host-fc-if/port-f-logi)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the fabric login retries:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope port-f-logi Server /chassis/adapter/host-fc-if/port-f-logi # set flogi-retries 4294967295 Server /chassis/adapter/host-fc-if/port-f-logi *# commit Server /chassis/adapter/host-fc-if/port-f-logi #
Command |
Description |
set flogi-timeout |
|
To set the fabric login (FLOGI) timeout value, use the set flogi-timeout command.
set flogi-timeout msec
msec | The number of milliseconds that the system waits before it tries to log in again. The range is 1 to 255000. |
The default msec value is 2000 milliseconds.
Port-f-logi (/chassis/adapter/host-fc-if/port-f-logi)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the fabric login timeout:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope port-f-logi Server /chassis/adapter/host-fc-if/port-f-logi # set flogi-timeout 10003 Server /chassis/adapter/host-fc-if/port-f-logi *# commit Server /chassis/adapter/host-fc-if/port-f-logi #
Command |
Description |
set flogi-retries |
|
To specify whether a handshake protocol is used for flow control, use the set FlowCtrl command.
set FlowCtrl { None | RTS-CTS }
None | No flow control is used. |
RTS-CTS | RTS/CTS is used for flow control. |
No flow control is used.
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify whether a handshake protocol is used for flow control. Request to Send / Clear to Send (RTS/CTS) helps to reduce frame collisions that can be introduced by a hidden terminal problem.
Note |
This setting must match the setting on the remote terminal application. |
This example configures the BIOS to use RTS/CTS protocol for flow control and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set FlowCtrl RTS-CTS Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
show server-management |
|
To specify whether the FRB2 timer is used by CIMC to recover the system if it halts during POST, use the set FRB-2 command.
set FRB-2 { Disabled | Enabled }
Disabled | The FRB2 timer is not used. |
Enabled | The FRB2 timer is started during POST and used to recover the system if necessary. |
The FRB2 timer is started during POST and used to recover the system if necessary.
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify whether the Fault Resilient Booting (FRB) level 2 timer is used by CIMC to recover the system from a watchdog timeout during power-on self test (POST).
This example configures the BIOS to not use the FRB2 timer to recover if a watchdog timeout occurs during POST, and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set FRB-2 Disabled Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
show server-management |
|
To specify whether the processor uses the Intel hardware prefetcher, use the set HardwarePrefetch command.
set HardwarePrefetch { Disabled | Enabled }
Disabled | The hardware prefetcher is not used. |
Enabled | The hardware prefetcher is used when cache issues are detected. |
The hardware prefetcher is used when cache issues are detected.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify whether the processor uses the Intel hardware prefetcher to fetch streams of data and instruction from memory into the unified second-level cache when necessary.
You must select the Custom option in the set CPUPerformance command in order to specify this value. For any value other than Custom, this setting is overridden by the setting in the selected CPU performance profile.
This example specifies that the processor uses the hardware prefetcher when necessary and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set CPUPerformance Custom Server /bios/advanced # set HardwarePrefetch Enable Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set CPUPerformance |
|
show advanced |
|
To specify the host name of the server, use the set hostname command.
set hostname host-name
host-name | The host name of the server. The host name can contain up to 63 characters, and will be used as the CLI prompt. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example sets the host name of the server to SanJose:
server# scope cimc server /cimc # scope network server /cimc/network # set hostname SanJose server /cimc/network* # commit SanJose /cimc/network #
Command |
Description |
show network |
|
To set the port number for Hyper Text Transfer Protocol (HTTP) services on the server, use the set http-port command.
set http-port port-number
port-number | The HTTP port number of the server. The range of valid values is 1 to 65536. |
The default HTTP port number is 80.
HTTP (/http)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to set the HTTP port number to 8080:
Server# scope http Server /http # set http-port 8080 Server /http* # commit Server /http #
Command |
Description |
show http-port |
|
show https-port |
|
To set the port number for Hyper Text Transfer Protocol (HTTPS) services on the server, use the set https-port command in http mode.
set https-port port-number
port-number | The HTTPS port number of the server. The range of valid values is 1 to 65536. |
The default port number is 443.
HTTP (/http)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example shows how to set the HTTPS port number:
server# scope http server /http # set https-port 443 server /http* # commit server /http #
Command |
Description |
|
|
|
|
To specify whether the processor uses Intel Hyper-Threading Technology, use the set IntelHyperThread command.
set IntelHyperThread { Disabled | Enabled }
Disabled | The processor does not permit hyperthreading. |
Enabled | The processor allows for the parallel execution of multiple threads. |
The processor allows for the parallel execution of multiple threads.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Intel Hyper-Threading Technology allows multithreaded software applications to execute threads in parallel within each processor.
Note |
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
This example specifies that the processor does not permit hyperthreading and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set IntelHyperThread Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify whether the processor uses Intel Turbo Boost Technology, use the set IntelTurboBoostTech command.
set IntelTurboBoostTech { Disabled | Enabled }
Disabled | The processor does not automatically increase its frequency. |
Enabled | The processor uses Intel Turbo Boost Technology if required. |
The processor uses Intel Turbo Boost Technology if required.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Intel Turbo Boost Technology allows the processor to automatically increase its frequency if it is running below power, temperature, or voltage specifications.
This example specifies that Intel Turbo Boost Technology is not used and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set IntelTurboBoostTech Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify whether the processor uses Intel Virtualization Technology, use the set IntelVT command.
set IntelVT { Disabled | Enabled }
Disabled | The processor does not permit virtualization. |
Enabled | The processor allows virtualization. |
The processor allows virtualization.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify whether the processor uses Intel Virtualization Technology (VT), which allows a platform to run multiple operating systems and applications in independent partitions.
Note |
If you change this option, you must power cycle the server before the setting takes effect. |
This example specifies that the processor does not permit virtualization and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set IntelVT Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify whether the processor uses Intel Virtualization Technology for Directed I/O (VT-d), use the set IntelVTD command.
set IntelVTD { Disabled | Enabled }
Disabled | The processor does not use virtualization technology for directed I/O. |
Enabled | The processor uses virtualization technology for directed I/O. |
The processor uses virtualization technology for directed I/O.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the processor does not use virtualization technology for directed I/O and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set IntelVTD Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the number of interrupt resources, use the set interrupt-count command.
set interrupt-count count
count | The number of interrupt resources. The range is 1 to 514. |
The default is 8.
Interrupt (/chassis/adapter/host-eth-if/interrupt)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the interrupt count:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope interrupt Server /chassis/adapter/host-eth-if/interrupt # set interrupt-count 10 Server /chassis/adapter/host-eth-if/interrupt *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/interrupt #
Command |
Description |
set coalescing-time |
|
set coalescing-type |
|
To set the Ethernet interrupt mode, use the set interrupt-mode command.
set interrupt-mode { intx | msi | msix }
intx | Line-based interrupt (PCI INTx). |
msi | Message-Signaled Interrupt (MSI). |
msix | Message Signaled Interrupts with the optional extension (MSI-X). This is the recommended and default option. |
The default option is msix.
Interrupt (/chassis/adapter/host-eth-if/interrupt)
Interrupt (/chassis/adapter/host-fc-if/interrupt)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the interrupt mode:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if/ # scope interrupt Server /chassis/adapter/host-eth-if/interrupt # set interrupt-mode msix Server /chassis/adapter/host-eth-if/interrupt *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/interrupt #
Command |
Description |
set interrupt-count |
|
To specify whether the processor supports Intel VT-d Interrupt Remapping, use the set InterruptRemap command.
set InterruptRemap { Disabled | Enabled }
Disabled | The processor does not support remapping. |
Enabled | The processor uses VT-d Interrupt Remapping as required. |
The processor uses VT-d Interrupt Remapping as required.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the processor does not use remapping and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set InterruptRemap Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the port used for KVM communication, use the set kvm-port command.
set kvm-port port-number
port-number | The port used for KVM communication. |
Port number 2068 is used for KVM communication.
KVM (/kvm)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example specifies that port number 2068 is used for KVM communication:
server# scope kvm server /kvm # set enabled yes server /kvm* # set kvm-port 2068 server /kvm* # commit server /kvm #
Command |
Description |
show kvm |
|
To specify whether redirection from a legacy operating system, such as DOS, is enabled on the serial port, use the set LegacyOSRedir command.
set LegacyOSRedir { Disabled | Enabled }
Disabled | The serial port enabled for console redirection is hidden from the legacy operating system. |
Enabled | The serial port enabled for console redirection is visible to the legacy operating system. |
Disabled
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example makes the serial port enabled for console redirection visible to the legacy operating system and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set LegacyOSRedir Enabled Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
show server-management |
|
To set the link down timeout of the host Fibre Channel Interface, use the set link-down-timeout command.
set link-down-timeout msec
msec | Specifies the link down timeout value, the number of milliseconds the uplink port should be offline before it informs the system that the uplink port is down and fabric connectivity has been lost. The range is 0 to 240000. |
The default is 30000 milliseconds.
Error-recovery (/chassis/adapter/host-fc-if/error-recovery)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the link down timeout:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope error-recovery Server /chassis/adapter/host-fc-if/error-recovery # set link-down-timeout 2000 Server /chassis/adapter/host-fc-if/error-recovery *# commit Committed host-fc-if fc0 settings will take effect upon the next server reset
To enable or disable the display of the KVM session on any monitor attached to the server, use the set local-video command.
set local-video { no | | yes }
no | The KVM session is not displayed on any monitor attached to the server. |
yes | The KVM session is displayed on any monitor attached to the server. |
The KVM session is displayed on any monitor attached to the server.
KVM (/kvm)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example enables the display of the KVM session on any monitor attached to the server:
server# scope kvm server /kvm # set enabled yes server /kvm* # set local-video yes server /kvm* # commit server /kvm #
Command |
Description |
show kvm |
|
To turn the server locator LED on or off, use the set locator-led command.
set locator-led { off | on }
off | Turns the locator LED off. |
on | Turns the locator LED on. |
None
Chassis (/chassis)
Physical drive (/chassis/storageadapter/physical-drive)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.4(1) | This command was added in the physical drive mode. |
Use this command to turn on or off the locator LED for the chassis or a physical drive.
This example shows how to turn on the locator LED for the chassis:
server# scope chassis server /chassis # set locator-led on server /chassis* # commit server /chassis #
Command |
Description |
show chassis |
|
show led |
|
To specify whether the system prioritizes low voltage or high frequency memory operations, use the set LvDDRMode command.
set LvDDRMode { Performance_Mode | Power_Saving_Mode }
Performance_Mode | The system prioritizes high frequency operations over low voltage operations. |
Power_Saving_Mode | The system prioritizes low voltage memory operations over high frequency memory operations. This mode may lower memory frequency in order to keep the voltage low. |
The system prioritizes low voltage memory operations over high frequency memory operations.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that high frequency memory operations are optimized and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set LvDDRMode Performance_Mode Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify a MAC address for an interface, use the set mac-addr command.
set mac-addr mac-addr
mac-addr | Specifies a MAC address in the form hh:hh:hh:hh:hh:hh or hhhh:hhhh:hhhh. |
None
Ethernet host interface (/chassis/adapter/host-eth-if)
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to specify a MAC address for the Fibre Channel host interface fc0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # set mac-addr 0123:4567:89ab Server /chassis/adapter/host-fc-if *# commit Server /chassis/adapter/host-fc-if #
Command |
Description |
|
|
To specify whether the server can boot from a USB device, use the set MakeUSBDeviceNonBootable command.
set MakeUSBDeviceNonBootable { Disabled | Enabled }
Disabled | The server can boot from a USB device. |
Enabled | The server cannot boot from a USB device. |
The server can boot from a USB device.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example allows the server to boot from a USB device and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set MakeUSBDeviceNonBootable Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set USBController |
|
show advanced |
|
To specify the maximum data field size for the Fibre Channel interface, use the set max-data-field-size command.
set max-data-field-size size
size | The maximum data field size. Specify a number between 256 and 2112. |
The maximum data field size is 2112.
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to set the maximum data field size to 1024 on interface fc0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # set max-data-field-size 1024 Server /chassis/adapter/host-fc-if *# commit Server /chassis/adapter/host-fc-if #
Command |
Description |
show host-fc-if detail |
|
To specify the maximum number of concurrent KVM sessions allowed, use the set max-sessions command.
set max-sessions sessions
sessions | The maximum number of concurrent KVM sessions allowed. This can be an integer between 1 and 4. |
A maximum of four concurrent KVM sessions is allowed.
KVM (/kvm)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example specifies that a maximum of two concurrent KVM sessions is allowed:
server# scope kvm server /kvm # set enabled yes server /kvm* # set max-sessions 2 server /kvm* # commit server /kvm #
Command |
Description |
show kvm |
|
To set the maximum logical unit numbers (LUNs) per target, use the set max-target-luns command.
set max-target-luns count
count | The maximum logical unit numbers (LUNs) per target; the maximum number of LUNs that the driver will discover. The range is 1 to 1024. |
The default is 256 LUNs.
Port (/chassis/adapter/host-fc-if/port)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the max-target-luns:
Server# scope chassis Server /chassis scope adapter 1 Server /chassis/adapter scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope port Server /chassis/adapter/host-fc-if/port # set max-target-luns 334 Server /chassis/adapter/host-fc-if/port *# commit Server /chassis/adapter/host-fc-if/port #
To enable or disable memory mapped I/O of 64-bit PCI devices to 4GB or greater address space, use the set MemoryMappedIOAbove4GB command.
set MemoryMappedIOAbove4GB { Disabled | Enabled }
Disabled | The server does not map I/O of 64-bit PCI devices to 4GB or greater address space. |
Enabled | The server maps I/O of 64-bit PCI devices to 4GB or greater address space. |
The server does not map I/O of 64-bit PCI devices to 4GB or greater address space.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to enable or disable memory mapped I/O of 64-bit PCI devices to 4GB or greater address space. Legacy option ROMs are not able to access addresses above 4GB. PCI devices that are 64-bit compliant but use a legacy option ROM may not function correctly with this setting enabled.
This example allows the server to map I/O of 64-bit PCI devices to 4GB or greater address space and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set MemoryMappedIOAbove4GB Enabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the server NIC mode, use the set mode command.
set mode { dedicated | shared_lom | shared_lom_10g | cisco_card | shipping }
dedicated | The management Ethernet port is used to access the CIMC. |
||
shared_lom |
|
||
shared_lom_10g | (If supported) The 10G LOM Ethernet host ports are used to access the CIMC. |
||
cisco_card | The ports on the installed adapter card are used to access the CIMC. |
||
shipping | (If supported) The management Ethernet port or ports provide a limited factory default configuration for initial connection. Select another mode for normal operation. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.0(1x) | The shipping keyword was introduced. |
This example sets the server NIC mode to dedicated:
server# scope cimc server /cimc # scope network server /cimc/network # set mode dedicated server /cimc/network* # commit server /cimc/network #
Command |
Description |
show network |
|
To specify an MTU for a vNIC, use the set mtu command.
set mtu mtu-value
mtu-value | Specifies the maximum transmission unit (MTU) or packet size that the vNIC accepts. Valid MTU values are 1500 to 9000 bytes; the default is 1500. |
The MTU is 1500 bytes.
Ethernet host interface (/chassis/adapter/host-eth-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to specify an MTU of 9000 for the Ethernet host interface eth0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # set mtu 9000 Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
|
|
To specify a user name, use the set name command.
set name user-name
user-name | The name of the user. The name can contain up to 70 characters. |
None
User (/user)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example configures a user name, password, and role:
server# scope user server /user # set enabled yes server /user* # set name user15 server /user* # set password cisco123 server /user* # set role read-only server /user* # commit server /user #
Command |
Description |
show user |
|
To enable or disable Network Interface Virtualization (NIV) on the adapter card, use the set niv-mode command.
set niv-mode { disabled | enabled }
disabled | Disables NIV mode on the card. |
enabled | Enables NIV mode on the card. |
NIV mode is disabled.
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to enable NIV mode on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # set niv-mode enabled Server /chassis/adapter *# commit Server /chassis/adapter #
Command |
Description |
show adapter |
|
To specify the action the system should take if power capping is enabled and the server requests more than its peak power allotment, use the set non-compliance-action command.
set non-compliance-action { force-power-reduction | none | power-off-host | throttle }
force-power-reduction | The server is forced to reduce its power consumption by any means necessary. This option is not available on some server models. |
none | No action is taken and the server is allowed to use more power than specified in the peak power setting. |
power-off-host | The server is shut down. |
throttle | Processes running on the server are throttled to bring the total power consumption down. |
None
Power cap (/power-cap)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify the action the system should take if power capping is enabled and the server requests more than its peak power allotment.
This example sets the non-compliance action to throttle processes on the server and commits the transaction:
Server# scope power-cap Server /power-cap # set enabled yes Server /power-cap *# set peak-power 1000 Server /power-cap *# set non-compliance-action throttle Server /power-cap *# commit Server /power-cap # show detail Cur Consumption (W): 688 Max Consumption (W): 1620 Min Consumption (W): 48 Minimum Configurable Limit (W): 500 Maximum Configurable Limit (W): 2000 Power Cap Enabled: yes Peak Power: 1000 Non Compliance Action: throttle Server /power-cap #
Command |
Description |
set peak-power |
|
show power-cap |
|
To specify whether the BIOS supports Non-Uniform Memory Access (NUMA), use the set NUMAOptimize command.
set NUMAOptimize { Disabled | Enabled }
Disabled | The BIOS does not support NUMA. |
Enabled | The BIOS includes the ACPI tables that are required for NUMA-aware operating systems. |
NUMA support is enabled.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify whether the BIOS supports NUMA. When NUMA support is enabled, the BIOS includes the ACPI tables that are required for NUMA-aware operating systems.
Note |
If you enable this option, the system must disable Inter-Socket Memory interleaving on some platforms. |
This example disables NUMA support in the BIOS and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set NUMAOptimize Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To enable or disable the first onboard Network Interface Card (NIC) on the server, use the set OnboardNic1 command.
set OnboardNic1 { Disabled | Enabled }
Disabled | NIC 1 is not available. |
Enabled | NIC 1 is available. |
NIC 1 is available.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
By replacing the numeral 1 in the command with the numeral 2, you can modify this command to specify whether the onboard NIC2 is available. For example, to enable or disable NIC 2, use the set OnboardNic2 command.
This example disables NIC 1 and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set OnboardNic1 Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set OnboardNic1ROM |
|
show advanced |
|
To specify whether the system loads the embedded PXE option ROM for the first onboard NIC on the server, use the set OnboardNic1ROM command.
set OnboardNic1ROM { Disabled | Enabled }
Disabled | The PXE option ROM is not available for NIC 1. |
Enabled | The PXE option ROM is available for NIC 1. |
The PXE option ROM is available for NIC 1.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
By replacing the numeral 1 in the command with the numeral 2, you can modify this command to specify whether the PXE option ROM for onboard NIC2 is available. For example, to specify the option ROM for NIC 2, use the set OnboardNic2ROM command.
This example specifies that the PXE option ROM is available for NIC 1 and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set OnboardNic1ROM Enabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set OnboardNic1 |
|
show advanced |
|
To specify whether the server uses its onboard built-in SATA controller, use the set OnboardSATA command.
set OnboardSATA { Disabled | Enabled }
Disabled | The server does not use its onboard built-in SATA controller. |
Enabled | The server uses its onboard built-in SATA controller. |
The server uses its onboard built-in SATA controller.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
This command is not available on all models and configurations. |
This example specifies that the server does not use its onboard built-in SATA controller and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set OnboardSATA Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the relative order of this device for PCI bus device number assignment, use the set order command.
set order { any | order }
any | No relative order is specified. |
order | Specifies a relative order. The range is 0 to 99. |
No relative order is specified.
Ethernet host interface (/chassis/adapter/host-eth-if)
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to specify the order of PCI bus number assignment of this device relative to other PCI bus devices. PCI bus numbers are assigned to devices by increasing relative order followed by devices for which no order is specified.
This example shows how to specify a relative PC bus number assignment order of 30 for the Fibre Channel host interface fc0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # set order 30 Server /chassis/adapter/host-fc-if *# commit Server /chassis/adapter/host-fc-if #
Command |
Description |
|
|
To set the outstanding IO count of the host Fibre Channel interface, use the set outstanding-io-count command.
set outstanding-io-count count
count | Specifies the number of I/O operations that can be pending in the vHBA at one time. The range is 1 to 1024. |
The default is 512 operations.
Port (/chassis/adapter/host-fc-if/port)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the outstanding-io-count:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope port Server /chassis/adapter/host-fc-if/port # set outstanding-io-count 343 Server /chassis/adapter/host-fc-if/port *# commit Server /chassis/adapter/host-fc-if/port #
To specify whether the processor supports Intel VT-d Pass-through DMA, use the set PassThroughDMA command.
set PassThroughDMA { Disabled | Enabled }
Disabled | The processor does not support pass-through DMA. |
Enabled | The processor uses VT-d Pass-through DMA as required. |
The processor uses VT-d Pass-through DMA as required.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the processor does not support VT-d Pass-through DMA and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set PassThroughDMA Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify a user password, use the set password command.
set password user-password
user-password | The password of the user. The password can contain up to 80 characters. |
None
User (/user)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example configures a user name, password, and role:
server# scope user server /user # set enabled yes server /user* # set name user15 server /user* # set password cisco123 server /user* # set role read-only server /user* # commit server /user #
Command |
Description |
show user |
|
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 specify whether the server can use the PCIe Option ROM expansion slots, use the set Pci-Opt-Roms command.
set Pci-Opt-Roms { Disabled | Enabled }
Disabled | The PCIe Option ROMs are not available. |
Enabled | The PCIe Option ROMs are available. |
The PCIe Option ROMs are available.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the PCIe Option ROMs are not available and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set Pci-Opt-Roms Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the maximum number of watts that can be allocated to the server, use the set peak-power command.
set peak-power watts
watts | The maximum number of watts that can be allocated to the server. |
Zero watts are allocated.
Power cap (/power-cap)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify the maximum number of watts that can be allocated to this server. Enter a number of watts within the range defined by the Minimum Configurable Limit field and the Maximum Configurable Limit field of the show power-cap detail command output. These fields are determined by the server model.
If the server requests more power than specified in this command, the system takes the action defined by the set non-compliance-action command.
This example sets the maximum number of watts allocated to 1000 and commits the transaction:
Server# scope power-cap Server /power-cap # set enabled yes Server /power-cap *# set peak-power 1000 Server /power-cap *# set non-compliance-action throttle Server /power-cap *# commit Server /power-cap # show detail Cur Consumption (W): 688 Max Consumption (W): 1620 Min Consumption (W): 48 Minimum Configurable Limit (W): 500 Maximum Configurable Limit (W): 2000 Power Cap Enabled: yes Peak Power: 1000 Non Compliance Action: throttle Server /power-cap #
Command |
Description |
set non-compliance-action |
|
show power-cap |
|
To specify a blocking time after multiple login failures, use the set penalty-time command.
set penalty-time penalty-seconds
penalty-seconds | The number of seconds the user remains locked out after exceeding the maximum number of login attempts within the specified time window. The range of valid values is 300 to 900. |
The default blocking time is 300 seconds.
IP blocking (/cimc/network/ipblocking)
Release | Modification |
---|---|
1.0(1X) | This command was introduced. |
This example sets the IP blocking time to 600 seconds:
server# scope cimc server /cimc # scope network server /cimc/network # scope ipblocking server /cimc/network/ipblocking # set enable yes server /cimc/network/ipblocking* # set penalty-time 600 server /cimc/network/ipblocking* # commit server /cimc/network/ipblocking #
Command |
Description |
set fail-count |
|
show ipblocking |
|
To enable or disable the persistent binding for the vHBA, use the set persistent-lun-binding command.
set persistent-lun-binding { disable | enable }
disable | Disables persistent-lun binding. |
enable | Enables persistent-lun binding. |
None
Persistent binding (/chassis/adapter/host-fc-if/perbi)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enable the persistent-lun binding of the host Fibre Channel interface:
Server# scope chassis Server/chassis # scope adapter 1 Server/chassis/adapter # scope host-fc-if fc0 Server/chassis/adapter/host-fc-if # scope perbi Server/chassis/adapter/host-fc-if/perbi # set persistent-lun-binding enable Server/chassis/adapter/host-fc-if/perbi *# commit Server/chassis/adapter/host-fc-if/perbi #
To enable or disable platform event alerts, use the set platform-event-enabled command.
set platform-event-enabled { no | | yes }
no | Disables platform event alerts. |
yes | Enables platform event alerts. |
Platform event alerts are enabled.
Fault (/fault)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example enables platform event alerts:
server# scope fault server /fault # set platform-event-enabled yes server /fault* # commit server /fault #
Command |
Description |
show fault |
|
show pef |
|
To set the port login (PLOGI) retries value, use the set plogi-retries command.
set plogi-retries count
count | Specifies the number of times that the system tries to log in to the fabric after the first failure. The range is 0 and 255. |
The default is 8 retries.
Port-p-logi (/chassis/adapter/host-fc-if/port-p-logi)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the plogi-retries of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope port-p-logi Server /chassis/adapter/host-fc-if/port-p-logi # set plogi-retries 03 Server /chassis/adapter/host-fc-if/port-p-logi *# commit Server /chassis/adapter/host-fc-if/port-p-logi #
Command |
Description |
set plogi-timeout |
|
To set the port login (PLOGI) timeout value of the host Fibre Channel interface, use the set plogi-timeout command.
set plogi-timeout msec
msec | Specifies the number of milliseconds that the system waits before it tries to log in again. The range is 1 to 255000. |
The default is 2000 milliseconds.
Port-p-logi (/chassis/adapter/host-fc-if/port-p-logi)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the port login (PLOGI) timeout value of the host Fibre Channel Interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if Server/chassis/adapter/host-fc-if # scope port-p-logi Server/chassis/adapter/host-fc-if/port-p-logi # set plogi-timeout 203 Server/chassis/adapter/host-fc-if/port-p-logi *# commit Server/chassis/adapter/host-fc-if/port-p-logi #
Command |
Description |
set port-plogi-retries |
|
To specify the action to be taken when chassis power is restored, use the set policy command.
set policy { power-off | power-on | restore-last-state }
power-off | Server power will remain off until manually turned on. |
power-on | Server power will be turned on when chassis power is restored. |
restore-last-state | Server power will return to the state before chassis power was lost. |
The default action is power-off.
Chassis (/chassis)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify the action to be taken when chassis power is restored after an outage.
When the selected action is power-on, you can select a delay in the restoration of power to the server.
This example sets the power restore policy to power-on with a fixed delay of 180 seconds (3 minutes) and commits the transaction:
Server# scope chassis Server /chassis # set policy power-on Server /chassis *# set delay fixed Server /chassis *# set delay-value 180 Server /chassis *# commit Server /chassis # show detail Chassis: Power: on Serial Number: QCI1404A1IT Product Name: UCS C200 M1 PID : R200-1120402 UUID: 01A6E738-D8FE-DE11-76AE-8843E138AE04 Locator LED: off Description: Testing power restore Power Restore Policy: power-on Power Delay Type: fixed Power Delay Value(sec): 180 Server /chassis #
Command |
Description |
set delay |
|
set delay-value |
|
To set the port-down-io-retry-count of the host Fibre Channel interface, use the set port-down-io-retry-count command.
set port-down-io-retry-count count
count | The number of times an I/O request to a port is returned because the port is busy before the system decides the port is unavailable. The range is 0 to 255. |
The default is 8 retries.
Error-recovery (/chassis/adapter/host-fc-if/error-recovery)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the port-down-io-retry-count:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if/ # scope error-recovery Server /chassis/adapter/host-fc-if/error-recovery # set port-down-io-retry-count 200 Server /chassis/adapter/host-fc-if/error-recovery *# commit Committed host-fc-if fc0 settings will take effect upon the next server reset Server /chassis/adapter/host-fc-if/error-recovery #
Command |
Description |
set port-down-timeout |
|
To set the port-down-timeout, use the set port-down-timeout command.
set port-down-timeout msec
msec | Specifies the number of milliseconds the uplink port should be offline before it informs the system that the uplink port is down and fabric connectivity has been lost. The range is 0 to 240000. |
The default is 10000 milliseconds.
Error-recovery (/chassis/adapter/host-fc-if/error-recovery)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the port-down-io-retry-timeout:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope error-recovery Server /chassis/adapter/host-fc-if/error-recovery # set port-down-timeout 9343 Server /chassis/adapter/host-fc-if/error-recovery *# commit Committed host-fc-if fc0 settings will take effect upon the next server reset Server /chassis/adapter/host-fc-if/error-recovery #
Command |
Description |
set port-down-io-retry-count |
|
To specify a port profile that should be associated with the vNIC, use the set port-profile command.
set port-profile name
name | The name of a port profile. |
None
Ethernet host interface (/chassis/adapter/host-eth-if)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
To use this command, you must enable NIV mode for the adapter. The name must be a port profile defined on the switch to which this server is connected. |
This example shows how to specify a port profile on interface eth0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # set niv-mode enabled Server /chassis/adapter *# scope host-eth-if eth0 Server /chassis/adapter/host-eth-if *# set port-profile TestProfile5 Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
set niv-mode |
|
show port-profiles |
|
To specify the action when the server encounters a critical error during power-on self test (POST), use the set POSTErrorPause command.
set POSTErrorPause { Disabled | Enabled }
Disabled | The BIOS continues to attempt to boot the server when a critical error occurs during POST. |
Enabled | The BIOS pauses the attempt to boot the server and opens the Error Manager when a critical error occurs during POST. |
The BIOS continues to attempt to boot the server when a critical error occurs during POST.
Main BIOS (/bios/main)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example configures the boot to pause when a critical error occurs during POST and commits the transaction:
Server# scope bios Server /bios # scope main Server /bios/main # set POSTErrorPause Enabled Server /bios/main *# commit Server /bios/main *# show detail Set-up parameters: Boot option retry: Disabled POST Error Pause: Enabled Server /bios/main #
Command |
Description |
show main |
|
To specify the IP address of the primary DNS server, use the set preferred-dns-server command.
set preferred-dns-server dns1-ipv4-address
dns1-ipv4-address | The IP address of the primary DNS server. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example specifies the IP address of the primary DNS server:
server# scope cimc server /cimc # scope network server /cimc/network # set preferred-dns-server 192.0.20.1 server /cimc/network* # commit server /cimc/network #
Command |
Description |
set alternate-dns-server |
|
show network |
|
To specify the highest privilege level that can be assigned to an IPMI session, use the set privilege-level command.
set privilege-level { admin | readonly | user }
admin | IPMI users can perform all available actions. |
readonly | IPMI users can view information but cannot make any changes. |
user | IPMI users can perform some functions but cannot perform administrative tasks. |
IPMI users can perform all available actions.
IPMI (/ipmi)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example sets the highest privilege level that can be assigned to an IPMI session to read-only:
server# scope ipmi server /ipmi # set enabled yes server /ipmi* # set privilege-level readonly server /ipmi* # commit server /ipmi #
Command |
Description |
show ipmi |
|
To specify whether the processor sends the C3 report to the operating system, use the set ProcessorC3Report command.
set ProcessorC3Report { Disabled | ACPI_C2 | ACPI_C3 }
Disabled | The processor does not send the C3 report. |
ACPI_C2 | The processor sends the C3 report using the ACPI C2 format. |
ACPI_C3 | The processor sends the C3 report using the ACPI C3 format. |
The processor does not send the C3 report.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the processor sends the C3 report using the ACPI C3 format and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set ProcessorC3Report ACPI_C3 Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify whether the processor sends the C6 report to the operating system, use the set ProcessorC6Report command.
set ProcessorC6Report { Disabled | Enabled }
Disabled | The processor does not send the C6 report. |
Enabled | The processor sends the C6 report. |
The processor sends the C6 report.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the processor does not send the C6 report and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set ProcessorC6Report Disable Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
To specify the slot in which the primary copy of the data resides, use the set raid-primary-member command.
set raid-primary-member { slot1 | slot2 }
slot1 | The primary copy of the data resides in slot 1. |
slot2 | The primary copy of the data resides in slot 2. |
The primary copy of the data resides in slot 1.
FlexFlash operational profile (/chassis/flexflash/operational-profile)
Release | Modification |
---|---|
1.3(3) | This command was introduced. |
Use this command to specify the slot in which the primary copy of the data resides.
Note |
Currently, Cisco Flexible Flash cards are supported only in slot 1. |
This example shows how to specify that the primary copy of the data resides in slot 1:
Server# scope chassis Server /chassis # scope flexflash FlexFlash-0 Server /chassis/flexflash # scope operational-profile Server /chassis/flexflash/operational-profile # set raid-primary-member slot1 Server /chassis/flexflash/operational-profile *# commit Server /chassis/flexflash/operational-profile #
Command |
Description |
scope operational-profile |
|
To specify a maximum data rate for the host interface, use the set rate-limit command.
set rate-limit { off | rate }
off | Rate limiting is disabled. |
rate | Specifies the rate limit in Mbps. The range is 1 to 10000. |
Rate limiting is disabled.
Ethernet host interface (/chassis/adapter/host-eth-if)
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to specify a rate limit of 500 Mbps on interface eth0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # set rate-limit 500 Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
show host-eth-if |
|
To specify the server NIC redundancy mode when the NIC mode is Shared LOM, use the set redundancy command.
set redundancy { none | active-active | active-standby }
none | The LAN On Motherboard (LOM) Ethernet ports operate independently and do not fail over if there is a problem. |
active-active | If supported, all LOM Ethernet ports are utilized. |
active-standby | If one LOM Ethernet port fails, traffic fails over to another LOM port. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example sets the server NIC redundancy mode to active-standby:
server# scope cimc server /cimc # scope network server /cimc/network # set redundancy active-standby server /cimc/network* # commit server /cimc/network #
Command |
Description |
set mode |
|
show network |
|
To set the the resource allocation timeout value (RATOV), use the set error-detect-timeout command.
set resource-allocation-timeout msec
msec | Specifies the resource allocation timeout value (RATOV), the number of milliseconds to wait before the system assumes that a resource cannot be properly allocated. The range is 5000 to 100000; the default is 10000 milliseconds. |
The default is 10000 milliseconds.
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the resource allocation timeout value to 5000 milliseconds:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # set resource-allocation-timeout 5000 Server /chassis/adapter/host-fc-if *# commit Server /chassis/adapter/host-fc-if #
Command |
Description |
set error-detect-timeout |
|
To set the receive queue count of the host Ethernet interface, use the set rq-count command.
set rq-count count
count | The number of receive queue resources to allocate. The range is 1 to 256. |
The default is 4.
Receive queue (/chassis/adapter/host-eth-if/recv-queue)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the number of receive queue resources to allocate:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope recv-queue Server /chassis/adapter/host-eth-if/recv-queue # set rq-count 3 Server /chassis/adapter/host-eth-if/recv-queue *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/recv-queue #
Command |
Description |
set rq-ring-size |
|
To set the receive queue ring size, use the set rq-ring-size command.
set rq-ring-size size
size | The number of descriptors in the receive queue. The range is 64 to 4094; the default is 512. |
The default is 512.
Receive queue (/chassis/adapter/host-eth-if/recv-queue)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the number of descriptors in the receive queue:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope recv-queue Server /chassis/adapter/host-eth-if/recv-queue # set eth-rq-ring-size 68 Server /chassis/adapter/host-eth-if/recv-queue *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/recv-queue #
Command |
Description |
set rq-count |
|
To enable or disable Receive-side Scaling (RSS), use the set rss command.
set rss { disable | enable }
disable | Disables RSS. |
enable | Enables RSS. |
The default is enable for the two default vNICs and disable for user-created vNICs.
RSS (/chassis/adapter/host-eth-if/rss)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to disable RSS:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope rss Server /chassis/adapter/host-eth-if/rss # set rss disable Server /chassis/adapter/host-eth-if/rss *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/rss #
Command |
Description |
set rss-hash-ipv4 |
|
set rss-hash-ipv6 |
|
To enable or disable the IPv4 RSS of the host Ethernet interface, use the set rss-hash-ipv4 command.
set rss-hash-ipv4 { disable | enable }
disable | Disables IPv4 RSS. |
enable | Enables IPv4 RSS. |
The default is enable.
RSS (/chassis/adapter/host-eth-if/rss)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the rss-hash-ipv4:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope rss Server /chassis/adapter/host-eth-if/rss # set rss-hash-ipv4 disable Server /chassis/adapter/host-eth-if/rss *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/rss #
Command |
Description |
set rss-hash-ipv6 |
|
set rss |
|
To enable or disable the IPv6 RSS of the host Ethernet interface, use the set rss-hash-ipv6 command.
set rss-hash-ipv6 { disable | enable }
disable | Disables IPv6 RSS. |
enable | Enables IPv6 RSS. |
The default is enable.
RSS (/chassis/adapter/host-eth-if/rss)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the rss-hash-ipv6:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope rss Server /chassis/adapter/host-eth-if/rss # set rss-hash-ipv6 disable Server /chassis/adapter/host-eth-if/rss *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/rss #
Command |
Description |
set rss-hash-ipv4 |
|
set rss |
|
To enable or disable the IPv6 Extension RSS of the host Ethernet interface, use the set rss-hash-ipv6-ex command.
set rss-hash-ipv6-ex { disable | enable }
disable | Disables IPv6 extension RSS. |
enable | Enables IPv6 extension RSS. |
The default is disable.
RSS (/chassis/adapter/host-eth-if/rss)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the rss-hash-ipv6-ex:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope rss Server /chassis/adapter/host-eth-if/rss # set rss-hash-ipv6-ex disable Server /chassis/adapter/host-eth-if/rss *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/rss #
Command |
Description |
set rss-hash-ipv6 |
|
set rss |
|
To enable or disable TCP/IPv4 RSS on the host Ethernet interface, use the set rss-hash-tcp-ipv4 command.
set rss-hash-tcp-ipv4 { disable | enable }
disable | Disables TCP/IPv4 RSS. |
enable | EnablesTCP/IPv4 RSS. |
The default is enable.
RSS (/chassis/adapter/host-eth-if/rss)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to enable TCP/IPv4 RSS:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope rss Server /chassis/adapter/host-eth-if/rss # set rss-hash-tcp-ipv4 enable Server /chassis/adapter/host-eth-if/rss *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/rss #
Command |
Description |
set rss |
|
set rss-hash-tcp-ipv6 |
|
To enable or disable the TCP/IPv6 RSS of the host Ethernet interface, use the set rss-hash-tcp-ipv6 command.
set rss-hash-tcp-ipv6 { disable | enable }
disable | Disables TCP/IPv6 RSS. |
enable | Enables TCP/IPv6 RSS. |
The default is enable.
RSS (/chassis/adapter/host-eth-if/rss)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the rss-hash-tcp-ipv6:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope rss Server /chassis/adapter/host-eth-if/rss # set rss-hash-tcp-ipv6 disable Server /chassis/adapter/host-eth-if/rss *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/rss #
Command |
Description |
set rss-hash-tcp-ipv4 |
|
set rss |
|
To set the TCP/IPv6 Extension RSS of the host Ethernet interface, use the set rss-hash-tcp-ipv6-ex command.
set rss-hash-tcp-ipv6-ex { disable | enable }
disable | Disables TCP/IPv6 extension RSS. |
enable | Enables TCP/IPv6 extension RSS. |
The default is disable.
RSS (/chassis/adapter/host-eth-if/rss)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the rss-hash-tcp-ipv6-ex:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope rss Server /chassis/adapter/host-eth-if/rss # set rss-hash-tcp-ipv6-ex Server /chassis/adapter/host-eth-if/rss *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/rss #
Command |
Description |
set rss-hash-tcp-ipv4-ex |
|
set rss |
|
To specify how the memory reliability, availability, and serviceability (RAS) is configured for the server, use the set SelectMemoryRAS command.
set SelectMemoryRAS { Maximum_Performance | Mirroring | Sparing }
Maximum_Performance | System performance is optimized. |
Mirroring | System reliability is optimized by using half the system memory as backup. |
Sparing | System reliability is enhanced with a degree of memory redundancy while making more memory available to the operating system than mirroring. |
System performance is optimized.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example configures memory mirroring for system reliability and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set SelectMemoryRAS Mirroring Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
show advanced |
|
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 enable or disable serial port A, use the set Serial-PortA command.
set Serial-PortA { Disabled | Enabled }
Disabled | The port is disabled. |
Enabled | The port is enabled. |
The port is enabled.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
This command is not available on all models and configurations. |
This example disables serial port A and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set Serial-PortA Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set SerialPortAAddress |
|
show advanced |
|
To specify the address to be used by serial port A, use the set SerialPortAAddress command.
set SerialPortAAddress { 2E8 | 3E8 | 3F8 }
2E8 | The port uses address 2E8. |
3E8 | The port uses address 3E8. |
3F8 | The port uses address 3F8. |
The port uses address 3F8.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
By replacing the port letter A in the command with the letter B, you can modify this command to specify an address for serial port B. For example, to specify an address for serial port B, use the set SerialPortBAddress command.
Note |
This command is not available on all models and configurations. |
This example specifies that serial port A uses address 3E8 and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set SerialPortAAddress 3E8 Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set Serial-PortA |
|
show advanced |
|
To enable or disable serial port B, use the set Serial-PortB command.
set Serial-PortB { Disabled | Enabled }
Disabled | The port is disabled. |
Enabled | The port is enabled. |
The port is enabled.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
This command is not available on all models and configurations. |
This example disables serial port B and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set Serial-PortB Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set SerialPortBAddress |
|
show advanced |
|
To specify the address to be used by serial port B, use the set SerialPortBAddress command.
set SerialPortBAddress { 2E8 | 2F8 | 3E8 | 3F8 }
2E8 | The port uses address 2E8. |
2F8 | The port uses address 2F8. |
3E8 | The port uses address 3E8. |
3F8 | The port uses address 3F8. |
The port uses address 2F8.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Note |
This command is not available on all models and configurations. |
This example specifies that serial port B uses address 3E8 and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set SerialPortBAddress 3E8 Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set Serial-PortB |
|
show advanced |
|
To specify the IP address of a remote server, use the set server-ip command.
set server-ip ip-address
ip-address | Specifies the IP address of a remote server. |
None
CIMC log server (/cimc/log/server)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.1(2) | This command was added to the CIMC log server command mode. |
1.4(1) | This command was removed from the LDAP command mode. |
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 |
show server |
|
To specify whether the PCIe expansion slot 1 is available to the server, use the set Slot1Disable command.
set Slot1Disable { Disabled | Enabled }
Disabled | The expansion slot is not available. |
Enabled | The expansion slot is available. |
The expansion slot is available.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
By replacing the numeral 1 in the command with the number of another PCIe expansion slot, you can modify this command to specify whether other expansion slots are available. For example, to configure expansion slot 2, use the set Slot2Disable command.
This example specifies that PCIe expansion slot 1 is not available and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set Slot1Disable Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set SlotMezzDisable |
|
show advanced |
|
To specify whether the PCIe mezzanine slot expansion ROM is available to the server, use the set SlotMezzDisable command.
set SlotMezzDisable { Disabled | Enabled }
Disabled | The mezzanine slot is not available. |
Enabled | The mezzanine slot is available. |
The mezzanine slot is available.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example specifies that the PCIe mezzanine slot expansion ROM is not available and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set SlotMezzDisable Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set Slot1Disable |
|
show advanced |
|
To specify the port number for SSH connections to CIMC, use the set ssh-port command.
set ssh-port port-number
port-number | The port number for SSH connections to CIMC. |
The default port number is 22.
Secure shell (/ssh)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example configures a port number of 22 for SSH connections:
server# scope ssh server /ssh # set enabled yes server /ssh* # set ssh-port 22 server /ssh* # commit server /ssh #
Command |
Description |
show ssh |
|
To specify the SNMP system contact information, use the set sys-contact command.
set sys-contact contact
contact | The SNMP contact information. |
None
SNMP (/snmp)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify the system contact person responsible for the SNMP implementation. The contact information can be up to 254 characters, such as an email address or a name and telephone number. To enter a value that contains spaces, you must enclose the entry with quotation marks.
SNMP must be enabled and saved before this command can be accepted.
This example configures the SNMP parameters and commits the transaction:
scope snmp Server /snmp # set enabled yes Server /snmp *# commit Server /snmp # set community-str cimcpublic Server /snmp *# set sys-contact "User Name <username@example.com> +1-408-555-1212" Server /snmp *# set sys-location "San Jose, California" Server /snmp *# commit Server /snmp # show detail SNMP Settings: SNMP Port: 161 System Contact: User Name <username@example.com> +1-408-555-1212 System Location: San Jose, California SNMP Community: cimcpublic SNMP Trap community: 0 Enabled: yes SNMP Trap Version: 1 SNMP Inform Type: inform Server /snmp #
Command |
Description |
scope snmp |
|
show snmp |
|
To specify the SNMP system server location, use the set sys-location command.
set sys-location location
location | The SNMP system server location information. |
None
SNMP (/snmp)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify the location of the host on which the SNMP agent (server) runs. The location information can be up to 254 characters. To enter a value that contains spaces, you must enclose the entry with quotation marks.
SNMP must be enabled and saved before this command can be accepted.
This example configures the SNMP parameters and commits the transaction:
scope snmp Server /snmp # set enabled yes Server /snmp *# commit Server /snmp # set community-str cimcpublic Server /snmp *# set sys-contact "User Name <username@example.com> +1-408-555-1212" Server /snmp *# set sys-location "San Jose, California" Server /snmp *# commit Server /snmp # show detail SNMP Settings: SNMP Port: 161 System Contact: User Name <username@example.com> +1-408-555-1212 System Location: San Jose, California SNMP Community: cimcpublic SNMP Trap community: 0 Enabled: yes SNMP Trap Version: 1 SNMP Inform Type: inform Server /snmp #
Command |
Description |
scope snmp |
|
show snmp |
|
To enable or disable the TCP Large Packet Receive Offload, use the set tcp-large-receive offload command.
settcp-large-receive-offload { disable | enable }
disable | The CPU processes all large packets. |
enable | The hardware reassembles all segmented packets before sending them to the CPU. This option may reduce CPU utilization and increase inbound throughput. |
The default is enable.
Offload (/chassis/adapter/host-eth-if/offload)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the TCP Large Packet Receive Offload:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope offload Server /chassis/adapter/host-eth-if/offload # set tcp-large-receive-offload disable Server /chassis/adapter/host-eth-if/offload *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/offload #
Command |
Description |
set tcp-tx-checksum-offload |
|
To enable or disable the TCP receive checksum validation offload, use the set tcp-rx-checksum-offload command.
set tcp-rx-checksum-offload { disable | enable }
disable | The CPU validates all packet checksums. |
enable | The CPU sends all packet checksums to the hardware for validation. This option may reduce CPU overhead. |
The default is enable.
Offload (/chassis/adapter/host-eth-if/offload)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the TCP rx checksum offload:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope offload Server /chassis/adapter/host-eth-if/offload # set tcp-rx-checksum-offload disable Server /chassis/adapter/host-eth-if/offload *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/offload #
Command |
Description |
set tcp-tx-checksum-offload |
|
set tcp-segment-offload |
|
To enable or disable the TCP segment offload, use the set tcp-segment-offload command.
set tcp-segment-offload { disable | enable }
disable | Disables the CPU segments large TCP packets. |
enable | Enables the CPU to send large TCP packets to the hardware to be segmented. |
The default is enable.
Offload (/chassis/adapter/host-eth-if/offload)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the TCP segment offload:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope offload Server /chassis/adapter/host-eth-if/offload # set tcp-segment-offload disable Server /chassis/adapter/host-eth-if/offload *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/offload #
Command |
Description |
set tcp-tx-checksum-offload |
|
set tcp-rx-checksum-offload |
|
To enable or disable the TCP Transmit Offload Checksum Validation, use the set tcp-tx-checksum-offload command.
set tcp-tx-checksum-offload { disable | | enable }
disable | The CPU validates all packet checksums. |
enable | The CPU sends all packet checksums to the hardware for validation. This option may reduce CPU overhead. |
The default is enable.
Offload (/chassis/adapter/host-eth-if/offload)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the TCP rx checksum offload:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope offload Server /chassis/adapter/host-eth-if/offload # set tcp-tx-checksum-offload disable Server /chassis/adapter/host-eth-if/offload *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/offload #
Command |
Description |
set tcp-tx-checksum-offload |
|
set tcp-rx-checksum-offload |
|
To specify the type of character formatting for console redirection, use the set TerminalType command.
set TerminalType { PC-ANSI | VT100 | VT-100-PLUS | VT-UTF8 }
PC-ANSI | The PC-ANSI terminal font is used. |
VT-UTF8 | A video terminal with the UTF-8 character set is used. |
VT100 | A supported vt100 video terminal and its character set are used. |
VT-100-PLUS | A supported vt100-plus video terminal and its character set are used. |
A supported vt100 video terminal and its character set are used.
Server Management BIOS (/bios/server-management)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to specify the type of character formatting for console redirection.
Note |
This setting must match the setting on the remote terminal application. |
This example specifies a video terminal with the UTF-8 character set and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set TerminalType VT-UTF8 Server /bios/server-management *# commit Server /bios/server-management #
Command |
Description |
show server-management |
|
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 specify a timeout period, use the set timeout command.
set timeout time
time | The timeout period, in seconds. |
The default HTTP timeout is 1800 seconds.
The default LDAP timeout is 60 seconds.
The default SSH timeout is 1800 seconds.
HTTP (/http)
LDAP (/ldap)
Secure shell (/ssh)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
In the HTTP and SSH scopes, use this command to specify the connection timeout period in seconds.
In the LDAP scope, use this command to specify the period in seconds until the LDAP search operation times out.
This example shows how to set the HTTP connection timeout to 600 seconds:
server# scope http server /http # set timeout 600 server /http* # commit server /http #
Command |
Description |
show http |
|
show ldap |
|
show ssh |
|
To specify whether the vNIC will trust host CoS or will remark packets, use the set trust-host-cos command.
set trust-host-cos { disable | enable }
disable | Received packets are remarked with the configured CoS value. |
enable | The existing CoS value of received packets is preserved. |
Received packets are remarked.
Ethernet host interface (/chassis/adapter/host-eth-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to specify whether the vNIC will trust host CoS or will remark packets. By default, the received host CoS is not trusted, and the vNIC will remark the packets with the CoS value configured by the set cos command or with a value of zero (0) if no CoS value is configured. If this command is enabled, the vNIC will preserve the CoS value of received packets.
This example shows how to specify that received CoS values are preserved (trusted) by Ethernet host interface eth0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # set trust-host-cos enable Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
set cos |
|
To specify the uplink port associated with a vNIC, use the set uplink command.
set uplink { 0 | 1 }
0 | All traffic for this vNIC goes through uplink port 0. |
1 | All traffic for this vNIC goes through uplink port 1. |
None
Ethernet host interface (/chassis/adapter/host-eth-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to associate uplink port 1 with the Ethernet host interface eth0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # set uplink 1 Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
show host-eth-if |
|
To specify the NIV uplink failback timeout for the host interface, use the set uplink-failback-timeout command.
set uplink-failback-timeout seconds
seconds | Specifies the timeout in seconds. The range is 0 to 600. |
None
Ethernet host interface (/chassis/adapter/host-eth-if)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
After a vNIC has started using its secondary interface, this setting controls how long the primary interface must be available before the system resumes using the primary interface for the vNIC.
Note |
To use this command, you must enable NIV mode for the adapter. |
This example shows how to specify an NIV uplink failback timeout of 60 seconds on interface eth0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # set niv-mode enabled Server /chassis/adapter *# scope host-eth-if eth0 Server /chassis/adapter/host-eth-if *# set uplink-failover enabled Server /chassis/adapter/host-eth-if *# set uplink-failback-timeout 60 Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
set niv-mode |
|
set uplink-failover |
|
To allow the vNIC to fail over to the secondary interface, use the set uplink-failover command.
set uplink-failover { disabled | enabled }
disabled | Disables failover. |
enabled | Allows failover. |
None
Ethernet host interface (/chassis/adapter/host-eth-if)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Enable this setting if traffic on this vNIC should fail over to the secondary interface if there are communication problems.
Note |
To use this command, you must enable NIV mode for the adapter. |
This example shows how to enable uplink failover on interface eth0 on adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # set niv-mode enabled Server /chassis/adapter *# scope host-eth-if eth0 Server /chassis/adapter/host-eth-if *# set uplink-failover enabled Server /chassis/adapter/host-eth-if *# set uplink-failback-timeout 60 Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
set niv-mode |
|
set uplink-failback-timeout |
|
To specify whether the server uses its built-in USB controller, use the set USBController command.
set USBController { Disabled | Enabled }
Disabled | The server does not use its built-in USB controller. |
Enabled | The server uses its built-in USB controller. |
The server uses its built-in USB controller.
Advanced BIOS (/bios/advanced)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example disables the built-in USB controller and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set USBController Disabled Server /bios/advanced *# commit Server /bios/advanced #
Command |
Description |
set MakeUSBDeviceNonBootable |
|
show advanced |
|
To specify the IPv4 address of the server, use the set v4-addr command.
set v4-addr ip-address
ip-address | An IPv4 address in the format X.X.X.X. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example sets the IPv4 address of the server:
server# scope cimc server /cimc # scope network server /cimc/network # set v4-addr 192.0.20.111 server /cimc/network* # commit server /cimc/network #
Command |
Description |
show network |
|
To specify the IPv4 address of the local gateway, use the set v4-gateway command.
set v4-gateway ip-address
ip-address | An IPv4 address in the format X.X.X.X. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example specifies the IPv4 address of the gateway:
server# scope cimc server /cimc # scope network server /cimc/network # set v4-gateway 192.0.20.254 server /cimc/network* # commit server /cimc/network #
Command |
Description |
show network |
|
To specify the IPv4 netmask of the server, use the set v4-netmask command.
set v4-netmask ip-address
ip-address | An IPv4 netmask in the format X.X.X.X. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example specifies the IPv4 netmask of the server:
server# scope cimc server /cimc # scope network server /cimc/network # set v4-netmask 255.255.240.0 server /cimc/network* # commit server /cimc/network #
Command |
Description |
show network |
|
To specify the virtual drives to be made available to the server, use the set virtual-drives-enabled command.
set virtual-drives-enabled drive-list
drive-list | A list of virtual drives. See the Usage Guidelines for options and format. |
None
FlexFlash operational profile (/chassis/flexflash/operational-profile)
Release | Modification |
---|---|
1.3(3) | This command was introduced. |
Use this command to specify the virtual drives to be made available to the server as a USB-style drive. List each virtual drive you want the server to access. The options are as follows:
When listing more than one option, you must enclose the list in quotation marks (").
This example shows how to specify the virtual drives to be made available to the server for the first flash device:
Server# scope chassis Server /chassis # scope flexflash FlexFlash-0 Server /chassis/flexflash # scope operational-profile Server /chassis/flexflash/operational-profile # set virtual-drives-enabled "SCU DRIVERS" Server /chassis/flexflash/operational-profile *# commit Server /chassis/flexflash/operational-profile #
Command |
Description |
scope operational-profile |
|
To specify the assigned VLAN for an interface, use the set vlan command.
set vlan { none | vlan-id }
none | The interface belongs to no VLAN. This is the default. |
vlan-id | The interface belongs to the specified VLAN. Valid VLAN identifiers are 1 to 4094. |
The interface belongs to no VLAN.
Ethernet host interface (/chassis/adapter/host-eth-if)
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
In an FCoE application, use this command to associate the vHBA with the FCoE VLAN.
This example shows how to assign the Fibre Channel host interface fc0 to VLAN 5:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # set vlan 5 Server /chassis/adapter/host-fc-if *# commit Server /chassis/adapter/host-fc-if #
Command |
Description |
|
|
To enable or disable VLAN membership for the server, use the set vlan-enabled command.
set vlan-enabled { no | yes }
no | VLAN membership is disabled. |
yes | VLAN membership is enabled. |
VLAN membership is disabled.
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example configures a VLAN connection for the CIMC to VLAN 200:
server# scope cimc server /cimc # scope network server /cimc/network # set vlan-enabled yes server /cimc/network* # set vlan-id 200 server /cimc/network* # commit server /cimc/network #
Command |
Description |
set vlan-id |
|
show network |
|
To specify the VLAN number for connection to the server, use the set vlan-id command.
set vlan-id id
id | The VLAN number. |
None
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example configures a VLAN connection for the CIMC to VLAN 200:
server# scope cimc server /cimc # scope network server /cimc/network # set vlan-enabled yes server /cimc/network* # set vlan-id 200 server /cimc/network* # commit server /cimc/network #
Command |
Description |
set vlan-enabled |
|
show network |
|
To specify the VLAN mode for a vNIC, use the set vlan-mode command.
set vlan-mode { access | trunk }
access | The vNIC belongs to only one VLAN. |
trunk | The vNIC can belong to more than one VLAN. |
The vNIC can belong to more than one VLAN.
Ethernet host interface (/chassis/adapter/host-eth-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to specify trunk VLAN mode for the Ethernet host interface eth0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # set vlan-mode trunk Server /chassis/adapter/host-eth-if *# commit Server /chassis/adapter/host-eth-if #
Command |
Description |
|
|
To specify the VLAN priority, use the set vlan-priority command.
set vlan-priority priority
priority | The VLAN priority. The range is 0 to 7. |
The default VLAN priority is 0.
Network (/cimc/network)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
This example configures a VLAN connection with a priority of 5:
server# scope cimc server /cimc # scope network server /cimc/network # set vlan-enabled yes server /cimc/network* # set vlan-id 200 server /cimc/network* # set vlan-priority 5 server /cimc/network* # commit server /cimc/network #
Command |
Description |
set vlan-enabled |
|
show network |
|
To set the transmit queue count of the host Ethernet interface, use the set wq-count command.
set wq-count count
count | The number of transmit queue resources to allocate. The range is 1 to 256. |
The default is 1.
Transmit queue (/chassis/adapter/host-eth-if/trans-queue)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the number of transmit queue resources to allocate:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope trans-queue Server /chassis/adapter/host-eth-if/trans-queue # set wq-count 3 Server /chassis/adapter/host-eth-if/trans-queue *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/trans-queue #
Command |
Description |
set wq-ring-size |
|
To set the transmit queue ring size, use the set wq-ring-size command.
set wq-ring-size size
size | The number of descriptors in the transmit queue. The range is 64 to 4094; the default is 256. |
The default is 256.
Transmit queue (/chassis/adapter/host-eth-if/trans-queue)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to set the number of descriptors in the transmit queue:
Server# scope chassis Server /chassis/ # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # scope trans-queue Server /chassis/adapter/host-eth-if/trans-queue # set wq-ring-size 68 Server /chassis/adapter/host-eth-if/trans-queue *# commit Committed host-eth-if eth0 settings will take effect upon the next server reset Server /chassis/adapter/host-eth-if/trans-queue #
Command |
Description |
set rq-count |
|
To specify the WWNN for an interface, use the set wwnn command.
set wwnn wwnn
wwnn | Specifies a unique World Wide Node Name (WWNN) for the adapter in the form hh:hh:hh:hh:hh:hh:hh:hh. |
None
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to assign a WWNN to the Fibre Channel host interface fc0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # set wwnn 01:23:45:67:89:ab:cd:ef Server /chassis/adapter/host-fc-if *# commit Server /chassis/adapter/host-fc-if #
Command |
Description |
set wwpn |
|
To specify the WWPN for an interface, use the set wwpn command.
set wwpn wwpn
wwpn | Specifies a unique World Wide Port Name (WWPN) for the adapter in the form hh:hh:hh:hh:hh:hh:hh:hh. |
None
Fibre Channel host interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to assign a WWPN to the Fibre Channel host interface fc0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # set wwpn 01:23:45:67:89:ab:cd:ef Server /chassis/adapter/host-fc-if *# commit Server /chassis/adapter/host-fc-if #
Command |
Description |
set wwnn |
|
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 show the adapter properties, use the show adapter command.
show adapter index [detail]
index | The PCI slot number of the adapter card. |
detail | (Optional) Displays detailed adapter properties in list form. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display information about the adapter:
Server# scope chassis Server /chassis # show adapter 1 PCI Slot Product Name Serial Number Product ID Vendor -------- -------------- -------------- -------------- -------------------- 1 UCS VIC P81E QCI1421A6SI N2XX-ACPCI01 Cisco Systems Inc 2 UCS VIC P81E QCI1409A1RY N2XX-ACPCI01 Cisco Systems Inc Server /chassis # show adapter 1 detail PCI Slot 1: Product Name: UCS VIC P81E Serial Number: QCI1421A6SI Product ID: N2XX-ACPCI01 Adapter Hardware Revision: 4 Current FW Version: 1.6(0.11) NIV: Enabled FIP: Enabled Configuration Pending: no CIMC Management Enabled : no VID: V00 Vendor: Cisco Systems Inc Description: LA-s4a FW Image 1 Version: 1.6(0.11) FW Image 1 State: RUNNING ACTIVATED FW Image 2 Version: 1.3(1.114) FW Image 2 State: BACKUP INACTIVATED FW Update Status: Idle FW Update Error: No error FW Update Stage: No operation (0%) FW Update Overall Progress: 0% Server /chassis #
Command |
Description |
activate-adapter-fw |
|
update-adapter-fw |
|
To display the advanced BIOS configuration settings, use the show advanced command.
show advanced [detail]
detail | (Optional) Displays detailed advanced BIOS configuration settings in list format. |
None
BIOS (/bios)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example displays the advanced BIOS configuration details:
Server# scope bios Server /bios # show advanced detail Set-up parameters: Intel(R) VT-d Address Translati: Enabled Adjacent Cache Line prefetch: Enabled CPU Performance: Enterprise Intel(R) VT-d Coherency Support: Disabled Number of enabled cores: All Direct Cache Access: Enabled Enhanced Intel Speedstep(R) Tec: Enabled Execute Disable: Enabled Hardware Prefetcher: Enabled Intel(R) Hyper-Threading Techno: Enabled Intel(R) Turbo Boost Technology: Enabled Intel(R) Virtualization Technol: Enabled Intel(R) VT for Directed IO: Enabled Intel(R) VT-d Interrupt Remappi: Enabled Low Voltage DDR Mode: Power Saving Mode Make Device Non Bootable: Disabled Memory Mapped I/O above 4GB: Disabled NUMA Optimized: Enabled Onboard Gbit NIC 1: Enabled Onboard Gbit NIC 1 ROM: Enabled Onboard Gbit NIC 2: Enabled Onboard Gbit NIC 2 ROM: Enabled Intel(R) VT-d PassThrough DMA: Enabled PCIe OptionROMs: Enabled Processor C3 Report: Disabled Processor C6 Report: Enabled Select Memory RAS: Maximum Performance Serial A Enable: Enabled Serial A Address: 3F8h PCIe Slot A ROM: No PCIe Slot B ROM: No PCIe Slot C ROM: No PCIe Slot D ROM: No PCIe Slot E ROM: Enabled USB Controller: Enabled Server /bios #
Command |
Description |
scope advanced |
|
To display battery backup information for a storage adapter, use the show bbu command.
show bbu [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display battery backup information for a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show bbu Controller Battery Type Battery Present Voltage Current Charge Charging State ---------- ------------ --------------- ---------- ---------- ------ -------------- SAS iBBU true 4.021 V 0.000 A 100% fully charged server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
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 information about the boot table of the host Fibre Channel interface, use the show boot command.
show boot [detail]
detail | (Optional) Displays detailed information about the boot table in list format. |
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if )
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display the boot table of the host Fibre Channel interface.
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # show boot Boot Table Entry Boot Target WWPN Boot LUN ID ----------------- -------------------------- ------------ 0 20:00:00:11:22:33:44:55 3 1 20:00:00:11:22:33:44:56 5 Server /chassis/adapter/host-fc-if #
Command |
Description |
create-boot-entry |
|
delete boot |
|
To display RAID levels supported by a storage adapter, use the show capabilities command.
show capabilities [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display RAID levels supported by a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show capabilities PCI Slot SAS: RAID-0 RAID-1 RAID-5 RAID-6 RAID-00 RAID-10 RAID-50 RAID-60 RAID-1e-rlq0 RAID-1e0-rlq0 RAID-srl-03 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
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 information about the completion queue of the host Ethernet interface, use the show comp-queue command.
show comp-queue [detail]
detail | (Optional) Displays detailed information in list format. |
None
Host Ethernet interface (/chassis/adapter/host-eth-if)
VM FEX interface (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added to the VM FEX interface. |
This example shows how to display information about the completion queue of the host Ethernet interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # show comp-queue Completion Queue Count Completion Queue Ring Size ------------------------- -------------------------- 5 1 Server /chassis/adapter/host-eth-if #
Command |
Description |
set cq-count |
|
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. |
1.3(1) | This command was modified to display enhanced property information. |
The detailed enhanced properties are described in the following table:
Name | Description |
---|---|
Name column |
The name of the DIMM slot in which the memory module is installed. |
Capacity column |
The size of the DIMM. |
Channel Speed column |
The clock speed of the memory channel, in megahertz. |
Channel Type column |
The type of memory channel. |
Memory Type Detail column |
The type of memory used in the device. |
Bank Locator column |
The location of the DIMM within the memory bank. |
Manufacturer column |
The vendor ID of the manufacturer. This can be one of the following: |
Serial Number column |
The serial number of the DIMM. |
Asset Tag column |
The asset tag associated with the DIMM, if any. |
Part Number column |
The part number for the DIMM assigned by the vendor. |
Visibility column |
Whether the DIMM is available to the server. |
Operability column |
Whether the DIMM is currently operating correctly. |
Data Width column |
The amount of data the DIMM supports, in bits. |
This example shows how to display detailed information about the DIMMs:
server# scope chassis server /chassis # show dimm detail Name MEM1 DIMM_1B: Capacity: 8192 MB Channel Speed (MHz): 1067 Channel Type: DDR3 Memory Type Detail: Synchronous Bank Locator: MEM1 SLOT Visibility: Yes Operability: NA Manufacturer: 0x802C Part Number: 36JSZS1G72PY-1G1A1 Serial Number: 0xEA27C463 Asset Tag: Unknown Data Width: 72 bits Name MEM1 DIMM_1A: Capacity: 8192 MB Channel Speed (MHz): 1067 Channel Type: DDR3 Memory Type Detail: Synchronous Bank Locator: MEM1 SLOT Visibility: Yes Operability: NA Manufacturer: 0x802C Part Number: 36JSZS1G72PY-1G1A1 --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 the number of errors seen by a storage adapter, use the show error-counters command.
show error-counters [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display the number of errors seen by a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show error-counters PCI Slot SAS: Memory Correctable Errors: 0 Memory Uncorrectable Errors: 0 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display information about the Fibre Channel error recovery, use the show error-recovery command.
show error-recovery [detail]
detail | (Optional) Displays detailed information about the error-recovery in list format. |
None
Host Fibre Channel Interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to show details of the host Fibre Channel interface errror recovery.
This example shows how to display the error recovery of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if show error-recovery Error Recovery Link Down Timeout(ms) Port Down Timeout(ms) -------------- ---------------------- ---------------------- Disabled 30000 10000 Server /chassis/adapter/host-fc-if/error-recovery #
Command |
Description |
set cq-count |
|
To display information about the external Ethernet interface, use the show ext-eth-if command.
show ext-eth-if [detail]
detail | (Optional) Displays detailed information in list format. |
None
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display the external Ethernet interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # show ext-eth-if Port ID Uplink port MAC address Link State Encapsulation Mode ------- ------------------------ ------------------- -------------------- 0 00:22:BD:D6:40:E0 Link Up CE 1 00:22:BD:D6:40:E1 SFP Not Installed CE Server /chassis/adapter #
Command |
Description |
show host-eth-if |
|
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 whether platform event alerts are enabled or disabled 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. |
1.4(1) | This command was modified to remove display of the SNMP community string. |
This command displays whether platform event alerts are enabled or disabled.
This example shows how to display whether platform event alerts are enabled or disabled:
server# show fault Platform Event Enabled ---------------------- yes 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 firmware version information for a storage adapter, use the show firmware-versions command.
show firmware-versions [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display firmware version information for a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show firmware-versions PCI Slot SAS: Product Name: LSI MegaRAID SAS 9260-8i Serial No: SV93404392 Firmware Package Build: 12.12.0-0038 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display summary information about installed Cisco Flexible Flash controllers, use the show flexflash command.
show flexflash [index] [detail]
index | (Optional) The name of the Cisco Flexible Flash controller. |
detail | (Optional) Displays detailed information in list format. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.3(3) | This command was introduced. |
This example shows how to display information about the first flash device:
Server# scope chassis Server /chassis # show flexflash FlexFlash-0 Controller Product Name Firmware Version Internal State Vendor ------------ ---------------- ----------------- --------------- -------- FlexFlash-0 Cisco FlexFlash 1.2 build 247 Connected Cypress Server /chassis #
Command |
Description |
show operational-profile |
|
To display information about installed hard disk drives (HDD) in the chassis, use the show hdd command.
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 a host Ethernet interface, use the show host-eth-if command.
show host-eth-if [ eth0 | eth1 | name ] [detail]
eth0 | (Optional) Displays information about the eth0 Ethernet interface. |
eth1 | (Optional) Displays information about the eth1 Ethernet interface. |
name | (Optional) Displays information about the named Ethernet interface. |
detail | (Optional) Displays detailed information in list form. |
None
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display information about the eth0 Ethernet interface of adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # show host-eth-if eth0 Name MTU Uplink Port MAC Address CoS VLAN PXE Boot ---------------- ---- ----------- ----------------- --- ---- -------- eth0 1500 0 00:22:BD:D6:40:E3 0 NONE enabled Server /chassis/adapter #
Command |
Description |
show ext-eth-if |
|
To display information about the host Fibre Channel interface, use the show host-fc-if command.
show host-fc-if [ fc0 | fc1 | name ] [detail]
fc0 | (Optional) Displays information about vHBA fc0. |
fc1 | (Optional) Displays information about vHBA fc1. |
name | (Optional) Displays information about a user-defined vHBA. |
detail | (Optional) Displays detailed information in list form. |
None
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was modified to add the name variable. |
This example shows how to display all vHBAs on adapter card 1 and the detailed properties of fc0:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # show host-fc-if Name World Wide Port Name FC SAN Boot Uplink Port -------- ------------------------ ----------- ----------- fc0 20:00:00:22:BD:D6:5C:35 Enabled 0 fc1 20:00:00:22:BD:D6:5C:36 Disabled 1 Server /chassis/adapter # show host-fc-if fc0 detail Name fc0: World Wide Node Name: 10:00:00:22:BD:D6:5C:35 World Wide Port Name: 20:00:00:22:BD:D6:5C:35 FC SAN Boot: Enabled Persistent LUN Binding: Disabled Uplink Port: 0 MAC Address: 00:22:BD:D6:5C:35 CoS: 3 VLAN: NONE Rate Limiting: OFF PCIe Device Order: ANY EDTOV: 2000 RATOV: 10000 Maximum Data Field Size: 2112 Channel Number: 3 Port Profile: Server /chassis/adapter #
Command |
Description |
create host-fc-if |
|
To display information about HTTP services on the server, use the show http command.
show http [ detail ]
detail | (Optional) Displays detailed information in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
Use this command to display information about HTTP ports, session timeout, and session activity.
This example shows how to display information about HTTP services:
Server# show http HTTP Port HTTPS Port Timeout Active Sessions Enabled HTTP Redirected ---------- ---------- -------- --------------- ------- ---------------- 80 443 1800 0 yes yes Server#
Command |
Description |
set http-port |
|
set https-port |
|
To display hardware information for a storage adapter, use the show hw-config command.
show hw-config [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display hardware information for a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show hw-config PCI Slot SAS: SAS Address 0: 500605b0000272bf SAS Address 1: 0000000000000000 SAS Address 2: 0000000000000000 SAS Address 3: 0000000000000000 SAS Address 4: 0000000000000000 SAS Address 5: 0000000000000000 SAS Address 6: 0000000000000000 SAS Address 7: 0000000000000000 BBU Present: true NVRAM Present: true Serial Debugger Present: true Memory Present: true Flash Present: true Memory Size: 512 MB Cache Memory Size: 394 MB Number of Backend Ports: 8 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display information about the interrupt of the host Ethernet interface or the host Fibre Channel Interface, use the show interrupt command.
show interrupt
detail | (Optional) Displays detailed information in list format. |
Host Ethernet interface (/chassis/adapter/host-eth-if )
Host Fibre Channel interface (/chassis/adapter/host-fc-if )
VM FEX interface (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added to the VM FEX interface. |
This example shows how to display the interrupt of the host Ethernet interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # show interrupt Interrupt Count Coalescing Time (us) Coalescing Type Interrupt Mode --------------- -------------------- --------------- --------------- 8 125 MIN MSIx Server /chassis/adapter/host-eth-if #
Command |
Description |
set interrupt-type |
|
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 Active Directory, use the show ldap command.
show ldap [detail]
detail | (Optional) Displays detailed information about the configuration and status of 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 Active Directory:
Server# show ldap detail LDAP Settings: Domain Controller 1: 192.0.20.123 Domain Controller 2: 0.0.0.0 Domain Controller 3: 0.0.0.0 BaseDN: example.com Encrypted: no Timeout: 60 Enabled: no Attribute: CiscoAvPair Group Authorization: yes Global Catalog 1: 192.0.20.11 Global Catalog 2: 0.0.0.0 Global Catalog 3: 0.0.0.0 Server#
Command |
Description |
set base-dn |
|
set dc |
|
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 the main BIOS configuration settings, use the show main command.
show main [detail]
detail | (Optional) Displays detailed main BIOS configuration settings in list format. |
None
BIOS (/bios)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example displays the main BIOS configuration details:
Server# scope bios Server /bios # show main detail Set-up parameters: Boot option retry: Disabled POST Error Pause: Disabled Server /bios #
Command |
Description |
scope main |
|
To display manufacturer data for a storage adapter, use the show mfg-data command.
show mfg-data [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display manufacturer data for a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show mfg-data PCI Slot SAS: Manufactured Date: 2009-09-19 Rework Date: Revision No: Battery FRU: server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
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 TCP offload of the host interface, use the show offload command.
show offload [detail]
detail | (Optional) Displays detailed information in list format. |
None
Host Ethernet interface (/chassis/adapter/host-eth-if)
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
VM FEX interface (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added to the VM FEX interface. |
This example shows how to display the TCP offload of the host Ethernet interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # show offload TCP Segment Offload TCP Rx Checksum TCP Tx Checksum Large Receive -------------------- ---------------- ---------------- ------------- Enabled Enabled Enabled Enabled Server /chassis/adapter/host-eth-if #
Command |
Description |
set tcp-segment-offload |
|
set tcp-rx-checksum-offload |
|
set tcp-tx-checksum-offload |
|
To display operational profile information about a Cisco Flexible Flash controller, use the show operational-profile command.
show operational-profile [detail]
detail | (Optional) Displays detailed information in list format. |
None
FlexFlash (/chassis/flexflash)
Release | Modification |
---|---|
1.3(3) | This command was introduced. |
This example shows how to display operational profile information about the first flash device:
Server# scope chassis Server /chassis # scope flexflash FlexFlash-0 Server /chassis/flexflash # show operational-profile detail FlexFlash Operational Profile: Primary Member Slot: slot1 I/O Error Threshold: 0 Host Accessible VDs: SCU HV Drivers HUU Server /chassis/flexflash #
Command |
Description |
scope operational-profile |
|
To display the properties of installed PCI adapters, use the show pci-adapter command.
show pci-adapter [detail]
detail | (Optional) Displays detailed properties of installed PCI adapters in list format. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example displays the pci-adapter configuration details:
Server# scope chassis Server /chassis # show pci-adapter Name Slot Vendor ID Device ID Product Name ---------------- ------ ---------------- ---------------- ------------------------- PCIe Adapter1 7 0x8086 0x10fb Intel 10 Gbps 2 port x... PCIe Adapter2 6 0x14e4 0x164f Broadcom 57711 10 Gbps... PCIe Adapter3 3 0x8086 0x10e8 Intel 1 Gbps 4 port E1... PCIe Adapter4 2 0x1077 0x8000 Qlogic QLE 8152-CNA 10... Server /chassis #
Command |
Description |
scope chassis |
|
To display PCI information for a storage adapter, use the show pci-info command.
show pci-info [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display PCI information for a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show pci-info PCI Slot SAS: Vendor ID: 1000 Device ID: 79 SubVendor ID: 1000 SubDevice ID: 9261 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
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 persistent LUN binding of the host Fibre Channel interface, use the show perbi command.
show perbi [detail]
detail | (Optional) Displays detailed information about the persistent LUN binding in list format. |
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display information about the persistent LUN binding of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc 1 Server /chassis/adapter/host-fc-if # scope perbi Server /chassis/adapter/host-fc-if/perbi # show Server /chassis/adapter/host-fc-if/perbi #
Command |
Description |
scope perbi |
|
To display physical drive information for a storage adapter or for a virtual drive, use the show physical-drive command.
show physical-drive drive-number [detail]
drive-number | (Optional) The drive number of the physical drive. |
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Virtual drive (/chassis/storageadapter/virtual-drive)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display detailed physical drive information for physical drive number 1 on the storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show physical-drive 1 detail Slot Number 1: Controller: SAS Status: online Manufacturer: FUJITSU Model: MBD2300RC Predictive Failure Count: 0 Drive Firmware: 5701 Coerced Size: 285568 MB Type: HDD server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display the number of physical drives for a storage adapter, use the show physical-drive-count command.
show physical-drive-count [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display the number of physical drives on the storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show physical-drive-count PCI Slot SAS: Physical Drive Count: 12 Critical Physical Drive Count: 1 Failed Physical Drive Count: 0 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display port information about the host Fibre Channel interface, use the show port command.
show port [detail]
detail | (Optional) Displays detailed port information in list format. |
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display port information for the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # show port I/O Throttle Count Maximum LUNS per Target -------------------- ------------------------ 512 256 Server /chassis/adapter/host-fc-if #
Command |
Description |
show port-p-logi |
|
show port-f-logi |
|
To display information about the Fibre Channel fabric login, use the show port-f-logi command.
show port-f-logi [detail]
detail | (Optional) Displays detailed information about the fabric login in list format. |
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if )
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display information about the fabric login of the host interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # show port-f-logi FLOGI Retries FLOGI Timeout (milli-secs) ------------- ---------------------------- INFINITE 2000 Server /chassis/adapter/host-fc-if #
Command |
Description |
show port-p-logi |
|
To display information about the Fibre Channel port login, use the show port-p-logi command.
show port-p-logi [detail]
detail | (Optional) Displays detailed information about the port login in list format. |
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if )
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display information about the port login of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # show port-p-login PLOGI Retries PLOGI Timeout (milli-secs) ------------- -------------------------- 8 2000 Server /chassis/adapter/host-fc-if #
Command |
Description |
show port-f-logi |
|
To display information about port profiles of the adapter card, use the show port-profiles command.
show port-profiles [detail]
detail | (Optional) Displays detailed information in list format. |
None
Adapter (/chassis/adapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display the port profiles of adapter card 1:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # show port-profiles Port Profile Name -------------------------------- Server /chassis/adapter #
Command |
Description |
set port-profile |
|
To display the server power consumption statistics and the power cap policy, use the show power-cap command.
show power-cap [detail]
detail | (Optional) Displays detailed information about the power consumption statistics and the power cap policy, in list format. |
None
Root (/server#)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
The displayed fields are described in the following table:
Name | Description |
---|---|
Current Consumption |
The power currently being used by the server, in watts. |
Maximum Consumption |
The maximum number of watts consumed by the server since the last time it was rebooted. |
Minimum Consumption |
The minimum number of watts consumed by the server since the last time it was rebooted. |
Minimum Configurable Limit |
The minimum amount of power that can be specified as the peak power cap for this server, in watts. |
Maximum Configurable Limit |
The maximum amount of power that can be specified as the peak power cap for this server, in watts. |
Additional fields are described in the following table:
This example shows how to display detailed information about the DIMMs:
server# show power-cap detail Cur Consumption (W): 247 Max Consumption (W): 286 Min Consumption (W): 229 Minimum Configurable Limit (W): 285 Maximum Configurable Limit (W): 1250 Power Cap Enabled: yes Peak Power: 0 Non Compliance Action: throttle Server#
Command |
Description |
set peak-power |
|
set non-compliance-action |
|
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 host interface receive queue, use the show recv-queue command.
show recv-queue [detail]
detail | (Optional) Displays detailed information in list format. |
None
Host Ethernet interface (/chassis/adapter/host-eth-if )
Host Fibre Channel interface (/chassis/adapter/host-fc-if )
VM FEX interface (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added to the VM FEX interface. |
This example shows how to display information about the host Ethernet interface receive queue:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter/ # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # show recv-queue Receive Queue Count Receive Queue Ring Size ------------------- ------------------------------ 4 512 Server /chassis/adapter/host-eth-if #
Command |
Description |
scope recv-queue |
|
To display information about the Receive-side Scaling (RSS) of the host Ethernet Interface, use the show rss command.
show rss [detail]
detail | (Optional) Displays detailed information in list format. |
None
Host Ethernet interface (/chassis/adapter/host-eth-if)
VM FEX interface (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added to the VM FEX interface. |
This example shows how to display information about RSS:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # show rss TCP Rx Side Scaling -------------------- Enabled Server /chassis/adapter/host-eth-if #
Command |
Description |
scope rss |
|
set rss |
|
To display running firmware information for a storage adapter, use the show running-firmware-images command.
show running-firmware-images [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display running firmware information for a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show running-firmware-images PCI Slot SAS: Firmware Version: 2.120.13-1133 BIOS Version: 3.20.00_4.11.05.00_0x0418A000 Preboot CLI Version: 04.04-017:#%00008 WebBIOS Version: 6.0-34-e_29-Rel NVDATA Version: 2.09.03-0009 Boot Block Version: 2.02.00.00-0000 BOOT Version: 01.250.04.219 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display information about the SCSI-IO of the host Fibre Channel interface, use the show scsi-io command.
show scsi-io
This command has no arguments or keywords.
None
Host Fibre Channel interface (/chassis/adapter/host-fc-if)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
This example shows how to display the SCSI-IO of the host Fibre Channel interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter # scope host-fc-if fc0 Server /chassis/adapter/host-fc-if # scope scsi-io Server /chassis/adapter/host-fc-if/scsi io # show CDB Transmit Queue Count CDB Transmit Ring Size ------------------------- ---------------------------------- 1 512 Server /chassis/adapter/host-fc-if/scsi io #
Command |
Description |
scope scsi-io |
|
To display the server management BIOS configuration settings, use the show server-management command.
show server-management [detail]
detail | (Optional) Displays detailed server management BIOS configuration settings in list format. |
None
BIOS (/bios)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example displays the server management BIOS configuration details:
Server# scope bios Server /bios # show server-management detail Set-up parameters: ACPI1.0 Support: Disabled Assert NMI on PERR: Enabled Assert NMI on SERR: Enabled PlugNPlay BMC detection: Disabled Baud rate: 9.6k Console redirection: Disabled FRB2 Enable: Enabled Flow Control: None Legacy OS redirection: Disabled Terminal type: VT100 Server /bios #
Command |
Description |
scope server-management |
|
To display firmware settings for a storage adapter, use the show settings command.
show settings [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display firmware settings for a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show settings PCI Slot SAS: Predictive Fail Poll Interval: 300 sec Rebuild Rate: 50 MB/s Patrol Read Rate: 30 MB/s Consistency Check Rate: 30 MB/s Reconstruction Rate: 30 MB/s Cache Flush Interval: 4 sec Max Drives to Spin Up at Once: 4 Delay Among Spinup Groups: 2 sec Physical Drive Coercion Mode: None Cluster Mode: false Battery Warning: true ECC Bucket Leak Rate: 1440 min Expose Enclosure Devices: true Maintain PD Fail History: true Enable Copyback on SMART: false Enable Copyback to SSD on SMART Error: true NCQ: false Enable Spin Down of Unconfigured Drives: true Enable SSD Patrol Read: false AutoEnhancedImport: false server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display the SNMP configuration, use the show snmp command.
show snmp [detail]
detail | (Optional) Displays detailed SNMP configuration information in list format. |
None
Root (server#)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
Use this command to display the following SNMP configuration information:
Name | Description |
---|---|
SNMP Port |
The UDP port on which the SNMP agent receives requests. |
System Contact |
The system contact person responsible for the SNMP implementation. |
System Location |
The location of the host on which the SNMP agent runs. |
SNMP Community |
The SNMP v1 or v2c community name or SNMP v3 username that CIMC includes on any trap messages it sends to the SNMP host. |
Enabled |
Whether the SNMP agent is enabled or disabled. |
This example displays the SNMP configuration details:
Server# show snmp detail SNMP Settings: SNMP Port: 161 System Contact: User Name <username@example.com> +1-408-555-1212 System Location: San Jose, California SNMP Community: cimcpublic Enabled: yes Server#
Command |
Description |
scope snmp |
|
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 firmware images to be activated onstartup for a storage adapter, use the show startup-firmware-images command.
show startup-firmware-images [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display startup firmware information for a storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show startup-firmware-images PCI Slot SAS: Startup Firmware Version: N/A Startup BIOS Version: N/A Startup Preboot CLI Version: N/A Startup WebBIOS Version: N/A Startup NVDATA Version: N/A Startup Boot Block Version: N/A Startup BOOT Version: N/A server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display summary information about installed storage adapters, use the show storageadapter command.
show storageadapter [slot] [detail]
slot | (Optional) The PCI slot name or number of a storage adapter. |
detail | (Optional) Displays detailed storage adapter information in list format. |
None
Chassis (/chassis)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display information about the storage adapter in the SAS PCI slot:
Server# scope chassis Server /chassis # show storageadapter SAS PCI Slot SAS: Product Name: LSI MegaRAID SAS 9260-8i Serial Number: SV93404392 Firmware Package Build: 12.12.0-0038 Product ID: LSI Logic Battery Status: fully charged Cache Memory Size: 394 MB Server /chassis #
Command |
Description |
scope storageadapter |
|
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 the host interface transmit queue, use the show trans-queue command.
show trans-queue [detail]
detail | (Optional) Displays detailed information in list format. |
None
Host Ethernet interface (/chassis/adapter/host-eth-if )
Host Fibre Channel interface (/chassis/adapter/host-fc-if )
VM FEX interface (/chassis/adapter/vmfex)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
1.4(1) | This command was added to the VM FEX interface. |
This example shows how to display information about the transmit queue for the host Ethernet interface:
Server# scope chassis Server /chassis # scope adapter 1 Server /chassis/adapter/ # scope host-eth-if eth0 Server /chassis/adapter/host-eth-if # show trans-queue Transmit Queue Count Transmit Queue Ring Size -------------------- ------------------------------- 1 256 Server /chassis/adapter/host-eth-if #
Command |
Description |
scope trans-queue |
|
To display information about SNMP trap destinations, use the show trap-destination command.
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
SNMP (/snmp)
Release | Modification |
---|---|
1.0(1) | This command was introduced. |
1.4(1) | This command was moved from the fault scope to the snmp scope. |
This example shows how to display information about the SNMP trap destinations:
server# scope snmp server /snmp # 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 /snmp #
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 virtual drive information for a storage adapter, use the show virtual-drive command.
show virtual-drive drive-number [detail]
drive-number | (Optional) The drive number of the virtual drive. |
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display virtual drive information for the storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show virtual-drive 1 Virtual Drive Status Name Size RAID Level -------------- -------------------- ------------------------ ---------- ---------- 0 Optimal SLES1SP1beta5 30720 MB RAID 0 1 Optimal RHEL5.5 30720 MB RAID 0 2 Optimal W2K8R2_DC 30720 MB RAID 0 3 Optimal VD_3 30720 MB RAID 0 4 Optimal ESX4.0u2 30720 MB RAID 0 5 Optimal VMs 285568 MB RAID 0 6 Optimal RHEL6-35GB 35840 MB RAID 0 7 Optimal OS_Ins_Test_DR 158720 MB RAID 0 8 Optimal 285568 MB RAID 1 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
To display the number of virtual drives for a storage adapter, use the show virtual-drive-count command.
show virtual-drive-count [detail]
detail | (Optional) Displays detailed information in list format. |
None
Storage adapter (/chassis/storageadapter)
Release | Modification |
---|---|
1.3(1) | This command was introduced. |
This example shows how to display the number of virtual drives on the storage adapter in the SAS PCI slot:
server# scope chassis server /chassis # scope storageadapter SAS server /chassis/storageadapter # show virtual-drive-count PCI Slot SAS: Virtual Drive Count: 9 Degraded Virtual Drive Count: 0 Offline Virtual Drive Count: 0 server /chassis/storageadapter #
Command |
Description |
show storageadapter |
|
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 update the adapter firmware, use the update-adapter-fw command.
update-adapter-fw tftp-ip-address path-and-filename { activate | no-activate } [pci-slot] [pci-slot]
tftp-ip-address | The IP address of the remote server hosting the adapter firmware. |
filename | The path and file name of the adapter firmware on the remote server. |
activate | Activates the new firmware on the next boot. |
no-activate | The new firmware will not be activated on the next boot. |
pci-slot | The PCI slot number of the adapter card. |
Chassis (/chassis)
Release | Modification |
---|---|
1.2(1) | This command was introduced. |
Use this command to download the specified adapter firmware file from the TFTP server, and then install the firmware as the backup image on one or two specified adapters or, if no adapter is specified, on all adapters. If the activate keyword is specified, the new firmware is activated on the next boot.
This example shows how to update and activate the adapter firmware on the adapter in slot 1:
Server # scope chassis Server /chassis # update-adapter-fw 192.0.2.34 /ucs/adapters/adapter4.bin activate 1 Server /chassis #
Command |
Description |
recover-adapter-update |
|
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 |
|