- Server Management in Cisco UCS Manager GUI
- Resetting a Server
- Reacknowledging a Server
- Removing a Server from a Chassis
- Decommissioning a Server
- Reacknowledging a Server Slot in a Chassis
- Removing a Non-Existent Server from the Configuration Database
- Resetting the CMOS for a Server
- Resetting the BMC for a Server
- Recovering the Corrupt BIOS on a Server
- Monitoring a Server
- Viewing the POST Results for a Server
Managing the Servers
This chapter includes the following sections:
- Server Management in Cisco UCS Manager GUI
- Resetting a Server
- Reacknowledging a Server
- Removing a Server from a Chassis
- Decommissioning a Server
- Reacknowledging a Server Slot in a Chassis
- Removing a Non-Existent Server from the Configuration Database
- Resetting the CMOS for a Server
- Resetting the BMC for a Server
- Recovering the Corrupt BIOS on a Server
- Monitoring a Server
- Viewing the POST Results for a Server
- Booting a Server
- Booting a Server from the Service Profile
- Shutting Down a Server
- Shutting Down a Server from the Service Profile
- Turning on the Locator LED for a Server
- Turning off the Locator LED for a Server
- Starting the KVM Console from a Server
- Starting the KVM Console from a Service Profile
- Starting the KVM Console from the KVM Launch Manager
Server Management in Cisco UCS Manager GUI
You can manage and monitor all servers in a Cisco UCS instance through Cisco UCS Manager GUI. Some server management tasks, such as changes to the power state, can be performed from the following locations:
The remaining management tasks can only be performed on the server.
If a 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 server in the slot.
Booting Servers
Booting a Server
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.
Booting a Server from the Service Profile
Shutting Down Servers
Shutting Down a Server
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 Shut Down link is dimmed in the Actions area, the server is not running.
After the server has been successfully shut down, the Overall Status field on the General tab displays a power-off status.
Shutting Down a Server from the Service Profile
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.
Resetting a Server
When you reset a server, Cisco UCS Manager sends a pulse on the reset line. You can choose to gracefully shutdown the operating system. If the operating system does not support a graceful shutdown, the server will be 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.
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.
Reacknowledging a Server
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.
Removing a Server from a Chassis
Physically remove the server before performing the following procedure.
What to Do Next
If you physically re-install the 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.
Decommissioning a Server
This procedure removes the server from the configuration. As long as the server physically remains in the Cisco UCS instance, Cisco UCS Manager considers the server to be decommissioned and ignores it.
What to Do Next
If you physically re-install the 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.
Reacknowledging a Server Slot in a Chassis
Perform the following procedure if you decommission a server without removing the physical hardware and you want Cisco UCS Manager to rediscover and recommission the server.
Removing a Non-Existent Server from the Configuration Database
Perform the following procedure if you physically removed a server from its slot in a chassis without first decommissioning the server. You cannot perform this procedure if the server is physically present in the chassis slot.
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. |
Toggling the Locator LED
Turning on the Locator LED for a Server
Step 1 | In the Navigation pane, click the Equipment tab. |
Step 2 | On the Equipment tab, expand . |
Step 3 | Choose the server that you need to locate. |
Step 4 | In the Work pane, click the General tab. |
Step 5 |
In the Actions area, click Turn on Locator LED. This action is not available if the locator LED is already turned on. The LED on the chassis starts flashing. |
Turning off the Locator LED for 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 turn off the locator LED. |
Step 4 | In the Work pane, click the General tab. |
Step 5 |
In the Actions area, click Turn off Locator LED. This action is not available if the locator LED is already turned off. The LED on the server stops flashing. |
Starting the KVM Console
Starting the KVM Console from a Server
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 access through the KVM console. | ||
Step 4 | In the Work pane, click the General tab. | ||
Step 5 |
In the Actions area, click KVM Console. The KVM console opens in a separate window.
|
Starting the KVM Console from a Service Profile
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 which contains the service profile for which you want to launch the KVM console. If the system does not include multi-tenancy, expand the root node. |
||
Step 4 | Choose the service profile for which you need KVM access to the associated server. | ||
Step 5 | In the Work pane, click the General tab. | ||
Step 6 |
In the Actions area, click KVM Console. The KVM console opens in a separate window.
|
Starting the KVM Console from the KVM Launch Manager
The KVM Launch Manager enables you to access a server through the KVM console without logging in to Cisco UCS Manager.
To access the KVM console for a server through the KVM Launch Manager, you need the following:
-
Cisco UCS username and password.
-
Name of the service profile associated with the server for which you want KVM access.
Step 1 |
In your web browser, type or select the web link for Cisco UCS Manager GUI. Example: The default web link is http://UCSManager_IP or https://UCSManager_IP. In a standalone configuration, UCSManager_IP is the IP address for the management port on the fabric interconnect. In a cluster configuration, UCSManager_IP is the IP address assigned to Cisco UCS Manager. |
Step 2 | On the Cisco UCS Manager page, click KVM Launch Manager. |
Step 3 | On the UCS - KVM Launch Manager Login page, do the following: |
Step 4 |
In the Service Profiles table of the KVM Launch Manager, do the following:
|
Resetting the CMOS for a Server
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: |
Resetting the BMC for a Server
On rare occasions, such as an issue with the current running firmware, troubleshooting a server may require you to reset the BMC. This procedure is not part of the normal maintenance of a server. After you reset the BMC, the server boots with the running version of the firmware for that 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 BMC. |
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 |
In the Recover Corrupt BIOS dialog box, do the following:
|
Recovering the Corrupt BIOS on a Server
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: |
Monitoring a Server
Step 1 | In the Navigation pane, click the Equipment tab. | ||||||||||||||||||||||||
Step 2 | On the Equipment tab, expand . | ||||||||||||||||||||||||
Step 3 | Click the server that you want to monitor. | ||||||||||||||||||||||||
Step 4 |
In the Work pane, click one of the following tabs to view the status of the server:
|
||||||||||||||||||||||||
Step 5 | In the Navigation pane, expand . | ||||||||||||||||||||||||
Step 6 |
In the Work pane, right-click one or more of the following components of the interface card to open the navigator and view the status of the component:
|
Viewing the POST Results for a Server
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. |