Table Of Contents

debug tarp events

debug tarp packets

debug tccs signaling

debug tdm

debug telco-return msg

debug telnet

debug text-to-fax

debug tftp

debug tgrm

debug tiff reader

debug tiff writer

debug time-range ipc

debug token ring

debug track

debug tsp

debug txconn all

debug txconn appc

debug txconn config

debug txconn data

debug txconn event

debug txconn tcp

debug txconn timer

debug udptn

debug v120 event

debug v120 packet

debug vg-anylan

debug video vicm

debug tarp events

To display information on Target Identifier Address Resolution Protocol (TARP) activity, use the debug tarp events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tarp events

no debug tarp events

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

For complete information on the TARP process, use the debug tarp packets command along with the debug tarp events command. Events are usually related to error conditions.

Examples

The following is sample output from the debug tarp events and debug tarp packets commands after the tarp resolve command was used to determine the NSAP address for the TARP target identifier (TID) named artemis.

Router# debug tarp events

Router# debug tarp packets

Router# tarp resolve artemis

Type escape sequence to abort.

Sending TARP type 1 PDU, timeout 15 seconds...

 NET corresponding to TID artemis is 49.0001.1111.1111.1111.00

*Mar  1 00:43:59: TARP-PA: Propagated TARP packet, type 1, out on Ethernet0

*Mar  1 00:43:59:        Lft = 100, Seq = 11, Prot type = 0xFE, URC = TRUE

*Mar  1 00:43:59:        Ttid len = 7, Stid len = 8, Prot addr len = 10

*Mar  1 00:43:59:        Destination NSAP: 49.0001.1111.1111.1111.00

*Mar  1 00:43:59:        Originator's NSAP: 49.0001.3333.3333.3333.00

*Mar  1 00:43:59:        Target TID: artemis

*Mar  1 00:43:59:        Originator's TID: cerd

*Mar  1 00:43:59: TARP-EV: Packet not propagated to 49.0001.4444.4444.4444.00 on 

         interface Ethernet0 (adjacency is not in UP state)

*Mar  1 00:43:59: TARP-EV: No route found for TARP static adjacency

         55.0001.0001.1111.1111.1111.1111.1111.1111.1111.00 - packet not sent

*Mar  1 00:43:59: TARP-PA: Received TARP type 3 PDU on interface Ethernet0

*Mar  1 00:43:59:        Lft = 100, Seq = 5, Prot type = 0xFE, URC = TRUE

*Mar  1 00:43:59:        Ttid len = 0, Stid len = 7, Prot addr len = 10

*Mar  1 00:43:59:        Packet sent/propagated by 49.0001.1111.1111.1111.af

*Mar  1 00:43:59:        Originator's NSAP: 49.0001.1111.1111.1111.00

*Mar  1 00:43:59:        Originator's TID: artemis

*Mar  1 00:43:59: TARP-PA: Created new DYNAMIC cache entry for artemis

Table 268 describes the significant fields in this display.

Table 268 debug tarp events Field Descriptions—tarp resolve Command 

Field	Descriptions
Sending TARP type 1 PDU	PDU requesting the NSAP of the specified TID.
timeout	Number of seconds the router will wait for a response from the Type 1 PDU. The timeout is set by the tarp t1-response-timer command.
NET corresponding to	NSAP address (in this case, 49.0001.1111.1111.1111.00) for the specified TID.
*Mar 1 00:43:59	Debug time stamp.
TARP-PA: Propagated	TARP packet: A Type 1 PDU was sent out on Ethernet interface 0.
Lft	Lifetime of the PDU (in hops).
Seq	Sequence number of the PDU.
Prot type	Protocol type of the PDU.
URC	Update remote cache bit.
Ttid len	Destination TID length.
Stid len	Source TID length.
Prot addr len	Protocol address length (bytes).
Destination NSAP	NSAP address that the PDU is being sent to.
Originator's NSAP	NSAP address that the PDU was sent from.
Target TID	TID that the PDU is being sent to.
Originator's TID	TID that the PDU was sent from.
TARP-EV: Packet not propagated	TARP event: The Type 1 PDU was not propagated on Ethernet interface 0 because the adjacency is not up.
TARP-EV: No route found	TARP event: The Type 1 PDU was not sent because no route was available.
TARP-PA: Received TARP	TARP packet: A Type 3 PDU was received on Ethernet interface 0.
Packet sent/propagated by	NSAP address of the router that sent or propagated the PDU.
TARP-PA: Created new DYNAMIC cache entry	TARP packet: A dynamic entry was made to the local TID cache.

Related Commands

Command	Description
debug tarp packets	Displays general information on TARP packets received, generated, and propagated on the router.

debug tarp packets

To display general information on TARP packets received, generated, and propagated on the router, use the debug tarp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tarp packets

no debug tarp packets

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

For complete information on the TARP process, use the debug tarp events command along with the debug tarp packet command. Events are usually related to error conditions.

Examples

The following is sample output from the debug tarp packet command after the tarp query command was used to determine the TID for the NSAP address 49.0001.3333.3333.3333.00:

Router# debug tarp packets

Router# debug tarp events

Router# tarp query 49.0001.3333.3333.3333.00

Type escape sequence to abort.

Sending TARP type 5 PDU, timeout 40 seconds...

 TID corresponding to NET 49.0001.3333.3333.3333.00 is cerdiwen

*Mar  2 03:10:11: TARP-PA: Originated TARP packet, type 5, to destination 
49.0001.3333.3333.3333.00

*Mar  2 03:10:11: TARP-PA: Received TARP type 3 PDU on interface Ethernet0

*Mar  2 03:10:11:        Lft = 100, Seq = 2, Prot type = 0xFE, URC = TRUE

*Mar  2 03:10:11:        Ttid len = 0, Stid len = 8, Prot addr len = 10

*Mar  2 03:10:11:        Packet sent/propagated by 49.0001.3333.3333.3333.af

*Mar  2 03:10:11:        Originator's NSAP: 49.0001.3333.3333.3333.00

*Mar  2 03:10:11:        Originator's TID: cerdiwen

*Mar  2 03:10:11: TARP-PA: Created new DYNAMIC cache entry for cerdiwen

Table 269 describes the significant fields shown in the display.

Table 269 debug tarp packets Field Descriptions—tarp query Command 

Field	Descriptions
Sending TARP type 5 PDU	PDU requesting the TID of the specified NSAP.
timeout	Number of seconds the router will wait for a response from the Type 5 PDU. The timeout is set by the tarp arp-request-timer command.
TID corresponding to NET	TID (in this case cerdiwen) for the specified NSAP address.
*Mar 2 03:10:11	Debug time stamp.
TARP-PA: Originated TARP packet	TARP packet: A Type 5 PDU was sent.
TARP P-A: Received TARP	TARP packet: A Type 3 PDU was received.
Lft	Lifetime of the PDU (in hops).
Seq	Sequence number of the PDU.
Prot type	Protocol type of the PDU.
URC	The update remote cache bit.
Ttid len	Destination TID length.
Stid len	Source TID length.
Prot addr len	Protocol address length (in bytes).
Packet sent/propagated	NSAP address of the router that sent or propagated the PDU.
Originator's NSAP	NSAP address that the PDU was sent from.
Originator's TID	TID that the PDU was sent from.
TARP-PA: Created new DYNAMIC cache entry	TARP packet: A dynamic entry was made to the local TID cache.

Related Commands

Command	Modification
debug tarp events	Displays information on TARP activity.

debug tccs signaling

To see information about the transparent CCS connection, use the debug tccs signaling command. To disable debugging output, use the no form of this command.

debug tccs signaling

no debug tccs signaling

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

EXEC

Command History

Release	Modification
12.0(7)XK	This command was introduced.
12.1(2)T	This command was integrated into the Cisco IOS 12.1(2)T release.

Usage Guidelines

Use this command with caution, because it displays every packet that the D channel transmits to the packet network and to the PBX. This command is CPU-intensive and should be used only as a last resort.

Use this command to debug a transparent CCS connection in the following cases:

•Observe the results of the ccs connect command results when you configure the setup.

•Observe CCS traffic at run time; the output shows the actual CCS packets received at run time and the number of packets received and sent.

Examples

The following example shows output from the command on both the originating and terminating sides:

Router# debug tccs signaling

TCCS Domain packet debugging is on

mazurka-4#

01:37:12: 1 tccs packets received from the port.

01:37:12: 1 tccs packets received from the nework.

01:37:12: tx_tccs_fr_pkt:pkt rcvd from network->tx_start

01:37:12: tx_tccs_fr_pkt: dlci=37, cid=100, payld-type =0,

        payld-length=162, cid_type=424

01:37:12: datagramsize=26

01:37:12: [0] A4 40 C0 0

01:37:12: [4] 86 86 86 86

01:37:12: [8] 86 86 86 86

01:37:12: [12] 86 86 86 86

01:37:12: [16] 86 86 86 86

01:37:12: [20] 86 86 86 86

01:37:12: [24] 86 86 11 48

01:37:12: 2 tccs packets received from the port.

01:37:12: 1 tccs packets received from the nework.

01:37:12: pri_tccs_rx_intr:from port->send_sub_channel

01:37:12: tccs_db->vcd = 37, tccs_db->cid = 100

01:37:12: pak->datagramsize=25

01:37:12: [0] A4 40 C0 0

01:37:12: [4] 42 43 43 43

01:37:12: [8] 43 43 43 43

01:37:12: [12] 43 43 43 43

01:37:12: [16] 43 43 43 43

01:37:12: [20] 43 43 43 43

01:37:12: [24] 43 43 43 0

Router# debug tccs signaling

00:53:26: 61 tccs packets received from the port.

00:53:26: 53 tccs packets received from the nework.

00:53:26: pri_tccs_rx_intr:from port->send_sub_channel

00:53:26: tccs_db->vcd = 37, tccs_db->cid = 100

00:53:26: pak->datagramsize=7

00:53:26: [0] A4 40 C0 0

00:53:26: [4] 0 1 7F 64

00:53:27: 62 tccs packets received from the port.

00:53:27: 53 tccs packets received from the nework.

00:53:27: pri_tccs_rx_intr:from port->send_sub_channel

00:53:27: tccs_db->vcd = 37, tccs_db->cid = 100

00:53:27: pak->datagramsize=7

00:53:27: [0] A4 40 C0 0

00:53:27: [4] 0 1 7F 64

00:53:28: 63 tccs packets received from the port.

00:53:28: 53 tccs packets received from the nework.

00:53:28: pri_tccs_rx_intr:from port->send_sub_channel

00:53:28: tccs_db->vcd = 37, tccs_db->cid = 100

00:53:28: pak->datagramsize=7

00:53:28: [0] A4 40 C0 0

00:53:28: [4] 0 1 7F 64

00:53:29: 64 tccs packets received from the port.

00:53:29: 53 tccs packets received from the nework.

debug tdm

To display time-division multiplexer (TDM) BUS CONNECTION information each time a connection is made on Cisco AS5300 access servers, use the debug tdm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tdm [api | detail | dynamic | pri | test | tsi | vdev]

no debug tdm [api | detail | dynamic | pri | test | tsi | vdev]

Syntax Description

api	(Optional) Displays a debug message whenever the TDM subsystem API is invoked from another subsystem.
detail	(Optional) Displays detailed messages (i.e., trace messages) whenever the TDM software executes.
dynamic	(Optional) Displays TDM debugging information whenever a backplane timeslot is allocated or deallocated.
pri	(Optional) Routes modem back-to-back connections from the modem-to-PRI board to modem board. By default, the modem back-to-back connections route from modem board to motherboard to modem board.
test	(Optional) Simulates the failure of allocating a TDM timeslot. Verifies that the software and TDM hardware recovers from the failure.
tsi	(Optional) Displays debugging information about the TSI Chip MT8980/MT90820 driver.
vdev	(Optional) TDM per voice device debug <0-2> slot and port number (that is, 0/1). Displays debug information whenever a modem board TDM connection is made.

Command Modes

Privileged EXEC

Usage Guidelines

The debug tdm command output is to be used primarily by a Cisco technical support representative. The debug tdm command enables display of debugging messages for specific areas of code that execute.

Examples

The following examples show the turning on of the debug option, performing a modem call, and turning off the debug option:

Router# debug tdm api

TDM API debugging is on

Router#

23:16:04: TDM(vdev reg: 0x3C500100/PRI reg: 0x3C400100): two way connection requested.

23:16:04: TDM(reg: 0x3C500100): Close connection to STo8, channel 1

23:16:04: TDM(reg: 0x3C500100): Connect STi4, channel 1 to STo8, channel 1

23:16:04: TDM(reg: 0x3C500100): Close connection to STo4, channel 1

23:16:04: TDM(reg: 0x3C500100): Connect STi8, channel 1 to STo4, channel 1

23:16:04: TDM(reg: 0x3C400100): Close connection to STo12, channel 31

23:16:04: TDM(reg: 0x3C400100): Close connection to STo8, channel 31

23:16:04: TDM(reg: 0x3C400100): Connect STi12, channel 31 to STo4, channel 1

23:16:04: TDM(reg: 0x3C400100): Connect STi4, channel 1 to STo12, channel 31

23:18:22: TDM(reg: 0x3C500100): default RX connection requested.

23:18:22: TDM(reg: 0x3C500100): Close connection to STo8, channel 1

23:18:22: TDM(reg: 0x3C500100): default TX connection requested.

23:18:22: TDM(reg: 0x3C500100): Close connection to STo4, channel 1

23:18:22: TDM(reg: 0x3C500100): Close connection to STo8, channel 1

23:18:22: TDM(reg: 0x3C500100): Close connection to STo4, channel 1

23:18:22: TDM(reg: 0x3C400100): default RX connection requested.

23:18:22: TDM(reg: 0x3C400100): Close connection to STo4, channel 1

23:18:22: TDM(reg: 0x3C400100): Connect STi12, channel 31 to STo8, channel 31

23:18:22: TDM(reg: 0x3C400100): default TX connection requested.

23:18:22: TDM(reg: 0x3C400100): Close connection to STo12, channel 31

23:18:22: TDM(reg: 0x3C400100): Connect STi8, channel 31 to STo12, channel 31

Router# no debug tdm api

TDM API debugging is off

Router# debug tdm detail

TDM Detail Debug debugging is on

router_2#show tdm pool 

Dynamic Backplane Timeslot Pool:

Grp ST Ttl/Free Req(Cur/Ttl/Fail)    Queues(Free/Used)   Pool Ptr

 0 0-3 128 128  0  0    0    0x60CB6B30 0x60CB6B30 0x60CB6B28

 1 4-7 128 128  0  3    0    0x60CB6B40 0x60CB6B40 0x60CB6B2C

Router#

Router# no debug tdm detail

TDM Detail Debug debugging is off

Router# debug tdm dynamic

TDM Dynamic BP Allocation debugging is on

Router#

23:30:16: tdm_allocate_bp_ts(), slot# 1, chan# 3

23:30:16: TDM(reg: 0x3C500100): Open Modem RX ST8, CH3 to BP ST4 CH3

23:30:16: TDM(reg: 0x3C500100): Open Modem TX ST8, CH3 to BP ST4 CH3

23:30:16: TDM Backplane Timeslot Dump @ 0x60E6D244, tdm_free_bptsCount[1] = 127

 vdev_slot : 0x01   bp_stream : 0x04

 vdev_channel : 0x03  bp_channel : 0x03   freeQueue : 0x60CB6B40

23:30:16: TDM(PRI:0x3C400100):Close PRI framer st12 ch31

23:30:16: TDM(PRI:0x3C400100):Close HDLC controller st8 ch31

23:30:43: tdm_deallocate_bp_ts(), slot# 1, chan# 3

23:30:43: TDM(reg: 0x3C500100):Close Modem RX ST8, CH3 to BP ST4 CH3

23:30:43: TDM(reg: 0x3C500100):Close Modem TX ST8, CH3 to BP ST4 CH3

23:30:43: TDM Backplane Timeslot Dump @ 0x60E6D244, tdm_free_bptsCount[1] = 128

 vdev_slot : 0x01   bp_stream : 0x04

 vdev_channel : 0x03  bp_channel : 0x03   freeQueue : 0x60CB6B40

Router#

Router# no debug tdm dynamic

TDM Dynamic BP Allocation debugging is off

Router# debug tdm pri

TDM connectvia PRI feature board debugging is on

Router# no debug tdm pri

TDM connectvia PRI feature board debugging is off

Router# debug tdm test

TDM Unit Test debugging is on

23:52:01: Bad tdm_allocate_bp_ts() call, simulating error condition for vdev in slot 1 

port 5

Router# no debug tdm test

TDM Unit Test debugging is off

Router# debug tdm tsi

TDM TSI debugging is on

Router#

23:56:40: MT90820(reg: 0x3C500100): Close connection to STi8, channel 9

23:56:40: MT90820(reg: 0x3C500100): Connect STi4, channel 10 to STo8, channel 9

23:56:40: MT90820(reg: 0x3C500100): Close connection to STi4, channel 10

23:56:40: MT90820(reg: 0x3C500100): Connect STi8, channel 9 to STo4, channel 10

23:56:40: MT90820(reg: 0x3C400100): Close connection to STi12, channel 31

23:56:40: MT90820(reg: 0x3C400100): Close connection to STi8, channel 31

23:56:40: MT90820(reg: 0x3C400100): Connect STi12, channel 31 to STo4, channel 10

23:56:40: MT90820(reg: 0x3C400100): Connect STi4, channel 10 to STo12, channel 31

23:57:03: MT90820(reg: 0x3C500100): Close connection to STi8, channel 9

23:57:03: MT90820(reg: 0x3C500100): Close connection to STi4, channel 10

23:57:03: MT90820(reg: 0x3C500100): Close connection to STi8, channel 9

23:57:03: MT90820(reg: 0x3C500100): Close connection to STi4, channel 10

23:57:03: MT90820(reg: 0x3C400100): Close connection to STi4, channel 10

23:57:03: MT90820(reg: 0x3C400100): Connect STi12, channel 31 to STo8, channel 31

23:57:03: MT90820(reg: 0x3C400100): Close connection to STi12, channel 31

23:57:03: MT90820(reg: 0x3C400100): Connect STi8, channel 31 to STo12, channel 31

Router#

Router# no debug tdm tsi

TDM TSI debugging is off

Router# debug tdm vdev ?

 <0-2> Slot/port number (i.e. 0/1)

Router# debug tdm vdev 1/8

Enabling TDM debug for voice device in slot 0 port 1

Router#

23:55:00: TDM(vdev reg: 0x3C500100/PRI reg: 0x3C400100): two way connection requested.

23:55:00: tdm_allocate_bp_ts(), slot# 1, chan# 8

23:55:00: TDM(reg: 0x3C500100): Open Modem RX ST8, CH8 to BP ST4 CH9

23:55:00: TDM(reg: 0x3C500100): Open Modem TX ST8, CH8 to BP ST4 CH9

23:55:00: TDM Backplane Timeslot Dump @ 0x60E6D2D4, tdm_free_bptsCount[1] = 127

 vdev_slot : 0x01   bp_stream : 0x04

 vdev_channel : 0x08  bp_channel : 0x09   freeQueue : 0x60CB6B40

23:55:00: TDM(PRI:0x3C400100):Close PRI framer st12 ch31

23:55:00: TDM(PRI:0x3C400100):Close HDLC controller st8 ch31

23:55:31: TDM(reg: 0x3C500100): default RX connection requested.

23:55:31: TDM(reg: 0x3C500100): default TX connection requested.

23:55:31: tdm_deallocate_bp_ts(), slot# 1, chan# 8

23:55:31: TDM(reg: 0x3C500100):Close Modem RX ST8, CH8 to BP ST4 CH9

23:55:31: TDM(reg: 0x3C500100):Close Modem TX ST8, CH8 to BP ST4 CH9

23:55:31: TDM Backplane Timeslot Dump @ 0x60E6D2D4, tdm_free_bptsCount[1] = 128

 vdev_slot : 0x01   bp_stream : 0x04

 vdev_channel : 0x08  bp_channel : 0x09   freeQueue : 0x60CB6B40

Router#

Router# no debug tdm vdev 1/8

Disabling TDM debug for voice device in slot 0 port 1

Router#

debug telco-return msg

To display debug messages for telco-return events, use the debug cable telco-return msg command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug cable telco-return msg

no debug cable telco-return msg

Syntax Description

This command has no arguments or keywords.

Defaults

Debugging for telco-return messages is not enabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(4)XI	This command was introduced.

Examples

ubr7223#debug cable telco-return msg

CMTS telco-return msg debugging is on

Related Commands

Command	Description
debug telco-return msg	Displays debug messages for telco-return events.

debug telnet

To display information about Telnet option negotiation messages for incoming Telnet connections to a Cisco IOS Telnet server, use the debug telnet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug telnet

no debug telnet

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
8.1	This command was introduced.

Examples

The following is sample output from the debug telnet command:

Router# debug telnet

*Oct 28 21:31:12.035:Telnet1/00:1 1 251 1

*Oct 28 21:31:12.035:TCP1/00:Telnet sent WILL ECHO (1)

*Oct 28 21:31:12.035:Telnet1/00:2 2 251 3

*Oct 28 21:31:12.035:TCP1/00:Telnet sent WILL SUPPRESS-GA (3)

*Oct 28 21:31:12.035:Telnet1/00:4 4 251 0

*Oct 28 21:31:12.035:TCP1/00:Telnet sent WILL BINARY (0)

*Oct 28 21:31:12.035:Telnet1/00:40000 40000 253 0

*Oct 28 21:31:12.035:TCP1/00:Telnet sent DO BINARY (0)

*Oct 28 21:31:12.035:Telnet1/00:10000000 10000000 253 31

*Oct 28 21:31:12.035:TCP1/00:Telnet sent DO WINDOW-SIZE (31)

*Oct 28 21:31:12.035:TCP1/00:Telnet received WILL TTY-TYPE (24)

*Oct 28 21:31:12.035:TCP1/00:Telnet sent DO TTY-TYPE (24)

*Oct 28 21:31:12.035:Telnet1/00:Sent SB 24 1

*Oct 28 21:31:12.035:TCP1/00:Telnet received WILL TTY-SPEED (32) (refused)

*Oct 28 21:31:12.035:TCP1/00:Telnet sent DONT TTY-SPEED (32)

*Oct 28 21:31:12.035:TCP1/00:Telnet received DO SUPPRESS-GA (3)

*Oct 28 21:31:12.035:TCP1/00:Telnet received WILL SUPPRESS-GA (3)

*Oct 28 21:31:12.035:TCP1/00:Telnet sent DO SUPPRESS-GA (3)

*Oct 28 21:31:12.035:TCP1/00:Telnet received DO ECHO (1)

*Oct 28 21:31:12.035:TCP1/00:Telnet received DO BINARY (0)

*Oct 28 21:31:12.035:TCP1/00:Telnet received WILL BINARY (0)

*Oct 28 21:31:12.059:TCP1/00:Telnet received WILL COMPORT (44)

*Oct 28 21:31:12.059:TCP1/00:Telnet sent DO COMPORT (44)

*Oct 28 21:31:12.059:TCP1/00:Telnet received DO COMPORT (44)

*Oct 28 21:31:12.059:TCP1/00:Telnet sent WILL COMPORT (44)

*Oct 28 21:31:12.059:TCP1/00:Telnet received WONT WINDOW-SIZE (31)

*Oct 28 21:31:12.059:TCP1/00:Telnet sent DONT WINDOW-SIZE (31)

*Oct 28 21:31:12.059:Telnet1/00:recv SB 24 0

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 10 TTY1/00:Telnet COMPORT rcvd bad

suboption:0xA/0x1E

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 1

*Oct 28 21:31:12.091:Telnet_CP-1/00 baudrate index 0

*Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 101 X.dctBXctBXctBX`W`P`>

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 2

*Oct 28 21:31:12.091:Telnet_CP-1/00 datasize index 8  8

*Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 102X.dctBXctBXctBX`W`P`>

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 3

*Oct 28 21:31:12.091:Telnet_CP-1/00 parity index 1  0

*Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 103 X.dctBXctBXctBX`W`P`>

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 4

*Oct 28 21:31:12.091:Telnet_CP-1/00 stopbits index 1

*Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 104 X.dctBXctBXctBX`W`P`>

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 5

*Oct 28 21:31:12.091:Telnet_CP-1/00 HW flow on

*Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 105 X.dctBXctBXctBX`W`P`>

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 11 nTTY1/00:Telnet COMPORT rcvd ba

d suboption:0xB/0xEE

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 5

*Oct 28 21:31:12.091:Telnet_CP-1/00 unimplemented option 0x10

*Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 105

*Oct 28 21:31:12.091:Telnet1/00:recv SB 44 5

*Oct 28 21:31:12.091:Telnet_CP-1/00 DTR on

*Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 105X.dctBXctBXctBX`W`P`>

*Oct 28 21:31:12.091:TCP1/00:Telnet received WONT WINDOW-SIZE (31)

*Oct 28 21:31:12.099:Telnet1/00:Sent SB 44 107 3

*Oct 28 21:31:12.099:COMPORT1/00:sending notification 0x33

Table 270 describes the significant fields shown in the display.

Table 270 debug telnet Field Descriptions 

Field	Description
Telnet1/00: 1 1 251 1	Untranslated decimal option negotiations that are sent. 1/00 denotes the line number that the Telnet server is operating on.
TCP1/00:	Symbolically decoded option negotiations. 1/00 denotes the line number that the Telnet server is operating on. Telnet option negotiations are defined in the following RFCs: •RFC 854—Telnet Protocol Specification •RFC 856—Telnet Binary Transmission •RFC 858—Telnet Suppress Go Ahead Option •RFC 1091—Telnet Terminal-Type Option •RFC 1123, sec. 3—Requirements for Internet Hosts—Application and Support •RFC 2217—Telnet Com Port Control Option

Related Commands

Command	Description
debug ip tcp transactions	Displays information on significant TCP transactions such as state changes, retransmissions, and duplicate packets.
debug modem	Displays modem line activity on an access server.

debug text-to-fax

To the off-ramp text-to-fax conversion, use the debug text-to-fax EXEC command to show information relating. To disable debugging output, use the no form of this command.debug text-to-fax

debug text-to-fax

no debug text-to-fax

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command History

Release	Modification
12.0(4)T	This command was introduced.

Examples

The following debug output shows the off-ramp text-to-fax conversion.

Router# debug text-to-fax 

Text to fax debugging is on

Router#6d03h: text2fax_data_handler: START_OF_CONNECTION

6d03h: text2fax_data_handler: new_context

6d03h: text2fax_data_handler: resolution: fine

6d03h: text2fax_data_handler: buffer size: 50

6d03h: text2fax_put_buffer: START_OF_FAX_PAGE

6d03h: text2fax_put_buffer: START_OF_FAX_PAGE

6d03h: text2fax_put_buffer: END_OF_FAX_PAGE. Dial now ...if not in progress

6d03h: text2fax_data_handler: START_OF_DATA

6d03h: text2fax_data_handler: END_OF_DATA

6d03h: text2fax_data_handler: Dispose context

6d03h: text2fax_data_handler: START_OF_CONNECTION

6d03h: text2fax_data_handler: END_OF_CONNECTION

6d03h: %FTSP-6-FAX_CONNECT: Transmission

6d03h: %FTSP-6-FAX_DISCONNECT: Transmission

6d03h: %LINK-3-UPDOWN: Interface Serial1:22, changed state to down

debug tftp

To display Trivial File Transfer Protocol (TFTP) debugging information when encountering problems netbooting or using the copy tftp system:running-config or copy system:running-config tftp commands, use the debug tftp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tftp

no debug tftp

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Examples

The following is sample output from the debug tftp command from the copy system:running-config tftp EXEC command:

Router# debug tftp

TFTP: msclock 0x292B4; Sending write request (retry 0), socket_id 0x301DA8

TFTP: msclock 0x2A63C; Sending write request (retry 1), socket_id 0x301DA8

TFTP: msclock 0x2A6DC; Received ACK for block 0,  socket_id 0x301DA8

TFTP: msclock 0x2A6DC; Received ACK for block 0,  socket_id 0x301DA8

TFTP: msclock 0x2A6DC; Sending block 1 (retry 0), socket_id 0x301DA8

TFTP: msclock 0x2A6E4; Received ACK for block 1,  socket_id 0x301DA8

Table 271 describes the significant fields in the first line of output.

Table 271 debug tftp Field Descriptions 

Message	Description
TFTP:	TFTP packet.
msclock 0x292B4;	Internal timekeeping clock (in milliseconds).
Sending write request (retry 0)	TFTP operation.
socket_id 0x301DA8	Unique memory address for the socket for the TFTP connection.

debug tgrm

To display debug messages for all trunk groups, use the debug tgrm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tgrm

no debug tgrm

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(3)T	This command was introduced.
12.2(2)XB1	This command was implemented on the Cisco AS5850 platform.
12.2(11)T	This command was integrated into Cisco IOS Release 12.2(11)T, and support was added for the Cisco AS5850 platform.

Examples

The following examples show output of the debug tgrm command.

This message indicates which interface was selected for the outgoing voice call:

TGRM:tgrm_select_interface() - Interface Serial0:23 selected

This message indicates that the outgoing voice call was denied because of trunk group configuration (Allowed shows the max-calls value):

TGRM:tgrm_select_interface() - Outgoing voice call denied. Allowed = 5, Current = 6

This message indicates that the trunk group has no interfaces belonging to it:

TGRM:tgrm_select_interface() - Trunk group 3 has no members

This message indicates that the outgoing voice or modem call was denied because of trunk group configuration (Allowed shows the max-calls value). For a data call, the message is "Outgoing data call denied."

TGRM:Serial0:23:tgrm_accept_call() - Outgoing voice call denied. Allowed = > 5,  
Current = 6

This message indicates that the incoming data call was denied because of trunk group configuration (Allowed shows the max-calls value). For a voice call, the message is "Incoming voice call denied."

TGRM:Serial0:23:tgrm_accept_call() - Incoming data call denied. Allowed = 5, Current = 6

Related Commands

Command	Description
debug cdapi events	Displays information about the CDAPI.
debug isdn events	Displays ISDN events occurring on the user side (on the router) of the ISDN interface.
debug isdn q931	Displays information about call setup and teardown of ISDN network connections (Layer 3) between the local router (user side) and the network.
trunk group (global)	Defines a trunk group globally.
trunk-group (interface)	Assigns a specified interface to a defined trunk group.

debug tiff reader

To display output about the off-ramp TIFF reader, use the debug tiff reader EXEC command. To disable debugging output, use the no form of this command.

debug tiff reader

no debug tiff-reader

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Defaults

Disabled

Command History

Release	Modification
12.0(4)T	This command was introduced.

Examples

The following debug example displays information about the off-ramp TIFF reader.

Router# debug tiff reader

*Jan 1 18:59:13.683: tiff_reader_data_handler: new context

*Jan 1 18:59:13.683: tiff_reader_data_handler: resolution: standard

*Jan 1 18:59:13.683: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
ENGINE_START/DONE gggg(pl 616E9994)

*Jan 1 18:59:13.691: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.699: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

*Jan 1 18:59:13.703: tiff_reader_put_buffer: START_OF_FAX_PAGEi>> tiff_reader_engine() 
case FAX_EBUFFER gggg

*Jan 1 18:59:13.711: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.719: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.727: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.735: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.743: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.751: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.759: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.767: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.775: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.787: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.795: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.803: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.811: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.819: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.827: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.835: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.843: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.851: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.863: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.871: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.879: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.887: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.895: tiff_reader_data_handler: buffer size: 1524

*Jan 1 18:59:13.903: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() 
case FAX_EBUFFER pppp(pl 616E9994)

i>> tiff_reader_engine() case FAX_EBUFFER gggg

*Jan 1 18:59:13.907: tiff_reader_data_handler: buffer size: 311i>> tiff_r_finish() 
END_OF_FAX_PAGE pppp

*Jan 1 18:59:13.907: tiff_reader_put_buffer: END_OF_FAX_PAGE. Dial now ...if not in 
progress

*Jan 1 18:59:13.907: tiff_reader_data_handler: END_OF_DATA

*Jan 1 18:59:13.907: tiff_reader_data_handler: BUFF_END_OF_PART

*Jan 1 18:59:13.907: tiff_reader_data_handler: Dispose context

Related Commands

Command	Description
debug tiff writer	Displays output about the on-ramp TIFF writer.

debug tiff writer

To display output about the on-ramp TIFF writer, use the debug tiff writer EXEC command. To disable debugging output, use the no form of this command.

debug tiff writer

debug tiff-writer

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

EXEC

Command History

Release	Modification
12.0(4)T	This command was introduced.

Examples

The following debug example shows information about the off-ramp TIFF writer.

Router# debug tiff writer

*Jan 1 18:54:59.419: tiff_writer_data_process: START_OF_CONNECTION

18:55:10: %FTSP-6-FAX_CONNECT: Reception

*Jan 1 18:55:14.903: tiff_writer_data_process: START_OF_FAX_PAGE

*Jan 1 18:55:14.903: tiff_writer_data_process: tiff file created = 2000:01:01 18:55:14

18:55:21: %FTSP-6-FAX_DISCONNECT: Reception

*Jan 1 18:55:19.039: tiff_writer_data_process: END_OF_CONNECTION or ABORT_CONNECTION

*Jan 1 18:55:19.039: tiff_writer_put_buffer: END_OF_FAX_PAGE

*Jan 1 18:55:19.039: send TIFF_PAGE_READY

*Jan 1 18:55:19.039: send TIFF_PAGE_READY

18:55:21: %LINK-3-UPDOWN: Interface Serial2:0, changed state to down

Related Commands

Command	Description
debug tiff reader	Displays output about the on-ramp TIFF reader.

debug time-range ipc

To enable debugging output for monitoring the time-range ipc messages between the Route Processor and the line card, use the debug time-range ipc command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug time-range ipc

no debug time-range ipc

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(2)T	This command was introduced.

Examples

The following is sample output from the debug time-range ipc command. In the following example, the time ranges sent to the line card are monitored:

Router# debug time-range ipc

00:14:19:TRANGE-IPC:Sent Time-range t1 ADD to all slots

00:15:22:TRANGE-IPC:Sent Time-range t1 ADD to all slots

In the following example, the time ranges deleted from the line card are monitored:

Router# debug time-range ipc

00:15:42:TRANGE-IPC:Sent Time-range t1 DEL to all slots

00:15:56:TRANGE-IPC:Sent Time-range t1 DEL to all slots

Related Commands

Command	Description
show time-range ipc	Displays the statistics about the time-range ipc messages between the Route Processor and line card.

debug token ring

To display messages about Token Ring interface activity, use the debug token ring command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug token ring

no debug token ring

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

This command reports several lines of information for each packet sent or received and is intended for low traffic, detailed debugging.

The Token Ring interface records provide information regarding the current state of the ring. These messages are only displayed when the debug token events command is enabled.

The debug token ring command invokes verbose Token Ring hardware debugging. This includes detailed displays as traffic arrives and departs the unit.

---

Caution It is best to use this command only on router and bridges with light loads.

---

Examples

The following is sample output from the debug token ring command:

Router# debug token ring

TR0: Interface is alive, phys. addr 5000.1234.5678

TR0:  in: MAC: acfc: 0x1105 Dst: c000.ffff.ffff Src: 5000.1234.5678 bf: 0x45

TR0:  in:   riflen 0, rd_offset 0, llc_offset 40

TR0: out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00

TR0: out: LLC: AAAA0300 00009000 00000100 AAC00000 00000802 50001234 ln: 28

TR0:  in: MAC: acfc: 0x1140 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x09

TR0:  in: LLC: AAAA0300 00009000 00000100 AAC0B24A 4B4A6768 74732072 ln: 28

TR0:   in:   riflen 0, rd_offset 0, llc_offset 14

TR0: out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00

TR0: out: LLC: AAAA0300 00009000 00000100 D1D00000 FE11E636 96884006 ln: 28

TR0:  in: MAC: acfc: 0x1140 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x09

TR0:  in: LLC: AAAA0300 00009000 00000100 D1D0774C 4DC2078B 3D000160 ln: 28

TR0:  in:   riflen 0, rd_offset 0, llc_offset 14

TR0: out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00

TR0: out: LLC: AAAA0300 00009000 00000100 F8E00000 FE11E636 96884006 ln: 28

Table 272 describes the significant fields in the second line of output.

Table 272 debug token ring Field Descriptions 

Message	Description
TR0:	Name of the interface associated with the Token Ring event.
in:	Indication of whether the packet was input to the interface (in) or output from the interface (out).
MAC:	Type of packet, as follows: •MAC—Media Access Control •LLC—Link Level Control
acfc: 0x1105	Access Control, Frame Control bytes, as defined by the IEEE 802.5 standard.
Dst: c000.ffff.ffff	Destination address of the frame.
Src: 5000.1234.5678	Source address of the frame.
bf: 0x45	Bridge flags for internal use by technical support staff.

Table 273 describes the significant fields shown in the third line of output.

Table 273 debug token ring Field Descriptions 

Message	Description
TR0:	Name of the interface associated with the Token Ring event.
in:	Indication of whether the packet was input to the interface (in) or output from the interface (out).
riflen 0	Length of the RIF field (in bytes).
rd_offset 0	Offset (in bytes) of the frame pointing to the start of the RIF field.
llc_offset 40	Offset in the frame pointing to the start of the LLC field.

Table 274 describes the significant fields shown in the fifth line of output.

Table 274 debug token ring Field Descriptions 

Message	Description
TR0:	Name of the interface associated with the Token Ring event.
out:	Indication of whether the packet was input to the interface (in) or output from the interface (out).
LLC:	Type of frame, as follows: •MAC—Media Access Control •LLC—Link Level Control
AAAA0300	This and the octets that follow it indicate the contents (hex) of the frame.
ln: 28	The length of the information field (in bytes).

debug track

To display tracking activity for tracked objects, use the debug track command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug track

no debug track

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(15)T	This command was introduced.

Usage Guidelines

Use this command to display activity for objects being tracked by the tracking process. These objects can be the state of IP routing, the line-protocol state of an interface, IP route reachability, and the IP route metric threshold.

Examples

The following example shows that object number 100 is being tracked and the state of IP routing on Ethernet interface 0/2 is down:

Router# debug track

Feb 26 19:56:23.247:Track:100 Adding interface object

Feb 26 19:56:23.247:Track:Initialise

Feb 26 19:56:23.247:Track:100 New interface Et0/2, ip routing Down

Feb 26 19:56:23.247:Track:Starting process

The following example shows that object number 100 is being tracked and the state of IP routing on Ethernet interface 0/2 has changed and is back up:

Router# debug track

Feb 26 19:56:41.247:Track:100 Change #2 interface Et0/2, ip routing Down->Up

00:15:07:%LINK-3-UPDOWN:Interface Ethernet0/2, changed state to up

00:15:08:%LINEPROTO-5-UPDOWN:Line protocol on Interface Ethernet0/2, changed state to up

Related Commands

Command	Description
show track	Displays tracking information.

debug tsp

To display information about the telephony service provider (TSP), use the debug tsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tsp {all | call | error | port}

no debug tsp {all | call | error | port}

Syntax Description

all	Enables all TSP debugging (except statistics)
call	Enables call debugging.
error	Error debugging.
port	Port debugging.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(6)T	This command was introduced.

Examples

The following example shows output for the debug tsp all command:

01:04:12:CDAPI TSP RX ===> callId=(32 ), Msg=(CDAPI_MSG_CONNECT_IND,1 ) 
Sub=(CDAPI_MSG_SUBTYPE_NULL,0 )cdapi_tsp_connect_ind 

01:04:12:TSP CDAPI:cdapi_free_msg returns 1

01:04:13:tsp_process_event:[0:D, 0.1 , 3] tsp_cdapi_setup_ack tsp_alert

01:04:13:tsp_process_event:[0:D, 0.1 , 5] tsp_alert_ind 

01:04:13:tsp_process_event:[0:D, 0.1 , 10] 

01:04:14:tsp_process_event:[0:D, 0.1 , 10] 

01:04:17:CDAPI TSP RX ===> callId=(32 ), Msg=(CDAPI_MSG_DISCONNECT_IND,7 ) 
Sub=(CDAPI_MSG_SUBTYPE_NULL,0 )cdapi_tsp_disc_ind 

01:04:17:TSP CDAPI:cdapi_free_msg returns 1

01:04:17:tsp_process_event:[0:D, 0.1 , 27] cdapi_tsp_release_indtsp_disconnet_tdm 

01:04:17:tsp_process_event:[0:D, 0.4 , 7] cdapi_tsp_release_comp

Related Commands

Command	Description
debug track	Displays information about the telephony service provider.
debug voip rawmsg	Displays the raw message owner, length, and pointer.

debug txconn all

To turn on all debug flags for CTRC communications with CICS, use the debug txconn all command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug txconn all

no debug txconn all

Syntax Description

This command has no arguments or keywords.

Defaults

By default, debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.

Examples

