VLANs and Quality of Service

VLANs on G1 Devices

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.


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 140: Configuring VLANs on the BN Web UI


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 141: 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 through the RN’s data port. If tagged frames are desired 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:

  1. The Data VLAN between the BN and connected router (or switch) is mandatory.

  2. The optional Data VLAN setting on the RN does not cause the RN to tag frames, rather, it overrides the Data VLAN setting on the BN.


Figure 142: No Data VLAN at End Device Port or RN


Figure 143: RN VLAN "a"


Figure 144: VLAN Set at End Device Port


Figure 145: VLAN set at End Device Port and RN

Multiple VLAN Scenarios

The color-coded diagram below illustrates the following three aspects:

  1. Different RNs connected to the same BN can have different VLAN settings.

  2. Multiple VLANs can pass through a single RN.

  3. 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 146: Multiple VLAN Scenario

Quality of Service

Traffic classification can be based on 802.1p Quality of Service (QoS) or Differentiated services (DSCP) and mapped to 8 hardware queues in the BN and 4 hardware queues in the RN. The Classification Type parameter is set on a per-BN basis in TCS under Network Configuration > Region > Market > Site > Cell > Sector. The color coding in the charts below is just to indicate what how traffic is queued in the BN vs. the RN.


Figure 147: 802.1p QoS Queues


Figure 148: DSCP Queues


Figure 149: Queuing on the BN


Figure 150: Queuing on the RN

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.