01-20-2015 05:52 AM
Hello!
I've noticed interesting behaviour in Cat3k.
Some time ago our management system started to send notifications that one of our switches (C3560E) have more than 80% memory utilization. I looked into it and saw that this was pretty much the same situation for almost a year that the switch is monitored. Recently it just grown a little, that gave more than 80% but before it was almost 80%.
Show version output suggesting that switch has 128M of memory:
cisco WS-C3560E-48TD (PowerPC405) processor (revision F0) with 131072K bytes of memory.
IOS version - 15.0(2)SE6
I took it to the lab, erased config to see if that was the problem (nothing fancy there - basic L2/L3 switching, marking traffic, few static routes, less than 40 vlans)
show memory after erasing config still showing high memory utilization and what is interesting total memory is less than 50M when it should be something around 128M.
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 4A4601C 49259992 36919476 12340516 11127860 8379892
I/O 6800000 8388608 5571764 2816844 2729744 2723328
Driver te 2C00000 4194304 106744 4087560 4087560 4087560
show proc memory output have a few lines that seems to consume more memory than others, although two of them freed the memory.
01-20-2015 01:01 PM
IOS version - 15.0(2)SE6
This is "normal" when you're running crappy software like the 15.0(2)SE train.
I will never recommend Cat 3K to run anything but 12.2(55)SE9. If you need features only found in 15.0(2)SE then stick with 15.0(2)SE4.
01-21-2015 06:01 AM
To be fair we use extensively this train on 4900M and 4500 platforms and it's going ok for now.
And 15.0(2)SE6 is considered MD release, release notes don't have anything on the memory side of issues (there is seems to be a bug with HTTPS which we don't use and disable explicitly).
I'll try to use the suggested by you release, but don't have too much hope that situation will change.
01-23-2015 04:58 PM
And 15.0(2)SE6 is considered MD release, release notes don't have anything on the memory side of issues (there is seems to be a bug with HTTPS which we don't use and disable explicitly).
I agree. But there are some bug Cisco's identified that will never be published to the publlic.
Let us know how you go.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide