The Cisco UCS 6300 Series Fabric Interconnect joins next-generation UCS products, including the following hardware:

Cisco UCS 6332 Fabric Interconnect, an Ethernet or Fibre Channel over Ethernet (FCoE) chassis with 32 40-Gigabit Ethernet QSFP+ ports

Cisco UCS 6332-16UP Fabric Interconnect, an Ethernet, FCoE, and Fibre Channel chassis with 16 1- or 10-Gigabit Ethernet SFP+ ports or 16 4-, 8-, or 16-Gbps Fibre Channel ports, 24 40-Gigabit Ethernet QSFP+ ports

Cisco 2304 IOM or Cisco 2304V2, I/O modules with eight 40-Gigabit backplane ports and four 40-Gigabit Ethernet uplink ports

Multiple VICs

UCS 6332 Fabric Interconnect is a 1RU, top-of-rack switch with 32 40-Gigabit Ethernet QSFP+ ports, one 100/1000 network management port, one RS-232 console port for setting the initial configuration, and two USB ports for saving or loading configurations (see Figure 12-10). The switch also includes an L1 port and an L2 port for connecting two fabric interconnects to provide high availability. The switch mounts in a standard 19-inch rack, such as the Cisco R-Series rack. Cooling fans pull air front-to-rear. That is, air intake is on the fan side, and air exhaust is on the port side.

Figure 12-10 Cisco UCS Fabric Interconnect 6332

Ports on the Cisco UCS 6300 Series Fabric Interconnects can be configured to carry either Ethernet or Fibre Channel traffic. These ports are not reserved. They cannot be used by a Cisco UCS domain until you configure them. When you configure a port on a fabric interconnect, the administrative state is automatically set to enabled. If the port is connected to another device, this may cause traffic disruption. You can disable the port after it has been configured.

The Cisco UCS Fabric Interconnect 6300 Series supports splitting a single QSFP port into four 10-Gigabit Ethernet ports using a supported breakout cable. By default, there are 32 ports in the 40-Gigabit mode. These 40-Gigabit Ethernet ports are numbered in a 2-tuple naming convention. For example, the second 40-Gigabit Ethernet port is numbered as 1/2. The process of changing the configuration from 40-Gigabit Ethernet to 10-Gigabit Ethernet is called breakout, and the process of changing the configuration from 4 10-Gigabit Ethernet to 40-Gigabit Ethernet is called unconfigure. When you break out a 40-Gigabit Ethernet port into 10-Gigabit Ethernet ports, the resulting ports are numbered using a 3-tuple naming convention. For example, the breakout ports of the second 40-Gigabit Ethernet port are numbered as 1/2/1, 1/2/2, 1/2/3, and 1/2/4. Table 12-2 summarizes the constraints for breakout functionality for Cisco UCS 6300 Series Fabric Interconnects.

Table 12-2 Cisco UCS 6300 Port Breakout Summary

Note

Up to four breakout ports are allowed if QoS jumbo frames are used.

The Cisco UCS 6454 Fabric Interconnect provides both network connectivity and management capabilities to the Cisco UCS system. The fabric interconnect provides Ethernet and Fibre Channel to the servers in the system. The servers connect to the fabric interconnect and then to the LAN or SAN.

Each Cisco UCS 6454 Fabric Interconnect runs the Cisco UCS Manager to fully manage all Cisco UCS elements. The fabric interconnect supports 10/25-Gigabit Ethernet ports in the fabric with 40/100-Gigabit Ethernet uplink ports. High availability can be achieved when a Cisco UCS 6454 Fabric Interconnect is connected to another Cisco UCS 6454 Fabric Interconnect through the L1 or L2 port on each device. UCS 6454 FI is a 1RU top-of-rack switch that mounts in a standard 19-inch rack, such as the Cisco R Series rack. It has 44 10/25-Gigabit Ethernet SFP28 ports (16 unified ports), 4 1/10/25-Gigabit Ethernet ports and 6 40/100-Gigabit Ethernet QSFP28 ports. Each 40/100-Gigabit Ethernet port can break out into 4 10/25-Gigabit Ethernet uplink ports. The 16 unified ports support 10/25-Gigabit Ethernet or 8/16/32-Gbps Fibre Channel speeds.

