Example: Configuring A Provider Vpls Network With Normalized Vlan Tags - Juniper JUNOS OS 10.4 Manual

Related
Documentation

Example: Configuring a Provider VPLS Network with Normalized VLAN Tags

Copyright © 2012, Juniper Networks, Inc.
Bridge domain
c1–vlan-100
Logical interface
ge-1/0/0.1
Logical interface
ge-2/0/0.1
Logical interface
ge-3/0/0.1
Logical interface
ge-4/0/0.1
the pair and
ge-4/0/0 outer-vlan-tag 500
Logical interface ge-5/0/0.1
the pair and
ge-5/0/0 outer-vlan-tag 500
The association of the received packet to a logical interface is done by matching the
VLAN tags of the received packet with the VLAN tags configured on one of the logical
interfaces on that physical port. The
c1–vlan-100 sets the normalized VLAN value to 100.
The following happens as a result of this configuration:
Packets received on logical interfaces
of 100 in the frame are accepted.
Packets received on logical interface
frame are accepted and have their tag values translated to the normalized VLAN tag
value of 100.
Packets received on logical interfaces
of 500 and inner tag values of 100 are accepted.
Unknown source MAC addresses and unknown destination MAC addresses are learned
based on their normalized VLAN values of 100 or 300.
All packets sent on a logical interface always have their associated
their VLAN tag fields.
Configuration and function of bridge domain
is similar to, but not identical to, that of bridge
customer-c1-virtual-switch
Ethernet Networking
VLANs Within a Bridge Domain or VPLS Instance on page 43
Packet Flow Through a Bridged Network with Normalized VLANs on page 44
Configuring a Normalized VLAN for Translation or Tagging on page 45
This topic provides a configuration example to help you effectively configure a network
of Juniper Networks MX Series 3D Universal Edge Routers for a bridge domain or virtual
private LAN service (VPLS) environment. The emphasis here is on choosing the normalized
virtual LAN (VLAN) configuration. The VPLS configuration is not covered in this chapter.
Chapter 4: VLANs Within Bridge Domain and VPLS Environments
for
customer-c1–virtual-switch
configured on physical port
configured on physical port
configured on physical port
can exist on an extended port/subinterface defined by
.
can exist on an extended port/subinterface defined by
.
configuration within the bridge domain
vlan-id 100
ge-1/0/0.1 or
with a single VLAN tag of 200 in the
ge-3/0/0.1
ge-4/0/0.1 and
c2-vlan-300
domain c1-vlan-100
.
has five logical interfaces:
.
ge-1/0/0
.
ge-2/0/0
.
ge-3/0/0
ge-2/0/0.1 with a single VLAN tag
ge-5/0/0.1 with outer tag values
vlan-id value(s) in
for
customer-c2-virtual-switch
for
51