Juniper Networks 10.4 PacketFlow Through a Bridged Network with NormalizedVLANs

•Example:Configuring One VPLS Instance for SeveralVLANs on page 55

PacketFlow Through a Bridged Network with NormalizedVLANs

Packetsreceived overa Layer 2 logical interface for bridging are processedin a strict

sequenceof steps.

Packetsreceived overa Layer 2 logical interface for bridging when a normalizedVLAN is

configuredwith a single or inner and outer VLAN identifier tags under the bridge domain

orthe VPLS routing instance are processed with the followingsteps:

1. Apacketreceived on a physical port is only acceptedfor further processing if the VLAN

tagsof the received packet matchthe VLAN tags associated with one of the logical

interfacesconfigured on that physicalport.

2. TheVLAN tags of the received packet arecompared with the normalized VLAN tags.

Ifthe VLAN tags of the received packet aredifferent from the normalized VLAN, then

theappropriateVLAN operations (such as push-push, pop-pop, pop-swap,swap-swap,

swap,and others) are done implicitly to convertthe received VLAN tags to the

normalizedVLAN tag value. For more information these operations,see the Junos

RoutingProtocols ConfigurationGuide.

3. Ifthe source MAC address of the received packetis not present in the source MAC

table,then it is learned based on the normalized VLAN tagvalue.

4. Thepacket is forwarded towardone or more egress Layer 2 logical interfacesbased

onthe destination MAC address. A packet with a known unicastdestination MAC

addressis only forwarded to one egresslogical interface. For each egress Layer2

logicalinterface, the normalized VLAN tagwithin the packet is compared with the

VLANtags configured on that logical interface.If the VLAN tags associated with an

egresslogical interface do not matchthe normalized VLAN tag in the frame, then

appropriateVLAN operations (such as push-push, pop-pop, pop-swap,swap-swap,

swap,and others) are implicitly done to convertthe normalized VLAN tags to the

VLANtags of the egress logical interface.For more information these operations, see

theJunos Routing Protocols ConfigurationGuide.

Documentation

MXSeries Ethernet Services Routers SolutionsPage•

•VLANsWithin a Bridge Domain or VPLS Instance on page 43

•Configuringa Normalized VLAN for Translationor Tagging on page45

•ConfiguringLearning Domains for VLAN IDs Bound to Logical Interfaceson page 47

•Example:Configuringa Provider Bridge Network with NormalizedVLAN Tags on page47

•Example:Configuringa Provider VPLS Network with Normalized VLAN Tagson page 51

•Example:Configuring One VPLS Instance for SeveralVLANs on page 55

Junos10.4 MX Series Ethernet ServicesRouters Solutions Guide