Overload CPU - Ip Input

Marcellus Wallace · ‎11-06-2017

Dear CISCO Team,

Crruntly I have deployed a C2900 Series Router. It's utilizing CPU maximum to 85% & Average to 70%. I have checked using process cpu command & found there is a process call IP Input which is using maximum CPU process. Kindly, advise me what is the problem with the router?

router01#sh processes cpu sorted
CPU utilization for five seconds: 82%/35%; one minute: 79%; five minutes: 79%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
172 1033953664 3057382342 0 43.59% 42.41% 42.31% 0 IP Input
194 607212 279558246 2 0.23% 0.23% 0.23% 0 Ethernet Msec Ti
31 1944 2158 900 0.23% 0.03% 0.00% 388 SSH Process
386 1846524 56961997 32 0.15% 0.12% 0.13% 0 PIM Process
406 405028 135801065 2 0.15% 0.13% 0.13% 0 HSRP Common
409 311880 105371205 2 0.15% 0.11% 0.10% 0 MFIB_mrib_write
168 186220 68086426 2 0.07% 0.05% 0.07% 0 IPAM Manager
128 231444 34214424 6 0.07% 0.06% 0.07% 0 VRRS Main thread
272 10580 4293113 2 0.07% 0.00% 0.00% 0 Inspect process
10 70320 2585980 27 0.00% 0.00% 0.00% 0 WATCH_AFS
11 0 1 0 0.00% 0.00% 0.00% 0 License Client N
12 0 1 0 0.00% 0.00% 0.00% 0 Image License br
13 3921412 36672 106932 0.00% 0.14% 0.12% 0 Licensing Auto U
14 0 1 0 0.00% 0.00% 0.00% 0 RMI RM Notify Wa
15 2009804 2199883 913 0.00% 0.07% 0.05% 0 Environmental mo
16 940 440354 2 0.00% 0.00% 0.00% 0 IPC Event Notifi
9 0 2 0 0.00% 0.00% 0.00% 0 Timers

Attached SH Running-config .

Thanks,

Reza Sharifi · ‎11-06-2017

Hi,

Have a look at this document for troubleshooting steps:

https://www.cisco.com/c/en/us/support/docs/routers/7500-series-routers/41160-highcpu-ip-input.html

HTH

Marcellus Wallace · ‎11-06-2017

Hi Team

Thanks, I following the procedure and here the result of the Debug that not understand to much good.

Kind regards.

14565705: Nov 6 18:50:47.700: FIBfwd-proc: Default:224.0.0.0/4 multicast entry
14565706: Nov 6 18:50:47.700: FIBipv4-packet-proc: packet routing failed
14565707: Nov 6 18:50:47.700: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.40 src 10.10.11.151 dst 239.0.10.1
14565708: Nov 6 18:50:47.700: FIBfwd-proc: Default:224.0.0.0/4 multicast entry
14565709: Nov 6 18:50:47.700: FIBipv4-packet-proc: packet routing failed
14565710: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1 (GigabitEthernet0/1.40), len 1344, output feature
14565711: Nov 6 18:50:47.700: UDP src=32988, dst=10004, MFIB Adjacency(92), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
14565712: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1 (GigabitEthernet0/1.40), len 1344, sending full packet
14565713: Nov 6 18:50:47.700: UDP src=32988, dst=10004
14565714: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1, len 1344, input feature
14565715: Nov 6 18:50:47.700: UDP src=32988, dst=10004, Access List(46), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
14565716: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1, len 1344, input feature
14565717: Nov 6 18:50:47.700: UDP src=32988, dst=10004, MCI Check(108), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
14565718: Nov 6 18:50:47.700: FIBipv4-packet-proc: route packet from GigabitEthernet0/0.15 src 10.10.11.151 dst 239.0.10.1
14565719: Nov 6 18:50:47.700: FIBfwd-proc: Default:224.0.0.0/4 multicast entry
14565720: Nov 6 18:50:47.700: FIBipv4-packet-proc: packet routing failed
14565721: Nov 6 18:50:47.700: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.40 src 10.10.11.151 dst 239.0.10.1
14565722: Nov 6 18:50:47.700: FIBfwd-proc: Default:224.0.0.0/4 multicast entry
14565723: Nov 6 18:50:47.700: FIBipv4-packet-proc: packet routing failed
14565724: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1 (GigabitEthernet0/1.40), len 1344, output feature
14565725: Nov 6 18:50:47.700: UDP src=32988, dst=10004, MFIB Adjacency(92), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
14565726: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1 (GigabitEthernet0/1.40), len 1344, sending full packet
14565727: Nov 6 18:50:47.700: UDP src=32988, dst=10004
14565728: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1, len 1344, input feature
14565729: Nov 6 18:50:47.700: UDP src=32988, dst=10004, Access List(46), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
14565730: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1, len 1344, input feature
14565731: Nov 6 18:50:47.700: UDP src=32988, dst=10004, MCI Check(108), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
14565732: Nov 6 18:50:47.700: FIBipv4-packet-proc: route packet from GigabitEthernet0/0.15 src 10.10.11.151 dst 239.0.10.1
14565733: Nov 6 18:50:47.700: FIBfwd-proc: Default:224.0.0.0/4 multicast entry
14565734: Nov 6 18:50:47.700: FIBipv4-packet-proc: packet routing failed
14565735: Nov 6 18:50:47.700: FIBipv4-packet-proc: route packet from GigabitEthernet0/1.40 src 10.10.11.151 dst 239.0.10.1
14565736: Nov 6 18:50:47.700: FIBfwd-proc: Default:224.0.0.0/4 multicast entry
14565737: Nov 6 18:50:47.700: FIBipv4-packet-proc: packet routing failed
14565738: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1 (GigabitEthernet0/1.40), len 1344, output feature
14565739: Nov 6 18:50:47.700: UDP src=32988, dst=10004, MFIB Adjacency(92), rtype 0, forus FALSE, sendself FALSE, mtu 0, fwdchk FALSE
14565740: Nov 6 18:50:47.700: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1 (GigabitEthernet0/1.40), len 1344, sending full packet
14565741: Nov 6 18:50:47.704: UDP src=32988, dst=10004
14565742: Nov 6 18:50:47.704: IP: s=10.10.11.151 (GigabitEthernet0/0.15), d=239.0.10.1, len 1344, input feature

Reza Sharifi · ‎11-06-2017

Hi,

Have a look at this post.

You may want to add a couple commands recommend in this post and test again.

https://supportforums.cisco.com/t5/lan-switching-and-routing/ip-input/td-p/2984212

HTH