Cisco Wireless LAN Controller System Message Guide, Release 8.0

LRADSIM Messages
LWAPP Messages

LRADSIM and LWAPP System Messages

This chapter contains the following topics:

LRADSIM Messages

This section contains LWAPP Radio Access Device Simulator (LRADSIM) messages.

Error Message %LRADSIM-3-AUTHREQFAIL: Unable to send authenticate message.

Explanation The system has failed to encapsulate the header in the authentication message.

Recommended Action This is a debug message only. No action is required.

Error Message %LRADSIM-3-INTMACFAIL: Unable to retrieve the interface MAC address.

Explanation The system is trying to retrieve the MAC address of an unplugged interface or the interface index exceeds the maximum supported interface.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %LRADSIM-3-INVDADDR: Invalid destination address provided.

Explanation The system is trying to use an invalid IP address.

Recommended Action This is a debug message only. No action is required.

Error Message %LRADSIM-3-INVMS: Invalid mobile identifier provided.

Explanation The system is trying to use an invalid AP for a mobile station.

Recommended Action This is a debug message only. No action is required.

Error Message %LRADSIM-3-INVPARAM: Invalid parameters provided to sendDiscoveryRequest.

Explanation A bad destination address or a invalid port number was specified as a parameter to the sendDiscoveryRequest.

Recommended Action This is a debug message only. No action is required.

Error Message %LRADSIM-3-INVRCB: Invalid control block identifier provided.

Explanation The system is trying to find an invalid or nonexistent control block in the list.

Recommended Action No action is required.

Error Message %LRADSIM-3-LRADINITFAIL: Unable to create the control block.

Explanation The system is unable to get a lock for the control block or trying to corrupt the DB with an invalid control block.

Error Message %LRADSIM-3-MSAUTHFAILED: Sending Auth Request for mobile [dec] on AP [dec]failed.

Explanation The system is trying to associate a mobile station on a nonexistent AP.

Recommended Action No action is required.

Error Message %LRADSIM-3-MSDISFAIL: Sending Discovery Request for mobile [dec] failed.

Explanation An invalid parameter has been passed to a discovery request.

Error Message %LRADSIM-3-MSLISTFAIL: Failed to initialize the mobile station list.

Explanation The system is unable to create a lock for the mobile station list. This problem occurs when the system memory is full.

Error Message %LRADSIM-3-NOINTFOUND: Unable to determine the number of interfaces in the system.

Explanation The system is unable to detect the number of active interface present in the system.

Recommended Action This is a debug message only. No action is required.

Error Message %LRADSIM-3-RCBMISMATCH: No active control block found for the ap Id [dec] Auth req can not besent for mobile Id [dec]

Explanation No active block has been found control block found for the AP and an Auth req cannot be sent for the mobile station.

Recommended Action No action is required.

Error Message %LRADSIM-3-SYSMEMFULL: Out of System buffers.

Explanation The system memory is full.

LWAPP Messages

This section contains Lightweight Access Point Protocol (LWAPP) messages.

Error Message %LWAPP-3-AAA_ERR: Could not send AP authorization request

Explanation Due to an error in the internal state of the AP, the AP authorization request could not be sent. The AP might not be able to join the controller.

Error Message %LWAPP-3-AAA_ERR2: Invalid AAA state (’[chars]’) for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The AP could not join the controller due to an internal error.

Error Message %LWAPP-3-ADD_OSSID_ERR: Unable to add [chars] SSID to override table for AP [chars]

Explanation Due to an internal error, override SSID information was not added into the database. The override SSID functionality might not work as expected.

Error Message %LWAPP-3-AKITA_ERR: AP ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) is not supported

Explanation This version of the controller software does not support the AP.

Recommended Action Obtain the right version of the software that supports the AP if you want this AP in the network.

Error Message %LWAPP-3-APEVTLOGDNLDERR: Failed to download event log from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars]

Explanation The controller was unable to download the event log from the specified remote AP. The exact reason of the failure is also in the message.

Recommended Action Identify the reason for the failure from the message.

Error Message %LWAPP-1-AP_CONTAINED: AP [chars] is being contained on slot [dec]

Explanation The specified AP has been detected as a rogue and is being contained.

Error Message %LWAPP-3-AP_DB_CREATE_ERR: Unable to create an entry for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in the database - [chars]

Explanation Could not add the AP into an entry in the internal database.

Error Message %LWAPP-3-AP_DB_DELETE_ERR1: Could not delete AP entry, invalid ID (x[hex])

Explanation Deleting the AP from the internal database has failed because the entry for the AP could not be found. It is possible that the AP has been removed from the controller.

Recommended Action Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, ignore the message. If it is still joined, restart the AP to ensure that it has the latest configuration and contact technical assistance if the problem recurs.

Error Message %LWAPP-3-AP_DB_DELETE_ERR2: Unable to remove AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [chars]

Explanation Due to an internal error, deleting the AP entry from the network processor has failed. If the AP attempts to join this controller, it might not function as expected.

Error Message %LWAPP-3-AP_DB_ERR1: Unable to find AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] entry in the database, could not process [chars]

Explanation The operation being performed for the AP has failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller.

Error Message %LWAPP-3-AP_DB_ERR2: Unable to find AP (id [int]) in the database, [chars]

Explanation The operation being performed for the AP failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller.

Recommended Action Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, the message might be ignored. If it is still joined, restart the AP to ensure that it has the latest configuration and contact technical assistance if the problem recurs.

Error Message %LWAPP-3-AP_DB_FULL: Could not allocate an entry for the AP, database is full

Explanation The internal database for the AP is full, so an entry for the AP could not be added. The AP will not be able to join the controller.

Error Message %LWAPP-3-AP_DBG: Could not execute debug command, command is too long; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The remote debug command is not supported, if possible because it is too long.

Recommended Action No action is required.

Error Message %LWAPP-3-AP_DB_INVALID: AP information in the database is invalid

Explanation An invalid AP entry was found in the AP database. If the AP is still joined to the controller, it might not function properly.

Error Message %LWAPP-4-AP_JDBG_ADD_FAILED: Unable to create AP Join information entry for AP:[hex]:[hex]:[hex]:[hex]:[hex][hex], [chars]

Explanation The AP join information could not be added to the debugging database for the indicated reason. Debugging logs might be incomplete.

Recommended Action If the AP join information entry could not be created because the controller is already maintaining a maximum number of entries supported on the particular controller platform, ignore the message until the controller is rebooted next. This controller does not record any AP join information for any new APs deployed until the next reboot. For all other reasons specified, copy the message and contact technical assistance.

Error Message %LWAPP-4-AP_JDBG_INIT_FAILED: Unable to initialize AP join debugging infrastructure ([chars])

Explanation This AP join debugging infrastructure could not be initialized for the specified number of APs to be supported. The exact reason for the failure is specified in the message. The ability to debug AP join issues is limited.

Recommended Action No action is required.

Error Message %LWAPP-4-AP_JDBG_INVALID_DATA: Invalid AP join debugging data detected ([chars])

Explanation An internal error has occurred when initializing AP join information for debugging. The ability to debug AP join issues is limited.

Recommended Action No action is required.

Error Message %LWAPP-3-AP_LOCK_ERR: Could not obtain exclusive access to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in the database

Explanation Access to an internal AP database has failed. The AP might not function as expected.

Error Message %LWAPP-4-AP_LOG_HOST_CFG_ERR: Unable to set system logging host configuration for AP:[hex]:[hex]:[hex]:[hex]:[hex][hex]

Explanation The controller could not configure system logging configuration for an AP. The AP might not longer be joined to a controller.

Recommended Action No action is required.

Error Message %LWAPP-6-AP_MODEL: [int] APs supported on platform ([chars])

Explanation Informational message that logs how the number of supported APs is being determined.

Recommended Action No action is required.

Error Message %LWAPP-2-AP_MODEL_ERR: Could not determine the # of APs supported from the model string ([chars])

Explanation The system is unable to find the number of APs supported from the machine model string. The system might become unstable.

Error Message %LWAPP-6-AP_NOT_CONTAINED: AP [chars] is not being contained on slot [dec]

Explanation The specified APis not a rogue, so it is not being contained.

Recommended Action No action is required.

Error Message %LWAPP-3-AP_POWER_ERR: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is unable to verify sufficient in-line power, radio slot [dec] is disabled

Explanation The AP power is not within requirements, so the radio slot has been disabled.

Error Message %LWAPP-6-AP_POWER_OK: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has verified sufficient in-line power, radio slot [dec] re-enabled

Explanation The AP power is within requirements, so the radio slot has been enabled.

Recommended Action No action is required.

Error Message %LWAPP-3-AP_REG_ERR: Could not register for AP state notification, maximum limit reached

Explanation An internal table that is used to pass state change notifications between processes is full. Configuration and state change information will not be handled properly and APs might not function as expected.

Error Message %LWAPP-3-AP_TYPE_ERR: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not an H-REAP AP, could not process RADIUS configuration payload

Explanation The RADIUS configuration is only permitted for an H-REAP AP.

Recommended Action Check whether the AP is an H-REAP AP. If not, try to configure the AP in H-REAP mode if possible to enable RADIUS configuration.

Error Message %LWAPP-3-ARP_ERR: Could not resolve ARP of sniffer server IP address ([chars]), disabling sniffing on AP [chars], slot [dec]

