Table Of Contents

debug tag-template event

debug tarp events

debug tarp packets

debug tbridge virtual-port

debug tcam_mgr

debug tccs signaling

debug tdm

debug telco-return msg

debug telnet

debug text-to-fax

debug tftp

debug tgrep error

debug tgrep events

debug tgrep fsm

debug tgrep io

debug tgrep messages

debug tgrep msgdump

debug tgrep timer-event

debug tgrep timers

debug tgrep tripr

debug tgrm

debug tidp

debug tiff reader

debug tiff writer

debug time-range ipc

debug tms consumer

debug tms controller

debug token ring

debug topology

debug track

debug tsp

debug tunnel rbscp

debug tunnel route-via

debug txconn all

debug txconn appc

debug txconn config

debug txconn data

debug txconn event

debug txconn tcp

debug txconn timer

debug udptn

debug usb driver

debug user-group

debug v120 event

debug v120 packet

debug vg-anylan

debug video vicm

debug vlan packet

debug voice aaa asnl

debug voice all

debug voice cp

debug voice dsp crash-dump

debug voice eecm

debug voice enum

debug voice fastpath

debug voice h221

debug voice h324

debug voice mlpp

debug voice protocol

debug voice register errors

debug voice register events

debug voice signaling

debug voice source-group

debug voice statistics

debug voice tdsm

debug voice translation

debug voice uri

debug voice vofr

debug voip aaa

debug voip ais

debug voip application

debug voip application stcapp all

debug voip application stcapp buffer-history

debug voip application stcapp error

debug voip application stcapp events

debug voip application stcapp functions

debug voip application stcapp port

debug voip application vxml

debug tag-template event

To display the tag application on a session (an Authentication Proxy or Extensible Authentication Protocol [EAP] over UDP session), use the debug tag-template event command in privileged EXEC mode. To disable debugging, use the no form of this command.

debug tag-template event

no debug tag-template event

Syntax Description

This command has no arguments or keywords.

Command Default

Debugging is turned off.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
12.4(6)T	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following example shows that the tag application on a session is to be displayed:

Router# debug tag-template event

Related Commands

Command	Description
show epm sessions ip	Displays whether tag policies have been applied.

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 network service access point (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 332 describes the significant fields shown in display.

Table 332 debug tarp events Field Descriptions—tarp resolve Command 

Field	Descriptions
Sending TARP type 1 PDU	Protocol data unit (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 Target Identifier Address Resolution Protocol (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 TARP target identifier (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 333 describes the significant fields shown in the display.

Table 333 debug tarp packets Field Descriptions—tarp query Command 

Field	Descriptions
Sending TARP type 5 PDU	Protocol data unit (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 tbridge virtual-port

To display Transparent Bridging Virtual Port events debug messages, use the debug tbridge virtual-port command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tbridge virtual-port

no debug tbridge virtual-port

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(2)T	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following is sample output from the debug tbridge virtual-port command:

Router# debug tbridge virtual-port

Transparent Bridging Virtual Port Events debugging is on

Router#

vBridge-Port: Received packet (vLAN 100) on FastEthernet0/0 matches with lw-vLAN range.

Set packet input interface to vBridgePort2/1.

Table 334 describes the significant fields shown in the display.

Table 334 debug tbridge virtual-port Field Descriptions 

Field	Description
vBridge-Port	Identifies the message as a Transparent Bridging Virtual Port debug message.
vLAN 100	The VLAN ID of the packet.
vBridgePort2/1	The interface the packet is to be bridged to.

debug tcam_mgr

To debug the ternary content addressable memory (TCAM) manager, use the debug tcam_mgr command in privileged EXEC configuration mode.

debug tcam_mgr {error | event | profile}

no debug tcam_mgr {error | event | profile}

Syntax Description

error	Enables debug messages related to TCAM manager errors.
event	Enables debug messages for TCAM manager events.
profile	Enables debug messages about the amount of time it takes to add and remove entries from the TCAM regions.

Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0 S	This command was introduced.
12.2(20)S2	This command was integrated into Cisco IOS Release 12.2(20)S2.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

The debug tcam_mgr command is intended for use by Cisco Systems technical support personnel.

---

Caution Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco Systems technical support personnel. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

---

Examples

The following example enables TCAM manager event debug messages. It shows the messages associated with shutting down and restarting an interface on the the 4-Port 10/100 Fast Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 4 of the Cisco 7304 router:

Router# debug tcam_mgr event

TCAM Manager Events debugging is on

Router# conf t

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# int fast 4/0/0

Router(config-if)# shut

Router(config-if)# 

4d01h: %LINK-5-CHANGED: Interface FastEthernet4/0/0, changed state to administratively 
down

4d01h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/0/0, changed state to 
down

Router(config-if)# 

Router(config-if)# no shut

Router(config-if)# 

4d01h: Freeing VC at 0 from mask at 0

4d01h: Freeing VC at 1 from mask at 0

4d01h: Freeing VC at 0 from mask at 8

4d01h:  Found Mbu at offset 0 index 0

4d01h: Allocated mbu at offset 0 index 0, vc_index 0 region 0

4d01h:  Found Mbu at offset 0 index 0

4d01h: Allocated mbu at offset 0 index 0, vc_index 1 region 0

4d01h:  Found Mbu at offset 0 index 1

4d01h: Allocated mbu at offset 0 index 1, vc_index 0 region 0

4d01h: %LINK-3-UPDOWN: Interface FastEthernet4/0/0, changed state to up

4d01h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/0/0, changed state to 
up

debug tccs signaling

To see information about the transparent Common Channel Signaling (CCS) connection, use the debug tccs signaling command in privileged EXEC mode. 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

Privileged EXEC

Command History

Release	Modification
12.0(7)XK	This command was introduced.
12.1(2)T	This command was integrated into Release 12.1(2)T and Release 12.1(2)T.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

---

Caution 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 shows sample 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 multiplexing (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 debugging message whenever the TDM subsystem application programming interface (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 recover 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 debugging 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 debugging 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.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following is sample output from the debug cable telco-return msg command:

ubr7223# debug cable telco-return msg

CMTS telco-return msg debugging is on

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.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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 335 describes the significant fields shown in the display.

Table 335 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 show information relating to the off-ramp text-to-fax conversion, use the debug text-to-fax command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug text-to-fax

no debug text-to-fax

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(4)T	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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 336 describes the significant fields in the first line of output.

Table 336 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 tgrep error

To turn on debugging for any Telephony Gateway Registration Protocol (TGREP) errors, use the debug tgrep error command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tgrep error

no debug tgrep error

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

The "We already have connection with such itad/tripid combo in progress" message appears when an error occurs where two location servers with the same Internet Telephony Administrative Domain (ITAD), and TripID initiate a Telephony Routing over IP (TRIP) connection to the gateway. When the second OPEN message arrives at the gateway, the debug trip error command displays the message.

Examples

The following shows sample output from the debug tgrep error command:

Errors : Process socket event has an invalid fd to work on

Errors : Process socket event has an invalid fd to work on

Errors : Process socket event has an invalid fd to work on

Errors : Process socket event has an invalid fd to work on

After the errors are reported, the open dump begins. The ITAD is identified in the dump.

------------------------ OPEN DUMP BEGINS ------------------------

 0x1 0xFFFFFFFF 0x0 0xFFFFFFB4 0x0

 0x0 0x4 0x58 0x6 0x7

 0xFFFFFF98 0xFFFFFFA9 0x0 0xC 0x0

 0x1 0x0 0x8 0x0 0x2

 0x0 0x4 0x0 0x0 0x0

 0x3

        Version    :1

        Hold Time    :180

        My ITAD      :1112

        TRIP ID      :101161129

                 Option Paramater #1

                 Param Type: Capability

                 Length 8

                         Cap Code :Send Receive Capability

                         Cap Len  :4

                                Send Rec Cap: RCV ONLY MODE

        -->All route types supported

------------------------ OPEN DUMP ENDS ------------------------

The "We already have connection with such itad/tripid combo in progress" message appears when an error occurs where two location servers with the same ITAD and TripID initiate a TRIP connection to the gateway.

We already have connection with such itad/tripid combo in progress

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Errors : Process socket event has an invalid fd to work on

Error: Active connection to the nbr failed NBR:16.1.1.203

Errors : Process socket event has an invalid fd to work on

Errors : Process socket event has an invalid fd to work on

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Errors : Process socket event has an invalid fd to work on

Errors : Process socket event has an invalid fd to work on

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Errors : Process socket event has an invalid fd to work on

Related Commands

Command	Description
debug tgrep events	Turns on debugging for main events occurring throughout the subsystem.
debug tgrep fsm	Turns on debugging for FSM activity.
debug tgrep io	Turns on debugging for detailed socket level activities.
debug tgrep messages	Turns on debugging for the movement of TGREP messages.
debug tgrep msgdump	Turns on debugging for the dump of the details of TGREP messages.
debug tgrep timer-event	Turns on debugging for events that are related to the timer.
debug tgrep timers	Turns on debugging for timer activity.
debug tgrep tripr	Turns on debugging for the TRIP Reporter.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrep events

To turn on debugging for main events occurring throughout the subsystem, use the debug tgrep events command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tgrep events

no debug tgrep events

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

Examples

The following example shows output from the debug tgrep events command:

tgrep-gw-1-02#Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Table 337 describes the significant fields shown in the display.

Table 337 debug tgrep events Field Descriptions

Field	Description
Received a TGREP_UPD_TIMER timeout	This event shows that a TGREP update timer timeout event occurred.
The bulkSyncQ size is 0 at this time	This event indicates the size of bulk sync queue.
The tgrepQ size is 0 at this time	This event indicates the size of TGREP queue.

Related Commands

Command	Description
debug tgrep error	Turns on debugging for any errors in functioning.
debug tgrep fsm	Turns on debugging for FSM activity.
debug tgrep io	Turns on debugging for detailed socket level activities.
debug tgrep messages	Turns on debugging for the movement of TGREP messages.
debug tgrep msgdump	Turns on debugging for the dump of the details of TGREP messages.
debug tgrep timer-event	Turns on debugging for events that are related to the timer.
debug tgreptimers	Turns on debugging for timer activity.
debug tgrep tripr	Turns on debugging for the TRIP Reporter.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrep fsm

To turn on debugging for Finite State Machine (FSM) events, use the debug tgrep fsm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tgrep fsm

no debug tgrep fsm

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

Examples

The following shows sample output from the debug tgrep fsm command:

Generic routes combined : 0x61FA38B4, 13 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x2 0x0 0x9 0x0

 0x5 0x0 0x0 0x0 0x3

 0x6D 0x63 0x69

-----------------------------------

+++++++++++++++++++++++++++++++++++++

 NEXT HOP SERVER : 0x61FA38C1, 10 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x3 0x0 0x6 0x0

 0x0 0x4 0xFFFFFFD2 0x0 0x0

-----------------------------------

+++++++++++++++++++++++++++++++++++++

 AD RD PATH : 0x61FA38CB, 10 bytes

++++++++++++++++++++Getting a major event 4 on I/O

Here, a write event occurs. Note how the finite state machine details each step of the writing process.

Received a TRIP_IO_WRITEQ_BOOLEAN event 313

The peer connection check for fd 1 is success

Writing some pending stuff first NBR:14.1.1.210

Moving ahead with more reading rc = 4

-->Starting regular write for nbr NBR:14.1.1.210

The queuesize before we start is 1

Selected primary socket for NBR:14.1.1.210

The peer connection check for fd 1 is success

Dequeued 1 message (left 0) for NBR:14.1.1.210 for writing to socket

A socket has gulped all that we fed it NBR:14.1.1.210 -- 92 bytes

Dequeued 0 message (left 0) for NBR:14.1.1.210 for writing to socket

Wrote out the whole socket buffer or Q in 2 attempts NBR:14.1.1.210 rc 4 was

NBR:14.1.1.210 Starting keepalive timer after writing something

Getting a major event 512 on I/O

Received an event on a socket for some nbr

Received Mask event of 0x1 for fd 1

Looking for fd match on nbr NBR:14.1.1.210

Now a read event occurs. After this event, the total number of TRIP messages read is displayed.

Recieved READ_EVENT for nbr NBR:14.1.1.210

Read 3 bytes from that network for nbr NBR:14.1.1.210

+++++++++++++++++++++++++++++++++++++

 This is what we READ : 0x63E79090, 3 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x3 0x4

-----------------------------------

NBR:14.1.1.210 Re-starting hold timer after a message is read

tmsg malloc total memory allocated is 95

Allocated another buffer for TRIP message

TRIP Messages Read so far 1

+++++++++++++++++++++++++++++++++++++

 Enqueing this tmsg : 0x691D09DC, 3 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x3 0x4

-----------------------------------

Enqueuing a message into the ReadQ of nbr: NBR:14.1.1.210

Read -1 bytes from that network for nbr NBR++++++++++++++++++

 0x0 0x4 0x0 0x6 0x2

 0x1 0x0 0x0 0x4 0xFFFFFFD2

-----------------------------------

Statistics for available circuits, total circuits, and call success rate are displayed.

+++++++++++++++++++++++++++++++++++++

 AD RD PATH : 0x61FA38D5, 10 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x5 0x0 0x6 0x2

 0x1 0x0 0x0 0x4 0xFFFFFFD2

-----------------------------------

+++++++++++++++++++++++++++++++++++++

 LOCAL PREF : 0x61FA38DF, 8 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x7 0x0 0x4 0x0

 0x0 0x0 0x5

-----------------------------------

+++++++++++++++++++++++++++++++++++++

 Available Ckts : 0x61FA38E7, 8 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0xF 0x0 0x4 0x0

 0x0 0x0 0x17

-----------------------------------

+++++++++++++++++++++++++++++++++++++

 TOTAL CIRCUITS : 0x61FA38EF, 8 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x10 0x0 0x4 0x0

 0x0 0x0 0x17

-----------------------------------

+++++++++++++++++++++++++++++++++++++

 CALL SUCCESS RATE : 0x61FA38F7, 12 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x11 0x0

tgrep-gw-1-02#

tgrep-gw-1-02#und al:14.1.1.210

Getting a major event 512 on I/O

Errors : Process socket event has an invalid fd to work on

l 0x8 0x0

 0x0 0x0 0x78 0x0 0x0

 0x0 0x7F

-----------------------------------

+++++++++++++++++++++++++++++++++++++

 PREFIX_ATTRIBUTE : 0x61FA3903, 64 bytes

++++++++++++++++++++++++++++++++++++++

The prefix is shown here in hex format.

 0x0 0x12 0x0 0x3C 0x0

 0x4 0x31 0x31 0x32 0x38

 0x0 0x4 0x31 0x31 0x32

 0x37 0x0 0x4 0x31 0x31

 0x32 0x36 0x0 0x4 0x31

 0x31 0x32 0x35 0x0 0x4

 0x31 0x31 0x32 0x34 0x0

 0x4 0x31 0x31 0x32 0x33

 0x0 0x4 0x31 0x31 0x32

 0x32 0x0 0x5 0x39 0x39

 0x39 0x39 0x39 0x0 0x9

 0x31 0x32 0x33 0x34 0x35

 0x36

Related Commands

Command	Description
debug tgrep error	Turns on debugging for any errors in functioning.
debug tgrep events	Turns on debugging for main events occurring throughout the subsystem.
debug tgrep io	Turns on debugging for detailed socket level activities.
debug tgrep messages	Turns on debugging for the movement of TGREP messages.
debug tgrep msgdump	Turns on debugging for the dump of the details of TGREP messages.
debug tgrep timer-event	Turns on debugging for events that are related to the timer.
debug tgrep timers	Turns on debugging for timer activity.
debug tgrep tripr	Turns on debugging for the TRIP Reporter.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrep io

To turn on debugging for detailed socket-level activities, use the debug tgrep io command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tgrep io

no debug tgrep io

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

Examples

The following shows sample output from the debug tgrep io command:

Dispatching a TRIP_EV_NBR_IO_ASYNC_RESET to I/O for NBR:16.1.1.202

Dispatching a TRIP_EV_NBR_IO_ASYNC_RESET to I/O for NBR:16.1.1.203

A socket has gulped all that we fed it NBR:16.1.1.202 -- 5 bytes

Closing all the fds for NBR:16.1.1.202

NBR:16.1.1.202 is not eligible to write, no non(-1) fd yet

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

A Socket error has caused a write failure NBR:16.1.1.203 errno 13

Closing all the fds for NBR:16.1.1.203

NBR:16.1.1.202 is not eligible to write, no non(-1) fd yet

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

At this point, the connection is initiated.

Going to initiate a connect to 16.1.1.202

Called a socket_connect with errno 11, confirmation later 

Initiated a Async connect call for nbr NBR:16.1.1.202 fd 1

Received Mask event of 0x1 for fd 1

Recieved WRITE_EVENT for nbr NBR:16.1.1.202

Only Active Open Succeeded

Post connect succeeded for the nbr NBR:16.1.1.202, fd 1

A socket has gulped all that we fed it NBR:16.1.1.202 -- 29 bytes

Wrote out the whole socket buffer or Q in 2 attempts NBR:16.1.1.202 rc 4 was

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Received Mask event of 0x1 for fd 1

Recieved READ_EVENT for nbr NBR:16.1.1.202

Read -1 bytes from that network for nbr NBR:16.1.1.202

Received Mask event of 0x1 for fd 1

Recieved READ_EVENT for nbr NBR:16.1.1.202

Read 3 bytes from that network for nbr NBR:16.1.1.202

Read -1 bytes from that network for nbr NBR:16.1.1.202

Errors begin to appear here.

Errors : Process socket event has an invalid fd to work on

Received Mask event of 0x1 for fd 1

Recieved READ_EVENT for nbr NBR:16.1.1.202

Read 29 bytes from that network for nbr NBR:16.1.1.202

Read -1 bytes from that network for nbr NBR:16.1.1.202

Errors : Process socket event has an invalid fd to work on

After the errors are detected, a dump occurs. The Internet Telephony Administrative Domain (ITAD) and Telephony Routing over IP (TRIP) ID are displayed.

------------------------ OPEN DUMP BEGINS ------------------------

 0x1 0xFFFFFFFF 0x0 0xFFFFFFB4 0x0

 0x0 0x4 0x58 0x6 0x7

 0xFFFFFF98 0xFFFFFFA9 0x0 0xC 0x0

 0x1 0x0 0x8 0x0 0x2

 0x0 0x4 0x0 0x0 0x0

 0x3

        Version    :1

        Hold Time    :180

        My ITAD      :1112

        TRIP ID      :101161129

                 Option Paramater #1

                 Param Type: Capability

                 Length 8

                         Cap Code :Send Receive Capability

                         Cap Len  :4

                                Send Rec Cap: RCV ONLY MODE

        -->All route types supported

------------------------ OPEN DUMP ENDS ------------------------

Doing fd reassignment for nbr NBR:16.1.1.202

Moving ahead with more reading rc = 4

A socket has gulped all that we fed it NBR:16.1.1.202 -- 3 bytes

Wrote out the whole socket buffer or Q in 2 attempts NBR:16.1.1.202 rc 4 was

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Received Mask event of 0x1 for fd 1

Recieved READ_EVENT for nbr NBR:16.1.1.202

Read 3 bytes from that network for nbr NBR:16.1.1.202

Read -1 bytes from that network for nbr NBR:16.1.1.202

Moving ahead with more reading rc = 4

A socket has gulped all that we fed it NBR:16.1.1.202 -- 598 bytes

Wrote out the whole socket buffer or Q in 2 attempts NBR:16.1.1.202 rc 4 was

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Errors : Process socket event has an invalid fd to work on

Received Mask event of 0x1 for fd 1

Recieved READ_EVENT for nbr NBR:16.1.1.202

Read 3 bytes from that network for nbr NBR:16.1.1.202

Read -1 bytes from that network for nbr NBR:16.1.1.202

Errors : Process socket event has an invalid fd to work on

Received Mask event of 0x1 for fd 1

Recieved READ_EVENT for nbr NBR:16.1.1.202

Read 15 bytes from that network for nbr NBR:16.1.1.202

Read -1 bytes from that network for nbr NBR:16.1.1.202

Errors : Process socket event has an invalid fd to work on

Going to initiate a connect to 16.1.1.203

Called a socket_connect with errno 11, confirmation later 

Initiated a Async connect call for nbr NBR:16.1.1.203 fd 2

Received Mask event of 0x1 for fd 2

Recieved WRITE_EVENT for nbr NBR:16.1.1.203

The Active connect never succeeded, no passive yet, resetting NBR:16.1.1.203

Error: Active connection to the nbr failed NBR:16.1.1.203

A Socket error has caused a write failure NBR:16.1.1.203 errno 13

Closing all the fds for NBR:16.1.1.203

Post connect succeeded for the nbr NBR:16.1.1.203, fd -1

Moving ahead with more reading rc = 4

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Errors : Process socket event has an invalid fd to work on

Going to initiate a connect to 16.1.1.203

Called a socket_connect with errno 11, confirmation later 

Initiated a Async connect call for nbr NBR:16.1.1.203 fd 2

Received Mask event of 0x1 for fd 2

Errors continue to occur. Note that the router still attempts to write, but the connection is not active.

Recieved WRITE_EVENT for nbr NBR:16.1.1.203

The Active connect never succeeded, no passive yet, resetting NBR:16.1.1.203

Error: Active connection to the nbr failed NBR:16.1.1.203

A Socket error has caused a write failure NBR:16.1.1.203 errno 13

Closing all the fds for NBR:16.1.1.203

Post connect succeeded for the nbr NBR:16.1.1.203, fd -1

Moving ahead with more reading rc = 4

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Errors : Process socket event has an invalid fd to work on

Received Mask event of 0x1 for fd 1

Recieved READ_EVENT for nbr NBR:16.1.1.202

Read 3 bytes from that network for nbr NBR:16.1.1.202

Read -1 bytes from that network for nbr NBR:16.1.1.202

Errors : Process socket event has an invalid fd to work on

Going to initiate a connect to 16.1.1.203

Called a socket_connect with errno 11, confirmation later 

Initiated a Async connect call for nbr NBR:16.1.1.203 fd 2

Received Mask event of 0x1 for fd 2

Recieved WRITE_EVENT for nbr NBR:16.1.1.203

The Active connect never succeeded, no passive yet, resetting NBR:16.1.1.203

Error: Active connection to the nbr failed NBR:16.1.1.203

A Socket error has caused a write failure NBR:16.1.1.203 errno 13

Closing all the fds for NBR:16.1.1.203

Post connect succeeded for the nbr NBR:16.1.1.203, fd -1

Moving ahead with more reading rc = 4

NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

Errors : Process socket event has an invalid fd to work on

Related Commands

Command	Description
debug tgrep error	Turns on debugging for any errors in functioning.
debug tgrep events	Turns on debugging for main events occurring throughout the subsystem.
debug tgrep fsm	Turns on debugging for FSM activity.
debug tgrep messages	Turns on debugging for the movement of TGREP messages.
debug tgrep msgdump	Turns on debugging for the dump of the details of TGREP messages.
debug tgrep timer-event	Turns on debugging for events that are related to the timer.
debug tgrep timers	Turns on debugging for timer activity.
debug tgrep tripr	Turns on debugging for the TRIP Reporter.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrep messages

To turn on debugging for movement of Telephony Gateway Registration Protocol (TGREP) messages, use the debug tgrep messages command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tgrep messages

no debug tgrep messages

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

Examples

The following shows sample output from the debug tgrep messages command:

tgrep-gw(config-tgrep)#Received an OPEN NBR:14.1.1.210

------------------------ OPEN DUMP BEGINS ------------------------

 0x1 0x0 0x0 0xFFFFFFB4 0x0

 0x0 0x0 0x19 0x0 0x0

 0x45 0x67 0x0 0x0

        Version    :1

        Hold Time    :180

        My ITAD      :25

        TRIP ID      :17767

        No optional parameters -- hence all route types supported.

        Send-Recv capability in effect

------------------------ OPEN DUMP ENDS ------------------------

After the dump occurs, the TRGREP messages are displayed. In this case, keepalive messages are being received by this gateway.

Enqueued a Keepalive for NBR:14.1.1.210

Received an KEEPALIVE NBR:14.1.1.210

Received Keepalive for NBR:14.1.1.210

Received an KEEPALIVE NBR:14.1.1.210

Related Commands

Command	Description
debug tgrep error	Turns on debugging for any errors in functioning.
debug tgrep events	Turns on debugging for main events occurring throughout the subsystem.
debug tgrep fsm	Turns on debugging for FSM activity.
debug tgrep io	Turns on debugging for detailed socket level activities.
debug tgrep msgdump	Turns on debugging for the dump of the details of TGREP messages.
debug tgrep timer-event	Turns on debugging for events that are related to the timer.
debug tgrep timers	Turns on debugging for timer activity.
debug tgrep tripr	Turns on debugging for the TRIP Reporter.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrep msgdump

To turn on debugging for the dump of the details of Telephony Gateway Registration Protocol (TGREP) messages, use the debug tgrep msgdump command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tgrep msgdump

no debug tgrep msgdump

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

Examples

The following shows sample output from the debug tgrep msgdump command:

tgrep-gw-1-02#Received an KEEPALIVE NBR:14.1.1.210

+++++++++++++++++++++++++++++++++++++

 TMSG datagramstart : 0x69188648, 150 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0xFFFFFF96 0x2 0x0 0x1

 0x0 0x0 0x0 0x2 0x0

 0x9 0x0 0x5 0x0 0x0

 0x0 0x3 0x6D 0x63 0x69

 0x0 0x3 0x0 0x6 0x0

 0x0 0x4 0xFFFFFFD2 0x0 0x0

 0x0 0x4 0x0 0x6 0x2

 0x1 0x0 0x0 0x4 0xFFFFFFD2

 0x0 0x5 0x0 0x6 0x2

 0x1 0x0 0x0 0x4 0xFFFFFFD2

 0x0 0x7 0x0 0x4 0x0

 0x0 0x0 0x5 0x0 0xF

 0x0 0x4 0x0 0x0 0x0

 0x16 0x0 0x10 0x0 0x4

 0x0 0x0 0x0 0x17 0x0

 0x11 0x0 0x8 0x0 0x0

 0x0 0x74 0x0 0x0 0x0

 0x7B 0x0 0x12 0x0 0x3C

 0x0 0x4 0x31 0x31 0x32

 0x38 0x0 0x4 0x31 0x31

 0x32 0x37 0x0 0x4 0x31

 0x31 0x32 0x36 0x0 0x4

 0x31 0x31 0x32 0x35 0x0

 0x4 0x31 0x31 0x32 0x34

 0x0 0x4 0x31 0x31 0x32

 0x33 0x0 0x4 0x31 0x31

 0x32 0x32 0x0 0x5 0x39

 0x39 0x39 0x39 0x39 0x0

 0x9 0x31 0x32 0x33 0x34

 0x35 0x36 0x37 0x38 0x39

After each event occurs, a dump of the message appears. The entire dump of each keepalive is being displayed.

-----------------------------------

Received an KEEPALIVE NBR:14.1.1.210

+++++++++++++++++++++++++++++++++++++

 TMSG datagramstart : 0x691B0CA0, 92 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0x5C 0x2 0x0 0x1

 0x0 0x0 0x0 0x2 0x0

 0xF 0x0 0x3 0x0 0x0

 0x0 0x9 0x31 0x32 0x33

 0x34 0x35 0x36 0x37 0x38

 0x39 0x0 0x3 0x0 0x6

 0x0 0x0 0x4 0xFFFFFFD2 0x0

 0x0 0x0 0x4 0x0 0x6

 0x2 0x1 0x0 0x0 0x4

 0xFFFFFFD2 0x0 0x5 0x0 0x6

 0x2 0x1 0x0 0x0 0x4

 0xFFFFFFD2 0x0 0x7 0x0 0x4

 0x0 0x0 0x0 0x5 0x0

 0xF 0x0 0x4 0x0 0x0

 0x0 0x17 0x0 0x10 0x0

 0x4 0x0 0x0 0x0 0x17

 0x0 0x11 0x0 0x8 0x0

 0x0 0x0 0x75 0x0 0x0

 0x0 0x78

-----------------------------------

+++++++++++++++++++++++++++++++++++++

 TMSG datagramstart : 0x691885EC, 150 bytes

++++++++++++++++++++++++++++++++++++++

 0x0 0xFFFFFF96 0x2 0x0 0x1

 0x0 0x0 0x0 0x2 0x0

 0x9 0x0 0x5 0x0 0x0

 0x0 0x3 0x6D 0x63 0x69

 0x0 0x3 0x0 0x6 0x0

 0x0 0x4 0xFFFFFFD2 0x0 0x0

 0x0 0x4 0x0 0x6 0x2

 0x1 0x0 0x0 0x4 0xFFFFFFD2

 0x0 0x5 0x0 0x6 0x2

 0x1 0x0 0x0 0x4 0xFFFFFFD2

 0x0 0x7 0x0 0x4 0x0

 0x0 0x0 0x5 0x0 0xF

 0x0 0x4 0x0 0x0 0x0

 0x16 0x0 0x10 0x0 0x4

 0x0 0x0 0x0 0x17 0x0

 0x11 0x0 0x8 0x0 0x0

 0x0 0x75 0x0 0x0 0x0

 0x7C 0x0 0x12 0x0 0x3C

 0x0 0x4 0x31 0x31 0x32

 0x38 0x0 0x4 0x31 0x31

 0x32 0x37 0x0 0x4 0x31

 0x31 0x32 0x36 0x0 0x4

 0x31 0x31 0x32 0x35 0x0

 0x4 0x31 0x31 0x32 0x34

 0x0 0x4 0x31 0x31 0x32

 0x33 0x0 0x4 0x31 0x31

 0x32 0x32 0x0 0x5 0x39

 0x39 0x39 0x39 0x39 0x0

 0x9 0x31 0x32 0x33 0x34

 0x35 0x36 0x37 0x38 0x39

-----------------------------------

Received an KEEPALIVE NBR:14.1.1.210

Received an KEEPALIVE NBR:14.1.1.210

Related Commands

Command	Description
debug tgrep error	Turns on debugging for any errors in functioning.
debug tgrep events	Turns on debugging for main events occurring throughout the subsystem.
debug tgrep fsm	Turns on debugging for FSM activity.
debug tgrep io	Turns on debugging for detailed socket level activities.
debug tgrep messages	Turns on debugging for the movement of TGREP messages.
debug tgrep timer-event	Turns on debugging for events that are related to the timer.
debug tgrep timers	Turns on debugging for timer activity.
debug tgrep tripr	Turns on debugging for the TRIP Reporter.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrep timer-event

To turn on debugging for events that are related to the timer, use the debug tgrep timer-event command in privileged EXEC mode. To turn off debugging, use the no form of this command.

debug tgrep timer-event

no debug tgrep timer-event

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

Examples

The following shows sample output from the debug tgrep timer-event command:

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

The Telephony Routing over IP (TRIP) timer registers timeouts until the next event occurs. Here, the timers are reset.

Entering trip_reset_nbr_timers to reset timers

Starting the CONNECT timer for nbr NBR:16.1.1.202 for value of 30 seconds

Stopping hold timer and keepalive timer while resetting NBR:16.1.1.202

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Timeouts are again reported until the next event.

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Here, the TRIP neighbor is cleared, which causes the timer to reset.

Router#clear trip nei *

Router#Entering trip_reset_nbr_timers to reset timers

Starting the CONNECT timer for nbr NBR:16.1.1.202 for value of 30 seconds

Stopping hold timer and keepalive timer while resetting NBR:16.1.1.202

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 3 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

IO_CONNECT TIMER for nbr NBR:16.1.1.202 has expired

NBR:16.1.1.202 -Restarting the connect timer

NBR:16.1.1.202 starting the holder timer after post connect with large value

------------------------ OPEN DUMP BEGINS ------------------------

 0x1 0xFFFFFFFF 0x0 0xFFFFFFB4 0x0

 0x0 0x4 0x58 0x6 0x7

 0xFFFFFF98 0xFFFFFFA9 0x0 0xC 0x0

 0x1 0x0 0x8 0x0 0x2

 0x0 0x4 0x0 0x0 0x0

 0x3

        Version    :1

        Hold Time    :180

        My ITAD      :1112

        TRIP ID      :101161129

                 Option Paramater #1

                 Param Type: Capability

                 Length 8

                         Cap Code :Send Receive Capability

                         Cap Len  :4

                                Send Rec Cap: RCV ONLY MODE

        -->All route types supported

------------------------ OPEN DUMP ENDS ------------------------

NBR:16.1.1.202 Starting keepalive timer after writing something

NBR:16.1.1.202 Re-starting hold timer after a message is read

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPNBR:16.1.1.202 Starting keepalive timer after writing so

mething

NBR:16.1.1.202 Re-starting hold timer after a message is read

D timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIIO_CONNECT TIMER for nbr NBR:16.1.1.202 has expired

NBR:16.1.1.202 -Stopping the connect timer, no need anymore

MER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

NBR:16.1.1.202 Re-starting hold timer after a message is read

Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Related Commands

Command	Description
debug tgrep error	Turns on debugging for any errors in functioning.
debug tgrep events	Turns on debugging for main events occurring throughout the subsystem.
debug tgrep fsm	Turns on debugging for FSM activity.
debug tgrep io	Turns on debugging for detailed socket level activities.
debug tgrep messages	Turns on debugging for the movement of TGREP messages.
debug tgrep msgdump	Turns on debugging for the dump of the details of TGREP messages.
debug tgrep timers	Turns on debugging for timer activity.
debug tgrep tripr	Turns on debugging for the TRIP Reporter.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrep timers

To turn on debugging for detailed socket level activities, use the debug tgrep timers command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug tgrep timers

no debug tgrep timers

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

Examples

The following shows sample output from the debug tgrep timers command:

tgrep-gw-1-02#Received a TGREP_UPD_TIMER timeout

The bulkSyncQ size is 0 at this time

The tgrepQ size is 0 at this time

Restarting the router UPD timer after expiry

Table 338 describes the significant fields shown in the display.

Table 338 debug tgrep timers Field Descriptions

Field	Description
Received a TGREP_UPD_TIMER timeout	This indicates that a timeout was received.
The bulkSyncQ size is 0 at this time	This indicates the size of the bulk sync queue.
The tgrepQ size is 0 at this time	This indicates the size of the TGREP queue.
Restarting the router UPD timer after expiry	This indicates that the timer has been reset.

Related Commands

Command	Description
debug tgrep error	Turns on debugging for any errors in functioning.
debug tgrep events	Turns on debugging for main events occurring throughout the subsystem.
debug tgrep fsm	Turns on debugging for FSM activity.
debug tgrep io	Turns on debugging for detailed socket level activities.
debug tgrep messages	Turns on debugging for the movement of TGREP messages.
debug tgrep msgdump	Turns on debugging for the dump of the details of TGREP messages.
debug tgrep timer-event	Turns on debugging for events that are related to the timer.
debug tgrep tripr	Turns on debugging for the TRIP Reporter.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrep tripr

To turn on debugging from the Telephony Routing over IP (TRIP) Reporter (TRIPR), use the debug tgrep tripr command in privileged EXEC mode. To turn off debugging, use the no form of this command.

debug tgrep tripr

no debug tgrep tripr

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(1)	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

There is always a performance penalty when using debug commands.

A watched queue is used to inform the TRIPR process about changes in any of the interesting attributes of dial peer that potentially could trigger TRIP update. A dial peer attribute change manifests into a prefix attribute change and is deposited into the watched queue of TRIPR by the Event Dispatcher. The trunk group system also does the same.

Examples

The following shows sample output from the debug tgrep tripr command:

20:51:11: tripr_build_triprtr_prefix_destination_ev : got the ev id 1 reason 64 num_prefix 
1 advertise 0x2prefix 1128 addrFam 4 

20:51:11: tripr_build_triprtr_prefix_destination_ev ac 22 tc 23 ac_avg 22 

20:51:11: tripr_build_triprtr_prefix_destination_ev csr success 0 total 0 

20:51:11: 

20:51:11: --------------------------------

20:51:11: attrib 0x4002

20:51:11: ******* REACHABLE ROUTE ******

20:51:11: TRIP_AF_E164 1128

20:51:11:  ac: 22

20:51:11: 

20:51:11: =======================================

20:51:11: tripr_build_triprtr_prefix_destination_ev : got the ev id 1 reason 64 num_prefix 
1 advertise 0x27prefix 123456789 addrFam 4 

20:51:11: tripr_build_triprtr_prefix_destination_ev ac 22 tc 23 ac_avg 22 

20:51:11: tripr_build_triprtr_prefix_destination_ev csr success 117 total 120 

20:51:11:  tg mci cc mci

20:51:11: tripr_build_triprtr_prefix_destination_ev tg mci cic 0 carrier mci

20:51:11: 

20:51:11: --------------------------------

20:51:11: attrib 0x1C002

20:51:11: ******* REACHABLE ROUTE ******

20:51:11: TRIP_AF_E164 123456789

20:51:11:  csr: tot 120 succ 117

20:51:11:  ac: 22tc: 23

20:51:11: 

20:51:11: =======================================

20:51:11: tripr_build_triprtr_prefix_destination_ev : got the ev id 1 reason 64 num_prefix 
1 advertise 0x27prefix 99999 addrFam 4 

20:51:11: tripr_build_triprtr_prefix_destination_ev ac 22 tc 23 ac_avg 22 

20:51:11: tripr_build_triprtr_prefix_destination_ev csr success 0 total 0 

20:51:11:  tg mci cc mci

20:51:11: tripr_build_triprtr_prefix_destination_ev tg mci cic 0 carrier mci

20:51:11: 

20:51:11: --------------------------------

20:51:11: attrib 0x1C002

20:51:11: ******* REACHABLE ROUTE ******

20:51:11: TRIP_AF_E164 99999

20:51:11:  csr: tot 0 succ 0

20:51:11:  ac: 22tc: 23

20:51:11: 

20:51:11: =======================================

Table 339 describes the significant fields in the display.

Table 339 debug tgrep tripr Field Descriptions 

Field	Description
ev id	This field can contain the following entries: •1—Prefix regular event •2—Trunk group regular event •3—Carrier regular event •4—Prefix sync event •5—Trunk group sync event •6—Carrier sync event •7—Null sync event
reason: (for a prefix family event)	This field can contain the following entries: •1—Prefix down •2—Prefix up •4—Prefix trunk group attribute changed •8—Prefix available circuits changed •16—Prefix total circuits changed •32—Prefix CSR changed •64—Prefix AC interesting point •128—Prefix carrier attributes changed •256—Prefix stop advertise configured •512—Prefix start advertise configured
reason: (for a trunk group family event)	This field can contain the following entries: •1—Trunk group down •2—Trunk group up •4—Trunk group prefix attribute changed •8—Trunk group available circuits changed •16—Trunk group total circuits changed •32—Trunk group CSR changed •64—Trunk group AC interesting point •128—Trunk group stop advertise configured •256—Trunk group start advertise configured
reason: (for a carrier family event)	This field can contain the following entries: •1—Carrier down •2—Carrier up •4—Carrier prefix attribute changed •8—Carrier available circuits changed •16—Carrier total circuits changed •32—Carrier CSR changed •64—Carrier AC interesting point •128—Carrier stop advertise configured •256—Carrier start advertise configured

Related Commands

Command	Description
debug tgrep error	Turns on debugging for any errors in functioning.
debug tgrep events	Turns on debugging for main events occurring throughout the subsystem.
debug tgrep fsm	Turns on debugging for FSM activity.
debug tgrep io	Turns on debugging for detailed socket level activities.
debug tgrep messsages	Turns on debugging for the movement of TGREP messages.
debug tgrep msgdump	Turns on debugging for the dump of the details of TGREP messages.
debug tgrep timer-event	Turns on debugging for events that are related to the timer.
debug tgrep timers	Turns on debugging for timer activity.
debug voip eddri	Turns on debugging for the EDDRI.

debug tgrm

To display debugging 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 [all | default | detail | error [call [informational] | software [informational]] | function | inout | service]

no debug tgrm

Syntax Description

all	(Optional) Displays all TGRM debugging messages.
default	(Optional) Displays detail, error, and inout information. This option also runs if no keywords are added.
detail	(Optional) Displays non-inout information related to call processing, such as call updates or call acceptance checking.
error	(Optional) Displays TGRM error messages.
call	(Optional) Displays call processing errors.
informational	(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.
software	(Optional) Displays software errors.
function	(Optional) Displays TGRM functions.
inout	(Optional) Displays information from the functions that form the external interfaces of TGRM to other modules or subsystems.
service	(Optional) Displays TGRM services.

Defaults

Debugging is not enabled.

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 implemented on the Cisco AS5850 platform.
12.3(8)T	The all, default, detail, error, call, informational, software, function, inout, and service keywords were added to this command.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

Because the debug tgrm command causes a large amount of messages to be generated, router performance can be affected.

---

Caution The debug tgrm command can impact the performance of your router. This command should only be used during low traffic periods.

---

Examples

The following is sample output from the debug tgrm all command for an incoming CAS call on a trunk group that is rejected because of the max-calls command:

Router# debug tgrm all 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_accept_call: 

    Timeslot=11, CallType=Voice, CallDirection=Incoming, Slot=2, SubUnit=1, Port=1, 
DS0-Group=1

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_member_core: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_trunk_member: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_trunk_member: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_member_trunk_internal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_member_core: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_trunk_member: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_trunk_member: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_channel_active: 

    Trunk=2/1:1 (TG 211), Timeslot=11, CallType=Voice, 

    CallDirection=Incoming

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_channel_delete: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_channel_delete_queue: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_call_count_update: 

    CallDirection=Incoming, Increment call count

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_call_count_update_no_crm: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_call_count_update_no_crm: 

    CountType=TGRM_COUNT_VOICE, CallDirection=Incoming, Increment call count

    Updated values: CallCount=1, FreeTimeslots=23

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_call_count_update_crm: 

    CallType=Voice, CallDirection=Incoming, Increment the call count

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 

    TG 211 found

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info: 

    TG 211 found

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_status: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 

    TG 211 found

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_allow_call: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_allow_call: 

    TG 211; CallType=Voice CallDirection=Incoming

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_allow_call: 

    Call denied; CallType=Voice CallDirection=Incoming; MaxAllowed=0 Current=1

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_accept_call: 

    Call Rejected; Reason - Maximum voice calls exceeded

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 

    TG 211 found

03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info: 

    TG 211 found

Table 340 describes the significant fields shown in the display.

Table 340 debug tgrm all Field Descriptions 

Field	Description
//-1/xxxxxxxxxxxx/TGRM/ tgrm_accept_call:	The format of this message is //callid/GUID/module name/function name: •CallEntry ID is -1. This indicates that a call leg has not been identified. •GUID is xxxxxxxxxxxx. This indicates that the GUID information is unavailable. •TGRM is the module name. •The tgrm_accept_call field shows that the trunk group is accepting a call.
Timeslot=11, CallType=Voice, CallDirection=Incoming, Slot=2, SubUnit=1, Port=1, DS0-Group=1	Shows information about the call, including timeslot, call type and direction, and port information.
tgrm_trunk_channel_active: Trunk=2/1:1 (TG 211), Timeslot=11, CallType=Voice, CallDirection=Incoming	Shows information for the active trunk group, including the port, timeslot, and call type and direction.
tgrm_tg_call_count_update: CallDirection=Incoming, Increment call count	Indicates that the call counter for the trunk group has been incremented.
tgrm_tg_call_count_update_no_crm: CountType=TGRM_COUNT_VOICE, CallDirection=Incoming, Increment call count Updated values: CallCount=1, FreeTimeslots=23	Indicates that the call counter for the trunk group has been updated outside of the Carrier Resource Manager (CRM). This field contains more data than a call counter increment message that uses the CRM.
tgrm_allow_call: TG 211; CallType=Voice CallDirection=Incoming	Shows that a call was allowed on the 2/1:1 trunk.
tgrm_allow_call: Call denied; CallType=Voice CallDirection=Incoming; MaxAllowed=0 Current=1	Shows that a call on the trunk group was denied.
tgrm_accept_call: Call Rejected; Reason - Maximum voice calls exceeded	Shows that a call was rejected on this trunk group due to a maximum number of voice calls being received.

debug tidp

To configure a networking device to process and display Trusted Information Distribution Protocol (TIDP) debug messages, use the debug tidp command in privileged EXEC mode. To stop debug messages from being processed and displayed, use the no form of this command.

debug tidp {errors | events | packets | registration | test}

no debug tidp {errors | events | packets | registration | test}

Syntax Description

errors	Displays debug error messages.
events	Displays general events.
packets	Displays packet information.
registration	Displays registration information.
test	Enables the TIDP test CLI, which allows you to use the tidp test command.

Command Default

None.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
12.4(6)T	This command was introduced.
12.4(15)XZ	This command was integrated into Cisco IOS Release 12.4(15)XZ.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.4(20)T	This command was integrated into Cisco IOS Release 12.4(20)T.

Usage Guidelines

The test keyword is entered to enable the TIDP test CLI, which allows you to send test messages between TIDP peers. This command must be enabled on the sender and receiver.

The registration keyword is entered to enable debug messages related to TIDP peer registration. This command is useful for troubleshooting peer registration problems and authentication/encryption key mismatches.

The packets keyword is entered to enable debug messages related to general TIDP communication problems.

The errors keyword is entered to enable debug messages that display information about unexpected error conditions.

The events keyword is entered to enable debug messages that display information about general TIDP transactions and events.

Examples

The following example is sample output from the debug tidp command entered with the errors keyword:

Router# debug tidp errors

TIDP errors debugging is on 

Router# 

01:23:04: %TIDP-4-AUTHFAIL: Message from 10.1.1.3 failed authentication 

01:44:53: %TIDP-5-REGFAIL: Failed to register to peer 10.1.1.2, group 10 

Table 341 describes the significant fields shown in the display.

Table 341 debug tidp errors Field Descriptions 

Field	Description
TIDP errors debugging is on	TIDP error debugging has been enabled.
TIDP-4-AUTHFAIL: Message from 10.1.1.3 failed authentication	TIDP failed to authenticate a message from the 10.1.1.3 peer.
TIDP-5-REGFAIL: Failed to register to peer 10.1.1.2, group 10	TIDP failed to register the 10.1.1.2 peer in group 10.

The following example is sample output from the debug tidp command entered with the events keyword:

Router# debug tidp events

TIDP events debugging is on 

00:07:49: TIDP: New key set KEY_1 added 

00:10:16: TIDP: New authentication receive key added 

00:11:13: TIDP: New authentication send key added 

00:12:25: TIDP: New group added - 10 

00:13:31: TIDP: New peer 10.1.1.2 added to group 10 

00:14:46: TIDP: Registration interval changed from (min: 4294967295, max: 42949) 

00:15:38: TIDP: Source-ip changed from 0.0.0.0 to 10.1.1.1 

00:22:12: TIDP: TIDP enabled 

Table 342 describes the significant fields shown in the display.

Table 342 debug tidp events Field Descriptions 

Field	Description
TIDP events debugging is on	TIDP event debugging has been enabled.
TIDP: New key set RED added	Key-set RED has been configured.
TIDP: New authentication receive key added	A receive authentication key has been configured.
TIDP: New authentication send key added	A send authentication key has been configured.
TIDP: New group added - 10	TIDP group 10 was created.
TIDP: New peer 10.1.1.2 added to group 10	The 10.1.1.2 peer was added to group 10.
TIDP: Registration interval changed from (min: 4294967295, max: 42949)	The registration interval has been manually configured.
TIDP: Source-ip changed from 0.0.0.0 to 10.1.1.1	The TIDP source interface has been configured.
TIDP: TIDP enabled	TIDP has been enabled.

The following example is sample output from the debug tidp command entered with the packets keyword:

Router# debug tidp packets 

TIDP packets debugging is on

00:14:01: TIDP: tidp_build_conx connecting to 10.1.1.2, fd 1

00:14:01: TIDP: tidp_build_conx connecting to 10.1.1.4, fd 4

00:14:31: TIDP: tidp_complete_conx connect failed to 10.1.1.2, fd 1

00:14:31: TIDP: tidp_complete_conx connect failed to 10.1.1.4, fd 4

Table 343 describes the significant fields shown in the display.

Table 343 debug tidp packets Field Descriptions 

Field	Description
TIDP: tidp_build_conx connecting to 10.1.1.2, fd 1	TIDP is attempting to connect the 10.1.1.2 peer.
TIDP: tidp_complete_conx connect failed to 10.1.1.2, fd 1	TIDP failed to connect to the 10.1.1.2 peer.

The following example is sample output from the debug tidp command entered with the registration keyword:

Router# debug tidp registration 

TIDP registration debugging is on

00:36:13: TIDP: tidp_process_reg_msg Registered to 10.1.1.3, grp 10 

00:39:46: TIDP: tidp_clear_conx Deregistered peer 10.1.1.4, grp 10 

Table 344 describes the significant fields shown in the display.

Table 344 debug tidp registration Field Descriptions 

Field	Description
TIDP: tidp_process_reg_msg Registered to 10.1.1.3, grp 10	TIDP successfully registered the 10.1.1.3 peer.
TIDP: tidp_clear_conx Deregistered peer 10.1.1.4, grp 10	TIDP successfully deregistered the 10.1.1.4 peer.

The following example, from the debug tidp command entered with the test keyword, enables TIDP test functionality. This example shows a test messages sent to the 10.1.1.2 peer in TIDP group 10.

Sender (10.1.1.1)

Router1# debug tidp test 

TIDP test debugging is on 

Router1# test tidp send group 10 peer 10.1.1.2 Unicast_Test_Message 

Receiver (10.1.1.2)

Router2# debug tidp test 

TIDP test debugging is on 

Router2# 

03:36:03: TIDP msg from 10.1.1.1, group 10: 'Unicast_Test_Message' 

Table 345 describes the significant fields shown in the display.

Table 345 debug tidp test Field Descriptions 

Field	Description
TIDP test debugging is on	TIDP test debugging CLI has been enabled.
03:36:03: TIDP msg from 10.1.1.1, group 10: 'Unicast_Test_Message'	TIDP test message printed in the console of the receiving peer.

Related Commands

Command	Description
test tidp	Sends test messages to a TIDP group or peer.

debug tiff reader

To display output about the off-ramp TIFF reader, use the debug tiff reader command in privileged EXEC mode. 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.

Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(4)T	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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 command in privileged EXEC mode. 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

Privileged EXEC

Command History

Release	Modification
12.0(4)T	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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 tms consumer

To enable the generation of debugging messages on a consumer, use the debug tms consumer command in privileged EXEC mode. To stop the processing and generation of debug messages, use the no form of this command.

debug tms consumer {all | errors [details] | events [details] | feature-interface | packet | protocol | xml [detail | error | event]}

no debug tms consumer {all | errors [details] | events [details] | feature-interface | packet | protocol | xml [detail | error | event]}

Syntax Description

all	Enables the generation of most forms of the consumer debugging messages. Note XML error debugging messages are not processed when this form of this command is enabled.
errors	Enables the generation of TMS error debugging messages.
details	(Optional) Enables the generation of detailed debugging messages.
events	Enables the generation of TMS event debugging messages.
feature-interface	Enables the generation of TMS debugging messages for ACL drop enforcement actions, or redirect enforcement actions (enabled by OER).
packet	Enables the generation of TMS packet debugging messages.
protocol	Enables the generation of TMS protocol debugging messages.
xml	Enables the generation of XML (Threat Information Message) debugging messages.
detail	(Optional) Enables the generation of detailed XML debugging messages.
error	(Optional) Enables the generation of XML error debugging messages.
event	(Optional) Enables the generation of XML event debugging messages.

Command Default

No debugging messages on a consumer are generated.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
12.4(6)T	This command was introduced.
12.4(15)XZ	This command was integrated into Cisco IOS Release 12.4(15)XZ.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
12.4(20)T	This command was integrated into Cisco IOS Release 12.4(20)T.

Usage Guidelines

The debug tms consumer command is entered on a consumer.

This command should be used with caution on a production router or networking device. We recommend that debugging is enabled for only individual components as necessary. This restriction is intended to prevent the console session from be overwhelmed by large numbers of messages.

Examples

Event Debugging Example

The following is sample output from the debug tms consumer command entered with the events keyword:

Router# debug tms consumer events 

TMS consumer event debugging is on

*Feb 27 21:27:18: TMS_EVE_CO:start timer Controller=10.1.1.1 period=180

*Feb 27 21:27:18: TMS_EVE:Posting a message for the service layer

*Feb 27 21:27:18: TMS_EVE_CO:Processing Reg messsage from ctrl=10.1.1.1 group=10

*Feb 27 21:27:18: TMS_EVE_CO:Processing Reg response from ctrl=10.1.1.1  group=10

*Feb 27 21:27:18: TMS_EVE_CO:start timer Controller=10.1.1.1 period=120

Table 346 describes the significant fields shown in the display.

Table 346 debug tms consumer events Field Descriptions 

Field	Description
TMS_EVE_CO	Event information for a consumer follows.

Feature-Interface Debugging Example

The following is sample output from the debug tms consumer command entered with the feature-interface keyword:

Router# debug tms consumer feature-interface 

TMS consumer feature-interface debugging is on

*Feb 27 21:28:12: TMS_FI_CO:OER:Policy Add client 2 pol id 12 tag 5000  nxthop 172.16.1.1

*Feb 27 21:28:12: TMS_FI_CO:OERCB:ctx C type 2 values 0

*Feb 27 21:28:12: TMS_FI_CO:OERCB:return code rcvd rc 1 

*Feb 27 21:28:12: TMS_FI_CO:OERCB:Threat (1, 1, 1) grpid 10 ctrlip 10.1.1.1 statflags 0 
pol state 1

*Feb 27 21:28:12: TMS_FI_CO:OERCB:Prefix create client 2 id 12 src 0.0.0.0 0.0.0.0 dst 
192.168.8.0 255.255.255.0 proto 6 0 - 0, 10 - 2000 grant TRUE exact TRUE

*Feb 27 21:28:12: TMS_FI_CO:OERCB:ctx C type 2 values 0

*Feb 27 21:28:12: TMS_FI_CO:OERCB:return code rcvd rc 1 

*Feb 27 21:28:12: TMS_FI_CO:OERCB:Threat (1, 1, 1) grpid 10 ctrlip 10.1.1.1 statflags 0 
pol state 3

*Feb 27 21:28:12: TMS_FI_CO:OERCB:Prefix create success with rc = 1

*Feb 27 21:28:13: TMS_FI_CO:ACL:CB3: acl 66886028 item 669C9F98 type 3 ADD 

*Feb 27 21:28:13: TMS_FI_CO:ACL:CB1: acl 66886028 modified.

*Feb 27 21:28:13: TMS_FI_CO:ACL:CB3: acl 66886098 item 669CA0E0 type 3 ADD 

*Feb 27 21:28:13: TMS_FI_CO:ACL:CB1: acl 66886098 modified.

Table 347 describes the significant fields shown in the display.

Table 347 debug tms consumer feature-interface Field Descriptions 

Field	Description
TMS_FI_CO	Information for a TMS feature-interface function follows.
OER	Information for a redirect enforcement action follows.
ACL	Information for an ACL drop enforcement action follows.

Packet Debugging Example

The following is sample output from the debug tms consumer command entered with the packet keyword:

Router# debug tms consumer packet 

TMS consumer packets debugging is on 

*Feb 27 00:00:38: TMSCONS:out:Type(6)HeartBeat Req trans-id 15698 len 16

*Feb 27 00:00:38:   tms_flags 8 msg_flags 0 reason 0

*Feb 27 00:00:38:   TLVs:

*Feb 27 00:00:38: TMSCONS:in:Type(6)HeartBeat Req trans-id 158 len 16

*Feb 27 00:00:38:   tms_flags 0 msg_flags 0 reason 0

*Feb 27 00:00:38:   TLVs:

Table 348 describes the significant fields shown in the display.

Table 348 debug tms consumer packet Field Descriptions 

Field	Description
TMSCONS	Information for a consumer message follows.
TLVs	Information about the TMS packet format follows.

Protocol Debugging Example

The following is sample output from the debug tms consumer command entered with the protocol keyword:

Router# debug tms consumer protocol 

TMS consumer protocol debugging is on

*Feb 27 21:27:18: TMS_PRO_CO:Sending RegReq ctrl=10.1.1.1 group=10

*Feb 27 21:27:18: TMS_PRO_CO:RegResp recvd controller 10.1.1.1 group 10

*Feb 27 21:27:18: TMS_PRO_CO:Sending Resync request for ctrl=10.1.1.1 group=10

*Feb 27 21:27:18: TMS_PRO_CO:Resync response recvd controller 10.1.1.1, group 10

*Feb 27 21:27:18: TMS_PRO_CO:Processing Resync response from Controller=10.1.1.1on 
Group=10

*Feb 27 21:28:12: TMS_PRO_CO:Threat msg recvd controller 10.1.1.1, Group 10

*Feb 27 21:28:12: TMS_PRO_CO:Processing Threat request from Controller=10.1.1.1on Group=10

*Feb 27 21:28:12: TMS_PRO_CO:msg:NewThreat (1,1,1) in grp 10 ctrl 10.1.1.1

*Feb 27 21:28:58: TMS_PRO_CO:Heartbeat msg recvd controller 10.1.1.1, Group 10

Table 349 describes the significant fields shown in the display.

Table 349 debug tms consumer protocol Field Descriptions 

Field	Description
TMS_PRO_CO	Information about the operation of the TMS protocol on a consumer follows.

XML Error Debugging Example

The following is sample output from the debug tms consumer command entered with the xml and error keywords:

Router# debug tms consumer xml error 

TMS consumer xml error debugs debugging is on

*Feb 27 21:28:12: TMS_XML_EVE:Decoding threat info

*Feb 27 21:28:12: TMS_XML_EVE:Found threat info

*Feb 27 21:28:12: TMS_XML_EVE:Found ERR

*Feb 27 21:28:12: TMS_XML_EVE:name is name, value is tc2

*Feb 27 21:28:12: Decoded Threat desc TLV:

*Feb 27 21:28:12:  Threat name = NAME:

*Feb 27 21:28:12:  Threat text = THREATTEXT:

*Feb 27 21:28:12:  Mitigation text = mitigationtext:

*Feb 27 21:28:12:  Threat classes :    [ tc2 ] 

*Feb 27 21:28:12:  ERR:

*Feb 27 21:28:12:  ASR = 5, SFR = 20, TFR = 40, ARR = 30 PD = 50

*Feb 27 21:28:12: TMS_XML_EVE:Decoding primtive

*Feb 27 21:28:12:  TMS-XML: Decoded primitive TLV 

*Feb 27 21:28:12:  Prim type = 2 

*Feb 27 21:28:12:  Primitive = redirect 

*Feb 27 21:28:12: TMS_XML_EVE:Decoding parameter

*Feb 27 21:28:12: TMS_XML_EVE:CNS PARSER  : Node is 129 tag = parameter

*Feb 27 21:28:12: TMS_XML_EVE:Found parameter

*Feb 27 21:28:12: TMS_XML_EVE:CNS PARSER  : Node is 130 tag = redirect

*Feb 27 21:28:12: TMS_XML_EVE:parameter : Found redirect

*Feb 27 21:28:12: TMS_XML_EVE:Found nexthop in redirect

*Feb 27 21:28:12: TMS_XML:Decoded Parameter TLV 

*Feb 27 21:28:12: Parameter type = 1

*Feb 27 21:28:12:  Redirect addr = 172.16.1.1 

*Feb 27 21:28:12: TMS_XML_EVE:Decoding match criteria

*Feb 27 21:28:12: TMS-XML: Decoded match crt TLV : 

*Feb 27 21:28:12:  Src addr : 0.0.0.0 , Src mask : 0.0.0.0

*Feb 27 21:28:12:  Dest addr : 192.168.8.0 , Dest mask : 255.255.255.0

*Feb 27 21:28:12:  Protocol : 6

*Feb 27 21:28:12:  Src port - Start : 0, End : 0

*Feb 27 21:28:12:  Dest port - Start : 10, End : 2000

Table 350 describes the significant fields shown in the display.

Table 350 debug tms consumer xml error Field Descriptions 

Field	Description
TMS_XML_EVE	Information for XML message event debugging follows.
TMS_XML	Information for XML message debugging follows.
TMS-XML	Threat information for XML message debugging follows.

Related Commands

Command	Description
debug tms controller	Enables the generation of debugging messages on a controller.

debug tms controller

To enable the generation of debugging messages on a TIDP Based Mitigation Services (TMS) controller, use the debug tms controller command in privileged EXEC mode. To stop the processing and generation of debug messages, use the no form of this command.

debug tms controller {all | errors [details] | events [details] | feature-interface | packet | protocol | xml [detail | error | event]}

no debug tms controller {all | errors [details] | events [details] | feature-interface | packet | protocol | xml [detail | error | event]}

Syntax Description

all	Enables the generation of most forms of the TMS consumer debugging messages. Note XML error debugging messages are not processed when this form of this command is enabled.
errors	Enables the generation of TMS error debugging messages.
details	(Optional) Enables the generation of detailed debugging messages.
events	Enables the generation of TMS event debugging messages.
packet	Enables the generation of TMS packet debugging messages.
protocol	Enables the generation of TMS protocol debugging messages.
xml	Enables the generation of XML (Threat Information Message) debugging messages.
detail	(Optional) Enables the generation of detailed XML debugging messages.
error	(Optional) Enables the generation of XML error debugging messages.
event	(Optional) Enables the generation of XML event debugging messages.

Command Default

No default behavior or values.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
12.4(6)T	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

The debug tms controller command is entered on a TMS controller.

This command should be used with caution on a production router or networking device. We recommend that debugging is enabled for only individual components as necessary. This restriction is intended to prevent the console session from be overwhelmed by large numbers of messages.

Examples

Event Debugging Example

The following is sample output from the debug tms controller command entered with the events keyword:

Router# debug tms controller events 

TMS controller events debugging is on

*Feb 27 10:12:42: TMS_EVE_CN:Timer expired group=10

*Feb 27 10:12:42: TMS_EVE_CN:Start timer: Group=10, period=120

*Feb 27 10:12:42: TMS_EVE:Posting a message for the service layer

*Feb 27 10:12:42: TMS_EVE_CN:Data packet recvd from DL layer

*Feb 27 10:13:34: TMS_EVE:Posting a message for the service layer

*Feb 27 10:13:34: TMS_EVE_CN:Data packet recvd from DL layer

*Feb 27 10:13:34: TMS_EVE_CN:Start timer: Group=10, period=120

*Feb 27 10:13:34: TMS_EVE:Posting a message for the service layer

*Feb 27 10:13:34: TMS_EVE_CN:Data packet recvd from DL layer

Table 351 describes the significant fields shown in the display.

Table 351 debug tms controller events Field Descriptions 

Field	Description
TMS_EVE_CN	Information for a TMS controller event message follows.

Packet Debugging Example

The following is sample output from the debug tms controller command entered with the packets keyword:

Router# debug tms controller packet 

TMS controller packets debugging is on 

TMS controller packets debugging is on 

*Feb 27 10:13:34: TMSCTRL:in:Type(1)Registration Req trans-id 15685 len 16 

*Feb 27 10:13:34:   tms_flags 8 msg_flags 1 reason 0 

*Feb 27 10:13:34:   TLVs: 

*Feb 27 10:13:34: TMSCTRL:out:Type(1)Registration Resp trans-id 15685 len 16 

*Feb 27 10:13:34:   tms_flags 1 msg_flags 1 reason 1 

*Feb 27 10:13:34:   TLVs: 

*Feb 27 10:13:34: TMSCTRL:in:Type(4)Resync/Audit Req trans-id 15686 len 16 

*Feb 27 10:13:34:   tms_flags 8 msg_flags 1 reason 0 

*Feb 27 10:13:34:   TLVs: 

*Feb 27 10:13:34: TMSCTRL:out:Type(4)Resync/Audit Resp trans-id 15686 len 24 

*Feb 27 10:13:34:   tms_flags 1 msg_flags 0 reason 0 

*Feb 27 10:13:34:   TLVs:  Summary(514,8) 

Table 352 describes the significant fields shown in the display.

Table 352 debug tms controller packet Field Descriptions 

Field	Description
TMSCTRL	Information for a TMS controller message follows.
TLVs	Information about the TMS packet format follows.

Protocol Debugging Example

The following is sample output from the debug tms controller command entered with the protocol keyword:

Router# debug tms controller protocol 

TMS controller protocol debugging is on 

*Feb 27 10:13:34: TMS_PRO_CN:Registration request recvd consumer 10.1.1.2, group 10 

*Feb 27 10:13:34: TMS_PRO_CN:Sending Reg resp to cons=10.1.1.2 group=10 

*Feb 27 10:13:34: TMS_PRO_CN:Resync request recvd consumer 10.1.1.2, group 10 

*Feb 27 10:13:34: TMS_PRO_CN:Received Resync Req Group=10 

*Feb 27 10:13:34: TMS_PRO_CN:Sending Resync resp for cons=10.1.1.2 group=10 ntids=0

Table 353 describes the significant fields shown in the display.

Table 353 debug tms controller protocol Field Descriptions 

Field	Description
TMS_PRO_CN	Information about the operation of the TMS protocol on a controller follows.

XML Debugging Example

The following is sample output from the debug tms controller command entered with the xml keyword:

Router# debug tms controller xml 

TMS controller xml debugs debugging is on

*Feb 27 10:13:45: TMS_XML_CN:Found tag threat in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag threat_info in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag primitive in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag parameter in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag tcdf in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag threat in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag threat_info in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag parameter in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag primitive in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag tcdf in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag threat in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag threat_info in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag parameter in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag primitive in threat file

*Feb 27 10:13:45: TMS_XML_CN:Found tag tcdf in threat file

*Feb 27 10:13:45: TMS_XML_EVE:Decoding threat tag

*Feb 27 10:13:45: TMS_XML_EVE:Found threat

*Feb 27 10:13:45: TMS_XML_EVE:Decoded threat TLV -  threat id : 1, owner id : 1, version : 
1

*Feb 27 10:13:45: TMS_XML_EVE:Decoding threat info

*Feb 27 10:13:45: TMS_XML_EVE:Found threat info

*Feb 27 10:13:45: TMS_XML_EVE:Found ERR

*Feb 27 10:13:45: TMS_XML_EVE:name is name, value is tc2

*Feb 27 10:13:45: Decoded Threat desc TLV:

*Feb 27 10:13:45:  Threat name = NAME:

*Feb 27 10:13:45:  Threat text = THREATTEXT:

*Feb 27 10:13:45:  Mitigation text = mitigationtext:

*Feb 27 10:13:45:  Threat classes :    [ tc2 ] 

*Feb 27 10:13:45:  ERR:

*Feb 27 10:13:45:  ASR = 5, SFR = 20, TFR = 40, ARR = 30 PD = 50

*Feb 27 10:13:45: TMS_XML_EVE:Decoding primtive

*Feb 27 10:13:45: TMS_XML_EVE:Found primtive

*Feb 27 10:13:45:  TMS-XML: Decoded primitive TLV 

*Feb 27 10:13:45:  Prim type = 2 

*Feb 27 10:13:45:  Primitive = redirect 

*Feb 27 10:13:45: TMS_XML_EVE:Decoding parameter

*Feb 27 10:13:45: TMS_XML_EVE:CNS PARSER  : Node is 129 tag = parameter

*Feb 27 10:13:45: TMS_XML_EVE:Found parameter

*Feb 27 10:13:45: TMS_XML_EVE:CNS PARSER  : Node is 130 tag = redirect

*Feb 27 10:13:45: TMS_XML_EVE:parameter : Found redirect

*Feb 27 10:13:45: TMS_XML_EVE:Found nexthop in redirect

*Feb 27 10:13:45: TMS_XML:Decoded Parameter TLV 

*Feb 27 10:13:45: Parameter type = 1

*Feb 27 10:13:45:  Redirect addr = 172.16.1.1

*Feb 27 10:13:45: TMS_XML_EVE:Decoding match criteria

*Feb 27 10:13:45: TMS-XML: Decoded match crt TLV : 

*Feb 27 10:13:45:  Src addr : 0.0.0.0 , Src mask : 0.0.0.0

*Feb 27 10:13:45:  Dest addr : 192.168.8.0 , Dest mask : 255.255.255.0

*Feb 27 10:13:45:  Protocol : 6

*Feb 27 10:13:45:  Src port - Start : 0, End : 0

*Feb 27 10:13:45:  Dest port - Start : 10, End : 2000

*Feb 27 10:13:45: TMS_EVE_CN:Threat (1,1,1) allocated.

*Feb 27 10:13:45: TMS_EVE_CN:Threat (1,1,1) added to LoadDB.

*Feb 27 10:13:45: TMS_XML_CN:Threat (1,1,1) Loaded into LoadDB

*Feb 27 10:13:45: TMS_XML_EVE:Decoding threat tag

*Feb 27 10:13:45: TMS_XML_EVE:Found threat

*Feb 27 10:13:45: TMS_XML_EVE:Decoded threat TLV -  threat id : 2, owner id : 1, version : 
1

Table 354 describes the significant fields shown in the display.

Table 354 debug tms controller xml Field Descriptions 

Field	Description
TMS_XML_EVE	Information for XML message event debugging follows.
TMS_XML_CN	Controller information for XML message debugging follows.
TMS-XML	Threat information for XML message debugging follows.

Related Commands

Command	Description
debug tms consumer	Enables the generation of debugging messages on a TMS consumer.

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 routers 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 355 describes the significant fields shown in the second line of output.

Table 355 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 356 describes the significant fields shown in the third line of output.

Table 356 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 routing information field (RIF) 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 357 describes the significant fields shown in the fifth line of output.

Table 357 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 topology

To enable debugging for topology related events, use the debug topology command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug topology {accounting | all | cache | db | event | ha | interface | locking | sb | state | topoid | vrf}

no debug topology {accounting | all | cache | db | event | ha | interface | locking | sb | state | topoid | vrf}

Syntax Description

accounting	Enables debugging for topology accounting.
all	Enables debugging for all topology routing events.
cache	Enables debugging for topology ID cache activity.
db	Enables debugging for topology DB events.
event	Enables debugging for topology notification events.
ha	Enables debugging for topology High Availability (HA) events.
interface	Enables debugging for topology interface association.
locking	Enables debugging for topology client locking activity.
sb	Enables debugging for topology sub-block.
state	Enables debugging for topology state change events.
topoid	Enables debugging for topology ID management events.
vrf	Enables debugging for topology VRF association.

Command Default

Debugging output for topology related events is disabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.2(33)SRB	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following example shows how to enable debugging for topology HA events:

Router# debug topology ha

Related Commands

Command	Description
show topology	Displays status and configuration information for topologies configured with MTR.

debug track

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

debug track

no debug track

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
12.2(15)T	This command was introduced.
12.3(8)T	The output was enhanced to include the track-list objects.
12.2(25)S	This command was integrated into Cisco IOS Release 12.2(25)S.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
Cisco IOS XE Release 2.1	This command was integrated into Cisco IOS XE Release 2.1.

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, the IP-route reachability, and the IP-route threshold metric.

Examples

The following example shows that object number 100 is being tracked and that 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 that 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

---

Note Effective with release 12.3(8)T, the debug tsp command is replaced by the debug voip tsp command. See the debug voip tsp command for more information.

---

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.
12.3(8)T	This command was replaced by the debug voip tsp command.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following shows sample output from the debug tsp all command:

Router# debug tsp all 

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 tunnel rbscp

To turn on the debugging output for Rate Based Satellite Control Protocol (RBSCP) tunnels, use the debug tunnel rbscp command in privileged EXEC mode. To turn off debugging output, use the no form of this command.

debug tunnel rbscp [ack_split | detail | msg | rto | state | window]

no debug tunnel rbscp [ack_split | detail | msg | rto | state | window]

Syntax Description

ack_split	(Optional) Displays debugging messages about RBSCP ACK splitting.
detail	(Optional) Displays detailed debugging messages about RBSCP.
msg	(Optional) Displays debugging messages about the RBSCP messages.
rto	(Optional) Displays debugging messages about RBSCP round-trip times (RTTs) and retransmission timeouts (RTOs).
state	(Optional) Displays debugging messages about the RBSCP states.
window	(Optional) Displays debugging messages about RBSCP window stuffing.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(7)T	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

Use the debug tunnel rbscp command in privileged EXEC mode to troubleshoot RBSCP command operations.

---

Caution Use any debugging command with caution as the volume of output generated can slow or stop the router operations. We recommend that this command be used only under the supervision of a Cisco engineer.

---

Examples

The following example turns on debugging messages about RBSCP messages:

Router# debug tunnel rbscp msg

Tunnel RBSCP message debugging is on

router#

*Mar  1 05:36:01.435: handling FWD_TSN: sequence=20h, tsn=0h

*Mar  1 05:36:03.371: rbscp_output_a_fwdtsn: tsn=0h, seq=Dh, for_hb=1

*Mar  1 05:36:10.835: handling FWD_TSN: sequence=21h, tsn=0h

*Mar  1 05:36:12.771: rbscp_output_a_fwdtsn: tsn=0h, seq=Eh, for_hb=1

*Mar  1 05:36:20.235: handling FWD_TSN: sequence=22h, tsn=0h

*Mar  1 05:36:22.171: rbscp_output_a_fwdtsn: tsn=0h, seq=Fh, for_hb=1

---

Note The debug output will vary depending on what the router is configured to do after the debug command is entered.

---

Table 358 describes the significant fields shown in the display.

Table 358 debug tunnel rbscp msg Field Descriptions 

Field	Description
handling FWD_TSN	The router has received and is processing a FWD_TSN message from a peer with a sequence number of 20 hex and a Transport Sequence Number (TSN) of 0 hex.
rbscp_output_a_fwdtsn	The router is sending a FWD_TSN message to the peer with a TSN of 0 hex, a sequence number of 0D hex and it is for a heartbeat (equivalent of a keepalive).

The following example turns on debugging messages about RBSCP round-trip times and retransmission timeouts:

Router# debug tunnel rbscp rto

Tunnel RBSCP RTT/RTO debugging is on

router#

*Mar  1 05:36:50.927: update_rtt: cur_rtt:549 ms:548 delay:0

*Mar  1 05:36:50.927: New RTT est:549 RTO:703

*Mar  1 05:37:00.327: update_rtt: cur_rtt:549 ms:548 delay:0

*Mar  1 05:37:00.327: New RTT est:549 RTO:703

*Mar  1 05:37:09.727: update_rtt: cur_rtt:549 ms:548 delay:0

*Mar  1 05:37:09.727: New RTT est:549 RTO:703

Table 359 describes the significant fields shown in the display.

Table 359 debug tunnel rbscp rto Field Descriptions 

Field	Description
update rtt: curr rtt	Displays the updated, previous, and current RTT, in milliseconds, and a number that represents the amount of additional delay from queuing.
New RTT est	Displays the estimated new RTT, in milliseconds.
RTO	Displays the new retransmission timeout, in milliseconds.

Related Commands

Command	Description
show rbscp	Displays state and statistical information about RBSCP tunnels.

debug tunnel route-via

To display debugging information about the tunnel transport using a subset of the route table, use the debug tunnel route-via command in privileged EXEC mode. To disable this feature, use the no form of this command.

debug tunnel route-via

no debug tunnel route-via

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.4(11)T	This command was introduced.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following sample output of debug tunnel route-via command displays the outgoing interface for the tunnel transport.

Router# debug tunnel route-via

Tunnel route-via debugging is on

*May 22 11:54:34.803: TUN-VIA: Tunnel0 candidate route-via Ethernet0/0, next hop

 10.73.2.1

*May 22 11:54:34.803: TUN-VIA: Tunnel0 route-via action is forward

Router# no debug tunnel route-via

undebug tunnel route-via 

Tunnel route-via debugging is off

Related Commands

Command	Description
show interface tunnel	Displays information about the physical output tunnel interface.
tunnel route-via	Specifies the outgoing interface of the tunnel transport.

debug txconn all

To turn on all debug flags for Cisco Transaction Connection (CTRC) communications with the Customer Information Control System (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

Debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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 Advanced Program-to-Program Communication (APPC)-related trace or error messages for communications with the Customer Information Control System (CICS), use the debug txconn appc 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

Debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

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

Router# debug txconn appc

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 Cisco Transaction Connection (CTRC) configuration and control blocks for Customer Information Control System (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

Debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following shows sample output from 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 Customer Information Control System (CICS) client and host data being handled by Cisco Transaction Connection (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

Debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following 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 Cisco Transaction Connection (CTRC) events related to Customer Information Control System (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

Debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following shows sample output from 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

Debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Examples

The following shows sample 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 Cisco Transaction Connection (CTRC) communications with Customer Information Control System (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

Debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.0(5)XN	This command was introduced.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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 UDP Telnet (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.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

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 usb driver

To display debug messages about universal serial bus (USB) transfers, use the debug usb driver command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug usb driver [transfer transfer-method]

no debug usb driver [transfer transfer-method]

Syntax Description

transfer	(Optional) Specifies the type of transfer method for which messages are to be displayed on the console.
transfer-method	One of the following options: interrupt, bulk, or control.

Command Default

None

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(14)T	This command was introduced.
12.4(11)T	This command was integrated into the Cisco 7200VXR NPE-G2 platform.
12.2SX	This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.

Usage Guidelines

The debug usb driver command produces a large amount of data that might slow down your system, so use this command with caution.

Examples

The following sample debug output is produced when the debug usb driver command with the transfer and control keywords is issued and when an eToken is unplugged and plugged back in:

Router# debug usb driver transfer bulk 

USB Driver Bulk Transfer debugging is on

Router# debug usb driver transfer control

USB Driver Control Transfer debugging is on

Router# debug usb stack 

Stack debugging is on

Router#

Router#

*Dec 22 06:18:29.399:%USB_HOST_STACK-6-USB_DEVICE_DISCONNECTED:A USB device has been 
removed from port 1.

*Dec 22 06:18:29.499:Detached:

*Dec 22 06:18:29.499:Host:         1

*Dec 22 06:18:29.499:Address:      18

*Dec 22 06:18:29.499:Manufacturer: AKS

*Dec 22 06:18:29.499:Product:      eToken Pro 4254

*Dec 22 06:18:29.499:Serial Number:

Router#

*Dec 22 06:18:29.499:%USB_TOKEN_FILESYS-6-USB_TOKEN_REMOVED:USB Token device 
removed:usbtoken1.

*Dec 22 06:18:29.499:%CRYPTO-6-TOKENREMOVED:Cryptographic token eToken removed from 
usbtoken1

Router#

Router#

Router#

Router#

Router#

*Dec 22 06:18:38.063:%USB_HOST_STACK-6-USB_DEVICE_CONNECTED:A Low speed USB device has 
been inserted in port 1.

*Dec 22 06:18:38.683:ATTACHED===>Class-driver activated

*Dec 22 06:18:38.683:Host:         1

*Dec 22 06:18:38.683:Address:      19

*Dec 22 06:18:38.683:Manufacturer: AKS

*Dec 22 06:18:38.683:Product:      eToken Pro 4254

*Dec 22 06:18:38.683:Serial Number:

*Dec 22 06:18:39.383:Control Transfer

Device Handle:0x3010000

Direction:0x0

Request:0x1

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

*Dec 22 06:18:39.383:Control Transfer

Device Handle:0x3010000

Direction:0x80

Request:0x81

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

*Dec 22 06:18:39.407:Control Transfer

Device Handle:0x3010000

Direction:0x0

Request:0x3

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

*Dec 22 06:18:39.407:Control Transfer

Device Handle:0x3010000

Direction:0x80

Request:0

my3825#x83

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

*Dec 22 06:18:39.503:Control Transfer

Device Handle:0x3010000

Direction:0x0

Request:0x2

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

*Dec 22 06:18:39.507:Control Transfer

Device Handle:0x3010000

Direction:0x80

Request:0x82

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

*Dec 22 06:18:39.507:%USB_TOKEN_FILESYS-6-USB_TOKEN_INSERTED:USB Token device 
inserted:usbtoken1.

*Dec 22 06:18:39.515:Control Transfer

Device Handle:0x3010000

Direction:0x0

Request:0x6

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

*Dec 22 06:18:39.515:%USB_TOKEN_FILESYS-6-REGISTERING_WITH_IFS:Registering USB Token File 
System usbtoken1:might take a while...

*Dec 22 06:18:39.515:Control Transfer

Device Handle:0x3010000

Direction:0x80

Request:0x86

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

*Dec 22 06:18:39.543:Control Transfer

Device Handle:0x3010000

Direction:0x0

Request:0x6

Type:0x40

Recipient:0x0

ValueDesc:0x0

ValueIndex:0x0

Index:0x0

.

.

.

debug user-group

To display information about the user group, use the debug user-group command in privileged EXEC mode. To disable this feature, use the no form of this command.

debug user-group {additions | all | api | database | deletions}

no debug user-group {additions | all | api | database | deletions}

Syntax Description

additions	Displays debugging information about additions to the user-group.
all	Displays all debugging information about the user-group.
api	Displays debugging information about the user-group Application Programming Interface (API).
database	Displays debugging information about the user-group database of associated source IP addresses.
deletions	Displays debugging information about deletions from the user-group.

Command Modes

Privileged EXEC (#)

Command History

Release	Modification
12.4(20)T	This command was introduced.

Usage Guidelines

To troubleshoot user-based firewall support, use the debug user-group command.

Examples

The following example configures debugging for user-group additions:

Router# debug user-group additions

Usergroup Additions debugging is on

Router# 

Related Commands

Command	Description
user-group	Defines the user-group associated with the identity policy.

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 360 describes the significant fields in the display.

Table 360 debug v120 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	V120 packet type: •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-AnyLAN port adapter 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 361 lists the messages that could be generated by this command.

Table 361 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 be displayed 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 debugging 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