HP E-MSM310, Management And Configuration Manual

Page: 163 / 210

Local mesh
Local mesh profiles
7-11
Settings
Enabled/Disabled
Specify if the profile is enabled or disabled. The profile is only active when enabled.
Name
Name of the profile.
Use
Select the interface to use for this link.
Speed
(Static links only)
Sets the speed the link will operate at. For load balancing, you may want to limit the speed of
a link when connecting to multiple destinations.
AES/CCMP
Enables AES with CCMP encryption to secure traffic on the link.
The node uses the key you specify in the PSK field to generate the keys that encrypt the
wireless data stream.
Specify a key that is between 8 and 64 ASCII characters in length. It is recommended that the
key be at least 20 characters long and be a mix of letters and numbers.
Policy manager
The policy manager controls global configuration settings that apply to all nodes that are part
of the local mesh.
For proper operation you should configure only one node as the policy manager. Setting
more than one node as the policy manager will prevent policies from being properly
implemented.
Although the policy manager can be any node, it is strongly recommended that you make the
master node the policy manager.
When the local mesh is established, all nodes search for the policy manager and report to it.
Enforce node limit
This policy lets you limit the total number of nodes that can make up a local mesh. When the
node limit is reached, additional nodes will not be able to join the local mesh.
This policy is primarily intended to be used in train applications to prevent unwanted
connections from neighboring train cars. For example, if there are eight cars in a train and
two APs in each car, except for the first one, there are a total of 15 APs in the train. By setting
the node limit policy to 15 nodes, when the 15 nodes in the train's local mesh are connected
together, then no more nodes will be allowed to join the mesh.