User manual JUNIPER NETWORKS JUNOSE 11.1.X BGP AND MPLS CONFIGURATION

[. . . ] JUNOSeTM Software for E SeriesTM Routing Platforms BGP and MPLS Configuration Guide Release 11. 1. x Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www. juniper. net Published: 2010-03-30 Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. [. . . ] 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. Point-to-Multipoint LSPs Overview 263 JUNOSe 11. 1. x BGP and MPLS Configuration Guide Figure 61 on page 264 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 264 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. Egress LSRs can also be directly connected to the ingress LSR. 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 264 Point-to-Multipoint LSPs Overview g016488 LSR 8 Chapter 2: MPLS Overview 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. You can alternatively configure the branch LSPs as a static path. 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. Penultimate hop popping (PHP) is the default when RSVP-TE or LDP is the signaling protocol. If the egress router advertises an implicit null label to achieve PHP on an upstream neighbor, enable IP IGMP on the static physical interface on which the unlabeled multicast packet is received by the router by using the ip igmp interface configuration command. host1(config-if)#ip igmp If the egress router advertises an explicit null or non-null label to its upstream neighbour to include a label in all MPLS packets, complete the following steps to configure an E Series router as an egress router: 1. Create a profile by using the profile command. Add commands to enable IP IGMP and IP processing on the loopback interface in the profile. host1(config)#profile mplsdynip host1(config-profile)#ip igmp host1(config-profile)#ip unnumbered loopback 0 2. Create a dynamic IPv4 interface on top of MPLS major interfaces and specify the profile that you created in the previous step to set attributes for this interface. Point-to-Multipoint LSPs Configuration 265 JUNOSe 11. 1. x BGP and MPLS Configuration Guide host1(config)#mpls create-dynamic-interfaces ip on-major-interfaces profile dynip For all types of labels that are advertised for the LSR that is the egress router for the prefix, you must complete the following steps, in addition to those detailed earlier, on the E Series router: 1. Enable IGMP on the interface which owns the route to the source by using the ip igmp command. [. . . ] 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 109 on page 684 lists the show l2vpn interface command output fields. Table 109: 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 684 Monitoring L2VPN Interfaces for VPWS Chapter 14: Monitoring VPWS Table 109: 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. Number of packets, bytes, errors and discards received on the interface Number of packets, bytes, errors and discards sent from the interface Number of messages queued to be sent on the interface Type of traffic class configured for traffic on the interface ATM virtual circuit to which the interface is bound Length of all messages queued to be sent to on this connection, in bytes Number of packets and bytes that have been forwarded Number of committed packets and bytes that have been dropped Number of conformed packets and bytes that have been dropped Administrative state Operational state Operational MTU MPLS shim interface UID Lower interface UID Condensed location Received Sent queue traffic-class bound to Queue length Forwarded Dropped committed Dropped conformed packets Dropped exceeded Number of exceeded packets and bytes that have been dropped Monitoring L2VPN Interfaces for VPWS 685 JUNOSe 11. 1. x BGP and MPLS Configuration Guide Related Topics show l2vpn interface Monitoring MPLS Forwarding Table for VPWS Purpose Display information about MPLS labels that are being used for forwarding. The brief keyword displays summary information for the MPLS labels. To display MPLS forwarding information for a particular label: host1#show mpls forwarding label 17 In label: 17 Label space: platform label space Owner: bgp Spoof check: router ERX-pe Action: MPLS next-hop: 28, l2transport to ATM2/0. 100 Statistics: 0 in pkts 0 in Octets 0 in errors 0 in discard pkts Action To display brief information about MPLS forwarding for all labels: host1:pe1# show mpls forwarding brief In Label Owner -------- -------17 bgp 18 bgp 26 ldp 27 ldp 28 ldp 29 ldp 30 ldp 31 ldp 46 ldp L2transport Action ------------------------------------------------------------l2transport to ATM2/0. 100 l2transport to ATM2/0. 12 lookup on inner header/label swap to 39 on ATM2/0. 20, nbr 20. 20. 20. 2 swap to 41 on ATM2/0. 20, nbr 20. 20. 20. 2 lookup on inner header/label swap to 43 on ATM2/0. 20, nbr 20. 20. 20. 2 swap to 44 on ATM2/0. 20, nbr 20. 20. 20. 2 swap to 40 on ATM2/0. 20, nbr 20. 20. 20. 2 Interface Owner Action --------------- -------- ----------------------------------------ATM2/0. 12 bgp swap to 801028, push 39 on ATM2/0. 20, nbr 20. 20. 20. 2 ATM2/0. 100 bgp swap to 801024, push 39 on ATM2/0. 20, nbr 20. 20. 20. 2 To display MPLS forwarding information for a particular interface: host1:pe#show mpls forwarding interface atm2/0. 100 In label: n/a, ATM2/0. 100 Owner: bgp Spoof check: router erx-pe Action: MPLS next-hop: 27, label 801024, resolved by MPLS next-hop 8 MPLS next-hop: 8, resolved by MPLS next-hop 9, peer 10. 3. 2. 2 686 Monitoring MPLS Forwarding Table for VPWS Chapter 14: Monitoring VPWS MPLS next-hop: 9, label 39 on ATM2/0. 20, nbr 10. 20. 20. 2 Statistics: Disabled Meaning Table 110 on page 687 lists the show mpls forwarding command output fields. Table 110: show mpls forwarding Output Fields Field Name In label Out label Label space Owner Field Description Label sent to upstream neighbor for route Label received from downstream neighbor for route Label space in which the label is assigned Signaling protocol that placed the label in the forwarding table: BGP, LDP, or RSVP-TE Type and location of spoof checking performed on the MPLS packet, router, or interface Action taken for MPLS packets arriving with that label Number of packets sent with the label Number of octets sent with the label Number of packets that are dropped for some reason before being sent Number of packets that are discarded due to lack of buffer space before being sent Layer 2 interface that is a member of an L2VPN Spoof check Action in pkts in Octets in errors in discardPkts Interface Related Topics show mpls forwarding Monitoring MPLS Forwarding Table for VPWS 687 JUNOSe 11. 1. x BGP and MPLS Configuration Guide 688 Monitoring MPLS Forwarding Table for VPWS Part 6 Index Index on page 691 Index 689 JUNOSe 11. 1. x BGP and MPLS Configuration Guide 690 Index Index Symbols 802. 3ad switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 AS-path, BGP access lists, modifying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 as-set keyword (aggregate-address). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 ATM (Asynchronous Transfer Mode) AAL0 encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 AAL5 encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 Martini encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 over MPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 passthrough for ATM over MPLS. . . . . . . . . . . . . . . . . 512, 515 VCC cell relay encapsulation configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 ATM cells concatenation of multiple for transportation over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 transported over a single pseudowire, subset of discarded on he remote PE device. . . . . . . . . . . . . . . 526 atm commands atm cell-packing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 atm mcpt-timers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 atm pvc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534, 536 ATM line modules and transport of a subset of ATM VCs over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 hardware limitations and support of multiple VCs over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 ATM Martini cell packing timer expired time interval and forwarding of MPLs packets. . . . . . . . . . . . . . . . . . 526 for concatenation of multiple cells and transmission over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 ATM n-to-one VCC cell transport (0x0009) pseudowire (PW) type used by LDP for subset of ATM VCs over a pseudowire transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 A access lists, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 assigning weights to neighbors. . . . . . . . . . . . . . . . . . . . . . . . . . . 112 distributing neighbor information. . . . . . . . . . . . . . . . . . . . . . . . . 83 access-list command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83, 85 address families. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 L2VPN. . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380, 579, 600, 649 multicast IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380 multicast IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380 route-target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 380 unicast IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380 unicast IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380 VPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380, 579, 600 VPN-IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380 VPN-IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380 VPWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 380, 649, 664 address-family command. . . . . . . . . . . . . 45, 154, 395, 443, 600 for L2VPN address family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 for VPWS address family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 administrative distance BGP, setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 admission control, MPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 advertise-map keyword (aggregate-address). . . . . . . . . . . . . . . . 61 aggregate addresses BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 aggregate-address command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 aggregation, LDP FEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 aggregator, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 append-after command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 APS/MSP (Automatic Protect Switching/Multiplex Section Protection). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 areas, OSPF defining. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608 AS (autonomous system). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 advertising networks in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 confederation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 IGP (interior gateway protocol). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 managing a large-scale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 AS path filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Index 691 JUNOSe 11. 1. x BGP and MPLS Configuration Guide ATM ports changed to LOS state and multiple VCs over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 configuring cell concatenation parameters requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 connectivity between two of them emulated using multiple VCs transport over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 not changed to LOS state during a failure on the pseudowire. . . . . . . . . . . . . . 526 ATM virtual circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 adding MPLS Martini circuit configuration for multiple VCs transport over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 and emulation of connectivity between ATM ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 based on RFC 4816 exception with subset of ATM cells transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 concatenation of multiple cells requirements for configuring. . . . . . . . . . . . . . . . . . . . . . . 528 configuring a subset of using the mpls-relay atm vpi-range command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 configuring VPI/VCI ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 hardware limitations of ATM LMs and transport of multiple VCs over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 in Martini topologies transportation over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 received on an ATM port opening VCs on the SAR scheduler. . . . . . . . . . . . . . 524 transmission of a subset of ATM cells over a pseudowire deployment scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 transmission of multiple cells over a pseudowire high availability and. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 limit on total number of. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 performance impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 unified ISSU and. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528 verifying cell concatenation. . . . . . . . . . . . . . . . . . . . . . . . . 568 verifying VCI/VPI ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 transmission of multiple VCs over a single pseudowire interoperation with cell relay on a subinterface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 transport of multiple cells over a pseudowire and ATM n-to-one VCC cell transport (0x0009) pseudowire (PW) type . . . . . . . . . . . . . . 527 transportation of cells from multiple circuits over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 transportation of multiple ATM cells concatetation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526 atomic-aggregate, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 attribute-map keyword (aggregate-address). . . . . . . . . . . . . . . . . 61 authentication BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 MPLS LDP MD5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 RSVP-TE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 auto-summary command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 autoconfiguration, LDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 autonomous system. [. . . ]