Table of Contents
Advertisement
Troubleshooting
Figure 84
Figure 85
Misconfiguration of the Mesh Access Point IP Address
Although most practical Layer 3 networks are deployed using DHCP IP address management, manual
IP address management and allocating IP addresses statically to each mesh node might be preferred by
some network administrators. Manual mesh access point IP address management can be a nightmare for
large networks, but it might make sense in small to medium size networks (approx. 10-100 mesh nodes)
given the number of mesh nodes are relatively small compared to client hosts.
Statically configuring the IP address on a mesh node has the possibility of putting a MAP on a wrong
network, such as a subnet or VLAN. This could prevent a mesh access point from successfully resolving
the IP gateway, eventually failing to discover a WLAN controller. In such a scenario, the mesh access
point falls back to its DHCP mechanism and automatically attempts to find a DHCP server and obtains
an IP address from it. This fallback mechanism prevents a mesh node from being potentially stranded
from a wrongly configured static IP address and allows it to obtain a correct address from a DHCP server
on the network.
Cisco Aironet 1520, 1130, 1240 Series Wireless Mesh Access Points, Design and Deployment Guide, Release 6.0
146
Neighbor Information for Child
Neighbor Information for Parent
OL-20213-01
Hide quick links:
Advertisement
Table of Contents
