Passport 7400, 15000 Multiprotocol Label Switching€¦ · 5 Passport 7400, 15000 Multiprotocol Label Switching Guide 2.2S1 Publication history February 2001 2.2S1 Standard General

Passport 7400, 15000

Multiprotocol LabelSwitchingGuide

241-5701-445


Multiprotocol Label SwitchingGuide

Publication: 241-5701-445Document status: StandardDocument version: 2.2S1Document date: February 2001

Copyright © 2001 Nortel Networks.All Rights Reserved.

Printed in Canada

NORTEL NETWORKS, the globemark design, the NORTEL NETWORKS corporate logo, DPN,DPN-100, and PASSPORT are trademarks of Nortel Networks.

5

Passport 7400, 15000 Multiprotocol Label Switching Guide 2.2S1

Publication history

February 20012.2S1 StandardGeneral availability. Contains information on Passport 7400 andPassport 15000 for the PCR 2.2 GA release.

6 Publication history

241-5701-445 2.2S1

7


Contents

About this document 13Who should read this document and why 13What you need to know 14How this document is organized 14What’s new in this document 14

Multiple LSPs per FEC 14Alarms and Statistics 15Configuring a hop-by-hop LSP 15MPLS on ATM IP FP 15

Text conventions 15Related documents 17How to get more help 17

Chapter 1Overview 19What is MPLS technology? 19How is MPLS implemented in Passport networks? 21Why use MPLS? 22How does MPLS work? 22

At the edge of the network 23In the network core 24In hop-by-hop routes 24In explicit routes 26

MPLS in Passport nodes 28

8 Contents

241-5701-445 2.2S1

Chapter 2MPLS description 29MPLS protocols 29

Label distribution protocol 29Constraint-based routing using LDP 32

Creation of LSPs 34Call setup for hop-by-hop LSPs 34Call setup for ER-LSPs 35LDP/CR-LDP interworking 37

Traffic engineering with MPLS 38MPLS using ATM media 40

Label encapsulation 41Ships-in-the-night operation 41QoS mapping 41

LSP recovery 42

Chapter 3Configuring MPLS 43Implementation of MPLS 43Prerequisites to configuring MPLS 45Installing MPLS software 45Configuring ports and interfaces 46

Configuring the virtual router and protocol port 46Configuring the ATM media and links 47Configuring the IP port 50Configuring the MPLS component 51Configuring the MPLS port 54

Configuring LSPs 57Configuring an LSP group and IP forwarding policy 57Configuring the explicit route path 60Configuring an ER-LSP 61Configuring a hop-by-hop LSP 64Configuring LSP quality of service 64

LDP/CR-LDP interworking configuration 67Considerations for configuring LDP/CR-LDP interworking 68

Contents 9


Configuring LDP/CR-LDP interworking 68Locking and unlocking an LSP 70

Chapter 4Monitoring and troubleshooting 71Tracing an LSP 71

Displaying the XcMap on the ingress node 72Displaying the InSegment on the next node 73Displaying the XcMap on the next node 73Following the path 74

Operational information on LSP groups and LSPs 74Displaying information on LSP groups 74Displaying information on LSPs 75Provisioning the alarm severity for a specific LSP 76

Tracing the peers of a node 77Displaying the Ldp component 77Listing the peers of a node 77Listing the sessions of a peer 78Listing the adjacencies of a session 78

Troubleshooting 79Statistics 79Solving problems 80

10 Contents

241-5701-445 2.2S1

List of figures

Figure 1 MPLS technology 20Figure 2 MPLS network 23Figure 3 Hop-by-hop LSP 25Figure 4 ER-LSP 26Figure 5 Strict and loose ER LSPs 27Figure 6 ER specification 28Figure 7 Downstream-on-demand label advertisement 32Figure 8 Call setup for hop-by-hop LSPs 35Figure 9 Call setup for ER-LSPs 36Figure 10 LDP/CR-LDP interworking 38Figure 11 MPLS traffic engineering 40Figure 12 MPLS and related components 44Figure 13 Component tree for configuring the virtual router and

protocol port 46Figure 14 Component tree for configuring the ATM media and

links 48Figure 15 Component tree for configuring the IP port 50Figure 16 Component tree for configuring the MPLS

component 52Figure 17 Component tree for configuring the MPLS port 55Figure 18 Component tree for configuring an LSP group and IP

forwarding policy 58Figure 19 Component tree for configuring the explicit route

path 60Figure 20 Component tree for configuring an ER-LSP 62Figure 21 Component tree for configuring LSP quality of

service 65Figure 22 Component tree for configuring LDP/CR-LDP

interworking 69Figure 23 Tracing an LSP 72

Contents 11


List of tables

Table 1 Mapping of MPLS traffic parameters to ATM servicecategories 42

Table 2 MPLS interface statistics 79Table 3 Troubleshooting the LSP 81

12 Contents

241-5701-445 2.2S1

13


About this document

This guide describes multiprotocol label switching (MPLS).

The following topics are discussed in this section:

• “Who should read this document and why” (page 13)

• “What you need to know” (page 14)

• “How this document is organized” (page 14)

• “What’s new in this document” (page 14)

• “Text conventions” (page 15)

• “Related documents” (page 17)

• “How to get more help” (page 17)

Who should read this document and whyThis guide is for persons who perform the following tasks for MPLS:

• planning

• engineering

• installing and configuring

• provisioning

• operating and maintaining

• troubleshooting

14 About this document

241-5701-445 2.2S1

What you need to knowThis guide assumes that you understand the Passport network architecture.You can learn more about the product by reading 241-5701-400Passport7400, 15000 Networking Overview.

How this document is organizedThe 241-5701-445Passport 7400, 15000 Multiprotocol Label SwitchingGuide, contains the following information:

• “Overview” (page 19) presents an overview of MPLS and itsapplications

• “MPLS description” (page 29) explains how MPLS works

• “Configuring MPLS” (page 43) explains how to install MPLS softwareand configure Passport nodes with MPLS

• “Monitoring and troubleshooting” (page 71) provides information youcan use in maintaining and trouble-shooting MPLS

What’s new in this documentThe following features were added to this document:

• “Multiple LSPs per FEC” (page 14)

• “Alarms and Statistics” (page 15)

• “Configuring a hop-by-hop LSP” (page 64)

• “MPLS on ATM IP FP” (page 15)

Multiple LSPs per FECThis feature introduces the ability to configure multiple LSPs, of differentquality of service, to the same FEC destination. The CDL for MPLS issignificantly changed by this feature. The following sections were updated bythis feature:

• “How is MPLS implemented in Passport networks?” (page 21)

• “Why use MPLS?” (page 22)

• “In explicit routes” (page 26)

• “Traffic engineering with MPLS” (page 38)

About this document 15


• “Configuring MPLS” (page 43)

• “Displaying the XcMap on the ingress node” (page 72)

• “Displaying the XcMap on the next node” (page 73)

• “Operational information on LSP groups and LSPs” (page 74)

Alarms and StatisticsThis feature introduces the ability to provision the alarm severity for specificLSPs. The following section was updated for this feature:

• “Provisioning the alarm severity for a specific LSP” (page 76)

Configuring a hop-by-hop LSPThe section “Configuring a hop-by-hop LSP” (page 64) was updated toinclude information about a hop-by-hop LSP setup using theLdpQoscomponent.

MPLS on ATM IP FPThis feature provides support for MPLS on the ATM IP FP. The followingsections were updated:

• “MPLS in Passport nodes” (page 28)

Text conventionsThis document uses the following text conventions:

• nonproportional spaced plain type

Nonproportional spaced plain type represents system generated text ortext that appears on your screen.

• nonproportional spaced bold type

Nonproportional spaced bold type represents words that you should typeor that you should select on the screen.


241-5701-445 2.2S1

• italics

Statements that appear in italics in a procedure explain the results of aparticular step and appear immediately following the step.

Words that appear in italics in text are for naming.

• [optional_parameter ]

Words in square brackets represent optional parameters. The commandcan be entered with or without the words in the square brackets.

• <general_term >

Words in angle brackets represent variables which are to be replaced withspecific values.

• UPPERCASE,lowercase

Passport commands are not case-sensitive and do not have to matchcommands and parameters exactly as shown in this document, with theexception of string options values (for example, file and directory names)and string attribute values.

• |

This symbol separates items from which you may select one; forexample, ON|OFF indicates that you may specify ON or OFF. If you donot make a choice, a default ON is assumed.

• ...

Three dots in a command indicate that the parameter may be repeatedmore than once in succession.

The term absolute pathname refers to the full specification of a path startingfrom the root directory. Absolute pathnames always begin with the slash ( / )symbol. A relative pathname takes the current directory as its starting point,and starts with any alphanumeric character (other than /).

About this document 17


Related documentsFor the complete list of documents contained in the Passport documentationlibrary, see 241-5701-001Passport 7400, 15000 Documentation Guide.

See the following Passport documents for information related to MPLS:

• 241-5701-600Passport 7400, 15000 Configuration Guide

• 241-5701-805Passport 7400, 15000 Understanding IP

• 241-5701-810Passport 7400, 15000 Configuring IP

• 241-5701-060Passport 7400, 15000 Components

• 241-5701-500Passport 6400, 7400, 15000 Alarms

How to get more helpFor information on training, problem reporting, and technical support, see the“Nortel Networks support services” section in the product overviewdocument.


241-5701-445 2.2S1

19


Chapter 1Overview

For an overview of multiprotocol label switching (MPLS), see the followingsections:

• “What is MPLS technology?” (page 19)

• “How is MPLS implemented in Passport networks?” (page 21)

• “Why use MPLS?” (page 22)

• “How does MPLS work?” (page 22)

• “MPLS in Passport nodes” (page 28)

What is MPLS technology?MPLS is a label-swapping, networking technology that forwards packettraffic over multiple, underlying layer-2 media. This technology integrateslayer-2 switching and layer-3 routing by linking the layer-2 infrastructurewith layer-3 routing characteristics. Layer-3 routing occurs at the edge of thenetwork, and layer-2 switching takes over in the MPLS network core. SeeFigure “MPLS technology” (page 20).

Essentially, MPLS forwards a packet by swapping labels at each node in itspath. MPLS makes it possible to create new label formats without having tochange routing protocols. For example, MPLS traffic can include internetprotocol (IP), frame relay, ATM, and even optical waveforms.

20 Chapter 1 Overview

241-5701-445 2.2S1

Figure 1MPLS technology

In its generic concept, MPLS can switch a frame from any kind of layer-2 linkto any other kind of layer-2 link. At this stage in the development of itsstandards, MPLS supports ATM, frame relay, Ethernet, and point-to-pointprotocol (PPP). Because traffic flow is independent of the MPLS controlprotocols, MPLS will be able to support routing protocols that have not yetbeen defined without any need for the underlying forwarding hardware tochange.

With MPLS, layer-3 traffic flows take advantage of the layer-2 trafficengineering abilities and quality of service (QoS) performance, withoutlosing the benefit of existing best-effort, hop-by-hop routing.

MPLS is an emerging standard for network-layer packet forwarding, based ona number of signaling protocols proposed by the Internet Engineering TaskForce (IETF). Among these protocols are the label distribution protocol(LDP), border gateway protocol (BGP), resource reservation protocol(RSVP), and constraint-based routing using LDP (CR-LDP). These signaling

PPT 2888 001 AA

MPLS network

MPLSnode

MPLSnode

Packet Packet label Packet

Forwardingon address

Forwardingon address

Forwardingon label

router router

Chapter 1 Overview 21


protocols distribute labels and forward MPLS traffic. The choice of protocoldepends on factors such as the location and role of the switching node. Insome cases, a node uses more than one distribution protocol.

How is MPLS implemented in Passport networks?In Passport networks, MPLS transports IP traffic over ATM infrastructure,allowing carriers and large enterprises to send IP data easily across the ATMbackbone. MPLS functionality at the control plane allows carriers to useexisting ATM hardware to efficiently transport IP traffic. Passport nodes runboth an IP routing protocol and the MPLS signaling protocols LDP and CR-LDP. These protocols allow the Passport nodes to establish label switchedpaths, which are essentially VCCs, over the ATM infrastructure. MultipleLSPs, with different quality of service and hot standby LSPs, can beconfigured to the same destination.

Passport nodes in the MPLS network can also run an ATM control plane tosupport ATM services. This hybrid method of running both control protocolsindependently is called ships-in-the-night mode.

The Passport network’s ATM infrastructure allows MPLS traffic to use theATM queueing and traffic management capabilities. This practice providesthe ability to deliver end-to-end QoS for IP traffic.

The Passport implementation of MPLS takes advantage of the distributednature of the Passport software. The LDP functionality, which drives theMPLS protocol, is not restricted to the control processor (CP) but isdistributed to the function processors (FP). In some cases, the only processingexecuted on the CP is the generation and handling of some of the LDPmessages. The FP handles all other MPLS functions. This distributedstructure improves the overall scalability and resource usage for largenetworks.


241-5701-445 2.2S1

Why use MPLS?Carrier organizations and large enterprises typically use MPLS in theirbackbone networks to improve network resource usage. As the key to thefuture of large-scale IP networks, MPLS provides the following benefits:

• independence of function—In MPLS, the forwarding plane is separatedfrom the routing protocol control plane, so that the MPLS core performsa simple forwarding function completely independently of the packetcontent. This practice allows policy and routing decisions to be appliedonly once at the network edge.

• traffic engineering—MPLS channels the operation of IP routing so thattraffic can be steered to achieve efficient network resource usage andoptimal performance. The grouping of LSPs into LSP groups, allows formultiple LSPs, of different quality of service, to the same FECdestination.

• resource control—MPLS allows you to control valuable resourcesprecisely, for example, through the definition of different classes ofservice.

• network evolution—MPLS is developing into a robust network in whicha single, unified protocol operates over multiple, underlying layer-2technologies.

• traffic aggregation—MPLS VC merge capability allows you to aggregateIP traffic towards a destination.

How does MPLS work?MPLS is a forwarding mechanism that works by applying a label to IP trafficentering the network. The label acts as a shorthand representation of the IPpacket header. As the traffic moves through the network, MPLS swaps thelabel at each node on the route, according to a pre-defined label database atthat node. At the egress side of the MPLS network, the packet is decapsulated,and continues under the IP routing protocol.

Figure “MPLS network” (page 23) shows an MPLS network with a numberof Passport nodes. The nodes at the edges of the network are label edgerouters (LER). The LER nodes provide ingress and egress functions for IPtraffic in the MPLS network. The core nodes are label switched routers



(LSR). The LSR nodes provide the high-speed switching functions for thenetwork. The path of data between the MPLS nodes is a label switched path(LSP). An LSP is a unidirectional tunnel through the network.

For more information on MPLS operation, see the following sections:

• Figure “MPLS network” (page 23)

• “In the network core” (page 24)

• “In hop-by-hop routes” (page 24)

• “In explicit routes” (page 26)

Figure 2MPLS network

At the edge of the networkWhen IP traffic arrives at an LER, MPLS applies the label for the first time.To do this, the LER analyzes the information in the IP packet header, andclassifies traffic according to its destination and class of servicecharacteristics. The destination can be as broad as a router identifier or IPaddress prefix, or it can be as specific as a full 32-bit IP host address.

PPT 2888 002 AA

MPLS network

LSP for FEC1

LSP for FEC2

LER

LERLER

LSR

FEC2

FEC1

FEC1

FEC2

LSR

LSR


241-5701-445 2.2S1

At the LER, MPLS uses the concept of a forwarding equivalence class (FEC)to map incoming traffic to an LSP. Essentially, a FEC defines a group ofpackets that are forwarded over the same path with the same forwardingtreatment. This means that all the packets with the same FEC can be mappedto the same label.

For each FEC, the LER sets up an LSP through the network to the destinationdefined by the FEC. After the traffic is assigned a FEC, the LER applies alabel based on the label information base (LIB). The LIB maps each FEC toan LSP label that defines the next-hop link. Because the underlying layer-2media is ATM, MPLS uses the VCI of the ATM VCC as the label.

To forward the packet, the LER looks up the FEC in the LIB, and thenencapsulates the packet with the LSP label. The LER then sends the packetout on the next-hop interface defined in the LIB.

In the network coreWhen a labeled packet arrives at an LSR, the LSR extracts the incoming labeland uses it as an index into the LIB. When the LSR finds the appropriate LIBentry, it extracts the corresponding outgoing label and swaps it with theincoming label in the packet. The LSR then sends the packet on the outgoinginterface to the appropriate next hop specified in the LIB entry.

Eventually, the packet reaches the edge of the MPLS network. At that point,an LER removes the encapsulating label, and the packet continues to itsdestination according to conventional IP routing methods.

In hop-by-hop routesThe basic LSP is a hop-by-hop LSP. A hop-by-hop LSP is part of a tree fromevery source to a particular destination. See Figure 3, “Hop-by-hop LSP,”(page 25). For these LSPs, MPLS builds a set of trees that duplicate thedestination-based trees that IP uses to forward traffic. MPLS converts thedestination-based trees into label-switching trees.

With IP routing, each router along a path examines a packet’s destination andchooses a new link. With MPLS, the packet follows the same path it wouldtake with IP routing, but the packet is assigned a label and link at the ingressLER. When the packet arrives at the next hop, its label is replaced with the



next label along the tree toward the destination and sent to the correspondinglink. In this way, the packet follows the IP routing path, but its IP header isnever checked along the route.

At each node, MPLS creates the tree by allocating a label for every next-hopMPLS destination and exchanging the labels with those peers. The exchangeis accomplished through LDP request and mapping messages. For example,in figure “Hop-by-hop LSP” (page 25), LSR G maps incoming labels 14, 23,and 24 to outgoing label 30.

Note: In the diagrams in this section, the node labelling (A, B, C)represents the actual IP addresses used by the software.

Figure 3Hop-by-hop LSP

PPT 2888 003 AA

A

B

C

E

F

H

G

D

LIBIn Out14 3023 3024 30

21

23 30

29

2414

12

5


241-5701-445 2.2S1

In explicit routesOne of the major advantages of MPLS is its ability to steer traffic, for exampleto avoid congestion or to meet the QoS of the traffic. MPLS allows thenetwork operator at the source node to determine an explicit route LSP (ER-LSP) that defines the path the traffic will take. Multiple ER-LSPs, withdifferent quality of service, can be configured to the same destination.

Unlike the hop-by-hop LSP, the ER-LSP does not have to follow the IP tree.Instead, the ER-LSP builds a path from source to destination. See figure “ER-LSP” (page 26).To build this path, MPLS embeds the explicit route into thelabel request message using the protocol called constraint-based routingusing LDP (CR-LDP).

Figure 4ER-LSP

There are two types of ER-LSPs: strict ERs and loose ERs. A strict ERspecifies the exact path a packet will take. MPLS at the source node explicitlyindicates all the hops along the path between the end points. A loose ERspecifies some, but not all, of the hops a packet must traverse on the way toits destination.

PPT 2888 004 AA

A

B

C

E

F

H

G

D

LIBIn Out14 4

21

2

4

14Route = D,F,H{ }



Figure “Strict and loose ER LSPs” (page 27) shows the difference betweenstrict and loose ERs. The strict ER in the illustration is specified at LER A as{LSR B, LSR D, LSR E}. In establishing a strict ER, MPLS does not need tocheck the IP routing tables, since the exact route is defined.

The loose ER in figure “Strict and loose ER LSPs” (page 27) is specified atLER A as {LSR E}. In the illustration, the complete path can be either{LER A, LSR B, LSR D, LER E} or {LER A, LSR C, LSR D, LER E}. Inthe loose segment between LER A and LSR E, MPLS checks the IP routingtables during call setup to determine the best next hop to the next specifiedER hop in the route.

In Passport MPLS, loose ERs are pinned ERs. This means that, after the routeis set up, it does not change unless failure occurs, even if the IP routing tableschange.

Figure 5Strict and loose ER LSPs

The network operator can specify each hop in an ER as either an ingressinterface address or an IPv4 prefix. For example, in figure “ER specification”(page 28), the strict ER can be identified at LER A as {LSRB_ID, 20.1.2.6,20.1.2.8}.

PPT 2888 005 AA

A

B D E

C

Strict ER

Loose ER


241-5701-445 2.2S1

Figure 6ER specification

MPLS in Passport nodesFor ER-LSPs, Passport nodes have both LER and LSR functionality. Thismeans that Passport nodes can originate ER-LSPs. For hop-by-hop LSPs,Passport nodes act only as ATM LSRs. This means that a Passport node canreceive and pass on LSP traffic, but cannot originate a hop-by-hop LSP.

PPT 2888 006 AA

A

B D E

C

20.1.2.3

20.1.2.5 20.1.2.7

20.1.2.4 20.1.2.6 20.1.2.8

29


Chapter 2MPLS description

For an explanation of how MPLS operates, see the following sections:

• “MPLS protocols” (page 29)

• “Creation of LSPs” (page 34)

• “Traffic engineering with MPLS” (page 38)

• “MPLS using ATM media” (page 40)

• “LSP recovery” (page 42)

MPLS protocolsThe MPLS protocols are used to set up, maintain, and tear down labelswitched paths (LSPs). The protocols allow LSP establishment by mappingnetwork-layer routing information to data link-layer switched paths. MPLSroutes are not supported in other protocols. LSPs are similar to static routes,and do not get exported; they appear only in the local routing table. For adescription of MPLS protocols, see the following sections:

• “Label distribution protocol” (page 29)

• “Constraint-based routing using LDP” (page 32)

Label distribution protocolThe basic signaling protocol in MPLS is the label distribution protocol(LDP). As its name indicates, LDP provides the method of distributing labelbinding information between MPLS nodes, or peers.

30 Chapter 2 MPLS description

241-5701-445 2.2S1

LDP messagesThere are four categories of LDP messages:

• discovery messages

These hello messages announce and maintain the presence of an LSR inthe network. An LSR periodically sends a hello message as a UDP packetto the LDP port of all its neighbors.

• session messages

These messages establish, maintain, and terminate sessions betweenLDP peers. When an LSR learns of another LSR through the hellomessage, it begins the LDP initialization procedure by opening a TCPconnection. In the initialization procedure, the LSRs exchangeinitialization messages. When the procedure is successfully completed,the two LSRs are peers.

At this stage, the LSRs exchange address messages, which are used tocreate databases of mapping between peer LDP identifiers and next-hopaddresses. After an LSR has advertised its interface addresses, it can sendlabel request or label mapping messages. If there is no other informationto exchange, LSR peers exchange keepalive messages to maintain thesession. To terminate a session, the LSR sends a shutdown message.

Chapter 2 MPLS description 31


• advertisement messages

These messages set up LSPs by creating, changing, and deleting labelmappings for FECs. An LSR requests a label with the request messageand advertises a label mapping with the mapping message.

The times at which the LSRs send these messages depend on the labeladvertisement mode and the label distribution control mode. PassportMPLS uses the downstream-on-demand label advertisement mode andthe ordered label distribution mode.

In the downstream-on-demand mode, shown in figure “Downstream-on-demand label advertisement” (page 32), the upstream LSR requests labelmappings and the downstream LSR assigns the labels and informs theupstream LSR. In the illustration, LSR B, on the egress side, is thedownstream LSR, and LSR A, on the ingress side, is the upstream LSR.

In the ordered distribution control mode, an LSR transmits a labelbinding only when it is the egress LSR for that FEC or when it hasreceived the binding from a downstream LSR. Otherwise, the LSR mustwait until it receives a label before returning a label to the next upstreamLSR.

• notification messages

These messages provide advisory information, such as status informationand signal error conditions.


241-5701-445 2.2S1

Figure 7Downstream-on-demand label advertisement

LDP encodingLDP uses a type-length-value (TLV) encoding scheme for the informationcarried in LDP messages. Each LDP message is made of specific TLVs. Forexample, the label request message contains a FEC TLV that defines the FECfor the LSP as an IPv4 address or a router identifier (IPv4 address prefix). Theaddress list TLV in the address message defines the interface addresses of theadvertising LDP peer. The label mapping message contains a FEC TLV and alabel TLV. A label TLV contains the VCI of the ATM VCC link.

Constraint-based routing using LDPConstraint-based routing using LDP (CR-LDP) is an extension of the LDPprotocol. CR-LDP allows forwarding on the basis of constraints such asexplicit routes or traffic parameters. CR-LDP permits the traffic engineeringthat is essential to the management and predictability of large networks.

PPT 2888 007 AA

Ingressside

Egressside

Upstream DownstreamMapping

Request

A Brouter router



CR-LDP builds on the LDP protocol, using the same mechanisms andmessages for peer discovery, session establishment, label distribution, anderror handling. The extensions to LDP are implemented in the followingadded TLVs in the label request and label mapping messages:

• explicit route (ER) and ER-hop TLVs

The ER TLV contains a list of nodes that defines the path of an ER-LSP.The ER TLV is made of one or more ER-hop TLVs. Each ER-hop TLVdefines one hop in the ER, using an IPv4 address prefix or a routeridentifier, and specifies whether the ER is strict or loose.

• traffic parameters TLV

This TLV defines the required characteristics of a constraint-based LSP.This TLV is included in a CR-LDP label request message to specify thetraffic parameters needed for the requested ER-LSP. When the LSRreceives the request, MPLS negotiates with the ATM software to reservethe requested bandwidth. If the resources are available, the LSR reservesthe bandwidth. If not, the LSR returns a notification message with theresource_unavailable status code. The TLV contains the following fields:

— the peak data rate (PDR) and peak burst size (PBS) fields define themaximum rate at which data can be sent to the ER-LSP

— the committed data rate (CDR) and committed burst size (CBS)fields define the rate at which the MPLS domain commits to beingavailable to the ER-LSP

— the frequency field constrains the amount of variable delay that thenetwork can introduce into the CDR

• LSP identifier (LSPID) TLV

This TLV provides a unique identifier for the LSP within the MPLSnetwork.


241-5701-445 2.2S1

Creation of LSPsBefore data can transfer over an LSP, the LSP must be set up using the LDPor CR-LDP protocol. For more information on LSP call setup see thefollowing sections:

• “Call setup for hop-by-hop LSPs” (page 34)

• “Call setup for ER-LSPs” (page 35)

Note: In the diagrams in this section, the node labelling (A, B, C)represents the actual IP addresses used by the software.

Call setup for hop-by-hop LSPsFigure “Call setup for hop-by-hop LSPs” (page 35) shows the hop-by-hopLSP setup process. The diagram shows the downstream-on-demand labeladvertisement mode and the ordered distribution control mode used in thePassport network.

1 At LER A, MPLS generates a label request message. LER A determinesthe link to the next hop (LSR B in the example) from the IP routing table,and sends on a label request message to LSR B.

2 At LSR B, MPLS receives the label request. MPLS determines the linkto the next hop (LSR D in the example) from the IP routing table, andsends on a label request message. The same process occurs at LSR D.

3 The label request message terminates at the destination LER, node F.MPLS at node F sends a label mapping message back to LSR D. Themapping message contains the label for LSR D to use in sending packetsto LER F.

Because the underlying layer-2 media is ATM, MPLS uses the VCI of theATM VCC as the label. The mapping between the FEC and the VCC ismaintained in the LIB. To determine the FEC/label mapping, the LSRsnegotiate with the ATM software to reserve a VCC.

In the example, MPLS at LER F sends a message to LSR D containingthe label 17.

4 MPLS at LSR D receives the mapping message and updates the LIB withthe label information for LER F. In the example, MPLS updates thedatabase with 17 as the outgoing label for FEC 20.1.2.3.



5 This process continues until the originating LER receives the mappingmessage and establishes the LSP.

Figure 8Call setup for hop-by-hop LSPs

Call setup for ER-LSPsFigure “Call setup for ER-LSPs” (page 36) illustrates the ER-LSP setupprocess for a strict ER. The process takes the following steps:

1 MPLS at LER A generates a label request message. The messagecontains ER-hop TLVs that define the ER path through nodes C and E toLER F.

PPT 2888 008 AA

B D

A F

Labelmapping

Labelrequest1

2

3

4

Routing tableAddr Next hop20.1.2.3 LSR D

Routing tableAddr Next hop20.1.2.3 LSR B

LIBIn FEC Out12 20.1.2.3 03


IP packet20.1.2.3 20.1.2.3

LSP

LDP messages


241-5701-445 2.2S1

2 At LSR C, MPLS receives the label request message and determinesfrom the ER hop list that the next-hop node is LSR E. Since the route ispre-defined, there is no need to check the IP routing table. MPLSremoves LSR C from the path list, and sends the message to LSR E. Theprocess repeats at LSR E.

3 At LER F, the request message terminates. MPLS sends a label mappingmessage back to LSR E. The mapping message contains the label fornode E to use in sending packets to LER F. In the example, the label is 13.

