cancel
Showing results for 
Search instead for 
Did you mean: 

X440 90+% CPU usage

X440 90+% CPU usage

davidj_cogliane
Contributor
We have multiple closets at a EDU customer's High School many of which are seeing 90+% CPU spikes on a regular basis. I have read the articles about 8-20% CPU usage and the cli related CPU levels of 30+%.

The customer is experiencing random network issues this for the second day in a row and it is hard to argue against the CPU usage being related. Yes, I understand switching should not be affected by CPU usage.

These are stacks of 3-6 X440-G2-48p.
They are running summitX-22.5.1.7-patch1-7
ELRP is configured
configure elrp-client periodic vlan NOLOOP ports all disable-port duration 600
configure elrp-client disable-port exclude ports 1:52
NOLOOP is on every port on every stack.
13 REPLIES 13

davidj_cogliane
Contributor
So that reveals guest wireless clients moving between local ports and the uplink port.

09/05/2019 09:46:18.57 MAC E0:89:7E:CE:40:64 on VLAN 913 moved from port 4:30 to port 1:52
09/05/2019 09:46:15.79 MAC 38:53:9C:A7:72:C3 on VLAN 913 moved from port 4:14 to port 4:22
09/05/2019 09:46:14.70 MAC E0:33:8E:BF:B5:F6 on VLAN 913 moved from port 4:30 to port 1:52
09/05/2019 09:46:14.62 MAC 38:53:9C:A7:72:C3 on VLAN 913 moved from port 4:24 to port 4:14
09/05/2019 09:46:10.99 MAC 38:53:9C:A7:72:C3 on VLAN 913 moved from port 1:52 to port 4:24
09/05/2019 09:46:07.58 MAC FC:18:3C:83:7F:95 on VLAN 913 moved from port 4:30 to port 1:52
09/05/2019 09:46:07.10 MAC FC:18:3C:76:ED:2C on VLAN 913 moved from port 4:28 to port 1:52
09/05/2019 09:46:05.40 MAC 38:53:9C:A7:72:C3 on VLAN 913 moved from port 4:12 to port 1:52
09/05/2019 09:46:02.82 MAC 38:53:9C:A7:72:C3 on VLAN 913 moved from port 4:30 to port 4:12
09/05/2019 09:45:36.17 MAC 70:3C:69:07:B1:4D on VLAN 913 moved from port 4:28 to port 4:30

great command by the way.

BradP
Extreme Employee
If you use the following commands, do you see macs moving back and forth?
enable log debug-mode
configure log filter defaultfilter add event fdb.macmove

We can also try "run script spath-stats.py" and see if anything jumps out there.

davidj_cogliane
Contributor
Sorry meant to paste from the log
Hal

09/05/2019 09:21:59.80 CPU utilization monitor: process hal consumes 92 % CPU
09/05/2019 09:21:54.81 CPU utilization monitor: process hal consumes 93 % CPU
09/05/2019 09:13:33.16 The maximum number of neighbors supported on port 4:35 was exceeded.
09/05/2019 09:07:19.83 CPU utilization monitor: process hal consumes 91 % CPU
09/05/2019 08:51:54.79 CPU utilization monitor: process hal consumes 92 % CPU
09/05/2019 08:36:54.79 CPU utilization monitor: process hal consumes 93 % CPU
09/05/2019 08:21:54.81 CPU utilization monitor: process hal consumes 92 % CPU
09/05/2019 08:06:59.82 CPU utilization monitor: process hal consumes 94 % CPU
09/05/2019 08:06:54.83 CPU utilization monitor: process hal consumes 91 % CPU
09/05/2019 08:00:57.26 The maximum number of neighbors supported on port 5:40 was exceeded.
09/05/2019 08:00:05.80 The maximum number of neighbors supported on port 4:35 was exceeded.
09/05/2019 07:51:59.83 CPU utilization monitor: process hal consumes 92 % CPU
09/05/2019 07:51:54.82 CPU utilization monitor: process hal consumes 91 % CPU
09/05/2019 07:45:04.26 The maximum number of neighbors supported on port 5:40 was exceeded.
09/05/2019 07:44:15.56 The maximum number of neighbors supported on port 4:35 was exceeded.
09/05/2019 07:21:59.79 CPU utilization monitor: process hal consumes 93 % CPU
09/05/2019 05:52:43.34 Setting hwclock time to system time, and broadcasting time
09/05/2019 01:21:27.34 Setting hwclock time to system time, and broadcasting time
09/04/2019 22:51:59.65 CPU utilization monitor: process hal consumes 91 % CPU
09/04/2019 21:06:59.62 CPU utilization monitor: process hal consumes 94 % CPU
09/04/2019 20:51:59.65 CPU utilization monitor: process hal consumes 94 % CPU
09/04/2019 20:50:11.40 Setting hwclock time to system time, and broadcasting time
09/04/2019 20:36:59.52 CPU utilization monitor: process hal consumes 95 % CPU
09/04/2019 20:21:59.54 CPU utilization monitor: process hal consumes 96 % CPU
09/04/2019 20:06:59.53 CPU utilization monitor: process hal consumes 95 % CPU
09/04/2019 19:51:59.54 CPU utilization monitor: process hal consumes 94 % CPU

BradP
Extreme Employee
Hi David

What process is spiking?

Thanks
Brad
GTM-P2G8KFN