Cisco Systems C3850NM410G

The mobility controller’s area of responsibility lies in the mobility subdomain it controls. All the mobility agents in the

subdomain form CAPWAP mobility tunnels to the mobility controller and report local and roamed client states to the

mobility controller. The mobility controller builds a database of client stations across all the mobility agents.

By distributing these functions in the Cisco Catalyst 3850 Switches in the access, converged access provides

scalable, resilient, feature-rich wireless services in conjunction with wired services and features.

Mobility Oracle

This is a software function that is responsible for client station visibility across the mobility controllers (mobility

subdomains) in its mobility domain. The mobility oracle is an optional entity in the hierarchy of mobility agent-

mobility controller-mobility oracle. The advantage of configuring a mobility oracle for a converged access

deployment is that it scales and reduces control events that occur for initial client joins and client roams, especially

in a multi-mobility controller environment. This function cannot be hosted on the Cisco Catalyst 3850, and can only

be hosted on software-upgraded Cisco 5508 WLC, WiSM2, or Cisco 5760 WLC. Typically the mobility oracle is

hosted on a controller appliance running the mobility controller function.

Logical Hierarchical Groupings of Roles

Mobility Group

Today’s Cisco Unified Wireless Network defines mobility group as a logical group of mobility controllers to enable

fast roaming of clients within the mobility controllers of a mobility group.

Switch Peer Group (SPG)

The converged access deployment defines a switch peer group (SPG) as a logical group of mobility agents within

one mobility controller (or mobility subdomain). The main advantage of configuring SPGs is to constrain the

roaming traffic to switches that form the SPG. When the mobility agents are configured in one SPG on the mobility

controller, the software automatically forms full mesh CAPWAP tunnels between the mobility agent switches These

CAPWAP tunnels can be formed in a multilayer network design (where the mobility agent switches are L2 adjacent

on a VLAN spanned across) or a routed access design (where the mobility agent switches are L3 adjacent). (See

Figure 8.)