There is a serious bug related to your symptoms on the NX-OS that you are running i.e 5.1(3). I cannot share the bug details here. This bug hits N7K if you running 5..1(1) - 5.1(3). Infact, I have advised my all the customers to upgrade to 5.1(5) if you are in the same train or go to 5.2/6.0. In the first chance you should not be running the 5.1(3) as far as my recommendation go.
There are two options for you.
1. If you have redundant sup engines, you can fail-over to the standby one and it should clear out the message temporarily.
2. Upgrade the NX-OS to atleast 5.1.(5) or 5.2/6.0 as mentioned.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...