When designing a large, high-availability wireless network, what changes to a mobility- group would create less load on the controllers while maintaining the same mobility messages?

Question

Options

• Aremove unnecessary controllers from the mobility-group to cut down on the controller's
• Bseparate the controllers into different mobility-groups per controller to only send relevant
• Cconfigure mobility-group multicast messaging
• Dconfigure the controllers into separate RF-Groups from the mobility-groups to cut down on

• A
  8% (3)
• B
  5% (2)
• C
  74% (29)
• D
  13% (5)

Explanation

In a large mobility group, each controller must send unicast mobility messages to every other controller, creating O(N²) message overhead that scales poorly. Configuring mobility-group multicast messaging allows a controller to send a single multicast packet that all other controllers in the group receive simultaneously, reducing the messaging load from N-1 unicast transmissions to a single multicast transmission per event. This preserves full mobility functionality while dramatically lowering CPU and network overhead on each controller. Choice A (removing controllers) reduces availability. Choice B (per-controller mobility groups) breaks seamless client roaming. Choice D conflates RF Groups with mobility groups - RF Groups manage RRM, not client roaming messages.

No community discussion yet for this question.