The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
You can manage and monitor all blade servers in a Cisco UCS instance through Cisco UCS Manager. Some blade server management tasks, such as changes to the power state, can be performed from the server and service profile.
The remaining management tasks can only be performed on the server.
If a blade server slot in a chassis is empty, Cisco UCS Manager provides information, errors, and faults for that slot. You can also reacknowledge the slot to resolve server mismatch errors and to have Cisco UCS Manager rediscover the blade server in the slot.
Consider the following guidelines when deciding whether to remove or decommission a blade server using Cisco UCS Manager:
Decommissioning is performed when a blade server is physically present and connected but you want to temporarily remove it from the configuration. Because it is expected that a decommissioned blade server will be eventually recommissioned, a portion of the server's information is retained by Cisco UCS Manager for future use.
Removing is performed when you physically remove a blade server from the server by disconnecting it from the chassis. You cannot remove a blade server from Cisco UCS Manager if it is physically present and connected to a chassis. Once the physical removal of the blade server is completed, the configuration for that blade server can be removed in Cisco UCS Manager.
During removal, active links to the blade server are disabled, all entries from databases are removed, and the server is automatically removed from any server pools that it was assigned to during discovery.
Note |
Only those servers added to a server pool automatically during discovery will be removed automatically. Servers that have been manually added to a server pool have to be removed manually. |
If you need to add a removed blade server back to the configuration, it must be reconnected and then rediscovered. When a server is reintroduced to Cisco UCS Manager it is treated like a new server and is subject to the deep discovery process. For this reason, it's possible that Cisco UCS Manager will assign the server a new ID that may be different from the ID that it held before.
Booting Blade Servers
If the Boot Server link is dimmed in the Actions area, you must shut down the server first.
After the server has booted, the Overall Status field on the General tab displays an OK status.
Tip |
You can also view the boot order tabs from the General tab of the service profile associated with a server. |
Shutting Down Blade Servers
When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager triggers the OS into a graceful shutdown sequence.
If the Shutdown Server link is dimmed in the Actions area, the server is not running.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server that you want to shut down. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Shutdown Server. |
Step 6 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
After the server has been successfully shut down, the Overall Status field on the General tab displays a power-off status.
When you use this procedure to shut down a server with an installed operating system, Cisco UCS Manager triggers the OS into a graceful shutdown sequence.
If the Shutdown Server link is dimmed in the Actions area, the server is not running.
Step 1 | In the Navigation pane, click the Servers tab. |
Step 2 | On the Servers tab, expand . |
Step 3 |
Expand the node for the organization where you want to create the service profile. If the system does not include multi-tenancy, expand the root node. |
Step 4 | Choose the service profile that requires the associated server to be shut down. |
Step 5 | In the Work pane, click the General tab. |
Step 6 | In the Actions area, click Shutdown Server. |
Step 7 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
After the server has been successfully shut down, the Overall Status field on the General tab displays a down status or a power-off status.
When you reset a server, Cisco UCS Manager sends a pulse on the reset line. You can choose to gracefully shut down the operating system. If the operating system does not support a graceful shut down, the server is power cycled. The option to have Cisco UCS Manager complete all management operations before it resets the server does not guarantee that these operations will be completed before the server is reset.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server that you want to reset. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Reset. |
Step 6 | In the Reset Server dialog box, do the following: |
The reset may take several minutes to complete. After the server has been reset, the Overall Status field on the General tab displays an ok status.
Perform the following procedure if you need to have Cisco UCS Manager rediscover the server and all endpoints in the server. For example, you can use this procedure if a server is stuck in an unexpected state, such as the discovery state.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server that you want to acknowledge. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Server Maintenance. |
Step 6 |
In the Maintenance dialog box, do the following:
Cisco UCS Manager disconnects the server and then builds the connections between the server and the fabric interconnect or fabric interconnects in the system. The acknowledgment may take several minutes to complete. After the server has been acknowledged, the Overall Status field on the General tab displays an OK status. |
Physically remove the server from its chassis before performing the following procedure.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server that you want to remove from the chassis. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Server Maintenance. |
Step 6 |
In the Maintenance dialog box, do the following:
The server is removed from the Cisco UCS configuration. |
Step 7 |
Go to the physical location of the chassis and remove the server hardware from the slot. For instructions on how to remove the server hardware, see the Cisco UCS Hardware Installation Guide for your chassis. |
If you physically re-install the blade server, you must re-acknowledge the slot to have Cisco UCS Manager rediscover the server.
For more information, see Reacknowledging a Server Slot in a Chassis.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server that you want to decommission. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Server Maintenance. |
Step 6 |
In the Maintenance dialog box, do the following:
The server is removed from the Cisco UCS configuration. |
If you physically re-install the blade server, you must re-acknowledge the slot to have Cisco UCS Manager rediscover the server.
For more information, see Reacknowledging a Server Slot in a Chassis.
Perform the following procedure if you decommissioned a blade server without removing the physical hardware from the chassis and you want Cisco UCS Manager to rediscover and recommission the server.
Step 1 | In the Navigation pane, click the Equipment tab. | ||||||
Step 2 | On the Equipment tab, expand . | ||||||
Step 3 | Choose the server whose slot you want to reacknowledge. | ||||||
Step 4 |
If Cisco UCS Manager displays a Resolve Slot Issue dialog box, do one of the following:
|
Perform the following procedure if you physically removed the server hardware without first decommissioning the server. You cannot perform this procedure if the server is physically present.
If you want to physically remove a server, see Removing a Server from a Chassis.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server that you want to remove from the configuration database. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Server Maintenance. |
Step 6 |
In the Maintenance dialog box, do the following:
Cisco UCS Manager removes all data about the server from its configuration database. The server slot is now available for you to insert new server hardware. |
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server for which you want to turn the locator LED on or off. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click one of the following: |
On rare occasions, troubleshooting a server may require you to reset the CMOS. This procedure is not part of the normal maintenance of a server.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server for which you want to reset the CMOS. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Recover Server. |
Step 6 | In the Recover Server dialog box, do the following: |
On rare occasions, such as an issue with the current running firmware, troubleshooting a server may require you to reset the CIMC. This procedure is not part of the normal maintenance of a server. After you reset the CIMC, the server boots with the running version of the firmware for that server.
If the CIMC is reset, the power monitoring functions of Cisco UCS become briefly unavailable for as long as it takes for the CIMC to reboot. While this usually only takes 20 seconds, there is a possibility that the peak power cap could be exceeded during that time. To avoid exceeding the configured power cap in a very low power-capped environment, consider staggering the rebooting or activation of CIMCs.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server for which you want to reset the CIMC. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Recover Server. |
Step 6 | In the Recover Server dialog box, do the following: |
On rare occasions, an issue with a server may require you to recover the corrupted BIOS. This procedure is not part of the normal maintenance of a server. After you recover the BIOS, the server boots with the running version of the firmware for that server. This radio button may be dimmed if the BIOS does not require recovery or the option is not available for a particular server.
Remove all attached or mapped USB storage from a server before you attempt to recover the corrupt BIOS on that server. If an external USB drive is attached or mapped from vMedia to the server, BIOS recovery fails.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server for which you want to recover the BIOS. |
Step 4 | In the Work pane, click the General tab. |
Step 5 | In the Actions area, click Recover Server. |
Step 6 | In the Recover Server dialog box, do the following: |
Step 7 | If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes. |
Step 8 |
In the Recover Corrupt BIOS dialog box, do the following:
|
You can view any errors collected during the Power On Self-Test process for a server and its adapters.
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server for which you want to view the POST results. |
Step 4 | In the Work pane, click the General tab. |
Step 5 |
In the Actions area, click View POST Results. The POST Results dialog box lists the POST results for the server and its adapters. |
Step 6 | (Optional)Click the link in the Affected Object column to view the properties of that adapter. |
Step 7 | Click OK to close the POST Results dialog box. |