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:
Consider the following guidelines when deciding whether to remove or decommission a chassis using Cisco UCS Manager:
Decommissioning is performed when a chassis is physically present and connected but you want to temporarily remove it from the configuration. Because it is expected that a decommissioned chassis will be eventually recommissioned, a portion of the chassis' information is retained by Cisco UCS Manager for future use.
Removing is performed when you physically remove a chassis from the system. Once the physical removal of the chassis is completed, the configuration for that chassis can be removed in Cisco UCS Manager.
Note |
You cannot remove a chassis from Cisco UCS Manager if it is physically present and connected. |
If you need to add a removed chassis back to the configuration, it must be reconnected and then rediscovered. During rediscovery Cisco UCS Manager will assign the chassis a new ID that may be different from ID that it held before.
Perform the following procedure if you increase or decrease the number of links that connect the chassis to the fabric interconnect. Acknowledging the chassis ensures that Cisco UCS Manager is aware of the change in the number of links and that traffics flows along all available links.
After you enable or disable a port on a fabric interconnect, wait for at least 1 minute before you reacknowledge the chassis. If you reacknowledge the chassis too soon, the pinning of server traffic from the chassis may not be updated with the changes to the port that you enabled or disabled.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# acknowledge chassis chassis-num | Acknowledges the specified chassis. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The following example acknowledges chassis 2 and commits the transaction:
UCS-A# acknowledge chassis 2 UCS-A* # commit-buffer UCS-A #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# decommission chassis chassis-num | Decommissions the specified chassis. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The decommission may take several minutes to complete.
The following example decommissions chassis 2 and commits the transaction:
UCS-A# decommission chassis 2 UCS-A* # commit-buffer UCS-A # show chassis Chassis: Chassis Overall Status Admin State ---------- ------------------------ ----------- 1 Operable Acknowledged 2 Accessibility Problem Decommission UCS-A #
Physically remove the chassis before performing the following procedure.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# remove chassis chassis-num | Removes the specified chassis. |
Step 2 | UCS-A# commit-buffer | Commits the transaction to the system configuration. |
The removal may take several minutes to complete.
The following example removes chassis 2 and commits the transaction:
UCS-A# remove chassis 2 UCS-A* # commit-buffer UCS-A #
This procedure returns the chassis to the configuration and applies the chassis discovery policy to the chassis. After this procedure, you can access the chassis and any servers in it.
Collect the following information about the chassis to be recommissioned:
The following example recommissions a Cisco UCS 5108 chassis and commits the transaction:
UCS-A# show chassis Chassis: Chassis Overall Status Admin State ---------- ------------------------ ----------- 1 Accessibility Problem Decommission UCS-A# recommission chassis "Cisco Systems Inc" "Cisco UCS 5108" FOX1252GNNN UCS-A* # commit-buffer UCS-A #
Note |
Chassis renumbering is supported in Cisco UCS Manager 1.4(2) and later releases. You cannot renumber a chassis in a prior release. |
If you are swapping IDs between chassis, you must first decommission both chassis and then wait for the chassis decommission FSM to complete before proceeding with the renumbering steps.
The following example decommissions two Cisco UCS 5108 chassis (chassis 7 and 8), switches their IDs, and commits the transaction:
UCS-A# show chassis inventory Chassis PID Vendor Serial (SN) HW Revision ------- --------- --------------- ----------- ------------- 1 N20-C6508 Cisco Systems Inc FOX1252GAAA 0 2 N20-C6508 Cisco Systems Inc FOX1252GBBB 0 3 N20-C6508 Cisco Systems Inc FOX1252GCCC 0 4 N20-C6508 Cisco Systems Inc FOX1252GDDD 0 5 N20-C6508 Cisco Systems Inc FOX1252GEEE 0 6 N20-C6508 Cisco Systems Inc FOX1252GFFF 0 7 N20-C6508 Cisco Systems Inc FOX1252GGGG 0 8 N20-C6508 Cisco Systems Inc FOX1252GHHH 0 9 N20-C6508 Cisco Systems Inc FOX1252GIII 0 10 N20-C6508 Cisco Systems Inc FOX1252GJJJ 0 11 N20-C6508 Cisco Systems Inc FOX1252GKKK 0 12 N20-C6508 Cisco Systems Inc FOX1252GLLL 0 13 N20-C6508 Cisco Systems Inc FOX1252GMMM 0 14 N20-C6508 Cisco Systems Inc FOX1252GNNN 0 UCS-A# decommission chassis "Cisco Systems Inc" "Cisco UCS 5108" FOX1252GHHH UCS-A*# commit-buffer UCS-A# decommission chassis "Cisco Systems Inc" "Cisco UCS 5108" FOX1252GIII UCS-A*# commit-buffer UCS-A# show chassis inventory Chassis PID Vendor Serial (SN) HW Revision ------- --------- --------------- ----------- ------------- 1 N20-C6508 Cisco Systems Inc FOX1252GAAA 0 2 N20-C6508 Cisco Systems Inc FOX1252GBBB 0 3 N20-C6508 Cisco Systems Inc FOX1252GCCC 0 4 N20-C6508 Cisco Systems Inc FOX1252GDDD 0 5 N20-C6508 Cisco Systems Inc FOX1252GEEE 0 6 N20-C6508 Cisco Systems Inc FOX1252GFFF 0 7 N20-C6508 Cisco Systems Inc FOX1252GGGG 0 10 N20-C6508 Cisco Systems Inc FOX1252GJJJ 0 11 N20-C6508 Cisco Systems Inc FOX1252GKKK 0 12 N20-C6508 Cisco Systems Inc FOX1252GLLL 0 13 N20-C6508 Cisco Systems Inc FOX1252GMMM 0 14 N20-C6508 Cisco Systems Inc FOX1252GNNN 0 UCS-A# show chassis decommissioned Chassis PID Vendor Serial (SN) HW Revision ------- --------- --------------- ----------- ------------- 8 N20-C6508 Cisco Systems Inc FOX1252GHHH 0 9 N20-C6508 Cisco Systems Inc FOX1252GIII 0 UCS-A# recommission chassis "Cisco Systems Inc" "Cisco UCS 5108" FOX1252GHHH 9 UCS-A* # commit-buffer UCS-A# recommission chassis "Cisco Systems Inc" "Cisco UCS 5108" FOX1252GIII 8 UCS-A* # commit-buffer UCS-A # show chassis inventory Chassis PID Vendor Serial (SN) HW Revision ------- --------- --------------- ----------- ------------- 1 N20-C6508 Cisco Systems Inc FOX1252GAAA 0 2 N20-C6508 Cisco Systems Inc FOX1252GBBB 0 3 N20-C6508 Cisco Systems Inc FOX1252GCCC 0 4 N20-C6508 Cisco Systems Inc FOX1252GDDD 0 5 N20-C6508 Cisco Systems Inc FOX1252GEEE 0 6 N20-C6508 Cisco Systems Inc FOX1252GFFF 0 7 N20-C6508 Cisco Systems Inc FOX1252GGGG 0 8 N20-C6508 Cisco Systems Inc FOX1252GIII 0 9 N20-C6508 Cisco Systems Inc FOX1252GHHH 0 10 N20-C6508 Cisco Systems Inc FOX1252GJJJ 0 11 N20-C6508 Cisco Systems Inc FOX1252GKKK 0 12 N20-C6508 Cisco Systems Inc FOX1252GLLL 0 13 N20-C6508 Cisco Systems Inc FOX1252GMMM 0 14 N20-C6508 Cisco Systems Inc FOX1252GNNN 0
Toggling the Locator LED
The following example turns on the locator LED for chassis 2 and commits the transaction:
UCS-A# scope chassis 2 UCS-A /chassis # enable locator-led UCS-A /chassis* # commit-buffer UCS-A /chassis #
The following example turns off the locator LED for chassis 2 and commits the transaction:
UCS-A# scope chassis 2 UCS-A /chassis # disable locator-led UCS-A /chassis* # commit-buffer UCS-A /chassis #