Current Position:Home > Removing WLCs from list in NVRAM for deployed LAPs

Removing WLCs from list in NVRAM for deployed LAPs

Update:11-30Source: network consolidation
Advertisement
Hi,
Here is a question, which I really would like to have an answer on. I have been searching for this, and can not find any on this. I am up to the point where I start to think it is simply not possible.
I would like to remove all existing WLCs from NVRAM in my LAPs. Simple, you may think, just boot it without registering and perform the command "clear lwapp private-config", and allthough this is through and I'm sure it will work, it would require me to organize about 300 LAPs to be shipped back to me so I can console into it and perform the command.
Another thing I thought of was clearing the config from WCS, but I found this only clears the config and not the list of previously joined controllers stored in NVRAM.
The background of my request is that we started out with WLCs back in code 3.1, and there it was recommended to have one mobility group if you wanted to have an anchor guest controller.
Today, we are running 5.2 and the number of WLCs we have in place is 21 and growing.
I believe that since we went to 4.2 we started having problems with LAPs sometimes registering to the wrong controller.
We have been troubelshooting this a lot, and with the current discoverey mechanism, where the LWAPP discovery respons includes all controllers in the mobility group, and aso the previously joined/learned controlelrs, we do understand why it happens.
So, the new updated design is to separate into different mobility groups and still make the necessary relationships to the guest anchor controller in the old mobility group. Works all fine. However, it did not resolve the problem of LAPs sometimes registering to the wrong controller.
And it makes sense if you read the documents, the LAP has learned and stored about all the WLCs in NVRAM, so it can select any, if for some reason the primary fails (it only happens ofcourse when the primary fails).
So, to ensure it will no longer rehome to another controller, I do need to remove all previuosly learned WLCs from NVRAM, but can not seem to find a way to do this without having console access, and I have about 300 LAPs in different countries, over appr. 30 locations.....
Help!!!!!
Thanks in advance for your thoughts on this,
Leo

The Best Answer

Advertisement
Hi,
Are you convinced this removes stored information in NVRAM for previously joined controllers. So far, my understanding was that only a factry default reset would do so, not the clear all config.
I do understand the clear all config does remove entries for primary, secondary and tertiary controllers but I'm still in doubt if that would ensure the AP will not wander to previously joined controllers.
Kind regards,
Leo
  • Removing WLCs from list in NVRAM for deployed LAPs Update:11-30

    Hi, Here is a question, which I really would like to have an answer on. I have been searching for this, and can not find any on this. I am up to the point where I start to think it is simply not possible. I would like to remove all existing WLCs from

  • SQL blocking during removal of report server from Scale-out-Deployment Update:10-11

    I recently removed a 2012 reporting service instance from the Reporting Service Scale-out-Deployment. After I removed the server, there was a lot of blocking  on the report DB for about 30 minutes. My report DB is on the same SQL instance as my TFS d

  • Initial AP registration on a 8510 WLC HA-SKU and N+1 deployment Update:10-11

    Hi, We have several 8510 controllers and one of them needs to be configured as HA SKU for N+1 deployment. I am testing the scenario with two controllers right now, so I have the primary and the secondary controller configured as part of the same Mobi

  • Cisco LAP 2602 can not join Virtual WLC Update:11-30

    dear all,  i just install Virtual WLC and i remove WLC 2504 , i install & configured it , but LAP can not join. it was work fine with WLC 2504. i used the same network topology with the old WLC. i receive this error logs. *spamApTask4: Feb 04 06:01:3

  • EPMA Validation Error: dimension removed or deleted since first deployment Update:11-30

    Dear experts, Our deployment is on EPMA and we were able to successfully deploy the Planning application before. Then we tried to update the dimension by loading UDA to each members, after which, we hit this error at validation: Error : The xxxx dime

  • Report Generation broken after deployment - Excel Set Cell Color and Border.vi Update:10-11

    Upon deployment, the Excel Set Cell Color and Border.vi became broken.  After installing LV2010 SP1 to view the VIs in the deployment, I noticed that in the second case structure where the code draws the border using the BorderAround invoke node, the

  • Deployment error using CMS (Component is not a SCA but a SDA) Update:10-11

    I haven't seen this message before on the forum so I thought I'd see if anyone else has run into this.  My landscape is as follows: Runtime System: NW04 SP14 JDI System:  NW04 SP19 SAP SCA plugins:  NW04 SP14 Application:  Standard web dynpro with 2

  • Exploded deployment doesn't work in Weblogic 8.1 Update:10-11

    Hi I have a very weird problem. I am trying to deploy my apllication in Weblogic 8.1 in exploded format.Well problem is when i deploy it ,on server startup Weblogic doesn't deploy it automatically way its mentioned in the release.txt and also way it

  • Requesting standard basic build and deployment requirements Update:10-11

    Operational Data:  Microsoft visual Studio 2008 Visual Basic Windows Forms Application Crystal Reports 12.0.2000.0 Deploying on Windows Server 2003, Standard Edition I have been having difficulty deploying a WindowsForms CrystalReports application th

  • Web service deployment error - CE 7.2(CAF) Update:10-11

    I am getting deployment error for CE 7.2 CAF application. it was working fine. Suddenly with out any changes in the code or the web service, I am not able deploy the application. if I remove the modeled service , it is successfully deployed. But mode