The following example shows the immediate output of the debug txconn all command. For examples of specific debugging messages, see the examples provided for the debug txconn appc, debug txconn config, debug txconn data, debug txconn event, debug txconn tcp, and debug txconn timer commands.

Router# debug txconn all

All possible TXConn debugging has been turned on

Related Commands

Command	Description
debug snasw	Displays debugging information related to SNA Switching Services.
debug txconn appc	Displays APPC-related trace or error messages for communications with CICS.
debug txconn config	Displays trace or error messages for CTRC configuration and control blocks for CICS communications.
debug txconn data	Displays CICS client and host data being handled by CTRC, in hexadecimal notation.
debug txconn event	Displays trace or error messages for CTRC events related to CICS communications.
debug txconn tcp	Displays error messages or traces for TCP/IP communications with CICS.
debug txconn timer	Displays performance information related to CICS communications.
show debugging	Displays the state of each debugging option.

debug txconn appc

To display APPC-related trace or error messages for communications with CICS, use the debug txconn command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug txconn appc

no debug txconn appc

Syntax Description

This command has no arguments or keywords.

Defaults

By default, debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.

Examples

The following example shows APPC debugging output from the debug txconn appc command:

01:18:05: TXCONN-APPC-622ADF38: Verb block =

01:18:05: TXCONN-APPC-622ADF38:  0001 0200 0300 0000 0400 0000 0000 0000

01:18:05: TXCONN-APPC-622ADF38:  0000 00FC 0000 0000 0000 0000 0000 0000

01:18:05: TXCONN-APPC-622ADF38:  0000 0000 0840 0007 0000 0000 0000 0000

01:18:05: TXCONN-APPC-622ADF38:  7BC9 D5E3 C5D9 4040 07F6 C4C2 4040 4040

01:18:05: TXCONN-APPC-622ADF38:  4040 4040 4040 4040 4040 4040 4040 4040

01:18:05: TXCONN-APPC-622ADF38:  4040 4040 4040 4040 4040 4040 4040 4040

01:18:05: TXCONN-APPC-622ADF38:  4040 4040 4040 4040 4040 4040 4040 4040

01:18:05: TXCONN-APPC-622ADF38:  4040 4040 4040 4040 0000 0000 0000 0000

01:18:05: TXCONN-APPC-622ADF38:  0000 0000 0000 0000 0000 0000 0000 0000

01:18:05: TXCONN-APPC-622ADF38:  0000 0000 0000 0000 0000 0000 0000 0000

01:18:05: TXCONN-APPC-622ADF38:  00E2 E3C1 D9E6 4BC7 C1E9 C5D3 D3C5 4040

01:18:05: TXCONN-APPC-622ADF38:  4040 0000 0000 0000 0000 0000

01:18:05: TXCONN-APPC-621E5730: Verb block =

01:18:05: TXCONN-APPC-621E5730:  0001 0200 0300 0000 0400 0000 0000 0000

01:18:05: TXCONN-APPC-621E5730:  0000 00FD 0000 0000 0000 0000 0000 0000

01:18:05: TXCONN-APPC-621E5730:  0000 0000 0840 0007 0000 0000 0000 0000

01:18:05: TXCONN-APPC-621E5730:  C9C2 D4D9 C4C2 4040 07F6 C4C2 4040 4040

01:18:05: TXCONN-APPC-621E5730:  4040 4040 4040 4040 4040 4040 4040 4040

01:18:05: TXCONN-APPC-621E5730:  4040 4040 4040 4040 4040 4040 4040 4040

01:18:05: TXCONN-APPC-621E5730:  4040 4040 4040 4040 4040 4040 4040 4040

01:18:05: TXCONN-APPC-621E5730:  4040 4040 4040 4040 0000 0000 0000 0000

01:18:05: TXCONN-APPC-621E5730:  0000 0000 0000 0000 0000 0000 0000 0000

01:18:05: TXCONN-APPC-621E5730:  0000 0000 0000 0000 0000 0000 0000 0000

01:18:05: TXCONN-APPC-621E5730:  00E2 E3C1 D9E6 4BE2 E3C5 D3D3 C140 4040

01:18:05: TXCONN-APPC-621E5730:  4040 0000 0000 0000 0000 0000

Related Commands

Command	Description
debug snasw	Displays debugging information related to SNA Switching Services.
debug txconn all	Displays all CTRC debugging information related to communications with CICS.
debug txconn config	Displays trace or error messages for CTRC configuration and control blocks for CICS communications.
debug txconn data	Displays CICS client and host data being handled by CTRC, in hexadecimal notation.
debug txconn event	Displays trace or error messages for CTRC events related to CICS communications.
debug txconn tcp	Displays error messages or traces for TCP/IP communications with CICS.
debug txconn timer	Displays performance information related to CICS communications.
show debugging	Displays the state of each debugging option.

debug txconn config

To display trace or error messages for CTRC configuration and control blocks for CICS communications, use the debug txconn config command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug txconn config

no debug txconn config

Syntax Description

This command has no arguments or keywords.

Defaults

By default, debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.

Examples

The following example shows output for the debug txconn config command:

Router# debug txconn config

22:11:37: TXCONN-CONFIG: deleting transaction 61FCE414

22:11:37: TXCONN-CONFIG: deleting connection 61FB5CB0

22:11:37: TXCONN-CONFIG: server 62105D6C releases connection 61FB5CB0

22:11:44: TXCONN-CONFIG: new connection 61FB64A0

22:11:44: TXCONN-CONFIG: server 6210CEB4 takes connection 61FB64A0

22:11:44: TXCONN-CONFIG: new transaction 61E44B9C

22:11:48: TXCONN-CONFIG: deleting transaction 61E44B9C

22:11:53: TXCONN-CONFIG: new transaction 61E44B9C

22:11:54: TXCONN-CONFIG: deleting transaction 61E44B9C

Related Commands

Command	Description
debug snasw	Displays debugging information related to SNA Switching Services.
debug txconn all	Displays all CTRC debugging information related to communications with CICS.
debug txconn appc	Displays APPC-related trace or error messages for communications with CICS.
debug txconn data	Displays CICS client and host data being handled by CTRC, in hexadecimal notation.
debug txconn event	Displays trace or error messages for CTRC events related to CICS communications.
debug txconn tcp	Displays error messages or traces for TCP/IP communications with CICS.
debug txconn timer	Displays performance information related to CICS communications.
show debugging	Displays the state of each debugging option.

debug txconn data

To display a hexadecimal dump of CICS client and host data being handled by CTRC, plus information about certain CTRC internal operations, use the debug txconn data command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug txconn data

no debug txconn data

Syntax Description

This command has no arguments or keywords.

Defaults

By default, debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.

Examples

The following example shows selected output from the debug txconn data command when a connection is established, data is received from the client via TCP/IP, data is sent to the client, and then the connection is closed.

Router# debug txconn data

TXConn DATA debugging is on

00:04:50: TXConn(62197464) Created

00:04:50: TXConn(62197464) State(0) MsgID(0) -> nextState(1)

00:04:50: TXConn(62197464) Client->0000 003A 0000 0002 000B 90A0

00:04:50: TXConn(62197464) Received LL 58 for session(0 0 2).

00:06:27: TXConn(62197464) Client<-0000 0036 0000 0003 000B 8001 0707 0864

00:06:53: TXConn(62175024) Deleted

The following lines show output when data is sent to the host:

00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) LL(58) FMH5(0) CEBI(0)

00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) State(0) MsgID(7844) -> nextState(1)

00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) conversationType(mapped) syncLevel(1) 
sec(0)

00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) TPName CCIN

00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) apDataLength(32) GDSID(12FF)

00:04:50: TXTrans(id:62197910 conn:62197464 addr:2) ->Host 0000 0008 03F4 F3F7 0000 0008 
0401 0000

The following lines show output when data is received from the host:

00:05:01: TXTrans(id:62197910 conn:62197464 addr:2) <-Host  0092 12FF 0000 000C 0102 0000 
0000 0002

The following lines show CTRC generating an FMH7 error message indicating that a CICS transaction has failed at the host or has been cleared by a router administrator:

00:06:27: TXTrans(id:6219853C conn:62197464 addr:3) Generating FMH7.

00:06:27: %TXCONN-3-TXEXCEPTION: Error occurred from transaction 3 of client 
157.151.241.10 connected to server CICSC, exception type is 9

The following line shows CTRC responding to an FMH7 error message sent by the CICS client program:

