A Mobility Domain enables users to roam geographically across the system while maintaining data sessions and VLAN or subnet membership, including IP address, regardless of connectivity to the network backbone. As users move from one area of a building or campus to another, client associations with servers or other resources remains the same.
The clustering functionality ensures mobility across an entire wireless network. With clustering, you can effortlessly create logical groups of controllers and access points, which share network and user information in a proactive manner for continuos and uninterrupted support.
You can create a mobility domain using the Create Mobility Domain window from the Network Director user interface.
A Mobility Domain group consists of a primary seed controller that contains the IP address of all controller members. A secondary controller might be optionally assigned. You must specify the primary seed while creating the mobility domain. A mobility domain cannot exist without the primary seed. You must explicitly configure only one controller per domain as the primary seed. All other controllers in the domain receive their Mobility Domain information from the seed.
You can optionally specify a secondary seed in a Mobility Domain. The secondary seed provides redundancy for the primary seed switch in the Mobility Domain. If the primary seed becomes unavailable, the secondary seed assumes the role of the seed controller. This allows the Mobility Domain to continue functioning if the primary seed becomes unavailable. When the primary seed fails, the remaining members form a Mobility Domain, with the secondary seed taking over as the primary seed controller.
Note: Even though selecting a secondary seed for mobility domain is optional, Network Director does not assign a secondary seed by default.
Enabling cluster for the mobility domain enables cluster mode for both primary and secondary seed. To include the other domain controllers in cluster, set the cluster mode for the domain controllers using the Cluster Mode column in the Controllers in Mobility Domain table. Only after enabling cluster for the mobility domain can the cluster mode for the other mobility domain controllers be set.
This is a mandatory field.
This is a mandatory field.
This is an optional field. However, If you do not select a secondary seed, the domain will be nonoperational during failure.
To delete an already specified secondary seed, click the Clear button next to Secondary Seed.
The Cluster Mode column in the Controllers in Mobility Domain table is displayed only if you select the Enable Cluster check box.
To enable cluster mode for the mobility domain members, select enable in the Cluster Mode column from the Controllers in the Mobility Domain table.
Note: The table displays the list of available devices. The devices you had selected as the primary and secondary seeds will not be displayed again. Also, if you select a device and click OK, then the selected device is not displayed in the available Select Controllers for Mobility Domain window.
You can edit or delete the mobility domain that you created.
To edit a mobility domain:
Network Director lists the mobility domains that you created earlier.
To delete a mobility domain:
If mobility domain has cluster please disable cluster for the domain and deploy the changes and then delete mobility domain. Do you want to continue?
Click No if you want to delete the mobility domain but the domain contains a cluster.
To delete a mobility domain that contains a cluster:
© 2018 Juniper Networks, Inc. All rights reserved