Cisco Nexus 9000 ACI-Mode Switches Release Notes, Release 16.0(5)

September 30, 2024

Added CSCwm66473 to the list of Open Issues.

June 3, 2024

Release 16.0(5j) became available. Added the resolved bugs for this release.

April 8, 2024

In the Compatibility Information section, added:

February 28, 2024

Release 16.0(5h) became available.

N9K-C9408

Cisco Nexus 9408 modular chassis switch with up to 128 200/100-Gigabit (256 100-Gigabit by 200G-to-2x100G breakout) ports using N9K-X9400-16W or 64 400/200/100-Gigabit (256 100-Gigabit by 400G-to-4x100G breakout) ports using N9K-X9400-8D.

N9K-C9504

Cisco Nexus 9504 switch chassis

N9K-C9508

Cisco Nexus 9508 switch chassis

N9K-C9508-B1

Cisco Nexus 9508 chassis bundle with 1 supervisor module, 3 power supplies, 2 system controllers, 3 fan trays, and 3 fabric modules

N9K-C9508-B2

Cisco Nexus 9508 chassis bundle with 1 supervisor module, 3 power supplies, 2 system controllers, 3 fan trays, and 6 fabric modules

N9K-C9516

Cisco Nexus 9516 switch chassis

N9K-X9400-8D

Cisco Nexus 9400 8-port 400 Gigabit QSFP-DD linecard expansion module

8

N/A

N/A

N/A

N9K-X9400-16W

Cisco Nexus 9400 16-port 200 Gigabit linecard expansion module

8

N/A

N/A

N/A

N9K-X9716D-GX

Cisco Nexus 9500 16-port 400 Gigabit Ethernet QSFP line card

N/A

4

8

16

N9K-X9736C-FX

Cisco Nexus 9500 36-port 40/100 Gigabit Ethernet Cloud Scale line card

N/A

4

8

16

N9K-X9736Q-FX

Cisco Nexus 9500 36-port 40 Gigabit Ethernet Cloud Scale line card

N/A

4

8

16

N9K-X9732C-EX

Cisco Nexus 9500 32-port, 40/100 Gigabit Ethernet Cloud Scale line card

Note: The N9K-X9732C-EX line card cannot be used when a fabric module is installed in FM slot 25.

N/A

4

8

16

N9K-C9504-FM-G

Cisco Nexus 9508 cloud scale fabric module (400G capable)

4

5

N9K-C9508-FM-G

Cisco Nexus 9508 cloud scale fabric module (400G capable)

4

5

N9K-C9504-FM-E

Cisco Nexus 9504 cloud scale fabric module

4

5

N9K-C9508-FM-E

Cisco Nexus 9508 cloud scale fabric module

4

5

N9K-C9508-FM-E2

Cisco Nexus 9508 cloud scale fabric module

4

5

N9K-C9516-FM-E2

Cisco Nexus 9516 cloud scale fabric module

4

5

N9K-C9504-FAN2

Nexus 9500 4-slot fan tray (gen 2)

N9K-C9504-FAN-PWR

Nexus 9500 4-slot fan tray power card blank

N9K-C9504-FAN

Fan tray for Cisco Nexus 9504 chassis

N9K-C9508-FAN2

Nexus 9500 8-slot fan tray (gen 2)

N9K-C9508-FAN-PWR

Nexus 9500 8-slot fan tray power card blank

N9K-C9508-FAN

Fan tray for Cisco Nexus 9508 chassis

N9K-C9516-FAN

Fan tray for Cisco Nexus 9516 chassis

N9K-C9400-SUP-A

Cisco Nexus 9400 Series supervisor module

N9K-SUP-A+

Cisco Nexus 9500 Series supervisor module

N9K-SUP-B+

Cisco Nexus 9500 Series supervisor module

N9K-SUP-A

Cisco Nexus 9500 Series supervisor module

N9K-SUP-B

Cisco Nexus 9500 Series supervisor module

N9K-SC-A

Cisco Nexus 9500 Series system controller

N9K-C9364D-GX2A

Cisco Nexus 9300 platform switch with 64 400/100-Gigabit QSFP-DD ports and 2 1/10 SFP+ ports.

N9K-C9348D-GX2A

Cisco Nexus 9300 platform switch with 48 400/100-Gigabit QSFP-DD ports and 2 1/10 SFP+ ports.

N9K-C9332D-GX2B

Cisco Nexus 9300 platform switch with 32p 400/100-Gigabit QSFP-DD ports and 2p 1/10 SFP+ ports.

N9K-C93600CD-GX

Cisco Nexus 9300 platform switch with 28 10/40/100-Gigabit Ethernet QSFP28 ports (ports 1-28) and 8 10/40/100/400-Gigabit QSFP-DD ports (ports 29-36).

N9K-C9316D-GX

Cisco Nexus 9300 platform switch with 16 10/40/100/400-Gigabit QSFP-DD ports (ports 1-16).

N9K-C9332C

Cisco Nexus 9300 platform switch with 32 40/100-Gigabit QSFP28 ports and 2 SFP ports. Ports 25-32 offer hardware support for MACsec encryption.

N9K-C9364C-GX

Cisco Nexus 9300 platform switch with 64 100-Gigabit Ethernet QSFP28 ports, two management ports (one 10/100/1000BASE-T port and one SFP port), one console port (RS-232), and one USB port.

N9K-C9364C

Cisco Nexus 9300 platform switch with 64 40/100-Gigabit QSFP28 ports and two 1/10-Gigabit SFP+ ports. The last 16 of the QSFP28 ports are colored green to indicate that they support wire-rate MACsec encryption.

NXA-PAC-2KW-PI

Nexus 9000 2KW AC power supply, port-side intake

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

N9K-PAC-1200W

1200W AC power supply, port side intake pluggable

Note: This power supply is supported only by the Cisco Nexus 93120TX and 9336PQ ACI-mode switches

N9K-PAC-1200W-B

1200W AC power supply, port side exhaust pluggable

Note: This power supply is supported only by the Cisco Nexus 93120TX and 9336PQ ACI-mode switches

NXA-PAC-1200W-PE

1200W AC power supply, port side exhaust pluggable, with higher fan speeds for NEBS compliance

NXA-PAC-1200W-PI

1200W AC power supply, port side intake pluggable, with higher fan speeds for NEBS compliance

NXA-PAC-1100W-PE2

1100W AC power supply, port side exhaust pluggable

NXA-PAC-1100W-PI2

1100W AC power supply, port side intake pluggable

NXA-PAC-750W-PE

750W AC power supply, port side exhaust pluggable, with higher fan speeds for NEBS compliance

Note: This power supply is supported only on release 14.2(1) and later.

NXA-PAC-750W-PI

750W AC power supply, port side intake pluggable, with higher fan speeds for NEBS compliance

Note: This power supply is supported only on release 14.2(1) and later.

NXA-PDC-2KW-PI

Nexus 9000 2KW DC power supply, port-side intake

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

NXA-PDC-1100W-PE

1100W AC power supply, port side exhaust pluggable

NXA-PDC-1100W-PI

1100W AC power supply, port side intake pluggable

NXA-PDC-930W-PE

930W AC power supply, port side exhaust pluggable

NXA-PDC-930W-PI

930W AC power supply, port side intake pluggable

NXA-PHV-2KW-PI

Nexus 9000 2KW AC power supply, port-side intake

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

NXA-PHV-1100W-PE

1100W HVAC/HVDC power supply, port-side exhaust

NXA-PHV-1100W-PI

1100W HVAC/HVDC power supply, port-side intake

N9K-PUV-1200W

1200W HVAC/HVDC dual-direction airflow power supply

N9K-C9300-FAN3

Burgundy port side intake fan

N9K-C9300-FAN3-B

Blue port side exhaust fan

N9K-C9400-FAN-PI

