This bug was typically reported by IDSM customers. However, it would also affect switches with 6380 NAMs. The docs indicate that only the 6380 NAMs triggered the leak. However, I went through the attached service requests, and I found one case where this bug was attributed to a SVC-NAM. That said, the bug should be fixed in 8.3(3).
I know of no catastrophic issues with the NAM and that version of CatOS code. Of course, that's not to say none exist. If you are worried about impacting your production network, schedule downtime to install and perform initial configuration of the NAM.
Thanks for the clarification. For your information, I have two NAMs installed on Cat6500 swithes and both are using the same version of OS of 8.3(3). These NAMs were running for the past 3 years without any issues.
Lately, we had detected high CPU usage on one of the switch and had reported this problem to Cisco TAC recently. Cisco TAC came back with the recommendation to remove the NAM as it was found to cause memory leak based on the bug detected and moreover the bug reported was on the older model of NAM and older version of CATOS.
So, I'm kind of puzzle over the recommendation provided since we had been using NAM for quite some time without any problem.
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...