MSM7xx Controllers Configuration Guide v6.4.0

Local mesh profiles
Each node supports up to six profiles plus one provisioning profile. When a profile is active, a
node constantly scans and tries to establish links as defined by the profile.
The local mesh provisioning profile is used by the wireless link created on a provisioned AP to
support discovery of the controller. Initially, this link operates in slave mode. If you configure this
profile as an alternate master, then it can also be used to establish up to nine downstream links
with alternate master or slave nodes. See “Provisioning local mesh links” (page 391) for more
information.
Local mesh profiles are configurable at the controlled APs, group, or AP level. To view all profiles
select Controller > Controlled APs >> Configuration > Local mesh. Or you can expand Controlled
APs and select a group or specific AP. The following is an example of the profile list displayed
when selecting Controlled APs >> Configuration > Local mesh.
Configuration guidelines
• In addition to the provisioning profile, you can configure a total of six local mesh profiles on
each node.
• Each local mesh profile (on a master or alternate master) can be used to establish up to nine
links with other nodes.
• The same security settings must be used on all nodes in the same mesh.
• Any node that reaches the controller through the local mesh and uses local mesh itself, must
be provisioned prior to discovery.
• Daisy-chaining of nodes using local mesh links dramatically reduces throughput (which is
typically divided by two for each hop) especially when one or more of the following are true:
◦ Nodes provide both upstream and downstream links on the same radio.
◦ Nodes share a radio with AP functionality.
◦ IP traffic originating from a node can be sent on the link on which the controller was
discovered.
Configuring a local mesh profile
To configure profiles #1 to #6, select a name in the list. The Local mesh profile page opens.
Local mesh profiles 387