300-425 · Question #267
Which feature must be incorporated into the network design to allow seamless Layer 3 roaming between controllers?
The correct answer is B. Mobility groups. Mobility groups allow multiple controllers to share client context, enabling a client to retain its IP address when roaming across subnet boundaries.
Question
Which feature must be incorporated into the network design to allow seamless Layer 3 roaming between controllers?
Options
- ASame VLANs across controllers
- BMobility groups
- CClient load balancing
- DLink aggregation
How the community answered
(32 responses)- A3% (1)
- B88% (28)
- C3% (1)
- D6% (2)
Why each option
Mobility groups allow multiple controllers to share client context, enabling a client to retain its IP address when roaming across subnet boundaries.
Using the same VLANs across controllers would force Layer 2 adjacency and effectively removes the Layer 3 boundary rather than enabling seamless roaming across it.
Mobility groups allow Cisco WLCs to communicate client association state over a mobility tunnel so that when a client roams to an AP joined to a different controller, the anchor controller preserves the original IP assignment. This anchor-foreign relationship is what makes Layer 3 roaming seamless without requiring shared VLANs.
Client load balancing distributes clients across APs to manage AP utilization but has no role in maintaining IP address continuity during a roam.
Link aggregation combines physical uplinks for increased bandwidth and redundancy on a single controller but does not provide any roaming or client mobility function.
Concept tested: Layer 3 roaming using WLC mobility groups anchor-foreign
Source: https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/70330-mobility-config-guide.html
Topics
Community Discussion
No community discussion yet for this question.