06-29-2014 12:40 AM - edited 03-04-2019 11:14 PM
What do we need to do if BGP Router contribute high process in CPU?
CPU utilization for five seconds: 97%/43%; one minute: 99%; five minutes: 92% | ||||||||||||||||||||||||
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process | ||||||||||||||||||||||||
44 36270732 35464661 1022 25.03% 15.21% 14.43% 0 BGP Router | ||||||||||||||||||||||||
325 7703860203228294256 0 10.47% 5.58% 5.24% 0 IP Input | ||||||||||||||||||||||||
455 7596596 28244228 268 5.59% 1.60% 0.82% 0 BGP I/O | ||||||||||||||||||||||||
543 13576608 8569950 1584 3.83% 18.94% 9.57% 0 BGP Task | ||||||||||||||||||||||||
9 152474380 15201602 10030 2.07% 0.27% 0.57% 0 Check heaps | ||||||||||||||||||||||||
376 16372652 7777145 2105 1.83% 13.93% 13.76% 0 IP RIB Update | ||||||||||||||||||||||||
358 56785192 14452691 3929 0.95% 0.44% 0.52% 0 CEF: IPv4 proces | ||||||||||||||||||||||||
23 55656604 116191071 479 0.71% 0.51% 0.50% 0 ARP Input | ||||||||||||||||||||||||
348 5736736 7812055 734 0.63% 4.19% 5.03% 0 XDR mcast | ||||||||||||||||||||||||
546 36531108 132425650 275 0.63% 0.37% 0.28% 0 Port manager per | ||||||||||||||||||||||||
35 56337684 306101724 184 0.23% 0.42% 0.30% 0 IPC Seat Manager | ||||||||||||||||||||||||
330 287962916 871459868 330 0.23% 0.39% 1.61% 0 SNMP ENGINE | ||||||||||||||||||||||||
286 7682841067821917 0 0.15% 0.07% 0.07% 0 Ethernet Msec Ti | ||||||||||||||||||||||||
626 354112 825565 428 0.15% 0.11% 0.09% 0 IPv6 Input | ||||||||||||||||||||||||
3 754316 523105917 1 0.15% 0.10% 0.09% 0 HSRP Common | ||||||||||||||||||||||||
385 2182508 14151135 154 0.15% 0.10% 0.14% 0 L3 Manager | ||||||||||||||||||||||||
317 44655884 658073408 67 0.07% 0.04% 0.21% 0 PDU DISPATCHER | ||||||||||||||||||||||||
395 4363480 4661440 936 0.07% 0.04% 0.05% 0 HIDDEN VLAN Proc | ||||||||||||||||||||||||
323 1161648 134374319 8 0.07% 0.04% 0.05% 0 VRRS Main thread | ||||||||||||||||||||||||
56 2269676 9230664 245 0.07% 0.08% 0.07% 0 Per-Second Jobs | ||||||||||||||||||||||||
240 1449416 1870109 775 0.07% 0.04% 0.05% 0 Compute load avg | ||||||||||||||||||||||||
243 1488814081309230003 113 0.07% 0.13% 0.76% 0 IP SNMP
|
06-29-2014 02:03 AM
Hi,
BGP Router process is in charge to determine the best path and processes any route "churn". It also sends and receives routes, establishes peers, and interacts with the routing information base (RIB).
(http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/107615-highcpu-bgp.html)
So I suggest to check what make this process working hard. Depending on that you can choose what to do: bgp dampening (if you have many changes in advertisement received form a neighbor), tuning timer (if neighbor is flapping), using peer-group / update-groups to reduce the amount of job your BGP process has to do to process updates etc...
Have a look here: https://supportforums.cisco.com/discussion/11604471/high-cpu-usage-bgp-router-process
Bye,
enrico
PS please rate if useful
06-29-2014 05:08 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide