- Preface
- Overview
- Managing the Server
- Viewing Server Properties
- Viewing Server Sensors
- Managing Remote Presence
- Managing User Accounts
- Configuring Network-Related Settings
- Managing Network Adapters
- Configuring Communication Services
- Managing Certificates
- Configuring Platform Event Filters
- CIMC Firmware Management
- Viewing Logs
- Server Utilities
- Index
Managing the Server
This chapter includes the following sections:
- Toggling the Locator LED
- Configuring the Server Boot Order
- Resetting the Server
- Shutting Down the Server
- Managing Server Power
- Configuring Power Policies
- Managing the Flexible Flash Controller
- Configuring BIOS Settings
Toggling the Locator LED
You must log in with user or admin privileges to perform this task.
This example disables the chassis locator LED and commits the transaction:
Server# scope chassis Server /chassis # set locator-led off Server /chassis *# commit Server /chassis #
Configuring the Server Boot Order
![]() Note |
Do not change the boot order while the host is performing BIOS power-on self test (POST). |
You must log in with user or admin privileges to perform this task.
The new boot order will be used on the next BIOS boot.
This example sets the boot order and commits the transaction:
Server# scope bios
Server /bios # set boot-order hdd,cdrom,fdd,pxe,efi
Server /bios *# commit
Server /bios # show detail
BIOS:
Boot Order: HDD,CDROM,FDD,PXE,EFI
Server /bios #
Resetting the Server
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis | Enters chassis command mode. |
| Step 2 | Server /chassis # power hard-reset | After a prompt to confirm, resets the server. |
This example resets the server:
Server# scope chassis Server /chassis # power hard-reset This operation will change the server's power state. Continue?[y|N]
Shutting Down the Server
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis | Enters chassis mode. |
| Step 2 | Server /chassis # power shutdown | Shuts down the server. |
The following example shuts down the server:
Server# scope chassis Server /chassis # power shutdown
Managing Server Power
Powering On the Server
![]() Note |
If the server was powered off other than through the CIMC, the server will not become active immediately when powered on. In this case, the server will enter standby mode until the CIMC completes initialization. |
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis | Enters chassis command mode. |
| Step 2 | Server /chassis # power on | Turns on the server. |
This example turns on the server:
Server# scope chassis Server /chassis # power on This operation will change the server's power state. Continue?[y|N]y Server /chassis # show Power Serial Number Product Name UUID ----- ------------- ------------- ------------------------------------ on Not Specified Not Specified 208F0100020F000000BEA80000DEAD00
Powering Off the Server
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis | Enters chassis command mode. |
| Step 2 | Server /chassis # power off | Turns off the server. |
This example turns 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 # show Power Serial Number Product Name UUID ----- ------------- ------------- ------------------------------------ off Not Specified Not Specified 208F0100020F000000BEA80000DEAD00
Power Cycling the Server
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis | Enters chassis command mode. |
| Step 2 | Server /chassis # power cycle | Power cycles the server. |
This example power cycles the server:
Server# scope chassis Server /chassis # power cycle
Configuring Power Policies
Viewing the Power Statistics
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# show power-cap detail | Displays the server power consumption statistics and the power cap policy. |
The displayed fields are described in the following table:
| Name | Description |
|---|---|
| Current Consumption |
The power currently being used by the server, in watts. |
| Maximum Consumption |
The maximum number of watts consumed by the server since the last time it was rebooted. |
| Minimum Consumption |
The minimum number of watts consumed by the server since the last time it was rebooted. |
| Minimum Configurable Limit |
The minimum amount of power that can be specified as the peak power cap for this server, in watts. |
| Maximum Configurable Limit |
The maximum amount of power that can be specified as the peak power cap for this server, in watts. |
Additional fields are described in the following table:
This example displays the detailed power statistics:
Server# show power-cap detail
Cur Consumption (W): 247
Max Consumption (W): 286
Min Consumption (W): 229
Minimum Configurable Limit (W): 285
Maximum Configurable Limit (W): 1250
Power Cap Enabled: yes
Peak Power: 0
Non Compliance Action: throttle
Server#
Power Capping Policy
The power capping policy determines how server power consumption is actively managed. When power capping is enabled, the system monitors how much power is allocated to the server and attempts to keep the power consumption below the allocated power. If the server exceeds its maximum allotment, the power capping policy triggers the specified non-compliance action.
Configuring the Power Cap Policy
You must log in with admin privileges to perform this task.
This example enables and configures a power cap policy 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 #
Configuring the Power Restore Policy
The power restore policy determines how power is restored to the server after a chassis power loss.
You must log in with admin privileges to perform this task.
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 #
Managing the Flexible Flash Controller
Cisco Flexible Flash
Some C-Series Rack-Mount Servers support an internal Secure Digital (SD) memory card for storage of server software tools and utilities. The SD card is hosted by the Cisco Flexible Flash storage adapter.
The SD storage is available to CIMC as four virtual USB drives. Three are preloaded with Cisco software and the fourth can hold a user-installed hypervisor or other content. The four virtual drives are as follows:
- Cisco UCS Server Configuration Utility (bootable)
- User-installed (may be bootable)
- Cisco drivers (not bootable)
- Cisco Host Upgrade Utility (bootable)
For information about the Cisco software utilities and packages, see the Cisco UCS C-Series Servers Documentation Roadmap at this URL:
Configuring the Flexible Flash Controller Properties
This example configures the properties of the flash controller:
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 *# set raid-primary-member slot1 Server /chassis/flexflash/operational-profile *# set virtual-drives-enabled "SCU HUU" Server /chassis/flexflash/operational-profile *# commit Server /chassis/flexflash/operational-profile #
Booting from the Flexible Flash
You can specify a bootable virtual drive on the Cisco Flexible Flash card 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 boot device is used only once. After the server has rebooted, this setting is ignored.
![]() Note |
Before you reboot the server, ensure that the virtual drive you select is enabled on the Cisco Flexible Flash card. |
This example specifies that the server boots from the Cisco UCS Server Configuration Utility the next time it is restarted:
Server# scope bios Server /bios # set boot-override SCU Committing the boot override BIOS will try boot to the specified boot device first. Failure to detect the boot device BIOS will boot from the list configured in the BIOS boot order. Server /bios *# commit Server /bios #
Resetting the Flexible Flash Controller
In normal operation, it should not be necessary to reset the Cisco Flexible Flash. We recommend that you perform this procedure only when explicitly directed to do so by a technical support representative.
![]() Note |
This operation will disrupt traffic to the virtual drives on the Cisco Flexible Flash controller. |
This example resets the flash controller:
Server# scope chassis Server /chassis # scope flexflash FlexFlash-0 Server /chassis/flexflash # reset This operation will reset Cisco Flexible Flash controller. Host traffic to VDs on this device will be disrupted. Continue?[y|N] y Server /chassis/flexflash #
Configuring BIOS Settings
Viewing BIOS Status
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope bios | Enters the BIOS command mode. |
| Step 2 | Server /bios # show detail | Displays details of the BIOS status. |
The BIOS status information contains the following fields:
| Name | Description |
|---|---|
| BIOS Version | The version string of the running BIOS. |
| Boot Order | The order of bootable target types that the server will attempt to use. |
| Boot Override Priority | This can be None, SCU, HV, or HUU. |
| FW Update/Recovery Status | The status of any pending firmware update or recovery action. |
| FW Update/Recovery Progress | The percentage of completion of the most recent firmware update or recovery action. |
This example displays the BIOS status:
Server# scope bios
Server /bios # show detail
BIOS Version: "C460M1.1.2.2a.0 (Build Date: 01/12/2011)"
Boot Order: EFI,CDROM,HDD
Boot Override Priority:
FW Update/Recovery Status: NONE
FW Update/Recovery Progress: 100
Server /bios #
Configuring Main BIOS Settings
You must log in with admin privileges to perform this task.
This example configures the BIOS to pause the boot upon a critical POST error and commits the transaction:
Server# scope bios Server /bios # scope main Server /bios/main # set POSTErrorPause Enabled Server /bios/main *# commit Changes to BIOS set-up parameters will require a reboot. Do you want to reboot the system?[y|N] n Changes will be applied on next reboot. Server /bios/main #
Configuring Advanced BIOS Settings
![]() Note |
Depending on your installed hardware, some configuration options described in this topic may not appear. |
You must log in with admin privileges to perform this task.
This example enables low voltage DDR memory mode and commits the transaction:
Server# scope bios Server /bios # scope advanced Server /bios/advanced # set LvDDRMode Enabled Server /bios/advanced *# commit Changes to BIOS set-up parameters will require a reboot. Do you want to reboot the system?[y|N] n Changes will be applied on next reboot. Server /bios/advanced #
Configuring Server Management BIOS Settings
You must log in with admin privileges to perform this task.
This example enables automatic detection of the BMC and commits the transaction:
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set BMCPnP Enabled Server /bios/server-management *# commit Changes to BIOS set-up parameters will require a reboot. Do you want to reboot the system?[y|N] n Changes will be applied on next reboot. Server /bios/server-management #
Restoring BIOS Defaults
You must log in as a user with admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope bios | Enters the BIOS command mode. |
| Step 2 | Server /bios # bios-setup-default | Restores BIOS default settings. This command initiates a reboot. |
This example restores BIOS default settings:
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
Server BIOS Settings
The tables in the following sections list the server BIOS settings that you can view and configure.
Server /bios/main # set BootOptionRetry ? <VALUE> Disabled* | Enabled
![]() Note |
We recommend that you verify the support for BIOS settings in your server. Depending on your installed hardware, some settings may not be supported. |
Main BIOS Settings
Advanced: Processor BIOS Settings
Advanced: Memory BIOS Settings
| Name | Description | ||
|---|---|---|---|
| Select Memory RAS set SelectMemoryRAS |
How the memory reliability, availability, and serviceability (RAS) is configured for the server. This can be one of the following: |
||
| NUMA Optimized set NUMAOptimize |
Whether the BIOS supports NUMA. This can be one of the following: |
||
| Low Voltage DDR Mode set LvDDRMode |
Whether the system prioritizes low voltage or high frequency memory operations. This can be one of the following: |
||
Sparing Mode set SparingMode |
The sparing mode used by the CIMC. This can be one of the following:
|
||
Mirroring Mode set MirroringMode |
Mirroring is supported across Integrated Memory Controllers (IMCs) where one memory riser is mirrored with another. This can be one of the following:
|
||
Patrol Scrub set PatrolScrub |
Whether the system actively searches for, and corrects, single bit memory errors even in unused portions of the memory on the server. This can be one of the following:
|
||
Patrol Scrub Interval set PatrolScrubDuration |
Controls the time interval between each patrol scrub memory access. A lower interval scrubs the memory more often but requires more memory bandwidth. Select a value between 5 and 23. The default value is 8.
|
||
CKE Low Policy set CKELowPolicy |
Controls the DIMM power savings mode policy. This can be one of the following:
|
Advanced: Mass Storage Controller BIOS Settings
| Name | Description |
|---|---|
| Onboard SATA Controller set OnboardSATA |
Whether the processor uses its built-in SATA controller. This can be one of the following: |
| SATA Mode set ConfigSATAMode |
The mode in which the SATA controller runs. This can be one of the following: |
Advanced: Serial Port BIOS Settings
| Name | Description |
|---|---|
| Serial A Enable set Serial-PortA |
Whether serial port A is enabled or disabled. This can be one of the following: |
| Serial A Address set SerialPortAAddress |
If serial port A is enabled, select the hex address that it should use. This can be one of the following: |
| Serial B Enable set Serial-PortB |
Whether serial port B is enabled or disabled. This can be one of the following: |
| Serial B Address set SerialPortBAddress |
If serial port B is enabled, select the hex address that it should use. This can be one of the following: |
Advanced: USB BIOS Settings
| Name | Description |
|---|---|
| USB Controller set USBController |
Whether the processor uses its built-in USB controller. This can be one of the following: |
| Make Device Non-Bootable set MakeUSBDeviceNonBootable |
Whether the server can boot from a USB device. This can be one of the following: |
USB Performance Mode set USBPerformanceMode |
Whether the server uses USB 2.0 or USB 1.1 mode. This can be one of the following:
|
Advanced: PCI BIOS Settings
| Name | Description |
|---|---|
| Memory Mapped I/O Above 4GB set MemoryMappedIOAbove4GB |
Whether to enable or disable memory mapped I/O of 64-bit PCI devices to 4GB or greater address space. Legacy option ROMs are not able to access addresses above 4GB. PCI devices that are 64-bit compliant but use a legacy option ROM may not function correctly with this setting enabled. This can be one of the following: |
| Onboard Gbit NIC 1 set OnboardNic1 |
Whether the first onboard Network Interface Card (NIC) is enabled or disabled on the server. This can be one of the following: |
| Onboard Gbit NIC 2 set OnboardNic2 |
Whether the second onboard NIC is enabled or disabled on the server. This can be one of the following: |
| Onboard Gbit NIC 1 ROM set OnboardNic1ROM |
Whether the system loads the embedded PXE option ROM for the first onboard NIC. This can be one of the following: |
| Onboard Gbit NIC 2 ROM set OnboardNic2ROM |
Whether the system loads the embedded PXE option ROM for the second onboard NIC. This can be one of the following: |
Onboard Gbit NIC 3 ROM set OnboardNic3ROM |
Whether the system loads the embedded PXE option ROM for the third onboard NIC. This can be one of the following: |
Onboard Gbit NIC 4 ROM set OnboardNic4ROM |
Whether the system loads the embedded PXE option ROM for the fourth onboard NIC. This can be one of the following: |
| PCIe Option ROMs set Pci-Opt-Roms |
Whether the server can use the PCIe Option ROM expansion slots. This can be one of the following: |
| PCIe Slot n ROM set SlotnDisable |
Whether the PCIe expansion slot designated by n is available to the server. This can be one of the following: |
| PCIe Mezzanine Slot ROM set SlotMezzDisable |
Whether the PCIe mezzanine slot expansion ROM is available to the server. This can be one of the following: |
Active Video set ActiveVideo |
How the server displays video. This can be one of the following: |
Server Management BIOS Settings
| Name | Description | ||
|---|---|---|---|
set BootOptionRetry |
Whether the BIOS retries NON-EFI based boot options without waiting for user input. This can be one of the following: |
||
| Assert NMI on SERR set AssertNMIOnSERR |
Whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a system error (SERR) occurs. This can be one of the following: |
||
| Assert NMI on PERR set AssertNMIOnPERR |
Whether the BIOS generates a non-maskable interrupt (NMI) and logs an error when a processor bus parity error (PERR) occurs. This can be one of the following: |
||
| FRB2 Enable set FRB-2 |
Whether the FRB2 timer is used by CIMC to recover the system if it hangs during POST. This can be one of the following: |
||
| PlugNPlay BMC Detection set BMCPnP |
Whether the system automatically detects the BMC in ACPI-compliant operating systems. This can be one of the following: |
||
| ACPI1.0 Support set ACPI10Support |
Whether the BIOS publishes the ACPI 1.0 version of FADT in the Root System Description table. This version may be required for compatibility with OS versions that only support ACPI 1.0. This can be one of the following: |
||
| Console Redirection set ConsoleRedir |
Allows 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. This can be one of the following:
|
||
| Flow Control set FlowCtrl |
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. This can be one of the following:
|
||
| Baud Rate set BaudRate |
What BAUD rate is used for the serial port transmission speed. If you disable Console Redirection, this option is not available. This can be one of the following:
|
||
| Terminal Type set TerminalType |
What type of character formatting is used for console redirection. This can be one of the following:
|
||
| Legacy OS Redirection set LegacyOSRedir |
Whether redirection from a legacy operating system, such as DOS, is enabled on the serial port. This can be one of the following: |
||
OS Boot Watchdog Timer set OSBootWatchdogTimer |
Whether the BIOS programs the watchdog timer with a specified timeout value. If the operating system does not complete booting before the timer expires, the CIMC resets the system and an error is logged. This can be one of the following:
|
||
OS Boot Watchdog Timer Timeout set OSBootWatchdogTimerTimeOut |
What timeout value the BIOS uses to configure the watchdog timer. This can be one of the following:
|
||
OS Boot Watchdog Policy set OSBootWatchdogTimerPolicy |
What action the system takes if the watchdog timer expires. This can be one of the following:
|

Feedback