To activate CIMC firmware, use the activate command.
activate
This command has no arguments or keywords.
Command Default
None
Command Modes
Firmware (/cimc/firmware)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
This example shows how to activate CIMC firmware:
server# scope cimc
server /cimc # scope firmware
server /cimc/firmware # activate
server /cimc/firmware #
Related Commands
Command
Description
show cimc
show version
activate-adapter-fw
To activate an adapter firmware image, use the activate-adapter-fw command.
activate-adapter-fwpci-slot image
Syntax Description
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.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
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.
Examples
Examples
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 #
Related Commands
Command
Description
show adapter detail
adapter-reset
To reset the adapter, use the adapter-reset command.
Note
Resetting the adapter also resets the host.
adapter-resetindex
Syntax Description
index
The PCI slot number of the adapter to be reset.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.4(6)
This command was introduced.
Usage Guidelines
Use this command to reset the adapter at the PCI slot number specified by the index argument.
Examples
Example
This example shows how to reset the adapter in PCI slot 1:
Server# scope chassis
Server /chassis # adapter-reset 1
This operation will reset the adapter and the host if it is on.
You may lose connectivity to the CIMC and may have to log in again.
Continue?[y|N] y
Server /chassis #
Related Commands
Command
Description
show adapter detail
adapter-reset-defaults
To reset the adapter to default setting, use the adapter-reset-defaults command.
adapter-reset-defaultsindex
Syntax Description
index
The PCI slot number of the adapter to be reset to factory default settings.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
Use this command to restore factory default settings for the adapter at the PCI slot number specified by the index argument.
Examples
Examples
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
This operation will reset the adapter to factory default.
All your configuration will be lost.
Continue?[y|N] y
Server /chassis #
Related Commands
Command
Description
show adapter detail
bios-setup-defaults
To restore the BIOS settings to default values, use the bios-setup-defaults command.
bios-setup-defaults
This command has no arguments or keywords.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to restore the BIOS settings to default values.
This command initiates a reboot.
Examples
Examples
This example shows how to restore the BIOS settings to default values:
Server# scope bios
Server /bios # bios-setup-default
This operation will reset the BIOS set-up tokens to factory defaults.
All your configuration will be lost.
Changes to BIOS set-up parameters will initiate a reboot.
Continue?[y|N]y
Related Commands
Command
Description
show bios
cancel
To stop the technical support process, use the cancel command.
cancel
This command has no arguments or keywords.
Command Default
None
Command Modes
Technical support (/cimc/tech-support)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
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 #
Related Commands
Command
Description
start
clear (log)
To clear the CIMC log, use the clear command in log mode.
clear
This command has no arguments or keywords.
Command Default
None
Command Modes
Log (/cimc/log)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
This example shows how to clear the CIMC log:
server# scope cimc
server /cimc # scope log
server /cimc/log # clear
server /cimc/log #
Related Commands
Command
Description
show sel
show sensor
clear (sel)
To clear the system event log, use the clear command in sel mode.
clear
This command has no arguments or keywords.
Command Default
None
Command Modes
System event log (/sel)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
This example shows how to clear the system event log:
server# scope sel
server /sel # clear
server /sel #
Related Commands
Command
Description
show sel
show sensor
clear-cmos
To clear the BIOS settings in CMOS memory, use the clear-cmos command.
clear-cmos
This command has no arguments or keywords.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.1(1)
This command was introduced.
Examples
Examples
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 #
Related Commands
Command
Description
show bios
commit
To save configuration changes, use the commit command.
commit
This command has no arguments or keywords.
Command Default
None
Command Modes
Any command mode
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
This example shows how to save a configuration change:
server /http # set enabled yes
server /http* # commit
server http #
Related Commands
Command
Description
discard
configure-vmfex
To specify the number of VM FEX interfaces you want CIMC to create, use the configure-vmfex command.
configure-vmfexport-count
Syntax Description
port-count
The number of VM FEX interfaces to create.
Command Default
None
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify the number of virtual machine fabric extender (VM FEX) interfaces you want CIMC to create. The range is 0 to 112. NIV mode must be enabled.
Examples
Example
This example shows how to specify that 24 VM FEX interfaces are created:
Server# scope chassis
Server /chassis # scope adapter 1
Server /chassis/adapter # set niv-mode enable
Server /chassis/adapter *# configure-vmfex 24
Server /chassis/adapter *# commit
Server /chassis/adapter #
Related Commands
Command
Description
scope vmfex
connect
To connect to either the server CLI or the server shell, use the connect command.
connect
{ host | shell }
Syntax Description
host
Specifies the CLI on the server.
shell
Specifies the GNU bash shell on the server.
Command Default
None
Command Modes
Any command mode
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
Use the exit command to exit the GNU bash shell.
Examples
Examples
This example shows how to connect to the server shell:
server# connect shell
bash-3.2
Related Commands
Command
Description
exit
create-boot-entry
To create a boot entry in the host Fibre Channel interface, use the create-boot-entry command.
create-boot-entrywwpnlun-id
Syntax Description
wwpn
The World Wide Port Name (WWPN) for the boot target.
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.
Examples
Examples
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 #
Related Commands
Command
Description
delete boot
create host-eth-if
To create a virtual Ethernet interface, use the create host-eth-if command.
createhost-eth-ifname
Syntax Description
name
The name of the vNIC.
Command Default
None
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
Use this command to create the virtual host Ethernet network interface card (vNIC). The name argument can be up to 32 ASCII characters.
Examples
Examples
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 #
Related Commands
Command
Description
delete host-eth-if
create host-fc-if
To create a virtual host bus adapter (vHBA), use the create host-fc-if command.
createhost-fc-ifname
Syntax Description
name
The name of the vHBA.
Command Default
None
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to create the virtual Fibre Channel host bus adapter (vHBA). The name argument can be up to 32 ASCII characters.
Examples
Examples
This example shows how to create a vHBA:
Server# scope chassis
Server /chassis # scope adapter 1
Server /chassis/adapter # create host-fc-if Vhba5
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 #
Related Commands
Command
Description
delete host-fc-if
delete boot
To delete a boot entry, use the delete boot command.
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.
Examples
Examples
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 #
Related Commands
Command
Description
create-boot-entry
show-boot
delete host-eth-if
To delete an Ethernet interface, use the delete host-eth-if command.
deletehost-eth-ifname
Syntax Description
name
The name of the vNIC.
Command Default
None
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
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.
Examples
Examples
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 #
Related Commands
Command
Description
create host-eth-if
delete host-fc-if
To delete a vHBA interface, use the delete host-fc-if command.
deletehost-fc-ifname
Syntax Description
name
The name of the vHBA.
Command Default
None
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to delete the specified virtual Fibre Channel host bus adapter (vHBA). You cannot delete either of the two default vHBAs, fc0 or fc1.
Examples
Examples
This example shows how to delete a vHBA:
Server# scope chassis
Server /chassis # scope adapter 1
Server /chassis/adapter # delete host-fc-if Vhba5
Server /chassis/adapter *# commit
New host-fc-if settings will take effect upon the next server reset
Server /chassis/adapter #
Related Commands
Command
Description
create host-fc-if
discard
To discard all configurations, use the discardcommand.
discard
This command has no arguments or keywords.
Command Default
None
Command Modes
Any command mode
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
This example shows how to discard all configurations:
server# discard
server#
Related Commands
Command
Description
show pending
exit
To leave any command mode, use the
exit command.
exit
This command has no arguments or keywords.
Command Default
None
Command Modes
Any command mode
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
This example shows how to exit BIOS command mode:
server /bios # exit
server#
Related Commands
Command
Description
scope
enter
export-config
To export a CIMC configuration, use the export-config command.
export-configtftp-ip-addresspath-and-filename
Syntax Description
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.
Command Default
None
Command Modes
Import-export (/cimc/import-export)
Command History
Release
Modification
1.1(2)
This command was introduced.
Usage Guidelines
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.
Examples
Examples
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 #
Related Commands
Command
Description
import-config
export-vnic
To export the adapter vNIC configuration, use the export-vnic command.
export-vnictftp-address path/name
Syntax Description
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.
Command Default
None
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
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.
Examples
Examples
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 #
Related Commands
Command
Description
import-vnic
factory-default (cimc)
To set the server to factory default, use the factory-default command.
factory-default
This command has no arguments or keywords.
Command Default
None
Command Modes
Cisco Integrated Manangement Controller (/cimc)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
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
generate-csr (certificate)
To generate a Certificate Request Signing (CSR), use the generate-csr command.
generatecsr
This command has no arguments or keywords.
Command Default
None
Command Modes
Certificate (/certificate)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
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 #
Related Commands
Command
Description
show certificate
show ssh
import-config
To import a CIMC configuration, use the import-config command.
import-configtftp-ip-addresspath-and-filename
Syntax Description
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.
Command Default
None
Command Modes
Import-export (/cimc/import-export)
Command History
Release
Modification
1.1(2)
This command was introduced.
Usage Guidelines
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.
Examples
Examples
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 #
Related Commands
Command
Description
export-config
import-vnic
To import the adapter vNIC configuration, use the import-vnic command.
import-vnictftp-address path/name
Syntax Description
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.
Command Default
None
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
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.
Examples
Examples
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 #
Related Commands
Command
Description
export-vnic
locateHDD
To turn on or off a hard disk drive (HDD) locator LED, use the locateHDD command.
locateHDDdrivenum
{ 1 | 2 }
Syntax Description
drivenum
The HDD number.
{1 | 2}
A value of 1 turns the LED on; a value of 2 turns the LED off.
Command Default
None
Command Modes
HDD (/chassis/hdd)
Command History
Release
Modification
1.4(5)
This command was introduced.
Examples
Example
This example turns on the locator LED on HDD 2:
Server# scope chassis
Server /chassis # scope hdd
Server /chassis/hdd # locateHDD 2 1
HDD Locate LED Status changed to 1
Server /chassis/hdd # show
Name Status LocateLEDStatus
-------------------- -------------------- --------------------
HDD1_STATUS present TurnOFF
HDD2_STATUS present TurnON
HDD3_STATUS absent TurnOFF
HDD4_STATUS absent TurnOFF
Server /chassis/hdd #
Related Commands
Command
Description
show hdd
ping (network)
To ping, use the ping command in network mode.
pingaddress
Syntax Description
address
The IP address or the hostname.
Command Default
None
Command Modes
Network (/cimc/network)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
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 #
power (chassis)
To manage server power, use the power command.
power{
cycle |
hard-reset |
off |
on |
shutdown}
Syntax Description
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.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
Examples
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 #
Usage Guidelines
Cycle—Power off, then power on.
Hard reset—Power off, then power on. Equivalent to pressing the front panel reset button, or performing an IPMI reset.
Shutdown—Graceful shut down of the OS, then power off.
Related Commands
Command
Description
show chassis
show psu
reapply (bios)
To reapply the boot order, use the reapplycommand in bios mode.
This command has no arguments or keywords.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.0(1x)
This command was introduced.
Examples
Examples
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 #
Related Commands
Command
Description
set boot-order (bios)
show actual-boot-order
reboot (chassis)
To reboot the server, use the reboot command.
reboot
This command has no arguments or keywords.
Command Default
None
Command Modes
Cisco Integrated Management Controller (/cimc)
Command History
Release
Modification
1.0(1)
This command was introduced.
1.0(1X)
This command was deprecated.
Examples
Examples
This example shows how to reboot the server:
server# scope cimc
server /cimc # reboot
This operation will reboot the BMC.
Continue?[y|n] y
Related Commands
Command
Description
power
rebuild
To rebuild the persistent binding table for the vHBA, use the rebuild command.
Persistent binding must be enabled in the vHBA properties.
Examples
Examples
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 #
Related Commands
Command
Description
show trans-queue
recover (bios)
To recover corrupted BIOS, use the recover command in firmware mode.
recover
This command has no arguments or keywords.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.0(1X)
This command was introduced.
Usage Guidelines
Before executing the recover command, perform the following tasks:
Ensure that the BIOS recovery ISO image is available for your use
Launch the KVM Console
Power off server
Map the BIOS recovery ISO image using
vMedia
Executing the recover command automatically
powers the server on. After the recovery is finished, power cycle or reset the server.
Note
This procedure is not available in some server models.
Examples
Examples
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.
Related Commands
Command
Description
show bios
show version
recover-adapter-update
To clear an incomplete firmware update condition, use the recover-adapter-update command.
recover-adapter-update [pci-slot] [pci-slot]
Syntax Description
pci-slot
The PCI slot number of the adapter card to be cleared. You can specify one or two adapters.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
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.
Examples
Examples
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 #
Related Commands
Command
Description
show adapter
update-adapter-fw
scope adapter
To enter the adapter command mode, use the scope adapter command.
scopeadapterpci-slot
Syntax Description
pci-slot
The PCI slot number of the adapter card.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
Use this command to enter the command mode for the adapter card at the specified PCI slot.
Examples
Examples
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 #
Related Commands
Command
Description
show adapter
scope advanced
To enter the advanced BIOS command mode, use the scopeadvanced command.
scopeadvanced
Syntax Description:
This command has no arguments or keywords.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
Examples
This example enters the advanced BIOS command mode:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced #
Related Commands
Command
Description
show advanced
scope bios
To enter bios mode, use the scope bios command.
scopebios
This command has no arguments or keywords.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use bios mode to set the server boot order:
CDROM—CD-ROM boot
EFI—Extensible Firmware Interface boot
FDD—Floppy disk drive boot
HDD—Hard disk drive boot
PXE—Preboot Execution Environment boot
Examples
Examples
This example shows how to enter BIOS mode:
server# scope bios
server /bios #
Related Commands
Command
Description
show bios
show firmware
scope certificate
To enter certificate mode, use the scope certificate command.
scopecertificate
This command has no arguments or keywords.
Command Default
None
Command Modes
Certificate (/certificate)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use certificate mode to perform the following tasks:
Generate a certificate signing request
Upload a signed certificate
Examples
Examples
This example shows how to enter certificate mode:
server# scope certificate
server /certificate #
Related Commands
Command
Description
generate-csr
show certificate
scope chassis
To enter chassis mode, use the scope chassis command.
scopechassis
This command has no arguments or keywords.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use chassis mode to set the following chassis properties:
Server description
Server locator LED state
Examples
Examples
This example shows how to enter chassis mode:
server# scope chassis
server /chassis #
Related Commands
Command
Description
show chassis
show led
scope cimc
To enter CIMC command mode, use the scope cimc command.
scopecimc
This command has no arguments or keywords.
Command Default
None
Command Modes
Cisco Integrated Management Controller (/cimc)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use cimc mode to perform the following actions:
Reset the CIMC to factory defaults
Reboot the CIMC
Examples
Examples
This example shows how to enter cimc mode :
server# scope cimc
server /cimc #
Related Commands
Command
Description
show cimc
show log (cimc)
scope comp-queue
To enter the completion queue command mode of the host Ethernet interface, use the scope comp-queue command.
This command was added in the VM FEX command mode.
Examples
Examples
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 #
Related Commands
Command
Description
set interrupt-count
scope ipblocking (network)
To enter ipblocking mode, use the scope ipblocking command in network mode.
scope ipblocking
This command has no arguments or keywords.
Command Default
None
Command Modes
IP blocking (/cimc/network/ipblocking)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use ipblocking mode to perform the following tasks:
Enable or disable IP blocking
Set failure count, failure window, and penalty time
Examples
Examples
This example shows how to enter ipblocking mode :
server# scope cimc
server /cimc # scope network
server /cimc/network # scope ipblocking
server /cimc/network/ipblocking #
Related Commands
Command
Description
show ipblocking
set penalty-time
scope ipmi
To enter ipmi mode, use the scope ipmi command.
scope ipmi
This command has no arguments or keywords.
Command Default
None
Command Modes
Intelligent Platform Management Interface (/ipmi)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use ipmi mode to perform the following tasks:
Enable or disable IPMI
Create an encryption key
Set the security privilege level
Examples
Examples
This example shows how to enter ipmi mode :
server# scope ipmi
server /ipmi #
Related Commands
Command
Description
show ipmi
set encryption-key
scope kvm
To enter kvm mode, use the scope kvm command.
scope kvm
This command has no arguments or keywords.
Command Default
None
Command Modes
Keyboard, video and mouse (/kvm)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use kvm mode to set the following KVM properties:
Encryption
KVM port number
Local video
Maximum sessions
Examples
Examples
This example shows how to enter KVM mode :
server# scope kvm
server /kvm #
Related Commands
Command
Description
set max-sessions
show kvm
scope ldap
To enter ldap mode, use the scopeldap command.
scopeldap
This command has no arguments or keywords.
Command Default
None
Command Modes
Lightweight Directory Access Protocol (/ldap)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use ldap mode to perform the following LDAP properties:
Enable or disable LDAP
Set attribute and Base DN (Base Distinguished Name)
Enable encryption
Create LDAP server IP address and connection timeout
Examples
This example shows how to enter ldap mode :
server# scope ldap
server /ldap #
Related Commands
Command
Description
set server-ip
show ldap
scope log (cimc)
To enter log mode, use the scope log command in cimc mode.
scopelog
This command has no arguments or keywords.
Command Default
None
Command Modes
Log (/cimc/log)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use log mode to perform the following tasks:
Clear the CIMC trace log
Display CIMC trace log entries
Examples
This example shows how to enter log mode :
server# scope cimc
server /cimc # scope log
server /cimc/log #
Related Commands
Command
Description
show entries
show log
scope main
To enter the main BIOS command mode, use the scopemain command.
scopemain
Syntax Description:
This command has no arguments or keywords.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
This example enters the main BIOS command mode:
Server# scope bios
Server /bios # scope main
Server /bios/main #
Related Commands
Command
Description
show main
scope network (cimc)
To enter network mode, use the scope network command in cimc mode.
scope network
This command has no arguments or keywords.
Command Default
None
Command Modes
Network (/cimc/network)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use network mode to perform the following tasks:
Enable DHCP and DNS
Create a host name
Set the NIC mode and redundancy
Create an IPv4 IP address, gateway, and netmask
Enable the VLAN membership feature
Examples
This example shows how to enter network mode :
server# scope cimc
server /cimc # scope network
server /cimc/network #
Related Commands
Command
Description
set dhcp-enabled
show network
scope offload
To enter the TCP offload command mode, use the scope offload command.
This command was added in the VM FEX command mode.
Examples
Example
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 #
Related Commands
Command
Description
set tcp-segment-offload
scope operational-profile
To enter the Cisco Flexible Flash operational profile command mode, use the scopeoperational-profile command.
scopeoperational-profile
This command has no arguments or keywords.
Command Default
None
Command Modes
FlexFlash (/chassis/flexflash)
Command History
Release
Modification
1.3(3)
This command was introduced.
Usage Guidelines
Use this command to enter the Cisco Flexible Flash operational profile command mode.
Examples
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 #
Related Commands
Command
Description
set error-count-threshold
set raid-primary-member
set virtual-drives-enabled
scope pef (fault)
To enter pef mode, use the scopepef command in fault mode.
scopepefpef-index
Syntax Description
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.
Command Default
None
Command Modes
Performance event filter (/fault/pef)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
Following is a list of the performance event filter indexes:
1—Temperature Critical Assert Filter
2—Temperature Warning Assert Filter
3—Voltage Critical Assert Filter
4—Current Assert Filter
5—Fan Critical Assert Filter
6—Processor Assert Filter
7—Power Supply Critical Assert Filter
8—Power Supply Warning Assert Filter
9—Power Supply Redundancy Lost Filter
10—Discrete Power Supply Assert Filter
11—Memory Assert Filter
12—Drive Slot Assert Filter
Examples
This example shows how to enter pef mode:
server# scope fault
server /fault # scope pef 3
server /fault/pef #
Related Commands
Command
Description
show pef
scope perbi
To enter the persistent LUN binding command mode for the vHBA, use the scope perbi command.
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 #
Related Commands
Command
Description
set persistent-lun-binding enable
scope physical-drive
To enter the physical drive command mode, use the scopephysical-drive command.
scopephysical-drivedrive-number
Syntax Description
drive-number
The drive number of the physical drive.
Command Default
None
Command Modes
Storage adapter (/chassis/storageadapter)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
You can use the physical-drive command mode to display general, inquiry, and status information about a physical drive.
Examples
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 #
Related Commands
Command
Description
show physical-drive
scope port
To enter the Fibre Channel port command mode, use the scope port command.
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 #
Related Commands
Command
Description
set max-target-luns
set outstanding-io-count
scope port-f-logi
To enter the Fibre Channel fabric login command mode, use the scope port-f-logi command.
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 #
Related Commands
Command
Description
set flogi-retries
set flogi-timeout
scope port-p-logi
To enter the Fibre Channel port login command mode, use the scope port-p-logi command.
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 #
Related Commands
Command
Description
set plogi-retries
set plogi-timeout
scope recv-queue
To enter the receive queue command mode, use the scope recv-queue command.
This command was added in the VM FEX command mode.
Examples
Example
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 #
Related Commands
Command
Description
set rss
scope scsi-io
To enter the SCSI I/O command mode, use the scope scsi-io command.
scopescsi-io
This command has no arguments or keywords.
Command Default
None
Command Modes
SCSI-IO (/chassis/adapter/host-fc-if/scsi-io)
Command History
Release
Modification
1.2(1)
This command was introduced.
Examples
Example
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 #
Related Commands
Command
Description
set cdb-wq-count
scope sel
To enter sel mode, use the scope sel command.
scopesel
This command has no arguments or keywords.
Command Default
None
Command Modes
System event log (/sel)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use sel mode to perform the following tasks:
Clear the system event log
Show configuration and system event log entries
Examples
This example shows how to enter sel mode :
server# scope sel
server /sel #
Related Commands
Command
Description
show entries
show sel
scope sensor
To enter sensor mode, use the scope sensor command.
scopesensor
This command has no arguments or keywords.
Command Default
None
Command Modes
Sensor (/sensor)
Command History
Release
Modification
1.0(1X)
This command was introduced.
Usage Guidelines
You use sensor mode to display fan, psu, psu-redundancy, temperature, and voltage sensors information.
Examples
This example shows how to enter sensor mode :
server# scope sensor
server /sensor #
Related Commands
Command
Description
show fan
show voltage
scope server-management
To enter the server management BIOS command mode, use the scopeserver-management command.
scopeserver-management
Syntax Description:
This command has no arguments or keywords.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
This example enters the server management BIOS command mode:
Server# scope bios
Server /bios # scope server-management
Server /bios/server-management #
Related Commands
Command
Description
show server-management
scope server (log)
To enter the command mode for a remote syslog server profile, use the scopeserver command.
scopeserver
{ 1 | 2 }
Syntax Description
1
Selects remote syslog server profile number 1.
2
Selects remote syslog server profile number 2.
Command Default
None
Command Modes
CIMC log (/cimc/log)
Command History
Release
Modification
1.1(2)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set enabled (server)
set server-ip
scope snmp
To enter the SNMP command mode, use the scopesnmp command.
scopesnmp
Syntax Description:
This command has no arguments or keywords.
Command Default
None
Command Modes
SNMP (/snmp)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
You can use the SNMP command mode to configure SNMP parameters such as location and contact.
Examples
This example shows how to enter SNMP command mode:
server# scope snmp
server /snmp #
Related Commands
Command
Description
scope trap-destination
show snmp
scope sol
To enter sol mode, use the scope sol command.
scope sol
This command has no arguments or keywords.
Command Default
None
Command Modes
Serial over LAN (/sol)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use sol mode to perform the following tasks:
Enable or disable SoL
Set the baud rate
Examples
This example shows how to enter sol mode :
server# scope sol
server /sol #
Related Commands
Command
Description
set baud-rate
show sol
scope ssh
To enter ssh mode, use the scope ssh command.
scopessh
This command has no arguments or keywords.
Command Default
None
Command Modes
Secure Shell (/ssh)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use ssh mode to perform the following tasks:
Enable or disable SSH
Set the SSH port number and connection timeout interval
Examples
This example shows how to enter ssh mode :
server# scope ssh
server /ssh #
Related Commands
Command
Description
set timeout (/ssh)
show ssh
scope storageadapter
To enter the storageadapter command mode, use the scopestorageadapter command.
scopestorageadapterslot
Syntax Description
slot
The PCI slot name or number of the storage adapter.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
You can use the storage adapter command mode to view storage adapter parameters such as the following:
Firmware images and versions
PCI information
Manufacturing information
Battery backup unit information
Supported RAID levels
Harware information
Error counters
Examples
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 #
Related Commands
Command
Description
show storageadapter
scope tech-support (cimc)
To enter tech-support mode, use the scope tech-support command in cimc mode.
scope tech-support
This command has no arguments or keywords.
Command Default
None
Command Modes
Technical support (/cimc/tech-support)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use tech-support mode to set up the TFTP path and server address.
Examples
This example shows how to enter tech-support mode :
server# scope cimc
server /cimc # scope tech-support
server /cimc/tech-support #
Related Commands
Command
Description
show tech-support
start
scope trans-queue
To enter the transmit queue command mode, use the scope trans-queue command.
This command was added in the VM FEX command mode.
Examples
Example
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 #
Related Commands
Command
Description
set wq-count
set wq-ring-size
scope trap-destination
To enter trap-destination command mode, use the scopetrap-destination command.
scopetrap-destinationtrap-destination-index
Syntax Description
trap-destination-index
The index of a specific trap destination profile.
Command Default
None
Command Modes
Trap destination (/snmp/trap-destination)
Command History
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.
Usage Guidelines
Use this command to access the four configurable trap destination profiles, identified by index numbers 1 through 4.
Examples
This example shows how to enter trap-destination mode:
Server# scope fault
Server /snmp # scope trap-destination 4
Server /snmp/trap-destination #
To enter user-session mode, use the scope user-session command.
scopeuser-sessionindex
Syntax Description
index
The session ID of a specific user session.
Command Default
None
Command Modes
User session (/user-session)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use user-session mode to display details about user sessions.
Examples
This example shows how to enter user-session mode :
server# scope user-session 31
server /user-session #
Related Commands
Command
Description
show user
show user-session
scope v3users
To enter the command mode for an SNMPv3 user, use the scope v3users command.
scopev3usersuser-index
Syntax Description
user-index
The number of the user to configure.
Command Default
None
Command Modes
SNMP (/snmp)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to enter the command mode for an SNMPv3 user. Specify a user number between 1 and 15.
Examples
This example enters the command mode for SNMPv3 user number 1:
Server# scope snmp
Server /snmp # scope v3users 1
Server /snmp/v3users #
Related Commands
Command
Description
show v3users
scope virtual-drive
To enter the virtual drive command mode, use the scopevirtual-drive command.
scopevirtual-drivedrive-number
Syntax Description
drive-number
The drive number of the virtual drive.
Command Default
None
Command Modes
Storage adapter (/chassis/storageadapter)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show virtual-drive
scope vmedia
To enter vmedia mode, use the scope vmedia command.
scope vmedia
This command has no arguments or keywords.
Command Default
None
Command Modes
Virtual media (/vmedia)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
You use vmedia mode to perform the following tasks:
Enable virtual media services
Enable encryption
Examples
This example shows how to enter vmedia mode :
server# scope vmedia
server /vmedia #
Related Commands
Command
Description
set
show vmedia
scope vmfex
To enter the VM FEX command mode, use the scope vmfex command.
scopevmfexport-id
Syntax Description
port-id
The name or number of the host Ethernet interface.
Command Default
None
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to enter the virtual machine fabric extender (VM FEX) command mode for the specified host Ethernet interface. NIV mode must be enabled.
Examples
Example
This example shows how to enter the VM FEX command mode for the host Ethernet interface named pts0:
Server# scope chassis
Server /chassis # scope adapter 1
Server /chassis/adapter # scope vmfex pts0
Server /chassis/adapter/vmfex #
Related Commands
Command
Description
show vmfex
sendSNMPtrap
To send a test message to the SNMP trap destination, use the sendSNMPtrap command.
sendSNMPtrap
Syntax Description:
This command has no arguments or keywords.
Command Default
None
Command Modes
SNMP trap destination (/snmp/trap-destination)
Command History
Release
Modification
1.3(1)
This command was introduced.
1.4(1)
This command was moved from the fault scope to the snmp scope.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
scope trap-destination
set ACPI10Support
To specify whether the BIOS publishes the ACPI 1.0 version, use the setACPI10Support command.
setACPI10Support
{ Disabled | Enabled }
Syntax Description
Disabled
The ACPI 1.0 version is not published.
Enabled
The ACPI 1.0 version is published.
Command Default
The ACPI 1.0 version is not published.
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show server-management
set action (pef)
To set up an action for a performance event filter, use the setaction command in pef mode.
Following is a list of the performance event filter indexes:
1—Temperature Critical Assert Filter
2—Temperature Warning Assert Filter
3—Voltage Critical Assert Filter
4—Current Assert Filter
5—Fan Critical Assert Filter
6—Processor Assert Filter
7—Power Supply Critical Assert Filter
8—Power Supply Warning Assert Filter
9—Power Supply Redundancy Lost Filter
10—Discrete Power Supply Assert Filter
11—Memory Assert Filter
12—Drive Slot Assert Filter
Examples
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 #
Related Commands
Command
Description
show pef
set ActiveVideo
To specify how the server displays video, use the setActiveVideo command.
setActiveVideo
{ Auto | Onboard_Device }
Syntax Description
Auto
The server uses an external graphics adapter for display if one is available.
Onboard_Device
The server always uses its internal graphics adapter even if an external graphics adapter is available.
Command Default
The server uses an external graphics adapter for display if one is available (Auto).
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(1)
This command was introduced.
Examples
This example specifies that the server always uses its internal graphics adapter and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set ActiveVideo Onboard_Device
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set addr (trap-destination)
To assign an IP address to an SNMP trap destination index, use the setaddr command in trap-destination mode.
setaddrip-address
Syntax Description
ip-address
The IP address of the trap destination. The format is x.x.x.x.
Command Default
None
Command Modes
SNMP trap destination (/snmp/trap-destination)
Command History
Release
Modification
1.0(1)
This command was introduced.
1.4(1)
This command was moved from the fault scope to the snmp scope.
Examples
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 #
Related Commands
Command
Description
show trap-destination
set AdjacentCacheLinePrefetch
To specify whether the processor uses the Intel Adjacent Cache Line Prefetch mechanism, use the setAdjacentCacheLinePrefetch command.
The Adjacent Cache Line Prefetch mechanism is not used.
Enabled
The Adjacent Cache Line Prefetch mechanism is used when cache issues are detected.
Command Default
The Adjacent Cache Line Prefetch mechanism is used when cache issues are detected.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set CPUPerformance
show advanced
set alternate-dns-server
To specify the IP address of the secondary DNS server, use the setalternate-dns-server command.
setalternate-dns-serverdns2-ipv4-address
Syntax Description
dns2-ipv4-address
The IP address of the secondary DNS server.
Command Default
None
Command Modes
Network (/cimc/network)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
set preferred-dns-server
show network
set Altitude
To specify the approximate number of meters above sea level at which the physical server is installed, use the setAltitude command.
The server is approximately 300 meters above sea level.
900_M
The server is approximately 900 meters above sea level.
1500_M
The server is approximately 1500 meters above sea level.
3000_M
The server is approximately 3000 meters above sea level.
Command Default
The server is approximately 300 meters above sea level.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Examples
This example specifies that the server is installed at approximately 900 meters above sea level and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set Altitude 900_M
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set AssertNMIOnPERR
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 setAssertNMIOnPERR command.
setAssertNMIOnPERR
{ Disabled | Enabled }
Syntax Description
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.
Command Default
Enabled
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set AssertNMIOnSERR
show server-management
set AssertNMIOnSERR
To specify whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a system error (SERR) occurs, use the setAssertNMIOnSERR command.
setAssertNMIOnSERR
{ Disabled | Enabled }
Syntax Description
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.
Command Default
Enabled
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set AssertNMIOnPERR
show server-management
set ATS
To specify whether the processor supports Intel VT-d Address Translation Services (ATS), use the setATS command.
setATS
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not support ATS.
Enabled
The processor uses VT-d ATS as required.
Command Default
The processor uses VT-d ATS as required.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show advanced
set attribute
To specify the LDAP attribute, use the setattribute command.
setattributeattribute-name
Syntax Description
attribute-name
The name of the attribute. The name can be up to 64 characters.
Command Default
None
Command Modes
LDAP (/ldap)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show ldap
set base-dn
To specify the top level domain name of the LDAP hierarchy, use the setbase-dn command.
setbase-dnbase-dn-name
Syntax Description
base-dn-name
The name of the LDAP Base DN. The name can contain up to 63 characters.
Command Default
None
Command Modes
LDAP (/ldap)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show ldap
set baud-rate
To specify the baud rate for serial over LAN (SoL) communications, use the setbaud-rate command.
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.
Examples
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 #
Related Commands
Command
Description
show server-management
set BMCPnP
To specify whether the system automatically detects the BMC in ACPI-compliant operating systems, use the setBMCPnP command.
setBMCPnP
{ Disabled | Enabled }
Syntax Description
Disabled
The system never automatically detects the BMC.
Enabled
The system automatically detects the BMC whenever possible.
Command Default
Disabled
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show server-management
set boot
To enable or disable remote boot for an adapter interface, use the set boot command.
setboot
{ disable | enable }
Syntax Description
disable
Disables remote boot.
enable
Enables remote boot.
Command Default
Remote boot is disabled for default vHBAs and user-created vNICs, and enabled for default vNICs.
To set the boot order for the server, use the setboot-order command in BIOS mode.
setboot-orderboot-list
Syntax Description
boot-list
A comma-separated list of boot devices.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
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:
hdd
pxe
fdd
efi
cdrom
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.
Examples
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 #
Related Commands
Command
Description
show bios
show actual-boot-order
set BootOptionRetry
To specify whether the BIOS retries NON-EFI based boot options without waiting for user input, use the setBootOptionRetry command.
setBootOptionRetry
{ Disabled | Enabled }
Syntax Description
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.
Command Default
The BIOS waits for user input before retrying NON-EFI based boot options.
Command Modes
Main BIOS (/bios/main)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
scope main
show main
set boot-override
To specify a device that will override the default boot priority the next time the server boots, use the setboot-override command.
setboot-override
{ None | SCU | HV | HUU }
Syntax Description
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.
Command Default
None
Command Modes
BIOS (/bios)
Command History
Release
Modification
1.3(3)
This command was introduced.
Usage Guidelines
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.
Examples
Example
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 #
Related Commands
Command
Description
show bios
set cdb-wq-count
To set the number of command descriptor block (CDB) transmit queue resources to allocate, use the set cdb-wq-count command.
setcdb-wq-countcount
Syntax Description
count
The number of command descriptor block (CDB) transmit queue resources to allocate. The range is 1 to 8. The default count is 1.
Command Default
The default count is 1.
Command Modes
SCSI-IO (/chassis/adapter/host-fc-if/scsi-io )
Command History
Release
Modification
1.2(1)
This command was introduced.
Examples
Example
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 #
Related Commands
Command
Description
set cdb-wq-ring-size
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.
setcdb-wq-ring-sizesize
Syntax Description
size
The number of descriptors in the command descriptor block (CDB) transmit queue. The range is 64 to 512.
Command Default
The default descriptor number is 512.
Command Modes
SCSI-IO (/chassis/adapter/host-fc-if/scsi-io )
Command History
Release
Modification
1.2(1)
This command was introduced.
Examples
Example
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 #
Related Commands
Command
Description
set cdb-wq-count
set channel-number
To specify the Network Interface Virtualization (NIV) channel number, use the set channel-number command.
setchannel-numbernumber
Syntax Description
number
The NIV channel number. Specify a number between 1 and 1000.
To use this command, you must enable NIV mode for the adapter.
Examples
Example
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 #
Related Commands
Command
Description
set niv-mode
show host-eth-if
set ChannelInterLeave
To specify how the CPU performs interleaving of memory blocks, use the setChannelInterLeave command.
The maximum amount of channel interleaving is used.
Command Default
The CPU determines what interleaving is done.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Usage Guidelines
Use this command to specify how the CPU divides memory blocks and spreads contiguous portions of data across interleaved channels to enable simultaneous read operations.
Examples
This example configures the CPU to perform the maximum amount of channel interleaving and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set ChannelInterLeave 8_Way
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set Ck410bConfigSpreadSpectrumEnable
To enable spread spectrum clock modulation for EMI reduction, use the set Ck410bConfigSpreadSpectrumEnable command.
The server does not use the spread spectrum function.
Enabled
The server uses the spread spectrum function.
Command Default
The server uses the spread spectrum function.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(3)
This command was introduced.
Usage Guidelines
Use this command to enable spread spectrum clock modulation. Spread Spectrum modulates the pulses produced by the clock on the motherboard in order to reduce the EMI (Electromagnetic Interference) generated by those pulses.
Examples
This example specifies that the server uses the spread spectrum function and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set Ck410bConfigSpreadSpectrumEnable Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set CkeLowPolicy
To specify the DIMM power savings mode policy, use the setCkeLowPolicy command.
setCkeLowPolicy
{ Auto | Disabled | Fast | Slow }
Syntax Description
Auto
The BIOS controls when a DIMM enters power saving mode based on the DIMM configuration.
Disabled
DIMMs do not enter power saving mode.
Fast
DIMMs enter power saving mode as often as possible.
Slow
DIMMs can enter power saving mode, but the requirements are higher. Therefore, DIMMs enter power saving mode less frequently.
Command Default
The BIOS controls when a DIMM enters power saving mode (Auto).
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(1)
This command was introduced.
Examples
This example specifies that DIMMs enter power saving mode as often as possible and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set CkeLowPolicy Fast
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set cli output
To change the CLI output, use the setclioutput command.
setclioutput
{ default |
| yaml }
Syntax Description
cli output
Specifies server CLI output.
default
Sets CLI output to default.
yaml
Sets CLI ouput to YAML (YAML Ain't Markup Language).
Command Default
None
Command Modes
Any command mode
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
This example shows how to change the CLI output to YAML:
server# set cli output yaml
CLI output format set to yaml
server#
set coalescing-time
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.
setcoalescing-timeusec
Syntax Description
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).
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
Related Commands
Command
Description
set coalescing-type
set coalescing-type
To set the coalescing type of the host Ethernet interface, use the set coalescing-type command.
setcoalescing-type
{ idle | min }
Syntax Description
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.
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 #
Related Commands
Command
Description
set coalescing-time
set CoherencySupport
To specify whether the processor supports Intel VT-d Coherency, use the setCoherencySupport command.
setCoherencySupport
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not support coherency.
Enabled
The processor uses Intel VT-d Coherency as required.
Command Default
The processor does not support Intel VT-d Coherency.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show advanced
set community-str
To specify the SNMP community name, use the setcommunity-str command.
setcommunity-strcommunity
Syntax Description
community
The SNMP v1 or v2c community name or SNMP v3 username.
Command Default
None
Command Modes
SNMP (/snmp)
Command History
Release
Modification
1.3(1)
This command was introduced.
1.4(1)
This command was moved from the fault command mode.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show snmp
set comport
To set the serial port through which the system routes serial over LAN (SoL) communications, use the setcomport command.
Note
This field is only available on some C-Series servers. If it is not available, the server always uses COM port 0 for SoL communication.
setcomport
{ com0 | com1 }
Syntax Description
com0
SoL communication is routed through COM port 0, an externally accessible serial port that supports either a physical RJ45 connection to an external device or a virtual SoL connection to a network device.
If you select this option, the system enables SoL and disables the RJ45 connection, which means that the server can no longer support an external serial device.
com1
SoL communication is routed through COM port 1, an internal port accessible only through SoL.
If you select this option, you can use SoL on COM port 1 and the physical RJ45 connection on COM port 0.
Command Default
None
Command Modes
Serial over LAN (/sol)
Command History
Release
Modification
1.4(6)
This command was introduced.
Usage Guidelines
Use this command to specify the COM port for serial port communications.
Note
Changing the comport setting disconnects any existing SoL sessions.
Examples
This example configures SoL communication to be routed through COM port 1 on the serial port and commits the transaction:
Server# scope sol
Server /sol # set comport com1
Server /sol *# set enabled yes
Server /sol *# commit
Server /sol #
Related Commands
Command
Description
show sol
set ConfigSATAMode
To specify the mode in which the SATA controller runs, use the setConfigSATAMode command.
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.
Command Default
The controller enables both AHCI and RAID.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
Note
This command is not available on all models and configurations.
Examples
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 #
Related Commands
Command
Description
show advanced
set ConsoleRedir
To allow a serial port to be used for console redirection during POST and BIOS booting, use the setConsoleRedir command.
setConsoleRedir
{ Disabled | Serial_Port_A }
Syntax Description
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.
Command Default
Disabled
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show server-management
set CoreMultiProcessing
To set the state of logical processor cores in a package, use the setCoreMultiProcessing command.
setCoreMultiProcessing
{ All | number }
Syntax Description
All
Enables multi processing on all logical processor cores.
number
The number of logical processor cores that can run on the server.
Command Default
Multi processing is enabled on all logical processor cores.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show advanced
set cos
To specify the CoS value to be marked by an interface, use the set cos command.
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.
Examples
Example
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 #
Related Commands
Command
Description
set trust-host-cos
set CpuEngPerfBias
To specify whether system performance or energy efficiency is more important on this server, use the setCpuEngPerfBias command.
Balanced, but energy efficiency is more important.
Balanced_Performance
Balanced, but performance is more important.
Energy_Efficient
Energy efficiency is most important.
Performance
Performance is most important.
Command Default
Balanced Performance
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(4)
This command was introduced.
Usage Guidelines
Note
The server ignores the setting for this command unless Power Management is set to Custom in the GUI, or the set CPUPowerManagement command is set to Custom in the CLI.
In addition, some operating systems, such as Windows 2008, ignore this parameter in favor of their own power plan.
Examples
This example specifies that energy efficiency is most important on this server and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set CpuEngPerfBias Energy_Efficient
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set CPUPowerManagement
set CpuFreqFloor
To specify whether the CPU is allowed to drop below the maximum non-turbo frequency when idle, use the setCpuFreqFloor command.
setCpuFreqFloor
{ Disabled | Enabled }
Syntax Description
Disabled
The CPU can drop below the maximum non-turbo frequency when idle. This option decreases power consumption but may reduce system performance.
Enabled
The CPU cannot drop below the maximum non-turbo frequency when idle. This option improves system performance but may increase power consumption.
Command Default
The CPU can drop below the maximum non-turbo frequency when idle.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Examples
This example configures the CPU to prevent dropping below the maximum non-turbo frequency when idle and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set CpuFreqFloor Disabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set CPUPerformance
To set the CPU performance profile for the server, use the setCPUPerformance command.
All performance profile options can be configured from the BIOS setup on the server.
Enterprise
Only the Data Cache Unit (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.
Command Default
The processor classifies memory areas.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
Use this command to set the CPU performance profile for the server. The performance profile consists of the following options:
Adjacent Cache-Line Prefetch
Data Reuse Optimization
Data Cache Unit (DCU) Streamer Prefetcher
DCU IP Prefetcher
Hardware Prefetcher
When the Custom option is selected, you can also configure the listed options using their individual commands.
Examples
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 #
Related Commands
Command
Description
set AdjacentCacheLinePrefetch
set DcuIpPrefetch
set DcuStreamerPrefetch
set HardwarePrefetch
set CPUPowerManagement
To configure the CPU power management settings, use the setCPUPowerManagement command.
The server uses the individual settings for a set of BIOS parameters.
Disabled
The server performs no CPU power management.
Energy_Efficient
The server determines the best settings for CPU power management.
Command Default
The server determines the best settings for CPU power management.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(4)
This command was introduced.
Usage Guidelines
Use this command to configure the CPU power management settings for the following options:
Enhanced Intel Speedstep Technology
Intel Turbo Boost Technology
Processor Power State C6
The CPU power management setting can be one of the following:
Custom—The server uses the individual settings for the BIOS parameters mentioned above. You must select this option if you want to change any of these BIOS parameters.
Disabled—The server does not perform any CPU power management and any settings for the BIOS parameters mentioned above are ignored.
Energy_Efficient—The server determines the best settings for the BIOS parameters mentioned above and ignores the individual settings for these parameters.
Examples
This example enables the individual settings for the related BIOS parameters and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set CPUPowerManagement Custom
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set EnhancedIntelSpeedStep
set IntelTurboBoostTech
set ProcessorC6Report
set cq-count
To set the number of completion queue resources to allocate, use the set cq-count command.
setcq-countcount
Syntax Description
count
The number of completion queue resources to allocate. The range is 1 to 512.
In general, the number of completion queues equals the number of transmit queues plus the number of receive queues.
Examples
Example
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 #
Related Commands
Command
Description
show comp-queue
set dc
To specify an Active Directory domain controller, use the set dc command.
setdcndc-host
Syntax Description
n
The index of the AD domain controller entry.
dc-host
The host name or IP address of the AD domain controller.
Command Default
None
Command Modes
LDAP (/ldap)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify the host name or IP address of an Active Directory (AD) domain controller (DC). CIMC can store up to three DCs for AD. Use an index number of 1 to 3 to store the server information.
Examples
Example
This example shows how to store an AD domain controller IP address as DC number 2:
Server# scope ldap
Server /ldap # set dc2 192.0.20.123
Server /ldap* # commit
Server /ldap #
Related Commands
Command
Description
set gc
show ldap
set DcuIpPrefetch
To enable or disable the DCU IP prefetcher, use the setDcuIpPrefetch command.
setDcuIpPrefetch
{ Disabled | Enabled }
Syntax Description
Disabled
The DCU IP prefetcher is disabled.
Enabled
The DCU IP prefetcher is enabled.
Command Default
The DCU IP prefetcher is enabled.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(4)
This command was introduced.
Usage Guidelines
Use this command to specify whether the processor uses the Data Cache Unit (DCU) Instruction Pointer-based (IP) Prefetch mechanism to analyze historical cache access patterns and preload the most relevant lines in the L1 cache. This can be one of the following:
Disabled—The processor does not preload any cache data.
Enabled—The DCU IP prefetcher preloads the L1 cache with the data it determines to be the most relevant.
Examples
This example enables the DCU IP prefetcher and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set DcuIpPrefetch Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set CPUPerformance
set DcuStreamerPrefetch
set DcuStreamerPrefetch
To specify whether the processor uses the Data Cache Unit (DCU) Prefetch mechanism, use the setDcuStreamerPrefetch command.
setDcuStreamerPrefetch
{ Disabled | Enabled }
Syntax Description
Disabled
The DCU Prefetch mechanism is disabled.
Enabled
The DCU Prefetch mechanism is enabled.
Command Default
The DCU Prefetch mechanism is enabled.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(4)
This command was introduced.
Usage Guidelines
Use this command to specify whether the processor uses the Data Cache Unit (DCU) Prefetch mechanism to determine if the processor should fetch the next line in the L1 cache before the line is actually requested. This can be one of the following:
Disabled—The processor does not try to anticipate cache read requirements and only fetches explicitly requested lines.
Enabled—The DCU prefetcher analyzes the cache read pattern and prefetches the next line in the cache if it determines that it may be needed.
Examples
This example enables the DCU Prefetch mechanism and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set DcuStreamerPrefetch Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set CPUPerformance
set DcuIpPrefetch
set delay
To specify whether server power is restored after a fixed or random time, use the setdelay command.
setdelay
{ fixed | random }
Syntax Description
fixed
Server power is restored after a fixed time.
random
Server power is restored after a random time.
Command Default
Server power is restored after a fixed time.
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set policy
set delay-value
set delay-value
To specify the delay time for restoring server power after an outage, use the setdelay-value command.
setdelay-valuedelay
Syntax Description
delay
The delay time in seconds.
Command Default
The default delay is 0 seconds.
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set policy
set delay
set DemandScrub
To specify whether the system corrects single bit memory errors encountered when the CPU or I/O makes a demand read, use the setDemandScrub command.
setDemandScrub
{ Disabled | Enabled }
Syntax Description
Disabled
Single bit memory errors are not corrected.
Enabled
Single bit memory errors are corrected in memory and the corrected data is set in response to the demand read.
Command Default
Single bit memory errors are corrected.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Examples
This example disables single bit memory errors and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set DemandScrub Disabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set description (chassis)
To set up a description for the chassis, use the setdescription command in chassis mode.
setdescriptionchassis-description
Syntax Description
chassis-description
The description of the chassis. The range of valid values is 1 to 64.
Command Default
None
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
This example shows how to :
server# scope chassis
server /chassis # set description testServer
server /chassis* # commit
server /chassis #
Related Commands
Command
Description
show chassis
set dhcp-enabled
To specify whether the CIMC uses DHCP to obtain an IP address, use the setdhcp-enabled command.
setdhcp-enabled
{ no | yes }
Syntax Description
no
The CIMC does not use DHCP to obtain an IP address.
yes
The CIMC uses DHCP to obtain an IP address.
Command Default
The CIMC does not use DHCP to obtain an IP address.
Command Modes
Network (/cimc/network)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show network
set DirectCacheAccess
To specify whether the processor can increase I/O performance by placing data from I/O devices directly into the processor cache, use the setDirectCacheAccess command.
setDirectCacheAccess
{ Disabled | Enabled }
Syntax Description
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.
Command Default
Data from I/O devices is placed directly into the processor cache.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show advanced
set DisableSCU
To specify whether the onboard software RAID controller is available to the server, use the setDisableSCU command.
setDisableSCU
{ Disabled | Enabled }
Syntax Description
Disabled
The software RAID controller is not available.
Enabled
The software RAID controller is available.
Command Default
The software RAID controller is not available.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Examples
This example specifies that the onboard software RAID controller is available to the server and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set DisableSCU Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set dns-use-dhcp
To specify whether the CIMC uses DHCP to obtain DNS server addresses, use the setdns-use-dhcp command.
setdns-use-dhcp
{ no | yes }
Syntax Description
no
The CIMC does not use DHCP to obtain DNS server addresses.
yes
The CIMC uses DHCP to obtain DNS server addresses.
Command Default
The CIMC does not use DHCP to obtain DNS server addresses.
Command Modes
Network (/cimc/network)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show network
set domain
To specify the Active Directory domain for an authorization group, use the setdomain command.
setdomaindomain-name
Syntax Description
domain-name
The Active Directory domain in which the group must reside.
Command Default
None
Command Modes
LDAP role group (/ldap/role-group)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify the Active Directory (AD) domain for an authorization group.
Examples
This example configures the domain name and other settings for an AD authorization group:
Server# scope ldap
Server /ldap # set group-auth yes
Server /ldap *# scope role-group 5
Server /ldap/role-group *# set name Training
Server /ldap/role-group *# set domain example.com
Server /ldap/role-group *# set role readonly
Server /ldap/role-group *# commit
Server /ldap/role-group #
Related Commands
Command
Description
scope role-group
set enabled
To enable or disable functions and actions on the server, use the set enabled command.
set enabled
{ no | yes }
Syntax Description
no
Disables the function or action.
yes
Enables the function or action.
Command Default
See the Usage Guidelines.
Command Modes
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)
Command History
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.
Usage Guidelines
Use this command to enable or disable a function or action. For the supported command modes, the following actions are enabled when yes is selected:
CIMC log server — Enables the sending of CIMC log entries to a remote syslog server. The default is disabled.
HTTP — Enables HTTP services on the server. The default is enabled.
IP blocking — Enables the blocking of login after several failed attempts. The default is disabled.
IPMI — Enables IPMI on the server. The default is enabled.
Keyboard Video Mouse — Enables KVM connections to CIMC. The default is enabled.
LDAP — Enables IPMI services on the server. The default is disabled.
Secure shell — Enables SSH services on the server. The default is enabled.
Serial over LAN — Enables SoL on the server. The default is disabled.
Trap destination — Enables SNMP trap destination services. The default is disabled.
User — Enables the user account.
Virtual media — Enables virtual media services on the server. The default is enabled.
XML API — Enables XML API access to CIMC on the server.
Examples
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 #
Related Commands
Command
Description
set encrypted
To enable or disable the encryption of information, use the setencrypted command.
setencrypted
{ no |
| yes }
Syntax Description
no
Information is not encrypted.
yes
Information is encrypted.
Command Default
Video information sent through the KVM is not encrypted.
The Active Directory is not encrypted.
Virtual media data is not encrypted.
Command Modes
KVM (/kvm)
LDAP (/ldap)
Virtual media (/vmedia)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
Use this command to enable or disable the encryption of data in the following command modes:
KVM command mode — Enables or disables the encryption of video information sent through the KVM.
LDAP command mode — Enables or disables the encryption of the Active Directory.
Virtual media command mode — Enables or disables the encryption of virtual media data.
Examples
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 #
Related Commands
Command
Description
show kvm
show ldap
show vmedia
set encryption-key
To specify the encryption key for IPMI communications, use the setencryption-key command.
setencryption-keyencryption-key
Syntax Description
encryption-key
The encryption key for IPMI communications. The key value must be 40 hexadecimal numbers.
Command Default
None
Command Modes
IPMI (/ipmi)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show ipmi
set EnhancedIntelSpeedStep
To specify whether the processor uses Enhanced Intel SpeedStep Technology, use the setEnhancedIntelSpeedStep command.
setEnhancedIntelSpeedStep
{ Disabled | Enabled }
Syntax Description
Disabled
The processor never dynamically adjusts its voltage or frequency.
Enabled
The processor uses Enhanced Intel SpeedStep Technology if required.
Command Default
The processor uses Enhanced Intel SpeedStep Technology if required.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
We recommend that you contact your operating system vendor to make sure the operating system supports this feature.
Note
The server ignores the setting for this command unless Power Management is set to Custom in the GUI, or the set CPUPowerManagement command is set to Custom in the CLI.
Examples
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 #
Related Commands
Command
Description
set CPUPowerManagement
set error-count-threshold
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.
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.
Examples
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 #
Related Commands
Command
Description
scope operational-profile
set error-detect-timeout
To set the error detection timeout value (EDTOV), use the set error-detect-timeout command.
seterror-detect-timeoutmsec
Syntax Description
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.
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 #
Related Commands
Command
Description
set resource-allocation-timeout
set ExecuteDisable
To classify memory areas on the server to specify where application code can execute, use the setExecuteDisable command.
setExecuteDisable
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not classify memory areas.
Enabled
The processor classifies memory areas.
Command Default
The processor classifies memory areas.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show advanced
set fail-count
To specify a limit on the number of unsuccessful login attempts, use the setfail-count command.
setfail-countfail-count
Syntax Description
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.
Command Default
The default failure count is 5 attempts.
Command Modes
IP blocking (/cimc/network/ipblocking)
Command History
Release
Modification
1.0(1X)
This command was introduced.
Usage Guidelines
The number of unsuccessful login attempts must occur within the time frame specified in the IP Blocking Fail Window setting.
Examples
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 #
Related Commands
Command
Description
set fail-window
show ipblocking
set fail-window
To specify a time window for unsuccessful login attempts, use the setfail-window command.
setfail-windowfail-window
Syntax Description
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.
Command Default
The default failure window is 60 seconds.
Command Modes
IP blocking (/cimc/network/ipblocking)
Command History
Release
Modification
1.0(1X)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
set fail-count
show ipblocking
set fc-rq-ring-size
To specify the receive queue ring size for the Fibre Channel interface, use the set fc-rq-ring-size command.
setfc-rq-ring-sizesize
Syntax Description
size
The Fibre Channel receive queue ring size. Specify a number between 64 and 128.
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 #
Related Commands
Command
Description
show recv-queue
set fc-wq-ring-size
To specify the transmit queue ring size for the Fibre Channel interface, use the set fc-wq-ring-size command.
setfc-wq-ring-sizesize
Syntax Description
size
The Fibre Channel transmit queue ring size. Specify a number between 64 and 128.
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 #
Related Commands
Command
Description
show trans-queue
set fcp-error-recovery
To set the FCP Error Recovery, use the set fcp-error-recovery command.
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 #
Related Commands
Command
Description
set link-down-timeout
set port-down-io-retry-count
set fip-mode
To enable or disable FCoE Initialization Protocol (FIP) on the adapter card, use the set fip-mode command.
setfip-mode
{ disabled | enabled }
Syntax Description
disabled
Disables FIP mode on the card.
enabled
Enables FIP mode on the card.
Command Default
FIP mode is enabled.
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.2(1)
This command was introduced.
Usage Guidelines
Note
Note: We recommend that you disable this option only when explicitly directed to do so by a technical support representative.
Examples
Example
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 #
Related Commands
Command
Description
show adapter detail
set flogi-retries
To specify the fabric login (FLOGI) retries value, use the set flogi-retries command.
setflogi-retries
{ infinite | count }
Syntax Description
infinite
Specifies infinite FLOGI retries.
count
Specifies the number of FLOGI retries. Enter a number between 0 and 4294967295.
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 #
Related Commands
Command
Description
set flogi-timeout
set flogi-timeout
To set the fabric login (FLOGI) timeout value, use the set flogi-timeout command.
setflogi-timeoutmsec
Syntax Description
msec
The number of milliseconds that the system waits before it tries to log in again. The range is 1 to 255000.
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 #
Related Commands
Command
Description
set flogi-retries
set FlowCtrl
To specify whether a handshake protocol is used for flow control, use the setFlowCtrl command.
setFlowCtrl
{ None | RTS-CTS }
Syntax Description
None
No flow control is used.
RTS-CTS
RTS/CTS is used for flow control.
Command Default
No flow control is used.
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show server-management
set FRB-2
To specify whether the FRB2 timer is used by CIMC to recover the system if it halts during POST, use the setFRB-2 command.
setFRB-2
{ Disabled | Enabled }
Syntax Description
Disabled
The FRB2 timer is not used.
Enabled
The FRB2 timer is started during POST and used to recover the system if necessary.
Command Default
The FRB2 timer is started during POST and used to recover the system if necessary.
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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).
Examples
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 #
Related Commands
Command
Description
show server-management
set gc
To specify an Active Directory global catalog server, use the set gc command.
setgcngc-host
Syntax Description
n
The index of the AD global catalog server entry.
gc-host
The host name or IP address of the AD global catalog server.
Command Default
None
Command Modes
LDAP (/ldap)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify the host name or IP address of an Active Directory (AD) global catalog (GC) server. CIMC can store up to three GC servers for AD. Use an index number of 1 to 3 to store the server information.
Examples
Example
This example shows how to store an AD global catalog server IP address as GC server number 2:
Server# scope ldap
Server /ldap # set gc2 192.0.20.11
Server /ldap* # commit
Server /ldap #
Related Commands
Command
Description
set dc
show ldap
set group-auth
To enable Active Directory authorization groups, use the set group-auth command.
setgroup-auth
{ yes | no }
Syntax Description
yes
AD authorization groups are enabled.
no
AD authorization groups are disabled.
Command Default
AD authorization groups are disabled.
Command Modes
LDAP (/ldap)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to enable Active Directory (AD) authorization groups. When AD groups are enabled, user authentication is also done on the group level for users who are not found in the local user database or who are not individually authorized to use CIMC in the Active Directory.
Examples
Example
This example shows how to enable AD authorization groups:
Server# scope ldap
Server /ldap # set group-auth yes
Server /ldap* # commit
Server /ldap #
Related Commands
Command
Description
scope role-group
set HardwarePrefetch
To specify whether the processor uses the Intel hardware prefetcher, use the setHardwarePrefetch command.
setHardwarePrefetch
{ Disabled | Enabled }
Syntax Description
Disabled
The hardware prefetcher is not used.
Enabled
The hardware prefetcher is used when cache issues are detected.
Command Default
The hardware prefetcher is used when cache issues are detected.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set CPUPerformance
show advanced
set hostname
To specify the host name of the server, use the sethostname command.
sethostnamehost-name
Syntax Description
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.
Command Default
None
Command Modes
Network (/cimc/network)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show network
set http-port
To set the port number for Hyper Text Transfer Protocol (HTTP) services on the server, use the sethttp-port command.
sethttp-portport-number
Syntax Description
port-number
The HTTP port number of the server. The range of valid values is 1 to 65536.
Command Default
The default HTTP port number is 80.
Command Modes
HTTP (/http)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show http-port
show https-port
set http-redirect
To redirect HTTP requests to HTTPS on the server, use the sethttp-redirect command.
sethttp-redirect
{ yes | no }
Syntax Description
yes
HTTP requests are redirected to HTTPS.
no
HTTP requests are not redirected to HTTPS.
Command Default
HTTP requests are redirected to HTTPS.
Command Modes
HTTP (/http)
Command History
Release
Modification
1.4(1)
This command was introduced.
Examples
This example shows how to redirect HTTP requests to HTTPS on the server:
Server# scope http
Server /http # set http-redirect yes
Server /http* # commit
Server /http #
Related Commands
Command
Description
set https-port
set https-port
To set the port number for Hyper Text Transfer Protocol (HTTPS) services on the server, use the sethttps-port command in http mode.
sethttps-portport-number
Syntax Description
port-number
The HTTPS port number of the server. The range of valid values is 1 to 65536.
Command Default
The default port number is 443.
Command Modes
HTTP (/http)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
This example shows how to set the HTTPS port number:
server# scope http
server /http # set https-port 443
server /http* # commit
server /http #
Related Commands
Command
Description
set inform-type
To specify whether SNMP notification messages are sent as simple traps or as inform requests, use the setinform-type command.
setinform-type
{ inform | trap }
Syntax Description
inform
SNMP notification messages are sent as inform requests.
trap
SNMP notification messages are sent as simple traps.
Command Default
SNMP notification messages are sent as simple traps.
Command Modes
SNMP (/snmp)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify whether SNMP notification messages are sent as simple traps or as inform requests requiring acknowledgment by the receiver.
SNMP must be enabled and saved before this command can be accepted.
Examples
This example specifies that notifications are sent as inform requests and commits the transaction:
scope snmp
Server /snmp # set enabled yes
Server /snmp *# commit
Server /snmp # set inform-type inform
Server /snmp *# commit
Server /snmp # show detail
SNMP Settings:
SNMP Port: 161
System Contact:
System Location:
SNMP Community:
SNMP Trap community: public-trap
Enabled: yes
SNMP Trap Version: 1
SNMP Inform Type: inform
Server /snmp #
Related Commands
Command
Description
show snmp
set IntelHyperThread
To specify whether the processor uses Intel Hyper-Threading Technology, use the setIntelHyperThread command.
setIntelHyperThread
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not permit hyperthreading.
Enabled
The processor allows for the parallel execution of multiple threads.
Command Default
The processor allows for the parallel execution of multiple threads.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show advanced
set IntelTurboBoostTech
To specify whether the processor uses Intel Turbo Boost Technology, use the setIntelTurboBoostTech command.
setIntelTurboBoostTech
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not automatically increase its frequency.
Enabled
The processor uses Intel Turbo Boost Technology if required.
Command Default
The processor uses Intel Turbo Boost Technology if required.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
Intel Turbo Boost Technology allows the processor to automatically increase its frequency if it is running below power, temperature, or voltage specifications.
Note
The server ignores the setting for this command unless Power Management is set to Custom in the GUI, or the set CPUPowerManagement command is set to Custom in the CLI.
Examples
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 #
Related Commands
Command
Description
set CPUPowerManagement
set IntelVT
To specify whether the processor uses Intel Virtualization Technology, use the setIntelVT command.
setIntelVT
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not permit virtualization.
Enabled
The processor allows virtualization.
Command Default
The processor allows virtualization.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show advanced
set IntelVTD
To specify whether the processor uses Intel Virtualization Technology for Directed I/O (VT-d), use the setIntelVTD command.
setIntelVTD
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not use virtualization technology for directed I/O.
Enabled
The processor uses virtualization technology for directed I/O.
Command Default
The processor uses virtualization technology for directed I/O.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show advanced
set interrupt-count
To specify the number of interrupt resources, use the set interrupt-count command.
setinterrupt-countcount
Syntax Description
count
The number of interrupt resources. The range is 1 to 514.
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 #
Related Commands
Command
Description
set coalescing-time
set coalescing-type
set interrupt-mode
To set the Ethernet interrupt mode, use the set interrupt-mode command.
setinterrupt-mode { intx | msi | msix }
Syntax Description
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.
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 #
Related Commands
Command
Description
set interrupt-count
set InterruptRemap
To specify whether the processor supports Intel VT-d Interrupt Remapping, use the setInterruptRemap command.
setInterruptRemap
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not support remapping.
Enabled
The processor uses VT-d Interrupt Remapping as required.
Command Default
The processor uses VT-d Interrupt Remapping as required.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show advanced
set kvm-port
To specify the port used for KVM communication, use the setkvm-port command.
setkvm-portport-number
Syntax Description
port-number
The port used for KVM communication.
Command Default
Port number 2068 is used for KVM communication.
Command Modes
KVM (/kvm)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show kvm
set LaunchPXEOptionROM
To specify whether the server can perform a PXE boot, use the setLaunchPXEOptionROM command.
setLaunchPXEOptionROM
{ Disabled | Enabled }
Syntax Description
Disabled
The server cannot perform a PXE boot.
Enabled
The server can perform a PXE boot.
Command Default
The server can perform a PXE boot.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(4)
This command was introduced.
Examples
This example specifies that the server can perform a PXE boot and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set LaunchPXEOptionROM Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
set LegacyOSRedir
To specify whether redirection from a legacy operating system, such as DOS, is enabled on the serial port, use the setLegacyOSRedir command.
setLegacyOSRedir
{ Disabled | Enabled }
Syntax Description
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.
Command Default
Disabled
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show server-management
set LegacyUSBSupport
To specify whether the system supports legacy USB devices, use the setLegacyUSBSupport command.
setLegacyUSBSupport
{ Auto | Disabled | Enabled }
Syntax Description
Auto
Disables legacy USB support if no USB devices are connected.
Disabled
USB devices are available only to EFI applications.
Enabled
Legacy USB support is always available.
Command Default
Legacy USB support is always available.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(4)
This command was introduced.
Examples
This example specifies that legacy USB support is always available and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set LegacyUSBSupport Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set UsbEmul6064
set link-down-timeout
To set the link down timeout of the host Fibre Channel Interface, use the set link-down-timeout command.
setlink-down-timeoutmsec
Syntax Description
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.
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
set local-syslog-severity
To specify the lowest level of messages that will be included in the CIMC log, use the setlocal-syslog-severity command.
setlocal-syslog-severitylevel
Syntax Description
level
The lowest level of messages that will be included in the CIMC log. See the Usage Guidelines for valid values.
Command Default
Messages of level Debug and higher are logged.
Command Modes
CIMC log (/cimc/log)
Command History
Release
Modification
1.4(3)
This command was introduced.
Usage Guidelines
The severity level can be one of the following, in decreasing order of severity:
emergency
alert
critical
error
warning
notice
informational
debug
CIMC does not log any messages with a severity below the selected severity. For example, if you select error, the CIMC log will contain all messages with the severity Emergency, Alert, Critical, or Error. It will not show Warning, Notice, Informational, or Debug messages.
Examples
Example
This example shows how to configure the logging of messages with a minimum severity of Warning:
Server# scope cimc
Server /cimc # scope log
Server /cimc/log # set local-syslog-severity warning
Server /cimc/log *# commit
Server /cimc/log #
Related Commands
Command
Description
show local-syslog-severity
set local-video
To enable or disable the display of the KVM session on any monitor attached to the server, use the setlocal-video command.
setlocal-video
{ no |
| yes }
Syntax Description
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.
Command Default
The KVM session is displayed on any monitor attached to the server.
Command Modes
KVM (/kvm)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show kvm
set locator-led
To turn the server locator LED on or off, use the setlocator-led command.
This command was added in the physical drive mode.
Usage Guidelines
Use this command to turn on or off the locator LED for the chassis or a physical drive.
Examples
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 #
Related Commands
Command
Description
show chassis
show led
set LomOpromControlPortn
To specify whether Option ROM is available on a legacy LOM port, use the setLomOpromControlPortn command.
setLomOpromControlPortn
{ Disabled | Enabled }
Syntax Description
n
Specifies a legacy LOM port number.
Disabled
Option ROM is not available on the specified LOM port.
Enabled
Option ROM is available on the specified LOM port.
Command Default
Option ROM is available on legacy LOM ports.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Usage Guidelines
Use this command to specify whether Option ROM is available on the legacy LOM port designated by n in the command name set LomOpromControlPortn.
Examples
This example specifies that Option ROM is not available on the legacy LOM port 2 and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set LomOpromControlPort2 Disabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set LvDDRMode
To specify whether the system prioritizes low voltage or high frequency memory operations, use the setLvDDRMode command.
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.
Command Default
The system prioritizes low voltage memory operations over high frequency memory operations.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show advanced
set mac-addr
To specify a MAC address for an interface, use the set mac-addr command.
setmac-addrmac-addr
Syntax Description
mac-addr
Specifies a MAC address in the form hh:hh:hh:hh:hh:hh or hhhh:hhhh:hhhh.
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 #
Related Commands
Command
Description
set MakeUSBDeviceNonBootable
To specify whether the server can boot from a USB device, use the setMakeUSBDeviceNonBootable command.
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 #
Related Commands
Command
Description
set USBController
show advanced
set ManagedBootRule
To specify how the server changes the boot order list defined through the CIMC GUI or CLI when there are no devices of a particular device type available or when the user defines a different boot order using the server's BIOS Setup Utility, use the set ManagedBootRule command.
setManagedBootRule
{ Strict | Loose }
Syntax Description
Strict
When no devices of a particular type are available, the system creates a placeholder for that device type in the boot order list. When a device of that type becomes available, it is added to the boot order in the previously defined position.
If the user defines a boot order through the server's BIOS Setup Utility, that boot order is given priority over the boot order configured through the CIMC GUI or CLI. All device types defined through CIMC that are not present in the boot order defined through the BIOS Setup Utility are removed from the boot order list.
Loose
When no devices of a particular type are available, the system removes that device type from the boot order. When a device of that type becomes available, the system adds it to the end of the boot order list.
If the boot order is configured through the server's BIOS Setup Utility, that boot order is given priority over the boot order configured through the CIMC GUI or CLI. All device types defined through CIMC that are not present in the boot order defined through the BIOS Setup Utility are moved to the end of the boot order list.
Command Default
The Boot Order Rules option is loose.
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.4(6)
This command was introduced.
Usage Guidelines
Use this command to specify how the server changes the boot order list defined through the CIMC GUI or CLI when there are no devices of a particular device type available or when the user defines a different boot order using the server's BIOS Setup Utility, use the set ManagedBootRule command.
The supported device types are:
HDD—Hard disk drive
FDD—Floppy disk drive
CDROM—Bootable CD-ROM or DVD
PXE—PXE boot
EFI—Extensible Firmware Interface
Examples
This example changes the Boot Order Rules option to strict and commits the transaction:
Server# scope bios
Server /bios # scope server-management
Server /bios/server-management # set ManagedBootRule Strict
Server /bios/server-management *# commit
Server /bios/server-management #
Related Commands
Command
Description
show actual-boot-order (bios)
set max-data-field-size
To specify the maximum data field size for the Fibre Channel interface, use the set max-data-field-size command.
setmax-data-field-sizesize
Syntax Description
size
The maximum data field size. Specify a number between 256 and 2112.
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 #
Related Commands
Command
Description
show host-fc-if detail
set max-sessions
To specify the maximum number of concurrent KVM sessions allowed, use the setmax-sessions command.
setmax-sessionssessions
Syntax Description
sessions
The maximum number of concurrent KVM sessions allowed. This can be an integer between 1 and 4.
Command Default
A maximum of four concurrent KVM sessions is allowed.
Command Modes
KVM (/kvm)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show kvm
set max-target-luns
To set the maximum logical unit numbers (LUNs) per target, use the set max-target-luns command.
setmax-target-lunscount
Syntax Description
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.
Command Default
The default is 256 LUNs.
Command Modes
Port (/chassis/adapter/host-fc-if/port)
Command History
Release
Modification
1.2(1)
This command was introduced.
Examples
Example
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 #
Related Commands
None
set MemoryMappedIOAbove4GB
To enable or disable memory mapped I/O of 64-bit PCI devices to 4GB or greater address space, use the setMemoryMappedIOAbove4GB command.
setMemoryMappedIOAbove4GB
{ Disabled | Enabled }
Syntax Description
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.
Command Default
The server does not map I/O of 64-bit PCI devices to 4GB or greater address space.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show advanced
set MirroringMode
To specify how memory is mirrored, use the setMirroringMode command.
setMirroringMode
{ Intersocket | Intrasocket }
Syntax Description
Intersocket
Each IMC is mirrored across two sockets.
Intrasocket
One IMC is mirrored with another IMC in the same socket.
Command Default
One IMC is mirrored with another IMC in the same socket.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify how memory is mirrored. Mirroring is supported across Integrated Memory Controllers (IMCs) where one memory riser is mirrored with another.
Note
This command is operative only if the set SelectMemoryRAS command is set to Mirroring.
Examples
This example configures memory mirroring across two sockets and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set SelectMemoryRAS Mirroring
Server /bios/advanced *# set MirroringMode Intersocket
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set SelectMemoryRAS
show advanced
set mode
To specify the server NIC mode, use the setmode command.
The management Ethernet port is used to access the CIMC.
shared_lom
The LAN On Motherboard (LOM) Ethernet host ports are used to access the CIMC.
Note
If you select Shared LOM, make sure that all host ports belong to the same subnet.
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.
Command Default
None
Command Modes
Network (/cimc/network)
Command History
Release
Modification
1.0(1)
This command was introduced.
1.0(1x)
The shipping keyword was introduced.
Examples
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 #
Related Commands
Command
Description
show network
set mtu
To specify an MTU for a vNIC, use the set mtu command.
setmtumtu-value
Syntax Description
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.
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 #
Related Commands
Command
Description
set name
To specify a user name, use the setname command.
setnameuser-name
Syntax Description
user-name
The name of the user. The name can contain up to 70 characters.
Command Default
None
Command Modes
User (/user)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show user
set NIC-ROM
To enable or disable an onboard NIC ROM, use the setNIC-ROM command.
setNIC-n-ROM
{ Disabled | Enabled }
Syntax Description
n
The number of the onboard NIC ROM.
Disabled
The onboard NIC ROM is disabled.
Enabled
The onboard NIC ROM is enabled.
Command Default
The onboard NIC ROM is enabled.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to enable or disable an onboard network interface card (NIC) ROM.
Examples
This example disables the onboard NIC 2 ROM and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set NIC-2-ROM Disabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set niv-mode
To enable or disable Network Interface Virtualization (NIV) on the adapter card, use the set niv-mode command.
setniv-mode
{ disabled | enabled }
Syntax Description
disabled
Disables NIV mode on the card.
enabled
Enables NIV mode on the card.
Command Default
NIV mode is disabled.
Command Modes
Adapter (/chassis/adapter)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
Use this command to enable or disable NIV mode on the adapter card. When NIV mode is enabled, vNICs have the following features:
Can be assigned to a specific channel
Can be associated with a port profile
Can fail over to another vNIC if there are communication problems
Examples
Example
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 #
Related Commands
Command
Description
show adapter
set non-compliance-action
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 setnon-compliance-action command.
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.
Command Default
None
Command Modes
Power cap (/power-cap)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set peak-power
show power-cap
set NUMAOptimize
To specify whether the BIOS supports Non-Uniform Memory Access (NUMA), use the setNUMAOptimize command.
setNUMAOptimize
{ Disabled | Enabled }
Syntax Description
Disabled
The BIOS does not support NUMA.
Enabled
The BIOS includes the ACPI tables that are required for NUMA-aware operating systems.
Command Default
NUMA support is enabled.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
show advanced
set OEMAESNIControl
To specify whether the server uses the AES-NI encryption instruction set, use the set OEMAESNIControl command.
setOEMAESNIControl
{ Disabled | Enabled }
Syntax Description
Disabled
The server does not use the AES-NI instruction set.
Enabled
The server uses the AES-NI instruction set when possible.
Command Default
The server does not use the AES-NI instruction set.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(3)
This command was introduced.
Usage Guidelines
Use this command to specify whether the server uses the processor's AES-NI (New Instructions) encryption instruction set that improves on the Advanced Encryption Standard (AES) algorithm.
Examples
This example specifies that the server uses the processor's AES-NI instruction set and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set OEMAESNIControl Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set OnboardNic1
To enable or disable the first onboard Network Interface Card (NIC) on the server, use the setOnboardNic1 command.
setOnboardNic1
{ Disabled | Enabled }
Syntax Description
Disabled
NIC 1 is not available.
Enabled
NIC 1 is available.
Command Default
NIC 1 is available.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set OnboardNic1ROM
show advanced
set OnboardNic1ROM
To specify whether the system loads the embedded PXE option ROM for the first onboard NIC on the server, use the setOnboardNic1ROM command.
setOnboardNic1ROM
{ Disabled | Enabled }
Syntax Description
Disabled
The PXE option ROM is not available for NIC 1.
Enabled
The PXE option ROM is available for NIC 1.
Command Default
The PXE option ROM is available for NIC 1.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set OnboardNic1
show advanced
set OnboardSATA
To specify whether the server uses its onboard built-in SATA controller, use the setOnboardSATA command.
setOnboardSATA
{ Disabled | Enabled }
Syntax Description
Disabled
The server does not use its onboard built-in SATA controller.
Enabled
The server uses its onboard built-in SATA controller.
Command Default
The server uses its onboard built-in SATA controller.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
Note
This command is not available on all models and configurations.
Examples
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 #
Related Commands
Command
Description
show advanced
set OptionROMPriority
To specify which Option ROM the server should launch, use the setOptionROMPriority command.
The server launches the EFI compatible PCI Option ROM.
Legacy_ROM
The server launches the legacy PCI Option ROM.
Command Default
The server launches the EFI compatible PCI Option ROM.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(4)
This command was introduced.
Usage Guidelines
If the server has both legacy and EFI compatible PCI Option ROMs, this command specifies which Option ROM the server should launch.
Examples
This example specifies that the server launches the EFI compatible PCI Option ROM and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set OptionROMPriority EFI_Compatible_ROM
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set MemoryMappedIOAbove4GB
set order
To specify the relative order of this device for PCI bus device number assignment, use the set order command.
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.
Examples
Example
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 #
Related Commands
Command
Description
set OSBootWatchdogTimer
To specify whether the BIOS programs the operating system boot watchdog timer with a timeout value, use the setOSBootWatchdogTimer command.
setOSBootWatchdogTimer
{ Disabled | Enabled }
Syntax Description
Disabled
The OS boot watchdog timer is disabled.
Enabled
The OS boot watchdog timer is enabled.
Command Default
The OS boot watchdog timer is disabled.
Command Modes
Server Management BIOS (/bios/server-management)
Command History
Release
Modification
1.4(4)
This command was introduced.
Usage Guidelines
Use this command to specify whether the BIOS programs the operating system (OS) boot watchdog timer with a timeout value. This can be one of the following:
Disabled—The watchdog timer is not used to track how long the server takes to boot.
Enabled—The watchdog timer tracks how long the server takes to boot. If the server does not boot within the length of time specified by the set OSBootWatchdogTimerTimeout command, the CIMC logs an error and takes the action specified by the set OSBootWatchdogTimerPolicy command.
Examples
This example enables the OS boot watchdog timer with a duration of 10 minutes and an action of reset and commits the transaction:
Server# scope bios
Server /bios # scope server-management
Server /bios/server-management # set OSBootWatchdogTimer Enabled
Server /bios/server-management *# set OSBootWatchdogTimerTimeout 10_mins
Server /bios/server-management *# set OSBootWatchdogTimerPolicy Reset
Server /bios/server-management *# commit
Server /bios/server-management #
Related Commands
Command
Description
set OSBootWatchdogTimerPolicy
set OSBootWatchdogTimerTimeout
set OSBootWatchdogTimerPolicy
To specify what action the system takes if the operating system boot watchdog timer expires, use the setOSBootWatchdogTimerPolicy command.
Use this command to specify what action the system takes if the operating system (OS) boot watchdog timer expires. This can be one of the following:
Do_Nothing—No action is taken if the OS boot watchdog timer expires.
Power_Down—The server is powered off if the server does not boot before the OS boot watchdog timer expires.
Reset—The server is reset if the server does not boot before the OS boot watchdog timer expires.
The duration of the OS boot watchdog timer is specified by the set OSBootWatchdogTimerTimeout command.
Note
This command is operative only if the OS boot watchdog timer is enabled by the set OSBootWatchdogTimer command.
Examples
This example enables the OS boot watchdog timer with a duration of 10 minutes and an action of reset and commits the transaction:
Server# scope bios
Server /bios # scope server-management
Server /bios/server-management # set OSBootWatchdogTimer Enabled
Server /bios/server-management *# set OSBootWatchdogTimerTimeout 10_mins
Server /bios/server-management *# set OSBootWatchdogTimerPolicy Reset
Server /bios/server-management *# commit
Server /bios/server-management #
Related Commands
Command
Description
set OSBootWatchdogTimer
set OSBootWatchdogTimerTimeout
set OSBootWatchdogTimerTimeout
To specify the duration of the operating system boot watchdog timer, use the setOSBootWatchdogTimerTimeout command.
Use this command to specify the duration of the operating system (OS) boot watchdog timer. If the server does not boot within the length of time specified by this command, the CIMC logs an error and takes the action specified by the set OSBootWatchdogTimerPolicy command.
Note
This command is operative only if the OS boot watchdog timer is enabled by the set OSBootWatchdogTimer command.
Examples
This example enables the OS boot watchdog timer with a duration of 10 minutes and an action of reset and commits the transaction:
Server# scope bios
Server /bios # scope server-management
Server /bios/server-management # set OSBootWatchdogTimer Enabled
Server /bios/server-management *# set OSBootWatchdogTimerTimeout 10_mins
Server /bios/server-management *# set OSBootWatchdogTimerPolicy Reset
Server /bios/server-management *# commit
Server /bios/server-management #
Related Commands
Command
Description
set OSBootWatchdogTimer
set OSBootWatchdogTimerPolicy
set outstanding-io-count
To set the outstanding IO count of the host Fibre Channel interface, use the set outstanding-io-count command.
setoutstanding-io-countcount
Syntax Description
count
Specifies the number of I/O operations that can be pending in the vHBA at one time. The range is 1 to 1024.
Command Default
The default is 512 operations.
Command Modes
Port (/chassis/adapter/host-fc-if/port)
Command History
Release
Modification
1.2(1)
This command was introduced.
Examples
Example
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 #
Related Commands
None
set PackageCStateLimit
To specify the amount of power available to the server components when they are idle, use the setPackageCStateLimit command.
Depending on n, the server provides full power to minimal power to the components. See the Usage Guidelines.
No_Limit
The server may enter any available C state.
Command Default
The default limit is C3_state.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify the amount of power available to the server components when they are idle. This can be one of the following:
C0_state—The server provides all server components with full power at all times. This option maintains the highest level of performance and requires the greatest amount of power.
C1_state—When the CPU is idle, the system slightly reduces the power consumption. This option requires less power than C0 and allows the server to return quickly to high performance mode.
C3_state—When the CPU is idle, the system reduces the power consumption further than with the C1 option. This requires less power than C1 or C0, but it takes the server slightly longer to return to high performance mode.
C6_state—When the CPU is idle, the system reduces the power consumption further than with the C3 option. This option saves more power than C0, C1, or C3, but there may be performance issues until the server returns to full power.
C7_state—When the CPU is idle, the server makes a minimal amount of power available to the components. This option saves the maximum amount of power but it also requires the longest time for the server to return to high performance mode.
No_Limit—The server may enter any available C state.
Note
This command is operative only if the set ProcessorCcxEnable command is set to Enabled.
Examples
This example specifies that a minimal amount of power is made available to the components when the CPU is idle and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set ProcessorCcxEnable Enabled
Server /bios/advanced # set PackageCStateLimit C7_state
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set ProcessorCcxEnable
show advanced
set PassThroughDMA
To specify whether the processor supports Intel VT-d Pass-through DMA, use the setPassThroughDMA command.
setPassThroughDMA
{ Disabled | Enabled }
Syntax Description
Disabled
The processor does not support pass-through DMA.
Enabled
The processor uses VT-d Pass-through DMA as required.
Command Default
The processor uses VT-d Pass-through DMA as required.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show advanced
set password
To specify a user password, use the setpassword command.
setpassworduser-password
Syntax Description
user-password
The password of the user. The password can contain up to 80 characters.
Command Default
None
Command Modes
User (/user)
Command History
Release
Modification
1.0(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show user
set path (tech-support)
To set the TFTP path, use the set path command in tech-support mode.
setpathtftp-path
Syntax Description
tftp-path
The TFTP path.
Command Default
None
Command Modes
Technical support (/cimc/tech-support)
Command History
Release
Modification
1.0(1)
This command was introduced.
Usage Guidelines
Specifies the path to the support data file should be stored.
Perform this task along with settftp-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.
Examples
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 #
Related Commands
Command
Description
set tftp-ip
show tech-support
set PatrolScrub
To specify whether the system actively searches for, and corrects, single bit memory errors, use the setPatrolScrub command.
setPatrolScrub
{ Disabled | Enabled }
Syntax Description
Disabled
The system checks for memory ECC errors only when the CPU reads or writes a memory address.
Enabled
The system periodically reads and writes memory searching for ECC errors.
Command Default
The system periodically reads and writes memory searching for ECC errors.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify whether the system actively searches for, and corrects, single bit memory errors even in unused portions of the memory on the server. If enabled and any errors are found, the system attempts to fix them. This option may correct single bit errors before they become multi-bit errors, but it may adversely affect performance when the patrol scrub is running.
When this function is disabled, the system checks for memory ECC errors only when the CPU reads or writes a memory address.
Examples
This example specifies that the system actively searches for and corrects single bit memory errors and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set PatrolScrub Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set PatrolScrubDuration
show advanced
set PatrolScrubDuration
To specify the interval between each patrol scrub memory access, use the setPatrolScrubDuration command.
setPatrolScrubDurationinterval
Syntax Description
interval
A value between 5 and 23.
Command Default
The interval is 8.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(1)
This command was introduced.
Usage Guidelines
Use this command to specify the interval between each patrol scrub memory access. A lower interval scrubs the memory more often but requires more memory bandwidth.
Note
This command is operative only if the set PatrolScrub command is set to Enabled.
Examples
This example specifies an interval of 20 between each patrol scrub memory access and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set PatrolScrub Enabled
Server /bios/advanced # set PatrolScrubDuration 20
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
set PatrolScrub
show advanced
set Pci-Opt-Roms
To specify whether the server can use the PCIe Option ROM expansion slots, use the setPci-Opt-Roms command.
setPci-Opt-Roms
{ Disabled | Enabled }
Syntax Description
Disabled
The PCIe Option ROMs are not available.
Enabled
The PCIe Option ROMs are available.
Command Default
The PCIe Option ROMs are available.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
show advanced
set PciMezzOptionROM
To specify whether the PCIe mezzanine slot expansion ROM is available to the server, use the setPciMezzOptionROM command.
setPciMezzOptionROM
{ Disabled | Enabled }
Syntax Description
Disabled
The PCIe mezzanine slot expansion ROM is not available to the server.
Enabled
The PCIe mezzanine slot expansion ROM is available to the server.
Command Default
The PCIe mezzanine slot expansion ROM is available to the server.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Examples
This example specifies that the PCIe mezzanine slot expansion ROM is available to the server and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set PciMezzOptionROM Enabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set PcieOptionROMs
To specify whether the server can use the PCIe Option ROM expansion slots, use the setPcieOptionROMs command.
setPcieOptionROMs
{ Disabled | Enabled }
Syntax Description
Disabled
The PCIe Option ROMs are not available.
Enabled
The PCIe Option ROMs are available.
Command Default
The PCIe Option ROMs are available.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Examples
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 PcieOptionROMs Disabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set PcieSlotnOptionROM
To specify whether a PCIe Option ROM expansion slot is available to the server, use the setPcieSlotnOptionROM command.
setPcieSlotnOptionROM
{ Disabled | Enabled }
Syntax Description
n
The number or letter of the PCIe slot.
Disabled
The specified expansion slot is not available.
Enabled
The specified expansion slot is available.
Command Default
The PCIe Option ROM expansion slot is available.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.4(5)
This command was introduced.
Usage Guidelines
Use this command to specify the availability of the PCIe Option ROM expansion slot designated by n in the command name set PcieSlotnOptionROM.
Examples
This example specifies that PCIe Option ROM expansion slot 2 is not available and commits the transaction:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set PcieSlot2OptionROM Disabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set PciOptRomsDisable
To specify whether the server can use the PCIe Option ROM expansion slots, use the setPciOptRomsDisable command.
setPciOptRomsDisable
{ Disabled | Enabled }
Syntax Description
Disabled
The PCIe Option ROMs are not available.
Enabled
The PCIe Option ROMs are available.
Command Default
The PCIe Option ROMs are available.
Command Modes
Advanced BIOS (/bios/advanced)
Command History
Release
Modification
1.3(1)
This command was introduced.
Examples
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 PciOptRomsDisable Disabled
Server /bios/advanced *# commit
Server /bios/advanced #
Related Commands
Command
Description
show advanced
set peak-power
To specify the maximum number of watts that can be allocated to the server, use the setpeak-power command.
setpeak-powerwatts
Syntax Description
watts
The maximum number of watts that can be allocated to the server.
Command Default
Zero watts are allocated.
Command Modes
Power cap (/power-cap)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set non-compliance-action
show power-cap
set penalty-time
To specify a blocking time after multiple login failures, use the setpenalty-time command.
setpenalty-timepenalty-seconds
Syntax Description
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.
Command Default
The default blocking time is 300 seconds.
Command Modes
IP blocking (/cimc/network/ipblocking)
Command History
Release
Modification
1.0(1X)
This command was introduced.
Examples
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 #
Related Commands
Command
Description
set fail-count
show ipblocking
set persistent-lun-binding
To enable or disable the persistent binding for the vHBA, use the set persistent-lun-binding command.
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 #
Related Commands
Command
Description
set plogi-timeout
set plogi-timeout
To set the port login (PLOGI) timeout value of the host Fibre Channel interface, use the set plogi-timeout command.
setplogi-timeoutmsec
Syntax Description
msec
Specifies the number of milliseconds that the system waits before it tries to log in again. The range is 1 to 255000.
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.
Command Default
The default action is power-off.
Command Modes
Chassis (/chassis)
Command History
Release
Modification
1.3(1)
This command was introduced.
Usage Guidelines
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.
Examples
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 #
Related Commands
Command
Description
set delay
set delay-value
set port-down-io-retry-count
To set the port-down-io-retry-count of the host Fibre Channel interface, use the set port-down-io-retry-count command.
setport-down-io-retry-countcount
Syntax Description
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.
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 #
Related Commands
Command
Description
set port-down-timeout
set port-down-timeout
To set the port-down-timeout, use the set port-down-timeout command.
setport-down-timeoutmsec
Syntax Description
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.
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 #
Related Commands
Command
Description
set port-down-io-retry-count
set port-profile (host-eth-if)
To specify a port profile that should be associated with the vNIC, use the set port-profile command in host-eth-if mode.
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.
Examples
Example
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 #
Related Commands
Command
Description
set niv-mode
show port-profiles
set port-profile (network)
To configure the server to connect to the network using a port profile, use the set port-profile command in network mode.
setport-profilename
Syntax Description
name
Specifies the port profile CIMC should use to configure the management interface, the virtual Ethernet, and the VIF on supported adapter cards such as the Cisco UCS VIC1225
Virtual Interface Card.
Enter up to 80 alphanumeric characters. You cannot use spaces or other special characters except for - (hyphen) and _ (underscore). In addition, the port profile name cannot begin with a hyphen.
Note
The port profile must be defined on the switch to which this server is connected.
Command Default
None
Command Modes
network (/network)
Command History
Release
Modification
1.4(6)
This command was introduced.
Usage Guidelines
Use this command to configure the network using a port profile.
Examples
This example connects to port profile abcde12345:
Server# scope cimc
Server /cimc # scope network
Server /cimc/network # set port-profile abcde12345
Server /cimc/network *# commit
Server /cimc/network # show detail
Network Setting:
IPv4 Address: 10.193.66.174
IPv4 Netmask: 255.255.248.0
IPv4 Gateway: 10.193.64.1
DHCP Enabled: no
Obtain DNS Server by DHCP: no
Preferred DNS: 0.0.0.0
Alternate DNS: 0.0.0.0
VLAN Enabled: no
VLAN ID: 1
VLAN Priority: 0
Port Profile: abcde12345
Hostname: Server
MAC Address: 50:3D:E5:9D:63:3C
NIC Mode: dedicated
NIC Redundancy: none
Server /cimc/network #
set POSTErrorPause
To specify the action when the server encounters a critical error during power-on self test (POST), use the setPOSTErrorPause command.