ProCurve / ProVision-Based
cancel
Showing results for 
Search instead for 
Did you mean: 

Aruba 3810m 100% CPU utilization

Marcel-Dupont
Occasional Visitor

Aruba 3810m 100% CPU utilization

Hi,

We recently bought an Aruba 3810m-48g and noticed that CPU gets up to 100% during 5 seconds every 30mn, caused by a process named IPSEC.
I also noticed that HTTP process is using CPU resources while web-management is disabled.
 
 % CPU | Description
-------+--------------------------
   3.2 | Idle
   1.6 | HTTP
  95.2 | IPsec
 
Can you help me solving this issue?
Here are infos about software versions : 
 
  Software revision  : KB.16.01.0004        Base MAC Addr      : 70106f-880f80
  ROM Version        : KB.16.01.0005        Serial Number      : SG63GYV3SN
 
Thanks.
3 REPLIES
parnassus
Honored Contributor

Re: Aruba 3810m 100% CPU utilization

The KB.16.01.0004 was the very first software version released for KB.16.01 software branch in January 2016: I suggest you to update at latest software version available (or, at least, run a software version not older than KB.16.01.0008) for KB.16.01 or, even better, move on newer software branches like KB.16.02 or KB.16.03 (KB.16.04 branch release seems just around the corner if not already available).

That's to say that a lot of fixes (and enhancements) were released along with many software updates happened during latest 18 months.

As example, consider that old KB.16.01.0007 fixed this:

CR_0000190925 Symptom/Scenario: A 100% CPU usage spike occurs every 10 minutes, caused by the HTTP task calling the Entropy function.
Marcel-Dupont
Occasional Visitor

Re: Aruba 3810m 100% CPU utilization

Hi,

As the switch is our network backbone, we'll schedule this update in the next coming weeks.

Thanks for your detailed answer !

parnassus
Honored Contributor

Re: Aruba 3810m 100% CPU utilization

Aruba 3810 resources on HPE Support portal provide KB.16.01, KB.16.02 and KB.16.03 with those latest software versions:

  • KB.16.01.0012 (February 2017)
  • KB.16.02.0020 (July 2017)
  • KB.16.03.0005 (July 2017)

References here.

Always refer to related Release Notes.