Cisco UCS Servers

Server Management

With global policies, global server pools and firmware management in Cisco UCS Central, you can manage general and complex server deployments for the following servers in your registered UCS domains:

  • Cisco UCS B-Series Blade Servers

  • Cisco UCS C-Series Rack-Mount Servers

  • Cisco UCS Mini

Cisco UCS X-Series Direct and Components:

  • Cisco UCS X-Series Direct Supported Chassis—Cisco UCS X9508 Chassis

  • Cisco UCS X-Series Direct Supported Blade Servers—X215c M8, X210c M7, X410c M7, X210c M6

  • Cisco UCS X-Series Direct Supported Fabric Interconnects—Cisco UCSX-I-9108-100G, UCSX-I-9108-25G

  • Cisco UCS X9508 Server Chassis equipped with X-Fabric Module

Cisco UCS X-Series Direct and Components

Cisco UCS X-Series Direct

Cisco UCS X-Series Direct®

The Cisco UCS X-Series Direct® simplifies your data center, adapting to the unpredictable needs of modern applications while also providing an edge scaled for remote branch office workloads. It minimizes the IT infrastructure deployed at edge locations to achieve desired business outcomes. As you are looking to increase the number of applications at the edge while deploying as little IT infrastructure as possible, the Cisco UCS X-Series Direct®, powered by Cisco Intersight® and Cisco UCS Central, enables the benefits of scale together with a secure and unified connectivity.

The Cisco UCS X-Series Direct begins with the Cisco UCS X9508 Chassis engineered to be adaptable and future ready. It is a standard, open system designed to deploy and automate faster in concert with a hybrid-cloud environment.

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. The I/O connectivity modules of the solution are the Cisco UCS X-Series Direct Fabric Interconnect Modules, a unified fabric for Ethernet and Fibre Channel. Additionally, the UCS X9508 chassis can have expanded GPU capabilities using the Cisco UCS X-Fabric technology which interconnects X-series compute and PCIe nodes using high-speed PCIe technology.

For more information see Cisco UCS X-Series Direct Data Sheet.

Cisco UCSX-9508 Chassis

The Cisco UCS X9508 Server Chassis and its components are part of the Cisco Unified Computing System (UCS). This system can use multiple server chassis configurations along with the Cisco UCS Fabric Interconnects to provide advanced options and capabilities in server and data management. The following configuration options are supported:

  • All Cisco UCS compute nodes. In a compute node-only configuration, two Intelligent Fabric Modules (IFMs) are required.

  • A mix of Cisco UCS compute nodes and Cisco UCS PCI Nodes. In this configuration, the compute nodes are paired 1:1 with Cisco UCS PCIe nodes, such as the Cisco UCS X440p PCIe Node. Two Intelligent Fabric Modules (IFMs) and two Cisco X9416 X-Fabric Modules (XFMs) are required.

The Cisco UCS X9508 Series server chassis is a scalable and flexible chassis for today’s and tomorrow’s data center that helps reduce total cost of ownership.

The chassis is seven rack units (7 RU) high and can mount in an industry-standard 19-inch rack with square holes for use with cage nuts or round-holes for use with spring nuts. The chassis can house up to eight Cisco UCS nodes.

Up to six hot-swappable AC power supplies are accessible from the front of the chassis. These power supplies can be configured to support nonredundant, N+1 redundant, N+2 redundant, and grid-redundant configurations. The rear of the chassis contains four hot-swappable fans, six power connectors (one per power supply), two horizontal top slots for Intelligent Fabric Modules (IFM1, IFM2), and two additional horizontal bottom slots for X-Fabric modules (XFM1, XFM2).

Cisco UCS X215c M8 Compute Node

The Cisco UCS X-Series Modular System simplifies your data center, adapting to the unpredictable needs of modern applications while also providing for traditional scale-out and enterprise workloads. It reduces the number of server types to maintain, helping to improve operational efficiency and agility as it helps reduce complexity. Powered by the Cisco Intersight™ cloud operations platform, it shifts your thinking from administrative details to business outcomes with hybrid cloud infrastructure that is assembled from the cloud, shaped to your workloads, and continuously optimized.

The Cisco UCS X215c M8 Compute Node is integrate into the Cisco UCS X-Series Modular System. Up to eight compute nodes can reside in the 7-Rack-Unit (7RU) Cisco UCS X9508 Chassis, offering one of the highest densities of compute, IO, and storage per rack unit in the industry.

The Cisco UCS X215c M8 Compute Node offers the following:

  • CPU: Up to 2x 4th Generation AMD EPYC Processors with up to 128 cores per processors

  • Memory:

    • 24 DIMM slots (12 DIMMs per CPU socket), up to 4800 MT/s DDR5.

    • Up to 6 TB of capacity.

  • Storage: Up to 6 hot-pluggable, Solid-State Drives (SSDs), or Non-Volatile Memory Express (NVMe) 2.5-inch drives with a choice of enterprise-class Redundant Array of Independent Disks (RAID) or pass-through controllers with four lanes each of PCIe Gen 4 connectivity and up to 2 M.2 SATA or NVMe drives for flexible boot and local storage capabilities.

  • Optional Front Mezzanine GPU module: The Cisco UCS Front Mezzanine GPU module is a passive PCIe Gen 4 front mezzanine option with support for up to two U.2 or U.3 NVMe drives and two HHHL GPUs.

  • mLOM virtual interface cards:

    • Cisco UCS Virtual Interface Card (VIC) 15420 occupies the server's Modular LAN on Motherboard (mLOM) slot, enabling up to 50Gbps (2 x25Gbps) of unified fabric connectivity to each of the chassis Intelligent Fabric Modules (IFMs) for 100Gbps connectivity per server.

    • Cisco UCS Virtual Interface Card (VIC) 15230 occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 100 Gbps of unified fabric connectivity to each of the chassis Intelligent Fabric Modules (IFMs) for 100 Gbps connectivity per server with secure boot capability.

  • Optional Mezzanine card:

    • Cisco UCS Virtual Interface Card (VIC) 15422 can occupy the server's mezzanine slot at the bottom rear of the chassis. An included bridge card extends this VIC's 100Gbps (4 x 25Gbps) of network connections through IFM connectors, bringing the total bandwidth to 100Gbps per VIC 15420 and 15422 (for a total of 200Gbps per server). In addition to IFM connectivity, the VIC 15422 I/O connectors link to Cisco UCS X-Fabric technology.

    • Cisco UCS PCI Mezz card for X-Fabric can occupy the server's mezzanine slot at the bottom rear of the chassis. This card's I/O connectors link to Cisco UCS X-Fabric modules and enable connectivity to the X440p PCIe Node.

  • Security: Includes secure boot silicon root of trust FPGA, ACT2 anti-counterfeit provisions, and optional Trusted Platform Model (TPM).

For complete list of supported peripherals for Cisco UCS X215c M8 Compute Node, see Cisco UCS X215c M8 Compute Node Spec Sheet.


Note

Cisco UCS X215c M8 Compute Node supports only 15000 Series secure boot VIC adapters.

The Cisco UCS X410c M7 Compute Node is the first 4-socket 4th Gen Intel® Xeon® Scalable Processors computing device to integrate into the Cisco UCS X-Series Modular System. Up to four compute nodes or two compute nodes and two GPU nodes can reside in the 7-rack-unit (7RU) Cisco UCS X9508 Server Chassis, offering high performance and efficiency gains for a wide range of mission-critical enterprise applications, memory-intensive applications and bare-metal and virtualized workloads.

The Cisco UCS X410c M7 Compute Node provides these main features:

  • CPU: Four 4th Gen Intel Xeon Scalable Processors with up to 60 cores per processor

  • Memory: Up to 16TB of main memory with 64x 256 GB DDR5-4800 Memory DIMMs

  • Storage: Up to six hot-pluggable solid-state drives (SSDs), or non-volatile memory express (NVMe) 2.5-inch drives with a choice of enterprise-class RAID or passthrough controllers, up to two M.2 SATA drives with optional hardware RAID

  • mLOM virtual interface cards:

    • Cisco UCS VIC 15420 occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 50 Gbps of unified fabric connectivity to each of the chassis’s intelligent fabric modules (IFMs) for 100 Gbps connectivity per server.

    • Cisco UCS VIC 15231 occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 100 Gbps of unified fabric connectivity to each of the chassis’s intelligent fabric modules (IFMs) for 100 Gbps connectivity per server.

    • Cisco UCS VIC 15230 (with secure boot feature) occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 100 Gbps of unified fabric connectivity to each of the chassis’s intelligent fabric modules (IFMs) for 100 Gbps connectivity per server.

  • Optional mezzanine card:

    • Cisco UCS 5th Gen VIC 15422 can occupy the server's mezzanine slot at the bottom rear of the chassis. This card's I/O connectors link to Cisco UCS X-Fabric technology. An included bridge card extends this VIC's 2x 50 Gbps of network connections through IFM connectors, bringing the total bandwidth to 100 Gbps per fabric (for a total of 200 Gbps per server).

    • Cisco UCS PCI Mezz card for Cisco UCS X-Fabric can occupy the server's mezzanine slot at the bottom rear of the chassis. This card's I/O connectors link to Cisco UCS X-Fabric modules and enable connectivity to the Cisco UCS X440p PCIe Node.

    • All VIC mezzanine cards also provide I/O connections from the X410c M7 compute node to the X440p PCIe node.

  • Security: The server supports an optional trusted platform module (TPM). Additional features include a secure boot FPGA and ACT2 anti-counterfeit provisions.

Cisco UCS X210c M7 Compute Node

The Cisco UCS X210c M7 Compute Node is the second generation of compute node to integrate into the Cisco UCS X-Series Modular System. It delivers performance, flexibility, and optimization for deployments in data centers, in the cloud, and at remote sites. This enterprise-class server offers market-leading performance, versatility, and density without compromise for workloads. Up to eight compute nodes can reside in the 7-rack-unit (7RU) Cisco UCS X210c M7 Compute Node, offering one of the highest densities of compute, I/O, and storage per rack unit in the industry.

The Cisco UCS X210c M7 Compute Node provides these main features:

  • CPU: Up to 2x 4th Gen Intel® Xeon® Scalable Processors with up to 60 cores per processor and up to 2.625 MB Level 3 cache per core and up to 112.5 MB per CPU.

  • Memory: Up to 8TB of main memory with 32x 256 GB DDR5-4800 DIMMs.

  • Storage: Up to six hot-pluggable, solid-state drives (SSDs), or non-volatile memory express (NVMe) 2.5-inch drives with a choice of enterprise-class redundant array of independent disks (RAIDs) or passthrough controllers, up to two M.2 SATA and M.2 NVMe drives with optional hardware RAID.

  • Optional front mezzanine GPU module: The Cisco UCS front mezzanine GPU module is a passive PCIe Gen 4.0 front mezzanine option with support for up to two U.2 NVMe drives and two HHHL GPUs.

  • mLOM virtual interface cards:

    • Cisco UCS Virtual Interface Card (VIC) 15420 occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 50 Gbps of unified fabric connectivity to each of the chassis intelligent fabric modules (IFMs) for 100 Gbps connectivity per server.

    • ◦ Cisco UCS Virtual Interface Card (VIC) 15231 occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 100 Gbps of unified fabric connectivity to each of the chassis intelligent fabric modules (IFMs) for 100 Gbps connectivity per server.

  • Optional mezzanine card:

    • Cisco UCS 5th Gen Virtual Interface Card (VIC) 15422 can occupy the server's mezzanine slot at the bottom rear of the chassis. This card's I/O connectors link to Cisco UCS X-Fabric technology. An included bridge card extends this VIC's 2x 50 Gbps of network connections through IFM connectors, bringing the total bandwidth to 100 Gbps per fabric (for a total of 200 Gbps per server).

    • Cisco UCS PCI Mezz card for X-Fabric can occupy the server's mezzanine slot at the bottom rear of the chassis. This card's I/O connectors link to Cisco UCS X-Fabric modules and enable connectivity to the Cisco UCS X440p PCIe Node.

    • All VIC mezzanine cards also provide I/O connections from the X210c M7 compute node to the X440p PCIe Node.

  • Security: The server supports an optional trusted platform module (TPM). Additional features include a secure boot FPGA and ACT2 anti-counterfeit provisions.

Cisco UCS X210c M6 Compute Node

The Cisco UCS X210c M6 Compute Node is the first computing device to integrate into the Cisco UCS X-Series Modular System. Up to eight compute nodes can reside in the 7-Rack-Unit (7RU) Cisco UCS X9508 Chassis, offering one of the highest densities of compute, I/O, and storage per rack unit in the industry.

The Cisco UCS X210c M6 Compute Node provides these main features:

  • CPU: Up to 2x 3rd Gen Intel® Xeon® Scalable Processors with up to 40 cores per processor and 1.5 MB Level 3 cache per core

  • Memory: Up to 32x 256 GB DDR4-3200 DIMMs for up to 8 TB of main memory. Configuring up to 16x 512-GB Intel Optane™ persistent memory DIMMs can yield up to 12 TB of memory.

  • Storage: Up to 6 hot-pluggable, solid-state drives (SSDs), or non-volatile memory express (NVMe) 2.5-inch drives with a choice of enterprise-class redundant array of independent disks (RAIDs) or pass-through controllers with four lanes each of PCIe Gen 4 connectivity and up to 2 M.2 SATA drives for flexible boot and local storage capabilities

  • Optional front mezzanine GPU module: The Cisco UCS Front Mezzanine GPU module is a passive PCIe Gen 4 front mezzanine option with support for up to two U.2 NVMe drives and two GPUs.

  • mLOM virtual interface cards:

    • Cisco UCS Virtual Interface Card (VIC) 14425 occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 50 Gbps of unified fabric connectivity to each of the chassis intelligent fabric modules (IFMs) for 100 Gbps connectivity per server.

    • Cisco UCS VIC 15231 occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 100 Gbps of unified fabric connectivity to each of the chassis intelligent fabric modules (IFMs) for 100 Gbps connectivity per server.

    • Cisco UCS VIC 15420 occupies the server's modular LAN on motherboard (mLOM) slot, enabling up to 100 Gbps of unified fabric connectivity to each of the chassis intelligent fabric modules (IFMs) for 100 Gbps connectivity per server.

  • Optional mezzanine card:

    • Cisco UCS VIC 14825 can occupy the server's mezzanine slot at the bottom rear of the chassis. This card's I/O connectors link to Cisco UCS X-Fabric technology. An included bridge card extends this VIC's 2x 50 Gbps of network connections through IFM connectors, bringing the total bandwidth to 100 Gbps per fabric (for a total of 200 Gbps per server).

    • Cisco UCS VIC 15422 X-Series mezz (UCSX-ME-V5Q50G) 4x25G can occupy the server's mezzanine slot at the bottom rear of the chassis. This card's I/O connectors link to Cisco UCS X-Fabric technology. An included bridge card extends this VIC's 2x 50 Gbps of network connections through IFM connectors, bringing the total bandwidth to 100 Gbps per fabric (for a total of 200 Gbps per server).

    • Cisco UCS PCI Mezz card for X-Fabric can occupy the server's mezzanine slot at the bottom rear of the chassis. This card's I/O connectors link to Cisco UCS X-Fabric modules and enable connectivity to the X440p PCIe Node.

  • Security: The server supports an optional trusted platform module (TPM). Additional features include a secure boot FPGA and ACT2 anti-counterfeit provisions

Intelligent Fabric Module (IFM)

The Intelligent Fabric Modules (IFMs) bring the unified fabric into the blade server enclosure, providing connectivity between the blade servers and the fabric interconnect, simplifying diagnostics, cabling, and management. Cisco UCS X-Series Servers support following IFMs:

  • Cisco UCS 9108 25G IFMs (UCSX-I-9108-25G)—supports aggregate data throughput of 2TB/s through two groups of four optical ports.

  • Cisco UCS 9108 100G IFMs (UCSX-I-9108-100G)—supports data throughput of 100G through two groups of 4 ports.

X-Fabric Module (XFM)

XFMs—Displays a summary of the X-Fabric Modules (XFM) in the chassis. Click a specific XFM to view the details of the fan modules. When you click a fan module, you can view the ID, model, and operational state of the fans.


Note

The XFM (UCSX-F-9416) slots are to be present in the respective two slots of UCSX 9508 Chassis.

The module is a configuration option:

  • The X-Fabric modules are required when the server chassis contains the Cisco UCS X440p PCIe node

  • The X-Fabric module is not required if your server chassis contains only Cisco UCS X-Series compute nodes, such as the Cisco UCS X210c.

For more information on X-Fabric Module (XFM) Fan Status, see Viewing X-Fabric Module (XFM) Fan Status.

Overview of Cisco UCS Fabric Interconnects 9108 100G (Cisco UCS X-Series Direct)

The Cisco UCS X-Series Direct is identified by the product ID UCSX-S9108-100G, and the product description Cisco UCS Fabric Interconnects 9108 100G.

Components of Cisco UCS Fabric Interconnects 9108 100G:

  • Two Cisco UCS X9508 Chassis

  • A pair of Cisco UCS Fabric Interconnects 9108 100G

  • 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

  • One or more of Cisco UCS X-Series M6, M7, and M8 Compute Nodes

  • Optional components:

    • Cisco UCS 9416 X-Fabric Modules

    • Cisco UCS X440p PCIe Node with up to four GPUs used in conjunction with the 9416 X-Fabric Modules

The Cisco UCS Fabric Interconnects 9108 100G platform streamlines data center architecture by eliminating the need for separate Fabric Interconnects (FIs), integrating essential networking and management functionality directly within the chassis. The Cisco UCS Fabric Interconnects 9108 100G platform is designed for deployments in smaller settings, where the compute server requirements are less extensive than those of a traditional data center. This solution is centered around a single-chassis system, the Cisco UCS X9508 Chassis, which incorporates Cisco UCS Fabric Interconnects 9108 100G directly into the chassis for a consolidated and efficient infrastructure. To ensure high availability, each chassis houses two Cisco UCS Fabric Interconnects 9108 100G that establish direct downlink connections to servers and provide uplink connections to facilitate seamless integration with both Local Area Network (LAN) and Storage Area Network (SAN) systems. The Fabric Interconnects (FIs) are adeptly designed to fit into the Cisco UCS X-Series chassis, presenting as a single module within the NX-OS environment that merges QSFP ports with server backplane ports.

The hardware configuration of the Cisco UCS Fabric Interconnects 9108 100G platform retains the same form factor as the standard Cisco UCS X-Series chassis, and features 17 MACs, each configurable for 10 Gbps, 25 Gbps, 40 Gbps, or 100 Gbps connectivity. It is equipped with an CPU, for operating NX-OS, Cisco UCS Manager for management and Chassis Management Controller (CMC) software. The Cisco UCS Fabric Interconnects 9108 100G includes an onboard Ethernet switch with multiple 10G links dedicated to out-of-band communication between blade components such as the Baseboard Management Controller (BMC), CMC. A dedicated 1G link facilitates IFM-to-IFM clustering and high availability synchronization. Within the Cisco UCS Fabric Interconnects 9108 100G, Ethernet ports 1-8, backplane ports 9-16, and the Baseboard Interface (BIF) port 17 coexist on a singular switch card. Ports 1-2 are unified to manage all SAN features and configurations. The 100G Ethernet ports [1-8] can also be configured as 25Gx4 SFP28 compatible breakout ports or 4x10G ports, offering flexible networking solutions to accommodate a range of data center needs.

Cisco UCS Fabric Interconnects 9108 100G (Cisco UCS X-Series Direct) Architecture

The Cisco UCS X-Series Direct architecture is engineered to support a diverse range of workloads, from traditional applications to cloud-native services, by offering a composable and disaggregated approach to computing resources. Key components of the Cisco UCS X-Series Direct architecture include:

  • Cisco UCSX-9508 Chassis—A modular and future-proof chassis that can accommodate various types of compute nodes, providing the flexibility to adapt to different workload requirements without the need for a complete hardware overhaul.

    Cisco UCS X-Series Direct supports the addition of a secondary Cisco UCS X9508 Chassis, enabling scalability of up to 20 servers. This includes both Cisco UCS C-Series servers and Cisco UCS X-Series Compute Nodes, providing flexible expansion options for diverse workloads.

  • Cisco UCS Fabric Interconnects 9108 100G—This solution is centered around a single-chassis system, the Cisco UCS X9508 Chassis, which incorporates Cisco UCS Fabric Interconnects 9108 100G directly into the chassis for a consolidated and efficient infrastructure. To ensure high availability, each chassis houses two Cisco UCS Fabric Interconnects 9108 100G that establish direct downlink connections to servers and provide uplink connections to facilitate seamless integration with both Local Area Network (LAN) and Storage Area Network (SAN) systems.

  • Software Architecture—In terms of the startup and operational model, the management, Cisco UCS Manager aligns with the approach taken in the Cisco UCS 6500 and 6400 Series Fabric Interconnects. In this model, Cisco UCS Manager is encapsulated within a container and is initiated by the underlying NX-OS, depending on the selected management mode.

Cisco UCS Fabric Interconnects

Cisco UCS 6600 Series Fabric Interconnects

Overview of Cisco UCS 6664 Fabric Interconnect

The Cisco UCS 6664 Fabric Interconnect is a 2-rack unit (RU), fixed-port system designed for Top-of-Rack deployment in data centers. The fabric interconnect has both Ethernet and unified ports. Unified ports provide Fibre Channel over Ethernet (FCoE), Fibre Channel, NVMe over Fabric, and Ethernet. By supporting these different protocols, you can use a single multi-protocol Virtual Interface Card (VIC) in your servers.

The UCS 6664 Fabric Interconnect supports an array of Gigabit Ethernet (GbE), Fibre Channel (FC), and Fibre Channel over Ethernet (FCoE) ports to offer connectivity to peer data center devices. This device is also ideal for high-performance, scalable, and secure networking in modern data centers.

The Cisco UCS 6664 Fabric Interconnect includes:

  • 64 total ports

    • 48 ports of 40/100 Gbps

    • 16 unified ports

      • Supports 10/25 Gbps for Ethernet and Fibre Channel over Ethernet (FCoE)

      • Supports 10/25 Gbps or 16/32/64 Gbps Fibre Channel for maximum flexibility

  • 2RU fixed form factor for dense 100 Gbps connectivity

  • Fibre Channel end-host and switch-mode support

Cisco UCS 6664 Fabric Interconnect Architecture

The Cisco UCS 6664 Fabric Interconnect is a high-density, line-rate, low-latency 100 Gbps solution specifically designed for the Cisco UCS X-Series Modular System and Cisco UCS C-Series Rack servers. It serves as a foundational component within Cisco UCS, unifying computing, networking, management, storage access, and virtualization resources into a single, cohesive system. This integrated approach is engineered to significantly reduce the Total Cost of Ownership (TCO) for data center deployments.

Architecture:

  • Front Panel: Houses all the network ports and system status lights (LEDs). These ports are highly flexible, supporting various connection types like Ethernet, Fibre Channel, and Fibre Channel over Ethernet (FCoE) through "Unified Ports."

  • Rear Panel: Contains the management connections (for setup and control), and the power supplies and fan modules.

  • Redundancy and Reliability: The design includes redundant power supplies and multiple fan modules to ensure continuous operation and efficient cooling.

This design allows the fabric interconnect to serve as a central hub, connecting servers to both the local network and external storage systems.

Key Features and Capabilities

  • Unified Fabric:The Cisco UCS 6664 Fabric Interconnect features 64 ports, including 48 QSFP ports (10/25 Gbps with Ethernet/FCoE support) and 16 Unified SFP ports (10/25 Gbps or 16/32/64 Gbps Fibre Channel). Ports 49-64 are optimized for secure uplinks with Media Access Control Security (MACsec).

  • Server Connectivity:

    • For Cisco UCS C-Series Rack Servers, direct connection to the 6664 Fabric Interconnect is supported. Alternatively, the Cisco Nexus 93180YC-FX3 switch can be deployed as a Fabric Extender (FEX) to provide the benefits of networking cabling consolidation for rack servers, similar to a modular server system.

    • For Cisco UCS X-Series Modular Systems, network cable consolidation is achieved through Intelligent Fabric Modules (IFMs). These IFMs are available in both 25 Gbps and 100 Gbps form factors, facilitating up to 200 Gbps of aggregate bandwidth per compute node.


Note

Port breakout functionality is not available on Cisco UCS 6664 Fabric Interconnects.

Port Functionality on Cisco UCS 6664 Fabric Interconnect

The Cisco UCS 6664 Fabric Interconnect is a 2-rack unit (RU) fixed-port system designed for flexible and high-performance networking. It features 64 front panel ports that support a variety of connectivity options.

Front Panel Port Configuration and Types

The UCS 6664 Fabric Interconnect supports the following possible configurations or port types for each front panel port:

Port Number Port Hardware Admin Port Speed Port Type Port Role
1-24 QSFP 28 40 Gbps/100 Gbps

Gigabit Ethernet

  • Server Port

  • Ethernet/FCoE Uplink Port

  • FCoE Storage Port

  • Appliance Port (EHM only)

  • Monitor Port
25-40 (Unified Ports) SFP28 16 Gbps/32 Gbps/64 Gbps Fibre Channel (FC)

  • FC Uplink Port

  • FC Storage Port
10 Gbps/25 Gbps Gigabit Ethernet

  • Server Port

  • Ethernet/FcoE Uplink Port

  • Appliance Port (EHM only)

  • Monitor Port

41-64

Note: Ports 49–64 are MAC Security (MACsec)-capable

QSFP 28 40 Gbps/100 Gbps Gigabit Ethernet

  • Server Port

  • Ethernet/FCoE Uplink Port

  • FCoE Storage Port

  • Appliance Port (EHM only)

  • Monitor Port

Note

Breakout port functionality is not supported on Cisco UCS 6600 Series Fabric Interconnects.

Replacing a Server

If you plan to replace a server registered in a Cisco UCS Domain, use the following instructions to prepare for the replacement:

  1. Disassociate any service profiles associated with the server from Cisco UCS Central.

  2. Decommission the server from Cisco UCS Central. If a motherboard replacement is required, delete the server from any of the associated pools and refresh inventory.

  3. Perform the necessary maintenance actions and reacknowledge the server from Cisco UCS Central.

  4. After the server is discovered, add it back to the server-pools as required.

  5. Refresh the inventory if required, and reassociate the service profiles from Cisco UCS Central.

Unified KVM Launcher

The Unified KVM Launcher page allows you to connect to any server in the Cisco UCS domain, whether or not they are associated with a service profile.

Beginning with Release 1.4, you can create users with the KVM privilege, or use the new KVM role that only has the KVM privilege. When users that only have the KVM privilege log into the Cisco UCS Central HTML5 UI, they will only be able to view the unified KVM launcher page.

Using the Unified KVM Launcher

Procedure

Step 1

On the menu bar, click the Alerts icon.

Step 2

Select Unified KVM Launcher.

Step 3

On the Unified KVM Launcher page, select the server that you want to connect to.

Use the checkboxes in the Filters area to narrow down the selections.

Step 4

Click Launch KVM.

Inband Policy

Cisco UCS Central lets you configure the Inband IP address on a server directly, or through an Inband Policy. This feature is supported on Cisco UCS Manager release 4.1 (3) and later. After you create an Inband policy, you can assign it to a domain group from Domain Configuration Settings in Domains Main View. The Inband Policy view displays details about the corresponding VLAN Group, the Default Management VLAN, and the Management IP pool associated with the policy.

Create Inband Policy

Procedure

Step 1

In the Actions bar, type Create Inband Policy and press Enter.

Step 2

In the Create Inband Policy dialog box, choose the Domain Group Location in which you want to create the policy and enter the Name and optional Description.

The name is case sensitive.

Step 3

In VLAN Group, select the VLAN group from the VLAN Group drop-down list, and the VLAN ID from the Default Management VLAN drop-down list to associate with this policy.

Step 4

In IP Pool, select Management IP Pool from the drop-down list to associate it with this policy.

Step 5

Click Create.

Step 6

(Optional) You can favorite this policy and pin it to the Cisco UCS Central dashboard to navigate to it directly.

After you create an Inband policy, you can assign it to a domain group from the Domain Configuration Settings in Domains Main View.

Step 7

In the Domain Configuration Settings window, click Inband Policy in the Management IP tab, and select the policy you want to assign to the domain group.

About KVM Outband Configuration

Beginning Cisco UCS Central, you can create a KVM Outband IP pool on Cisco UCS Central and assign it to a domain directly. With a KVM Outband IP pool, you can automatically push down the IP addresses to available blade and rack servers by assigning them to a Cisco UCS domain through Domain Configuration Settings. The physical KVM Outband settings are independent from the KVM Outband configuration associated with a service profile. This feature is supported on Cisco UCS Manager 4.1(3) and later.

KVM Outband IP pools have the following features:

  • An Outband pool pushed down to Cisco UCS Manager can override any local configuration on Cisco UCS Manager. However, a Cisco UCS Manager user can edit the Outband KVM configuration locally, and the option to edit the IP pool is not grayed out on the Cisco UCS Manager GUI.

  • When an Outband configuration is altered locally on Cisco UCS Manager, the IP addresses associated with the pool are released and are available for other associations.

  • If you are non-admin Cisco UCS Central user, you require Domain-Group-Management privileges to create, read, update, or delete a KVM Outband configuration.

  • When you modify a Management IP pool to add, remove, or update a block, use the Reapply Configuration option from the Domains Main View. This option ensures that the pool is refreshed with the modified IP addresses before it is pushed down to Cisco UCS Manager. However, if you unassign a pool or switch the Management IP pools, you do not have to reapply the configuration settings.


    Note

    A warning message displays when you use the Reapply Configuration option. When you accept the option to reapply the configuration, Cisco UCS Central reapplies the configuration of only the Management IP addresses.

  • You can verify the assigned physical KVM Outband IP pool when you Launch KVM from the Server Details page. The drop-down menu on the KVM Console Launch displays the physical KVM Outband and the IPv4 Outband associated with a service profile.


    Note

    IPv6 is not supported for KVM Outband.

  • You can access the CIMC through an Outband or Inband address. In the case of an Outband address, traffic traverses the fabric interconnect (FI) via the management port to the network. Traffic to and from an Inband address traverses through the FI via the fabric uplink port.

  • In Cisco UCS Central, KVM Outband support is managed through an IP pool and not with a static IP.

Equipment Policies

Equipment policies allow you to tune your servers and other equipment to suit your requirements. Equipment policies can only be set at the domain group level, and apply to all servers in that domain group.


Note

Equipment policies are not included in service profiles.

Managing Equipment Policies

Procedure

Step 1

Click the Domain Group Navigation icon and choose a domain group.

Step 2

Click the Configuration icon and choose System Policies.

Step 3

In Equipment, click Basic and complete the following fields:

  1. In Rack Management Action, select how server management is configured when a new rack server is discovered:

    • Auto Acknowledged—Cisco UCS automatically configures server management by domain based on the available server connections.

    • User Acknowledged—Cisco UCS does not automatically configure server management. It waits until acknowledged by the user.

  2. In MAC Address Table Aging Time, select the length of time an idle MAC address remains in the MAC address table before it is removed:

    • Mode Default—System uses the default value. For end-host mode, the default is 14,500 seconds. For switching mode, the default is 300 seconds.

    • Never—Cisco UCS never removes MAC addresses from the table.

    • Other—Enter a custom value in the dd:hh:mm:ss field.

  3. In VLAN Port Count Optimization, select whether Cisco UCS can logically group VLANs to optimize the use of ports and reduce the CPU load on the FI.

  4. In Firmware Auto Server Sync State, select the firmware synchronization policy for recently discovered blade servers or rack servers:

    • User Acknowledged—Cisco UCS does not synchronize firmware until the administrator acknowledges the upgrade.

    • No Actions—Cisco UCS does not perform any firmware upgrade on the server.

  5. In Info Action, select whether the information policy displays the uplink switches that are connected to the Cisco UCS domain.

Step 4

Click Discovery and complete the fields to specify how you want the system to behave when you add a new chassis or FEX:

  1. In Chassis/FEX Link Action, select the minimum threshold for the number of links between the chassis or FEX and the fabric interconnect.

  2. In Chassis/FEX Link Grouping Preference, select whether the links from the system IO controllers, IOMs, or FEXes to the fabric interconnects are grouped in a port channel.

  3. In the Multicast Hardware Hash, click Enable to specify if Cisco UCS can use all of the links from the IOMs or FEXes to the fabric interconnects for multicast traffic.

  4. In the Backplane Speed Preference, choose the speed that you want to use.

Step 5

Click Power and complete the following fields:

  1. In Power Redundancy, select the power redundancy policy that you want to use:

    • N+1—The total number of power supplies, plus one additional power supply for redundancy, equally share the power load for the chassis. If any additional power supplies are installed, Cisco UCS sets them to a "turned-off" state.

    • Grid—Two power sources are turned on, or the chassis requires greater than N+1 redundancy. If one source fails, the surviving power supplies continue to provide power to the chassis.

    • Non-Redundant—All installed power supplies are turned on and the load is evenly balanced. Only power small configurations (requiring less than 2500W) by a single power supply.

    • N+2—The total number of PSUs to satisfy non-redundancy, plus two additional PSU for redundancy, are turned on and equally share the power load for the chassis. If any additional PSUs are installed, Cisco UCS Central sets them to a "turned-off" state only when the Power Save mode is enabled. If the power to any PSU is disrupted, Cisco UCS Central can recover without an interruption in service.

      After consideration of redundancy, the effective number of PSUs are atleast two. For example, for N it is two PSUs, N+1 it is three PSUs, and for N+2 and Grid it is four PSUs.

      Note

       
      N+2 redundancy mode is supported only for Cisco UCSX-9508 Chassis. For all other chassis, Cisco UCS Central treats N+2 mode as N+1 mode only.

  2. In Power Allocation, select the power allocation management mode used in the Cisco UCS domain:

    • Policy Driven Chassis Group Cap—Configures power allocation at the chassis level through power control policies included in the associated service profiles.

    • Manual Blade Level Cap—Configures power allocation on each individual blade server in all chassis.

    Specifies how the power cap values of the servers are calculated. If it is enabled, the servers will be profiled during discovery through benchmarking. This policy applies when the Global Power Allocation Policy is set to Policy Driven Chassis Group Cap.

  3. In Power Profiling Policy, select the power profiling policy. You can set the Power Profiling Policy to one of the following:

    • Disabled—The minimum and maximum power cap values of the blades are calculated based on the static power consumption values of each of the components.

    • Enabled—The minimum and maximum power cap values of the blades are measured as part of the server discovery. These values are similar to the actual power consumption of the blades.

      Note

       

      After enabling the Power Profiling Policy, you must re-acknowledge the blades to obtain the minimum and maximum power cap.

  4. Power Save Policy—Globally manages the chassis to maximize energy efficiency or availability.

  5. Cisco UCSX-9508 Chassis Power Extended Policy—Manages the chassis to maximize energy efficiency or availability.

    Power Extended Policy is effective only when we have PSU Redundant Policy Mode. For example, the total power available can be extended when we have N+1, N+2 and Grid to PSU Redundancy modes.

  6. Cisco UCSX-9508 Chassis Fan Control Policy—Manages you to control the fan speed to bring down server power consumption and noise levels.

  7. In ID Soaking Interval, specify the number of seconds Cisco UCS Central waits before reassigning a pool entity that Cisco UCS released. Enter an integer between 0 and 86400.

Step 6

Click Save.

Managing Rack Discovery Policies

Procedure

Step 1

Click the Domain Group Navigation icon and choose a domain group.

Step 2

Click the Configuration icon and choose System Policies.

Step 3

In Rack Discovery, click Enabled.

Step 4

In Basic, for Discovery Policy Action, select how you want the system to behave when you add a new rack server.

  • Immediate—Cisco UCS domain attempts to discover new servers automatically.

  • User Acknowledged—Cisco UCS domain waits until the user tells it to search for new servers.

Step 5

Click Policies and select the scrub policy that you want to run on a newly discovered server.

The server must meet the criteria in the selected server pool policy qualification.

Step 6

Click Save.

Power Management in Cisco UCS Central

Power Capping in Cisco UCS Central

You can control the maximum power consumption on a server through power capping, as well as manage the power allocation in the Cisco UCS Manager for blade servers, rack servers, UCS Mini, and mixed UCS domains.

