This could have happened for a number of reasons. You would get a SYS-2-MALLOCFAIL if your switch has temporarily or permanently used all available memory. Or if the switch has fragmented all of the memory down in to such small peices that it can't find a chunk big enough for its needs. Or it could be a memory leak, which would be a software bug. The traceback sometime points to a bug.
You could do a "show proc mem" and have a look to see what memory is free and if any processes are hogging the memory.
I have had this before and it was a virus. You could see that the main user of memory was the IP Packets. But this was on a router, on a 3550, you would expect the switching to take place so fast that the packets are not in memory for too long.
So, have a look at the "show proc mem" and see if anything jumps out - or post it if you like. If it's memory fragmentation, then a reboot could sort. If it's a software bug, then you should find it on the bug tracker.
You could also try turning on nbar protocol-discovery to see what protocols are hogging the interfaces - that may also help in the hunt for a virus.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...