Cisco UCS Manager GUI Configuration Guide, Release 1.3(1)
Managing the Servers
Download this chapter
Managing the ServersManaging the Servers
Download the complete book
UCSM_GUI_Configuration_Guide_1_3_1.pdfUCSM_GUI_Configuration_Guide_1_3_1.pdf (PDF - 6 MB)
 Feedback

Contents

Managing the Servers

This chapter includes the following sections:

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:


  • General tab for the server

  • General tab for the service profile associated with the server

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
Step 3   Choose the server that you want to boot.
Step 4   In the Work pane, click the General tab.
Step 5   In the Actions area, click Boot Server.
Step 6   If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

After the server has booted, the Overall Status field on the General tab displays an OK status.

Booting a Server from the Service Profile

Procedure
Step 1   In the Navigation pane, click the Servers tab.
Step 2   On the Servers tab, expand Servers > Service Profiles.
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 booted.
Step 5   In the Work pane, click the General tab.
Step 6   In the Actions area, click Boot Server.
Step 7   If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.
Step 8   Click OK in the Boot Server dialog box.

After the server has booted, the Overall Status field on the General tab displays an ok status or an up status.

Determining the Boot Order of a Server


Tip

You can also view the boot order tabs from the General tab of the service profile associated with a server.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
Step 3   Click the server for which you want to determine the boot order.
Step 4   In the Work pane, click the General tab.
Step 5   If the Boot Order Details area is not expanded, click the Expand icon to the right of the heading.
Step 6   To view the boot order assigned to the server, click the Configured Boot Order tab.
Step 7   To view what will boot from the various devices in the physical server configuration, click the Actual Boot Order tab.
Note   

The Actual Boot Order tab always shows "Internal EFI Shell" at the bottom of the boot order list.

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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 Shut Down.
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.

Shutting Down a Server from the Service Profile

Procedure
Step 1   In the Navigation pane, click the Servers tab.
Step 2   On the Servers tab, expand Servers > Service Profiles.
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 Shut Down.
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.

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
  1. Click the Power Cycle option.
  2. Optional: Check the check box if you want Cisco UCS Manager to complete all management operations that are pending on this server.
  3. Click OK.

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
  1. Click Re-acknowledge.
  2. Click OK.

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.

Removing a Server from a Chassis

Before You Begin

Physically remove the server from its chassis before performing the following procedure.


Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
  1. Click Decommission.
  2. Click OK.

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.

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 decommissions a server and deletes it from the Cisco UCS configuration. The server hardware physically remains in the Cisco UCS instance. However, Cisco UCS Manager ignores it and does not list it with the other servers in the chassis.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
  1. Click Decommission.
  2. Click OK.

The server is removed from the Cisco UCS configuration.

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
Option Description

The here link in the Situation area

Click this link and then click Yes in the confirmation dialog box. Cisco UCS Manager reacknowledges the slot and discovers the server in the slot.

OK

Click this button if you want to proceed to the General tab. You can use the Reacknowledge Slot link in the Actions area to have Cisco UCS Manager reacknowledge the slot and discover the server in the slot.

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
  1. Click Remove.
  2. Click OK.

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

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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

KVM Console

The KVM console is an interface accessible from the Cisco UCS Manager GUI or the KVM Launch Manager that emulates a direct KVM connection. Unlike the KVM dongle, which requires you to be physically connected to the server, the KVM console allows you to connect to the server from a remote location across the network.

Instead of using CD/DVD or floppy drives directly connected to the server, the KVM console uses virtual media, which are actual disk drives or disk image files that are mapped to virtual CD/DVD or floppy drives. You can map any of the following to virtual drives:


  • CD/DVD or floppy drives on your computer

  • Disk image files on your computer

  • CD/DVD or floppy drives on the network

  • Disk image files on the network

To install an OS from a virtual CD/DVD or floppy drive, you must ensure that the virtual CD/DVD or floppy drive is set as the first boot device in the service profile.

Installing an OS using the KVM console may be slower than using the KVM dongle because the installation files must be downloaded across the network to the server. If you map a disk drive or disk image file from a network share to a virtual drive, the installation may be even slower because the installation files must be downloaded from the network to the KVM console (your computer) and then from the KVM console to the server. When using this installation method, we recommend that you have the installation media as close as possible to the system with the KVM console.

Starting the KVM Console from a Server

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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.

Tip   

If the Caps Lock key on your keyboard is on when you open a KVM session, and you subsequently turn off your Caps Lock key, the KVM console may continue to act as if Caps Lock is turned on. To synchronize the KVM console and your keyboard, press Caps Lock once without the KVM console in focus and then press Caps Lock again with the KVM console in focus.

Starting the KVM Console from a Service Profile

