Upon checking the logs, I'm seeing a lot of these messages;
*emWeb: Oct 25 14:11:01.345: #LOG-3-Q_IND: spam_lrad.c:10136 Validation of STAT_PAYLOAD failed - AP 00:3a:98:09:4e:d0
Always the same MAC address, which I assume is a Cisco AP trying to join.
Anyone know what this means? The output interpreter/message decoder isn't much help.
5508 Controller running ver 188.8.131.52.
*spamApTask6: Oct 25 14:19:58.547: #LWAPP-3-VALIDATE_ERR: spam_lrad.c:10136 Validation of STAT_PAYLOAD failed - AP 00:3a:98:09:4e:d0
*Dot1x_NW_MsgTask_0: Oct 25 14:17:01.149: #LOG-3-Q_IND: spam_lrad.c:10136 Validation of STAT_PAYLOAD failed - AP 00:3a:98:09:4e:d0
All refer to the same MAC above.
Also I noticed in the traps that the RADIUS server is flipping to the backup every few minutes after the 'live' one doesn't respond in a timely manner....
|Thu Oct 25 14:29:55 2012||RADIUS server 10.2.100.50:1646 activated on WLAN 2|
|33||Thu Oct 25 14:29:55 2012||RADIUS server 10.15.5.100:1646 deactivated on WLAN 2|
|34||Thu Oct 25 14:29:55 2012||RADIUS server 10.15.5.100:1646 failed to respond to request (ID 195) for client 00:21:6a:4c:6a:e0 / user 'KIE\NDaly'|
|35||Thu Oct 25 14:29:47 2012||RADIUS server 10.15.5.100:1646 activated on WLAN 2|
|36||Thu Oct 25 14:29:47 2012||RADIUS server 10.2.100.50:1646 deactivated on WLAN 2|
|37||Thu Oct 25 14:29:47 2012||RADIUS server 10.2.100.50:1646 failed to respond to request (ID 58) for client 00:21:6a:4c:6a:e0 / user 'KIE\NDaly'|
Checking for network issues between the WLC and ACS now....
I am seeing the same issue on with the same version of code. We have a 7500 running 184.108.40.206. We have been putting Office Extend APs on it (the 602i model). Today, we moved over an 1131AG that was working fine on 220.127.116.11 in HREAP Office Extend mode, but after moving over it has a yellow status LED. The user says he can see the SSID, but cannot connect (makes me think a potential data channel issue). The AP shows REG for the controller status, while all other OEAPs show UP. And in the log, I see the same error along with a few others:
*spamApTask4: Nov 20 08:03:45.288: #LWAPP-3-VALIDATE_ERR: spam_lrad.c:10136 Validation of STAT_PAYLOAD failed - AP 00:xx:xx:xx:xx:xx (x'd out for security)
*spamApTask4: Nov 20 08:00:48.896: #LWAPP-3-HREAP_ERR3: spam_lrad.c:47864
00:xx:xx:xx:xx:xx (x'd out for security)Vlan ACL mapping Support is not supported on OfficeExtend AP.
*spamApTask4: Nov 20 08:00:42.619: #CAPWAP-3-SEM_RELEASE_ERR: capwap_ac_db.c:106 The system could not release exclusive access of AP entry for 00:xx:xx:xx:xx:xx (x'd out for security)
I did confirm the Data channel is not operational via "show dtls connections". Only the control channel is up. Going to move it back to the 18.104.22.168 controller.
Just a follow up, the HREAP Office Extend mode WAP did eventually start working on the 7500 running 22.214.171.124. I'm thinking that may have been a user issue because I didn't change anything and it just started working.
Anyway, that first error message persists and indeed fills up the logs.
I am also getting this with a customer 5508 controller running 7.3 code. this error is happening with a bunch of access points. The network is mostly 1242 and 3502i access points. I am currently trying to see if the problem is related to a specific model or mode. Does anyone know if this is a bug or a specific issue.
The customer said that all of their clients are still working and they have not experienced any issues. It is just crushing their syslog server.
so my customer's site has mainly 1242 access points with a handful of 3502i and 1142 access points. the error is only occuring for the 1242 access point. the error is also accuring whether the access point is configured for local mode or flexconnect mode.
Does this have anything to do with accepting MIC in the ap policies configuration?
All clients are working appropriately but the error keeps reoccuring every 3-5 minutes.
any idea what the root cause of this problem is and how the problem can be resolved?
I have the same problem. 126.96.36.199 and AP 1242.
I had a case opened and Cisco says it is a non-impacting bug. Here was their response:
I was able to find what the error messages mean. It’s a stats payload structure definition mismatch between the legacy AP code(ap_m_v12t) and WLC. It does not seem to be service impacting or causing any client issues. There is a bug opened for this problem. The bug id is CSCub65591.
Having the same problem:
LOG-3-Q_IND: Validation of STAT_PAYLOAD failed - AP
LWAPP-3-VALIDATE_ERR: Validation of STAT_PAYLOAD failed - AP
We run a mix of 1131, 3502, 3602. The ones having the problems are the 1131s.
I'm getting this probem to,
*spamApTask0: May 03 17:59:59.762: #LOG-3-Q_IND: spam_lrad.c:10136 Validation of STAT_PAYLOAD failed - AP
If its not service impacting, I wouldn't worry about it as there was a bug ID for the older v12 AP's.
Sent from Cisco Technical Support iPhone App