Cisco Nexus 9000 ACI-Mode Switches Release Notes, Release 13.2(4)

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 22, 2021

In the Open Issues section, added bug CSCvt73069.

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.

May 12, 2020

13.2(4e): In the Open Bugs section, added bug CSCvo01105.

March 13, 2020

13.2(4d): In the Resolved Bugs section, added bug CSCvr98827.

September 27, 2019

In the Supported Hardware section, for the N9K-C9336C-FX2 switch, changed the port profile note to:

The port profile feature does supports downlink conversion of ports 31 through 34. Ports 35 and 36 can only be used as uplinks.

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-C9348GC-FXP, 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.

September 3, 2019

13.2(4e): In the Open Bugs section, added bug CSCvp94661.

August 28, 2019

13.2(4d): In the Open Bugs section, added bugs CSCvq42673  and CSCvq43477.

August 14, 2019

13.2(4d): In the Open Bugs section, added bug CSCvp92269, CSCvq43058, and CSCvq43477.

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.

June 5, 2019

In the Supported Hardware section, for the N9K-C9364C switch, removed the following erroneous sentence:

The last 16 of the QSFP28 ports are colored green to indicate that they support wire-rate MACsec encryption.

February 12, 2019

In the Supported Hardware section, added APIC L2 and APIC M2.

February 6, 2019

13.2(4d): In the Known Behaviors section, added bug CSCvo22890.

January 30, 2019

13.2(4d): In the Open Bugs section, added bug CSCvn69340.

December 20, 2018

13.2(4e): Release 13.2(4e) became available; there are no changes to this document for this release.

November 15, 2018

Release 13.2(4d) 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

Note: The Cisco N9K-C9336PQ switch is supported for multipod.  The N9K-9336PQ switch is not supported for inter-site connectivity with Cisco ACI Multi-Site, but is supported for leaf switch-to-spine switch connectivity within a site.  The N9K-9336PQ switch is not supported when multipod and Cisco ACI Multi-Site are deployed together.

Spine switch

N9K-C9364C

Cisco Nexus 9364C switch is a 2-rack unit (RU), fixed-port switch designed for spine-leaf-APIC deployment in data centers. This switch supports 64 40/100-Gigabit QSFP28 ports and two 1/10-Gigabit SFP+ ports.

The following PSUs are supported for the N9K-C9364C:

■                    NXA-PAC-1200W-PE

■                    NXA-PAC-1200W-PI

■                    N9K-PUV-1200W

■                    NXA-PDC-930W-PE

■                    NXA-PDC-930W-PI

Note: 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.

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

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-C9508-FM-E2

Cisco Nexus 9508 Fabric module supporting 100 Gigabit line cards

Spine switch module

N9K-C9516-FM

Cisco Nexus 9516 Fabric module supporting 100 Gigabit line cards

Spine switch module

N9K-C9516-FM-E2

Cisco Nexus 9516 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

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

Spine switch module

N9K-X9736C-FX

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

Note: 1-Gigabit QSA is not supported on ports 1/29-36. This line card supports the ability to add a fifth Fabric Module to the Cisco N9K-C9504 and N9K-C9508 switches. The fifth Fabric Module can only be inserted into slot 25.

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-A+

Cisco Nexus 9500 Series supervisor module

Switch module

N9K-SUP-B

Cisco Nexus 9500 Series supervisor module

Switch module

N9K-SUP-B+

Cisco Nexus 9500 Series supervisor module

Leaf switch

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.

Leaf switch

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.

Leaf switch

N9K-C93120TX

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

Leaf switch

N9K-C93128TX

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

Leaf switch

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 either 24 40G ports or 12 100G ports. If 100G is connected the Port1, Port 2 will be HW disabled.

Note: This switch has the following limitations:

■        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.

■        Port profiles and breakout ports are not supported on the same port.

Leaf switch

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

Leaf switch

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.

Leaf switch

N9K-C9332PQ

Cisco Nexus 9332PQ Top-of-rack (ToR) Layer 3 switch with 26 APIC-facing ports and 6 fixed-Gigabit spine facing ports.

Leaf switch

N9K-C9336C-FX2

Cisco Nexus C9336C-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 does supports downlink conversion of ports 31 through 34. Ports 35 and 36 can only be used as uplinks.

Leaf switch

N9K-C9348GC-FXP

The Cisco Nexus 9348GC-FXP switch (N9K-C9348GC-FXP) is a 1-RU fixed-port, L2/L3 switch, designed for ACI deployments. This switch has 48 100/1000-Megabit 1GBASE-T downlink ports, 4 10-/25-Gigabit SFP28 downlink ports, and 2 40-/100-Gigabit QSFP28 uplink ports.

This switch supports the following PSUs:

■        NXA-PAC-350W-PI

■        NXA-PAC-350W-PE

■        NXA-PAC-1100W-PI

■        NXA-PAC-1100W-PE

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.

When a Cisco N9K-C9348GC-FXP switch has only one PSU inserted and connected, the PSU status for the empty PSU slot will be displayed as "shut" instead of "absent" due to a hardware limitation.

The PSU SPROM is not readable when the PSU is not connected. The model displays as "UNKNOWN" and status of the module displays as "shutdown."

Leaf switch

N9K-C9372PX

Cisco Nexus 9372PX Top-of-rack (ToR) Layer 3 switch with 48 Port 1/10-Gigabit APIC-facing ports Ethernet SFP+ front panel 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+.

Leaf switch

N9K-C9372PX-E

Cisco Nexus 9372PX-E Top-of-rack (ToR) Layer 3 switch with 48 Port 1/10-Gigabit APIC-facing ports Ethernet SFP+ front panel 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+.

Leaf switch

N9K-C9372TX

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

Leaf switch

N9K-C9372TX-E

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

Leaf switch

N9K-C9396PX

Cisco Nexus 9300 platform switch with 48 1/10-Gigabit SFP+ front panel ports and 6 or 12 40-Gigabit Ethernet QSFP spine-facing ports  

Leaf switch

N9K-C9396TX

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

Leaf switch fan

NXA-FAN-30CFM-B

Red port side intake fan

Leaf switch fan

NXA-FAN-30CFM-F

Blue port side exhaust fan

Leaf switch fan

NXA-FAN-65CFM-PE

Blue port side exhaust fan

Leaf switch fan

NXA-SFAN-65CFM-PE

Blue port side exhaust fan

Leaf switch fan

NXA-FAN-65CFM-PI

Burgundy port side intake fan

Leaf switch fan

NXA-SFAN-65CFM-PI

Burgundy port side intake fan

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

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

Leaf switch power supply unit

NXA-PAC-1100W-PE2

1100W AC power supply, port side exhaust pluggable

Leaf switch power supply unit

NXA-PAC-1100W-PI2

1100W AC power supply, port side intake pluggable

Leaf switch power supply unit

N9K-PAC-650W

650W AC Power supply, port side intake pluggable

Leaf switch power supply unit

N9K-PAC-650W-B

650W AC Power supply, port side exhaust pluggable

Leaf switch power supply unit

NXA-PDC-1100W-PE

1100W AC power supply, port side exhaust pluggable

Leaf switch power supply unit

NXA-PDC-1100W-PI

1100W AC power supply, port side intake pluggable

Leaf switch power supply unit

NXA-PHV-1100W-PE

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

Leaf switch power supply unit

NXA-PHV-1100W-PI

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

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

Leaf switch power supply unit

N9K-PUV-3000W-B

3000W AC Power supply, port side exhaust pluggable

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.

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.

Leaf switch power supply unit

NXA-PAC-500W-PE

500W AC Power supply, port side exhaust pluggable

Leaf switch power supply unit

NXA-PAC-500W-PI

500W AC Power supply, port side intake pluggable

Leaf switch power supply unit

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 ACI-mode switch.

Leaf switch power supply unit

UCSC-PSU-930WDC V01

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

Leaf switch power supply unit

UCS-PSU-6332-DC

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

N9K-C93108TC-FX

Switch

Yes

No

N9K-C93180YC-FX

Switch

Yes

No

N9K-C93216TC-FX2

Switch

Yes

No

N9K-C9332C

Switch

Yes

Yes, only on the last 8 ports

N9K-C93360YC-FX2

Switch

Yes

No

N9K-C9336C-FX2

Switch

Yes

No

N9K-C9348GC-FXP

Switch

Yes, only with 10G+

No

N9K-C9364C

Switch

Yes

Yes, only on the last 16 ports

N9K-X9736C-FX

Line Card

Yes

Yes, only on the last 8 ports

CSCvo01105

The SSD lifetime on a switch may be reduced significantly due to constant ARP/ICMPv6 adjacency updates. Rather than process all adjacency updates in real-time, this enhancement is raised to report changes every minute to reduce early SSD wear out.

13.2(4e) and later

CSCvo42234

There is high SSD utilization on the standby supervisor for a 95xx ACI spine switch.

13.2(4e) and later

CSCvp94661

There is an EPM crash on a leaf switch that receives the Endpoint Announce packet with a malformed length field.

13.2(4e) and later

CSCvp98108

Traffic to be flooded in an EPG does not have fabricencap as the VNID in the IVXLAN header. Instead it has the primary VLAN that is configured for the path.

13.2(4e) and later

CSCvr49904

Traffic with a UDP destination port of 8472 is dropped on ingress by the ACI fabric.

13.2(4e) and later

CSCvr76058

A leaf switch crashes due to the following reason:

    Reason: reset-triggered-due-to-ha-policy-of-reset

    Service:device_test hap reset

13.2(4e) and later

CSCvr83337

A Cisco ACI leaf switch unexpectedly reloads and generates a core file.

13.2(4e) and later

CSCvs49377

After a virtual machine is vMotioned, traffic begins to drop the source from that endpoint. When running "show logging ip access-list internal packet-log deny" on the leaf switch, you can see policy drops for the endpoint.

13.2(4e) and later

CSCvt25383

The pervasive static route is missing on the spine node.

13.2(4e) and later

CSCvu40050

The spine node KIC database is missing the v4 default route from RIB. This causes in-band return traffic to drop on the way back to the border leaf nodes.

13.2(4e) and later

CSCve06334

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

13.2(4d) 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.

13.2(4d) and later

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.

13.2(4d) and later

CSCvg95192

Endpoint information is missing in the spine switches.

13.2(4d) and later

CSCvh11299

In COOP, the MAC IP address route has the wrong VNID, and endpoints are missing from the IP address DB of COOP.

13.2(4d) and later

CSCvh14815

BGP EVPN has the tenant endpoint information, while COOP does not have the endpoint.

13.2(4d) and later

CSCvh18100

If Cisco ACI Virtual Edge or AVS is operating in VxLAN non-switching mode behind a FEX, the traffic across the intra-EPG endpoints will fail when the bridge domain has ARP flooding enabled.

13.2(4d) and later

CSCvj03533

When IPv6 packets are received, mab is triggered. But, only the MAC address endpoint is learned, not the IP address endpoint.

13.2(4d) and later

CSCvj23046

In Cisco ACI Multi-Site plus multi-pod topologies, there could be multicast traffic loss for about 30 seconds on the remote-site. If only one LC has fabric links, there are other LCs with no fabric links and the LC with fabric links is reloaded.

13.2(4d) and later

CSCvj29908

Traffic gets dropped when a new TX SA is programmed after an old Rx SA is deleted on the peer and there are breakout ports in the link down state.

13.2(4d) and later

CSCvj50973

When the MTU settings for OSPF neighboring router interfaces do not match, the routers will be stuck in the Exstart/Exchange state. This behavior is expected. This bug is an enhancement to raise a fault to the APIC so that the routers' stuck state can be easily detected by the administrator.

13.2(4d) and later

CSCvk34581

When viewing a congested interface, you do not see any drops in the output of the "show interface" command. If you type "vsh_lc" to drop into the linecard shell, and then view the platform counters for the given port, you can see Buffer Drops on output.

13.2(4d) and later

CSCvk48856

The port LED shows green when a few breakout ports lanes are down.

13.2(4d) and later

CSCvk73228

This is an enhancement to decode the binary logs offline directly from the techsupport.

13.2(4d) and later

CSCvk74561

Link down detection on the copper transceiver port takes around 1 second of time when its peer switch reloads. This issue is only with a copper transceiver.

13.2(4d) and later

CSCvm75395

A route map is deployed even when the route profile is configured incorrectly. When upgrading to a release that includes the fixed for this defect, the incorrectly deployed route map is removed from the leaf switch, which may affect traffic that was using the route map.

13.2(4d) and later

CSCvn28108

A switch gets stuck in a bootloop with the following error raised on the console:

[ 1041.090380] obfl_klm writing reset reason 58, LC insertion sequence failure => [Failures < MAX] : powercycle

[ 1042.207780] write_mtd_flash_panic: successfully wrote 88 bytes at address 0xd68 to RR Iter: 0.

13.2(4d) and later

CSCvn69340

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

13.2(4d) and later

CSCvn92765

Excessive SSD writes are observed by ICMPv6, which can use up to 42GB per day.

13.2(4d) and later

CSCvo39715

When downgrading a Cisco ACI fabric, the OSPF neighbors go down after downgrading the Cisco APICs from a 3.2 or later release to a pre-3.2 release. After the upgrade, the switches are still running a 13.2 or later release.

13.2(4d) and later

CSCvo53218

10-20 second packet loss is observed when the designated forwarder leaf switch comes back online after a reload.

13.2(4d) and later

CSCvo74427

In a setup in which a leaf switch has 2 links to a spine switch, one link might flap a few times. The flapping seems to be triggered by a physical link flap (from the ethpm logs). After the link came up, the IS-IS update never reaches URIB. So, the leaf switch does not send any traffic on this link to the spine switch. The IS-IS database has the routes learned from this spine switch on both links.

13.2(4d) and later

CSCvp09949

Copy service traffic will fail to reach the TEP where the copy devices are connected. Traffic will not be seen on the spine switches.

13.2(4d) and later

CSCvp50075

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

13.2(4d) and later

CSCvp59361

A kernel panic seen in some random scenarios.

13.2(4d) and later

CSCvp63213

While ACI switches are still initializing after an upgrade, TACACS requests are seen coming from the switch IP address, with the remote IP address set to 127.0.0.1 for the admin user.

13.2(4d) and later

CSCvp91758

Fault F0449 gets raised and the ASIC vrm(5) status fails on the Cisco N9K-93108TC-EX or N9K-93180YC-EX switches.

13.2(4d) and later

CSCvp92269

Running a Qualys security scan results in the following message:

CWE - 693 Protection Mechanism Failure -

"HTTP Security Header Not Detected"

13.2(4d) and later

CSCvq20711

On a leaf switch, the "show interface description" command output in the ACI mode does not match the output of the "show int description" command output in the VSH mode.

13.2(4d) and later

CSCvq25729

Traffic is dropped when it is destined to a pervasive route and when the endpoint is not learned. This issue can be also seen on a border leaf switch when "disable remote EP learning" is set.

13.2(4d) and later

CSCvq42673

1) Deploy the breakout configuration.

2) Deploy a port channel or vPC configuration on these broken-out ports.

3) Remove the breakout configuration. The port channel or vPC configuration is still present in the APIC.

4) Deploy the breakout configuration. This action causes a port channel bringup failure, or causes the port channel manager or eth_port_manager to crash on the switch.

This issue occurs when the vPC or port channel configuration is present even before the breakout is applied.

13.2(4d) and later

CSCvq43058

A spine switch fabric module or line card is reloaded unexpectedly due to a kernel panic. The stack trace includes the following statement:

Kernel panic - not syncing: Out of memory: system-wide panic_on_oom is enabled

13.2(4d) and later

CSCvq43477

In the IPv6 options, for the source-link layer address field, IPv6 traffic is blackholed because the leaf switch sets the incorrect MAC address in the router advertisement's (RA's) source link-layer address. This happens only with RAs that are sent as a reply to the router solicitation from the host. Unsolicited RAs from the leaf switch have the correct MAC address of the leaf switch itself.

The border leaf switch sends out unsolicited RA messages correctly with its link MAC address (0022.bdf8.19ff) in the source link-layer address field.

13.2(4d) and later

CSCvq54991

Spine switches will not export flows in the absence of the controller IP address or if the controller and collectors have a different subnet.

13.2(4d) and later

CSCvq57935

A GOLF-enabled VRF instance is put into the Down state on the spine switches. This can be confirmed with the "show bgp process vrf <vrf-name>" command from the CLI of the spine switches. Behaviors that may indicate this issue include a loss of reachability to the endpoints in a GOLF-enabled VRF instance and missing routes on the leaf switch for the VRF instance in question.

13.2(4d) and later

CSCvq64803

A leaf switch crashes with the "Unknown" reset reason when the breakout ports configuration is re-applied.

The reset reason for this switch is as follows:

        Image Version : 13.2(3o)

        Reset Reason (LCM): Unknown (0) at time Fri Jul 12 14:21:14 2019

        Reset Reason (SW): Reset triggered due to HA policy of Reset (16) at time Fri Jul 12 14:17:40 2019

        Service (Additional Info): Reset triggered due to HA policy of Reset

