Bridge GUI Guide: Network Configuration
51
between FastPath MPs. When
Enabled
(the default), traffic
between MPs is subject to Fortress’s Mobile Security Protocol
(MSP), as configured on the Bridge itself (refer to Section 4.1).
3.2.1.3
Mobility Factor
To facilitate node mobility in the FP Mesh network,
Mobility
Factor
adjusts the frequency at which the costs of data paths to
neighbor nodes are sampled so that cost changes can be
transmitted to the network. The higher the
Mobility Factor
, the
more frequent is the cost sampling.
NOTE:
All MPs in
the FP Mesh net-
work should use the
same mobility factor.
Enter the highest relative speed of nodes in the network, in
miles per hour, as the
Mobility Factor
for all the MPs in the FP
Mesh network. For example, if nodes could move at
approximately 10 mph and in opposite directions, their highest
relative speed is 20 mph: enter
20
for
Mobility Factor
.
Set the
Mobility Factor
between
1
(the appropriate setting for a
stationary node) and
60
. The default is
30
.
3.2.1.4
Mesh Subnet ID
When FP Mesh is enabled, a
Unique Local IPv6 Unicast
Address
, as defined in RFC 4193, is generated for the Fortress
Bridge Mesh Point in the format:
| 7 bits |1| 40 bits | 16 bits | 64 bits |
+--------+-+------------+-----------+----------------------------+
| Prefix |L| Global ID | Subnet ID | Interface ID |
+--------+-+------------+-----------+----------------------------+
Prefix
-
FC00::/7
identifies the address as a Local IPv6
unicast address
L
-
1
if the prefix is locally assigned (
0
value definition t.b.d.)
Global ID
- pseudo-randomly allocated 40-bit global
identifier used to create a globally unique prefix
Subnet ID
- 16-bit subnet identifier
Interface ID
- 64-bit Interface ID
The subnet ID portion of the RFC-4193 address will facilitate
network segmentation in a future release of FastPath Mesh.
3.2.1.5
Network Cost Weighting
CAUTION:
The de-
fault cost equa-
tion values are optimal
for FP Mesh implemen-
tation. Ill-considered
changes can easily affect
network behavior ad-
versely.
Traffic on an FP Mesh network is routed along the least costly
path to its destination. 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.
