Download Print this page

Nokia 7210 SAS-K 2F4T6C series User Manual

7210 sas os service access switch mpls.
Hide thumbs

Advertisement

7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide7210 SAS M, T, X, R6, R12, Mxp,
Sx MPLS Configuration Guide
7210 SERVICE ACCESS SWITCH
7210 SAS OS 7210 SAS-K 2F4T6C MPLS
Guide
Release 9.0.R8
3HE12059AAAETQZZA
Issue: 01
September 2017
Nokia — Proprietary and confidential.
Use pursuant to applicable agreements.

Advertisement

   Also See for Nokia 7210 SAS-K 2F4T6C series

   Related Manuals for Nokia 7210 SAS-K 2F4T6C series

   Summary of Contents for Nokia 7210 SAS-K 2F4T6C series

  • Page 1

    7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide7210 SAS M, T, X, R6, R12, Mxp, Sx MPLS Configuration Guide 7210 SERVICE ACCESS SWITCH 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide Release 9.0.R8 3HE12059AAAETQZZA Issue: 01 September 2017 Nokia — Proprietary and confidential. Use pursuant to applicable agreements.

  • Page 2

    © 2017 Nokia. Contains proprietary/trade secret information which is the property of Nokia and must not be made available to, or copied or used by anyone outside Nokia without its written authorization. Not to be used or disclosed except in accordance with applicable agreements.

  • Page 3: Table Of Contents

    Nokia 7210 SAS-K 2F4T6C Router Configuration Process ........

  • Page 4

    Table of Contents Common Configuration Tasks ............49 Configuring MPLS Components .

  • Page 5

    Table of Contents Other Reasons for Label Actions ..........160 Cleanup .

  • Page 6

    Table of Contents Page 6 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 7

    IST OF ABLES Preface Table 1: Configuration Process ............15 MPLS and RSVP Table 2: Packet/Label Field Description .

  • Page 8

    List of Tables Page 8 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 9

    IST OF IGURES MPLS and RSVP Figure 1: Label Placement ............19 Figure 2: Label Packet Placement .

  • Page 10

    List of Figures Page 10 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 11: Preface

    Preface About This Guide This guide describes the services and protocol support provided by the 7210 SAS-K2F4T6C Series and presents examples to configure and implement MPLS, RSVP, and LDP protocols. This document is organized into functional chapters and provides concepts and descriptions of the implementation flow, as well as Command Line Interface (CLI) syntax and command usage.

  • Page 12: List Of Technical Publications

    Preface List of Technical Publications The 7210- D, 7210 SAS-E, 7210 SAS-K 2F2T1C and 7210 SAS-K 2F4T6C documentation set is composed of the following books: • 7210- D, 7210 SAS-E, 7210 SAS-K 2F2T1C and 7210 SAS-K 2F4T6C Basic System Configuration Guide This guide describes basic system configurations and operations.

  • Page 13: Getting Started

    TARTED In This Chapter This chapter provides process flow information to configure MPLS, RSVP, and LDP protocols. Nokia 7210 SAS-K 2F4T6C Router Configuration Process Table 1 lists the tasks necessary to configure MPLS applications functions. This guide is presented in an overall logical configuration flow. Each section describes a software area and provides CLI syntax and command usage to configure parameters for a functional area.

  • Page 14

    Getting Started Page 16 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 15: Mpls And Rsvp

    MPLS and RSVP In This Chapter This chapter provides information to configure MPLS and RSVP. • MPLS on page 18 → MPLS Label Stack on page 18 → Label Switching Routers on page 21 → Using RSVP for MPLS on page 29 →...

  • Page 16: Mpls

    MPLS Label Stack MPLS Multiprotocol Label Switching (MPLS) is a label switching technology that provides the ability to set up connection-oriented paths over a connection less IP network. MPLS facilitates network traffic flow and provides a mechanism to engineer network traffic patterns independently from routing tables.

  • Page 17: Figure 1: Label Placement

    MPLS and RSVP Figure 1: Label Placement Table 2: Packet/Label Field Description Field Description Label This 20-bit field carries the actual value (unstructured) of the label. This 3-bit field is reserved for experimental use. It is currently used for Class of Service (CoS).

  • Page 18: Label Values

    MPLS Label Stack Labeled packet processing is independent of the level of hierarchy. Processing is always based on the top label in the stack which includes information about the operations to perform on the packet's label stack. Label Values Packets travelling along an LSP (see Label Switching Routers on page 21) are identified by its label, the 20-bit, unsigned integer.

  • Page 19: Label Switching Routers

    MPLS and RSVP Label Switching Routers LSRs perform the label switching function. LSRs perform different functions based on it’s position in an LSP. Routers in an LSP do one of the following: • The router at the beginning of an LSP is the ingress label edge router (ILER). The ingress router can encapsulate packets with an MPLS header and forward it to the next router along the path.

  • Page 20

    Label Switching Routers previous hop router to this router (strict) or can traverse through other routers (loose). You can control how the path is set up. They are similar to static LSPs but require less configuration. See RSVP on page →...

  • Page 21: Mpls Facility Bypass Method Of Mpls Fast Re-route (frr)

    MPLS and RSVP MPLS Facility Bypass Method of MPLS Fast Re-Route (FRR) The MPLS facility bypass method of MPLS Fast Re-Route (FRR) functionality is extended to the ingress node. The behavior of an LSP at an ingress LER with both fast reroute and a standby LSP path configured is as follows: •...

  • Page 22: Figure 3: Bypass Tunnel Nodes

    Label Switching Routers PLR Bypass LSP Selection Rules Figure 3: Bypass Tunnel Nodes The PLR uses the following rules to select a bypass LSP among multiple manual and dynamic bypass LSP’s at the time of establishment of the primary LSP path or when searching for a bypass for a protected LSP which does not have an association with a bypass tunnel: 1.

  • Page 23

    MPLS and RSVP 7. If the PLR node successfully makes an association, it must set the “local protection available” flag in the IPv4 address sub-object of the RRO starting in the next RESV refresh message it sends upstream. 8. For all primary LSP that requested FRR protection but are not currently associated with a bypass tunnel, the PLR node on reception of RESV refresh on the primary LSP path repeats Steps 1-7.

  • Page 24: Figure 4: Frr Node-protection Example

    Label Switching Routers FRR Node-Protection (Facility) The MPLS Fast Re-Route (FRR) functionality enables PLRs to be aware of the missing node protection and lets them regularly probe for a node-bypass. The following describes an LSP scenario: PE_1 PE_2 PE_3 PE_4 Figure 4: FRR Node-Protection Example Where: •...

  • Page 25

    MPLS and RSVP The switchover time is measured from the time the control plane detected the failure of the interface or neighbor/next-hop to the time the IOM completed the reprogramming of all the impacted ILM or service records in the data path. This includes the time it takes for the control plane to send a down notification to all IOMs to request a switch to the backup NHLFE.

  • Page 26: Rsvp

    Label Switching Routers RSVP The Resource Reservation Protocol (RSVP) is a network control protocol used by a host to request specific qualities of service from the network for particular application data streams or flows. RSVP is also used by routers to deliver quality of service (QoS) requests to all nodes along the path(s) of the flows and to establish and maintain state to provide the requested service.

  • Page 27: Using Rsvp For Mpls

    MPLS and RSVP PATH:30.30.30.1 PATH:30.30.30.1 PATH:30.30.30.1 10.10.10.1 30.30.30.1 RESV:10.10.10.1 RESV:10.10.10.1 RESV:10.10.10.1 RESV:10.10.10.1 label label label label 100|push 100|200|swap 200|300|swap 300|pop 10.10.10.1 30.30.30.1 OSSG016 Figure 6: LSP Using RSVP Path Set Up Figure 6 displays an example of an LSP path set up using RSVP. The ingress label edge router (ILER 1) transmits an RSVP path message (path: 30.30.30.1) downstream to the egress label edge router (ELER 4).

  • Page 28: Rsvp Traffic Engineering Extensions For Mpls

    Using RSVP for MPLS packets that are assigned the same label value by a specific node are considered to belong to the same FEC which defines the RSVP flow. For use with MPLS, RSVP already has the resource reservation component built-in which makes it ideal to reserve resources for LSPs.

  • Page 29: Reservation Styles

    MPLS and RSVP • Lifetime of the key. A key is user-generated key using a third party software/hardware and enters the value as static string into CLI configuration of the RSVP interface. The key will continue to be valid until it is removed from that RSVP interface. •...

  • Page 30: Rsvp Overhead Refresh Reduction

    RSVP Overhead Refresh Reduction RSVP Overhead Refresh Reduction The RSVP refresh reduction feature consists of the following capabilities implemented in accordance to RFC 2961, RSVP Refresh Overhead Reduction Extensions: • RSVP message bundling — This capability is intended to reduce overall message handling load.

  • Page 31

    MPLS and RSVP All LSPs for which this node is the egress LER and for which the path message is received from the previous hop node over this RSVP interface will signal the implicit null label. This means that if the egress LER is also the merge-point (MP) node, then the incoming interface for the path refresh message over the bypass dictates if the packet will use the implicit null label or not.

  • Page 32: Mpls Traffic Engineering

    TE Metric (IS-IS and OSPF) MPLS Traffic Engineering Without traffic engineering, routers route traffic according to the SPF algorithm, disregarding congestion or packet types. With traffic engineering, network traffic is routed efficiently to maximize throughput and minimize delay. Traffic engineering facilitates traffic flows to be mapped to the destination through a different (less congested) path other than the one selected by the SPF algorithm.

  • Page 33

    MPLS and RSVP shortest path among the all SPF paths will be selected based on the TE metric instead of the IGP metric used by default. The TE metric is only used in CSPF computations for MPLS paths and not in the regular SPF computation for IP reachability.

  • Page 34: Advanced Mpls/rsvp Features

    LSP Path Change Advanced MPLS/RSVP Features • LSP Path Change on page 36 • Manual LSP Path Switch on page 37 • Shared Risk Link Groups on page 37 • TE Graceful Shutdown on page 41 LSP Path Change The tools perform router mpls update-path {lsp lsp-name path current-pathname new-path new-path-name} command instructs MPLS to replace the path of the primary or second- ary LSP.

  • Page 35: Manual Lsp Path Switch

    MPLS and RSVP Manual LSP Path Switch This feature provides a new command to move the path of an LSP from a standby secondary to an- other standby secondary. The base version of the command allows the path of the LSP to move from a standby (or an active secondary) to another standby of the same priority.

  • Page 36: Enabling Disjoint Backup Paths

    Shared Risk Link Groups and up since the head-end LER needs the most current ERO computed by CSPF for the primary path. CSPF would return the list of SRLG groups along with the ERO during primary path CSPF computation. At a subsequent establishment of a secondary path with the SRLG constraint, the MPLS/RSVP task will query again CSPF providing the list of SLRG group numbers to be avoided.

  • Page 37: Figure 7: Shared Risk Link Groups

    MPLS and RSVP → Configure primary FRR (one-to-one/facility) LSP path(s). Consider that each PLR will create a detour/bypass that will only avoid the SRLG membership(s) configured on the primary LSP path egress interface. In a one-to-one case, detour-detour merging is out of the control of the PLR, thus the latter will not ensure that its detour will be prohibited to merge with a colliding one.

  • Page 38: Static Configurations Of Srlg Memberships

    Shared Risk Link Groups This feature is supported on OSPF and IS-IS interfaces on which RSVP is enabled. Static Configurations of SRLG Memberships This feature provides operations with the ability to enter manually the link members of SRLG groups for the entire network at any 7210 SAS node which will need to signal LSP paths (for example, a head-end node).

  • Page 39: Te Graceful Shutdown

    MPLS and RSVP CSPF will not use entered SRLG membership if an interface is not listed as part of a router ID in the TE database. If an interface was not entered into the user SRLG database, it will be assumed that it does not have any SRLG membership.

  • Page 40: Mpls/rsvp Configuration Process Overview

    TE Graceful Shutdown MPLS/RSVP Configuration Process Overview Figure 8 displays the process to configure MPLS and RSVP parameters. START ENABLE MPLS CONFIGURE MPLS INTERFACE PARAMETERS CONFIGURE RSVP INTERFACE PARAMETERS CONFIGURE PATH PARAMETERS CONFIGURE LSP PARAMETERS CONFIGURE LSP-PATH PARAMETERS Figure 8: MPLS and RSVP Configuration and Implementation Flow Page 42 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 41: Configuration Notes

    MPLS and RSVP Configuration Notes This section describes MPLS and RSVP caveats. • Interfaces must already be configured in the config>router>interface context before they can be specified in MPLS and RSVP. • A router interface must be specified in the config>router>mpls context in order to apply it or modify parameters in the config>router>rsvp context.

  • Page 42

    TE Graceful Shutdown Page 44 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 43: Configuring Mpls And Rsvp With Cli

    MPLS and RSVP Configuring MPLS and RSVP with CLI This section provides information to configure MPLS and RSVP using the command line interface. Topics in this section include: • MPLS Configuration Overview on page 46 → LSPs on page 46 →...

  • Page 44: Mpls Configuration Overview

    LSPs MPLS Configuration Overview Multi protocol Label Switching (MPLS) enables routers to forward traffic based on a simple label embedded into the packet header. A router examines the label to determine the next hop for the packet, saving time for router address lookups to the next node when forwarding packets.

  • Page 45: Router Interface

    MPLS and RSVP Router Interface At least one router interface and one system interface must be defined in the config>router>interface context in order to configure MPLS on an interface. Choosing the Signaling Protocol If only static label switched paths are used in your configurations, then you must manually define the paths through the MPLS network.

  • Page 46: Basic Mpls Configuration

    Choosing the Signaling Protocol Basic MPLS Configuration This section provides information to configure MPLS and configuration examples of common configuration tasks. To enable MPLS on routers, you must configure at least one MPLS interface. The other MPLS configuration parameters are optional. This follow displays an example of an MPLS configuration.

  • Page 47: Common Configuration Tasks

    MPLS and RSVP Common Configuration Tasks This section provides a brief overview of the tasks to configure MPLS and provides the CLI commands. The following protocols must be enabled on each participating router. • MPLS • RSVP (for RSVP-signaled MPLS only) •...

  • Page 48: Configuring Mpls Components

    Configuring MPLS Components Configuring MPLS Components Use the MPLS and RSVP CLI syntax displayed below for: • Configuring Global MPLS Parameters on page 50 • Configuring an MPLS Interface on page 51 • Configuring MPLS Paths on page 52 • Configuring an MPLS LSP on page 53 •...

  • Page 49: Configuring An Mpls Interface

    MPLS and RSVP Configuring an MPLS Interface Configure the label-map parameters if the interface is used in a static LSP. To configure an MPLS interface on a router, enter the following commands: CLI Syntax: config>router>mpls interface no shutdown admin-group group-name [group-name...(up to 32 max)] label-map swap no shutdown...

  • Page 50: Configuring Mpls Paths

    Configuring MPLS Paths Configuring MPLS Paths Configure an LSP path to use in MPLS. When configuring an LSP, the IP address of the hops that the LSP should traverse on its way to the egress router must be specified. The intermediate hops must be configured as either strict or loose meaning that the LSP must take either a direct path from the previous hop router to this router (strict) or can traverse through other routers (loose).

  • Page 51: Configuring An Mpls Lsp

    MPLS and RSVP Configuring an MPLS LSP Configure an LSP path for MPLS. When configuring an LSP, you must specify the IP address of the egress router in the to statement. Specify the primary path to be used. Secondary paths can be explicitly configured or signaled upon the failure of the primary path.

  • Page 52: Configuring A Static Lsp

    Configuring an MPLS LSP Configuring a Static LSP An LSP can be explicitly (statically) configured. Static LSPs are configured on every node along the path. The label’s forwarding information includes the address of the next hop router. Use the following CLI syntax to configure a static LSP: CLI Syntax: config>router>mpls static-lsp lsp-name to ip-address...

  • Page 53: Configuring Manual Bypass Tunnels

    MPLS and RSVP Configuring Manual Bypass Tunnels Consider the following network setup. A----B----C----D E----F The user first configures the option to disable the dynamic bypass tunnels. Listed below are the steps to configure the manual bypass tunnels: 1. Configure the option to disable the dynamic bypass tunnels on the 7210 SAS node B (if required).

  • Page 54

    Configuring Manual Bypass Tunnels A:7210 SAS>config>router>mpls>path# info ------------------------------------------- path "BEFC" hop 10 10.10.10.11 strict hop 20 10.10.10.12 strict hop 30 10.10.10.13 strict no shutdown exit lsp "bypass-BC" to 10.10.10.15 primary "BEFC" exit no shutdown ------------------------------------------- A:7210 SAS >config>router>mpls>path# 3. Configure an LSP from A to D and indicate fast-reroute bypass protection, select the facility as “FRR method”.

  • Page 55: Configuring Rsvp Parameters

    MPLS and RSVP Configuring RSVP Parameters RSVP is used to set up LSPs. RSVP must be enabled on the router interfaces that are participating in signaled LSPs. The keep-multiplier and refresh-time default values can be modified in the RSVP context. Initially, interfaces are configured in the config>router>mpls>interface context.

  • Page 56: Configuring Rsvp Message Pacing Parameters

    Configuring RSVP Message Pacing Parameters Configuring RSVP Message Pacing Parameters RSVP message pacing maintains a count of the messages that were dropped because the output queue for the egress interface was full. Use the following CLI syntax to configure RSVP parameters: CLI Syntax: config>router>rsvp no shutdown msg-pacing...

  • Page 57: Configuring Graceful Shutdown

    MPLS and RSVP Configuring Graceful Shutdown Enable TE graceful shutdown on the maintenance interface using the config>router>rsvp>interface>graceful-shutdown command. Disable graceful shutdown by executing the no form of the command at the RSVP interface level or at the RSVP level. This restores the user-configured TE parameters of the maintenance links, and the 7210 SAS maintenance node floods them.

  • Page 58: Mpls Configuration Management Tasks

    Modifying MPLS Parameters MPLS Configuration Management Tasks This section discusses the following MPLS configuration management tasks: • Modifying MPLS Parameters on page 60 • Modifying MPLS Path Parameters on page 62 • Modifying MPLS Static LSP Parameters on page 63 •...

  • Page 59: Modifying An Mpls Lsp

    MPLS and RSVP Modifying an MPLS LSP Some MPLS LSP parameters such as primary and secondary, must be shut down before they can be edited or deleted from the configuration. The following displays a MPLS LSP configuration example. Refer to the LSP configuration page A:ALA-1>>config>router>mpls>lsp# info ----------------------------------------------...

  • Page 60: Modifying Mpls Path Parameters

    Modifying MPLS Path Parameters Modifying MPLS Path Parameters In order to modify path parameters, the config>router>mpls>path context must be shut down first. The following displays a path configuration example. Refer to the LSP configuration on page A:ALA-1>config>router>mpls# info #------------------------------------------ echo "MPLS" #------------------------------------------ path "secondary-path"...

  • Page 61: Modifying Mpls Static Lsp Parameters

    MPLS and RSVP Modifying MPLS Static LSP Parameters In order to modify static LSP parameters, the config>router>mpls>path context must be shut down first. The following displays a static LSP configuration example. Refer to the static LSP configuration on page A:ALA-1>config>router>mpls# info ---------------------------------------------- static-lsp "static-LSP"...

  • Page 62: Deleting An Mpls Interface

    Deleting an MPLS Interface Deleting an MPLS Interface In order to delete an interface from the MPLS configuration, the interface must be shut down first. Use the following CLI syntax to delete an interface from the MPLS configuration: CLI Syntax: mpls [no] interface ip-int-name shutdown A:ALA-1>config>router>mpls# info...

  • Page 63: Rsvp Configuration Management Tasks

    MPLS and RSVP RSVP Configuration Management Tasks This section discusses the following RSVP configuration management tasks: • Modifying RSVP Parameters on page 65 • Modifying RSVP Message Pacing Parameters on page 66 • Deleting an Interface from RSVP on page 66 Modifying RSVP Parameters Only interfaces configured in the MPLS context can be modified in the RSVP context.

  • Page 64: Modifying Rsvp Message Pacing Parameters

    Modifying RSVP Message Pacing Parameters Modifying RSVP Message Pacing Parameters RSVP message pacing maintains a count of the messages that were dropped because the output queue for the egress interface was full. The following example displays command usage to modify RSVP parameters: The following example displays a modified RSVP message pacing configuration example.

  • Page 65: Mpls/rsvp Command Reference

    MPLS and RSVP MPLS/RSVP Command Reference Command Hierarchies • MPLS Commands on page 67 • MPLS Path Commands on page 70 • RSVP Commands on page 70 • Show Commands on page 71 • Clear Commands on page 72 • Debug Commands on page 73 MPLS Commands config —...

  • Page 66: Mpls Lsp Commands

    Command Hierarchies — [no] static-lsp lsp-name — no push label — push label nexthop ip-address — [no] shutdown — ip-address — [no] static-lsp-fast-retry seconds — user-srlg-db [enable | disable] MPLS LSP Commands config — router — [no] mpls — [no] lsp-name [bypass-only —...

  • Page 67

    MPLS and RSVP — no hop-limit — [no] include group-name [group-name...(up to 5 max)] — [no] path-preference — [no] record — [no] record-label — [no] shutdown — [no] srlg — [no] standby — [no] shutdown — ip-address 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide Page 69...

  • Page 68: Mpls Path Commands

    Command Hierarchies MPLS Path Commands config — router — [no] mpls — [no] p2p-active-path-fast-retry — [no] path path-name — hop-index ip-address {strict | loose} — no hop-index — [no] shutdown — [no] static-lsp lsp-name — push label nexthop ip-address — no push out-label —...

  • Page 69: Show Commands

    MPLS and RSVP Show Commands show — router — mpls — bypass-tunnel [to ip-address] [protected-lsp name] [dynamic | manual] [detail] — interface [ip-int-name|ip-address] [label-map label] — interface [ip-int-name|ip-address] — label start-label [end-label | in-use | label-owner] — label-range — [lsp-name] [status {up|down}] [from ip-address| to ip-address] [detail] —...

  • Page 70: Tools Commands

    Command Hierarchies Tools Commands — perform — router — mpls — cspf to ip-addr [from ip-addr] [bandwidth bandwidth] [include-bitmap bitmap] [exclude-bitmap bitmap] [hop-limit limit] [exclude-address excl-addr [excl-addr...(upto 8 max)]] [use-te-metric] [strict-srlg] [srlg- group grp-id...(up to 8 max)] [skip-interface interface-name] — force-switch-path [lsp lsp-name] [path path-name] —...

  • Page 71: Debug Commands

    MPLS and RSVP Debug Commands debug — router — mpls [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel- id] [lsp-id lsp-id] — no mpls — [no] event — [detail] — no — [detail] — no — [detail] — no — lsp-setup [detail] —...

  • Page 72

    Command Hierarchies — no resv — resverr [detail] — no resverr — resvtear [detail] — no resvtear — srefresh [detail] — no srefresh Page 74 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 73

    MPLS and RSVP MPLS Configuration Commands Generic Commands shutdown Syntax [no] shutdown Context config>router>mpls config>router>mpls>interface config>router>mpls>lsp>primary config>router>mpls>lsp>secondary Description This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. MPLS is not enabled by default and must be explicitely enabled (no shutdown). The operational state of the entity is disabled as well as the operational state of any entities contained within.

  • Page 74

    MPLS Commands MPLS Commands mpls Syntax [no] mpls Context config>router Description This command enables the context to configure MPLS parameters. MPLS is not enabled by default and must be explicitely enabled (no shutdown). The shutdown command administratively disables MPLS. The no form of this command deletes this MPLS protocol instance; this will remove all configuration parameters for this MPLS instance.

  • Page 75

    MPLS and RSVP hold-timer Syntax hold-timer seconds no hold-timer Context config>router>mpls Description This command specifies the amount of time that the ingress node holds before programming its data plane and declaring the LSP up to the service module. The no form of the command disables the hold-timer. Default 1 second Parameters...

  • Page 76

    MPLS Commands When this option is enabled, CSPF includes the SRLG constraint in the computation of a FRR detour or bypass for protecting the primary LSP path. CSPF prunes all links with interfaces which belong to the same SRLG as the interface which is being protected, i.e., the outgoing interface at the PLR the primary path is using.

  • Page 77

    MPLS and RSVP user-srlg-db Syntax user-srlg-db [enable | disable] Context config>router>mpls Description This command enables the use of CSPF by the user SRLG database. When the MPLS module makes a request to CSPF for the computation of an SRLG secondary path, CSPF will query the local SRLG and compute a path after pruning links that are members of the SRLG IDs of the associated primary path.

  • Page 78

    MPLS Commands Parameters ip-address — Specifies the router ID for this system. This must be the router ID configured under the base router instance, the base OSPF instance or the base IS-IS instance. Values [a.b.c.d] interface Syntax interface ip-address srlg-group group-name [group-name...(up to 5 max)] no interface ip-address [srlg-group group-name...(up to 5 max)] Context config>router>mpls>srlg-database>router-id...

  • Page 79

    MPLS and RSVP Syntax [no] pop Context config>router>mpls>if>label-map Description This command specifies that the incoming label must be popped (removed). No label stacking is supported for a static LSP. The service header follows the top label. Once the label is popped, the packet is forwarded based on the service header.

  • Page 80

    MPLS Commands swap Syntax swap {out-label | implicit-null-label} nexthop ip-address no swap {out-label | implicit-null-label} Context config>router>mpls>interface>label-map Description This command swaps the incoming label and specifies the outgoing label and next hop IP address on an LSR for a static LSP. The no form of this command removes the swap action associated with the in-label.

  • Page 81

    MPLS and RSVP push Syntax no push label push label nexthop ip-address Context config>router>mpls>static-lsp Description This command specifies the label to be pushed on the label stack and the next hop IP address for the static LSP. The no form of this command removes the association of the label to push for the static LSP. Parameters label —...

  • Page 82

    MPLS Commands Syntax to ip-address Context config>router>mpls>static-lsp Description This command specifies the system IP address of the egress router for the static LSP. This command is required while creating an LSP. For LSPs that are used as transport tunnels for services, the to IP address must be the system IP address.

  • Page 83

    MPLS and RSVP MPLS Interface Commands interface Syntax [no] interface ip-int-name Context config>router>mpls Description This command specifies MPLS protocol support on an IP interface. No MPLS commands are executed on an IP interface where MPLS is not enabled. An MPLS interface must be explicitly enabled (no shutdown).

  • Page 84

    MPLS Commands srlg-group Syntax [no] srlg-group group-name [group-name...(up to 5 max)] Context config>router>mpls>interface Description This command defines the association of RSVP interface to an SRLG group. An interface can belong to up to 64 SRLG groups. However, each single operation of the srlg-group command allows a maximum of 5 groups to be specified at a time.

  • Page 85

    MPLS and RSVP LSP Commands Syntax [no] lsp lsp-name [bypass-only] Context config>router>mpls Description This command creates an LSP that is signaled dynamically by the . When the LSP is created, the egress router must be specified using the to command and at least one primary or secondary path must be specified.

  • Page 86

    MPLS Commands adspec Syntax [no] adspec Context config>router>mpls>lsp Description When enabled, the ADSPEC object will be included in RSVP messages for this LSP. The ADSPEC object is used by the ingress LER to discover the minimum value of the MTU for links in the path of the LSP.

  • Page 87

    MPLS and RSVP Default no cspf Parameters use-te-metric — Specifies to use the use of the TE metric for the purpose of the LSP path computation by CSPF. exclude Syntax [no] exclude group-name [group-name...(up to 5 max)] Context config>router>mpls>lsp Description This command specifies the admin groups to be excluded when an LSP is set up in the primary or secondary contexts.

  • Page 88

    MPLS Commands The no form of the fast-reroute command removes the detour LSP from each node on the primary path. This command will also remove configuration information about the hop-limit and the bandwidth for the detour routes. The no form of fast-reroute hop-limit command reverts to the default value. Default no fast-reroute —...

  • Page 89

    MPLS and RSVP node-protect Syntax [no] node-protect Context config>router>mpls>lsp>fast-reroute Description This command enables or disables node and link protection on the specified LSP. Node protection ensures that traffic from an LSP traversing a neighboring router will reach its destination even if the neighboring router fails.

  • Page 90

    MPLS Commands the new value is equal to or greater than the current number hops of the established LSP, then the LSP is not affected. The no form of this command returns the parameter to the default value. Default Parameters number —...

  • Page 91

    MPLS and RSVP Syntax to ip-address Context config>router>mpls>lsp Description This command specifies the system IP address of the egress router for the LSP. This command is mandatory to create an LSP. An IP address for which a route does not exist is allowed in the configuration. If the LSP signaling fails because the destination is not reachable, an error is logged and the LSP operational status is set to down.

  • Page 92

    MPLS Commands Parameters seconds — The amount of time, in seconds, between attempts to re-establish the LSP after it has failed. Allowed values are integers in the range of 1 to 600. Values 1 — 600 rsvp-resv-style Syntax rsvp-resv-style [se | ff] Context config>router>mpls>lsp Description...

  • Page 93

    MPLS and RSVP 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide Page 95...

  • Page 94

    MPLS Commands Primary and Secondary Path Commands primary Syntax primary path-name no primary Context config>router>mpls>lsp Description This command specifies a preferred path for the LSP. This command is optional only if the secondary path-name is included in the LSP definition. Only one primary path can be defined for an LSP.

  • Page 95

    MPLS and RSVP order to delete it. The no secondary path-name command will not result in any action except a warning message on the console indicating that the secondary path is administratively up. Default none Parameters path-name — The case-sensitive alphanumeric name label for the LSP path up to 32 characters in length.

  • Page 96

    MPLS Commands Use the no form of the command to remove the exclude command. Default no exclude Parameters group-name — Specifies the existing group-name to be excluded when an LSP is set up. hop-limit Syntax hop-limit number no hop-limit Context config>router>mpls>lsp>primary config>router>mpls>lsp>secondary Description...

  • Page 97

    MPLS and RSVP record Syntax [no] record Context config>router>mpls>lsp>primary config>router>mpls>lsp>secondary Description This command enables recording of all the hops that an LSP path traverses. Enabling record increases the size of the PATH and RESV refresh messages for the LSP since this information is carried end-to-end along the path of the LSP.

  • Page 98

    MPLS Commands If CSPF is not enabled on the LSP name, then a secondary path of that LSP which has the SRLG constraint included will be shut down and a specific failure code will indicate the exact reason for the failure in show>router>mpls>lsp>path>detail output.

  • Page 99

    MPLS and RSVP Default no srlg standby Syntax [no] standby Context config>router>mpls>lsp>secondary Description The secondary path LSP is normally signaled once the primary path LSP fails. The standby keyword ensures that the secondary path LSP is signaled and maintained indefinitely in a hot-standby state. When the primary path is re-established then the traffic is switched back to the primary path LSP.

  • Page 100

    MPLS Commands Page 102 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 101

    MPLS and RSVP LSP Path Commands Syntax hop hop-index ip-address {strict | loose} no hop hop-index Context config>router>mpls>path Description This command specifies the IP address of the hops that the LSP should traverse on its way to the egress router. The IP address can be the interface IP address or the system IP address. If the system IP address is specified then the LSP can choose the best available interface.

  • Page 102

    MPLS Commands p2p-active-path-fast-retry Syntax p2p-active-path-fast-retry seconds no p2p-active-path-fast-retry Context config>router>mpls Description This command configures a global parameter to allow the user to apply a shorter retry timer for the first try after an active LSP path went down due to a local failure or the receipt of a RESVTear. This timer is used only in the first try.

  • Page 103

    MPLS and RSVP shutdown Syntax [no] shutdown Context config>router>mpls>path Description This command disables the existing LSPs using this path. All services using these LSPs are affected. Binding information, however, is retained in those LSPs. Paths are created in the shutdown state. The no form of this command administratively enables the path.

  • Page 104

    MPLS Commands Page 106 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 105

    MPLS and RSVP Static LSP Commands static-lsp Syntax [no] static-lsp lsp-name Context config>router>mpls Description This command is used to configure a static LSP on the ingress router. The static LSP is a manually set up LSP where the nexthop IP address and the outgoing label (push) must be specified. The no form of this command deletes this static LSP and associated information.

  • Page 106

    MPLS Commands shutdown Syntax [no] shutdown Context config>router>mpls>static-lsp Description This command is used to administratively disable the static LSP. The no form of this command administratively enables the static LSP. Default shutdown Syntax to ip-address Context config>router>mpls>static-lsp Description This command specifies the system IP address of the egress router for the static LSP. When creating an LSP this command is required.

  • Page 107

    MPLS and RSVP RSVP Configuration Commands Generic Commands shutdown Syntax [no] shutdown Context config>router>rsvp config>router>rsvp>interface Description This command disables the RSVP protocol instance or the RSVP-related functions for the interface. The RSVP configuration information associated with this interface is retained. When RSVP is administratively disabled, all the RSVP sessions are torn down.

  • Page 108

    RSVP Commands RSVP Commands rsvp Syntax [no] rsvp Context config>router Description This command enables the context to configure RSVP protocol parameters. RSVP is not enabled by default and must be explicitely enabled (no shutdown). RSVP is used to set up LSPs. RSVP should be enabled on all router interfaces that participate in signaled LSPs.

  • Page 109

    MPLS and RSVP separate RSVP neighbor. The user will have to enable BFD on each interface and RSVP will register with the BFD session running with each of those neighbors independently Similarly the disabling of BFD on the interface results in removing registration of the interface with BFD.

  • Page 110

    RSVP Commands c. A CSPF LSP with the adaptive option disabled and which current path is over the listed maintenance interfaces in the PathErr message. These are not subject to make-before-break. d. A non CSPF LSP which current path is over the listed maintenance interfaces in the PathErr message.

  • Page 111

    MPLS and RSVP rapid-retransmit-time Syntax rapid-retransmit-time hundred-milliseconds no rapid-retransmit-time Context config>router>rsvp Description This command defines the value of the Rapid Retransmission Interval. It is used in the re- transmission mechanism to handle unacknowledged message_id objects and is based on an exponential back-off timer.

  • Page 112

    RSVP Commands refresh-time Syntax refresh-time seconds no refresh-time Context config>router>rsvp Description The refresh-time controls the interval, in seconds, between the successive Path and Resv refresh messages. RSVP declares the session down after it misses keep-multiplier number consecutive refresh messages. The no form of this command reverts to the default value. Default 30 seconds Parameters...

  • Page 113: Interface Commands

    MPLS and RSVP Interface Commands interface Syntax [no] interface ip-int-name Context config>router>rsvp Description This command enables RSVP protocol support on an IP interface. No RSVP commands are executed on an IP interface where RSVP is not enabled. The no form of this command deletes all RSVP commands such as hello-interval and subscription, which are defined for the interface.

  • Page 114

    Interface Commands sender complies to the procedures for RSVP message generation in RFC 2747, RSVP Cryptographic Authentication. A RSVP receiver uses the key together with the authentication algorithm to process received RSVP messages. The MD5 implementation does not support the authentication challenge procedures in RFC 2747. The no form of this command disables authentication.

  • Page 115

    MPLS and RSVP implicit-null-label Syntax implicit-null-label [enable | disable] no implicit-null-label Context config>router>rsvp Description This command enables the use of the implicit null label for all LSPs signalled by RSVP on the node. All LSPs for which this node is the egress LER and for which the path message is received from the previous hop node over this RSVP interface will signal the implicit null label.

  • Page 116

    Interface Commands Finally, when ‘reliable-delivery’ option is enabled on any interface, RSVP message pacing is disabled on all RSVP interfaces of the system, for example, the user cannot enable the msg-pacing option in the config>router>rsvp context, and error message is returned in CLI. Conversely, when the msg-pacing option is enabled, the user cannot enable the reliable delivery option on any interface on this system.

  • Page 117

    MPLS and RSVP 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide Page 119...

  • Page 118

    Interface Commands Message Pacing Commands msg-pacing Syntax [no] msg-pacing Context config>router>rsvp Description This command enables RSVP message pacing in which the specified number of RSVP messages, specified in the max-burst command, are sent in a configured interval, specified in the period command.

  • Page 119

    MPLS and RSVP Show Commands bypass-tunnel Syntax bypass-tunnel [to ip-address] [protected-lsp [lsp-name]] [dynamic | manual] [detail] Context show>router>mpls Description If fast reroute is enabled on an LSP and the facility method is selected, instead of creating a separate LSP for every LSP that is to be backed up, a single LSP is created which serves as a backup for a set of LSPs.

  • Page 120

    10.10.36.6 lag-2 130591 ------------------------------------------------------------------------------- Bypass Tunnels : 4 =============================================================================== *A:Dut-A>show>router>mpls# interface Syntax interface [ip-int-name | ip-address] [label-map label] interface [ip-int-name | ip-address] Context show>router>mpls Description This command displays MPLS interface information. Parameters ip-int-name — The name of the network IP interface. An interface name cannot be in the form of an IP address.

  • Page 121

    MPLS and RSVP Label Description (Continued) Specifies whether the label value is statically or dynamically assigned. Type A:7210SAS# show router mpls interface =============================================================================== MPLS Interfaces =============================================================================== Interface Port-id TE-metric ------------------------------------------------------------------------------- system system None Admin Groups None Srlg Groups None ip-10.10.2.3 1/1/15 None Admin Groups...

  • Page 122

    Label Description The total number of labels being used by RSVP. In-use labels in entire range Sample Output *A:SRU4>config>router>mpls# show router mpls label 202 ================================================================= MPLS Label 202 ================================================================= Label Label Type Label Owner ----------------------------------------------------------------- static-lsp STATIC ----------------------------------------------------------------- In-use labels in entire range : 5057 ================================================================= *A:SRU4>config>router>mpls#...

  • Page 123

    MPLS and RSVP *A:Dut-A# Syntax lsp lsp-name [status {up|down}] [from ip-address | to ip-address] [detail] lsp {transit | terminate} [status {up | down}] [from ip-address | to ip-address | lsp-name name] [detail] lsp count lsp lsp-name activepath lsp lsp-name path [path-name] [status {up |down}] [detail] lsp [lsp-name] path [path-name] mbb Context show>router>mpls...

  • Page 124

    Label Description (Continued) The total number of LSPs configured. LSPs The IP address of the ingress router for the LSP. From The length of time the LSP has been operational. LSP Up Time The number of transitions that have occurred for the LSP. Transitions The number of attempts that the software should make to re-establish Retry Limit...

  • Page 125

    MPLS and RSVP Label Description (Continued) se — Specifies a shared reservation environment with a limited res- Resv Style ervation scope. This reservation style creates a single reservation over a link that is shared by an explicit list of senders. ff —...

  • Page 126

    Hop Limit : 255 Negotiated MTU : 0 Adaptive : Enabled ClassType FastReroute : Disabled Oper FR : Disabled CSPF : Disabled ADSPEC : Disabled Metric Include Grps: Exclude Grps None None Type : RegularLsp Least Fill : Disabled LdpOverRsvp : Enabled VprnAutoBind : Enabled Oper Metric : 65535...

  • Page 127

    MPLS and RSVP Label Description (Continued) The IP address of the hop that the LSP should traverse on the way to IP Address the egress router. Strict — The LSP must take a direct path from the previous hop Strict/Loose router to the next router.

  • Page 128

    static-lsp Syntax static-lsp [lsp-name] static-lsp {transit | terminate} static-lsp count Context show>router>mpls Description This command displays MPLS static LSP information. Output MPLS Static LSP Output — The following table describes MPLS static LSP output fields. Label Description The name of the LSP used in the path. Lsp Name The system IP address of the egress router for the LSP.

  • Page 129

    MPLS and RSVP aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 aps-1 1/1/10 11.22.11.3 3/2/8...

  • Page 130

    status Syntax status Context show>router>mpls Description This command displays MPLS operation information. Output MPLS Status Output — The following table describes MPLS status output fields. Label Description Down — MPLS is administratively disabled. Admin Status Up — MPLS is administratively enabled. Down —...

  • Page 131

    MPLS and RSVP AB Sample Multipli*: 1 AB Adjust Multipli*: 288 Exp Backoff Retry : Disabled CSPF On Loose Hop : Disabled Lsp Init RetryTime*: 30 seconds Logger Event Bundl*: Disabled Sec FastRetryTimer : Disabled Static LSP FR Timer: 30 seconds P2P Max Bypass Ass*: 1000 P2PActPathFastRetry: Disabled In Maintenance Mode: No...

  • Page 132

    *A:7210SAS# Show RSVP Commands interface Syntax interface [ip-int-name | ip-address] statistics [detail] Context show>router>rsvp Description This command shows RSVP interfaces. ip-int-name — The name of the network IP interface. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

  • Page 133

    MPLS and RSVP Label Description (Continued) Specifies the percentage of the link bandwidth that RSVP can use for Subscription reservation. When the value is zero (0), no new sessions are permitted on this interface. Specifies the speed for the interface. Port Speed Specifies the amount of unreserved bandwidth.

  • Page 134

    Label Description (Continued) The total number of RSVP RESV CONFIRM messages received on Resv Confirms the RSVP interface. Total RSVP RESV ERROR messages received on RSVP interface. Resv Errors Total RSVP RESV TEAR messages received on RSVP interface. Resv Tears Total RSVP RESV summary refresh messages received on interface.

  • Page 135

    MPLS and RSVP detail — Displays detailed information. Output RSVP Session Output — The following table describers RSVP session output fields. Label Description The IP address of the originating router. From The IP address of the egress router. The IP address of the tunnel’s ingress node supporting this RSVP ses- Tunnel ID sion.

  • Page 136

    =============================================================================== RSVP Sessions =============================================================================== From Tunnel LSP Name State ------------------------------------------------------------------------------- 10.20.1.1 10.20.1.3 A_C_2::A_C_2 ------------------------------------------------------------------------------- Sessions : 1 =============================================================================== A:ALA-12# Page 138 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 137

    MPLS and RSVP statistics Syntax statistics Context show>router>rsvp Description This command displays global statistics in the RSVP instance. Output RSVP Statistics Output — The following table describes RSVP statistics output fields. Label Description The total number of path timeouts. PATH Timeouts The total number of RESV timeouts.

  • Page 138

    Label Description (Continued) Disabled — Message pacing is disabled. RSVP message transmis- sion is not regulated. Displays the time interval, in milliseconds, when the router can send Pacing Period the specified number of RSVP messages specified in the rsvp max- burst command.

  • Page 139

    MPLS and RSVP Tools Commands cspf Syntax cspf to ip-addr [from ip-addr] [bandwidth bandwidth] [include-bitmap bitmap] [exclude- bitmap bitmap] [hop-limit limit] [exclude-address excl-addr [excl-addr...(up to 8 max)]] [use-te-metric] [strict-srlg] [srlggroup grp-id...(up to 8 max)] [skip-interface interface- name] Context tools>perform>router>mpls Description This command computes a CSPF path with specified user constraints.

  • Page 140

    resignal Syntax resignal {lsp lsp-name path path-name | delay minutes} Context tools>perform>router>mpls Description This command resignal is a specific LSP path. The minutes parameter configures the global timer or all LSPs for resignal. If only lsp-name and path-name are provided, the LSP will be resignaled imme- diately.

  • Page 141

    MPLS and RSVP Clear Commands interface Syntax interface ip-int-name Context clear>router>mpls Description This command resets or clears statistics for MPLS interfaces. Parameters ip-int-name — The name of an existing IP interface. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. Syntax lsp lsp-name Context...

  • Page 142

    Debug Commands mpls Syntax mpls [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tun- nel-id] [lsp-id lsp-id] no mpls Context debug>router Description This command enables and configures debugging for MPLS. Parameters lsp lsp-name — Name that identifies the LSP. The LSP name can be up to 32 characters long and must be unique.

  • Page 143

    MPLS and RSVP Syntax all [detail] no all Context debug>router>mpls>event debug>router>rsvp>event Description This command debugs all events. The no form of the command disables the debugging. Parameters detail — Displays detailed information about all events. auth Syntax auth no auth Context debug>router>rsvp>event Description...

  • Page 144

    Parameters detail — Displays detailed information about MPLS IOM events. lsp-setup Syntax lsp-setup [detail] no lsp-setup Context debug>router>mpls>event Description This command debugs LSP setup events. The no form of the command disables the debugging. Parameters detail — Displays detailed information about LSP setup events. Syntax mbb [detail] no mbb...

  • Page 145

    MPLS and RSVP Syntax xc [detail] no xc Context debug>router>mpls>event Description This command debugs cross connect events. The no form of the command disables the debugging. Parameters detail — Displays detailed information about cross connect events. rsvp Syntax [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel-id] [lsp-id lsp-id] [interface ip-int-name] no rsvp Context...

  • Page 146

    path Syntax path [detail] no path Context debug>router>rsvp>event Description This command debugs path-related events. The no form of the command disables the debugging. Parameters detail — Displays detailed information about path-related events. resv Syntax resv [detail] no resv Context debug>router>rsvp>event Description This command debugs RSVP reservation events.

  • Page 147

    MPLS and RSVP Syntax ack [detail] no ack Context debug>router>rsvp>packet Description This command debugs ack packets. The no form of the command disables the debugging. Parameters detail — Displays detailed information about RSVP-TE ack packets. bundle Syntax bundle [detail] no bundle Context debug>router>rsvp>packet Description...

  • Page 148

    path Syntax path [detail] no path Context debug>router>rsvp>packet Description This command enables debugging for RSVP path packets. The no form of the command disables the debugging. Parameters detail — Displays detailed information about path-related events. patherr Syntax patherr [detail] no patherr Context debug>router>rsvp>packet Description...

  • Page 149

    MPLS and RSVP resverr Syntax resverr [detail] no resverr Context debug>router>rsvp>packet Description This command debugs ResvErr packets. The no form of the command disables the debugging. Parameters detail — Displays detailed information about ResvErr packets. resvtear Syntax resvtear [detail] no resvtear Context debug>router>rsvp>packet Description...

  • Page 150

    Page 152 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 151: Label Distribution Protocol

    Label Distribution Protocol In This Chapter This chapter provides information to enable Label Distribution Protocol (LDP). Topics in this chapter include: • Label Distribution Protocol on page 154 → LDP and MPLS on page 154 → LDP Architecture on page 155 →...

  • Page 152: Label Distribution Protocol

    LDP and MPLS Label Distribution Protocol NOTE: 7210 SAS-K 2F4T6C supports only TLDP for the purposes of exchanging the service labels. It does not support link LDP. The following sections explain the generic LDP behavior. It does not imply that link LDP is supported on 7210 SAS-K2F4T6C. Label Distribution Protocol (LDP) is a protocol used to distribute labels in non-traffic-engineered applications.

  • Page 153: Ldp Architecture

    Label Distribution Protocol LDP) and allocated a label. The mapping between the label and the FEC is communicated to the forwarding plane. In order for this processing on the packet to occur at high speeds, optimized tables are maintained in the forwarding plane that enable fast access and packet identification. When an unlabeled packet ingresses the router, classification policies associate it with a FEC.

  • Page 154: Subsystem Interrelationships

    Subsystem Interrelationships Subsystem Interrelationships The sections below describe how LDP and the other subsystems work to provide services. Memory LDP MIB Session DB Label Send/ Timer Protocol Receive Send/ Config Receive (CLI/SNMP) Timer DB FEC/ Label DB Logger Event Queue Interface Service Event...

  • Page 155: Memory Manager And Ldp

    Label Distribution Protocol Memory Manager and LDP LDP does not use any memory until it is instantiated. It pre-allocates some amount of fixed memory so that initial startup actions can be performed. Memory allocation for LDP comes out of a pool reserved for LDP that can grow dynamically as needed. Fragmentation is minimized by allocating memory in larger chunks and managing the memory internally to LDP.

  • Page 156: Execution Flow

    In the router, the adjacency management is done through the establishment of a Service Distribution Path (SDP) object, which is a service entity in the Nokia service model. The Nokia service model uses logical entities that interact to provide a service. The service model requires the service provider to create configurations for four main entities: •...

  • Page 157

    Label Distribution Protocol If the SDP is identified as using LDP signaling, then an LDP extended hello adjacency is attempted. If another SDP is created to the same remote destination, and if LDP signaling is enabled, no further action is taken, since only one adjacency and one LDP session exists between the pair of nodes.

  • Page 158: Label Exchange

    Label Exchange Label Exchange Label exchange is initiated by the service manager. When an SDP is attached to a service (for example, the service gets a transport tunnel), a message is sent from the service manager to LDP. This causes a label mapping message to be sent. Additionally, when the SDP binding is removed from the service, the VC label is withdrawn.

  • Page 159

    Label Distribution Protocol When the user changes the implicit null configuration option, LDP withdraws all the FECs and re- advertises them using the new label value. Global Outbound filtering is performed by way of the configuration of an export policy. The Global LDP export policy can be used to explicitly originate label bindings for local interfaces.

  • Page 160: Ldp Fast-reroute For Is-is And Ospf Prefixes

    LDP Fast-Reroute for IS-IS and OSPF Prefixes FEC Resolution Procedure When prefer-tunnel-in-tunnel is Enabled When LDP tries to resolve a prefix received over a T-LDP session, it performs a lookup in the Routing Table Manager (RTM). This lookup returns the next hop to the destination PE and the advertising router (ABR or destination PE itself).

  • Page 161

    Label Distribution Protocol config>router>isis>loopfree-alternate config>router>ospf>loopfree-alternate. The above commands instruct the IGP SPF to attempt to pre-compute both a primary next-hop and an LFA next-hop for every learned prefix. When found, the LFA next-hop is populated into the RTM along with the primary next-hop for the prefix. Next the user enables the use by LDP of the LFA next-hop by configuring the following option: config>router>ldp>fast-reroute When this command is enabled, LDP will use both the primary next-hop and LFA next-hop, when...

  • Page 162: Ldp Frr Procedures

    LDP Fast-Reroute for IS-IS and OSPF Prefixes LDP FRR Procedures The LDP FEC resolution when LDP FRR is not enabled operates as follows. When LDP receives a FEC, label binding for a prefix, it will resolve it by checking if the exact prefix, or a longest match prefix when the aggregate-prefix-match option is enabled in LDP, exists in the routing table and is resolved against a next-hop which is an address belonging to the LDP peer which advertized the binding, as identified by its LSR-id.

  • Page 163

    Label Distribution Protocol new feature introduced for faster tracking of link LDP peers. See Section 1.2.1 for more details. The tunnel-down-dump-time option or the label-withdrawal-delay option, when enabled, does not cause the corresponding timer to be activated for a FEC as long as a backup NHLFE is still available.

  • Page 164: Is-is And Ospf Support For Loop-free Alternate Calculation

    LDP Fast-Reroute for IS-IS and OSPF Prefixes When an RSVP LSP is used as a shortcut by IGP, it is included by SPF as a P2P link and can also be optionally advertised into the rest of the network by IGP. Thus the SPF is able of using a tunneled next-hop as the primary next-hop for a given prefix.

  • Page 165: Figure 10: Topology With Primary And Lfa Routes

    Label Distribution Protocol 5 (8) Primary Route LFA Link-Protect Route LFA Node-Protect Route Figure 10: Topology with Primary and LFA Routes The primary route is by way of R3. The LFA route by way of R2 has two equal cost paths to reach R5.

  • Page 166: Figure 11: Example Topology With Broadcast Interfaces

    LDP Fast-Reroute for IS-IS and OSPF Prefixes 5 (8) Primary Route LFA Link-Protect Route Figure 11: Example Topology with Broadcast Interfaces In order for next-hop R2 to be a link-protect LFA for route R5 from R1, it must be loop-free with respect to the R1-R3 link’s Pseudo-Node (PN).

  • Page 167

    Label Distribution Protocol • Rule 3: Link-protect LFA backup next-hop (primary next-hop R1-R3 is a broadcast interface): Distance_opt(R2, R5) < Distance_opt(R2, R1) + Distance_opt(R1, R5) and, Distance_opt(R2, R5) < Distance_opt(R2, PN) + Distance_opt(PN, R5) where; PN stands for the R1-R3 link Pseudo-Node. For the case of P2P interface, if SPF finds multiple LFA next-hops for a given primary next-hop, it follows the following selection algorithm: A) It will pick the node-protect type in favor of the link-protect type.

  • Page 168

    LDP Fast-Reroute for IS-IS and OSPF Prefixes does not guarantee link protection, can still be selected as a last resort. The same thing, a link- protect LFA which does not avoid the PN may still be selected as a last resort.Both the computed primary next-hop and LFA next-hop for a given prefix are programmed into RTM.

  • Page 169

    Label Distribution Protocol B) The algorithms continues with first set if not empty, otherwise it continues with second set. C) If the second set is used, the algorithm selects the tunneled LFA next-hop which endpoint corresponds to the node advertising the prefix. →...

  • Page 170: Multi-area And Multi-instance Extensions To Ldp

    Multi-Area and Multi-Instance Extensions to LDP Multi-Area and Multi-Instance Extensions to LDP To extend LDP across multiple areas of an IGP instance or across multiple IGP instances, the current standard LDP implementation based on RFC 3036 requires that all the /32 prefixes of PEs be leaked between the areas or instances.

  • Page 171: Ldp Process Overview

    Label Distribution Protocol LDP Process Overview Figure 12 displays the process to provision basic LDP parameters. START ENABLE LDP APPLY EXPORT/IMPORT POLICIES CONFIGURE LDP INTERFACE PARAMETERS CONFIGURE TARGETED SESSION PARAMETERS CONFIGURE PATH PARAMETERS CONFIGURE PEER PARAMETERS ENABLE 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide Page 173...

  • Page 172: Figure 12: Ldp Configuration And Implementation

    Multi-Area and Multi-Instance Extensions to LDP START ENABLE LDP CONFIGURE TARGETED SESSION PARAMETERS CONFIGURE PEER PARAMETERS ENABLE Figure 12: LDP Configuration and Implementation Page 174 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 173: Configuring Ldp With Cli

    Label Distribution Protocol Configuring LDP with CLI This section provides information to configure LDP using the command line interface. Topics in this section include: • LDP Configuration Overview on page 176 • Basic LDP Configuration on page 177 • Common Configuration Tasks on page 178 •...

  • Page 174: Ldp Configuration Overview

    LDP Configuration Overview When the implementation of LDP is instantiated, the protocol is in the state. In no shutdown addition, targeted sessions are then enabled. The default parameters for LDP are set to the documented values for targeted sessions in draft-ietf-mpls-ldp-mib-09.txt. Page 176 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 175: Basic Ldp Configuration

    Label Distribution Protocol Basic LDP Configuration This chapter provides information to configure LDP and remove configuration examples of common configuration tasks. The LDP protocol instance is created in the (enabled) state. no shutdown 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide Page 177...

  • Page 176: Common Configuration Tasks

    Enabling LDP Common Configuration Tasks This section provides information to configure: • Enabling LDP on page 178 • Targeted Session Parameters on page 181 • Peer Parameters on page 199 Enabling LDP LDP must be enabled in order for the protocol to be active. MPLS must also be enabled. MPLS is enabled in the context.

  • Page 177: Configuring Graceful-restart Helper Parameters

    TLV in the LDP initialization message, assisting the LDP in preserving its IP forwarding state across the restart. Nokia’s recovery is self-contained and relies on information stored internally to self-heal. This feature is only used to help third-party routers without a self-healing capability to recover.

  • Page 178: Applying Export And Import Policies

    Applying Export and Import Policies Applying Export and Import Policies Both inbound and outbound label binding filtering are supported. Inbound filtering allows a route policy to control the label bindings an LSR accepts from its peers. An import policy can accept or reject label bindings received from LDP peers.

  • Page 179: Targeted Session Parameters

    Label Distribution Protocol Targeted Session Parameters Use the following syntax to specify targeted-session parameters: CLI Syntax: config>router# ldp targeted-session disable-targeted-session hello timeout factor keepalive timeout factor peer ip-address no bfd-enable hello timeout factor keepalive timeout factor no shutdown The following example displays an LDP configuration example: A:ALA-1>config>router>ldp# info ---------------------------------------------- targeted-session...

  • Page 180: Interface Parameters

    Interface Parameters Interface Parameters Use the following syntax to configure interface parameters: CLI Syntax: config>router# ldp interface-parameters hello timeout factor keepalive timeout factor transport-address {system|interface} interface ip-int-name hello timeout factor keepalive timeout factor transport-address {system|interface} no shutdown The following example displays an interface parameter configuration example: A:ALU_SIM11>config>router>ldp# info ---------------------------------------------- aggregate-prefix-match...

  • Page 181: Session Parameters

    Label Distribution Protocol Session Parameters Use the following syntax to specify session parameters: CLI Syntax: config>router# ldp session-parameters peer ip-address auth-keychain name authentication-key [authentication-key|hash-key] [hash|hash2] A:ALA-1>config>router>ldp# info ---------------------------------------------- session-parameters peer 10.10.10.104 authentication-key "3WErEDozxyQ" hash exit exit targeted-session hello 5000 255 keepalive 5000 255 peer 10.10.10.104 no bfd-enable...

  • Page 182: Ldp Signaling And Services

    LDP Signaling and Services LDP Signaling and Services When LDP is enabled, targeted sessions can be established to create remote adjacencies with nodes that are not directly connected. When service distribution paths (SDPs) are configured, extended discovery mechanisms enable LDP to send periodic targeted hello messages to the SDP’s far-end point.

  • Page 183: Ldp Configuration Management Tasks

    Label Distribution Protocol LDP Configuration Management Tasks This section discusses the following LDP configuration management tasks: • Disabling LDP on page 185 • Modifying Targeted Session Parameters on page 186 Disabling LDP The no ldp command disables the LDP protocol on the router. All parameters revert to the default settings.

  • Page 184: Modifying Targeted Session Parameters

    LDP Signaling and Services Modifying Targeted Session Parameters The modification of LDP targeted session parameters does not take effect until the next time the session goes down and is re-establishes. Individual parameters cannot be deleted. The form of a targeted-session parameter command reverts modified values back to the default. The following example displays the command syntax usage to revert targeted session parameters back to the default values: Example:...

  • Page 185: Modifying Interface Parameters

    Label Distribution Protocol Modifying Interface Parameters The modification of LDP targeted session parameters does not take effect until the next time the session goes down and is re-establishes. Individual parameters cannot be deleted. The no form of a interface-parameter command reverts modified values back to the defaults. The following output displays the default values: 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide Page 187...

  • Page 186

    LDP Signaling and Services Page 188 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 187: Ldp Command Reference

    Command Hierarchies LDP Command Reference Command Hierarchies • LDP Commands on page 189 • Show Commands on page 190 • Clear Commands on page 191 • Debug Commands on page 192 LDP Commands config — router — [no] — [no] aggregate-prefix-match —...

  • Page 188: Show Commands

    Command Hierarchies — no keepalive — [no] shutdown — transport-address {system | interface} — label-withdrawal-delay seconds — [no] prefer-tunnel-in-tunnel — session-parameters — [no] peer ip-address — [no] export-addresses — export-addresses policy-name [policy-name ... (up to 5 max)] — no export-addresses —...

  • Page 189: Clear Commands

    Command Hierarchies — bindings active prefixes [egress-nh ip-address] [family] [{summary | detail}] — bindings active prefixes prefix ip-prefix/ip-prefix-length [{summary | detail}] [egress-if port-id] — bindings active prefixes prefix ip-prefix/ip-prefix-length [{summary | detail}] [egress-lsp tunnel-id] — bindings active prefixes prefix ip-prefix/ip-prefix-length [egress-nh ip-address] [{summary | detail}] —...

  • Page 190: Debug Commands

    Command Hierarchies Debug Commands [no] debug — router — [no] — [no] interface interface-name — [no] event — [no] messages — [no] packet [detail] — hello [detail] — no hello — peer ip-address — [no] event — [no] bindings — [no] messages —...

  • Page 191

    Generic Commands LDP Configuration Commands Generic Commands Syntax [no] ldp Context config>router Default This command creates the context to configure an LDP parameters. LDP is not enabled by default and must be explicitely enabled (no shutdown). To suspend the LDP protocol, use the shutdown command. Configuration parameters are not affected.

  • Page 192

    aggregate-prefix-match Syntax [no] aggregate-prefix-match Context config>router>ldp Description The command enables the use by LDP of the aggregate prefix match procedures. When this option is enabled, LDP performs the following procedures for all prefixes. When an LSR receives a FEC-label binding from an LDP neighbor for a given specific FEC1 element, it will install the binding in the LDP FIB if: •...

  • Page 193

    Generic Commands export Syntax export policy-name [policy-name …upto 5 max] no export Context config>router>ldp Description This command specifies the export route policies used to determine which routes are exported to LDP. Policies are configured in the config>router>policy-options context. If no export policy is specified, non-LDP routes will not be exported from the routing table manager to LDP.

  • Page 194

    • The TCP connection used by a link LDP session to a peer went down, due say to next-hop track- ing of the LDP transport address in RTM, which brings down the LDP session. In this case, LDP sends a neighbor/next-hop down message to the IOM for this LDP peer only. •...

  • Page 195

    Generic Commands Parameters ip-prefix/mask — Specify information for the specified IP prefix and mask length. Values <ip-address/mask> ipv4-prefix - a.b.c.d ipv4-prefix-le - [0..32] ipv6-prefix x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x - [0..FFFF]H d - [0..255]D ipv6-prefix-le - [0..128] next-hop — Specify the IP address of the next hop of the prefix. advertised-label —...

  • Page 196

    implicit-null-label Syntax [no] implicit-null-label Context config>router>ldp Description This command enables the use of the implicit null label. Use this command to signal the IMPLICIT NULL option for all LDP FECs for which this node is the egress LER. The no form of this command disables the signaling of the implicit null label. Default no implicit-null-label maximum-recovery-time...

  • Page 197

    Generic Commands import Syntax import policy-name [policy-name …upto 5 max] no import Context config>router>ldp Description This command configures import route policies to determine which label bindings (FECs) are accepted from LDP neighbors. Policies are configured in the config>router>policy-options context. If no import policy is specified, LDP accepts all label bindings from configured LDP neighbors. Import policies can be used to limit or modify the routes accepted and their corresponding parameters and metrics.

  • Page 198

    keepalive Syntax keepalive timeout factor no keepalive Context config>router>ldp>interface-parameters>interface>ipv4 config>router>ldp>interface-parameters>ipv4 config>router>ldp>targ-session>ipv4 config>router>ldp>targ-session>peer Description This command configures the time interval, in seconds, that LDP waits before tearing down the session. The factor parameter derives the keepalive interval. If no LDP messages are exchanged for the configured time interval, the LDP session is torn down. Keepalive timeout is usually three times the keepalive interval.

  • Page 199

    Generic Commands local-lsr-id Syntax local-lsr-id interface-name no local-lsr-id Context config>router>ldp>targeted-session>peer Description This command enables the use the use of the address of a specific interface as the LSR-ID for the hello adjacency of a T-LDP session. The interface can be a regular interface or a loopback interface, including the system interface.

  • Page 200

    prefix-ipv4 Syntax prefix-ipv4 {enable | disable} Context config>router>ldp>interface-params>interface>ipv4>fec-type-capability Description This command enables and disables IPv4 prefix FEC capability on the interface. enable — Keyword to enable IPv4FEC capability. disable — Keyword to disable IPv4FEC capability. hello Syntax hello timeout factor no hello Context config>router>ldp>interface-parameters>interface>ipv4...

  • Page 201

    Generic Commands factor — Specifies the number of keepalive messages that should be sent on an idle LDP session in the hello timeout interval. Values 1 — 255 hello-reduction Syntax hello-reduction {enable factor | disable} no hello-reduction Context config>router>ldp>targ-session>ipv4 Description This command enables the suppression of periodic targeted Hello messages between LDP peers once the targeted LDP session is brought up.

  • Page 202

    factor — Specifies the hello reduction dampening factor. Values 3 to 20 interface Syntax [no] interface ip-int-name Context config>router>ldp>if-params Description This command enables LDP on the specified IP interface. The no form of the command deletes the LDP interface and all configuration information associated with the LDP interface.

  • Page 203

    Generic Commands ipv4 Syntax ipv4 Context config>router>ldp>interface-parameters>interface config>router>ldp>interface-parameters config>router>ldp>targeted-session Description This command enables the context to configure IPv4 LDP parameters for the interface. Default transport-address Syntax transport-address {interface | system} no transport-address Context config>router>ldp>interface-parameters>interface>ipv4 config>router>ldp>interface-parameters>interface>ipv6 config>router>ldp>interface-parameters>ipv4 Description This command configures the transport address to be used when setting up the LDP TCP sessions. The transport address can be configured as interface or system.

  • Page 204

    Page 206 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 205

    Session Parameters Commands Session Parameters Commands session-parameters Syntax session-parameters Context config>router>ldp Description This command enables the context to configure peer-specific parameters. Default peer Syntax [no] peer ip-address Context config>router>ldp>session-parameters Description This command configures parameters for an LDP peer. Default Parameters ip-address —...

  • Page 206

    export-prefixes Syntax export-prefixes policy-name [policy-name ... (up to 5 max)] no export-prefixes Context config>router>ldp>session-params>peer Description This command specifies the export route policy used to determine which prefixes received from other LDP and T-LDP peers are re-distributed to this LDP peer via the LDP/T-LDP session to this peer. A prefix that is filtered out (deny) will not be exported.

  • Page 207

    Session Parameters Commands fec129-cisco-interop Syntax [no] fec129-cisco-interop Context config>router>ldp>session-params>peer Description This command configures whether LDP will provide translation between non-compliant FEC 129 Cisco formats. Peer LDP sessions must be manually configured towards the non-compliant Cisco PEs. When enabled, Cisco non-compliant format will be used to send and interpret received label release messages.

  • Page 208

    Targeted Session Commands targeted-session Syntax targeted-session Context config>router>ldp Description This command configures targeted LDP sessions. Targeted sessions are LDP sessions between non- directly connected peers. Hello messages are sent directly to the peer platform instead of to all the routers on this subnet multicast address. The discovery messages for an indirect LDP session are addressed to the specified peer and not to the multicast address.

  • Page 209

    Targeted Session Commands tunneling Syntax [no] tunneling Context config>router>ldp>targ-session>peer Description This command enables LDP over tunnels. The no form of the command disables tunneling. Default no tunneling Syntax [no] lsp lsp-name Context config>router>ldp>targ-session>tunneling Description This command configures a specific LSP destined to this peer and to be used for tunneling of LDP FEC over RSVP.

  • Page 210

    Page 212 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 211

    Show LDP Commands auth-keychain Syntax auth-keychain [keychain] Context show>router>ldp Description This command displays LDP sessions using a particular authentication key-chain. Parameters keychain — Specifies an existing keychain name. Sample Output *A:ALA-48>config>router>ldp# show router ldp auth-keychain =============================================================================== LDP Peers =============================================================================== Peer TTL Security Min-TTL-Value Authentication Auth key chain ------------------------------------------------------------------------------- 10.20.1.3...

  • Page 212

    Show Commands summary — Displays information in a summarized format. detail — Displays detailed information. active-ecmp — Displays the LDP active bindings with ECMP routes that have been successfully installed in the hardware FIB. session ip-addr — Displays configuration information about LDP sessions. ip-prefix —...

  • Page 213

    Label Description The service type exchanging labels. The possible types displayed are Type VPLS, Epipe, Spoke, and Unknown. The value used by each end of an SDP tunnel to identify the VC. VCId The unique service identification number identifying the service in the SvcID service domain.

  • Page 214

    Show Commands 2.2.2.2/32 131071U 6.6.6.6 ..6.6.6.6/32 131071 1/1/9:26 10.11.26.6 6.6.6.6 ------------------------------------------------------------------------------- No. of Prefix Bindings: 10 =============================================================================== =============================================================================== LDP Generic P2MP Bindings =============================================================================== P2MP-Id RootAddr Interface Peer IngLbl EgrLbl EgrIntf/ EgrNextHop LspId ------------------------------------------------------------------------------- 8193 1.1.1.1 73732 1.1.1.1 131065U 8193 2.2.2.2 73728 1.1.1.1...

  • Page 215

    No Matching Entries Found =============================================================================== A:7210SAS# A:7210SAS# show router ldp bindings p2mp-id 8193 root 2.2.2.2 detail =============================================================================== LDP LSR ID: 2.2.2.2 =============================================================================== Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn WP - Label Withdraw Pending, BU - Alternate Next-hop for Fast Re-Route =============================================================================== LDP Generic P2MP Bindings ===============================================================================...

  • Page 216

    Show Commands =============================================================================== LDP In-Band-SSM P2MP Bindings (Active) =============================================================================== Source Group Interface RootAddr IngLbl EgrLbl EgrIntf/ EgrNextHop ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- No Matching Entries Found =============================================================================== A:7210SAS# A:7210SAS# show router ldp bindings fec-type p2mp detail =============================================================================== LDP LSR ID: 2.2.2.2 =============================================================================== Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn WP - Label Withdraw Pending, BU - Alternate Next-hop for Fast Re-Route ===============================================================================...

  • Page 217

    EgrNextHop : 10.11.12.1 Egr. Flags : None Ing. Flags : None Metric : 1560 ------------------------------------------------------------------------------- P2MP Type P2MP-Id : 8193 Root-Addr : 2.2.2.2 ------------------------------------------------------------------------------- Ing Lbl Peer : 6.6.6.6 Egr Lbl : 131059 Egr Int/LspId : 1/1/9:26 EgrNextHop : 10.11.26.6 Egr.

  • Page 218

    Show Commands Label Description (Continued) The total number of hello adjacencies discovered. No. of Hello Adja- cencies The amount of time the adjacency has been enabled. Up Time The time left before a neighbor is declared to be down. Hold-Time Remain- The number of hello messages received for this adjacency.

  • Page 219

    Table 46 describes the FEC originate parameters output fields. FEC Originate Output Fields Table 3: Label Description Prefix Specifies the static prefix FEC. NHType Specifies the type of next-hop represented by this row entry: unknown — The next-hop type has not been set. IP Addr —...

  • Page 220

    Show Commands Parameters ip-int-name — The name of an existing interface. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. ip-address — The IP address of the LDP neighbor. detail — Displays detailed information. Output LDP Interface Output —...

  • Page 221

    Syntax parameters Context show>router>ldp Description This command displays configuration information about LDP parameters. Output LDP Parameters Output — The following table describes the LDP parameters output fields. Label Description The factor used to derive the Keepalive interval. Keepalive Timeout The time interval, in seconds, that LDP waits before tearing down the Keepalive Factor session.

  • Page 222

    Show Commands Hold Time : 45 sec Hello Factor Passive Mode : False Targeted Sessions : Enabled =============================================================================== *A:SRU4>config>router>ldp# Page 224 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 223

    session Syntax session [ip-addr[label-space] local-addresses [sent|recv] ip-addr ip-address session [ip-addr[label-space] [session-type] [state state] [summary|detail] session [ip-addr[label-space] local-addresses [sent|recv] [family] session [ip-addr[label-space] [sent|recv] overload [fec-type fec-type] session [sent|recv] overload [fec-type fec-type] [family] session [ip-addr[label-space] statistics [packet-type] [session-type] session statistics [packet-type] [session-type] [family] session [session-type] [state state] [summary|detail] [family] Context show>router>ldp...

  • Page 224

    Show Commands Sample Output *A:SRU4>config>router>ldp# show router ldp session ============================================================================== LDP Sessions ============================================================================== Peer LDP Id Adj Type State Msg Sent Msg Recv Up Time ------------------------------------------------------------------------------ 1.1.1.1:0 Link Nonexistent 0d 00:00:04 10.8.100.15:0 Both Nonexistent 14653 21054 0d 12:48:25 10.20.1.20:0 Both Established 105187 84837...

  • Page 225

    Mesg Sent : 478 Mesg Recv : 480 FECs Sent : 182 FECs Recv : 170 Addrs Sent : 13 Addrs Recv : 16 GR State : Capable Label Distribution : DU Nbr Liveness Time : 0 Max Recovery Time MP MBB : Not Capable Dynamic Capability: Not Capable...

  • Page 226

    Show Commands Parameters family — Specifies a peer family for which to display information. Values ipv4, ipv6 ip-address — Specifies the IP address of a targeted LDP peer for which to display information. ipv4-address — a.b.c.d Values ipv6-address — x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x —...

  • Page 227

    status Syntax status Context show>router>ldp Description This command displays LDP status information. Output LDP Status Output — The following table describes LDP status output fields. Label Description Up — The LDP is administratively enabled. Admin State Down — The LDP is administratively disabled. Up —...

  • Page 228

    Show Commands Label Description (Continued) The total number of attempted sessions for this LDP instance. Attempted Ses- sions The total number of “Session Rejected” or “No Hello Error” notifica- No Hello Err tion messages sent or received by this LDP instance. The total number of “Session Rejected”...

  • Page 229

    family — Specifies a peer family for which to display information. Values ipv4, ipv6 ip-address — Specifies the IP address of a targeted LDP peer for which to display information. Values ipv4-address — a.b.c.d ipv6-address — x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x —...

  • Page 230

    Show Commands targ-peer-template-map Syntax targ-peer-template-map [template-name [peer]] Context show>router>ldp Description This command displays information about targeted LDP peer template mapping. Parameters template-name — Specifies the name of a template map. 32 characters maximum. peer — Keyword to display peer information. tcp-session-parameters Syntax tcp-session-parameters [family]...

  • Page 231

    Clear Commands instance Syntax instance Context clear>router>ldp Description This command resets the LDP instance. interface Syntax interface [ip-int-name] Context clear>router>ldp Description This command restarts or clears statistics for LDP interfaces. Parameters ip-int-name — The name of an existing interface. If the string contains special characters (#, $, spaces and other special characters), the entire string must be enclosed within double quotes.

  • Page 232

    Show Commands statistics Syntax statistics Context clear>router>ldp Description This command clears LDP instance statistics. Page 234 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 233

    Debug Commands The following output shows debug LDP configurations discussed in this section. A:ALA-12# debug router ldp peer 10.10.10.104 A:ALA-12>debug>router>ldp# show debug ldp debug router "Base" ldp peer 10.10.10.104 event bindings messages exit packet hello init keepalive label exit exit exit exit A:ALA-12>debug>router>ldp#...

  • Page 234

    Show Commands Parameters ip-address — The IP address of the LDP peer. event Syntax [no] event Context debug>router>ldp>peer Description This command configures debugging for specific LDP events. bindings Syntax [no] bindings Context debug>router>ldp>peer>event Description This command displays debugging information about addresses and label bindings learned from LDP peers for LDP bindings.

  • Page 235

    hello Syntax hello [detail] no hello Context debug>router>ldp>peer>packet Description This command enables debugging for LDP hello packets. The no form of the command disables the debugging output. Parameters detail — Displays detailed information. init Syntax init [detail] no init Context debug>router>ldp>peer>packet Description This command enables debugging for LDP Init packets.

  • Page 236

    Show Commands Page 238 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 237

    Standards and Protocol Support Note: The information presented is subject to change without notice. Nokia assumes no responsibility for inaccuracies contained herein. M(A,N) means 7210 SAS-M in both Access-uplink mode and Network mode; Similarly M(N) means 7210 SAS-M in network mode only T(A,N) means 7210 SAS-M in both Access-uplink mode and Network mode;...

  • Page 238

    Standards and Protocol Support RFC 1772, Application of the Border Gateway Protocol in the Internet is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1997, BGP Communities Attribute is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/ 10GE, Sx-10/100GE, R6, and R12 RFC 2385, Protection of BGP Sessions via the TCP MD5 Signature Option is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 239

    Standards and Protocol Support RFC 5291, Outbound Route Filtering Capability for BGP-4 is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5668, 4-Octet AS Specific BGP Extended Community is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 6811, Prefix Origin Validation is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 Circuit Emulation...

  • Page 240: Fast Reroute

    Standards and Protocol Support IEEE 802.3ab, 1000BASE-T is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S- 1/10GE, Sx-10/100GE, R6, and R12 IEEE 802.3ac, VLAN Tag is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/ 10GE, Sx-10/100GE, R6, and R12 IEEE 802.3ad, Link Aggregation is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 241

    Standards and Protocol Support RFC 951, Bootstrap Protocol (BOOTP) is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1034, Domain Names - Concepts and Facilities is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1035, Domain Names - Implementation and Specification is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 242

    Standards and Protocol Support RFC 4632, Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/ 10GE, Sx-10/100GE, R6, and R12 RFC 5880, Bidirectional Forwarding Detection (BFD) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5881, Bidirectional Forwarding Detection (BFD) IPv4 and IPv6 (Single Hop) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 243

    Standards and Protocol Support RFC 5384, The Protocol Independent Multicast (PIM) Join Attribute Format is supported on M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 6513, Multicast in MPLS/BGP IP VPNs is supported on T(N), Mxp, R6, and R12 RFC 6514, BGP Encodings and Procedures for Multicast in MPLS/IP VPNs is supported on T(N), Mxp, R6, and R12 RFC 6515, IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPNs is...

  • Page 244

    Standards and Protocol Support RFC 3122, Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification is supported on M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 3587, IPv6 Global Unicast Address Format is supported on M(N), T(N), X, Mxp, Sx/ S-1/10GE, Sx-10/100GE, R6, and R12 RFC 4007, IPv6 Scoped Address Architecture is supported on M(N), T(N), X, Mxp, Sx/S- 1/10GE, Sx-10/100GE, R6, and R12...

  • Page 245

    Standards and Protocol Support ISO/IEC 10589:2002, Second Edition, Nov. 2002, Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1195, Use of OSI IS-IS for Routing in TCP/IP and Dual Environments is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 246

    Standards and Protocol Support RFC 5310, IS-IS Generic Cryptographic Authentication is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 6232, Purge Originator Identification TLV for IS-IS is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 6233, IS-IS Registry Extension for Purges is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 Management...

  • Page 247

    Standards and Protocol Support LLDP-MIB, IEEE P802.1AB(TM) LLDP MIB is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1157, A Simple Network Management Protocol (SNMP) is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1215, A Convention for Defining Traps for use with the SNMP is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 1724, RIP Version 2 MIB Extension is supported on Mxp...

  • Page 248

    Standards and Protocol Support RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol is supported on M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 2819, Remote Network Monitoring Management Information Base is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 2856, Textual Conventions for Additional High Capacity Data Types is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 249

    Standards and Protocol Support RFC 3635, Definitions of Managed Objects for the Ethernet-like Interface Types is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 3826, The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User- based Security Model is supported on D, E, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/ S-1/10GE, Sx-10/100GE, R6, and R12 RFC 3877, Alarm Management Information Base (MIB) is supported on D, E, K5, K12,...

  • Page 250

    Standards and Protocol Support RFC 5332, MPLS Multicast Encapsulations is supported on T(N), Mxp, R6, and R12 MPLS — GMPLS draft-ietf-ccamp-rsvp-te-srlg-collect-04, RSVP-TE Extensions for Collecting SRLG Information is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 MPLS —...

  • Page 251

    Standards and Protocol Support RFC 6378, MPLS Transport Profile (MPLS-TP) Linear Protection is supported on T(N), R6, and R12 RFC 6426, MPLS On-Demand Connectivity and Route Tracing is supported on T(N), R6, and R12 RFC 6428, Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile is supported on T(N), R6, and R12 RFC 6478, Pseudowire Status for Static Pseudowires is supported on T(N), R6, and R12 RFC 7213, MPLS Transport Profile (MPLS-TP) Next-Hop Ethernet Addressing is...

  • Page 252

    Standards and Protocol Support RFC 4950, ICMP Extensions for Multiprotocol Label Switching is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5712, MPLS Traffic Engineering Soft Preemption is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5817, Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12...

  • Page 253

    Standards and Protocol Support RFC 5187, OSPFv3 Graceful Restart (Helper Mode) is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5243, OSPF Database Exchange Summary List Optimization is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5250, The OSPF Opaque LSA Option is supported on K12, M(N), T(N), X, Mxp, Sx/ S-1/10GE, Sx-10/100GE, R6, and R12 RFC 5309, Point-to-Point Operation over LAN in Link State Routing Protocols is supported...

  • Page 254: Quality Of Service

    Standards and Protocol Support RFC 6391, Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network is supported on Mxp, R6, and R12 RFC 6718, Pseudowire Redundancy is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/ 10GE, Sx-10/100GE, R6, and R12 RFC 6870, Pseudowire Preferential Forwarding Status bit is supported on K12, M(N), T(N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 RFC 7023, MPLS and Ethernet Operations, Administration, and Maintenance (OAM)

  • Page 255

    Standards and Protocol Support IEEE 1588-2008, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems is supported on D-ETR, K5, K12, M(A,N), T(A,N), X, Mxp, Sx-1/10GE, R6, and R12 ITU-T G.781, Synchronization layer functions, issued 09/2008 is supported on D-ETR, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-10/100GE, R6, and R12 ITU-T G.813, Timing characteristics of SDH equipment slave clocks (SEC), issued 03/ 2003 is supported on D-ETR, K5, K12, M(A,N), T(A,N), X, Mxp, Sx/S-1/10GE, Sx-...

  • Page 256

    Standards and Protocol Support Page 258 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 257

    NDEX paths 46, 52 router interface signaling protocol overview static LSP architecture execution flow label exchange LDP and MPLS RSVP subsystems overview label manager for MPLS LDP configuration hellos logger message pacing memory manager traffic engineering service manager configuring configuring command reference basic message pacing...

  • Page 258

    Page 260 7210 SAS OS 7210 SAS-K 2F4T6C MPLS Guide...

  • Page 259: Technical Support

    Customer Document and Product Support Customer documentation Customer Documentation Welcome Page Technical Support Product Support Portal Documentation feedback Customer Documentation Feedback...

  • Page 260

    © 2017 Nokia. 3HE12059AAAETQZZA...

Comments to this Manuals

Symbols: 0
Latest comments: