Campus lan and Wireless lan solution Design Guide

 
Cisco DNA Spaces network architectures 
Figure 27. 
An on premises deployment of Cisco DNA Spaces is required for the following: 
● 
Hyperlocation
—To use the Cisco Aironet 4800 Series or 3700 Series APs with a hyperlocation antenna, or 
to use fast path on all APs on an on-premises server, it is required to receive fast path UDP data on port 
2003 from the access point and use it for location calculations. 
● 
Integration with Cisco DNA Center or Prime Infrastructure
—To provide location data to Cisco DNA 
Center or Prime Infrastructure, an on-premise server is currently required. 
Wireless design models 
This guide describes the following design models and their recommended use: 
● 
Centralized (local-mode) design model 
● 
Cisco FlexConnect design model 
● 
Cisco SD-Access Wireless design model 
● 
Cisco Catalyst 9800 Embedded on Catalyst 9100 Series APs (EWC) design model 
Centralized (local-mode) design model
A centralized design model, also known as a local-mode design model, is recommended primarily for large site 
deployments. The benefits of a centralized design include IP address management, simplified configuration and 
troubleshooting, and roaming at scale. In a centralized design model, the WLAN controller and APs are both 
located within the same site.
You can connect the WLAN controller to a data center services block, a separate services block off of the 
campus core, or a LAN distribution layer. Wireless traffic between WLAN clients and the LAN is tunneled by 
using the control and provisioning of wireless APs (CAPWAP) protocol between the controller and the AP. This 
has the advantage of decoupling the subnet on which the wireless clients terminate from the AP; requiring the 
availability of the wireless client VLAN only at the controller, thus simplifying the deployment. 

---

© 2020 Cisco and/or its affiliates. All rights reserved. 
Page 40 of 76