1. Deploying a Million-AP WiFi Network
Architecture for Massively scalable deployment
RAJESH GANDHI

2. Considerations for large scale deployment
Buyer
Cost
Planner:
Scalability
Low Foot print
Easy Deployment
Security
Flexibility
Planning Tools
O&M
Manageability
Reliability
Monitoring

3. Low Cost
Capex
COTS Hardware
AP from factory
Competitive SW Cost
Opex:
Less manpower
Less training requirements
Less Power, Battery Bank & Fuel

4. Deployment & Foot Print
Ease of deployment
Plug & Play (Zero Touch deployment)
Auto discovery and management
Low Foot Print
Light weight management, Efficient Protocol
High Density Packing ( More #AP/Server)
Multi-tenancy
Green Deployment

5. Scalability & Flexibility
Start small, Grow as per needs
Add capacity by throwing more HW resources
VM based, Multiple VM per blade
Flexibility
Separate Data & Control plane

6. Manageability & Monitoring
Mass Manageability
Centralized Mass Configuration & Version upgrade
Location based hierarchy
Template, inheritance based policies
Automated Provisioning
Easy Monitoring
Centralized Monitoring
Real time alerts
Performance Reporting
Integration to 3rd party systems

7. Security & Reliability
Security & compliance
Best in class security
Compliance reports
Reliability
Highly Available Architecture
VM based Local Redundancy & Disaster Recovery
Multiple Data Centers for HA

8. Top Features
Smart phone App for management (Nano)
RF Planner

9. Large scale deployment Cloud Architecture
Centralized NOC
Mojo WiFi Cloud
Billing
AAA dB
DHCP
Central Switch
Management Plane
User Authentication
Local Break Out
Internet
CSS
Typical Site WiFi Network

10. Geographical Redundancy: Logical representation
Cloud Deployment Model
Two site GR model.
LR: N+1 or N+2.
Periodic data replication.
Site A acts as redundant site for Site B & vice versa. . VM VM VM VM VM VM VM VM
Hypervisor
Point to Point Connectivity
Hypervisor
Chassis
Chassis
Storage
Storage
Replication
Site A
Site B

11. Total HW Requirement (for LR+GR)
Suggested HW
Chassis
HP C-700
Blade
BL460Gen9
2 x Intel Xeon E5-2690v3 (12 core)
128 GB RAM
2 x 10G CAN
SAN Storage
VNX-5600
( IOPS)

12. Conventional Solution versus Mojo Cloud for 1M AP Deployment
Conventional solutions
Racks 12 53
Controllers
200
Zero
Appliances
EMS
100
Zero
200
Zero
Appliances
Security
Many field teams needed to support distributed physical deployments
Small
Central
Team
Team

13. Deployment Effort Conventional Solution Mojo 3 weeks 1 week 5 days
Initial Deployment Tasks
Conventional Solution
Mojo
Pre-Deployment rack space planning and logistics, including high availability design
3 weeks
1 week
Setting up IP routing across switches, controllers etc.
5 days
2 days
Hardware needed at every site
Yes No
Team Needed for Deployment and Handover
Post Deployment Tasks
Conventional Solution
Mojo
Scalability
Needs to be managed at every site
Easier as there are fewer number of sites
Monitoring
No comprehensive network view in multi-controllers environment
Why ?
Centralized EMS needed to get this view making it cost dominated feature
Single pane view of the network.
Country to Floor granularity with Mojo Navigator

14. High Level requirements of cloud managed massively scalable deployment model
Centrally managed, Single Pan of glass visibility
Start small, Grow as per requirements
COTS hardware for servers
AP Hardware at factory cost
Fully redundant – Highly available
Green deployment, Low footprint
Zero Touch deployment
NW Set up issue to be done