Burgundy port side intake fan

NXA-FAN-160CFM-PE

Blue port side exhaust fan

NXA-FAN-160CFM-PI

Burgundy port side intake fan

NXA-FAN-35CFM-PE

Blue port side exhaust fan

NXA-FAN-35CFM-PI

Burgundy port side intake fan

N9K-C9408

Cisco Nexus 9408 modular chassis switch with up to 128 200/100-Gigabit (256 100-Gigabit by 200G-to-2x100G breakout) ports using N9K-X9400-16W or 64 400/200/100-Gigabit (256 100-Gigabit by 400G-to-4x100G breakout) ports using N9K-X9400-8D.

N9K-X9400-8D

Cisco Nexus 9400 8-port 400 Gigabit QSFP-DD linecard expansion module

4

8

16

N9K-X9400-16W

Cisco Nexus 9400 16-port 200 Gigabit linecard expansion module

4

8

16

N9K-C9400-SUP-A

Cisco Nexus 9400 Series supervisor module

N9K-C9364D-GX2A

Cisco Nexus 9300 platform switch with 64 400/100-Gigabit QSFP-DD ports and 2 1/10 SFP+ ports.

N9K-C9348D-GX2A

Cisco Nexus 9300 platform switch with 48 400/100-Gigabit QSFP-DD ports and 2 1/10 SFP+ ports.

N9K-C9332D-GX2B

Cisco Nexus 9300 platform switch with 32p 400/100-Gigabit QSFP-DD ports and 2p 1/10 SFP+ ports.

N9K-C9316D-GX

Cisco Nexus 9300 platform switch with 16 10/40/100/400-Gigabit QSFP-DD ports (ports 1-16).

N9K-C9364C-GX

Cisco Nexus 9300 platform switch with 64 100-Gigabit Ethernet QSFP28 ports, two management ports (one 10/100/1000BASE-T port and one SFP port), one console port (RS-232), and one USB port.

N9K-C93600CD-GX

Cisco Nexus 9300 platform switch with 28 10/40/100-Gigabit Ethernet QSFP28 ports (ports 1-28) and 8 10/40/100/400-Gigabit QSFP-DD ports (ports 29-36).

N9K-C93180YC-FX3

Cisco Nexus 9300 platform switch with 48 100M/1/10/25-Gigabit Ethernet SFP28 ports, 6 40/100-Gigabit QSFP28 ports, two management ports (one 10/100/1000BASE-T and one SFP+), one console port (RS-232), and one USB port.

N9K-C93180YC-FX3H

Cisco Nexus 9300 platform switch with 24 100M/1/10/25-Gigabit Ethernet SFP28 ports, 6 40/100-Gigabit QSFP28 ports, one management port (10/100/1000BASE-T), one console port (RS-232), and one USB port.

N9K-C93108TC-FX3H

Cisco Nexus 9300 platform switch with 24 100M/1/10-GBASE-T (copper) ports, 6 40/100-Gigabit QSFP28 ports, two management ports (one 10/100/1000BASE-T and one SFP+), one console port (RS-232), and one USB port.

N9K-C93108TC-FX3P

Cisco Nexus 9300 platform switch with 48 100M/1/10-GBASE-T (copper) ports, 6 40/100-Gigabit QSFP28 ports, two management ports (one 10/100/1000BASE-T and one SFP+), one console port (RS-232), and one USB port.

N9K-C93108TC-FX3

Cisco Nexus 9300 platform switch with 48 100M/1/10-GBASE-T (copper) ports, 6 40/100-Gigabit QSFP28 ports, two management ports (one 10/100/1000BASE-T and one SFP+), one console port (RS-232), and one USB port.

N9K-C9348GC-FX3

Cisco Nexus 9300 platform switch with 48 100M/1-GBASE-T (copper) ports, 4 1/10/25-Gigabit SFP28 ports, two 40/100G QSFP28 ports, two management ports (one 10/100/1000BASE-T and one SFP+), one console port (RS-232), and one USB port.

N9K-C93240YC-FX2

Cisco Nexus 9300 platform switch with 48 1/10/25-Gigabit Ethernet SFP28 ports and 12 40/100-Gigabit Ethernet QSFP28 ports. The N9K-C93240YC-FX2 is a 1.2-RU switch.

Note: 10/25G-LR-S with QSA is not supported.

N9K-C93216TC-FX2

Cisco Nexus 9300 platform switch with 96 1/10GBASE-T (copper) front panel ports and 12 40 /100-Gigabit Ethernet QSFP28 spine-facing ports

N9K-C93360YC-FX2

Cisco Nexus 9300 platform switch with 96 1/10/25-Gigabit front panel ports and 12 40 /100-Gigabit Ethernet QSFP spine-facing ports.

Note: The supported total number of fabric ports and port profile converted fabric links is 64.

N9K-C9336C-FX2-E

Cisco Nexus 9336C-FX2 Top-of-rack (ToR) switch with 36 fixed 40/100-Gigabit Ethernet QSFP28 spine-facing ports.

Note: 1-Gigabit QSA is not supported on ports 1/1-6 and 1/33-36. The port profile feature supports downlink conversion of ports 31 through 34. Ports 35 and 36 can only be used as uplinks.

N9K-C9336C-FX2

Cisco Nexus 9336C-FX2 Top-of-rack (ToR) switch with 36 fixed 40/100-Gigabit Ethernet QSFP28 spine-facing ports.

Note: 1-Gigabit QSA is not supported on ports 1/1-6 and 1/33-36. The port profile feature supports downlink conversion of ports 31 through 34. Ports 35 and 36 can only be used as uplinks.

N9K-C93108TC-FX

Cisco Nexus 9300 platform switch with 48 1/10GBASE-T (copper) front panel ports and 6 fixed 40/100-Gigabit Ethernet QSFP28 spine-facing ports.

Note: Incoming FCOE packets are redirected by the supervisor module. The data plane-forwarded packets are dropped and are counted as forward drops instead of as supervisor module drops.

N9K-C93108TC-FX-24

Cisco Nexus 9300 platform switch with 24 1/10GBASE-T (copper) front panel ports and 6 fixed 40/100-Gigabit Ethernet QSFP28 spine-facing ports.

Note: Incoming FCOE packets are redirected by the supervisor module. The data plane-forwarded packets are dropped and are counted as forward drops instead of as supervisor module drops.

N9K-C93180YC-FX

Cisco Nexus 9300 platform switch with 48 1/10/25-Gigabit Ethernet SFP28 front panel ports and 6 fixed 40/100-Gigabit Ethernet QSFP28 spine-facing ports. The SFP28 ports support 1-, 10-, and 25-Gigabit Ethernet connections and 8-, 16-, and 32-Gigabit Fibre Channel connections.

Note: Incoming FCOE packets are redirected by the supervisor module. The data plane-forwarded packets are dropped and are counted as forward drops instead of as supervisor module drops.

N9K-C93180YC-FX-24

Cisco Nexus 9300 platform switch with 24 1/10/25-Gigabit Ethernet SFP28 front panel ports and 6 fixed 40/100-Gigabit Ethernet QSFP28 spine-facing ports. The SFP28 ports support 1-, 10-, and 25-Gigabit Ethernet connections and 8-, 16-, and 32-Gigabit Fibre Channel connections.

Note: Incoming FCOE packets are redirected by the supervisor module. The data plane-forwarded packets are dropped and are counted as forward drops instead of as supervisor module drops.

N9K-C9348GC-FXP

Cisco Nexus 9348GC-FXP switch with 48 100/1000-Megabit 1GBASE-T downlink ports, 4 10-/25-Gigabit SFP28 downlink ports, and 2 40-/100-Gigabit QSFP28 uplink ports.

N9K-C93108TC-EX

Cisco Nexus 9300 platform switch with 48 1/10GBASE-T (copper) front panel ports and 6 40/100-Gigabit QSFP28 spine facing ports.

N9K-C93108TC-EX-24

Cisco Nexus 9300 platform switch with 24 1/10GBASE-T (copper) front panel ports and 6 40/100-Gigabit QSFP28 spine facing ports.

N9K-C93180LC-EX

Cisco Nexus 9300 platform switch with 24 40-Gigabit front panel ports and 6 40/100-Gigabit QSFP28 spine-facing ports.

The switch can be used as either a 24 40G port switch or a 12 100G port switch. If 100G is connected the Port1, Port 2 will be HW disabled.

N9K-C93180YC-EX

Cisco Nexus 9300 platform switch with 48 1/10/25-Gigabit front panel ports and 6-port 40/100 Gigabit QSFP28 spine-facing ports.

N9K-C93180YC-EX-24

Cisco Nexus 9300 platform switch with 24 1/10/25-Gigabit front panel ports and 6-port 40/100 Gigabit QSFP28 spine-facing ports.

NXA-PAC-2KW-PE

Nexus 9000 2KW AC power supply, port-side exhaust

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

NXA-PAC-2KW-PI

Nexus 9000 2KW AC power supply, port-side intake

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

N9K-PAC-1200W

1200W AC power supply, port side intake pluggable

Note: This power supply is supported only by the Cisco Nexus 93120TX and 9336PQ ACI-mode switches

N9K-PAC-1200W-B

1200W AC power supply, port side exhaust pluggable

Note: This power supply is supported only by the Cisco Nexus 93120TX and 9336PQ ACI-mode switches

N9k-PAC-3000W-B

3000W AC power supply, port side intake

N9K-PAC-650W

650W AC power supply, port side intake pluggable

N9K-PAC-650W-B

650W AC power supply, port side exhaust pluggable

NXA-PAC-1200W-PE

1200W AC power supply, port side exhaust pluggable, with higher fan speeds for NEBS compliance

NXA-PAC-1200W-PI

1200W AC power supply, port side intake pluggable, with higher fan speeds for NEBS compliance

NXA-PAC-1100W-PE2

1100W AC power supply, port side exhaust pluggable

NXA-PAC-1100W-PI2

1100W AC power supply, port side intake pluggable

NXA-PAC-750W-PE

750W AC power supply, port side exhaust pluggable, with higher fan speeds for NEBS compliance

Note: This power supply is supported only on release 14.2(1) and later.

NXA-PAC-750W-PI

750W AC power supply, port side intake pluggable, with higher fan speeds for NEBS compliance

Note: This power supply is supported only on release 14.2(1) and later.

NXA-PAC-650W-PE

650W AC power supply, port side exhaust pluggable

NXA-PAC-650W-PI

650W AC power supply, port side intake pluggable

NXA-PAC-500W-PE

500W AC Power supply, port side exhaust pluggable

NXA-PAC-500W-PI

500W AC Power supply, port side intake pluggable

NXA-PAC-350W-PE

350W AC power supply, port side exhaust pluggable

NXA-PAC-350W-PI

350W AC power supply, port side intake pluggable

NXA-PDC-2KW-PE

Nexus 9000 2KW DC power supply, port-side exhaust

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

NXA-PDC-2KW-PI

Nexus 9000 2KW DC power supply, port-side intake

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

NXA-PDC-1100W-PE

1100W AC power supply, port side exhaust pluggable

NXA-PDC-1100W-PI

1100W AC power supply, port side intake pluggable

NXA-PDC-930W-PE

930W AC power supply, port side exhaust pluggable

NXA-PDC-930W-PI

930W AC power supply, port side intake pluggable

NXA-PDC-715W-PI

715W DC power supply, port side intake pluggable

Note: This power supply is supported only by the Cisco Nexus 93108TC-FX3P ACI-mode switch.

NXA-PDC-440W-PE

440W DC power supply, port side exhaust pluggable, with higher fan speeds for NEBS compliance

Note: This power supply is supported only by the Cisco Nexus 9348GC-FXP and 9348GC-FX3 ACI-mode switches.

NXA-PDC-440W-PI

440W DC power supply, port side intake pluggable, with higher fan speeds for NEBS compliance

Note: This power supply is supported only by the Cisco Nexus 9348GC-FXP and 9348GC-FX3 ACI-mode switches.

NXA-PHV-2KW-PE

Nexus 9000 2KW AC power supply, port-side exhaust

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

NXA-PHV-2KW-PI

Nexus 9000 2KW AC power supply, port-side intake

Note: This power supply is supported only by the Cisco Nexus 9364C-GX ACI-mode switch.

NXA-PHV-1100W-PE

1100W HVAC/HVDC power supply, port-side exhaust

NXA-PHV-1100W-PI

1100W HVAC/HVDC power supply, port-side intake

NXA-PHV-350W-PE

350W HVAC/HVDC power supply, port-side exhaust

NXA-PHV-350W-PI

350W HVAC/HVDC power supply, port-side intake

N9K-PUV-1200W

1200W HVAC/HVDC dual-direction airflow power supply

N9K-PUV-3000W-B

3000W AC power supply, port side exhaust pluggable

UCSC-PSU-930WDC V01

Port side exhaust DC power supply compatible with all leaf switches

UCS-PSU-6332-DC

930W DC power supply, reversed airflow (port side exhaust)

N9K-C9300-FAN2

Burgundy port side intake fan

N9K-C9300-FAN2-B

Blue port side exhaust fan

N9K-C9300-FAN3

Burgundy port side intake fan

N9K-C9300-FAN3-B

Blue port side exhaust fan

N9K-C9400-FAN-PI

Burgundy port side intake fan

NXA-FAN-160CFM2-PE

Blue port side exhaust fan

NXA-FAN-160CFM2-PI

Burgundy port side intake fan

NXA-FAN-160CFM-PE

Blue port side exhaust fan

NXA-FAN-160CFM-PI

Burgundy port side intake fan

NXA-FAN-30CFM-B

Burgundy port side intake fan

NXA-FAN-30CFM-F

Blue port side exhaust fan

NXA-SFAN-30CFM-PE

Blue port side exhaust fan

NXA-SFAN-30CFM-PI

Burgundy port side intake fan

NXA-FAN-35CFM-PE

Blue port side exhaust fan

NXA-SFAN-35CFM-PE

Blue port side exhaust fan

NXA-FAN-35CFM-PI

Burgundy port side intake fan

NXA-SFAN-35CFM-PI

Burgundy port side intake fan

NXA-FAN-65CFM-PE

Blue port side exhaust fan

NXA-SFAN-65CFM-PE

Blue port side exhaust fan

NXA-FAN-65CFM-PI

Burgundy port side intake fan

NXA-SFAN-65CFM-PI

Burgundy port side intake fan

Spine switch

N9K-C9336PQ

Modular spine switch line card

N9K-X9736PQ

Modular spine switch fabric module

N9K-C9504-FM

N9K-C9508-FM

N9K-C9516-FM

Leaf Switch

N9K-C93120TX

N9K-C93128TX

N9K-C9332PQ

N9K-C9372PX

N9K-C9372PX-E

N9K-C9372TX

N9K-C9372TX-E

N9K-C9396PX

N9K-C9396TX

Expansion Modules

N9K-M12PQ

N9K-M6PQ

N9K-M6PQ-E

CSCwm66473

When using a N9K-C93108TC-FX3 in ACI mode, a diagnostic failure is displayed for RTC-TEST.

16.0(5h) through 16.0(7e).

CSCvg85886

When an ARP request is generated from one endpoint to another endpoint in an isolated EPG, an ARP glean request is generated for the first endpoint.

16.0(5h) and later

CSCwm58397

Stale MAC entry in Infra BD with constant CooP bounce updates in Fabric for the given MAC.

- MAC is present in two locations in Fabric for Infra BD

1. Old Leafs (VPC pair, only 1x switch in the pair has the stale entry) has MAC only local learn while MAC is no longer behind this leaf.

This entry doesn't time out and might refresh from any flooded frame in Infra BD though not updating the learn as Xr learn.

2. New Leafs where MAC locally resides, i.e. correct location.

16.0(5j) and later

CSCwm62890

Opflex connection not established between Agent and directly connected leaf No communication from Inband/CPU to directly connect host in Infra VLAN, however may affect other BDs.

16.0(5j) and later

CSCwm01630

Msite Announce packet (Tracking used by IPSLA) from site 1 with modular spines are not reaching site 2 spines due to TTL being expired on ISN.

16.0(5j) and later

CSCwj91816

PSU-fail fault with code F0411 from nodes were observed intermittently on APIC. The faults were raised and cleared in TCA lifecycle.

16.0(5h) and later

CSCwj21979

1) Leaf is a remote leaf

2) One or more port channel exists with fabric ports as members

16.0(5h) and later

CSCwk44519

N9K-C93180YC-FX3 fabric interfaces are flapping on eth 1/51 and 52.

16.0(5h) and later

CSCvw89840

Traffic originating from a vPC TEP is dropped for Layer 2 multicast and unknown unicast traffic when pod redundancy is triggered.

16.0(5h) and later

CSCvy31805

The PBR destination group for bypass action is not properly programmed with PBR service graph for service devices behind l3out and with "bypass" action enabled to redirect to another service node in the graph.Now on bypass switchover, the traffic doesn't get redirected to the next service node in the chain.

16.0(5h) and later

CSCwc61780

N9K-C9408 ASIC SFP+ ports on N9K-C9400-SUP-A card are not supported.

16.0(5h) and later

CSCwd89607

When endpoint rogue detection or endpoint loop control is enabled with first hop security, the fabric might flag incorrect endpoint moves. This might lead to loss of traffic or the disabling of bridge domain learning.

16.0(5h) and later

CSCwf45328

BGP generates a core after deleting and restoring an SR MPLS infra L3Out node profile. This issue occurred with a scale configuration (800 VRF instances).

16.0(5h) and later

CSCwf74167

An endpoint does not receive a DHCP response when First-Hop Security (FHS) is enabled.

16.0(5h) and later

CSCwf78322

Customer sees the following fault for a spine switch:

F920312 or customer notices low memory condition in fixed spines with 16GB memory

16.0(5h) and later

CSCwf80004

Upon upgrade to the 16.0(3) release from an earlier release, using SSH to connect to the switch does not succeed.

The SSH client end displays the "connection refused" message.

16.0(5h) and later

CSCwf80004

Upon upgrade to the 16.0(5) release from an earlier release, using SSH to connect to the switch does not succeed. The SSH client end displays the "connection refused" message.

16.0(5h) and later

CSCwf87280

All the conditions for priority flow control (PFC) are met, such as consistent congestion or PFC frames received. But, PFC frames are not generated on the front panel interface to slow down the sender.

16.0(5h) and later

CSCwf93802

Traffic loss is observed because an endpoint is not synced from leaf1 to leaf2.

16.0(5h) and later

CSCwh15088

4X25G-CU (<=3m) links do not come on certain ports of GX2 platforms with AN on-enforce.

When auto-negotiation is enabled on 25G speed on GX2 retimer ports, the link does not come up.

16.0(5h) and later

CSCwh39489

The ACI-mode switch 16.0(3) release and later causes high memory utilization of 16GB modular spine switch supervisors. The Cisco APIC raises a fault with either of the following fault codes:

·       F4341

·       F4342

16.0(5h) and later

CSCwi01017

This bug is only applicable when scale of the switch config is high. Repeated tech-support collection causes the log files to be completely deleted from under /mnt/ifc/log/.

16.0(5h) and later

CSCwi87437

MFDM MTS buffer is stuck, causing the MFDM process to not process updates coming from other processes. This can impact broadcast programming on the downstream component, which causes a BUM issue.

16.0(5h) and later

CSCwi89535

A leaf switch crashes due to the following reason:

Reason: Reset triggered due to HA policy of ResetService: sdkhal hap resetVersion : xxx

16.0(5h) and later

CSCwj16816

Virtual machines behind remote leaf switches are not able to resolve to a bridge domain gateway when spine switch connectivity is lost.

16.0(5h) and later

CSCwj19730

A port gets stuck on an old VLAN.

16.0(5h) and later

CSCwj23667

- Enabling MACsec between ACI and Nexus devices.

- The MACsec session needs to be established.

- CDP neighbors are not available for the interface, but the LLDP neighbors are correct.

16.0(5h) and later

CSCwj30440

The supervisor of a leaf switch silently reloads.

16.0(5h) and later

CSCwj40048

When running "show power inline" from the default shell, ibash, "not well-formed (invalid token)" is returned and not the expected interface power usage

16.0(5h) and later

CSCwj44601

The Infoblox servers are in across pods and they form a cluster using VRRP. When PBR vzAny is enabled, the Infoblox cluster stops working. When PBR vzAny is disabled, the Infoblox cluster starts working again.

16.0(5h) and later

CSCwj49728

After reloading, a spine switch advertises its routes to the Inter Pod Network (IPN) with a MED 200 for approximately 10 minutes. This prevents IPN traffic from being routed to the reloaded spine switch immediately after the reload. Approximately 10 minutes after the reload, this MED value 200 is removed. However, there are some cases where this MED 200 may not be set. If MED 200 is not applied to its routes, traffic may be routed to a spine switch that is not yet ready, resulting in dropped packets.

16.0(5h) and later

CSCwj50547

N9K-C93360YC-FX2 running 16.0(3e) ACI code crashes and generates LLDP core file.

16.0(5h) and later

CSCwj51461

A host has connectivity loss when the destination host fail overed using UCS Fabric Failover. Issue happens when PVLAN and Micro segmentation are enabled on EPG with Proxy-ARP flag.

16.0(5h)

CSCwj51461

A host has connectivity loss when the destination host fail overed using UCS Fabric Failover. Issue happens when PVLAN and Micro segmentation are enabled on EPG with Proxy-ARP flag.

16.0(5h) and later

CSCwj51767

There is a kernel panic resulting in a switch reset or crash:

  Reason: Kernel Panic

  System version: 15.2(8e)

  Service: system crash

16.0(5h) and later

CSCwj59815

FM-G fabric modules (potentially other modules as well) fail to initialize when inserted into a switch running 16.0(2h).

From the fabric modules' console logs, the partitions appear to be different than what is seen on other fabric modules that have been successfully initialized.

16.0(5h) and later

CSCwj67989

When configuring a /32 subnet for "IP Data-plane Learning disabled" under an EPG, the subnet is deployed to a leaf switch with the EPG as well as the EPGs' consumed source EPG by the contract. As a result, it adds a remote endpoint (XR EP) to the hardware and causes any received iVXLAN packet with an inner destination to hit the /32 endpoint, which gets dropped by the loop prevention ACL.

This /32 endpoint may become stale even after the /32 EPG subnet has been deleted from the Cisco APIC.

16.0(5h) and later

CSCwj76543

N9K-X9736C-FX line cards may randomly reload, which can impact traffic due to the type of reload that occurs.

16.0(5h) and later

CSCwj87708

An ACI-mode spine switch forwards traffic to the wrong service leaf switch and causes traffic loss when using active/standby Layer 1 policy-based redirect and a failover occurs.

16.0(5h) and later

CSCwj94677

Auto-negotiation does not work on a Cisco N9K-C9408 switch that has one of the following line-card expansion modules (LEMs):

16.0(5h) and later

CSCwk23291

