06-29-2016 12:09 AM - edited 03-05-2019 04:19 AM
Hi Guys
I am having intermittent high cpu on the 7206VXR (NPE-G1) router which goes above 70% and comes back normal to 40 % after sometime
when it goes high Per-Second Jobs shows 1.35% and on interface showing output and input drops both WAN and Gi0/1 as well
Router ISP BW is 600Mbps .need to know if its a traffic /QOS which router is not able to handle the load as in BW monitoring of WAN link goes avg on 220 mbps and Rx and Tx load is also not high
need to know what could be the issue or could be oversubscription of this input errors and unknown pro drop/output drops
below are the output of the interface and WAN utilization
sh proc cpu sort
CPU utilization for five seconds: 67%/64%; one minute: 71%; five minutes: 68%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
42 1722308028 99901457 17240 1.35% 1.37% 1.36% 0 Per-Second Jobs
157 4106996 2780438948 1 1.19% 1.11% 1.17% 0 HQF Shaper Backg
301 88 139 633 0.31% 0.02% 0.00% 3 Virtual Exec
2 631196 19798863 31 0.07% 0.07% 0.07% 0 Load Meter
169 87348 193259231 0 0.07% 0.00% 0.00% 0 CCE DP URLF cach
132 35960 93966142 0 0.07% 0.01% 0.00% 0 ILMI Timer Proce
118 998340 333361286 2 0.07% 0.02% 0.00% 0 TCP Timer
IOS:c7200-adventerprisek9-mz.124-24.T5.bin"
ID: CISCO7206VXR
interface GigabitEthernet0/3
description IP-CONNECT ISP WAN LINK
ip address 10.x.x.x.x 255.255.255.252
ip nbar protocol-discovery
ip flow ingress
ip flow egress
duplex auto
speed auto
media-type gbic
negotiation auto
service-policy output QOS
interface GigabitEthernet0/1
description Link to HQ
ip address 10..x.x.x.x 255.255.255.0
ip access-group 101 out
duplex full
speed 1000
media-type rj45
no negotiation auto
GigabitEthernet0/1 is up, line protocol is up
Description: Link to HQ
Internet address is 10.1.250.200/24
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 15/255, rxload 52/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is RJ45
output flow-control is unsupported, input flow-control is XON
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 8/75/0/113 (size/max/drops/flushes); Total output drops: 3910
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 205578000 bits/sec, 27942 packets/sec
5 minute output rate 61682000 bits/sec, 19778 packets/sec
3741785087 packets input, 3853071941 bytes, 0 no buffer
Received 91556612 broadcasts, 0 runts, 0 giants, 0 throttles
7029005 input errors, 0 CRC, 0 frame, 7029005 overrun, 0 ignored
0 watchdog, 209497288 multicast, 0 pause input
0 input packets with dribble condition detected
921491430 packets output, 585150574 bytes, 0 underruns
9 output errors, 0 collisions, 3 interface resets
3295813 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
9 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
=============================================
GigabitEthernet0/3 is up, line protocol is up
Description: IP-CONNECT to ISP
Internet address is 10.x.x.x./30
MTU 1500 bytes, BW 600000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 83/255, rxload 24/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, link type is autonegotiation, media type is LX
output flow-control is XON, input flow-control is XON
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:24, output 00:00:00, output hang never
Last clearing of "show interface" counters 1y31w
Input queue: 0/75/16/252 (size/max/drops/flushes); Total output drops: 163912473
Queueing strategy: Class-based queueing
Output queue: 63/1000/0 (size/max total/drops)
5 minute input rate 56912000 bits/sec, 18717 packets/sec
5 minute output rate 195545000 bits/sec, 27055 packets/sec
3209462578 packets input, 1125360610 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
21972 input errors, 0 CRC, 0 frame, 21972 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
3899036769 packets output, 3478522230 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped ou
QOS:
policy-map QOS
class APPS_CLASS
priority percent 20
class TRAFFIC_CLASS
bandwidth percent 10
class UPDATE_CLASS
bandwidth percent 20
shape average percent 15
class class-default
bandwidth percent 20
100
90
80 ***** ***** ***** **********
70 ************************************************************
60 ************************************************************
50 ************************************************************
40 ************************************************************
30 ************************************************************
20 ************************************************************
10 ************************************************************
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per second (last 60 seconds)
797776766767777667766777667787877776667777677767666656655665
938375166661111843955742989804077702451301324643831274463414
--More-- 100
90 *
80 *** * * * * *** **** *
70 #####*#********* ##**###**######### ***** *** **
60 ####################################################**** **
50 ############################################################
40 ############################################################
30 ############################################################
20 ############################################################
10 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
07-01-2016 03:06 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Your high CPU utilization, as almost all interrupt CPU, already shows that.
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