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

[WLC] How to configure a Mobility Domain via the RingMaster



Article ID: KB33172 KB Last Updated: 28 Sep 2018Version: 1.0

This article provides the steps for configuring mobility-domain via the RingMaster.


Perform the following steps to configure mobility-domain via the RingMaster:

 1. Login to the RingMaster.

2. Select Upload WLC in the right corner to upload the primary controller.

3. Repeat step 2 to and specify the IP address of the secondary controller.

4. After uploading both the primary and secondary controllers into the RingMaster, select the Configuration tab, and then click on the Create Mobility Domain option.


5. Enter the Mobility Domain Name.


6. Choose the controllers to add into the mobility-domain.

7. Assign the Primary Seed and Secondary Seed for the mobility-domain. Then click Finish.

8. After creating the mobility-domain, select the Devices tab. Click on the Review option which is available on the right-hand side task panel to review the local changes. Similarly, Click on the Deploy option which is available on the right-hand side task panel to deploy the local changes.

9. Repeat step 8 (review and deploy) for the secondary controller.

10. Once the mobility-domain has been configured, we can verify the deployment from the CLI with the following command:

800R223# sh mobility-domain
Mobility Domain name:  ABC
Flags: u = up[2], d/e = down/config error[0], c = cluster enabled[0],
       p = primary seed, s = secondary seed (S = cluster preempt mode enabled),
       a = mobility domain active seed, A = cluster active seed (if different),
       m = member, y = syncing[0], w = waiting to sync[0], n = sync completed[0],
       f = sync failed[0]
Member: * = switch behind NAT
Member            Flags  Model     Version     NoAPs  APCap
----------------  -----  --------  ----------  -----  -----      upa--  MX-800R         2     16      us---  WLC880R         0     16


Related Links

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