13.2(4d) and later

CSCvq67792

Posting the IPv6 interface configuration (including BFD enable) by using the API in an L3Out results in SVIs using the secondary IP address as the BFD source IP address. This causes the BFD session to fail.

13.2(4d) and later

CSCvq98750

In Cisco ACI when using MAC pinning with a vPC, prior to reloading when you run the 'show vpc brief' command on the CLI, the command shows that the vPC is passing consistency checks. However, after reloading the leaf switch, the vPC then properly displays the consistency check as 'Not Applicable'.

13.2(4d) and later

CSCvr08148

The N9K-C93180YC-EX leaf switch reboots for an unknown reason without any affected services:

Last reset

  Reason: Unknown

  System version: <VERSION>

  Service:

13.2(4d) and later

CSCvr75413

After upgrading a leaf switch, the switch brings up the front panel ports before the policies are programmed. This may cause a connectivity issue if a connected host relies on the link level state to decide whether or not it can forward traffic on a particular NIC or port. The loss duration would be proportional to the scale of configuration policies that must be programmed.

13.2(4d) and later

CSCvr79911

An LLDP/CDP MAC address entry gets stuck in the blade switch table on a leaf switch in a vPC. The entry can get stuck if the MAC address flaps and hits the move detection interval, which stops all learning for the address.  Use the following command to verify if a switch has a stale MAC address entry:

module-1# show system internal epmc bladeswitch_mac all

13.2(4d) 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.

13.2(4d) 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 fw 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.

13.2(4d) and later

CSCvs40299

The policy_mgr process on an ACI leaf switch has a memory leak and results in an unexpected reload.

The problem can happen over a long period of time, such as a year. Depending on when individual switches were last rebooted, multiple devices could experience the reload at around the same time.

13.2(4d) and later

CSCvs45414

A N9K-X9736PQ linecard in an ACI mode Nexus 9500 spine switch unexpectedly reloads. The following output is seen in the command "show system reset-reason module 1":

    `show system reset-reason module 1`

    *************** module reset reason (1) *************

    0) At 2019-12-01T00:00:00.00

        Reason: line-card-not-responding

        Service:Line card not responding => [Failures < MAX] : powercycle

        Version:

13.2(4d) 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.

13.2(4d) and later

CSCvt00231

Traffic destined to a switch is policy dropped.  The contracts configured on the switch look correct, but the ELAM drop reason shows a clear SECURITY_GROUP_DENY. If you dump the FPC and FPB pt.index results of the ELAM, the values are different. Specifically, the FPC index is wrong when you check the Stats Idx under the specific ACLQOS rule. FPC should be the summary of the final result. In this case, there are two hits, but there is one stable entry in TCAM and one that is not stable.

13.2(4d) and later

CSCvt08181

All routes to a particular spine switch are removed from uRIB on all leaf switches in the fabric.

13.2(4d) and later

CSCvt39689

Glean ARP (0xfff2, 239.255.255.240) flood is stopped on the transit leaf switch and is not delivered toward all the leaf switches in the fabric. Thus, silent host discovery does not work.

13.2(4d) and later

CSCvt52620

There is a stale pervasive route after a DHCP relay label is deleted.

13.2(4d) and later

CSCvt73069

A Cisco ACI fabric is not fully fit after a Cisco APIC firmware upgrade.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) and later

CSCvu15712

If a spine switch's PTEP is configured as the multipod L3Out router ID and the router ID is later changed, the spine switch's PTEP loopback gets deleted and the MP BGP session goes down.

13.2(4d) and later

CSCvu61024

Zoning-rules are not programmed in the hardware after reloading a switch.

13.2(4d) and later

CSCvu72416

Triggered by a physical layer issue, such as fiber or a bad transceiver, a link flap may happen every now and then. However, it is uncommon to have continuous flaps when the node is left unattended over an extended period, such as having 688,000 flaps over a year. Each time after the fabric link flaps, one dbgRemotePort managed object is added to the policyElement database. After a long time flapping like this, unexpected memory allocation and access can be triggered for the Nexus OS process, such as policy_mgr or ethpm.

This defect is to enhance the object-store to reduce the impact for such scenarios.

13.2(4d) and later

CSCvv33100

The IPS port is not down when an RX cable is removed on a Cisco ACI leaf switch 1G port.

An ACI switch with 1G fiber would signal a peer IOS device, such as a Catalyst 6000 series switch, with flow control auto/desired to turn on the flow control.

13.2(4d) and later

CSCvw07282

On a modular spine switch, an unconnected port's switching state is disabled, which means it is out of service. The issue is that after reloading a line card, all of the ports on that line card change to switching state enabled, even if the port is not connected to anything. This issue is mostly cosmetic; there is no real impact if an unconnected port has switching state enabled.

13.2(4d) and later

CSCwa12763

External route import for a VRF instance fails on a leaf switch after removing a shared services contract between two EPGs.

13.2(4d) and later

CSCwb08081

A route profile that matches on community list and sets the local pref and community is not working post upgrade to 5.2.x release.

route-map imp-l3out-L3OUT_WAN-peer-2359297, permit, sequence 4201

  Match clauses:

    community  (community-list filter): peer16389-2359297-exc-ext-in-L3OUT_WAN_COMMUNITY-rgcom

  Set clauses:

    local-preference 200

    community xxxxx:101 xxxxx:500 xxxxx:601 xxxxy:4 additive

The match clause works as expected, but the set clause is ignored.

13.2(4d) and later

CSCwd29346

An ACI switch's console may continuously output messages similar to:

svc_ifc_eventmg (*****) Ran 7911 msecs in last 7924 msecs

13.2(4d) and later

CSCvs10395

Leaf switch downlinks all go down at one time due to FabricTrack.

13.2(4d)

CSCvi05870

On reload, vPC interfaces are temporarily brought online and then brought down.  During this transition, traffic loss may be seen for 3-10 seconds.

13.2(4d)

CSCvi22143

Multi-destination traffic is not sent out the leaf switch uplinks or downlinks to other devices. This can result in ARP resolution problems or issues with the spanning tree.

13.2(4d)

CSCvj58567

When used for IPN connectivity, the fixed 10 Gb ports Eth1/65 and Eth1/66 cannot resolve ARP.

13.2(4d)

CSCvj99258

The kernel crashes with the following entry (dc3_sensor) in the dmesg-mtdoops or kernel crash logs:

    <0>[62761.120792] BUG: soft lockup - CPU#3 stuck for 22s! [dc3_sensor:7911]

13.2(4d)

CSCvk15151

There is a 1G port flap when 1G SFP modules are inserted into other ports on same MAC address.

13.2(4d)

CSCvk33286

The device reloads with the reset reason of "kernel-panic." This applies to kernel panics with and without PCIE issues recorded on dmesg-mtdoops.

13.2(4d)

CSCvk36215

1G QSA links are not coming up in the switches.

13.2(4d)

CSCvk41926

A leaf switch reloads and shows the following reason:

reset-triggered-due-to-ha-policy-of-reset

There is also an LLDP core file generated after the crash.

13.2(4d)

CSCvk50550

Cisco NX-OS shows fault F2821 under normal operations with no impact to traffic.

13.2(4d)

CSCvk75726

The bridge domain gateway IP address is not present in COOP.

13.2(4d)

CSCvm05674

The following fault is raised on the Cisco APIC for database corruption on the SQLLite database:

Database got corrupted.[SQLiteCorruptionException]

13.2(4d)

CSCvm06425

The fault F3045 "IGMP Snooping fabric learning is disabled" is erroneously raised.

13.2(4d)

CSCvm09903

Following the upgrade of a Cisco ACI leaf switch, uplink port 1/51 may stay down for an extended period of time.  Eventually the link will recover on its own.

13.2(4d)

CSCvm15457

The product Cisco Nexus 9000 Series Fabric Switches - ACI mode includes a version of the Linux kernel that is affected by the IP Fragment Reassembly Denial of Service Vulnerability identified by the following Common Vulnerability and Exposures (CVE) ID:

CVE-2018-5391

Cisco has confirmed that this product is impacted.

13.2(4d)

CSCvm16440

PPI-COPP stats are not incrementing and traffic is not rate limited. Instead, traffic is hitting on the default COPP policy.

13.2(4d)

CSCvm26708

A 100/40G bidirectional platform sometimes latches onto a 40G link even when the peer has a 100/40G bidirectional platform between the leaf switch and spine switch.

13.2(4d)

CSCvm37645

Link detection takes up to 17 seconds when a ToR switch goes down.

13.2(4d)

CSCvm40454

After an overnight continuous interface flap test, the link fails to come up or a HAL process core might be seen on the switch (leaf or spine).

13.2(4d)

CSCvm46784

A link takes a longer time to come up when connected with 25G transceivers.

13.2(4d)

CSCvm47525

Packets are transmitted tagged with vlan-0.  This can result in connectivity issues (for example, pings will time out) for connecting devices that do no support or expect tagged frames.

13.2(4d)

CSCvm48676

A Cisco N9K-C93180LC-EX switch reboots with the following reason:

reset-triggered-due-to-ha-policy-of-reset

13.2(4d)

CSCvm48981

A Bidirectional Forwarding Detection (BFD) session stays in the DOWN state.

13.2(4d)

CSCvm52368

After creating a static L3Out in the same VRF instance as L3Out, the fault F0467 appears for OSPF L3Outs.

13.2(4d)

CSCvm55571

A contract with a subject that allows ssh and has reverse filter port enabled will not work after upgrading to the 13.2.3i release. The ability to use ssh to connect to the switch stops working.

13.2(4d)

CSCvm65702

If initially only a few leaf switches were configured with the Netflow policy and then the leaf switch profile was changed to include all leaf switches, Netflow will fail on some of the leaf switches.

13.2(4d)

CSCvm70324

When a peer is configured with private remove-as option in parallel, the private remove-as is not going to work in backend.

13.2(4d)

CSCvm75089

When attempting to run "show processes memory", the full output does not display, but instead the command fails early with the following error:

dn "sys/procsys/proc-0/CDprocProcMem5min" could not be found

Error executing command, check logs for details

13.2(4d)

CSCvm75296

Enabling the TrustSec feature on BGP causes traffic disruption.

13.2(4d)

CSCvm77485

IGMP messages are no longer flooded by a Cisco ACI leaf switch in a bridge domain with IGMP snooping disabled.

13.2(4d)

CSCvm82499

Traffic destined to a PBR anycast MAC address is dropped on the spine switch.

13.2(4d)

CSCvm88651

Traffic potentially drops with the reason of "VLAN_XLATE_MISS" or "UC_TENANT_MYTEP_BRIDGE_MISS" on changing the port scope policy from GLOBAL to LOCAL and back to GLOBAL, or changing LOCAL to GLOBAL.

13.2(4d)

CSCvn00808

When enabling "Limit IP Learning to Subnet" (limitIpLearnToSubnets) on a bridge domain, all endpoints including IP addresses within the subnet are flushed from the leaf and affect connectivity until the endpoints are relearned.

The expectation is that only endpoints outside of the configured subnet are flushed.

13.2(4d)

CSCvn17131

The Spanning Tree Protocol (STP) PortFast Bridge Protocol Data Units (BPDUs) are not transited across the fabric, which can lead to Layer 2 instability. You can check for tx, but not rx BPDUs, with the following command:

show spanning internal info all | egrep 'bpdu_in|bpdu_out|Eth1'

13.2(4d)

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.

13.2(4d) 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.

13.2(4d) and later

CSCup65586

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

13.2(4d) 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.

13.2(4d) and later

CSCup92534

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

13.2(4d) and later

CSCuq39829

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

13.2(4d) and later

CSCuq46369

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

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) and later

CSCur01336

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

13.2(4d) and later

CSCur81822

The access-port operational status is always “trunk”.

13.2(4d) 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.

13.2(4d) and later

CSCus29623

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

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) and later

CSCuv57316

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

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) and later

CSCuy06749

Traffic is dropped between two isolated EPGs.

13.2(4d) and later

CSCuy22288

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

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) and later

CSCuy61018

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

13.2(4d) and later

CSCuy96912

The debounce timer is not supported on 25G links.

13.2(4d) 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.

13.2(4d) and later

CSCuz13614

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

13.2(4d) 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.

13.2(4d) and later

CSCuz47058

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

13.2(4d) and later

CSCuz65221

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

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) and later

CSCvb39965

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

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) 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.

13.2(4d) and later

CSCvo22890

There is intermittent packet loss for some flows through FX2 leaf switches when the no-drop class is enabled.

13.2(4d) and later

CSCvo39715

When downgrading a Cisco ACI fabric, the OSPF neighbors go down after downgrading the Cisco APICs from a 3.2 or later release to a pre-3.2 release. After the upgrade, the switches are still running a 13.2 or later release.

13.2(4d) and later