Examples

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

Router# debug tag-template event

Examples

The following is sample output from the debug tarp eventsand 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

The table below describes the significant fields shown in display.

Examples

The following is sample output from the debug tarp packet command after the tarp querycommand 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

The table below describes the significant fields shown in the display.

Examples

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

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.

The table below describes the significant fields shown in the display.

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

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.

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 

Examples

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#

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

Examples

The following is sample output from the debug telnetcommand:

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

The table below describes the significant fields shown in the display.

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

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

The table below describes the significant fields in the first line of output.

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

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

The table below describes the significant fields shown in the display.

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

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

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

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

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

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

The table below describes the significant fields shown in the display.

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: =======================================

The table below describes the significant fields in the display.

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

The table below describes the significant fields shown in the display.

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

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

Examples

The following is sample output from the debug time-range ipccommand. 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

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

The table below describes the significant fields shown in the second line of output.

The table below describes the significant fields shown in the third line of output.

The table below describes the significant fields shown in the fifth line of output.

Examples

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

Device# debug topology ha

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

Examples

The sample output for the command is as follows:

debug trifecta all
Router-sp#debug trifecta all
TRIFECTA severe debugging is on
TRIFECTA major debugging is on
TRIFECTA minor debugging is on
TRIFECTA debug debugging is on
Router-sp#
Jan 24 20:06:34.463 IST: SP: process_trifecta_msgs(): Polling TIMEINFO slot 2.
Jan 24 20:06:34.463 IST: SP: send_time_zone_info_to_x86(): sending time zone info to X86 slot 2
Jan 24 20:07:24.467 IST: SP: process_trifecta_msgs(): Polling TIMEINFO slot 2.
Jan 24 20:07:24.467 IST: SP: send_time_zone_info_to_x86(): sending time zone info to X86 slot 2
Jan 24 20:08:14.471 IST: SP: process_trifecta_msgs(): Polling TIMEINFO slot 2.
Jan 24 20:08:14.471 IST: SP: send_time_zone_info_to_x86(): sending time zone info to X86 slot 2
Jan 24 20:09:04.475 IST: SP: process_trifecta_msgs(): Polling TIMEINFO slot 2.
Jan 24 20:09:04.475 IST: SP: send_time_zone_info_to_x86(): sending time zone info to X86 slot 2
Jan 24 20:09:54.479 IST: SP: process_trifecta_msgs(): Polling TIMEINFO slot 2.
Jan 24 20:09:54.479 IST: SP: send_time_zone_info_to_x86(): sending time zone info to X86 slot 2

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

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.

The table below describes the significant fields shown in the display.

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

The table below describes the significant fields shown in the display.

Examples

The following sample output of debug tunnel route-viacommand 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

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

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

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

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.

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.

Examples

The following shows sample output from the debug txconn tcpcommand:

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)

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)

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.

Examples

The following sample debug output is produced when the debug usb drivercommand 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
.
.
.

Examples

The following example configures debugging for user-group additions:

Router# debug user-group additions
Usergroup Additions debugging is on
Router
#
 

Examples

The following is sample output from the debug v120 eventcommand 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

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 

The table below describes the significant fields in the display.

Examples

The following is sample output from the debug vfi checkpoint command:

Router# debug vfi checkpoint 
*Jun  5 22:37:17.268: AToM HA: CF status 3 not processed
*Jun  5 22:37:17.268: VFI HA: CF status 3 not processed
*Jun  5 22:37:17.296: AC HA RF: CId:83, Seq:228, Sta:RF_STATUS_PEER_COMM, Opr:0, St:ACTIVE, PSt:STANDBY HOT
*Jun  5 22:37:17.296: VFI HA: CID 145, Seq 229, Status RF_STATUS_PEER_COMM, Op 0, State ACTIVE, Peer STANDBY HOT
*Jun  5 22:37:17.296: AToM HA: CID 84, Seq 230, Status RF_STATUS_PEER_COMM, Op 0, State ACTIVE, Peer STANDBY HOT
*Jun  5 22:37:17.444: AToM HA: CF status 3 not processed
*Jun  5 22:37:17.444: VFI HA: CF status 3 not processed
*Jun  5 22:37:17.268: %OIR-SP-3-PWRCYCLE: Card in module 6, is being power-cycled (RF request)
*Jun  5 22:37:17.792: AC HA RF: CId:83, Seq:228, Sta:RF_STATUS_PEER_PRESENCE, Opr:0, St:ACTIVE, PSt:DISABLED
*Jun  5 22:37:17.792: VFI HA: CID 145, Seq 229, Status RF_STATUS_PEER_PRESENCE, Op 0, State ACTIVE, Peer DISABLED
*Jun  5 22:40:40.244: SP-STDBY: SP: Currently running ROMMON from S (Gold) region
*Jun  5 22:40:45.028: %DIAG-SP-STDBY-6-RUN_MINIMUM: Module 6: Running Minimal Diagnostics...
*Jun  5 22:40:56.492: %DIAG-SP-STDBY-6-DIAG_OK: Module 6: Passed Online Diagnostics
*Jun  5 22:41:53.436: %SYS-SP-STDBY-5-RESTART: System restarted 
*Jun  5 22:42:12.760: VFI HA: CID 145 Seq 229 Event RF_PROG_STANDBY_BULK Op 0 State ACTIVE Peer STANDBY COLD-BULK
*Jun  5 22:42:12.764: VFI HA: Ignore RF progression event, VFI Mgr process is not running, skipped bulk sync 
*Jun  5 22:42:16.948: %ISSU_PROCESS-SP-7-DEBUG: Peer state is [ STANDBY HOT ]; Please issue the runversion command
*Jun  5 22:42:15.928: %PFREDUN-SP-STDBY-6-STANDBY: Ready for SSO mode
*Jun  5 22:42:16.956: %RF-SP-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
*Jun  5 22:42:16.112: %SYS-SP-STDBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output--

Examples

The following is sample output from the debug vg-anylancommand:

Router# debug vg-anylan
%HP100VG-5-LOSTCARR: HP100VG(2/0), lost carrier

The table below lists the messages that could be generated by this command.

Examples

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

Router# debug video vicm
Video ViCM FSM debugging is on
***** Starting Video call *****
Router# SVC HANDLE in rcvd:0x80001B:
00:42:55:ViCM - current state = Idle, Codec Ready
00:42:55:ViCM - current event = SVC Setup
00:42:55:ViCM - new state = Call Connected
00:42:55:ViCM - current state = Call Connected
00:42:55:ViCM - current event = SVC Connect Ack
00:42:55:ViCM - new state = Call Connected
*****Video Call Disconnecting*****
Router#
00:43:54:ViCM - current state = Call Connected
00:43:54:ViCM - current event = SVC Release
00:43:54:ViCM - new state = Remote Hangup
00:43:54:ViCM - current state = Remote Hangup
00:43:54:ViCM - current event = SVC Release Complete
00:43:54:ViCM - new state = Remote Hangup
mc3810_video_lw_periodic:Codec is not ready
mc3810_video_lw_periodic:sending message
00:43:55:ViCM - current state = Remote Hangup
00:43:55:ViCM - current event = DTR Deasserted
00:43:55:ViCM - new state = Idle
mc3810_video_lw_periodic:Codec is ready
mc3810_video_lw_periodic:sending message
00:43:55:ViCM - current state = Idle
00:43:55:ViCM - current event = DTR Asserted
00:43:55:ViCM - new state = Idle, Codec Ready

Examples

The following is sample output from the debug vlan packet output. In this example, a VLAN packet with a VLAN ID of 1000 was received on FDDI interface 0 and this interface was not configured to route or switch this VLAN packet:

Router# debug vlan packet
vLAN: IEEE 802.10 packet bearing vLAN ID 1000 received on interface
   Fddi0 which is not configured to route/switch ID 1000.

Examples

The following output is displayed when the debug voice aaa asnl command is entered:

Router# debug voice aaa asnl
01:39:15:voip_aaa_accounting_pthru_send:Method List Name:ml1, aaa_av_list 0x62D69FCC, acct_rec_type 3
01:39:15:voip_aaa_search_mlist_node_by_name:Method List Name:ml15
01:39:15:voip_aaa_accounting_pthru_send:Accounting Probe UID=1, adb = 629977A0
01:39:15:voip_aaa_accounting_pthru_send(1):increment num_acct_sent counter

The table below describes the significant fields shown in the display.

Examples

The debug voice all command output provides debug output for all the debug commands for the Voice Call Manager compiled into one display. For sample output of the individual commands, see the sample displays for the debug voice cp, debug voice eecm, debug voice protocol, debug voice signaling, and debug voice tdsmcommands.

Examples

The following is sample output from the debug voice cp command:

Router# debug voice cp 1/1
Voice Call Processing State Machine debugging is on
1/1: CPD( ), idle gets event seize_ind
1/1: CPD( ), idle gets event dsp_ready
1/1: CPD( ), idle ==> collect
1/1: CPD(in), collect gets event digit
1/1: CPD(in), collect gets event digit
1/1: CPD(in), collect gets event digit
1/1: CPD(in), collect gets event digit
1/1: CPD(in), collect gets event addr_done
1/1: CPD(in), collect ==> request
1/1: CPD(in), request gets event call_proceeding
1/1: CPD(in), request ==> in_wait_answer
1/1: CPD(in), in_wait_answer gets event call_accept
1/1: CPD(in), in_wait_answer gets event call_answered
1/1: CPD(in), in_wait_answer ==> connected
1/1: CPD(in), connected gets event peer_onhook
1/1: CPD(in), connected ==> disconnect_wait
1/1: CPD(in), disconnect_wait gets event idle_ind
1/1: CPD(in), disconnect_wait ==> idle

Examples

The following example shows a debug message that confirms that a crash dump file has been written to the specified destination. The stack is displayed on the console, and the DSPware version, complexity (image set), and Cisco IOS software version is also displayed.

Router# debug voice dsp crash-dump keepalives
 
*Mar  8 03:42:19.505:Got back DSP status 0x12 0x0 for dsp 9 slot 1 
*Mar  8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 10 slot 1 
*Mar  8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 11 slot 1 
*Mar  8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 12 slot 1 
*Mar  8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 13 slot 1 
*Mar  8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 14 slot 1 
*Mar  8 03:42:21.509:status cleared done, dsp 9 slot 1 
*Mar  8 03:42:21.513:status cleared done, dsp 10 slot 1 
*Mar  8 03:42:21.513:status cleared done, dsp 11 slot 1 
*Mar  8 03:42:21.513:status cleared done, dsp 12 slot 1 
*Mar  8 03:42:21.513:status cleared done, dsp 13 slot 1 

*Mar 8 03:42:21.513:status cleared done, dsp 14 slot 1

The following command disables all the debugging output on the screen to stop the output from the debug voice dsp crash-dump keepalives command:

Router# undebug all

The following example shows the debug voice dsp crash-dump details command entry when no DSP crash is present. There is no debugging output until there is one DSP crash. When the crash dump feature is turned on, the detailed debug messages are displayed.

Router# debug voice dsp crash-dump details
 

Examples

The following is sample output from the debug voice eecm command:

Router# debug voice eecm
1/1: EECM(in), ST_NULL       EV_ALLOC_DSP
1/1: EECM(in), ST_DIGIT_COLLECT  EV_PARSE_DIGIT  3
1/1: EECM(in), ST_DIGIT_COLLECT  EV_PARSE_DIGIT  7
1/1: EECM(in), ST_DIGIT_COLLECT  EV_PARSE_DIGIT  0
1/1: EECM(in), ST_DIGIT_COLLECT  EV_PARSE_DIGIT  2
1/1: EECM(in), ST_ADDRESS_DONE   EV_OUT_SETUP
-1/-1: EECM(out), ST_NULL     EV_IN_SETUP
1/1: EECM(in), ST_OUT_REQUEST   EV_IN_PROCEED
1/2: EECM(out), ST_SEIZE      EV_ALLOC_DSP
1/2: EECM(out), ST_SEIZE      EV_OUT_ALERT
1/1: EECM(in), ST_OUT_REQUEST   EV_IN_ALERT
1/1: EECM(in), ST_OUT_REQUEST   EV_OUT_ALERT_ACK
1/2 EECM(out), ST_IN_PENDING   EV_OUT_CONNECT
1/1: EECM(in), ST_WAIT_FOR_ANSWER EV_IN_CONNECT
1/2: EECM(out), ST_ACTIVE     EV_OUT_REL
1/1: EECM(in), ST_ACTIVE      EV_IN_REL
1/1: EECM(in), ST_DISCONN_PENDING EV_OUT_REL_ACK