HP E-MSM310, Management And Configuration Manual

Page: 167 / 210

Local mesh
Local mesh profiles
7-15
When a node joins a new mesh, it is considered to be the consequence of a car change (or
replacement of an AP). This event triggers the following actions:
 The node software is updated, given that a software update URL is configured.
 The node configuration is updated, given that a configuration file URL is configured.
This will consequently change the node mesh ID to the one found in the configuration
file. If no configuration file URL is provided, the node will immediately proceed with
updating its mesh ID.
 An SNMP trap is sent.
After completing a configuration or software download, a local mesh node will wait an
additional 30 seconds before rebooting if a downstream link was established with
another node in promiscuous mode. The purpose of this delay is to give downstream
nodes some more time to download their software and configuration, improving the total
convergence time of an entire train network after a master car change.
Preserve master link across reboots
(Alternate master or slave nodes)
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.
Allow forced links
(Alternate Master, Slave only)
When enabled, the node will accept any connection forced from a master and it will
change its mesh ID in order to use the master mesh ID.
Allow 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.
Update 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.