Don't put a class B static pointing to a broadcast interface--use a next hop instead. The problem is, most likely, that the router is arping for every possible address within the class B range, and then building a seperate adjacency table entry for each one, which is going to suck up a _lot_ of memory, enough to crash the router, even (I've seen it happen many times).
What routing protocol is this? If it's EIGRP (you said topology, which implies it is), take look at show ip eigrp events, and see where most of the topology changes are coming from. Are these topology changes things that you are expecting, or are they something that seems like a problem? If they seem like a problem let's look at them, and see if we can isolate where they are coming from, and figure out some way to reduce the load on this router.
Summarization and route filters are the two best techniques to reduce the scope of topology changes in a network.
I would say that you should investigate the spanning tree issues by trying to determine what links on the spanning tree might be changing status on a regular basis. I would think that you could do some sort of debug that would tell you what spanning tree change took place, which would lead you to the source of the changes, but I'll leave a more detailed answer to those who know spanning tree better than I do.
On the memory issues, fragmentation is generally caused by the router using most of its memory while doing a lot of alloc's and free's while in a very low memory condition. When this happens, the outcome is, sometimes, severe memory fragmentation, evidenced by a very small block in the largest column of show memory, with a much larger number in the free column. The only real way to recover from this is a reload, and then working on things to prevent it from hapenning again.
As for dead memory, that's a little trickier. Suppose a process allocates some memory, then terminates without freeing that memory. This would be considered "dead" memory. Note that dead memory is most often actually in use by a some process other than the one that allocated the memory. The reason it's called "dead" is because IOS doesn't know what processes are actually using the memory, but the process that allocated it is dead. Generally, dead memory doesn't represent any sort of memory leak, it's just part and parcel of the normal operation of IOS.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.