LWAPP AP1000 restart repeated near every 1 minute

Unanswered Question
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
john.preves Fri, 11/09/2007 - 22:31
User Badges:
  • Silver, 250 points or more

do you still have addresses left? I have been burnt by that a couple of times when I thought the scope was built only to find it had 8 addresses defined and couldn't figure out why any subsequent AP's wouldn't connect.

john.preves Fri, 11/09/2007 - 22:34
User Badges:
  • Silver, 250 points or more

also you said the option 43 stuff was correct but I would still double check the IP helper address on that vlan.


I would think about using DNS as well or static IP's for the AP's

john.preves Sun, 11/11/2007 - 05:48
User Badges:
  • Silver, 250 points or more

I'm trying to understand your question, but if you are defining 'reserved' as reserved for a static address in the same vlan as your active DHCP scope, then you only need the one for the AP.


you still need addresses for the clients, which you know already, but you should check to ensure that the scope is built and enough addresses are active and available

jakew Sun, 11/11/2007 - 07:55
User Badges:
  • Silver, 250 points or more

I assume all the APs are AP1000s right? If the AP is restarting about every minute, that indicates that there's an error somewhere in the LWAPP state machine between discovery and run states.


I'd advise you to walk through the LWAPP state machine to see where it breaks. First check that the LWAPP Discover is working correctly. The check the LWAPP Join process. You can do this via "debug lwapp events enable" on the CLI. You should see:


LWAPP Discovery Request from AP

WLC sending LWAPP Discovery response


then...

LWAPP Join Request from AP

WLC sending LWAPP Join response to AP


If you get this far, then the AP is probably running into an error downloading code or the config from the WLC.


You should also check to see how much latency you have in the WAN link...


All that being said, are you sure you don't have a bad AP?



dennischolmes Sun, 11/11/2007 - 14:48
User Badges:
  • Gold, 750 points or more

To understand these processes that Jake has given you I am uploading a couple of files. Look these over and follow Jake's troubleshooting. Refer to LWAPP debugs sections of the configuration guide for your version of code.



Actions

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