- Preface
- Overview
- Installing the Server Operating System or Hypervisor
- Managing the Server
- Managing Storage Using RAID
- Viewing Server Properties
- Viewing Server Sensors
- Managing Remote Presence
- Managing User Accounts
- Configuring Network-Related Settings
- Configuring Communication Services
- Managing Certificates
- Configuring Platform Event Filters
- Firmware Management
- Viewing Faults and Logs
- Server Utilities
- Diagnostic Tests
- Index
Managing the Server
This chapter includes the following sections:
- Configuring the Server Boot Order
- Resetting the Server
- Shutting Down the Server
- Locking Cisco IOS CLI Configuration Changes
- Unlocking Cisco IOS CLI Configuration Changes
- Managing Server Power
- Configuring BIOS Settings
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 cdrom:Virtual-CD,hdd:raid,efi To manage boot-order: - Reboot server to have your boot-order settings take place - Do not disable boot options via BIOS screens - If a specified device type is not seen by the BIOS, it will be removed from the boot order configured on the BMC - Your boot order sequence will be applied subject to the previous rule. The configured list will be appended by the additional device types seen by the BIOS Server /bios *# commit Server /bios # Server /bios # show detail BIOS: BIOS Version: "UCSES.1.5.0.1 (Build Date: 02/14/2013)" Boot Order: CDROM:Virtual-CD,HDD:RAID,EFI FW Update/Recovery Status: None, OK Active BIOS: main
Resetting the Server
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
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 |
After the prompt to confirm, shuts down the server.
|
This example shuts down the server:
Server# scope chassis Server /chassis # power shutdown This operation will change the server's power state. Do you want to continue?[y|N]y
Locking Cisco IOS CLI Configuration Changes
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 # show detail |
(Optional) Displays server properties, which allows you to determine the current status of the IOS lockout (whether it is locked or unlocked). |
Step 3 | Server /chassis # set ios-lockout locked |
Prevents configuration changes from being made using the Cisco IOS CLI. |
Step 4 | Server /chassis* # commit |
Commits the changes. |
Step 5 | Server /chassis # show detail |
(Optional) Displays server properties, which allows you to determine the current status of the IOS lockout (whether it is locked or unlocked). |
This example prevents configuration changes from being made using the Cisco IOS CLI:
Server# scope chassis Server /chassis # show detail Chassis: Power: on Power Button: unlocked IOS Lockout: unlocked Serial Number: FHH16150031 Product Name: E160DP PID : UCS-E160DP-M1/K9 UUID: 0024C4F4-89F2-0000-A7D1-770BCA4B8924 Description Server /chassis # set ios-lockout locked Server /chassis* # commit Server /chassis # show detail Chassis: Power: on Power Button: unlocked IOS Lockout: locked Serial Number: FHH16150031 Product Name: E160DP PID : UCS-E160DP-M1/K9 UUID: 0024C4F4-89F2-0000-A7D1-770BCA4B8924 Description
Unlocking Cisco IOS CLI Configuration Changes
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 # show detail |
(Optional) Displays server properties, which allows you to determine the current status of the IOS lockout (whether it is locked or unlocked). |
Step 3 | Server /chassis # set ios-lockout unlocked |
Allows configuration changes to be made using the Cisco IOS CLI. |
Step 4 | Server /chassis* # commit |
Commits the changes. |
Step 5 | Server /chassis # show detail |
(Optional) Displays server properties, which allows you to determine the current status of the IOS lockout (whether it is locked or unlocked). |
This example allows configuration changes to be made using the Cisco IOS CLI:
Server# scope chassis Server /chassis # show detail Chassis: Power: on Power Button: unlocked IOS Lockout: locked Serial Number: FHH16150031 Product Name: E160DP PID : UCS-E160DP-M1/K9 UUID: 0024C4F4-89F2-0000-A7D1-770BCA4B8924 Description Server /chassis # set ios-lockout unlocked Server /chassis* # commit Server /chassis # show detail Chassis: Power: on Power Button: unlocked IOS Lockout: unlocked Serial Number: FHH16150031 Product Name: E160DP PID : UCS-E160DP-M1/K9 UUID: 0024C4F4-89F2-0000-A7D1-770BCA4B8924 Description
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 |
---|
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 PID UUID ----- ------------- ------------- ------------- ------------------------------------ on FOC16161F1P E160D UCS-E160D-M... 1255F7F0-9F17-0000-E312-94B74999D9E7
Powering Off the Server
![]() Note | This procedure is not applicable to the NIM E-Series NCE. |
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 PID UUID ----- ------------- ------------- ------------- ------------------------------------ off FOC16161F1P E160D UCS-E160D-M... 1255F7F0-9F17-0000-E312-94B74999D9E7
Power Cycling the Server
![]() Note | This procedure is not applicable to the NIM E-Series NCE. |
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 |
After the prompt to confirm, power cycles the server.
|
This example power cycles the server:
Server# scope chassis Server /chassis # power cycle This operation will change the server's power state. Continue?[y|N]y
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.
![]() Note | These commands are supported only on ISR 4K routers, not on ISR G2. For ISR G2, refer to the BIOS configuration in CIMC. |
Command or Action | Purpose | |
---|---|---|
Step 1 | Server# scope cimc |
Enters the cimc 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: |
Step 4 | Server /cimc/power-restore-policy# commit |
Commits the transaction to the system configuration. |
This example sets the power restore policy to power-on 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 # show detail Power Restore Policy: Power Restore Policy: power-on Server /CIMC/power-restore-policy #
Locking the Server's Front Panel Power Button
![]() Note | This procedure is applicable to E-Series Servers and the SM E-Series NCE. This procedure is not applicable to the EHWIC E-Series NCE and the NIM E-Series NCE. |
Use this procedure to disable the physical power button, which is located on the front panel of the physical server. Once the power button is disabled, you cannot use the front panel power button to turn the server power on or off.
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 # show detail |
(Optional) Displays server properties, which allows you to determine the current status of the power button (whether it is locked or unlocked). |
Step 3 | Server /chassis # set power-button locked |
Disables the power button. You cannot use the front panel power button to turn the server power on or off. |
Step 4 | Server /chassis* # commit |
Commits the changes. |
Step 5 | Server /chassis # show detail |
(Optional) Displays server properties, which allows you to determine the current status of the power button (whether it is locked or unlocked). |
This example disables the server's physical power button, which is located on the front panel of the physical server:
Server# scope chassis Server /chassis # show detail Chassis: Power: on Power Button: unlocked IOS Lockout: unlocked Serial Number: FHH16150031 Product Name: E160DP PID : UCS-E160DP-M1/K9 UUID: 0024C4F4-89F2-0000-A7D1-770BCA4B8924 Description Server /chassis # set power-button locked Server /chassis* # commit Server /chassis # show detail Chassis: Power: on Power Button: locked IOS Lockout: unlocked Serial Number: FHH16150031 Product Name: E160DP PID : UCS-E160DP-M1/K9 UUID: 0024C4F4-89F2-0000-A7D1-770BCA4B8924 Description
Unlocking the Server's Front Panel Power Button
![]() Note | This procedure is applicable to E-Series Servers and the SM E-Series NCE. This procedure is not applicable to the EHWIC E-Series NCE and the NIM E-Series NCE. |
Use this procedure to enable the physical power button, which is located on the front panel of the physical server. Once the power button is enabled, you can use the front panel power button to turn the server power on or off.
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 # show detail |
(Optional) Displays server properties, which allows you to determine the current status of the power button (whether it is locked or unlocked). |
Step 3 | Server /chassis # set power-button unlocked |
Enables the power button. You can use the front panel power button to turn the server power on or off. |
Step 4 | Server /chassis* # commit |
Commits the changes. |
Step 5 | Server /chassis # show detail |
(Optional) Displays server properties, which allows you to determine the current status of the power button (whether it is locked or unlocked). |
This example enable the server's physical power button, which is located on the front panel of the physical server:
Server# scope chassis Server /chassis # show detail Chassis: Power: on Power Button: locked IOS Lockout: unlocked Serial Number: FHH16150031 Product Name: E160DP PID : UCS-E160DP-M1/K9 UUID: 0024C4F4-89F2-0000-A7D1-770BCA4B8924 Description Server /chassis # set power-button unlocked Server /chassis* # commit Server /chassis # show detail Chassis: Power: on Power Button: unlocked IOS Lockout: unlocked Serial Number: FHH16150031 Product Name: E160DP PID : UCS-E160DP-M1/K9 UUID: 0024C4F4-89F2-0000-A7D1-770BCA4B8924 Description
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 order of bootable target types that the server will attempt to use. |
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 FW Update/Recovery Status: NONE FW Update/Recovery Progress: 100 Server /bios #
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. | For the CLI commands, descriptions and information about the options for each BIOS setting, see the following topics: |
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 shows how to enable Intel virtualization technology:
Server# scope bios
Server /bios # scope advanced
Server /bios/advanced # set IntelVTD 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. | For the CLI commands, descriptions and information about the options for each BIOS setting, see the following topic: |
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 shows how to set the BAUD rate to 9.6k :
Server# scope bios Server /bios # scope server-management Server /bios/server-management # set BaudRate 9.6k 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 #
Clearing the BIOS CMOS
On rare occasions, troubleshooting a server may require you to clear the server's BIOS CMOS memory. This procedure is not part of the normal maintenance of a server.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | Server# scope bios |
Enters the BIOS command mode. | ||
Step 2 | Server /bios # clear-cmos |
After a prompt to confirm, clears the CMOS memory.
|
This example clears the BIOS 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
Clearing the BIOS Password
Command or Action | Purpose |
---|
This example clears the BIOS password:
Server# scope bios Server /bios # clear-bios-password This operation will clear the BIOS Password. Note: Server should be rebooted to clear BIOS password. Continue?[y|N]y
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
Server BIOS Settings
The tables in the following sections list the server BIOS settings that you can view and configure.
![]() 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. |
Advanced: Processor BIOS Settings
Name | Description | ||
---|---|---|---|
Intel Turbo Boost Technology Intel Turbo Boost Technology |
Whether the processor uses Intel Turbo Boost Technology, which allows the processor to automatically increase its frequency if it is running below power, temperature, or voltage specifications. This can be one of the following: |
||
Enhanced Intel Speedstep Technology |
Whether the processor uses Enhanced Intel SpeedStep Technology, which allows the system to dynamically adjust processor voltage and core frequency. This technology can result in decreased average power consumption and decreased average heat production. This can be one of the following:
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
||
Intel Hyper-Threading Technology |
Whether the processor uses Intel Hyper-Threading Technology, which allows multithreaded software applications to execute threads in parallel within each processor. This can be one of the following:
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
||
Number of Enabled Cores |
Sets the state of logical processor cores in a package. If you disable this setting, Hyper Threading is also disabled. This can be one of the following:
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
||
Execute Disable |
Classifies memory areas on the server to specify where application code can execute. As a result of this 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. This can be one of the following:
We recommend that you contact your operating system vendor to make sure the operating system supports this feature. |
||
Intel Virtualization Technology |
Whether the processor uses Intel Virtualization Technology (VT), which allows a platform to run multiple operating systems and applications in independent partitions. This can be one of the following:
|
||
Intel VT for Directed IO |
Whether the processor uses Intel Virtualization Technology for Directed I/O (VT-d). This can be one of the following: |
||
Intel VT-d Interrupt Remapping |
Whether the processor supports Intel VT-d Interrupt Remapping. This can be one of the following: |
||
Intel VT-d Coherency Support |
Whether the processor supports Intel VT-d Coherency. This can be one of the following: |
||
Intel VT-d Address Translation Services |
Whether the processor supports Intel VT-d Address Translation Services (ATS). This can be one of the following: |
||
Intel VT-d PassThrough DMA |
Whether the processor supports Intel VT-d Pass-through DMA. This can be one of the following: |
||
Direct Cache Access |
Allows processors to increase I/O performance by placing data from I/O devices directly into the processor cache. This setting helps to reduce cache misses. This can be one of the following: |
||
Processor C3 Report |
Whether the processor sends the C3 report to the operating system. This can be one of the following: |
||
Processor C6 Report |
Whether the processor sends the C6 report to the operating system. This can be one of the following: |
||
Hardware Prefetcher |
Whether the processor allows the Intel hardware prefetcher to fetch streams of data and instruction from memory into the unified second-level cache when necessary. This can be one of the following:
|
||
Adjacent Cache-Line Prefetch |
Whether the processor uses the Intel Adjacent Cache-Line Prefetch mechanism to fetch data when necessary. This can be one of the following:
|
||
Package C State Limit |
The amount of power available to the server components when they are idle. This can be one of the following:
|
||
Patrol Scrub |
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:
|
||
Demand Scrub |
Whether the system allows a memory scrub to be performed on demand. This can be one of the following:
|
||
Device Tagging |
Whether the system allows devices and interfaces to be grouped based on a variety of information, including descriptions, addresses, and names. This can be one of the following: |
Advanced: Memory BIOS Settings
Name | Description |
---|---|
Select Memory RAS |
How the memory reliability, availability, and serviceability (RAS) is configured for the server. This can be one of the following: |
Advanced: Serial Port BIOS Settings
Name | Description |
---|---|
Serial A Enable |
Whether serial port A is enabled or disabled. This can be one of the following: |
Advanced: USB BIOS Settings
Name | Description |
---|---|
USB Port 0 |
Whether the processor uses USB port 0. This can be one of the following: |
USB Port 1 |
Whether the processor uses USB port 1. This can be one of the following: |
Server Management BIOS Settings
Name | Description | ||
---|---|---|---|
Assert NMI on SERR |
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 |
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 |
Whether the FRB2 timer is used by CIMC to recover the system if it hangs during POST. This can be one of the following: |
||
Console Redirection |
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 |
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 |
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 |
What type of character formatting is used for console redirection. This can be one of the following:
|
||
OS Boot Watchdog Timer |
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 Policy |
The action the system takes when the watchdog timer expires. This can be one of the following:
|