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 part contains the following chapters:
The Cisco UCSME-4308 modular chassis consists of the following main components:
Compute cartridges that host the modular servers.
A shared adapter that uses system link technology to manage all the traffic that flows between hosts and the management entities in the chassis.
A storage controller and backplane SSDs.
PSUs, fans, and a Chassis Management Controller.
You can manage and monitor all these components through Cisco UCS Manager.
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 Cisco UCS Manager 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. |
When the chassis ID changes to x, its service profile association also changes. Service profiles that were previously associated with chassis x will now be associated with this chassis. This will result in requests for creation of new virtual drives. The existing virtual drives will then go into the orphaned state.
In this scenario, virtual drive creation could fail due to free space limitation, or due to disk groups being different. In either case, you will have to delete the orphaned virtual drives for service profile association to succeed.
Reprovisioning a removed chassis is similar to provisioning a new chassis.
Acknowledging the chassis ensures that Cisco UCS Manager is aware of the current physical configuration of the chassis.
1. UCS-A# acknowledge chassis chassis-num
2. UCS-A# commit-buffer
Command or Action | Purpose |
---|
The following example acknowledges chassis 2 and commits the transaction:
UCS-A# acknowledge chassis 2 UCS-A* # commit-buffer UCS-A #
1. UCS-A# decommission chassis chassis-num
2. UCS-A# commit-buffer
Command or Action | Purpose |
---|
The decommission may take several minutes to complete.
The following example decommissions chassis 2 and commits the transaction in a set up with 2 chassis:
UCS-A# decommission chassis 2 UCS-A* # commit-buffer UCS-A # show chassis Chassis: Chassis Overall Status Admin State ---------- ------------------------ ----------- 1 Operable Acknowledged 2 Decomissioning Acknowledged UCS-A # show chassis decommissioned Vendor Model Serial (SN) Chassis ID ---------- ---------- ----------- ---------- Cisco Systems Inc UCSME-4308 FHH1816P06E 2 UCS-A # show chassis Chassis: Chassis Overall Status Admin State ---------- ------------------------ ----------- 1 Operable Acknowledged
Physically remove the chassis before performing the following procedure.
1. UCS-A# remove chassis chassis-num
2. UCS-A# commit-buffer
Command or Action | Purpose |
---|
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 #
Collect the following information about the chassis to be recommissioned by using the show chassis decommissioned or show chassis inventory commands:
1. UCS-A# recommission chassis vendor-name model-name serial-num
2. UCS-A# commit-buffer
The following example recommissions a Cisco UCS 4308 chassis and commits the transaction:
UCS-A# show chassis decommissioned Chassis: Chassis Overall Status Admin State ---------- ------------------------ ----------- 1 Accessibility Problem Decommission UCS-A# recommission chassis "Cisco Systems Inc" "UCSME-4308" FCH1828V370 UCS-A* # commit-buffer UCS-A# show chassis decommissioned UCS-A #
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.
1. UCS-A# show chassis inventory
2. Verify that the chassis inventory does not include the chassis that you want to renumber and a chassis with the number that you want to use.
3. UCS-A# recommission chassis vendor-name model-name serial-num [chassis-num]
4. UCS-A# commit-buffer
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# show chassis inventory |
Displays information about your chassis. |
Step 2 | Verify that the chassis inventory does not include the chassis that you want to renumber and a chassis with the number that you want to use. |
If either of these chassis are listed in the chassis inventory, decommission those chassis. You must wait until the decommission FSM is complete and the chassis are not listed in the chassis inventory before continuing. This might take several minutes. To see which chassis have been decommissioned, issue the show chassis decommissioned command. |
Step 3 | UCS-A# recommission chassis vendor-name model-name serial-num [chassis-num] |
Recommissions and renumbers the specified chassis. |
Step 4 | UCS-A# commit-buffer |
Commits the transaction to the system configuration. |
The following example decommissions two Cisco UCS chassis (chassis 2 and 3), switches their IDs, and commits the transaction:
UCS-A# show chassis inventory Chassis PID Vendor Serial (SN) HW Revision ------- --------- --------------- ----------- ------------- 1 UCSME-4308 Cisco Systems Inc FHH1816P06D 0 2 UCSME-4308 Cisco Systems Inc FCH1840V04T 0 3 UCSME-4308 Cisco Systems Inc FCH1828V2HL 0 4 UCSME-4308 Cisco Systems Inc FCH1828V370 0 UCS-A# decommission chassis "Cisco Systems Inc" "UCSME-4308" FCH1840V04T UCS-A*# commit-buffer UCS-A# decommission chassis "Cisco Systems Inc" "UCSME-4308" FCH1828V2HL UCS-A*# commit-buffer UCS-A# show chassis inventory Chassis PID Vendor Serial (SN) HW Revision ------- --------- --------------- ----------- ------------- 1 UCSME-4308 Cisco Systems Inc FHH1816P06D 0 4 UCSME-4308 Cisco Systems Inc FCH1828V370 0 UCS-A# show chassis decommissioned Chassis PID Vendor Serial (SN) HW Revision ------- --------- --------------- ----------- ------------- 2 UCSME-4308 Cisco Systems Inc FCH1840V04T 0 3 UCSME-4308 Cisco Systems Inc FCH1828V2HL 0 UCS-A# recommission chassis "Cisco Systems Inc" "UCSME-4308" FCH1840V04T 3 UCS-A* # commit-buffer UCS-A# recommission chassis "Cisco Systems Inc" "UCSME-4308" FCH1828V2HL 2 UCS-A* # commit-buffer UCS-A # show chassis inventory Chassis PID Vendor Serial (SN) HW Revision ------- --------- --------------- ----------- ------------- 1 UCSME-4308 Cisco Systems Inc FHH1816P06D 0 2 UCSME-4308 Cisco Systems Inc FCH1828V2HL 0 3 UCSME-4308 Cisco Systems Inc FCH1840V04T 0 4 UCSME-4308 Cisco Systems Inc FCH1828V370 0
You can display all the cartridges in a specified chassis from the chassis mode. You can also display the status of all the cartridges from the EXEC mode.
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # show cartridge
Command or Action | Purpose |
---|
UCS-A # scope chassis 1 UCS-A /chassis # show cartridge Cartridge: Slot ID PID Presence ---------- ---------- -------- 1 UCSME-142-M4 Equipped 2 UCSME-142-M4 Equipped 3 UCSME-142-M4 Equipped 4 UCSME-142-M4 Equipped 5 UCSME-142-M4 Equipped 6 UCSME-142-M4 Equipped 7 UCSME-142-M4 Equipped 8 UCSME-142-M4 Equipped
The following example shows the status of all the cartridges from the EXEC mode:
UCS-A # show cartridge status Cartridge Slot Status PID ---------- --------------------------------- --- 1/1 Equipped UCSME-142-M4 1/2 Equipped UCSME-142-M4 1/3 Equipped UCSME-142-M4 1/4 Equipped UCSME-142-M4 1/5 Equipped UCSME-142-M4 1/6 Equipped UCSME-142-M4 1/7 Equipped UCSME-142-M4 1/8 Equipped UCSME-142-M4 2/1 Equipped UCSHD-B162-M4 2/2 Equipped UCSME-142-M4 2/3 Equipped UCSME-142-M4 2/4 Empty 2/5 Empty 2/6 Empty 2/7 Empty 2/8 Empty
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # show detail
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCS-A# scope chassis chassis-num |
Enters chassis mode for the specified chassis. | ||
Step 2 | UCS-A /chassis # show detail |
Displays information about the specified chassis.
|
The following example shows the information about the specified chassis:
UCS-A # scope chassis 1 UCS-A /chassis* # show detail Chassis: Chassis: 1 User Label: Overall Status: Operable Oper qualifier: N/A Operability: N/A Conf State: Ok Admin State: Acknowledged Conn Path: A,B Conn Status: A,B Discovery Status: A,B Presence: Unknown Managing Instance: B Product Name: Cisco UCS 4308 PID: UCSME-4308 VID: V00 Part Number: 68-5199-02 Vendor: Cisco Systems Inc Model: UCSME-4308 Serial (SN): FCH1842V1QV HW Revision: 0 Mfg Date: 2014-10-16T00:00:00.000 Power State: Ok Thermal Status: Ok SEEPROM operability status: N/A Current Task:
1. UCS-A # show server status
Command or Action | Purpose |
---|
The following example shows the status for all servers in the Cisco UCS domain:
UCS-A # show server status Server Slot Status Availability Overall Status Discovery ------- --------------------------------- ------------ --------------------- --------- 1/1/1 Equipped Unavailable Ok Complete 1/1/2 Equipped Unavailable Ok Complete 1/2/1 Equipped Unavailable Ok Complete 1/2/2 Equipped Unavailable Ok Complete 1/3/1 Equipped Unavailable Ok Complete 1/3/2 Equipped Unavailable Ok Complete 1/4/1 Equipped Unavailable Ok Complete 1/4/2 Equipped Unavailable Ok Complete 1/5/1 Equipped Unavailable Ok Complete 1/5/2 Equipped Unavailable Ok Complete 1/6/1 Equipped Unavailable Ok Complete 1/6/2 Equipped Unavailable Ok Complete 1/7/1 Equipped Unavailable Ok Complete 1/7/2 Equipped Unavailable Ok Complete 1/8/1 Equipped Unavailable Ok Complete 1/8/2 Equipped Unavailable Ok Complete 2/1/1 Equipped Available Unassociated Complete 2/1/2 Equipped Available Unassociated Complete 2/2/1 Equipped Available Unassociated Complete 2/2/2 Equipped Available Unassociated Complete 2/3/1 Equipped Available Unassociated Complete 2/3/2 Equipped Available Unassociated Complete
Toggling the Locator LED
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # enable locator-led
3. UCS-A /chassis # commit-buffer
Command or Action | Purpose |
---|
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 #
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # disable locator-led
3. UCS-A /chassis # commit-buffer
Command or Action | Purpose |
---|
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 #