01-19-2017 04:51 AM
Hi everyone, I have a CISCO 6503 switch and it has a high CPU utilization but the processes are below 2%, ¿what could be the problem here?.
ra-uda-greuna#show processes cpu sorted 5sec | e 0.00
CPU utilization for five seconds: 77%/71%; one minute: 80%; five minutes: 81%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
9 62649120 3116919 20099 2.39% 0.55% 0.45% 0 Check heaps
250 107071360 246764421 433 1.67% 1.19% 1.29% 0 IP Input
252 77593912 402993376 192 0.71% 0.53% 0.56% 0 ADJ resolve proc
12 62814604 108249358 580 0.55% 0.69% 0.72% 0 ARP Input
331 61124976 10409366 5872 0.31% 0.29% 0.29% 0 CEF: IPv4 proces
524 8181472 21291653 384 0.15% 0.06% 0.05% 0 PIM Process
352 8523460 3060537 2784 0.07% 0.06% 0.06% 0 HIDDEN VLAN Proc
200 32564 2734 11910 0.07% 0.05% 0.01% 1 Virtual Exec
ra-uda-greuna#show logging system last 10
SEQ: MM/DD/YY HH:MM:SS MOD/SUB: SEV, COMP, MESSAGE
==============================
1: 01/10/17 12:57:05 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): RP CPU is busy (87% util).
2: 01/10/17 12:55:20 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): netint_thr_active[1].
3: 01/10/17 12:53:34 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): RP CPU is busy (83% util). netint_thr_active[1].
4: 01/10/17 12:53:04 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): netint_thr_active[1].
5: 01/10/17 12:47:48 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): RP CPU is busy (92% util). netint_thr_active[1].
6: 01/10/17 12:47:03 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): RP CPU is busy (83% util). netint_thr_active[1].
7: 01/10/17 12:46:18 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): RP CPU is busy (82% util). netint_thr_active[1].
8: 01/10/17 12:44:02 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): netint_thr_active[1].
9: 01/10/17 12:42:47 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): netint_thr_active[1].
10: 01/10/17 12:42:17 1/-1: MAJ, GOLD,
test_sp_rp_inband_ping[1]: diag_hit_sp_sys_limit. SP-RP Ping Test skipped. Reason(s): RP CPU is busy (82% util). netint_thr_active[1].
Best regards from Chile.
01-19-2017 11:44 AM
This is being caused by interrupt processing. This means the CPU is having to process some traffic instead of the hardware for some reason.
Here is an article about it.
CPU utilization for five seconds: 77%/71%
02-12-2017 01:38 AM
Thank for the help [@p.dath]
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