Explanation The ARP resolution for the sniffer server has failed and has been disabled.

Recommended Action Check the network configuration and also the configuration of the server IP address on the controller. Ensure that the server is reachable.

Error Message %LWAPP-3-BAND_ERR: Invalid band parameter for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The traffic stream metrics status could not be sent to the specified AP due to an internal error. Traffic stream metrics might not function as expected.

Error Message %LWAPP-1-BIG_NAV: Big Nav attack detected on AP [chars], slot [dec], channel [dec], (errors [dec])

Explanation A NAV attack has been detected on the specified AP.

Recommended Action Check for a NAV has been attack in the network.

Error Message %LWAPP-3-BUILD_STR_ERR: [chars]

Explanation Due to an internal error, the software version information of the controller could not be obtained. The AP might not be able to join the controller.

Error Message %LWAPP-3-CCX_LINKTEST_ERR: Received unexpected CCX Linktest report message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is dropping the unexpected CCX Linktest report message from the AP.

Error Message %LWAPP-3-CCX_RM_ERR: Received an invalid CCX resource management subtype payload (radio management state [dec], slot identifier [dec])

Explanation The radio resource management message was not processed due to an invalid parameter. The CCX radio resource management might not function as expected.

Error Message %LWAPP-3-CERT_ERR1: Error verifying AP certificate, [chars]

Explanation Due to an internal error while processing the AP certificate. A join request has been dropped.

Error Message %LWAPP-3-CERT_ERR2: Unable to retrieve controller’s certificate for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An internal error occurred while obtaining the controller’s certificate.

Error Message %LWAPP-3-CERT_ERR4: Unable to read the controller MAC address from the certificate

Explanation An internal error occurred while reading the MAC address of the controller from the certificate.

Error Message %LWAPP-3-CFG_ERR: Could not save LWAPP configuration in file [chars]

Explanation An error occurred when copying an LWAPP config file to persistent storage. Some of the LWAPP configuration might be lost and the system might not behave as expected.

Error Message %LWAPP-3-CHKSUM_ERR: Invalid checksum in data transfer payload from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (opcode [dec])

Explanation Due to an error in the checksum, the message from the AP has been dropped. The requested information from the AP could not be obtained.

Error Message %LWAPP-6-CONSOLE_LOGIN: Console login success on AP [chars]

Explanation A login attempt on the AP’s console was successful.

Recommended Action No action is required.

Error Message %LWAPP-3-CONSOLE_LOGIN_ERR1: Console login failure on AP [chars]

Explanation A login attempt on the AP’s console was unsuccessful.

Recommended Action Someone tried to log into the AP’s console but authentication failed. If this message is seen multiple times check if someone is attempting to forcibly log into the AP’s console.

Error Message %LWAPP-3-CONSOLE_LOGIN_ERR2: Unknown AP console login alarm from the AP [chars]

Explanation The AP has sent a console login alarm that the controller could not understand.

Error Message %LWAPP-3-COUNT_ERR1: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] marked as [chars] but internal counter is zero

Explanation Due to an error, information about the type of AP is corrupted. The AP might not function as expected.

Error Message %LWAPP-3-COUNT_ERR2: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] type count flag is not set

Explanation Due to an error, information about the type of AP has been corrupted. The AP might not function as expected.

Error Message %LWAPP-3-COUNT_ERR3: Mismatch in the internal count (used entries [dec], normal [dec], mesh [dec])

Explanation Due to an error, information about the type of the AP has been corrupted. The AP might not function as expected.

Error Message %LWAPP-3-COUNT_ERR4: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] marked as normal but internal counter does not reflect this

Explanation Due to an error, information about the type of AP has been corrupted. The AP might not function as expected.

Error Message %LWAPP-3-CRYPTO_ERR1: Unable to encrypt crypto payload with public key for message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An internal error occurred while encrypting a message to the AP. If the AP is already connected to the controller, it might be disconnected. If not, it might not be able to join the controller.

Error Message %LWAPP-3-CRYPTO_ERR2: Unable to encrypt crypto payload with private key for message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Error Message %LWAPP-3-DECODE_ERR: Error decoding [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The LWAPP message sent by the AP was not understood by the controller, so the message has been dropped. The AP might not function as expected.

Error Message %LWAPP-3-DECRYPT_ERR: Unable to decrypt [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Decryption of the LWAPP message has failed. The message has been dropped and the AP might not function as expected.

Error Message %LWAPP-3-DECRYPT_ERR1: Invalid session identifier ([dec]) - unable to decrypt packet; AP:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, decryption of the LWAPP message on the controller has failed and the message has been dropped. The AP might not function as expected.

Error Message %LWAPP-3-DECRYPT_ERR2: Error decrypting public key in key update response from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Rekeying could fail because decrypting with a public key has failed. The AP might not function as expected.

Error Message %LWAPP-3-DECRYPT_ERR3: Private key decryption failed in key update response from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Rekeying could fail because decrypting with a private key has failed. The AP might not function as expected.

Error Message %LWAPP-3-DECRYPT_ERR5: Error decrypting packet (using old key) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (session identifier [hex])

Explanation Due to an internal error, the LWAPP packet could not be decrypted. The AP might not function as expected.

Error Message %LWAPP-3-DECRYPT_ERR8: Authentication of packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] failed, packet will be dropped

Explanation The LWAPP message from the AP has been dropped because of an authentication failure that led to an error in decryption. The AP might not function as expected.

Error Message %LWAPP-3-DECRYPT_ERR9: Unable to decrypt packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with the private key

Explanation Due to an internal error, decrypting the LWAPP message with a private key has failed. The AP might not function as expected.

Error Message %LWAPP-3-DISC_AP_MGR_CAP: Ignoring discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - no AP manager found with spare capacity

Explanation No AP manager was found with the capacity to handle another AP, so the discovery request from an AP was not accepted. The AP will continue to search for an available controller.

Recommended Action Verify the AP manager interface configuration. If the configuration is correct, the maximum number of supported APs has probably been reached.

Error Message %LWAPP-3-DISC_AP_MGR_ERR1: Unable to process primary discovery request from AP on interface ([int]), VLAN ([int]), could not get AP manager [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation A discovery response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.

Recommended Action Correct the AP manager interface configuration.

Error Message %LWAPP-3-DISC_AP_MGR_ERR2: Unable to process primary discovery request from AP, AP manager IP address is invalid [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation A discovery response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.

Recommended Action Correct the AP manager interface configuration.

Error Message %LWAPP-3-DISC_BCAST_ERR: Ignoring a discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] via broadcast AP (IP = [dec].[dec].[dec].[dec]) is not in the same subnet as the controller

Explanation The controller ignored a broadcast discovery request from an AP because the AP is not on the same subnet as the controller.

Recommended Action No action is required.

Error Message %LWAPP-3-DISC_INTF_ERR1: Ignoring discovery request received on non-management interface ([int]) in L3 LWAPP mode

Explanation A discovery request from an AP was ignored because it was received on an invalid interface. The network configuration might be invalid.

Recommended Action Check the network configuration to ensure that packets from the AP are correctly routed.

Error Message %LWAPP-3-DISC_INTF_ERR2: Ignoring discovery request received on a wrong VLAN ([dec]) on interface ([int]) in L3 LWAPP mode

Explanation A discovery request from an AP was ignored because it was received on an invalid interface. Network configuration might be invalid.

Recommended Action Check the network configuration to ensure that packets from the AP are correctly routed.

Error Message %LWAPP-3-DISC_INTF_STATE_ERR: Unable to get [chars] state of interface ’[chars]’ (port [int]), not returning interface in discovery response

Explanation An internal error has occurred when obtaining the administrative state of the interface, so this was not sent in the discovery response. The AP will not be able to send a join request to that interface.

Error Message %LWAPP-0-DISC_LEN_ERR1: Invalid discovery request received from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - message length ([int]) is invalid

Explanation An incorrectly formatted discovery request was received from an AP and was ignored. The AP might not be able to join a controller.

Error Message %LWAPP-0-DISC_LEN_ERR2: Invalid primary discovery request received from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - message length ([int]) is invalid

Explanation An incorrectly formatted primary discovery request was received from an AP and was ignored. The AP might not be able to join a controller.

Error Message %LWAPP-3-DISC_MAX_AP1: Dropping discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - limit for maximum APs supported [dec] reached

Explanation The system’s maximum limit on the number of supported APs has been reached, so this AP will not be serviced.

Recommended Action No action is required.

Error Message %LWAPP-3-DISC_MAX_AP2: Dropping primary discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum APs joined [dec]/[dec]

Explanation The system’s maximum limit on the number of supported APs has been reached, so this AP will not be serviced.

Recommended Action No action is required.

Error Message %LWAPP-3-DISC_MAX_DOWNLOAD: Ignoring discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum number of downloads ([int]) exceeded

Explanation A discovery request from an AP was rejected because the maximum number of concurrent downloads are already in progress. The AP might successfully join the controller on a later attempt.

Recommended Action No action is required.

Error Message %LWAPP-3-DISC_MAX_JOIN: Rejecting discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum AP joins ([int]) exceeded

Explanation A discovery request from an AP was rejected because the maximum number of concurrent joins are already in progress. The AP might successfully join the controller on a later attempt.

Recommended Action No action is required.

Error Message %LWAPP-3-DISC_OTAP_ERR: Ignoring OTAP discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], OTAP is disabled

Explanation The controller has received a discovery request from an AP that has learned the controller’s address over the air, but Over The Air Provisioning (OTAP) is disabled on the controller.

Recommended Action Enable OTAP on the controller if desired; otherwise ignore this message.

Error Message %LWAPP-6-DISC_RESPONSE_SENT: Discovery Response sent successfully to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation A discovery response has been sent succesfully to the AP.

Recommended Action No action is required.

Error Message %LWAPP-4-DISC_TIME_ERR: Unable to retrieve time information while processing discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, the time at which the AP discovery request was received was not recorded. The AP might join the controller and function normally but monitoring of the AP’s presence or absence might not work as expected.

Recommended Action No action is required.

Error Message %LWAPP-3-DISC_TYPE_ERR: Ignoring LWAPP packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - LWAPP packet is not a discovery or a join request (type = [dec]) and session ID is zero

Explanation An invalid LWAPP message was received from an AP and was ignored. The AP might not function as expected.

Error Message %LWAPP-3-DISC_VLAN_ERR: Received a discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on an unsupported VLAN ([int]), dropping the request

Explanation A discovery request was received on a port on which no interface was created.

Recommended Action Check the network configuration to ensure that packets from the AP are correctly routed.

Error Message %LWAPP-3-DISK_ERR: Not enough disk space to store crash file from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An internal error has occurred while attempting to store crash information from the AP to persistent storage.

Error Message %LWAPP-3-DSCP_ERR: Could not get configured DSCP map for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error in obtaining DSCP information for the specified AP, enterprise to enterprise DSCP functionality might not work as expected.

Error Message %LWAPP-3-DUP_AP_IP: Duplicate IP address detected for AP [chars], IP address of AP [chars], this is a duplicate of IP on another machine (MAC address [hex]:[hex]:[hex]:[hex]:[hex]:[hex])

Explanation A duplicate IP address has been detected for the specified AP.

Recommended Action Check the DHCP configuration and also change the IP address of the AP if it was configured statically.

Error Message %LWAPP-3-DUP_ERR: Received a duplicate [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation A duplicate request for a key update has been received from the AP. It is possible that the link between the AP and the controller is slow.

Recommended Action No action is required.

Error Message %LWAPP-3-DUP_IP: Adding client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to exclusion list due to IP Address conflict with AP ’[chars]’

Explanation The AP and client have the same IP address. The Client was block listed.

Recommended Action Check the DHCP configuration and also change the IP address of the AP if it was configured statically.

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 might be connectivity issues between the AP and the controller.

Recommended Action Check if the AP has rebooted, if it has been removed from the network, or if there are connectivity issues between the AP and the controller.

Error Message %LWAPP-3-ENCRYPT_ERR: Encryption of [chars] failed; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system could not transmit the LWAPP message so it could not be encrypted. The AP might not function as expected.

Error Message %LWAPP-3-ENCRYPT_ERR2: Unable to encrypt payload to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with public key

Explanation Due to an internal error, encryption of the crypto payload with the public key has failed. This problem could lead to failures in rekeying and sending the join response.

Error Message %LWAPP-3-ENCRYPT_ERR3: Unable to encrypt payload to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with the private key

Explanation Due to an internal error, encryption of the crypto payload with the private key failed. This could lead to failures in rekeying and also sending the join response.

Error Message %LWAPP-3-FILE_ERR: Unable to open [chars] file for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An internal error has occurred while attempting to store crash information from the AP to persistent storage. The AP crash information might be lost.

Error Message %LWAPP-3-FILE_ERR1: Unable to obtain LWAPP parameters, error opening file [chars]

Explanation An internal error occurred when retrieving LWAPP information from persistent storage. The system might become unstable.

Error Message %LWAPP-3-FILE_ERR3: [chars] [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, an invalid file name was received and the controller could not send a message to the AP for obtaining the specified information.

Error Message %LWAPP-3-FILE_ERR4: Internal file error while processing image data payload message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, the AP’s image information could not be obtained. A firmware download to the AP might fail.

Error Message %LWAPP-3-FILE_ERR5: File could not be opened to store [chars] information from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, data from the AP could not be stored in persistent memory. Some information related to the AP might be lost.

Error Message %LWAPP-3-FILE_ERR6: Unable to write [chars] information from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] into local file

Explanation Due to an internal error, data from the AP could not be stored in persistent memory. Some information related to the AP might be lost.

Error Message %LWAPP-3-HDR_ENCAP_ERR: Unable to encapsulate LWAPP header for [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system could not send the LWAPP packet due to an internal error in encapsulating the packet. The AP might not function as expected.

Error Message %LWAPP-3-HDR_ERR: Received LWAPP packet with unsupported bit field ([hex],[hex]) from [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet

Explanation An invalid LWAPP packet has been received and the packet has been dropped.

Error Message %LWAPP-3-HDR_ERR2: LWAPP header translation failed, dropping the packet

Explanation An internal error occurred when processing an LWAPP control packet. The LWAPP header was not understood and the packet has been dropped.

Error Message %LWAPP-3-HDR_ERR3: Failed parsing LWAPP

Explanation Due to an internal error, LWAPP header processing has failed. The packet has been dropped.

Error Message %LWAPP-3-HDR_PARSE_ERR: LWAPP header parsing failed, dropping the packet

Explanation Processing of an LWAPP control packet from the AP has failed because the LWAPP header was not understood. The AP might not function as expected.

Error Message %LWAPP-3-HREAP_ERR: Received invalid H-REAP operation for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] while processing RADIUS configuration payload (flag [hex])

Explanation Due to an internal error, the RADIUS configuration could not be updated on the specified AP.

Error Message %LWAPP-3-HREAP_ERR2: Received invalid RADIUS port number (AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]) while processing RADIUS configuration payload

Explanation Due to an invalid port number, the RADIUS configuration could not be updated on the specified AP.

Error Message %LWAPP-3-IMAGE_DOWNLOAD_ERR: Refusing [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - controller image upgrade is in process

Explanation The specified request from the AP is ignored because the controller’s software is being upgraded. Future attempts from the AP might succeed.

Recommended Action No action is required.

Error Message %LWAPP-3-IMAGE_DOWNLOAD_ERR2: Refusing image download request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - max downloads ([dec]) in progress

Explanation The system is ignoring the image download request from the AP because the maximum number of concurrent image download requests are in progress. This is a temporary condition; future attempts by the AP might succeed.

Recommended Action No action is required.

Error Message %LWAPP-3-IMAGE_DOWNLOAD_ERR3: Refusing image download request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - unable to open image file [chars]

Explanation Due to an internal error, the image for the AP requesting image download could not be obtained. The AP image download will fail.

Error Message %LWAPP-3-IMAGE_DOWNLOAD_ERR4: Refusing image download request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - unable to open MD5 file [chars]

Explanation Due to an internal error, the image for the AP requesting image download could not be obtained. The AP image download will fail.

Error Message %LWAPP-3-INDEX_ERR: Invalid index ([int]) while [chars] per port AP load information

Explanation An internal error occurred when processing AP load information. Some AP management functions might not work as expected.

Error Message %LWAPP-3-INVALID_AID: Received invalid association identifier ([int]) for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on a REAP AP

Explanation An internal error caused an invalid association ID to be received from an AP for the indicated client. The client might experience communication problems.

Error Message %LWAPP-3-INVALID_AID2: Association identifier [int] for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is already in use by [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An internal error caused an invalid association ID to be received from an AP for the indicated client. The client might experience communication problems.

Error Message %LWAPP-3-INVALID_DELIM: Invalid delimiter ([dec]) in AP authorization list

Explanation Due to an invalid delimiter specified, the AP could not be authenticated, so a join response could not be sent.

Recommended Action Check the delimiter configured on the controller.

Error Message %LWAPP-3-INVALID_IP: Invalid sniffer server IP address ([hex]), disabling sniffing on AP [chars], slot [dec]

Explanation Sniffing has been disabled because the IP address of the server was invalid.

Recommended Action Check the configuration of the sniffer server’s IP address.

Error Message %LWAPP-3-INVALID_PARAMETER: Invalid [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The specified parameter was not understood by the controller, so the message was not processed. The AP might not function as expected.

Error Message %LWAPP-3-INVALID_PARAMETER1: [chars] ([dec]); AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The value of parameter specified was not understood by the controller, so the message was not processed. The AP might not function as expected.

Error Message %LWAPP-3-INVALID_PARAMETER2: [chars] ([dec]) - [chars]; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The value of parameter specified was not understood by the controller, so the message was not processed. AP might not function as expected.

Error Message %LWAPP-3-INVALID_PARAMETER3: [chars] ([dec])

Explanation The value of parameter specified was not understood by the controller, so the message was not processed.

Error Message %LWAPP-3-INVALID_PARAMETER4: [chars]

Explanation The value of parameter specified was not understood by the controller, the message was not processed.

Error Message %LWAPP-3-INVALID_RADIO: Received an unsupported radio ([dec]), [chars]

Explanation Performing the specified operation on the radio for the AP has failed because the radio was not understood by the controller. The AP might not function as expected.

Error Message %LWAPP-3-INVALID_RADIO2: Received invalid radio type ([dec]) for AP [chars] on slot [dec], could not verify power level for the AP

Explanation Due to an internal error, an invalid radio type has been received. The specified operation could not be performed.

Error Message %LWAPP-3-INVALID_SESSIONID: Received invalid session identifier in [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (expected [dec] and got [dec])

Explanation A mismatch has occurred on the session identifier in the message from the AP. The message has been dropped.

Error Message %LWAPP-3-INVALID_SLOT: Invalid slot identifier ([dec]) - [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The slot identifier sent by the AP was not understood by the controller, so the specified message was not processed. The AP might not function as expected.

Error Message %LWAPP-3-INVALID_SLOT2: Invalid slot identifier ([dec]) - [chars] ([dec]): AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The slot identifier for the AP was not understood by the controller, so the specified message was not processed. The AP might not function as expected.

Error Message %LWAPP-3-INVALID_WLAN: Invalid WLAN identifier ([int]) obtained while building MFP config payload

Explanation An internal error occurred when attempting to retrieve the WLAN configuration. The MFP might not be operational or might not work as expected.

Error Message %LWAPP-3-IP_ERR: Could not plumb AP’s ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) IP address ([dec].[dec].[dec].[dec]), next hop MAC ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) and VLAN ([dec]) to fast path

Explanation Due to an internal error, the IP address of the AP could not be configured in the network processor. The AP might not function as expected.

Error Message %LWAPP-3-IP_PROT_ERR: IP protocol ([dec]) in the received packet - from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not UDP, LWAPP packets are only UDP, dropping the packet

Explanation An invalid packet received from the AP has been dropped.

Error Message %LWAPP-3-JOIN_AP_MGR_ERR1: Could not get IP address of AP manager interface, dropping join request from AP [hex]:[hex]:[hex]:[hex]:[hex][hex]

Explanation A join response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.

Error Message %LWAPP-3-JOIN_AP_MGR_ERR2: Received a join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] for someone else ([dec].[dec].[dec].[dec]), dropping the packet

Explanation A join request with a destination IP address that does not match any AP manager’s IP address, has been dropped.

Recommended Action Check the network configuration and also the configuration of the AP manager on the controller and ensure that the packets from the AP are routed correctly.

Error Message %LWAPP-3-JOIN_DB_ERR: Could not allocate an entry in the database for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - dropping the join request (# of APs joined = [dec])

Explanation An internal error has resulted in a failure while creating an entry for the AP in the database.

Recommended Action Check if the number of APs that are currently joined to this controller is also the maximum limit.

Error Message %LWAPP-3-JOIN_HIGH_PRIORITY_AP_ERR: Disconnecting AP [chars] since a higher priority AP with priority [dec] joined Max number of APs allowed [dec]

Explanation When an AP join priority is enabled and the controller has the maximum numbers of APs connected, a low priority AP is disconnected when a high priority AP joins.

Recommended Action No action is required.

Error Message %LWAPP-3-JOIN_INTF_ERR1: Received a join request on an invalid interface ([dec]) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet

Explanation The IP address of the interface on which the join request was received could not be obtained.

Recommended Action Check the interface configuration on the controller.

Error Message %LWAPP-3-JOIN_INVALID_ERR1: Invalid [chars] in LWAPP join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The AP sent a join request that was invalid because it lacked certain payloads. Such requests are dropped at the controller. AP might not be able to join the controller.

Error Message %LWAPP-3-JOIN_INVALID_ERR2: Invalid [chars] ([dec]) in join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The AP sent a join request that was invalid because lengths of certain payloads within the request were incorrect. Such requests are dropped at the controller. The AP might not be able to join the controller.

Error Message %LWAPP-3-JOIN_INVALID_SLOT: Join request from AP ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) has invalid number of slots ([dec], instead of [dec]), dropping the packet

Explanation The number of radios that the AP supports is invalid as per what is sent in the join request. The join request has been dropped.

Error Message %LWAPP-3-JOIN_MAC_ERR: Received a join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] destined for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on port [int]/VLAN [int] - invalid destination MAC address, dropping the packet

Explanation The MAC address in the join request was invalid, so this request has been dropped by the controller.

Recommended Action Check the network configuration and ensure that the packets from the AP are routed correctly.

Error Message %LWAPP-6-JOIN_MASTER: Controller is also configured as the master, AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The controller is also configured as the primary controller. Change the configuration of the controller so that it is not the primary.

Recommended Action No action is required.

Error Message %LWAPP-3-JOIN_MAX_AP_ERR: Received a join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - reached limit for maximum APs [dec]/[dec], dropping the packet

Explanation Each controller has a limit on the number of APs that can be supported. This limit has been reached, so the AP was not serviced.

Recommended Action No action is required.

Error Message %LWAPP-3-JOIN_MAX_AP_INTF_ERR: Received a join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], reached limit for maximum number of APs ([dec]) on interface [dec], dropping the packet

Explanation Each interface has a limit on the number of APs that can be supported. This limit has been reached for the interface. The join request has been dropped. If the AP sends join request to another interface, a join response might be sent.

Recommended Action No action is required.

Error Message %LWAPP-3-JOIN_MAX_DOWNLOAD_ERR: Reached max limit ([dec]) on the number of APs that can download image, dropping join request

Explanation The controller could not respond to the join request from the AP because the current limit on the maximum number of concurrent image downloads possible has been reached. This problem might be a transient condition. If AP continues to send join requests, a join response would be sent.

Recommended Action No action is required.

Error Message %LWAPP-3-JOIN_MAX_JOIN_ERR: Reached max limit ([dec]) on the number of APs that can join the controller, dropping join request

Explanation The controller could not respond to the join request from the AP because the current limit on the maximum number of concurrent join requests that can be processed has been reached. This problem might be a transient condition. If AP continues to send join requests, a join response would be sent.

Recommended Action No action is required.

Error Message %LWAPP-3-JOIN_UNSUPP_AP: Received a join request from an unsupported AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [chars] (model [chars]), dropping the packet

Explanation This version of the controller software does not support the AP model.

Recommended Action Check the documentation regarding the software version on supported AP models. Remove this AP from the network or move to a version of software that supports the AP.

Error Message %LWAPP-3-KEY_ERR1: Unable to obtain public key from the certificate of AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex], [chars]

Explanation Due to an internal error, a public key for the AP could not be obtained, and a join response could not be sent to the AP.

Error Message %LWAPP-3-KEY_ERR2: Invalid public key type in certificate for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an invalid public key type for the AP, a join response could not be sent to the AP.

Error Message %LWAPP-3-KEY_ERR3: Unable to free public key for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, public key information for this AP was not removed from the database while deleting the AP. There might be problems if this AP attempts to join the controller again.

Error Message %LWAPP-4-L3_PACK_ERR: Received an L3 LWAPP packet in L2 LWAPP mode, dropping the packet

Explanation The controller is configured in L3 LWAPP mode so packets received for the L2 LWAPP mode are being dropped.

Recommended Action No action is required.

Error Message %LWAPP-6-LAG_TRAN: Link aggregation configuration is in transition

Explanation The controller’s link aggregation configuration has been changed but the changes do not take effect until the next system reboot.

Recommended Action No action is required.

Error Message %LWAPP-2-LIST_ERR1: List is corrupted - (head [address], tail [address], count [int])

Explanation An internal error caused the list of APs maintained by the controller to become corrupted. The system might become unstable.

Error Message %LWAPP-2-LIST_ERR2: List is corrupted - (head [address], tail [address], count [int], p [address], p->next[address], p->prev [address])

Explanation An internal error caused the list of APs maintained by the controller to become corrupted. The system might become unstable.

Error Message %LWAPP-2-LIST_ERR3: List is corrupted - (head [address], tail [address], count [int], actual [int])

Explanation An internal error caused the list of APs maintained by the controller to become corrupted. The system might become unstable.

Error Message %LWAPP-2-LIST_ERR4: List is corrupted - (head [address], tail [address], p [address], p->next [address], p->tail[address])

Explanation An internal error caused the list of APs maintained by the controller to become corrupted. The system might become unstable.

Error Message %LWAPP-2-LIST_ERR5: Skipping duplicate insertion - ( head [address], tail [address], count [int],entry [address])

Explanation An internal error occurred when attempting to add an entry to the AP database. The system might become unstable.

Error Message %LWAPP-2-LIST_ERR6: Entry [address] not in the list - ([address], head [address], tail [address])

Explanation An internal error occurred when attempting to remove an entry from the AP database. The system might become unstable.

Error Message %LWAPP-3-LIST_ERR7: Unable to delete AP entry, index ([dec]) is greater than maximum allowed

Explanation The system is unable to delete an entry in the AP table due to an internal error.

Error Message %LWAPP-3-LIST_ERR8: Unable to delete AP entry, entry not allocated

Explanation The system is unable to a delete entry in the AP table; the entry has not been allocated.

Error Message %LWAPP-3-MAX_AID: Reached max limit ([dec]) on the association ID for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation A maximum number of clients that can be supported on the AP has been reached, and association identifiers have been exhausted. A new client cannot be supported on the AP.

Recommended Action No action is required.

Error Message %LWAPP-3-MAX_AID2: Reached max limit on the association ID for AP (max association ID [dec])

Explanation A maximum number of clients that can be supported on the AP has been reached, and association identifiers have been exhausted. A new client cannot be supported on the AP.

Recommended Action No action is required.

Error Message %LWAPP-3-MBUF_ERR: No more system buffers, could not receive LWAPP packet

Explanation The system is out of system buffers.

Error Message %LWAPP-3-MCAST_APP_ERR: Failed to obtain multicast appliance configuration for interface [int], using default index ([int])

Explanation Due to an internal error, the multicast appliance configuration could not be obtained. Multicast might not operate as expected.

Error Message %LWAPP-3-MEM_ERR: Unable to allocate memory [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is running on low memory.

Error Message %LWAPP-3-MEM_ERR2: Unable to allocate memory for LWAPP message

Explanation System is running low on memory.

Error Message %LWAPP-3-MEM_ERR3: Unable to allocate memory [chars]

Explanation The system is running low on memory.

Error Message %LWAPP-3-MEM_ERR4: Unable to allocate memory [chars] (AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex])

Explanation The system is running low on memory.

Error Message %LWAPP-3-MFP_ERR: MFP report count ([int]) is too big in message; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Could not process an MFP report because the message is too large. The MFP might not work as expected.

Error Message %LWAPP-3-MFP_ERR1: Ignoring MFP message [chars] with invalid slot ([int]) in message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The MFP message from the AP had an invalid slot; the MFP might not function as expected.

Error Message %LWAPP-3-MIC_COUNTER: Received MIC countermeasure, WLAN [dec], slot [dec] AP [chars] client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation MIC errors have occurred on the specified AP. Clients might not be able to connect on the specified WLAN.

Recommended Action Check for attacks in the network.

Error Message %LWAPP-3-MIGRATE_ERR: Failed to migrate to regulatory domain requested for AP (name [chars], model [chars], MAC [hex]:[hex]:[hex]:[hex]:[hex]:[hex],serial number [chars])

Explanation An attempt to migrate to a new regulatory domain has failed on the AP.

Error Message %LWAPP-3-MIRROR_ERR: Setting mirroring mode failed

Explanation Due to an internal error, the configuration of the mirroring mode has failed.

Error Message %LWAPP-0-MSG_QUEUE_ERR: LWAPP message queue has not been created

Explanation The LWAPP subsystem has not been initialized. APs might not be able to join the controller.

Error Message %LWAPP-3-MSG_RCV: Could not receive message from LWAPP queue

Explanation An internal error has occurred while reading an LWAPP message. The system will attempt to process other LWAPP messages.

Error Message %LWAPP-3-MSG_SEND_ERR: Unable to send [chars] message to LWAPP; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The LWAPP process might be busy. If this condition persists, it could lead to loss of LWAPP packets, dropping of AP connections, and the AP not getting configuration changes from the controller.

Error Message %LWAPP-3-MSG_SEND_ERR2: Unable to send [chars] message to LWAPP

Explanation The LWAPP process might be busy. If this condition persists, it could lead to loss of LWAPP packets, dropping of AP connections and AP not getting configuration changes from the controller.

Error Message %LWAPP-0-MSGTAG071: MESH Child [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has changed route or disconnected from Parent ([chars]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Explanation The MESH Child [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has changed a route or disconnected from the parent ([chars]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-0-MSGTAG072: Parent changed excessively. AP [chars] changed parent macAddr =[hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Explanation A parent changed a route excessively. The AP [chars] has changed the parent MAC address=[hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG073: Unknown Mesh Neighbor Event from the AP [chars].

Explanation An unknown mesh neighbor event has occurred from the AP [chars].

Error Message %LWAPP-3-MSGTAG162: Did not specify the MAC address for Mesh Neigh Request [dec]config

Explanation The system did not specify the MAC address for the mesh neighbor request [dec] the configuration.

Error Message %LWAPP-3-MSGTAG221: [chars]() : Could not generate nonce

Explanation [chars]() : The System Could not generate a nonce.

Error Message %LWAPP-3-MSGTAG257: 1: msgLen [dec]

Explanation 1: msgLen [dec]

Error Message %LWAPP-3-MSGTAG258: 2: len [dec] Type : [dec] = [dec]

Explanation 2: len [dec] Type : [dec] = [dec]

Error Message %LWAPP-3-MSGTAG259: 1: msgLen [dec]

Explanation 1: msgLen [dec]

Error Message %LWAPP-3-MSGTAG260: 2: len [dec] Type : [dec] = [dec]

Explanation 2: len [dec] Type : [dec] = [dec]

Error Message %LWAPP-3-MSGTAG261: 1: msgLen [dec]

Explanation 1: msgLen [dec]

Error Message %LWAPP-3-MSGTAG262: 2: len [dec] Type : [dec] = [dec]

Explanation 2: len [dec] Type : [dec] = [dec]

Error Message %LWAPP-3-MSGTAG263: 1: msgLen [dec]

Explanation 1: msgLen [dec]

Error Message %LWAPP-3-MSGTAG264: 2: len [dec] Type : [dec] = [dec]

Explanation 2: len [dec] Type : [dec] = [dec]

Error Message %LWAPP-3-MSGTAG265: 1: msgLen [dec]

Explanation 1: msgLen [dec]

Error Message %LWAPP-3-MSGTAG266: 2: len [dec] of [dec] Type : [dec] = [dec]

Explanation 2: len [dec] of [dec] Type : [dec] = [dec]

Error Message %LWAPP-3-MSGTAG267: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG268: spamMeshSecbhStatsPayloadDecode: len received:[dec] expected=[dec] numQueues=[dec]\n

Explanation spamMeshSecbhStatsPayloadDecode: len received:[dec] expected=[dec] numQueues=[dec]\n

Error Message %LWAPP-3-MSGTAG269: spamMeshSecbhStatsPayloadDecode: unexpected slotId=[dec]\n

Explanation spamMeshSecbhStatsPayloadDecode: unexpected slotId=[dec]\n

Error Message %LWAPP-3-MSGTAG270: 1: msgLen [dec]

Explanation 1: msgLen [dec]

Error Message %LWAPP-3-MSGTAG271: MESH_NODE_UPDATE_PAYLOAD: len received:[dec] expected=[dec]

Explanation MESH_NODE_UPDATE_PAYLOAD: len received:[dec] expected=[dec]

Error Message %LWAPP-3-MSGTAG272: spamDecodeMeshNodeUpdate: invalid payload type=[dec]

Explanation spamDecodeMeshNodeUpdate: invalid payload type=[dec]

Error Message %LWAPP-3-MSGTAG273: 1: msgLen [dec]

Explanation 1: msgLen [dec]

Error Message %LWAPP-3-MSGTAG274: 2: len [dec] of [dec] Type : [dec] = [dec]

Explanation 2: len [dec] of [dec] Type : [dec] = [dec]

Error Message %LWAPP-3-MSGTAG275: 1: msgLen [dec]

Explanation 1: msgLen [dec]

Error Message %LWAPP-3-MSGTAG276: 2: len [dec] of [dec] Type : [dec] = [dec]

Explanation 2: len [dec] of [dec] Type : [dec] = [dec]

Error Message %LWAPP-3-MSGTAG277: spamSendLinktestRequest: refusing to send request when previous request is pending ltid [dec]

Explanation spamSendLinktestRequest: refusing to send a request when a previous request is pending ltid [dec].

Error Message %LWAPP-3-MSGTAG278: spamDecodeLinktestResponse invalid msgLen [dec]

Explanation spamDecodeLinktestResponse invalid msgLen [dec]

Error Message %LWAPP-3-MSGTAG279: spamDecodeLinktestResponse LINKTEST_CFG_PAYLOAD([dec]): invalid payload len [dec] != [dec] (msglen [dec])

Explanation spamDecodeLinktestResponse LINKTEST_CFG_PAYLOAD([dec]): invalid payload len [dec] != [dec] (msglen [dec])

Error Message %LWAPP-3-MSGTAG280: spamDecodeLinktestResponse LINKTEST_RESULTS_PAYLOAD([dec]): invalid payload len [dec] != [dec]

Explanation spamDecodeLinktestResponse LINKTEST_RESULTS_PAYLOAD([dec]): invalid payload len [dec] != [dec]

Error Message %LWAPP-3-MSGTAG281: Out of range linktest ID ([dec]) specified

Explanation An out of range linktest ID ([dec]) has specified.

Error Message %LWAPP-3-MSGTAG282: Attempt to obtain results from free linktest ID ([dec])

Explanation An attempt has been made to obtain results from the free linktest ID ([dec]).

Error Message %LWAPP-3-MSGTAG283: invalid linktestId [dec]

Explanation The system has detected an invalid linktestId [dec].

Error Message %LWAPP-3-MSGTAG284: invalid linktestId [dec]

Explanation The system has detected an invalid linktestId [dec].

Error Message %LWAPP-3-MSGTAG285: invalid linktestId [dec]

Explanation The system has detected an nvalid linktestId [dec].

Error Message %LWAPP-3-MSGTAG286: apfApLinktestFree: attempt to free linktestId=[dec] which is already free

Explanation apfApLinktestFree: an attempt has been to free a linktestId=[dec] that is already free.

Error Message %LWAPP-3-MSGTAG287: FREEING LinkTest [dec]: (status [dec]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -> [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation FREEING LinkTest [dec]: (status [dec]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -> [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Error Message %LWAPP-3-MSGTAG288: aplinktest_test: apfApLinktest returned failure

Explanation aplinktest_test: apfApLinktest returned failure

Error Message %LWAPP-3-MSGTAG289: aplinktest_test: apfApLinktest returned success, ltid [dec]

Explanation aplinktest_test: apfApLinktest returned success, ltid [dec]

Error Message %LWAPP-3-MSGTAG290: aplinktest_test: apfApLinktest returned failure

Explanation aplinktest_test: apfApLinktest returned failure

Error Message %LWAPP-3-MSGTAG291: aplinktest_test: apfApLinktest returned success, ltid [dec]

Explanation aplinktest_test: apfApLinktest returned success, ltid [dec]

Error Message %LWAPP-3-MSGTAG292: [dec]: (status [dec]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -> [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec]

Explanation [dec]: (status [dec]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -> [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec]

Error Message %LWAPP-3-MSGTAG293: [dec]: FREE

Explanation [dec]: FREE

Error Message %LWAPP-3-MSGTAG535: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] associated. Last AP rebooting was because RAP was using radio backhaul as uplink for 15 minutes.

Explanation The AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has associated. The last AP reboot was because the RAP was using a radio backhaul as an uplink for 15 minutes.

Error Message %LWAPP-3-MSGTAG650: LWAPP Join Request Country Code invalid for Bridge AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An LWAPP join request country code is invalid for the Bridge AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG651: LWAPP Join Request Bridge Authentication failed for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An LWAPP join request bridge authentication has failed for the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG675: Mesh APs not supported in multi-country mode. Rejected AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Mesh APs are not supported in multi-country mode. Rejected AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG702: Not creating SSID [chars] on Bridge AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because wlan0 is not supported

Explanation This system is not creating an SSID [chars] on the Bridge AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because WLAN0 is not supported.

Error Message %LWAPP-3-MSGTAG829: Unable to allocate buffer for mesh link para message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for mesh link para message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG830: Unable to allocate buffer for AP BH rate message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for the AP BH rate message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG831: Unable to allocate buffer for AP BH dev message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for the AP BH dev message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG832: Unable to allocate buffer for AP Bridge State message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for the AP bridge state message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG833: Unable to allocate buffer for AP Bridge Groupname message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for the AP bridge group name message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG834: Unable to allocate buffer for AP Public Safety message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for the AP public safety message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG881: Unable to allocate buffer for Mesh Neigh Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for the mesh neigh request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG882: Unable to allocate buffer for Mesh Linktest Data Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for the mesh link test data request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG883: Unable to allocate buffer for Mesh Path Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for the mesh path request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG884: Unable to allocate buffer for Mesh Stats Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for th mesh stats request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG885: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG886: Received Mesh stats response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a mesh stats response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG887: Security processing of Mesh Stats Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Security processing of a mesh stats response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG888: Processing of Mesh Stats Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing of a mesh stats response failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG889: Unable to allocate buffer for Mesh Security Stats Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for a mesh security stats request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG890: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG891: Received Mesh Security Stats response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received mesh security stats response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG892: Processing of Mesh Security Stats Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing of mesh security stats response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG893: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG894: Received Mesh Adj response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a mesh adj response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG895: Security processing of Mesh Adj Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Security processing of a mesh adj response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG896: Processing of Mesh Adj Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing of a mesh adj response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG897: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG898: Received Mesh Neigh response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a mesh neigh response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG899: Security processing of Mesh Neigh Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Security processing of a mesh neigh response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG900: Processing of Mesh Neigh Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing of a mesh neigh response failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG901: Unable to allocate buffer for Mesh Linkrate Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for a mesh link rate request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG902: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG903: Received Mesh Linkrate response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a mesh link rate response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG904: Security processing of Mesh Linkrate Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Security processing of a mesh link rate response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG905: Processing of Mesh Linkrate Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing of a mesh link rate response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG906: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG907: Received station stats update from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a station stats update from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG908: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG909: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG910: Received mesh node update from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a mesh node update from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG911: Processing of mesh node update failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing amesh node update failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG912: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG913: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG914: Received mesh env. update from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a mesh env. update from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG915: Processing of mesh env. update failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing of a mesh env. update has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG916: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG917: Failed to update CAC module with parent address: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has failed to update the CAC module with the parent address: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG918: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG919: Received mesh neighs update from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a mesh neighs update from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG920: Processing of mesh neighs update failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing of a mesh neighs update has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG921: Unable to allocate buffer for Linktest Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to allocate a buffer for a link test request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG922: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG923: spamDecodeLinktestResponse LINKTEST_CFG_PAYLOAD([dec]): linktest ID from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation spamDecodeLinktestResponse LINKTEST_CFG_PAYLOAD([dec]): linktest ID from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG924: spamDecodeLinktestResponse (ltid:[dec]) unexpected LINKTEST_CFG_PAYLOAD from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation spamDecodeLinktestResponse (ltid:[dec]) unexpected LINKTEST_CFG_PAYLOAD from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG925: spamDecodeLinktestResponse LINKTEST_RESULTS_PAYLOAD([dec]): invalid linktest ID([dec]) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation spamDecodeLinktestResponse LINKTEST_RESULTS_PAYLOAD([dec]): invalid linktest ID([dec]) from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG926: spamDecodeLinktestResponse (ltid:[dec]) unexpected LINKTEST_RESULTS_PAYLOAD from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation spamDecodeLinktestResponse (ltid:[dec]) unexpected LINKTEST_RESULTS_PAYLOAD from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG927: spamDecodeLinktestResponse unrecognized payload [dec] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation spamDecodeLinktestResponse unrecognized payload [dec] from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG928: Linktest requested for unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Link test requested for an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG929: Linktest already running on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Link test already running on the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG930: Linktest already running on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Link test already running on the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG931: link test id is already in use: [dec]

Explanation Link test ID is already in use: [dec].

Error Message %LWAPP-3-MSGTAG932: Too many linktests running, cannot manage AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Too many link tests running; cannot manage the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG933: Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG934: Received linktest response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system has received a link test response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-MSGTAG935: Processing of linktest response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Processing of a link test response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Error Message %LWAPP-3-NPU_ERR: Invalid NPU index [int]

Explanation The system is indexing into the network processor’s internal table with an invalid index.

Error Message %LWAPP-3-NPU_ERR2: All NPU indices have been used (max [dec])

Explanation The System could not create an entry for the AP in fast path because the internal database is full. The AP might not be able to join the controller.

Error Message %LWAPP-3-NPU_ERR3: Could not allocate NPU index for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, the AP entry in the fast path could not be configured successfully. The AP might not be able to join the controller.

Error Message %LWAPP-3-NPU_ERR4: Failed to add NPU entry for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], index: [int], switch IP: [int].[int].[int].[int], switch port: [int], interface num: [int], VLAN: [int] AP IP: [int].[int].[int].[int], AP Port: [int], next hop MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, the AP entry could not be added to the network processor. The AP might not behave as expected.

Error Message %LWAPP-3-OFDM_ERR: Received invalid OFDM channel ([int]), unable to set the channel

Explanation An internal error occurred when attempting to configure a channel.

Error Message %LWAPP-3-OSSID_ERR: Override SSID [chars] does not exist on the controller

Explanation The system could not delete the specific override SSID from the controller’s database The override SSID functionality might not work as expected.

Error Message %LWAPP-3-PARSE_ERR: LWAPP header parsing failed for packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet

Explanation An internal error has occurred when processing a LWAPP control packet. The LWAPP header was not understood, so the packet was dropped. The AP might not function as expected.

Error Message %LWAPP-3-PARSE_ERR2: LWAPP header parsing failed, dropping the packet

Explanation An internal error has occurred when processing a LWAPP control packet. The LWAPP header was not understood, so the packet was dropped. The AP might not function as expected.

Error Message %LWAPP-3-PARSE_ERR3: Unable to parse LWAPP headers for [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An internal error has occurred when processing a LWAPP control packet. The LWAPP header was not understood, so the packet was dropped. The AP might not function as expected.

Error Message %LWAPP-3-PAYLOAD_ERR: [chars] - AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Not all payloads expected in the LWAPP message are present. The controller is dropping LWAPP messages from the AP. The AP might not be able to join the controller.

Error Message %LWAPP-3-PAYLOAD_MISSING: [chars] -

Explanation Not all payloads expected in the LWAPP message are present.

Error Message %LWAPP-0-PDISC_LEN_ERR: Invalid primary discovery request received from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - message length ([int]) is invalid

Explanation An incorrectly formatted primary discovery request was received from an access point and was ignored.

Recommended Action No action is required.

Error Message %LWAPP-6-PORTMAP_ERR: Failed to obtain multicast port map for interface [int], using default index ([int])

Explanation The system could not get information on a multicast port using the information that is available for unicast. Multicast might not work as expected.

Error Message %LWAPP-3-PROFILE_NAME_ERR: Could not find profile name for WLAN [dec] with SSID [chars]; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The profile name for the WLAN could not be found in the database.

Error Message %LWAPP-3-PROFILE_NAME_ERR2: Could not find profile name for WLAN with SSID [chars]

Explanation The profile name for the WLAN could not be found in the database.

Error Message %LWAPP-3-RADIO_CRASH: Radio ([dec]) crashed and generated a core dump on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An error has occurred on the radio for the specified AP. The AP might not function as expected.

Recommended Action Collect the radio crash information for the AP and contact technical assistance.

Error Message %LWAPP-2-RADIO_ERR: [chars] failure on radio slot [dec] on AP [chars]

Explanation The radio slot on the specified AP has failed. It will impact clients that are connected.

Error Message %LWAPP-3-RADIO_ERR2: Unknown AP radio failed alarm ([dec]) from the AP [chars]

Explanation The AP has sent a radio failed alarm that the controller could not understand.

Error Message %LWAPP-2-RADIO_NOERR: AP [chars] recovered from [chars] failure on radio slot [dec]

Explanation The radio slot on the specified AP is not experiencing failures at this time.

Recommended Action No action is required.

Error Message %LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The join reply has not been sent to the AP because AP authentication failed.

Recommended Action Check the AP credentials on the RADIUS server, or the local MAC filtering table - if it was configured. Also check if RADIUS servers are configured and are reachable.

Error Message %LWAPP-3-RADIUS_PORT_ERR: Received invalid RADIUS port number for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The port number for RADIUS is incorrect. RADIUS configuration could not be configured on the AP.

Recommended Action Check the RADIUS configuration for the H-REAP APs configured on the controller.

Error Message %LWAPP-3-RADIUS_SECRET_ERR1: MAC filtering request dropped as shared secret for RADIUS was not found

Explanation The system is unable to find a RADIUS password, so the MAC filter authenticate request has been canceled. The AP might not be able to join the controller.

Recommended Action Check the RADIUS shared secret configured on the controller and the RADIUS server.

Error Message %LWAPP-3-RADIUS_SECRET_ERR2: Received invalid RADIUS shared secret; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The length of the shared secret is incorrect, so the RADIUS configuration could not be configured on the AP.

Recommended Action Check the RADIUS configuration for the H-REAP APs configured on the controller.

Error Message %LWAPP-3-RD_ERR: Regulatory domain of the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] does not match the country code ([chars])

Explanation A mismatch has occurred in the country code and regulatory domain configured on the AP and controller. The AP might not be able to join the controller.

Recommended Action Check if the correct (that intended to work with the AP) country code is configured on the controller

Error Message %LWAPP-3-RD_ERR10: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is disabled - default country code is [chars]

Explanation Due to an error in the regulatory domain configured on the AP and the inability to associate a correct country code, the AP has been disabled. The AP will not be able to function as expected.

Recommended Action Check if the correct country code is configured on the controller

Error Message %LWAPP-3-RD_ERR2: Regulatory domain for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not updated for all slots. (Updated [dec] out of [dec] filled slots)

Explanation An error has occurred in the regulatory domain information for the slots on the AP. All of them do not have it configured. The AP might not be able to join the controller.

Error Message %LWAPP-3-RD_ERR3: Invalid regulatory domain ([hex]) sent by AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (slot: [dec] [chars])

Explanation The regulatory domain configured on the AP slot was not understood. The AP might not be able to join the controller.

Recommended Action Check if the correct country code is configured on the controller.

Error Message %LWAPP-3-RD_ERR4: Invalid regulatory domain [chars] for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The regulatory domain configured on the AP was not understood. The AP might not be able to join the controller.

Recommended Action Check if the correct country code is configured on the controller

Error Message %LWAPP-3-RD_ERR5: APs ([hex]:[hex]:[hex]:[hex]:[hex]:[hex] - slot [dec] [chars]) regulatory domain is not set, this is not allowed in country [chars]

Explanation Due to an error in the regulatory domain configured on the AP, the AP might not be able to join the controller.

Error Message %LWAPP-3-RD_ERR6: APs ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) regulatory domain ([chars]) is not supported in country ([chars]), slot [chars] ([dec]) supports [chars]

Explanation Due to an error in the regulatory domain configured on the AP, the AP might not be able to join the controller.

Recommended Action Check if the correct country code is configured on the controller

Error Message %LWAPP-3-RD_ERR7: Invalid country code ([chars]) for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an error in the regulatory domain configured on the AP, the AP might not be able to join the controller.

Error Message %LWAPP-3-RD_ERR8: Country code ([chars]) not configured for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an error in the regulatory domain configured on the AP, the AP might not be able to join the controller.

Recommended Action Check if the correct country code is configured on the controller

Error Message %LWAPP-3-RD_ERR9: APs [hex]:[hex]:[hex]:[hex]:[hex]:[hex] country code changed from ([chars]) to ([chars])

Explanation The country code associated with the regulatory domain configured on the AP was incorrect, so the country code has been changed. The AP might not function correctly in the region it is deployed.

Recommended Action The AP is functioning correctly with the changed country code, ignore this message. If the AP is not functioning correctly, contact technical assistance.

Error Message %LWAPP-3-REBOOT_ERR2: AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] joined to the controller currently experienced a reboot earlier - ([chars] [chars] [chars])

Explanation The AP was unable to service clients because as it experienced a reboot due to the reason specified in the message.

Recommended Action Obtain the AP crash files from the controller, and collect all the message logs. Also, if the AP experienced a reboot as a result of missing heartbeat from the controller, check the network for connectivity issues. If the AP experienced a reboot because a join response was not obtained, check connectivity issues to the AP manager interface if the controller is in L3 mode, and ensure that it is reachable. After collecting the above data, contact technical assistance if necessary.

Error Message %LWAPP-6-REBOOT_INFO1: Controller initiated reboot of AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] that has currently joined the controller - ([chars] [chars])

Explanation The last reboot for the specified AP was triggered by the controller due to configuration changes on the AP that required a reboot.

Recommended Action No action is required.

Error Message %LWAPP-3-RECV_FAIL: Could not process LWAPP packet

Explanation An internal error has occurred while processing the LWAPP packet. The packet was dropped.

Error Message %LWAPP-3-REKEY_ERR: Did not receive an expected rekey message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The AP might be disconnected because the rekeying message expected from the AP was not received.

Error Message %LWAPP-3-REPLAY_ERR: Received replay error on slot [dec], WLAN ID [dec], count [dec] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The controller has received a replay error on the specified AP and WLAN.

Recommended Action Check if there is a replay attack in the network.

Error Message %LWAPP-3-ROGUE_ERR: Could not send rogue report for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, rogue information could not be sent.

Error Message %LWAPP-3-RX_ERR: Received an unexpected LWAPP packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The controller had no pending messages for this AP, so the unexpected response received was dropped. It is possible that this message arrived late at the controller.

Recommended Action No action is required.

Error Message %LWAPP-3-RX_ERR3: Received LWAPP packet with invalid sequence number (got [dec]expected [dec]) - from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An LWAPP packet sequence mismatch has occurred, and the LWAPP packet was dropped. The AP might not function as expected.

Recommended Action No action is required.

Error Message %LWAPP-3-RX_ERR4: Received invalid add mobile action ([int]) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (read index = [int])

Explanation Adding a client to the AP has failed. The client might not be serviced as expected.

Error Message %LWAPP-3-RX_ERR7: Received an invalid sequence number, [chars] ; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The LWAPP sequencing has failed for this LWAPP message, and the message was dropped. The AP might not function as expected.

Error Message %LWAPP-3-RX_ERR8: Unable to receive [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, the LWAPP message could not be processed by the controller. The AP might not function as expected.

Error Message %LWAPP-3-RX_ERR9: Received a bad sequenced [chars] message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An LWAPP packet sequence mismatch has occurred, and a LWAPP packet was dropped.The AP might not function as expected.

Error Message %LWAPP-1-SECURITY_ERR: Not advertising SSID [chars] on REAP AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because L3 security is enabled

Explanation Only H-REAP APs can advertise the specified SSID due to security issues. The system is not advertising this SSID on the AP because it is not an H-REAP AP.

Recommended Action No action is required.

Error Message %LWAPP-2-SEM_CREATE_ERR: Could not create semaphore [chars]

Explanation The system is unable to allocate a lock for handling operations on the internal database. The system might become unstable.

Error Message %LWAPP-3-SIG_ERR: No pattern in signature with id [dec], (list id = [dec]), could not encode signature

Explanation Due to an internal error, the LWAPP message between the controller and AP was not delivered. The system might not behave as expected.

Error Message %LWAPP-3-SIG_ERR1: Unable to find name for signature [dec] in list [dec] for report from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].

Explanation The controller could not process the signature report sent by the AP. Some attacks might not be detected.

Error Message %LWAPP-3-SIG_ERR10: Unable to re-enable signature processing on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The controller could not notify the AP about the new signature. The signature processing on the AP might not work as expected.

Error Message %LWAPP-3-SIG_ERR2: Unable to find description for signature [dec] in list [dec] for report from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The controller could not process the signature report sent by the AP. Some attacks might not be detected.

Error Message %LWAPP-3-SIG_ERR3: Unknown signature track information ([dec])

Explanation The controller could not process the signature report sent by the AP. Some attacks might not be detected.

Error Message %LWAPP-3-SIG_ERR4: Unknown signature report type ([dec])

Explanation The controller could not process the signature report sent by the AP. Some attacks might not be detected.

Error Message %LWAPP-3-SIG_ERR5: Could not gain exclusive access to the signature database

Explanation The controller could not send a signature list to the AP due to an internal error.

Error Message %LWAPP-3-SIG_ERR6: All signatures are disabled in the [chars] signature file.

Explanation The controller could not send signature information to the AP because all signatures are disabled.

Recommended Action Check if all signatures are disabled, and enable them if desired.

Error Message %LWAPP-3-SIG_ERR7: Unable to send toggle signature request to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The controller has failed to change the state of the signature processing on the specified AP. The signature processing on the AP might not function as expected.

Error Message %LWAPP-3-SIG_ERR8: Unable to disable signature processing on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, the signature processing on the specified AP could not be disabled. As a result, the new signature information could not be sent to the AP.

Error Message %LWAPP-3-SIG_ERR9: Error sending new signatures to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation New signature information could not be sent to the AP. The signature processing on the AP might not work as expected.

Error Message %LWAPP-4-SIG_INFO1: Signature information; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], alarm ON, [chars] sig [chars], track [chars]precedence [dec], hits [dec], slot [dec], channel [dec], most offending MAC [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Bad signature information has been detected on the specified AP.

Recommended Action No action is required.

Error Message %LWAPP-3-SLOT_ERR: AP ([chars]) has no radio cards

Explanation No radio cards were detected on the AP. The AP might not be able to service clients.

Error Message %LWAPP-2-SOCK_ERR: Error [chars] LWAPP socket

Explanation An internal error has occurred. The LWAPP subsystem could not be initialized.

Error Message %LWAPP-3-SOCK_ERR2: Socket select error ([dec])

Explanation An internal error has caused a temporary failure in a message handling process. The system is attempting to recover from this situation.

Error Message %LWAPP-3-SOCK_ERR3: Could not read from the LWAPP socket

Explanation A failure has occurred when processing an internal LWAPP message. The system might become unstable.

Error Message %LWAPP-3-SOCK_ERR4: Could not read from LWAPP socket, frame length out of bounds ([dec])

Explanation A failure has occurred when processing an internal LWAPP message. The system might become unstable.

Error Message %LWAPP-3-SSID_ERR1: Not creating SSID [chars] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because WEP 128 bit encryption is not supported on the AP

Explanation The specified WLAN was not added on the AP because 128 bit encryption is not supported on the AP.

Recommended Action Change the number of bits in the encryption, or ignore this message if the AP does not need to advertise the SSID.

Error Message %LWAPP-3-SSID_ERR2: Not creating SSID [chars] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because diagnostics channel is enabled

Explanation The specified WLAN was not added to the AP because diagnostics have been enabled on that WLAN.

Recommended Action If the WLAN needs to be enabled, disable the diagnostics channel on the WLAN.

Error Message %LWAPP-3-STATIC_IP_ERR: Configured static IP Address is not valid for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The IP address information sent by the AP is incorrect.

Error Message %LWAPP-2-TASK_CREATE_ERR: Failed to create LWAPP [chars] task

Explanation An internal error has occurred and the LWAPP subsystem could not be initialized. The APs might not be able to join the controller.

Error Message %LWAPP-3-TIME_ERR1: Unable to retrieve current time when processing [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, information about the current time on the controller could not be obtained. The AP might not function as expected.

Error Message %LWAPP-3-TIME_ERR2: Keeping connection from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in overload condition (max allowed APs [dec], current load [dec])

Explanation The controller is overloaded, but this echo request is being processed.

Recommended Action Check if another controller needs to be added to support the number of APs that are deployed.

Error Message %LWAPP-3-TIME_ERR3: Unable to retrieve time information to send AP timesync config packet

Explanation Due to an internal error, information about the controller’s time could not be sent to the AP. The AP and controller time might not be synchronized and the AP might not function as expected.

Error Message %LWAPP-3-TMR_ERR: [chars] timer count ([dec]) does not match that in the AP ([dec]) AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, this timer event was not processed. The AP might not operate as expected.

Error Message %LWAPP-3-TMR_FREE_ERR: Failed to free [chars] timer; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An internal error occurred while processing a timer. The AP might not operate as expected.

Error Message %LWAPP-3-TMR_START_ERR: Failed to start [chars] timer; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, the timer could not be triggered. The AP might not operate as expected.

Error Message %LWAPP-3-TX_ERR: Could not transmit LWAPP packet, transmission queue is full for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An LWAPP packet transmission has failed because the transmit queue has reached a maximum limit. It is possible that the response packets from the AP are not reaching the controller.

Recommended Action Check if the AP has rebooted or if it has been removed from the network. Also, check if there are connectivity issues between the AP and the controller.

Error Message %LWAPP-3-TX_ERR2: Transmission of LWAPP message failed for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, the LWAPP message could not be transmitted. The AP might not function as expected.

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 The maximum number of times that an LWAPP control packet is transmitted before declaring the AP is dead has been reached for this AP. The AP might 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. Also check if there are connectivity issues between the AP and the controller.

Error Message %LWAPP-3-TX_ERR4: Unable to retrieve AP’s ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) reachability information (VLAN identifier, port number, etc) to [chars]

Explanation An LWAPP message has been dropped because the information to send the message was not available.

Error Message %LWAPP-3-TX_ERR5: Failed to transmit [chars] to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to an internal error, an LWAPP message could not be transmitted.

Error Message %LWAPP-3-TX_ERR6: Could not send LWAPP control packet, data length ([int]) exceeds MTU ([int]) on interface [int]

Explanation Due to an incorrect length of the LWAPP message, it has been dropped.

Error Message %LWAPP-3-TX_ERR7: Could not transmit LWAPP control packet (error = [int])

Explanation Due to an internal error, an LWAPP message could not be transmitted.

Error Message %LWAPP-3-TX_ERR8: Unable to determine MTU for interface [int]

Explanation An error has occurred while obtaining the MTU for the interface. The LWAPP message has been dropped.

Error Message %LWAPP-3-UDP_PORT_ERR: Received invalid UDP port ([dec]) in the packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet

Explanation An invalid packet received from the AP has been dropped.

Error Message %LWAPP-3-UNSUPP_AP: Refusing image download request from unsupported AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The AP is not supported in the current version of the controller’s software, so the request to download the image has been ignored.

Recommended Action No action is required.

Error Message %LWAPP-3-UNSUPPORTED_TYPE: Received an invalid [chars] ([dec]): AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The information received on the controller was not understood, so the message has been dropped.

Error Message %LWAPP-3-UNSUPPORTED_TYPE2: Received an invalid [chars] ([dec])

Explanation The information received on the controller was not understood, so the message has been dropped.

Error Message %LWAPP-3-UNSUPPORTED_TYPE3: Received an invalid [chars] ([dec]) or [chars] ([dec]); AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The information received on the controller was not understood, so the message has been dropped.

Error Message %LWAPP-3-VALIDATE_ERR: Validation of [chars] failed - AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to invalid parameters sent, the validation of the LWAPP message has failed and the message has been dropped.

Error Message %LWAPP-3-VENDOR_ID_ERR: Invalid vendor identifier in vendor specific payload from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Due to invalid vendor information, the message from the AP has been dropped.

Error Message %LWAPP-3-VENDOR_SPEC_ERR: Failed decoding vendor specific payload

Explanation The message from the AP could not be processed due an error in the vendor-specific information.

Error Message %LWAPP-3-WLAN_ERR: Unable to find WLAN [dec] - [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation An internal error has occurred because the WLAN information could not be found. The specified operation could not be performed.

Error Message %LWAPP-3-WLAN_ERR2: Unable to find WLAN [dec] to be deleted; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The requested WLAN does not exist in the database, so the request to delete has been ignored.

Error Message %LWAPP-3-WLAN_ERR4: Unable to add WLAN on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - max limit reached

Explanation An invalid WLAN ID has been received because the controller could not configure the WLAN on the AP.

Error Message %LWAPP-3-WLAN_ERR5: Unable to find WLAN [dec] to be updated on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The requested WLAN does not exist in the database, so the request to update the information on the AP has been ignored.

Error Message %LWAPP-6-WLAN_STATUS_ERR: [chars] [dec] [chars] [dec] [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The operation attempted on the slot for the WLAN was not necessary, because the AP was already in that state, so this message has been ignored.

Recommended Action No action is required.

Error Message %LWAPP-6-CAPWAP_CREATED_AP: Discarding LWAPP [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] since AP entry is created in CAPWAP

Explanation The message has been received in LWAPP from the AP, but the AP entry was created by CAPWAP. The system is ignoring the message.

Explanation No action is required.

Error Message %LWAPP-6-CAPWAP_SUPP_VER: Discarding [chars] in LWAPP from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] supporting CAPWAP

Explanation The message was received in LWAPP from an AP that supports CAPWAP. This condition might be normal. The AP will join the controller in CAPWAP after the maximum number of retries in LWAPP.

Recommended Action No action is required.

Error Message %LWAPP-4-MSGTAG098: Mesh AP [chars] unable to support the configured VLAN [dec].

Explanation The maximum limit on the number of VLANs has been exceeded on the specified AP or in any upstream AP.

Recommended Action Check the number of configured VLANs. Remove unwanted or unused VLANs.

Error Message %LWAPP-2-SPAMSEND: Sending through spam instead of capwap; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation The system could not transmit the LWAPP message because it could not be encrypted. The AP might not function as expected.

Error Message %LWAPP-0-RADIUS_ERR: The system could not send join reply, AP authorization failed; AP:%02x:%02x:%02x:%02x:%02x:%02x

Explanation The join reply has not been sent to the AP because AP authentication failed.

Recommended Action Check the AP credentials on the RADIUS server or check if the local MAC filtering table is configured. Also check if RADIUS servers are configured and are reachable.

Bias-Free Language

Book Title

Cisco Wireless LAN Controller System Message Guide, Release 8.0

Chapter Title

LRADSIM and LWAPP System Messages

Results

Chapter: LRADSIM and LWAPP System Messages

LRADSIM and LWAPP System Messages

LRADSIM Messages

LWAPP Messages

Was this Document Helpful?

Contact Cisco