Filter
Top Products
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 54 of 70
Traffic Paths in Converged Access
This section explains the traffic path (profile) for local and roamed wireless clients across the different SPGs and
mobility controllers. (See Figure 21.)
Figure 21. Client Roams Within an SPG in Converged Access
As seen earlier, roams within an SPG are constrained within the anchor and foreign switches of the SPG.
As mentioned before, traffic for wireless clients that roam across an SPG has to traverse a mobility controller.
Assume that the mobility controller does the routing for the traffic that is roamed across an SPG. In Figure 21, the
client roams from initial MA1 in SPG1 to MA3 in SPG2. In this case the roamed traffic is terminated and
encapsulated at the new mobility agent, in the mobility agent-to-mobility controller CAPWAP tunnel and switched to
MC1. The mobility controller knows the anchor (PoP) switch for this client and encapsulates the traffic and switches
it to the anchor, MA1. The anchor switch applies ACLs to this traffic and also serves symmetrical routing in case
the roam is an L3 roam. (See Figure 22.)