Cisco Systems C3850NM410G Relevant Outputs for Tracking Client Roams in Converged Access

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 55 of 70
Figure 22. Client Roams Across Mobility Controller in Converged Access
In the preceding scenario, an intersubdomain (intermobility controller) roam is explained. The initial client join
happens at MA1 in SPG1. The wireless traffic is terminated locally at MA1 and delivered to the wired side when the
client is static. When the client roams to an access point connected to MC2, it roams from the subdomain whose
master is MC1. In this case, the traffic path for the roamed client is terminated at the foreign (PoA) MC2 switch.
The foreign (PoA) MC2 switch encapsulates this traffic in the mobility controller-to-mobility controller CAPWAP
tunnel and switches the traffic to MC1. This switch encapsulates this traffic in the mobility controller-to-mobility
agent CAPWAP tunnel and lands it back to the anchor (PoP) MA1 switch. The ACL policy is applied at the anchor
switch (MA1), and this switch forwards this traffic into the wired portion of the network.
Relevant Outputs for Tracking Client Roams in Converged Access
This section explains how all the preceding theory does look in practice. This section will cover relevant outputs for
wireless clients as they initially join the wireless network and follow them as they roam through the wireless
network.
The client wireless VLAN is spanned across three switches (MC1, MA1, and MA2). The fourth mobility agent
switch, MA3, is in a routed access design across which the client wireless VLAN cannot be spanned.
The second mobility controller switch, MC2, is also a routed access design across which the client wireless VLAN
cannot be spanned.
The L2 roam by default in converged access is tunneled. The example network covers the scenarios in which L2
tunneled roam, followed by L3 roam, and lastly L2 nontunneled roams occur.