® Junos OS MX Series Ethernet Services Routers Solutions Guide Release 10.4 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.
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.
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 Softwa
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 227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable. 13. Interface Information.
vi Copyright © 2010, Juniper Networks, Inc.
Abbreviated Table of Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Part 1 Overview Chapter 1 Overview of Ethernet Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Part 2 Basic Solutions for MX Series Routers Chapter 2 Basic Layer 2 Features on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Chapter 3 Virtual Switches . . . . . . . . . . . . . . . . . .
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide viii Copyright © 2010, Juniper Networks, Inc.
Table of Contents About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Junos Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Chapter 3 Virtual Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Layer 2 Features for a Switching Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Configuring Virtual Switches as Separate Routing Instances . . . . . . . . . . . . . . . . 40 Chapter 4 VLANs Within Bridge Domain and VPLS Environments . . . . . . . . . . . . . . . .
Table of Contents Part 3 Ethernet Filtering, Monitoring, and Fault Management Solutions for MX Series Routers Chapter 9 Layer 2 Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . .
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Part 4 Index Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 xii Copyright © 2010, Juniper Networks, Inc.
List of Figures Part 1 Overview Chapter 1 Overview of Ethernet Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Figure 1: Native (Normal) and VLAN-Tagged Ethernet Fames . . . . . . . . . . . . . . . . 12 Figure 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 . . . . . .
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Figure 22: Ethernet LFM with Loopback Support . . . . . . . . . . . . . . . . . . . . . . . . . 142 Chapter 13 Ethernet Ring Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Figure 23: Ethernet Ring Protection Example Nodes . . . . . . . . . . . . . . . . . . . . . . 148 Figure 24: ERP with Multiple Protection Instances Configured on Three MX Series Routers . . . . . . . . . . . . . . . . . .
List of Tables About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi Part 3 Ethernet Filtering, Monitoring, and Fault Management Solutions for MX Series Routers Chapter 11 ITU-T Y.
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 Jun
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Objectives 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. 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/.
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.
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 configuration snippet into a text file, save the file with a name, and copy the file to a directory on your routing platform.
About This Guide Table 1: Notice Icons Icon Meaning Description Informational note 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 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Table 2: Text and Syntax Conventions (continued) Convention Description Examples | (pipe symbol) 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. broadcast | multicast # (pound sign) Indicates a comment specified on the same line as the configuration statement to which it applies.
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/ .
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 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: 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:
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 4 • 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. As in a virtual LAN, a bridge domain spans one or more ports of multiple devices.
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.1ad. • PBBN—Provider backbone bridged network.
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).
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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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.
Chapter 1: Overview of Ethernet Solutions 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 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 •
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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 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.
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
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Figure 1: Native (Normal) and VLAN-Tagged Ethernet Fames 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.1Q (formerly IEEE 802.1q) specification. Together, the four added bytes form the VLAN tag, but the individual fields that comprise it are more important.
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.
Junos 10.
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 core network. The VLAN labels in the packet are stacked with MPLS labels, as shown in Figure 2 on page 15.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Figure 3: A Metro Ethernet Network with MX Series Routers In Figure 3 on page 16, the circled numbers reflect the different formats that the Ethernet frames can take as the frames 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.
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 • La
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 18 • 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 Copyright © 2010, Juniper Networks, Inc.
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 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
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 use packets to detect and prevent routing loops, bridges use xSTP frames to detect and prevent bridging loops.
Chapter 2: Basic Layer 2 Features on MX Series Routers Figure 5: Bridging Network with MX Series Routers 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.
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 1 has 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.
Chapter 2: Basic 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 { gigether-options { 802.3ad ae2; } } interfaces ge-2/1/1 { gigether-options { 802.3ad ae2; } } interfaces ge-2/1/2 { gigether-options { 802.
Junos 10.
Chapter 2: Basic Layer 2 Features on MX Series Routers encapsulation vlan-bridge; vlan-id 100; } } interfaces ge-3/3/3 { encapsulation flexible-ethernet-services; vlan-tagging; # Customer interface uses singly-tagged frames unit 200 { encapsulation vlan-bridge; vlan-id 200; } } interfaces ge-5/1/0 { gigether-options { 802.3ad ae3; } } interfaces ge-5/1/1 { gigether-options { 802.3ad ae3; } } interfaces ge-5/1/2 { gigether-options { 802.3ad ae3; } } interfaces ge-5/1/3 { gigether-options { 802.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide vlan-id 100; } unit 200 { vlan-id 200; } } 3.
Chapter 2: Basic Layer 2 Features on MX Series Routers 802.3ad ae3; } } interfaces ge-11/1/2 { gigether-options { 802.3ad ae3; } } interfaces ge-11/1/3 { gigether-options { 802.3ad ae2; } } interfaces ge-11/1/4 { gigether-options { 802.3ad ae2; } } interfaces ge-11/1/5 { gigether-options { 802.
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 { 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/2/1.200; interface ge-2/2/6.200; interface ae1.
Chapter 2: Basic Layer 2 Features on MX Series Routers domain-type bridge; vlan-id 200; interface ge-3/3/3.200; interface ae1.200; interface ae3.200; } } 3. Configure a bridge domain on Router 3: [edit] bridge-domains { vlan100 { domain-type bridge; vlan-id 100; interface ge-2/2/2.100; interface ae3.100; } vlan200 { domain-type bridge; vlan-id 200; interface ge-3/3/3.200; interface ae3.
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. 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.
Chapter 2: Basic Layer 2 Features on MX Series Routers 3.
Junos 10.
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 address database. NOTE: You configure IRB on Router 2 and Router 3.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide interface ae1.100; interface ae3.100 routing-interface irb.0; } vlan-200 { domain-type bridge; vlan-id 200; interface ge-3/3/3.200; interface ae1.200; interface ae3.200 routing-interface irb.1; } } 2. Configure the router link and IRB on Router 3: [edit] interfaces { xe-1/1/0 { unit 0 { family inet { address 10.0.20.3/24; # Routing interface } } } irb { unit 0 { family inet { address 10.0.1.3/24 { vrrp-group 1 { virtual-address 10.0.1.
Chapter 2: Basic Layer 2 Features on MX Series Routers unit 4 { family inet { address 10.0.3.4/24 { } } unit 5 { family inet { address 10.0.3.5/24 { } } unit 6 { family inet { address 10.0.3.6/24 { } } unit 7 { family inet { address 10.0.3.7/24 { } } unit 8 { family inet { address 10.0.3.8/24 { } } } } bridge-domains { vlan-100 { domain-type bridge; vlan-id 100; interface ge-2/2/2.100; interface ae2.100; interface ae3.100; routing-interface irb.
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.
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.
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.
Chapter 3: Virtual Switches Related Documentation • MX Series Ethernet Services Routers Solutions Page • Layer 2 Features for a Switching Environment on page 39 Copyright © 2010, Juniper Networks, Inc.
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 Ta
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.
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.
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 configuration.
Chapter 4: VLANs Within Bridge Domain and VPLS Environments • Related Documentation 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.
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 The Layer 2 provider edge (PE) routers are MX Series routers.
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: • L2-PE1 at Site 1: VLAN 100 and VLAN 300 • L2-PE2 at Site 2: VLAN 100 • L2-PE3 at Site 3: VLAN 100 • L2-PE4 at Site 4: VLAN 300 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.
Junos 10.
Chapter 4: VLANs Within Bridge Domain and VPLS Environments Bridge domain c1–vlan-100 for customer-c1–virtual-switch has five logical interfaces: • Logical interface ge-1/0/0.1 configured on physical port ge-1/0/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.
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 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 8 on page 52.
Chapter 4: VLANs Within Bridge Domain and VPLS Environments to P0 and P1, Site 2 is connected to P0 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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-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.
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: • 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 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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 for redundancy, although both links are only shown for L2-PE1 at Site 1. Site 1 is connected to P0 and P1, Site 2 is connected to P0 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.
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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide } # End of customer-c1-v1-to-v1000 customer-c1-v1500 { instance-type vpls; vlan-id 1500; interface ge-1/0/0.11; interface ge-6/0/0.11; } # End of customer-c1-v1500 } # End of routing-instances Note the use of the vlan-id all and vlan-id-range statements in the VPLS instance called customer-c1-v1-to-v1000. The vlan-id all statement implicitly creates multiple learning domains, each with its own normalized VLAN.
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 In some 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.
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 0 { ... # 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; } ...
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.
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 i
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 with 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.
Chapter 6: Dynamic Profiles for VLAN Interfaces and Protocols 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 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide } 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 arriving with VLAN identifier 10 on ge-0/0/1 are normalized to a frame with VLAN identifier 100.
Chapter 6: Dynamic Profiles for VLAN Interfaces and Protocols } } 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 VLAN value of 100. The same configuration can be accomplished using dynamic profiles.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide vlan-tags outer 200 inner 100; } } NOTE: This is not a complete router configuration. 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 configuration.
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 ]; # Other departements } } protocols vpls { site-range 10; site sample-site-1 { site-identifier 1; } } ...
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 ]; } } } NOTE: This is not a complete router configuration.
Chapter 6: Dynamic Profiles for VLAN Interfaces and Protocols 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.
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; ...
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 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Related Documentation • MX Series Ethernet Services Routers Solutions Page • 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.
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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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> 2 clients, (2 IP address 192.168.1.1 192.168.1.
CHAPTER 8 MX Series Router in an ATM Ethernet Interworking 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 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).
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Because of the translation, the flow of packets and frames between PE1 (the M 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 L3 PE2 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.
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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide at-2/0/0 { encapsulation ethernet-over-atm; atm-options { vpi 100; } unit 0 { vci 100.34; family inet { address 30.1.1.1/24; } } } } PE1 Configuation Configure the Layer 2 Circuit [edit] interfaces { at-2/0/1 { atm-options { vpi 100; } unit 0 { encapsulation vlan-vci-ccc; vpi 100; vci-range 32 63; } } ge-5/0/0 { unit 0 { family inet { address 20.1.1.1/24; } family mpls; } } protocols { mpls { interface ge-5/0/0.0; } ospf { area 0.0.0.
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 { vlan-vci-tagging; encapsulation vlan-vci-ccc; unit 0 { vlan-id 100; inner-vlan-id-range start 32 end 63; } } ge-0/2/8 { unit 0 { 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 lo0.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide vlan-tags outer 100 inner 34; family inet { address 30.1.1.
Chapter 8: MX Series Router in an ATM Ethernet Interworking Function PE1 Configuation Configure the Layer 2 Circuit [edit] interfaces { at-2/0/1 { atm-options { vpi 100; } unit 0 { encapsulation vlan-vci-ccc; vpi 100; vci-range 32 63; } } ge-5/0/0 { unit 0 { family inet { address 20.1.1.1/24; } family mpls; } } protocols { mpls { interface ge-5/0/0.0; } ospf { area 0.0.0.0 { interface ge-5/0/0.0; interface lo0.0 { passive; } } } ldp { interface all; } l2circuit { neighbor 10.255.171.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide ge-0/2/0 { gigether-options { 802.3ad ae0; } } ge-0/2/8 { unit 0 { family inet { address 20.1.1.10/24; } family mpls; ae0 { vlan-vci-tagging; encapsulation vlan-vci-ccc; unit 0 { 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 { interface ge-0/2/8.0; interface lo0.0 { passive; } } } ldp { interface all; } l2circuit { neighbor 10.255.171.45 { interface ae0.
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>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
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide atm-options { vpi 100; } unit 0 { encapsulation vlan-vci-ccc; vpi 100; vci-range start 32 end 63; } } ge-5/0/0 { 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/0/0.
Chapter 8: MX Series Router in an ATM Ethernet Interworking Function } 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 { interface ge-0/2/8.0; } connections { remote-interface-switch rws1 { interface ge-0/2/0.
Junos 10.
Chapter 8: MX Series Router in an ATM Ethernet Interworking Function 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/0/0.0; } connections { remote-interface-switch rws1 { interface at-2/0/1.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide family mpls; } } ae0 { vlan-vci-tagging; encapsulation vlan-vci-ccc; unit 0 { 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 rws1 { interface ae0.
Chapter 8: MX Series Router in an ATM Ethernet Interworking Function You verify your configuration on the MX Series router with the show connections command: user@PE2>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 encapsulation lsp-sw: LSP switching DS -- disabled tx-p2mp-sw: transmit P2MP switching Dn -- down rx-p2mp-sw: receive P
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 Protection on page 145 Copyright © 2010, Juniper Networks, Inc.
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.
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.
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-unicast-non-ip-mcast-policer { if-exceeding { bandwidth-limit 50k; burst-size-limit 150k; } then loss-priority high; } 2.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 4.
Chapter 9: Layer 2 Firewall Filters count evil-mac-address; # Counts frame with the bad source MAC address discard; } term two { then accept; # Make sure to accept other traffic } } } } 2.
Junos 10.4 MX Series Ethernet Services Routers Solutions 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 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.
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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide } 3.
CHAPTER 10 IEEE 802.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide • 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.
Chapter 10: IEEE 802.1ag 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).
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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 1 { encapsulation vlan-vpls; vlan-id 2000; } } ge-0/0/0 { unit 0 { family inet { address 10.200.1.
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 vlan2000-PE1 { site-identifier 2; } } } } [edit protocols] rsvp { interface ge-0/0/0.0; } mpls { label-switched-path PE1-to-PE2 { to 10.100.1.1; } interface ge-0/0/0.0; } bgp { group PE1-to-PE2 { type internal; local-address 10.200.1.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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 2000; } } ge-5/2/7 { unit 0 { family inet { address 10.100.1.1/24; } family mpls; } } lo0 { unit 0 { family inet { address 10.255.168.
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 { interface ge-5/2/7.0; } mpls { label-switched-path PE2-to-PE1 { to 10.200.1.1; } interface ge-5/2/7.0; } bgp { group PE2-to-PE1 { type internal; local-address 10.100.1.1; family l2vpn { signaling; } local-as 65000; neighbor 10.200.1.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide direction up; auto-discovery; } } } } } } Configuration of P router MPLS only, no CFM needed: [edit] interfaces { ge-5/2/7 { # Connected to PE1 unit 0 { family inet { address 10.200.1.10/24; } family mpls; } } ge-0/1/0 { # Connected to PE2 unit 0 { family inet { address 10.100.1.10/24; } family mpls; } } lo0 { unit 0{ family inet { address 10.255.168.240/32; } } } } [edit] protocols { rsvp { interface ge-0/1/0.0; interface ge-5/2/7.
Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management 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 { level 7; maintenance-association customer-site1 { continuity-check { interval 1s; } mep 800 { interface ge-5/2/3.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide interval 1s; } mep 700 { interface ge-0/2/9.
Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management Here are the configurations of CFM on the customer routers. CFM on L2-CE1 [edit interfaces] ge-0/2/9 { vlan-tagging; unit 0 { vlan-id 2000; } } [edit protoccols oam ethernet] connectivity-fault-management { maintenance-domain customer { level 7; maintenance-association customer-site1 { continuity-check { interval 1s; } mep 700 { interface ge-0/2/9.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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; interface ge-5/0/9.0; interface ge-5/1/7.
Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management encapsulation flexible-ethernet-services; unit 0 { encapsulation vlan-bridge; vlan-id 2000; } } ge-5/2/3 { vlan-tagging; encapsulation flexible-ethernet-services; unit 0 { encapsulation vlan-bridge; vlan-id 2000; } } [edit bridge-domains] bridge-vlan2000 { domain-type bridge; interface ge-5/2/3.0; interface ge-5/1/7.
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 Physical Interfaces CFM can be used to monitor the physical link between two routers. This functionality is similar to that supported by theIEEE 802.3ah LFM protocol.
Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management } } } } The configuration on Router 2 mirrors that on Router 1.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 118 Copyright © 2010, Juniper Networks, Inc.
CHAPTER 11 ITU-T Y.
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.
Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements For two-way (round-trip) Ethernet frame delay measurement, either 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.
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.
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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Table 3: Monitor Ethernet Delay Command Parameters (continued) Parameter Parameter Range Description wait time 1–255 seconds (default: 1) (Optional) Specifies the number of seconds to wait between frames. The default is 1 second.
Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements 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.
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 0 { vlan-id 512; } } } protocols { oam { ethernet { connectivity-fault-management { traceoptions { file eoam_cfm.
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 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.
Junos 10.
Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements Identifier MAC address 101 00:90:69:0a:48:57 State ok Interface 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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 NOTE: When two systems are close to each other, their one-way delay values are very high compared to their two-way delay values.
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 201 { interface ge-5/2/9.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide } 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.
Chapter 11: ITU-T Y.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 8 92 9 92 10 108 Average two-way delay : Average two-way delay variation: Best case two-way delay : Worst case two-way delay : 103 usec 8 usec 92 usec 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.
Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements Untagged interface configuration for Router MX-1. [edit] interfaces { ge-5/0/0 { unit 0; } ge-5/2/9 { unit 0; } } protocols { oam { ethernet { connectivity-fault-management { traceoptions { file eoam_cfm.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide connectivity-fault-management { traceoptions { file eoam_cfm.
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 • Example: 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Example: Configuring Ethernet LFM Between PE and CE In this 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.
Chapter 12: IEEE 802.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide pdu-threshold 5; } } } } } 2.
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 AE0: [edit] chassis { aggregated-devices { ethernet { device-count 1; } } } interfaces ge-1/0/1 { gigether-options { 802.3ad ae0; } } interfaces ge-2/0/0 { gigether-options { 802.3ad ae0; } } interfaces ae0 { unit 0 { family inet { address 11.11.11.2/24; } } } protocols { oam { ethernet { link-fault-management { interface ae0; } } } } 2.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 802.3ad ae0; } } interfaces ae0 { unit 0 { family inet { address 11.11.11.
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 the CE router: [edit] interfaces ge-1/1/0 { unit 0 { family inet { address 11.11.11.
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 • Example: Viewing Ethernet Ring Protection Status—Ring Failure Condition o
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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.
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 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Example: Configuring Ethernet Ring Protection for MX Series Routers 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 Example Topology The links connecting the three MX Series routers are shown in Figure 23 on page 148.
Chapter 13: Ethernet Ring Protection • 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 is pg103. NOTE: Although not strictly required for physical ring protection, this example configures Ethernet OAM with MEPs.
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.
Chapter 13: Ethernet Ring Protection ge-1/0/2 { vlan-tagging; encapsulation flexible-ethernet-services; unit 1 { encapsulation vlan-bridge; vlan-id 100; } } ge-1/2/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/1.1; interface ge-1/0/2.1; } } 3.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 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 configure Router 3: 1.
Chapter 13: Ethernet Ring Protection 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.
Junos 10.
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.
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] • ring-2—Data channel [500,600] Customer sites CS1 router Two customer sites are connected to AS 1: • Customer site 1, VLAN 200 and VLAN 300 • Customer site 2, VLAN 500 and VLAN 600 CS1 has the following protection group properties: • RPL owner—ring-1. • East interface—ge-3/2/4.0. • West interface—ge-5/2/3.0.
Chapter 13: Ethernet Ring Protection Table 5: Components of the Network Topology (continued) Property Settings AS1 router 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 following bridging properties: • bd100 is associated with vlan-id 100. • bd101 is associated with vlan-id 101. • bd200 is associated with vlan-id 200.
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 Procedure To configure ERP on CS1: 1.
Chapter 13: Ethernet Ring Protection interfaces { ge-3/2/4 { vlan-tagging; unit 0 { family bridge { interface-mode trunk; vlan-id-list 100-1000; } } } ge-5/2/3 { vlan-tagging; unit 0 { family bridge { interface-mode trunk; 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.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide } } } } routing-instances { vs { instance-type virtual-switch; interface ge-3/2/4.0; interface ge-5/2/3.
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 Procedure To configure ERP on CS2: 1.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide interface-mode trunk; vlan-id-list 100-1000; } } } ge-2/0/8 { unit 0 { family bridge { interface-mode trunk; vlan-id-list 100-1000; } } } protocols { protection-group { ethernet-ring ring-1 { east-interface { 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.
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 Configuration To quickly configure AS1 for ERP, copy the following commands and paste them into the switch terminal window of AS1: [edit] set interfaces ge-2/0/5 unit 0 family bridge interface-mode trunk set interfaces ge-2/0/5 unit 0 family bridge vlan-id-list 100-1000 set interfaces ge-2/1/1 unit 0 family bridge inte
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide NOTE: Always configure the east-interface statement first, before configuring the west-interface statement. [edit protection-group] user@as1# set ethernet-ring ring-1 east-interface control-channel ge-2/0/5.0 user@as1# set ethernet-ring ring-1 east-interface control-channel vlan 100 user@as1# set ethernet-ring ring-1 west-interface control-channel ge-2/1/1.
Chapter 13: Ethernet Ring Protection } 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.
Junos 10.
Chapter 13: Ethernet Ring Protection ge-5/2/3 123 forwarding Ethernet ring data channel parameters for protection group ring-2 Meaning Interface STP index Forward State ge-3/2/4 ge-5/2/3 124 125 discarding forwarding 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 a ring interface.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Node ID NR No Link Blocked No No NR No Yes Yes Ring-1 00:21:59:03:ff:d0 Ring-2 Meaning 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.
Chapter 13: Ethernet Ring Protection ge-2/0/4 ge-2/0/8 300 300 44 45 default—switch/bd300 default-switch/bd300 Ethernet ring IFBD parameters for protection group ring-2 Interface ge-2/0/4 ge-2/0/8 ge-2/0/4 ge-2/0/8 Meaning Vlan 500 500 600 600 STP Index 46 47 46 47 Bridge Domain default—switch/bd500 default-switch/bd500 default—switch/bd600 default-switch/bd600 The output displayed shows the ring interfaces ge-2/0/4 and ge-2/0/8 in protection groups ring-1 and ring-2.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Ethernet ring data channel parameters for protection group ring-2 Interface ge-2/0/5 ge-2/1/1 Meaning STP index 24 25 Forward State forwarding forwarding 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 a ring interface.
Chapter 13: Ethernet Ring Protection 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 the following: Router 1 Operational Commands (Normal Ring Operation) user@router1> show protection-group ethernet-ring aps Ethernet Ring Name Request/state No Flush Ring Protection Link Blocked pg101 NR No Yes Originator Yes
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Router 3 will see almost identical information. user@router2> show protection-group ethernet-ring interface Ethernet ring port parameters for protection group pg102 Interface ge-1/2/1 ge-1/0/2 Control Channel ge-1/2/1.1 ge-1/0/2.1 Forward State forwarding forwarding Ring Protection Link End No No Signal Failure Admin State Clear IFF ready Clear IFF ready Note that both interfaces are forwarding.
Chapter 13: Ethernet Ring Protection Originator No Remote Node ID 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@router1> show protection-group ethernet-ring interface Ethernet ring port parameters for protection group pg101 Interface ge-1/0/1 ge-1/2/4 Control Channel ge-1/0/1.1 ge-1/2/4.
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide Signal Failure Clear set Admin State IFF ready IFF ready Note that the failed interface (ge-1/0/2.1) is not forwarding. Router 3 will see almost identical information. user@router2> show protection-group ethernet-ring node-state Ethernet ring APS State Event Ring Protection Link Owner pg102 idle NR-RB No Restore Timer disabled Quard Timer disabled Operation state operational Note that Router 2 is not the owner.
PART 4 Index • Index on page 177 Copyright © 2010, Juniper Networks, Inc.
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...................................................xxii < >, in syntax descriptions...................................................xxi [ ], in configuration statements.......................................xxii { }, in configuration statements.......................................xxii | (pipe), in syntax descriptions.........................................xxii A acronyms Ethernet.....................
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide VLAN tag nesting............................................................13 VLAN tags...........................................................................11 Ethernet frame delay configuring.......................................................................122 examples.......................................................125, 130, 134 statistics..................................................................
Index R ring protection Ethernet overview................................................145, 147 routers defined..................................................................................6 S statistics Ethernet frame delay..........................................123, 124 support, technical See technical support syntax conventions................................................................xxi T technical support contacting JTAC.............................................................
Junos 10.4 MX Series Ethernet Services Routers Solutions Guide 180 Copyright © 2010, Juniper Networks, Inc.
