Cisco IOS XR MPLS Debug Command Reference, Release 3.6
MPLS Traffic Engineering Debug Commands on Cisco IOS XR software
Download this chapter
MPLS Traffic Engineering Debug Commands on Cisco IOS XR softwareMPLS Traffic Engineering Debug Commands on Cisco IOS XR software
Download the complete book
Cisco IOS XR MPLS Debug Command Reference, Release 3.6Cisco IOS XR MPLS Debug Command Reference, Release 3.6 (PDF - 2 MB)
give_us_feedback

Table Of Contents

MPLS Traffic Engineering Debug Commands on Cisco IOS XR Software

debug mpls te-igp

debug mpls traffic-eng

debug mpls traffic-eng ds-te

debug mpls traffic-eng gmpls

debug mpls traffic-eng link-management

debug mpls traffic-eng path

debug mpls traffic-eng pce

debug mpls traffic-eng pce dump-messages

debug mpls traffic-eng topology

debug mpls traffic-eng tunnels


MPLS Traffic Engineering Debug Commands on Cisco IOS XR Software

This chapter describes the commands used to debug Multiprotocol Label Switching Traffic Engineering (MPLS-TE) on Cisco IOS XR software.

debug mpls te-igp

To display information about the MPLS-TE IGP library, use the debug mpls te-igp command in EXEC mode. To disable debugging output, use the no form of this command.

debug mpls te-igp

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.2

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.3.0

No modification.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance.For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows how to enable MPLS-TE IGP library debugging: 

RP/0/RP0/CPU0:router# debug mpls te-igp

debug mpls traffic-eng

To display information about MPLS-TE configuration, use the debug mpls traffic-eng command in EXEC mode. To disable debugging output, use the no form of this command.

debug mpls traffic-eng {areas | autoroute | connections | debug-events | errors | frr | load-balancing | temib}

no debug mpls traffic-eng {areas | autoroute | connections | debug-events | errors | frr | load-balancing | temib}

Syntax Description

areas

Displays IGPs where MPLS TE is enabled.

autoroute

Displays tunnels announced to the Interior Gateway Protocol (IGP).

connections

Displays connections to server events.

debug-events

Displays general debugging information.

errors

Displays MPLS TE error information.

frr

Displays MPLS TE fast reroute (FRR) events.

load-balancing

Displays unequal cost load balancing over tunnels.

temib

Displays MPLS-TE mib debug information.


Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.2

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.3.0

No modification.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance.For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows debug output for automatic routing over TE tunnels: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng autoroute


RP/0/0/CPU0:Jun 11 11:08:19.479 : te_control[376]: Adding tunnel-te15 to autoroute list

RP/0/0/CPU0:Jun 11 11:08:19.480 : te_control[376]: TE-Auto: announcement that destination 
30.30.30.30 has 1 tunnels

RP/0/0/CPU0:Jun 11 11:08:19.482 : te_control[376]:   tunnel-te15 (traffic share 0, nexthop 
30.30.30.30)

debug mpls traffic-eng ds-te

To debug differentiated services TE (DS-TE) events, use the debug mpls traffic-end ds-te command in EXEC mode. To return to the default behavior, use the no form of this command.

debug mpls traffic-end ds-te

no debug mpls traffic-end ds-te

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.3.0

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance.For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows debug output for MPLS-TE differentiated services: 

RP/0/RP0/CPU0:router# debug mpls traffic-end ds-te

RP/0/0/CPU0:Jun 11 11:09:36.716 : te_control[376]: te_verify_bandwidth: Verifying 
tunnel-te15 with 100 of Class type 0

RP/0/0/CPU0:Jun 11 11:09:36.719 : te_control[376]: te_apply_bandwidth: Configuring 
tunnel-te15 with 100 of Class type 0


RP/0/0/CPU0:Jun 11 11:09:36.478 : te_control[376]: tspvif_has_valid_class_type_priority: 
Tunnel 15: CT = 0, SetupP = 7, HoldP = 7 setup_matched = TRUE, hold_matched = TRUE

debug mpls traffic-eng gmpls

To debug Generalized-MPLS (GMPLS) information, use the debug mpls traffic-eng gmpls command in privileged EXEC mode. To return to the default behavior, use the no form of this command.

debug mpls traffic-eng gmpls

no debug mpls traffic-eng gmpls

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.3.0

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance.For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows debug output for MPLS GMPLS using the debug mpls traffic-eng gmpls command: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng gmpls


RP/0/0/CPU0:Jun 11 11:11:33.544 : te_control[376]: tspvif_set_direction_bidirectional: 
direction bidirectional for tunnel tunnel-te15

RP/0/0/CPU0:Jun 11 11:10:28.319 : te_control[376]: mpls_te_rsvp_api_callback_handler: 
setup_lkup (LSPID = 115): matching setup is present, current LSP is present protect LSP is 
absent for tunnel-te15

debug mpls traffic-eng link-management

To display information about MPLS-TE interfaces and Label Switch Path (LSP) admission control, use the debug mpls traffic-eng link-management command in EXEC mode. To disable debugging output, use the no form of this command.

debug mpls traffic-eng link-management {admission-control | advertisements | bandwidth-allocation | checkpoint | errors | events | filter tunnel-ID | igp | igp-neighbors | links | routing | timers}

no debug mpls traffic-eng link-management {admission-control | advertisements | bandwidth-allocation | checkpoint | errors | events | filter tunnel-ID | igp | igp-neighbors | links | routing | timers}

Syntax Description

admission-control

Displays information about TE LSP admission control on TE interfaces.

advertisements

Displays resource advertisements for TE interfaces.

bandwidth-allocation

Displays bandwidth allocation for TE LSPs.

checkpoint

Displays TE engineering checkpoint-related activities on TE interfaces.

errors

Displays TE link resource management-related errors.

events

Displays TE link management system events.

filter tunnel-ID

Displays filter messages based on the tunnel ID. Filter range is 0 to 65535. Tunnel-ID range is 0 to 4294967295.

igp

Displays TE link management process communications with IGP.

igp-neighbors

Displays changes to the link management database for IGP neighbors.

links

Displays TE link management interface events.

routing

Displays TE link management routing resolutions.

timers

Displays TE link management timer information.


Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.2

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.3.0

No modification.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows debug output for the debug mpls traffic-eng link-management admission-control command: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng link-management admission-control


TE-LM-ADMIT: Rx-ed LspAdmitRequest downlink=POS0_7_0_1 uplink=NOT SET 

TE-LM-ADMIT: tunnel='10.20.20.20 1_387 (10.90.90.90)': Inserted in 'name' tree 

TE-LM-ADMIT: tunnel='10.20.20.20 1_387 (10.90.90.90)': Created [3 tunnels total] 

TE-LM-ADMIT: tunnel='10.20.20.20 1_387 (10.90.90.90)': Inserted in 'downstream link' tree 
(POS0/7/0/1, 7) 

TE-LM-EVENTS: tunnel='10.20.20.20 1_387 (10.90.90.90)': "New" -> "Admitting 2nd Path Leg" 

TE-LM-RSRC: rrr_lm_rp_psc_install:817, PSC-RP install tunnel='10.20.20.20 1_387 
(10.90.90.90)' 

TE-LM-RSRC: rrr_lm_rp_psc_path_out:460, Path-Out: Held downstream bw=0 on 
link='POS0/7/0/1' 

TE-LM-EVENTS: tunnel='10.20.20.20 1_387 (10.90.90.90)': "Admitting 2nd Path Leg" -> "Path 
Admitted" 

TE-LM-ADMIT: CAC has granted RSVP Path query for tunnel='10.20.20.20 1_387 (10.90.90.90)' 
on intf=POS0_7_0_1[reason='None'] 

TE-LM-ADMIT: Rx-ed LspAdmitRequest downlink=POS0_7_0_1 uplink=NOT SET 

TE-LM-EVENTS: tunnel='10.20.20.20 1_387 (10.90.90.90)': "Path Admitted" -> "Admitting 1st 
Resv Leg" 

TE-LM-RSRC: rrr_lm_rp_psc_install:817, PSC-RP install tunnel='10.20.20.20 1_387 
(10.90.90.90)' 

