Dynamic Mtu Detection; Xml Configuration File - Cisco Mesh Access Points Deployment Manual

Cisco mesh access points, design and deployment guide, release 7.3
Table of Contents

Advertisement

Mesh Network Components
The mesh access point searches a list of controllers configured on the access point (primed) during setup.
Note
3 If Step 2 fails after 10 attempts, the mesh access point falls back to DHCP and attempts to connect in 10
tries.
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 there is no discovery 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. After both the access point and the controller are set at the new MTU,
all data within their path are fragmented into the new MTU. The new MTU size is used until it is changed.
The default MTU on switches and routers is 1500 bytes.

XML Configuration File

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.
The current release does not support binary configuration files; however, configuration files are in the
Note
binary state immediately after an upgrade from a mesh release to controller software release 7.0. 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 default values.
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 an 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. Then, you can download the
file back to the controller. The controller converts the configuration file back to XML format, saves it to flash
memory, and reboots using the new configuration.
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:
OL-27593-01
Cisco Mesh Access Points, Design and Deployment Guide, Release 7.3
XML Configuration File
41

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents