Table of Contents
Advertisement
When this option is enabled, the AP will first try re-connecting to the master (alt-master) it was
connected to before rebooting (or disabling/re-enabling the profile). This re-connection happens
during the initial discovery time. After that period, the regular best master identification mechanism
will take over.
10.3.1.3.3.11Allow Forced Links
(Alternate master or slave nodes)
This option allows the AP to accept forced links from a master (alt-master). A link is forced from the
master by using the force link button next to the slave`s entry in the local mesh scan. A link can be
forced to a slave (alt-master) in a different mesh. This will cause the slave to save the new mesh ID
and use it from that point onward.
10.3.1.3.3.12Update Mesh ID from Server
(Master nodes only)
This is similar to promiscuous mode, but for a master. It is primary used in train application. When
this option is enabled, the master will check if the mesh ID in the configuration file on the server is
the same as the mesh ID locally configured. The server (and configuration file name) is specified in
the URL located in Maintenance > Config file management > Scheduled operations.
This allows a master AP to be replaced without changing the mesh ID of a train and without having
to configure that AP to use this mesh ID. The mesh ID is stored on the server.
10.3.1.3.3.13Restart Discovery
(Alternate master or slave nodes)
This button tells the AP to bring down any link it has already established and restart looking for the
best master to which it can connect. It can be used when a new master is installed close to a slave
and you want the slave to connect to that master, without rebooting.
BreezeMAX Wi² and BreezeACCESS Wi² System Manual
Local Mesh Profiles
183
Advertisement
Table of Contents
