Alvarion BreezeACCESS II Release Note page 5

AU that is configured to operate with both "Shared Key" and "Open System"
algorithms will also accept a wrong WEP key of SU in Shared Key mode. In
this case the AU does not send a reject message to the SU.
When daisy-chaining GPS cards, the GPS card in slave mode will not switch automatically to master
mode in case of a failure/switching off of the master GPS card.
When working with management Vlan ID, the AU alarms will analyze data only from SU with the same
management Vlan ID.
Previous limitations
In case VLAN forwarding is used, it is needed to enter the VLAN management ID to the forwarding list of
the AU before the upgrade. Otherwise, it will be impossible to ma nage the SUs until configured.
In case SU voice unit was upgraded from version prior to 3.0 and now is upgraded to version 4.3, the
G.729 Frames per packet value needs to be manually configured to "6". Failing to do so may cause
decreased performance in ACSE mode.
Downgrade from 4.3 to version 3.x (except of special version 3.052.3) will have the following restrictions:
If VLAN ID - Management (or VLAN ID Voice & Management) is equal to 65535, after the downgrade it
will be automatically reverted to value of "1" and Management capabilities to the unit might be lost.
Using version 4.3 MIB file, ring frequency should be set to the frequency value (17, 20, 25, 50) and not
to the menu index.
GU-BS parameters return to default setting in case of software version downgrade.
Voice configured with G.723 codec + VAD on + Fast start mode cannot operate with Cisco gateway, as
this feature is not supported by the gateway.
The ACSE protocol does not support the use of VAD.
When the CIR/MIR algorithm is used, it effects the prioritization of packets more than other priority
mechanisms such as ToS and/or VLAN priority.
Uplink rate for AlvariBASE is practically limited to 2 Mbps.
The configuration of frequency parameters using 1.75MHz channel spacing can only be done using
the flexible hopping mechanism (fixed sub -bands selection cannot be used).
Fatal error messages are not displayed on the monitor through Telnet but only sent to the event
log.
In cases where "DHCP only" is defined the SU doesn't send the correct IP address to the gatekeeper.
Compatibility and Interoperability
Version 4.3 is compatible with all BreezeACCESS II, XL, V and MMDS hardware platforms.
When ACSE mode is disabled, the version is compatible with all previous BreezeACCESS software
versions, allowing interoperability between Access Units and Subscriber Units with mixed software
versions.
When using the ACSE, this software is compatible with version 4.0 only. However, units in ACSE mode
enabled are not interoperable with units that do not operate in ACSE mode.
When using the enhanced flexible mechanism, it is not interoperable with other flexible hopping
mechanism. Therefore, all units should use the same hopping mechanism.
The current implementation of Flexible Hopping is not compatible with Fixed Sub Bands mechanism or
Site Proprietary mechanism. All units should be configured to the same hopping mechanism.
Monitor Changes
The monitor has been adopted to support the new features detailed above.
Software version 4.3 is indicated on the main menu.
Alvarion Ltd. BreezeCOM and Floware unite
21a HaBarzel St. Tel Aviv, 69710 Israel Main Line / Fax: 972 3 645 6262 / 6222
Page 5 of 5
www.alvarion.com