changing LAP between locations

Answered Question
Apr 14th, 2010

Have came accross a pretty odd scenario - a LAP has joined WLC1 on location 1 with no problem - client needs to change this LAP over to location 2 where it should join WLC2 - location 2 has more LAPs that have already been associated with WLC2 with no problem however this just introduced LAP would not join WLC2 but keep on joining WLC1.   Option 43 settings with DHCP have been set up correctly - wouldn't this LAP join WLC2 when is moved to location 2 automatically using DHCP Option 43?  Does LAP need to be converted to autonomous so it would not keep joining WLC1?  Tried to reset configuration on LAP through WLC1's GUI as well as WLC's CLI - even though LAP configuration is reset to factury defaults, AP reboots and it keeps on joining WLC1 - not able to change anything on LAP through CLI either as AP is blocked (ERROR!!! Command is disabled) as soon as it reboots and joins WLC1.

Any input on the Cisco Support Community out there???

Correct Answer by Leo Laohoo about 6 years 10 months ago

You are correct, however, if you put the details of WLC2 (name and management IP address) into the Primary Controller field, the LAP will immediately go and join WLC2.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Leo Laohoo Wed, 04/14/2010 - 02:18

You can change it by going to the WLC where the LAP has joined.  Go to All APs > Details > Click on the AP of your choice then go to the High Availability tab.  Enter the WLC name and management IP address.

Don't forget to rate our posts.  Thank you.

KRIS GJ Wed, 04/14/2010 - 17:30

Thanks for the reply but that adds a WLC to the LAP as a backup.  Issue is that LAP needs to join another WLC (WLC2) and not the current one that keeps on joining (WLC1) - by adding a WLC on the High Availability tab for the LAP, it adds a secondary or backup WLC in case the primary is not found - by doing this LAP keeps on joining WLC1 which joined first on location 1 and not WLC2 on location 2 which is the WLC it should be joining - pretty much - LAP should automatically join the appropriate WLC depending on DHCP Option 43 but that is not working for some reason - LAP should automatically DHCP an IP address and according to this join the respective WLC - that is not working but would need to know if there is anything that needs to be done prior moving a LAP from location 1 to location 2 - any input on this?

Correct Answer
Leo Laohoo Wed, 04/14/2010 - 18:51

You are correct, however, if you put the details of WLC2 (name and management IP address) into the Primary Controller field, the LAP will immediately go and join WLC2.

Actions

This Discussion

Related Content

 

 

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