User guide

Optimizing Performance
6-7
Alvarion
! Wired stations connected to the cabling system.
If your network uses BNC coax cable (10Base2), make sure that terminators
are placed on both ends.
Checking the Length of Your LAN Segments
In exceptional cases, networking problems may be caused by LAN segments
that have been stretched over (too) large distances.
In these situations, frequent collisions might occur because stations can no
longer detect the carriers transmitted by distant stations. Collided frames will
no longer be received by the addressed station.
The occurrence of a LAN segment system that is too long can be diagnosed
with the remote statistics found on the
Remote tab in the monitor mode of the
AP Manager.
1. Select
Interface 1: Ethernet from the pull-down menu to display the statistics
for the Ethernet interface.
2. Compare the number of
In errors with the number of Bridge in packets.
! When the number of
In errors is 1% of the Bridge in packets or more,
there may be a cabling problem.
3. Monitor the value increase of the parameter
Bytes in over a longer period of
time.
! When this number increases constantly with more than 600,000 bytes
per second, this may indicate a problem with the length of your LAN
segment.
You may need to consult a network expert to verify and/or adjust the length of
your cable segments.
If this does not solve your problem, consider one of the following options as
described in this chapter:
! Protocol Filtering on page 6-3
! Optimizing Wireless Connections on page 6-7
Optimizing Wireless Connections
When the link quality of communications between a wireless station and its
Base Station is poor, packets communicated between this station and the Base
NOTE:
If you decide to split the LAN (segment) into multiple (sub) segments, make sure that all
BreezeNET equipped devices will be grouped into the same LAN segment. BreezeNET
stations will not be able to roam between LAN segments that are separated by routers and/
or gateways..