Procedure
Step 1   In the Navigation pane, click the Servers tab.
Step 2   On the Servers tab, expand Servers > Service Profiles.
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.

Tip   

If the Caps Lock key on your keyboard is on when you open a KVM session, and you subsequently turn off your Caps Lock key, the KVM console may continue to act as if Caps Lock is turned on. To synchronize the KVM console and your keyboard, press Caps Lock once without the KVM console in focus and then press Caps Lock again with the KVM console in focus.

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.

Before You Begin

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.


Procedure
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:
  1. Enter your Cisco UCS username and password.
  2. Click OK.
Step 4   In the Service Profiles table of the KVM Launch Manager, do the following:
  1. Choose the service profile for which you need KVM access to the associated server.
  2. In the Launch KVM row for that service profile, click Launch.

    The KVM console opens in a separate window.

    Tip   

    If the Caps Lock key on your keyboard is on when you open a KVM session, and you subsequently turn off your Caps Lock key, the KVM console may continue to act as if Caps Lock is turned on. To synchronize the KVM console and your keyboard, press Caps Lock once without the KVM console in focus and then press Caps Lock again with the KVM console in focus.

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
  1. Click Reset CMOS.
  2. Click OK.

Resetting the CIMC for a Server

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
  1. Click Reset iCIMC (Server Controller).
  2. Click OK.

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.

Before You Begin
Important:

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.


Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
  1. Click Recover Corrupt BIOS.
  2. Click OK.
Step 7   In the Recover Corrupt BIOS dialog box, do the following:
  1. Complete the following fields:
    Name Description

    Version To Be Activated drop-down list

    Choose the firmware version that you want to activate from the drop-down list.

    Ignore Compatibility Check check box

    By default, Cisco UCS makes sure that the firmware version is compatible with everything running on the server before it activates that version.

    Check this check box if you want Cisco UCS to activate the firmware without making sure that it is compatible first.

    Note   

    We recommend that you use this option only when explicitly directed to do so by a technical support representative.

  2. Click OK.

Monitoring a Server

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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:
Option Description

General tab

Provides an overview of the status of the server, including a summary of any faults, a summary of the server properties, and a physical display of the server and its components.

Inventory tab

Provides details about the properties and status of the components of the server on the following subtabs:


  • Motherboard—Information about the motherboard and information about the server BIOS settings. You can also recover corrupt BIOS firmware from this subtab.

  • CIMC—Information about the CIMC and its firmware, and provides access to the SEL for the server. You can also update and activate the CIMC firmware from this subtab.

  • CPU—Information about each CPU in the server.

  • Memory—Information about each memory slot in the server and the DIMM in that slot.

  • Interface cards—Information about each adapter installed in the server.

  • HBAs—Properties of each HBA and the configuration of that HBA in the service profile associated with the server.

  • NICs—Properties of each NIC and the configuration of that NIC in the service profile associated with the server. You can expand each row to view information about the associated VIFs and vNICs.

  • Storage—Properties of the storage controller, the local disk configuration policy in the service profile associated with the server, and for each hard disk in the server.

Tip   

If the server contains one or more SATA devices, such as a hard disk drive or solid state drive, Cisco UCS Manager GUI displays the vendor name for the SATA device in the Vendor field.

However, Cisco UCS Manager CLI displays ATA in the Vendor field and includes the vendor information, such as the vendor name, in a Vendor Description field. This second field does not exist in Cisco UCS Manager GUI.

Virtual Machines

Displays details about any virtual machines hosted on the server.

Installed Firmware tab

Displays the firmware versions on the CIMC, adapters, and other server components. You can also use this tab to update and activate the firmware on those components.

Management Logs tab

Displays the system event log for the server.

Faults tab

Displays an overview of the faults generated by the server. You can click on any fault to view additional information.

Events tab

Displays an overview of the events generated by the server. You can click on any event to view additional information.

FSM tab

Provides details about the current FSM task running on the server, including the status of that task. You can use this information to diagnose errors with those tasks.

Statistics tab

Displays statistics about the server and its components. You can view these statistics in tabular or chart format.

Temperatures tab

Displays temperature statistics for the components of the server. You can view these statistics in tabular or chart format.

Power tab

Displays power statistics for the components of the server. You can view these statistics in tabular or chart format.

Step 5   In the Navigation pane, expand Server_ID > Interface Cards > Interface_Card_ID.
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:

  • Interface card

  • DCE interfaces

  • HBAs

  • NICs

Tip   

Expand the nodes in the table to view the child nodes. For example, if you expand a NIC node, you can view each VIF created on that NIC.

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.

Procedure
Step 1   In the Navigation pane, click the Equipment tab.
Step 2   On the Equipment tab, expand Equipment > Chassis > Chassis Number > Servers.
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.