Table Of Contents

debug tag-switching adjacency

Usage Guidelines

Sample Display

Related Commands

debug tag-switching atm-tdp api

Usage Guidelines

Sample Display

Related Commands

debug tag-switching atm-tdp routes

Usage Guidelines

Sample Display

Related Commands

debug tag-switching atm-tdp states

Usage Guidelines

Sample Display

Related Commands

debug tag-switching packets

Syntax Description

Usage Guidelines

Sample Display

debug tag-switching tdp advertisements

Sample Display

Related Commands

debug tag-switching tdp bindings

Sample Display

Related Command

debug tag-switching tdp directed-neighbors

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tdp peer state-machine

Usage Guidelines

Sample Display

debug tag-switching tdp pies received

Syntax Description

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tdp pies sent

Syntax Description

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tdp session io

Syntax Description

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tdp session state-machine

Usage Guidelines

Sample Display

debug tag-switching tdp transport connections

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tdp transport events

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tdp transport timers

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tfib cef

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tfib enc

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tfib state

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tfib struct

Sample Display

Related Commands

debug tag-switching tfib tsp

Sample Display

Related Command

debug tag-switching traffic-engineering

Syntax Description

Sample Display

Related Command

debug tag-switching traffic-engineering interfaces

Usage Guidelines

Sample Display

Related Command

debug tag-switching traffic-engineering metrics

Usage Guidelines

Sample Display

Related Command

debug tag-switching traffic-engineering routing-table

Usage Guidelines

Sample Display

Related Command

debug tag-switching tsp-tunnels events

Usage Guidelines

Sample Display

Related Command

debug tag-switching tsp-tunnels signalling

Usage Guidelines

Sample Display

Related Commands

debug tag-switching tsp-tunnels tagging

Usage Guidelines

Sample Display

Related Command

debug tag-switching adjacency

Use the debug tag-switching adjacency EXEC command to display changes to Tag Switching entries in the adjacency database. The no form of this command disables debugging output.

[no] debug tag-switching adjacency

Usage Guidelines

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

Sample Display

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

describes the significant fields in this display.

Table 138 Debug Tag-Switching Adjacency Field Description

Field	Description
add	Adding an entry to the database.
update	Updating the MAC address for an existing entry.
10.10.0.1	Address of neighbor TSR.
Ethernet0/0/0	Connecting interface.

Related Commands

show adjacency

debug tag-switching atm-tdp api

Use the debug tag-switching atm-tdp api EXEC command to display information about the VCI allocation of tag VCs (TVCs), free, and cross-connect requests. The no form of this command disables debugging output.

[no] debug tag-switching atm-tdp api

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.

Sample Display

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

describes the significant fields in the display.

Table 139 Debug Tag-Switching ATM-TDP API Field Descriptions

Field	Description
TAGATM_API	The subsystem that prints the message.
interface	The interface used by the driver to allocate or free VPI/VCI resources.
dir	The direction of the VC: In—Input or receive VC Out—Output VC
vpi	Virtual path identifier.
vci	Virtual channel identifier.
result	The return error code from the driver API.

Related Commands

debug tag-switching atm-tdp states

debug tag-switching atm-tdp routes

Use the debug tag-switching atm-tdp routes EXEC command to display information about the state of the routes for which VCI requests are being made. The no form of this command disables debugging output.

[no] debug tag-switching atm-tdp routes

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.

Sample Display

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

describes the significant fields in the display.

Table 140 Debug Tag-Switching ATM-TDP Routes Field Descriptions 

Field	Description
CleanupRoutes	Cleans up the routing table after a route has been deleted.
not deleting route of idb ATM0/0.2	The route cleanup event has not removed the specified route.
rdbIndex	Index identifying the route.
tcatmFindRouteTags	Request a VC for the route.
idb	The internal descriptor for an interface.
nh	Next hop for the route.
index	Identifier for the route.
AddNewRoute	Action of adding routes for a prefix or address.

Related Commands

tag-switching atm-tdp holdtime

debug tag-switching atm-tdp states

Use the debug tag-switching atm-tdp states EXEC command to display information about TVC state transitions as they occur. The no form of this command disables debugging output.

[no] debug tag-switching atm-tdp states

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.

Sample Display

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

describes the significant fields in the display.

Table 141 Debug Tag-Switching ATM-TDP States Field Descriptions

Field	Description
Transit Output	Output side of a TVC.
VPI/VCI	VC value.
Transit Input	Input side of a TVC.

Related Commands

tag-switching atm-tdp holdtime

debug tag-switching packets

Use the debug tag-switching packets EXEC command to display tagged packets switched by this router. The no form of this command disables debugging output.

[no] debug tag-switching packets [interface]

Syntax

interface

(Optional) Interface or subinterface name.

Description

Usage Guidelines

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

---

Note   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.

---

Sample Display

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

describes the significant fields in the display.

Table 142 Debug Tag-Switching Packets Field Descriptions

Field	Description
Hs0/0	The identifier for the interface on which the packet was received or transmitted.
recvd	Packet received.
xmit	Packet transmitted.
CoS	Class of Service field from the packet tag header.
TTL	Time To Live field from the packet tag header.
(no tag)	Last tag popped off the packet and transmitted untagged.
Tag(s)	A list of tags on the packet, ordered from top of stack to bottom.

debug tag-switching tdp advertisements

Use the debug tag-switching tdp advertisements EXEC command to print information about the advertisement of tags and interface addresses to TDP peer devices. The no form of this command disables debugging output.

[no] debug tag-switching tdp advertisements

Sample Display

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)

describes the significant fields in the display.

Table 143 Debug Tag-Switching TDP Advertisements Field Descriptions

Field	Description
tagcon:	Identifies the source of the message as the tag control subsystem.
adj a.b.c.d:e	The TDP identifier of the peer device to which the advertisement has been made.
(pp 0xnnnnnnnn)	The identifier for the data structure used to represent the peer device at the tag distribution level. Useful for correlating debug output.
advertise X	What was advertised to the peer device—either an interface address ("a.b.c.d") or tag binding ("a.b.c.d/m, tag t (#n)").
(#n)	For a tag binding advertisement, the sequence number of the Tag Information Base (TIB) modification that made it necessary to advertise the tag.

Related Commands

show tag-switching tdp neighbors

debug tag-switching tdp bindings

Use the debug tag-switching tdp bindings EXEC command to print information about changes to the tag information base (TIB) used to keep track of tag bindings learned from TDP peer devices through TDP downstream tag distribution. The no form of this command disables debugging output.

[no] debug tag-switching tdp bindings

Sample Display

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

describes the significant fields in the display.

Table 144 Debug Tag-Switching TDP Bindings Field Descriptions

Field	Description
tagcon:	Identifies the source of the message as the tag control subsystem.
tibent(network/mask)	The destination that has a tag binding change.
created; reason	A TIB entry has been created for the specified destination for the indicated reason.
rem tag ...	Describes a change to the tag bindings for the specified destination. The change is for a tag binding learned from the specified TDP peer device.
lcl tag ...	Describes a change to a locally assigned (incoming) tag for the specified destination.
(#n)	The sequence number of the modification to the TIB corresponding to the local tag change.
a.b.c.d:n: e.f.g.h added to addr<->tdp ident map	The address e.f.g.h has been added to the set of addresses associated with TDP identifier a.b.c.d:n.

Related Command

show tag-switching tdp bindings

debug tag-switching tdp directed-neighbors

Use the debug tag-switching tdp directed-neighbors EXEC command to print information about the directed neighbor mechanism. This mechanism establishes TDP adjacencies to peer devices that are not directly adjacent, such as peer devices at either end of a tunnel. The no form of this command disables debugging output.

[no] debug tag-switching tdp directed-neighbors

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.

Sample Display

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

describes the significant fields in the display.

Table 145 Debug Tag-Switching TDP Directed-Neighbors Field Descriptions

Field	Description
tdp_directednbr:	Identifies this as a TDP directed neighbor debug statement.
TDPDirAdj addr:	Identifies the IP address to which a TDP adjacency is desired.

Related Commands

show tag-switching tdp neighbors

debug tag-switching tdp peer state-machine

Use the debug tag-switching tdp peer state-machine EXEC command to print information about state transitions at the tag distribution level. The no form of this command disables debugging output.

[no] debug tag-switching tdp peer state-machine

Usage Guidelines

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

•Transport—The transport level establishes and maintains TCP connections used to support TDP sessions.

•Protocol—The protocol level implements the TDP session setup protocol, and constructs and parses TDP PDUs and PIEs.

•Tag distribution—The tag distribution level uses TDP sessions to exchange tags with TDP peer devices.

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.

Sample Display

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

describes the significant fields in the display.

Table 146 Debug Tag-Switching TDP Peer State-Machine Field Descriptions

Field	Description
tagcon:	Identifies the source of the message as the tag control subsystem.
adj a.b.c.d:e	The TDP identifier of the peer device for the session with the state change.
(pp 0xnnnnnnnn)	Address of the data structure used to represent the peer device at the tag distribution level. It is useful for correlating debug output.
Event E	The event causing the state change.
S1 -> S2	The state of the TDP session has changed from state S1 to state S2.

debug tag-switching tdp pies received

Use the debug tag-switching tdp pies received EXEC command to print information about TDP protocol information elements (PIEs) received from TDP peer devices. The no form of this command disables debugging output.

[no] debug tag-switching tdp pies received [all]

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.

Sample Display

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)

describes the significant fields in the display.

Table 147 Debug Tag-Switching TDP Pies Received All Field Descriptions

Field	Description
tdp:	Identifies the source of the message as TDP.
Rcvd xxx PIE	The type of PIE received.
from a.b.c.d	The host that sent the PIE. Used in the early stages of the opening of a TDP session, when the TDP identifier is not yet known.
from a.b.c.d:e	The TDP identifier of the peer device that sent the PIE.
(pp 0xnnnnnnnn)	Identifies the data structure used to represent the peer device at the tag distribution level. Useful for correlating debug output.

Related Commands

debug tag-switching tdp pies sent

debug tag-switching tdp pies sent

Use the debug tag-switching tdp pies sent EXEC command to print information about state transitions at the tag distribution level. The no form of this command disables debugging output.

[no] debug tag-switching tdp pies sent [all]

Syntax

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

Description

Usage Guidelines

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

Sample Display

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)

describes the significant fields in the display.

Table 148 Debug Tag-Switching TDP PIEs Sent All Field Descriptions

Field	Description
tdp:	Identifies the source of the message as TDP.
Queued xxx PIE	Indicates that a PIE of the specified type has been queued for transmission.
Sent xxx PIE	Indicates that a PIE of the specified type has been sent on the TDP session TCP connection.
to a.b.c.d	The host to which the PIE has been sent or for which it has been queued. Used in the early stages of opening a TDP session when the TDP identifier is not yet known.
to a.b.c.d:e	The TDP identifier of the peer device to which the PIE has been sent or for which it has been queued.
(pp 0xnnnnnnnn)	Identifies the data structure used to represent the peer device at the tag distribution level. Useful for correlating debug output.

Related Commands

debug tag-switching tdp pies received
debug tag-switching tdp session io

debug tag-switching tdp session io

Use the debug tag-switching tdp session io EXEC command to print the contents of TDP PIEs sent to and received from TDP peer devices. The no form of this command disables debugging output.

[no] debug tag-switching tdp session io [all]

Syntax

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

Description

Usage Guidelines

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

•Transport—The transport level establishes and maintains TCP connections used to support TDP sessions.

•Protocol—The protocol level implements the TDP session setup protocol, and constructs and parses TDP PDUs and PIEs.

•Tag distribution—The tag distribution level uses TDP sessions to exchange tags with TDP peer devices.

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.

Sample Display

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 

describes the significant fields in the display.

Table 149 Debug Tag-Switching TDP Session IO Field Descriptions

Field	Description
tdp:	Identifies the source of the message as TDP.
Rcvd xxx PIE	Indicates that a PIE of the specified type has been received.
from a.b.c.d	The host to which the PIE has been sent. Used in the early stages of the opening of a TDP session when the TDP identifier is not yet known.
Sent xxx PIE	Indicates that a PIE of the specified type has been sent.
to a.b.c.d	The host to which the PIE has been sent. Used in the early stages of opening a TDP session when the TDP identifier is not yet known.
to a.b.c.d:e	The TDP identifier of the peer device to which the PIE has been sent.
(pp 0xnnnnnnnn)	Identifies the data structure used to represent the peer device at the tag distribution level. Useful for correlating debug output.
--TDP xxx PIE	The type of PIE that has been sent.
PDU_hdr: TDP Id: a.b.c.d:e	The TDP identifier of the sender included in the TDP PDU header.
PIE contents: 0xnn ... 0xnn	The contents of the PIE represented as a sequence of bytes.

Related Commands

debug tag-switching tdp pies received
debug tag-switching tdp pies sent

debug tag-switching tdp session state-machine

Use the debug tag-switching tdp session state-machine EXEC command to print information about state transitions at the protocol level. The no form of this command disables debugging output.

[no] debug tag-switching tdp session state-machine

Usage Guidelines

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

•Transport—The transport level establishes and maintains TCP connections used to support TDP sessions.

•Protocol—The protocol level implements the TDP session setup protocol, and constructs and parses TDP PDUs and PIEs.

•Tag distribution—The tag distribution level uses TDP sessions to exchange tags with TDP peer devices.

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.

Sample Display

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

describes the significant fields in the display.

Table 150 Debug Tag-Switching TDP Session State-Machine Field Descriptions

Field	Description
tdp:	Identifies the source of the message as TDP.
adj:a.b.c.d	Identifies the network address of the TDP peer device.
(0xnnnnnnnn)	Identifies the data structure used to represent the peer device at the protocol level. Useful for correlating debug output.
Event: E	The event that caused the state transition.
S1 -> S2	The state of the TDP session has changed from state S1 to state S2.

debug tag-switching tdp transport connections

Use the debug tag-switching tdp transport connections EXEC command to print information about the TCP connections used to support TDP sessions. The no form of this command disables debugging output.

[no] debug tag-switching tdp transport connections

Usage Guidelines

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

•Transport—The transport level establishes and maintains TCP connections used to support TDP sessions.

•Protocol—The protocol level implements the TDP session setup protocol, and constructs and parses TDP PDUs and PIEs.

•Tag distribution—The tag distribution level uses TDP sessions to exchange tags with TDP peer devices.

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.

Sample Display

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

describes the significant fields in the display.

Table 151 Debug Tag-Switching TDP Transport Connections Field Descriptions 

Field	Description
tdp:	Identifies the source of the message as TDP.
adj 0xnnnnnnnn	Identifies the data structure used to represent the peer device at the transport level. Useful for correlating debug output.
a.b.c.d -> p.q.r.s	Indicates a TCP connection between a.b.c.d and p.q.r.s.
a.b.c.d:x -> p.q.r.s:y	Indicates a TCP connection between a.b.c.d, port x and p.q.r.s, port y.

Related Commands

debug tag-switching tdp transport events

debug tag-switching tdp transport events

Use the debug tag-switching tdp transport events EXEC command to print information about the events related to the TDP peer discovery mechanism, which is used to determine the devices with which to establish TDP sessions. The no form of this command disables debugging output.

[no] debug tag-switching tdp transport events

Usage Guidelines

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

•Transport—The transport level establishes and maintains TCP connections used to support TDP sessions.

•Protocol—The protocol level implements the TDP session setup protocol, and constructs and parses TDP PDUs and PIEs.

•Tag distribution—The tag distribution level uses TDP sessions to exchange tags with TDP peer devices.

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.

Sample Display

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

describes the significant fields in the display.

Table 152 Debug Tag-Switching TDP Transport Events Field Descriptions 

Field	Description
tdp:	Identifies the source of the message as TDP.
adj 0xnnnnnnnn	Identifies data structure used to represent the peer device at the transport level. Useful for correlating debug output.
a.b.c.d (p.q.r.s:n)	Network address and TDP identifier of the peer device.
intf_id	Interface identifier (non-zero for TC-ATM interfaces, 0 otherwise).
opt 0xn	Bits that describe options in the TDP discovery hello packet: 0x1—Directed hello option 0x2—Send directed hello option 0x4—Transport address option

Related Commands

debug tag-switching tdp transport connections

debug tag-switching tdp transport timers

Use the debug tag-switching tdp transport timers EXEC command to print information about events that restart the "hold" timers that are part of the TDP discovery mechanism. The no form of this command disables debugging output.

[no] debug tag-switching tdp transport timers

Usage Guidelines

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

•Transport—The transport level establishes and maintains TCP connections used to support TDP sessions.

•Protocol—The protocol level implements the TDP session setup protocol. The construction and parsing of TDP PDUs and PIEs occur at this level.

•Tag distribution—The tag distribution level uses TDP sessions to exchange tags with TDP peer devices.

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.

Sample Display

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

describes the significant fields in the display.

Table 153 Debug Tag-Switching TDP Transport Timers Field Descriptions

Field	Description
tdp	Identifies the source of the message as TDP.
adj 0xnnnnnnnn	Identifies the data structure used to represent the peer device at the transport level.
a.b.c.d	Network address of the peer device.

Related Commands

debug tag-switching tdp transport events

debug tag-switching tfib cef

Use the debug tag-switching tfib cef EXEC command to print detailed information about tag rewrites being created, resolved, and deactivated as CEF routes are added, changed, or removed. The no form of this command disables debugging.

[no] debug tag-switching tfib cef

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 debug tag-switching tfib cef has been issued, several lines of output are displayed for each route.

Sample Display

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

describes the significant fields in the display. See for a description of special tag names seen in the debug output.

Table 154 Debug Tag-Switching TFIB CEF Field Descriptions 

Field	Description
TFIB	The name of the subsystem issuing the debug output.
tagcon	The name of subsystem issuing the debug output (Tag Control).
tc_ip_rtlookup fail on x.y.w.z/m: subnet_lookup failed	The destination with IP address and mask shown is not in the Routing Table.
route tag chg x.y.w.z/m	Request to create TFIB entry for specified prefix/mask.
idx=-1	The index within FIB entry of the path whose TFIB entry is being created. -1 means all paths for this FIB entry.
inc=s	Incoming tag of entry being processed.
outg=s	Outgoing tag of entry being processed.
enabled=0xn	Bit mask indicating types of Tag Switching currently enabled (0x1 = dynamic, 0x2 = TSP tunnels, 0x3 = both).
fib complete delete	Indicates FIB entry being deleted.
prefix=x.y.w.z/m	A destination prefix.
delete_info=1	Indicates that tag_info is also being deleted.
deactivate tag rew for x.y.w.z/m	Indicates tag rewrite for specified prefix is being deleted.
index=n	Index of path in FIB entry being processed.
set fib rew: pfx x.y.w.z/m	Indicates tag rewrite is being installed or deleted from the FIB entry for the specified destination for tag imposition purposes.
add=0	Indicates tag rewrite is being deleted from the FIB (no longer imposing tag).
tag_rew->adj=s	Adjacency of tag_rewrite for tag imposition.
resolve tag rew,prefix=x.y.w.z/m	Indicates the FIB route to the specified prefix is being resolved.
no tag_info	Indicates there is no tag_info for the destination (destination not tagged).
no parent	Indicates route is not recursive.
fib scanner start	Indicates the periodic scan of the FIB has started.
needed:1	Indicates TFIB needs the FIB to be scanned.
unres:n	The number of unresolved TFIB entries.
mac:n	The number of TFIB entries missing MAC strings.
loadinfo:n	Indicates whether non-recursive accounting state has changed and thus the loadinfo information in the TFIB needs to be adjusted.
fib upd loadinf x.y.w.z/m	Indicates that a check for non-recursive accounting is being made and TFIB loadinfo information for specified prefix is being updated.
tag=s	Incoming tag of entry.
fib no loadin	Indicates corresponding FIB entry has no loadinfo.
tfib no loadin	Indicates TFIB entry has no loadinfo.
fib check cleanup for x.y.w.z/m	Indicates a check is being made on the TFIB entry for specified destination to see if rewrite needs to be removed from TFIB.
return_value=x	If 0, no change in TFIB entry. If 1, there was a change.
fib_scanner_end	FIB scan has come to an end.
create dynamic entry for x.y.w.z/m	The TFIB has been enabled and a TFIB entry is being created for the specified destination.
call find_route_tags	The tags for that destination are being requested.
dist_method=n	The tag distribution method -- TDP, TC-ATM, and so on.
next_hop=x.y.z.w	Next hop for the destination.
interface name	Outgoing interface for the destination.
create tag info	A tag_info data structure is being created for the destination.
has no info	The destination does not already have a tag_info.
finish fib res x.y.z.w/m	The TFIB entry for the specified route is being completed.
parent outg tag s	If recursive, specifies the outgoing tag of the route through which it recurses (the parent). If not recursive, s = "no parent."
tagcon: route_tag_change for: x.y.z.w/m	Tag Control is notifying TFIB that tags are available for specified destination.
intag s	Incoming tag for the destination.
outtag s	Outgoing tag for the destination.
nexthop tsr x.y.z.w.i	TDP ID of next hop which sent the tag.

