User manual JUNIPER NETWORKS JUNOSE SOFTWARE FOR E SERIES 11.0.X BGP AND MPLS CONFIGURATION GUIDE 2009-12-30

[. . . ] JUNOSeTM Software for E SeriesTM Routing Platforms BGP and MPLS Configuration Guide Release 11. 0. x Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www. juniper. net Published: 2009-12-30 Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered 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. [. . . ] Link protection can provide a bypass LSP for each of the branch LSPs that make up the point-to-multipoint LSP. If any of the primary paths fail, traffic can be quickly switched to the bypass path. You can configure branch LSPs statically, dynamically, or as a combination of static and dynamic LSPs. You can enable graceful restart on point-to-multipoint LSPs. Using E Series Routers as Egress LSRs You can use E Series routers as egress LSRs in a point-to-multipoint LSP. To create a point-to-multipoint LSP and to use E Series routers as egress LSRs, no special configuration is required. The configuration that you made for point-to-point LSPs, which enables MPLS RSVP-TE on the interface that must signal an LSP in that virtual router context, is sufficient. 258 Point-to-Multipoint LSPs Overview Chapter 2: MPLS Overview Figure 61 on page 259 shows a point-to-multipoint LSP with multiple egress LSRs. The multicast source sends a packet to the ingress router, LSR 1, which in turn sends the packet on the point-to-multipoint LSP to the branch router, LSR 2. The branch router, LSR 2, is connected to another branch router, LSR 3. Here, LSR 3 is not directly connected to the ingress router, LSR 1, but only to the branch router, LSR 2. These branch routers, in turn, replicate the packet and forward it to E Series routers, LSRs 4 through 7, configured as egress LSRs. The configuration shown in Figure 61 on page 259 is an example of an LSP that contains segments that run from ingress LSR to one or more branch and egress LSRs. For example, sub-LSPs exist between LSR 1 and LSR 2, and between LSR 2 and LSR 4. The sub-LSP between LSR 2 and LSR 4 is an egress sub-LSP that transmits the replicated packet from branch router, LSR 2, to egress E Series router, LSR 4. In this figure, the connection between LSR 8 and LSR 1 is an example of this type. NOTE: You cannot use E Series routers as core or ingress LSRs. You need to use Juniper Networks routers running JUNOS software to function as core or ingress LSRs in the point-to-multipoint LSP. Figure 61: Simple MPLS Domain Egress routers Branch routers Sub-LSP Ingress router LSR 2 Multicast source LSR 1 LSR 5 LSR 4 LSR 6 LSR 3 LSR 7 Use the show mpls rsvp tunnels p2mp role tail command to view the status and configuration information for point-to-multipoint egress tunnels. Related Topics Monitoring Status and Configuration for MPLS Tunnels show mpls tunnels g016488 LSR 8 Point-to-Multipoint LSPs Overview 259 JUNOSe 11. 0. x BGP and MPLS Configuration Guide Point-to-Multipoint LSPs Configuration To set up a point-to-multipoint LSP, you configure the primary LSP from the ingress router and the branch LSPs that carry traffic to the egress routers. The configuration of the primary point-to-multipoint LSP is similar to a signaled LSP. In addition to the conventional LSP configuration, you specify a path name on the primary LSP and this same path name on each branch LSP. By default, the branch LSPs are dynamically signaled by means of CSPF and require no configuration. Because E Series routers can only function as egress routers, you must use M-series routers running JUNOS software as ingress routers to enable point-to-multipoint LSPs to send packets through the network to the endpoints connected to the egress routers. Observe the following guidelines to deliver multicast data using point-to-multipoint LSPs on the egress E Series routers: The IP interface on which the packet arrives must be an IGMP-owned interface. An IGMP-owned interface refers to an interface in which IGMP is the only multicast protocol enabled. The actual route to the source must be through an IGMP-owned interface. Configuring an E Series Router as an Egress Router The configuration of an E Series router as an egress router depends on the type of label advertised for the LSR that is the egress router for the prefix. [. . . ] Priority value for the VPWS instance for the multihomed site; displayed only when the value for the Multi-homed field is Yes Route targets configured for the VPWS instance Layer 2 interface that is a member of the VPWS instance Local customer site ID configured on the layer 2 interface Remote customer site ID configured on the layer 2 interface Administrative state of the connection, disabled or enabled Operational state of the connection, up or down Site-Priority Route Targets Interface Local-Site-Id Remote-Site-Id Admin state Oper state Monitoring VPWS Instances 677 JUNOSe 11. 0. x BGP and MPLS Configuration Guide Related Topics show l2vpn instance Monitoring L2VPN Interfaces for VPWS Purpose Display configuration and status information for interfaces on the router that are that are configured to be members of VPWS L2VPNs in the current VR. You can display information for a specific L2VPN interface, for all L2VPN interfaces in the specified VPWS instance, or for all L2VPN interfaces in all VPWS instances. The detail keyword displays detailed information about the specified L2VPN interface or all L2VPN interfaces. To display L2VPN interface information for a particular VPWS instance: host1#show l2vpn interface instance l2vpn1 MPLS shim interface ATM2/0. 100 ATM circuit type is AAL5 Member of L2VPN instance l2vpn1 Local site ID is 1 Remote site ID is 2 Control word is preferred by default Do send sequence numbers by default Relay format is atm-aal5-sdu-vcc by default Administrative state is enabled Operational state is up Operational MTU is 9180 MPLS shim interface UID is 0x2d000007 Lower interface UID is 0x0b000005 Condensed location is 0x00020000 Received: 3 packets 204 bytes 19 errors 0 discards Sent: 0 packets 0 bytes 0 errors 0 discards queue 0: traffic class best-effort, bound to atm-vc ATM2/0. 100 Queue length 0 bytes Forwarded packets 0, bytes 0 Dropped committed packets 0, bytes 0 Dropped conformed packets 0, bytes 0 Dropped exceeded packets 0, bytes 0 Action Meaning Table 108 on page 678 lists the show l2vpn interface command output fields. Table 108: show l2vpn interface Output Fields Field Name MPLS shim interface ATM circuit type Field Description Type and specifier for MPLS shim interface Type of ATM circuit 678 Monitoring L2VPN Interfaces for VPWS Chapter 14: Monitoring VPWS Table 108: show l2vpn interface Output Fields (continued) Field Name Member of L2VPN instance Local site ID Remote site ID Control word send sequence numbers Relay format Field Description Name of the VPWS instance to which the interface belongs Local customer site ID configured on the interface Remote customer site ID configured on the interface Local preference for the control word, preferred or not preferred Local preference for sequence numbers, send or don't send Type of signaling and encapsulation used by the router for layer 2 traffic Administrative state of the interface, enabled or disabled Operational state of the interface, up or down Maximum allowable size in bytes of the maximum transmission unit for the interface UID automatically assigned to the MPLS shim interface when it is created UID automatically assigned to the MPLS major interface when it is created Internal, platform-dependent, 32-bit representation of the interface location, used by Juniper Networks Customer support for troubleshooting. [. . . ]