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

[. . . ] JunosETM Software for E SeriesTM Broadband Services Routers BGP and MPLS Configuration Guide Release 11. 2. x Published: 2010-07-16 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. [. . . ] This address is made available to the nodes upstream of the target node, using signaling protocols, such as RSVP. This sub-TLV may be used to trace a specific egress node in a point-to-multipoint LSP. Node Address P2MP Responder Identifier Sub-TLVs You can use the IPv4 or IPv6 Node Address P2MP Responder Identifier sub-TLVs in an echo request that contains the RSVP P2MP Session or Multicast LDP FEC Stack sub-TLV. A node that receives an echo request with this sub-TLV present responds only if the address in the sub-TLV corresponds to any address that is local to the node. This address in the sub-TLV might be of any physical interface or the router ID of the node itself. The address in this sub-TLV can be the address of any transit, branch, or egress node for that point-to-multipoint LSP. Related Topics · · Troubleshooting MTU Problems in Point-to-Point LSPs on page 379 Ping Extensions for Point-to-Multipoint LSPs Connectivity Verification at Egress Nodes on page 246 Point-to-Multipoint LSPs Connectivity Verification at Egress Nodes Overview on page 246 Verifying and Troubleshooting MPLS Connectivity on page 370 · · LDP Discovery Mechanisms LDP uses two different mechanisms for peer discovery. Peer discovery removes the need to explicitly configure the label-switching peers for an LSR. 250 Copyright © 2010, Juniper Networks, Inc. Chapter 3: MPLS Overview · · LDP uses the basic discovery mechanism to discover directly connected LDP peers. LDP uses the extended discovery mechanism to discover peers that are not directly connected. LDP Basic Discovery Mechanism To discover directly connected peers, LSRs periodically send out LDP link hellos on the interface. The link hellos are contained in UDP packets that are addressed to the well-known LDP discovery port, 646. The destination address for the ports is 224. 0. 0. 2. Using this port and address ensures that the hellos are sent to all routers on the interface's subnet. The link hello includes the LDP identifier for the label space that the LSR intends to use for the interface. In the JunosE implementation, this is always the platform label space, so the LDP identifier specifies the LSR ID and a value of 0 for the label space. The link hello also includes other information, such as the hello hold time configured on the interface. The hello hold time specifies how long an LSR maintains a record of hellos received from potential peers. When an LSR receives a link hello, it identifies the sending LSR as a potential LDP peer on that interface. The LSRs form a hello adjacency to keep track of each other. The basic discovery mechanism is enabled by default when you enable LDP on an interface. You can configure the link hellos in the LDP profile with the hello hold-time and hello interval commands. You can configure a transport IP address to be globally included in link hellos with the mpls ldp discovery transport-address command. LDP Extended Discovery Mechanism To discover LDP peers that are not directly connected, LSRs periodically send out LDP targeted hellos to potential peers. The targeted hellos are contained in UDP packets that are addressed to the well-known LDP discovery port, 646. The destination address for the ports is a specific targeted address. [. . . ] 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 Action Copyright © 2010, Juniper Networks, Inc. 675 JunosE 11. 2. x BGP and MPLS Configuration Guide 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 676 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 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 Administrative state Operational state Operational MTU MPLS shim interface UID Lower interface UID 676 Copyright © 2010, Juniper Networks, Inc. Chapter 16: Monitoring VPWS Table 141: show l2vpn interface Output Fields (continued) Field Name Condensed location Field Description 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 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 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 Copyright © 2010, Juniper Networks, Inc. 677 JunosE 11. 2. x BGP and MPLS Configuration Guide 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 678 lists the show mpls forwarding command output fields. Table 142: 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 Spoof check Action in pkts 678 Copyright © 2010, Juniper Networks, Inc. Chapter 16: Monitoring VPWS Table 142: show mpls forwarding Output Fields (continued) Field Name in Octets in errors Field Description 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 in discardPkts Interface Related Topics · show mpls forwarding Copyright © 2010, Juniper Networks, Inc. 679 JunosE 11. 2. x BGP and MPLS Configuration Guide 680 Copyright © 2010, Juniper Networks, Inc. PART 6 Index · Index on page 683 Copyright © 2010, Juniper Networks, Inc. 681 JunosE 11. 2. x BGP and MPLS Configuration Guide 682 Copyright © 2010, Juniper Networks, Inc. Index Symbols 802. 3ad switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539 AS-path, BGP access lists, modifying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 as-set keyword (aggregate-address). . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 ATM (Asynchronous Transfer Mode) AAL0 encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 AAL5 encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 Martini encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 over MPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 passthrough for ATM over MPLS. . . . . . . . . . . . . . . . . . . 512, 515 VCC cell relay encapsulation configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535 overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 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 A access lists, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 assigning weights to neighbors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 distributing neighbor information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 access-list command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82, 83 address families. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 L2VPN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384, 579, 596, 643 multicast IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384 multicast IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384 route-target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 384 unicast IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384 unicast IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384 VPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384, 579, 596 VPN-IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384 VPN-IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384 VPWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 150, 384, 643, 656 address-family command. . . . . . . . . . . . 45, 151, 398, 444, 596 for L2VPN address family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656 for VPWS address family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604 AS (autonomous system). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 advertising networks in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 confederation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 IGP (interior gateway protocol). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 managing a large-scale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 AS path filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Copyright © 2010, Juniper Networks, Inc. 683 JunosE 11. 2. 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 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. . . . . . . . . . . . . . . . . . . . . . . . . . . 566 verifying VCI/VPI ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 transmission of multiple VCs over a single pseudowire interoperation with cell relay on a subinterface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 MPLS LDP MD5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 RSVP-TE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 auto-summary command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 autoconfiguration, LDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 autonomous system. [. . . ]