Juniper EX9200 Features Manual

Vpls feature guide ex series

Hide thumbs Also See for EX9200:

Features manual (448 pages)

Manual (118 pages)

Overview manual (72 pages)

Table Of Contents

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

page of 198

/ 198
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual See also: Feature Manual

VPLS Feature Guide for EX9200 Switches

Release

16.2

Modified: 2016-11-02

Table of Contents

Need help?

Do you have a question about the EX9200 and is the answer not in the manual?

Questions and answers

Summary of Contents for Juniper EX9200

Page 2 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.
Page 4 VPLS Feature Guide for EX9200 Switches Configuring Inter-AS VPLS with MAC Processing at the ASBR ... . 18 Inter-AS VPLS with MAC Operations Configuration Summary ..18 Configuring the ASBRs for Inter-AS VPLS .
Page 6 VPLS Feature Guide for EX9200 Switches connectivity-type ........... 114 encapsulation (Physical Interface) .
Page 13: About The Documentation
® 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/ If the information in the latest release notes differs from the information in the documentation, follow the product Release Notes.
Page 14: Merging A Full Example
VPLS Feature Guide for EX9200 Switches If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the command. These procedures are load merge relative described in the following sections.
Page 15: Documentation Conventions
Table 2: Text and Syntax Conventions Convention Description Examples Bold text like this Represents text that you type. To enter configuration mode, type the configure command: user@host> configure Copyright © 2016, Juniper Networks, Inc.
Page 16 VPLS Feature Guide for EX9200 Switches Table 2: Text and Syntax Conventions (continued) Convention Description Examples Fixed-width text like this Represents output that appears on the user@host> show chassis alarms terminal screen. No alarms currently active Italic text like this...
Page 17: Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can provide feedback by using either of the following methods: Online feedback rating system—On any page of the Juniper Networks TechLibrary site , simply click the stars to rate the content, http://www.juniper.net/techpubs/index.html and use the pop-up form to provide us with information about your experience.
Page 18: Opening A Case With Jtac
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: http://kb.juniper.net/InfoCenter/ 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/...
Page 21: Introduction To Vpls And Supported Standards
Layer 2 VPN forwards packets in point-to-point fashion only. The paths carrying VPLS traffic between each PE router participating in a routing instance are called pseudowires. The pseudowires are signaled using either BGP or LDP. Copyright © 2016, Juniper Networks, Inc.
Page 22: Supported Vpls Standards
VPLS Feature Guide for EX9200 Switches Supported VPLS Standards Junos OS substantially supports the following Internet RFCs and draft, which define standards for virtual private LAN service (VPLS). RFC 4761, Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling...
Page 23: Vpls Configuration Overview
(IGP) on the PE and provider (P) routers. By default, VPLS is disabled. Many configuration procedures for VPLS are identical to the procedures for Layer 2 VPNs and Layer 3 VPNs. Copyright © 2016, Juniper Networks, Inc.
Page 24: Configuring An Ethernet Switch As The Ce Device For Vpls
Layer 2 connections, such as those configured with Layer 2 VPNs, Layer 2 circuits, and VPLS instances. However, CE Ethernet switches that generate proprietary BPDU frames might not be able to run STP across Juniper Networks routing platforms configured for these emulated Layer 2 connections.
Page 25: Configuring Vpls
Configuring BGP Path Selection for Layer 2 VPNs on page 77 Configuring Load Balancing and Performance on page 81 Configuring Class of Service and Firewall Filters in VPLS on page 85 Monitoring and Tracing VPLS on page 103 Copyright © 2016, Juniper Networks, Inc.
Page 27: Configuring Signaling Protocols For Vpls
If the destination is a remote CE device (connected to another PE router), the PE router discards the packet. If the PE router cannot determine the destination of the VPLS packet, it floods the packet to all attached CE devices. This process is illustrated in Figure 1 on page Copyright © 2016, Juniper Networks, Inc.
Page 28: Figure 1: Flooding A Packet With An Unknown Destination To All Pe Routers In
Layer 2 connections, such as those configured with Layer 2 VPNs, Layer 2 circuits, and VPLS routing instances. However, CE Ethernet switches that generate proprietary BPDU frames might not be able to run STP across Juniper Networks routing platforms configured for these emulated Layer 2 connections.
Page 29: Bgp Signaling For Vpls Pe Routers Overview
PE routers participating in the VPLS network. Related VPLS Multihoming Overview on page 61 Documentation VPLS Path Selection Process for PE Routers on page 57 Copyright © 2016, Juniper Networks, Inc.
Page 30: Interoperability Between Bgp Signaling And Ldp Signaling In Vpls
VPLS Feature Guide for EX9200 Switches Interoperability Between BGP Signaling and LDP Signaling in VPLS You can configure a VPLS routing instance where some of the PE routers use BGP for signaling and some use LDP for signaling. NOTE: In the VPLS documentation, the word router in terms such as PE router is used to refer to any device that provides routing functions.
Page 31: Figure 2: Bgp And Ldp Signaling For A Vpls Routing Instance
BGP-signaled PE routers can logically function within a single VPLS routing instance. NOTE: The following features are not supported for VPLS routing instances configured with both BGP and LDP signaling: Point-to-multipoint LSPs Integrated routing and bridging IGMP snooping Copyright © 2016, Juniper Networks, Inc.
Page 32: Flooding Unknown Packets Across Mesh Groups
VPLS Feature Guide for EX9200 Switches Flooding Unknown Packets Across Mesh Groups Broadcast, multicast, and unicast packets of unknown origin received from a PE router are flooded to all local CE routers. They are also flooded to all of the PE routers in the VPLS routing instance except the PE routers that are a part of the originating PE router mesh group.
Page 33: Configuring Interoperability Between Bgp Signaling And Ldp Signaling In Vpls
LDP BGP Interworking Platform Support on page 16 Configuring FEC 128 VPLS Mesh Groups for LDP BGP Interworking on page 16 Configuring FEC 129 VPLS Mesh Groups for LDP BGP Interworking on page 17 Copyright © 2016, Juniper Networks, Inc.
Page 34: Ldp Bgp Interworking Platform Support
Configuring Integrated Routing and Bridging Support for LDP BGP Interworking with VPLS on page 18 Configuring Inter-AS VPLS with MAC Processing at the ASBR on page 18 LDP BGP Interworking Platform Support LDP BGP interworking is supported on the following Juniper Networks routers and routing platforms: M10i M40e...
Page 35: Configuring Fec 129 Vpls Mesh Groups For Ldp Bgp Interworking
VPLS network. To terminate multiple pseudowires at a single VPLS mesh group, include the statement: local-switching local-switching; You can include this statement at the following hierarchy levels: [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] Copyright © 2016, Juniper Networks, Inc.
Page 36: Configuring Integrated Routing And Bridging Support For Ldp Bgp Interworking With Vpls
VPLS Feature Guide for EX9200 Switches [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] Configuring Integrated Routing and Bridging Support for LDP BGP Interworking with VPLS Beginning with Junos OS Release 9.4, you can configure an integrated routing and bridging (IRB) interface on a router that functions as an autonomous system border router (ASBR) in an inter-AS VPLS environment between BGP-signaled VPLS and LDP-signaled VPLS.
Page 37: Configuring The Asbrs For Inter-As Vpls
You can include these statements at the following hierarchy levels: [edit routing-instances routing-instance-name protocols vpls] [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls] Related Example: Configuring BGP Autodiscovery for LDP VPLS Documentation Example: Configuring BGP Autodiscovery for LDP VPLS with User-Defined Mesh Groups Copyright © 2016, Juniper Networks, Inc.
Page 39: Assigning Routing Instances To Vpls
[ routing-instance-name ]; label-block-size size; mac-table-aging-time time; mac-table-size size; neighbor neighbor-id; no-control-word; no-tunnel-services; site site-name { active-interface any; primary interface-name; interface interface-name { interface-mac-limit limit; mesh-group mesh-group-name; multi-homing; Copyright © 2016, Juniper Networks, Inc.
Page 40 VPLS Feature Guide for EX9200 Switches site-identifier identifier; site-preference preference-value { backup; primary; site-range number; traceoptions { file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>; tunnel-services devices device-names; primary primary-device-name; vpls-id vpls-id; You can include this statement at the following hierarchy levels:...
Page 41: Configuring Bgp Signaling For Vpls
To configure the site name and the site identifier, include the and the site site-identifier statements: site site-name { interface interface-name { interface-mac-limit limit; site-identifier identifier; The numerical identifier can be any number from 1 through 65,534 that uniquely identifies the local VPLS site. Copyright © 2016, Juniper Networks, Inc.
Page 42: Configuring Automatic Site Identifiers For Vpls
VPLS Feature Guide for EX9200 Switches You can include these statements at the following hierarchy levels: [edit routing-instances routing-instance-name protocols vpls] [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls] Configuring Automatic Site Identifiers for VPLS When you enable automatic site identifiers, the Junos OS automatically assigns site identifiers to VPLS sites.
Page 43: Configuring The Site Range
The following configurations illustrate this concept. The configurations are for the VPLS routing instances on three routers, two spoke routers and one hub router: Copyright © 2016, Juniper Networks, Inc.
Page 44 VPLS Feature Guide for EX9200 Switches Router 1—spoke: routing-instance hub-and-spoke { no-local-switching; protocols { vpls { site-range 8; no-tunnel-services; site spoke-9 { site-identifier 9 { multi-homing; site-preference primary; site spoke-10 { site-identifier 10 { multi-homing; site-preference backup; Router 2—spoke: routing-instance hub-and-spoke { no-local-switching;...
Page 45: Configuring The Vpls Site Interfaces
65,535, the highest possible value, ensuring that the VPLS site is the most likely to be selected. For a list of hierarchy levels at which you can include the statement, see site-preference the statement summary section for this statement. Copyright © 2016, Juniper Networks, Inc.
Page 46: Configuring Ldp Signaling For Vpls
VPLS Feature Guide for EX9200 Switches Configuring LDP Signaling for VPLS You can configure LDP as the signaling protocol for a VPLS routing instance. This functionality is described in RFC 4762, Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling.
Page 47: Configuring Ldp Signaling For The Vpls Routing Instance
Be aware of the following behavior with regard to TLVs when configuring LDP-signaled VPLS in a network with equipment from other vendors: When a Juniper Network’s device receives a TLV with an empty address, LDP accepts the TLV. When a MAC address is withdrawn, LDP specifies a zero address (0.0.0.0) for the AddressList.
Page 48: Configuring Ldp Signaling On The Router
VPLS Feature Guide for EX9200 Switches You can include this statement at the following hierarchy levels: [edit routing-instances routing-instance-name protocols vpls] [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls] NOTE: ACX Series routers do not support the hierarchy. [edit logical-systems] To configure the VPLS routing instance to use LDP signaling, you also must include the...
Page 49: Configuring Vpls Routing Instance And Vpls Interface Connectivity
VPLS effectively provides a bridge between Ethernet networks. As a consequence, only two encapsulation types are available: —Ethernet ethernet —Ethernet virtual LAN (VLAN) ethernet-vlan If you do not specify an encapsulation type for the VPLS routing instance or the VPLS neighbor, ethernet is used. Copyright © 2016, Juniper Networks, Inc.
Page 50: Instance
VPLS Feature Guide for EX9200 Switches To specify an encapsulation type for the VPLS routing instance, include the statement: encapsulation-type encapsulation-type (ethernet | ethernet-vlan); You can include this statement at the following hierarchy levels: [edit routing-instances routing-instance-name protocols vpls] [edit logical-systems logical-system-name routing-instances routing-instance-name...
Page 51: Configuring The Size Of The Vpls Mac Address Table
To change the VPLS MAC table size for each VPLS or VPN routing instance, include the statement: mac-table-size mac-table-size size; You can include this statement at the following hierarchy levels: [edit routing-instances routing-instance-name protocols vpls] Copyright © 2016, Juniper Networks, Inc.
Page 52: Limiting The Number Of Mac Addresses Learned From An Interface
VPLS Feature Guide for EX9200 Switches [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls] NOTE: ACX Series routers do not support the hierarchy. [edit logical-systems] When you include the statement, the affected interfaces include all mac-table-size interfaces within the VPLS routing instance, including the local interfaces, the LSI interfaces, and the VT interfaces.
Page 53: Removing Addresses From The Mac Address Database
MAC address database that have been learned dynamically. With the dynamically learned MAC addresses removed, MAC address convergence requires less time to complete. You can clear dynamically learned MAC addresses from the MAC address database by including the mac-flush statement: mac-flush [ explicit-mac-flush-message-options ]; Copyright © 2016, Juniper Networks, Inc.
Page 54: Configuring Vpls Fast Reroute Priority
VPLS Feature Guide for EX9200 Switches To clear dynamically learned MAC addresses globally across all devices participating in the routing instance, you can include the statement at the following hierarchy levels: [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls] [edit routing-instances routing-instance-name protocols vpls]...
Page 55 { fast-reroute-priority high; To display the fast reroute priority setting configured for a VPLS routing instance, use operational command. For information about using this show route instance detail command, see the CLI Explorer Copyright © 2016, Juniper Networks, Inc.
Page 56: Specifying The Vt Interfaces Used By Vpls Routing Instances
VPLS Feature Guide for EX9200 Switches Specifying the VT Interfaces Used by VPLS Routing Instances By default, the Junos OS automatically selects one of the virtual tunnel (VT) interfaces available to the router for de-encapsulating traffic from a remote site. The Junos OS cycles through the currently available VT interfaces, regularly updating the list of available VT interfaces as new remote sites are discovered and new connections are brought up.
Page 57 PIM proxying method is not discussed here and is outside the scope of this document. For more information about PIM proxying, see PIM Snooping over VPLS Related Example: Configuring PIM Snooping for VPLS Documentation Copyright © 2016, Juniper Networks, Inc.
Page 58: Vpls Label Blocks Operation
VPLS Feature Guide for EX9200 Switches VPLS Label Blocks Operation A virtual private LAN service (VPLS) is a Layer 2 (L2) service that emulates a local area network (LAN) across a wide area network (WAN). VPLS labels are defined and exchanged in the Border Gateway Protocol (BGP) control plane.
Page 59: Requirements For Nlri Elements
VPLS update, it sends the same label block information to all other PE routers. Each PE router that receives the LB advertisement infers the label intended for Router PE-A by adding its own site ID to the label base. Copyright © 2016, Juniper Networks, Inc.
Page 60: Label Blocks In Junos Os
VPLS Feature Guide for EX9200 Switches In this manner, each receiving PE gets a unique label for PE-A for that VPLS. This simple method is enhanced by using a VE block offset (VBO). A label block is defined as: <Label Base (LB), VE block offset (VBO), VE block size (VBS)>...
Page 61: Figure 4: Label Mapping Example
262147 to send traffic to a PE router configured with site ID 18. However, only PE routers configured with site IDs 17 to 24 can use the label block shown to set up pseudowires. Related Example: Building a VPLS From Router 1 to Router 3 to Validate Label Blocks Documentation Copyright © 2016, Juniper Networks, Inc.
Page 62: Configuring The Label Block Size For Vpls
VPLS Feature Guide for EX9200 Switches Configuring the Label Block Size for VPLS VPLS MPLS packets have a two-label stack. The outer label is used for normal MPLS forwarding in the service provider’s network. If BGP is used to establish VPLS, the inner label is allocated by a PE router as part of a label block.
Page 63 VPLS routing-instance use the same Layer 2 VPN ID, the one that you configure at the hierarchy level. [edit routing-instances] Related Example: Configuring BGP Autodiscovery for LDP VPLS Documentation Copyright © 2016, Juniper Networks, Inc.
Page 65: Associating Interfaces With Vpls
You can include these statements at the following hierarchy levels: [edit interfaces interface-name] [edit logical-systems logical-system-name interfaces interface-name] NOTE: In the VPLS documentation, the word router in terms such as PE router is used to refer to any device that provides routing functions. Copyright © 2016, Juniper Networks, Inc.
Page 66: Configuring The Vpls Interface Name
VPLS Feature Guide for EX9200 Switches The following sections provide enough information to enable you to configure interfaces for VPLS routing. Configuring the VPLS Interface Name on page 48 Configuring VPLS Interface Encapsulation on page 48 Enabling VLAN Tagging on page 51...
Page 67: Associating Interfaces With Vpls
The traffic can then be forwarded to the PE router. Interfaces with VLAN VPLS encapsulation accept packets carrying standard TPID values only. On M Series routers (except the M320 router), the 4-port Fast Ethernet Copyright © 2016, Juniper Networks, Inc.
Page 68 VPLS Feature Guide for EX9200 Switches TX PIC and the 1-port, 2-port, and 4-port, 4-slot Gigabit Ethernet PICs can use the Ethernet VPLS encapsulation type. To configure the encapsulation type for logical interfaces, include the encapsulation statement: encapsulation (ether-vpls-over-atm-llc | vlan-vpls);...
Page 69: Enabling Vlan Tagging
You can bind a VLAN identifier to a logical interface by including the vlan-id statement: vlan-id number; You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] Copyright © 2016, Juniper Networks, Inc.
Page 70: Enabling Vlans For Hub And Spoke Vpls Networks
VPLS Feature Guide for EX9200 Switches You can also configure a logical interface to forward packets and learn MAC addresses within each VPLS routing instance configured with a VLAN ID that matches a VLAN ID specified in a list using the vlan-id-list statement.
Page 71 The aggregated Ethernet interface must also be configured for the VPLS routing instance as shown in the following example: [edit] routing-instances { green { instance-type vpls; interface ae0.0; route-distinguisher 10.255.234.34:1; vrf-target target:11111:1; protocols { vpls { site-range 10; site green3 { site-identifier 3; Copyright © 2016, Juniper Networks, Inc.
Page 72: Vpls And Aggregated Ethernet Interfaces
VPLS Feature Guide for EX9200 Switches Interface ae0.0 represents the aggregated Ethernet interface in the routing instance configuration. The VPLS routing instance configuration is otherwise standard. VPLS and Aggregated Ethernet Interfaces You can configure aggregated Ethernet interfaces between CE devices and PE routers for VPLS routing instances.
Page 73: Configuring Vpls Without A Tunnel Services Pic
An Enhanced FPC is required. ATM1 interfaces are not supported. Aggregated SONET/SDH interfaces are not supported as core-facing interfaces. Channelized interfaces are not supported as core-facing interfaces. GRE-encapsulated interfaces are not supported as core-facing interfaces. Copyright © 2016, Juniper Networks, Inc.
Page 75: Configuring Pseudowires
If the site preference is 0, the preference attribute is obtained from the local preference. If the preference values are the same, select the path with the lower router ID. Copyright © 2016, Juniper Networks, Inc.
Page 76 VPLS Feature Guide for EX9200 Switches If the router IDs are the same, the routes are from the same PE router and the advertisement is considered to be an update. The router ID corresponds to the value of the originator ID for the BGP attribute (if present). Otherwise, the IP address for the remote BGP peer is used.
Page 77: Configuring Static Pseudowires For Vpls
[edit routing-instances routing-instance-name protocols vpls neighbor address backup-neighbor address] hierarchy level and for a mesh group by including it at the [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name neighbor address] hierarchy level. Copyright © 2016, Juniper Networks, Inc.
Page 78 VPLS Feature Guide for EX9200 Switches For a list of hierarchy levels at which you can include the statement, see the static statement summary section for this statement. To enable static VPLS on a router, you need to either configure a virtual tunnel interface (requires the router to have a tunnel services PIC) or you can configure a label switching interface (LSI).
Page 79: Configuring Multihoming
Figure 5: CE Device Multihomed to Two PE Routers NOTE: In the VPLS documentation, the word router in terms such as PE router is used to refer to any device that provides routing functions. Copyright © 2016, Juniper Networks, Inc.
Page 80 VPLS Feature Guide for EX9200 Switches Figure 5 on page 61 illustrates how a CE device could be multihomed to two PE routers. Device CE1 is multihomed to Routers PE1 and PE2. Device CE2 has two potential paths to reach Device CE1, but only one path is active at any one time. If Router PE1 were the designated VPLS edge (VE) device (also called a designated forwarder), BGP would signal a pseudowire from Router PE3 to Router PE1.
Page 81: Vpls Multihoming Reactions To Network Failures
Layer 2 advertisements from that multihomed PE router. The remote PE routers each run the BGP and VPLS path selection procedures again and reroute their pseudowires to the backup multihomed PE router. Copyright © 2016, Juniper Networks, Inc.
Page 82: Bgp And Vpls Path Selection For Multihomed Pe Routers
VPLS Feature Guide for EX9200 Switches Alternatively, the remote PE routers could discover that the BGP next hop, represented by the failed multihomed PE router, is unreachable. For this case, the remote PE routers mark the Layer 2 routes advertised by the multihomed PE router as unreachable. The remote PE routers each run the BGP and VPLS path selection procedures again and reroute their pseudowires to the backup multihomed PE router.
Page 83 The PE router originated one of the multihomed advertisements and selected its own advertisement as the best path. This PE router has been selected as the designated VE device. Selection as the designated VE device triggers the creation of pseudowires to and from the other PE Copyright © 2016, Juniper Networks, Inc.
Page 84: Configuring Vpls Multihoming (Fec 128)
VPLS Feature Guide for EX9200 Switches routers in the VPLS network. When the remote customer site is also multihomed, the designated VE device triggers the creation of pseudowires to and from only the designated VE device for the remote site.
Page 85: Vpls Multihomed Site Configuration
Most of these statements are explained in more detail in the rest of this chapter. The following sections explain how to configure the statements that are specific to VPLS multihoming: Specifying an Interface as the Active Interface on page 68 Configuring Multihoming on the PE Router on page 68 Copyright © 2016, Juniper Networks, Inc.
Page 86: Specifying An Interface As The Active Interface
VPLS Feature Guide for EX9200 Switches Specifying an Interface as the Active Interface You need to specify one of the interfaces for the multihomed site as the primary interface. If there are multiple interfaces, the remaining interfaces are activated only when the primary interface goes down.
Page 87 Chapter 7: Configuring Multihoming Related VPLS Multihoming Overview on page 61 Documentation Example: VPLS Multihoming, Improved Convergence Time active-interface on page 109 multi-homing on page 141 Copyright © 2016, Juniper Networks, Inc.
Page 89: Configuring Point-To-Multipoint Lsps
Figure 7 on page Figure 6: Flooding Unknown VPLS Traffic Using Ingress Replication Figure 7: Flooding Unknown VPLS Traffic Using a Point-to-Multipoint LSP Copyright © 2016, Juniper Networks, Inc.
Page 90 VPLS Feature Guide for EX9200 Switches NOTE: In the VPLS documentation, the word router in terms such as PE router is used to refer to any device that provides routing functions. The point-to-multipoint LSP used for VPLS flooding can be either static or dynamic. In either case, for each VPLS routing instance, the PE router creates a dedicated point-to-multipoint LSP.
Page 91: Configuring Static Point-To-Multipoint Flooding Lsps
[edit routing-instances routing-instance-name provider-tunnel rsvp-te label-switched-path-template] hierarchy level, causes the point-to-multipoint LSPs to be created with default parameters. The default parameters are for a minimally configured point-to-multipoint LSP. The name of this Copyright © 2016, Juniper Networks, Inc.
Page 92: Configuring Dynamic Point-To-Multipoint Flooding Lsps With A Preconfigured Template
VPLS Feature Guide for EX9200 Switches point-to-multipoint LSP is also generated automatically and is based on the following model: id:vpls:router-id:routing-instance-name The following command output for illustrates how a show show mpls lsp p2mp point-to-multipoint flood LSP name could appear if you configure the...
Page 93: Mapping Vpls Traffic To Specific Lsps
{ install-nexthop lsp-regex [ "^a-to-b2$" "^a-to-c2$" ]; accept; community company-1 members target:11111:1; community company-2 members target:11111:2; You can include the statement at the following hierarchy policy-statement vpls-priority levels: [edit policy-options] [edit logical-systems logical-system-name policy-options] Copyright © 2016, Juniper Networks, Inc.
Page 94 VPLS Feature Guide for EX9200 Switches Include the statement to apply the policy to the forwarding table: export vpls-priority export vpls-priority; You can include this statement at the following hierarchy levels: [edit routing-options forwarding-table] [edit logical-systems logical-system-name routing-options forwarding-table] For more information about how to configure routing policies, see the Routing Policies, Firewall Filters, and Traffic Policers Feature Guide.
Page 95: Configuring Bgp Path Selection For Layer 2 Vpns
CHAPTER 9 Configuring BGP Path Selection for Layer 2 VPNs Enabling BGP Path Selection for Layer 2 VPNs and VPLS on page 78 Copyright © 2016, Juniper Networks, Inc.
Page 96: Enabling Bgp Path Selection For Layer 2 Vpns And Vpls
PE router could receive two or more separate but apparently valid paths to the same CE device. By default, Juniper Networks routers use just the designated forwarder path selection algorithm to select the best path to reach each Layer 2 VPN or VPLS routing instance destination (for more information, see “VPLS Path Selection Process for PE Routers”...
Page 97 Related Understanding BGP Path Selection Documentation VPLS Path Selection Process for PE Routers on page 57 VPLS Feature Guide for EX9200 Switches l2vpn-use-bgp-rules Copyright © 2016, Juniper Networks, Inc.
Page 99: Configuring Load Balancing And Performance
To optimize VPLS traffic flows across multiple paths, include the family multiservice statement at the hierarchy level: [edit forwarding-options hash-key] family multiservice destination-mac; label-1; label-2; payload { ip { layer-3 { (destination-ip-only | source-ip-only); Copyright © 2016, Juniper Networks, Inc.
Page 100 VPLS Feature Guide for EX9200 Switches layer-3-only; layer-4; source-mac; symetric-hash { complement; You can configure one or more of the following options to load-balance using the specified packet information: —Include the destination-address MAC information in the hash key destination-mac for Layer 2 load balancing.
Page 101 For more information about how to configure per-packet load balancing, see theRouting Policies, Firewall Filters, and Traffic Policers Feature Guide. Related Configuring VPLS Load Balancing Based on IP and MPLS Information Documentation Configuring VPLS Load Balancing on MX Series 3D Universal Edge Routers Copyright © 2016, Juniper Networks, Inc.
Page 103: Configuring Class Of Service And Firewall Filters In Vpls
Configuring Firewall Filters and Policers for VPLS You can configure both firewall filters and policers for VPLS. Firewall filters allow you to filter packets based on their components and to perform an action on packets that match Copyright © 2016, Juniper Networks, Inc.
Page 104: Configuring A Vpls Filter
VPLS Feature Guide for EX9200 Switches the filter. Policers allow you to limit the amount of traffic that passes into or out of an interface. VPLS filters and policers act on a Layer 2 frame that includes the media access control (MAC) header (after any VLAN rewrite or other rules are applied), but does not include the cyclical redundancy check (CRC) field.
Page 105: Configuring An Interface-Specific Counter For Vpls
VPLS FTF as an input filter. To specify a VPLS FTF, include the statement at the filter input [edit routing-instance hierarchy level: routing-instance-name forwarding-options family vpls] [edit routing-instance routing-instance-name forwarding-options family vpls] Copyright © 2016, Juniper Networks, Inc.
Page 106: Changing Precedence For Spanning-Tree Bpdu Packets
VPLS Feature Guide for EX9200 Switches filter input filter-name; Changing Precedence for Spanning-Tree BPDU Packets Spanning tree BPDU packets are automatically set to a high precedence. The queue number on these packets is set to 3. On M Series routers (except the M320 router) by default, a queue value of 3 indicates high precedence.
Page 107: Configuring A Filter For Flooded Traffic
When specifying policing bandwidth, the VPLS policer considers all Layer 2 bytes in a packet to determine the packet length. To configure a VPLS policer, include the statement at the hierarchy policer [edit firewall] level: [edit firewall] Copyright © 2016, Juniper Networks, Inc.
Page 108: Firewall Filter Match Conditions For Vpls Traffic
VPLS Feature Guide for EX9200 Switches policer policer-name { bandwidth-limit limit; burst-size-limit limit; then action; To apply a VPLS policer to an interface, include the statement: policer policer { input input-policer-name; output output-policer-name; You can include this statement at the following hierarchy levels:...
Page 109: Table 5: Firewall Filter Match Conditions For Vpls Traffic
VPLS prefix lists support only IPv4 addresses. IPv6 addresses included in a VPLS prefix list will be discarded. destination-prefix-list name (MX Series routers and EX Series switches only) Do not match destination prefixes in the specified list. For more information, see the match condition. except destination-prefix-list Copyright © 2016, Juniper Networks, Inc.
Page 110 VPLS Feature Guide for EX9200 Switches Table 5: Firewall Filter Match Conditions for VPLS Traffic (continued) Match Condition Description (MX Series routers and EX Series switches only) Match the Differentiated Services code point dscp number (DSCP). The DiffServ protocol uses the type-of-service (ToS) byte in the IP header. The most significant 6 bits of this byte form the DSCP.
Page 111 Do not match this range of values range-except forwarding-class class Match the forwarding class. Specify assured-forwarding best-effort expedited-forwarding , or network-control Do not match the forwarding class. For details, see the match condition. forwarding-class-except forwarding-class class Copyright © 2016, Juniper Networks, Inc.
Page 112 VPLS Feature Guide for EX9200 Switches Table 5: Firewall Filter Match Conditions for VPLS Traffic (continued) Match Condition Description Match the ICMP message code field. icmp-code message-code If you configure this match condition, we recommend that you also configure the next-header match condition in the same term.
Page 113 (MX Series routers and EX Series switches only) Do not match on the IP protocol field. ipv6-destination-address (MX Series only) 128-bit address that is the final destination node address for this packet. address Copyright © 2016, Juniper Networks, Inc.
Page 114 VPLS Feature Guide for EX9200 Switches Table 5: Firewall Filter Match Conditions for VPLS Traffic (continued) Match Condition Description (MX Series only) Match the IPv6 destination addresses in a named-list. ipv6-destination-prefix-list named-list protocol (MX Series only) Match IPv6 next header protocol type.
Page 115 (MX Series only) Match the IPv6 address in a named-list. ipv6-prefix-list address (MX Series only) 128-bit address that is the originating source node address for this packet. ipv6-source-address (MX Series only) Match the IPv6 source address in a named-list. ipv6-source-prefix-list named-list Copyright © 2016, Juniper Networks, Inc.
Page 116 VPLS Feature Guide for EX9200 Switches Table 5: Firewall Filter Match Conditions for VPLS Traffic (continued) Match Condition Description number (MX Series only) Differentiated Services code point (DSCP). The DiffServ protocol uses the ipv6-traffic-class type-of-service (ToS) byte in the IP header. The most significant 6 bits of this byte form the DSCP.
Page 117 (MX Series routers and EX Series switches only) Do not match on the TCP or UDP source port source-port-except number field. You cannot specify the match conditions in the same term. port source-port Copyright © 2016, Juniper Networks, Inc.
Page 118 VPLS Feature Guide for EX9200 Switches Table 5: Firewall Filter Match Conditions for VPLS Traffic (continued) Match Condition Description (MX Series routers and EX Series switches only) Match the source prefixes in the specified prefix source-prefix-list name list. Specify a prefix list name defined at the...
Page 119 VLAN Ethernet type field of a VPLS packet. vlan-ether-type value Do not match on the VLAN Ethernet type field of a VPLS packet. vlan-ether-type-except value Related Guidelines for Configuring Firewall Filters Documentation Firewall Filter Terminating Actions Firewall Filter Nonterminating Actions Copyright © 2016, Juniper Networks, Inc.
Page 121: Monitoring And Tracing Vpls
—VPLS connections (events and state changes) connections error —Error conditions —VPLS advertisements received or sent using BGP nlri route —Trace-routing information —VPLS topology changes caused by reconsideration or advertisements topology received from other PE routers using BGP Copyright © 2016, Juniper Networks, Inc.
Page 123: Configuration Statements And Operational Commands
PART 3 Configuration Statements and Operational Commands Configuration Statements on page 107 Operational Commands on page 169 Copyright © 2016, Juniper Networks, Inc.
Page 125: Configuration Statements
(VPLS Multihoming for FEC 128) on page 141 multi-homing (VPLS Multihoming for FEC 129) on page 142 neighbor (Protocols VPLS) on page 143 no-tunnel-services on page 145 peer-active (VPLS Multihoming for FEC 129) on page 146 Copyright © 2016, Juniper Networks, Inc.
Page 126 VPLS Feature Guide for EX9200 Switches peer-as (VPLS) on page 147 ping-interval on page 148 preference (Interface-Level Preference for VPLS Multihoming for FEC 129) on page 149 preference (Site-Level Preference for VPLS Multihoming for FEC 129) on page 150 primary (VPLS Multihoming) on page 151...
Page 127: Active-Interface (Vpls Multihoming)
[edit routing-instances instance-name protocols vpls multi-homing] hierarchy level. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Specifying an Interface as the Active Interface on page 68 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 128: Any (Vpls Multihoming)
VPLS Feature Guide for EX9200 Switches any (VPLS Multihoming) Syntax any; Hierarchy Level [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-homing active-interface], [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-homing site site-name active-interface], [edit routing-instances instance-name protocols vpls multi-homing active-interface],...
Page 129: Automatic-Site-Id
—The time in seconds to wait at startup to receive all the VPLS information for the route targets configured on the other PE routers included in the VPLS routing instance. Copyright © 2016, Juniper Networks, Inc.
Page 130: Best-Site
VPLS Feature Guide for EX9200 Switches Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring Automatic Site Identifiers for VPLS on page 24 Documentation best-site Syntax best-site; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols...
Page 131: Bfd-Liveness-Detection (Layer 2 Vpn And Vpls)
The remaining statements are explained separately. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Copyright © 2016, Juniper Networks, Inc.
Page 132: Connectivity-Type
VPLS Feature Guide for EX9200 Switches Related Configuring BFD for Layer 2 VPN and VPLS Documentation Example: Configuring BFD for Static Routes for Faster Network Failure Detection connectivity-type Syntax connectivity-type (ce | irb | permanent); Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols...
Page 133: Encapsulation (Physical Interface)
TCC version ( )—Similar to CCC and has the same configuration cisco-hdlc-tcc restrictions, but used for circuits with different media on either side of the connection. —Use Cisco-compatible HDLC framing on CCC circuits. cisco-hdlc-ccc Copyright © 2016, Juniper Networks, Inc.
Page 134 VPLS Feature Guide for EX9200 Switches —Use Cisco-compatible HDLC framing on TCC circuits for connecting cisco-hdlc-tcc different media. ethernet-bridge —Use Ethernet bridge encapsulation on Ethernet interfaces that have bridging enabled and that must accept all packets. —Use Ethernet CCC encapsulation on Ethernet interfaces that must accept ethernet-ccc packets carrying standard Tag Protocol ID (TPID) values.
Page 135 CCC, Layer 2 virtual private networks (VPNs), and VPLS encapsulations on a single physical port. If you configure flexible Ethernet services encapsulation on the physical interface, VLAN IDs from 1 through 511 are no longer reserved for normal VLANs. Copyright © 2016, Juniper Networks, Inc.
Page 136 VPLS Feature Guide for EX9200 Switches —For IQ interfaces only, use flexible Frame Relay encapsulation when flexible-frame-relay you want to configure multiple per-unit Frame Relay encapsulations. This encapsulation type allows you to configure any combination of TCC, CCC, and standard Frame Relay encapsulations on a single physical port. Also, each logical interface can have any DLCI value from 1 through 1022.
Page 137 Previously, it was possible to commit family inet this invalid configuration. Required Privilege interface—To view this statement in the configuration. Level interface-control—To add this statement to the configuration. Copyright © 2016, Juniper Networks, Inc.
Page 138 VPLS Feature Guide for EX9200 Switches Related Configuring Interface Encapsulation on Physical Interfaces Documentation Configuring CCC Encapsulation for Layer 2 VPNs Configuring Layer 2 Switching Cross-Connects Using CCC Configuring TCC Encapsulation for Layer 2 VPNs and Layer 2 Circuits Configuring ATM Interface Encapsulation...
Page 139: Encapsulation-Type (Layer 2 Vpns)
—CESOP-based Layer 2 VPN —Cisco Systems–compatible HDLC cisco-hdlc —Ethernet ethernet —Ethernet VLAN ethernet-vlan —Frame Relay frame-relay —Frame Relay port mode frame-relay-port-mode —Layer 2.5 interworking VPN interworking —PPP —SATSOP-E1–based Layer 2 VPN satsop-e1 Copyright © 2016, Juniper Networks, Inc.
Page 140 VPLS Feature Guide for EX9200 Switches —SATSOP-E3–based Layer 2 VPN satsop-e3 —SATSOP-T1–based Layer 2 VPN satsop-t1 —SATSOP-T3–based Layer 2 VPN satsop-t3 Default: For VPLS networks, the default encapsulation type is ethernet Required Privilege routing—To view this statement in the configuration.
Page 141: Family Multiservice
(M120 and M320 routers only)—Include the second MPLS label in the hash key. label-2 If both label-1 label-2 are specified, the entire first label and the first 16 bits of the second label are hashed. Copyright © 2016, Juniper Networks, Inc.
Page 142 VPLS Feature Guide for EX9200 Switches (MX Series, M120, and M320 routers only)—Include the packet’s IP payload in payload the hash key. (MX Series, M120, and M320 routers only)—Include the IP address of the IPv4 or IPv6 payload in the hash key.
Page 143 Configuring Load Balancing Based on MAC Addresses Documentation Configuring VPLS Load Balancing Based on IP and MPLS Information Configuring VPLS Load Balancing on MX Series 3D Universal Edge Routers Configuring VPLS Load Balancing on page 81 Copyright © 2016, Juniper Networks, Inc.
Page 144: Fast-Reroute-Priority
VPLS Feature Guide for EX9200 Switches fast-reroute-priority Syntax fast-reroute-priority (high | low | medium); Hierarchy Level [edit forwarding-options] [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options], [edit routing-instances routing-instance-name forwarding-options] Release Information Statement introduced in Junos OS Release 9.5. Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Page 145: Identifier (Vpls Multihoming For Fec 129)
—Number that identifies the multihomed site. Range: 1 through 65535 Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Example: Configuring VPLS Multihoming (FEC 129) Documentation Copyright © 2016, Juniper Networks, Inc.
Page 146: Interface (Routing Instances)
Related Configuring Routing Instances on PE Routers in VPNs Documentation Configuring EVPN Routing Instances Configuring EVPN Routing Instances on EX9200 Switches interface (VPLS Routing Instances) on page 130 Copyright © 2016, Juniper Networks, Inc.
Page 147: Interface (Vpls Multihoming For Fec 129)
Options —Name of the interface (for example, interface-name ge-0/1/0.1 Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Example: Configuring VPLS Multihoming (FEC 129) Documentation Copyright © 2016, Juniper Networks, Inc.
Page 148: Interface (Vpls Routing Instances)
VPLS Feature Guide for EX9200 Switches interface (VPLS Routing Instances) Syntax interface interface-name { mac-pinning; interface-mac-limit limit; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls site site-name], [edit routing-instances routing-instance-name protocols vpls],...
Page 149: Interface-Mac-Limit (Vpls)
Related Configuring EVPN Routing Instances Documentation Configuring EVPN Routing Instances on EX9200 Switches Limiting the Number of MAC Addresses Learned from an Interface on page 34 interface mac-table-size on page 139 Copyright © 2016, Juniper Networks, Inc.
Page 150: L2Vpn-Id
VPLS Feature Guide for EX9200 Switches l2vpn-id Syntax l2vpn-id (as-number:id | ip-address:id); Hierarchy Level [edit logical-systems logical-system-name routing-instances instance-name], [edit routing-instances instance-name] Release Information Statement introduced in Junos OS Release 10.4R2. Description Specify a globally unique Layer 2 VPN community identifier for the instance.
Page 151: Label-Block-Size
Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring the Label Block Size for VPLS on page 44 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 152: Label-Switched-Path-Template (Multicast)
VPLS Feature Guide for EX9200 Switches label-switched-path-template (Multicast) Syntax label-switched-path-template { (default-template | lsp-template-name); Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel rsvp-te], [edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel ingress-replication label-switched-path], [edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel selective group address source source-address rsvp-te],...
Page 153: Local-Switching (Vpls)
(which has a limit of 14). Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring Switching Between Pseudowires Using VPLS Mesh Groups on page 17 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 154: Mac-Flush
VPLS Feature Guide for EX9200 Switches mac-flush Syntax mac-flush [ explicit-mac-flush-message-options ]; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name], [edit routing-instances routing-instance-name protocols vpls], [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] Release Information Statement introduced in Junos OS Release 10.0.
Page 155 Level routing-control—To add this statement to the configuration. Related Configuring VPLS Routing Instances on page 21 Documentation Configuring Interoperability Between BGP Signaling and LDP Signaling in VPLS on page 15 Copyright © 2016, Juniper Networks, Inc.
Page 156: Mac-Table-Aging-Time
VPLS Feature Guide for EX9200 Switches mac-table-aging-time Syntax mac-table-aging-time time; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls], [edit routing-instances routing-instance-name protocols vpls] [edit bridge-options], [edit routing-instances routing-instance-name protocols evpn] NOTE: For MX Series routers, the configuration statement is supported at...
Page 157: Mac-Table-Size
Related Configuring EVPN Routing Instances Documentation Configuring EVPN Routing Instances on EX9200 Switches Configuring the Size of the VPLS MAC Address Table on page 33 Configuring Improved VPLS MAC Address Learning on T4000 Routers with Type 5 FPCs enhanced-mode evpn Copyright ©...
Page 158: Mesh-Group (Protocols Vpls)
VPLS Feature Guide for EX9200 Switches mesh-group (Protocols VPLS) Syntax mesh-group mesh-group-name { interface interface-name; l2vpn-id (as-number:id | ip-address:id); local-switching; mac-flush [ explicit-mac-flush-message-options ]; neighbor address {...}; peer-as all; pseudowire-status-tlv hot-standby-vc-on; route-distinguisher (as-number:id | ip-address:id); vpls-id number; vrf-export [ policy-names ];...
Page 159: Multi-Homing (Vpls Multihoming For Fec 128)
Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring Multihoming on the PE Router on page 68 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 160: Multi-Homing (Vpls Multihoming For Fec 129)
VPLS Feature Guide for EX9200 Switches multi-homing (VPLS Multihoming for FEC 129) Syntax multi-homing { peer-active; site site-name { active-interface interface-name { any; primary interface-name; identifier identifier; interface interface-name { preference preference-value; peer-active; preference (preference-value | backup | primary); Hierarchy Level...
Page 161: Neighbor (Protocols Vpls)
Junos OS Release 10.0. option was added in Junos OS Release 14.2 for MX Series routers to provide vpls-id-list support for multiple pseudowires between the same pair of PEs in LDP-VPLS. Copyright © 2016, Juniper Networks, Inc.
Page 162 VPLS Feature Guide for EX9200 Switches Description Specify each of the PE routers participating in the VPLS domain. Configuring this statement enables LDP for signaling VPLS. NOTE: In the VPLS documentation, the word router in terms such as PE router is used to refer to any device that provides routing functions.
Page 163: No-Tunnel-Services
Related Configuring VPLS Without a Tunnel Services PIC on page 55 Documentation Configuring Static Pseudowires for VPLS on page 59 Configuring EXP-Based Traffic Classification for VPLS on page 85 Copyright © 2016, Juniper Networks, Inc.
Page 164: Peer-Active (Vpls Multihoming For Fec 129)
VPLS Feature Guide for EX9200 Switches peer-active (VPLS Multihoming for FEC 129) Syntax peer-active; Hierarchy Level [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-homing], [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-homing site site-name], [edit routing-instances instance-name protocols vpls multi-homing],...
Page 165: Peer-As (Vpls)
—This option is required. All peer routers, the ASBRs, are placed within the same VPLS mesh group. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring Inter-AS VPLS with MAC Processing at the ASBR on page 18 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 166: Ping-Interval
VPLS Feature Guide for EX9200 Switches ping-interval Syntax ping-interval seconds; Hierarchy Level [edit logical-systems logical-system-name protocols l2circuit neighbor address interface interface-name oam], [edit logical-systems logical-system-name routing-instances instance-name protocols l2vpn oam], [edit logical-systems logical-system-name routing-instances instance-name protocols vpls neighbor address oam],...
Page 167: Preference (Interface-Level Preference For Vpls Multihoming For Fec 129)
—Preference value for the interface. preference-value Range: 1 through 65535 Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Example: Configuring VPLS Multihoming (FEC 129) Documentation Copyright © 2016, Juniper Networks, Inc.
Page 168: Preference (Site-Level Preference For Vpls Multihoming For Fec 129)
VPLS Feature Guide for EX9200 Switches preference (Site-Level Preference for VPLS Multihoming for FEC 129) Syntax preference (preference-value | backup | primary); Hierarchy Level [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-homing site site-name], [edit routing-instances instance-name protocols vpls multi-homing site site-name] Release Information Statement introduced in Junos OS Release 12.3.
Page 169: Primary (Vpls Multihoming)
Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Specifying an Interface as the Active Interface on page 68 Documentation any on page 110 Copyright © 2016, Juniper Networks, Inc.
Page 170: Rsvp-Te (Routing Instances Provider Tunnel)
VPLS Feature Guide for EX9200 Switches rsvp-te (Routing Instances Provider Tunnel) Syntax rsvp-te { label-switched-path-template { (default-template | lsp-template-name); static-lsp lsp-name; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name provider-tunnel], [edit routing-instances routing-instance-name provider-tunnel] Release Information Statement introduced in Junos OS Release 8.3.
Page 171: Site (Vpls Multihoming For Fec 128)
Specify the site name and site identifier for a site. Allows you to configure a remote site ID for remote sites. Options —Name of the site. site-name The remaining statements are explained separately. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Copyright © 2016, Juniper Networks, Inc.
Page 172: Site (Vpls Multihoming For Fec 129)
VPLS Feature Guide for EX9200 Switches site (VPLS Multihoming for FEC 129) Syntax site site-name { active-interface interface-name { any; primary interface-name; identifier identifier; interface interface-name { preference preference-value; peer-active; preference (preference-value | backup | primary); Hierarchy Level [edit logical-systems logical-system-name routing-instances instance-name protocols vpls...
Page 173: Site-Identifier (Vpls)
16-bit number greater than zero. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring the VPLS Site Name and Site Identifier on page 23 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 174: Site-Preference
VPLS Feature Guide for EX9200 Switches site-preference Syntax site-preference preference-value { backup; primary; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols l2vpn site site-name], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls site site-name], [edit routing-instances routing-instance-name protocols l2vpn site site-name],...
Page 175: Site-Range
—Maximum number of site identifiers. We recommend using the default value. number Range: 1 through 65,534 Default: 65,534 Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring the Site Range on page 25 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 176: Static (Protocols Vpls)
VPLS Feature Guide for EX9200 Switches static (Protocols VPLS) Syntax static { incoming-label label; outgoing-label label; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls neighbor address], [edit logical-systems logical-system-name routing-instances routing-instance-name protocols...
Page 177: Template
Specify a template for the dynamically generated point-to-multipoint LSPs used for VPLS flooding. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring Dynamic Point-to-Multipoint Flooding LSPs with a Preconfigured Template Documentation on page 74 Copyright © 2016, Juniper Networks, Inc.
Page 178: Traceoptions (Protocols Vpls)
VPLS Feature Guide for EX9200 Switches traceoptions (Protocols VPLS) Syntax traceoptions { file filename <files number> <size size> <world-readable | no-world-readable>; flag flag <flag-modifier> <disable>; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls], [edit routing-instances routing-instance-name protocols vpls] Release Information Statement introduced before Junos OS Release 7.4.
Page 179 —Allow any user to read the log file. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Tracing VPLS Traffic and Operations on page 103 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 180: Tunnel-Services (Routing Instances Vpls)
VPLS Feature Guide for EX9200 Switches tunnel-services (Routing Instances VPLS) Syntax tunnel-services { devices device-names; primary primary-device-name; Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls], [edit routing-instances routing-instance-name protocols vpls] Release Information Statement introduced before Junos OS Release 7.4.
Page 181: Vlan-Id
Level interface-control—To add this statement to the configuration. Related Configuring Interfaces for VPLS Routing on page 47 Documentation Configuring VLAN IDs for Logical Interfaces on page 51 Copyright © 2016, Juniper Networks, Inc.
Page 182: Vlan-Tagging
For Fast Ethernet and Gigabit Ethernet interfaces, aggregated Ethernet interfaces configured for VPLS, and pseudowire subscriber interfaces, enable the reception and transmission of 802.1Q VLAN-tagged frames on the interface. NOTE: On EX Series switches except for EX4300 and EX9200 switches, the statements cannot be configured vlan-tagging family ethernet-switching on the same interface.
Page 183: Vpls (Interfaces)
Specify the VPLS protocol family information for the logical interface. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring Interfaces for VPLS Routing on page 47 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 184: Vpls (Routing Instance)
VPLS Feature Guide for EX9200 Switches vpls (Routing Instance) Syntax vpls { mac-pinning; active-interface any; primary interface-name; community COMM; connectivity-type (ce | irb); control-word; encapsulation-type ethernet; ignore-encapsulation-mismatch; ignore-mtu-mismatch; import-labeled-routes [ routing-instance-name ]; interface interface-name; interface-mac-limit limit; label-block-size size; mac-flush [ explicit-mac-flush-message-options ];...
Page 185 Configure a virtual private LAN service (VPLS) routing instance. The remaining statements are explained separately. Required Privilege routing—To view this statement in the configuration. Level routing-control—To add this statement to the configuration. Related Configuring VPLS Routing Instances on page 21 Documentation Copyright © 2016, Juniper Networks, Inc.
Page 186: Vpls-Id
VPLS Feature Guide for EX9200 Switches vpls-id Syntax vpls-id vpls-id; Hierarchy Level [edit logical-systems logical-system-name routing-instances instance-name protocols l2vpn], [edit logical-systems logical-system-name routing-instances instance-name protocols l2vpn mesh-group mesh-group-name], [edit logical-systems logical-system-name routing-instances instance-name protocols vpls], [edit logical-systems logical-system-name routing-instances instance-name protocols vpls...
Page 187: Operational Commands
—Clear statistics and protocol database information. clear —Trace mtrace packets from source to receiver. mtrace —Perform real-time debugging of various software components, including monitor the routing protocols and interfaces. —Determine the reachability of a remote network host. ping Copyright © 2016, Juniper Networks, Inc.
Page 188: Commonly Used Operational Mode Commands
VPLS Feature Guide for EX9200 Switches —Display the current configuration and information about interfaces, routing show protocols, routing tables, routing policy filters, system alarms, and the chassis. test —Test the configuration and application of policy filters and autonomous system (AS) path regular expressions.
Page 189 Routes that form a label-switched path show route label-switched-path RSVP Status of interfaces on which RSVP is running show rsvp interface Currently active RSVP sessions show rsvp session RSVP packet and error counters show rsvp statistics Copyright © 2016, Juniper Networks, Inc.
Page 190: Example: Running Operational Mode Commands On Logical Systems
VPLS Feature Guide for EX9200 Switches Example: Running Operational Mode Commands on Logical Systems This example shows how to set the CLI to a specified logical system view, run operational-mode commands for the logical system, and then return to the main router view.
Page 191: Example: Viewing Bgp Trace Files On Logical Systems
Verification on page 178 Requirements You must have the privilege for the logical system. view Configure a network, such as the BGP network shown in Example: Configuring Internal BGP Peering Sessions on Logical Systems. Copyright © 2016, Juniper Networks, Inc.
Page 192 VPLS Feature Guide for EX9200 Switches Overview Logical systems have their individual directory structure created in the directory. It contains the following /var/logical-systems/logical-system-name subdirectories: /config —Contains the active configuration specific to the logical system. —Contains system log and tracing files specific to the logical system.
Page 193 192.168.40.4 (Internal AS 17): code 6 (Cease) subcode 4 (Administratively Reset), Reason: Management session cleared BGP neighbor Aug 10 17:14:22.831851 bgp_send: sending 21 bytes to 192.168.40.4 (Internal AS 17) Aug 10 17:14:22.831901 Aug 10 17:14:22.831901 BGP SEND 192.168.6.5+53889 -> 192.168.40.4+179 Copyright © 2016, Juniper Networks, Inc.
Page 194 VPLS Feature Guide for EX9200 Switches Aug 10 17:14:22.831959 BGP SEND message type 3 (Notification) length 21 Aug 10 17:14:22.831999 BGP SEND Notification code 6 (Cease) subcode 4 (Administratively Reset) Filter the output of the log file. user@host> file show /var/logical-systems/A/log/bgp-log | match "flags 0x40"...
Page 195 10k files 2; flag update detail; flag all; local-address 192.168.6.5; export send-direct; neighbor 192.163.6.4; neighbor 192.168.40.4; To reactivate logging, use the configuration-mode statement. activate [edit protocols bgp group internal-peers] user@host:A# activate traceoptions user@host:A# commit Copyright © 2016, Juniper Networks, Inc.
Page 196: Example: Configuring System Logging On Logical Systems
VPLS Feature Guide for EX9200 Switches Results From configuration mode, confirm your configuration by entering the show logical-systems A protocols bgp group internal-peers command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
Page 197 To configure system logging: Configure trace operations on the logical system. [edit logical-systems lsys1 system syslog] user@host# set host 10.209.10.69 ftp critical user@host# set allow-duplicates user@host# set file lsys1-file1 daemon error user@host# set file lsys1-file1 firewall critical Copyright © 2016, Juniper Networks, Inc.
Page 198 VPLS Feature Guide for EX9200 Switches If you are done configuring the device, commit the configuration. [edit] user@host# commit user@host# exit Results From configuration mode, confirm your configuration by entering the show logical-systems command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Juniper EX9200 Features Manual

Chapter 1 Introduction to VPLS and Supported Standards

Chapter 2 VPLS Configuration Overview

Chapter 3 Configuring Signaling Protocols for VPLS

Chapter 4 Assigning Routing Instances to VPLS

Chapter 5 Associating Interfaces with VPLS

Chapter 6 Configuring Pseudowires

Chapter 7 Configuring Multihoming

Chapter 8 Configuring Point-To-Multipoint Lsps

Chapter 9 Configuring BGP Path Selection for Layer 2 Vpns

Chapter 10 Configuring Load Balancing and Performance

Chapter 11 Configuring Class of Service and Firewall Filters in VPLS

Chapter 12 Monitoring and Tracing VPLS

Chapter 13 Configuration Statements

Chapter 14 Operational Commands

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Juniper EX9200

Summary of Contents for Juniper EX9200

Table of Contents