User's Manual

Fortress ES-Series CLI Guide: Networking and Radio Configuration
31
The ULA is not configurable. You can use set bridging to
enter a specific 16-bit hexadecimal subnet identifier. The
default is
0x8895.
# set bridging -mode mesh -s <subnetIdInHex>
FastPath Mesh Zone
Use the -zone parameter to indicate whether FP Mesh network
traffic will pass in the
clear zone or the encrypted zone:
# set bridging -mode mesh -zone clear|encrypted
Placing the network in the encrypted zone globally enables
end-to-end Fortress’s Mobile Security Protocol (MSP) for the
FP Mesh network.
The Mesh Point Core interfaces used to form the network must
be configured to reside in the same
-zone as the FP Mesh
network overall (refer to Section 3.9).
You must be logged on to an
administrator-level account to
change configuration settings (refer to Section 2.2).
Cost parameters
CAUTION: The
default cost equa-
tion values are normally
optimal for FP Mesh. Ill-
considered changes can
easily affect network
behavior adversely.
You can rebalance how the FP Mesh network computes the
throughput and latency costs of available data paths by
specifying new values for a and/or b in the FP Mesh cost
equation:
cost = a *(1/CLS) + b*(Q/CLS) + U
...in which:
 CLS - (Current Link Speed) is the time-averaged link
speed, as measured in bits per second.
 Q - is the time-averaged current queue depth, as measured
in bits.
 U - is the user defined per-interface cost offset, which
allows you to configure one link to be more costly than
another. Any non-negative integer between
0 (zero) and
4,294,967,295 can be defined (for configuration
information, refer to Section 3.4.9.11 for wireless and
Section 3.9 for Ethernet interface controls).
 a and b - are user defined constants, corresponding to
throughput and latency, respectively. Any non-negative
integer between
0 (zero) and 65,535 can be defined. The
default for each is
1.
Define new throughput and latency values with
set bridging -cost-parameters -a and -b, where the
aValue is the throughput cost weighting factor and the bValue is
the latency cost weighting factor. As a rule, a higher
aValue
improves overall throughput, while a higher
bValue , reduces
latency.