Home

Juniper Networks 10.4 Network Router User Manual

Contents

1. xxiii Opening a Case with JTAC xxiii Part 1 Overview Chapter 1 Overview of Ethernet Solutions 0 ccc cece eee eee eee 3 Ethernet Terms and Acronyms EE Ee Ee ee see ee ee ee ee eee 3 Networking and Internetworking with Bridges and Routers 6 Network Addressing at Layer 2 and Layer3 7 Networking at Layer 2 Benefits of Ethernet Frames 9 Networking at Layer 2 Challenges of Ethernet MAC Addresses 10 Networking at Layer 2 Forwarding VLAN Tagged Frames 11 Networking at Layer 2 Forwarding Dual Tagged Frames 13 Networking at Layer 2 Logical Interface Types 14 A Metro Ethernet Network with MX Series Routers 15 Layer 2 Networking Standards 17 Part 2 Basic Solutions for MX Series Routers Chapter 2 Basic Layer 2 Features on MX Series Routers 21 Layer 2 Features for a Bridging Environment 21 Example Roadmap Configuring a Basic Bridge Domain Environment 22 Example IOPOlOBVE us bh a acest ong RAS ED tee riad a Se ald 22 Example Scenari ie ER RE EER RE EE EE ER in RE Ie ES GE a RR 23 Example Configuration Summary ee ee es ss ee eee eee 24 Example Step Configuring Interfaces and VLAN Tags
2. 103 Ethernet Operations Administration and Maintenance 103 Ethernet OAM Connectivity Fault Management 104 Example Configuring Ethernet CFM over VPLS 105 Example Configuring Ethernet CFM on Bridge Connections 112 Example Configuring Ethernet CFM on Physical Interfaces 116 ITU T Y 1731 Ethernet Frame Delay Measurements 119 Ethernet Frame Delay Measurements 119 Configuring MEP Interfaces to Support Ethernet Frame Delay Measurements 122 Triggering an Ethernet Frame Delay Measurements Session 123 Viewing Ethernet Frame Delay Measurements Statistics 124 Example Configuring One Way Ethernet Frame Delay Measurements with Single Tagged InterfaceS EE EE eee eee eens 125 Example Configuring Two Way Ethernet Frame Delay Measurements with Single Tagged Interfaces 130 Example Configuring Ethernet Frame Delay Measurements with Untagged Interfaces 24 45 EE ER EE EE aa OO EE or 134 IEEE 802 3ah OAM Link Fault Management 137 Ethernet OAM Link Fault Management 137 Example Configuring Ethernet LFM Between PE andCE 138 Example Configuring Ethernet LFM for CCC 139 Example Configuring Ethernet LF
3. 24 Example Step Configuring Bridge Domains 30 Example Step Configuring Spanning Tree Protocols 32 Example Step Configuring Integrated Bridging and Routing 34 Copyright 2010 Juniper Networks Inc ix Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Virtual Switches siros in sas date ai RE sada que Eee ESE ie Ee Bb une shawls 39 Layer 2 Features for a Switching Environment 39 Configuring Virtual Switches as Separate Routing Instances 40 VLANs Within Bridge Domain and VPLS Environments 43 VLANs Within a Bridge Domain or VPLS Instance 43 Packet Flow Through a Bridged Network with Normalized VLANS 44 Configuring a Normalized VLAN for Translation or Tagging 45 Implicit VLAN Translation to a Normalized VLAN 45 Sending Tagged or Untagged Packets over VPLS Virtual Interfaces 46 Configuring a Normalized VLAN 46 Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces 47 Example Configuring a Provider Bridge Network with Normalized VLAN Tags 47 Example Configuring a Provider VPLS Network with Normalized VLAN Tags 51 Example Configuring One VPLS Instance for Severa
4. 2 Configure LFM on Router 2 for AEO edit chassis aggregated devices ethernet device count 1 interfaces ge 1 0 0 1 gigether options 802 3ad aeO interfaces ge 5 0 0 1 gigether options Copyright 2010 Juniper Networks Inc 141 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation 802 3ad aeO interfaces aeO 1 unit O family inet address 11 11 11 1 24 protocols oam ethernet link fault management interface aeO MX Series Ethernet Services Routers Solutions Page Ethernet OAM Link Fault Management on page 137 Example Configuring Ethernet LFM Between PE and CE on page 138 Example Configuring Ethernet LFM for CCC on page 139 Example Configuring Ethernet LFM with Loopback Support on page 142 Example Configuring Ethernet LFM with Loopback Support 142 In this example LFM is configured between PE and CE The PE can put the CE in remote loopback mode This allows the PE to have all the traffic sent to the CE looped back for diagnostics purposes as shown in Figure 22 on page 142 Figure 22 Ethernet LFM with Loopback Support 1 LFM gt id Ly ge 1 1 0 ge 1 0 0 pad Ly To configure LFM between a PE and a CE g016841 1 Configure LFM loopback on the PE router edit interfaces ge 1 0 0 1 unit O family inet address 11 11 11 1 24 Copyright 2
5. 103 Figure 15 Ethernet OAM with VPLS 0 0 0 000000 cece cee eee eee 106 Figure 16 Ethernet CFM over a Bridge Network 112 Figure 17 Ethernet CFM on Physical Interfaces 116 ITU T Y 1731 Ethernet Frame Delay Measurements 119 Figure 18 Ethernet OAM Overview 120 IEEE 802 3ah OAM Link Fault Management 137 Figure 19 Ethernet LFM Between PE andCE 138 Figure 20 Ethernet LFM for CCC 139 Figure 21 Ethernet LFM for Aggregated Ethernet 140 Copyright 2010 Juniper Networks Inc xiii Junos 10 4 MX Series Ethernet Services Routers Solutions Guide xiv Chapter 13 Figure 22 Ethernet LFM with Loopback Support 142 Ethernet Ring Protection 44 145 Figure 23 Ethernet Ring Protection Example Nodes 148 Figure 24 ERP with Multiple Protection Instances Configured on Three MX Series ROUTES ARE ARE OE RE ee N es eee 155 Copyright 2010 Juniper Networks Inc List of Tables About This Guide es EER ae RES EER DERE BERE DEE EE De MEE REK SEER xvii Table 1 Notice CONS si ige vue EER ee te Lada des ed bath re ER ER S xxi Table 2 Text and Syntax Conventions xxi Part 3 Ethernet Filtering
6. 128 Statistics CCMs sent CCMs received out of sequence LBMs sent Valid in order LBRs received Valid out of order LBRs received LBRs received with corrupted data LBRs sent LTMs sent LTMs received LTRs sent LTRs received Sequence number of next LTM reques 1DMs sent Valid 1DMs received Invalid 1DMs received DMMs sent DMRs sent Valid DMRs received Invalid DMRs received Remote MEP count 1 Identifier MAC address State 201 00 90 69 0a 43 94 t ok OOOOOOOOOOORKM uw LO pi O OOOOO Interface ge 0 2 5 0 The remote MEP database statistics are available on Router MX 1 user MX 1 show oam ethernet connectivity fault management mep database maintenance domain md6 Maintenance domain name md6 Format string Level 6 Maintenance association name ma6 Format string Continuity check status enabled Interval 100ms Loss threshold 3 frames MEP identifier 201 Direction down MAC address 00 90 69 0a 43 94 Auto discovery enabled Priority 0 Interface name ge 5 2 9 0 Interface status Active Link status Up Defects Remote MEP not receiving CCM Erroneous CCM received Cross connect CCM received RDI sent by some MEP Statistics CCMs sent CCMs received out of sequence LBMs sent Valid in order LBRs received Valid out of order LBRs received LBRs received with corrupted data LBRs sent LTMs sent LTMs received LTRs sent LTRs received Sequence number of next LTM reques 1DMs sent Valid 1DMs
7. 2010 Juniper Networks Inc Chapter 8 MX Series Router in an ATM Ethernet Interworking Function Example Configuring MX Series Router ATM Ethernet Interworking Consider the router topology shown in Figure 13 on page 79 The MX Series router is configured as the Provider Edge 2 PE2 router in the figure to support the ATM Ethernet IWF Figure 13 ATM Ethernet VLAN Interworking L2 circuits if switch I P backhaul Stacked VLAN Service __cE2 j Customer Edge 1 Provider Edge 1 Provider Edge 2 Customer Edge 2 ATM DSLAM Ethernet B RAS gt VPI maps to outer VLAN tag VCI maps to inner VLAN tag g017428 The relevant router interfaces are On CEI the CET PEI interface is at 2 0 0 with IP address 30 1 1 1 24 On PEI The PEI CE1 interface is at 2 0 1 with no IP address required The PEI PE2 interface is ge 5 0 0 with IP address 20 1 1 1 24 On PE2 The PE2 CE2 interface is ge 0 2 0 with no IP address required The PE2 PEI interface is ge 0 2 8 with IP address 20 1 1 10 24 CE2 interface is ge 0 0 0 with IP address 30 1 1 10 24 NOTE These are not complete router configurations Configuring PE2 with a Layer 2 Circuit on page 79 Configuring PE2 with a Layer 2 Circuit over Aggregated Ethernet on page 82 Configuring PE2 with a Remote Interface Switch on page 85 Configuring PE2 with a Remote Interface Switch over Aggregated Ethernet on page 88 Configuring
8. e East interface ge 2 0 5 0 e West interface ge 2 1 1 0 Data channel for ring I VLAN 200 VLAN 300 Data channel for ring 2 VLAN 500 VLAN 600 ASI has the following bridging properties e bdi00is associated with vlan id 100 e bd101 is associated with vlan id 101 e bd200 is associated with vlan id 200 e bd300 is associated with vlan id 300 e bd500 is associated with vlan id 500 e bd600 is associated with vlan id 600 Configuration CLI Quick Configuration To enable ERP with ring instances on CS1 CS2 and ASI perform these tasks Configuring ERP on CS1 on page 157 Configuring ERP on CS2 on page 160 Configuring ERP on AS1 on page 163 Configuring ERP on CS1 To quickly configure CS1 for ERP copy the following commands and paste them into the switch terminal window of CS1 edit set interfaces ge 3 2 4 vlan tagging set interfaces ge 3 2 4 unit O family bridge interface mode trunk set interfaces ge 3 2 4 unit O family bridge vlan id list 100 1000 set interfaces ge 5 2 3 vlan tagging set interfaces ge 5 2 3 unit O family bridge interface mode trunk set interfaces ge 5 2 3 unit O family bridge vlan id list 100 1000 set protocols protection group ethernet ring ring 1 ring protection link owner set protocols protection group ethernet ring ring 1 east interface control channel ge 3 2 4 0 set protocols protection group ethernet ring ring 1 east interface control channel vlan 100 set protocols pro
9. learning domain A MAC address database where the MAC addresses are added based on the normalized VLAN tags LFM Link fault management A method used to detect problems on links and spans on an Ethernet network defined in IEEE 802 3ah See also OAM MSTI Multiple Spanning Tree Instance One of a number of spanning trees calculated by MSTP within an MST region The MSTI provides a simple and fully connected active topology for frames classified as belonging to a VLAN that is mapped to the MSTI by the MST configuration table used by the MST bridges of that MST region See also CIST 4 Copyright 2010 Juniper Networks Inc Chapter 1 Overview of Ethernet Solutions MSTP Multiple Spanning Tree Protocol A spanning tree protocol used to prevent loops in bridge configurations Unlike other types of STPs MSTP can block ports selectively by VLAN See also RSTP OAM Operation Administration and Maintenance A set of tools used to provide management for links device and networks See also LFM PBB Provider backbone bridge Q in Q See 802 lad PBBN Provider backbone bridged network RSTP Rapid Spanning Tree Protocol A spanning tree protocol used to prevent loops in bridge configurations RSTP is not aware of VLANs and blocks ports at the physical level See also MSTP S TAG A field defined in the IEEE 802 1ad Q in Q encapsulation header that carries the S VLAN identifier information See also B TA
10. remote interface switchrwsl f interface at 2 0 1 0 transmit lsp lspl 2 receive lsp lsp2 1 PE2 Configuation Configure the Remote Interface Switch over aggregated Ethernet on the MX Series Router edit chassis aggregated devices ethernet device count 1 interfaces ge 0 2 0 1 gigether options 802 3ad aeO ge 0 2 8 unit O family inet address 20 1 1 10 24 family iso Copyright 2010 Juniper Networks Inc 89 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide family mpls aeO vlan vci tagging encapsulation vlan vci ccc unit O vlan id 100 inner vlan id range start 32 end 63 protocols rsvp interface ge 0 2 8 0 mpls label switched path lsp2 1 from 10 255 171 14 to 10 255 171 45 label switched path lsp1 2 from 10 255 171 45 to 10 255 171 14 interface ge 0 2 8 0 isis interface ge 0 2 8 0 connections remote interface switch rwsl f interface ae0 O transmit lsp lsp2 1 receive lsp lspl 2 CE2 Configuation Configure Dual Tagged Ethernet Interface edit interfaces ge 0 0 0 1 flexible vlan tagging encapsulation flexible ethernet services unit O vlan tags outer 100 inner 34 family inet address 30 1 1 10 24 90 Copyright 2010 Juniper Networks Inc Chapter 8 MX Series Router in an ATM Ethernet Interworking Function You verify your configuration on the M
11. 10 108 Average two way delay 103 usec Average two way delay variation 8 usec Best case two way delay 92 usec Worst case two way delay 122 usec Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Frame Delay Measurements on page 119 Configuring MEP Interfaces to Support ETH DM on page 122 Triggering an ETH DM Session on page 123 Viewing ETH DM Statistics on page 124 Configuring One Way ETH DM with Single Tagged Interfaces on page 125 Configuring ETH DM with Untagged Interfaces on page 134 Example Configuring Ethernet Frame Delay Measurements with Untagged Interfaces Ethernet frame delay measurements are supported on untagged interfaces All commands are the same as for tagged interfaces Only the configurations are different This section shows the untagged interface configurations for Routers MX 1 and MX 2 NOTE These are not complete router configurations 134 Copyright 2010 Juniper Networks Inc Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements Untagged interface configuration for Router MX 1 edit interfaces ge 5 0 0 1 unit O ge 5 2 9 1 unit O protocols oam ethernet connectivity fault management traceoptions file eoam_cfm log size 1g files 2 world readable flag all linktrace path database size 255 age 10s maintenance domain md6 level 6 maintenance association ma6 continuity check interval 100ms hol
12. Average delay 0 usec Average delay variation 0 usec Best case delay 0 usec Worst case delay 0 usec MX Series Ethernet Services Routers Solutions Page Ethernet Frame Delay Measurements on page 119 Configuring MEP Interfaces to Support ETH DM on page 122 Viewing ETH DM Statistics on page 124 Configuring One Way ETH DM with Single Tagged Interfaces on page 125 Configuring Two Way ETH DM with Single Tagged Interfaces on page 130 Configuring ETH DM with Untagged Interfaces on page 134 Viewing Ethernet Frame Delay Measurements Statistics 124 Once Ethernet frame delay measurement statistics have been collected they can be displayed To retrieve the last 100 Ethernet frame delay measurement statistics per remote MEP or per CFM session two types of show commands are provided For all OAM frame counters and Ethernet frame delay measurement statistics For Ethernet frame delay measurement statistics only To retrieve all Ethernet frame delay measurement statistics for a given session use the show oam ethernet connectivity fault management mep statistics maintenance domain name maintenance association name local mep identifier remote mepidentifier count count command To retrieve only Ethernet frame delay measurement statistics for a given session use the show oam ethernet connectivity fault management delay statistics maintenance domain name maintenance association name local mep identifier remote mep
13. Layer 2 Networking Standards on page 17 Copyright 2010 Juniper Networks Inc Chapter 1 Overview of Ethernet Solutions Networking at Layer 2 Forwarding Dual Tagged Frames The use of VLAN tagging to group or bundle sets of MAC addresses is a start toward a method of forwarding LAN traffic based on information found in the frame not on IP address in the packet However there is a major limitation in trying to build forwarding tables based on VLAN tags Simply put there are not enough VLAN tags Twelve bits only supply enough space for 4096 unique VLAN tags This is hardly enough for all the LANs on a large corporate campus let alone the whole world A 12 bit tag might suffice for the local campus arena but for the metropolitan area comprising a whole city more bits are needed The number of bits in the VLAN tag two bytes for the TPID and two bytes for the TCI field are fixed and cannot be extended However another VLAN tag can be added to the frame forming an inner and outer VLAN tag arrangement This arrangement is defined in the IEEE 802 1ad specification and applies to devices that function on the provider bridge level This means that Ethernet frames tagged at the local or customer VLAN level can receive another outer VLAN tag when they are sent to the provider s LAN switches As a result Ethernet frames can be switched across a metropolitan area not just among the local organizations devices at the campus level T
14. Site 3 is connected to P2 and P3 as shown and Site 4 is connected to P1 and P3 as shown VPLS pseudowires configured on the PE and P routers carry traffic between the sites 48 Copyright 2010 Juniper Networks Inc Chapter 4 VLANS Within Bridge Domain and VPLS Environments The VLANS bridging paths are shown with distinct dashed and dotted lines The VLANS at each site are e L2 PE1at Site 1 VLAN 100 and VLAN 300 L2 PE2 at Site 2 VLAN 100 e L2 PE3 at Site 3 VLAN 100 L2 PE4 at Site 4 VLAN 300 D NOTE The configurations in this chapter are only partial examples of complete and functional router configurations Do not copy these configurations and use them directly on an actual system The following is the configuration of interfaces virtual switches and bridge domains for MX Series router L2 PET edit interfaces ge 1 0 0 encapsulation flexible ethernet services flexible vlan tagging unit 11 encapsulation vlan bridge vlan id 100 unit 11 encapsulation vlan bridge vlan id 301 interface ge 2 0 0 1 encapsulation flexible ethernet services flexible vlan tagging unit 1 encapsulation vlan bridge vlan id 100 interface ge 3 0 0 1 encapsulation flexible ethernet services flexible vlan tagging unit 1 encapsulation vlan bridge vlan id 200 NOTE 200 is translated to normalized VLAN vlaue interfaces ge 4 0 0 1 encapsulation flexible ethernet services flexible vlan tagging
15. filter input customer l Related MX Series Ethernet Services Routers Solutions Page Documentation Firewall Filters for Bridge Domains and VPLS Instances on page 95 Example Configuring Filtering of Frames by MAC Address on page 98 Example Configuring Filtering of Frames by IEEE 802 lp Bits on page 99 Example Configuring Filtering of Frames by Packet Loss Priority on page 101 Example Configuring Filtering of Frames by MAC Address This example firewall filter finds frames with a certain source MAC address 88 05 00 29 3c de 48 then counts and silently discards them For more information about configuring firewall filter match conditions see the Junos OS Policy Framework Configuration Guide The filter is applied to the VLAN configured as vlan100200 as an input filter on Router 1 NOTE This example does not present exhaustive configuration listings for all routers in the figures However you can use this example with a broader configuration strategy to complete the MX Series router network Ethernet Operations Administration and Maintenance OAM configurations To configure filtering of frames by MAC address 1 Configure evil mac address the firewall filter edit firewall family bridge filter evil mac address term one from source mac address 88 05 00 29 3c de 48 then 98 Copyright 2010 Juniper Networks Inc Chapter 9 Layer 2 Firewall Filters count evil mac address
16. unit 11 encapsulation vlan bridge vlan tags outer 500 inner 100 This places two VLAN tags on the provider pseudowire Copyright 2010 Juniper Networks Inc 49 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide interfaces ge 5 0 0 1 encapsulation flexible ethernet services flexible vlan tagging unit 11 encapsulation vlan bridge vlan tags outer 500 inner 100 This places two VLAN tags on the provider pseudowire unit 11 encapsulation vlan bridge vlan tags outer 600 inner 300 This places two VLAN tags on the provider pseudowire interfaces ge 6 0 0 encapsulation flexible ethernet services flexible vlan tagging unit 11 encapsulation vlan bridge vlan id 300 routing instances customer cl virtual switch instance type virtual switch bridge domains cl vlan 100 domain type bridge vlan id 100 Customer VLAN 100 uses these five logical interfaces interface ge 1 0 01 interface ge 2 0 0 1 interface ge 3 0 0 1 interface ge 4 0 01 interface ge 5 0 0 1 End of cl vlan 100 End of bridge domains End of customer cl virtual switch customer c2 virtual switch instance type virtual switch bridge domains c2 vlan 300 domain type bridge vlan id 300 Customer VLAN 300 uses these three logical interfaces interface ge 1 0 0 11 interface ge 5 0 0 11 interface ge 6 0 0 11 End of cl vlan 300 1 End of bridge domains End of customer c2 virtu
17. 73 Example Configuring DHCP Relay in a Bridge Domain VLAN Environment 74 Example Configuring DHCP Relay in a VPLS Routing Instance Environment 75 MX Series Router in an ATM Ethernet Interworking Function 77 MX Series Router ATM Ethernet Interworking Function 77 Example Configuring MX Series Router ATM Ethernet Interworking 79 Configuring PE2 with a Layer 2 Circuit 79 Configuring PE2 with a Layer 2 Circuit over Aggregated Ethernet 82 Configuring PE2 with a Remote Interface Switch 85 Configuring PE2 with a Remote Interface Switch over Aggregated Ethernet as dco oat ho Pt dh ns She ee Rime Mr nr 88 Copyright 2010 Juniper Networks Inc Part 3 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Table of Contents Ethernet Filtering Monitoring and Fault Management Solutions for MX Series Routers Layer 2 Firewall Filters 0 0 ccc cece eee ss sus ee ek see 95 Firewall Filters for Bridge Domains and VPLS Instances 95 Example Configuring Policing and Marking of Traffic Entering a VPLS Core 96 Example Configuring Filtering of Frames by MAC Address 98 Example Configuring Filtering of Frames by IEEE 802 1p Bits 99 Example Configuring Filtering of Frames by Packet Loss Priority 101 IEEE 802 1ag OAM Connectivity Fault Management
18. This is necessary to avoid the potential bridging loop formed by the triangular architecture of the routers MSTP is configured on the three routers so the set of VLANS has an independent loop free topology The Layer 2 traffic can be load shared over 65 independent paths 64 Multiple Spanning Tree Instances MSTIS and one Common and Internal Spanning Tree CIST each spanning a set of VLANs The configuration names revision level and VLAN tO MSTI mapping must match in order to utilize the load sharing capabilities of MSTP otherwise each router will be in a different region To configure the Spanning Tree Protocol on all three routers 1 Configure MSTP on Router 1 edit protocols mstp configuration name mstp for R1 2 3 The names must match to be in the same region revision level 3 The revision levels must match bridge priority O This bridge acts as root bridge for VLAN 100 and 200 interface ael interface ae2 msti 1 vlan100 This VLAN corresponds to MSTP instance 1 msti 2 vlan200 This VLAN corresponds to MSTP instance 2 2 Configure MSTP on Router 2 edit protocols mstp configuration name mstp for R1 2 3 The names must match to be in the same region revision level 3 The revision levels must match interface ael interface ae3 msti 1 vlan100 This VLAN corresponds to MSTP instance 1 bridge priority 4096 This bridge acts as VLAN 100 designated bridge on the R2 R3 seg
19. denned rrarena e nee 6 bridging packet OWN in RA E N 44 bulk bridge domain configuration Of As di nine ani 59 Cc CFM Ethernet Overview run 104 comments in configuration statements xxii Copyright 2010 Juniper Networks Inc configuring Ethernet frame delay MX Series bridge domains MX Series integrated bridging and routing 34 MX Series interfaces and VLAN tags 24 MX Series Layer 2 DaSICS ee ese er see ee ee ee eg ee 22 MX Series spanning tree Protocols 32 conventions TEXT AMG Synta iese EIE nn nn curly braces in configuration statements customer SUPPOrT nes CONTACTING TAC rensenonennnmianasnns D DHCP relay MX Series configuration 74 MX Series overview ala MX Series VLAN configuration 75 documentation COMMENTS OM EE EE levered xxii domains implicit creation for VLANS ese er ee se ee ee een eek 47 dynamic profiles MX Series VPLS examples 63 64 68 E Ethernet AEFONYMS es be E ee eed ee EE N ek 3 ef ide AE EE CFM overview frame delay s Ese RE ee ee SE SE LFM example MAC addresSeS ss se se ann metro See Metro Ethernet OAM orde naa ring protection example ring protection failure condition ring protection normal operation ring protection Overview sesse se sesse se ee ee ee dn ig le el RA N ON 177 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide VLAN tag nestiNg sesse ee ee ee ee ee ee ee ee ee ee ee ee
20. sesse sek seek sek seek ek ek eek ee ek ek ee ee ee ee ee ee 3 U user priority IEEE 802 1p filtering on 99 V virtual switches CONIISUIEIOPE castes sees see arr EE edge bee ati ct 40 overview VLAN translation on MX Series 59 VLAN GEE EE OE tannins 11 NESTE sania EO EE 13 VLAN translation MX Series exampDIeS ee ee ee see ee ek ee ee ee ee ee ee 59 VLANS and VPLS ie ER Ee ee eek De gee Sk N ee SE Ego egg eg bridge network example implicit learning domains esse see ee see ee ee ee MX Series examDIeS ie ee ee ee ee ee ee eek ee MX Series examples with VPLS normalization and translation normalized RE GER ee Re Ie ER oe ee single VPLS example ese ee ee ee ee ee eek Ge ee eg translation iii VPLS labels example VPLS MX Series examples MX Series VLAN examples Virtual interfaces ss VPLS pseudowires with dynamic profiles on MX Copyright 2010 Juniper Networks Inc Index 179 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 180 Copyright 2010 Juniper Networks Inc
21. unit O vlan id 30 edit dynamic profiles green vpls pw 1 interfaces junos interface ifd name unit junos underlying unit number vlan tags outer 200 inner 100 NOTE Thisis not a complete router configuration With this configuration broadcast packets inside frames arriving with VLAN identifier 10 on ge 0 0 1 are normalized to a frame with VLAN identifier 100 The broadcast packet and frames egressing ge 0 0 2 or ge 0 0 3 have this VLAN value swapped to 20 and 30 respectively according to the interface configuration Frames egress the VPLS pseudowire in routing instance green with an outer VLAN tag value of 200 pushed on top of the normalized value CE Routers Without Dynamic Profiles 66 You can apply a dynamic profile to an entire VPLS configuration not just a neighbor Consider the following configuration which does not use dynamic profiles to manipulate VLAN identifiers on a customer edge CE router with VLAN identifier 100 edit routing instances green instance type vpls interface ge 0 0 1 1 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 ge 0 0 1 unit O vlan id 100 ge 0 0 2 unit O vlan id 100 Copyright 2010 Juniper Networks Inc Chapter 6 Dynamic Profiles for VLAN Interfaces and Protocols ge 0 0 3 1 unit O vlan id 100 D
22. vendors customers and service providers are attracted to the idea of using Ethernet in as many places of their networks as possible The perceived benefits of Ethernet are Most information starts and ends inside Ethernet frames Today this applies to data as well as voice for example VoIP and video for example Web cams Ethernet frames have all the essentials for networking such as globally unique source and destination addresses error control and so on Ethernet frames can carry any kind of packet Networking at Layer 2 is protocol independent independent of the Layer 3 protocol Layer 2 networks work for IP packets and all other Layer 3 protocols More layers added to the Ethernet frame only slow the networking process down nodal processing delay Adjunct networking features such as class of service CoS or multicasting can be added to Ethernet as readily as IP networks If more of the end to end transfer of information from a source to a destination can be done in the form of Ethernet frames more of the benefits of Ethernet can be realized on the network Networking at Layer 2 can be a powerful adjunct to IP networking but it is not usually a substitute for IP networking Copyright 2010 Juniper Networks Inc 9 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation D NOTE Networking at the frame level says nothing about the presence or absence of IP addres
23. 13 VEAN tasse ES ee DEE E nsenranda anna 11 Ethernet frame delay CONUN anina N OE N 122 examples StALSUES MA De ED ee RT examples bridge network with normalized VLANS ee 47 Ethernet frame delay 125 130 134 Ethernet LFM 138 139 140 142 Ethernet ring failure condition 172 Ethernet ring normal operation 171 Ethernet ring protection 148 single VPLS for several VLANS ee ese ee see ee eg 55 VLAN tags with VPLS labels ee esse ee sees seek 5 F features MX Series Layer 2 basics ese ee see ee ee ee eek 21 firewall filter example for MX Series 96 98 99 101 firewall filters TOF SA nR ES 95 font CONVENTIONS ns Xxi frame delay Edele N EE 119 G slet io N EE EE 3 l icons defined notice XX IEEE 802 1p priority bits filtering on 99 interface types LAVE AE A E AE EA A 14 interfaces slee Ai nn ere tee ins Mle 14 UNK ana A 14 L Layer 2 bridging firewall filter matching by IEEE 802 1p priority bits 99 matching by packet loss priority PLP 101 learned VLAN priority IEEE 802 1p filtering oo EE N OE R 99 M MAG addressbS si ae Ee ea 10 11 178 manuals COMMENTS OM vexscctistei nt ermiee titine re neo ie xxii Metro Ethernet cian hace RE SEG niacin 15 MX Series automatic bridge domains basic Layer 2 features bulk bridge domain configuration 59 configuring basic Layer 2 22 configuring bridge domains see esse ek ee ee 30 configuring integrated bridging and ROULINS s R
24. 2 4 1 forwarding No Signal Failure Admin State Clear IFF ready Clear IFF ready Note that the protection interface is discarding while the other interface is forwarding user router1 gt show protection group ethernet ring node state Ethernet ring APS State Event Ring Protection Link Owner pg101 idle NR RB Yes Restore Timer Quard Timer Operation state disabled disabled operational Note that Router 1 is the owner and timers are disabled user router1 gt show protection group ethernet ring statistics group name pg101 Ethernet Ring statistics for PG pg101 RAPS sent 5 RAPS received Local SF happened Remote SF happened NR event happened NR RB event happened h Note that only minimal RAPS messages have been sent to establish the ring Under normal operating conditions the other routers on the ring Router 2 and Router 3 will see the following similar output user router2 gt show protection group ethernet ring aps Ethernet Ring Name Request state No Flush Ring Protection Link Blocked pg102 NR No Yes Originator Remote Node ID No 00 01 01 00 00 01 Copyright 2010 Juniper Networks Inc 171 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation Router 3 will see almost identical information user router2 gt show protection group ethernet ring interface Ethernet ring port parameters for protection group pg102 Interface Control Channel Forward State Ring Protectio
25. 9 0 direction down auto discovery CFM on L2 CE2 edit interfaces ge 1 0 7 vlan tagging unit O vlan id 2000 edit protoccols oam ethernet connectivity fault management maintenance domain customer level 7 maintenance association customer site2 continuity check interval 1s mep 800 1 interface ge 1 0 7 0 direction down auto discovery Here are the configurations of CFM on the provider routers CFM on PE edit interfaces ge 5 0 9 1 Copyright 2010 Juniper Networks Inc 113 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide vlan tagging encapsulation flexible ethernet services unit O encapsulation vlan bridge vlan id 2000 ge 5 1 7 1 vlan tagging encapsulation flexible ethernet services unit O encapsulation vlan bridge vlan id 2000 edit bridge domains bridge vlan2000 1 domain type bridge vlan id 2000 interface ge 5 0 9 0 interface ge 5 1 7 0 edit protocols oam ethernet connectivity fault management maintenance domain provider outer f level 5 maintenance association provider outer sitel f continuity check interval 1s mep 200 interface ge 5 0 9 0 direction up auto discovery maintenance domain provider inner level 3 maintenance association provider inner sitel continuity check interval 1s mep 200 interface ge 5 1 7 0 direction down auto discovery CFM
26. Action Meaning Related Documentation 170 Ethernet ring data channel parameters for protection group ring 2 Interface STP index Forward State ge 2 0 5 24 forwarding ge 2 1 1 25 forwarding The output displayed shows the STP index number used by eachinterfaceinringinstances ring 1 and ring 2 The STP index controls the forwarding behavior for a set of VLANS on the data channel of a ring instance on aring interface For ring instances there are multiple STP index numbers here representing VLANs 200 300 500 and 600 The Forward State shows whether the data channel is forwarding or discarding traffic All data channels are forwarding traffic Verifying the VLANs on AS Verify the data channel logical interfaces and the VLAN IDs controlled by a ring instance data channel List dynamic VLAN membership user as1 gt show protection group ethernet ring vlan Ethernet ring IFBD parameters for protection group ring 1 Interface Vian STP Index Bridge Domain ge 2 0 5 200 22 default switch bd200 ge 2 1 1 200 23 default switch bd200 ge 2 0 5 300 22 default switch bd300 ge 2 1 1 300 23 default switch bd300 Ethernet ring IFBD parameters for protection group ring 2 Interface Vlan STP Index Bridge Domain ge 2 0 5 500 24 default switch bd500 ge 2 1 1 500 25 default switch bd500 ge 2 0 5 600 24 default switch bd600 ge 2 1 1 600 25 default switch bd600 The output displayed shows the ring interfaces ge 2 0 5 and ge 2 1 1 in protecti
27. DM 802 3ah The IEEE specification for link fault management LFM a method for OAM of Ethernet links 802 10 The IEEE specification for adding virtual local area network VLAN tags to an Ethernet frame B MAC The backbone source and destination MAC address fields found in the IEEE 802 lah provider MAC encapsulation header Copyright 2010 Juniper Networks Inc 3 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide bridge A network component defined by the IEEE that forwards frames from one LAN segment or VLAN to another The bridging function can be contained in a router LAN switch or other specialized device See also switch bridge domain A set of logical ports that share the same flooding or broadcast characteristics Asin a virtual LAN a bridge domain spans one or more ports of multiple devices By default each bridge domain maintains its own forwarding database of MAC addresses learned from packets received on ports belonging to that bridge domain See alsobroadcast domain and VLAN B TAG A field defined in the IEEE 802 1ah provider MAC encapsulation header that carries the backbone VLAN identifier information The format of the B TAG field is the same as that of the IEEE 802 1ad S TAG field See also S TAG B VID The specific VLAN identifier carried in a B TAG CFM Connectivity fault management The part of Ethernet OAM that monitors events at levels above the physical level as do
28. Example Configuring DHCP Relay ina VPLS Routing Instance Environment on page 75 74 Copyright 2010 Juniper Networks Inc Chapter 7 MX Series Router as a DHCP Relay Agent Example Configuring DHCP Relay in a VPLS Routing Instance Environment The following example configures DHCP relay in a bridge domain VLAN environment The MX Series router will trust only the MAC addresses learned on the listed interfaces NOTE This is not a complete router configuration The router has three interfaces two interfaces ge 2 2 4 and ge 2 2 6 using VLAN 100 for the DHCP clients and one xe 9 2 0 leading ot the DHCP server The router performs the DHCP snooping relay function Configure the edit interfaces Interfaces ge 2 2 4 1 encapsulation ethernet bridge unit O family bridge interface mode access vlan id 100 ge 2 2 6 encapsulation ethernet bridge unit O family bridge interface mode access vlan id 100 xe 9 2 0 1 unit O family bridge interface mode access vlan id 100 Configure the Routing edit routing instances Instance Virtual vsl Switch instance type virtual switch interface ge 2 2 4 0 interface ge 2 2 6 0 interface xe 9 2 0 bridge domains bd1 domain type bridge vlan id 100 forwarding options dhcp relay DHCP snooping group hdhcp Copyright 2010 Juniper Networks Inc 75 Junos 10 4 MX Series Ethernet Services Routers Solutions Guid
29. Figure 5 on page 23 The figure shows three MX Series routers acting as Layer 2 devices Copyright 2010 Juniper Networks Inc Chapter 2 Basic Layer 2 Features on MX Series Routers Figure 5 Bridging Network with MX Series Routers VLAN 205 VLAN 100 200 VLAN 200 ge 2 2 2 ge 2 2 1 ge 2 2 6 We e 2 1 3 switch ge 2 1 5 Ne FT ge 2 1 2 VLAN 200 205 ge 2 2 4 EE E SE switch ge 5 1 3 gt ge 11 1 3 ge 5 1 4 Pd Ny ge 11 1 4 5 1 5 r LAN 200 205 gei14 1 5 ge switch ge 2 2 9 ge 5 1 0 ge 11 1 0 3 ge 5 1 1 N ge 2 Router 2 Jgesf A t AE3 j ge 11 112 Router 3 xe 2 1 0 xe 1 1 0 VLAN 100 VLAN 200 VLAN 200 VLAN 200 VLAN 100 ge 2 2 2 ge 3 3 3 ge 2 2 6 ge 3 3 3 ge 2 2 2 Internet The three routers each have a series of hosts on their Ethernet interfaces as well as aggregated Ethernet links between them Router 2 and Router 3 are linked to the Internet and Router 1 and Router 3 are also linked to switches configured with a range of VLANs as shown in the figure Because the VLAN tags are important the routers run Multiple STP MSTP on the links connecting them to prevent bridging loops Rapid STP or RSTP does not recognize VLAN tags and blocks ports without regard for VLAN tagging Example Scenario The network administrator wants to configure these links and devices so that Thesix Gigabit Ethernet links between Route
30. Guide Copyright 2010 Juniper Networks Inc 73 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related MX Series Ethernet Services Routers Solutions Page D tati oe EE OON Example Configuring DHCP Relay in a Bridge Domain VLAN Environment on page 74 Example Configuring DHCP Relay in a VPLS Routing Instance Environment on page 75 Example Configuring DHCP Relay in a Bridge Domain VLAN Environment The following example configures DHCP relay in a VPLS environment to trust only the MAC addresses learned on the listed interfaces NOTE This is not a complete router configuration edit routing instances classic vpls instance type vpls interface ge 1 1 1 0 interface ge 1 1 2 0 interface ge 1 1 3 0 interface ge 1 1 4 0 interface ge 1 1 5 0 vlan id 20 forwarding options dhcp relay Here is where DHCP is configured group vlan 20 bridge interface ge 1 1 1 0 interface ge 1 1 2 0 interface ge 1 1 3 0 interface ge 1 1 4 0 interface ge 1 1 5 0 protocol vpls site id 567 Other VPLS configuration statements Only MAC addresses learned on the five listed Gigabit Ethernet interfaces will be trusted for DHCP relay purposes For more information on configuring DHCP see the Junos OS Subscriber Access Configuration Guide Related MX Series Ethernet Services Routers Solutions Page D tati eee MX Series Router as a Layer 2 DHCP Relay Agent on page 73
31. MEP can send a request to begin a two way delay measurement to its peer MEP which responds with timestamp information Run time statistics are collected and displayed at the initiator MEP The clocks do not need to be synchronized at the transmitting and receiving MEPs The Junos OS supports the optional timestamps in delay measurement reply DMR frames to increase the accuracy of delay calculations The Junos OS also supports hardware assisted timestamping for Ethernet frame delay protocol data units PDUs in the reception path Use the show commands at the initiator MEP to display two way delay statistics and at the receiver MEP to display one way delay statistics The following are some limitations with regard to using Ethernet frame delay measurement This feature is available only on MX Series routers Ethernet frame delay measurements are available only when the distributed periodic packet management daemon ppmd is enabled The statistics collected are lost after graceful Routing Engine switchover GRES You can monitor only one session to the same remote MEP or MAC address Accuracy is compromised when the system changes such as from reconfiguration We recommend performing Ethernet frame delay measurements on a stable system Theuse of Ethernet frame delay measurements on aggregated Ethernet and pseudowire interfaces is not supported The use of hardware assisted timestamping is not supported on all MX DPCs
32. Monitoring and Fault Management Solutions for MX Series Routers Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements 119 Table 3 Monitor Ethernet Delay Command Parameters 123 Table 4 Show Ethernet Delay Command Parameters 125 Chapter 13 Ethernet Ring Protection 44 145 Table 5 Components of the Network Topology 156 Copyright 2010 Juniper Networks Inc XV Junos 10 4 MX Series Ethernet Services Routers Solutions Guide xvi Copyright 2010 Juniper Networks Inc About This Guide This preface provides the following guidelines for using the Junos OS MX Series Ethernet Services Routers Solutions Guide Junos Documentation and Release Notes on page xvii Objectives on page xviii Audience on page xviii Supported Routing Platforms on page xix Using the Indexes on page xix Using the Examples in This Manual on page xix Documentation Conventions on page xx Documentation Feedback on page xxii Requesting Technical Support on page xxii Junos Documentation and Release Notes For a list of related Junos documentation see http www juniper net techpubs software junos If the information in the latest release notes differs from the information in the documentation follow the Junos Release Notes To obtain the most current version of all Juniper Networks technical document
33. Rev B or higher is required If you attempt to perform Ethernet frame delay measurements to a non MX partner the incoming Ethernet frame delay PDUs are discarded silently Ethernet delay measurement commands and capabilities are not available on non MX routers Related MX Series Ethernet Services Routers Solutions Page Documentation Configuring MEP Interfaces to Support ETH DM on page 122 Triggering an ETH DM Session on page 123 e Viewing ETH DM Statistics on page 124 Configuring One Way ETH DM with Single Tagged Interfaces on page 125 Configuring Two Way ETH DM with Single Tagged Interfaces on page 130 Configuring ETH DM with Untagged Interfaces on page 134 Copyright 2010 Juniper Networks Inc 121 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Configuring MEP Interfaces to Support Ethernet Frame Delay Measurements Ethernet frame delay measurement is a useful tool for providing performance statistics or supporting or challenging Service Level Agreements SLAs By default Ethernet frame delay measurement uses software for timestamping and delay calculations You can optionally use hardware timing to assist in this process and increase the accuracy of the delay measurement results This assistance is available on the reception path Before you can perform Ethernet frame delay measurements on MX Series routers you must have done the following Configured Ethernet OAM and CFM correctly Prepar
34. Syntax Conventions continued Convention pipe symbol Description Indicates a choice between the mutually exclusive keywords or variables on either side of the symbol The set of choices is often enclosed in parentheses for clarity Examples broadcast multicast string string2 string3 pound sign Indicates a comment specified on the same line as the configuration statement to which it applies rsvp Required for dynamic MPLS only square brackets Enclose a variable for which you can substitute one or more values community name members community ids Indention and braces Identify a level in the configuration hierarchy semicolon J Web GUI Conventions Bold text like this Identifies a leaf statement at a configuration hierarchy level Represents J Web graphical user interface GUI items you click or select edit routing options static route default nexthop address retain e Inthe Logical Interfaces box select All Interfaces e To cancel the configuration click Cancel gt bold right angle bracket Separates levels in a hierarchy of J Web selections In the configuration editor hierarchy select Protocols gt Ospf Documentation Feedback We encourage you to provide feedback comments and suggestions so that we can improve the documentation You can send your comments to techpubs comments juniper net
35. The VLAN identifier is determined explicitly by configuration The VLAN identifier is specified as none meaning the VLAN tags are not translated or generated The inner and outer VLAN identifier tags are both determined explicitly by configuration MX Series Ethernet Services Routers Solutions Page Packet Flow Through a Bridged Network with Normalized VLANs on page 44 Configuring a Normalized VLAN for Translation or Tagging on page 45 Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces on page 47 Example Configuring a Provider Bridge Network with Normalized VLAN Tags on page 47 Example Configuring a Provider VPLS Network with Normalized VLAN Tags on page 51 Copyright 2010 Juniper Networks Inc 43 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Example Configuring One VPLS Instance for Several VLANS on page 55 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 1 Related Documentation 44 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
36. and ii the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license s for use of the Software Customer collectively the Parties 2 The Software In this Agreement Software means the program modules and features of the Juniper or Juniper supplied software for which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller or which was embedded by Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller Software also includes updates upgrades and new releases of such software Embedded Software means Software which Juniper has embedded in or loaded onto the Juniper equipment and any updates upgrades additions or replacements which are subsequently embedded in or loaded onto the equipment 3 License Grant Subject to payment of the applicable fees and the limitations and restrictions set forth herein Juniper grants to Customer a non exclusive and non transferable license without right to sublicense to use the Software in executable form only subject to the following use restrictions a Customer shall use Embedded Software solely as embedded in and for execution on Juniper equipment originally purchased by Customer from Juniper or an authorized Juniper reseller b Customer shall use the Software on a single hardware chassis having a single processing unit or as ma
37. 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 MX Series Et
38. configuring filter match conditions for Layer 2 bridging traffic on the MX Series routers see the Junos OS Policy Framework Configuration Guide Copyright 2010 Juniper Networks Inc 99 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide D NOTE Layer 2 bridging is supported only on the MX Series routers For more information about how to configure Layer 2 bridging see the Junos OS Policy Framework Configuration Guide the Junos OS Routing Protocols Configuration Guide and the Junos OS Feature Guide This example Layer 2 bridging firewall filter finds any incoming frames with an IEEE 802 1p learned VLAN priority level of either 1 or 2 and then classifies the packet in the best effort default forwarding class D NOTE This example does not present exhaustive configuration listings for all routers in the figures However you can use this example with a broader configuration strategy to complete the MX Series router network Ethernet Operations Administration and Maintenance OAM configurations To configure filtering of frames by IEEE 802 lp bits 1 Configure the firewall filter filter learn vlan configure forwarding edit firewall family bridge filter filter learn vlan configure forwarding termOf from learn vlan 1p priority 1 2 then forwarding class best effort 2 Apply the firewall filter filter learn vlan configure forwarding as an input filter to ge 0 0 0 edit interfaces ge
39. defaults Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection 153 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation MX Series Ethernet Services Routers Solutions Page Ethernet Ring Protection on page 145 Example Viewing Ethernet Ring Protection Status Normal Ring Operation on page 171 Example Viewing Ethernet Ring Protection Status Ring Failure Condition on page 172 Example Configuring Load Balancing Within Ethernet Ring Protection for MX Series Routers Requirements MX Series routers support Ethernet ring protection ERP to help achieve high reliability and network stability ERP is Used in router or bridge networks to protect against link failure A single ring topology is configured that uses one specific link called a ring protection link RPL to protect the whole ring When all links are up and running the RPL blocks traffic and remains idle However if a link fails the RPL routes traffic to bypass the failure on the ring MX Series routers now support ERP ring instances Whereas traffic in a ring topology follows the same path traffic within a ring instance uses data channels to allow some traffic to pass through one path while other traffic can follow a different one Dividing traffic in this way supports traffic load balancing in the ring This example describes how to use ERP with ring instances to load balance traffic while still pro
40. failed link will then unblock the RPL port so both ports are active D NOTE The R APS protocol does not detect the number of RPL owner nodes configured on the ring You must configure only one RPL and RPL owner per ring or protection switching will not work properly Ethernet ring protection only works when one link on the ring fails Multiple link failures will break the ring and cause protection switching to fail Several restrictions apply to Ethernet ring protection The Ethernet ring protection configured as a single instance only works at the physical level adjacent nodes must be directly connected The ring protection operates at the interface port level and not at the VLAN level Manual command based switching to protection mode is not supported Nonrevertive switching is not supported When the link failure is cleared traffic always returns to normal operation The interconnection of multiple rings for protection purposes is not supported You can configure Ethernet ring protection to optomize traffic load balancing by using multiple ring instances For more information about multiple ring instances see Ethernet Ring Protection Using Ring Instances for Load Balancing on page 147 MX Series Ethernet Services Routers Solutions Page Example Configuring Ethernet Ring Protection for MX Series Routers on page 148 Example Viewing Ethernet Ring Protection Status Normal Ring Operation on page 171 Exam
41. of Traffic Entering a VPLS Core on page 96 Example Configuring Filtering of Frames by MAC Address on page 98 Example Configuring Filtering of Frames by IEEE 802 1p Bits on page 99 102 Copyright 2010 Juniper Networks Inc CHAPTER 10 IEEE 802 1ag OAM Connectivity Fault Management Ethernet Operations Administration and Maintenance on page 103 Ethernet OAM Connectivity Fault Management on page 104 Example Configuring Ethernet CFM over VPLS on page 105 Example Configuring Ethernet CFM on Bridge Connections on page 112 Example Configuring Ethernet CFM on Physical Interfaces on page 116 Ethernet Operations Administration and Maintenance This topic provides an overview to help you effectively configure Ethernet Operations Administration and Maintenance OAM on a network of Juniper Networks MX Series Ethernet Services Routers For more information about configuring OAM parameters on Ethernet interfaces see the Junos OS Network Interfaces Configuration Guide Ethernet OAM provides the tools that network management software and network managers can use to determine how a network of Ethernet links is functioning Ethernet OAM should Rely only on the media access control MAC address or virtual local area network VLAN identifier for troubleshooting Work independently of the actual Ethernet transport and function over physical Ethernet ports or a virtual service such as pseudowire and so on Iso
42. of the GPL at http www gnu org licenses gpl html and a copy of the LGPL at http www gnu org licenses lgpl html 15 Miscellaneous This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles The provisions of the U N Convention for the International Sale of Goods shall not apply to this Agreement For any disputes arising under this Agreement the Parties hereby consent to the personal and exclusive jurisdiction of and venue in the state and federal courts within Santa Clara County California This Agreement constitutes the entire and sole agreement between Juniper and the Customer with respect to the Software and supersedes all prior and contemporaneous agreements relating to the Software whether oral or written including any inconsistent terms contained in a purchase order except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing by the party to be charged If any portion of this Agreement is held invalid the Parties agree that such invalidity shall not affect the validity of the remainder of this Agreement This Agreement and associated documentation has been written in the English language and t
43. or fill out the documentation feedback form at https www juniper net cgi bin docbugreport If you are using e mail be sure to include the following information with your comments Document or topic name URL or page number Software release version if applicable Requesting Technical Support Technical product support is available through the Juniper Networks Technical Assistance Center JTAC If you are a customer with an active J Care or JNASC support contract xxii Copyright 2010 Juniper Networks Inc About This Guide or are covered under warranty and need postsales technical support you can access our tools and resources online or open a case with JTAC JTAC policies For a complete understanding of our JTAC procedures and policies review the JTAC User Guide located at http www juniper net us en local pdf resource guides 7100059 en pdf Product warranties For product warranty information visit http www juniper net support warranty JTAC Hours of Operation The JTAC centers have resources available 24 hours a day 7 days a week 365 days a year Self Help Online Tools and Resources For quick and easy problem resolution Juniper Networks has designed an online self service portal called the Customer Support Center CSC that provides you with the following features Find CSC offerings http www juniper net customers support Find product documentation http www juniper net te
44. path database size 255 age 10s maintenance domain md6 level 6 maintenance association ma6 continuity check interval 100ms hold interval 1 mep 101 interface ge 0 2 5 0 direction down auto discovery From Router MX 2 start a one way delay measurement to Router MX 1 user MX 2 gt monitor ethernet delay measurement one way mep 201 maintenance domain md6 maintenance association ma6 count 10 One way ETH DM request to 00 90 69 0a 43 94 Interface ge 0 2 5 0 1DM Frames sent 10 Delay measurement statistics Packets transmitted 10 Average delay NA Average delay variation NA Best case delay NA Worst case delay NA The counters are displayed as part of the local MEP database on Router MX 2 user MX 2 gt show oam ethernet connectivity fault management mep database maintenance domain md6 maintenance domain ma6 Maintenance domain name md6 Format string Level 6 Maintenance association name ma6 Format string Continuity check status enabled Interval 100ms Loss threshold 3 frames MEP identifier 101 Direction down MAC address 00 90 69 0a 48 57 Auto discovery enabled Priority 0 Interface name ge 0 2 5 0 Interface status Active Link status Up Defects Remote MEP not receiving CCM no Erroneous CCM received no Cross connect CCM received no RDI sent by some MEP no Copyright 2010 Juniper Networks Inc 127 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide
45. received Invalid 1DMs received DMMs sent DMRs sent Valid DMRs received Invalid DMRs received Remote MEP count 1 t no no no no vi N N OOOOOOOOOOOORM HA OOOOO Copyright 2010 Juniper Networks Inc Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements Identifier MAC address State Interface 101 00 90 69 0a 48 57 ok ge 5 2 9 0 The remote Router MX 1 should also collect the delay statistics up to 100 per session for display with mep statistics or delay statistics user MX 1 show oam ethernet connectivity fault management mep statistics maintenance domain md6 MEP identifier 201 MAC address 00 90 69 0a 43 94 Remote MEP count 1 CCMs sent 3240 CCMs received out of sequence 0 LBMs sent 0 Valid in order LBRs received 0 Valid out of order LBRs received 0 LBRs received with corrupted data 0 LBRs sent 0 LTMs sent 0 LTMs received 0 LTRs sent 0 LTRs received 0 Sequence number of next LTM request 0 1DMs sent 0 Valid 1DMs received 10 Invalid 1DMs received 9 DMMs sent 0 DMRs sent 0 Valid DMRs received 0 Invalid DMRs received 0 Remote MEP identifier 101 Remote MAC address 00 90 69 0a 48 57 Delay measurement statistics Index One way delay Two way delay usec usec 1 370 2 357 3 344 4 332 5 319 6 306 7 294 8 281 9 269 10 255 Average one way delay 312 usec Average one way delay variation 11 usec Best case one way delay 2
46. ring Router 2 and Router 3 will see the following similar output Router 2 and Router 3 user router2 gt show protection group ethernet ring aps Operational Ethernet Ring Name Request state No Flush Ring Protection Link Blocked Commands Failure pg102 aF No No Condition originator Remote Node ID Yes 00 00 00 00 00 00 Note the failure event SF Router 3 will see almost identical information user router2 gt show protection group ethernet ring interface Ethernet ring port parameters for protection group pg102 Interface Control Channel Forward State Ring Protection Link End ge 1 2 1 ge 1 2 1 1 forwarding No ge 1 0 2 ge 1 0 2 1 discarding No Copyright 2010 Juniper Networks Inc 173 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 174 Related Documentation Signal Failure Admin State Clear IFF ready set IFF ready Note that the failed interface ge 1 0 2 1 is not forwarding Router 3 will see almost identical information user router2 gt show protection group ethernet ring node state Ethernet ring APS State Event Ring Protection Link Owner pg102 idle NR RB No Restore Timer Quard Timer Operation state disabled disabled operational Note that Router 2 is not the owner Router 3 will see almost identical information user router2 gt show protection group ethernet ring statistics group name pg102 Ethernet Ring statistics for PG pg102 RAPS sent rol RAPS received Local SF happened Remote SF happ
47. router1 gt show protection group ethernet ring aps Ethernet Ring Name Request state No Flush Ring Protection Link Blocked pg101 SF NO No Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection Originator Remote Node ID No 00 01 02 00 00 01 Note that the ring protection link is no longer blocked and the node is no longer marked as originator user routerl show protection group ethernet ring interface Ethernet ring port parameters for protection group pg101 Interface Contro1 Channel Forward State Ring Protection Link End ge 1 0 1 ge 1 0 1 1 forwarding Yes ge 1 2 4 ge 1 2 4 1 forwarding No Signal Failure Admin State Clear IFF ready Clear IFF ready Note that the protection interface is now forwarding so is the other interface user router1 gt show protection group ethernet ring node state how protection group ethernet ring node state Ethernet ring APS State Event Ring Protection Link Owner pg101 protected SF Yes Restore Timer Quard Timer Operation state disabled disabled operational Note that Router 1 has recorded the span failure SF user router1 gt show protection group ethernet ring statistics group name pg101 Ethernet Ring statistics for PG pg101 RAPS sent amp S RAPS received Local SF happened Remote SF happened NR event happened NR RB event happened HOMO Note that the R APS messages have recorded the remote failure Under a failure condition the other routers on the
48. sure that PPMD is configured properly Without distributed PPMD delay measurement results are not valid 122 Copyright 2010 Juniper Networks Inc Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements To perform Ethernet frame delay measurement make sure that the following configuration statement is NOT present edit routing options ppm no delegate processing This turns distributed PPMD OFF Related MX Series Ethernet Services Routers Solutions Page Doc mentation Ethernet Frame Delay Measurements on page 119 Triggering an ETH DM Session on page 123 Viewing ETH DM Statistics on page 124 Configuring One Way ETH DM with Single Tagged Interfaces on page 125 Configuring Two Way ETH DM with Single Tagged Interfaces on page 130 Configuring ETH DM with Untagged Interfaces on page 134 Triggering an Ethernet Frame Delay Measurements Session Before Ethernet frame delay measurement statistics can be displayed they must be collected To trigger Ethernet frame delay measurement use the monitor ethernet delay measurement one way two way remote mac address mep identifier maintenance domain name maintenance association ma id count count wait time operational command The fields for this command are described in Table 3 on page 123 Table 3 Monitor Ethernet Delay Command Parameters Parameter Parameter Range Description one way or two way NA Perform a one way or two way round trip d
49. tag values 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 vlan id value s in their VLAN tag fields Configuration and function of bridge domain c2 vlan 300 for customer c2 virtual switch is similar to but not identical to that of bridge domain cl vlan 100 for customer cl virtual switch Related MX Series Ethernet Services Routers Solutions Page Documentation 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 Example Configuring a Provider VPLS Network with Normalized VLAN Tags This topic provides a configuration example to help you effectively configure a network of Juniper Networks MX Series Ethernet Services 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 Copyright 2010 Juniper Networks Inc 51 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide For more information about configuring Ethernet pseudowires as part of VPLS see the Junos OS Feature Guide NOTE This topic does not present exh
50. to merge the incoming configuration into the current candidate configuration If the example configuration contains the top level of the hierarchy or multiple hierarchies the example is a full example In this case use the load merge command If the example configuration does not start at the top level of the hierarchy the example is a snippet In this case use the load merge relative command These procedures are described in the following sections Merging a Full Example To merge a full example follow these steps 1 From the HTML or PDF version of the manual copy a configuration example into a text file save the file with a name and copy the file to a directory on your routing platform For example copy the following configuration to a file and name the file ex script conf Copy the ex script conf file to the var tmp directory on your routing platform system scripts commit file ex script xsl interfaces fxpO 1 disable unit O family inet address 10 0 0 1 24 Copyright 2010 Juniper Networks Inc xix Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 2 Merge the contents of the file into your routing platform configuration by issuing the load merge configuration mode command edit user host load merge var tmp ex script conf load complete Merging a Snippet To merge a snippet follow these steps 1 From the HTML or PDF version of the manual copy a configu
51. unit number for the VPLS pseudowire is not available for in advance to configure characteristics such as VLAN identifiers and other parameters As aresult certain VLAN manipulation features that are easily applied to static interfaces such as xe ge and so on are either not supported on dynamic interfaces or supported in an awkward fashion However on MX Series routers there is another configuration method that dynamic interfaces can use to determine their VLAN parameters when they are created by a running router dynamic profiles A dynamic profile is a conceptual container that includes parameters associated with a dynamic entity parameters whose values are not know at the time the entity is configured For more information about dynamic profiles see the Junos OS Subscriber Access Configuration Guide There are many types of dynamic profiles The two dynamic profiles that are used in conjunction with VLANs and VPLS are Sjunos interface ifd name for a dynamic physical interface and Sjunos underlying unit number for a dynamic logical interface unit Dynamic profiles for VPLS are only supported on MX Series routers Related MX Series Ethernet Services Routers Solutions Page Documentation Copyright 2010 Juniper Networks Inc 63 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Example Configuring VPLS Pseudowires with Dynamic Profiles Basic Solutions on page 64 Example Configuring VPLS Pseudowires wi
52. vlan 101 set ethernet ring ring 2 west interface control channel ge 5 2 3 0 set ethernet ring ring 2 west interface control channel vlan 101 set ethernet ring ring 2 data channel vlan 500 600 3 Configure the routing instance the bridge domains and the VLAN IDs associated with each bridge domain edit routing instances user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 set vs instance type virtual switch set vs interface ge 3 2 4 0 set vs interface ge 5 2 3 0 set vs bridge domains bd100 vlan id 100 set vs bridge domains bd101 vlan id 101 set vs bridge domains bd200 vlan id 200 set vs bridge domains bd300 vlan id 300 set vs bridge domains bd500 vlan id 500 set vs bridge domains bd600 vlan id 600 Results Check the results of the configuration user cs1 gt show configuration 158 Copyright 2010 Juniper Networks Inc interfaces ge 3 2 4 1 vlan tagging unit O family bridge interface mode trunk vlan id list 100 1000 ge 5 2 3 1 vlan tagging unit O family bridge interface mode trunk vlan id list 100 1000 protocols protection group ethernet ring ring 1 east interface control channel ge 3 2 4 0 vlan 100 ring protcection link end west interface control channel ge 5 2 3 0 vlan 100 data channel vlan 200 300 J protection group 1 ethernet ring ring 2 east interface control cha
53. vlan id list 100 1000 2 Enable ERP specifying the control channels and data channels for ring 1 and ring 2 and configure ring 2 as the ring protection link owner NOTE Always configure the east interface statement first before configuring the west interface statement edit protection group user cs2 user cs2 user cs2 user cs2 user cs2 user cs2 user cs2 user cs2 user cs2 user cs2 user cs2 user cs2 set ethernet ring ring 1 east interface control channel ge 2 0 4 0 set ethernet ring ring 1 east interface control channel vlan 100 set ethernet ring ring 1 west interface control channel ge 2 0 8 0 set ethernet ring ring 1 west interface control channel vlan 100 set ethernet ring ring 2 data channel vlan 200 300 set ethernet ring ring 2 east interface control channel ge 2 0 4 0 set ethernet ring ring 2 east interface control channel vlan 101 set ethernet ring ring 2 ring protection link owner set ethernet ring ring 2 west interface control channel ge 2 0 8 0 set ethernet ring ring 2 west interface control channel vlan 101 set ethernet ring ring 2 west interface ring protection link end set ethernet ring ring 2 data channel vlan 500 600 3 Configure the routing instance the bridge domains and the VLAN IDs associated with each bridge domain edit bridge domains user cs2 user cs2 user cs2 user cs2 user cs2 user cs2 set bd100 vlan id 100 set bd101 vlan id 101 set bd200 vlan id 200 set b
54. 0 0 0 1 unit O family bridge filter input filter learn vlan configure forwarding Related MX Series Ethernet Services Routers Solutions Page Doc m ntation Firewall Filters for Bridge Domains and VPLS Instances on page 95 Example Configuring Policing and Marking of Traffic Entering a VPLS Core on page 96 Example Configuring Filtering of Frames by MAC Address on page 98 100 Copyright 2010 Juniper Networks Inc Chapter 9 Layer 2 Firewall Filters Example Configuring Filtering of Frames by Packet Loss Priority on page 101 Example Configuring Filtering of Frames by Packet Loss Priority To configure an MX Series router firewall filter to provide matching on the packet loss priority PLP level carried in the frame use the loss priority or loss priority except match condition Packet loss priority matching is available for all protocols For more detailed information about configuring firewall filters and configuring filter match conditions for Layer 2 bridging traffic on the MX Series routers see the Junos OS Policy Framework Configuration Guide NOTE Layer 2 bridging is supported only on the MX Series routers For more information about how to configure Layer 2 bridging see the Junos OS Network Interfaces Configuration Guide the Junos OS Routing Protocols Configuration Guide and the Junos OS Feature Guide This example Layer 2 bridging firewall filter finds any incoming frames with a packet
55. 010 Juniper Networks Inc Chapter 12 IEEE 802 3ah OAM Link Fault Management protocols oam ethernet link fault management interface ge 1 0 0 pdu interval 1000 pdu threshold 5 remote loopback 2 Configure LFM loopback on th edit interfaces ge 1 1 0 unit O family inet address 11 11 11 2 24 protocols oam ethernet e CE router link fault management interface ge 1 1 0 pdu interval 1000 pdu threshold 5 negotiation options allow remote loopback Related Documentation Example Configuring Ethernet Example Configuring Ethernet Example Configuring Ethernet MX Series Ethernet Services Ro uters Solutions Page Ethernet OAM Link Fault Management on page 137 LFM Between PE and CE on page 138 LFM for CCC on page 139 LFM for Aggregated Ethernet on page 140 Copyright 2010 Juniper Networks Inc 143 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 144 Copyright 2010 Juniper Networks Inc CHAPTER 13 Ethernet Ring Protection Ethernet Ring Protection on page 145 Ethernet Ring Protection Using Ring Instances for Load Balancing on page 147 Example Configuring Ethernet Ring Protection for MX Series Routers on page 148 Example Configuring Load Balancing Within Ethernet Ring Protection for MX Series Routers on page 154 Example Viewing Ethernet Ring Protection Status Normal Ring Operation on page 171 Exampl
56. 100ms hold interval 1 mep 101 interface ge 0 2 5 0 direction down auto discovery From Router MX 1 start a two way delay measurement to Router MX 2 user MX 1 monitor ethernet delay measurement two way mep 101 maintenance domain md6 maintenance association ma6 count 10 Two way ETH DM request to 00 90 69 0a 48 57 Interface ge 5 2 9 0 DMR received from 00 90 69 0a 48 57 Delay 100 usec Delay variation 0 usec DMR received from 00 90 69 0a 48 57 Delay 92 usec Delay variation 8 usec DMR received from 00 90 69 0a 48 57 Delay 92 usec Delay variation 0 usec DMR received from 00 90 69 0a 48 57 Delay 111 usec Delay variation 19 usec DMR received from 00 90 69 0a 48 57 Delay 110 usec Delay variation 1 usec DMR received from 00 90 69 0a 48 57 Delay 119 usec Delay variation 9 usec DMR received from 00 90 69 0a 48 57 Delay 122 usec Delay variation 3 usec DMR received from 00 90 69 0a 48 57 Delay 92 usec Delay variation 30 usec DMR received from 00 90 69 0a 48 57 Delay 92 usec Delay variation 0 usec DMR received from 00 90 69 0a 48 57 Delay 108 usec Delay variation 16 usec Delay measurement statistics Packets transmitted 10 Valid packets received 10 Average delay 103 usec Average delay variation 8 usec Best case delay 92 usec Worst case delay 122 usec The counters are displayed as part of the MEP database on Router MX 1 maintenance domain MD6 user MX 1 gt show oam ethernet connectivity fault ma
57. 200 122 vs bd200 ge 5 2 3 200 123 vs bd200 ge 3 2 4 300 122 vs bd300 ge 5 2 3 300 123 vs bd300 Ethernet ring IFBD parameters for protection group ring 2 Interface Vian STP Index Bridge Domain ge 3 2 4 500 124 vs bd500 ge 5 2 3 500 125 vs bd500 ge 3 2 4 600 124 vs bd600 ge 5 2 3 600 125 vs bd600 Meaning The output displayed shows the ring interfaces ge 3 2 4 and ge 5 2 3 in protection groups ring 1 and ring 2 For ring 1 VLAN 200 and VLAN 300 are being supported on both STP Index 122 and 123 on bridge domains bd200 and bd300 For ring 2 VLAN 500 and VLAN 600 are being supported on both STP Index 124 and 125 on bridge domains bd500 and bd600 The data channel controls the traffic on the VLAN IDs to facilitate load balancing Verifying the Ethernet Protection Ring on CS2 Purpose Verify that ERP is enabled on CS2 Action Show the status of the ring APS R APS messages to determine if there is a ring failure user cs2 gt show protection group ethernet ring aps Ethernet Ring Name Request state No Flush Ring Protection Originator Remote Copyright 2010 Juniper Networks Inc 167 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 168 Meaning Purpose Action Meaning Purpose Action Node ID Link Blocked Ring 1 NR No No No 00 21 59 03 ff d0 Ring 2 NR No Yes Yes The output displayed shows that protection groups ring 1 and ring 2 have a Request state of NR meaning there is no request for APS on the
58. 299776 Local interface ge 0 2 0 0 Status Up Encapsulation VLAN Q in Q and VCI Interworking Configuring PE2 with a Layer 2 Circuit over Aggregated Ethernet CE Configuation edit interfaces 82 at 2 0 0 encapsulation ethernet over atm atm options vpi 100 unit O vci 100 34 family inet address 30 1 1 1 24 Configure Ethernet over ATM on the ATM interface Copyright 2010 Juniper Networks Inc Chapter 8 MX Series Router in an ATM Ethernet Interworking Function PE1Configuation Configure the Layer 2 Circuit edit interfaces at 2 0 11 atm options vpi 100 unit O encapsulation vlan vci ccc vpi 100 vci range 32 63 ge 5 0 0 1 unit O family inet address 20 1 1 1 24 family mpls protocols mpls interface ge 5 0 0 0 ospf area 0 0 0 0 1 interface ge 5 0 0 0 interface loO 0 passive ldp interface all circuit neighbor 10 255 171 14 interface at 2 0 1 0 1 virtual circuit id 100 PE2 Configuation Configure the Layer 2 Circuit over Aggregated Ethernet on the MX Series Router edit chassis aggregated devices ethernet device count 1 interfaces Copyright 2010 Juniper Networks Inc 83 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide ge 0 2 0 1 gigether options 802 3ad aeO ge 0 2 8 1 unit OT family inet address 20 1 1 10 24 fam
59. 55 usec Worst case one way delay 370 usec user MX 1 gt show oam ethernet connectivity fault management delay statistics maintenance domain md6 MEP identifier 201 MAC address 00 90 69 0a 43 94 Remote MEP count 1 Remote MAC address 00 90 69 0a 48 57 Delay measurement statistics Index One way delay Two way delay usec usec 1 370 Copyright 2010 Juniper Networks Inc 129 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation 2 357 3 344 4 332 5 319 6 306 7 294 8 281 9 269 10 255 Average one way delay 312 usec Average one way delay variation 11 usec Best case one way delay 255 usec D NOTE When two systems are close to each other their one way delay values are very high compared to their two way delay values This is because one way delay measurement requires the timing for the two systems to be synchronized at a very granular level and MX Series routers do not support this granular synchronization However two way delay measurement does not require synchronized timing making two way delay measurements more accurate MX Series Ethernet Services Routers Solutions Page Ethernet Frame Delay Measurements on page 119 Configuring MEP Interfaces to Support ETH DM on page 122 Triggering an ETH DM Session on page 123 Viewing ETH DM Statistics on page 124 Configuring Two Way ETH DM with Single Tagged Interfaces on page 130 Configuring ETH DM with Untagge
60. A GE EE GER GR ES EE 34 configuring interfaces and VLAN tags 24 configuring spanning tree protocols 32 Ethernet CM inner Ethernet LEM nes Ethernet OAM esse see see se se ek ek ek ee ek eek ee ee ee ee example configurations firewall filter example firewall filters hs Layer 2 interface types VLAN and VPLS configurations 59 60 VLAN normalization esse see se ee ek se see ek ee 43 45 VLAN translation 59 VPLS pseudowires with dynamic olie N EN 63 64 68 MX Series router ATM inter WOrkKINS nn 77 ATM interworking example 79 N networking With bridges and routers ee ee ee see see ek ee ee ee ee 6 normalization VAN EE ententes 43 45 normalized VLAN nr 46 translation RE Ee Pe Ee ess 45 notice icons defined ss XX O OAM Ethernet CEM se ese Ee Pe 105 112 116 Ethernet LEM sees see see se ee ek ek ee ee eek ee ee ee ee ee ee 137 Ethernet OVervieW sesse see ee sek se ee ee ek ek Ee ee ee 103 P packet flow edel ii AE OE ED EE N packet loss priority PLP filtering on parentheses in syntax descriptions Copyright 2010 Juniper Networks Inc R ring protection Ethernet overview 145 147 routers EN al so EE 6 S statistics Ethernet frame delay 123 124 support technical See technical support syntax Conventions is es SERS SEE Ee Ge ee PA De gegee xxi T technical support contacting JTAC s sessssssersssrssnssrrerirsrsenrrrsnnrsrrerresrren xxii terminology Ethernet
61. AC address The target MIP or MEP generates a unicast loopback reply in response to the received loopback message The loopback message follows the same path as a data packet and intermediate bridges simply forward the packet to the destination MIP or MEP MX Series Ethernet Services Routers Solutions Page Ethernet OAM Connectivity Fault Management on page 104 Example Configuring Ethernet CFM over VPLS on page 105 Example Configuring Ethernet CFM on Bridge Connections on page 112 Example Configuring Ethernet CFM on Physical Interfaces on page 116 Ethernet OAM Connectivity Fault Management 104 The most complete connectivity fault management CFM is defined in IEEE 802 1ag This topic emphasizes the use of CFM in a Metro Ethernet environment The major features of CFM are Fault monitoring using the continuity check protocol This is a neighbor discovery and health check protocol which discovers and maintains adjacencies at the VLAN or link level Path discovery and fault verification using the linktrace protocol Similar to IP traceroute this protocol maps the path taken to a destination MAC address through one or more bridged networks between the source and destination Fault isolation using the loopback protocol Similar to IP ping this protocol works with the continuity check protocol during troubleshooting CFM partitions the service network into various administrative domains For example operators pr
62. C address 00 90 69 0a 43 94 Remote MEP count 1 CCMs sent 3154 CCMs received out of sequence 0 LBMs sent 0 Valid in order LBRs received 0 Valid out of order LBRs received 0 LBRs received with corrupted data 0 LBRs sent 0 LTMs sent 0 LTMs received 0 LTRs sent 0 LTRs received 0 Sequence number of next LTM request 0 1DMs sent 0 Valid 1DMs received 0 Invalid 1DMs received 0 DMMs sent 10 DMRs sent 0 Valid DMRs received 10 Invalid DMRs received 0 Remote MEP identifier 101 Remote MAC address 00 90 69 0a 48 57 Delay measurement statistics Index One way delay Two way delay usec usec 100 92 92 111 110 119 122 NOR KUR Copyright 2010 Juniper Networks Inc 133 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 8 92 9 92 10 108 Average two way delay 103 usec Average two way delay variation 8 usec Best case two way delay 92 usec Worst case two way delay 122 usec The collected delay statistics are also saved up to 100 per session and displayed as part of the MEP delay statistics on Router MX 1 user MX 1 gt show oam ethernet connectivity fault management delay statistics maintenance domain md6 MEP identifier 201 MAC address 00 90 69 0a 43 94 Remote MEP count 1 Remote MAC address 00 90 69 0a 48 57 Delay measurement statistics Index One way delay Two way delay Cusec Cusec 1 100 2 92 3 92 4 111 5 110 6 119 7 122 8 92 9 92
63. Counts frame with the bad source MAC address discard term two then accept Make sure to accept other traffic 2 Apply evil mac address as an input filter to vlan100200 on Router 1 edit routing instances virtual switch R1 1 bridge domains vlan100200 1 domain type bridge forwarding options filter input evil mac address Related MX Series Ethernet Services Routers Solutions Page Documentation Firewall Filters for Bridge Domains and VPLS Instances on page 95 Example Configuring Policing and Marking of Traffic Entering a VPLS Core on page 96 Example Configuring Filtering of Frames by IEEE 802 1p Bits on page 99 Example Configuring Filtering of Frames by Packet Loss Priority on page 101 Example Configuring Filtering of Frames by IEEE 802 1p Bits For the bridge and vpls protocol families only MX Series router firewall filters can be configured to provide matching on IEEE 802 1p priority bits in packets with dual VLAN tags _To configure a firewall filter term that includes matching on IEEE 802 1p learned VLAN priority in the outer VLAN tag use the learn vlan 1p priority or learn vlan 1p priority except match condition To configure a firewall filter term that includes matching on IEEE 802 1p user priority in the inner VLAN tag use the user vlan Ip priority or user vlan 1p priority except match condition For more detailed information about configuring firewall filters and
64. FM session to another However these measurements are not made to Maintenance Intermediate Points MIPs Figure 18 Ethernet OAM Overview Customer bridge Operator 1 bridges Operator 2 bridges Customer bridge Mag lag Man las Was ia Mg ag Mn ag Man Wag or or or or or or or or or or or or MIP Dil MIP DI MIP Lis MIP Dl MIP Dl MIP DI al il mn lt gt Provider level UE lt MIP MIP gt CIE Operator level Tee lt LM UE Up MEPs MIP gem MIP Seg Up MEP MEP Maintenance End Point MIP Maintenance Intermediate Point also known as a Loopback Point 120 9016806 There are two types of Ethernet frame delay measurements One way Two way round trip For one way Ethernet frame delay measurement either MEP can send a request to begin a one way delay measurement to its peer MEP However the statistics are collected only at the receiver MEP This feature requires the clocks at the transmitting and receiving MEPs to be synchronized If these clocks fall out of synchronization only one way delay variation and average delay variation values are computed correctly and therefore valid Use the show commands at the receiver MEP to display one way delay statistics Copyright 2010 Juniper Networks Inc Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements For two way round trip Ethernet frame delay measurement either
65. G S tagged service interface The interface between a customer edge CE device and the I BEB or IB BEB network components Frames passed through this interface contain an S TAG field See also B tagged service interface S VLAN The specific service instance VLAN identifier carried inside the S TAG field See also B VID switch A network device that attempts to perform as much of the forwarding task in hardware as possible The switch can function as a bridge LAN switch router or some other specialized device and forwards frames packets or other data units See also bridge virtual switch A routing instance that can contain one or more bridge domains VLAN Virtual LAN Defines a broadcast domain a set of logical ports that share the same flooding or broadcast characteristics VLANs span one or more ports on multiple devices By default each VLAN maintains its own Layer 2 forwarding database containing MAC addresses learned from packets received on ports belonging to the VLAN See also bridge domain Y1731 The international standard for Ethernet Frame Delay Measurements ETH DM At this point these acronyms and terms are just a bewildering array of letters and words It is the goal of this manual to make the contents of this list familiar and allow you to place each of them in context and understand how they relate to each other To do that a basic understanding of modern Ethernet standards and technology i
66. JUNIPET NETWORKS Junos OS MX Series Ethernet Services Routers Solutions Guide Published 2010 10 07 Copyright 2010 Juniper Networks Inc Juniper Networks Inc 1194 North Mathilda Avenue Sunnyvale California 94089 USA 408 745 2000 www juniper net This product includes the Envoy SNMP Engine developed by Epilogue Technology an Integrated Systems Company Copyright 1986 1997 Epilogue Technology Corporation All rights reserved This program and its documentation were developed at private expense and no part of them is in the public domain This product includes memory allocation software developed by Mark Moraes copyright 1988 1989 1993 University of Toronto This product includes FreeBSD software developed by the University of California Berkeley and its contributors All of the documentation and software included in the 4 4BSD and 4 4BSD Lite Releases is copyrighted by the Regents of the University of California Copyright 1979 1980 1983 1986 1988 1989 1991 1992 1993 1994 The Regents of the University of California All rights reserved GateD software copyright 1995 the Regents of the University All rights reserved Gate Daemon was originated and developed through release 3 0 by Cornell University and its collaborators Gated is based on Kirton s EGP UC Berkeley s routing daemon routed and DCN s HELLO routing protocol Development of Gated has been supported in part by the
67. Juniper for all costs and damages related to any liability incurred by Juniper as a result of Customer s non compliance or delay with its responsibilities herein Customer s obligations under this Section shall survive termination or expiration of this Agreement 11 Export Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign agency or authority and not to export or re export the Software or any direct product thereof in violation of any such restrictions laws or regulations or without all necessary approvals Customer shall be liable for any such violations The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customer s ability to export the Software without an export license iv Copyright 2010 Juniper Networks Inc 12 Commercial Computer Software The Software is commercial computer software and is provided with restricted rights Use duplication or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 2277201 through 2277202 4 FAR 12 212 FAR 27 405 b 2 FAR 52 227 19 or FAR 52 227 14 ALT Ill as applicable 13 Interface Information To the extent required by applicable law and at Customer s written request Juniper shall provide Customer With the interface information needed to achieve interoperability between the Soft
68. M for Aggregated Ethernet 140 Example Configuring Ethernet LFM with Loopback Support 142 Ethernet Ring Protection 0 00 cee 145 Ethernet Ring Protection SE EE ee se teen eens 145 Ethernet Ring Protection Using Ring Instances for Load Balancing 147 Example Configuring Ethernet Ring Protection for MX Series Routers 148 Example Topolosy ss 2 Vets show cde ewe awed ER MEE need eae ee 148 Router 1 RPL Owner Configuration 149 Router 2 Contiguration sis rs EE EE BEE und DEE BEE eek edhe soo oe ean 150 Router3 ConiisuratiOn ss EE EE RE DE Ee eel KEER PER ESE SE EE 152 Example Configuring Load Balancing Within Ethernet Ring Protection for MX Series ROULEIS EER oe ER DE RE Pee eee EER DEE ose ed VR EER EER ER ieee ad 154 Example Viewing Ethernet Ring Protection Status Normal Ring Operation 171 Example Viewing Ethernet Ring Protection Status Ring Failure Condition 172 Copyright 2010 Juniper Networks Inc Xi Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Part 4 Index xii Copyright 2010 Juniper Networks Inc List of Figures Part 1 Chapter 1 Part 2 Chapter 2 Chapter 4 Chapter 8 Part 3 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Overview Overview of Ethernet Solutions 3 Figure 1 Native Normal and VLAN Tagged Ethernet Fames 12 Figu
69. N 200 is translated to 500 oningress VLAN 500 is translated to VLAN 200 on egress Copyright 2010 Juniper Networks Inc 59 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide The following example translates incoming trunk packets from VLAN identifier 200 to 500 and 201 to 501 other valid VLAN identifiers are not affected edit interfaces ge 1 0 1 unit O Other logical interface statements family bridge interface mode trunk Translation is only for trunks vlan id list 100 500 600 vlan rewrite translate 200 500 translate 201 501 Other bridge statements D NOTE This example also translates frame VLANs from 500 to 200 and 501 to 201 on egress Related MX Series Ethernet Services Routers Solutions Page Documentation Bulk Configuration of VLANs and Bridge Domains on page 59 Example Configuring Multiple Bridge Domains with a VLAN ID List on page 60 Example Configuring Multiple Bridge Domains with a VLAN ID List To configure multiple bridge domains with one statement include the vlan id list statement at the edit bridge domains hierarchy level The following example automatically configures 4093 bridge domains named sales vlan 2 through sales vlan 4094 edit bridge domains sales This is the prefix vlan id list 2 4096 These are the numbers You can configure these bridge domains in a virtual switch routing instance However if a VLAN iden
70. NOTE This is not a complete router configuration With this configuration broadcast packets inside frames arriving on ge 0 0 1 are normalized to a dual tagged frame with an outer VLAN value of 200 and an inner VLAN value of 100 The same configuration can be accomplished using dynamic profiles CE Routers and Dynamic Profiles Consider the following configuration which uses dynamic profiles at the protocols level edit routing instances green instance type vpls interface ge 0 0 1 interface ge 0 0 21 interface ge 0 0 3 1 vlan id 100 Desired inner VLAN tag on the VPLS pseudowire protocols vpls associate profile green_vpls_pw_2 The profile vpls id 10 neighbor 10 1 1 20 more edit interfaces ge 0 0 1 unit O vlan id 100 ge 0 0 2 unit O vlan id 100 ge 0 0 3 1 unit O vlan id 100 edit dynamic profiles green vpls pw 2 interfaces junos interface ifd name unit junos underlying unit number Copyright 2010 Juniper Networks Inc 67 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation vlan tags outer 200 inner 100 With this configuration broadcast packets inside frames arriving with VLAN identifier 100 on ge 0 0 1 are normalized to a frame with VLAN identifier 100 in this case they are unchanged The broadcast packet and frames egressing ge 0 0 2 or ge 0 0 3 are unchanged as well according to the interface con
71. National Science Foundation Portions of the GateD software copyright 1988 Regents of the University of California All rights reserved Portions of the GateD software copyright 1991 D L S Associates This product includes software developed by Maker Communications Inc copyright 1996 1997 Maker Communications Inc Juniper Networks Junos Steel Belted Radius NetScreen and ScreenOS are registered trademarks of Juniper Networks Inc in the United States and other countries The Juniper Networks Logo the Junos logo and JunosE are trademarks of Juniper Networks Inc All other rademarks service marks registered trademarks or registered service marks are the property of their respective owners Juniper Networks assumes no responsibility for any inaccuracies in this document Juniper Networks reserves the right to change modify ransfer or otherwise revise this publication without notice Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks U S Patent Nos 5 473 599 5 905 725 5 909 440 6 192 051 6 333 650 6 359 479 6 406 312 6 429 706 6 459 579 6 493 347 6 538 518 6 538 899 6 552 918 6 567 902 6 578 186 and 6 590 785 Junos OS MX Series Ethernet Services Routers Solutions Guide Release 10 4 Copyright 2010 Juniper Networks Inc All rights reserved Printed in USA Writing Walter G
72. O Alternate port H VLAN 100 vere ee van se ee VLAN 200 016833 Related MX Series Ethernet Services Routers Solutions Page Docum ntation Layer 2 Features for a Bridging Environment on page 21 Example Roadmap Configuring a Basic Bridge Domain Environment on page 22 Example Step Configuring Interfaces and VLAN Tags on page 24 Example Step Configuring Bridge Domains on page 30 Example Step Configuring Integrated Bridging and Routing on page 34 Example Step Configuring Integrated Bridging and Routing Router 2 and Router 3 on the bridging network act as a kind of gateway to the Layer 3 routers in the rest of the network Router 2 and Router 3 must be able to route packets as well as bridge frames This requires the configuration of integrated routing and bridging IRB on Routers 2 and 3 The link to the router network is xe 2 1 0 on Router 2 and xe 1 1 0 on Router 3 You configure IRB in two steps 1 Configure the IRB interface using the irb statement 34 Copyright 2010 Juniper Networks Inc Chapter 2 Basic Layer 2 Features on MX Series Routers 2 Reference the IRB interface at the bridge domain level of the configuration IRB supports Layer 2 bridging and Layer 3 routing on the same interface If the MAC address on the arriving frame is the same as that of the IRB interface then the packet inside the frame is routed Otherwise the MAC address is learned or looked up in the MAC add
73. Other routing instance statements edit dynamic profiles green_vpls_pw_2 interfaces junos interface ifd name unit junos underlying unit number family bridge interface mode trunk inner vlan id list 10 20 40 50 J Removed Accounting VLAN 30 70 Copyright 2010 Juniper Networks Inc Chapter 6 Dynamic Profiles for VLAN Interfaces and Protocols D NOTE This is not a complete router configuration In this case frames arriving on the interfaces are classified according to their bridge domains and switched if necessary to the VPLS pseudowire trunk except for Engineering frames Engineering frames VLAN 30 are only switched within the interfaces listed within bridge domain accounting and any statically configured trunk interfaces and are prevented from crossing the VPLS pseudowire due to the absence of VLAN 30 on the trunk We can combine the two examples and use dynamic profiles to forward the frames other than accounting frames to the remote site with an out tag of 200 This configuration keeps the Accounting frames from reaching the remote site and pushes an outer tag of 200 on VPLS pseudowire traffic edit routing instances green instance type virtual switch Other routing instance statements protocols vpls site range 10 site sample site 1 site identifier 1 associate profile green_vpls_pw_3 Apply profile here Other routing instance statements edit dynamic profiles gre
74. PE1 Site 1 DA P1 SA L2PE1 y 0x8100 VLAN 500 Transport LABEL VPLS LABEL DA SA g0162828 Ethertype 0x800 L2 PE4 SIP Site 4 56 The Layer 2 PE routers are MX Series routers Each site is connected to two P routers for redundancy although both links are only shown for L2 PE1 at Site 1 Site 1 is connected to PO and P Site 2 is connected to PO and P2 not shown Site 3 is connected to P2 and P3 and Site 4 is connected to P1 and P3 VPLS pseudowires configured on the PE and P routers carry traffic between the sites The pseudowires for the VPLS instances are shown with distinct dashed and dotted lines Most sites have multiple VLANs configured Service provider SP 1 is providing VPLS services for customer Cl services that could span several sites Now customer C1 can have many VLANS in the range from 1 through 1000 for example Copyright 2010 Juniper Networks Inc Chapter 4 VLANS Within Bridge Domain and VPLS Environments If VLANs 1 through 1000 for customer C1 span the same sites then the vlan id all and vlan range statements provide a way to switch all of these VLANS with a minimum configuration effort and fewer switch resources NOTE You cannot use the vlan id all statement if you configure an IRB interface on one or more of the VLANs The following example illustrates the use of the vlan id all statement edit interfac
75. PE2 with a Layer 2 Circuit CE Configuation Configure Ethernet over ATM on the ATM interface edit interfaces Copyright 2010 Juniper Networks Inc 79 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide at 2 0 0 1 encapsulation ethernet over atm atm options vpi 100 unit O vci 100 34 family inet address 30 1 1 1 24 PE1Configuation Configure the Layer 2 Circuit edit interfaces at 2 0 11 atm options vpi 100 unit O encapsulation vlan vci ccc vpi 100 vci range 32 63 ge 5 0 0 unit O family inet address 20 1 1 1 24 family mpls protocols mpls interface ge 5 0 0 0 ospf area 0 0 0 0 1 interface ge 5 0 0 0 interface loO 0 passive ldp interface all circuit neighbor 10 255 171 14 interface at 2 0 1 0 virtual circuit id 100 80 Copyright 2010 Juniper Networks Inc Chapter 8 MX Series Router in an ATM Ethernet Interworking Function PE2 Configuation Configure the Layer 2 Circuit on the MX Series Router edit interfaces ge 0 2 0 1 vlan vci tagging encapsulation vlan vci ccc unit O vlan id 100 inner vlan id range start 32 end 63 ge 0 2 8 unit O family inet address 20 1 1 10 24 family mpls protocols mpls interface ge 0 2 8 0 ospf area 0 0 0 0 interface ge 0 2 8 0 interface loO 0 passive ldp interface all ci
76. Routers Layer 2 Firewall Filters tics sees kie Sea anata Bek du dues nes re aise tro ess 95 IEEE 802 1ag OAM Connectivity Fault Management 103 ITU T Y 1731 Ethernet Frame Delay Measurements 119 IEEE 802 3ah OAM Link Fault Management 137 Ethernet Ring Protection 4 444 145 Index INDEX 5 s RE EE RE HO EE ee des 177 Copyright 2010 Juniper Networks Inc vii Junos 10 4 MX Series Ethernet Services Routers Solutions Guide viii Copyright 2010 Juniper Networks Inc Table of Contents About This Guide reses EE sie RES BERE RR DERE DEE EE ened REK SE EE xvii Junos Documentation and Release Notes xvii ODJECtIVES sise d s N ER EE EE Gene OR RE EE EK IE xviii Audiente ARE EE HE EE et Obi we WE bende NG xviii Supported Routing Platforms xix Using the lINGEX S 2 412410 SERE EER EE RE oa nbn patio alee EE ae din RE xix Using the Examples in This Manual xix Merging a Full Example xix Merging a SniDDEt issue se wld se aren fab es da W s be NE ne eee XX Documentation Conventions EE EE eee eee eens XX Documentation Feedback SS ES SS eee teens xxii Requesting Technical Support xxii Self Help Online Tools and Resources
77. S OR FOR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT THE SOFTWARE OR ANY JUNIPER OR JUNIPER SUPPLIED SOFTWARE IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER SUPPLIED SOFTWARE EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW JUNIPER DISCLAIMS ANY AND ALL WARRANTIES IN AND TO THE SOFTWARE WHETHER EXPRESS IMPLIED STATUTORY OR OTHERWISE INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT IN NO EVENT DOES JUNIPER WARRANT THAT THE SOFTWARE OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE WILL OPERATE WITHOUT ERROR OR INTERRUPTION OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK In no event shall Juniper s or its suppliers or licensors liability to Customer whether in contract tort including negligence breach of warranty or otherwise exceed the price paid by Customer for the Software that gave rise to the claim or if the Software is embedded in another Juniper product the price paid by Customer for such other product Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set forth herein that the same reflect an allocation of risk between the Parties including the risk that a contract remedy may fail of its essential purp
78. S1 router CS1 has the following protection group properties e RPL owner ring 1 e East interface ge 3 2 4 0 e West interface ge 5 2 3 0 Data channel for ring 1 VLAN 200 VLAN 300 Data channel for ring 2 VLAN 500 VLAN 600 e Ring protection link end for ring 1 ge 3 2 4 0 CS1 has the following routing and bridging properties e Routing instance vs e Bridge domains e bdl100 is associated with vlan id 100 e bd101 is associated with vlan id 101 e bd200 is associated with vlan id 200 e bd300 is associated with vlan id 300 e bd500 is associated with vlan id 500 e bd600 is associated with vlan id 600 CS2 router CS2 has the following protection group properties e RPLowner ring 2 e East interface ge 2 0 4 0 e West interface ge 2 0 8 0 e Ring protection link end for ring 2 ge 2 0 8 0 e Data channel for ring I VLAN 200 VLAN 300 Data channel for ring 2 VLAN 500 VLAN 600 CS2 has the following bridging properties e bdi00is associated with vlan id 100 e bd101 is associated with vlan id 101 e bd200 is associated with vlan id 200 e bd300 is associated with vlan id 300 e bd500 is associated with vlan id 500 e bd600 is associated with vlan id 600 156 Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection Table 5 Components of the Network Topology continued Property Settings ASI router ASI has the following protection group properties
79. Series router and PE2 the MX series router routers is not symmetrical as is shown in Figure 11 on page 78 Figure 11 ATM Ethernet VLAN Interworking Packet Structure 1 PE1 gt PE2 Ls Ethertype SA DA Inner VLAN MPLS Ethernet 8 bytes is an ATM cookie added by an M Series ATM pic The first 2 bytes of this ATM cookie is inner VLAN 2 PE2 gt PE1 g017429 Ls Ethertype SA DA Inner VLAN MPLS Ethernet For PE to PE2 traffic the 8 bytes following the MPLS header is an ATM cookie added by the M Series ATM PIC The first two bytes are the inner VLAN tag which is why the field extends to the right of the figure The traffic between PE2 and CE2 is a normal flow of stacked Ethernet frames You can also configure a CCC with remote interface switch or Layer 2 circuit over Aggregated Ethernet on the MX Series router PE2 When CCC is configured for Aggregated Ethernet the flow of packets is as shown in Figure 12 on page 78 Figure 12 CCC to Stacked VLAN Translation 1 CCC to stacked vlan rm Ethertype SA DA Inner VLAN MPLS Ethernet L3 Ethertype Man Ovlan SA DA 2 Stacked vlan to CCC L3 Ethertype Man Ovlan SA DA rm Ethertype SA DA Inner VLAN MPLS Ethernet g017430 MX Series Ethernet Services Routers Solutions Page Configuring MX Series Router ATM Ethernet Interworking on page 79 Copyright
80. Tagging on page 45 Example Configuring One VPLS Instance for Several VLANs This topic provides a configuration example to help you effectively configure a network of Juniper Networks MX Series Ethernet Services 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 For more information about configuring Ethernet pseudowires as part of VPLS see the Junos OS Feature Guide O NOTE This topic does not present exhaustive configuration listings for all routers in the figures However you can use it with a broader configuration strategy to complete the MX Series router network configurations Consider the VPLS network shown in Figure 9 on page 56 Copyright 2010 Juniper Networks Inc 55 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Figure 9 Many VLANS on One VPLS Instance DA PO PseudoWire for VLAN All SA L2PE1 L2 PE2 Site 2 0x8100 VLAN AN On PseudoWire for VLAN 1500 VLAN 500 Transport LABEL VPLS LABEL DA SA 0x8100 VLAN 1 1000 Ethertype 0x8100 SIP ge 3 0 0 1 ge 2 0 0 1 wee N ge 1 0 0 1 ge 1 0 0 11 ge 6 0 0 11 VLAN All VLAN All PS EET L2 PE3 ge 5 0 0 11 Site 3 L2
81. X Series router with the show connections command user PE2 gt show connections CCC and TCC connections Link Monitoring On Legend for status St UN uninitialized NP not present WE wrong encapsulation DS disabled Dn down gt only outbound conn is up lt only inbound conn is up Up operational RmtDn remote CCC down Restart restarting Connection Circuit trans rws1 1 ae0 0 1sp2 1 1sp1 2 Legend for connection types if sw interface switching rmt if remote interface switching 1sp sw LSP switching tx p2mp sw transmit P2MP switching rx p2mp sw receive P2MP switching Legend for circuit types intf interface tlsp transmit LSP rlsp receive LSP Type St Time last up Up rmt if RmtDn May 12 15 34 46 intf Up tlsp Up rlsp Up Related MX Series Ethernet Services Routers Solutions Page Documentation MX Series Router ATM Ethernet Interworking Function on page 77 Copyright 2010 Juniper Networks Inc 91 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 92 Copyright 2010 Juniper Networks Inc PART 3 Ethernet Filtering Monitoring and Fault Management Solutions for MX Series Routers Layer 2 Firewall Filters on page 95 IEEE 802 1ag OAM Connectivity Fault Management on page 103 ITU T Y 1731 Ethernet Frame Delay Measurements on page 119 IEEE 802 3ah OAM Link Fault Management on page 137 Ethernet Ring Protectio
82. agreement objective parameters which can include bandwidth and reliability In many cases a service provider could be subject to penalties imposed by regulation statute or contract if network performance is not within the bounds established for the service One key performance objective is delay along with its close relative delay variation often called jitter Some applications will function just as well with high delays across the network and high delay variations such as bulk file transfer while other applications such as voice can only function with low and stable delays Many networks invoke protocols or features available at Layer 3 the packet layer or higher to measure network delays and jitter link by link However when the network consists of many Ethernet links there is little available at Layer 2 the frame layer that allows routers to measure frame delay and jitter This is where the ability to configure and monitor Ethernet frame delay is helpful On a Juniper Networks MX Series Ethernet Services Router equipped with the Distributed Port Concentrator MX DPC only you can perform Ethernet frame delay measurements referred to as ETH DM in Ethernet specifications This feature allows you to configure on demand Operation Administration and Maintenance OAM statements for the measurement of frame delay and frame delay variation jitter You can configure Ethernet frame delay measurement in either one way or two way round t
83. al address 10 0 2 51 priority 254 unit 2 family inet address 10 0 3 2 24 unit 3 f family inet address 10 0 3 3 24 36 Copyright 2010 Juniper Networks Inc unit 4 family inet address 10 0 3 4 24 unit 5 family inet address 10 0 3 5 24 1 unit 6 family inet address 10 0 3 6 24 1 unit 71 family inet address 10 0 3 7 24 unit 8 family inet address 10 0 3 8 24 bridge domains Copyright 2010 Juniper Networks Inc vlan 100 domain type bridge vlan id 100 interface ge 2 2 2 100 interface ae2 100 interface ae3 100 routing interface irb O vlan 200 1 domain type bridge vlan id 200 interface ge 3 3 3 200 interface ae2 200 interface ae3 200 routing interface irb l vlan201 vlan id 201 routing interface irb 2 vlan202 1 vlan id 202 routing interface irb 3 vlan203 vlan id 203 routing interface irb 4 Chapter 2 Basic Layer 2 Features on MX Series Routers 37 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide vlan204 vlan id 204 routing interface irb 5 vlan205 vlan id 205 routing interface irb 6 Related MX Series Ethernet Services Routers Solutions Page Documentation Layer 2 Features for a Bridging Environment on page 21 Example Roadmap Configuring a Basic Bridge Domain Environment on page 22 Example Step Configuring Interfaces
84. al switch end of routing instances 50 Copyright 2010 Juniper Networks Inc Chapter 4 VLANS Within Bridge Domain and VPLS Environments Bridge domain cl vlan 100 for customer cl virtual switch has five logical interfaces Logical interface ge 1 0 0 1 configured on physical port ge 1 0 0 Logical interface ge 2 0 0 1 configured on physical port ge 2 0 0 Logical interface ge 3 0 0 1 configured on physical port ge 3 0 0 Logical interface ge 4 0 0 1 can exist on an extended port subinterface defined by the pair ge 4 0 0 and outer vlan tag 500 Logical interface ge 5 0 0 1 can exist on an extended port subinterface defined by the pair ge 5 0 0 and 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 vlan id 100 configuration within the bridge domain cl vlan 100 sets the normalized VLAN value to 100 The following happens as a result of this configuration Packets received on logical interfaces ge 1 0 0 1 or ge 2 0 0 1 with a single VLAN tag of 100 in the frame are accepted Packets received on logical interface ge 3 0 0 1 with a single VLAN tag of 200 in the frame are accepted and have their tag values translated to the normalized VLAN tag value of 100 Packets received on logical interfaces ge 4 0 0 1 and ge 5 0 0 1 with outer
85. alized VLAN Use either the vlan id vlan number statement to tag all packets with one normalized VLAN tag or the vlan tags outer outer vlan number inner inner vlan number statement to tag all packets with the normalized outer and inner VLAN tags if you want to tag packets sent onto the VPLS pseudowires Use the vlan id none statement to remove the incoming VLAN tags identifying a Layer 2 logical interface when packets are sent over VPLS pseudowires This statement is also used to configure shared VLAN learning NOTE The outgoing packets can still contain customer VLAN tags If integrated routing and bridging IRB is configured for a bridge domain or a VPLS routing instance then you must configure a normalized VLAN using one of the following statements vlan id vlan number vlan id none Copyright 2010 Juniper Networks Inc Chapter 4 VLANS Within Bridge Domain and VPLS Environments vlan tags outer outer vlan number inner inner vlan number Use the vlan id all statement to configure bridging for several VLANS with minimal amount of configuration and switch resources For an example of this configuration see Example Configuring One VPLS Instance for Several VLANS on page 55 Related MX Series Ethernet Services Routers Solutions Page Documentation VLANs Within a Bridge Domain or VPLS Instance on page 43 Packet Flow Through a Bridged Network with Normalized VLANs on page 44 Example Configuri
86. and VLAN Tags on page 24 Example Step Configuring Bridge Domains on page 30 Example Step Configuring Spanning Tree Protocols on page 32 38 Copyright 2010 Juniper Networks Inc CHAPTER 3 Virtual Switches Layer 2 Features for a Switching Environment on page 39 Configuring Virtual Switches as Separate Routing Instances on page 40 Layer 2 Features for a Switching Environment Juniper Networks MX Series Ethernet Services Routers include all standard Ethernet capabilities as well as enhanced mechanisms for service providers to provision and support large numbers of Ethernet services in addition to all Layer 3 services The MX Series routers include several features to contain and control the Ethernet environment One of these features is the virtual switch MX Series routers allow the collapsing of multiple diverse switch networks to a single platform by running virtual instances of as many Spanning Tree Protocols STPs as needed to support all broadcast domains This is important because there are many incompatible versions of STP and without a way to run multiple virtual instances a separate switch would be needed to support each one With MX Series virtual switch configuration you can continue to running existing STP protocols with the option to migrate to a common STP protocol if desired Virtual switches also make it easy to separate independent switched Ethernet networks each possibly carrying several VLANs Becaus
87. are nested bridges ona provider backbone will normally only switch on the outer VLAN tag Allin all the inner 12 bit tagging space is more than adequate for a Metro Ethernet network Any limitations in the VLAN tag space can be addressed by adding more VLAN tags to the basic Ethernet frame Related MX Series Ethernet Services Routers Solutions Page D tati OCUMENTaHON Ethernet Terms and Acronyms on page 3 Copyright 2010 Juniper Networks Inc 13 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 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 Benefits of Ethernet Frames on page 9 Networking at Layer 2 Challenges of Ethernet MAC Addresses on page 10 Networking at Layer 2 Forwarding VLAN Tagged Frames on page 11 Networking at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15 Layer 2 Networking Standards on page 17 Networking at Layer 2 Logical Interface Types Related Documentation Two main types of interfaces are used in Layer 2 configurations Layer 2 logical interface This type of interface uses the VLAN ID as a virtual circuit identifier and the scope of the VLAN ID is local to the interface port This type of interface is often used in service provider centric applications Access or trunk interface This type of interface uses a VLAN ID with global signif
88. ation see the product documentation page on the Juniper Networks website at http www juniper net techpubs Juniper Networks supports a technical book program to publish books by Juniper Networks engineers and subject matter experts with book publishers around the world These books go beyond the technical documentation to explore the nuances of network architecture deployment and administration using the Junos operating system Junos OS and Juniper Networks devices In addition the Juniper Networks Technical Library published in conjunction with O Reilly Media explores improving network security reliability and availability Using Junos OS configuration techniques All the books are for sale at technical bookstores and book outlets around the world The current list can be viewed at http www juniper net books Copyright 2010 Juniper Networks Inc xvii Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Objectives Audience xviii This guide provides an overview of the Layer 2 features of the Junos OS and describes how to configure the features to provide solutions to several network scenarios D NOTE For additional information about Junos OS either corrections to or information that might have been omitted from this guide see the software release notes at http www juniper net This guide is designed for network administrators who are configuring and monitoring Layer 2 features of the Junos OS To
89. austive configuration listings for all routers in the figures However you can use it with a broader configuration strategy to complete the MX Series router network configurations Consider the VPLS network shown in Figure 8 on page 52 Figure 8 VLAN Tags and VPLS Labels DA PO PseudoWire for VLAN SA L2PE1 0x8100 VLAN 500 Transport LABEL L2 PE2 Site 2 VPLS LABEL DA SA 0x8100 VLAN 100 Ethertype 0x8100 SIP sesse sees PseudoWire for VLAN None ge 3 0 0 1 PE ee ge 2 0 0 1 gt _ l AD AL ge 4 0 0 1 ge 1 0 0 1 L2 PE1 ge 1 0 0 11 Site 1 L2 PE3 ge 6 0 0 11 z a Site 3 ge 5 0 0 11 ID QT DA P1 SA L2PE1 0x8100 VLAN 500 Transport LABEL VPLS LABEL DA SA L2 PE4 Ethertype 0x800 Site 4 SIP g0162827 The Layer 2 PE routers are MX Series routers Each site is connected to two P routers for redundancy although both links are only shown for L2 PE1 at Site 1 Site 1is connected 52 Copyright 2010 Juniper Networks Inc Chapter 4 VLANS Within Bridge Domain and VPLS Environments to PO and PI Site 2 is connected to PO and P2 not shown Site 3 is connected to P2 and P3 and Site 4 is connected to P1 and P3 VPLS pseudowires configured on the PE and P routers carry traffic b
90. be used as the basis for a truly global network Ethernet MAC addresses come from the IEEE and IP subnet addresses come from various Internet authorities IP also employs a naming convention absent in Ethernet but we ll ignore that in this discussion The key differences in how these addresses are assigned make all the difference when it comes to the basic functions of a bridge as opposed to a router Copyright 2010 Juniper Networks Inc 7 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide D NOTE The opposite of a globally unique network address is the locally significant connection identifier which connects two endpoints on a network For example MPLS labels such as 1000001 can repeat in a network but a public IP address can appear on the Internet in only one place at a time otherwise it is an error All devices on LANs that are attached to the Internet have both MAC layer and IP addresses Frames and packets contain both source and destination addresses in their headers In general MAC addresses are 48 bits long The first 24 bits are assigned by the IEEE and form the organizationally unique identifier OUI of the manufacturer or vendor requesting the address The last 24 bits form the serial number of the LAN interface cards and their uniqueness must be enforced by the company some companies reuse numbers of bad or returned cards while others do not Pv4 addresses are 32 bits long A variable nu
91. ce Switch on the MX Series Router edit interfaces ge 0 2 0 1 vlan vci tagging encapsulation vlan vci ccc unit O vlan id 100 inner vlan id range start 32 end 63 86 Copyright 2010 Juniper Networks Inc Chapter 8 MX Series Router in an ATM Ethernet Interworking Function ge 0 2 8 unit O family inet address 20 1 1 10 24 family iso family mpls protocols rsvp interface ge 0 2 8 0 mpls label switched path lsp2 1 from 10 255 171 14 to 10 255 171 45 label switched path lspl 2 from 10 255 171 45 to 10 255 171 14 interface ge 0 2 8 0 isis interface ge 0 2 8 0 connections remote interface switchrwsl f interface ge 0 2 0 0 transmit lsp lsp2 1 receive lsp lspl 2 CE2 Configuation Configure Dual Tagged Ethernet Interface edit interfaces ge 0 0 0 1 flexible vlan tagging encapsulation flexible ethernet services unit O vlan tags outer 100 inner 34 family inet address 30 1 1 10 24 You verify your configuration on the MX Series router with the show connections command Copyright 2010 Juniper Networks Inc Junos 10 4 MX Series Ethernet Services Routers Solutions Guide user PE2 gt show connections CCC and TCC connections Link Monitoring On Legend for status St Legend for connection types UN uninitialized if sw interface switching NP not present rmt if remote interface switching WE wrong enca
92. check the connectivity among its provider edge PE routers By the customer to check the connectivity among its customer edge CE routers NOTE The configured customer CFM level must be greater than service provider CFM level In many Metro Ethernet networks CFM is used to monitor connectivity over a VPLS and bridge network Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Operations Administration and Maintenance on page 103 Example Configuring Ethernet CFM over VPLS on page 105 Example Configuring Ethernet CFM on Bridge Connections on page 112 Example Configuring Ethernet CFM on Physical Interfaces on page 116 Example Configuring Ethernet CFM over VPLS In this example both the customer and service provider are running Ethernet CFM over a VPLS and a multiprotocol label switching MPLS network The network is shown in Figure 15 on page 106 The customer has configured Ethernet CFM on MX Series routers L2 CE1 and L2 CE2 The service provider has configured Ethernet CFM on MX Series routers PE P and PE2 D NOTE The configurations in this example are only partial examples of complete and functional router configurations Do not copy these configurations and use them directly on an actual system The service provider is using CFM level 5 and the customer is using CFM level 7 The boundaries are marked with up mep and down mep CFM terminology in the figure Copyrig
93. chpubs Find solutions and answer questions using our Knowledge Base http kb juniper net Download the latest versions of software and review release notes http www juniper net customers csc software Search technical bulletins for relevant hardware and software notifications https www juniper net alerts Join and participate in the Juniper Networks Community Forum http www juniper net company communities Open a case online in the CSC Case Management tool http www juniper net cm To verify service entitlement by product serial number use our Serial Number Entitlement SNE Tool https tools juniper net SerialNumberEntitlementSearch Opening a Case with JTAC You can open a case with JTAC on the Web or by telephone Use the Case Management tool in the CSC at http www juniper net cm Call 1 888 314 JTAC 1 888 314 5822 toll free in the USA Canada and Mexico For international or direct dial options in countries without toll free numbers visit us at http www juniper net support requesting support html Copyright 2010 Juniper Networks Inc xxiii Junos 10 4 MX Series Ethernet Services Routers Solutions Guide xxiv Copyright 2010 Juniper Networks Inc PART 1 Overview Overview of Ethernet Solutions on page 3 Copyright 2010 Juniper Networks Inc Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 2 Copyright 2010 Juniper Networks Inc CHAPTER 1 Ov
94. complete router configuration With this configuration broadcast packets inside frames arriving with VLAN identifier 10 on ge 0 0 1 are normalized to a dual tagged frame with an outer VLAN value of 200 and an inner VLAN value of 100 The broadcast packet and frames egressing ge 0 0 2 or ge 0 0 3 have the outer VLAN value stripped and the inner VLAN value swapped to 20 and 30 respectively according to the interface configuration However this stripping of the outer VLAN tag and the swapping is extra work because the frames will still egress the VPLS pseudowire in routing instance green with an outer VLAN tag value of 200 and an inner VLAN tag value of 100 also according to the configuration The same configuration can be accomplished more effectively using dynamic profiles VPLS Pseudowire Interfaces and Dynamic Profiles Consider the following configuration which uses dynamic profiles to manipulate VLAN identifiers edit routing instances green instance type vpls interface ge 0 0 1 1 interface ge 0 0 21 interface ge 0 0 3 1 vlan id 100 Desired inner VLAN tag on the VPLS pseudowire protocols vpls vpls id 10 neighbor 10 1 1 20 associate profile green_vpls_pw_1 The profile more edit interfaces ge 0 0 1 unit O vlan id 10 ge 0 0 2 unit O vlan id 20 Copyright 2010 Juniper Networks Inc 65 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide ge 0 0 3 1
95. d Interfaces on page 134 Example Configuring Two Way Ethernet Frame Delay Measurements with Single Tagged Interfaces 130 This example uses two MX routers MX 1 and MX 2 The configuration creates a CFM down MEP session on a VLAN tagged logical interface connecting the two ge 5 2 9 on Router MX 1 and ge 0 2 5 on Router MX 2 Configuration on Router MX 1 edit interfaces ge 5 2 9 1 vlan tagging unit O vlan id 512 Copyright 2010 Juniper Networks Inc Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements protocols oam ethernet connectivity fault management traceoptions file eoam_cfm log size 1g files 2 world readable flag all linktrace path database size 255 age 10s maintenance domain md6 level 6 maintenance association ma6 continuity check interval 100ms hold interval 1 mep 2011 interface ge 5 2 9 0 direction down auto discovery Configuration on Router MX 2 edit interfaces ge 0 2 5 1 vlan tagging unit O vlan id 512 protocols oam ethernet connectivity fault management traceoptions file eoam_cfm log size 1g files 2 world readable flag all linktrace path database size 255 age 10s Copyright 2010 Juniper Networks Inc 131 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 132 maintenance domain md6 level 6 maintenance association ma6 continuity check interval
96. d interval 1 mep 2011 interface ge 5 0 0 direction down auto discovery Untagged interface configuration for Router MX 2 edit interfaces ge O 2 21 Unit O ge 0 2 5 1 unit O protocols oam ethernet Copyright 2010 Juniper Networks Inc 135 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide connectivity fault management traceoptions file eoam cfm log size lg files 2 world readable flag all linktrace path database size 255 age 10s maintenance domain md6 level 6 maintenance association ma6 continuity check interval 100ms hold interval 1 mep 101 interface ge 0 2 2 direction down auto discovery Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Frame Delay Measurements on page 119 Configuring MEP Interfaces to Support ETH DM on page 122 Triggering an ETH DM Session on page 123 e Viewing ETH DM Statistics on page 124 Configuring One Way ETH DM with Single Tagged Interfaces on page 125 Configuring Two Way ETH DM with Single Tagged Interfaces on page 130 136 Copyright 2010 Juniper Networks Inc CHAPTER 12 IEEE 802 3ah OAM Link Fault Management Ethernet OAM Link Fault Management on page 137 Example Configuring Ethernet LFM Between PE and CE on page 138 Example Configuring Ethernet LFM for CCC on page 139 Example Configuring Ethernet LFM for Aggregated Ethernet on page 140 Examp
97. d on logical interfaces ge 1 0 0 1 or ge 2 0 0 1 or ge 3 0 0 1 with a single VLAN tag in the range from 1 through 1000 in the frame are accepted Unknown source MAC addresses and unknown destination MAC addresses are learned based on their normalized VLAN values of 1 through 1000 All packets sent on the VPLS pseudowire have a normalized VLAN tag after the source MAC address field in the encapsulated Ethernet packet Although there are only three logical interfaces in the VPLS instance called customer cl v1 to v1000 the same MAC address for example M1 can be learned on different logical interfaces for different VLANs For example MAC address M1 could be learned on logical interface ge 1 0 0 1 for VLAN 500 and also on logical interface ge 2 0 0 1 for VLAN 600 MX Series Ethernet Services Routers Solutions Page VLANs Within a Bridge Domain or VPLS Instance on page 43 Packet Flow Through a Bridged Network with Normalized VLANs on page 44 Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces on page 47 Copyright 2010 Juniper Networks Inc CHAPTER 5 Bulk Administration of Layer 2 Features on MX Series Routers Bulk Configuration of VLANS and Bridge Domains on page 59 Example Configuring VLAN Translation with a VLAN ID List on page 59 Example Configuring Multiple Bridge Domains with a VLAN ID List on page 60 Bulk Configuration of VLANS and Bridge Domains Related Documentation In s
98. d300 vlan id 300 set bd500 vlan id 500 set bd600 vlan id 600 Results Check the results of the configuration user cs2 gt show configuration interfaces ge 2 0 4 1 unit O family bridge Copyright 2010 Juniper Networks Inc 161 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide interface mode trunk vlan id list 100 1000 ge 2 0 8 unit O family bridge interface mode trunk vlan id list 100 1000 protocols protection group ethernet ring ring 1 east interface control channel ge 2 0 4 0 vlan 100 west interface control channel ge 2 0 8 0 vlan 100 data channel vlan 200 300 ethernet ring ring 2 east interface control channel ge 2 0 4 0 vlan 101 west interface control channel ge 2 0 8 0 vlan 101 ring protcection link end data channel vlan 500 500 bridge domains bd100 vlan id 100 162 Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection bd101 vlan id 101 bd200 vlan id 200 bd300 vlan id 300 bd500 vlan id 500 bd600 vlan id 600 Configuring ERP on AS1 CLI Quick To quickly configure AS for ERP copy the following commands and paste them into the Configuration switch terminal window of ASI edit set interfaces ge 2 0 5 unit O family bridge interface mode trunk set interface
99. 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 El edit interfaces ge 5 2 3 vlan tagging unit O vlan id 2000 edit protocols oam ethernet connectivity fault management maintenance domain customer level 7 maintenance association customer sitel continuity check interval 1s mep 800 interface ge 5 2 3 0 direction down auto discovery CFMonL2 CE2 Hereis the configuration of CFM L2 CE2 edit interfaces ge 0 2 9 1 vlan tagging unit O vlan id 2000 edit protocols oam ethernet connectivity fault management maintenance domain customer level 7 maintenance association customer sitel continuity check Copyright 2010 Juniper Networks Inc TM Junos 10 4 MX Series Ethernet Services Routers Solutions Guide interval Is mep 700 interface ge 0 2 9 0 direction down auto discovery Related MX Series Ethernet Services Routers Solutions Page D tati OSUMEMEANON Ethernet Operations Administration and Maintenance on page 103 Ethernet OAM Connectivity Fault Management on page 104 Example Configuring Ethernet CFM on Bridge Connections on page 112 Example Configuring Ethernet CFM on Physical Interfaces on page 116 Example Configuring Ethernet CFM on Bridge Connections In this example both the customer and service provider are running Ethernet CFM over a simple bridge ne
100. domains vlanlOO domain type bridge vlan id 100 interface ge 2 2 2 100 interface ael 100 interface ae3 100 vlan200 1 30 Copyright 2010 Juniper Networks Inc Related Documentation Chapter 2 Basic Layer 2 Features on MX Series Routers domain type bridge vlan id 200 interface ge 3 3 3 200 interface ael 200 interface ae3 200 3 Configure a bridge domain on Router 3 edit bridge domains vlanlOO domain type bridge vlan id 100 interface ge 2 2 2 100 interface ae3 100 vlan200 1 domain type bridge vlan id 200 interface ge 3 3 3 200 interface ae3 200 vlan201 domain type bridge vlan id 201 vlan202 domain type bridge vlan id 202 vlan203 1 domain type bridge vlan id 203 vlan204 domain type bridge vlan id 204 vlan205 1 domain type bridge vlan id 205 MX Series Ethernet Services Routers Solutions Page Layer 2 Features for a Bridging Environment on page 21 Example Roadmap Configuring a Basic Bridge Domain Environment on page 22 Example Step Configuring Interfaces and VLAN Tags on page 24 Example Step Configuring Spanning Tree Protocols on page 32 Example Step Configuring Integrated Bridging and Routing on page 34 Copyright 2010 Juniper Networks Inc 31 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Example Step Configuring Spanning Tree Protocols Configure the Spanning Tree Protocol on all three routers
101. e 76 Documentation interface ge 2 2 4 0 interface ge 2 2 6 0 You verify your configuration by using two related commands show dhcp relay binding routing instance vs bridge domains bd show dhcp relay binding routing instance vs1 bridge domains bd detail user routerl 2 clients 2 IP address 192 168 1 1 192 168 1 2 user router1 gt 2 clients 2 show dhcp relay binding routing instance vs1 bridge domains bd1 bound 0 slecting 0 renewing O rebinding Hardware address Type Lease expires at 00 00 00 42 a8 e3 active 2008 12 12 15 56 04 PST 00 00 00 42 a8 e4 active 2008 12 12 15 56 10 PST show dhcp relay binding routing instance vs1 bridge domains bdi detail bound 0 slecting 0 renewing O rebinding Clients bindings information IP address 192 168 1 1 Hardware address 00 00 00 42 a8 e3 Type active Lease expires at 2008 12 12 15 56 04 PST State bound interface ge 2 2 6 0 IP address 192 168 1 2 Hardware address 00 00 00 42 a8 e4 Type active Lease expires at 2008 12 12 15 56 10 PST State bound interface ge 2 2 4 0 MX Series Ethernet Services Routers Solutions Page MX Series Router as a Layer 2 DHCP Relay Agent on page 73 Example Configuring DHCP Relay in a Bridge Domain VLAN Environment on page 74 Copyright 2010 Juniper Networks Inc CHAPTER 8 MX Series Router in an ATM Ethernet Interworking Function MX Series Router ATM Ethernet Interworking Function on
102. e Viewing Ethernet Ring Protection Status Ring Failure Condition on page 172 Ethernet Ring Protection Link failure is often an unavoidable part of networking However there are methods of improving the reliability of a router or bridge network even when link failures occur For example SONET SDH seal healing rings are frequently used to add a level of robustness to router networks This ring protection switching is now extended to Ethernet links You can configure Ethernet ring protection for a series of two or more systems so that if one link fails traffic is rerouted around the failure on the ring The basic idea of Ethernet ring protection is to use one specific link to protect the whole ring This special link is the ring protection link RPL When all links are Up and running the RPL blocks traffic and remains idle The RPL itself is controlled by the designated RPL owner node There is only one RPL owner node on the ring and the RPL owner node is responsible for blocking the RPL interface under normal operating conditions However if a link failure occurs on the ring the RPL owner node is responsible for unblocking the RPL interface and protection switching the traffic on the alternate path around the ring An Ethernet ring automatic protection switching R APS messaging protocol coordinates the protection activities of all nodes on the ring The APS blocks traffic over the failed link and unblocks traffic over the RPL When the fa
103. e 142 Example Configuring Ethernet LFM for CCC In this example LFM is configured between two PEs PE1 and PE2 connected using CCC With LFM in place a link fault will be detected immediately instead of depending on routing protocols to find the fault on end to end CCC connection This also helps in detecting the exact failed link instead of only finding that the end to end CCC connectivity has failed Also because LFM runs at the link layer level it does not need a IP address to operate and so can be used where bidirectional fault detection BFD cannot The links running LFM are shown in Figure 20 on page 139 Figure 20 Ethernet LFM for CCC ge 1 1 0 ge 1 0 0 al L am CCC LFM l I I I I I i lt gt 016839 To configure Ethernet LFM between two PEs connected using CCC 1 Configure LFM on the PE router with CCC edit interfaces ge 1 1 0 encapsulation ethernet ccc unit O protocols oam ethernet link fault management interface ge 1 1 0 pdu interval 1000 Copyright 2010 Juniper Networks Inc 139 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide pdu threshold 5 2 Configure LFM on the PE2 router with CCC edit interfaces ge 1 0 0 1 encapsulation ethernet ccc unit O protocols oam ethernet link fault management interface ge 1 0 0 pdu interval 1000 pdu threshold 5 Related MX Series Ethernet Services Routers Solutions Pa
104. e is ge 1 0 2 1 the RPL and the west control channel interface is ge 1 2 1 1 The protection group is pg102 Router 3 s east control channel interface is ge 1 0 3 1 the RPL and the west control channel interface is ge 1 0 4 1 The protection group is pg103 D NOTE Although not strictly required for physical ring protection this example configures Ethernet OAM with MEPs Router 1 RPL Owner Configuration To configure Router 1 the RPL owne r 1 Configure the interfaces edit interfaces ge 1 0 1 vlan tagging encapsulation flexible ethernet services unit 1 encapsulation vlan bridge vlan id 100 ge 1 2 4 1 vlan tagging encapsulation flexible ethernet services unit 1 encapsulation vlan bridge vlan id 100 2 Configure the bridge domain edit bridge domains bd1 domain type bridge interface ge 1 2 4 1 interface ge 1 0 1 1 3 Configure the Ethernet ring protection gorup edit protocols protection group ethernet ring pg101 node id 00 01 01 00 00 01 ring protection link owner east interface Copyright 2010 Juniper Networks Inc 149 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide control channel ge 1 0 1 1 ring protection link end west interface control channel ge 1 2 4 1 4 Configure Ethernet OAM edit protocols oam ethernet connectivity fault management action profile rmep defaults d
105. e sent over the VPLS pseudowires 54 Copyright 2010 Juniper Networks Inc Chapter 4 VLANS Within Bridge Domain and VPLS Environments The following happens on the C2 VLAN as a result of the vlan id none configuration AMAC table is created for each instance of vlan id none All MAC addresses learned over the interfaces belonging to this VPLS instance are added to this table The received or configured VLAN tags are not considered when the MAC addresses are added to this table This is a case of shared VLAN learning Packets with a single VLAN tag value of 301 are accepted on interface ge 1 0 0 11 The VLAN tag value 301 is then popped and removed from the frame of this packet 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 this packet All packets sent on pseudowires will not have any VLAN tags used to identify the incoming Layer 2 logical interface ER NOTE The packet can still contain other customer VLAN tags Packets received from pseudowires are looked up in the MAC table associated with the VPLS instance Any customer VLAN tags in the frame are ignored Related MX Series Ethernet Services Routers Solutions Page Documentation 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
106. e the same VLAN ID can be used in multiple switched networks virtual switches can keep each VLAN and broadcast domain logically separated D NOTE In a router environment there is always a default routing instance When you need only one routing instance on the router you use the default routing instance without qualification However if you need more than one routing instance you must configure statements to create additional routing instances In a switching environment the same is true of virtual switches if you need more than one virtual switch in addition to the default you must create them For more information about STPs and virtual switches see the Junos OS Layer 2 Configuration Guide Related MX Series Ethernet Services Routers Solutions Page Documentation Copyright 2010 Juniper Networks Inc 39 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Configuring Virtual Switches as Separate Routing Instances on page 40 Configuring Virtual Switches as Separate Routing Instances You can configure two virtual switches as separate routing instances on an MX Series router with bridge domains and VLANS Before you begin you should have already configured a basic bridge domain environment For a general description of a basic bridge domain environment see Layer 2 Features for a Bridging Environment on page 21 For an example of a basic bridge domain configuration see Example Roadmap Configu
107. ed the measurement between two compatibly configured MX Series routers Enabled the distributed periodic packet management deamon ppmd Avoided trying to perform Ethernet frame delay measurement on aggregated Ethernet or pseudowire interfaces which are not supported Made sure the MX DPCs support hardware assisted timestamping if that feature is configured At the end of this configuration you create two MX Series routers that can perform and display Ethernet frame delay measurements on Ethernet interfaces using optional hardware timestamping By default Ethernet frame delay measurement uses software for timestamping and delay calculations You can optionally use hardware timing to assist in this process and increase the accuracy of the delay measurement results This assistance is available on the reception path To configure hardware assisted timestamping 1 To enable Ethernet frame delay measurement hardware assistance on the reception path include the hardware assisted timestamping statement at the edit protocols oam ethernet connectivity fault management performance monitoring hierarchy level edit protocols oam ethernet connectivity fault management performance monitoring hardware assisted timestamping Enable timestamping in hardware 2 Ethernet frame delay measurement requires that distributed PPMD is enabled Before you can gather statistics for Ethernet frame delay measurement you must make
108. efault action interface down maintenance domain di level O maintenance association 100 meplf interface ge 1 0 1 remote mep 2 action profile rmep defaults maintenance domain d2 level O maintenance association 100 meplf interface ge 1 2 4 remote mep 2 action profile rmep defaults Router 2 Configuration To configure Router 2 1 Configure the interfaces edit interfaces 150 Copyright 2010 Juniper Networks Inc ge 1 0 2 vlan tagging encapsulation flexible ethernet services unit 1 encapsulation vlan bridge vlan id 100 ge V2 11 vlan tagging encapsulation flexible ethernet services unit 1 encapsulation vlan bridge vlan id 100 2 Configure the bridge domain edit bridge domains bdl domain type bridge interface ge 1 2 1 1 interface ge 1 0 21 3 Configure the Ethernet protection group edit protocols protection group ethernet ring pg102 east interface control channel ge 1 0 2 1 west interface control channel ge 1 2 1 1 4 Configure Ethernet OAM edit protocols oam ethernet connectivity fault management action profile rmep defaults default action interface down maintenance domain di Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection 151 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide level O maint
109. elay measurement remote mac address Unicast MAC address Send delay measurement frames to the destination unicast MAC address use the format xx Xxx Xx xx xx xx Multicast MAC addresses are not supported mep identifier 1 8191 The MEP identifier to use for the measurement The discovered MAC address for this MEP identifier is used maintenance domain Existing MD name Specifies an existing maintenance domain MD to use for the name measurement maintenance association Existing MA identifier Specifies an existing maintenance association MA identifier to use for ma id the measurement count count 1 65535 default 10 Optional Specifies the number of Ethernet frame delay frames to send The default is 10 Copyright 2010 Juniper Networks Inc 123 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Table 3 Monitor Ethernet Delay Command Parameters continued Parameter wait time Parameter Range Description 1 255 seconds Optional Specifies the number of seconds to wait between frames The default 1 default is 1 second Related Documentation If you attempt to monitor delays to a nonexistent MAC address you must exit the application manually using C user host gt monitor ethernet delay measurement two way 00 11 22 33 44 55 Two way ETH DM request to 00 11 22 33 44 55 Interface ge 5 2 9 0 AC Delay measurement statistics Packets transmitted 10 Valid packets received 0
110. en_vpls_pw_3 interfaces junos interface ifd name unit junos underlying unit number vlan id 200 This is the outer tag family bridge interface mode trunk inner vlan id list 10 20 40 50 J Removed Accounting VLAN 30 NOTE This is not a complete router configuration IN this case frames arriving on the interfaces are classified according to their bridge domains and switched if necessary to the VPLS pseudowire trunk with an outer VLAN tag of 200 except for Engineering frames Engineering frames VLAN 30 are only switched within the interfaces listed within bridge domain accounting and any statically configured trunk interfaces and are prevented from crossing the VPLS pseudowire due to the absence of VLAN 30 on the trunk Copyright 2010 Juniper Networks Inc 71 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Configuration of Tag Translation Using Dynamic Profiles Consider a final case where the bridge domain VLANS need translation at the VPLS pseudowire trunk interface In this case sales VLAN 10 is mapped to VLAN 110 and engineering VLAN 20 is mapped to VLAN 120 This configuration adds tag translation to the VPLS pseudowire traffic edit routing instances green instance type virtual switch Other routing instance statements protocols vpls site range 10 site sample site 1 site identifier 1 associate profile green_vpls_pw_4 Apply profile here Other r
111. enance association 100 mep2 interface ge 1 2 1 remote mep 1 action profile rmep defaults maintenance domain d3 level O maintenance association 100 meplf interface ge 1 0 2 remote mep 2 action profile rmep defaults Router 3 Configuration To configure Router 3 1 Configure the interfaces edit interfaces ge 1 0 4 vlan tagging encapsulation flexible ethernet services unit 1 encapsulation vlan bridge vlan id 100 ge 1 0 3 1 vlan tagging encapsulation flexible ethernet services unit 1 encapsulation vlan bridge vlan id 100 2 Configure the bridge domain edit bridge domains bdl 152 Copyright 2010 Juniper Networks Inc domain type bridge interface ge 1 0 4 1 interface ge 1 0 3 1 3 Configure the Ethernet protection group edit protocols protection group ethernet ring pg103 east interface control channel ge 1 0 3 1 west interface control channel ge 1 0 4 1 4 Configure Ethernet OAM edit protocols oam ethernet connectivity fault management action profile rmep defaults default action interface down maintenance domain d2 level O maintenance association 100 mep2 interface ge 1 0 4 remote mep 1 action profile rmep defaults maintenance domain d3 level O maintenance association 100 mep2 interface ge 1 0 3 remote mep 1 action profile rmep
112. encapsulation extended vlan bridge vlan tagging unit 100 Copyright 2010 Juniper Networks Inc 27 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide vlan id 100 unit 200 1 vlan id 200 3 Configure the Ethernet interfaces and VLAN tags on Router 3 edit chassis aggregated devices ethernet device count 2 Number of AE interfaces on router interfaces ge 2 2 2 1 encapsulation flexible etherent services vlan tagging Customer interface uses singly tagged frames unit 100 encapsulation vlan bridge vlan id 100 interfaces ge 2 2 4 1 unit O family bridge interface mode trunk vlan id list 200 205 This trunk port is part of VLAN range 200 205 interfaces ge 2 2 6 1 unit O family bridge interface mode acess vlan id 200 interfaces ge 3 3 3 1 encapsulation flexible ethernet services vlan tagging Customer interface uses singly tagged frames unit 200 encapsulation vlan bridge vlan id 200 interfaces ge 11 1 0 gigether options 802 3ad ae3 interfaces ge 11 1 1 gigether options 28 Copyright 2010 Juniper Networks Inc Related Documentation Copyright 2010 Chapter 2 Basic Layer 2 Features on MX Series Routers 802 3ad ae3 interfaces ge 11 1 2 1 gigether options 802 3ad ae3 interfaces ge 11 1 3 1 gigether options 802 3ad ae2 interfaces ge 11 1 4 gigether o
113. encapsulation vlan bridge vlan id 200 interfaces ael encapsulation extended vlan bridge vlan tagging unit 100 vlan id 100 unit 200 vlan id 200 interfaces ae2 unit O family bridge interface mode trunk vlan id list 100 200 205 2 Configure the Ethernet interfaces and VLAN tags on Router 2 edit chassis aggregated devices ethernet device count 2 Number of AE interfaces on the router interfaces ge 2 2 2 1 encapsulation flexible ethernet services vlan tagging Customer interface uses singly tagged frames unit 100 26 Copyright 2010 Juniper Networks Inc Chapter 2 Basic Layer 2 Features on MX Series Routers encapsulation vlan bridge vlan id 100 interfaces ge 3 3 3 1 encapsulation flexible ethernet services vlan tagging Customer interface uses singly tagged frames unit 200 1 encapsulation vlan bridge vlan id 200 interfaces ge 5 1 0 1 gigether options 802 3ad ae3 interfaces ge 5 1 1 1 gigether options 802 3ad ae3 interfaces ge 5 1 2 1 gigether options 802 3ad ae3 interfaces ge 5 1 3 1 gigether options 802 3ad ael interfaces ge 5 1 4 gigether options 802 3ad ael interfaces ge 5 1 5 gigether options 802 3ad ael interfaces ael encapsulation extended vlan bridge vlan tagging unit 100 vlan id 100 unit 200 vlan id 200 interfaces ae3
114. ened NR event happened NR RB event happened HROOHRRK Note that the R APS messages have recorded the remote failure Router 3 will see almost identical information MX Series Ethernet Services Routers Solutions Page Ethernet Ring Protection on page 145 Example Configuring Ethernet Ring Protection for MX Series Routers on page 148 Example Viewing Ethernet Ring Protection Status Normal Ring Operation on page 171 Copyright 2010 Juniper Networks Inc PART 4 Index Index on page 177 Copyright 2010 Juniper Networks Inc 175 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 176 Copyright 2010 Juniper Networks Inc Index Symbols comments in configuration statements xxii in syntax descriptions ss xxii lt gt IN Syntax descriptions Xxi in configuration statements sesse esse xxii in configuration statements sesse sees xxii pipe in Syntax descriptions ee see esse ee seek xxii A acronyms Sug NE 3 addresses Layer 2 and Layer 3 7 ATM interworking MX Series fOUTEr srenninemneneennnntnennne 77 MX Series router example ee ee ee ee ee ee ee 79 automatic bridge domains ON MX SETE Sasnnn nananana 59 60 B benefits of Ethernet ss 9 braces in configuration statements sees xxii brackets angle in syntax descriptions xxi square in configuration statements xxii bridge domains MX Series EXamMplES nes 59 60 bridges
115. ent 6 Confidentiality The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper As such Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software for Customer s internal business purposes 7 Ownership Juniper and Juniper s licensors respectively retain ownership of all right title and interest including copyright in and to the Software associated documentation and all copies of the Software Nothing in this Agreement constitutes a transfer or conveyance of any right title or interest in the Software or associated documentation or a sale of the Software associated documentation or copies of the Software 8 Warranty Limitation of Liability Disclaimer of Warranty The warranty applicable to the Software shall be as set forth in the warranty statement that accompanies the Software the Warranty Statement Nothing in this Agreement shall give rise to any obligation to support the Software Support services may be purchased separately Any such support shall be governed by a separate written support services agreement TO THE MAXIMUM EXTENT PERMITTED BY LAW JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS LOSS OF DATA OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICE
116. er as1 user as1 user as1 user as1 user as1 user as1 set bd100 vlan id 100 set bd101 vlan id 101 set bd200 vlan id 200 set bd300 vlan id 300 set bd500 vlan id 500 set bd600 vlan id 600 Results Check the results of the configuration user asl gt show configuration interfaces ge 2 0 5 unit O family bridge interface mode trunk vlan id list 100 1000 ge 2 1 1 unit O family bridge interface mode trunk vlan id list 100 1000 protocols protection group ethernet ring ring 1 east interface control channel ge 2 0 5 0 vlan 100 164 Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection f west interface control channel ge 2 1 1 0 vlan 100 data channel 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 2 1 1 0 vlan 101 data channel vlan 500 600 bridge domains bd100 vlan id 100 bd101 vlan id 101 bd200 vlan id 200 bd300 vlan id 300 bd500 1 vlan id 500 bd600 vlan id 600 Copyright 2010 Juniper Networks Inc 165 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Verification 166 Purpose Action Meaning Purpose Action To confirm that the ERP configuration for multiple ring instances is operating p
117. erform these tasks Verifying the Ethernet Protection Ring on CS1 on page 166 Verifying the Data Channel CS1 on page 166 Verifying the VLANs on CS1 on page 167 Verifying the Ethernet Protection Ring on CS2 on page 167 Verifying the Data Channel CS2 on page 168 Verifying the VLANs on CS2 on page 168 Verifying the Ethernet Protection Ring on ASI on page 169 Verifying the Data Channels on AS on page 169 Verifying the VLANs on AS on page 170 Verifying the Ethernet Protection Ring on CS1 Verify that ERP is enabled on CS1 Show the status of the ring automatic protection switching R APS messages to determine if there is a ring failure user cs1 gt show protection group ethernet ring aps Ethernet Ring Name Request state No Flush Ring Protection Originator Remote Node ID Link Blocked ring 1 NR No Yes Yes ring 2 NR No Yes No 13 22 af 31 fc 00 The output displayed shows that protection groups ring 1 and ring 2 have a Request state of NR meaning there is no request for APS on the ring If a Request state of SF is displayed it indicates there is a signal failure on the ring The output also shows that the ring protection link is not blocked The No Flush field displays No indicating that MAC addresses will be flushed when the ring nodes receive this message first time A value of Yes would indicate MAC address flushing is not needed The Originator field for ring 1 dispays yes indicating that this node is an R APS ori
118. erview of Ethernet Solutions Ethernet Terms and Acronyms on page 3 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 Benefits of Ethernet Frames on page 9 Networking at Layer 2 Challenges of Ethernet MAC Addresses on page 10 Networking at Layer 2 Forwarding VLAN Tagged Frames on page 11 Networking at Layer 2 Forwarding Dual Tagged Frames on page 13 Networking at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15 Layer 2 Networking Standards on page 17 Ethernet Terms and Acronyms Networking with a switch over Ethernet on a LAN is different than networking with a router with IP over a wider area Even the words used to talk about Ethernet networking are different from those used in IP routing This topic provides a list of all the terms and acronyms used in the Junos OS Layer 2 Configuration Guide as well terms that apply to a complete network using Ethernet as a carrier technology 802 lad The IEEE specification for O in O encapsulation and bridging of Ethernet frames 802 lah The IEEE specification for media access control MAC tunneling encapsulation and bridging of Ethernet frames across a provided backbone managed bridge 802 3ag The IEEE specification for a wide range of Ethernet Operations Administration and Maintenance OAM features See also OAM CFM and ETH
119. es LFM See also OAM LFM and ETH DM CIST Common and Internal Spanning Tree The single spanning tree calculated by the spanning tree protocol STP and the rapid spanning tree protocol RSTP and the logical continuation of that connectivity through multiple spanning tree MST bridges and regions calculated to ensure that all LANs in the bridged LAN are simply and fully connected See also MSTI ETH DM Ethernet Frame Delay Measurements See also OAM CFM and Y 1731 Ethernet A term loosely applied to a family of LAN standards based on the original proprietary Ethernet from DEC Intel and Xerox DIX Ethernet and the open specifications developed by the IEEE 802 3 committee IEEE 802 3 LANs In practice few LANs comply completely with DIX Ethernet or IEEE 802 3 IRB Integrated bridging and routing IRB provides simultaneous support for Layer 2 bridging and Layer 3 routing within the same bridge domain Packets arriving on an interface of the bridge domain are Layer 2 switched or Layer 3 routed based on the destination MAC address Packets addressed to the router s MAC address are routed to other Layer 3 interfaces SID The 24 bit service instance identifier field carried inside an I TAG The I SID defines the service instance to which the frame is mapped TAG A field defined in the IEEE 802 lah provider MAC encapsulation header that carries the service instance information I SID associated with the frame
120. es ge 1 0 0 flexible ethernet services flexible vlan tagging unit 11 encapsulation vlan vpls vlan id range 1 1000 unit 11 encapsulation vlan vpls vlan id 1500 interfaces ge 2 0 0 1 flexible ethernet services flexible vlan tagging unit 1 encapsulation vlan vpls vlan id range 1 1000 Note the use of the VLAN id range statement interfaces ge 3 0 0 flexible ethernet services flexible vlan tagging unit 1 encapsulation vlan vpls vlan id 1 1000 interfaces ge 6 0 0 1 flexible ethernet services flexible vlan tagging unit 11 encapsulation vlan vpls vlan id 1500 routing instances customer cl vl to vlOOO instance type vpls vlan id all Note the use of the VLAN id all statement interface ge 1 0 0 1 interface ge 2 0 0 1 interface ge 3 0 0 1 Copyright 2010 Juniper Networks Inc 57 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 58 Related Documentation End of customer cl v1 to v1000 customer cl v1500 1 instance type vpls vlan id 1500 interface ge 1 0 0 11 interface ge 6 0 0 11 End of customer cl v1500 End of routing instances Note the use of the vlan id all and vlan id range statements in the VPLS instance called customer cl v1 to v1000 The vlan id all statement implicitly creates multiple learning domains each with its own normalized VLAN The following happens as a result of the vlan id all configuration Packets receive
121. es make their way from a host on one Ethernet switching hub to a host on the other hub The frame can have two VLAN tags inner and outer one tag only the inner or no tags at all The structure of these various Ethernet frames is shown in Figure 4 on page 16 MX Series router MX Series router router Figure 4 VLAN Tags on a Metro Ethernet Network TPI 8100 TPI 88a8 P DA SA Type P DA SA P DA SA P DA SA P DA SA Type Related Documentation Data and padding CRC Type Data and padding CRC 802 1p Q tag VLAN tag 40 VMAN tag 802 1p Q tag VLAN tag 5 TPI 8100 f VLAN tag 40 Data and padding CRC 802 1p Q tag TPI 8100 f VLAN tag 40 Data and padding CRC Data and padding CRC 016817 As the frame flows from a LAN based host on one end of Figure 4 on page 16 to the other the Ethernet frame can have No VLAN tags At locations 1 and 5 the Ethernet frames can be native and have no VLAN tags at all many NIC cards can include configuration of a VLAN identifier but not all One VLAN tag At locations 2 and 4 from the VLAN aware switching hub to the MX Series router the Ethernet frame has one VLAN tag if a VLAN tag is not present on arriving frames a tag is added by the MX Series router Two VLAN tags At location 3 between two provider bridges the MX Series routers exchange frames with two VLAN ta
122. etween the sites The pseudowires for the VPLS instances are shown with distinct dashed and dotted lines The VLANs at each site are e L2 PE1at Site 1 VLAN 100 and VLAN 300 e L2 PE2 at Site 2 VLAN 100 e L2 PE3 at Site 3 VLAN 100 e L2 PE4 at Site 4 VLAN 300 Service provider SP 1 is providing VPLS services for customer Cl and C2 L2 PE1 is configured with a VPLS instance called customer cl vsi The VPLS instance sets up pseudowires to remote Site 2 and Site 3 L2 PE1 is also configured with a VPLS instance called customer c2 vsi The VPLS instance sets up a pseudowire to remote Site 4 The following is the configuration of interfaces virtual switches and bridge domains for MX Series router L2 PE1 edit interfaces ge 1 0 0 encapsulation flexible ethernet services flexible vlan tagging unit 1 encapsulation vlan vpls vlan id 100 unit 11 encapsulation vlan vpls vlan id 301 interfaces ge 2 0 0 encapsulation flexible ethernet services flexible vlan tagging unit 1 encapsulation vlan vpls vlan id 100 interfaces ge 3 0 0 encapsulation flexible ethernet services flexible vlan tagging unit 1 encapsulation vlan vpls vlan id 200 Should be translated to normalized VLAN value interfaces ge 6 0 0 1 encapsulation flexible ethernet services flexible vlan tagging unit 11 Copyright 2010 Juniper Networks Inc 53 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide e
123. example LFM is enabled on an IP link between the provider edge PE and customer edge CE interfaces If the link goes down the fault will be detected by LFM and the interfaces on both sides will be marked Link Layer Down This results in notifications to various subsystems for example routing which will take appropriate action The link running LFM is shown in Figure 19 on page 138 Figure 19 Ethernet LFM Between PE and CE JL JEU ab JL ccc aE ae AF AE 9016838 To configure Ethernet LFM on an IP link between PE and CE interfaces 1 Configure LFM on the PE router edit interfaces ge 1 1 0 unit O family inet address 11 11 11 1 24 protocols oam ethernet link fault management interface ge 1 1 0 pdu interval 1000 pdu threshold 5 2 Configure LFM on the CE router edit interfaces ge 1 1 0 unit OT family inet address 11 11 11 2 24 protocols oam ethernet Copyright 2010 Juniper Networks Inc Related Documentation Chapter 12 IEEE 802 3ah OAM Link Fault Management link fault management interface ge 1 1 0 pdu interval 1000 pdu threshold 5 MX Series Ethernet Services Routers Solutions Page Ethernet OAM Link Fault Management on page 137 Example Configuring Ethernet LFM for CCC on page 139 Example Configuring Ethernet LFM for Aggregated Ethernet on page 140 Example Configuring Ethernet LFM with Loopback Support on pag
124. figuration For output packets if the VLAN tags associated with an egress logical interface do not match the normalized VLAN tags within the packet then appropriate VLAN tag operations such as push push pop pop pop swap Swap swap swap and others are implicitly made to convert the normalized VLAN tags to the VLAN tags for the egress logical interface For more information about these operations see the Junos OS Routing Protocols Configuration Guide Sending Tagged or Untagged Packets over VPLS Virtual Interfaces If the packets sent over the VPLS virtual interfaces vt or lsi interfaces need to be tagged by the normalized VLAN use one of the following configuration statements vlan id vlan number Tags all packets sent over the VPLS virtual interface with the configured vlan number For an example of this configuration see Example Configuring One VPLS Instance for Several VLANs on page 55 vlan tags outer outer vlan number inner inner vlan number Tags all packets sent over the VPLS virtual interfaces with the specified inner and outer VLAN tags If the incoming VLAN tags identifying a Layer 2 logical interface are removed when packets are sent over VPLS virtual interfaces use the vlan id none statement NOTE Even when the vlan id none statement is configured the packets can still contain other customer VLAN tags Configuring a Normalized VLAN 46 The following factors are important when configuring a norm
125. figuration Frames egress the VPLS pseudowire in routing instance green with an outer VLAN tag value of 200 pushed on top of the normalized value MX Series Ethernet Services Routers Solutions Page Dynamic Profiles for VPLS Pseudowires on page 63 Example Configuring VPLS Pseudowires with Dynamic Profiles Complex Solutions on page 68 Example Configuring VPLS Pseudowires with Dynamic Profiles Complex Solutions Dynamic profiles for VPLS pseudowires can be helpful in a variety of VLAN configurations This section explores some of these situations through examples D NOTE These examples are not complete router configurations All of the examples in this section address the same basic topology A routing instance blue uses a trunk bridge to connect different departments in an organization each with their own VLANS at two different sites The organization uses a BGP based VPLS with a virtual switch to accomplish this Configuration of Routing Instance and Interfaces Without Dynamic Profiles on page 68 Configuration of Routing Instance and Interfaces Using Dynamic Profiles on page 69 Configuration of Tag Translation Using Dynamic Profiles on page 72 Configuration of Routing Instance and Interfaces Without Dynamic Profiles 68 The basic configuration of routing instance and interfaces without dynamic profiles follows edit routing instance blye instance type virtual switch route distinguisher 10 1 1 10 1 vrf tar
126. figuring Layer 3 features and protocols as well as comprehensive information about interfaces and system basics please see the other Junos configuration guides Configuring Layer 2 features on an MX Series router can vary from the very simple aggregated Ethernet trunk interfaces spanning trees to the more complex inner and outer VLAN tags broadcast domains to the very complicated integrated bridging and routing Layer 2 filtering This chapter offers a fairly complex configuration for Layer 2 processing in a bridged environment Generally there are four things that you must configure in an Layer 2 environment Interfaces and virtual LAN VLAN tags Layer 2 interfaces are usually various type of Ethernet links with VLAN tags used to connect to customer devices or other bridges or routers Bridge domains Bridge domains limit the scope of media access control MAC learning and thereby the size of the MAC table and also determine where the device should propagate frames sent to broadcast unknown unicast and multicast BUM MAC addresses Copyright 2010 Juniper Networks Inc 21 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation Spanning Tree Protocols xSTP where the x represents the STP type Bridges function by associating a MAC address with an interface similar to the way a router associates an IP network address with a next hop interface Just as routing protocols
127. forwarding packets with no entries in their table In contrast to perform the same role a bridge would need one table entry for every LAN interface on host or bridge in the world This is hard enough to do for Ethernets that span a metropolitan area let alone the entire world NOTE There are other reasons that Ethernet would be hard pressed to become a truly global network including the fact that MAC addresses do not often have names associated with them while IP addresses do for example 192 168 27 48 might be host48 accounting juniper net This section addresses only the address issues 8 Copyright 2010 Juniper Networks Inc Chapter 1 Overview of Ethernet Solutions Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Terms and Acronyms on page 3 Networking and Internetworking with Bridges and Routers on page 6 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 Layer 2 Forwarding VLAN Tagged Frames on page 11 Networking at Layer 2 Forwarding Dual Tagged Frames on page 13 Networking at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15 Layer 2 Networking Standards on page 17 Networking at Layer 2 Benefits of Ethernet Frames In spite of the difficulties of Using a bridge to perform the network role of a router many
128. ge Documentation Ethernet OAM Link Fault Management on page 137 Example Configuring Ethernet LFM Between PE and CE on page 138 Example Configuring Ethernet LFM for Aggregated Ethernet on page 140 Example Configuring Ethernet LFM with Loopback Support on page 142 Example Configuring Ethernet LFM for Aggregated Ethernet In this example LFM is configured on an aggregated Ethernet interface AEO between Router 1 and Router 2 When configured on aggregated Ethernet LFM runs on all the individual member links LFM is enabled or disabled on the member links as they are added or deleted from the aggregation group The status of individual links is used to determine the status of the aggregated interface The use of LFM with aggregated Ethernet is shown in Figure 21 on page 140 Figure 21 Ethernet LFM for Aggregated Ethernet ge 1 0 1 ge 2 0 0 LFM 016840 140 Copyright 2010 Juniper Networks Inc Chapter 12 IEEE 802 3ah OAM Link Fault Management To configure LFM on an aggregated Ethernet interface between two routers 1 Configure LFM on Router 1 for AEO edit chassis aggregated devices ethernet device count 1 interfaces ge 1 0 1 1 gigether options 802 3ad aeO interfaces ge 2 0 0 1 gigether options 802 3ad aeO interfaces aeO 1 unit O family inet address 11 11 11 2 24 protocols oam ethernet link fault management interface aeO
129. get target 1000 1 interface ge 3 0 0 The trunk interface bridge domains sales vlan id 10 Copyright 2010 Juniper Networks Inc Chapter 6 Dynamic Profiles for VLAN Interfaces and Protocols interface ge 0 0 0 1 Other interfaces and statements for Sales engineering vlan id 20 interface ge 1 0 2 0 Other interfaces and statements for Engineering accounting vlan id 30 interface ge 2 0 3 0 Other interfaces and statements for Accounting others vlan id list 40 50 J Other departements protocols vpls site range 10 site sample site 1 site identifier 1 Other statements for instance Blue edit interfaces ge 0 0 1 unit O vlan id 100 ge 3 0 0 1 unit O family bridge interface mode trunk This is the trunk vlan id list 10 20 30 40 50 More interface statements This configuration switches the departmental VLAN traffic sales engineering etc bridge domains over the VPLS pseudowire trunk connecting to the other site Configuration of Routing Instance and Interfaces Using Dynamic Profiles Here is how dynamic profiles can be applied to this basic configuration First consider the requirement to push an outer VLAN tag value of 200 onto the VPLS pseudowire frames on egress Dynamic profiles easily satisfy this requirement edit routing instance green instance type virtual switch Other routing insta
130. gged case and to distinguish among VLAN tag Ethertype and length field for the tagged case The answer was to constrain the TPID field to values that were not valid Ethernet frame lengths or defined as valid Ethertypes The first VLAN tag added to an Ethernet frame is always indicated by a TPID value of 0x8100 This is not the VLAN identifier which appears in the next two bytes In Figure 1 on page 12 a native or normal Ethernet frame is compared to a VLAN tagged Ethernet frame The lengths of each field in bytes is shown next to the field name Copyright 2010 Juniper Networks Inc N Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Figure 1 Native Normal and VLAN Tagged Ethernet Fames Normal Ethernet frame Preamble 7 SFD 1 DA 6 SA 6 Type Length 2 Data 46 to 1500 CRC 4 IEEE 802 1Q Tagged Frame inestied fields Preamble 7 SFD 1 DA 6 SA 6 2TPI 2 TAG Type Length 2 Data 46 to 1500 CRC 4 User Priority CFI 12 bits of VLAN ID to identify 4 096 possible VLANs 3 bits 1 bit 12 bits The VLAN tag subtracts four bytes from the total MTU length of the Ethernet frame but this is seldom a problem if kept in mind When this tag is used in an Ethernet frame the frame complies with the IEEE 802 10 formerly IEEE 802 1q specification Together the four added bytes form the VLAN tag but the individual fields that comprise it are more i
131. ginator Verifying the Data Channel CS1 Verify the forwarding state of the data channel List the interfaces acting as the control channels and their respective data channels represented by the Spanning Tree Protocol STP index number user cs1 gt show protection group ethernet ring data channel Ethernet ring data channel parameters for protection group ring 1 Interface STP index Forward State ge 3 2 4 122 forwarding Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection ge 5 2 3 123 forwarding Ethernet ring data channel parameters for protection group ring 2 Interface STP index Forward State ge 3 2 4 124 discarding ge 5 2 3 125 forwarding Meaning The output displayed shows the STP index number used by eachinterfaceinring instances ring 1 and ring 2 The STP index controls the forwarding behavior for a set of VLANS on the data channel of a ring instance on aring interface For ring instances there are multiple STP index numbers here representing VLANS 200 300 500 and 600 The Forward State shows whether the data channel is forwarding or discarding traffic Verifying the VLANs on CS1 Purpose Verify the data channel logical interfaces and the VLAN IDs controlled by a ring instance data channel Action List dynamic VLAN membership user cs1 show protection group ethernet ring vlan Ethernet ring IFBD parameters for protection group ring 1 Interface Vian STP Index Bridge Domain ge 3 2 4
132. gs The outer tags are added and removed by the MX Series routers MX Series Ethernet Services Routers Solutions Page Ethernet Terms and Acronyms on page 3 Copyright 2010 Juniper Networks Inc Chapter 1 Overview of Ethernet Solutions 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 Benefits of Ethernet Frames on page 9 Networking at Layer 2 Challenges of Ethernet MAC Addresses on page 10 Networking at Layer 2 Forwarding VLAN Tagged Frames on page 11 Networking at Layer 2 Forwarding Dual Tagged Frames on page 13 Networking at Layer 2 Logical Interface Types on page 14 Layer 2 Networking Standards on page 17 Layer 2 Networking Standards For additional information about the Layer 2 networking features available on Juniper Networks MX Series Ethernet Services Routers see the following references 802 lad IEEE standard Provider Bridges 802 lag lIEEE standard Connectivity Fault Management 802 lah IEEE standard Provider Backbone Bridges 802 1p IEEE draft standard Wireless Access in Vehicular Environments 802 1O IEEE standard Provider Backbone Bridge Traffic Engineering 802 3ah 2004 IEEE standard Operations Administration and Management OAM for link fault management LFM or simple connectivity fault management CFM at the data link layer Also known as Ethernet in t
133. he Parties agree that the English version will govern For Canada Les parties aux pr sent s confirment leur volont que cette convention de m me que tous les documents y compris tout avis quis y rattach soient redig s en langue anglaise Translation The parties confirm that this Agreement and all related documentation is and will be in the English language Copyright 2010 Juniper Networks Inc vV Vi Copyright 2010 Juniper Networks Inc Part 1 Chapter 1 Part 2 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Part 3 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Part 4 Abbreviated Table of Contents About This Guide sis ra Sa GEE DE Re MERS EERS peda ee hemes xvii Overview Overview of Ethernet Solutions cc ccc cece eee eee eee eee eee 3 Basic Solutions for MX Series Routers Basic Layer 2 Features on MX Series Routers 21 Virtual Switches ss aa E EER E EER RE EE EER EE ARE EE EER EER RE RE KERE 39 VLANs Within Bridge Domain and VPLS Environments 43 Bulk Administration of Layer 2 Features on MX Series Routers 59 Dynamic Profiles for VLAN Interfaces and Protocols 63 MX Series Router as a DHCP Relay Agent 73 MX Series Router in an ATM Ethernet Interworking Function 77 Ethernet Filtering Monitoring and Fault Management Solutions for MX Series
134. he First Mile EFM and EFM OAM 802 3 2008 Clause 57 IEEE standard Operations Administration and Maintenance OAM Incorporates 802 3ah 2004 within the IEEE standard Carrier sense multiple access with Collision Detection CSMA CD Access Method and Physical Layer Specifications RFC 4761 IETF draft Virtual Private LAN Service VPLS Using BGP for Auto discovery and Signaling RFC 4762 IETF draft Virtual Private LAN Service VPLS Using Label Distribution Protocol LDP Signaling Y1731 ITU T recommendation OAM Functions and Mechanisms for Ethernet based Networks OSI RM Open Systems Interconnection Reference Model Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Terms and Acronyms on page 3 Networking and Internetworking with Bridges and Routers on page 6 Network Addressing at Layer 2 and Layer 3 on page 7 Copyright 2010 Juniper Networks Inc 17 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Networ Networ Networ Networ Networ king at Layer 2 Benefits of Ethernet Frames on page 9 king at Layer 2 Challenges of Ethernet MAC Addresses on page 10 king at Layer 2 Forwarding VLAN Tagged Frames on page 11 king at Layer 2 Forwarding Dual Tagged Frames on page 13 king at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15 Copyright 2010 Juniper Networks Inc Basic S
135. he outer tag defined in IEEE 802 1adis often called the Virtual Metropolitan Area Network VMAN tag a good way to recall the intended scope of the specification The outer tag is placed after the MAC source address moving the inner tag backwards in the frame Both tags can be added at the same time by the same device called a push push operation changed by a device a swap operation or removed by a device one at a time pop or together pop pop Devices can perform elaborate variations on these operations such as pop swap push to accomplish the necessary networking tasks with the frames they process The IEEE specification indicates that the outer tag of a doubly tagged Ethernet frame should have a TPID value of 0x88a8 Any network device can easily tell if it has received a frame with one tag 0x8100 or two tags 0x88a8 However because the value 0x8100 always means that a VLAN tag is present most vendors and networks use the same TPID value 0x8100 for the inner and outer tags As long as the configuration and processing are consistent there is no confusion and the TPID value can usually be changed if necessary How do nested VLAN tags solve the VLAN numbering limitation Taken together the two VLAN tags can be thought of as providing 24 bits for tagging space 12 bits at the outer level and 12 bits at the inner level However it is important to realize that the bits are not acted on as if they were all one tag Even when the tags
136. hernet connectivity fault management maintenance domain private level O maintenance association private ma continuity check interval 1s mep 100 interface ge 0 2 5 direction down auto discovery Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Operations Administration and Maintenance on page 103 Ethernet OAM Connectivity Fault Management on page 104 Example Configuring Ethernet CFM over VPLS on page 105 Example Configuring Ethernet CFM on Bridge Connections on page 112 Copyright 2010 Juniper Networks Inc 117 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 118 Copyright 2010 Juniper Networks Inc CHAPTER 11 ITU T Y 1731 Ethernet Frame Delay Measurements Ethernet Frame Delay Measurements on page 119 Configuring MEP Interfaces to Support Ethernet Frame Delay Measurements on page 122 Triggering an Ethernet Frame Delay Measurements Session on page 123 Viewing Ethernet Frame Delay Measurements Statistics on page 124 Example Configuring One Way Ethernet Frame Delay Measurements with Single Tagged Interfaces on page 125 Example Configuring Two Way Ethernet Frame Delay Measurements with Single Tagged Interfaces on page 130 Example Configuring Ethernet Frame Delay Measurements with Untagged Interfaces on page 134 Ethernet Frame Delay Measurements Performance management depends on the accurate measurement of service
137. hernet Services Routers Solutions Page VLANs Within a Bridge Domain or VPLS Instance on page 43 Configuring a Normalized VLAN for Translation or Tagging on page 45 Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces on page 47 Example Configuring a Provider Bridge Network with Normalized VLAN Tags on page 47 Example Configuring a Provider VPLS Network with Normalized VLAN Tags on page 51 Example Configuring One VPLS Instance for Several VLANs on page 55 Copyright 2010 Juniper Networks Inc Chapter 4 VLANS Within Bridge Domain and VPLS Environments Configuring a Normalized VLAN for Translation or Tagging This topic provides configuration and operational information to help you manipulate virtual local area networks VLANS within a bridge domain or a virtual private LAN service VPLS instance The VPLS configuration is not covered in this topic For more information about configuring Ethernet pseudowires as part of VPLS see the Junos OS Feature Guide D NOTE This topic is not intended as a troubleshooting guide However you can use it with a broader troubleshooting strategy to identify Juniper Networks MX Series Ethernet Services Routers network problems The manipulation of VLANs within a bridge domain or a VPLS instance can be done in several ways By using the vlan map statements at the edit interfaces hierarchy level This chapter does not use vlan map For more information about VLAN maps see the Ju
138. ht 2010 Juniper Networks Inc 105 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Figure 15 Ethernet OAM with VPLS Customer domain y I lt I I AD 5 2 3 yai Le o 0 0 VEAN E000 si M ge 1 0 ge 5 2 I I i Provider domain I I A Provider level 5 CFM AA Customer level 7 CFM AD L2 CE2 VLAN 2000 Up mep A 9016835 Down mep 4 The following are the configurations of the VPLS and CFM on the service provider routers Configuration of PET edit chassis foc5 pic Of tunnel services bandwidth 1g edit interfaces ge 1 0 7 encapsulation flexible ethernet services vlan tagging unit 1 encapsulation vlan vpls vlan id 2000 ge 0 0 0 1 unit O family inet address 10 200 1 1 24 family mpls loO unit O family inet address 10 255 168 231 32 primary address 127 0 0 1 32 edit routing instances 106 Copyright 2010 Juniper Networks Inc Chapter 10 IEEE 802 1ag OAM Connectivity Fault Management vpls vlan2000 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 site vlan2OOO PEI1 site identifier 2 edit protocols rsvp interface ge 0 0 0 0 mpls label switched path PE1 to PE2 to 10 100 1 1 l interface ge 0 0 0 0 bg
139. icance The access or trunk interface is implicitly associated with bridge domains based on VLAN membership Access or trunk interfaces are typically used in enterprise centric applications NOTE The difference between access interfaces and trunk interfaces is that access interfaces can be part of one VLAN only and the interface is normally attached to an end user device packets are implicitly associated with the configured VLAN In contrast trunk interfaces multiplex traffic from multiple VLANs and usually interconnect switches MX Series Ethernet Services Routers Solutions Page Ethernet Terms and Acronyms on page 3 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 Benefits of Ethernet Frames on page 9 Networking at Layer 2 Challenges of Ethernet MAC Addresses on page 10 Networking at Layer 2 Forwarding VLAN Tagged Frames on page 11 Networking at Layer 2 Forwarding Dual Tagged Frames on page 13 A Metro Ethernet Network with MX Series Routers on page 15 Layer 2 Networking Standards on page 17 Copyright 2010 Juniper Networks Inc Chapter 1 Overview of Ethernet Solutions A Metro Ethernet Network with MX Series Routers What would a Metro Ethernet network with Juniper Networks MX Series Ethernet Services Routers look like It is very likely that the Metro Ethernet network will place MX Series routers at the edge of a VPLS and MPLS c
140. icast non ip mcast policer if exceeding bandwidth limit 50k burst size limit 150k then loss priority high 2 Configure three color policer ip multicast traffic policer a three color policer to limit the IP multicast traffic edit firewall three color policer ip multicast traffic policer two rate color blind committed information rate 4m committed burst size 256k peak information rate 4100000 peak burst size 256k 3 Configure customer 1 a firewall filter that uses the two policers to limit and mark customer traffic The first term marks the IP multicast traffic based on the destination MAC address and the second term polices the broadcast unknown unicast and non IP multicast traffic edit firewall family vpls filter customer 1 term tO from destination mac address 01 00 5e 00 00 00 24 then three color policer two rate ip multicast traffic policer forwarding class expedited forwarding termtl from traffic type broadcast unknown unicast multicast then policer bcast unknown unicast non ip mcast policer Copyright 2010 Juniper Networks Inc 97 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 4 Apply the firewall filter as an input filter to the customer interface at ge 2 1 0 edit interfaces ge 2 1 0 vlan tagging encapsulation flexible ethernet services unit 5 encapsulation vlan vpls vlan id 9 family vpls
141. ices labels or marks on or in any copy of the Software or any product in which the Software is embedded e distribute any copy of the Software to any third party including as may be embedded in Juniper equipment sold in the secondhand market f use any locked or key restricted feature function service application operation or capability without first purchasing the applicable license s and obtaining a valid key from Juniper even if such feature function service application operation or capability is enabled without a key g distribute any key for the Software provided by Juniper to any third party h use the Copyright 2010 Juniper Networks Inc iii Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller i use Embedded Software on non Juniper equipment j use Embedded Software or make it available for use on Juniper equipment that the Customer did not originally purchase from Juniper or an authorized Juniper reseller k disclose the results of testing or benchmarking of the Software to any third party without the prior written consent of Juniper or L use the Software in any manner other than as expressly provided herein 5 Audit Customer shall maintain accurate records as necessary to verify compliance with this Agreement Upon request by Juniper Customer shall furnish such records to Juniper and certify its compliance with this Agreem
142. ices 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 For more information about configuring Ethernet pseudowires as part of VPLS see the Junos OS Feature Guide Copyright 2010 Juniper Networks Inc 47 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide NOTE This topic does not present exhaustive configuration listings for all routers in the figures However you can use it with a broader configuration strategy to complete the MX Series router network configurations Consider the provider bridge network shown in Figure 7 on page 48 Figure 7 Provider Bridge Network Using Normalized VLAN Tags L2 PE1 Site 2 l l l ge 3 0 0 1 l l ge 2 0 0 1 i LL m ge 4 0 0 1 ge 1 0 0 1 ge 1 0 0 11 L2 PE1 Site 1 ge 5 0 0 1 Mm kasies D ab IP QT ge 6 0 0 11 L2 PE3 Site 3 ge 5 0 0 11 Provider VLAN 500 esse esse Provider VLAN 600 L2 PE4 Site 4 g0162826 The Layer 2 provider edge PE routers are MX Series routers Each site is connected to two provider P routers for redundancy although both links are only shown for L2 PEI at Site 1 Site 1 is connected to PO and P1 as shown Site 2 is connected to PO and P2 not shown
143. identifier count count command Copyright 2010 Juniper Networks Inc Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements D NOTE The only difference in the two commands is the use of the mep statistics and delay statistics keyword The fields for these commands are described in Table 4 on page 125 Table 4 Show Ethernet Delay Command Parameters Parameter Parameter Range Description maintenance domain name Existing MD name Specifies an existing maintenance domain MD to use maintenance association ma id Existing MA identifier Specifies an existing maintenance association MA identifier to use local mep identifier 1 8191 When a MEP has been specified display statistics only for the local MEP remote mep identifier 1 8191 When a MEP has been specified display statistics only for the discovered MEP count count 1 100 default 100 The number of entries to display in the results table By default all100 entries are displayed if they exist D NOTE For each MEP you will see frame counters for sent and received Ethernet frame delay measurement frames whenever MEP statistics are displayed Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Frame Delay Measurements on page 119 Configuring MEP Interfaces to Support ETH DM on page 122 Triggering an ETH DM Session on page 123 Configuring One Way ETH DM with Single Tagged Interfaces on page 125 Configuring Tw
144. iginally invented to allow LAN switches to distinguish between physical groups of LAN ports and logical groups of LAN ports In other words there was a need to configure a LAN switch or group of local LAN switches to know that these ports belong to VLAN A and these ports belong to VLAN B This was important because of how all LANs not just Ethernet work at the frame level Lots of frames on a LAN are broadcast to all stations hosts and network nodes on the LAN segment Also multicasting works by flooding traffic within the VLAN The stations that received broadcast frames form the broadcast domain of the LAN Only Ethernet frames belonging to same broadcast domain are forwarded out certain ports on the LAN switch This prevents broadcast storms and isolates routine control frames onto the LAN segment where they make the most sense The VLAN tag was invented to distinguish among different VLAN broadcast domains on a group of LAN switches The VLAN tag is a two byte field inserted between the source MAC address and the Ethertype or length field in an Ethernet frame Another two byte field the Tag Protocol Identifier TPI or TPID precedes the VLAN tag field Two fields were necessary to hold one piece of information the VLAN tag to enable receivers to distinguish between untagged or plain Ethernet frames and those containing VLAN tags A mechanism was required to differentiate between the Ethertype and length field for the unta
145. iled link is repaired the traffic reverts to its normal pattern That is the RPL owner blocks the RPL link and unblocks traffic over the cleared link Two or more nodes form a ring Links between the nodes form a chain with the last node also connecting the first Every ring node therefore has two ports related to the ring one in each direction In this chapter these directions are referred to as east and west Copyright 2010 Juniper Networks Inc 145 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 146 Related Documentation 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 conditions require This node initiates the R APS message Normal node All other nodes on the ring that is those that are not the RPL owner node operate as normal nodes and have no special role on the ring In addition to roles each node on the Ethernet ring can be in one of several states Init The node is not yet participating in the ring ldle The node is performing normally there is no link failure on the ring In this state traffic is unblocked on both ring ports except for the RPL owner node which blocks the RPL port the other RPL owner port is unblocked Protection When a failure occurs on the ring a normal node will have traffic blocked on the ring port that connects to the failed link The RPL owner if it is not at one end of the
146. ily mpls aeO vlan vci tagging encapsulation vlan vci ccc unit O vlan id 100 inner vlan id range start 32 end 63 protocols mpls interface ge 0 2 8 0 ospf area 0 0 0 0 1 interface ge 0 2 8 0 interface loO 0 passive ldp 1 interface all l2circuit neighbor 10 255 171 45 interface ae0 0 virtual circuit id 100 CE2 Configuation Configure Dual Tagged Ethernet Interface edit interfaces ge 0 0 0 1 flexible vlan tagging encapsulation flexible ethernet services unit O vlan tags outer 100 inner 34 family inet address 30 1 1 10 24 84 Copyright 2010 Juniper Networks Inc Chapter 8 MX Series Router in an ATM Ethernet Interworking Function You verify your configuration on the MX Series router with the show l2circuit connections command user PE2 gt show l2circuit connections Layer 2 Circuit Connections Legend for connection status St EI encapsulation invalid NP interface h w not present MM mtu mismatch Dn down EM encapsulation mismatch VC Dn Virtual circuit Down CM control word mismatch Up operational VM vlan id mismatch CF Call admission control failure OL no outgoing label IB TDM incompatible bitrate NC intf encaps not CCC TCC T TDM misconfiguration BK Backup Connection ST Standby Connection CB rcvd cell bundle size bad XX unknown SP Static Pseudowire Legend for
147. instance has a data channel A data channel is a group of bridge domain virtual LAN VLAN IDs All VLAN IDs within the same ring interface share the same data forwarding properties controlled by the ERP The data channel on ring 1 is 200 300 The data channel on ring 2 is 500 600 Two customer site switches are connected to AS1 Customer site 1 uses VLANs 200 and 300 Customer site 2 Uses VLANs 500 and 600 Figure 24 ERP with Multiple Protection Instances Configured on Three MX Series Routers ring 1 data channel 200 300 ring 2 data channel 500 600 RPL owner RPL owner ring 1 ring 2 JL ge 5 2 3 0 ge 2 0 4 0 JL T FT west interface east interface Ne EF g 3 2 4 0 ge 2 0 80 east interface west interface RP link end ring 1 RP link end ring 2 ge 2 0 5 0 ge 2 V 1 0 west interface east interface DE AS1 IE KIX Customer Site 1 Customer Site 2 VLANs 200 300 VLANs 500 600 g017469 Table 5 on page 156 describes the components of the example topology Copyright 2010 Juniper Networks Inc 155 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Table 5 Components of the Network Topology Property Settings Ring instances ring 1 Data channel 200 300 e ring 2 Data channel 500 600 Customer sites Two customer sites are connected to AS 1 e Customer site 1 VLAN 200 and VLAN 300 e Customer site 2 VLAN 500 and VLAN 600 C
148. interface ge 5 2 7 0 mpls label switched path PE2 tO PET 1 to 10 200 1 1 interface ge 5 2 7 0 bgp group PE2 tO PEI1 type internal local address 10 100 1 1 family L2vpn signaling local as 65000 neighbor 10 200 1 1 ospf traffic engineering reference bandwidth 4g area O O O O 1 interface all interface fxpO O disable interface ge 5 2 7 0 oam ethernet connectivity fault management maintenance domain customer sitel level 5 maintenance association customer sitel continuity check interval 1s mep 200 1 interface ge 5 0 9 1 Copyright 2010 Juniper Networks Inc 109 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide direction up auto discovery Configuration of P MPLS only no CFM needed router edit interfaces ge 5 2 7 Connected to PE unit O family inet address 10 200 1 10 24 family mpls ge 0 1 0 Connected to PE2 unit O family inet address 10 100 1 10 24 family mpls loO unit Of family inet address 10 255 168 240 32 edit protocols rsvp interface ge 0 1 0 0 interface ge 5 2 7 0 mpls interface ge 0 1 0 0 interface ge 5 2 7 0 ospf traffic engineering reference bandwidth 4g area 0 0 0 0 interface all 110 Copyright 2010 Juniper Networks Inc Chapter 10 IEEE 802 1ag OAM Connectivity Fault Management interface fxpO O
149. interface status Up operational Dn down Neighbor 10 255 171 45 Interface Type St Time last up Up trans ae0 0 vc 100 rmt Up May 12 14 48 58 2009 2 Remote PE 10 255 171 45 Negotiated control word Yes Null Incoming label 299872 Outgoing label 299824 Local interface ae0 0 Status Up Encapsulation VLAN Q in Q and VCI Interworking Configuring PE2 with a Remote Interface Switch CElConfiguation Configure Ethernet over ATM on the ATM interface edit interfaces at 2 0 0 encapsulation ethernet over atm atm options vpi 100 unit O vci 100 34 family inet address 30 1 1 1 24 PE1Configuation Configure the Remote Interface Switch edit interfaces at 2 0 1 Copyright 2010 Juniper Networks Inc 85 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide atm options vpi 100 unit O encapsulation vlan vci ccc vpi 100 vci range start 32 end 63 l ge 5 0 0 unit O family inet address 20 1 1 1 24 family iso family mpls protocols rsvp interface ge 5 0 0 0 mpls label switched path lsp1 2 from 10 255 171 45 to 10 255 171 14 label switched path lsp2 1 from 10 255 171 14 to 10 255 171 45 interface ge 5 0 0 0 isis interface ge 5 0 0 0 connections remote interface switch rwsl f interface at 2 0 1 0 transmit lsp lspl 2 receive lsp lsp2 1 PE2 Configuation Configure the Remote Interfa
150. l Interfaces CFM can be used to monitor the physical link between two routers This functionality is similar to that supported by thelEEE 802 3ah LFM protocol NOTE The configurations in this example are only partial examples of complete and functional router configurations Do not copy these configurations and use them directly on an actual system In the following example two routers Router 1 and Router 2 are connected by a point to point Gigabit Ethernet link The link between these two routers is monitored using CFM This is shown in Figure 17 on page 116 The single boundary is a down mep in CFM terminology Figure 17 Ethernet CFM on Physical Interfaces AL ge 1 0 1 ge 0 2 5 AL I I a 7 q y Upmep VY Physical level 0 CFM Vv Down mep W 016837 Router Configure the interface and CFM edit interfaces ge 1 0 1 unit O family inet protocols oam ethernet connectivity fault management maintenance domain private level O maintenance association private ma continuity check interval 1s mep 100 1 interface ge 1 0 1 direction down auto discovery 116 Copyright 2010 Juniper Networks Inc Chapter 10 IEEE 802 1ag OAM Connectivity Fault Management The configuration on Router 2 mirrors that on Router 1 Router2 Configure the interface and CFM edit interfaces ge 0 2 5 unit O family inet protocols oam et
151. l VLANS 55 Bulk Administration of Layer 2 Features on MX Series Routers 59 Bulk Configuration of VLANs and Bridge Domains 59 Example Configuring VLAN Translation with a VLAN ID List 59 Example Configuring Multiple Bridge Domains with a VLAN ID List 60 Dynamic Profiles for VLAN Interfaces and Protocols 63 Dynamic Profiles for VPLS Pseudowires 63 Example Configuring VPLS Pseudowires with Dynamic Profiles Basic Solutions AE bre RE te ME EE a OP ae Rh eee 64 VPLS Pseudowire Interfaces Without Dynamic Profiles 64 VPLS Pseudowire Interfaces and Dynamic Profiles 65 CE Routers Without Dynamic Profiles 66 CE Routers and Dynamic Profiles 67 Example Configuring VPLS Pseudowires with Dynamic Profiles Complex Solutions RR Lease eA Oh ae eee ea deg EE ER 68 Configuration of Routing Instance and Interfaces Without Dynamic Profiles EE EE et cease ak hare Boh oho ues er Rode rm Se at ne te 68 Configuration of Routing Instance and Interfaces Using Dynamic Profiles EE DER RE DE Cue Rat ne RR A EE oe Ge RE ET age ANS 69 Configuration of Tag Translation Using Dynamic Profiles 72 MX Series Router as a DHCP Relay Agent 73 MX Series Router as a Layer 2 DHCP Relay Agent
152. late faults over a flat or single operator network architecture or a nested or hierarchical or multi provider networks OAM can provide simple link level information provide performance statistics or track end to end connectivity across the network Simple link fault management LFM for Ethernet links is defined in IEEE 802 3ah Ethernet OAM functions are implemented as Fault detection and notification provided by continuity check messages Path discovery provided by the linktrace protocol Copyright 2010 Juniper Networks Inc 103 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation Fault isolation verification and recovery isolation and verification are provided by a combination of protocols while recovery is the function of protocols such as spanning tree The loopback protocol used in Ethernet OAM is modeled on the standard IP ping After a fault is detected the loopback protocol performs fault verification and isolation under the direction of a network operator The loopback is performed using request and response message pairs A unicast loopback message is generated by a MEP and a loopback reply is generated by the destination MIP or MEP The target MAC address is learned by the continuity check protocol or linktrace protocol The loopback message s packet is always forwarded to a unique port by the originating MEP as determined by a MAC table lookup or the MEP interface M
153. le Configuring Ethernet LFM with Loopback Support on page 142 Ethernet OAM Link Fault Management Link Fault Management LFM can be used for physical link level fault detection and management The IEEE 802 3ah LFM works across a point to point Ethernet link either directly connected or through repeaters LFM provides the following functions e Failure detection on physical links in both directions as well as unidirectional failures Ability to put a port in link loopback mode remotely for diagnostics Report and receive link error events such as framing or symbol errors LFM runs at the physical or aggregated interface level When configured on an aggregated interface LFM is run individually on each member link LFM is a link layer protocol and does not need a Layer 3 IPv4 or IPv6 address to operate This allows for LFM to function on circuit cross connect transport cross connect CCC TCC encapsulated interfaces Related MX Series Ethernet Services Routers Solutions Page Documentation Example Configuring Ethernet LFM Between PE and CE on page 138 Example Configuring Ethernet LFM for CCC on page 139 Example Configuring Ethernet LFM for Aggregated Ethernet on page 140 Example Configuring Ethernet LFM with Loopback Support on page 142 Copyright 2010 Juniper Networks Inc 137 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Example Configuring Ethernet LFM Between PE and CE 138 In this
154. le 2 Text and Syntax Conventions Convention Bold text like this Description Represents text that you type Examples To enter configuration mode type the configure command user host gt configure Fixed width text like this Represents output that appears on the terminal screen user host gt show chassis alarms No alarms currently active Italic text like this e Introduces important new terms e A policy term is a named structure e Identifies book names that defines match conditions and actions e Identifies RFC and Internet draft titles e Junos System Basics Configuration Guide RFC1997 BGP Communities Attribute Italic text like this Represents variables options for which Configure the machine s domain name you substitute a value in commands or configuration statements edit root set system domain name domain name Text like this Represents names of configuration e To configure a stub area include the statements commands files and directories IP addresses configuration hierarchy levels or labels on routing platform components stub statement at the edit protocols ospf area area id hierarchy level e Theconsole port is labeled CONSOLE lt gt angle brackets Enclose optional keywords or variables stub lt default metric metric gt Copyright 2010 Juniper Networks Inc Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Table 2 Text and
155. llowed in a routing instance Bridge options are not supported with the vlan id list statement Only trunk interfaces are supported There is no support for integrated routing and bridging IRB You display the status and other parameters for automatic bridge domains configured with the vlan id list statement using the same show l2 learning instance command as used for individually configured bridge domains Related MX Series Ethernet Services Routers Solutions Page Documentation Bulk Configuration of VLANs and Bridge Domains on page 59 Example Configuring VLAN Translation with a VLAN ID List on page 59 Copyright 2010 Juniper Networks Inc 61 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 62 Copyright 2010 Juniper Networks Inc CHAPTER 6 Dynamic Profiles for VLAN Interfaces and Protocols Dynamic Profiles for VPLS Pseudowires on page 63 Example Configuring VPLS Pseudowires with Dynamic Profiles Basic Solutions on page 64 Example Configuring VPLS Pseudowires with Dynamic Profiles Complex Solutions on page 68 Dynamic Profiles for VPLS Pseudowires A router often has two types of interfaces Static interfaces which are configured before the router is booted Dynamic interfaces which are created after the router is booted and while it is running A VPLS pseudowire interface such as Isi 1048576 is dynamically created by the system Therefore the logical interface
156. loss priority PLP level of medium high and then classifies the packet in the expedited forwarding default forwarding class D NOTE This example does not present exhaustive configuration listings for all routers in the figures However you can use this example with a broader configuration strategy to complete the MX Series router network Ethernet Operations Administration and Maintenance OAM configurations To configure filtering of frames by packet loss priority 1 Configure the firewall filter filter plp configure forwarding edit firewall family bridge filter filter plp configure forwarding termO from loss priority medium high then forwarding class expedited forwarding 2 Configure a Layer 2 bridging domain bd for the ge 0 0 0 interface that has already been configured at the edit interfaces hierarchy level edit bridge domains bd domain type bridge interface ge 0 0 0 Copyright 2010 Juniper Networks Inc 101 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 3 Apply the filter filter plp configure forwarding as an input filter to the ge 0 0 0 interface edit interfaces ge 0 0 0 unit O family bridge filter input filter plp configure forwarding Related MX Series Ethernet Services Routers Solutions Page Documentation Firewall Filters for Bridge Domains and VPLS Instances on page 95 Example Configuring Policing and Marking
157. mber of the beginning bits are assigned by an Internet authority and represent a subnet located somewhere in the world The remaining bits are assigned locally and when joined to the network portion of the address uniquely identify some host on a particular network IPv6 addresses are 128 bits long Although there are significant differences for the purposes of this discussion it is enough to point out that there is also a network and host portion to an IPv6 address Note that MAC addresses are mainly organized by manufacturer and IP addresses are organized by network which is located in a particular place Therefore the IP address can easily be used by routers for a packet s overall direction for example 192 168 27 48 is west of here However the MAC addresses on a vendor s interface cards can end up anywhere in the world and often do Consider a Juniper Networks router as a simple example Every Ethernet LAN interface on the router that sends or receives packets places them inside Ethernet frames with MAC addresses All of these interfaces share the initial 24 bits assigned to Juniper Networks Two might differ only in one digit from one interface to another Yet the routers containing these MAC interfaces could be located on opposite sides of the world An Internet backbone router only needs a table entry for every network not host in the world Most other routers only have a portion of this full table and a default route for
158. ment msti 2 vlan200 This VLAN corresponds to MSTP instance 2 32 Copyright 2010 Juniper Networks Inc Chapter 2 Basic Layer 2 Features on MX Series Routers 3 Configure MSTP on Router 3 edit protocols mstp configuration name mstp for R1 2 3 The names must match to be in the same region revision level 3 The revision levels must match interface ae2 interface ae3 mstil vlan100 This VLAN corresponds to MSTP instance 1 msti 2 vlan200 This VLAN corresponds to MSTP instance 2 bridge priority 4096 This bridge acts as VLAN 200 designated bridge on the R2 R3 segment As a result of this configuration VLAN 100 and VLAN 200 share physical links but have different designated ports root ports and alternate ports on the three different routers The designated root and alternate ports for the two VLANS on the three routers are shown in Figure 6 on page 34 Copyright 2010 Juniper Networks Inc 33 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Figure 6 Designated Root and Alternate Ports VLAN 100 200 VLAN 200 ge 2 2 1 ge 2 2 6 AE l p AE2 Router 1 switch is Qu woe o e wy SO Ka h K KA Qu KA 7 fe SO Il i E O 25 Router 2 TEE EE RT H l f AE3 AE3 l xe 2 1 0 xe 1 1 0 VLAN 100 VLAN 200 VLAN 200 VLAN 100 ge 2 2 2 ge 3 3 3 ge 3 3 3 ge 2 2 2 Internet Designated Root port
159. mportant The 2 byte TPID field is just a number and has no structure only having allowed and disallowed values However the 2 byte Tag Control Information TCI field has a defined structure The three bits of the User Priority field are defined by the IEEE 802 1p specification These can mimic class of service CoS parameters established at other layers of the network IP precedence bits or MPLS EXP bits and so on The Canonical Format Indicator CFI bit indicates whether the following 12 bits of VLAN identifier conform to Ethernet or not For Ethernet frames this bit is always set to O The other possible value CFI 1 is used for Token Ring LANs and tagged frames should never be bridged between an Ethernet and Token Ring LAN regardless of the VLAN tag or MAC address The 12 bit VLAN ID allows for 4096 possible VLANs but not all values are used in all cases Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Terms and Acronyms on page 3 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 Benefits of Ethernet Frames on page 9 Networking at Layer 2 Challenges of Ethernet MAC Addresses on page 10 Networking at Layer 2 Forwarding Dual Tagged Frames on page 13 Networking at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15
160. n Guide The position of the router is shown in Figure 14 on page 96 Figure 14 Policing and Marking Traffic Entering a VPLS Core ge 2 1 0 ge 3 1 0 VPLS cloud 9016834 There are four major parts to the configuration The policer for broadcast unknown unicast and non IP multicast traffic This example marks the loss priority as high if this type of traffic exceeds 50 Kbps The two rate three color policer for IP multicast traffic This example configures a committed information rate CIR of 4 Mbps a committed burst size of 256 Kbytes a peak information rate of 4 1 Mbps and a peak burst size of 256 Kbytes the same as the CIR The filter that applies the two policers to VPLS The application of the filter to the customer interface configuration as an input filter ED NOTE This example does not present exhaustive configuration listings for all routers in the figures However you can use this example with a broader configuration strategy to complete the MX Series router network Ethernet Operations Administration and Maintenance OAM configurations Copyright 2010 Juniper Networks Inc Chapter 9 Layer 2 Firewall Filters To configure policing and marking of traffic entering a VPLS core 1 Configure policer bcast unknown unicast non ip mcast policer a firewall policer to limit the aggregate broadcast unknown unicast and non IP multicast to 50 kbps edit firewall policer bcast unknown un
161. n Link End ge 1 2 1 ge 1 2 1 1 forwarding No ge 1 0 2 ge 1 0 2 1 forwarding No Signal Failure Admin State Clear IFF ready Clear IFF ready Note that both interfaces are forwarding Router 3 will see almost identical information user router2 gt show protection group ethernet ring node state Ethernet ring APS State Event Ring Protection Link Owner pg102 idle NR RB No Restore Timer Quard Timer Operation state disabled disabled operational Note that Router 2 is not the owner Router 3 will see almost identical information user router2 gt show protection group ethernet ring statistics group name pg102 Ethernet Ring statistics for PG pg102 RAPS sent 0 RAPS received Local SF happened Remote SF happened NR event happened NR RB event happened HOOOM Router 3 will see almost identical information MX Series Ethernet Services Routers Solutions Page Ethernet Ring Protection on page 145 Example Configuring Ethernet Ring Protection for MX Series Routers on page 148 Example Viewing Ethernet Ring Protection Status Ring Failure Condition on page 172 Example Viewing Ethernet Ring Protection Status Ring Failure Condition Router 1 Operational Commands Ring Failure Condition 172 This section assumes that Ethernet ring protection is configuring correctly that Router lis the ring protection link RPL owner and that there is a link failure between Router 2 and Router 3 in the configuration example user
162. n on page 145 Copyright 2010 Juniper Networks Inc 93 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 94 Copyright 2010 Juniper Networks Inc CHAPTER 9 Layer 2 Firewall Filters Firewall Filters for Bridge Domains and VPLS Instances on page 95 Example Configuring Policing and Marking of Traffic Entering a VPLS Core on page 96 Example Configuring Filtering of Frames by MAC Address on page 98 Example Configuring Filtering of Frames by IEEE 802 1p Bits on page 99 Example Configuring Filtering of Frames by Packet Loss Priority on page 101 Firewall Filters for Bridge Domains and VPLS Instances Juniper Networks MX Series Ethernet Services Routers support firewall filters for the bridge and vpls protocol families You configure these firewall filters to control traffic within bridge domains and VPLS instances This chapter explores some of the ways that filters can be used in a Layer 2 environment to control traffic MX Series router firewall filters can be applied to Input interfaces Output interfaces Input to the Layer 2 forwarding table NOTE Broadcast unicast Unknown and multicast BUM traffic is not affected by input and output policies BUM traffic can only be filtered by forwarding table policies You use a firewall filter after taking the following two steps 1 You configure any policers and the firewall filter at the edit firewall hierarchy level 2 You apply
163. n page 21 The individual configuration steps are described in greater detail in separate topics To configure Layer 2 processing in a bridged domain network 1 Related Documentation Configure the Ethernet interfaces and VLAN tags on all three routers as described in Example Step Configuring Interfaces and VLAN Tags on page 24 Configure the bridge domains on all three routers as described in Example Step Configuring Bridge Domains on page 30 Configure the Spanning Tree Protocol on all three routers as described in Example Step Configuring Spanning Tree Protocols on page 32 Configure IRB as described in Example Step Configuring Integrated Bridging and Routing on page 34 MX Series Ethernet Services Routers Solutions Page Layer 2 Features for a Bridging Environment on page 21 Example Step Configuring Interfaces and VLAN Tags on page 24 Example Step Configuring Bridge Domains on page 30 Example Step Configuring Spanning Tree Protocols on page 32 Example Step Configuring Integrated Bridging and Routing on page 34 Example Step Configuring Interfaces and VLAN Tags Configure the Ethernet interfaces and VLAN tags on all three routers D NOTE The configurations in this chapter are only partial examples of 24 complete and functional router configurations Do not copy these configurations and use them directly on an actual system Copyright 2010 Juniper Networks Inc Chapter 2 Ba
164. nagement mep database maintenance domain md6 Maintenance domain name md6 Format string Level 6 Maintenance association name ma6 Format string Continuity check status enabled Interval 100ms Loss threshold 3 frames MEP identifier 201 Direction down MAC address 00 90 69 0a 43 94 Auto discovery enabled Priority 0 Interface name ge 5 2 9 0 Interface status Active Link status Up Defects Remote MEP not receiving CCM no Erroneous CCM received no Cross connect CCM received no RDI sent by some MEP no Statistics CCMs sent 894 Copyright 2010 Juniper Networks Inc Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements CCMs received out of sequence 0 LBMs sent 0 Valid in order LBRs received 0 Valid out of order LBRs received 0 LBRs received with corrupted data 0 LBRs sent 0 LTMs sent 0 LTMs received 0 LTRs sent 0 LTRs received 0 Sequence number of next LTM request 0 1DMs sent 0 Valid 1DMs received 0 Invalid 1DMs received 0 DMMs sent 10 DMRs sent 0 Valid DMRs received 10 Invalid DMRs received 0 Remote MEP count 1 Identifier MAC address State Interface 101 00 90 69 0a 48 57 ok ge 5 2 9 0 The collected MEP statistics are saved up to 100 per remote MEP or per CFM session and displayed as part of the MEP statistics on Router MX 1 user MX 1 gt show oam ethernet connectivity fault management mep statistics maintenance domain md6 MEP identifier 201 MA
165. ncapsulation vlan vpls vlan id 302 routing instances customer cl 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 End of customer cl vsi customer c2 vsi instance type vpls vlan id none This will remove the VLAN tags from packets sent on VPLS for customer 2 interface ge 1 0 0 11 interface ge 6 0 0 11 End of customer c2 vsi End of routing instances D NOTE This is not a complete router configuration Consider the first VLAN for customer C1 The vlan id 100 statement in the VPLS instance called customer cl vsi sets the normalized VLAN to 100 All packets sent over the pseudowires have a VLAN tag of 100 The following happens on VLAN 100 as a result of this configuration Packets received on logical interfaces ge 1 0 0 1 or ge 2 0 0 1 with a single VLAN tag of 100 in the frame are accepted Packets received on logical interface ge 3 0 0 1 with a single VLAN tag of 200 in the frame are accepted and have their tag values translated to the normalized VLAN tag value of 100 Unknown source MAC addresses and unknown destination MAC addresses are learned based on their normalized VLAN values of 100 All packets sent on the VPLS pseudowire have vlan id 100 in their VLAN tag fields Now consider the second VLAN for Customer C2 The vlan id none statement in the VPLS instance called customer c2 vsi removes the incoming VLAN tags before the packets ar
166. nce statements protocols vpls site range 10 Copyright 2010 Juniper Networks Inc 69 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide site sample site 1 site identifier 1 associate profile green vpls pw 1 Apply profile here Other routing instance statements edit dynamic profiles green vpls pw 1 interfaces junos interface ifd name unit junos underlying unit number vlan id 200 This is the outer tag family bridge interface mode trunk inner vlan id list 10 20 30 40 50 J D NOTE This is not a complete router configuration With the dynamic profile a packet in a frame arriving on an interface is classified as belonging to one of the bridge domains VLANs 10 50 At the egress of the trunk VPLS pseudowire the outer VLAN tag 200 is pushed onto the frame At the ingress of the psuedowire at the remote location the outer VLAN tag 200 is removed and the frame is delivered to the appropriate bridge domain But what if the packets associated with the Accounting VLAN are not to be forwarding to the remote site Dynamic profiles are useful here as well This configuration keeps the Accounting frames from reaching the remote site edit routing instances green instance type virtual switch Other routing instance statements protocols vpls site range 10 site sample site 1 site identifier 1 associate profile green_vpls_pw_2 Apply profile here
167. nect CS2 to CS1 and configure the family statement as bridge with a VLAN ID list of 100 through 1000 edit interfaces user as1 set ge 2 0 5 unit O family bridge interface mode trunk user as1 set ge 2 0 5 unit O family bridge vlan id list 100 1000 user as1 set ge 2 1 1 unit O family bridge interface mode trunk user as1 set ge 2 1 1 unit O family bridge vlan id list 100 2 Enable ERP specifying the control channels and data channels for ring 1 and ring 2 Copyright 2010 Juniper Networks Inc 163 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide configuring the west interface statement edit protection group set ethernet ring ring 1 east interface control channel ge 2 0 5 0 set ethernet ring ring 1 east interface control channel vlan 100 set ethernet ring ring 1 west interface control channel ge 2 1 1 0 set ethernet ring ring 1 west interface control channel vlan 100 set ethernet ring ring 2 east interface control channel ge 2 0 5 set ethernet ring ring 2 east interface control channel vlan 101 set ethernet ring ring 2 west interface control channel ge 2 1 1 0 set ethernet ring ring 2 west interface control channel vlan 101 set ethernet ring ring 2 data channel vlan 500 600 user as1 user as1 user as1 user as1 user as1 user as1 user as1 user as1 user as1 3 Configure the routing instance the bridge domains and the VLAN IDs associated with each bridge domain edit bridge domains us
168. ng a Provider Bridge Network with Normalized VLAN Tags on page 47 Example Configuring a Provider VPLS Network with Normalized VLAN Tags on page 51 Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces A learning domain is a MAC address database to which the MAC addresses are added based on the normalized VLAN tags The normalized VLAN tags associated with a learning domain are always carried within packets sent over VPLS virtual interfaces To configure bridging for several VLANs using a minimal amount of configuration and switch resources use the vlan id all configuration statement to implicitly configure multiple learning domains for a bridge domain or VPLS instance Fora logical interface with a single VLAN tag the statement implicitly creates a learning domain for each normalized VLAN of the interface For a logical interface with dual VLAN tags the statement implicitly creates a learning domain for each inner VLAN normalized VLAN Related MX Series Ethernet Services Routers Solutions Page Documentation VLANs Within a Bridge Domain or VPLS Instance on page 43 Packet Flow Through a Bridged Network with Normalized VLANs on page 44 Example Configuring One VPLS Instance for Several VLANs on page 55 Example Configuring a Provider Bridge Network with Normalized VLAN Tags This topic provides a configuration example to help you effectively configure a network of Juniper Networks MX Series Ethernet Serv
169. nnel ge 3 2 4 0 vlan 101 west interface control channel ge 5 2 3 0 vlan 101 data channel vlan 500 600 J Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection 159 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 160 CLI Quick Configuration 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 bd200 vlan id 200 bd300 vlan id 300 bd500 vlan id 500 bd600 vlan id 600 Configuring ERP on CS2 To quickly configure CS2 for ERP copy the following commands and paste them into the switch terminal window of CS2 edit set interfaces ge 2 0 4 unit O family bridge interface mode trunk set interfaces ge 2 0 4 unit O family bridge vlan id list 100 1000 set interfaces ge 2 0 8 unit O family bridge interface mode trunk set interfaces ge 2 0 8 unit O family bridge vlan id list 100 1000 set protocols protection group ethernet ring ring 1 east interface control channel ge 2 0 4 0 set protocols protection group ethernet ring ring 1 east interface control channel vlan 100 set protocols protection group ethernet ring ring 1 west interface control channel ge 2 0 8 0 set protocols protection group ethernet ring ring 1 west interface control channel vlan 100 set protocols protection group ethernet ring ring 1 data channel
170. nos OS Network Interfaces Configuration Guide By using vlan id statements within a bridge domain or VPLS instance hierarchy This method is used in the configuration in this chapter The vlan id and vlan tags statements under the bridge domain or VPLS routing instance are used to Translate normalize received VLAN tags or Implicitly create multiple learning domains each with a learn VLAN The use of a VLAN map or a normalized VLAN is optional This section discusses the following topics Implicit VLAN Translation to a Normalized VLAN on page 45 Sending Tagged or Untagged Packets over VPLS Virtual Interfaces on page 46 Configuring a Normalized VLAN on page 46 Implicit VLAN Translation to a Normalized VLAN The VLAN tags of a received packet are compared with the normalized VLAN tags specified with either the vlan id or vlan tags statements If the VLAN tags of the received packet are different from the normalized VLAN tags then appropriate VLAN tag operations such as push push pop pop pop swap swap swap swap and others are implicitly made to convert the received VLAN tags to the normalized VLAN tags For more information about these operations see the Junos OS Routing Protocols Configuration Guide Copyright 2010 Juniper Networks Inc 45 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Then the source MAC address of a received packet is learned based on the normalized VLAN con
171. ny chassis or processing units for which Customer has paid the applicable license fees provided however with respect to the Steel Belted Radius or Odyssey Access Client software only Customer shall use such Software on a single computer containing a single physical random access memory space and containing any number of processors Use of the Steel Belted Radius or IMS AAA software on multiple computers or virtual machines e g Solaris zones requires multiple licenses regardless of whether such computers or virtualizations are physically contained on a single chassis c Product purchase documents paper or electronic User documentation and or the particular licenses purchased by Customer may specify limits to CUstomer s use of the Software Such limits may restrict use to a maximum number of seats registered endpoints concurrent users sessions calls connections subscribers clusters nodes realms devices links ports or transactions or require the purchase of separate licenses to use particular features functionalities services applications operations or capabilities or provide throughput performance configuration bandwidth interface processing temporal or geographical limits In addition such limits may restrict the use of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software Customer s use of the Software shall be subject to all such limitati
172. o Way ETH DM with Single Tagged Interfaces on page 130 Configuring ETH DM with Untagged Interfaces on page 134 Example Configuring One Way Ethernet Frame Delay Measurements with Single Tagged Interfaces This example uses two MX Series routers MX 1 and MX 2 The configuration creates a CFM down MEP session ona VLAN tagged logical interface connecting the two ge 5 2 9 on Router MX 1 and ge 0 2 5 on Router MX 2 Copyright 2010 Juniper Networks Inc 125 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide NOTE These are not complete router configurations Configuration on Router MX 1 edit interfaces ge 5 2 9 vlan tagging unit O vlan id 512 protocols oam ethernet connectivity fault management traceoptions file eoam_cfm log size 1g files 2 world readable flag all linktrace path database size 255 age 10s maintenance domain md6 level 6 maintenance association ma6 continuity check interval 100ms hold interval 1 mep 2011 interface ge 5 2 9 0 direction down auto discovery Configuration on Router MX 2 edit interfaces ge 0 2 5 1 vlan tagging unit O vlan id 512 126 Copyright 2010 Juniper Networks Inc Chapter 11 ITU T Y 1731 Ethernet Frame Delay Measurements protocols oam ethernet connectivity fault management traceoptions file eoam_cfm log size 1g files 2 world readable flag all linktrace
173. olutions for MX Series Routers Basic Layer 2 Features on MX Series Routers on page 21 e Virtual Switches on page 39 VLANs Within Bridge Domain and VPLS Environments on page 43 Bulk Administration of Layer 2 Features on MX Series Routers on page 59 Dynamic Profiles for VLAN Interfaces and Protocols on page 63 MX Series Router as a DHCP Relay Agent on page 73 MX Series Router in an ATM Ethernet Interworking Function on page 77 Copyright 2010 Juniper Networks Inc Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 20 Copyright 2010 Juniper Networks Inc CHAPTER 2 Basic Layer 2 Features on MX Series Routers Layer 2 Features for a Bridging Environment on page 21 Example Roadmap Configuring a Basic Bridge Domain Environment on page 22 Example Step Configuring Interfaces and VLAN Tags on page 24 Example Step Configuring Bridge Domains on page 30 Example Step Configuring Spanning Tree Protocols on page 32 Example Step Configuring Integrated Bridging and Routing on page 34 Layer 2 Features for a Bridging Environment You configure MX Series routers exactly as you would any other router running the Junos OS That is all the familiar Layer 3 features and protocols are available on the MX Series routers However you can configure Layer 2 features that are unique to the MX Series routers This chapter addresses Layer 2 configuration for the MX Series routers For information about con
174. om source LAN to destination LAN However the MAC address is much larger than the IPv4 address currently used on the Internet backbone 48 bits compared to the 32 bits of IPv4 This poses problems Also because the MAC address has no network organization like the IPv4 or IPv6 address an Layer 2 network node must potentially store every conceivable MAC address in memory for next hop table lookups Instead of tables of about 125 000 entries every Layer 2 network node would have to store millions of entries for example 24 bits the potential NIC production from one Ethernet vendor would require a table of more than 16 million entries MX Series Ethernet Services Routers Solutions Page Ethernet Terms and Acronyms on page 3 Networking and Internetworking with Bridges and Routers on page 6 Network Addressing at Layer 2 and Layer 3 on page 7 Copyright 2010 Juniper Networks Inc Chapter 1 Overview of Ethernet Solutions 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 Forwarding Dual Tagged Frames on page 13 Networking at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15 Layer 2 Networking Standards on page 17 Networking at Layer 2 Forwarding VLAN Tagged Frames VLAN tags were not developed as a way to limit network node table entries They were or
175. ome cases service providers must deal with thousands of bridge domains on a single switch By default the router does not create more than one bridge domain The configuration of even several hundred bridge domains one at a time can be a burden However you can configure multiple bridge domains with only one statement Each bridge domain will have the form prefix vlan number The prefix and number are supplied by the configuration statement MX Series Ethernet Services Routers Solutions Page Example Configuring VLAN Translation with a VLAN ID List on page 59 Example Configuring Multiple Bridge Domains with a VLAN ID List on page 60 Example Configuring VLAN Translation with a VLAN ID List In many cases the VLAN identifiers on the frames of an interface s packets are not exactly correct VLAN translation or VLAN rewrite allows you to configure bidirectional VLAN identifier translation with a list on frames arriving on and leaving from a logical interface This lets you use unique VLAN identifiers internally and maintain legacy VLAN identifiers on logical interfaces To perform VLAN translation on the packets on a trunk interface insert the vlan rewrite statement at the edit interfaces interface name unit unit number hierarchy level You must also include the family bridge statement at the same level because VLAN translation is only supported on trunk interfaces The reverse translation takes place on egress In other words if VLA
176. on PE2 edit interfaces ge 5 1 7 1 vlan tagging 114 Copyright 2010 Juniper Networks Inc Chapter 10 IEEE 802 1ag OAM Connectivity Fault Management encapsulation flexible ethernet services unit O encapsulation vlan bridge vlan id 2000 ge 5 2 3 vlan tagging encapsulation flexible ethernet services unit O encapsulation vlan bridge vlan id 2000 edit bridge domains bridge vlan2000 1 domain type bridge interface ge 5 2 3 0 interface ge 5 1 7 0 edit protocols oam ethernet connectivity fault management maintenance domain provider outer f level 5 maintenance association provider outer sitel f continuity check interval 1s mep 100 1 interface ge 5 2 3 0 direction up auto discovery maintenance domain provider inner level 3 maintenance association provider inner sitel continuity check interval 1s mep 100 1 interface ge 5 1 7 0 direction down auto discovery Related MX Series Ethernet Services Routers Solutions Page D tati oEARIEPESUER Ethernet Operations Administration and Maintenance on page 103 Ethernet OAM Connectivity Fault Management on page 104 Copyright 2010 Juniper Networks Inc 15 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Example Configuring Ethernet CFM over VPLS on page 105 Example Configuring Ethernet CFM on Physical Interfaces on page 116 Example Configuring Ethernet CFM on Physica
177. on groups ring 1 and ring 2 For ring 1 VLAN 200 and VLAN 300 are being supported on both STP Index 22 and 23 on bridge domains bd200 and bd300 For ring 2 VLAN 500 and VLAN 600 are being supported on both STP Index 24 and 25 on bridge domains bd500 and bd600 The data channel controls the traffic on the VLAN IDs to facilitate load balancing Ethernet Ring Protection Using Ring Instances for Load Balancing on page 147 Ethernet Ring Protection on page 145 Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection Example Viewing Ethernet Ring Protection Status Normal Ring Operation Router 1 Operational Commands Normal Ring Operation Router 2 and Router 3 Operational Commands Normal Ring Operation Under normal operating conditions when Ethernet ring protection is configured correctly the ring protection link RPL owner Router 1 in the configuration example will see the following user router1 gt show protection group ethernet ring aps Ethernet Ring Name Request state No Flush Ring Protection Link Blocked pg101 NR No Yes Originator Remote Node ID Yes Note that the ring protection link is blocked and the node is marked as the originator of the protection user router1 gt show protection group ethernet ring interface Ethernet ring port parameters for protection group pg101 Interface Control Channel Forward State Ring Protection Link End ge 1 0 1 ge 1 0 1 1 discarding Yes ge 1 2 4 ge 1
178. onnected was usually based on some form of Ethernet This is why Ethernet and IP fit so well together Ethernet defines the LAN and the Internet protocols define how these LANs are connected More specifically Ethernet LANs and IP networks occupy different layers of the Internet s TCP IP protocol suite Between sender and receiver networks deal with the bottom three layers of the model the physical layer Layer 1 the data link or MAC layer Layer 2 and the network layer Layer 3 D NOTE These layers are also found in the Open Systems Interconnect Reference Model OSI RM however in this chapter they are applied to the TCP IP protocol suite All digital networks ultimately deal with zeroes and ones and the physical layer defines bit representation on the media Physical layer standards also define mechanical aspects of the network such as electrical characteristics or connector shapes functional aspects such as bit sequence and organization and so on The physical layer only spits bits and has very little of the intelligence required to implement a complete network Devices that connect LAN segments at the physical layer are called hubs and all bits that appear on one port of the hub are also sent out on the other ports This also means that bad bits that appear on one LAN segment are propagated to all other LAN segments Above the physical layer the data link layer defines the first order bit structure or frame for the ne
179. ons and purchase of all applicable licenses d For any trial copy of the Software Customer s right to use the Software expires 30 days after download installation or use of the Software Customer may operate the Software after the 30 day trial period only if Customer pays for a license to do so Customer may not extend or create an additional trial period by re installing the Software after the 30 day trial period e The Global Enterprise Edition of the Steel Belted Radius software may be used by Customer only to manage access to Customer s enterprise network Specifically service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel Belted Radius software to support any commercial network access services The foregoing license is not transferable or assignable by Customer No license is granted herein to any user who did not originally purchase the applicable license s for the Software from Juniper or an authorized Juniper reseller 4 Use Prohibitions Notwithstanding the foregoing the license provided herein does not permit the Customer to and Customer agrees not to and shall not a modify unbundle reverse engineer or create derivative works based on the Software b make unauthorized copies of the Software except as necessary for backup purposes c rent sell transfer or grant any rights in and to any copy of the Software in any form to any third party d remove any proprietary not
180. oralski Editing Sonia Saruba Joanne McClintock Illustration Nathaniel Woodward Faith Bradford Cover Design Edmonds Design Revision History October 2010 R1 Junos OS Release 10 4 The information in this document is current as of the date listed in the revision history YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant The Junos OS has no known time related limitations through the year 2038 However the NTP application is known to have some difficulty in the year 2036 ii Copyright 2010 Juniper Networks Inc END USER LICENSE AGREEMENT READ THIS END USER LICENSE AGREEMENT AGREEMENT BEFORE DOWNLOADING INSTALLING OR USING THE SOFTWARE BY DOWNLOADING INSTALLING OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED HEREIN YOU AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER AS A REPRESENTATIVE AGENT AUTHORIZED TO BIND THE CUSTOMER CONSENT TO BE BOUND BY THIS AGREEMENT IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN THEN A DO NOT DOWNLOAD INSTALL OR USE THE SOFTWARE AND B YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS 1 The Parties The parties to this Agreement are i Juniper Networks Inc if the Customer s principal office is located in the Americas or Juniper Networks Cayman Limited if the Customer s principal office is located outside the Americas such applicable entity being referred to herein as Juniper
181. ore network The VLAN labels in the packet are stacked with MPLS labels as shown in Figure 2 on page 15 For a more detailed examination of this type of Metro Ethernet network see Example Configuring a Provider VPLS Network with Normalized VLAN Tags on page 51 Figure 2 A Metro Ethernet Network DA PO PseudoWire for VLAN SA L2PE1 0x8100 VLAN 500 Transport LABEL L2 PE2 Site 2 VPLS LABEL DA SA 0x8100 VLAN 100 Ethertype 0x8100 SIP ETTET PseudoWire for VLAN None ge 3 0 0 1 AE Bi ge 2 0 0 1 ge 1 0 0 1 L2 PE1 ge 1 0 0 11 Site 1 L2 PE3 Site 3 ge 6 0 0 11 ge 5 0 0 11 DA P1 SA L2PE1 0x8100 VLAN 500 Transport LABEL VPLS LABEL DA SA L2 PE4 Ethertype 0x800 Site 4 SIP g0162827 Another possible configuration this one without the VPLS and MPLS core is shown in Figure 3 on page 16 Copyright 2010 Juniper Networks Inc 15 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Figure 3 A Metro Ethernet Network with MX Series Routers Ethernet hub TPI 8100 delle od Series TPI 88a8 TPI 88a8 TPI 88a8 9016820 Ethernet hub 4 TPI 8100 ooo In Figure 3 on page 16 the circled numbers reflect the different formats that the Ethernet frames can take as the fram
182. ose and cause consequential loss and that the same form an essential basis of the bargain between the Parties 9 Termination Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license granted herein Upon such termination Customer shall destroy or return to Juniper all copies of the Software and related documentation in Customer s possession or control 10 Taxes All license fees payable under this agreement are exclusive of tax Customer shall be responsible for paying Taxes arising from the purchase of the license or importation or use of the Software If applicable valid exemption documentation for each taxing jurisdiction shall be provided to Juniper prior to invoicing and Customer shall promptly notify Juniper if their exemption is revoked or modified All payments made by Customer shall be net of any applicable withholding tax Customer will provide reasonable assistance to Juniper in connection with such withholding taxes by promptly providing Juniper with valid tax receipts and other required documentation showing Customer s payment of any withholding taxes completing appropriate applications that would reduce the amount of withholding tax to be paid and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder Customer shall comply with all applicable tax laws and regulations and Customer will promptly pay or reimburse
183. outing instance statements edit dynamic profiles green_vpls_pw_4 interfaces junos interface ifd name unit junos underlying unit number family bridge interface mode trunk vlan id list 10 20 30 40 50 J All VLANs vlan rewrite translate 110 10 Sales VLAN vlan rewrite translate 120 20 Engineering VLAN D NOTE This is not a complete router configuration This translates the sales and engineering VLAN tags egressing the VPLS pseudowire accordingly At the ingress of the VPLS pseudowire VLANs 110 and 120 are translated back to 10 and 20 respectively Related MX Series Ethernet Services Routers Solutions Page D tati EME PE Dynamic Profiles for VPLS Pseudowires on page 63 Example Configuring VPLS Pseudowires with Dynamic Profiles Basic Solutions on page 64 72 Copyright 2010 Juniper Networks Inc CHAPTER 7 MX Series Router as a DHCP Relay Agent MX Series Router as a Layer 2 DHCP Relay Agent on page 73 Example Configuring DHCP Relay in a Bridge Domain VLAN Environment on page 74 Example Configuring DHCP Relay ina VPLS Routing Instance Environment on page 75 MX Series Router as a Layer 2 DHCP Relay Agent The Dynamic Host Configuration Protocol DHCP is Used by a DHCP client host to determine Layer 3 information such as an IP address from a DHCP server DHCP uses the client s MAC Layer 2 address to query the server A router can be used as a DHCP relay agent to pass the quer
184. oviders and customers may be part of different administrative domains Each administrative domain is mapped into one maintenance domain providing enough information to perform its own management thus avoiding security breaches and making end to end monitoring possible Each maintenance domain is associated with a maintenance domain level from O through 7 Level allocation is based on the network hierarchy where outermost domains are assigned a higher level than the innermost domains Customer end points have to highest maintenance domain level In a CFM Copyright 2010 Juniper Networks Inc Chapter 10 IEEE 802 lag OAM Connectivity Fault Management maintenance domain each service instance is called a maintenance association A maintenance association can be thought as a full mesh of maintenance endpoints MEPs having similar characteristics MEPs are active CFM entities generating and responding to CFM protocol messages There is also a maintenance intermediate point MIP which is a CFM entity similar to the MEP but more passive MIPs only respond to CFM messages MEPs can be up MEPs or down MEPs A link can connect a MEP at level 5 to a MEP at level 7 The interface at level 5 is an up MEP because the other end of the link is at MEP level 7 and the interface at level 7 is a down MEP because the other end of the link is at MEP level 5 In a Metro Ethernet network CFM is commonly used at two levels By the service provider to
185. p group PEl to PE2 type internal local address 10 200 1 1 family l2vpn signaling local as 65000 neighbor 10 100 111 ospf traffic engineering reference bandwidth 4g area 0 0 0 0 1 interface all interface fxpO O disable interface ge 0 0 0 0 oam ethernet connectivity fault management maintenance domain customer sitel level 5 maintenance association customer sitel continuity check Copyright 2010 Juniper Networks Inc 107 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide interval 1s mep 100 1 interface ge 1 0 71 direction up auto discovery Configuration of PE2 edit chassis foc5 pic Of tunnel services bandwidth 1g edit interfaces ge 5 0 9 1 vlan tagging encapsulation flexible ethernet services unit 1 encapsulation vlan vpls vlan id 2000 ge 5 2 7 unit O family inet address 10 100 1 1 24 family mpls OO unit O family inet address 10 255 168 230 32 1 primary address 127 0 0 1 32 edit routing instances vpls vlan2000 1 instance type vpls vlan id 2000 interface ge 5 0 9 1 108 Copyright 2010 Juniper Networks Inc Chapter 10 IEEE 802 1ag OAM Connectivity Fault Management route distinguisher 10 255 168 230 2000 vrf target target 1000 1 protocols vpls site range 10 site vlan2000 PE2 site identifier 1 edit protocols rsvp
186. page 77 Example Configuring MX Series Router ATM Ethernet Interworking on page 79 MX Series Router ATM Ethernet Interworking Function You can configure an MX Series router as part of an ATM Ethernet interworking function IWF scenario mapping outer and inner VLAN tags to ATM Virtual Path Identifier VPI and Virtual Channel Identifier VCI The ATM Ethernet interworking scenario is shown in Figure 10 on page 77 The MX Series router is configured as the Provider Edge 2 PE2 router in the figure to support the ATM Ethernet IWF Ethernet is the only transport type supported Figure 10 ATM Ethernet VLAN Interworking L2 circuits if switch I P backhaul ATM DSLAM Service Stacked VLAN Service _ CE2 q T Customer Edge 1 Provider Edge 1 Provider Edge 2 Customer Edge 2 ATM DSLAM Ethernet B RAS gt VPI maps to outer VLAN tag 5 VCI maps to inner VLAN tag g017428 The PEI router translates between ATM and Ethernet VLANs Only an M Series router can function as the PE router The PE router translates between the ATM VPI and VCI and Ethernet VLAN tags as follows ATM VPI to and from outer VLAN tag of the Ethernet frame ATM VCI to and from inner VLAN tag of the Ethernet frame Copyright 2010 Juniper Networks Inc 77 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 78 Related Documentation Because of the translation the flow of packets and frames between PE the M
187. ple Viewing Ethernet Ring Protection Status Ring Failure Condition on page 172 Ethernet Ring Protection Using Ring Instances for Load Balancing on page 147 Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection Example Configuring Load Balancing Within Ethernet Ring Protection for MX Series Routers on page 154 Ethernet Ring Protection Using Ring Instances for Load Balancing Related Documentation Juniper Network MX Series Ethernet Services Routers support Ethernet ring protection ERP to help achieve high reliability and network stability ERP is used in router or bridge networks to protect against link failure A single ring topology is configured that uses one specific link called a ring protection link RPL to protect the whole ring When all links are up and running the RPL blocks traffic and remains idle However if a link fails the RPL routes traffic to bypass the failure on the ring NOTE To learn how ERP works in a single ring topology see Ethernet Ring Protection on page 145 MX Series routers now support ERP ring instances Whereas traffic in a single ring topology follows the same path traffic within ring instances allows some traffic to pass through one path while other traffic can follow a different path Dividing traffic in this way supports traffic load balancing in the physical ring Ring instances are like traffic channels that contain different sets of virtual LANS VLAN
188. psulation 1sp sw LSP switching DS disabled tx p2mp sw transmit P2MP switching Dn down rx p2mp sw receive P2MP switching gt only outbound conn is up lt only inbound conn is up Legend for circuit types Up operational intf interface RmtDn remote CCC down tlsp transmit LSP Restart restarting rlsp receive LSP Connection Circuit Type St Time last up Up trans rws1 rmt if Up May 13 11 25 40 1 ge 0 2 0 0 intf Up 1sp2 1 tlsp Up 1sp1 2 rlsp Up Configuring PE2 with a Remote Interface Switch over Aggregated Ethernet CE1Configuation Configure Ethernet over ATM on the ATM interface edit interfaces at 2 0 0 encapsulation ethernet over atm atm options vpi 100 unit O vci 100 34 family inet address 30 1 1 1 24 PE1Configuation Configure the Remote Interface Switch edit interfaces at 2 0 1 atm options vpi 100 unit O encapsulation vlan vci ccc vpi 100 vci range start 32 end 63 ge 5 0 0 88 Copyright 2010 Juniper Networks Inc Chapter 8 MX Series Router in an ATM Ethernet Interworking Function unit O family inet address 20 1 1 1 24 family iso family mpls protocols rsvp interface ge 5 0 0 0 mpls label switched path lsp1 2 from 10 255 171 45 to 10 255 171 14 label switched path lsp2 1 from 10 255 171 14 to 10 255 171 45 interface ge 5 0 0 0 isis interface ge 5 0 0 0 connections
189. ptions 802 3ad ae2 interfaces ge 11 1 5 gigether options 802 3ad ae2 interfaces ae2 unit O family bridge interface mode trunk vlan id list 100 200 205 interfaces ae3 encapsulation extended vlan bridge vlan tagging unit 100 vlan id 100 unit 200 vlan id 200 MX Series Ethernet Services Routers Solutions Page Layer 2 Features for a Bridging Environment on page 21 Example Roadmap Configuring a Basic Bridge Domain Environment on page 22 Example Step Configuring Bridge Domains on page 30 Example Step Configuring Spanning Tree Protocols on page 32 Example Step Configuring Integrated Bridging and Routing on page 34 Juniper Networks Inc 29 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Example Step Configuring Bridge Domains To configure the bridge domains on all three routers 1 Configure a bridge domain on Router 1 edit bridge domains vlanlOO domain type bridge vlan id 100 interface ge 2 2 1 100 interface ael 100 vlan200 1 domain type bridge vlan id 200 interface ge 2 2 1 200 interface ge 2 2 6 200 interface ael 200 vlan201 1 domain type bridge vlan id 201 vlan202 domain type bridge vlan id 202 vlan203 1 domain type bridge vlan id 203 vlan204 domain type bridge vlan id 204 vlan205 1 domain type bridge vlan id 205 2 Configure a bridge domain on Router 2 edit bridge
190. r 1 and the other routers ge 2 1 0 through ge 2 1 5 are gathered into two aggregated Ethernet AE links mixing bridged traffic from the VLANs AE1 will consist of the first three links and AE2 will use the last three links The same approach is taken for the links on Router 2 and Router 3 The Gigabit Ethernet links from Router 1 to the customer devices ge 2 2 1 and ge 2 2 6 will be bridged and include VLAN tag 100 on ge 2 2 1 and VLAN tag 200 on ge 2 2 6 The other two routers Router 2 and Router 3 also have two ports configured to handle VLAN 100 on one port ge 2 2 2 and VLAN 200 on the other ge 3 3 3 Copyright 2010 Juniper Networks Inc 23 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Router 2 and Router 3 have IRB configured so that they can pass traffic to other routers in the rest of the network Router lhas an access interface which provides bridging on VLAN 205 and is connected to a customer device configured on ge 2 2 2 Router 3 has an access interface which provides bridging on VLAN 200 and is connected to a customer device configured on ge 2 2 6 Router 1 and Router 3 are configured with a trunk interface to a switch for VLANs 200 205 On both routers this interface is ge 2 2 4 Example Configuration Summary This procedure summarizes the minimum configuration steps required for Layer 2 processing in a bridged environment as described in Layer 2 Features for a Bridging Environment o
191. ration snippet into a text file save the file with a name and copy the file to a directory on your routing platform For example copy the following snippet to a file and name the file ex script snippet conf Copy the ex script snippet conf file to the var tmp directory on your routing platform commit file ex script snippet xsl 2 Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode command edit user host edit system scripts edit system scripts 3 Merge the contents of the file into your routing platform configuration by issuing the load merge relative configuration mode command edit system scripts user host load merge relative var tmp ex script snippet conf load complete For more information about the load command see the Junos OS CLI User Guide Documentation Conventions Table 1 on page xxi defines notice icons used in this guide xx Copyright 2010 Juniper Networks Inc Table 1 Notice Icons Icon Meaning O Informational note Description About This Guide Indicates important features or instructions Caution Indicates a situation that might result in loss of data or hardware damage Warning Alerts you to the risk of personal injury or death Laser warning AN A s Alerts you to the risk of personal injury from a laser Table 2 on page xxi defines the text and syntax conventions used in this guide Tab
192. rcuit neighbor 10 255 171 45 interface ge 0 2 0 0 virtual circuit id 100 CE2 Configuation Configure Dual Tagged Ethernet Interface edit interfaces ge 0 0 0 flexible vlan tagging encapsulation flexible ethernet services unit O Copyright 2010 Juniper Networks Inc 81 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide vlan tags outer 100 inner 34 family inet address 30 1 1 10 24 You verify your configuration on the MX Series router with the show l2circuit connections command user PE2 gt show l2circuit connections Layer 2 Circuit Connections Legend for connection status St EI encapsulation invalid NP MM mtu mismatch Dn EM encapsulation mismatch VC Dn CM control word mismatch Up VM vlan id mismatch CF OL no outgoing label IB NC intf encaps not CCC TCC TM BK Backup Connection ST CB rcvd cell bundle size bad XX SP Static Pseudowire Legend for interface status Up operational Dn down Neighbor 10 255 171 45 Interface Type St ge 0 2 0 0 vc 100 rmt Up interface h w not present down Virtual circuit Down operational Call admission control failure TDM incompatible bitrate TDM misconfiguration Standby Connection unknown Time last up Up trans May 12 13 01 50 2009 1 Remote PE 10 255 171 45 Negotiated control word Yes Null Incoming label 299824 Outgoing label
193. re 2 A Metro Ethernet Network 15 Figure 3 A Metro Ethernet Network with MX Series Routers 16 Figure 4 VLAN Tags on a Metro Ethernet Network 16 Basic Solutions for MX Series Routers Basic Layer 2 Features on MX Series Routers 21 Figure 5 Bridging Network with MX Series Routers 23 Figure 6 Designated Root and Alternate Ports 34 VLANs Within Bridge Domain and VPLS Environments 43 Figure 7 Provider Bridge Network Using Normalized VLAN Tags 48 Figure 8 VLAN Tags and VPLS Labels 52 Figure 9 Many VLANs on One VPLS Instance 56 MX Series Router in an ATM Ethernet Interworking Function 77 Figure 10 ATM Ethernet VLAN Interworking 77 Figure 11 ATM Ethernet VLAN Interworking Packet Structure 78 Figure 12 CCC to Stacked VLAN Translation 78 Figure 13 ATM Ethernet VLAN Interworking 79 Ethernet Filtering Monitoring and Fault Management Solutions for MX Series Routers Layer 2 Firewall Filters 0 0 ccc ee sae ee eee eee eee eee eee nae 95 Figure 14 Policing and Marking Traffic Entering a VPLS Core 96 IEEE 802 1ag OAM Connectivity Fault Management
194. ress database NOTE You configure IRB on Router 2 and Router 3 The Virtual Router Redundancy Protocol VRRP is configured on the IRB interface so that both links can be used to carry traffic between the bridge domain and the router network To configure IRB on Router 2 and Router 3 1 Configure the router link and IRB on Router 2 edit interfaces xe 2 1 0 unit O family inet address 10 0 10 2 24 Routing interface irb unit O family inet address 10 0 1 2 24 1 vrrp group 1 virtual address 10 0 1 51 priority 254 unit 1 family inet address 10 0 2 2 24 vrrp group 2 virtual address 10 0 2 51 priority 100 bridge domains vlan 100 domain type bridge vlan id 100 interface ge 2 2 2 100 Copyright 2010 Juniper Networks Inc 35 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide interface ael 100 interface ae3 100 routing interface irb O vlan 200 1 domain type bridge vlan id 200 interface ge 3 3 3 200 interface ael 200 interface ae3 200 routing interface irb l 2 Configure the router link and IRB on Router 3 edit interfaces xe 1 1 0 unit O family inet address 10 0 20 3 24 Routing interface irb unit O family inet address 10 0 1 3 24 vrrp group1 virtual address 10 0 1 51 priority 100 unit 1 family inet address 10 0 2 3 24 vrrp group 2 virtu
195. ring If a Request state of SF is displayed it indicates there is a signal failure on the ring The output also shows that the ring protection link is not blocked The No Flush field displays No indicating that MAC addresses will be flushed when the ring nodes receive this message first time A value of Yes would indicate MAC address flushing is not needed The Originator field for ring 1 dispays yes indicating that this node is an R APS originator The Originator field for ring 2 dispays No indicating that this node is not an R APS originator Verifying the Data Channel CS2 Verify the forwarding state of the data channel List the interfaces acting as the control channels and their respective data channels represented by the STP index number user cs2 gt show protection group ethernet ring data channel Ethernet ring data channel parameters for protection group ring 1 Interface STP index Forward State ge 2 0 4 44 forwarding ge 2 0 8 45 forwarding Ethernet ring data channel parameters for protection group ring 2 Interface STP index Forward State ge 2 0 4 46 forwarding ge 2 0 8 47 discarding The output displayed shows the STP index number used by each interface in ring instances ring 1 and ring 2 The STP index controls the forwarding behavior for a set of VLANs on the data channel of a ring instance on aring interface For ring instances there are multiple STP index numbers here representing VLANs 200 300 500 and 600 The For
196. ring a Basic Bridge Domain Environment on page 22 More detailed examples are also provided for the four features generally required in a Layer 2 environment Interfaces and VLAN tags required Bridge domains required by the topology Spanning tree protocols required by the topology Integrated bridging and routing required by the topology At the end of this configuration you create two virtual switches as separate routing instances to separate the VLANs and broadcast domains Because the same VLAN ID can be used in multiple switched networks virtual switches can keep each VLAN and broadcast domain logically separated To configure two virtual switches as separate routing instances 1 The following statements configure the first virtual switch in a routing instance edit routing instances virtual switch 1 instance type virtual switch Virtual switch 1 configuration with one STP VLAN ID set 2 The following statement configure the second virtual switch in a different routing instance edit routing instances virtual switch 2 instance type virtual switch Virtual switch 2 configuration with another STP VLAN ID set This is not a complete configuration For more information about configuring virtual switches see the Junos OS Layer 2 Configuration Guide 40 Copyright 2010 Juniper Networks Inc Chapter 3 Virtual Switches Related MX Series Ethernet Services Routers Solution
197. rip mode to gather frame delay statistics and simultaneous statistics from multiple sessions Ethernet frame Copyright 2010 Juniper Networks Inc 119 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide delay measurement provides fine control to operators for triggering delay measurement on a given service and can be used to monitor Service Level Agreements SLAs Ethernet frame delay measurement also collects other useful information such as worst and best case delays average delay and average delay variation Ethernet frame delay measurement supports hardware based timestamping in the receive direction for delay measurements It also provides runtime display of delay statistics when two way delay measurement is triggered Ethernet frame delay measurement records the last 100 samples collected per remote maintenance end point MEP or per connectivity fault management CFM session You can retrieve the history at any time using simple commands You can clear all Ethernet frame delay measurement statistics and PDU counters Ethernet frame delay measurement is fully compliant with the ITU T Y 1731 OAM Functions and Mechanisms for Ethernet based Networks specification Ethernet frame delay measurement uses the IEEE 802 1ag CFM infrastructure An overview of the architecture established for Ethernet OAM is shown in Figure 18 on page 120 Generally Ethernet frame delay measurements are made in a peer fashion from one MEP or C
198. rm perfectly functional networks on their own at the frame level can be linked at the network layer and in fact that is one of the major functions of IP Devices that link LANs at the network layer are called routers and IP routers are the network nodes of the Internet Related MX Series Ethernet Services Routers Solutions Page Documentation Ethernet Terms and Acronyms on page 3 Network Addressing at Layer 2 and Layer 3 on page 7 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 Layer 2 Forwarding VLAN Tagged Frames on page 11 Networking at Layer 2 Forwarding Dual Tagged Frames on page 13 Networking at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15 Layer 2 Networking Standards on page 17 Network Addressing at Layer 2 and Layer 3 The Internet is a global public network with IP subnets connected by routers and exchanging packets Can a global public network consist of Ethernet LANs connected by bridges and exchanging frames Yes it can but there are several differences that must be addressed before Ethernet can function as effectively as IP in the metropolitan area Metro Ethernet let alone globally One of the key differences is the addresses used by Layer 2 frames and Layer 3 packets Both Ethernet and IP use globally unique network addresses that can
199. s A ring instance is responsible for the protection of a subset of VLANs that transport traffic over the physical ring When ring instances are configured for the ring each ring instance should have its own RPL owner an east and a west interface and a ring protection link end Each ring instance has a control channel and a specific data channel A data channel is a group of bridge domain VLAN IDs All VLAN IDs within the same ring interface share the same data forwarding properties controlled by the ERP If no data channel is defined in the ring configuration ERP will only operate on the physical link instead of as a ring instance using logical links When operating ERP in a topology with other protocols the following considerations should be observed Ifa physical interface is part of an Ethernet ring it cannot be configured for Spanning Tree Protocol STP or Multiple Spanning Tree Protocol MSTP ERP and Per VLAN Spanning Tree PVST can be configured on the same topology as long as PVST doesn t share the same VLAN with any Ethernet ring instance configured on the physical port If ERP is configured only as a physical ring instance a ring without a data channel in a topology also configured for PVST ERP checks the PYST configuration on two ring interfaces and automatically creates a data channel excluding VLANs used by PVST Ethernet Ring Protection on page 145 Example Configuring Ethernet Ring Protection for MX Serie
200. s Page D tati SELHMEN EP ON Layer 2 Features for a Switching Environment on page 39 Copyright 2010 Juniper Networks Inc 41 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide 42 Copyright 2010 Juniper Networks Inc CHAPTER 4 VLANS Within Bridge Domain and VPLS Environments 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 Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces on page 47 Example Configuring a Provider Bridge Network with Normalized VLAN Tags on page 47 Example Configuring a Provider VPLS Network with Normalized VLAN Tags on page 51 Example Configuring One VPLS Instance for Several VLANs on page 55 VLANs Within a Bridge Domain or VPLS Instance A packet received on a physical port is only accepted for processing if the VLAN tags of the received packet match the VLAN tags associated with one of the logical interfaces configured on the physical port The VLAN tags of the received packet are translated only if they are different than the normalized VLAN tags For the translation case the VLAN identifier tags specify the normalized VLAN For this case the terms learn VLAN and normalized VLAN can be used interchangeably You can specify the normalized VLAN using one of the following conditions Related Documentation
201. s Routers on page 148 Copyright 2010 Juniper Networks Inc 147 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Example Configuring Ethernet Ring Protection for MX Series Routers Example Topology 148 This example configures Ethernet ring protection for three MX Series router nodes Example Topology on page 148 Router 1 RPL Owner Configuration on page 149 Router 2 Configuration on page 150 Router 3 Configuration on page 152 The links connecting the three MX Series routers are shown in Figure 23 on page 148 Figure 23 Ethernet Ring Protection Example Nodes RPL Owner ge 1 2 4 AL ge 1 0 1 West q 7 East R APS Channel pg101 g016988 ge 1 0 4 ge 1 2 1 West West JD ge 1 0 3 ge 1 0 2 AL Ne ge East East ay pg103 pg1 02 This example uses the following topology details for Ethernet ring protection Router lis the RPL owner The node identification for Router 1 is MAC address 00 01 01 00 00 01 The RPL link is ge 1 0 1 1 this is also the R APS messaging control channel _ Traffic flows among the nodes in the configured bridge domains That is only the control channels are configured Router Vs east control channel interface is ge 1 0 1 1 the RPL and the west control channel interface is ge 1 2 4 1 The protection group is pg101 Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection Router 2 s east control channel interfac
202. s ge 2 0 5 unit O family bridge vlan id list 100 1000 set interfaces ge 2 1 1 unit O family bridge interface mode trunk set interfaces ge 2 1 1 unit O family bridge vlan id list 100 1000 set protocols protection group ethernet ring ring 1 east interface control channel ge 2 0 5 0 set protocols protection group ethernet ring ring 1 east interface control channel vlan 100 set protocols protection group ethernet ring ring 1 west interface control channel ge 2 1 1 0 set protocols protection group ethernet ring ring 1 west interface control channel vlan 100 set protocols protection group ethernet ring ring 1 data channel vlan 200 300 set protocols protection group ethernet ring ring 2 east interface control channel ge 2 0 5 0 set protocols protection group ethernet ring ring 2 east interface control channel vlan 101 set protocols protection group ethernet ring ring 2 west interface control channel ge 2 1 1 0 set protocols protection group ethernet ring ring 2 west interface control channel vlan 101 set protocols protection group ethernet ring ring 2 data channel vlan 500 600 set bridge domains bd100 vlan id 100 set bridge domains bd101 vlan id 101 set bridge domains bd200 vlan id 200 set bridge domains bd300 vlan id 300 set bridge domains bd500 vlan id 500 set bridge domains bd600 vlan id 600 Step by Step To configure ERP on ASI Procedure 1 Configure the trunk interface ge 2 0 5 to connect CS2 to CS1 and trunk interface ge 2 1 1 to con
203. s necessary Related MX Series Ethernet Services Routers Solutions Page Documentation 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 Benefits of Ethernet Frames on page 9 Networking at Layer 2 Challenges of Ethernet MAC Addresses on page 10 Networking at Layer 2 Forwarding VLAN Tagged Frames on page 11 Copyright 2010 Juniper Networks Inc 5 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Networking at Layer 2 Forwarding Dual Tagged Frames on page 13 Networking at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15 Layer 2 Networking Standards on page 17 Networking and Internetworking with Bridges and Routers Traditionally different hardware software and protocols have been used on LANs and on networks that cover wider areas national or global A LAN switch is different than a router an Ethernet frame is different than an IP packet and the methods used to find destination MAC addresses are different than those used to find destination IP addresses This is because LANs based on Ethernet were intended for different network environments than networks based on IP The Internet protocol suite TCP IP was intended as an internetworking method to connect local customer networks The local customer network that aservice provider s IP routers c
204. s to determine if there is a ring failure user as1 gt show protection group ethernet ring aps Ethernet Ring Name Request state No Flush Ring Protection Originator Remote Node ID Link Blocked Ring 1 NR No Yes No 00 21 59 03 ff d0 Ring 2 NR No Yes No 13 22 af 31 fc 00 Meaning Theoutput displayed shows that protection groups ring 1 and ring 2 have a Request state of NR meaning there is no request for APS on the ring If a Request state of SF is displayed it indicates there is a signal failure on the ring The output also shows that the ring protection link is not blocked The No Flush field displays No indicating that MAC addresses will be flushed when the ring nodes receive this message first time A value of Yes would indicate MAC address flushing is not needed The Originator field for ring 1 and ring 2 displays No indicating that this node is not the R APS originator Verifying the Data Channels on AS1 Purpose Verify the forwarding state of the data channel Action List the interfaces acting as the control channels and their respective data channels represented by the STP index number user as1 show protection group ethernet ring data channel Ethernet ring data channel parameters for protection group ring 1 Interface STP index Forward State ge 2 0 5 22 forwarding ge 2 1 1 23 forwarding Copyright 2010 Juniper Networks Inc 169 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Meaning Purpose
205. ses at the packet level Almost all ports links and devices on a network of LAN switches still have IP addresses just as do all the source and destination hosts There are many reasons for the continued need for IP not the least of which is the need to manage the network A device or link Without an IP address is usually invisible to most management applications Also utilities such as remote access for diagnostics file transfer of configurations and software and so on cannot run without IP addresses as well as MAC addresses MX Series Ethernet Services Routers Solutions Page Ethernet Terms and Acronyms on page 3 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 Challenges of Ethernet MAC Addresses on page 10 Networking at Layer 2 Forwarding VLAN Tagged Frames on page 11 Networking at Layer 2 Forwarding Dual Tagged Frames on page 13 Networking at Layer 2 Logical Interface Types on page 14 A Metro Ethernet Network with MX Series Routers on page 15 Layer 2 Networking Standards on page 17 Networking at Layer 2 Challenges of Ethernet MAC Addresses Related Documentation If a networked Layer 2 device such as a bridge or LAN switch could contain a list of all known MAC addresses then the network node could function in much the same way as a router forwarding frames instead of packets hop by hop through the network fr
206. sic Layer 2 Features on MX Series Routers 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 aggregated devices ethernet device count 2 Number of AE interfaces on router interfaces ge 2 1 0 1 gigether options 802 3ad ae2 interfaces ge 2 1 1 gigether options 802 3ad ae2 interfaces ge 2 1 2 1 gigether options 802 3ad ae2 interfaces ge 2 1 3 1 gigether options 802 3ad ael interfaces ge 2 1 4 gigether options 802 3ad ael interfaces ge 2 1 5 1 gigether options 802 3ad ael interfaces ge 2 2 1 encapsulation flexible ethernet services vlan tagging Customer interface uses singly tagged frames unit 100 encapsulation vlan bridge vlan id 100 unit 200 encapsulation vlan bridge vlan id 200 interfaces ge 2 2 2 1 unit O Copyright 2010 Juniper Networks Inc 25 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide family bridge interface mode access vlan id 205 interfaces ge 2 2 4 native vlan id 200 Untagged packets get vlan 200 tag unit O family bridge interface mode trunk vlan id list 200 205 This trunk port is part of VLAN range 200 205 interfaces ge 2 2 6 encapsulation flexible ethernet services vlan tagging Customer interface uses singly tagged frames unit 200
207. tection group ethernet ring ring 1 east interface ring protection link end set protocols protection group ethernet ring ring 1 west interface control channel ge 5 2 3 0 set protocols protection group ethernet ring ring 1 west interface control channel vlan 100 set protocols protection group ethernet ring ring 1 data channel vlan 200 300 set protocols protection group ethernet ring ring 2 east interface control channel ge 3 2 4 0 set protocols protection group ethernet ring ring 2 east interface control channel vlan 101 set protocols protection group ethernet ring ring 2 west interface control channel ge 5 2 3 0 set protocols protection group ethernet ring ring 2 west interface control channel vlan 101 set protocols protection group ethernet ring ring 2 data channel vlan 500 600 set routing instances vs instance type virtual switch set routing instances vs interface ge 3 2 4 0 set routing instances vs interface ge 5 2 3 0 set routing instances vs bridge domains bd101 vlan id 101 set routing instances vs bridge domains bd200 vlan id 200 Copyright 2010 Juniper Networks Inc 157 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide set routing instances vs bridge domains bd300 vlan id 300 set routing instances vs bridge domains bd500 vlan id 500 set routing instances vs bridge domains bd600 vlan id 600 Step by Step To configure ERP on CS1 Procedure 1 Configure the trunk interface ge 3 2 4 to connect CS1 to CS2 and the
208. th Dynamic Profiles Complex Solutions on page 68 Example Configuring VPLS Pseudowires with Dynamic Profiles Basic Solutions The following limitations apply to dynamic profiles for VPLS on MX Series routers The native vlan id statement is not supported The native inner vlan id statement is not supported The interface mode access statement option is not supported The vlan id range statement is not supported In many cases a configuration Using dynamic profiles is more efficient than a static configuration as shown by the examples in this topic VPLS Pseudowire Interfaces Without Dynamic Profiles on page 64 VPLS Pseudowire Interfaces and Dynamic Profiles on page 65 CE Routers Without Dynamic Profiles on page 66 CE Routers and Dynamic Profiles on page 67 VPLS Pseudowire Interfaces Without Dynamic Profiles 64 Consider the following configuration which does not use dynamic profiles to manipulate VLAN identifiers edit routing instances green instance type vpls interface ge 0 0 1 1 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 ge 0 0 1 unit O vlan id 10 ge 0 0 2 unit O Copyright 2010 Juniper Networks Inc Chapter 6 Dynamic Profiles for VLAN Interfaces and Protocols vlan id 20 ge 0 0 3 1 unit O vlan id 30 D NOTE This is not a
209. the properly configured firewall filter to an interface D NOTE You should deploy firewall filters carefully because it is easy to cause unforeseen side effects on all traffic especially traffic that is not the intended target of the filter For more information about configuring firewall filters see the Junos OS Policy Framework Configuration Guide Copyright 2010 Juniper Networks Inc 95 Junos 10 4 MX Series Ethernet Services Routers Solutions Guide Related Documentation MX Series Ethernet Services Routers Solutions Page Example Configuring Policing and Marking of Traffic Entering a VPLS Core on page 96 Example Configuring Filtering of Frames by MAC Address on page 98 Example Configuring Filtering of Frames by IEEE 802 1p Bits on page 99 Example Configuring Filtering of Frames by Packet Loss Priority on page 101 Example Configuring Policing and Marking of Traffic Entering a VPLS Core 96 This example firewall filter allows a service provider to limit the aggregate broadcast traffic entering the virtual private LAN service VPLS core The broadcast unknown unicast and non IP multicast traffic received from one of the service provider s customers on a logical interface has a policer applied The service provider has also configured a two rate three color policer to limit the customer s IP multicast traffic For more information on the configuration of policers see the Junos OS Class of Service Configuratio
210. tifier is already part of a VLAN identifier list in a bridge domain under a routing instance then you cannot configure an explicit bridge domain with that VLAN identifier In other words there can be no overlap between a VLAN identifier list and another VLAN identifier configuration The following example removes the VLAN identifier 5 from the original VLAN list vlan id list 1 10 and configures the bridge domain explicitly edit routing instance rtg inst 10 instance type virtual switch interface ge 7 3 0 0 60 Copyright 2010 Juniper Networks Inc Chapter 5 Bulk Administration of Layer 2 Features on MX Series Routers bridge domains bd vlan 5 vlan id 5 bd vlan id 1 4 6 10 If a VLAN identifier is already part of a VLAN identifier list in a bridge domain under a routing instance then you must delete the VLAN identifier from the list before you can configure an explicit or regular bridge domain Also the explicit bridge domain will not perform properly unless it has the same name as the bridge domain in the VLAN identifier list In other words if sales vlan 100 was part of a bridge domain VLAN list and you wish to configure it explicitly you must use the same naming convention edit bridge domains sales vlan 100 You must use this name explicitly vlan id 100 The following limitations apply to automatic bridge domain configuration Only one vlan id list statement is a
211. trunk interface ge 5 2 3 to connect CS to AS and configure the family statement as bridge with a VLAN ID list of 100 through 1000 edit interfaces user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 set ge 3 2 4 vlan tagging set ge 3 2 4 unit O family bridge interface mode trunk set ge 3 2 4 unit O family bridge vlan id list 100 1000 set ge 5 2 3 vlan tagging set ge 5 2 3 unit O family bridge interface mode trunk set ge 5 2 3 unit O family bridge vlan id list 100 1000 2 Enable ERP specifying the control channels and data channels for ring 1 and ring 2 and configure ring 1 as the ring protection link owner D NOTE Always configure the east interface statement first before configuring the west interface statement edit protection group user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 user cs1 set ethernet ring ring 1 ring protection link owner set ethernet ring ring 1 east interface control channel ge 3 2 4 0 set ethernet ring ring 1 east interface control channel vlan 100 set ethernet ring ring 1 east interface ring protection link end set ethernet ring ring 1 west interface control channel ge 5 2 3 0 set ethernet ring ring 1 west interface control channel vlan 100 set ethernet ring ring 1 data channel vlan 200 300 set ethernet ring ring 2 east interface control channel ge 3 2 4 0 set ethernet ring ring 2 east interface control channel
212. twork The network is shown in Figure 16 on page 112 The customer has configured Ethernet CFM on MX Series routers L2 CE and L2 CE2 The service provider has configured Ethernet CFM on MX Series routers PE and PE2 D NOTE The configurations in this example are only partial examples of complete and functional router configurations Do not copy these configurations and use them directly on an actual system The service provider is using CFM level 3 for the link between PE and PE2 and level 5 from one CE facing port to the other The customer is using CFM level 7 The boundaries are marked with Up mep and down mep CFM terminology in the figure Figure 16 Ethernet CFM over a Bridge Network Customer domain i Provider domain a l l l l ge 5 1 7 e VLAN 2000 i PE2 VLAN 2000 ge 5 1 7 Ne Vol l Provider level 3 CFM Vv og l l Provider level 5 CFM TT Customer level 7 CFM A Up mes A Down mep Vv 112 Copyright 2010 Juniper Networks Inc Chapter 10 IEEE 802 1ag OAM Connectivity Fault Management Here are the configurations of CFM on the customer routers CFM on L2 CEI edit interfaces ge 0 2 9 1 vlan tagging unit O vlan id 2000 edit protoccols oam ethernet connectivity fault management maintenance domain customer level 7 maintenance association customer sitel continuity check interval Is mep 700 interface ge 0 2
213. twork type Also loosely called the MAC layer technically the MAC layer is a sublayer required only on LANs Layer 2 sends and receives frames Frames are the last things that bits were before they left the sender and the first things that bits become when they arrive on an interface Because frames have a defined structure unlike bits frames can be used for error detection control plane activities not all frames must carry user data some frames are used by the network to control the link and so forth LAN segments can be linked at the frame level and these devices are called bridges Bridges examine arriving frames and decide whether to forward them on an interface All bridges today are called learning bridges because they can find out more about the network than 6 Copyright 2010 Juniper Networks Inc Chapter 1 Overview of Ethernet Solutions could older bridges that were less intelligent devices Bridges learn much about the LAN segments they connect to from protocols like those in the Spanning Tree Protocol STP family The network layer Layer 3 is the highest layer used by network nodes to forward traffic as part of the data plane On the Internet the network layer is the IP layer and can run either IPv4 or IPV6 which are independent implementations of the same functions The IP layer defines the structure and purpose of the packet which is in turn the content of the frame at Layer 2 As expected LAN segments which now fo
214. use packets to detect and prevent routing loops bridges use xSTP frames to detect and prevent bridging loops Layer 2 loops are more devastating to a network because of the broadcast nature of Ethernet LANs Integrated bridging and routing IRB Support for both Layer 2 bridging and Layer 3 routing on the same interface Frames are bridged if they are not sent to the router s MAC address Frames sent to the router s MAC address are routed to other interfaces configured for Layer 3 routing MX Series Ethernet Services Routers Solutions Page Example Roadmap Configuring a Basic Bridge Domain Environment on page 22 Example Step Configuring Interfaces and VLAN Tags on page 24 Example Step Configuring Bridge Domains on page 30 Example Step Configuring Spanning Tree Protocols on page 32 Example Step Configuring Integrated Bridging and Routing on page 34 Example Roadmap Configuring a Basic Bridge Domain Environment Example Topology 22 Configuring Layer 2 features on MX Series routers can vary from the very simple aggregated Ethernet trunk interfaces spanning trees to the more complex inner and outer VLAN tags broadcast domains to the very complicated integrated bridging and routing Layer 2 filtering This example offers a fairly complex configuration for Layer 2 processing in a bridged environment Example Topology on page 22 Example Scenario on page 23 Example Configuration Summary on page 24 Consider the network in
215. use this guide you need a broad understanding of networks in general the Internet in particular networking principles and network configuration You must also be familiar with one or more of the following Internet routing protocols Border Gateway Protocol BGP Distance Vector Multicast Routing Protocol DVMRP Intermediate System to Intermediate System IS IS Internet Control Message Protocol ICMP router discovery Internet Group Management Protocol IGMP Multiprotocol Label Switching MPLS Open Shortest Path First OSPF Protocol Independent Multicast PIM Resource Reservation Protocol RSVP Routing Information Protocol RIP Simple Network Management Protocol SNMP Personnel operating the equipment must be trained and competent must not conduct themselves in a careless willfully negligent or hostile manner and must abide by the instructions provided by the documentation Copyright 2010 Juniper Networks Inc About This Guide Supported Routing Platforms For the Layer 2 features described in this manual the Junos OS currently supports the following routing platforms Juniper Networks MX Series Ethernet Services Routers Using the Indexes This reference contains a standard index with topic entries Using the Examples in This Manual If you want to use the examples in this manual you can use the load merge or the load merge relative command These commands cause the software
216. viding network protection from link failure Requirements on page 154 Overview and Topology on page 154 Configuration on page 157 e Verification on page 166 This example uses the following hardware and software components Two MX Series routers acting as core switches One MX Series router acting as an aggregation switch Junos OS Release 10 2 or later for MX Series routers Overview and Topology 154 Figure 24 on page 155 displays the topology for this example The topology contains three MX Series routers CS1 and CS2 act as core routers in the topology and AS acts as an aggregation switch Each router has two ring instances ring 1 and ring 2 All nodes on the ring coordinate protection activities by exchanging messages through the Ethernet ring automatic protection switching R APS messaging protocol Each ring instance has Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection an RPL owner The ring 1 RPL owner is CS1 the ring 2 RPL owner is CS2 The RPL owners block or unblock the RPL as conditions require and initiate R APS messages Each ring instance has two interface ports an east interface and a west interface that participate in the instance Interface ge 2 0 8 0 the west interface on CS2 is the ring protection link end where ring 2 s RPL terminates Interface ge 3 2 4 0 the east interface on CS is the ring protection link end where ring 1 s RPL terminates Each ring
217. vlan 200 300 set protocols protection group ethernet ring ring 2 ring protection link owner set protocols protection group ethernet ring ring 2 east interface control channel ge 2 0 4 0 set protocols protection group ethernet ring ring 2 east interface control channel vlan 101 set protocols protection group ethernet ring ring 2 west interface control channel ge 2 0 8 0 set protocols protection group ethernet ring ring 2 west interface ring protection link end set protocols protection group ethernet ring ring 2 west interface control channel vlan 101 set protocols protection group ethernet ring ring 2 data channel vlan 500 600 set bridge domains bd100 vlan id 100 set bridge domains bd101 vlan id 101 Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection set bridge domains bd200 vlan id 200 set bridge domains bd300 vlan id 300 set bridge domains bd500 vlan id 500 set bridge domains bd600 vlan id 600 Step by Step To configure ERP on CS2 Procedure 1 Configure the trunk interface ge 2 0 4 to connect CS2 to CS1 and trunk interface ge 2 0 8 to connect CS2 to CS1 and configure the family statement as bridge with a VLAN ID list of 100 through 1000 edit interfaces user cs2 user cs2 user cs2 user cs2 set ge 2 0 4 unit O family bridge interface mode trunk set ge 2 0 4 unit O family bridge vlan id list 100 1000 set ge 2 0 8 unit O family bridge interface mode trunk set ge 2 0 8 unit O family bridge
218. ward State shows whether the data channel is forwarding or discarding traffic Verifying the VLANs on CS2 Verify the data channel logical interfaces and the VLAN IDs controlled by a ring instance data channel List dynamic VLAN membership user cs2 gt show protection group ethernet ring vlan Ethernet ring IFBD parameters for protection group ring 1 Interface Vian STP Index Bridge Domain ge 2 0 4 200 44 default switch bd200 ge 2 0 8 200 45 default switch bd200 Copyright 2010 Juniper Networks Inc Chapter 13 Ethernet Ring Protection ge 2 0 4 300 44 default switch bd300 ge 2 0 8 300 45 default switch bd300 Ethernet ring IFBD parameters for protection group ring 2 Interface Vlan STP Index Bridge Domain ge 2 0 4 500 46 default switch bd500 ge 2 0 8 500 47 default switch bd500 ge 2 0 4 600 46 default switch bd600 ge 2 0 8 600 47 default switch bd600 Meaning The output displayed shows the ring interfaces ge 2 0 4 and ge 2 0 8 in protection groups ring 1 and ring 2 For ring 1 VLAN 200 and VLAN 300 are being supported on both STP Index 44 and 45 on bridge domains bd200 and bd300 For ring 2 VLAN 500 and VLAN 600 are being supported on both STP Index 46 and 47 on bridge domains bd500 and bd600 The data channel controls the traffic on the VLAN IDs to facilitate load balancing Verifying the Ethernet Protection Ring on AS1 Purpose Verify that ERP is enabled on ASI Action Show the status of the ring APS R APS message
219. ware and another independently created program on payment of applicable fee if any Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable terms and conditions upon which Juniper makes such information available 14 Third Party Software Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products or technology are embedded in or services are accessed by the Software shall be a third party beneficiary with respect to this Agreement and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper In addition certain third party software may be provided with the Software and is subject to the accompanying license s if any of its respective owner s To the extent portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such portions publicly available such as the GNU General Public License GPL or the GNU Library General Public License LGPL Juniper will make such source code portions including Juniper modifications as appropriate available upon request for a period of up to three years from the date of distribution Such request can be made in writing to Juniper Networks Inc 1194 N Mathilda Ave Sunnyvale CA 94089 ATTN General Counsel You may obtain a copy
220. y on to a server while the router appears to reply to the client You can configure a Juniper Networks MX Series Ethernet Services Router to act as a DHCP relay agent The MX Series router configuration at Layer 2 accesses the Layer 3 information with DHCP snooping DHCP servers and relay agents have a level of trust in the MAC addresses used in DHCP client queries A hacker can spoof invalid MAC addresses and overwhelm the server or relay agent with flooded traffic Or the hacker can try to determine other information such as the IP address range used by devices on the network The DHCP process should only trust MAC addresses that are valid for a particular network You can configure the MX Series router to use MAC addresses obtained by the Layer 2 address learning process to control the flooding of DHCP packets Several restrictions apply to DHCP configuration on the MX Series routers All statements referring to option 82 including circuit information in DHCP relay messages are not supported on the MX Series routers This feature works for static IP MAC bindings on the MX Series routers The DHCP snooping database table is not restored after a Routing Engine reboot The DHCP Discover message is not flooded to the DHCP server when broadband service aggregator BSA and broadband service router BSR are provisioned on the same switch For more information on configuring DHCP see the Junos OS Subscriber Access Configuration

Download Pdf Manuals

Related Search

Related Contents

MANUAL DE OPERAÇÃO E MANUTENÇÃO DE ESTAÇÃO  Bomba dosificadora magnética - delta® DLTa  COMUNE DI PALERMO PIANO DI SICUREZZA E  Catalistino EYEON 3/2012 - tec security applications  User Manual  Samsung Електрична духова шафа PREZIO-2Cov із подвійною системою готування (подвійною конвекцією), 65 л Керівництво користувача  Alcatel OneTouch 318D Owner's Manual  Westinghouse A19 Specification Sheet  Lien vers les documents  Platinum Remote Control  

Copyright © All rights reserved. Failed to retrieve file