Appropriate VLAN configuration is crucial for the proper functionality of the Tarana devices. Action must be taken by the user before the devices will pass data traffic. Although the devices may show up on the Tarana Cloud Suite (TCS) without any VLAN configuration, it is important to note that this is the result of management traffic sent from the devices to TCS and not data traffic
Tagged and untagged management traffic is supported. By default, management traffic is untagged. This optional feature is configured through the BN’s web UI.
BN VLANs
The first consideration to be made in data VLAN configuration is the fact that the BN’s data ports (DATA1, DATA2, DATA3) require ingressing and egressing data frames to be tagged (802.1q). By default, the BN will tag egressing data frames with VLAN 2000. Arriving frames sent from the network router to the BN’s data port must therefore also be tagged with this VLAN number. The default Data VLAN can be changed via the BN’s web UI, as seen below.
Figure 1: Configuring VLANs on the BN Web UI</span >
RN VLANs
The second consideration is that the optional VLAN setting on the RN overrides the VLAN setting on the BN (the RN does not tag or untag frames). In this case, arriving frames sent from the network router to the BN’s data port must be tagged with the VLAN number of the RN’s setting. In the image below, this would be VLAN 50.
Figure 2: Configuring the Data VLAN on the RN (TCS and RN Web UI)
Tarana VLAN Logic
The tables below detail the VLAN logic for the Tarana devices. Please note this logic allows for multiple VLANs to pass the RN’s data port. If tagged frames are desired to be downstream of the RN, appropriate VLAN configurations at the network switch/router must be made.
There are two aspects to consider pertaining to the VLAN settings of Tarana devices:
- The Data VLAN between the BN and connected router (or switch) is mandatory.
- The optional Data VLAN setting on the RN does not cause the RN to tag frames, rather, overrides the Data VLAN setting on the BN.
Figure 3: No Data VLAN at End Device Port or RN
Figure 4: RN VLAN "a"
Figure 5: VLAN Set at End Device Port
Figure 6: VLAN set at End Device Port and RN
Multiple VLAN Scenarios
The color-coded diagram below illustrates the following three aspects:
- Different RNs connected to the same BN can have different VLAN settings.
- Multiple VLANs can pass through a single RN.
- Untagged frames can pass through the same RN that passes multiple VLANs.
Depending on the desired tag for a frame egressing out of the RN’s data port, the appropriate tagging must be applied at the router.
Figure 7: Multiple VLAN Scenarios</span >
Comments
Could you also confirm the Max L2 MTU that the BN and RNs can pass?
Good morning, Matt. The radios support a maximum L-2 MTU of 2048 bytes. Thank you for the question. This detail will be added to the documentation.
What ether-type does the configuration use for the stacked data VLAN (default 2000): 0x8100 / 0x88a8 / 0x9100?
The TPID is 8100 for both inner and outer tags (if used). Please see the Tarana training portal to self-enroll in the G1 TCS Administration course for more about VLANs in a Tarana network. https://learn.taranawireless.com/
Please sign in to leave a comment.