Cisco Cisco Aironet 1522 Lightweight Outdoor Mesh Access Point デザインガイド

ページ / 184
 
31
Cisco Aironet 1520, 1130, 1240 Series Wireless Mesh Access Points, Design and Deployment Guide, Release 6.0
OL-20213-01
  Architecture Overview
CLI commands with known keywords and proper syntax are converted to XML while improper CLI 
commands are ignored and saved to flash memory. Any field with an invalid value is filtered out and set 
to a default by the XML validation engine.Validation occurs during bootup.
To see any ignored commands or invalid configuration values, enter this command: 
show invalid-config 
Note
You can only execute this command before either the clear config or save config command. If 
the downloaded configuration contains a large number of invalid CLI commands, you might 
want to upload the invalid configuration to the TFTP or FTP server for analysis.
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
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 MAPs. 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 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 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.
Cisco is a leading member of the Simple, Efficient, and Extensible Mesh (SEEMesh) consortium. The 
Cisco mesh model has become solidly embedded in one of the main contending proposals for the 802.11 
task group, which is moving towards becoming a mesh standard for the industry. The combined design, 
known as Hybrid Wireless Mesh (routing) Protocol (HWMP), serves both the fixed type of deployments 
and the mobile deployments. HWMP is favored by other SEEMesh supporters because it combines low 
complexity with great flexibility. AWPP has been selected as the draft foundation for HWMP. Cisco 
Systems has taken a leading role in setting standards in the mesh field.
Traffic Flow
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.