Meshconnex policy – Brocade Mobility Access Point System Reference Guide (Supporting software release 5.5.0.0 and later) User Manual
Page 485
Brocade Mobility Access Point System Reference Guide
475
53-1003100-01
6
Smart RF Configuration and Deployment Considerations
Before defining a Smart RF supported configuration, refer to the following deployment guidelines to
ensure the configuration is optimally effective:
•
Smart RF is not able to detect a voice call in progress, and will switch to a different channel
resulting in voice call reconnections
•
The Smart RF calibration process impacts associated users and should not be run during
business or production hours. The calibration process should be performed during scheduled
maintenance intervals or non-business hours.
•
For Smart RF to provide effective recovery, RF planning must be performed to ensure
overlapping coverage exists at the deployment site. Smart RF can only provide recovery when
access points are deployed appropriately. Smart RF is not a solution, it's a temporary measure.
Administrators need to determine the root cause of RF deterioration and fix it. Smart RF
history/events can assist.
Brocade recommends that if a Smart RF managed radio is operating in WLAN mode on a channel
requiring DFS, it will switch channels if radar is detected.
•
If Smart RF is enabled, the radio picks a channel defined in the Smart RF policy.
•
If Smart RF is disabled, but a Smart RF policy is mapped, the radio picks a channels
specified in the Smart RF policy
•
If no SMART RF policy is mapped, the radio selects a random channel
If the radio is a dedicated sensor, it stops termination on that channel if a neighboring access point
detects radar. The access point attempts to come back to its original channel (statically configured
or selected by Smart RF) after the channel evacuation period has expired.
Change this behavior using a
no dfs-rehome
command from the CLI. This keeps the radio on the
newly selected channel and prevents the radio from coming back to the original channel, even after
the channel evacuation period.
MeshConnex Policy
MeshConnex is a mesh networking technology comparable to the 802.11s mesh networking
specification. MeshConnex meshing uses a hybrid proactive/on-demand path selection protocol,
similar to Ad hoc On Demand Distance Vector (AODV) routing protocols. This allows it to form
efficient paths using multiple attachment points to a distribution WAN, or form purely ad-hoc
peer-to-peer mesh networks in the absence of a WAN. Each device in the MeshConnex mesh
proactively manages its own path to the distribution WAN, but can also form peer-to-peer paths on
demand to improve forwarding efficiency. MeshConnex is not compatible with Mobility MiNT Based
meshing, though the two technologies can be enabled simultaneously in certain circumstances.
MeshConnex is designed for large-scale, high-mobility outdoor mesh deployments. MeshConnex
continually gathers data from beacons and transmission attempts to estimate the efficiency and
throughput of each MP-to-MP link. MeshConnex uses this data to dynamically form and continually
maintain paths for forwarding network frames.