Table of Contents
Advertisement
You can include this statement at the following hierarchy levels:
When a packet is received that is tagged with a VLAN ID specified in the trunk
interface list of VLAN IDs, the packet is accepted and forwarded within the bridge
domain that is configured with the matching VLAN ID.
When a packet is received that is tagged with a VLAN ID not specified in the trunk
interface list of VLAN IDs, the native VLAN ID is pushed in front of the existing VLAN
tag or tags and the packet is forwarded within the bridge domain that is configured
with the matching VLAN ID.
When an untagged packet is received on a trunk interface, the native VLAN ID is
added to the packet and the packet is forwarded within the bridge domain that is
configured with the matching VLAN ID.
A bridge domain configured with a matching VLAN ID must be configured before
the trunk interface is configured. To learn more about configuring bridge domains,
see the JUNOS Routing Protocols Configuration Guide.
Configuring a Trunk Interface on a Bridge Network
On MX Series routers, you can configure a trunk interface on a bridge network.
The following output sample shows trunk port configuration on a bridge network:
user@host# run show interfaces
ge-0/0/0 {
}
ge-2/0/0 {
}
ge-2/0/1 {
}
[edit interfaces interface-name unit logical-unit-number family bridge interface-mode
trunk]
[edit logical-systems logical-system-name interfaces interface-name unit
logical-unit-number family bridge interface-mode trunk]
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 1;
}
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 1-200;
}
}
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 1;
}
Chapter 34: Configuring 802.1Q VLANs
Configuring a Trunk Interface on a Bridge Network
641
Advertisement
Table of Contents
