12-27-2010 12:40 PM - edited 07-03-2021 07:35 PM
We are noticing that we are getting alarms and time stats showing several AP's disconnect and reconnect within a minute. Is this normal behavior? I also ran a report for device Up Time and there are several that have an uptime less than a day. We have 4 - 4404 controllers, software version 4.2.176.0, approx. 250 LAP1131AG-A-K9 AP's, WCS version 6.0.181.0 . Thanks for any assistance.
01-11-2011 01:49 PM
1131 H-REAP AP will not join WLC due to Duplicate (replayed) record |
Symptom:1131 AP in H-REAP mode will not join a controller upgraded to 5.2. Conditions:H-REAP mode AP, Controller version 5.2.157.0 Workaround:Put the AP into local mode Further Problem Description:When the H-REAP mode AP tries to join a controller running 5.2 and initiate the DTLS, it increments a sequence number within the message. The AP gets to sequence number 13 and then puts out the following syslog message Message: 28: AP:0018.18fd.0248: *Feb 19 00:15:36.418: %DTLS-3-BAD_RECORD: Erroneous record received from X.Y.Z.A: Duplicate (replayed) record Every DTLS packet from the controller after that message generates the above message Typical messages that follow this one are: *Feb 11 00:15:47.078: %CAPWAP-3-ERRORLOG: Invalid event 12 & state 8 combination. *Feb 11 00:16:17.166: %CAPWAP-3-ERRORLOG: Ignoring message from different vendor. *Feb 11 00:16:17.166: %CAPWAP-3-ERRORLOG: Invalid msg element type 0 in Configuration Status Response. *Feb 11 00:16:17.166: %CAPWAP-3-ERRORLOG: Failed to decode Configuration Status Response from X.Y.Z.A |
I think this is more HREAP specific ,,,
01-12-2011 12:24 AM
i confirm, we are using Hreap.
I upgraded WLC to 7.0.98 last week-end. It's running. I'm waiting few weeks to confirm it solves the problem.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide