Chassis Management

Chassis Management in Cisco UCS Manager CLI

You can manage and monitor all chassis in a Cisco UCS domain through Cisco UCS Manager CLI.

Cisco UCS X9508 Series Chassis

The Cisco UCS X-Series Modular System begins with the Cisco UCS X9508 Chassis. With a midplane-free design, I/O connectivity for the X9508 chassis is accomplished with frontloading, vertically oriented compute nodes intersecting with horizontally oriented I/O connectivity modules in the rear of the chassis. A unified Ethernet fabric is supplied with the Cisco UCS 9108 Intelligent Fabric Modules.

The system is primed with Cisco UCS 9108 Intelligent Fabric Modules that provide a robust Ethernet fabric and is set to accommodate emerging protocols with the innovative Cisco UCS X-Fabric Technology, ensuring easy upgrades with new modules as they become available.

The major feature of the chassis include:

  • 7-Rack-Unit (7RU) chassis has 8x front-facing flexible slots. These can house a combination of compute nodes and a pool of future I/O resources that may include GPU accelerators, disk storage, and nonvolatile memory.

  • 2x Cisco UCS 9108 Intelligent Fabric Modules (IFMs) at the top of the chassis that connect the chassis to upstream Cisco UCS 6400 Series Fabric Interconnects. Each IFM features.

    • Up to 100 Gbps of unified fabric connectivity per compute node

    • 8x 25-Gbps SFP28 uplink ports. The unified fabric carries management traffic to the Cisco Intersight cloud-operations platform, Fibre Channel over Ethernet (FCoE) traffic, and production Ethernet traffic to the fabric interconnects.

  • At the bottom are slots ready to house future I/O modules that can flexibly connect the compute modules with I/O devices. We call this connectivity Cisco UCS X-Fabric technology because “X” is a variable that can evolve with new technology developments.

  • Six 2800W Power Supply Units (PSUs) provide 54V power to the chassis with N, N+1, and N+N redundancy. A higher voltage allows efficient power delivery with less copper and reduced power loss.

  • Efficient, 4x100mm, dual counter-rotating fans deliver industry-leading airflow and power efficiency. Optimized thermal algorithms enable different cooling modes to best support the network environment. Cooling is modular so that future enhancements can potentially handle open- or closed-loop liquid cooling to support even higher-power processors.

The Cisco UCS X-Series Direct, identified as UCSX-S9108-100G, enhances the Cisco UCS X-Series Modular System by incorporating a pair of internal Cisco UCS Fabric Interconnects S9108 100G. This integration creates a self-contained system that connects up to eight server nodes with unified fabric, IP, and Fibre Channel connectivity, all managed by Cisco UCS Manager. The X-Series Direct is compatible with all components of the X-Series Modular System.

This Cisco UCS X9508 Chassis supports Cisco UCS 6664, Cisco UCS X-Series Direct, Cisco UCS 6536, UCS 6454, UCS 64108 Fabric Interconnects.

For more information, see Cisco UCS X9508 Chassis Data Sheet.

Secondary Cisco UCS X9508 Chassis for Cisco UCS X-Series Direct

Cisco UCS Manager Release 6.0(1b) introduces support for adding a secondary Cisco UCS X9508 chassis to an existing Cisco UCS Fabric Interconnects 9108 100G (Cisco UCS X-Series Direct) configuration. This enhancement increases system scalability and flexibility, enabling easier expansion of your data center infrastructure to meet changing application demands.

Each Cisco UCS X9508 chassis supports up to 8 server nodes, allowing the following configurations and supporting a total of up to 20 servers within the same management domain:

  • Up to 16 X-Series Compute Nodes when two chassis are connected (8 servers per chassis × 2 chassis).

  • Up to four C-Series rack servers can also be connected.

  • The chassis supports one or more of the following servers:

    • Up to eight two-socket Cisco UCS X215c M8 Compute Nodes

    • Up to eight two-socket Cisco UCS X210c M6/M7/M8 Compute Nodes

    • Up to four four-socket Cisco UCS X410c M7 Compute Nodes

    • Up to four Cisco UCS C220 M7/M8 Servers

    • Up to four Cisco UCS C240 M7/M8 Servers

    • Up to four Cisco UCS C225 M7/M8 Servers

    • Up to four Cisco UCS C245 M7/M8 Servers

To add a secondary chassis and C-Series rack servers, do the following:

  • Connect the secondary Cisco UCS X9508 chassis to the existing X-Series Direct setup.

  • Add and configure the supported Cisco UCS C-Series rack servers as part of the domain.

  • Configure the server ports and wait for the secondary chassis and rack servers to be discovered.


Note


