Руководство По Проектированию для Cisco Cisco Aironet 1522 Lightweight Outdoor Mesh Access Point

Access passwords are hidden (obfuscated) in the configuration file. To enable or disable access point or 
controller passwords, enter the following command:

config switchconfig secret-obfuscation {enable | disable}

AWPP is designed specifically for wireless mesh networking to provide ease of deployment, fast 
convergence, and minimal resource consumption.

AWPP takes advantage of the CAPWAP WLAN, where client traffic is tunneled to the controller and is 
therefore hidden from the AWPP process. Also, the advance radio management features in the CAPWAP 
WLAN solution are available to the wireless mesh network and do not have to be built into AWPP.

AWPP enables a remote access point to dynamically find the best path back to a RAP for each MAP that 
is part of the RAP’s bridge group (BGN). Unlike traditional routing protocols, AWPP takes RF details 
into account.

To optimize the route, a MAP actively solicits neighbor MAP. During the solicitation, the MAP learns 
all of the available neighbors back to a RAP, determines which neighbor offers the best path, and then 
synchronizes with that neighbor. The path decisions of AWPP are based on the link quality and the 
number of hops. 

AWPP automatically determines the best path back to the CAPWAP controller by calculating the cost of 
each path in terms of the signal strength and number of hops. After the path is established, AWPP 
continuously monitors conditions and changes routes to reflect changes in conditions. AWPP also 
performs a smoothing function to signal condition information to ensure that the ephemeral nature of RF 
environments does not impact network stability.

The traffic flow within the wireless mesh can be divided into three components: 

Overlay CAPWAP traffic that flows within a standard CAPWAP access point deployment; that is, 
CAPWAP traffic between the CAPWAP access point and the CAPWAP controller.

Wireless mesh data frame flow.

AWPP exchanges.

As the CAPWAP model is well known and the AWPP is a proprietary protocol, only the wireless mesh 
data flow is described. The key to the wireless mesh data flow is the address fields of the 802.11 frames 
being sent between mesh access points.

An 802.11 data frame can use up to four address fields: receiver, transmitter, destination, and source. 
The standard frame from a WLAN client to an AP uses only three of these address fields because the 
transmitter address and the source address are the same. However, in a WLAN bridging network, all four 
address fields are used because the source of the frame might not be the transmitter of the frame, because 
the frame might have been generated by a device behind the transmitter.

 shows an example of this type of framing. The source address of the frame is MAP:03:70, the 

destination address of this frame is the controller (the mesh network is operating in Layer 2 mode), the 
transmitter address is MAP:D5:60, and the receiver address is RAP:03:40.