Solved: IP Input.

azibnaseem · ‎10-25-2016

Dear CISCO Team,

Crruntly I have deployed a C2900 Series Router. It's utilizing CPU maximum to 80% & 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?

Any thing else related to configuration can be provided.

Thanks,

Palani Mohan · ‎10-27-2016

Dear Naseem

Thank you for sending the data. It is very helpful. Reviewing it, I recommend two config changes. These are:

#1

ip access-list extended cisin
.
.
.
deny   ip 10.0.0.0 0.255.255.255 any log
deny   ip 172.16.0.0 0.15.255.255 any log
deny   ip 192.168.0.0 0.0.255.255 any log
deny   ip 182.177.0.0 0.0.255.255 any log

Notice the log keyword at the end? This is causing pkts matching this ACL to be process switched. The process name associated with process switching is IP Input. Since we are dealing with pkts transiting the router, please plan a very short maint window, remove the ACL from Gi0/0 and Gi0/1 using the cmd "no ip access-group cisin in" and "no ip access-group cisin out".

Then proceed to modify the ACL such that the same deny lines shown above are typed but this time, without the log word at the end. After making changes to the ACL, please apply the ACL again to the interfaces Gi0/0 and Gi0/1

Second config change I recommend is:

int gig 0/1

ip route-cache

ip route-cache cef

int gig 0/2

ip route-cache

ip route-cache cef

NOTE: I see very little traffic for Gig0/1 but, based on the description, it is likely that you are using this as backup forGig0/0. So, when traffic is flowing through Gi0/1, unless the above change is made, it will cause IP Input to be high, again.

Feel free to ask any questions OR clarifications on the above. I will do my best to answer them.

Kind regards .... Palani

View solution in original post

Palani Mohan · ‎10-31-2016

Hi Naseem

Very glad to hear the problem is resolved. Here is some more info. A router by nature is responsible for moving pkts between interfaces. CPU is involved in moving/routing pkts.

Routing pkts may be process switched OR interrupt switched. In other words, by default, a Cisco router would interrupt switch a pkt. When it is unable to do so, pkt is left to process switching to take care of routing this pkt. The process name associated with process switching is "IP Input.

Process switching is many times slower than interrupt switching. These days, most of the pkts are expected to be interrupt switched. So, when you reported CPU was high due to process switching, the way I interpreted was "what is causing interrupt switching to handoff these pkts to process switching?". This is the background for asking for the running-config.

One of Mark's response listed the conditions that would cause the pkt to be process switched. We identified the precise cause and that is the background for the changes recommended. The document named Troubleshooting High CPU Utilization in IP Input Process is the basis for our discussion.
Kind regards ... Palani

View solution in original post

Mark Malone · ‎10-25-2016

Hi

high cpu from ip input can be a number of things was there anything 2nd high in your proc output or anything in logs showing cpu related or irregular ?

cef is enabled yes

no logging on acls ? this causes it too

was there high interrupt traffic ? can you post your show proc cpu sorted , if the routers over utilized it will process switch traffic which will shoot up ip input and cpu as its sent there instead of being cef switched

IP Input

The Cisco IOS^® software process called IP input takes care of process-switching IP packets. If the IP input process uses unusually high CPU resources, the router is process-switching a lot of IP traffic. Check these issues:

Interrupt switching is disabled on an interface (or interfaces) that has (have) a lot of traffic

Interrupt switching refers to the use of switching algorithms other than process switching. Examples include fast switching, optimum switching, Cisco Express Forwarding switching, and so on (refer to Performance Tuning Basics for details). Examine the output of the show interfaces switching command to see which interface is burdened with traffic. You can check the show ip interface command to see which switching method(s) are used on each interface. Re-enable interrupt switching on that interface. Remember that regular fast switching is configured on output interfaces: if fast switching is configured on an interface, packets that go out of that interface are fast-switched. Cisco Express Forwarding switching is configured on input interfaces. To create Forwarding Information Base (FIB) and adjacency table entries on a particular interface, configure Cisco Express Forwarding switching on all interfaces that route to that interface.
Fast switching on the same interface is disabled

If an interface has a lot of secondary addresses or subinterfaces and there is a lot of traffic sourced from the interface and destined for an address on that same interface, then all of those packets are process-switched. In this situation, you should enable ip route-cache same-interface on the interface. When Cisco Express Forwarding switching is used, you do not need to enable Cisco Express Forwarding switching on the same interface separately.
Fast switching on an interface providing policy routing is disabled

If a route-map has been configured on an interface, and a lot of traffic is handled by the route-map, then the router process-switches this traffic. In this situation, you should enable ip route-cache policy on the interface. Check the restrictions mentioned in the "Enabling Fast-Switched Policy-Based Routing" section of Configuring Policy-Based Routing.
Traffic that cannot be interrupt-switched arrives

This can be any of the listed types of traffic. Click on linked items for more information.
- Packets for which there is no entry yet in the switching cache
  
  Even if fast, optimum, or Cisco Express Forwarding switching (CEF) is configured, a packet for which there is no match in the fast-switching cache or FIB and adjacency tables is processed. An entry is then created in the appropriate cache or table, and all subsequent packets that match the same criteria are fast, optimum, or CEF-switched. In normal circumstances, these processed packets do not cause high CPU utilization. However, if there is a device in the network which 1) generates packets at an extremely high rate for devices reachable through the router, and 2) uses different source or destination IP addresses, there is not a match for these packets in the switching cache or table, so they are processed by the IP Input process (if NetFlow switching is configured, source and destination TCP ports are checked against entries in the NetFlow cache as well). This source device can be a non-functional device or, more likely, a device attempting an attack.
  
  (*) Only with glean adjacencies. Refer to Cisco Express Forwarding for more information about Cisco Express Forwarding adjacencies.
