Configuration Guide - MPLS

Transcription

1 Release: Document Revision: NN A Rev01

2 Release: 5.3 Publication: NN Document Revision: Document status: Standard Document release date: 30 March 2009 Copyright 2009 Nortel Networks All Rights Reserved. Printed in Canada, India, and the United States of America LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their respective owners. ATTENTION For information about the safety precautions, read "Safety messages" in this guide. For information about the software license, read "Software license" in this guide.

3 Contents About this document MPLS overview Introduction Basic MPLS concepts MPLS network structure MPLS architecture MPLS and routing protocols References MPLS applications MPLS-based VPN MPLS-based QoS Basic MPLS configuration Introduction Label distribution and management LSP tunnel and label stack PHP TTL processing in MPLS MPLS ping and traceroute Basic LDP concepts Working mechanism of LDP Basic LDP operations LDP loop detection LDP Fast Reroute LDP Graceful Restart References Configuring basic MPLS capability Establishing the configuration task Configuring the LSR ID Enabling MPLS Checking the configuration Adjusting MPLS parameters Issue 5.3 (30 March 2009) Nortel Networks Inc. i

4 2.3.1 Establishing the configuration task Configuring PHP Setting the MPLS MTU of the interface Configuring the interval for collecting MPLS statistics Configuring the load balancing mode of MPLS Layer 3 forwarding Configuring FRR on the load balancing mode Checking the configuration Configuring static LSPs Establishing the configuration task Configuring the ingress for a static LSP Configuring the transit for a static LSP Configuring the egress for a static LSP Checking the configuration Configuring MPLS LDP Establishing the configuration task Enabling LDP Setting parameters for LDP discovery Setting parameters for LDP sessions Configuring label distribution and retention mode Configuring loop detection Configuring LDP MD5 authentication Configuring LDP MTU signaling Checking the configuration Configuring the LDP multi-instance Establishing the configuration task Configuring LDP multi-instance Checking the configuration Configuring the policy for establishing LSPs Establishing the configuration task Configuring the policy for triggering LSP setup Configuring the policy for establishing transit LSPs Shielding the MPLS hop count Establishing the configuration task Configuring MPLS IP TTL propagation Configuring the path taken by ICMP response packets Configuring LDP FRR Establishing the configuration task Enabling LDP FRR Allowing BFD to modify the PST T Checking the configuration Configuring LDP GR Establishing the configuration task ii Nortel Networks Inc. Issue 5.3 (30 March 2009)

5 Enabling LDP GR Configuring LDP GR parameters Testing LDP GR Iterating the nonlabel public network route to the LSP Establishing the configuration task Iterating the nonlabel public network route to the LSP Checking the configuration Maintaining MPLS Resetting LDP Clearing MPLS statistics Configuring MPLS ping or traceroute Enabling MPLS LSP trapping Debugging MPLS Configuration examples Example of configuring static LSPs Example of configuring LDP sessions Example of configuring LSPs by using LDP Example of configuring transit LSPs through the prefix list Example of configuring LDP FRR Example of configuring LDP GR MPLS TE configuration Introduction TE and MPLS TE Basic MPLS TE concepts Implementation of MPLS TE CR-LSP CR-LDP RSVP-TE RSVP authentication extension Traffic forwarding Fast Reroute Automatic FRR CR-LSP backup Diff-Serv-Aware TE References Configuring basic MPLS TE capability Establishing the configuration task Enabling MPLS TE Creating an MPLS TE tunnel Configuring static MPLS TE tunnels Establishing the configuration task Issue 5.3 (30 March 2009) Nortel Networks Inc. iii

6 3.3.2 Configuring an MPLS TE tunnel using static CR-LSP Configuring the ingress of static CR-LSP Configuring the transit of static CR-LSP Configuring the egress of static CR-LSP Checking the configuration Configuring the MPLS TE tunnel using CR-LDP Establishing the configuration task Configuring link bandwidth Configuring OSPF TE Configuring IS-IS TE Configuring the MPLS TE explicit path Configuring constraints for the MPLS TE tunnel Configuring CSPF Establishing the MPLS TE tunnel using CR-LDP Checking the configuration Configuring the MPLS tunnel using RSVP-TE Establishing the configuration task Configuring the link bandwidth Configuring OSPF TE Configuring IS-IS TE Configuring MPLS TE explicit path Configuring constraints for the MPLS TE tunnel Configuring CSPF Establishing the MPLS TE tunnel using RSVP-TE Checking the configuration Configuring advanced RSVP-TE features Establishing the configuration task Configuring the RSVP Hello extension Configuring the RSVP resource reservation style Configuring RSVP timers Configuring the RSVP refresh mechanism Enabling the reservation confirmation mechanism Configuring RSVP authentication Configuring the handshake function Configuring the message window function Checking the configuration Adjusting the establishment of CR-LSP Establishing the configuration task Configuring CSPF tiebreaking Configuring route pinning Configuring the administrative group and affinity property Configuring reoptimization for CR-LSP iv Nortel Networks Inc. Issue 5.3 (30 March 2009)

