Contents

• Managing Rack-Mount Servers
• Rack-Mount Server Management
• Booting a Rack Server
• Shutting Down a Rack Server
• Power Cycling a Rack Server
• Performing a Hard Reset on a Rack Server
• Acknowledging a Rack Server
• Decommissioning a Rack Server
• Turning On the Locator LED for a Rack Server
• Turning Off the Locator LED for a Rack Server
• Resetting the CMOS for a Rack Server
• Resetting the CIMC for a Rack Server
• Recovering the Corrupt BIOS on a Rack Server
• Showing the Status for a Rack-Mount Server

Managing Rack-Mount Servers

---

This chapter includes the following sections:

• Rack-Mount Server Management
• Booting a Rack Server
• Shutting Down a Rack Server
• Power Cycling a Rack Server
• Performing a Hard Reset on a Rack Server
• Acknowledging a Rack Server
• Decommissioning a Rack Server
• Turning On the Locator LED for a Rack Server
• Turning Off the Locator LED for a Rack Server
• Resetting the CMOS for a Rack Server
• Resetting the CIMC for a Rack Server
• Recovering the Corrupt BIOS on a Rack Server
• Showing the Status for a Rack-Mount Server

Rack-Mount Server Management

You can manage and monitor all rack-mount servers that have been integrated with a Cisco UCS instance through Cisco UCS Manager. All management and monitoring features are supported for rack-mount servers except power capping. Some rack-mount server management tasks, such as changes to the power state, can be performed from both the server and service profile. The remaining management tasks can only be performed on the server.

Cisco UCS Manager provides information, errors, and faults for each rack-mount server that it has discovered.

Tip	For information about how to integrate a supported Cisco UCS rack-mount server with Cisco UCS Manager, see the hardware installation guide for that server.

Booting a Rack Server

Before You Begin

Associate a service profile with a rack server.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope org org-name	Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name .
Step 2	UCS-A /org # scope service-profile profile-name	Enters organization service profile mode for the specified service profile.
Step 3	UCS-A /org/service-profile # power up	Boots the rack server associated with the service profile.
Step 4	UCS-A /org/service-profile # commit-buffer	Commits the transaction to the system configuration.

The following example boots the rack server associated with the service profile named ServProf34 and commits the transaction:

UCS-A# scope org /
UCS-A /org* # scope service-profile ServProf34
UCS-A /org/service-profile # power up
UCS-A /org/service-profile* # commit-buffer
UCS-A /org/service-profile #

Shutting Down a Rack 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.

Before You Begin

Associate a service profile with a rack server.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope org org-name	Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name.
Step 2	UCS-A /org # scope service-profile profile-name	Enters organization service profile mode for the specified service profile.
Step 3	UCS-A /org/service-profile # power down	Shuts down the rack server associated with the service profile.
Step 4	UCS-A /org/service-profile # commit-buffer	Commits the transaction to the system configuration.

The following example shuts down the rack server associated with the service profile named ServProf34 and commits the transaction:

UCS-A# scope org /
UCS-A /org # scope service-profile ServProf34
UCS-A /org/service-profile # power down
UCS-A /org/service-profile* # commit-buffer
UCS-A /org/service-profile #

Power Cycling a Rack Server

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope server server-num	Enters server mode for the specified rack server.
Step 2	UCS-A /server # cycle {cycle-immediate | cycle-wait}	Power cycles the rack server. Use the cycle-immediate keyword to immediately begin power cycling the rack server; use the cycle-wait keyword to schedule the power cycle to begin after all pending management operations have completed.
Step 3	UCS-A# commit-buffer	Commits the transaction to the system configuration.

The following example immediately power cycles rack server 2 and commits the transaction:

UCS-A#  scope server 2
UCS-A /server # cycle cycle-immediate
UCS-A /server* # commit-buffer
UCS-A /server # 

Performing a Hard Reset on a Rack Server

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.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope server server-num	Enters server mode for the specified server.
Step 2	UCS-A /server # reset {hard-reset-immediate | hard-reset-wait}	Performs a hard reset of the rack server. Use the hard-reset-immediate keyword to immediately begin hard resetting the server; use the hard-reset-wait keyword to schedule the hard reset to begin after all pending management operations have completed.
Step 3	UCS-A /server # commit-buffer	Commits the transaction to the system configuration.

The following example performs an immediate hard reset of rack server 2 and commits the transaction:

UCS-A#  scope server 2
UCS-A /server # reset hard-reset-immediate
UCS-A /server* # commit-buffer
UCS-A /server # 

Acknowledging a Rack 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

	Command or Action	Purpose
Step 1	UCS-A# acknowledge server server-num	Acknowledges the specified rack server.
Step 2	UCS-A# commit-buffer	Commits the transaction to the system configuration.

The following example acknowledges server 2 and commits the transaction:

UCS-A#  acknowledge server 2
UCS-A* # commit-buffer
UCS-A # 

Decommissioning a Rack 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.

Procedure

	Command or Action	Purpose
Step 1	UCS-A# decommission server server-num	Decommissions the specified rack server.
Step 2	UCS-A# commit-buffer	Commits the transaction to the system configuration.

The following example decommissions rack server 2 and commits the transaction:

UCS-A# decommission server 2
UCS-A* # commit-buffer
UCS-A # 

Turning On the Locator LED for a Rack Server

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope server server-num	Enters server mode for the specified rack server.
Step 2	UCS-A /server # enable locator-led	Turns on the server locator LED.
Step 3	UCS-A /server # commit-buffer	Commits the transaction to the system configuration.

The following example turns on the locator LED for server 2 and commits the transaction:

UCS-A# scope server 2
UCS-A /server # enable  locator-led
UCS-A /server* # commit-buffer
UCS-A /server # 

Turning Off the Locator LED for a Rack Server

Procedure

	Command or Action	Purpose
Step 1	UCS-A# scope server server-num	Enters server mode for the specified server.
Step 2	UCS-A /server # disable locator-led	Turns off the rack server locator LED.
Step 3	UCS-A /server # commit-buffer	Commits the transaction to the system configuration.

The following example turns off the locator LED for rack server 2 and commits the transaction:

UCS-A# scope server 2
UCS-A /server # disable  locator-led
UCS-A /server* # commit-buffer
UCS-A /server # 

Resetting the CMOS for a Rack 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

	Command or Action	Purpose
Step 1	UCS-A# scope server server-num	Enters server mode for the rack server.
Step 2	UCS-A /server # reset-cmos	Resets the CMOS for the rack server.
Step 3	UCS-A /server # commit-buffer	Commits the transaction to the system configuration.

The following example resets the CMOS for rack server 2 and commits the transaction:

UCS-A# scope server 2
UCS-A /server # reset-cmos
UCS-A /server* # commit-buffer
UCS-A /server #  

Resetting the CIMC for a Rack 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

	Command or Action	Purpose
Step 1	UCS-A# scope server server-num	Enters server mode for the specified rack server.
Step 2	UCS-A /server # scope CIMC	Enters server CIMC mode
Step 3	UCS-A /server/CIMC # reset	Resets the CIMC for the rack server.
Step 4	UCS-A /server/CIMC # commit-buffer	Commits the transaction to the system configuration.

The following example resets the CIMC for rack server 2 and commits the transaction:

UCS-A# scope server 2
UCS-A /server # scope CIMC
UCS-A /server/cimc # reset
UCS-A /server/cimc* # commit-buffer
UCS-A /server/cimc #  

Recovering the Corrupt BIOS on a Rack Server

On rare occasions, an issue with a rack 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 rack server boots with the running version of the firmware for that 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

	Command or Action	Purpose
Step 1	UCS-A# scope server server-id	Enters server mode for the specified rack server.
Step 2	UCS-A /server # recover-bios version ignorecompcheck	Loads and activates the specified BIOS version. To activate the firmware without making sure that it is compatible first, include the ignorecompcheck keyword. We recommend that you use this option only when explicitly directed to do so by a technical support representative.
Step 3	UCS-A /server # commit-buffer	Commits the transaction.

The following example shows how to recover the BIOS:

UCS-A# scope server 1
UCS-A /server # recover-bios S5500.0044.0.3.1.010620101125
UCS-A /server* # commit-buffer
UCS-A /server # 

Showing the Status for a Rack-Mount Server

Procedure

	Command or Action	Purpose
Step 1	UCS-A# show server status	Shows the status for all servers in the Cisco UCS instance.

The following example shows the status for all servers in the Cisco UCS instance. The servers numbered 1 and 2 do not have a slot listed in the table because they are rack servers.

Server Slot  Status    Availability  Overall Status  Discovery
--------------------------------------------------------------------
1/1          Equipped  Unavailable   Ok              Complete  
1/2          Equipped  Unavailable   Ok              Complete  
1/3          Equipped  Unavailable   Ok              Complete  
1/4          Empty     Unavailable   Ok              Complete  
1/5          Equipped  Unavailable   Ok              Complete  
1/6          Equipped  Unavailable   Ok              Complete  
1/7          Empty     Unavailable   Ok              Complete  
1/8          Empty     Unavailable   Ok              Complete
1            Equipped  Unavailable   Ok              Complete 
2            Equipped  Unavailable   Ok              Complete