- Packets destined for the router
  
  These are examples of packets destined for the router:
  - Routing updates that arrive at an extremely high rate. If the router receives an enormous amount of routing updates that have to be processed, this task might overload the CPU. Normally, this cannot happen in a stable network. The way you can gather more information depends on the routing protocol you have configured. However, you can start to check the output of the show ip route summary command periodically. Values that change rapidly are a sign of an unstable network. Frequent routing table changes mean increased routing protocol processing, which results in increased CPU utilization. For further information on how to troubleshoot this issue, refer to the Troubleshooting TCP/IP section of the Internetwork Troubleshooting Guide.
  - Any other kind of traffic destined for the router. Check who is logged on to the router and user actions. If someone is logged on and issues commands that produce long output, the high CPU utilization by the "IP input" process is followed by a much higher CPU utilization by the Virtual Exec process.
  - Spoof attack. To identify the problem, issue the show ip traffic command to check the amount of IP traffic. If there is a problem, the number of received packets with a local destination is significant. Next, examine the output of the show interfaces and show interfaces switching commands to check which interface the packets are coming in. Once you have identified the receiving interface, turn on ip accounting on the outgoing interface and see if there is a pattern. If there is an attack, the source address is almost always different, but the destination address is the same. An access list can be configured to solve the issue temporarily (preferably on the device closest to the source of the packets), but the real solution is to track down the source device and stop the attack.
- Broadcast traffic
  
  Check the number of broadcast packets in the show interfaces command output. If you compare the amount of broadcasts to the total amount of packets that were received on the interface, you can gain an idea of whether there is an overhead of broadcasts. If there is a LAN with several switches connected to the router, then this can indicate a problem with Spanning Tree.
- IP packets with options
- Packets that require protocol translation
- Multilink Point-to-Point Protocol (supported in Cisco Express Forwarding switching)
- Compressed traffic
  
  If there is no Compression Service Adapter (CSA) in the router, compressed packets must be process-switched.
- Encrypted traffic
  
  If there is no Encryption Service Adapter (ESA) in the router, encrypted packets must be process-switched.
- Packets that go through serial interfaces with X.25 encapsulation
  
  In the X.25 protocol suite, flow control is implemented on the second Open System Interconnection (OSI) layer.
A lot of packets, that arrive at an extremely high rate, for a destination in a directly attached subnet, for which there is no entry in the Address Resolution Protocol (ARP) table. This should not happen with TCP traffic because of the windowing mechanism, but can happen with User Datagram Protocol (UDP) traffic. To identify the problem, repeat the actions suggested in order to track down a spoof attack.
A lot of multicast traffic goes through the router. Unfortunately, there is no easy way to examine the amount of multicast traffic. The show ip traffic command only shows summary information. However, if you have configured multicast routing on the router, you can enable fast-switching of multicast packets with the ip mroute-cache interface configuration command (fast-switching of multicast packets is off by default).
Router is oversubscribed. If the router is over-used and cannot handle this amount of traffic, try to distribute the load among other routers or purchase a high-end router.
IP Network Address Translation (NAT) is configured on the router, and lots of Domain Name System (DNS) packets go through the router. UDP or TCP packets with source or destination port 53 (DNS) are always punted to process level by NAT.
There are other packet types that are punted to processing.
There is fragmentation of IP Datagram. There is a small increase in CPU and memory overhead due to fragment of an IP datagram. Refer to Resolve IP Fragmentation, MTU, MSS, and PMTUD Issues with GRE and IPSEC for more information on how to troubleshoot this issue.

Whatever the reason for high CPU utilization in the IP Input process, the source of the problem can be tracked down if you debug the IP packets. Since the CPU utilization is already high, the debug process has to be performed with extreme caution. The debug process produces lots of messages, so only logging buffered should be configured.

Logging to a console raises unnecessary interrupts to the CPU and increases the CPU utilization. Logging to a host (or monitor logging) generates additional traffic on interfaces.

The debug process can be started with the debug ip packet detail exec command. This session should not last longer than three to five seconds. Debugging messages are written in the logging buffer. A capture of a sample IP debugging session is provided in the Sample IP Packet Debugging Session section of this document. Once the source device of unwanted IP packets is found, this device can be disconnected from the network, or an access list can be created on the router to drop packets from that destination.

azibnaseem · ‎10-25-2016

Dear Mark,

Thanks for the reply.

ip cef is enabled. show proc cpu, screen shot is attached for your kind reference. Kindly, review and advise accordingly.

Thanks,

Mark Malone · ‎10-26-2016

Hi there is a large amount of interrupt traffic 34% being process switched router looks to be over utilized looking at that output , has this being happening since the install ?

what does the show proc cpu history provide can you post that

are your interfaces constantly running hot ?

azibnaseem · ‎10-26-2016

Hi,

Yes, it is happening since the installation.

Screen shots are attached for cpu proc history.

I have checked all interfaces are working normally.

Mark Malone · ‎10-26-2016

Looking at the outputs there's too much traffic going through the router , 72hr cpu shows it did drop off for a period but started back up again so something is causing it from the lan side , your saying the interfaces are ok but have you calculated the volume of traffic going through them ,when its like this are you saying there 1/255 or whats the use on them , you will probably need to do a debug as the previous post shows steps how to identify what might be causing high cpu from ip input , each one of these steps needs to be ruled out until you get to the debug and see exactly whats causing it , debugging ip packet can kill a router that's got too much traffic going through it so make sure its sent to the buffer and overwrites itself rather than to the console or it might just completely hang

msamighersheen · ‎05-20-2022

sh ip traffic
IP statistics:
Rcvd: 22364849 total, 5283015 local destination
0 format errors, 0 checksum errors, 0 bad hop count
0 unknown protocol, 17081834 not a gateway
0 security failures, 0 bad options, 4254550 with options
Opts: 0 end, 0 nop, 0 basic security, 0 loose source route
0 timestamp, 0 extended security, 0 record route
0 stream ID, 0 strict source route, 4254550 alert, 0 cipso, 0 ump
0 other
Frags: 0 reassembled, 0 timeouts, 0 couldn't reassemble
3068 fragmented, 0 couldn't fragment
Bcast: 2118152 received, 0 sent
Mcast: 0 received, 0 sent
Sent: 2442625 generated, 0 forwarded
Drop: 637350 encapsulation failed, 0 unresolved, 0 no adjacency
0 no route, 0 unicast RPF, 0 forced drop
0 options denied, 0 source IP address zero

ICMP statistics:
Rcvd: 0 format errors, 0 checksum errors, 0 redirects, 0 unreachable
149174 echo, 0 echo reply, 0 mask requests, 0 mask replies, 0 quench
0 parameter, 0 timestamp, 0 info request, 0 other
0 irdp solicitations, 0 irdp advertisements
Sent: 0 redirects, 0 unreachable, 0 echo, 149174 echo reply
0 mask requests, 0 mask replies, 0 quench, 0 timestamp
0 info reply, 0 time exceeded, 0 parameter problem
0 irdp solicitations, 0 irdp advertisements

TCP statistics:
Rcvd: 38807 total, 0 checksum errors, 199 no port
Sent: 12995 total

PIMv2 statistics: Sent/Received
Total: 0/0, 0 checksum errors, 0 format errors
Registers: 0/0 (0 non-rp, 0 non-sm-group), Register Stops: 0/0, Hellos: 0/0
Join/Prunes: 0/0, Asserts: 0/0, grafts: 0/0
Bootstraps: 0/0, Candidate_RP_Advertisements: 0/0
State-Refresh: 0/0

IGMP statistics: Sent/Received
Total: 0/0, Format errors: 0/0, Checksum errors: 0/0
Host Queries: 0/0, Host Reports: 0/0, Host Leaves: 0/0
DVMRP: 0/0, PIM: 0/0

UDP statistics:
Rcvd: 5095007 total, 0 checksum errors, 750789 no port
Sent: 2280459 total, 0 forwarded broadcasts

ARP statistics:
Rcvd: 102347639 requests, 160275 replies, 0 reverse, 0 other
Sent: 25 requests, 117950 replies (0 proxy), 0 reverse
Drop due to input queue full: 29913

Palani Mohan · ‎10-26-2016

Dear Naseem

From show proc cpu, we see about 60% of the CPU cycles is spent servicing IP Input. The “past 72 hours” section indicate CPU is following business hours.

60+% used by IP Input needs to be investigated, for sure. Troubleshooting why CPU is high due to IP Input is among the most complex of the problems. Trying to make progress via forum adds an additional dimension to the complexity.

With this for background, please log the output of the following to a txt file and send it over:

term exec prompt timestamp
show tech
term len 0
show log

Take the output of the following 2-3 times, 30-45 sec apart

show int
show int summary
show ip traffic
show ip cef switching stats
show ip cef switching stats feature

NOTE: None of the above is service impacting and so, can be captured any time, during the day. Having said that all of the above needs to be captured when IP Input is atleast 45%

To save a session as a txt file, please familiarize yourself with
https://www.packet6.com/saving-your-putty-sessions-to-a-log-file/

Sincerely ... Palani

azibnaseem · ‎10-27-2016

Dear Mr. Palani,

Thanks for the reply.

I have followed the steps and made a file. File is attached, kindly review and advise accordingly.

Thanks,

Palani Mohan · ‎10-27-2016

Dear Naseem

Thank you for sending the data. It is very helpful. Reviewing it, I recommend two config changes. These are:

#1

ip access-list extended cisin
.
.
.
deny   ip 10.0.0.0 0.255.255.255 any log
deny   ip 172.16.0.0 0.15.255.255 any log
deny   ip 192.168.0.0 0.0.255.255 any log
deny   ip 182.177.0.0 0.0.255.255 any log

Notice the log keyword at the end? This is causing pkts matching this ACL to be process switched. The process name associated with process switching is IP Input. Since we are dealing with pkts transiting the router, please plan a very short maint window, remove the ACL from Gi0/0 and Gi0/1 using the cmd "no ip access-group cisin in" and "no ip access-group cisin out".

Then proceed to modify the ACL such that the same deny lines shown above are typed but this time, without the log word at the end. After making changes to the ACL, please apply the ACL again to the interfaces Gi0/0 and Gi0/1

Second config change I recommend is:

int gig 0/1

ip route-cache

ip route-cache cef

int gig 0/2

ip route-cache

ip route-cache cef

NOTE: I see very little traffic for Gig0/1 but, based on the description, it is likely that you are using this as backup forGig0/0. So, when traffic is flowing through Gi0/1, unless the above change is made, it will cause IP Input to be high, again.

Feel free to ask any questions OR clarifications on the above. I will do my best to answer them.

Kind regards .... Palani

azibnaseem · ‎10-28-2016

Dear Mr. Palani,

Thank you so much for your reply.

I have made configuration changes suggested by you after that problem has been solved and cpu usage is reduced to 20 %. It's really helpful for me.

Kind Regards'

Palani Mohan · ‎10-31-2016

Hi Naseem

Very glad to hear the problem is resolved. Here is some more info. A router by nature is responsible for moving pkts between interfaces. CPU is involved in moving/routing pkts.

Routing pkts may be process switched OR interrupt switched. In other words, by default, a Cisco router would interrupt switch a pkt. When it is unable to do so, pkt is left to process switching to take care of routing this pkt. The process name associated with process switching is "IP Input.

Process switching is many times slower than interrupt switching. These days, most of the pkts are expected to be interrupt switched. So, when you reported CPU was high due to process switching, the way I interpreted was "what is causing interrupt switching to handoff these pkts to process switching?". This is the background for asking for the running-config.

One of Mark's response listed the conditions that would cause the pkt to be process switched. We identified the precise cause and that is the background for the changes recommended. The document named Troubleshooting High CPU Utilization in IP Input Process is the basis for our discussion.
Kind regards ... Palani

azibnaseem · ‎11-01-2016

Dear Mr. Palani,

I am very thankful to you fro your kind support. It's really helpful for me in order to resolve my issue.

I need to know on thing that how would I differentiate between Interrupt switched or Process switched Packets.

kind Regards'

johan · ‎09-08-2019

I have this problem too, may i ask what i must change on my configuration?

CPU utilization for five seconds: 98%/77%; one minute: 90%; five minutes: 80%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
173 20522548 116868497 175 19.93% 14.24% 4.72% 0 IP Input
387 17742916 4284630711 0 0.39% 0.64% 0.79% 0 IP SLAs XOS Even
157 5704 1236 4614 0.15% 0.18% 0.10% 390 Virtual Exec

Thanks

msamighersheen · ‎05-20-2022

CPU utilization for five seconds: 26%/3%; one minute: 32%; five minutes: 39%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
1 143 1300 110 0.00% 0.00% 0.00% 0 Chunk Manager
2 2752 127281 21 0.00% 0.00% 0.00% 0 Load Meter
3 101 5492 18 0.00% 0.00% 0.00% 0 DHCPD Timer
4 7867037 353766 22237 10.86% 1.63% 1.24% 0 Check heaps
5 447 969 461 0.00% 0.00% 0.00% 0 Pool Manager
6 0 2 0 0.00% 0.00% 0.00% 0 Timers
7 0 2 0 0.00% 0.00% 0.00% 0 License Client N
8 1428680 10606 134704 0.00% 0.13% 0.15% 0 Licensing Auto U
9 84 3 28000 0.00% 0.00% 0.00% 0 Image License br
10 17865289 61513707 290 0.31% 3.65% 5.41% 0 ARP Input
11 0 12 0 0.00% 0.00% 0.00% 0 AAA_SERVER_DEADT
12 0 2 0 0.00% 0.00% 0.00% 0 AAA high-capacit
13 0 1 0 0.00% 0.00% 0.00% 0 Policy Manager
14 16 9 1777 0.00% 0.00% 0.00% 0 Entity MIB API
15 0 1 0 0.00% 0.00% 0.00% 0 IFS Agent Manage
16 323 10607 30 0.00% 0.00% 0.00% 0 IPC Dynamic Cach
17 0 1 0 0.00% 0.00% 0.00% 0 IPC Zone Manager
18 46465 628415 73 0.00% 0.00% 0.00% 0 IPC Periodic Tim
19 8 1 8000 0.00% 0.00% 0.00% 0 IPC Managed Time
20 7816 628436 12 0.00% 0.00% 0.00% 0 IPC Deferred Por
21 0 1 0 0.00% 0.00% 0.00% 0 IPC Seat Manager
22 0 1 0 0.00% 0.00% 0.00% 0 IPC Session Serv
23 59 4 14750 0.00% 0.00% 0.00% 0 PrstVbl
24 0 1 0 0.00% 0.00% 0.00% 0 Crash writer
25 0 1 0 0.00% 0.00% 0.00% 0 License IPC stat
26 0 1 0 0.00% 0.00% 0.00% 0 License IPC serv
27 14138 628354 22 0.00% 0.00% 0.00% 0 GraphIt
28 0 2 0 0.00% 0.00% 0.00% 0 SMART
29 0 2 0 0.00% 0.00% 0.00% 0 XML Proxy Client
30 0 1 0 0.00% 0.00% 0.00% 0 ARP Snoop
31 12320 628419 19 0.00% 0.00% 0.00% 0 Dynamic ARP Insp
32 0 1 0 0.00% 0.00% 0.00% 0 Critical Bkgnd
33 40058 76379 524 0.00% 0.00% 0.00% 0 Net Background
34 0 2 0 0.00% 0.00% 0.00% 0 IDB Work
35 0 27 0 0.00% 0.00% 0.00% 0 Logger
36 19693 628369 31 0.00% 0.00% 0.00% 0 TTY Background
37 387537 628540 616 0.15% 0.12% 0.08% 0 Per-Second Jobs
38 320006 10861 29463 0.00% 0.03% 0.00% 0 Per-minute Jobs
39 9 7 1285 0.00% 0.00% 0.00% 0 IF-MGR control p
40 9 14 642 0.00% 0.00% 0.00% 0 IF-MGR event pro
41 0 1 0 0.00% 0.00% 0.00% 0 Inode Table Dest
42 0 1 0 0.00% 0.00% 0.00% 0 AggMgr Process
43 17 1087 15 0.00% 0.00% 0.00% 0 Transport Port A
44 9348 177970 52 0.00% 0.00% 0.00% 0 HC Counter Timer
45 0 1 0 0.00% 0.00% 0.00% 0 SFF8472
46 9 37 243 0.00% 0.00% 0.00% 0 EEM ED Identity
47 0 73 0 0.00% 0.00% 0.00% 0 EEM ED MAT
48 9292 52004 178 0.00% 0.00% 0.00% 0 EEM ED ND
49 52 69 753 0.00% 0.00% 0.00% 0 USB Startup
50 32852 12380821 2 0.00% 0.00% 0.00% 0 DownWhenLooped
51 0 1 0 0.00% 0.00% 0.00% 0 HULC PBR Tcam Me
52 0 1 0 0.00% 0.00% 0.00% 0 HULC ACL Tcam Me
53 0 1 0 0.00% 0.00% 0.00% 0 Hulc Warm Upgrad
54 0 1 0 0.00% 0.00% 0.00% 0 HRPC lpip reques
55 0 2 0 0.00% 0.00% 0.00% 0 HLPIP Sync Proce
56 0 1 0 0.00% 0.00% 0.00% 0 HRPC hnetwpol re
57 0 1 0 0.00% 0.00% 0.00% 0 HRPC EnergyWise
58 0 1 0 0.00% 0.00% 0.00% 0 HRPC actual powe
59 18334 2508639 7 0.00% 0.00% 0.00% 0 HUSB Console
60 0 1 0 0.00% 0.00% 0.00% 0 HULC QM Tcam Mem
61 839 21364 39 0.00% 0.00% 0.00% 0 Net Input
62 36533 127262 287 0.00% 0.00% 0.00% 0 Compute load avg
63 4136 12 344666 0.00% 0.00% 0.00% 0 X2 HAMM detect p
64 0 1 0 0.00% 0.00% 0.00% 0 Madmax Process
65 0 1 0 0.00% 0.00% 0.00% 0 HRPC asic-stats
66 15009250 6751747 2223 2.39% 2.17% 2.15% 0 RedEarth I2C dri
67 25049707 4162116 6018 3.19% 3.58% 3.49% 0 RedEarth Tx Mana
68 333519 3357821 99 0.00% 0.03% 0.06% 0 RedEarth Rx Mana
69 3225 127281 25 0.00% 0.00% 0.00% 0 HULC Thermal Pro
70 0 1 0 0.00% 0.00% 0.00% 0 HRPC hsm request
71 0 8 0 0.00% 0.00% 0.00% 0 Stack Mgr
72 168 9 18666 0.00% 0.00% 0.00% 0 Stack Mgr Notifi
73 922 85991 10 0.00% 0.00% 0.00% 0 Adjust Regions
74 71725 628391 114 0.00% 0.00% 0.00% 0 hrpc -> response
75 2818 154391 18 0.00% 0.00% 0.00% 0 hrpc -> request
76 12778 153873 83 0.00% 0.00% 0.00% 0 hrpc <- response
77 0 1 0 0.00% 0.00% 0.00% 0 HRPC hcomp reque
78 17542 3127612 5 0.00% 0.00% 0.00% 0 yeti2_emac_proce
79 0 11 0 0.00% 0.00% 0.00% 0 HULC Device Mana
80 0 3 0 0.00% 0.00% 0.00% 0 HRPC hdm non blo
81 0 2 0 0.00% 0.00% 0.00% 0 HRPC hdm blockin
82 2469 127271 19 0.00% 0.00% 0.00% 0 HIPC bkgrd proce
83 0 1 0 0.00% 0.00% 0.00% 0 RTTYS Process
84 117 1728 67 0.00% 0.00% 0.00% 0 Hulc Port-Securi
85 0 1 0 0.00% 0.00% 0.00% 0 HRPC hpsecure re
86 0 1 0 0.00% 0.00% 0.00% 0 HRPC hlfm reques
87 167865 18268438 9 0.15% 0.03% 0.04% 0 HLFM address lea
88 41242 628371 65 0.00% 0.00% 0.00% 0 HLFM aging proce
89 92262 18294191 5 0.00% 0.01% 0.00% 0 HLFM address ret
90 0 1 0 0.00% 0.00% 0.00% 0 HRPC hrcmd reque
91 8 5 1600 0.00% 0.00% 0.00% 0 HRPC emac reques
92 8237 30987 265 0.00% 0.00% 0.00% 0 HRPC hulc misc r
93 2972 212118 14 0.00% 0.00% 0.00% 0 HVLAN main bkgrd
94 0 2 0 0.00% 0.00% 0.00% 0 HVLAN Mapped Vla
95 0 2 0 0.00% 0.00% 0.00% 0 Vlan shutdown Pr
96 4825 23241 207 0.00% 0.00% 0.00% 0 HRPC vlan reques
97 0 1 0 0.00% 0.00% 0.00% 0 HULC VLAN REF Ba
98 314 10608 29 0.00% 0.00% 0.00% 0 hulc_xps_process
99 0 1 0 0.00% 0.00% 0.00% 0 HRPC ilp request
100 121912 628382 194 0.00% 0.00% 0.00% 0 Hulc ILP Alchemy
101 279 769 362 0.00% 0.00% 0.00% 0 HULC PM Vector P
102 0 1 0 0.00% 0.00% 0.00% 0 HPM Msg Retry Pr
103 299 10611 28 0.00% 0.00% 0.00% 0 DHCPD Database
104 718473 10567534 67 0.00% 0.18% 0.25% 0 hpm main process
105 0 10 0 0.00% 0.00% 0.00% 0 HPM Stack Sync P
106 0 1 0 0.00% 0.00% 0.00% 0 HRPC pm request
107 9 3 3000 0.00% 0.00% 0.00% 0 HPM if_num mappi
108 4135763 628221 6583 0.63% 0.66% 0.68% 0 hpm counter proc
109 0 1 0 0.00% 0.00% 0.00% 0 HRPC pm-counters
110 0 4 0 0.00% 0.00% 0.00% 0 hpm vp events ca
111 0 1 0 0.00% 0.00% 0.00% 0 HRPC hcmp reques
112 0 303 0 0.00% 0.00% 0.00% 0 HCEF ADJ Refresh
113 0 1 0 0.00% 0.00% 0.00% 0 HRPC hl3mm reque
114 0 1 0 0.00% 0.00% 0.00% 0 hl3md_rpfq_thrl_
115 4919 444147 11 0.00% 0.00% 0.00% 0 hl3mm
116 2270 317762 7 0.00% 0.00% 0.00% 0 hl3mm_rp
117 0 1 0 0.00% 0.00% 0.00% 0 HACL Queue Proce
118 0 1 0 0.00% 0.00% 0.00% 0 HRPC acl request
119 0 29 0 0.00% 0.00% 0.00% 0 HACL Acl Manager
120 0 1 0 0.00% 0.00% 0.00% 0 HRPC aim request
121 0 1 0 0.00% 0.00% 0.00% 0 HRPC backup inte
122 1751 2132 821 0.00% 0.00% 0.00% 0 OBFL TEMP obfl0
123 0 1 0 0.00% 0.00% 0.00% 0 HRPC cdp request
124 0 1 0 0.00% 0.00% 0.00% 0 HULC CISP Proces
125 0 1 0 0.00% 0.00% 0.00% 0 HRPC dot1x reque
126 0 1 0 0.00% 0.00% 0.00% 0 Dot1X Msg Retry
127 0 4 0 0.00% 0.00% 0.00% 0 HULC DOT1X Proce
128 0 1 0 0.00% 0.00% 0.00% 0 HRPC lldp reques
129 0 1 0 0.00% 0.00% 0.00% 0 HRPC system mtu
130 0 1 0 0.00% 0.00% 0.00% 0 HRPC sdm request
131 0 1 0 0.00% 0.00% 0.00% 0 SMI MSG Retry Pr
132 0 1 0 0.00% 0.00% 0.00% 0 HRPC Smart Insta
133 71365 3127622 22 0.00% 0.02% 0.00% 0 Hulc Storm Contr
134 0 2 0 0.00% 0.00% 0.00% 0 HSTP Sync Proces
135 0 1 0 0.00% 0.00% 0.00% 0 HRPC stp_cli req
136 0 1 0 0.00% 0.00% 0.00% 0 HRPC stp_state_s
137 0 2 0 0.00% 0.00% 0.00% 0 S/W Bridge Proce
138 0 1 0 0.00% 0.00% 0.00% 0 HRPC hudld reque
139 0 1 0 0.00% 0.00% 0.00% 0 HRPC vqpc reques
140 0 1 0 0.00% 0.00% 0.00% 0 HRPC hled reques
141 5116385 14723603 347 0.00% 0.99% 1.37% 0 Hulc LED Process
142 24936 465831 53 0.00% 0.00% 0.00% 0 HL3U bkgrd proce
143 0 1 0 0.00% 0.00% 0.00% 0 HRPC hl3u reques
144 1367 145563 9 0.00% 0.00% 0.00% 0 HL3U PBR bkgrd p
145 78 5315 14 0.00% 0.00% 0.00% 0 HL3U PBR n-h res
146 0 1 0 0.00% 0.00% 0.00% 0 HRPC obfl reques
147 3593 2337 1537 0.00% 0.13% 0.14% 1 SSH Process
148 0 1 0 0.00% 0.00% 0.00% 0 HRPC dtp request
149 0 1 0 0.00% 0.00% 0.00% 0 HRPC show_forwar
150 0 1 0 0.00% 0.00% 0.00% 0 HRPC snmp reques
151 0 1 0 0.00% 0.00% 0.00% 0 HULC SNMP Proces
152 1094132 127285 8595 0.15% 0.15% 0.15% 0 HQM Stack Proces
153 273748 254535 1075 0.15% 0.04% 0.04% 0 HRPC qos request
154 0 1 0 0.00% 0.00% 0.00% 0 HRPC span reques
155 0 1 0 0.00% 0.00% 0.00% 0 HRPC system post
156 0 1 0 0.00% 0.00% 0.00% 0 Hulc Reload Mana
157 0 1 0 0.00% 0.00% 0.00% 0 HRPC hrcli-event
158 59 3544 16 0.00% 0.00% 0.00% 0 HCMP sync proces
159 0 2 0 0.00% 0.00% 0.00% 0 image mgr
160 0 1 0 0.00% 0.00% 0.00% 0 HRFS OIR Proc
161 67 9 7444 0.00% 0.00% 0.00% 0 HL2MCM
162 60 9 6666 0.00% 0.00% 0.00% 0 HL2MCM
163 0 22 0 0.00% 0.00% 0.00% 0 AAA Server
164 8 57 140 0.00% 0.00% 0.00% 0 AAA ACCT Proc
165 0 1 0 0.00% 0.00% 0.00% 0 ACCT Periodic Pr
166 0 1 0 0.00% 0.00% 0.00% 0 AAA System Acct
167 0 1 0 0.00% 0.00% 0.00% 0 AUTH POLICY Fram
168 8 9 888 0.00% 0.00% 0.00% 0 Auth Manager
169 0 1 0 0.00% 0.00% 0.00% 0 Auth-proxy AAA B
170 9 2127 4 0.00% 0.00% 0.00% 0 IP Admin SM Proc
171 77726 120830 643 0.00% 0.01% 0.00% 0 CDP Protocol
172 118 11 10727 0.00% 0.00% 0.00% 0 SpanTree Helper
173 0 2 0 0.00% 0.00% 0.00% 0 ENABLE AAA
174 0 1 0 0.00% 0.00% 0.00% 0 CMD HANDLER
175 0 2 0 0.00% 0.00% 0.00% 0 AAA Dictionary R
176 42 5316 7 0.00% 0.00% 0.00% 0 DHCP Snooping
177 0 2 0 0.00% 0.00% 0.00% 0 Dot1x Mgr Proces
178 0 1 0 0.00% 0.00% 0.00% 0 EAP Framework
179 0 1 0 0.00% 0.00% 0.00% 0 EAP Test
180 0 3 0 0.00% 0.00% 0.00% 0 CEF switching ba
181 2150425 13655143 157 0.00% 0.59% 0.98% 0 IP Input
182 0 1 0 0.00% 0.00% 0.00% 0 ICMP event handl
183 4979 1226965 4 0.00% 0.00% 0.00% 0 IP ARP Track
184 1405 632503 2 0.00% 0.00% 0.00% 0 fnvRootHubPortSt
185 0 1 0 0.00% 0.00% 0.00% 0 tHUB
186 0 1 0 0.00% 0.00% 0.00% 0 IPv6 ping proces
187 0 1 0 0.00% 0.00% 0.00% 0 MAB Framework
188 1266 209 6057 0.00% 0.00% 0.00% 0 OBFL UPTIME obfl
189 0 1 0 0.00% 0.00% 0.00% 0 SMI Director DB
190 0 1 0 0.00% 0.00% 0.00% 0 SMI CDP Update H
191 0 1 0 0.00% 0.00% 0.00% 0 SMI Backup Proce
192 0 2 0 0.00% 0.00% 0.00% 0 SMI IBC server p
193 0 1 0 0.00% 0.00% 0.00% 0 SMI IBC client p
194 0 2 0 0.00% 0.00% 0.00% 0 SMI IBC Download
195 1461795 5915371 247 0.31% 0.28% 0.24% 0 Spanning Tree
196 1407 10635 132 0.00% 0.00% 0.00% 0 Spanning Tree St
197 0 12 0 0.00% 0.00% 0.00% 0 802.1x switch
198 243 10607 22 0.00% 0.00% 0.00% 0 802.1x MDA Aging
199 0 1 0 0.00% 0.00% 0.00% 0 802.1x Webauth F
200 0 2 0 0.00% 0.00% 0.00% 0 DTP Protocol
201 0 1 0 0.00% 0.00% 0.00% 0 HRPC dai request
202 0 1 0 0.00% 0.00% 0.00% 0 HULC DAI Process
203 0 1 0 0.00% 0.00% 0.00% 0 HRPC power down
204 0 1 0 0.00% 0.00% 0.00% 0 HRPC ip device t
205 0 1 0 0.00% 0.00% 0.00% 0 HRPC ip source g
206 0 1 0 0.00% 0.00% 0.00% 0 HULC IP Source g
207 409308 628361 651 0.00% 0.02% 0.05% 0 PI MATM Aging Pr
208 6690 637777 10 0.00% 0.00% 0.00% 0 UDLD
209 2940 57008 51 0.00% 0.00% 0.00% 0 Port-Security
210 0 2 0 0.00% 0.00% 0.00% 0 Switch Backup In
211 0 2 0 0.00% 0.00% 0.00% 0 IP Host Track Pr
212 0 1 0 0.00% 0.00% 0.00% 0 Link State Group
213 142 10607 13 0.00% 0.00% 0.00% 0 MMN bkgrd proces
214 745 63631 11 0.00% 0.00% 0.00% 0 Ethchnl
215 26 22 1181 0.00% 0.00% 0.00% 0 VMATM Callback
216 950 12728 74 0.00% 0.00% 0.00% 0 CEF background p
217 0 1 0 0.00% 0.00% 0.00% 0 IP IRDP
218 0 1 0 0.00% 0.00% 0.00% 0 CEF RF HULC Conv
219 0 2 0 0.00% 0.00% 0.00% 0 XDR mcast
220 678 63630 10 0.00% 0.00% 0.00% 0 IP ACL XDR LC Ba
221 0 1 0 0.00% 0.00% 0.00% 0 IPC LC Message H
222 0 1 0 0.00% 0.00% 0.00% 0 XDR RP Ping Back
223 42 5315 7 0.00% 0.00% 0.00% 0 XDR RP backgroun
224 0 1 0 0.00% 0.00% 0.00% 0 XDR RP Test Back
225 0 1 0 0.00% 0.00% 0.00% 0 Critical Auth
226 0 2 0 0.00% 0.00% 0.00% 0 LINE AAA
227 0 1 0 0.00% 0.00% 0.00% 0 IP RIB Update
228 77 579 132 0.00% 0.00% 0.00% 0 TCP Timer
229 27 147 183 0.00% 0.00% 0.00% 0 TCP Protocols
230 16147 1087760 14 0.00% 0.00% 0.00% 0 Socket Timers
231 51 2303 22 0.00% 0.00% 0.00% 0 HTTP CORE
232 49 7974 6 0.00% 0.00% 0.00% 0 Cluster L2
233 868 63636 13 0.00% 0.00% 0.00% 0 Cluster RARP
234 842 79680 10 0.00% 0.00% 0.00% 0 Cluster Base
235 1079110 3254846 331 0.00% 0.30% 0.26% 0 DHCPD Receive
236 0 2 0 0.00% 0.00% 0.00% 0 Dot1x Supplicant
237 0 2 0 0.00% 0.00% 0.00% 0 Dot1x Supplicant
238 0 2 0 0.00% 0.00% 0.00% 0 Dot1x Supplicant
239 0 1 0 0.00% 0.00% 0.00% 0 RARP Input
240 0 1 0 0.00% 0.00% 0.00% 0 HRPC dhcp snoopi
241 0 4 0 0.00% 0.00% 0.00% 0 HULC DHCP Snoopi
242 122707 672981 182 0.00% 0.00% 0.00% 0 Inline Power
243 110042 1399980 78 0.00% 0.01% 0.00% 0 Marvell wk-a Pow
244 3495 31821 109 0.00% 0.00% 0.00% 0 HULC stack power
245 0 1 0 0.00% 0.00% 0.00% 0 HRPC stack power
246 14622 91507 159 0.00% 0.00% 0.00% 0 IGMPSN L2MCM
247 305738 1682112 181 0.00% 0.04% 0.05% 0 IGMPSN MRD
248 199088 873476 227 0.00% 0.00% 0.04% 0 IGMPSN
249 0 1 0 0.00% 0.00% 0.00% 0 IGMPQR
250 0 3 0 0.00% 0.00% 0.00% 0 L2TRACE SERVER
251 11844 91506 129 0.00% 0.00% 0.00% 0 MLDSN L2MCM
252 0 1 0 0.00% 0.00% 0.00% 0 MRD
253 0 1 0 0.00% 0.00% 0.00% 0 MLD_SNOOP
254 0 1 0 0.00% 0.00% 0.00% 0 HRPC hl2mcm igmp
255 0 1 0 0.00% 0.00% 0.00% 0 HRPC hl2mcm mlds
256 57 274 208 0.00% 0.00% 0.00% 0 LOCAL AAA
257 0 1 0 0.00% 0.00% 0.00% 0 EPM MAIN PROCESS
258 17 17 1000 0.00% 0.00% 0.00% 0 SpanTree Flush
259 287 359 799 0.00% 0.00% 0.00% 0 TPLUS
260 244 4 61000 0.00% 0.00% 0.00% 0 OBFL MSG obfl0
261 8 12 666 0.00% 0.00% 0.00% 0 crypto engine pr
262 34 4 8500 0.00% 0.00% 0.00% 0 Crypto CA
263 0 1 0 0.00% 0.00% 0.00% 0 Crypto PKI-CRL
264 0 1 0 0.00% 0.00% 0.00% 0 Crypto SSL
265 0 1 0 0.00% 0.00% 0.00% 0 encrypt proc
266 0 1 0 0.00% 0.00% 0.00% 0 HRPC x_setup req
267 0 1 0 0.00% 0.00% 0.00% 0 Licensing MIB pr
268 17 27 629 0.00% 0.00% 0.00% 0 VTP Trap Process
269 0 8 0 0.00% 0.00% 0.00% 0 AAA SEND STOP EV
270 0 2 0 0.00% 0.00% 0.00% 0 DHCP Security He
271 93 10 9300 0.00% 0.00% 0.00% 0 Syslog Traps
272 0 2 0 0.00% 0.00% 0.00% 0 VTPMIB EDIT BUFF
273 0 1 0 0.00% 0.00% 0.00% 0 HCD Process
274 0 1 0 0.00% 0.00% 0.00% 0 HRPC cable diagn
275 0 2 0 0.00% 0.00% 0.00% 0 DiagCard1/-1
276 11093 779528 14 0.00% 0.00% 0.00% 0 PM Callback
277 17 5 3400 0.00% 0.00% 0.00% 0 VLAN Manager
278 0 1 0 0.00% 0.00% 0.00% 0 Connection Mgr
279 316 50985 6 0.00% 0.00% 0.00% 0 dhcp snooping sw
280 67 10 6700 0.00% 0.00% 0.00% 0 OBFL ENV obfl0
281 0 9 0 0.00% 0.00% 0.00% 0 EEM Server
282 0 2 0 0.00% 0.00% 0.00% 0 EEM Policy Direc
283 319372 10624 30061 0.00% 0.02% 0.00% 0 OBFL VOLT obfl0
284 9 45 200 0.00% 0.00% 0.00% 0 Syslog
285 0 2 0 0.00% 0.00% 0.00% 0 STP FAST TRANSIT
286 0 2 0 0.00% 0.00% 0.00% 0 CSRT RAPID TRANS
287 318165 17874 17800 0.00% 0.06% 0.17% 0 crypto sw pk pro
288 77 357 215 0.00% 0.00% 0.00% 0 SSH Event handle
289 0 10 0 0.00% 0.00% 0.00% 0 SNMP Timers
290 1295245 1934929 669 0.00% 0.15% 0.20% 0 IP SNMP
291 850263 921907 922 0.00% 0.15% 0.13% 0 PDU DISPATCHER
292 16602808 960396 17287 0.00% 2.29% 2.66% 0 SNMP ENGINE
293 0 2 0 0.00% 0.00% 0.00% 0 IP SNMPV6
294 0 1 0 0.00% 0.00% 0.00% 0 SNMP ConfCopyPro
295 496 58 8551 0.00% 0.00% 0.00% 0 SNMP Traps
296 15610 728481 21 0.00% 0.00% 0.00% 0 NTP
297 0 2 0 0.00% 0.00% 0.00% 0 hulc cfg mgr mas
298 5093 24 212208 0.00% 0.14% 0.33% 0 hulc running con
299 0 1 0 0.00% 0.00% 0.00% 0 LICENSE AGENT
300 1433 2144 668 0.00% 0.00% 0.00% 0 OBFL POE obfl0
301 1655 42399 39 0.00% 0.00% 0.00% 0 OBFL I/O Buffer