4 LSR E receives the mapping message, and updates the LIB entry forLER F.

5 This process continues until LER A receives the mapping message andestablishes the ER.

Figure 9Call setup for ER-LSPs

PPT 2888 009 AA

Labelmapping

Labelrequest:C,E,F

1

5

2 3

4LIBIn FEC Out07 20.1.2.3 19


IP packet20.1.2.3

20.1.2.3

B

C E

FA

D

ER

CR-LDP messages



Call setup for a loose ER is a combination of the process for a hop-by-hopLSP and the process for a strict ER. The loose ER setup works like the strictER setup for those segments of the route that have defined end points. In theloose segments, MPLS accesses the IP routing tables to get next-hopinformation.

LDP/CR-LDP interworkingFigure “LDP/CR-LDP interworking” (page 38) shows a situation in whichthe LDP and CR-LDP protocols work together. In this case, traffic flows upto a point in the network core on an LSP. At a certain LSR, traffic engineeringconditions require the traffic to continue on an ER-LSP. LDP/CR-LDPinterworking allows a tandem LSR to aggregate LDP traffic at the LDP/CR-LDP boundary into a traffic-engineered core based on CR-LDP.

There are three possible interworking situations:

• LDP to CR-LDP to LDP

In this case, an LSP begins in the LDP domain, tunnels through the CR-LDP domain, and terminates in another LDP domain.

• CR-LDP to LDP

In this case, an LSP begins in the CR-LDP domain and ends in the LDPdomain.

• LDP to CR-LDP

In this case, an LSP begins in the LDP domain and terminates in the CR-LDP domain.

In the first interworking situation, the first and last nodes in the CR-LDPdomain handle the conversion from one protocol to the other. In the other twocases, only one conversion is needed, and the egress CR-LDP node or theingress CR-LDP node handles the conversion.

In LDP to CR-LDP interworking, the ingress node MPLS in the CR-LDPdomain translates all ingress LDP messages into CR-LDP messages. Thenetwork operator at that node provisions the interworking ER-LSP and insertsan ER hop list into the label request message. (The provisioned FEC element


241-5701-445 2.2S1

must match the FEC in the hop-by-hop request message exactly.) In theexample in figure “LDP/CR-LDP interworking” (page 38), the ER-hop TLVsspecifying LSR F and LSR H are inserted into the label request at LSR D.

If the LSP terminates in the LDP domain, the egress LSR in the CR-LDPdomain translates the CR-LDP messages back into LDP messages.

Figure 10LDP/CR-LDP interworking

Traffic engineering with MPLSWith the increasing demand and explosive growth of the Internet, carriersneed a network infrastructure that is dependable and offers consistent,predictable network performance. The traffic engineering capabilities ofMPLS provide a solution for this situation. The cornerstone of the MPLSsolution is the ER-LSP, which the network operator can manipulate to controlthe transport of IP traffic.

The ER-LSP can be used to map traffic flows onto the network, independentlyof the layer-3 topology, so that each application receives the QoS it needs.MPLS allows the network operator to configure an LSP group, with multiple

PPT 2888 010 AA

A

B

C

E

F

H

G

21

29

24

14

12

5

Labelrequest F,H{ }

6

D

LDP CR-LDP



LSPs, to the same FEC destination. Each LSP group has up to four activeprimary LSPs, with different QoS and up to seven hot standby backup LSPsfor each primary LSP, to the same FEC destination.

Each LSP in an LSP group is configured to a particular service category calledMPLS service category (MSC). Each MSC has its own QoS requirements.There are a maximum of eight MSC classes (0-7) in an LSP group. Thenetwork operator can define a one-to-one mapping between IP class ofservice (COS) and MPLS service category (MSC). Each of the four currentlyavailable IP COS values (0,1,2,3) can be mapped to a unique MSC value of 0to 7. As there are four IP COS values and eight MSC values, it is expected thatsome MSC values will not be mapped to an IP COS value.

Figure “MPLS traffic engineering” (page 40) shows a simple example ofMPLS traffic engineering. In the example, a video server is configured atLSR A on the ingress side, and a video client is configured at LSR F on theegress side. Regular IP traffic runs across an ATM connection from LSR A toLSR F, following a best-effort, shortest path. If the video stream is introducedon this path, the path becomes congested, and the QoS will degrade. WithMPLS, the network operator can configure an ER-LSP through LSR B andLSR D. The ER-LSP forces the video traffic to follow the longer route, butmaintains the QoS.

To guarantee the service in case of link failures, the network operator canconfigure a maximum of seven standby LSPs per primary LSP. A standbyLSP is an LSP that can take over the traffic carried by the primary LSP, oranother standby LSP, if that LSP should fail. The standby LSP serves in thesame MPLS service category (MSC) as the primary LSP.

Standby LSPs are hierarchically ordered under the primary LSP. The orderingdetermines the order in which a standby LSP takes over in the event of aprimary failure (and which standby would take over in the event of a standbyfailure). In order to provide fast switchover capability, a standby LSP is in theestablished state, and occupies bandwidth along the backup LSP path.

LSP2 represents a standby LSP path from LSR A through LSR C and LSR Eto LSR F. If a link fails on LSP1, the traffic switches to LSP2, the first standbyin the primary LSP’s standby list.


241-5701-445 2.2S1

Since the primary LSP is intended to be the preferred LSP for traffic use, acheck of all the primary LSPs under all LSP groups is performed every fiveseconds. If a primary LSP is found to be available to carry traffic, but has astandby that is currently carrying the traffic, the data path is switched to thatof the primary LSP.

Figure 11MPLS traffic engineering

MPLS using ATM mediaThe supporting layer-2 medium for Passport MPLS is ATM. For informationon the interaction between MPLS and ATM see the following sections:

• “Label encapsulation” (page 41)

• “Ships-in-the-night operation” (page 41)

• “QoS mapping” (page 41)

PPT 2888 011 AA

IP traffic

Hot stand-by

ER-LSP

From server To client

C E

F

LSP2

LSP1

A

B D

router router



Label encapsulationPassport MPLS supports two types of label encoding:

• single-level VCI encoding

• null shim header encoding

For operation in the Passport network, MPLS uses the ATM VCI as the label.The label is contained in the combined VCI and VPI fields of the ATM header.

The shim header, defined by MPLS standards, is a generic label that is placedbetween the layer 2 and layer 3 headers. The shim label is commonly used forPPP and LAN hardware. Passport MPLS places a null shim label in theheaders at the LERs to support interworking with LSRs from other vendorswhose products use shim headers.

Ships-in-the-night operationPassport MPLS interacts with ATM in the operating mode called ships-in-the-night. In this mode, MPLS and ATM control planes share hardware ports, butwork independently. This mode of operation allows a Passport node tofunction simultaneously as an ATM switch and an MPLS LSR. The MPLScontrol plane provides IP-based services, and the ATM control plane providesATM-based services. The two control planes share memory, VPI/VCI space,processing capacity, and traffic management capabilities.

In ships-in-the-night mode, MPLS and ATM share the ATM VPI/VCI space.Initially, the network operator configures the MPLS label range. Then, theVPI/VCI label range for MPLS is negotiated with the ATM software duringLDP peer initialization. After negotiation, MPLS can use only the VPI/VCIrange agreed to. ATM can use the entire VPI/VCI space.

The network operator defines one VCC as the MPLS control channel for eachLDP interface.

QoS mappingTo support mission-critical traffic, carriers need to be able to guarantee anend-to-end QoS for a traffic path. To do this, the network operator configuresan ER-LSP with a set of traffic parameters provisioned to define its QoS. The


241-5701-445 2.2S1

QoS values defined by MPLS traffic parameters map directly to ATM servicecategories. Table “Mapping of MPLS traffic parameters to ATM servicecategories” (page 42) shows this mapping.

After the ER-LSP is set up over ATM media with the appropriate QoS, itsMPLS traffic is treated the same as ATM traffic. Bandwidth reservation andtraffic management for the ER-LSP are based on the corresponding ATMservice category indicated by its traffic parameters.

LSP recoveryIf a failure occurs during LSP setup, the LSR immediately downstream fromthe failure point releases the LSP to the egress LER. The LSR immediatelyupstream from the failure point sends a notification message to the ingressLER to tear down the connection.

The ingress LER releases the LSP to the failure point and begins a recoveryprocess. If there is a hot stand-by path configured, the LER shifts the trafficto the stand-by path. Otherwise, the LER attempts to set up a new LSP to thedestination. This rerouting attempt is called global repair.

Table 1Mapping of MPLS traffic parameters to ATM service categories

ATM servicecategory

MPLS traffic parameters

PDR PBS CDR CBS Frequency

CBR.1 PCR(CLP0+1)

CDVT PCR(CLP0+1)

CDVT Very frequent

VBR.3 (rt) PCR(CLP0+1)

CDVT SCR (CLP0) MBS (CLP0) Frequent

VBR.3 (nrt) PCR(CLP0+1)

CDVT SCR (CLP0) MBS (CLP0) Unspecified

UBR PCR(CLP0+1)

CDVT — — Unspecified

43


Chapter 3Configuring MPLS

For information on how to configure MPLS, see the following sections:

• “Implementation of MPLS” (page 43)

• “Prerequisites to configuring MPLS” (page 45)

• “Installing MPLS software” (page 45)

• “Configuring ports and interfaces” (page 46)

• “Configuring LSPs” (page 57)

• “LDP/CR-LDP interworking configuration” (page 67)

• “Locking and unlocking an LSP” (page 70)

For general configuration information and basic configuration procedures,see 241-5701-600Passport 7400, 15000 Configuration Guide. For moredetailed definitions of the components you use to configure MPLS, see241-5701-060Passport 7400, 15000 Components.

Implementation of MPLSThe figure“MPLS and related components” (page 44) shows the componentstructure for MPLS, and its related components and subcomponents.

44 Chapter 3 Configuring MPLS

241-5701-445 2.2S1

Figure 12MPLS and related components

PPT 3019 001 AA

EM

Vr

Ip

PP

Ldp

Peer

LspGroup

Lsp

Path

XcMapHop

IpForwardIpv4AddrMscMap

AtmMpe

AtmConn

Atmlf

Vcc

Mpls

Session

Te

CrQos

Msc

LdpQ

IpPort

Nep

MplsPort

Ldplf

InSeg

OutSeg

Adjacency

Chapter 3 Configuring MPLS 45


Prerequisites to configuring MPLSBefore you configure MPLS on a Passport node, you must

• remove any pre-PCR2.2 version of MPLS from the node.

• make sure that the IP software is installed on the node (for moreinformation, see 241-5701-810Passport 7400, 15000 Configuring IP)

• make sure that the atmmpe (wanDte) software is installed on the node(for more information, see 241-5701-810Passport 7400, 15000Configuring IP)

Installing MPLS softwareYou can install MPLS software after the base software and the IP and ATMMPE features have been installed on the Passport node. To install MPLSsoftware, use the following procedure:

1 Add the MPLS application to the application version list of the Softwarecomponent.

set sw avl mpls_<version>

where:

<version> is the application version from the Passport ReleaseSupplement.

2 Add a logicalProcessorType component.

add sw lpt/<lpt_name>

where:

<lpt_name> is any mnemonic (for example, mpls_lp).

3 Set the LPT feature list to include the MPLS feature.

set sw lpt/<lpt_name> fl mplsCrldp

where:

<lpt_name> is the mnemonic you used in step 2.


241-5701-445 2.2S1

Configuring ports and interfacesBefore you can configure MPLS, you must set up the logical ports andinterfaces for the MPLS software to use. To do this setup, use the followingprocedures:

• “Configuring the virtual router and protocol port” (page 46)

• “Configuring the ATM media and links” (page 47)

• “Configuring the IP port” (page 50)

• “Configuring the MPLS port” (page 54)

• “Configuring the MPLS component” (page 51)

Configuring the virtual router and protocol portThe first stage in configuring MPLS is to create the virtual router, the IPcomponent, and the protocol port. The figure “Component tree forconfiguring the virtual router and protocol port” (page 46) shows thecomponents configured in this procedure.

Figure 13Component tree for configuring the virtual router and protocol port

1 Add a Vr component.

add Vr/<vrId>

where:

<vrId> is an alphanumeric string of up to eight characters that identifiesthe VR.

2 Add an Ip component as a subcomponent of the Vr component.

PPT 3019 002 AA

EM

VirtualRouter (Vr)

Ip

ProtocolPort (Pp)



add Vr/<vrId> Ip

where:

<vrId> is the name assigned to this VR.

3 Add a ProtocolPort (PP) component as a subcomponent of the Vrcomponent.

add Vr/<vrId> pp/<pp_id>

where:


<pp_id> is an alphanumeric string of up to 20 characters that identifiesthe PP.

Configuring the ATM media and linksAfter the VR and PP are configured, you need to perform the following tasks:

• Configure the atmmpe service.

• Configure the ATM interface.

• Link theAtmMpe component to the PP you defined previously.

• Link theAtmMpe component to the ATM interface.

• Link the PP to theAtmMpe component.

The figure “Component tree for configuring the ATM media and links”(page 48) shows the components configured in this procedure.


241-5701-445 2.2S1

Figure 14Component tree for configuring the ATM media and links

1 Add the AtmMpe component.

add AtmMpe/<mpe_name>

where:

<mpe_name> is a decimal in the range 0 to 255

2 Add the AtmConnection component as a subcomponent of the AtmMpecomponent.

add AtmMpe/<mpe_name> AtmConn/<conn>

where:

<mpe_name> is the identifier assigned to this AtmMpe component.

<conn> is a decimal in the range 0 to 255.

3 Link the AtmMpe component to the VR PP.

set AtmMpe/<mpe_name> linkToProtocolPort Vr/<vrId> pp/<pp_id>

where:



PPT 3019 003 AA

EM

VirtualRouter (Vr)

ProtocolPort (Pp)

AtmMultiprotocolEncapsulation (AtmMpe)

AtmConnection (Ac)

AtmInterface(Atmlf)

VirtualChannelConnection (Vcc)

NailedUpEndpoint (Nep)



<pp_id> is the identifier assigned to this PP.

4 Add the AtmIf component.

add atmIf/<n> Vcc/<vpi.vci>

where:

<n> is the instance value of the AtmIf component in the range of 1 to1024.

<vpi.vci> is the identifier of the VP and VC of the virtual channel.

5 Define the ATM VCC as a nailed-up connection.

add atmIf/<n> Vcc/<vpi.vci> Nep

where:

<n> is the instance value of the AtmIf component.


6 Modify the ATM VCC atmServiceCategory if desired.

set atmIf/<n> vcc/<vpi.vci> vcd Tm atmServiceCategoryconstantBitRate

where:



vcd is the VirtualChannelDescriptor.

Note: When an atmIf/<n>/<vpi.vci> channel is created, the defaultatmServiceCategory unspecifiedBitRate is used. If you anticipate that theuser traffic on the link will run near its maximum capacity, provision theatmServiceCategory with the constantBitRate value, to ensure that thecontrol traffic flowing through the channel will not starve and LSPs will notbe affected.

7 Link the AtmConn component to the Nep component.

set atmMpe/<mpe_name> AtmConn/<conn> AtmConnectionAtmIf/<n> Vcc/<vpi.vci> Nep

where:


<conn> is the identifier assigned to this instance of the AtmMpe AtmConnsubcomponent.


241-5701-445 2.2S1


<vpi.vci> is the identifier of the VP and VC of the virtual channel

8 Link the PP component to the AtmMpe component.

set Vr/<vrId> pp/<pp_id> linkToMedia<media_application>

where:



<media_application> is the identifier of the AtmMpe component.

Configuring the IP portTo configure the IP port, you need to add an IP port as a subcomponent of thePP and define its IP address. The figure “Component tree for configuring theIP port” (page 50) shows the components configured in this procedure.

Figure 15Component tree for configuring the IP port

1 Add an IpPort component as a subcomponent of the PP component.

add Vr/<vrId> pp/<pp_id> IpPort

where:



PPT 3019 004 AA

EM

VirtualRouter (Vr)

ProtocolPort (Pp)

IpPort

IpLogicalInterface (LogicalIf)



2 Define the IP address for the port.

add Vr/<vrId> pp/<pp_id> IpPort logicalIf/<ip_address>

where:



<ip_address> is the 32-bit address assigned to this logical interface.

Note: An LSP connection created on a specific LdpIf component ispinned to the ipLogicalInterface component address provisioned underthe IP Port of the corresponding protocol port.The LdpIf component mustbe disabled prior to modifying or deleting the ipLogicalInterfacecomponent.

3 Define a network mask for the protocol port.

set Vr/<vrId> pp/<pp_id> IpPort logicalIf/<ip_address>netMask <mask>

where:



<ip_address> is the 32-bit address assigned to this logical interface.

<mask> is the network mask to be used with the IP address.

Configuring the MPLS componentBefore you can configure the MPLS port, you need to create the MPLScomponent under the VR and provision MPLS and LDP parameters. Thefigure “Component tree for configuring the MPLS component” (page 52)shows the components and attributes configured in this procedure.

Note:MPLS is supported on one virtual router only.


241-5701-445 2.2S1

Figure 16Component tree for configuring the MPLS component

1 Add the Mpls component as a subcomponent of the Vr component.

add Vr/<vrId> mpls

where:


2 Add the Ldp component as a subcomponent.

add Vr/<vrId> Mpls Ldp

3 Provision the Mpls component parameters.

set Vr/<vrId> mpls adminStatus <status> lsrIdProv<ip_address> lspGroupPolicy <policy>

where:


<status> is enabled (the default) to enable the LDP protocol on thisnode to establish relationships with neighbor LSRs, or disabled to disableLDP.

<ip_address> is an IP address for the node (known as the LSRidentifier), or 0 (the default) to indicate that the VR router ID must be used

PPT 3019 005 AA

EM

VirtualRouter (Vr)

MultiprotocolLabelSwitching (Mpls) adminstatus IsrIdProv IspGroupPolicy

Ldp maxLspPerPeer keepAliveHoldTimer helloTimer failedInitThreshold loopDetection hopCountLimit



as the node address for MPLS. If the Ospf routerid attribute is provisioned,then the LsrId attribute must be the same.

Note: If the LsrId attribute is changed, the MPLS ports will go down. Thisservice interruption is not reported.

<policy> is restrictive (the default) to define a restrictive policy (the LSRaccepts LSPs for those LspGroups defined on this LSR), or liberal todefine a liberal policy (the LSR accepts LSPs for all LspGroups exceptthose that are administratively disabled).

4 If required, change the routing preference. See 241-5701-805 Passport7400, 15000 Understanding IP for more information.

To change the routing preference attribute for MPLS LDP, enter thefollowing command:

set Vr/<vrId> Mpls defaultLdpMplsRtePref <route_pref>

To change the routing preference attribute for MPLS CRLDP, enter thefollowing command:

set Vr/<vrId> Mpls defaultCrLdpMplsRtePref<route_pref>

where:

<route_pref> is the routing preference. The attribute is a decimalnumber between 1 and 255 where 255 means the route is never put in theforwarding table.

Note: Attribute default is 8 for MPLS LDP and 10 for MPLS CRLDP.

5 Provision the Ldp component parameters.

set Vr/<vrId> mpls ldp maxLspPerPeer <max_lsp>keepAliveHoldTimer <ka_time> helloTimer <h_time>failedInitThreshold <threshold> loopDetection <loop>hopCountLimit <limit>

where:


<max_lsp> is a decimal number between 1 and 2000 that specifies theupper limit on the number of LSPs that can be set up for an LDPadjacency.

<ka_time> is the number of seconds in the range 1 to 15 specified forthe keepalive hold timer interval.


241-5701-445 2.2S1

<h_time> is the number of seconds in the range 1 to 10 specified for thehello timer interval.

<threshold> defines the threshold of initialization attempts in the rangeof 1 to 20. If this threshold is exceeded,failedInitSessionThresholdExceeded notification is generated.

<loop> is on to indicate that the LSP loop detection capability is enabled,or off to indicate that it is disabled. When you enable loop detection, youmust set the hopCountLimit attribute.

<limit> specifies the number of hops allowed for each LSP in the range2 to 40.

Note:Deleting the MPLS component does not delete the MPLS port. Allports must be deleted before deleting the MPLS component.

Configuring the MPLS portAfter the MPLS component has been created, you need to create the MPLSport under the protocol port and link the MPLS port to the nailed-up ATMconnection. The figure “Component tree for configuring the MPLS port”(page 55) shows the components and attributes configured in this procedure.



Figure 17Component tree for configuring the MPLS port

1 Prior to adding the MplsPort component, ensure that the IP port isunlocked and operational. Once this has been verified, add an MplsPortcomponent as a subcomponent of the PP component.

add Vr/<vrId> pp/<pp_id> mplsPort

where:



When you add the MplsPort component, the system automatically addsthe LdpIf component as its subcomponent. Only one LdpIf componentcan be configured under the MplsPort component. If more than one LdpIfcomponent is added, the LdpIf sessions will not establish.

2 Provision the MplsPort component parameters.

PPT 3019 006 AA

EM

VirtualRouter (Vr)

ProtocolPort (Pp)

MplsPort minorUtilAlarmThreshold majorUtilAlarmThreshold criticalUtilAlarmThreshold utilAlarmState

LabelDistributionProtocolIf (LdpIf) mediaName atmLabelMinIn atmLabelMinOut atmLabelMaxIn atmLabelMinOut


241-5701-445 2.2S1

set Vr/<vrId> pp/<pp_id> mplsPortminorUtilAlarmThreshold <minor>majorUtilAlarmThreshold <major>criticalUtilAlarmThreshold <critical> utilAlarmStatus<status>

where:



<minor> defines the threshold value (between 1 and 100) over which aminor alarm occurs to indicate three minutes of sustained total averageutilization above the threshold. A value of 100 disables the threshold.

<major> defines the threshold value (between 1 and 100) over which amajor alarm occurs to indicate three minutes of sustained total averageutilization above the threshold. A value of 100 disables the threshold.

<critical> defines the threshold value (between 1 and 100) over whicha critical alarm occurs to indicate three minutes of sustained total averageutilization above the threshold. A value of 100 disables the threshold.

<status> is enabled to enable the threshold for the utilization alarms, ordisabled to disable the alarms.

3 Link the MplsPort LdpIf subcomponent to the nailed-up ATM connection.

set Vr/<vrId> pp/<pp_id> mplsPort ldpIf mediaNameAtmIf/<n> Vcc/<vpi.vci> Nep

where:





Note: A change to the AtmMpe AtmConnection component requires thatthe change be reflected in the LdpIf mediaName attribute.

4 Provision the MplsPort LdpIf component parameters.

set Vr/<vrId> pp/<pp_id> mplsPort ldpIf atmLabelMinIn<min_in> atmLabelMaxIn <max_in> atmLabelMinOut<min_out> atmLabelMaxOut <max_out>

where:





<min_in> defines the minimum value of the ATM label that this LSR willreceive on this interface in the range 0 to 254 or 0 to 16127.

<max_in> defines the maximum value of the ATM label that this LSR willreceive on this interface in the range 0 to 254 or 0 to 16127.

<min_out> defines the minimum value of the ATM label that this LSR willsend on this interface in the range 0 to 254 or 0 to 16127.

<max_out> defines the maximum value of the ATM label that this LSRwill send on this interface in the range 0 to 254 or 0 to 16127.

Note 1: You cannot set the labelType attribute. It is always set toatmLabel.

Note 2: The label range must correspond to ATM VCI range values.

Note 3: If label range values span over VPs other than VPI 0, and theATM card being used is a CQC-based card, the AtmIf ConnMapOverridecomponent must be configured appropriately. ThenumNonZeroVpisForVccs attribute must be set to include all, or at leastsome, of the VPs indicated as desired under the LdpIf component for thelabel range. Atm media will permit LSP creation only on those VPs in LdpIflabel range which overlap with the ones specified under theConnMapOverride component

Configuring LSPsPassport nodes do not originate hop-by-hop LSPs. The LSPs that you will beconfiguring, then, are ER-LSPs. To configure LSPs, use the followingprocedures:

• “Configuring an LSP group and IP forwarding policy” (page 57)

• “Configuring the explicit route path” (page 60)

• “Configuring an ER-LSP” (page 61)

• “Configuring LSP quality of service” (page 64)

Configuring an LSP group and IP forwarding policyTo configure an LSP group, you must add theLspGroup component andconfigure the IP forwarding policy for the LSP group. The figure“Component tree for configuring an LSP group and IP forwarding policy”(page 58) shows the components configured in this procedure.


241-5701-445 2.2S1

Figure 18Component tree for configuring an LSP group and IP forwarding policy

1 Add an LspGroup component under the Mpls component.

add Vr/<vrId> Mpls lspGroup/<lspg_name>

where:


<lspg_name> is the identifier assigned to the LSP group.

2 Add the IpFwdPolicy component

add Vr/<vrId> Mpls lspGroup/<lspg_name> IpFwd

where:



3 Define an ipv4Addr subcomponent of the IpFwd component to specify thecommon destination IP address of all LSPs in this group.

add Vr/<vrId> Mpls lspGroup/<lspg_name> IpFwdipv4Addr/<ipv4Element>,<ipv4Prefix>

where:



PPT 3019 007 AA

EM

VirtualRouter (Vr)

MultiprotocolLabelSwitching (Mpls)

IpFwdPolicy (IpFwd)

LspGroup (LspG)

Ipv4Addr (Ipv4)

CosMscMapping (MscMap)



<ipv4Element> is the IP address of the FEC for the LSP group.

<ipv4Prefix> is the length of the IP address specified in theipv4Element.

4 Add the MscMap component for class of service to MPLS servicecategory mapping.

add Vr/<vrId> Mpls LspGroup/<lspg_name> IpFwd MscMap

where:



5 Configure the bestMatchOverride attribute.

set Vr/<vrId> Mpls lspGroup/<lspg_name> ipv4Addr/<ipv4Element>, <ipv4Prefix> bestMatchOverride <mode>

where:



<ipv4Element> is the IP address of the FEC for the LSP group.


<mode> is enabled or disabled (the default).

6 Configure the class of service to MPLS service category mapping, ifdesired.

set Vr/<vrId> Mpls LspGroup/<lspG_name> IpFwd MscMap<value_COS> <value_MSC>

where:



<value_COS> is an IP class of service category and <value_MSC> isthe MPLS service category to which you would like the class of service tomap.


241-5701-445 2.2S1

Configuring the explicit route pathTo configure the explicit route path, you must define the hops that form a path.The figure “Component tree for configuring the explicit route path” (page 60)shows the components and attributes configured in this procedure.

Figure 19Component tree for configuring the explicit route path

1 Add a Path subcomponent as a subcomponent of the Mpls component.

add Vr/<vrId> Mpls Path/<path>

where:


<path> is the identifier assigned to this path.

2 Add a Hop subcomponent to the Path component.

add Vr/<vrId> Mpls Path/<path> Hop/<hop>

where:



<hop> is the identifier assigned to this hop.

3 Set the Hop component parameters.

PPT 3019 008 AA

EM

VirtualRouter (Vr)


Hop ipv4Addr (ipv4) ipv4PrefixLen hopMode (mode)

Path



set Vr/<vrId> Mpls Path/<path> Hop/<hop> ipv4Address<ipv4Element>, ipv4PrefixLen <ipv4Prefix>, hopMode<mode>

where:



<hop> is the identifier assigned to this hop.

<ipv4Element> is the IP address of the hop destination.


<mode> is strict (the default) to specify a strict hop (this is the next hop inthe path after the last hop specified) or loose to specify a loose hop (thishop may be more than one hop away from the last hop).

4 Repeat step 2 and step 3 for each hop in the path.

Configuring an ER-LSPMultiple ER-LSPs, under a common LSP group, can be configured to thesame destination IP address. The figure “Component tree for configuring anER-LSP” (page 62) shows the components and attributes configured in thisprocedure.


241-5701-445 2.2S1

Figure 20Component tree for configuring an ER-LSP

1 Add an Lsp component under the LspGroup component.

add Vr/<vrId> Mpls LspGroup/lspG_name> Lsp/<lspId>

where:



<lspId> is the identifier assigned to the LSP.

2 Add the TrafficEngineering subcomponent under the Lsp component.

add Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId> Te

where:




3 Add the MplsServiceCategory subcomponent under the Lsp component.

PPT 3019 009 AA

EM

VirtualRouter (Vr)


LabelSwitchedPath (Lsp)

TrafficEngineering (Te) pathName pathOnDemand isPinned

MplsServiceCategory (Msc) serviceCategory (sC) standbyLsp (sLsp)

LspGroup (LspG)

Path



add Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>Msc

where:




4 Set the LSP service category.

set Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>Msc serviceCategory/<category>

where:




<category> is a value from 0-7 to indicate a primary LSP, or standby toindicate that the LSP is acting as a standby LSP for a primary LSP.

5 Make the association between the path and the LSP, by setting thepathname attribute of the TrafficEngineering component.

set Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId> Tepathname <path>

where:




<path> is the full path to be used by the LSP.

6 Set the mode of the pathOnDemand attribute, to specify when the LSPwill be set up.

set Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId> TepathOnDemand/<mode>

where:




241-5701-445 2.2S1


<mode> is enabled to activate path on demand for the LSP in LDP to CR-LDP interworking, or disabled (the default) for non-interworking situations.

7 Set the standby LSPs of the primary or main LSP.

set Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>Msc standbyLsp <list>

where:




<list> is a list of the LSPs assigned as standby LSPs for this primary.

Configuring a hop-by-hop LSPTo support hop-by-hop LSPs, theLdpQos component must be configured.See “Configuring LSP quality of service” (page 64) for details on adding theLdpQos component. Note also that thepathName attribute of theTecomponent is not applicable. If this value is already set, thepathNameattribute is ignored. You may leave thepathNameattribute blank. For detailson setting the attribute, see “Configuring an ER-LSP” (page 61). There are noprovisioning changes for the cross connect map display. For details, see“Monitoring and troubleshooting” (page 71).

Configuring LSP quality of serviceUnder theLsp component are two subcomponents for setting the MPLSquality of service for an LSP. TheCrLdpQoscomponent represents the MPLSquality of service for an LSP using the CR-LDP signaling protocol. TheLdpQoscomponent represents the MPLS quality of service for an LSP usingthe LDP signaling protocol. Note that theLdpQos component and theCrLdpQos component are mutually exclusive: only one of the componentsmay be added under theLsp component. The figure “Component tree forconfiguring LSP quality of service” (page 65) shows the components andattributes that are configured in this procedure.



Figure 21Component tree for configuring LSP quality of service

1 For an LSP using the LDP signaling protocol, add the LdpQossubcomponent under the Lsp component.

add Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>LdpQos

where:




2 For an LSP using the CR-LDP signaling protocol, add the CrLdpQossubcomponent under the Lsp component.

add Vr/<vrId> Mpls Lspgroup/<lspg_name> Lsp/<lspId>CrLdpQos

where:



PPT 3019 010 AA

EM

VirtualRouter (Vr)



LdpQos (LdpQ)

CrLdpQos (CrQos) peakDataRate (pdr) committedDataRate (cdr) peakBurstSize (pbs) committedBurstSize (cbs)

LspGroup (LspG)


241-5701-445 2.2S1


3 Set the maximum rate at which traffic should be sent to the path.

set Vr/<vrId> Mpls Lspgroup/<lspg_name> Lsp/<lspId>CrLdpQos peakDataRate <rate>

where:




<rate> is a value which specifies the maximum rate for traffic to the path.

4 Set the committed data rate.

set Vr/<vrId> Mpls Lspgroup/<lspg_name> Lsp/<lspId>CrLdpQos committedDataRate <rate>

where:




<rate> is a value which specifies the committed data rate.

5 Set the maximum burst size.

set Vr/<vrId> Mpls Lspgroup/<lspg_name> Lsp/<lspId>CrLdpQos peakBurstSize <size>

where:




<size> is a value which specifies the maximum burst size.

6 Set the committed burst size.

set Vr/<vrId> Mpls Lspgroup/<lspg_name> Lsp/<lspId>CrLdpQos committedBurstSize <size>

where:






<size> is a value which specifies the committed burst size.

LDP/CR-LDP interworking configurationConfiguring LDP/CR-LDP interworking depends on which of the followingcases is in effect:

• LDP to CR-LDP to LDP

In this case, an LSP begins in the LDP domain, tunnels through the CR-LDP domain, and ends in another LDP domain. LDP messages aretranslated to CR-LDP and back again, as the LSP enters each domain. Toconfigure this case, you must

— set thepathOnDemand attribute of the ER-LSP at the first node inthe CR-LDP domain (this attribute causes MPLS to wait for an LDPrequest before setting up the LSP)

— configure the LDP interface on the last node in the CR-LDP domainas an interworking interface

• CR-LDP to LDP

In this case, the LSP begins in the CR-LDP domain and ends in the LDPdomain. To configure this case, you need to configure the LDP interfaceon the last node in the CR-LDP domain as an interworking interface.

• LDP to CR-LDP

In this case, the LSP begins in the LDP domain and terminates in the CR-LDP domain. To configure this case, you must configure thepathOnDemandattribute of the ER-LSP at the first node in the CR-LDPdomain.

See the following information to configure interworking:

• “Considerations for configuring LDP/CR-LDP interworking” (page 68)

• “Configuring LDP/CR-LDP interworking” (page 68)


241-5701-445 2.2S1

Considerations for configuring LDP/CR-LDP interworkingNote the following considerations for configuring interworking:

• Global repair is not supported when the CR-LDP LSPs are interworkingwith LDP.

• Hot stand-by paths are not supported when the CR-LDP LSPs areinterworking with LDP.

• Multiple ipv4 addresses in a hop-by-hop request message are notsupported.

• The last hop ipv4 address in the hop list corresponds to the ipv4 addressoutside the Passport domain. The egress LDP in the domain is configuredfor interworking.

Configuring LDP/CR-LDP interworkingThe figure “Component tree for configuring LDP/CR-LDP interworking”(page 69) shows the components and attributes that are configured in thisprocedure.



Figure 22Component tree for configuring LDP/CR-LDP interworking

Use the following procedure to configure LDP/CR-LDP interworking.

1 Configure the ER-LSP. (See “Configuring LSPs” (page 57) for details.)

2 At the first node in the CR-LDP domain, provision the pathOnDemandattribute of the ER-LSP.

set Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId> TepathOnDemand <mode>

where:


<lspId> is the identifier assigned to this LSP.

<mode> is enable to enable path-on-demand for the LSP, or disable (thedefault) to disable path-on-demand for the LSP in non-interworkingsituations.

3 At the last node in the CR-LDP domain, provision the LdpInterfacecomponent for interworking.

PPT 3019 011 AA

EM

VirtualRouter (Vr)


ProtocolPort (Pp)


TrafficEngineering (Te) pathOnDemand

LspGroup (LspG)

LabelDistributionProtocolIf (LdpIf) IdpInterworking (IdpInw)

MplsPort


241-5701-445 2.2S1

set Vr/<vrId> pp/<pp_id> mplsPort LdpIfldpInterworking <iw>

where:



<iw> is true to enable LDP/CR-LDP interworking for the interface, or false(the default) to disable LDP/CR-LDP interworking for the interface.

Locking and unlocking an LSPIf you wish to change the quality of service, path, hop, or FEC destination foran LSP, you must lock and then unlock the LSP for the changes to take effect.The following steps describe how to lock and unlock an LSP:

1 To lock an Lsp component instance:

lock Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>Te

where:




2 To unlock an Lsp component instance;

unlock Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>Te

where:




71


Chapter 4Monitoring and troubleshooting

For information on monitoring and troubleshooting MPLS, see the followingsections:

• “Tracing an LSP” (page 71)

• “Operational information on LSP groups and LSPs” (page 74)

• “Tracing the peers of a node” (page 77)

• “Troubleshooting” (page 79)

For general information about maintenance procedures, see 241-5701-600Passport 7400, 15000 Configuration Guide.

Tracing an LSPTo trace an LSP, you normally need to examine the operational attributes ofthe LSP segments and theXcMapcomponent at a number of Passport nodes.Figure “Tracing an LSP” (page 72) shows a simplified three node topologythat you can use as a reference.

To trace an LSP path across multiple nodes, use the following procedures:

• “Displaying the XcMap on the ingress node” (page 72)

• “Displaying the InSegment on the next node” (page 73)

• “Displaying the XcMap on the next node” (page 73)

• “Following the path” (page 74)

72 Chapter 4 Monitoring and troubleshooting

241-5701-445 2.2S1

Figure 23Tracing an LSP

Displaying the XcMap on the ingress nodeThe first step in tracing the LSP is to display theXcMapcomponent of yourstarting point, which is often the first node in the LSP. (In figure “Tracing anLSP” (page 72), the starting point is the ingress node.)

1 Determine the name of the XcMap component by displaying thecrossConnectMapName attribute for the LSP.

d Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>

where:




2 Display the XcMap component, using the identifier returned afterdisplaying the crossConnectMapName attribute.

d Vr/<vrId> Mpls XcMap/<crossConnectMapName>

where:


<crossConnectMapName> is the identifier assigned to the XcMapcomponent.

PPT 2888 012 AA

A BB

VCC label

Ingressnode

Starttracing Egress

nodeTandemnode

Chapter 4 Monitoring and troubleshooting 73


The system displays the operational attributes of the XcMap component.These attributes include the component names of the MplsPortInSegment and MplsPort OutSegment components of the LSP at thisnode. The InSegment component and OutSegment component identifiersare the VCC labels for those segments of the LSP. In the case of aningress node, there is no incoming segment, so only the OutSegmentcomponent data is displayed.

Displaying the InSegment on the next nodeAfter you have the name of theMplsPort OutSegment component on theingress node, you can display it as theInSegmentcomponent on the next nodein the LSP. In figure “Tracing an LSP” (page 72), the next node after theingress node is the tandem node.

1 Display the MplsPort InSegment component on the next node.

d Vr/<vrId> pp/<pp_id> mplsPort inSegment/<vcc_label>

where:

<vrId> is the name assigned to the VR.


<vcc_label> is the label, or VCC identifier, for the InSegment (which isthe OutSegment of the previous node).

Displaying the XcMap on the next nodeTo determine theOutSegment component identifier on the next node, youneed to display theXcMap component.

1 Display the XcMap component.

d Vr/<vrId> Mpls XcMap/<crossConnectMapName>

where:


<crossConnectMapName> is the identifier assigned to the XcMapcomponent.

The system displays the operational attributes of the XcMap component.These attributes include the component names of the MplsPortInSegment and mplsPort OutSegment components of the LSP at thisnode. If this were the last hop of the path, MplsPortOutSegmentcomponent would be blank.


241-5701-445 2.2S1

Following the pathWith the name of theMplsPort OutSegment from theXcMap component ofthe second node, you can display theMplsPort InSegmenton the next node inthe LSP. In figure “Tracing an LSP” (page 72), the next node is the egressnode. With longer LSPs, you can continue to follow the path by

• using the outgoing segment you know to find out the incoming segmentidentifier of the next node

• displaying theXcMap component of the next node to find out theidentifier of the outgoing segment

Operational information on LSP groups and LSPsTo discover operational information about the multiple LSPs under theLspGroup component, use the following procedures:

Note:These procedures are done in operational mode. For details onoperational mode, see 241-5701-275Passport 7400, 15000Commissioning Guide.

• “Displaying information on LSP groups” (page 74)

• “Displaying information on LSPs” (page 75)

Displaying information on LSP groups1 To view a list of all the LSP groups under the Mpls component:

list Vr/<vrId> Mpls LspGroup/*

where:


2 To view operational information on all LspGroup component instances:

display Vr/<vrId> Mpls LspGroup/*

where:


3 To view operational information for a given LspGroup componentinstance:

display Vr/<vrId> Mpls LspGroup/<lspg_name>



where:



4 To view a list of all the subcomponents of an LspGroup component:

list Vr/<vrId> Mpls LspGroup/<lspg_name>

where:



Displaying information on LSPs1 To view a list of all the LSPs under the Mpls component:

list Vr/<vrId> Mpls LspGroup/* Lsp/*

where:


2 To view operational information on all Lsp component instances:

display Vr/<vrId> Mpls LspGroup/* Lsp/*

where:


3 To view operational information for a given Lsp component instance:

display Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>

where:




4 To view a list of all the subcomponents of an Lsp component:

list -p Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId>

where:



241-5701-445 2.2S1



5 To view operational information on the MPLS service category for all Lspcomponent instances:

display Vr/<vrId> Mpls LspGroup/* Lsp/* Msc

where:


Provisioning the alarm severity for a specific LSPTo specify if a failed LSP should generate a major alarm, use the followingcommand:

set Vr/<vrId> MplsGroup/<lspg_name> Lsp/<lspId> TealarmControl major

where:




To specify if a failed LSP should generate a critical alarm, use the followingcommand:

set Vr/<vrId> MplsGroup/<lspg_name> Lsp/<lspId> TealarmControl critical

where:




To disable alarms on a specific LSP, use the following command:

set Vr/<vrId> Mpls LspGroup/<lspg_name> Lsp/<lspId> TealarmControl none

where:






Tracing the peers of a nodeTo trace the peers of a node, use the following procedures:

• “Displaying the Ldp component” (page 77)

• “Listing the peers of a node” (page 77)

• “Listing the sessions of a peer” (page 78)

• “Listing the adjacencies of a session” (page 78)

Displaying the Ldp componentTo determine if a Passport switch has an active peer, display the Ldpcomponent.

1 d -o vr/<vrId> Mpls Ldp

where:


The system displays the number of active peers and sessions, as well asthe total number of attempted sessions on the Vr.

Listing the peers of a nodeUse the following procedure to list the peers of a Passport node.

1 l -o Vr/ <vrId> Mpls Ldp /*

where:


The system lists all of the active peers, if any. Each peer instance is therouterId of the peer.

2 d -o Vr/<vrId> Mpls Ldp Peer/<peer>

where:


<peer> is the identifier assigned to the peer.


241-5701-445 2.2S1

The system display the hello mode, number of established sessions, andnumber of attempted sessions for the peer instance.

Listing the sessions of a peerUse the following procedure to list the sessions of a peer.

1 l -o Vr/<vrId> Mpls Ldp peer/<peer> session/*

where:



The system lists all of the sessions corresponding to that peer. A sessioninstance represents the local routerId and its corresponding port.

2 d -o Vr/<vrId> Mpls Ldp Peer/<peer> session/<session>

where:



<session> is the identifier assigned to the session.

The system displays the operational state of the session, remote LdpIf,transport Ipv4 address, the local LdpIf interface component name and theprotocol version. The session may have multiple adjacency instances.The remote LdpIf represents the adjacency instance that co-exists withthis session on the same connection.

Listing the adjacencies of a sessionUse the following procedure to list the adjacencies of a session and theircorresponding operational attribute.

1 l -o Vr/(vrId> Mpls Ldp Peer/<peer> session/<session> adj/*

where:




<adj> is the identifier assigned to the adjacency.



The system lists all the adjacencies corresponding to the session. Anadjacency instance is the corresponding port on the peer.

2 d -o Vr/<vrId> Mpls Ldp Peer/<peer> session/<session> adj/<adj>

where:




<adj> is the identifier assigned to the adjacency.

The system displays the name of its LdpIf component.

TroubleshootingTo solve problems that occur with MPLS, use the following sections:

• “Statistics” (page 79)

• “Solving problems” (page 80)

StatisticsTable “MPLS interface statistics” (page 79) lists the statistics reported by theMPLS interface.

Table 2MPLS interface statistics

Statistic Reported byMplsPort

Reported byInSegment

Reported byOutSegment

inLabelsUsed yes no no

inOctets no yes no

inPackets no no no

inDiscards no yes no

inErrors no yes no

failedLabelLookup no no no

outLabelsUsed yes no no

(Sheet 1 of 2)


241-5701-445 2.2S1

Solving problemsThe main source for troubleshooting information is the label switched path(LSP). If a label switched path (LSP) has come up successfully, theoperStatus attribute will indicate established. If an LSP has not beensuccessfully established, theoperStatus attribute will indicate idle.

outOctets no no yes

outPackets no no no

outDiscards no no yes

outErrors no no no

inUtil no no no

inTrafAboveMinorUtilAlarmThresh

no no no

inTrafAboveMajorUtilAlarmThresh

no no no

inTrafAboveCritUtilAlarmThresh

no no no

outUtil no no no

outTrafAboveMinorUtilAlarmThresh

no no no

outTrafAboveMajorUtilAlarmThresh

no no no

outTrafAboveCritUtilAlarmThresh

no no no

Table 2 (continued)MPLS interface statistics

Statistic Reported byMplsPort

Reported byInSegment

Reported byOutSegment

(Sheet 2 of 2)



If the operStatusattribute indicates that the LSP is idle, the administrator canrefer to thelastTearDownReason attribute for information on why the LSPhas not been established. (Note that it is not possible to determine the node inquestion.)

2> d vr/0 mpls lspGroup/<lspg_name> lsp/<lspId>

Vr/0 Mpls LspG/179 Lsp/1adminState = unlocked

operationalState = enabled usageState = busy operStatus = established

direction = uniDirectionalOutcrossConnectMapName = Vr/0 Mpls XcMap/1140854775retryCount = 63pathFailureCount = 5lastTearDownReason = badLooseNodepathUpDateTime = 2001-02-08 11:03:24.33alarmControlOper = none

Table 3Troubleshooting the LSP

Tear Down Reason Trouble Shooting Solution

loopDetected The hop list for the ER contains a loop. Check hop lists forloops and correct

noRoute A remote peer is down and a route for the specifiedLSP cannot be established.

Check remote peersand determine whichone(s) are down.Remedy problem andreturn to service.

noLabelResources 1) The label resources for a specific peer do nothave any more labels available.2) The atmLabelMinIn and the atmLabelMaxInattributes are not a subset of the AtmIf CAattributes minAutoSelectedVciforVpiZero andmaxAutoSelectedVciforVpiZero.

Change the range oflabels or stop routingLSPs through thispeer.

badStrictNode A bad hop exists in the path for a specific strict ERLSP.

Check your hop listand remedy the badhop.

(Sheet 1 of 2)


241-5701-445 2.2S1

badLooseNode A bad hop exists in the path for a specific loose ERLSP

Check your hop listand remedy the badhop

sessRejNoHello A situation can arise when a session sends an initbefore the hello. This might happen betweendifferent versions of the software. Software thatconforms to the specification will not result in thisproblem being seen.

Check the version ofsoftware being usedand make sure it isthe latest version.

TrafficParaUnavailable

A label was not setup as a result of the trafficparameters not being available.

Provide a traffic TLVfor the ER-LSP.

labelRequestAbort A label request got aborted as a result ofconfiguration on the switch.

The problem shouldremedy itself oncethe configurationchanges have takeneffect. Check the LSPstatus to see if it getsestablished, or referto the last tear downreason again.

erLocked The LSP ER is locked. Unlock the ER LSP.

peerDown An egress peer on the Passport shelf is down. Check the passportand bring the Peerinto service.

Table 3 (continued)Troubleshooting the LSP

Tear Down Reason Trouble Shooting Solution

(Sheet 2 of 2)


Multiprotocol Label SwitchingGuide

Release 2.2

Copyright © 2001 Nortel Networks.All Rights Reserved.

NORTEL NETWORKS, the globemark design, the NORTELNETWORKS corporate logo, DPN, DPN-100, and PASSPORT aretrademarks of Nortel Networks.

Publication: 241-5701-445Document status: StandardDocument version: 2.2S1Document date: February 2001Printed in Canada

Documents

Passport 7400, 15000 Multiprotocol Label Switching€¦ · 5 Passport 7400, 15000 Multiprotocol Label Switching Guide 2.2S1 Publication history February 2001 2.2S1 Standard General