Cisco Bug: CSCte83622 - 'RIP Router' process is stuck in a loop sending continuous updates
Feb 22, 2014
- Cisco IOS
Known Affected Releases
Symptoms: High CPU utilization is seen on Cisco IOS Release 12.0(33)S5 code due to "RIP Send" and "BGP Scanner". Conditions: RIP in Cisco IOS Release 12.0(33)S does not have a separate database about the routes. When RIP has to send update packets, it will scan the whole routing table, validate each prefix and create the update packets and send out. Above event will have to happen every 15 seconds as per the timers configuration. With a network where there are 150k routes learned by BGP, it is quite possible the routing table scan during update generation can be CPU intensive. We will see the problem of continuous rip updates and high CPU until an RIP Send process. Please note that a Supernet prefix needs to be installed in the RIB, and RIP has to include them in its updates. If it is originated by static or other routing protocols, we will see the symptom if they are redistributed into RIP.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases