EWC - V9.21.15 - AP3620 reboots unexpected (if users generate too much traffic )

  • 0
  • 2
  • Question
  • Updated 2 years ago
  • Answered
My customer complains that a AP3620 reboot only based on the user load. Is this possible ??

I use EWC V9.21.15.

ap.log tell me that the regarding AP has bootet - but which trace file or log message tell me the reason for the last boot ?

Please help.

Regards
Photo of M.Nees

M.Nees, Embassador

  • 9,620 Points 5k badge 2x thumb

Posted 2 years ago

  • 0
  • 2
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 50,114 Points 50k badge 2x thumb
I'd upgrade to v10, there are no known bugs in v10 for AP26xx and AP36xx.
Photo of M.Nees

M.Nees, Embassador

  • 9,620 Points 5k badge 2x thumb
Good joke ....
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 50,114 Points 50k badge 2x thumb
Go to GUI > Logs > AP > Traces
Select the AP and click on retrieve traces.

If the controller is in a good mood that should download the AP trace file.
Open the .tar file and you'll find ap.logLastReboot.gz and one or more files with the name ap-report.txt*.gz.

Might be that you'd find the cause in this files or you'd need to open a ticket so the GTAC could take a look in the incl. dump.

BTW, does the > Logs > AP > Logs > Severity:All .... doesn't show the reboot cause ?
Photo of M.Nees

M.Nees, Embassador

  • 9,620 Points 5k badge 2x thumb
You are right getting Trace Files from AP is not very reliable... i need 3 tries ...

unfortunately ap.logLastReboot.gz is corrupted but ap-report.txt tell me something:
Jan  1 00:00:52 kernel: kTrapMonitor: process cap is missing (fatal) -- reboot in [5+ sec]

As you see below is decide opening a case.

Regards,
Matthias
Photo of Gareth Mitchell

Gareth Mitchell, Extreme Escalation Support Engineer

  • 5,690 Points 5k badge 2x thumb
Hi Matthias

I would recommend you open a case to have the logs looked at.

-Gareth
Photo of M.Nees

M.Nees, Embassador

  • 9,620 Points 5k badge 2x thumb
Case opened 01281431

Jan  1 00:00:52 kernel: kTrapMonitor: process cap is missing (fatal) -- reboot in [5+ sec]
Photo of M.Nees

M.Nees, Embassador

  • 9,620 Points 5k badge 2x thumb
The problem is solved!

With the help of the excellent GTAC (thanks to Gareth) - we can find the root cause and solve the problem.

The Switchport was (historical) set to 100MBit and not to 1000MBit. Changing that solved the problem.


Regards,
Matthias
Photo of Gareth Mitchell

Gareth Mitchell, Extreme Escalation Support Engineer

  • 5,690 Points 5k badge 2x thumb