router/ethernetswitch …zte.by/manuals/59xx(v4.8.22)/mpls volume.pdfsubinterface parameters ofthe...

ZXR10Router/Ethernet Switch

Command Manual (MPLS Volume)

Version 4.8.22

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900Fax: (86) 755 26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATION

Copyright © 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATIONor of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,the user of this document shall not acquire any license to the subject matter herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 Dec. 28, 2008 First Edition

Serial Number: sjzl20086538

About This Manual.............................................. i

Command Introduction .....................................1Manual Use Guide........................................................... 1

Description of Man-Machine Commands............................. 1

Auxiliary Function ........................................................... 2

Command Mode ............................................................. 3

MPLS LDP Configuration ....................................7clear mpls ldp ................................................................ 8

clear mpls ldp dampening ................................................ 8

clear mpls ldp flap .......................................................... 9

mpls ip (Global Configuration) .......................................... 9

mpls ip(Interface Configuration) ......................................10

mpls label range............................................................10

mpls ldp access-fec........................................................11

mpls ldp advertise-labels ................................................12

mpls ldp advertise-labels old-style ...................................14

mpls ldp backoff ............................................................15

mpls ldp bfd .................................................................16

mpls ldp dampening.......................................................16

mpls ldp dampening-acl .................................................17

mpls ldp discovery hello .................................................18

mpls ldp discovery targeted-hello ....................................19

mpls ldp discovery transport-address ...............................19

mpls ldp egress.............................................................21

mpls ldp enable connect-with-dod....................................22

mpls ldp explicit-null ......................................................22

mpls ldp graceful-restart ................................................23

mpls ldp holdtime..........................................................24

mpls ldp neighbor password............................................25

mpls ldp request-labels ..................................................25

mpls ldp router-id..........................................................26

mpls ldp style ...............................................................27

mpls ldp target-session ..................................................28

mpls xconnect...............................................................28

show mpls forwarding-table ............................................29

show mpls l2transport binding.........................................30

show mpls l2transport vc................................................31

show mpls label range....................................................33

show mpls ldp backoff....................................................33

show mpls ldp bindings ..................................................34

show mpls ldp dampening summary.................................36

show mpls ldp flap-statistics summary .............................37

show mpls ldp discovery.................................................38

show mpls interface.......................................................39

show mpls ldp neighbor..................................................39

show mpls ldp graceful-restart ........................................41

show mpls ldp parameters ..............................................42

MPLS BGP VPN Configuration ..........................43description ...................................................................43

export map...................................................................44

import map ..................................................................44

ip vrf ...........................................................................45

ip vrf forwarding............................................................45

maximum routes ...........................................................46

monitor session.............................................................46

monitor session destination.............................................47

monitor session source...................................................47

rd................................................................................47

route-target..................................................................48

show ip protocol routing vrf ............................................48

show ip protocol routing vrf-summary ..............................49

show ip route mng.........................................................49

show ip route vpn..........................................................49

show ip route vrf ...........................................................50

show ip route vrf-summary.............................................50

show ip vrf ...................................................................50

show monitor session.....................................................51

tunnel checksum ...........................................................51

tunnel destination..........................................................52

tunnel key ....................................................................52

tunnel mode .................................................................52

tunnel sequence ............................................................53

tunnel source................................................................53

VPLS Configuration..........................................55clear flowstat vpls..........................................................55

clear flowstat vpws ........................................................56

clear mac-table vfi.........................................................56

peer ............................................................................57

pwtype.........................................................................58

show mac-filter .............................................................59

show mac-table.............................................................59

show mpls l2transport vc vpls .........................................60

show mpls l2transport vpn summary................................62

show vfi .......................................................................62

show vfi brief ................................................................63

stp-tunnel enable ..........................................................64

vcid .............................................................................64

vpls apply-mac-filter ......................................................65

vfi ...............................................................................66

vfi mspw ......................................................................66

vpls mac-filter...............................................................67

vlan range ....................................................................68

xconnect vfi ..................................................................68

MPLS Traffic Engineering Configuration...........69clear ip rsvp authentication.............................................70

ip explicit-path ..............................................................70

ip rsvp authentication ....................................................71

ip rsvp authentication challenge ......................................71

ip rsvp authentication challenge-imp ................................72

ip rsvp authentication lifetime .........................................72

ip rsvp authentication key passphrase ..............................73

ip rsvp authentication type .............................................73

ip rsvp authentication window-size...................................74

ip rsvp bandwidth..........................................................74

ip rsvp bfd....................................................................75

ip rsvp signalling hello graceful-restart .............................76

ip rsvp signalling hello graceful-restart refresh

interval ................................................................76

ip rsvp signalling hello graceful-restart refresh misses .........77

ip rsvp signalling hello graceful-restart timers

recovery-time .......................................................77

ip rsvp signalling hello graceful-restart timers

restart-time ..........................................................78

ip rsvp signalling refresh interval .....................................78

ip rsvp signalling refresh misses ......................................79

mpls oam(Global Configuration) ......................................79

mpls oam(Interface Configuration)...................................80

mpls static tunnel ..........................................................80

mpls traffic-eng ds-te.....................................................81

mpls traffic-eng ds-te bc-mode........................................81

mpls traffic-eng ds-te exp-maps ......................................82

mpls traffic-eng ds-te te-class .........................................82

mpls traffic-eng signaling advertise implicit-null.................83

mpls traffic-eng tunnels(Global Configuration) ...................84

mpls traffic-eng tunnels(Interface Configuration) ...............84

show ip rsvp authentication ............................................85

show ip explicit-path......................................................86

show ip rsvp hello graceful-restart ...................................87

show ip rsvp refresh parameter .......................................87

show mpls traffic-eng autoroute ......................................88

show mpls traffic-eng ds-te exp-map ...............................88

show mpls traffic-eng ds-te te-class .................................89

show mpls traffic-eng interface detail ...............................90

show mpls traffic-eng tunnels..........................................91

show mpls traffic-eng tunnels remote-tunnel.....................93

tunnel mpls oam back-up-lsp tunnel ................................94

tunnel mpls oam tunnelid ...............................................94

tunnel mpls oam type ....................................................95

tunnel mpls traffic-eng autoroute announce ......................95

tunnel mpls traffic-eng autoroute metric ...........................96

tunnel mpls traffic-eng bandwidth....................................97

tunnel mpls traffic-eng bfd..............................................97

tunnel mpls traffic-eng class-type ....................................98

tunnel mpls traffic-eng path-option ..................................98

tunnel mpls traffic-eng record-route.................................99

tunnel mpls traffic-eng tunnels priority ........................... 100

tunnel static ingress..................................................... 100

FRR Configuration .........................................103ip rsvp signalling hello.................................................. 103

ip rsvp signalling hello refresh interval............................ 103

ip rsvp signalling hello refresh misses............................. 104

mpls traffic-eng backup_tunnel ..................................... 104

show ip backup route ................................................... 105

show ip rsvp hello instance detail................................... 105

show ip rsvp hello instance summary ............................. 106

show mpls traffic-eng fast-reroute ................................. 107

show mpls traffic-eng interface...................................... 108

tunnel mpls traffic-eng fast-reroute................................ 109

About This Manual

Purpose This manual provides procedures and guidelines that support theoperation of ZXR10 router and Ethernet switch.

IntendedAudience

This manual is intended for engineers and technicians who performoperation activities on ZXR10 router and Ethernet switch.

What Is in ThisManual

This manual contains the following chapters:

Chapter Summary

Chapter 1, CommandIntroduction

This describes the use method of thecommand manual, command description,format convention, auxiliary function andmode.

Chapter 2, MPLS LDPConfiguration

Describes how to configure MPLS routeswitching and show commands, includingthe MPLS and tunnel configurationcommands.

Chapter 3, MPLS VPNConfiguration

Describes how to configure MPLS VPN andshow commands.

Chapter 4, VPLSConfiguration

Describes how to configure VPLS and showcommands.

Chapter 5, MPLSTraffic EngineeringConfiguration

Describes how to configure MPLS trafficengineering and show commands.

Chapter 6, FRRConfiguration

Describes how to configure FRR and showcommands.

RelatedDocumentation

The following documentation is related to this manual:

� ZXR10 Router/Ethernet Switch Command Manual (CommandIndex Volume)

� ZXR10 Router/Ethernet Switch Command Manual (EthernetSwitch Volume)

� ZXR10 Router/Ethernet Switch Command Manual (Basic Con-figuration Volume I)

� ZXR10 Router/Ethernet Switch Command Manual (Basic Con-figuration Volume II)

� ZXR10 Router/Ethernet Switch Command Manual (Basic Con-figuration Volume III)

� ZXR10 Router/Ethernet Switch Command Manual (Remote Ac-cess Volume)

� ZXR10 Router/Ethernet Switch Command Manual (IPv4 Rout-ing Volume I)

� ZXR10 Router/Ethernet Switch Command Manual (IPv4 Rout-ing Volume II)

Confidential and Proprietary Information of ZTE CORPORATION i

ZXR10 Command Manual (MPLS Volume)

� ZXR10 Router/Ethernet Switch Command Manual (QoS Vol-ume)

� ZXR10 Router/Ethernet Switch Command Manual (SecurityVolume)

� ZXR10 Router/Ethernet Switch Command Manual (NetworkManagement Volume)

� ZXR10 Router/Ethernet Switch Command Manual (MulticastVolume)

� ZXR10 Router/Ethernet Switch Command Manual (IPv6 Vol-ume)

� ZXR10 Router/Ethernet Switch Command Manual (Voice andVideo Service Volume)

ii Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Command Introduction

Table of ContentsManual Use Guide............................................................... 1Description of Man-Machine Commands................................. 1Auxiliary Function............................................................... 2Command Mode ................................................................. 3

Manual Use GuideThe commands in other volumes are classified by functional mod-ules, and each functional module corresponds to a chapter andthe commands in the chapter are organized in the form of level 2directory and in the order of a–z.

To search a command, do as follows:

1. Find the desired command by referring to ZXR10 Router/Eth-ernet Switch Command Manual — Command Index.

2. Find command details by the volume, chapter/section and pageof the obtained command.

Description of Man-MachineCommandsEach MML command is described by the following items:

� Function

It describes the function implemented by this command.

� Command Mode

It describes the mode in which this command can be executed.

� Format

It describes the complete format of this command, includingthe no format if possible.

� Parameter Description

It describes parameters in this command in the form and pre-scribes the range and default value. If different products have

Confidential and Proprietary Information of ZTE CORPORATION 1


different parameter ranges or default values, an additionalform is used for description.

� Default

The default value is available in the case that this command isnot set. The default parameter value is not described here forvalue selection.

Additional description shall be given if different products havedifferent default values.

� Instructions

First describes the platform version information about thiscommand. For example, “The platform version X.X.XX or latersupports this command” indicates this command is providedfrom the beginning of the platform version X.X.XX. This com-mand is provided from the platform version 2.6 by default.

Second describes the use method and precautions of this com-mand.

� Example

It describes the use of this command in an example.

� Related Commands

Lists the command(s) related to this command.

� History Command

It describes history version information related to this com-mand if a command is changed after version upgrade.

Do not describe the history command if this entry does not exist.

Auxiliary FunctionThe auxiliary function for ZXR10 devices is as follows.

1. In any command mode, enter a question mark (?) after theDOS prompt of the system, a list of available commands in thecommand mode will be displayed. With the context-sensitivehelp function, the keywords and parameter lists of any com-mands can be obtained.

i. In any command mode, enter a question mark "?" after theDOS prompt of the system, and a list of all commands inthe mode and the brief description of the commands willbe displayed.

ii. Input the question mark behind a character or characterstring to view the list of commands or keywords beginningwith this character or character string. Note that there isno space between the character (string) and the questionmark.

iii. Press TAB behind the character string. If the command orkeyword beginning with this character string is unique, itshall be completed with a space at the end. Note that thereis no space between the character string and the TAB.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Command Introduction

iv. Input a question mark after a command, a keyword or aparameter, the next keyword or parameter to be input willbe listed, and also a brief explanation will be given. Notethat a space must be entered before the question mark.

2. If incorrect command, keyword or parameter is input, the errorisolation is offered with ^ in the user interface after you pressENTER. The ^ is below the first character of the input incorrectcommand, keyword or parameter.

3. ZXR10 router/Ethernet switch allows the command or key-word to be abbreviated into a character or character string thatuniquely identifies this command or keyword. For example, theshow command can be abbreviated to sh or sho.

4. The user interface supports the function of recording inputcommands. A maximum of ten history commands can berecorded. The function is very useful in re-invocation of a longor complicated command or ingress.

To re-invoke a command from the record buffer, conduct oneof the following operations, as shown below.

Command Function

Press CTRL-P or theup arrow key

Re-invokes the latest command in therecord buffer. Repeat these keys toinvoke old commands forwards.

Press CTRL-N or thedown arrow key

Rolls the commands downward. When thelast command line is reached, one moreoperation will roll the commands from thebegging of the buffer cyclically.

In any mode, execute the show history command to list thelatest commands input in this mode.

Command ModeThe command modes in this manual are shown below.

Mode Prompt Admis-sionMode

EntryCommand

Functions

Execmode

ZXR10> enters directlyafter loggingthe system

Views simpleinformation

Privi-legedmode

ZXR10# Execmode

enable Configuressystemparameters

Globalconfig-urationmode

ZXR10(config)# Privi-legedmode

configureterminal

Configuresglobal serviceparameters




EntryCommand

Functions

Inter-faceconfig-urationmode

ZXR10(config-if)#


interface Configuresportparametersand selectsa port typedepending onthe keyword

Subin-terfacemode

ZXR10 (config-subif)#


interface Configuressubinterfaceparametersof theNPCI/NPCT

VLANdata-baseconfig-urationmode

ZXR10(vlan-db)#

Privi-legedmode

vlan database

Creates ordeletes VLANsin batches

VLANconfig-urationmode

ZXR10(config-vlan)#


vlan ConfiguresVLANparameters

MSTPconfig-urationmode

ZXR10(config-mstp)#


spanning-tree mst configuration

ConfiguresMSTPparameters

BasicACLconfig-urationmode

ZXR10(config-basic-acl)#


acl basic Defines basicACL rule

Ex-tendedACLconfig-urationmode

ZXR10(config-ext-acl)#


acl extend Definesextended ACLrule

Lineconfig-urationmode

ZXR10(config-line)#


line console0

line <1~64>(GAR)

Configuresparametersrelated toserial portand telnetconnection

Layer2 ACLconfig-urationmode

ZXR10(config-link-acl)#


acl link Defines layer2 ACL rule


Chapter 1 Command Introduction


EntryCommand

Functions

HybridACLconfig-urationmode

ZXR10(config-hybd-acl)#


acl hybrid Defines hybridACL rule

Routerstand-ard ACLmode

ZXR10 (config-std-nacl)#


ip access-list Defines routerstandard ACLrule

Routerex-tendedACLmode

ZXR10 (config-ext-nacl)#


ip access-list Defines routerextended ACLrule

router rip ConfiguresRIPparameters

router ospf ConfiguresOSPFparameters

router isis ConfiguresIS-ISparameters

router bgp ConfiguresBGPparameters

routerpimsm

ConfiguresPIM-SMparameters

ipv6 routerrip

ConfiguresRIPngparameters.

Routeconfig-urationmode

ZXR10(config-router)#


ipv6 routerospf

ConfiguresOSPFv3parameters

VRFconfig-urationmode

ZXR10(config-vrf)#


ip vrf ConfiguresVRFparameters

VFI con-figu-rationmode

ZXR10(config-vfi)#


vfi ConfiguresVPLS relatedparameters




EntryCommand

Functions

Routeconfig-urationmode(RIP)

address-family ipv4 vrf

ConfiguresRIP VRFparameters

IPv4 ad-dressfamilyconfig-urationmode

ZXR10(config-router-af)#

Routeconfig-urationmode(BGP)

address-family vpnv4

address-family ipv4 vrf

ConfiguresBGP VPNand VRFparameters

Routeconfig-urationmode(BGP4+)

address-family ipv6

ConfiguresBGP4+unicastaddress family

IPv6unicastaddressfamilyconfig-urationmode

ZXR10(config-router-af)#

Routeconfig-urationmode(IS-ISv6)

address-family ipv6

ConfiguresIS-ISv6address family

Routemapconfig-urationmode

ZXR10(config-route-map)#


route-map Configuresroute mapmatching itemand operation

Channe-lizationconfig-urationmode

ZXR10(config-control)#


control Configureschannelizationfor ce1, ce3and cpos3

Dialpeerconfig-urationmode

ZXR10(config-voip100)#


dial-peervoice

Configuresbusinessrelated tointegratedservice

Voiceportconfig-urationmode

ZXR10(config-voice-port)#


voice-port Configuresvoice service

IPSecconfig-urationmode

ZXR10(config-ipsec)#


ipsec ConfiguresIPv6 IPSecprotection

Diagno-sis mode

ZXR10(diag)# Privi-legedmode

diagnose Tests CPUand memoryusage


C h a p t e r 2

MPLS LDP Configuration

Table of Contentsclear mpls ldp .................................................................... 8clear mpls ldp dampening.................................................... 8clear mpls ldp flap .............................................................. 9mpls ip (Global Configuration) .............................................. 9mpls ip(Interface Configuration) ..........................................10mpls label range................................................................10mpls ldp access-fec............................................................11mpls ldp advertise-labels ....................................................12mpls ldp advertise-labels old-style .......................................14mpls ldp backoff ................................................................15mpls ldp bfd .....................................................................16mpls ldp dampening ..........................................................16mpls ldp dampening-acl .....................................................17mpls ldp discovery hello .....................................................18mpls ldp discovery targeted-hello ........................................19mpls ldp discovery transport-address ...................................19mpls ldp egress.................................................................21mpls ldp enable connect-with-dod........................................22mpls ldp explicit-null ..........................................................22mpls ldp graceful-restart ....................................................23mpls ldp holdtime..............................................................24mpls ldp neighbor password................................................25mpls ldp request-labels ......................................................25mpls ldp router-id..............................................................26mpls ldp style ...................................................................27mpls ldp target-session ......................................................28mpls xconnect...................................................................28show mpls forwarding-table ................................................29show mpls l2transport binding.............................................30show mpls l2transport vc....................................................31show mpls label range........................................................33show mpls ldp backoff........................................................33show mpls ldp bindings ......................................................34show mpls ldp dampening summary.....................................36show mpls ldp flap-statistics summary .................................37show mpls ldp discovery.....................................................38show mpls interface...........................................................39show mpls ldp neighbor......................................................39show mpls ldp graceful-restart ............................................41show mpls ldp parameters ..................................................42



clear mpls ldpPurpose Use this command to reset the LDP router or its connection with

some neighbor.

Command Modes Privileged EXEC

Syntax clear mpls ldp [neighbor <ip-address>]

SyntaxDescription

neighbor <ip-address>

IP address of the neighbor, in the dotteddecimal format

Instructions After this command is configured, the router is reset and inter-rupted, and all LDP sessions are reestablished. The recheck of theaccess-fec and egress policies, advertisement and request policies,and the explicit pop-up label advertisement policy is performed onall FECS. The resetting of the session with the designated neigh-bor means the interruption and the reestablishment of the LDPsession with this neighbor only. The recheck is only performed onthe policy related with this neighbor (advertisement, request, andexp-null policies).

Example � This example describes how to reset LDP.ZXR10#clear mpls ldp

� This example describes how to reset the session with the LSRwhose router ID is 100.1.1.1.ZXR10#clear mpls ldp neighbor 100.1.1.1

clear mpls ldp dampeningPurpose Use this command to clear LDP routes dampening and unsuppress

the suppressed routes.


Syntax clear mpls ldp dampening [<ip-address><net-mask>]

SyntaxDescription

<ip-address> The network IP address relates to clear dampinformation, in the dotted decimal notation

<net-mask> Network mask, in the dotted decimal notation

Instructions After this command is configured, the router will clear and resetLDP dampening information already generated, and the router willunsuppress the suppressed LSP; the router will reset flapping sup-press information of some specified LSP, and only the dampeninginformation of this LSP will be cleared. If this LSP is suppressed,the router will unsuppress it.

Example � This example describes how to reset LDP dampening informa-tion.

ZXR10#clear mpls ldp dampening


Chapter 2 MPLS LDP Configuration

� This example describes how to reset dampening information ofa LSP.

ZXR10#clear mpls ldp dampening

clear mpls ldp flapPurpose Use this command to clear the flapping statistic information of LDP

routers.


Syntax clear mpls ldp flap [<ip-address><net-mask>]

SyntaxDescription

<ip-address> Network IP address, in the dotted decimalformat

<net-mask> Network mask, in the dotted decimal format

Instructions After this command is configured, the router will clear the count ofthe flapping of LDP entities where flapping has already occurred ,and the router will reset the count of the flapping of some specifiedLSP; only the count of the flapping of this LSP is cleared and resetand it will be recounted from 0.

Example � This example describes how to rest LDP flapping statistic infor-mation.ZXR10#clear mpls ldp flap

� This example describes how to reset the flapping statistic in-formation of a LSP.ZXR10#clear mpls ldp flap 100.1.1.1 32

mpls ip (GlobalConfiguration)

Purpose Use this command to enable LDP to establish an LSP along a com-mon hop-by-hop routing path. Disable LDP with the no form ofthis command.

Command Modes Global configuration

Syntax mpls ip

no mpls ip

Defaults LDP is disabled by default.

Instructions � his command enables LDP to establish an LSP along a commonhop-by-hop routing path. In addition, it is necessary to enableLDP on the interface to realize dynamic label switching on theinterface.



� Use the no form of this command to disable LDP to establishan LSP along a common hop-by-hop routing path no matterwhether LDP is enabled on the interface or not.

mpls ip(InterfaceConfiguration)

Purpose Use this command to enable LDP label switching on the interface.Disable LDP label switching with the no form of this command.

Command Modes Interface configuration

Syntax mpls ip

no mpls ip

Defaults This command is disabled by default.

Instructions � This command enables LDP to exchange labels on the interfaceof layer 3. Once the command is configured, LSR starts to pe-riodically send hello messages on the interface. When packetsto the destination network obtain the outgoing label to somedestination network, the outgoing label will be added into thepackets and the packets will be forwarded from this interface.Note that this command will take effect only after mpls ip isconfigured in global configuration mode.

� The no form of this command make packets routed from thisinterface no more carry labels and cease the label switching onthe interface.

Example This example describes how to enable LDP on the interface fei_1/1.ZXR10(config)#mpls ipZXR10(config)#interface fei_1/1ZXR10(config-if)#mpls ip

RelatedCommands

show mpls interface

show mpls ldp discovery

mpls label rangePurpose Use this command to configure a label range for LDP. Restore de-

fault with the no form of this command.


Syntax mpls label range <min-label><max-label>

no mpls label range

SyntaxDescription

<min-label> Minimal available label, range: 16~1048575

<max-label> Maximal available label, range: 16~1048575



Example This example describes how to set the label range as 1000~10000.ZXR10(config)#mpls label range 1000 10000

RelatedCommands

show mpls label range

mpls ldp access-fecPurpose Use this command to control LDP’s creation of FEC for which des-

tination networks and make sure whether FEC can be created forrouting networks obtained by BGP; this command controls FECfilter policy. To disable this feature, use the no form of this com-mand.


Syntax mpls ldp access-fec {for <prefix-access-list>| host-route-only | bgp | force}

no mpls ldp access-fec [bgp]

SyntaxDescription

for <prefix-access-list>

Destination network to be filtered, basic ACL:1~99 and 1000~1499

host-route-only Creates FEC only for the destination network(host address) with 32-bit mask

bgp Creates FEC for the specified route networkobtained from BGP

force Takes effect immediatedly

Defaults LDP creates FEC for all destination networks except the route net-works obtained by BGP.

Instructions � By default, LDP creates FEC for all destination networks exceptthe route networks obtained by BGP. However, the number ofnetworks may be so large that it needs to filter the network forwhich FEC need not be created ; or the network administratorwants to control the creation of FEC , that is, FEC is createdonly for the authorized network. This command can realizesuch functions.

� The mpls ldp access-fec for <prefix-access-list> commandcan make filter be based on access list. FEC can be createdfor all destination addresses allowed by the access list. Onlystandard ACL is supported now.

� The mpls ldp access-fec host-route-only command makeFEC be created only for the destination address with 32-bitmask. The mpls ldp access-fec host-route-only commandis especially valid in the MPLS/BGP VPN application, becauseunder such application, LDP only exchanges the label of thenext-hop address (that is, the outer label, the label to the PE)of VPN routes. The mpls ldp access-fec host-route-onlycommand can effectively decrease the number of FECs.

� This command does not collide with the above two policies.By default, FEC is not created for route networks obtained by



BGP. This command can make FEC also be created for routenetworks obtained by BGP.

� Use thempls ldp access-fec command to configure policy butit does not take effect immediately. But The mpls ldp access-fec force command makes the configuration take effectimmediately.

Tip:

mpls ldp access-fec for <prefix-access-list> andmpls ldp access-fec host-route-only are mutually exclusive. Thus the networkadministrator can choose only one control policy at any time.

Example 1. This example describes how to configure the router to createFEC only for the destination address with 32-bit mask:ZXR10(config)#mpls ldp access-fec host-route-only

2. This example describes how to configure the router to createthe labels of networks 10.101.0.0 and 10.221.0.0 only andthey act immediately.ZXR10(config)#ip access-list standard 10ZXR10(config-std-nacl)#permit 10.101.0.0 0.0.255.255ZXR10(config-std-nacl)#permit 10.221.0.0 0.0.255.255ZXR10(config-std-nacl)#exitZXR10(config)#mpls ldp access-fec for 10

3. This example describes how to configure the router to createFEC for route networks obtained by BGP.ZXR10(config)#mpls ldp access-fec bgp

RelatedCommands

show mpls ldp binding

show running-config

mpls ldp advertise-labelsPurpose Use this command to control the distribution of locally assigned la-

bels (incoming labels) through LDP. This command controls whichdestination network segment labels are advertised to which neigh-bors. To disable this feature, use the no form of this command.


Syntax mpls ldp advertise-labels [for <prefix-access-list>[to <peer-access-list>]]

no mpls ldp advertise-labels [for <prefix-access-list>[to <peer-access-list>]]

SyntaxDescription


Destination network label to be advertised,basic ACL: 1~99 and 1000~1499

to <peer-access-list> Advertises which labels to which neighbors,basic ACL: 1~99 and 1000~1499



Defaults All labels are advertised to all neighbors by default.

Instructions The no mpls ldp advertise-labels command without any op-tional parameter forbids the distribution of any locally assignedlabels. To restore the distribution of all locally assigned labels, usethe mpls ldp advertise-labels command without any optionalparameter. Only standard ACL is supported now.

Up to 99mpls ldp advertise-labels commands can be executed,those commands work together to determine how LSR advertiseslocal labels. In the case that multiple commands are configured,the following rules should be followed:

1. Each mpls ldp advertise-labels command has a (prefix acl,peer acl) pair. The access list pair is (none, none) when no op-tional parameter is specified; and it is (prefix-acl, none) whenthe optional parameter is specified but without the keywordno.

2. There is only one (prefix acl, peer acl) pair “applied to” eachprefix in accordance with the following rules:

i. One (prefix acl, peer acl) pair “applies to” one prefix onlywhen prefix acl “matches” the prefix, and the match con-dition is that prefix acl permits the prefix.

ii. In the case that there is more than one (prefix acl, peeracl) pair “matching” a prefix; the first (prefix acl, peer acl)pair “applies to” the prefix (in the sequence configured inshow running-config).

3. When LSR is to advertise a prefix label, it executes the followingoperations:

i. Finds the (prefix acl, peer acl) pair “applied to” the prefix.

ii. In the case that there is no (prefix acl, peer acl) pair“applied to” the prefix, the label is not advertised to anyneighbor if the no mpls ldp advertise-labels commandis executed; otherwise, the label is advertised to all neigh-bors.

iii. In the case that one (prefix acl, peer acl) pair “applied to”the prefix, the label is not advertised to any neighbor ifprefix acl denies the prefix.

iv. If prefix acl permits the prefix and there is no peer acl(namely none), the label is advertised to all neighbors.

v. If prefix acl permits the prefix and there is one peer acl, thelabel is advertised to all neighbors permitted by peer acl.

Tip:

This command takes effect immediately after its configuration.The command can be configured only when the network in sta-ble status. Otherwidse, it could not take effect immediately. Donot use this command frequently.

Example 1. This example describes how to forbid the router from advertis-ing any label to any neighbor.ZXR10(config)#no mpls ldp advertise-labels



2. This example describes how to make the router advertise labelsof networks 10.101.0.0 and 10.221.0.0 to all neighbors.ZXR10(config)#ip access-list standard 10ZXR10(config-std-nacl)#permit 10.101.0.0 0.0.255.255ZXR10(config-std-nacl)#permit 10.221.0.0 0.0.255.255ZXR10(config-std-nacl)#exitZXR10(config)#mpls ldp advertise-labels for 10ZXR10(config)#no mpls ldp advertise-labels

3. This example describes how to make the router advertisethe 59.0.0.0 label to LSR 155.0.0.55 only and advertise the35.0.0.0 label to LSR 133.0.0.33 only.ZXR10(config)#ip access-list standard 10ZXR10(config-ext-nacl)#permit 59.0.0.0 0.255.255.255ZXR10(config-ext-nacl)#exitZXR10(config)#ip access-list standard 11ZXR10(config-ext-nacl)#permit 155.0.0.55 0.0.0.0ZXR10(config-ext-nacl)#exitZXR10(config)#ip access-list standard 20ZXR10(config-ext-nacl)#permit 35.0.0.0 0.255.255.255ZXR10(config-ext-nacl)#exitZXR10(config)#ip access-list standard 21ZXR10(config-ext-nacl)#permit 133.0.0.33 0.0.0.0ZXR10(config-ext-nacl)#exitZXR10(config)#mpls ldp advertise-labels for 10 to 11ZXR10(config)#mpls ldp advertise-labels for 20 to 21

RelatedCommands

mpls ldp advertise-labels old-style

mpls ldp advertise-labelsold-style

Purpose Use this command to allow the <prefix-access-list> argument af-ter the keyword for in the mpls ldp advertise-labels commandto be interpreted according to the earlier Cisco IOS software re-leases. To disable this feature, use the no form of this command.


Syntax mpls ldp advertise-labels old-style

no mpls ldp advertise-labels old-style

Defaults By default, ZXR10 interprets the parameter <prefix-access-list>after the keyword for according to the rule described in the in-struction of the mpls ldp advertise-labels command.

Instructions Generally, the parameter <prefix-access-list> after the keywordfor conforms to the following rules:

One (prefix acl, peer acl) pair “applies to” a prefix only when theprefix ACL “matches” the prefix, and the match condition is thatthe prefix ACL permits the prefix. This is the general processingmethod of access list.

In the early Cisco IOS version, however, the parameter <prefix-access-list> after the keyword for in thempls ldp advertise-labelscommand is interpreted in a different way as follows:

One (prefix acl, peer acl) pair “applies to” a prefix only when theprefix ACL “matches” the prefix, and the match condition is that



prefix ACL permits or denies the prefix explicitly. The parameterprefix ACL with “permit any” or “deny any” matches all prefixes.

The difference between the Cisco early rules and the general pro-cessing method of access list is that:

The explicit deny (including deny any) makes the (prefix acl, peeracl) pair “applied to” the prefix, while the implicit deny does nottake any effect.

If users are used to the early rule, thempls ldp advertise-labelsold-style command can be used.

Example This example describes how to configure the router to use the earlyrules of Cisco to interpret the parameter <prefix-access-list> afterthe keyword for in the mpls ldp advertise-labels command.ZXR10(config)#mpls ldp advertise-labels old-style

RelatedCommands

mpls ldp advertise-labels

mpls ldp backoffPurpose Use this command to configure the parameter of the LDP session

backoff reestablishment mechanism. To restore default, use theno form of this command.


Syntax mpls ldp backoff <initial-backoff><maximum-backoff>

no mpls ldp backoff

SyntaxDescription

<initial-backoff> Initial backoff time in seconds, range:10~65535, default: 15 seconds

<maximum-backoff> Maximum backoff time in seconds, range:10~65535, default: 120 seconds

Instructions � The LDP session backoff reestablishment mechanism preventstwo LSRs with incompatible configurations falling into the end-less cycle form the establishment of the session to the fail-ure. If the establishment of the session fails because of theincompatible configurations of the two LSRs, the two LSRs willput off their attempt to establish a session next time (namelyback off). The backoff time is exponentially increased until itreaches the maximum backoff.

� The default value of the parameter of the LDP session back-off reestablishment mechanism is defined by the LDP protocolspecifications. There is no need to change tyhe default config-uration until the default parameter indeed causes bad behav-iors.

Example This example describes how to set the initial backoff time as 30seconds and the maximum backoff time as 240 seconds.ZXR10(config)#mpls ldp backoff 30 240



RelatedCommands

show mpls ldp backoff

show mpls ldp parameters

mpls ldp bfdPurpose Use this command to configure the corresponding parameters of

LDP LSP BFD and trigger the bfd session for creating LSP.


Syntax mpls ldp bfd <FEC address><mask length> interval <interval>min_rx <min_rx> Multiplier <multiplier>

no mpls ldp bfd <FEC address><mask length> interval <interval> min_rx <min_rx> Multiplier <multiplier>

SyntaxDescription

<FEC address> Specifies the LSP address for creating bfd. Itis generally a remote address network

<mask length> Specifies the sub network mask length ofremote address. range: 1~32

<interval> Specifies the minimal sending interval, inmilliseconds. range: 50~999

<min_rx> Specifies the minimal receiving interval, inmilliseconds. range: 50~999

<multiplier> Specifies the multiplier when the detectionovertimes. range: 3~50

Instructions This command triggers the creation of LSP BFD, and specifies thenetwork address of LSP.

Example This example describes how to triggers the creation of BFD of LSP2.2.2.2.ZXR10(config)#mpls ldp bfd 2.2.2.2 32 interval 50min_rx 50 multiplier 3

RelatedCommands

show bfd nei ldp-lsp

mpls ldp dampeningPurpose Use this command to configure LDP to enable the route dampening

or modify the various LDP route dampening factors. Disable thiscommand by using no form of this command.


Syntax mpls ldp dampening [<half-life><reuse><suppress><max-suppress-time>]

no mpls ldp dampening



SyntaxDescription

<half-life> Time (in minutes) after which a penalty isdecreased by half after the half-life period(which is 15 minutes by default). The rangeof the half-life period is 1~45 minutes

<reuse> Reuse values based on accumulated penalties.If the penalty for a flapping route decreaseenough to fall below this value, the route isunsuppressed. range: 1~20000, default: 750

<suppress> A route is suppressed when its penaltyexceeds this limit. range: 1~20000, default:2000

<max-suppress-time>

Maximum time (in minutes) a route can besuppressed. range: 1~255, default: 60minutes


Instructions If there is no parameter after this command, the LDP route damp-ening will be valid with default values. The parameters have tobe configured together. If any one parameter is configured, thenother parameters have to be configured. The parameter <suppress> value should be larger than the <reuse> value.

Example This example describes how to enable LDP route dampening.ZXR10(config)#mpls ldp dampening

RelatedCommands

show running-config

mpls ldp dampening-aclPurpose Use this command to control which destination networks for which

LDP creates LDP dampening entities. configure the destinationnetworks for which the LDP creates the LDP dampening entity. Todisable this feature, use the no form of this command, and the noform of this command will take effect immediately.


Syntax mpls ldp dampening-acl {for <prefix-access-list>| force}

no mpls ldp dampening-acl

SyntaxDescription


Specifies which networks to be filtered. basicACL: 1~99 and 1000~1499

force Takes effect immediately

Defaults The filtering of flapping is valid only when the function of LDPdampening takes effect. By default, LDP records the dampeninginformation for flapping destination networks.

Instructions By default, LDP records the dampening information for flappingdestination networks. However, there are so many networks in



the actual network that it needs to filter the networks for whichthere is no need to record the dampening information.

The mpls ldp access-fec force command takes effect immedi-ately.

Example 1. This example describes how to record the dampening informa-tion for LSP of networks 10.101.0.0 and 10.221.0.0.ZXR10(config)#ip access-list standard num 10ZXR10(config-std-acl)#permit 10.101.0.0 0.0.255.255ZXR10(config-std-acl)#permit 10.221.0.0 0.0.255.255ZXR10(config-std-acl)#exitZXR10(config)#mpls ldp dampening-acl for 10ZXR10(config)#mpls ldp dampening-acl force

2. This example describes how to restore the default settings.ZXR10(config)#no mpls ldp dampening-aclZXR10(config)#mpls ldp dampening-acl force

RelatedCommands

show running-config

mpls ldp discovery helloPurpose Use this command to configure the interval for sending LDP hello

discovery messages and the timeout time of the discovered LDPneighbor between the directly connected LSRs. To restore default,use the no form of this command.


Syntax mpls ldp discovery hello {holdtime <holdtime>| interval <interval>}

no mpls ldp discovery hello {holdtime | interval}

SyntaxDescription

holdtime <holdtime> Holdtime (in seconds) of the status if theneighbor discovered by LDP can not receiveany subsequent hello messages, range:1~2147483, default: 15 seconds

interval <interval> Interval of LDP’s periodically sending hellomessages (in seconds), range: 1~2147483,default: 5 seconds

Example This example describes how to set the status holdtime as 100 sec-onds and the interval for sending hello messages as 20 seconds.ZXR10(config)#mpls ldp discovery hello holdtime 100ZXR10(config)#mpls ldp discovery hello interval 20



RelatedCommands

show mpls ldp parameter

mpls ldp discoverytargeted-hello

Purpose Use this command to configure the interval for sending LDP hellodiscovery messages and the timeout time of the discovered LDPneighbor between the indirectly connected LSRs. To restore de-fault, use the no form of this command.


Syntax mpls ldp discovery targeted-hello {holdtime <holdtime>|interval <interval>}

no mpls ldp discovery targeted-hello {holdtime | interval}

SyntaxDescription

holdtime <holdtime> Holdtime of the status if the neighbordiscovered by LDP can not receive anysubsequent hello messages (in seconds),range: 1~2147483, default: 45 seconds

interval <interval> Interval of LDP’s periodically sending hellomessages (in seconds), range: 1~2147483,default: 15 seconds

Instructions This command is supported after the platform version 4.6.02.

Example This example describes how to set the status holdtime as 100 sec-onds and the interval for sending hello messages as 20 seconds.ZXR10(config)#mpls ldp discovery targeted-hello holdtime 100ZXR10(config)#mpls ldp discovery targeted-hello interval 20

RelatedCommands

show mpls ldp parameter

mpls ldp discoverytransport-address

Purpose Use this command to configure the transmission address parame-ter carried in hello messages on the layer 3 interface. To disablethis feature, use the no form of this command.


Syntax mpls ldp discovery transport-address {interface |<ip-address>}

no mpls ldp discovery transport-address



SyntaxDescription

interface Specifies the interface address as thetransmission address advertised in the hellomessage

<ip-address> Specifies some address as the transmissionaddress advertised in the hello message

Defaults By default, ZXR10 takes the router identifier as the transmissionaddress advertised in the hello message on the frame interface.

Instructions A TCP connection must be established before an LDP session isset up between LDP routers, which requires every router know thepeer transmission address (IP address). The LDP discovery mech-anism enables the LDP router to advertise its own transmissionaddress used for establishing TCP connection to the peer.

