- Preface
- Mesh Network Components
- Mesh Deployment Modes
- Design Considerations
- Air Time Fairness in Mesh Deployments rel 8.4
- Site Preparation and Planning
- Connecting the Cisco 1500 Series Mesh Access Points to the Network
- Checking the Health of the Network
- Troubleshooting
- Managing Mesh Access Points with Cisco Prime Infrastructure
- Index
Design Considerations
This chapter describes important design considerations and provides an example of a wireless mesh design.
Each outdoor wireless mesh deployment is unique, and each environment has its own challenges with available locations, obstructions, and available network infrastructure. Design requirements driven by expected users, traffic, and availability needs are also major design criteria. This chapter contains the following sections:
Wireless Mesh Constraints
The following are a few system characteristics to consider when you design and build a wireless mesh network. Some of these characteristics apply to the backhaul network design and others to the CAPWAP controller design:
Wireless Backhaul Data Rate
Backhaul is used to create only the wireless connection between the access points. The backhaul interface is 802.11a/n/ac/g depending upon the access point. The rate selection is important for effective use of the available RF spectrum. The rate can also affect the throughput of client devices, and throughput is an important metric used by industry publications to evaluate vendor devices.
Dynamic Rate Adaptation (DRA) introduces a process to estimate optimal transmission rate for packet transmissions. It is important to select rates correctly. If the rate is too high, packet transmissions fail resulting in communication failure. If the rate is too low, the available channel bandwidth is not used, resulting in inferior products, and the potential for catastrophic network congestion and collapse.
Data rates also affect the RF coverage and network performance. Lower data rates, for example 6 Mbps, can extend farther from the access point than can higher data rates, for example 1300 Mbps. As a result, the data rate affects cell coverage and consequently the number of access points required. Different data rates are achieved by sending a more redundant signal on the wireless link, allowing data to be easily recovered from noise. The number of symbols sent out for a packet at the 1-Mbps data rate is higher than the number of symbols used for the same packet at 11 Mbps. Therefore, sending data at the lower bit rates takes more time than sending the equivalent data at a higher bit rate, resulting in reduced throughput.
A lower bit rate might allow a greater distance between MAPs, but there are likely to be gaps in the WLAN client coverage, and the capacity of the backhaul network is reduced. An increased bit rate for the backhaul network either requires more MAPs or results in a reduced SNR between MAPs, limiting mesh reliability and interconnection.
Note | The data rate can be set on the backhaul on a per AP basis. It is not a global command. |
The required minimum LinkSNR for backhaul links per data rate is shown in Table 1.
54 |
31 |
48 |
29 |
36 |
26 |
24 |
22 |
18 |
18 |
12 |
16 |
9 |
15 |
6 |
14 |
-
The required minimum LinkSNR value is driven by the data rate and the following formula: Minimum SNR + fade margin.
Table 2 summarizes the calculation by data rate.
135 |
1 |
26.3 |
157.5 |
1 |
27.3 |
30 |
2 |
12.3 |
60 |
2 |
14.3 |
90 |
2 |
16.3 |
120 |
2 |
20.3 |
180 |
2 |
24.3 |
240 |
2 |
27.3 |
270 |
2 |
29.3 |
300 |
2 |
30.3 |
-
If we take into account the effect of MRC for calculating Minimum Required Link SNR. Table 3 shows the required LinkSNR for 802.11a/g (2.4 GHz and 5 GHz) for AP1552 and 1522 with 3 Rx antennas (MRC gain).
If we consider only 802.11n rates, then Table 4 shows LinkSNR requirements with AP1552 for 2.4 and 5 GHz.
Controller Planning
The following items affect the number of controllers required in a mesh network:
-
Mesh access points (RAPs and MAPs) in the network.
The wired network that connects the RAP and controllers can affect the total number of access points supported in the network. If this network allows the controllers to be equally available to all access points without any impact on WLAN performance, the access points can be evenly distributed across all controllers for maximum efficiency. If this is not the case, and controllers are grouped into various clusters or PoPs, the overall number of access points and coverage are reduced.
-
Number of mesh access points (RAPs and MAPs) supported per controller. See Table 1.
For clarity, nonmesh access points are referred to as local access points in this document.
Local AP Support (nonmesh)1 |
||
---|---|---|
55082 |
||
25043 |
||
3504 | 150 | 150 |
5520 | 1500 | 1500 |
8540 | 6000 | 6000 |