Weird AP join issue

Unanswered Question
Nov 16th, 2009
User Badges:

I have a strange one. If I take a new access point to one of our remote and plug it in, it will not join the controllers at the home location (running latest 4.2) but it will eventually find one of our 2106 controllers running 5.1. If I take an access point out and plug it into the network and have it join the controller before it is shipped (but with no configuration changes) it will work just fine. These are new 1130 series access points (factory LWAPP). I had a local tech look at one and he said that it is getting the no join response message, but from the controller debugs I can see the that it is getting a response from the join request. The WAN is a 3mb connection with a an MTU of approximately 1475. The latency is sub 100 MS round trip. The access point is finding the controllers no problem. Clocks are correct on the controller and the 1130's have the MIC so it shouldn't be a problem with that. Main location controllers are 4404's with LAG on the interfaces. One controller has 37 access points connected while the other has 60.

Just to restate. I can take one of the access points that isn't functioning correctly at a remote and if I plug it in to the network at HQ and let it flash up it works just fine at the remote.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Leo Laohoo Mon, 11/16/2009 - 14:09
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

Did you configure HREAP?

Can the LAP ping the management IP address of the WLC (running 4.X)? If so, console into the AP and in enable mode type the command "lwap ap controller ip address ".

Hope this helps.

SHANNON WYATT Mon, 11/16/2009 - 15:03
User Badges:

Not yet, as I can't manage the access point yet. I can ping the management IP address.

Like I was saying, I can take one of these problem access points, bring it back to hq and plug it in, after it upgrades to current code send it back out and it comes up no problem.


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