A Cisco ACI-mode switch regularly sends UDP packets from port 1534 to the broadcast address of the out-of-band management interface. This can be observed by using the tcpdump command from any switch whose out-of-band management interface address belongs to same subnet. This kind of broadcast will not reach the Cisco ACI-mode switch OS because iptables by default deny it.

16.0(5h) and later

CSCwk37834

A leaf switch will crash due to aclqos hap reset.

16.0(5h) and later

CSCwk39458

A leaf switch crashes due to FCPC hap reset.

16.0(5h) and later

CSCwk47025

When querying for OID 1.3.6.1.2.1.1.2.0 for N9K-C9332D-GX2B, the incorrect value is returned by the switch if role is spine:

 - If role is spine: it will return 1.3.6.1.4.1.9.12.3.1.3.1570 (Nexus 9336PQ)

 - If role is leaf: it will return 1.3.6.1.4.1.9.12.3.1.3.2403 (Nexus 9332D-GX2B)

16.0(5h) and later

CSCwj59815

FM-G fabric modules (potentially other modules as well) fail to initialize when inserted into a switch running 16.0(2h).

From the FM's console logs, we can observe that the partitions appear to be different than what is seen on other FMs that have been successfully initialized.

16.0(5j)

CSCwd65255

If an EPLD update is triggered on an affected SUP, the SUP will not automatically boot. The supervisor's STS LED may be blinking yellow and console may not be responsive.

16.0(5h)

CSCwe90254

When a TechSupport file for a 9500 chassis with FM-E2 fabric modules is collected, the CLI commands needed to be run for the NX-OS TechSupport are wrong.

16.0(5h)

CSCwf15461

Whenever an EPG is configured with multiple physical domains using overlapping VLAN pools, following some configuration such as deleting/adding a pool to a domain or adding/removing a domain in an EPG, the fabric encapsulation (VXLAN ID used for VLAN encapsulation) might be mismatched.

F3274 will be seen and traffic to a vPC server might be impacted in that EPG.

16.0(5h)

CSCwf53105

"vsh" process generates multiple core files on switches after starting OnDemand Techsupport collection for leaf switches.

16.0(5h)

CSCwf57396

The 30 second input rate and 30 second output rate show values beyond 30 seconds for an interface that is disabled.

16.0(5h)

CSCwf58246

In the case of large network instability with a lot of flaps, the APIC may disable hardware learning and disable COOP to endpoint notification on a leaf switch. This can lead to a COOP entry on a spine switch pointing to a "wrong" location. This is a very rare scenario.

16.0(5h)

CSCwf88948

After a system controller switchover, there is no ping/ssh response from the spine switch in-band management for several minutes. It seems that there is an issue with path between SUP and linecard.

16.0(5h)

CSCwf92861

EVPN type 5 routes get stuck at the overlay-1 EVPN table with a refcount of 1. Because of this, the cleanup thread cannot clean up the VRF instance and remains stuck at deletion.

16.0(5h)

CSCwf95702

The vsh -c 'show ntp peer-status' command may show an already-deleted NTP server entry. Sometimes, it may cause issue with NTP getting synced to the latest added server. This behavior is not consistent.

16.0(5h)

CSCwh03684

HAL has high CPU utilization.

16.0(5h)

CSCwh07391

Traffic coming from ISN or IPN may get misclassified as iTraceroute or will not preserve CoS correctly. On any FM that was reloaded, dot1p preserve may have not been set correctly post reload.

16.0(5h)

CSCwh13845

After a spine switch stateful reload/upgrade, you may observe traffic drops in the ACI fabric. In case there are remote leaf switches, you may see remote leaf switches not forming a tunnel with the spine switches. On the upgraded/stateful reloaded spine switches, check the output of "show coop internal info global". If you observe the "Local Adjacency" as "Citizen", then you have hit this defect.

16.0(5h)

CSCwh15691

fvL3EpDef is not removed after adjacency gets updated.

16.0(5h)

CSCwh18633

Multicast convergence is slower than expected. Applications that use multicast for time sensitive tasks, for example, keep alive for HA, will be impacted and cause subsequent service impact.

16.0(5h)

CSCwh19186

Configuring a MAC address of "FF:FF:FF:FF:FF:FF" under the L3Out SVI MAC Exception Group causes all MAC addresses learned in the associated external bridge domain to be excluded from rogue endpoint control.

All MAC addresses from such SVIs will be marked as rogue for 30 seconds only if they move 3,000 times in 10 minutes.

16.0(5h)

CSCwh21375

When an SNMP GET is sent with the OID "iso.3.6.1.2.1.1.2.0" on a leaf/spine switch, the leaf/spine switch reponds with the faulty value 1.3.6.1.4.1.9.12.3.1.3.1570.

16.0(5h)

CSCwh21417

A switch's power supply is functioning properly even though the following error message persists:

LOG_LOCAL0-2-SYSTEM_MSG [E4204936][transition][critical][sys]  %PLATFORM-2-PS_UNSUPPORTED: Detected an unsupported power supply 2 Unknown for CISCO Multilayer Switch (Serial number LIT233023Z5 )

16.0(5h)

CSCwh26304

++ The temperature data measured by the sensors are not displayed in GUI correctly for PID: N9K-C9364C-GX.

++ the customer wants to see the temperature data under the next menu item: ../Fabric/Inventory/PodN/Node-XXX/Chassis/Supervisor Modules/Slot1/Equipment Sensors/1..5/Stats

++ Show Topology view does not show anything! (Normalized Temperature, Current Temperature) as per the images attached to the case by comparing them with another model where there are no issues.

++ Show Table View shows the data (Normalized Temperature, Current Temperature), but the Timestamp field does not show a meaningful value: 0NaN/NaN/NaN NaN:NaN:NaN

16.0(5h)

CSCwh29782

A Cisco Nexus 9000 switch in the ACI-mode cannot negotiate on a 1G link due to the "Remote Fault seen" error.

16.0(5h)

CSCwh46624

There is a Layer 1 connectivity issue between a N9K-C93180YC-FX3 device and Dell Power Edge FX2s server chassis. The servers have an Intel X710 NIC. The 10G ports fail to come when the Dell side I/O module is flapped. This issue is not specific to port/SFP/speed and may happen with 25G or other port types with other remote devices.

16.0(5h)

CSCwh46885

When the fabric nodes are using ACI release 15.2(7g), the N9K-C9348 switch fails during the POAP DHCP discover phase.

16.0(5h)

CSCwh48737

Bounce entry for an endpoint may point to wrong TEP address, leading to connectivity failures.

16.0(5h)

CSCwh60203

There is unexpected behavior with the DHCP relay when using DHCP relay with the "DHCP server preference" feature. The issue is triggered by deleting one of the bridge domains that use the DHCP relay label. This causes the Cisco APIC to remove the DHCP server's SVI from all switches involved in the change, which means that all other bridge domains on those switches can no longer do DHCP relay.

16.0(5h)

CSCwh64732

The hardware is DOM-capable (Y), but DOM information is not showing up for the command: "show int ethernet 1/X transceiver details"

16.0(5h)

CSCwh67412

ACI displays fan speed percentage incorrectly.

16.0(5h)

CSCwh71704

When one of the vPC peers reloads and comes up, the non-reloaded peer is seen to be suspending the vPC interfaces.

16.0(5h)

CSCwh72876

The EPM process crashed when there was no disk space was available at /var/sysmgr/tmp_logs/.

16.0(5h)

CSCwh73346

After removing service graph association from a shared L3Out contract, traffic will be dropped on the border leaf switch.

16.0(5h)

CSCwh73782

Traffic that is forwarded by a spine switch toward a leaf switch is dropped by one of the spine switch's fabric modules. On this fabric module where packets are dropped, the TEP of the destination leaf switch is not programmed in FIB and HAL.

16.0(5h)

CSCwh75559

tcpdump on the tahoe0 interface randomly has incorrect time stamps (sometimes an old time stamp).

16.0(5h)

CSCwh76977

The device reloaded unexpectedly because of "sdkhal hap reset" after the "show platform internal hal l3 intfdb" command was executed in command-line interface in vsh_lc mode.

16.0(5h)

CSCwh76996

While inserting or reloading a leaf switch, its vPC peer will try to bring up the vPC when the peer IP is 0.0.0.0.

16.0(5h)

CSCwh77467

SDKHAL crashes are seen on an ACI spine N9K-C9364D-GX2A switch running 15.2(7g).  A core file is also generated.

16.0(5h)

CSCwh77567

If there is a single endpoint move local-to-remote or remote-to-local within the detection interval, then the move count is not reset. This may lead to an endpoint being incorrectly marked as rogue on the node.

16.0(5h)

CSCwh78987

Breakout ports configured as port channel members are no longer part of the port channel post clean reload.

16.0(5h)

CSCwh79632

Uplink ports flap frequently on leaf switch. Eth1/51 may be observed to flap more frequently than other ports.

16.0(5h)

CSCwh81430

After reloading a Cisco 93108TC-FX3P switch that was upgraded to a release earlier than 5.2(8h), random copper/RJ45 interfaces might not come up. This can occur for port 1/48 on multiple leaf switches in the fabric. A fault F0532 is raised for these ports on the APIC GUI, with the reason being shown as "not-connected".

16.0(5h)

CSCwh84746

An endpoint moves between POD1 and POD2. On POD3, the endpoint is going to the FREEZE state and on POD1 and POD2 its not moving to the FREEZE state after the move stops.

16.0(5h)

CSCwh91351

There is an issue with FX3 switches and the following scenario:

* Leaf 207-208 on a vPC.

* The source and destination are connected to these pairs through a vPC.

* The source and destination are on different VRF instances. So, VRF leaking is in place to communicate with these two endpoints.

When return traffic hits leaf switch 207, communication is successful. When return traffic hits leaf switch 208, communication is dropped. When communication is dropped, it hits rule 5048.

16.0(5h)

CSCwh92659

An endpoint may become out of sync between spine switches in different pods. Each spine switch may point to a local pod TEP as the tunnel next hop for the leaf switches. The issue does not get cleared until the incorrect pod spine switches age/delete their COOP entry.

16.0(5h)

CSCwi04853

While configuring the "Spine Supervisor Module On-Demand Diag" from the APIC GUI, the spine switch will unexpectedly reboot due to a device_test hap reset. After the switch reboots, F0404 will be raised for each diagnostic.

16.0(5h)

CSCwi05613

This issue can be seen when BGP L3Outs have import or export route maps configured using match statements based on regular expressions (for example matching of regex: (65[2-3]01:102..). If BGP regex communities are configured, both the deny and permit statements are not always honored and there are unexpected results.From the BGP and routing table perspective, routes come in with an extended community value that are being permitted incorrectly or denied incorrectly based on the ACI route map that is configured.

16.0(5h)

CSCwi17513

This issue occurs when a border leaf switch reboots and rejoins the fabric after reloading. At this point, both port tracking and PIM overload timers are active, preventing the rebooted border leaf switch from sending PIM hellos.After the PIM overload timer expires, the border leaf switch starts sending PIM hello through the fabric tunnel interface and stripe-winners on other border leaf switches are recalculated. If at this point the L3Out is still down due to port tracking, it can happen that for some VRF instances, the PIM join over the fabric tunnel interface to the other border leaf switch is not sent. This leads to a multicast traffic loss until the next PIM join is sent.

16.0(5h)

CSCwi18214

A leaf switch repeatedly reloads due to policyelem abnormal exit and HAP reset.

16.0(5h)

CSCwi21299

When there is an FCOE interface flap or speed change due to inserting an SFP, this affects the dataplane of other FCOE interfaces that share the same MAC address.

16.0(5h)

CSCwi31656

1. SPAN traffic does not go out from the destination SPAN port after the peer interface flaps.

2. MAC credit goes to zero for the SPAN destination port after the peer interface flaps.

3. You also might see the native interface that is part of same MAC address hardware in which the SPAN destination port is configured stop sending control plane packets because the CPU buffer is exhausted by the SPAN destination port.

16.0(5h)

CSCuo37016

When configuring the output span on a FEX Hif interface, all the layer 3 switched packets going out of that FEX Hif interface are not spanned. Only layer 2 switched packets going out of that FEX Hif are spanned.

16.0(5h) and later

CSCup65586

The show interface command shows the tunnel's Rx/Tx counters as 0.

16.0(5h) and later

CSCup82908

The show vpc brief command displays the wire-encap VLAN Ids and the show interface .. trunk command displays the internal/hardware VLAN IDs. Both VLAN IDs are allocated and used differently, so there is no correlation between them.

16.0(5h) and later

CSCup92534

Continuous "threshold exceeded" messages are generated from the fabric.

16.0(5h) and later

CSCuq39829

Switch rescue user ("admin") can log into fabric switches even when TACACS is selected as the default login realm.

16.0(5h) and later

CSCuq46369

An extra 4 bytes is added to the untagged packet with Egress local and remote SPAN.

16.0(5h) and later

CSCuq77095

When the command show ip ospf vrf <vrf_name> is run from bash on the border leaf switch, the checksum field in the output always shows a zero value.

16.0(5h) and later

CSCuq92447

When modifying the L2Unknown Unicast parameter on a Bridge Domain (BD), interfaces on externally connected devices may bounce. Additionally, the endpoint cache for the BD is flushed and all endpoints will have to be re-learned.

16.0(5h) and later

CSCur81822

The access-port operational status is always "trunk".

16.0(5h) and later

CSCus18541

An MSTP topology change notification (TCN) on a flood domain (FD) VLAN may not flush endpoints learned as remote where the FD is not deployed.

16.0(5h) and later

CSCus43167

Any TCAM that is full, or nearly full, will raise the usage threshold fault. Because the faults for all TCAMs on leaf switches are grouped together, the fault will appear even on those with low usage.

Workaround:  Review the leaf switch scale and reduce the TCAM usage. Contact TAC to isolate further which TCAM is full.

16.0(5h) and later

CSCut59020

If Backbone and NSSA areas are on the same leaf switch, and default route leak is enabled, Type-5 LSAs cannot be redistributed to the Backbone area.

16.0(5h) and later

CSCuu66310

If a bridge domain "Multi Destination Flood" mode is configured as "Drop", the ISIS PDU from the tenant space will get dropped in the fabric.

16.0(5h) and later

CSCuv57302

Atomic counters on the border leaf switch do not increment for traffic from an endpoint group going to the Layer 3 out interface.

16.0(5h) and later

CSCuv57315

Atomic counters on the border leaf switch do not increment for traffic from the Layer 3 out interface to an internal remote endpoint group.

16.0(5h) and later

CSCuv57316

TEP counters from the border leaf switch to remote leaf switch nodes do not increment.

16.0(5h) and later

CSCux97329

With the common pervasive gateway, only the packet destination to the virtual MAC is being properly Layer 3 forwarded. The packet destination to the bridge domain custom MAC fails to be forwarded. This is causing issues with certain appliances that rely on the incoming packets’ source MAC to set the return packet destination MAC.

16.0(5h) and later

CSCuy02543

Bidirectional Forwarding Detection (BFD) echo mode is not supported on IPv6 BFD sessions carrying link-local as the source and destination IP address. BFD echo mode also is not supported on IPv4 BFD sessions over multihop or VPC peer links.

16.0(5h) and later

CSCuy06749

Traffic is dropped between two isolated EPGs.

16.0(5h) and later

CSCuy22288

The iping command’s replies get dropped by the QOS ingress policer.

16.0(5h) and later

CSCuy61018

The default minimum bandwidth is used if the BW parameter is set to "0", and so traffic will still flow.

16.0(5h) and later

CSCuz13529

With the N9K-C93180YC-EX switch, drop packets, such as MTU or storm control drops, are not accounted for in the input rate calculation.

16.0(5h) and later

CSCuz47058

SAN boot over a virtual port channel or traditional port channel does not work.

16.0(5h) and later

CSCvb39965

Slow drain is not supported on FEX Host Interface (HIF) ports.

16.0(5h) and later

CSCvd11146

Bridge domain subnet routes advertised out of the Cisco ACI fabric through an OSPF L3Out can be relearned in another node belonging to another OSPF L3Out on a different area.

16.0(5h) and later

CSCvn94400

There is a traffic blackhole that lasts anywhere from a few seconds to a few mins after a border leaf switch is restored.

16.0(5h) and later

CSCvp04772

During an upgrade on a dual-SUP system, the standby SUP may go into a failed state.

16.0(5h) and later

CSCvq71034

There is a policy drop that occurs with L3Out transit cases.

16.0(5h) and later

CSCvr12912

A switch reloads due to a sysmgr heartbeat failure and sysmgr HAP reset.

16.0(5h) and later

CSCvr61096

In a port group that has ports of mixed speeds, the first port in the port group that has valid optics present and is not in the admin down state is processed. The ports that come up later are brought up if they are using the same speed; otherwise, they are put in the hw-disabled state.

For example, if ports 14 and 15 are up and are using the 100G speed, then if ports 13 and 16 are using the 40G speed, these ports will be put in the hw-disabled state. After reloading or upgrading, you might not have the same interfaces in the port group in the UP state and in the hw-disabled state as you did before the reload or upgrade.

16.0(5h) and later

CSCvt61851

When MPLS VRF stats (egress) is compared with Layer 2 interface egress stats, we can find that the packet count matches for both while there could be a discrepancy with the bytes count.

16.0(5h) and later

CSCvu02371

The DEI value in a Layer 2 header of spanned Tx packets from an MPLS interface might not have the same value as the actual data path packet.

16.0(5h) and later

CSCvu42069

The event log shows VTEP tunnel down and up events. The down time and up time are the same, and there is no fault message.

16.0(5h) and later

CSCvx62362

When a service device is connected behind an L3Out in 2-arm mode with both legs on the same leaf switch, tracking packets get dropped.

16.0(5h) and later

CSCvy06135

The leaf switch techsupport with a specified time range fails when the space "/mnt/ifc/log" gets filled up by more than 80%.

16.0(5h) and later

CSCvy71586

400G port is automatically broken out into 4 breakout ports. After performing online insertion and removal (OIR) of a 400G transceiver, one of the breakout ports has the "SFP not inserted" or "SFP missing" state.

16.0(5h) and later

CSCvz84284

Upon deletion of a VRF instance that has a micro-BFD port channel in the "up" state, all the member ports of the port channel that were in the "up" state prior to the VRF instance deletion go to the "down" state. The micro-BFD port channels never transition back to the "up" state.

16.0(5h) and later

CSCwa78857

Cisco APIC allows you to configure any number of DHCP relay addresses. However, the maximum number of relay address that can be supported is 16 from a switch. If a 17th DHCP provider is added to the DHCP label, it will not be used even if one of first 16 DHCP providers is removed.

16.0(5h) and later

CSCwd64518

A virtual machine has connectivity loss when the destination virtual machine is migrated using vMotion. This issue happens only if microsegmentation is enabled on the EPG.

16.0(5h) and later

CSCwd95467

With N9K-X9400-16W LEM, a pair of odd and even number ports such as port 1/1 and 1/2 must work as the same link type: downlink or fabric link because of CSCwd95467. This consideration is not applicable to N9K-X9400-8D.

16.0(5h) and later

CSCwe08179

A peer vPC leg goes down after swapping a 16 port LEM with an 8 port LEM. The following error shows in the "show vpc" output: "Peer does not have corresponding vPC". The leg on the peer switch immediately comes up, but traffic is still disrupted.

16.0(5h) and later

CSCwe33967

After deleting or adding a VRF instance, the BGP peer session picks up the default timer values instead of the configured values. This is evidenced by the holdIntvl and kaIntvl values in the bgpPeerEntry managed object in the policy engine. The issue happens intermittently.

16.0(5h) and later

CSCwe41508

As a result of new features, certain PIDs running ACI release 6.0(5) software in 32-bit architecture will see increase in memory consumption and their process virtual address space.

This particular issue is seen with a trigger of 500 bridge domain (BD) deletions and addition in a scale configuration of 64k fvrspath scale, 1980 BDs  along with 123k policycam entries. In release 6.0(5) with a 32-bit image, process memory could run close to the limit of 4GB.”

In this scenario, EPM is running at 3.9GB. During the vlan creation as part of the above trigger, EPM attempts to retrieve sclass corresponding to the vlan through DME and DME access is failing. Memory map failures are seen through the instance of EPM.

The DME failure may be due to mmap failures.

16.0(5h) and later

CSCwe97510

When AN On-Enforce is enabled on QDD-4ZQ100G-COPPER breakouts on switches with -GX or -GX2 in the product ID, the links do not come up.

16.0(5h) and later

CSCwf88389

After an SVI member port flap, ECMP hashing no longer uses the flapped SVI's path and instead uses other SVI paths.

16.0(5h) and later

CSCwf90351

With the rogue endpoint feature, a MAC address gets flagged as rogue. A leaf switch ignores any further moves of the rogue endpoint for 15 minutes, which can cause an outage. Traffic coming from a FEX vPC carries the Physical Tunnel Endpoint (PTEP) as the source IP address of the outer header (SIPo) instead of the FEX vPC Tunnel Endpoint (TEP).

16.0(5h) and later

N/A

Load balancers and servers must be Layer 2 adjacent. Layer 3 direct server return is not supported. If a load balancer and servers are Layer 3 adjacent, then they have to be placed behind the Layer 3 out, which works without a specific direct server return virtual IP address configuration.

16.0(5h) and later

N/A

IPN should preserve the CoS and DSCP values of a packet that enters IPN from the ACI spine switches. If there is a default policy on these nodes that change the CoS value based on the DSCP value or by any other mechanism, you must apply a policy to prevent the CoS value from being changed. At the minimum, the remarked CoS value should not be 4, 5, 6, or 7. If CoS is changed in the IPN, you must configure a DSCP-CoS translation policy in the APIC for the pod that translates queuing class information of the packet into the DSCP value in the outer header of the iVXLAN packet. You can also embed CoS by enabling CoS preservation. For more information, see the Cisco APIC and QoS KB article.

16.0(5h) and later

N/A

The following properties within a QoS class under "Global QoS Class policies" should not be changed from their default value and is only used for debugging purposes:

MTU (default – 9216 bytes)

Queue Control Method (default – Dynamic)

Queue Limit (default – 1522 bytes)

Minimum Buffers (default – 0)

16.0(5h) and later

N/A

The modular chassis Cisco ACI spine nodes, such as the Cisco Nexus 9508, support warm (stateless) standby where the state is not synched between the active and the standby supervisor modules. For an online insertion and removal (OIR) or reload of the active supervisor module, the standby supervisor module becomes active, but all modules in the switch are reset because the switchover is stateless. In the output of the show system redundancy status command, warm standby indicates stateless mode.

16.0(5h) and later

N/A

When a recommissioned APIC controller rejoins the cluster, GUI and CLI commands can time out while the cluster expands to include the recommissioned APIC controller.

16.0(5h) and later

N/A

If connectivity to the APIC cluster is lost while a switch is being decommissioned, the decommissioned switch may not complete a clean reboot. In this case, the fabric administrator should manually complete a clean reboot of the decommissioned switch.

16.0(5h) and later

N/A

Before expanding the APIC cluster with a recommissioned controller, remove any decommissioned switches from the fabric by powering down and disconnecting them. Doing so will ensure that the recommissioned APIC controller will not attempt to discover and recommission the switch.

16.0(5h) and later

N/A

Multicast router functionality is not supported when IGMP queries are received with VxLAN encapsulation.

16.0(5h) and later

N/A

IGMP Querier election across multiple Endpoint Groups (EPGs) or Layer 2 outsides (External Bridged Network) in a given bridge domain is not supported. Only one EPG or Layer 2 outside for a given bridge domain should be extended to multiple multicast routers if any.

16.0(5h) and later

N/A

The rate of the number of IGMP reports sent to a leaf switch should be limited to 1000 reports per second.

16.0(5h) and later

N/A

Unknown IP multicast packets are flooded on ingress leaf switches and border leaf switches, unless "unknown multicast flooding" is set to "Optimized Flood" in a bridge domain. This knob can be set to "Optimized Flood" only for a maximum of 50 bridge domains per leaf switch.

If "Optimized Flood" is enabled for more than the supported number of bridge domains on a leaf switch, follow these configuration steps to recover:

Set "unknown multicast flooding" to "Flood" for all bridge domains mapped to a leaf switch.

Set "unknown multicast flooding" to "Optimized Flood" on needed bridge domains.

16.0(5h) and later

N/A

Traffic destined to Static Route EP VIPs sourced from N9000 switches (switches with names that end in -EX) might not function properly because proxy route is not programmed.

16.0(5h) and later

N/A

An iVXLAN header of 50 bytes is added for traffic ingressing into the fabric. A bandwidth allowance of (50/50 + ingress_packet_size) needs to be made to prevent oversubscription from happening. If the allowance is not made, oversubscription might happen resulting in buffer drops.

16.0(5h) and later

N/A

An IP/MAC Ckt endpoint configuration is not supported in combination with static endpoint configurations.

16.0(5h) and later

N/A

An IP/MAC Ckt endpoint configuration is not supported with Layer 2-only bridge domains. Such a configuration will not be blocked, but the configuration will not take effect as there is no Layer 3 learning in these bridge domains.

16.0(5h) and later

N/A

An IP/MAC Ckt endpoint configuration is not supported with external and infra bridge domains because there is no Layer 3 learning in these bridge domains.

16.0(5h) and later

N/A

An IP/MAC Ckt endpoint configuration is not supported with a shared services provider configuration. The same or overlapping prefix cannot be used for a shared services provider and IP Ckt endpoint. However, this configuration can be applied in bridge domains having shared services consumer endpoint groups.

16.0(5h) and later

N/A

An IP/MAC Ckt endpoint configuration is not supported with dynamic endpoint groups. Only static endpoint groups are supported.

16.0(5h) and later

N/A

No fault will be raised if the IP/MAC Ckt endpoint prefix configured is outside of the bridge domain subnet range. This is because a user can configure bridge domain subnet and IP/MAC Ckt endpoint in any order and so this is not error condition. If the final configuration is such that a configured IP/MAC Ckt endpoint prefix is outside all bridge domain subnets, the configuration has no impact and is not an error condition.

16.0(5h) and later

N/A

Dynamic deployment of contracts based on instrImmedcy set to onDemand/lazy not supported; only immediate mode is supported.

16.0(5h) and later

N/A

When a server and load balancer are on the same endpoint group, make sure that the Server does not generate ARP/GARP/ND request/response/solicits. This will lead to learning of LB virtual IP (VIP) towards the Server and defeat the purpose of DSR support.

16.0(5h) and later

N/A

Direct server return is not supported for shared services. Direct server return endpoints cannot be spread around different virtual routing and forwarding (VRF) contexts.

16.0(5h) and later

N/A

Configurations for a virtual IP address can only be /32 or /128 prefix.

16.0(5h) and later

N/A

Client to virtual IP address (load balancer) traffic always will go through proxy-spine because fabric data-path learning of a virtual IP address does not occur.

16.0(5h) and later

N/A

GARP learning of a virtual IP address must be explicitly enabled. A load balancer can send GARP when it switches over from active-to-standby (MAC changes).

16.0(5h) and later

N/A

Learning through GARP will work only in ARP Flood Mode.

16.0(5h) and later

N9K-X9716D-GX

4

4

No

No

4

4

N9K-X9736C-FX

5

5

5

5

5

5

N9K-X9736Q-FX

5

5

5

5

5

5

N9K-X9732C-EX

No

No

4

4

4

4

N9K-X9716D-GX

If you connect a Cisco N9K-X9716D-GX breakout port to a non-Cisco ACI peer, such as a standalone switch capable of 100G, the link comes up and LLDP is detected. However, this is an unsupported scenario, but no fault is generated.

N9K-C9408

This switch has the following limitations:

N9K-C9364C

You can deploy multipod or Cisco ACI Multi-Site separately (but not together) on the Cisco N9K-9364C switch starting in the 3.1 release.  You can deploy multipod and Cisco ACI Multi-Site together on the Cisco N9K-9364C switch starting in the 3.2 release.

A 930W-DC PSU (NXA-PDC-930W-PE or NXA-PDC-930W-PI) is supported in redundancy mode if 3.5W QSFP+ modules or passive QSFP cables are used and the system is used in 40C ambient temperature or less; for other optics or a higher ambient temperature, a 930W-DC PSU is supported only with 2 PSUs in non-redundancy mode.

1-Gigabit QSA is not supported on ports 1/49-64.

This switch supports the following PSUs:

N9K-C9364D-GX2A

Ports 65 and 66 do not support flow telemetry nor NetFlow.

N9K-C9348D-GX2A

Ports 65 and 66 do not support flow telemetry nor NetFlow.

N9K-C9332D-GX2B

The following information applies to this switch:

◦    10G GLC-T optics

◦    100M speed

◦    Flow telemetry

◦    NetFlow

◦    MACsec, PTP, and SyncE

◦    PFC and no-drop classes

◦    FC and FCoE mode

N9K-C9408

This switch has the following limitations:

N9K-C9364C-GX

This switch has the following limitations:

N9K-C93600CD-GX

This switch has the following limitations:

N9K-C9364D-GX2A

Ports 65 and 66 do not support flow telemetry nor NetFlow.

N9K-C9348D-GX2A

Ports 65 and 66 do not support flow telemetry nor NetFlow.

N9K-C9332D-GX2B

The following information applies to this switch:

◦    10G GLC-T optics

◦    100M speed

◦    Flow telemetry

◦    NetFlow

◦    MACsec, PTP, and SyncE

◦    PFC and no-drop classes

◦    FC and FCoE mode

N9K-C9316D-GX

Auto-negotiation and forward error correction are not supported when you use this switch is as a leaf switch.

N9K-C93180YC-FX3

The following information applies to this switch:

N9K-C9336C-FX2

The following information applies to this switch:

N9K-C93240YC-FX2

The following information applies when this switch is configured with port-side intake airflow:

The following information applies when this switch is configured with port-side exhaust airflow:

The following information applies regardless of the airflow direction:

N9K-C93360YC-FX2

The following information applies to this switch:

N9K-C9348GC-FXP

This switch supports the following PSUs:

The following information applies to this switch:

N9K-C93180YC-FX-24

This switch does not support the 10G GLC-T optic.

N9K-C93180YC-FX

The following information applies to this switch:

N9K-C93180YC-EX-24

This switch does not support the 10G GLC-T optic.

N9K-C93180YC-EX

The following information applies to this switch:

N9K-C93180LC-EX

This switch has the following limitations:

N9K-C9332C

Switch

Yes, only on the last 8 ports

N9K-C9364C

Switch

Yes, only on the last 16 ports

N9K-X9736C-FX

Line Card

Yes, only on the last 8 ports