Page 2 Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Page 7 Series Routers ..........154 Example: Viewing Ethernet Ring Protection Status—Normal Ring Operation . . . 171 Example: Viewing Ethernet Ring Protection Status—Ring Failure Condition ..172 Copyright © 2012, Juniper Networks, Inc. Table of Contents...
Page 13: About This Guide
Juniper Networks website at http://www.juniper.net/techpubs/ Juniper Networks supports a technical book program to publish books by Juniper Networks engineers and subject matter experts with book publishers around the world. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration using the Junos operating system (Junos OS) and Juniper Networks devices.
Page 14: Objectives
NOTE: For additional information about the 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/ Copyright © 2012, Juniper Networks, Inc.
Page 15: Supported Routing Platforms
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 3D Universal Edge Routers Using the Indexes This reference contains a standard index with topic entries.
Page 16: Merging A Snippet
Table 1 on page xvii configuration mode command: . Copy the ex-script-snippet.conf configuration mode command: command, see the load defines notice icons used in this guide. file to the directory /var/tmp Junos OS CLI User Guide Copyright © 2012, Juniper Networks, Inc.
Page 17: Table 1: Notice Icons
Italic text like this Italic text like this Text like this < > (angle brackets) Copyright © 2012, Juniper Networks, Inc. Description Indicates important features or instructions. Indicates a situation that might result in loss of data or hardware damage.
Page 18: Documentation Feedback
URL or page number Software release version (if applicable) Requesting Technical Support Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support contract, xviii Description...
Page 19: Self-Help Online Tools And Resources
7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features:...
Page 23: Overview Of Ethernet Solutions
Ethernet frame. B–MAC—The backbone source and destination MAC address fields found in the IEEE 802.1ah provider MAC encapsulation header. Copyright © 2012, Juniper Networks, Inc. , as well terms that apply to a Junos OS Layer 2 Configuration Guide...
Page 24 MSTP within an MST region. The MSTI provides a simple and fully connected active topology for frames classified as belonging to a VLAN that is mapped to the MSTI by the MST configuration table used by the MST bridges of that MST region. See also CIST. Copyright © 2012, Juniper Networks, Inc.
Page 25 Networking at Layer 2: Benefits of Ethernet Frames on page 9 Networking at Layer 2: Challenges of Ethernet MAC Addresses on page 10 Networking at Layer 2: Forwarding VLAN Tagged Frames on page 11 Copyright © 2012, Juniper Networks, Inc. Chapter 1: Overview of Ethernet Solutions...
Page 26: Networking And Internetworking With Bridges And Routers
NOTE: These layers are also found in the Open Systems Interconnect Reference Model (OSI-RM); however, in this chapter they are applied to the TCP/IP protocol suite. Copyright © 2012, Juniper Networks, Inc.
Page 27: Network Addressing At Layer 2 And Layer 3
Ethernet, but we'll ignore that in this discussion.) The key differences in how these addresses are assigned make all the difference when it comes to the basic functions of a bridge as opposed to a router. Copyright © 2012, Juniper Networks, Inc. Chapter 1: Overview of Ethernet Solutions...
Page 28 Ethernet frames with MAC addresses. All of these interfaces share the initial 24 bits assigned to Juniper Networks. Two might differ only in one digit from one interface to another. Yet the routers containing these MAC interfaces could be located on opposite sides of the world.
Page 29: Networking At Layer 2: Benefits Of Ethernet Frames
Ethernet frames, more of the benefits of Ethernet can be realized on the network. Networking at Layer 2 can be a powerful adjunct to IP networking, but it is not usually a substitute for IP networking. Copyright © 2012, Juniper Networks, Inc. Chapter 1: Overview of Ethernet Solutions...
Page 30: Networking At Layer 2: Challenges Of Ethernet Mac Addresses
IP address is usually invisible to most management applications. Also, utilities such as remote access for diagnostics, file transfer of configurations and software, and so on cannot run without IP addresses as well as MAC addresses. Copyright © 2012, Juniper Networks, Inc.
Page 31: Networking At Layer 2: Forwarding Vlan Tagged Frames
Figure 1 on page Ethernet frame. The lengths of each field, in bytes, is shown next to the field name. Copyright © 2012, Juniper Networks, Inc. Chapter 1: Overview of Ethernet Solutions 12, a native or normal Ethernet frame is compared to a VLAN-tagged .
Page 32: Figure 1: Native (Normal) And Vlan-Tagged Ethernet Frames
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 Copyright © 2012, Juniper Networks, Inc.
Page 33: Networking At Layer 2: Forwarding Dual-Tagged Frames
VLAN tag space can be addressed by adding more VLAN tags to the basic Ethernet frame. Related Ethernet Networking Documentation Ethernet Terms and Acronyms on page 3 Copyright © 2012, Juniper Networks, Inc. . Any network device can easily tell if it has received 0x88a8 ) or two tags ( 0x8100 0x88a8 0x8100 ) for the inner and outer tags.
Page 34: Networking At Layer 2: Logical Interface Types
VLAN only and the interface is normally attached to an end-user device (packets are implicitly associated with the configured VLAN). In contrast, trunk interfaces multiplex traffic from multiple VLANs and usually interconnect switches. Copyright © 2012, Juniper Networks, Inc.
Page 35: A Metro Ethernet Network With Mx Series Routers
A Metro Ethernet Network with MX Series Routers What would a Metro Ethernet network with Juniper Networks MX Series 3D Universal Edge Router 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.
Page 36: Figure 3: A Metro Ethernet Network With Mx Series Routers
Network Addressing at Layer 2 and Layer 3 on page 7 16, the circled numbers reflect the different formats that the Ethernet Figure 4 on page Figure 4 on page 16 to the other, Copyright © 2012, Juniper Networks, Inc.
Page 37: Layer 2 Networking Standards
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 Copyright © 2012, Juniper Networks, Inc. Chapter 1: Overview of Ethernet Solutions...
Page 38 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 © 2012, Juniper Networks, Inc.
Page 39: Basic Solutions For Mx Series Routers
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 © 2012, Juniper Networks, Inc.
Page 41: Basic Layer 2 Features On Mx Series Routers
Bridge domains—Bridge domains limit the scope of media access control (MAC) learning (and thereby the size of the MAC table) and also determine where the device should propagate frames sent to broadcast, unknown unicast, and multicast (BUM) MAC addresses. Copyright © 2012, Juniper Networks, Inc.
Page 42: Example Roadmap: Configuring A Basic Bridge Domain Environment
Example Scenario on page 23 Example Configuration Summary on page 24 Example Topology Consider the network in acting as Layer 2 devices. Figure 5 on page 23. The figure shows three MX Series routers Copyright © 2012, Juniper Networks, Inc.
Page 43: Example Scenario
Router 2 and Router 3 have IRB configured so that they can pass traffic to other routers in the rest of the network. Copyright © 2012, Juniper Networks, Inc. Chapter 2: Basic Layer 2 Features on MX Series Routers ) are gathered into two aggregated Ethernet (AE) links mixing bridged traffic...
Page 44: Example Configuration Summary
Do not copy these configurations and use them directly on an actual system. . Router 3 has an access interface which “Layer 2 Features for a Bridging “Example Step: “Example Copyright © 2012, Juniper Networks, Inc.
Page 45 100; unit 200 { encapsulation vlan-bridge; vlan-id 200; interfaces ge-2/2/2 { unit 0 { Copyright © 2012, Juniper Networks, Inc. Chapter 2: Basic Layer 2 Features on MX Series Routers device-count 2; # Number of AE interfaces on router...
Page 46 100 { interface-mode access; vlan-id 205; interface-mode trunk; vlan-id-list 200-205; # This trunk port is part of VLAN range 200–205 interface-mode trunk; vlan-id-list 100, 200–205; device-count 2; # Number of AE interfaces on the router Copyright © 2012, Juniper Networks, Inc.
Page 47 { encapsulation extended-vlan-bridge; vlan-tagging; unit 100 { vlan-id 100; unit 200 { vlan-id 200; interfaces ae3 { encapsulation extended-vlan-bridge; vlan-tagging; unit 100 { Copyright © 2012, Juniper Networks, Inc. Chapter 2: Basic Layer 2 Features on MX Series Routers...
Page 48 802.3ad ae3; interfaces ge-11/1/1 { gigether-options { device-count 2; # Number of AE interfaces on router interface-mode trunk; vlan-id-list 200-205; # This trunk port is part of VLAN range 200–205 interface-mode access; vlan-id 200; Copyright © 2012, Juniper Networks, Inc.
Page 49 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 Copyright © 2012, Juniper Networks, Inc. Chapter 2: Basic Layer 2 Features on MX Series Routers interface-mode trunk;...
Page 50: Example Step: Configuring Bridge Domains
204; vlan205 { domain-type bridge; vlan-id 205; Configure a bridge domain on Router 2: [edit] bridge-domains { vlan100 { domain-type bridge; vlan-id 100; interface ge-2/2/2.100; interface ae1.100; interface ae3.100; vlan200 { Copyright © 2012, Juniper Networks, Inc.
Page 51 Example Step: Configuring Interfaces and VLAN Tags on page 24 Example Step: Configuring Spanning Tree Protocols on page 32 Example Step: Configuring Integrated Bridging and Routing on page 34 Copyright © 2012, Juniper Networks, Inc. Chapter 2: Basic Layer 2 Features on MX Series Routers...
Page 52: Example Step: Configuring Spanning Tree Protocols
# This VLAN corresponds to MSTP instance 1 bridge-priority 4096; # This bridge acts as VLAN 100 designated bridge on # the R2-R3 segment vlan200; # This VLAN corresponds to MSTP instance 2 Copyright © 2012, Juniper Networks, Inc.
Page 53: Figure 6: Designated, Root, And Alternate Ports
The designated, root, and alternate ports for the two VLANs on the three routers are shown in Figure 6 on page Figure 6: Designated, Root, and Alternate Ports Copyright © 2012, Juniper Networks, Inc. Chapter 2: Basic Layer 2 Features on MX Series Routers region vlan100; # This VLAN corresponds to MSTP instance 1 vlan200;...
Page 54: Example Step: Configuring Integrated Bridging And Routing
{ address 10.0.10.2/24; # Routing interface family inet { address 10.0.1.2/24 { on Router 2 and xe-2/1/0 Copyright © 2012, Juniper Networks, Inc.
Page 55 [edit] interfaces { xe-1/1/0 { unit 0 { irb { unit 0 { Copyright © 2012, Juniper Networks, Inc. Chapter 2: Basic Layer 2 Features on MX Series Routers vrrp-group 1 { virtual-address 10.0.1.51; priority 254; family inet { address 10.0.2.2/24 { vrrp-group 2 { virtual-address 10.0.2.51;...
Page 56 { address 10.0.3.3/24 { family inet { address 10.0.3.4/24 { family inet { address 10.0.3.5/24 { family inet { address 10.0.3.6/24 { family inet { address 10.0.3.7/24 { family inet { address 10.0.3.8/24 { Copyright © 2012, Juniper Networks, Inc.
Page 57 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 Copyright © 2012, Juniper Networks, Inc. Chapter 2: Basic Layer 2 Features on MX Series Routers...
Page 59: Chapter 3 Virtual Switches
Configuring Virtual Switches as Separate Routing Instances on page 40 Layer 2 Features for a Switching Environment Juniper Networks MX Series 3D Universal Edge 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.
Page 60: Configuring Virtual Switches As Separate Routing Instances
For more information about configuring virtual switches, see the Configuration Guide 21. For an example of a basic bridge domain “Example Roadmap: Configuring a Basic Bridge Domain Environment” “Layer 2 Features Junos OS Layer 2 Copyright © 2012, Juniper Networks, Inc.
Page 63: Vlans Within Bridge Domain And Vpls Environments
Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces on page 47 Example: Configuring a Provider Bridge Network with Normalized VLAN Tags on page 47 Example: Configuring a Provider VPLS Network with Normalized VLAN Tags on page 51 Copyright © 2012, Juniper Networks, Inc.
Page 64: Packet Flow Through A Bridged Network With Normalized Vlans
Example: Configuring a Provider Bridge Network with Normalized VLAN Tags on page 47 Example: Configuring a Provider VPLS Network with Normalized VLAN Tags on page 51 Example: Configuring One VPLS Instance for Several VLANs on page 55 Copyright © 2012, Juniper Networks, Inc.
Page 65: Configuring A Normalized Vlan For Translation Or Tagging
Chapter 4: VLANs Within Bridge Domain and VPLS Environments NOTE: This topic is not intended as a troubleshooting guide. However, you can use it with a broader troubleshooting strategy to identify Juniper Networks MX Series 3D Universal Edge Router network problems. statements at the...
Page 66: Sending Tagged Or Untagged Packets Over Vpls Virtual Interfaces
VLAN tags identifying a Layer vlan-id none NOTE: The outgoing packets can still contain customer VLAN tags. Junos OS Routing Protocols interfaces) need to be lsi- “Example: Configuring —Tags all packets sent over statement. statement Copyright © 2012, Juniper Networks, Inc.
Page 67: Configuring Learning Domains For Vlan Ids Bound To Logical Interfaces
This topic provides a configuration example to help you effectively configure a network of Juniper Networks MX Series 3D Universal Edge Routers for a bridge domain or virtual private LAN service (VPLS) environment. The emphasis here is on choosing the normalized virtual LAN (VLAN) configuration.
Page 68: Figure 7: Provider Bridge Network Using Normalized Vlan Tags
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. Figure 7 on page Copyright © 2012, Juniper Networks, Inc.
Page 69 1 { encapsulation vlan-bridge; vlan-tags outer 500 inner 100; # This places two VLAN tags on the provider Copyright © 2012, Juniper Networks, Inc. Chapter 4: VLANs Within Bridge Domain and VPLS Environments NOTE: The configurations in this chapter are only partial examples of complete and functional router configurations.
Page 70 100; # Customer VLAN 100 uses these five logical interfaces interface ge-1/0/0.1; interface ge-2/0/0.1; interface ge-3/0/0.1; interface ge-4/0/0.1; interface ge-5/0/0.1; domain-type bridge; vlan-id 300; # Customer VLAN 300 uses these three logical interfaces interface ge-1/0/0.11; interface ge-5/0/0.11; interface ge-6/0/0.11; Copyright © 2012, Juniper Networks, Inc.
Page 71: Example: Configuring A Provider Vpls Network With Normalized Vlan Tags
This topic provides a configuration example to help you effectively configure a network of Juniper Networks MX Series 3D Universal Edge Routers for a bridge domain or virtual private LAN service (VPLS) environment. The emphasis here is on choosing the normalized virtual LAN (VLAN) configuration.
Page 72: Figure 8: Vlan Tags And Vpls Labels
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. Figure 8 on page Copyright © 2012, Juniper Networks, Inc.
Page 73 11 { encapsulation vlan-vpls; Copyright © 2012, Juniper Networks, Inc. Chapter 4: VLANs Within Bridge Domain and VPLS Environments . The VPLS instance sets up customer-c1-vsi . The VPLS instance sets up a pseudowire to remote Site 4.
Page 74 VLAN tag of 200 in the in their VLAN tag fields. vlan-id 100 vlan-id none statement in the VPLS vlan-id none configuration: . All MAC addresses learned . The ge-1/0/0.11 Copyright © 2012, Juniper Networks, Inc.
Page 75: Example: Configuring One Vpls Instance For Several Vlans
This topic provides a configuration example to help you effectively configure a network of Juniper Networks MX Series 3D Universal Edge Routers for a bridge domain or virtual private LAN service (VPLS) environment. The emphasis here is on choosing the normalized virtual LAN (VLAN) configuration.
Page 76: Figure 9: Many Vlans On One Vpls Instance
Most sites have multiple VLANs configured. Service provider SP-1 is providing VPLS services for customer C1, services that could span several sites. Now customer C1 can have many VLANs in the range from 1 through 1000 (for example). Copyright © 2012, Juniper Networks, Inc.
Page 77 # Note the use of the VLAN id all statement interface ge-1/0/0.1; interface ge-2/0/0.1; interface ge-3/0/0.1; Copyright © 2012, Juniper Networks, Inc. Chapter 4: VLANs Within Bridge Domain and VPLS Environments statements provide a way to switch all of these VLANs with a minimum NOTE:...
Page 78 , the same MAC address (for example, M1) can be learned on ge-1/0/0.1 for VLAN 500 and also on logical interface for VLAN 600. configuration: , or , or , with a ge-2/0/0.1 ge-3/0/0.1 Copyright © 2012, Juniper Networks, Inc.
Page 79: Bulk Administration Of Layer 2 Features On Mx Series Routers
The reverse translation takes place on egress. In other words, if VLAN 200 is translated to 500 on ingress, VLAN 500 is translated to VLAN 200 on egress. Copyright © 2012, Juniper Networks, Inc. . The prefix and number are supplied prefix-vlan-number...
Page 80: Example: Configuring Multiple Bridge Domains With A Vlan Id List
NOTE: This example also translates frame VLANs from 500 to 200 and 501 to 201 on egress. hierarchy level. [edit bridge-domains] ) and configures the bridge domain explicitly: vlan-id-list sales-vlan-2 Copyright © 2012, Juniper Networks, Inc.
Page 81 Bulk Configuration of VLANs and Bridge Domains on page 59 Example: Configuring VLAN Translation with a VLAN ID List on page 59 Copyright © 2012, Juniper Networks, Inc. Chapter 5: Bulk Administration of Layer 2 Features on MX Series Routers...
Page 83: Dynamic Profiles For Vlan Interfaces And Protocols
The router contains several predefined variables that enable dynamic association of interfaces and logical units to incoming subscriber requests. While configuring dynamic profile, use the variable physical interface and Copyright © 2012, Juniper Networks, Inc. $junos-interface-ifd-name for a dynamic logical interface $junos-underlying-unit-number lsi.1048576...
Page 84: Vpls Pseudowire Interfaces Without Dynamic Profiles
200 inner 100; protocols vpls { vpls-id 10; neighbor 10.1.1.20; {...more...} Junos OS Subscriber Access Configuration Guide statement is not supported. statement is not supported. statement option is not supported. statement is not supported. Copyright © 2012, Juniper Networks, Inc.
Page 85: Vpls Pseudowire Interfaces And Dynamic Profiles
# The profile {...more...} [edit interfaces] ge-0/0/1 { Copyright © 2012, Juniper Networks, Inc. Chapter 6: Dynamic Profiles for VLAN Interfaces and Protocols NOTE: This is not a complete router configuration. are normalized to a dual-tagged frame with an outer VLAN value of 200...
Page 86: Ce Routers Without Dynamic Profiles
VLAN identifier 100. The broadcast packet have this VLAN value swapped to 20 and ge-0/0/2 ge-0/0/3 with an outer VLAN tag value of 200 pushed on top green Copyright © 2012, Juniper Networks, Inc.
Page 87: Ce Routers And Dynamic Profiles
100; ge-0/0/2 { unit 0 { vlan-id 100; ge-0/0/3 { unit 0 { Copyright © 2012, Juniper Networks, Inc. Chapter 6: Dynamic Profiles for VLAN Interfaces and Protocols NOTE: This is not a complete router configuration. ge-0/0/1 level: protocols...
Page 88: Example: Configuring Vpls Pseudowires With Dynamic Profiles-Complex
VLAN identifier 100 (in this case, they with an outer VLAN tag value of 200 pushed on top green NOTE: These examples are not complete router configurations. ge-0/0/2 ge-0/0/3 Copyright © 2012, Juniper Networks, Inc.
Page 89: Profiles
VPLS pseudowire trunk connecting to the other site. Configuration of Routing Instance and Interfaces Using Dynamic Profiles Here is how dynamic profiles can be applied to this basic configuration. Copyright © 2012, Juniper Networks, Inc. Chapter 6: Dynamic Profiles for VLAN Interfaces and Protocols...
Page 90 { site-range 10; site sample-site-1 { site-identifier 1; associate-profile green_vpls_pw_2; # Apply profile here ... # Other routing instance statements [edit dynamic-profiles] green_vpls_pw_2 interfaces $junos-interface-ifd-name { NOTE: This is not a complete router configuration. Copyright © 2012, Juniper Networks, Inc.
Page 91 VPLS pseudowire trunk with an outer VLAN tag of 200, except for Engineering frames. Engineering frames (VLAN 30) are only Copyright © 2012, Juniper Networks, Inc. Chapter 6: Dynamic Profiles for VLAN Interfaces and Protocols NOTE: This is not a complete router configuration.
Page 92: Configuration Of Tag Translation Using Dynamic Profiles
(VLAN 10) is mapped to VLAN 110 and sales (VLAN 20) is mapped to VLAN 120. NOTE: This is not a complete router configuration. VLAN tags egressing the VPLS pseudowire sales engineering and any statically accounting Copyright © 2012, Juniper Networks, Inc.
Page 93: Mx Series Router As A Dhcp Relay Agent
You can configure a Juniper Networks MX Series Ethernet Services Router to act as a DHCP relay agent. The MX Series router configuration at Layer 2 accesses the Layer 3 information with DHCP snooping.
Page 94: Example: Configuring Dhcp Relay In A Bridge Domain Vlan Environment
Example: Configuring DHCP Relay in a VPLS Routing Instance Environment on page 75 NOTE: This is not a complete router configuration. group vlan-20–bridge { interface ge-1/1/1.0; interface ge-1/1/2.0; interface ge-1/1/3.0; interface ge-1/1/4.0; interface ge-1/1/5.0; Junos OS Subscriber Access Configuration Copyright © 2012, Juniper Networks, Inc.
Page 95: Example: Configuring Dhcp Relay In A Vpls Routing Instance Environment
{ bd1 { domain-type bridge; vlan-id 100; forwarding-options { Copyright © 2012, Juniper Networks, Inc. Chapter 7: MX Series Router as a DHCP Relay Agent NOTE: This is not a complete router configuration. xe-9/2/0 ) leading to the DHCP server. The router performs...
Page 96 : 2008 12 12 15:56:04 PST : bound : ge—2/2/6.0 : 192.168.1.2 : 00:00:00:42:a8:e4 : active : 2008 12 12 15:56:10 PST : bound : ge—2/2/4.0 Lease expires at 2008 12 12 15:56:04 PST 2008 12 12 15:56:10 PST Copyright © 2012, Juniper Networks, Inc.
Page 97: Mx Series Router In An Atm Ethernet Interworking Function
The PE1 router translates between the ATM VPI and VCI and Ethernet VLAN tags as follows: ATM VPI to and from outer VLAN tag of the Ethernet frame ATM VCI to and from inner VLAN tag of the Ethernet frame Copyright © 2012, Juniper Networks, Inc. L2 circuits (if-switch) I/P backhaul ATM DSLAM Service...
Page 98: Figure 11: Atm Ethernet Vlan Interworking Packet Structure
Configuring MX Series Router ATM Ethernet Interworking on page 79 Inner VLAN MPLS Inner VLAN MPLS Inner VLAN MPLS Ivlan Ovlan Ivlan Ovlan Inner VLAN MPLS Figure Ethernet Ethernet Figure 12 on page Ethernet Ethernet Copyright © 2012, Juniper Networks, Inc.
Page 99: Example: Configuring Mx Series Router Atm Ethernet Interworking
Configuring Router PE2 with a Remote Interface Switch on page 85 Configuring Router PE2 with a Remote Interface Switch over Aggregated Ethernet on page 88 Copyright © 2012, Juniper Networks, Inc. Chapter 8: MX Series Router in an ATM Ethernet Interworking Function Figure 13 on page...
Page 100: Configuring Router Pe2 With A Layer 2 Circuit
32 63; ge-5/0/0 { unit 0 { family inet { 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 { address 30.1.1.1/24; address 20.1.1.1/24; passive; Copyright © 2012, Juniper Networks, Inc.
Page 101 { ldp { interface all; l2circuit { neighbor 10.255.171.45 { interface ge-0/2/0.0 { Copyright © 2012, Juniper Networks, Inc. Chapter 8: MX Series Router in an ATM Ethernet Interworking Function virtual-circuit-id 100; address 20.1.1.10/24; passive; virtual-circuit-id 100;...
Page 102: Configuring Router Pe2 With A Layer 2 Circuit Over Aggregated Ethernet
Remote PE: 10.255.171.45, Negotiated control-word: Yes (Null) Incoming label: 299824, Outgoing label: 299776 Local interface: ge-0/2/0.0, Status: Up, Encapsulation: VLAN Q-in-Q and show l2circuit connections Time last up # Up trans May 12 13:01:50 2009 Copyright © 2012, Juniper Networks, Inc.
Page 103 { ldp { interface all; l2circuit { neighbor 10.255.171.14 { interface at-2/0/1.0 { Copyright © 2012, Juniper Networks, Inc. Chapter 8: MX Series Router in an ATM Ethernet Interworking Function address 30.1.1.1/24; address 20.1.1.1/24; passive; virtual-circuit-id 100;...
Page 104 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 { ldp { interface all; l2circuit { neighbor 10.255.171.45 { interface ae0.0 { address 20.1.1.10/24; passive; virtual-circuit-id 100; Copyright © 2012, Juniper Networks, Inc.
Page 105: Configuring Router Pe2 With A Remote Interface Switch
Configuration Configure Ethernet over ATM on the ATM interface. [edit] interfaces { Copyright © 2012, Juniper Networks, Inc. Chapter 8: MX Series Router in an ATM Ethernet Interworking Function address 30.1.1.10/24; NP -- interface h/w not present Dn -- down...
Page 106 { 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; address 30.1.1.1/24; address 20.1.1.1/24; Copyright © 2012, Juniper Networks, Inc.
Page 107 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.0; transmit-lsp lsp2-1; receive-lsp lsp1-2; Copyright © 2012, Juniper Networks, Inc. Chapter 8: MX Series Router in an ATM Ethernet Interworking Function address 20.1.1.10/24;...
Page 108: Configuring Router Pe2 With A Remote Interface Switch Over Aggregated Ethernet
Legend for circuit types intf -- interface tlsp -- transmit LSP rlsp -- receive LSP Type rmt-if intf tlsp rlsp command: show connections interface switching Time last up # Up May 13 11:25:40 Copyright © 2012, Juniper Networks, Inc.
Page 109 10.255.171.45; interface ge-5/0/0.0; isis { interface ge-5/0/0.0; connections { remote-interface-switch rws1 { Copyright © 2012, Juniper Networks, Inc. Chapter 8: MX Series Router in an ATM Ethernet Interworking Function address 30.1.1.1/24; address 20.1.1.1/24; interface at-2/0/1.0; transmit-lsp lsp1-2; receive-lsp lsp2-1;...
Page 110 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/08.0; isis { interface ge-02/08.0; { address 20.1.1.10/24; Copyright © 2012, Juniper Networks, Inc.
Page 111 Related ATM Ethernet Interworking Documentation MX Series Router ATM Ethernet Interworking Function on page 77 Copyright © 2012, Juniper Networks, Inc. Chapter 8: MX Series Router in an ATM Ethernet Interworking Function address 30.1.1.10/24; Legend for connection types if-sw:...
Page 113: 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 © 2012, Juniper Networks, Inc.
Page 115: Layer 2 Firewall Filters
Example: Configuring Filtering of Frames by Packet Loss Priority on page 101 Firewall Filters for Bridge Domains and VPLS Instances Juniper Networks MX Series 3D Universal Edge Routers support firewall filters for the bridge within bridge domains and VPLS instances. This chapter explores some of the ways that filters can be used in a Layer 2 environment to control traffic.
Page 116: Example: Configuring Policing And Marking Of Traffic Entering A Vpls Core
Enhanced IP mode, then separate filter instances are created for each bridge domain that the filter is applied to. Figure 14 on page Junos OS Class of Service Configuration Copyright © 2012, Juniper Networks, Inc.
Page 117 { filter customer-1 { term t0 { term t1 { Copyright © 2012, Juniper Networks, Inc. NOTE: This example does not present exhaustive configuration listings for all routers in the figures. However, you can use this example with a broader configuration strategy to complete the MX Series router network Ethernet Operations, Administration, and Maintenance (OAM) configurations.
Page 118: Example: Configuring Filtering Of Frames By Mac Address
However, you can use this example with a broader configuration strategy to complete the MX Series router network Ethernet Operations, Administration, and Maintenance (OAM) configurations. , the firewall filter: evil-mac-address ge-2/1/0 Junos OS Policy Framework as an vlan100200 Copyright © 2012, Juniper Networks, Inc.
Page 119: Example: Configuring Filtering Of Frames By Ieee 802.1P Bits
To configure a firewall filter term that includes matching on IEEE 802.1p user priority (in the inner VLAN tag), use the match condition. Copyright © 2012, Juniper Networks, Inc. from { source-mac-address 88:05:00:29:3c:de/48; then { count evil-mac-address; # Counts frame with the bad source MAC address discard;...
Page 120 MX Series router network Ethernet Operations, Administration, and Maintenance (OAM) configurations. filter-learn-vlan-configure-forwarding from { learn-vlan-1p-priority [1 2]; then forwarding-class best-effort; filter-learn-vlan-configure-forwarding filter { input filter-learn-vlan-configure-forwarding; Junos OS Junos OS Policy best-effort as an input filter to Copyright © 2012, Juniper Networks, Inc.
Page 121: Example: Configuring Filtering Of Frames By Packet Loss Priority
Configure a Layer 2 bridging domain been configured at the [edit bridge-domains] Copyright © 2012, Juniper Networks, Inc. NOTE: Layer 2 bridging is supported only on the MX Series routers. For more information about how to configure Layer 2 bridging, see the...
Page 122 Example: Configuring Filtering of Frames by MAC Address on page 98 Example: Configuring Filtering of Frames by IEEE 802.1p Bits on page 99 filter-plp-configure-forwarding filter { input filter-plp-configure-forwarding; as an input filter to the ge-0/0/0 Copyright © 2012, Juniper Networks, Inc.
Page 123: Ieee 802.1Ag Oam Connectivity-Fault Management
Ethernet Operations, Administration, and Maintenance This topic provides an overview to help you effectively configure Ethernet Operations, Administration, and Maintenance (OAM) on a network of Juniper Networks MX Series 3D Universal Edge Routers. For more information about configuring OAM parameters on...
Page 124: Ethernet Oam Connectivity Fault Management
0 through 7. Level allocation is based on the network hierarchy, where outermost domains are assigned a higher level than the innermost domains. Customer end points have to highest maintenance domain level. In a CFM Copyright © 2012, Juniper Networks, Inc.
Page 125: Example: Configuring Ethernet Cfm Over Vpls
The service provider is using CFM level 5 and the customer is using CFM level 7. The boundaries are marked with “up mep” and “down mep” CFM terminology in the figure. Copyright © 2012, Juniper Networks, Inc. Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management...
Page 126: Figure 15: Ethernet Oam With Vpls
2000; ge-0/0/0 { unit 0 { family inet { address 10.200.1.1/24; family mpls; lo0 { unit 0 { family inet { address 10.255.168.231/32 { address 127.0.0.1/32; [edit routing-instances] vpls-vlan2000 { primary; Copyright © 2012, Juniper Networks, Inc.
Page 127 { disable; interface ge-0/0/0.0; oam { ethernet { connectivity-fault-management { maintenance-domain customer-site1 { Copyright © 2012, Juniper Networks, Inc. Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management site-identifier 2; level 5; maintenance-association customer-site1 { continuity-check { interval 1s;...
Page 128 { unit 0 { family inet { address 10.255.168.230/32 { address 127.0.0.1/32; [edit routing-instances] vpls-vlan2000 { instance-type vpls; vlan-id 2000; interface ge-5/0/9.1; route-distinguisher 10.255.168.230:2000; mep 100 { interface ge-1/0/7.1; direction up; auto-discovery; primary; Copyright © 2012, Juniper Networks, Inc.
Page 129 { disable; interface ge-5/2/7.0; oam { ethernet { connectivity-fault-management { maintenance-domain customer-site1 { Copyright © 2012, Juniper Networks, Inc. Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management site-identifier 1; level 5; maintenance-association customer-site1 { continuity-check { interval 1s; mep 200 { interface ge-5/0/9.1;...
Page 130 { rsvp { interface ge-0/1/0.0; interface ge-5/2/7.0; mpls { interface ge-0/1/0.0; interface ge-5/2/7.0; ospf { traffic-engineering; reference-bandwidth 4g; area 0.0.0.0 { interface all; interface fxp0.0 { auto-discovery; address 10.200.1.10/24; address 10.100.1.10/24; address 10.255.168.240/32; Copyright © 2012, Juniper Networks, Inc.
Page 131 2000; [edit protocols oam] ethernet { connectivity-fault-management { maintenance-domain customer { level 7; maintenance-association customer-site1 { Copyright © 2012, Juniper Networks, Inc. Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management disable; continuity-check { interval 1s; mep 800 { interface ge-5/2/3.0;...
Page 132: Example: Configuring Ethernet Cfm On Bridge Connections
The configurations in this example are only partial examples of complete and functional router configurations. Do not copy these configurations and use them directly on an actual system. Figure 16 on page 112. The customer Copyright © 2012, Juniper Networks, Inc.
Page 133 800 { Here are the configurations of CFM on the provider routers. CFM on PE1 [edit interfaces] ge-5/0/9 { vlan-tagging; Copyright © 2012, Juniper Networks, Inc. Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management interval 1s; interface ge-0/2/9.0; direction down; auto-discovery;...
Page 134 { level 3; maintenance-association provider-inner-site1 { continuity-check { interval 1s; mep 200 { interface ge-5/1/7.0; direction down; auto-discovery; CFM on PE2 [edit interfaces] ge-5/1/7 { vlan-tagging; encapsulation flexible-ethernet-services; Copyright © 2012, Juniper Networks, Inc.
Page 135 100 { interface ge-5/1/7.0; direction down; auto-discovery; Related Ethernet OAM Documentation Ethernet Operations, Administration, and Maintenance on page 103 Ethernet OAM Connectivity Fault Management on page 104 Copyright © 2012, Juniper Networks, Inc. Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management...
Page 136: Example: Configuring Ethernet Cfm On Physical Interfaces
Do not copy these configurations and use them directly on an actual system. Figure 17 on page 116. The single boundary is a “down mep” maintenance-domain private { level 0; maintenance-association private-ma { continuity-check { interval 1s; Copyright © 2012, Juniper Networks, Inc.
Page 137 Ethernet OAM Connectivity Fault Management on page 104 Example: Configuring Ethernet CFM over VPLS on page 105 Example: Configuring Ethernet CFM on Bridge Connections on page 112 Copyright © 2012, Juniper Networks, Inc. Chapter 10: IEEE 802.1ag OAM Connectivity-Fault Management mep 100 { interface ge-1/0/1;...
Page 139: Itu-T Y.1731 Ethernet Frame Delay Measurements
This is where the ability to configure and monitor Ethernet frame delay is helpful. On a Juniper Networks MX Series Ethernet Services Router equipped with the Distributed Port Concentrator (MX-DPC) only, you can perform Ethernet frame delay measurements (referred to as ETH-DM in Ethernet specifications).
Page 140: Figure 18: Ethernet Oam Overview
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 Figure 18 on Copyright © 2012, Juniper Networks, Inc.
Page 141 Configuring Two-Way ETH-DM with Single-Tagged Interfaces on page 130 Configuring ETH-DM with Untagged Interfaces on page 134 Copyright © 2012, Juniper Networks, Inc. Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements commands at the initiator MEP to display two-way delay statistics, and at...
Page 142: Configuring Mep Interfaces To Support Ethernet Frame Delay Measurements
Ethernet frame delay measurement, you must make sure that PPMD is configured properly. Without distributed PPMD, delay measurement results are not valid. hardware-assisted-timestamping connectivity-fault-management { performance-monitoring { hardware-assisted-timestamping; # Enable timestamping in hardware. statement at the [edit protocols hierarchy level: Copyright © 2012, Juniper Networks, Inc.
Page 143: Triggering An Ethernet Frame Delay Measurements Session
Existing MA identifier ma-id count count 1–65535 (default: 10) Copyright © 2012, Juniper Networks, Inc. Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements Table 3 on page Description Perform a one-way or two-way (round-trip) delay measurement. Send delay measurement frames to the destination unicast MAC address (use the format xx:xx:xx:xx:xx:xx).
Page 144: Viewing Ethernet Frame Delay Measurements Statistics
[local-mep identifier] [remote-mep identifier] [count count] Description (Optional) Specifies the number of seconds to wait between frames. The default is 1 second. commands are provided: show command. Copyright © 2012, Juniper Networks, Inc.
Page 145: Example: Configuring One-Way Ethernet Frame Delay Measurements With Single-Tagged Interfaces
This example uses two MX Series routers: CFM down MEP session on a VLAN-tagged logical interface connecting the two ( on Router Copyright © 2012, Juniper Networks, Inc. Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements NOTE: The only difference in the two commands is the use of the keyword.
Page 146 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.0; direction down; auto-discovery; MX-2 Copyright © 2012, Juniper Networks, Inc.
Page 147 Remote MEP not receiving CCM Erroneous CCM received Cross-connect CCM received RDI sent by some MEP Copyright © 2012, Juniper Networks, Inc. Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements traceoptions { file eoam_cfm.log size 1g files 2 world-readable; flag all;...
Page 148 DMRs sent Valid DMRs received Invalid DMRs received Remote MEP count: 1 MAC address State Interface 00:90:69:0a:43:94 ge-0/2/5.0 : 1590 : 10 MX-1 : no : no : no : no : 1572 : 10 Copyright © 2012, Juniper Networks, Inc.
Page 149 MEP identifier: 201, MAC address: 00:90:69:0a:43:94 Remote MEP count: 1 Remote MAC address: 00:90:69:0a:48:57 Delay measurement statistics: Index Copyright © 2012, Juniper Networks, Inc. Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements MAC address State 00:90:69:0a:48:57 should also collect the delay statistics (up to 100 per session)
Page 150: Example: Configuring Two-Way Ethernet Frame Delay Measurements With Single-Tagged Interfaces
However, two-way delay measurement does not require synchronized timing, making two-way delay measurements more accurate. MX-1 MX-2 on Router ge-0/2/5 MX-2 NOTE: These are not complete router configurations. MX-1 . The configuration creates a CFM ge-5/2/9 Copyright © 2012, Juniper Networks, Inc.
Page 151 0 { vlan-id 512; protocols { oam { ethernet { connectivity-fault-management { Copyright © 2012, Juniper Networks, Inc. Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements traceoptions { file eoam_cfm.log size 1g files 2 world-readable; flag all; linktrace { path-database-size 255;...
Page 152 100ms; hold-interval 1; mep 101 { interface ge-0/2/5.0; direction down; auto-discovery; MX-1 , start a two-way delay measurement to Router MX-2 maintenance MX-1 : no : no : no : no : 894 Copyright © 2012, Juniper Networks, Inc.
Page 153 Valid DMRs received Invalid DMRs received Remote MEP identifier: 101 Remote MAC address: 00:90:69:0a:48:57 Delay measurement statistics: Index Copyright © 2012, Juniper Networks, Inc. Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements MAC address State 00:90:69:0a:48:57 One-way delay Two-way delay...
Page 154: Interfaces
: 103 usec : 92 usec : 122 usec MX-1 One-way delay Two-way delay (usec) (usec) : 103 usec : 92 usec : 122 usec NOTE: These are not complete router configurations. MX-1 MX-2 Copyright © 2012, Juniper Networks, Inc.
Page 155 0; ge-0/2/5 { unit 0; protocols { oam { ethernet { Copyright © 2012, Juniper Networks, Inc. Chapter 11: ITU-T Y.1731 Ethernet Frame Delay Measurements MX-1 traceoptions { file eoam_cfm.log size 1g files 2 world-readable; flag all; linktrace { path-database-size 255;...
Page 156 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/2; direction down; auto-discovery; Copyright © 2012, Juniper Networks, Inc.
Page 157: Ieee 802.3Ah Oam Link-Fault Management
Example: Configuring Ethernet LFM Between PE and CE on page 138 Example: Configuring Ethernet LFM for CCC on page 139 Example: Configuring Ethernet LFM for Aggregated Ethernet on page 140 Example: Configuring Ethernet LFM with Loopback Support on page 142 Copyright © 2012, Juniper Networks, Inc.
Page 158: Example: Configuring Ethernet Lfm Between Pe And Ce
{ protocols { oam { ethernet { Link-Layer-Down Figure 19 on page address 11.11.11.1/24; link-fault-management { interface ge-1/1/0 { pdu-interval 1000; pdu-threshold 5; address 11.11.11.2/24; . This results in notifications to 138. Copyright © 2012, Juniper Networks, Inc.
Page 159: Example: Configuring Ethernet Lfm For Ccc
{ encapsulation ethernet-ccc; unit 0; protocols { oam { ethernet { Copyright © 2012, Juniper Networks, Inc. Chapter 12: IEEE 802.3ah OAM Link-Fault Management link-fault-management { interface ge-1/1/0 { pdu-interval 1000; pdu-threshold 5; Figure 20 on page 139...
Page 160: Example: Configuring Ethernet Lfm For Aggregated Ethernet
The use of LFM with aggregated Ethernet is shown in Figure 21: Ethernet LFM for Aggregated Ethernet pdu-threshold 5; link-fault-management { interface ge-1/0/0 { pdu-interval 1000; pdu-threshold 5; Figure 21 on page 140. Copyright © 2012, Juniper Networks, Inc.
Page 161 { aggregated-devices { ethernet { interfaces ge-1/0/0 { gigether-options { 802.3ad ae0; interfaces ge-5/0/0 { gigether-options { Copyright © 2012, Juniper Networks, Inc. Chapter 12: IEEE 802.3ah OAM Link-Fault Management device-count 1; address 11.11.11.2/24; link-fault-management { interface ae0; device-count 1;...
Page 162: Example: Configuring Ethernet Lfm With Loopback Support
To configure LFM between a PE and a CE: Configure LFM loopback on the PE router: [edit] interfaces ge-1/0/0 { unit 0 { family inet { address 11.11.11.1/24; link-fault-management { interface ae0; Figure 22 on page address 11.11.11.1/24; 142. Copyright © 2012, Juniper Networks, Inc.
Page 163 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 Copyright © 2012, Juniper Networks, Inc. Chapter 12: IEEE 802.3ah OAM Link-Fault Management link-fault-management { interface ge-1/0/0 { pdu-interval 1000;...
Page 165: Ethernet Ring Protection
Two or more nodes form a ring. Links between the nodes form a chain, with the last node also connecting the first. Every ring node therefore has two ports related to the ring, one in each direction. In this chapter, these directions are referred to as east and west. Copyright © 2012, Juniper Networks, Inc.
Page 166 The R-APS protocol does not detect the number of RPL owner nodes configured on the ring. You must configure only one RPL and RPL owner per ring or protection switching will not work properly. “Ethernet Copyright © 2012, Juniper Networks, Inc.
Page 167: Ethernet Ring Protection Using Ring Instances For Load Balancing
Related Ethernet Ring Protection on page 145 Documentation Example: Configuring Ethernet Ring Protection for MX Series Routers on page 148 Copyright © 2012, Juniper Networks, Inc. NOTE: To learn how ERP works in a single-ring topology, see Protection” on page 145.
Page 168: Example: Configuring Ethernet Ring Protection For Mx Series Routers
(this is also the R-APS messaging control channel). ge-1/0/1.1 ge-1/2/4.1 . The protection group is Figure 23 on page 148. R-APS Channel ge-1/2/1 West ge-1/0/2 East pg102 (the RPL) and the west control pg101 Copyright © 2012, Juniper Networks, Inc.
Page 169: Router 1 (Rpl Owner) Configuration
Configure the Ethernet ring protection group: [edit] protocols { protection-group { ethernet-ring pg101 { Copyright © 2012, Juniper Networks, Inc. ge-1/0/2.1 . The protection group is ge-1/2/1.1 ge-1/0/3.1 . The protection group is ge-1/0/4.1 NOTE: Although not strictly required for physical ring protection, this example configures Ethernet OAM with MEPs.
Page 170: Router 2 Configuration
{ level 0; maintenance-association 100 { mep 1 { interface ge-1/0/1; remote-mep 2 { action-profile rmep-defaults; maintenance-domain d2 { level 0; maintenance-association 100 { mep 1 { interface ge-1/2/4; remote-mep 2 { action-profile rmep-defaults; Copyright © 2012, Juniper Networks, Inc.
Page 171 [edit] protocols { protection-group { ethernet-ring pg102 { Configure Ethernet OAM: [edit] protocols { oam { ethernet { Copyright © 2012, Juniper Networks, Inc. encapsulation vlan-bridge; vlan-id 100; encapsulation vlan-bridge; vlan-id 100; east-interface { control-channel ge-1/0/2.1; west-interface { control-channel ge-1/2/1.1;...
Page 172: Router 3 Configuration
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; encapsulation vlan-bridge; vlan-id 100; encapsulation vlan-bridge; vlan-id 100; Copyright © 2012, Juniper Networks, Inc.
Page 173 [edit] protocols { protection-group { ethernet-ring pg103 { Configure Ethernet OAM: [edit] protocols { oam { ethernet { Copyright © 2012, Juniper Networks, Inc. east-interface { control-channel ge-1/0/3.1; west-interface { control-channel ge-1/0/4.1; connectivity-fault-management { action-profile rmep-defaults { default-action { interface-down;...
Page 174: Series Routers
MX Series routers. CS1 and CS2 act as core routers in the topology, and AS1 acts as an aggregation switch. Each router has two ring instances, ring-1 and ring-2. All nodes on displays the topology for this example. The topology contains three Copyright © 2012, Juniper Networks, Inc.
Page 175 300. Customer site 2 uses VLANs 500 and 600. Figure 24: ERP with Multiple Protection Instances Configured on Three MX Series Routers data-channel [200,300] Table 5 on page 156 Copyright © 2012, Juniper Networks, Inc. ge-2/0/8.0 , the west interface on CS2, is the ring ring-1 RPL owner ring-1 ge-5/2/3.0...
Page 176: Table 5: Components Of The Network Topology
100 is associated with bd101 vlan-id 101 is associated with bd200 vlan-id 200 is associated with bd300 vlan-id 300 bd500 is associated with vlan-id 500 bd600 is associated with vlan-id 600 Copyright © 2012, Juniper Networks, Inc.
Page 178 CS1 to AS, and configure the as the ring protection link owner: ring-1 NOTE: Always configure the east-interface configuring the west-interface statement. statement as with family bridge ring-1 ring-2 statement first, before Copyright © 2012, Juniper Networks, Inc.
Page 179 { vlan-tagging; unit 0 { family bridge { protocols { protection-group { ethernet-ring ring-1 { protection-group { ethernet-ring ring-2{ Copyright © 2012, Juniper Networks, Inc. interface-mode trunk; vlan-id-list 100-1000; interface-mode trunk; vlan-id-list 100-1000; east-interface { control-channel { ge-3/2/4.0; vlan 100;...
Page 181 Check the results of the configuration: user@cs2> show configuration interfaces { ge-2/0/4 { unit 0 { Copyright © 2012, Juniper Networks, Inc. to connect CS2 to CS1 and trunk interface ge-2/0/4 to connect CS2 to CS1, and configure the as the ring protection link owner:...
Page 182 100-1000; 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]; control-channel { ge-2/0/4.0; vlan 101; control-channel { ge-2/0/8.0; vlan 101; ring-protection-link-end; vlan [500, 500]; Copyright © 2012, Juniper Networks, Inc.
Page 183 0 family bridge vlan-id-list 100-1000 user@as1# set ge-2/1/1 unit 0 family bridge interface-mode trunk user@as1# set ge-2/1/1 unit 0 family bridge vlan-id-list 100 Copyright © 2012, Juniper Networks, Inc. to connect CS2 to CS1 and trunk interface ge-2/0/5...
Page 184 { ethernet-ring ring-1 { NOTE: Always configure the east-interface configuring the west-interface interface-mode trunk; vlan-id-list 100-1000 interface-mode trunk; vlan-id-list 100-1000 east-interface { control-channel { ge-2/0/5.0; vlan 100; ring-1 ring-2 statement first, before statement. Copyright © 2012, Juniper Networks, Inc.
Page 185 101; bd200 { vlan-id 200; bd300 { vlan-id 300; bd500 { vlan-id 500; bd600 { vlan-id 600; Copyright © 2012, Juniper Networks, Inc. west-interface { control-channel { ge-2/1/1.0; vlan 100; data-channel { vlan [200, 300]; control-channel { ge-2/0/5.0; vlan 101;...
Page 186 , indicating that this node is an R-APS originator. STP index Forward State Ring Protection Originator Remote Link Blocked have a ring-1 ring-2 Request/state Request/state is displayed, , indicating that MAC field for Originator ring-1 Copyright © 2012, Juniper Networks, Inc.
Page 187 Verify that ERP is enabled on CS2. Action Show the status of the ring APS (R-APS) messages to determine if there is a ring failure: user@cs2>show protection-group ethernet-ring aps Copyright © 2012, Juniper Networks, Inc. forwarding forwarding STP index Forward State...
Page 188 . The STP index controls the forwarding behavior for a set of VLANs on forwarding Link Blocked have a ring-1 ring-2 Request/state Request/state is displayed, , indicating that MAC Originator field for ring-1 field for Originator ring-2 Forward traffic. discarding Copyright © 2012, Juniper Networks, Inc.
Page 189 Verify the forwarding state of the data channel. Action List the interfaces acting as the control channels and their respective data channels (represented by the STP index number): user@as1>show protection-group ethernet-ring data-channel Copyright © 2012, Juniper Networks, Inc. Vlan STP Index Bridge Domain default—switch/bd200 default-switch/bd200 default—switch/bd300...
Page 190 , VLAN 200 and VLAN 300 are being supported on both ring-2 ring-1 on bridge domains bd200 STP Index 24 Forward discarding traffic. All data channels in protection groups ge-2/1/1 . For , VLAN 500 and VLAN bd300 ring-2 on bridge domains bd500 Copyright © 2012, Juniper Networks, Inc.
Page 191: Example: Viewing Ethernet Ring Protection Status-Normal Ring Operation
3) will see the following similar output: Router 2 and Router 3 user@router2> show protection-group ethernet-ring aps Ethernet Ring Name Operational pg102 Commands (Normal Ring Operation) Originator Copyright © 2012, Juniper Networks, Inc. Request/state No Flush Remote Node ID Control Channel Forward State ge-1/0/1.1 discarding ge-1/2/4.1...
Page 192: Example: Viewing Ethernet Ring Protection Status-Ring Failure Condition
Ring Protection Link End ge-1/2/1.1 forwarding ge-1/0/2.1 forwarding Admin State IFF ready IFF ready APS State Event Ring Protection Link Owner idle NR-RB Quard Timer Operation state disabled operational Request/state No Flush Ring Protection Link Blocked Copyright © 2012, Juniper Networks, Inc.
Page 193 Note the failure event (SF). 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 Copyright © 2012, Juniper Networks, Inc. Remote Node ID 00:01:02:00:00:01 Control Channel Forward State ge-1/0/1.1 forwarding ge-1/2/4.1...
Page 194 Example: Viewing Ethernet Ring Protection Status—Normal Ring Operation on page 171 Admin State IFF ready IFF ready ge-1/0/2.1 ) is not forwarding. Router 3 will see almost APS State Event Ring Protection Link Owner idle NR-RB Quard Timer Operation state disabled operational Copyright © 2012, Juniper Networks, Inc.
Page 197: Index
Ethernet frame delay...122 MX Series bridge domains...30 Copyright © 2012, Juniper Networks, Inc. MX Series integrated bridging and MX Series interfaces and VLAN MX Series Layer 2 basics...22 MX Series spanning tree conventions text and syntax...xvii...
Page 198 (PLP), filtering parentheses, in syntax ring protection Ethernet overview...145, routers defined...6 statistics Ethernet frame delay...123, support, technical See technical support tags...24 syntax conventions...xvii protocols...32 CFM...104 LFM...137 OAM...103 types...14 example...79 routers...6 LFM...137 overview...103 on...101 descriptions...xviii Copyright © 2012, Juniper Networks, Inc.
Page 199 MX Series examples with VPLS...47, 51, normalization and translation...43, normalized...46 single VPLS example...55 translation...45 VPLS labels example...51 VPLS MX Series examples...59, MX Series VLAN examples...47, 51, virtual interfaces...46 VPLS pseudowires with dynamic profiles on MX Series...63, 64, Copyright © 2012, Juniper Networks, Inc. Index...

This manual is also suitable for:

Mx series

Juniper JUNOS OS 10.4 Manual

Chapter 3 Virtual Switches

Chapter 1 Overviewofethernetsolutions

Chapter 10 Ieee802.1Agoamconnectivity-Faultmanagement

Chapter 11 ITU-Ty.1731Ethernetframedelaymeasurements

Chapter 12 Ieee802.3Ahoamlink-Faultmanagement

Chapter 13 Ethernetringprotection

Chapter 2 Basiclayer2Featuresonmxseriesrouters

Chapter 4 Vlanswithinbridgedomainandvplsenvironments

Chapter 5 Bulkadministrationoflayer2Featuresonmxseriesrouters

Chapter 6 Dynamicprofilesforvlaninterfacesandprotocols

Chapter 7 Mxseriesrouterasadhcprelayagent

Chapter 8 Mxseriesrouterinanatmethernetinterworkingfunction

Chapter 9 Layer2Firewallfilters

Quick Links

Need help?

Questions and answers

Related Manuals for Juniper JUNOS OS 10.4

Summary of Contents for Juniper JUNOS OS 10.4

This manual is also suitable for:

Table of Contents