00:07:11: TXTrans(id:62197910 conn:62197464 addr:2) Generating FMH7 +RSP.

Related Commands

Command	Description
debug snasw	Displays debugging information related to SNA Switching Services.
debug txconn all	Displays all CTRC debugging information related to communications with CICS.
debug txconn appc	Displays APPC-related trace or error messages for communications with CICS.
debug txconn config	Displays trace or error messages for CTRC configuration and control blocks for CICS communications.
debug txconn event	Displays trace or error messages for CTRC events related to CICS communications.
debug txconn tcp	Displays error messages or traces for TCP/IP communications with CICS.
debug txconn timer	Displays performance information related to CICS communications.
show debugging	Displays the state of each debugging option.

debug txconn event

To display trace or error messages for CTRC events related to CICS communications, use the debug txconn event command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug txconn event

no debug txconn event

Syntax Description

This command has no arguments or keywords.

Defaults

By default, debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.

Examples

The following example shows output for the debug txconn event command:

Router# debug txconn event

TXConn event debugging is on

Router#

22:15:08: TXCONN-EVENT: [*] Post to 62146464(cn), from 6211E744(tc), msg

61FC6170, msgid 0x6372 'cr', buffer 6211289C.

22:15:08: TXCONN-EVENT: Dispatch to 62146464, from 6211E744, msg 61FC6170,

msgid 6372 'cr', buffer 6211289C.

22:15:08: TXCONN-EVENT: [*] Post to 61E44BA0(sn), from 62146464(cn), msg

621164D0, msgid 0x7844 'xD', buffer 0.

22:15:08: TXCONN-EVENT: [*] Post to 6211E744(tc), from 62146464(cn), msg

61FC6170, msgid 0x6347 'cG', buffer 0.

22:15:08: TXCONN-EVENT: Dispatch to 61E44BA0, from 62146464, msg 621164D0,

msgid 7844 'xD', buffer 0.

22:15:08: TXCONN-EVENT: Dispatch to 6211E744, from 62146464, msg 61FC6170,

msgid 6347 'cG', buffer 0.

22:15:08: TXCONN-EVENT: [*] Post to 62146464(cn), from 6211E744(tc), msg

61FC6170, msgid 0x6372 'cr', buffer 6211289C.

22:15:08: TXCONN-EVENT: Dispatch to 62146464, from 6211E744, msg 61FC6170,

msgid 6372 'cr', buffer 6211289C.

22:15:08: TXCONN-EVENT: [*] Post to 61E44BA0(sn), from 62146464(cn), msg

61FBFBF4, msgid 0x7844 'xD', buffer 0.

22:15:08: TXCONN-EVENT: [*] Post to 6211E744(tc), from 62146464(cn), msg

61FC6170, msgid 0x6347 'cG', buffer 0.

22:15:08: TXCONN-EVENT: Dispatch to 61E44BA0, from 62146464, msg 61FBFBF4,

msgid 7844 'xD', buffer 0.

22:15:08: TXCONN-EVENT: [*] Post to 61FC6394(ap), from 61E44BA0(sn), msg

621164D0, msgid 0x634F 'cO', buffer 0.

22:15:08: TXCONN-EVENT: Dispatch to 6211E744, from 62146464, msg 61FC6170,

msgid 6347 'cG', buffer 0.

Related Commands

Command	Description
debug snasw	Displays debugging information related to SNA Switching Services.
debug txconn all	Displays all CTRC debugging information related to communications with CICS.
debug txconn appc	Displays APPC-related trace or error messages for communications with CICS.
debug txconn config	Displays trace or error messages for CTRC configuration and control blocks for CICS communications.
debug txconn data	Displays CICS client and host data being handled by CTRC, in hexadecimal notation.
debug txconn tcp	Displays error messages or traces for TCP/IP communications with CICS.
debug txconn timer	Displays performance information related to CICS communications.
show debugging	Displays the state of each debugging option.

debug txconn tcp

To display error messages and traces for TCP, use the debug txconn tcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug txconn tcp

no debug txconn tcp

Syntax Description

This command has no arguments or keywords.

Defaults

By default, debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.

Examples

The following example displays output from the debug txconn tcp command:

Router# debug txconn tcp

TXCONN-TCP-63528473: tcpdriver_passive_open returned NULL

TXCONN-TCP-63528473: (no memory) tcp_reset(63829482) returns 4

TXCONN-TCP: tcp_accept(74625348,&error) returns tcb 63829482, error 4

TXCONN-TCP: (no memory) tcp_reset(63829482) returns 4

TXCONN-TCP-63528473: (open) tcp_create returns 63829482, error = 4

TXCONN-TCP-63528473: tcb_connect(63829482,1.2.3.4,2010) returns 4

TXCONN-TCP-63528473: (open error) tcp_reset(63829482) returns 4

TXCONN-TCP-63528473: tcp_create returns 63829482, error = 4

TXCONN-TCP-63528473: tcb_bind(63829482,0.0.0.0,2001) returns 4

TXCONN-TCP-63528473: tcp_listen(63829482,,) returns 4

TXCONN-TCP-63528473: (errors) Calling tcp_close (63829482)

Related Commands

Command	Description
debug ip	Displays debugging information related to TCP/IP communications.
debug snasw	Displays debugging information related to SNA Switching Services.
debug txconn all	Displays all CTRC debugging information related to communications with CICS.
debug txconn appc	Displays APPC-related trace or error messages for communications with CICS.
debug txconn config	Displays trace or error messages for CTRC configuration and control blocks for CICS communications.
debug txconn data	Displays CICS client and host data being handled by CTRC, in hexadecimal notation.
debug txconn event	Displays trace or error messages for CTRC events related to CICS communications.
debug txconn timer	Displays performance information related to CICS communications.
show debugging	Displays the state of each debugging option.

debug txconn timer

To display performance information regarding CTRC communications with CICS, use the debug txconn timer command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug txconn timer

no debug txconn timer

Syntax Description

This command has no arguments or keywords.

Defaults

By default, debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.

Examples

The following example shows turnaround time and host response time in milliseconds for a CICS transaction requested through CTRC. Turnaround time is measured from when CTRC receives the first request packet for the transaction until CTRC sends the last response packet of the transaction to the client. Host response time is measured from when CTRC sends the last request packet for a transaction to the host until CTRC receives the first response packet from the host for that transaction.

Router# debug txconn timer

TXConn timer debugging is on

00:04:14: TXTrans(id:622F4350 conn:62175024 addr:1) Turnaround Time = 4536(msec) 
HostResponseTime = 120(msec)

Related Commands

Command	Description
debug snasw	Displays debugging information related to SNA Switching Services.
debug txconn all	Displays all CTRC debugging information related to communications with CICS.
debug txconn appc	Displays APPC-related trace or error messages for communications with CICS.
debug txconn config	Displays trace or error messages for CTRC configuration and control blocks for CICS communications.
debug txconn data	Displays CICS client and host data being handled by CTRC, in hexadecimal notation.
debug txconn event	Displays trace or error messages for CTRC events related to CICS communications.
debug txconn tcp	Displays error messages or traces for TCP/IP communications with CICS.
show debugging	Displays the state of each debugging option.

debug udptn

To display debug messages for UDPTN events, use the debug udptn command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug udptn

no debug udptn

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)T	This command was introduced.

Examples

The following is sample output from the debug udptn command:

terrapin# debug udptn

terrapin# udptn 172.16.1.1

Trying 172.16.1.1 ... Open

*Mar 1 00:10:15.191:udptn0:adding multicast group.

*Mar 1 00:10:15.195:udptn0:open to 172.16.1.1:57 Loopback0jjaassdd

*Mar 1 00:10:18.083:udptn0:output packet w 1 bytes

*Mar 1 00:10:18.087:udptn0:Input packet w 1 bytes

terrapin# disconnect

Closing connection to 172.16.1.1 [confirm] y

terrapin#

*Mar 1 00:11:03.139:udptn0:removing multicast group.

Related Commands

Command	Description
udptn	Enables transmission or reception of UDP packets.
transport output	Defines the protocol that can be used for outgoing connections from a line.

debug v120 event

To display information on V.120 activity, use the debug v120 event command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug v120 event

no debug v120 event

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

V.120 is an ITU specification that allows for reliable transport of synchronous, asynchronous, or bit transparent data over ISDN bearer channels.

For complete information on the V.120 process, use the debug v120 packet command along with the debug v120 event command. V.120 events are activity events rather than error conditions.

Examples

The following is sample output from the debug v120 event command of V.120 starting up and stopping. Also included is the interface that V.120 is running on (BR 0) and where the V.120 configuration parameters are obtained from (default).

Router# debug v120 event

0:01:47: BR0:1-v120 started - Setting default V.120 parameters

0:02:00: BR0:1:removing v120

Related Commands

Command	Description
debug v120 packet	Displays general information on all incoming and outgoing V.120 packets.

debug v120 packet

To display general information on all incoming and outgoing V.120 packets, use the debug v120 packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug v120 packet

no debug v120 packet

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

The debug v120 packet command shows every packet on the V.120 session. You can use this information to determine whether incompatibilities exist between Cisco's V.120 implementation and other vendors' V.120 implementations.

V.120 is an ITU specification that allows for reliable transport of synchronous, asynchronous, or bit transparent data over ISDN bearer channels.

For complete information on the V.120 process, use the debug v120 events command along with the debug v120 packet command.

Examples

The following is sample output from the debug v120 packet command for a typical session startup:

Router# debug v120 packet

0:03:27: BR0:1: I SABME:lli 256 C/R 0 P/F=1

0:03:27: BR0:1: O UA:lli 256 C/R 1 P/F=1

0:03:27: BR0:1: O IFRAME:lli 256 C/R 0 N(R)=0 N(S)=0 P/F=0 len 43

0x83 0xD 0xA 0xD 0xA 0x55 0x73 0x65 

0x72 0x20 0x41 0x63 0x63 0x65 0x73 0x73 

0:03:27: BR0:1: I RR:lli 256 C/R 1 N(R)=1 P/F=0

0:03:28: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=0 P/F=0 len 2

0x83 0x63 

0:03:28: BR0:1: O RR:lli 256 C/R 1 N(R)=1 P/F=0

0:03:29: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=1 P/F=0 len 2

0x83 0x31 

0:03:29: BR0:1: O RR:lli 256 C/R 1 N(R)=2 P/F=0

%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to up

0:03:31: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=2 P/F=0 len 2

0x83 0x55 

0:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=3 P/F=0 len 3

0x83 0x31 0x6F 

0:03:32: BR0:1: O RR:lli 256 C/R 1 N(R)=3 P/F=0

0:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=4 P/F=0 len 2

0x83 0x73 

0:03:32: BR0:1: O RR:lli 256 C/R 1 N(R)=5 P/F=0

0:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=5 P/F=0 len 2

0x83 0xA 

0:03:32: BR0:1: O IFRAME:lli 256 C/R 0 N(R)=6 N(S)=1 P/F=0 len 9

0x83 0xD 0xA 0x68 0x65 0x66 0x65 0x72 0x3E 

Table 275 describes the significant fields in the display.

Table 275 debug v.120 packet Field Descriptions 

Field	Descriptions
BR0:1	Interface number associated with this debugging information.
I/O	Packet going into or out of the interface.
SABME, UA, IFRAME, RR	V.120 packet type. In this case: •SABME—Set asynchronous balanced mode, extended •US—Unnumbered acknowledgment •IFRAME—Information frame •RR—Receive ready
lli 256	Logical link identifier number.
C/R 0	Command or response.
P/F=1	Poll final.
N(R)=0	Number received.
N(S)=0	Number sent.
len 43	Number of data bytes in the packet.
0x83	Up to 16 bytes of data.

Related Commands

Command	Description
debug tarp events	Displays information on TARP activity.

debug vg-anylan

To monitor error information and 100VG connection activity, use the debug vg-anylan command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug vg-anylan

no debug vg-anylan

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Usage Guidelines

This command could create a substantial amount of command output.

Examples

The following is sample output from the debug vg-anylan command:

Router# debug vg-anylan

%HP100VG-5-LOSTCARR: HP100VG(2/0), lost carrier

Table 276 lists the possible messages that could be generated by this command.

Table 276 debug vg-anylan Message Descriptions 

Message	Description	Action
%HP100VG-5-LOSTCARR: HP100VG(2/0), lost carrier	Lost carrier debug message. The VG controller detects that the link to the hub is down due to cable, hub, or VG controller problem.	Check, repair, or replace the cable or hub. If you determine that the cable and hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.
%HP100VG-5-CABLEERR: HP100VG(2/0), cable error, training failed	Bad cable error messages. Cable did not pass training.1	Check, repair, or replace the cable or hub. If you determine that the cable and hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.
%HP100VG-5-NOCABLE: HP100VG(2/0), no tone detected, check cable, hub	No cable attached error message. The VG MAC cannot hear tones from the hub.1	Check, repair, or replace the cable or hub. If you determine that the cable and hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.
HP100VG-1-FAIL: HP100VG(2/0), Training Fail - unable to login to the hub	Training to the VG network failed. Login to the hub rejected by the hub.1	Take action based on the following error messages: •%HP100VG-1-DUPMAC: HP100VG(2/0), A duplicate MAC address has been detected •HP100VG-1-LANCNF: HP100VG(2/0), Configuration is not compatible with the network •%HP100VG-1-ACCESS: HP100VG(2/0), Access to network is not allowed
%HP100VG-1-DUPMAC: HP100VG(2/0), A duplicate MAC address has been detected	Duplicate MAC address on the same VG network. Two VG devices on the same LAN segment have the same MAC address.	Check the router configuration to make sure that no duplicate MAC address is configured.
%HP100VG-1-LANCNF: HP100VG(2/0), Configuration is not compatible with the network	Configuration of the router is not compatible to the network.	Check that the configuration of the hub for Frame Format, Promiscuous, and Repeater bit indicates the proper configuration.
%HP100VG-1-ACCESS: HP100VG(2/0), Access to network is not allowed	Access to the VG network is denied by the hub.	Check the configuration of the hub.
%HP100VG-3-NOTHP100VG: Device reported 0x5101A	Could not find the 100VG PCI device on a 100VG-AnyLAN port adapter.	Make sure the 100VG-AnyLAN port adapter is properly seated in the slot. Otherwise repair or replace the 100VG-AnyLAN port adapter.
%HP100VG-1-DISCOVER: Only found 0 interfaces on bay 2, shutting down bay	No 100VG interface detected on a 100VG-AnyLAN port adapter in a slot.	Make sure the 100VG-AnyLAN port adapter is properly seated in the slot. Otherwise repair or replace the 100VG-AnyLAN port adapter.

1 This message might display when the total load on the cascaded hub is high. Wait at least 20 seconds before checking to determine if the training really failed. Check if the protocol is up after 20 seconds before starting troubleshooting.

debug video vicm

To display debug messages for the Video Call Manager (ViCM) that handles video calls, enter the
debug video vicm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug video vicm

no debug video vicm

Syntax Description

This command has no arguments or keywords.

Defaults

Debugging for the ViCM is not enabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XK	This command was introduced.
12.0(6)T	This command was modified.

Examples

The following example shows output when you use the debug video vicm command. Comments are enclosed in asterisks (*).

Router# debug video vicm

Video ViCM FSM debugging is on

***** Starting Video call *****

Router# SVC HANDLE in rcvd:0x80001B:

00:42:55:ViCM - current state = Idle, Codec Ready

00:42:55:ViCM - current event = SVC Setup

00:42:55:ViCM - new state = Call Connected

00:42:55:ViCM - current state = Call Connected

00:42:55:ViCM - current event = SVC Connect Ack

00:42:55:ViCM - new state = Call Connected

*****Video Call Disconnecting*****

Router#

00:43:54:ViCM - current state = Call Connected

00:43:54:ViCM - current event = SVC Release

00:43:54:ViCM - new state = Remote Hangup

00:43:54:ViCM - current state = Remote Hangup

00:43:54:ViCM - current event = SVC Release Complete

00:43:54:ViCM - new state = Remote Hangup

mc3810_video_lw_periodic:Codec is not ready

mc3810_video_lw_periodic:sending message

00:43:55:ViCM - current state = Remote Hangup

00:43:55:ViCM - current event = DTR Deasserted

00:43:55:ViCM - new state = Idle

mc3810_video_lw_periodic:Codec is ready

mc3810_video_lw_periodic:sending message

00:43:55:ViCM - current state = Idle

00:43:55:ViCM - current event = DTR Asserted

00:43:55:ViCM - new state = Idle, Codec Ready