Table of Contents
Advertisement
Multiple RAPs
If multiple RAPs are to be deployed, the purpose for deploying these RAPs needs to be considered. If
the RAPs are being deployed to provide hardware diversity, the additional RAP(s) should be deployed
on the same channel as the primary RAP to minimize the convergence time in a scenario where the mesh
transfers from one RAP to another. When planning RAP hardware diversity, the 32 MAPs per RAP
limitation should be remembered.
If additional RAPs are deployed to primarily provide additional capacity, then the additional RAPs
should be deployed on a different channel than its neighboring RAPs to minimize the interference on the
backhaul channels.
Adding a second RAP on a different channel also reduces the collision domain through channel planning
or through RAP cell splitting. Channel planning allocates different non-overlapping channels to mesh
nodes in the same collision domain to minimize the collision probability. RAP cell splitting is a simple,
yet effective, way to reduce the collision domain. Instead of deploying one RAP with omni-directional
antennas in a mesh network, two or more RAPs with directional antennas can be deployed. These RAPs
collocate with each other and operate on different frequency channels, thus dividing a large collision
domain into several smaller ones that operate independently.
If the mesh access point bridging features are being used with multiple RAPs, these RAPs should all be
on the same subnet to ensure that a consistent subnet is provided for bridge clients.
If you build your mesh with multiple RAPs on different subnets, MAP convergence times increase if a
MAP has to failover to another RAP on a different subnet. One way to limit this from happening is to
use different BGNs for segments in your network that are separated by subnet boundaries.
Indoor WLAN Network to Outdoor Mesh
Mobility groups can be shared between outdoor mesh networks and indoor WLAN networks. It is also
possible for a controller to control indoor (1130, 1240) and outdoor mesh access points (1522, 1524)
simultaneously. The same WLANs are broadcast out both the indoor outdoor mesh access points.
Connecting the Cisco 1520 Series Mesh Access Point to Your
Network
The wireless mesh terminates on two points on the wired network. The first location is where the RAP
attaches to the wired network, and where all bridged traffic connects to the wired network. The second
location is where the CAPWAP controller connects to the wired network; this is where WLAN client
traffic from the mesh network connects to the wired network. This is shown schematically in
The WLAN client traffic from CAPWAP is tunneled at Layer 2, and matching WLANs should terminate
on the same switch VLAN as where the controllers are collocated. The security and network
configuration for each of the WLANs on the mesh depend on the security capabilities of the network to
which the controller is connected.
Note
When an HSRP configuration is in operation on a mesh network, Cisco recommends the In-Out multicast
mode be configured. For more details on multicast configuration, refer to
Multicast on the Mesh Network" section on page
Cisco Aironet 1520, 1130, 1240 Series Wireless Mesh Access Points, Design and Deployment Guide, Release 6.0
OL-20213-01
Connecting the Cisco 1520 Series Mesh Access Point to Your Network
119.
Figure
36.
"Using the CLI to Enable
53
Hide quick links:
Advertisement
Table of Contents
