- Preface
- Overview
- Installing the Server OS
- Managing the Server
- Viewing Server Properties
- Viewing Sensors
- Managing Remote Presence
- Managing User Accounts
- Configuring Network-Related Settings
- Managing Network Adapters
- Managing Storage Adapters
- Configuring Communication Services
- Managing Certificates and Server Security
- Configuring Platform Event Filters
- Cisco IMC Firmware Management
- Viewing Faults and Logs
- Server Utilities
- BIOS Parameters by Server Model
- BIOS Token Name Comparison for Multiple Interfaces
- Index
- Toggling the Locator LED
- Toggling the Front Locator LED for the Chassis
- Toggling the Locator LED for a Hard Drive
- Selecting a Time Zone
- Managing the Server Boot Order
- Server Boot Order
- Viewing the Boot Device Detail
- Configuring the Precision Boot Order
- Modifying the Attributes of a Boot Device
- Rearranging Device Boot Order
- Re-Applying the Boot Order Configuration
- Deleting an Existing Boot Device
- Overview to UEFI Secure Boot
- Enabling UEFI Secure Boot Mode
- Disabling UEFI Secure Boot
- Viewing the Actual Server Boot Order
- Configuring a Server to Boot With a One-Time Boot Device
- Assigning User-defined Server Description and Asset Tag
- Resetting the Server
- Shutting Down the Server
- Managing Server Power
- Configuring Power Policies
- Power Capping
- Enabling Power Characterization
- Configuring the Power Cap Policy
- Configuring Standard Power Profile
- Configuring Advanced Power Profile Settings
- Resetting the Power Profiles to Defaults
- Viewing the Power Capping Configuration
- Viewing the Power Statistics
- Configuring the Power Restore Policy
- Configuring Fan Policies
- Configuring DIMM Black Listing
- Configuring BIOS Settings
- BIOS Profiles
- Updating Firmware on Server Components
- Viewing Product ID (PID) Catalog Details
- Uploading and Activating PID Catalog
Managing the Server
This chapter includes the following sections:
- Toggling the Locator LED
- Toggling the Front Locator LED for the Chassis
- Toggling the Locator LED for a Hard Drive
- Selecting a Time Zone
- Managing the Server Boot Order
- Resetting the Server
- Shutting Down the Server
- Managing Server Power
- Configuring Power Policies
- Configuring Fan Policies
- Configuring DIMM Black Listing
- Configuring BIOS Settings
- BIOS Profiles
- Updating Firmware on Server Components
- Viewing Product ID (PID) Catalog Details
- Uploading and Activating PID Catalog
Toggling the Locator LED
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
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 #
Toggling the Front Locator LED for the Chassis
This option is available only on some UCS C-Series servers.
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
This example disables the chassis locator LED and commits the transaction:
Server# scope chassis Server /chassis # set front-locator-led off Server /chassis *# commit Server /chassis #
Toggling the Locator LED for a Hard Drive
This action is available only on some UCS C-Series servers.
You must log in with user or admin privileges to perform this task.
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 #
Selecting a Time Zone
Selecting a Time Zone
Selecting a time zone helps you choose a local time zone so that you can view the local time rather than the default machine time. Cisco IMC Web UI and the CLI provide you options to choose and set a time zone of your choice.
Setting the time zone to your local time will apply the time zone variable to all the services that utilize the system timing. This impacts the logging information and is utilized in the following applications of the Cisco IMC:
When you set a local time, the timestamp on the applications that you can view are updated with the local time that you have chosen.
Selecting a Time Zone
You must log in with user or admin privileges to perform this task.
This example sets the time zone:
Server# scope CIMC
Server /CIMC # timezone-select
Please identify a location so that time zone rules can be set correctly.
Please select a continent or ocean.
1) Africa
2) Americas
3) Antarctica
4) Arctic Ocean
5) Asia
6) Atlantic Ocean
7) Australia
8) Europe
9) Indian Ocean
10) Pacific Ocean
#? 2
Please select a country whose clocks agree with yours.
1) Anguilla
2) Antigua & Barbuda
3) Argentina
4) Aruba
5) Bahamas
6) Barbados
7) Belize
8) Bolivia
9) Brazil
10) Canada
11) Caribbean Netherlands
12) Cayman Islands
13) Chile
14) Colombia
15) Costa Rica
16) Cuba
17) Curacao
18) Dominica
19) Dominican Republic
20) Ecuador
21) El Salvador
22) French Guiana
23) Greenland
24) Grenada
25) Guadeloupe
26) Guatemala
27) Guyana
28) Haiti
29) Honduras
30) Jamaica
31) Martinique
32) Mexico
33) Montserrat
34) Nicaragua
35) Panama
36) Paraguay
37) Peru
38) Puerto Rico
39) St Barthelemy
40) St Kitts & Nevis
41) St Lucia
42) St Maarten (Dutch part)
43) St Martin (French part)
44) St Pierre & Miquelon
45) St Vincent
46) Suriname
47) Trinidad & Tobago
48) Turks & Caicos Is
49) United States
50) Uruguay
51) Venezuela
52) Virgin Islands (UK)
53) Virgin Islands (US)
#? 49
Please select one of the following time zone regions.
1) Eastern Time
2) Eastern Time - Michigan - most locations
3) Eastern Time - Kentucky - Louisville area
4) Eastern Time - Kentucky - Wayne County
5) Eastern Time - Indiana - most locations
6) Eastern Time - Indiana - Daviess, Dubois, Knox & Martin Counties
7) Eastern Time - Indiana - Pulaski County
8) Eastern Time - Indiana - Crawford County
9) Eastern Time - Indiana - Pike County
10) Eastern Time - Indiana - Switzerland County
11) Central Time
12) Central Time - Indiana - Perry County
13) Central Time - Indiana - Starke County
14) Central Time - Michigan - Dickinson, Gogebic, Iron & Menominee Counties
15) Central Time - North Dakota - Oliver County
16) Central Time - North Dakota - Morton County (except Mandan area)
17) Central Time - North Dakota - Mercer County
18) Mountain Time
19) Mountain Time - south Idaho & east Oregon
20) Mountain Standard Time - Arizona (except Navajo)
21) Pacific Time
22) Alaska Time
23) Alaska Time - Alaska panhandle
24) Alaska Time - southeast Alaska panhandle
25) Alaska Time - Alaska panhandle neck
26) Alaska Time - west Alaska
27) Aleutian Islands
28) Metlakatla Time - Annette Island
29) Hawaii
#? 8
The following information has been given:
United States
Eastern Time - Indiana - Crawford County
Is the above information OK?
1) Yes
2) No
#? 1
You have chosen to set timezone settings to:
America/Indiana/Marengo
Continue?[y|N]: y
Timezone has been updated.
The local time now is: Sun Jun 1 02:21:15 2014 EST
Server /CIMC #
Managing the Server Boot Order
Server Boot Order
Using Cisco IMC, you can configure the order in which the server attempts to boot from available boot device types. In the legacy boot order configuration, Cisco IMC allows you to reorder the device types but not the devices within the device types. With the precision boot order configuration, you can have a linear ordering of the devices. In the web UI or CLI you can change the boot order and boot mode, add multiple devices under each device types, rearrange the boot order, set parameters for each device type.
When you change the boot order configuration, Cisco IMC sends the configured boot order to BIOS the next time that server is rebooted. To implement the new boot order, reboot the server after you make the configuration change. The new boot order takes effect on any subsequent reboot. The configured boot order remains until the configuration is changed again in Cisco IMC or in the BIOS setup.
 Note | When you create a new policy using the configure boot order feature, BIOS tries to map this new policy to the devices in the system. It displays the actual device name and the policy name to which it is mapped in the Actual Boot Order area. If BIOS cannot map any device to a particular policy in Cisco IMC, the actual device name is stated as NonPolicyTarget in the Actual Boot Order area. |
Note | When you upgrade Cisco IMC to the latest version 2.0(x) for the first time, the legacy boot order is migrated to the precision boot order. During this process, previous boot order configuration is erased and all device types configured before updating to 2.0 version are converted to corresponding precision boot device types and some dummy devices are created for the same device types. you can view these devices in the Configured Boot Order area in the web UI. To view these devices in the CLI, enter show boot-device command. During this the server's actual boot order is retained and it can be viewed under actual boot order option in web UI and CLI. |
When you downgrade Cisco IMC prior to 2.0(x) verison the server's last legacy boot order is retained, and the same can be viewed under Actual Boot Order area. For example:
-
If you configured the server in a legacy boot order in 2.0(x) version, upon downgrade a legacy boot order configuration is retained.
-
If you configured the server in a precision boot order in 2.0(x), upon downgrade the last configured legacy boot order is retained.
-
Boot order configuration prior to 2.0(x) is referred as legacy boot order. If your running version is 2.0(x), then you cannot configure legacy boot order through web UI, but you can configure through CLI and XML API. In the CLI, you can configure it by using set boot-order HDD,PXE command. Even though, you can configure legacy boot order through CLI or XML API, in the web UI this configured boot order is not displayed.
-
Legacy and precision boot order features are mutually exclusive. You can configure either legacy or precision boot order. If you configure legacy boot order, it disables all the precision boot devices configured. If you configure precision boot order, then it erases legacy boot order configuration.
Viewing the Boot Device Detail
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.
| Command or Action | Purpose |
|---|
This example displays the details of the created bootable device:
Server# scope bios
Server /bios # show boot-device
Boot Device Device Type Device State Device Order
-------------------- ------------ ------------------ ----------------
TestUSB USB Enabled 1
TestPXE PXE Enabled 2
Server /bios # show boot-device detail
Boot Device TestSAN:
Device Type: SAN
Device State: Enabled
Device Order: 1
Slot Id:
Lun Id:
Boot Device TestUSB:
Device Type: USB
Device State: Enabled
Device Order: 2
Sub Type: HDD
Boot Device TestPXE:
Device Type: PXE
Device State: Enabled
Device Order: 3
Slot Id: L
Port Number: 1
Configuring the Precision 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.
This example configures the boot order, creates a boot device, set the attributes of the new device and commit the transaction:
Server# scope bios
Server /bios # create boot-device TestPXE PXE
Server /bios # scope boot-device TestPXE
Server /bios /boot-device # set state Enabled
Server /bios /boot-device # set slot L
Server /bios /boot-device # set port 1
Server /bios /boot-device # set order 1
Server /bios /boot-device # commit
Enabling boot device will overwrite Legacy Boot Order configuration
Continue?[y|N]y
Server /bios /boot-device # y
Commiting device configuration
Server /bios/boot-device # show detail
BIOS:
BIOS Version: "C240M3.2.0.0.15 (Build Date: 03/16/2014)"
Boot Order: (none)
Boot Override Priority:
FW Update/Recovery Status: None, OK
UEFI Secure Boot: disabled
Configured Boot Mode: None
Actual Boot Mode: Legacy
Last Configured Boot Order Source: CIMC
Server /bios/boot-device # show boot-device detail
Boot Device TestPXE:
Device Type: PXE
Device State: Enabled
Device Order: 1
Slot Id: L
Port Number: 1
Reboot the server to boot with your new boot order.
Modifying the Attributes of a Boot Device
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.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | Server# scope bios |
Enters the BIOS command mode. | ||
| Step 2 | Server /bios # scope boot-device created boot device name. |
Enters the management of the created bootable devices. | ||
| Step 3 | Server /bios /boot-device # set state {Enabled|Disabled}. |
Enables or disables the device. The default state is disabled.
| ||
| Step 4 | Server /bios /boot-device* # set order {Index | 1-50}. |
Specifies the order of booting for particular device in the device list. Enter a number between 1 and 50 based on the total number of created device.
| ||
| Step 5 | Server /bios /boot-device* # set port {value | 1-255 }. |
Specifies the port of the slot in which the device is present. Enter a number between 1 and 255. | ||
| Step 6 | Server /bios /boot-device* # commit |
Commits the transaction to the system configuration. |
This example modifies the attributes of an existing device:
Server# scope bios Server /bios *# scope boot-device scu-device-hdd Server /bios/boot-device # set status enabled Server /bios/boot-device *# set order 2 Server /bios/boot-device *# set port 1 Server /bios/boot-device *# commit Enabling boot device will overwrite boot order Level 1 configuration Continue?[y|N]y Server /bios/boot-device #
Rearranging Device 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.
| Command or Action | Purpose |
|---|
This example rearranges the selected boot devices:
Server# scope bios Server /bios # rearrange-boot-device TestPXE:1,TestUSB:2 Server /bios # show boot-device Boot Device Device Type Device State Device Order -------------------- ------------ ------------------ ---------------- TestPXE PXE Disabled 1 TestUSB USB Disabled 2 Server /bios #
Re-Applying the Boot Order Configuration
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.
| Command or Action | Purpose |
|---|
This example re-applies the boot order to BIOS:
Server# scope bios Server /bios # re-apply Server /bios #
Reboot the host after reapplying the boot order to BIOS.
Deleting an Existing Boot Device
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.
| Command or Action | Purpose |
|---|
This example deletes the selected device from the device list:
Server# scope bios Server /bios # remove-boot-device scu-device-hdd Server /bios #
Overview to UEFI Secure Boot
You can use Unified Extensible Firmware Interface (UEFI) secure boot to ensure that all the EFI drivers, EFI applications, option ROM or operating systems prior to loading and execution are signed and verified for authenticity and integrity, before you load and execute the operating system. You can enable this option using either web UI or CLI. When you enable UEFI secure boot mode, the boot mode is set to UEFI mode and you cannot modify the configured boot mode until the UEFI boot mode is disabled.
Note | If you enable UEFI secure boot on a nonsupported OS, on the next reboot, you cannot boot from that particular OS. If you try to boot from the previous OS, an error is reported and recorded the under system software event in the web UI. You must disable the UEFI secure boot option using Cisco IMC to boot from your previous OS. |
Also, if you use an unsupported adapter, an error log event in Cisco IMC SEL is recorded. The error messages is displayed that says:
System Software event: Post sensor, System Firmware error. EFI Load Image Security Violation. [0x5302] was asserted .
| Components | Types |
|---|---|
|
Supported OS |
|
|
Broadcom PCI adapters |
|
|
Intel PCI adapters |
|
|
QLogic PCI adapters |
|
|
Fusion-io |
|
|
LSI |
Enabling UEFI Secure Boot Mode
| Command or Action | Purpose |
|---|
This example enables UEFI secure boot mode and commits the transaction
Server# scope bios Server /bios # set secure-boot enable Setting Value : enable Commit Pending. Server /bios *# commit UEFI Secure boot state changed successfully. Execute 'show detail' command to check the current status Server /bios #
Reboot the server to have your configuration boot mode settings take place.
Disabling UEFI Secure Boot
| Command or Action | Purpose |
|---|
This example disables UEFI secure boot mode and commits the transaction
Server# scope bios Server /bios # set secure-boot disable Setting Value : enable Commit Pending. Server /bios *# commit UEFI Secure boot state changed successfully. Execute 'show detail' command to check the current status Server /bios #
Reboot the server to have your configuration boot mode settings take place.
Viewing the Actual Server Boot Order
The actual server boot order is the boot order actually used by the BIOS when the server last booted. The actual boot order can differ from the boot order configured in Cisco IMC.
| Command or Action | Purpose |
|---|
This example displays the actual boot order of the legacy boot order from the last boot:
Server# scope bios Server /bios # show actual-boot-order Boot Order Type Boot Device ------------ ------------------------- ----------------------------------- 1 CD/DVD CD-ROM 2 CD/DVD Cisco Virtual CD/DVD 1.18 3 Network Device (PXE) Cisco NIC 23:0.0 4 Network Device (PXE) MBA v5.0.5 Slot 0100 5 Network Device (PXE) MBA v5.0.5 Slot 0101 6 Network Device (PXE) MBA v5.0.5 Slot 0200 7 Network Device (PXE) MBA v5.0.5 Slot 0201 8 Network Device (PXE) Cisco NIC 22:0.0 9 Internal EFI Shell Internal EFI Shell 10 FDD Cisco Virtual HDD 1.18 11 FDD Cisco Virtual Floppy 1.18 Server /bios #
Server /bios # show actual-boot-order Boot Order Boot Device Device Type Boot Policy ------------ ----------------------------------- --------------- -------------------- 1 IBA GE Slot 0201 v1398 PXE TestPXE 2 IBA GE Slot 0200 v1398 PXE NonPolicyTarget 3 IBA GE Slot 0202 v1398 PXE NonPolicyTarget 4 IBA GE Slot 0203 v1398 PXE NonPolicyTarget 5 "UEFI: Built-in EFI Shell " EFI NonPolicyTarget Server /bios #
Configuring a Server to Boot With a One-Time Boot Device
You can configure a server to boot from a particular device only for the next server boot, without disrupting the currently configured boot order. Once the server boots from the one time boot device, all its future reboots occur from the previously configured boot order.
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | Server# scope bios |
Enters the BIOS command mode. | ||
| Step 2 | Server# /bios show boot-device |
Displays the list of available boot drives. | ||
| Step 3 | Server# /bios set one-time-boot-device device-order |
Sets the boot order.
| ||
| Step 4 | Server# /bios * commit |
Commits the transaction. | ||
| Step 5 | Server# /bios show detail | (Optional)
Displays the BIOS details. |
This example shows how to configure a server to boot with a one-time boot device:
Server scope bios
Server /bios # show boot-device
Boot Device Device Type Device State Device Order
------------------------------ ------------ ------------------ ----------------
KVMDVD VMEDIA Enabled 1
vkvm VMEDIA Enabled 2
Server /bios # set one-time-boot-device KVMDVD
Server /bios *# 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 # show detail
BIOS:
BIOS Version: "C240M3.3.0.0.9 (Build Date: 10/02/16)"
Boot Order: (none)
FW Update/Recovery Status: None, OK
UEFI Secure Boot: disabled
Configured Boot Mode: Legacy
Actual Boot Mode: Legacy
Last Configured Boot Order Source: CIMC
One time boot device: KVMDVD
Server /bios #
Assigning User-defined Server Description and Asset Tag
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis |
Enters chassis command mode. |
| Step 2 | Server /chassis # set description <Server Description> |
Enters the server description. |
| Step 3 | Server /chassis* # set asset-tag <Asset Tag> |
Enters the asset tag. |
| Step 4 | Server /chassis* # commit |
Commits the transaction. |
| Step 5 | Server /chassis # show detail | (Optional)
Displays the server details. |
This example shows how to assign user-defined server description and asset tag:
Server# scope chassis Server/chassis # set description DN1-server Server/chassis* # set asset-tag powerpolicy Server /chassis* # commit Server /chassis # show detail Chassis: Power: on Serial Number: FCH1834V23X Product Name: UCS C220 M4S PID : UCSC-C220-M4S UUID: 414949AC-22D6-4D0D-B0C0-F7950E9217C1 Locator LED: off Description: DN1-server Asset Tag: powerpolicy Server /chassis #
Resetting the Server
If any firmware or BIOS updates are in progress, do not reset the server until those tasks are complete.
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
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
If any firmware or BIOS updates are in progress, do not shut down the server until those tasks are complete.
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
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 Cisco IMC, the server will not become active immediately when powered on. In this case, the server will enter standby mode until the Cisco IMC completes initialization. |
If any firmware or BIOS updates are in progress, do not change the server power until those tasks are complete.
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
This example shows how to turn on the server:
Server# scope chassis Server /chassis # power on Warning: System is already powered ON, this action is ineffective. Do you want to continue?[y|N]y
Powering Off the Server
If any firmware or BIOS updates are in progress, do not power off the server until those tasks are complete.
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
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
If any firmware or BIOS updates are in progress, do not power cycle the server until those tasks are complete.
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
This example power cycles the server:
Server# scope chassis Server /chassis # power cycle
Configuring Power Policies
Power Capping
This section is valid only for some UCS C-Series servers.
Power capping determines how server power consumption is actively managed. When you enable power capping option, the system monitors power consumption and maintains the power below the allocated power limit. If the server cannot maintain the power limit or cannot bring the platform power back to the specified power limit within the correction time, power capping performs actions that you specify in the Action field under the Power Profile area.
Once power capping is enabled, you can configure multiple power profiles to either have standard or advanced power profiles with defined attributes. If you choose a standard power profile, you can set the power limit, correction time, corrective-action, suspend period, hard capping, and policy state (if enabled). If you choose an advanced power profile, in addition to the attributes of the standard power profile, you can also set the domain specific power limits, safe throttle level, and ambient temperature based power capping attributes.
Note | The following changes are applicable for Cisco UCS C-Series release 2.0(13) and later:
|
The Run Power Characterization option in the Power Cap Configuration Tab of the Web UI power cycles the host and starts power characterization.
Enabling Power Characterization
This option is available only on some Cisco UCS C-Series servers.
You must log in with admin privileges to perform this task.
| Command or Action | Purpose |
|---|
This example shows how to automatically invoke power characterization during a host reboot:
Server# scope chassis Server /chassis# scope power-cap-config Server /chassis /power-cap-config # set run-pow-char-at-boot Server /chassis /power-cap-config* # commit Server /chassis/power-cap-config #
Configuring the Power Cap Policy
This option is available only on some Cisco UCS C-Series servers.
You must log in with admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis |
Enters chassis command mode. |
| Step 2 | Server /chassis # scope power-cap-config |
Enters power cap command mode. |
| Step 3 | Server /chassis /power-cap-config# set pow-cap-enable {yes | no} |
Enables or disables the capping of power to the server. |
| Step 4 | Server /chassis /power-cap-config# commit |
Commits the transaction to the system configuration. |
This example shows how to enable the power capping policy:
Server# scope chassis Server /chassis# scope power-cap-config Server /chassis /power-cap-config # set pow-cap-enable yes Server /chassis /power-cap-config* # commit Server /chassis/power-cap-config #
Configuring Standard Power Profile
This option is available only on some Cisco UCS C-Series servers.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis |
Enters chassis command mode. |
| Step 2 | Server /chassis # scope power-cap-config |
Enters power cap command mode. |
| Step 3 | Server /chassis /power-cap-config# set pow-cap-enable {yes | no} |
Enables or disables the power capping capability of the system. |
| Step 4 | Server /chassis /power-cap-config# scope power-profile standard |
Enters the standard command mode of a power profile |
| Step 5 | Server /chassis /power-cap-config# set allow-throttle yes | no |
Enables or disables the system to maintain the power limit by forcing the processor to use the throttling state (T-state) and memory throttle. |
| Step 6 | Server /chassis /power-cap-config# set corr-time value |
Sets the correction time in which the platform power should be brought back to the specified power limit before taking the action specified in the Action mode. The range is from 3 and 600 seconds. The default is 3 seconds. |
| Step 7 | Server /chassis /power-cap-config# set except-action alert | shutdown |
Specifies the action to be performed if the specified power limit is not maintained within the correction time. This can be one of the following: |
| Step 8 | Server /chassis /power-cap-config# set hard-cap yes | no |
Enables or disables the system to maintain the power consumption below the specified power limit. |
| Step 9 | Server /chassis /power-cap-config# set pow-limit value |
Specifies the power limit. Enter a value within the specified range. |
| Step 10 | Server /chassis /power-cap-config# set susp-pd {h:m-h:m | |ll,Mo,Tu,We,Th,Fr,Sa,Su.} |
Specifies the time period that the power capping profile is not active. |
| Step 11 | Server /chassis /power-cap-config# commit |
Commits the transaction to the system. |
This example shows how to configure standard power profile:
Server# scope chassis
Server /chassis# scope power-cap-config
Server /chassis /power-cap-config # set pow-cap-enable yes
Server /chassis /power-cap-config* # commit
Server /chassis/power-cap-config # scope power-profile advance
Server /chassis/power-cap-config # set allow-throttle yes
Server /chassis/power-cap-config* # set corr-time 6
Server /chassis/power-cap-config* # set except-action alert
Server /chassis/power-cap-config* # set hard-cap yes
Server /chassis/power-cap-config* # set pow-limit 360
Server /chassis/power-cap-config* # set susp-pd 1:30-2:30|All
Server /chassis/power-cap-config* # commit
Server /chassis/power-cap-config # show detail
Power Cap Config:
Power Characterization Enabled: yes
Power Capping: no
Power Characterization Status: Completed
Platform Min (Allow-Throttle)(W): 164
Platform Min (Efficient)(W): 290
Platform Max (W): 581
Memory Min (W): 2
Memory Max (W): 5
CPU Min (Allow-Throttle)(W): 64
CPU Min (Efficient)(W): 177
CPU Max (W): 330
Configuring Advanced Power Profile Settings
You can configure these settings only on some UCS C-Series servers.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server # scope chassis |
Enters chassis command mode. |
| Step 2 | Server /chassis # scope power-cap-config |
Enters power cap command mode. |
| Step 3 | Server /chassis /power-cap-config # set pow-cap-enable {yes | no} |
Enables or disables the power capping capability of the server. |
| Step 4 | Server /chassis /power-cap-config # commit |
Commits the transaction to the system. |
| Step 5 | Server /chassis /power-cap-config # scope power-profile advanced |
Enters the advance command mode of a power profile. |
| Step 6 | Server /chassis /power-cap-config/power-profile # set allow-throttle {yes | no} |
Enables or disables the system to maintain the power limit by forcing the processor to use the throttling state (T-state) and memory throttle. |
| Step 7 | Server /chassis /power-cap-config/power-profile # set corr-time value |
Sets the maximum time to take corrective actions in order to bring the platform back to the specified power limit before taking the actions specified in the Action mode. The range is from 3 and 600 seconds. The default is 3 seconds. |
| Step 8 | Server /chassis /power-cap-config/power-profile # set cpu-power-limit value |
Specifies the power limit for the CPU. Enter power in watts within the range specified. |
| Step 9 | Server /chassis /power-cap-config/power-profile # set cpu-safe-Tlvl value |
Specifies the throttling level for the CPU. The range is from 0 and 100 percentage. |
| Step 10 | Server /chassis /power-cap-config/power-profile # set except-action {alert | shutdown} |
Specifies the action to be performed if the specified power limit is not maintained within the correction time. This can be one of the following: |
| Step 11 | Server /chassis /power-cap-config/power-profile # set hard-cap {yes | no} |
Enables or disables the system to maintain the power consumption below the specified power limit. |
| Step 12 | Server /chassis /power-cap-config/power-profile # set mem-pow-limit value |
Specifies the power limit for the memory. Enter power in watts within the range specified. |
| Step 13 | Server /chassis /power-cap-config/power-profile # set mem-safe-Tlvl value |
Specifies the throttling level for the memory. The range is from 0 and 100 percentage. |
| Step 14 | Server /chassis /power-cap-config/power-profile # set fail-safe-timeout value |
Specifies a safe throttle policy when the power capping functionality is impacted internal faults such as missing power readings for platforms or CPUs. The range is from 1 and 10 seconds. |
| Step 15 | Server /chassis /power-cap-config/power-profile # set plat-safe-Tlvl value |
Specifies the throttling level for the platform in percentage. The range is from 0 and 100. |
| Step 16 | Server /chassis /power-cap-config/power-profile # set plat-temp value |
Specifies the inlet temperature sensor. Enter value in Celsius. |
| Step 17 | Server /chassis /power-cap-config/power-profile # set pow-limit value |
Specifies the power limit. Enter power in watts within the range specified. |
| Step 18 | Server /chassis /power-cap-config/power-profile # set susp-pd {h:m-h:m | |ll,Mo,Tu,We,Th,Fr,Sa,Su.} |
Specifies the time period that the power capping profile will not be active. |
| Step 19 | Server /chassis/power-cap-config/power-profile # set thermal-power-limit value |
Specifies the power limit to be maintained. Enter power in watts within the range specified. |
| Step 20 | Server /power-cap-config/power-profile # commit |
Commits the transaction to the system configuration. |
This example shows how to configure the advance power profile setting:
Server# scope chassis Server /chassis# scope power-cap-config Server /chassis /power-cap-config # set pow-cap-enable yes Server /chassis /power-cap-config* # commit Server /chassis/power-cap-config # scope power-profile advanced Server /chassis/power-cap-config/power-profile # set allow-throttle yes Server /chassis/power-cap-config/power-profile* # set corr-time 6 Server /chassis/power-cap-config/power-profile*# set cpu-power-limit 259 Server /chassis/power-cap-config/power-profile* # set cpu-safe-Tlvl 50 Server /chassis/power-cap-config/power-profile* # set except-action alert Server /chassis/power-cap-config/power-profile* # set hard-cap yes Server /chassis/power-cap-config/power-profile* # set mem-pow-limit 259 Server /chassis/power-cap-config/power-profile* # set mem-safe-Tlvl 50 Server /chassis/power-cap-config/power-profile* # set fail-safe-timeout 10 Server /chassis/power-cap-config/power-profile* # set plat-safe-Tlvl 50 Server /chassis/power-cap-config/power-profile* # set plat-temp 35 Server /chassis/power-cap-config/power-profile* # set pow-limit 360 Server /chassis/power-cap-config/power-profile* # set susp-pd 1:30-2:30|All Server /chassis/power-cap-config/power-profile* # set thermal-power-limit 354 Server /chassis/power-cap-config/power-profile* # commit Server /chassis/power-cap-config/power-profile #
Resetting the Power Profiles to Defaults
This option is available only on some Cisco UCS C-Series servers.
You must log in with admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis |
Enters chassis command mode. |
| Step 2 | Server /chassis # scope power-cap-config |
Enters power cap command mode. |
| Step 3 | Server /chassis # set reset-power-profile-to-defaults |
Resets the power profile settings to factory-default values and disables power capping. |
| Step 4 | Server /chassis # commit |
Commits the transaction to the system. |
This example shows how to reset the power profile to the default settings:
Server# scope chassis Server /chassis# scope power-cap-config Server /chassis /power-cap-config # reset-power-profile-to-defaults Server /chassis /power-cap-config* # commit Server /chassis/power-cap-config #
Viewing the Power Capping Configuration
This option is available only on some Cisco UCS C-Series servers.
You must log in with admin privileges to perform this task.
| Command or Action | Purpose |
|---|
This example shows how to view information about the power cap configuration:
Server #scope chassis
Server/chassis # scope power-cap-config
Server /chassis/power-cap-config # show detail
Power Cap Config:
Power Characterization Enabled: yes
Power Capping: no
Power Characterization Status: Completed
Platform Min (Allow-Throttle)(W): 164
Platform Min (Efficient)(W): 290
Platform Max (W): 581
Memory Min (W): 2
Memory Max (W): 5
CPU Min (Allow-Throttle)(W): 64
CPU Min (Efficient)(W): 177
CPU Max (W): 330
Server /chassis/power-cap-config #
Viewing the Power Statistics
This option is available only on some UCS C-Series servers.
You must log in with admin privileges to perform this task.
| Command or Action | Purpose |
|---|
This example shows how to view the power statistics of an individual domain:
Server #scope chassis Server /chassis # show power-monitoring Domain Current (W) Minimum (W) Maximum (W) Average (W) ---------- ------------ ------------ ------------ ------------ Platform 180 160 504 180 CPU 53 33 275 53 Memory 2 2 6 2 Server /chassis #
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.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server # Scope CIMC |
Enters the Cisco IMC command mode. |
| Step 2 | Server /CIMC # Scope power-restore-policy |
Enters the power restore policy command mode. |
| Step 3 | Server /CIMC/power-restore-policy # set policy {power-off | power-on | restore-last-state} |
Specifies the action to be taken when chassis power is restored. Select one of the following:
When the selected action is power-on, you can select a delay in the restoration of power to the server. |
| Step 4 | Server /CIMC/power-restore-policy # set delay {fixed | random} | (Optional)
Specifies whether server power will be restored after a fixed or random time. The default is fixed. This command is accepted only if the power restore action is power-on. |
| Step 5 | Server /CIMC/power-restore-policy # set delay-value delay | (Optional)
Specifies the delay time in seconds. The range is 0 to 240; the default is 0. |
| Step 6 | Server /CIMC/power-restore-policy # commit |
Commits the transaction to the system configuration. |
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 CIMC
Server /CIMC # Scope power-restore-policy
Server /CIMC/power-restore-policy # set policy power-on
Server /CIMC/power-restore-policy *# commit
Server /CIMC/power-restore-policy # set delay fixed
Server /CIMC/power-restore-policy *# set delay-value 180
Server /CIMC/power-restore-policy *# commit
Server /CIMC/power-restore-policy # show detail
Power Restore Policy:
Power Restore Policy: power-on
Power Delay Type: fixed
Power Delay Value(sec): 180
Server /CIMC/power-restore-policy #
Configuring Fan Policies
Fan Control Policies
Fan Control Policies enable you to control the fan speed to bring down server power consumption and noise levels. Prior to these fan policies, the fan speed increased automatically when the temperature of any server component exceeded the set threshold. To ensure that the fan speeds were low, the threshold temperatures of components are usually set to high values. While this behavior suited most server configurations, it did not address the following situations:
-
Maximum CPU performance
For high performance, certain CPUs must be cooled substantially below the set threshold temperature. This required very high fan speeds which resulted in higher power consumption and increased noise levels.
-
Low power consumption
To ensure the lowest power consumption, fans must run very slowly, and in some cases, stop completely on servers that support it. But slow fan speeds resulted in servers overheating. To avoid this situation, it is necessary to run fans at a speed that is moderately faster than the lowest possible speed.
With the introduction of fan policies, you can determine the right fan speed for the server, based on the components in the server. In addition, it allows you to configure the fan speed to address problems related to maximum CPU performance and low power consumption.
Following are the fan policies that you can choose from:
-
Balanced
This setting can cool almost any server configuration, but may not be suitable for servers with PCIe cards, since these cards overheat easily.
-
Performance
This setting can be used for server configurations where maximum fan speed is required for high performance. With this setting, the fan speeds will run at the same speed or higher speed than that of the Balanced fan policy.
-
Low Power
This is the default policy. This setting is ideal for minimal configuration servers that do not contain any PCIe cards.
-
High Power
This setting can be used for server configurations that require fan speeds ranging from 60 to 85%. This policy is ideal for servers that contain PCIe cards that easily overheat and have high temperatures. The minimum fan speed set with this policy varies for each server platform, but is approximately in the range of 60 to 85%.
-
Maximum Power
This setting can be used for server configurations that require extremely high fan speeds ranging between 70% to 100%. This policy is ideal for servers that contain PCIe cards that easily overheat and have extremely high temperatures. The minimum fan speed set with this policy varies for each server platform, but is approximately in the range of 70 to 100%.
Note | Although you set a fan policy in Cisco IMC, the actual speed that the fan runs at is determined by the configuration requirements of the server. For example, if you set the fan policy to Balanced, but the server includes PCIe cards that overheat easily, then the speed of the fans on the server is adjusted automatically to the required minimum fan speed to prevent the overheating. If you have set a fan speed configuration higher than required, the system retains the selected fan speed. The Applied Fan Policy displays the actual fan speed that runs on the server. |
The Configuration Status displays the status of the configured fan policy. This can be one of the following:
-
SUCCESS —The selected fan policy matches the actual fan speed that runs on the server.
-
PENDING —The configured fan policy is not in effect yet. This can be due to one of the following: -
FAN POLICY OVERRIDE—Overrides the specified fan speed with the actual speed determined by the configuration requirements of the server.
Configuring a Fan Policy
The fan policy determines the cooling requirements for your server. Prior to setting the fan policy, you must determine if your server includes PCIe cards that overheat easily.
You must log in with admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis |
Enters the chassis command mode. |
| Step 2 | Server /chassis # scope fan-policy |
Enters the fan policy command mode. |
| Step 3 | Server /chassis/fan-policy # set fan-policy |
Sets the fan policy for the server. It can be one of the following:
|
| Step 4 | Server /chassis/fan-policy # commit |
Commits the changes to the server. |
This example shows how to set the fan policy to maximum power for a server:
server # scope chassis
server /chassis # scope fan-policy
server /chassis/fan-policy # set fan-policy maximum-power
server /chassis/fan-policy* # commit
server /chassis/fan-policy # show detail
Fan Policy: maximum-power
Applied Fan Policy: Max Power
Configuration Status: SUCCESS
server /chassis/fan-policy #
Configuring DIMM Black Listing
DIMM Black Listing
In Cisco IMC, the state of the Dual In-line Memory Module (DIMM) is based on SEL event records. A DIMM is marked bad if the BIOS encounters a non-correctable memory error or correctable memory error with 16000 error counts during memory test execution during BIOS post. If a DIMM is marked bad, it is considered a non-functional device.
If you enable DIMM blacklisting, Cisco IMC monitors the memory test execution messages and blacklists any DIMM that encounters memory errors at any given point of time in the DIMM SPD data. This allows the host to map out those DIMMs.
DIMMs are mapped out or blacklisted only when Uncorrectable errors occur. When a DIMM gets blacklisted, other DIMMs in the same channel are ignored or disabled, which means that the DIMM is no longer considered bad.
Note | DIMMs do not get mapped out or blacklisted for 16000 Correctable errors. |
Enabling DIMM Black Listing
You must be logged in as an administrator.
| Command or Action | Purpose |
|---|
Server# scope dimm-blacklisting
Server /dimm-blacklisting # set enabled yes
Server /dimm-blacklisting* # commit
Server /dimm-blacklisting #
Server /dimm-blacklisting # show detail
DIMM Blacklisting:
Enabled: yes
Configuring BIOS Settings
Viewing BIOS Status
| Command or Action | Purpose |
|---|
The BIOS status information contains the following fields:
| Name | Description |
|---|---|
|
BIOS Version |
The version string of the running BIOS. |
|
Boot Order |
The legacy boot order of bootable target types that the server will attempt to use. |
|
Boot Override Priority |
This can be None, or HV. |
|
FW Update/Recovery Status |
The status of any pending firmware update or recovery action. |
|
UEFI Secure Boot |
Enables or Disables UEFI secure boot. |
|
Configured Boot Mode |
The boot mode in which h BIOS will try to boot the devices. |
|
Actual Boot Mode |
The actual boot mode in which BIOS booted the devices. |
|
Last Configured Boot Order Source |
The last configured boot order source by BIOS. |
This example displays the BIOS status:
Server# scope bios Server /bios # show detail Server /bios # show detail BIOS Version: "CxxxM1.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 #
Server# scope bios
Server /bios # show detail
BIOS:
BIOS Version: "Cxxx3.2.0.0.15 (Build Date: 03/xx/201x)"
Boot Order: (none)
Boot Override Priority:
FW Update/Recovery Status: None, OK
UEFI Secure Boot: disabled
Configured Boot Mode: Legacy
Actual Boot Mode: Legacy
Last Configured Boot Order Source: CIMC
One time boot device: (none)
Server /bios #
Configuring Main BIOS Settings
You must log in 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 # scope main |
Enters the main BIOS settings command mode. |
| Step 3 | Configure the BIOS settings. |
The BIOS parameters available depend on the model of the server that you are using. For descriptions and information about the options for each BIOS setting, see: |
| Step 4 | Server /bios/main # commit |
Commits the transaction to the system configuration. Changes are applied on the next server reboot. If server power is on, you are prompted to choose whether to reboot now. |
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.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope bios |
Enters the BIOS command mode. |
| Step 2 | Server /bios # scope advanced |
Enters the advanced BIOS settings command mode. |
| Step 3 | Configure the BIOS settings. |
The BIOS parameters available depend on the model of the server that you are using. For descriptions and information about the options for each BIOS setting, see: |
| Step 4 | Server /bios/advanced # commit |
Commits the transaction to the system configuration. Changes are applied on the next server reboot. If server power is on, you are prompted to choose whether to reboot now. |
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.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope bios |
Enters the BIOS command mode. |
| Step 2 | Server /bios # scope server-management |
Enters the server management BIOS settings command mode. |
| Step 3 | Configure the BIOS settings. |
The BIOS parameters available depend on the model of the server that you are using. For descriptions and information about the options for each BIOS setting, see: |
| Step 4 | Server /bios/server-management # commit |
Commits the transaction to the system configuration. Changes are applied on the next server reboot. If server power is on, you are prompted to choose whether to reboot now. |
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 |
|---|
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
Entering BIOS Setup
| Command or Action | Purpose |
|---|
This example enables you to enter BIOS setup:
Server# scope bios Server /bios # enter-bios-setup This operation will enable Enter BIOS Setup option. Host must be rebooted for this option to be enabled. Continue?[y|N]y
Restoring BIOS Manufacturing Custom Defaults
In instances where the components of the BIOS no longer function as desired, you can restore the BIOS set up tokens to the manufacturing default values.
Note | This action is only available for some C-Series servers. |
| Command or Action | Purpose |
|---|
This example shows how to restore the BIOS set up tokens to the manufacturing default values:
Server # scope bios Server /bios # restore-mfg-defaults This operation will reset the BIOS set-up tokens to manufacturing defaults. The system will be powered on. Continue? [y|n] N Server /bios #
BIOS Profiles
On the Cisco UCS server, default token files are available for every server platform, and you can configure the value of these tokens using the Graphic User Interface (GUI), CLI interface, and the XML API interface. To optimize server performance, these token values must be configured in a specific combination.
Configuring a BIOS profile helps you to utilize pre-configured token files with the right combination of the token values. Some of the pre-configured profiles that are available are virtualization, high-performance, low power, and so on. You can download the various options of these pre-configured token files from the Cisco website and apply it on the servers through the BMC.
You can edit the downloaded profile to change the value of the tokens or add new tokens. This allows you to customize the profile to your requirements without having to wait for turnaround time.
- Activating a BIOS Profile
- Taking a Back-Up of a BIOS Profile
- Deleting a BIOS Profile
- Displaying BIOS Profiles
- Displaying Information of a BIOS Profile
- Displaying details of the BIOS Profile
Activating a BIOS Profile
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope bios |
Enters the BIOS command mode. |
| Step 2 | Server# /bios scope bios-profile |
Enters the BIOS profile command mode. |
| Step 3 | Server# /bios/bios-profile activate virtualization |
You are prompted to back up the BIOS configuration. Enter y. |
| Step 4 | You are prompted to reboot the system to apply the changes to the BIOS set-up parameters. Enter y. |
Initiates the system reboot. |
This example activates the specified BIOS profile:
Server # scope bios Server /bios # scope bios-profile Server /bios/bios-profile # activate virtualization It is recommended to take a backup before activating a profile. Do you want to take backup of BIOS configuration?[y/n] y backup-bios-profile succeeded. bios profile “virtualization” deleted Changes to BIOS set-up parameters will require a reboot. Do you want to reboot the system?[y|N]y A system reboot has been initiated. Server /bios/bios-profile #
Taking a Back-Up of a BIOS Profile
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
This example backs up a BIOS profile:
Server # scope bios Server /bios # scope bios-profile Server /bios/bios-profile # backup backup-bios-profile succeeded. Server /bios #
Deleting a BIOS Profile
You must log in with user or admin privileges to perform this task.
| Command or Action | Purpose |
|---|
This example deletes the specified BIOS profile:
Server # scope bios Server /bios # scope bios-profile Server /bios/bios-profile # delete performance Server /bios/bios-profile #
Displaying BIOS Profiles
| Command or Action | Purpose |
|---|
This example displays all the BIOS profiles:
Server # scope bios Server /bios # show bios-profile ID Name Active ------ ---------------- -------- -------- 1 performance yes 2 virtualization no 3 none no 4 cisco_backup no Server /bios #scope bios-profile Server /bios #
Displaying Information of a BIOS Profile
| Command or Action | Purpose |
|---|
This example displays information of the specified BIOS profile:
Server # scope bios Server /bios # scope bios-profile Server /bios/bios-profile # info performance TOKEN NAME PROFILE VALUE ACTUAL VALUE ==================================================================== TPMAdminCtrl Enabled Enabled ASPMSupport Disabled Disabled Server /bios/bios-profile #
Displaying details of the BIOS Profile
| Command or Action | Purpose |
|---|
This example displays the details of the BIOS profile:
Server # scope bios Server /bios # scope bios-profile Server /bios/bios-profile # show detail Active Profile: Virtualization Install Status: bios profile install done Server /bios/bios-profile #
Updating Firmware on Server Components
If any firmware or BIOS updates are in progress, do not reset the server until those tasks are complete.
You must log in with user or admin privileges to perform this task.
Server must be powered off.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server# scope chassis |
Enters chassis command mode. |
| Step 2 | Server /chassis # scope firmware |
Enters firmware command mode. |
| Step 3 | Server /chassis/firmware # show detail |
Displays the firmware update required on some components message. |
| Step 4 | Server /chassis/firmware # update-all |
Updates the firmware on the server components. |
This example resets the server:
Server# scope chassis Server /chassis # scope firmware Server /chassis / firmware # show detail Firmware update required on some components, please run update-all (under chassis/firmware scope). Server /chassis / firmware # update-all
Viewing Product ID (PID) Catalog Details
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Server # scope chassis |
Enters chassis command mode. |
| Step 2 | Server /chassis # show cpu-pid |
Displays the CPU PID details. |
| Step 3 | Server /chassis # show dimm-pid |
Displays the memory PID details. |
| Step 4 | Server /chassis # show pciadapter-pid |
Displays the PCI adapters PID details. |
| Step 5 | Server /chassis # show hdd-pid |
Displays the HDD PID details. |
This example shows how to create view PID details
Server # scope chassis Viewing CPU PID details Server /chassis # show cpu-pid Socket Product ID Model ------ -------------------- ---------------------------------------- CPU1 UCS-CPU-E52660B Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.2... CPU2 UCS-CPU-E52660B Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.2... Viewing memory PID details Server /chassis # show dimm-pid Name Product ID Vendor ID Capacity Speed ----------------- -------------------- ---------- --------- ------ DIMM_A1 UNKNOWN NA Failed NA DIMM_A2 UNKNOWN NA Ignore... NA DIMM_B1 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_B2 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_C1 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_C2 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_D1 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_D2 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_E1 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_E2 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_F1 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_F2 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_G1 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_G2 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_H1 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 DIMM_H2 UCS-MR-1X162RZ-A 0xCE00 16384 MB 1866 Viewing PCI adapters PID details Server /chassis # show pciadapter-pid Slot Product ID Vendor ID Device ID SubVendor ID SubDevice ID ------ -------------------- ---------- ----------- ------------- ------------- 1 UCSC-MLOM-CSC-02 0x1137 0x0042 0x1137 0x012e Viewing HDD PID details Server /chassis # show hdd-pid Disk Controller Product ID Vendor Model ---- ----------- -------------------- ---------- ------------ 1 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 2 SLOT-MEZZ UCS-C3X60-HD4TB SEAGATE ST4000NM0023 3 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 4 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 5 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 6 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 7 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 8 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 9 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 10 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 11 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 12 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 13 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 14 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 15 SLOT-MEZZ UCS-C3X60-HD4TB SEAGATE ST4000NM0023 16 SLOT-MEZZ UCS-C3X60-HD4TB SEAGATE ST4000NM0023 19 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 28 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 54 SLOT-MEZZ UCSC-C3X60-HD6TB SEAGATE ST6000NM0014 55 SLOT-MEZZ UCSC-C3X60-HD6TB SEAGATE ST6000NM0014 56 SLOT-MEZZ UCSC-C3X60-HD4TB TOSHIBA MG03SCA400 57 SLOT-MEZZ UCS-HD4T7KS3-E WD WD4001FYY... 58 SLOT-MEZZ UCS-HD4T7KS3-E WD WD4001FYY... 59 SLOT-MEZZ UCS-HD4T7KS3-E WD WD4001FYY... 60 SLOT-MEZZ UCS-HD4T7KS3-E WD WD4001FYY... Server /chassis #
Uploading and Activating PID Catalog
You must log in as a user with admin privileges to perform this task.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 | Server# scope chassis |
Enters the chassis command mode. | ||
| Step 2 | Server# /chassis scope pid-catalog |
Enters the PID catalog command mode. | ||
| Step 3 | Server /chassis/pid-catalog # upload-pid-catalog remote-protocol IP Address PID Catalog file |
| ||
| Step 4 | Server# /chassis/pid-catalog show detail | (Optional)
Displays the status of the upload. | ||
| Step 5 | Server# /chassis/pid-catalog activate |
Activates the uploaded PID catalog. | ||
| Step 6 | Server# /chassis/pid-catalog show detail |
Displays the status of the activation. |
This example uploads and activates the PID catalog:
Server # scope chassis Server /chassis # scope pid-catalog Uploading PID Catalog Server /chassis/pid-catalog # upload-pid-catalog tftp 172.22.141.66 pid-ctlg-2_0_12_78_01.tar.gz upload-pid-catalog initialized. Please check the status using "show detail". Server /chassis/pid-catalog # Server /chassis/pid-catalog # show detail Upload Status: Upload Successful Activation Status: Please Activate Catalog Current Activated Version: N/A Activating the uploaded PID catalog Server /chassis/pid-catalog # activate Successfully activated PID catalog Server /chassis/pid-catalog # show detail Upload Status: Activation Status: Activation Successful Current Activated Version: 2.0(12.78).01 Server /chassis/pid-catalog #
Feedback