Downloads |
Table Of Contents
Tag Switching on Cisco 7000 Family
Tag Switching and Traffic Engineering
Traffic Engineering Tunnel Configuration
Case 1—Enable Tag Switching Incrementally in a Network
Case 2—Route Tagged Packets to Network A Only
Case 3—Limit Tag Distribution on a Tag Switching Network
Traffic Engineering Configuration Task
Engineer Traffic Across a Path.
Enabling Tag Switching Incrementally in a Network
Enabling Tag Switching for a Subset of Destination Prefixes
Selecting the Destination Prefixes and Paths
Displaying Tag Switching TDP Binding Information
Displaying Tag Switching Forwarding Table Information
Displaying Tag Switching Interface Information
Displaying Tag Switching TDP Neighbor Information
Enabling TSP Tunnel Signalling
Displaying the TSP Tunnel Information
show tag-switching atm-tdp bindings
show tag-switching atm-tdp capability
show tag-switching atm-tdp summary
show tag-switching forwarding-table
show tag-switching tdp bindings
show tag-switching tdp discovery
show tag-switching tdp neighbors
show tag-switching tdp parameters
show tag-switching tsp-tunnels
tag-switching atm allocation-mode
tag-switching ip (configuration)
tag-switching ip default-route
tag-switching tag-range downstream
tag-switching tsp-tunnels (configuration)
tag-switching tsp-tunnels (interface)
debug tag-switching atm-tdp api
debug tag-switching atm-tdp routes
debug tag-switching atm-tdp states
debug tag-switching tdp advertisements
debug tag-switching tdp bindings
debug tag-switching tdp directed-neighbors
debug tag-switching tdp peer state-machine
debug tag-switching tdp pies received
debug tag-switching tdp pies sent
debug tag-switching tdp session io
debug tag-switching tdp session state-machine
debug tag-switching tdp transport connections
debug tag-switching tdp transport events
debug tag-switching tdp transport timers
debug tag-switching tfib state
debug tag-switching tfib struct
debug tag-switching tsp-tunnels events
debug tag-switching tsp-tunnels signalling
debug tag-switching tsp-tunnels tagging
How to Read System Error Messages
Error Message Traceback Reports
Tag Switching on Cisco 7000 Family
Feature Summary
Tag Switching combines the performance and capabilities of Layer 2 (data link layer) switching with the proven scalability of Layer 3 (network layer) routing. It enables service providers to meet challenges brought about by explosive growth and provides the opportunity for differentiated services without necessitating the sacrifice of existing infrastructure. The Tag Switching architecture is remarkable for its flexibility. Data can be transferred over any combination of Layer 2 technologies, support is offered for all Layer 3 protocols, and scaling is possible well beyond anything offered in today's networks.
Specifically Tag Switching can efficiently enable the delivery of IP services over an ATM switched network. It supports the creation of different routes between a source and a destination on a purely router-based Internet backbone. Service providers who use Tag Switching can save money and increase revenue and productivity.
Benefits
Tag Switching offers the following benefits:
•
IP over ATM scalability—Enables service providers to keep up with Internet growth
•
•
•
List of Terms
ATM-TSR—A Tag Switching router with a number of TC-ATM interfaces. The router forwards the cells among these interfaces using tags carried in the VPI/VCI field.
ATM edge TSR—A router that is connected to the ATM-TSR cloud through TC-ATM interfaces. The ATM edge TSR adds tags to untagged packets and strips tags from tagged packets.
forwarding equivalence class—A set of packets, which, however different they may be, are indistinguishable to the forwarding function.
headend—The upstream, transmit end of a tunnel.
tag—A short fixed-length label that tells switching nodes how the data (packets or cells) should be forwarded.
tag imposition—The act of putting the first tag on a packet.
tag edge router—The router that performs tag imposition.
Tag Switch—A node that forwards units of data (packets or cells) on the basis of tags.
tag-switched path (TSP)—A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through Tag Switching mechanisms. A tag-switched path can be chosen dynamically, based on normal routing mechanisms, or through configuration.
Tag Switching Router (TSR)—A Layer 3 router that forwards packets based on the value of a tag encapsulated in the packets.
tailend—The downstream, receive end of a tunnel.
TDP—Tag Distribution Protocol. The protocol used to distribute tag bindings on TSRs.
TFIB—Tag Forwarding Information Base. The data structure used by the switching function to switch tagged packets.
TIB—Tag Information Base. A database used to store tags learned from other TSRs as well as tags assigned by the local TSR.
traffic engineering—The techniques and processes used to cause routed traffic to travel through the network on a path other than the one that would have been chosen if standard routing methods had been used.
traffic engineering tunnel— A tag-switched path tunnel that is used for engineering traffic. It is set up through means other than normal Layer 3 routing and is used to direct traffic over a path different from the one that Layer 3 routing would cause it to take.
tag-switched path (TSP) tunnel—A configured connection between two routers, using Tag Switching to carry the packets.
Tag VC (TVC)—An ATM virtual circuit that is set up through ATM TSR tag distribution procedures.
tag-controlled ATM interface (TC-ATM interface)—An interface on a router or switch that uses tag distribution procedures to negotiate tag VCs.
Restrictions
Tag Switching on the router requires that Cisco Express Forwarding (CEF) be enabled. Refer to the Cisco Express Forwarding (CEF) feature documentation for configuration information.
Memory Requirements
The recommended minimum memory requirement in platforms carrying full Internet routing information is the same as for Cisco Express Forwarding. For more details, see the Release Notes for Cisco IOS 11.1 CC and Feature Modules.
Platforms
Tag switching is supported on the following platforms:
•
•
•
•
Supported Media
The interfaces supported are
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
Supported MIBs and RFCs
This feature supports RFC 2105, Cisco Systems' Tag Switching Architectural Overview.
Functional Description
Tag switching is a high-performance packet forwarding technology. It integrates the performance and traffic management capabilities of data link layer (Layer 2) switching with the scalability and flexibility of network layer (Layer 3) routing.
Tag Functions
In conventional Layer 3 forwarding, as a packet traverses the network, each router extracts all the information relevant to forwarding the packet from the Layer 3 header. This information is then used as an index for a routing table lookup to determine the packet's next hop.
In the most common case, the only relevant field in the header is the destination address field, but in some cases other header fields may also be relevant. As a result, the header analysis must be done independently at each router through which the packet passes, and a complicated lookup must also be done at each router.
In Tag Switching, the analysis of the Layer 3 header is done just once. The Layer 3 header is then mapped into a fixed length, unstructured value called a tag.
Many different headers can map to the same tag, as long as those headers always result in the same choice of next hop. In effect, a tag represents a forwarding equivalence class—that is, a set of packets, which, however different they may be, are indistinguishable to the forwarding function.
The initial choice of tag need not be based exclusively on the contents of the Layer 3 header; it can also be based on policy. This allows forwarding decisions at subsequent hops to be based on policy as well.
Once a tag is chosen, a short tag header is put at the front of the Layer 3 packet, so that the tag value can be carried across the network with the packet. At each subsequent hop, the forwarding decision can be made simply by looking up the tag. There is no need to re-analyze the header. Since the tag is a fixed length and unstructured value, looking it up is fast and simple.
Distribution of Tag Bindings
Each tag switching router (TSR) makes an independent, local decision as to which tag value is used to represent which forwarding equivalence class. This association is known as a tag binding. Each TSR informs its neighbors of the tag bindings it has made. This is done by means of the Tag Distribution Protocol (TDP).
When a tagged packet is being sent from TSR A to a neighboring TSR B, the tag value carried by the packet is the tag value that B assigned to represent the packet's forwarding equivalence class. Thus the tag value changes as the packet travels through the network.
Tag Switching and Routing
A tag represents a forwarding equivalence class, but it does not represent a particular path through the network. In general, the path through the network continues to be chosen by the existing
Layer 3 routing algorithms such as OSPF, EIGRP, and BGP. That is, at each hop when a tag is looked up, the next hop chosen is determined by the dynamic routing algorithm.Tag Switching and Traffic Engineering
In conventional Layer 3 routing, network topologies frequently include multiple paths between two points, but the normal routing procedure is to select a single path as the Layer 3 route between two points regardless of the load on the links that implement the path. As a consequence, some links are congested and some are underused.
Traffic engineering provides a way to override routing protocols across multiple routers. It gives you the ability to direct selected traffic over specific paths in the network in order to efficiently use network resources and provide different levels of service.
To engineer your network traffic, you follow a two-step process. First, you define a sequence of links between two routers. Tag switching is used to tunnel packets between the two routers over these links. The links collectively form a tag switched path (TSP) tunnel, which defines a traffic engineering path. Second, you select the traffic which you want forwarded on to the tunnel.
Static Route Configuration
Traffic Engineering Tunnel Configuration
Configuration and the initiation of the tunnel are controlled by the headend (transmit end) router. Per-tunnel configuration of other routers is unnecessary.
Routers create and maintain the traffic engineering tunnels based on information you enter through the command line interface (CLI). See the section called "Command Reference."
Configuration Tasks
This section describes three sample cases where Tag Switching is configured on Cisco 7500/7200 series routers. These cases show the levels of control possible in selecting how Tag Switching is deployed in a network.
lists the cases, including the steps to perform Tag Switching and their corresponding Cisco IOS CLI commands.
Table 1 Tag Switching—Levels of Control
For more information about the IOS CLI commands, see the section called "Command Reference."
shows a router-only Tag Switching network with Ethernet interfaces. The following sections outline the procedures for configuring Tag Switching and displaying Tag Switching information in a network based on the topology shown in .
Note
Figure 1 A Router-Only Tag Switching Network with Ethernet Interfaces
Case 1—Enable Tag Switching Incrementally in a Network
In the first case, the assumption is that you want to deploy Tag Switching incrementally throughout a network of routers, but that you do not want to restrict which destination prefixes are tag switched. For a description of the commands listed in these cases, see the section on "Command Reference."
To enable Tag Switching incrementally in a network, perform these steps and enter the commands in router configuration mode (see ).
After you perform these steps, R1 applies tags to packets that are forwarded through interface e0/1, with a next hop to R3.
Tag switching can be enabled throughout the rest of the network by the repetition of steps 1 and 2 as appropriate on other routers until all routers and interfaces are enabled for Tag Switching.
Case 2—Route Tagged Packets to Network A Only
In the second case to be considered here, the assumption is that you want to enable Tag Switching for a subset of destination prefixes. This option might be used to test Tag Switching across a large network. In this case, you would configure the system so that only a small number of destinations is tag switched (for example, internal test networks) without the majority of traffic being affected.
Perform the steps in the following table at each router in the network in router configuration mode (see ),
.
Case 3—Limit Tag Distribution on a Tag Switching Network
The third case demonstrates the full control which is available to you in determining the destination prefixes and paths for which Tag Switching is enabled.
Configure the routers so that packets addressed to network A are tagged, all other packets are untagged, and only links R1-R3, R3-R4, R4-R6, and R6-R7 carry tagged packets addressed to A. For example, suppose the normally routed path for packets arriving at R1 addressed to network A or network B is R1, R3, R5, R6, R7. A packet addressed to A would flow tagged on links R1-R3 and R6-R7, and untagged on links R3-R5 and R5-R6. A packet addressed to B would follow the same path, but would be untagged on all links.
Assume that at the outset the routers are configured so that packets addressed to network A are tagged and all other packets are untagged (as at the completion of Case 2).
Use the tag-switching advertise-tags command and access lists to limit tag distribution. Specifically, you need to configure routers R2, R5, and R8 to distribute no tags to other routers. This ensures that no other routers send tagged packets to any of those three. You also need to configure routers R1, R3, R4, R6, and R7 to distribute tags only for network A and to distribute them only to the appropriate adjacent router; that is, R3 distributes its tag for network A only to R1, R4 only to R3, and so on.
To limit tag distribution on a Tag Switching network, perform these steps in router configuration mode.
Traffic Engineering Configuration Task
This section describes a sample traffic engineering case. This case describes the steps necessary to engineer traffic across the "middle" path R3-R5-R8 (see ).
The assumption is made that traffic from R1 and R2 (in ), which is intended for R11, would be directed by Layer 3 routing along the "upper" path R3-R4-R7-R10-R11.
shows a router-only Tag Switching network with traffic-engineered paths.
Figure 2 Sample Tag Switching Network with Traffic Engineered Paths
Engineer Traffic Across a Path.
The following table lists the configuration commands you need to engineer traffic across the "middle" path R3-R5-R8 by building a tunnel R1-R3-R5-R8-R10, without affecting the path taken by traffic from R2 (see ).
To engineer traffic across a path, perform the following steps in router configuration mode:
Configuration Examples
This section provides sample configurations for the Cisco 7500/7200 series routers. It contains the following sections:
•
•
•
•
•
•
•
•
•
Enabling Tag Switching Incrementally in a Network
The following example shows you how to configure Tag Switching incrementally throughout a network of routers. You enable Tag Switching first between one pair of routers (in this case, R1 and R3 shown in ) and add routers step by step until every router in the network is tag switch enabled.
router-1# configuration terminal
router-1(config)# ip cef distributed
router-1(config)# tag-switching ip
router-1(config)# interface e0/1
router-1(config-if)# tag-switching ip
router-1(config-if)# exit
router-1(config)#router-3# configuration terminal
router-3(config)# ip cef distributed
router-3(config)# tag-switching ip
router-3(config)# interface e0/1
router-3(config-if)# tag-switching ip
router-3(config-if)# exit
router-3(config)#Enabling Tag Switching for a Subset of Destination Prefixes
The following example shows the commands you enter at each of the routers to enable Tag Switching for only a subset of destination prefixes (see ).
Router(config)# access-list-1 permit A
Router(config)# tag-switching advertise-tags for 1Selecting the Destination Prefixes and Paths
The following example shows the commands you enter to configure the routers to select the destination prefixes and paths for which Tag Switching is enabled. When you configure R2, R5, and R8 to distribute no tags to other routers, you ensure that no routers send them tagged packets. You also need to configure routers R1, R3, R4, R6, and R7 to distribute tags only for network A and only to the applicable adjacent router. This configuration ensures that R3 distributes its tag for
network A only to R1, R4 only to R3, R6 only to R4, and R7 only to R6 (see ).router-2(config)# no tag-switching advertise-tags
router-5(config)# no tag-switching advertise-tags
router-8(config)# no tag-switching advertise-tags
router-1(config)# access-list permit R1
router-1(config)# no tag-switching advertise-tags for 1
router-1(config)# tag-switching advertise-tags for 1 to 2
router-1(config)# exit
router-3# access-list 1 permit A
router-3# access-list 2 permit R1
router-3# tag-switching advertise-tags for 1 to 2
router-3# exit
router-4# access-list 1 permit A
router-4# access-list 2 permit R3
router-4# tag-switching advertise-tags for 1 to 2
router-4# exitrouter-6# access-list 1 permit A
router-6# access-list 2 permit R4
router-6# tag-switching advertise-tags for 1 to 2
router-6# exitrouter-7# access-list 1 permit A
router-7# access-list 2 permit R6
router-7# tag-switching advertise-tags for 1 to 2
router-7# exitDisplaying Tag Switching TDP Binding Information
Use the show tag-switching tdp bindings command to display the contents of the Tag Information Base (TIB). The display can show the entire database or can be limited to a subset of entries, based on prefix, input or output tag values or ranges, and/or the neighbor advertising the tag.
Note
Router# show tag-switching tdp bindingsMatching entries:tib entry: 10.92.0.0/16, rev 28local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.102.0.0/16, rev 29local binding: tag: 26remote binding: tsr: 172.27.32.29:0, tag: 26tib entry: 10.105.0.0/16, rev 30local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.205.0.0/16, rev 31local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.211.0.7/32, rev 32local binding: tag: 27remote binding: tsr: 172.27.32.29:0, tag: 28tib entry: 10.220.0.7/32, rev 33local binding: tag: 28remote binding: tsr: 172.27.32.29:0, tag: 29tib entry: 99.101.0.0/16, rev 35local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 100.101.0.0/16, rev 36local binding: tag: 29remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 171.69.204.0/24, rev 37local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 172.27.32.0/22, rev 38local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 210.10.0.0/16, rev 39local binding: tag: imp-null(1)tib entry: 210.10.0.8/32, rev 40remote binding: tsr: 172.27.32.29:0, tag: 27Displaying Tag Switching Forwarding Table Information
Use the show tag-switching forwarding-table command to display the contents of the Tag Forwarding Information Base (TFIB). The TFIB lists the tags, output interface information, prefix or tunnel associated with the entry, and number of bytes received with each incoming tag. A request can show the entire TFIB or can be limited to a subset of entries. A request can also be restricted to selected entries in any of the following ways:
•
•
•
•
•
Router# show tag-switching forwarding-tableLocal Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface26 Untagged 10.253.0.0/16 0 Et4/0/0 172.27.32.428 1/33 10.15.0.0/16 0 AT0/0.1 point2point29 Pop tag 10.91.0.0/16 0 Hs5/0 point2point1/36 10.91.0.0/16 0 AT0/0.1 point2point30 32 10.250.0.97/32 0 Et4/0/2 10.92.0.732 10.250.0.97/32 0 Hs5/0 point2point34 26 10.77.0.0/24 0 Et4/0/2 10.92.0.726 10.77.0.0/24 0 Hs5/0 point2point35 Untagged [T] 10.100.100.101/32 0 Tu301 point2point36 Pop tag 168.1.0.0/16 0 Hs5/0 point2point1/37 168.1.0.0/16 0 AT0/0.1 point2point[T] Forwarding through a TSP tunnel.View additional tagging info with the 'detail' optionDisplaying Tag Switching Interface Information
Use the show tag-switching interfaces command to show information about the requested interface or about all interfaces on which Tag Switching is enabled. The per-interface information includes the interface name and indications as to whether IP Tag Switching is enabled and operational.
Router# show tag-switching interfacesInterface IP Tunnel OperationalHssi3/0 Yes Yes NoATM4/0.1 Yes Yes Yes (ATM tagging)Ethernet5/0/0 No Yes YesEthernet5/0/1 Yes No YesEthernet5/0/2 Yes No NoEthernet5/0/3 Yes No YesEthernet5/1/1 Yes No NoThe following shows sample output from the show tag-switching interfaces command when you specify detail:
Router# show tag interface detailInterface Hssi3/0:IP tagging enabledTSP Tunnel tagging enabledTagging not operationalMTU = 4470Interface ATM4/0.1:IP tagging enabledTSP Tunnel tagging enabledTagging operationalMTU = 4470ATM tagging: Tag VPI = 1, Control VC = 0/32Interface Ethernet5/0/0:IP tagging not enabledTSP Tunnel tagging enabledTagging operationalMTU = 1500Interface Ethernet5/0/1:IP tagging enabledTSP Tunnel tagging not enabledTagging operationalMTU = 1500Interface Ethernet5/0/2:IP tagging enabledTSP Tunnel tagging not enabledTagging not operationalMTU = 1500Interface Ethernet5/0/3:IP tagging enabledTSP Tunnel tagging not enabledTagging operationalMTU = 1500Displaying Tag Switching TDP Neighbor Information
Use the show tag-switching tdp neighbors command to display the status of Tag Distribution Protocol (TDP) sessions. The neighbor information branch can have information about all TDP neighbors or can be limited to the neighbor with a specific IP address or, TDP identifier, or to TDP neighbors known to be accessible over a specific interface.
Router# show tag-switching tdp neighborsPeer TDP Ident: 10.220.0.7:1; Local TDP Ident 172.27.32.29:1TCP connection: 10.220.0.7.711 - 172.27.32.29.11029State: Oper; PIEs sent/rcvd: 17477/17487; Downstream on demandUp time: 01:03:00TDP discovery sources:ATM0/0.1Peer TDP Ident: 210.10.0.8:0; Local TDP Ident 172.27.32.29:0TCP connection: 210.10.0.8.11004 - 172.27.32.29.711State: Oper; PIEs sent/rcvd: 14656/14675; Downstream;Up time: 2d5hTDP discovery sources:Ethernet4/0/1Ethernet4/0/2POS6/0/0Addresses bound to peer TDP Ident:99.101.0.8 172.27.32.28 10.105.0.8 10.92.0.810.205.0.8 210.10.0.8Enabling TSP Tunnel Signalling
The following example shows you how to configure support for tag-switched path (TSP) tunnel signalling along a path and on each interface crossed by one or more tunnels:
Router(config)# ip cef distributedRouter(config)# tag-switching tsp-tunnelsRouter(config)# interface e0/1Router(config-if)# tag-switching tsp-tunnelsRouter(config-if)# interface e0/2Router(config-if)# tag-switching tsp-tunnelsRouter(config-if)# exitConfiguring a TSP Tunnel
The following example shows you how to set the encapsulation of the tunnel to Tag Switching and how to define hops in the path for the TSP.
Follow these steps to configure a two-hop tunnel, hop 0 being the headend router. For hops 1 and 2, you specify the IP addresses of the incoming interfaces for the tunnel. The tunnel interface number is arbitrary, but must be less than 65,535.
Router(config)# interface tunnel 2003Router(config-if)# tunnel mode tag-switchingRouter(config-if)# tunnel tsp-hop 1 10.10.0.12Router(config-if)# tunnel tsp-hop 2 10.50.0.24 lasthopRouter(config-if)# exitTo shorten the previous path, you delete a hop by entering the following commands:
Router(config)# interface tunnel 2003Router(config-if)# no tunnel tsp-hop 2Router(config-if)# tunnel tsp-hop 1 10.10.0.12 lasthopRouter(config-if)# exitDisplaying the TSP Tunnel Information
Use the show tag-switching tsp tunnels command to display information about the configuration and status of selected tunnels.
Router# show tag-switching tsp-tunnelsSignalling Summary:TSP Tunnels Process: runningRSVP Process: runningForwarding: enabledTUNNEL ID DESTINATION STATUS CONNECTION 10.106.0.6.2003 10.2.0.12 up upCommand Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 11.1 command references.
This section includes commands supported for Tag Switching. There are no examples of command output for the configuration commands, since they typically do not generate output.
All other commands used with this feature are documented in the Cisco IOS Release 11.1 command references.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
show tag-switching atm-tdp bindings
To display the requested entries from the ATM TDP tag binding database, use the show tag-switching atm-tdp bindings command. The ATM TDP database contains TIB entries for tag VCs on TC-ATM interfaces.
show tag-switching atm-tdp bindings [network {mask | length}]
[local-tag vpi vci ][remote-tag vpi vci] [neighbor interface]Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
The display output can show entries from the entire database, or it can be limited to a subset of entries based on prefix, VC tag value, and/or an assigning interface.
Sample Displays
The following is router sample output from the show tag-switching atm-tdp bindings command:
Router# show tag-switching atm-tdp bindingsDestination: 10.16.0.16/32Tailend Router ATM1/0.1 1/35 1/34 Active, VCD=2Destination: 10.24.0.0/24Tailend Router ATM1/0.1 1/39 Active, VCD=3Destination: 10.15.0.15/32Tailend Router ATM1/01 1/33 Active, VCD=4Destination: 10.23.0 0/24Tailend Router ATM1/01 1/37 Active, VCD=5lists the significant fields in this display.
Table 2 Show Tag-Switching ATM-TDP Bindings Field Descriptions
The following is ATM switch sample output from the show tag-switching atm-tdp bindings command:
Switch# show tag-switching atm-tdp bindingsDestination: 6.6.6.6/32Tailend Switch ATM0/0/3 1/34 Active -> Terminating ActiveDestination: 150.0.0.0/16Tailend Switch ATM0/0/3 1/35 Active -> Terminating ActiveDestination: 4.4.4.4/32Transit ATM0/0/3 1/33 Active -> ATM0/1/1 1/33 ActiveRelated Commands
show tag-switching atm-tdp summary
show tag-switching atm-tdp capability
To display the ATM TDP tag capabilities, use the show tag-switching atm-tdp capability command.
show tag-switching atm-tdp capability
Syntax Description
This command has no keywords or arguments.
Command Mode
Privileged EXEC
Sample Display
The following example shows the display from the show tag-switching atm-tdp capability command.
Router# show tag-switching atm-tdp capabilityVPI VCI Alloc Odd/Even VC MergeATM0/1/0 Range Range Scheme Scheme IN OUTNegotiated [100 - 101] [33 - 1023] UNIDIR - -Local [100 - 101] [33 - 16383] UNIDIR EN ENPeer [100 - 101] [33 - 1023] UNIDIR - -VPI VCI Alloc Odd/Even VC MergeATM0/1/1 Range Range Scheme Scheme IN OUTNegotiated [201 - 202] [33 - 1023] BIDIR - -Local [201 - 202] [33 - 16383] UNIDIR ODD NO NOPeer [201 - 202] [33 - 1023] BIDIR EVEN - -lists the significant fields in this display.
Table 3 Show Tag-Switching ATM-TDP Capability Field Descriptions
Related Command
tag-switching atm control-vc
tag-switching atm vc-merge
tag-switching atm vpishow tag-switching atm-tdp summary
To display summary information on ATM tag bindings, use the show tag-switching atm-tdp summary command.
show tag-switching atm-tdp summary
Syntax Description
This command has no arguments or keywords.
Command Mode
Privileged EXEC
Sample Display
The following is sample output from the show tag-switching atm-tdp summary command:
Router# show tag-switching atm-tdp summaryTotal number of destinations: 788TC-ATM bindings summary interface total active bindwait local remote other ATM0/0/0 594 592 1 296 298 1 ATM0/0/1 590 589 0 294 296 1 ATM0/0/2 1179 1178 0 591 588 1 ATM0/0/3 1177 1176 0 592 585 1 ATM0/1/0 1182 1178 4 590 588 0 Waiting for bind on ATM0/0/0 10.21.0.0/24lists the significant fields in this display.
Table 4 Show Tag-Switching ATM-TDP Summary Field Descriptions
Related Commands
show tag-switching atm-tdp bindings
show tag-switching forwarding-table
To display the contents of the Tag Forwarding Information Base (TFIB), use the show tag-switching forwarding-table command.
show tag-switching forwarding-table [{network {mask | length} | tags tag [- tag] |
interface interface | next-hop address | tsp-tunnel [tunnel-id ]}] [detail]Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
The optional parameters allow specification of a subset of the entire TFIB.
Sample Displays
The following is sample output from the show tag-switching forwarding-table command:
Router# show tag-switching forwarding-tableLocal Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface26 Untagged 10.253.0.0/16 0 Et4/0/0 172.27.32.428 1/33 10.15.0.0/16 0 AT0/0.1 point2point29 Pop tag 10.91.0.0/16 0 Hs5/0 point2point1/36 10.91.0.0/16 0 AT0/0.1 point2point30 32 10.250.0.97/32 0 Et4/0/2 10.92.0.732 10.250.0.97/32 0 Hs5/0 point2point34 26 10.77.0.0/24 0 Et4/0/2 10.92.0.726 10.77.0.0/24 0 Hs5/0 point2point35 Untagged [T] 10.100.100.101/32 0 Tu301 point2point36 Pop tag 168.1.0.0/16 0 Hs5/0 point2point1/37 168.1.0.0/16 0 AT0/0.1 point2point[T] Forwarding through a TSP tunnel.View additional tagging info with the 'detail' optionThe following is sample output from the show tag-switching forwarding-table command when you specify detail:
Router# show tag-switching forwarding-table detailLocal Outgoing Prefix Bytes tag Outgoing NextHoptag tag or VC or Tunnel Id switched interface26 Untagged 10.253.0.0/16 0 Et4/0/0 172.27.32.4MAC/Encaps=0/0, MTU=1504, Tag Stack{}28 1/33 10.15.0.0/16 0 AT0/0.1 point2pointMAC/Encaps=4/8, MTU=4470, Tag Stack{1/33(vcd=2)}00020900 0000200029 Pop tag 10.91.0.0/16 0 Hs5/0 point2pointMAC/Encaps=4/4, MTU=4474, Tag Stack{}FF0300811/36 10.91.0.0/16 0 AT0/0.1 point2pointMAC/Encaps=4/8, MTU=4470, Tag Stack{1/36(vcd=3)}00030900 0000300030 32 10.250.0.97/32 0 Et4/0/2 10.92.0.7MAC/Encaps=14/18, MTU=1500, Tag Stack{32}006009859F2A00E0F7E984828847 0002000032 10.250.0.97/32 0 Hs5/0 point2pointMAC/Encaps=4/8, MTU=4470, Tag Stack{32}FF030081 0002000034 26 10.77.0.0/24 0 Et4/0/2 10.92.0.7MAC/Encaps=14/18, MTU=1500, Tag Stack{26}006009859F2A00E0F7E984828847 0001A00026 10.77.0.0/24 0 Hs5/0 point2pointMAC/Encaps=4/8, MTU=4470, Tag Stack{26}FF030081 0001A00035 Untagged 10.100.100.101/32 0 Tu301 point2pointMAC/Encaps=0/0, MTU=1504, Tag Stack{}, via Et4/0/236 Pop tag 168.1.0.0/16 0 Hs5/0 point2pointMAC/Encaps=4/4, MTU=4474, Tag Stack{}FF0300811/37 168.1.0.0/16 0 AT0/0.1 point2pointMAC/Encaps=4/8, MTU=4470, Tag Stack{1/37(vcd=4)}00040900 00004000lists the significant fields in this display.
Table 5 Show Tag-Switching Forwarding-Table Field Descriptions
show tag-switching interfaces
To display information about one or more interfaces that have Tag Switching enabled, use the show tag-switching interfaces command.
show tag-switching interfaces [interface][detail]
Syntax Description
interface
(Optional.) The interface about which to display Tag Switching information.
detail
(Optional.) Display information in long form.
Command Mode
EXEC
Usage Guidelines
You can show information about the requested interface or about all interfaces on which Tag Switching is enabled.
Sample Display
The following is sample output from the show tag-switching interfaces command:
Router# show tag-switching interfacesInterface IP Tunnel OperationalHssi3/0 Yes Yes NoATM4/0.1 Yes Yes Yes (ATM tagging)Ethernet5/0/0 No Yes YesEthernet5/0/1 Yes No YesEthernet5/0/2 Yes No NoEthernet5/0/3 Yes No YesEthernet5/1/1 Yes No No
Note
lists the significant fields in this display.
Table 6 Show Tag-Switching Interfaces Command Field Descriptions
The following is sample output from the show tag-switching interfaces command when you specify detail:
Router# show tag-switching interface Ethernet2/0/1 detailInterface Hssi3/0:IP tagging enabledTSP Tunnel tagging enabledTagging not operationalMTU = 4470Interface ATM4/0.1:IP tagging enabledTSP Tunnel tagging enabledTagging operationalMTU = 4470ATM tagging: Tag VPI = 1, Control VC = 0/32Interface Ethernet5/0/0:IP tagging not enabledTSP Tunnel tagging enabledTagging operationalMTU = 1500Interface Ethernet5/0/1:IP tagging enabledTSP Tunnel tagging not enabledTagging operationalMTU = 1500Interface Ethernet5/0/2:IP tagging enabledTSP Tunnel tagging not enabledTagging not operationalMTU = 1500Interface Ethernet5/0/3:IP tagging enabledTSP Tunnel tagging not enabledTagging operationalMTU = 1500Related Commands
tag-switching tsp-tunnels
tag-switching ipshow tag-switching tdp bindings
To display the contents of the tag information base (TIB), use the show tag-switching tdp bindings command:
show tag-switching tdp bindings [network {mask | length} [longer-prefixes]]
[local-tag tag [- tag]} [remote-tag tag [- tag] [neighbor address] [local]Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
A request can specify that the entire database be shown, or it or can be limited to a subset of entries. A request to show a subset of entries can be based on the prefix, on input or output tag values or on ranges, and/or the neighbor advertising the tag.
Sample Displays
The following is sample output from the show tag-switching tdp bindings command. This form of the command causes the contents of the entire TIB to be displayed.
Router# show tag-switching tdp bindingsMatching entries:tib entry: 10.92.0.0/16, rev 28local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.102.0.0/16, rev 29local binding: tag: 26remote binding: tsr: 172.27.32.29:0, tag: 26tib entry: 10.105.0.0/16, rev 30local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.205.0.0/16, rev 31local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.211.0.7/32, rev 32local binding: tag: 27remote binding: tsr: 172.27.32.29:0, tag: 28tib entry: 10.220.0.7/32, rev 33local binding: tag: 28remote binding: tsr: 172.27.32.29:0, tag: 29tib entry: 99.101.0.0/16, rev 35local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 100.101.0.0/16, rev 36local binding: tag: 29remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 171.69.204.0/24, rev 37local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 172.27.32.0/22, rev 38local binding: tag: imp-null(1)remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 210.10.0.0/16, rev 39local binding: tag: imp-null(1)tib entry: 210.10.0.8/32, rev 40remote binding: tsr: 172.27.32.29:0, tag: 27The following is sample output from the show tag tdp bindings 10.0.0.0 8 longer-prefixes neighbor 172.27.32.29 variant of the command; it displays tags learned from TSR 172.27.32.29 for network 10.0.0.0 and any of its subnets. The use of the neighbor option suppresses the output of local tags and tags learned from other neighbors.
Router# show tag tdp bindings 10.0.0.0 8 longer-prefixes neighbor 172.27.32.29tib entry: 10.92.0.0/16, rev 28remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.102.0.0/16, rev 29remote binding: tsr: 172.27.32.29:0, tag: 26tib entry: 10.105.0.0/16, rev 30remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.205.0.0/16, rev 31remote binding: tsr: 172.27.32.29:0, tag: imp-null(1)tib entry: 10.211.0.7/32, rev 32remote binding: tsr: 172.27.32.29:0, tag: 28tib entry: 10.220.0.7/32, rev 33remote binding: tsr: 172.27.32.29:0, tag: 29lists the significant fields in this display.
Table 7 Show Tag-Switching TDP Bindings Field Description
Related Commands
show tag-switching tdp neighbors
show tag-switching forwarding-tableshow tag-switching tdp discovery
To display the status of the TDP discovery process, use the show tag-switching tdp discovery command. Status means a list of interfaces over which TDP discovery is running.
show tag-switching tdp discovery
Syntax Description
This command has no arguments or keywords.
Command Mode
Privileged EXEC
Sample Display
The following is sample output from the show tag-switching tdp discovery command.
Router# show tag-switching tdp discoveryLocal TDP Identifier:172.27.32.29:0TDP Discovery Sources:Interfaces:ATM0/0.1: xmit/recvATM0/0.1: xmit/recEthernet4/0/1: xmit/recvEthernet4/0/2: xmit/recvPOS6/0/0: xmit/recvlists the significant fields in this display.
Table 8 Show Tag-Switching TDP Discovery Field Descriptions
Related Commands
show tag-switching tdp neighbors
show tag-switching tdp neighbors
To display the status of Tag Distribution Protocol (TDP) sessions, enter the show tag-switching tdp neighbor command:
show tag-switching tdp neighbors {[address | interface] [detail]}
Syntax Description
address
(Optional.) The neighbor with this IP address.
interface
(Optional.) TDP neighbors accessible over this interface.
detail
(Optional.) Display information in long form.
Command Mode
Privileged EXEC
Usage Guidelines
The neighbor information branch can give information about all TDP neighbors, or it can be limited to
•
•
Sample Display
The following is sample output from the show tag-switching tdp neighbors command:
Router# show tag-switching tdp neighborsPeer TDP Ident: 10.220.0.7:1; Local TDP Ident 172.27.32.29:1TCP connection: 10.220.0.7.711 - 172.27.32.29.11029State: Oper; PIEs sent/rcvd: 17477/17487; Downstream on demandUp time: 01:03:00TDP discovery sources:ATM0/0.1Peer TDP Ident: 210.10.0.8:0; Local TDP Ident 172.27.32.29:0TCP connection: 210.10.0.8.11004 - 172.27.32.29.711State: Oper; PIEs sent/rcvd: 14656/14675; DownstreamUp time: 2d5hTDP discovery sources:Ethernet4/0/1Ethernet4/0/2POS6/0/0Addresses bound to peer TDP Ident:99.101.0.8 172.27.32.28 10.105.0.8 10.92.0.810.205.0.8 210.10.0.8lists the significant fields in this display.
Table 9 Show Tag-Switching TDP Neighbors Field Descriptions
Related Commands
show tag-switching tdp discovery
show tag-switching tdp parameters
To display available TDP parameters, use the show tag-switching tdp parameters command:
show tag-switching tdp parameters
Syntax Description
This command has no keywords or arguments.
Command Mode
Privileged EXEC
Sample Display
The following example shows the display from the show tag-switching tdp parameters command:
Router# show tag-switching tdp parametersProtocol version: 1Downstream tag pool: min tag: 10; max_tag: 10000; reserved tags: 16Session hold time: 15 sec; keep alive interval: 5 secDiscovery hello: holdtime: 15 sec; interval: 5 secDiscovery directed hello: holdtime: 15 sec; interval: 5 secAccepting directed helloslists the significant fields in this display.
Table 10 Show Tag-Switching TDP Parameters Command Field Descriptions
Related Command
tag-switching tdp holdtime
tag-switching tdp discoveryshow tag-switching tsp-tunnels
To display information about the configuration and status of selected tunnels, use the show tag-switching tsp-tunnels command.
show tag-switching tsp-tunnels [{head | middle | tail | all | remote | address} [interface-number]] [brief]
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
The optional arguments restrict the set of tunnels displayed. With no optional arguments, the command displays all tunnels passing through the node.
Each TSP tunnel has a globally unique identifier. When signalling the TSP tunnel is signalled and is available at each hop, this identifier is used. This identifier is a combination of the originating IP address and the number of the IOS tunnel interface used in configuring the TSP tunnel at the headend.
Sample Display
The following is sample output from the show tag-switching tsp-tunnels command:
Signalling Summary:TSP Tunnels Process: runningRSVP Process: runningForwarding: enabledTUNNEL ID DESTINATION STATUS CONNECTION 10.106.0.6 0 10.2.0.12 up uplists the significant fields in this display.
Table 11 Show Tag-Switching TSP-Tunnels Field Descriptions
Related Commands
tag-switching tsp-tunnels
tunnel mode tag-switchingtag-switching advertise-tags
To control the distribution of locally assigned (incoming) tags via the Tag Distribution Protocol (TDP), use the tag-switching advertise-tags command. To disable tag advertisement, use the no form of this command.
tag-switching advertise-tags [for access-list-number [to access-list-number]
no tag-switching advertise-tags [for access-list-number [to access-list-number]
Syntax Description
Default
Advertise all to all is the default.
Command Mode
Global configuration
Usage Guidelines
To enable the distribution of all locally assigned tags to all TDP neighbors, use the tag-switching advertise-tags command
You can enter multiple tag-switching advertise-tags commands. Taken together, they determine how local tags are advertised.
Note
Examples
In the following example, the router is configured to advertise all locally assigned tags to all TDP neighbors. This is the default.
Router(config)# tag-switching advertise-tagsIn the following example, the router is configured to advertise to all TDP neighbors tags for networks 10.101.0.0 and 10.221.0.0 only.
Router(config)# access-list 1 permit 10.101.0.0 0.0.255.255Router(config)# access-list 4 permit 10.221.0.0 0.0.255.255 Router(config)# tag-switching advertise-tags for 1 Router(config)# tag-switching advertise-tags for 4In the following example, the router is configured to advertise all tags to all TDP neighbors except neighbor 10.101.0.8.
Router(config)# access-list 1 permit any Router(config)# access-list 2 deny 10.101.0.8 Router(config)# tag-switching advertise-tags Router(config)# tag-switching advertise-tags for 1 to 2tag-switching atm allocation-mode
To control the mode used for handling tag binding requests on TC-ATM interfaces, use the tag-switching atm allocation-mode global configuration command. Use the no form of this command to disable this feature.
tag-switching atm allocation-mode {optimistic | conservative}
no tag-switching atm allocation-mode {optimistic | conservative}
Syntax Description
optimistic
Tag binding is returned immediately and packets are discarded until the downstream setup is complete.
conservative
Tag binding is delayed until the tag VC has been set up downstream.
Default
The default is conservative.
Command Mode
Global configuration
Example
In the following example, the mode for handling binding requests is set to optimistic on a TC-ATM interface:
tag-switching atm allocation-mode optimistictag-switching atm control-vc
To configure the VPI and VCI to be used for the initial link to the Tag Switching peer device, use the tag-switching atm control-vc subinterface configuration command. The initial link is used to establish the TDP session and to carry non-IP traffic. To clear the interface configuration, use the no form of this command.
tag-switching atm control-vc vpi vci
no tag-switching atm control-vc vpi vciSyntax Description
Default
If the subinterface has not changed to a VP tunnel, the default is 0/32. If the subinterface corresponds to VP tunnel VPI X, the default is X/32.
Command Mode
Interface configuration
Usage Guidelines
For a router interface (for example, an AIP) ATM Tag Switching can be enabled only on a tag-switch subinterface.
Note
On the Cisco LightStream 1010 ATM switch, a subinterface corresponds to a VP tunnel, so the VPI field of the control-vc must match the VPI field of the VP tunnel.
Example
The following example shows you how to create a Tag Switching subinterface on a router and how to select VPI 1 and VCI 34 as the control VC.
interface atm4/0.1 tag-switchingtag-switching iptag-switching atm control-vc 1 34Related Commands
show tag-switching interfaces
show tag-switching atm-tdp capabilitytag-switching atm maxhops
To limit the maximum hop counts to a value you have specified, use the tag-switching atm maxhops command. Use the no form of this command to disable this feature.
tag-switching atm maxhops
no tag-switching atm maxhopsSyntax Description
This command has no keywords or arguments.
Default
The default is 254.
Command Mode
Configuration
Usage Guidelines
When an ATM TSR receives a BIND REQUEST, it does not send a BIND back if the value in the request is equal to the maxhops value. Instead, the ATM TSR or TSR returns an error that specifies that the hop count has been reached.
When an ATM-TSR initiates a request for a tag binding, it includes a parameter specifying the maximum number of hops that the request should travel before reaching the edge of the ATM Tag Switching region. This is used to prevent forwarding loops in setting up tag paths across the ATM region.
Example
The following example shows how to set the hop limit to 2.
(config)# tag-switching atm maxhops 2
Related Commands
show tag-switching atm-tdp bindings
tag-switching atm vc-merge
To control whether vc-merge (multipoint-to-point) is supported for unicast tag VCs, use the tag-switching atm vc-merge command. Use the no form of this command to disable this feature.
tag-switching atm vc-merge
no tag-switching atm vc-merge
Syntax Description
This command has no keywords or arguments.
Default
The default is enabled if the hardware supports the ATM-VC merge capability.
Command Mode
Global configuration
Example
Since the default mode is to enable VC merge, you need not issue the tag-switching atm vc-merge command. However to disable VC merge, you must enter the no form of the command:
no tag-switching atm vc-mergeRelated Commands
show tag-switching atm-tdp capability
tag-switching atm vpi
To configure the range of values to use in the VPI field for tag VCs, use the tag-switching atm vpi command. To clear the interface configuration, use the no form of this command.
tag-switching atm vpi vpi [- vpi]
no tag-switching atm vpi vpi [- vpi]Syntax Description
vpi
Virtual path identifier (low end of range).
-vpi
(Optional.) Virtual path identifier (high end of range).
Default
The default is 1-1.
Command Mode
Interface configuration
Usage Guidelines
To configure ATM Tag Switching on a router interface (for example, an ATM Interface Processor), you must enable a Tag Switching subinterface.
Note
Use this command to select an alternate range of VPI values for ATM tag assignment on this interface. The two ends of the link negotiate a range defined by the intersection of the range configured at each end.
Example
The following example shows you how to create a subinterface and how to select a VPI range from VPI 1 to VPI 3:
interface atm4/0.1 tag-switchingtag-switching iptag-switching atm vpi 1-3Related Commands
tag-switching atm control-vc
tag-switching ip (configuration)
To allow Tag Switching of IPv4 packets, use the tag-switching ip command. To disable IP Tag Switching across all interfaces, use the no form of this command.
tag-switching ip
no tag-switching ipSyntax Description
This command has no arguments or keywords.
Default
Tag Switching of IPv4 packets is allowed.
Command Mode
Global configuration
Usage Guidelines
Dynamic Tag Switching (that is, distribution of tags based on routing protocols) is allowed by this optional command, but it is not actually enabled until the interface-level tag-switching ip command is issued on at least one interface. The no form of this command stops the distribution of dynamic tags, and the sending of outgoing tagged packets on all interfaces. The command does not affect the sending of tagged packets through TSP tunnels.
For a TC-ATM interface, the no form of this command prevents the establishment of tag VCs beginning at, terminating at, or passing through the platform.
Example
Since the default mode is to allow Tag Switching of IPv4 packets if enabled on an interface, this command is only needed to disable the feature globally.
The following example shows how to prevent the distribution of dynamic tags on all interfaces:
configure terminalno tag-switching ipRelated Commands
tag-switching ip (interface)
tag-switching ip (interface)
To enable Tag Switching of IPv4 packets on an interface, use the tag-switching ip interface configuration command. To disable IP Tag Switching on this interface, use the no form of this command.
tag-switching ip
no tag-switching ipSyntax Description
This command has no arguments or keywords.
Default
Tag Switching of IPv4 packets is disabled on this interface.
Command Mode
Interface configuration
Usage Guidelines
The first time this command is issued on any interface, dynamic Tag Switching is enabled on the router as a whole. TDP hello messages are issued on this interface. When an outgoing tag for a destination routed out through this interface is received, packets sent to that destination are assigned with that tag.
The no form of this command causes packets routed out through this interface to be sent untagged, and outgoing TDP hello messages are no longer sent.
When the no form is issued on the only interface of a router for which Tag Switching was enabled, dynamic Tag Switching is disabled on the router as a whole.
For a TC-ATM interface, the no form of this command prevents the establishment of tag VCs beginning at, terminating at, or passing through the platform.
Example
In the following example, Tag Switching is enabled on the specified Ethernet interface.
configure terminalinterface e0/2tag-switching ipRelated Commands
tag-switching advertise-tags
show tag-switching interfacestag-switching ip default-route
To enable the distribution of tags associated with the IP default route, use the tag-switching ip default-route command.
tag-switching ip default-route
Syntax Description
This command has no arguments or keywords.
Default
No distribution of IP default routes.
Command Mode
Global configuration
Usage Guidelines
Dynamic Tag Switching (that is, distribution of tags based on routing protocols) must be enabled before you can use the tag-switching ip default-route command.
Example
The following commands enable the distribution of tags associated with the IP default route:
configure terminaltag-switching iptag-switching ip default-routeRelated Commands
tag-switching ip (configuration)
tag-switching ip (interface)tag-switching mtu
To override the per-interface maximum transmission unit (MTU), use the tag-switching mtu interface configuration command. To restore the default, use the no form of this command.
tag-switching mtu bytes
no tag-switching mtuSyntax Description
Default
Minimum is 128 bytes; maximum depends on interface medium type.
Command Mode
Interface configuration
Usage Guidelines
If a tagged IP packet exceeds the MTU set for the interface, the Cisco IOS software will fragment it. All devices on a physical medium must have the same protocol MTU in order to operate.
Note
Example
The following example sets the maximum tagged packet size for the first serial interface to 300 bytes:
interface serial 0tag-switching mtu 300tag-switching tag-range downstream
To configure the size of the tag space for downstream unicast tag allocation, use the tag-switching tag-range downstream command. Use the no form of this command to revert to the platform defaults.
tag-switching tag-range downstream min max reserved
no tag-switching tag-range downstream min max reserved
Syntax Description
Default
The default values for the parameters just listed are as follows:
min—10
max—100000
reserved—16Command Mode
Global configuration
Example
The following example shows how to configure the size of the tag space for downstream unicast tag allocation. In the example, min is set with the value of 10, max is set with the value of 12000, and reserved is set with the value of 16.
tagsw-r9# configure terminalEnter configuration commands, one per line. End with Ctrl/Z.
Router(config)# tag-switching tag-range downstream 10 12000 16Router(config)#Related Commands
show tag-switching tdp parameters
tag-switching tdp discovery
To configure the interval between transmission of TDP discovery hello messages, or the hold time for a TDP transport connection, use the tag-switching tdp discovery global configuration command.
tag-switching tdp discovery {hello | directed hello} {holdtime | interval} seconds
Syntax Description
Default
The default values for holdtime and interval are
holdtime—15 seconds
interval—5 secondsCommand Mode
Global configuration
Example
In the following example, the interval for which a connection stays up if no hello messages are received is set to 5 seconds:
tag-switching tdp discovery hello holdtime 5Related Commands
show tag-switching tdp parameters
tag-switching tdp holdtime
tag-switching tdp holdtime
To enable TSP tunnel functionality on a device, use the tag-switching tdp holdtime command.
tag-switching tdp holdtime seconds
Syntax Description
seconds
The time for which a TDP session is maintained in the absence of TDP messages from the session peer device.
Default
The default value for the seconds parameter is 15.
Command Mode
Global configuration
Usage Guidelines
When a TDP session is initiated, the hold time is set to the lower of the values configured at the two ends.
Example
In the following example, the hold time of TDP sessions is configured for 30 seconds:
tag-switching tdp holdtime 30Related Commands
show tag-switching tdp parameters
tag-switching tdp discoverytag-switching tsp-tunnels (configuration)
To allow the operation of Tag-Switched Path (TSP) tunnels, use the tag-switching tsp-tunnels global configuration command. To disable the operation of TSP tunnels, use the no form of this command.
tag-switching tsp-tunnels
no tag-switching tsp-tunnels
Syntax Description
This command has no arguments or keywords.
Default
Off
Command Mode
Global configuration
Usage Guidelines
TSP tunnel operation is allowed on the device by this optional command, but proper operation also requires that the interface-level tag-switching tsp-tunnels command be issued on the interfaces that are used by TSP tunnels. The no form of this command completely disables TSP tunnel operation on the device.
Example
The following example shows how to allow TSP tunnel operation on a device:
configure terminalip cef distributed tag-switching tsp-tunnelsRelated Commands
ip cef distributed
show tag-switching tsp-tunnelstag-switching tsp-tunnels (interface)
To allow TSP tunnel operation over an interface, use the tag-switching tsp-tunnels interface configuration command. To disable TSP tunnel operation over an interface, use the no form of this command.
tag-switching tsp-tunnels
no tag-switching tsp-tunnels
Syntax Description
This command has no arguments or keywords.
Default
Off
Command Mode
Interface configuration
Usage Guidelines
TSP tunnel operation over a specific interface is allowed by this optional command. In order for TSP tunnels to operate over an interface, the tag-switching tsp-tunnels global configuration command must also be enabled. The no form of this command disables TSP tunnel operation over the specified interface.
Example
The following example shows how to allow TSP tunnel operation over an interface:
configure terminal ip cef distributed tag-switching tsp-tunnelsRelated Commands
ip cef distributed
show tag-switching tsp-tunnelstunnel mode tag-switching
To set the encapsulation mode of the tunnel to Tag Switching, use the tunnel mode tag-switching interface configuration command. Use the no form of this command to disable this feature.
tunnel mode tag-switching
no tunnel mode tag-switchingSyntax
This command has no arguments or keywords.
Command Mode
Interface configuration
Usage Guidelines
A tunnel interface number must be less than or equal to 65535.
The tunnel mode tag-switching command fails if the interface number is invalid for a TSP tunnel identifier.
Example
In the following example, the tunnel mode is set to Tag Switching:
interface tunnel 5 tunnel mode tag-switchingRelated Commands
interface tunnel
tunnel tsp-hoptunnel tsp-hop
To define hops in the path for the Tag Switching tunnel, use the tunnel tsp-hop interface configuration command. Use the no form of this command to remove these hops.
tunnel tsp-hop hop-number A.B.C.D [lasthop]
no tunnel tsp-hop hop-number A.B.C.D [lasthop]Syntax
Default
Off
Command Mode
Interface configuration
Usage Guideline
The list of tunnel hops must specify a strict source route for the tunnel. In other words, the router at hop <N> must be directly connected to the router at hop <N>+1.
Example
The following example shows the configuration of a two-hop tunnel. The first hop router/switch is 82.0.0.2, and the second and last hop is router/switch 81.0.0.2.
interface tunnel 5 tunnel mode tag-switching ip unnumbered e0/1 tunnel tsp-hop 1 82.0.0.2 tunnel tsp-hop 2 81.0.0.2 lasthopRelated Commands
interface tunnel
tunnel mode tag-switchingDebug Commands
This section contains an alphabetical listing of the Tag Switching debug commands and their descriptions. Documentation for each command includes a brief description of its use, command syntax, usage guidelines, sample output, and a description of that output.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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 an example of the display you see when you enter debug tag-switching adjacency:
Router# debug tag-switching adjacencyTAG ADJ: add 10.10.0.1, Ethernet0/0/0TAG ADJ: update 10.10.0.1, Ethernet0/0/0lists the significant fields shown in this display.
Table 12 Debug Tag-Switching Adjacency Command 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 an example of the display you see when you enter debug tag-switching atm-tdp api:
Router# debug tag-switching atm-tdp apiTailend Router Free tag Req 167.50.0.0 on ATM0/0.2 VPI/VCI 1/674TAGATM_API: received tag free requestinterface: ATM0/0.2 dir: in vpi: 1 vci: 674TAGATM_API: completed tag freeinterface: ATM0/0.2 vpi: 1 vci: 674result: TAGATM_OKlists the significant fields in this display.
Table 13
Debug Tag-Switching ATM-TDP API Field Descriptions
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
Here is an example of the display you see when you enter debug tag-switching atm-tdp routes:
Router# debug tag-switching atm-tdp routesCleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.7.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0AddNewRoute,153.7.0.0/16,idb=ATM0/0.2CleanupRoutes,153.7.0.0/16CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.8.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0AddNewRoute,153.8.0.0/16,idb=ATM0/0.2CleanupRoutes,153.8.0.0/16CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.9.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0AddNewRoute,153.9.0.0/16,idb=ATM0/0.2CleanupRoutes,153.9.0.0/16CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.10.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0AddNewRoute,153.10.0.0/16,idb=ATM0/0.2CleanupRoutes,153.10.0.0/16CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0tcatmFindRouteTags,153.11.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0AddNewRoute,153.11.0.0/16,idb=ATM0/0.2CleanupRoutes,153.11.0.0/16lists the significant fields in this display.
Table 14 Debug Tag-Switching ATM-TDP Routes Field Descriptions
Related Commands
debug 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
Here is an example of the display you see when you enter debug tag-switching atm-tdp states:
Router# debug tag-switching atm-tdp statesTransit Output 166.35.0.0 VPI/VCI 1/67 Active -> XmitRelease NoPathTransit Input 166.35.0.0 VPI/VCI 1/466 Active -> ApiWaitParentLoss ParentLossTransit Input 166.35.0.0 VPI/VCI 1/466 ApiWaitParentLoss -> ParentWait ApiSuccessTransit Input 166.35.0.0 VPI/VCI 1/466 ParentWait -> XmitWithdraw NoPathTransit Input 166.35.0.0 VPI/VCI 1/466 XmitWithdraw -> XmitWithdraw TransmitTransit Input 166.35.0.0 VPI/VCI 1/466 XmitWithdraw -> NonExistent ReleaseTransit Input 166.35.0.0 VPI/VCI 1/466 NonExistent -> NonExistent ApiSuccesslists the significant fields in this display.
Table 15 Debug Tag-Switching ATM-TDP States Field Descriptions
Transit Output
Output side of a TVC.
VPI/VCI
VC value.
Transit Input
Input side of a TVC.
Related Commands
debug 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
Description
Usage Guidelines
The optional interface parameter restricts the display to only those packets received or transmitted on the indicated interface.
Note
Sample Display
The following is an example of the display you see when you enter debug tag-switching packets:
Router# debug tag-switching packetsTAG: Hs3/0: recvd: CoS=0, TTL=254, Tag(s)=27TAG: Hs0/0: xmit: (no tag)TAG: Hs0/0: recvd: CoS=0, TTL=254, Tag(s)=30TAG: Hs3/0: xmit: CoS=0, TTL=253, Tag(s)=27lists the significant fields in this display.
Table 16
Debug Tag-Switching Packets Command Field Descriptions
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 an example of the display you see when you enter debug tag-switching tdp advertisements:
Router# debug tag-switching tdp advertisementstagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 99.101.0.8tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 172.27.32.28tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.105.0.8tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.92.0.8tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 10.205.0.8tagcon: adj 210.9.0.9:0 (pp 0x60D8E98C): advertise 210.8.0.8tagcon: 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)lists the significant fields in this display.
Table 17 Debug Tag-Switching TDP Advertisements Command Field Descriptions
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 an example of the display you see when you enter debug tag-switching tdp bindings:
Router# debug tag-switching tdp bindingstagcon: tibent(10.105.0.0/16): created; find route tags requesttagcon: tibent(10.105.0.0/16): lcl tag 1 (#2) assignedtagcon: tibent(10.102.0.0/16): created; find route tags requesttagcon: tibent(10.102.0.0/16): lcl tag 26 (#4) assignedtagcon: 210.9.0.9:0: 99.101.0.9 added to addr<->tdp ident maptagcon: 210.9.0.9:0: 172.27.32.29 added to addr<->tdp ident maptagcon: 210.9.0.9:0: 10.105.0.9 added to addr<->tdp ident maptagcon: tibent(172.27.32.0/22): rem tag 1 from 210.9.0.9:0 addedtagcon: tibent(200.26.0.0/16): rem tag 30 from 210.9.0.9:0 addedtagcon: tibent(210.8.0.8/32): created; remote tag learnedtagcon: tibent(210.8.0.8/32): rem tag 31 from 210.9.0.9:0 addedlists the significant fields in this display.
Table 18 Debug Tag-Switching TDP Bindings Command Field Descriptions
Related Commands
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 an example of the display you see when you enter debug tag-switching tdp directed-neighbors:
Router# debug tag-switching tdp directed-neighborstdp_directednbr: TDPDirAdj 10.11.10.11 received address addition notificationtdp_directednbr: TDPDirAdj 10.11.10.11 TDP peer settdp_directednbr: TDPDirAdj 10.11.10.11 received address deletion notificationtdp_directednbr: TDPDirAdj 10.11.10.11 peer clearedlists the significant fields in this display.
Table 19 Debug Tag-Switching TDP Directed-Neighbors Command Field Descriptions
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:
•
•
•
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 an example of the display you see when you enter debug tag-switching tdp peer state-machine:
Router# debug tag tdp peer state-machinetagcon: start TDP TCP timers for 202.0.0.1:1 (pp 0x60D8ABC8)tagcon: adj 202.0.0.1:1-1 (pp 0x60D8ABC8): Event unsol openunsol op pdg -> estabtagcon: start TDP TCP timers for 210.9.0.9:0 (pp 0x60D93608)tagcon: adj 210.9.0.9:0 (pp 0x60D93608): Event unsol openunsol op pdg -> estabtagcon: adj 210.9.0.9:0 (pp 0x60D93608): Event downestab -> dstroytagcon: adj 202.0.0.1:1 (pp 0x60D8ABC8): Event downestab -> dstroytagcon: start TDP TCP timers for 202.0.0.1:1 (pp 0x60DAC678)tagcon: adj 202.0.0.1:1-1 (pp 0x60DAC678): Event unsol openunsol op pdg -> defrdtagcon: start TDP TCP timers for 210.9.0.9:0 (pp 0x60D895C4)tagcon: adj 210.9.0.9:0 (pp 0x60D895C4): Event unsol openunsol op pdg -> defrdtagcon: adj 210.9.0.9:0 (pp 0x60D93608): Event cleanup donedstroy -> non-extagcon: adj 210.9.0.9:0 (pp 0x60D895C4): Event undeferdefrd -> estabtagcon: adj 202.0.0.1:1 (pp 0x60D8ABC8): Event cleanup donedstroy -> non-extagcon: adj 202.0.0.1:1-1 (pp 0x60DAC678): Event undeferdefrd -> establists the significant fields in this display.
Table 20 Debug Tag-Switching TDP Peer State-Machine Command Field Descriptions
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
Usage Guidelines
TDP requires periodic transmission of keep alive PIEs. If you do not specify the all option, periodic keep alive PIEs are not displayed.
Sample Display
The following is an example of the display you see when you enter debug tag-switching tdp pies received:
Router# debug tag tdp pies received alltdp: 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)lists the significant fields in this display.
Table 21 Debug Tag-Switching TDP Pies Received All Command Field Descriptions
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
Description
Usage Guidelines
TDP requires periodic transmission of keep alive PIEs. If you do not specify the all option, periodic keep alive PIEs are not displayed.
Sample Display
The following is an example of the display you see when you enter debug tag-switching tdp pies sent all:
Router# debug tag tdp pies sent alltdp: 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)lists the significant fields in this display.
Table 22 Debug Tag-Switching TDP PIEs Sent All Command Field Descriptions
Related Commands
debug tag-switching tdp pies received
debug tag-switching tdp session i/0debug 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
Description
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 keep alive PIEs. If you do not specify the all option, periodic keep alive PIEs are not displayed.
Sample Display
The following is an example of the display you see when you enter debug tag-switching tdp session io:
Router# debug tag-switching tdp session io alltdp: 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 0x040x01 0x00 0x00 0x1Etdp: 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 0x040x01 0x00 0x00 0x0Ftdp: 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 0x00tdp: 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 0x00tdp: 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 0x290x00 0x01 0x00 0x03 0x00 0x23 0x20 0x63 0x65 0x00 0x09 0x20 0xAC 0x1B 0x20 0x1D0x20 0x0A 0x69 0x00 0x09 0x20 0x0A 0x5C 0x00 0x09 0x20 0x0A 0x6F 0x00 0x09 0x200x0A 0xCD 0x00 0x09 0x20 0xD2 0x09 0x00 0x09tdp: 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 0xF00x00 0x00 0x00 0x00 0x00 0x01 0x00 0x02 0x00 0xE6 0x00 0x00 0x00 0x00 0x01 0x100x0A 0x6F 0x00 0x00 0x00 0x00 0x01 0x16 0xAC 0x1B 0x20 0x00 0x00 0x00 0x00 0x010x10 0xD2 0x09 0x00 0x00 0x00 0x00 0x1A 0x20 0x0A 0x0B 0x00 0x0B 0x00 0x00 0x00lists the significant fields in this display.
Table 23 Debug Tag-Switching TDP Session IO Command Field Descriptions
Related Commands
debug tag-switching tdp pies received
debug tag-switching tdp pies sentdebug 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:
•
•
•
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 an example of the display you see when you enter debug tag-switching tdp session state-machine:
Router# debug tag-switching tdp session state-machinetdp: adj:210.9.0.9(0x60DDBB4C): Event: Xport opened;Non-existent -> Init pasvtdp: tdp_create_ptcl_adj: tp = 0x60DDBB4C, ipaddr = 210.9.0.9tdp: adj:210.9.0.9(0x60DDBB4C): Event: Xport opened;Init pasv -> Init pasvtdp: adj:10.105.0.9(0x60DDBB4C): Event: Rcv TDP Open;Init pasv -> Open rcvd pasvtdp: adj:10.105.0.9(0x60DDBB4C): Event: Rcv TDP KA;Open rcvd pasv -> Opertdp: adj:unknown(0x60DDBB4C): Event: Xport closed;Oper -> Non-existentlists the significant fields in this display.
Table 24 Debug Tag-Switching TDP Session State-Machine Field Descriptions
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:
•
•
•
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 an example of the display you see when you enter debug tag-switching transport connections:
Router# debug tag-switching tdp transport connectionsDebug output at active peer:tdp: Opening conn; adj 0x60F7C604, 210.9.0.9 <-> 172.27.32.28tdp: Conn is up; adj 0x60F7C604, 210.9.0.9:11018 <-> 172.27.32.28:711tdp: Hold timer expired for adj 0x60F7C604, will close conntdp: Closing conn 210.9.0.9:11018 <-> 172.27.32.28:711, adj 0x60F7C604Debug output at passive peer:tdp: Incoming conn 172.27.32.28:711 <-> 210.9.0.9:11018tdp: Conn closed by peer; adj 0x60EB5FD4172.27.32.28:711 <-> 210.9.0.9:11018, Ethernet1/1/1tdp: Closing conn 172.27.32.28:711 <-> 210.9.0.9:11018, adj 0x60EB5FD4lists the significant fields in this display.
Table 25 Debug Tag-Switching TDP Transport Connections Field Descriptions
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:
•
•
•
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 an example of the display you see when you enter debug tag-switching tdp transport events:
Router# debug tag tdp transport eventstdp: Rcvd hello; Ethernet1/1/1, from 10.105.0.9 (210.9.0.9:0), intf_id 0, opt 0x4tdp: Hello from 10.105.0.9 (210.9.0.9:0) to 255.255.255.255, opt 0x4tdp: New adj 0x60DF6E50 from 10.105.0.9 (210.9.0.9:0), Ethernet1/1/1tdp: Rcvd hello; ATM3/0.1, from 200.26.0.4 (202.0.0.1:1), intf_id 1, opt 0x4, tcatmtdp: Rcvd hello; Ethernet1/1/1, from 10.105.0.9 (210.9.0.9:0), intf_id 0, opt 0x4tdp: Hello from 10.105.0.9 (210.9.0.9:0) to 255.255.255.255, opt 0x4tdp: Ignore Hello Timer for Ethernet1/1/1; intf not TDP readytdp: Send hello; Ethernet1/1/1, src/dst 10.105.0.8/255.255.255.255, inst_id 0tdp: Incoming conn 172.27.32.28:711 <-> 210.9.0.9:11019tdp: Found adj 0x60DF6E50 for 210.9.0.9 (Hello xport addr opt)tdp: New temporary adj 0x61033D38 from 210.9.0.9tdp: Real adj 0x60DF6E50 bound to 210.9.0.9:0, replacing temp adj 0x61033D38tdp: Adj 0x61033D38; state set to closedtdp: Rcvd hello; Ethernet1/1/1, from 10.105.0.9 (210.9.0.9:0), intf_id 0, opt 0x4tdp: Rcvd hello; ATM3/0.1, from 200.26.0.4 (202.0.0.1:1), intf_id 1, opt 0x4, tcatmtdp: Send hello; ATM3/0.1, src/dst 99.101.0.8/255.255.255.255, inst_id 1, tcatmtdp: Rcvd hello; Ethernet1/1/1, from 10.105.0.9 (210.9.0.9:0), intf_id 0, opt 0x4tdp: Send hello; Ethernet1/1/1, src/dst 10.105.0.8/255.255.255.255, inst_id 0tdp: Rcvd hello; ATM3/0.1, from 200.26.0.4 (202.0.0.1:1), intf_id 1, opt 0x4, tcatmlists the significant fields in this display.
Table 26 Debug Tag-Switching TDP Transport Events Field Descriptions
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:
•
•
•
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 an example of the display you see when you enter debug tag-switching tdp transport timers:
Router# debug tag-switching tdp transport timerstdp: Start holding timer; adj 0x60D5BC10, 200.26.0.4tdp: Start holding timer; adj 0x60EA9360, 10.105.0.9tdp: Start holding timer; adj 0x60D5BC10, 200.26.0.4tdp: Start holding timer; adj 0x60EA9360, 10.105.0.9tdp: Start holding timer; adj 0x60D5BC10, 200.26.0.4tdp: Start holding timer; adj 0x60EA9360, 10.105.0.9lists the significant fields in this display.
Table 27 Debug Tag-Switching TDP Transport Timers Command Field Descriptions
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 an example of the display you see when you enter debug tag-switching tfib cef
Router# debug tag-switching tfib cefCisco Express Forwarding related TFIB services debugging is ontagcon: tc_ip_rtlookup fail on 10.0.0.0/8:subnet_lookup failedTFIB: route tag chg 10.7.0.7/32,idx=1,inc=Withdrn,outg=Withdrn,enabled=0x2TFIB: fib complete delete: prefix=10.7.0.7/32,inc tag=26,delete_info=1TFIB: deactivate tag rew for 10.7.0.7/32,index=0TFIB: set fib rew: pfx 10.7.0.7/32,index=0,add=0,tag_rew->adj=Ethernet2/3TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parentTFIB: fib scanner start:needed:1,unres:0,mac:0,loadinfo:0TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parentTFIB: fib upd loadinf 10.100.100.100/32,tag=Tun_hd,fib no loadin,tfib no loadinTFIB: fib check cleanup for 10.100.100.100/32,index=0,return_value=0TFIB: fib_scanner_endTFIB: create dynamic entry for 10.11.0.11/32TFIB: call find_route_tags,dist_method=1,next_hop=10.93.0.11,Et2/3TFIB: route tag chg 10.11.0.11/32,idx=0,inc=26,outg=Unkn,enabled=0x3TFIB: create tag info 10.11.0.11/32,inc tag=26,has no infoTFIB: resolve tag rew,prefix=10.11.0.11/32,has tag_info,no parentTFIB: finish fib res 10.11.0.11/32:index 0,parent outg tag no parentTFIB: fib upd loadinf 10.11.0.11/32,tag=26,fib no loadin,tfib no loadinTFIB: set fib rew: pfx 10.11.0.11/32,index=0,add=1,tag_rew->adj=Ethernet2/3tagcon: route_tag_change for: 10.250.0.97/32intag 33, outtag 28, nexthop tsr 10.11.0.11:0TFIB: route tag chg 10.250.0.97/32,idx=0,inc=33,outg=28,enabled=0x3TFIB: deactivate tag rew for 10.250.0.97/32,index=0TFIB: set fib rew: pfx 10.250.0.97/32,index=0,add=0,tag_rew->adj=Ethernet2/3TFIB: create tag info 10.250.0.97/32,inc tag=33,has old infoOn VIP:TFIB: route tag chg 10.13.72.13/32,idx=0,inc=34,outg=Withdrn,enabled=0x3TFIB: deactivate tag rew for 10.13.72.13/32,index=0TFIB: set fib rew: pfx 10.13.72.13/32,index=0,add=0,tag_rew->adj=TFIB: create tag info 10.13.72.13/32,inc tag=34,has old infoTFIB: resolve tag rew,prefix=10.13.72.13/32,has tag_info,no parentTFIB: finish fib res 10.13.72.13/32:index 0,parent outg tag no parentTFIB: set fib rew: pfx 10.100.100.100/32,index=0,add=0,tag_rew->adj=TFIB: create tag info 10.100.100.100/32,inc tag=37,has old infoTFIB: resolve tag rew,prefix=10.100.100.100/32,has tag_info,no parentTFIB: finish fib res 10.100.100.100/32:index 0,parent outg tag no parentTFIB: fib upd loadinf 10.100.100.100/32,tag=37,fib no loadin,tfib no loadinlists the significant fields in this display. See for a description of special tag names seen in the debug output.
Table 28 Debug Tag-Switching TFIB CEF Command Field Descriptions
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 an example of the display you see when you enter debug tag-switching tfib enc. This example shows the encapsulations for three routes that have been created and placed into the TFIB.
Router# debug tag-switching tfib encTFIB: finish res:inc tag=28,outg=Imp_null,next_hop=10.93.72.13,Ethernet4/0/3TFIB: update_mac, mac_length = 14,addr=10.93.72.13,idb=Ethernet4/0/3TFIB: get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7TFIB: get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79TFIB: encaps:inc=28,outg=Imp_null,idb:Ethernet4/0/3,sizes 14,14,1504,type 0TFIB: finish res:inc tag=30,outg=27,next_hop=10.93.72.13,Ethernet4/0/3TFIB: get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7TFIB: get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79TFIB: encaps:inc=30,outg=27,idb:Ethernet4/0/3,sizes 14,18,1500,type 0TFIB: finish res:inc tag=30,outg=10,next_hop=0.0.0.0,ATM0/0.1TFIB: get ip adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=7TFIB: get tag adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=79TFIB: encaps:inc=30,outg=10,idb:ATM0/0,sizes 4,8,4470,type 1lists the significant fields in this display.
Table 29 Debug Tag-Switching TFIB ENC Command Field Descriptions
lists special tags, which sometimes appear in the debug output, and their meanings.
Table 30 Special Tags Seen in Debug Output
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 an example of the display you see when you enter debug tag-switching tfib state:
Router# debug tag-switching tfib stateTFIB enable/disable state debugging is onTFIB: Upd tag sb 6(status:0xC1,tmtu:1500,VPI:1-1 VC=0/32,et:0/0/0),lc 0x0TFIB: intf status chg: idb=Et4/0/2,status=0xC1,oldstatus=0xC3TFIB: interface dyntag change,change in state to Ethernet4/0/2TFIB: enable entered, table exists,enabler type=0x2TFIB: enable, TFIB already enabled, types now 0x3,returningTFIB: enable entered, table exists,enabler type=0x1TFIB: disable entered, table exists,type=0x1TFIB: cleanup: tfib[32] still non-0On linecard only:TFIB: disable lc msg recvd, type=0x1TFIB: Ethernet4/0/1 fibidb subblock message receivedTFIB: enable lc msg recvd, type=0x1TFIB: Tunnel301 set encapfix to 0x6016A97Clists the significant fields in this display.
Table 31 Debug Tag-Switching TFIB State Command Field Descriptions
Related Commands
debug tag-switching tfib enc
debug tag-switching tfib state
debug tag-switching tfib structdebug 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 an example of the display you see when you enter debug tag-switching tfib struct.
Router# debug tag-switching tfib structTFIB data structure changes debugging is onTFIB: delete tag rew, incoming tag 32TFIB: remove from tfib,inc tag=32TFIB: set loadinfo,tag=32,no old loadinfo,no new loadinfoTFIB: TFIB not in use. Checking for entries.TFIB: cleanup: tfib[0] still non-0TFIB: remove from tfib,inc tag=Tun_hdTFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfoTFIB: TFIB freed.TFIB: enable, TFIB allocated, size 4024 bytes, maxtag = 500TFIB: create tag rewrite: inc Tun_hd,outg UnknTFIB: add to tfib at Tun_hd, first in circular list, mac=0,enc=0TFIB: delete tag rew, incoming tag Tun_hdTFIB: remove from tfib,inc tag=Tun_hdTFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfoTFIB: create tag rewrite: inc Tun_hd,outg UnknTFIB: add to tfib at Tun_hd, first in circular list, mac=0,enc=0TFIB: create tag rewrite: inc 26,outg UnknTFIB: add to tfib at 26, first in circular list, mac=0,enc=0TFIB: add to tfib at 27, added to circular list, mac=0,enc=0TFIB: delete tag rew, incoming tag Tun_hdTFIB: remove from tfib,inc tag=Tun_hdTFIB: set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfoTFIB: add to tfib at 29, added to circular list, mac=4,enc=8TFIB: delete tag rew, incoming tag 29TFIB: remove from tfib,inc tag=29lists the significant fields in this display.
Table 32 Debug Tag-Switching TFIB Struct Command Field Descriptions
Related Commands
tag-switching tfib cef
tag-switching tfib enc
tag-switching tfib statedebug 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 an example of the display you see when you enter debug tag-switching tfib tsp:
Router# debug tag-switching tfib tspTSP-tunnel related TFIB services debugging is onTFIB: tagtun,next hop=10.93.72.13,inc=35,outg=1,idb=Et4/0/3TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=7,nh=10.93.72.13TFIB: tagtun,next hop=10.92.0.7,inc=36,outg=1,idb=Et4/0/2TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun tag chg linec,fiblc=0,in tg=36,o tg=1,if=6,nh=10.92.0.7TFIB: tagtun_delete, inc = 36tagtun tag del linec,itag=12TFIB: tagtun_delete, inc = 35tagtun tag del linec,itag=12TFIB: tagtun,next hop=10.92.0.7,inc=35,outg=1,idb=Et4/0/2TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=6,nh=10.92.0.7On VIP:TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfoTFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.92.0.7,if=6TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfolists the significant fields in this display.
Table 33 Debug Tag-Switching Tfib State Command Field Descriptions
Related Commands
debug tag-switching tfib enc
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 an example of the display you see when you enter debug tag-switching tsp-tunnels events:
Router# debug tag-switching tsp-tunnels eventsTSP-TUNNEL: received event for Tunnels Checkup Timer: timer firedTSP-TUNNEL: received event for Tunnel1206: Interface administratively downlists the significant fields in this display.
Table 34 Debug Tag-Switching TSP-Tunnels Events Command Field Descriptions
Related Commands
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 an example of the display you see when you enter debug tag-switching tsp-tunnels signalling:
Router# debug tag-switching tsp-tunnels signallingOpen at tunnel head:TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: RSVP head-end openOpen at tunnel tail:TSP-TUNNEL-SIG: received NEW PATH TAIL ARRIVAL event about tunnel 10.106.0.6 1206TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: RSVP tail-end openTSP-TUNNEL-SIG: tunnel 10.106.0.6 1206 NEW PATH TAIL ARRIVAL event handled successfullyState setup at tail hop:TSP-TUNNEL-SIG: received ADD RESV request for tunnel 10.106.0.6 1206TSP-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 1206State setup at intermediate hop:TSP-TUNNEL-SIG: received ADD RESV request for tunnel 10.106.0.6 1206TSP-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 1206State setup at head hop:TSP-TUNNEL-SIG: received ADD RESV request for tunnel 10.106.0.6 1206TSP-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 1206lists the significant fields in this display.
Table 35 Debug Tag-Switching TSP-Tunnels Signalling Command Field Descriptions
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 closeTSP-TUNNEL-SIG: received DELETE RESV request for tunnel 10.106.0.6 1206TSP-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 1206Output at intermediate hop:TSP-TUNNEL-SIG: received DELETE RESV request for tunnel 10.106.0.6 1206TSP-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 1206Output at tunnel tail:TSP-TUNNEL-SIG: received PATH TAIL DELETION event about tunnel 10.106.0.6 1206TSP-TUNNEL-SIG: tunnel 10.106.0.6 1206: RSVP tail-end closeTSP-TUNNEL-SIG: received DELETE RESV request for tunnel 10.106.0.6 1206TSP-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 1206TSP-TUNNEL-SIG: PATH TAIL DELETION event handled successfullyRelated Commands
debug tag-switching tsp-tunnels events
debug tag-switching tsp-tunnels taggingdebug 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 an example of the display you see when you enter debug tag-switching tsp-tunnels tagging:
Router# debug tag-switching tsp-tunnels taggingTSP-TUNNEL-TAGGING: tunnel 10.106.0.6 1206: fabric PROGRAM requestTSP-TUNNEL-TAGGING: tunnel 10.106.0.6 1206: programming tag VC 1/43 on output interface ATM0/0.1TSP-TUNNEL-TAGGING: background thread startingTSP-TUNNEL-TAGGING: background thread started (pid 57)TSP-TUNNEL-TAGGING: descriptor D7AB40: created [1 total]TSP-TUNNEL-TAGGING: descriptor D7AB40: continuing "Program" requestTSP-TUNNEL-TAGGING: descriptor D7AB40: allocated outgoing ATM VC 1/43 (vcd 12)TSP-TUNNEL-TAGGING: descriptor D7AB40: set "Interface Point Out State" to, allocatedTSP-TUNNEL-TAGGING: # of resource points held for "TC-ATM" interfaces: 1TSP-TUNNEL-TAGGING: enabling TFIB fabric programmingTSP-TUNNEL-TAGGING: TFIB is now enabledTSP-TUNNEL-TAGGING: descriptor D7AB40: set "Fabric State" to, enabledTSP-TUNNEL-TAGGING: descriptor D7AB40: set "Fabric Kind" to, default (TFIB)TSP-TUNNEL-TAGGING: descriptor D7AB40: set "Fabric State" to, setTSP-TUNNEL-TAGGING: tunnel 10.106.0.6 1206: fabric PROGRAM replyTSP-TUNNEL-TAGGING: background thread awaiting eventslists the significant fields in this display.
Table 36 Debug Tag-Switching TSP-Tunnels Tagging Command Field Descriptions
Related Commands
debug tag-switching tsp-tunnels signally
System Error Messages
This section lists and describes Cisco IOS Tag Switching system error messages. The system software sends these error messages to the console (and, optionally, to a logging server on another system) during operation. Not all system error messages indicate problems with your system. Some are purely informational, while others may help diagnose problems with communications lines, internal hardware, or the system software.
How to Read System Error Messages
System error messages begin with a percent sign (%) and are structured as follows:
%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-textFACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. lists the system facilities codes.
SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. lists the severity levels.
MNEMONIC is a code that uniquely identifies the error message.
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. lists the representations of variable fields and the type of information in them.
The following is a sample system error message:
%LINK-2-BADVCALL: Ints. TDR=[dec]
Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default is to log messages to the console at the debugging level (7). For more information, see the system configuration chapter and descriptions of the logging command in the appropriate Cisco IOS configuration guide and command reference publications.
Table 39 Representation of Variable Fields in Error Messages
Error Message Traceback Reports
Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative.
The following sample message includes traceback information:
-Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860Tag Switching Error Messages
This section lists the Tag Switching error messages.
Error Message%LLIST-3-OFFLIST: [chars] from 0x[hex], 0x[hex] not on listExplanation An internal inconsistency was detected when an attempt was made to remove from a list an item not on the list.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%LLIST-3-ONLIST: [chars] to 0x[hex], 0x[hex] on listExplanation An internal inconsistency was detected when an attempt was made to add to a list an item already on the list.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-ALLOC: Cannot alloc [chars]Explanation An attempt to allocate a tag-switching data structure failed because of a low memory condition.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical support representative for assistance.
Error Message%TAGCON-3-BUFFERBIND: unexpected error [dec]; peer [chars]; [chars]Explanation An unexpected failure occurred during the building of a TDP protocol information element (PIE) for transmission to a TDP peer device. It occurred when an attempt was made to add a tag binding or an address to the PIE.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-CONSISTENCY: [chars]Explanation An action attempted by the tag control process encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-DEADADJ: [inet]/[int], [chars]Explanation A problem was encountered in the cleanup following termination of a TDP session.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-DEFCASE_BINDING_PIE: Unexpected blist_type ([dec]) for [chars] PIE from peer [chars]Explanation A TDP PIE that was received from a TDP peer device contained an unexpected binding list type. The PIE will be ignored.
Recommended Action This is an informational message. The system ignores the PIE. This may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by the disabling of dynamic Tag Switching at the chassis level (enter the no tag ip command), waiting 15 to 20 seconds, and then reenabling it (enter the tag-switching ip command). Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-DIRADJTREE: [inet]/[int]; [chars]Explanation An operation on the TDP directed adjacency data structure failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-EVENTQ: Can't alloc work item for [chars]Explanation When a process, such as the TDP process, must request that the tag distribution and control process take some action, it queues a work item for the tag distribution and control process. If the attempt to queue the work item fails, the message shown here is generated. The failure can occur if the system is unable to allocate memory to hold the work request, or if the process has stopped accepting requests on its work queue.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-INIT: process cannot initializeExplanation The tag distribution and control process failed to initialize itself. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical support representative for assistance.
Error Message%TAGCON-3-LATREVNUMWRAP: Tag Local Address Table revision number wrappedExplanation The revision number used to manage advertisement of interface addresses to TDP peer devices overflowed. This results in faulty advertisement of interface addresses to TDP peer devices and faulty Tag Switching on those peer devices.
Recommended Action To restore proper interface address advertisement, reboot the platform. Report this condition to your technical support representative.
Error Message%TAGCON-3-NOTIMPL: peer [chars]; [chars] not implementedExplanation A TDP peer device has requested an action that is not currently implemented by the tag distribution and control subsystem.
Recommended Action The request is ignored. If it occurs repeatedly, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-PEERSM: TDP peer [int]([chars]): [chars]Explanation An operation involving the state machine for a TDP peer device failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-PROCESS: process not createdExplanation An attempt to create the tag distribution and control process failed. The probable cause is insufficient memory.
Recommended Action Reduce other system activity, if possible. If this message persists, call your technical support representative for assistance.
Error Message%TAGCON-3-RADIXTREE: TIB walk failed ([chars])Explanation Some Tag Information Base (TIB) maintenance operations involve a complete scan (walk) of the TIB data structure. This message is generated when a TIB walk encounters an unexpected failure.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-REGISTRY: Unexpected [chars] for reg_invoke_[chars]Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the error message text.
Error Message%TAGCON-3-SM: Unexpected event; state=[chars], event=[chars]Explanation An operation on the state machine for the tag distribution and control process failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-TDPID: peer [chars], TDP Id/Addr mapping problem ([chars])Explanation The tag distribution and control process maintains a data structure used to convert between the TDP identifier for a TDP peer device and the IP addresses of that peer device. This message is generated when an internal inconsistency is discovered in that data structure.
Recommended Action Disable dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), wait 15 to 20 seconds, and then reenable it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-3-TDPID_ADDR_TBL: [chars] sort bad; item [dec]Explanation The tag distribution and control process maintains a data structure used to convert between the TDP identifier for a TDP peer device and the IP addresses of that peer device. This message is generated when an internal inconsistency is discovered in that data structure.
Recommended Action Disable dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), wait 15 to 20 seconds, and then reenable it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-4-ADDRQ: Can't alloc work item for [int]Explanation When a new IP address for a TDP peer device is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an "address process." This message is generated when an attempt to queue work for the address process fails.
Recommended Action This is an informational message. The system remembers that it needs to do this work and regularly attempts to queue the necessary work item. If this message occurs repeatedly, copy it exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-4-ADDR_PROC: Can't create tagcon addr procExplanation When a new IP address for a TDP peer device is learned, it may be necessary to update the TFIB for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an "address process". This message is generated when an attempt to create the address process fails.
Recommended Action This is an informational message. As long as it needs the process, the system regularly attempts to create it. If this message occurs repeatedly, copy it exactly as it appears, and report it to your technical support representative.
Error Message%TAGCON-4-INIT_TAG_ALLOC: Failure to initialize tag allocation pool [dec]Explanation The system was unable to initialize the data structure used to support allocation of tags for Tag Switching for the specified tag pool.
Recommended Action The system ignores the event. However, because the system will not be able to allocate tags from the tag pool, it will not advertise them to peer devices. Therefore, it will not be able to forward tagged packets it receives (because it advertises no tags, it should not receive any tagged packets). Copy the message exactly as it appears, and report it along with the startup and running configuration to your technical support representative.
Error Message%TAGCON-5-SEND: cannot queue TDP [chars] pie for [int]([chars])Explanation An attempt to queue a TDP PIE for transmission to a TDP peer device failed.
Recommended Action This is an informational message. Failure to queue a PIE for a peer device should occur only when the TDP session with the peer device no longer exists. The software should recover from this situation by discarding the TDP session and trying to establish a new one. If this message occurs repeatedly, copy it exactly as it appears, and report it to your technical support representative.
Error Message%TCATM-3-BADINSERT: [inet]/[int] x[hex] to 0x[hex]Explanation An internal inconsistency was detected when an attempt was made to insert an item in a list.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TCATM-3-BADSTATE: [inet]/[int] [chars] [chars]->[chars]Recommended Action ATM TAG Control uses a table-driven state machine to keep track and transition a TVC through various states. A state transition occurs when a TVC receives one of many possible events. When this error occurs, it means that a TVC receives an event that it did not expect while in this state.
Recommended Action The system can continue, but may lose the TVC that generates this error. Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TCATM-3-NOTRUNNING: ATM-TAGCONTROL is not runningExplanation An attempt to request or to create a binding failed while the ATM tag-control system was not initialized. Probable cause is misconfiguration or low memory.
Recommended Action Reduce other system activity if possible, and call your technical support representative for assistance.
Error Message%TCATM-3-OFFLIST: [inet]/[int] 0x[hex] not on list 0x[hex]Explanation An internal inconsistency was detected when an attempt was made to remove from a list an item not on the list.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TCATM-3-ONLIST: [inet]/[int] 0x[hex] on list 0x[hex]Explanation An internal inconsistency was detected when an attempt was made to add to a list an item already on the list.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TCATM-3-PROCESS: process not createdExplanation An attempt to create the ATM tag control process failed. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible, and call your technical support representative for assistance.
Error Message%TCATM-3-UNEXPECTEDBIND: Interface [chars] received unexpected bind for [int]%mExplanation An unexpected bind is received for a prefix. This message appears only when a memory resource allocation failure prevents this peer device from asking the neighbor to release the bind. The system will continue, but the downstream neighbor could be holding a binding for which there is no matching VCI at this end.
Recommended Action Reduce other system activity if possible, and call your technical support representative for assistance.
Error Message%TCATM-4-HOP_EXCEEDED: Hop Count exceeded for [int]%m on [chars]Explanation This message appears when a loop is discovered in the network.
Recommended Action Check the configuration and network path for the relevant prefix.
Error Message%TCATM-4-MALFORMED_PIE: Interface [chars] malformed TDP PIEExplanation ATM TAG Control received a malformed PIE from TDP.
Recommended Action This does not affect system operation, but if the error persists, report it to your technical support representative.
Error Message%TCATM-4-NOTAGIP: Tag switching disabled on [chars]Explanation Tag Switching is not enabled on the specified interface. Tag VCI requests and advertising will be rejected. As a side effect, the VCI requests at the upstream device can remain in BindWait state until Tag Switching is reenabled on this interface.
Error Message%TCATM-4-ROUTING_LOOP: Possible routing loop [int]%m on [chars]Explanation This message appears when a loop is discovered in the network.
Recommended Action Check the configuration and network path for the relevant prefix.
Error Message%TDP-3-BAD_ADDRESS_LEN: peer [chars]; address len [dec]Explanation A TDP PIE containing an address with a bad length has been received from a peer device.
Recommended Action This is an informational message. The system ignores the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-BAD_METRIC_LEN: peer [chars]; metric len [dec]Explanation A TDP PIE containing a metric with a bad length has been received from a peer device.
Recommended Action This is an informational message. The system ignores the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-BAD_MLIST_TYPE: peer [chars]; mlist_type [dec]; [chars] pieExplanation A TDP PIE containing an unknown metric list type or one that is unexpected for the situation has been received from a peer device.
Recommended Action This is an informational message. The system ignores the PIE. This may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-BAD_PIE: peer [chars]; unknown pie type 0x[hex]Explanation An unknown TDP PIE type has been received from a peer device.
Recommended Action This is an informational message. The system ignores the PIE. This may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the no tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-BAD_PREFIX_LEN: peer [chars]; prefix len [dec]Explanation A TDP PIE containing a destination prefix with a bad length has been received from a peer device.
Recommended Action This is an informational message. The system ignores the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-CONSISTENCY: [chars]Explanation An action attempted by the TDP encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-GENERAL: [chars]Explanation An action attempted by the TDP implementation failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-KA_NOMEMORY: Can't alloc KA PIEExplanation An attempt to allocate a buffer for a TDP Keep Alive PIE has failed.
Recommended Action The system omits transmission of the TDP keep alive PIE. This may result in termination of one or more TDP sessions as the peer devices time out the sessions. If this message persists, reduce other system activity if possible, and call your technical support representative for assistance.
Error Message%TDP-3-MALFORMED_PIE: peer [chars]; format error for pie type 0x[hex]Explanation A malformed TDP PIE has been received from a TDP peer device.
Recommended Action This is an informational message. The system recovers from this situation by terminating the TDP session and attempting to establish a new session with the peer device. If this message occurs repeatedly, copy it exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-PTCLREAD: peer [chars], read failureExplanation An error occurred while attempting to read a TDP PDU received from a peer device.
Recommended Action This is an informational message. The system recovers from this situation by terminating the TDP session and attempting to establish a new session with the peer device. If this message occurs repeatedly, copy it exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-SM: unexpected event: peer [int]([chars]), state=[chars], event=[chars][chars]Explanation An operation on the state machine for a TDP peer device failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-TAGATM_BAD_RANGE: Interface [chars], Bad VPI range. Can't start a TDP sessionExplanation The VPI range exchanged between the TDP peer devices is nonoverlapping.
Recommended Action The system cannot create a TDP session between the affected TDP peer devices. Reissue the tag-switching vpi command on the appropriate interface with the correct VPI range.
Error Message%TDP-3-TAGATM_NOMEM: Interface [chars], Resource failure. Can't start a TDP sessionExplanation An attempt to allocate a buffer for TDP TAGATM VPI/VCI ranges has failed.
Recommended Action The system cannot create a TDP session between the affected TDP peer devices. If this message persists, reduce other system activity if possible, and call your technical support representative for assistance.
Error Message%TDP-3-UNEXPECTED_ALIST_TYPE: peer [chars]; alist_type [dec]; [chars] pieExplanation A TDP PIE containing an address list type that is unexpected for the situation has been received from a peer device.
Recommended Action This is an informational message. The system ignores the PIE. This may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the no tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-UNEXPECTED_BLIST_TYPE: peer [chars]; blist_type [dec]; [chars] pieExplanation A TDP PIE containing a binding list type that is unexpected for the situation has been received from a peer device.
Recommended Action This is an informational message. The system ignores the PIE. This may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the no tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-UNEXPECTED_PIE: peer [chars]; unexpected pie type 0x[hex]Explanation A TDP PIE that is unexpected for the situation has been received from a peer device.
Recommended Action This is an informational message. The system ignores the PIE. This may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-UNKNOWN_ALIST_TYPE: peer [chars]; alist_type [dec]; [chars] pieExplanation A TDP PIE containing an unknown address list type has been received from a peer device.
Recommended Action This is an informational message. The system ignores the PIE. This may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-3-UNKNOWN_BLIST_TYPE: peer [chars]; blist_type [dec]; [chars] pieExplanation A TDP PIE containing an unknown binding list type has been received from a peer device.
Recommended Action This is an informational message. The system ignores the PIE. This may result in impaired or faulty Tag Switching with the peer device. You might be able to correct the situation by disabling dynamic Tag Switching at the chassis level (enter the no tag-switching ip command), waiting 15 to 20 seconds, and then reenabling it (enter the tag-switching ip command). In addition, copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TDP-4-IDENT: cannot set chassis TDP identExplanation The TDP requires that each chassis have a TDP identifier. An attempt to set the TDP identifier for the chassis has failed.
Recommended Action This is an informational message. As long as it needs to set its chassis TDP identifier, the system periodically attempts to do so until it succeeds. If this message occurs repeatedly, copy it exactly as it appears, and report it to your technical support representative.
Error Message%TDP-4-PTCL: peer [chars], [chars]Explanation A violation of the TDP protocol by a TDP peer device has been detected.
Recommended Action This is an informational message. The system recovers from this situation by terminating the TDP session and attempting to establish a new session with the peer device. If this message occurs repeatedly, copy it exactly as it appears, and report it to your technical support representative.
Error Message%TDP-5-ACL: tag advertise-tags has no effect for tc-atmRecommended Action The tag-switching advertise-tags configuration command has no effect for tag-controlled ATM interfaces. The rationale for this behavior is summed up this way:
•
•
Recommended Action No action is required.
Error Message%TDP-5-ACL1: tag advertise-tags has no effect for tc-atmRecommended Action The tag-switching advertise-tags configuration command has no effect for tag-controlled ATM interfaces. The rationale for this behavior is summed up this way:
•
•
Recommended Action No action is required.
Error Message%TDP-5-INFO: [chars]Explanation This is an informational message generated by the TDP implementation.
Recommended Action No action is required.
Error Message%TFIB-2-BADENCAPLEN: Invalid encaps length [dec], tag size [dec]Recommended Action This is an informational message. The system omits the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TFIB-2-MEMORY: No memory for [chars]Explanation An operation on the Tag Forwarding Information Base (TFIB) requiring memory failed because of insufficient free memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical support representative for assistance.
Error Message%TFIB-7-INVALIDINDEX: Temporary path count difference for [inet]/[int], tfib entry [dec],loadinfo has [dec],fib has [dec]Explanation A temporary difference occurred between the Cisco Express Forwarding (CEF) data base and the TFIB. This difference will be resolved later.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TFIB-7-INVALIDTAG: Invalid tag [chars] [chars]Explanation An inval
