topic Discovery response message header encapsulation failed in Wireless

Discovery response message header encapsulation failed

Scott_O'Brien — Sun, 04 Jul 2021 03:50:38 GMT

Hey All,

i get this from an AP any ideas why this may be happening?

Last Error Occurred	Failed to send Lwapp discovery response
Last Error Occurred Reason	Discovery response message header encapsulation failed
Last Join Error Timestamp	Sep 19 15:56:36.771

running WLC version

7.0.98.0

Discovery response message header encapsulation failed

Msmith401 — Thu, 29 Nov 2012 17:44:53 GMT

I'm running into the same problem. Have you figured out the cause? Thanks!

Discovery response message header encapsulation failed

Saravanan Lakshmanan — Fri, 30 Nov 2012 23:30:12 GMT

what's the AP model used?

either unsupported code or AP model used.

Discovery response message header encapsulation failed

Msmith401 — Fri, 30 Nov 2012 23:41:56 GMT

It's a 1231G. It's on the list of supported APs with WLC code 7.0.x.

I'm still stumped.

Discovery response message header encapsulation failed

Saravanan Lakshmanan — Fri, 30 Nov 2012 23:43:42 GMT

do you've firewall between AP and WLC.

how AP and WLC are connected?

are AP and WLC on same vlan?

get debug capwap/lwapp from AP.

Discovery response message header encapsulation failed

Msmith401 — Fri, 30 Nov 2012 23:48:32 GMT

The only firewall is outside of the core. I tried placing the AP on an AP VLAN with other working APs and also on the controller VLAN, neither worked. I don't know if I can run debugs on the AP becuase it's running the recovery image hosted at http://www.cisco.com/cisco/pub/software/portal/select.html?&mdfid=277026213&flowid=7580&softwareid=280775090 and its command set is very limited.

Discovery response message header encapsulation failed

Msmith401 — Fri, 30 Nov 2012 23:53:31 GMT

I got this off the controller...

(Cisco Controller) >show ap join stats summary 00:13:19:c8:f9:b6

Is the AP currently connected to controller................ No

Time at which the AP joined this controller last time...... Not applicable

Type of error that occurred last........................... Failed to send Lwapp discovery response

Reason for error that occurred last........................ Discovery response message header encapsulation failed

Time at which the last join error occurred................. Nov 29 17:23:35.793

(Cisco Controller) >show ap join stats det 00:13:19:c8:f9:b6

Discovery phase statistics

- Discovery requests received.............................. 94

- Successful discovery responses sent...................... 88

- Unsuccessful discovery request processing................ 100

- Reason for last unsuccessful discovery attempt........... Discovery response message header encapsulation failed

- Time at last successful discovery attempt................ Nov 29 17:19:01.162

- Time at last unsuccessful discovery attempt.............. Nov 29 17:23:35.793

Join phase statistics

- Join requests received................................... 0

- Successful join responses sent........................... 0

- Unsuccessful join request processing..................... 0

- Reason for last unsuccessful join attempt................ Not applicable

- Time at last successful join attempt..................... Not applicable

- Time at last unsuccessful join attempt................... Not applicable

Configuration phase statistics

- Configuration requests received.......................... 0

- Successful configuration responses sent.................. 0

- Unsuccessful configuration request processing............ 0

- Reason for last unsuccessful configuration attempt....... Not applicable

- Time at last successful configuration attempt............ Not applicable

--More-- or (q)uit

- Time at last unsuccessful configuration attempt.......... Not applicable

Last AP message decryption failure details

- Reason for last message decryption failure............... Not applicable

Last AP disconnect details

- Reason for last AP connection failure.................... Not applicable

- Last AP disconnect reason................................ Not applicable

Last join error summary

- Type of error that occurred last......................... Failed to send Lwapp discovery response

- Reason for error that occurred last...................... Discovery response message header encapsulation failed

- Time at which the last join error occurred............... Nov 29 17:23:35.793

AP disconnect details

- Reason for last AP connection failure.................... Not applicable

Ethernet Mac : 00:00:00:00:00:00 Ip Address : 0.0.0.0

(Cisco Controller) >show ap join stats summary 00:13:19:c8:f9:b6

Is the AP currently connected to controller................ No

Time at which the AP joined this controller last time...... Not applicable

Type of error that occurred last........................... Failed to send Lwapp discovery response

Reason for error that occurred last........................ Discovery response message header encapsulation failed

Time at which the last join error occurred................. Nov 29 17:23:35.793

(Cisco Controller) >show ap join stats det 00:13:19:c8:f9:b6

Discovery phase statistics

- Discovery requests received.............................. 94

- Successful discovery responses sent...................... 88

- Unsuccessful discovery request processing................ 100

- Reason for last unsuccessful discovery attempt........... Discovery response message header encapsulation failed

- Time at last successful discovery attempt................ Nov 29 17:19:01.162

- Time at last unsuccessful discovery attempt.............. Nov 29 17:23:35.793

Join phase statistics

- Join requests received................................... 0

- Successful join responses sent........................... 0

- Unsuccessful join request processing..................... 0

- Reason for last unsuccessful join attempt................ Not applicable

- Time at last successful join attempt..................... Not applicable

- Time at last unsuccessful join attempt................... Not applicable

Configuration phase statistics

- Configuration requests received.......................... 0

- Successful configuration responses sent.................. 0

- Unsuccessful configuration request processing............ 0

- Reason for last unsuccessful configuration attempt....... Not applicable

- Time at last successful configuration attempt............ Not applicable

--More-- or (q)uit

- Time at last unsuccessful configuration attempt.......... Not applicable

Last AP message decryption failure details

- Reason for last message decryption failure............... Not applicable

Last AP disconnect details

- Reason for last AP connection failure.................... Not applicable

- Last AP disconnect reason................................ Not applicable

Last join error summary

- Type of error that occurred last......................... Failed to send Lwapp discovery response

- Reason for error that occurred last...................... Discovery response message header encapsulation failed

- Time at which the last join error occurred............... Nov 29 17:23:35.793

AP disconnect details

- Reason for last AP connection failure.................... Not applicable

Ethernet Mac : 00:00:00:00:00:00 Ip Address : 0.0.0.0

Discovery response message header encapsulation failed

Saravanan Lakshmanan — Sat, 01 Dec 2012 00:02:13 GMT

seem to be an cable issue, try swapping cable.

console into AP and run these debugs.

AP#debug lwapp console cli

AP#debug lwapp client event

AP#debug lwapp client error

AP#debug capwap client event

AP#debug capwap client error

Re: Discovery response message header encapsulation failed

Msmith401 — Mon, 03 Dec 2012 20:19:26 GMT

This is what it tells me:

flashfs[0]: 4 files, 2 directories

flashfs[0]: 0 orphaned files, 0 orphaned directories

flashfs[0]: Total bytes: 7741440

flashfs[0]: Bytes used: 1755648

flashfs[0]: Bytes available: 5985792

flashfs[0]: flashfs fsck took 9 seconds.

Reading cookie from flash parameter block...done.

Base ethernet MAC Address: 00:13:19:c8:f9:b6

Initializing ethernet port 0...

Reset ethernet port 0...

Reset done!

ethernet link up, 100 mbs, full-duplex

Ethernet port 0 initialized: link is up

Loading "flash:/c1200-rcvk9w8-mx/c1200-rcvk9w8-mx"...################################################################################################################################################################################

File "flash:/c1200-rcvk9w8-mx/c1200-rcvk9w8-mx" uncompressed and installed, entry point: 0x3000

executing...

Restricted Rights Legend

Use, duplication, or disclosure by the Government is

subject to restrictions as set forth in subparagraph

Rights clause at FAR sec. 52.227-19 and subparagraph

Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.

170 West Tasman Drive

San Jose, California 95134-1706

Cisco IOS Software, C1200 Software (C1200-RCVK9W8-M), Version 12.3(7)JX9, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Compiled Tue 17-Jul-07 00:44 by tinhuang

Image text-base: 0x00003000, data-base: 0x0033DA20

Initializing flashfs...

flashfs[1]: 4 files, 2 directories

flashfs[1]: 0 orphaned files, 0 orphaned directories

flashfs[1]: Total bytes: 7741440

flashfs[1]: Bytes used: 1755648

flashfs[1]: Bytes available: 5985792

flashfs[1]: flashfs fsck took 2 seconds.

flashfs[1]: Initialization complete....done Initializing flashfs.

cisco AIR-AP1231G-A-K9 (PowerPC405GP) processor (revision B0) with 14838K/1536K bytes of memory.

Processor board ID FTX0907J0E8

PowerPC405GP CPU at 196Mhz, revision number 0x0145

Last reset from power-on

1 FastEthernet interface

32K bytes of flash-simulated non-volatile configuration memory.

Base ethernet MAC Address: 00:13:19:C8:F9:B6

Part Number : 73-8704-08

PCA Assembly Number : 800-23211-09

PCA Revision Number : A0

PCB Serial Number : FOC09024TMB

Top Assembly Part Number : 800-23304-08

Top Assembly Serial Number : FTX0907J0E8

Top Revision Number : A0

Product/Model Number : AIR-AP1231G-A-K9

Press RETURN to get started!

*Mar 1 00:00:04.402: %SYS-5-RESTART: System restarted --

Cisco IOS Software, C1200 Software (C1200-RCVK9W8-M), Version 12.3(7)JX9, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Compiled Tue 17-Jul-07 00:44 by tinhuang

*Mar 1 00:00:05.380: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up

*Mar 1 00:00:06.380: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up

ap>

ap>en

ap#debug lwapp console cli

LWAPP console CLI allow/disallow debugging is on

ap#debug lwapp client event

LWAPP Client EVENT display debugging is on

ap#debug lwapp client error

LWAPP Client ERROR display debugging is on

ap#debug capwap client event

% Invalid input detected at '^' marker.

ap#debug capwap client error

% Invalid input detected at '^' marker.

ap#

*Mar 1 00:00:23.416: LWAPP_CLIENT_EVENT: lwapp_ip_address_change - ADDING IP 10.0.0.1, 255.255.255.0; resolvemethod 1, ip_dhcp_addr 0

*Mar 1 00:00:23.419: LWAPP_CLIENT_EVENT: lwapp_set_ip_address - Seting Static IP 10.0.0.1 255.255.255.0 on FastEthernet0

*Mar 1 00:00:23.419: LWAPP_CLIENT_EVENT: lwapp_set_ip_address - Seting Default Gateway IP to 10.0.0.2

*Mar 1 00:00:23.425: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:00:23.425: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY

*Mar 1 00:00:23.431: LWAPP_CLIENT_EVENT: parse_lwapp_config: hostname AP0013.19c8.f9b6

end

*Mar 1 00:00:23.447: LWAPP_CLIENT_EVENT: lwapp_crypto_init_mic_keys_and_certs : MIC not present

*Mar 1 00:00:23.453: LWAPP_CLIENT_EVENT: lwapp_crypto_init_ssc_keys_and_certs found key(1) label CISCO_IOS_SSC_Keys

*Mar 1 00:00:23.458: LWAPP_CLIENT_EVENT: lwapp_crypto_init_ssc_keys_and_certs Certs Keylen 294

*Mar 1 00:00:23.459: LWAPP_CLIENT_EVENT: lwapp_crypto_init_ssc_keys_and_certs Public Key Match Found CISCO_IOS_SSC_Keys

*Mar 1 00:00:24.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:00:34.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:00:34.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:00:44.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:00:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:00:54.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:00:54.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:01:04.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:01:04.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:01:14.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:01:14.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:01:24.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:01:24.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:01:34.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:01:34.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:01:44.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:01:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:01:54.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:01:54.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:02:04.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:02:04.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:02:04.389: LWAPP_CLIENT_EVENT: lwapp_check_image_good: image is good now

*Mar 1 00:02:14.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:02:14.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

AP0013.19c8.f9b6#

*Mar 1 00:02:24.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:02:24.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:02:34.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:02:34.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:02:44.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:02:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:02:54.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:02:54.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:03:04.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:03:04.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:03:14.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:03:14.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:03:24.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:03:24.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:03:34.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:03:34.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:03:44.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:03:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:03:44.036: LWAPP_CLIENT_EVENT: spamStartDhcp - AP IP FALLBACK TO DHCP

Translating "CISCO-LWAPP-CONTROLLER.org.org"...domain server (10.1.0.254)

*Mar 1 00:03:53.074: LWAPP_CLIENT_EVENT: lwapp_ip_address_change - ADDING IP 10.0.1.254, 255.255.255.0; resolvemethod A, ip_dhcp_addr 1

*Mar 1 00:03:53.181: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.0.1.254, mask 255.255.255.0, hostname AP0013.19c8.f9b6

[OK]

