Can't change LWAP association to different Controller

Unanswered Question
Apr 17th, 2008

I have a customer with LWAPs that are associated to a specific controller. They want to change the controller it's associated to, but it keeps returning to the original controller. They've tried assigning the Primary controller via WCS/WiSM, resetting the AP to default config, then resetting the LWAP.....the LWAP still associates with original controller.

A new LWAP out of the box goes to the correct controller with no problem. So, there is still something in the previously assigned controller to an LWAP that is not being cleared. Can someone tell how we can do this?

Any help would be appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
rob.huffman Thu, 04/17/2008 - 10:39

Hi Richard,

If these are upgraded AP's you may have to add the AP Auth list to all controllers;

Configuring an Access Point Authorization Template

Follow these steps to add an access point authorization template or make changes to an existing template. These templates are devised for Cisco 11xx/12xx series access points converted from IOS to LWAPP or for 1030 access points connecting in bridge mode.

Step 1 Choose Configure > Controller Templates.

Step 2 From the Security selections in the left sidebar menu, choose AP authorization.

Step 3 If you want to add a new template, choose Add Template from the Select a command drop-down menu and click GO. To make modifications to an existing template, click a MAC address in the AP Base Radio MAC column. The AP Authorization Template appears (see Figure 9-12), and the number of controllers the template is applied to automatically populates.

Step 4 Select the Import from File check box if you want to import a file containing access point MAC addresses.

Note You can only import a .csv file. Any other file formats are not supported.

Step 5 Enter the file path from where you want to import the file.

Step 6 Click Save.

From this doc;

Hope this helps!


rlortiz Thu, 04/17/2008 - 12:57


Good info, but the 1242 Access Points have not been upgraded.

So, still looking for some more input on this.



rob.huffman Fri, 04/18/2008 - 05:34

Hi Richard,

Sorry about that :(

You could try these two methods;

Configuring Static Parameters to Register the Access Point to a Controller

Using the password that the controller sent to the access point, enter into EXEC mode on the access point console. When the access point is running LWAPP or a recovery IOS image, you can configure the static IP address on the access point, the IP address on the controller, the access point hostname, and the default gateway IP address by entering these commands:

•lwapp ap ip address ip-addr subnet-mask

•lwapp ap controller ip address ip-addr

•lwapp ap hostname ap-hostname

•lwapp ap ip default-gateway ip-addr

The access point with a recovery IOS image uses the static controller IP address to register to the specified controller and download the current LWAPP image. After the access point successfully registers to the controller, it receives configurations from the controller. The access point static hostname and the IP address of the controller are deleted from the access point configuration file. However, the access point static IP address and the netmask and the default gateway IP address are not deleted.

When the access point is running a recovery IOS image, the commands to configure the static IP address on the access point, the IP address on the controller, the access point hostname, and the default gateway IP address are always enabled.

These commands are disabled in the following cases:

•When the access point is running an LWAPP image.

•When the access point has an LWAPP configuration file in NVRAM.

•When the access point is in REGISTERED state with the controller.

The access point console displays the following error message if you enter any of these commands when they are disabled:

"ERROR!!! Command is disabled."

Using Master Controller Mode;

But I think you will like the ideas here better (from Lynne, Dan and Richard);

Hope this helps!


imobiwan Tue, 05/13/2008 - 12:07

I had the same problem until I set up all the vedor specific DHCP options pointing option 43 to the new controller and THEN going into the WCS and and resetting the Access Point to default settings. After the reboot the access point found the correct controller through DHCP.

I experienced the exact same behavior and it turned out to be as related to the mobility group TABLE (not just the mobility group name field) not being populated in each of the controllers with entries for each of the other controllers.

Once the mobility group table was correctly populated, the controllers were aware of each other and the LWAPs would quickly connect to the desired controller upon changing their PRIMARY CONTROLLER setting.

For more detail on this, please go to this link to an earlier forum posting:

I hope this helps,

- John

(Please remember to rate helpful posts)


This Discussion



Trending Topics - Security & Network