Cisco Nexus 9000 ACI-Mode Switches Release Notes, Release 12.2(3)

July 6, 2021

In the Supported Hardware section, added the NXA-PAC-500W-PI and NXA-PAC-500W-PE PSUs.

June 24, 2021

Added open issue CSCvu07844.

January 19, 2021

In the Known Behaviors section, changed the following sentence:

The Cisco Nexus 9508 ACI-mode switch supports warm (stateless) standby where the state is not synched between the active and the standby supervisor modules.

To:

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.

March 13, 2020

12.2(3j): In the Resolved Bugs section, added bug CSCvr98827.

September 20, 2019

In the Usage Guidelines section, added the following bullet:

■      A 25G link that is using the IEEE-RS-FEC mode can communicate with a link that is using the CL16-RS-FEC mode. There will not be a FEC mismatch and the link will not be impacted.

September 11, 2019

In the Supported Hardware section, for the N9K-C93108TC-FX and N9K-C93180YC-FX switches, added the following note:

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.

August 14, 2019

12.2(3j): In the Open Bugs section, added bug CSCvp92269.

August 6, 2019

12.2(3r): In the Open Bugs section, added bug CSCvm96490.

July 31, 2019

In the Compatibility Information section, added the following bullet:

■      On Cisco ACI platforms, 25G copper optics do not honor auto-negotiation, and therefore auto-negotiation on the peer device (ESX or standalone) must be disabled to bring up the links.

January 30, 2019

12.2(3j): In the Open Bugs section, added bug CSCvn69340.

January 28, 2019

12.2(3j): In the Open Bugs section, added bug CSCvi76161.

October 24, 2018

12.2(3j): In the Open Bugs section, added bug CSCvm66008.

June 7, 2018

12.2(3j): In the Open Bugs section, added bug CSCvg35892.

April 24, 2018

12.2(3j): In the Open Bugs section, added bug CSCvi57920.

February 19, 2018

12.2(3t): Release 12.2(3t) became available. Added the resolved bugs for this release.

December 21, 2017

12.2(3s): Release 12.2(3s) became available. Added the resolved bugs for this release.

December 6, 2017

12.2(3j): In the Known Behaviors section, added bug CSCvd63567.

December 2, 2017

12.2(3r): Release 12.2(3r) became available. Added the resolved bugs for this release.

November 13, 2017

12.2(3p): Release 12.2(3p) became available. Added the resolved bugs for this release.

September 7, 2017

12.2(3j): Release 12.2(3j) became available.

Chassis

N9K-C9504

Cisco Nexus 9504 chassis with 4 I/O slots

Chassis

N9K-C9508

Cisco Nexus 9508 chassis with 8 I/O slots

Chassis component

N9K-C9508-FAN

Fan tray

Chassis component

N9k-PAC-3000W-B

Cisco Nexus 9500 3000W AC power supply, port side intake

Pluggable module (GEM)

N9K-M12PQ

12-port or 8-port

Pluggable module (GEM)

N9K-M6PQ

6-port

Pluggable module (GEM)

N9K-M6PQ-E

6-port, 40 Gigabit Ethernet expansion module

Spine switch

N9K-C9336PQ

Cisco Nexus 9336PQ switch, 36-port 40 Gigabit Ethernet QSFP

Spine switch

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

Spine switch

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

Spine switch

N9K-C9516

Cisco Nexus 9516 switch with 16 line card slots

Note: This switch supports up to 10 line cards.

Spine switch fan

N9K-C9300-FAN3

Port side intake fan

Spine switch fan

N9K-C9300-FAN3-B

Port side exhaust fan

Spine switch module

N9K-C9504-FM

Cisco Nexus 9504 fabric module supporting 40 Gigabit line cards

Spine switch module

N9K-C9504-FM-E

Cisco Nexus 9504 fabric module supporting 100 Gigabit line cards

Spine switch module

N9K-C9508-FM