The advertisement of the transmission address can be explicit (thatis, the transmission address appears in the hello message) or im-plicit (that is, there is no transmission address appearing in thehello message). The receiver of hello messages takes the sourceIP address of the hello message as the transmission address to setup TCP connection with the sender.

The mpls ldp discovery transport-address command providesa way to change the default behavior of the router. If the interfaceparameter is used, LDP advertises the IP address of the interface inthe hello message on the interface. If the <ip-address> parameteris used, the LDP advertises the designated IP address in the hellomessage on the interface.

If the configuration of the transmission address is changed duringthe precess of the running of the interface, ZXR10 router will deletethe current adjacency relationship on the interface. If there is noother adjacent relationship maintaining the session maintained bythe current adjacent relationship on the interface (multiple links donot exist), the session will be closed. The adjacency relationship(and the session) will be reestablished after a hello message isreceived from the peer.

Tip:

If there are multiple links between routers, these routers mustadvertise the same transmission address on the corresponding in-terfaces.

Example This example describes how to use the IP address of the interfaceas the transmission address on the interface oc3_2/1, and set thetransmission address as 145.22.0.56 on the interface oc3_4/1.ZXR10(config#)interface oc3_2/1ZXR10(config-if)#mpls ldp discovery transport-address interfaceZXR10(config)#interface oc3_4/1ZXR10(config-if)#mpls ldp discovery transport-address 145.22.0.56

RelatedCommands


show mpls ldp neighbor



mpls ldp egressPurpose Use this command to control LDP to allocate popup labels to the

designated indirectly connected destination networks (that is, theegress control policy). To disable this feature, use the no form ofthis command.


Syntax mpls ldp egress {for <prefix-access-list>| nexthop <nexthop-access-list>}

no mpls ldp egress {for | nexthop}

SyntaxDescription


Specifies which destination networks to whichpopup labels are allocated, range: 1~99

nexthop <nexthop-access-list>

Specifies the nexthop of the destinationnetworks, range: 1~99

Defaults By default, LDP allocates popup labels only to the directly con-nected networks and makes advertisements to the peer LSR.

Instructions By default, LDP allocates popup labels only to the directly con-nected networks and makes advertisements to the peer LSR. Fordestination networks not directly connected, LDP acquires the idlelabel from the label pool as the incoming label and chooses thelabel value in the mapping message sent by the next hop of theroute as the outgoing label.

If local router is an edge LSR and the router of nexthop may bea non-MPLS router, local LSR cannot bind the outgoing label, andthe received label packet be will discarded at the data layer be-cause there is no outgoing label according to the MPLS frameworkprotocol.

In this case, it is necessary to configure the egress control pol-icy to specify LDP to allocate popup labels to destination networksflowing out of MPLS network, and make advertises to the upstreamLSR. Thus upstream LSR will forward the traffic from the MPLS net-work in the form of IP packets (or explicitly popup label packets).

There are two kinds of control policies: based on destination net-work segment and based on next hop.

1. The egress control policy based on destination networks (mplsldp egress for <prefix-access-list>) directly specifies whichdestination where local LSR is terminated.

2. The egress control policy based on next hop (mpls ldp egressnexthop <nexthop-access-list>) specifies which neighborsare non-MPLS routers so that the traffic of these neighborsas next hops is the traffic out of MPLS. Local router allocatespopup labels for this traffic.

As long as a route meets either of the two policies, that is, thedestination prefix is permitted by <prefix-access-list> or the nexthop is permitted by <nexthop-access-list> , the LDP will allocatea popup label to it.

The policy takes effect only on the refreshed FECs after the config-uration and does not reallocate labels to the existing FECs. There-



fore, it is not recommended to configure this command when thesystem is running to avoid inconsistency.

Example 1. The router allocates popup labels to all subnet routes in net-works 10.101.0.0/16 and 10.221.0.0/16, and allocates popuplabels to all subnet routes in network 10.222.0.0/16 but not in10.222.1.0/24.ZXR10(config)#ip access-list standard 10ZXR10(config-std-nacl)#permit 10.101.0.0 0.0.255.255ZXR10(config-std-nacl)#permit 10.221.0.0 0.0.255.255ZXR10(config-std-nacl)#deny 10.222.1.0 0.0.0.255ZXR10(config-std-nacl)#permit 10.222.0.0 0.0.255.255ZXR10(config-std-nacl)#exitZXR10(config)#mpls ldp egress for 10

2. The router allocates popup labels to all destination networkswhose next hop are 100.1.1.3:ZXR10(config)#ip access-list standard 11ZXR10(config-std-nacl)#permit 100.1.1.3 0.0.0.0ZXR10(config-std-nacl)#exitZXR10(config)#mpls ldp egress nexthop 11

mpls ldp enableconnect-with-dod

Purpose Use this command to set the compatibility of the label advertise-ment mode. To disable this feature, use the no form of this com-mand.


Syntax mpls ldp enable connect-with-dod

no mpls ldp enable connect-with-dod

Instructions Use this command to make the router to interconnect with LSRadopting the DOD mode.

mpls ldp explicit-nullPurpose Use this command to make the router which is supposed to adver-

tise implicit null labels advertise explicit null labels. To disable thisfeature, use the no form of this command.


Syntax mpls ldp explicit-null [for <prefix-access-list>][to <peer-access-list>]

no mpls ldp explicit-null



SyntaxDescription


Specifies the prefix of the explicit null labelsreplacing implicit ones, range: 1~99

to <peer-access-list> Specifies which neighbors that the explicitnull labels replaces implicit ones is advertisedto, range: 1~99

Defaults By default, ZXR10 advertises directly connected networks to allneighbors by means of implicit null labels.

Instructions � By default, ZXR10 advertises directly connected networks toall neighbors by means of implicit null labels. The implicit nulllabel causes the Penultimate Hop Poping (PHP) router to makePHP. Sometimes, however, it is prohibited for the PHP router tomake such action so that the explicit null label is used in theoutgoing label forwarding packet.

� The mpls ldp explicit-null command enables the router toadvertise explicit null labels to the neighbors permitted by<peer-access-list> and the directly connected networks permittedby <prefix-access-list>. If the parameter <prefix-access-list>is not specified in the command, explicit null labels will be ad-vertised to all the directly connected networks; if the parame-ter <peer-access-list> is not specified in the command, explicitnull labels will be advertised to all neighbors.

� This command takes effect only to the label advertisementmessages after the configuration. If labels have been adver-tised before the policy is configured, and the matched networksand neighbors will not change unless the session is interruptedand reestablished. Therefore, it is not recommended to con-figure this command when the system is running to avoid in-consistency.

Example 1. This example describes how to make LDP advertise all directroutes by explicit null labels to all neighbors.ZXR10(config)#mpls ldp explicit-nul

2. This example describes how to advertise explicit null labels tothe directly connected network 137.5.0.0, and advertise im-plicit null labels to other directly connected networks.ZXR10(config)#mpls ldp explicit-null for 10ZXR10(config)#ip access-list standard 10ZXR10(config-std-nacl)#permit 137.5.0.0 0.0.255.255ZXR10(config-std-nacl)#deny anyZXR10(config-ext-nacl)#

mpls ldp graceful-restartPurpose Use this command to enable the router to support LDP Graceful

restart function.


Syntax mpls ldp graceful-restart [timer {max-recovery <interval>|neighbor-liveness <interval>}]



no mpls ldp graceful-restart [timer {max-recovery | neighbor-liveness}]

SyntaxDescription max-recovery

<interval>Maximum time for LSR to wait for the labelrecovery of the peer neighbor (in seconds), itneeds negotiation. range: 15~600, default:120 seconds

neighbor-liveness<interval>

Maximum time for LSR to wait for the LDPsession recovery (in seconds), it needsnegotiation. range: 5~300, default: 120seconds

Instructions � This command is supported after the platform version 4.6.03.

� By default, LDP does not support GR function. GR function istriggered by the corresponding configuration. But it needs LDPto reestablish neighbors or restart protocols to make this com-mand take effect, because the relevant parameters negotiatein the initialized messages.

Example This example describes how to enable the router to support LDPGR function. The value of neighbor- liveness is configured as 30seconds, and the value of max-recovery is configured as 40 sec-onds.ZXR10(config)#mpls ldp graceful-restartZXR10(config)#mpls ldp graceful-restart timer neighbor-liveness 30ZXR10(config)#mpls ldp graceful-restart timer max-recovery 40

RelatedCommands

show mpls ldp graceful-restart

show mpls ldp neighbor graceful-restart

mpls ldp holdtimePurpose Use this command to configure the holdtime for LDP sessions not

to receive any subsequent LDP messages. To restore default, usethe no form of this command.


Syntax mpls ldp holdtime <seconds>

no mpls ldp holdtime

SyntaxDescription

<seconds> Holdtime for LDP sessions not to receivesubsequent LDP messages (in seconds),range: 15~65535, default: 180 seconds

Instructions When a session is set up between two LSRs, the smaller value ofthe configured parameters of the two LSRs will be taken as thenegotiated holdtime.

Example This example describes how to set the holdtime as to 30 seconds.ZXR10(config)#mpls ldp holdtime 30



RelatedCommands


show mpls ldp parameters

mpls ldp neighbor passwordPurpose Use this command to configure MD5 key for LDP to establish a

TCP connection with a neighbor. To disable this feature, use theno form of this command.


Syntax mpls ldp neighbor <ip-address> password <password>

no mpls ldp neighbor <ip-address> password

SyntaxDescription

<ip-address> Address of the neighbor used in TCPconnection or router ID identifying theneighbor, in the dotted decimal format

password<password>

MD5 key used for establishing TCP connectionwith the neighbor, 3~80 characters

Defaults By default, there is no MD5 option in ZXR10 LDP session.

Instructions MD5 authentication can be introduced between LDP peers to au-thenticate each TCP section. To enable MD5 authentication, bothLSRs should be configured with authentication and use the samekey; otherwise, the session cannot be established.

If the key of the session with some neighbor is changed with thempls ldp neighbor command (including the no form of this com-mand), the current session is interrupted and a new session isestablished.

Example This example describes how to establish a session with a neighborwhose TCP connection address is 140.2.1.15 by using abcdefg asthe MD5 authentication key.ZXR10(config)#mpls ldp neighbor 140.2.1.15 password abcdefg

mpls ldp request-labelsPurpose Use this command to configure the prefix and downstream neigh-

bors for which LDP sends request messages. To disable this fea-ture, use the no form of this command.


Syntax mpls ldp request-labels for <prefix-access-list>

no mpls ldp request-labels

SyntaxDescription

<prefix-access-list> Prefix access list for the request message tobe sent, range: 1~99



Defaults By default, ZXR10 does not send any request messages.

Instructions � This command enables the router to send label request mes-sages for some prefixes. If the parameter <prefix-access-list>is configured, the router will send label request messages toits downstream router with the prefix permitted by the list.

� This command takes effect only on the FECs created after theconfiguration or those of the downstream LSRs discovered afterthe configuration. Therefore, it is not recommended to config-ure this command when the system is running to avoid incon-sistency.

Example This example describes how to configure the router to send labelrequest messages to the FEC in the network 10.1.1.0/16.ZXR10(config)#mpls ldp request-labels for 10ZXR10(config)#ip access-list standard 10ZXR10(config-ext-nacl)#permit 10.1.1.0 0.0.255.255ZXR10(config-ext-nacl)#exit

mpls ldp router-idPurpose Use this command to configure the LDP router identifier. To disable

this feature, use the no form of this command.


Syntax mpls ldp router-id <interface-name>[force]

no mpls ldp router-id [force]

SyntaxDescription

<interface-name> Specifies the IP address of an interface as therouter identifier of LDP (if the interface is inthe UP state)

force Immediately changes the router identifier

Defaults By default, the election rules of LDP router identifier on ZXR10 areas follows:

1. Firstly, if the mpls ldp router-id command is used to desig-nate the address of an interface as the router identifier, andthe interface has an IP address and it is in the UP state, theaddress of the interface will be used as the router identifier.

2. Secondly, if there are loopback interfaces configured with IPaddresses, the maximum IP address of the loopback interfacewill serve as the router identifier.

3. Lastly, among the IP addresses of interfaces configured with IPaddresses and in the UP state, the maximum one is selectedas the router identifier.

Instructions By default, the automatically elected router identifier may be un-available sometimes, for example, the routing protocol does notadvertise the IP address elected as the router identifier to neigh-bors. In addition, the router configuration may cause the LPDrouter identifier is uncertain, and this invalidates the neighbor’scontrol policy.



The mpls ldp router-id command specifies the IP address of aninterface as the router identifier. Note that the interface whose IPaddress serves as the router identifier must be in the UP state.

If the optional parameter force is not specified, the router iden-tifier specified by the mpls ldp router-id command will not takeeffect until the next router identifier election, and the router iden-tifier takes place in the following cases:

1. LDP restarts.2. The interface whose IP address serves as the current router ID

is shut down.3. The interface whose IP address is specified as the current

router ID is not configured with any address.

If the optional parameter force is specified, the effect of the mpls ldp router-id command depends on the current state of thespecified interface.

1. If the specified interface is in the UP state and its address is notthe current router identifier, the router will change the routeridentifier to the specified value, interrupt all the current ses-sions, release labels learned from the sessions, and terminatethe MPLS forwarding related with the bounding of these labels.

2. If the specified interface is in the DOWN state, the router willchange the router identifier to the specified value once the in-terface is in the UP state, interrupt all the current sessions,release labels learned from the sessions, and terminate theMPLS forwarding related with the bounding of these labels.

Example This example describes how to specify the IP address of the inter-face fei_1/1 as the router identifier.ZXR10(config)#mpls ldp router-id fei_1/1

Relatedcommands


mpls ldp stylePurpose Ue this command to adopt a new keepalive mechanism of LDP

sessions. Once a hello packet is received, reset the keepalive timeof the session this hello packet maintains.


Syntax mpls ldp style

no mpls ldp style

Instructions By default, ZXROS updates the keepalive timer of sessions when-ever it receives each LDP TCP packet. After the configuration ofthis command, the timer will be reset whenever each LDP PDUpacket (including TCP and UDP packets) is received.

Example This example describes how to enable the new keepalive mecha-nism of LDP sessions.ZXR10(config)#mpls ldp style



mpls ldp target-sessionPurpose Use this command to configure the address of the indirect remote

target session and establish the target session. To delete the ses-sion, use the no form of this command.


Syntax mpls ldp target-session <ip-address>

no mpls ldp target-session <ip-address>

SyntaxDescription

<ip-address> IP address or router identifier of the remoteneighbor


Example This example describes how to establish a target session with therouter whose router identifier is 1.1.1.1.ZXR10(config)#mpls ldp target-session 1.1.1.1

RelatedCommands


mpls xconnectPurpose Use this command to configure the address, VPWS identifier, and

tunnel number of the remote interface. The creation of VPWS istriggered between local interface and the remote interface. Deletethe VPWS with the no form of this command.


Syntax mpls xconnect <ip-address><vc-id>[tunnel <tunnel number>]

no mpls xconnect

SyntaxDescription

<ip-address> IP address of the remote interface or routeridentifier of the remote node

<vc-id> VPWS identifier, range: 1~4294967295

tunnel <tunnelnumber>

Tunnel number used for creating VPWS,range: 1~1024


� The vc-id must be unique among local nodes, and the corre-sponding interface of the remote node must be assigned withthe same vc-id. The unique PW identifier throughout the net-work is composed of the remote node address and the vd-id.

� If there is the tunnel parameter, MPLS labels are allocated bythe specified tunnel. If there is no tunnel parameter, MPLSlabels are allocated by LDP.



Example In this example, VPWS with vc-id 100 is established with the nodewhose router identifier is 1.1.1.1 on the interface fei_2/1.ZXR10(config#)interface fei_2/1ZXR10(config-if)#mpls xconnect 1.1.1.1 100

RelatedCommands

show mpls l2transport binding

show mpls forwarding-tablePurpose Use this command to check the label forwarding information data-

base.

Command Modes All modes

Syntax show mpls forwarding-table [<prefix>[{<mask>|<mask-len>}]]

SyntaxDescription

<prefix> Destination address prefix in the forwardinginformation database

<mask> Mask of destination address prefix

<mask-len> Mask length of destination address prefix, 1~ 32

Example This example describes how to show information about the currentneighbor .ZXR10(config)#show mpls forwarding-tableMpls Ldp Forwarding-table:InLabel OutLabel Dest Pfxlen Interface NextHop201 Pop tag 3.4.5.6 32 fei_1/1 101.1.1.2202 Pop tag 120.1.1.0 24 fei_1/1 101.1.1.2

ZXR10(config)#show mpls forwarding-table 120.1.1.0Mpls Ldp Forwarding-table:InLabel OutLabel Dest Pfxlen Interface NextHop202 Pop tag 120.1.1.0 24 fei_1/1 101.1.1.2

The displayed field descriptions are shown below.

Field Description

InLabel Incoming label

OutLabel Outgoing label

Dest Destination network or destination hostaddress

Pfxlen Prefix length

Interface Outgoing interface

NextHop Next hop



show mpls l2transportbinding

Purpose Use this command to check label binding information of L2 VPN.

Command Modes User EXEX and privileged EXEC

Syntax show mpls l2transport binding [<vc-id>|<ip-address>| local-label <local-label>| remote-label <remote-label>]

SyntaxDescription

<vc-id> VC identifier, range: 1~4294967295

<ip-address> Remote IP address bounded

local-label<local-label>

Locally assigned label, range: 0~1048575

remote-label<remote-label>

Remotely assigned label, range: 0~1048575


Example This example describes how to show the current L2 transport bind-ing information.ZXR10(config)#show mpls l2transport bindingDestination Address: 3.4.5.6, VC ID: 201Local Label: 16

Cbit: 0 VC Type: VLAN GroupID: 0MTU: 1500 Interface Desc: fei_1/2.1

Remote Label: 16Cbit: 0 VC Type: VLAN GroupID: 0MTU: 1500 Interface Desc: fei_5/5.1

Destination Address: 3.4.5.6, VC ID: 202Local Label: 17

Cbit: 0 VC Type: VLAN GroupID: 0MTU: 1500 Interface Desc: fei_1/2.2

Remote Label: 17Cbit: 0 VC Type: VLAN GroupID: 0MTU: 1500 Interface Desc: fei_5/5.2


Field Description

Destination Address Peer address

VC ID ID of VC

Local Label Locally assigned label

Cbit Flag of control field

VC Type Type of VC

GroupID Group ID information

MTU Maximum transmission unit



Field Description

Interface Desc Port information

Remote Label Remotely assigned label

show mpls l2transport vcPurpose Use this command to check the VC information transmitted at

Layer 2.


Syntax show mpls l2transport vc [{vcid <vcidmin>[<vcidmax>]|interface <interface-name>[<loca-lcircuit-id1>[<local-circuit-id2>]]| destination <ip-addr>}][detail]

SyntaxDescription

vcid Shows information based on vcid

<vcidmin> Lower limit of the designated vcid or thedesignated vcid range, it is must be specifiedif there is the parameter vcid specified.range: 1~4294967295

<vcidmax> Upper limit of the vcid show range,1~4294967295

interface <interfacename>

Name of the interface bounded with VPWS

<local circuit id1> Vlan ID for Ethernet, or vpi for the ATMinterface, range: 0~65535

<local circuit id2> Vlan ID for Ethernet, or vpi for the ATMinterface, range: 0~65535

destination<ip-addr>

VC destination address, in the dotted decimalformat

[detail] Detailed information of an entry


All the current VCs are displayed if there is no parameter specified.

This command is provided only on ZXR10 GER and ZXR10T64E/T128.

Example 1. This example describes how to show all the current VCs.ZXR10#show mpls l2transport vcLocalIntf LocalCircuit DestAddress VCID Statusfei_1/8.200 VlanID: 600 3.4.5.6 600 upfei_1/8.199 VlanID: 599 3.4.5.6 599 upfei_1/8.198 VlanID: 598 3.4.5.6 598 upfei_1/8.197 VlanID: 597 3.4.5.6 597 upfei_1/8.196 VlanID: 596 3.4.5.6 596 up

2. This example describes how to show VCs with VCID in the rangeof 201 to 205.ZXR10#show mpls l2transport vc vcid 201 205



LocalIntf LocalCircuit DestAddress VCID Statusfei_1/2.5 VlanID: 205 3.4.5.6 205 upfei_1/2.4 VlanID: 204 3.4.5.6 204 upfei_1/2.3 VlanID: 203 3.4.5.6 203 upfei_1/2.2 VlanID: 202 3.4.5.6 202 upfei_1/2.1 VlanID: 201 3.4.5.6 201 up

3. This example describes how to show VCs with destination ad-dress as 3.4.5.6.ZXR10#show mpls l2transport vc destintion 3.4.5.6LocalIntf LocalCircuit DestAddress VCID Statusfei_1/8.200 VlanID: 600 3.4.5.6 600 upfei_1/8.199 VlanID: 599 3.4.5.6 599 upfei_1/8.198 VlanID: 598 3.4.5.6 598 up

4. This example describes how to show detailed information ofthe VC with VCID as 201.ZXR10#show mpls l2transport vc vcid 201 detailLocalInterface: fei_1/2.1 up, lineProtocol up, localCircuitVlanID: 201 up

Destination address: 3.4.5.6, VC ID: 201, VC status: upTunnel label: imp-null, direct connected or TE tunnelOutput interface: fei_1/1 ,imposed label stack { 16 }Create time: 10:42:39, last status change time: 10:42:39Signalling protocol: LDP, peer 3.4.5.6:0 upMPLS VC labels: local 16, remote 16Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:fei_5/5.1

Sequencing: receive disabled, send disabled


Field Description

LocalIntf(LocalInter-face)

Local interface bounded with VPWS

LocalCircuit Link ID of local interface. It is displayedas ETHER; VlanID for the interfaceencapsulated with Ethernet; AAL5 vpi/vcifor the ATM interface encapsulated withAAL5; DCLI for the interface encapsulatedwith FR; or PPP for the interfaceencapsulated with ppp

DestAddress VC destination address (global next hopaddress)

VCID Designated VCID

Status VC current state: VC is up only when localinterface is up and resolves valid outertunnel label

Tunnel label Outer tunnel label, displayed as directconnection or RSVP-TE

Output interface Actual output interface

imposed label stack Label stack in the packet

Create time Time when VC is created

last status changetime

Period since VC changed recently



Field Description

Signalling protocol Signalling protocol for allocating VC labels

MPLS VC labels VC label

Group ID Group identifier

MTU Maximum transmission unit

Remote interfacedescription

Description of the remote interfacebounded with VPWS

Sequencing Sequencing function

show mpls label rangePurpose Use this command to show the label range that LDP can use.

Command Modes User EXEC and privileged EXEC

Syntax show mpls label range [detail]

SyntaxDescription

detail Shows detailed information of labels

Example This example shows the output of the show mpls label rangecommand.ZXR10#show mpls label range detailDownstream label pool: Min/Max label:16/1048575total 1048000 labels free now

The displayed field description is shown below.

Field Description

Downstream labelpool

Shows the configured minimal/maximalusable label value

RelatedCommands

mpls label range

show mpls ldp backoffPurpose Use this command to show the configuration of LDP session

backoff reestablishment parameters and the session in the backoffreestablishment state.


Syntax show mpls ldp backoff

Example This example shows the output of the show mpls ldp backoffcommand.ZXR10#show mpls ldp backoff



LDP initial/maximum backoff: 30/240 secLDP Id Backoff(sec) Waiting(sec)144.0.0.44:0 60 30155.0.0.55:0 120 90


Field Description

LDP initial/maximumbackoff

Shows backoff parameters of which the unitis second

LDP Id ID of LDP neighbor

Backoff(sec) Shows backoff time

Waiting(sec) Shows waiting time in the backoff state

RelatedCommands

mpls ldp backoff

show mpls ldp bindingsPurpose Use this command to show information about the binding of

learned LDP labels.


Syntax show mpls ldp bindings [<ip-address>{<net-mask>|<length>}[longer-prefixes]][local-label <label>[<label>]][remote-label <label>[<label>]][neighbor [<ip-address>]][detail]

show mpls ldp bindings summary

SyntaxDescription

<ip-address> IP address of the destination network, in thedotted decimal format


<length> Mask length, range: 0~32

longer-prefixes Shows the label bindings of the networkmatching the designated network but withlonger mask

local-label<label>[<label>]

Shows the entries matching the local labelvalue, and specifies the label range with theparameter label – label, range: 0~1048575

remote-label<label>[<label>]

Shows the entries matching the label valueallocated by neighbor with the label rangespecified by the parameter label – label,range: 0~1048575

summary Shows the summary of all entries anddownstream bindings in the LDP FEC table



Instructions This command shows all entries and downstream bindings in theLDP FEC table if there is no parameter specified.

Example 1. This example describes how to show all entries and down-stream bindings in the LDP FEC table.ZXR10#show mpls ldp bindings34.0.0.0/255.0.0.0local binding: label: imp-nullremote binding: lsr: 155.0.0.55:0, label: 17remote binding: lsr: 66.66.0.66:0, label: 18remote binding: lsr: 144.0.0.44:0, label: imp-null45.0.0.0/255.0.0.0local binding: label: 19remote binding: lsr: 155.0.0.55:0, label: imp-null inuseremote binding: lsr: 66.66.0.66:0, label: 16remote binding: lsr: 144.0.0.44:0, label: imp-null66.66.0.66/255.255.255.255local binding: label: 20remote binding: lsr: 155.0.0.55:0, label: 19remote binding: lsr: 66.66.0.66:0, label: imp-null(inuse)remote binding: lsr: 144.0.0.44:0, label: 18103.0.0.0/255.0.0.0local binding: label: imp-null155.0.0.55/255.255.255.255local binding: label: 25remote binding: lsr: 155.0.0.55:0, label: imp-null(inuse)remote binding: lsr: 144.0.0.44:0, label: 24remote binding: lsr: 66.66.0.66:0, label: 24

2. This example describes how to show label bindings of the net-work 166.0.0.0 and its subnets learned by the LSR 144.0.0.44.ZXR10#show mpls ldp bindings 166.0.0.0 8longer-prefixes neighbor 144.0.0.44166.44.0.0/255.255.0.0local binding: label: 29remote binding: lsr: 144.0.0.44:0, label: 25166.246.0.0/255.255.0.0local binding: label: 32remote binding: lsr: 144.0.0.44:0, label: 46


Field Description

a.b.c.d/a.b.c.d IP prefix and mask

local binding Local label binding

advertise to Advertises to neighbors

remote binding Label binding learned from neighbor

3. This example describes how to show the total number of entriesand downstream bindings in the LDP FEC table.ZXR10#show mpls ldp bindings summaryTotal number of prefixes: 17Total number of Upstream LSP Control Block: 51Total number of Downstream LSP Control Block: 45

Generic label binbingsassigned learnedprefixes in labels out labels17 17 14




Field Description

Total number ofprefixes

Total number of FECs discovered by LDProuting or created by downstream mapping

Total number ofUpstream LSPControl Block

Total number of upstream control blockscreated by LDP

Total number ofDownstream LSPControl Block

Total number of downstream control blockscreated by LDP

Generic labelbinbings

Universal label binding summary

Prefixes Total number of FECs exchanged hop byhop by LDP

Assigned in labels Number of incoming label prefixes assignedby LDP

Learned out labels Number of outgoing label prefixes learnedby LDP

show mpls ldp dampeningsummary

Purpose Use this command to show the suppressed LSP in the current LDPflapping routes.


Syntax show mpls ldp dampening summary [<ip-address><net-mask>]

SyntaxDescription

<ip-address> Network IP address related to the dampeninginformation, in the dotted decimal format


Instructionsinformation

If there is not any parameter after this command , all informationabout LSP in LDP flapping routes is displayed. If there is a parame-ter after this command, the dampening information of current LSPis displayed.

Example This example describes how to display information about LDP dis-covery.ZXR10#show mpls ldp dampening summaryDamp LSPS of ldp:status codes: d dampedInLable OutLable Network NH FromReuse Penaltyd 17 3 25.25.25.25/32 20.1.1.25 25.25.25.25:000:00:01 1729




Field Description

d The LSP is suppressed

InLable Ingress label

OutLable Egress Label

Network NetworkIP address and mask length of LSP

From LDP Router identifier of the remote neighbor

Reuse Time from the last time to receiving packetsto now

Penalty Penalty value. Values of LSP reuse andsuppression are decided by this value

show mpls ldp flap-statisticssummary

Purpose Use this command to show dampening information of LSP in LDPflapping routes.


Syntax show mpls ldp flap-statistics summary [<ip-address><net-mask>]

SyntaxDescription

<ip-address> Ntwork IP address related to dampeninginformation, in the dotted decimal format


Instructions If there is not any parameter after this command, all informationabout LSP in LDP flapping routes is displayed. If there is a param-eter after this command, dampening information of current LSP isdispalyed.

Example This example describes how to show information about LDP .ZXR10#show mpls ldp flap-statistics summaryFlap LSPS of ldp: 2status codes: d damped , * valid, h history.

InLable OutLable Network NH From Flaps DurationReuse Penaltyd 17 3 25.25.25.25/32 20.1.1.25 25.25.25.25:0 2 00:00:1300:00:58 2638


Field Description

d, *, h d implies this LSP is suppressed now. *implies the current lsp exists in history linklist, and LDP is valid. h implies the current lspexists in history link list, and ldp is invalid



Field Description

InLable Ingress label

OutLable Egress Label

Network Network IP address and mask length of LSP

NH Next hop address

From LDP Router identifier of the remote neighbor

Flaps Flapping time of current lsp

Duration Time from the first time to drop packets untilnow

Reuse Time from the last time to receive packetsuntil now

Penalty Penalty value, values of LSP reuse andsuppression are decided by this value

show mpls ldp discoveryPurpose Use this command to show information about LDP discovery .


Syntax show mpls ldp discovery [detail]

SyntaxDescription

detail Shows the detailed information of thediscovered neighbor

Example This example describes how to show information about LDP dis-covery .ZXR10#show mpls ldp discoveryLocal LDP Identifier:

95.95.95.95:0Discovery Sources:

Interfaces:fei_5/1 (ldp): xmit/recv

LDP Id: 93.93.93.93:0; IP addr: 95.93.5.93fei_6/1 (ldp): xmit/recv

LDP Id: 98.98.98.98:0; IP addr: 95.98.6.98


Field Description

Local LDP Identifier Local LDP identifier

Interface List of interfaces acting the LDP discovery

Xmit Indicates that the interface is sending hellomessage

Recv Indicates that the interface is receiving hellomessage



Field Description

Src IP addr Source address of hello messages sent fromneighbors

Transport IP addr Transmission address of the TCP connectionindicated by neighbor

IP addr Transmission address of the TCP connectionindicated by neighbor

show mpls interfacePurpose Use this command to show the interface on which LDP is enabled.


Syntax show mpls interface [<interface-name>]

SyntaxDescription

<interface-name> Interface name

Instructions If there is no parameter after this command , it shows completeinformation of the interface where LDP is enabled.

Example This example describes how to show information about the inter-face where LDP is enabled.ZXR10#show mpls interfacesInterface IP Tunnel Operationalfei_1/1 Yes(ldp) No Nofei_1/2 Yes(ldp) No Nofei_1/3 Yes(ldp) No YesPOS3_2/0 Yes(ldp) No No


Field Description

Interface Interface name

IP “Yes” indicates to support MPLS hop-by-hoplabel switching

Tunnel Reserved version to be upgraded

Operational Interface state

show mpls ldp neighborPurpose Use this command to show information about LDP sessions.


Syntax show mpls ldp neighbor [<neighbor>|<interface-name>][detail]



SyntaxDescription

<neighbor> IP address of the neighbor, in the dotteddecimal format

<interface-name> Interface name, shows neighbors acceptedfrom the designated interface

detail Shows detailed information

Example 1. This example describes how to show detailed information aboutan LDP session.ZXR10#show mpls ldp neighbor detailPeer LDP Ident: 172.1.1.1:0; Local LDP Ident 200.1.1.1:0TCP connection: 204.1.1.100.1025 - 200.1.1.1.646State: Oper; Msgs sent/rcvd: 257/222; DownstreamUp time: 01:09:15LDP discovery sources:fei_1/1; Src IP addr: 204.1.1.100holdtime: 15000 ms, hello interval: 5000 msfei_1/2; Src IP addr: 196.1.1.100holdtime: 15000 ms, hello interval: 5000 msAddresses bound to peer LDP Ident:196.1.1.100 204.1.1.100 180.1.1.100Peer holdtime: 60000 ms; KA interval: 20000 ms……ZXR10#show mpls ldp neighbor fei_1/1Peer LDP Ident: 172.1.1.1:0; Local LDP Ident 200.1.1.1:0TCP connection: 204.1.1.100.1025 - 200.1.1.1.646State: Oper; Msgs sent/rcvd: 262/226; DownstreamUp time: 01:10:35LDP discovery sources:fei_1/1, Src IP addr: 204.1.1.100fei_1/2, Src IP addr: 196.1.1.100Addresses bound to peer LDP Ident:196.1.1.100 204.1.1.100 180.1.1.100

2. This example describes how to show neighbors accepted fromthe interface fei_1/1.ZXR10#show mpls ldp neighbor fei_1/1Peer LDP Ident: 172.1.1.1:0; Local LDP Ident 200.1.1.1:0TCP connection: 204.1.1.100.1025 - 200.1.1.1.646State: Oper; Msgs sent/rcvd: 262/226; DownstreamUp time: 01:10:35LDP discovery sources:fei_1/1, Src IP addr: 204.1.1.100fei_1/2, Src IP addr: 196.1.1.100Addresses bound to peer LDP Ident:196.1.1.100 204.1.1.100 180.1.1.100


Field Description

Peer LDP Ident LDP identifier of the session of the neigbor

Local LDP Ident LDP identifier of the session of local router

TCP connection TCP connection that supports the session

State Session state

Msgs sent/rcvd Number of LDP messages received andsent through the session



Field Description

Downstream Indicates the session is in the downstreamautonomous label distribution control mode

Downstream ondemand

Indicates the session in the downstreamlabel distribution on demand control mode

Up time Period when the session is in the currentstate

LDP discoverysources

Adjacent relationship list maintaining thesession

interface Interface where the adjacency relation iscreated

Src IP addr Source IP address of peer hello messageswhich establish the adjacency relationship

holdtime Holdtime when the adjacency relationshipdoes not receive hello messages

hello interval Interval for sending hello messagesnegotiated in the adjacency relationship

Addresses bound topeer LDP Ident

IP addresses of all interfaces advertisedin the session by the neighbor. These IPaddresses may be the next hop of the localrouting entry

Peer holdtime Holdtime when the neighbor does notreceive LDP messages

KA interval Interval for sending keepalive messages

show mpls ldpgraceful-restart

Purpose Use this command to examine the current configuration informa-tion of LDP Graceful Restart.


Syntax show mpls ldp graceful-restart


Example This example describes how to show the current configuration in-formation of LDP GR.ZXR10#show mpls ldp graceful-restartLDP Graceful Restart is enabledNeighbor Liveness Timer: 30 secondsMax Recovery Timer: 40 secondsGraceful Restart-enabled Sessions:




Field Description

LDP Graceful Restartis enabled

Route has been configured with LDP GR

Neighbor LivenessTimer

Time interval of Neighbor Liveness Timer

Max Recovery Timer Time interval of Max Recovery Timer

Graceful Restart-enabled Sessions

Show the current GR process

show mpls ldp parametersPurpose Use this command to show information about current parameters

of LDP.


Syntax show mpls ldp parameters

Example This example describes how to show the current parameter infor-mation about LDP.ZXR10#show mpls ldp parameters Protocol version: 1Downstream label pool: min label: 16; max label: 100000 Sessionhold time: 180 sec; keep alive interval: 60 sec Discoveryhello: holdtime: 15 sec; interval: 5 sec Downstream onDemand max hop count: 255 LDP initial/maximum backoff: 15/120sec LDP loop detection: off


Field Description

Protocol version Version

Downstream labelpool

Label pool information

Session hold time Holdtime of the session

keep alive interval Interval for sending keepalive messages

Discovery hello Setting of basic discovery parameters

Downstream onDemand max hopcount

Reserved version upgrading

LDP initial/maximumbackoff

Setting of parameters for the LDP sessionbackoff reestablishment mechanism

LDP loop detection Reserved version upgrading


C h a p t e r 3

MPLS BGP VPNConfiguration

Table of Contentsdescription .......................................................................43export map.......................................................................44import map ......................................................................44ip vrf ...............................................................................45ip vrf forwarding................................................................45maximum routes ...............................................................46monitor session.................................................................46monitor session destination ................................................47monitor session source.......................................................47rd....................................................................................47route-target......................................................................48show ip protocol routing vrf ................................................48show ip protocol routing vrf-summary ..................................49show ip route mng.............................................................49show ip route vpn..............................................................49show ip route vrf ...............................................................50show ip route vrf-summary.................................................50show ip vrf .......................................................................50show monitor session.........................................................51tunnel checksum ...............................................................51tunnel destination..............................................................52tunnel key ........................................................................52tunnel mode .....................................................................52tunnel sequence................................................................53tunnel source....................................................................53

descriptionPurpose Use this command to set the description about a VRF. Delete the

description with the no form of this command.

Command Modes VRF configuration

Syntax description <string>

no description

SyntaxDescription

<string> Description about the VRF, a string of 1~16characters



Defaults There is no description by default.

Example This example describes how to set the description about the VPNnamed zte as ZTE-VPN.ZXR10(config)#ip vrf zteZXR10(config-vrf)#description zte-vpn

export mapPurpose Use this command to set the export route map related to the VRF.

Delete the configuration with the no form of this command.


Syntax export map <map-tag>

no export map <map-tag>

SyntaxDescription <map-tag> Name of the route map, a string of 1~16

characters

Defaults There is no route map related to the VRF by default.

Example This example describes how to set export route map related to theVPN named zte. The name of the route map is outmap.ZXR10(config)#ip vrf zteZXR10(config-vrf)#export map outmap

RelatedCommands

import map

import mapPurpose Use this command to set the import route map related to a VRF.

Delete the configuration with the no form of this command.


Syntax import map <map-tag>

no import map <map-tag>

SyntaxDescription <map-tag> Name of the route map, a string of 1~16

characters

Defaults There is no route map related to the VRF by default.

Example This example describes how to set the import route map relatedto the VPN named zte. The name of the route map is inmap.ZXR10(config)#ip vrf zteZXR10(config-vrf)#import map inmap


Chapter 3 MPLS BGP VPN Configuration

RelatedCommands

export map

ip vrfPurpose Use this command to configure a VPN instance (VRF). Delete the

VRF with the no form of this command.


Syntax ip vrf <vrf-name>

no ip vrf <vrf-name>

SyntaxDescription

<vrf-name> NRF name, a string of 1~16 characters

Instructions � The name is only locally valid and it is used when some inter-face is bounded with the VPN.

� Enter the VRF configuration mode after the command is exe-cuted successfully.

Example This example describes how to configure a VPN named zte.ZXR10(config)#ip vrf zteZXR10(config-vrf)#

ip vrf forwardingPurpose Use this command to associate an interface with a VRF. Cancel the

association with the no form of this command.


Syntax ip vrf forwarding <vrf-name>

no ip vrf forwarding

SyntaxDescription

<vrf-name> VRF name, a string of 1~16 characters

Defaults The interface is associated with the global routing table by default.

Instructions The original IP address of the interface where this command isused is deleted, it needs reconfiguring.

Example This example describes how to associate the interface Loopback1with the VPN named zte.ZXR10(config)#interface loopback1ZXR10(config-if)#ip vrf forwarding zte

RelatedCommands

ip vrf

rd



maximum routesPurpose Use this command to control the number of routes entering VRF

and give the related alarm.


Syntax maximum routes limit {warn threshold | warn-only}

no maximum routes

SyntaxDescription

limit Maximum number of routes allowed, range:1-42949672955

warn threshold Warn threshold in percent format, range:1~100

warn-only Only gives a warning message if the maximumupper limit is exceeded

Defaults None

Instructions This command is supported after the platform version 4. 8.21.

If it is the first time to configure this command, it needs configuringwith VRF instances.

Example 1. This example describes how to set the maximum number ofroutes entering VRF as 1000. An alarm will appear when theroutes exceed 75% of the maximum upper limit.ZXR10(config)#ip vrf zteZXR10(config-vrf)#Maximum routes 1000 75

2. This example describes how to set the maximum number ofroutes entering VRF as 1000. An alarm will appear when routesexceed the maximum upper limit.ZXR10(config)#ip vrf zteZXR10(config-vrf)#Maximum routes 1000 warning-only

RelatedCommands

show ip vrf detail

monitor sessionPurpose Use this command to configure port monitor session. Delete the

session with the no form of this command.


Syntax monitor session <number>

no monitor session <number>

SyntaxDescription

<number> Port monitor session number, range: 1~8

Instructions Only switches support port monitor configuration. Because ZXR105900 only support one session temporarily, this command doesnot make sense for ZXR10 5900 and it has been deleted.



monitor session destinationPurpose Use this command to add destination monitor ports into sessions.


Syntax monitor session <number> destination

no monitor session

SyntaxDescription


monitor session sourcePurpose Use this command to add source monitor port into session.


Syntax monitor session <number> source direction {both | cpu-rx |cpu-tx | rx | tx}

no monitor session

SyntaxDescription


both Direction of the traffic collecting is bidirectional

cpu-rx Direction of the traffic collecting is to CPU

cpu-tx Direction of the traffic collecting is from CPU

rx The direction of traffic collecting is receiving

tx The direction of traffic collecting is sending

rdPurpose Use this command to configure a route distinguisher (RD) for the

VRF.


Syntax rd <route-distinguisher>

SyntaxDescription

<route-distinguisher> Route distinguisher of the VRF, in twoformats: <1~65535>:<0~4294967295> orA.B.C.D:<0~65535>

Defaults There is no route distinguisher by default.

Instructions The VRF does not take effect until the route distinguisher is con-figured.

Examples This example describes how to configure an route distinguisher forthe VPN named zte.



ZXR10(config)#ip vrf zteZXR10(config-vrf)#rd 1:1

route-targetPurpose Use this command to create route-target extended community at-

tribute related to the VRF. Delete the attribute with the no com-mand.


Syntax route-target [import | export | both]<extended-community>

no route-target [import | export | both][<extended-community>]

SyntaxDescription

import Imports routes to the VRF according to theroute-target extended community attribute

export Exports VRF routes carrying the route-targetextended community attribute

both Configures the parameters import andexport at the same time

<extended-community>

Route-target extended commun-ity attribute, in two formats:<1~65535>:<0~4294967295> orA.B.C.D:<0~65535>

Defaults There is no route-target extended community attribute related tothe VRF by default.

Example This example describes how to configure the route-target extendedcommunity attribute for the VPN named zte.ZXR10(config)#ip vrf zteZXR10(config-vrf)#route-target import 1:1ZXR10(config-vrf)#route-target export 1:1

show ip protocol routing vrfPurpose Use this command to show information about the corresponding

VRF protocol routing table (incoming and outgoing labels).


Syntax show ip protocol routing vrf <vrf-name>[network <ip-address>[mask <net-mask>]]



SyntaxDescription


network <ip-address>

Network number, in the dotted decimal format

mask <net-mask> Network mask, in the dotted decimal format

Instructions If the network number parameter is used, the networks matchingthe parameter in the protocol routing table will be displayed. Ifthe network number and network mask parameters are used, theprotocol routes matching the address/mask will be displayed.

show ip protocol routingvrf-summary

Purpose Use this command to show the total number of the correspondingVRF routing tables.


Syntax show ip protocol routing vrf-summary <vrf-name>

SyntaxDescription


show ip route mngPurpose Use this command to show the route information of management

ports.


Syntax show ip route mng

Example This example describes how to show the route information of man-agement ports.ZXR10#show ip route mng

show ip route vpnPurpose Use this command to show the route information of VPN instances.


Syntax show ip route vpn

Example This example describes how to show the route information of allVPN instances.



ZXR10#show ip route vpn

show ip route vrfPurpose Use this command to show the VRF route information.


Syntax show ip route vrf <vrf-name>[network <ip-address>[mask<net-mask>]]

SyntaxDescription


network <ip-address>

Network IP address, in the dotted decimalformat

mask <net-mask> Subnet mask, in the dotted decimal format

Example This example describes how to show the route information of theVRF named zte.ZXR10#show ip route vrf zte

show ip route vrf-summaryPurpose Use this command to show the total number of VRF routes.


Syntax show ip route vrf-summary <vrf-name>

SyntaxDescription


Example This example describes how to show the total number of routes inthe VRF named zte.ZXR10#show ip route vrf-summary zte

show ip vrfPurpose Use this command to show the VRF configuration information.


Syntax show ip vrf [brief | detail | interfaces | summary][<vrf-name>]



SyntaxDescription

brief Shows the brief VRF information and relatedinterfaces

detail Shows the detailed VRF information andrelated interfaces

interfaces Shows the detailed information of interfacesassociated with the VRF

summary Displays the current VPN total number andthe maximum configured VPN number on therack

<vrf-name> Shows the detailed information of interfacesassociated with the VRF

Example This example describes how to show the detailed configuration in-formation of all the VRFs.ZXR10#show ip vrf detail

show monitor sessionPurpose Use this command to show the content of monitor session entry.


Syntax show monitor session <number>

SyntaxDescription


tunnel checksumPurpose Use this command to configure local GRE tunnel to enable the tun-

nel checksum option. Cancel the configuration with the no formof this command.


Syntax tunnel checksum

no tunnel checksum

Example This example describes how to configure local GRE tunnel to enablethe tunnel checksum option.ZXR10(config)#interface fei_5/1ZXR10(config-if)#tunnel checksum



tunnel destinationPurpose Use this command to configure a destination address for the tun-

nel. Cancel the configuration with the no form of this command.


Syntax tunnel destination {ipv4 | ipv6}<ip-address>

no tunnel destination

SyntaxDescription

<ip-address> Destination IP address or IPv6 address of thetunnel

Example This example sets the destination address of the tunnel as10.10.10.2:ZXR10(config)#interface fei_7/1ZXR10(config-if)#tunnel destination ipv4 10.10.10.2

History command tunnel source <ip-address>

This command is expressed before the platform version V4.6.01.The keywords IPv4 and IPv6 are provided after the platform ver-sion V4.6.01.

tunnel keyPurpose Use this command to configure local GRE tunnel to enable the key

option and configure a key. Cancel the configuration with the noform of this command.


Syntax tunnel key <key>

no tunnel key

SyntaxDescription

<key> Tunnel key, range: 0~4294967295

tunnel modePurpose Use this command to configure the tunnel mode. Cancel the con-

figuration with the no form of this command.


Syntax tunnel mode {gre ip | mpls traffic-eng | ipv6ip [6to4]|ipipv6}

no tunnel mode



SyntaxDescription

gre ip Configures the tunnel as GRE tunnel

mpls traffic-eng Configures the tunnel as mpls traffic enginetunnel

ipv6ip Configures the tunnel as ipv6 over ip tunnel(provided only in the project supporting IPv6)

ipv6ip 6to4 Configures the tunnel as 6to4 tunnel(provided only in the project supporting IPv6)

ipipv6 Configures the tunnel as 4in6 tunnel (providedonly in the project supporting IPv6)

Instructions ZXR10 5900 series support 6in4 and 6to4 tunnels only. The othertypes of routers and switches supports all of kinds of tunnels.

Example This example describes how to configure the tunnel as GRE tunnel.ZXR10(config)#interface fei_7/1ZXR10(config-if)#tunnel mode gre ip

tunnel sequencePurpose Use this command to configure local GRE tunnel to enable the tun-

nel sequence option. Cancel the configuration with the no form ofthis command.


Syntax tunnel sequence

no tunnel sequence

tunnel sourcePurpose Use this command to configure the source address for the tunnel.

Cancel the configuration with the no form of this command.


Syntax tunnel source {ipv4 | ipv6}<ip-address>

no tunnel source

SyntaxDescription

<ip-address> Source IP address or IPv6 address of thetunnel

Example This example describes how to set the source address of the tunnelas 10.10.10.1.ZXR10(config)#interface fei_2/1 ZXR10(config-if)#tunnelsource ipv4 10.10.10.1

History Command tunnel source <ip-address>



This command is expressed before the platform version v4.6.01.The keywords ipv4 and ipv6 are provided after the platform ver-sion v4.6.01.


C h a p t e r 4

VPLS Configuration

Table of Contentsclear flowstat vpls..............................................................55clear flowstat vpws ............................................................56clear mac-table vfi.............................................................56peer ................................................................................57pwtype ............................................................................58show mac-filter .................................................................59show mac-table.................................................................59show mpls l2transport vc vpls .............................................60show mpls l2transport vpn summary....................................62show vfi ...........................................................................62show vfi brief ....................................................................63stp-tunnel enable ..............................................................64vcid .................................................................................64vpls apply-mac-filter ..........................................................65vfi ...................................................................................66vfi mspw ..........................................................................66vpls mac-filter...................................................................67vlan range ........................................................................68xconnect vfi......................................................................68

clear flowstat vplsPurpose Use this command to clear the flow statistics information to which

VPLS corresponds.


Syntax clear flowstat vpls [vfi <vfi-name>]

clear flowstat vpls

SyntaxDescription

<vfi-name> VFI name that VPLS example(to clear flowstatistic) corresponds to

Instructions Clera VPLS flow statistics information by force.

Only ZXR10 6900 and ZXR10 8900 support this command.

Example This example describes how to clear vfi1 and all vfi flow.ZXR10#clear flowstat vpls vfi vfi1ZXR10#clear flowstat vpls



RelatedCommands

show mac-table

clear flowstat vpwsPurpose Use this command to clear the flow statistics information to which

VPWS corresponds.


Syntax clear flowstat vpws vcid <vcid>

clear flowstat vpws vlanid <vlan-id>

SyntaxDescription

<vcid> Vcid that VPWS corresponds to

<vlan-id> Vlan-id that VPWS corresponds to

Instructions Clera VPWS flow statistics information by force.

Only ZXR10 6900 and ZXR10 8900 support this command.

Example This example describes how to clear VPWS flow statistics.ZXR10#clear flowstat vpws vcid 2ZXR10#clear flowstat vpws vlanid 2

RelatedCommands

show mac-table

clear mac-table vfiPurpose Use this command to clear the MAC address table of the specified

virtual private LAN service (VPLS).


Syntax clear mac-table vfi <vfi-name>

SyntaxDescription

<vfi-name> Corresponding VFI name of the VPLS instanceof the MAC address to be cleared

Instructions � Use this command to force to clear the MAC address forwardingtable of the VPLS instead of clear the MAC address by aging it.

� This command is provided only for ZXR10 GER and ZXR10T64E/T128.

Example This example describes how to clear the MAC address table of vfi1.ZXR10#clear mac-table vfi vfi1


Chapter 4 VPLS Configuration

RelatedCommands

show mac-table

peerPurpose Use this command to specify the addresses of other PEs in the

same VPLS domain and establish pseudo-wires. Delete the estab-lished pseudo-wires with the no form of this command.

Use this command to configure a pair of addresses of other PEsand the vcid in a static multi-hop pseudo-wire S-PE instance, andestablish pseudo-wires. Delete the established pseudo-wires withthe no form of this command.

Command Modes VFI configuration and CFI MSPW configuration

Syntax For VFI configuration mode,

peer <peer-ip-address>[spoke][tunnel <tunnel-number>]

no peer <peer-ip-address>

For VFI MSPW configuration mode,

peer <peer-ip-address> vcid <vcid>

no peer <peer-ip-address>

SyntaxDescription

<peer-ip-address> IP address of the peer PE, in general it is therouter identifier

spoke If the optional parameter spoke is specified,the type of pseudo-wire is spoke; otherwise,it is hub

<tunnel-number> Tunnel number used for establishing VPLS,range: 1~1024

<vcid> Different VPLS instances of the same PE has adifferent vcid, VPLS instances with the samevcid of the different PEs belongs to the sameVPLS, range: 1~4294967294

Defaults The default peer type is “hub” in VFI configuration mode.

The default peer type is “spoke” in VFI MSPW configuration mode.

Instructions This command is supported after the platform version 4.6.02. Thiscommand is supported to be configured under vfi mspw configu-ration mode after the platform version 4.8.20.

The current solution does not support the VPLS automatic discov-ery mechanism, thus it is necessary to specify all PE addresses inthe same VPLS. This command uses the parameters specified inthe vcid and pwtype commands to establish a pseudo-wire withthe designated PE. The spoke type is used for VPLS hierarchy andcross-domain.

Example 1. This example describes how to execute the peer command inVFI configuration mode on the PE.ZXR10(config)#vfi vfi1



ZXR10(config-vfi)#peer 4.4.4.4

2. This example describes how to execute the peer command inVFI MSPW configuration mode on the PE.ZXR10(config)#vfi mspw vfi1ZXR10(config-vfi-mspw)#peer 4.4.4.4 vcid 40

RelatedCommands

vfi

vcid

pwtype

vfi mspw

pwtypePurpose Use this command to specify the type of a pseudo-wire established

by the VPLS instance.

Use this command to specify the type of a pseudo-wire in a staticmulti-hop pseudo-wire S-PE configuration instance.

Command Modes] VFI configuration or VFI MSPW configuration

Syntax pwtype {ethernet | ethernet-vlan}

SyntaxDescription

ethernet |ethernet-vlan

Pseudo-wire type: Ethernet or Ethernet-vlan


When a pseudo-wire is established between two PEs, there mustbe the negotiation about the type of the pseudo-wire established.There are two types of the pseudo-wire in VPLS: Ethernet andEthernet-vlan. The establishment of a pseudo-wire will fail if thepseudo-wire types designated by PEs are different.

The two pseudo-wire types correspond to two ways for providingthe VPLS service. If the pseudo-wire type is Ethernet, the VPLSservice is provided in the transparent mode. That is, the PE directlyforwards the user data without checking or processing the vlantag of the user data. In this case, the the vlan tag is regardedas the distinguisher for the user to manage private networks. Inthis mode, the input interface offered to the user must be the realinterface.

If the pw type is Ethernet-vlan, the VPLS service is provided inthe rewrite mode. That is, the ingress PE router peels off the vlantag in the user data and then forwards the pseudo-wire , while theegress PE attaches the corresponding vlan tag to the user dataaccording to the outgoing interface type and then forwards it tothe user.

Example 1. This example describes how to configure the pseudo-wire typein VFI configuration mode on the PE.ZXR10(config)#vfi vfi1ZXR10(config-vfi)#pwtype Ethernet



2. This example describes how to configure the pseudo-wire typein VFI MSPW configuration mode on the PE.ZXR10(config)#vfi vfi1ZXR10(config-vfi-mspw)#pwtype mspw ethernet

RelatedCommands

vfi

vcid

peer

no peer

show mac-filterPurpose Use this command to show detailed information about the filtering

of some VPLS MAC .


Syntax show mac-filter <rule_number>

SyntaxDescription

<rule_number> Rule number for MAC filtering, range: 0~127

Instructions This command is supported by ZXR10 T64E/T128.

Example This example describes how to show detaiedl information aboutthe filtering of some VPLS MAC .ZXR10(config)#show mac-filter 1RuleNo FilterNo MAC_Bottom MAC_Top1 1 0001.0002.0003 0001.0002.00031 0 0002.0003.0004 0002.0003.00061 2 0003.0004.0005 0003.0004.0007


Field Description

RuleNo Filter rule number

FilterNo Filter rule entry number

MAC_Bottom Filter rule entry number

MAC_Top Maximum MAC address to be filtered

show mac-tablePurpose Use this command to show the MAC table of a VPLS instance.


Syntax show mac-table <vfi-name>



SyntaxDescription

<vfi-name> Name of the Virtual Forwarding Instance (VFI)in the VPLS

Instructions This command is provided only for ZXR10 GER and ZXR10T64E/T128.

Example This example describes how to show the MAC table of the vfi1.ZXR10#show mac-table vfi1MAC peer-address outIntLab outExtLab outInterface type0000.0000.2009 Local NULL NULL fei_7/8 dynamic0000.0000.3005 1.1.1.1 16 3 fei_7/5 dynamic0000.0000.3004 1.1.1.1 16 3 fei_7/5 dynamic


Field Description

MAC MAC address

peer-address Peer address, namely the remote address

outIntLab Inner outgoing label

outExtLab Outer outgoing label

outInterface Outgoing interface

type MAC address type, statically configured ordynamically learned

RelatedCommands

clear mac-table vfi

show mpls l2transport vcvpls

Purpose Use this command to display information about the pseudo-wiresuccessfully established .


Syntax show mpls l2transport vc vpls [{[vcid <vc-id>[<max-vc-id>]][vfi <vfi-name>][destination <ip-address>][detail]}]

SyntaxDescription

<vc-id> Shows VPLS information corresponding withthe designated vc-id, or shows the minimalvc-id value, range: 0~42949672955

<max-vc-id> Shows the maximal vc-id value, range:0~42949672955

<vfi-name> Shows VPLS information of the VFI with thedesignated name



<ip-address> Shows information about the pseudo—wireestablished with the designated peer address

detail Shows detailed VPLS information


Example 1. This example describes how to show VPLS information of theVFI named 1.ZXR10#show mpls l2 vc vpls vfi 1VFIName LocalCircuit DestAddress VC ID Status1 VFI 7.7.7.7 1 up1 VFI 6.6.6.6 1 up

2. This example describes how to show detailed VPLS informationof the VFI named 1.ZXR10#show mpls l2transport vc vpls vfi 1 detailLocal interface: VFI 1 upDestination address: 7.7.7.7, VC ID: 1, VC status: upTunnel label:Output interface: fei_3/7, imposed label stack { 16, 17 }Create time: 00:00:18, last status change time: 00:00:18Signalling protocol: LDP, peer 7.7.7.7 : 0, upMPLS VC labels: local 2518, remote 17Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledLocal interface: VFI 1 upDestination address: 6.6.6.6, VC ID: 1, VC status: upTunnel label:Output interface: fei_3/6, imposed label stack { 50016, 50017 }Create time: 00:00:18, last status change time: 00:00:18Signalling protocol: LDP, peer 6.6.6.6 : 0, upMPLS VC labels: local 2517, remote 50017Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabled


Field Description

VFIName VFI name

LocalCircuit Local link type, it indicates the L2VPN VPLSin this example

DestAddress Remote destination address

VC ID VC identifier

Status VC status of the VPLS



RelatedCommands

show mpls l2transport vpn summary

show mpls l2transport vpnsummary

Purpose Use this command to show the number of VPWSs and VPLSs in theL2VPN.


Syntax show mpls l2transport vpn summary


Example This example describes how to show the number of L2VPNs con-figured on the router.ZXR10#show mpls l2transport vpn summaryThe summary information about configured l2 vpn:vpn_type current/max

vpws 0/1501vpls 3/4096

RelatedCommands

show mpls l2transport vc vpls

show vfiPurpose Use this command to show detailed information about some virtual

forwarding instance (VFI).


Syntax show vfi <vfi-name>

SyntaxDescription

<vfi-name> Designated virtual forwarding instance (VFI)name in VPLS

Instructions This command is provided only for ZXR10 GER, ZXR10 T64E/T128,and ZXR10 6900/8900.

Example This example describes how to show detailed information of a VPLSvirtual forwarding instance (VFI).ZXR10(config)#show vfi aaFlag: (spoke) Spoke type PW

(tunnelId:X) Get outer label from MPLSTE tunnel and X istunnel IDVfi name: aa VCID: 10 PwType: Ethernet StpTunnel: StpEnableLocal attachment circuit:fei_3/1.1Vlan id: 1

Neighbors connected via pseudowires:15.15.15.15




Field Description

spoke Topology type is spoke

tunnelId:X The outer tunnel encapsulation type isRSVPTE, X indicates the corresponding tunnelidentifier

Vfi name Virtual forwarding instance (VFI) name

Local attachmentcircuit

Circuit interfaces locally bounded

Vlan id VLAN identifier of the interface in theEthernet-vlan instance

Vlan range VLAN range of the interface in the Ethernetinstance

Neighbors connectedvia pseudowires

Indicates that those PEs are in adjacencyrelations with local instance

RelatedCommands

show vfi brief

show vfi briefPurpose Use this command to show brief information about all VPLS in-

stances configured.


Syntax show vfi brief

Instructions This command is provided only for the ZXR10 GER and ZXR10T64E/T128.

Example This example describes how to show the current VPLS virtual for-warding instance (VFI) table.ZXR10#show vfi briefTotal VFI number is 2VFI name VCID PWtypeaa 2 Ethernet-vlanvfi 1 Ethernet


Field Description

Total VFI number is 2 Total number of currently configured virtualforwarding instances (VFIs)

VFI name Virtual forwarding instance (VFI) name

Name of the VFI VC identifier of the virtual forwarding instance(VFI)

PWtype Forwarding mode of this instance



RelatedCommands

show vfi

stp-tunnel enablePurpose Use this command to set stp tunnel in vfi.

Command Modes Vfi configuration

Syntax stp-tunnel enable

no stp-tunnel enable

SyntaxDescription

enable Enables STP tunnel in vfi.

Instructions The platform version 4.8.22 and upgrade versions support thiscommand.

Use this command to set VPLS stp tunnel.

Example This example describes how to set stp tunnel in vfi.ZXR10(config-vfi)#stp-tunnel enable

RelatedCommands

no vfi

vid

pwtype

peer

no peer

vpls mac-filter

vcidPurpose Use this command to specify a virtual channel identifier (VCID) for

the VPLS instance.

Command Modes VFI configuration

Syntax vcid <vcid>

SyntaxDescription

<vcid> Different VPLS instances on the same PEhave different virtual channel identifiers(VCIDs), and VPLS instances with the samevirtual channel identifier (VCID) on differentPEs belong to the same VPLS, range:1~4294967296


If VPLS instances on two PE routers belong to the same VPLS, apseudo wire (PW) must be established between the PEs for com-munication of these VPLS instances. The pseudo wire (PW) is es-



tablished to exchange MPLS inner labels which identifies VPLS be-tween two PEs. MPLS inner labels are also named virtual channel(VC) labels (the pseudo wire (PW) is composed of the VC labeland the MPLS outer label of the LSP). The virtual channel identi-fier (VCID) configured by this command is used to identify differentVPLS when VC labels are exchanged between PEs.

Example This example describes how to configure the virtual channel iden-tifier (VCID) as 100 on the PE.ZXR10(config)#vfi vfi1ZXR10(config-vfi)# vcid 100

RelatedCommands

vfi

pwtype

peer

vpls apply-mac-filterPurpose Use this command to apply MAC filter rule to a virtual forwarding

instance (VFI) on the PE.

Command Modes VFI configuration

Syntax vpls apply-mac-filter <rule_number> global

no vpls apply-mac-filter <rule_number> global

SyntaxDescription

<rule_number> MAC filter rule number

global All members of this virtual forwardinginstance (VFI) are valid


� Use this command to apply VPLS MAC filtering.

Example This example describes how to apply MAC filter rule to a virtualforwarding instance (VFI) member on the PE.ZXR10(config)#vfi vfi1ZXR10(config-vfi)#vpls apply-mac-filter 1 global

RelatedCommands

no vfi

vcid

pwtype

peer

no peer

vpls mac-filter



vfiPurpose Use this command to create a VPLS instance on the PE. Delete the

VPLS instance with the no form of this command.


Syntax vfi <vfi-name>

no vfi <vfi-name>

SyntaxDescription

<vfi-name> Virtual forwarding instance (VFI), namely thename of L2 VPN


� A virtual forwarding instance (VFI) is a VPLS instance on the PErouter. The virtual forwarding instances (VFIs) with the samevirtual channel identifier (VCID) on different PEs belong to thesame VPLS and they can communicate with each other. Afterthis command is executed, enter the VFI configuration mode.

Example This example describes how to configure a name for the VPLS in-stance on the PE.ZXR10(config)#vfi vfi1ZXR10(config-vfi)#

RelatedCommands

no vfi

vid

pwtype

peer

no peer

vfi mspwPurpose Use this command to configure the multi-hop static pseudo wire

(PW) S-PE.


Syntax vfi mspw <vfi-name>

no vfi mspw <vfi-name>

SyntaxDescription

<vfi-name> S-PE MSPW VFI name


� MSPW VFI is a configuration on PE router, which acts as S-PEnode to implement multi-hop static PW forwarding. This con-figuration allows the configuration instance to act as a forward-ing relaying node of the static multi-hop pseudo wire (PW). Usethis command to enter VFI MSPW configuration mode.



Example This example describes how to configure static multi-hop pseudowire (PW) forwarding relaying on the PE.ZXR10(config)#vfi mspw vfi1ZXR10(config-vfi-mspw)#

RelatedCommands

no vfi mspw

pwtype

peer

no peer

vpls mac-filterPurpose Use this command to create a VPLS MAC filter rule, including the

entries. Delete the VPLS MAC filter rule with the no form of thiscommand.


Syntax vpls mac-filter-rule <rule_number><single | range><filter_number><mac-addr><mac-addr>

no vpls mac-filter-rule <rule_number><filter_number>

SyntaxDescription

<rule_number> MAC filter rule number

<single | range> Filter rule type. single or range

<filter_number> MAC filter entry number

<mac-addr> MAC address


� Use this command to implement VPLS MAC filtering.

Example This example describes how to configure the VPLS instance nameon the PE.ZXR10(config)#vpls mac-filter-rule 1ZXR10(config)#vpls mac-filter-rule 1 single 1 0001.0002.0003

RelatedCommands

no vfi

vid

pwtype

peer

no peer



vlan rangePurpose Use this command to configure the VLAN range on the real inter-

face bounded with the VFI attribute.

Command Modes VFI interface configuration

Syntax vlan range <range num><bottom limit><top limit>

no vlan range <range num>

SyntaxDescription <range num> VLAN range number, range: 1~3

<bottom limit> Lower limit of the VLAN range

<top limit> Upper limit of the VLAN range

Instructions Three VLAN ranges can be configured on local interface once.

This command is provided only for ZXR10 GER and ZXR10T64E/T128.

Example This example describes how to configure a VLAN range in PE VFIinterface configuration mode.ZXR10(config)#vfi vfi1ZXR10(config-vfi)#vlan range 1 10 80

RelatedCommands

no vlan range

xconnect vfiPurpose Use this command to add local interface to a virtual forwarding

instance (VFI). Cancel the setting with the no form of this com-mand.


Syntax xconnect vfi <vfi-name>

no xconnect vfi

SyntaxDescription

<vfi-name> Virtual forwarding instance (VFI) name

Instructions � Use this command to add local interface to a virtual forward-ing instance (VFI), and this interface is used to access virtualprivate LAN service (VPLS) for users. The data received fromthis interface is user data.

� This command is provided only for ZXR10 GER and ZXR10T64E/T128.

Example This example describes how to add the interface fei_3/1 to vfi1 inPE interface mode.ZXR10(config)#interface fei_3/1ZXR10(config-if)#xconnect vfi vfi1


C h a p t e r 5

MPLS Traffic Engineering Configuration

Table of Contentsclear ip rsvp authentication.................................................70ip explicit-path ..................................................................70ip rsvp authentication ........................................................71ip rsvp authentication challenge ..........................................71ip rsvp authentication challenge-imp ....................................72ip rsvp authentication lifetime .............................................72ip rsvp authentication key passphrase ..................................73ip rsvp authentication type .................................................73ip rsvp authentication window-size.......................................74ip rsvp bandwidth..............................................................74ip rsvp bfd........................................................................75ip rsvp signalling hello graceful-restart .................................76ip rsvp signalling hello graceful-restart refresh interval ...........76ip rsvp signalling hello graceful-restart refresh misses ............77ip rsvp signalling hello graceful-restart timers recov-ery-time...........................................................................77ip rsvp signalling hello graceful-restart timers restart-time ................................................................................78ip rsvp signalling refresh interval .........................................78ip rsvp signalling refresh misses ..........................................79mpls oam(Global Configuration) ..........................................79mpls oam(Interface Configuration).......................................80mpls static tunnel ..............................................................80mpls traffic-eng ds-te.........................................................81mpls traffic-eng ds-te bc-mode............................................81mpls traffic-eng ds-te exp-maps ..........................................82mpls traffic-eng ds-te te-class .............................................82mpls traffic-eng signaling advertise implicit-null.....................83mpls traffic-eng tunnels(Global Configuration) .......................84mpls traffic-eng tunnels(Interface Configuration) ...................84show ip rsvp authentication ................................................85show ip explicit-path..........................................................86show ip rsvp hello graceful-restart .......................................87show ip rsvp refresh parameter ...........................................87show mpls traffic-eng autoroute ..........................................88show mpls traffic-eng ds-te exp-map ...................................88show mpls traffic-eng ds-te te-class .....................................89show mpls traffic-eng interface detail ...................................90show mpls traffic-eng tunnels..............................................91show mpls traffic-eng tunnels remote-tunnel.........................93tunnel mpls oam back-up-lsp tunnel ....................................94tunnel mpls oam tunnelid ...................................................94tunnel mpls oam type ........................................................95



tunnel mpls traffic-eng autoroute announce ..........................95tunnel mpls traffic-eng autoroute metric ...............................96tunnel mpls traffic-eng bandwidth........................................97tunnel mpls traffic-eng bfd..................................................97tunnel mpls traffic-eng class-type ........................................98tunnel mpls traffic-eng path-option ......................................98tunnel mpls traffic-eng record-route.....................................99tunnel mpls traffic-eng tunnels priority ............................... 100tunnel static ingress......................................................... 100

clear ip rsvp authenticationPurpose Use this command to clear the Security Assistant (SA) of RSVP on

local device.


Syntax clear ip rsvp authentication [A.B.C.D][send | receive]

SyntaxDescription

A.B.C.D Neighbor address

send Clears the sendSA relationship with theneighbor

receive Clears the recvSA relationship with theneighbor

Instructions � This command is an optional command.

� This command is supported after the platform version 4.8.21.

Example This example describes how to clear all security assistant relation-ships on local node.ZXR10#clear ip rsvp authentication

ip explicit-pathPurpose Use this command to configure the next hop for an explicit path in

traffic engineering.


Syntax ip explicit-path {name <name>| identifier <identifier>} next-address <A.B.C.D>{loose | strict}

no ip explicit-path {name <name>| identifier <identifier>}

SyntaxDescription name <name> Explicit path name, 1~16 characters

identifier <identifier>

Explicit path identifier, range: 1~65535


Chapter 5 MPLS Traffic Engineering Configuration

strict Strict path

loose Loose path

<A.B.C.D> IP address of the neighbor node, in the dotteddecimal notation

Defaults There is no explicit path by default.

Instructions Use this command to configure an explicit path and specify thenext hop information for the traffic engineering tunnel. The pathcan be identified by a name or a digit, and its next hops are rankedwith the sequence configured.

Example This example describes how to configure a explict path named test.The next hop is a loose path 100.1.1.1.ZXR10(config)#ip explicit-path name test next-address 100.1.1.1 loose

ip rsvp authenticationPurpose Use this command to enable RSVP authentication on the interface.

Cancel this configuration with the no form of this command.


Syntax ip rsvp authentication

no ip rsvp authentication

Defaults There is no RSVP authentication on the interface by default.

Instructions � This command is a must. This command must be configuredon the interface for enabling RSVP authentication.


Example This example describes how to enable RSVP authentication on theinterface fei_1/1.ZXR10(config)#interface fei_1/1ZXR10(config-if)#ip rsvp authentication

ip rsvp authenticationchallenge

Purpose Use this command to enable challenge mechanism on the inter-face of local device. The interface as a receiver requires challengemechanism be used to confirm the first sequence. If the neigh-bor fails to pass the challenge, neighbor packets are not received.Disable this function with the no form of this command.


Syntax ip rsvp authentication challenge



no ip rsvp authentication challenge

Defaults The behavior of this command is disabled on the interface by de-fault.



Example This example describes how to enable challenge mechanism onthe interface fei_1/1.ZXR10(config)#interface fei_1/1ZXR10(config-if)#ip rsvp authentication challenge

ip rsvp authenticationchallenge-imp

Purpose Use this command to make the interface as the sender require thechallenge mechanism be used on the interface, the interface actsas a sender. Disable this function by using the no form of thiscommand.


Syntax ip rsvp authentication challenge-imp

no ip rsvp authentication challenge-imp

Defaults The behavior is enabled by default.



Example This example describes how to make the interface as the senderrequire the challenge mechanism be used on the interface fei_1/1.ZXR10(config)#interface fei_1/1ZXR10(config-if)#ip rsvp authentication challenge-imp

ip rsvp authentication lifetimePurpose Use this command to configure the lifetime of the authentication

key on the interface. Restore the default value with the no formof this command.


Syntax ip rsvp authentication lifetime <lifetime>

no ip rsvp authentication lifetime

SyntaxDescription

<lifetime> Life time of the authentication key in seconds,range: 1~86400

Defaults The default lifetime is 1800 seconds (30 minutes).



Instructions � This command is an optional command for configuring the life-time of the password of the RSVP authentication on the inter-face. Each interface supports the lifetime of security assistant(SA). If the SA is not used during the lifetime, it will not bedeleted. If the SA is used during the lifetime, it will be re-served.


Example This example describes how to configure the lifetime of the au-thentication key as 5 seconds.ZXR10(config)#interface fei_1/1ZXR10(config-if)#ip rsvp authentication lifetime 5

ip rsvp authentication keypassphrase

Purpose Use this command to configure RSVP authentication key on theinterface. Clear this configuration with the no form of this com-mand.


Syntax ip rsvp authentication key passphrase <passphrase>

no ip rsvp authentication key passphrase

SyntaxDescription

<passphrase> Authentication key configured by user, 8~40characters

Defaults The interface adopts “rsvpteauth” as the key by default.



Example This example describes how to configure the RSVP authenticationkey as zxr102008.ZXR10(config)#interface fei_1/1ZXR10(config-if)#ip rsvp authentication key passphrase zxr102008

ip rsvp authentication typePurpose Use this command to configure RSVP authentication type (MD5 or

SHA1). Restore the default type MD5 with the no form of thiscommand.


Syntax ip rsvp authentication type {md5 | sha1}

no ip rsvp authentication type



SyntaxDescription

md5 MD5 authentication type

sha1 SHA1 authentication type

Defaults MD5 authentication type is adopted on the interface by default.



Example This example describes how to configure the RSVP authenticationtype as MD5 on the interface.ZXR10(config)#interface fei_1/1ZXR10(config-if)#ip rsvp authentication type md5

ip rsvp authenticationwindow-size

Purpose Use this command to configure the authentication window size.Restore the default value with the no form of this command.


Syntax ip rsvp authentication window-size <window-size>

no ip rsvp authentication window-size

SyntaxDescription

<window-size> Authentication window size, range: 1~64

Defaults The authentication window size is 1 by default.

Instructions � This command is an optional command for configuring theRSVP authentication window size on the interface. Whenpackets are received, the authentication window is used tosave the sequence recently received. If the sequence of thesubsequent packet is new, or it is in the authentication windowbut it is never used, it will be received. Otherwise, it will berefused.


Example This example describes how to configure the authentication win-dow size as 5.ZXR10(config)#interface fei_1/1ZXR10(config-if)#ip rsvp authentication window－size 5

ip rsvp bandwidthPurpose Use this command to configure the TE bandwidth in interface con-

figuration mode on the interface. Restore default with the no formof this command.




Syntax ip rsvp bandwidth<interface-kbps><perflow-kbps>[{bc1<bc1-bw-kbps>}]

no ip rsvp bandwidth

SyntaxDescription

<interface-kbp> 1~10000000 Maximal bandwidth supportingtraffic engineering on the interface, unit:kbps, range: 1~10000000

<perflow-kbps> Maximal bandwidth of the flow the trafficengineering passing through the interface,unit: kbps, range: 1~10000000

<bc1-bw-kbps> Bcl bandwidth configured by the user, unit:kbps, range: 1~10000000

Defaults By default, this command is disabled. And the maximal usablebandwidth of traffic engineering on the interface and that of anLSP are 75% of the physical bandwidth.

Instructions The maximal bandwidth configured by this command is invalid ifthe bandwidth occupied by the UP tunnel is larger than the config-ured value. In this case, users must shut down the correspondingUP tunnel to release the occupied bandwidth.

Example This example describes how to configure the maximum TE band-width as 20000kbps, the maximum flow bandwidth as 2000kpbs.ZXR10(config)#interface gei_1/1ZXR10(config-if)#ip rsvp bandwidth 20000 2000

ip rsvp bfdPurpose Use this command to configure RSVP Bidirectional Forwarding De-

tection (BFD) function on the interface. Delete the configurationwith the no form of this command.


Syntax ip rsvp bfd

no ip rsvp bfd

Defaults The behavior of this command is disabled by default.

Instructions When there is no tunnel passing through this interface, Bidirec-tional Forwarding Detection (BFD) sessions are not establishedeven if this command is configured.

Example This example describes how to configure Bidirectional ForwardingDetection (BFD) function on the interface.ZXR10(config)#interface fei_1/1ZXR10(config-if)#ip rsvp bfd



ip rsvp signalling hellograceful-restart

Purpose Use this command to enable the graceful restart (GR) function ofMPLS traffic engineering. Disable this function with the no form ofthis command.


Syntax ip rsvp signalling hello graceful-restart

no ip rsvp signalling hello graceful-restart

Defaults This function is disabled by default.

Example This example describes how to enable the graceful restart (GR)function of MPLS traffic engineering.ZXR10(config)#ip rsvp signalling hello graceful-restart

ip rsvp signalling hellograceful-restart refreshinterval

Purpose Use this command to configure Hello refreshing interval of MPLStraffic engineering (TE) graceful restart (GR) function. Restore thedefault value with the no form of this command.


Syntax ip rsvp signalling hello graceful-restart refresh interval <interval-value>

no ip rsvp signalling hello graceful-restart refresh interval

SyntaxDescription

<interval-value> Hello refresh interval, unit: millisecond,range: 10~30000

Defaults The default value is 10000 milliseconds by default.

Example This example describes how to configure the Hello refresh intervalas 3000 milliseconds.ZXR10(config)#ip rsvp signalling hello graceful-restartrefresh interval 3000



ip rsvp signalling hellograceful-restart refreshmisses

Purpose Use this command to configure the number of missing Hellopackets of the MPLS traffic engineering (TE) graceful restart(GR). When the lost number is exceeded, the neighbor judgesthe packets as lost. As a result, graceful restart (GR) is enabled.Restore the default value with the no form of this command.


Syntax ip rsvp signalling hello graceful-restart refresh misses <msg-count >

no ip rsvp signalling hello graceful-restart refresh misses

SyntaxDescription < msg-count > Number of the missing hello packets, range:

4~10

Defaults The default missing number is 4.

Example This example describes how to configure the number of missinggraceful restart hello packets as 3.ZXR10(config)# ip rsvp signalling hello graceful-restartrefresh misses 3

ip rsvp signalling hellograceful-restart timersrecovery-time

Purpose Use this command to configure the recovery time of the MPLS traf-fic engineering (TE) graceful restart(GR). Restore the default valuewith the no form of this command.


Syntax ip rsvp signalling hello graceful-restart timers recovery-time <time>

no ip rsvp signalling hello graceful-restart timers recovery-time

SyntaxDescription

<time> Recovery time of graceful restart (GR) inmilliseconds, range: 0~30000

Defaults The default value is 120000 milliseconds by default.



Example This example describes how to configure the recovery time as30000 milliseconds.ZXR10(config)#ip rsvp signalling hello graceful-restarttimers recovery-time 30000

ip rsvp signalling hellograceful-restart timersrestart-time

Purpose Use this command to configure the restart time of the MPLS trafficengineering (TE) graceful restart (GR). Restore the default valuewith the no form of this command.


Syntax ip rsvp signalling hello graceful-restart timers restart-time<time>

no ip rsvp signalling hello graceful-restart timers restart-time

SyntaxDescription

<time> Restart time of the graceful restart (GR) inmilliseconds, range: 0~30000

Defaults The default value is 120000 milliseconds.

Example This example describes how to configure the restart time of theMPLS traffic engineering (TE) graceful restart (GR) as 30000 mil-liseconds.ZXR10(config)#ip rsvp signalling hello graceful-restarttimers restart-time 30000

ip rsvp signalling refreshinterval

Purpose Use this command to configure the time interval of sending refreshpackets. Restore the default setting with the no form of this com-mand.


Syntax ip rsvp signalling refresh interval <interval-value>

no ip rsvp signalling refresh interval



SyntaxDescription

<interval-value> Time interval of sending refresh packets inseconds, default: 30000 milliseconds, range:5000~4294967295

Example This exmaple describes how to configure the time interval of send-ing refresh packets as 60000 milliseconds.ZXR10(config)#ip rsvp signalling refresh interval 60000

ip rsvp signalling refreshmisses

Purpose Use this command to configure the number of missing refreshpackets. If the number of missing refresh packets reaches thespecified number, RSVP deletes the corresponding message sav-ing status.


Syntax ip rsvp signalling refresh misses <msg-count>

no ip rsvp signalling refresh misses

SyntaxDescription <msg-count> Number of missing refresh packets, range:

2~10

Defaults The default number of missing refresh packets is 4 by default.

Example This example describes how to configure the number of missingrefresh packets as 6.ZXR10(config)#ip rsvp signalling refresh misses 6

mpls oam(GlobalConfiguration)

Purpose Use this command to enable MPLS OAM. If not enabling the relatedMPLS OAM, the configuration does not take effect. Disable MPLSOAM with the no command.


Syntax mpls oam

no mpls oam

Defaults MPLS OAM is disabled by default.

Instructions Enables MPLS traffic engine in global configuration firstly.

Example This example describes how to enable MPLS OAM in devices.



ZXR10(config)#mpls oam

mpls oam(InterfaceConfiguration)

Purpose Use this command to enable MPLS OAM. If not enabling the relatedMPLS OAM, the configuration does not take effect. Disable MPLSOAM in tunnel with the no command.

Command Modes Tunnel interface configuration

Syntax mpls oam

no mpls oam


SyntaxDescription

enable Enables STP tunnel in vfi.

Instructions Enables MPLS traffic engine in global configuration firstly. Thiscommand takes effect when the tunnel is UP. If the configurationinformation is not complete, the configuration is unsuccessful.

Example This example describes how to enable MPLS OAM in tunnel inter-face.ZXR10(config)#interface tunnel5ZXR10(config-if)#mpls oam

mpls static tunnelPurpose Use this command to set static tunnel lsp information. Delete the

configuration with the no command.


Syntax mpls static tunnel <tunnel-id> ingress <lsr-id> egress <lsr-id>[in-port <if-name> in-label <label>][out-port <if-name>out-label <label>][next-hop <ip-address>]

no mpls static tunnel <tunnel-id> ingress <lsr-id> egress<lsr-id>


SyntaxDescription

<tunnel-id> Static lsp mark

ingress <lsr-id> Static lsp ingress router-id

egress <lsr-id> Static lsp egress router-id

in-port <if-name> In-port name



in-label <label In-label name

out-port <if-name> Out-port name

out-label <label> out-label name

next-hop <ip-address>

Next hop ip address

<tunnel-id> The tunnel id

Instructions Enables mpls oam in global configuration firstly.

Example This example describes how to set tunnel1, ingress ip address1.1.1.1, egress ip address 2.2.2.2, in-label 17, in-port gei_1/2,out-label 18, out-port gei_1/3, next-hop 20.20.20.1.ZXR10(config-if)#mpls static tunnel 1 ingress 1.1.1.1 egress 2.2.2.2in-port gei_1/2 in-label 17 out-port gei_1/3 out-label 18next-hop 20.20.20.1

mpls traffic-eng ds-tePurpose Use this command to enable DS-TE function in global configuration

mode. Cancel this configuration with the no form of this command.


Syntax mpls traffic-eng ds-te

no mpls traffic-eng ds-te

Defaults DS-TE function is disabled by default.


Example This example describes how to enable DS-TC function.ZXR10(config)#mpls traffic-eng ds-te

mpls traffic-eng ds-tebc-mode

Purpose Use this command to configure the bandwidth constraints (BC)type of DS-TE. Cancel this configuration with the no form of thiscommand.


Syntax mpls traffic-eng ds-te bc-mode [mam | extend-mam]

no mpls traffic-eng ds-te bc-mode



SyntaxDescription mam Maximum allocation model

extend-mam Extended maximum allocation model

Defaults The bandwidth constraints (BC) mode is RDM by default.

Example This example describes how to configure the bandwidth constraints(BC) type of DS-TE as extend-mam.ZXR10(config)#mpls traffic-eng ds-te bc-mode extend-mam

mpls traffic-eng ds-teexp-maps

Purpose Use this command to configure the exp-map map relationship.Cancel this configuration with the no form of this command.


Syntax mpls traffic-eng ds-te exp-maps exp <exps> output tunnel<tunnelid>{classtype <ctype>}

no mpls traffic-eng ds-te exp-maps <teclass>

SyntaxDescription <exps> Exp value, range: 0~7

<tunnelid> Tunnel, range: 1~1024

<ctype> Classtype, range: 0~7



Example In this example, the exp-map map is the combination of the cor-responding tunnel 1 and ct0 of exp1.ZXR10(config)# mpls traffic-eng ds-te exp-maps exp 1 outputtunnel1 classtype 0

mpls traffic-eng ds-tete-class

Purpose Use this command to configure the TE-CLASSmapping relationshipin global configuration mode. Cancel this configuration with the noform of this command.


Syntax mpls traffic-eng ds-te te-class te-class<teclass> classtype<ctype> priority <priority>



no mpls traffic-eng ds-te te-class te-class <teclass>

SyntaxDescription

<teclass> Te-class, range: 0~7

<priority> Priorityl, range: 0~7

<ctype> Classtype, range: 0~1

Defaults By default, the mapping relationship is shown below.

TE-CLASS CType Priority

0 0 7

1 1 7

2 — —

3 — —

4 0 0

5 1 0

6 — —

7 — —


Example This example describes how to configure the TC-CLASS mappingnamed Teclass1, which is the combination of the correspondingct0 and the priority 1.ZXR10(config)# mpls traffic-eng ds-te te-classes te-class 1class-type 0 priority 1

mpls traffic-eng signalingadvertise implicit-null

Purpose Use this command to configure the RSVP implicit-null function.


Syntax mpls traffic-eng signaling advertise implicit-null [force]

no mpls traffic-eng signaling advertise implicit-null [force]

SyntaxDescription

force The command with this option takes effectfor all tunnels, including the built and newtunnels. Without this option, then it onlytakes effect for new tunnels



Defaults It is implicit-null configuration by default.

Instructions � If the function is enabled on a node, and this node as the trail-ing node of the tunnel distributes a implicit-null label 3 to thelast but one hop. If this function is disabled on the interface,a implicit-null label 0 is distributed tothe last but one hop.

� Restore the default implicit-null configuration with the no formof this command. If there is the force parameter after theno form of this command, then the new configuration will takeeffect on all tunnels (the created and new tunnels). If there isno force parameter after the no form of this command, thenit only takes effect on the new tunnel.

Example This example describes how to configure RSVP implicit-null func-tion.ZXR10(config)#mpls traffic-eng signalling advertise implicit-null

mpls traffic-engtunnels(GlobalConfiguration)

Purpose Use this command to enable MPLS traffic engineering signalling.Disable the function with the no form of this command.


Syntax mpls traffic-eng tunnels

no mpls traffic-eng tunnels

Defaults MPLS traffic engineering is not supported by default..

Instructions To enable the router to support MPLS traffic engineering, usersmust configure this command in the global configuration mode andenable MPLS traffic engineering on the related interfaces.

Example This example describes how to enable MPLS TE.ZXR10(config)#mpls traffic-eng tunnels

mpls traffic-engtunnels(InterfaceConfiguration)

Purpose Use this command to enable MPLS traffic engineering signallingon a interface. Disable the function with the no form of this com-mand.




Syntax mpls traffic-eng tunnels

no mpls traffic-eng tunnels

Defaults The interface does not support MPLS traffic engineering by default.

Instructions To enable the interface to support MPLS traffic engineering, usersmust enable MPLS traffic engineering in global configuration mode,and then enable MPLS traffic engineering on the interface. Theinterface accepts the MPLS traffic engineering signalling requestand floods its resource information through IGP.

Example This example describes how to enable MPLS TE signalling on theinterface.ZXR10(config)#interface fei_3/1ZXR10config-if)#mpls traffic-eng tunnels

show ip rsvp authenticationPurpose Use this command to show the status and configuration informa-

tion of all security assistants (SAs) or some neighbor.

Command Modes All modes except User EXEC

Syntax show ip rsvp authentication [<A.B.C.D >]

SyntaxDescription

<A.B.C.D> Neighbor address

Defaults The information of all security assistants (SAs) is displayed by de-fault.


Example The following contents will be shown after using this command.ZXR10#show ip rsvp authenticationNeighbor: 10.10.10.2 Key ID (hex): 0a0a0a010000Interface: fei_1/1Direction: SendExpiration: 00:03:59Last valid seq # sent: 0x1e286cb10Windowsize: 5Integriy HF flag: Set

Neighbor: 10.10.10.2 Key ID (hex): 0a0a0a020000Interface: fei_1/1Direction: ReceiveExpiration: 00:03:31Last valid seq # rcvd: 0x1e2868f0eChallenge: ConfiguredWindowsize: 5Integriy HF flag: SetSequence window:0x1e2868f0b0x1e2868f0c0x1e2868f0d0x1e2868f0e

The descriptions of the displayed information are shown below.

Field Description

Interface Corresponding interface name of the SA



Field Description

Direction Direction of the SA (send or receive)

Expiration Expiration time of the SA

Last valid seq Latest valid sequence

Challenge Whether passes the challenge negotiation

Windowsize SA window size

Integriy HFflag Whether supports the challenge

Sequence window Valid sequence group

show ip explicit-pathPurpose Use this command to show detailed information about the explicit

path.

Command Modes All modes except user EXEC

Syntax show ip explicit-path [name <name>| identifier <identifier>]

SyntaxDescription name <name> Path name

identifier <identifier>

Path identifier, range: 1~65535

Instructions This command is used to show detailed information about the ex-plicit path. If the router does not support MPLS traffic engineering,there is no such information displayed.

Example The following contents will be shown after using this command.(The data below are for reference only):ZXR10#show ip explicit-pathPATH namepath_123

1. next-address 192.1.1.1 strict2. next-address 1.1.1.1 loose

PATH identifier 1231. next-address 10.40.88.36 strict2. next-address 3.2.1.6 loose

ZXR10#show ip explicit-path name path_123PATH namepath_123

1. next-address 192.1.1.1 strict2. next-address 1.1.1.1 loose


Field Description

PATH Name of the path or number of flags

1. next-address First IP address in the path

2. next-address Second IP address in the path



show ip rsvp hellograceful-restart

Purpose Use this command to show detailed information about the RSVPGraceful Restart HELLO instance.


Syntax show ip rsvp hello graceful-restart


Example The following contents will be shown after using this command.ZXR10#show ip rsvp hello graceful-restartGraceful Restart: Enabled

Refresh interval: 10000 msecsRefresh misses: 4Advertised restart time: 1000 msecsAdvertised recovery time: 120000 msecs


Filed Description

Graceful Restart whether graceful restart (GR) is enabled

Refresh interval Hello refreshing interval of GR

Refresh misses Hello missing number of GR

Advertised restarttime

Restart time of the advertisement

Advertised recoverytime

Recovery time of the advertisement

show ip rsvp refreshparameter

Purpose Use this command to show the signalling refreshing time and theconfiguration information of missing packets.


Syntax show ip rsvp refresh parameter


Example The following contents will be shown after using this command.ZXR10#show ip rsvp refresh parameterRSVP-TE: Enabled

RSVP signalling refresh interval: 30000 msecsRSVP signalling refresh misses : 4




Field Description

RSVP signallingrefresh interval

Refreshing time of RSVP protocol signallingmessages

RSVP signallingrefresh misses

Number of refreshing missing messages ofRSVP protocol signalling messages

show mpls traffic-engautoroute

Purpose Use this command to show the status and configuration informa-tion of all tunnels with automatic routes.


Syntax show mpls traffic-eng autoroute


Example The following contents will be shown after using this command.(The data below is for reference only):ZXR10# show mpls traffic-eng autorouteMPLS TE autorouting enableddestination 1.1.1.25 has 1 tunnels

TunnelId DestRouterId TunnelState Destination StateNextHop MetricType MetricValue

1 1.1.1.25 UP 10.10.10.2 relative -1


Field Description

TunnelId Tunnel ID

Destination TE RouteID of the tunnel destination

State Tunnel state

NextHop Next hop address of the tunnel

MetricType Metric type

MetricValue Metric value

show mpls traffic-eng ds-teexp-map

Purpose Use this command to show exp-map mapping relationship.


Syntax show mpls traffic-eng ds-te exp-map




Example The following contents will be shown after using this command.(The data below is for reference only):ZXR10#show mpls traffic-eng ds-te exp-mapExp OutTunnel Ctype3 14 1 2


Field Description

Exp Exp-map value

OutTunnel Tunnel identifier

Ctype Ctype corresponding to the tunnel

show mpls traffic-eng ds-tete-class

Purpose Use this command to show TE-CLASS mapping relationship.


Syntax show mpls traffic-eng ds-te te-class


Example The following contents will be shown after using this command.(The data below is for reference only):ZXR10#show mpls traffic-eng ds-te te-classTeclassId CType Priority0 0 71 0 12 unused3 unused4 0 05 1 06 unused7 unused


Field Description

TeclassID TE-CLASS value

Ctype Ctype corresponding to the tunnel

Priority Tunnel priority



show mpls traffic-enginterface detail

Purpose Use this command to show detailed RSVP information on the in-terface.


Syntax show mpls traffic-eng interface detail [<interface-name>]

SyntaxDescription

<interface-name> Interface where RSTP traffic engineering isenabled

Defaults Information of all interfaces where RSTP traffic engineering is en-abled are displayed by default.


Example The following contents will be shown after using this command.(The data below are for reference only):ZXR10#show mpls traffic-eng interface detail fei_1/1fei_1/1:

Bandwidth:Curr allocated: 0K bits/secMax. allowed (total): 75000K bits/secMax. allowed (per flow): 75000K bits/secAuthentication: enabledKey: <encrypted>Type: md5Challenge: enabledChallenge-imp: ImplementedWindow size: 5Lifetime: 300

BFD:enable disconnected down unprotectedfrr_counter: 0

out_lsp_counter: 0

in_lsp_counter: 0


Field Description

Bandwidth Current bandwidth

Authentication Whether authentication is enabled on theinterface

Key Authentication key on the interface

Type Authentication type

Challenge Authentication receiver supporting challenge

Challenge-imp Authentication sender supporting challenge

Window size Authentication window size

Lifetime SA lifetime of the authentication



Field Description

BFD BFD state

frr_counter FRR number

out_lsp_counter Number of LSPs which take the interface asthe outgoing interface

in_lsp_counter Number of LSPs which take the interface asthe incoming interface

showmpls traffic-eng tunnelsPurpose Use this command to show detailed inforamtion about the MPLS

tunnel.


Syntax show mpls traffic-eng tunnels [brief][summary][tunnel<tunnel_id>]

SyntaxDescription

brief Shows brief tunnel information

tunnel <tunnel_id> Shows local tunnel information

summary Shows statistic tunnel information

Example This example shows brief information (the data below is for refer-ence only).ZXR10#show mpls traffic-eng tunnels briefSignalling Summary:LSP Tunnels Process: runningRSVP Process: runningForwarding: enabledTUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROTTunnel_1 10.112.0.12 - unknown up/downTunnel_2 10.110.0.10 - fei_1/4 up/upTunnel_3 10.110.0.20 fei_1/2fei_1/4 up/up


Field Description

LSP Tunnels Process LSP tunnel state

RSVP Process RSVP protocol state

Forwarding Forwarding state

TUNNEL NAME Tunnel name

DESTINATION Destination address of the tunnel

UP IF Uplink interface of the tunnel

DOWN IF Downlink interface of the tunnel

STATE/PROT Tunnel administration/running state



This example shows information about the tunnel namedtunnel11.ZXR10#show mpls traffic-eng tunnels tunnel11name: tunnel_11 (Tunnel11) Destination: 2.2.2.2Status:Admin: up Oper: up Path: valid Signalling: connectedPath option: 11, type explicit pos_412

Config Parameters:Bandwidth: 0 kbps (Global) Priority: 0 0 Affinity: 0x0/0x0Metric Type: IGP (default) Fast-reroute: enable

InLabel:-OutLabel:pos_5/1,16RSVP Signalling Info :

src 4.4.4.4 , Dst 2.2.2.2, Tun_Id 11, Tun_Instance 6RSVP Path Info:Explicit Route: 67.1.1.2 67.1.1.1 66.1.1.1 66.1.1.2 2.2.2.2Record Route: NONETspec:ave rate= 0 kbits, burst= 8000 bytes,

peak rate = 0 kbitsRSVP Resv Info:Record Route: NONEFspec:ave rate= 0 kbits, burst= 8000 bytes,

peak rate = 0 kbits

History:Tunnel:Time since created: 0 days, 5 hours, 17 minutesPrior LSP:0

Current LSP: Uptime:0 days, 5 hours, 16 minutes


Field Description

Name Tunnel name

Destination Destination address of the tunnel

Admin Tunnel administration state: up/down/Admin-down (tunnel interface is shutdown)

Oper Tunnel running state: up/down

Path Tunnel path state: valid/invalid

Signalling Tunnel signalling state: down/connected/sig-nalling

Path option Explicit path configuration

Bandwidth Reserved tunnel bandwidth

Priority Priority for establishing and holding the tunnel

Affinity Tunnel affinity

Fast-reroute Whether the tunnel supports fast reroute:enable/disable

InLabel Incoming label and the interface of the tunnel

OutLabel Outgoing label and the interface of the tunnel

src Source address of the tunnel

Dst Destination address of the tunnel



Field Description

Tun_Id Tunnel identifier

Tun_Instance LSP identifier of the tunnel

Explicit Route Explicit path established in the tunnel

Record Route Address of each hop of the tunnel

showmpls traffic-eng tunnelsremote-tunnel

Purpose Use this command to show remote MPLS tunnel in detail.


Syntax show mpls traffic-eng tunnels remote-tunnel [tunnel-id<tunnel_id> lsp-id<lsp_id> ingress-id <ingress_id> egress-id<egress_id>]

SyntaxDescription

tunnel-id<tunnel_id>

Tunnel identifier of the remote tunnel

lsp-id<lsp_id> Instance identifier of the remote tunnel

ingress-id<ingress_id>

Ingress address of the remote tunnel

egress-id<egress_id>

Egress address of the remote tunnel

Example This example describes how to show information about the re-mote tunnel. The ingress address is 1.1.1.15, the egress addressis1.1.1.25, the tunnel identifier is 2, and the instance identifier is6.ZXR10#show mpls traffic-eng tunnels remote-tunneltunnel-id 2 lsp-id 6 ingress-id 1.1.1.15 egress-id 1.1.1.25LSP Tunnel tunnel_2 is signaled, connection is upInLabel:fei_1/1, 0OutLabel:-RSVP Signalling Info :

src 1.1.1.15 , Dst 1.1.1.25, Tun_Id 2, Tun_Instance 6RSVP Path Info:Explicit Route: 80.1.2.2 1.1.1.25Record Route: NONETspec:ave rate= 0 kbits, burst= 2000 bytes,

peak rate = 0 kbitsRSVP Resv Info:Record Route: NONE

Fspec:ave rate= 0 kbits, burst= 2000 bytes,peak rate = 0 kbits




Field Description

InLabel Ingress labels and the interface of the tunnel

OutLabel Egress labels and the interface of the tunnel

src Source address of tunnel

Dst Destination address of tunnel

Tun_Id Tunnel identifier

Tun_Instance LSP identifier of the tunnel

Explicit Route Explicit path established by the tunnel

Record Route Address of each hop of the tunnel

tunnel mpls oam back-up-lsptunnel

Purpose Use this command to set OAM backup lsp in tunnel mode.

Command Modes Tunnel configuration

Syntax tunnel mpls oam back-up-lsp tunnel <tunnel-id>

no tunnel mpls oam back-up-lsp

SyntaxDescription

<tunnel-id> tunnel id, 1~1024

Defaults No configuration by default.

Instructions This command must be set when tunnel is UP and OAM is disabled.

Example This example describes how to set mpls oam backup tunnel totunnel2.ZXR10(config)#interface tunnel5ZXR10(config-if)#tunnel mpls oam back-up-lsp tunnel2

tunnel mpls oam tunnelidPurpose Use this command to set OAM backup lsp in tunnel mode.


Syntax tunnel mpls oam tunnelid <tunnel-id> ingress <tunnel-id>back-forward-lsp < tunnel-index > type {cv | ffd frequence<time>}

no tunnel mpls oam tunnelid < tunnel-id > ingress <lsr-id>



SyntaxDescription

< tunnel-index > Tunnel number of the reverse direction

<tunnel-id> Tunnel id, 1~1024

<tunnel-id> Static lsp ingress node routerid

<time> Refresh time interval, the value is: 10, 20,50, 100, 200, 500(in milliseconds)


Instructions This command can be activated by other commands. Users canchoose to enable it or not.

Example This example describes how to set tunnel oam whose tunnelid is1 and ingress is 1.1.1.1 to cv mode, set reverse tunnel to 2.ZXR10(config)#interface tunnel5ZXR10(config-if)#tunnel mpls oam tunnelid 1 ingress 1.1.1.1back-forward-lsp 2 type cv

tunnel mpls oam typePurpose Use this command to set detection in tunnel mode.


Syntax tunnel mpls oam type {cv|ffd frequence < interval >}

no tunnel mpls oam type

SyntaxDescription

< interval > Refresh time interval, the value is: 10, 20,50, 100, 200, 500(in milliseconds)

Defaults NULL by default.

By default, ffd refresh interval is 500 milliseconds and cv is 1 sec-ond.

Instructions This command can be set when tunnel is UP and OAM is disabled.

Example This example describes how to set MPLS oam to FFD and timeperiod to 20 milliseconds.ZXR10(config)#interface tunnel5ZXR10(config-if)#tunnel mpls oam type ffd frequence 20

tunnel mpls traffic-engautoroute announce

Purpose Use this command to enable MPLS automatic routing on the tunnelinterface. Disable this function with the no form of this command.




Syntax tunnel mpls traffic-eng autoroute announce

no tunnel mpls traffic-eng autoroute announce

Defaults The tunnel does not support automatic routing by default.


Example This example describes how to enable MPLS automatic routing onthe tunnel interface.ZXR10(config)#interface tunnel5ZXR10(config-if)#tunnel mpls traffic-eng autoroute announce

tunnel mpls traffic-engautoroute metric

Purpose Use this command to configure the metric type and value of thetunnel automatic route. Disable this function with the no form ofthis command.


Syntax tunnelmpls traffic-eng autoroutemetric {<value>| absolute<value>| relative <value>}

no tunnel mpls traffic-eng autoroute metric

SyntaxDescription

<value> Absolute metric value, range: 1~4294967295

absolute <value> Absolute metric value of the absolute metrictype, range: 1~4294967295

relative <value> Metric value relative to IGP of the relativemetric style, range: -10~10

Defaults The default metric type is IGP. The default metric value is IGP met-ric value.


Example 1. This example describes how to configure the metric value ofautomatic routes as 2.ZXR10(config)#interface tunnel5ZXR10(config-if)# tunnel mpls traffic-eng autoroute metric 2ZXR10(config-if)# tunnel mpls traffic-eng autoroute metricabsolute 2ZXR10(config-if)# tunnel mpls traffic-eng autoroute metricrelative -2

2. This example describes how to configure the metric type asabsolute metric, and the metric value is 2.ZXR10(config)#interface tunnel5ZXR10(config-if)# tunnel mpls traffic-eng autoroute metricabsolute 2

3. This exmaple describes how to configure the metric type asrelative metric, and the metric value is -2.



ZXR10(config)#interface tunnel5ZXR10(config-if)# tunnel mpls traffic-eng autoroute metricrelative -2

tunnel mpls traffic-engbandwidth

Purpose Use this command to configure the bandwidth reserved for estab-lishing a tunnel on the tunnel interface. Restore default with theno form of this command.


Syntax tunnel mpls traffic-eng bandwidth <bandwidth>

no tunnel mpls traffic-eng bandwidth

SyntaxDescription

<bandwidth> Bandwidth reserved for the traffic engineeringtunnel, unit: kbps, range: 0~4294967295

Defaults There is no bandwidth reserved for establishing a tunnel.

Instructions If the interface is used by an UP tunnel, the configuration of thiscommand is invalid. In this case, shut down the UP tunnel first.

Example This example describes how to configure the reserved bandwidthas 100kbps.ZXR10(config)#interface fei_3/1ZXR10(config-if)#tunnel mpls traffic-eng bandwidth 100

tunnel mpls traffic-eng bfdPurpose Use this command to enable Bidirectional Forwarding Detection

(BFD) on the tunnel. Cancel this configuration with the no form ofthis command.


Syntax tunnel mpls traffic-eng bfd

no tunnel mpls traffic-eng bfd

Defaults The tunnel does not Bidirectional Forwarding Detection (BFD) bydefault.

Example This example describes how to enable Bidirectional Forwarding De-tection (BFD) on the tunnel.ZXR10(config)#interface tunnel5ZXR10(config-if)#tunnel mpls traffic-eng bfd



tunnel mpls traffic-engclass-type

Purpose Use this command to configure the tunnel class type and the band-width requirement in tunnel interface configuration mode. Cancelthis configuration with the no form of this command.


Syntax tunnel mpls traffic-eng class-type <ct>[bandwidth <bw>]

no tunnel mpls traffic-eng class-type <ct>

SyntaxDescription <ctr> Class type, range: 0~1

<bw> Bandwidth requirement under the class type,range: 1~10000000

Defaults The default type is CT0, and there is no bandwidth requirementsby default.


Example This example describes how to configure the CT type of the tunnelas 1, and the bandwidth requirement as 1000kps.ZXR10(config)#interface tunnel5ZXR10(config-if)# tunnel mpls traffic-eng class-type 1bandwidth 1000

tunnel mpls traffic-engpath-option

Purpose Use this command to configure to obtain ERO by dynamic selectionor explicit path statically on tunnel interface of the device. Cancelthe setting with the no command.


Syntax tunnel mpls traffic-eng path-option <number>{dynamic |explicit {name <path-name>| identifier <id>}}

no tunnel mpls traffic-eng path-option <number>

SyntaxDescription

<number> Number of the option, range: 1~16

name <path-name> Name of the used explicit path, 1~16characters

dynamic Uses the dynamic path computation mode

identifier <id> Digital identifier of the used explicit path,range: 1~65535



Defaults There is no path option configured for the tunnel.

Instructions The establishment of the traffic engineering tunnel provides pathconstraints to designate a flag for each optional path.

Example This example describes how to configure the method of obtainingERO is dynamic selection.ZXR10(config)#interface tunnel5ZXR10(config-if)#tunnel mpls traffic-eng path-option 1 dynamic

The following contents will be shown after using this command.ZXR10#show mpls traffic-eng tunnels summarySignalling Summary:LSP Tunnels Process: runningRSVP Process: runForwarding: enabledHead:6 interfaces,2 active signalling attempts,2 establishedMidpoints:0,Tails: 64


Field Description

LSP Tunnels Process LSP tunnel state

RSVP Process RSVP protocol state

Forwarding Forwarding state

Head Statistic information of local tunnel

interface Number of tunnels in MPLS traffic engineering

active signallingattempts

Number of tunnels successfully establishedor being established

established Number of established tunnels

Midpoints Statistic information of local router serving asthe intermediate node of the tunnel

Tails Statistic information of local router serving asthe end node of the tunnel

tunnel mpls traffic-engrecord-route

Purpose Use this command to enable the tunnel path record function onthe tunnel interface. Disable the function with the no form of thiscommand.


Syntax tunnel mpls traffic-eng record-route

no tunnel mpls traffic-eng record-reroute

Defaults The tunnel path record function is disabled by default.

Example This example describes how to enable the tunnel path record func-tion.



ZXR10(config)#interface fei_5/1ZXR10(config-if)#tunnel mpls traffic-eng record-route

tunnel mpls traffic-engtunnels priority

Purpose Use this command to configure the tunnel priority on the tunnelinterface. Disable this function with the no form of this command.


Syntax tunnel mpls traffic-eng priority <setup_priority><holdup-priority>

no tunnel mpls traffic-eng priority

SyntaxDescription

<setup_priority> Setup priority of the tunnel

<holdup-priority> Holdup priority of the tunnel

Defaults The default priority is 7.


Example This example describes how to configure the setup priority as 2,and the holdup priority as 2.ZXR10(config)#interface tunnel5ZXR10(config-if)#tunnel mpls traffic-eng priority 2 2

tunnel static ingressPurpose Use this command to set static tunnel lsp information. Delete the

configuration with the no command.


Syntax tunnel static ingress <lsr-id> egress <lsr-id>[out-port <if-name> out-label <label>][next-hop <ip-address>]

no tunnel static ingress <lsr-id> egress <lsr-id>

SyntaxDescription

ingress <lsr-id> Static lsp ingress node routerid

egress <lsr-id> Static lsp egress node routerid

out-label <label> Out-label

out-port <if-name> Out-port

<ip-address> Next hop ip address




Instructions When tunnel is DOWN, set it to UP.

Example This example describes how to set tunnel ingress to 1.1.1.1,egress to 2.2.2.2, out-label to 17, out-port to gei_1/1, next-hopto 10.10.10.1.ZXR10(config)#interface tunnel5ZXR10(config-if)#tunnel static ingress 1.1.1.1 egress 2.2.2.2out-port gei_1/1 out-label 17 next-hop 10.10.10.1



This page is intentionally blank.


C h a p t e r 6

FRR Configuration

Table of Contentsip rsvp signalling hello...................................................... 103ip rsvp signalling hello refresh interval................................ 103ip rsvp signalling hello refresh misses................................. 104mpls traffic-eng backup_tunnel ......................................... 104show ip backup route ....................................................... 105show ip rsvp hello instance detail....................................... 105show ip rsvp hello instance summary ................................. 106show mpls traffic-eng fast-reroute ..................................... 107show mpls traffic-eng interface.......................................... 108tunnel mpls traffic-eng fast-reroute.................................... 109

ip rsvp signalling helloPurpose Use this command to enable RSVP hello messages in global con-

figuration and interface configuration mode.

Command Modes Global configuration, interface configuration

Syntax ip rsvp signalling hello

no ip rsvp signalling hello

Instructions � This command id supported after the platform version 4.6.02.

� To enable the router to support RSVP hello messages, this com-mand must be configured in global configuration mode, andthis command must be enabled on the related interface at thesame time. After this command is enabled, the interface sendsRSVP hello messages to its neighbor at regular time and re-ceives the return message from the neighbor to detect its life-time state.

ip rsvp signalling hellorefresh interval

Purpose Use this command to configure the time interval for the interfaceto send RSVP hello requests.




Syntax ip rsvp signalling hello refresh interval <interval>

no ip rsvp signalling hello refresh interval

SyntaxDescription

<interval> Time interval in seconds, range: 10~30000,default: 100 seconds


� The node periodically sends hello request messages (includingthe HELLO REQUEST object) to the neighbor at the configuredinterval.

ip rsvp signalling hellorefresh misses

Purpose Use this command to specify how many Hello acknowledgments anode can miss in a row before the node considers that communi-cation with its neighbor is down


Syntax ip rsvp signalling hello refresh misses <num>

no ip rsvp signalling hello refresh misses

SyntaxDescription <num> Number of sequential Hello acknowledgments

that a node can miss, range: 4~10, default: 4


� The node sends HELLO requests to the neighbor and the neigh-bor answers HELLO acknowledgments. The node will considercommunication with its neighbor is DOWN when the numberof received acknowledgments does not exceed the configuredvalue. If a link is very congested or has a very heavy load, itis recommended to set this number to a value higher than thedefault value to ensure that Hello does not falsely declare thata neighbor is down.

mpls traffic-engbackup_tunnel

Purpose Use this command to assign one or more backup tunnels to a pro-tected interface.


Syntax mpls traffic-eng backup_tunnel <tunnel-id>


Chapter 6 FRR Configuration

no mpls traffic-eng backup_tunnel <tunnel-id>

SyntaxDescription

<tunnel-id> Tunnel identifier of the backup tunnel that canbe used in case of a failure

Defaults No backup tunnels are used if this interface goes down.


� If there is a link or node failure on the interface, the configuredbackup tunnel provides the link protection or node protectionfor the main tunnel that needs local protection.

� Only 1:1 mode is supported now. That is to say, there is onlyone backup tunnel for the interface to be protected.

� The mutual main/standby mode is not supported.

show ip backup routePurpose Use this command to show main/standby routing information

about Fast Reroute (FRR).


Syntax show ip backup route

Example This example describes how to show main/standby routing infor-mation about Fast Reroute (FRR).ZXR10#show ip backup route

show ip rsvp hello instancedetail

Purpose Use this command to show detailed information about a Hello in-stance.


Syntax show ip rsvp hello instance detail [filter destination <ip-address>]

SyntaxDescription

<ip-address> IP address of the neighbor node, in the dotteddecimal format

Instructions This command is supported after the platform version 4.6.02 .

Example This example shows detailed information about a Hello instance.ZXR10#show ip rsvp hello instance detailNeighbor 200.1.1.1 Source 200.1.1.2Hello globally enabled

State:UP



Type:respond to requestI/F: Eth1/1LSP protectiong:0Refresh Interval(msec)

Configured:100Src_instance 0Xa9f07c13 , Dst_instance 0X9BBAA407


Field Description

neighbor IP address of the neighbor

Source IP address of the node sending hello requests

State Communications state: UP indicatesnormal communication and LOST indicatescommunication is lost or fails

type ACTIVE (the node sends hello requests) ;PASSIVE (the neighbor sends hello requests)

I/F Interface type

LSP protection Number of the protected LSPs

Refresh IntervalConfigued

Interval for sending the hello requests

Src_instance Source instance value in the HELLO object

Dst_instance Destination instance value in the HELLOobject

show ip rsvp hello instancesummary

Purpose Use this command to show summary information about a Helloinstance.


Syntax show ip rsvp hello instance summary


Example This example shows summary information about a Hello instance.ZXR10#show ip rsvp hello instance summaryClinet I/F Neighbor Type State LostCnt LspsEt1/1 11.0.0.1 PASSIVE UP 0 1Se2/1 12.0.0.1 PASSIVE UP 0 1




Field Description

Neighbor IP address of the neighbor

State Communications state: UP indicatesnormal communication and LOST indicatescommunication is lost or fails

Type ACTIVE (the node sends hello requests);PASSIVE (the neighbor sends hello requests)

I/F Interface type

LostCnt Number of lost neighbors

show mpls traffic-engfast-reroute

Purpose Use this command to display the contents of the Fast ReRoutedatabase.


Syntax show mpls traffic-eng fast-reroute


Example This example displays the contents of the Fast ReRoute database.ZXR10#show mpls traffic-eng fast-rerouteTunnel head end item informationProtected Tunnel In-label Out intf/label FRR intf/label StatusTunnel10 Tun hd POS5/0 Tu0:12304 readyLSP midpoint frr information:LSP identifier In-label Out intf/label FRR intf/label Status10.110.0.10 24 [456]


Field Description

Protected Tunnel Identifier of the tunnel to be protected

In-label Label value advertised to other nodes by localnode. “Tun hd” indicates the node is the headnode of the tunnel without advertisement oflabels

Out intf/label Outgoing interface of the protected tunnel

label: the label value advertised by the nexthop at the intermediate node

FRR intf/label FRR interface: backup tunnel interface

Label: the label value advertised by the nexthop at the intermediate node

Status FRR current state: ready or active



Field Description

Prefix Address for labels to forward packets by

LSP identifier LSP identifier, including source address,tunnel identidier and lsp identifier

show mpls traffic-enginterface

Purpose Use this command to display information about interfaces whereRSVP traffic engineering is enbaled.

Command Modes All mods except user EXEC

Syntax show mpls traffic-eng interface [<interface-name >]

SyntaxDescription

interface Shows information about a interface whereRSVP traffic engineering is enabled

<interface-name > Locally configured interface with RSVP trafficengineering function

Defaults All the interfaces with RSVP traffic engineering function will be dis-played by default.


Example 1. This example displays information about interfaces whereRSVP traffic engineering is enabled.ZXR10#show mpls traffic-eng interfaceI/F TE Hello interval(ms) misses BK-PATH i/f max(kpbs)flow max(kpbs)fei_1/1 YES NO 100 4 NO 75000 75000fei_1/2 YES NO 100 4 NO 75000 75000fei_1/4 YES YES 100 4 TUL3 75000 75000


Field Description

I/F RSVP TE interface

TE Whether the interface has RSVP TE function

Hello Whether the interface has RSVP hellofunction

Interval Time interval for the interface to send theRSVP hello requests

misses Specifies how many Hello acknowledgmentsa node can miss in a row before the nodeconsiders communication with its neighboris down



Field Description

BK-PATH Whether the interface is configured withbackup tunnel

i/f max Maximal bandwidth of the interfacesupporting traffic engineering

flow max Maximal bandwidth of traffic engineeringflow passing through the interface

2. This example displays information about the interface fei_1/4where RSVP traffic engineering is enabled.ZXR10#show mpls traffic-eng interface fei_1/4I/F TE Hello intervalms）misses BK-PATH i/f max（kpbs）flow max（kpbs）fei_1/4 YES YES 100 4 TUL3 75000 75000

tunnel mpls traffic-engfast-reroute

Purpose Use this command to configure the tunnel to support Fast ReRoute(FRR).


Syntax tunnel mpls traffic-eng fast-reroute

no tunnel mpls traffic-eng fast-reroute

Defaults The tunnel does not support Fast ReRoute (FRR) by default.


� The tunnel supports Fast ReRoute (FRR) and informs the down-stream node that it needs local protection. The downstreamnode tries its best to offer local protection and sends relatedinformation to the head node if local protection is available.


router/ethernetswitch …zte.by/manuals/59xx(v4.8.22)/mpls volume.pdfsubinterface parameters ofthe...

Documents