User's Manual
Table Of Contents
- FCC and IC Statement
- Getting started
- 1.1. Document structure
- 1.2. Abbreviations
- 1.3. Document marks
- System Description
- 2.1. Introducing InfiLINK XG
- 2.2. Hardware Description
- 2.3. InfiLINK XG Specifications
- Installation
- 3.1. Installation Requirements
- 3.2. Equipment Positioning Guidelines
- 3.3. Installing the Outdoor Units
- 3.4. Installing the Indoor Unit
- Commissioning
- 4.1. Introduction
- 4.2. Step by step procedure
- Operation & Administration
- 5.1. Introduction
- 5.2. InfiLINK XG unit access
- 5.3. Status
- 5.3.1. Interface Statistics
- 5.3.2. Wireless Link Statistics
- 5.4. Antenna alignment
- 5.5. Maintenance
- 5.5.1. Firmware
- 5.5.2. Upload
- 5.5.3. Download
- 5.5.4. Bottom section of the page
- 5.6. Settings
- 5.6.1. General
- 5.6.2. Network Access
- 5.6.3. Radio
- 5.6.4. Switch
- 5.6.5. VLAN Switching
- 5.6.6. SNMP
- 5.6.7. Apply and Try buttons for the configuration
- 5.6.8. Configuring QoS
- 5.6.9. Configuring per-VLAN 802.1p priority assignment
- Troubleshooting
- 5
- 6.1. Introduction
- 6.2. The wireless link is down (it got lost)
- 6.3. No access to the local unit
- 6.4. Expected capacity is not met
- 6.5. Errors on the wireless link, throughput fluctuations
- 6.6. No data is being transferred
- 6.7. The management of the unit is lost
- 6.7.1. ERConsole recovery procedure
- 6.7.2. Restore to factory settings using ERConsole
Chapter 3 - Configuration
Technical User Manual
InfiLINK XG
80
You can customize the native VLAN configuration according to the specific
requirements. For example, there can be ports that should allow only tagged traffic
to pass and ports that allow both tagged and untagged traffic.
Example - Port ge0 and ge1 should allow only VLANs 10 and 20 to pass.
Additionally, port ge1 should also allow the untagged traffic.
In this case, no native VLAN should be configured for the ge0 port and port ge1
should have VLAN 10 or 20 configured as native VLAN. The default VLAN should
be set to “off” on both ports, otherwise VLAN 1 will be allowed to pass!
Figure 59 - Native VLAN configuration example
NOTE
Changing the native VLAN, will automatically disable the Default VLAN, by setting it to
“off” on the specific port.
NOTE
When a different VLAN besides the Default VLAN is set as native, the “native” option
becomes unavailable for all other VLANs. In order to change the native VLAN in this
case you have to first remove the current native VLAN by changing the state to “on” or
“off”. After this, the “native” option is again available for all other VLANs.
5.6.5.4. Allow multiple VLANs
This section will describe step by step how to configure separate VLANs for
management and for the data traffic as follows:
VLAN 100 is used for the management of the unit
VLAN 200 is used for the data traffic
NOTE
In order to configure the VLAN based management access, it is necessary to associate
the IP address of the management interface with the management VLAN 100. If you
begin by enabling the VLAN-based switching and remove the native VLAN, you will lose
contact with the unit and ERConsole must be used for recovery.