Cisco Nexus 9000 Series NX-OS Release Notes, Release 9.2(4)
Use this document with documents listed in Related Documentation.
Table 1 shows the online change history of this document.
June 24, 2020 |
Removed CSCvp30516 from the Open Caveats. |
January 27, 2020 |
Updated the Upgrade Instructions. |
January 26, 2020 |
Added CSCvc95008 to Known Behaviors. |
January 7, 2020 |
Added CSCvq58618 to Resolved Caveats. |
November 15, 2019 |
Updated Limitations section for breakout issue. |
October 6, 2019 |
Updated Transceiver Module Group URL. |
August 23, 2019 |
Moved the Traffic Storm Control feature from Security to Layer 2 features. |
August 20, 2019 |
Known Behaviors—Cisco NX-OS Release 9.2(4)
Obtaining Documentation and Submitting a Service Request
The Cisco Nexus 3000 Series switches, which includes Cisco Nexus 3100, 3200, 3400-S, 3500, and 3600 platform switches, and Cisco Nexus 9300 and 9500 platform switches run on the same binary image, also called the “unified” image.
Cisco NX-OS Release 9.2(1) is the first release that adopts unified version numbering. As more platforms have been added, there is no need to have a “platform” designator as used in the past.
An example of a previous release number is: 7.0(3)I7(4). In this format, the ‘I’ is the platform designator.
Moving forward for the previously identified platforms, we will be adopting the simplified 3-letter versioning scheme. For example, a release with X.Y(Z) would mean:
X – Unified release major
Y – Major / Minor release
Z – Maintenance release (MR)
Where the Z = 1 is always the first FCS release of a Major/Minor release.
Note: In order to accommodate upgrade compatibility from an older software version that is expecting a platform designator, when the install all command is entered or the show install all impact command is entered, the version string appears as 9.2(1)I9(1). The “I9(1)” portion of the string can be safely ignored. It will later appear as 9.2(1).
Temporary licenses with an expiry date are available for evaluation and lab use purposes. They are strictly not allowed to be used in production. Please use a permanent or subscription license that has been purchased through Cisco for production purposes.
When you downgrade from Cisco NX-OS Release 9.2(4) to an earlier release, the features that use the ACI+NX-OS Essentials, Advantage, and add-on licenses or the Hardware Streaming Telemetry license continue to work in honor mode in the downgraded version. In addition, the output of the how license usage command continues to include entries for these unsupported licenses.
For more information, see the Cisco NX-OS Licensing Guide.
This section includes the following sections:
Table 2 Cisco Nexus 9500 Switches
Table 3 Cisco Nexus 9500 Cloud Scale Line Cards
Table 4 Cisco Nexus 9500 R-Series Line Cards
Table 5 Cisco Nexus 9500 Classic Line Cards
Table 6 Cisco Nexus 9500 Cloud Scale Fabric Modules
Table 7 Cisco Nexus 9500 R-Series Fabric Modules
Table 8 Cisco Nexus 9500 Fabric Modules
Table 9 Cisco Nexus 9500 Fabric Module Blanks with Power Connector
Table 10 Cisco Nexus 9500 Supervisor Modules
Table 11 Cisco Nexus 9500 System Controller
Table 12 Cisco Nexus 9500 Fans and Fan Trays
Table 13 Cisco Nexus 9500 Power Supplies
Table 14 Cisco Nexus 9200 and 9300 Fans and Fan Trays
Table 15 Cisco Nexus 9200 and 9300 Power Supplies
Table 16 Cisco Nexus 9200 and 9300 Switches
Table 17 Cisco Nexus 9000 Series Uplink Modules
Table 2 Cisco Nexus 9500 Switches
Description |
|
N9K-C9504 |
7.1-RU modular switch with slots for up to 4 line cards in addition to two supervisors, 2 system controllers, 3 to 6 fabric modules, 3 fan trays, and up to 4 power supplies. |
N9K-C9508 |
13-RU modular switch with slots for up to 8 line cards in addition to two supervisors, 2 system controllers, 3 to 6 fabric modules, 3 fan trays, and up to 8 power supplies. |
N9K-C9516 |
21-RU modular switch with slots for up to 16 line cards in addition to two supervisors, 2 system controllers, 3 to 6 fabric modules, 3 fan trays, and up to 10 power supplies. |
Table 3 Cisco Nexus 9500 Cloud Scale Line Cards
Product ID |
Description |
Maximum Quantity |
||
Cisco Nexus 9504 |
Cisco Nexus 9508 |
Cisco Nexus 9516 |
||
N9K-X9736C-FX |
Cisco Nexus 9500 36-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
16 |
N9K-X9732C-FX |
Cisco Nexus 9500 32-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
16 |
N9K-X9732C-EX |
Cisco Nexus 9500 32-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
16 |
N9K-X9736C-EX |
Cisco Nexus 9500 36-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
16 |
N9K-X9788TC-FX |
Cisco Nexus 9500 48-port 1/10-G BASE-T Ethernet and 4-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
16 |
N9K-X97160YC-EX |
Cisco Nexus 9500 48-port 10/25-Gigabit Ethernet SFP28 and 4-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
16 |
Table 4 Cisco Nexus 9500 R-Series Line Cards
Product ID |
Description |
Maximum Quantity |
|
Cisco Nexus 9504 |
Cisco Nexus 9508 |
||
N9K-X9636C-R |
Cisco Nexus 9500 36-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
N9K-X9636C-RX |
Cisco Nexus 9500 32-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
N9K-X9636Q-R |
Cisco Nexus 9500 36-port 40 Gigabit Ethernet QSFP line card |
4 |
8 |
N9K-X96136YC-R |
Cisco Nexus 9500 16-port 1/10 Gigabit, 32-port 10/25 Gigabit, and 4-port 40/100 Gigabit Ethernet line card |
4 |
8 |
Table 5 Cisco Nexus 9500 Classic Line Cards
Product ID |
Description |
Maximum Quantity |
||
Cisco Nexus 9504 |
Cisco Nexus 9508 |
Cisco Nexus 9516 |
||
N9K-X9408C-CFP2 |
Line card with 8 100 Gigabit CFP2 ports |
4 |
8 |
16 |
N9K-X9432C-S |
Cisco Nexus 9500 32-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
N/A |
N9K-X9432PQ |
Cisco Nexus 9500 32-port 40 Gigabit Ethernet QSFP+ line card |
4 |
8 |
16 |
N9K-X9636PQ |
Cisco Nexus 9500 36-port 40 Gigabit Ethernet QSFP+ line card |
4 |
8 |
N/A |
N9K-X9464PX |
Cisco Nexus 9500 48 1/10-Gigabit SFP+ and 4-port 40-Gigabit Ethernet QSFP+ line card |
4 |
8 |
16 |
N9K-X9464TX |
Cisco Nexus 9500 48 port 1/10-Gigabit BASE-T Ethernet and 4-port 40-Gigabit Ethernet QSFP+ line card |
4 |
8 |
16 |
N9K-X9464TX2 |
Cisco Nexus 9500 48 port 1/10-Gigabit BASE-T Ethernet and 4-port 40-Gigabit Ethernet QSFP+ line card |
4 |
8 |
16 |
N9K-X9536PQ |
Cisco Nexus 9500 36-port 40 Gigabit Ethernet QSFP+ line card |
4 |
8 |
16 |
N9K-X9564PX |
Cisco Nexus 9500 48 1/10-Gigabit SFP+ and 4 port 40-Gigabit Ethernet QSFP+ line card |
4 |
8 |
16 |
N9K-X9564TX |
Cisco Nexus 9500 48 port 1/10-Gigabit BASE-T Ethernet and 4 port 40-Gigabit Ethernet QSFP+ line card |
4 |
8 |
16 |
Table 6 Cisco Nexus 9500 Cloud Scale Fabric Modules
Product ID |
Description |
Minimum |
Maximum |
N9K-C9504-FM-E |
Cisco Nexus 9504 100-Gigabit cloud scale fabric module |
4 |
5 |
N9K-C9508-FM-E |
Cisco Nexus 9508 100-Gigabit cloud scale fabric module |
4 |
5 |
N9K-C9508-FM-E2 |
Cisco Nexus 9508 100-Gigabit cloud scale fabric module |
4 |
5 |
N9K-C9516-FM-E |
Cisco Nexus 9516 50-Gigabit cloud scale fabric module |
4 |
5 |
N9K-C9516-FM-E2
|
Cisco Nexus 9516 100-Gigabit cloud scale fabric module |
4 |
5 |
Table 7 Cisco Nexus 9500 R-Series Fabric Modules
Product ID |
Description |
Minimum |
Maximum |
N9K-C9504-FM-R |
Cisco Nexus 9504 100-Gigabit R-Series fabric module |
4 |
6 |
N9K-C9508-FM-R |
Cisco Nexus 9508 100-Gigabit R-Series fabric module |
4 |
6 |
Table 8 Cisco Nexus 9500 Fabric Modules
Product ID |
Description |
Minimum |
Maximum |
N9K-C9504-FM |
Cisco Nexus 9504 40-Gigabit fabric module |
3 |
6 |
N9K-C9508-FM |
Cisco Nexus 9508 40-Gigabit fabric module |
3 |
6 |
N9K-C9516-FM |
Cisco Nexus 9516 40-Gigabit fabric module |
3 |
6 |
N9K-C9504-FM-S |
Cisco Nexus 9504 100-Gigabit fabric module |
4 |
4 |
N9K-C9508-FM-S |
Cisco Nexus 9508 100-Gigabit fabric module |
4 |
4 |
Table 9 Cisco Nexus 9500 Fabric Module Blanks with Power Connector
Product ID |
Description |
Minimum |
Maximum |
N9K-C9508-FM-Z |
Cisco Nexus 9508 Fabric blank with Fan Tray Power Connector module |
N/A |
2 |
N9K-C9516-FM-Z |
Cisco Nexus 9516 Fabric blank with Fan Tray Power Connector module |
N/A |
2 |
Table 10 Cisco Nexus 9500 Supervisor Modules
Supervisor |
Description |
Quantity |
N9K-SUP-A |
1.8-GHz supervisor module with 4 cores, 4 threads, and 16 GB of memory |
2 |
N9K-SUP-A+ |
1.8-GHz supervisor module with 4 cores, 8 threads, and 16 GB of memory |
2 |
N9K-SUP-B |
2.2-GHz supervisor module with 6 cores, 12 threads, and 24 GB of memory |
2 |
N9K-SUP-B+ |
1.9-GHz supervisor module with 6 cores, 12 threads, and 32 GB of memory |
2 |
NOTE: N9K-SUP-A and N9K-SUP-A+ are not supported on Cisco Nexus 9504 and 9508 switches with -R line cards.
Table 11 Cisco Nexus 9500 System Controller
Product ID |
Description |
Quantity |
N9K-SC-A |
Cisco Nexus 9500 Platform System Controller Module |
2 |
Table 12 Cisco Nexus 9500 Fans and Fan Trays
Product ID |
Description |
Quantity |
N9K-C9504-FAN |
Fan tray for 4-slot modular chassis |
3 |
N9K-C9508-FAN |
Fan tray for 8-slot modular chassis |
3 |
N9K-C9516-FAN |
Fan tray for 16-slot modular chassis |
3 |
Table 13 Cisco Nexus 9500 Power Supplies
Product ID |
Description |
Quantity |
Cisco Nexus Switches |
N9K-PAC-3000W-B |
3 KW AC power supply |
Up to 4 |
Cisco Nexus 9504 |
N9K-PDC-3000W-B |
3 KW DC power supply |
Up to 4 |
Cisco Nexus 9504 |
N9K-PUV-3000W-B |
3 KW Universal AC/DC power supply |
Up to 4 |
Cisco Nexus 9504 |
N9K-PUV2-3000W-B |
3.15-KW Dual Input Universal AC/DC Power Supply |
Up to 4 |
Cisco Nexus 9504 |
Table 14 Cisco Nexus 9200 and 9300 Fans and Fan Trays
Product ID |
Description |
Quantity |
Cisco Nexus Switches |
|
N9K-C9300-FAN1 |
Fan 1 module with port-side intake airflow (burgundy coloring) |
3 |
9396PX (early versions) |
|
N9K-C9300-FAN1-B |
Fan 1 module with port-side exhaust airflow (blue coloring) |
3 |
9396PX (early versions) |
|
N9K-C9300-FAN2 |
Fan 2 module with port-side intake airflow (burgundy coloring) |
3 |
93128TX |
9396PX |
N9K-C9300-FAN2-B |
Fan 2 module with port-side exhaust airflow (blue coloring) |
3 |
93128TX |
9396PX |
N9K-C9300-FAN3 |
Fan 3 module with port-side intake airflow (burgundy coloring) |
3 |
92304QC |
93120TX |
N9K-C9300-FAN3-B |
Fan 3 module with port-side exhaust airflow (blue coloring) |
3 |
92304QC |
93120TX |
NXA-FAN-160CFM-PE |
Fan module with port-side exhaust airflow (blue coloring) |
3 |
9364C |
|
NXA-FAN-160CFM-PI |
Fan module with port-side intake airflow (burgundy coloring) |
3 |
9364C |
|
NXA-FAN-30CFM-B |
Fan module with port-side intake airflow (burgundy coloring) |
3 |
92160YC-X |
9332PQ 9348GC-FXP 9372PX-E 9372TX-E |
NXA-FAN-30CFM-F |
Fan module with port-side exhaust airflow (blue coloring) |
3 |
92160YC-X |
9332PQ 9348GC-FXP 9372PX-E 9372TX-E |
NXA-FAN-35CFM-PE |
Fan module with port-side exhaust airflow (blue coloring) |
4 |
92300YC |
9332C |
NXA-FAN-35CFM-PI |
Fan module with port-side intake airflow (burgundy coloring) |
4 |
92300YC |
9332C |
NXA-FAN-65CFM-PE |
Fan module with port-side exhaust airflow (blue coloring) |
3 |
93240YC-FX2 |
9336C-FX2 |
NXA-FAN-65CFM-PI |
Fan module with port-side exhaust airflow (burgundy coloring) |
3 |
93240YC-FX2 |
9336C-FX2 |
Table 15 Cisco Nexus 9200 and 9300 Power Supplies
Product ID |
Description |
Quantity |
Cisco Nexus Switches |
|
N9K-PAC-650W |
650-W AC power supply with port-side intake (burgundy coloring) |
2 |
9332PQ 9372TX |
9372TX-E |
N9K-PAC-650W-B |
650-W AC power supply with port-side exhaust (blue coloring) |
2 |
9332PQ 9372TX |
9372TX-E |
N9K-PAC-1200W |
1200-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
93120TX |
|
N9K-PAC-1200W-B |
1200-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
93120TX |
|
N9K-PUV-1200W |
3000-W Universal AC/DC power supply with bidirectional airflow (white coloring) |
2 |
92160YC-X |
93120TX |
NXA-PAC-350W-PE |
350-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
9348GC-FXP |
|
NXA-PAC-350W-PI |
350-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
9348GC-FXP |
|
NXA-PAC-500W-PE |
500-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
93108TC-EX |
93180YC-EX |
NXA-PAC-500W-PI |
500-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
93108TC-EX |
93180YC-EX |
NXA-PAC-650W-PE |
650-W power supply with port-side exhaust (blue coloring) |
2 |
92160YC-X |
92304QC |
NXA-PAC-650W-PI |
650-W power supply with port-side intake (burgundy coloring) |
2 |
92160YC-X |
92304QC |
NXA-PAC-1100W-PE |
1100-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
9348GC-FXP |
|
NXA-PAC-1100W-PE2 |
1100-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
93240YC-FX2 9332C |
9336C-FX2 |
NXA-PAC-1100W-PI |
1100-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
9348GC-FXP |
|
NXA-PAC-1100W-PI2 |
1100-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
93240YC-FX2 9332C |
9336C-FX2 |
NXA-PDC-1100W-PE |
1100-W DC power supply with port-side exhaust airflow (blue coloring) |
2 |
93240YC-FX2 |
9332C 9336C-FX2 |
NXA-PDC-1100W-PI |
1100-W DC power supply with port-side intake airflow (burgundy coloring) |
2 |
93240YC-FX2 |
9332C 9336C-FX2 |
NXA-PHV-1100W-PE |
1100-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
93240YC-FX2 |
9336C-FX2 |
NXA-PHV-1100W-PI |
1100-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
93240YC-FX2 |
9336C-FX2 |
NXA-PAC-1200W-PE |
1200-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
9272Q |
9364C |
NXA-PAC-1200W-PI |
1200-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
9272Q |
9364C |
NXA-PDC-440W-PI
|
440-W DC power supply with port-side intake airflow (burgundy coloring) |
2 |
9348GC-FXP |
|
NXA-PDC-930W-PE |
930-W DC power supply with port-side exhaust airflow (blue coloring) |
2 |
93108TC-FX |
93180YC-FX |
NXA-PDC-930W-PI |
930-W DC power supply with port-side intake airflow (burgundy coloring) |
2 |
93108TC-FX |
93180YC-FX |
NXA-PDC-1100W-PE |
1100-W DC power supply with port-side exhaust airflow (blue coloring) |
2 |
93240YC-FX |
|
NXA-PHV-1100W-PE |
1100-W DC power supply with port-side exhaust airflow (blue coloring) |
2 |
93240YC-FX |
|
UCS-PSU-6332-DC |
930-W DC power supply with port-side exhaust (gray coloring) |
2 |
92160YC-X |
9332PQ 9372TX |
UCSC-PSU-930WDC |
930-W DC power supply with port-side intake (green coloring) |
2 |
92160YC-X |
9332PQ 9372TX |
Table 16 Cisco Nexus 9200 and 9300 Switches
Cisco Nexus Switch |
Description |
N9K-C92160YC-X |
1-RU Top-of-Rack switch with 48 10-/25-Gigabit SFP+ ports and 6 40-Gigabit QSFP+ ports (4 of these ports support 100-Gigabit QSFP28 optics). |
N9K-C92300YC |
1.5-RU Top-of-Rack switch with 48 10-/25-Gigabit SFP28 ports and 18 fixed 40-/100-Gigabit QSFP28 ports. |
N9K-C92304QC |
2-RU Top-of-Rack switch with 56 40-Gigabit Ethernet QSFP+ ports (16 of these ports support 4x10 breakout cables) and 8 100-Gigabit QSFP28 ports. |
N9K-C9236C |
1-RU Top-of-Rack switch with 36 40-/100-Gigabit QSFP28 ports (144 10-/25-Gigabit ports when using breakout cables) |
N9K-C9272Q |
2-RU Top-of-Rack switch with 72 40-Gigabit Ethernet QSFP+ ports (35 of these ports also support 4x10 breakout cables for 140 10-Gigabit ports) |
N9K-C9332C |
1-RU fixed switch with 32 40/100-Gigabit QSFP28 ports and 2 fixed 1/10-Gigabit SFP+ ports. |
N9K-C9336C-FX2 |
1-RU switch with 36 40-/100-Gb Ethernet QSFP28 ports. |
N9K-C9364C |
2-RU Top-of-Rack switch with 64 40-/100-Gigabit QSFP28 ports and 2 1-/10-Gigabit SFP+ ports. - Ports 1 to 48 support 40/100-Gigabit speeds. |
N9K-C93108TC-EX |
1-RU Top-of-Rack switch with 48 10GBASE-T (copper) ports and 6 40-/100-Gigabit QSFP28 ports |
N9K-C93108TC-FX |
1-RU Top-of-Rack switch with 48 100M/1/10GBASE-T (copper) ports and 6 40-/100-Gigabit QSFP28 ports |
N9K-C93120TX |
2-RU Top-of-Rack switch with 96 1/10GBASE-T (copper) ports and 6 40-Gigabit QSFP+ ports |
N9K-C93128TX |
3-RU Top-of-Rack switch with 96 1/10GBASE-T (copper) ports and an uplink module up to 8 40-Gigabit QSFP+ ports |
N9K-C93180LC-EX |
1-RU Top-of-Rack switch with 24 40-/50-Gigabit QSFP+ downlink ports and 6 40/100-Gigabit uplink ports. You can configure 18 downlink ports as 100-Gigabit QSFP28 ports or as 10-Gigabit SFP+ ports (using breakout cables) |
N9K-C93180YC-EX |
1-RU Top-of-Rack switch with 48 10-/25-Gigabit SFP28 fiber ports and 6 40-/100-Gigabit QSFP28 ports |
N9K-C93180YC-FX |
1-RU Top-of-Rack switch with 10-/25-/32-Gigabit Ethernet/FC ports and 6 40-/100-Gigabit QSFP28 ports. You can configure the 48 ports as 1/10/25-Gigabit Ethernet ports or as FCoE ports or as 8-/16-/32-Gigabit Fibre Channel ports. |
N9K-C93240YC-FX2 |
1.2-RU Top-of-Rack switch with 48 10-/25-Gigabit SFP28 fiber ports and 12 40-/100-Gigabit Ethernet QSFP28 ports. |
N9K-C9332PQ |
1-RU switch with 32 40-Gigabit Ethernet QSFP+ ports (26 ports support 4x10 breakout cables and 6 ports support QSFP-to-SFP adapters) |
N9K-C9348GC-FXP |
Nexus 9300 with 48p 100M/1 G, 4p 10/25 G SFP+ and 2p 100 G QSFP |
N9K-C9372PX |
1-RU Top-of-Rack switch with 48 1-/10-Gigabit SFP+ ports and 6 40-Gigabit QSFP+ ports |
N9K-C9372PX-E |
An enhanced version of the Cisco Nexus 9372PX-E switch. |
N9K-C9372TX |
1-RU Top-of-Rack switch with 48 1-/10GBASE-T (copper) ports and 6 40-Gigabit QSFP+ ports |
N9K-C9372TX-E |
An enhanced version of the Cisco Nexus 9372TX-E switch. |
N9K-C9396PX |
2-RU Top-of-Rack switch with 48 1-/10-Gigabit Ethernet SFP+ ports and an uplink module with up to 12 40-Gigabit QSFP+ ports |
N9K-C9396TX |
2-RU Top-of-Rack switch with 48 1/10GBASE-T (copper) ports and an uplink module with up to 12 40-Gigabit QSFP+ ports |
Table 17 Cisco Nexus 9000 Series Uplink Modules
Product ID |
Description |
N9K-M4PC-CFP2 |
Cisco Nexus 9300 uplink module with 4 100-Gigabit Ethernet CFP2 ports. For the Cisco Nexus 93128TX switch, only two of the ports are active. For the Cisco Nexus 9396PX and 9396TX switches, all four ports are active. |
N9K-M6PQ |
Cisco Nexus 9300 uplink module with 6 40-Gigabit Ethernet QSFP+ ports for the Cisco Nexus 9396PX, 9396TX, and 93128TX switches. |
N9K-M6PQ-E |
An enhanced version of the Cisco Nexus N9K-M6PQ uplink module. |
N9K-M12PQ |
Cisco Nexus 9300 uplink module with 12 40-Gigabit Ethernet QSPF+ ports. |
To determine which transceivers and cables are supported by this switch, see the Transceiver Module (TMG) Compatibility Matrix.
To see the transceiver specifications and installation information, see https://www.cisco.com/c/en/us/support/interfaces-modules/transceiver-modules/products-installation-guides-list.html.
Full FEX module support has been added for the following switches:
■ N9K-C9336C-FX2
■ N9K-C93108TC-FX
■ N9K-C93180YC-FX
■ N9K-C93240YC-FX2
For more information, see the Cisco Nexus 9000 Series Switch FEX Support page.
■ Cisco Nexus 9300 platform switches do not support FEXs on uplink modules (ALE).
■ Beginning with Cisco NX-OS Release 9.2(1), straight-through FEX support is added to Cisco Nexus 93240YC-FX2 and 9336C-FX2 switches.
■ Active-Active FEX and straight-through FEX are not supported on the Cisco Nexus 9348GC-FXP switch.
■ For FEX HIF port channels, enable the STP port type edge using the spanning tree port type edge [trunk] command.
This section lists the following topics:
■ New Hardware Features in Cisco NX-OS Release 9.2(4)
■ New Software Features in Cisco NX-OS Release 9.2(4)
No new hardware for Cisco NX-OS Release 9.2(4).
Cisco NX-OS Release 9.2(4) supports the following new software features:
■ Line Card Support: Added support for the N9K-X9636C-R, N9K-X9636Q-R, N9K-X9636C-RX and N9K-X96136YC-R line cards.
■ Fabric Module Support: Added support for the N9K-C9508-FM-R and N9K-C9504-FM-R fabric modules.
■ Scale monitoring has been expanded to cover the following four technology groups:
o Layer 2 switching
o Multicast routing
o Unicast routing
o VXLAN
For more information, see the Cisco Nexus 9000 Series NX-OS iCAM Configuration Guide, 9.2(x).
Layer 2 Features
■ Traffic Storm Control: Support added for the Cisco Nexus 9500 platform switches with the N9K-X96136YC-R line card and N9K-C9504-FM-R fabric module.
For more information, see the Cisco Nexus 9000 Series Layer 2 Configuration Guide, Release 9.2(x).
Security Features
■ IP ACLs: Added the ability to identify traffic using TCP flags. This support is added to Cisco Nexus 9500 platform switches with N9K-X96136YC-R, N9K-X9636C-R, and N9K-X9636C-RX line cards and N9K-C9504-FM-R fabric module.
For more information, see the Cisco Nexus 9000 Series Security Configuration Guide, Release 9.2(x).
Note: All caveats listed in this document are those that were reported against the Cisco Nexus 9000 Series switches.
Cisco Nexus 9000 Series, Cisco Nexus 9500-R/Cisco Nexus-3600-R Series, Cisco Nexus 3000 Series, and Cisco Nexus 3500 Series are platforms that run on the unified software and binary. Since some caveats listed against these platforms could be applicable to the Cisco Nexus 3000 series platform too, we recommend that you review the list of caveats in the Release Notes of the other platforms for this release, to see if those are applicable to your network configuration.
This section includes the following topics:
■ Resolved Caveats—Cisco NX-OS Release 9.2(4)
■ Open Caveats—Cisco NX-OS Release 9.2(4)
■ Known Behaviors—Cisco NX-OS Release 9.2(4)
The following table lists the Resolved Caveats in Cisco NX-OS Release 9.2(4). Click the bug ID to access the Bug Search tool and see additional information about the bug.
Bug ID |
Description |
TACACS non blocking connect failed with error code 98 |
|
STP port type edge not working after upgrade to I7(x) in dual-homed FEX setup |
|
N9k/VXLAN Outer BD for Infra VLAN is programmed incorrectly causing packet forwarding failure |
|
Generate Syslog when buffers on Nexus 9000 exceed threshold values |
|
tahusd core seen multiple times on 2 switches |
|
tahusd crash on clear ip route * |
|
N9K-X9736C-FX QINQ wrong vlan TAG after poweroff/on module |
|
N9300 as PTP slave may experience high correction and MPD when connected to GM via L2 switch |
|
Service "interface-vlan" crashed |
|
N9K: MTS leak from SAP 175 (Ethpm SAP) to SAP 153 (Pixm App VDC Local SAP) |
|
Multicast traffic doesn't egress onto VPC peer-link for Nexus 9K with Cisco ASIC. |
|
vPC leaks 13 KB @ libqosmgr_mcec with show vpc consistency global |
|
cpmCPUMemoryFree return wrong value from /proc/meminfo. |
|
Safety check to avoid Kernel panic |
|
N9K BGP sessions unstable when TCP packets received from same source to multiple local addresses. |
|
Nexus 93180YC-FX : Link debounce timer not working as expected |
|
routes count mismatch between show ip route summary and show forwarding ipv4 route summary |
|
N9K flooding frames with DMAC of 0180.C200.0003 in VXLAN |
|
N9K-C9272Q:show inventory shows NXA-FAN-30CFM-B instead of N9K-C9300-FAN3 |
|
N9K-X9736C-FX's /35 and /36 ports not coming up with QSFP-100G-SR4-S |
|
Mac address is not advertised out in bgp EVPN when port-security is enabled. |
|
ISIS is calculating metric for IPv6 based on worse LSP |
|
N9K FEX HIF configuration frozen after disruptive upgrade |
|
Modular N9K With Cloudscale Asic May Not Fragment IP Traffic |
|
N9k-C93108TC-EX interface speed may become mismatched between switch and connected device |
|
Crash on N9K-C93180YC-EX when port-security is added in FEX port for |
|
HTTP GET sent too late in python shell |
|
N9k BGP - When changing export map on VRF, RT does not always update in EVPN AF |
|
N9K // Error ("Object doesn't exist") communicating with MTS_SAP_SPM w/ NAT config |
|
SSH - dcos_sshd: (non-sysmgr) crashes on authentication attempt. |
|
N9K (-EX/FX models) does not syslog by default when MAC learning is disabled |
|
Unable to install license ACI-SEC-XF/NXOS-AD-XF on Nexus C93180YC-FX with software 9.2(3)/9.2.3 |
|
Longevity: Kernel Panic - unable to handle kernel paging request in rwsem_get_owner |
|
BGP route may stuck at dampened state |
|
Default FEC should be "OFF" for any read in Eprom@192Byte as 0x18h |
|
BGP memory leak due to BMP server sending TCP zerowindow pkt |
|
"no lacp suspend-individual" - Port in individual state is still part of the PC - traffic is dropped |
|
system dot1q-tunnel transit - provider_bd & keep_inner_qtag bits not set in RWX for VXLAN vlans |
|
EIGRP neighborship over IPv6 link-local addressing scheme is not formed |
|
Inconsistency seen between ACLQOS software state reference count and ACLQOS PSS |
|
IGMP v2/v3 mix: shutdown igmpv2 receivers and igmpv3 receivers are also removed from mrib oifl |
|
LLFC pause received on PFC enabled port leads to CPU-PG buildup |
|
Nexus 9000:::Unable to bring up F mode san-port-channel or trunking between MDS and N9K |
|
Nexus 93180YC-EX crahes due to tahusd process during enhanced ISSU from 7.0(3)I7(5) to 7.0(3)I7(5a) |
|
Kernel panic reloads in inet6_lookup_listener |
|
Multicast traffic not forwarding after force arp delete on FX2 TORs |
|
Sub-millisecond drop on an OIF in case if anouter OIF is added/deleted |
|
SVI counters do not work on N9K-C93240YC-FX2 |
|
N9K: shows incorrect privilege level after change radius config |
|
N9K active SUP being pulled out slowly, cause chassis reset issue |
|
show system resources shows high memory usage |
|
PIM may not return from isolate mode after leaving maintenance mode |
|
VXLAN: Spine MAC address learned on Leaf's Layer3 interface |
|
N9K:T2: Selective qinq -Traffic fails on interface when port mode changes to trunk |
|
N9300 NAT acl breaks non NAT traffic due to label sharing with unrelated racl |
|
N9K switch may restart due to HAP reset on service tahusd after multiple port flaps |
|
100G interface on N9K running NXOS may fails to come up when its connected to switch running ACI |
|
patching.repo has been saved to .rpmstore leading to patch installation failure |
|
MRIB crashed with watchdog due to loop in txlist |
|
n9k generates LSA even when the interface fails to come up |
|
MPLS Labeled Traffic Not Forwarded By N9K-C9364C Which is VXLAN VTEP |
|
L2 IPv6 Multicast Dropped from RACL on SVI // set IPMCV6_ENABLE flag only when ipv6 pim is enabled |
|
N93180LX-EX : tahusd crash seen with QSA on port 32 on 7.0(3)I7(6) |
|
NVE loopback flaps up and down after reload in autorecovery scenario in 7.0.3.I7.6 |
|
pause frame received on N9K is identified as multicast and mac would be learned |
|
Snmpbulkwalk on csstHwInternalErrorInstTable shows memory leak on each iteration. |
|
Switch-profiles fail with add/remove vlan on trunk port-profile |
|
N9K STP port type is not correct for L2 access ports |
|
N9k crash in tahusd process due to interrupt |
|
FCoE source mac addr is zeros during rapid FDIC/FLOGI/LOGO |
|
N9K NX-OS 9.2(3) SNMPd Crash / MTS Queue Congestion When Doing GETBULK on entPhysicalEntry |
|
Transit device consuming VxLAN encapsulated and GRE(IP-in-IP) traffic not intended for itself. |
|
FD leak seen in URIB during "show routing hash" or "show routing vxlan-hash" failure scenarios |
|
Nexus N9K-C9236C reboots with a 'urib' core |
|
Archive back up configuration not working |
|
SNMP v3 information leaking vulnerability still found in 7.0.3.I7.6 |
|
Gen 1 N9K May Not Bring Link Up When Connected To 3rd Party NIC Following Link Flap |
|
TCP networking vulnerabilities in FreeBSD and Linux kernels(TCP_SACK) |
|
N9K : peer port flapping and new igmp join coming will cause port oversubscription |
|
N9k: FCOE traffic from NP uplinks has invalid source fcf mac of all zeros |
|
EOR/BL/FX - mcast traffic not correctly forwarded if OIF is on remote LC |
|
ipfib hap reset seen when consistency checker runs on MPLS links |
|
MPLS L3 VPN as Egress PE fails to POP labels when sending traffic to CE Router |
|
ebgp peer no advertise local-labeled-route template inheritance does not work after process restart |
|
PIP Tunnel Wrong VLAN Tag when adding VLAN with Ingress Replication EVPN |
|
`no snmp trap link-status` not removed by checkpoint rollback initiated from NX-API REST |
|
LLDP frame sent from n9k is not set as PSE device |
|
N9K snmpd signal 8 crash |
|
Configuring no mpls ip forwarding on one interface breaks the same interface on different module |
|
EPLD Upgrade failure on N9K-SUP-A |
|
prevent tac-pac running when the user is not network-admin |
|
NX BGP: md5 does not work if vrf name is more than 19 character |
|
"policyelem" process crash when configure n9k via NX-API REST |
The following table lists the open caveats in the Cisco NX-OS Release 9.2(4). Click the bug ID to access the Bug Search tool and see additional information about the bug.
OTM URIB Assert Error on Boot |
|
Storm control counters does not work on 9500-R and Nexus 3600 platforms |
|
OC ACL: delete ipv4 ace with hop-limit configs fails |
|
CRC seen on links with Dual speed BiDi & 40g BiDi optics. |
|
PTP High correction on slave when master have SVI which have IGMP Connected Group Membership |
|
ACL Stats - Packet hitting an ACE entry with log option will be counted twice |
|
vlan counters should display L3 counters info |
|
EOR/FX:FT latency max out issue started appearing |
|
Generate Error message for FHS policy, When lable are not available. |
|
CRC errors occur on the neighbor devices when connects QSFP-100G-LR4-S on N3K-C36180YC-R |
|
Need new CLI for setting configurable MAC UP timer |
|
Nexus 9300 - Block CLI to configure sub-interface with 40G uplink ports |
The following known behaviors are in this release:
Table 2 Known Behaviors in Cisco NX-OS Release 9.2(4)
Bug ID |
Description |
On Cisco Nexus 9300-EX, 9348GC-FXP, 93108TC-FX, 93180YC-FX, 9336C-FX2, and 93240YC-FX2 switches, when 802.1q EtherType has changed on an interface, the EtherType of all interfaces on the same slice will be changed to the configured value. This change is not persistent after a reload of the switch and will revert to the EtherType value of the last port on the slice. |
■ Release 9.2(4) brings in a new kernel and new processes.
■ Interface counter statistics are grouped together in the XML/JSON output. The output for the show interface-counters command in JSON format has changed/
■ NX-API does not support insecure HTTP by default.
■ NX-API does not support weak TLSv1 protocol by default.
■ Stronger ciphers are used in this release.
■ A new command, no service password-recovery is supported.
■ Only one version out of v4 and v6 versions of the uRPF command can be configured on an interface. If one version is configured, all the mode changes must be done by the same version. The other version is blocked on that interface. Cisco Nexus 9300-EX, 9300-FX, and 9300-FX2 platform switches do not have this limitation and you can configure v4 and v6 version of urpf cmd individually.
■ In the NX-API sandbox, whenever XML or JSON output is generated for the show run command or the show startup command, the output contains additional characters.
</nf:source> <============nf: is extra
<namespace> : extra characters are seen with XML and JSON from NX-API.
To perform a software upgrade, follow the installation instructions in the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.2(x).
o 9.2(2)
o 7.0(3)I7(4), 7.0(3)I7(5), 7.0(3)I7(5a), 7.0(3)I7(6), 7.0(3)I7(7)
Note: Enhanced ISSU to Cisco NX-OS Release 9.2(4) is not supported as there are kernel fixes that cannot take effect without reloading the underlying kernel.
■ When downgrading from the Cisco NX-OS Release 9.2(4) to earlier releases, make sure that the ACL TCAM usage for ingress features does exceed the allocated TCAM space in the absence of the label sharing feature. Label sharing is a new feature in Cisco NX-OS Release 9.2(4). Otherwise, interfaces with RACLs that could not fit in the TCAM will be disabled after the downgrade.
■ When upgrading from Cisco NX-OS Release 9.2(2) or earlier releases to Cisco NX-OS Release 9.2(4), you need to make sure that ingress RACL TCAM region is not more than 50% full. Otherwise, the atomic update feature will be enabled after the upgrade and interfaces with RACLs that exceed 50% of TCAM allocation will remain down.
■ When upgrading from Cisco NX-OS Releases 7.0(3)I4(8), 7.0(3)I5(3), and 7.0(3)I6(1) to Cisco NX-OS Release 9.2(4) results in a disruptive upgrade. If syncing images to standby SUP failed during the disruptive upgrade from Cisco NX-OS Releases 7.0(3)I4(8), 7.0(3)I5(3,) or 7.0(3)I6(1) to 9.2(4), you should manually copy the image to the standby SUP and perform the disruptive upgrade.
■ When upgrading to Cisco NX-OS Release to 9.2(4) from any release prior to 7.0(3)I2(3) an intermediate upgrade to 7.0(3)I4(x), 7.0(3)I5(x), 7.0(3)I6(x), or 7.0(3)I7(x) is required. We recommend using Cisco NX-OS Release 7.0(3)I4(8) or 7.0(3)I7(4) as the interim release to aid in a smooth migration. For further details, please refer to CSCvk66763.
■ When upgrading from Cisco NX-OS Release 7.0(3)I6(1) or 7.0(3)I7(1) to Cisco NX-OS Release 9.2(4), if the Cisco Nexus 9000 Series switches are running vPC and they are connected to an IOS-based switch via Layer 2 vPC, there is a likelihood that the Layer 2 port channel on the IOS side will become error disabled. The workaround is to disable the spanning-tree etherchannel guard misconfig command on the IOS switch before starting the upgrade process. Once both the Cisco Nexus 9000 Series switches are upgraded, you can re-enable the command. For more information, see defect CSCvg05807.
■ An upgrade performed via the install all command for Cisco NX-OS Release 7.0(3)I2(2b) to Release 9.2(4) might result in the VLANs being unable to be added to the existing FEX HIF trunk ports. To recover from this, the following steps should be performed after all FEXs have come online and the HIFs are operationally up:
1. Enter the copy run bootflash:fex_config_restore.cfg command at the prompt.
2. Enter the copy bootflash:fex_config_restore.cfg running-config echo-commands command at the prompt.
■ In Cisco NX-OS Release 7.0(3)I6(1) and earlier, performing an ASCII replay or running the copy file run command on a FEX HIF configuration requires manually reapplying the FEX configuration after the FEX comes back up.
■ When upgrading to Cisco NX-OS Release 9.2(4) from 7.0(3)I2(x) or before and running EVPN VXLAN configuration, an intermediate upgrade to 7.0(3)I4(x) or 7.0(3)I5(x) or 7.0(3)I6(x) is required. For further details, please refer to CSCvh02777.
■ An ISSU can be performed only from a Cisco NX-OS Release 7.0(3)I4(1) to a later image.
■ While performing an ISSU, VRRP and VRRPv3 displays the following messages:
For additional information, see the Cisco NX-OS ISSU Support application.
The following are the upgrade paths from previous 7.0(3)F3(x) releases:
■ Release 7.0(3)F3(x) -> Release 7.0(3)F3(4) -> Release 9.2(4)
NOTE: This upgrade is disruptive.
Cisco NX-OS Release 7.0(3)I1(2) Upgrade Patch
https://software.cisco.com/download/special/release.html?config=ea82d4567eeb829ad4f32ae29c627cfc
Cisco NX-OS Release 7.0(3)I1(3) Upgrade Patch
https://software.cisco.com/download/special/release.html?config=e3e68dd1e8db9633978e080b9b715df8
Cisco NX-OS Release 7.0(3)I1(3a) Upgrade Patch
https://software.cisco.com/download/special/release.html?config=0f2015eebc7ea0d606441171b4a3baf2
4. Upgrade using the install all command.
The following table is an example of a patch upgrade:
Disable the Guest Shell if you need to downgrade from Cisco NX-OS Release 9.2(4) to an earlier release.
■ ISSU (non-disruptive) downgrade is not supported.
For information about software maintenance upgrades, see the “Performing Software Maintenance Upgrades” section in the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.2(x).
If you are going to apply the patch for the issue described in CSCvh04723, you must make sure that the ACL is deleted before applying the patch. Otherwise, the issue will be seen again. This issue applies only to the ACL which has the redirect keyword in it.
This section lists limitations related to Cisco NX-OS Release 9.2(4).
■ PTP is not supported on the 96136YC-R line card or for line cards on the Cisco Nexus 9504 switch.
■ The following features are not supported on the Cisco Nexus 3464C and 9364C switches.
o 100 G port cannot support breakout (HW limitation)
o FEX
o ISSU
o Segment routing
o Tetration (HW limitation)
■ The following feature is not supported on the Cisco Nexus 9332C:
o uRPF
■ The following switches support QSFP+ with the QSFP to SFP/SFP+ adapter (40 Gb to 10 Gb):
o N9K-C93108TC-FX
o N9K-C93180YC-FX
■ Note: The Cisco Nexus 9300 platforms support for the QSFP+ breakout has the following limitations:
■ 1 Gb with QSFP-to-SFP Adapter is not supported.
■ For the Cisco Nexus 9332PQ switch, all ports except 13-14 and 27-32 can support breakout.
■ The following switches support the breakout cable (40 Gb ports to 4x10-Gb ports):
o N9K-C93180LC-EX—last four ports are breakout capable (10x4, 24x4, 50x2)
o N9K-X9732C-FX line card
■ Limitations for ALE (Application Link Engine) uplink ports are listed at the following URL:
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/ale_ports/b_Limitations_for_ALE_Uplink_Ports_on_Cisco_Nexus_9000_Series_Switches.html
Notes regarding unsupported features:
■ Cisco Nexus 9200, 9300-EX, and 9300-FX Platform Switches
■ Cisco Nexus 9500 Platform N9K-X9408PC-CFP2 Line Card and 9300 Platform Switches
■ Cisco Nexus 9504 and 9508 Switches with -R and -RX Line Cards
The following features are not supported for the Cisco Nexus 9200 platform switches and the Cisco Nexus 93108TC-EX and 93180YC-EX switches:
■ Cisco Nexus 9272PQ and Cisco Nexus 92160YC platforms do not support the PXE boot of the NXOS image from the loader.
■ ACL filters to span subinterface traffic on the parent interface
■ Egress QoS policer is supported on the Cisco Nexus 9300-EX and 9300-FX platform switches. It is not supported on the Cisco Nexus 9200 platform switch. The only policer action supported is drop. Remark action is not supported on egress policer.
■ FEX (supported for Cisco Nexus 9300-EX platform switches but not for Cisco Nexus 9200 platform switches.)
■ GRE v4 payload over v6 tunnels
■ IP-in-IP on Cisco Nexus 92160 switch
■ ISSU enhanced is not supported on the Cisco Nexus 9300-FX platform switch.
■ Layer 2 Q-in-Q is supported only on Cisco Nexus 9300-EX platform switches (93108TC-EX and 93180YC-EX) and Cisco Nexus 9500 platform switches with the X9732C-EX line card.
■ MTU (Multi Transmission Unit) checks for packets received with an MPLS header
■ NetFlow is not supported on Cisco Nexus 9200 platform switches. It is supported on Cisco Nexus 9300-EX and 9300-FX platform switches.
■ Packet-based statistics for traffic storm control (only byte-based statistics are supported)
■ PVLANs (supported on Cisco Nexus 9300 and 9300-EX platform switches but not on Cisco Nexus 9200 platform switches)
■ Q-in-VNI is not supported on Cisco Nexus 9200 platform switches. Beginning with Cisco NX-OS Release 7.0(3)I5(1), Q-in-VNI is supported on Cisco Nexus 9300-EX platform switches.
■ Q-in-Q for VXLAN is not supported on Cisco Nexus 9200 and 9300-EX platform switches
■ Q-in-VNI is not supported on Cisco Nexus 9200 platform switches (supported on Cisco Nexus 9300-EX platform switches)
■ Resilient hashing for ECMP on the Cisco Nexus 9200 platform switches.
■ Resilient hashing for port-channel
■ Rx SPAN for multicast if the SPAN source and destination are on the same slice and no forwarding interface is on the slice
■ SVI uplinks with Q-in-VNI are not supported with Cisco Nexus 9300-EX platform switches
■ Traffic storm control for copy-to-CPU packets
■ Traffic storm control with unknown multicast traffic
■ Tx SPAN for multicast, unknown multicast, and broadcast traffic
■ VACL redirects for TAP aggregation
The following features are not supported for the Cisco Nexus 9500 platform N9K-X9408PC-CFP2 line card and Cisco Nexus 9300 platform switches with generic expansion modules (N9K-M4PC-CFP2):
■ FEX (this applies to the N9K-X9408PC-CFP2 and –EX switches, not all Cisco Nexus 9300 platform switches)
■ MCT (Multichassis EtherChannel Trunk)
■ PTP (Precision Time Protocol)
■ PVLAN (supported on Cisco Nexus 9300 platform switches)
■ Shaping support on 100g port is limited
■ SPAN destination/ERSPAN destination IP
The following feature is not supported:
■ 2x50 breakout
The following features are not supported for the N9K-X96136YC-R line card:
■ Breakout is not supported.
■ PTP and gPTP are not supported.
The following feature is not supported for the N9K-X9736C-FX line card:
■ Ports 29-36 do not support 1 Gbps speed.
The following features are not supported for Cisco Nexus 9500 cloud scale (EX/FX) line cards:
■ IPv6 support for policy-based routing
■ SPAN port-channel destinations
The entire Cisco Nexus 9000 Series NX-OS documentation set is available at the following URL:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/tsd-products-support-series-home.html
The Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference is available at the following URL:
https://developer.cisco.com/site/nx-os/docs/n3k-n9k-api-ref/
The Cisco NX-OS Supported MIBs URL:
ftp://ftp.cisco.com/pub/mibs/supportlists/nexus9000/Nexus9000MIBSupportList.html
Cisco Nexus 9000 Series Software Upgrade and Downgrade Guide URL:
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/92x/upgrade/guide/b-cisco-nexus-9000-nx-os-software-upgrade-downgrade-guide-92x.html
The Cisco Nexus 9000 Series FPGA/EPLD Upgrade Release Notes, Release 9.2(4) is available at the following URL:
The Cisco Nexus 9000 Series NX-OS Verified Scalability Guide, Release 9.2(4) is available at the following URL:
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/92x/scalability/guide_924/b-Cisco-Nexus-9000-Series-NX-OS-Verified-Scalability-Guide-924.html
To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus9k-docfeedback@cisco.com. We appreciate your feedback.
For information on obtaining documentation and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
https://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Open a service request online at:
https://tools.cisco.com/ServiceRequestTool/create/launch.do
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)