Description

Customers may observe high Routing Engine (RE) CPU utilization where the eventd process consumes significant CPU resources (up to 100%). This can impact overall device performance and responsiveness.

Symptoms

Run the following command to check RE CPU utilization:
show chassis routing-engine | no-more
 
Routing Engine status:
Temperature                 35 degrees C / 95 degrees F
CPU temperature            66 degrees C / 150 degrees F
Total memory               4096 MB (32% used)
5 sec CPU utilization:
User                       18 percent
Background                 0 percent
Kernel                     82 percent
Interrupt                  0 percent
Idle                       0 percent  <<<<<<<<<<<
 

Check running processes:

 
show system processes extensive | no-more
 
PID    USERNAME PRI NICE  SIZE   RES   STATE  C   TIME    WCPU    COMMAND
2302   root     123 0     1950M  1229M CPUx   x   ???     93.21%   flowd_octeon_hm
1699   root     123 0     43384K 13240K RUN   0   4906.4  64.65%   eventd  <<<<<<<<<<<
 
  • eventd consuming high CPU (e.g., >60%)
  • High kernel utilization
  • RE CPU idle at or near 0%

Solution

Possible reasons:
Excessive SNMP polling or trap generation
High host inbound traffic triggering event processing
Increased logging or event handling load on the RE
 

1. Check SNMP Activity

  • Verify if there is excessive SNMP polling or traps:
    • Reduce SNMP polling frequency
    • Limit or filter unnecessary SNMP traps

2. Analyze Host Inbound Traffic

  • Check for abnormal or high-rate traffic destined to the RE
  • Apply rate-limiting or filtering policies if required
3. Capture Core for Analysis 
 
start shell user root
gcore -c <gcore-file-name> <pid>
 

Replace <pid> with the PID of the eventd process.

4. Restart eventd Process (Workaround) -  ( no user or traffic impact ) 

If CPU remains high:

> restart event-processing

 

If the issue persists after restarting eventd:

  • Collect var logs and core files
  • Contact JTAC for further investigation and root cause analysis

Modification History

2024-11-01 : Article Created