TE-LM-RSRC: rrr_lm_rp_psc_resv_in:569, Resv-In: Locked downstream bw=0 on 
link='POS0/7/0/1' 

TE-LM-EVENTS: tunnel='10.20.20.20 1_387 (10.90.90.90)': "Admitting 1st Resv Leg" -> "Resv 
Admitted" 

TE-LM-ADMIT: CAC has granted RSVP Resv query for tunnel='10.20.20.20 1_387 (10.90.90.90)' 
on intf=POS0_7_0_1[reason='None']

The following example shows debug output for the debug mpls traffic-eng link-management advertisements command: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng link-management advertisements 


TE-LM-ADV: area ospf area 0: IGP announcement: link POS0/7/0/1: info changed 

TE-LM-ADV: area ospf area 0: IGP msg: link POS0/7/0/1: includes subnet type (1), described 
nbrs (1) 

TE-LM-ADV: LSA: Flooding mgr rx-ed msg: link information change (POS0/7/0/1) 

TE-LM-ADV: area ospf area 0: *** Flooding node information *** 

System Information:: 

Flooding Protocol: OSPF 

Header Information:: 

IGP System ID: 10.20.20.20 

MPLS TE Router ID: 10.20.20.20 

Flooded Links: 1 

Link ID:: 0 (POS0_7_0_1) 

Link IP Address: 10.15.12.1 

Neighbor: ID 10.90.90.90, IP 10.15.12.2 

TE metric: 1 

IGP metric: 1 

Physical Bandwidth: 155520 kbits/sec 

Max Res. Global BW: 1000000 kbits/sec 

Max Res. Sub BW: 0 kbits/sec 

Global Pool Sub Pool 

----------- ---------- 

Reservable Bandwidth[0]: 1000000 0 kbits/sec 

Reservable Bandwidth[1]: 1000000 0 kbits/sec 

Reservable Bandwidth[2]: 1000000 0 kbits/sec 

Reservable Bandwidth[3]: 1000000 0 kbits/sec 

Reservable Bandwidth[4]: 1000000 0 kbits/sec 

Attribute Flags: 0x00000000

debug mpls traffic-eng path

To display information about MPLS-TE path calculation, use the debug mpls traffic-eng path command in EXEC mode. To disable debugging output, use the no form of this command.

debug mpls traffic-eng path {tunnel-id | lookup | spf | verify}

no debug mpls traffic-eng path {tunnel-id | lookup | spf | verify}

Syntax Description

tunnel-ID

Displays debug output for this tunnel only. Range is 0 to 4294967295.

lookup

Displays path calculation lookup events.

spf

Displays shortest path first (SPF) calculations events.

verify

Displays path verifications events.


Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.2

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.3.0

No modification.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows debug output for the calculation of an SPF TE path: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng path spf 


RP/0/RP0/CPU0:Aug 20 07:43:20.317: te_control[114]: TE-PCALC_SPF:0000.0000.0010.00 aw 0 
min_bw -1, 

prev_node(NULL) 

RP/0/RP0/CPU0:Aug 20 07:43:20.317: te_control[114]: TE-PCALC_SPF:0000.0000.0010.00 

RP/0/RP0/CPU0:Aug 20 07:43:20.317: te_control[114]: TE-PCALC_SPF:0000.0000.0020.00 aw 10 
min_bw 155000, 

prev_node(0000.0000.0010.00)

debug mpls traffic-eng pce

To display information about MPLS-TE path computation element (PCE), use the debug mpls traffic-eng pce command in EXEC mode. To disable debugging output, use the no form of this command.

debug mpls traffic-eng pce {config | dump-messages | error | igp | keepalive | path | session | timer | tunnel}

no debug mpls traffic-eng pce {config | detail | dump-messages | error | igp | keepalive | path | session | timer | tunnel}

Syntax Description

config

Displays PCE configuration information.

error

Displays PCE errors.

igp

Displays PCE IGP interactions.

keepalive

Displays PCE keepalive messages.

path

Displays PCE path computation information.

session

Displays PCE session information.

timer

Displays PCE time information.

tunnel

Displays PCE tunnel information


Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.5.0

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows debug output for the debug mpls traffic-eng pce tunnel command: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng pce tunnel


RP/0/0/CPU0:May 28 07:15:26.507 : te_control[375]: tspvif_verify_setups: tunnel-te10, 3639 

RP/0/0/CPU0:May 28 07:15:26.507 : te_control[375]: tunnel-te10: popt does not have new 
path, flag 0 

RP/0/0/CPU0:May 28 07:15:26.507 : te_control[375]: PCE primary path request: Tun 
tunnel-te10, LSP ID 10 po_idx = 1, pce_addr = 0.0.0.0 src = 0.0.0.0 dst = 60.60.60.60 bw = 
0 affinity = 0 setup_priority = 7 hold_priority = 7

RP/0/0/CPU0:May 28 07:15:26.508 : te_control[375]: tunnel-te10: Destination 60.60.60.60 
directly reachable

debug mpls traffic-eng pce dump-messages

To display information about MPLS-TE path computation element (PCE) dump-messages, use the debug mpls traffic-eng pce dump-messages command in EXEC mode. To disable debugging output, use the no form of this command.

debug mpls traffic-eng pce dump-messages {all | close | error | keepalive | notify | open | request | response | unknown}

no debug mpls traffic-eng pce dump-messages {all | close | error | keepalive | notify | open | request | response | unknown}

Syntax Description

all

Displays all PCE dump-messages.

close

Displays PCE protocol (PCEP) close messages.

error

Displays PCE error messages.

keepalive

Displays PCEP keepalive messages.

notify

Displays PCE notify messages.

open

Displays PCEP open messages.

request

Displays PCReq messages.

response

Displays PCRep messages.

unknown

Displays unknown PCEP messages.


Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.5.0

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance.For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows debug output for the debug mpls traffic-eng pce dump-messages all command: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng pce dump-messages all


RP/0/0/CPU0:Jan 16 23:01:11.552 : te_control[375]: pce_pcep_open:3911

RP/0/0/CPU0:Jan 16 23:01:11.553 : te_control[375]: HDR P1: 0x00001001

RP/0/0/CPU0:Jan 16 23:01:11.553 : te_control[375]: HDR P2: 0x00000010

RP/0/0/CPU0:Jan 16 23:01:11.554 : te_control[375]: OBJ_HDR: [0x00080101]

RP/0/0/CPU0:Jan 16 23:01:11.554 : te_control[375]:    OBJ_CLASS: [0x1]

RP/0/0/CPU0:Jan 16 23:01:11.554 : te_control[375]:    OBJ_TYPE: [0x1]

RP/0/0/CPU0:Jan 16 23:01:11.555 : te_control[375]:    RSRVD: [0x0]

RP/0/0/CPU0:Jan 16 23:01:11.555 : te_control[375]:    P_FLAG: [0x0]

RP/0/0/CPU0:Jan 16 23:01:11.555 : te_control[375]:    I_FLAG: [0x0]

RP/0/0/CPU0:Jan 16 23:01:11.555 : te_control[375]:    LEN: [0x08]

RP/0/0/CPU0:Jan 16 23:01:11.555 : te_control[375]: OPEN_OBJ:[0x00F01E01] 

RP/0/0/CPU0:Jan 16 23:01:11.555 : te_control[375]:    VER: [0x1]

RP/0/0/CPU0:Jan 16 23:01:11.556 : te_control[375]:    FLAGS: [0x0]

debug mpls traffic-eng topology

To display information about MPLS-TE topology events, use the debug mpls traffic-eng topology command in EXEC mode. To disable debugging output, use the no form of this command.

debug mpls traffic-eng topology {change | lsa}

no debug mpls traffic-eng topology {change | lsa}

Syntax Description

change

Displays topology change events.

lsa

Displays topology link-state advertisement (LSA) events.


Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.2

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.3.0

No modification.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance.For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows sample output for TE topology change events: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng topology change


RP/0/RP0/CPU0:Route-2#RP/0/RP0/CPU0:Aug 20 08:20:41.831: te_control[114]: TE-PCALC_LSA: 
NODE_CHANGE_UP isis level-2 

RP/0/RP0/CPU0:Aug 20 08:20:41.833: te_control[114]: link flags: 

RP/0/RP0/CPU0:Aug 20 08:20:41.834: te_control[114]: LINK_CHANGE_UP 

RP/0/RP0/CPU0:Aug 20 08:20:41.836: te_control[114]: system_id: 0000.0000.0002.00, link: 
10.2.2.2 

RP/0/RP0/CPU0:Aug 20 08:20:41.838: te_control[114]: nbr_system_id: 0000.0000.0001.00, link 
10.2.2.1 

RP/0/RP0/CPU0:Aug 20 08:20:41.839: te_control[114]: TE-PCALC_LSA: NODE_CHANGE_UPDATE isis 
level-2 

RP/0/RP0/CPU0:Aug 20 08:20:41.841: te_control[114]: link flags: 

RP/0/RP0/CPU0:Aug 20 08:20:41.841: te_control[114]: LINK_CHANGE_UP 

RP/0/RP0/CPU0:Aug 20 08:20:41.843: te_control[114]: system_id: 0000.0000.0002.00, link: 
10.1.1.2 

RP/0/RP0/CPU0:Aug 20 08:20:41.846: te_control[114]: nbr_system_id: 0000.0000.0001.00, link 
10.1.1.1 

RP/0/RP0/CPU0:Aug 20 08:20:41.848: te_control[114]: TE-PCALC_LSA: NODE_CHANGE_ROUTER_ID 
isis level-2 

RP/0/RP0/CPU0:Aug 20 08:20:41.851: te_control[114]: link flags: 

RP/0/RP0/CPU0:Aug 20 08:20:41.852: te_control[114]: LINK_CHANGE_BW 

RP/0/RP0/CPU0:Aug 20 08:20:41.852: te_control[114]: LINK_CHANGE_ATTRIBUTE 

RP/0/RP0/CPU0:Aug 20 08:20:41.853: te_control[114]: LINK_CHANGE_SWITCHING 

RP/0/RP0/CPU0:Aug 20 08:20:41.854: te_control[114]: LINK_CHANGE_NBR 

RP/0/RP0/CPU0:Aug 20 08:20:41.857: te_control[114]: system_id: 0000.0000.0002.00, link: 
8.15.148.180 

RP/0/RP0/CPU0:Aug 20 08:20:41.858: te_control[114]: nbr_system_id: 080f.9354.0000.00, link 
10.0.0.1 

RP/0/RP0/CPU0:Aug 20 08:20:41.859: te_control[114]: Loc topology changed for 10.20.20.20 

RP/0/RP0/CPU0:Aug 20 08:20:41.861: te_control[114]: Sending..local topology: 

RP/0/RP0/CPU0:Aug 20 08:20:41.864: te_control[114]: loc intfc addr = 10.2.2.2 rem intfc 
addr = 10.2.2.1 rem rtr id = 10.0.0.0 

RP/0/RP0/CPU0:Aug 20 08:20:41.864: te_control[114]: loc intfc addr = 10.1.1.2 rem intfc 
addr = 10.1.1.1 rem rtr id = 10.0.0.0

The following example shows sample output for TE topology lsa events: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng topology lsa


RP/0/RP0/CPU0:Route-2(config)#RP/0/RP0/CPU0:Aug 20 08:22:18.457: te_control[114]: 
te_igp_lsa_dump: Dumping received LSA 

RP/0/RP0/CPU0:Aug 20 08:22:18.457: te_control[114]: igp_area_id: 

RP/0/RP0/CPU0:Aug 20 08:22:18.458: te_control[114]: area = 2, handle = 0x1 

RP/0/RP0/CPU0:Aug 20 08:22:18.460: te_control[114]: system_id/node_id: 

RP/0/RP0/CPU0:Aug 20 08:22:18.461: te_control[114]: protocol = 1, node type = 1 

RP/0/RP0/CPU0:Aug 20 08:22:18.493: te_control[114]: system id = 0000.0000.0002 

RP/0/RP0/CPU0:Aug 20 08:22:18.494: te_control[114]: rrr_lsa_valid_flags = 0x1 

RP/0/RP0/CPU0:Aug 20 08:22:18.495: te_control[114]: rrr_router_id = 20.20.20.20 

RP/0/RP0/CPU0:Aug 20 08:22:18.496: te_control[114]: num_links = 1 

RP/0/RP0/CPU0:Aug 20 08:22:18.499: te_control[114]: rrr_fragment_id = 0 

RP/0/RP0/CPU0:Aug 20 08:22:18.500: te_control[114]: rrr_node_lsa_flag = 0x0 

RP/0/RP0/CPU0:Aug 20 08:22:18.503: te_control[114]: Dumping information for link = 0 

RP/0/RP0/CPU0:Aug 20 08:22:18.504: te_control[114]: rrr_fragment_id = 0 

RP/0/RP0/CPU0:Aug 20 08:22:18.513: te_control[114]: rrr_link_valid_flags = 0x1D7F 

RP/0/RP0/CPU0:Aug 20 08:22:18.514: te_control[114]: rrr_link_subnet_type = 1 

RP/0/RP0/CPU0:Aug 20 08:22:18.516: te_control[114]: my_ip_address = 7.2.2.2 

RP/0/RP0/CPU0:Aug 20 08:22:18.516: te_control[114]: nbr_ip_address = 7.2.2.1 

RP/0/RP0/CPU0:Aug 20 08:22:18.519: te_control[114]: rrr_metric_te = 10 

RP/0/RP0/CPU0:Aug 20 08:22:18.520: te_control[114]: admin_weight = 0 

RP/0/RP0/CPU0:Aug 20 08:22:18.521: te_control[114]: rrr_metric_igp = 10 

RP/0/RP0/CPU0:Aug 20 08:22:18.529: te_control[114]: max_link_bw = 1284788416

debug mpls traffic-eng tunnels

To display information about MPLS-TE tunnel events, use the debug mpls traffic-eng tunnels command in EXEC mode. To disable debugging output, use the no form of this command.

debug mpls traffic-eng tunnels {chkpt | events | filter tunnel-ID | reoptimize | signaling | state | timers}

no debug mpls traffic-eng tunnels {chkpt | events | filter tunnel-ID | reoptimize | signaling | state | timers}

Syntax Description

chkpt

Displays MPLS-TE tunnel chkpt events.

events

Displays MPLS-TE tunnel events

filter tunnel-ID

Displays filter messages based on the tunnel ID. Filter range is 0 to 65535. Tunnel-ID range is 0 to 4294967295.

reoptimize

Displays MPLS-TE tunnel reoptimization events.

signaling

Displays MPLS-TE tunnel signaling events.

state

Displays MPLS-TE tunnel state events.

timers

Displays MPLS-TE tunnel timers events.


Command Modes

EXEC

Command History

Release
Modification

Release 3.2

This command was introduced on the Cisco CRS-1 and
Cisco XR 12000 Series Router.

Release 3.3.0

No modification.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

No modification.


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco IOS XR Software.

Task ID

Task ID
Operations

mpls-te

read


Examples

The following example shows debug output for TE tunnels: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng tunnels events


RP/0/0/CPU0:Aug 19 11:25:01.540:te_control[338]: LSP-TUNNEL: posting action(s) to 
all-tunnels:

RP/0/0/CPU0:Aug 19 11:25:01.540:te_control[338]:               perform full reevaluation

RP/0/0/CPU0:Aug 19 11:25:01.541:te_control[338]: LSP-TUNNEL: scheduling pending actions on 
all-tunnels

RP/0/0/CPU0:Aug 19 11:25:01.542:te_control[338]: LSP-TUNNEL: actions processor credits: 
old 99998, new 3600300 [36003 msecs], updated 100000

RP/0/0/CPU0:Aug 19 11:25:01.543:te_control[338]: LSP-TUNNEL: actions processor scheduling 
delayed 0 msecs [100000 credits]

RP/0/0/CPU0:Aug 19 11:25:01.544:te_control[338]: LSP-TUNNEL: processing actions list...

RP/0/0/CPU0:Aug 19 11:25:01.544:te_control[338]: LSP-TUNNEL: applying actions to 
all-tunnels, as follows:

RP/0/0/CPU0:Aug 19 11:25:01.544:te_control[338]:               perform full reevaluation

RP/0/0/CPU0:Aug 19 11:25:01.544:te_control[338]: LSP-TUNNEL: done COMPLETE processing of 
actions list

The following example shows debug output for TE signaling: 

RP/0/RP0/CPU0:router# debug mpls traffic-eng tunnels signaling


RP/0/0/CPU0:Aug 19 11:26:22.762:te_control[338]: LSP-TUNNEL-SIG: tunnel tunnel-te15 [1]: 
RSVP head-end open

RP/0/0/CPU0:Aug 19 11:26:22.763:te_control[338]: Hop 0 set to 10.10.10.10

RP/0/0/CPU0:Aug 19 11:26:22.763:te_control[338]: Info for hop=1

RP/0/0/CPU0:Aug 19 11:26:22.764:te_control[338]:  iftype = num

RP/0/0/CPU0:Aug 19 11:26:22.765:te_control[338]:  ip_addr = 7.1.1.2

RP/0/0/CPU0:Aug 19 11:26:22.765:te_control[338]: Info for hop=2

RP/0/0/CPU0:Aug 19 11:26:22.766:te_control[338]:  iftype = num

RP/0/0/CPU0:Aug 19 11:26:22.766:te_control[338]:  ip_addr = 20.20.20.20

RP/0/0/CPU0:Aug 19 11:26:22.767:te_control[338]: Returning 0x800 as GPID. tunnel-te15 is 
not optical

RP/0/0/CPU0:Aug 19 11:26:22.786:te_control[338]: tspts_install_tags

RP/0/0/CPU0:Aug 19 11:26:22.788:te_control[338]: determine_out_nbr_addr: NextHop 7.1.1.2, 
SrcPrt: 1, DstPrt: 15; NbrRtrID 20.20.20.20

RP/0/0/CPU0:Aug 19 11:26:22.789:te_control[338]: update_tspec: Received tspec for tunnel  
Burst = 1000; Rate = 0; MinUnit = 40 MaxUnit = 500; Peak = 0;

RP/0/0/CPU0:Aug 19 11:26:22.790:te_control[338]: update_class_type: No class type object 
found for tunnel router_t15 CT = 0

RP/0/0/CPU0:Aug 19 11:26:22.793:te_control[338]: Received Path Admission Response 0 for 
source 10.10.10.10, Dest 20.20.20.20, DstPrt 15, SrcPrt 1, ExtID 0xa0a0a0a

RP/0/0/CPU0:Aug 19 11:26:22.854:te_control[338]: Rcvd EV_PATH_CREATE for src a0a0a0a 
srcprt 1 dstprt 15 hdl 4b100007

RP/0/0/CPU0:Aug 19 11:26:22.910:te_control[338]: RSVP_API_EV_PATH_MATCH_RESV_CREATE Client 
Cookie 485cef2c

RP/0/0/CPU0:Aug 19 11:26:22.910:te_control[338]:  Working LSP: is_connected = 0, 
ps_out_ifh = 0x0

RP/0/0/CPU0:Aug 19 11:26:22.911:te_control[338]: tspts_handle_rsvp_midpoint_resv_event: 
Valid midpoint resv event: Midpoint Match RESV Create;Dest: 20.20.20.20; Src: 10.10.10.10; 
PrevHop: 7.1.1.2; InputIF: 0x3000900

RP/0/0/CPU0:Aug 19 11:26:22.912:te_control[338]: update_resv_rro: 
rsvp_api_argblock_get_rro: 'rsvp_api' detected the 'fatal' condition 'no such 
state/object'

RP/0/0/CPU0:Aug 19 11:26:22.913:te_control[338]: update_fspec: Received fspec for tunnel 
router_t15 QOS = 5; Burst = 1000; Rate = 0; MinUnit = 0 MaxUnit = 500; Peak = 0; Requested 
= 0; Slack = 0

RP/0/0/CPU0:Aug 19 11:26:22.924:te_control[338]: Received Resv Admission Response 0 for 
source 10.10.10.10, Dest 20.20.20.20, DstPrt 15, SrcPrt 1, ExtID 0xa0a0a0a

RP/0/0/CPU0:Aug 19 11:26:22.926:te_control[338]: mpls_te_resv_admitted_head HEAD RESV