Juniper-networks JUNOS OS 10.4 Manuel d'utilisateur

Junos®OSMX Series 3D Universal Edge Routers SolutionsGuideRelease13.1R1Published: 2013-02-13Copyright © 2013, Juniper Networks, Inc.

Figure 22: Ethernet LFM with Loopback Support . . . . . . . . . . . . . . . . . . . . . . . . . 148Chapter 13 Ethernet Ring Protection . . . . . . . .

For more information on configuring DHCP, see the Junos OS Subscriber Management,Release 13.1.RelatedDocumentationDHCP Relay Agent•• Example: Configur

• Example: Configuring DHCP Relay in a VPLS Routing Instance Environment on page 81Example: Configuring DHCP Relay in a VPLS Routing Instance Environm

dhcp-relay { # DHCP snoopinggroup hdhcp {interface ge-2/2/4.0;interface ge-2/2/6.0;}}}}}}You verify your configuration by using two related commands:•

CHAPTER 8MX Series Router in an ATM EthernetInterworking FunctionThis chapter discusses the following topics:•MX Series Router ATM Ethernet Interworki

Because of the translation, the flow of packets and frames between PE1 (the M Seriesrouter) and PE2 (the MX series router) routers is not symmetrical,

Example: Configuring MX Series Router ATM Ethernet InterworkingConsider the router topology shown in Figure 13 on page 85. The MX Series router isconf

Configuring Router PE2 with a Layer 2 CircuitRouter CE1ConfigurationThe configuration of the Layer 2 circuit is based on LDP-signaled MPLS connections

}}ldp {interface all;}l2circuit {neighbor 10.255.171.14 {interface at-2/0/1.0 {virtual-circuit-id 100;}}}}Router PE2ConfigurationConfigure the Layer 2

}}Router CE2ConfigurationConfigure the dual- tagged Ethernet interface.[edit]interfaces {ge-0/0/0 {flexible-vlan-tagging;encapsulation flexible-ethern

atm-options {vpi 100;}unit 0 {vci 100.34;family inet {address 30.1.1.1/24;}}}}Router PE1ConfigurationConfigure the Layer 2 circuit.[edit]interfaces {a

List of TablesAbout This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiTable 1: Notice I

}}Router PE2ConfigurationConfigure the Layer 2 circuit over aggregated Ethernet on the MX Series router.[edit]chassis {aggregated-devices {ethernet {d

}}}Router CE2ConfigurationConfigure the dual-tagged Ethernet interface.[edit]interfaces {ge-0/0/0 {flexible-vlan-tagging;encapsulation flexible-ethern

at-2/0/0 {encapsulation ethernet-over-atm;atm-options {vpi 100;}unit 0 {vci 100.34;family inet {address 30.1.1.1/24;}}}}Router PE1ConfigurationConfigu

connections {remote-interface-switch rws1 {interface at-2/0/1.0;transmit-lsp lsp1-2;receive-lsp lsp2-1;}}}Router PE2ConfigurationConfigure the remote

}Router CE2ConfigurationConfigure the dual-tagged Ethernet interface.[edit]interfaces {ge-0/0/0 {flexible-vlan-tagging;encapsulation flexible-ethernet

unit 0 {vci 100.34;family inet {address 30.1.1.1/24;}}}}Router PE1ConfigurationConfigure the remote interface switch.[edit]interfaces {at-2/0/1 {atm-o

}}}Router PE2ConfigurationConfigure the remote interface switch over aggregated Ethernet on the MX Series router.[edit]chassis {aggregated-devices {et

connections {remote-interface-switch rwsl {interface ae0.0 {transmit-lsp- lsp-1sp2-1;receive-lsp lsp1-2;}}}Router CE2ConfigurationConfigure the dual-t

Copyright © 2013, Juniper Networks, Inc.98Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

PART 3Ethernet Filtering, Monitoring, and FaultManagement Solutions for MX SeriesRouters•Layer 2 Firewall Filters on page 101•IEEE 802.1ag OAM Connect

Copyright © 2013, Juniper Networks, Inc.xiiJunos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

Copyright © 2013, Juniper Networks, Inc.100Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

CHAPTER 9Layer 2 Firewall FiltersThis chapter discusses the following topics:•Firewall Filters for Bridge Domains and VPLS Instances on page 101•Examp

NOTE: You should deploy firewall filters carefully because it is easy to causeunforeseen side effects on all traffic, especially traffic that is not t

•The filter that applies the two policers to VPLS.•The application of the filter to the customer interface configuration as an input filter.NOTE: This

forwarding-class expedited-forwarding;}}term t1 {from {traffic-type [ broadcast unknown-unicast multicast ];}then policer bcast-unknown-unicast-non-ip

To configure filtering of frames by MAC address:1.Configure evil-mac-address, the firewall filter:[edit firewall]family bridge {filter evil-mac-addres

Example: Configuring Filtering of Frames by IEEE 802.1p BitsFor the bridge and vpls protocol families only, MX Series router firewall filters can beco

2.Apply the firewall filter filter-learn-vlan-configure-forwarding as an input filter toge-0/0/0:[edit interfaces]ge-0/0/0 {unit 0 {family bridge {fil

To configure filtering of frames by packet loss priority:1.Configure the firewall filter filter-plp-configure-forwarding:[edit firewall]family bridge

CHAPTER 10IEEE 802.1ag OAM Connectivity-FaultManagementThis chapter discusses the following topics:•Ethernet Operations, Administration, and Maintenan

About This GuideThis preface provides the following guidelines for using the Junos®OS MX Series 3DUniversal Edge Routers Solutions Guide:•Junos Docume

•Fault isolation, verification, and recovery (isolation and verification are provided by acombination of protocols, while recovery is the function of

maintenance domain, each service instance is called a maintenance association. Amaintenance association can be thought as a full mesh of maintenance e

Figure 15: Ethernet OAM with VPLSThe following are the configurations of the VPLS and CFM on the service provider routers.Configuration of PE1 [edit c

instance-type vpls;vlan-id 2000;interface ge-1/0/7.1;route-distinguisher 10.255.168.231:2000;vrf-target target:1000:1;protocols {vpls {site-range 10;s

}mep 100 {interface ge-1/0/7.1;direction up;auto-discovery;}}}}}}Configuration of PE2 [edit chassis]fpc 5 {pic 0 {tunnel-services {bandwidth 1g;}}}[ed

vrf-target target:1000:1;protocols {vpls {site-range 10;site vlan2000-PE2 {site-identifier 1;}}}}[edit protocols]rsvp {interface ge-5/2/7.0;}mpls {lab

auto-discovery;}}}}}}Configuration of ProuterMPLS only, no CFM needed:[edit]interfaces {ge-5/2/7 {# Connected to PE1unit 0 {family inet {address 10.20

disable;}interface ge-0/1/0.0;interface ge-5/2/7.0;}}}CFM on L2-CE1 Here is the configuration of CFM on L2-E1:[edit interfaces]ge-5/2/3 {vlan-tagging;

}mep 700 {interface ge-0/2/9.0;direction down;auto-discovery;}}}}}RelatedDocumentationEthernet OAM•• Ethernet Operations, Administration, and Maintena

CFM on L2-CE1 [edit interfaces]ge-0/2/9 {vlan-tagging;unit 0 {vlan-id 2000;}}[edit protocols oam ethernet]connectivity-fault-management {maintenance-d

ObjectivesThis guide provides an overview of the Layer 2 features of the Junos OS and describeshow to configure the features to provide solutions to s

encapsulation flexible-ethernet-services;unit 0 {encapsulation vlan-bridge;vlan-id 2000;}}ge-5/1/7 {vlan-tagging;encapsulation flexible-ethernet-servi

unit 0 {encapsulation vlan-bridge;vlan-id 2000;}}ge-5/2/3 {vlan-tagging;encapsulation flexible-ethernet-services;unit 0 {encapsulation vlan-bridge;vla

• Example: Configuring Ethernet CFM over VPLS on page 111• Example: Configuring Ethernet CFM on Physical Interfaces on page 122Example: Configuring Et

mep 100 {interface ge-1/0/1;direction down;auto-discovery;}}}}}}}The configuration on Router 2 mirrors that on Router 1, with the exception of the mep

Copyright © 2013, Juniper Networks, Inc.124Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

CHAPTER 11ITU-T Y.1731 Ethernet Frame DelayMeasurementsThis chapter discusses the following topics:•Ethernet Frame Delay Measurements on page 125•Conf