*Mar 1 00:03:53.181: LWAPP_CLIENT_EVENT: lwapp_ip_address_change - ADDING IP 10.0.1.254, 255.255.255.0; resolvemethod A, ip_dhcp_addr 1

*Mar 1 00:03:54.057: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:03:54.057: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found

*Mar 1 00:03:54.183: LWAPP_CLIENT_EVENT: lwapp_name_lookup - add (0) 10.0.254.253

*Mar 1 00:03:54.183: LWAPP_CLIENT_EVENT: lwapp_name_lookup - add (1) 10.0.254.254

*Mar 1 00:04:04.057: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR

*Mar 1 00:04:04.057: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway NOT found

*Mar 1 00:04:15.063: %LWAPP-5-CHANGED: LWAPP changed state to JOIN

*Mar 1 00:04:20.063: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response

*Mar 1 00:04:20.063: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.

*Mar 1 00:04:20.063: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.

*Mar 1 00:04:20.064: %LWAPP-5-CHANGED: LWAPP changed state to DOWN

And this is on the controller:

(Cisco Controller) >show ap join stats summary 00:13:19:c8:f9:b6

Is the AP currently connected to controller................ No

Time at which the AP joined this controller last time...... Not applicable

Type of error that occurred last........................... Failed to send Lwapp discovery response

Reason for error that occurred last........................ Discovery response message header encapsulation failed

Time at which the last join error occurred................. Nov 29 17:23:35.793

(Cisco Controller) >show ap join stats detailed 00:13:19:c8:f9:b6

Discovery phase statistics

- Discovery requests received.............................. 97

- Successful discovery responses sent...................... 94

- Unsuccessful discovery request processing................ 100

- Reason for last unsuccessful discovery attempt........... Discovery response message header encapsulation failed

- Time at last successful discovery attempt................ Dec 03 20:07:22.259

- Time at last unsuccessful discovery attempt.............. Nov 29 17:23:35.793

Join phase statistics

- Join requests received................................... 0

- Successful join responses sent........................... 0

- Unsuccessful join request processing..................... 0

- Reason for last unsuccessful join attempt................ Not applicable

- Time at last successful join attempt..................... Not applicable

- Time at last unsuccessful join attempt................... Not applicable

Configuration phase statistics

- Configuration requests received.......................... 0

- Successful configuration responses sent.................. 0

- Unsuccessful configuration request processing............ 0

- Reason for last unsuccessful configuration attempt....... Not applicable

- Time at last successful configuration attempt............ Not applicable

--More-- or (q)uit

- Time at last unsuccessful configuration attempt.......... Not applicable

Last AP message decryption failure details

- Reason for last message decryption failure............... Not applicable

Last AP disconnect details

- Reason for last AP connection failure.................... Not applicable

- Last AP disconnect reason................................ Not applicable

Last join error summary

- Type of error that occurred last......................... Failed to send Lwapp discovery response

- Reason for error that occurred last...................... Discovery response message header encapsulation failed

- Time at which the last join error occurred............... Nov 29 17:23:35.793

AP disconnect details

- Reason for last AP connection failure.................... Not applicable

Ethernet Mac : 00:00:00:00:00:00 Ip Address : 10.0.1.254

(Cisco Controller) >

Discovery response message header encapsulation failed

Saravanan Lakshmanan — Mon, 03 Dec 2012 20:28:21 GMT

for the ssc cert issue, did you add the key to wlc.

http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a00806a426c.shtml

it doesn't look like the AP and WLC's management/ap manager on same network.

Discovery response message header encapsulation failed

Msmith401 — Mon, 03 Dec 2012 20:40:31 GMT

I've used the debug pm pki command on this AP and in the past, but it doesn't show anything for this AP.

The WLC doesn't have an individual AP manager interface. The management and AP manager interfaces are merged into the managemant interface. It has the option enabled called "Dynamic AP Management". The management interface is set untagged. The native VLAN contains the subnet of the management interface.

Re: Discovery response message header encapsulation failed

Msmith401 — Tue, 04 Dec 2012 21:48:01 GMT

Is it possible that the recvoery code is the problem? I have other APs like this that work but they run C1200-k9w8-mx.124-23c.JA4.

The ones that don't work are running the recovery image from cisco.com c1200-rcvk9w8-mx.

I tried to TFTP the code off a working AP which worked. But when I tried to TFTP it onto the bad AP, it fails with a checksum error.