User manual JUNIPER NETWORKS JUNOSE SOFTWARE FOR E SERIES 11.3.X BGP AND MPLS CONFIGURATION GUIDE 2010-10-12

[. . . ] JunosETM Software for E SeriesTM Broadband Services Routers BGP and MPLS Configuration Guide Release 11. 3. x Published: 2010-10-12 Copyright © 2010, Juniper Networks, Inc. Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www. juniper. net Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. [. . . ] If the LSR recovers within the proper interval, the entries are no longer marked as stale and are used as they were before the LDP connection failed. If the LSR does not recover in time, the entries are deleted. LDP graceful restart supports only the downstream-unsolicited mode of label distribution. Successful operation of LDP graceful restart requires that stateful SRP switchover (high availability) be configured on the router. Although you can configure LDP graceful restart 256 Copyright © 2010, Juniper Networks, Inc. Chapter 3: MPLS Overview if stateful SRP switchover is not configured on the router, the graceful restart capability will not function. You can configure an LSR to restart itself gracefully and to support graceful restart in its neighbors (helper mode), or helper mode alone. In either case, the LSR includes the fault tolerant (FT) session TLV in the LDP initialization messages it sends at session startup. The TLV includes values for the reconnect timeout and the recovery time. When both graceful restart and the helper mode are disabled, the LSR does not include the TLV in its LDP initialization messages. The configurable reconnect time specifies how long you want the LSR's neighbors to wait for the LSR to resume exchanging LDP messages with the neighbors after the connection failure. The reconnect timeout value is nonzero when graceful restart is enabled. When you disable graceful restart but enable helper mode, the reconnect timeout is set to zero to announce to the neighbors that the LSR does not preserve MPLS forwarding state across the restart. The presence of the TLV indicates to the neighbors that the LSR supports them if they gracefully restart. That is, the LSR in this case waits for a gracefully restarting neighbor to resume sending messages. Table 54 on page 257 summarizes the states possible for LDP graceful restart. Table 54: Summary of LDP Graceful Restart States Graceful restart enabled? Yes No No Helper mode enabled? Yes Yes No FT TLV sent to neighbor? Yes Yes No Reconnect timeout value sent in TLV Nonzero Zero ­ The recovery time specifies how long the LSR retains its MPLS forwarding state across the restart. When the LSR restarts, it marks the forwarding state entries as stale. The forwarding state holding timer begins counting down from the configured recovery time value. If the timer expires before the restart completes, the LSR deletes all stale entries. When the LSR sends new LDP initialization messages to its neighbors, the messages contain the current value of the timer. When the LSR restarts, if a neighbor of the LSR has previously received the FT session TLV from the LSR with a nonzero reconnect timeout value, the neighbor retains the label mapping information that it has previously received from the LSR and marks that information as stale. Alternatively, if the neighbor received an FT session TLV with a timeout value of zero (indicating that only helper mode is enabled) or no TLV at all (indicating that both graceful restart and helper mode are disabled), it deletes the label mapping information. Also when the LSR restarts, the neighbor sets its neighbor liveness timer to the lesser of the two values, the reconnect timeout value and its own configurable neighbor liveness Copyright © 2010, Juniper Networks, Inc. 257 JunosE 11. 3. x BGP and MPLS Configuration Guide timer value. [. . . ] 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 Action Copyright © 2010, Juniper Networks, Inc. 683 JunosE 11. 3. x BGP and MPLS Configuration Guide 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 Meaning Table 141 on page 684 lists the show l2vpn interface command output fields. Table 141: show l2vpn interface Output Fields Field Name MPLS shim interface ATM circuit type Member of L2VPN instance Local site ID Remote site ID Control word send sequence numbers Relay format Field Description Type and specifier for MPLS shim interface Type of ATM circuit 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 Administrative state Operational state 684 Copyright © 2010, Juniper Networks, Inc. Chapter 16: Monitoring VPWS Table 141: show l2vpn interface Output Fields (continued) Field Name Operational MTU Field Description 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 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 Related Documentation · 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: Action Copyright © 2010, Juniper Networks, Inc. 685 JunosE 11. 3. x BGP and MPLS Configuration Guide 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 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 MPLS next-hop: 9, label 39 on ATM2/0. 20, nbr 10. 20. 20. 2 Statistics: Disabled Meaning Table 142 on page 686 lists the show mpls forwarding command output fields. Table 142: show mpls forwarding Output Fields Field Name In label Out label Field Description Label sent to upstream neighbor for route Label received from downstream neighbor for route 686 Copyright © 2010, Juniper Networks, Inc. Chapter 16: Monitoring VPWS Table 142: show mpls forwarding Output Fields (continued) Field Name Label space Owner Field Description 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 Documentation · show mpls forwarding Copyright © 2010, Juniper Networks, Inc. 687 JunosE 11. 3. x BGP and MPLS Configuration Guide 688 Copyright © 2010, Juniper Networks, Inc. PART 6 Index · Index on page 691 Copyright © 2010, Juniper Networks, Inc. 689 JunosE 11. 3. x BGP and MPLS Configuration Guide 690 Copyright © 2010, Juniper Networks, Inc. Index Symbols 802. 3ad switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545 AS-path, BGP access lists, modifying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 as-set keyword (aggregate-address). . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 ATM (Asynchronous Transfer Mode) AAL0 encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 AAL5 encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 Martini encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 over MPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 passthrough for ATM over MPLS. . . . . . . . . . . . . . . . . . . 516, 519 VCC cell relay encapsulation configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542 overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 ATM cells concatenation of multiple for transportation over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 transported over a single pseudowire, subset of discarded on he remote PE device. . . . . . . . . . . . . . 530 atm commands atm cell-packing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542 atm mcpt-timers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542 atm pvc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540, 542 ATM line modules and transport of a subset of ATM VCs over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 hardware limitations and support of multiple VCs over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 ATM Martini cell packing timer expired time interval and forwarding of MPLs packets. . . . . . . . . . . . . . . . . 530 for concatenation of multiple cells and transmission over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 A access lists, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 assigning weights to neighbors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 distributing neighbor information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 access-list command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82, 83 address families. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 L2VPN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386, 587, 604, 651 multicast IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386 multicast IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386 route-target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 386 unicast IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386 unicast IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386 VPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386, 587, 604 VPN-IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386 VPN-IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386 VPWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 386, 651, 664 address-family command. . . . . . . . . . . . . 45, 151, 401, 447, 604 for L2VPN address family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 for VPWS address family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664 administrative distance BGP, setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 admission control, MPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 advertise-map keyword (aggregate-address). . . . . . . . . . . . . 61 aggregate-address command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 aggregation, LDP FEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 aggregator, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 append-after command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 APS/MSP (Automatic Protect Switching/Multiplex Section Protection). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 areas, OSPF defining. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612 AS (autonomous system). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 advertising networks in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 confederation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 IGP (interior gateway protocol). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 managing a large-scale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 AS path filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Copyright © 2010, Juniper Networks, Inc. 691 JunosE 11. 3. x BGP and MPLS Configuration Guide ATM n-to-one VCC cell transport (0x0009) pseudowire (PW) type used by LDP for subset of ATM VCs over a pseudowire transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531 ATM ports changed to LOS state and multiple VCs over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 configuring cell concatenation parameters requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 connectivity between two of them emulated using multiple VCs transport over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 not changed to LOS state during a failure on the pseudowire. . . . . . . . . . . . . . 530 ATM virtual circuits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 adding MPLS Martini circuit configuration for multiple VCs transport over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 and emulation of connectivity between ATM ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 based on RFC 4816 exception with subset of ATM cells transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 concatenation of multiple cells requirements for configuring. . . . . . . . . . . . . . . . . . . . . . . . . . 532 configuring a subset of using the mpls-relay atm vpi-range command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 configuring VPI/VCI ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 hardware limitations of ATM LMs and transport of multiple VCs over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 in Martini topologies transportation over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 received on an ATM port opening VCs on the SAR scheduler. . . . . . . . . . . . . 529 transmission of a subset of ATM cells over a pseudowire deployment scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565 transmission of multiple cells over a pseudowire high availability and. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 limit on total number of. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 performance impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 unified ISSU and. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 verifying cell concatenation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 verifying VCI/VPI ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 transmission of multiple VCs over a single pseudowire interoperation with cell relay on a subinterface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531 transport of multiple cells over a pseudowire and ATM n-to-one VCC cell transport (0x0009) pseudowire (PW) type . . . . . . . . . . . 531 transportation of cells from multiple circuits over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 transportation of multiple ATM cells concatetation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 atomic-aggregate, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 attribute-map keyword (aggregate-address). . . . . . . . . . . . . . 61 authentication BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 MPLS LDP MD5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 RSVP-TE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 auto-summary command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 autoconfiguration, LDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 autonomous system. [. . . ]