Note

The Cisco UCS 6454 Fabric Interconnect supported 8 unified ports (ports 1–8) with Cisco UCS Manager 4.0(1) and 4.0(2), but with release 4.0(4) and later it supports 16 unified ports (ports 1–16).

The Cisco UCS 6454 Fabric Interconnect supports a maximum of eight FCoE port channels or four SAN ports, or a maximum of eight SAN port channels and FCoE port channels (four each). It also has one network management port, one console port for setting the initial configuration, and one USB port for saving or loading configurations. The FI also includes L1/L2 ports for connecting two fabric interconnects for high availability. The fabric interconnect contains a CPU board that consists of the following:

Intel Xeon D-1528 v4 Processor, 1.6 GHz

64 GB of RAM

8 MB of NVRAM (4 NVRAM chips)

128-GB SSD (bootflash)

The ports on the Cisco UCS 6454 Fabric Interconnect can be configured to carry either Ethernet or Fibre Channel traffic. You can configure only the first 16 ports to carry Fibre Channel traffic. The ports cannot be used by a Cisco UCS domain until you configure them.

Note

When you configure a port on a fabric interconnect, the administrative state is automatically set to enabled. If the port is connected to another device, this may cause traffic disruption. The port can be disabled and enabled after it has been configured.

Ports on the Cisco UCS 6454 Fabric Interconnect are numbered and grouped according to their function. The ports are numbered top to bottom and left to right. Figure 12-9 shows the port numbering, which is as follows:

Figure 12-9 Cisco UCS 6454 Fabric Interconnect

1. Ports 1–16: Unified ports can operate as 10/25-Gigabit Ethernet or 8/16/32-Gbps Fibre Channel. FC ports are converted in groups of four.

2. Ports 17–44: Each port can operate as either a 10-Gbps or 25-Gbps SFP28 port.

Note

When you use Cisco UCS Manager releases earlier than 4.0(4), ports 9–44 are 10/25-Gbps Ethernet or FCoE.

3. Ports 45–48: Each port can operate as a 1-Gigabit Ethernet, 10-Gigabit Ethernet, or 25-Gigabit Ethernet or FCoE port.

4. Uplink Ports 49–54: Each port can operate as either a 40-Gbps or 100-Gbps Ethernet or FCoE port. When you use a breakout cable, each of these ports can operate as 4 × 10-Gigabit Ethernet or 4 × 25-Gigabit Ethernet or FCoE ports. Ports 49–54 can be used only to connect to Ethernet or FCoE uplink ports, and not to UCS server ports.

Cisco UCS 6454 Fabric Interconnects support splitting a single 40/100-Gigabit Ethernet QSFP port into four 10/25-Gigabit Ethernet ports using a supported breakout cable. These ports can be used only as uplink ports connecting to a 10/25G switch. On the UCS 6454 Fabric Interconnect, by default, there are six ports in the 40/100G mode. These are ports 49 to 54. These 40/100G ports are numbered in a 2-tuple naming convention. For example, the second 40G port is numbered as 1/50. The process of changing the configuration from 40G to 10G, or from 100G to 25G is called breakout, and the process of changing the configuration from 4 × 10G to 40G or from 4 × 25G to 100G is called unconfigure.

When you break out a 40G port into 10G ports or a 100G port into 25G ports, the resulting ports are numbered using a 3-tuple naming convention. For example, the breakout ports of the second 40-Gigabit Ethernet port are numbered as 1/50/1, 1/50/2, 1/50/3, and 1/50/4. Figure 12-9 shows the rear view of the Cisco UCS 6454 Fabric Interconnect and includes the ports that support breakout port functionality (Group 4).

The Cisco UCS S3260 storage server is a modular dual-node x86 server designed for investment protection (see Figure 12-6). Its architectural flexibility provides high performance or high capacity for your data-intensive workloads. Using a storage server combined with the Cisco UCS Manager, you can easily deploy storage capacity from terabytes to petabytes within minutes.

Figure 12-5 UCS C-Series Rack Servers

Figure 12-6 Cisco UCS Storage Server

The Cisco UCS S3260 server is designed as a storage server to support storage and processing of huge amounts of data in the data canter. It provides dual-node capability, based on the 2nd Gen Intel® Xeon® Scalable processor, it features up to 1,080 TB of local storage in a compact 4-Rack-Unit (4RU) form factor. The drives can be configured with enterprise-class Redundant Array of Independent Disks (RAID) redundancy or with a pass-through Host Bus Adapter (HBA) controller. Network connectivity is provided with dual-port up to 40-Gbps nodes in each server, with expanded unified I/O capabilities for data migration between Network-Attached Storage (NAS) and SAN environments. This storage-optimized server comfortably fits in a standard 32-inch-depth rack, such as the Cisco® R 42610 Rack..

Cisco UCS B-Series blade servers are based on Intel Xeon processors (see Figure 12-4). They work with virtualized and nonvirtualized applications to increase performance, energy efficiency, flexibility, and administrator productivity.

With the Cisco UCS blade server, you can quickly deploy stateless physical and virtual workloads with the programmability that the Cisco UCS Manager and Cisco Single Connect technology enables.

Cisco UCS B480 M5 is a full-width server that uses second-generation Intel Xeon Scalable processors or Intel Xeon Scalable processors with up to 12 TB of memory, or up to 18 TB of Intel Optane DC persistent memory; up to four SAS, SATA, and NVMe drives; M.2 storage; up to four GPUs; and 160-Gigabit Ethernet connectivity. It offers exceptional levels of performance, flexibility, and I/O throughput to run the most demanding applications.

Figure 12-4 UCS B200 M5 and B480 M5 Blade Servers

Cisco UCS B200 M5 is a half-width server that uses second-generation Intel Xeon Scalable processors or Intel Xeon Scalable processors with up to 3 TB of memory or 6 TB of Intel Optane DC persistent memory; up to two SAS, SATA, and NVMe drives; plus M.2 storage; up to two GPUs; and up to 80-Gigabit Ethernet. The Cisco UCS B200 M5 blade server offers exceptional levels of performance, flexibility, and I/O throughput to run applications.

A new addition to the Cisco B-series servers is the 6^th generation of blade servers, which comes in the form of the B200 M6 blade server. Building on the legacy of the B200 servers, it provides extended support for up to 12 TB of memory, up to 40 cores per socket, four M.2 drives with RAID support, two Cisco VIC 1400. The sixth generation B200 servers have two CPU sockets and support for the 3^rd generation of Intel Scalable CPUs.

Note

The central processing unit (CPU) is designed to control all computer parts, improve performance, and support parallel processing. The current CPU is a multicore processor. A graphic processing unit (GPU) is used in computer graphic cards and image processing. The GPU can be used as a coprocessor to accelerate CPUs. In today’s IT world, distributed applications (such as artificial intelligence, or AI) or deep learning applications require high-speed and parallel processing. GPUs are the best solution for distributed applications because GPUs contain high-core density (256 cores or more) compared to CPUs that contain 8 or 16 or a maximum of 32 cores. CPUs can offload some of the compute-intensive and time-consuming portions of the code to the GPU.