In Cisco UCS X-Series Direct configurations, actions such as recommission, decommission, and remove are available only for the secondary Cisco UCS X9508 chassis; these actions cannot be performed on the primary Cisco UCS X9508 chassis.


Cisco UCS 5108 Blade Server Chassis

The Cisco UCS 5100 Series Blade Server Chassis is logically part of the fabric interconnects, thus creating a single, coherent management domain and decreasing management complexity. In the management domain, server management is handled by the fabric interconnect, while I/O and network management is extended to every chassis and blade server. Basing the I/O infrastructure on a unified fabric allows the Cisco Unified Computing System to have a simple and streamlined chassis yet offer a comprehensive set of I/O options. This results in the chassis having only five basic components:

  • The physical chassis with passive midplane and active environmental monitoring circuitry

  • Four power-supply bays with power entry in the rear, and redundant-capable, hot-swappable power supply units accessible from the front panel

  • Eight hot-swappable fan trays, each with two fans

  • Two fabric extender slots accessible from the back panel

  • Eight blade server slots accessible from the front panel

The blade server chassis has flexible partitioning with removable dividers to handle two blade server form factors:

  • Half-width blade servers have access to power and two 10GBASE-KR connections, one to each fabric extender slot.

  • Full-width blade servers connect to power and two connections to each fabric extender.

Guidelines for Removing and Decommissioning Chassis

Consider the following guidelines when deciding whether to remove or decommission a chassis using Cisco UCS Manager:

Decommissioning a Chassis

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 a Chassis

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.

Acknowledging a Chassis

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 re-acknowledge the chassis. If you re-acknowledge the chassis too soon, the pinning of server traffic from the chassis might not get updated with the changes to the port that you enabled or disabled.

Procedure

  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.

Example

The following example acknowledges chassis 2 and commits the transaction:

UCS-A# acknowledge chassis 2
UCS-A* # commit-buffer
UCS-A # 

Decommissioning a Chassis

Procedure

  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.

Example

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 # 

Removing a Chassis

Before you begin

Physically remove the chassis before performing the following procedure.

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.

Example

The following example removes chassis 2 and commits the transaction:

UCS-A# remove chassis 2
UCS-A* # commit-buffer
UCS-A # 

Recommissioning a Chassis

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.


Note


This procedure is not applicable for Cisco UCS S3260 Chassis.


Before you begin

Collect the following information about the chassis to be recommissioned by using the show chassis decommissioned or show chassis inventory commands:

  • Vendor name

  • Model name

  • Serial number

Procedure

  Command or Action Purpose

Step 1

UCS-A# recommission chassis vendor-name model-name serial-num

Recommissions the specified chassis.

Step 2

UCS-A# commit-buffer

Commits the transaction to the system configuration.

Note

 

After recommissioning a chassis and committing the transaction, if you immediately run the show chassis command, you may not see any change in the Admin State of the chassis. It may take a while before the state of the chassis changes after it is recommissioned.

Example

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" "N20-C6508" FOX1252GNNN
UCS-A* # commit-buffer
UCS-A # 

Renumbering a Chassis


Note


You cannot renumber a blade server through Cisco UCS Manager. The ID assigned to a blade server is determined by its physical slot in the chassis. To renumber a blade server, you must physically move the server to a different slot in the chassis.



Note


This procedure is not applicable for Cisco UCS S3260 Chassis.


Before you begin

If you are swapping IDs between chassis, you must first decommission both chassis, then wait for the chassis decommission FSM to complete before proceeding with the renumbering steps.

Procedure

  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 following:

  • The chassis you want to renumber

  • A chassis with the number 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.

Example

The following example decommissions two Cisco UCS chassis (chassis 8 and 9), 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 8
UCS-A*# commit-buffer
UCS-A# decommission chassis 9
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" "N20-C6508" FOX1252GHHH 9
UCS-A* # commit-buffer
UCS-A# recommission chassis "Cisco Systems Inc" "N20-C6508" 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 

Turning On the Locator LED for a Chassis

Procedure

  Command or Action Purpose

Step 1

UCS-A# scope chassis chassis-num

Enters chassis mode for the specified chassis.

Step 2

UCS-A /chassis # enable locator-led

Turns on the chassis locator LED.

Step 3

UCS-A /chassis # commit-buffer

Commits the transaction to the system configuration.

Example

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 # 

Turning Off the Locator LED for a Chassis

Procedure

  Command or Action Purpose

Step 1

UCS-A# scope chassis chassis-num

Enters chassis mode for the specified chassis.

Step 2

UCS-A /chassis # disable locator-led

Turns off the chassis locator LED.

Step 3

UCS-A /chassis # commit-buffer

Commits the transaction to the system configuration.

Example

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 #