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:
Associate a service profile with a server or server pool.
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 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 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 server or server pool.
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 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 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 #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope server chassis-num / server-num | Enters chassis server mode for the specified server. |
Step 2 | UCS-A /chassis/server # cycle {cycle-immediate | cycle-wait} | Power cycles the server. Use the cycle-immediate keyword to immediately begin power cycling the 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 server 4 in chassis 2 and commits the transaction:
UCS-A# scope server 2/4 UCS-A /chassis/server # cycle cycle-immediate UCS-A /chassis/server* # commit-buffer UCS-A /chassis/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.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope server chassis-num / server-num | Enters chassis server mode for the specified server. |
Step 2 | UCS-A /chassis/server # reset {hard-reset-immediate | hard-reset-wait} | Performs a hard reset of the 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# commit-buffer | Commits the transaction to the system configuration. |
The following example performs an immediate hard reset of server 4 in chassis 2 and commits the transaction:
UCS-A# scope server 2/4 UCS-A /chassis/server # reset hard-reset-immediate UCS-A /chassis/server* # commit-buffer UCS-A /chassis/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 chassis-num / server-num | Acknowledges the specified server. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The following example acknowledges server 4 in chassis 2 and commits the transaction:
UCS-A# acknowledge server 2/4 UCS-A* # commit-buffer UCS-A #
Physically remove the server before performing the following procedure.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# remove server chassis-num / server-num | Removes the specified server. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The following example removes server 4 in chassis 2 and commits the transaction:
UCS-A# remove server 2/4 UCS-A* # commit-buffer UCS-A #
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 Acknowledging 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.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# decommission server chassis-num / server-num | Decommissions the specified server. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The following example decommissions server 4 in chassis 2 and commits the transaction:
UCS-A# decommission server 2/4 UCS-A* # commit-buffer UCS-A #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope server chassis-num / server-num | Enters chassis server mode for the specified chassis. |
Step 2 | UCS-A /chassis/server # enable locator-led | Turns on the server locator LED. |
Step 3 | UCS-A /chassis/server # commit-buffer | Commits the transaction to the system configuration. |
The following example turns on the locator LED for server 4 in chassis 2 and commits the transaction:
UCS-A# scope server 2/4 UCS-A /chassis/server # enable locator-led UCS-A /chassis/server* # commit-buffer UCS-A /chassis/server #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope server chassis-num / server-num | Enters chassis mode for the specified chassis. |
Step 2 | UCS-A /chassis/server # disable locator-led | Turns off the server locator LED. |
Step 3 | UCS-A /chassis/server # commit-buffer | Commits the transaction to the system configuration. |
The following example turns off the locator LED for server 4 in chassis 2 and commits the transaction:
UCS-A# scope chassis 2/4 UCS-A /chassis/server # disable locator-led UCS-A /chassis/server* # commit-buffer UCS-A /chassis/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.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope server chassis-num / server-num | Enters chassis server mode for the specified chassis. |
Step 2 | UCS-A /chassis/server # reset-cmos | Resets the CMOS for the server. |
Step 3 | UCS-A /chassis/server # commit-buffer | Commits the transaction to the system configuration. |
The following example resets the CMOS for server 4 in chassis 2 and commits the transaction:
UCS-A# scope server 2/4 UCS-A /chassis/server # reset-cmos UCS-A /chassis/server* # commit-buffer UCS-A /chassis/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.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope server chassis-num / server-num | Enters chassis server mode for the specified chassis. |
Step 2 | UCS-A /chassis/server # scope bmc | Enters chassis server BMC mode |
Step 3 | UCS-A /chassis/server/bmc # reset | Resets the BMC for the server. |
Step 4 | UCS-A /chassis/server/bmc # commit-buffer | Commits the transaction to the system configuration. |
The following example resets the BMC for server 4 in chassis 2 and commits the transaction:
UCS-A# scope server 2/4 UCS-A /chassis/server # scope bmc UCS-A /chassis/server/cimc # reset UCS-A /chassis/server/cimc* # commit-buffer UCS-A /chassis/server/cimc #