Cisco Software Advisory Notice for CSCvm57328 and CSCvi76161
Author: Cisco Systems, Inc.
Date: 2019-07-25T00:00:00+00:00
Keywords: router; quick; mobile
Description: Software advisory and workaround for CSCvm57328 and CSCvi76161.

Software Advisory Notice

Dear Cisco Customer,

Cisco has identified the following software issue with the release that you have selected that may affect your use of this software. Review the Software Advisory notice here to determine if the issue applies to your environment. You may proceed to download this software if you have no concerns with the issue described.

For more comprehensive information about what is included in this software, refer to the documentation at the following site:

https://www.cisco.com/c/en/us/support/cloud-systems-management/application-policy-infrastructure-controller-apic/tsd-products-support-series-home.html

Affected Software and Replacement Solution for CSCvm57328 and CSCvi76161

Software Type

Affected Software

Releases

Minimum Recommended Software

Release with Fix

Cisco NX-OS

Any release prior to 12.2(4p)

12.2(4r)

Issue Description

Cisco has recently identified a defect (CSCvm57328 and CSCvi76161) in the Cisco Application Centric Infrastructure (ACI).

You are impacted by this issue only if you are upgrading from one of the affected software releases to a 13.2(2) release or later, or are downgrading from a 13.2(2) release or later to one of the affected software releases.

A version mismatch between Cisco ACI leaf switches may cause an unexpected EP announce message to be received by the EPM process on the leaf switch, resulting in an EPM crash. You may experience this issue when upgrading leaf switches that belong to two different maintenance groups.

As an example, Leaf 101 is in Maintenance Group "Odds" and Leaf 102 is in Maintenance Group "Evens." If you upgrade Maintenance Group "Odds" (thus upgrading Leaf 101), after the "Odds" upgrade completes, Leaf 102 may continuously HAP reset and reload.

Workaround

There are 2 possible workaround options for this issue.

Workaround 1: Performing a Two-Step Upgrade

The first workaround involves a two-step upgrade:

1.     Upgrade to the 12.2(4r) release.

2.     Upgrade to the desired destination release.

Workaround 2: Using the testapi Binary

The second workaround involves using the testapi binary to disable the endpoint announce feature temporarily during the upgrade. You must use the testapi binary after the Cisco APIC and all spines are upgraded to 3.2(2) or later releases, but before the leaf switches are upgraded. To use this method, contact Cisco TAC.