Scenario 2: Centralized Traffic On A Controller With Vlan Egress; How It Works; Configuration Overview - HP MSM7xx Management And Configuration Manual

Mobility traffic manager

Scenario 2: Centralized traffic on a controller with VLAN egress

Scenario 2: Centralized traffic on a controller
with VLAN egress
This scenario illustrates how to centralize the traffic from a VSC that is deployed on several
APs on different subnets and send it to one or more VLANs via the controller.

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 on VLAN 40. To accomplish this, the egress network in the VSC binding is
set to a network profile that defines a VLAN on the controller's Internet port.
User A

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.
9-24
LAN port
192.168.1.1
Network 1 Network 2
192.168.10.0 192.168.20.0
1 2
User B
Internet port
192.168.40.1
VLAN 40
Network 3
192.168.30.0
3
User C
Network 4
VLAN 40