Professional Documents
Culture Documents
VLAN ID-Based Forwarding: Date
VLAN ID-Based Forwarding: Date
VLAN ID-Based Forwarding: Date
Version: v1.0
Abstract: This Application Notes describes the configuration of a specific feature of the Thomson
Gateway: VLAN ID-Based Forwarding. This feature is explained by integrating the Thomson
Gateway in a scenario where untagged, priority-tagged or VLAN-tagged frames have to be
bridged between the local Ethernet segment and the DSL line. The practical realization of the
scenario is described using CLI commands.
Applicability: This Application Note applies to all Thomson DSL Gateways with R7.4 and higher.
Updates: Thomson continuously develops new solutions, but is also committed to improving its existing
products.
For more information on Thomson's latest technological innovations, documents and software
releases, visit us at http://www.thomson-broadband.com
Chapter 1
1 Introduction
VLANs
The Ethernet frames that have to be forwarded may reside in different VLANs. This implies that all Ethernet
frames contain a (802.1Q) VLAN ID. Communication between different VLANs is not allowed on the link layer.
Only routers can make connections between different VLANs. VLANs create thus separated logical Ethernet
segments within a single physical segment.
Ethernet QoS
Ethernet frames optionally contain a (802.1p) user priority indication. If Ethernet QoS is taken into account
during bridging, it can be based on two steps:
1 Mapping the user priority of an incoming frame to an internal priority class. This classification can be
based on:
The type of the interface on which the frame is entering the bridge.
The (802.1p) user priority value.
The IP Type of Service octet (TOS-byte) for IP packets, using the Precedence or DSCP notation.
2 Sending out the frame while taking into account its internal priority class. This class can be used to:
Perform priority queuing on a single PVC.
Perform traffic multiplexing over a range of PVCs.
Related documents
For detailed information on the features, CLI commands and parameters used in this document, see:
Thomson Gateway Ethernet Configuration Guide.
Thomson Gateway VLAN Configuration Guide.
Thomson Gateway Ethernet QoS Configuration Guide.
E-DOC-CTC-20080229-0007 v1.0
1
Chapter 2
Introduction
In this scenario, the Thomson Gateway is intended to classify VLAN-tagged Ethernet frames based on their
VLAN ID. Per VLAN ID, you have to be able to configure to which PVC the frames must be forwarded.
This scenario configures the Thomson Gateway as bridge with two PVCs. Frames coming in on a local
interface are checked on their VLAN ID and are only forwarded on PVCs that are member of the same VLAN.
For example, frames that are member of VLAN A are forwarded to the first PVC. Frames that are member of
VLAN B or VLAN C are forwarded to the second PVC. The receiving local interface should not influence the
result.
Following illustration shows the VLAN ID-based forwarding scenario:
Thomson Gateway DSLAM
A 5
A 5
A 2 A 2
B 7 PVC1
B 3 B 7 C 1
B 3
C 2
C 2
PVC2
C 1
Mechanisms
To set up this scenario, we use following mechanisms:
VLAN awareness: the Ethernet bridge must be fully VLAN aware. As a result, the Ethernet bridge takes
the VLAN tag in the header of received frames into account.
VLANs: several VLANs are created on the Thomson Gateway. The local interfaces must be member of all
possible VLANs that can appear in the VLAN tag of received frames. The configured VLAN membership
of the PVCs defines to which PVC the frames must be forwarded.
Configuration overview
Following configuration steps have to be performed to configure the Thomson Gateway for this scenario:
1 Define which PVCs must be used by configuring an ATM interface for each one of them.
2 Connect the ATM interfaces to the Ethernet bridge.
3 Make the bridge VLAN aware.
2 E-DOC-CTC-20080229-0007 v1.0
Chapter 2
4 Define a VLAN for each VLAN ID the Ethernet bridge has to handle.
5 Define which interfaces are part of which VLAN.
6 Save the configuration.
=>:saveall
To create, configure and connect the ATM interfaces on top of the phonebook entries, execute following CLI
commands:
E-DOC-CTC-20080229-0007 v1.0
3
Chapter 2
From this moment on, all Ethernet frames coming in on the Ethernet bridge with a VLAN tag are only
forwarded to interfaces configured as an explicit member of that VLAN.
A logical name is associated with the effective VID that is used in the VLAN tag of the frame. The
‘addrule=disabled’ parameter forces the Thomson Gateway to create a separate filtering database for the
created VLAN. As a result, the same MAC address (e.g. the DSLAM MAC address) can be used in different
VLANs, for example when different VLANs are connected to the same device (e.g. the DSLAM).
The ‘untagged=disabled’ parameter avoids that the VLAN tag is stripped off when the frames are sent out on
the interface.
The ‘untagged=disabled’ parameter avoids that the VLAN tag is stripped off when the frames are sent out on
the interface.
4 E-DOC-CTC-20080229-0007 v1.0
Chapter 2
=>:saveall
Expected result
To display the list of VLANs on the Ethernet bridge, execute following CLI command:
To retrieve an overview of the population of the different VLANs, execute following CLI command:
Frames received on a bridge port are checked for their VLAN ID and are only sent out on bridge ports that are
member of the same VLAN. The table above shows that frames with VID 10 (representing VLAN A) are only
transmitted on PVC1. Frames with VID 11 (VLAN B) or 12 (VLAN C) are transmitted on PVC2.
It can be seen that all interfaces are also member of the default VLAN, and, as a result, also have connectivity
with the Thomson Gateway.
For example, to accept only VLAN-tagged frames on bridge port 4, execute following command:
E-DOC-CTC-20080229-0007 v1.0
5
Chapter 2
Additionally, you can use following CLI command to prevent the Thomson Gateway from modifying the user
priority indication in the VLAN tag:
6 E-DOC-CTC-20080229-0007 v1.0
Visit us at:
www.thomson-broadband.com
Coordinates:
Thomson Telecom
Prins Boudewijnlaan 47
B-2650 Edegem
Belgium
Copyright