cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1307
Views
5
Helpful
3
Replies

CSCvc90507 - Memory leak under fed main event due to multicast

amit.kandhil161
Level 1
Level 1

Is16.3.5b also impacted with this Bug?

 

Cisco IOS Software [Denali], Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9-M), Version 16.3.5b

 

Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 52 WS-C3650-48PD 16.3.5b CAT3K_CAA-UNIVERSALK9 INSTALL
2 52 WS-C3650-48PD 16.3.5b CAT3K_CAA-UNIVERSALK9 INSTALL
3 52 WS-C3650-48PD 16.3.5b CAT3K_CAA-UNIVERSALK9 INSTALL
4 52 WS-C3650-48PD 16.3.5b CAT3K_CAA-UNIVERSALK9 INSTALL

3 Replies 3

Leo Laohoo
Hall of Fame
Hall of Fame
If the information found in this bug is to be "trusted", then the Known Affected Version is 16.3.1 only and the stack is running 16.3.5b which should not be affected.

Seems like it hits the version as well. It hits 1 of our switch. 

ROM: IOS-XE ROMMON
BOOTLDR: CAT3K_CAA Boot Loader (CAT3K_CAA-HBOOT-M) Version 3.56, RELEASE SOFTWARE (P)

SW01 uptime is 23 weeks, 5 days, 18 hours, 57 minutes
Uptime for this control processor is 23 weeks, 5 days, 19 hours, 2 minutes
System returned to ROM by Power Failure
System image file is "flash:cat3k_caa-universalk9.16.03.05b.SPA.bin"

 

ed Memory value 97% exceeds critical level 95%
*Aug 26 22:22:23.499 UTC: %PLATFORM-3-ELEMENT_CRITICAL:Switch 1 R0/0: smand: 1/RP/0: Used Memory value 97% exceeds critical level 95%
*Aug 26 22:32:33.555 UTC: %PLATFORM-3-ELEMENT_CRITICAL:Switch 1 R0/0: smand: 1/RP/0: Used Memory value 97% exceeds critical level 95%
SW01#show platform software status control-processor
1-RP0: online, statistics updated 2 seconds ago
Load Average: healthy
1-Min: 1.29, status: healthy, under 5.00
5-Min: 1.46, status: healthy, under 5.00
15-Min: 1.43, status: healthy, under 5.00
Memory (kb): critical
Total: 3978124
Used: 3851580 (97%), status: critical
Free: 126544 (3%)
Committed: 4614592 (116%), over 99%

In our environment, we have witnessed similar behavior with a memory leak in fed main event in 16.6.4 code that seems correlated with multicast.  In our case, which is still being worked by TAC, memory consumption stabilizes once we stop the offending multicast stream.