|
|
Table Of Contents
debug ephone extension-assigner
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
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
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-faxJan 1 04:58:39.898: docmsp_call_setup_request: callid=18Jan 1 04:58:39.902: docmsp_call_setup_request(): ramp data dir=OFFRAMP, conf dir=SRCJan 1 04:58:39.902: docmsp_caps_ind: call id=18, src=17Jan 1 04:58:39.902: docmsp_bridge cfid=5, srccid=18, dstcid=17Jan 1 04:58:39.902: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC, encode out=2Jan 1 04:58:39.902: docmsp_rcv_msp_ev: call id =18, evID = 42Jan 1 04:58:39.902: docmsp_bridge cfid=6, srccid=18, dstcid=15Jan 1 04:58:39.902: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=DEST, encode out=2Jan 1 04:58:39.902: docmsp_process_rcv_data: call id src=0, dst=18Jan 1 04:58:39.902: docmsp_generate_page:Jan 1 04:58:39.902: docmsp_generate_page: new context for Call 18Jan 1 04:58:39.922: docmsp_get_msp_event_buffer:Jan 1 04:58:42.082: docmsp_xmit: call id src=15, dst=18Jan 1 04:58:42.082: docmsp_process_rcv_data: call id src=15, dst=18Jan 1 04:58:42.082: offramp_data_process:Jan 1 04:58:42.102: docmsp_xmit: call id src=15, dst=18Jan 1 04:58:42.106: docmsp_process_rcv_data: call id src=15, dst=18Jan 1 04:58:42.106: offramp_data_process:Jan 1 04:58:42.122: docmsp_xmit: call id src=15, dst=18Jan 1 04:58:42.126: docmsp_process_rcv_data: call id src=15, dst=18Jan 1 04:58:42.126: offramp_data_process:Jan 1 04:58:42.142: docmsp_xmit: call id src=15, dst=18Jan 1 04:58:42.146: docmsp_xmit: call id src=15, dst=18Related Commands
debug dmsp fax-to-doc
Note
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
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=20Related Commands
debug dmsp doc-to-fax
Displays debugging messages for the doc Media Service Provider TIFF or text2Fax engine.
debug dmvpn
To debug Dynamic Multipoint VPN (DMVPN) sessions, use the debug dmvpn command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dmvpn {[{condition [unmatched] | [peer [nbma | tunnel {ip-address}]] | [vrf {vrf-name}] | [interface {tunnel number}]}] | [{error | detail | packet | all} {nhrp | crypto | tunnel | socket | all}]}
no debug dmvpn {[{condition [unmatched] | [peer [nbma | tunnel {ip-address}]] | [vrf {vrf-name}] | [interface {tunnel number}]}] | [{error | detail | packet | all} {nhrp | crypto | tunnel | socket | all}]}
Syntax Description
Command Default
DMVPN debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Conditional debugging will be in effect once the debug level has been specified. Either error level, detail level, packet level, or all debug levels may be turned on. Once conditional debugging is enabled, the condition keyword must be specified if you wish to disable conditional debugging.
There are three levels of debugging. From the least detailed information to the most detailed information, the DMVPM debugging levels are: error level, detail level, and packet level.
Error Level Debugging
When error level debugging is enabled with the debug dmvpn error command, the following debugging commands are enabled by default:
•
•
•
Detail Level Debugging
When event level debugging is enabled with the debug dmvpn detail command, the following debugging commands are enabled by default:
•
•
•
•
•
•
•
Packet Level Debugging
When event level debugging is enabled with the debug dmvpn packet command, the following debugging commands are enabled by default:
•
•
Note
Examples
The following example shows how to enable conditional DMVPN debugging for a specific peer NBMA address:
Router# debug dmvpn condition peer nbma 192.0.2.1The following example shows how to enable conditional DMVPN debugging when context is not available to check against debugging conditions:
Router# debug dmvpn condition unmatchedThe following example shows how to disable conditional debugging for a specific tunnel interface, tunnel1:
Router# no debug dmvpn condition interface tunnel1
The following example shows how to disable all conditional debugging:
Router# no debug dmvpn condition
Related Commands
debug nhrp condition
Enables NHRP conditional debugging.
debug nhrp error
Displays NHRP error level debugging information.
debug dot11
To enable debugging of radio functions, use the debug dot11 command in privileged EXEC mode. To stop or disable the debug operation, use the no form of this command.
debug dot11 {events | forwarding | mgmt | packets | syslog | virtual-interface}
no debug dot11 {events | forwarding | mgmt | packets | syslog | virtual-interface}
Syntax Descriptionno debug dot11
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
12.2(4)JA
This command was introduced.
12.4(2)T
This command was integrated into Cisco IOS Release 12.4(2)T.
Usage Guidelines
Use this command to display debugging information about radio functions.
Examples
The following example shows how to enable debugging all radio-related events:
Router# debug dot11 eventsRelated Commands
debug dot11 aaa
Enables debugging of dot11 AAA operations.
debug dot11 dot11radio
Enables radio debug options.
debug dot11 aaa
To enable debugging of dot11 authentication, authorization, and accounting (AAA) operations, use the debug dot11 aaa command in privileged EXEC mode. To disable or stop the debug operation, use the no form of this command.
debug dot11 aaa {accounting | authenticator {all | dispatcher | mac-authen | process | rxdata | state-machine | txdata} | dispatcher | manager {all | dispatcher | keys | rxdata | state-machine | supplicant | txdata}}
no debug dot11 aaa {accounting | authenticator {all | dispatcher | mac-authen | process | rxdata | state-machine | txdata} | dispatcher | manager {all | dispatcher | keys | rxdata | state-machine | supplicant | txdata}}
Syntax Descriptionno debug dot11
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display debugging information about dot11 AAA operations.
Examples
The following example shows how to activate debugging for 802.11 AAA accounting packets:
Router# debug dot11 aaa accountingRelated Commands
debug dot11
Enables debugging of radio functions.
debug dot11 dot11radio
Enables radio debug options.
debug dot11 dot11radio
To enable radio debug options, use the debug dot11 dot11radio command in privileged EXEC mode. To disable debug options, use the no form of this command.
debug dot11 dot11radio interface {accept-radio-firmware | dfs simulate [channel] | monitor {ack | address | beacon | crc | lines | plcp | print | probe | store} | print {hex | if | iv | lines | mic | plcp | printf | raw | shortadr} | stop-on-failure | trace {off | print | store}}
no debug dot11 dot11radio interface {accept-radio-firmware | dfs simulate [channel] | monitor {ack | address | beacon | crc | lines | plcp | print | probe | store} | print {hex | if | iv | lines | mic | plcp | printf | raw | shortadr} | stop-on-failure | trace {off | print | store}}
Syntax Description
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
12.2(4)JA
This command was introduced.
12.4(2)T
This command was integrated into Cisco IOS Release 12.4(2)T.
Usage Guidelines
Use this command to display debugging information about radio options.
Examples
This example shows how to begin monitoring of all packets with CRC errors:
Router# debug dot11 dot11radio 0 monitor crcRelated Commands
debug dot11
Enables debugging of radio functions.
debug dot11 aaa
Enables debugging of dot11 AAA operations.
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
Command Modes
Privileged EXEC
Command History
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: 0x101E01E90: 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: 0x101E01D60: 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: 0x101E01D60: 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: 0x000401F22460: 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 addressTable 77 describes significant fields shown in the display.
Related Commands
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
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug dot1x command is the same as the no debug dot1x command.
Related Commands
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
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 eventDRiP gets a packet from the network:
612B92C0: 01000C00 00000000 0C501900 0000AAAA .........P....**612B92D0: 0300000C 00020000 00000100 0CCCCCCC .............LLL612B92E0: 00000C50 19000020 AAAA0300 000C0102 ...P... **......612B92F0: 01010114 00000002 00000002 00000C50 ...............P612B9300: 19000001 04C00064 04 .....@.d.DRiP gets a packet from the network:
Recvd. pakDRiP recognizes that the VLAN ID it is getting is a new one from the network:
6116C840: 0100 0CCCCCCC ...LLL6116C850: 00102F72 CBFB0024 AAAA0300 000C0102 ../rK{.$**......6116C860: 01FF0214 0002E254 00015003 00102F72 ......bT..P.../r6116C870: C8000010 04C00014 044003EB 14 H....@...@.k.DRIP : remote update - Never heard of this vlanDRiP 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 VLAN0DRIP : resolve remote - action = 1The local platform is notified of change in state:
DRIP Change notification active vlan 20Another new VLAN ID was received in the packet:
DRIP : resolve remote for vlan 1003 in Vlan0No action is required:
DRIP : resolve remote - action = 0Thirty seconds have expired, and DRiP sends its local database entries to all its trunk ports:
DRIP : local timer expiredDRIP : transmit on 0000.0c50.1900, length = 24612B92C0: 01000C00 00000000 0C501900 0000AAAA .........P....**612B92D0: 0300000C 00020000 00000100 0CCCCCCC .............LLL612B92E0: 00000C50 19000020 AAAA0300 000C0102 ...P... **......612B92F0: 01FF0114 00000003 00000002 00000C50 ...............P612B9300: 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
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 packetThe 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 **............%v039E5FE0: 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...@.d039FBD70: 04 .Related Commands
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
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:
•
•
•
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 clockDial Shelf Controller Clock debugging is onAS5800#00:02:55: Clock Addition msg of len 12 priority 8 from slot 1 port 1 on line 000:02:55: Trunk 1 has reloadedRelated Commands
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
Command Modes
Privileged EXEC
Command History
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 traceNIP tracing debugging is onAS5800# show dsip tracingNIP Control Packet Trace------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.4c72.0058 Type:200B SrcShelf:1 SrcSlot:11MsgType:0 MsgLen:82 Timestamp: 00:49:14------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.4c72.0028 Type:200B SrcShelf:1 SrcSlot:5MsgType:0 MsgLen:82 Timestamp: 00:49:14------------------------------------------------------------Related Commands
debug dspapi
Note
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
Defaults
This command is not enabled.
Command Modes
Privileged EXEC
Command History
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 allRelated Commands
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
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 eventsDSP 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 freedRelated Commands
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
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 activationDSPU: LS HOST3745 connectedDSPU: PU HOST3745 activatedDSPU: LU HOST3745-2 activatedDSPU: LU HOST3745-3 activated...DSPU: LU HOST3745-253 activatedDSPU: LU HOST3745-254 activatedDSPU: LU HOST3745-2 deactivatedDSPU: LU HOST3745-3 deactivated...DSPU: LU HOST3745-253 deactivatedDSPU: LU HOST3745-254 deactivatedDSPU: LS HOST3745 disconnectedDSPU: PU HOST3745 deactivatedTable 78 describes the significant fields shown in the display.
Related Commands
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
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 packetDSPU: Rx: PU HOST3745 data length 12 data:2D0003002BE16B80 000D0201DSPU: Tx: PU HOST3745 data length 25 data:2D0000032BE1EB80 000D020100850000 000C060000010000 00DSPU: Rx: PU HOST3745 data length 12 data:2D0004002BE26B80 000D0201DSPU: Tx: PU HOST3745 data length 25 data:2D0000042BE2EB80 000D020100850000 000C060000010000 00Table 79 describes the significant fields shown in the display.
Related Commands
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
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 stateDSPU: LS HOST3745: input=StartLs, Reset -> PendConOutDSPU: LS HOST3745: input=ReqOpn.Cnf, PendConOut -> XidDSPU: LS HOST3745: input=Connect.Ind, Xid -> ConnInDSPU: LS HOST3745: input=Connected.Ind, ConnIn -> ConnectedDSPU: PU HOST3745: input=Actpu, Reset -> ActiveDSPU: LU HOST3745-2: input=uActlu, Reset -> upLuActiveDSPU: LU HOST3745-3: input=uActlu, Reset -> upLuActive...DSPU: LU HOST3745-253: input=uActlu, Reset -> upLuActiveDSPU: LU HOST3745-254: input=uActlu, Reset -> upLuActiveDSPU: LS HOST3745: input=PuStopped, Connected -> PendDiscDSPU: LS HOST3745: input=Disc.Cnf, PendDisc -> PendCloseDSPU: LS HOST3745: input=Close.Cnf, PendClose -> ResetDSPU: PU HOST3745: input=T2ResetPu, Active -> ResetDSPU: LU HOST3745-2: input=uStopLu, upLuActive -> ResetDSPU: LU HOST3745-3: input=uStopLu, upLuActive -> Reset...DSPU: LU HOST3745-253: input=uStopLu, upLuActive -> ResetDSPU: LU HOST3745-254: input=uStopLu, upLuActive -> ResetTable 80 describes the significant fields shown in the display.
Related Commands
debug drip event
Displays debugging messages for DRiP packets.
debug drip packet
Displays information on DSPU packet.
debug dspu trace
Displays information on DSPU trace activity.
debug dspu trace
To display information on downstream physical unit (DSPU) trace activity, which includes all finite state machine (FSM) activity, use the debug dspu trace command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dspu trace [name]
no debug dspu trace [name]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
Use the debug dspu trace command to display all FSM state changes. To see FSM state changes only, use the debug dspu state command. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu trace command.
Examples
The following is sample output from the debug dspu trace command:
Router# debug dspu traceDSPU: LS HOST3745 input = 0 ->(1,a1)DSPU: LS HOST3745 input = 5 ->(5,a6)DSPU: LS HOST3745 input = 7 ->(5,a9)DSPU: LS HOST3745 input = 9 ->(5,a28)DSPU: LU HOST3745-2 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-3 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-252 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-253 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-254 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)Table 81 describes significant fields shown in the output.
Related Commands
debug dss ipx event
To display debugging messages for route change events that affect Internetwork Packet Exchange (IPX) Multilayer Switching (MLS), use the debug dss ipx event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dss ipx event
no debug dss ipx event
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug dss ipx event command:
Router# debug dss ipx eventDSS IPX events debugging is onRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface vlan 22Router(config-if)# ipx access-group 800 out05:51:36:DSS-feature:dss_ipxcache_version():idb:NULL, reason:42,prefix:0, mask:FFFFFFFF05:51:36:DSS-feature:dss_ipx_access_group():idb:Vlan2205:51:36:DSS-feature:dss_ipx_access_list()05:51:36:DSS-base 05:51:33.834 dss_ipx_invalidate_interface Vl2205:51:36:DSS-base 05:51:33.834 dss_set_ipx_flowmask_reg 205:51:36:%IPX mls flowmask transition from 1 to 2 due to new status ofsimple IPX access list on interfacesRelated Commands
debug eap
To display information about Extensible Authentication Protocol (EAP), use the debug eap command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eap {all | errors | events | packets | sm}
no debug eap {all | errors | events | packets | sm}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following sample output from the debug eap all command shows all EAP information:
Router# debug eap all*Apr 9 19:19:05.475: eapauth_start_timer: eap-ev:Starting txWhen timer 3(10.0.0.1)*Apr 9 19:19:06.108: eapauth_post_msg_to_process: eap-ev:10.0.0.1: msg =6(eventEapResponse)*Apr 9 19:19:06.108: eap_auth 10.0.0.1: during state eapauth_connecting, got event4(eapResponse)*Apr 9 19:19:06.108: @@@ eap_auth 10.0.0.1: eapauth_connecting -> eapauth_authenticating*Apr 9 19:20:11.907: eap_parse_aaa_resp: eap-packets:10.0.0.1: AAA Resp Status =PASS*Apr 9 19:20:11.907: eap_parse_aaa_resp: eap-packets:10.0.0.1: Status Query Timeout=30*Apr 9 19:20:11.907: eap_dump_packet: eap-packets:EAP code: 0x3 id: 0x8 length: 0x0004*Apr 9 19:20:11.907: eap_parse_aaa_resp: eap-packets:10.0.0.1: Received MPPE_RECV_KEY(32)819C2BC0: 3E >819C2BD0: 138EC4CB FCACC44F EA4F56C8 4853BA0F ..DK|,DOjOVHHS:.819C2BE0: 9CB08871 B8ABC03A 3E97A96C EBF6DE .0.q8+@:>.)lkv^*Apr 9 19:20:11.911: eap_bend 10.0.0.1: during state eapbend_response, got event2(eapBendSuccess)*Apr 9 19:20:11.911: @@@ eap_bend 10.0.0.1: eapbend_response -> eapbend_success*Apr 9 19:20:11.911: eap_bend 10.0.0.1: idle during state eapbend_success*Apr 9 19:20:11.911: @@@ eap_bend 10.0.0.1: eapbend_success -> eapbend_idle*Apr 9 19:20:11.911: eap_auth 10.0.0.1: during state eapauth_authenticating, gotevent 10(eapSuccess)Related Commands
debug eigrp fsm
To display debugging information about Enhanced Interior Gateway Routing Protocol (EIGRP) feasible successor metrics (FSM), use the debug eigrp fsm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp fsm
no debug eigrp fsm
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Usage Guidelines
This command helps you observe EIGRP feasible successor activity and to determine whether route updates are being installed and deleted by the routing process.
Examples
The following is sample output from the debug eigrp fsm command:
Router# debug eigrp fsmDUAL: dual_rcvupdate(): 172.25.166.0 255.255.255.0 via 0.0.0.0 metric 750080/0DUAL: Find FS for dest 172.25.166.0 255.255.255.0. FD is 4294967295, RD is 4294967295 foundDUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0DUAL: dual_rcvupdate(): 192.168.4.0 255.255.255.0 via 0.0.0.0 metric 4294967295/4294967295DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0In the first line, DUAL stands for diffusing update algorithm. It is the basic mechanism within EIGRP that makes the routing decisions. The next three fields are the Internet address and mask of the destination network and the address through which the update was received. The metric field shows the metric stored in the routing table and the metric advertised by the neighbor sending the information. If shown, the term "Metric... inaccessible" usually means that the neighbor router no longer has a route to the destination, or the destination is in a hold-down state.
In the following output, EIGRP is attempting to find a feasible successor for the destination. Feasible successors are part of the DUAL loop avoidance methods. The FD field contains more loop avoidance state information. The RD field is the reported distance, which is the metric used in update, query, or reply packets.
The indented line with the "not found" message means a feasible successor (FS) was not found for 192.168.4.0 and EIGRP must start a diffusing computation. This means it begins to actively probe (sends query packets about destination 192.168.4.0) the network looking for alternate paths to 192.164.4.0.
DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295The following output indicates the route DUAL successfully installed into the routing table:
DUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0The following output shows that no routes to the destination were discovered and that the route information is being removed from the topology table:
DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0debug eigrp neighbor
To display neighbors discovered by the Enhanced Interior Gateway Routing Protocol (EIGRP), use the debug eigrp neighbor command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp neighbor [siatimer] [static]
no debug eigrp neighbor [siatimer] [static]
Syntax Description
Defaults
Debugging for EIGRP neighbors is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug eigrp neighbor command:
Router# debug eigrp neighbor staticEIGRP Static Neighbors debugging is onRouter# configure terminalRouter(config)# router eigrp 100Router(config-router)# neighbor 10.1.1.1 e3/1Router(config-router)#22:40:07:EIGRP:Multicast Hello is disabled on Ethernet3/1!22:40:07:EIGRP:Add new static nbr 10.1.1.1 to AS 100 Ethernet3/1Router(config-router)# no neighbor 10.1.1.1 e3/1Router(config-router)#22:41:23:EIGRP:Static nbr 10.1.1.1 not in AS 100 Ethernet3/1 dynamic list22:41:23:EIGRP:Delete static nbr 10.1.1.1 from AS 100 Ethernet3/122:41:23:EIGRP:Multicast Hello is enabled on Ethernet3/1!Related Commands
neighbor
Defines a neighboring router with which to exchange routing information.
show ip eigrp neighbors
Displays EIGRP neighbors.
debug eigrp notifications
To debug notifications sent from the L2L3 API interface, use the debug eigrp notifications command in privileged EXEC mode. To turn off debugging, use the no form of this command.
debug eigrp notifications {rib | interface}
Syntax Description
rib
Captures notifications from the routing information base (RIB)
interface
Captures notifications from the interface.
Command Default
Debugging of EIGRP notifications for the L2L3 API interface is not enabled.
Command Modes
Privileged EXEC
Command History
12.4(15)XF
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
Consult Cisco technical support before using this command.
Caution
Examples
The following example displays information about the L2L3 API Interface:
Router# debug eigrp notifications rib
Related Commands
debug eigrp nsf
To display nonstop forwarding (NSF) events in the console of the router, use the debug eigrp nsf command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp nsf
no debug eigrp nsf
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The output from the debug eigrp nsf command displays NSF-specific events. This command can be issued on an NSF-capable or NSF-aware router.
Examples
The following example enables EIGRP NSF debugging:
Router# debug eigrp nsfRelated Commands
timers nsf route-hold
Sets the route-hold timer for NSF-aware routers that run EIGRP.
debug eigrp packet
To display EIGRP debugging information about packets, use the debug eigrp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp packet [SIAquery SIAreply ack hello ipxsap probe query reply request retry stub terse update verbose]
no debug eigrp packet
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.0(7)T
This command was introduced.
12.4
The keywords were supported.
12.4(6)T
Support for IPv6 was added.
Usage Guidelines
If a communication session is closing when it should not be, an end-to-end connection problem might be the cause. The debug eigrp packet command is useful to TAC for analyzing the messages traveling between the local and remote hosts.
Note
Examples
The following is sample output from the debug eigrp packet command:
Router# debug eigrp packetEIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x1, Seq 1, Ack 0EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x0, Seq 2, Ack 0The output shows transmission and receipt of Enhanced Interior Gateway Routing Protocol (EIGRP) packets. These packet types may be hello, update, request, query, or reply packets. The sequence and acknowledgment numbers used by the EIGRP reliable transport algorithm are shown in the output. Where applicable, the network-layer address of the neighboring router is also included.
Table 82 describes the significant fields shown in the display.
debug eigrp transmit
To display transmittal messages sent by the Enhanced Interior Gateway Routing Protocol (EIGRP), use the debug eigrp transmit command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp transmit [ack] [build] [detail] [link] [packetize] [peerdown] [sia] [startup] [strange]
no debug eigrp transmit [ack] [build] [detail] [link] [packetize] [peerdown] [sia] [startup] [strange]
Syntax Description
Defaults
Debugging for EIGRP transmittal messages is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug eigrp transmit command:
Router# debug eigrp transmitEIGRP Transmission Events debugging is on(ACK, PACKETIZE, STARTUP, PEERDOWN, LINK, BUILD, STRANGE, SIA, DETAIL)Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router#(config)# router eigrp 100Router#(config-router)# network 10.4.9.0 0.0.0.255Router#(config-router)#5d22h: DNDB UPDATE 10.0.0.0/8, serno 0 to 1, refcount 0Router#(config-router)#debug eou
To display information about Extensible Authentication Protocol over User Datagram Protocol (UDP) (EAPoUDP), use the debug eou command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eou {all | eap | errors | events | packets | ratelimit | sm}
no debug eou {all | eap | errors | events | packets | ratelimit | sm}
Syntax Description
Defaults
If you do not enter any keywords, debugging is turned on for all EAPoUDP messages.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output from the debug eou all command shows all EAPoUDP information:
Router# debug eou all*Apr 9 19:30:40.782: eou-ev:EOU Init Validation for idb= FastEthernet0/0.420 src_mac=0001.027c.f364 src_ip= 10.0.0.1*Apr 9 19:30:40.786: eou_auth 10.0.0.1: initial state eou_initialize has enter*Apr 9 19:30:40.786: @@@ eou_auth 10.0.0.1: eou_initialize -> eou_hello*Apr 9 19:30:40.786: eou-ev:eou_send_hello_request: Send Hello Request host= 10.0.0.15eou_port= 5566 (hex)*Apr 9 19:30:40.790: EAPoUDP (tx) Flags:0 Ver=1 opcode=2 Len=8 MsgId=3839857370 AssocID=0*Apr 9 19:30:40.790: Dumping TLV contents*Apr 9 19:30:40.790: TLV M:1 R:0 Type=ASSOCIATION ID Length=4 Association=-1994800267*Apr 9 19:30:40.999: EAPoUDP (rx) Flags:128 Ver=1 opcode=2 Len=24 MsgId=3839857370 AssocID=2300167029*Apr 9 19:30:40.999: Dumping TLV contents*Apr 9 19:30:40.999: TLV M:1 R:0 Type=COOKIE PAYLOAD Length=1207167CE0: 8919C375 259B6D41 5FEA5D27 ..Cu%.mA_j]'07167CF0:*Apr 9 19:30:40.999: TLV M:1 R:0 Type=ASSOCIATION ID Length=4 Association=1016688999*Apr 9 19:31:50.048: @@@ eou_auth 10.0.0.1: eou_eap -> eou_eap*Apr 9 19:31:50.048: eou-ev:10.0.0.1: msg = 24(eventEouEapSuccess)*Apr 9 19:31:50.048: eou_auth 10.0.0.1: during state eou_eap, got event14(eouEapSuccess)*Apr 9 19:31:50.048: @@@ eou_auth 10.0.0.1: eou_eap -> eou_result*Apr 9 19:31:50.052: eou-ev:Starting RESULT timer 3(10.0.0.1)Related Commands
debug eap
Displays information about EAP messages.
debug ip admission eapoudp
Displays information about EAPoUDP network admission control events.
debug ephone alarm
To set SkinnyStation alarm messages debugging for the Cisco IP phone, use the debug ephone alarm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone alarm [mac-address mac-address]
no debug ephone alarm [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone alarm command shows all the SkinnyStation alarm messages sent by the Cisco IP phone. Under normal circumstances, this message is sent by the Cisco IP phone just before it registers, and the message has the severity level for the alarm set to "Informational" and contains the reason for the phone reboot or re-register. This type of message is entirely benign and does not indicate an error condition.
If the mac-address keyword is not used, the debug ephone alarm command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following example shows a SkinnyStation alarm message that is sent before the Cisco IP phone registers:
Router# debug ephone alarmphone keypad resetCM-closed-TCPCM-bad-stateRelated Commands
debug ephone blf
To display debugging information for Busy Lamp Field (BLF) presence features, use the debug ephone blf command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone blf [mac-address mac-address]
no debug ephone blf [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.4(11)XJ
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
Use this command for troubleshooting BLF speed-dial and BLF call-list features for phones in a presence service.
Examples
The following is sample output from the debug ephone blf command.
Router# debug ephone blfEPHONE BLF debugging is enabled*Sep 4 07:18:26.307: skinny_asnl_callback: subID 16 type 4*Sep 4 07:18:26.307: ASNL_RESP_NOTIFY_INDICATION*Sep 4 07:18:26.307: ephone-1[1]:ASNL notify indication message, feature index 4, subID [16]*Sep 4 07:18:26.307: ephone-1[1]:line status 6, subID [16]*Sep 4 07:18:26.307: ephone-1[1]:StationFeatureStatV2Message sent, status 2*Sep 4 07:18:26.307: skinny_asnl_callback: subID 23 type 4*Sep 4 07:18:26.307: ASNL_RESP_NOTIFY_INDICATION*Sep 4 07:18:26.307: ephone-2[2]:ASNL notify indication message, feature index 2, subID [23]*Sep 4 07:18:26.311: ephone-2[2]:line status 6, subID [23]*Sep 4 07:18:26.311: ephone-2[2]:StationFeatureStatV2Message sent, status 2*Sep 4 07:18:28.951: skinny_asnl_callback: subID 16 type 4*Sep 4 07:18:28.951: ASNL_RESP_NOTIFY_INDICATION*Sep 4 07:18:28.951: ephone-1[1]:ASNL notify indication message, feature index 4, subID [16]*Sep 4 07:18:28.951: ephone-1[1]:line status 1, subID [16]*Sep 4 07:18:28.951: ephone-1[1]:StationFeatureStatV2Message sent, status 1*Sep 4 07:18:28.951: skinny_asnl_callback: subID 23 type 4*Sep 4 07:18:28.951: ASNL_RESP_NOTIFY_INDICATION*Sep 4 07:18:28.951: ephone-2[2]:ASNL notify indication message, feature index 2, subID [23]*Sep 4 07:18:28.951: ephone-2[2]:line status 1, subID [23]*Sep 4 07:18:28.951: ephone-2[2]:StationFeatureStatV2Message sent, status 1Related Commands
debug ephone ccm-compatible
To display Cisco CallManager notification updates for calls between Cisco CallManager and Cisco CallManager Express, use the debug ephone ccm-compatible command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone ccm-compatible [mac-address mac-address]
no debug ephone ccm-compatible [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays call flow notification information for all calls between Cisco CallManager and Cisco CallManager Express, but it is most useful for filtering out specific information for transfer and forward cases. For basic call information, use the debug ephone state command.
If you do not specify the mac-address keyword, the debug ephone ccm-compatible command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the no form of this command with the mac-address keyword.
Debugging can be enabled or disabled on any number of Cisco IP phones. Cisco IP phones that have debugging enabled are listed in the debug field of the show ephone command output. When debugging is enabled for a Cisco IP phone, debug output is displayed for all phone extensions (virtual voice ports) associated with that phone.
Examples
The following sample output displays call flow notifications between Cisco CallManager and Cisco CallManager Express:
Router# debug ephone ccm-compatible*May 1 04:30:02.650:ephone-2[2]:DtAlertingTone/DtHoldTone - mediaActive reset during CONNECT*May 1 04:30:02.654:ephone-2[2]:DtHoldTone - force media STOP state*May 1 04:30:02.654://93/xxxxxxxxxxxx/CCAPI/ccCallNotify:(callID=0x5D,nData->bitmask=0x00000007)*May 1 04:30:02.654://93/xxxxxxxxxxxx/VTSP:(50/0/3):-1:0:5/vtsp_process_event:vtsp:[50/0/3 (93), S_CONNECT, E_CC_SERVICE_MSG]*May 1 04:30:02.654://93/xxxxxxxxxxxx/VTSP:(50/0/3):-1:0:5/act_service_msg_down:.*May 1 04:30:02.658:dn_callerid_update DN 3 number= 12009 name= CCM7960 in state CONNECTED*May 1 04:30:02.658:dn_callerid_update (incoming) DN 3 info updated to*May 1 04:30:02.658:calling= 12009 called= 13003 origCalled=*May 1 04:30:02.658:callingName= CCM7960, calledName= , redirectedTo =*May 1 04:30:02.658:ephone-2[2][SEP003094C2999A]:refreshDisplayLine for line 1DN 3 chan 1*May 1 04:30:03.318:ephone-2[2]:DisplayCallInfo incoming call*May 1 04:30:03.318:ephone-2[2]:Call Info DN 3 line 1 ref 24 called 13003 calling 12009 origcalled 13003 calltype 1*May 1 04:30:03.318:ephone-2[2]:Original Called Name UUT4PH3*May 1 04:30:03.318:ephone-2[2]:CCM7960 calling*May 1 04:30:03.318:ephone-2[2]:UUT4PH3Related Commands
debug ephone detail
To set detail debugging for the Cisco IP phone, use the debug ephone detail command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone detail [mac-address mac-address]
no debug ephone detail [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone detail command includes the error and state levels.
If the mac-address keyword is not used, the debug ephone detail command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of detail debugging of the Cisco IP phone with MAC address 0030.94c3.8724. The sample is an excerpt of some of the activities that takes place during call setup, connected state, active call, and the call being disconnected.
Router# debug ephone detail mac-address 0030.94c3.8724Ephone detail debugging is enabled1d04h: ephone-1[1]:OFFHOOK..1d04h: Skinny Call State change for DN 1 SIEZE..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsOffHook..1d04h: ephone-1[1]:SetLineLamp 1 to ON..1d04h: ephone-1[1]:KeypadButtonMessage 5..1d04h: ephone-1[1]:KeypadButtonMessage 0..1d04h: ephone-1[1]:KeypadButtonMessage 0..1d04h: ephone-1[1]:KeypadButtonMessage 2..1d04h: ephone-1[1]:Store ReDial digit: 5002.SkinnyTryCall to 5002 instance 1..1d04h: ephone-1[1]:Store ReDial digit: 50021d04h: ephone-1[1]:SkinnyTryCall to 5002 instance 1..1d04h: Skinny Call State change for DN 1 ALERTING..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsRingOut..1d04h: ephone-1[1]:SetLineLamp 1 to ON1d04h: SetCallInfo calling dn 1 dn 1calling [5001] called [5002]..1d04h: ephone-1[1]: Jane calling1d04h: ephone-1[1]: Jill..1d04h: SkinnyUpdateDnState by EFXS_RING_GENERATEfor DN 2 to state RINGING..1d04h: SkinnyGetCallState for DN 2 CONNECTED..1d04h: ephone-1[1]:SetLineLamp 3 to ON1d04h: ephone-1[1]:UpdateCallState DN 1 state 4 calleddn 2..1d04h: Skinny Call State change for DN 1 CONNECTED..1d04h: ephone-1[1]:OpenReceive DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 80..1d04h: ephone-1[1]:OpenReceiveChannelAck 1.2.172.21 port=201801d04h: ephone-1[1]:Outgoing calling DN 1 Far-ephone-2 called DN 21d04h: SkinnyGetCallState for DN 1 CONNECTED..1d04h: ephone-1[1]:SetCallState line 3 DN 2 TsOnHook..1d04h: ephone-1[1]:SetLineLamp 3 to OFF..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsOnHook..1d04h: ephone-1[1]:Clean Up Speakerphone state1d04h: ephone-1[1]:SpeakerPhoneOnHook1d04h: ephone-1[1]:Clean up activeline 11d04h: ephone-1[1]:StopTone sent to ephone1d04h: ephone-1[1]:Clean Up phone offhook state1d04h: SkinnyGetCallState for DN 1 IDLE1d04h: called DN -1, calling DN -1 phone -11d04h: ephone-1[1]:SetLineLamp 1 to OFF1d04h: UnBinding ephone-1 from DN 11d04h: UnBinding called DN 2 from DN 11d04h: ephone-1[1]:ONHOOK1d04h: ephone-1[1]:SpeakerPhoneOnHook1d04h: ephone-1[1]:ONHOOK NO activeline...Related Commands
debug ephone error
To set error debugging for the Cisco IP phone, use the debug ephone error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone error [mac-address mac-address]
no debug ephone error [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone error command cancels debugging at the detail and state level.
If the mac-address keyword is not used, the debug ephone error command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of error debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone error mac-address 0030.94c3.8724EPHONE error debugging is enabledsocket [2] send ERROR 11Skinny Socket [2] retry failureRelated Commands
debug ephone extension-assigner
To display status messages produced by the extension assigner application, use the debug ephone extension-assigner command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone extension-assigner
no debug ephone extension-assigner
Syntax Description
This command has no arguments or keywords.
Command Default
Debug ephone extension-assigner is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays status messages produced by the extension assigner application, including messages related to the functions performed by the following Tcl commands:
•
•
•
Before using this command, you must load the Tcl script for the extension assigner application.
Examples
The following is sample output of extension assigner debugging as the extension assigner application queries phones for their status and issues commands to assign or unassign extension numbers.
*Jun 9 19:08:10.627: ephone_query: inCallID=47, tag=4, ephone_tag=4*Jun 9 19:08:10.627: extAssigner_IsEphoneMacPreset: ephone_tag = 4, ipKeyswitch.max_ephones = 96*Jun 9 19:08:10.627: extAssigner_IsEphoneMacPreset: ephone_ptr->mac_addr_str = 000B46BDE075, MAC_EXT_RESERVED_VALUE = 02EAEAEA0000*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: callID = 47*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: vdbPtr->physical_interface_type (26); CV_VOICE_EFXS (26)*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: vdbPtr->type (6); CC_IF_TELEPHONY (6)*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: htsp->sig_type (26); CV_VOICE_EFXS (26)*Jun 9 19:08:10.627: SkinnyGetActivePhoneIndexFromCallid: dn = 4, chan = 1*Jun 9 19:08:10.627: ephone_query: EXTASSIGNER_RC_SLOT_ASSIGNED_TO_CALLING_PHONE*Jun 9 19:08:22.763: ephone_unassign: inCallID=47, tag=4, ephone_tag=4*Jun 9 19:08:22.763: extAssigner_IsEphoneMacPreset: ephone_tag = 4, ipKeyswitch.max_ephones = 96*Jun 9 19:08:22.763: extAssigner_IsEphoneMacPreset: ephone_ptr->mac_addr_str = 000B46BDE075, MAC_EXT_RESERVED_VALUE = 02EAEAEA000*Jun 9 19:08:22.763: is_ephone_auto_assigned: button-1 dn_tag=4*Jun 9 19:08:22.763: is_ephone_auto_assigned: NO*Jun 9 19:08:22.763: SkinnyGetActivePhoneIndexFromCallid: callID = 47*Jun 9 19:08:22.763: SkinnyGetActivePhoneIndexFromCallid: vdbPtr->physical_interface_type (26); CV_VOICE_EFXS (26)*Jun 9 19:08:22.767: SkinnyGetActivePhoneIndexFromCallid: vdbPtr->type (6); CC_IF_TELEPHONY (6)*Jun 9 19:08:22.767: SkinnyGetActivePhoneIndexFromCallid: htsp->sig_type (26); CV_VOICE_EFXS (26)*Jun 9 19:08:22.767: SkinnyGetActivePhoneIndexFromCallid: dn = 4, chan = 1*Jun 9 19:08:29.795: ephone-4[8]:fStationOnHookMessage: Extension Assigner request restart, cmd=2, new mac=02EAEAEA0004, ephone_tag=4*Jun 9 19:08:30.063: %IPPHONE-6-UNREGISTER_NORMAL: ephone-4:SEP000B46BDE075 IP:5.5.0.1 Socket:8 DeviceType:Phone has unregistered normally.*Jun 9 19:08:30.063: ephone-4[8][SEP000B46BDE075]:extAssigner_assign: new mac=02EAEAEA0004, ephone-tag=4*Jun 9 19:08:30.063: extAssigner_simple_assign: mac=02EAEAEA0004, tag=4*Jun 9 19:08:30.063: ephone_updateCNF: update cnf_file ephone_tag=4*Jun 9 19:08:30.063: extAssigner_assign: restart again (mac=02EAEAEA0004) ephone_tag=4*Jun 9 19:08:30.131: %IPPHONE-6-REG_ALARM: 23: Name=SEP000B46BDE075 Load=8.0(2.0) Last=Reset-Restart*Jun 9 19:08:30.135: %IPPHONE-6-REGISTER_NEW: ephone-7:SEP000B46BDE075 IP:5.5.0.1 Socket:10 DeviceType:Phone has registered.*Jun 9 19:08:30.503: %IPPHONE-6-UNREGISTER_NORMAL: ephone-7:SEP000B46BDE075 IP:5.5.0.1 Socket:10 DeviceType:Phone has unregistered normally.*Jun 9 19:08:43.127: %IPPHONE-6-REG_ALARM: 22: Name=SEP000B46BDE075 Load=8.0(2.0) Last=Reset-Reset*Jun 9 19:08:43.131: %IPPHONE-6-REGISTER: ephone-7:SEP000B46BDE075 IP:5.5.0.1 Socket:13 DeviceType:Phone has registered.Related Commands
debug ephone state
Sets state debugging for Cisco IP phones.
debug voip application script
Displays status messages produced by voice over IP application scripts.
debug ephone keepalive
To set keepalive debugging for the Cisco IP phone, use the debug ephone keepalive command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone keepalive [mac-address mac-address]
no debug ephone keepalive [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone keepalive command sets keepalive debugging.
If the mac-address keyword is not used, the debug ephone keepalive command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of the keepalive status for the Cisco IP phone with MAC address 0030.94C3.E1A8:
Router# debug ephone keepalive mac-address 0030.94c3.E1A8EPHONE keepalive debugging is enabled for phone 0030.94C3.E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: Skinny Checking for stale sockets1d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: Skinny active socket list (3/96): 1 2 4Related Commands
debug ephone loopback
To set debugging for loopback calls, use the debug ephone loopback command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone loopback [mac-address mac-address]
no debug ephone loopback [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone loopback command sets debugging for incoming and outgoing calls on all loopback-dn pairs or on the single loopback-dn pair that is associated with the IP phone that has the MAC address specified in this command.
If you enable the debug ephone loopback command and the debug ephone pak command at the same time, the output displays packet debug output for the voice packets that are passing through the loopback-dn pair.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with that Cisco IP phone.
Examples
The following example contains two excerpts of output for a call that is routed through a loopback. The first excerpt is output from the show running-config command and displays the loopback configuration used for this example. The second excerpt is output from the debug ephone loopback command.
Router# show running-config...ephone-dn 14number 1514!!ephone-dn 42number 17181..loopback-dn 43 forward 4no huntstop!!ephone-dn 43number 19115..loopback-dn 42 forward 4!...A loopback call is started. An incoming call to 1911514 (ephone-dn 43) uses the loopback pair of ephone-dns to become an outgoing call to extension 1514. The number in the outgoing call has only four digits because the loopback-dn command specifies forwarding of four digits. The outgoing call uses ephone-dn 42, which is also specified in the loopback-dn command under ephone-dn 43. When the extension at 1514 rings, the following debug output is displayed:
Router# debug ephone loopbackMar 7 00:57:25.376:Pass processed call info to special DN 43 chan 1Mar 7 00:57:25.376:SkinnySetCallInfoLoopback DN 43 state IDLE to DN 42 state IDLEMar 7 00:57:25.376:Called Number = 1911514 Called Name =Mar 7 00:57:25.376:Calling Number = 8101 Calling Name =orig Called Number =Copy Caller-ID info from Loopback DN 43 to DN 42Mar 7 00:57:25.376:DN 43 Forward 1514Mar 7 00:57:25.376:PredictTarget match 1514 DN 14 is idleMar 7 00:57:25.380:SkinnyUpdateLoopbackState DN 43 state RINGING calledDn -1Mar 7 00:57:25.380:Loopback DN 42 state IDLEMar 7 00:57:25.380:Loopback DN 43 calledDN -1 callingDn -1 G711Ulaw64kMar 7 00:57:25.380:SkinnyUpdateLoopbackState DN 43 to DN 42 signal OFFHOOKMar 7 00:57:25.380:SetDnCodec Loopback DN 43 codec 4:G711Ulaw64k vad 0 size 160Mar 7 00:57:25.380:SkinnyDnToneLoopback DN 42 state SIEZE to DN 43 state RINGINGMar 7 00:57:25.380:TONE ON DtInsideDialToneMar 7 00:57:25.380:SkinnyDnToneLoopback called number = 1911514Mar 7 00:57:25.380:DN 43 Forward 1514Mar 7 00:57:25.380:DN 42 from 43 Dial 1514Mar 7 00:57:25.384:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGINGMar 7 00:57:25.384:TONE OFFMar 7 00:57:25.384:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGINGMar 7 00:57:25.384:TONE OFFMar 7 00:57:25.384:SkinnyUpdateLoopbackState DN 42 state ALERTING calledDn -1Mar 7 00:57:25.384:Loopback DN 43 state RINGINGMar 7 00:57:25.384:Loopback Alerting DN 42 calledDN -1 callingDn -1 G711Ulaw64kMar 7 00:57:25.388:ephone-5[7]:DisplayCallInfo incoming callMar 7 00:57:25.388:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGINGMar 7 00:57:25.388:TONE ON DtAlertingToneMar 7 00:57:25.388:SkinnyDnToneLoopback DN 42 to DN 43 deferred alerting by DtAlertingToneMar 7 00:57:25.388:EFXS_STATE_ONHOOK_RINGING already done for DN 43 chan 1Mar 7 00:57:25.388:Set prog_ind 0 for DN 42 chan 1...When extension 1514 answers the call, the following debug output is displayed:
...Mar 7 00:57:32.158:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGINGMar 7 00:57:32.158:TONE OFFMar 7 00:57:32.158:dn_support_g729 true DN 42 chan 1 (loopback)Mar 7 00:57:32.158:SetDnCodec Loopback DN 43 codec 4:G711Ulaw64k vad 0 size 160Mar 7 00:57:32.158:SkinnyUpdateLoopbackState DN 42 state CALL_START calledDn 14Mar 7 00:57:32.158:Loopback DN 43 state RINGINGMar 7 00:57:32.158:SkinnyUpdateLoopbackState DN 42 to DN 43 deferred alerting by CALL_START already sentMar 7 00:57:32.158:SetDnCodec reassert defer_start for DN 14 chan 1Mar 7 00:57:32.158:Delay media until loopback DN 43 is readyMar 7 00:57:32.158:SkinnyUpdateLoopbackCodec check for DN 14 chan 1 from DN 42 loopback DN 43Mar 7 00:57:32.158:SkinnyUpdateLoopbackCodec DN chain is 14 1, other=42, lb=43, far=-1 1, final=43 1Mar 7 00:57:32.158:SkinnyUpdateLoopbackCodec DN 14 chan 1 DN 43 chan 1 codec 4 matchMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 42 state CONNECTED calledDn 14Mar 7 00:57:32.162:Loopback DN 43 state RINGINGMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 42 to DN 43 signal ANSWERMar 7 00:57:32.162:Loopback DN 42 calledDN 14 callingDn -1 G711Ulaw64kMar 7 00:57:32.162:Loopback DN 43 calledDN -1 callingDn -1 incoming G711Ulaw64kMar 7 00:57:32.162:ephone-5[7][SEP000DBDBEF37D]:refreshDisplayLine for line 1 DN 14 chan 1Mar 7 00:57:32.162:dn_support_g729 true DN 43 chan 1 (loopback)Mar 7 00:57:32.162:SetDnCodec Loopback DN 42 codec 4:G711Ulaw64k vad 0 size 160Mar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 state CALL_START calledDn -1Mar 7 00:57:32.162:Loopback DN 42 state CONNECTEDMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 has defer_dn 14 chan 1 setMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 has defer_dn 14 chan 1:-invoke SkinnyOpenReceiveMar 7 00:57:32.162:SkinnyUpdateLoopbackCodec check for DN 14 chan 1 from DN 42 loopback DN 43Mar 7 00:57:32.162:SkinnyUpdateLoopbackCodec DN chain is 14 1, other=42, lb=43, far=-1 1, final=43 1Mar 7 00:57:32.162:SkinnyUpdateLoopbackCodec DN 14 chan 1 DN 43 chan 1 codec 4 matchMar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 state CALL_START calledDn -1Mar 7 00:57:32.162:Loopback DN 42 state CONNECTEDMar 7 00:57:32.454:SkinnyGetDnAddrInfo DN 43 LOOPBACKupdate media address to 10.0.0.6 25390 from DN 14Mar 7 00:57:33.166:ephone-5[7]:DisplayCallInfo incoming call...When the called extension, 1514, goes back on-hook, the following debug output is displayed:
...Mar 7 00:57:39.224:Loopback DN 42 disc reason 16 normal state CONNECTEDMar 7 00:57:39.224:SkinnyUpdateLoopbackState DN 42 state CALL_END calledDn -1Mar 7 00:57:39.224:Loopback DN 43 state CONNECTEDMar 7 00:57:39.224:SkinnyUpdateLoopbackState DN 42 to DN 43 signal ONHOOKMar 7 00:57:39.236:SkinnyDnToneLoopback DN 42 state IDLE to DN 43 state IDLEMar 7 00:57:39.236:TONE OFFMar 7 00:57:39.236:SkinnyDnToneLoopback DN 43 state IDLE to DN 42 state IDLEMar 7 00:57:39.236:TONE OFFTable 83 describes the significant fields shown in the display.
Related Commands
debug ephone message
To enable message tracing between ephones, use the debug ephone message command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone message [detail]
no debug ephone message
Syntax Description
detail
(Optional) Displays signaling connection control protocol (SCCP) messages sent and received between ephones in the Cisco Unified CallManager Express (Cisco Unified CME) system.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
The debug ephone message command enables message tracing between ephones.
The debug ephone command debugs all ephones associated with a Cisco Unified CME router.
You can enable or disable debugging on any number of ephones. To see the ephones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a ephone, the debug output is displayed for the directory numbers associated with the ephone.
Examples
The following is sample output for the debug ephone message command for ephones:
Router# debug ephone messageEPHONE skinny message debugging is enabled*Jul 17 12:12:54.883: Received message from phone 7, SkinnyMessageID = StationKeepAliveMessageID*Jul 17 12:12:54.883: Sending message to phone 7, SkinnyMessageID = StationKeepAliveAckMessageIDThe following command disables ephone message debugging:
Router# no debug ephone messageEPHONE skinny message debugging is disabledRelated Commands
debug ephone moh
To set debugging for music on hold (MOH), use the debug ephone moh command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone moh [mac-address mac-address]
no debug ephone moh [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Always use the no moh command before modifying or replacing the MOH file in Flash memory.
When a configuration using the multicast moh command is used and the debug ephone moh command is enabled, if you delete or modify the MOH file in the router's Flash memory, the debug output can be excessive and can flood the console. The multicast MOH configuration should be removed before using the no moh command when the debug ephone moh command is enabled.
Examples
The following sample output shows MOH activity prior to the first MOH session. Note that if you enable multicast MOH, that counts as the first session.
Router# debug ephone mohMar 7 00:52:33.817:MOH AU fileMar 7 00:52:33.817:skinny_open_moh_play set type to 3Mar 7 00:52:33.825: 2E73 6E64 0000 0018 0007 3CCA 0000 0001Mar 7 00:52:33.825: 0000 1F40 0000 0001 FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFFMar 7 00:52:33.825:Mar 7 00:52:33.825:AU file processing Found .sndMar 7 00:52:33.825:AU file data start at 24 end at 474338Mar 7 00:52:33.825:AU file codec Media_Payload_G711Ulaw64kMar 7 00:52:33.825:MOH read file header type AU start 24 end 474338Mar 7 00:52:33.825:MOH pre-read block 0 at write-offset 0 from 24Mar 7 00:52:33.833:MOH pre-read block 1 at write-offset 8000 from 8024Mar 7 00:52:33.845:Starting read server with play-offset 0 write-offset 16000Table 84 describes the significant fields shown in the display.
Related Commands
moh (telephony-service)
Generates an audio stream from a file for MOH in a Cisco CME system.
multicast moh
Uses the MOH audio stream as a multicast source in a Cisco CME system.
debug ephone mwi
To set message waiting indication (MWI) debugging for the Cisco IOS Telephony Service router, use the debug ephone mwi command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone mwi
no debug ephone mwi
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone mwi command sets message waiting indication debugging for the Cisco IOS Telephony Service router. Because the MWI protocol activity is not specific to any individual Cisco IP phone, setting the MAC address keyword qualifier for this command is not useful.
Note
Examples
The following is sample output of the message waiting indication status for the Cisco IOS Telephony Service router:
Router# debug ephone mwiRelated Commands
debug ephone pak
To provide voice packet level debugging and to print the contents of one voice packet in every 1024 voice packets, use the debug ephone pak command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone pak [mac-address mac-address]
no debug ephone pak [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone pak command provides voice packet level debugging and prints the contents of one voice packet in every 1024 voice packets.
If the mac-address keyword is not used, the debug ephone pak command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of packet debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone pak mac-address 0030.94c3.8724EPHONE packet debugging is enabled for phone 0030.94c3.872401:29:14: ***ph_xmit_ephone DN 3 tx_pkts 5770 dest=10.2.1.1 orig len=32pakcopy=0 discards 27 ip_enctype 0 0 last discard: unsupported payload type01:29:14: to_skinny_duration 130210 offset -30 last -40 seq 0 adj 001:29:14: IP: 45B8 003C 0866 0000 3F11 3F90 2800 0001 0A02 010101:29:14: TTL 63 TOS B8 prec 501:29:14: UDP: 07D0 6266 0028 000001:29:14: sport 2000 dport 25190 length 40 checksum 001:29:14: RTP: 8012 16AF 9170 6409 0E9F 000101:29:14: is_rtp:1 is_frf11:0 vlen:0 delta_t:160 vofr1:0 vofr2:0scodec:11 rtp_bits:8012 rtp_codec:18 last_bad_payload 1901:29:14: vencap FAILED01:29:14: PROCESS SWITCH01:29:15: %SYS-5-CONFIG_I: Configured from console by console01:29:34: ***SkinnyPktIp DN 3 10.2.1.1 to 40.0.0.1 pkts 4880 FAST sw01:29:34: from_skinny_duration 15091001:29:34: nw 3BBC2A8 addr 3BBC2A4 mac 3BBC2A4 dg 3BBC2C4 dgs 2A01:29:34: MAC: 1841 080001:29:34: IP: 45B8 0046 682E 0000 3E11 E0BD 0A02 0101 2800 000101:29:34: TTL 62 TOS B8 prec 501:29:34: UDP: 6266 07D0 0032 000001:29:34: sport 25190 dport 2000 length 50 checksum 001:29:34: RTP: 8012 55FF 0057 8870 3AF4 C39401:29:34: RTP: rtp_bits 8012 seq 55FF ts 578870 ssrc 3AF4C39401:29:34: PAYLOAD:01:29:34: 1409 37C9 54DE 449C 3B42 0446 3AAB 182E01:29:34: 56BC 5184 58E5 56D3 13BE 44A7 B8C401:29:34:01:29:37: ***ph_xmit_ephone DN 3 tx_pkts 6790 dest=10.2.1.1 orig len=32pakcopy=0 discards 31 ip_enctype 0 0 last discard: unsupported payload type01:29:37: to_skinny_duration 153870 offset -150 last -40 seq 0 adj 001:29:37: IP: 45B8 003C 0875 0000 3F11 3F81 2800 0001 0A02 010101:29:37: TTL 63 TOS B8 prec 501:29:37: UDP: 07D0 6266 0028 000001:29:37: sport 2000 dport 25190 length 40 checksum 001:29:37: RTP: 8012 1AAF 9173 4769 0E9F 000101:29:37: is_rtp:1 is_frf11:0 vlen:0 delta_t:160 vofr1:0 vofr2:0Related Commands
debug ephone qov
To display quality of voice (QOV) statistics for calls when preset limits are exceeded, use the debug ephone qov command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone qov [mac-address mac-address]
no debug ephone qov [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Once enabled, the debug ephone qov command produces output only when the QOV statistics reported by phones exceed preset limits. Phones are polled every few seconds for QOV statistics on VoIP calls only, not on local PSTN calls. An output report is produced when limits are surpassed for either or both of the following:
•
•
To receive a QOV report at the end of each call regardless of whether the QOV limits have been exceeded, enable the debug ephone alarm command in addition to the debug ephone qov command.
The debug ephone statistics command displays the raw statistics that are polled from phones and used to generate QOV reports.
Examples
The following sample output describes QOV statistics for a call on ephone 5:
Router# debug ephone qovMar 7 00:54:57.329:ephone-5[7]:QOV DN 14 chan 1 (1514) ref 4 called=1514 calling=8101Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:Lost 91 Jitter 0 Latency 0Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:previous Lost 0 Jitter 0 Latency 0Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:Router sent 1153 pkts, current phone got 1141received by all (shared) phones 0Mar 7 00:54:57.329:ephone-5[7]:worst jitter 0 worst latency 0Mar 7 00:54:57.329:ephone-5[7]:Current phone sent 1233 packetsMar 7 00:54:57.329:ephone-5[7]:Signal Level to phone 3408 (-15 dB) peak 3516 (-15 dB)Table 85 describes the significant fields shown in the display.
Related Commands
debug ephone alarm
Displays alarm messages for IP phones.
debug ephone statistics
Displays call statistics for IP phones.
debug ephone raw
To provide raw low-level protocol debugging display for all Skinny Client Control Protocol (SCCP) messages, use the debug ephone raw command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone raw [mac-address mac-address]
no debug ephone raw [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone raw command provides raw low-level protocol debug display for all SCCP messages. The debug display provides byte level display of Skinny TCP socket messages.
If the mac-address keyword is not used, the debug ephone raw command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of raw protocol debugging for the Cisco IP phone with MAC address 0030.94c3.E1A8:
Router# debug ephone raw mac-address 0030.94c3.E1A8EPHONE raw protocol debugging is enabled for phone 0030.94C3.E1A81d05h: skinny socket received 4 bytes on socket [1]0 0 0 01d05h:1d05h: SkinnyMessageID = 01d05h: skinny send 4 bytes4 0 0 0 0 0 0 0 0 1 0 01d05h: socket [1] sent 12 bytes OK (incl hdr) for ephone-(1)1d06h: skinny socket received 4 bytes on socket [1]0 0 0 01d06h:1d06h: SkinnyMessageID = 01d06h: skinny send 4 bytes4 0 0 0 0 0 0 0 0 1 0 01d06h: socket [1] sent 12 bytes OK (incl hdr) for ephone-(1)Related Commands
debug ephone register
To set registration debugging for the Cisco IP phone, use the debug ephone register command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone register [mac-address mac-address]
no debug ephone register [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone register command sets registration debugging for the Cisco IP phones.
If the mac-address keyword is not used, the debug ephone register command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of registration debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone register mac-address 0030.94c3.8724Ephone registration debugging is enabled1d06h: New Skinny socket accepted [1] (2 active)1d06h: sin_family 2, sin_port 50778, in_addr 10.1.0.211d06h: skinny_add_socket 1 10.1.0.21 507781d06h: ephone-(1)[1] StationRegisterMessage (2/3/12) from 10.1.0.211d06h: ephone-(1)[1] Register StationIdentifier DeviceName SEP003094C3E1A81d06h: ephone-(1)[1] StationIdentifier Instance 1 deviceType 71d06h: ephone-1[-1]:stationIpAddr 10.1.0.211d06h: ephone-1[-1]:maxStreams 01d06h: ephone-(1) Allow any Skinny Server IP address 10.1.0.6...1d06h: ephone-1[1]:RegisterAck sent to ephone 1: keepalive period 30.Related Commands
debug ephone sccp-state
To set debugging for the SCCP call state, use the debug ephone sccp-state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone sccp-state [mac-address mac-address]
no debug ephone sccp-state [mac-address mac-address]
Syntax Description
Command Default
Debugging is not enabled for SCCP state.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
This command is used with Cisco Unified CallManager Express (Cisco Unified CME).
This command outputs only the debug messages that correspond to SCCP messages sent to IP phones to indicate the SCCP phone call state, such as RingIn, OffHook, Connected, and OnHook. These debug messages are also included in the output for the debug ephone detail command among other information.
Examples
The following example sets SCCP state debugging for one Cisco Unified CME phone with the MAC address of 678B.AEF9.DAB5.
Router# debug ephone sccp-state mac-address 678B.AEF9.DAB5EPHONE SCCP state message debugging is enabledfor ephones 000B.BEF9.DFB5*Mar 8 06:38:45.863: %ISDN-6-CONNECT: Interface Serial2/0/0:22 is now connected to 4085254871 unknown*Mar 8 06:38:50.487: ephone-2[13]:SetCallState line 4 DN 60(60) chan 1 ref 100 TsRingIn *Mar 8 06:38:52.399: ephone-2[13]:SetCallState line 4 DN 60(-1) chan 1 ref 100 TsOffHook *Mar 8 06:38:52.399: ephone-2[13]:SetCallState line 4 DN 60(-1) chan 1 ref 100 TsConnected*Mar 8 06:38:58.415: %ISDN-6-CONNECT: Interface Serial2/0/0:22 is now connected to 4085254871 unknown*Mar 8 06:38:59.963: ephone-2[13]:SetCallState line 4 DN 60(-1) chan 1 ref 100 TsOnHook *Mar 8 06:38:59.975: %ISDN-6-DISCONNECT: Interface Serial2/0/0:22 disconnected from 4085254871 , call lasted 7 secondsRelated Commands
debug ephone detail
Sets detail debugging for one or all Cisco Unified IP phones.
debug ephone state
To set state debugging for the Cisco IP phone, use the debug ephone state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone state [mac-address mac-address]
no debug ephone state [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone state command sets state debugging for the Cisco IP phones.
If the mac-address keyword is not used, the debug ephone state command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of state debugging for the Cisco IP phone with MAC address 0030.94c3.E1A8:
Router# debug ephone state mac-address 0030.94c3.E1A8EPHONE state debugging is enabled for phone 0030.94C3.E1A81d06h: ephone-1[1]:OFFHOOK1d06h: ephone-1[1]:SIEZE on activeline 01d06h: ephone-1[1]:SetCallState line 1 DN 1 TsOffHook1d06h: ephone-1[1]:Skinny-to-Skinny call DN 1 to DN 2 instance 11d06h: ephone-1[1]:SetCallState line 1 DN 1 TsRingOut1d06h: ephone-1[1]:Call Info DN 1 line 1 ref 158 called 5002 calling 50011d06h: ephone-1[1]: Jane calling1d06h: ephone-1[1]: Jill1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsRingIn1d06h: ephone-1[1]:Call Info DN 2 line 3 ref 159 called 5002 calling 50011d06h: ephone-1[1]: Jane calling1d06h: ephone-1[1]: Jill1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsCallRemoteMultiline1d06h: ephone-1[1]:SetCallState line 1 DN 1 TsConnected1d06h: ephone-1[1]:OpenReceive DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 801d06h: ephone-1[1]:OpenReceiveChannelAck 1.2.172.21 port=240101d06h: ephone-1[1]:StartMedia 1.2.172.22 port=246121d06h: DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 801d06h: ephone-1[1]:CloseReceive1d06h: ephone-1[1]:StopMedia1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsOnHook1d06h: ephone-1[1]:SetCallState line 1 DN 1 TsOnHook1d06h: ephone-1[1]:SpeakerPhoneOnHook1d06h: ephone-1[1]:ONHOOK1d06h: ephone-1[1]:SpeakerPhoneOnHook1d06h: SkinnyReportDnState DN 1 ONHOOKRelated Commands
debug ephone statistics
To set call statistics debugging for the Cisco IP phone, use the debug ephone statistics command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone statistics [mac-address mac-address]
no debug ephone statistics [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone statistics command provides a debug monitor display of the periodic messages from the Cisco IP phone to the router. These include transmit-and-receive packet counts and an estimate of drop packets. The call statistics can also be displayed for live calls using the show ephone command.
If the mac-address keyword is not used, the debug ephone statistics command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
You can enable or disable debugging on any number of Cisco IP phones. To see the Cisco IP phones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for the directory numbers associated with the Cisco IP phone.
Examples
The following is sample output of statistics debugging for the Cisco IP phone with MAC address 0030.94C3.E1A8:
Router# debug ephone statistics mac-address 0030.94C3.E1A8EPHONE statistics debugging is enabled for phone 0030.94C3.E1A81d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 2 call ref 1631d06h: ephone-1[1]:GetCallStats line 1 ref 162 DN 1: 50011d06h: ephone-1[1]:Call Stats for line 1 DN 1 5001 ref 1621d06h: ephone-1[1]:TX Pkts 0 bytes 0 RX Pkts 0 bytes 01d06h: ephone-1[1]:Pkts lost 4504384 jitter 0 latency 01d06h: ephone-1[1]:Src 0.0.0.0 0 Dst 0.0.0.0 0 bytes 80 vad 0 G711Ulaw64k1d06h: ephone-1[1]:GetCallStats line 1 ref 162 DN 1: 50011d06h: STATS: DN 1 Packets Sent 01d06h: STATS: DN 2 Packets Sent 01d06h: ephone-1[1]:Call Stats found DN -1 from Call Ref 1621d06h: ephone-1[1]:Call Stats for line 0 DN -1 5001 ref 1621d06h: ephone-1[1]:TX Pkts 275 bytes 25300 RX Pkts 275 bytes 253001d06h: ephone-1[1]:Pkts lost 0 jitter 0 latency 0Related Commands
debug ephone video
To set video debugging for ephones, use the debug ephone video command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone video
no debug ephone video
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging is disabled for ephone video.
Command Modes
Privileged EXEC
Command History
12.4(4)XC
This command was introduced.
12.4(9)T
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
The debug ephone video command sets ephone video traces, which provide information about different video states for the call, including video capabilities selection, start, and stop.
The debug ephone command debugs all ephones that are registered to the Cisco Unified CallManager Express (Cisco Unified CME) system.
You can enable or disable debugging on any number of ephones. To see the ephones that have debugging enabled, enter the show ephone command and look at the debug field in the output. When debugging is enabled for a ephone, the debug output is displayed for the directory numbers associated with the ephone.
Examples
The following is sample output for the debug ephone video command for ephones:
Router# debug ephone video*Mar 13 16:10:02.703: SkinnyVideoCodecMatch_Caps2Caps: match capability: tx_idxcap = 4, tx_idxpref = 3,*Mar 13 16:10:02.703: rx_idxcap = 0, rx_idxpref = 0, videoBitRate = 7040 tx_mpi = 1*Mar 13 16:10:04.711: ephone-19[1][SEPFFFA00000019]:checkToOpenMultiMedia: dn=19, chan=1*Mar 13 16:10:04.711: ephone-19[1]:skinnyDP[19].s2s = 0*Mar 13 16:10:04.711: ephone-19[1]:s2s is not set - hence not video capable*Mar 13 16:10:04.719: ephone-19[1][SEPFFFA00000019]:SkinnyStartMultiMediaTransmission: chan 1 dn 19*Mar 13 16:10:04.723: ephone-19[1]:Accept OLC and open multimedia channel*Mar 13 16:10:04.723: ephone-19[1][SEPFFFA00000019]:SkinnyOpenMultiMediaReceiveChannel: dn 19 chan 1*Mar 13 16:10:04.967: ephone-19[1][SEPFFFA00000019]:fStationOpenReceiveChannelAckMessage: MEDIA_DN 19 MEDIA_CHAN 1*Mar 13 16:10:04.967: ephone-19[1]:fStationOpenMultiMediaReceiveChannelAckMessage:*Mar 13 16:10:04.967: ephone-19[1]:Other_dn == -1sk3745-2#*Mar 13 16:10:14.787: ephone-19[1]:SkinnyStopMedia: Stop Multimedia*Mar 13 16:10:14.787: ephone-19[1][SEPFFFA00000019]:SkinnyCloseMultiMediaReceiveChannel: passThruPartyID = 0, callReference = 23*Mar 13 16:10:14.787: ephone-19[1]:SkinnyStopMultiMediaTransmission: line 1 chan 1 dn 19Related Commands
debug ephone vm-integration
To display pattern manipulation information used for integration with voice-mail applications, use the debug ephone vm-integration command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug ephone vm-integration [mac-address mac-address]
no debug ephone vm-integration [mac-address mac-address]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays the voice-mail integration patterns that were created using the pattern commands in vm-integration configuration mode. The patterns are used to forward calls to a voice-mail number that is set with the voicemail command.
If you do not specify the mac-address keyword, the debug ephone vm-integration command debugs all Cisco IP phones that are registered to the router. To remove debugging for Cisco IP phones, enter the no form of this command with the mac-address keyword.
Examples
The following sample output shows information for the vm-integration tokens that have been defined:
Router# debug ephone vm-integration*Jul 23 15:38:03.294:ephone-3[3]:StimulusMessage 15 (1) From ephone 2*Jul 23 15:38:03.294:ephone-3[3]:Voicemail access number pattern check*Jul 23 15:38:03.294:SkinnyGetCallState for DN 3 chan 1 IDLE*Jul 23 15:38:03.294:called DN -1 chan 1, calling DN -1 chan 1 phone -1 s2s:0*Jul 23 15:38:03.294:dn number for dn 3 is 19003*Jul 23 15:38:03.294:Updated number for token 1 is 19003*Jul 23 15:38:03.294:CDN number for dn 3 is*Jul 23 15:38:03.294:Updated number for token 2 is*Jul 23 15:38:03.294:Updated number for token 0 is*Jul 23 15:38:03.294:Update is 219003**Jul 23 15:38:03.294:New Voicemail number is 19101219003*Table 86 describes the significant fields shown in the display.
Related Commands
debug errors
To display errors, use the debug errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug errors
no debug errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug errors command:
Router# debug errors(2/0): Encapsulation error, link=7, host=836CA86D.(4/0): VCD#7 failed to echo OAM. 4 triesThe first line of output indicates that a packet was routed to the interface, but no static map was set up to route that packet to the proper virtual circuit.
The second line of output shows that an OAM F5 (virtual circuit) cell error occurred.
debug eswilp
To enable debugging of Ethernet switch network module features, use the debug eswilp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eswilp {dot1x | filtermgr | fltdrv | igmp | port-driver | power-supply | span | switch-pm}
no debug eswilp {dot1x | filtermgr | fltdrv | igmp | port-driver | power-supply | span | switch-pm}
Syntax Description
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug eswilp command is the same as the no debug eswilp command.
Examples
The following example shows debugging messages for the IGMP snooping services on the Ethernet switch network module being displayed:
Router# debug eswilp igmpRelated Commands
show debugging
Displays information about the types of debugging that are enabled.
debug ethernet lmi
To enable debugging of Ethernet local management interface (LMI) messages on all interfaces or on a specified interface, use the debug ethernet lmi command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ethernet lmi {all | errors | events | packets} [interface type number]
no debug ethernet lmi {all | errors | events | packets} [interface type number]
Syntax Description
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When you use the all keyword, keep in mind how many interfaces support Ethernet LMI. Some messages may be lost if many interfaces are supported.
Use of the errors keyword enables debugging of Ethernet LMI errors such as invalid messages; for example, unexpected information element (IE) and mandatory IE missing.
Use of the events keyword enables debugging of Ethernet LMI events such as status changes, timeouts, and messages received.
Use of the packets keyword enables debugging of decoded Ethernet LMI packets.
The output from this command is a log of activity. Use this command to troubleshoot Ethernet LMI in your network.
Examples
The following example output from the debug ethernet lmi all command shows event and packet messages:
Router# debug ethernet lmi allEthernet LMI errors debugging is onEthernet LMI packets debugging is onEthernet LMI events debugging is onEthernet LMI packets hex debugging is on00:29:32: ELMI Et0/0 EVENT: ce_event: State 0x0, Event 0x400:29:32: ELMI Et0/0 EVENT: Old State=0x0, Event=0x4, New State=0x200:29:32: ELMI Et0/0 EVENT: Updated Stat Type: ETHER_LMI_ST_LMSG_SENT00:29:32: ELMI Et0/0 PKT HEX: TX->:0x01750101010202B4B3030500000000040000000000000:29:32: ELMI Et0/0 PACKET: OutgoingProtocol Version : 0x1Message : STATUS ENQ (0x75)Report Type : CheckSequence Number : Snd(0xB4), Rcv(0xB3)Data Instance : Value(0x4)00:29:32: ELMI Et0/0 PKT HEX: RX<-:0x017D0101010202B4B4030500000000040000000000000:29:32: ELMI Et0/0 PACKET: IncomingProtocol Version : 0x1Message : STATUS (0x7D)Report Type : CheckSequence Number : Snd(0xB4), Rcv(0xB4)Data Instance : Value(0x4)00:29:32: ELMI Et0/0 EVENT: ce_event: State 0x2, Event 0x100:29:32: ELMI Et0/0 EVENT: Update seq: current send 0xB4 rcv 0xB300:29:32: ELMI Et0/0 EVENT: Updated Stat Type: ETHER_LMI_ST_LMSG_RCVD00:29:32: ELMI Et0/0 EVENT: Old State=0x2, Event=0x1, New State=0x0The following example output from the debug ethernet lmi all command shows detailed information about the user-network interfaces (UNIs) and Ethernet virtual connections (EVCs) for packet messages.
Router# debug ethernet lmi allEthernet LMI errors debugging is onEthernet LMI packets debugging is onEthernet LMI events debugging is onEthernet LMI packets hex debugging is onJun 16 18:59:49.372: ELMI Gi0/1 PKT HEX: RX<-:0x017D0101000202D30103050000000004Jun 16 18:59:49.372: ELMI Gi0/1 PACKET: IncomingProtocol Version : 0x1Message : STATUS (0x7D)Report Type : FullSequence Number : Snd(0xD3), Rcv(0x1)Data Instance : Value(0x4)UNI : BundleUNI Id : 'uni_sandiego'EVC Status : Evc Ref(0x1), New, ActiveEVC Parameters : Point-to-PointEVC Id : 'EVC_P2P_110'Remote UNI Sum : Cfgd(1), Up(1)EVC Status : Evc Ref(0x2), New, ActiveEVC Parameters : MultiPoint-to-MultiPointEVC Id : 'EVC_MP2MP_101'Remote UNI Sum : Cfgd(2), Up(2)CEVLAN EVC Map : Evc Ref(0x1), Seq(0x1)EVC Map : Num Vlans(1), 110CEVLAN EVC Map : Evc Ref(0x2), Seq(0x1)EVC Map : Num Vlans(1), 101Remote UNI Status : Evc Ref(0x1), Uni Ref(0x26), UpUNI Id o deb al : 'cisco_newyork'Remote UNI Status : Evc Ref(0x2), Uni Ref(0x1D), UpUNI Id : 'uni_newyork'Remote UNI Status : Evc Ref(0x2), Uni Ref(0x96), UpUNI Id : 'miami-detroit'Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: ce_event: State 0x1, Event 0x0Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update seq: current send 0x1 rcv 0x0Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update uni:Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update evc_sts: ref_id: 0x1Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update evc_param: type 0x0Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update evc_idJun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update remote_uni_sum cfgd 1 up 1Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update evc_sts: ref_id: 0x2Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update evc_param: type 0x1Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update evc_idJun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update remote_uni_sum cfgd 2 up 2Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update cevlan_evc_map: ref_id: 0x1 seq#1Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update evc_map: num_vlans 1Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update cevlan_evc_map: ref_id: 0x2 seq# 1Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update evc_map: num_vlans 1Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update remote_uni_det: evc ref_id: 0x1 u6Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update remote_uni_det: evc ref_id: 0x2 uDJun 16 18:59:49.372: ELMI Gi0/1 EVENT: Update remote_uni_det: evc ref_id: 0x2 u6Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: upd_lmi_db: new uni_evc ref 0x1Jun 16 18:59:49.372: ELMI Gi0/1 EVENT: upd_lmi_db: new uni_evc ref 0x2Jun 16 18:59:49.372: %ETHER_LMI-6-MISMATCHED_VLAN_NOT_CONFIGURED: VLAN 101,110 1Jun 16 18:59:49.372: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthnJun 16 18:59:49.376: ELMI Gi0/1 EVENT: Update di: current 0x0 rcvd 0x4Jun 16 18:59:49.376: ELMI Gi0/1 EVENT: Old State=0x1, Event=0x0, New State=0x0Jun 16 18:59:49.376: ELMI Gi0/1 EVENT: Updated Stat Type: ETHER_LMI_ST_LFULL_MSDJun 16 18:59:50.100: %SYS-5-CONFIG_I: Configured from console by consoleJun 16 18:59:59.376: ELMI Gi0/1 EVENT: ce_event: State 0x0, Event 0x4Jun 16 18:59:59.376: ELMI Gi0/1 EVENT: Old State=0x0, Event=0x4, New State=0x2Jun 16 18:59:59.376: ELMI Gi0/1 EVENT: Updated Stat Type: ETHER_LMI_ST_LMSG_SENTThe following example shows output of the debug ethernet lmi all interface command for interface Ethernet 0/0.Router# debug ethernet lmi all interface ethernet 0/0Ethernet LMI errors debugging is on for Ethernet0/0Ethernet LMI packets debugging is on for Ethernet0/0Ethernet LMI events debugging is on for Ethernet0/0Ethernet LMI packets hex debugging is on for Ethernet0/000:45:14: ELMI Et0/0 EVENT: ce_event: State 0x0, Event 0x400:45:14: ELMI Et0/0 EVENT: Old State=0x0, Event=0x4, New State=0x200:45:14: ELMI Et0/0 EVENT: Updated Stat Type: ETHER_LMI_ST_LMSG_SENT00:45:14: ELMI Et0/0 PKT HEX: TX->:0x017501010102021312030500000000040000000000000:45:14: ELMI Et0/0 PACKET: OutgoingProtocol Version : 0x1Message : STATUS ENQ (0x75)Report Type : CheckSequence Number : Snd(0x13), Rcv(0x12)Data Instance : Value(0x4)00:45:14: ELMI Et0/0 PKT HEX: RX<-:0x017D01010102021313030500000000040000000000000:45:14: ELMI Et0/0 PACKET: IncomingProtocol Version : 0x1Message : STATUS (0x7D)Report Type : CheckSequence Number : Snd(0x13), Rcv(0x13)Data Instance : Value(0x4)00:45:14: ELMI Et0/0 EVENT: ce_event: State 0x2, Event 0x100:45:14: ELMI Et0/0 EVENT: Update seq: current send 0x13 rcv 0x1200:45:14: ELMI Et0/0 EVENT: Updated Stat Type: ETHER_LMI_ST_LMSG_RCVD00:45:14: ELMI Et0/0 EVENT: Old State=0x2, Event=0x1, New State=0x0debug ethernet oam
To enable all Ethernet operations, administration, and maintenance (OAM) debugging, use the debug ethernet oam command in privileged EXEC mode. To disable Ethernet OAM debuging, use the no form of this command.
debug ethernet oam {all | config | ha | link-monitor | loopback | packet {decode | rx | tx} | sm}
no debug ethernet oam {all | config | ha | link-monitor | loopback | packet {decode | rx | tx} | sm}
Syntax Description
Command Default
All Ethernet OAM debug commands are enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When you use the all keyword, keep in mind the number of interfaces supporting Ethernet OAM. If many interfaces are supported, some messages may be lost and system performance can degrade.
The ha keyword is not available in Cisco IOS Release 12.4(15)T.
The output from this command is a log of activity. Use this command to troubleshoot Ethernet OAM in your network.s
Examples
The following example shows output of the debug ethernet oam all command:
Router# debug ethernet oam all*Aug 17 14:00:53.732: ether_oam_port Gi2/9: during state INACTIVE,got event 3(link_up)*Aug 17 14:00:53.732: @@@ ether_oam_port Gi2/9: INACTIVE -> FAULT*Aug 17 14:00:53.732: ether_oam_port Gi2/9: idle during state FAULT*Aug 17 14:00:53.732: @@@ ether_oam_port Gi2/9: FAULT -> FAULT2*Aug 17 14:00:53.732: ether_oam_port Gi2/9: during state FAULT2, gotevent 6(mode_active)*Aug 17 14:00:53.732: @@@ ether_oam_port Gi2/9: FAULT2 -> ACTIVE_SEND_LOCAL*Aug 17 14:00:54.212: EOAM RX PAK(Gi2/9):*Aug 17 14:00:54.212: 03 00 08 00 01 10 01 00 00 00 0D 05 DC 00 00 0C *Aug 17 14:00:54.212: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00*Aug 17 14:00:54.212: 00 00 00 00 00 00 00 00*Aug 17 14:00:54.212: ether_oam_port Gi2/9: during stateSEND_LOCAL_REMOTE, got event 8(local_satisfied)1w5d: %ETHERNET_OAM-6-ENTER_SESSION: The client on interface Gi2/11 has entered the OAM session.*Aug 17 14:00:55.212: EOAM RX PAK(Gi2/9):*Aug 17 14:00:55.212: 03 00 50 00 01 10 01 00 00 00 0D 05 DC 00 00 0C*Aug 17 14:00:55.212: 00 00 00 SYMPRD w=104857600 lt=1 ht=0elapsed_time=1032(ms) rx_sym=1000000000 err_sym=0 *Aug 17 14:00:55.740: EOAM LM(Gi2/9): FRM w=1 lt=1 ht=0 t_frm=0 err_frm=0*Aug 17 14:00:55.740: EOAM LM(Gi2/9): FRMPRD w=10000000 lt=1 ht=0 t_frm=1 err_frm=0*Aug 17 14:00:55.740: EOAM LM(Gi2/9): w=1 lt=10 ht=0 err_frm=0*Aug 17 14:00:55.740: EOAM LM(Gi2/9): w=1 lt=10 ht=0 err_frm=0*Aug 17 14:00:55.832: EOAM TX PAK(Gi2/9):*Aug 17 14:00:55.832: 03 00 50 00 0 1 10 01 00 00 00 0D 05 DC 00 00 0C*Aug 17 14:00:55.832: 00 00 00 01 02 10 01 00 00 00 0D 05 DC 00 00 0C *Aug 17 14:00:55.832: 00 00 00 01 *Aug 17 14:00:55.832: EOAM TX PAK(Gi2/9): 00 00 00 0D 05 DC 00 00 0C*Aug 17 14:00:56.212: 00 00 00 01 02 10 01 00 00 00 0D 05 DC 00 00 0C*Aug 17 14:00:56.212: 00 00 00 01 00 00 00 00 00 00 00 00 00 00*Aug 17 14:00:56.212: EOAM RX PAK(Gi2/9): infotlv w/ same revision *Aug 17 14:00:56.820: EOAM LM(Gi2/9): SYMPRD w=104857600 lt=1 ht=0elapsed_time=1000(ms) rx_sym=1000000000 err_sym=0*Aug 17 14:00:56.820: EOAM LM(Gi2/9): FRM w=1 lt=1 ht=0 t_frm=0 err_frm=0*Aug 17 14:00:56.820: EOAM LM(Gi2/9): 05 FRMPRD w=10000000 lt=1 ht=0 t_frm=3 err_frm=0*Aug 17 14:00:57.820: EOAM LM(Gi2/9): w=1 lt=10 ht=0 err_frm=0*Aug 17 14:00:57.820: EOAM LM(Gi2/9): w=1 lt=10 ht=0 err_frm=0*Aug 17 14:00:57.856: EOAM TX PAK(Gi2/9):*Aug 17 14:00:57.856: 03 00 50 00 01 10 01 00 00 00 0D 05 DC 00 00 0C*Aug 17 14:00:57.856: 00 00 00 01 02 10 01 00 00 00 0D 17 14:00:58.212: 05 DC 00 00 0C*Aug 17 14:00:57.856: 00 00 00 01*Aug 17 14:00:57.856: EOAM TX PAK(Gi2/9): sent OAMPDU w/ op=0*Aug 17 14:00:58.212: EOAM RX PAK(Gi2/9):*Aug 17 14:00:58.212: EOAM RX PAK(Gi2/9): infotlv w/ same revision*Aug 17 14:00:58.820: EOAM LM(Gi2/9): SYMPRD w=104857600 lt=1 ht=0elapsed_time=1000(ms) rx_sym=1000000000 err_sym=0*Aug 17 14:00:58.820: EOAM LM(Gi2/9): FRM w=1 lt=1 ht=0 t_frm=0 err_frm=0*Aug 17 14:00:58.820: EOAM LM(Gi2/9): FRMPRD w=10000000 lt=1 ht=0 t_frm=4 err_frm=0*Aug 17 14:00:58.820: EOAM LM(Gi2/9): w=1 lt=10 ht=0 err_frm=0*Aug 17 14:00:58.820: EOAM LM(Gi2/9): w=1 lt=10 ht=0 err_frm=0*Aug 17 14:00:58.856: EOAM TX PAK(Gi2/9):*Aug 17 14:00:58.856: 03 00 50 00 01 10 01 00 00 00 0D 05 DC 00 00 0C*Aug 17 14:00:58.856: 00 00 00 01 02 10 01 00 00 00 0D 05 DC 00 00 0C*Aug 17 14:00:58.856: 00 sent OAMPDU w/ op=0w=1 lt=10 ht=0 err_frm=0*Aug 17 14:00:59.856: EOAM TX PAK(Gi2/9):*Aug 17 14:00:59.856: 03 00 50 00 01 10 01 00 00*Aug 17 14:01:00.832: EOAM LM(Gi2/9): SYMPRD w=104857600 lt=1 ht=0elapsed_time=1008(ms) rx_sym=1000000000 err_sym=0*Aug 17 14:01:00.832: EOAM LM(Gi2/9): FRM w=1 lt=1 ht=0 t_frm=0 err_frm=0*Aug 17 14:01:00.832: EOAM LM(Gi2/9): FRMPRD w=10000000 lt=1 ht=0 t_frm=6 err_frm=0*Aug 17 14:01:00.832: EOAM LM(Gi2/9): w=1 lt=10 ht=0 err_frm=0*Aug 17 14:01:00.832: EOA M LM(Gi2/9): w=1 lt=10 ht=0 err_frm=0*Aug 17 14:01:00.856: EOAM TX PAK(Gi2/9):*Aug 17 14:01:00.856: 03 00 50 00 01 10 01 00 00 00 0D 05 DC 00 00 0C*Aug 17 14:01:00.856: 00 00debug event manager
To turn on the debugging output of Embedded Event Manager (EEM) processes, use the debug event manager command in privileged EXEC mode. To turn off debugging output, use the no form of this command or the undebug command.
debug event manager {action cli | action cns | action mail | all | api calls | api errors | detector all | detector application | detector cli | detector counter | detector interface | detector ioswdsysmon | detector none | detector snmp | detector syslog | detector timer | metricdir | policydir | server events | server scheduling | tcl cli_library | tcl commands | tcl smtp_library}
no debug event manager {action cli | action cns | action mail | all | api calls | api errors | detector all | detector application | detector cli | detector counter | detector interface | detector ioswdsysmon | detector none | detector snmp | detector syslog | detector timer | metricdir | policydir | server events | server scheduling | tcl cli_library | tcl commands | tcl smtp_library}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug event manager command to troubleshoot EEM command operations.
Caution
Examples
The following example turns on debugging messages about EEM server events and then configures an applet to write a message—Test message—to syslog. The debug output that follows displays the various EEM operations that occur as the applet is processed.
Router# debug event manager server eventsDebug Embedded Event Manager server events debugging is onRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# event manager applet timer-testRouter(config-applet)# event timer countdown time 20Router(config-applet)# action label1 syslog msg "Test message"Router(config-applet)# endRouter#03:46:55: fh_server: fh_io_msg: received msg 6 from client jobid 1103:46:55: fh_server: fh_io_msg: handling event register with esid = 2303:46:55: fh_msg_send_to_fd: receive a reply msg, minor: 503:46:55: fh_server: fh_io_msg: received msg 26 from client jobid 1103:46:55: fh_msg_send_to_fd: receive a reply msg, minor: 503:46:55: %SYS-5-CONFIG_I: Configured from console by console03:47:15: fd_pulse_hndlr: received a pulse from /dev/fm/fd_timer03:47:15: fh_msg_send_to_fd: receive a reply msg, minor: 503:47:15: fd_pulse_hndlr: received FH_MSG_EVENT_PUBLISH03:47:15: fh_schedule_callback: fh_schedule_callback: cc=632C0B68 prev_epc=0; epc=63A4167003:47:15: fh_io_msg: received FH_MSG_API_INIT; jobid=13, processid=82, client=3, job name=EEM Callback Thread03:47:15: fh_server: fh_io_msg: received msg 10 from client jobid 1303:47:15: %HA_EM-6-LOG: timer-test: Test message03:47:15: fh_server: fh_io_msg: received msg 62 from client jobid 1303:47:15: fh_schedule_callback: fh_schedule_callback: cc=632C0B68 prev_epc=63A41670; epc=003:47:15: fh_server: fh_io_msg: received msg 1 from client jobid 1303:47:15: fh_io_msg: received FH_MSG_API_CLOSE client=3
Table 87 describes some of the significant fields shown in the display.
debug events
To display events, use the debug events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug events
no debug events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command displays events that occur on the interface processor and is useful for diagnosing problems in an network. It provides an overall picture of the stability of the network. In a stable network, the debug events command does not return any information. If the command generates numerous messages, the messages can indicate the possible source of problems.
When configuring or making changes to a router or interface for, enable the debug events command. Doing so alerts you to the progress of the changes or to any errors that might result. Also use this command periodically when you suspect network problems.
Examples
The following is sample output from the debug events command:
Router# debug eventsRESET(4/0): PLIM type is 1, Rate is 100Mbpsaip_disable(4/0): state=1config(4/0)aip_love_note(4/0): asr=0x201aip_enable(4/0)aip_love_note(4/0): asr=0x4000aip_enable(4/0): restarting VCs: 7aip_setup_vc(4/0): vc:1 vpi:1 vci:1aip_love_note(4/0): asr=0x200aip_setup_vc(4/0): vc:2 vpi:2 vci:2aip_love_note(4/0): asr=0x200aip_setup_vc(4/0): vc:3 vpi:3 vci:3aip_love_note(4/0): asr=0x200aip_setup_vc(4/0): vc:4 vpi:4 vci:4aip_love_note(4/0): asr=0x200aip_setup_vc(4/0): vc:6 vpi:6 vci:6aip_love_note(4/0): asr=0x200aip_setup_vc(4/0): vc:7 vpi:7 vci:7aip_love_note(4/0): asr=0x200aip_setup_vc(4/0): vc:11 vpi:11 vci:11aip_love_note(4/0): asr=0x200Table 88 describes the significant fields shown in the display.
The following line indicates that the AIP was reset. The PLIM detected was 1, so the maximum rate is set to 100 Mbps.
RESET(4/0): PLIM type is 1, Rate is 100MbpsThe following line indicates that the AIP was given a shutdown command, but the current configuration indicates that the AIP should be up:
aip_disable(4/0): state=1The following line indicates that a configuration command has been completed by the AIP:
aip_love_note(4/0): asr=0x201The following line indicates that the AIP was given a no shutdown command to take it out of the shutdown state:
aip_enable(4/0)The following line indicates that the AIP detected a carrier state change. It does not indicate that the carrier is down or up, only that it has changed.
aip_love_note(4/0): asr=0x4000The following line of output indicates that the AIP enable function is restarting all permanent virtual circuits (PVCs) automatically:
aip_enable(4/0): restarting VCs: 7The following lines of output indicate that PVC 1 was set up and a successful completion code was returned:
aip_setup_vc(4/0): vc:1 vpi:1 vci:1aip_love_note(4/0): asr=0x200
Posted: Fri Jul 13 04:37:51 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
