Juniper Networks 10.4 - Manuals

Chapter 3 Virtual Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Layer 2 Features for a Switching Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Configuring Virtual Switches as Separate Routing Instances . . . . ...

Part 3 Ethernet Filtering, Monitoring, and Fault Management Solutionsfor MX Series Routers Chapter 9 Layer 2 Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Firewall Filters for Bridge Domains and VPLS Instances . . . . . . . . . . . . . ...

Part 4 Index Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Copyright © 2010, Juniper Networks, Inc. xii Junos 10.4 MX Series Ethernet Services Routers Solutions Guide

List of Figures Part 1 Overview Chapter 1 Overview of Ethernet Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Figure 1: Native (Normal) and VLAN-Tagged Ethernet Fames . . . . . . . . . . . . . . . . 12Figure 2: A Metro Ethernet Network . . . . . . . . . . . ....

List of Tables About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiTable 2: Text and Syntax Conventions . . ....

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 th...

Objectives This guide provides an overview of the Layer 2 features of the Junos OS and describeshow to configure the features to provide solutions to several network scenarios. NOTE: For additional information about Junos OS—either corrections to or information that might have been omitted from this...

Supported Routing Platforms For the Layer 2 features described in this manual, the Junos OS currently supports thefollowing 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 T...

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, ...

Table 2: Text and Syntax Conventions (continued) Examples Description Convention broadcast | multicast ( string1 | string2 | string3 ) Indicates a choice between the mutuallyexclusive keywords or variables on eitherside of the symbol. The set of choices isoften enclosed in parentheses for clarity. |...

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

CHAPTER 1 Overview 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: Challenge...

• 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, ...

could older bridges that were less intelligent devices. Bridges learn much about the LANsegments 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 trafficas part of the data plane. On...

Related Documentation MX Series Ethernet Services Routers Solutions Page • • 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 Ad...

NOTE: Networking at the frame level says nothing about the presence or absence of IP addresses at the packet level. Almost all ports, links, and deviceson a network of LAN switches still have IP addresses, just as do all the sourceand destination hosts. There are many reasons for the continued need ...

• 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 Rou...

Networking at Layer 2: Forwarding Dual-Tagged Frames The use of VLAN tagging to group (or bundle) sets of MAC addresses is a start towarda method of forwarding LAN traffic based on information found in the frame, not on IPaddress in the packet. However, there is a major limitation in trying to build...

• 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 T...

A Metro Ethernet Network with MX Series Routers What would a Metro Ethernet network with Juniper Networks MX Series Ethernet ServicesRouters look like? It is very likely that the Metro Ethernet network will place MX Seriesrouters at the edge of a VPLS and MPLS core network. The VLAN labels in the pa...

• 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 T...

PART 2 Basic Solutions for MX Series Routers • Basic Layer 2 Features on MX Series Routers on page 21 • 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 Inte...

CHAPTER 2 Basic Layer 2 Features on MX SeriesRouters • 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...

• Spanning Tree Protocols (xSTP, where the “x” represents the STP type)—Bridgesfunction by associating a MAC address with an interface, similar to the way a routerassociates an IP network address with a next-hop interface. Just as routing protocolsuse packets to detect and prevent routing loops, bri...

• Router 2 and Router 3 have IRB configured so that they can pass traffic to other routersin the rest of the network. • Router 1 has an access interface which provides bridging on VLAN 205 and is connectedto a customer device configured on ge-2/2/2 . Router 3 has an access interface which provides b...

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 { gigether-options { 802.3ad ae2; } }i...

family bridge { interface-mode access;vlan-id 205; } } }interfaces ge-2/2/4 { native-vlan-id 200; # Untagged packets get vlan 200 tagunit 0 { family bridge { 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-e...

vlan-id 100; }unit 200 { vlan-id 200; } } 3. Configure the Ethernet interfaces and VLAN tags on Router 3: [edit]chassis { aggregated-devices { ethernet { device-count 2; # Number of AE interfaces on router } } }interfaces ge-2/2/2 { encapsulation flexible-etherent-services;vlan-tagging; # Customer i...

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 { vlan100 { domain-type bridge;vlan-id 100;interface ge-2/2/1.100;interface ae1.100; }vlan200 { domain-type bridge;vlan-id 200;interface ge-2/...

Example Step: Configuring Spanning Tree Protocols Configure the Spanning Tree Protocol on all three routers. This is necessary to avoid thepotential bridging loop formed by the triangular architecture of the routers. MSTP isconfigured on the three routers so the set of VLANs has an independent, loop...

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 matchinterface ae2;interface ae3;msti 1 { vlan100; # This VLAN corresponds to MSTP instance 1 }msti 2 { vlan200; # ...

Figure 6: Designated, Root, and Alternate Ports Related Documentation 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 V...

interface ae1.100;interface ae3.100routing-interface irb.0; }vlan-200 { domain-type bridge;vlan-id 200;interface ge-3/3/3.200;interface ae1.200;interface ae3.200routing-interface irb.1; } } 2. Configure the router link and IRB on Router 3: [edit]interfaces { xe-1/1/0 { unit 0 { family inet { address...

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 Ethernetcapabilities as ...

• 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 Seriesrouter with bridge domains and VLANs. Before you begin, you should have already confi...

CHAPTER 4 VLANs Within Bridge Domain and VPLSEnvironments • 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 ...

• 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 strictsequence of steps. Packets received over a Layer 2 logical interface for bridging ...

Configuring a Normalized VLAN for Translation or Tagging This topic provides configuration and operational information to help you manipulatevirtual 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...

Then, the source MAC address of a received packet is learned based on the normalizedVLAN configuration. For output packets, if the VLAN tags associated with an egress logical interface do notmatch the normalized VLAN tags within the packet, then appropriate VLAN tag operations(such as push-push, pop...

NOTE: This topic does not present exhaustive configuration listings for all routers in the figures. However, you can use it with a broader configurationstrategy to complete the MX Series router network configurations. Consider the provider bridge network shown in Figure 7 on page 48. Figure 7: Provi...

For more information about configuring Ethernet pseudowires as part of VPLS, see the Junos OS Feature Guide . NOTE: This topic does not present exhaustive configuration listings for all routers in the figures. However, you can use it with a broader configurationstrategy to complete the MX Series rou...

encapsulation vlan-vpls;vlan-id 302; } }routing-instances { customer-c1-vsi { instance-type vpls;vlan-id 100;interface ge-1/0/0.1;interface ge-2/0/0.1;interface ge-3/0/0.1; } # End of customer-c1-vsicustomer-c2-vsi { instance-type vpls;vlan-id none; # This will remove the VLAN tags from packets sent...

The following happens on the C2 VLAN as a result of the vlan-id none configuration: • A MAC 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 receivedor configured VLAN tags are not consider...

Figure 9: Many VLANs on One VPLS Instance The Layer 2 PE routers are MX Series routers. Each site is connected to two P routers forredundancy, although both links are only shown for L2-PE1 at Site 1. Site 1 is connectedto P0 and P1, Site 2 is connected to P0 and P2 (not shown), Site 3 is connected t...

CHAPTER 5 Bulk Administration of Layer 2 Featureson 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...

The following example translates incoming trunk packets from VLAN identifier 200 to500 and 201 to 501 (other valid VLAN identifiers are not affected): [edit interfaces ge-1/0/1]unit 0 { ... # Other logical interface statementsfamily bridge { interface-mode trunk # Translation is only for trunksvlan-...

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 arouting instance, then you must delete the VLAN identifier from the list before you canconfigure an explicit or “regular” bridge domain. Al...

CHAPTER 6 Dynamic Profiles for VLAN Interfaces andProtocols • Dynamic Profiles for VPLS Pseudowires on page 63 • Example: Configuring VPLS Pseudowires with Dynamic Profiles—BasicSolutions on page 64 • Example: Configuring VPLS Pseudowires with Dynamic Profiles—ComplexSolutions on page 68 Dynamic Pro...

• Example: Configuring VPLS Pseudowires with Dynamic Profiles—Basic Solutions onpage 64 • Example: Configuring VPLS Pseudowires with Dynamic Profiles—Complex Solutionson page 68 Example: Configuring VPLS Pseudowires with Dynamic Profiles—Basic Solutions The following limitations apply to dynamic pro...

vlan-id 20; } }ge-0/0/3 { unit 0 { vlan-id 30; } } NOTE: This is not a complete router configuration. With this configuration, broadcast packets inside frames arriving with VLAN identifier 10on ge-0/0/ 1 are normalized to a dual-tagged frame with an outer VLAN value of 200 and an inner VLAN value of...

}ge-0/0/3 { unit 0 { 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: This is not a complete router configuration. With this configuration, broadcast packets inside frames arriv...

} }ge-0/0/3 { unit 0 { vlan-id 100; } } 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 VLANvalue of 100. The same configuration can be ...

vlan-tags outer 200 inner 100; } } NOTE: This is not a complete router configuration. With this configuration, broadcast packets inside frames arriving with VLAN identifier100 on ge-0/0/ 1 are normalized to a frame with VLAN identifier 100 (in this case, they are unchanged). The broadcast packet and...

NOTE: This is not a complete router configuration. In this case, frames arriving on the interfaces are classified according to their bridgedomains and switched, if necessary, to the VPLS pseudowire trunk, except for Engineeringframes. Engineering frames (VLAN 30) are only switched within the interfa...

Configuration of Tag Translation Using Dynamic Profiles Consider a final case where the bridge domain VLANs need translation at the VPLSpseudowire 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 transla...

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 in a VPLS Routing Instance Environment on page 75 MX Series Router as a Laye...

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 vs1 bridge-domains bd1 • show dhcp relay binding routing-instance vs1 bridge-domains bd1 detail user@router1> show dhcp relay binding rout...

CHAPTER 8 MX Series Router in an ATM EthernetInterworking Function • MX Series Router ATM Ethernet Interworking Function on 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 a...

Example: Configuring MX Series Router ATM Ethernet Interworking Consider the router topology shown in Figure 13 on page 79. The MX Series router isconfigured as the Provider Edge 2 (PE2) router in the figure to support the ATM EthernetIWF. Figure 13: ATM Ethernet VLAN Interworking CE1 CE2 g017428 AT...

vlan-tags outer 100 inner 34;family inet { address30.1.1.10/24; } } } } You verify your configuration on the MX Series router with the show l2circuit connections command: user@PE2> show l2circuit connections Layer-2 Circuit Connections: Legend for connection status (St) EI -- encapsulation invali...

} } } } You verify your configuration on the MX Series router with the show l2circuit connections command: user@PE2> 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 ...

}ge-0/2/8 { unit 0 { 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 lsp1-2 { from 10.255.171.45;to 10.255.171.14; }interface ge-0/2/8.0; }isis { in...

unit 0 { 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/...

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 Frame...

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 pag...

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 { filter { input customer-1; } } } } Related Documentation MX Series Ethern...

count evil-mac-address; # Counts frame with the bad source MAC addressdiscard; }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 { doma...

• 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 losspriority (PLP) level carried in the frame, use the loss-priority or l...

CHAPTER 10 IEEE 802.1ag OAM Connectivity-FaultManagement • 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 ...

• Fault isolation, verification, and recovery (isolation and verification are provided by acombination of protocols, while recovery is the function of protocols such as spanningtree) The loopback protocol used in Ethernet OAM is modeled on the standard IP ping. Aftera fault is detected, the loopback...

maintenance domain, each service instance is called a maintenance association. Amaintenance association can be thought as a full mesh of maintenance endpoints (MEPs)having similar characteristics. MEPs are active CFM entities generating and respondingto CFM protocol messages. There is also a mainten...

Figure 15: Ethernet OAM with VPLS The following are the configurations of the VPLS and CFM on the service provider routers. Configuration of PE1 [edit chassis]fpc 5 { pic 0 { tunnel-services { bandwidth 1g; } } } [edit interfaces]ge-1/0/7 { encapsulation flexible-ethernet-services;vlan-tagging;unit ...

interval 1s; }mep 100 { interface ge-1/0/7.1;direction up;auto-discovery; } } } } } } Configuration of PE2 [edit chassis]fpc 5 { pic 0 { tunnel-services { bandwidth 1g; } } } [edit interfaces]ge-5/0/9 { vlan-tagging;encapsulation flexible-ethernet-services;unit 1 { encapsulation vlan-vpls;vlan-id 20...

interface fxp0.0 { disable; }interface ge-0/1/0.0;interface ge-5/2/7.0; } } } CFM on L2-CE1 Here is the configuration of CFM on L2-E1: [edit interfaces]ge-5/2/3 { vlan-tagging;unit 0 { vlan-id 2000; } } [edit protocols oam]ethernet { connectivity-fault-management { maintenance-domain customer { leve...

interval 1s; }mep 700 { interface ge-0/2/9.0;direction down;auto-discovery; } } } } } Related Documentation MX Series Ethernet Services Routers Solutions Page • • Ethernet Operations, Administration, and Maintenance on page 103 • Ethernet OAM Connectivity Fault Management on page 104 • Example: Conf...

vlan-tagging;encapsulation flexible-ethernet-services;unit 0 { encapsulation vlan-bridge;vlan-id 2000; } }ge-5/1/7 { vlan-tagging;encapsulation flexible-ethernet-services;unit 0 { encapsulation vlan-bridge;vlan-id 2000; } } [edit bridge-domains]bridge-vlan2000 { domain-type bridge;vlan-id 2000;inter...

• Example: Configuring Ethernet CFM over VPLS on page 105 • Example: Configuring Ethernet CFM on Physical Interfaces on page 116 Example: Configuring Ethernet CFM on Physical Interfaces CFM can be used to monitor the physical link between two routers. This functionality issimilar to that supported b...

CHAPTER 11 ITU-T Y.1731 Ethernet Frame DelayMeasurements • 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 Measurem...

delay measurement provides fine control to operators for triggering delay measurementon a given service and can be used to monitor Service Level Agreements (SLAs). Ethernet frame delay measurement also collects other useful information, such as worstand best case delays, average delay, and average d...

For two-way (round-trip) Ethernet frame delay measurement, either MEP can send arequest to begin a two-way delay measurement to its peer MEP, which responds withtimestamp information. Run-time statistics are collected and displayed at the initiatorMEP. The clocks do not need to be synchronized at th...

To perform Ethernet frame delay measurement, make sure that the followingconfiguration statement is NOT present: [edit routing-options]ppm { no-delegate-processing; # This turns distributed PPMD OFF. } Related Documentation MX Series Ethernet Services Routers Solutions Page • • Ethernet Frame Delay ...

Table 3: Monitor Ethernet Delay Command Parameters (continued) Description Parameter Range Parameter (Optional) Specifies the number of seconds to wait between frames. Thedefault is 1 second. 1–255 seconds(default: 1) wait time If you attempt to monitor delays to a nonexistent MAC address, you must ...

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 Description Parameter Range Parameter Specifies an existing maintenance dom...

Statistics: CCMs sent : 1590 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 :...

} } }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; ...

}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-1 , start a two-way delay measurement to Router MX-2 . user@MX-1> monitor ethernet delay-m...

CHAPTER 12 IEEE 802.3ah OAM Link-FaultManagement • 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 • Exampl...

Example: Configuring Ethernet LFM Between PE and CE In this example, LFM is enabled on an IP link between the provider edge (PE) and customeredge (CE) interfaces. If the link goes down, the fault will be detected by LFM and theinterfaces on both sides will be marked Link-Layer-Down . This results in...

link-fault-management { interface ge-1/1/0 { pdu-interval 1000;pdu-threshold 5; } } } } } Related Documentation 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 Etherne...

pdu-threshold 5; } } } } } 2. Configure LFM on the PE2 router with CCC: [edit]interfaces ge-1/0/0 { encapsulation ethernet-ccc;unit 0; }protocols { oam { ethernet { link-fault-management { interface ge-1/0/0 { pdu-interval 1000;pdu-threshold 5; } } } } } Related Documentation MX Series Ethernet Serv...

802.3ad ae0; } }interfaces ae0 { unit 0 { family inet { address 11.11.11.1/24; } } }protocols { oam { ethernet { link-fault-management { interface ae0; } } } } Related Documentation MX Series Ethernet Services Routers Solutions Page • • Ethernet OAM Link Fault Management on page 137 • Example: Confi...

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 Prote...

• Router 2’s east control channel interface 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 i...

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 { default-action { interface-down; } }maintenance-domain d1 { level 0;...

level 0;maintenance-association 100 { mep 2 { interface ge-1/2/1;remote-mep 1 { action-profile rmep-defaults; } } } }maintenance-domain d3 { level 0;maintenance-association 100 { mep 1 { interface ge-1/0/2;remote-mep 2 { action-profile rmep-defaults; } } } } } } } } Router 3 Configuration To configu...

} } } 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: ...

Table 5: Components of the Network Topology Settings Property • ring-1 —Data channel [200,300] • ring-2 —Data channel [500,600] Ring instances Two customer sites are connected to AS 1: • Customer site 1, VLAN 200 and VLAN 300 • Customer site 2, VLAN 500 and VLAN 600 Customer sites CS1 has the follow...

Table 5: Components of the Network Topology (continued) Settings Property AS1 has the following protection group properties: • East interface— ge-2/0/5.0 . • West interface— ge-2/1/ 1.0 . • Data channel for ring-1 — VLAN 200 , VLAN 300 . • Data channel for ring-2 — VLAN 500 , VLAN 600 . AS1 has the ...

set routing-instances vs bridge-domains bd300 vlan-id 300set routing-instances vs bridge-domains bd500 vlan-id 500set routing-instances vs bridge-domains bd600 vlan-id 600 Step-by-Step Procedure To configure ERP on CS1: Configure the trunk interface ge-3/2/4 to connect CS1 to CS2 and the trunk inter...

} } } }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 CLI Quick Config...

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 Configuration To quickly configure AS1 for ERP, copy the following commands and paste them into theswitch terminal window of AS1: [edit] set interfaces ...

Verification To confirm that the ERP configuration for multiple ring instances is operating, performthese 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 ...

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 each interface in ring instances ring-1 and ring-2 . The STP ind...

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 Domainge-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 def...

Ethernet ring data channel parameters for protection group ring-2 Interface STP index Forward Statege-2/0/5 24 forwarding ge-2/1/1 25 forwarding Meaning 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 ...

Example: Viewing Ethernet Ring Protection Status—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 thefollowing: Router 1 Operational Commands (Normal Ri...

Router 3 will see almost identical information. user@router2> 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 forwarding No...

Originator Remote Node IDNo 00:01:02:00:00:01 Note that the ring protection link is no longer blocked and the node is no longer markedas originator. user@router1> show protection-group ethernet-ring interface Ethernet ring port parameters for protection group pg101 Interface Control Channel Forwa...

Index Symbols #, comments in configuration statements..................xxii( ), in syntax descriptions...................................................xxii< >, in syntax descriptions...................................................xxi[ ], in configuration statements...........................