Cisco UCS Central supports power capping on the following:

  • Cisco UCS Fabric Interconnects 9108 100G (Cisco UCS X-Series Direct)


    Note

    Cisco UCSX-9508 Chassis supports Policy Driven Chassis Group Cap.

    When you choose to select Policy Driven Chassis Group Cap, Cisco UCS Manager calculates the power allotment for Cisco UCSX-9508 Chassis and when you choose to select Manual Blade Level Power Cap, Chassis Management Controller (CMC) calculates the power allotment for Cisco UCSX-9508 Chassis.

Cisco UCS Manager provides the following power management policies to help you allocate power to your servers:

Power Management Policies

Description

Power Profiling Policy

Enables or disables the power profiling of the system

Note

 

This property is supported only on Cisco UCS X-Series servers.

Power Sync Policy

Addresses power synchronization issues between the associated service profiles and the servers.

Power Control Policy

Specifies the priority to calculate the initial power allocation for each blade in a chassis.

Power Save Policy

Globally manages the chassis to maximize energy efficiency or availability.

Cisco UCSX-9508 Chassis Power Extended Policy

Manages the chassis to maximize energy efficiency or availability.

Power Extended Policy is effective only when we have PSU Redundant Policy Mode. For example, the total power available can be extended when we have N+1, N+2 and Grid to PSU Redundancy modes.

Cisco UCSX-9508 Chassis Fan Control Policy

 Manages you to control the fan speed to bring down server power consumption and noise levels.

Global Power Allocation

Specifies the Policy Driven Chassis Group Power Cap or the Manual Blade Level Power Cap to apply to all servers in a chassis.

Global Power Profiling

Specifies how the power cap values of the servers are calculated. If it is enabled, the servers will be profiled during discovery through benchmarking. This policy applies when the Global Power Allocation Policy is set to Policy Driven Chassis Group Cap.

Creating or Editing Power Sync Policy

Power Sync policy addresses power synchronization issues between the associated service profiles and the servers. You can use the Power Sync policy to synchronize the power state when the power state of the service profile differs from the actual power state of the server. The Power Sync policy applies to all the service profiles by default. You cannot delete the default Power Sync policy, but you can edit the default policy. You can create your own power sync policies and apply them to the service profiles. You can also create a Power Sync policy that is specific to a service profile and it always takes precedence over the default policy.

Procedure

Step 1

In the Actions bar, type Create Power Sync Policy and press Enter.

Step 2

In the Power Sync Policy dialog box, choose the Organization in which you want to create the policy.

Step 3

Enter the Name and optional Description.

The name is case sensitive.

Step 4

Choose the Sync Option.

This can be one of the following:

  • Default Sync—After the initial server association, any configuration change or management connectivity changes that you perform trigger a server reassociation. This option synchronizes the desired power state to the physical server if the physical server power state is off and the desired power state is on. This is the default behavior.

  • Always Sync—When the initial server association or the server reassociation occurs, this option always synchronize the desired power state to the physical power state even if the physical server power state is on and desired power state is off.

  • Initial Only Sync—This option only synchronizes the power to a server when a service profile is associated to the server for the first time or when the server is re-commissioned. When you set this option, resetting the power state from the physical server side does not affect the desired power state on the service profile.

Viewing Power Sync Policy

Procedure

Step 1

Click the Browse Tables icon and choose Policies.

Step 2

Click on the Power Sync check box to select it.

Step 3

On the Policies page, click on the Power Sync Policy you want to view the details for.

The Power Sync Policy view displays policy usage and the Power Sync options defined in the policy. The policy usage shows if the policy is associated with a service profile, the location of the policy, and power options defined in the policy.

Power Control Policy

You can create a Power Control policy in Cisco UCS Central and include it in the service profile to enable the system to manage the power allocation control for the blade servers in the registered Cisco UCS domains.

Cisco UCS uses the priority set in the Power Control policy, along with the blade type and configuration, to calculate the initial power allocation for each blade within a chassis.

During normal operation, the active blades within a chassis can borrow power from idle blades within the same chassis. If all blades are active and reach the power cap, service profiles with higher priority power control policies take precedence over service profiles with lower priority power control policies. Priority is ranked on a scale of 1-10, where 1 indicates the highest priority and 10 indicates lowest priority. The default priority is 5.

For mission-critical applications, a special priority called no-cap is also available. Setting the priority to no-cap prevents Cisco UCS from leveraging unused power from a particular server. With this setting, the server is allocated the maximum amount of power possible for that type of server.

Creating or Editing a Power Control Policy

Procedure

Step 1

In the Actions bar, type Create Power Control Policy and press Enter.

Step 2

In the Power ControlPolicy dialog box, choose the Organization in which you want to create the policy.

Step 3

Enter the Name and optional Description.

The name is case sensitive.

Step 4

Choose the Fan Speed.

This can be one of the following:

  • Low Power—The fan runs at the minimum speed required to keep the server cool.

  • Balanced—The fan runs faster when needed based on the heat generated by the server. When possible, the fan returns to the minium required speed.

  • Performance—The fan is kept at the speed needed for better server performance. This draws more power but means the fan is already at speed if the server begins to heat up.

  • High Power—The fan is kept at an even higher speed that emphasizes performance over power consumption.

  • Max Power—The fan is kept at the maximum speed at all times. This option provides the most cooling and uses the most power.

  • Any—The server determines the optimal fan speed.

Step 5

Choose whether to enable Power Capping.

Step 6

If Enabled, choose the Power Group Priority.

Priority is ranked on a scale of 1-10, where 1 indicates the highest priority and 10 indicates lowest priority. The default priority is 5.

Step 7

Click Create.

Power Save Policy

Power Save Mode is a configurable chassis policy that allows you to non-disruptively apply bias for either energy efficiency (when enabled) or availability (when disabled). By default, the Power Save Policy will be disabled. Disabling the Power Save Mode policy allows all PSUs present to remain active, regardless of the Power Redundancy setting. Enabling the Power Save Policy sets the PSUs to active as per the power redundancy policy.


Note

Today, when the requested power budget is less than the available power capacity, the additional PSU capacity is placed in Power Save Mode automatically. This increases the efficiency of active PSUs and minimizes energy wasted for conversion losses. However, there are a few use cases, where this default behavior can result in an outage:

  • Lightly loaded chassis that only requires 2X PSU to support the requested power policy (Grid) and the customer did NOT follow the installation guide recommendation regarding PSU input power connections. In this scenario, the chassis has both active PSUs connected to one feed, and the other two PSUs in Power Save mode connected to another feed. If the feed connected to the active PSUs is lost, the entire chassis will experience a service interruption.

  • A heavily loaded chassis that requires a 3X PSUs to support the requested power policy (N+1), and the customer's rack provides the chassis with dual feed. In this scenario, 3X PSUs are active and 1X PSU is placed in Power Save mode. If the feed connected to two of the active PSUs is lost (planned or unplanned), the customer could experience an outage if the load is greater than the remaining active PSU can support.

A Power Save mode policy can help avoid an outage situation.

The policy is global and is inherited by all chassis managed by the Cisco UCS Central.

Creating a Power Save Policy

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Click the Equipment node.

Step 3

In the Work pane, click the Policies tab.

Step 4

Click the Global Policies subtab.

Step 5

In the Power Save Policy area, check the Enable checkbox to enable the Global Power Control Policy.

Step 6

Click Save.

Fan Control Policy for Cisco UCSX-9508 Chassis

Fan Control Policy enables you to control the fan speed to bring down server power consumption and noise levels of Cisco UCSX-9508 Chassis. With the introduction of Fan Control policies, you can determine the right fan speed for the server, based on the components in the server.

Globally managing the fan speed can help in power management by applying a single policy for all B-series and X-series server fans in an enclosure, based on general cooling needs. For X-series servers, set the fan speed on a per-chassis basis in the Global Policies.

Fan Control policy options include:

  • Acoustic—The fan speed is reduced to reduce noise levels in acoustic-sensitive environments. Rather than regulating energy consumption and preventing component throttling as in other modes, the Acoustic option could result in short-term throttling to achieve a lowered noise level.

  • Balanced—The fan runs at a faster speed when needed, based on the heat generated by the server. When possible, the fan returns to the minimum required speed. This is the default option.

  • Low Power—The fan runs at the minimum speed that is required to keep the server cool.

  • High Power—The fan is kept at an even higher speed that emphasizes performance over power consumption.

  • Max Power—The fan is kept at the maximum speed at all times. This option provides the most cooling and uses the most power.

Creating a Cisco UCSX-9508 Chassis Power Extended Policy

Use this process to create a global Cisco UCSX-9508 Chassis Power Extended Policy.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

In the Work pane, click the Policies tab.

Step 3

In the Cisco UCSX-9508 Chassis Power Extedned Policy area, choose to enable or disable chassis power extended policy.

Chassis Extended Policy works only with non-redundant policy as the extended power is derived from redundant PSU

Step 4

Click Save.

Creating a Cisco UCSX-9508 Chassis Fan Control Policy

You can create a Fan Control Policy and define the right fan control setting based on the server configuration and server components.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

In the Work pane, click the Policies tab.

Step 3

In the Cisco UCSX-9508 Chassis Fan Control Policy area, choose the following options:

  • Balanced

  • Low Power

  • High Power

  • Max Power

  • Acoustic

Step 4

Click Save.

Viewing X-Fabric Module (XFM) Fan Status

This procedure is applicable only for Cisco UCS X9508 Server Chassis equipped with XFM.

Procedure

Step 1

In the Navigation pane, click Equipment.

Step 2

Expand Equipment > Chassis > Chassis Number > XFM Modules > XFM Module Number > Fans > Fan Module NumberEquipment > Chassis > Chassis Number > IO Modules.

Step 3

Choose the Fan number for which you want to view.

Step 4

In the Work pane, click the General tab.

The overall status for this fan appear. The fields in this tab are:

Column

Description

Name

A navigation tree that allows you to view a particular component and its subcomponents. You can right-click a component to view any actions available for that component.

Operability

A brief description of the operating state of the component.

If a fan is inoperable, it can be replaced with a new fan module. Contact Cisco technical support for more information.

Performance

A brief description of the performance state of the component.

Power

A brief description of the power state of the component.

Temperature

A description of the temperature state of the component.

Physical and Logical Inventory

Cisco UCS Central allows you to view all fabric interconnects, servers, chassis, and FEXes located in your Cisco UCS domains. You can also view individual components for each type of hardware, such as cartridges, fans, CPUs, IOMs, and ports.

You can also view the logical inventory details such as the server pools and ID pools in the registered UCS domains.

Fabric Interconnect

The Fabric Interconnect (FI) page displays the following information related to FIs associated with the registered Cisco UCS domain:

FI

Hardware

FW

Status

This column displays the following information for a fabric interconnect:

  • The associated domain name and FI ID

  • Domain group location

  • IP address of the domain

This column displays the following hardware information for a fabric interconnect:

  • The model number and type of FI

  • Serial number

  • The number of fixed and expansion module ports

  • The number of ethernet and fabric channel ports

This column displays the following firmware details for a fabric interconnect:

  • Firmware version

  • Firmware status

This column displays the following status for a fabric interconnect:

  • Overall status

  • Worst fault level

  • Locator LED status

Fabric Interconnect Main View

The Fabric Interconnect Main View page displays the following information related to the selected Fabric Interconnect (FI) and its components within a registered Cisco UCS domain.

  • Basic—Displays an overview of the FI within the domain, hardware details, firmware version, number of ports (Ethernet or FC) that are in use and available for use, management IP, and fault summary details.

  • Fixed Mod.—Displays overall status, firmware, hardware, properties, and fault summary details of the fixed modules installed in the FI .

  • Exp. Mod.—Displays overall status, firmware, hardware, properties, and fault summary details of the expansion modules installed in the FI.

  • Fans—Displays overall status, and hardware details of the fan.

  • PSUs—Displays overall status, fault summary, and hardware details of the PSU.

  • Ports—Displays ports, port role, and port status for all ports in the FI.

  • Port Channels—Displays all port channels in the FI and detailed information about each port channel.

  • Traffic Monitoring—Displays traffic monitoring sessions for the Ethernet or FC ports.

