Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[WLA/WLC] How to upgrade the cluster via the CLI



Article ID: KB27073 KB Last Updated: 12 Mar 2013Version: 1.0
This article provides information on how to upgrade the cluster via the CLI.
How to upgrade the cluster via the CLI.

The upgrade cluster command is used to upgrade the cluster to a different MSS version. Before running the command, perform the following procedure:
  1. Upload the same version of MSS on all the controllers that belong to the cluster.

  2. The new MSS version will have to be uploaded to the idle boot partition.To check what versions are currently present on the boot partition, run the following command:
    *wlc880-tac01# dir
    Output omitted
    Filename Size Created
    boot0:WC080202.8XX 26 MB Jan 08 2013, 08:48:00
    *boot1:WC077203.8XX 25 MB Feb 12 2013, 14:52:54
    As you can see, the controller is now running MSS 7.7. It has to be upgraded to 8.0. Make sure that the new MSS version is present on all the controllers in the cluster. So, on each of them, issue the same dir command and check if the same MSS version is present on the idle boot partition (in this case, the idle partition is boot0).

  3. On all the controllers, issue the following command (set boot partition bootx; where x is the number of the partition that has the MSS version, to which the cluster is to be upgraded):
    *wlc880-tac01# set boot partition boot0
    success: Boot partition set to boot0:WC080202.8XX (
  4. Save the configuration on the controllers.
    On the primary-seed, issue the upgrade cluster command:
    *wlc880-tac01# upgrade cluster
    This will reset cluster devices. Any unsaved configuration changes will be lost. Are you sure? (y/n) [n]y
    The upgrade to the new MSS will be sequentially performed on the controllers. When a controller is upgraded, the APs that booted from it will failover to the rest of the controllers. After all the controllers have been upgraded, check if the APs have also downloaded the new firmware. The APs with no client connections will be first migrated/upgraded.

    The system evaluates the remaining APs with client connections and tries to determine if a nearby AP can provide the same Wireless Service that can accept the client connection. If so, the AP with the current client connection is migrated/upgraded, which forces the client to Roam. Typically, this is seamless to the end-user.

  5. Finally, in case of any remaining APs with client connections, with which it is not possible to determine if a neighboring AP is available, migrate/upgrade these APs in batches to allow the Cluster to come back into full sync. It is possible that this may impact client connections for the duration of that AP upgrade process.

The following image illustrates the complete upgrade work flow:

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search