Specifications

BreezeACCESS VL Ver. 6.6 GA Release Notes Page 5 of 6
o A special warning message might be displayed in the log file:
WRN: Unknown vendor private element code: 15
WRN: Unknown vendor private element code: 16
WRN: Unknown vendor private element code: 17
o Parameters that are not included in the old ADB table will be either not available
(unknown) or with wrong values.
• When DFS is enabled, ANI “Pulse Detection Sensitivity” parameter, although configurable, is not
significant. In this case, an equivalent value of High will be automatically assigned to this
parameter.
• It is recommended to use TFTP, as opposed to FTP, in all cases when files need to be transferred
from/to the unit.
• It is not recommended to force the Noise Floor to more than 15-20dB above the measured value.
This might affect the SNR calculation (showing much higher values) for signals that are up to
10dB above the new Noise Floor Forced Value.
• When the DFS option is enabled, the Noise Floor Value cannot be higher than -90dBm.
• RSSI reading feature requires a field calibration of the Noise Floor. Without this calibration the
RSSI value read may have less accuracy (7-10dB). It is recommended to run the Calibration of
Noise Floor at least once before using the RSSI readings.
• The Noise Floor Calibration might fail in case of heavy interference present on more than 50% of
the available RF channels.
• Spectrum Analysis might display NF values of 0 on channels with very high continuous
interference, because the unit is not able to calibrate the NF. This might occur together with
unusually high values of Signal Width (over 200 microseconds).
• If Noise Floor Level setting on the AU is high, an SU might not be able to associate even if the
downlink SNR is good. This is because higher the NF value in the AU will result in shorter
coverage distance. (RSSI=SNR+NF)
• In the current version, Extended VLAN rules do not apply to PPPoE encapsulated traffic (the
algorithm does not look inside PPPoE frames).
• In case of “Statistics-Based Rate Control” feature, when a transmitted packet doesn't arrive
successfully from the first try, sometimes it is dropped without 10 attempts of re-transmitting. Also,
sometimes the retransmissions are performed only on the same modulation even if Retries on
Lower Modulations are enabled and possible.
• In case of using Statistics-Based Rate Control mechanism, with Retries on Lower Modulations
enabled, dropped frames on modulation 8 can still occur, either because of short retries (RTS
dropped) or trials on higher modulations from modulation levels lower than 8.
• The maximum recommended Multicast Modulation Level to be configured in the AU is 6.
Configuring a higher value might lead to increased amounts of CRC at the receiving SUs.
• Packets received from Ethernet and dropped at the Ethernet port are not reported in Traffic
Statistics counters.
• With respect to system performance with small packets (e.g. 64 bytes):
o For high MIR values, MIR might not be reachable with small packets.
o Small packets expected maximum throughput starting with Release 6.0 is below
40.000pps – around 33000pps for uplink unidirectional only.