Fortress Technologies ecure Wireless Access Bridge - Manual (Page 18)

Fortress Wireless Access Bridge: Installation
8
2.2.2 Preparing the Network
Any Ethernet device—including hubs, switches and access
points—directly connected to the Bridge must have auto-
negotiation capability (and have the feature enabled), or link
and/or packet loss could result. Refer to a device’s
documentation to configure its negotiation options.
Secure Clients (and other Fortress Bridges) in communication
with the Fortress Bridge must use the same encryption
algorithm and must be assigned the same Access ID (as
established in Step 5 of Section 2.4.2).
NOTE: In
/multire
deployments, the trans-
mission and reception
settings on all of the ra-
ios used to form the
network must match.
If you are deploying multiple Fortress Bridges in a poto-
po or reto-multipo network hey should be correctly
configured for their network roles. Typically, one Bridge serves
as the roo node in the network and the rest are configured as
non-roo nodes.
A Fortress Bridge in root mode does not initiate connections
with other Fortress Bridges, while Bridges in non-roo mode do
initiate connections with other Fortress Bridges—either directly
with a roo Bridge or with another non-roo Bridge. (The Bridge
Mode is established in Step 8 of Section 2.4.2.)
2.2.3 Port Locations
The Bridge’s dual antenna ports and grounding stud are
located on the back panel. The rest of the Bridge’s rerts are
located on the fro panel, shown below.
Figure 2.1 Fortress Bridge Port Locations