|
|
Table Of Contents
debug mpls ldp transport connections
debug mpls ldp transport events
debug mpls traffic-eng autoroute
debug mpls traffic-eng link-management admission-control
debug mpls traffic-eng link-management advertisements
debug mpls traffic-eng link-management bandwidth-allocation
debug mpls traffic-eng link-management errors
debug mpls traffic-eng link-management events
debug mpls traffic-eng link-management igp-neighbors
debug mpls traffic-eng link-management links
debug mpls traffic-eng link-management preemption
debug mpls traffic-eng link-management routing
debug mpls traffic-eng load-balancing
debug mpls traffic-eng topology change
debug mpls traffic-eng topology lsa
debug mpls traffic-eng tunnels errors
debug mpls traffic-eng tunnels events
debug mpls traffic-eng tunnels labels
debug mpls traffic-eng tunnels reoptimize
debug mpls traffic-eng tunnels signalling
debug mpls traffic-eng tunnels state
debug mpls traffic-eng tunnels timers
debug mpls xtagatm cross-connect
debug mpls ldp transport connections
To display information about the TCP connections used to support Label Distribution Protocol (LDP) sessions, use the debug mpls ldp transport connections command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls ldp transport connections [peer-acl acl] [interface interface]
no debug mpls ldp transport connections [peer-acl acl] [interface interface]
Syntax Description
Defaults
Displays information about LDP TCP connection activity for all peers and all interfaces.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to monitor LDP activity relating to the establishment of the TCP connection for LDP sessions.
When two devices establish a TCP connection for an LDP session, the device with the larger transport address plays an active role and the other plays a passive role. The active device attempts to establish a TCP connection to the well-known LDP port at the passive device. The passive device waits for the connection to the well-known port to be established.
Examples
The following shows sample output from the debug mpls ldp transport connections command:
Router# debug mpls ldp transport connectionsDebug output at active peer:ldp: Opening listen port 646 for 10.0.0.44, 34.0.0.44ldp: Open LDP listen TCB 0x60E105BC; lport = 646; fhost = 10.0.0.44ldp: Add listen TCB to list; tcb 0x60E105BC; addr 10.0.0.44ldp: Incoming ldp conn 133.0.0.33:646 <-> 10.0.0.44:11042ldp: create ptcl_adj: tp = 0x610ECD64, ipaddr = 10.0.0.44Debug output at passive peer:ldp: Opening ldp conn; adj 0x60BAC33C, 10.0.0.44 <-> 133.0.0.33ldp: ldp conn is up; adj 0x60BAC33C, 10.0.0.44:11042 <-> 133.0.0.33:646Table 225 describes the significant fields shown in the sample display.
Related Commands
debug mpls ldp transport events
Prints information about the events related to the LDP peer discovery mechanism.
debug mpls ldp transport events
To display information about events related to the Label Distribution Protocol (LDP) peer discovery mechanism, use the debug mpls ldp transport events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls ldp transport events [peer-acl acl] [interface]
no debug mpls ldp transport events [peer-acl acl] [interface]
Syntax Description
Defaults
Displays information about LDP discovery activity for all peers and all interfaces.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the command to monitor LDP discovery activity. This mechanism is used to determine the devices with which you wish to establish LDP sessions.
This command might generate a great deal of output. Use the peer-acl option or interface option, or both, to limit the output to peers or interfaces of interest.
Note
The command includes all of the output generated by the debug mpls ldp transport connections command.
Examples
The following shows sample output from the debug mpls ldp transport events command:
Router# debug mpls ldp transport eventsldp: enabling ldp on Ethernet1/1/1ldp: Set intf id: intf 0x611D684C, Ethernet1/1/1, not lc-atm, intf_id 0ldp: Set intf id: intf 0x617C5638, ATM0/0.2, not lc-atm, intf_id 0ldp: Send ldp hello; ATM3/0.1, src/dst 8.1.1.1/224.0.0.2, inst_id 1, tcatmldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt 0x8, tcatmldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0ldp: Rcvd ldp hello; Ethernet1/1/1, from 10.105.0.9 (7.1.1.1:0), intf_id 0, opt 0xCldp: ldp Hello from 10.105.0.9 (7.1.1.1:0) to 224.0.0.2, opt 0xCldp: New adj 0x617C5EBC from 10.105.0.9 (7.1.1.1:0), Ethernet1/1/1ldp: Opening ldp conn; adj 0x617C5EBC, 8.1.1.1 <-> 7.1.1.1ldp: ldp conn is up; adj 0x617C5EBC, 8.1.1.1:11013 <-> 7.1.1.1:646ldp: Send ldp hello; ATM3/0.1, src/dst 8.1.1.1/224.0.0.2, inst_id 1, tcatmldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt 0x8, tcatmldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0ldp: Rcvd ldp hello; Ethernet1/1/1, from 10.105.0.9 (7.1.1.1:0), intf_id 0, opt 0xC...ldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0ldp: Send ldp hello; ATM3/0.1, src/dst 8.1no tag ip.0.2, inst_id 1, tcatmldp: disabling ldp on Ethernet1/1/1ldp: Hold timer expired for adj 0x617C5EBC, will close connldp: Closing ldp conn 8.1.1.1:11013 <-> 7.1.1.1:646, adj 0x617C5EBCldp: Adjacency 0x617C5EBC, 10.105.0.9 timed outldp: Adj 0x617C5EBC; state set to closedldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt 0x8, tcatmldp: Ignore Hello from 10.105.0.9, Ethernet1/1/1; no intfTable 226 describes the significant fields in the sample display.
Related Commands
debug mpls lfib cef
To print detailed information about label rewrites being created, resolved, and deactivated as Cisco Express Forwarding (CEF) routes are added, changed, or removed, use the debug mpls lfib cef command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls lfib cef
no debug mpls lfib cef
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
Usage Guidelines
Several lines of output are produced for each route placed into the label-forwarding information base (LFIB). If your router has thousands of labeled routes, be careful about issuing this command. When label switching is first enabled, each of these routes is placed into the LFIB, and several lines of output are displayed for each route.
Examples
The following is sample output from the debug mpls lfib cef command:
Router# debug mpls lfib cefCisco Express Forwarding related TFIB services debugging is ontagcon: tc_ip_rtlookup fail on 10.0.0.0/8:subnet_lookup failedTFIB: route tag chg 10.7.0.7/32,idx=1,inc=Withdrn,outg=Withdrn,enabled=0x2TFIB: fib complete delete: prefix=10.7.0.7/32,inc tag=26,delete_info=1TFIB: deactivate tag rew for 10.7.0.7/32,index=0TFIB: set fib rew: pfx 10.7.0.7/32,index=0,add=0,tag_rew->adj=Ethernet2/3TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parentTFIB: fib scanner start:needed:1,unres:0,mac:0,loadinfo:0TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parentTFIB: fib upd loadinf 10.100.100.100/32,tag=Tun_hd,fib no loadin,tfib no loadinTFIB: fib check cleanup for 10.100.100.100/32,index=0,return_value=0TFIB: fib_scanner_endTFIB: create dynamic entry for 10.11.0.11/32TFIB: call find_route_tags,dist_method=1,next_hop=10.93.0.11,Et2/3TFIB: route tag chg 10.11.0.11/32,idx=0,inc=26,outg=Unkn,enabled=0x3TFIB: create tag info 10.11.0.11/32,inc tag=26,has no infoTFIB: resolve tag rew,prefix=10.11.0.11/32,has tag_info,no parentTFIB: finish fib res 10.11.0.11/32:index 0,parent outg tag no parentTFIB: fib upd loadinf 10.11.0.11/32,tag=26,fib no loadin,tfib no loadinTFIB: set fib rew: pfx 10.11.0.11/32,index=0,add=1,tag_rew->adj=Ethernet2/3tagcon: route_tag_change for: 10.250.0.97/32intag 33, outtag 28, nexthop tsr 10.11.0.11:0TFIB: route tag chg 10.250.0.97/32,idx=0,inc=33,outg=28,enabled=0x3TFIB: deactivate tag rew for 10.250.0.97/32,index=0TFIB: set fib rew: pfx 10.250.0.97/32,index=0,add=0,tag_rew->adj=Ethernet2/3TFIB: create tag info 10.250.0.97/32,inc tag=33,has old infoOn VIP:TFIB: route tag chg 10.13.72.13/32,idx=0,inc=34,outg=Withdrn,enabled=0x3TFIB: deactivate tag rew for 10.13.72.13/32,index=0TFIB: set fib rew: pfx 10.13.72.13/32,index=0,add=0,tag_rew->adj=TFIB: create tag info 10.13.72.13/32,inc tag=34,has old infoTFIB: resolve tag rew,prefix=10.13.72.13/32,has tag_info,no parentTFIB: finish fib res 10.13.72.13/32:index 0,parent outg tag no parentTFIB: set fib rew: pfx 10.100.100.100/32,index=0,add=0,tag_rew->adj=TFIB: create tag info 10.100.100.100/32,inc tag=37,has old infoTFIB: resolve tag rew,prefix=10.100.100.100/32,has tag_info,no parentTFIB: finish fib res 10.100.100.100/32:index 0,parent outg tag no parentTFIB: fib upd loadinf 10.100.100.100/32,tag=37,fib no loadin,tfib no loadinTable 227 lists the significant fields shown in the display.
See Table 229 for a description of special labels that appear in the output of this debug command.
Related Commands
debug mpls lfib enc
To print detailed information about label encapsulations while label rewrites are created or updated and placed in the label-forwarding information base (LFIB), use the debug mpls lfib enc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls lfib enc
no debug mpls lfib enc
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
Usage Guidelines
Several lines of output are produced for each route placed into the LFIB. If your router has thousands of labeled routes, issue this command with care. When label switching is first enabled, each of these routes is placed into the LFIB and a label encapsulation is created. The command output shows you on which adjacency the label rewrite is being created and the labels assigned.
Examples
The following is sample output from the debug mpls lfib enc command. This example shows the encapsulations for three routes that have been created and placed into the LFIB.
Router# debug mpls lfib encTFIB: finish res:inc tag=28,outg=Imp_null,next_hop=10.93.72.13,Ethernet4/0/3TFIB: update_mac, mac_length = 14,addr=10.93.72.13,idb=Ethernet4/0/3TFIB: get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7TFIB: get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79TFIB: encaps:inc=28,outg=Imp_null,idb:Ethernet4/0/3,sizes 14,14,1504,type 0TFIB: finish res:inc tag=30,outg=27,next_hop=10.93.72.13,Ethernet4/0/3TFIB: get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7TFIB: get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79TFIB: encaps:inc=30,outg=27,idb:Ethernet4/0/3,sizes 14,18,1500,type 0TFIB: finish res:inc tag=30,outg=10,next_hop=0.0.0.0,ATM0/0.1TFIB: get ip adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=7TFIB: get tag adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=79TFIB: encaps:inc=30,outg=10,idb:ATM0/0,sizes 4,8,4470,type 1Table 228 describes the significant fields shown in the display.
Table 229 describes the special labels, which sometimes appear in the debug output, and their meanings.
Related Commands
debug mpls lfib lsp
To print detailed information about label rewrites being created and deleted as label-switched path (LSP) tunnels are added or removed, use the debug mpls lfib lsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls lfib lsp
no debug mpls lfib lsp
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
Examples
The following is sample output from the debug mpls lfib lsp command:
Router# debug mpls lfib lspTSP-tunnel related TFIB services debugging is onTFIB: tagtun,next hop=10.93.72.13,inc=35,outg=1,idb=Et4/0/3TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=7,nh=10.93.72.13TFIB: tagtun,next hop=10.92.0.7,inc=36,outg=1,idb=Et4/0/2TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun tag chg linec,fiblc=0,in tg=36,o tg=1,if=6,nh=10.92.0.7TFIB: tagtun_delete, inc = 36tagtun tag del linec,itag=12TFIB: tagtun_delete, inc = 35tagtun tag del linec,itag=12TFIB: tagtun,next hop=10.92.0.7,inc=35,outg=1,idb=Et4/0/2TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=6,nh=10.92.0.7On VIP:TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.92.0.7,if=6TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTable 230 describes the significant fields shown in the sample display.
Related Commands
debug mpls lfib state
To trace what happens when label switching is enabled or disabled, use the debug mpls lfib state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls lfib state
no debug mpls lfib state
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
Usage Guidelines
Use this command when you wish to trace what happens to the label-forwarding information base (LFIB) when you issue the mpls ip or the mpls tsp-tunnel command.
Examples
The following is sample output from the debug mpls lfib state command:
Router# debug mpls lfib stateTFIB enable/disable state debugging is onTFIB: Upd tag sb 6(status:0xC1,tmtu:1500,VPI:1-1 VC=0/32,et:0/0/0),lc 0x0TFIB: intf status chg: idb=Et4/0/2,status=0xC1,oldstatus=0xC3TFIB: interface dyntag change,change in state to Ethernet4/0/2TFIB: enable entered, table exists,enabler type=0x2TFIB: enable, TFIB already enabled, types now 0x3,returningTFIB: enable entered, table exists,enabler type=0x1TFIB: disable entered, table exists,type=0x1TFIB: cleanup: tfib[32] still non-0On linecard only:TFIB: disable lc msg recvd, type=0x1TFIB: Ethernet4/0/1 fibidb subblock message receivedTFIB: enable lc msg recvd, type=0x1TFIB: Tunnel301 set encapfix to 0x6016A97CTable 231 describes the significant fields shown in the display.
Related Commands
debug mpls lfib struct
To trace the allocation and freeing of label-forwarding information base (LFIB)-related data structures, such as the LFIB itself, label rewrites, and label_info data, use the debug mpls lfib struct command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls lfib struct
no debug mpls lfib struct
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
Examples
The following is sample output from the debug mpls lfib struct command:
Router# debug mpls lfib structTFIB data structure changes debugging is onTFIB: delete tag rew, incoming tag 32TFIB: remove from tfib,inc tag=32TFIB: set loadinfo,tag=32,no old loadinfo,no new loadinfoTFIB: TFIB not in use. Checking for entries.TFIB: cleanup: tfib[0] still non-0TFIB: remove from tfib,inc tag=Tun_hdTFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfoTFIB: TFIB freed.TFIB: enable, TFIB allocated, size 4024 bytes, maxtag = 500TFIB: create tag rewrite: inc Tun_hd,outg UnknTFIB: add to tfib at Tun_hd, first in circular list, mac=0,enc=0TFIB: delete tag rew, incoming tag Tun_hdTFIB: remove from tfib,inc tag=Tun_hdTFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfoTFIB: create tag rewrite: inc Tun_hd,outg UnknTFIB: add to tfib at Tun_hd, first in circular list, mac=0,enc=0TFIB: create tag rewrite: inc 26,outg UnknTFIB: add to tfib at 26, first in circular list, mac=0,enc=0TFIB: add to tfib at 27, added to circular list, mac=0,enc=0TFIB: delete tag rew, incoming tag Tun_hdTFIB: remove from tfib,inc tag=Tun_hdTFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfoTFIB: add to tfib at 29, added to circular list, mac=4,enc=8TFIB: delete tag rew, incoming tag 29TFIB: remove from tfib,inc tag=29Table 232 describes the significant fields shown in the display.
Related Commands
debug mpls lspv
To display information related to the Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Ping/Traceroute feature, use the debug mpls lspv command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls lspv [tlv] [error] [event] [ipc] [packet [data | error]] [path-discovery] [multipath] [all]
no debug mpls lspv
Syntax Description
tlv
(Optional) Displays MPLS echo packet type, length, values (TLVs) information as it is being coded and decoded.
error
(Optional) Displays errors during MPLS echo request and echo reply encoding and decoding. See Table 233.
event
(Optional) Displays MPLS echo request, reply send and receive event information.
ipc
(Optional) Interprocess communication. Displays debug information regarding communication between the route processor and line cards.
packet data
(Optional) Displays detailed debug information for MPLS echo packets that are sent and received. This output is seen only on the originating router and the router generating the reply.
packet error
(Optional) Displays packet errors for MPLS echo request and reply. No output is expected for this command.
path-discovery
(Optional) Provides information regarding LSP traceroute path discovery operations.
multipath
(Optional) Displays multipath information.
all
(Optional) Enables all the command keywords.
Command Default
MPLS LSP debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to monitor activity associated with the ping mpls and the trace mpls commands.
Table 233 lists the messages displayed by the debug mpls lspv error command and the reason for each error message.
Examples
The following is sample output from the ping mpls command when LSPV event debugging is enabled:
Router# debug mpls lspv eventLSPV event debugging is onRouter# ping mpls ipv4 10.131.159.252/32 repeat 1Sending 1, 100-byte MPLS Echos to 10.131.159.252/32,timeout is 2 seconds, send interval is 0 msec:Codes: '!' - success, 'Q' - request not transmitted,'.' - timeout, 'U' - unreachable,'R' - downstream router but not targetType escape sequence to abort.!Success rate is 100 percent (1/1), round-trip min/avg/max = 48/48/48 msRouter#*Dec 31 19:31:15.366: LSPV:waiting for 2 seconds*Dec 31 19:31:15.366: LSPV: sender_handle: 2000002D, Event Echo Requests Start, [Idle->Waiting for Echo Reply]*Dec 31 19:31:15.414: LSPV: sender_handle: 2000002D, Event Echo Reply Received, [Waiting for Echo Reply->Waiting for Interval]*Dec 31 19:31:15.466: LSPV: sender_handle: 2000002D, Event Echo Requests Cancel, [Waiting for Interval->Idle]Router# undebug allAll possible debugging has been turned offThe following is sample output from the ping mpls command when LSPV TLV debugging is enabled:
Router# debug mpls lspv tlvLSPV tlv debugging is onRouter# ping mpls ipv4 10.131.159.252/32 repeat 1Sending 1, 100-byte MPLS Echos to 10.131.159.252/32,timeout is 2 seconds, send interval is 0 msec:Codes: '!' - success, 'Q' - request not transmitted,'.' - timeout, 'U' - unreachable,'R' - downstream router but not targetType escape sequence to abort.!Success rate is 100 percent (1/1), round-trip min/avg/max = 40/40/40 msRouter#*Dec 31 19:32:32.566: LSPV: Echo Hdr encode: version 1, msg type 1, reply mode 2 , return_code 0, return_subcode 0, sender handle 9400002E, sequence number 1, timestamp sent 14:32:32 EST Wed Dec 31 2003, timestamp rcvd 19:00:00 EST Thu Dec 31 1899*Dec 31 19:32:32.566: LSPV: IPV4 FEC encode: destaddr 10.131.159.252/32*Dec 31 19:32:32.566: LSPV: Pad TLV encode: type 1, size 18, pattern 0xABCD*Dec 31 19:32:32.606: LSPV: Echo Hdr decode: version 1, msg type 2, reply mode 2, return_code 3, return_subcode 0, sender handle 9400002E, sequence number 1, timestamp sent 14:32:32 EST Wed Dec 31 2003, timestamp rcvd 14:32:32 EST Wed Dec 31 2003Router# undebug allAll possible debugging has been turned offThe following is sample output from the trace mpls multipath command when LSPV multipath debugging is on:
Router# debug mpls lspv multipathmultipath information debugging is onRouter# trace mpls multipath ip 10.5.5.5/32Starting LSP Multipath Traceroute for 10.5.5.5/32Codes: '!' - success, 'Q' - request not sent, '.' - timeout,'L' - labeled output interface, 'B' - unlabeled output interface,'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,'P' - no rx intf label prot, 'p' - premature termination of LSP,'R' - transit router, 'I' - unknown upstream index,'X' - unknown return code, 'x' - return code 0Type escape sequence to abort.LL*Aug 30 20:39:03.719: LSPV: configuring bitmask multipath, base 0x7F000000, bitmapsize 32, start 0x7F000000, numbits 32*Aug 30 20:39:03.719: LSPV: multipath info: info_length 4, bitmapsize 32, multipath_length 8, start 127.0.0.0, base 127.0.0.0, numbits 32*Aug 30 20:39:03.719: LSPV: multipath info: info_length 4, bitmapsize 32, multipath_length 8, start 127.0.0.0, base 127.0.0.0, numbits 32*Aug 30 20:39:03.719: LSPV: getnext bit_cursor 0, index 0, mask 0x80000000*Aug 30 20:39:03.719: LSPV: next addr 127.0.0.0*Aug 30 20:39:03.719: LSPV: multipath info: datagramsize 8*Aug 30 20:39:03.719: 7F 00 00 00 FF FF FF FF*Aug 30 20:39:04.007: LSPV: multipath info: !Path 0 found,output interface Et1/0 source 10.2.3.2 destination 172.17.0.0Paths (found/broken/unexplored) (1/0/0)Echo Request (sent/fail) (3/0)Echo Reply (received/timeout) (3/0)Total Time Elapsed 924 msRouter# datagramsize 8*Aug 30 20:39:04.007: 7F 00 00 00 FF FF FF FF*Aug 30 20:39:04.007: LSPV: ds map convert: rtr_id A030404, mtu 1500 intf_addr 10.3.4.4 hashkey 8, multipath length 8, info 2130706432*Aug 30 20:39:04.007: LSPV: multipath info: hashkey type 8, base 0x7F000000, bitmapsize 32, info0 0xFFFFFFFF*Aug 30 20:39:04.007: LSPV: multipath info: info_length 4, bitmapsize 32, multipath_length 8, start 172.17.0.0, base 172.17.0.0, numbits 32*Aug 30 20:39:04.007: LSPV: getnext bit_cursor 0, index 0, mask 0x80000000*Aug 30 20:39:04.007: LSPV: next addr 172.17.0.0*Aug 30 20:39:04.007: LSPV: multipath info: datagramsize 8*Aug 30 20:39:04.007: 7F 00 00 00 FF FF FF FF*Aug 30 20:39:04.299: LSPV: multipath info: datagramsize 8*Aug 30 20:39:04.299: 7F 00 00 00 FF FF FF FF*Aug 30 20:39:04.299: LSPV: ds map convert: rtr_id A040505, mtu 1504 intf_addr 10.4.5.5 hashkey 8, multipath length 8, info 2130706432*Aug 30 20:39:04.299: LSPV: multipath info: hashkey type 8, base 0x7F000000, bitmapsize 32, info0 0xFFFFFFFF*Aug 30 20:39:04.299: LSPV: multipath info: info_length 4, bitmapsize 32, multipath_length 8, start 172.17.0.0, base 172.17.0.0, numbits 32*Aug 30 20:39:04.299: LSPV: getnext bit_cursor 0, index 0, mask 0x80000000*Aug 30 20:39:04.299: LSPV: next addr 127.0.0.0*Aug 30 20:39:04.299: LSPV: multipath info: datagramsize 8*Aug 30 20:39:04.299: 7F 00 00 00 FF FF FF FFRouter# undebug allmultipath information debugging is offRelated Commands
ping mpls
Checks MPLS LSP connectivity.
trace mpls
Discovers MPLS LSP routes that packets will actually take when traveling to their destinations.
debug mpls packets
To display labeled packets switched by the host router, use the debug mpls packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls packets [interface]
no debug mpls packets [interface]
Syntax Description
Defaults
Displays all labeled packets regardless of interface.
Command Modes
Privileged EXEC
Command History
11.1CT
This command was introduced.
12.1(3)T
This command was modified to reflect new MPLS IETF terminology and CLI syntax.
Usage Guidelines
The optional interface parameter restricts the display to only those packets received or sent on the indicated interface.
Note
Examples
The following is sample output from the debug mpls packets command:
Router# debug mpls packetsTAG: Hs3/0: recvd: CoS=0, TTL=254, Tag(s)=27TAG: Hs0/0: xmit: (no tag)TAG: Hs0/0: recvd: CoS=0, TTL=254, Tag(s)=30TAG: Hs3/0: xmit: CoS=0, TTL=253, Tag(s)=27Table 234 describes the significant fields shown in the display.
Related Commands
debug mpls static binding
To display information related to static binding events, use the debug mpls static binding command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls static binding [vrf vpn-name]
no debug mpls static binding [vrf vpn-name]
Syntax Description
vrf vpn-name
Displays information only for the specified VPN routing and forwarding instance (vpn-name).
Defaults
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug mpls static binding command to troubleshoot problems related to MPLS static labels or VRF aware MPLS static labels. If you specify the vrf keyword, debug is enabled only for a specified VRF.
Examples
The following is sample output from the debug mpls static binding command:
Router# debug mpls static binding vrf vpn100MPLS Static label bindings debugging is on00:15:13: mpls: Add remote static binding: 59.0.0.0/8; label 0; nexthop 165.13.0.8:000:15:13: mpls: Add static label binding for 59.0.0.0/800:15:13: mpls: Add static label binding for 107.0.0.0/800:15:13: mpls: Add remote static binding: 107.0.0.0/8; label 2607; nexthop 166.0.0.66:000:15:13: mpls: Add static label binding for 130.66.0.0/1600:15:18: mpls: Periodic static label adjust00:15:18: mpls: Static label update: 59.0.0.0/800:15:18: Add remote label: nexthop: 165.13.0.8:0; label: 000:15:18: mpls: Periodic static label adjust00:15:18: mpls: Static label update: 107.0.0.0/800:15:18: Waiting for withdrawal of dynamic local label 5500:15:18: Add remote label: nexthop: 166.0.0.66:0; label: 260700:15:18: mpls: Periodic static label adjust00:15:18: mpls: Static label update: 130.66.0.0/1600:15:18: Waiting for withdrawal of dynamic local label 1700:15:28: mpls: Periodic static label adjust00:15:28: mpls: Periodic static label adjust00:15:28: mpls: Static label update: 107.0.0.0/800:15:28: Local label 55 added to tib00:15:28: Signal route tag change, in label 55;out label 8388611; nh 199.44.44.7700:15:28: mpls: Periodic static label adjust00:15:28: mpls: Static label update: 130.66.0.0/1600:15:28: Local label 17 added to tib00:15:28: Signal route tag change, in label 17;out label 8388611; nh 199.44.44.6600:15:38: mpls: Periodic static label adjust00:15:38: mpls: Periodic static label adjust00:15:38: mpls: Periodic static label adjustRelated Commands
mpls static binding ipv4 vrf
Binds a prefix to a local label.
show debug
Displays active debug output.
debug mpls traffic-eng areas
To print information about traffic engineering area configuration change events, use the debug mpls traffic-eng areas command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng areas
no debug mpls traffic-eng areas
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, information is printed about traffic engineering area configuration change events:
Router# debug mpls traffic-eng areasTE-AREAS:isis level-1:up eventTE-PCALC_LSA:isis level-1debug mpls traffic-eng autoroute
To print information about automatic routing over traffic engineering tunnels, use the debug mpls traffic-eng autoroute command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng autoroute
no debug mpls traffic-eng autoroute
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, information is printed about automatic routing over traffic engineering tunnels:
Router# debug mpls traffic-eng autorouteTE-Auto:announcement that destination 0001.0000.0003.00 has 1 tunnelsTunnel1 (traffic share 333, nexthop 10.112.0.12)debug mpls traffic-eng link-management admission-control
To print information about traffic engineering label-switched path (LSP) admission control on traffic engineering interfaces, use the debug mpls traffic-eng link-management admission-control command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management admission-control [detail] [acl-number]
no debug mpls traffic-eng link-management admission-control [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-number argument were added.
Examples
In the following example, information is printed about traffic engineering LSP admission control on traffic engineering interfaces:
Router# debug mpls traffic-eng link-management admission-controlTE-LM-ADMIT:tunnel 10.106.0.6 1_10002:created [total 4]TE-LM-ADMIT:tunnel 10.106.0.6 1_10002: "None" -> "New"TE-LM-ADMIT:tunnel 10.106.0.6 1_10002: "New" -> "Admitting 2nd Path Leg"TE-LM-ADMIT:tunnel 10.106.0.6 1_10002: "Admitting 2nd Path Leg" -> "Path Admitted"TE-LM-ADMIT:Admission control has granted Path query for 10.106.0.6 1_10002 (10.112.0.12) on link Ethernet4/0/1 [reason 0]TE-LM-ADMIT:tunnel 10.106.0.6 1_10002: "Path Admitted" -> "Admitting 1st Resv Leg"TE-LM-ADMIT:tunnel 10.106.0.6 1_10002: "Admitting 1st Resv Leg" -> "Resv Admitted"TE-LM-ADMIT:Admission control has granted Resv query for 10.106.0.6 1_10002 (10.112.0.12) on link Ethernet4/0/1 [reason 0]debug mpls traffic-eng link-management advertisements
To print information about resource advertisements for traffic engineering interfaces, use the debug mpls traffic-eng link-management advertisements command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management advertisements [detail] [acl-number]
no debug mpls traffic-eng link-management advertisements [detail] [acl-number]
Syntax Description
detail
(Optional) Prints detailed debugging information.
acl-number
(Optional) Uses the specified access list to filter the debugging information.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, detailed debugging information is printed about resource advertisements for traffic engineering interfaces:
Router# debug mpls traffic-eng link-management advertisements detailTE-LM-ADV:area isis level-1:IGP announcement:link Et4/0/1:info changedTE-LM-ADV:area isis level-1:IGP msg:link Et4/0/1:includes subnet type (2), described nbrs (1)TE-LM-ADV:area isis level-1:IGP announcement:link Et4/0/1:info changedTE-LM-ADV:area isis level-1:IGP msg:link Et4/0/1:includes subnet type (2), described nbrs (1)TE-LM-ADV:LSA:Flooding manager received message:link information change (Et4/0/1)TE-LM-ADV:area isis level-1:*** Flooding node information ***System Information::Flooding Protocol: ISISHeader Information::IGP System ID: 0001.0000.0001.00MPLS TE Router ID: 10.106.0.6Flooded Links: 1Link ID:: 0Link IP Address: 10.1.0.6IGP Neighbor: ID 0001.0000.0001.02Admin. Weight: 10Physical Bandwidth: 10000 kbits/secMax Reservable BW: 5000 kbits/secDownstream::Reservable Bandwidth[0]: 5000 kbits/secReservable Bandwidth[1]: 2000 kbits/secReservable Bandwidth[2]: 2000 kbits/secReservable Bandwidth[3]: 2000 kbits/secReservable Bandwidth[4]: 2000 kbits/secReservable Bandwidth[5]: 2000 kbits/secReservable Bandwidth[6]: 2000 kbits/secAttribute Flags: 0x00000000Table 235 describes the significant fields shown in the display.
debug mpls traffic-eng link-management bandwidth-allocation
To print detailed information about bandwidth allocation for traffic engineering label-switched paths (LSPs), use the debug mpls traffic-eng link-management bandwidth-allocation command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management bandwidth-allocation [detail] [acl-number]
no debug mpls traffic-eng link-management bandwidth-allocation [detail] [acl-number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T. The detail keyword and the acl-number argument were added.
Examples
In the following example, information is printed about bandwidth allocation for traffic engineering LSPs:
Router# debug mpls traffic-eng link-management bandwidth-allocationTE-LM-BW:tunnel 10.106.0.6 1_10002:requesting Downstream bw hold (3000000 bps [S]) on link Et4/0/1TE-LM-BW:tunnel 10.106.0.6 1_10002:Downstream bw hold request succeededTE-LM-BW:tunnel 10.106.0.6 1_10002:requesting Downstream bw lock (3000000 bps [S]) on link Et4/0/1TE-LM-BW:tunnel 10.106.0.6 1_10002:Downstream bw lock request succeededЧ_„RsRelated Commands
debug mpls traffic-eng link-management errors
To print information about errors encountered during any traffic engineering link management procedure, use the debug mpls traffic-eng link-management errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management errors [detail]
no debug mpls traffic-eng link-management errors [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, detailed debugging information is printed about errors encountered during a traffic engineering link management procedure:
Router# debug mpls traffic-eng link-management errors detail00:04:48 TE-LM-ROUTING: link Et1/1/1: neighbor 0010.0000.0012.01: add to IP peer db failedRelated Commands
debug mpls traffic-eng link-management events
To print information about traffic engineering link management system events, use the debug mpls traffic-eng link-management events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management events [detail]
no debug mpls traffic-eng link-management events [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
Examples
In the following example, detailed debugging information is printed about traffic engineering link management system events:
Router# debug mpls traffic-eng link-management events detailTE-LM-EVENTS:stopping MPLS TE Link Management processTE-LM-EVENTS:MPLS TE Link Management process dying nowdebug mpls traffic-eng link-management igp-neighbors
To print information about changes to the link management database of Interior Gateway Protocol (IGP) neighbors, use the debug mpls traffic eng link-management igp-neighbors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management igp-neighbors [detail]
no debug mpls traffic-eng link-management igp-neighbors [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
Examples
In the following example, detailed debugging information is printed about changes to the link management database of IGP neighbors:
Router# debug mpls traffic-eng link-management igp-neighbors detailTE-LM-NBR:link AT0/0.2:neighbor 0001.0000.0002.00:created (isis level-1, 10.42.0.10, Up)[total 2]Related Commands
debug mpls traffic-eng link-management events
Prints information about traffic engineering-related ISIS events.
debug mpls traffic-eng link-management links
To print information about traffic engineering link management interface events, use the debug mpls traffic-eng link-management links command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management links [detail]
no debug mpls traffic-eng link-management links [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
Examples
In the following example, detailed debugging information is printed about traffic engineering link management interface events:
Router# debug mpls traffic-eng link-management links detailTE-LM-LINKS:link AT0/0.2:RSVP enabledTE-LM-LINKS:link AT0/0.2:increasing RSVP bandwidth from 0 to 5000000TE-LM-LINKS:link AT0/0.2:created [total 2]TE-LM-LINKS:Binding MPLS TE LM Admission Control as the RSVP Policy Server on ATM0/0.2TE-LM-LINKS:Bind attempt succeededTE-LM-LINKS:link AT0/0.2:LSP tunnels enableddebug mpls traffic-eng link-management preemption
To print information about traffic engineering label-switched path (LSP) preemption, use the debug mpls traffic-eng link-management preemption command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management preemption [detail]
no debug mpls traffic-eng link-management preemption [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, detailed debugging information is printed about traffic engineering LSP preemption:
Router# debug mpls traffic-eng link-management preemption detailTE-LM-BW:preempting Downstream bandwidth, 1000000, for tunnel 10.106.0.6 2_2TE-LM-BW:building preemption list to get bandwidth, 1000000, for tunnel 10.106.0.6 2_2 (priority 0)TE-LM-BW:added bandwidth, 3000000, from tunnel 10.106.0.6 1_2 (pri 1) to preemption listTE-LM-BW:preemption list build to get bw, 1000000, succeeded (3000000)TE-LM-BW:preempting bandwidth, 1000000, using plist with 1 tunnelsTE-LM-BW:tunnel 10.106.0.6 1_2:being preempted on AT0/0.2 by 10.106.0.6 2_2TE-LM-BW:preemption of Downstream bandwidth, 1000000, succeededdebug mpls traffic-eng link-management routing
To print information about traffic engineering link management routing resolutions that can be performed to help Resource Reservation Protocol (RSVP) interpret explicit route objects, use the debug mpls traffic-eng link-management routing command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng link-management routing [detail]
no debug mpls traffic-eng link-management routing [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
Examples
In the following example, detailed debugging information is printed about traffic engineering link management routing resolutions that can be performed to help RSVP interpret explicit route objects:
Router# debug mpls traffic-eng link-management routing detailTE-LM-ROUTING:route options to 10.42.0.10:building list (w/ nhop matching)TE-LM-ROUTING:route options to 10.42.0.10:adding {AT0/0.2, 10.42.0.10}TE-LM-ROUTING:route options to 10.42.0.10:completed list has 1 linksRelated Commands
debug mpls traffic-eng load-balancing
To print information about unequal cost load balancing over traffic engineering tunnels, use the debug mpls traffic-eng load-balancing command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng load-balancing
no debug mpls traffic-eng load-balancing
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, information is printed about unequal cost load balancing over traffic engineering tunnels:
Router# debug mpls traffic-eng load-balancingTE-Load:10.210.0.0/16, 2 routes, loadbalancing based on MPLS TE bandwidthTE-Load:10.200.0.0/16, 2 routes, loadbalancing based on MPLS TE bandwidthdebug mpls traffic-eng path
To print information about traffic engineering path calculation, use the debug mpls traffic-eng path command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng path {num | lookup | spf | verify}
no debug mpls traffic-eng path {num | lookup | spf | verify}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, information is printed about the calculation of the traffic engineering path:
Router# debug mpls traffic-eng path lookupTE-PCALC:Tunnel1000 Path Setup to 10.110.0.10:FULL_PATHTE-PCALC:bw 0, min_bw 0, metric:0TE-PCALC:setup_pri 0, hold_pri 0TE-PCALC:affinity_bits 0x0, affinity_mask 0xFFFFTE-PCALC_PATH:create_path_hoplist:ip addr 10.42.0.6 unknown.debug mpls traffic-eng topology change
To print information about traffic engineering topology change events, use the debug mpls traffic-eng topology change command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng topology change
no debug mpls traffic-eng topology change
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, information is printed about traffic engineering topology change events:
Router# debug mpls traffic-eng topology changeTE-PCALC_LSA:NODE_CHANGE_UPDATE isis level-1link flags:LINK_CHANGE_BWsystem_id:0001.0000.0001.00, my_ip_address:10.42.0.6nbr_system_id:0001.0000.0002.00, nbr_ip_address 10.42.0.10debug mpls traffic-eng topology lsa
To print information about traffic engineering topology link state advertisement (LSA) events, use the debug mpls traffic-eng topology lsa command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng topology lsa
no debug mpls traffic-eng topology lsa
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, information is printed about traffic engineering topology LSA events:
Router# debug mpls traffic-eng topology lsaTE-PCALC_LSA:node_lsa_add:Received a LSA:flags 0x1 !IGP Id:0001.0000.0001.00, MPLS TE Id:10.106.0.6 is VALID has 2 links (frag_id 0)link[0 ]:Nbr IGP Id:0001.0000.0001.02frag_id 0, Intf Address:0.0.0.0admin_weight:10, attribute_flags:0x0link[1 ]:Nbr IGP Id:0001.0000.0002.00frag_id 0, Intf Address:10.42.0.6, Nbr Intf Address:10.42.0.10admin_weight:100, attribute_flags:0x0TE-PCALC_LSA:(isis level-1):Received lsa:IGP Id:0001.0000.0001.00, MPLS TE Id:10.106.0.6 Router Node id 8link[0 ]:Nbr IGP Id:0001.0000.0002.00, nbr_node_id:9, gen:114frag_id 0, Intf Address:10.42.0.6, Nbr Intf Address:10.42.0.10admin_weight:100, attribute_flags:0x0physical_bw:155520 (kbps), max_reservable_bw:5000 (kbps)allocated_bw reservable_bw allocated_bw reservable_bw------------ ------------- ------------ -------------bw[0]:0 5000 bw[1]:3000 2000bw[2]:0 2000 bw[3]:0 2000bw[4]:0 2000 bw[5]:0 2000bw[6]:0 2000 bw[7]:0 2000debug mpls traffic-eng tunnels errors
To print information about errors encountered during any traffic engineering tunnel management procedure, use the debug mpls traffic-eng tunnels errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng tunnels errors [detail]
no debug mpls traffic-eng tunnels errors [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, detailed debugging information is printed about errors encountered during a traffic engineering tunnel management procedure:
Router# debug mpls traffic-eng tunnels errors00:04:14: LSP-TUNNEL-SIG: Tunnel10012[1]: path verification failed (unprotected) [Can't use link 10.12.4.4 on node 10.0.0.4]debug mpls traffic-eng tunnels events
To print information about traffic engineering tunnel management system events, use the debug mpls traffic-eng tunnels events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng tunnels events [detail]
no debug mpls traffic-eng tunnels events [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.
Examples
In the following example, detailed debugging information is printed about traffic engineering tunnel management system events:
Router# debug mpls traffic-eng tunnels events detailLSP-TUNNEL:received event:interface admin. down [Ethernet4/0/1]LSP-TUNNEL:posting action(s) to all-tunnels:check static LSPsLSP-TUNNEL:scheduling pending actions on all-tunnelsLSP-TUNNEL:applying actions to all-tunnels, as follows:check static LSPsdebug mpls traffic-eng tunnels labels
To print information about Multiprotocol Label Switching (MPLS) label management for traffic engineering tunnels, use the debug mpls traffic-eng tunnels labels command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng tunnels labels [detail] [acl-number]
no debug mpls traffic-eng tunnels labels [detail] [acl-number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-number argument were added.
Examples
In the following example, detailed debugging information is printed about MPLS label management for traffic engineering tunnels:
Router# debug mpls traffic-eng tunnels labels detailLSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:fabric PROGRAM requestLSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:programming label 16 on output interface ATM0/0.2LSP-TUNNEL-LABELS:descriptor 71FA64:continuing "Program" requestLSP-TUNNEL-LABELS:descriptor 71FA64:set "Interface Point Out State" to, allocatedLSP-TUNNEL-LABELS:# of resource points held for "default" interfaces:2LSP-TUNNEL-LABELS:descriptor 71FA64:set "Fabric State" to, enabledLSP-TUNNEL-LABELS:descriptor 71FA64:set "Fabric Kind" to, default (LFIB)LSP-TUNNEL-LABELS:descriptor 71FA64:set "Fabric State" to, setLSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:fabric PROGRAM replyTo restrict output to information about a single tunnel, you can configure an access list and supply it to the debug command. Configure the access list as follows:
Router(config-ext-nacl)# permit udp host scr_address host dst_address eq tun intfcFor example, if tunnel 10012 has destination 10.0.0.11 and source 10.0.0.4, as determined by the show mpls traffic-eng tunnels command, the following access list could be configured and added to the debug command:
Router(config-ext-nacl)# permit udp host 10.0.0.4 10.0.0.11 eq 10012debug mpls traffic-eng tunnels reoptimize
To print information about traffic engineering tunnel reoptimizations, use the debug mpls traffic-eng tunnels reoptimize command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng tunnels reoptimize [detail] [acl-number]
no debug mpls traffic-eng tunnels reoptimize [detail] [acl-number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-number argument were added.
Examples
In the following example, detailed debugging information is printed about traffic engineering tunnel reoptimizations that match access list number 101:
Router# debug mpls traffic-eng tunnels reoptimize detail 101LSP-TUNNEL-REOPT:Tunnel1 curr option 2 (0x6175CF8C), activate new option 2LSP-TUNNEL-REOPT:Tunnel1 new path:option 2 [10002], weight 20LSP-TUNNEL-REOPT:Tunnel1 old path:option 2 [2], weight 110LSP-TUNNEL-REOPT:Tunnel1 [10002] set as reoptLSP-TUNNEL-REOPT:Tunnel1 path option 2 [10002] installing as currentLSP-TUNNEL-REOPT:Tunnel1 [2] removed as currentLSP-TUNNEL-REOPT:Tunnel1 [2] set to delayed cleanLSP-TUNNEL-REOPT:Tunnel1 [10002] removed as reoptLSP-TUNNEL-REOPT:Tunnel1 [10002] set to currentdebug mpls traffic-eng tunnels signalling
To print information about traffic engineering tunnel signalling operations, use the debug mpls traffic-eng tunnels signalling command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng tunnels signalling [detail] [acl-number]
no debug mpls traffic-eng tunnels signalling [detail] [acl-number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-number argument were added.
Examples
In the following example, detailed debugging information is printed about traffic engineering tunnel signalling operations that match access list number 101:
Router# debug mpls traffic-eng tunnels signalling detail 101LSP-TUNNEL-SIG:tunnel Tunnel1 [2]:RSVP head-end openLSP-TUNNEL-SIG:tunnel Tunnel1 [2]:received Path NHOP CHANGELSP-TUNNEL-SIG:Tunnel1 [2]:first hop change:0.0.0.0 --> 10.1.0.10LSP-TUNNEL-SIG:received ADD RESV request for tunnel 10.106.0.6 1 [2]LSP-TUNNEL-SIG:tunnel 10.106.0.6 1 [2]:path next hop is 10.1.0.10 (Et4/0/1)LSP-TUNNEL-SIG:Tunnel1 [2] notified of new label informationLSP-TUNNEL-SIG:sending ADD RESV reply for tunnel 10.106.0.6 1 [2]debug mpls traffic-eng tunnels state
To print information about state maintenance for traffic engineering tunnels, use the debug mpls traffic-eng tunnels state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng tunnels state [detail] [acl-number]
no debug mpls traffic-eng tunnels state [detail] [acl-number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
In the following example, detailed debugging information is printed about state maintenance for traffic engineering tunnels that match access list number 99:
Router# debug mpls traffic-eng tunnels state detail 99LSP-TUNNEL:tunnel 10.106.0.6 1 [2]: "Connected" -> "Disconnected"LSP-TUNNEL:Tunnel1 received event:LSP has gone downLSP-TUNNEL:tunnel 10.106.0.6 1 [2]: "Disconnected" -> "Dead"LSP-TUNNEL-SIG:Tunnel1:changing state from up to downLSP-TUNNEL:tunnel 10.106.0.6 1 [2]: "Dead" -> "Connected"debug mpls traffic-eng tunnels timers
To print information about traffic engineering tunnel timer management, use the debug mpls traffic-eng tunnels timers command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls traffic-eng tunnels timers [detail] [acl-number]
no debug mpls traffic-eng tunnels timers [detail] [acl-number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)S
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-number argument were added.
Examples
In the following example, detailed debugging information is printed about traffic engineering tunnel timer management:
Router# debug mpls traffic-eng tunnels timers detailLSP-TUNNEL-TIMER:timer fired for Action SchedulerLSP-TUNNEL-TIMER:timer fired for Tunnel Head Checkupdebug mpls xtagatm cross-connect
To display requests and responses for establishing and removing cross-connects on the controlled ATM switch, use the debug mpls xtagatm cross-connect command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls xtagatm cross-connect
no debug mpls xtagatm cross-connect
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
Usage Guidelines
This command monitors requests to establish or remove cross-connects from XmplsATM interfaces to the Virtual Switch Interface (VSI) master, as well as the VSI master responses to these requests.
Note
Examples
The following is sample output from the debug mpls xtagatm cross-connect command:
Router# debug mpls xtagatm cross-connectXTagATM: cross-conn request; SETUP, userdata 0x17, userbits 0x1, prec 70xC0100 (Ctl-If) 1/32 <-> 0xC0200 (XTagATM0) 0/32XTagATM: cross-conn response; DOWN, userdata 0x60CDCB5C, userbits 0x2, resultOK0xC0200 1/37 --> 0xC0300 1/37Table 236 describes the significant fields shown in the display.
Related Commands
show xtagatm cross-connect
Displays information about remotely connected ATM switches.
debug mpls xtagatm errors
To display information about error and abnormal conditions that occur on XmplsATM interfaces, use the debug mpls xtagatm errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls xtagatm errors
no debug mpls xtagatm errors
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
Usage Guidelines
Use the debug mpls xtagatm errors command to display information about abnormal conditions and events that occur on XmplsATM interfaces.
Examples
The following is sample output from the debug mpls xtagatm errors command:
Router# debug mpls xtagatm errorsXTagATM VC: XTagATM0 1707 2/352 (ATM1/0 1769 3/915): Cross-connect setupfailed NO_RESOURCESThis message indicates a failed attempt to set up a cross-connect for a terminating a virtual circuit (VC) on XmplsATM0. The reason for the failure was a lack of resources on the controlled ATM switch.
debug mpls xtagatm events
To display information about major events that occur on XmplsATM interfaces, not including events for specific XmplsATM virtual circuits (VCs) and switch cross-connects, use the debug mpls xtagatm events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls xtagatm events
no debug mpls xtagatm events
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
Usage Guidelines
Use the debug mpls xtagatm events command to monitor major events that occur on XmplsATM interfaces. This command monitors events that pertain only to XmplsATM interfaces as a whole and does not include any events that pertain to individual XmplsATM VCs or individual switch cross-connects. The specific events that are monitored when the debug mpls xtagatm events command is in effect include the following:
•
•
•
Examples
The following is sample output from the debug mpls xtagatm events command:
Router# debug mpls xtagatm eventsXTagATM: desired cross-connect table size set to 256XTagATM: ExATM API intf event Up, port 0xA0100 (None)XTagATM: ExATM API intf event Down, port 0xA0100 (None)XTagATM: marking all VCs stale on XTagATM0Table 237 describes the significant fields shown in the display.
debug mpls xtagatm vc
To display information about events that affect individual XmplsATM terminating virtual circuits (VCs), use the debug mpls xtagatm vc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug mpls xtagatm vc
no debug mpls xtagatm vc
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced.
12.2(4)T
This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.
Usage Guidelines
Use the debug mpls xtagatm vc command to display detailed information about all events that affect individual XmplsATM terminating VCs.
Note
Examples
The following is sample output from the debug mpls xtagatm vc command:
Router# debug mpls xtagatm vcXTagATM VC: XTagATM1 18 0/32 (ATM1/0 0 0/0): Setup, Down --> UpPendXTagATM VC: XTagATM1 18 0/32 (ATM1/0 88 1/32): Complete, UpPend --> UpXTagATM VC: XTagATM1 19 1/33 (ATM1/0 0 0/0): Setup, Down --> UpPendXTagATM VC: XTagATM0 43 0/32 (ATM1/0 67 1/84): Teardown, Up --> DownPendTable 238 describes the significant fields shown in the display.
Posted: Mon Jul 2 06:44:58 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