The Cisco Unified Computing System (UCS) has a unique architecture that integrates compute, data network access, and storage network access into a common set of components under a single management portal (single-pane-of-glass portal). The Cisco UCS combines access layer networking and servers. This high-performance, next-generation server system provides a data center with a high degree of workload agility and scalability. The hardware and software components support Cisco’s unified fabric, which runs multiple types of data center traffic over a single converged network adapter. Figure 12-1 shows UCS management and network connectivity.

Figure 12-1 Cisco Unified Computing System Architecture

The simplified architecture of the Cisco UCS reduces the number of required devices and centralizes switching resources. By eliminating switching inside a chassis, Cisco significantly reduced the network access layer fragmentation. The Cisco UCS implements a Cisco unified fabric within racks and groups of racks, supporting Ethernet and Fibre Channel protocols. This simplification reduces the number of switches, cables, adapters, and management points by up to two-thirds. All devices in a Cisco UCS domain remain under a single management domain, which remains highly available through the use of redundant components. The Cisco UCS architecture provides the following features (see Figure 12-2):

High availability: The management and data plane of the Cisco UCS is designed for high availability and redundant access layer fabric interconnects. In addition, the Cisco UCS supports existing high-availability and disaster recovery solutions for the data center, such as data replication and application-level clustering technologies.

Scalability: A single Cisco UCS domain supports multiple chassis and their servers, all of which are administered through one Cisco UCS Manager.

Flexibility: A Cisco UCS domain allows you to quickly align computing resources in the data center with rapidly changing business requirements. This built-in flexibility is determined by whether you choose to fully implement the stateless computing feature. Pools of servers and other system resources can be applied as necessary to respond to workload fluctuations, support new applications, scale existing software and business services, and accommodate both scheduled and unscheduled downtime. Server identity can be abstracted into a mobile service profile that can be moved from server to server with minimal downtime and no need for additional network configuration. With this level of flexibility, you can quickly and easily scale server capacity without having to change the server identity or reconfigure the server, LAN, or SAN. During a maintenance window, you can quickly do the following:

 Deploy new servers to meet unexpected workload demand and rebalance resources and traffic.

Shut down an application, such as a database management system, on one server and then boot it up again on another server with increased I/O capacity and memory resources.

The Cisco Unified Computing System (UCS) is the industry’s first converged data center platform. The Cisco UCS delivers smart, programmable infrastructure that simplifies and speeds enterprise-class applications and service deployment in bare-metal, virtualized, and cloud-computing environments.

The Cisco UCS is an integrated computing infrastructure with intent-based management to automate and accelerate deployment of all applications, including virtualization and cloud computing, scale-out and bare-metal workloads, and in-memory analytics, in addition to edge computing that supports remote and branch locations and massive amounts of data from the Internet of Things (IoT).

This chapter covers the following key topics:

Cisco UCS Architecture: This section provides an overview of UCS B-Series, C-Series, and Fabric Interconnect (FI) architecture and connectivity.

Cisco UCS Initial Setup and Management: This section covers UCS B-Series and C-Series initial setup and configuration.

Cisco UCS Network Management: This section discusses UCS LAN management, including VLANs, pools, polices, quality of service (QoS), and templates.

Cisco UCS Storage: This section discusses UCS SAN management, including SAN connectivity (iSCSI, Fibre Channel, FCoE), VSANs, WWN pools, and zoning.

“Do I Know This Already?” Quiz

The “Do I Know This Already?” quiz enables you to assess whether you should read this entire chapter thoroughly or jump to the “Exam Preparation Tasks” section. If you are in doubt about your answers to these questions or your own assessment of your knowledge of the topics, read the entire chapter. Table 12-1 lists the major headings in this chapter and their corresponding “Do I Know This Already?” quiz questions. You can find the answers in Appendix A, “Answers to the ‘Do I Know This Already?’ Quizzes.”

Table 12-1 “Do I Know This Already?” Section-to-Question Mapping

Caution

The goal of self-assessment is to gauge your mastery of the topics in this chapter. If you do not know the answer to a question or are only partially sure of the answer, you should mark that question as wrong for purposes of the self-assessment. Giving yourself credit for an answer you correctly guess skews your self-assessment results and might provide you with a false sense of security.

The Remote SPAN (RSPAN) feature enables you to remotely monitor traffic for one or more SPAN sources distributed in one or more source switches in a Fibre Channel fabric. The SPAN destination (SD) port is used for remote monitoring in a destination switch. A destination switch is usually different from the source switch(es) but is attached to the same Fibre Channel fabric. You can replicate and monitor traffic in any remote Cisco MDS 9000 Family switch or director, just as you would monitor traffic in a Cisco MDS source switch.

The RSPAN feature is nonintrusive and does not affect network traffic switching for those SPAN source ports. Traffic captured on the remote switch is tunneled across a Fibre Channel fabric that has trunking enabled on all switches in the path from the source switch to the destination switch. The Fibre Channel tunnel is structured using trunked ISL (TE) ports. In addition to TE ports, the RSPAN feature uses two other interface types, as shown in Figure 11-6.

SD ports: A passive port. The FC analyzer can obtain remote SPAN traffic from these passive ports.

ST ports: SPAN tunnel (ST) ports are entry point ports in the source switch for the RSPAN Fibre Channel tunnel. ST ports are special RSPAN ports and cannot be used for normal Fibre Channel traffic.

RSPAN has the following advantages:

Enables nondisruptive traffic monitoring at a remote location

Provides a cost-effective solution by using one SD port to monitor remote traffic on multiple switches

Works with any Fibre Channel analyzer

Is compatible with the Cisco MDS 9000 Port Analyzer adapters

Does not affect traffic in the source switch but shares the ISL bandwidth with other ports in the fabric

Figure 11-6 RSPAN Transmission

An FC tunnel is a logical data path between a source switch and a destination switch. The FC tunnel originates from the source switch and terminates at the remotely located destination switch. RSPAN uses a special Fibre Channel tunnel (FC tunnel) that originates at the ST port in the source switch and terminates at the SD port in the destination switch. You must bind the FC tunnel to an ST port in the source switch and map the same FC tunnel to an SD port in the destination switch. After the mapping and binding are configured, the FC tunnel is referred to as an RSPAN tunnel, as shown in Figure 11-7.

Remote Network Monitoring (RMON) is an Internet Engineering Task Force (IETF) standard monitoring specification that allows various network agents and console systems to exchange network monitoring data. RMON is disabled by default, and no events or alarms are configured in the switch. You can configure your RMON alarms and events by using the CLI or an SNMP-compatible network management station to monitor Cisco MDS 9000 Family switches.

All switches in the Cisco MDS 9000 Family support the following RMON functions (defined in RFC 2819):

Alarm: Each alarm monitors a specific management information base (MIB) object for a specified interval. When the MIB object value exceeds a specified value (rising threshold), the alarm condition is set, and only one event is triggered regardless of how long the condition exists. When the MIB object value falls below a certain value (falling threshold), the alarm condition is cleared. This allows the alarm to trigger again when the rising threshold is crossed again.

Event: Determines the action to take when an event is triggered by an alarm. The action can be to generate a log entry, an SNMP trap, or both.

SPAN

The Switched Port Analyzer (SPAN) feature is supported by switches in the Cisco MDS 9000 Family. It monitors network traffic through a Fibre Channel interface. Traffic through any Fibre Channel interface can be replicated to a special port called the SPAN destination port (SD port). Any Fibre Channel port in a switch can be configured as an SD port. When an interface is in SD port mode, it cannot be used for normal data traffic. You can attach a Fibre Channel analyzer to the SD port to monitor SPAN traffic, as shown in Figure 11-3.

Figure 11-3 SPAN Transmission

SD ports do not receive frames; they only transmit a copy of the SPAN source traffic. The SPAN feature is nonintrusive and does not affect switching of network traffic for any SPAN source ports.

