Meshpoint, Meshpoint-config-instance, Chapter 27 – Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) User Manual
Page 1273: See chapter 27, <$elemtextmeshpoint
Brocade Mobility RFS Controller CLI Reference Guide
1265
53-1003098-01
Chapter
27
MESHPOINT
This chapter summarizes the Meshpoint commands in the CLI command structure.
Meshpoints are detector radios that monitor their coverage areas for potential failed peers or
coverage area holes requiring transmission adjustments for coverage compensation.
This chapter is organized as follows:
•
•
meshpoint-qos-policy-config-instance
•
meshpoint-device-config-instance
meshpoint-config-instance
MeshConnex (MCX) is a mesh networking technology that is comparable to the 802.11s mesh
networking specification. MCX 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 MCX mesh proactively
manages its own path to the distribution WAN, but can also form peer-to-peer paths on demand to
improve forwarding efficiency.
MCX is not compatible with MiNT Based meshing, though the two technologies can be enabled
simultaneously in certain circumstances.
MCX is designed for large-scale, high-mobility outdoor mesh deployments. MCX continually gathers
data from beacons and transmission attempts to estimate the efficiency and throughput of each
MP-to-MP link. MCX uses this data to dynamically form and continually maintain paths for
forwarding network frames.
In MCX systems, a meshpoint (MP) is a virtual mesh networking instance on a device, similar to a
WLAN AP. On each device, up to 4 MPs can be created and 2 can be created per radio. MPs can be
configured to use one or both radios in the device. If the MP is configured to use both radios, the
path selection protocols will continually select the best radio to reach each destination. Each MP
participates in a single Mesh Network, defined by the MeshID. The MeshID is typically a descriptive
network name, similar to the SSID of a WLAN. All MPs configured to use the same MeshID attempt
to form a mesh and interoperate. The MeshID allows overlapping mesh networks to discriminate
and disregard MPs belonging to different networks.
Use the (config) instance to configure a meshpoint. To navigate to the meshpoint configuration
instance, use the following command:
rfs7000-37FABE(config)#meshpoint test
rfs7000-37FABE(config-meshpoint-test)#