Table Of Contents

debug dmsp doc-to-fax

debug dmsp fax-to-doc

debug dot1x

debug dot1x (EtherSwitch)

debug drip event

debug drip packet

debug dsc clock

debug dsip

debug dspapi

debug dspfarm

debug dspu activation

debug dspu packet

debug dspu state

debug dspu trace

debug dss ipx event

debug eap

debug eigrp fsm

debug eigrp neighbor

debug eigrp nsf

debug eigrp packet

debug eigrp transmit

debug eou

debug ephone alarm

debug ephone ccm-compatible

debug ephone detail

debug ephone error

debug ephone keepalive

debug ephone loopback

debug ephone moh

debug ephone mwi

debug ephone pak

debug ephone qov

debug ephone raw

debug ephone register

debug ephone state

debug ephone statistics

debug ephone vm-integration

debug errors

debug eswilp

debug event manager

debug events

debug dmsp doc-to-fax

---

Note Effective with release 12.3(8)T, the debug dmsp doc-to-fax command is replaced by the debug fax dmsp command. See the debug fax dmsp command for more information.

---

To display debugging messages for the doc Media Service Provider (docMSP) TIFF or text2Fax engine, use the debug dmsp doc-to-fax command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dmsp doc-to-fax [text-to-fax | tiff-reader]

no debug dmsp doc-to-fax [text-to-fax | tiff-reader]

Syntax Description

text-to-fax	(Optional) Displays debugging messages that occur while the DocMSP Component is receiving text packets and producing T4 fax data.
tiff-reader	(Optional) Displays debugging messages that occur while the DocMSP Component is receiving TIFF packets and producing T4 fax data.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(3)XI	This command was introduced on the Cisco AS5300 access server.
12.3(8)T	This command was replaced by the debug fax dmsp command.

Examples

The following is sample output from the debug dmsp doc-to-fax command:

Router# debug dmsp doc-to-fax

Jan  1 04:58:39.898: docmsp_call_setup_request: callid=18 

Jan  1 04:58:39.902: docmsp_call_setup_request():  ramp data dir=OFFRAMP, conf dir=SRC

Jan  1 04:58:39.902: docmsp_caps_ind: call id=18, src=17

Jan  1 04:58:39.902: docmsp_bridge cfid=5, srccid=18, dstcid=17

Jan  1 04:58:39.902: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC, encode out=2

Jan  1 04:58:39.902: docmsp_rcv_msp_ev: call id =18, evID = 42 

Jan  1 04:58:39.902: docmsp_bridge cfid=6, srccid=18, dstcid=15

Jan  1 04:58:39.902: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=DEST, encode out=2

Jan  1 04:58:39.902: docmsp_process_rcv_data: call id src=0, dst=18 

Jan  1 04:58:39.902: docmsp_generate_page: 

Jan  1 04:58:39.902: docmsp_generate_page: new context for Call 18

Jan  1 04:58:39.922: docmsp_get_msp_event_buffer: 

Jan  1 04:58:42.082: docmsp_xmit: call id src=15, dst=18

Jan  1 04:58:42.082: docmsp_process_rcv_data: call id src=15, dst=18 

Jan  1 04:58:42.082: offramp_data_process: 

Jan  1 04:58:42.102: docmsp_xmit: call id src=15, dst=18

Jan  1 04:58:42.106: docmsp_process_rcv_data: call id src=15, dst=18 

Jan  1 04:58:42.106: offramp_data_process: 

Jan  1 04:58:42.122: docmsp_xmit: call id src=15, dst=18

Jan  1 04:58:42.126: docmsp_process_rcv_data: call id src=15, dst=18 

Jan  1 04:58:42.126: offramp_data_process: 

Jan  1 04:58:42.142: docmsp_xmit: call id src=15, dst=18

Jan  1 04:58:42.146: docmsp_xmit: call id src=15, dst=18

Related Commands

Command	Description
debug dmsp fax-to-doc	Displays debugging messages for doc MPS fax-to-doc.

debug dmsp fax-to-doc

---

Note Effective with release 12.3(8)T, the debug dmsp fax-to-doc command is replaced by the debug fax dmsp command. See the debug fax dmsp command for more information.

---

To display debugging messages for doc MSP (docMSP) fax-to-doc, use the debug dmsp fax-to-doc command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dmsp fax-to-doc [tiff-writer]

no debug dmsp fax-to-doc [tiff-writer]

Syntax Description

tiff-writer

(Optional) Displays debug messages that occur while the DocMSP Component is receiving T4 fax data and producing TIFF packets.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(3)XI	This command was introduced on the Cisco AS5300 access server.
12.3(8)T	This command was replaced by the debug fax dmsp command.

Examples

The following is sample output from the debug dmsp fax-to-doc command:

Router# debug dmsp fax-to-doc

*Oct 16 08:29:54.487: docmsp_call_setup_request: callid=22 

*Oct 16 08:29:54.487: docmsp_call_setup_request():  ramp data dir=OFFRAMP, conf dir=SRC

*Oct 16 08:29:54.487: docmsp_caps_ind: call id=22, src=21

*Oct 16 08:29:54.487: docmsp_bridge cfid=15, srccid=22, dstcid=21

*Oct 16 08:29:54.487: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC, encode out=2

*Oct 16 08:29:54.487: docmsp_bridge cfid=16, srccid=22, dstcid=17

*Oct 16 08:29:54.487: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=DEST, encode out=2

*Oct 16 08:29:54.487: docmsp_xmit: call id src=17, dst=22

*Oct 16 08:29:54.487: docmsp_process_rcv_data: call id src=17, dst=22 

*Oct 16 08:29:54.487: offramp_data_process: 

*Oct 16 08:29:54.515: docmsp_get_msp_event_buffer: 

*Oct 16 08:29:56.115: docmsp_call_setup_request: callid=24 

*Oct 16 08:29:56.115: docmsp_call_setup_request():  ramp data dir=ONRAMP, conf dir=DEST

*Oct 16 08:29:56.115: docmsp_caps_ind: call id=24, src=20

*Oct 16 08:29:56.115: docmsp_bridge cfid=17, srccid=24, dstcid=20

Related Commands

Command	Description
debug dmsp doc-to-fax	Displays debugging messages for the doc Media Service Provider TIFF or text2Fax engine.

debug dot1x

To display 802.1X debugging information, use the debug dot1x command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dot1x [aaa | all | process | rxdata | state-machine | supplicant | txdata | vlan]

no debug dot1x [aaa | all | process | rxdata | state-machine | supplicant | txdata | vlan]

Syntax Description

aaa	(Optional) Provides information for authentication, authorization, and accounting (AAA) communications.
all	(Optional) Enables all 802.1X debugging messages.
process	(Optional) Provides information regarding the 802.1X process.
rxdata	(Optional) Provides information for packets that have been received from clients.
state-machine	(Optional) Provides information regarding the 802.1X state machine.
supplicant	(Optional) Provides information about the supplicant.
txdata	(Optional) Provides information regarding packets that have been transmitted to clients.
vlan	(Optional) Provides information regarding the MAC address-based VLAN operation. Note VLAN interfaces are currently not supported.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(2)XA	This command was introduced.
12.3(4)T	This command was integrated into Cisco IOS Release 12.3(4)T.
12.3(11)T	The supplicant keyword was added.

Examples

The following is sample output for the debug dot1x command:

Router# debug dot1x 

*Mar 31 03:42:27.190: dot1x_hold_enqueue: Enqueued the packet to global hold queue

*Mar 31 03:42:27.206: dot1x_process: dequeued a hold client from  DOT1X HOLD Q for                                          
macaddr=0001.024b.87ce, hwidb=Ethernet0

*Mar 31 03:42:27.210: dot1x_aaa_add_client_entry: 0001.024b.87ce is added to the client 
list

*Mar 31 03:42:27.210: dot1x_aaa_run_auth_methods: Start auth method EAP

*Mar 31 03:42:27.210: dot1x_aaa_start: in the dot1x_aaa_start

*Mar 31 03:42:27.210: dot1x_process: DOT1X EVENT BEING HANDLED

*Mar 31 03:42:27.214: dot1x_run_rfsm: current state INIT, received EAP_START, mac: 
0001.024b.87ce

*Mar 31 03:42:27.214: dot1x_send_id_req_to_client: sending identity request for 
0001.024b.87ce

*Mar 31 03:42:27.214: dot1x_client_send_packet: Sending out an eapol packet

*Mar 31 03:42:27.214: EAPOL pak dump tx

*Mar 31 03:42:27.214: EAPOL Version: 0x1  type: 0x0  length: 0x0005

*Mar 31 03:42:27.218: EAP code: 0x1  id: 0x1  length: 0x0005 type: 0x1 

01E01E90:          01000005 01010005 01            .........   

*Mar 31 03:42:27.226: mac_identity_check: DOT1X packet, can't drop it

*Mar 31 03:42:27.226: dot1x_eapol_enqueue: Enqueued the eapol packet to global eapol queue

*Mar 31 03:42:27.218: dot1x_send_id_req_to_client: Starting timer client_timeout

*Mar 31 03:42:27.226: dot1x_start_timer: Started the Timer for client 0001.024b.87ce, 30 
seconds

*Mar 31 03:42:27.226: dot1x_process: dequeued a packet from  EAPOL Q link-type 0x8A

*Mar 31 03:42:27.226: dot1x_parse_client_pak: Received EAPOL packet from 0001.024b.87ce

*Mar 31 03:42:27.226: EAPOL pak dump rx

*Mar 31 03:42:27.226: EAPOL Version: 0x1  type: 0x0  length: 0x000A

*Mar 31 03:42:27.226: EAP code: 0x2  id: 0x1  length: 0x000A type: 0x1 

01E01D60: 0100000A 0201000A 01636973 636F      .........cisco  

*Mar 31 03:42:27.230: dot1x_run_rfsm: current state CLIENT_WAIT, received CLIENT_REPLY, 
mac: 0001.024b.87ce

*Mar 31 03:42:27.230: dot1x_stop_timer: Stopped the Timer for client 0001.024b.87ce

*Mar 31 03:42:27.234: dot1x_send_response_to_server: Sending client data to server

*Mar 31 03:42:27.234: dot1x_send_aaa_request: Trying to send the aaa request to auth 
server

*Mar 31 03:42:27.238: EAP pak dump tx

*Mar 31 03:42:27.238: EAP code: 0x2  id: 0x1  length: 0x000A type: 0x1 

01E01D60:          0201000A 01636973 636F          .....cisco  

*Mar 31 03:42:27.238: dot1x_send_aaa_request: aaa request sent successfully

*Mar 31 03:42:27.242: dot1x_send_response_to_server: Starting server timer

*Mar 31 03:42:27.242: dot1x_start_timer: Started the Timer for client 0001.024b.87ce, 30 
seconds

*Mar 31 03:42:49.294: dot1x_parse_aaa_resp: received AAA response for 0001.024b.87ce

*Mar 31 03:42:49.294: dot1x_parse_aaa_resp: Received server response: FAIL

*Mar 31 03:42:49.298: dot1x_run_rfsm: current state SERVER_WAIT, received SERVER_FAIL, 
mac: 0001.024b.87ce

*Mar 31 03:42:49.298: dot1x_stop_timer: Stopped the Timer for client 0001.024b.87ce

*Mar 31 03:42:49.298: dot1x_send_client_fail: Authentication failed for 0001.024b.87ce

*Mar 31 03:42:49.298: dot1x_client_send_packet: Sending out an eapol packet

*Mar 31 03:42:49.302: EAPOL pak dump tx

*Mar 31 03:42:49.302: EAPOL Version: 0x1  type: 0x0  length: 0x0004

*Mar 31 03:42:49.302: EAP code: 0x4  id: 0x1  length: 0x0004

01F22460:                            01000004              ....

01F22470: 04010004                             ....            

*Mar 31 03:42:49.306: dot1x_send_client_fail: Starting the quietWhile timer for 
0001.024b.87ce as the client supports dot1x

*Mar 31 03:42:49.306: dot1x_start_timer: Started the Timer for client 0001.024b.87ce, 120 
seconds

*Mar 31 03:42:49.310: 0001.024b.87ce(Ethernet0->Ethernet0): Processing started

*Mar 31 03:42:49.310: 0001.024b.87ce(Ethernet0->Ethernet0): Unable to determine IP address

Table 64 describes significant fields shown in the display.

Table 64 debug dot1x Field Descriptions 

Field	Description
dot1x_aaa_run_auth_methods	Starts the authentication process for the user.
dot1x_run_rfsm	Makes the state machine transition. Various states include CLIENT_WAIT (waiting for a response from the client), SERVER_WAIT, SERVER_PASS (a positive authentication result has been received from the server), and SERVER_FAIL.
mac_identity_check	Checks the authentication result for the user.

Related Commands

Command	Description
clear dot1x	Clears 802.1X interface information.
identity profile default	Creates an identity profile and enters dot1x profile configuration mode.
show dot1x	Shows details for an identity profile.

debug dot1x (EtherSwitch)

To enable debugging of the 802.1x protocol when an Ethernet switch network module is installed, use the debug dot1x command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dot1x {all | authsm | backend | besm | core | reauthsm}

no debug dot1x {all | authsm | backend | besm | core | reauthsm}

Syntax Description

all	Enables debugging of all conditions.
authsm	Enables debugging of the authenticator state machine, which is responsible for controlling access to the network through 802.1x-enabled ports.
backend	Enables debugging of the interaction between the 802.1x process and the router RADIUS client.
besm	Enables debugging of the backend state machine, which is responsible for relaying authentication request between the client and the authentication server.
core	Enables debugging of the 802.1x process, which includes 802.1x initialization, configuration, and the interaction with the port manager module.
reauthsm	Enables debugging of the reauthentication state machine, which manages periodic reauthentication of the client.

Defaults

Debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(6)EA2	This command was introduced.
12.2(15)ZJ	This command was implemented on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
12.3(4)T	This command was integrated into Cisco IOS Release 12.3(4)T on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.

Usage Guidelines

The undebug dot1x command is the same as the no debug dot1x command.

Related Commands

Command	Description
show debugging	Displays information about the types of debugging that are enabled.
show dot1x	Displays 802.1x statistics, administrative status, and operational status for the router or for the specified interface.

debug drip event

To display debugging messages for Duplicate Ring Protocol (DRiP) events, use the debug drip event command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug drip event

no debug drip event

Syntax Description

This command has no arguments or keywords.

Defaults

Debugging is disabled for DRiP events.

Command Modes

Privileged EXEC

Command History

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

Usage Guidelines

When a TrBRF interface is configured on the Remote Switch Module (RSM), the DRiP protocol is activated. The DRiP protocol adds the VLAN ID specified in the router command to its database and recognizes the VLAN as a locally configured, active VLAN.

Examples

The following is sample output from the debug drip event command:

Router# debug drip event

DRiP gets a packet from the network:

612B92C0: 01000C00 00000000 0C501900 0000AAAA  .........P....**

612B92D0: 0300000C 00020000 00000100 0CCCCCCC  .............LLL

612B92E0: 00000C50 19000020 AAAA0300 000C0102  ...P... **......

612B92F0: 01010114 00000002 00000002 00000C50  ...............P

612B9300: 19000001 04C00064 04                 .....@.d.       

DRiP gets a packet from the network:

Recvd. pak

DRiP recognizes that the VLAN ID it is getting is a new one from the network:

6116C840:                       0100 0CCCCCCC            ...LLL

6116C850: 00102F72 CBFB0024 AAAA0300 000C0102  ../rK{.$**......

6116C860: 01FF0214 0002E254 00015003 00102F72  ......bT..P.../r

6116C870: C8000010 04C00014 044003EB 14        H....@...@.k. 

DRIP : remote update - Never heard of this vlan

DRiP attempts to resolve any conflicts when it discovers a new VLAN. The value action = 1 means to notify the local platform of change in state.

DRIP : resolve remote for vlan 20 in VLAN0

DRIP : resolve remote - action = 1

The local platform is notified of change in state:

DRIP Change notification active vlan 20

Another new VLAN ID was received in the packet:

DRIP : resolve remote for vlan 1003 in Vlan0

No action is required:

DRIP : resolve remote - action = 0

Thirty seconds have expired, and DRiP sends its local database entries to all its trunk ports:

DRIP : local timer expired

DRIP : transmit on 0000.0c50.1900, length = 24

612B92C0: 01000C00 00000000 0C501900 0000AAAA  .........P....**

612B92D0: 0300000C 00020000 00000100 0CCCCCCC  .............LLL

612B92E0: 00000C50 19000020 AAAA0300 000C0102  ...P... **......

612B92F0: 01FF0114 00000003 00000002 00000C50  ...............P

612B9300: 19000001 04C00064 04                 .....@.d. 

debug drip packet

To display debugging messages for Duplicate Ring Protocol (DRiP) packets, use the debug drip packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug drip packet

no debug drip packet

Syntax Description

This command has no arguments or keywords.

Defaults

Debugging is not enabled for DRiP packets.

Command Modes

Privileged EXEC

Command History

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

Usage Guidelines

Before you use this command, you can optionally use the clear drip command first. As a result the DRiP counters are reset to 0. If the DRiP counters begin to increment, the router is receiving packets.

Examples

The following is sample output from the debug drip packet command:

Router# debug drip packet

The following type of output is displayed when a packet is entering the router and you use the show debug command:

039E5FC0:     0100 0CCCCCCC 00E0A39B 3FFB0028    ...LLL.`#.?{.(

039E5FD0: AAAA0300 000C0102 01FF0314 0000A5F6  **............%v

039E5FE0: 00008805 00E0A39B 3C000000 04C00028  .....`#.<....@.(

039E5FF0: 04C00032 044003EB 0F                 .@.2.@.k.       

039FBD20:                   01000C00 00000010          ........

The following type of output is displayed when a packet is sent by the router:

039FBD30: A6AEB450 0000AAAA 0300000C 00020000  &.4P..**........

039FBD40: 00000100 0CCCCCCC 0010A6AE B4500020  .....LLL..&.4P. 

039FBD50: AAAA0300 000C0102 01FF0114 00000003  **..............

039FBD60: 00000002 0010A6AE B4500001 04C00064  ......&.4P...@.d

039FBD70: 04                                   . 

Related Commands

Command	Description
debug drip event	Displays debugging messages for DRiP events.

debug dsc clock

To display debugging output for the time-division multiplexing (TDM) clock-switching events on the dial shelf controller (DSC), use the debug dsc clock command in privileged EXEC mode. To disable debugging output, use the no form of this command.

[execute-on] debug dsc clock

[execute-on] no debug dsc clock

Syntax Description

This command has no arguments or keywords; however, it can be used with the execute-on command.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.3(2)AA	This command was introduced.

Usage Guidelines

To perform this command from the router shelf on the Cisco AS5800 series platform, use the execute-on slot slot-number debug dsc clock form of this command.

The debug dsc clock command displays TDM clock-switching events on the dial shelf controller. The information displayed includes the following:

•Clock configuration messages received from trunks via NBUS

•Dial shelf controller clock configuration messages from the router shelf over the dial shelf interface link

•Clock switchover algorithm events

Examples

The following example shows that the debug dsc clock command has been enabled, and that trunk messages are received, and that the configuration message has been received:

AS5800# debug dsc clock

Dial Shelf Controller Clock debugging is on

AS5800#

00:02:55: Clock Addition msg of len 12 priority 8 from slot 1 port 1 on line 0

00:02:55: Trunk 1 has reloaded

Related Commands

Command	Description
execute-on	Executes commands remotely on a line card.
show dsc clock	Displays information about the dial shelf controller clock.

debug dsip

To display debugging output for Distributed System Interconnect Protocol (DSIP) used between a router shelf and a dial shelf, use the debug dsip command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dsip {all | api | boot | console | trace | transport}

no debug dsip {all | api | boot | console | trace | transport}

Syntax Description

all	View all DSIP debugging messages.
api	View DSIP client interface (API) debugging messages.
boot	View DSIP booting messages that are generated when a download of the feature board image is occurring properly.
console	View DSIP console operation while debugging.
trace	Enable logging of header information concerning DSIP packets entering the system into a trace buffer. This logged information can be viewed with the show dsip tracing command.
transport	Debug the DSIP transport layer, the module that interacts with the underlying physical media driver.

Command Modes

Privileged EXEC

Command History

Release	Modification
11.3(2)AA	This command was introduced.

Usage Guidelines

The debug dsip command is used to enable the display of debugging messages for DSIP between the router shelf and the dial shelf. Using this command, you can display booting messages generated when the download of an image occurs, view console operation, and trace logging of MAC header information and DSIP transport layer information as modules interact with the underlying physical media driver. This command can be applied to a single modem or a group of modems.

Once the debug dsip trace command has been enabled, you can read the information captured in the trace buffer using the show dsip tracing command.

Examples

The following example indicates the debug dsip trace command logs MAC headers of the various classes of DSIP packets. To view the logged information, use the show dsip tracing command:

AS5800# debug dsip trace

NIP tracing debugging is on

AS5800# show dsip tracing

NIP Control Packet Trace

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

Dest:00e0.b093.2238 Src:0007.4c72.0058 Type:200B SrcShelf:1 SrcSlot:11

MsgType:0 MsgLen:82 Timestamp: 00:49:14

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

Dest:00e0.b093.2238 Src:0007.4c72.0028 Type:200B SrcShelf:1 SrcSlot:5

MsgType:0 MsgLen:82 Timestamp: 00:49:14

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

Related Commands

Command	Description
debug modem	Displays information about the dial shelf, including clocking information.
show dsip tracing	Displays DSIP media header information logged using the debug dsip trace command.

debug dspapi

---

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

---

To enable debugging for Digital Signal Processor (DSP) application programming interface (API) message events, use the debug dspapi command in privileged EXEC mode. To reset the default value for this feature, use the no form of this command.

debug dspapi {all | command | detail | error | notification | response}

no debug dspapi {all | command | detail | error | notification | response}

Syntax Description

all	Enables all debug dspapi options (command, detail, error, notification and response).
command	Displays commands sent to the DSPs.
detail	Displays additional detail for the DSP API debugs enabled.
error	Displays any DSP API errors.
notification	Displays notification messages sent from the DSP (for example, tone detection notification).
response	Displays responses sent by the DSP (for example, responses to statistic requests).

Defaults

This command is not enabled.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(5)XM	This command was introduced on the Cisco AS5300 and Cisco AS5800.
12.1(5)XM1	This command was implemented on the Cisco AS5350 and Cisco AS5400.
12.2(2)T	This command was implemented on the Cisco 1700, Cisco 2600 series, Cisco 3600 series, and the Cisco 3810.
12.2(8)T	This command was integrated into Cisco IOS Release 12.2(8)T.
12.3(8)T	This command was replaced by the debug voip dspapi command.

Usage Guidelines

DSP API message events used to communicate with DSPs are intended for use with Connexant (Nextport) and Texas Instrument (54x) DSPs. This command severely impacts performance and should be used only for single-call debug capture.

Examples

The following example shows how to enable debugging for all DSP API message events:

Router# debug dspapi all

Related Commands

Command	Description
debug hpi	Enables debugging for HPI message events.

debug dspfarm

To display digital signal processor (DSP) farm service debugging information, use the debug dspfarm command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dspfarm {all | errors | events | packets}

no debug dspfarm

Syntax Description

all	All DSP-farm debug-trace information.
errors	DSP-farm errors.
events	DSP-farm events.
packets	DSP-farm packets.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release	Modification
12.1(5)YH	This command was introduced on the Cisco VG200.
12.2(13)T	This command was implemented on the Cisco 2600 series, Cisco 3620, Cisco 3640, Cisco 3660, and Cisco 3700 series.

Usage Guidelines

The router on which this command is used must be equipped with one or more digital T1/E1 packet voice trunk network modules (NM-HDVs) or high-density voice (HDV) transcoding/conferencing DSP farms (NM-HDV-FARMs) to provide DSP resources.

Debugging is turned on for all DSP-farm-service sessions. You can debug multiple sessions simultaneously, with different levels of debugging for each.

Examples

The following is sample output from the debug dspfarm events command:

Router# debug dspfarm events

DSP Farm service events debugging is on

*Mar  1 00:45:51: Sent 180 bytes to DSP 4 channel 2

*Mar  1 00:45:53: Sent 180 bytes to DSP 4 channel 3

*Mar  1 00:45:55: Sent 180 bytes to DSP 4 channel 1

*Mar  1 00:45:56: Sent 180 bytes to DSP 4 channel 2

*Mar  1 00:45:58: Sent 180 bytes to DSP 4 channel 3

*Mar  1 00:46:00: Sent 180 bytes to DSP 4 channel 1

*Mar  1 00:46:01: xapi_dspfarm_modify_connection: sess_id 26, conn_id 2705, conn_mode 3, 
ripaddr 10.10.1.7, rport 20170

*Mar  1 00:46:01: dspfarm_process_appl_event_queue: XAPP eve 6311C4B0 rcvd

*Mar  1 00:46:01: dspfarm_find_stream: stream 63121F1C, found in sess 631143CC, cid 2705

*Mar  1 00:46:01: dspfarm_modify_connection: old_mode 4, new_mode 3

*Mar  1 00:46:01: dspfarm_close_local_rtp: stream 63121F1C, local_rtp_port 22656

*Mar  1 00:46:01: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C4C8, 
eve_id 5, context 6311426C, result 0

*Mar  1 00:46:01: xapi_dspfarm_delete_connection: sess_id 26, conn_id 2705

*Mar  1 00:46:01: dspfarm_process_appl_event_queue: XAPP eve 6311C4E0 rcvd

*Mar  1 00:46:01: dspfarm_find_stream: stream 63121F1C, found in sess 631143CC, cid 2705

*Mar  1 00:46:01: dspfarm_close_local_rtp: stream 63121F1C, local_rtp_port 0

*Mar  1 00:46:01: dspfarm_release_dsp_resource: sess 631143CC, stream 63121F1C, num_stream 
3, sess_type 2, sess_dsp_id 2040000, stream_dsp_id 2040002

*Mar  1 00:46:01: dspfarm_drop_conference:slot 2 dsp 4 ch 2

*Mar  1 00:46:01: dspfarm_send_drop_conf: Sent drop_conference to DSP 4 ch 2

*Mar  1 00:46:01: dspfarm_xapp_enq: Sent msg 8 to DSPFARM

*Mar  1 00:46:01: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C4F8, 
eve_id 9, context 6311426C, result 0

*Mar  1 00:46:01: dspfarm_process_dsp_event_queue: DSP eve 6312078C rcvd

*Mar  1 00:46:01: dspfarm_delete_stream: sess_id 26, conn_id 2705, stream 63121F1C,  in 
sess 631143CC is freed

*Mar  1 00:46:01: Sent 180 bytes to DSP 4 channel 3

*Mar  1 00:46:04: Sent 180 bytes to DSP 4 channel 3

*Mar  1 00:46:05: xapi_dspfarm_modify_connection: sess_id 26, conn_id 2689, conn_mode 3, 
ripaddr 10.10.1.5, rport 19514

*Mar  1 00:46:05: dspfarm_process_appl_event_queue: XAPP eve 6311C510 rcvd

*Mar  1 00:46:05: dspfarm_find_stream: stream 63121E34, found in sess 631143CC, cid 2689

*Mar  1 00:46:05: dspfarm_modify_connection: old_mode 4, new_mode 3

*Mar  1 00:46:05: dspfarm_close_local_rtp: stream 63121E34, local_rtp_port 25834

*Mar  1 00:46:05: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C528, 
eve_id 5, context 63114244, result 0

*Mar  1 00:46:05: xapi_dspfarm_delete_connection: sess_id 26, conn_id 2689

*Mar  1 00:46:05: dspfarm_process_appl_event_queue: XAPP eve 6311C540 rcvd

*Mar  1 00:46:05: dspfarm_find_stream: stream 63121E34, found in sess 631143CC, cid 2689

*Mar  1 00:46:05: dspfarm_close_local_rtp: stream 63121E34, local_rtp_port 0

*Mar  1 00:46:05: dspfarm_release_dsp_resource: sess 631143CC, stream 63121E34, num_stream 
2, sess_type 2, sess_dsp_id 2040000, stream_dsp_id 2040001

*Mar  1 00:46:05: dspfarm_drop_conference:slot 2 dsp 4 ch 1

*Mar  1 00:46:05: dspfarm_send_drop_conf: Sent drop_conference to DSP 4 ch 1

*Mar  1 00:46:05: dspfarm_xapp_enq: Sent msg 8 to DSPFARM

*Mar  1 00:46:05: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C558, 
eve_id 9, context 63114244, result 0

*Mar  1 00:46:05: dspfarm_process_dsp_event_queue: DSP eve 6311586C rcvd

*Mar  1 00:46:05: dspfarm_delete_stream: sess_id 26, conn_id 2689, stream 63121E34,  in 
sess 631143CC is freed

*Mar  1 00:46:05: xapi_dspfarm_modify_connection: sess_id 26, conn_id 2721, conn_mode 3, 
ripaddr 10.10.1.6, rport 21506

*Mar  1 00:46:05: dspfarm_process_appl_event_queue: XAPP eve 6311C570 rcvd

*Mar  1 00:46:05: dspfarm_find_stream: stream 63122004, found in sess 631143CC, cid 2721

*Mar  1 00:46:05: dspfarm_modify_connection: old_mode 4, new_mode 3

*Mar  1 00:46:05: dspfarm_close_local_rtp: stream 63122004, local_rtp_port 19912

*Mar  1 00:46:05: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C588, 
eve_id 5, context 63114294, result 0

*Mar  1 00:46:05: xapi_dspfarm_delete_connection: sess_id 26, conn_id 2721

*Mar  1 00:46:05: dspfarm_process_appl_event_queue: XAPP eve 6311C5A0 rcvd

*Mar  1 00:46:05: dspfarm_find_stream: stream 63122004, found in sess 631143CC, cid 2721

*Mar  1 00:46:05: dspfarm_close_local_rtp: stream 63122004, local_rtp_port 0

*Mar  1 00:46:05: dspfarm_release_dsp_resource: sess 631143CC, stream 63122004, num_stream 
1, sess_type 2, sess_dsp_id 2040000, stream_dsp_id 2040003

*Mar  1 00:46:05: dspfarm_drop_conference:slot 2 dsp 4 ch 3

*Mar  1 00:46:05: dspfarm_drop_conference: Last conferee - closing the conf session

*Mar  1 00:46:05: dspfarm_send_close_conf: Sent close_conference to DSP 4

*Mar  1 00:46:05: dspfarm_drop_conference: Removed the conf in dsp 4

*Mar  1 00:46:05: dspfarm_xapp_enq: Sent msg 8 to DSPFARM

*Mar  1 00:46:05: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C5B8, 
eve_id 9, context 63114294, result 0

*Mar  1 00:46:05: dspfarm_process_dsp_event_queue: DSP eve 6311586C rcvd

*Mar  1 00:46:05: dspfarm_delete_stream: sess_id 26, conn_id 2721, stream 63122004,  in 
sess 631143CC is freed

Related Commands

Command	Description
debug frame-relay vc-bundle	Sets debugging for SCCP and its applications at one of four levels.
dspfarm (DSP farm)	Enables DSP-farm service.
sccp	Enables SCCP and its associated transcoding and conferencing applications.
show dspfarm	Displays summary information about DSP resources.

debug dspu activation

To display information on downstream physical unit (DSPU) activation, use the debug dspu activation command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dspu activation [name]

no debug dspu activation [name]

Syntax Description

name	(Optional) The host or physical unit (PU) name designation.

Command Modes

Privileged EXEC

Usage Guidelines

The debug dspu activation command displays all DSPU activation traffic. To restrict the output to a specific host or PU, include the host or PU name argument. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu activation command.

Examples

The following is sample output from the debug dspu activation command. Not all intermediate numbers are shown for the "activated" and "deactivated" logical unit (LU) address ranges.

Router# debug dspu activation 

DSPU: LS HOST3745 connected

DSPU: PU HOST3745 activated

DSPU: LU HOST3745-2 activated

DSPU: LU HOST3745-3 activated

.

.

.

DSPU: LU HOST3745-253 activated

DSPU: LU HOST3745-254 activated

DSPU: LU HOST3745-2 deactivated

DSPU: LU HOST3745-3 deactivated

.

.

.

DSPU: LU HOST3745-253 deactivated

DSPU: LU HOST3745-254 deactivated

DSPU: LS HOST3745 disconnected

DSPU: PU HOST3745 deactivated

Table 65 describes the significant fields shown in the display.

Table 65 debug dspu activation Field Descriptions 

Field	Description
DSPU	Downstream PU debugging message.
LS	Link station (LS) event triggered the message.
PU	PU event triggered the message.
LU	LU event triggered the message.
HOST3745	Host name or PU name.
HOST3745-253	Host name or PU name and the LU address, separated by a dash.
connected activated disconnected deactivated	Event that occurred to trigger the message.

Related Commands

Command	Description
debug dspu packet	Displays information on a DSPU packet.
debug dspu state	Displays information on DSPU FSM state changes.
debug dspu trace	Displays information on DSPU trace activity.

debug dspu packet

To display information on a downstream physical unit (DSPU) packet, use the debug dspu packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dspu packet [name]

no debug dspu packet [name]

Syntax Description

name	(Optional) The host or PU name designation.

Command Modes

Privileged EXEC

Usage Guidelines

The debug dspu packet command displays all DSPU packet data flowing through the router. To restrict the output to a specific host or physical unit (PU), include the host or PU name argument. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu packet command.

Examples

The following is sample output from the debug dspu packet command:

Router# debug dspu packet 

DSPU: Rx: PU HOST3745 data length 12 data:

    2D0003002BE16B80 000D0201

DSPU: Tx: PU HOST3745 data length 25 data:

    2D0000032BE1EB80 000D020100850000 000C060000010000 00

DSPU: Rx: PU HOST3745 data length 12 data:

    2D0004002BE26B80 000D0201

DSPU: Tx: PU HOST3745 data length 25 data:

    2D0000042BE2EB80 000D020100850000 000C060000010000 00

Table 66 describes the significant fields shown in the display.

Table 66 debug dspu packet Field Descriptions 

Field	Description
DSPU: Rx:	Received frame (packet) from the remote PU to the router PU.
DSPU: Tx:	Transmitted frame (packet) from the router PU to the remote PU.
PU HOST3745	Host name or PU associated with the transmit or receive.
data length 12 data:	Number of bytes of data, followed by up to 128 bytes of displayed data.

Related Commands

Command	Description
debug drip event	Displays debugging messages for DRiP packets.
debug dspu state	Displays information on DSPU FSM state changes.
debug dspu trace	Displays information on DSPU trace activity.

debug dspu state

To display information on downstream physical unit (DSPU) finite state machine (FSM) state changes, use the debug dspu state command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug dspu state [name]

no debug dspu state [name]

Syntax Description

name	(Optional) The host or physical unit (PU) name designation.

Command Modes

Privileged EXEC

Usage Guidelines

Use the debug dspu state command to display only the FSM state changes. To see all FSM activity, use the debug dspu trace command. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu state command.

Examples

The following is sample output from the debug dspu state command. Not all intermediate numbers are shown for the "activated" and "deactivated" logical unit (LU) address ranges.

Router# debug dspu state 

DSPU: LS HOST3745: input=StartLs, Reset -> PendConOut

DSPU: LS HOST3745: input=ReqOpn.Cnf, PendConOut -> Xid

DSPU: LS HOST3745: input=Connect.Ind, Xid -> ConnIn

DSPU: LS HOST3745: input=Connected.Ind, ConnIn -> Connected

DSPU: PU HOST3745: input=Actpu, Reset -> Active

DSPU: LU HOST3745-2: input=uActlu, Reset -> upLuActive

DSPU: LU HOST3745-3: input=uActlu, Reset -> upLuActive

.

.

.

DSPU: LU HOST3745-253: input=uActlu, Reset -> upLuActive

DSPU: LU HOST3745-254: input=uActlu, Reset -> upLuActive

DSPU: LS HOST3745: input=PuStopped, Connected -> PendDisc

DSPU: LS HOST3745: input=Disc.Cnf, PendDisc -> PendClose

DSPU: LS HOST3745: input=Close.Cnf, PendClose -> Reset

DSPU: PU HOST3745: input=T2ResetPu, Active -> Reset

DSPU: LU HOST3745-2: input=uStopLu, upLuActive -> Reset

DSPU: LU HOST3745-3: input=uStopLu, upLuActive -> Reset

.

.

.

DSPU: LU HOST3745-253: input=uStopLu, upLuActive -> Reset

DSPU: LU HOST3745-254: input=uStopLu, upLuActive -> Reset

Table 67 describes the significant fields shown in the display.

Table 67 debug dspu state Field Descriptions 

Field	Description
DSPU	Downstream PU debug message.
LS	Link station (LS) event triggered the message.