Take a look at this
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a00809d16f0.shtml
This is almost always due to route churn. Take a look at your routing
table (global and/or VRF) for routes that recently updated (show ip
route | i 0:00) and that might give you some clues as to where the
churn is coming from.
-Pete
On Tue, Oct 2, 2012 at 6:00 PM, CiscoNSP_list CiscoNSP_list
cisconsp_l...@hotmail.com wrote:
Hi Guys, High cpu from BGP router process started ~48 hours ago - Happens
every 30 seconds (Cisco 7200, NPE-G2normal load is 45-50% cpu) #sh
processes cpu sorted
CPU utilization for five seconds: 86%/44%; one minute: 53%; five minutes: 50%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
28920754676 99918606207 35.12% 6.76% 5.68% 0 BGP Router
All peering sessions on the 7200 have uptime of years(Or many weeks),
but I think it has to be due to a re-convergence? Have the following
configured under address-family vpnv4 (This conf has always been on the
7200(years))...but the 30 second scan time matches the CPU spikes.bgp
scan-time import 10
bgp scan-time 30 Any suggestions on how to track down the cause? Cheers.
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
