BreezeACCESS GFSK Ver 4.0 - Alvarion
BreezeACCESS GFSK Ver 4.0 - Alvarion
BreezeACCESS GFSK Ver 4.0 - Alvarion
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Technical Note<br />
<strong>BreezeACCESS</strong> <strong>GFSK</strong><br />
VLAN in <strong>Ver</strong>sion <strong>4.0</strong><br />
Clarification<br />
Relevant for: BreezeAccess II/XL/MMDS Products family<br />
Issued by<br />
Alfred Cohen – Product Expert<br />
Date of Release 13/5/2002<br />
<strong>Alvarion</strong> Ltd.<br />
Customer Service Center<br />
Technical Support Department<br />
Technical Support Department
General<br />
This document clarifies technical aspects related to the implementation of certain <strong>BreezeACCESS</strong> features functionality. The<br />
intention is to give further technical information in order to understand the nature of phenomena that can be encountered.<br />
This paper clarifies the built-in auto-preservation process during upgrade of the VLAN parameters required in the firmware. This is<br />
in order to maintain system integrity due to the changed VLAN implementation functionality in version <strong>4.0</strong>.<br />
For in-depth understanding of the VLAN feature please refer to the <strong>BreezeACCESS</strong> System Manual.<br />
Implementation<br />
<strong>BreezeACCESS</strong> firmware version <strong>4.0</strong> and above include an improved VLAN feature that allows the ability to configure VLAN<br />
Management independently from the bridge functionality of the device. This gives the flexibility to manage the device with or<br />
without VLAN no matter how the bridge data flow is configured (Hybrid, Trunk or Access).<br />
In order to accomplish NO VLAN Management in version <strong>4.0</strong> it is required that the “VLAN MANAGEMENT ID” parameter to be<br />
configured for decimal value 65535 ( Hex: FFFF)<br />
Firmware version 3.1.1 didn’t allow such values to be configured where previous versions had the partial ability to support such<br />
parameter configuration (SU only).<br />
Example: A device with version 3.1.1 configured with VLAN Management ID “1” (default) and configured to work in Hybrid mode<br />
can be managed only with “NO VLAN” frames, where if it were configured as “Trunk” it could be managed only with “VLAN “<br />
frames matching VLAN ID “1”.<br />
The firmware may change the Management VLAN ID value upon upgrade in order to maintain functional integrity.<br />
If the firmware version that the upgrade is performed from is less than <strong>4.0</strong> and the VLAN Link Type is configured for “Hybrid”, the<br />
unit will be auto-configured for VLAN Management ID of “65535” after the upgrade. This will maintain the “No VLAN” management<br />
ability. In other cases the already configured parameters will be preserved.<br />
Note: In case of firmware version downgrade from version <strong>4.0</strong> when VLAN ID - Management (or VLAN ID Voice & Management)<br />
is equal to ”65535”, the parameter will automatically revert to a value of "1" and Management might be lost.<br />
Technical Support Department