7 3.7.6 Checking the configuration Adjusting the establishment of the MPLS TE tunnel Establishing the configuration task Configuring loop detection Configuring the route record and label record Configuring tunnel reestablishment parameters Configuring the tunnel priority Checking the configuration Influencing traffic forwarding Establishing the configuration task Configuring the failed link timer Configuring flooding thresholds Configuring metrics for path calculation Configuring the IGP shortcut Configuring forwarding adjacency Configuring the type of traffic forwarded by the tunnel Configuring MPLS TE Fast Reroute Establishing the configuration task Enabling Fast Reroute on the ingress of the primary LSP Configuring bypass tunnels on the PLR Configuring node protection Configuring automatic FRR Establishing the configuration task Enabling Auto FRR in the MPLS view Enabling Auto FRR in the interface view Configuring Auto FRR on the ingress of the tunnel Checking the configuration Configuring the backup CR-LSP Establishing the configuration task Configuring the backup CR-LSP Checking the configuration Maintaining MPLS TE Clearing the running information Resetting the tunnel interface Debugging MPLS TE Configuration examples Example of establishing an MPLS TE tunnel using static CR-LSP Example of establishing an MPLS TE tunnel using RSVP-TE Example of establishing an MPLS TE tunnel using CR-LDP Example of configuring the handshake and the message window Example of configuring tunnel properties Example of configuring Fast Reroute Issue 5.3 (30 March 2009) Nortel Networks Inc. v

8 Example of configuring Auto FRR Example of configuring CR-LSP backup Example of configuring MPLS TE in BGP/MPLS IP VPN Example of configuring an inter-area tunnel A Glossary... A-1 B Acronyms and abbreviations...b-1 Index... i-1 vi Nortel Networks Inc. Issue 5.3 (30 March 2009)

9 Figures Figure 1-1 Label encapsulation structure Figure 1-2 Label encapsulation location in a packet Figure 1-3 MPLS network structure Figure 1-4 Architecture of MPLS Figure 1-5 MPLS and routing protocols Figure 1-6 MPLS-based VPN Figure 2-1 LSP tunnel Figure 2-2 Label distribution process Figure 2-3 Application of iterating the non-label public network route to the LSP Figure 2-4 Networking of configuring static LSPs Figure 2-5 Networking diagram of LDP session configuration Figure 2-6 Networking diagram of configuring transit LSPs through the prefix list Figure 2-7 Networking diagram of configuring LDP FRR Figure 2-8 Networking diagram of configuring LDP GR Figure 3-1 Schematic diagram of make-before-break Figure 3-2 Establishing an LSP tunnel Figure 3-3 Basic principle of handshake Figure 3-4 Schematic diagram of IGP shortcut and forwarding adjacency Figure 3-5 Schematic diagram of FRR link protection Figure 3-6 Schematic diagram of FRR node protection Figure 3-7 Relationship between the global bandwidth and the subpool bandwidth Figure 3-8 Networking diagram of static CR-LSP configuration Figure 3-9 Networking diagram of the MPLS TE tunnel configured by RSVP-TE Figure 3-10 Networking diagram of the MPLS TE tunnel configured by CR-LDP Figure 3-11 Networking diagram of the RSVP authentication Figure 3-12 Networking diagram of configuring tunnel properties Issue 5.3 (30 March 2009) Nortel Networks Inc. vii

10 Figure 3-13 Networking diagram of MPLS TE FRR configuration Figure 3-14 Example of configuring Auto FRR Figure 3-15 Networking diagram of CR-LSP backup Figure 3-16 Networking diagram of MPLS TE configuration in the VPN Figure 3-17 Networking diagram of configuring an MPLS TE tunnel using RSVP-TE viii Nortel Networks Inc. Issue 5.3 (30 March 2009)

11 Tables Table 1-1 Fields in a label Issue 5.3 (30 March 2009) Nortel Networks Inc. ix

12 Contents About this document...1 Issue 5.3 (30 March 2009) Nortel Networks Inc. i

13

14 About this document About this document Overview This section describes the organization of this document, product version, intended audience, conventions, and update history. Related versions The following table lists the product versions related to this document. Product name Version Nortel Secure Router 8000 Series 1.0 Intended audience This document is intended for the following audience: network operators network administrators network maintenance engineers Organization This document consists of three chapters and is organized as follows. Chapter Description 1 MPLS overview This chapter describes the architecture and application of Multiprotocol Label Switching (MPLS). Issue 5.3 (30 March 2009) Nortel Networks Inc. 1

15 About this document Nortel Secure Router 8000 Series Chapter 2 Basic MPLS configuration 3 MPLS TE configuration Appendix A Glossary Appendix B Acronyms and abbreviations Description This chapter describes the fundamentals of MPLS forwarding and Label Distribution Protocol (LDP), the policy of establishing the static Label Switched Path (LSP), the dynamic LSP, the Border Gateway Protocol (BGP)/MPLS virtual private network (VPN) and LSP, and the basic MPLS configuration procedures and examples. This chapter describes the fundamentals of MPLS traffic engineering (TE) and provides configuration procedures and examples for the static CR-LSP tunnel, the MPLS TE tunnel based on dynamic signaling protocol, the end-to-end protection route, partial protection through Fast Reroute (FRR), traffic forwarding of the BGP/MPLS IP VPN through the TE tunnel, and adjusting the traffic dynamically through LDP over TE. This appendix contains a glossary of frequently used terms. This appendix lists frequently used acronyms and abbreviations. Conventions Symbol conventions This section describes the symbol and text conventions used in this document. Symbol Description Indicates a hazard with a high level of risk that, if not avoided, can result in death or serious injury. Indicates a hazard with a medium or low level of risk that, if not avoided, can result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, can cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text. 2 Nortel Networks Inc. Issue 5.3 (30 March 2009)

16 About this document General conventions Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman font. Names of files, directories, folders, and users are in boldface. For example, log on as the user root. Book titles are in italics. Terminal display is in Courier New font. Command conventions Convention Boldface Italic Description The keywords of a command line are in boldface. Command arguments are in italics. [ ] Items (keywords or arguments) in square brackets [ ] are optional. { x y... } Alternative items are grouped in braces and separated by vertical bars. You select one item. [ x y... ] Optional alternative items are grouped in square brackets and separated by vertical bars. You select one item or no item. { x y... } * Alternative items are grouped in braces and separated by vertical bars. You can select a minimum of one item or a maximum of all items. &<1-n> The parameter before the ampersand sign (&) can be repeated 1 to n times. A line starting with the number sign () contains comments. GUI conventions Convention Boldface Description Buttons, menus, parameters, tabs, windows, and dialog box titles are in boldface. For example, click OK. > Multilevel menus are in boldface and separated by the right-angled bracket sign (>). For example, choose File > Create > Folder. Issue 5.3 (30 March 2009) Nortel Networks Inc. 3

17 About this document Nortel Secure Router 8000 Series Keyboard operation Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, Ctrl+Alt+A means press the three keys concurrently. Press the keys in sequence. For example, Alt, A means press the two keys in sequence. Mouse operation Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a new position. Update history Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions. Updates in Issue 01 ( ) This is the first commercial release of this document. 4 Nortel Networks Inc. Issue 5.3 (30 March 2009)

18 Contents 1 MPLS overview Introduction Basic MPLS concepts MPLS network structure MPLS architecture MPLS and routing protocols References MPLS applications MPLS-based VPN MPLS-based QoS Issue 5.3 (30 March 2009) Nortel Networks Inc. i

19

20 Figures Figure 1-1 Label encapsulation structure Figure 1-2 Label encapsulation location in a packet Figure 1-3 MPLS network structure Figure 1-4 Architecture of MPLS Figure 1-5 MPLS and routing protocols Figure 1-6 MPLS-based VPN Issue 5.3 (30 March 2009) Nortel Networks Inc. iii

21

22 Tables Table 1-1 Fields in a label Issue 5.3 (30 March 2009) Nortel Networks Inc. v

23

24 1 MPLS overview 1 MPLS overview About this chapter The following table shows the contents of this chapter. Section Description 1.1 Introduction This section describes the concepts, networking, and architecture of Multiprotocol Label Switching (MPLS). 1.2 MPLS applications This section describes the applications of MPLS. Issue 5.3 (30 March 2009) Nortel Networks Inc. 1-1

25 1 MPLS overview Nortel Secure Router 8000 Series 1.1 Introduction This section describes the concepts that you need to know before you configure MPLS: Basic MPLS concepts MPLS network structure MPLS architecture MPLS and routing protocols References Basic MPLS concepts While forwarding packets, Multiprotocol Label Switching (MPLS) analyzes the IP packet header only at the network edge and not at every hop. This differs from traditional IP routing and increases the forwarding speed and saves processing time. MPLS originates from Internet Protocol version 4 (IPv4). The core technique of MPLS is applied to multiple network layer protocols, including Internet Protocol version 6 (IPv6), Internet Packet Exchange (IPX), Appletalk, DECnet, and Connectionless Network Protocol (CLNP). Forwarding Equivalence Class Label MPLS is a high-performance forwarding technology that takes packets with the same forwarding mode as a class. This type of class is called the Forwarding Equivalence Class (FEC). Packets of the same FEC are treated alike in the MPLS network. The source address, destination address, source port, destination port, protocol type, virtual private network (VPN), or any of combination of these determines an FEC. For example, packets that are transmitted to the same destination through the longest match algorithm belong to an FEC. A label is a short identifier of a fixed length with local significance. It is used to uniquely identify an FEC. The label assigned to the packet represents an FEC. In some cases, different labels are assigned to an FEC, but only a single label represents it. A label is 4 bytes long and is contained in the packet header, excluding the topology information. Figure 1-1 shows the label encapsulation structure. Figure 1-1 Label encapsulation structure Label Exp S TTL A label contains four fields as described in Table Nortel Networks Inc. Issue 5.3 (30 March 2009)

26 1 MPLS overview Table 1-1 Fields in a label Field Description Length Label Exp S TTL Represents the label value, and is used as the pointer for forwarding. Reserved and used for experiments. It is generally used as Class of Service (CoS). Represents a label stack. The value 1 refers to the bottom layer label. Represents the Time To Live (TTL), and has the same meaning as the TTL in the IP packet. 20 bits 3 bits 1 bit 8 bits The label is a connection identifier, similar to the Asynchronous Transfer Mode (ATM) Virtual Path Identifier/ Virtual Channel Identifier (VPI/VCI) and the Frame Relay Data Link Connection Identifier (DLCI). If the link layer protocol has a label field, the label is encapsulated in the field. If the link layer protocol has no label field, the label resides between Layer 2 and Layer 3 like a shim. The label, therefore, can be supported by any link layer protocol. Figure 1-2 shows the label encapsulation location in a packet. Figure 1-2 Label encapsulation location in a packet Ethernet/PPP header Label Ethernet/SONET/SDH packet Layer 3 data ATM header Label ATM packet in frame mode Layer 3 data Label Switched Router A Label Switched Router (LSR) is a basic component of the MPLS network, and all LSRs support MPLS. An LSR has two components: Label Distribution Protocol Control part: Allocates labels, selects routes, creates the label-forwarding information base, and sets up or deletes a Label Switched Path (LSP). Forwarding part: Forwards received packets according to the entries in the label-forwarding base. Label Distribution Protocol (LDP) is the control protocol of MPLS. It is similar to the signaling protocol in a traditional network. Issue 5.3 (30 March 2009) Nortel Networks Inc. 1-3

27 1 MPLS overview Nortel Secure Router 8000 Series Label Switched Path LDP is responsible for packet classification, label distribution, LSP establishment, and maintenance. MPLS supports the following label distribution protocols: specially defined protocols for label distribution, such as LDP and Constraint-based Routing LDP (CR-LDP) extended existent protocols that support label distribution, such as Border Gateway Protocol (BGP) and Resource Reservation Protocol (RSVP) The router supports the protocols mentioned above and the static LSP. A Label Switched Path (LSP) refers to the path along which an FEC is MPLS network. transmitted in the The LSP functions as a unidirectional path from the ingress to the egress, similar to the ATM or Frame Relay (FR) virtual circuit. Each node in the path is an LSR. Two neighboring LSRs are called the upstream LSR and the downstream LSR, according to the data transmission direction. The types of LSPs are as follows: Static LSP: The administrator configures static LSPs. Dynamic LSP: The routing protocol and the label distribution protocol generate dynamic LSPs MPLS network structure Figure 1-3 shows the LSRs in the MPLS network. The network consisting of LSRs is called an MPLS domain. An edge LSR, also called Label Edge Router (LER), is located at the edge of the domain and has a neighboring LSR that does not run MPLS. The LSR located inside the domain is called a core LSR. The core LSR can be either a router that supports MPLS or an ATM LSR upgraded from an ATM switch. MPLS runs between the LSRs in the domain, and IP runs between an LER and a router outside the domain. The LSRs along which labeled packets are transmitted form an LSP. The ingress LER is called ingress, the egress LER is called egress, and the intermediate LER is called transit. 1-4 Nortel Networks Inc. Issue 5.3 (30 March 2009)

28 1 MPLS overview Figure 1-3 MPLS network structure Ingress Egress MPLS Core Switch (LSR) MPLS Edge Router(LER) Label Switched Path (LSP) Figure 1-3 shows the MPLS working process. The details are as follows: 1. LDP establishes a label map for the preferred FECs in each LSR through the routing table generated by traditional routing protocols like Open Shortest Path First (OSPF) and Intermediate System-Intermediate System (IS-IS). 2. The ingress receives a packet, determines its FEC, and adds a label to the packet. This packet is called the MPLS labeled packet. 3. The transits forward the packet according to its label and the label forwarding information base without any Layer 3 processing. 4. The egress strips off the label and continues the forwarding for delivery. MPLS is a tunnel technique rather than a service or application. It is a routing and forwarding platform that combines label switched forwarding with network layer routing. It supports multiple upper-layer protocols and services, and guarantees security during the transmission of information MPLS architecture MPLS architecture comprises the following: The control plane, which is connectionless and implemented through the current IP network. The forwarding plane, which is also known as the data plane and is connection-oriented. It uses the Layer 2 network such as ATM or FR. MPLS uses a short label of a fixed length to encapsulate packets. The data with the label is fast-forwarded on the data plane. The powerful, flexible routing function of the IP network is used on the control plane to meet the demands of new applications. Figure 1-4 shows the architecture of MPLS. Issue 5.3 (30 March 2009) Nortel Networks Inc. 1-5

29 1 MPLS overview Nortel Secure Router 8000 Series Figure 1-4 Architecture of MPLS Control Plane IP Routing Protocol Routing Information Base (RIB) Label Information Base(LIB) MPLS IP Routing Protocol Forwarding Plane Label Forwarding Information Base(LFIB) On the forwarding plane, core LSRs forward only labeled packets, whereas LERs forward both labeled packets and IP packets. The labeled packets use the Label Forwarding Information Base (LFIB), and the IP packets use the Forwarding Information Base (FIB) MPLS and routing protocols Establishing the LSP by the routing table When LDP establishes an LSP in the hop-by-hop manner, it specifies the next hop according to the routing table on the LSR. The information in the routing table is collected by the routing protocol, such as Interior Gateway Protocol (IGP) and BGP. LDP uses only the routing information. Supporting label distribution by the extension of existing protocols The extension of existing protocols, such as BGP and RSVP, also supports the distribution of MPLS labels. Supporting MPLS applications by the extension of routing protocols In some MPLS applications, it is necessary to extend the routing protocols. For example, the MPLS-based VPN application requires the extension of BGP so that BGP supports the sending of VPN routing information. MPLS-based traffic engineering (TE) requires the extension of OSPF or IS-IS to carry the link status information. Figure 1-5 shows the relationship between MPLS and routing protocols. 1-6 Nortel Networks Inc. Issue 5.3 (30 March 2009)

30 1 MPLS overview Figure 1-5 MPLS and routing protocols ISIS OSPF LDP CR-LDP RSVP-TE TEDB LSP Management (LSPM) MPLS Forwarding References For more information about MPLS, see RFC 3031 (Multiprotocol Label Switching Architecture). 1.2 MPLS applications With the development of the Application Specific Integrated Circuit (ASIC) technology, the route searching speed does not hinder network growth. This means that MPLS no longer has distinct advantages in improved forwarding speed. MPLS, however, combines the powerful Layer 3 routing function of IP networks and the high-efficiency forwarding mechanism of traditional Layer 2 networks. It is connection-oriented on the forwarding plane, which is similar to the forwarding mode of the existing Layer 2 networks. These characteristics allow seamless connection of IP networks and Layer 2 networks such as the ATM network and the FR network. MPLS also offers a better solution to applications such as Quality of Service (QoS), TE, and VPN MPLS-based VPN For traditional VPNs, the transmission of data between private networks and public networks is usually performed through tunneling protocols such as Generic Routing Encapsulation (GRE), Layer 2 Tunneling Protocol (L2TP), and Point-to-Point Tunneling Protocol (PPTP). The LSP itself is a tunnel on the public network. The implementation of VPNs using MPLS has an advantage. The MPLS-based VPN connects the geographically dispersed branches of a private network by using the LSP, forming a united network. The MPLS-based VPN also supports interconnection between different VPNs. Figure 1-6 shows the basic structure of an MPLS-based VPN: The Customer Edge (CE) can be a router, a switch, or a host. The Provider Edge (PE) is a router residing in the backbone network. Issue 5.3 (30 March 2009) Nortel Networks Inc. 1-7

31 1 MPLS overview Nortel Secure Router 8000 Series Figure 1-6 MPLS-based VPN PE3 CE3 VPN branch 3 CE1 PE1 VPN branch 1 Backbone network PE2 CE2 VPN branch MPLS-based QoS The PE manages VPN users, sets up LSP connections between PEs, and assigns routes for each branch of users of the same VPN. Usually the route allocation between PEs is performed by LDP or the extended BGP. The MPLS-based VPN supports IP address space overlap between different branches and interconnection between different VPNs. Compared to traditional routes, VPN routes are added with the branch and VPN distinguisher information. Therefore, it is necessary to extend BGP to carry the VPN routing information. The router supports MPLS-based TE and differentiated services (Diff-serv) features. It ensures effective network utilization and implements differentiated services according to the priorities of streams. Thus, the router provides voice and video streams with low delay, low packet loss, and stable bandwidth guarantee. Because it is difficult to perform TE over the entire network, the Diff-serv model of QoS is commonly implemented in actual networking solutions. The Diff-serv model maps a service to a certain service class at the network edge according to the QoS requirement of the service. The Differentiated Service (DS) field (derived from the TOS field) in the IP packet uniquely identifies the service. Each node in the backbone network then performs the preset service policies. Service policies are applied to diversified services according to the field to ensure QoS. The QoS classification and label mechanism in the Diff-serv model is similar to MPLS label distribution. MPLS-based Diff-serv is implemented by integrating Diff-serv distribution into MPLS label distribution. NOTE This document describes MPLS basics and MPLS TE. 1-8 Nortel Networks Inc. Issue 5.3 (30 March 2009)

32 1 MPLS overview For information about MPLS VPN configuration, see Nortel Secure Router 8000 Series Configuration Guide - VPN (NN ). For information about MPLS QoS configuration, see Nortel Secure Router 8000 Series Configuration Guide - QoS (NN ). Issue 5.3 (30 March 2009) Nortel Networks Inc. 1-9

33 Contents 2 Basic MPLS configuration Introduction Label distribution and management LSP tunnel and label stack PHP TTL processing in MPLS MPLS ping and traceroute Basic LDP concepts Working mechanism of LDP Basic LDP operations LDP loop detection LDP Fast Reroute LDP Graceful Restart References Configuring basic MPLS capability Establishing the configuration task Configuring the LSR ID Enabling MPLS Checking the configuration Adjusting MPLS parameters Establishing the configuration task Configuring PHP Setting the MPLS MTU of the interface Configuring the interval for collecting MPLS statistics Configuring the load balancing mode of MPLS Layer 3 forwarding Configuring FRR on the load balancing mode Checking the configuration Configuring static LSPs Establishing the configuration task Configuring the ingress for a static LSP Configuring the transit for a static LSP Configuring the egress for a static LSP Issue 5.3 (30 March 2009) Nortel Networks Inc. i

