Syntax Description

This command has no arguments or keywords.

Usage Guidelines

You can use the debug tag-switching adjacency command to monitor those instances when entries are updated or added to the adjacency.

Examples

The following is sample output from the debug tag-switching adjacency command:

Router# debug tag-switching adjacency
 
TAG ADJ: add 10.10.0.1, Ethernet0/0/0
TAG ADJ: update 10.10.0.1, Ethernet0/0/0
 

Related Commands

Command	Description
show adjacency	Displays CEF adjacency table information.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

You can use the debug tag-switching atm-tdp api command with the debug tag-switching atm-tdp states command to display more complete information about a TVC.

Examples

The following is sample output from the debug tag-switching atm-tdp api command:

Router# debug tag-switching atm-tdp api
 
Tailend Router Free tag Req 167.50.0.0 on ATM0/0.2 VPI/VCI 1/674
 TAGATM_API: received tag free request
             interface: ATM0/0.2  dir: in  vpi: 1  vci: 674
 TAGATM_API: completed tag free
             interface: ATM0/0.2  vpi: 1  vci: 674
             result: TAGATM_OK
 

Related Commands

Command	Description
debug tag-switching atm-tdp states	Displays information about TVC state transitions as they occur.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

When there are many routes and system activities (that is, shutting down interfaces, learning of new routes, and so forth), the debug tag-switching atm-tdp routes command displays a lot of information that may interfere with system timing. Most commonly, this affects the normal operation of Tag Distribution Protocol (TDP). You should increase the TDP hold time value by using the tag-switching tdp holdtime command.

Examples

The following is sample output from the debug tag-switching atm-tdp routes command:

Router# debug tag-switching atm-tdp routes
 
CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0
tcatmFindRouteTags,153.7.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0
AddNewRoute,153.7.0.0/16,idb=ATM0/0.2
CleanupRoutes,153.7.0.0/16
CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0
tcatmFindRouteTags,153.8.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0
AddNewRoute,153.8.0.0/16,idb=ATM0/0.2
CleanupRoutes,153.8.0.0/16
CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0
tcatmFindRouteTags,153.9.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0
AddNewRoute,153.9.0.0/16,idb=ATM0/0.2
CleanupRoutes,153.9.0.0/16
CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0
tcatmFindRouteTags,153.10.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0
AddNewRoute,153.10.0.0/16,idb=ATM0/0.2
CleanupRoutes,153.10.0.0/16
CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0
tcatmFindRouteTags,153.11.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0
AddNewRoute,153.11.0.0/16,idb=ATM0/0.2
CleanupRoutes,153.11.0.0/16
 

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

When there are many routes and system activities (that is, shutting down interfaces, learning of new routes, and so forth), the debug tag-switching atm-tdp states command outputs a lot of information that may interfere with system timing. Most commonly, this affects the normal operation of Tag Distribution Protocol (TDP). You should increase the TDP hold time value by using the tag-switching tdp holdtime command.

Examples

The following is sample output from the debug tag-switching atm-tdp states command:

Router# debug tag-switching atm-tdp states
 
Transit Output 166.35.0.0 VPI/VCI 1/67 Active -> XmitRelease NoPath
Transit Input 166.35.0.0 VPI/VCI 1/466 Active -> ApiWaitParentLoss ParentLoss
Transit Input 166.35.0.0 VPI/VCI 1/466 ApiWaitParentLoss -> ParentWait ApiSuccess
Transit Input 166.35.0.0 VPI/VCI 1/466 ParentWait -> XmitWithdraw NoPath
Transit Input 166.35.0.0 VPI/VCI 1/466 XmitWithdraw -> XmitWithdraw Transmit
Transit Input 166.35.0.0 VPI/VCI 1/466 XmitWithdraw -> NonExistent Release
Transit Input 166.35.0.0 VPI/VCI 1/466 NonExistent -> NonExistent ApiSuccess
 

Syntax Description

interface

(Optional) Interface or subinterface name.

Usage Guidelines

The optional interface parameter restricts the display to only those packets received or transmitted on the indicated interface.

Caution Use this command with care, because it generates output for every packet processed. Furthermore, enabling this command causes fast and distributed Tag Switching to be disabled for the selected interfaces. Use this command only when traffic on the network is low, so other activity on the system is not adversely affected.

Examples

The following is sample output from the debug tag-switching packets command:

Router# debug tag-switching packets
 
TAG: Hs3/0: recvd: CoS=0, TTL=254, Tag(s)=27
TAG: Hs0/0: xmit: (no tag)
 
TAG: Hs0/0: recvd: CoS=0, TTL=254, Tag(s)=30
TAG: Hs3/0: xmit: CoS=0, TTL=253, Tag(s)=27
 

Syntax Description

This command has no arguments or keywords.

Examples

The following is sample output from the debug tag-switching tdp advertisements command:

Router# debug tag-switching tdp advertisements
 
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 99.101.0.8
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 172.27.32.28
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.105.0.8
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.92.0.8
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.205.0.8
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 210.8.0.8
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.105.0.0/16, tag 1 (#2)
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.102.0.0/16, tag 26 (#4)
tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.227.0.0/16, tag 27 (#6)
 

Related Commands

Command	Description
show tag-switching tdp neighbors	Displays the status of TDP sessions.

Syntax Description

This command has no arguments or keywords.

Examples

The following is sample output from the debug tag-switching tdp bindings command:

Router# debug tag-switching tdp bindings
 
tagcon: tibent(10.105.0.0/16): created; find route tags request
tagcon: tibent(10.105.0.0/16): lcl tag 1 (#2) assigned
tagcon: tibent(10.102.0.0/16): created; find route tags request
tagcon: tibent(10.102.0.0/16): lcl tag 26 (#4) assigned
tagcon: 210.9.0.9:0: 99.101.0.9 added to addr<->tdp ident map
tagcon: 210.9.0.9:0: 172.27.32.29 added to addr<->tdp ident map
tagcon: 210.9.0.9:0: 10.105.0.9 added to addr<->tdp ident map
tagcon: tibent(172.27.32.0/22): rem tag 1 from 210.9.0.9:0 added
tagcon: tibent(200.26.0.0/16): rem tag 30 from 210.9.0.9:0 added
tagcon: tibent(210.8.0.8/32): created; remote tag learned
tagcon: tibent(210.8.0.8/32): rem tag 31 from 210.9.0.9:0 added
 

Related Commands

Command	Description
show tag-switching tdp bindings	Displays the contents of the tag information base.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

The directed neighbor mechanism starts TDP discovery between two TSRs that are not necessarily directly adjacent. This mechanism is used, for instance, to support two-level tagging across a TSP tunnel, and to support traffic engineering metric exchange across a TSP tunnel.

The mechanism is based on an IP address, such as the IP address of the last hop of a TSP tunnel. A TSR wanting to establish a TDP adjacency to some other TSR with a given IP address is the active TSR for that directed neighbor discovery. A TSR willing to respond to that discovery is the passive TSR for that discovery.

As with TDP discovery between adjacent TSRs, it is possible to have multiple directed neighbor discovery sessions running between two TSRs, all supporting a single TDP adjacency.

The debug messages track discovery changes, such as discovery or loss of a directed neighbor. As a detail reflected in the debug prints, discovery of a directed neighbor with IP address X is complete when a TDP adjacency comes up and the far end announces that IP address X is one of its IP addresses.

Examples

The following is sample output from the debug tag-switching tdp directed-neighbors command:

Router# debug tag-switching tdp directed-neighbors
 
tdp_directednbr: TDPDirAdj 10.11.10.11 received address addition notification
tdp_directednbr: TDPDirAdj 10.11.10.11 TDP peer set
tdp_directednbr: TDPDirAdj 10.11.10.11 received address deletion notification
tdp_directednbr: TDPDirAdj 10.11.10.11 peer cleared
 

Related Commands

Command	Description
show tag-switching tdp neighbors	Displays the status of TDP sessions.

s

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

TDP sessions are supported by data structures and state machines at three levels:

The debug tag-switching tdp transport commands provide visibility of activity at the transport level, the debug tag-switching tdp session commands at the protocol level, and the debug tag-switching tdp peer commands at the tag distribution level.

Examples

The following is sample output from the debug tag-switching tdp peer state-machine command:

Router# debug tag tdp peer state-machine
 
tagcon: start TDP TCP timers for 202.0.0.1:1 (pp 0x60D8ABC8)
tagcon: adj 202.0.0.1:1-1 (pp 0x60D8ABC8): Event unsol open
        unsol op pdg -> estab
tagcon: start TDP TCP timers for 210.9.0.9:0 (pp 0x60D93608)
tagcon: adj 210.9.0.9:0 (pp 0x60D93608): Event unsol open
        unsol op pdg -> estab
tagcon: adj 210.9.0.9:0 (pp 0x60D93608): Event down
        estab -> dstroy
tagcon: adj 202.0.0.1:1 (pp 0x60D8ABC8): Event down
        estab -> dstroy
tagcon: start TDP TCP timers for 202.0.0.1:1 (pp 0x60DAC678)
tagcon: adj 202.0.0.1:1-1 (pp 0x60DAC678): Event unsol open
        unsol op pdg -> defrd
tagcon: start TDP TCP timers for 210.9.0.9:0 (pp 0x60D895C4)
tagcon: adj 210.9.0.9:0 (pp 0x60D895C4): Event unsol open
        unsol op pdg -> defrd
tagcon: adj 210.9.0.9:0 (pp 0x60D93608): Event cleanup done
        dstroy -> non-ex
tagcon: adj 210.9.0.9:0 (pp 0x60D895C4): Event undefer
        defrd -> estab
tagcon: adj 202.0.0.1:1 (pp 0x60D8ABC8): Event cleanup done
        dstroy -> non-ex
tagcon: adj 202.0.0.1:1-1 (pp 0x60DAC678): Event undefer
        defrd -> estab
 

Syntax Description

all	(Optional) TDP received PIEs, including periodic keepalive PIEs.

Usage Guidelines

TDP requires periodic transmission of keepalive PIEs. If you do not specify the all option, periodic keepalive PIEs are not displayed.

Examples

The following is sample output from the debug tag-switching tdp pies received command:

Router# debug tag tdp pies received all
 
tdp: Rcvd open PIE from 202.0.0.1 (pp 0x0)
tdp: Rcvd keep_alive PIE from 202.0.0.1:1 (pp 0x0)
tdp: Rcvd request_bind PIE from 202.0.0.1:1 (pp 0x60DAC678)
tdp: Rcvd request_bind PIE from 202.0.0.1:1 (pp 0x60DAC678)
tdp: Rcvd open PIE from 210.9.0.9 (pp 0x0)
tdp: Rcvd keep_alive PIE from 210.9.0.9:0 (pp 0x0)
tdp: Rcvd bind PIE from 202.0.0.1:1 (pp 0x60DAC678)
tdp: Rcvd bind PIE from 202.0.0.1:1 (pp 0x60DAC678)
 

Related Commands

Command	Description
debug tag-switching tdp pies sent	Prints information about state transitions at the tag distribution level.

Syntax Description

all	(Optional) TDP sent PIEs, including periodic keepalive PIEs.

Usage Guidelines

TDP requires periodic transmission of keepalive PIEs. If you do not specify the all option, periodic keepalive PIEs are not displayed.

Examples

The following is sample output from the debug tag-switching tdp pies sent all command:

Router# debug tag tdp pies sent all
 
tdp: Queued open PIE to 210.222.0.222:1 (pp 0x0)
tdp: Sent open PIE to 210.222.0.222:1 (pp 0x0)
tdp: Queued keep_alive PIE to 210.222.0.222:1 (pp 0x0)
tdp: Sent keep_alive PIE to 210.222.0.222:1 (pp 0x0)
tdp: Queued request_bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Sent request_bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Queued request_bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Sent request_bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Queued open PIE to 210.8.0.8 (pp 0x0)
tdp: Queued bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Sent bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Queued bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Sent bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Queued bind PIE to 210.222.0.222:1 (pp 0x60F264C8)
tdp: Queued open PIE to 210.8.0.8 (pp 0x0)
tdp: Sent open PIE to 210.8.0.8 (pp 0x0)
tdp: Queued keep_alive PIE to 210.8.0.8:0 (pp 0x0)
tdp: Sent keep_alive PIE to 210.8.0.8:0 (pp 0x0)
tdp: Queued address PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Sent address PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Queued bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Queued bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Queued bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Queued bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Queued bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Sent bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Sent bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Sent bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Sent bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
tdp: Sent bind PIE to 210.8.0.8:0 (pp 0x60F161AC)
 

Related Commands

Command	Description
debug tag-switching tdp pies received	Prints information about TDP PIEs received from TDP peer devices.
debug tag-switching tdp session io	Prints the contents of TDP PIEs sent to and received from TDP peer devices.

Syntax Description

all	(Optional) TDP session I/O activity, including I/O for periodic keepalives.

Usage Guidelines

TDP sessions are supported by data structures and state machines at three levels:

The debug tag-switching tdp transport commands provide visibility of activity at the transport level, the debug tag-switching tdp session commands at the protocol level, and the debug tag-switching tdp peer commands at the tag distribution level.

TDP requires periodic transmission of keepalive PIEs. If you do not specify the all option, periodic keepalive PIEs are not displayed.

Examples

The following is sample output from the debug tag-switching tdp session io command:

Router# debug tag-switching tdp session io all
 
tdp: Rcvd open PIE from 210.9.0.9 (pp 0x0)
tdp: TDP open PIE: PDU hdr: TDP Id: 210.9.0.9:0; PIE Contents:
  0x00 0x01 0x00 0x10 0xD2 0x09 0x00 0x09 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x04 
  0x01 0x00 0x00 0x1E 
tdp: Sent open PIE to 210.9.0.9:0 (pp 0x0)
tdp: TDP open PIE: PDU hdr: TDP Id: 172.27.32.28:0; PIE Contents:
  0x00 0x01 0x00 0x10 0xAC 0x1B 0x20 0x1C 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x04 
  0x01 0x00 0x00 0x0F 
tdp: Sent keep_alive PIE to 210.9.0.9:0 (pp 0x0)
tdp: TDP keep_alive PIE: PDU hdr: TDP Id: 172.27.32.28:0; PIE Contents:
  0x00 0x01 0x00 0x0C 0xAC 0x1B 0x20 0x1C 0x00 0x00 0x00 0x00 0x05 0x00 0x00 0x00 
tdp: Rcvd keep_alive PIE from 210.9.0.9:0 (pp 0x0)
tdp: TDP keep_alive PIE: PDU hdr: TDP Id: 210.9.0.9:0; PIE Contents:
  0x00 0x01 0x00 0x0C 0xD2 0x09 0x00 0x09 0x00 0x00 0x00 0x00 0x05 0x00 0x00 0x00 
tdp: Rcvd address PIE from 210.9.0.9:0 (pp 0x60E109F0)
tdp: TDP address PIE: PDU hdr: TDP Id: 210.9.0.9:0; PIE Contents:
  0x00 0x01 0x00 0x35 0xD2 0x09 0x00 0x09 0x00 0x00 0x00 0x00 0x08 0x00 0x00 0x29 
  0x00 0x01 0x00 0x03 0x00 0x23 0x20 0x63 0x65 0x00 0x09 0x20 0xAC 0x1B 0x20 0x1D 
  0x20 0x0A 0x69 0x00 0x09 0x20 0x0A 0x5C 0x00 0x09 0x20 0x0A 0x6F 0x00 0x09 0x20 
  0x0A 0xCD 0x00 0x09 0x20 0xD2 0x09 0x00 0x09 
tdp: Rcvd bind PIE from 210.9.0.9:0 (pp 0x60E109F0)
tdp: TDP bind PIE: PDU hdr: TDP Id: 210.9.0.9:0; PIE Contents:
  0x00 0x01 0x00 0xFC 0xD2 0x09 0x00 0x09 0x00 0x00 0x00 0x00 0x02 0x00 0x00 0xF0 
  0x00 0x00 0x00 0x00 0x00 0x01 0x00 0x02 0x00 0xE6 0x00 0x00 0x00 0x00 0x01 0x10 
  0x0A 0x6F 0x00 0x00 0x00 0x00 0x01 0x16 0xAC 0x1B 0x20 0x00 0x00 0x00 0x00 0x01 
  0x10 0xD2 0x09 0x00 0x00 0x00 0x00 0x1A 0x20 0x0A 0x0B 0x00 0x0B 0x00 0x00 0x00 
 

Related Commands

Command	Description
debug tag-switching tdp pies received	Prints information about TDP PIEs received from TDP peer devices.
debug tag-switching tdp pies sent	Prints information about state transitions at the tag distribution level.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

TDP sessions are supported by data structures and state machines at three levels:

The debug tag-switching tdp transport commands provide visibility of activity at the transport level, the debug tag-switching tdp session commands at the protocol level, and the debug tag-switching tdp peer commands at the tag distribution level.

Examples

The following is sample output from the debug tag-switching tdp session state-machine command:

Router# debug tag-switching tdp session state-machine
 
tdp: adj:210.9.0.9(0x60DDBB4C): Event: Xport opened;
     Non-existent -> Init pasv
tdp: tdp_create_ptcl_adj: tp = 0x60DDBB4C, ipaddr = 210.9.0.9
tdp: adj:210.9.0.9(0x60DDBB4C): Event: Xport opened;
     Init pasv -> Init pasv
tdp: adj:10.105.0.9(0x60DDBB4C): Event: Rcv TDP Open;
     Init pasv -> Open rcvd pasv
tdp: adj:10.105.0.9(0x60DDBB4C): Event: Rcv TDP KA;
     Open rcvd pasv -> Oper
tdp: adj:unknown(0x60DDBB4C): Event: Xport closed;
     Oper -> Non-existent
 

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

TDP sessions are supported by data structures and state machines at three levels:

The debug tag-switching tdp transport commands provide visibility of activity at the transport level, the debug tag-switching tdp session commands at the protocol level, and the debug tag-switching tdp peer commands at the tag distribution level.

When two devices establish a TCP connection for a TDP 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 TDP port at the passive device. The passive device waits for the connection to the well known port to be established.

Examples

The following is sample output from the debug tag-switching transport connections command:

Router# debug tag-switching tdp transport connections
 
Debug output at active peer:
 
tdp: Opening conn; adj 0x60F7C604, 210.9.0.9 <-> 172.27.32.28
tdp: Conn is up; adj 0x60F7C604, 210.9.0.9:11018 <-> 172.27.32.28:711
tdp: Hold timer expired for adj 0x60F7C604, will close conn
tdp: Closing conn 210.9.0.9:11018 <-> 172.27.32.28:711, adj 0x60F7C604
 
Debug output at passive peer:
 
tdp: Incoming conn 172.27.32.28:711 <-> 210.9.0.9:11018
tdp: Conn closed by peer; adj 0x60EB5FD4
     172.27.32.28:711 <-> 210.9.0.9:11018, Ethernet1/1/1
tdp: Closing conn 172.27.32.28:711 <-> 210.9.0.9:11018, adj 0x60EB5FD4
 

Related Commands

Command	Description
debug tag-switching tdp transport events	Prints information about the events related to the TDP peer discovery mechanism, which is used to determine the devices with which to establish TDP sessions.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

TDP sessions are supported by data structures and state machines at three levels:

The debug tag-switching tdp transport commands provide visibility of activity at the transport level, the debug tag-switching tdp session commands at the protocol level, and the debug tag-switching tdp peer commands at the tag distribution level.

Examples

The following is sample output from the debug tag-switching tdp transport events command:

Router# debug tag tdp transport events
 
tdp: Rcvd hello; Ethernet1/1/1, from 10.105.0.9 (210.9.0.9:0), intf_id 0, opt 0x4
tdp: Hello from 10.105.0.9 (210.9.0.9:0) to 255.255.255.255, opt 0x4
tdp: New adj 0x60DF6E50 from 10.105.0.9 (210.9.0.9:0), Ethernet1/1/1
tdp: Rcvd hello; ATM3/0.1, from 200.26.0.4 (202.0.0.1:1), intf_id 1, opt 0x4, tcatm
tdp: Rcvd hello; Ethernet1/1/1, from 10.105.0.9 (210.9.0.9:0), intf_id 0, opt 0x4
tdp: Hello from 10.105.0.9 (210.9.0.9:0) to 255.255.255.255, opt 0x4
tdp: Ignore Hello Timer for Ethernet1/1/1; intf not TDP ready
tdp: Send hello; Ethernet1/1/1, src/dst 10.105.0.8/255.255.255.255, inst_id 0
tdp: Incoming conn 172.27.32.28:711 <-> 210.9.0.9:11019
tdp: Found adj 0x60DF6E50 for 210.9.0.9 (Hello xport addr opt)
tdp: New temporary adj 0x61033D38 from 210.9.0.9
tdp: Real adj 0x60DF6E50 bound to 210.9.0.9:0, replacing temp adj 0x61033D38
tdp: Adj 0x61033D38; state set to closed
tdp: Rcvd hello; Ethernet1/1/1, from 10.105.0.9 (210.9.0.9:0), intf_id 0, opt 0x4
tdp: Rcvd hello; ATM3/0.1, from 200.26.0.4 (202.0.0.1:1), intf_id 1, opt 0x4, tcatm
tdp: Send hello; ATM3/0.1, src/dst 99.101.0.8/255.255.255.255, inst_id 1, tcatm
tdp: Rcvd hello; Ethernet1/1/1, from 10.105.0.9 (210.9.0.9:0), intf_id 0, opt 0x4
tdp: Send hello; Ethernet1/1/1, src/dst 10.105.0.8/255.255.255.255, inst_id 0
tdp: Rcvd hello; ATM3/0.1, from 200.26.0.4 (202.0.0.1:1), intf_id 1, opt 0x4, tcatm
 

Related Commands

Command	Description
debug tag-switching tdp transport connections	Prints information about the TCP connections used to support TDP sessions.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

The debug tag-switching tdp transport commands provide visibility of activity at the transport level, the debug tag-switching tdp session commands at the protocol level, and the debug tag-switching tdp peer commands at the tag distribution level.

Examples

The following is sample output from the debug tag-switching tdp transport timers command:

Router# debug tag-switching tdp transport timers
 
tdp: Start holding timer; adj 0x60D5BC10, 200.26.0.4
tdp: Start holding timer; adj 0x60EA9360, 10.105.0.9
tdp: Start holding timer; adj 0x60D5BC10, 200.26.0.4
tdp: Start holding timer; adj 0x60EA9360, 10.105.0.9
tdp: Start holding timer; adj 0x60D5BC10, 200.26.0.4
tdp: Start holding timer; adj 0x60EA9360, 10.105.0.9
 

Related Commands

Command	Description
debug tag-switching tdp transport events	Prints information about the events related to the TDP peer discovery mechanism, which is used to determine the devices with which to establish TDP sessions.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

Several lines of output are produced for each route placed into the TFIB. If your router has thousands of tagged routes, be careful about issuing this command. When Tag Switching is first enabled, each of these routes is placed into the TFIB. If the debug tag-switching tfib cef command is issued, several lines of output are displayed for each route.

Examples

The following is sample output from the debug tag-switching tfib cef command:

Router# debug tag-switching tfib cef
 
Cisco Express Forwarding related TFIB services debugging is on
 
tagcon: tc_ip_rtlookup fail on 10.0.0.0/8:subnet_lookup failed
TFIB: route tag chg 10.7.0.7/32,idx=1,inc=Withdrn,outg=Withdrn,enabled=0x2
TFIB: fib complete delete: prefix=10.7.0.7/32,inc tag=26,delete_info=1
TFIB: deactivate tag rew for 10.7.0.7/32,index=0
TFIB: set fib rew: pfx 10.7.0.7/32,index=0,add=0,tag_rew->adj=Ethernet2/3
TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parent
TFIB: fib scanner start:needed:1,unres:0,mac:0,loadinfo:0
TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parent
TFIB: fib upd loadinf 10.100.100.100/32,tag=Tun_hd,fib no loadin,tfib no loadin
TFIB: fib check cleanup for 10.100.100.100/32,index=0,return_value=0
TFIB: fib_scanner_end
TFIB: create dynamic entry for 10.11.0.11/32
TFIB: call find_route_tags,dist_method=1,next_hop=10.93.0.11,Et2/3
TFIB: route tag chg 10.11.0.11/32,idx=0,inc=26,outg=Unkn,enabled=0x3
TFIB: create tag info 10.11.0.11/32,inc tag=26,has no info
TFIB: resolve tag rew,prefix=10.11.0.11/32,has tag_info,no parent
TFIB: finish fib res 10.11.0.11/32:index 0,parent outg tag no parent
TFIB: fib upd loadinf 10.11.0.11/32,tag=26,fib no loadin,tfib no loadin
TFIB: set fib rew: pfx 10.11.0.11/32,index=0,add=1,tag_rew->adj=Ethernet2/3
tagcon: route_tag_change for: 10.250.0.97/32
        intag 33, outtag 28, nexthop tsr 10.11.0.11:0
TFIB: route tag chg 10.250.0.97/32,idx=0,inc=33,outg=28,enabled=0x3
TFIB: deactivate tag rew for 10.250.0.97/32,index=0
TFIB: set fib rew: pfx 10.250.0.97/32,index=0,add=0,tag_rew->adj=Ethernet2/3
TFIB: create tag info 10.250.0.97/32,inc tag=33,has old info
On VIP:
TFIB: route tag chg 10.13.72.13/32,idx=0,inc=34,outg=Withdrn,enabled=0x3
TFIB: deactivate tag rew for 10.13.72.13/32,index=0
TFIB: 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 info
TFIB: resolve tag rew,prefix=10.13.72.13/32,has tag_info,no parent
TFIB: finish fib res 10.13.72.13/32:index 0,parent outg tag no parent
TFIB: 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 info
TFIB: resolve tag rew,prefix=10.100.100.100/32,has tag_info,no parent
TFIB: finish fib res 10.100.100.100/32:index 0,parent outg tag no parent
TFIB: fib upd loadinf 10.100.100.100/32,tag=37,fib no loadin,tfib no loadin
 

Related Commands

Command	Description
debug tag-switching tfib enc	Prints detailed information about tag encapsulations while tag rewrites are created or updated and placed into the TFIB.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

Several lines of output are produced for each route placed into the TFIB. If your router has thousands of tagged routes, be careful about issuing this command. When Tag Switching is first enabled, each of these routes is placed into the TFIB, and a tag encapsulation is created. When debug tag-switching tfib enc is issued, several lines of output are displayed for each route.

Examples

The following is sample output from the debug tag-switching tfib enc command. This example shows the encapsulations for three routes that have been created and placed into the TFIB.

Router# debug tag-switching tfib enc
 
TFIB: finish res:inc tag=28,outg=Imp_null,next_hop=10.93.72.13,Ethernet4/0/3
TFIB: update_mac, mac_length = 14,addr=10.93.72.13,idb=Ethernet4/0/3
TFIB: get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7
TFIB: get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79
TFIB: encaps:inc=28,outg=Imp_null,idb:Ethernet4/0/3,sizes 14,14,1504,type 0
TFIB: finish res:inc tag=30,outg=27,next_hop=10.93.72.13,Ethernet4/0/3
TFIB: get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7
TFIB: get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79
TFIB: encaps:inc=30,outg=27,idb:Ethernet4/0/3,sizes 14,18,1500,type 0
TFIB: finish res:inc tag=30,outg=10,next_hop=0.0.0.0,ATM0/0.1
TFIB: get ip adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=7
TFIB: get tag adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=79
TFIB: encaps:inc=30,outg=10,idb:ATM0/0,sizes 4,8,4470,type 1
 

Related Commands

Command	Description
debug tag-switching tfib state	Traces what is happening as tag-switching is enabled or disabled.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

Use this command when you wish to trace what happens to the TFIB when you issue tag-switching ip or tag-switching tsp-tunnel commands.

Examples

The following is sample output from the debug tag-switching tfib state command:

Router# debug tag-switching tfib state
 
TFIB enable/disable state debugging is on
TFIB: Upd tag sb 6(status:0xC1,tmtu:1500,VPI:1-1 VC=0/32,et:0/0/0),lc 0x0
TFIB: intf status chg: idb=Et4/0/2,status=0xC1,oldstatus=0xC3
TFIB: interface dyntag change,change in state to Ethernet4/0/2
TFIB: enable entered, table exists,enabler type=0x2
TFIB: enable, TFIB already enabled, types now 0x3,returning
TFIB: enable entered, table exists,enabler type=0x1
TFIB: disable entered, table exists,type=0x1
 
TFIB: cleanup: tfib[32] still non-0
 
On linecard only:
 
TFIB: disable lc msg recvd, type=0x1
TFIB: Ethernet4/0/1 fibidb subblock message received
TFIB: enable lc msg recvd, type=0x1
TFIB: Tunnel301 set encapfix to 0x6016A97C
 

Related Commands

Command	Description
debug tag-switching tfib enc	Prints detailed information about tag encapsulations while tag rewrites are created or updated and placed into the TFIB.
debug tag-switching tfib struct	Traces the allocation and freeing of TFIB-related data structures---the TFIB itself, tag-rewrites, and tag-info data.

Syntax Description

This command has no arguments or keywords.

Examples

The following is sample output from the debug tag-switching tfib struct command:

Router# debug tag-switching tfib struct
 
TFIB data structure changes debugging is on
 
TFIB: delete tag rew, incoming tag 32
TFIB: remove from tfib,inc tag=32
TFIB: set loadinfo,tag=32,no old loadinfo,no new loadinfo
TFIB: TFIB not in use.  Checking for entries.
TFIB: cleanup: tfib[0] still non-0
TFIB: remove from tfib,inc tag=Tun_hd
TFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo
TFIB: TFIB freed.
TFIB: enable, TFIB allocated, size 4024 bytes, maxtag = 500
TFIB: create tag rewrite: inc Tun_hd,outg Unkn
TFIB: add to tfib at Tun_hd, first in circular list, mac=0,enc=0
TFIB: delete tag rew, incoming tag Tun_hd
TFIB: remove from tfib,inc tag=Tun_hd
TFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo
TFIB: create tag rewrite: inc Tun_hd,outg Unkn
TFIB: add to tfib at Tun_hd, first in circular list, mac=0,enc=0
TFIB: create tag rewrite: inc 26,outg Unkn
TFIB: add to tfib at 26, first in circular list, mac=0,enc=0
TFIB: add to tfib at 27, added to circular list, mac=0,enc=0
TFIB: delete tag rew, incoming tag Tun_hd
TFIB: remove from tfib,inc tag=Tun_hd
TFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo
TFIB: add to tfib at 29, added to circular list, mac=4,enc=8
TFIB: delete tag rew, incoming tag 29
TFIB: remove from tfib,inc tag=29
 

Related Commands

Command	Description
debug tag-switching tfib cef	Prints detailed information about tag rewrites being created, resolved, and deactivated as CEF routes are added, changed, or removed.
debug tag-switching tfib enc	Prints detailed information about tag encapsulations while tag rewrites are created or updated and placed into the TFIB.
debug tag-switching tfib state	Traces what is happening as tag-switching is enabled or disabled.

Syntax Description

This command has no arguments or keywords.

Examples

The following is sample output from the debug tag-switching tfib tsp command:

Router# debug tag-switching tfib tsp
 
TSP-tunnel related TFIB services debugging is on
 
TFIB: tagtun,next hop=10.93.72.13,inc=35,outg=1,idb=Et4/0/3
TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=7,nh=10.93.72.13
TFIB: tagtun,next hop=10.92.0.7,inc=36,outg=1,idb=Et4/0/2
TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun tag chg linec,fiblc=0,in tg=36,o tg=1,if=6,nh=10.92.0.7
TFIB: tagtun_delete, inc = 36
tagtun tag del linec,itag=12
TFIB: tagtun_delete, inc = 35
tagtun tag del linec,itag=12
TFIB: tagtun,next hop=10.92.0.7,inc=35,outg=1,idb=Et4/0/2
TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=6,nh=10.92.0.7
 
On VIP:
TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7
TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6
TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7
TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6
TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfo
TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.92.0.7,if=6
TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6
TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo
 

Related Commands

Command	Description
debug tag-switching tfib enc	Prints detailed information about tag encapsulations while tag rewrites are created or updated and placed into the TFIB.

Syntax Description n

events

(Optional) Events signaled to the traffic engineering routing process, periodic timers, and reevaluation of traffic engineering routes.

Examples

The following is sample output from the debug tag-switching traffic-engineering events command:

Router# debug tag-switching traffic-engineering events
 
te_events: event signalled
te_events: traffeng timer
te_events: re-evaluating prefix 1.1.1.1/32
te_events: re-evaluating prefix 2.2.2.2/32
 

Related Commands

Command	Description
show ip traffic-engineering	Displays information about the traffic engineering configuration and metric information associated with it.

Related Commands

Command	Description
show tag-switching tsp-tunnels	Displays information about the configuration and status of selected tunnels.

Examples

The following is sample output from the debug tag-switching traffic-engineering metrics command:

Router# debug tag-switching traffic-engineering metrics
 
Debug output at tunnel head:
te_metric: tdp peer 10.11.0.11:0 announced as up
te_metric: TEAdj (Head) 10.11.0.11:0 allocated (0x60F72940)
te_metric: TunAdj Tunnel13: brought up adj rev 3
te_metric: metric 1.1.1.1/32 requested (entry 0x60F5D4FC, refcnt 1)
te_metric: metric entry queued for transmit (entry 0x60F5D4FC, type 1, rev 17, adj next 0x60F5D4FC)
te_metric: metric 2.2.2.2/32 requested (entry 0x60F78920, refcnt 1)
te_metric: metric entry queued for transmit (entry 0x60F78920, type 1, rev 18, adj next 0x60F5D4FC)
te_metric: metric request (mlist type 2) pdu buffered for 10.11.0.11:0
te_metric: metric request (mlist type 2) pdu buffered for 10.11.0.11:0
te_metric: TEAdj (Head) revision sent updated from 0 to 20
te_metric: metric announce pie received from 10.11.0.11:0
te_metric: metric announce (mlist type 1) pdu received from 10.11.0.11:0
te_metric: metric announce (mlist type 1) pdu received from 10.11.0.11:0
 

Related Commands

Command	Description
show ip traffic-engineering	Displays information about the traffic engineering configuration and metric information associated with it.

Syntax Description

This command has no arguments or keywords.

Usage Guidelines

Traffic engineering overrides IP routing table entries in the forwarding table.

Examples

The following is sample output from the debug tag-switching traffic-engineering routing-table command showing a traffic engineering entry being added and deleted from the forwarding table:

Router# debug tag-switching traffic-engineering routing-table
 
te_rttab: te_rttab add 4.4.4.4/32->Tunnel13
te_rttab: te_rttab delete 4.4.4.4/32
 

Related Commands

Command	Description
show ip traffic-engineering	Displays information about the traffic engineering configuration and metric information associated with it.

Related Commands

Command	Description
debug tag-switching tsp-tunnels signalling	Enables logging of TSP tunnel signaling activity.

The debug tag-switching tsp-tunnels signalling command displays the signaling requests made to RSVP by the TSP tunnels modules at the headend and tail-end routers. It also displays the signaling requests made by RSVP to the TSP tunnels modules at every hop along the path, in order to establish the TSP tunnel state.

Examples

The following is sample output from the debug tag-switching tsp-tunnels signalling command:

Router# debug tag-switching tsp-tunnels signalling
 
Open at tunnel head:
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: RSVP head-end open
Open at tunnel tail:
  TSP-TUNNEL-SIG: received NEW PATH TAIL ARRIVAL event about tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: RSVP tail-end open
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206 NEW PATH TAIL ARRIVAL event handled successfully
State setup at tail hop:
  TSP-TUNNEL-SIG: received ADD RESV request for tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: path previous hop is 10.2.0.10 (Et4/0/2)
  TSP-TUNNEL-SIG: sending ADD RESV reply for tunnel 10.106.0.6 1206
State setup at intermediate hop:
  TSP-TUNNEL-SIG: received ADD RESV request for tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: path previous hop is 10.32.0.6 (AT1/0.1)
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: path next hop is 10.2.0.12 (Et4/0/2)
  TSP-TUNNEL-SIG: sending ADD RESV reply for tunnel 10.106.0.6 1206
State setup at head hop:
  TSP-TUNNEL-SIG: received ADD RESV request for tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: path next hop is 10.32.0.10 (AT0/0.1)
  TSP-TUNNEL-SIG: sending ADD RESV reply for tunnel 10.106.0.6 1206
 

The display output for signaling teardown uses the same format:

Output at tunnel head:
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: RSVP head-end close
  TSP-TUNNEL-SIG: received DELETE RESV request for tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: path next hop is 10.32.0.10 (AT0/0.1)
  TSP-TUNNEL-SIG: sending DELETE RESV reply for tunnel 10.106.0.6 1206
Output at intermediate hop:
  TSP-TUNNEL-SIG: received DELETE RESV request for tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: path previous hop is 10.32.0.6 (AT1/0.1)
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: path next hop is 10.2.0.12 (Et4/0/2)
  TSP-TUNNEL-SIG: sending DELETE RESV reply for tunnel 10.106.0.6 1206
Output at tunnel tail:
  TSP-TUNNEL-SIG: received PATH TAIL DELETION event about tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: RSVP tail-end close
  TSP-TUNNEL-SIG: received DELETE RESV request for tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: path previous hop is 10.2.0.10 (Et4/0/2)
  TSP-TUNNEL-SIG: sending DELETE RESV reply for tunnel 10.106.0.6 1206
  TSP-TUNNEL-SIG: PATH TAIL DELETION event handled successfully

Related Commands

Command	Description
debug tag-switching tsp-tunnels events	Enables logging of significant events that affect TSP tunnels.
debug tag-switching tsp-tunnels tagging	Enables logging of TSP tunnel Tag Switching state programming.

Related Commands

Command	Description
show xtagatm cross-connect	Displays information about remotely connected ATM switches.

Related Commands

Command	Description
debug tag-switching xtagatm cross-connect	Displays requests and responses for establishing and removing cross-connects on the controlled ATM switch.
debug tag-switching xtagatm events	Displays information about major events that occur on XTagATM interfaces, not including events for specific XTagATM VCs and switch cross-connects.
debug tag-switching xtagatm vc	Display information about events that affect individual XTagATM terminating VCs.