frame delay measurement in either one-way or two-way (round-trip) mode to gatherframe delay statistics and simultaneous statistics from multiple sessi

For two-way (round-trip) Ethernet frame delay measurement, either MEP can send arequest to begin a two-way delay measurement to its peer MEP, which re

Configuring MEP Interfaces to Support Ethernet Frame Delay MeasurementsEthernet frame delay measurement is a useful tool for providing performance sta

To perform Ethernet frame delay measurement, make sure that the followingconfiguration statement is NOT present:[edit routing-options]ppm {no-delegate

Supported Routing PlatformsFor the Layer 2 features described in this manual, the Junos OS currently supports thefollowing routing platforms:•Juniper

Table 3: Monitor Ethernet Delay Command Parameters (continued)DescriptionParameter RangeParameter(Optional) Specifies the number of seconds to wait be

NOTE: The only difference in the two commands is the use of themep-statistics and delay-statistics keyword.The fields for these commands are described

NOTE: These are not complete router configurations.Configuration on Router MX-1:[edit]interfaces {ge-5/2/9 {vlan-tagging;unit 0 {vlan-id 512;}}}protoc

}protocols {oam {ethernet {connectivity-fault-management {traceoptions {file eoam_cfm.log size 1g files 2 world-readable;flag all;}linktrace {path-dat

Statistics: CCMs sent : 1590 CCMs received out of sequence : 0 LBMs sent

Identifier MAC address State Interface 101 00:90:69:0a:48:57 ok ge-5/2/9.0The remote Router MX-1 should also collec

2 357 3 344 4 332 5 319 6 306 7

}}}protocols {oam {ethernet {connectivity-fault-management {traceoptions {file eoam_cfm.log size 1g files 2 world-readable;flag all;}linktrace {path-d

}maintenance-domain md6 {level 6;maintenance-association ma6 {continuity-check {interval 100ms;hold-interval 1;}mep 101 {interface ge-0/2/5.0;directio

CCMs received out of sequence : 0 LBMs sent : 0 Valid in-order LBRs received

}2. Merge the contents of the file into your routing platform configuration by issuing theload merge configuration mode command:[edit]user@host# load

8 92 9 92 10 108 Average two-wa

Untagged interface configuration for Router MX-1.[edit]interfaces {ge-5/0/0 {unit 0;}ge-5/2/9 {unit 0;}}protocols {oam {ethernet {connectivity-fault-m

connectivity-fault-management {traceoptions {file eoam_cfm.log size 1g files 2 world-readable;flag all;}linktrace {path-database-size 255;age 10s;}mai

CHAPTER 12IEEE 802.3ah OAM Link-FaultManagementThis chapter discusses the following topics:•Ethernet OAM Link Fault Management on page 143•Example: Co

Example: Configuring Ethernet LFM Between Provider Edge and Customer EdgeIn this example, LFM is enabled on an IP link between the provider edge (PE)

link-fault-management {interface ge-1/1/0 {pdu-interval 1000;pdu-threshold 5;}}}}}RelatedDocumentationEthernet OAM•• Ethernet OAM Link Fault Managemen

pdu-threshold 5;}}}}}2.Configure LFM on the PE2 router with CCC:[edit]interfaces ge-1/0/0 {encapsulation ethernet-ccc;unit 0;}protocols {oam {ethernet

Figure 21: Ethernet LFM for Aggregated EthernetTo configure LFM on an aggregated Ethernet interface between two routers:1.Configure LFM on Router 1 fo

}interfaces ge-1/0/0 {gigether-options {802.3ad ae0;}}interfaces ge-5/0/0 {gigether-options {802.3ad ae0;}}interfaces ae0 {unit 0 {family inet {addres

To configure LFM between a PE and a CE:1.Configure LFM loopback on the PE router:[edit]interfaces ge-1/0/0 {unit 0 {family inet {address 11.11.11.1/24

Table 1: Notice IconsDescriptionMeaningIconIndicates important features or instructions.Informational noteIndicates a situation that might result in l

• Example: Configuring Ethernet LFM Between Provider Edge and Customer Edge onpage 144• Example: Configuring Ethernet LFM for CCC on page 145• Example

CHAPTER 13Ethernet Ring ProtectionThis chapter discusses the following topics:•Ethernet Ring Protection on page 151•Ethernet Ring Protection Using Rin

Every node on the ring is one of two types:•RPL owner node—This node owns the RPL and blocks or unblocks the RPL as conditionsrequire. This node initi

• Example: Configuring Load Balancing Within Ethernet Ring Protection for MX SeriesRouters on page 160Ethernet Ring Protection Using Ring Instances fo

Example: Configuring Ethernet Ring Protection for MX Series RoutersThis example configures Ethernet ring protection for three MX Series router nodes:•

•Router 2’s east control channel interface is ge-1/0/2.1 (the RPL) and the west controlchannel interface is ge-1/2/1.1. The protection group is pg102.

3. Configure the Ethernet ring protection group:[edit]protocols {protection-group {ethernet-ring pg101 {node-id 00:01:01:00:00:01;ring-protection-link

Router 2 ConfigurationTo configure Router 2:1. Configure the interfaces:[edit]interfaces {ge-1/0/2 {vlan-tagging;encapsulation flexible-ethernet-servi

control-channel ge-1/2/1.1;}}}}4. Configure Ethernet OAM:[edit]protocols {oam {ethernet {connectivity-fault-management {action-profile rmep-defaults {

unit 1 {encapsulation vlan-bridge;vlan-id 100;}}ge-1/0/3 {vlan-tagging;encapsulation flexible-ethernet-services;unit 1 {encapsulation vlan-bridge;vlan

Table 2: Text and Syntax Conventions (continued)ExamplesDescriptionConventionbroadcast | multicast(string1 | string2 | string3)Indicates a choice betw

connectivity-fault-management {action-profile rmep-defaults {default-action {interface-down;}}maintenance-domain d2 {level 0;maintenance-association 1

traffic to pass through one path while other traffic can follow a different one. Dividingtraffic in this way supports traffic load-balancing in the ri

Figure 24: ERP with Multiple Protection Instances Configured on ThreeMX Series RoutersAS1CS1 CS2g017469ge-5/2/3.0west-interfacege-2/0/4.0east-interfac

Table 5: Components of the Network Topology (continued)SettingsPropertyCS1 has the following protection group properties:•RPL owner—ring-1.•East inter

Table 5: Components of the Network Topology (continued)SettingsPropertyAS1 has the following protection group properties:•East interface—ge-2/0/5.0.•W

set routing-instances vs bridge-domains bd200 vlan-id 200set routing-instances vs bridge-domains bd300 vlan-id 300set routing-instances vs bridge-doma

vlan-tagging;unit 0 {family bridge {interface-mode trunk;vlan-id-list 100-1000;}}}ge-5/2/3 {vlan-tagging;unit 0 {family bridge {interface-mode trunk;v

}}routing-instances {vs {instance-type virtual-switch;interface ge-3/2/4.0;interface ge-5/2/3.0;bridge-domains {bd100 {vlan-id 100;}bd101 {vlan-id 101

set bridge-domains bd500 vlan-id 500set bridge-domains bd600 vlan-id 600Step-by-StepProcedureTo configure ERP on CS2:Configure the trunk interface ge-

}ge-2/0/8 {unit 0 {family bridge {interface-mode trunk;vlan-id-list 100-1000;}}}protocols {protection-group {ethernet-ring ring-1 {east-interface {con

or are covered under warranty, and need postsales technical support, you can accessour tools and resources online or open a case with JTAC.•JTAC polic

vlan-id 200;}bd300 {vlan-id 300;}bd500 {vlan-id 500;}bd600 {vlan-id 600;}}}Configuring ERP on AS1CLI QuickConfigurationTo quickly configure AS1 for ER

[edit protection-group]user@as1# set ethernet-ring ring-1 east-interface control-channel ge-2/0/5.0user@as1# set ethernet-ring ring-1 east-interface c

vlan [200, 300];}}}}protection-group {ethernet-ring ring-2 {east-interface {control-channel {ge-2/0/5.0;vlan 101;}}west-interface {control-channel {ge

•Verifying the Ethernet Protection Ring on CS2 on page 174•Verifying the Data Channel CS2 on page 175•Verifying the VLANs on CS2 on page 175•Verifying

ge-3/2/4 124 discarding ge-5/2/3 125 forwarding Meaning The output displayed shows the STP index number used by each inte

Meaning The output displayed shows that protection groups ring-1 and ring-2 have a Request/stateof NR, meaning there is no request for APS on the ring

Interface Vlan STP Index Bridge Domainge-2/0/4 500 46 default—switch/bd500 ge-2/0/8 500 47 default-sw

Interface STP index Forward Statege-2/0/5 24 forwarding ge-2/1/1 25 forwarding Meaning The output displayed shows t

Router 1 OperationalCommands (NormalRing Operation)user@router1> show protection-group ethernet-ring apsEthernet Ring Name Request/state No Flush

Interface Control Channel Forward State Ring Protection Link End ge-1/2/1 ge-1/2/1.1 forwarding No ge-1/0/2

Juniper Networks, Inc.1194 North Mathilda AvenueSunnyvale, California 94089USA408-745-2000www.juniper.netThis product includes the Envoy SNMP Engine,

Copyright © 2013, Juniper Networks, Inc.xxJunos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

Ethernet ring port parameters for protection group pg101Interface Control Channel Forward State Ring Protection Link End ge-1/0/1 ge-1/0/1.1

Note that the failed interface (ge-1/0/2.1) is not forwarding. Router 3 will see almostidentical information.user@router2> show protection-group et

Copyright © 2013, Juniper Networks, Inc.182Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

PART 4Index•Index on page 185183Copyright © 2013, Juniper Networks, Inc.

Copyright © 2013, Juniper Networks, Inc.184Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

IndexSymbols#, comments in configuration statements...xviii( ), in syntax descriptions...

Ethernet ring normal operation...177Ethernet ring protection...154single VPLS fo

Ttechnical supportcontacting JTAC...xviiiterminologyEthernet...

Copyright © 2013, Juniper Networks, Inc.188Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

PART 1Overview•Overview of Ethernet Solutions on page 31Copyright © 2013, Juniper Networks, Inc.

Copyright © 2013, Juniper Networks, Inc.2Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

CHAPTER 1Overview of Ethernet SolutionsThis chapter discusses the following topics:•Ethernet Terms and Acronyms on page 3•Networking and Internetworki

•B–MAC—The backbone source and destination MAC address fields found in the IEEE802.1ah provider MAC encapsulation header.•bridge—A network component d

the MST configuration table used by the MST bridges of that MST region. See alsoCIST.•MSTP—Multiple Spanning Tree Protocol. A spanning-tree protocol u

• Networking at Layer 2: Challenges of Ethernet MAC Addresses on page 10• Networking at Layer 2: Forwarding VLAN Tagged Frames on page 11• Networking

segments can be linked at the frame level, and these devices are called bridges. Bridgesexamine arriving frames and decide whether to forward them on

NOTE: The opposite of a “globally unique network address” is the “locallysignificant connection identifier” which connects two endpoints on a network.

RelatedDocumentationEthernet Networking•• Ethernet Terms and Acronyms on page 3• Networking and Internetworking with Bridges and Routers on page 6• Ne

Abbreviated Table of ContentsAbout This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiPa

NOTE: Networking at the frame level says nothing about the presence orabsence of IP addresses at the packet level. Almost all ports, links, and device

• Networking at Layer 2: Benefits of Ethernet Frames on page 9• Networking at Layer 2: Forwarding VLAN Tagged Frames on page 11• Networking at Layer 2

Figure 1: Native (Normal) and VLAN-Tagged Ethernet FramesThe VLAN tag subtracts four bytes from the total MTU length of the Ethernet frame, butthis is

Networking at Layer 2: Forwarding Dual-Tagged FramesThe use of VLAN tagging to group (or bundle) sets of MAC addresses is a start towarda method of fo

• Networking and Internetworking with Bridges and Routers on page 6• Network Addressing at Layer 2 and Layer 3 on page 7• Networking at Layer 2: Benef

A Metro Ethernet Network with MX Series RoutersWhat would a Metro Ethernet network with Juniper Networks MX Series 3D UniversalEdge Router look like?

Figure 3: A Metro Ethernet Network with MX Series RoutersIn Figure 3 on page 16, the circled numbers reflect the different formats that the Ethernetfr

• Networking at Layer 2: Benefits of Ethernet Frames on page 9• Networking at Layer 2: Challenges of Ethernet MAC Addresses on page 10• Networking at

• Networking at Layer 2: Forwarding VLAN Tagged Frames on page 11• Networking at Layer 2: Forwarding Dual-Tagged Frames on page 13• Networking at Laye

PART 2Basic Solutions for MX Series RoutersThis chapter discusses the following topics:•Basic Layer 2 Features on MX Series Routers on page 21•Virtual

Copyright © 2013, Juniper Networks, Inc.ivJunos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

Copyright © 2013, Juniper Networks, Inc.20Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

CHAPTER 2Basic Layer 2 Features on MX SeriesRouters•Layer 2 Features for a Bridging Environment on page 21•Example Roadmap: Configuring a Basic Bridge

•Spanning Tree Protocols (xSTP, where the “x” represents the STP type)—Bridgesfunction by associating a MAC address with an interface, similar to the

Figure 5: Bridging Network with MX Series RoutersThe three routers each have a series of hosts on their Ethernet interfaces, as well asaggregated Ethe

•Router 1 has an access interface which provides bridging on VLAN 205 and is connectedto a customer device configured on ge-2/2/2. Router 3 has an acc

To configure the Ethernet interfaces and VLAN tags on all three routers:1.Configure the Ethernet interfaces and VLAN tags on Router 1:[edit]chassis {a

family bridge {interface-mode access;vlan-id 205;}}}interfaces ge-2/2/4 {native-vlan-id 200; # Untagged packets get vlan 200 tagunit 0 {family bridge

encapsulation vlan-bridge;vlan-id 100;}}interfaces ge-3/3/3 {encapsulation flexible-ethernet-services;vlan-tagging; # Customer interface uses singly-t

vlan-id 100;}unit 200 {vlan-id 200;}}3.Configure the Ethernet interfaces and VLAN tags on Router 3:[edit]chassis {aggregated-devices {ethernet {device

802.3ad ae3;}}interfaces ge-11/1/2 {gigether-options {802.3ad ae3;}}interfaces ge-11/1/3 {gigether-options {802.3ad ae2;}}interfaces ge-11/1/4 {gigeth

Table of ContentsAbout This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiJunos Document

Example Step: Configuring Bridge DomainsThere are two supported ways to configure an IRB with bridge domains. One way is touse the interface-mode trun

interface ge-2/2/2.100;interface ae1.100;interface ae3.100;}vlan200 {domain-type bridge;vlan-id 200;interface ge-3/3/3.200;interface ae1.200;interface

• Example Step: Configuring Interfaces and VLAN Tags on page 24• Example Step: Configuring Spanning Tree Protocols on page 32• Example Step: Configuri

msti 2 {vlan200; # This VLAN corresponds to MSTP instance 2}}}3.Configure MSTP on Router 3:[edit]protocols {mstp {configuration-name mstp-for-R1-2-3;

Figure 6: Designated, Root, and Alternate PortsRelatedDocumentationEthernet Networking•• Layer 2 Features for a Bridging Environment on page 21• Examp

IRB supports Layer 2 bridging and Layer 3 routing on the same interface. If the MACaddress on the arriving frame is the same as that of the IRB interf

}}bridge-domains {vlan-100 {domain-type bridge;vlan-id 100;interface ge-2/2/2.100;interface ae1.100;interface ae3.100routing-interface irb.0;}vlan-200

}}unit 3 {family inet {address 10.0.3.3/24 {}}unit 4 {family inet {address 10.0.3.4/24 {}}unit 5 {family inet {address 10.0.3.5/24 {}}unit 6 {family i

vlan-id 202;routing-interface irb.3}vlan203 {vlan-id 203;routing-interface irb.4}vlan204 {vlan-id 204;routing-interface irb.5}vlan205 {vlan-id 205;rou

CHAPTER 3Virtual SwitchesThis chapter discusses the following topics:•Layer 2 Features for a Switching Environment on page 39•Configuring Virtual Swit

Chapter 3 Virtual Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Layer 2 Features for

RelatedDocumentationEthernet Networking•• Configuring Virtual Switches as Separate Routing Instances on page 40Configuring Virtual Switches as Separat

For more information about configuring virtual switches, see the Junos OS Layer 2Configuration Guide.RelatedDocumentation• Ethernet Networking• Layer

Copyright © 2013, Juniper Networks, Inc.42Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

CHAPTER 4VLANs Within Bridge Domain and VPLSEnvironmentsThis chapter discusses the following topics:•VLANs Within a Bridge Domain or VPLS Instance on

• Example: Configuring a Provider Bridge Network with Normalized VLAN Tags on page 47• Example: Configuring a Provider VPLS Network with Normalized VL

Configuring a Normalized VLAN for Translation or TaggingThis topic provides configuration and operational information to help you manipulatevirtual lo

Then, the source MAC address of a received packet is learned based on the normalizedVLAN configuration.For output packets, if the VLAN tags associated

•vlan-tags outer outer-vlan-number inner inner-vlan-number•Use the vlan-id all statement to configure bridging for several VLANS with minimalamount of

NOTE: This topic does not present exhaustive configuration listings for allrouters in the figures. However, you can use it with a broader configuratio

The VLANs’ bridging paths are shown with distinct dashed and dotted lines. The VLANsat each site are:•L2-PE1 at Site 1: VLAN 100 and VLAN 300•L2-PE2 a

Part 3 Ethernet Filtering, Monitoring, and Fault Management Solutionsfor MX Series RoutersChapter 9 Layer 2 Firewall Filters . . . . . . . . . . . . .

}}interfaces ge-5/0/0 {encapsulation flexible-ethernet-services;flexible-vlan-tagging;unit 1 {encapsulation vlan-bridge;vlan-tags outer 500 inner 100;

Bridge domain c1–vlan-100 for customer-c1–virtual-switch has five logical interfaces:•Logical interface ge-1/0/0.1 configured on physical port ge-1/0/

For more information about configuring Ethernet pseudowires as part of VPLS, see theJunos OS Feature Guides.NOTE: This topic does not present exhausti

and P3, and Site 4 is connected to P1 and P3. VPLS pseudowires configured on the PEand P routers carry traffic between the sites.The pseudowires for t

vlan-id 302;}}routing-instances {customer-c1-vsi {instance-type vpls;vlan-id 100;interface ge-1/0/0.1;interface ge-2/0/0.1;interface ge-3/0/0.1;} # En

•Packets with a single VLAN tag value of 302 are accepted on interface ge-6/0/0.11.The VLAN tag value 302 is then popped and removed from the frame of

Figure 9: Many VLANs on One VPLS InstanceThe Layer 2 PE routers are MX Series routers. Each site is connected to two P routers forredundancy, although

If VLANs 1 through 1000 for customer C1 span the same sites, then the vlan-id all andvlan-range statements provide a way to switch all of these VLANs

For the same network topology illustrated in Figure 9 on page 56, if VLANs 1 through 1000for customer C1 span the same sites, you can normalize the VL

encapsulation vlan-vpls;vlan-id-range 1-1000; # Note the use of the VLAN id range statement.input-vlan-map {push; /* Push the service vlan on input */

Part 4 IndexIndex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Copyright

tag is 1300 for received packets and for logical interface ge-3/0/0.1, the normalizedVLAN tag is 1400. Then, the source MAC address of a received pack

}interfaces ge-3/0/0 {encapsulation flexible-ethernet-services;flexible-vlan-tagging;unit 1 {encapsulation vlan-vpls;interface-mode trunk;vlan-id-rang

The following operations are performed when you use the vlan-id all configuration:•The logical interfaces are configured as a trunk port that multiple

CHAPTER 5Bulk Administration of Layer 2 Featureson MX Series RoutersThis chapter discusses the following topics:•Bulk Configuration of VLANs and Bridg

other words, if VLAN 200 is translated to 500 on ingress, VLAN 500 is translated to VLAN200 on egress.The following example translates incoming trunk

The following example removes the VLAN identifier 5 from the original VLAN list(vlan-id-list [ 1–10 ]) and configures the bridge domain explicitly:[ed

Copyright © 2013, Juniper Networks, Inc.66Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

CHAPTER 6Dynamic Profiles for VLAN Interfaces andProtocolsThis chapter discusses the following topics:•Dynamic Profiles for VPLS Pseudowires on page 6

configuring a dynamic profile, use the $junos-interface-ifd-name variable for a dynamicphysical interface and the $junos-underlying-unit-number variab

interface ge-0/0/2.1;interface ge-0/0/3.1;vlan-tags outer 200 inner 100;protocols vpls {vpls-id 10;neighbor 10.1.1.20;}{...more...}}[edit interfaces]g

List of FiguresPart 1 OverviewChapter 1 Overview of Ethernet Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Fi

vpls-id 10;neighbor 10.1.1.20 {associate-profile green_vpls_pw_1; # The profile}}{...more...}}[edit interfaces]ge-0/0/1 {unit 0 {vlan-id 10;}}ge-0/0/2

interface ge-0/0/3.1;vlan-tags outer 200 inner 100;protocols vpls {vpls-id 10;neighbor 10.1.1.20;}{...more...}}[edit interfaces]ge-0/0/1 {unit 0 {vlan

unit 0 {vlan-id 100;}}ge-0/0/2 {unit 0 {vlan-id 100;}}ge-0/0/3 {unit 0 {vlan-id 100;}}[edit dynamic-profiles]green_vpls_pw_2 interfaces $junos-interfa

their own VLANs, at two different sites. The organization uses a BGP-based VPLS witha virtual switch to accomplish this.•Configuration of Routing Inst

interface-mode trunk; # This is the trunkvlan-id-list [ 10 20 30 40 50 ];}}}... # More interface statementsThis configuration switches the departmenta

instance-type virtual-switch;... # Other routing instance statementsprotocols vpls {site-range 10;site sample-site-1 {site-identifier 1;}associate-pro

interface-mode trunk;inner-vlan-id-list [ 10 20 40 50 ]; # Removed Accounting VLAN 30}}}NOTE: This is not a complete router configuration.In this case

This translates the sales and engineering VLAN tags exiting the VPLS pseudowireaccordingly. At the ingress of the VPLS pseudowire, VLANs 110 and 120 a

Copyright © 2013, Juniper Networks, Inc.78Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide

CHAPTER 7MX Series Router as a DHCP Relay AgentThis chapter discusses the following topics:•MX Series Router as a Layer 2 DHCP Relay Agent on page 79•