SPAN sources refer to the interfaces from which traffic can be monitored. You can also specify VSAN as a SPAN source, in which case, all supported interfaces in the specified VSAN are included as SPAN sources. When a VSAN as a source is specified, all physical ports and port channels in that VSAN are included as SPAN sources. A TE port is included only when the port VSAN of the TE port matches the source VSAN. A TE port is excluded even if the configured allowed VSAN list may have the source VSAN, but the port VSAN is different. You cannot configure source interfaces (physical interfaces, port channels, or sup-fc interfaces) and source VSANs in the same SPAN session.

You can choose the SPAN traffic in the ingress direction, the egress direction, or both directions for any source interface:

Ingress source (Rx): Traffic entering the switch fabric through this source interface is spanned, or copied, to the SD port, as shown in Figure 11-4.

Figure 11-4 SPAN Traffic from the Ingress Direction

Egress source (Tx): Traffic exiting the switch fabric through this source interface is spanned, or copied, to the SD port, as shown in Figure 11-5.

Figure 11-5 SPAN Traffic from the Egress Direction

The SPAN feature is available for the following interface types:

Physical ports: These port types include F, FL, TE, E, and TL ports.

System management features are used to monitor and manage a switch using Cisco MDS NX-OS software. These features are described next.

System Messages

System messages are monitored remotely by accessing the switch through Telnet, SSH, or the console port, or by viewing the logs on a system message logging server. The system message logging software saves the messages in a log file or directs the messages to other devices. This feature has the following capabilities:

Provides logging information for monitoring and troubleshooting

Allows the user to select the types of captured logging information

Allows the user to select the destination server to forward the captured logging information

By default, the switch logs normal but significant system messages to a log file and sends these messages to the system console. You can specify which system messages should be saved based on the type of facility and the severity level. Messages are time-stamped to enhance real-time debugging and management.

You can access the logged system messages using the CLI or by saving them to a correctly configured system message logging server. The switch software saves system messages in a file that can save up to 1200 entries.

Log messages are not saved across system reboots. However, a maximum of 100 log messages with a severity level of critical and below (levels 0, 1, and 2) is saved in NVRAM.

Call Home

Call Home provides email-based notification of critical system events. A versatile range of message formats is available for optimal compatibility with pager services, standard email, or XML-based automated parsing applications. Common uses of this feature may include direct paging to a network support engineer, email notification to a Network Operations Center, and utilization of Cisco Smart Call Home services for direct case generation with the Technical Assistance Center.

The Call Home functionality is available directly through the Cisco MDS 9000 Series switches and the Cisco Nexus 5000 Series switches. It provides multiple Call Home messages, each with separate potential destinations. You can define your own destination profiles in addition to predefined profiles; you also can configure up to 50 email addresses for each destination profile. Flexible message delivery and format options make it easy to integrate specific support requirements.

The Call Home feature offers the following advantages:

A fixed set of predefined alerts for trigger events on the switch.

Automatic execution and attachment of relevant command output.

Multiple message format options:

Short Text: Suitable for pagers or printed reports.

Plain Text: Full formatted message information suitable for human reading.

XML: Matching readable format using Extensible Markup Language (XML) and document type definitions (DTDs) named Messaging Markup Language (MML). The XML format enables communication with the Cisco Systems Technical Assistance Center.

Multiple concurrent message destinations. You can configure up to 50 email destination addresses for each destination profile.

Multiple message categories including system, environment, switching module hardware, supervisor module, hardware, inventory, syslog, RMON, and test.

Secure messages transport directly from your device or through an HTTP proxy server or a downloadable transport gateway (TG). You can use a TG aggregation point to support multiple devices or in cases where security requires that your devices not be connected directly to the Internet.

Smart Call Home is a component of Cisco SMARTnet Service that offers proactive diagnostics, real-time alerts, and personalized web-based reports on selected Cisco devices. Smart Call Home provides fast resolution of system problems by analyzing Call Home messages sent from your devices and providing a direct notification path to Cisco customer support.

Embedded Event Manager

The Embedded Event Manager (EEM) monitors events that occur on your device and takes action to recover or troubleshoot these events, based on your configuration. EEM consists of three major components:

Event statements: Events to monitor from Cisco NX-OS component that may require some action, workaround, or notification.

Action statements: An action that the EEM can take, such as sending an email or disabling an interface, to recover from an event.

Policies: An event paired with one or more actions to troubleshoot or recover from the event.

To learn more about EEM configuration, refer to Chapter 16, “Automation and Scripting Tools.”

Switches and directors in the Cisco MDS 9000 Series contain several electrical programmable logical devices (EPLDs) that provide hardware functionalities in all of the modules. Cisco periodically provides EPLD image upgrades to include enhanced hardware functionality or to resolve known issues.

EPLD images are released as part of a Cisco MDS NX-OS release. Therefore, the EPLD images have a version number that matches the Cisco MDS NX-OS release they are part of.

An EPLD image is a package containing updates for each type of EPLD. Because EPLD changes are infrequent, an EPLD image may contain new updates for only some EPLDs. The remaining EPLD updates will be the same version as the previous EPLD image. You do not need to update your EPLD images unless otherwise advised by the Technical Assistance Center (TAC).

You can use the show version module slot epld command to view all current EPLD versions on a specified module, as shown in Example 11-2.

Example 11-2 Displaying Current EPLD Versions for a Module

switch# show version module 1 epld

EPLD Device Version
—————————————
Power Manager 1.003
IO SPI 1.003
IO SPI 2 1.002

You can use the show version fan slot epld command to view all current EPLD versions on a specific fan module. Example 11-3 shows the currently installed EPLD versions on a fan module.

Example 11-3 Displaying Current EPLD Versions for a Fan Module

switch# show version fan 1 epld

EPLD Device Version
—————————————
Fan Controller (1) 0.006
Fan Controller (2) 0.006

To view all current EPLD versions on a fabric module, you can use the show version xbar slot epld command. Example 11-4 shows the currently installed EPLD versions on a fabric module.

Example 11-4 Displaying Current EPLD Versions for a Fabric Module

switch# show version xbar 2 epld

EPLD Device Version
—————————————
Power Manager 1.002

You can use the show version epld uri command to view all the updates contained in an EPLD package. Example 11-5 shows the available EPLD versions.

Example 11-5 Displaying EPLD Versions in an EPLD Image for a Cisco MDS 9700 Series Switch

switch# show version epld bootflash:m9000-pkg2.8.2.1.epld

Retrieving EPLD versions… Please wait.

EPLD image file 8.2.1 built on Wed Sep 27 04:43:59 2017

Module Type Model EPLD Device Version
—————————————————————————–
Supervisor Module-3 DS-X97-SF1-K9 Power Manager SPI 20.000

Supervisor Module-3 DS-X97-SF1E-K9 Power Manager SPI 20.000

Fabric Module 1 DS-X9718-FAB1 Power Manager 1.002

Fabric Module 1 DS-X9710-FAB1 Power Manager 1.003

Fabric Module 1 DS-X9706-FAB1 Power Manager 1.002

Fabric Module 2 DS-X9710-FAB-2 Power Manager 0.001

16 Gbps Advanced FC Module DS-X9448-768K9 Power Manager 8.000
16 Gbps Advanced FC Module DS-X9448-768K9 IO 15.000
10 Gbps FCoE Module DS-X9848-480K9 Power Manager 0.006
10 Gbps FCoE Module DS-X9848-480K9 IO 0.005

40 Gbps FCoE Module DS-X9824-960K9 Power Manager SPI 1.005
40 Gbps FCoE Module DS-X9824-960K9 IO SPI 2 0.028
40 Gbps FCoE Module DS-X9824-960K9 IO SPI 0.031

Fan DS-C9718-FAN Fan Controller (1) 0.006
Fan DS-C9718-FAN Fan Controller (2) 0.006
Fan DS-C9710-FAN Fan Controller (1) 0.006
Fan DS-C9710-FAN Fan Controller (2) 0.006

Fan DS-C9706-FAN Fan Controller (1) 0.006
Fan DS-C9706-FAN Fan Controller (2) 0.006

2/4/8/16G Fabric Switch DS-C9396S-K9 IO SPI 2 1.002
2/4/8/16G Fabric Switch DS-C9396S-K9 IO SPI 1.003

32 Gbps Advanced FC Module DS-X9648-1536K9 Power Manager SPI 0.002
32 Gbps Advanced FC Module DS-X9648-1536K9 SFP SPI 0.005
32 Gbps Advanced FC Module DS-X9648-1536K9 IO SPI 0.038

4/8/16/32G 1 RU Fabric Switch DS-C9132T IO SPI 2 0.022
4/8/16/32G 1 RU Fabric Switch DS-C9132T MI IO SPI 0.017
4/8/16/32G 1 RU Fabric Switch DS-C9132T LEM IO SPI 0.0

EPLDs can be installed, upgraded, or downgraded using CLI commands. Installing a module EPLD update includes the updating of both supervisors and switching modules. At the end of this process, the target module is reloaded. For switching modules, this disrupts traffic on all ports of the module for the duration of the reload. You can use the install all epld uri parallel module slot command to update EPLD images for a module in the Cisco MDS 9700 Series switches, as shown in Example 11-6.

Example 11-6 Updating Module EPLDs on a Cisco MDS 9700 Series Switch

switch# install all epld bootflash:m9000-pkg2.8.2.1.epld parallel module 6

WARNING!!!: Executing the “install all epld” command
may result in multiple modules going offline and
affect redundant links.


It is strongly recommended to use one of the following
when EPLD upgrade is attempted on a system carrying
production traffic.
1) “install module <mod#> epld”
2) “install all epld <uri> parallel module <mod#>”
where <mod#> is on a single module


For EPLD upgrade best practices, please refer to the link-

http://www.cisco.com/en/US/docs/switches/datacenter/
sw/best_practices/cli_mgmt_guide/epld_upgrade.html
 Do you want to continue (y/n) ? [n] y
Copy complete, now saving to disk (please wait)…

EPLD image signature verification passed
 Compatibility check:
Module Type Upgradable Impact      Reason
—— —- ———- ———– —————–
6      SUP   Yes        disruptive  Module Upgradable

Retrieving EPLD versions… Please wait.

Images will be upgraded according to following table:
Module Type EPLD               Running-Version New-Version Upg-Required
—— —- —————— ————— ———– ————-
6      SUP  Power Manager SPI  18.000          19.000      Yes

The above modules require upgrade.
Do you want to continue (y/n) ? [n] y

Starting Module 6 EPLD Upgrade
Module 6 : Power Manager SPI [Upgrade Started ]
Module 6 : Power Manager SPI [Erasing ] : 100.00%
Module 6 : Power Manager SPI [Programming ] : 100.00% (6020818 of 6020818 total
bytes)


Module 6 Upgrade Done.

Waiting for Module 6 to come online.


Module 6 EPLD upgrade is successful.

EPLD Upgrade Completed.
Module Type Upgrade-Result
—— —- ————–
6      SUP     Succes

You can use the install module slot epld uri command to update EPLD images for a module in the Cisco MDS switches except the Cisco MDS 9700 Series switches, as shown in Example 11-7. If the module number specified in the install module slot epld uri command is not present, the update is aborted. If the module is present but not online, the module state is reported and the switch software prompts you to continue. If you continue, the module is brought online, and all the EPLDs on the module are updated, regardless of whether or not they require it.