Cisco Nexus 9508 fabric module supporting 40 Gigabit line cards

Spine switch module

N9K-C9508-FM-E

Cisco Nexus 9508 Fabric module supporting 100 Gigabit line cards

Spine switch module

N9K-X9732C-EX

Cisco Nexus 9500 32-port, 40/100 Gigabit Ethernet QSFP28 aggregation module

Spine switch module

N9K-X9736PQ

Cisco Nexus 9500 36-port, 40 Gigabit Ethernet QSFP aggregation module

Switch module

N9K-SC-A

Cisco Nexus 9500 Series system controller

Switch module

N9K-SUP-A

Cisco Nexus 9500 Series supervisor module

Switch module

N9K-SUP-B

Cisco Nexus 9500 Series supervisor module

Top-of-rack (ToR) leaf switch

N9K-C93108TC-EX

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

Top-of-rack (ToR) leaf switch

N9K-C93108TC-FX

Cisco Nexus 9300 platform switch with 48 1/10GBASE-T (copper) APIC-facing 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.

Top-of-rack (ToR) leaf switch

N9K-C93120TX

Cisco Nexus 9300 platform switch with 96 1/10GBASE-T (copper) APIC-facing ports and 6-port 40-Gigabit Ethernet QSFP spine-facing ports

Top-of-rack (ToR) leaf switch

N9K-C93128TX

Cisco Nexus 9300 platform switch with 96 1/10GBASE-T (copper) APIC-facing ports and 6 or 8 40-Gigabit Ethernet QSFP spine-facing ports

Top-of-rack (ToR) leaf switch

N9K-C93180LC-EX

Cisco Nexus 9300 platform switch with 24 40-Gigabit APIC-facing ports and 6 10/40/100-Gigabit QSFP28 spine-facing ports

Note: This switch has the following limitations:

·       This release does not support 1 Gbps for QSA.

·       The top and bottom ports must use the same speed. If there is a speed mismatch, the top port takes precedence and bottom port will be error disabled. Both ports both must be used in either the 40 Gbps or 10 Gbps mode.

·       Ports 26 and 28 are hardware disabled.

·       This release supports 40 and 100 Gbps for the front panel ports. The uplink ports can be used at the 100 Gbps speed.

Top-of-rack (ToR) leaf switch

N9K-C93180YC-EX

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

Top-of-rack (ToR) leaf switch

N9K-C93180YC-FX

Cisco Nexus 9300 platform switch with 48 10/25-Gigabit Ethernet SFP28 APIC-facing 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.

Top-of-rack (ToR) leaf switch

N9K-C9332PQ

Cisco Nexus 9332PQ Top-of-rack (ToR) Layer 3 switch with 32 40-Gigabit Ethernet QSFP+ APIC-facing ports

Top-of-rack (ToR) leaf switch

N9K-C9372PX

Cisco Nexus 9372PX Top-of-rack (ToR) Layer 3 switch with 48 10GBASE-T (copper) Ethernet SFP+ APIC-facing ports and 6 40-Gbps Ethernet QSFP+ spine-facing ports

Note: Only the downlink ports 1-16 and 33-48 are capable of supporting SFP1-10G-ZR SFP+.

Top-of-rack (ToR) leaf switch

N9K-C9372PX-E

Cisco Nexus 9372PX-E Top-of-rack (ToR) Layer 3 switch with 48 10GBASE-T (copper) Ethernet SFP+ APIC-facing ports and 6 40-Gbps Ethernet QSFP+ spine-facing ports

Note: Only the downlink ports 1-16 and 33-48 are capable of supporting SFP1-10G-ZR SFP+.

Top-of-rack (ToR) leaf switch

N9K-C9372TX

Cisco Nexus 9372TX Top-of-rack (ToR) Layer 3 switch with 48 1/10GBASE-T (copper) APIC-facing ports and 6 40-Gbps Ethernet QSFP spine-facing ports

Top-of-rack (ToR) leaf switch

N9K-C9372TX-E

Cisco Nexus 9372TX-E Top-of-rack (ToR) Layer 3 switch with 48 10GBASE-T (copper) APIC-facing ports and 6 40-Gbps Ethernet QSFP+ spine-facing ports

Top-of-rack (ToR) leaf switch

N9K-C9396PX

Cisco Nexus 9300 platform switch with 48 1/10GBASE-T (copper) SFP+ APIC-facing ports and 6 or 12 40-Gigabit Ethernet QSFP spine-facing ports

Top-of-rack (ToR) leaf switch

N9K-C9396TX

Cisco Nexus 9300 platform switch with 48 1/10GBASE-T (copper) APIC-facing ports and 6 or 12 40-Gigabit Ethernet QSFP spine-facing ports

Top-of-rack (ToR) leaf switch fan

NXA-FAN-30CFM-B

Port side intake fan

Top-of-rack (ToR) leaf switch fan

NXA-FAN-30CFM-F

Port side exhaust fan

Top-of-rack (ToR) leaf switch power supply unit

N9K-PAC-1200W

1200W AC Power supply, port side intake pluggable

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

Top-of-rack (ToR) leaf switch power supply unit

N9K-PAC-1200W-B

1200W AC Power supply, port side exhaust pluggable

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

Top-of-rack (ToR) leaf switch power supply unit

N9K-PAC-650W

650W AC Power supply, port side intake pluggable

Top-of-rack (ToR) leaf switch power supply unit

N9K-PAC-650W-B

650W AC Power supply, port side exhaust pluggable

Top-of-rack (ToR) leaf switch power supply unit

N9K-PUV-1200W

1200W HVAC/HVDC dual-direction airflow power supply

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

Top-of-rack (ToR) leaf switch power supply unit

N9K-PUV-3000W-B

3000W AC Power supply, port side exhaust pluggable

Top-of-rack (ToR) leaf switch power supply unit

NXA-PAC-1200W-PE

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

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

Top-of-rack (ToR) leaf switch power supply unit

NXA-PAC-1200W-PI

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

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

Top-of-rack (ToR) leaf switch power supply unit

NXA-PAC-500W-PE

500W AC Power supply, port side exhaust pluggable

Top-of-rack (ToR) leaf switch power supply unit

NXA-PAC-500W-PI

500W AC Power supply, port side intake pluggable

Top-of-rack (ToR) leaf switch power supply unit

UCSC-PSU-930WDC V01

Port side exhaust DC power supply compatible with all ToR leaf switches

Top-of-rack (ToR) leaf switch power supply unit

UCS-PSU-6332-DC

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

N2K-B22DELL-P

B22 FEX for Dell

N2K-B22HP-P

B22 FEX for HP

N2K-B22IBM-P

B22 FEX for IBM

N2K-C2248PQ-10GE

Cisco Nexus 2248PQ 10GE Fabric Extender, 2PS, 4 Fan Module, 48x1/10GE (req SFP/SFP+) + 4x40G QSFP+(req QSFP+), choice of airflow and power supply

N2K-C2248TP-1GE

Cisco Nexus 2248TP Series 1GE Fabric Extender, 2 AC PS, 1 Fan Module (Standard Airflow/port side exhaust), 48x100/1000Base-T + 4x10GE (req SFP+), same as N2K-C2248TP

N2K-C2248TP-E-1GE

Cisco Nexus 2248TP-E Series 1GE Fabric Extender, 2PS, 1 Fan Module, 48x100/1000Base-T + 4x10GE (req SFP+), 32MB buffer, choice of airflow and power supply

N2K-C2332TQ

Cisco Nexus 2332TQ 10G BASE T Fabric Extender, 2PS, 3 Fan Module, 48x100M/1/10GE + 4x40G QSFP+(req QSFP+), choice of airflow and power supply

N2K-C2348TQ

Cisco Nexus 2348TQ 10G BASE T Fabric Extender, 2PS, 3 Fan Module, 48x100M/1/10GE + 6x40G QSFP+(req QSFP+), choice of airflow and power supply

N2K-C2348UPQ

48 100Mῖ/1/10 Gigabit Ethernet and Unified Port host interfaces (SFP+) and up to 6ῖ QSFP+ 10/40 Gigabit Ethernet fabric interfaces

N2K-C2232PP-10GE

Cisco Nexus 2232PP Series 10GE Fabric Extender, 2 AC PS, 1 Fan Module (Standard Airflow/port side exhaust), 32x1/10GE (required SFP/SFP+) + 8x10GE (required SFP+), same as N2K-C2232PP

N2K-C2232TM-E-10GE

Cisco Nexus 2232TM-E Series 10GBASE-T Fabric Extender, 2PS, 1 Fan Module, 32x1/10GBase-T + 8x10GE Module (required SFP+), choice of airflow and power supply

CSCvm96490

After a policy upgrade, fault "F1583 - BIOS version mismatch detected." is present for N9K-C93108TC-EX and N9K-C93180YC-EX switches.

12.2(3r) and later

CSCve06334

MAC and IP endpoints are not learned on the local vPC pair.

12.2(3j) and later

CSCvf09313

In the 12.2(2i) release, the BPDU filter only prevents interfaces from sending BPDUs, but does not prevent interfaces from receiving BPDUs.

12.2(3j) and later

CSCvf85014

Multicast traffic loss might occur during spine switch upgrade/reload when at least one fabric link port from spine switch to ToR is in "admin down" state.

12.2(3j) and later

CSCvg35892

There is a delay in internal process communication of over a minute due to a timeout (timeout period is 60 seconds). This can manifest itself in different ways. In one way, the Policy Element sent a delete/create request for a VLAN to the VLAN manager, but the VLAN manager did not process the request until the initial request timed out. This resulted in an outage that lasted a little over a minute while changing a BD from Unknown Unicast Flood to Hardware Proxy.

12.2(3j) and later

CSCvi57920

A UCS 1225 vNIC goes down after changing the peer Cisco ACI leaf node name.

12.2(3j) and later

CSCvi76161

A version mismatch between Cisco ACI leaf switches causes the EPM process to crash and a HAP reset to occur.

12.2(3j) and later

CSCvm66008

When you have two NSSA areas deployed on a vPC leaf switch pair that also see each other as OSPF peers and both L3Outs have the default route leak policy configured, then if you delete one of the L3Outs, the following things occur:

OSPF generates the default route without a tag

The peer installs that route in RIB

The peer redistributes the route into BGP

The peer advertises the route to rest of the leaf switches

This issue blackholes all traffic that uses the default route.

12.2(3j) and later

CSCvn69340

The BFD session does not get instantiated under some circumstances in one of the VPC legs for static routes.

12.2(3j) and later

CSCvp50075

A leaf switch experiences an unexpected reload due to a HAP reset.

12.2(3j) and later

CSCvp92269

Running a Qualys security scan results in the following message:

CWE - 693 Protection Mechanism Failure -

"HTTP Security Header Not Detected"

12.2(3j) and later

CSCvr98827

Some of the control plane packets are incorrectly classified as the user class and are reported as dropped in single chip spine switches. The statistics are incorrect because the packets are not actually dropped.

12.2(3j) and later

CSCvs18150

After a certain set of steps, it is observed that the deny-external-tag route-map used for transit routing loop prevention gets set back to the default tag 4294967295. Since routes arriving in Cisco ACI with this tag are denied from being installed in the routing table, if the VRF table that has the route-tag policy is providing transit for another VRF table in Cisco ACI (for instance and inside and outside VRF with a firewall connecting them) and the non-transit VRF table has the default route-tag policy, routes from the non-transit VRF table would not be installed in the transit VRF table.

This bug is also particularly impactful in scenarios where transit routing is being used and OSPF or EIGRP is used on a vPC border leaf switch pair. vPC border leaf switches peer with each other, so if member A gets a transit route from BGP, redistributes into OSPF, and then advertises to member B (since they are peers)...without a loop prevention mechanism, member B would install the route through OSPF since it has a better admin distance and would then advertise back into BGP. This VRF tag is set on redistribution of BGP > OSPF and then as a table map in OSPF that blocks routes with the tag from getting installed in the routing table. When hitting this bug, the route-map used for redistributing into OSPF still sets the tag to the correct value. However, the table map no longer matches the correct tag. Rather, it matches the default tag. As a result, member A (could be B) would install the route through OSPF pointing to B. It would then redistribute it back into BGP with the med set to 1. The rest of the fabric (including member B) would install the BGP route pointing to member A since its med is better than the original route's med.

12.2(3j) and later

CSCvs76848

A switch SSD fails in less than two years and needs replacement. The /mnt/pss/ssd_log_amp.log file shows daily P/E cycles increasing by 10 or more each day, and fault "F3525: High SSD usage" is observed. Check the switch activity and contact Cisco Technical Support if the "High SSD usage" fault is raised on the switch.

12.2(3j) and later

CSCvt82388

A switch SSD fails in less than two years and needs replacement. The /mnt/pss/ssd_log_amp.log file shows daily P/E cycles increasing by 10 or more each day, and fault "F3525: High SSD usage" is observed. ARP/ICMPv6 adjacency updates can also contribute to many SSD writes.

12.2(3j) and later

CSCvu01639

There are faults for failed contract rules and prefixes on switches prior to the -EX switches. Furthermore, traffic that is destined to an L3Out gets dropped because the compute leaf switches do not have the external prefix programmed in ns shim GST-TCAM. You might also see that leaf switches prior to the -EX switches do not have all contracts programmed correctly in the hardware.

12.2(3j) and later

CSCvu07844

When a Cisco N9K-C93180LC-EX, N9K-93180YC-EX, or N9K-C93108TC-EX leaf switch receives control, data, or BUM traffic from the front panel ports with the storm policer configured for BUM traffic, the storm policer will not get enforced. As such, the switch will let all such traffic through the system.

12.2(3j) and later

CSCvh64426

The RJ45 link does not come up when connecting to an N9K-C93108TC-EX switch at 100 Mbps.

12.2(3t)

CSCvh91642

If the VLAN scale limit is hit, the VLAN translation table will not be cleaned up even after removing the VLANs that exceed the scale limit. This can introduce unexpected connectivity issues for the VLANs that do not have a translation entry.

12.2(3t)

CSCve03012

When traffic flows from the internal leaf switch side to the external leaf switch side, from IntLeafs to ExtLeaf, the traffic is load-balanced well. However, from ExtLeaf to the external side, the traffic is not load-balanced; the traffic uses a single path only (it is polarized).

After eliminating one of the two external leaf switches, the remained Ext_Leaf#1 switch sends traffic with both of the ECMP links.

Additionally, when packets are generated through the other port of InternalLeaf#1 in the case of traffic that was injected through two ports from InternalLeaf#1, the traffic is transmitted through the other ECMP port of Ext_Leaf#1. In this case, both of links in Ext_Leaf#1 were used correctly.

12.2(3s)

CSCve19790

After a link is disabled between a policy element (PE) device and a GOLF N7000-series switch, the VxLAN tunnel between Cisco ACI leaf switches and the GOLF N7000-series switch is removed. Pings from endpoints in Cisco ACI to the PE device that is connected to GOLF devices begin to fail.

Reenabling the link does not resolve the issue.

12.2(3s)

CSCve06787

Fault F2571 sometimes displays on leaf switches that are being used for Cisco Tetration Analytics integration.

12.2(3r)

CSCve08739

When using GOLF, a ping from outside or inside the Cisco ACI fabric to the GOLF router will not be successful.

12.2(3r)

CSCvf89664

An SNMP core is dumped when an SNMP context name is configured as null.

12.2(3r)

CSCvf99198

Bidirectional forwarding detection sessions between a Cisco ACI ToR and N7K keep flapping and never come up.

12.2(3r)

CSCvg58924

ICMP traffic to between endpoints might get dropped, but other traffic, including TCP and UDP, are not impacted.

12.2(3r)

CSCve19668

The ACLQOS or Hardware Abstraction Layer (HAL) process might fail when there are multiple access SPAN sessions configured in both directions coupled with tenant SPAN.

12.2(3p)

CSCve65374

Traffic that flows toward some tunnel endpoints (TEPs) will be dropped. This issue occurs because the tunnel toward those TEPs is programmed with drop adjacency.

12.2(3p)

CSCvf32867

The EPM show commands do not work when the VRF instance name size is more than 32 characters.

12.2(3p)

CSCvf67718

An EX linecard or E fabric module crashes and resets when it encounters the PCIe uncorrectable error. You can see that the card failed, powered off, and then got removed and reinserted by navigating to the following location in the Cisco APIC GUI and viewing the events:

Fabric > Inventory > Pod x > Spine > History > Events

12.2(3p)

CSCvg13666

A switch virtual interface (SVI) is down and does not come up.

12.2(3p)

CSCvg37153

Switches have a memory leak that can potentially lead to an out of memory reload, and the TAH_MEM_ENUM_tah_sug_fta_filtertcamdata table is seeing much greater memory allocation and usage than other nodes in the environment.

12.2(3p)

CSCvb42675

The Endpoint Manager (EPM) process might leak memory when adding or removing an Attachable Access Entity Profile (AEP).

12.2(3j)

CSCvc21356

A N9K-C93108TC-EX switch might forward large packets (> 381 byte IP packets) as CRC errors if the switch receives the packets on a 100Mbp speed interface and transmits the packets to a 1 gigabit interface on the same leaf switch.

12.2(3j)

CSCvd10246

If an ECMP route exists in the inband management VRF instance and is later deleted, there might be stale routes that cause forwarding issues.

12.2(3j)

CSCvd56870

In a multi-pod configuration with a single Layer 3 Out (L3out) distributed across four border leaf switches (two in pod 1 and two in pod 2), traffic might drop at the transit border leaf switch if the bounce bit is set.

12.2(3j)

CSCvd77155

An Open Shortest Path First (OSPF) session between border ToR switches using the stretched Switched Virtual Interface (SVI) might end and adjacency might point to an incorrect tunnel interface.

12.2(3j)

CSCvd80459

The Broadcom "HiGig" link might go down for some links, causing traffic to those links to be destroyed or discarded without informing the sender or recipient of the traffic’s failed delivery.

12.2(3j)

CSCvd87231

A fault F1321 might be raised and cleared periodically for all fan slots on a leaf switch.

12.2(3j)

CSCve04932

After an upgrading or downgrading a switch from the Cisco NX-OS Release 12.2(1o) or 12.2(1n), the Hot Standby Router Protocol (HSRP) virtual IP might be unreachable and the Address Resolution Protocol (ARP) table on external devices will show that the MAC for the virtual IP (VIP) is "Incomplete." The external device ARP table might show that the MAC address for the VIP is the MAC address of the active IP interface and not the virtual MAC address. This might disable redundancy when the active leaf switch goes down.

12.2(3j)

CSCve05164

A leaf switch might send a DHCP request with an empty model or with a wrong pod model. This might break connectivity to the affected host.

12.2(3j)

CSCve25234

When the OpFlex traffic packet is in transit from the spine switch, the spine switch might be programming zero source MAC [What does this mean?] on the infra native transit packets, which might cause an OpFlex connection failure.

12.2(3j)

CSCve26184

A Cisco Nexus 9000 Series ACI-Mode leaf switch might reboot if the endpoint manager client (EPMC) crashes.

12.2(3j)

CSCve30327

The Border Gateway Protocol (BGP) might be unable to form a neighbor connection across a Cisco ACI fabric where at least one leaf switch is an "EX" leaf.

12.2(3j)

CSCve39801

Simple Network Management Protocol (SNMP) process memory usage might increase because of continuous interface route flap.

12.2(3j)

CSCve40338

The fabric modules of a Cisco Nexus 9500 switch that is in ACI mode might enter the unrecoverable error status after the diagnostic level of the fabric modules get changed to full and the fabric modules are rebooted.

12.2(3j)

CSCve56651

The connection between a local host/client and server might fail to form when using a contract filter that uses the "established" designation as a TCP session rule on older model Cisco Nexus 9000 Series ACI-mode "-EX" leaf switches.

12.2(3j)

CSCve58800

Inband management might become unavailable after upgrading to one of the Cisco Nexus 9000 Series ACI-Mode Switch 12.2 releases.

12.2(3j)

CSCve79605

The HSRP virtual MAC address might attach from the virtual PortChannel (vPC) orphan port and might be announced with the vPC’s virtual IP address instead of the physical IP address.

12.2(3j)

CSCvf01042

During an endpoint move between two leaf switches, a third leaf switch might maintain the old endpoint information.

12.2(3j)

CSCvf43074

Remote IP learning might be limited to a single bridge domain (BD) subnet.

12.2(3j)

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.

12.2(3j) and later

CSCuo50533

When output span is enabled on a port where the filter is VLAN, multicast traffic in the VLAN that goes out of that port is not spanned.

12.2(3j) and later

CSCup65586

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

12.2(3j) 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.

12.2(3j) and later

CSCup92534

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

12.2(3j) and later

CSCuq39829

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

12.2(3j) and later

CSCuq46369

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

12.2(3j) and later

CSCuq77095

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

12.2(3j) and later

CSCuq83910

When an IP address moves from one MAC behind one ToR to another MAC behind another ToR, even though the VM sends a GARP packet, in ARP unicast mode, this GARP packet is not flooded. As a result, any other host with the original MAC to IP binding sending an L2 packet will send to the original ToR where the IP was in the beginning (based on MAC lookup), and the packet will be sent out on the old port (location). Without flooding the GARP packet in the network, all hosts will not update the MAC-to-IP binding.

12.2(3j) 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.

12.2(3j) and later

CSCuq93389

If an endpoint has multiple IPs, the endpoint will not be aged until all IPs go silent. If one of the IP addresses is reassigned to another server/host, the fabric detects it as an IP address move and forwarding will work as expected.

12.2(3j) and later

CSCur01336

The power supply will not be detected after performing a PSU online insertion and removal (OIR).

12.2(3j) and later

CSCur81822

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

12.2(3j) 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.

12.2(3j) and later

CSCus29623

The transceiver type for some Cisco AOC (active optical) cables is displayed as ACU (active copper).

12.2(3j) 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.

12.2(3j) and later

CSCus54135

The default route is not leaked by BGP when the scope is set to context. The scope should be set to Outside for default route leaking.

12.2(3j) and later

CSCus61748

If the TOR 1RU system is configured with the RED fan (the reverse airflow), the air will flow from front to back. The temperature sensor in the back will be defined as an inlet temperature sensor, and the temperature sensor in the front will be defined as an outlet temperature sensor.

If the TOR 1RU system is configured with the BLUE fan (normal airflow), the air will flow from back to front. The temperature sensor in the front will be defined as an inlet temperature sensor, and the temperature sensor in the back will be defined as outlet temperature sensor.

