Juniper JUNOS OS 10.4 User manual

Junos

®

OS

MX Series 3D Universal Edge Routers Solutions

Guide

Release

12.1

Published: 2012-03-08

Juniper Networks, Inc.

1194 North Mathilda Avenue

Sunnyvale, California 94089

USA

408-745-2000

www.juniper.net

of them is in the public domain.

This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation

release 3.0 by Cornell University and its collaborators. Gated is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s

HELLO routing protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD

L. S. Associates.

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United

States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other

trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,

transfer, or otherwise revise this publication without notice.

Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are

owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,

6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.

Junos

®

OS MX Series 3D Universal Edge Routers Solutions Guide

Release 12.1

Revision History

March 2012—R1 Junos OS 12.1

The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the

year 2038. However, the NTP application is known to have some difficulty in the year 2036.

END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks

software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at

http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions

of that EULA.

Abbreviated Table of Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

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

Chapter 4 VLANs Within Bridge Domain and VPLS Environments . . . . . . . . . . . . . . . . 43

Chapter 5 Bulk Administration of Layer 2 Features on MX Series Routers . . . . . . . . . . 59

Chapter 6 Dynamic Profiles for VLAN Interfaces and Protocols . . . . . . . . . . . . . . . . . . . 63

Chapter 7 MX Series Router as a DHCP Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 8 MX Series Router in an ATM Ethernet Interworking Function . . . . . . . . . . . . 77

Part 3 Ethernet Filtering, Monitoring, and Fault Management Solutions

for MX Series Routers

Chapter 9 Layer 2 Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 10 IEEE 802.1ag OAM Connectivity-Fault Management . . . . . . . . . . . . . . . . . . 103

Chapter 11 ITU-T Y.1731 Ethernet Frame Delay Measurements . . . . . . . . . . . . . . . . . . . . 119

Chapter 12 IEEE 802.3ah OAM Link-Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . 137

Chapter 13 Ethernet Ring Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Part 4 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide

Table of Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Junos Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Supported Routing Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Using the Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Part 1 Overview

Chapter 1 Overview of Ethernet Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Ethernet Terms and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Networking and Internetworking with Bridges and Routers . . . . . . . . . . . . . . . . . . . 6

Network Addressing at Layer 2 and Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Networking at Layer 2: Benefits of Ethernet Frames . . . . . . . . . . . . . . . . . . . . . . . . 9

Networking at Layer 2: Challenges of Ethernet MAC Addresses . . . . . . . . . . . . . . . 10

Networking at Layer 2: Forwarding VLAN Tagged Frames . . . . . . . . . . . . . . . . . . . . 11

Networking at Layer 2: Forwarding Dual-Tagged Frames . . . . . . . . . . . . . . . . . . . . 13

Networking at Layer 2: Logical Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

A Metro Ethernet Network with MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . 15

Layer 2 Networking Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Part 2 Basic Solutions for MX Series Routers

Chapter 2 Basic Layer 2 Features on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Layer 2 Features for a Bridging Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Example Roadmap: Configuring a Basic Bridge Domain Environment . . . . . . . . . 22

Example Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Example Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Example Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Example Step: Configuring Interfaces and VLAN Tags . . . . . . . . . . . . . . . . . . . . . . 24

Example Step: Configuring Bridge Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Example Step: Configuring Spanning Tree Protocols . . . . . . . . . . . . . . . . . . . . . . . 32

Example Step: Configuring Integrated Bridging and Routing . . . . . . . . . . . . . . . . . 34

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

VLANs Within a Bridge Domain or VPLS Instance . . . . . . . . . . . . . . . . . . . . . . . . . 43

Packet Flow Through a Bridged Network with Normalized VLANs . . . . . . . . . . . . 44

Configuring a Normalized VLAN for Translation or Tagging . . . . . . . . . . . . . . . . . . 45

Implicit VLAN Translation to a Normalized VLAN . . . . . . . . . . . . . . . . . . . . . . 45

Sending Tagged or Untagged Packets over VPLS Virtual Interfaces . . . . . . . 46

Configuring a Normalized VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces . . . . . . . 47

Example: Configuring a Provider Bridge Network with Normalized VLAN Tags . . . 47

Example: Configuring a Provider VPLS Network with Normalized VLAN Tags . . . . 51

Example: Configuring One VPLS Instance for Several VLANs . . . . . . . . . . . . . . . . 55

Chapter 5 Bulk Administration of Layer 2 Features on MX Series Routers . . . . . . . . . . 59

Bulk Configuration of VLANs and Bridge Domains . . . . . . . . . . . . . . . . . . . . . . . . . 59

Example: Configuring VLAN Translation with a VLAN ID List . . . . . . . . . . . . . . . . . 59

Example: Configuring Multiple Bridge Domains with a VLAN ID List . . . . . . . . . . . 60

Chapter 6 Dynamic Profiles for VLAN Interfaces and Protocols . . . . . . . . . . . . . . . . . . . 63

Dynamic Profiles for VPLS Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Example: Configuring VPLS Pseudowires with Dynamic Profiles—Basic

Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

VPLS Pseudowire Interfaces Without Dynamic Profiles . . . . . . . . . . . . . . . . . 64

VPLS Pseudowire Interfaces and Dynamic Profiles . . . . . . . . . . . . . . . . . . . . 65

CE Routers Without Dynamic Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

CE Routers and Dynamic Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Example: Configuring VPLS Pseudowires with Dynamic Profiles—Complex

Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configuration of Routing Instance and Interfaces Without Dynamic

Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configuration of Routing Instance and Interfaces Using Dynamic

Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuration of Tag Translation Using Dynamic Profiles . . . . . . . . . . . . . . . . 72

Chapter 7 MX Series Router as a DHCP Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

MX Series Router as a Layer 2 DHCP Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Example: Configuring DHCP Relay in a Bridge Domain VLAN Environment . . . . . 74

Example: Configuring DHCP Relay in a VPLS Routing Instance Environment . . . . 75

Chapter 8 MX Series Router in an ATM Ethernet Interworking Function . . . . . . . . . . . . 77

MX Series Router ATM Ethernet Interworking Function . . . . . . . . . . . . . . . . . . . . . 77

Example: Configuring MX Series Router ATM Ethernet Interworking . . . . . . . . . . . 79

Configuring Router PE2 with a Layer 2 Circuit . . . . . . . . . . . . . . . . . . . . . . . . . 80

Configuring Router PE2 with a Layer 2 Circuit over Aggregated Ethernet . . . . 82

Configuring Router PE2 with a Remote Interface Switch . . . . . . . . . . . . . . . . 85

Configuring Router PE2 with a Remote Interface Switch over Aggregated

Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide

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

Example: Configuring Filtering of Frames by IEEE 802.1p Bits . . . . . . . . . . . . . . . . 99

Example: Configuring Filtering of Frames by Packet Loss Priority . . . . . . . . . . . . . 101

Chapter 10 IEEE 802.1ag OAM Connectivity-Fault Management . . . . . . . . . . . . . . . . . . 103

Ethernet Operations, Administration, and Maintenance . . . . . . . . . . . . . . . . . . . . 103

Ethernet OAM Connectivity Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Example: Configuring Ethernet CFM over VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Example: Configuring Ethernet CFM on Bridge Connections . . . . . . . . . . . . . . . . . 112

Example: Configuring Ethernet CFM on Physical Interfaces . . . . . . . . . . . . . . . . . 116

Chapter 11 ITU-T Y.1731 Ethernet Frame Delay Measurements . . . . . . . . . . . . . . . . . . . . 119

Ethernet Frame Delay Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Configuring MEP Interfaces to Support Ethernet Frame Delay Measurements . . 122

Triggering an Ethernet Frame Delay Measurements Session . . . . . . . . . . . . . . . . 123

Viewing Ethernet Frame Delay Measurements Statistics . . . . . . . . . . . . . . . . . . . 124

Example: Configuring One-Way Ethernet Frame Delay Measurements with

Single-Tagged Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Example: Configuring Two-Way Ethernet Frame Delay Measurements with

Single-Tagged Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Example: Configuring Ethernet Frame Delay Measurements with Untagged

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Chapter 12 IEEE 802.3ah OAM Link-Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . 137

Ethernet OAM Link Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Example: Configuring Ethernet LFM Between PE and CE . . . . . . . . . . . . . . . . . . . 138

Example: Configuring Ethernet LFM for CCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Example: Configuring Ethernet LFM for Aggregated Ethernet . . . . . . . . . . . . . . . 140

Example: Configuring Ethernet LFM with Loopback Support . . . . . . . . . . . . . . . . 142

Chapter 13 Ethernet Ring Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Ethernet Ring Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Ethernet Ring Protection Using Ring Instances for Load Balancing . . . . . . . . . . . 147

Example: Configuring Ethernet Ring Protection for MX Series Routers . . . . . . . . 148

Example Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Router 1 (RPL Owner) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Router 2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Router 3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Example: Configuring Load Balancing Within Ethernet Ring Protection for MX

Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Example: Viewing Ethernet Ring Protection Status—Normal Ring Operation . . . 171

Example: Viewing Ethernet Ring Protection Status—Ring Failure Condition . . . . 172

Table of Contents

Part 4 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide

List of Figures

Part 1 Overview

Chapter 1 Overview of Ethernet Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 1: Native (Normal) and VLAN-Tagged Ethernet Frames . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . 16

Part 2 Basic Solutions for MX Series Routers

Chapter 2 Basic Layer 2 Features on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 5: Bridging Network with MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . 23

Figure 6: Designated, Root, and Alternate Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4 VLANs Within Bridge Domain and VPLS Environments . . . . . . . . . . . . . . . . 43

Figure 7: Provider Bridge Network Using Normalized VLAN Tags . . . . . . . . . . . . . 48

Figure 8: VLAN Tags and VPLS Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 9: Many VLANs on One VPLS Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 8 MX Series Router in an ATM Ethernet Interworking Function . . . . . . . . . . . . 77

Figure 10: ATM Ethernet VLAN Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Figure 11: ATM Ethernet VLAN Interworking Packet Structure . . . . . . . . . . . . . . . . 78

Figure 12: CCC to Stacked VLAN Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Figure 13: ATM Ethernet VLAN Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Part 3 Ethernet Filtering, Monitoring, and Fault Management Solutions

for MX Series Routers

Chapter 9 Layer 2 Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Figure 14: Policing and Marking Traffic Entering a VPLS Core . . . . . . . . . . . . . . . . 96

Chapter 10 IEEE 802.1ag OAM Connectivity-Fault Management . . . . . . . . . . . . . . . . . . 103

Figure 15: Ethernet OAM with VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Figure 16: Ethernet CFM over a Bridge Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Figure 17: Ethernet CFM on Physical Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Chapter 11 ITU-T Y.1731 Ethernet Frame Delay Measurements . . . . . . . . . . . . . . . . . . . . 119

Figure 18: Ethernet OAM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Chapter 12 IEEE 802.3ah OAM Link-Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . 137

Figure 19: Ethernet LFM Between PE and CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Figure 20: Ethernet LFM for CCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Figure 21: Ethernet LFM for Aggregated Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . 140

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

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide

List of Tables

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Part 3 Ethernet Filtering, Monitoring, and Fault Management Solutions

for MX Series Routers

Chapter 11 ITU-T Y.1731 Ethernet Frame Delay Measurements . . . . . . . . . . . . . . . . . . . . 119

Table 3: Monitor Ethernet Delay Command Parameters . . . . . . . . . . . . . . . . . . . . 123

Table 4: Show Ethernet Delay Command Parameters . . . . . . . . . . . . . . . . . . . . . 125

Chapter 13 Ethernet Ring Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Table 5: Components of the Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide

About This Guide

This preface provides the following guidelines for using the Junos

®

OS MX Series 3D

Universal Edge Routers Solutions Guide:

•

Junos Documentation and Release Notes on page xiii

•

Objectives on page xiv

•

Audience on page xiv

•

Supported Routing Platforms on page xv

•

Using the Indexes on page xv

•

Using the Examples in This Manual on page xv

•

Documentation Conventions on page xvi

•

Documentation Feedback on page xviii

•

Requesting Technical Support on page xviii

Junos Documentation and Release Notes

For a list of related Junos documentation, see

http://www.juniper.net/techpubs/software/junos/ .

If the information in the latest release notes differs from the information in the

documentation, follow the Junos Release Notes.

To obtain the most current version of all Juniper Networks

®

technical documentation,

see the product documentation page on the Juniper Networks website at

http://www.juniper.net/techpubs/ .

Juniper Networks supports a technical book program to publish books by Juniper Networks

engineers and subject matter experts with book publishers around the world. These

books go beyond the technical documentation to explore the nuances of network

architecture, deployment, and administration using the Junos operating system (Junos

OS) and Juniper Networks devices. In addition, the Juniper Networks Technical Library,

published in conjunction with O'Reilly Media, explores improving network security,

reliability, and availability using Junos OS configuration techniques. All the books are for

sale at technical bookstores and book outlets around the world. The current list can be

viewed at http://www.juniper.net/books .

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

Audience

This guide is designed for network administrators who are configuring and monitoring

Layer 2 features of the Junos OS.

To use this guide, you need a broad understanding of networks in general, the Internet

in particular, networking principles, and network configuration. You must also be familiar

with one or more of the following Internet routing protocols:

•

Border Gateway Protocol (BGP)

•

Distance Vector Multicast Routing Protocol (DVMRP)

•

Intermediate System-to-Intermediate System (IS-IS)

•

Internet Control Message Protocol (ICMP) router discovery

•

Internet Group Management Protocol (IGMP)

•

Multiprotocol Label Switching (MPLS)

•

Open Shortest Path First (OSPF)

•

Protocol-Independent Multicast (PIM)

•

Resource Reservation Protocol (RSVP)

•

Routing Information Protocol (RIP)

•

Simple Network Management Protocol (SNMP)

Personnel operating the equipment must be trained and competent; must not conduct

themselves in a careless, willfully negligent, or hostile manner; and must abide by the

instructions provided by the documentation.

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions 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 3D Universal Edge Routers

Using the Indexes

This reference contains a standard index with topic entries.

Using the Examples in This Manual

If you want to use the examples in this manual, you can use the load merge or the load

merge relative command. These commands cause the software to merge the incoming

configuration into the current candidate configuration. The example does not become

active until you commit the candidate configuration.

If the example configuration contains the top level of the hierarchy (or multiple

hierarchies), the example is a full example. In this case, use the load merge command.

If the example configuration does not start at the top level of the hierarchy, the example

is a snippet. In this case, use the load merge relative command. These procedures are

described in the following sections.

Merging a Full Example

To merge a full example, follow these steps:

1. From the HTML or PDF version of the manual, copy a configuration example into a

text file, save the file with a name, and copy the file to a directory on your routing

platform.

For example, copy the following configuration to a file and name the file ex-script.conf.

Copy the ex-script.conf file to the /var/tmp directory on your routing platform.