Related Commands

debug tag-switching tfib enc

debug tag-switching tfib enc

Use the debug tag-switching tfib enc EXEC command to print detailed information about tag encapsulations while tag rewrites are created or updated and placed into the Tag Forwarding Information Base (TFIB). This output shows you which adjacency the tag rewrite is being created on and the tags. The no form of this command disables debugging output.

[no] debug tag-switching tfib enc

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.

Sample Display

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

describes the significant fields in the display.

Table 155 Debug Tag-Switching TFIB ENC Field Descriptions 

Field	Description
TFIB	Identifies the source of the message as the TFIB subsystem.
finish res	Shows that the TFIB resolution is being finished.
inctag=x or inc=x	An incoming (local) tag for the TFIB entry is being created. Tags can be numbers or special values.
outg=y	An outgoing (remote) tag for the TFIB entry is being created.
next_hop=a.b.c.d	IP address of next hop for the destination.
interface	The outgoing interface through which a packet will be sent.
get ip adj	Shows that the IP adjacency to use in the TFIB entry is being determined.
get tag adj	Shows that the tag-switching adjacency to use for the TFIB entry is being determined.
addr = a.b.c.d	The IP address of the adjacency.
is_p2p=x	If 1, this is a point-to-point adjacency. If 0, it is not.
fibidb = s	The interface of the adjacency.
linktype = x	The link type of the adjacency (7 = LINK_IP or 79 = LINK_TAG).
sizes x,y,z	x = length of macstring, y = length of tag encapsulation, z = tag MTU.
type = x	Tag encapsulation type. 0= normal, 1 = TCATM, 2 = TSP tunnel.
idb:s	Outgoing interface.
update_mac	Shows that the macstring of the adjacency is being updated.

describes the special tags that may appear in the debug output.

Table 156 Special Tags Seen in Debug Output

Special Tag	Meaning
Unassn—Inital value	No tag assigned yet.
Unused	This destination does not have a tag (for example, a BGP route).
Withdrn	The tag for this destination has been withdrawn.
Unkn	This destination should have a tag, but it is not known yet.
Get_res	A recursive route that will get a tag when resolved.
Exp_null	Explicit null tag—used over TC-ATM.
Imp_null	Implicit null tag—for directly connected routes.
Tun_hd	For head of TSP tunnel.

Related Commands

debug tag-switching tfib state

debug tag-switching tfib state

Use the debug tag-switching tfib state EXEC command to trace what is happening as tag-switching is enabled or disabled. The no form of this command disables debugging output.

[no] debug tag-switching tfib state

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.

Sample Display

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

describes the significant fields in the display.

Table 157 Debug Tag-Switching TFIB State Field Descriptions 

Field	Description
TFIB	Identifies the source of the message as the TFIB subsystem.
Upd tag sb x	Shows that the status of the xth Tag Switching subblock is being updated, where x is the interface number. There is a Tag Switching subblock for each interface on which Tag Switching has ever been enabled.
(status:0xC1,tmtu:1500,VPI:1-1VC=0/32, et:0/0/0),lc 0x0)	The values of the fields in the Tag Switching subblock: 1) the status byte, the MTU, the range of ATM VPs, control VP and control VC (if this is a TC-ATM interface), the encapsulation type, encapsulation information, and tunnel interface number, and the line card number to which the update message is being sent (0 means all line cards)
intf status change	Shows that there was an interface status change.
idb=Et4/0/2	The interface whose status changed.
status=0xC1	The new status bits in the Tag Switching subblock of the idb.
oldstatus=0xC3	What the old status bits were before the change.
Interface dyntag change, change in state to Ethernet4/0/2	Shows that there was a change in dynamic tag status for the particular interface.
enable entered	Shows that the code that enables the TFIB was invoked.
TFIB already enabled	Shows that TFIB was already enabled when this call was made.
table exists	Shows that a TFIB table had already been allocated in a previous call.
cleanup: tfib[x] still non-0	Indicates TFIB is in the process of being deleted, but that slot x is still around.
disable lc mesg recvd, type=0x1	Shows that a message to disable Tag Switching type 1 (dynamic) was received by the line card.
disable entered, table exists,type=0x1	Shows that a call to disable dynamic Tag Switching was issued.
Ethernet4/0/1 fibidb subblock message received	Shows that a message giving fibidb status change was received on the lc.
enable lc msg recvd,type=0x1	Shows that a message to enable Tag Switching type 1 (dynamic) was received by the line card.
Tunnel301 set encapfix to 0x6016A97C	Shows that fibidb Tunnel301 on the line card received an encapsulation fixup.
types now 0x3, returning	Gives the value of the bitmask indicating the type of Tag Switching enabled. 0x1 means dynamic Tag Switching; 0x2 means tsp-tunnels; and 0x3 means both.

Related Commands

debug tag-switching tfib enc
debug tag-switching tfib struct

debug tag-switching tfib struct

Use the debug tag-switching tfib struct EXEC command to trace the allocation and freeing of TFIB-related data structures—the TFIB itself, tag-rewrites, and tag-info data. The no form of this command disables debugging output.

[no] debug tag-switching tfib struct

Sample Display

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

describes the significant fields in the display.

Table 158 Debug Tag-Switching TFIB Struct Field Descriptions 

Field	Description
TFIB	The subsystem issuing the message.tt
delete tag rew	A tag_rewrite is being freed.
remove from tfib	A tag rewrite is being removed from the TFIB.
inc tag-s	The incoming tag of the entry being processed.
set loadinfo	The loadinfo field in the TFIB entry is being set (used for nonrecursive accounting).
tag=s	The incoming tag of the entry being processed.
no old loadinfo	The TFIB entry did not have a loadinfo before.
no new loadinfo	The TFIB entry should not have a loadinfo now.
TFIB not is use. Checking for entries	Tag Switching has been disabled, and the TFIB is being freed up.
cleanup: tfib[x] still non-0	The TFIB is being checked for any entries in use, and entry x is the lowest numbered slot still in use.
TFIB freed	The TFIB table has been freed.
enable, TFIB allocated, size x bytes, maxtag = y	Tag Switching has been enabled, and a TFIB of x bytes has been allocated. The largest legal tag is y.
create tag rewrite	A tag_rewrite is being created.
inc s	The incoming tag.
outg s	The outgoing tag.
add to tfib at s	A tag_rewrite has been placed in the TFIB at slot s.
first in circular list	This TFIB slot had been empty, and this is the first rewrite in the list.
mac=0,enc=0	Length of the mac string and total encapsulation length, including tags.
added to circular list	A tag_rewrite is being added to a TFIB slot which already had an entry. This rewrite is being inserted in the circular list.

Related Commands

debug tag-switching tfib cef
debug tag-switching tfib enc
debug tag-switching tfib state

debug tag-switching tfib tsp

Use the debug tag-switching tfib tsp EXEC command to print detailed information about tag rewrites being created and deleted as TSP tunnels are added or removed. The no form of this command disables debugging output.

[no] debug tag-switching tfib tsp

Sample Display

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

describes the significant fields in the display.

Table 159 Debug Tag-Switching Tfib State Field Descriptions 

Field	Description
tagtun	Name of routine entered
next hop=x.y.z.w	Next hop for the tunnel being created
inc=x	Incoming tag for this hop of the tunnel being created
outg=x	Outgoing tag (1 means Implicit Null tag)
idb=s	Outgoing interface for the tunnel being created
if_number=7	Interface number of outgoing interface
tsptunnel	Name of routine entered
tsptun update loadinfo	Procedure being performed
tag=x	Incoming tag of TFIB slot whose loadinfo is being updated
loadinfo_reqd=x	Shows whether a loadinfo is expected for this entry (non-recursive accounting is on)
no new loadinfo	Means no change in loadinfo required
no old loadinfo	Means there was no loadinfo before
tagtun tag chg linec	Linecard is being informed of the TSP tunnel
fiblc=x	Which linecard being informed (0 means all)
in tg=x	Incoming tag of new TSP tunnel
o tg=x	Outgoing tag of new TSP tunnel
if=x	Outgoing interface number
nh=x.y.w.z	Next hop IP address
tagtun_delete	Procedure being performed: delete a TSP tunnel
tagtun tag del linec	Inform linecard of TSP tunnel deletion
tagtun chg msg	Linecard has received a message to create a TSP tunnel

Related Command

debug tag-switching tfib enc

debug tag-switching traffic-engineering

Use the debug tag-switching traffic-engineering EXEC command to print information about events affecting the traffic engineering routing process. The no form of this command disables debugging output.

[no] debug tag-switching traffic-engineering [events]

Syntax

events

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

Description

Sample Display

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

describes the significant fields in the display.

Table 160 Debug Tag-Switching Traffic-Engineering Events Field Descriptions

Field	Description
te_events:	Identifies this as a traffic engineering events debug statement.
prefix X/X:	Identifies the filter being evaluated.

Related Command

show ip traffic-engineering

debug tag-switching traffic-engineering interfaces

Use the debug tag-switching traffic-engineering interfaces EXEC command to print information about changes to tunnels configured with traffic engineering routes. The no form of this command disables debugging output.

[no] debug tag-switching traffic-engineering interfaces

Usage Guidelines

The traffic engineering routing process keeps track of tunnels that have traffic engineering routes configured through them. This debug command provides information about significant changes (such as up/down transitions) to those tunnels.

Sample Display

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

Router# debug tag-switching traffic-engineering interfaces

te_intfcs: interface Tunnel12 down notification received

te_intfcs: Tunnel12 up/down event

describes the field in the display.

Table 161 Debug Tag-Switching Traffic-Engineering Interfaces Field Description

Field	Description
te_intfcs:	Identifies this as a traffic engineering interface debug statement.

Related Command

show tag-switching tsp-tunnels

debug tag-switching traffic-engineering metrics

Use the debug tag-switching traffic-engineering metrics EXEC command to print information about metric exchange in support of the traffic engineering loop prevention algorithm. The no form of this command disables debugging output.

[no] debug tag-switching traffic-engineering metrics

Usage Guidelines

Metric exchange is supported by data structures in two areas:

•Adjacency establishment—A TDP adjacency must be established between the head and tail of the tunnel, over which metrics can be exchanged.

•Metric exchange—Metrics are actually requested and advertised over the adjacency.

Sample Display

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

describes the significant fields in the display.

Table 162 Debug Tag-Switching Traffic-Engineering Metrics Field Descriptions

Field	Description
te_metric:	Identifies this as a traffic engineering metric debug statement.
tdp peer id:	Identifies the TDP peer device.
TEAdj (Head) id:	Traffic engineering metric exchange state for TDP peer device.
TunAdj:	Traffic engineering metric exchange state for tunnel metric.
X/X:	Metric record.
entry 0xnnnnnnnn:	Identifies the data structure for the metric entry. Useful for correlating debug output.

Related Command

show ip traffic-engineering

debug tag-switching traffic-engineering routing-table

Use the debug tag-switching traffic-engineering routing-table EXEC command to print information about traffic engineering's interactions with the IP routing table and with the forwarding table, Cisco Express Forwarding (CEF). The no form of this command disables debugging output.

[no] debug tag-switching traffic-engineering routing-table

Usage Guidelines

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

Sample Display

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

describes the significant fields in the display.

Table 163 Debug Tag-Switching Traffic-Engineering Routing-Table Field Descriptions

Field	Description
te_rttab:	Identifies this as a traffic engineering routing table debug statement.
add/delete:	Operation on forwarding table.
X/X:	The prefix/mask whose forwarding table entry is being changed.

Related Command

show ip traffic-engineering

debug tag-switching tsp-tunnels events

Use the debug tag-switching tsp-tunnels events EXEC command to enable logging of significant events that affect TSP tunnels. The no form of this command disables debugging output.

[no] debug tag-switching tsp-tunnels events

Usage Guidelines

The debug tag-switching tsp-tunnels events command displays notifications received by the TSP tunnels module. The notifications displayed are generally associated with timers, interfaces, or interface addresses.

Sample Display

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

Router# debug tag-switching tsp-tunnels events

TSP-TUNNEL: received event for Tunnels Checkup Timer: timer fired

TSP-TUNNEL: received event for Tunnel1206: Interface administratively down

describes the significant fields in the display.

Table 164 Debug Tag-Switching TSP-Tunnels Events Field Descriptions

Field	Description
TSP-TUNNEL	Identifies the source of the message as TSP tunnels.
received event for	Identifies the object affected by the event.
timer fired	Describes the event that has occurred for the named object. This field is object-specific.

Related Command

debug tag-switching tsp-tunnels signalling

debug tag-switching tsp-tunnels signalling

Use the debug tag-switching tsp-tunnels signalling EXEC command to enable logging of TSP tunnel signalling activity. The no form of this command disables debugging output.

[no] debug tag-switching tsp-tunnels signalling

Usage Guidelines

TSP tunnels are signalled using the Resource Reservation Protocol (RSVP). TSP tunnel establishment is initiated at the head-end router by making an active open request to RSVP, which causes a message to be sent towards the tail-end router. At the tail-end router, RSVP notifies the TSP tunnels module of the incoming open request. If the tailend router accepts the request, it makes a corresponding passive open request to RSVP, which causes a message to return to the headend router, establishing the TSP tunnel state at each hop along the way.

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

