WiNG 5 Architecture Examples 2012 Michael Elin, CCIE#5360 [email protected] MOTOROLA...

16
WiNG 5 Architecture Examples 2012 Michael Elin, CCIE#5360 [email protected] MOTOROLA SOLUTIONS

Transcript of WiNG 5 Architecture Examples 2012 Michael Elin, CCIE#5360 [email protected] MOTOROLA...

WiNG 5Architecture Examples

2012

Michael Elin, CCIE#[email protected]

MOTOROLA SOLUTIONS

PAGE 2

AGENDA

ARCHITECTURE Considerations & Products positioning :

Deployment on 1 smallautonomous site

PAGE 3

Virtual Controller Concept

Small Deployments

Wired network

AP 6511 is:VIRTUAL CONTROLLER

1

Others AP 6511 are automatically

ADOPTED by Virtual Controller

2 Up to 24

ONE SMALL AUTONOMOUS SITE (< 25 APs)

1 RF-DOMAIN

3 4

• The AP « Virtual Controller »:• Is the single Point of Management for 24 APs of the same TYPE• Can manage ONLY ONE “RF-Domain” (ONE SITE)

MRF DOMAINMANAGER

PAGE 4

AP as a Controller (Virtual Controller) - Considerations

Small Deployments

• “STARTER KIT” solution :• Better than Autonomous AP solutions• When RFS x000 is not needed or too expensive

• NO automatic REDUNDANT “Virtual Controller” in this concept

• NO RFS in this architecture

• Scalable solution :• If redundant management solution is needed

• If # of Access Point grows over 25

Replace AP « Virtual Controller »

by RFS

PAGE 5

With AP 6511 :

Small Deployments

Extended to others 4 digits APs in new release

• WiNG 5.2• AP 6532• AP 7131N

• Future release• AP 6521• AP 7161

• WiNG 5.0.1• WiNG 5.1

PAGE 6

AGENDA

ARCHITECTURE Considerations & Products positioning :

Deployment on 1 medium to large size site

PAGE 7

With a Controller RFS that provides:

Medium Deployments

Wired network

• Management features with redundant capabilities• Advanced Security features (Role Based firewall)• Wireless IPS (WIPS) services,• RF Domain management (eg. SMART-RF) for more than 25 APs• The Clustering Mode provides a centralized point of management

RFS seriesCONTROLLER

CLUSTERActive/Active

or Active/Passive

1 2 N = 36 with RFS 4000 256 with RFS 6000 1024 with RFS 7000

ONE MEDIUM / LARGE AUTONOMOUS SITE (>25 APs)

1 RF-DOMAINM

RF DOMAINMANAGER

PAGE 8

AGENDA

ARCHITECTURE Considerations & Products positioning :

Deployment onmany sites

PAGE 9

Medium / Large Deployments

Cluster of 2 RFS ControllersSingle point of Management

Architecture Type: A Campus with many buildings

Building #2

Building #1

3 digits AP & Local bridging

KO

X

3 digits AP & Tunneling

X

KO

Routed LAN

Building #3

1 RF-DOMAIN1 RF-DOMAIN

1 RF-DOMAIN

(<25 APs)(<25 APs)

• Controller RFS can manage MULTIPLE “RF-Domain”• 25 Access Points or less on each remote “RF-Domain”

MRF DOMAINMANAGER

MM

PAGE 10

Medium / Large Deployments

Cluster of 2 RFS ControllersSingle point of Management

Architecture Type: A Headquarter and some remote sites

Regional Office #1

Headquarter

4 digits AP & Local bridging

OK

X

4 digits AP & Local bridging

X

OK

WAN

Regional Office #2

1 RF-DOMAIN

1 RF-DOMAIN 1 RF-DOMAIN

• Controller RFS can manage MULTIPLE “RF-Domain”• 25 Access Points or less on each Remote “RF-Domain”

(<25 APs) (<25 APs)

MRF DOMAINMANAGER

MM

PAGE 11

Medium / Large Deployments

• Access Points on different sites can be centrally managed with RFS x000:• 4 digits APs – Continue to work in case of a WAN link failure • 3 digits APs – Service disruption in case of a WAN link failure

• Number of AP Licence on RFS x000 = Sum of Access Point on each site

• Access Point Adoption : Layer 3 on Remote sites

• DHCP option permit a zero configuration deployment on Layer 3 remote sites:• Option 189 : value = Controller IP address• Option 191 : value = Controller IP address with 2 pools

(ex. Local / Remote)• Option 192 : value = 1 (force 4 digit Access Point adoption)

Architecture Considerations: Campus or Remote sites

PAGE 12

AGENDA

ARCHITECTURE Considerations & Products positioning :

Deploymenton many small size sites

PAGE 13

Large Deployments

• NX 9000 behaves as a RFS controller with Control Plane ONLY (Management)• Up to 10 000 Access Points • WiNG 5 introduces RF Domain Manager at the Access Point level• RF Domain Manager brings local Services (ex. SMART-RF)

Architecture with small remote sites and NX 9000

Shop #04

Shop #05Shop #01

NOC / Data Center

NX 9000

Local bridging

Local bridgingLocal bridging

RF Domain #05

RF DOMAIN MANAGER

WAN

RF Domain #04

RF Domain #01

Shop #02Local bridging

RF Domain #02

Shop #03

Local bridging

RF Domain #03

< 24 APs

< 24 APs

< 24 APs

< 24 APs

< 24 APs

M

M

M

M

M

Single point of Management

PAGE 14

AGENDA

ARCHITECTURE Considerations & Products positioning :

Deployment onmany largesize sites

PAGE 15

Large Deployments

• RFS on each site for large number of AP, Clustering for high availability• Centralized Supervision with AirDefense Services Platform (ADSP)

(Infrastructure Management license)• With Sensors, ADSP adds Wireless IDS / IPS features

Architecture with many large sites and ADSP

Factory #1 Factory #2

WareHouseHeadquarter

NOC / Data Center

AirDefense Services Platform

WAN

RF-DOMAIN

#2

RF-DOMAIN

#1

RF-DOMAIN

#3

RF-DOMAIN

#4

> 25 APs

> 25 APs > 25 APs

> 25 APs

M

M M

M

CentralizedSupervision

& Security

Sensor

Sensor

Sensor

Sensor

THANK YOU…

MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the property of their respective owners. © 2010 Motorola, Inc. All rights reserved.

iProtect Classification as Appropriate