Coverged Access Ing PDF

Cisco Learning Express
Converged Access
Juan%David%Duarte%C.,%MSc%
Virtual(Systems(Engineer
(
GVE Services offered through Cisco Partner Plus
The Service Offerings provided by GVE will be based on partners level of entitlement through Partner
Plus. FY15 will include a new Level II escalation service offering to participating Distributors in support of
Prestige and Elite partners.
Level I Pre Sales

Technical Support. Provided
to Aspire, Prestige, and
Elite Partners.
PH
2014 Cisco
Ciscoand/or
and/orits
itsaffiliates.
affiliates.All
Allrights
rightsreserved.
reserved.
NEW FY15 - Level II Escalated Pre

Sales Technical Support. Provided to
Entitled Distributors supporting Prestige
or Elite partners.
GVE for
Distributor
Cisco Confidential
Level II Pre Sales Technical Support.

Provided to Prestige through entitled Disti
and Elite direct or through entitled Disti.
PH+
2
Cisco Confidential
Agenda(
Solu5on%Overview%
%
%
Architecture%and%Roaming
%
%
%
Design%Op5ons
TECCRS-2678
2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public EVALUATIONS!%%Tell(us(how(we(did(((

3 (
Agenda(
Solu5on%Overview%%
Evolu5on%%Towards%One%Policy,%One%Management,%One%Network%
%
Converged(Access((Pla=orm(Overviews(
(
Wired(and(Wireless((Deployment(OpBons(
TECCRS-2678
Cisco Public
Performance Protection for

your 802.11n WiFi Network
Enterprise Wireless Evolution
From Best-Effort to Mission-Critical and Very High Density

Casual
Pervasive
indoors
Media Rich
Applications
Very High Density
Mission Critical
CleanAir
Hotspot
System Management
Capacity
Self Healing
and Optimizing
TECCRS-2678
VXI Capable
Cisco Public
Wireless Standards
Past, Present, and Future
Nice%to%Have%
Pervasive%
Media%Rich%Applica5ons%
Mission%Cri5cal%
%10Gbps%
CLIENTS%/%BANDWIDTH%
Future?%
802.11acY2%
3.5%Gbps%
802.11acY1%
~1%Gbps%
802.11n%
450%Mbps%
802.11a,%802.11b%
11%Mbps%
802.11g%
54%Mbps%
11Mbps%
Early%2000%
2002%
2004%
2006%
2008%
2010%
2012%
2014%
2016%
How Many Mobile Data Devices
Do You Think You Will Carry Everywhere in 2016?

Think about it, and choose the best answer
1 3 5 7
TECCRS-2678
Cisco Public
Unified Access
Uncompromised User Experience in Any Workspace
One%Network%
One%Management%
One%Policy%
TECCRS-2678
Unified Access
Cisco Public
One Network, with Converged Access

A New Deployment Mode for Wired / Wireless
Cisco(Wireless(
LAN(Controller(
WLC%5760%
IOS%Based%WLAN%Controller(
Internal(
Resources(
Consistent(IOS(and(ASIC(as(Catalyst(3x50(
Required(to(scale(beyond(200/250(AP(
or(8(000/16(000(client(domains(
One%Network%
Converged%Access%Mode(
Corporate%
Network%
Integrated(wireless(controller(
Distributed(wired/wireless(data(plane(
Cisco((
(CAPWAP(terminaBon(on(switch)(Access(Point(
Internet%
Catalyst%3650%
Catalyst(Switch(
Cisco(Firewall(
Catalyst%3850%
LAN(Mgmt(
SoluBon(
One%Policy%
Wireless(Control(
System(
ISE%
Access(Control(
Server(
IdenBty(
Mgmt(
One%Management%
Guest(
Server(
Prime%
NAC(
Proler(
Converged Wired / Wireless Access
Cisco Converged Access Deployment
Benefits Overview
Single%
pla_orm%for(
wired(and(
wireless(
(
Common(IOS,(same(
administraBon(point,(
one(release(
Network(wide(
Consistent(
visibility(for(
security(and(
faster(
Quality(of(Service(
troubleshooBng%
control%
%
Wired(and(wireless(
trac(visible(at(
every(hop(
%
Hierarchical(bandwidth(
management(and(
distributed(policy(
enforcement(
Maximum%
resiliency%with(
fast(stateful(
recovery%
%
Layered(network(high(
availability(design(with(
stateful(switchover(
Scale%with(
distributed(wired(
and(wireless(
data(plane(
(
Large(stack(bandwidth;(
40G(wireless(/(switch;(
ecient(mulBcast;(
802.11ac(opBmized(
U n i f i eTECCRS-2678
d A c c e s s - O n 2014
e P
oand/or
l i citsyaffiliates.
| OAllnrights
e reserved.
M a n a g e mCisco
e Public
nt | One Network
Cisco
10
Agenda%%%%TECCRSb2678(
Solu5on%Overview%%
EvoluBon((Towards(One(Policy,(One(Management,(One(Network(
%
Converged%Access%%Pla_orm%Overviews%
(
Wired(and(Wireless((Deployment(OpBons(
TECCRS-2678
Cisco Public
11
Converged Access Components

Complete Overview
One%Policy%%
One%Management%%
BYOD(policy(management(
Device(proling(and(posture(
Guest(access(portal(
Full(wired(and(wireless(management(
User/device(centric(view(
IntuiBve(troubleshooBng(workows(
with(IdenBty(Services(Engine((ISE)(1.2(
with(Cisco(Prime(2.0(
Who?( What?( When?(Where?( How?(
Catalyst(3850((
Cisco(Prime(
ISE(
5760(Wireless(Controller(
Catalyst(3650((
Catalyst%3850%
Catalyst%3650%
Fully(integrated(wired(and(wireless(
switch(
480G(StackWise,(StackPower(
Wireless:(50(APs,(2K(clients,(40G(
Flexible(NetFlow,(Granular(QoS,(UADP(
Fully(integrated(wired(and(wireless(
switch(
160G(StackWise(
Wireless:(25(APs,(1K(clients,(40G(
Flexible(NetFlow,(Granular(QoS,(UADP(
5760%Wireless%Controller%
Consistent(IOS(with(Catalyst(3650/3850(
60G,(1K(APs,(12K(Clients,(480G(stack(HA(
Redundancy(
Flexible(Ne=low,(Granular(QoS,(3x(UADP(
B e s t - i n - C l a s s P e r f o r m a n c e , S e c u r i t y, a n d R e s i l i e n c y
TECCRS-2678
Cisco Public
12
Catalyst 3850 and 3650 Switches
Single Platform for Wired and Wireless
20+%Years%of%IOS%Richness%%Now%on%Wireless%
WIRED(
WIRELESS(
Features:(
%%
Centralized(deployment(
L2/L3(Fast(Roaming(
Clean(Air(
Video(Stream(
Radio(Resource(
Management((RRM)(
Wireless(Security(
Radio(performance(
802.11ac(
TECCRS-2678
Features:(
%%
Benets%
Built(on(UADP%(Ciscos(InnovaBve((((
Flexparser(ASIC(technology(
Eliminates(operaBonal(complexity(
Single(modern(OperaBng(System(for(wired(
and(wireless((
( 2014 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Stacking(and(HA(
SGT(&(Advanced(IdenBty(
Visibility(and(Control(
Flexible(NetFlow(
Granular(QoS(
Smart(OperaBons(
EEM,(scripBng(
IOSbXE(Modular(OS(
13
Catalyst 3850
Platform Overview
Wireless(CAPWAP(
TerminaBon(in(HW(
Up(to(50(APs(/
2000(clients(per(
stack,(and(40G(
per(switch(
480(Gbps((
Stacking(Bandwidth(
FRU(Fans,(Power(
Supplies(b(HA(
Up(to(2000(Clients(
per(Stack(
Stackpower(
Full(POE+(
(
Granular(QoS(/(Flexible(
NetFlow(
MulBbCore(CPU(
APs(must(be(directly(connected(to(Catalyst(3850(
TECCRS-2678
Line(Rate(on(All(Ports(
40(Gbps(Uplink(
Bandwidth(
(Modular)(
Built%on%Ciscos%Innova5ve%UADP%ASIC%%
Cisco Public
14
New Catalyst 3650 Switch

Platform Overview
New(FrontbEnd((
Power(Supplies(
Modular(160(Gbps((
9(members(Stack(
FRU(Fans(
Up(to(25(APs(/(1000(clients(per(
stack,(and(40G(per(switch(
Wireless(CAPWAP(
TerminaBon(in(HW(
Up(to(1000(Clients(
per(Stack(
Fixed(1G/10G(Uplinks((
SGT/SGACL(
Up(to(40(Gbps(
Uplink(Bandwidth(
(
Granular(QoS(/(Flexible(
NetFlow(
APs(must(be(directly(connected(to(Catalyst(3650(
TECCRS-2678
Line(Rate(
on(All(Ports(
Full(POE+(
Cisco Public
15
Wireless LAN Controller (WLC) 5760

Platform Overview
Up(to(1000(
Access(Points(
Centralized,(or(
Converged(Access(
Deployment(Modes(
6x(1/10G(SFP+(
uplinks(with(LAG(
Granular(QoS(
First(IOSbBased(
Wireless(LAN(Controller(
Up(to(12,000(Concurrent(Clients(
802.11ac(
OpBmized(
60(Gbps(Wireless(Bandwidth(
Flexible(NetFlow(
FRU(Power(Supplies(
FRU(Fans(
TECCRS-2678
Cisco Public
16
Solu5on%Overview%%
EvoluBon((Towards(One(Policy,(One(Management,(One(Network(
%
Converged(Access((Pla=orm(Overviews(
(
Wired%and%Wireless%%Deployment%Op5ons%
TECCRS-2678
Cisco Public
17
Unified Access Includes Converged Access

Wireless Deployment Mode Options
One Policy, One Management,

One Network
Unified Access Wireless
Autonomous
FlexConnect
(Private Cloud)
Centralized
Converged
Access
Individual(APs(
Trac(Distributed(
at(AP(
Trac(Centralized((
at(Controller(
Trac(Distributed((
at(Switch(
Unparalleled Deployment Flexibility

TECCRS-2678
Cisco Public
18
Agenda(
Converged%Access%System%Architecture,%Roaming,%and%High%Availability%%
Exis5ng%Wireless%Deployments%%Architecture%Refresher%
%
Converged(Access((Terminology(and(Building(Blocks(
%
Converged(Access((Trac(Flows(and(Roaming(
(
(
TECCRS-2678
Cisco Public
19
Converged Access
Network Requirements Driving Wireless Evolution

Increased scalability, Centralized policy application
Weve Been Here Before

Centralized tunneling of user traffic to
controller (data plane and control plane)
System-wide coordination for channel
and power assignment, rogue detection,
security attacks, interference, roaming
Hotspot
deployments with
nomadic roaming
Standalone
Access Point
Autonomous
Mode
TECCRS-2678
Functionality
split with
CAPWAP
Control plane functionality on NG Controller

(also possible on upgraded 5508s, WiSM2s
for brownfield deployments, or NG Converged
Access switches for small, branch deployments)
Cisco
Converged
Access
Controller
Cisco
Unified
Wireless
Access Point
Frees up the AP to focus on real-time
communication, policy application and
optimize RF & MAC functionality such as
CleanAir, ClientLink
Scale
andand/or
Services
2014 Cisco
its affiliates. All rights reserved.
Data plane functionality on NG Switches

(also possible on NG Controllers, for deployments
in which a centralized approach is preferred)
Unified wired-wireless experience
(security, policy, services)
Common policy enforcement, Common
services for wired and wireless traffic
(NetFlow, advanced QoS, and more )
Performance
and Unified Experience
Cisco Public
20
Data Center /
Service block
Architecture Constructs
CUWN Tunnel Types
Mobility
Group
Internet
PI
ISE
Intranet
Well-known,
proven
architecture
EoIP Mobility Tunnel ( < 7.2)

CAPWAP Option in 7.3
WLC #1
Foreign WLC
Guest Anchor
LEGEND
WLC #2
CAPWAP
Tunnels
Encrypted
(see Notes)
Notes
AP
Existing Unified Wireless Deployment today
AP
SSID VLAN
Mapping
(at controller)
SSID2 SSID1 SSID3

TECCRS-2678
AP
AP
Inter-Controller (Guest Anchor)

EoIP / CAPWAP Tunnel
Inter-Controller
EoIP / CAPWAP Tunnel
AP-Controller CAPWAP Tunnel
802.11 Control Session + Data Plane
AP / WLC CAPWAP Tunnels are an IETF Standard

UDP ports used
5246: Encrypted Control Traffic
5247: Data Traffic (non-Encrypted or DTLS Encrypted (configurable)
Inter-WLC Mobility Tunnels

EoIP IP Protocol 97 AireOS 7.3 introduces CAPWAP option
Used for inter-WLC L3 Roaming and Guest Anchor
Cisco Public
21
CUWN Control Functions
Mobility
Group
Data Center /
Service block
PI
Internet
ISE
Intranet
EoIP Mobility Tunnel ( < 7.2)

CAPWAP Option in 7.3
MA
WLC #1
WLC #2 MA
MC
MC
MC
LEGEND
MA
Foreign WLC
Guest Anchor
CAPWAP
Tunnels
AP
AP
SSID2 SSID1 SSID3

TECCRS-2678
AP
MA
Mobility Agent
Terminates CAPWAP Tunnels,
Maintains Client Database
MC
Mobility Controller
Handles Roaming, RRM, WIPS, etc.
AP
These%will%become%important%later%
as(we(delve(into(the(Converged(Access(
deployment((
Cisco Public
Additional
details on
controller
functionality
22
For(Your(
Reference(
Mobility Group, Details
Group of Wireless LAN Controllers (WLCs) in
Mobility(Group(dened:(
a network with the same Mobility Group name
Provides Seamless Mobility and
WLC(3(
Fast Roaming for clients
Up to 24 WLCs members in one Mobility
Group, statically configured
Full mesh of tunnels between members

WLC(1(
WLC(4(
Messages can be sent using Multicast

Mobility Control Messages
UDP port 1666 for un-encrypted traffic

WLC(2(
Mobility(Group(
User Data traffic
EoIP (IP protocol 97)

NAT between members is supported
TECCRS-2678
Cisco Public
23
For(Your(
Reference(
Mobility Domain (List), Details

Mobility(Domain((List)(dened:(
Group of controllers configured on a single
WLC that specifies members in different

mobility groups
Provides seamless Mobility for clients
(
(
(clients keep original IP address)

Up to 72 WLCs in one WLCs Mobility List
(
(
(
(
Full mesh of tunnels between members
Messages can be sent using Multicast

Mobility Control Messages
Mobility(Group(1(
Mobility(Group(2(
Mobility(Domain(
UDP port 1666 for un-encrypted traffic

User Data traffic
EoIP (IP protocol 97)

NAT between members is supported
TECCRS-2678
Cisco Public
24
Point of Presence (PoP), Point of Attachment (PoA)

Data CenterDMZ
Campus
Data Center
Campus Services
Si
WiSM2s / 5508s
ISE
PI
MC
MA
MC
MA
MC
MA
MC
MC
MA
Internet
MA
Si
Point of Presence (PoP) vs.

Point of Attachment (PoA)
Si
Si
PoP%
PoA%
Layer 2
Mobility Group
Si
Guest Anchors
Si
PoP is where the wireless user

is seen to be within the wired
portion of the network
Anchors client IP address
Used for security policy application
Si
Si
Si
Campus
Access
Si
PoA is where the wireless user

has roamed to while mobile
Moves with user AP connectivity
Used for user mobility and QoS
policy application
Now, lets see how mobility works
when a user roams in this deployment model
TECCRS-2678
Cisco Public
25
Layer 2 Roaming (Campus Deployment)

Data CenterDMZ
Campus
Data Center
Campus Services
Si
WiSM2s / 5508s
ISE
PI
MC
MA
MC
MA
MC
MA
MC
MC
MA
Internet
MA
Si
Si
Initially, the users PoP and PoA

are co-located on the same controller
Si
PoP%
PoA%
Layer 2
Mobility Group
Si
Guest Anchors
Si
Si
Note in this deployment model, it is assumed

that all of the controllers within the DC share
a common set of user VLANs at Layer 2
Si
Si
Si
Initially, the users traffic flow is as shown
Campus
Access
TECCRS-2678
Cisco Public
26

Data CenterDMZ
Campus
Data Center
Campus Services
Si
WiSM2s / 5508s
ISE
PI
MC
MA
MC
MA
MC
MA
Si
MC
MC
MA
Internet
MA
Now, the user roams to an AP handled by

a different controller, within the same
Mobility Group
Si
PoA%
Layer 2
Mobility Group
Si
Si
Si
Si
Campus
Access
TECCRS-2678
Guest Anchors
Si
PoP%
Si
Move(of(
the(users(
enBre(Mobility(
Context(
Si
The users PoP and PoA both move to the

new controller handling that user after the
roam (possible since the controllers in this
deployment model are all L2-adjacent within
the VLANs)
After the roam, the users traffic flow
is as shown
Cisco Public
27

Data Center
Campus Services
Data CenterDMZ
Campus
Si
Guest Anchors
MC
MC
MA
Internet
MA
Si
ISE
Si
Initially, the users PoP and PoA

are co-located on the same controller
Si
PI
PI
Si
Si
PoP
MC
PoAMA
5508 /
WiSM-2
MC
Si
Si
MA
5508 /
WiSM-2
Si
Si
Layer 3
Mobility
Group
Note in this deployment model, it is assumed

that all of the controllers across the Campus
do not share a common set of user VLANs
at Layer 2
(i.e. the controllers are all L3-separated)
Initially, the users traffic flow is as shown
Campus
Access
TECCRS-2678
Cisco Public
28

Data Center
Campus Services
Data CenterDMZ
Campus
Si
Guest Anchors
MC
MC
MA
Internet
Symmetric
Mobility
Tunneling
MA
Si
ISE
Si
Now, the user roams to an AP handled by

a different controller, within the same
Mobility Group
Si
PI
PI
Si
Si
PoP
MC
PoAMA
5508 /
WiSM-2
MC
Si
Si
MA
5508 /
WiSM-2
Campus
Access
Si
Si
Layer 3
Mobility
Group
The users PoA moves to the new controller

handling that user after the roam but the
users PoP stays fixed on the original
controller that the user associated to
This is done to ensure that the user retains
the same IP address across an L3 boundary
roam and also to ensure continuity of policy
application during roaming
After the roam, the users
traffic flow is as shown
TECCRS-2678
Cisco Public
29
Roaming with Mobility Anchors
Data Center
Campus Services
Data CenterDMZ
Campus
Si
Guest Anchors
MC
PoP%
MC
MA
Internet
MA
Si
ISE
Si
Now, lets examine roaming

with Mobility Anchor use
Si
PI
PI
Si
MC
PoAMA
PoA%
5508 /
WiSM-2
MC
Si
Si
Si
MA
5508 /
WiSM-2
Campus
Access
Si
Si
Layer 3
Mobility
Group
When using Mobility Anchors, the users PoP

is always located at the Mobility Anchor
controller ... while the users PoA moves
as the user roams
Again, this is done to ensure that the user retains
the same IP address across an L3 boundary
roam and also to ensure continuity of policy
application during roaming
Before the roam, the users traffic flow
is as shown (tunneling of user traffic
back to the Mobility Anchor
guest traffic assumed)
TECCRS-2678
Cisco Public
30
Roaming with Mobility Anchors
Data Center
Campus Services
Data CenterDMZ
Campus
Si
Guest Anchors
MC
PoP%
MC
MA
Internet
MA
Si
ISE
Si
Now, lets examine roaming

with Mobility Anchor use
Si
PI
PI
Si
MC
MA
MC
Si
MA
PoA%
5508 /
WiSM-2
Si
Si
5508 /
WiSM-2
Campus
Access
TECCRS-2678
Si
Si
Layer 3
Mobility
Group
After the roam, the users PoA moves to the

new controller that handles the AP the user
has roamed onto however, the users PoP
remains fixed at the Mobility Anchor controller
After the roam, the users traffic flow
is as shown
(tunneling of user traffic back to the
Mobility Anchor guest traffic assumed)
Cisco Public
31
Traffic Flow
WiSM2s(/(
5508s(
CUCM
MC
PoP%
MA
MC
MA
PSTN
PoA%
Separate
policies and
services for wired
and wireless
users
In this example, a VoIP user is on

todays CUWN network, and is
making a call from a wireless
handset to a wired handset
Wireless%policies%
implemented%
on%controller(
The same
traffic paths are
incurred for voice,
video, data, etc.
all centralized
Wired%policies%
implemented%
on%switch(
TECCRS-2678
Traffic Flows,
Unified Wireless
We can see that all of the users

traffic needs to be hairpinned
back through the centralized
controller, in both directions
In this example, a total of 9 hops
are incurred for each direction
of the traffic path (including the
controllers Layer 3 roaming
might add more hops)
Cisco Public
32
For(Your(
Reference(
Key Considerations Data Plane, Details

Today wireless Data Plane is centralized,
wireless traffic is overlaid on top of the wired network

All traffic hair-pinned back through the central Controller (local mode)
Traffic is not visible as its inside a CAPWAP tunnel
Policies are usually applied in different places in the network for wired (switch) and wireless (Controller)
A distributed wireless and wired data plane brings:

1. Scalability as wireless is terminated at access switch, same level of performance
is delivered for wireless and wired
2. Enable end to end traffic visibility for all traffic types from network access
same tools for troubleshooting that are available for wired
3. Common policy enforcement point for wired and wireless
4. High Availability wireless controller fault is isolated (for example to a single switch/floor)
5. Rich media optimization support mission critical application with QoS applied closest to source
TECCRS-2678
Cisco Public
33
ExisBng(Wireless(Deployments((Architecture(Refresher(
(
Converged%Access%%Terminology%and%Building%Blocks%
%
Converged(Access((Trac(Flows(and(Roaming(
(
(
TECCRS-2678
Cisco Public
34
Converged Access Architecture
What Were Going to Cover
CA System Architecture
Roaming, High Availability
Corner
Stones
Deployment and Design
Foundational Elements
TECCRS-2678
for the
Access Solution35
CiscoConverged
Public
Converged Access
Deployment Overview
Mobility Domain
ISE
MO#
PI
Mobility Group
MC
MC
Sub-Domain
#1
SPG
SPG
MA
TECCRS-2678
Sub-Domain
#2
MA
MA
MA
MA
MA
Cisco Public
36
Converged Access
For(Your(
Reference(
Mobility Architecture
Mobility(
Oracle(
Mobility(
Controller(
Mobility(Group(N(
%%%%%%%%
Mobility(Subdomain(A(
Mobility(
Agent(
Peer(Group(1(
Mobility(Subdomain(B(
Mobility(Group(M(
Peer(Group(2(
Mobility(Domain(
Fast%Roam%
Full%Authen5ca5on%
14ms%
50ms%
TECCRS-2678
80ms%
>%250ms%
120ms%
Cisco Public
37
Converged Access
Components Physical and Logical Entities

Physical Entities
Mobility Agent (MA) Terminates CAPWAP tunnel from AP

Mobility Controller (MC) Manages mobility within
and across Sub-Domains
Mobility Oracle (MO) Superset of MC,
allows for Scalable Mobility Management within a Domain
Logical Entities
Mobility Groups Grouping of Mobility Controllers (MCs)

to enable Fast Roaming, Radio Frequency Management, etc.
Mobility Domain Grouping of MCs to support seamless roaming
Switch Peer Group (SPG) Localizes traffic for roams
within a Distribution Block
Cisco Public(4400, 5500, WiSM2)
TECCRS-2678
2014 Cisco and/or itsall
affiliates.
All rights
MA, MC,
Mobility Group functionality
exist
in reserved.
todays controllers
38
Converged Access
Physical Entities Mobility Agents (MAs)

ISE
Mobility Group
PI
MA is the first level in the

hierarchy of MA / MC / MO
One MA per Catalyst 3x50 Stack
MA
TECCRS-2678
MA
MA
Maintains Client DB
of locally served clients
Interfaces to the Mobility Controller
(MC)
Cisco Public
39
Converged Access
Physical Entities Mobility Controllers (MCs)

ISE
Mobility Group
PI
Mandatory element in design

Can be hosted on a MA (smaller deployments)
Manages mobility-related state of the
downstream MAs
Maintains Client DB within a Sub-Domain
(1 x MC = One Sub-Domain)
MA
MA
MA
Handles RF functions (including RRM)

Multiple MCs can be grouped together
in a Mobility Group for scalability
TECCRS-2678
Supported platforms are Catalyst 3850,

Catalyst 3650, WiSM2, 5508, and 5760
Cisco Public
40
Converged Access
Physical Entities Catalyst 3850 / 3650 Switch Stack

BestYinYClass%
Wired%Switches%%
with%Integrated%
Wireless%Mobility%
func5onality(
MA
Can act as a Mobility Agent (MA)
for terminating CAPWAP tunnels for locally connected APs

MC
as well as a Mobility Controller (MC)
for other Mobility Agent (MA) switches, in small deployments

- MA/MC functionality works on a Stack of Catalyst 3850 / 3650 Switches
- MA/MC functionality runs on Stack Master
- Stack Standby synchronizes some information (useful for intra-stack HA)
TECCRS-2678
Cisco Public
41
Converged Access
Logical Entities Switch Peer Groups (SPGs)

Sub-Domain 1
SPGs are a logical construct, not a physical one
SPG-B
SPGs can be formed across Layer 2 or Layer 3 boundaries
MA
MA
MC
SPG-A
MA
MA
SPGs are designed to constrain roaming traffic to a

smaller area, and optimize roaming capabilities and
performance
Current thinking on best practices dictates that
SPGs will likely be built around buildings,
around floors within a building, or other
areas that users are likely to roam most within
Made up of multiple Catalyst 3x50

switches as Mobility Agents (MAs),
plus an MC (on controller as shown)
Handles roaming across SPG (L2 / L3)
Roamed traffic within an SPG moves directly

between the MAs in that SPG (CAPWAP full mesh)
Roamed traffic between SPGs moves
via the MC(s) servicing those SPGs
MAs within an SPG are fully-meshed

(auto-created at SPG formation)
Hierarchical
architecture
is optimized for
scalability and
roaming
Fast Roaming within an SPG

Multiple SPGs under the control
of a single MC form a Sub-Domain
TECCRS-2678
Cisco Public
42
Converged Access
Logical Entities Switch Peer Groups and Mobility Group

Sub-Domain 3
Sub-Domain 1
SPG-E
SPG-B
MA
MA
MA
MA
MC
MC
SPG-A
Mobility
Group
MA
Made up of multiple Catalyst 3x50

switches as Mobility Agents (MAs),
plus an MC (on controller as shown)
Handles roaming across SPG (L2 / L3)
MAs within an SPG are fully-meshed
(auto-created at SPG formation)
Multiple SPGs under the control
of a single MC form a Sub-Domain
TECCRS-2678
MA
MA
Made up of Multiple
Mobility Controllers (MCs)
SPG-C
Handles roaming across MG (L2 / L3)
MA
RF Management (RRM, handled by RF

Group), Key Distribution for Fast Roaming
One Mobility Controller (MC) manages

RRM for the entire RF Group
Fast Roams are limited to

Mobility Group member MCs
SPG-D
MA
Fast Roaming within an SPG
SPG-F
MC
MA
MA
MA
Sub-Domain 2
Cisco Public
43
Converged Access
Physical Entities Mobility Oracle (MO)

Mobility Group
ISE
MO
PI
MC
MC
Top level in the MA / MC / MO

Hierarchy Optional
Further enhances scalability and performance
by coordinating Inter-MC roams
(removes need for N2 communications between
MCs, improves client join performance)
MA
MA
MA
Maintains database of clients across

multiple Mobility Controllers (MCs)
Can be a Software-Upgraded
WiSM2, 5508 or 5760 Controller
TECCRS-2678
Cisco Public
44
Converged Access
For(Your(
Reference(
Scalability Considerations
As with any solution there are scalability constraints to be aware of

These are summarized below, for quick reference
Full details on scalability for both CUWN as well as Converged Access deployments
is located in the Reference section at the end of this slide deck
3650 as MC 3850 as MC
(3.3.1SE)
(3.3.1SE)
Scalability
WLC2504
(7.6)
WLC5760
(7.6)
WLC5508
(7.6)
WiSM2
(7.6)
Max APs Supported per MC
25
50
75
1000
500
1000
Max APs Supported in overall Mobility Domain
200
250
5400
72000
36000
72000
Max Clients Supported per MC
1000
2000
1000
12000
7000
15000
Max Clients Supported in overall Mobility Domain
8000
16000
72000
864000
504000
1.08M
Max number of MC in Mobility Domain
72
72
72
72
Max number of MC in Mobility Group
24
24
24
24
Max number of MAs in Sub-domain (per MC)
16
16
350
350
350
350
Max number of SPGs in Mobility Sub-Domain (per MC)
24
24
24
24
Max number of MAs in a SPG
16
16
64
64
64
64
64
64
16
512
512
512
Max number of WLANs
TECCRS-2678
Cisco Public
45
ExisBng(Wireless(Deployments((Architecture(Refresher%
%
Converged(Access((Terminology(and(Building(Blocks(
%
Converged%Access%%Trac%Flows%and%Roaming%
(
(
TECCRS-2678
Cisco Public
46
Converged Access
Roaming Point of Presence (PoP), Point of Attachment (PoA)

Point of Presence (PoP) vs.
Point of Attachment (PoA)
MC
PoP is where the wireless user

is seen to be within the wired
portion of the network
PoA is where the wireless user
has roamed to while mobile
Before a user roams, PoP and
PoA are in the same place
SPG
MA
Note for the purposes of illustrating

MA
MA
PoP
PoA
AP
TECCRS-2678
AP
AP
If users
associate and
remain stationary,
this is their
traffic flow
roaming, we are showing the purple

connections herein that indicate the
connections between the MAs and their
corresponding MC for the Switch Peer
Group (or Groups) involved on each slide
notice that, in this example, the traffic
does NOT flow through the MC
Cisco Public
47
Converged Access
Very
Traffic Flow and Roaming Branch, Single Catalyst 3x50 Stack common
Notice how the 3x50 switch stack
shown is an MC (as well as an MA)
in a branch such as this with 50 APs
or less, no discrete controller is
necessarily required
roaming
case
MC
Central Location
Guest Anchor
CAPWAP tunnel
to Guest Anchor
MC
3x50
Switch
MA
PoP
PoA
PI
MA
WAN
CAPWAP
tunnels
control and
data path
ISE
DMZ
Roaming
across Stack
(small branch)
Roaming,
Single Catalyst 3x50 Switch Stack
In this example, the user roams within their 3x50-based switch stack
for a small Branch site, this may be the only type of roam
Roaming within a stack does not change the users PoP or PoA
since the stack implements a single MA (redundant within the stack),
and thus a user that roams to another AP serviced by the same stack
does not cause a PoA move (PoA stays local to the stack)
TECCRS-2678
Cisco Public
48
Converged Access
Traffic Flow
WiSM2s(/(
5508s(/(5760s(
CUCM(
MC
MA
MC
MA
PSTN
Converged
policies and
services for
wired and
wireless
users
Traffic Flows, Comparison

(Converged Access)
Now, our VoIP user is on a Cisco
Converged Access network, and is
again making a call from a wireless
handset to a wired handset
Traffic
does not
flow
via MCs
More efficient
since traffic flows
are localized to
the 3x50 switch
Performance
Increase
SPG(
PoP%
Wired and
wireless policies
implemented
on 3x50 switch
TECCRS-2678
PoA%

traffic is localized to their Peer
Group, below the distribution
layer, in both directions
In this example, a total of 1 hop
is incurred for each direction
of the traffic path (assuming
no roaming) two additional
hops may be incurred for routing
Cisco Public
49
Converged Access
Traffic Flow and Roaming Branch, L2 / L3 Roam (within SPG)

Roaming
across Stacks
Very
common
roaming
case
Roaming, Within a Switch

Peer Group (Branch)
(larger branch)
Now, lets examine a roam at a larger branch, with multiple

3x50-based switch stacks joined together via a distribution layer
uRPF, Symmetrical
Routing, NetFlow,
Stateful Policy
Application
SPG
MC
MA
MA
MA
PoP
In this example, the larger Branch site consists of a single

Switch Peer Group and the user roams within that SPG
again, at a larger Branch such as this, this may be
the only type of roam
The user may or may not have roamed across an L3
boundary (depends on wired setup) however, users are
always* taken back to their PoP for policy application
PoA
Again, notice how the 3x50 switch stack on the

left is an MC (as well as an MA) in this picture
in a larger branch such as this with 50 APs
or less, no discrete controller is necessarily required
TECCRS-2678
Cisco Public
* Adjustable via setting,

may be useful for L2
roams (detailed on slides
in following section of
this slide deck)
50
Converged Access
Traffic Flow and Roaming Campus, L2 / L3 Roam (within SPG)

Very
common
roaming
case
Roaming
within an SPG
MC
Roaming,
Within an SPG (Campus)
(L3 behaviour
and default L2
behaviour)
Now, lets examine a few

more types of user roams
In this example, the user roams

within their Switch Peer Group
since SPGs are typically
Note the traffic in this most
formed around floors or other
common type of roam did not
geographically-close areas,
have to be transported back to, or
this is the most likely and
via, the MC (controller) servicing
most common type of roam
SPG
MA
PoP%
PoA%
MA
MA
the Switch Peer Group traffic

stayed local to the SPG only
(i.e. under the distribution layer
in this example not back
through the core).
This is an important
consideration for Switch Peer
Group, traffic flow, and
Controller scalability.
TECCRS-2678
The user may or may not have

roamed across an L3 boundary
(depends on wired setup)
however, users are always*
taken back to their PoP
for policy application
Cisco Public
51
Converged Access
Traffic Flow with Intra-SPG Roam

WiSM2s(/(
5508s(/(5760s(
MC
MC
PSTN
CUCM(
Converged
policies and
services for
wired and
wireless
users
Traffic Flows, Comparison

(Converged Access)
Now, our VoIP user on the Cisco
Converged Access network roams,
while a call is in progress between
the wireless and wired handsets
Traffic
still does
not flow
via MCs
More efficient
since traffic flows
are still localized
to the SPG
Performance &
Scalability
SPG(
PoP%
Wired and
wireless policies
implemented
on 3x50 switch
TECCRS-2678
MA
MA
MA
MA
PoA%

traffic is still localized to their
Switch Peer Group, below the
distribution layer,
in both directions
In this example, a total of 3 hops
is incurred for each direction
of the traffic path (assuming
intra-SPG roaming) two
additional hops may be
incurred for routing
Cisco Public
52
Converged Access
Traffic Flow and Roaming Campus, L2 / L3 Roam (across SPGs)

Less
common
roaming
case
Roaming,
Across SPGs (Campus)
MC

In this example, the user
roams across Switch Peer
Groups since SPGs are
typically formed around floors
or other geographically-close
areas, this type of roam
is possible, but less likely
than roaming within an SPG
Roaming
across SPGs
(L3 separation
assumed at
access layer)
SPG(
SPG(
MA
MA
MA
MA
MA
MA
PoP%
PoA%
TECCRS-2678
Cisco Public
Typically, this type of roam

will take place across an L3
boundary (depends on wired
setup) however, users are
always* taken back to their
PoP for policy application
53
Converged Access
Traffic Flow and Roaming Campus, L2 / L3 Roam (across SPGs & MCs)
Least
common
roaming
case
MC
Roaming, Across
SPGs and MCs (Campus)
MC
MTE
MTE
Roaming
across
Controllers
(L3 separation
assumed at
access layer)
SPG(

In this example, the user roams

across Switch Peer Groups and
Controllers (within the same
Mobility Group) again, this
type of roam is possible, but
less likely than intra-SPG
roaming
SPG(
MA
MA
MA
MA
MA
MA
PoP%
PoA%
Anchor
TECCRS-2678
Foreign
Cisco Public
Typically, this type of roam

will take place across an L3
boundary (depends on wired
setup) however, users are
always* taken back to their
PoP for policy application
54
Converged Access
Catalyst 3x50-based MCs Functionality

As we saw previously, we can also optionally use a Catalyst 3x50 switch
as an MC + co-located MA for a Switch Peer Group lets explore this in more detail
Single Catalyst 3x50 MC supported per Switch Peer Group
which can have up to 16 x MAs (stacks) per 3x50-based MC
Single Catalyst 3850 MC can handle up to 50 APs
and 2,000 clients total (therefore, up to 50 APs
and 2,000 clients in a Catalyst 3850-based
Switch Peer Group). Single Catalyst 3650
MC can handle up to 25 APs and 1,000
clients total (therefore, up to 25 APs
and 1,000 clients total in a 3650-based
Switch Peer Group).
MC handles
inter-SPG
roaming,
RRM, Guest
Access, etc.
Guest Anchor
MC
MA
ISE
But what if
we want to scale
larger, without
implementing a
discrete controller?
SPG
MC
MA
MA
MA
Is this possible?
More scalable MC
capability can be
provided by 5760 /
5508 / WiSM2
TECCRS-2678
PI
Cisco Public
55
Converged Access
Catalyst 3x50-based MCs Scaling

Switch Peer Group / Mobility Group Scaling with Catalyst 3x50
Up to 8 x Catalyst 3x50 MCs can be formed into a Mobility Group
Guest Anchor
Up to 250 APs total and 16,000 clients

supported (maximum) across a Mobility
Group made up solely of Catalyst 3850s
MC
Up to 200 APs total and 8,000 clients

supported (maximum) across a Mobility
Group made up solely of Catalyst 3650s
Licensing
is per MC
not pooled
across MCs
Guest tunneling is per MC

to Guest Anchor controller
MA
ISE
PI
SPG$
!"#
SPG$
!"#
SPG$
Mobility Group
!"#
SPG$
!"#
SPG$
!"#
SPG$
!"#
RRM, etc. is
coordinated
across the
MCs in the
same Mobility
Group
TECCRS-2678
SPG
MC
MA
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
!"#
Full mesh of MCs

across Mobility Group
SPG
MA
MA
MC
MA
MA
MA
Cisco Public
56
Design%and%Deployment%Op5ons,%and%Migra5on%%
(
Converged%Access%%Design%Op5ons%%(Branch%and%Campus)%
TECCRS-2678
Cisco Public
57
Converged Access Small Branch
No Discrete Controllers, Catalyst 3x50s as MCs / MAs
Up to
25 / 50 APs
Central Location
ISE
WAN
PI
Guest Anchor(s)
DMZ
Applicable
to a Small
Branch
Deployment
Characteristics
MC
MA
Independent of WAN link (compared to FlexConnect) as

bandwidth and latency are a concern only for Guest traffic
Allows for Advanced QoS, WAN optimization,
NetFlow, and other services for wireless and wired traffic
Supports Layer 3 roaming
Supports VideoStream and optimized multicast
Good availability due to MA/MC redundancy within the 3x50 stack provides
wireless continuity with either WAN outage or switch failure within the stack
TECCRS-2678
Cisco Public
58
Converged Access Small / Medium Branch
No Discrete Controllers, Catalyst 3x50s as MCs / MAs, Single SPG
Up to
25 / 50 APs
Central Location
ISE
WAN
Guest Anchor(s)
Deployment
could consist
of multiple stacks
one stack as MC/MA,
rest of stacks as
MAs only
DMZ
PI
Applicable
to a Small to
Medium Branch
Deployment
Characteristics
No discrete controllers deployed, even with multiple
wiring closets
Allows for Advanced QoS, WAN optimization, NetFlow,
and other services for wireless ad wired traffic
Si

Switch
Peer
Group
MC
MA
TECCRS-2678
MA
MA
MA

Good availability due to MA/MC redundancy within the
switch stacks provides wireless continuity with either WAN
outage or switch failure within the stack
Cisco Public
59
Converged Access Large Branch
No Discrete Controllers, Catalyst 3x50s as MCs / MAs, Multiple SPGs

Scalability
up to 8 x 3x50-based MCs
Up to
200 / 250
APs
MC
ISE
WAN
Guest Anchor(s)
DMZ
Note MCs handling

one or more SPGs each,
all MCs meshed into a
single Mobility Group for
the site. 1 Guest tunnel
per MC to Anchor.
Mobility Group
Switch
Peer
Groups
Central Location
MA
PI
Applicable
to a Larger
Branch
Deployment
Characteristics
No discrete controllers deployed, even at a larger branch
Si
Allows for Advanced QoS, WAN optimization, NetFlow,

and other services for wireless ad wired traffic
Si

MA
MC
MA
MA

Good availability due to MA/MC redundancy within the switch
stacks provides wireless continuity with either WAN outage
or switch failure within the stack
TECCRS-2678
Cisco Public
60
Converged Access Small Campus
Up to 200 / 250
APs
Catalyst 3x50s as MC s / MAs, Multiple SPGs

Scalability up to 8 x 3x50-based MCs
Characteristics
Data Center
MC
No discrete controllers deployed,

even at a small Campus
Allows for Advanced QoS,
NetFlow, and other services
for wireless and wired traffic
ISE
MA
PI
Guest Anchors
Si
MC
Campus / Metro
MA
MO
Si
(Optional)

Supports roaming between
distribution layers, keeps
many roams localized
below dist. layer
Si
Si
Si
Si
Si
Switch
Peer
Groups
MC
MA
TECCRS-2678
Si
Mobility Group
MA
MC
Good availability due to MC/MA

redundancy within the Cat 3x50
stacks moderately scalable
using 3x50s (up to 8 in total)
as MCs, combined with a single
Mobility Group in the deployment
MA
MA
Applicable
to a Small
Campus
Deployment
Note MCs handling one

or more SPGs each, all MCs
meshed into a single Mobility
Group for the site. Guest tunnel
per MC to Anchor.
Cisco Public
61
Converged Access Large Campus
>250 APs
Centralized Controllers as MCs, 3x50s as MAs Only

5760s /
WiSM2s /
5508s
Data Center
ISE
PI
Campus Services
Guest Anchors
Si
MC
MC
Campus / Metro
Si
MO
Si
Si
Applicable
to a Larger
Campus
(Optional)
MC
Mobility
Group
Characteristics
Si
Use of discrete controllers as MCs, combined with Catalyst 3x50

switches as MAs, provides for a very scalable solution
Si
Allows for Advanced QoS, NetFlow,

and other services for wireless and wired traffic
Si
Si
Si
Switch
Peer
Groups
MA
TECCRS-2678
Si
MA
Supports Layer 3 roaming provides scalability by

keeping many roams localized to SPGs (below dist.)
MA
MA
Good availability due to MA

redundancy (switch stacks) and
MC redundancy (controllers)
Simplified Mobility deployment using
switches as MAs only, vs. the use
of switches as MCs / MAs
Cisco Public
62
Converged Access Large Campus
>250 APs
Distributed Controllers as MCs, 3x50s as MAs Only

Characteristics
Data Center
Use of discrete controllers as MCs,

combined with switches as MAs,
provides for a very
scalable solution
Use of distributed
controllers (vs. centralized
in DC) may be more
appropriate in some
wireless deployments
Switch
Peer
Groups
MC
Campus / Metro
MO
Si
TECCRS-2678
(Optional)
Supports Layer 3 roaming provides scalability by keeping

many roams localized to SPGs
(below distribution)
Si
MC
MC
Si
Si
MA
Si
MA
Applicable
to a Larger
Campus
Allows for Advanced QoS, NetFlow, and other services

for wireless and wired traffic
Mobility
Group
MC
Si
PI
Guest Anchors
Si
Si
5760s /
WiSM2s /
5508s
ISE
MA
MA
Good availability due to MA

redundancy (switch stacks) and
MC redundancy (controllers)
Simplified Mobility deployment
using switches as MAs only,
vs. the use of switches
as MCs / MAs)
Cisco Public
63
WrapYUp%and%Final%Thoughts%%
TECCRS-2678
Cisco Public
64
Bringing Together Wired and Wireless
How Are We Addressing This Shift?

Control plane functionality
on NG Controller
(also possible on upgraded 5508s, WiSM2s for

brownfield deployments, or NG Converged Access
switches for small, branch deployments)
Next-Generation WLAN Controller (5760)
Controller
Data plane functionality

on NG Switches
(also possible on NG Controllers, for deployments
in which a centralized approach is preferred)
Next-Generation Switches (Catalyst 3850s)
Enabled by Ciscos strength

in Silicon and Systems
UADP ASIC
TECCRS-2678
An Evolutionary Advance to Ciscos Wired

+ Wireless Portfolio, to address device and
bandwidth scale, and services demands .
Cisco Public
65

Evolving from Overlay
Data Center /
Service block
ISE
Existing Unified Wireless Deployment Today
PI
Intranet
Mobility Group
Well-known
and well-proven
Prior to Migration
to Converged
Access
EtherIP Mobility Tunnel
5508 / WiSM2
5508 / WiSM2
Separate
policies and
services for wired
and wireless
users
Wireless policies
implemented
on controller
Wired policies
implemented
on switch
TECCRS-2678
All wireless
traffic centralized
via controllers
as shown
CAPWAP
Tunnels
CAPWAP
Tunnels
Cisco Public
66

To Integrated
Data Center /
Service block
ISE
Increase in visibility
and control (NetFlow,
Advanced QoS, etc)
via local termination
of both wired and
wireless traffic
PI
Intranet
Mobility Group
MC
Implementation
of End-to-End
Converged
Access
Deployment
Switch
Peer
Groups
CAPWAP Mobility Tunnel
MA
5760 or upgraded
WiSM2 / 5508
MA
MA
5760 or upgraded
WiSM2 / 5508
MA
MA
Switch
Peer
Groups
MA
MA
TECCRS-2678
MA
MA
CAPWAP
Tunnels
CAPWAP
Tunnels
Wired and
wireless policies
implemented
on 3x50 switch
MA
MC
Cisco Public
Increase in
performance and
scalability via local
termination of both
wired and wireless
traffic
Catalyst 3x50
switches
Converged
policies and
services for wired
and wireless
users
67
Bringing Together Wired and Wireless
With a Next-Generation Deployment and Solution

Mobility Domain
ISE
MO#
PI
Cisco
Converged
Access
Mobility Group
MC
MC
Deployment
Sub-Domain
#1
SPG
Sub-Domain
#2
An Evolutionary
Advance to Ciscos
Wired + Wireless
Portfolio, to address
device and bandwidth
scale, and services
demands .
SPG
MA
TECCRS-2678
MA
MA
MA
MA
MA
Cisco Public
68
Converged Access
Tell Us How We Did!
Did We Achieve Our Objective?

Do You Have a Better Understanding
of what Converged Access is
of how Converged Access works
and how you would use it
in your network designs?
Dont Forget
to fill out your evaluations!
TECCRS-2678
Corner
Stone
Cisco Public
69

Coverged Access Ing PDF

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Coverged Access Ing PDF

Загружено:

Авторское право:

Доступные форматы

Cisco Learning Express

GVE Services offered through Cisco Partner Plus

Level I Pre Sales

NEW FY15 - Level II Escalated Pre

Level II Pre Sales Technical Support.

2014 Cisco and/or its affiliates. All rights reserved.

Cisco Public EVALUATIONS!%%Tell(us(how(we(did(((

2014 Cisco and/or its affiliates. All rights reserved.

Performance Protection for

Enterprise Wireless Evolution

From Best-Effort to Mission-Critical and Very High Density

Very High Density

2014 Cisco and/or its affiliates. All rights reserved.

How Many Mobile Data Devices

Do You Think You Will Carry Everywhere in 2016?

2014 Cisco and/or its affiliates. All rights reserved.

Uncompromised User Experience in Any Workspace

2014 Cisco and/or its affiliates. All rights reserved.

One Network, with Converged Access

Converged Wired / Wireless Access

Cisco Converged Access Deployment

2014 Cisco and/or its affiliates. All rights reserved.

Converged Access Components

Who?( What?( When?(Where?( How?(

2014 Cisco and/or its affiliates. All rights reserved.

Catalyst 3850 and 3650 Switches

Cisco Converged Access Deployment

Single Platform for Wired and Wireless

Cisco Converged Access Deployment

Cisco Converged Access Deployment

New Catalyst 3650 Switch

Wireless LAN Controller (WLC) 5760

2014 Cisco and/or its affiliates. All rights reserved.

Unified Access Includes Converged Access

One Policy, One Management,

Unparalleled Deployment Flexibility

2014 Cisco and/or its affiliates. All rights reserved.

2014 Cisco and/or its affiliates. All rights reserved.

Network Requirements Driving Wireless Evolution

Weve Been Here Before

Control plane functionality on NG Controller

Data plane functionality on NG Switches

EoIP Mobility Tunnel ( < 7.2)

Existing Unified Wireless Deployment today

SSID2 SSID1 SSID3

Inter-Controller (Guest Anchor)

AP / WLC CAPWAP Tunnels are an IETF Standard

Inter-WLC Mobility Tunnels

2014 Cisco and/or its affiliates. All rights reserved.

Existing Unified Wireless Deployment today

EoIP Mobility Tunnel ( < 7.2)

SSID2 SSID1 SSID3

Existing Unified Wireless Deployment today

Mobility Group, Details

Group of Wireless LAN Controllers (WLCs) in

a network with the same Mobility Group name

Provides Seamless Mobility and

Fast Roaming for clients

Up to 24 WLCs members in one Mobility

Group, statically configured

Full mesh of tunnels between members

Messages can be sent using Multicast