Packet Flow Through a Bridged Network with Normalized VLANs
Packets received over a Layer 2 logical interface for
bridging are processed in a strict sequence of steps.
Packets received over a Layer 2 logical interface for
bridging when a normalized VLAN is configured with a single or inner
and outer VLAN identifier tags under the bridge domain or the VPLS
routing instance are processed with the following steps:
- A packet received on a physical port is only accepted
for further processing if the VLAN tags of the received packet match
the VLAN tags associated with one of the logical interfaces configured
on that physical port.
- The VLAN tags of the received packet are compared with
the normalized VLAN tags. If the VLAN tags of the received packet
are different from the normalized VLAN, then the appropriate VLAN
operations (such as push-push, pop-pop, pop-swap, swap-swap, swap,
and others) are done implicitly to convert the received VLAN tags
to the normalized VLAN tag value. For more information these operations,
see the Junos Routing Protocols Configuration Guide.
- If the source MAC address of the received packet is not
present in the source MAC table, then it is learned based on the normalized
VLAN tag value.
- The packet is forwarded toward one or more egress Layer
2 logical interfaces based on the destination MAC address. A packet
with a known unicast destination MAC address is only forwarded to
one egress logical interface. For each egress Layer 2 logical interface,
the normalized VLAN tag within the packet is compared with the VLAN
tags configured on that logical interface. If the VLAN tags associated
with an egress logical interface do not match the normalized VLAN
tag in the frame, then appropriate VLAN operations (such as push-push,
pop-pop, pop-swap, swap-swap, swap, and others) are implicitly done
to convert the normalized VLAN tags to the VLAN tags of the egress
logical interface. For more information these operations, see the Junos Routing Protocols Configuration Guide.
Published: 2013-02-13