Specifications
BreezeACCESS VL Ver. 6.6 GA Release Notes Page 4 of 6
parameter in the AU, and the Maximum TX Power parameter in the SUs connected to
this AU, should not be set to a value above “20-Antenna Gain”.
o For units with HW Revision C, frequency 5265 MHz should not be used with a 10
MHz bandwidth. For these units, the Transmit Power parameter in the AU, and the
Maximum TX Power parameter in the SUs connected to this AU, should not be set to
a value above “25-Antenna Gain”.
• In BreezeACCESS VL units operating in the 4.9 GHz Japan band (not B&B point-to-point) with a
10 MHz bandwidth, the following rules must be met for full compliance with regulations:
o When operating at 4945 MHz, the Transmit Power parameter in the AU should not be
set to a value above 11 dBm. The Maximum Transmit Power of the SU should not be
set to a value above 10 dBm.
o When operating at 5055 MHz, the Transmit Power parameter in the AU should not be
set to a value above 13 dBm. The Maximum Transmit power of the SU should not be
set to a value above 10 dBm.
This requirement, although not indicated in the certification document, is needed following the tests
performed in the certification lab.
• When encryption is used by the Authentication Algorithm (Shared Key option), in large cells (more
than 80 SUs) the association process may be relatively long.
• In units with HW Revision B, Burst Mode cannot be enabled when using WEP for Data
Encryption. In units with HW Revision B, the Burst Mode option will be “blocked” upon trying to
enable it when using WEP for Data Encryption. This limitation does not apply to units with HW
Revision C. Note that the Burst Mode parameter may be wrongly displayed on HW Revision B
units as Enabled instead of Blocked, when DFS or Data Encryption is enabled. However, the
behavior of the Burst Mode is as expected (blocked).
• The Country Code Learning by SU feature does not function with the default ESSID (ESSID1).
• MAC Address Deny/Allow List supports maximum 100 entries.
• Calculated distance in 10MHz channels might not be accurate when the AU and SUs do not run
the same software version; if the AU uses SW version 5.0 or later and the SU(s) use SW version
3.1 or earlier, the calculated distance might be higher by 10 km than the actual one. It is highly
recommended to upgrade the entire cell to the same software version, or use manual cell distance
mode.
• The character “;” (semicolon) is a reserved character. It should not be used in defining any string
parameters (unit name, ESSID, etc) since the string will be cut before the semicolon.
• If you are using the Feature Upgrade option in Telnet to enter a license string using copy and
paste operation, check carefully that the string is copied properly. You may have to enter it
manually due to potential problems in performing copy/paste in Telnet.
• Country Code related limitations:
o An SU will learn a Country Code from the AU only if the SU is running from its main
version.
o In a deployment with two (or more) AUs running different Country Codes, if the
Country Code Learning feature is enabled, SUs may migrate after reset from one AU
to the other, try to learn the Country Code during association process and never be
able to come back to the original AU. In such cases, the Preferred AU feature must
be enabled in the SUs before enabling Country Code learning.
• When an SU running a SW version lower than 5.0 is associated with an AU running SW version
5.0 or later: