User's Manual

Table Of Contents
Fortress ES-Series CLI Guide: Networking and Radio Configuration
37
temporary transient routing loop. In those special deployments,
the protocol can suppress the loop more quickly if the Mesh
Time To Live (TTL) is set. The default for the TTL is four hops,
which is optimal for a large full-connected mesh and
acceptable for many other deployments.
In contrast, if the Mesh network deployment is a chain of hops
with no alternate routing paths, change the setting to be the
number of hops in the longest optimal routing path, plus 2.
To disable TTL checking, set the TTL to off or 0.
Specify the TTL setting with the
set mesh command:
# set mesh -ttl off|0-15
3.2.3.7 Viewing Current Mesh Performance Parameters
View current mesh performance parameters with
show:
# show mesh
Mesh is enabled
RFC 4193 ULA: FD00:0:8895:8895:214:8CFF:FE2A:1C00
Subnet Id: 0x8895
Mesh Transmit Control: auto
Mesh Reactivity: most
Mesh Time to Live: 4
Mesh Multicast RSSI clamp: -80 dBm
Mesh Multicast rate clamp: 12 Mbps
Mesh Multicast Mode: auto
Mesh Control Packet Interval: auto
3.2.3.8 Frame Processor Parameters
The Frame Processor mode should always be set to
responsive
(the default) when FastPath Mesh is enabled. This
setting should only be changed under the direction of Fortress
technical support personnel.
Establish frame processor parameters with
set fp -mode.
# set fp -mode responsive|performance
View current frame processor mode settings with show fp:
# show fp
Mode: responsive
3.2.4 STP Bridging
NOTE:
STP
Bridg-
ing Mode is
incompatible with the
Mesh Point’s VLAN
function (see Section
3.11).
STP bridging is being deprecated in this release and will
no longer be a configurable option in subsequent
releases. Fortress therefore recommends using FastPath
Mesh, which is the default setting.
When STP is used for link management, the Fortress Mesh
Point can connect to other Fortress Mesh Points to form mesh
networks and, on separate BSSs, simultaneously serve as