This article provides a step-by-step procedure for swapping out three clustered MX2800 controllers with three WLC2800 controllers, while maintaining the existing configuration.

The goal is to swap out three clustered MX2800s with three WLC2800s, while maintaining the existing configuration.

The exchange will be done by replacing individual MX2800 controllers with WLC2800s controllers, one at a time. The MX2800 should be upgraded to a version of code that also exists for the WLC2800, and the WLC2800 should be running the same version. Ring Master should be also upgraded to that version of code.

We will begin with the third unit (cluster member), follow with the second unit (secondary seed) and finish with the first unit (primary seed).

Preparation:

1. Load the code on the WLC2800s to match the existing MX2800 version and install new licenses. Label the boxes.


2. Check Ring Master to ensure that there are no outstanding changes. Ring Master should be at the same version of code.


3. Make a copy of the configuration from each of the three current MX2800s and load them onto the three new WLC2800s. The serial and model numbers will be different from the Ring Master database.


4. Make a backup of the Ringmaster folder.

Begin Hardware Swaps

1. Note the number of operational access points (APs) and the number of connected devices/users.


2. Remove the MX2800 that is the cluster member. The APs should remain operational and immediately re-balance across the operational controllers.


3. In Ring Master, edit the controller to reflect the new model and serial number.


4. Connect the new controller. Confirm its presence in Ringmaster. Check its inclusion into the cluster using the ‘show mobility-domain’ command. The APs will re-balance across all controllers.


5. Remove the MX2800 that is the secondary seed. The APs should remain operational and immediately re-balance across the operational controllers.


6. In Ring Master, edit the controller to reflect the new model and serial number.


7. Connect the new controller. Confirm its presence in Ring Master. Check its inclusion into the cluster using the ‘show mobility-domain’ command. The APs will re-balance across all controllers.


8. Remove the MX2800 that is the primary seed. The APs should remain operational and immediately re-balance across the operational controllers.


9. In Ring Master, edit the controller to reflect the new model and serial number.


10. Connect the new controller. Confirm its presence in Ring Master. Check its inclusion into the cluster using the show mobility-domain command. The APs will re-balance across all controllers.


11. Perform system checks to ensure everything is operational. Check the active APs and the user count.

Conclusion

At this time all systems should be operational, running the same configuration on newer WLC2800 hardware.

Future controller upgrades will be done using the WCnnnn.280 images rather than MXnnnn.280 images. Ring Master can be upgraded as usual.