From the airflow perspective, the inlet sensor reading should always be less than the outlet sensor reading. However, in the TOR 1RU family, the front panel temperature sensor has some inaccurate readings due to the front panel utilization and configuration, which causes the inlet temperature sensor reading to be very close, equal, or even greater than the outlet temperature reading.

12.2(3j) and later

CSCut59020

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

12.2(3j) and later

CSCuu11347

Traffic from the orphan port to the vPC pair is not recorded against the tunnel stats.  Traffic from the vPC pair to the orphan port is recorded against the tunnel stats.

12.2(3j) and later

CSCuu11351

Traffic from the orphan port to the vPC pair is only updated on the destination node, so the traffic count shows as excess.

12.2(3j) 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.

12.2(3j) and later

CSCuv57302

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

12.2(3j) and later

CSCuv57315

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

12.2(3j) and later

CSCuv57316

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

12.2(3j) and later

CSCuw09389

For direct server return operations, if the client is behind the Layer 3 out, the server-to-client response will not be forwarded through the fabric.

12.2(3j) 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.

12.2(3j) and later

CSCuy00084

BCM does not have a stats option for yellow packets/bytes, and so BCM does not show in the switch or APIC GUI stats/observer.

12.2(3j) 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.

12.2(3j) and later

CSCuy06749

Traffic is dropped between two isolated EPGs.

12.2(3j) and later

CSCuy22288

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

12.2(3j) and later

CSCuy25780

An overlapping or duplicate prefix/subnet could cause the valid prefixes not to be installed because of batching behavior on a switch. This can happen during an upgrade to the 1.2(2) release.

12.2(3j) and later

CSCuy47634

EPG statistics only count total bytes and packets. The breakdown of statistics into multicast/unicast/broadcast is not available on new hardware.

12.2(3j) and later

CSCuy56975

You must configure different router MACs for SVI on each border leaf if L3out is deployed over port-channels/ports with STP and OSPF/OSPFv3/eBGP protocols are used. There is no need to configure different router MACs if you use VPC.

12.2(3j) and later

CSCuy61018

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

12.2(3j) and later

CSCuy96912

The debounce timer is not supported on 25G links.

12.2(3j) and later

CSCuz12913

An ACI leaf switch sends ARP to a device (such as a router or host) that belongs to directly connected subnets for an L3Out. After ARP is resolved, devices in directly connected subnets on two different L3Outs can talk each other without any contracts.

12.2(3j) 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.

12.2(3j) and later

CSCuz13614

For traffic coming out of an L3out to an internal EPG, stats for the actrlRule will not increment.

12.2(3j) and later

CSCuz13810

When subnet check is enabled, a ToR does not learn IP addresses locally that are outside of the bridge domain subnets. However, the packet itself is not dropped and will be forwarded to the fabric. This will result in such IP addresses getting learned as remote endpoints on other ToRs.

12.2(3j) and later

CSCuz47058

SAN boot over a virtual Port Channel or traditional Port Channel does not work.

12.2(3j) and later

CSCuz65221

A policy-based redirect (PBR) policy to redirect IP traffic also redirects IPv6 neighbor solicitation and neighbor advertisement packets.

12.2(3j) and later

CSCva98767

The front port of the QSA and GLC-T 1G module has a 10 to 15-second delay as it comes up from the insertion process.

12.2(3j) and later

CSCvb36823

If you have only one spine switch that is part of the infra WAN and you reload that switch, there can be drops in traffic. You should deploy the infra WAN on more than one spine switch to avoid this issue.

12.2(3j) and later

CSCvb39965

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

12.2(3j) and later

CSCvb49451

In the case of endpoints in two different TOR pairs across a spine switch that are trying to communicate, an endpoint does not get relearned after being deleted on the local TOR pair. However, the endpoint still has its entries on the remote TOR pair.

12.2(3j) 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.

12.2(3j) and later

CSCvd63567

After upgrading a switch, Layer 2 multicast traffic flowing across PODs gets affected for some of the bridge domain Global IP Outsides.

12.2(3j) and later