You can also perform the following tasks:

  • View configuration status.

  • Turn on or off the Locator LED.

  • Set the switching mode.

  • Manage unified port configuration.

  • Create port channels.

  • Create Traffic Monitoring.

  • Configure Evacuation.

    Note
    You can configure the evacuation state by selecting one of these Admin Evac Mode options:

    • Enabled - Stops the traffic on the IO module or the fabric interconnect

    • Disabled - Restarts traffic on the IO module or the fabric interconnect

    To evacuate a fabric interconnect regardless of its current evacuation state, you can select one of these Force Evac options:

    • Enabled - To evacuate the FI regardless of the current evacuation state

    • Disabled - Disables force evacuation of the FI regardless of the evacuation state


    Note

    For more information about Fabric Evacuation, see Fabric Evacuation and Configuring Fabric Evacuation.

  • Launch Cisco UCS Manager for the specific Cisco UCS domain.


    Note

    • Your browser must have pop-ups enabled.

    • For Cisco UCS Manager release 4.1(3) or later, this launches the HTML5 GUI. If the Cisco UCS Manager credentials match the credentials for your Cisco UCS Central login, then the system will automatically log in to the Cisco UCS Manager GUI without prompting for the login information.

Launch Cisco UCS Manager Fabric Interconnect Statistics

You can launch Cisco UCS Manager Fabric Interconnect (FI) statistics from the Tools menu in Cisco UCS Central to view these details for the FI:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager Fabric Interconnect PSU Statistics

You can launch Cisco UCS Manager PSU statistics for a Fabric Interconnect (FI) from the Tools menu in Cisco UCS Central to view these details:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager Port Statistics

You can launch Cisco UCS Manager Port statistics from the Tools menu in Cisco UCS Central to view these details:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Fabric Evacuation

Cisco UCS Central enables Fabric Evacuation, which is the ability to evacuate all traffic that flows through a fabric interconnect (FI) from all servers attached to it through an IOM or FEX while upgrading a system. Upgrading the secondary FI in a system disrupts active traffic on the FI. This traffic fails over to the primary FI. Using Fabric Evacuation, you can stop all traffic that is active through an FI. After verifying that the traffic failed over completely, and upgrading the secondary FI, you can restart all the stopped flows after rebooting the secondary FI and all the connected IOMs. In a cluster configuration, you can change the cluster lead to the subordinate FI, stop all the flows, and upgrade the other FI in the same manner.

Cisco UCS Central 2.1 supports Fabric Evacuation during Firmware AutoInstall to ensure that the appropriate failover settings are configured for the firmware upgrade. Fabric Evacuation is now automatically turned on during an FI upgrade and reboot during an AutoInstall. Fabric Evacuation is automatically configured when there is an activation prior to reboot on any of the FIs during an AutoInstall. Fabric Evacuation also forces an immediate failover of Fabric-Failover vNICs and ensures that there are no active vNICs in the target FI. This feature avoids the disruption when a primary FI goes down for a short duration for activation, and the secondary FI takes over through the heartbeat loss detection mechanism.

During an upgrade, Fabric Evacuation goes through the following steps:

  1. Stop all traffic that is active through an FI.

  2. Upgrade the secondary FI.

  3. Restart all stopped traffic flows.

  4. Change the cluster lead to the secondary FI.

  5. Repeat Steps 1 to 4 to upgrade the primary FI.


Note

Fabric Evacuation is supported:

  • At the FI level in Cisco UCS Manager release 2.2(4) and later.

  • In AutoInstall only in Cisco UCS Manager release 4.1(3).

  • Only on a subordinate FI.

  • In a cluster configuration.

Fabric Evacuation has the following limitations:

  • Evacuation on I/O modules is not supported.

  • Evacuation of directly-attached rack servers is not supported. Evacuation on the FI is enabled by manually bringing down the server ports when there are directly-connected rack servers. For an IOM/FEX, the HIF ports must be brought down to enable evacuation.

  • Downgrade from Cisco UCS Manager 2.2(4) to earlier releases places the FIs in the regular mode. However, server traffic flows through regardless of the configuration on the FI when you run the Cisco UCS Manager 2.2(4) image.

  • If you use AutoInstall with Fabric Evacuation to downgrade to a Cisco UCS Manager release earlier than 4.1(3), Fabric Evacuation does not work as configured.

  • When an FI is configured for evacuation, all blade and rack servers connected through the Fabric Extender are evacuated.

Configuring Fabric Evacuation

You can configure the fabric evacuation state of a fabric interconnect (FI) to enable or restart all traffic that flows through the FI. You can set the properties to turn Fabric Evacuation on automatically during an FI upgrade and reboot during Auto Install.

Procedure

Step 1

From a Cisco UCS Domain, select the Fabric Interconnects name for which you want to view the fabric evacuation state.

The Fabric Interconnect main view displays the key indicators for the FI, including the Admin Evac Mode and the Oper Evac Mode that indicate the current evacuation status of the FI.

Step 2

From Tools, select Configure Evacuation.

The Configure Evacuation dialog box displays.

Step 3

To configure fabric evacuation on the specified Fabric Interconnect, select one of the following options under Admin Evac Mode:

    • Enabled—Stops traffic on the IO module or the fabric interconnect

    • Disabled —Restarts traffic on the IO module or the fabric interconnect

Step 4

(Optional) To evacuate a Fabric Interconnect regardless of its current evacuation state, select one of the options under Force:

    • Enabled—To evacuate the FI regardless of the current evacuation state

    • Disabled —Disables force evacuation of the FI regardless of the evacuation state

    Note

     

    When you stop the server traffic and then enable traffic evacuation, the system moves to a NO-OP status. When you select the Force (Enabled) option, it ensures that the second command does not involve a NO-OP and the traffic is forced to shut down again.

Step 5

Click OK.

The following warning messages display when you choose Enabled or Disabled, respectively: 
  
There are outstanding faults since last FI reboot. Please make sure all the data paths on other
FI are working before proceeding with this FI Evacuation to avoid interruption to the data traffic.
Are you sure you want to continue?

Disabling fabric evacuation will cause server traffic that failed over to the Primary Fabric 
Interconnect to fail back to this Fabric Interconnect. Are you sure you want to continue?

Note

 

After triggering fabric evacuation, the backplane ports on the FEX/IOM are shutdown. You must reboot the fabric interconnect to restart the traffic flows.

Step 6

Click OK or Cancel on the warning messages as necessary.

On the Fabric Interconnect main view, check the values for Admin Evac Mode and Oper Evac Mode. These values display the current evacuation status.

Server Details

The Server page displays the following information related to the servers associated with the registered Cisco UCS domain:

Servers

Hardware

Configuration

Status

This column displays the following information for a server:

  • The associated domain name, chassis ID, and slot ID

  • Domain group location

  • Management IP address

This column displays the following hardware information for a server:

  • Blade server model

  • The number of cores the CPU has and the total RAM on the motherboard

  • The serial number

  • The number of CPUs and the speed

This column displays the following configuration for a server:

  • Service profile name

  • Service profile organization location

  • Firmware version

  • Firmware status

This column displays the following status for a server:

  • Overall status

  • Worst fault level

  • Power status

  • Decommissioned server.

    You can recommission a decommissioned server. You can also remove a decommissioned rack server and delete all data about the server from the Delete option in the System Tools submenu.

Servers Details Page

You can view the following information on the selected server and its components, and also perform various tasks:


Note

Depending on the server type, the options may vary.

  • Basic—Displays associated service profile, fault summary, hardware, and firmware details of the selected server. The server Asset tag is displayed as a read-only field in this page. Beginning Cisco UCS Central release 2.1, a server reboot log is also displayed with the top five reasons for the reset along with the time and source of power transition. To view the server reboot log, Cisco UCS Central 2.1 must be registered with Cisco UCS Manager 4.1(3) and later.

    For servers that have a KMIP Certification policy configured at the domain scope, this tab displays additional details related to KMIP Certificate for the supported servers. For information on security-related remote operations, see Security-Related Operations in the Cisco UCS Central Storage Management Guide.

  • Motherboard—Displays the overall status and the hardware details of the motherboard.

  • CIMC— Displays the overall status of firmware version, server activity status, hardware specifications, and in-band policy.

  • CPUs—Displays a list of all the CPUs in the server. Select a processor to view overall status and hardware and other details of the selected processor.

  • GPUs—Displays a list of all graphics cards in the server. Select a graphics card to view the overall status and additional details.

    Support for the following new GPUs:

    • NVIDIA A16 GPU on X440p: PCIE 250W 4X16GB, FHFL (UCSC-CGPU-A16 )—Cisco UCS X215c M8 (with PCIe Node).

    • NVIDIAH100-NVL GPU 400W, 94GB, 2-slot FHFL (UCSC-GPU-H100-NVL)—Cisco UCS X215c M8 (with PCIe Node), UCS X210c M7, UCS C245 M8, UCS C240 M7.

    • NVIDIA L4-Mezz GPU 70W, 24GB, 1-slot HHHL (UCSX-GPU-L4-Mezz)—Cisco UCS X215c M8 and UCS X210c M7.

    Extended support for the following existing GPUs:

    • NVIDIAL40 300W, 48GB wPWR CBL (UCSC-GPU-L40)—Cisco UCS X215c M8 (with PCIe Node).

    • NVIDIA L40S: 350W, 48GB, 2-slot FHFL GPU (UCSC-GPU-L40S)—Cisco UCS X215c M8 (with PCIe Node).

    • NVIDIA L4:70W, 24GB, 1-slot HHHL GPU (UCSC-GPU-L4)—Cisco UCS X215c M8 (with PCIe Node).

  • Security—Displays a list of all hardware security modules in the server, such as the Cisco Mezzanine Crypto Card.

  • Memory—Displays a list of available memory in the selected server. Select a memory card to view the current overall status and other details.

  • Adapters—Displays details of the adapter in the selected server. Select an adapter to view overall status, power status, and other product details. The Interfaces tab in the Adapter Details page displays details of the adapter interfaces that are added to a service profile. Select an interface to view admin state, operability status, MAC addresses, and other details of the interface. The following types of interfaces are displayed in the adapters Inventory after you assign them to the service profile:

    • DCE

    • NIC

    • HBA

    • ISCSI


      Note
      Remote operations are not supported on ISCSI devices.

    Cisco UCS Central lets you perform one of the following remote operations for the adapter interfaces: enable, disable, or reset connectivity of the devices. For an HBA interface, you can enable or disable the interface, or reset connectivity. In the case of a failover vNIC interface, you can enable, disable, or reset connectivity of the active or stand-by interfaces to the fabric interconnect. The Configuration Status window displays the Admin state of the interfaces when there is a change in the remote operations.

  • Controllers—Displays the list of storage controllers, such as SAS or FlexFlash. Select a controller to view operability and other product details. For FlexFlash FX3S Controllers, you can view the Configuration Status of the controller, Configure Auto-Sync of the SD cards, Format SD cards, and Reset the FlexFlash Controller from the Tools menu. For all other controllers, these options will be non-operational.

    You can perform these server actions for Storage controllers :


    Note
    If you choose to pair or unpair the SD cards from Configure Auto-Sync, the contents of the SD cards are synced and the status displayed in the Operation State property. The FlexFlash controller view displays the Operation Status, Raid Pair syncing status and other properties consistent with Cisco UCS Manager. For more information about FlexFlash controller properties in Cisco UCS Manager, see Cisco UCS Manager Storage Management Guide.

    Note

    The dual HBA Controllers on the Cisco S3260 servers are discovered and displayed on the server details page. This feature is supported from Cisco UCS Central 2.1 and Cisco UCS Manager 4.1(3) and later.

    Supported Storage Controllers:

    Cisco Tri-Mode 24G SAS RAID Controller w/4GB Cache (UCSC-RAID-HP) to handle U.3 drives in RAID or Direct attached modes.

  • Storage Enclosures—Displays a list of the storage enclosures in the selected server. You can view details on the enclosure or the individual slots.

  • Storage—Displays list of the storage in the selected server. Select a disk to view the current overall status, hardware, and controller details.

  • LUNs—Displays a list of the virtual drives created on the server. Select a virtual drive to view the status, configuration status, and other details. You can also perform virtual-drive related tasks.

  • From the Tools menu, you can perform the following actions: View Configuration Status, Reset, Recover, Decommission a server, Re-Acknowledge, Reset Server to Factory Default, Configure Management IPs, Start Diagnostic test, Toggle the locator LED. For more information about Diagnostic test, see About End-to-End Diagnostics.


    Note
    The Reset Server to Factory Defaults is shown only for the supported servers. This feature is supported on servers with CIMC version 2.2(7) and later.

