EWC - V9.21.15 - AP3620 reboots unexpected (if users generate too much traffic )
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-31-2017 08:05 PM
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
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
8 REPLIES 8
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2017 07:29 AM
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
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2017 07:29 AM
Thanks Matthias, to close the loop I wrote this article: https://gtacknowledge.extremenetworks.com/articles/Solution/AP3620-looses-connectivity-to-the-contro...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-01-2017 01:07 PM
Hi Matthias
I would recommend you open a case to have the logs looked at.
-Gareth
I would recommend you open a case to have the logs looked at.
-Gareth
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-01-2017 01:07 PM
Case opened 01281431
Jan 1 00:00:52 kernel: kTrapMonitor: process cap is missing (fatal) -- reboot in [5+ sec]
Jan 1 00:00:52 kernel: kTrapMonitor: process cap is missing (fatal) -- reboot in [5+ sec]
