The Cisco UCSME-4308
modular chassis consists of the following main components:
cartridges that host the modular servers.
adapter that uses system link technology to manage all the traffic that flows
between hosts and the management entities in the chassis.
controller and backplane SSDs.
PSUs, fans, and
a Chassis Management Controller.
You can manage and
monitor all these components through Cisco UCS Manager.
Removing and Decommissioning Chassis
following guidelines when deciding whether to remove or decommission a chassis
Cisco UCS Manager:
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.
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.
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.
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
Reprovisioning a removed chassis is
similar to provisioning a new chassis.
chassis ensures that Cisco UCS Manager is aware of the current physical
configuration of the chassis.
transaction to the system configuration.
example acknowledges chassis 2 and commits the transaction:
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
To see which
chassis have been decommissioned, issue the
Discovery Status, introduced in Cisco UCS Manager Release 2.5,
indicates the sides from which the chassis is fully discovered. While the
Connection Path attribute indicates the basic reachability of the chassis from
a particular FI, the Discovery Status attribute indicates that the chassis
inventory has been completed on that side.
example shows the information about the specified chassis:
UCS-A # scope chassis 1
UCS-A /chassis* # show detail
Overall Status: Operable
Oper qualifier: N/A
Conf State: Ok
Admin State: Acknowledged
Conn Path: A,B
Conn Status: A,B
Discovery Status: A,B
Managing Instance: B
Product Name: Cisco UCS 4308
Part Number: 68-5199-02
Vendor: Cisco Systems Inc
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
Showing the Status
of all the Servers in the Cisco UCS Domain
1. UCS-A #
Shows the status
for all servers in the Cisco UCS domain.
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
Turning On the Locator LED for a Chassis
1.UCS-A# scope chassischassis-num
2.UCS-A /chassis # enable locator-led
3.UCS-A /chassis # commit-buffer
UCS-A# scope chassischassis-num
Enters chassis mode for the specified chassis.
UCS-A /chassis # enable locator-led
Turns on the chassis locator LED.
UCS-A /chassis # commit-buffer
Commits the transaction to the system configuration.
The following example turns on the locator LED for chassis 2 and commits the transaction: