Mobility traffic manager
Scenario 1: Centralizing traffic on a controller
9-21
Scenario 1: Centralizing traffic on a controller
This scenario illustrates how to centralize the traffic from a VSC that is deployed on several
APs on different subnets.
How it works
In this scenario, a single controller manages several APs deployed on different subnets. The
default VSC (named HP) is assigned to each AP and is used to provide wireless services for
users. All traffic on this VSC is tunneled to the controller by MTM, where it is egressed onto
the wired network. To accomplish this, the egress network in the VSC binding is set to the
network profile that is assigned to the controller’s LAN port.
Configuration overview
The following sections provide a summary of the configuration settings needed to enable
MTM support only. It is assumed that installation and configuration of all controllers and APs
so that they are fully operational on the network was performed as explained in the other
chapters in this guide.
W
L
A
N
LAN port
192.168.30.1
W
L
A
N
2
1
User B
User A
Network 2
192.168.20.0
Network 1
192.168.10.0
Network 3
192.168.30.0
User B
User A
To Next Page
Loading...
Need help?
General