34 2.4.5 Checking the configuration Configuring MPLS LDP Establishing the configuration task Enabling LDP Setting parameters for LDP discovery Setting parameters for LDP sessions Configuring label distribution and retention mode Configuring loop detection Configuring LDP MD5 authentication Configuring LDP MTU signaling Checking the configuration Configuring the LDP multi-instance Establishing the configuration task Configuring LDP multi-instance Checking the configuration Configuring the policy for establishing LSPs Establishing the configuration task Configuring the policy for triggering LSP setup Configuring the policy for establishing transit LSPs Shielding the MPLS hop count Establishing the configuration task Configuring MPLS IP TTL propagation Configuring the path taken by ICMP response packets Configuring LDP FRR Establishing the configuration task Enabling LDP FRR Allowing BFD to modify the PST T Checking the configuration Configuring LDP GR Establishing the configuration task Enabling LDP GR Configuring LDP GR parameters Testing LDP GR Iterating the nonlabel public network route to the LSP Establishing the configuration task Iterating the nonlabel public network route to the LSP Checking the configuration Maintaining MPLS Resetting LDP Clearing MPLS statistics Configuring MPLS ping or traceroute Enabling MPLS LSP trapping ii Nortel Networks Inc. Issue 5.3 (30 March 2009)

35 Debugging MPLS Configuration examples Example of configuring static LSPs Example of configuring LDP sessions Example of configuring LSPs by using LDP Example of configuring transit LSPs through the prefix list Example of configuring LDP FRR Example of configuring LDP GR Issue 5.3 (30 March 2009) Nortel Networks Inc. iii

36

37 Figures Figure 2-1 LSP tunnel Figure 2-2 Label distribution process Figure 2-3 Application of iterating the non-label public network route to the LSP Figure 2-4 Networking of configuring static LSPs Figure 2-5 Networking diagram of LDP session configuration Figure 2-6 Networking diagram of configuring transit LSPs through the prefix list Figure 2-7 Networking diagram of configuring LDP FRR Figure 2-8 Networking diagram of configuring LDP GR Issue 5.3 (30 March 2009) Nortel Networks Inc. v

38

39 2 Basic MPLS configuration 2 Basic MPLS configuration About this chapter The following table shows the contents of this chapter. Section Description 2.1 Introduction This section describes Multiprotocol Label Switching (MPLS) principles and concepts. 2.2 Configuring basic MPLS capability This section describes how to enable the basic MPLS capability. 2.3 Adjusting MPLS parameters This section describes how to configure MPLS Penultimate Hop Popping (PHP), MPLS Maximum Transmission Unit (MTU), and the load balancing mode. 2.4 Configuring static LSPs This section describes how to configure the static Label Switched Path (LSP). 2.5 Configuring MPLS LDP This section describes how to configure MPLS Label Distribution Protocol (LDP). 2.6 Configuring the LDP This section describes how to configure the LDP multi-instance multi-instance. 2.7 Configuring the policy for This section describes how to configure the policy of establishing LSPs establishing the LSP. 2.8 Shielding the MPLS hop This section describes how to process the MPLS Time count To Live (TTL). 2.9 Configuring LDP FRR This section describes how to configure LDP Fast Reroute (FRR) Configuring LDP GR This section describes how to configure LDP Graceful Restart (GR) Iterating the nonlabel public network route to the LSP This section describes how to allow IP traffic to be forwarded through MPLS. Issue 5.3 (30 March 2009) Nortel Networks Inc. 2-1

40 2 Basic MPLS configuration Nortel Secure Router 8000 Series Section Description 2.12 Maintaining MPLS This section describes how to maintain MPLS Configuration examples This section provides MPLS configuration examples. 2-2 Nortel Networks Inc. Issue 5.3 (30 March 2009)

41 2 Basic MPLS configuration 2.1 Introduction This section describes the concepts that you need to know before you configure the basic MPLS capability: Label distribution and management LSP tunnel and label stack PHP TTL processing in MPLS MPLS ping and traceroute Basic LDP concepts Working mechanism of LDP Basic LDP operations LDP loop detection LDP Fast Reroute LDP Graceful Restart References NOTE The router supports LDP Graceful Restart (GR). For information about GR, see Nortel Secure Router 8000 Series Configuration Guide - Reliability (NN ). The router supports MPLS on Ethernet interfaces and POS interfaces Label distribution and management Label advertisement mode Label distribution control In the MPLS architecture, the downstream LSR binds a label to a particular FEC and then notifies the upstream LSR. That is, the downstream LSR assigns labels and distributes the labels from downstream to upstream. The two MPLS label advertisement modes are as follows: Downstream Unsolicited (DU) In DU mode, an LSR does not require a label request from upstream when distributing a label. Downstream-on-Demand (DoD) In DoD mode, an LSR must have received a label request from upstream when distributing a label. Before establishing an LSP, the two neighboring upstream and downstream LSRs must agree on the label advertisement mode. The label distribution control mode is the time policy used by the LSR to assign labels when establishing LSPs. The two label control modes are as follows: Issue 5.3 (30 March 2009) Nortel Networks Inc. 2-3

42 2 Basic MPLS configuration Nortel Secure Router 8000 Series Label retention mode Independent label distribution control In independent label distribution control mode, each LSR advertises label mappings to the LSRs connected with it at any time. This mode can cause upstream labels to be distributed before downstream labels are received. Ordered label distribution control In ordered label control mode, the LSR sends a label mapping message upstream only when the LSR receives a label mapping message for a specific FEC or when it serves as the egress of LSP. In label retention mode, when an LSR identifies that its neighbor is not the next hop to an FEC, the LSR handles the label bound to an FEC. The two label retention modes are as follows: Liberal label retention mode In liberal label retention mode, the LSR keeps the label mapping received from the neighboring LSR whether or not its neighbor is the next hop. Conservative label retention mode In conservative label retention mode, the LSR keeps the label mapping received from the neighboring LSR only when the LSR identifies that its neighbor is the next hop. A change in network topology can lead to a change of the next-hop neighbor: If liberal label retention mode is used, the LSR can use the labels sent from the next-hop or non-next-hop neighbors to recreate LSPs. This, however, requires more memory and label space. If conservative label retention mode is used, the LSR keeps the labels sent from only the next-hop neighbors. This saves the memory and label space. The LSP is recreated, however, at a lower speed. The conservative label retention mode is usually used together with the DoD mode in LSRs with limited label space. Nortel recommends that you use a combination of DU, ordered label distribution control, and liberal label retention mode. Labeled packets forwarding On the ingress, packets entering the network are classified into various FECs by their characteristics. This classification is based on the destination IP address prefix or host address. Packets belonging to the same FEC have the same label and pass through the same path in the MPLS domain. The LSR assigns a label for an incoming packet, and then forwards it through a specified interface LSP tunnel and label stack LSP tunnel MPLS supports the LSP tunnel. On an LSP, the LSR Ru and LSR Rd are upstream and downstream for each other. The path between the LSR Ru and LSR Rd, however, may not be a part of the path provided by the routing protocol. MPLS allows the establishment of a new LSP path between the LSR Ru and the LSR Rd. The LSR Ru is the starting point and the LSR Rd is the ending point of this LSP. The LSP between the LSR Ru and the LSR Rd is referred to as the LSP tunnel. 2-4 Nortel Networks Inc. Issue 5.3 (30 March 2009)

43 2 Basic MPLS configuration The tunnel is classified into two types: If the path along which the tunnel passes and the path obtained from the routing protocol are consistent, the tunnel is called a hop-by-hop routed tunnel. If the two paths are not consistent, the tunnel is called an explicitly routed tunnel. Figure 2-1 LSP tunnel Level 1 R1 R2 R3 R4 Level 2 R21 R22 Multilevel label stack PHP As shown in Figure 2-1, LSP <R2 R21 R22 R3> is a tunnel between R2 and R3. When a packet is sent through an LSP tunnel that is more than one layer, multilevel labels form the label stack. The push and pop operations are conducted for the label stack on the ingress and the egress of each LSP. There is no limit on the depth of the label stack in MPLS. The labels are organized in the label stack according to the last-in-first-out rule, and MPLS processes the labels from the top of the stack. If the depth of the label stack of a packet is n, the label on the bottom of the stack is a Level 1 label, and the label on the top of the stack is a Level n label. An unlabeled packet is regarded as a packet with an empty label stack; that is, the depth of the label stack is null. As shown in Figure 2-1 the label stack of the packet sent from R1 to R4 is as follows: The packet has a one-level label between R1 and R2. When it enters the LSP <R2, R1 R22 R3> tunnel, the packet has two-level labels. The Level 2 label at the top of the stack is used to direct the packet to R3. When the packet arrives at R3, its Level 2 label is popped. The Level 1 label is used to direct the packet to R4. In the MPLS network, the LSR forwards the packet according to its label. On the egress, the label is removed and the packet is forwarded as an IP packet. In certain MPLS applications, the egress requires only IP forwarding, and the MPLS label has no significance for forwarding. In this case, use Penultimate Hop Popping (PHP) to pop the label at the penultimate node. This saves label operations on the egress. The PHP feature is configured on the egress. The label distribution mode is selected based on the support of PHP by the penultimate node. According to RFC 3032 (MPLS Label Stack Encoding): Issue 5.3 (30 March 2009) Nortel Networks Inc. 2-5

44 2 Basic MPLS configuration Nortel Secure Router 8000 Series Label value 0 stands for IPv4 explicit null label. This value is valid only when it appears at the bottom of the label stack. When a packet is assigned an explicit null label, the egress pops the label and forwards the packet as an IP packet without searching the label routing table. Label value 3 stands for implicit null label. This value does not appear in the label stack. When an LSR is distributed an implicit null label, it does not use this value to replace the original value, but performs the pop operation directly TTL processing in MPLS TTL propagation ICMP response packet The MPLS label comprises an 8-bit Time To Live (TTL) field that is similar to the TTL field in an IP header. The TTL can prevent route loops and can also be used in the traceroute function. As described in RFC 3031, an LSR node copies the TTL value of the IP packet or that of the upper-layer label to the TTL field of the added label. When the LSR forwards a labeled packet, the TTL value of the label at the top of the label stack is decreased by one. When the label is out of the label stack, the LSR copies the TTL value at the top of the stack to the IP packet or the lower-layer label. Before the LSP traverses the non-ttl LSP segment formed by ATM-LSRs or FR-LSRs, the TTL should be uniformly processed. This is because the LSRs within the domain cannot process the TTL. That is, the value of the length in this non-ttl LSP segment should decrease by one when the packet enters the segment. In MPLS VPN applications, you can hide the MPLS backbone network structure for security reasons. The router supports different TTL propagation settings for VPN packets and public network packets. In the MPLS VPN, the backbone routers cannot relay VPN packets over MPLS. When the TTL of an MPLS packet expires, an ICMP response packet is forwarded along the LSP to the egress. The egress continues to relay the ICMP response packet based on IP routing. This increases the network traffic and the packet forwarding delay. For the MPLS packets with a single label, the router allows the Internet Control Message Protocol (ICMP) response packet to be sent back using the IP route directly or the LSP when the TTL expires MPLS ping and traceroute In MPLS, the MPLS control plane establishes an LSP. It cannot, however, detect the error when an LSP fails to forward data. This causes difficulty in network maintenance. The MPLS ping or traceroute function helps to detect errors in the LSP and locate the fault. Similar to IP ping or traceroute, MPLS ping or traceroute uses an MPLS echo request and MPLS echo reply to detect the availability of an LSP. These two kinds of messages are transmitted in User Datagram Protocol (UDP) format with the port number The MPLS echo request message carries FEC information to be detected, and is sent along the LSP like other data packets with the same FEC. In this manner, the LSP is detected. 2-6 Nortel Networks Inc. Issue 5.3 (30 March 2009)

45 2 Basic MPLS configuration For MPLS ping, the echo request message should reach the egress of the LSP, and then the control plane of the egress determines whether this LSR is the egress of the FEC. For MPLS traceroute, the echo request message is sent to every transit. Then, the control plane of the transit determines if this LSR is a transit of the LSP. When the message reaches the egress, the destination address contained in the IP header of the echo request message is set as an address on the /8 network segment (loopback address of this LSR), and the TTL is set to 1. This avoids further forwarding Basic LDP concepts LDP peers LDP session LDP message LDP defines various messages in label distribution and the related processes. The LSR directly maps the routing information of the network layer to the data link layer and establishes an LSP by using LDP. To enable label switching on all intermediate nodes in the network, you can establish an LSP between two LSRs that are enabled with LDP and terminate it at the egress of the network. For more information about LDP, see RFC 3036 (LDP Specification). LDP peers are two LSRs with an LDP session that exchange labels or FEC mappings through LDP. The LDP peers obtain each other s label information through an LDP session. In an LDP session, LSRs exchange messages on advertising and releasing labels. The two types of LDP sessions are as follows: Local LDP session: an LDP session between two LSRs that are directly connected. Remote LDP session: an LDP session between two LSRs that are indirectly connected. LDP involves four types of messages: Discovery message: used to notify or maintain the existing LSRs in the network. Session message: used to establish, maintain, or terminate a session between LDP peers. Advertisement message: used to create, modify, or delete a label for an FEC. Notification message: used to provide suggestive messages or error notifications. To assure the reliability of LDP message transmission, UDP is used only in the discovery phase. Session messages, advertisement messages, and notification messages are all transported through Transmission Control Protocol (TCP). Label space and LDP identifier A label space is the value range of labels that are allocated to LDP peers. You can specify a label space for each interface of an LSR (per-interface label space) or for the entire LSR (per-platform label space). An LDP identifier identifies a specified LSR label space. It is a 6-byte value in the following format: Issue 5.3 (30 March 2009) Nortel Networks Inc. 2-7

46 2 Basic MPLS configuration Nortel Secure Router 8000 Series <LSR ID>: <label space number> The IP address of four bytes is used to represent the LSR ID and the remaining two bytes are used for the label space number Working mechanism of LDP Figure 2-2 shows the process of LDP label distribution. Figure 2-2 Label distribution process LSP1 Ingress A LSP2 Label Request Label Mapping B C D Egress Ingress Label Request E F G Label Mapping MPLS LSR MPLS LER I H Egress LDP Session On an LSP, along the data transmission direction, neighboring LSRs are called the upstream LSR and downstream LSR. As shown in Figure 2-2, B on LSP1 is the upstream LSR of C. Labels are distributed in two modes: DoD and DU. The main difference between these two modes is whether the label mapping distribution requires the upstream request or is initialized by the downstream. DoD mode In the DoD mode, a label is distributed in the following manner: The upstream sends a label request message containing FEC descriptive information to the downstream. The downstream distributes a label for this FEC, and then sends the label mapping message with the label to the upstream. When the downstream LSR sends back the label mapping message depends on its label control mode as follows: In ordered mode, the message is sent back to its upstream LSR when the downstream has received a label mapping message for the FEC from its downstream LSR. 2-8 Nortel Networks Inc. Issue 5.3 (30 March 2009)