WLC snmptrap messages

Hi,
WLC 8500 send out two types log.
For system messages -> syslog
For client and access-point messages ->snmptrap.
We want to track these snmptrap messages. In WLC User interface trap messages are readable. "Client abc associated in wlan abcd."
But we cannot read messages on any snmptrap receivers application. All messages seems just oid and their values.
"1.3.6.7.25.34.98 = abcd."
How to merge these oids and their description to make more readeable.
Thanks for all.

It sounds like your SNMP trap receiver application doesn't have the SNMP MIB files required to map the OID to a description. You can download the MIBS for the WLCs from the Download section as described below. Once you have the file/s you will need to reference them within the trap receiver application, usually be putting them into a certain folder, it varies by application.
Products -> Wireless -> Wireless LAN Controller -> Standalone Controllers -> Cisco 5500 Series Wireless Catalyst -> Cisco 5508 Wireless Controller -> Management Information Base (MIB)
There is a similar discussion on this at the link below too-
https://supportforums.cisco.com/discussion/11268776/problem-wlc-and-snmp-ap-assocdisassoc-trap-and-3rd-party-nms
Pete.

Similar Messages

WLC and message logs

We have a WLC 4402 and there are a lot of messages in the log. How can I find out what the messages means ?
F.example :
Jul 20 07:07:25.076 apf_80211.c:1923 APF-1-PROC_RSN_WARP_IE_FAILED: Could not process the RSN and WARP IE's. station not using RSN (WPA2) on WLAN requiring RSN.MobileStation: 00:13:46:6e:c3:ff, SSID:HVO.
J F.

Its an authentication issue. Use 802.1x, WPA/PSK or LEAP with WPA/ TKIP

WLC Warning Message: Our AP is under attack

Hi there,
I receive this Warning message in WLC version 5.0:
Warning: Our AP with Base Radio MAC 00:1f:6d:b9:48:d0 is under attack (contained) by another AP on radio type 802.11b/g
So, what does it means? Can someone explain..Great Thanks.

I am getting the same message, but I've not been able to diagnose the issue yet.
It seems that the AP is being contained by another wireless system. However, there is no information that I can find to indicate what is "attacking" or "containing" the AP.

WLC syslog messages

Does anyone know where to find a overview for the controller's syslog messages ?
Regards
johann Folkestad

I think the WLC configuration guide has a chapter for error messages. This might have your necesary information.
http://www.cisco.com/en/US/products/ps6366/products_configuration_guide_chapter09186a008076ce82.html

WLC cert messages

We are having a few problems with one of our WiSM controllers.
The console is spammed with lots of fp_main_task: messages, an example is below
sshpmLoadSystemCerts: calling x509_alloc()*fp_main_task: Feb 01 11:36:49.862: sshpmLoadSystemCerts: calling x509_decode()*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: constructing 4 byte CID*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: storing CA cert bsnDefaultBuildCert in row 3*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: verifying MAGIC2*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: preparing to read in 2 certs from block 2*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: loading CA cert into row 4 from block 2 header 1*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: allocating 839-byte buffer for cscoDefaultNewRootCaCert*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: calling x509_alloc()*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: calling x509_decode()*fp_main_task: Feb 01 11:36:49.868: sshpmLoadSystemCerts: constructing 4 byte CID*fp_main_task: Feb 01 11:36:49.868: sshpmLoadSystemCerts: storing CA cert cscoDefaultNewRootCaCert in row 4*fp_main_task: Feb 01 11:36:49.868:
Has anyone got any experience of this and how it's resolved?
The controller is set up the same as 3 others in the same mobility group and this is the only one with any issue like this. I've checked and re-applied certificates.
It doesn't appear to be causing much of an issue, but there are limited numbers of APs connected to this controller.

We are having a few problems with one of our WiSM controllers.
The console is spammed with lots of fp_main_task: messages, an example is below
sshpmLoadSystemCerts: calling x509_alloc()*fp_main_task: Feb 01 11:36:49.862: sshpmLoadSystemCerts: calling x509_decode()*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: constructing 4 byte CID*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: storing CA cert bsnDefaultBuildCert in row 3*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: verifying MAGIC2*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: preparing to read in 2 certs from block 2*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: loading CA cert into row 4 from block 2 header 1*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: allocating 839-byte buffer for cscoDefaultNewRootCaCert*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: calling x509_alloc()*fp_main_task: Feb 01 11:36:49.866: sshpmLoadSystemCerts: calling x509_decode()*fp_main_task: Feb 01 11:36:49.868: sshpmLoadSystemCerts: constructing 4 byte CID*fp_main_task: Feb 01 11:36:49.868: sshpmLoadSystemCerts: storing CA cert cscoDefaultNewRootCaCert in row 4*fp_main_task: Feb 01 11:36:49.868:
Has anyone got any experience of this and how it's resolved?
The controller is set up the same as 3 others in the same mobility group and this is the only one with any issue like this. I've checked and re-applied certificates.
It doesn't appear to be causing much of an issue, but there are limited numbers of APs connected to this controller.

ISE 1.2 rejects RADIUS messages from 5508 WLC

The setup in ref is:
WLC 5508 HA pair running 7.6 talking to ISE 1.2 patch 7 (was 6).
Wireless users are authenticated fine, so the 5508 is a valid NAD in ISE, but...
When I setup active RADIUS fallback, so that the WLC can poll the ISE servers I get the message:
"The RADIUS request from a non-wireless device was dropped because the installed license is for wireless devices only"
Why would ISE drop a RADIUS message from a WLC which is a wireless device? Surely this is a mistake?

Hi Nicholas,
This is a known defect.
CSCug34679 ISE drop keep alive coming from WLC.
Symptom:
ISE drops keep alive authentications coming from the WLC, with message 11054 Request from a non-wireless device due to installed wireless license.
Conditions:
When only a wireless license is install on the ISE and using active keep alive on the WLC.
Workaround:
Use passive keep alive on the WLC and not active.
Regards,
Jatin Katyal
*Do rate helpful posts*

Guest WLAN Spalsh page to external URL

Hi, I want to setup a webpage for my guest network (no authentication) users. When the client connects to the open guest network and upon opening a browser they would be directed to a survey that I would like them to take, if they don't want to take it they can begin browsing to other sites without issue. How do I do this on a my 5508 WLC?

You mean in the WLAN config? If so, that didn't work either.
To recap where I am at now I have my WLAN setup with just passthrough.
Then under security Web auth > web login page I have it set as
Unfortunatlly, I still cannot leave the External Webauth URL empty
With the above setup, the client after connecting to the WLAN has the browser auto launch and appears to direct to the redirect site, however the page just refreshes and does not load. Long URL with domain.com/blah blah blah/1.1.1.1 virtual interface of the WLC.
Message was edited by: Andrew Schulz

Interesting things to monitor via syslog/snmp etc on 5508?

Hi all,
We don't use Cisco prime for network monitoring. I'm interesting and monitoring and alerting on any potential wireless performance or security issues.
Has anyone got any suggestions for interesting things to monitor on a 5508 WLC? We have a range of AP's some of them CleanAir and some older.
We can monitor or alert on specific syslog messages, snmp traps, or snmp gets.
Has anyone got any favorite things the like to monitor?

This is a tough one, specially if you do not have cisco wireless management system (like WCS or Prime)
Here is WLC system message guide, you may need to go through it & find what to look at depend on your interest (there are so many)
http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-6/message/guide/sysmsg76.html
HTH
Rasika
**** Pls rate all useful responses. Each time you rate a response Cisco will donate $1 to Kiva ****

AP 1242-AG

By mistake I deleted boot file and now access point only boots up in ap mode.
When I run Dir I get nothing.
How can I restore the image back?
I have tried Hyper terminal xmodem but it failed.
I tried to assign IP address but it does not recognise the command but dir.
ap:
ap:
I need help and my access point.
Sent from Cisco Technical Support iPad App

Hi mohammed,
You just connect the AP to your Infrastructure(edge swicth or...). AP will detect the config and image automatically from WLC.
FYI:
The LAPs are "zero touch" deployed, and no individual configuration of LAPs is required.
In order for the WLC to be able to manage the LAP, the LAP should discover the controller and register with the WLC. After the LAP has registered to the WLC, LWAPP messages are exchanged and the AP initiates a firmware download from the WLC (if there is a version mismatch between the AP and WLC). If the AP's onboard firmware is not the same as the WLC's, the AP will download firmware to stay in sync with the WLC. The firmware download mechanism utilizes LWAPP. Then, the WLC provisions the LAP with the configurations that are specific to the WLANs so that the LAP can accept client associations. These WLAN-specific configurations include:
    Service set identifier (SSID)
    Security parameters
    IEEE 802.11 parameters, such as:
        Data rate
        Radio channels
        Power levels
Regards

ISE 1.2 - WLC 5508 - NAS sends RADIUS accounting update messages too frequently

I'm getting this error in ISE referring to my Cisco 5508 WLC. I'm not sure how to turn down the frequency. Any ideas?
NAS sends RADIUS accounting update messages too frequently
Verify NAS configuration. Verify known NAS issues.

I opened up a TAC case with Cisco yesterday and this is the response i got from them:
There is bug on the WLC side to reduce the number acct updates:
CSCug14713- WLC sends acct-update twice in the same millisecond
This is fixed in 8.x on the WLC.
So, it looks at though we just have to deal with it until they release an 8.x version for the WLC. In the meantime, you can disable the alerts in ISE.
Administration>Settings>Alarm Settings>Misconfigured Network Device Detected
Edit that alarm and set it to disabled

Updated WLCs shows wierd log messages and most APs do not associate

Hi, I recently updated my 4402 WLC to latest Software Version (7.0.98.0).
This first seamed to have worked fine. WLCs rebooted fine, then APs rebooted and upgraded their software images.
All fine as it seamed.
The I went on to also upgrade to latest Emergency Image Version(5.2.157.0).
After rebooting the WLCs most APs won't associate again.
Logs from WLCs shows a lot of messages like:
Oct 7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct 7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:38 wlc-1 WLC-1: -Traceback: 105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:38 wlc-1 WLC-1:
Oct 7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct 7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:38 wlc-1 WLC-1: -Traceback: 105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:38 wlc-1 WLC-1:
Oct 7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct 7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:39 wlc-1 WLC-1: -Traceback: 105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:39 wlc-1 WLC-1:
Oct 7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct 7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:39 wlc-1 WLC-1: -Traceback: 105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:39 wlc-1 WLC-1:
Oct 7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct 7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:40 wlc-1 WLC-1: -Traceback: 105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:40 wlc-1 WLC-1:
Oct 7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct 7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:40 wlc-1 WLC-1: -Traceback: 105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:40 wlc-1 WLC-1:
Oct 7 20:11:40 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:40.905: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
Oct 7 20:11:40 wlc-1 WLC-1: -Traceback: 105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:40 wlc-1 WLC-1:
Oct 7 20:11:43 wlc-1 WLC-1: *mmMobility: Oct 07 22:11:43.210: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:43 wlc-1 WLC-1: -Traceback: 105fbe18 102d8be0 102bc81c 102d5d20 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:43 wlc-1 WLC-1:
Oct 7 20:11:43 wlc-1 WLC-1: *mmListen: Oct 07 22:11:43.210: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
Oct 7 20:11:43 wlc-1 WLC-1: *mmListen: Oct 07 22:11:43.211: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:43 wlc-1 WLC-1: -Traceback: 105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:43 wlc-1 WLC-1:
Oct 7 20:11:50 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:50.913: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
Oct 7 20:11:50 wlc-1 WLC-1: -Traceback: 105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc
When looking back a bit in the logs it looks like this started after upgrading the Software version. But after this first reload it the APs came back and worked. Now they don't.
The case seams to be the same with both my WLCs.
What could have gone wrong?
Please advice.

Not sure which messages are concerning you the most...
Regarding the message:
Oct 7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
Oct 7 20:11:39 wlc-1 WLC-1: -Traceback: 105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
Oct 7 20:11:39 wlc-1 WLC-1:
There is already a bug for it: CSCth64522
And for:
Oct 7 20:11:50 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:50.913: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
Oct 7 20:11:50 wlc-1 WLC-1: -Traceback: 105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc
Looks like it's matching CSCtf39550
Both bug fixes should be included in the next 7.0 release and should not impact the WLC behavior.
Hope this helps...

Unknown error message in WLC Config Analyzer

Hello,
does anybody know what means the following error message from WLC Config Analyzer?
30026,General: Network state not matching: WLC3-Ortona,on 11g. My state :True, its state :True. This may introduce join issues on APs
My WLC IOS version is 7.0.98.0
Thanks
Johnny

Hello,
does anybody know what means the following error message from WLC Config Analyzer?
30026,General: Network state not matching: WLC3-Ortona,on 11g. My state :True, its state :True. This may introduce join issues on APs
My WLC IOS version is 7.0.98.0
Thanks
Johnny

WLC sending a message of AP under attack

Hi to all,
I've been getting this message from my WLC and I'm not able to find what doest it really mean and if there is something that could be done in order to solve it.
"Warning : Our AP with Base Radio MAC 00:14:a8:53:0b:20 is under attack (contained) by another AP on radio type 802.11b/g"
"Warning Cleared: Our AP with Base Radio MAC 00:14:a8:53:0b:20 is no longer under attack (contained) by another AP on radio type 802.11b/g"
Can this cause me problems in the performance of my wireless network???
Thanks in advance for your help.

Hi,
The firmware is 4.2.112.0
Thanks in advance for your help.

Unterstanding syslog messages from our wlc

Hello,
we use two wlc 4402 (4.1.181.0) and several leightweight accesspoints (AIR-AP1010-E-K9 and AIR-AP1030-E-K9 ) connected to them.
On our syslog server we get a lot of messages from the two wlc, and there are 3 message types which I am a little bit afraid of.
1. ca. 10 times per hour we get the message
apf_80211.c:4792 APF-6-NO_CONFIG_CHANGES: Not saving 'apf.cfg' - no config changes."
Cisco system message guide:
Error Message %APF-6-NO_CONFIG_CHANGES: Not saving '[chars]' - no config changes.
Explanation Not saving - no config changes.
Recommended Action No action is required.
Does anybody know why we get this messages and if it's possibly to suppress them?
2. Intermittently (several times a day) we get the following message types:
a) [ERROR] spam_l2.c 723: Max retransmissions reached on AP 00:0B:85:56:63:40 (CONFIGURE_COMMAND^M , 2)"
b) [ERROR] spam_tmr.c 569: Did not receive hearbeat reply from AP 00:0b:85:56:ae:40"
The MAC address is not every time the same but one of our accesspoints.
On our network management system we get the following trap messages with nearly exactly the same timestamp:
14.01.2008 04:21:56 CET
AP ''00.0b.85.56.63.40'', interface ''0x1'' is down.
When Airespace AP's interface operation status goes down this trap will be sent.
bsnAPDot3MacAddress = 00.0b.85.56.63.40
bsnAPIfSlotId = 0x1
14.01.2008 04:21:56 CET
AP disassociated from Switch.
When an Airespace AP disassociates from a Airespace Switch, the AP disassociated notification will be sent with the dot3 MAC address of the Airespace AP. This will notify the management system to remove Airespace AP from this Airespace Switch.
bsnAPMacAddrTrapVariable =
14.01.2008 04:22:25 CET
AP associated with Switch.
When an Airespace AP Associates to a Airespace Switch, the AP associated notification will be sent with the dot3 MAC address of the Airespace AP. This will help the management system to discover the Airespace AP and add it to system.
bsnAPMacAddrTrapVariable =
bsnAPPortNumberTrapVariable = 1
Cisco system message guide:
a) Error Message %LWAPP-3-TX_ERR3: Max retransmissions for LWAPP control message reached on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] for [chars] (number of pending messages is [dec])
Explanation Maximum number of times an LWAPP control packet is transmitted before declaring the AP dead has been reached for this AP. The AP may not be on the network, or might have rebooted.
Recommended Action Check if the AP has rebooted or if it has been removed from the network, or if there are connectivity issues between the AP and the controller.
b) Error Message %LWAPP-3-ECHO_ERR: Did not receive heartbeat reply; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]
Explanation Controller did not get a response for the AP heartbeat message. There may be connectivity issues between the AP and the controller.
Recommended Action Check if the AP has rebooted or if it has been removed from the network, or if there are connectivity issues between the AP and the controller.
Because we don't see any network problems I'm wondering why the connection is lost.
Does anybody have an idea, perhaps CSCsh13928 (http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsh13928, but we don't have much traffic on the wlans) ?
Is there any possibility to remotely check if the accesspoint rebooted?
If you need further information please give me a short feedback.
Many thanks in advance,
Thorsten Steffen

Thanks for the help.
I have set up to send email and syslog messages from the RME applications. LMS server immediately started to send messages to the email server but syslog messages are not forwarded to the syslog server. Everything was done according to your instructions except that the name of the first script (syslog_forward.pl) is made consistent with what the second script (.bat) refer to (forward1.pl). What's the problem? Do RME sends the standard syslog messages via UDP port 514?
Sincerely.

WLC 5508 - LAP1242: Failed to handle capwap control message from controller

Hello everyone,
after finally successfully upgrading my WLCs from 6.0.199.4 to 7.6.100.0 there is another problem showing up...
If I want to change any configuration regarding the APs on the WLCs (which doesn't work) I get the following error-messages from the APs:
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.169: %CAPWAP-3-ERRORLOG: Validate Msg: msg type 12 does not supported payload 215
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.169: %CAPWAP-3-ERRORLOG: Validate Msg: error in Unknown Payload(215) payload (received length = 9, payload type = 215)
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.170: %CAPWAP-3-ERRORLOG: Failed to validate vendor specific message element type 215 len 9.
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.170: %CAPWAP-3-ERRORLOG: Failed to decode Configuration update request.
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.170: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 7 state 11.
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.171: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
Find attached some informations regarding the AP and the 5508.
Any suggestions are, as always, highly appriciated.
Regards
Manuel

Good morning,
if I need free space at the flash: How much is "enough" to handle config changes?
Here you can see the filesystem of one of my accesspoints (all are affected):
AP#dir all-filesystems
Directory of arch:/
    2 -rwx       91288 Feb 22 2014 18:16:42 +00:00 event.log
    8 drwx         448 Feb 22 2014 18:16:38 +00:00 c1240-k9w8-mx.124-25e.JAO3
    4 drwx           0   Nov 2 2011 23:32:18 +00:00 configs
    5 -rwx         397 Feb 22 2014 18:19:03 +00:00 env_vars
    6 -rwx        6168 Feb 27 2014 18:14:24 +00:00 private-multiple-fs
No space information available
Directory of flash:/
    2 -rwx       91288 Feb 22 2014 18:16:42 +00:00 event.log
    8 drwx         448 Feb 22 2014 18:16:38 +00:00 c1240-k9w8-mx.124-25e.JAO3
    4 drwx           0   Nov 2 2011 23:32:18 +00:00 configs
    5 -rwx         397 Feb 22 2014 18:19:03 +00:00 env_vars
    6 -rwx        6168 Feb 27 2014 18:14:24 +00:00 private-multiple-fs
15740928 bytes total (10614784 bytes free)
Directory of zflash:/
    2 -rwx       91288 Feb 22 2014 18:16:42 +00:00 event.log
    8 drwx         448 Feb 22 2014 18:16:38 +00:00 c1240-k9w8-mx.124-25e.JAO3
    4 drwx           0   Nov 2 2011 23:32:18 +00:00 configs
    5 -rwx         397 Feb 22 2014 18:19:03 +00:00 env_vars
    6 -rwx        6168 Feb 27 2014 18:14:24 +00:00 private-multiple-fs
15740928 bytes total (10614784 bytes free)
Directory of archive:/
No files in directory
No space information available
Directory of system:/
    2 dr-x           0                    memory
    1 -rw-       17631                    running-config
No space information available
Directory of nvram:/
   30 -rw-           0                    startup-config
   31 ----           0                    private-config
    1 ----        4100                    lwapp_ap.cfg
    6 ----         528                    lwapp_ap_tlv.cfg
32768 bytes total (26572 bytes free)
Regards, Manuel

WLC snmptrap messages

Similar Messages

Maybe you are looking for