system {

scripts {

commit {

file ex-script.xsl;

}

interfaces {

fxp0 {

disable;

unit 0 {

family inet {

address 10.0.0.1/24;

}

About This 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.

For example, copy the following snippet to a file and name the file

ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory

on your routing platform.

commit {

file ex-script-snippet.xsl; }

2. Move to the hierarchy level that is relevant for this snippet by issuing the following

configuration mode command:

[edit]

user@host# edit system scripts

[edit system scripts]

3. Merge the contents of the file into your routing platform configuration by issuing the

load merge relative configuration mode command:

[edit system scripts]

user@host# load merge relative /var/tmp/ex-script-snippet.conf

load complete

For more information about the load command, see the Junos OS CLI User Guide.

Documentation Conventions

Table 1 on page xvii defines notice icons used in this guide.

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide

Table 1: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Table 2 on page xvii defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

ExamplesDescriptionConvention

To enter configuration mode, type the

configure command:

user@host> configure

Represents text that you type.Bold text like this

user@host> show chassis alarms

No alarms currently active

Represents output that appears on the

terminal screen.

Fixed-width text like this

•

A policy term is a named structure

that defines match conditions and

actions.

•

Junos OS System Basics Configuration

Guide

•

RFC 1997, BGP Communities Attribute

•

Introduces important new terms.

•

Identifies book names.

•

Identifies RFC and Internet draft titles.

Italic text like this

Configure the machine’s domain name:

[edit]

root@# set system domain-name

domain-name

Represents variables (options for which

you substitute a value) in commands or

configuration statements.

Italic text like this

•

To configure a stub area, include the

stub statement at the [edit protocols

ospf area area-id] hierarchy level.

•

The console port is labeled CONSOLE.

Represents names of configuration

statements, commands, files, and

directories; interface names;

configuration hierarchy levels; or labels

on routing platform components.

Text like this

stub <default-metric metric>;Enclose optional keywords or variables.< > (angle brackets)

About This Guide

Table 2: Text and Syntax Conventions (continued)

ExamplesDescriptionConvention

broadcast | multicast

(string1 | string2 | string3)

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.

| (pipe symbol)

rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the

same line as the configuration statement

to which it applies.

# (pound sign)

community name members [

community-ids ]

Enclose a variable for which you can

substitute one or more values.

[ ] (square brackets)

[edit]

routing-options {

static {

route default {

nexthop address;

retain;

}

Identify a level in the configuration

hierarchy.

Indention and braces ( { } )

Identifies a leaf statement at a

configuration hierarchy level.

; (semicolon)

J-Web GUI Conventions

•

In the Logical Interfaces box, select

All Interfaces.

•

To cancel the configuration, click

Cancel.

Represents J-Web graphical user

interface (GUI) items you click or select.

Bold text like this

In the configuration editor hierarchy,

select Protocols>Ospf.

Separates levels in a hierarchy of J-Web

selections.

> (bold right angle bracket)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can send your comments to

techpubs-comments@juniper.net, or fill out the documentation feedback form at

https://www.juniper.net/cgi-bin/docbugreport/ . If you are using e-mail, be sure to include

the following information with your comments:

•

Document or topic name

•

URL or page number

•

Software release version (if applicable)

Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance

Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide

or are covered under warranty, and need postsales technical support, you can access

our tools and resources online or open a case with JTAC.

•

JTAC policies—For a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf .

•

Product warranties—For product warranty information, visit

http://www.juniper.net/support/warranty/ .

•

JTAC Hours of Operation —The JTAC centers have resources available 24 hours a day,

7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online

self-service portal called the Customer Support Center (CSC) that provides you with the

following features:

•

Find CSC offerings: http://www.juniper.net/customers/support/

•

Find product documentation: http://www.juniper.net/techpubs/

•

Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

•

Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

•

Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/

•

Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

•

Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

To verify service entitlement by product serial number, use our Serial Number Entitlement

(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

•

Use the Case Management tool in the CSC at http://www.juniper.net/cm/ .

•

Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, visit us at

http://www.juniper.net/support/requesting-support.html

About This Guide

Junos OS 12.1 MX Series 3D Universal Edge Routers Solutions Guide

Page is loading ...

Juniper JUNOS OS 10.4 User manual

This manual is also suitable for

Juniper JUNOS OS 10.4 User manual

Related papers

Other documents