Cisco Cisco Aironet 1522 Lightweight Outdoor Mesh Access Point 디자인 가이드

다운로드
페이지 184
30
Cisco Aironet 1520, 1130, 1240 Series Wireless Mesh Access Points, Design and Deployment Guide, Release 6.0
OL-20213-01
  Architecture Overview
4.
If both steps 2 and 3 fail and there is no successful CAPWAP connection to a controller, then the 
mesh access point falls back to LWAPP.
5.
If no discovery occurs after attempting steps 2, 3 and 4, the mesh access point tries the next link.
Dynamic MTU Detection
If the MTU is changed in the network, the access point detects the new MTU value and forwards that to 
the controller to adjust to the new MTU. Once both the access point and the controller are set at the new 
MTU, all data within their path is fragmented into the new MTU. The new MTU size is used until 
changed. Default MTU on switches and routers is 1500 bytes.
XML Configuration File
Beginning in release 5.2, mesh features within the controller’s boot configuration file are saved in an 
XML file in ASCII format. The XML configuration file is saved in the flash memory of the controller.
Note
Release 5.2 does not support binary configuration files; however, configuration files are in the binary 
state immediately after an upgrade from a mesh release to controller software release 5.2. After reset, the 
XML configuration file is selected.
Caution
Do not edit the XML file. Downloading a modified configuration file onto a controller causes a cyclic 
redundancy check (CRC) error on boot and the configuration is reset to the defaults. 
You can easily read and modify the XML configuration file by converting it to CLI format. To convert 
from XML to CLI format, upload the configuration file to a TFTP or FTP server. The controller initiates 
the conversion from XML to CLI during the upload. 
Once on the server, you can read or edit the configuration file in CLI format. When finished, you 
download the file back to the controller. The controller then converts the configuration file back to XML 
format, saves it to flash memory, and then reboots using the new configuration.
Note
The controller does not support uploading and downloading of port configuration CLI commands. If you 
want to configure the controller ports, enter the relevant commands summarized below:
Note
The commands listed below are manually entered after the software upgrade to release 5.2.
config port linktrap {port all} {enable disable}–Enables or disables the up and down link traps 
for a specific controller port or for all ports. 
config port adminmode {port all} {enable | disable}–Enables or disables the administrative 
mode for a specific controller port or for all ports. 
config port multicast appliance port {enable disable}–Enables or disables the multicast 
appliance service for a specific controller port.
config port power {port all} {enable disable}–Enables or disables power over Ethernet (PoE) 
for a specific controller port or for all ports.