cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
575
Views
0
Helpful
3
Replies
Highlighted
Beginner

Hight cpu related to ip input proccess

Gghhhhjhmss-mashreq-ebv-rb#sh processes cpu | exclude 0.00%__0.00%__0.00%
CPU utilization for five seconds: 85%/24%; one minute: 47%; five minutes: 52%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
2 5852 1943710 3 0.00% 0.01% 0.00% 0 Load Meter
3 1436 656 2189 0.00% 0.00% 0.04% 388 SSH Process
6 9214392 1481995 6217 0.00% 0.07% 0.06% 0 Check heaps
7 658172 1191890 552 1.83% 0.60% 0.44% 0 Pool Manager
13 6478680 161868 40024 0.00% 0.06% 0.05% 0 Licensing Auto U
16 9073012 9708951 934 0.00% 0.08% 0.06% 0 Environmental mo
58 65628 2938371 22 0.00% 0.05% 0.07% 0 Net Background
88 25068 1944822 12 0.07% 0.00% 0.00% 0 Compute load avg
89 1299292 325422 3992 0.00% 0.01% 0.00% 0 Per-minute Jobs
90 136100 9726598 13 0.07% 0.03% 0.02% 0 Per-Second Jobs
121 29664 19436110 1 0.07% 0.03% 0.02% 0 BPSM stat Proces
129 2608896 169655 15377 0.00% 0.01% 0.00% 0 BGP Scanner
132 186052 151815821 1 0.07% 0.05% 0.06% 0 VRRS Main thread
172 119244 303048076 0 0.07% 0.04% 0.05% 0 IPAM Manager
176 23063172 17761562 1298 58.39% 30.33% 32.02% 0 IP Input
204 149908 2416927979 0 0.07% 0.22% 0.23% 0 HQF Output Shape
210 33352 9705655 3 0.07% 0.01% 0.00% 0 ADJ background
323 3918640 9662965 405 0.00% 0.20% 0.52% 0 IP SNMP
340 981796 4224535 232 0.00% 0.05% 0.16% 0 PDU DISPATCHER
343 1690640 4197775 402 0.00% 0.18% 0.57% 0 SNMP ENGIN
====================================

3 REPLIES 3
Highlighted

IP Input process increases when packets are being punted to the CPU for forwarding or for the device to itself consume them instead of those being forwarded by a lookup in the CEF table.
Common reasons are:
- CEF is disabled globally or independently on an interface forwarding traffic.
- The Router is receiving too much traffic destined to an IP address it owns like a loopback or interface IP.
- The Router is receiving too much IP traffic coming in with TTL=1 in the IP header. The router has to punt it to CPU since decreasing the TTL  to zero makes it consume it.
- The Router has to fragment or reassemble fragmented IP packets. More commonly seen when there are GRE tunnels configured on the Router.
- There is an ACL with an entry having the “log” keyword, this ACL is attached to an interface and too many packets are hitting that entry. Those packets are punted to CPU for the ACL line to log an entry for the traffic.
- etc etc
The way to troubleshoot the IP Input process running high is by looking what of the previous reasons is impacting the Router while the IP input process is running high.

Highlighted
Hall of Fame Expert

Have you reviewed Cisco documents for troubleshooting this? E.g. : https://www.cisco.com/c/en/us/support/docs/routers/7500-series-routers/41160-highcpu-ip-input.html
Highlighted

mss-mashreq-ebv-rb# show int stat
Interface Embedded-Service-Engine0/0 is disabled

GigabitEthernet0/0
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 54646877 4220462401 3738616536 2011143320
Route cache 1575385487 4252113944 536405 100516846
Total 1630032364 4177609049 3739152941 2111660166
GigabitEthernet0/1
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 752504 49631272 975291 64273519
Route cache 1046299 191855342 1575385478 2245511103
Total 1798803 241486614 1576360769 2309784622
Interface GigabitEthernet0/2 is disabled

Cellular0/0/0
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 71 6453 71 11221
Route cache 0 0 0 0
Total 71 6453 71 11221
Interface Cellular0/0/1 is disabled

Loopback0
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 0 0 0 0
Route cache 0 0 0 0
Total 0 0 0 0
mss-mashreq-ebv-rb#

 

 

--------------------------------------------------------


No active filter modules.

Trap logging: level debugging, 54476 message lines logged
Logging to 86.96.226.101 (MSS) (udp port 514, audit disabled,
link up),
54475 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 86.96.228.248 (MSS) (udp port 514, audit disabled,
link up),
54476 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 217.165.211.117 (MSS) (udp port 514, audit disabled,
link up),
54476 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging Source-Interface: VRF Name:
Loopback0 MSS

Log Buffer (51200 bytes):
19 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.390 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.842 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.842 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.842 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.842 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.842 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.842 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full
Jul 7 2019 17:32:18.842 UAE: %SNMP-3-INPUT_QFULL_ERR: Packet dropped due to input queue full

-------------------------------------------------------------------------------------------

 

mss-mashreq-ebv-rb#show buffers input-interface gi0/0 packet

Public particle pools:

Private particle pools:

mss-mashreq-ebv-rb#show buffers input-interface gi0/1 packet

Public particle pools:

Private particle pools:

mss-mashreq-ebv-rb#

 

 

 

 

 

----------------------------------------------------------------------------

 

 

 

 

Content for Community-Ad