Lightweight AP Connectivity Problem

Unanswered Question
Dec 4th, 2007
User Badges:
  • Silver, 250 points or more

Hi Guys (& Ladies?),

I have a 4404 running, with a number of 1130 AG Access Points. APs are in different subnets, and were provisioned using DHCP - this all works fine.

Problems begin if I reboot / lose the Wireless LAN Controller. The APs correctly identify they're alone, and begin the re-connection / discovery process as expected.

From the AP perspective, it is sending messages to the correct IP / Port of the WLC, but never receives a response. (FILE: AP Port Span.pcap, the specific AP being spanned is, the WLC Mgmt Interface is

From the WLC perspective, the LWAPP Discovery messages are received, but the WLC believes they contain error(s) ("UNKNOWN IE 58" and "UNKNOWN IE 99"), and so never responds. (FILE: "WLC debug lwapp packet.txt")

Currently, the only way to recover from the situation is to pull the power on the Access Points and reboot them (not easy as some APs on Power Injectors at remote sites).

So the question is, how do I fix this problem? :o)

Cheers All,


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Richard Atkin Mon, 12/10/2007 - 01:07
User Badges:
  • Silver, 250 points or more

Hi All,

Just so you know, the UNKNOWN IE messages are normal, and the numbers correspond with the provisioning type that was used.

In the end, the problem was caused by a problem on a Firewall where Stateful UDP wasn't configured properly, and so if a response (from WLC to AP) was recieved that was a fragmented UDP packet, it would drop the the whole packet (ie, both Fragments).

Some work on the Firewall fixed the problem.

jesse.fields Fri, 02/29/2008 - 13:32
User Badges:

I would be interested to learn what the fix to this issue is. I am currently experiencing the same errors but with a new 1130AG at a remote site. I get the UNKNOWN 58 then the UNKNOWN 99 messages on the controller. I have tested with another AP in different areas of my network with no problems. I have verified there are no ports being blocked beteen the AP's network and the controller.



This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode