WLC 8540 Design

[Oron Yaniv]

Hi,

today we have two WLC 8540 in HA topology, with 8.2 software, we cannot upgrade the software because we have old APs (1142,2600,3600 etc,) as long as new APs (3800/3700). second, we consider buying a new 9100 AP series, but those APs supported by the  8540 from version 8.9.

we decided to install new  WLC8540 - stand alone, and we will migrate old APs to the new 8540, that's will allow us to upgrade the 8540 HA.

i thought to install the new 8540 as stand-alone and to stretch the  L2 between the two WLC.

the L3/GW of the clients reside on the L3 switch the 8540 connected to.

which installation we can deploy? i have no previous knowledge, so i will glad for a suggestion whats the best deployment?


thanks,

[Oron Yaniv]

Hi,

today we have two WLC 8540 in HA topology, with 8.2 software, we cannot upgrade the software because we have old APs (1142,2600,3600 etc,) as long as new APs (3800/3700). second, we consider buying a new 9100 AP series, but those APs supported by the  8540 from version 8.9.

we decided to install new  WLC8540 - stand alone, and we will migrate old APs to the new 8540, that's will allow us to upgrade the 8540 HA.

i thought to install the new 8540 as stand-alone and to stretch the  L2 between the two WLC.

the L3/GW of the clients reside on the L3 switch the 8540 connected to.

which installation we can deploy? i have no previous knowledge, so i will glad for a suggestion whats the best deployment?


thanks,

[balaji.bandi]

If you have legacy AP, which not support latest code ( you need to mitigate this issue, either upgrade - as you mentioned upgrading to 9100) - if they need to be in the network, then you need to maintain old version of code in the network.

If all the devices(AP) able to support in the matrix the version you looking to go new version.

your approach make sense.

1, Deploy new WLC controller, Move a couple of AP and test it ( this is very very important notes for you)

2. Wait for 2-4weeks and users tested the AP move to a new Controller with a new WLC Code.

3. Move the Rest of the AP to a new controller.

4. (Do not remove or upgrade old controller, until all stable working at least 3-4 weeks (personally seen some issues around) - even though tested, new code broke the client's access - took a Long time to diagnosis

5. If any AP connected users have an issue you can move them back to OLD Controller and verify the issue (is this resolved or same - its easy for you to understand the issue)

6. After 4 weeks all good, its time for your OLD WLC HA to Move to new WLC Code

7. Move the AP back to Upgraded HA WLC - close off the upgrade project.

Hope this steps make sense?

[Oron Yaniv]

thanks, Balaji, that sounds good and makes a lot of sense.

can I transfer the configuration from the 8540-HA mode to the new 8540-StandAlone mode?

in that way, it will save me a lot of time (and avoid misconfiguration) at the new 8540.

0. the new 8540 disconnects from the network at this phase

1. install 8.2.171 code on new 8540

2.  deploy the configuration from the 8540-HA to new 8540 (to preserve the configuration across 8540`s).

3. change the MGMT IPs (to avoid duplicate IPs).

4. connect as new 8540 to the network.

can this method work?

[balaji.bandi · Accepted solution]

Check my comments below :

yes you can copy the exiting config to new WLC 

0. the new 8540 disconnects from the network at this phase

BB - yes that means this is offline, ready for restore config from OLD Live controller to this controller Offline (make sure you remove HA and IP address config as per the requirement.

Note: I suggest to run the same version of the old controller Code in the new Controller, once you restored the config, and modified the config as suggested above., then upgrade to the desired version, this is the best approach.

1. install 8.2.171 code on new 8540

BB - as mentioned above, upgrade after loading the config.

2.  deploy the configuration from the 8540-HA to the new 8540 (to preserve the configuration across 8540`s).

BB -  By now the config also available with the new version - check no errors reported after the upgrade.

3. change the MGMT IPs (to avoid duplicate IPs).

BB - this already covered on the above steps.

4. connect as new 8540 to the network.

BB - yes install the kit in to Live Environment. - if you have TEST AP, migrate to the AP to the new controller. and test

or move non-critical area AP to new controller as test phase. (if any issue you can easy move back to OLD controller after capturing the information required to mitigate the issue)

I believe this is the best approach I think to be reasonable.

Make sure you have compatibility matrix checked with your AP. and read the release notes and understand the caveats before upgrade.- this is very important.

[Scott Fella]

That is a good approach. What I have done that is my workflow is download the config and use an editor to change the hostname, IP address, add the mobility group setting or just remove that and add it later. Then you run a diff between the old config and your new edited config and check to see what is different. The new config should of course start with the word “config” and the command should have a trailing whitespace. Then with the new controller offline on the same code as your current, you can upload the config through the service port. Once I upload, I then do another backup and run a diff from that new backup to the existing config just to make sure nothing changed. Once you are good, you can connect the controller to the network and do your testing and piloting.