You can perform the following server-related tasks:

  • Launch the KVM Console. You can launch the HTML-5 based KVM client from Cisco UCS Central 2.1 and later.

  • Launch Cisco UCS Manager for the specific Cisco UCS domain.


    Note

    • Your browser must have pop-ups enabled.

    • For Cisco UCS Manager release 4.1(3) or later, this launches the HTML5 GUI. If the Cisco UCS Manager credentials match the credentials for your Cisco UCS Central login, then the system will automatically log in to the Cisco UCS Manager GUI without prompting for the login information.

  • Launch Cisco UCS Manager GUI for the selected Cisco UCS domain. Beginning Cisco UCS Central 2.1, you can sign on to a Cisco UCS Domain with the same user credentials that you provide for logging on to Cisco UCS Central. These credentials will provide the same roles/locales as Cisco UCS Central. For the Cisco UCS domains prior to 3.1(2), the existing functionality will continue to work as before. If you are not logged in the Cisco UCS domain with the same password, it prompts you to provide a new password. In order to log in as a remote user, you must authenticate the user role in the Manage UCS Central Authentication window. The single sign-on feature works for launching the UCS domain and KVM on any server, or a service profile using the Cisco UCS Central user credentials, roles, and locales.


    Note

    Single sign-on is supported on Cisco UCS Manager release 4.1(3) and later.

  • Launch corresponding Cisco UCS Manager Statistics pages for the following:


    Important

    To view Cisco UCS Manager content from Cisco UCS Central, ensure to log in to the Cisco UCS Central GUI with the same hostname, or IP address that was used to register Cisco UCS Manager with Cisco UCS Central.

Beginning Cisco UCS Central 2.1, you can launch the KVM HTML-5 based client from the sub-menu in the Server view. The HTML-5 based client launches only if your set up has Cisco UCS Manager 4.1(3) or later, and if you have installed CIMC version 3.1.22.x and higher. This feature is supported on the Cisco UCS B- Series server models or higher. If you run earlier versions of Cisco UCS Manager with the supported versions of firmware, Launch KVM Client launches the Java based client.

Security Related Operations

You can create security policies for Self-Encrypting Drives (SEDs) through a Storage Profile in Cisco UCS Central. In addition to creating security policies, you can perform additional operations on the supported servers. The following table lists the remote operations and their descriptions:

Component

Remote Action

Action

Controller

Unlock Disk

Unlocks ForeignSecured and Locked Disks encrypted using a Local Policy.

Modify Remote Key

Modifies the Key in the KMIP Server and fetches the new Key for Encryption.

Disable Security

Disables Security on the Controller when no Secured Disks are present on Controller.

Unlock for Remote

Unlocks ForeignSecured and Locked Disks encrypted using a Remote Policy.

Virtual Disk

Secure Virtual Drive

Secures LUNs comprised only of SEDs when the Controller is Security Enabled.

Physical Disk

Enable Encryption

Used to Secure JBOD

Self-Encrypting Drive(SED) when Controller is Security Enabled.

Secure Erase

Erases disk cryptographically to make it Unsecured and Reusable.

Secure Erase Foreign Configuration

Erases ForeignSecured and Locked disks cryptographically to make them Unsecured and Unconfigured Good

For more information about SED Management and security policies, see Cisco UCS Manager Storage Management Guide.

Launch Cisco UCS Manager Power Tab

You can launch Cisco UCS Manager server power statistics from the Tools menu in Cisco UCS Central to view these details for the server:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

NIC Mode and NIC Redundancy Settings

Table 1. Valid NIC Redundancy Settings For Each NIC Mode

NIC Mode

Valid NIC Redundancy Settings

Shared LOM EXT

Active-active

Dedicated

None

Shared LOM

Active-active

Active-standby

Cisco Card

Active-active

Active-standby

This server has the following NIC mode settings that you can choose from:

  • Shared LOM EXT (default)—This is the shared LOM extended mode, the factory-default setting. With this mode, the Shared LOM and Cisco Card interfaces are both enabled. You must select the default Active-Active NIC redundancy setting in the following step.

    In this NIC mode, DHCP replies are returned to both the shared LOM ports and the Cisco card ports. If the system determines that the Cisco card connection is not getting its IP address from a Cisco UCS Manager system because the server is in standalone mode, further DHCP requests from the Cisco card are disabled. Use the Cisco Card NIC mode if you want to connect to Cisco IMC through a Cisco card in standalone mode.

  • Shared LOM—The 1-Gb/10-Gb Ethernet ports are used to access Cisco IMC. You must select either the Active-Active or Active-standby NIC redundancy setting in the following step.

  • Dedicated—The dedicated management port is used to access Cisco IMC. You must select the None NIC redundancy setting in the following step.

  • Cisco Card—The ports on an installed Cisco UCS Virtual Interface Card (VIC) are used to access the Cisco IMC. You must select either the Active-Active or Active-standby NIC redundancy setting in the following step.

    See also the required VIC Slot setting below.

This server has the following NIC redundancy settings that you can choose from:

  • None—The Ethernet ports operate independently and do not fail over if there is a problem. This setting can be used only with the Dedicated NIC mode.

  • Active-standby—If an active Ethernet port fails, traffic fails over to a standby port. Shared LOM and Cisco Card modes can each use either Active-standby or Active-active settings.

  • Active-active (default)—All Ethernet ports are utilized simultaneously. The Shared LOM EXT mode must use only this NIC redundancy setting. Shared LOM and Cisco Card modes can each use either Active-standby or Active-active settings.

Launch Cisco UCS Manager SEL Logs

You can launch the Cisco UCS Manager SEL Logs from Cisco UCS Central to view the system event log generated by the server.

It includes the following buttons below the log:

  • Export—Exports the log to a text file.

  • Copy—Copies the selected portion of the log to the clipboard.

  • Print—Opens the Print dialog box so that you can print the log.

  • Refresh—Displays any new messages that have been generated since the log was displayed.

  • Backup—Backs up the log to the server specified in the SEL policy for this Cisco UCS domain.

  • Clear—Clears the entries from the log.


    Note

    This action triggers an automatic backup if Clear is enabled in the SEL policy Action option box.

Launch Cisco UCS Manager Server Temperatures Tab

Displays temperature statistics for the components of the server. You can view these statistics in tabular or chart format.

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager VIF Paths Tab

You can launch theCisco UCS Manager VIF Paths table from Cisco UCS Central to view the following details about VIF Paths:

Name Description

Name column

The name of the virtual interface path. Expand the name to view the virtual circuits contained in that path, if any.

Adapter Port column

The adapter port associated with this interface.

FEX Host Port column

The FEX port that serves as the host port for this interface.

FEX Network Port column

The FEX port that serves as the network port for this interface.

FI Server Port column

The fabric interconnect (FI) port information, in the form fabric name/port ID/slot ID.

vNIC column

The vNIC associated with the virtual circuit.

FI Uplink column

The uplink status for the FI.

Link State column

The link state for the interface.

State Qual column

The link quality for the interface.

Launch Cisco UCS Manager Adapter Interface Statistics

You can launch Cisco UCS Manager adapter interface statistics from the Tools menu in Cisco UCS Central to view these details about the following adapter interfaces:

  • HBAs

  • NICs

  • iSCSI vNICs

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager Server Statistics Tab

Statistics Subtab

You can launch the Cisco UCS Manager Server Statistics tab fromCisco UCS Central and view the statistical counters available for the selected component.

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager CIMC Sessions Tab

You can view the Cisco UCS Manager CIMC Sessions for a registered UCS domain from Cisco UCS Central. The following details are displayed for the active CIMC sessions:

Column Description

Name

The name of the user who launched the session.

Session ID

The ID associated with the session.

Session Type

This can be one of the following:

  • KVM

  • Vmedia

  • SOL

CIMC Address

The Management IP address on which the session is established.

Login Time

The date and time the session started.

Last Update Time

The last time the session information was updated by CIMC.

Administrative State

This can be one of the following:

  • Active

  • Inactive

Privilege

The privilege level of the user. This can be one of the following:

  • Read-write (RW)

  • Read Only

  • Granted (vMedia)

Source Address

The IP address of the computer from which the session was opened.

Service Profile

The name of the service profile associated with the session.

The value is displayed when a session is launched with the service profile IP address.

Note

 

This field is not displayed when you view CIMC Sessions from the Servers tab.

Server

The name of the server associated with the session.

Note

 

This field is not displayed when you view CIMC Sessions from the Equipment tab.

Launch Cisco UCS Manager Installed Host Firmware Package Tab

You can view the Cisco UCS Manager Installed Host Firmware Package tab from the list of Policies in the Service Profile Details view. This option is available only if you have an associated service profile. You can view the following details for the installed firmware pack items:
Name Description
Update Firmware button

Click this button to update the firmware on one or more components.

Activate Firmware button

Click this button to activate the backup firmware version on one or more components.

Capability Catalog button

Click this button to open the Catalog Update Tasks Tab.

Management Extension button

Click this button to open the Management Extension General Tab..

Name column

A navigation tree that allows you to view a particular component and its subcomponents. You can right-click a component to view any actions available for that component.

Model column

The model number.

Running Version column

The firmware version used by the component.

Startup Version column

The version of the firmware that takes effect the next time that the component reboots.

Backup Version column

Displays the firmware version that exists in memory, but is not being used by the server.

Update Status column

This can be one of the following:

  • Ready—This firmware version is ready to activate.

  • Updating—This firmware version is being updated.

  • Failed—The firmware update failed. For more information, double-click the component to view the Status Details area on the General tab.

Activate Status column

This can be one of the following:

  • Ready—Activation succeeded and the component is running the new version.

  • Activating—The system is activating the new firmware version.

  • Failed—The firmware activation failed. For more information, double-click the failed component to view its status properties.

About End-to-End Diagnostics

With Cisco UCS Central, you can initiate end-to-end diagnostics in an integrated fashion with Cisco UCS Manager, in order to troubleshoot hardware issues and conduct burn-in tests on your environments.


Note

Cisco UCS Central does not fully support end-to-end diagnostics. For task-based information on conducting end-to-end diagnostics refer to the Cisco UCS Manager documentation. This feature also excludes policies in Cisco UCS Central. Also, Cisco UCS Central does not report instances of bad memory.


Note

Initiating the end-to-end diagnostic process causes a system reboot. Also, if the process should stop mid-execution, a fault message is captured and displays the stage in which the fault occurred. You can manually restart the diagnostic process.


Note

The connectivity to a Cisco UCS Domain can temporarily show Lost Connectivity status. This happens when Cisco UCS Manager gets extremely busy processing the job at hand and may not be able to respond to HeartBeat messages from Cisco UCS Central. The system will recover to normal connectivity after the Cisco UCS Domain completes the job.

Feature Functions

Remote diagnostic capability

Remotely diagnose your Cisco UCS Manager hardware components and environments.

Trigger the diagnostic process (start/stop) from Cisco UCS Central

Initiate the diagnostic process from within Cisco UCS Central and then let Cisco UCS Manager continue with the full diagnostic process.

Diagnoses multiple servers simultaneously

Cisco UCS Central can identify multiple servers to diagnose.

Dynamically assign diagnostic policy changes to Cisco UCS Manager

Policy changes can be pushed from Cisco UCS Central to Cisco UCS Manager.

Conducting End-to-End Diagnostics

With Cisco UCS Central, you can initiate end-to-end diagnostics in an integrated fashion with Cisco UCS Manager, in order to troubleshoot hardware issues and conduct burn-in tests on your environments.


Note

You can run diagnostics on both servers and domains. However, initiating the diagnostic process causes a server reboot. Additionally, if the diagnostic test fails, an error is shown in the fail stage in the FSM and in the result session. If you manually stop the diagnostic process, no error is displayed. Consequently, if the process should stop mid-execution, a fault message is captured and displays the stage in which the fault occurred. You can also manually restart the diagnostic process.

Procedure

Step 1

On the menu bar, click Servers.

Step 2

Choose a server.

Step 3

Click the Tools icon.

Step 4

Choose Start Diagnostics Test.

Step 5

Click Yes.

The diagnostics process begins.

Step 6

Click the System Alerts icon.

Step 7

Choose Diagnostics Configuration Status.

The Configuration Status page appears. The following information is displayed:

Option Description

Server System (Management IP)

Displays the server system (as well as the Finite State Machine (FSM) stage, if present).

Server Domain

Displays the configuration status of the selected server domain.

Diagnostic Status

Displays the current diagnostics process of the selected server or domain.

