NOTE: ACX Series routers do not support the [edit logical-systems] hierarchy.
NOTE: For a single VLAN or VPLS routing instance, you can include either
the vlan-id or the vlan-tags statement, but not both. If you do not configure
a vlan-id or vlan-tags for the VLAN or the VPLS routing instance, the Layer 2
packets received are forwarded to the outbound Layer 2 interface without
having the VLAN tag modified unless an output-vlan-map is configured on
the Layer 2 interface. This results in a frame being forwarded to a Layer 2
interface with a VLAN tag that is different from what is configured for the
Layer 2 interface. Note that a frame received from the Layer 2 interface is still
required to match the VLAN tag(s) specified in the interface configuration.
The invalid configuration may cause a Layer 2 loop to occur. In ACX5048 and
ACX5096 routers, if the interface VLAN is configured as vlan-id-list, it is
mandatory to normalize the VPLS routing instance. vlan-id all is not supported
in ACX5048 and ACX5096 routers.
The VLAN tags associated with the inbound logical interface are compared with the
normalizing VLAN identifier. If the tags are different, they are rewritten as described in
Table 48 on page 758. The source MAC address of a received packet is learned based on
the normalizing VLAN identifier.
If the VLAN tags associated with the outbound logical interface and the normalizing
VLAN identifier are different, the normalizing VLAN identifier is rewritten to match the
VLAN tags of the outbound logical interface, as described in Table 49 on page 758.
The following steps outline the process for bridging a packet received over a Layer 2
logical interface when you specify a normalizing VLAN identifier using either the vlan-id
number or vlan-tags statement for a VLAN or a VPLS routing instance:
1. When a packet is received on a physical port, it is accepted only if the VLAN identifier
of the packet matches the VLAN identifier of one of the logical interfaces configured
on that port.
2. The VLAN tags of the received packet are then compared with the normalizing VLAN
identifier. If the VLAN tags of the packet are different from the normalizing VLAN
identifier, the VLAN tags are rewritten as described in Table 48 on page 758.
3. If the source MAC address of the received packet is not present in the source MAC
table, it is learned based on the normalizing VLAN identifier.
4. The packet is then forwarded toward one or more outbound Layer 2 logical interfaces
based on the destination MAC address. A packet with a known unicast destination
MAC address is forwarded only to one outbound logical interface. For each outbound
Layer 2 logical interface, the normalizing VLAN identifier configured for the VLAN or
VPLS routing instance is compared with the VLAN tags configured on that logical
1263Copyright © 2017, Juniper Networks, Inc.
Chapter 35: Configuring Virtual Private LAN Service
To Next Page
Loading...
Need help?
General