Sample Display

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

describes the significant fields in the display.

Table 165 Debug Tag-Switching TSP-Tunnels Signalling Field Descriptions 

Field	Description
TSP-TUNNEL-SIG	Identifies the source of the message as TSP tunnels signalling.
tunnel 10.106.0.6 1206	Identifies the tunnel being signalled.
RSVP head-end open	TSP tunnels module has made an active open request to RSVP for a tunnel head.
received NEW PATH TAIL ARRIVAL	RSVP has notified the TSP tunnels module of an incoming setup request.
RSVP tail-end open	TSP tunnels module has made a passive open request to RSVP for a tunnel tail.
received ADD RESV request	TSP tunnels module has received a state setup request from RSVP for a tunnel.
path previous hop is	Indicates the address of the previous hop in the path of the TSP tunnel being signalled, followed by the interface (in parentheses) being used to reach that hop.
path next hop is	Indicates the address of the next hop in the path of the TSP tunnel being signalled, followed by the interface (in parentheses) being used to reach that hop.
sending ADD RESV reply	The TSP tunnels module is sending a response to an earlier state setup request made by RSVP. If an error is not explicitly indicated, then the request was completed without failure.

The display output for signalling 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

debug tag-switching tsp-tunnels events
debug tag-switching tsp-tunnels tagging

debug tag-switching tsp-tunnels tagging

Use the debug tag-switching tsp-tunnels tagging EXEC command to enable logging of TSP tunnel Tag Switching state programming. The no form of this command disables debugging output.

[no] debug tag-switching tsp-tunnels tagging

Usage Guidelines

The debug tag-switching tsp-tunnels tagging command displays the setup and removal of the tag-switched path state (and any additional forwarding state) at a router hop that is associated with TSP tunnels.

Sample Display

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

Router# debug tag-switching tsp-tunnels tagging

TSP-TUNNEL-TAGGING: tunnel 10.106.0.6 1206: fabric PROGRAM request

  TSP-TUNNEL-TAGGING: tunnel 10.106.0.6 1206: programming tag VC 1/43 on output 
interface ATM0/0.1

  TSP-TUNNEL-TAGGING: background thread starting

  TSP-TUNNEL-TAGGING: background thread started (pid 57)

  TSP-TUNNEL-TAGGING: descriptor D7AB40: created [1 total]

  TSP-TUNNEL-TAGGING: descriptor D7AB40: continuing "Program" request

  TSP-TUNNEL-TAGGING: descriptor D7AB40: allocated outgoing ATM VC 1/43 (vcd 12)

  TSP-TUNNEL-TAGGING: descriptor D7AB40: set "Interface Point Out State" to, allocated

  TSP-TUNNEL-TAGGING: # of resource points held for "TC-ATM" interfaces: 1

  TSP-TUNNEL-TAGGING: enabling TFIB fabric programming

  TSP-TUNNEL-TAGGING: TFIB is now enabled

  TSP-TUNNEL-TAGGING: descriptor D7AB40: set "Fabric State" to, enabled

  TSP-TUNNEL-TAGGING: descriptor D7AB40: set "Fabric Kind" to, default (TFIB)

  TSP-TUNNEL-TAGGING: descriptor D7AB40: set "Fabric State" to, set

  TSP-TUNNEL-TAGGING: tunnel 10.106.0.6 1206: fabric PROGRAM reply

  TSP-TUNNEL-TAGGING: background thread awaiting events

describes the significant fields in the display.

Table 166 Debug Tag-Switching TSP-Tunnels Tagging Field Descriptions 

Field	Description
TSP-TUNNEL-TAGGING	Identifies the source of the message as TSP tunnel tagging.
tunnel 10.106.0.6 1206	Identifies the tunnel being programmed.
fabric PROGRAM request	Identifies the request that has been entered by the signalling code. The verb "PROGRAM" indicates that the state is being installed. All other verbs indicate that the state is being removed.
programming tag	Identifies an input or output interface being programmed and the tag being set up or removed.
descriptor xxxxxx	Identifies the switching fabric resource being used to send, switch, or receive tunnel data.
allocated outgoing...	Indicates that an outgoing tag (or VPI/VCI) has been allocated on the outgoing interface.
enabling TFIB fabric programming	The TFIB switching fabric is required to support this tunnel and is enabled for use by this tunnel.
TFIB is now enabled	The TFIB's state has changed to active—it was not previously in use.
programming TFIB: 0x1A(26)* --> 0x1(1)	The TFIB is being programmed to forward tunnel packets as follows: packets arriving with tag 26 will be forwarded with tag 1. Tag 1 is the Implicit Null tag.
set "<resource>" to, <state>	The resource identified by <resource> has been placed in the state described by <state>.
fabric PROGRAM reply	Indicates that the request has been completed and that a reply is being sent to the signalling code. If an error is not explicitly indicated, the request was completed without a failure.

Related Command

debug tag-switching tsp-tunnels signalling