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 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. |
Consider the following guidelines when deciding whether to remove or decommission a rack-mount server using Cisco UCS Manager:
Decommissioning is performed when a rack-mount server is physically present and connected but you want to temporarily remove it from the configuration. Because it is expected that a decommissioned rack-mount 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 the server from the system by disconnecting the rack-mount server from the fabric extender. You cannot remove a rack-mount server from Cisco UCS Manager if it is physically present and connected to the fabric extender. Once the rack-mount server is disconnected, the configuration for that rack-mount server can be removed in Cisco UCS Manager.
During removal, management interfaces are disconnected, 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 rack-mount 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.
Associate a service profile with a rack-mount server.
The following example boots the rack-mount 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 #
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.
Associate a service profile with a rack-mount server.
The following example shuts down the rack-mount 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 #
The following example immediately power cycles rack-mount 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 #
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.
The following example performs an immediate hard reset of rack-mount 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 #
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.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# acknowledge server server-num | Acknowledges the specified rack-mount server. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The following example acknowledges rack-mount server 2 and commits the transaction:
UCS-A# acknowledge server 2 UCS-A* # commit-buffer UCS-A #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# decommission server server-num | Decommissions the specified rack-mount server. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The following example decommissions rack-mount server 2 and commits the transaction:
UCS-A# decommission server 2 UCS-A* # commit-buffer UCS-A #
Physically disconnect the CIMC LOM cables that connect the rack-mount server to the fabric extender before performing the following procedure. For high availability setups, remove both cables.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# remove server server-num | Removes the specified rack-mount server. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The following example removes rack-mount server 4 and commits the transaction:
UCS-A# remove server 4 UCS-A* # commit-buffer UCS-A #
If you physically reconnect the rack-mount server, you must re-acknowledge it to have Cisco UCS Manager rediscover the server.
For more information, see Acknowledging a Rack-Mount Server.
The following example turns on the locator LED for rack-mount 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 #
The following example turns off the locator LED for rack-mount 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 #
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.
The following example resets the CMOS for rack-mount server 2 and commits the transaction:
UCS-A# scope server 2 UCS-A /server # reset-cmos UCS-A /server* # commit-buffer UCS-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.
The following example resets the CIMC for rack-mount 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 #
On rare occasions, an issue with a rack-mount server may require you to recover the corrupted BIOS. This procedure is not part of the normal maintenance of a rack-mount server. After you recover the BIOS, the rack-mount server boots with the running version of the firmware for that 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.
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 #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# show server status | Shows the status for all servers in the Cisco UCS instance. |
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