Step 8

Once the process is complete click Close.

A pass or fail notice is displayed.

Configuration Status

You can view the FSM status for a server in the domain from the Configuration Status window. You can navigate to this window from Tools > Configuration Status on the following pages:

  • Server Details

  • Service Profile Details

  • Image Library Download Details

  • Fabric Interconnect Details

  • Infrastructure Firmware Management Details

  • FlexFlash Controller

  • Globalizing Service Profiles

An FSM is a workflow model, similar to a flow chart, that is composed of the following:

  • A finite number of stages

  • Transition between those stages

  • Operations

The current stage in an FSM is determined by past stages and the operations performed to transition between these stages. The transition between one stage to another is dependent on the success or failure of an operation. The Configuration Status window displays the following details for various components:

Launch pages in Cisco UCS Central

Configuration Status Details

Server Details

  • Server System (Management IP) tab

    • System Status

    • FSM Stages

  • Server Domain tab

    • Discover Domain Status of the Current FSM

    • FSM Stages

Service Profile Details

  • Service Profile System tab

    • Success System Status

    • FSM Stages

  • Service Profile Domain tab

    • Configure Domain Status

    • FSM Stages

  • Server tab

    • Associate Domain Status

    • FSM Stages

Image Library Download Details

  • Download Success/Fail System Status

  • FSM Stages

Fabric Interconnect Details

  • Configure Physical Domain Status

  • FSM Stages

Infrastructure Firmware Management Details

  • Infrastructure Firmware Deploy Domain Status

  • FSM Stages

  • The System Status section displays these details for all components: Status, Progress Status(percent), and FSM Details (button).

  • Click FSM Details to view these details about the configuration status: Order of Operations, Name, Description, Time Stamp, Retries, and Status for the domain.

  • You can favorite the Configuration Status window to navigate directly to the configuration status of a component from the Cisco UCS Central dashboard.

FlexFlash Configuration Status

You can view the following configuration status of the FlexFlash SD cards in the FlexFlash Configuration Status window:

  • Domain Status—Shows the Last Status and the number of Retries for re-pairing the SD cards.

    • Time Stamp—Time when pairing completed

    • Stage Completed—Sync status completed

    • Stage Description—Description of the sync status

    • Error Code—Error code in the case of a failed pairing attempt

    • Error Description—Description of the error code

  • Domain Stages—Shows the Name, Time Stamp of when the SD card re-pair was attempted, and the current status of the MOpsPair.

  • Configuration Stage—Shows the Configuration Status, Order and Retries, Stage Name, Time Stamp, and Stage Description of the FlexFlash mirroring in progress.

Chassis Inventory

The Chassis page displays the following information related to the chassis associated with the registered Cisco UCS domain:

Chassis

Hardware

Configuration

Status

This column displays the following information for a chassis:

  • The associated domain name and chassis ID

  • Domain group location

  • Fabric side

This column displays the following hardware information for a chassis:

  • Model number of the chassis

  • Serial number of the chassis

  • Number of blades

This column displays the following configuration for a Chassis:

  • Configuration status

  • Configuration error count

This column displays the following status for a Chassis:

  • Overall status

  • Worst fault level

  • Power status

  • Thermal status

  • Decommissioned chassis.

    You can recommission the chassis by specifying a valid chassis ID.

Chassis Main View

The Chassis Main View page allows you to manage and monitor all chassis in a Cisco UCS domain through Cisco UCS Central GUI.

You can view the following information on the selected chassis and its components within a registered Cisco UCS domain:

  • Basic—Displays the overall status and, overview of all the components within the selected chassis, fault summary, configuration errors and hardware details.

  • IOM Left—Displays overall status, hardware details and fault summary of the left IOM module.

  • IOM Right—Displays overall status, hardware details and fault summary details of the right IOM module.

  • Servers—Displays overall status, hardware, and firmware details of the server associated with this chassis. If you select a server, the page redirects to the server detail view page.

  • Fans—Displays a list of fans in the chassis. Select a fan to view information related to its module, overall status and hardware details.

  • PSUs— Displays a list of all the PSUs in the chassis. Select a PSU to view information related to its fault summary, overall status, and other property details.

  • PCIe Nodes— Displays a list of Peripheral Component Interconnect Express (PCIe) devices and their slot IDs. Expand the PCIe Devices to display the firmware version and hardware details for each PCIe device.

    • Configuration—You can view the firmware version of the device.

    • Hardware—You can view the Slot ID, Product Name, Serial Number, and Vendor information of the device.

  • XFMs—Displays a summary of the X-Fabric Modules (XFM) in the chassis. Click a specific XFM to view the details of the fan modules. When you click a fan module, you can view the ID, model, and operational state of the fans. For more information, see Viewing X-Fabric Module (XFM) Fan Status


    Note

    The XFM (UCSX-F-9416) slots are to be present in the respective two slots of UCSX 9508 Chassis.

You can also perform the following tasks:

  • Acknowledge and decommission a chassis. You can also launch the chassis statistics tab on Cisco UCS Manager.

  • Turn on or turn off the Locator LED for a chassis.

  • Verify that that you are in a Single-Server Single SIOC or Single-Server Dual SIOC mode.

  • Launch Cisco UCS Manager for the specific Cisco UCS domain.


    Note

    • Your browser must have pop-ups enabled.

    • For Cisco UCS Manager release 4.1(3) or later, this launches the HTML5 GUI. If the Cisco UCS Manager credentials match the credentials for your Cisco UCS Central login, then the system will automatically log in to the Cisco UCS Manager GUI without prompting for the login information.

Launch Cisco UCS Manager Chassis Statistics

You can launch Cisco UCS Manager Chassis statistics from the Tools menu in Cisco UCS Central to view these details for a chassis:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager Chassis FAN Statistics

You can launch Cisco UCS Manager Chassis FAN statistics from the Tools menu in Cisco UCS Central to view these details for a chassis:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click the + (plus sign) button at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)— Amperes

  • (babbles)

  • (bytes)— Number of bytes

  • ©)—Celsius

  • (collisions)— Number of times a network collision was encountered

  • (drops)— Number of times packets were dropped during the transfer

  • (errors)— Number of errors encountered

  • (lostCarrier)— Number of times the carrier was lost during transmission

  • (MB)— Megabytes

  • (noCarrier)— Number of times no carrier could be found

  • (packets)— Number of packets transferred

  • (pause)— Number of pauses encountered during data transmission

  • (resets)— Number or resets encountered during data transmission

  • (V)—Volts

  • (W)— Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager PSU Statistics

You can launch Cisco UCS Manager PSU statistics for a chassis from the Tools menu in Cisco UCS Central to view these details for a chassis:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager Fabric Interconnect IO Module Left Statistics

You can launch Cisco UCS Manager Fabric Interconnect IOM Left statistics from the Tools menu in Cisco UCS Central to view these details for the IO module:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Launch Cisco UCS Manager Fabric Interconnect IO Module Right Statistics

You can launch Cisco UCS Manager Fabric Interconnect IOM Right statistics from the Tools menu in Cisco UCS Central to view these details for the IO module:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Storage Chassis View

The Storage Chassis page allows you to manage and monitor all Cisco UCS S3260 Storage Servers in a Cisco UCS domain.

You can view the following information on the selected chassis and its components:

  • Basic—Displays the overall status and an overview of all the components within the selected chassis, fault summary, configuration errors and hardware details.

  • System IO Controllers—Displays overall status and detailed information about the shared adapter.

  • Servers—Displays overall status, hardware, and firmware details of the server associated with this chassis. If you select a server, the page redirects to the server detail view page.

  • SAS Expanders—Displays the overall status, configuration, and hardware for each SAS expander associated with this chassis.

  • Storage Enclosures—Displays the overall status and configuration of the storage enclosures associated with this chassis by enclosure or by slot.

  • Storage—Displays list of the storage in the selected server. Select a disk to view the current overall status, hardware, and controller details.

  • Fans—Displays a list of fans in the chassis. Select a fan to view information related to its module, overall status and hardware details.

  • PSUs—Displays a list of all the PSUs in the chassis. Select a PSU to view information related to its fault summary, overall status, and other property details.

You can also perform the following tasks:

  • Acknowledge and decommission a chassis.

  • Turn on or turn off the Locator LED for a chassis.

  • Modify the discovery policy for the selected chassis.

  • Launch Cisco UCS Manager for the specific Cisco UCS domain.


    Note

    • Your browser must have pop-ups enabled.

    • For Cisco UCS Manager release 4.1(3) or later, this launches the HTML5 GUI. If the Cisco UCS Manager credentials match the credentials for your Cisco UCS Central login, then the system will automatically log in to the Cisco UCS Manager GUI without prompting for the login information.

FEX

The All FEX page displays the following information for each FEX associated with a registered Cisco UCS domains:

FEX

Hardware

Configuration

Status

This column displays the following information for a FEX:

  • The associated domain name and FEX ID

  • Domain group location

  • Fabric Side

This column displays the following hardware information for a FEX:

  • Model number

  • Serial number

  • Number of ports available

This column displays the following configuration for a FEX:

  • Configuration status

  • Configuration error count

This column displays the following status for a FEX:

  • Overall status

  • Worst fault level

  • Power status

  • Thermal status

  • Decommissioned FEX.

    You can recommission the FEX by specifying a valid FEX ID.

    You can also remove a decommissioned FEX and delete all data about the FEX from the Delete option in the System Tools submenu.

FEX Main View

You can view the following information related to the FEX and its components within a registered Cisco UCS domain:

  • Basic—Displays fault summary, overall status and hardware details of the FEX within UCS domain.

  • IOM—Displays fault summary, overall status, and properties of the IOM.

  • Servers—Displays number of rack servers connected to the FEX. Select a server to view more information on overall status, firmware and hardware details of the server.

  • Fans—Displays a list of fans in the FEX. Select a fan to view more information related to the module number, overall status and hardware details.

  • PSUs— Displays a list of all the PSUs in the FEX. Select a PSU to view details on fault summary, status, properties, and status of power supply units.

You can also perform the following tasks:

  • Acknowledge, decommission, and recommission a FEX.

  • Turn on or turn off Locator LED for FEXes.

  • Launch Cisco UCS Manager for the specific Cisco UCS domain.


    Note

    • Your browser must have pop-ups enabled.

    • For Cisco UCS Manager release 4.1(3) or later, this launches the HTML5 GUI. If the Cisco UCS Manager credentials match the credentials for your Cisco UCS Central login, then the system will automatically log in to the Cisco UCS Manager GUI without prompting for the login information.

Launch Cisco UCS Manager FEX Statistics

You can launch Cisco UCS Manager FEX statistics from the Tools menu in Cisco UCS Central to view these details:

Name Description

Toggle History Table button

Splits the right-hand pane vertically and displays the History table in the bottom portion of the pane. When you select a counter in the top portion of the pane, the History table displays the information recorded each time the data from that counter was collected.

Modify Collection Policy button

Open the General tab for the selected counter, which enables you to specify the collection and reporting intervals for the counter.

Note

 

This option is only available if a counter is selected.

Name column

A tree view showing the system components for which statistical counters are available. To view the counters associated with a component, expand that part of the navigation tree. To view all counters, click + (plus sign) at the top of the chart.

System statistics for fabric interconnects and FEX are available. These include:

  • CPU usage

  • Memory usage, including low kernel memory

    Note

     

    A major fault is raised on the fabric interconnect if the available kernel memory is less than 100 MB.

  • ECC errors

Value column

For the top-level component, this column shows the date and time the counter was last updated. For the actual counters, this column shows the current value of the counter.

The unit the value is in can be determined by the code appended to the name of the counter:

  • (A)—Amperes

  • (babbles)

  • (bytes)—Number of bytes

  • (©)—Celsius

  • (collisions)—Number of times a network collision was encountered

  • (drops)—Number of times packets were dropped during the transfer

  • (errors)—Number of errors encountered

  • (lostCarrier)—Number of times the carrier was lost during transmission

  • (MB)—Megabytes

  • (noCarrier)—Number of times no carrier could be found

  • (packets)—Number of packets transferred

  • (pause)—Number of pauses encountered during data transmission

  • (resets)—Number or resets encountered during data transmission

  • (V)—Volts

  • (W)—Watts

  • (blank)

Avg column

The average value for the counter.

Note

 

For aggregated counters, this is the average delta within the reporting interval.

Max column

