×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Sup V 10GE unexpected reboot

Unanswered Question

I have a 4510R with dual redundant Sup V 10GE engines. This is on a lightly used network.I have done a show tech support and forwarded it to Cisco. Being as this was done though on the "failover" engine much of the most relevant info is not there. There is also no log info or crashinfo files. One of the things I am trying to get an answer on is the high level of memory being held in the dead "process". It is 32MB's and basically holding steady. 99% of this number has been allocated by the Router Kernel.

Is this unusual? It seems to me to be very high. If anyone has any experience or point me to some documentation on this I would be most appreciative.

Thanks you

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.

A memory block is considered as dead if the process which created the block exits (no longer around). Each block keeps track of the address and pid of the process which created it. During periodic memory tallying, if the process that scheduler finds out from a block pid doesn't match the the process that the block remembered, the block is marked as dead. The "dead memory" in IOS is misleading as not all of the "dead memory" may actually be dead, and might still be in active use by the system. In IOS it is relatively common for one process to allocate blocks that will stick around even after that process is dead. This is especially true for configuration processes like exec which might create all sorts of things. So memory marked as belonging to process *Dead* was allocated under the control of a process that is no longer running. It is normal to have a significant chunk of memory in such a state--for instance, if persistent system data structures are created due to the actions of some process, the memory will be marked as belonging to that process, but the process doesn't ever return the memory (some other process may return it later on). The only way to actually clear that is to reload the device.

Actions

This Discussion