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. 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. [. . . ] Because the route to the source can change dynamically, we recommend that you enable IGMP on all interfaces of the router or, at least, on all interfaces that might be the next hop interface to the source. Disable the multicast reverse path forwarding (RPF) check policy for all the streams that will be delivered on the point-to-multipoint LSP by using the ip multicast-routing disable-rpf-check command. For more information, see Enabling and Disabling RPF Checks in the JUNOSe Multicast Routing Configuration Guide. 2. Related Topics Point-to-Multipoint LSPs Overview on page 257 show mpls tunnels Point-to-Multipoint LSPs Configuration 261 JUNOSe 11. 0. x BGP and MPLS Configuration Guide 262 Point-to-Multipoint LSPs Configuration Chapter 3 Configuring MPLS This chapter describes how to configure Multiprotocol Label Switching (MPLS) on the router, and contains the following sections: Basic MPLS Configuration Tasks on page 264 MPLS Global Configuration Tasks on page 265 LDP and RSVP-TE Interface Profile Configuration Tasks on page 269 MPLS Interface Configuration Tasks on page 270 MPLS Tunnel Configuration Tasks on page 272 MPLS Tunnel Profile Configuration Tasks on page 273 Configuring Explicit Routing for MPLS on page 275 Additional LDP Configuration Tasks on page 277 Configuring LDP FEC Deaggregation on page 277 Configuring LDP Graceful Restart on page 278 Configuring LDP Autoconfiguration on page 279 Configuring LDP-IGP Synchronization on page 280 Configuring LDP MD5 Authentication on page 281 Controlling LDP Label Distribution on page 282 Additional RSVP-TE Configuration Tasks on page 282 Configuring RSVP MD5 Authentication on page 283 Configuring RSVP-TE Fast Rerouting with RSVP-TE Bypass Tunnels on page 284 Configuring RSVP-TE Hello Messages to Determine Peer Reachability on page 287 Configuring RSVP-TE Graceful Restart on page 288 Configuring RSVP-TE Hellos Based on Node IDs on page 289 Configuring the BFD Protocol for RSVP-TE on page 290 Configuring IGPs and MPLS on page 291 Configuring MPLS and Differentiated Services on page 295 Configuring the Tunneling Model for Differentiated Services on page 295 Configuring EXP Bits for Differentiated Services on page 296 Example Differentiated Services Application and Configuration on page 296 263 JUNOSe 11. 0. x BGP and MPLS Configuration Guide Classifying Traffic for Differentiated Services on page 299 Example Traffic Class Configuration for Differentiated Services on page 304 Basic MPLS Configuration Tasks Configuring an MPLS network includes a number of tasks: To configure an MPLS network: Configure settings common to all MPLS usage on a given LSR. See "MPLS Global Configuration Tasks" on page 265. (Optional) Configure LDP or RSVP-TE interface profiles. See "LDP and RSVP-TE Interface Profile Configuration Tasks" on page 269. Configure each interface on an LSR that uses MPLS. See "MPLS Interface Configuration Tasks" on page 270. Configure MPLS tunnels or topology-driven LSPs. See "MPLS Tunnel Configuration Tasks" on page 272. (Optional) Configure a profile that contains settings to be used by multiple MPLS tunnels. See "MPLS Tunnel Profile Configuration Tasks" on page 273. Many users find it convenient to configure MPLS by completing the tasks in each set of tasks before moving to the next set. However, you do not have to complete the tasks in the listed order. For example, you might perofrm all the pure MPLS tasks relevant to your network and then perform all the relevant LDP or RSVP-TE tasks. The type of network you want to implement determines which sets of tasks you must complete, as indicated in Table 27 on page 264. Table 27: Configuration Tasks by Type of Network Traffic Engineering Network Yes Optional Yes Yes Yes Topology-Driven Network (Best-Effort, Hop-by-Hop, LDP) Yes Optional Yes No No Task Set Global Interface Profile Interface Tunnel Tunnel Profile In addition to the basic configuration tasks, you might need to perform other LDP or RSVP-TE configuration tasks. 264 Basic MPLS Configuration Tasks Chapter 3: Configuring MPLS To configure LDP and RSVP-TE, depending on your network topology and needs: Configure LDP features depending on your network design. See "Additional LDP Configuration Tasks" on page 277. Configure RSVP-TE features depending on your network design. See "Additional RSVP-TE Configuration Tasks" on page 282. MPLS Global Configuration Tasks Complete these tasks to configure a virtual router as an LSR. You perform these commands in Global Configuration mode. The following sequence is arbitrary; you can perform these tasks in any order. Your choice of label distribution protocol determines whether the LDP or RSVP-TE global tasks are appropriate for your network design. MPLS global configuration tasks include the following sets of tasks: MPLS Global Tasks on page 265 LDP Global Tasks on page 266 RSVP-TE Global Tasks on page 268 MPLS Global Tasks In a typical network, you perform only the first task. You might also perform the optional configuration tasks, but typically do not need to do so. 1. Enable MPLS on a virtual router. host1(config)#mpls 2. (Optional) Configure the time-to-live field placed in the MPLS header when a label is first added to an IP packet. host1(config)#mpls ip propagate-ttl forwarded 3. (Optional) Configure the tunneling model for differentiated services. See "Configuring MPLS and Differentiated Services" on page 295 for more information and command descriptions. host1(config)#mpls tunnel-model uniform 4. (Optional) Specify whether to use the TOS value (the default condition) or the UPC value of the packet as the value of the EXP bits when the router acts as an LER. host1(config)#mpls copy-upc-to-exp 5. (Optional) Specify whether the EXP bits for VPN MPLS labels can be modified by EXP bit mapping or by policy for differentiated services. host1(config)#mpls preserve-vpn-exp MPLS Global Configuration Tasks 265 JUNOSe 11. 0. x BGP and MPLS Configuration Guide 6. (Optional) Specify whether to create dynamic IP interfaces on top of MPLS major interfaces and optionally what profile to use for them. host1(config)#mpls create-dynamic-interfaces ip on-major-interfaces profile v4intf LDP Global Tasks Typically, you do not configure anything for LDP at the global level, but you can perform the following optional tasks. 1. (Optional) Enable LDP and topology-driven LSP. Any LDP-related command creates LDP implicitly, negating the need to issue this command. host1(config)#mpls ldp 2. (Optional) Configure the redistribution of IGP routes to LDP. host1(config)#mpls ldp redistribute ospf route-map boston5 3. (Optional) Configure a global LDP profile that specifies how long an LSR maintains link hello records before another link hello is sent, the interval between link hellos, or both. host1(config)#mpls ldp interface profile ldp1 host1(config-ldp)#hello hold-time 55 host1(config-ldp)#hello interval 10 4. (Optional) Configure lists of peer addresses that targeted hello messages are sent to or accepted from. host1(config)#mpls ldp targeted-hello send list 10. 21. 5. 87 host1(config)#mpls ldp targeted-hello receive list 192. 168. 45. 25 NOTE: The mpls ldp targeted-hello receive list command is unnecessary if you configure the mpls ldp targeted-hello send list command. (Optional) Configure the hold time and interval values for targeted hello messages used in LDP extended discovery. host1(config)#mpls ldp targeted-hello holdtime 90 host1(config)#mpls ldp targeted-hello interval 30 6. 5. (Optional) Configure LDP session retry values. host1(config)#mpls ldp session retry-time 2 host1(config)#mpls ldp session retries 1800 7. (Optional) Configure the period that LDP negotiates with its peer for which the LDP session is maintained in the absence of any LDP messages. host1(config)#mpls ldp session holdtime 1800 8. (Optional) Configure the interval at which LDP sends session keepalive messages. 266 LDP Global Tasks Chapter 3: Configuring MPLS host1(config)#mpls ldp session keepalive-time 180 9. (Optional) Specify an IP address to be advertised to peers as the transport address in discovery hello messages. host1(config)#mpls ldp discovery transport-address 192. 168. 34. 2 10. (Optional) Configure independent control as the method of label distribution that LDP uses. host1(config)#mpls ldp independent-control 11. [. . . ] 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. 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 679 JUNOSe 11. 0. 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 680 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 109 on page 681 lists the show mpls forwarding command output fields. Table 109: 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 681 JUNOSe 11. 0. x BGP and MPLS Configuration Guide 682 Monitoring MPLS Forwarding Table for VPWS Part 6 Index Index on page 685 Index 683 JUNOSe 11. 0. x BGP and MPLS Configuration Guide 684 Index Index Symbols 802. 3ad switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534 AS-path, BGP access lists, modifying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 attribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 as-set keyword (aggregate-address). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 ATM (Asynchronous Transfer Mode) AAL0 encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 AAL5 encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 Martini encapsulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 over MPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 passthrough for ATM over MPLS. . . . . . . . . . . . . . . . . 506, 509 VCC cell relay encapsulation configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 ATM cells concatenation of multiple for transportation over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 transported over a single pseudowire, subset of discarded on he remote PE device. . . . . . . . . . . . . . . 520 atm commands atm cell-packing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 atm mcpt-timers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530 atm pvc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528, 530 ATM line modules and transport of a subset of ATM VCs over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 hardware limitations and support of multiple VCs over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 ATM Martini cell packing timer expired time interval and forwarding of MPLs packets. . . . . . . . . . . . . . . . . . 520 for concatenation of multiple cells and transmission over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 ATM n-to-one VCC cell transport (0x0009) pseudowire (PW) type used by LDP for subset of ATM VCs over a pseudowire transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 A access lists, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 assigning weights to neighbors. . . . . . . . . . . . . . . . . . . . . . . . . . . 112 distributing neighbor information. . . . . . . . . . . . . . . . . . . . . . . . . 83 access-list command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83, 85 address families. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 L2VPN. . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374, 573, 594, 643 multicast IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374 multicast IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374 route-target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 374 unicast IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374 unicast IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374 VPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374, 573, 594 VPN-IPv4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374 VPN-IPv6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374 VPWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43, 153, 374, 643, 658 address-family command. . . . . . . . . . . . . 45, 154, 389, 437, 594 for L2VPN address family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 for VPWS address family. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 administrative distance BGP, setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 admission control, MPLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 advertise-map keyword (aggregate-address). . . . . . . . . . . . . . . . 61 aggregate addresses BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 aggregate-address command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 aggregation, LDP FEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 aggregator, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 append-after command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 APS/MSP (Automatic Protect Switching/Multiplex Section Protection). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 areas, OSPF defining. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602 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 685 JUNOSe 11. 0. x BGP and MPLS Configuration Guide ATM ports changed to LOS state and multiple VCs over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 configuring cell concatenation parameters requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 connectivity between two of them emulated using multiple VCs transport over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 not changed to LOS state during a failure on the pseudowire. . . . . . . . . . . . . . 520 ATM virtual circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 adding MPLS Martini circuit configuration for multiple VCs transport over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 and emulation of connectivity between ATM ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 based on RFC 4816 exception with subset of ATM cells transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 concatenation of multiple cells requirements for configuring. . . . . . . . . . . . . . . . . . . . . . . 522 configuring a subset of using the mpls-relay atm vpi-range command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 configuring VPI/VCI ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 hardware limitations of ATM LMs and transport of multiple VCs over a pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 in Martini topologies transportation over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 received on an ATM port opening VCs on the SAR scheduler. . . . . . . . . . . . . . 518 transmission of a subset of ATM cells over a pseudowire deployment scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554 transmission of multiple cells over a pseudowire high availability and. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 limit on total number of. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 performance impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 unified ISSU and. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 verifying cell concatenation. . . . . . . . . . . . . . . . . . . . . . . . . 562 verifying VCI/VPI ranges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 transmission of multiple VCs over a single pseudowire interoperation with cell relay on a subinterface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 transport of multiple cells over a pseudowire and ATM n-to-one VCC cell transport (0x0009) pseudowire (PW) type . . . . . . . . . . . . . . 521 transportation of cells from multiple circuits over a single pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 transportation of multiple ATM cells concatetation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 atomic-aggregate, BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 attribute-map keyword (aggregate-address). . . . . . . . . . . . . . . . . 61 authentication BGP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 MPLS LDP MD5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 RSVP-TE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 auto-summary command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 autoconfiguration, LDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 autonomous system. [. . . ]