The maximum recorded value for the counter.

Note

 

For aggregated counters, this is the maximum delta within the reporting interval.

Min column

The minimum recorded value for the counter.

Note

 

For aggregated counters, this is the minimum delta within the reporting interval.

Delta column

The largest change recorded for the counter.

Chart Subtab

If you already created a chart during this session, the Chart tab displays that chart. Otherwise, when you navigate to the Chart tab, Cisco UCS Manager GUI displays the Select Statistics dialog box. This dialog box enables you to select one or two statistics to view as a line graph.

If you right-click the chart, you can access a pop-up menu with additional options. This menu enables you to:

  • Change the appearance of the chart by selecting Properties

  • Change the statistics displayed on the chart by selecting Configure Chart

  • Print the chart by selecting Print

Domains Table View

The Domains Table View page displays the following information related to the domains registered with Cisco UCS Central:

Domain

Hardware

Configuration

Status

This column displays the following information for a registered domain:

  • The associated domain name and site

  • Domain group location

  • Management IP address

  • Owner

This column displays the following hardware information for a registered domain:

  • Fabric interconnect model number and cluster state (HA or Standalone)

  • Number of chassis and FEX

  • Number of blade and rack servers

  • Number of blade servers available for storage

This column displays the following configuration for a registered domain:

  • Platform family

  • Firmware version

  • Firmware status

This column displays the following status for a registered domain:

  • Overall status

  • Worst fault level

  • Trial expiry or status

Domain Group Details

From the Domain Group page, you can view information about the entities associated with a domain group. This includes the following:

  • Backup

  • Settings

  • Inventory

  • Domain IDs

  • Policies

  • VLANs

  • VSANs

If you click the Settings icon, you can perform the following tasks:

  • Create a system profile or system policy.

  • Manage users, authentication, SNMP, and Call Home settings.

  • Edit the domain group, and delete any user-created domain group.


    Note

    The domain group root cannot be deleted.

Domains Main View

The Cisco UCS Domain page displays the following information related to a selected Cisco UCS domain:

  • Basic—Displays information related to the overall status, firmware, resources available, fault summary and management details of the selected Cisco UCS domain.

    Also, you can suspend and acknowledge a Cisco UCS Central subscription, and re-evaluate the membership of the domain. The Firmware Upgrade Validation Status field displays Failure to indicate that upgrade has failed. You must resolve the faults before you use the Force Deploy option to continue with the upgrade.

  • FI—Displays the number of Fabric Interconnects (FI) associated with a domain, overall status, hardware, and firmware details of the FI.

    If you want to view more information on the status of the components in the FI, click on an FI from the list.

  • Chassis—Displays the number of chassis associated with a domain, overall status, hardware, and configuration details of the chassis. For more information on the status of the components in the chassis, click on a chassis from the list.

  • FEX—Displays the number of FEX associated with a domain, overall status, hardware, and configuration details of the FEX. For more information on the status of the components in the FEX, click on an FEX from the list.

  • Servers—Displays the number of servers in a domain and the number of available servers. For more information on overall status, hardware, and configuration details of the server, click Go to Servers Table.

  • Pin Groups—Displays the list of all pin groups in a domain and the details of each pin group.

  • FC Zone Profiles—Displays list of FC Zone Profiles created in the Domain.

  • Diagnostics — Launch Cisco UCS Central Diagnostic tests.

On the Cisco UCS Domain page, you can do the following:

  • Launch Cisco UCS Manager GUI for the selected Cisco UCS Domain. Beginning Cisco UCS Central release 2.1, you can sign-on to a Cisco UCS Domain with the same user credentials that you provide for logging on to Cisco UCS Central. However, you will be prompted to specify the new password if the passwords are different. In order to log in as a remote user, you must authenticate the user role in the Manage UCS Central Authentication window. After you authenticate the user, you need not provide the credentials again to sign-on to the Cisco UCS Domain. You can also create local user roles and define permissions, authentication servers, locales, and domain groups and sign-on to the Cisco UCS Domain from Cisco UCS Central without specifying the credentials again.


    Note

    Single sign-on is supported on Cisco UCS manager release 4.1(3) and later.

  • Activate UCS Central subscription when the overall status of a domain is suspended.

  • Re-evaluate membership

  • Assign Domain to Domain Group

  • Create Pin Group — Create a LAN or SAN Pin Group.

  • Create FC Zone Profile

  • Domain Configuration Settings

  • Suspend UCS Central Subscription (when the overall status of a domain is OK).

  • Reapply Configuration

ID Universe

The ID Universe displays the collections of identities, or physical or logical resources, that are available in the system. All pools increase the flexibility of service profiles and allow you to centrally manage your system resources. Pools that are defined in Cisco UCS Central are called Global Pools and can be shared between Cisco UCS domains. Global Pools allow centralized ID management across Cisco UCS domains that are registered with Cisco UCS Central. By allocating ID pools from Cisco UCS Central to Cisco UCS Manager, you can track how and where the IDs are used, prevent conflicts, and be notified if a conflict occurs. Pools that are defined locally in Cisco UCS Manager are called Domain Pools.


Note

The same ID can exist in different pools, but can be assigned only once. Two blocks in the same pool cannot have the same ID.

You can pool identifying information, such as MAC addresses, to preassign ranges for servers that host specific applications. For example, you can configure all database servers across Cisco UCS domains within the same range of MAC addresses, UUIDs, and WWNs.

From the ID Universe page, you can view the total number IDs for each type of pool, and how many of the total are Available, In Use, or have a Conflict. If you click on a Resource, you can view detailed information about that ID and where it is used.

All Pools

Display a complete list of ID pools in the system. You can use filter to sort by Utilization Status, Org or ID Type to view availability and usage.

Exporting Inventory Lists

You can export data to CSV, XLS, and PDF formats from table views in Cisco UCS Central.

Procedure

Step 1

In the Task bar, select a data table of an inventory view from the Show search tables menu.

This launches the Opening report dialog box.

Step 2

In an inventory view, click the CSV, XLS, or PDF icon of your selected export format.

This launches the Opening report dialog box.

Step 3

Click the Open with or Save as option to complete the export process.

Viewing Configuration Status

Procedure

Step 1

Navigate to the All Servers, All Chassis, All Fabric Interconnects, All FEX, or Firmware page.

For example, select Servers from the Search icon, or select Firmware from the Operations icon.

Step 2

Click on a server, chassis, FI, FEX, or firmware package.

Step 3

On the detailed view for your selection, click the Notification icon (bell icon representation) and select Configuration Status.

The Configuration Status page displays.

Step 4

Click Close to close the window.

Inventory Faults

You can view faults from each individual inventory page. Click the Browse Tables icon and choose a physical inventory type. Click your selection to open the inventory page, and then click the Faults icon to view the following information:

  • Filters—Filter the data in the table by severity, fault type, and timestamp.

  • Code—Unique identifier associated with the fault.

  • Timestamp—Day and time at which the fault occurred.

  • Cause—Brief description of what caused the fault.

  • Affected Object—The name and location of the component that this issue affects, and the domain name where it is found.

  • Fault Details—More information about the log message.

  • Severity—Displays an icon denoting the fault severity. The icon key displays below the table.

  • Action—Whether user acknowledgment is required.

Toggling Locator LEDs

You can toggle the locator LEDs on and off for servers, chassis, fabric interconnects, and FEXes.

Procedure

Step 1

Navigate to the All Servers, All Chassis, All Fabric Interconnects, or All FEX page.

For example, select Servers from the Search icon.

Step 2

From the All Servers, All Chassis, All Fabric Interconnects, or All FEX page, click on a server, chassis, FI, or FEX.

Step 3

On the detailed view for the selected server, chassis, FI, or FEX, check the status of the Locator LED.

The Locator LED status is located at the top of the Basic tab.

Step 4

Click the Operations icon and select Toggle Locator LED.

About End-to-End Diagnostics

With Cisco UCS Central, you can initiate end-to-end diagnostics in an integrated fashion with Cisco UCS Manager, in order to troubleshoot hardware issues and conduct burn-in tests on your environments.


Note

Cisco UCS Central does not fully support end-to-end diagnostics. For task-based information on conducting end-to-end diagnostics refer to the Cisco UCS Manager documentation. This feature also excludes policies in Cisco UCS Central. Also, Cisco UCS Central does not report instances of bad memory.


Note

Initiating the end-to-end diagnostic process causes a system reboot. Also, if the process should stop mid-execution, a fault message is captured and displays the stage in which the fault occurred. You can manually restart the diagnostic process.


Note

The connectivity to a Cisco UCS Domain can temporarily show Lost Connectivity status. This happens when Cisco UCS Manager gets extremely busy processing the job at hand and may not be able to respond to HeartBeat messages from Cisco UCS Central. The system will recover to normal connectivity after the Cisco UCS Domain completes the job.

Feature Functions

Remote diagnostic capability

Remotely diagnose your Cisco UCS Manager hardware components and environments.

Trigger the diagnostic process (start/stop) from Cisco UCS Central

Initiate the diagnostic process from within Cisco UCS Central and then let Cisco UCS Manager continue with the full diagnostic process.

Diagnoses multiple servers simultaneously

Cisco UCS Central can identify multiple servers to diagnose.

Dynamically assign diagnostic policy changes to Cisco UCS Manager

Policy changes can be pushed from Cisco UCS Central to Cisco UCS Manager.

Displaying the Results of an End-to-End Diagnostic Test

Before you begin

Initiate the About End-to-End Diagnostics process.

Procedure

  Command or Action Purpose

Step 1

UCSC(resource-mgr)/domain-mgmt/ucs-domain/chassis/server/diag # show detail server-name

Shows the details of the server diagnostic process.

Step 2

UCSC(resource-mgr)/domain-mgmt/ucs-domain/chassis/server/diag* # show result

Displays the server diagnostic results.

Step 3

UCSC(resource-mgr)/domain-mgmt/ucs-domain/chassis/server/diag # scope result result-number

Enters into the results information and assigns a number to the output.

Step 4

UCSC(resource-mgr)/domain-mgmt/ucs-domain/chassis/server/diag # show detail

Displays the server diagnostic results.

Example

The following example shows how to create a end-to-end diagnosis and display the operation's details: 

UCSC(resource-mgr)# scope org /
UCSC(resource-mgr) /domain-mgmt/ucs-domain/chassis/server/diag* # show detail 

Server Diagnostics:
 Oper State: Failed
 Error Descr: Diagnostic operation Failed
 Diag Overall Progress: 100
 Current Diag Policy Name: BBB
 Scheduled Diag Policy Name:
 Current Task:
UCSC(resource-mgr) /domain-mgmt/ucs-domain/chassis/server/diag* # show result 

Server Diag Results:
 Id Status Descr Result Progress
 --- ----------- --------------------------------------------- ------- --------
 1 Completed Test passed Pass 100
UCSC(resource-mgr) /domain-mgmt/ucs-domain/chassis/server/diag* # show result 1
UCSC(resource-mgr) /domain-mgmt/ucs-domain/chassis/server/diag/result* # show detail

Server Diag Results:
 Id: 1
 Status: Completed
 Descr: Test passed
 Result: Pass
 Progress: 100
UCSC(resource-mgr) /domain-mgmt/ucs-domain/chassis/server/diag/result* #

Dynamic Searches

Cisco UCS Central enables you to save a dynamic search query that includes filters such as name, label, tag, ID, and PID. Unless you delete a query, it is retained when background processes are restarted or when the system is rebooted. Your search results are dynamically updated with current data when you select and execute a saved query.

Saving Dynamic Search Queries

Procedure

Step 1

From the Task bar, select a view such as Domains, Policies, Schedules from the navigation menu.

Step 2

In the Filters panel, select parameters for your search such as Fault level status or Platform name.

When you make selections, a save icon appears at the right of Filters.

Step 3

Click the save icon and enter a context-sensitive name for the search query you want to create.

Step 4

Click Save this filter.

The query you created is listed under Saved Searches in the Filters panel.

Executing a Saved Search Query

Procedure

Step 1

In the Filters panel under Saved Searches, select a query that you previously saved.

Step 2

Verify that the filters you selected when you created the query are checked.

The search results are dynamically updated.

Deleting a Saved Search Query

Procedure

Step 1

In the Filters panel under Saved Searches, select a query that you previously saved.

Step 2

Click the trash can icon at the right of the query name.

The search query immediately disappears.