AP170 100% CPU utilisation

  • 1
  • Question
  • Updated 4 years ago
  • Answered
  • (Edited)

Hello,

One of my access points AP170 is keeping 100% CPU utilisation. I reset it to default settings from HiveManager but problem still exists. Can you advice what to do with it please?


T001#sh cpu
CPU total utilization:                100.000%
CPU user utilization:                 10.679%
CPU system utilization:               18.446%


T001#sh mem
Total Memory:       125888 KB
Free Memory:         62328 KB
Used Memory:         63560 KB


Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes

Posted 4 years ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Before digging in to this further, is the access point in question running 6.1r6? Do other APs of the same model have exactly the same configuration? Is there anything unique or that stands out about the operating environment?
Photo of Gary Smith

Gary Smith, Official Rep

  • 299 Posts
  • 61 Reply Likes
Hi Marek,

Could you run the following command on the CLI and share the output;

"show system processes state"

This should give a better idea of what process is using the CPU.

Kind Regards,
Gary Smith
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes

It was working normally until Friday last week. AP170 has HiveOS 6.1r2.1359, HM is Enterprise   6.1r5 virtual appliance.

TESSKEWAH001#sh cpu detail
CPU total utilization:                100.000%
CPU user utilization:                 7.843%
CPU system utilization:               27.450%
Number of interrupt in last second:   1774
Interrupt utilization:                0.000%
Soft interrupt utilization:           64.705%
TESSKEWAH001#

TESSKEWAH001#show system processes state

Mem: 91424K used, 34464K free, 0K shrd, 17960K buff, 29884K cached
CPU: 14.4% usr 24.8% sys  0.0% nic  0.0% idle  0.0% io  0.0% irq 60.8% sirq
Load average: 3.99 3.50 2.66 6/213 14821
  PID  PPID USER     STAT   VSZ %MEM CPU %CPU COMMAND
  109   100 root     R    44956 35.6   0 71.2 /opt/ah/bin/l7d
  249   246 root     S    37084 29.4   0  4.8 /opt/ah/bin/ah_auth
   91     1 root     R    30164 23.9   0  4.8 /opt/ah/bin/amrp2
   38     1 root     S     9096  7.2   0  4.8 /opt/ah/bin/ah_syslogd
   39     1 root     S     2256  1.7   0  4.0 /opt/ah/bin/ah_klogd
14813 14378 root     R     3820  3.0   0  3.2 top
  297   254 root     S    25460 20.2   0  0.8 /opt/ah/bin/ah_vpn
  279   213 root     S    19724 15.6   0  0.8 /opt/ah/bin/ah_asd
  350   339 root     S    19412 15.4   0  0.8 /opt/ah/bin/ah_nbr
    4     1 root     SW<      0  0.0   0  0.8 [events/0]
  122   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  186   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  183   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  130   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  410   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  129   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  123   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  501   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  107     1 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  128   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  182   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  187   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  121   107 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  184   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  185   121 root     S    54576 43.3   0  0.0 /opt/ah/bin/ah_dcd
  108   100 root     S    44956 35.6   0  0.0 /opt/ah/bin/l7d
   87     1 root     S    44956 35.6   0  0.0 /opt/ah/bin/l7d
  144   100 root     S    44956 35.6   0  0.0 /opt/ah/bin/l7d
  100    87 root     S    44956 35.6   0  0.0 /opt/ah/bin/l7d
  375   366 root     R    40616 32.2   0  0.0 /opt/ah/bin/capwap
  393   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  367   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  372   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  394   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  370   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  373   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  371   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  368   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  369   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  374   366 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  338     1 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  366   338 root     S    40616 32.2   0  0.0 /opt/ah/bin/capwap
  286   246 root     S    37084 29.4   0  0.0 /opt/ah/bin/ah_auth
  248   246 root     S    37084 29.4   0  0.0 /opt/ah/bin/ah_auth
  287   246 root     S    37084 29.4   0  0.0 /opt/ah/bin/ah_auth
  284   246 root     S    37084 29.4   0  0.0 /opt/ah/bin/ah_auth
  225     1 root     S    37084 29.4   0  0.0 /opt/ah/bin/ah_auth
  285   246 root     S    37084 29.4   0  0.0 /opt/ah/bin/ah_auth
  250   246 root     S    37084 29.4   0  0.0 /opt/ah/bin/ah_auth
  246   225 root     S    37084 29.4   0  0.0 /opt/ah/bin/ah_auth
  396   387 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui
  391   387 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui
  349     1 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui
  388   387 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui
  392   387 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui
  509   387 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui
  389   387 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui
  390   387 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui
  395   387 root     S    35764 28.3   0  0.0 /opt/ah/bin/ah_webui

Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Can I suggest you update and try and reproduce the issue then with the latest version of HiveOS?

You should, incidentally, update to HiveManager and HiveOS 6.1r6 as it closes important security vulnerabilities as well as fixing other issues.
Photo of Gary Smith

Gary Smith, Official Rep

  • 299 Posts
  • 61 Reply Likes
Marek,

Nick makes a good suggestion of upgrading. Please try this and retest. Try to avoid upgrading while the CPU is very high as this may cause adverse affects.

From your output it appears that the l7d process is the top process. This is the process which relates to the application reporting.

Kind Regards,
Gary Smith
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Just a reminder that updating the L7 signatures is a separate process to updating HiveOS. If you can reproduce with everything in their latest versions, it seems to me that it would be worth pursuing further via a support case.
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes

I upgraded access point to HiveOS 6.1r3b.1502. That fixed the problem. CPU utilisation is now 17%.

Thank you for you help.

Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
You should definitely strongly consider moving to 6.1r6 now that it is available. Curious what made you decide on 6.1r3b? Not having to upgrade HiveManager?
(Edited)
Photo of Marek Szymonski

Marek Szymonski

  • 44 Posts
  • 4 Reply Likes
I don't want to upgrade HiveManager today because I don't know what other issues it can cause. 6.1r3b was the latest OS version I had.
Photo of Travis Kaufman

Travis Kaufman, Champ

  • 113 Posts
  • 30 Reply Likes
I went to 5.1r5 actually, it helped the CPU dramatically