Cisco IOS Debug Command Reference

Cisco IOS Debug Command Reference May 2008

Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0805R) Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco IOS Debug Command Reference © 2008 Cisco Systems, Inc. All rights reserved.

Introduction The Cisco IOS Debug Command Reference book consists of the following chapters: •

Using Debug Commands—Explains how you use debug commands to diagnose and resolve internetworking problems.

•

Conditionally Triggered Debugging—Describes how to obtain debugging messages for packets entering or leaving a router on a specified interface.

•

Debug Commands—Provides detailed descriptions of the debug commands and how to use them.

•

X.25 Cause and Diagnostic Codes—Describes the X.25 causes and diagnostic codes that appear in certain debug command output.

•

ISDN Switch Types, Codes, and Values—Contains a list of the supported switch types, the ISDN cause codes, cause values, bearer capability values, and progress description field values that are valid within the debug commands for ISDN.

Output formats vary with each debug command. Some commands generate a single line of output per packet, whereas others generate multiple lines of output per packet. Some generate large amounts of output; others generate only occasional output. Some generate lines of text, and others generate information in field format. Therefore, the way debug command output is documented also varies. For example, the output for debug commands that generate lines of text is usually described line by line, and the output for debug commands that generate information in field format is usually described in tables. By default, the network server sends the output from the debug commands to the console. Sending output to a terminal (virtual console) produces less overhead than sending it to the console. Use the terminal monitor privileged EXEC command to send output to a terminal. For more information about redirecting output, see the “Using Debug Commands” chapter.


DB-1

Introduction

Cisco IOS Debug Command Reference

DB-2

May 2008

Using Debug Commands This chapter explains how to use debug commands to diagnose and resolve internetworking problems. Specifically, this chapter covers the following topics:

Caution

•

Entering debug commands

•

Using the debug ? command

•

Using the debug all command

•

Generating debug command output

•

Redirecting debug and error message output

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

Entering debug Commands All debug commands are entered in privileged EXEC mode, and most debug commands take no arguments. For example, to enable the debug isdn q931 command, enter the following the command line in privileged EXEC mode: debug isdn q931 To turn off the debug isdn q931 command, enter the no form of the command at the command line in privileged EXEC mode: no debug isdn q931 To display the state of each debugging option, enter the following at the command line in privileged EXEC mode: show debugging


DB-3

Using Debug Commands Using the debug ? Command

Using the debug ? Command To list and see a brief description of all the debugging command options, enter the following command at the command line in privileged EXEC mode: debug ? Not all debugging commands listed in the debug ? output are described in this document. Commands are included here based on their usefulness in assisting you to diagnose network problems. Commands not included are typically used internally by Cisco engineers during the development process and are not intended for use outside the Cisco environment.

Using the debug all Command To enable all system diagnostics, enter the following command at the command line in privileged EXEC mode: debug all The no debug all command turns off all diagnostic output. Using the no debug all command is a convenient way to ensure that you have not accidentally left any debug commands turned on.

Caution

Because debugging output takes priority over other network traffic, and because the debug all command generates more output than any other debug command, it can severely diminish the performance of the router or even render it unusable. In virtually all cases, it is best to use more specific debug commands.

Generating debug Command Output Enabling a debug command can result in output similar to the following example for the debug modem command: Router# debug modem 15:25:51: 15:25:51: 15:25:51: 15:27:51: 15:27:51: 15:27:51: 15:27:52: 15:27:52: 15:27:57: 15:27:58:

TTY4: tty4: TTY4: TTY4: TTY4: TTY4: TTY4: tty4: TTY4: TTY4:

DSR came up Modem: IDLE->READY Autoselect started Autoselect failed Line reset Modem: READY->HANGUP dropping DTR, hanging up Modem: HANGUP->IDLE restoring DTR DSR came up

The router continues to generate such output until you enter the corresponding no debug command (in this case, the no debug modem command).


DB-4

May 2008

Using Debug Commands Redirecting debug and Error Message Output

If you enable a debug command and no output is displayed, consider the following possibilities: •

The router may not be properly configured to generate the type of traffic you want to monitor. Use the more system:running-config EXEC command to check its configuration.

•

Even if the router is properly configured, it may not generate the type of traffic you want to monitor during the particular period that debugging is turned on. Depending on the protocol you are debugging, you can use commands such as the TCP/IP ping EXEC command to generate network traffic.

Redirecting debug and Error Message Output By default, the network server sends the output from debug commands and system error messages to the console. If you use this default, monitor debug output using a virtual terminal connection, rather than the console port. To redirect debug output, use the logging command options within configuration mode as described in the following sections. Possible destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server. The syslog format is compatible with 4.3 Berkeley Standard Distribution (BSD) UNIX and its derivatives.

Note

Be aware that the debugging destination you use affects system overhead. Logging to the console produces very high overhead, whereas logging to a virtual terminal produces less overhead. Logging to a syslog server produces even less, and logging to an internal buffer produces the least overhead of any method. To configure message logging, you need to be in configuration command mode. To enter this mode, use the configure terminal command at the EXEC prompt.

Enabling Message Logging To enable message logging to all supported destinations other than the console, enter the following command: logging on The default condition is logging on. To direct logging to the console only and disable logging output to other destinations, enter the following command: no logging on


DB-5


Setting the Message Logging Levels You can set the logging levels when logging messages to the following devices: •

Console

•

Monitor

•

Syslog server

Table 1 lists and briefly describes the logging levels and corresponding keywords you can use to set the logging levels for these types of messages. The highest level of message is level 0, emergencies. The lowest level is level 7, debugging, which also displays the greatest amount of messages. For information about limiting these messages, see sections later in this chapter. Table 1

Message Logging Keywords and Levels

Level

Keyword

Description

Syslog Definition

0

emergencies

System is unusable.

LOG_EMERG

1

alerts

Immediate action is needed.

LOG_ALERT

2

critical

Critical conditions exist.

LOG_CRIT

3

errors

Error conditions exist.

LOG_ERR

4

warnings

Warning conditions exist.

LOG_WARNING

5

notification

Normal, but significant, conditions exist.

LOG_NOTICE

6

informational

Informational messages.

LOG_INFO

7

debugging

Debugging messages.

LOG_DEBUG

Limiting the Types of Logging Messages Sent to the Console To limit the types of messages that are logged to the console, use the logging console router configuration command. The full syntax of this command follows: logging console level no logging console The logging console command limits the logging messages displayed on the console to messages up to and including the specified severity level, which is specified by the level argument. Keywords are listed in order from the most severe level to the least severe. The no logging console command disables logging to the console. The following example sets console logging of messages at the debugging level, which is the least severe level and which displays all logging messages: logging console debugging


DB-6

May 2008


Logging Messages to an Internal Buffer The default logging device is the console; all messages are displayed on the console unless otherwise specified. To log messages to an internal buffer, use the logging buffered router configuration command. The full syntax of this command follows: logging buffered no logging buffered The logging buffered command copies logging messages to an internal buffer instead of writing them to the console. The buffer is circular in nature, so newer messages overwrite older messages. To display the messages that are logged in the buffer, use the show logging privileged EXEC command. The first message displayed is the oldest message in the buffer. The no logging buffered command cancels the use of the buffer and writes messages to the console (the default).

Limiting the Types of Logging Messages Sent to Another Monitor To limit the level of messages logged to the terminal lines (monitors), use the logging monitor router configuration command. The full syntax of this command follows: logging monitor level no logging monitor The logging monitor command limits the logging messages displayed on terminal lines other than the console line to messages with a level up to and including the specified level argument. To display logging messages on a terminal (virtual console), use the terminal monitor privileged EXEC command. The no logging monitor command disables logging to terminal lines other than the console line. The following example sets the level of messages displayed on monitors other than the console to notification: logging monitor notification

Logging Messages to a UNIX Syslog Server To log messages to a syslog server host, use the logging host global configuration command. The full syntax of this command follows: logging host {ip-address | host-name} [xml] no logging host {ip-address | host-name} [xml] The logging host command identifies a syslog server host that is to receive logging messages. The ip-address argument is the IP address of the host. By issuing this command more than once, you build a list of syslog servers that receive logging messages. The no logging host command deletes the syslog server with the specified address from the list of syslogs.


DB-7


Limiting Messages to a Syslog Server To limit the number of messages sent to syslog servers, use the logging trap router configuration command. The full syntax of this command follows: logging trap level no logging trap The logging trap command limits the logging messages sent to syslog servers to logging messages with a level up to and including the specified level argument. To send logging messages to a syslog server, specify its host address with the logging host command. The default trap level is informational. The no logging trap command returns the trap level to the default. The current software generates the following categories of syslog messages: •

Error messages at the emergencies level.

•

Error messages at the alerts level.

•

Error messages at the critical level.

•

Error messages about software or hardware malfunctions, displayed at the errors level.

•

Interface up/down transitions and system restart messages, displayed at the notification level.

•

Reload requests and low-process stack messages, displayed at the informational level.

•

Output from the debug commands, displayed at the debugging level.

The show logging privileged EXEC command displays the addresses and levels associated with the current logging setup. The command output also includes ancillary statistics.

Example of Setting Up a UNIX Syslog Daemon To set up the syslog daemon on a 4.3 BSD UNIX system, include a line such as the following in the file /etc/syslog.conf: local7.debugging /usr/adm/logs/tiplog

The local7 keyword specifies the logging facility to be used. The debugging keyword specifies the syslog level. See Table 1 for other keywords that can be listed. The UNIX system sends messages at or above this level to the specified file, in this case /usr/adm/logs/tiplog. The file must already exist, and the syslog daemon must have permission to write to it. For the System V UNIX systems, the line should read as follows: local7.debug /usr/admin/logs/cisco.log8


DB-8

May 2008

Conditionally Triggered Debugging When the Conditionally Triggered Debugging feature is enabled, the router generates debugging messages for packets entering or leaving the router on a specified interface; the router will not generate debugging output for packets entering or leaving through a different interface. You can specify the interfaces explicitly. For example, you may want to see debugging messages only for one interface or subinterface. You can also turn on debugging for all interfaces that meet specified conditions. This feature is useful on dial access servers, which have a large number of ports. Normally, the router will generate debugging messages for every interface, resulting in a large number of messages that consume system resources and can make it difficult to find the specific information you need. By limiting the number of debugging messages, you can receive messages related to only the ports you want to troubleshoot. The Conditionally Triggered Debugging feature controls the output from the following protocol-specific debug commands: •

debug aaa {accounting | authorization | authentication}

•

debug dialer packets

•

debug isdn {q921 | q931}

•

debug modem

•

debug ppp {packet | negotiation | error | authentication | compression | cbcp}

Although this feature limits the output of the listed commands, it does not automatically enable the generation of debugging output from these commands. Debugging messages are generated only when the protocol-specific debug command is enabled. The debug command output is controlled through two processes: •

The protocol-specific debug commands specify which protocols are being debugged. For example, the debug dialer events command generates debugging output related to dialer events.

•

The debug condition commands limit these debugging messages to those related to a particular interface. For example, the debug condition username cisco command generates debugging output only for interfaces with packets that specify a username of cisco.

To configure Conditionally Triggered Debugging, perform the tasks described in the following sections: •

Enabling Protocol-Specific Debug Commands

•

Enabling Conditional Debugging Commands

•

Specifying Multiple Conditions


DB-9

Conditionally Triggered Debugging Enabling Protocol-Specific Debug Commands

Enabling Protocol-Specific Debug Commands To generate any debugging output, the protocol-specific debug command for the desired output must be enabled. Use the show debugging command to determine which types of debugging are enabled. Use the following commands in privileged EXEC mode to enable or disable the desired protocol-specific debug commands as needed: Command

Purpose

show debugging

Determines which types of debugging are enabled.

debug protocol

Enables the desired debugging commands.

no debug protocol

Disables the debugging commands that are not desired.

If you want to have no output, disable all the protocol-specific debug commands.

Enabling Conditional Debugging Commands If no debug condition commands are enabled, all debugging output, regardless of the interface, will be displayed for the enabled protocol-specific debug commands. The first debug condition command you enter enables conditional debugging. The router will display messages only for interfaces that meet one of the specified conditions. If multiple conditions are specified, the interface must meet at least one of the conditions in order for messages to be displayed. To enable messages for interfaces specified explicitly or for interfaces that meet certain conditions, perform the tasks described in the following sections: •

Displaying Messages for One Interface

•

Displaying Messages for Multiple Interfaces

•

Limiting Messages Based on Conditions

Displaying Messages for One Interface To disable debugging messages for all interfaces except one, use the following command in privileged EXEC mode: Command

Purpose

debug condition interface interface-type interface-number

Disables debugging messages for all interfaces except one.

If you enter the debug condition interface command, the debugging output will be turned off for all interfaces except the specified interface. To reenable debugging output for all interfaces, use the no debug condition interface command.


DB-10

May 2008

Conditionally Triggered Debugging Enabling Conditional Debugging Commands

Displaying Messages for Multiple Interfaces To enable debugging messages for multiple interfaces, use the following commands in privileged EXEC mode: Command

Purpose

debug condition interface interface-type interface-number

Disables debugging messages for all interfaces except one. To enable debugging messages for additional interfaces, repeat this command until debugging messages are enabled for all desired interfaces.

If you specify more than one interface by entering this command multiple times, debugging output will be displayed for all of the specified interfaces. To turn off debugging on a particular interface, use the no debug interface command. If you use the no debug interface all command or remove the last debug interface command, debugging output will be reenabled for all interfaces.

Limiting Messages Based on Conditions The router can monitor interfaces to learn if any packets contain the specified value for one of the following conditions: •

Username

•

Calling party number

•

Called party number

If you enter a condition, such as calling number, debug output will be stopped for all interfaces. The router will then monitor every interface to learn if a packet with the specified calling party number is sent or received on any interfaces. If the condition is met on an interface or subinterface, debug command output will be displayed for that interface. The debugging output for an interface is “triggered” when the condition has been met. The debugging output continues to be disabled for the other interfaces. If at some later time the condition is met for another interface, the debug output will become enabled for that interface as well. Once debugging output has been triggered on an interface, the output will continue until the interface goes down. However, the session for that interface might change, resulting in a new username, called party number, or calling party number. Use the no debug interface command to reset the debug trigger mechanism for a particular interface. The debugging output for that interface will be disabled until the interface meets one of the specified conditions. To limit debugging messages based on a specified condition, use the following command in privileged EXEC mode: Command

Purpose

debug condition {username username | called dial-string | caller dial-string}

Enables conditional debugging. The router will display messages only for interfaces that meet this condition.

To reenable the debugging output for all interfaces, use the no debug condition all command.


DB-11

Conditionally Triggered Debugging Specifying Multiple Conditions

Specifying Multiple Conditions To limit debugging messages based on more than one condition, use the following commands in privileged EXEC mode as needed: Command

Purpose


Enables conditional debugging and specifies the first condition.


Specifies the second condition. Repeat this task until all conditions are specified.

If you enter multiple debug condition commands, debugging output will be generated if an interface meets at least one of the conditions. If you use the no debug condition command to remove one of the conditions, using interfaces that meet only that condition will no longer produce debugging output. However, interfaces that meet a condition other than the removed condition will continue to generate output. Only if no active conditions are met for an interface will the output for that interface be disabled.

Conditionally Triggered Debugging Configuration Examples In this example, four conditions have been set by the following commands: •

debug condition interface serial 0

•

debug condition interface serial 1

•

debug condition interface virtual-template 1

•

debug condition username cisco

The first three conditions have been met by one interface. The fourth condition has not yet been met. Router# show debug condition Condition 1: interface Se0 (1 flags triggered) Flags: Se0 Condition 2: interface Se1 (1 flags triggered) Flags: Se1 Condition 3: interface Vt1 (1 flags triggered) Flags: Vt1 Condition 4: username cisco (0 flags triggered)

When any debug condition command is entered, debugging messages for conditional debugging are enabled. The following debugging messages show conditions being met on different interfaces as serial interface 0 and serial interface 1 come up. For example, the second line of output indicates that serial interface 0 meets the username cisco condition. *Mar 1 00:04:41.647: %LINK-3-UPDOWN: Interface Serial0, changed state to up *Mar 1 00:04:41.715: Se0 Debug: Condition 4, username cisco triggered, count 2 *Mar 1 00:04:42.963: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up *Mar 1 00:04:43.271: Vi1 Debug: Condition 3, interface Vt1 triggered, count 1 *Mar 1 00:04:43.271: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up *Mar 1 00:04:43.279: Vi1 Debug: Condition 4, username cisco triggered, count 2 *Mar 1 00:04:43.283: Vi1 Debug: Condition 1, interface Se0 triggered, count 3 *Mar 1 00:04:44.039: %IP-4-DUPADDR: Duplicate address 172.27.32.114 on Ethernet 0, sourced by 00e0.1e3e.2d41


DB-12

May 2008

Conditionally Triggered Debugging Conditionally Triggered Debugging Configuration Examples

*Mar 1 00:04:44.283: changed state to up *Mar 1 00:04:54.667: *Mar 1 00:04:54.731: *Mar 1 00:04:54.735: *Mar 1 00:04:55.735: state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, %LINK-3-UPDOWN: Interface Serial1, changed state to up Se1 Debug: Condition 4, username cisco triggered, count 2 Vi1 Debug: Condition 2, interface Se1 triggered, count 4 %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed

After a period of time, the show debug condition command displays the revised list of conditions: Router# show debug condition Condition 1: interface Se0 (2 flags triggered) Flags: Se0 Vi1 Condition 2: interface Se1 (2 flags triggered) Flags: Se1 Vi1 Condition 3: interface Vt1 (2 flags triggered) Flags: Vt1 Vi1 Condition 4: username cisco (3 flags triggered) Flags: Se0 Vi1 Se1

Next, serial interface 1 and serial interface 0 go down. When an interface goes down, conditions for that interface are cleared. *Mar 1 00:05:51.443: *Mar 1 00:05:51.471: *Mar 1 00:05:51.479: *Mar 1 00:05:52.443: state to down *Mar 1 00:05:56.859: *Mar 1 00:05:56.887: *Mar 1 00:05:56.895: *Mar 1 00:05:56.899: *Mar 1 00:05:56.899: *Mar 1 00:05:56.903: *Mar 1 00:05:57.907: state to down *Mar 1 00:05:57.907: changed state to down

%LINK-3-UPDOWN: Interface Serial1, changed state to down Se1 Debug: Condition 4, username cisco cleared, count 1 Vi1 Debug: Condition 2, interface Se1 cleared, count 3 %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed %LINK-3-UPDOWN: Interface Serial0, changed state to down Se0 Debug: Condition 4, username cisco cleared, count 1 Vi1 Debug: Condition 1, interface Se0 cleared, count 2 Vi1 Debug: Condition 3, interface Vt1 cleared, count 1 Vi1 Debug: Condition 4, username cisco cleared, count 0 %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1,

The final show debug condition output is the same as the output before the interfaces came up: Router# show debug condition Condition 1: interface Se0 (1 flags triggered) Flags: Se0 Condition 2: interface Se1 (1 flags triggered) Flags: Se1 Condition 3: interface Vt1 (1 flags triggered) Flags: Vt1 Condition 4: username cisco (0 flags triggered)


DB-13

Conditionally Triggered Debugging Conditionally Triggered Debugging Configuration Examples


DB-14

May 2008

Debug Commands This chapter contains an alphabetical listing of the debug commands and their descriptions. Documentation for each command includes a brief description of its use, command syntax, usage guidelines, sample output, and a description of that output.


DB-15

Debug Commands debug aaa accounting

debug aaa accounting To display information on accountable events as they occur, use the debug aaa accounting command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug aaa accounting no debug aaa accounting

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Usage Guidelines

The information displayed by the debug aaa accounting command is independent of the accounting protocol used to transfer the accounting information to a server. Use the debug tacacs and debug radius protocol-specific commands to get more detailed information about protocol-level issues. You can also use the show accounting command to step through all active sessions and to print all the accounting records for actively accounted functions. The show accounting command allows you to display the active “accountable events” on the system. It provides systems administrators a quick look at what is happening, and may also be useful for collecting information in the event of a data loss of some kind on the accounting server. The show accounting command displays additional data on the internal state of the authentication, authorization, and accounting (AAA) security system if debug aaa accounting is turned on as well.

Examples

The following is sample output from the debug aaa accounting command: Router# debug aaa accounting 16:49:21: AAA/ACCT: EXEC acct start, line 10 16:49:32: AAA/ACCT: Connect start, line 10, glare 16:49:47: AAA/ACCT: Connection acct stop: task_id=70 service=exec port=10 protocol=telnet address=172.31.3.78 cmd=glare bytes_in=308 bytes_out=76 paks_in=45 paks_out=54 elapsed_time=14

Related Commands

Command

Description

debug aaa authentication

Displays information on accountable events as they occur.

debug aaa authorization

Displays information on AAA/TACACS+ authorization.

debug radius

Displays information associated with the RADIUS.

debug tacacs

Displays information associated with the TACACS.


DB-16

May 2008

Debug Commands debug aaa authentication

debug aaa authentication To display information on authentication, authorization, and accounting (AAA) TACACS+ authentication, use the debug aaa authentication command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug aaa authentication no debug aaa authentication

Syntax Description


Command Modes

Privileged EXEC (#)

Usage Guidelines

Use this command to learn the methods of authentication being used and the results of these methods.

Examples

The following is sample output from the debug aaa authentication command. A single EXEC login that uses the “default” method list and the first method, TACACS+, is displayed. The TACACS+ server sends a GETUSER request to prompt for the username and then a GETPASS request to prompt for the password, and finally a PASS response to indicate a successful login. The number 50996740 is the session ID, which is unique for each authentication. Use this ID number to distinguish between different authentications if several are occurring concurrently. Router# debug aaa authentication 6:50:12: AAA/AUTHEN: create_user user='' ruser='' port='tty19' rem_addr='172.31.60.15' authen_type=1 service=1 priv=1 6:50:12: AAA/AUTHEN/START (0): port='tty19' list='' action=LOGIN service=LOGIN 6:50:12: AAA/AUTHEN/START (0): using “default” list 6:50:12: AAA/AUTHEN/START (50996740): Method=TACACS+ 6:50:12: TAC+ (50996740): received authen response status = GETUSER 6:50:12: AAA/AUTHEN (50996740): status = GETUSER 6:50:15: AAA/AUTHEN/CONT (50996740): continue_login 6:50:15: AAA/AUTHEN (50996740): status = GETUSER 6:50:15: AAA/AUTHEN (50996740): Method=TACACS+ 6:50:15: TAC+: send AUTHEN/CONT packet 6:50:15: TAC+ (50996740): received authen response status = GETPASS 6:50:15: AAA/AUTHEN (50996740): status = GETPASS 6:50:20: AAA/AUTHEN/CONT (50996740): continue_login 6:50:20: AAA/AUTHEN (50996740): status = GETPASS 6:50:20: AAA/AUTHEN (50996740): Method=TACACS+ 6:50:20: TAC+: send AUTHEN/CONT packet 6:50:20: TAC+ (50996740): received authen response status = PASS 6:50:20: AAA/AUTHEN (50996740): status = PASS


DB-17

Debug Commands debug aaa authorization

debug aaa authorization To display information on authentication, authorization, and accounting (AAA) TACACS+ authorization, use the debug aaa authorization command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug aaa authorization no debug aaa authorization

Syntax Description


Command Modes

Privileged EXEC (#)

Usage Guidelines

Use this command to learn the methods of authorization being used and the results of these methods.

Examples

The following is sample output from the debug aaa authorization command. In this display, an EXEC authorization for user “carrel” is performed. On the first line, the username is authorized. On the second and third lines, the attribute value (AV) pairs are authorized. The debug output displays a line for each AV pair that is authenticated. Next, the display indicates the authorization method used. The final line in the display indicates the status of the authorization process, which, in this case, has failed. Router# debug aaa authorization 2:23:21: 2:23:21: 2:23:21: 2:23:21: 2:23:21: 2:23:21: 2:23:21: 2:23:21:

AAA/AUTHOR (0): user='carrel' AAA/AUTHOR (0): send AV service=shell AAA/AUTHOR (0): send AV cmd* AAA/AUTHOR (342885561): Method=TACACS+ AAA/AUTHOR/TAC+ (342885561): user=carrel AAA/AUTHOR/TAC+ (342885561): send AV service=shell AAA/AUTHOR/TAC+ (342885561): send AV cmd* AAA/AUTHOR (342885561): Post authorization status = FAIL

The aaa authorization command causes a request packet containing a series of AV pairs to be sent to the TACACS+ daemon as part of the authorization process. The daemon responds in one of the following three ways: •

Accepts the request as is

•

Makes changes to the request

•

Refuses the request, thereby refusing authorization

Table 2 describes AV pairs associated with the debug aaa authorization command that may appear in the debug output.


DB-18

May 2008


Table 2

Attribute Value Pairs for Authorization

Attribute Value

Description

service=arap

Authorization for the AppleTalk remote access (ARA) protocol is being requested.

service=shell

Authorization for EXEC startup and command authorization is being requested.

service=ppp

Authorization for PPP is being requested.

service=slip

Authorization for SLIP is being requested.

protocol=lcp

Authorization for LCP is being requested (lower layer of PPP).

protocol=ip

Used with service=slip to indicate which protocol layer is being authorized.

protocol=ipx

Used with service=ppp to indicate which protocol layer is being authorized.

protocol=atalk

Used with service=ppp or service=arap to indicate which protocol layer is being authorized.

protocol=vines

Used with service=ppp for VINES over PPP.

protocol=unknown

Used for undefined or unsupported conditions.

cmd=x

Used with service=shell, if cmd=NULL, this is an authorization request to start an EXEC. If cmd is not NULL, this is a command authorization request and will contain the name of the command being authorized. For example, cmd=telnet.

cmd-arg=x

Used with service=shell. When performing command authorization, the name of the command is given by a cmd=x pair for each argument listed. For example, cmd-arg=archie.sura.net.

acl=x

Used with service=shell and service=arap. For ARA, this pair contains an access list number. For service=shell, this pair contains an access class number. For example, acl=2.

inacl=x

Used with service=ppp and protocol=ip. Contains an IP input access list for SLIP or PPP/IP. For example, inacl=2.

outacl=x

Used with service=ppp and protocol=ip. Contains an IP output access list for SLIP or PPP/IP. For example, outacl=4.

addr=x

Used with service=slip, service=ppp, and protocol=ip. Contains the IP address that the remote host should use when connecting via SLIP or PPP/IP. For example, addr=172.30.23.11.

routing=x

Used with service=slip, service=ppp, and protocol=ip. Equivalent in function to the /routing flag in SLIP and PPP commands. Can either be true or false. For example, routing=true.

timeout=x

Used with service=arap. The number of minutes before an ARA session disconnects. For example, timeout=60.

autocmd=x

Used with service=shell and cmd=NULL. Specifies an autocommand to be executed at EXEC startup. For example, autocmd=telnet yxz.com.

noescape=x

Used with service=shell and cmd=NULL. Specifies a noescape option to the username configuration command. Can be either true or false. For example, noescape=true.


DB-19


Table 2

Attribute Value Pairs for Authorization (continued)

Attribute Value

Description

nohangup=x

Used with service=shell and cmd=NULL. Specifies a nohangup option to the username configuration command. Can be either true or false. For example, nohangup=false.

priv-lvl=x

Used with service=shell and cmd=NULL. Specifies the current privilege level for command authorization as a number from 0 to 15. For example, priv-lvl=15.

zonelist=x

Used with service=arap. Specifies an AppleTalk zonelist for ARA. For example, zonelist=5.

addr-pool=x

Used with service=ppp and protocol=ip. Specifies the name of a local pool from which to get the address of the remote host.


DB-20

May 2008

Debug Commands debug aaa cache filterserver

debug aaa cache filterserver To help troubleshoot your filter cache configurations, use the debug aaa cache filterserver command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug aaa cache filterserver no debug aaa cache filterserver

Syntax Description


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(13)T

This command was introduced.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB

12.2SX

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

12.2(33)SRC

This command was integrated into Cisco IOS Release 12.2(33)SRC.

Examples

The following is sample output from the debug aaa cache filterserver command: Router# debug aaa cache filterserver AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/CACHE: AAA/CACHE: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/FLTSV: AAA/CACHE: AAA/CACHE: AAA/CACHE: AAA/CACHE:

need "myfilter" (fetch), call 0x612DAC64 send req, call 0x612DAC50 method SERVER_GROUP myradius recv reply, call 0x612DAC50 (PASS) create cache add attr "call-inacl" add attr "call-inacl" add attr "call-inacl" skip attr "filter-cache-refresh" skip attr "filter-cache-time" set "AAA filtserv cache" entry "myfilter" refresh? no set "AAA filtserv cache" entry "myfilter" cachetime 15 add attr to list "call-inacl" call 0x612DAC64 add attr to list "call-inacl" call 0x612DAC64 add attr to list "call-inacl" call 0x612DAC64 PASS call 0x612DAC64 timer "AAA filtserv cache", next in 10 secs (0 entries) timer "AAA filtserv cache", next in 10 secs (1 entry) destroy "AAA filtserv cache" entry "myfilter" timer "AAA filtserv cache", next in 10 secs (0 entries)


DB-21

Debug Commands debug aaa cache filterserver

Related Commands

Command

Description

aaa authorization cache filterserver

Enables AAA authorization caches and the downloading of ACL configurations from a RADIUS filter server.


DB-22

May 2008

Debug Commands debug aaa cache group

debug aaa cache group To debug the caching mechanism and ensure that entries are being cached from AAA Server Responses and are being found when queried, use the debug aaa cache group command in privileged EXEC mode. debug aaa cache group

Syntax Description


Command Default

Debug information for all cached entries is displayed.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(28)SB


12.2SX


12.2(33)SRC


Usage Guidelines

Use this command to display debug information about cached entries.

Examples

The following example shows how to display debug information about all cached entries: Router# debug aaa cache group

Related Commands

Command

Description

clear aaa cache group

Clears an individual entry or all entries in the cache.

show aaa cache group

Displays cache entries stored by the AAA Auth Cache.


DB-23

Debug Commands debug aaa dead-criteria transactions

debug aaa dead-criteria transactions To display authentication, authorization, and accounting (AAA) dead-criteria transaction values, use the debug aaa dead-criteria transactions command in privileged EXEC mode. To disable dead-criteria debugging, use the no form of this command. debug aaa dead-criteria transactions no debug aaa dead-criteria transactions

Syntax Description


Defaults

If the command is not configured, debugging is not turned on.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(6)


12.3(7)T

This command was integrated into Cisco IOS Release 12.3(7)T. The command output includes two new fields: Current Tries and Elapsed Time.

12.2SX


Usage Guidelines

Dead-criteria transaction values may change with every AAA transaction. Some of the values that can be displayed are estimated outstanding transactions, retransmit tries, and dead-detect intervals. These values are explained in Table 3.

Examples

The following example shows dead-criteria transaction information for a particular server group: Router# debug aaa dead-criteria transactions AAA Transaction debugs debugging is on *Nov 14 23:44:17.403: AAA/SG/TRANSAC: Computed Retransmit Tries: 10, Current Tries: 3, Current Max Tries: 10 *Nov 14 23:44:17.403: AAA/SG/TRANSAC: Computed Dead Detect Interval: 10s, Elapsed Time: 317s, Current Max Interval: 10s *Nov 14 23:44:17.403: AAA/SG/TRANSAC: Estimated Outstanding Transactions: 6, Current Max Transactions: 6


DB-24

May 2008

Debug Commands debug aaa dead-criteria transactions

Table 3 describes the significant fields shown in the display. Table 3

Related Commands

debug aaa dead-criteria transactions Field Descriptions

Field

Description

AAA/SG/TRANSAC

AAA server-group transactions.

Computed Retransmit Tries

Currently computed number of retransmissions before the server is marked as dead.

Current Tries

Number of successive failures since the last valid response.

Current Max Tries

Maximum number of tries since the last successful transaction.

Computed Dead Detect Interval

Period of inactivity (the number of seconds since the last successful transaction) that can elapse before the server is marked as dead. The period of inactivity starts when a transaction is sent to a server that is considered live. The dead-detect interval is the period that the router waits for responses from the server before the router marks the server as dead.

Elapsed Time

Amount of time that has elapsed since the last valid response.

Current Max Interval

Maximum period of inactivity since the last successful transaction.

Estimated Outstanding Transactions

Estimated number of transactions that are associated with the server.

Current Max Transactions

Maximum transactions since the last successful transaction.

Command

Description

radius-server dead-criteria

Forces one or both of the criteria—used to mark a RADIUS server as dead—to be the indicated constant.

show aaa dead-criteria

Displays dead-criteria detection information for an AAA server.


DB-25

Debug Commands debug aaa per-user

debug aaa per-user To display debugging information about PPP session per-user activities, use the debug aaa per-user command in privileged EXEC mode. To turn off debugging, use the no form of this command. debug aaa per-user no debug aaa per-user

Syntax Description


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

11.3 T

This command has existed since Cisco IOS Release 11.3 T.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2SX


Usage Guidelines

The per-user module is responsible for installing per-user attributes for PPP sessions.

Examples

The following example displays the configuration commands that were generated by the per-user process: Router# debug aaa per-user AAA/PER-USER: line=[ip access-list standard Virtual-Access2#31] AAA/PER-USER: line=[deny 10.0.0.2 0.0.0.0] AAA/PER-USER: line=[permit any]

The fields in the display are self-explanatory.

Related Commands

Command

Description


Displays information on AAA TACACS+ authorization.

debug ppp

Displays information on traffic and exchanges in an internetwork implementing the PPP.

debug radius

Displays information associated with RADIUS.

debug tacacs

Displays information associated with TACACS.


DB-26

May 2008

Debug Commands debug aaa pod

debug aaa pod To display debug messages related to packet of disconnect (POD) packets, use the debug aaa pod command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug aaa pod no debug aaa pod

Syntax Description

This command has no keywords or arguments.

Defaults

Debugging for POD packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(2)XB

Support for the voice applications as well as support for the Cisco AS5350, Cisco AS5400 and the Cisco 3600 series was added.

Examples

12.2(2)XB1

Support for the Cisco AS5800 was added.

12.2(11)T

Support for the Cisco AS5850 was added. This command was integrated into Cisco IOS Release 12.2(11)T.

12.2(33)SRA


12.2SX


The following example shows output from a successful POD request when using the show debug command: Router# debug aaa pod AAA POD packet processing debugging is on Router# show debug General OS: AAA POD packet processing debugging is on Router# Apr 25 17:15:59.318:POD:172.19.139.206 request queued Apr 25 17:15:59.318:voice_pod_request: Apr 25 17:15:59.318:voip_populate_pod_attr_list: Apr 25 17:15:59.318:voip_pod_get_guid: Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val: Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr_len=50 Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr=h323-conf-id Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr_len=50 value_len=35


DB-27

Debug Commands debug aaa pod

Apr 25 17:15:59.318:voip_pod_get_guid:conf-id=FFA7785F F7F607BB 00000000 993FB1F4 n_bytes=35 Apr 25 17:15:59.318:voip_pod_get_guid:GUID = FFA7785F F7F607BB 00000000 993FB1F4 Apr 25 17:15:59.318:voip_populate_pod_attr_list: Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val: Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr_len=23 Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr=h323-originate Apr 25 17:15:59.318:voip_pod_get_vsa_attr_val:attr_len=23 value_len=6 Apr 25 17:15:59.318:voip_get_call_direction: Apr 25 17:15:59.318:voip_get_call_direction:returning answer Apr 25 17:15:59.318:voip_eval_pod_attr: Apr 25 17:15:59.318:cc_api_trigger_disconnect: Apr 25 17:15:59.322:POD:Sending ACK to 172.19.139.206/1700 Apr 25 17:15:59.322:voip_pod_clean:

Related Commands

Command

Description

aaa pod server

Enables the POD feature.


DB-28

May 2008

Debug Commands debug aaa redundancy

debug aaa redundancy To view debug output that displays authentication, authorization, and accounting (AAA) redundancy events during session activation, session synchronization to the standby device, and dynamic session updates to the standby device, use the debug aaa redundancy command in privileged EXEC mode. To disable debugging for AAA redundancy, use the no form of this command. debug aaa redundancy no debug aaa redundancy

Syntax Description


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(31)SB2


12.2SX


12.2(33)SRC


Usage Guidelines

This command displays the AAA synchronization data for the session synchronization to the standby device. This information might be useful for diagnosing any AAA issues related to the session synchronization.

Examples

The following example shows sample output of the debug aaa redundancy command collected while activating a session and synchronizing the session to the standby device: Router# debug aaa redundancy Logs on Active ============== 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55: 01:31:55:

CCM: New State[Not Ready] CCM: PPPoE Required CCM: PPP Required CCM: LTERM Required CCM: PPPoE is Initiator AAA/BIND(0000000B): Bind i/f Virtual-Template1 CCM: AAA Ready AAA/CCM/(0000000B): AAA sso init completed successfully SSS INFO: Element type is Access-Type = 3 (PPPoE) SSS INFO: Element type is Protocol-Type = 0 (PPP) SSS INFO: Element type is Media-Type = 1 (Ethernet) SSS INFO: Element type is Switch-Id = 4105 (00001009) SSS INFO: Element type is Segment-Hdl = 4114 (00001012) SSS INFO: Element type is AAA-Id = 11 (0000000B)


DB-29


01:31:55: SSS INFO: Element type is AccIe-Hdl = 33554441 (02000009) 01:31:55: SSS INFO: Element type is SHDB-Handle = 1476395017 (58000009) 01:31:55: SSS INFO: Element type is Input Interface = "GigabitEthernet6/0/0" 01:31:55: SSS MGR [uid:10]: Sending a Session Assert ID Mgr event 01:31:55: SSS MGR [uid:10]: Updating ID Mgr with the following keys: aaa-unique-id 11 (0xB) 01:31:55: SSS MGR [uid:10]: Handling Policy Service Authorize action (1 pending sessions) 01:31:55: SSS PM [uid:10][63D5D594]: RM/VPDN disabled: RM/VPDN author not needed 01:31:55: SSS PM [uid:10][63D5D594]: AAA author needed for registered user 01:31:55: SSS MGR [uid:10]: Got reply Need More Keys from PM 01:31:55: SSS MGR [uid:10]: Handling Need More Keys action 01:31:57: SSS INFO: Element type is Unauth-User = "user1" 01:31:57: SSS INFO: Element type is AccIe-Hdl = 33554441 (02000009) 01:31:57: SSS INFO: Element type is AAA-Id = 11 (0000000B) 01:31:57: SSS INFO: Element type is Access-Type = 0 (PPP) 01:31:57: SSS INFO: Element type is Protocol-Type = 0 (PPP) 01:31:57: SSS MGR [uid:10]: Sending a Session Update ID Mgr event 01:31:57: SSS MGR [uid:10]: Updating ID Mgr with the following keys: username "user1" aaa-unique-id 11 (0xB) 01:31:57: SSS MGR [uid:10]: Handling Policy Send More Keys action 01:31:57: SSS PM [uid:10][63D5D594]: AAA author needed for registered user 01:31:57: SSS PM [uid:10][63D5D594]: SGBP disabled: SGF author not needed 01:31:57: SSS MGR [uid:10]: Got reply Local Terminate from PM 01:31:57: SSS MGR [uid:10]: Handling Connect Local Service action 01:31:57: SSS MGR [uid:10]: Need the resource type determined key 01:31:57: SSS MGR [uid:10]: Handling Need More Keys action 01:31:57: SSS MGR [uid:10]: Not yet ready to start the Local service 01:31:57: AAA/AUTHEN/PPP (0000000B): Pick method list 'default' 01:31:57: RADIUS/ENCODE(0000000B):Orig. component type = PPoE 01:31:57: RADIUS: AAA Unsupported Attr: client-mac-address[42] 14 01:31:57: RADIUS: 30 30 30 61 2E 34 32 37 64 2E 65 63 [ 000a.427d.ec] 01:31:57: RADIUS: AAA Unsupported Attr: interface [171] 7 01:31:57: RADIUS: 36 2F 30 2F 30 [ 6/0/0] 01:31:57: RADIUS(0000000B): Config NAS IP: 0.0.0.0 01:31:57: RADIUS/ENCODE(0000000B): acct_session_id: 11 01:31:57: RADIUS(0000000B): sending 01:31:57: RADIUS/ENCODE: Best Local IP-Address 9.2.76.2 for Radius-Server 9.2.36.253 01:31:57: RADIUS(0000000B): Send Access-Request to 9.2.36.253:1645 id 1645/10, len 86 01:31:57: RADIUS: authenticator FD E8 32 9A 71 15 50 44 - BE FF 19 D0 09 D4 8D 15 01:31:57: RADIUS: Framed-Protocol [7] 6 PPP [1] 01:31:57: RADIUS: User-Name [1] 9 "user1" 01:31:57: RADIUS: User-Password [2] 18 * 01:31:57: RADIUS: NAS-Port-Type [61] 6 Virtual [5] 01:31:57: RADIUS: NAS-Port [5] 6 0 01:31:57: RADIUS: NAS-Port-Id [87] 9 "6/0/0/0" 01:31:57: RADIUS: Service-Type [6] 6 Framed [2] 01:31:57: RADIUS: NAS-IP-Address [4] 6 9.2.76.2 01:31:57: RADIUS: Received from id 1645/10 9.2.36.253:1645, Access-Accept, len 32 01:31:57: RADIUS: authenticator E4 68 43 2C 2F E7 B4 57 - 05 70 FF B1 22 13 E8 0F 01:31:57: RADIUS: Idle-Timeout [28] 6 200 01:31:57: RADIUS: Service-Type [6] 6 Framed [2] 01:31:57: RADIUS(0000000B): Received from id 1645/10 01:31:57: SSS INFO: Element type is Auth-User = "user1" 01:31:57: SSS INFO: Element type is AAA-Attr-List = C5000100 01:31:57: SSS INFO: Element type is idletime 200 (0xC8) 01:31:57: SSS INFO: Element type is service-type 2 [Framed] 01:31:57: SSS INFO: Element type is Resource-Determined = 1 (YES) 01:31:57: SSS INFO: Element type is Access-Type = 0 (PPP) 01:31:57: SSS INFO: Element type is Protocol-Type = 0 (PPP) 01:31:57: SSS INFO: Element type is Final = 1 (YES) 01:31:57: SSS MGR [uid:10]: Handling Connect Local Service action 01:31:57: SSS MGR [uid:10]: Rcvd an AAA attr list from SIP, pushing it to the PM 01:31:57: SSS MGR [uid:10]: Handling Send Policy Push Cng action


DB-30

May 2008


01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 63D5D594 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57: 01:31:57:

SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS

AAA AAA AAA AAA AAA AAA MGR AAA AAA AAA AAA AAA AAA AAA AAA

AUTHOR [uid:10]: Root SIP PPPoE AUTHOR [uid:10]: Enable PPPoE parsing AUTHOR [uid:10]: Enable PPP parsing AUTHOR [uid:10]: Active key set to Unauth-User AUTHOR [uid:10]: Authorizing key user1 AUTHOR [uid:10]: Spoofed AAA reply sent for key user1 [uid:10]: Not yet ready to start the Local service AUTHOR [uid:10]: Received an AAA pass AUTHOR [uid:10]: SIP PPP[60A0504C] parsed as Success AUTHOR [uid:10]: SIP PPP[61571560] parsed as Ignore AUTHOR [uid:10]: SIP PPPoE[61599FB0] parsed as Success AUTHOR [uid:10]: SIP Root parser not installed AUTHOR [uid:10]: No service authorization info found AUTHOR [uid:10]: Active Handle present AUTHOR [uid:10]: Freeing Active Handle; SSS Policy Context Handle =

SSS AAA AUTHOR [uid:10]: Free request SSS MGR [uid:10]: Got reply Apply Config from PM SSS MGR [uid:10]: Successfully applied policy config SSS MGR [uid:10]: Handling Connect Local Service action CCM: LTERM Required SSS LTERM [uid:10]: Processing Local termination request SSS LTERM [uid:10]: Sent create-clone request to vtemplate manager SSS LTERM [uid:10]: Created vaccess interface Vi3 CCM: LTERM Ready SSS LTERM [uid:10]: Segment provision successful SSS MGR [uid:10]: Handling Local Service Connected action SSS MGR [uid:10]: Apply for Vi3: segment 4114, owner 3825205277 SSS MGR [uid:10]: Interface config 212C27B8 SSS MGR [uid:10]: Per-user config 2146BD48 SSS LTERM [uid:10]: Switching session provisioned SSS MGR [uid:10]: Handling Local Service Connected, Features Applied action %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up SSS LTERM [uid:10]: Installed Vi3 process path switching vector SSS LTERM [uid:10]: Installed Vi3 fastsend path switching vector AAA/BIND(0000000B): Bind i/f Virtual-Access3 CCM: PPPoE Ready CCM: PPP Ready CCM: PPP Old State[Not Ready] Event[All Ready] CCM: New State[Ready] AAA/CCM/(0000000B): No of sync avps = 4 Total sync data len = 94 CCM: PPP Adding Data Type[6] Subtype[0] Length[14] CCM: PPP Adding Data Type[5] Subtype[0] Length[10] CCM: PPP Adding Data Type[8] Subtype[0] Length[6] CCM: PPP Adding Data Type[7] Subtype[0] Length[0] CCM: PPP Adding Data Type[1] Subtype[0] Length[8] CCM: PPP Adding Data Type[41] Subtype[0] Length[4] CCM: PPPoE Adding Data Type[1] Subtype[0] Length[54] CCM: PPPoE Adding Data Type[2] Subtype[0] Length[2] CCM: PPPoE Adding Data Type[5] Subtype[0] Length[4] CCM: PPPoE Adding Data Type[6] Subtype[0] Length[4] CCM: PPPoE Adding Data Type[7] Subtype[0] Length[20] CCM: PPPoE Adding Data Type[8] Subtype[0] Length[16] CCM: AAA Adding Data Type[1] Subtype[0] Length[4] AAA/CCM/(0000000B): Adding sync avp [AAA Unique Id] Length = 4 CCM: AAA Adding Data Type[2] Subtype[0] Length[2] AAA/CCM/(0000000B): Adding sync avp [AAA Authen Method Index] Length = 2 CCM: AAA Adding Data Type[3] Subtype[0] Length[4] AAA/CCM/(0000000B): Adding sync avp [AAA Acct Sess id] Length = 4 CCM: AAA Adding Data Type[4] Subtype[0] Length[84] AAA/CCM/(0000000B): Adding sync avp [AAA Author Data] Length = 84 AAA/CCM: Adding author data entry 32 CCM: LTERM Adding Data Type[1] Subtype[0] Length[4] SSS LTERM [uid:10]: LTERM segment handle synced


DB-31


01:31:57: CCM: Send[Sync Session] Length[240] NumItems[17] Event[0x0] 01:31:57: Client[PPP] Type[6] Subtype[0] Length[14] 01:31:57: 01 04 05 D4 03 04 C0 23 05 06 03 F4 37 79 01:31:57: Client[PPP] Type[5] Subtype[0] Length[10] 01:31:57: 01 04 05 D4 05 06 9A 6B 68 FE 01:31:57: Client[PPP] Type[8] Subtype[0] Length[6] 01:31:57: 03 06 07 01 01 01 01:31:57: Client[PPP] Type[7] Subtype[0] Length[0] 01:31:57: 01:31:57: Client[PPP] Type[1] Subtype[0] Length[8] 01:31:57: 73 75 6D 61 6E 74 68 00 01:31:57: Client[PPP] Type[41] Subtype[0] Length[4] 01:31:57: 00 00 00 02 01:31:57: Client[PPPoE] Type[1] Subtype[0] Length[54] 01:31:57: 00 03 A0 10 22 90 00 0A 42 7D EC 38 88 63 11 19 01:31:57: 00 00 00 22 01 02 00 06 61 61 61 5F 68 61 01 04 01:31:57: 00 10 98 99 BB 6D 59 B8 35 33 0B FB 14 B9 07 EB 01:31:57: 83 B4 01 01 00 00 01:31:57: Client[PPPoE] Type[2] Subtype[0] Length[2] 01:31:57: 00 0A 01:31:57: Client[PPPoE] Type[5] Subtype[0] Length[4] 01:31:57: 00 00 10 09 01:31:57: Client[PPPoE] Type[6] Subtype[0] Length[4] 01:31:57: 00 00 10 12 01:31:57: Client[PPPoE] Type[7] Subtype[0] Length[20] 01:31:57: 00 02 06 00 00 00 A6 B8 00 00 00 00 00 00 00 2A 01:31:57: 00 00 FF FF 01:31:57: Client[PPPoE] Type[8] Subtype[0] Length[16] 01:31:57: 00 00 00 03 00 00 00 00 00 00 00 19 00 00 00 1D 01:31:57: 01:31:57: Client[AAA] Type[1] Subtype[0] Length[4] 01:31:57: 00 00 00 0B 01:31:57: Client[AAA] Type[2] Subtype[0] Length[2] 01:31:57: 00 00 01:31:57: Client[AAA] Type[3] Subtype[0] Length[4] 01:31:57: 00 00 00 0B 01:31:57: Client[AAA] Type[4] Subtype[0] Length[84] 01:31:57: 00 00 00 00 00 00 00 00 63 E8 73 D0 00 00 00 0B 01:31:57: 64 02 FE 71 00 00 00 00 00 00 00 00 00 00 00 00 01:31:57: 00 00 00 04 00 00 00 01 00 00 00 20 00 00 00 00 01:31:57: 58 00 00 09 02 0A 00 20 E4 68 43 2C 2F E7 B4 57 01:31:57: 05 70 FF B1 22 13 E8 0F 1C 06 00 00 00 C8 06 06 01:31:57: 00 00 00 02 01:31:57: Client[LTERM] Type[1] Subtype[0] Length[4] 01:31:57: 00 00 20 13 01:31:57: CCM: New State[Dyn Sync] 01:31:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up Logs on Standby ================ 01:21:16: CCM ISSU: Received negotiation message type [ISSU_RC_USER_MESSAGE_COMP] 01:21:16: CCM: Receive[Sync Session] Length[240] NumItems[17] Flags[0x0] 01:21:16: CCM: New State[Not Ready] 01:21:16: Client[PPP] Type[6] Subtype[0] Length[14] 01:21:16: 01 04 05 D4 03 04 C0 23 05 06 03 F4 37 79 01:21:16: Client[PPP] Type[5] Subtype[0] Length[10] 01:21:16: 01 04 05 D4 05 06 9A 6B 68 FE 01:21:16: Client[PPP] Type[8] Subtype[0] Length[6] 01:21:16: 03 06 07 01 01 01 01:21:16: Client[PPP] Type[7] Subtype[0] Length[0] 01:21:16: 01:21:16: Client[PPP] Type[1] Subtype[0] Length[8]


DB-32

May 2008


01:21:16: 73 75 6D 61 6E 74 68 00 01:21:16: Client[PPP] Type[41] Subtype[0] Length[4] 01:21:16: 00 00 00 02 01:21:16: Client[PPPoE] Type[1] Subtype[0] Length[54] 01:21:16: 00 03 A0 10 22 90 00 0A 42 7D EC 38 88 63 11 19 01:21:16: 00 00 00 22 01 02 00 06 61 61 61 5F 68 61 01 04 01:21:16: 00 10 98 99 BB 6D 59 B8 35 33 0B FB 14 B9 07 EB 01:21:16: 83 B4 01 01 00 00 01:21:16: Client[PPPoE] Type[2] Subtype[0] Length[2] 01:21:16: 00 0A 01:21:16: Client[PPPoE] Type[5] Subtype[0] Length[4] 01:21:16: 00 00 10 09 01:21:16: Client[PPPoE] Type[6] Subtype[0] Length[4] 01:21:16: 00 00 10 12 01:21:16: Client[PPPoE] Type[7] Subtype[0] Length[20] 01:21:16: 00 02 06 00 00 00 A6 B8 00 00 00 00 00 00 00 2A 01:21:16: 00 00 FF FF 01:21:16: Client[PPPoE] Type[8] Subtype[0] Length[16] 01:21:16: 00 00 00 03 00 00 00 00 00 00 00 19 00 00 00 1D 01:21:16: 01:21:16: Client[AAA] Type[1] Subtype[0] Length[4] 01:21:16: 00 00 00 0B 01:21:16: Client[AAA] Type[2] Subtype[0] Length[2] 01:21:16: 00 00 01:21:16: Client[AAA] Type[3] Subtype[0] Length[4] 01:21:16: 00 00 00 0B 01:21:16: Client[AAA] Type[4] Subtype[0] Length[84] 01:21:16: 00 00 00 00 00 00 00 00 63 E8 73 D0 00 00 00 0B 01:21:16: 64 02 FE 71 00 00 00 00 00 00 00 00 00 00 00 00 01:21:16: 00 00 00 04 00 00 00 01 00 00 00 20 00 00 00 00 01:21:16: 58 00 00 09 02 0A 00 20 E4 68 43 2C 2F E7 B4 57 01:21:16: 05 70 FF B1 22 13 E8 0F 1C 06 00 00 00 C8 06 06 01:21:16: 00 00 00 02 01:21:16: Client[LTERM] Type[1] Subtype[0] Length[4] 01:21:16: 00 00 20 13 01:21:16: CCM:PPPoE Recreate Session Active[0x58000009] Standby[0x98000009] 01:21:16: CCM: PPPoE Required 01:21:16: CCM: PPP Required 01:21:16: CCM: LTERM Required 01:21:16: CCM: PPPoE is Initiator 01:21:16: AAA/CCM/: return checkpointed aaa id = 0000000B 01:21:16: Adding cache entry for id B 01:21:16: Author cache len 84 84 84 01:21:16: AAA/CCM/(0000000B):return acct_sess_id = 11 01:21:16: CCM: AAA Ready 01:21:16: AAA/CCM/(0000000B): AAA sso init completed successfully 01:21:16: SSS INFO: Element type is Access-Type = 3 (PPPoE) 01:21:16: SSS INFO: Element type is Protocol-Type = 0 (PPP) 01:21:16: SSS INFO: Element type is Media-Type = 1 (Ethernet) 01:21:16: SSS INFO: Element type is Switch-Id = 4105 (00001009) 01:21:16: SSS INFO: Element type is Segment-Hdl = 4114 (00001012) 01:21:16: SSS INFO: Element type is AAA-Id = 11 (0000000B) 01:21:16: SSS INFO: Element type is AccIe-Hdl = 4127195145 (F6000009) 01:21:16: SSS INFO: Element type is SHDB-Handle = 2550136841 (98000009) 01:21:16: SSS INFO: Element type is Input Interface = "GigabitEthernet6/0/0" 01:21:16: SSS MGR [uid:10]: Sending a Session Assert ID Mgr event 01:21:16: SSS MGR [uid:10]: Updating ID Mgr with the following keys: aaa-unique-id 11 (0xB) 01:21:16: SSS MGR [uid:10]: Handling Policy Service Authorize action (1 pending sessions) 01:21:16: SSS PM [uid:10][63D6963C]: RM/VPDN disabled: RM/VPDN author not needed 01:21:16: SSS MGR [uid:10]: Got reply Need More Keys from PM 01:21:16: SSS MGR [uid:10]: Handling Need More Keys action 01:21:16: SSS INFO: Element type is Unauth-User = "user1" 01:21:16: SSS INFO: Element type is AccIe-Hdl = 4127195145 (F6000009)


DB-33


01:21:16: SSS INFO: Element type is AAA-Id = 11 (0000000B) 01:21:16: SSS INFO: Element type is Access-Type = 0 (PPP) 01:21:16: SSS INFO: Element type is Protocol-Type = 0 (PPP) 01:21:16: SSS MGR [uid:10]: Sending a Session Update ID Mgr event 01:21:16: SSS MGR [uid:10]: Updating ID Mgr with the following keys: username "user1" aaa-unique-id 11 (0xB) 01:21:16: SSS MGR [uid:10]: Handling Policy Send More Keys action 01:21:16: SSS PM [uid:10][63D6963C]: SGBP disabled: SGF author not needed 01:21:16: SSS MGR [uid:10]: Got reply Local Terminate from PM 01:21:16: SSS MGR [uid:10]: Handling Connect Local Service action 01:21:16: SSS MGR [uid:10]: Need the resource type determined key 01:21:16: SSS MGR [uid:10]: Handling Need More Keys action 01:21:16: SSS MGR [uid:10]: Not yet ready to start the Local service 01:21:16: AAA/CCM/(0000000B):return authen_method_index = 0 01:21:16: RADIUS/ENCODE(0000000B):Orig. component type = PPoE 01:21:16: RADIUS: AAA Unsupported Attr: client-mac-address[42] 14 01:21:16: RADIUS: 30 30 30 61 2E 34 32 37 64 2E 65 63 [ 000a.427d.ec] 01:21:16: RADIUS: AAA Unsupported Attr: interface [171] 7 01:21:16: RADIUS: 36 2F 30 2F 30 [ 6/0/0] 01:21:16: RADIUS(0000000B): Config NAS IP: 0.0.0.0 01:21:16: RADIUS/ENCODE(0000000B): acct_session_id: 11 01:21:16: RADIUS(0000000B): sending 01:21:16: RADIUS/ENCODE: Best Local IP-Address 2.1.1.1 for Radius-Server 9.2.36.253 01:21:16: RADIUS(0000000B): Send Access-Request to 9.2.36.253:1645 id 1645/10, len 86 01:21:16: RADIUS: authenticator 14 48 25 90 A5 7B 53 02 - 11 05 01 13 6D 34 E2 04 01:21:16: RADIUS: Framed-Protocol [7] 6 PPP [1] 01:21:16: RADIUS: User-Name [1] 9 "user1" 01:21:16: RADIUS: User-Password [2] 18 * 01:21:16: RADIUS: NAS-Port-Type [61] 6 Virtual [5] 01:21:16: RADIUS: NAS-Port [5] 6 0 01:21:16: RADIUS: NAS-Port-Id [87] 9 "6/0/0/0" 01:21:16: RADIUS: Service-Type [6] 6 Framed [2] 01:21:16: RADIUS: NAS-IP-Address [4] 6 2.1.1.1 01:21:16: RADIUS: Cached response 01:21:16: RADIUS: authenticator E4 68 43 2C 2F E7 B4 57 - 05 70 FF B1 22 13 E8 0F 01:21:16: RADIUS: Idle-Timeout [28] 6 200 01:21:16: RADIUS: Service-Type [6] 6 Framed [2] 01:21:16: RADIUS(0000000B): Received from id 1645/10 01:21:16: SSS INFO: Element type is Auth-User = "user1" 01:21:16: SSS INFO: Element type is AAA-Attr-List = 20000100 01:21:16: SSS INFO: Element type is idletime 200 (0xC8) 01:21:16: SSS INFO: Element type is service-type 2 [Framed] 01:21:16: SSS INFO: Element type is Resource-Determined = 1 (YES) 01:21:16: SSS INFO: Element type is Access-Type = 0 (PPP) 01:21:16: SSS INFO: Element type is Protocol-Type = 0 (PPP) 01:21:16: SSS INFO: Element type is Final = 1 (YES) 01:21:16: SSS MGR [uid:10]: Handling Connect Local Service action 01:21:16: SSS MGR [uid:10]: Rcvd an AAA attr list from SIP, pushing it to the PM 01:21:16: SSS MGR [uid:10]: Handling Send Policy Push Cng action 01:21:16: SSS MGR [uid:10]: Not yet ready to start the Local service 01:21:16: SSS MGR [uid:10]: Got reply Apply Config from PM 01:21:16: SSS MGR [uid:10]: Successfully applied policy config 01:21:16: SSS MGR [uid:10]: Handling Connect Local Service action 01:21:16: CCM: LTERM Required 01:21:16: SSS LTERM [uid:10]: Processing Local termination request 01:21:16: SSS LTERM [uid:10]: Sent create-clone request to vtemplate manager 01:21:16: SSS LTERM [uid:10]: Created vaccess interface Vi3 01:21:16: CCM: LTERM Ready 01:21:16: SSS LTERM [uid:10]: Segment provision successful 01:21:16: SSS MGR [uid:10]: Handling Local Service Connected action 01:21:16: SSS MGR [uid:10]: Apply for Vi3: segment 4114, owner 2566914077 01:21:16: SSS MGR [uid:10]: Interface config 218170B8 01:21:16: SSS MGR [uid:10]: Per-user config 63E06550


DB-34

May 2008


01:21:16: 01:21:16: 01:21:16: 01:21:16: 01:21:16: 01:21:16: 01:21:16: 01:21:16:

SSS LTERM [uid:10]: Switching session provisioned SSS MGR [uid:10]: Handling Local Service Connected, Features Applied action SSS LTERM [uid:10]: Installed Vi3 process path switching vector SSS LTERM [uid:10]: Installed Vi3 fastsend path switching vector CCM: PPPoE Ready CCM: PPP Ready CCM: PPP Old State[Not Ready] Event[All Ready] CCM: New State[Ready]


Related Commands

debug aaa redundancy Field Descriptions

Field

Description

(0000000B)

AAA unique id for the session.

Adding sync avp

Adding synchronization attribute value pair (AVP).

[AAA Unique Id]

The AAA synchronization data type.

Command

Description

debug ccm-manager

Displays debugging information about Cisco CallManager.


DB-35

Debug Commands debug aaa sg-server selection

debug aaa sg-server selection To obtain information about why the RADIUS and TACACS+ server group system in a router is choosing a particular server, use the debug aaa sg-server selection command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug aaa sg-server selection no debug aaa sg-server selection

Syntax Description


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(1)


12.2(28)SB

This command was extended for RADIUS server load balancing to show which server is selected on the basis of a load balancing algorithm.

12.4(11)T

This command was integrated into Cisco IOS Release 12.4(11)T.

12.2SX


12.2(33)SRC


Examples

The following example shows that debugging has been set to display information about server selection: Router# debug aaa sg-server selection

The following two debug outputs display the behavior of RADIUS transactions within a server group with the server-reorder-on-failure feature configured. Debug 1

In the following sample output, the RADIUS server-reorder-on-failure feature is configured. The server retransmits are set to 0 (so each server is attempted only once before failover to the next configured server), and the transmissions per transaction are set to 4 (the transmissions will stop on the third failover). The third server in the server group (192.0.2.118) has accepted the transaction on the third transmission (second failover). 00:38:35: 00:38:53: 00:38:53: 00:38:58: 00:38:58: 00:38:59: 00:38:59: 00:38:59: 00:38:59: attribute

%SYS-5-CONFIG-I: Configured from console by console RADIUS/ENCODE(OOOOOOOF) : ask "Username: " RADIUS/ENCODE (0000000F) : send packet; GET-USER RADIUS/ENCODE (0000000F) : ask "Password: " RADIUS/ENCODE(0000000F) : send packet; GET-PASSWORD RADIUS: AAA Unsupported [152] 4 RADIUS: 7474 [tt] RADIUS (0000000F) : Storing nasport 2 in rad-db RADIUS/ENCODE(0000000F) : dropping service type, "radius-server 6 on-for-login-auth" is off


DB-36

May 2008


00:38:59: RADIUS (0000000F) : Config NAS IP: 192.0.2.4 00:38:59: RADIUS/ENCODE (0000000F) : acct-session-id: 15 00:38:59: RADIUS (0000000F) : sending 00:38:59: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.1 00:38:59: RAPIUS(0000000F) : Send Access-Request to 192.0.2.1:1645 id 21645/11, len 78 00:38:59: RADIUS:: authenticator 4481 E6 65 2D 5F 6F OA -lE F5 81 8F 4E 1478 9C 00:38:59: RADIUS: User-Name [1] 7 "username" 00:38:59: RADIUS: User-Password [2] 18 * 00:38:59: RADIUS: NAS-Port fSl 6 2 00:~8:59: RADIUS: NAS-Port-Type [61] 6 Virtual [5] 00:38:59: RADIUS: Calling-Station-Id [31] 15 "192.0.2.23" 00:39:00: RADIUS: NAS-IP-Address [4] 6 192.0.2.130 00:39:02: RADIUS: Fail-over to (192.0.2.2:1645,1646) for id 21645/11 00:39:02: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.2 00:39:04: RADIUS: Fail-over to (192.0.2.118:1645,1646) for id 21645/11 00:39:04: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.118 00:39:05: RADIUS: Received from id 21645/11 192.0.2.118:1645, Access-Accept, len 26 00:39:05: RADIUS: authenticator 5609 56 F9 64 4E DF 19- F3 A2 DD 73 EE 3F 9826 00:39:05: RADIUS: Service-Type [6] 6 Login [1]

Debug 2

In the following sample output, the RADIUS server-reorder-on-failure feature is configured. The server retransmits are set to 0, and the transmissions per transaction are set to 8. In this transaction, the transmission to server 192.0.2.1 has failed on the eighth transmission. 00:42:30: RADIUS(00000011): Received from id 21645/13 00:43:34: RADIUS/ENCODE(00000012) : ask "Username: " 00:43:34: RADIUS/ENCODE(00000012) : send packet; GET-USER 00:43:39: RADIUS/ENCODE(00000012) : ask "Password: " 00:43:39: RADIUS/ENCODE(00000012) : send packet; GET-PASSWORD 00:43:40: RADIUS: AAA Unsupported [152] 4 00:43:40: RADIUS: 7474 [tt] 00:43:40: RADIUS(00000012) : Storing nasport 2 in rad-db 00:43:40: RADIUS/ENCODE(00000012): dropping service type, "radius-server attribute 6 on-for-login-auth" is off 00:43:40: RADIUS(00000012) : Co~fig NAS IP: 192.0.2.4 00:43:40: RADIUS/ENCODE(00000012) : acct-session-id: 18 00:43:40: RADIUS(00000012) : sending 00:43:40: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.118 00:43:40: RADIUS(00000012) : Send Access-Request to 192.0.2.118:1645 id 21645/14, len 78 00:43:40: RADIUS: authenticator B8 OA 51 3A AF A6 0018 -B3 2E 94 5E 07 OB 2A 00:43:40: RADIUS: User-Name [1] 7 "username" 00:43:40: RADIUS: User-Password [2] 18 * 00:43:40: RADIUS: NAS-Port [5] 6 2 00:43:40: RADIUS: NAS-Port-Type [61] 6 Virtual [5] 00:43:40: RADIUS: Calling-Station-]d [31] 15 "192.0.2.23" 00:43:40: RADIUS: NAS-IP-Address [4] 6 192.0.2.130 00:43:42: RADIUS: Fail-over to (192.0.2,1:1645,1646) for id 21645/14 00:43:42: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.1 00:43:44: RADius: Fail-over to (192.0.2.2:1645,1646) for id 21645/14 00:43:44: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.2 00:43:46: RADIUS: Fail-over to (192.0.2.118:1645,1646) for id 21645/14 00:43:46: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.118 00:43:48: RADIUS: Fail-over to (192.0.2.1:1645,1646) for id 21645/14 00:43:48: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.1 00:43:50: RADIUS: Fail-over to (192.0.2.2:1645,1646) for id 21645/14 00:43:50: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.2 00:43:52: RADIUS: Fail-over to (192.0.2.118:1645,1646) for id 21645/14 00:43:52: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.118 00:43:54: RADIUS: Fail-over to (192.0.2.1:1645,1646) for id 21645/14 00:43:54: RADIUS/ENCODE: Best Local IP-Address 192.0.2.130 for Radius-Server 192.0.2.1 00:43:56: RADIUS: No response from (192.0.2.1:1645,1646) for id 21645/14


DB-37


00:43:56:RADIUS/DECODE: parse response no app start; FAIL 00:43:56: RADIUS/DECODE: parse response;FAIL

The field descriptions are self-explanatory. Debug 3

In the following sample output, the RADIUS server load balancing feature is enabled with a batch size of 3. The server selection, based on the load balancing algorithm, is shown as five access-requests that are being sent to the server group. Router# debug aaa sg-server selection Jul 16 03:15:05: Jul 16 03:15:05: server. Jul 16 03:15:05: Jul 16 03:15:05: server. Jul 16 03:15:05: Jul 16 03:15:05: server. Jul 16 03:15:05: Jul 16 03:15:05: server. Jul 16 03:15:05: Jul 16 03:15:05: Jul 16 03:15:05: Jul 16 03:15:05: Jul 16 03:15:05: Jul 16 03:15:05: Jul 16 03:15:05:

AAA/SG/SERVER_SELECT: Obtaining least loaded server. AAA/SG/SERVER_SELECT: [3] transactions remaining in batch. Reusing AAA/SG/SERVER_SELECT: Obtaining least loaded server. AAA/SG/SERVER_SELECT: [2] transactions remaining in batch. Reusing AAA/SG/SERVER_SELECT: Obtaining least loaded server. AAA/SG/SERVER_SELECT: [1] transactions remaining in batch. Reusing AAA/SG/SERVER_SELECT: Obtaining least loaded server. AAA/SG/SERVER_SELECT: No more transactions in batch. Obtaining a new AAA/SG/SERVER_SELECT: AAA/SG/SERVER_SELECT: AAA/SG/SERVER_SELECT: AAA/SG/SERVER_SELECT: AAA/SG/SERVER_SELECT: AAA/SG/SERVER_SELECT: AAA/SG/SERVER_SELECT:

Obtaining a new least loaded server. Server[0] load: 3 Server[1] load: 0 Server[2] load: 0 Selected Server[1] with load 0 [3] transactions remaining in batch. Obtaining least loaded server.

Jul 16 03:15:05: AAA/SG/SERVER_SELECT: [2] transactions remaining in batch. Reusing server. The field descriptions are self-explanatory.

Related Commands

Command

Description

load-balance

Enables RADIUS server load balancing for named RADIUS server groups.

radius-server load-balance

Enables RADIUS server load balancing for the global RADIUS server group.

radius-server retry method reorder

Specifies the reordering of RADIUS traffic retries among a server group.

radius-server transaction max-tries

Specifies the maximum number of transmissions per transaction that may be retried on a RADIUS server.

test aaa group

Tests RADIUS load balancing server response manually.


DB-38

May 2008

Debug Commands debug aaa test

debug aaa test To show when the idle timer or dead timer has expired, when test packets are being sent, server response status, and the server state for RADIUS server load balancing, use the debug aaa test command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug aaa test no debug aaa test

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.4(11)T


12.2SX


12.2(33)SRC


Examples

In the following sample output, the RADIUS server load balancing feature is enabled. The idle timer has expired. Router# debug aaa test Router# Jul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) quarantined. Jul 16 00:07:01: AAA/SG/TEST: Sending test request(s) to server (192.0.2.245:1700,1701) Jul 16 00:07:01: AAA/SG/TEST: Sending 1 Access-Requests, 1 Accounting-Requests in current batch. Jul 16 00:07:01: AAA/SG/TEST(Req#: 1): Sending test AAA Access-Request. Jul 16 00:07:01: AAA/SG/TEST(Req#: 1): Sending test AAA Accounting-Request. Jul 16 00:07:01: AAA/SG/TEST: Obtained Test response from server (192.0.2.245:1700,1701) Jul 16 00:07:01: AAA/SG/TEST: Obtained Test response from server (192.0.2.245:1700,1701) Jul 16 00:07:01: AAA/SG/TEST: Necessary responses received from server (192.0.2.245:1700,1701) Jul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) marked ALIVE. Idle timer set for 60 sec(s). Jul 16 00:07:01: AAA/SG/TEST: Server (192.0.2.245:1700,1701) removed from quarantine.

Related Commands

Command

Description

load-balance

Enables RADIUS server load balancing for named RADIUS server groups.

radius-server host

Enables RADIUS automated testing for load balancing.


DB-39

Debug Commands debug aaa test

Command

Description

radius-server load-balance

Enables RADIUS server load balancing for the global RADIUS server group.

test aaa group

Tests RADIUS load balancing server response manually.


DB-40

May 2008

Debug Commands debug acircuit checkpoint

debug acircuit checkpoint To enable the display of attachment circuit (AC) events when Any Transport over MPLS (AToM) is configured for nonstop forwarding/stateful switchover (NSF/SSO) and Graceful Restart, use the debug acircuit checkpoint command in privileged EXEC mode. To disable the display of these messages, use the no form of this command. debug acircuit checkpoint no debug acircuit checkpoint

Syntax Description


Defaults

Debugging of the AToM NSF/SSO and Graceful Restart feature is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB.

12.2SX


Usage Guidelines

Use debug commands with care. They use a significant amount of CPU time and can affect system performance.

Examples

The debug acircuit checkpoint command is issued on the active RP: Router# debug mpls l2transport checkpoint Router# debug acircuit checkpoint Router# show debug AToM HA: AToM checkpointing events and errors debugging is on AC HA: Attachment Circuit Checkpoint debugging is on Router# conf terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface Fa5/1/1.2 Router(config-subif)# xconnect 10.55.55.2 1002 pw-class mpls AToM HA [10.55.55.2, 1002]: Build provision msg, SSM sw/seg 8192/8194 [0x2000/0x2002] PW i d 9216 [0x2400] local label 21 AC HA: Dynamic Sync. Event:4 Sw:8192[2000] Se:16385[4001] AToM HA: CF sync send complete AC HA CF: Sync send complete. Code:0


DB-41

Debug Commands debug acircuit checkpoint

On the standby RP, the following messages indicate that it receives checkpointing data: AC HA [10.55.55.2, 1002]: Add to WaitQ. Flags:1 AToM HA [10.55.55.2, 1002]: Received 32-byte provision version 1 CF message AC HA CF: ClientId:89, Entity:0 Length:40 AToM HA [10.55.55.2, 1002]: Process chkpt msg provision [1], ver 1 AToM HA [10.55.55.2, 1002]: Reserved SSM sw/seg 8192/8194 [0x2000/0x2002] PW id 9216 [0x24 00] AC HA: Process Msg:35586. Ptr:44CBFD90. Val:0 AC HA: Sync. Event:4 CktType:4 Sw:8192[2000] Se:16385[4001] AC HA [10.55.55.2, 1002]: Remove from WaitQ. Flags:1[OK][OK]

During a switchover from the active to the backupRoute Processor, the debug messages look similar to the following: %HA-5-MODE: Operating mode is hsa, configured mode is sso. AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Opr:5, St:STANDBY HO T, PSt:ACTIVE AToM HA: CID 84, Seq 715, Status RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Op 5, State STANDB Y HOT, Peer ACTIVE AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_PRESENCE, Opr:0, St:STANDBY HOT, PSt:ACTIVE AToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_PRESENCE, Op 0, State STANDBY HOT, Peer AC TIVE AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_COMM, Opr:0, St:STANDBY HOT, PSt:DISABLED AToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_COMM, Op 0, State STANDBY HOT, Peer DISABL ED %HA-2-CUTOVER_NOTICE: Cutover initiated. Cease all console activity until system restarts. %HA-2-CUTOVER_NOTICE: Do not add/remove RSPs or line cards until switchover completes. %HA-2-CUTOVER_NOTICE: Deinitializing subsystems... %OIR-6-REMCARD: Card removed from slot 4, interfaces disabled %OIR-6-REMCARD: Card removed from slot 5, interfaces disabled %OIR-6-REMCARD: Card removed from slot 9, interfaces disabled %HA-2-CUTOVER_NOTICE: Reinitializing subsystems... %HA-2-CUTOVER_NOTICE: System preparing to restart... %HA-5-NOTICE: Resuming initialization... AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_REDUNDANCY_MODE_CHANGE, Opr:7, St:STANDBY HOT, PS t:DISABLED . . . %LDP-5-GR: LDP restarting gracefully. Preserving forwarding state for 250 seconds. AC HA RF: CId:83, Seq:710, Sta:RF_PROG_ACTIVE, Opr:0, St:ACTIVE, PSt:DISABLED AToM HA: CID 84, Seq 715, Event RF_PROG_ACTIVE, Op 0, State ACTIVE, Peer DISABLED AC HA: Process Msg:35588. Ptr:0. Val:0 AC HA: Switchover: Standby->Active AC HA RF: Reconciling

Related Commands

Command

Description

debug mpls l2transport checkpoint

Enables the display of AToM events when AToM is configured for NSF/SSO and Graceful Restart.


DB-42

May 2008

Debug Commands debug acircuit

debug acircuit To display errors and events that occur on the attachment circuits (the circuits between the provider edge (PE) and customer edge (CE) routers), use the debug acircuit command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug acircuit {error | event} no debug acircuit {error | event}

Syntax Description

error

Displays errors that occur in attachment circuits.

event

Displays events that occur in attachment circuits.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(23)S


12.2(14)S

This command was integrated into Cisco IOS Release 12.2(14)S.

12.2(15)T


12.2(25)S


12.2(27)SBC

Support for this command was integrated into Cisco IOS Release 12.2(27)SBC.

12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug acircuit command to identify provisioning events, setup failures, circuit up and down events, and configuration failures on attachment circuits. An attachment circuit connects a PE router to a CE router. A router can have many attachment circuits. The attachment circuit manager controls all the attachment circuits from one central location. Therefore, when you enable the debug messages for the attachment circuit, you receive information about all the attachment circuits.

Examples

The following is sample output from the debug acircuit event command when you enable an interface: Router# debug acircuit event *Jan 28 15:19:03.070: *Jan 28 15:19:03.070: acmgr_circuit_up *Jan 28 15:19:03.070: *Jan 28 15:19:03.070: *Jan 28 15:19:03.070:

ACLIB: ac_cstate() Handling circuit UP for interface Se2/0 ACLIB [11.0.1.1, 200]: pthru_intf_handle_circuit_up() calling ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-Connecting ACMGR: Receive msg Se2/0 ACMGR: circuit up event, SIP state chg down to connecting,


DB-43

Debug Commands debug acircuit

action is service request *Jan 28 15:19:03.070: Se2/0 ACMGR: Sent a sip service request *Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: AC updating switch context. *Jan 28 15:19:03.070: Se2/0 ACMGR: Rcv SIP msg: resp connect forwarded, hdl 9500001D, l2ss_hdl 700001E *Jan 28 15:19:03.070: Se2/0 ACMGR: service connected event, SIP state chg connecting to connected, action is respond forwarded *Jan 28 15:19:03.070: ACLIB: pthru_intf_response hdl is 9500001D, response is 1 *Jan 28 15:19:03.070: ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-Connected

The following is sample output from the debug acircuit event command when you disable an interface: Router# debug acircuit event *Jan 28 15:25:57.014: ACLIB: SW AC interface INTF-DOWN for interface Se2/0 *Jan 28 15:25:57.014: ACLIB [11.0.1.1, 200]: Setting new AC state to Ac-Idle *Jan 28 15:25:57.014: ACLIB: SW AC interface INTF-DOWN for interface Se2/0 *Jan 28 15:25:57.014: Se2/0 ACMGR: Receive msg *Jan 28 15:25:57.014: Se2/0 ACMGR: circuit down event, SIP state chg connected to end, action is service disconnect *Jan 28 15:25:57.014: Se2/0 ACMGR: Sent a sip service disconnect *Jan 28 15:25:57.014: ACLIB [11.0.1.1, 200]: AC deleting switch context. *Jan 28 15:25:59.014: %LINK-5-CHANGED: Interface Serial2/0, changed state to administratively down *Jan 28 15:25:59.014: ACLIB: ac_cstate() Handling circuit DOWN for interface Se2/0 *Jan 28 15:26:00.014:%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to down

The following example shows output from the debug acircuit command for an xconnect session on an Ethernet interface: Router# debug acircuit 23:28:35: ACLIB [10.0.3.201, 5]: SW AC interface UP for Ethernet interface Et2/1 23:28:35: ACLIB [10.0.3.201, 5]: pthru_intf_handle_circuit_up() calling acmgr_circuit_up 23:28:35: ACLIB [10.0.3.201, 5]: Setting new AC state to Ac-Connecting 23:28:35: ACLIB [10.0.3.201, 5]: SW AC interface UP for Ethernet interface Et2/1 23:28:35: ACLIB [10.0.3.201, 5]: pthru_intf_handle_circuit_up() ignoring up event. Already connected or connecting. 23:28:35: ACMGR: Receive msg 23:28:35: Et2/1 ACMGR: circuit up event, SIP state chg down to connecting, action is service request 23:28:35: Et2/1 ACMGR: Sent a sip service request 23:28:37: %LINK-3-UPDOWN: Interface Ethernet2/1, changed state to up 23:28:38: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet2/1, changed state to up 23:28:53: Et2/1 ACMGR: Rcv SIP msg: resp connect forwarded, hdl D6000002, sss_hdl 9E00000F 23:28:53: Et2/1 ACMGR: service connected event, SIP state chg connecting to connected, action is respond forwarded 23:28:53: ACLIB: pthru_intf_response hdl is D6000002, response is 1 23:28:53: ACLIB [10.0.3.201, 5]: Setting new AC state to Ac-Connected

The command output is self-explanatory.

Related Commands

Command

Description

debug vpdn

Displays errors and events relating to L2TP configuration and the surrounding Layer 2 tunneling infrastructure.

debug xconnect

Displays errors and events related to an xconnect configuration.


DB-44

May 2008

Debug Commands debug adjacency

debug adjacency To enable the display of information about the adjacency database, use the debug adjacency command in privileged EXEC mode. To disable the display of these events, use the no form of this command. debug adjacency [epoch | ipc | state | table] [prefix] [interface] [connectionid id] [link {ipv4 | ipv6 | mpls}] no debug adjacency [epoch | ipc | state | table] [prefix] [interface] [connectionid id] [link {ipv4 | ipv6 | mpls}]

Syntax Description

epoch

(Optional) Displays adjacency epoch events.

ipc

(Optional) Displays interprocess communication (IPC) events for adjacencies.

state

(Optional) Displays adjacency system state machine events.

table

(Optional) Displays adjacency table operations.

prefix

(Optional) Displays debugging events for the specified IP address or IPv6 address. Note

On the Cisco 10000 series routers, IPv6 is supported in Cisco IOS Release 12.2(28)SB and later releases.

interface

(Optional) Displays debugging events for the specified interface. For line cards, you must specify the line card if_number (interface number). Use the show cef interface command to obtain line card if_numbers.

connectionid id

(Optional) Displays debugging events for the specified client connection identification number.

link {ipv4 | ipv6 | mpls} (Optional) Displays debugging events for the specified link type (IP, IPv6, or Multiprotocol Label Switching [MPLS] traffic). Note


Defaults

Debugging events are not displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XE

This command was introduced on the Cisco 7600 series routers.

12.1(1)E

This command was implemented on the Cisco 7600 series routers.

12.2(14)SX

This command was implemented on the Supervisor Engine 720.

12.2(25)S

This command was integrated into Cisco IOS Release 12.2(25)S, and the prefix, interface, connectionid id, and link {ipv4 | ipv6 | mpls} keywords and arguments were added.


DB-45

Debug Commands debug adjacency

Usage Guidelines

Release

Modification

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series routers.

12.2(33)SRA


12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

12.2SX


Because debugging output is assigned high priority in the CPU process, you should use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Also, you should use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use. You can use any combination of the prefix, interface, connectionid id, and link {ipv4 | ipv6 | mpls} keywords and arguments (in any order) as a filter to enable debugging for a specified subset of adjacencies.

Note

Examples


The following example shows how to display information on the adjacency database: Router# debug adjacency *Jan 27 06:22:50.543: ADJ-ios_mgr: repopulate adjs on up event for Ethernet3/0 *Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: init/update from interface *Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: set bundle to IPv6 adjacency oce *Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) no src set: allocated, setup and inserted OK *Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) src IPv6 ND: source IPv6 ND added OK *Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 (incomplete) src IPv6 ND: computed macstring (len 14): OK *Jan 27 06:22:50.543: ADJ: IPV6 adj out of Ethernet3/0, addr FE80::20C:CFFF:FEDF:6854 src IPv6 ND: made complete (macstring len 0 to 14/0 octets) 00:04:40: %LINK-3-UPDOWN: Interface Ethernet3/0, changed state to up 00:04:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet3/0, changed

Related Commands

Command

Description

clear adjacency

Clears the Cisco Express Forwarding adjacency table.

clear arp-cache

Deletes all dynamic entries from the ARP cache.

show adjacency

Displays Cisco Express Forwarding adjacency table information.

show mls cef adjacency

Displays information about the hardware Layer 3 switching adjacency node.


DB-46

May 2008

Debug Commands debug alarm-interface

debug alarm-interface To show real-time activities in the data channel or the management channel of the Alarm Interface Controller (AIC), use the debug alarm-interface command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug alarm-interface slot-number {data | management} no debug alarm-interface slot-number {data | management}

Syntax Description

slot-number

Router chassis slot where the AIC network module is installed.

data

Displays AIC serial data channel and asynchronous craft port communication activity.

management

Displays IOS-to-AIC communication activity.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XG

This command was introduced for the Cisco 2600 series and the Cisco 3600 series.

12.2(8)T


12.2SX


Usage Guidelines

This command allows you to observe the management channel activity from the AIC in the specified slot. Such activity shows that the software running on the AIC CPU has reached a minimum level of working order.

Examples

The following is sample output from the debug alarm-interface command: Router# debug alarm-interface AIC Slot 1:STATUS received

The following is sample output from the debug alarm-interface 1 data command: Router# debug alarm-interface 1 data AIC Slot 1:STATUS received aic_fastsend:particle count=1, len=1504 aic_pak_to_txring:scattered particle count=1, tx bytes=1504, leftover=0 aic_interrupt:# 30419 gstar=0x1000000


DB-47

Debug Commands debug alarm-interface

aic_safe_start:particle count=1, len=524 aic_pak_to_txring:scattered particle count=1, tx bytes=524, leftover=0 aic_process_TXivq:ivq - 0x42040000 at 15, slice 1 aic_interrupt:# 30420 gstar=0x1000000 aic_process_TXivq:ivq - 0x42040000 at 16, slice 1 aic_interrupt:# 30421 gstar=0x10000000 aic_scc_rx_intr:sts_dlen=0xC5E10000, len=1504, RSTA=0xA0 aic_serial_RX_interrupt:rxtype=1, len=1504, aic_scc_rx_intr:last_rxbd has aged, 2 aic_process_RXivq:ivq - 0x60000 at 13, slice 1 aic_interrupt:# 30422 gstar=0x10000000 aic_scc_rx_intr:sts_dlen=0xC20D0000, len=524, RSTA=0xA0 aic_serial_RX_interrupt:rxtype=1, len=524, aic_process_RXivq:ivq - 0x60000 at 14, slice 1 aic_interrupt:# 30423 gstar=0x20000000 aic_scc_rx_intr:sts_dlen=0xC00D0000, len=12, RSTA=0xA0 aic_mgmt_RX_interrupt:len=12 aic_mgmt_fastsend:particle count=1, len=20 / 20 aic_pak_to_txring:scattered particle count=1, tx bytes=20, leftover=0 aic_scc_rx_intr:last_rxbd has aged, 2 aic_process_RXivq:ivq - 0x10060000 at 37, slice 1 aic_interrupt:# 30424 gstar=0x2000000 aic_process_TXivq:ivq - 0x52040000 at 24, slice 1

Related Commands

Command

Description

alarm-interface

Enters the alarm interface mode and configures the AIC.

reset

Resets the AIC CPU.


DB-48

May 2008

Debug Commands debug alps ascu

debug alps ascu To enable debugging for airline product set (ALPS) agent set control units (ASCUs) use the debug alps ascu command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug alps ascu {event | packet | detail | all | format {ipars | router | both}} [interface [ascu id]] no debug alps ascu {event | packet | detail | all | format {ipars | router | both}} [interface [ascu id]]

Syntax Description

event

Displays ASCU events or protocol errors.

packet

Displays sent or received packets.

detail

Displays all ASCU protocol events.

all

Enables event, packet, and detail debugging.

format {ipars | router | both}

Specifies how to display ASCU addresses and the hexadecimal data in the debug output: •

ipars—Displays only the IPARS hexadecimal output.

•

router—Displays only the router hexadecimal output.

•

both—Displays both the IPARS and router hexadecimal output.

The only difference between the IPARS output and the router output is the format of the hexadecimal data. interface

(Optional) Enables debugging on a specified interface. Applies only to the event, packet, detail, and all keywords.

ascu id

(Optional) Enables debugging for a specified ASCU.

Defaults

Debugging is off.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)T

This command was introduced for limited availability.

12.0(1)

This command was available for general release.

12.0(5)T

This command was modified.

12.1(2)T

The format, ipars, router, and both keywords were added. The output for this command was modified to include IPARS and router formats.


DB-49


Usage Guidelines

Release

Modification

12.2(33)SRA


12.2SX


To enable debugging for a group of ASCUs, enter a separate command for each ASCU interface and IA combination. The interface option applies only to the event, packet, detail, and all keywords.

Note

Examples

To specify the particular debug tracing level (event, packet, detail or all) and the format (router, pairs or both), you must configure the debug alps ascu command two times: once to configure the debug tracing level and once to configure the format.

The following output is from the debug alps ascu event command, showing events or protocol errors in router format for ASCU 42 on interface Serial7: Router# debug alps ascu format router Router# debug alps ascu event Serial7 42 ALPS ASCU: T1 expired for ascu 42 on i/f Serial7 ALPS ASCU: DOWN event while UP for ascu 42 on i/f Serial7 : C1 count = 1

Note

If you specify the ipars or both format for the event or detail tracing level, both the IPARS and router formats will be displayed. The following output is from the debug alps ascu event command, showing events or protocol errors in ipars format for ASCU 42 on interface Serial7: Router# debug alps ascu format ipars Router# debug alps ascu event Serial7 42 ALPS ASCU: T1 expired for ascu 42/2F on i/f Serial7 ALPS ASCU: DOWN event while UP for ascu 42/2F on i/f Serial7 : C1 count = 1

The following output is from the debug alps ascu detail command, showing all protocol events in router format for ASCU 42 on interface Serial6: Router# debug alps ascu format router Router# debug alps ascu detail Serial6 42 ALPS ASCU: ALPS ASCU: ALPS ASCU: ALPS ASCU: ALPS ASCU: ALPS ASCU: RTP_MATIP ALPS ASCU:

Tx ALC ALC GO Tx ALC ALC GO Tx ALC Rx ALC

POLL MSG (+ 0 pad bytes) to ascu 42 on i/f Serial6 AHD MSG rcvd from ascu 42 on i/f Serial6 POLL MSG (+ 0 pad bytes) to ascu 42 on i/f Serial6 AHD MSG rcvd from ascu 42 on i/f Serial6 POLL MSG (+ 0 pad bytes) to ascu 42 on i/f Serial6 DATA MSG (14 bytes + CCC) from ascu 42 on i/f Serial6, fwd to ckt

ALC GO AHD MSG rcvd from ascu 42 on i/f Serial6


DB-50

May 2008


ALPS ASCU: Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6 ALPS ASCU: Tx ALC POLL MSG (3 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6

Note

If you specify the ipars or both format for the event or detail tracing level, both the IPARS and router formats will be displayed. The following output is from the debug alps ascu detail command, showing all protocol events in both format for ASCU 42 on interface Serial6: Router# debug alps ascu format both Router# debug alps ascu detail Serial6 42 ALPS ASCU: ALPS ASCU: ALPS ASCU: ALPS ASCU: ALPS ASCU: ALPS ASCU: RTP_MATIP ALPS ASCU: ALPS ASCU: ALPS ASCU:

Tx ALC ALC GO Tx ALC ALC GO Tx ALC Rx ALC

POLL MSG (+ 0 pad bytes) to ascu 42/2F on i/f Serial6 AHD MSG rcvd from ascu 42/2F on i/f Serial6 POLL MSG (+ 0 pad bytes) to ascu 42/2F on i/f Serial6 AHD MSG rcvd from ascu 42/2F on i/f Serial6 POLL MSG (+ 0 pad bytes) to ascu 42/2F on i/f Serial6 DATA MSG (14 bytes + CCC) from ascu 42/2F on i/f Serial6, fwd to ckt

ALC GO AHD MSG rcvd from ascu 42/2F on i/f Serial6 Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6 Tx ALC POLL MSG (3 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6

The following output is from the debug alps ascu packet command, showing all packets sent or received in router format for ASCU 42 on interface Serial6: Router# debug alps ascu packet format router Serial6 42 ALPS ASCU: Tx ALC 02321D26 0C261616 140C0D18 26163135 ALPS ASCU: Rx ALC RTP_MATIP 42607866 65717866 65717966 755124 ALPS ASCU: Tx ALC 022038 26253138 26253139 263511E4

SERVICE MSG (18 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6 0611C6 DATA MSG (14 bytes + CCC) from ascu 42 on i/f Serial6, fwd ckt

DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6

The following output is from the debug alps ascu packet command, showing all packets sent or received in ipars format for ASCU 42 on interface Serial6: Router# debug alps ascu packet format ipars Serial6 42 ALPS ASCU: Tx ALC SERVICE MSG (18 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6 ALPS IPARS Format: 2F2C1126 33262525 35331339 26251C14 271DC6 ALPS ASCU: Rx ALC DATA MSG (14 bytes + CCC) from ascu 42/2F on i/f Serial6, fwd ckt RTP_MATIP ALPS IPARS Format: 2F3E3826 161C3826 161C1826 141D24 ALPS ASCU: Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6 ALPS IPARS Format: 2F3E38 26161C38 26161C18 26141DE4


DB-51


The following output is from the debug alps ascu packet command, showing all packets sent or received in both formats for ASCU 42 on interface Serial6: Router# debug alps ascu packet format both Serial6 42 ALPS ASCU: Tx ALC SERVICE MSG (18 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6 ALPS Router Format: 02321D26 0C261616 140C0D18 26163135 0611C6 ALPS IPARS Format: 2F2C1126 33262525 35331339 26251C14 271DC6 ALPS ASCU: Rx ALC DATA MSG (14 bytes + CCC) from ascu 42/2F on i/f Serial6, fwd ckt RTP_MATIP ALPS Router Format: 42607866 65717866 65717966 755124 ALPS IPARS Format: 2F3E3826 161C3826 161C1826 141D24 ALPS ASCU: Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42/2F on i/f Serial6 ALPS Router Format: 022038 26253138 26253139 263511E4 ALPS IPARS Format: 2F3E38 26161C38 26161C18 26141DE4


DB-52

May 2008

Debug Commands debug alps circuit event

debug alps circuit event To enable event debugging for airline product set (ALPS) circuits, use the debug alps circuit event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug alps circuit event [name] no debug alps circuit event [name]

Syntax Description

name

Defaults

If no circuit name is specified, then debugging is enabled for every ALPS circuit.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3 T


12.2(33)SRA


12.2SX


Usage Guidelines

(Optional) Name given to identify an ALPS circuit on the remote customer premises equipment (CPE).

To enable debugging for a single ALPS circuit, specify the name of the circuit. To enable debugging for a group of circuits, enter a separate command for each circuit name.

Examples

The following is sample output from the debug alps circuit event command for circuit RTP_AX25: alps-rcpe# debug alps circuit event RTP_AX25 ALPS P1024 CKT: FSM - Ckt= RTP_AX25, State= OPEN, (CloseAndDisable)->DISC ALPS P1024 CKT: FSM - Ckt= RTP_AX25, State= DISC, (TmrStartNullRetry)->INOP ALPS P1024 CKT: Ckt= RTP_AX25, Open - peer set to ALPS P1024 CKT: Ckt= RTP_AX25, Open - peer open. ALPS P1024 CKT: FSM - Ckt= RTP_AX25, State= INOP, (Open)->OPNG ALPS P1024 CKT: FSM - Ckt= RTP_AX25, State= OPNG, (CacheAndFwdAscuData)->OPEN

Event= DISABLE: Event= ENABLE: 200.100.40.2 Event= RETRY_TIMEOUT: Event= CKT_OPEN_CFM:

alps-ccpe# debug alps circuit event RTP_AX25


DB-53

Debug Commands debug alps circuit event

ALPS AX.25 FSM: Ckt= RTP_AX25, State= OPEN, (PvcKill,CktRemove,TmrStartClose)->INOP ALPS AX.25 FSM: Ckt= RTP_AX25, State= INOP, (-,-,-)->INOP ALPS AX.25 FSM: Ckt= RTP_AX25, State= INOP, (-,CktDestroy,TmrStop)->INOP ALPS AX.25 FSM: Ckt= RTP_AX25, State= INOP, (PvcMake,CktAdd,TmrStartOpen)->OPNG ALPS AX.25 FSM: Ckt= RTP_AX25, State= OPNG, (-,-,-)->OPNG ALPS AX.25 FSM: Ckt= RTP_AX25, State= OPNG, (-,OpnCfm,TmrStop)->OPEN

Event= CktClose, Rsn= 12: Event= X25PvcInact, Rsn= 0: Event= X25VcDeleted, Rsn= 0: Event= CktOpReq, Rsn= 4: Event= X25ResetTx, Rsn= 0: Event= X25VcUp, Rsn= 0:


DB-54

May 2008

Debug Commands debug alps peer event

debug alps peer event To enable event debugging for airline product set (ALPS) peers, use the debug alps peer event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug alps peer event ipaddr no debug alps peer event ipaddr

Syntax Description

ipaddr

Defaults

If no IP address is specified, debugging is enabled for every peer connection.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3 T


12.2(33)SRA


12.2SX


Usage Guidelines

Peer IP address.

To enable debugging for a single remote ALPS peer, specify the peer IP address. To enable debugging for a set of remote peers, enter the command for each peer IP address.

Examples

The following is sample output from the debug alps peer event command: Router# debug alps peer event ALPS ALPS ALPS ALPS ALPS ALPS

PEER: PEER: PEER: PEER: PEER: PEER:

FSM - Peer 200.100.25.2, Event ALPS_CLOSED_IND, State OPENED peer 200.100.25.2 closed - closing peer circuits. Promiscuous peer created for 200.100.25.2 TCP Listen - passive open 200.100.25.2(11003) -> 10000 FSM - Peer 200.100.25.2, Event ALPS_OPEN_IND, State DISCONN peer 200.100.25.2 opened OK.


DB-55

Debug Commands debug alps peer

debug alps peer To enable event or packet debugging for airline product set (ALPS) peers, use the debug alps peer command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug alps peer {event | packet} [ip-address] no debug alps peer {event | packet} [ip-address]

Syntax Description

event

Specifies debugging for an event.

packet

Specifies debugging for a packet.

ip-address

(Optional) Remote peer IP address.

Defaults

If no IP address is specified, then debugging is enabled for every peer connection.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)T


12.0(1)


12.0(5)T

The packet keyword was added. The format for the output was modified for consistency.

12.2(33)SRA


12.2SX


Usage Guidelines

To enable debugging for a single remote ALPS peer, specify the peer IP address. To enable debugging for a set of remote peers, enter the command for each peer IP address.

Examples

The following is sample output from the debug alps peer packet command: Router# debug alps peer packet ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) - TX Peer Data Msg (18 bytes) 040A5320: 01 00001241 040A5330:45546B5F 6F4F7757 67477B5B 51 ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) - RX Peer Data Msg (18 bytes) 04000550: 01000012 4145546B 5F6F4F77 04000560:5767477B 5B51 ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) - TX Peer Data Msg (18 bytes)


DB-56

May 2008

Debug Commands debug alps peer

0409F6E0: 01 00001241 45546B5F 0409F6F0:6F4F7757 67477B5B 51 ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) - RX Peer Data Msg (18 bytes) 04000680: 01000012 4145546B 04000690:5F6F4F77 5767477B 5B51


DB-57

Debug Commands debug alps snmp

debug alps snmp To enable debugging for airline product set (ALPS) Simple Network Management Protocol (SNMP) agents, use the debug alps snmp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug alps snmp no debug alps snmp

Syntax Description


Defaults

Debugging for SNMP agents is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)T


12.0(1)T


Examples

12.0(5)T

This command was added to the documentation.

12.1(2)T

The output for this command was modified to reflect MIB and SNMP changes.

12.2(33)SRA


12.2SX


The following output is from the debug alps snmp command. The first line shows a circuit event status change. The second line shows an ASCU status change. The third line shows a peer connection status change. Router# debug alps snmp ALPS CktStatusChange Notification for circuit CKT-1 ALPS AscuStatusChange Notification for ascu (Serial3, 41) PeerConnStatusChange Notification for peer (10.227.50.106, MATIP_A_CKT-1)

The following output shows that an open failure has occurred on circuit 1: ALPS CktOpenFailure Notification for circuit CKT1

The following output shows that a partial rejection to an ALPS circuit peer open request has occurred on circuit 1: ALPS CktPartialReject Notification for ascu (Serial2, 41) on circuit CKT1


DB-58

May 2008

Debug Commands debug appfw

debug appfw To display debug messages about Cisco IOS Firewall events, use the debug appfw command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug appfw {application protocol | function-trace | object-creation | object-deletion | events | timers | detailed} no debug appfw {application protocol | function-trace | object-creation | object-deletion | events | timers | detailed}

Syntax Description

application protocol

Displays messages about protocol events of firewall-inspected applications, including details about the protocol’s packets. Currently, the only supported protocol is HTTP. (Issue the http keyword.)

function-trace

Displays messages about software functions called by Cisco IOS Firewall.

object-creation

Displays messages about software objects that are being created by Cisco IOS Firewall. Cisco IOS Firewall-inspected sessions begin when the object is created.

object-deletion

Displays messages about software objects that are being deleted by Cisco IOS Firewall. Cisco IOS Firewall-inspected sessions close when the object is deleted.

events

Displays messages about Cisco IOS software events, including Cisco IOS Firewall packet processing.

timers

Displays messages about Cisco IOS Firewall timer events, such as an idle timeout by the Cisco IOS Firewall.

detailed

Detailed information for all other enabled Cisco IOS Firewall debugging is displayed. Note

This keyword should be used in conjunction with other Cisco IOS Firewall debugging commands.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Examples

The following sample configuration shows how to configure an HTTP policy with application firewall debugging enabled: Router(config)# appfw policy-name myPolicyAPPFW APPFW APPFW

FUNC:appfw_policy_find

FUNC:appfw_policy_find -- Policy myPolicy is not found FUNC:appfw_policy_alloc


DB-59

Debug Commands debug appfw

APPFW APPFW APPFW APPFW

FUNC:appfw_policy_alloc -- policy_alloc 0x65727278 FUNC:appfw_policy_alloc -- Policy 0x65727278 is set to valid FUNC:appfw_policy_alloc -- Policy myPolicy has been created FUNC:appfw_policy_command -- memlock policy 0x65727278

! Debugging sample for application (HTTP) creation Router(cfg-appfw-policy)# application httpAPPFW APPFW APPFW APPFW APPFW APPFW

FUNC:appfw_http_command

FUNC:appfw_http_appl_find FUNC:appfw_http_appl_find -- Application not found FUNC:appfw_http_appl_alloc FUNC:appfw_http_appl_alloc -- appl_http 0x64D7A25C FUNC:appfw_http_appl_alloc -- Application HTTP parser structure 64D7A25C created

! Debugging sample for HTTP-specific application inspection Router(cfg-appfw-policy-http)# Router(cfg-appfw-policy-http)# strict-http action reset alarm APPFW FUNC:appfw_http_subcommand APPFW FUNC:appfw_http_subcommand -- strict-http cmd turned on Router# debug appfw detailed APPFW Detailed Debug debugging is on fw7-7206a#debug appfw object-creation APPFW Object Creations debugging is on fw7-7206a#debug appfw object-deletion APPFW Object Deletions debugging is on


DB-60

May 2008

Debug Commands debug apple arp

debug apple arp To enable debugging of the AppleTalk Address Resolution Protocol (AARP), use the debug apple arp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple arp [type number] no debug apple arp [type number]

Syntax Description

type

(Optional) Interface type.

number

(Optional) Interface number.

Command Modes

Privileged EXEC

Usage Guidelines

This command is helpful when you experience problems communicating with a node on the network you control (a neighbor). If the debug apple arp display indicates that the router is receiving AARP probes, you can assume that the problem does not reside at the physical layer.

Examples

The following is sample output from the debug apple arp command: Router# debug apple arp Ether0: Ether0: Ether0: Ether0: Ether0: Ether0:

AARP: AARP: AARP: AARP: AARP: AARP:

Sent resolve for 4160.26 Reply from 4160.26(0000.0c00.0453) for 4160.154(0000.0c00.8ea9) Resolved waiting request for 4160.26(0000.0c00.0453) Reply from 4160.19(0000.0c00.0082) for 4160.154(0000.0c00.8ea9) Resolved waiting request for 4160.19(0000.0c00.0082) Reply from 4160.19(0000.0c00.0082) for 4160.154(0000.0c00.8ea9)

Explanations for representative lines of output follow. The following line indicates that the router has requested the hardware MAC address of the host at network address 4160.26: Ether0: AARP: Sent resolve for 4160.26

The following line indicates that the host at network address 4160.26 has replied, giving its MAC address (0000.0c00.0453). For completeness, the message also shows the network address to which the reply was sent and its hardware MAC address (also in parentheses). Ether0: AARP: Reply from 4160.26(0000.0c00.0453) for 4160.154(0000.0c00.8ea9)

The following line indicates that the MAC address request is complete: Ether0: AARP: Resolved waiting request for 4160.26(0000.0c00.0453)


DB-61

Debug Commands debug apple domain

debug apple domain To enable debugging of the AppleTalk domain activities, use the debug apple domain command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple domain no debug apple domain

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use the debug apple domain command to observe activity for domains and subdomains. Use this command in conjunction with the debug apple remap command to observe interaction between remapping and domain activity. Messages are displayed when the state of a domain changes, such as creating a new domain, deleting a domain, and updating a domain.

Examples

The following is sample output from the debug apple domain command intermixed with output from the debug apple remap command; the two commands show related events: Router# debug apple domain Router# debug apple remap AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1 AT-REMAP: ReshuffleRemapList for subdomain 1 AT-REMAP: Could not find a remap for cable 3000-3001 AT-DOMAIN: atdomain_DisablePort for Tunnel0 AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1] AT-DOMAIN: Disabling interface Ethernet1 AT-DOMAIN: atdomain_DisablePort for Ethernet1 AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1] AT-DOMAIN: CleanSubDomain for inbound subdomain 1 AT-REMAP: Remap for net 70 inbound subdomain 1 has been deleted AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 AT-DOMAIN: DeleteRemapTable for subdomain 1 AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 AT-DOMAIN: CleanSubDomain for outbound subdomain 1 AT-DOMAIN: DeleteRemapTable for subdomain 1 AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1 Remapped Net 10000 AT-REMAP: Remap for net 50 outbound subdomain 1 has been deleted AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1] AT-DOMAIN: CleanSubDomain for inbound subdomain 1 AT-DOMAIN: DeleteRemapTable for subdomain 1 AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 AT-DOMAIN: CleanSubDomain for outbound subdomain 1 AT-DOMAIN: DeleteRemapTable for subdomain 1 AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1


DB-62

May 2008

Debug Commands debug apple domain

Related Commands

Command

Description

debug apple remap

Enables debugging of the AppleTalk remap activities.


DB-63

Debug Commands debug apple eigrp-all

debug apple eigrp-all To enable debugging output from the Enhanced IGRP routines, use the debug apple eigrp-all privileged EXEC command. The no form of this command disables debugging output. debug apple eigrp-all no debug apple eigrp-all

Syntax Description


Command History

Release

Modification

10.0


12.2(13)T

This command is no longer supported in Cisco IOS Mainline relesaes or in Technology-based(T-train) releases. It might continue to appear in 12.2S-family releases.

12.2SX


Usage Guidelines

Caution

Examples

The debug apple eigrp-all command can be used to monitor acquisition of routes, aging route table entries, and advertisement of known routes through Enhanced IGRP.

Because the debug apple eigrp-all command can generate many messages, use it only when the CPU utilization of the router is less than 50 percent.

The following is sample output from the debug apple eigrp-all command: Router# debug apple eigrp-all 3:54:34: 3:54:37: 3:54:37: 3:54:37: 3:54:37: 3:54:37: 3:54:39: 3:54:42: 3:54:42: 3:54:42: 3:54:42: 3:54:42:

atigrp2_router: peer is 83.195 AT: atigrp2_write: about to send packet Ethernet2: output AT packet: enctype UNKNOWN, size 65 07FFFFFF0000FFFFFFFFFFFF00000C1485B00046|0041ACD100000053FF8F58585802059110 000000000000000000000000000000010001000C010001000000000F0204000C0053005300 AT: atigrp2, src=Ethernet2:83.143, dst=83-83, size=52, EIGRP pkt sent atigrp2_router: peer is 83.195 AT: atigrp2_write: about to send packet Ethernet2: output AT packet: enctype UNKNOWN, size 65 07FFFFFF0000FFFFFFFFFFFF00000C1485B00046|0041ACD100000053FF8F58585802059110 000000000000000000000000000000010001000C010001000000000F0204000C0053005300 AT: atigrp2, src=Ethernet2:83.143, dst=83-83, size=52, EIGRP pkt sent


DB-64

May 2008

Debug Commands debug apple eigrp-all


debug apple eigrp Field Descriptions

Field

Description

atigrp2_router:

AppleTalk address of the neighbor.

AT:

Indicates that this is an AppleTalk packet.

Ethernet2:

Name of the interface through which the router received the packet.

src=

Name of the interface sending the Enhanced IGRP packet, as well at its AppleTalk address.

dst=

Cable range of the destination of the packet.

size=

Size of the packet (in bytes).


DB-65

Debug Commands debug apple errors

debug apple errors To display errors occurring in the AppleTalk network, use the debug apple errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple errors [type number] no debug apple errors [type number]

Syntax Description

type


number


Command Modes

Privileged EXEC

Usage Guidelines

In a stable AppleTalk network, the debug apple errors command produces little output. To solve encapsulation problems, enable debug apple errors and debug apple packet together.

Examples

The following is sample output from the debug apple errors command when a router is brought up with a zone that does not agree with the zone list of other routers on the network: Router# debug apple errors %AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19 %AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19 %AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19

As the output suggests, a single error message indicates zone list incompatibility; this message is sent out periodically until the condition is corrected or the debug apple errors command is turned off. Most of the other messages that the debug apple errors command can generate are obscure or indicate a serious problem with the AppleTalk network. Some of these other messages follow. In the following message, RTMPRsp, RTMPReq, ATP, AEP, ZIP, ADSP, or SNMP could replace NBP, and “llap dest not for us” could replace “wrong encapsulation”: Packet discarded, src 4160.12-254,dst 4160.19-254,NBP,wrong encapsulation

In the following message, in addition to an invalid echo packet error, other possible errors are unsolicited AEP echo reply, unknown echo function, invalid ping packet, unknown ping function, and bad responder packet type: Ethernet0: AppleTalk packet error; no source address available AT: pak_reply: dubious reply creation, dst 4160.19 AT: Unable to get a buffer for reply to 4160.19 Processing error, src 4160.12-254,dst 4160.19-254,AEP, invalid echo packet


DB-66

May 2008

Debug Commands debug apple errors

The debug apple errors command can print out additional messages when other debugging commands are also turned on. When you turn on both the debug apple errors and debug apple events commands, the following message can be generated: Proc err, src 4160.12-254,dst 4160.19-254,ZIP,NetInfo Reply format is invalid

In the preceding message, in addition to the NetInfo Reply format is invalid error, other possible errors are NetInfoReply not for me, NetInfoReply ignored, NetInfoReply for operational net ignored, NetInfoReply from invalid port, unexpected NetInfoReply ignored, cannot establish primary zone, no primary has been set up, primary zone invalid, net information mismatch, multicast mismatch, and zones disagree. When you turn on both the debug apple errors and debug apple nbp commands, the following message can be generated: Processing error,...,NBP,NBP name invalid

In the preceding message, in addition to the NBP name invalid error, other possible errors are NBP type invalid, NBP zone invalid, not operational, error handling brrq, error handling proxy, NBP fwdreq unexpected, No route to srcnet, Proxy to “*” zone, Zone “*” from extended net, No zone info for “*”, and NBP zone unknown. When you turn on both the debug apple errors and debug apple routing commands, the following message can be generated: Processing error,...,RTMPReq, unknown RTMP request

In the preceding message, in addition to an unknown RTMP request error, other possible errors are RTMP packet header bad, RTMP cable mismatch, routed RTMP data, RTMP bad tuple, and Not Req or Rsp.


DB-67

Debug Commands debug apple events

debug apple events To display information about AppleTalk special events, neighbors becoming reachable or unreachable, and interfaces going up or down, use the debug apple events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple events [type number] no debug apple events [type number]

Syntax Description

type


number


Command Modes

Privileged EXEC

Usage Guidelines

Only significant events (for example, neighbor and route changes) are logged. The debug apple events command is useful for solving AppleTalk network problems because it provides an overall picture of the stability of the network. In a stable network, the debug apple events command does not return any information. If the command generates numerous messages, those messages can indicate possible sources of the problems. When configuring or making changes to a router or interface for AppleTalk, enable the debug apple events command to alert you to the progress of the changes or to any errors that might result. Also use this command periodically when you suspect network problems. The debug apple events command is also useful to determine whether network flapping (nodes toggling online and offline) is occurring. If flapping is excessive, look for routers that only support 254 networks. When you enable the debug apple events command, you will see any messages that the apple event-logging configuration command normally displays. Turning on the debug apple events command, however, does not cause the apple event-logging command to be maintained in nonvolatile memory. Only turning on the apple event-logging command explicitly stores it in nonvolatile memory. Furthermore, if the apple event-logging command is already enabled, turning on or off the debug apple events command does not affect the apple event-logging command.


DB-68

May 2008


Examples

The following is sample output from the debug apple events command that describes a nonseed router coming up in discovery mode: router# debug apple events Ether0: AT: Resetting interface address filters %AT-5-INTRESTART: Ether0: AppleTalk port restarting; protocol restarted Ether0: AppleTalk state changed; unknown -> restarting Ether0: AppleTalk state changed; restarting -> probing %AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 65401.148 Ether0: AppleTalk state changed; probing -> acquiring %AT-6-ACQUIREMODE: Ether0: AT port initializing; acquiring net configuration Ether0: AppleTalk state changed; acquiring -> restarting Ether0: AppleTalk state changed; restarting -> line down Ether0: AppleTalk state changed; line down -> restarting Ether0: AppleTalk state changed; restarting -> probing %AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 4160.148 Ether0: AppleTalk state changed; probing -> acquiring %AT-6-ACQUIREMODE: Ether0: AT port initializing; acquiring net configuration Ether0: AppleTalk state changed; acquiring -> requesting zones Ether0: AT: Resetting interface address filters %AT-5-INTRESTART: Ether0: AppleTalk port restarting; protocol restarted Ether0: AppleTalk state changed; requesting zones -> verifying AT: Sent GetNetInfo request broadcast on Ethernet0 Ether0: AppleTalk state changed; verifying -> checking zones Ether0: AppleTalk state changed; checking zones -> operational S2542

Discovery mode state changes

As the output shows, the debug apple events command is useful in tracking the discovery mode state changes through which an interface progresses. When no problems are encountered, the state changes progress as follows: 1.

Line down.

2.

Restarting.

3.

Probing (for its own address [node ID] using AARP).

4.

Acquiring (sending out GetNetInfo requests).

5.

Requesting zones (the list of zones for its cable).

6.

Verifying (that the router’s configuration is correct. If not, a port configuration mismatch is declared).

7.

Checking zones (to make sure its list of zones is correct).

8.

Operational (participating in routing).

Explanations for individual lines of output follow. The following message indicates that a port is set. In this case, the zone multicast address is being reset. Ether0: AT: Resetting interface address filters

The following messages indicate that the router is changing to restarting mode: %AT-5-INTRESTART: Ether0: AppleTalk port restarting; protocol restarted Ether0: AppleTalk state changed; unknown -> restarting

The following message indicates that the router is probing in the startup range of network numbers (65280 to 65534) to discover its network number: Ether0: AppleTalk state changed; restarting -> probing


DB-69


The following message indicates that the router is enabled as a nonrouting node using a provisional network number within its startup range of network numbers. This type of message only appears if the network address the router will use differs from its configured address. This is always the case for a discovery-enabled router; it is rarely the case for a nondiscovery-enabled router. %AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 65401.148

The following messages indicate that the router is sending out GetNetInfo requests to discover the default zone name and the actual network number range in which its network number can be chosen: Ether0: AppleTalk state changed; probing -> acquiring %AT-6-ACQUIREMODE: Ether0: AT port initializing; acquiring net configuration

Now that the router has acquired the cable configuration information, the following message indicates that it restarts using that information: Ether0: AppleTalk state changed; acquiring -> restarting

The following messages indicate that the router is probing for its actual network address: Ether0: AppleTalk state changed; restarting -> line down Ether0: AppleTalk state changed; line down -> restarting Ether0: AppleTalk state changed; restarting -> probing

The following message indicates that the router has found an actual network address to use: %AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 4160.148

The following messages indicate that the router is sending out GetNetInfo requests to verify the default zone name and the actual network number range from which its network number can be chosen: Ether0: AppleTalk state changed; probing -> acquiring %AT-6-ACQUIREMODE: Ether0: AT port initializing; acquiring net configuration

The following message indicates that the router is requesting the list of zones for its cable: Ether0: AppleTalk state changed; acquiring -> requesting zones

The following messages indicate that the router is sending out GetNetInfo requests to make sure its understanding of the configuration is correct: Ether0: AppleTalk state changed; requesting zones -> verifying AT: Sent GetNetInfo request broadcast on Ethernet0

The following message indicates that the router is rechecking its list of zones for its cable: Ether0: AppleTalk state changed; verifying -> checking zones

The following message indicates that the router is now fully operational as a routing node and can begin routing: Ether0: AppleTalk state changed; checking zones -> operational


DB-70

May 2008


The following shows sample debug apple events output that describes a nondiscovery-enabled router coming up when no other router is on the wire. router# debug apple events

S2543

Indicates a nondiscoveryenabled router with no other router on the wire

Ethernet1: AT: Resetting interface address filters %AT-5-INTRESTART: Ethernet1: AppleTalk port restarting; protocol restarted Ethernet1: AppleTalk state changed; unknown -> restarting Ethernet1: AppleTalk state changed; restarting -> probing %AT-6-ADDRUSED: Ethernet1: AppleTalk node up; using address 4165.204 Ethernet1: AppleTalk state changed; probing -> verifying AT: Sent GetNetInfo request broadcast on Ethernet1 Ethernet1: AppleTalk state changed; verifying -> operational %AT-6-ONLYROUTER: Ethernet1: AppleTalk port enabled; no neighbors found

As the output shows, a nondiscovery-enabled router can come up when no other router is on the wire; however, it must assume that its configuration (if accurate syntactically) is correct, because no other router can verify it. Notice that the last line indicates this situation. The following is sample output from the debug apple events command that describes a discovery-enabled router coming up when there is no seed router on the wire: Router# debug apple events Ether0: AT: Resetting interface address filters %AT-5-INTRESTART: Ether0: AppleTalk port restarting; protocol restarted Ether0: AppleTalk state changed; unknown -> restarting Ether0: AppleTalk state changed; restarting -> probing %AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 65401.148 Ether0: AppleTalk state changed; probing -> acquiring AT: Sent GetNetInfo request broadcast on Ether0 AT: Sent GetNetInfo request broadcast on Ether0 AT: Sent GetNetInfo request broadcast on Ether0 AT: Sent GetNetInfo request broadcast on Ether0 AT: Sent GetNetInfo request broadcast on Ether0

As the output shows, when you attempt to bring up a nonseed router without a seed router on the wire, it never becomes operational; instead, it hangs in the acquiring mode and continues to send out periodic GetNetInfo requests. The following is sample output from the debug apple events command when a nondiscovery-enabled router is brought up on an AppleTalk internetwork that is in compatibility mode (set up to accommodate extended as well as nonextended AppleTalk) and the router has violated internetwork compatibility:

Indicates configuration mismatch

E0: AT: Resetting interface address filters %AT-5-INTRESTART: E0: AppleTalk port restarting; protocol restarted E0: AppleTalk state changed; restarting -> probing %AT-6-ADDRUSED: E0: AppleTalk node up; using address 41.19 E0: AppleTalk state changed; probing -> verifying AT: Sent GetNetInfo request broadcast on Ethernet0 %AT-3-ZONEDISAGREES: E0: AT port disabled; zone list incompatible with 41.19 AT: Config error for E0, primary zone invalid E0: AppleTalk state changed; verifying -> config mismatch


DB-71

S2545

router# debug apple events


The following three configuration command lines indicate the part of the configuration of the router that caused the configuration mismatch: lestat(config)# interface ethernet 0 lestat(config-if)# apple cab 41-41 lestat(config-if)# apple zone Marketing

The router shown had been configured with a cable range of 41-41 instead of 40-40, which would have been accurate. Additionally, the zone name was configured incorrectly; it should have been “Marketing,” rather than being misspelled as “Markting.”


DB-72

May 2008

Debug Commands debug apple nbp

debug apple nbp To display debugging output from the Name Binding Protocol (NBP) routines, use the debug apple nbp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple nbp [type number] no debug apple nbp [type number]

Syntax Description

type


number


Command Modes

Privileged EXEC

Usage Guidelines

To determine whether the router is receiving NBP lookups from a node on the AppleTalk network, enable debug apple nbp at each node between the router and the node in question to determine where the problem lies.

Caution

Examples

Because the debug apple nbp command can generate many messages, use it only when the CPU utilization of the router is less than 50 percent.

The following is sample output from the debug apple nbp command: Router# debug apple nbp AT: NBP ctrl = LkUp, ntuples = 1, id = 77 AT: 4160.19, skt 2, enum 0, name: =:ciscoRouter@Low End SW Lab AT: LkUp =:ciscoRouter@Low End SW Lab AT: NBP ctrl = LkUp-Reply, ntuples = 1, id = 77 AT: 4160.154, skt 254, enum 1, name: lestat.Ether0:ciscoRouter@Low End SW Lab AT: AT: AT: AT: AT: AT: AT:

NBP ctrl = LkUp, ntuples = 1, 4160.19, skt 2, enum 0, name: NBP ctrl = LkUp, ntuples = 1, 4160.19, skt 2, enum 0, name: NBP ctrl = LkUp, ntuples = 1, 4160.19, skt 2, enum 0, name: LkUp =:ciscoRouter@Low End SW

id = 78 =:IPADDRESS@Low End SW Lab id = 79 =:IPGATEWAY@Low End SW Lab id = 83 =:ciscoRouter@Low End SW Lab Lab

AT: NBP ctrl = LkUp, ntuples = 1, id = 84 AT: 4160.19, skt 2, enum 0, name: =:IPADDRESS@Low End SW Lab AT: AT: AT: AT:

NBP ctrl 4160.19, NBP ctrl 4160.19,

= LkUp, ntuples = 1, skt 2, enum 0, name: = LkUp, ntuples = 1, skt 2, enum 0, name:

id = 85 =:IPGATEWAY@Low End SW Lab id = 85 =:IPGATEWAY@Low End SW Lab


DB-73


The first three lines describe an NBP lookup request: AT: NBP ctrl = LkUp, ntuples = 1, id = 77 AT: 4160.19, skt 2, enum 0, name: =:ciscoRouter@Low End SW Lab AT: LkUp =:ciscoRouter@Low End SW Lab

Table 6 describes the fields in the first line of output. Table 6

debug apple nbp Field Descriptions—First Line of Output

Field

Description

AT: NBP

Indicates that this message describes an AppleTalk NBP packet.

ctrl = LkUp

Identifies the type of NBP packet. Possible values are as follows: •

LkUp—NBP lookup request.

•

LkUp-Reply—NBP lookup reply.

ntuples = 1

Indicates the number of name-address pairs in the lookup request packet. Range: 1 to 31 tuples.

id = 77

Identifies an NBP lookup request value.

Table 7 describes the fields in the second line of output. Table 7

debug apple nbp Field Descriptions—Second Line of Output

Field

Description

AT:

Indicates that this message describes an AppleTalk packet.

4160.19

Indicates the network address of the requester.

skt 2

Indicates the internet socket address of the requester. The responder will send the NBP lookup reply to this socket address.

enum 0

Indicates the enumerator field. Used to identify multiple names registered on a single socket. Each tuple is assigned its own enumerator, incrementing from 0 for the first tuple.

name: =:ciscoRouter@Low End SW Lab

Indicates the entity name for which a network address has been requested. The AppleTalk entity name includes three components: •

Object (in this case, a wildcard character [=], indicating that the requester is requesting name-address pairs for all objects of the specified type in the specified zone).

•

Type (in this case, ciscoRouter).

•

Zone (in this case, Low End SW Lab).

The third line in the output essentially reiterates the information in the two lines above it, indicating that a lookup request has been made regarding name-address pairs for all objects of the ciscoRouter type in the Low End SW Lab zone.


DB-74

May 2008


Because the router is defined as an object of type ciscoRouter in zone Low End SW Lab, the router sends an NBP lookup reply in response to this NBP lookup request. The following two lines of output show the response of the router: AT: NBP ctrl = LkUp-Reply, ntuples = 1, id = 77 AT: 4160.154, skt 254, enum 1, name: lestat.Ether0:ciscoRouter@Low End SW Lab

In the first line, ctrl = LkUp-Reply identifies this NBP packet as an NBP lookup request. The same value in the id field (id = 77) associates this lookup reply with the previous lookup request. The second line indicates that the network address associated with the entity name of the router (lestat.Ether0:ciscoRouter@Low End SW Lab) is 4160.154. The fact that no other entity name/network address is listed indicates that the responder only knows about itself as an object of type ciscoRouter in zone Low End SW Lab.


DB-75

Debug Commands debug apple packet

debug apple packet To display per-packet debugging output, use the debug apple packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple packet [type number] no debug apple packet [type number]

Syntax Description

type


number


Command Modes

Privileged EXEC

Usage Guidelines

With this command, you can monitor the types of packets being slow switched. It displays at least one line of debugging output per AppleTalk packet processed. The output reports information online when a packet is received or a transmission is attempted. When invoked in conjunction with the debug apple routing, debug apple zip, and debug apple nbp commands, the debug apple packet command adds protocol processing information in addition to generic packet details. It also reports successful completion or failure information. When invoked in conjunction with the debug apple errors command, the debug apple packet command reports packet-level problems, such as those concerning encapsulation.

Caution

Examples

Because the debug apple packet command can generate many messages, use it only when the CPU utilization of the router is less than 50 percent.

The following is sample output from the debug apple packet command: Router# debug apple packet Ether0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000 AT: src=Ethernet0:4160.47, dst=4160-4160, size=10, 2 rtes, RTMP pkt sent AT: ZIP Extended reply rcvd from 4160.19 AT: ZIP Extended reply rcvd from 4160.19 AT: src=Ethernet0:4160.47, dst=4160-4160, size=10, 2 rtes, RTMP pkt sent Ether0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000 Ether0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000


DB-76

May 2008

Debug Commands debug apple packet

Table 8 describes the fields in the first line of output. Table 8

debug apple packet Field Descriptions—First Line of Output

Field

Description

Ether0:

Name of the interface through which the router received the packet.

AppleTalk packet


enctype SNAP

Encapsulation type for the packet.

size 60

Size of the packet (in bytes).

encaps000000000000000000000000

Encapsulation.

Table 9 describes the fields in the second line of output. Table 9

debug apple packet Field Descriptions—Second Line of Output

Field

Description

AT:


src=Ethernet0:4160.47

Name of the interface sending the packet and its AppleTalk address.

dst=4160-4160

Cable range of the destination of the packet.

size=10

Size of the packet (in bytes.)

2 rtes

Indicates that two routes in the routing table link these two addresses.

RTMP pkt sent

Type of packet sent.

The third line indicates the type of packet received and its source AppleTalk address. This message is repeated in the fourth line because AppleTalk hosts can send multiple replies to a given GetNetInfo request.


DB-77

Debug Commands debug apple remap

debug apple remap To enable debugging of the AppleTalk remap activities, use the debug apple remap command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple remap no debug apple remap

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use the debug apple remap command with the debug apple domain command to observe activity between domains and subdomains. Messages from the debug apple remap command are displayed when a particular remapping function occurs, such as creating remaps or deleting remaps.

Examples

The following is sample output from the debug apple remap command intermixed with output from the debug apple domain command; the two commands show related events. Router# debug apple remap Router# debug apple domain AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1 AT-REMAP: ReshuffleRemapList for subdomain 1 AT-REMAP: Could not find a remap for cable 3000-3001 AT-DOMAIN: atdomain_DisablePort for Tunnel0 AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1] AT-DOMAIN: Disabling interface Ethernet1 AT-DOMAIN: atdomain_DisablePort for Ethernet1 AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1] AT-DOMAIN: CleanSubDomain for inbound subdomain 1 AT-REMAP: Remap for net 70 inbound subdomain 1 has been deleted AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 AT-DOMAIN: DeleteRemapTable for subdomain 1 AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 AT-DOMAIN: CleanSubDomain for outbound subdomain 1 AT-DOMAIN: DeleteRemapTable for subdomain 1 AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1 Remaped Net 10000 AT-REMAP: Remap for net 50 outbound subdomain 1 has been deleted AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1] AT-DOMAIN: CleanSubDomain for inbound subdomain 1 AT-DOMAIN: DeleteRemapTable for subdomain 1 AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 AT-DOMAIN: CleanSubDomain for outbound subdomain 1 AT-DOMAIN: DeleteRemapTable for subdomain 1 AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1


DB-78

May 2008

Debug Commands debug apple remap

Related Commands

Command

Description

debug apple domain

Enables debugging of the AppleTalk domain activities.


DB-79

Debug Commands debug apple routing

debug apple routing To enable debugging output from the Routing Table Maintenance Protocol (RTMP) routines, use the debug apple routing command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple routing [type number] no debug apple routing [type number]

Syntax Description

type


number


Command Modes

Privileged EXEC

Usage Guidelines

This command can be used to monitor acquisition of routes, aging of routing table entries, and advertisement of known routes. It also reports conflicting network numbers on the same network if the network is misconfigured.

Caution

Examples

Because the debug apple routing command can generate many messages, use it only when router CPU utilization is less than 50 percent.

The following is sample output from the debug apple routing command: Router# debug apple routing AT: AT: AT: AT: AT: AT: AT: AT: AT:

src=Ethernet0:4160.41, dst=4160-4160, size=19, 2 rtes, RTMP pkt sent src=Ethernet1:41069.25, dst=41069, size=427, 96 rtes, RTMP pkt sent src=Ethernet2:4161.23, dst=4161-4161, size=427, 96 rtes, RTMP pkt sent Route ager starting (97 routes) Route ager finished (97 routes) RTMP from 4160.19 (new 0,old 94,bad 0,ign 0, dwn 0) RTMP from 4160.250 (new 0,old 0,bad 0,ign 2, dwn 0) RTMP from 4161.236 (new 0,old 94,bad 0,ign 1, dwn 0) src=Ethernet0:4160.41, dst=4160-4160, size=19, 2 rtes, RTMP pkt sent

Table 10 describes the fields in the first line of sample debug apple routing output. Table 10

debug apple routing Field Descriptions—First Line of Output

Field

Description

AT:

Indicates that this is AppleTalk debugging output.

src=Ethernet0:4160.41

Indicates the source router interface and network address for the RTMP update packet.

dst=4160-4160

Indicates the destination network address for the RTMP update packet.


DB-80

May 2008

Debug Commands debug apple routing

Table 10

debug apple routing Field Descriptions—First Line of Output (continued)

Field

Description

size=19

Displays the size of this RTMP packet (in bytes).

2 rtes

Indicates that this RTMP update packet includes information on two routes.

RTMP pkt sent

Indicates that this type of message describes an RTMP update packet that the router has sent (rather than one that it has received).

The following two messages indicate that the ager has started and finished the aging process for the routing table and that this table contains 97 entries: AT: Route ager starting (97 routes) AT: Route ager finished (97 routes)

Table 11 describes the fields in the following line of the debug apple routing command output: AT: RTMP from 4160.19 (new 0,old 94,bad 0,ign 0, dwn 0)

Table 11

debug apple routing Field Descriptions

Field

Description

AT:

Indicates that this is AppleTalk debugging output.

RTMP from 4160.19

Indicates the source address of the RTMP update the router received.

new 0

Displays the number of routes in this RTMP update packet that the router did not already know about.

old 94

Displays the number of routes in this RTMP update packet that the router already knew about.

bad 0

Displays the number of routes the other router indicates have gone bad.

ign 0

Displays the number of routes the other router ignores.

dwn 0

Displays the number of poisoned tuples included in this packet.


DB-81

Debug Commands debug apple zip

debug apple zip To display debugging output from the Zone Information Protocol (ZIP) routines, use the debug apple zip command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug apple zip [type number] no debug apple zip [type number]

Syntax Description

type


number


Command Modes

Privileged EXEC

Usage Guidelines

This command reports significant events such as the discovery of new zones and zone list queries. It generates information similar to that generated by the debug apple routing command, but generates it for ZIP packets instead of Routing Table Maintenance Protocol (RTMP) packets. You can use the debug apple zip command to determine whether a ZIP storm is taking place in the AppleTalk network. You can detect the existence of a ZIP storm when you see that no router on a cable has the zone name corresponding to a network number that all the routers have in their routing tables.

Examples

The following is sample output from the debug apple zip command: Router# debug apple zip AT: AT: AT: AT: AT:

Sent GetNetInfo request broadcast on Ether0 Recvd ZIP cmd 6 from 4160.19-6 3 query packets sent to neighbor 4160.19 1 zones for 31902, ZIP XReply, src 4160.19 net 31902, zonelen 10, name US-Florida

The first line indicates that the router has received an RTMP update that includes a new network number and is now requesting zone information: AT: Sent GetNetInfo request broadcast on Ether0

The second line indicates that the neighbor at address 4160.19 replies to the zone request with a default zone: AT: Recvd ZIP cmd 6 from 4160.19-6

The third line indicates that the router responds with three queries to the neighbor at network address 4160.19 for other zones on the network: AT: 3 query packets sent to neighbor 4160.19

The fourth line indicates that the neighbor at network address 4160.19 responds with a ZIP extended reply, indicating that one zone has been assigned to network 31902: AT: 1 zones for 31902, ZIP XReply, src 4160.19


DB-82

May 2008

Debug Commands debug apple zip

The fifth line indicates that the router responds that the zone name of network 31902 is US-Florida, and the zone length of that zone name is 10: AT: net 31902, zonelen 10, name US-Florida


DB-83

Debug Commands debug appn all

debug appn all To turn on all possible debugging messages for Advanced Peer-to-Peer Networking (APPN), use the debug appn all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug appn all no debug appn all

Note

Refer to the other forms of the debug appn command to enable specific debug output selectively.

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command shows all APPN events. Use other forms of the debug appn command to display specific types of events.

Caution

Because the debug appn all command can generate many messages and alter timing in the network node, use it only when instructed by authorized support personnel.

Caution

Debugging output takes priority over other network traffic. The debug appn all command generates more output than any other debug appn command and can alter timing in the network node. This command can severely diminish router performance or even render it unusable. In virtually all cases, it is best to use specific debug appn commands.

Examples

Refer to the documentation for specific debug appn commands for examples and explanations.

Related Commands

Command

Description

debug appn cs

Displays the APPN CS component activity.

debug appn ds

Displays debugging information on APPN DS component activity.

debug appn hpr

Displays information related to HPR code execution.

debug appn ms

Displays debugging information on APPN MS component activity.

debug appn nof

Displays information on APPN NOF component activity.

debug appn pc

Displays debugging information on APPN PC component activity.

debug appn ps

Displays debugging information on APPN PS component activity.

debug appn scm

Displays debugging information on APPN SCM component activity.


DB-84

May 2008

Debug Commands debug appn all

Command

Description

debug appn ss

Displays SS events.

debug appn ss

Displays debugging information on APPN TRS component activity.


DB-85

Debug Commands debug appn cs

debug appn cs To display Advanced Peer-to-Peer Networking (APPN) Configuration Services (CS) component activity, use the debug appn cs command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug appn cs no debug appn cs

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The CS component is responsible for defining link stations, ports, and connection networks. It is responsible for the activation and deactivation of ports and link stations and handles status queries for these resources.

Examples

The following is sample output from the debug appn cs command. In this example a link station is being stopped. Router# debug appn cs Turned on event 008000FF Router# appn stop link PATTY APPN: ----- CS ----APPN: ----- CS ----APPN: ----- CS ----APPN: ----- CS ----APPN: ----- CS ----APPN: ----- CS ----APPN: ----- CS ----APPN: ----- CS ----APPN: ----- CS ----APPN: ----- CS ----%APPN-6-APPNSENDMSG:

Deq STOP_LS message FSM LS: 75 17 5 8 Sending DEACTIVATE_AS - station PATTY deactivate_as_p->ips_header.lpid = A80A60 deactivate_as_p->ips_header.lpid = A80A60 Sending DESTROY_TG to PC - station PATTY - lpid=A80A60 Deq DESTROY_TG - station PATTY FSM LS: 22 27 8 0 Sending TG update for LS PATTY to TRS ENTERING XID_PROCESSING: 4 Link Station PATTY stopped

Table 12 describes the significant fields and messages shown in the display. Table 12

debug appn cs Field Descriptions

Field

Description

APPN

APPN debugging output.

CS

CS component output.

Deq

CS received a message from another component.


DB-86

May 2008

Debug Commands debug appn cs

Table 12

Related Commands

debug appn cs Field Descriptions (continued)

Field

Description

FSM LS

Link station finite state machine is being referenced.

Sending

CS is sending a message to another component.

Command

Description

debug appn all

Turns on all possible debugging messages for APPN.


DB-87

Debug Commands debug appn ds

debug appn ds To display debugging information on Advanced Peer-to-Peer Networking (APPN) Directory Services (DS) component activity, use the debug appn ds command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug appn ds no debug appn ds

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The DS component manages searches for resources in the APPN network. DS is also responsible for registration of resources within the network.

Examples

The following is sample output from the debug appn ds command. In this example a search has been received. Router# debug appn ds Turned on event 080000FF APPN: NEWDS: LS: search from: NETA.PATTY APPN: NEWDS: pcid: DD3321E8B5667111 APPN: NEWDS: Invoking FSM NNSolu APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: APPN: NEWDS: LSfsm_parent: 00A89940 row: 0 col: 0 inp: 80000000 APPN: NEWDS: Rcvd a LMRQ APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: APPN: NEWDS: LSfsm_parent: 00A89940 row: 8 col: 1 inp: 40000000 APPN: NEWDS: LSfsm_child: 00A89BE8 row: 0 col: 0 inp: 80000080 APPN: NEWDS: PQenq REQUEST_ROUTE(RQ) to TRS APPN: NEWDS: LSfsm_child: 00A8A1C0 row: 1 col: 0 inp: 80000008 APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: APPN: NEWDS: LSfsm_child: 00A8A1C0 row: 7 col: 1 inp: 80844008 APPN: NEWDS: Rcvd a LMRY APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: APPN: NEWDS: LSfsm_child: 00A8A1C0 row: 14 col: 5 inp: 40800000 APPN: NEWDS: LSfsm_parent: 00A89940 row: 3 col: 1 inp: 80840000 APPN: NEWDS: send locate to node: NETA.PATTY

0 col: 0 inp: 80200000

12 col: 1 inp: 40000000

5 col: 1 inp: 80C04000

16 col: 6 inp: 40800000


debug appn ds Field Descriptions

Field

Description

APPN


NEWDS

DS component output.

search from

Locate was received from NETA.PATTY.


DB-88

May 2008

Debug Commands debug appn ds

Table 13

Related Commands

debug appn ds Field Descriptions (continued)

Field

Description

LSfsm_

Locate Search finite state machine is being referenced.

PQenq

Message was sent to another component.

Rcvd

Message was received from another component.

send locate

Locate will be sent to NETA.PATTY.

Command

Description

debug appn all



DB-89

Debug Commands debug appn hpr

debug appn hpr To display debugging information related to High Performance Routing (HPR) code execution, use the debug appn hpr command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug appn hpr no debug appn hpr

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug appn hpr command: Router# debug appn hpr APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN:

-- ncl.ncl_map_dlc_type() -- mapping TOKEN_RING(4) to NCL_TR(3) -- ncl.ncl_port() -- called with port_type:3, cisco_idb:893A14, hpr_ssap:C8 -- ncl.process_port_change() -- port coming up -- ncl.process_port_change() -- PORT_UP -- ncl.ncl_port_fsm -- FSM Invoked: Input:0, State:0->1, Action:0 -- ncl.ncl_port_fsm -- FSM Invoked: Input:1, State:1->2, Action:1 -- ncl.ncl_unmap_dlc_type() -- mapping NCL(3) to CLS(3) ----- ANR ----- Sending ACTIVATE_SAP.req -- cswncsnd.main() -- received LSA_IPS ips. -- ncl.ncl_port_fsm -- FSM Invoked: Input:3, State:2->3, Action:4 -- ncl.ncl_assign_anr() -- Assigned ANR,anr:8002 -- ncl.ncl_map_dlc_type() -- mapping TOKEN_RING(4) to NCL_TR(3) -- ncl.ncl_populate_anr() -- anr:8002, dlc_type:3, idb 893A14 -- ncl.ncl_populate_anr() -- send anr_tbl_update to owning cswncsnd -- ncl.ncl_ls_fsm -- FSM Invoked: Input:0, State:0->1, Action:0 ncl.ncl_send_reqopn_stn_req -- ncl.ncl_unmap_dlc_type() -- mapping NCL(3) to CLS(3) -- ncl.ncl_ls_fsm() -- send anr_tbl_update to owning cswncsnd -- cswncsnd.main() -- received ANR_TBL_UPDATE ips. -- cswncsnd.apply_anr_table_update() -- ANR:8002 -- cswncsnd.main() -- received ANR_TBL_UPDATE ips. -- cswncsnd.apply_anr_table_update() -- ANR:8002 -- cswncsnd.main() -- received LSA_IPS ips. -- ncl.ncl_ls_fsm -- FSM Invoked: Input:1, State:1->2, Action:1 -- ncl.ncl_ls_fsm -- P_CEP_ID:AAF638 -- ncl.ncl_ls_fsm() -- send anr_tbl_update to owning cswncsnd -- cswncsnd.main() -- received ANR_TBL_UPDATE ips. -- cswncsnd.apply_anr_table_update() -- ANR:8002 rtpm: rtp_send() sent data over connection B9D5E8 hpr timer: rtt start time clocked at 135952 ms -- cswncsnd.main() -- received NCL_SND_MSG ips. -- cswncsnd.process_nlp_from_rtp() -- label: 8002, send to p_cep 00AAF638. hpr timer: rtt end time clocked at 135972 ms hpr timer: round trip time measured at 20 ms

Table 14 describes the significant fields shown in the display.


DB-90

May 2008

Debug Commands debug appn hpr

Table 14

Related Commands

debug appn hpr Field Descriptions

Field

Description

APPN


NCL

Network control layer debugging output. Network control layer is the component that handles ANR packets.

ncl_port_fsm

Network control layer port finite state machine has been invoked.

ncl_assign_anr

ANR label has been assigned to an activating link station.

ncl_populate_anr

System is updating the ANR record with information specific to the link station.

ncl_ls_fsm

Network control layer link finite state machine has been invoked.

rtp_send

RTP is about to send a packet.

hpr timer

Debugging output related to an HPR timer.

rtt start time

RTP is measuring the round-trip time for an HPR status request packet. This is the start time.

NCL_SND_MSG

Network control layer has been requested to send a packet.

process_nlp_from_rtp

Network control layer has been requested by RTP to send a packet.

rtt end time

RTP is measuring the round-trip time for an HPR status request packet. This is the time.

round trip time

Round-trip time for this HPR status exchange has been computed.

Command

Description

debug appn all



DB-91

Debug Commands debug appn ms

debug appn ms To display debugging information on Advanced Peer-to-Peer Networking (APPN) Management Services (MS) component activity, use the debug appn ms command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug appn ms no debug appn ms

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The MS component is responsible for generating, sending, and forwarding network management information in the form of traps and alerts to a network management focal point, such as Netview, in the APPN network.

Examples

The following is sample output from the debug appn ms command. In this example an error occurred that caused an alert to be generated. Router# debug appn ms APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN: APPN:

----- MSS00 ---- Deq ALERT_MSU msg --- MSP70 --- ALERT MV FROM APPN WITH VALID LGTH --- MSCPL --- Find Active FP --- MSP30 --- Entering Build MS Transport --- MSP31 --- Entering Building Routing Info. --- MSP34 --- Entering Build GDS --- MSP32 --- Entering Building UOW correlator --- MSP34 --- Entering Build GDS --- MSP30 --- Building GDS 0x1310 --- MSP30 --- Building MS Transport --- MSP72 --- ACTIVE FP NOT FOUND, SAVE ONLY --- MSUTL --- UOW File not found *Sep 14 18:37:31.535:%AUDIT-1-RUN_VERSION:Hash: 24D98B13B87D106E7E6A7E5D1B3CE0AD User: *Sep 14 18:37:31.583:%AUDIT-1-RUN_CONFIG:Hash: 4AC2D776AA6FCA8FD7653CEB8969B695 User: *Sep 14 18:37:31.587:Audit:Trying to hash nvram:startup-config *Sep 14 18:37:31.587:Audit:nvram:startup-config Done. *Sep 14 18:37:31.587:Audit:Trying to hash nvram:private-config *Sep 14 18:37:31.591:Audit:nvram:private-config Done. *Sep 14 18:37:31.591:Audit:Trying to hash nvram:underlying-config *Sep 14 18:37:31.591:Audit:nvram:underlying-config Done. *Sep 14 18:37:31.591:Audit:Trying to hash nvram:persistent-data *Sep 14 18:37:31.591:Audit:nvram:persistent-data Done. *Sep 14 18:37:31.595:Audit:Trying to hash nvram:ifIndex-table *Sep 14 18:37:31.595:Audit:Skipping nvram:ifIndex-table *Sep 14 18:37:31.595:%AUDIT-1-STARTUP_CONFIG:Hash: 95DD497B1BB61AB33A629124CBFEC0FC User: *Sep 14 18:37:31.595:Audit:Trying to hash filesystem disk0:


DB-158

May 2008

Debug Commands debug audit

*Sep 14 18:37:31.775:Audit:Trying to hash attributes of disk0:c7200-p-mz.120-23.S *Sep 14 18:37:32.103:Audit:disk0:c7200-p-mz.120-23.S DONE *Sep 14 18:37:32.103:Audit:disk0:DONE *Sep 14 18:37:32.103:Audit:Trying to hash filesystem bootflash: *Sep 14 18:37:32.103:Audit:Trying to hash attributes of bootflash:c7200-kboot-mz.121-8a.E *Sep 14 18:37:32.107:Audit:bootflash:c7200-kboot-mz.121-8a.E DONE *Sep 14 18:37:32.107:Audit:Trying to hash attributes of bootflash:crashinfo_20030115-182547 *Sep 14 18:37:32.107:Audit:bootflash:crashinfo_20030115-182547 DONE *Sep 14 18:37:32.107:Audit:Trying to hash attributes of bootflash:crashinfo_20030115-212157 *Sep 14 18:37:32.107:Audit:bootflash:crashinfo_20030115-212157 DONE *Sep 14 18:37:32.107:Audit:Trying to hash attributes of bootflash:crashinfo_20030603-155534 *Sep 14 18:37:32.107:Audit:bootflash:crashinfo_20030603-155534 DONE *Sep 14 18:37:32.107:Audit:bootflash:DONE *Sep 14 18:37:32.107:%AUDIT-1-FILESYSTEM:Hash: 330E7111F2B526F0B850C24ED5774EDE User: *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for 7206VXR chassis, Hw Serial#:28710795, Hw Revision:A *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for NPE 400 Card, Hw Serial#:28710795, Hw Revision:A *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for I/O Dual FastEthernet Controller *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for i82543 (Livengood) *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for i82543 (Livengood) *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot *Sep 14 18:37:32.107:Audit:Hashing entitymib entry for Chassis Slot *Sep 14 18:37:32.107:%AUDIT-1-HARDWARE_CONFIG:Hash: 32F66463DDA802CC9171AF6386663D20 User:

Related Commands

Command

Description

audit filesize

Changes the size of the audit file.

audit interval

Changes the time interval that is used for calculating hashes.


DB-159

Debug Commands debug autoupgrade

debug autoupgrade To display the debug output of the Cisco IOS Auto-Upgrade Manager (AUM), use the debug autoupgrade command in privileged EXEC mode. To disable debug output, use the no form of this command. debug autoupgrade no debug autoupgrade

Syntax Description


Command Default

The debug output is disabled.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(15)T


12.2SX


Usage Guidelines

Use the debug autoupgrade command when you encounter a problem with AUM and provide the output to TAC. Run the debug autoupgrade command and then run AUM to view the debug messages.

Examples

The following example shows how to enable the debugging of Cisco IOS Auto-Upgrade Manager: Router# debug autoupgrade Auto Upgrade Manager debugging ON Router# Router# upgrade automatic getversion tftp://10.1.0.1/username/aaa Image not found. Router# Jun 14 14:23:08.251 IST: AUM: Currently running software: flash:c3825-adventerprisek9-mz.CALVIN_AUM_EFT1 Jun 14 14:23:08.251 IST: AUM: Reload type:2 hour:0 min:0 Jun 14 14:23:08.251 IST: AUM: Disk management: 1 Jun 14 14:23:08.251 IST: AUM: Get image tftp://10.1.0.1/username/aaa from local server and upgrade: Jun 14 14:23:08.251 IST: AUM: Extracted image name: aaa Jun 14 14:23:08.339 IST: AUM: get image info: failed to open url Jun 14 14:23:08.339 IST: AUM: get image info: image size unknown


DB-160

May 2008

Debug Commands debug autoupgrade

Related Commands

Command

Description

upgrade automatic getversion

Downloads a Cisco IOS software image directly from www.cisco.com or from a non-Cisco server.


DB-161

Debug Commands debug auto-config

debug auto-config To enable debugging for autoconfiguration applications, use the debug auto-config command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug auto-config {all | errors | events | parser} no debug auto-config {all | errors | events | parser}

Syntax Description

all

Displays all autoconfiguration debug trace.

errors

Displays autoconfiguration errors.

events

Displays autoconfiguration events.

parser

Displays autoconfiguration parser.

Command Default

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)XY

This command was introduced on the Communication Media Module.

12.3(14)T


12.4(3)

This command was integrated into Cisco IOS Release 12.4(3).

12.2SX


Examples

The following example shows the debug auto-config command used to enable debugging for autoconfiguration applications and to display autoconfiguration events: Router# debug auto-config events . . . Feb 8 02:17:31.119: dnld_app_check_state(0x628C8164)... Feb 8 02:17:31.123: dnld_chk_app_handle(0x628C8164) Feb 8 02:17:31.123: dnld_app_check_state: appl = 0x628C8164, state = 0x11 . . .


DB-162

May 2008

Debug Commands debug auto-config

Table 34 describes significant fields shown in the display. Table 34

debug auto-config Field Descriptions

Field

Description

0x628C8164

Identifies the application handle, an auto-generated number for debugging.

0x11

Displays the state of the application. State values are as follows: 0x11—Registered and enabled. 0x1—Download application enabled. 0x10—Download application registered.

Related Commands

Command

Description

auto-config

Enables autoconfiguration or enters auto-config application configuration mode for the SCCP application.

debug sccp config

Enables SCCP event debugging.

show auto-config

Displays the current status of autoconfiguration applications.


DB-163

Debug Commands debug backhaul-session-manager session

debug backhaul-session-manager session To debug all the available sessions or a specified session, use the debug backhaul-session-manager session command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug backhaul-session-manager session {state | xport} {all | session-id} no debug backhaul-session-manager session {state | xport} {all | session-id}

Caution

Syntax Description

Use caution when enabling this debug command in a live system. It produces significant amounts of output, which could lead to a disruption of service.

state

Shows information about state transitions. Possible states are as follows: SESS_SET_IDLE: A session-set has been created. SESS_SET_OOS: A session(s) has been added to session-group(s). No ACTIVE notification has been received from Virtual Switch Controller (VSC). SESS_SET_ACTIVE_IS: An ACTIVE notification has been received over one in-service session-group. STANDBY notification has not been received on any available session-group(s). SESS_SET_STNDBY_IS: A STANDBY notification is received, but there is no in-service active session-group available. SESS_SET_FULL_IS: A session-group in-service that has ACTIVE notification and at least one session-group in-service that has STANDBY notification. SESS_SET_SWITCH_OVER: An ACTIVE notification is received on session-group in-service, which had received STANDBY notification.

xport

Provides traces for all packets (protocol data units (PDUs)), application PDUs, and also session-manager messages.

all

All available sessions.

session-id

A specified session.

Defaults

Debugging for backhaul-session-manager session is not enabled.

Command Modes

Privileged EXEC


DB-164

May 2008


Command History

Examples

Release

Modification

12.1(1)T


12.2(2)T

Support for this command was introduced on the Cisco 7200 series routers.

12.2(4)T

This command was implemented on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.

12.2(2)XB

This command was implemented on the Cisco AS5350 and Cisco AS5400.

12.2(2)XB1

This command was implemented on the Cisco AS5850 platform.

12.2(8)T

This command was implemented on Cisco IAD2420 series integrated access devices (IADs). This command is not supported on the access servers in this release.

12.2(11)T

This command was implemented on Cisco AS5350, Cisco AS5400, and Cisco AS5850 platforms.

12.2(33)SRA


12.2SX


The following is output for the debug backhaul-session-manager session all command: Router# debug backhaul-session-manager session all Router# debug_bsm_command:DEBUG_BSM_SESSION_ALL 23:49:14:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET) 23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE 23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:14:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT 23:49:14:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:19:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET) 23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE 23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:19:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT 23:49:19:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:24:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET) 23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE 23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:24:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT 23:49:24:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:29:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET) 23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE 23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:29:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT


DB-165


23:49:29:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:34:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET) 23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE 23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:34:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT 23:49:34:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:49:34:SESSION:XPORT:sig rcvd. session = 33, connid = 0x80BA14EC, sig = 1 (CONN-FAILED) 23:49:34:SESSION:STATE:(33) old-state:OPEN, new-state:CLOSE_WAIT

The following example displays output for the debug backhaul-session-manager session state all command: Router# debug backhaul-session-manager session state all Router# debug_bsm_command:DEBUG_BSM_SESSION_STATE_ALL 23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:CLOSE 23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS 23:50:54:SESSION:STATE:(34) old-state:OPEN_WAIT, new-state:OPEN_WAIT 23:50:54:SESSION:STATE:(34) state:OPEN_WAIT, use-state:OOS

The following example displays output for the debug backhaul-session-manager session xport all command: Router# debug backhaul-session-manager session xport all Router# debug_bsm_command:DEBUG_BSM_SESSION_XPORT 23:51:39:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET) 23:51:42:SESSION:XPORT:sig rcvd. session = 33, connid = 0x80BA14EC, sig = 5 (CONN-RESET) 23:51:44:SESSION:XPORT:sig rcvd. session = 34, connid = 0x80BA12FC, sig = 5 (CONN-RESET)

Related Commands

Command

Description

debug backhaul-session-manager set

Traces state changes and receives messages and events for all available session-sets or a specified session-set.


DB-166

May 2008

Debug Commands debug backhaul-session-manager set

debug backhaul-session-manager set To trace state changes and receive messages and events for all the available session sets or a specified session set, use the debug backhaul-session-manager set command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug backhaul-session-manager set {all | name set-name} no debug backhaul-session-manager set {all | name set-name}

Syntax Description

all

All available session sets.

name set-name

A specified session set.

Defaults

Debugging for backhaul session sets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T


12.2(2)T

Support for this command was introduced on the Cisco 7200 series routers.

12.2(4)T


12.2(2)XB


12.2(2)XB1


12.2(8)T

This command was implemented on Cisco IAD2420 series integrated access devices (IADs). This command is not supported on the access servers in this release.

12.2(11)T

This command was implemented on Cisco AS5350, Cisco AS5400, and Cisco AS5850 platforms.

12.2(33)SRA


12.2SX



DB-167

Debug Commands debug backhaul-session-manager set

Examples

The following is output for the debug backhaul-session-manager set command for all available session sets: Router# debug backhaul-session-manager set all Router# debug_bsm_command:DEBUG_BSM_SET_ALL Function set_proc_event() is called Session-Set :test-set Old State :BSM_SET_OOS New State :BSM_SET_OOS Active-Grp :NONE Session-Grp :g-11 Old State :Group-None New State :Group-None Event rcvd :EVT_GRP_INS BSM:Event BSM_SET_UP is sent to user Session-Set :test-set Old State :BSM_SET_OOS New State :BSM_SET_ACTIVE_IS Active-Grp :g-11 Session-Grp :g-11 Old State :Group-None New State :Group-Active Event rcvd :BSM_ACTIVE_TYPE

The following is output for the debug backhaul-session-manager set name set1 command: Router# debug backhaul-session-manager set name set1 Router# debug_bsm_command:DEBUG_BSM_SET_NAME Router# Function set_proc_event() is called Session-Set :test-set Old State :BSM_SET_OOS New State :BSM_SET_OOS Active-Grp :NONE Session-Grp :g-11 Old State :Group-None New State :Group-None Event rcvd :EVT_GRP_INS Router#BSM:Event BSM_SET_UP is sent to user Session-Set :test-set Old State :BSM_SET_OOS New State :BSM_SET_ACTIVE_IS Active-Grp :g-11 Session-Grp :g-11 Old State :Group-None New State :Group-Active Event rcvd :BSM_ACTIVE_TYPE

Related Commands

Command

Description

debug backhaul-session-manager session

Debugs all available sessions or a specified session.


DB-168

May 2008

Debug Commands debug backup

debug backup To monitor the transitions of an interface going down then back up, use the debug backup command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug backup no debug backup

Syntax Description


Defaults

No default behavior or values.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0


12.2(33)SRA


12.2SX


Usage Guidelines

The debug backup command is useful for monitoring dual X.25 interfaces configured as primary and backup in a Telco data communication network (DCN).

Examples

The following example shows how to start the debug backup command: Router# debug backup

Related Commands

Command

Description

backup active interface

Activates primary and backup lines on specific X.25 interfaces.

show backup

Displays interface backup status.


DB-169

Debug Commands debug bert

debug bert To display information on the bit error rate testing (BERT) feature, use the debug bert command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bert no debug bert

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(2)XD


12.2(33)SRA


12.2SX


Usage Guidelines

The debug bert command output is used primarily by Cisco technical support representatives. The debug bert command displays debugging messages for specific areas of executed code.

Examples

The following is output from the debug bert command: Router# debug bert Bit Error Rate Testing debugging is on Router# no debug bert Bit Error Rate Testing debugging is off

Related Commands

Command

Description

bert abort

Aborts a bit error rate testing session.

bert controller

Starts a bit error rate test for a particular port on a Cisco AS5300 router.

bert profile

Sets up various bit error rate testing profiles.


DB-170

May 2008

Debug Commands debug bfd

debug bfd To display debugging messages about Bidirectional Forwarding Detection (BFD), use the debug bfd command in privileged EXEC mode. To disable debugging output, use the no form of this command. Cisco IOS Release 12.2(18)SXE, 12.4(4)T, and 12.2(33)SRA

debug bfd {event | packet [ip-address]} no debug bfd {event | packet [ip-address]} Cisco IOS Release 12.0(31)S

debug bfd {event | packet [ip-address] | ipc-error | ipc-event | oir-error | oir-event} no debug bfd {event | packet [ip-address] | ipc-error | ipc-event | oir-error | oir-event}

Syntax Description

event

(Optional) Displays debugging information about BFD state transitions.

packet

(Optional) Displays debugging information about BFD control packets.

ip-address

(Optional) Displays debugging information about BFD only for the specified IP address.

ipc-error

(Optional) Displays debugging information with interprocess communication (IPC) errors on the Route Processor (RP) and line card (LC).

ipc-event

(Optional) Displays debugging information with IPC events on the RP and LC.

oir-error

(Optional) Displays debugging information with online insertion and removal (OIR) errors on the RP and LC.

oir-event

(Optional) Displays debugging information with OIR events on the RP and LC.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(18)SXE


12.0(31)S


12.4(4)T


12.2(33)SRA


12.2SX



DB-171


Usage Guidelines

Note

Examples

The debug bfd command can be used to troubleshoot the BFD feature.

Because BFD is designed to send and receive packets at a very high rate, consider the potential effect on system resources before enabling this command, especially if there are a large number of BFD peers. The debug bfd packet command should be enabled only on a live network at the direction of Cisco Technical Assistance Center personnel.

The following example shows output from the debug bfd packet command. The IP address has been specified in order to limit the packet information to one interface: Router# debug bfd packet 172.16.10.5 BFD packet debugging is on *Jan 26 14:47:37.645: Tx*IP: dst 172.16.10.1, plen 24. BFD: diag 2, St/D/P/F (1/0/0/0), mult 5, len 24, loc/rem discr 1 1, tx 1000000, rx 1000000 100000, timer 1000 ms, #103 *Jan 26 14:47:37.645: %OSPF-5-ADJCHG: Process 10, Nbr 172.16.10.12 on Ethernet1/4 from FULL to DOWN, Neighbor Down: BFD node down *Jan 26 14:47:50.685: %OSPF-5-ADJCHG: Process 10, Nbr 172.16.10.12 on Ethernet1/4 from LOADING to FULL, Loading Done *Jan 26 14:48:00.905: Rx IP: src 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (1/0/0/0), mult 4, len 24, loc/rem discr 2 1, tx 1000000, rx 1000000 100000, timer 4000 ms, #50 *Jan 26 14:48:00.905: Tx IP: dst 172.16.10.1, plen 24. BFD: diag 2, St/D/P/F (2/0/0/0), mult 5, len 24, loc/rem discr 1 2, tx 1000000, rx 1000000 100000, timer 1000 ms, #131 *Jan 26 14:48:00.905: Rx IP: src 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (3/0/0/0), mult 4, len 24, loc/rem discr 2 1, tx 1000000, rx 1000000 100000, timer 4000 ms, #51 *Jan 26 14:48:00.905: Tx IP: dst 172.16.10.1, plen 24. BFD: diag 0, St/D/P/F (3/0/0/0), mult 5, len 24, loc/rem discr 1 2, tx 1000000, rx 1000000 100000, timer 1000 ms, #132

The following example shows output from the debug bfd event command when an interface between two BFD neighbor routers fails and then comes back online: Router# debug bfd event 22:53:48: BFD: bfd_neighbor - action:DESTROY, proc:1024, idb:FastEthernet0/1, neighbor:172.16.10.2 22:53:48: BFD: bfd_neighbor - action:DESTROY, proc:512, idb:FastEthernet0/1, neighbor:172.16.10.2 22:53:49: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event DETECT TIMER EXPIRED, state UP -> FAILING . . . 22:56:35: BFD: bfd_neighbor - action:CREATE, proc:1024, idb:FastEthernet0/1, neighbor:172.16.10.2 22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 0, state FAILING -> DOWN 22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 0, state DOWN -> INIT 22:56:37: Session [172.16.10.1,172.16.10.2,Fa0/1,1], event RX IHY 1, state INIT -> UP


DB-172

May 2008



debug bfd event Field Descriptions

Field

Description

bfd_neighbor action:DESTROY

The BFD neighbor will tear down the BFD session.

Session [172.16.10.1, 172.16.10.2, Fa0/1,1]

IP addresses of the BFD neighbors holding this session that is carried over FastEthernet interface 0/1.

event DETECT TIMER EXPIRED

The BFD neighbor has not received BFD control packets within the negotiated interval and the detect timer has expired.

state UP -> FAILING

The BFD event state is changing from Up to Failing.

Session [172.16.10.1, 172.16.10.2, Fa0/1,1], event RX IHY 0

The BFD session between the neighbors indicated by the IP addresses that is carried over FastEthernet interface 0/1 is changing state from Failing to Down. The I Hear You (IHY) bit value is shown as 0 to indicate that the remote system is tearing down the BFD session.

event RX IHY 0, state DOWN -> INIT

The BFD session is still considered down, and the IHY bit value still is shown as 0, and the session state changes from DOWN to INIT to indicate that the BFD session is again initializing, as the interface comes back up.

event RX IHY 1, state INIT -> UP

The BFD session has been reestablished, and the IHY bit value changes to 1 to indicate that the session is live. The BFD session state changes from INIT to UP.

The following example shows output from the debug bfd packet command when an interface between two BFD neighbor routers fails and then comes back online. The diagnostic code changes from 0 (No Diagnostic) to 1 (Control Detection Time Expired) because no BFD control packets could be sent (and therefore detected by the BFD peer) after the interface fails. When the interface comes back online, the diagnostic code changes back to 0 to signify that BFD packets can be sent and received by the BFD peers. Router# debug bfd packet 23:03:25: Rx IP: src 172.16.10.2, plen 24. BFD: diag 0, H/D/P/F (0/0/0/0), mult 3, len 24, loc/rem discr 5 1, tx 1000000, rx 100007 23:03:25: Tx IP: dst 172.16.10.2, plen 24. BFD: diag 1, H/D/P/F (0/0/0/0), mult 5, len 24, loc/rem discr 1 5, tx 1000000, rx 1000008 23:03:25: Tx IP: dst 172.16.10.2, plen 24. BFD: diag 1, H/D/P/F (1/0/0/0), mult 5, len 24, loc/rem discr 1 5, tx 1000000, rx 1000009


debug bfd packet Field Descriptions

Field

Description

Rx IP: src 172.16.10.2

The router has received this BFD packet from the BFD router with source address 172.16.10.2.

plen 24

Length of the BFD control packet, in bytes.


DB-173


Table 36

debug bfd packet Field Descriptions (continued)

Field

Description

diag 0

A diagnostic code specifying the local system’s reason for the last transition of the session from Up to some other state. State values are as follows:

H/D/P/F (0/0/0/0)

•

0—No Diagnostic

•

1—Control Detection Time Expired

•

2—Echo Function Failed

•

3—Neighbor Signaled Session Down

•

4—Forwarding Plane Reset

•

5—Path Down

•

6—Concentrated Path Down

•

7—Administratively Down

H bit—Hear You bit. This bit is set to 0 if the transmitting system either is not receiving BFD packets from the remote system or is tearing down the BFD session. During normal operation the I Hear You bit is set to 1. D bit—Demand Mode bit. If the Demand Mode bit set, the transmitting system wants to operate in demand mode. BFS has two modes—asynchronous and demand. The Cisco implementation of BFD supports only asynchronous mode. P bit—Poll bit. If the Poll bit is set, the transmitting system is requesting verification of connectivity or of a parameter change. F bit—Final bit. If the Final bit is set, the transmitting system is responding to a received BFC control packet that had a Poll (P) bit set.

mult 3

Detect time multiplier. The negotiated transmit interval, multiplied by the detect time multiplier, determines the detection time for the transmitting system in BFD asynchronous mode. The detect time multiplier is similar to the hello multiplier in IS-IS, which is used to determine the holdtimer: (hellointerval) * (hellomultiplier) = holdtimer. If a hello packet is not received within the hold-timer interval, a failure has occurred. Similarly, for BFD: (transmit interval) * (detect multiplier) = detect timer. If a BFD control packet is not received from the remote system within the detect-timer interval, a failure has occurred.

len 24

The BFD packet length.


DB-174

May 2008


Table 36

debug bfd packet Field Descriptions (continued)

Field

Description

loc/rem discr 5 1

The values for My Discriminator (local) and Your Discriminator (remote) BFD neighbors. •

My Discriminator—Unique, nonzero discriminator value generated by the transmitting system, used to demultiplex multiple BFD sessions between the same pair of systems.

•

Your Discriminator—The discriminator received from the corresponding remote system. This field reflects the received value of My Discriminator, or is zero if that value is unknown.

tx 1000000

Desired minimum transmit interval.

rx 100007

Required minimum receive interval.


DB-175

Debug Commands debug bgp ipv6 dampening

debug bgp ipv6 dampening To display debugging messages for IPv6 Border Gateway Protocol (BGP) dampening, use the debug bgp ipv6 dampening command in privileged EXEC mode. To disable debugging messages for IPv6 BGP dampening, use the no form of this command. debug bgp ipv6 {unicast | multicast} dampening [prefix-list prefix-list-name] no debug bgp ipv6 {unicast | multicast} dampening [prefix-list prefix-list-name]

Syntax Description

unicast

Specifies IPv6 unicast address prefixes.

multicast

Specifies IPv6 multicast address prefixes.

prefix-list prefix-list-name

(Optional) Name of an IPv6 prefix list.

Command Default

Debugging for IPv6 BGP dampening packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)T


12.0(21)ST

This command was integrated into Cisco IOS Release 12.0(21)ST.

12.0(22)S


Usage Guidelines

12.2(13)T

The prefix-list keyword was added.

12.0(24)S


12.2(14)S


12.2(28)SB


12.2(25)SG

This command was integrated into Cisco IOS Release 12.2(25)SG.

12.2(33)SRA


12.2(33)SXH


12.2SX


The debug bgp ipv6 dampening command is similar to the debug ip bgp dampening command, except that it is IPv6-specific. Use the prefix-list keyword and an argument to filter BGP IPv6 dampening debug information through an IPv6 prefix list.


DB-176

May 2008


Note

Examples

By default, the network server sends the output from debug commands and system error messages to the console. To redirect debugging output, use the logging command options within global configuration mode. Destinations are the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server.

The following is sample output from the debug bgp ipv6 dampening command: Router# debug bgp ipv6 dampening 00:13:28:BGP(1):charge penalty for 2000:0:0:1::/64 path 2 1 reuse/suppress 750/2000 00:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty 00:13:28:BGP(1):charge penalty for 2000:0:0:1:1::/80 path 2 reuse/suppress 750/2000 00:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty 00:13:28:BGP(1):charge penalty for 2000:0:0:5::/64 path 2 1 reuse/suppress 750/2000 00:13:28:BGP(1):flapped 1 times since 00:00:00. New penalty 00:16:03:BGP(1):charge penalty for 2000:0:0:1::/64 path 2 1 reuse/suppress 750/2000 00:16:03:BGP(1):flapped 2 times since 00:02:35. New penalty

with halflife-time 15 is 1000 1 with halflife-time 15 is 1000 with halflife-time 15 is 1000 with halflife-time 15 is 1892

00:18:28:BGP(1):suppress 2000:0:0:1:1::/80 path 2 1 for 00:27:30 (penalty 2671) 00:18:28:halflife-time 15, reuse/suppress 750/2000 00:18:28:BGP(1):suppress 2000:0:0:1::/64 path 2 1 for 00:27:20 (penalty 2664) 00:18:28:halflife-time 15, reuse/suppress 750/2000

The following example shows output for the debug bgp ipv6 dampening command filtered through the prefix list named marketing: Router# debug bgp ipv6 dampening prefix-list marketing 00:16:08:BGP(1):charge penalty for 2001:0DB8::/64 path 30 with halflife-time 15 reuse/suppress 750/2000 00:16:08:BGP(1):flapped 1 times since 00:00:00. New penalty is 10

Table 37 describes the fields shown in the display. Table 37

debug bgp ipv6 dampening Field Descriptions

Field

Description

penalty

Numerical value of 1000 assigned to a route by a router configured for route dampening in another autonomous system each time a route flaps. Penalties are cumulative. The penalty for the route is stored in the BGP routing table until the penalty exceeds the suppress limit. If the penalty exceeds the suppress limit, the route state changes from history to damp.

flapped

Number of times a route is available, then unavailable, or vice versa.

halflife-time

Amount of time (in minutes) by which the penalty is decreased after the route is assigned a penalty. The halflife-time value is half of the half-life period (which is 15 minutes by default). Penalty reduction happens every 5 seconds.


DB-177


Table 37

debug bgp ipv6 dampening Field Descriptions (continued)

Field

Description

reuse

The limit by which a route is unsuppressed. If the penalty for a flapping route decreases and falls below this reuse limit, the route is unsuppressed. That is, the route is added back to the BGP table and once again used for forwarding. The default reuse limit is 750. Routes are unsuppressed at 10-second increments. Every 10 seconds, the router determines which routes are now unsuppressed and advertises them to the world.

suppress

Limit by which a route is suppressed. If the penalty exceeds this limit, the route is suppressed. The default value is 2000.

maximum suppress limit Maximum amount of time (in minutes) a route is suppressed. The (not shown in sample output) default value is four times the half-life period. damp state State in which the route has flapped so often that the router will not (not shown in sample output) advertise this route to BGP neighbors.

Related Commands

Command

Description

debug bgp ipv6 updates

Displays debugging messages for IPv6 BGP update packets.


DB-178

May 2008

Debug Commands debug bgp ipv6 updates

debug bgp ipv6 updates To display debugging messages for IPv6 Border Gateway Protocol (BGP) update packets, use the debug bgp ipv6 updates command in privileged EXEC mode. To disable debugging messages for IPv6 BGP update packets, use the no form of this command. debug bgp ipv6 {unicast | multicast} updates [ipv6-address] [prefix-list prefix-list-name] [in | out] no debug bgp ipv6 {unicast | multicast} updates [ipv6-address] [prefix-list prefix-list-name] [in | out]

Syntax Description

unicast

Specifies IPv6 unicast address prefixes.

multicast

Specifies IPv6 multicast address prefixes.

ipv6-address

(Optional) The IPv6 address of a BGP neighbor. This argument must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.

prefix-list prefix-list-name

(Optional) Name of an IPv6 prefix list.

in

(Optional) Indicates inbound updates.

out

(Optional) Indicates outbound updates.

Command Default

Debugging for IPv6 BGP update packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)T


12.0(21)ST


12.0(22)S


12.2(13)T


12.0(24)S


12.2(14)S


12.2(28)SB


12.2(25)SG

This command was integrated into Cisco IOS Release 12.2(25)SG.

12.2(33)SRA


12.2SX



DB-179


Usage Guidelines

The debug bgp ipv6 updates command is similar to the debug ip bgp updates command, except that it is IPv6-specific. Use the prefix-list keyword to filter BGP IPv6 updates debugging information through an IPv6 prefix list.

Note

Examples

By default, the network server sends the output from debug commands and system error messages to the console. To redirect debugging output, use the logging command options within global configuration mode. Destinations are the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server. For complete information on debug commands and redirecting debugging output, refer to the Release 12.2 Cisco IOS Debug Command Reference.

The following is sample output from the debug bgp ipv6 updates command: Router# debug bgp ipv6 updates 14:04:17:BGP(1):2000:0:0:2::2 computing updates, afi 1, neighbor version 0, table version 1, starting at :: 14:04:17:BGP(1):2000:0:0:2::2 update run completed, afi 1, ran for 0ms, neighbor version 0, start version 1, throttled to 1 14:04:19:BGP(1):sourced route for 2000:0:0:2::1/64 path #0 changed (weight 32768) 14:04:19:BGP(1):2000:0:0:2::1/64 route sourced locally 14:04:19:BGP(1):2000:0:0:2:1::/80 route sourced locally 14:04:19:BGP(1):2000:0:0:3::2/64 route sourced locally 14:04:19:BGP(1):2000:0:0:4::2/64 route sourced locally 14:04:22:BGP(1):2000:0:0:2::2 computing updates, afi 1, neighbor version 1, table version 6, starting at :: 14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (format) 2000:0:0:2::1/64, next 2000:0:0:2::1, metric 0, path 14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (format) 2000:0:0:2:1::/80, next 2000:0:0:2::1, metric 0, path 14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (prepend, chgflags:0x208) 2000:0:0:3::2/64, next 2000:0:0:2::1, metric 0, path 14:04:22:BGP(1):2000:0:0:2::2 send UPDATE (prepend, chgflags:0x208) 2000:0:0:4::2/64, next 2000:0:0:2::1, metric 0, path

The following is sample output from the debug bgp ipv6 updates command filtered through the prefix list named sales: Router# debug bgp ipv6 updates prefix-list sales 00:18:26:BGP(1):2000:8493:1::2 send UPDATE (prepend, chgflags:0x208) 7878:7878::/64, next 2001:0DB8::36C, metric 0, path


debug bgp ipv6 updates Field Descriptions

Field

Description

BGP(1):

BGP debugging for address family index (afi) 1.

afi

Address family index.

neighbor version

Version of the BGP table on the neighbor from which the update was received.


DB-180

May 2008


Table 38

Related Commands

debug bgp ipv6 updates Field Descriptions (continued)

Field

Description

table version

Version of the BGP table on the router from which you entered the debug bgp ipv6 updates command.

starting at

Starting at the network layer reachability information (NLRI). BGP sends routing update messages containing NLRI to describe a route and how to get there. In this context, an NLRI is a prefix. A BGP update message carries one or more NLRI prefixes and the attributes of a route for the NLRI prefixes; the route attributes include a BGP next hop gateway address, community values, and other information.

route sourced locally

Indicates that a route is sourced locally and that updates are not sent for the route.

send UPDATE (format)

Indicates that an update message for a reachable network should be formatted. Addresses include prefix and next hop.

send UPDATE (prepend, chgflags:0x208)

Indicates that an update message about a path to a BGP peer should be written.

Command

Description

debug bgp ipv6 dampening

Displays debugging messages for IPv6 BGP dampening packets.


DB-181

Debug Commands debug bgp nsap dampening

debug bgp nsap dampening To display debug messages for Border Gateway Protocol (BGP) network service access point (NSAP) prefix address dampening, use the debug bgp nsap dampening command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bgp nsap dampening [filter-list access-list-number] no debug bgp nsap dampening [filter-list access-list-number]

Syntax Description

filter-list access-list-number

Command Default

Debugging for BGP NSAP dampening events is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)T


12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX


Usage Guidelines

Note

Examples

(Optional) Displays debug messages for BGP NSAP dampening events that match the access list. The acceptable access list number range is from 1 to 199.

The debug bgp nsap dampening command is similar to the debug ip bgp dampening command, except that it is specific to the NSAP address family.

By default, the network server sends the output from debug commands and system error messages to the console. To redirect debug output, use the logging command options within global configuration mode. Destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server.

The following example shows output for the debug bgp nsap dampening command: Router# debug bgp nsap dampening 16:21:34: BGP(4): Dampening route-map modified.

Only one line of output is displayed unless the bgp dampening command is configured with a route map in NSAP address family configuration mode. The following example shows output for the debug bgp nsap dampening command when a route map is configured:


DB-182

May 2008

Debug Commands debug bgp nsap dampening

20:07:19: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15 reuse/suppress 750/2000 20:07:19: BGP(4): flapped 1 times since 00:00:00. New penalty is 1000 20:08:59: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15 reuse/suppress 750/2000 20:08:59: BGP(4): flapped 2 times since 00:01:39. New penalty is 1928 20:10:04: BGP(4): charge penalty for 49.0404 path 65202 65404 with halflife-time 15 reuse/suppress 750/2000 20:10:04: BGP(4): flapped 3 times since 00:02:44. New penalty is 2839 20:10:48: BGP(4): suppress 49.0404 path 65202 65404 for 00:28:10 (penalty 2752) 20:10:48: halflife-time 15, reuse/suppress 750/2000


debug bgp nsap dampening Field Descriptions

Field

Description

penalty

Numerical value of 1000 assigned to a route by a router configured for route dampening in another autonomous system each time a route flaps. Penalties are cumulative. The penalty for the route is stored in the BGP routing table until the penalty exceeds the suppress limit. If the penalty exceeds the suppress limit, the route state changes from history to damp.

halflife-time

Amount by which the penalty is decreased after the route is assigned a penalty. The half-life-time value is half of the half-life period (which is 15 minutes by default). Penalty reduction occurs every 5 seconds.

flapped

Number of times a route is available, then unavailable, or vice versa.

reuse

The limit by which a route is unsuppressed. If the penalty for a flapping route decreases and falls below this reuse limit, the route is unsuppressed. That is, the route is added back to the BGP table and once again used for forwarding. The default reuse limit is 750. Unsuppressing of routes occurs at 10-second increments. Every 10 seconds, the router learns which routes are now unsuppressed and advertises them throughout the network.

suppress

Limit by which a route is suppressed. If the penalty exceeds this limit, the route is suppressed. The default value is 2000.

maximum suppress limit Maximum amount of time a route is suppressed. The default value is (not shown in sample output) four times the half-life period. damp state State in which the route has flapped so often that the router will not (not shown in sample output) advertise this route to BGP neighbors.

Related Commands

Command

Description

debug bgp nsap

Displays debug messages for BGP NSAP packets.

debug bgp nsap updates

Displays debug messages for BGP NSAP update events.


DB-183

Debug Commands debug bgp nsap updates

debug bgp nsap updates To display debug messages for Border Gateway Protocol (BGP) network service access point (NSAP) prefix address update packets, use the debug bgp nsap updates command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bgp nsap updates [ip-address] [in | out] [filter-set clns-filter-set-name] no debug bgp nsap updates [ip-address] [in | out] [filter-set clns-filter-set-name]

Syntax Description

ip-address

(Optional) The IP address of a BGP neighbor.

in

(Optional) Indicates inbound updates.

out

(Optional) Indicates outbound updates.

filter-set clns-filter-set-name

(Optional) Name of a Connectionless Network Service (CLNS) filter set.

Command Default

Debugging for BGP NSAP prefix update packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug bgp nsap updates command is similar to the debug ip bgp updates command, except that it is specific to the NSAP address family. Use the ip-address argument to display the BGP update debug messages for a specific BGP neighbor. Use the clns-filter-set-name argument to display the BGP update debug messages for a specific NSAP prefix.

Note

Examples


The following example shows output for the debug bgp nsap updates command: Router# debug bgp nsap updates


DB-184

May 2008

Debug Commands debug bgp nsap updates

02:13:45: BGP(4): 10.0.3.4 send 49.0303.3333.3333.3333.3333.00, 02:13:45: BGP(4): 10.0.3.4 send 49.0303.3333.3333.3333.3333.00, 02:13:45: BGP(4): 10.0.3.4 send 49.0303.3333.3333.3333.3333.00, 02:13:45: BGP(4): 10.0.2.2 send 49.0303.3333.3333.3333.3333.00,

UPDATE metric UPDATE metric UPDATE metric UPDATE metric

(format) 49.0101, next 0, path 65202 65101 (format) 49.0202, next 0, path 65202 (format) 49.0303, next 0, path (format) 49.0404, next 0, path 65404


Related Commands

debug bgp nsap updates Field Descriptions

Field

Description

BGP(4):

BGP debug for address family index (afi) 4.

route sourced locally (not shown in display)

Indicates that a route is sourced locally and that updates are not sent for the route.

send UPDATE (format)

Indicates that an update message for a reachable network should be formatted. Addresses include NSAP prefix and next hop.

rcv UPDATE (not shown in display)

Indicates that an update message about a path to a BGP peer has been received. Addresses include NSAP prefix.

Command

Description

debug bgp nsap

Displays debug messages for BGP NSAP packets.

debug bgp nsap dampening

Displays debug messages for BGP NSAP prefix dampening events.


DB-185

Debug Commands debug bgp nsap

debug bgp nsap To enable the display of Border Gateway Protocol (BGP) debugging information specific to the network service access point (NSAP) address family, use the debug bgp nsap command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bgp nsap no debug bgp nsap

Syntax Description


Command Default

Debugging of BGP NSAP address-family code is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

Note

Examples

The debug bgp nsap command is similar to the debug ip bgp command, except that it is specific to the NSAP address family.


The following example shows output for the debug bgp nsap command. The BGP(4) identifies that BGP version 4 is operational. Router# debug bgp nsap 00:46:46: BGP(4): 00:46:46: BGP(4): 00:46:46: BGP(4): 00:46:46: BGP(4): eBGP-neighbor 00:46:46: BGP(4): eBGP-neighbor 00:46:59: BGP(4):

removing removing removing 10.1.2.1

CLNS route to CLNS route to CLNS route to removing CLNS

49.0101 49.0303 49.0404 route 49.0101.1111.1111.1111.1111.00 to

10.2.4.4 removing CLNS route 49.0303.4444.4444.4444.4444.00 to Applying map to find origin for prefix 49.0202.2222


DB-186

May 2008

Debug Commands debug bgp nsap

00:46:59: BGP(4): Applying map to find origin for prefix 49.0202.3333

Related Commands

Command

Description

debug bgp nsap dampening

Displays debug messages for BGP NSAP prefix dampening events.

debug bgp nsap updates

Displays debug messages for BGP NSAP prefix update packets.


DB-187

Debug Commands debug bgp vpnv6 unicast

debug bgp vpnv6 unicast To display Border Gateway Protocol (BGP) virtual private network (VPN) debugging output, use the debug bgp vpnv6 unicast command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bgp vpnv6 unicast no debug bgp vpnv6

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRB


12.2(33)SXH


12.2SX


Usage Guidelines

Note

Examples

Use the debug bgp vpnv6 unicast command to help troubleshoot the BGP VPN.

By default, the network server sends the output from debug commands and system error messages to the console. To redirect debugging output, use the logging command options within global configuration mode. Destinations are the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server. For complete information on debug commands and redirecting debugging output, refer to the Cisco IOS Debug Command Reference, Release 12.4.

The following example enables BGP debugging output for IPv6 VPN instances: Router# debug bgp vpnv6 unicast


DB-188

May 2008

Debug Commands debug bri-interface

debug bri-interface To display debugging information on ISDN BRI routing activity, use the debug bri-interface command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bri-interface no debug bri-interface

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug bri-interface command indicates whether the ISDN code is enabling and disabling the B channels when attempting an outgoing call. This command is available for the low-end router products that have a multi-BRI network interface module installed.

Caution

Examples

Because the debug bri-interface command generates a substantial amount of output, use it only when traffic on the IP network is low, so other activity on the system is not adversely affected.

The following is sample output from the debug bri-interface command: Router# debug bri-interface BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI: BRI:

write_sid: wrote 1B for subunit 0, slot 1. write_sid: wrote 15 for subunit 0, slot 1. write_sid: wrote 17 for subunit 0, slot 1. write_sid: wrote 6 for subunit 0, slot 1. write_sid: wrote 8 for subunit 0, slot 1. write_sid: wrote 11 for subunit 0, slot 1. write_sid: wrote 13 for subunit 0, slot 1. write_sid: wrote 29 for subunit 0, slot 1. write_sid: wrote 1B for subunit 0, slot 1. write_sid: wrote 15 for subunit 0, slot 1. write_sid: wrote 17 for subunit 0, slot 1. write_sid: wrote 20 for subunit 0, slot 1. Starting Power Up timer for unit = 0. write_sid: wrote 3 for subunit 0, slot 1. Starting T3 timer after expiry of PUP timeout for unit = 0, current state is F4. write_sid: wrote FF for subunit 0, slot 1. Activation for unit = 0, current state is F7. enable channel B1 write_sid: wrote 14 for subunit 0, slot 1.

%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up.!!! BRI: disable channel B1 BRI: write_sid: wrote 15 for subunit 0, slot 1.


DB-189

Debug Commands debug bri-interface

%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to down %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to down

The following line indicates that an internal command was written to the interface controller. The subunit identifies the first interface in the slot. BRI: write_sid: wrote 1B for subunit 0, slot 1.

The following line indicates that the power-up timer was started for the named unit: BRI: Starting Power Up timer for unit = 0.

The following lines indicate that the channel or the protocol on the interface changed state: %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up %LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up.!!! %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to down

The following line indicates that the channel was disabled: BRI: disable channel B1

Lines of output not described are for use by support staff only.

Related Commands

Command

Description

debug isdn event

Displays ISDN events occurring on the user side (on the router) of the ISDN interface.

debug isdn q921

Displays data link-layer (Layer 2) access procedures that are taking place at the router on the D channel (LSPD).

debug isdn q931

Displays information about call setup and teardown of ISDN network connections (Layer 3) between the local router (user side) and the network.


DB-190

May 2008

Debug Commands debug bsc event

debug bsc event To display all events occurring in the Binary Synchronous Communications (Bisync) feature, use the debug bsc event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bsc event [number] no debug bsc event [number]

Syntax Description

number

Command Modes

Privileged EXEC

Usage Guidelines

This command traces all interfaces configured with a bsc protocol-group number command.

Examples

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

(Optional) Group number.

Router# debug bsc event BSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFile BSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFile BSC: Serial2 POLLEE-FSM inp:E_LineFail old_st:CU_Down new_st:TCU_EOFile 0:04:32: BSC: Serial2 :SDI-rx: 9 bytes BSC: Serial2 POLLEE-FSM inp:E_RxEtx old_st:CU_Down new_st:TCU_EOFile 0:04:32: BSC: Serial2 :SDI-rx: 5 bytes BSC: Serial2 POLLEE-FSM inp:E_RxEnq old_st:CU_Down new_st:TCU_EOFile BSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Down new_st:TCU_InFile BSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Idle new_st:TCU_InFile %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2, changed state to up %LINK-3-UPDOWN: Interface Serial2, changed state to up BSC: Serial2 POLLEE-FSM inp:E_Timeout old_st:CU_Idle new_st:TCU_InFile 0:04:35: BSC: Serial2 :SDI-rx: 9 bytes BSC: Serial2 POLLEE-FSM inp:E_RxEtx old_st:CU_Idle new_st:TCU_InFile 0:04:35: BSC: Serial2 :SDI-rx: 5 bytes BSC: Serial2 POLLEE-FSM inp:E_RxEnq old_st:CU_Idle new_st:TCU_InFile 0:04:35: BSC: Serial2 :NDI-rx: 3 bytes

Related Commands

Command

Description

debug bsc packet

Displays all frames traveling through the Bisync feature.

debug bstun events

Displays BSTUN connection events and status.


DB-191

Debug Commands debug bsc packet

debug bsc packet To display all frames traveling through the Binary Synchronous Communications (Bisync) feature, use the debug bsc packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bsc packet [group number] [buffer-size bytes] no debug bsc packet [group number] [buffer-size bytes]

Syntax Description

group number


buffer-size bytes

(Optional) Number of bytes displayed per packet (defaults to 20).

Defaults

The default number of bytes displayed is 20.

Command Modes

Privileged EXEC

Usage Guidelines

This command traces all interfaces configured with a bsc protocol-group number command.

Examples

The following is sample output from the debug bsc packet command: Router# debug bsc packet 0:23:33: 0:23:33: 0:23:33: 0:23:33: 0:23:33: 0:23:33:

Related Commands

BSC: BSC: BSC: BSC: BSC: BSC:

Serial2 Serial2 Serial2 Serial2 Serial2 Serial2

Command

:NDI-rx :SDI-tx :SDI-rx :SDI-tx :SDI-rx :SDI-tx

: : : : : :

27 bytes 401A400227F5C31140C11D60C8C5D3D3D51D4013 12 bytes 00323237FF3232606040402D 2 bytes 1070 27 bytes 401A400227F5C31140C11D60C8C5D3D3D51D4013 2 bytes 1061 5 bytes 00323237FF

Description

debug bsc event

Displays all events occurring in the Bisync feature.

debug bstun events



DB-192

May 2008

Debug Commands debug bstun events

debug bstun events To display BSTUN connection events and status, use the debug bstun events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bstun events [number] no debug bstun events [number]

Syntax Description

number

Command Modes

Privileged EXEC

Usage Guidelines

When you enable the debug bstun events command, messages showing connection establishment and other overall status messages are displayed.


You can use the debug bstun events command to assist you in determining whether the BSTUN peers are configured correctly and are communicating. For example, if you enable the debug bstun packet command and you do not see any packets, you may want to enable event debugging.

Note

Examples

Also refer to the debug bsc packet and debug bsc event commands. Currently, these two commands support the only protocol working through the BSTUN tunnel. Sometimes frames do not go through the tunnel because they have been discarded at the Bisync protocol level.

The following is sample output from the debug bstun events command of keepalive messages working correctly. If the routers are configured correctly, at least one router will show reply messages. Router# debug bstun events BSTUN: Received Version Reply opcode from (all[2])_172.16.12.2/1976 at 1360 BSTUN: Received Version Request opcode from (all[2])_172.16.12.2/1976 at 1379 BSTUN: Received Version Reply opcode from (all[2])_172.16.12.2/1976 at 1390

Note

In a scenario where there is constantly loaded bidirectional traffic, you might not see keepalive messages because they are sent only when the remote end has been silent for the keepalive period. The following is sample output from the debug bstun events output of an event trace in which the wrong TCP address has been specified for the remote peer. These are non-keepalive related messages. Router# debug bstun events BSTUN: Change state for peer (C1[1])172.16.12.22/1976 (closed->opening) BSTUN: Change state for peer (C1[1])172.16.12.22/1976 (opening->open wait) %BSTUN-6-OPENING: CONN: opening peer (C1[1])172.16.12.22/1976, 3 BSTUN: tcpd sender in wrong state, dropping packet BSTUN: tcpd sender in wrong state, dropping packet BSTUN: tcpd sender in wrong state, dropping packet


DB-193

Debug Commands debug bstun events

Related Commands

Command

Description

debug bsc event

Displays all events occurring in the Bisync feature.

debug bsc packet

Displays all frames traveling through the Bisync feature.

debug bstun packet

Displays packet information on packets traveling through the BSTUN links.


DB-194

May 2008

Debug Commands debug bstun packet

debug bstun packet To display packet information on packets traveling through the BSTUN links, use the debug bstun packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bstun packet [group number] [buffer-size bytes] no debug bstun packet [group number] [buffer-size bytes]

Syntax Description

group number

(Optional) BSTUN group number.

buffer-size bytes

(Optional) Number of bytes displayed per packet (defaults to 20).

Defaults

The default number of bytes displayed is 20.

Command Modes

Privileged EXEC

Examples

The following is sample output from the debug bstun packet command: Router# debug bstun packet BSTUN bsc-local-ack: 0:00:00 Serial2 BSTUN bsc-local-ack: 0:00:00 Serial2 BSTUN bsc-local-ack: 0:00:06 Serial2

Related Commands

SDI: Addr: 40 Data: 02C1C1C1C1C1C1C1C1C1 SDI: Addr: 40 Data: 02C1C1C1C1C1C1C1C1C1 NDI: Addr: 40 Data: 0227F5C31140C11D60C8

Command

Description

debug bstun events



DB-195

Debug Commands debug bundle errors

debug bundle errors To enable the display of information on bundle errors, use the debug bundle errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug bundle errors no debug bundle errors

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command to enable the display of error information for a bundle, such as reports of inconsistent mapping in the bundle.

Related Commands

Command

Description

bump

Configures the bumping rules for a VC class that can be assigned to a VC bundle.

bundle

Creates a bundle or modifies an existing bundle to enter bundle configuration mode.

debug bundle events

Enables display of bundle events when use occurs.


DB-196

May 2008

Debug Commands debug bundle events

debug bundle events To enable display of bundle events when use occurs, use the debug bundle events command in privileged EXEC mode. To disable the display, use the no form of this command. debug bundle events no debug bundle events

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command to enable the display of bundle events, such as occurrences of VC bumping, when bundles were brought up, when they were taken down, and so forth.

Related Commands

Command

Description

debug bstun packet

Enables the display of information on bundle errors.


DB-197

Debug Commands debug call fallback detail

debug call fallback detail To display details of the call fallback, use the debug call fallback detail command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call fallback detail no debug call fallback detail

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(2)XB1


Usage Guidelines

12.2(4)T


12.2(4)T3

This command was implemented on the Cisco 7500 series routers routers.

12.2(11)T


12.2SX


Every time a call request is received, the debug call fallback detail command displays in the command-line interface (CLI) cache lookup and call acceptance/rejection information. Use this command to monitor call requests as they enter the call fallback subsystem. If you have a large amount of calls in your router, enabling this command can cause delays in your routing functions as the debug statistics are constantly compiled and sent to your terminal. Also, debug messages on your terminal may make for difficult CLI configuring.

Examples

The following example depicts a call coming in to 10.1.1.4 with codec g729r8. Because there is no cache entry for this destination, a probe is sent and values are inserted into the cache. A lookup is performed again, entry is found, and a fallback decision is made to admit the call. Router# debug call fallback detail When cache is empty: debug call fallback detail: 2d19h:fb_lookup_cache:10.1.1.4, codec:g729r8 2d19h:fb_lookup_cache:No entry found.


DB-198

May 2008

Debug Commands debug call fallback detail

2d19h:fb_check:no entry exists, enqueueing probe info... 10.1.1.4, codec:g729r8 2d19h:fb_main:Got FB_APP_INQ event 2d19h:fb_main:Dequeued prob info: 10.1.1.4, codec:g729r8 2d19h:fb_lookup_cache:10.1.1.4, codec:g729r8 2d19h:fb_lookup_cache:No entry found. 2d19h:fb_cache_insert:insert:10.1.1.4, codec:g729r8 2d19h:fb_cache_insert:returning entry:10.1.1.4, codec:g729r8 2d19h:fb_initiate_probe:Creating probe... 10.1.1.4, codec:g729r8 2d19h:fb_initiate_probe:Created and started on probe #13, 10.1.1.4, codec:g729r8 2d19h:fb_lookup_cache:10.1.1.4, codec:g729r8 2d19h:fb_lookup_cache:Found entry. 2d19h:fb_check:returned FB_CHECK_TRUE, 10.1.1.4, codec:g729r8 2d19h:fb_main:calling callback function with:TRUE

The following example depicts a call coming in to 10.1.1.4 with codec g729r8. A lookup is performed, entry is found, and a fallback decision is made to admit the call. Router# debug call fallback detail When cache is full: 2d19h:fb_lookup_cache:10.1.1.4, codec:g729r8 2d19h:fb_lookup_cache:Found entry. 2d19h:fb_check:returned FB_CHECK_TRUE, 10.1.1.4, codec:g729r8 2d19h:fb_main:calling callback function with:TRUE


DB-199

Debug Commands debug call fallback probe

debug call fallback probe To display details of the call fallback probes, use the debug call fallback probe command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call fallback probe no debug call fallback probe

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(2)XA

The call fallback and call fallback reject-cause-code commands were introduced.

12.2(2)XB1


12.2(4)T


12.2(4)T3


12.2SX


Usage Guidelines

Every time a probe is received, the debug call fallback probe command displays in the command-line interface (CLI) network traffic information collected by the probe. Use this command to monitor the network traffic information the probes carry as they enter the call fallback subsystem and log cache entries. If you have frequent return of probes to your router, enabling this command can cause delays in your routing functions as the debug statistics are constantly compiled and sent to your terminal. Also, debug messages on your terminal may make for difficult CLI configuring.

Examples

The following example depicts a call coming in to 10.1.1.4 and codec type g729r8. Because there is no cache entry for this IP address, a g729r8 probe is initiated. The probe consists of 20 packet returns with an average delay of 43 milliseconds. The “jitter out” is jitter from source to destination router and “jitter in” is jitter from destination to source router. The delay, loss, and Calculated Planning Impairment Factor (ICPIF) values following g113_calc_icpif are the instantaneous values, whereas those values following “New smoothed values” are the values after applying the smoothing with weight 65. Router# debug call fallback probe 2d19h:fb_initiate_probe:Probe payload is 32


DB-200

May 2008

Debug Commands debug call fallback probe

2d19h:fb_main:NumOfRTT=20, RTTSum=120, loss=0, delay=43, jitter in=0, jitter out=0-> 10.1.1.4, codec:g729r8 2d19h:g113_calc_icpif(delay (w/codec delay)=43, loss=0, expect_factor=10) Icpif=0 2d19h:fb_main:Probe timer expired, 10.1.1.4, codec:g729r8 2d19h:fb_main:NumOfRTT=20, RTTSum=120, loss=0, delay=43, jitter in=0, jitter out=0-> 10.1.1.4, codec:g729r8 2d19h:g113_calc_icpif(delay (w/codec delay)=43, loss=0, expect_factor=10) Icpif=0 2d19h:fb_main:New smoothed values:inst_weight=65, ICPIF=0, Delay=43, Loss=0 -> 10.1.1.4, codec:g729r8


DB-201

Debug Commands debug call filter detail

debug call filter detail To display details of the debug trace inside the generic call filter module (GCFM), use the debug call filter detail command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call filter detail no debug call filter detail

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Examples

The following sample output from the debug call filter detail command shows the detailed activity of the GCFM, which is the internal module that controls the debug filtering. Router# debug call filter detail 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: vs the 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h:

gcfm_call_get_hash_address: hashtable index = 345 gcfm_call_search_hash:no found gcfm_init_call_record: gcfm_init_percall_matchlist: === list 1: service_state=2, callp's: 0 gcfm_call_get_hash_address: hashtable index = 345 gcfm_call_enlist: count before this enlist 0 on 624D6000 gcfm_call_enlist: tail is empty guid=C2E4C789-214A-11D4-804C-000A8A389BA8 gcfm_call_get_hash_address: hashtable index = 345 gcfm_call_search_hash: search requested guid=C2E4C789-214A-11D4-804C-000A8A389BA8 entry guid=C2E4C789-214A-11D4-804C-000A8A389BA8 gcfm_call_search_hash: found gcfm_update_percall_condlist_context: gcfm_update_percall_condlist_context: check cond = 2 gcfm_copy_match_cond: gcfm_update_cond_through_matchlist: gcfm_check_percond_with_matchlist: check match-list 1 gcfm_matchlist_percond_check: gcfm_matchlist_percond_check: check cond=2 gcfm_matchlist_percond_check: compare 42300 to configured 42300 gcfm_check_cond_tel_number: gcfm_check_cond_tel_number: matched


DB-202

May 2008

Debug Commands debug call filter detail

5d18h: gcfm_matchlist_percond_check: checked result is 1 5d18h: gcfm_is_bitfield_identical: 5d18h: gcfm_update_cond_through_matchlist: service=1, percallmatchlist tag=1,current_status = 1, service_filter=0 5d18h: gcfm_percall_notify_condition: not linked call record


debug call filter detail Field Descriptions

Field

Description

5d18h: gcfm_init_percall_matchlist:

Shows that the filtering has been initiated.

5d18h: gcfm_call_enlist: tail is empty Shows the global unique identifier (GUID) for the call. guid=C2E4C789-214A-11D4-804C-00 0A8A389BA8 5d18h: Shows which match list is being checked. gcfm_check_percond_with_matchlis t: check match-list 1

Related Commands

5d18h: gcfm_matchlist_percond_check: checked result is 1

Shows that the call matched conditions in match list 1.

Command

Description

debug call filter inout

Displays the debug trace inside the GCFM.

debug condition match-list

Runs a filtered debug on a voice call.

show call filter components

Displays the components used for filtering calls.


DB-203

Debug Commands debug call filter inout

debug call filter inout To display the debug trace inside the generic call filter module (GCFM), use the debug call filter inout command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call filter inout no debug call filter inout

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Examples

The following sample output from the debug call filter inout command shows the incoming and outgoing activity of the GCFM, which is the internal module that controls the debug filtering. Router# debug call filter inout 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h: 5d18h:

gcfm_generate_guid: component ISDN gets guid gcfm_percall_register: component ISDN gcfm_percall_register: component ISDN return selected=0 gcfm_percall_notify_condition: component ISDN for sync=1 gcfm_percall_notify_condition: component ISDN successfully selected = 0 gcfm_check_percall_status: component TGRM gcfm_check_percall_status: component TGRM return selected=0 gcfm_check_percall_status: component TGRM gcfm_check_percall_status: component TGRM return selected=0 gcfm_percall_register: component VTSP gcfm_percall_register: component VTSP for return selected value 0 gcfm_percall_notify_condition: component VTSP for sync=1 gcfm_percall_notify_condition: component VTSP successfully selected = 0 gcfm_percall_register: component CCAPI gcfm_percall_register: component CCAPI for return selected value 0 gcfm_check_percall_status: component NUMBER-TRANSLATION gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=0 gcfm_percall_register: component VOICE-IVR-V2 gcfm_percall_register: component VOICE-IVR-V2 for return selected value 0 gcfm_check_percall_status: component NUMBER-TRANSLATION gcfm_check_percall_status: component NUMBER-TRANSLATION gcfm_check_percall_status: component DIAL-PEER gcfm_check_percall_status: component DIAL-PEER return selected=0


DB-204

May 2008


5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component DIAL-PEER 5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=0 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component DIAL-PEER 5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=0 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component DIAL-PEER 5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=0 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component DIAL-PEER 5d18h: gcfm_check_percall_status: component DIAL-PEER return selected=0 5d18h: gcfm_check_percall_status: component DIAL-PEER 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_percall_register: component CCAPI 5d18h: gcfm_percall_register: component CCAPI for return selected value 0 5d18h: gcfm_percall_register: component VOICE-IVR-V2 5d18h: gcfm_percall_register: component VOICE-IVR-V2 for return selected value 0 5d18h: gcfm_percall_notify_condition: component VOICE-IVR-V2 for sync=1 5d18h: gcfm_percall_notify_condition: component VOICERouter#IVR-V2 successfully selected = 1 5d18h: gcfm_percall_register: component H323 5d18h: gcfm_percall_register: component H323 for return selected value 1 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=1 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=1 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=1 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=1 5d18h: gcfm_clear_condition: component VOICE-IVR-V2 5d18h: gcfm_clear_condition: component VOICE-IVR-V2 successfully 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=0 5d18h: gcfm_percall_deregister: component CCAPI 5d18h: gcfm_percall_deregister: component CCAPI successfully 5d18h: gcfm_percall_deregister: component H323 5d18h: gcfm_percall_deregister: component H323 successfully 5d18h: gcfm_percall_deregister: component ISDN 5d18h: gcfm_percall_deregister: component ISDN successfully 5d18h: gcfm_percall_deregister: component VOICE-IVR-V2 5d18h: gcfm_percall_deregister: component VOICE-IVR-V2 successfully 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION 5d18h: gcfm_check_percall_status: component NUMBER-TRANSLATION return selected=0 5d18h: gcfm_percall_deregister: component CCAPI 5d18h: gcfm_percall_deregister: component CCAPI successfully 5d18h: gcfm_percall_deregister: component VTSP 5d18h: gcfm_percall_deregister: component VTSP successfully 5d18h: gcfm_percall_deregister: component VOICE-IVR-V2 5d18h: gcfm_terminate_track_guid: component VOICE-IVR-V2 terminate, success 5d18h: gcfm_percall_deregister: component VOICE-IVR-V2 successfully


debug call filter inout Field Descriptions

Field

Description

gcfm_generate_guid:

Shows that a GUID has been generated.

gcfm_percall_register:

Shows components that have been registered for the call.

gcfm_percall_notify_condition:

Shows that a component has been notified of the call.


DB-205


Table 42

Related Commands

debug call filter inout Field Descriptions (continued)

Field

Description

gcfm_check_percall_status:

Shows the status of a component of the call.

gcfm_percall_register:

Shows that a component has been registered.

gcfm_clear_condition:

Shows that a condition is cleared for a component.

gcfm_percall_deregister:

Shows that a component has been deregistered.

gcfm_terminate_track_guid:

Shows that the router is no longer tracking the GUID.

Command

Description

debug call filter detail

Displays the details of the debug trace inside the GCFM.

debug condition match-list

Runs a filtered debug on a voice call.

show call filter components

Displays the components used for filtering calls.


DB-206

May 2008

Debug Commands debug call rsvp-sync events

debug call rsvp-sync events To display events that occur during Resource Reservation Protocol (RSVP) setup, use the debug call rsvp-sync events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call rsvp-sync events no debug call rsvp-sync events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI1


12.1(5)T


12.2(2)XB1

This command was implemented on the Cisco AS5850.

12.2(11)T

Support for the command was implemented in Cisco AS5850 images.

12.2(33)SRA


12.2SX


Usage Guidelines

It is highly recommended that you log the output from the debug call rsvp-sync events command to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following example shows a portion of sample output for a call initiating RSVP when using the debug call rsvp-sync events command: 00:03:25:

Parameters: localip: 10.19.101.117 :localport: 16660

00:03:25:

Parameters: remoteip: 10.19.101.116 :remoteport: 17568

00:03:25: QoS Primitive Event for Call id 0x1 : QoS Listen 00:03:25: Lookup to be done on hashkey 0x1 in hash table 0x61FC2498 00:03:25: Hashed entry 0x1 in call table 0x61FC2498 00:03:25: Entry Not found


DB-207

Debug Commands debug call rsvp-sync events

00:03:25:

Parameters: localip: 10.19.101.117

00:03:25:

remoteip: 10.19.101.116

00:03:25:

QoSpcb : 0x61FC34D8

00:03:25: Response Status : 0 Starting timer for call with CallId 0x1 for 10000 secs 00:03:25:

Handling QoS Primitive QoS Listen

00:03:25:

Establishing RSVP RESV state : rsvp_request_reservation()

00:03:25:

For streams from 10.19.101.116:17568 to 10.19.101.117:16660

00:03:25:

RSVP Confirmation required

00:03:25: QoS Primitive Event for Call id 0x1 : QoS Resv 00:03:25: Lookup to be done on hashkey 0x1 in hash table 0x61FC2498 00:03:25: Hashed entry 0x1 in call table 0x61FC2498 00:03:25:

Initiating RVSP PATH messages to be Sent : reg_invoke_rsvp_advertise_sender()

00:03:25:

Advertizing for streams to 10.19.101.116:17568 from 10.19.101.117:16660

00:03:25:

RESV notification event received is : 2

00:03:25: Received RESVCONFIRM 00:03:25: RESV CONFIRM message received from 10.19.101.116 for RESV setup from 10.19.101.117 00:03:25:

RESV event received is : 0

00:03:25: RESV message received from 10.19.101.116:17568 for streams from 10.19.101.117:16660 00:03:25: RESERVATIONS ESTABLISHED : CallId: 1Stop timer and notify Session Protocol of Success (ie. if notification requested) 00:03:25:

Related Commands

Invoking spQoSresvCallback with Success

Command

Description

call rsvp-sync

Enables synchronization between RSVP and the H.323 voice signaling protocol.

call rsvp-sync resv-timer

Sets the timer for RSVP reservation setup.

debug call rsvp-sync func-trace

Displays messages about the software functions called by RSVP synchronization.

show call rsvp-sync conf

Displays the RSVP synchronization configuration.

show call rsvp-sync stats

Displays statistics for calls that attempted RSVP reservation.


DB-208

May 2008

Debug Commands debug call rsvp-sync func-trace

debug call rsvp-sync func-trace To display messages about software functions called by Resource Reservation Protocol (RSVP), use the debug call rsvp-sync func-trace command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call rsvp-sync func-trace no debug call rsvp-sync func-trace

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI1


12.1(5)T


12.2(2)XB1


12.2(33)SRA


12.2SX


Usage Guidelines

It is highly recommended that you log the output from the debug call rsvp-sync func-trace command to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following example shows a portion of sample output for a call initiating RSVP when using the debug call rsvp-sync func-trace command in conjunction with the debug call rsvp-sync events command: 00:03:41: Entering Function QoS_Listen 00:03:41: Parameters:localip:10.10.101.116 :localport:17568 00:03:41:remoteip:10.10.101.117 :remoteport:0 00:03:41: Entering Function qos_dequeue_event 00:03:41: Entering Function process_queue_event 00:03:41: QoS Primitive Event for Call id 0x2 :QoS Listen 00:03:41: Entering Function get_pcb


DB-209

Debug Commands debug call rsvp-sync func-trace

00:03:41: Entering Function hash_tbl_lookup 00:03:41:Lookup to be done on hashkey 0x2 in hash table 0x61FAECD8 00:03:41: Entering Function hash_func 00:03:41:Hashed entry 0x2 in call table 0x61FAECD8 00:03:41:Entry Not found 00:03:41: Entering Function qos_dequeue_pcb 00:03:41: Entering Function qos_initialize_pcb 00:03:41: Parameters:localip:10.10.101.116 00:03:41:

remoteip:10.10.101.117

00:03:41: QoSpcb :0x61FAFD18 00:03:41: Response Status :0 00:03:41: Entering Function hash_tbl_insert_entry 00:03:41: Entering Function hash_func 00:03:41: Handling QoS Primitive QoS Listen 00:03:41: Entering Function qos_dequeue_hash_port_entry 00:03:41: Entering Function qos_port_tbl_insert_entry 00:03:41: Entering Function hash_func 00:03:41: Doing RSVP Listen :rsvp_add_ip_listen_api()

Related Commands

Command

Description

call rsvp-sync

Enables synchronization between RSVP and the H.323 voice signaling protocol.

call rsvp-sync resv-timer

Sets the timer for RSVP reservation setup.

debug call rsvp-sync events

Displays the events that occur during RSVP synchronization.

show call rsvp-sync conf

Displays the RSVP synchronization configuration.

show call rsvp-sync stats

Displays statistics for calls that attempted RSVP reservation.


DB-210

May 2008

Debug Commands debug call threshold

debug call threshold To see details of the trigger actions, use the debug call threshold command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call threshold module no debug call threshold

Syntax Description

module

The module argument can be one of the following: •

core—Traces the resource information.

•

detail—Traces for detail information.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XA


12.2(4)T

The command was integrated into Cisco IOS Release 12.2(4)T. Support for the Cisco AS5300, Cisco AS5350, and Cisco AS5400 is not included in this release.

Examples

12.2(2)XB1


12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T and implemented on Cisco 7200 series routers.

12.2(11)T

Support for this command was implemented on Cisco AS5850, Cisco AS5800, Cisco AS5300, Cisco AS5350, and Cisco AS5400 series images.

12.2SX


The following is sample output from the debug call threshold core command: Router# debug call threshold core RSCCAC Core info debugging is on

The following is sample output from the debug call threshold detail command: Router# debug call threshold detail All RSCCAC info debugging is on


DB-211

Debug Commands debug call treatment action

debug call treatment action To debug the call treatment actions, use the debug call treatment action command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call treatment action no debug call treatment action

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XA


12.2(4)T

The command was integrated into Cisco IOS Release 12.2(4)T.

Examples

12.2(2)XB1


12.2(8)T


12.2(11)T

Support for this command was implemented on Cisco AS5850, Cisco AS5800, Cisco AS5300, Cisco AS5350, and Cisco AS5400 series images.

12.2SX


Debug actions are performed on calls by call treatment. The following sample output shows that call treatment is turned on: Router# debug call treatment action Call treatment action debugging is on


DB-212

May 2008

Debug Commands debug callback

debug callback To display callback events when the router is using a modem and a chat script to call back on a terminal line, use the debug callback command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug callback no debug callback

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command is useful for debugging chat scripts on PPP and AppleTalk Remote Access Protocol (ARAP) lines that use callback mechanisms. The output provided by the debug callback command shows you how the call is progressing when used with the debug ppp or debug arap commands.

Examples

The following is sample output from the debug callback command: Router# debug callback TTY7 Callback process initiated, user: exec_test dialstring 123456 TTY7 Callback forced wait = 4 seconds TTY7 Exec Callback Successful - await exec/autoselect pickup TTY7: Callback in effect

Related Commands

Command

Description

debug cable env

Displays ARAP events.

debug ppp



DB-213

Debug Commands debug call-mgmt

debug call-mgmt To display debugging information for call accounting, including modem and time slot usage, for active and recent calls, use the debug call-mgmt command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug call-mgmt no debug call-mgmt

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1


12.2(33)SRA


12.2SX


Examples

The following is sample output after the debug call-mgmt command has been enabled: Router# debug call-mgmt Call Management debugging is on Router# Dec 26 13:57:27.710: msg_to_calls_mgmt: msg type CPM_NEW_CALL_CSM_CONNECT received Dec 26 13:57:27.714: In actv_c_proc_message, access type CPM_INSERT_NEW_CALL, call type CPM_ISDN_ANALOG: CSM completed connecting a new modem call . . . Dec 26 13:57:45.906: msg_to_calls_mgmt: msg type CPM_NEW_CALL_ISDN_CONNECT received Dec 26 13:57:45.906: In actv_c_proc_message, access type CPM_INSERT_NEW_CALL, call type CPM_ISDN_ANALOG: Added a new ISDN analog call to the active-calls list CC-Slot#7, DSX1-Ctrlr#17, DS0-Timeslot#1 Mdm-Slot#1, Mdm-Port#3, TTY#219 . . . Dec 26 13:58:25.682: Call mgmt per minute statistics: active list length: 1


DB-214

May 2008


Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec

history list length: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.682: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686: 26 13:58:25.686:

3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0

timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots timeslots

active active active active active active active active active active active active active active active active active active active active active active active active active active active active

at at at at at at at at at at at at at at at at at at at at at at at at at at at at

slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot

7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7, 7,

ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr ctrlr

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

Router# clear int as1/03 Dec 26 13:58:26.538: msg_to_calls_mgmt: msg type CPM_VOICE_CALL_REJ_NO_MOD_AVAIL received Dec 26 13:58:26.538: In actv_c_proc_message, access type CPM_REMOVE_DISC_CALL, call type CPM_ISDN_ANALOG: Removed a disconnected ISDN analog call CC-Slot#7, DSX1-Ctrlr#17, DS0-Timeslot#1 Dec 26 13:58:26.538: Mdm-Slot#1, Mdm-Port#3, TTY#219


debug call-mgmt Field Descriptions

Field

Description

CPM_NEW_CALL_CSM_CONNECT

Indicates the arrival of a new call.

access type CPM_INSERT_NEW_CALL,

Indicates that the new call is an analog ISDN B channel call (either a voice call or a call over an analog modem), rather than a digital (V.110) call.

call type CPM_ISDN_ANALOG: CC-Slot#7, DSX1-Ctrlr#17, DS0-Timeslot#1 Mdm-Slot#1, Mdm-Port#3, TTY#219

Indicates that the call is connected via the B channel on Serial7/17:1 to the asynchronous modem resource 1/03 (interface async1/03, also known as line tty219).

Dec 26 13:58:25.682: Call mgmt per minute Displays periodic statistics that give the allocation state of each DSX1 interface present in the system, as well as statistics: the number of current (active) and recent (history) calls. active list length: 1 history list length: 3


DB-215


Table 43

debug call-mgmt Field Descriptions (continued)

Field

Description

Dec 26 13:58:26.538: msg_to_calls_mgmt: Indicates that the analog ISDN B channel call has been disassociated from a modem. msg type CPM_VOICE_CALL_REJ_NO_MOD_ AVAIL received access type CPM_REMOVE_DISC_CALL,

Indicates that the analog ISDN B channel call has been disconnected.

call type CPM_ISDN_ANALOG: Removed a disconnected ISDN analog call CC-Slot#7, DSX1-Ctrlr#17, DS0-Timeslot#1 Dec 26 13:58:26.538: Mdm-Slot#1, Mdm-Port#3, TTY#219

Indicates that the call has been disconnected via the B channel on Serial7/17:1 to the asynchronous modem resource 1/03 (interface async1/03, also known as line tty219).


DB-216

May 2008

Debug Commands debug capf-server

debug capf-server To collect debug information about the CAPF server, use the debug capf-server command in privileged EXEC mode. To disable collection of debug information, use the no form of this command. debug capf-server {all | error | events | messages} no debug capf-server

Syntax Description

all

Collect all CAPF information available.

error

Collect only information about CAPF errors.

events

Collect only information about CAPF status events.

messages

Collect only CAPF system messages.

Command Default

Collection of CAPF debug information is disabled.

Command Modes

Privileged EXEC

Command History

Cisco IOS Release

Modification

12.4(4)XC


12.4(9)T


12.2SX


Usage Guidelines

This command is used with Cisco Unified CallManager Express phone authentication.

Examples

The following example shows debug messages for the CAPF server. Router# debug capf-server all 001891: .Jul 21 18:17:07.014: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000E325C9A43 IP:10.10.10.194 So cket:3 DeviceType:Phone has unregistered normally. 001892: .Jul 21 18:17:20.495: New Connection from phone, socket 1 001893: .Jul 21 18:17:20.495: Created New Handshake Process 001894: .Jul 21 18:17:20.499: SSL Handshake Error -6983 001895: .Jul 21 18:17:21.499: SSL Handshake Error -6983 001896: .Jul 21 18:17:22.555: SSL Handshake Successful 001897: .Jul 21 18:17:22.555: ephone_capf_send_auth_req: 001898: .Jul 21 18:17:22.555: ephone_capf_ssl_write: 12 bytes 001899: .Jul 21 18:17:22.711: ephone_capf_ssl_read: Read 35 bytes 001900: .Jul 21 18:17:22.711: ephone_capf_handle_phone_msg: msgtype 2 001901: .Jul 21 18:17:22.711: ephone_capf_process_auth_res_msg: SEP000E325C9A43 AuthMode 2 001902: .Jul 21 18:17:22.711: ephone_capf_send_delete_cert_req_msg: SEP000E325C9A43


DB-217

Debug Commands debug capf-server

001903: .Jul 21 18:17:22.711: ephone_capf_ssl_write: 8 bytes 001904: .Jul 21 18:17:23.891: ephone_capf_ssl_read: Read 12 bytes 001905: .Jul 21 18:17:23.891: ephone_capf_handle_phone_msg: msgtype 14 001906: .Jul 21 18:17:23.891: certificate delete successful for SEP000E325C9A43 001907: .Jul 21 18:17:24.695: ephone_capf_release_session: SEP000E325C9A43 001908: .Jul 21 18:17:24.695: ephone_capf_send_end_session_msg: SEP000E325C9A43 001909: .Jul 21 18:17:24.695: ephone_capf_ssl_write: 12 bytes 001910: .Jul 21 18:17:25.095: %IPPHONE-6-REG_ALARM: 22: Name=SEP000E325C9A43 Load=7.2(2.0) Last=Rese t-Reset 001911: .Jul 21 18:17:25.099: %IPPHONE-6-REGISTER: ephone-1:SEP000E325C9A43 IP:10.10.10.194 Socket:2 De viceType:Phone has registered. 001912: .Jul 21 18:18:05.171: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000E325C9A43 IP:1.1.1.127 So cket:2 DeviceType:Phone has unregistered normally. 001913: .Jul 21 18:18:18.288: New Connection from phone, socket 1 001914: .Jul 21 18:18:18.288: Created New Handshake Process 001915: .Jul 21 18:18:18.292: SSL Handshake Error -6983 001916: .Jul 21 18:18:19.292: SSL Handshake Error -6983 001917: .Jul 21 18:18:20.348: SSL Handshake Successful 001918: .Jul 21 18:18:20.348: ephone_capf_send_auth_req: 001919: .Jul 21 18:18:20.348: ephone_capf_ssl_write: 12 bytes^Z 001920: 001921: 001922: 001923: 1024 001924: 001925: 001926: 001927: 0sh 001928:

.Jul .Jul .Jul .Jul

21 21 21 21

18:18:20.492: 18:18:20.492: 18:18:20.492: 18:18:20.492:

ephone_capf_ssl_read: Read 35 bytes ephone_capf_handle_phone_msg: msgtype 2 ephone_capf_process_auth_res_msg: SEP000E325C9A43 AuthMode 2 ephone_capf_send_PhKeyGenReq_msg: SEP000E325C9A43 KeySize

.Jul .Jul .Jul .Jul

21 21 21 21

18:18:20.492: 18:18:20.540: 18:18:20.540: 18:18:20.540:

ephone_capf_ssl_write: 13 bytes ephone_capf_ssl_read: Read 8 bytes ephone_capf_handle_phone_msg: msgtype 17 ephone_capf_process_req_in_progress: SEP000E325C9A43 delay

.Jul 21 18:18:21.924: %SYS-5-CONFIG_I: Configured from console by user1 on console


DB-218

May 2008

Debug Commands debug cas

debug cas To debug channel-associated signaling (CAS) messages and to debug the establishment of a time-division multiplexing (TDM) connection between a DS0 and a digital modem, use the debug cas command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cas slot slot number port port number no debug cas slot slot number port port number

Syntax Description

slot slot number

Slot and slot number. Valid values are 0 and 1.

port port number

Port and port number. Valid values are 0 and 1.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)T

This command was introduced for the Cisco AS5200 and AS5300 platforms.

12.2(2)T

This command was integrated into Cisco IOS Release 12.2(2)T and support was added for the Cisco 2600 series and Cisco 3600 series platforms.

12.3(1)

This command was integrated into Cisco IOS Release 12.3(1) and support was added for the Cisco 2600 XM series, Cisco 2691, and Cisco 3700 series platforms.

12.3(4)T


12.2(33)SRA


12.2SX


Usage Guidelines

When the NM-xCE1T1PRI network module is used with an NM-xDM and a DS0-group is configured under the controller, you can use the debug cas command to debug CAS signaling messages and the establishment of a TDM connection between a DS0 and a digital modem. Use the debug cas command to identify and troubleshoot call connection problems on a T1/E1 interface. With this command, you can trace the complete sequence of incoming and outgoing calls.

Examples

The following shows an example session to enable debugging CAS and generate troubleshooting output: Router# show debug Router# debug cas slot 1 port 0 CAS debugging is on Router#


DB-219


debug-cas is on at slot(1) dsx1(0) Router# show debug CAS debugging is on

The following example shows output for the first outgoing call: Router# p 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: *Mar 2 00:17:45: dsx1_alloc_cas_channel: channel 0 dsx1_timeslot 1(0/0): TX SEIZURE (ABCD=0001)(0/0): RX SEIZURE_ACK (ABCD=1101)(0/1): RX_IDLE (ABCD=1001)(0/2): RX_IDLE (ABCD=1001)(0/3): RX_IDLE (ABCD=1001)(0/4): RX_IDLE (ABCD=1001)(0/5): RX_IDLE (ABCD=1001)(0/6): RX_IDLE (ABCD=1001)(0/7): RX_IDLE (ABCD=1001)(0/8): RX_IDLE (ABCD=1001)(0/9): RX_IDLE (ABCD=1001)(0/10): RX_IDLE (ABCD=1001)(0/11): RX_IDLE (ABCD=1001)(0/12): RX_IDLE (ABCD=1001)(0/13): RX_IDLE (ABCD=1001)(0/14): RX_IDLE (ABCD=1001)(0/16): RX_IDLE (ABCD=1001)(0/17): RX_IDLE (ABCD=1001)(0/18): RX_IDLE (ABCD=1001)(0/19): RX_IDLE (ABCD=1001)(0/20): RX_IDLE (ABCD=1001)(0/21): RX_IDLE (ABCD=1001).(0/22): RX_IDLE (ABCD=1001)(0/23): RX_IDLE (ABCD=1001)(0/24): RX_IDLE (ABCD=1001)(0/25): RX_IDLE (ABCD=1001)(0/26): RX_IDLE (ABCD=1001)(0/27): RX_IDLE (ABCD=1001)(0/28): RX_IDLE (ABCD=1001)(0/29): RX_IDLE (ABCD=1001)(0/30): RX_IDLE (ABCD=1001)...(0/0): RX ANSWERED (ABCD=0101). Success rate is 0 percent (0/5) Router# *Mar 2 00:18:13.333: %LINK-3-UPDOWN: Interface Async94, changed state to up *Mar 2 00:18:13.333: %DIALER-6-BIND: Interface As94 bound to profile Di1 *Mar 2 00:18:14.577: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async94, changed state to up Router# p 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 160/180/236 ms

The following example shows that the call is cleared on the router: Router# clear int dialer 1 Router# (0/0): TX IDLE (ABCD=1001)(0/0): RX IDLE (ABCD=1001) *Mar 2 00:18:28.617: %LINK-5-CHANGED: Interface Async94, changed state to reset *Mar 2 00:18:28.617: %DIALER-6-UNBIND: Interface As94 unbound from profile Di1 *Mar 2 00:18:29.617: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async94, changed state to down et2-c3745-1# *Mar 2 00:18:33.617: %LINK-3-UPDOWN: Interface Async94, changed state to down

The following example shows a subsequent outbound CAS call: Router# p 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: *Mar 2 00:18:40: dsx1_alloc_cas_channel: channel 5 dsx1_timeslot 6(0/5): TX SEIZURE (ABCD=0001)(0/5): RX SEIZURE_ACK (ABCD=1101)....(0/5): RX ANSWERED (ABCD=0101). Success rate is 0 percent (0/5)


DB-220

May 2008


Router# *Mar 2 00:19:08.841: %LINK-3-UPDOWN: Interface Async93, changed state to up *Mar 2 00:19:08.841: %DIALER-6-BIND: Interface As93 bound to profile Di1 *Mar 2 00:19:10.033: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async93, changed state to up Router# p 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 160/167/176 ms

The following example shows the call cleared by the switch: Router# (0/5): TX IDLE (ABCD=1001)(0/5): RX IDLE (ABCD=1001) *Mar 2 00:19:26.249: %LINK-5-CHANGED: Interface Async93, changed state to reset *Mar 2 00:19:26.249: %DIALER-6-UNBIND: Interface As93 unbound from profile Di1 *Mar 2 00:19:27.249: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async93, changed state to down Router# *Mar 2 00:19:31.249: %LINK-3-UPDOWN: Interface Async93, changed state to down

The following example shows an incoming CAS call: Router# (0/0): RX SEIZURE (ABCD=0001) *Mar 2 00:22:40: dsx1_alloc_cas_channel: channel 0 dsx1_timeslot 1(0/0): TX SEIZURE_ACK (ABCD=1101)(0/0): TX ANSWERED (ABCD=0101) Router# *Mar 2 00:23:06.249: %LINK-3-UPDOWN: Interface Async83, changed state to up *Mar 2 00:23:06.249: %DIALER-6-BIND: Interface As83 bound to profile Di1 *Mar 2 00:23:07.653: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async83, changed state to up

Related Commands

Command

Description

show debug

Displays information about the types of debugging that are enabled for your router.


DB-221

Debug Commands debug ccaal2 session

debug ccaal2 session To display the ccaal2 function calls during call setup and teardown, use the debug ccaal2 session command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccaal2 session no debug ccaal2 session

Syntax Description


Defaults

Debugging for ATM Adaptation Layer type 2 (AAL2) sessions is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)XA

This command was introduced for the Cisco MC3810 series.

12.1(2)T

This command was integrated in Cisco IOS Release 12.1(2)T.

12.2(2)T

Support for this command was implemented on the Cisco 7200 series routers.

12.2(33)SRA


12.2SX


Usage Guidelines

Use this command when troubleshooting an AAL2 trunk setup or teardown problem.

Examples

The following example shows sample output from the debug ccaal2 session command for a forced shutdown of a voice port: Router# debug ccaal2 session CCAAL2 Session debugging is on Router# configure terminal Enter configuration commands, one per line. Router(config)# voice-port 2/0:0 Router(config-voiceport)# shutdown

End with CNTL/Z.

00:32:45:ccaal2_call_disconnect:peer tag 0 00:32:45:ccaal2_evhandle_call_disconnect:Entered 00:32:45:ccaal2_call_cleanup:freeccb 1, call_disconnected 1 00:32:45:starting incoming timer:Setting accept_incoming to FALSE and 00:32:45:timer 2:(0x622F6270)starts - delay (70000) 00:32:45:ccaal2_call_cleanup:Generating Call record 00:32:45:cause=81 tcause=81 cause_text=unspecified


DB-222

May 2008

Debug Commands debug ccaal2 session

00:32:45:ccaal2_call_cleanup:ccb 0x63FF1700, vdbPtr 0x62DFF2E0 freeccb_flag=1, call_disconnected_flag=1 00:32:45:%LINK-3-UPDOWN:Interface recEive and transMit2/0:0(1), changed state to Administrative Shutdown

The following example shows sample output from the debug ccaal2 session command for a trunk setup on a voice port: Router# debug ccaal2 session Router(config-voiceport)# no shutdown Router(config-voiceport)# 00:35:28:%LINK-3-UPDOWN:Interface recEive and transMit2/0:0(1), changed state to up 00:35:35:ccaal2_call_setup_request:Entered 00:35:35:ccaal2_evhandle_call_setup_request:Entered 00:35:35:ccaal2_initialize_ccb:preferred_codec set(-1)(0) 00:35:35:ccaal2_evhandle_call_setup_request:preferred_codec set(5)(40). VAD is 1 00:35:35:ccaal2_call_setup_trunk:subchannel linking successfulccaal2_receive:xmitFunc is NULL 00:35:35:ccaal2_caps_ind:PeerTag = 49 00:35:35: codec(preferred) = 1, fax_rate = 2, vad = 2 00:35:35: cid = 56, config_bitmask = 258, codec_bytes = 40, signal_type=8 00:35:36:%HTSP-5-UPDOWN:Trunk port(channel) [2/0:0(1)] is up Router(config-voiceport)#

Related Commands

Command

Description

show debug

Shows which debug commands are enabled.


DB-223

Debug Commands debug ccfrf11 session

debug ccfrf11 session To display the ccfrf11 function calls during call setup and teardown, use the debug ccfrf11 session command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccfrf11 session no debug ccfrf11 session

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)XG

This command was introduced for the Cisco 2600 and Cisco 3600 series routers.

12.0(4)T


12.0(7)XK

This command was first supported on the Cisco MC3810 series.

12.1(2)T

Support for this command was implemented in Cisco MC3810 images.

Usage Guidelines

12.2(33)SRA


12.2SX


Use this command to display debug information about the various FRF.11 VoFR service provider interface (SPI) functions. Note that this debug command does not display any information regarding the proprietary Cisco switched-VoFR SPI. This debug is useful only when the session protocol is “frf11-trunk.”

Examples

The following is sample output from the debug ccfrf11 session command: Router# debug ccfrf11 session INCOMING CALL SETUP (port setup for answer-mode): *Mar 6 18:04:07.693:ccfrf11_process_timers:scb (0x60EB6040) timer (0x60EB6098) expired *Mar 6 18:04:07.693:Setting accept_incoming to TRUE *Mar 6 18:04:11.213:ccfrf11_incoming_request:peer tag 800:callingNumber=+2602100, calledNumber=+3622110 *Mar 6 18:04:11.213:ccfrf11_initialize_ccb:preffered_codec set(-1)(0) *Mar 6 18:04:11.213:ccfrf11_evhandle_incoming_call_setup_request:calling +2602100, called +3622110 Incoming Tag 800 *Mar 6 18:04:11.217:ccfrf11_caps_ind:PeerTag = 800 *Mar 6 18:04:11.217: codec(preferred) = 4, fax_rate = 2, vad = 2 *Mar 6 18:04:11.217: cid = 30, config_bitmask = 0, codec_bytes = 20, signal_type=2 *Mar 6 18:04:11.217: required_bandwidth 8192 *Mar 6 18:04:11.217:ccfrf11_caps_ind:Bandwidth reservation of 8192 bytes succeeded.


DB-224

May 2008

Debug Commands debug ccfrf11 session

*Mar

6 18:04:11.221:ccfrf11_evhandle_call_connect:Entered

CALL SETUP (MASTER): 5d22h:ccfrf11_call_setup_request:Entered 5d22h:ccfrf11_evhandle_call_setup_request:Entered 5d22h:ccfrf11_initialize_ccb:preffered_codec set(-1)(0) 5d22h:ccfrf11_evhandle_call_setup_request:preffered_codec set(9)(24) 5d22h:ccfrf11_call_setup_trunk:subchannel linking successful 5d22h:ccfrf11_caps_ind:PeerTag = 810 5d22h: codec(preferred) = 512, fax_rate = 2, vad = 2 5d22h: cid = 30, config_bitmask = 1, codec_bytes = 24, signal_type=2 5d22h: required_bandwidth 6500 5d22h:ccfrf11_caps_ind:Bandwidth reservation of 6500 bytes succeeded. CALL TEARDOWN: *Mar 6 18:09:14.805:ccfrf11_call_disconnect:peer tag 0 *Mar 6 18:09:14.805:ccfrf11_evhandle_call_disconnect:Entered *Mar 6 18:09:14.805:ccfrf11_call_cleanup:freeccb 1, call_disconnected 1 *Mar 6 18:09:14.805:ccfrf11_call_cleanup:Setting accept_incoming to FALSE and starting incoming timer *Mar 6 18:09:14.809:timer 2:(0x60EB6098)starts - delay (70000) *Mar 6 18:09:14.809:ccfrf11_call_cleanup:Alive timer stopped *Mar 6 18:09:14.809:timer 1:(0x60F64104) stops *Mar 6 18:09:14.809:ccfrf11_call_cleanup:Generating Call record *Mar 6 18:09:14.809:cause=10 tcause=10 cause_text="normal call clearing." *Mar 6 18:09:14.809:ccfrf11_call_cleanup:Releasing 8192 bytes of reserved bandwidth *Mar 6 18:09:14.809:ccfrf11_call_cleanup:ccb 0x60F6404C, vdbPtr 0x610DB7A4 freeccb_flag=1, call_disconnected_flag=1

Related Commands

Command

Description


Displays the ccswvoice function calls during call setup and teardown.

debug ccswvoice vofr-session


debug vtsp session

Displays the first 10 bytes (including header) of selected VoFR subframes for the interface.


DB-225

Debug Commands debug cch323 capacity

debug cch323 capacity To track the call capacity of the gatekeeper, use the debug cch323 capacity command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cch323 capacity no debug cch323 capacity

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Usage Guidelines

Use the debug cch323 capacity command to track the maximum and current call capacity values in the Registration, Admission, and Status (RAS) Protocol messages and to debug capacity-related problems while sending RAS messages. This command is entered on the gateway to monitor the call capacity of the gatekeeper. The command lists the values for current and maximum call capacity provided by the trunk group capacity resource manager if and when the H.323 Service Provider Interface (SPI) requests the information for all or specific groups of circuits.

Examples

The following is sample output from the debug cch323 capacity command: Router# debug cch323 capacity Call Capacity Information tracing is enabled 5d00h: 5d00h: 5d00h: 5d00h:

cch323_process_carrier_update: Registered = 1,Event = 1,Reason = 1 cch323_process_carrier_update: CarrierId = CARRIERA_NEWENGLAND cch323_fill_crm_CallCapacities: Reason = 1, GroupID = CARRIERA_NEWENGLAND Capacity Details: Maximum Channels in Group: 23 Max. Voice Calls(In) : 23, Max. Voice Calls(Out): 23 Active Voice Calls(In): 5, Active Voice Calls(Out): 7 Max. Voice Calls(to GK): 23, Avail. Voice Calls(to GK): 11

The gatekeeper displays this output when trunk groups are added, deleted, or modified or when circuits in a trunk group are deactivated or activated (similar to ISDN layer 2 down/up).


DB-226

May 2008


5d00h: cch323_process_carrier_update: Registered = 1,Event = 1,Reason = 1 5d00h: cch323_process_carrier_update: CarrierId = CARRIERA_NEWENGLAND


debug cch323 capacity Update Field Descriptions

Field

Description

Registered

Gateway registration:

Event

•

0=Gateway is not registered to the gatekeeper

•

1=Gateway is registered to the gatekeeper at the time of the change

Carriers updated:

Reason

•

0=All carriers updated

•

1=Single carrier updated

Reason for the update notification:

CarrierID

•

0=CURRENT_CAPACITY_UPDATE

•

1=MAX_CAPACITY_UPDATE

•

2=BOTH_CAPACITY_UPDATE

ID of the trunk group or carrier to which the change applies.

The gatekeeper displays this output whenever call capacity information is sent to the gatekeeper. 5d00h: cch323_fill_crm_CallCapacities: Reason = 1, GroupID = CARRIERA_NEWENGLAND 5d00h: Capacity Details: Maximum Channels in Group: 23 Max. Voice Calls(In) : 23, Max. Voice Calls(Out): 23 Active Voice Calls(In): 5, Active Voice Calls(Out): 7 Max. Voice Calls(to GK): 23, Avail. Voice Calls(to GK): 11


debug cch323 capacity Call Capacity Field Descriptions

Field

Description

GroupID

The circuit’s carrier identification (ID) or trunk group label.

Maximum Channels in Group

Maximum number of physical (or configured) circuits.

Max. Voice Calls(In)

Maximum number of allowed incoming voice and data calls.

Max. Voice Calls(Out)

Maximum number of allowed outgoing voice and data calls.

Active Voice Calls(In)

Current number of active incoming voice and data calls.

Active Voice Calls(Out)

Current number of active outgoing voice and data calls.


DB-227


Table 45

Related Commands

debug cch323 capacity Call Capacity Field Descriptions (continued)

Field

Description

Max. Voice Calls(to GK)

Maximum call capacity value to be sent to the gatekeeper in the RAS message.

Avail. Voice Calls(to GK)

Available call capacity value to be sent to the gatekeeper in the RAS message.

Command

Description

endpoint circuit-id h323id

Associates a carrier with a non-Cisco endpoint.


DB-228

May 2008

Debug Commands debug cch323 h225

debug cch323 h225 To provide the trace of the state transition of the H.225 state machine based on the processed events, use the debug cch323 h225 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cch323 h225 no debug cch323 h225

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2


12.2(2)XB1


12.2(11)T


12.2SX


Usage Guidelines

State Descriptions

The state definitions of the different states of the H.225 state machine are as follows: •

H225_IDLE—This is the initial state of the H.225 state machine. The H.225 state machine is in this state before issuing a call setup request (for the outbound IP call case) or ready to receive an incoming IP call.

•

H225_SETUP—This is the call setup state. The state machine transitions to this state after sending out a call setup request, or after the reception of an incoming call indication.

•

H225_ALERT—This is the call alerting state. The state machine transitions to this state after sending the alerting message or after the reception of an alerting message from the peer.

•

H225_CALLPROC—This is the call proceeding state.

•

H225_ACTIVE—This is the Call connected state. In this state, the call is active. The state machine transitions to this state after sending the connect message to the peer or after the reception of the connect message from the peer.

•

H225_WAIT_FOR_ARQ—This is the state where the H.225 state machine is waiting for the completion of the ARQ process from the Registration, Admission, and Status Protocol (RAS) state machine.


DB-229


•

H225_WAIT_FOR_DRQ—This is the state where the H.225 state machine is waiting for the completion of the DRQ process from the RAS state machine.

•

H225_WAIT_FOR_H245—This is the state where the H.225 state machine is waiting for the success or failure from the H.245 state machine.

Events Description

The event definitions of the different events of the H.225 state machine are as follows: •

H225_EVENT_NONE— No event.

•

H225_EVENT_ALERT—This event indicates the H.225 state machine to send an alerting message to the peer.

•

H225_EVENT_ALERT_IND—This event indicates the H.225 state machine that an alerting message is received from the peer.

•

H225_EVENT_CALLPROC—This event indicates the H.225 state machine to send a call proceeding message to the peer.

•

H225_EVENT_CALLPROC_IND—This event indicates the H.225 state machine that a call proceeding message is received from the peer.

•

H225_EVENT_REJECT—This event indicates the H.225 state machine to reject the call setup request from the peer.

•

H225_EVENT_REJECT_IND—This event indicates the H.225 state machine that a call setup request to the peer is rejected.

•

H225_EVENT_RELEASE—This event indicates the H.225 state machine to send a release complete message to the peer.

•

H225_EVENT_RELEASE_IND—This event indicates the H.225 state machine that a release complete message is received from the peer.

•

H225_EVENT_SETUP—This event indicates the H.225 state machine to send a setup message to the peer.

•

H225_EVENT_SETUP_IND—This event indicates the H.225 state machine that a setup message is received from the peer.

•

H225_EVENT_SETUP_CFM—This event indicates the H.225 state machine to send a connect message to the peer.

•

H225_EVENT_SETUP_CFM_IND—This event indicates the H.225 state machine that a connect message from the peer.

•

H225_EVENT_RAS_SUCCESS—This event indicates the H.225 state machine that the pending RAS operation is successful.

•

H225_EVENT_RAS_FAILED—This event indicates the H.225 state machine that the pending RAS operation failed.

•

H225_EVENT_H245_SUCCESS—This event indicates the H.225 state machine that the pending H.245 operation is successful.

•

H225_EVENT_H245_FAILED—This event indicates the H.225 state machine that the pending H.245 operation failed.


DB-230

May 2008


Examples

The following is sample output from the debug cch323 h225 command: Router# debug cch323 h225 20:59:17:Set new event H225_EVENT_SETUP 20:59:17:H225 FSM:received event H225_EVENT_SETUP while at state H225_IDLE 20:59:17:Changing from H225_IDLE state to H225_SETUP state 20:59:17:cch323_h225_receiver:received msg of type SETUPCFM_CHOSEN 20:59:17:H225 FSM:received event H225_EVENT_SETUP_CFM_IND while at state H225_SETUP 20:59:17:Changing from H225_SETUP state to H225_ACTIVE state 20:59:17:Set new event H225_EVENT_H245_SUCCESS 20:59:17:H225 FSM:received event H225_EVENT_H245_SUCCESS while at state H225_ACTIVE 20:59:20:Set new event H225_EVENT_RELEASE 20:59:20:H225 FSM:received event H225_EVENT_RELEASE while at state H225_ACTIVE 20:59:20:Changing from H225_ACTIVE state to H225_WAIT_FOR_DRQ state 20:59:20:Set new event H225_EVENT_RAS_SUCCESS 20:59:20:H225 FSM:received event H225_EVENT_RAS_SUCCESS while at state H225_WAIT_FOR_DRQ 20:59:20:Changing from H225_WAIT_FOR_DRQ state to H225_IDLE state


DB-231


debug cch323 h245 To provide the trace of the state transition of the H.245 state machine based on the processed events, use the debug cch323 h245 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cch323 h245 no debug cch323 h245

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2


12.2(2)XB1


12.2(11)T


12.2SX


Usage Guidelines

The H.245 state machines include the following three state machines: •

Master SlaveDetermination (MSD) state machine

•

Capability Exchange (CAP) state machine

•

Open Logical Channel (OLC) state machine

State Definitions

The definitions are as follows: •

H245_MS_NONE— This is the initial state of the master slave determination state machine.

•

H245_MS_WAIT—In this state, a Master Slave Determination message is sent, waiting for the reply.

•

H245_MS_DONE— The result is in.

•

H245_CAP_NONE—This is the initial state of the capabilities exchange state machine.

•

H245_CAP_WAIT—In this state, a cap exchange message is sent, waiting for reply.

•

H245_CAP_DONE—The result is in.

•

H245_OLC_NONE—This is the initial state of the open logical channel state machine.


DB-232

May 2008


•

H245_OLC_WAIT: OLC message sent, waiting for reply.

•

H245_OLC_DONE: OLC done.

Event definitions

Examples

•

H245_EVENT_MSD—Send MSD message

•

H245_EVENT_MS_CFM—Send MSD acknowledge message

•

H245_EVENT_MS_REJ—Send MSD reject message

•

H245_EVENT_MS_IND— Received MSD message

•

H245_EVENT_CAP—Send CAP message

•

H245_EVENT_CAP_CFM—Send CAP acknowledge message

•

H245_EVENT_CAP_REJ—Send CAP reject

•

H245_EVENT_CAP_IND—Received CAP message

•

H245_EVENT_OLC—Send OLC message

•

H245_EVENT_OLC_CFM—Send OLC acknowledge message

•

H245_EVENT_OLC_REJ—Send OLC reject message

•

H245_EVENT_OLC_IND—Received OLC message

The following is sample output from the debug cch323 h245 command: Router# debug cch323 h245 20:58:23:Changing to new event H245_EVENT_MSD 20:58:23:H245 MS FSM:received event H245_EVENT_MSD while at state H245_MS_NONE 20:58:23:changing from H245_MS_NONE state to H245_MS_WAIT state 20:58:23:Changing to new event H245_EVENT_CAP 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP while at state H245_CAP_NONE 20:58:23:changing from H245_CAP_NONE state to H245_CAP_WAIT state 20:58:23:cch323_h245_receiver:received msg of type M_H245_MS_DETERMINE_INDICATION 20:58:23:Changing to new event H245_EVENT_MS_IND 20:58:23:H245 MS FSM:received event H245_EVENT_MS_IND while at state H245_MS_WAIT 20:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_INDICATION 20:58:23:Changing to new event H245_EVENT_CAP_IND 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_IND while at state H245_CAP_WAIT 20:58:23:cch323_h245_receiver:received msg of type M_H245_MS_DETERMINE_CONFIRM 20:58:23:Changing to new event H245_EVENT_MS_CFM 20:58:23:H245 MS FSM:received event H245_EVENT_MS_CFM while at state H245_MS_WAIT 20:58:23:changing from H245_MS_WAIT state to H245_MS_DONE state 0:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_CONFIRM 20:58:23:Changing to new event H245_EVENT_CAP_CFM 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_CFM while at state H245_CAP_WAIT 20:58:23:changing from H245_CAP_WAIT state to H245_CAP_DONE state 20:58:23:Changing to new event H245_EVENT_OLC 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC while at state


DB-233


H245_OLC_NONE 20:58:23:changing from H245_OLC_NONE state to H245_OLC_WAIT state 20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTABLISH_INDICATION 20:58:23:Changing to new event H245_EVENT_OLC_IND 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_IND while at state H245_OLC_WAIT 20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTAB_ACK 20:58:23:Changing to new event H245_EVENT_OLC_CFM 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_CFM while at state H245_OLC_WAIT 20:58:23:changing from H245_OLC_WAIT state to H245_OLC_DONE state


DB-234

May 2008

Debug Commands debug cch323 preauth

debug cch323 preauth To enable diagnostic reporting of authentication, authorization, and accounting (AAA) call preauthentication for H.323 calls, use the debug cch323 preauth command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cch323 preauth no debug cch323 preauth

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Examples

The following is debugging output for a single H.323 call: Router# debug cch323 preauth CCH323 preauth tracing is enabled cch323_is_preauth_reqd is TRUE Jan 23 18:39:56.393: In cch323_send_preauth_req for preauth_id = -1 Jan 23 18:39:56.393: Entering rpms_proc_print_preauth_req Jan 23 18:39:56.393: Request = 0 Jan 23 18:39:56.393: Preauth id = 86514 Jan 23 18:39:56.393: EndPt Type = 1 Jan 23 18:39:56.393: EndPt = 192.168.81.102 Jan 23 18:39:56.393: Resource Service = 1 Jan 23 18:39:56.393: Call_origin = answer Jan 23 18:39:56.393: Call_type = voip Jan 23 18:39:56.393: Calling_num = 2230001 Jan 23 18:39:56.393: Called_num = 1#1130001 Jan 23 18:39:56.393: Protocol = 0 Jan 23 18:39:56.393: cch323_insert_preauth_tree:Created node with preauth_id = 86514 ,ccb 6852D5BC , node 651F87FC Jan 23 18:39:56.393:rpms_proc_create_node:Created node with preauth_id = 86514 Jan 23 18:39:56.393:rpms_proc_send_aaa_req:uid got is 466725 Jan 23 18:39:56.397:rpms_proc_preauth_response:Context is for preauth_id 86514, aaa_uid 466725 Jan 23 18:39:56.397: Entering Function cch323_rpms_proc_callback_func


DB-235

Debug Commands debug cch323 preauth

Jan 23 18:39:56.397:cch323_rpms_proc_callback_func:PREAUTH_SUCCESS for preauth id 86514 aaa_uid 466725 auth_serv 1688218168 Jan 23 18:39:56.397:rpms_proc_preauth_response:Deleting Tree node for preauth id 86514 uid 466725 Jan 23 18:39:56.397:cch323_get_ccb_and_delete_from_preauth_tree:Preauth_id=86514 cch323_get_ccb_and_delete_from_preauth_tree:651F87FC node and 6852D5BC ccb


debug cch323 preauth Field Descriptions

Field

Description

Request

Request Type—0 for preauthentication, 1 for disconnect.

Preauth id

Identifier for the preauthentication request.

EndPt Type

Call Origin End Point Type—1 for IP address, 2 for IZCT value.

EndPt

Call Origin End Point Value—An IP address or IZCT value.

Resource Service

Resource Service Type—1 for Reservation, 2 for Query.

Call_origin

Answer.

Call_type

Voice over IP (VoIP).

Calling_num

Calling Party Number (CLID).

Called_num

Called Party Number (DNIS).

Protocol

0 for H.323, 1 for SIP.

function reports

Various identifiers and status reports for executed functions.


DB-236

May 2008

Debug Commands debug cch323 ras

debug cch323 ras To provide the trace of the state transition of the Registration, Admission, and Status (RAS) Protocol state machine based on the processed events, use the debug cch323 ras command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cch323 ras no debug cch323 ras

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2


12.2(2)XB1


12.2(11)T


12.2SX


Usage Guidelines

RAS operates in two state machines. One global state machine controls the overall RAS operation of the Gateway. The other state machine is a per call state machine that controls the active calls. State definitions

The state definitions of the different states of the RAS state machine follow: •

CCH323_RAS_STATE_NONE—This is the initial state of the RAS state machine.

•

CCH323_RAS_STATE_GRQ—The state machine is in the Gatekeeper Request (GRQ) state. In this state, the gateway is in the process of discovering a gatekeeper.

•

CCH323_RAS_STATE_RRQ—The state machine is in the Registration Request (RRQ) state. In this state, the gateway is in the process of registering with a gatekeeper.

•

CCH323_RAS_STATE_IDLE—The global state machine is in the idle state.

•

CCH323_RAS_STATE_URQ—The state machine is in the Unregistration Request (URQ) state. In this state, the gateway is in the process of unregistering with a gatekeeper.

•

CCH323_RAS_STATE_ARQ—The per call state machine is in the process of admitting a new call.

•

CCH323_RAS_STATE_ACTIVE—The per call state machine is in the call active state.


DB-237


•

CCH323_RAS_STATE_DRQ—The per call state machine is in the process of disengaging an active call.

Event Definitions

These are the event definitions of the different states of the RAS state machine:

Examples

•

CCH323_RAS_EVENT_NONE—Nothing.

•

CCH323_RAS_EVENT_GWUP—Gateway is coming up.

•

CCH323_RAS_EVENT_GWDWN—Gateway is going down.

•

CCH323_RAS_EVENT_NEWCALL—New call.

•

CCH323_RAS_EVENT_CALLDISC—Call disconnect.

•

CCH323_RAS_EVENT_GCF—Received Gatekeeper Confirmation (GCF).

•

CCH323_RAS_EVENT_GRJ—Received Gatekeeper Rejection (GRJ).

•

CCH323_RAS_EVENT_ACF—Received Admission Confirmation (ACF).

•

CCH323_RAS_EVENT_ARJ—Received Admission Rejection (ARJ).

•

CCH323_RAS_EVENT_SEND_RRQ—Send Registration Request (RRQ).

•

CCH323_RAS_EVENT_RCF—Received Registration Confirmation (RCF).

•

CCH323_RAS_EVENT_RRJ—Received Registration Rejection (RRJ).

•

CCH323_RAS_EVENT_SEND_URQ—Send URQ.

•

CCH323_RAS_EVENT_URQ—Received URQ.

•

CCH323_RAS_EVENT_UCF—Received Unregister Confirmation (UCF).

•

CCH323_RAS_EVENT_SEND_UCF—Send Unregister Confirmation (UCF).

•

CCH323_RAS_EVENT_URJ—Received Unregister Reject (URJ).

•

CCH323_RAS_EVENT_BCF—Received Bandwidth Confirm (BCF).

•

CCH323_RAS_EVENT_BRJ—Received Bandwidth Rejection (BRJ).

•

CCH323_RAS_EVENT_DRQ—Received Disengage Request (DRQ).

•

CCH323_RAS_EVENT_DCF—Received Disengage Confirm (DCF).

•

CCH323_RAS_EVENT_SEND_DCF—Send Disengage Confirm (DCF).

•

CCH323_RAS_EVENT_DRJ—Received Disengage Reject (DRJ).

•

CCH323_RAS_EVENT_IRQ—Received Interrupt Request (IRQ).

•

CCH323_RAS_EVENT_IRR—Send Information Request (IRR).

•

CCH323_RAS_EVENT_TIMEOUT—Message timeout.

The following is sample output from the debug cch323 preauth command: Router# debug cch323 preauth 20:58:49:Changing to new event CCH323_RAS_EVENT_SEND_RRQ cch323_run_ras_sm:received event CCH323_RAS_EVENT_SEND_RRQ while at CCH323_RAS_STATE_IDLE state cch323_run_ras_sm:changing to CCH323_RAS_STATE_RRQ state cch323_ras_receiver:received msg of type RCF_CHOSEN cch323_run_ras_sm:received event CCH323_RAS_EVENT_RCF while at CCH323_RAS_STATE_RRQ state


DB-238

May 2008


cch323_run_ras_sm:changing to CCH323_RAS_STATE_IDLE state 20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_NEWCALL while at CCH323_RAS_STATE_IDLE state 20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ARQ cch323_ras_receiver:received msg of type ACF_CHOSEN 20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_ACF while at CCH323_RAS_STATE_ARQ state 20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ACTIVE 20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_CALLDISC while at CCH323_RAS_STATE_ACTIVE state 20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_DRQ cch323_ras_receiver:received msg of type DCF_CHOSEN 20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_DCF while at CCH323_RAS_STATE_DRQ state 20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_IDLE 20:59:04:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_IRR while at CCH323_RAS_STATE_ACTIVE state 20:59:04:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ACTIVE


DB-239

Debug Commands debug cch323 video

debug cch323 video To provide debugging output for video components within the H.323 subsystem, use the debug cch323 video command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cch323 video no debug cch323 video

Syntax Description


Command Modes

Privileged EXEC

Command History

Cisco IOS Release

Modification

12.4(4)XC


12.4(9)T


12.2SX


Usage Guidelines

Use this command to enable a debugging trace for the video component in an H.323 network.

Examples

Originating Gateway Example

The following is sample output of the debugging log for an originating Cisco Unified CallManager Express (Cisco Unified CME) gateway after the debug cch323 video command was enabled: Router# show log Syslog logging: enabled (11 messages dropped, 487 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) Console logging: disabled Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging: level debugging, 1144 messages logged, xml disabled, filtering disabled Logging Exception size (4096 bytes) Count and timestamp logging messages: disabled Trap logging: level informational, 1084 message lines logged Log Buffer (6000000 bytes): Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: Entry Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: Have peer Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_pref_codec_list: First preferred codec(bytes)=16(20) Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_peer_info: Flow Mode set to FLOW_THROUGH


DB-240

May 2008


Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_caps_chn_info: No peer leg setup params Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_get_caps_chn_info: Setting CCH323_SS_NTFY_VIDEO_INFO Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_h323_control_options_outgoing: h245 sm mode = 8463 Jun 13 09:19:42.006: //103030/C7838B198002/H323/cch323_set_h323_control_options_outgoing: h323_ctl=0x20 Jun 13 09:19:42.010: //103030/C7838B198002/H323/cch323_rotary_validate: No peer_ccb available

Terminating Gateway Example

The following is sample output of the debugging log for a terminating Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) gateway after the debug cch323 video command was enabled: Router# show log Syslog logging: enabled (11 messages dropped, 466 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) Console logging: disabled Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging: level debugging, 829 messages logged, xml disabled, filtering disabled Logging Exception size (4096 bytes) Count and timestamp logging messages: disabled Trap logging: level informational, 771 message lines logged Log Buffer (200000 bytes): Jun 13 09:19:42.011: //103034/C7838B198002/H323/setup_ind: Receive bearer cap infoXRate 24, rateMult 12 Jun 13 09:19:42.011: //103034/C7838B198002/H323/cch323_set_h245_state_mc_mode_incoming: h245 state m/c mode=0x10F, h323_ctl=0x2F Jun 13 09:19:42.015: //-1/xxxxxxxxxxxx/H323/cch245_event_handler: callID=103034 Jun 13 09:19:42.019: //-1/xxxxxxxxxxxx/H323/cch245_event_handler: Event CC_EV_H245_SET_MODE: data ptr=0x465D5760 Jun 13 09:19:42.019: //-1/xxxxxxxxxxxx/H323/cch323_set_mode: callID=103034, flow Mode=1 spi_mode=0x6 Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_do_call_proceeding: set_mode NOT called yet...saved deferred CALL_PROC Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_h245_connection_sm: state=0, event=0, ccb=4461B518, listen state=0 Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_process_set_mode: Setting inbound leg mode flags to 0x10F, flow-mode to FLOW_THROUGH Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_process_set_mode: Sending deferred CALL_PROC Jun 13 09:19:42.019: //103034/C7838B198002/H323/cch323_do_call_proceeding: set_mode called so we can proceed with CALLPROC Jun 13 09:19:42.027: //103034/C7838B198002/H323/cch323_h245_connection_sm: state=1, event=2, ccb=4461B518, listen state=1 Jun 13 09:19:42.027: //103034/C7838B198002/H323/cch323_send_cap_request: Setting mode to VIDEO MODE Jun 13 09:19:42.031: //103034/C7838B198002/H323/cch323_h245_cap_ind: Masks au=0xC data=0x2 uinp=0x32


DB-241


Related Commands

Command

Description

debug ephone video

Sets video debugging for the Cisco Unified IP phone.

show call active video

Displays call information for SCCP video calls in progress.

show call history video Displays call history information for SCCP video calls. show debugging



DB-242

May 2008

Debug Commands debug cch323

debug cch323 To provide debugging output for various components within the H.323 subsystem, use the debug cch323 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cch323 {all | error | h225 | h245 | nxe | ras | rawmsg | session} no debug cch323

Syntax Description

all

Enables all debug cch323 commands.

error

Traces errors encountered in the H.323 subsystem and can be used to help troubleshoot problems with H.323 calls.

h225

Traces the state transition of the H.225 state machine on the basis of the processed event.

h245

Traces the state transition of the H.245 state machine on the basis of the processed events.

nxe

Displays Annex E events that have been transmitted and received.

ras

Traces the state transition of the Registration, Admission, and Status (RAS) state machine on the basis of the processed events.

rawmsg

Troubleshoots raw message buffer problems.

session

Traces general H.323 events and can be used to troubleshoot H.323 problems.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2

The debug cch323 command and the following keywords were introduced: h225, h245, and ras.

12.2(2)XA

The nxe keyword was added.

12.2(4)T

The following keywords were introduced: all, error, rawmsg, and session. The nxe keyword was integrated into Cisco IOS Release 12.2(4)T on all Cisco H.323 platforms. This command does not support the Cisco access server platforms in this release.

12.2(2)XB1


12.2SX



DB-243


Usage Guidelines

The debug cch323 Command with the all Keyword

When used with the debug cch323 command, the all keyword provides debug output for various components within the H.323 subsystem. The debug cch323 command used with the all keyword enables the following debug cch323 commands:

Caution

error

Enables a CCH323 Service Provider Interface (SPI) trace.

h225

Enables an H225 state machine debugging trace.

h245

Enables an H245 state machine debugging trace.

nxe

Enables an Annex E debugging trace.

ras

Enables a RAS state machine debugging trace.

rawmsg

Enables a CCH323 RAWMSG debugging trace.

session

Enables a Session debugging trace.

Using the debug cch323 all command could slow your system and flood the TTY if there is significant call traffic. The debug cch323 Command with the error Keyword

When used with the debug cch323 command, the error keyword allows you to trace errors encountered in the H.323 subsystem.

Note

There is little or no output from this command when there is a stable H.323 network. The debug cch323 Command with the h225 Keyword

When used with the debug cch323 command, the h225 keyword allows you to trace the state transition of the H.225 state machine on the basis of the processed event. The definitions of the different states of the H.225 state machine follow: •

H225_IDLE—This is the initial state of the H.225 state machine. The H.225 state machine is in this state before issuing a call setup request (for the outbound IP call case) or when ready to receive an incoming IP call.

•

H225_SETUP—This is the call setup state. The state machine changes to this state after sending out a call setup request or after receiving an incoming call indication.

•

H225_ALERT—This is the call alerting state. The state machine changes to this state after sending the alerting message or after receiving an alerting message from the peer.

•

H225_CALLPROC—This is the call proceeding state.

•

H225_ACTIVE—This is the call connected state. In this state, the call is active. The state machine changes to this state after sending the connect message to the peer or after receiving the connect message from the peer.

•

H225_WAIT_FOR_ARQ—This is the state in which the H.225 state machine is waiting for the completion of the Admission Request (ARQ) process from the RAS state machine.


DB-244

May 2008


•

H225_WAIT_FOR_DRQ—This is the state in which the H.225 state machine is waiting for the completion of the Disengage Request (DRQ) process from the RAS state machine.

•

H225_WAIT_FOR_H245—This is the state in which the H.225 state machine is waiting for the success or failure from the H.245 state machine.

The definitions of the different events of the H.225 state machine follow: •

H225_EVENT_NONE—There is no event.

•

H225_EVENT_ALERT—This event instructs the H.225 state machine to send an alert message to the peer.

•

H225_EVENT_ALERT_IND—This event indicates to the H.225 state machine that an alert message arrived from the peer.

•

H225_EVENT_CALLPROC—This event instructs the H.225 state machine to send a call proceeding message to the peer.

•

H225_EVENT_CALLPROC_IND—This event indicates to the H.225 state machine that a call proceeding message has been received from the peer.

•

H225_EVENT_REJECT—This event instructs the H.225 state machine to reject the call setup request from the peer.

•

H225_EVENT_REJECT_IND—This event indicates to the H.225 state machine that a call setup request to the peer has been rejected.

•

H225_EVENT_RELEASE—This event instructs the H.225 state machine to send a release complete message to the peer.

•

H225_EVENT_RELEASE_IND—This event indicates to the H.225 state machine that a release complete message has been received from the peer.

•

H225_EVENT_SETUP—This event instructs the H.225 state machine to send a setup message to the peer.

•

H225_EVENT_SETUP_IND—This event indicates to the H.225 state machine that a setup message has been received from the peer.

•

H225_EVENT_SETUP_CFM—This event instructs the H.225 state machine to send a connect message to the peer.

•

H225_EVENT_SETUP_CFM_IND—This event indicates to the H.225 state machine that a connect message arrived from the peer.

•

H225_EVENT_RAS_SUCCESS—This event indicates to the H.225 state machine that the pending RAS operation succeeded.

•

H225_EVENT_RAS_FAILED—This event indicates to the H.225 state machine that the pending RAS operation failed.

•

H225_EVENT_H245_SUCCESS—This event indicates to the H.225 state machine that the pending H.245 operation succeeded.

•

H225_EVENT_H245_FAILED—This event indicates to the H.225 state machine that the pending H.245 operation failed.


DB-245


The debug cch323 Command with the h245 Keyword

When used with the debug cch323 command, the h245 keyword allows you to trace the state transition of the H.245 state machine on the basis of the processed event. The H.245 state machines include the following three state machines: •

Master slave determination (MSD) state machine

•

Capability exchange (CAP) state machine

•

Open logical channel (OLC) state machine

The state definitions follow: •

H245_MS_NONE—This is the initial state of the MSD state machine.

•

H245_MS_WAIT—In this state, an MSD message is sent, and the device is waiting for the reply.

•

H245_MS_DONE— The result is in.

•

H245_CAP_NONE—This is the initial state of the CAP state machine.

•

H245_CAP_WAIT—In this state, a CAP message is sent, and the device is waiting for the reply.

•

H245_CAP_DONE—The result is in.

•

H245_OLC_NONE—This is the initial state of the OLC state machine.

•

H245_OLC_WAIT—In this state, an OLC message is sent, and the device is waiting for the reply.

•

H245_OLC_DONE—The result is in.

The event definitions follow: •

H245_EVENT_MSD—Send MSD message.

•

H245_EVENT_MS_CFM—Send MSD acknowledge message.

•

H245_EVENT_MS_REJ—Send MSD reject message.

•

H245_EVENT_MS_IND—Received MSD message.

•

H245_EVENT_CAP—Send CAP message.

•

H245_EVENT_CAP_CFM—Send CAP acknowledge message.

•

H245_EVENT_CAP_REJ—Send CAP reject message.

•

H245_EVENT_CAP_IND—Received CAP message.

•

H245_EVENT_OLC—Send OLC message.

•

H245_EVENT_OLC_CFM—Send OLC acknowledge message.

•

H245_EVENT_OLC_REJ—Send OLC reject message.

•

H245_EVENT_OLC_IND—Received OLC message.

The debug cch323 Command with the nxe Keyword

When used with the debug cch323 command, the nxe keyword allows you to display the Annex E events that have been transmitted and received. The debug cch323 Command with the ras Keyword

When used with the debug cch323 command, the ras keyword allows you to trace the state transition of the RAS state machine based on the processed events. RAS operates in two state machines. One global state machine controls the overall RAS operation of the gateway. The other state machine is a per-call state machine that controls the active calls.


DB-246

May 2008


The definitions of the different states of the RAS state machine follow: •

CCH323_RAS_STATE_NONE—This is the initial state of the RAS state machine.

•

CCH323_RAS_STATE_GRQ—The state machine is in the Gatekeeper Request (GRQ) state. In this state, the gateway is discovering a gatekeeper.

•

CCH323_RAS_STATE_RRQ—The state machine is in the Registration Request (RRQ) state. In this state, the gateway is registering with a gatekeeper.

•

CCH323_RAS_STATE_IDLE—The global state machine is in the idle state.

•

CCH323_RAS_STATE_URQ—The state machine is in the Unregistration Request (URQ) state. In this state, the gateway is in the process of unregistering with a gatekeeper.

•

CCH323_RAS_STATE_ARQ—The per-call state machine is in the process of admitting a new call.

•

CCH323_RAS_STATE_ACTIVE—The per-call state machine is in the call active state.

•

CCH323_RAS_STATE_DRQ—The per-call state machine is in the process of disengaging an active call.

The definitions of the different events of the RAS state machine follow: •

CCH323_RAS_EVENT_NONE—Nothing.

•

CCH323_RAS_EVENT_GWUP—Gateway is coming up.

•

CCH323_RAS_EVENT_GWDWN—Gateway is going down.

•

CCH323_RAS_EVENT_NEWCALL—New call.

•

CCH323_RAS_EVENT_CALLDISC—Call disconnect.

•

CCH323_RAS_EVENT_GCF—Received Gatekeeper Confirmation (GCF).

•

CCH323_RAS_EVENT_GRJ—Received Gatekeeper Rejection (GRJ).

•

CCH323_RAS_EVENT_ACF—Received Admission Confirmation (ACF).

•

CCH323_RAS_EVENT_ARJ—Received Admission Reject (ARJ).

•

CCH323_RAS_EVENT_SEND_RRQ—Send Registration Request (RRQ).

•

CCH323_RAS_EVENT_RCF—Received Registration Confirmation (RCF).

•

CCH323_RAS_EVENT_RRJ—Received Registration Rejection (RRJ).

•

CCH323_RAS_EVENT_SEND_URQ—Send Unregistration Request (URQ).

•

CCH323_RAS_EVENT_URQ—Received URQ.

•

CCH323_RAS_EVENT_UCF—Received Unregister Confirmation (UCF).

•

CCH323_RAS_EVENT_SEND_UCF—Send UCF.

•

CCH323_RAS_EVENT_URJ—Received Unregister Reject (URJ).

•

CCH323_RAS_EVENT_BCF—Received Bandwidth Confirm (BCF).

•

CCH323_RAS_EVENT_BRJ—Received Bandwidth Rejection (BRJ).

•

CCH323_RAS_EVENT_DRQ—Received Disengage Request (DRQ).

•

CCH323_RAS_EVENT_DCF—Received Disengage Confirm (DCF).

•

CCH323_RAS_EVENT_SEND_DCF—Send DCF.

•

CCH323_RAS_EVENT_DRJ—Received Disengage Reject (DRJ).

•

CCH323_RAS_EVENT_IRQ—Received Interrupt Request (IRQ).

•

CCH323_RAS_EVENT_IRR—Send Information Request (IRR).


DB-247


•

CCH323_RAS_EVENT_TIMEOUT—Message timeout.

The debug cch323 Command with the rawmsg Keyword

When used with the debug cch323 command, the rawmsg keyword allows you to troubleshoot raw message buffer problems.

Caution

Using the debug cch323 command with the rawmsg keyword could slow your system and flood the TTY if there is significant call traffic. The debug cch323 Command with the session Keyword

Used with the debug cch323 command, the session keyword allows you to trace general H.323 events.

Caution

Examples

Using the debug cch323 session command could slow your system and flood the TTY if there is significant call traffic.

The debug cch323 Command with the all Keyword Example

The debug cch323 all command and keyword combination provides output for the following keywords: error, h225, h245, nxe, ras, rawmsg, and session. Examples of output for each keyword follow. The debug cch323 Command with the error Keyword Example

The following is sample output from a typical debug cch323 error request on a Cisco 3640 router: Router# debug cch323 error cch323_h225_receiver:received msg of unknown type 5

The debug cch323 Command with the h225 Keyword Example

The following is sample output from a typical debug cch323 h225 request on a Cisco 3640 router: Router# debug cch323 h225 20:59:17:Set new event H225_EVENT_SETUP 20:59:17:H225 FSM:received event H225_EVENT_SETUP while at state H225_IDLE 20:59:17:Changing from H225_IDLE state to H225_SETUP state 20:59:17:cch323_h225_receiver:received msg of type SETUPCFM_CHOSEN 20:59:17:H225 FSM:received event H225_EVENT_SETUP_CFM_IND while at state H225_SETUP 20:59:17:Changing from H225_SETUP state to H225_ACTIVE state 20:59:17:Set new event H225_EVENT_H245_SUCCESS 20:59:17:H225 FSM:received event H225_EVENT_H245_SUCCESS while at state H225_ACTIVE 20:59:20:Set new event H225_EVENT_RELEASE 20:59:20:H225 FSM:received event H225_EVENT_RELEASE while at state H225_ACTIVE 20:59:20:Changing from H225_ACTIVE state to H225_WAIT_FOR_DRQ state 20:59:20:Set new event H225_EVENT_RAS_SUCCESS 20:59:20:H225 FSM:received event H225_EVENT_RAS_SUCCESS while at state H225_WAIT_FOR_DRQ 20:59:20:Changing from H225_WAIT_FOR_DRQ state to H225_IDLE state


DB-248

May 2008



debug cch323 h225 Field Descriptions

Field

Description

H225_EVENT_SETUP

This event instructs the H.225 state machine to send a setup message to the peer.

H225_IDLE

The initial state of the H.225 state machine. The H.225 state machine is in this state before issuing a call setup request (for the outbound IP call case) or when ready to receive an incoming IP call.

H225_SETUP

The call setup state. The state machine changes to this state after sending out a call setup request or after receiving an incoming call indication.

SETUPCFM_CHOSEN

The H225 connect message that has been received from a remote H323 endpoint.

H225_EVENT_SETUP_CFM_IND

This event indicates to the H.225 state machine that a connect message arrived from the peer.

H225_ACTIVE

The call connected state. In this state, the call is active. The state machine changes to this state after sending the connect message to the peer or after receiving the connect message from the peer.

H225_EVENT_H425_SUCCESS

This event indicates to the H.225 state machine that the pending H.245 operation succeeded.

H225_EVENT_RELEASE

This event instructs the H.225 state machine to send a release complete message to the peer.

H225_WAIT_FOR_DRQ

The state in which the H.225 state machine is waiting for the completion of the DRQ process from the RAS state machine.

H225_EVENT_RAS_SUCCESS

This event indicates to the H.225 state machine that the pending RAS operation succeeded.

H225 FSM

The finite state machine.

The debug cch323 Command with the h245 Keyword Example

The following is sample output from a typical debug cch323 h245 request on a Cisco 3640 router: Router# debug cch323 h245 20:58:23:Changing to new event H245_EVENT_MSD 20:58:23:H245 MS FSM:received event H245_EVENT_MSD while at state H245_MS_NONE 20:58:23:changing from H245_MS_NONE state to H245_MS_WAIT state 20:58:23:Changing to new event H245_EVENT_CAP 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP while at state H245_CAP_NONE 20:58:23:changing from H245_CAP_NONE state to H245_CAP_WAIT state 20:58:23:cch323_h245_receiver:received msg of type M_H245_MS_DETERMINE_INDICATION 20:58:23:Changing to new event H245_EVENT_MS_IND 20:58:23:H245 MS FSM:received event H245_EVENT_MS_IND while at state H245_MS_WAIT


DB-249


20:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_INDICATION 20:58:23:Changing to new event H245_EVENT_CAP_IND 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_IND while at state H245_CAP_WAIT 20:58:23:cch323_h245_receiver:received msg of type M_H245_MS_DETERMINE_CONFIRM 20:58:23:Changing to new event H245_EVENT_MS_CFM 20:58:23:H245 MS FSM:received event H245_EVENT_MS_CFM while at state H245_MS_WAIT 20:58:23:changing from H245_MS_WAIT state to H245_MS_DONE state 0:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_CONFIRM 20:58:23:Changing to new event H245_EVENT_CAP_CFM 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_CFM while at state H245_CAP_WAIT 20:58:23:changing from H245_CAP_WAIT state to H245_CAP_DONE state 20:58:23:Changing to new event H245_EVENT_OLC 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC while at state H245_OLC_NONE 20:58:23:changing from H245_OLC_NONE state to H245_OLC_WAIT state 20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTABLISH_INDICATION 20:58:23:Changing to new event H245_EVENT_OLC_IND 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_IND while at state H245_OLC_WAIT 20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTAB_ACK 20:58:23:Changing to new event H245_EVENT_OLC_CFM 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_CFM while at state H245_OLC_WAIT 20:58:23:changing from H245_OLC_WAIT state to H245_OLC_DONE state


debug cch323 h245 Field Descriptions

Field

Description

H245_EVENT_MSD

Send MSD event message to the state machine.

H245 MS FSM

An H225 master slave determination finite state machine.

H245_MS_NONE

The initial state of the MSD state machine.

H245_MS_WAIT

In this state, a MSD message is sent, and the device is waiting for the reply.

H245_EVENT_CAP

Send CAP event message.

H245 CAP FSM

This is the H245 terminal CAP finite state machine.

H245_CAP_NONE

The initial state of the CAP state machine.

H245_CAP_WAIT

In this state, a CAP message is sent, and the device is waiting for the reply.

M_H245_MS_DETERMINE _INDICATION

The MSD message that has been received by an H245 terminal from a remote H323 endpoint.

H245_EVENT_MS_IND

Received MSD event message.

M_H245_CAP_TRANSFER_INDICATION

A CAP message that has been received by the H245 terminal from an H323 remote endpoint.


DB-250

May 2008


Table 48

debug cch323 h245 Field Descriptions (continued)

Field

Description

H245_EVENT_CAP_IND

Received CAP event message.

M_H245_MS_DETERMINE_CONFIRM

A confirmation message that the H245 master slave termination message was sent.

H245_EVENT_MS_CFM

Send MSD acknowledge event message.

H245_MS_DONE

The result is in.

M_H245_CAP_TRANSFER_CONFIRM

An indication to the H245 terminal that the CAP message was sent.

H245_EVENT_CAP_CFM

Send CAP acknowledge event message.

H245_CAP_DONE

The result is in.

H245_EVENT_OLC

Send OLC event message.

H245_OLC_NONE

The initial state of the OLC state machine.

H245_OLC_WAIT

In this state, an OLC message is sent, and the device is waiting for the reply.

M_H245_UCHAN_ESTABLISH_INDICATION

The OLC message received by an H245 terminal from a remote H323 endpoint.

H245_EVENT_OLC_IND

Received OLC event message.

M_H245_UCHAN_ESTAB_ACK

The OLC message acknowledgment received by an H245 terminal from a remote H323 endpoint.

H245_EVENT_OLC_CFM

Send OLC acknowledge event message.

H245 OLC FSM

The OLC finite state machine of the H245 terminal.

H245_EVENT_OLC_CFM

Send OLC acknowledge event message.

H245_OLC_DONE

The result is in.

The debug cch323 Command with the nxe Keyword Example

The following is sample output from a debug cch323 nxe request: Router# debug cch323 nxe 00:15:54:nxe_handle_usrmsg_to_remote:User Message size is 227 00:15:54:nxe_msg_send_possible:Msg put in the active Q for CRV [3, direction flag 0] 00:15:54:nxe_send_msg:H323chan returns bytes sent=241, the actual len=241, to IPaddr [0xA4D4A02], Port [2517] 00:15:54:nxe_handle_usrmsg_to_remote:Usr Msg sent for IPaddr [0xA4D4A02], Port [2517], CRV [3, direction flag 0] 00:15:54:nxe_parse_msg_from_remote:Msg received from IP [0xA4D4A02], Port [2517] 00:15:54:nxe_parse_msg_from_remote:Value of PDU flags = 0x2 00:15:54:nxe_parse_payload:Transport msg type, Payload flag = 0x0 00:15:54:nxe_receive_ack:Ack received for 1 pdus 00:15:54:nxe_receive_ack:Ack received for seqnum=13 from IPAddr [0xA4D4A02], Port [2517] 00:15:54:nxe_parse_msg_from_remote:Msg received from IP [0xA4D4A02], Port [2517] 00:15:54:nxe_parse_msg_from_remote:Value of PDU flags = 0x3 00:15:54:nxe_parse_payload:Static msg type, Payload flag = 0xA0 00:15:54:nxe_parse_x_static:Rx H225 msg from IPaddr [0xA4D4A02], Port [2517], CRV [3, direction flag 0] 00:15:54:nxe_make_ackmsg:NXE ACK Msg made to ack seqnum=14 00:15:54:nxe_send_msg:H323chan returns bytes sent=16, the actual len=16, to IPaddr


DB-251


[0xA4D4A02], Port [2517] 00:15:54:nxe_parse_msg_from_remote:Ack sent for Destination IPaddr [0xA4D4A02], Port [2517] 00:15:54:nxe_parse_msg_from_remote:Msg received from IP [0xA4D4A02], Port [2517] 00:15:54:nxe_parse_msg_from_remote:Value of PDU flags = 0x3 00:15:54:nxe_parse_payload:Static msg type, Payload flag = 0xA0 00:15:54:nxe_parse_x_static:Rx H225 msg from IPaddr [0xA4D4A02], Port [2517], CRV [3, direction flag 0]

The debug cch323 Command with the ras Keyword Example

The following is sample output from a typical debug cch323 ras request on a Cisco 3640 router: Router# debug cch323 ras 20:58:49:Changing to new event CCH323_RAS_EVENT_SEND_RRQ cch323_run_ras_sm:received event CCH323_RAS_EVENT_SEND_RRQ while at CCH323_RAS_STATE_IDLE state cch323_run_ras_sm:changing to CCH323_RAS_STATE_RRQ state cch323_ras_receiver:received msg of type RCF_CHOSEN cch323_run_ras_sm:received event CCH323_RAS_EVENT_RCF while at CCH323_RAS_STATE_RRQ state cch323_run_ras_sm:changing to CCH323_RAS_STATE_IDLE state 20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_NEWCALL while at CCH323_RAS_STATE_IDLE state 20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ARQ cch323_ras_receiver:received msg of type ACF_CHOSEN 20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_ACF while at CCH323_RAS_STATE_ARQ state 20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ACTIVE 20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_CALLDISC while at CCH323_RAS_STATE_ACTIVE state 20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_DRQ cch323_ras_receiver:received msg of type DCF_CHOSEN 20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_DCF while at CCH323_RAS_STATE_DRQ state 20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_IDLE 20:59:04:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_IRR while at CCH323_RAS_STATE_ACTIVE state 20:59:04:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ACTIVE


debug cch323 ras Field Descriptions

Field

Description

CCH323_RAS_EVENT_SEND_RRQ

Send RRQ event message.

CCH323_RAS_STATE_IDLE

The global state machine is in the idle state.

CCH323_RAS_STATE_RRQ

The state machine is in the RRQ state. In this state, the gateway is registering with a gatekeeper.

RCF_CHOSEN

A registration confirm message that has been received from a gatekeeper.

CCH323_RAS_EVENT_RCF

Received RCF event message.

CCH323_RAS_EVENT_NEWCALL

New call event.

CCH323_RAS_STATE_ARQ

The per-call state machine is in the process of admitting a new call.


DB-252

May 2008


Table 49

debug cch323 ras Field Descriptions (continued)

Field

Description

ACF_CHOSEN

ACF message that has been received from a gatekeeper.

CCH323_RAS_EVENT_ACF

Received ACF event message.

CCH323_RAS_STATE_ACTIVE

The per-call state machine is in the call active state.

CCH323_RAS_EVENT_CALLDISC

Call disconnect event message.

CCH323_RAS_STATE_DRQ

The per-call state machine is in the process of disengaging an active call.

DCF_CHOSEN

The disengage confirm message that has been received from a gatekeeper.

CCH323_RAS_EVENT_DCF

Received DCF event message.

CCH323_RAS_EVENT_IRR

Send IRR event message.

The debug cch323 Command with the rawmsg Keyword Example

The following is sample output from a typical debug cch323 rawmsg request on a Cisco 3640 router: Router# debug cch323 rawmsg 00:32:04:cch323_h225_progress_ind:raw message is 4 bytes:1E 02 81 88 00:32:22:cch323_h225_release_ind:raw message is 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:32:22:cch323_h225_release_notify:raw message 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

80 bytes:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 is 80 bytes:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

The debug cch323 Command with the session Keyword Examples

Following are two examples of output using the debug cch323 session command and keyword combination. The first example is for a call setup on an originating gateway. The second example is for a call setup on a terminating gateway. The following is sample output from a typical debug cch323 session request for a call setup on an originating gateway: Router# debug cch323 session 00:33:49:cch323_call_setup:gw_id=1, callID=16 00:33:49:cch323_get_new_ccb:ccb (0x81D12D2C) is in use 00:33:49:cch323_call_setup:inserted ccb cch323_get_peer_info:faxrate[21]proto[2]bitmask[10002]t38_inhibit[0]global_fax[0] 00:33:49:Not using Voice Class Codec 00:33:49:cch323_get_peer_info:preffered_codec set to G729IETF with Bytes = 20 00:33:49:cch323_get_peer_info:peer:81FC0D14, peer->voice_peer_tag:12D, ccb:81D12D2C 00:33:49:Call_setup Playout Mode:0,Init 60, Min 40, Max 200 00:33:49:No account/pin number available 00:33:49:cch323_call_setup_normal:for callID 10


DB-253


00:33:49:timer (0x81D130D4)starts - delay (15000) 00:33:49:cch323_ct_main:SOCK 1 Event 0x1 00:33:49:timer(0x81D130D4) stops 00:33:49:Near-end Pref Codecs = G.729 IETF 00:33:49: generic_open_logical_channel:codec is g729 00:33:49:cch323_generic_open_logical_channel:Filling in qosCapability field to 0 00:33:49:timer (0x81D130D4)starts - delay (15000) 00:33:49:cch323_ct_main:SOCK 1 Event 0x1 00:33:49:cch323_ct_main:SOCK 1 Event 0x1 00:33:49: [1]towner_data=0x81D13C88, len=105, msgPtr=0x81D07608 00:33:49:cch323_gw_process_read_socket:received msg for H.225 00:33:49:timer(0x81D130D4) stops 00:33:49:timer (0x81D130D4)starts - delay (180000) 00:33:49:Codec:loc(16), rem(16), Bytes:loc(20), Fwd(20), Rev(20) 00:33:49:cch323_rtp_open_notify: 00:33:50:cch323_ct_main:SOCK 1 Event 0x1 00:33:50: [1]towner_data=0x81D13C88, len=71, msgPtr=0x81F1F2E0 00:33:50:cch323_gw_process_read_socket:received msg for H.225 00:33:50:cch323_caps_ind:cap_modem_proto:0, cap_modem_codec:0, cap_modem_redundancy:0 payload 100 00:33:50:cch323_caps_ind:Load DSP with Negotiated codec(16) g729r8, Bytes=20 00:33:50:cch323_caps_ind:set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE

The following is sample output from a typical debug cch323 session request for a call setup on a terminating gateway: Router# debug cch323 session 00:23:27:cch323_ct_main:SOCK 0 Event 0x1 00:23:27:cch323_ct_main:SOCK 1 Event 0x1 00:23:27: [1]towner_data=0x81F9CA9C, len=179, msgPtr=0x81D15C6C 00:23:27:cch323_gw_process_read_socket:received msg for H.225 00:23:27:cch323_h225_receiver CCB not existing already 00:23:27:cch323_get_new_ccb:ccb (0x81F90184) is in use 00:23:27:cch323_h225_receiver Got a new CCB for call id -2115467564 00:23:27:cch323_h225_setup_ind 00:23:27:Not using Voice Class Codec 00:23:27:cch323_set_peer:peer:81FB3228, peer->voice_peer_tag:12C, ccb:81F90184 00:23:27:Near-end Pref Codecs = G.729 IETF 00:23:27:Codec:loc(16), rem(16), Bytes:loc(20), Fwd(20), Rev(20) 00:23:27:cch323_build_fastStart_cap_response:Retrieved qosCapability of 0 00:23:27:cch323_build_fastStart_cap_response:In Response Filling in qosCapability field to 0 00:23:27:Not using Voice Class Codec


DB-254

May 2008


Related Commands

Command

Description

clear h323 gateway

Clears the H.323 gateway counters.

debug h323-annexg

Displays all pertinent AnnexG messages that have been transmitted and received.

debug voip rawmsg

Displays the raw message owner, length, and pointer.

show h323 gateway

Displays statistics for H.323 gateway messages that have been sent and received and displays the reasons for which H.323 calls have been disconnected.


DB-255

Debug Commands debug ccm-manager

debug ccm-manager To display debugging information about Cisco CallManager, use the debug ccm-manager command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccm-manager {backhaul {errors | events | packets} | config-download {all | errors | events | packets | tone | xml} | errors | events | music-on-hold {errors | events | packets} | packets} no debug ccm-manager

Syntax Description

backhaul

config-download

Enables debugging of the Cisco CallManager backhaul. The keywords are as follows: •

errors—Displays Cisco CallManager backhaul errors.

•

events—Displays Cisco CallManager backhaul events.

•

packets—Displays Cisco CallManager packets.

Enables debugging of the Cisco CallManager configuration download. The keywords are as follows: •

all—Displays all Cisco CallManager configuration parameters.

•

errors—Displays Cisco CallManager configuration errors.

•

events—Displays Cisco CallManager configuration events.

•

packets—Displays Cisco CallManager configuration packets.

•

tone—Displays Cisco CallManager downloaded custom tones.

•

xml—Displays the Cisco CallManager configuration XML parser.

errors

Displays errors related to Cisco CallManager.

events

Displays Cisco CallManager events, such as when the primary Cisco CallManager server fails and control is switched to the backup Cisco CallManager server.

music-on-hold

Displays music on hold (MOH). The keywords are as follows:

packets

•

errors—Displays MOH errors.

•

events—Displays MOH events.

•

packets—Displays MOH packets.

Displays Cisco CallManager packets.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T

This command was introduced for Cisco CallManager Version 3.0 and the Cisco VG200.

12.2(2)XA

This command was implemented on Cisco 2600 series and Cisco 3600 series routers.


DB-256

May 2008


Examples

Release

Modification

12.2(2)XN

Support for enhanced MGCP voice gateway interoperability was added to Cisco CallManager Version 3.1 for the Cisco 2600 series, Cisco 3600 series, and Cisco VG200.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco IAD2420 series.

12.2(15)XJ

The tone keyword was added for the following platforms: Cisco 2610XM, Cisco 611XM, Cisco 2620XM, Cisco 2621XM, Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3640A, Cisco 3660, Cisco 3725, and Cisco 3745.

12.3(4)T

The tone keyword was added.

12.3(14)T

New output was added relating to the SCCP protocol.

12.2SX


The following is sample output from the debug ccm-manager events command: Router# debug ccm-manager events *Feb 28 22:56:05.873: cmapp_mgcpapp_go_down: Setting mgc status to NO_RESPONSE *Feb 28 22:56:05.873: cmapp_host_fsm: New state DOWN for host 0 (172.20.71.38) *Feb 28 22:56:05.873: cmapp_mgr_process_ev_active_host_failed: Active host 0 (172.20.71.38) failed *Feb 28 22:56:05.873: cmapp_mgr_check_hostlist: Active host is 0 (172.20.71.38) *Feb 28 22:56:05.877: cmapp_mgr_switchover: New actv host will be 1 (172.20.71.44) *Feb 28 22:56:05.877: cmapp_host_fsm: Processing event GO_STANDBY for host 0 (172.20.71.38) in state DOWN *Feb 28 22:56:05.877: cmapp_open_new_link: Open link for [0]:172.20.71.38 *Feb 28 22:56:05.877: cmbh_open_tcp_link: Opening TCP link with Rem IP 172.20.71.38, Local IP 172.20.71.19, port 2428 *Feb 28 22:56:05.881: cmapp_open_new_link: Open initiated OK: Host 0 (172.20.71.38), session_id=8186DEE4 *Feb 28 22:56:05.881: cmapp_start_open_link_tmr: Host 0 (172.20.71.38), tmr 0 *Feb 28 22:56:05.881: cmapp_host_fsm: New state STANDBY_OPENING for host 0 (172.20.71.38) *Feb 28 22:56:05.881: cmapp_host_fsm: Processing event GO_ACTIVE for host 1 (172.20.71.44) in state STANDBY_READY *Feb 28 22:56:05.885: cmapp_mgr_send_rehome: new addr=172.20.71.44,port=2427 *Feb 28 22:56:05.885: cmapp_host_fsm: New state REGISTERING for host 1 (172.20.71.44)

You can use the debug ccm-manager config-download tone command to verify the parameters assigned to each locale. The following sample output shows the locale name United Kingdom and lists all the dual-tone parameters for that region: Router# debug ccm-manager config-download tone 00:09:07: cmapp_prefix_process_tag_tones: 00:09:07: cmapp_process_tag_trkLocaleName: region = United Kingdom 00:09:07: cmapp_process_tag_pulse_ratio: pulse ratio = 40 00:09:07: cmapp_process_tag_dtmf_llevel: low frequency level = 65438 00:09:07: cmapp_process_tag_dtmf_hlevel: high frequency level = 65463 00:09:07: cmapp_process_tag_special_oper: operation = uLaw 00:09:07: cmapp_prefix_process_tag_lpig: 00:09:07: cmapp_process_tag_fxs: ignore LPIG for fxs 00:09:07: cmapp_process_tag_fxo: ignore LPIG for fxo


DB-257


00:09:07: cmapp_process_tag_digital: ignore LPIG for digital 00:09:07: cmapp_prefix_process_tag_lpog: 00:09:07: cmapp_process_tag_fxs: ignore LPOG for fxsBoth ports are in service 00:09:07: cmapp_process_tag_fxo: ignore LPOG for fxo 00:09:07: cmapp_process_tag_digital: ignore LPOG for digital 00:09:07: cmapp_prefix_process_tag_tonetable_info: 00:09:07: cmapp_prefix_process_tag_dualtone: TID=[0:CPTONE_BUSY] 00:09:07: cmapp_process_tag_nf: number of frequencies = 1 00:09:07: cmapp_process_tag_dr: direction = 0 00:09:07: cmapp_process_tag_fof: frequency 1 = 400 00:09:07: cmapp_process_tag_fos: frequency 2 = 0 00:09:07: cmapp_process_tag_fot: frequency 3 = 0 00:09:07: cmapp_process_tag_fo4: frequency 4 = 0 00:09:07: cmapp_prefix_process_tag_aof_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -200 00:09:07: cmapp_process_tag_fxo: amplitude of 1st = -200 00:09:07: cmapp_process_tag_digital: amplitude of 1st = -240 00:09:07: cmapp_prefix_process_tag_aos_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 0 00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 0 00:09:07: cmapp_process_tag_digital: amplitude of 2nd = 0 00:09:07: cmapp_prefix_process_tag_aot_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 0 00:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 0 00:09:07: cmapp_process_tag_digital: amplitude of 3rd = 0 00:09:07: cmapp_prefix_process_tag_ao4_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 0 00:09:07: cmapp_process_tag_fxo: amplitude of 4th = 0 00:09:07: cmapp_process_tag_digital: amplitude of 4th = 0 00:09:07: cmapp_process_tag_ontf: frequency 1 on time = 375 00:09:07: cmapp_process_tag_oftf: frequency 1 off time = 375 00:09:07: cmapp_process_tag_onts: frequency 2 on time = 0 00:09:07: cmapp_process_tag_ofts: frequency 2 off time = 0 00:09:07: cmapp_process_tag_ontt: frequency 3 on time = 0 00:09:07: cmapp_process_tag_oftt: frequency 3 off time = 0 00:09:07: cmapp_process_tag_ont4: frequency 4 on time = 0 00:09:07: cmapp_process_tag_oft4: frequency 4 off time = 0 00:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 0 00:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 0 00:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 0 00:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 0 00:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 0 00:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 0 00:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 0 00:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 0 00:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 0 00:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 0 00:09:07: cmapp_prefix_process_tag_dualtone: TID=[1:CPTONE_RING_BACK] 00:09:07: cmapp_process_tag_nf: number of frequencies = 2 00:09:07: cmapp_process_tag_dr: direction = 0 00:09:07: cmapp_process_tag_fof: frequency 1 = 400 00:09:07: cmapp_process_tag_fos: frequency 2 = 450 00:09:07: cmapp_process_tag_fot: frequency 3 = 0 00:09:07: cmapp_process_tag_fo4: frequency 4 = 0 00:09:07: cmapp_prefix_process_tag_aof_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -190 00:09:07: cmapp_process_tag_fxo: amplitude of 1st = -190 00:09:07: cmapp_process_tag_digital: amplitude of 1st = -190 00:09:07: cmapp_prefix_process_tag_aos_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = -190 00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = -190 00:09:07: cmapp_process_tag_digital: amplitude of 2nd = -190


DB-258

May 2008


00:09:07: cmapp_prefix_process_tag_aot_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 0 00:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 0 00:09:07: cmapp_process_tag_digital: amplitude of 3rd = 0 00:09:07: cmapp_prefix_process_tag_ao4_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 0 00:09:07: cmapp_process_tag_fxo: amplitude of 4th = 0 00:09:07: cmapp_process_tag_digital: amplitude of 4th = 0 00:09:07: cmapp_process_tag_ontf: frequency 1 on time = 400 00:09:07: cmapp_process_tag_oftf: frequency 1 off time = 200 00:09:07: cmapp_process_tag_onts: frequency 2 on time = 400 00:09:07: cmapp_process_tag_ofts: frequency 2 off time = 2000 00:09:07: cmapp_process_tag_ontt: frequency 3 on time = 0 00:09:07: cmapp_process_tag_oftt: frequency 3 off time = 0 00:09:07: cmapp_process_tag_ont4: frequency 4 on time = 0 00:09:07: cmapp_process_tag_oft4: frequency 4 off time = 0 00:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 0 00:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 0 00:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 0 00:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 0 00:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 0 00:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 0 00:09:07: cmapp_process_tag_rct1: cadence 1 repeat count = 0 00:09:07: cmapp_process_tag_rct2: cadence 2 repeat count = 0 00:09:07: cmapp_process_tag_rct3: cadence 3 repeat count = 0 00:09:07: cmapp_process_tag_rct4: cadence 4 repeat count = 0 00:09:07: cmapp_prefix_process_tag_dualtone: TID=[2:CPTONE_CONGESTION] 00:09:07: cmapp_process_tag_nf: number of frequencies = 1 00:09:07: cmapp_process_tag_dr: direction = 0 00:09:07: cmapp_process_tag_fof: frequency 1 = 400 00:09:07: cmapp_process_tag_fos: frequency 2 = 0 00:09:07: cmapp_process_tag_fot: frequency 3 = 0 00:09:07: cmapp_process_tag_fo4: frequency 4 = 0 00:09:07: cmapp_prefix_process_tag_aof_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 1st = -200 00:09:07: cmapp_process_tag_fxo: amplitude of 1st = -200 00:09:07: cmapp_process_tag_digital: amplitude of 1st = -200 00:09:07: cmapp_prefix_process_tag_aos_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 2nd = 0 00:09:07: cmapp_process_tag_fxo: amplitude of 2nd = 0 00:09:07: cmapp_process_tag_digital: amplitude of 2nd = 0 00:09:07: cmapp_prefix_process_tag_aot_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 3rd = 0 00:09:07: cmapp_process_tag_fxo: amplitude of 3rd = 0 00:09:07: cmapp_process_tag_digital: amplitude of 3rd = 0 00:09:07: cmapp_prefix_process_tag_ao4_level: 00:09:07: cmapp_process_tag_fxs: amplitude of 4th = 0 00:09:07: cmapp_process_tag_fxo: amplitude of 4th = 0 00:09:07: cmapp_process_tag_digital: amplitude of 4th = 0 00:09:07: cmapp_process_tag_ontf: frequency 1 on time = 400 00:09:07: cmapp_process_tag_oftf: frequency 1 off time = 350 00:09:07: cmapp_process_tag_onts: frequency 2 on time = 225 00:09:07: cmapp_process_tag_ofts: frequency 2 off time = 525 00:09:07: cmapp_process_tag_ontt: frequency 3 on time = 0 00:09:07: cmapp_process_tag_oftt: frequency 3 off time = 0 00:09:07: cmapp_process_tag_ont4: frequency 4 on time = 0 00:09:07: cmapp_process_tag_oft4: frequency 4 off time = 0 00:09:07: cmapp_process_tag_fof2: frequency 1 cadence 2 = 0 00:09:07: cmapp_process_tag_fos2: frequency 2 cadence 2 = 0 00:09:07: cmapp_process_tag_fof3: frequency 1 cadence 3 = 0 00:09:07: cmapp_process_tag_fos3: frequency 2 cadence 3 = 0 00:09:07: cmapp_process_tag_fof4: frequency 1 cadence 4 = 0 00:09:07: cmapp_process_tag_fos4: frequency 2 cadence 4 = 0


DB-259


00:09:07: 00:09:07: 00:09:07: 00:09:07: ! end

cmapp_process_tag_rct1: cmapp_process_tag_rct2: cmapp_process_tag_rct3: cmapp_process_tag_rct4:

cadence cadence cadence cadence

1 2 3 4

repeat repeat repeat repeat

count count count count

= = = =

0 0 0 0

The following is sample output from the debug ccm-manager config-download all command for an error case in which the configuration file cannot be accessed for a Skinny Client Control Protocol (SCCP) download: *Jan 9 07:28:33.499: cmapp_xml_process_timer: *Jan 9 07:28:33.499: cmapp_xml_find_ep_by_name: Checking for ep_name [*] *Jan 9 07:28:33.499: cmapp_xml_exec_fsm: Endpoint is [*] *Jan 9 07:28:33.499: cmapp_xml_exec_fsm: endpoint = * state = CMAPP_XML_FILE_DNLD, event = CMAPP_XML_EVT_FILE_DNLD_TIMER *Jan 9 07:28:33.499: cmapp_xml_file_retry_timer_expired: state = CMAPP_XML_FILE_DNLD, event = CMAPP_XML_EVT_FILE_DNLD_TIMER *Jan 9 07:29:14.499: cmapp_xml_tftp_download_file: Unable to read file tftp://10.6.6.31/Router.cisco.com.cnf.xml, rc=-2 *Jan 9 07:29:14.499: cmapp_xml_get_xml_file: Could not read file tftp://10.6.6.31/Router.cisco.com.cnf.xml, len = 0 *Jan 9 07:29:14.499: cmapp_xml_tftp_download_file: Unable to read file tftp:///Router.cisco.com.cnf.xml, rc=-2 *Jan 9 07:29:14.499: cmapp_xml_get_xml_file: Could not read file tftp:///Router.cisco.com.cnf.xml, len = 0 *Jan 9 07:29:14.499: cmapp_xml_tftp_download_file: Unable to read file tftp:///Router.cisco.com.cnf.xml, rc=-2 *Jan 9 07:29:14.499: cmapp_xml_get_xml_file: Could not read file tftp:///Router.cisco.com.cnf.xml, len = 0 *Jan 9 07:29:14.499: cmapp_xml_exec_fsm: New state = CMAPP_XML_FILE_DNLD, ep = 6544CFA8

The following is sample output from the debug ccm-manager config-download all command for a successful SCCP download: *Jan 9 09:44:45.543: cmapp_sccp_config: *Jan 9 09:44:45.543: cmapp_sccp_reset_curcfg: *Jan 9 09:44:45.543: cmapp_sccp_init_curcfg: *Jan 9 09:44:45.543: cmapp_sccp_download_gw_config_file: *Jan 9 09:44:45.543: cmapp_sccp_get_gw_name: *Jan 9 09:44:45.543: cmapp_sccp_get_gw_name: XML file name generated->SKIGW0C85226910.cnf.xml *Jan 9 09:44:45.543: cmapp_sccp_get_xml_file_via_tftp: *Jan 9 09:44:45.543: cmapp_sccp_tftp_download_file: *Jan 9 09:44:45.543: cmapp_sccp_tftp_get_file_size: *Jan 9 09:44:45.563: cmapp_sccp_get_buffer: *Jan 9 09:44:45.575: cmapp_sccp_tftp_download_file: File (tftp://10.2.6.101/SKIGW0C85226910.cnf.xml) read 8162 bytes *Jan 9 09:44:45.575: cmapp_sccp_get_xml_file_via_tftp: Read file tftp://10.2.6.101/SKIGW0C85226910.cnf.xml, len = 8162 *Jan 9 09:44:45.575: cmapp_parse_gw_xml_file: *Jan 9 09:44:45.579: cmapp_sccp_gw_chardata_handler: ccm found, priority=0


DB-260

May 2008


The following lines show the conversion of XML data into router configuration information for the endpoint: *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan

9 9 9 9 9 9 9 9 9 9

09:44:45.579: 09:44:45.579: 09:44:45.579: 09:44:45.579: 09:44:45.579: 09:44:45.579: 09:44:45.579: 09:44:45.579: 09:44:45.579: 09:44:45.579:

cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler: cmapp_sccp_gw_start_element_handler:

Unit has been set to 1 Subunit has been set to 0 Endpoint has been set to 0 Endpoint has been set to 1 Endpoint has been set to 2 Endpoint has been set to 3 Subunit has been set to 1 Endpoint has been set to 0 Endpoint has been set to 1 Unit has been set to 2

Table 50 describes the significant fields shown in the displays. Table 50

Related Commands

debug ccm-manager Field Descriptions

Field

Description

nn:nn:nn:

Timestamp time in hours (military format), minutes, and seconds that indicates when the Cisco CallManager event occurred.

cmapp_ error message:

The Cisco CallManager routine in which the error event occurred.

LocaleName

Region name, such as United Kingdom.

low frequency level

DTMF low frequency.

high frequency level

DTMF high frequency.

operation

Special operations, such as uLaw.

Command

Description

show ccm-manager

Displays a list of Cisco CallManager servers, their current status, and their availability.


DB-261

Debug Commands debug ccsip all

debug ccsip all To enable all Session Initiation Protocol (SIP)-related debugging, use the debug ccsip all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip all no debug ccsip all

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

12.1(1)T


12.1.(3)T

The output of this command was changed.

12.2(2)XA

Support was added for the Cisco AS5350 and Cisco AS5400 universal gateways.

12.2(2)XB1

This command was implemented on the Cisco AS5850 universal gateway.

12.2(8)T


12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T. Support for the Cisco AS5300 universal access server, Cisco AS5350, Cisco AS5400, and Cisco AS5850 universal gateway is not included in this release.

12.2SX


Usage Guidelines

The debug ccsip all command enables the following SIP debug commands: •

debug ccsip events

•

debug ccsip error

•

debug ccsip states

•

debug ccsip messages

•

debug ccsip calls


DB-262

May 2008


Examples

The following example displays debug output from one side of the call: Router# debug ccsip all All SIP call tracing enabled Router1# *Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_NONE, SUBSTATE_NONE) (STATE_IDLE, SUBSTATE_NONE) *Mar 6 14:10:42: Queued event from SIP SPI : SIPSPI_EV_CC_CALL_SETUP *Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_idle_call_setup *Mar 6 14:10:42: act_idle_call_setup:Not using Voice Class Codec

to

*Mar 6 14:10:42: act_idle_call_setup: preferred_codec set[0] type :g711ulaw bytes: 160 *Mar 6 14:10:42: Queued event from SIP SPI : SIPSPI_EV_CREATE_CONNECTION *Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_IDLE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_CONNECTING) *Mar 6 14:10:42: REQUEST CONNECTION TO IP:166.34.245.231 PORT:5060 *Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_IDLE, SUBSTATE_CONNECTING) to (STATE_IDLE, SUBSTATE_CONNECTING) *Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_idle_connection_created *Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_idle_connection_created: Connid(1) created to 166.34.245.231:5060, local_port 54113 *Mar 6 14:10:42: sipSPIAddLocalContact *Mar 6 14:10:42: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE *Mar 6 14:10:42: CCSIP-SPI-CONTROL: sip_stats_method *Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_IDLE, SUBSTATE_CONNECTING) to (STATE_SENT_INVITE, SUBSTATE_NONE) *Mar 6 14:10:42: Sent: INVITE sip:[email protected];user=phone;phone-context=unknown SIP/2.0 Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: Date: Sat, 06 Mar 1993 19:10:42 GMT Call-ID: [email protected] Cisco-Guid: 2881152943-2184249548-0-483039712 User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Max-Forwards: 6 Timestamp: 731427042 Contact: Expires: 180 Content-Type: application/sdp Content-Length: 137 v=0 o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230 s=SIP Call t=0 0 c=IN IP4 166.34.245.230 m=audio 20208 RTP/AVP 0 *Mar 6 14:10:42: Received: SIP/2.0 100 Trying Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: Date: Mon, 08 Mar 1993 22:36:40 GMT Call-ID: [email protected] Timestamp: 731427042 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Content-Length: 0


DB-263


*Mar 6 14:10:42: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060 *Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_sentinvite_new_message *Mar 6 14:10:42: CCSIP-SPI-CONTROL: sipSPICheckResponse *Mar 6 14:10:42: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 6 14:10:42: Roundtrip delay 4 milliseconds for method INVITE *Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING) *Mar 6 14:10:42: Received: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: Date: Mon, 08 Mar 1993 22:36:40 GMT Call-ID: [email protected] Timestamp: 731427042 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Content-Type: application/sdp Content-Length: 137

to

v=0 o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231 s=SIP Call t=0 0 c=IN IP4 166.34.245.231 m=audio 20038 RTP/AVP 0 *Mar 6 14:10:42: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060 *Mar 6 14:10:42: CCSIP-SPI-CONTROL: act_recdproc_new_message *Mar 6 14:10:42: CCSIP-SPI-CONTROL: sipSPICheckResponse *Mar 6 14:10:42: CCSIP-SPI-CONTROL: sipSPICheckResponse : Updating session description *Mar 6 14:10:42: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 6 14:10:42: Roundtrip delay 8 milliseconds for method INVITE *Mar 6 14:10:42: HandleSIP1xxRinging: SDP MediaTypes negotiation successful! Negotiated Codec : g711ulaw , bytes :160 Inband Alerting : 0 *Mar 6 14:10:42: 0x624CFEF8 : State change from (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_ALERTING) *Mar 6 14:10:46: Received: SIP/2.0 200 OK Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: ;tag=27D3FCA8-C7F Date: Mon, 08 Mar 1993 22:36:40 GMT Call-ID: [email protected] Timestamp: 731427042 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Contact: CSeq: 101 INVITE Content-Type: application/sdp Content-Length: 137 v=0 o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231 s=SIP Call t=0 0 c=IN IP4 166.34.245.231 m=audio 20038 RTP/AVP 0


DB-264

May 2008


*Mar 6 14:10:46: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060 *Mar 6 14:10:46: CCSIP-SPI-CONTROL: act_recdproc_new_message *Mar 6 14:10:46: CCSIP-SPI-CONTROL: sipSPICheckResponse *Mar 6 14:10:46: CCSIP-SPI-CONTROL: sipSPICheckResponse : Updating session description *Mar 6 14:10:46: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 6 14:10:46: Roundtrip delay 3536 milliseconds for method INVITE *Mar 6 14:10:46: CCSIP-SPI-CONTROL: act_recdproc_new_message: SDP MediaTypes negotiation successful! Negotiated Codec : g711ulaw , bytes :160 *Mar 6 14:10:46: CCSIP-SPI-CONTROL: sipSPIReconnectConnection *Mar 6 14:10:46: Queued event from SIP SPI : SIPSPI_EV_RECONNECT_CONNECTION *Mar 6 14:10:46: CCSIP-SPI-CONTROL: recv_200_OK_for_invite *Mar 6 14:10:46: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE *Mar 6 14:10:46: CCSIP-SPI-CONTROL: sip_stats_method *Mar 6 14:10:46: 0x624CFEF8 : State change from (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_ALERTING) to (STATE_ACTIVE, SUBSTATE_NONE) *Mar 6 14:10:46: The Call Setup Information is : Call Control Block (CCB) : 0x624CFEF8 State of The Call : STATE_ACTIVE TCP Sockets Used : NO Calling Number : 3660110 Called Number : 3660210 Negotiated Codec : g711ulaw Source IP Address (Media): 166.34.245.230 Source IP Port (Media): 20208 Destn IP Address (Media): 166.34.245.231 Destn IP Port (Media): 20038 Destn SIP Addr (Control) : 166.34.245.231 Destn SIP Port (Control) : 5060 Destination Name : 166.34.245.231 *Mar 6 14:10:46: HandleUdpReconnection: Udp socket connected for fd: 1 with 166.34.245.231:5060 *Mar 6 14:10:46: Sent: ACK sip:[email protected]:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: ;tag=27D3FCA8-C7F Date: Sat, 06 Mar 1993 19:10:42 GMT Call-ID: [email protected] Max-Forwards: 6 Content-Type: application/sdp Content-Length: 137 CSeq: 101 ACK v=0 o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230 s=SIP Call t=0 0 c=IN IP4 166.34.245.230 m=audio 20208 RTP/AVP 0 *Mar 6 14:10:46: CCSIP-SPI-CONTROL: ccsip_caps_ind *Mar 6 14:10:46: ccsip_caps_ind: Load DSP with codec (5) g711ulaw, Bytes=160 *Mar 6 14:10:46: ccsip_caps_ind: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE *Mar 6 14:10:46: CCSIP-SPI-CONTROL: ccsip_caps_ack *Mar 6 14:10:50: Received: BYE sip:[email protected]:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 166.34.245.231:54835 From: ;tag=27D3FCA8-C7F


DB-265


To: "3660110" Date: Mon, 08 Mar 1993 22:36:44 GMT Call-ID: [email protected] User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Max-Forwards: 6 Timestamp: 731612207 CSeq: 101 BYE Content-Length: 0 *Mar 6 14:10:50: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:54835 *Mar 6 14:10:50: CCSIP-SPI-CONTROL: act_active_new_message *Mar 6 14:10:50: CCSIP-SPI-CONTROL: sact_active_new_message_request *Mar 6 14:10:50: CCSIP-SPI-CONTROL: sip_stats_method *Mar 6 14:10:50: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE *Mar 6 14:10:50: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 6 14:10:50: CCSIP-SPI-CONTROL: sipSPIInitiateCallDisconnect : Initiate call disconnect(16) for outgoing call *Mar 6 14:10:50: 0x624CFEF8 : State change from (STATE_ACTIVE, SUBSTATE_NONE) to (STATE_DISCONNECTING, SUBSTATE_NONE) *Mar 6 14:10:50: Sent: SIP/2.0 200 OK Via: SIP/2.0/UDP 166.34.245.231:54835 From: ;tag=27D3FCA8-C7F To: "3660110" Date: Sat, 06 Mar 1993 19:10:50 GMT Call-ID: [email protected] Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Timestamp: 731612207 Content-Length: 0 CSeq: 101 BYE *Mar *Mar *Mar *Mar *Mar

6 6 6 6 6

14:10:50: Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_DISCONNECT 14:10:50: CCSIP-SPI-CONTROL: act_disconnecting_disconnect 14:10:50: CCSIP-SPI-CONTROL: sipSPICallCleanup 14:10:50: Queued event from SIP SPI : SIPSPI_EV_CLOSE_CONNECTION 14:10:50: CLOSE CONNECTION TO CONNID:1

*Mar 6 14:10:50: sipSPIIcpifUpdate :CallState: 4 Playout: 1755 DiscTime:48305031 ConnTime 48304651 *Mar 6 14:10:50: 0x624CFEF8 : State change from (STATE_DISCONNECTING, SUBSTATE_NONE) (STATE_DEAD, SUBSTATE_NONE) *Mar 6 14:10:50: The Call Setup Information is :

to

Call Control Block (CCB) : 0x624CFEF8 State of The Call : STATE_DEAD TCP Sockets Used : NO Calling Number : 3660110 Called Number : 3660210 Negotiated Codec : g711ulaw Source IP Address (Media): 166.34.245.230 Source IP Port (Media): 20208 Destn IP Address (Media): 166.34.245.231 Destn IP Port (Media): 20038 Destn SIP Addr (Control) : 166.34.245.231 Destn SIP Port (Control) : 5060 Destination Name : 166.34.245.231 *Mar

6 14:10:50: Disconnect Cause (CC) Disconnect Cause (SIP)

: 16 : 200


DB-266

May 2008


*Mar 6 14:10:50: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote port: 5060

The following example displays debut output from the other side of the call: Router# debug ccsip all All SIP call tracing enabled 3660-2# *Mar 8 17:36:40: Received: INVITE sip:[email protected];user=phone;phone-context=unknown SIP/2.0 Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: Date: Sat, 06 Mar 1993 19:10:42 GMT Call-ID: [email protected] Cisco-Guid: 2881152943-2184249548-0-483039712 User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Max-Forwards: 6 Timestamp: 731427042 Contact: Expires: 180 Content-Type: application/sdp Content-Length: 137 v=0 o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230 s=SIP Call t=0 0 c=IN IP4 166.34.245.230 m=audio 20208 RTP/AVP 0 *Mar 8 17:36:40: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:54113 *Mar 8 17:36:40: CCSIP-SPI-CONTROL: sipSPISipIncomingCall *Mar 8 17:36:40: 0x624D8CCC : State change from (STATE_NONE, SUBSTATE_NONE) (STATE_IDLE, SUBSTATE_NONE) *Mar 8 17:36:40: CCSIP-SPI-CONTROL: act_idle_new_message *Mar 8 17:36:40: CCSIP-SPI-CONTROL: sact_idle_new_message_invite *Mar 8 17:36:40: CCSIP-SPI-CONTROL: sip_stats_method *Mar 8 17:36:40: sact_idle_new_message_invite:Not Using Voice Class Codec

to

*Mar 8 17:36:40: sact_idle_new_message_invite: Preferred codec[0] type: g711ulaw Bytes :160 *Mar 8 17:36:40: sact_idle_new_message_invite: Media Negotiation successful for an incoming call *Mar 8 17:36:40: sact_idle_new_message_invite: Negotiated Codec :160 Preferred Codec : g711ulaw, bytes :160 *Mar *Mar *Mar

: g711ulaw, bytes

8 17:36:40: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE 8 17:36:40: CCSIP-SPI-CONTROL: sip_stats_status_code 8 17:36:40: Num of Contact Locations 1 3660110 166.34.245.230 5060

*Mar 8 17:36:40: 0x624D8CCC : State change from (STATE_IDLE, SUBSTATE_NONE) (STATE_RECD_INVITE, SUBSTATE_RECD_INVITE_CALL_SETUP) *Mar 8 17:36:40: Sent: SIP/2.0 100 Trying Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: Date: Mon, 08 Mar 1993 22:36:40 GMT

to


DB-267


Call-ID: [email protected] Timestamp: 731427042 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Content-Length: 0 *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

8 8 8 8 8 8 8 8 8 8

17:36:40: 17:36:40: 17:36:40: 17:36:40: 17:36:40: 17:36:40: 17:36:40: 17:36:40: 17:36:40: 17:36:40:

Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_PROCEEDING CCSIP-SPI-CONTROL: act_recdinvite_proceeding Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_ALERTING CCSIP-SPI-CONTROL: ccsip_caps_ind ccsip_caps_ind: codec(negotiated) = 5(Bytes 160) ccsip_caps_ind: Load DSP with codec (5) g711ulaw, Bytes=160 ccsip_caps_ind: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE CCSIP-SPI-CONTROL: ccsip_caps_ack CCSIP-SPI-CONTROL: act_recdinvite_alerting 180 Ringing with SDP - not likely

*Mar 8 17:36:40: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE *Mar 8 17:36:40: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 8 17:36:40: 0x624D8CCC : State change from (STATE_RECD_INVITE, SUBSTATE_RECD_INVITE_CALL_SETUP) to (STATE_SENT_ALERTING, SUBSTATE_NONE) *Mar 8 17:36:40: Sent: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: Date: Mon, 08 Mar 1993 22:36:40 GMT Call-ID: [email protected] Timestamp: 731427042 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Content-Type: application/sdp Content-Length: 137 v=0 o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231 s=SIP Call t=0 0 c=IN IP4 166.34.245.231 m=audio 20038 RTP/AVP 0 *Mar 8 17:36:44: Queued event From SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_CONNECT *Mar 8 17:36:44: CCSIP-SPI-CONTROL: act_sentalert_connect *Mar 8 17:36:44: sipSPIAddLocalContact *Mar 8 17:36:44: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE *Mar 8 17:36:44: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 8 17:36:44: 0x624D8CCC : State change from (STATE_SENT_ALERTING, SUBSTATE_NONE) (STATE_SENT_SUCCESS, SUBSTATE_NONE) *Mar 8 17:36:44: Sent: SIP/2.0 200 OK Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: ;tag=27D3FCA8-C7F Date: Mon, 08 Mar 1993 22:36:40 GMT Call-ID: [email protected] Timestamp: 731427042 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Contact: CSeq: 101 INVITE Content-Type: application/sdp Content-Length: 137

to

v=0 o=CiscoSystemsSIP-GW-UserAgent 969 7889 IN IP4 166.34.245.231


DB-268

May 2008


s=SIP Call t=0 0 c=IN IP4 166.34.245.231 m=audio 20038 RTP/AVP 0 *Mar 8 17:36:44: Received: ACK sip:[email protected]:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 166.34.245.230:54113 From: "3660110" To: ;tag=27D3FCA8-C7F Date: Sat, 06 Mar 1993 19:10:42 GMT Call-ID: [email protected] Max-Forwards: 6 Content-Type: application/sdp Content-Length: 137 CSeq: 101 ACK v=0 o=CiscoSystemsSIP-GW-UserAgent 1212 283 IN IP4 166.34.245.230 s=SIP Call t=0 0 c=IN IP4 166.34.245.230 m=audio 20208 RTP/AVP 0 *Mar 8 17:36:44: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:54113 *Mar 8 17:36:44: CCSIP-SPI-CONTROL: act_sentsucc_new_message *Mar 8 17:36:44: CCSIP-SPI-CONTROL: sip_stats_method *Mar 8 17:36:44: 0x624D8CCC : State change from (STATE_SENT_SUCCESS, SUBSTATE_NONE) (STATE_ACTIVE, SUBSTATE_NONE) *Mar 8 17:36:44: The Call Setup Information is :

to

Call Control Block (CCB) : 0x624D8CCC State of The Call : STATE_ACTIVE TCP Sockets Used : NO Calling Number : 3660110 Called Number : 3660210 Negotiated Codec : g711ulaw Source IP Address (Media): 166.34.245.231 Source IP Port (Media): 20038 Destn IP Address (Media): 166.34.245.230 Destn IP Port (Media): 20208 Destn SIP Addr (Control) : 166.34.245.230 Destn SIP Port (Control) : 5060 Destination Name : 166.34.245.230 *Mar 8 17:36:47: Queued event From *Mar 8 17:36:47: CCSIP-SPI-CONTROL: *Mar 8 17:36:47: Queued event from *Mar 8 17:36:47: 0x624D8CCC : State (STATE_ACTIVE, SUBSTATE_CONNECTING) *Mar 8 17:36:47: REQUEST CONNECTION

SIP SPI to CCAPI/DNS : SIPSPI_EV_CC_CALL_DISCONNECT act_active_disconnect SIP SPI : SIPSPI_EV_CREATE_CONNECTION change from (STATE_ACTIVE, SUBSTATE_NONE) to TO IP:166.34.245.230 PORT:5060

*Mar 8 17:36:47: 0x624D8CCC : State change from (STATE_ACTIVE, SUBSTATE_CONNECTING) to (STATE_ACTIVE, SUBSTATE_CONNECTING) *Mar 8 17:36:47: CCSIP-SPI-CONTROL: act_active_connection_created *Mar 8 17:36:47: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection *Mar 8 17:36:47: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection: Connid(1) created to 166.34.245.230:5060, local_port 54835 *Mar 8 17:36:47: Queued event from SIP SPI : SIPSPI_EV_SEND_MESSAGE *Mar 8 17:36:47: CCSIP-SPI-CONTROL: sip_stats_method *Mar 8 17:36:47: 0x624D8CCC : State change from (STATE_ACTIVE, SUBSTATE_CONNECTING) to (STATE_DISCONNECTING, SUBSTATE_NONE) *Mar 8 17:36:47: Sent:


DB-269


BYE sip:[email protected]:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 166.34.245.231:54835 From: ;tag=27D3FCA8-C7F To: "3660110" Date: Mon, 08 Mar 1993 22:36:44 GMT Call-ID: [email protected] User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Max-Forwards: 6 Timestamp: 731612207 CSeq: 101 BYE Content-Length: 0

*Mar 8 17:36:47: Received: SIP/2.0 200 OK Via: SIP/2.0/UDP 166.34.245.231:54835 From: ;tag=27D3FCA8-C7F To: "3660110" Date: Sat, 06 Mar 1993 19:10:50 GMT Call-ID: [email protected] Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Timestamp: 731612207 Content-Length: 0 CSeq: 101 BYE

*Mar 8 17:36:47: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:54113 *Mar 8 17:36:47: CCSIP-SPI-CONTROL: act_disconnecting_new_message *Mar 8 17:36:47: CCSIP-SPI-CONTROL: sact_disconnecting_new_message_response *Mar 8 17:36:47: CCSIP-SPI-CONTROL: sipSPICheckResponse *Mar 8 17:36:47: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 8 17:36:47: Roundtrip delay 4 milliseconds for method BYE *Mar *Mar *Mar

8 17:36:47: CCSIP-SPI-CONTROL: sipSPICallCleanup 8 17:36:47: Queued event from SIP SPI : SIPSPI_EV_CLOSE_CONNECTION 8 17:36:47: CLOSE CONNECTION TO CONNID:1

*Mar 8 17:36:47: sipSPIIcpifUpdate :CallState: 4 Playout: 1265 DiscTime:66820800 ConnTime 66820420 *Mar 8 17:36:47: 0x624D8CCC : State change from (STATE_DISCONNECTING, SUBSTATE_NONE) (STATE_DEAD, SUBSTATE_NONE) *Mar 8 17:36:47: The Call Setup Information is :

to

Call Control Block (CCB) : 0x624D8CCC State of The Call : STATE_DEAD TCP Sockets Used : NO Calling Number : 3660110 Called Number : 3660210 Negotiated Codec : g711ulaw Source IP Address (Media): 166.34.245.231 Source IP Port (Media): 20038 Destn IP Address (Media): 166.34.245.230 Destn IP Port (Media): 20208 Destn SIP Addr (Control) : 166.34.245.230 Destn SIP Port (Control) : 5060 Destination Name : 166.34.245.230 *Mar


: 16 : 200


DB-270

May 2008



Related Commands

Command

Description

debug ccsip calls

Shows all SIP SPI call tracing.

debug ccsip error

Shows SIP SPI errors.

debug ccsip events

Shows all SIP SPI events tracing.

debug ccsip info

Shows all SIP SPI message tracing.

debug ccsip states

Shows all SIP SPI state tracing.


DB-271

Debug Commands debug ccsip calls

debug ccsip calls To show all Session Initiation Protocol (SIP) Service Provider Interface (SPI) call tracing, use the debug ccsip calls command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip calls no debug ccsip calls

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

12.1(1)T


12.1(3)T


12.2(2)XA


12.2(2)XB1

This command was introduced on the Cisco AS5850 universal gateway.

12.2(8)T


12.2(11)T


12.2SX


Usage Guidelines

This command traces the SIP call details as they are updated in the SIP call control block.

Examples

The following example displays debug output from one side of the call: Router1# debug ccsip calls SIP Call statistics tracing is enabled Router1# *Mar 6 14:12:33: The Call Setup Information is : Call Control Block (CCB) : 0x624D078C State of The Call : STATE_ACTIVE


DB-272

May 2008


TCP Sockets Used : Calling Number : Called Number : Negotiated Codec : Source IP Address (Media): Source IP Port (Media): Destn IP Address (Media): Destn IP Port (Media): Destn SIP Addr (Control) : Destn SIP Port (Control) : Destination Name : *Mar

NO 3660110 3660210 g711ulaw 166.34.245.230 20644 166.34.245.231 20500 166.34.245.231 5060 166.34.245.231

6 14:12:40: The Call Setup Information is : Call Control Block (CCB) : 0x624D078C State of The Call : STATE_DEAD TCP Sockets Used : NO Calling Number : 3660110 Called Number : 3660210 Negotiated Codec : g711ulaw Source IP Address (Media): 166.34.245.230 Source IP Port (Media): 20644 Destn IP Address (Media): 166.34.245.231 Destn IP Port (Media): 20500 Destn SIP Addr (Control) : 166.34.245.231 Destn SIP Port (Control) : 5060 Destination Name : 166.34.245.231

*Mar


: 16 : 200

The following example displays debug output from the other side of the call: Router2# debug ccsip calls SIP Call statistics tracing is enabled Router2# *Mar 8 17:38:31: The Call Setup Information is : Call Control Block (CCB) : 0x624D9560 State of The Call : STATE_ACTIVE TCP Sockets Used : NO Calling Number : 3660110 Called Number : 3660210 Negotiated Codec : g711ulaw Source IP Address (Media): 166.34.245.231 Source IP Port (Media): 20500 Destn IP Address (Media): 166.34.245.230 Destn IP Port (Media): 20644 Destn SIP Addr (Control) : 166.34.245.230 Destn SIP Port (Control) : 5060 Destination Name : 166.34.245.230 *Mar

8 17:38:38: The Call Setup Information is: Call Control Block (CCB) : 0x624D9560 State of The Call : STATE_DEAD TCP Sockets Used : NO Calling Number : 3660110 Called Number : 3660210 Negotiated Codec : g711ulaw Source IP Address (Media): 166.34.245.231


DB-273


Source IP Port (Media): Destn IP Address (Media): Destn IP Port (Media): Destn SIP Addr (Control) : Destn SIP Port (Control) : Destination Name : *Mar


Related Commands

20500 166.34.245.230 20644 166.34.245.230 5060 166.34.245.230

: 16 : 200

Command

Description

debug ccsip all

Enables all SIP-related debugging.

debug ccsip error


debug ccsip events


debug ccsip info


debug ccsip states



DB-274

May 2008

Debug Commands debug ccsip error

debug ccsip error To show Session Initiation Protocol (SIP) Service Provider Interface (SPI) errors, use the debug ccsip error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip error no debug ccip error

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

12.1(1)T


12.2(2)XA


12.2(2)XB1


12.2(8)T


12.2(11)T


12.2SX


Usage Guidelines

This command traces all error messages generated from errors encountered by the SIP subsystem.

Examples

The following example displays debug output from one side of the call: Router1# debug ccsip error SIP Call error tracing is enabled Router1# *Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_idle_call_setup *Mar 6 14:16:41: act_idle_call_setup:Not using Voice Class Codec *Mar *Mar

6 14:16:41: act_idle_call_setup: preferred_codec set[0] type :g711ulaw bytes: 160 6 14:16:41: REQUEST CONNECTION TO IP:166.34.245.231 PORT:5060


DB-275


*Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_idle_connection_created *Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_idle_connection_created: Connid(1) created to 166.34.245.231:5060, local_port 55674 *Mar 6 14:16:41: sipSPIAddLocalContact *Mar 6 14:16:41: CCSIP-SPI-CONTROL: sip_stats_method *Mar 6 14:16:41: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060 *Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_sentinvite_new_message *Mar 6 14:16:41: CCSIP-SPI-CONTROL: sipSPICheckResponse *Mar 6 14:16:41: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 6 14:16:41: Roundtrip delay 4 milliseconds for method INVITE *Mar 6 14:16:41: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060 *Mar 6 14:16:41: CCSIP-SPI-CONTROL: act_recdproc_new_message *Mar 6 14:16:41: CCSIP-SPI-CONTROL: sipSPICheckResponse *Mar 6 14:16:41: CCSIP-SPI-CONTROL: sipSPICheckResponse : Updating session description *Mar 6 14:16:41: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 6 14:16:41: Roundtrip delay 8 milliseconds for method INVITE *Mar 6 14:16:41: HandleSIP1xxRinging: SDP MediaTypes negotiation successful! Negotiated Codec : g711ulaw , bytes :160 Inband Alerting : 0 *Mar 6 14:16:45: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:5060 *Mar 6 14:16:45: CCSIP-SPI-CONTROL: act_recdproc_new_message *Mar 6 14:16:45: CCSIP-SPI-CONTROL: sipSPICheckResponse *Mar 6 14:16:45: CCSIP-SPI-CONTROL: sipSPICheckResponse : Updating session description *Mar 6 14:16:45: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 6 14:16:45: Roundtrip delay 3844 milliseconds for method INVITE *Mar 6 14:16:45: CCSIP-SPI-CONTROL: act_recdproc_new_message: SDP MediaTypes negotiation successful! Negotiated Codec : g711ulaw , bytes :160 *Mar 6 14:16:45: CCSIP-SPI-CONTROL: sipSPIReconnectConnection *Mar 6 14:16:45: CCSIP-SPI-CONTROL: recv_200_OK_for_invite *Mar 6 14:16:45: CCSIP-SPI-CONTROL: sip_stats_method *Mar 6 14:16:45: HandleUdpReconnection: Udp socket connected for fd: 1 with 166.34.245.231:5060 *Mar 6 14:16:45: CCSIP-SPI-CONTROL: ccsip_caps_ind *Mar 6 14:16:45: ccsip_caps_ind: Load DSP with codec (5) g711ulaw, Bytes=160 *Mar 6 14:16:45: ccsip_caps_ind: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE *Mar 6 14:16:45: CCSIP-SPI-CONTROL: ccsip_caps_ack *Mar 6 14:16:49: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.231:56101 *Mar 6 14:16:49: CCSIP-SPI-CONTROL: act_active_new_message *Mar 6 14:16:49: CCSIP-SPI-CONTROL: sact_active_new_message_request *Mar 6 14:16:49: CCSIP-SPI-CONTROL: sip_stats_method *Mar 6 14:16:49: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 6 14:16:49: CCSIP-SPI-CONTROL: sipSPIInitiateCallDisconnect : Initiate call disconnect(16) for outgoing call *Mar 6 14:16:49: CCSIP-SPI-CONTROL: act_disconnecting_disconnect *Mar 6 14:16:49: CCSIP-SPI-CONTROL: sipSPICallCleanup *Mar 6 14:16:49: CLOSE CONNECTION TO CONNID:1 *Mar 6 14:16:49: sipSPIIcpifUpdate :CallState: 4 Playout: 2945 DiscTime:48340988 ConnTime 48340525 *Mar 6 14:16:49: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote port: 5060


DB-276

May 2008


The following example displays debug output from the other side of the call: Router2# debug ccsip error SIP Call error tracing is enabled Router2# *Mar 8 17:42:39: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:55674 *Mar 8 17:42:39: CCSIP-SPI-CONTROL: sipSPISipIncomingCall *Mar 8 17:42:39: CCSIP-SPI-CONTROL: act_idle_new_message *Mar 8 17:42:39: CCSIP-SPI-CONTROL: sact_idle_new_message_invite *Mar 8 17:42:39: CCSIP-SPI-CONTROL: sip_stats_method *Mar 8 17:42:39: sact_idle_new_message_invite:Not Using Voice Class Codec *Mar 8 17:42:39: sact_idle_new_message_invite: Preferred codec[0] type: g711ulaw Bytes :160 *Mar 8 17:42:39: sact_idle_new_message_invite: Media Negotiation successful for an incoming call *Mar 8 17:42:39: sact_idle_new_message_invite: Negotiated Codec :160 Preferred Codec : g711ulaw, bytes :160

: g711ulaw, bytes

*Mar *Mar

8 17:42:39: CCSIP-SPI-CONTROL: sip_stats_status_code 8 17:42:39: Num of Contact Locations 1 3660110 166.34.245.230 5060

*Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

8 8 8 8 8 8 8 8

17:42:39: 17:42:39: 17:42:39: 17:42:39: 17:42:39: 17:42:39: 17:42:39: 17:42:39:

CCSIP-SPI-CONTROL: act_recdinvite_proceeding CCSIP-SPI-CONTROL: ccsip_caps_ind ccsip_caps_ind: codec(negotiated) = 5(Bytes 160) ccsip_caps_ind: Load DSP with codec (5) g711ulaw, Bytes=160 ccsip_caps_ind: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE CCSIP-SPI-CONTROL: ccsip_caps_ack CCSIP-SPI-CONTROL: act_recdinvite_alerting 180 Ringing with SDP - not likely

*Mar 8 17:42:39: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 8 17:42:42: CCSIP-SPI-CONTROL: act_sentalert_connect *Mar 8 17:42:42: sipSPIAddLocalContact *Mar 8 17:42:42: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 8 17:42:42: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:55674 *Mar 8 17:42:42: CCSIP-SPI-CONTROL: act_sentsucc_new_message *Mar 8 17:42:42: CCSIP-SPI-CONTROL: sip_stats_method *Mar 8 17:42:47: CCSIP-SPI-CONTROL: act_active_disconnect *Mar 8 17:42:47: REQUEST CONNECTION TO IP:166.34.245.230 PORT:5060 *Mar 8 17:42:47: CCSIP-SPI-CONTROL: act_active_connection_created *Mar 8 17:42:47: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection *Mar 8 17:42:47: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection: Connid(1) created to 166.34.245.230:5060, local_port 56101 *Mar 8 17:42:47: CCSIP-SPI-CONTROL: sip_stats_method *Mar 8 17:42:47: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 166.34.245.230:55674 *Mar 8 17:42:47: CCSIP-SPI-CONTROL: act_disconnecting_new_message *Mar 8 17:42:47: CCSIP-SPI-CONTROL: sact_disconnecting_new_message_response *Mar 8 17:42:47: CCSIP-SPI-CONTROL: sipSPICheckResponse *Mar 8 17:42:47: CCSIP-SPI-CONTROL: sip_stats_status_code *Mar 8 17:42:47: Roundtrip delay 0 milliseconds for method BYE *Mar *Mar

8 17:42:47: CCSIP-SPI-CONTROL: sipSPICallCleanup 8 17:42:47: CLOSE CONNECTION TO CONNID:1

*Mar 8 17:42:47: sipSPIIcpifUpdate :CallState: 4 Playout: 1255 DiscTime:66856757 ConnTime 66856294


DB-277



Related Commands

Command

Description

debug ccsip all


debug ccsip calls


debug ccsip events


debug ccsip info


debug ccsip states



DB-278

May 2008

Debug Commands debug ccsip events

debug ccsip events To enable tracing of events that are specific to service provider interface (SPI), use the debug ccsip events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip events no debug ccsip events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

12.1(1)T


12.2(2)XA


12.2(2)XB1

This command was introduced on the Cisco AS5850 universal gateway.

12.2(11)T


12.2(15)T

Much of the information formerly found in the output of the debug ccsip events command is now reported in the output of the debug ccsip info and debug ccsip media commands. The debug ccsip events command now displays only the debugging information specifically related to SIP events.

12.2SX


Usage Guidelines

Note

This command previously traced all events posted to Session Initiation Protocol (SIP) SPI from all interfaces and also provided general SIP SPI information. Beginning with Cisco IOS Release 12.2(15)T, the debug ccsip events command displays only debugging information specifically related to SIP SPI events. Media stream and SIP SPI information is now reported in the debug ccsip media and debug ccsip info command output.

This command is intended for use by Cisco technicians only.


DB-279

Debug Commands debug ccsip events

Examples

The following is sample output from the debug ccsip events command for a Cisco 3660: Router# debug ccsip events SIP Call events tracing is enabled Router# Nov 15 18:20:25.779: Queued event from Nov 15 18:20:25.779: Queued event from Nov 15 18:20:25.783: Queued event from Nov 15 18:20:25.815: Queued event from Nov 15 18:20:25.819: Queued event from Nov 15 18:20:28.339: Queued event from Nov 15 18:20:28.339: Queued event from Nov 15 18:20:50.844: Queued event from Nov 15 18:20:50.844: Queued event from Nov 15 18:20:50.848: Queued event from

Related Commands

SIP SIP SIP SIP SIP SIP SIP SIP SIP SIP

SPI SPI SPI SPI SPI SPI SPI SPI SPI SPI

: : : : : : : : : :

SIPSPI_EV_CC_CALL_SETUP SIPSPI_EV_CREATE_CONNECTION SIPSPI_EV_SEND_MESSAGE SIPSPI_EV_CREATE_CONNECTION SIPSPI_EV_SEND_MESSAGE SIPSPI_EV_CLOSE_CONNECTION SIPSPI_EV_SEND_MESSAGE SIPSPI_EV_CLOSE_CONNECTION SIPSPI_EV_SEND_MESSAGE SIPSPI_EV_CC_CALL_DISCONNECT

Command

Description

debug ccsip all


debug ccsip info

Enables tracing of general SIP SPI information.

debug ccsip media

Enables tracing of SIP call media streams.


DB-280

May 2008

Debug Commands debug ccsip info

debug ccsip info To enable tracing of general service provider interface (SPI) information, use the debug ccsip info command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip info no debug ccsip info

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(15)T


12.2SX


Usage Guidelines

Note

Examples

Beginning in Cisco IOS Release 12.2(15)T, the debug ccsip info command is a separate option that displays general SIP SPI information for debug purposes. In past releases, this output was part of the debug ccsip events command.


The following is sample output from the debug ccsip info command for a Cisco 3660: Router# debug ccsip info SIP Call info tracing is enabled Router# Nov 15 18:19:22.670: ****Adding to UAC table Nov 15 18:19:22.670: adding call id E to table Nov 15 18:19:22.670: CCSIP-SPI-CONTROL: act_idle_call_setup Nov 15 18:19:22.670: act_idle_call_setup:Not using Voice Class Codec Nov 15 18:19:22.670: act_idle_call_setup: preferred_codec set[0] type :g729r8 bytes: 20 Nov 15 18:19:22.670: sipSPICopyPeerDataToCCB: From CLI: Modem NSE payload = 100, Passthrough = 0,Modem relay = 0, Gw-Xid = 1 SPRT latency 200, SPRT Retries = 12, Dict Size = 1024 String Len = 32, Compress dir = 3 Nov 15 18:19:22.670: ****Deleting from UAC table Nov 15 18:19:22.670: ****Adding to UAC table Nov 15 18:19:22.670: sipSPIUsetBillingProfile: sipCallId for billing records = [email protected] Nov 15 18:19:22.674: CCSIP-SPI-CONTROL: act_idle_connection_created Nov 15 18:19:22.674: CCSIP-SPI-CONTROL: act_idle_connection_created: Connid(1) created to 172.18.193.190:5060, local_port 56981


DB-281


Nov 15 18:19:22.674: CCSIP-SPI-CONTROL: sipSPIOutgoingCallSDP Nov 15 18:19:22.674: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, ptime: 10 Nov 15 18:19:22.674: sip_generate_sdp_xcaps_list: Modem Relay disabled. X-cap not needed Nov 15 18:19:22.674: sipSPIAddLocalContact Nov 15 18:19:22.674: sip_stats_method Nov 15 18:19:22.690: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:5060 Nov 15 18:19:22.690: CCSIP-SPI-CONTROL: act_sentinvite_new_message Nov 15 18:19:22.690: CCSIP-SPI-CONTROL: sipSPICheckResponse Nov 15 18:19:22.690: sip_stats_status_code Nov 15 18:19:22.690: Roundtrip delay 16 milliseconds for method INVITE Nov 15 18:19:22.706: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:5060 Nov 15 18:19:22.706: CCSIP-SPI-CONTROL: act_recdproc_new_message Nov 15 18:19:22.706: CCSIP-SPI-CONTROL: sipSPICheckResponse Nov 15 18:19:22.706: sip_stats_status_code Nov 15 18:19:22.706: Roundtrip delay 32 milliseconds for method INVITE Nov 15 18:19:22.706: sipSPIGetSdpBody : Parse incoming session description Nov 15 18:19:22.706: HandleSIP1xxSessionProgress: Content-Disposition received in 18x response:session;handling=required Nov 15 18:19:22.706: sipSPIDoMediaNegotiation: number of m lines is 1 Nov 15 18:19:22.706: sipSPIDoAudioNegotiation: Codec (g729r8) Negotiation Successful on Static Payload Nov 15 18:19:22.706: sipSPIDoPtimeNegotiation: One ptime attribute found - value:10 Nov 15 18:19:22.706: convert_ptime_to_codec_bytes: Values :Codec: g729r8 ptime :10, codecbytes: 20 Nov 15 18:19:22.710: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, ptime: 10 Nov 15 18:19:22.710: sipSPIDoDTMFRelayNegotiation: m-line index 1 Nov 15 18:19:22.710: sipSPIDoDTMFRelayNegotiation: Requested DTMF-RELAY option(s) not found in Preferred DTMF-RELAY option list! Nov 15 18:19:22.710: sip_sdp_get_modem_relay_cap_params: Nov 15 18:19:22.710: sip_sdp_get_modem_relay_cap_params: NSE payload from X-cap = 0 Nov 15 18:19:22.710: sip_do_nse_negotiation: NSE Payload 100 found in SDP Nov 15 18:19:22.710: sip_do_nse_negotiation: Remote NSE payload = local one = 100, Use it Nov 15 18:19:22.710: sip_select_modem_relay_params: X-tmr not present in SDP. Disable modem relay Nov 15 18:19:22.710: sipSPIDoQoSNegotiation - SDP body with media description Nov 15 18:19:22.710: ccsip_process_response_contact_record_route Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_bridge: confID = 4, srcCallID = 14, dstCallID = 13 Nov 15 18:19:22.710: sipSPIUupdateCcCallIds: old src/dest ccCallids: -1/-1, new src/dest ccCallids: 14/13 Nov 15 18:19:22.710: sipSPIUupdateCcCallIds: old streamcallid=-1, new streamcallid=14 Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_caps_ind Nov 15 18:19:22.710: ccsip_get_rtcp_session_parameters: CURRENT VALUES: stream_callid=14, current_seq_num=0x1B1B Nov 15 18:19:22.710: ccsip_get_rtcp_session_parameters: NEW VALUES: stream_callid=14, current_seq_num=0x180C Nov 15 18:19:22.710: ccsip_caps_ind: Load DSP with negotiated codec : g729r8, Bytes=20 Nov 15 18:19:22.710: ccsip_caps_ind: set forking flag to 0x0 Nov 15 18:19:22.710: sipSPISetDTMFRelayMode: set DSP for dtmf-relay = CC_CAP_DTMF_RELAY_INBAND_VOICE_AND_OOB Nov 15 18:19:22.710: sip_set_modem_caps: Negotiation already Done. Set negotiated Modem caps Nov 15 18:19:22.710: sip_set_modem_caps: Modem Relay & Passthru both disabled Nov 15 18:19:22.710: sip_set_modem_caps: nse payload = 100, ptru mode = 0, ptru-codec=0, redundancy=0, xid=0, relay=0, sprt-retry=12, latecncy=200, compres-dir=3, dict=1024, strnlen=32 Nov 15 18:19:22.710: ccsip_caps_ind: Load DSP with codec : g729r8, Bytes=20 Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: ccsip_caps_ack Nov 15 18:19:22.710: ccsip_caps_ack: set forking flag to 0x60FD1EAC Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: act_recdproc_connection_created


DB-282

May 2008


Nov 15 18:19:22.710: CCSIP-SPI-CONTROL: sipSPICheckSocketConnection: Connid(2) created to 172.18.193.190:5060, local_port 51663 Nov 15 18:19:22.714: sip_stats_method Nov 15 18:19:22.722: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:5060 Nov 15 18:19:22.722: CCSIP-SPI-CONTROL: act_recdproc_new_message Nov 15 18:19:22.722: CCSIP-SPI-CONTROL: sipSPICheckResponse Nov 15 18:19:22.722: sip_stats_status_code Nov 15 18:19:22.722: Roundtrip delay 48 milliseconds for method PRACK Nov 15 18:19:24.706: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:5060 Nov 15 18:19:24.706: CCSIP-SPI-CONTROL: act_recdproc_new_message Nov 15 18:19:24.706: CCSIP-SPI-CONTROL: sipSPICheckResponse Nov 15 18:19:24.706: sip_stats_status_code Nov 15 18:19:24.706: Roundtrip delay 2032 milliseconds for method PRACK Nov 15 18:19:24.706: sipSPIGetSdpBody : Parse incoming session description Nov 15 18:19:24.710: CCSIP-SPI-CONTROL: sipSPIUACSessionTimer Nov 15 18:19:24.710: CCSIP-SPI-CONTROL: act_recdproc_continue_200_processing Nov 15 18:19:24.710: CCSIP-SPI-CONTROL: act_recdproc_continue_200_processing: *** This ccb is the parent Nov 15 18:19:24.710: sipSPICompareRespMediaInfo Nov 15 18:19:24.710: sipSPIDoMediaNegotiation: number of m lines is 1 Nov 15 18:19:24.710: sipSPIDoAudioNegotiation: Codec (g729r8) Negotiation Successful on Static Payload Nov 15 18:19:24.710: sipSPIDoPtimeNegotiation: One ptime attribute found - value:10 Nov 15 18:19:24.710: convert_ptime_to_codec_bytes: Values :Codec: g729r8 ptime :10, codecbytes: 20 Nov 15 18:19:24.710: convert_codec_bytes_to_ptime: Values :Codec: g729r8 codecbytes :20, ptime: 10 Nov 15 18:19:24.710: sipSPIDoDTMFRelayNegotiation: m-line index 1 Nov 15 18:19:24.710: sipSPIDoDTMFRelayNegotiation: Requested DTMF-RELAY option(s) not found in Preferred DTMF-RELAY option list! Nov 15 18:19:24.710: sip_sdp_get_modem_relay_cap_params: Nov 15 18:19:24.710: sip_sdp_get_modem_relay_cap_params: NSE payload from X-cap = 0 Nov 15 18:19:24.710: sip_do_nse_negotiation: NSE Payload 100 found in SDP Nov 15 18:19:24.710: sip_do_nse_negotiation: Remote NSE payload = local one = 100, Use it Nov 15 18:19:24.710: sip_select_modem_relay_params: X-tmr not present in SDP. Disable modem relay Nov 15 18:19:24.710: sipSPIProcessMediaChanges Nov 15 18:19:24.710: ccsip_process_response_contact_record_route Nov 15 18:19:24.710: CCSIP-SPI-CONTROL: sipSPIProcess200OKforinvite Nov 15 18:19:24.710: sip_stats_method Nov 15 18:19:24.710: udpsock_close_connect: Socket fd: 1 closed for connid 1 with remote port: 5060 Nov 15 18:19:37.479: HandleUdpSocketReads :Msg enqueued for SPI with IPaddr: 172.18.193.190:52180 Nov 15 18:19:37.483: ****Found CCB in UAC table Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: act_active_new_message Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: sact_active_new_message_request Nov 15 18:19:37.483: sip_stats_method Nov 15 18:19:37.483: sip_stats_status_code Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: sipSPIInitiateCallDisconnect : Initiate call disconnect(16) for outgoing call Nov 15 18:19:37.483: udpsock_close_connect: Socket fd: 2 closed for connid 2 with remote port: 5060 Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: act_disconnecting_disconnect Nov 15 18:19:37.483: CCSIP-SPI-CONTROL: sipSPICallCleanup Nov 15 18:19:37.483: sipSPIIcpifUpdate :CallState: 4 Playout: 10230 DiscTime:1745148 ConnTime 1743871 Nov 15 18:19:37.483: ****Deleting from UAC table Nov 15 18:19:37.483: Removing call id E Nov 15 18:19:37.483: freeing ccb 63330954


DB-283


Related Commands

Command

Description

debug ccsip all


debug ccsip events

Enables tracing of events that are specific to SIP SPI.

debug ccsip media

Enables tracing of SIP call media streams.


DB-284

May 2008

Debug Commands debug ccsip media

debug ccsip media To enable tracing of Session Initiation Protocol (SIP) call media streams, use the debug ccsip media command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip media no debug ccsip media

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(15)T


12.2SX


Usage Guidelines

Note

Examples

Beginning in Cisco IOS Release 12.2(15)T, the debug ccsip media command is a separate option that displays debugging information specific to SIP media stream processing. In past releases, this output was part of the debug ccsip events command.


The following is sample output from the debug ccsip media command for a Cisco 3660: Router# debug ccsip media SIP Call media tracing is enabled Router# Nov 15 18:19:53.835: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49 Nov 15 18:19:53.835: sipSPIReserveRtpPort: reserved port 16500 for stream 1 Nov 15 18:19:53.867: sipSPIReplaceSDP Nov 15 18:19:53.871: sipSPICopySdpInfo Nov 15 18:19:53.871: sipSPIUpdCallWithSdpInfo: Preferred Codec : g729r8, bytes :20 Preferred DTMF relay : inband-voice Preferred NTE payload : 101 Early Media : No Delayed Media : No Bridge Done : No New Media : No DSP DNLD Reqd : No Nov 15 18:19:53.871: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49 Nov 15 18:19:53.871: sipSPIUpdCallWithSdpInfo: M-line Index : 1


DB-285

Debug Commands debug ccsip media

State : STREAM_ADDING (3) Callid : -1 Negotiated Codec : g729r8, bytes :20 Negotiated DTMF relay : inband-voice Negotiated NTE payload : 0 Media Srce Addr/Port : 172.18.195.49:16500 Media Dest Addr/Port : 172.18.193.190:19148 Nov 15 18:19:53.871: sipSPIProcessRtpSessions Nov 15 18:19:53.871: sipSPIAddStream: Adding stream 1 (callid 16) to the VOIP RTP library Nov 15 18:19:53.871: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49 Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: for m-line 1 Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: rtcp_session info laddr = 172.18.195.49, lport = 16500, raddr = 172.18.193.190, rport=19148 Nov 15 18:19:53.871: sipSPIUpdateRtcpSession: No rtp session, creating a new one Nov 15 18:19:53.871: sipSPISetStreamInfo: num_streams = 1 Nov 15 18:19:53.871: sipSPISetStreamInfo: adding stream type 0 from mline 1 Nov 15 18:19:53.871: sipSPISetStreamInfo: caps.stream_count=1, caps.stream[0].stream_type=0x1, caps.stream_list.xmitFunc=voip_rtp_xmit, caps.stream_list.context=0x634F1F2C (gccb) Nov 15 18:19:55.555: sipSPICompareSDP Nov 15 18:19:55.555: sipSPICompareStreams: stream 1 dest_port: old=19148 new=19148 Nov 15 18:19:55.555: sipSPICompareStreams: Flags set for stream 1: RTP_CHANGE=No CAPS_CHANGE=No Nov 15 18:19:55.555: sipSPICompareSDP: Flags set for call: NEW_MEDIA=No DSPDNLD_REQD=No Nov 15 18:19:55.555: sipSPIReplaceSDP Nov 15 18:19:55.555: sipSPICopySdpInfo Nov 15 18:19:55.555: sipSPIUpdCallWithSdpInfo: Preferred Codec : g729r8, bytes :20 Preferred DTMF relay : inband-voice Preferred NTE payload : 101 Early Media : No Delayed Media : No Bridge Done : Yes New Media : No DSP DNLD Reqd : No Nov 15 18:19:55.555: sipSPISetMediaSrcAddr: media src addr for stream 1 = 172.18.195.49 Nov 15 18:19:55.555: sipSPIUpdCallWithSdpInfo: M-line Index : 1 State : STREAM_ACTIVE (3) Callid : 16 Negotiated Codec : g729r8, bytes :20 Negotiated DTMF relay : inband-voice Negotiated NTE payload : 0 Media Srce Addr/Port : 172.18.195.49:16500 Media Dest Addr/Port : 172.18.193.190:19148

Related Commands

Command

Description

debug ccsip all


debug ccsip events

Enables tracing of events that are specific to SIP SPI.

debug ccsip info

Enables tracing of general SIP SPI events.


DB-286

May 2008

Debug Commands debug ccsip messages

debug ccsip messages To show all Session Initiation Protocol (SIP) Service Provider Interface (SPI) message tracing, use the debug ccsip messages command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip messages no debug ccsip messages

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

12.1(1)T


12.1.(3)T


12.2(2)XA


12.2(2)XB1


12.2(8)T

This command was implemented on Cisco 7200 series routers.

12.2(11)T


12.2SX


Usage Guidelines

Examples

This command traces the Session Initiation Protocol (SIP) messages exchanged between the SIP UA client (UAC) and the access server.

The following example shows debug output from one side of the call: Router1# debug ccsip messages SIP Call messages tracing is enabled Router1# *Mar 6 14:19:14: Sent: INVITE sip:[email protected];user=phone;phone-context=unknown SIP/2.0 Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110"


DB-287


To: Date: Sat, 06 Mar 1993 19:19:14 GMT Call-ID: [email protected] Cisco-Guid: 2881152943-2184249568-0-483551624 User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Max-Forwards: 6 Timestamp: 731427554 Contact: Expires: 180 Content-Type: application/sdp Content-Length: 138 v=0 o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230 s=SIP Call t=0 0 c=IN IP4 166.34.245.230 m=audio 20762 RTP/AVP 0 *Mar 6 14:19:14: Received: SIP/2.0 100 Trying Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To: Date: Mon, 08 Mar 1993 22:45:12 GMT Call-ID: [email protected] Timestamp: 731427554 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Content-Length: 0 *Mar 6 14:19:14: Received: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To: Date: Mon, 08 Mar 1993 22:45:12 GMT Call-ID: [email protected] Timestamp: 731427554 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Content-Type: application/sdp Content-Length: 138 v=0 o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231 s=SIP Call t=0 0 c=IN IP4 166.34.245.231 m=audio 20224 RTP/AVP 0 *Mar 6 14:19:16: Received: SIP/2.0 200 OK Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To: ;tag=27DBC6D8-1357 Date: Mon, 08 Mar 1993 22:45:12 GMT Call-ID: [email protected] Timestamp: 731427554 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Contact: CSeq: 101 INVITE Content-Type: application/sdp


DB-288

May 2008


Content-Length: 138 v=0 o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231 s=SIP Call t=0 0 c=IN IP4 166.34.245.231 m=audio 20224 RTP/AVP 0 *Mar 6 14:19:16: Sent: ACK sip:[email protected]:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To: ;tag=27DBC6D8-1357 Date: Sat, 06 Mar 1993 19:19:14 GMT Call-ID: [email protected] Max-Forwards: 6 Content-Type: application/sdp Content-Length: 138 CSeq: 101 ACK v=0 o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230 s=SIP Call t=0 0 c=IN IP4 166.34.245.230 m=audio 20762 RTP/AVP 0 *Mar 6 14:19:19: Received: BYE sip:[email protected]:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 166.34.245.231:53600 From: ;tag=27DBC6D8-1357 To: "3660110" Date: Mon, 08 Mar 1993 22:45:14 GMT Call-ID: [email protected] User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Max-Forwards: 6 Timestamp: 731612717 CSeq: 101 BYE Content-Length: 0 *Mar 6 14:19:19: Sent: SIP/2.0 200 OK Via: SIP/2.0/UDP 166.34.245.231:53600 From: ;tag=27DBC6D8-1357 To: "3660110" Date: Sat, 06 Mar 1993 19:19:19 GMT Call-ID: [email protected] Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Timestamp: 731612717 Content-Length: 0 CSeq: 101 BYE

The following example show debug output from the other side of the call: Router2# debug ccsip messages SIP Call messages tracing is enabled Router2# *Mar 8 17:45:12: Received: INVITE sip:[email protected];user=phone;phone-context=unknown SIP/2.0 Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To:


DB-289


Date: Sat, 06 Mar 1993 19:19:14 GMT Call-ID: [email protected] Cisco-Guid: 2881152943-2184249568-0-483551624 User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Max-Forwards: 6 Timestamp: 731427554 Contact: Expires: 180 Content-Type: application/sdp Content-Length: 138 v=0 o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230 s=SIP Call t=0 0 c=IN IP4 166.34.245.230 m=audio 20762 RTP/AVP 0 *Mar 8 17:45:12: Sent: SIP/2.0 100 Trying Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To: Date: Mon, 08 Mar 1993 22:45:12 GMT Call-ID: [email protected] Timestamp: 731427554 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Content-Length: 0 *Mar 8 17:45:12: Sent: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To: Date: Mon, 08 Mar 1993 22:45:12 GMT Call-ID: [email protected] Timestamp: 731427554 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled CSeq: 101 INVITE Content-Type: application/sdp Content-Length: 138 v=0 o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231 s=SIP Call t=0 0 c=IN IP4 166.34.245.231 m=audio 20224 RTP/AVP 0 *Mar 8 17:45:14: Sent: SIP/2.0 200 OK Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To: ;tag=27DBC6D8-1357 Date: Mon, 08 Mar 1993 22:45:12 GMT Call-ID: [email protected] Timestamp: 731427554 Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Contact: CSeq: 101 INVITE Content-Type: application/sdp Content-Length: 138


DB-290

May 2008


v=0 o=CiscoSystemsSIP-GW-UserAgent 1193 7927 IN IP4 166.34.245.231 s=SIP Call t=0 0 c=IN IP4 166.34.245.231 m=audio 20224 RTP/AVP 0 *Mar 8 17:45:14: Received: ACK sip:[email protected]:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 166.34.245.230:55820 From: "3660110" To: ;tag=27DBC6D8-1357 Date: Sat, 06 Mar 1993 19:19:14 GMT Call-ID: [email protected] Max-Forwards: 6 Content-Type: application/sdp Content-Length: 138 CSeq: 101 ACK v=0 o=CiscoSystemsSIP-GW-UserAgent 5596 7982 IN IP4 166.34.245.230 s=SIP Call t=0 0 c=IN IP4 166.34.245.230 m=audio 20762 RTP/AVP 0 *Mar 8 17:45:17: Sent: BYE sip:[email protected]:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 166.34.245.231:53600 From: ;tag=27DBC6D8-1357 To: "3660110" Date: Mon, 08 Mar 1993 22:45:14 GMT Call-ID: [email protected] User-Agent: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Max-Forwards: 6 Timestamp: 731612717 CSeq: 101 BYE Content-Length: 0 *Mar 8 17:45:17: Received: SIP/2.0 200 OK Via: SIP/2.0/UDP 166.34.245.231:53600 From: ;tag=27DBC6D8-1357 To: "3660110" Date: Sat, 06 Mar 1993 19:19:19 GMT Call-ID: [email protected] Server: Cisco VoIP Gateway/ IOS 12.x/ SIP enabled Timestamp: 731612717 Content-Length: 0 CSeq: 101 BYE

Related Commands

debug ccsip all


debug ccsip calls


debug ccsip error


debug ccsip events


debug ccsip states



DB-291

Debug Commands debug ccsip preauth

debug ccsip preauth To enable diagnostic reporting of authentication, authorization, and accounting (AAA) preauthentication for Session Initiation Protocol (SIP) calls, use the debug ccsip preauth command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip preauth no debug ccsip preauth

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Examples

The following example shows debug output for a single SIP call: Router# debug ccsip preauth SIP Jan Jan Jan

Call preauth tracing is enabled 23 18:43:17.898::Preauth Required 23 18:43:17.898: In sipSPISendPreauthReq for preauth_id = 86515, ccb = 67AF4E10 23 18:43:17.898: Entering rpms_proc_print_preauth_req

Jan 23 18:43:17.898: Request = 0 Jan 23 18:43:17.898: Preauth id = 86515 Jan 23 18:43:17.898: EndPt Type = 1 Jan 23 18:43:17.898: EndPt = 192.168.80.70 Jan 23 18:43:17.898: Resource Service = 1 Jan 23 18:43:17.898: Call_origin = answer Jan 23 18:43:17.898: Call_type = voip Jan 23 18:43:17.898: Calling_num = 2270001 Jan 23 18:43:17.898: Called_num = 1170001 Jan 23 18:43:17.898: Protocol = 1 Jan 23 18:43:17.898:sipSPISendPreauthReq:Created node with preauth_id = 86515, ccb 67AF4E10 , node 6709C280 Jan 23 18:43:17.898:rpms_proc_create_node:Created node with preauth_id = 86515 Jan 23 18:43:17.898:rpms_proc_send_aaa_req:uid got is 466728 Jan 23 18:43:17.902:rpms_proc_preauth_response:Context is for preauth_id 86515, aaa_uid 466728 Jan 23 18:43:17.902:rpms_proc_preauth_response:Deleting Tree node for preauth id 86515 uid 466728


DB-292

May 2008

Debug Commands debug ccsip preauth

Jan 23 18:43:17.902:sipSPIGetNodeForPreauth:Preauth_id=86515 Jan 23 18:43:17.902: ccsip_spi_process_preauth_event:67AF4E10 ccb & 6709C280 node Jan 23 18:43:17.902: In act_preauth_response:67AF4E10 ccb Jan 23 18:43:17.902: act_preauth_response:Deleting node 6709C280 from tree


debug ccsip preauth Field Descriptions

Field

Description

Request


Preauth id


EndPt Type

Call Origin End Point Type—1 for IP address, 2 for Interzone ClearToken (IZCT) value.

EndPt


Resource Service


Call_origin

Answer.

Call_type


Calling_num

Calling Party Number (CLID).

Called_num

Called Party Number (DNIS).

Protocol


function reports



DB-293

Debug Commands debug ccsip states

debug ccsip states To show all Session Initiation Protocol (SIP) Service Provider Interface (SPI) state tracing, use the debug ccsip states command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip states no debug ccsip states

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

12.1(1)T


12.2(2)XA


12.2(2)XB1


12.2(8)T

This command was implemented on Cisco 7200 series routers.

12.2(11)T


12.2SX


Usage Guidelines

This command traces the state machine changes of SIP SPI and displays the state transitions.

Examples

The following example shows all SIP SPI state tracing: Router1# debug ccsip states SIP Call states tracing is enabled Router1# *Jan 2 18:34:37.793:0x6220C634 :State change from (STATE_NONE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_NONE) *Jan 2 18:34:37.797:0x6220C634 :State change from (STATE_IDLE, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_CONNECTING) *Jan 2 18:34:37.797:0x6220C634 :State change from (STATE_IDLE, SUBSTATE_CONNECTING) to (STATE_IDLE, SUBSTATE_CONNECTING)


DB-294

May 2008

Debug Commands debug ccsip states

*Jan 2 18:34:37.801:0x6220C634 :State change from (STATE_IDLE, SUBSTATE_CONNECTING) to (STATE_SENT_INVITE, SUBSTATE_NONE) *Jan 2 18:34:37.809:0x6220C634 :State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING) *Jan 2 18:34:37.853:0x6220C634 :State change from (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_ALERTING) *Jan 2 18:34:38.261:0x6220C634 :State change from (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_ALERTING) to (STATE_ACTIVE, SUBSTATE_NONE) *Jan 2 18:35:09.860:0x6220C634 :State change from (STATE_ACTIVE, SUBSTATE_NONE) to (STATE_DISCONNECTING, SUBSTATE_NONE) *Jan 2 18:35:09.868:0x6220C634 :State change from (STATE_DISCONNECTING, SUBSTATE_NONE) to (STATE_DEAD, SUBSTATE_NONE) *Jan 2 18:28:38.404: Queued event from SIP SPI :SIPSPI_EV_CLOSE_CONNECTION

Related Commands

Command

Description

debug ccsip all


debug ccsip calls


debug ccsip error


debug ccsip events


debug ccsip info



DB-295

Debug Commands debug ccsip transport

debug ccsip transport To enable tracing of the Session Initiation Protocol (SIP) transport handler and the TCP or User Datagram Protocol (UDP) process, use the debug ccsip transport command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccsip transport no debug ccsip transport

Syntax Description


Command Modes

Privileged EXEC

Command History

12.3(8)T


12.2SX


Usage Guidelines

Use the debug ccsip transport command to debug issues related to connection and transport usage and to see the flow of the messages being sent or received.

Examples

The following is sample output from the debug ccsip transport command for a Cisco 3660: Router# debug ccsip transport . . . 1w1d: //18/8E16980D800A/SIP/Transport/sipSPISendInvite: Sending Invite to the transport layer 1w1d: //18/8E16980D800A/SIP/Transport/sipSPIGetSwitchTransportFlag: Return the Global configuration, Switch Transport is TRUE 1w1d: //18/8E16980D800A/SIP/Transport/sipSPITransportSendMessage: msg=0x64082D50, addr=172.18.194.183, port=5060, sentBy_port=0, is_req=1, transport=1, switch=1, callBack=0x614FAB58 1w1d: //18/8E16980D800A/SIP/Transport/sipSPITransportSendMessage: Proceedable for sending msg immediately 1w1d: //18/8E16980D800A/SIP/Transport/sipTransportLogicSendMsg: switch transport is 1 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportGetInterfaceMtuSize: MTU size for remote address 172.18.194.183 is 500 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportVerifyMsgForMTUThreshold: Interface MTU Size 500, Msg Size 1096 1w1d: //18/8E16980D800A/SIP/Transport/sipTransportLogicSendMsg: Switching msg=0x64082D50 transport UDP->TCP 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportSetAgeingTimer: Aging timer initiated for holder=0x64084058,addr=172.18.194.183 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipCreateConnHolder: Created new holder=0x64084058, addr=172.18.194.183 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostRequestConnection: Posting TCP conn create request for addr=172.18.194.183, port=5060, context=0x64128D5C


DB-296

May 2008


1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportSetConnWaitTimer: Wait timer set for connection=0x64129BF4,addr=172.18.194.183, port=5060 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipCreateConnInstance: Created new initiated conn=0x64129BF4, connid=-1, addr=172.18.194.183, port=5060, transport=tcp 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipConnectionManagerProcessConnCreated: gConnTab=0x64128D5C, addr=172.18.194.183, port=5060, connid=1, transport=tcp 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipInstanceHandleConnectionCreated: Moving connection=0x64129BF4, connid=1state to pending 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWConnectionCreated: context=0x64128D5C 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipConnectionManagerProcessConnCreated: gConnTab=0x64128D5C, addr=172.18.194.183, port=5060, connid=1, transport=tcp 1w1d: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportPostSendMessage: Posting send for msg=0x64082D50, addr=172.18.194.183, port=5060, connId=1 for TCP . . .


debug ccsip transport Field Descriptions

Field

Description

Sending Invite to the transport layer

Indicates that the SIP signaling state machine has invoked transport layer operations such as transport arbitration logic and the connection management interface.

switch transport is 1

Indicates that the gateway has been provisioned to enable the transport switching functionality based on the message size. 1 is true and 0 is false.

MTU size for remote address

Indicates that the bound outgoing Ethernet interface that sends the message to the given remote address is configured for an MTU size of the indicated value.

Interface MTU Size 500, Msg Size 1096

Indicates that the size of the message is larger than the size of the MTU; thus transport switching (from UDP to TCP) should be enabled.

Switching msg=... transport UDP->TCP

Indicates that transport switching from UDP to TCP is occurring for the handled message because of the large size of the message.

Aging timer initiated for Indicates that the connection algorithm is started; that is, the counter begins holder to age out the TCP or UDP connection if inactivity occurs. Posting TCP conn create request

Indicates a request for a TCP connection from a lower TCP process.

sipSPITransportSendM Indicates all the transport related attributes that the SIP signaling state essage:msg=0x64082D machine originally gives to the transport layer to send out the message. The 50, addr=...transport=1, attributes are: switch=1, • transport: 1 for UDP; 2 for TCP. callBack=0x614FAB58 • switch (switching transport enabled or disabled for large messages): 1 for enabled; 0 for disabled. Posting send for msg=0x64082D50, addr=...for TCP

Indicates that all transport and connection related operations are complete. The message is sent out on the network targeted to the given address, port, and transport.


DB-297


Related Commands

Command

Description

debug ccsip all


debug ccsip info

Enables tracing of general SIP SPI information.

transport switch

Enables switching between UDP and TCP transport mechanisms globally for large SIP messages.

voice-class sip transport switch

Enables switching between UDP and TCP transport mechanisms for large SIP messages for a specific dial peer.


DB-298

May 2008

Debug Commands debug ccswvoice vo-debug

debug ccswvoice vo-debug To display detailed debugging information related to ccswvoice function calls during call setup and teardown, use the debug ccswvoice vo-debug command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccswvoice vo-debug no debug ccswvoice vo-debug

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(1)MA

This command was introduced on the Cisco MC3810 networking device.

12.0(7)XK

This command was implemented on the Cisco 3600 series router.

12.1(2)T


12.2SX


Usage Guidelines

Use this command when attempting to troubleshoot a Vo call that uses the “cisco-switched” session protocol. This command provides the same information as the debug ccswvoice vo-session command, but includes additional debugging information relating to the calls.

Examples

The following shows sample output from the debug ccswvoice vo-debug command: Router# debug ccswvoice vo-debug 2w2d: ccswvoice: callID 529927 pvcid -1 cid -1 state NULL event O/G SETUP 2w2d: ccswvoice_out_callinit_setup: callID 529927 using pvcid 1 cid 15 2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G INIT event I/C PROC 2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G PROC event I/C ALERTccfrf11_caps_ind: codec(preferred) = 1 2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state O/G ALERT event I/C CONN 2w2d: ccswvoice_bridge_drop: dropping bridge calls src 529927 dst 529926 pvcid 1 cid 15 state ACTIVE 2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state ACTIVE event O/G REL 2w2d: ccswvoice: callID 529927 pvcid 1 cid 15 state RELEASE event I/C RELCOMP 2w2d: ccswvo_store_call_history_entry: cause=10 tcause=10 cause_text=normal call clearing.


DB-299

Debug Commands debug ccswvoice vo-debug

Related Commands

Command

Description

debug ccswvoice vo-session



DB-300

May 2008

Debug Commands debug ccswvoice vofr-debug

debug ccswvoice vofr-debug To display the ccswvoice function calls during call setup and teardown, use the debug ccswvoice vofr-debug command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccswvoice vofr-debug no debug ccswvoice vofr-debug

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)XG

This command was introduced on the Cisco 2600 and Cisco 3600 series routers.

12.0(4)T


12.0(7)XK

This command was implemented on the Cisco MC3810 networking device.

12.1(2)T


12.2SX


Usage Guidelines

Use this command when troubleshooting a VoFR call that uses the “cisco-switched” session protocol. This command provides the same information as the debug ccswvoice vofr-session command, but includes additional debugging information relating to the calls.

Examples

The following shows sample output from the debug ccswvoice vofr-debug command: Router# debug ccswvoice vofr-debug CALL TEARDOWN: 3640_vofr(config-voiceport)# *Mar 1 03:02:08.719:ccswvofr_bridge_drop:dropping bridge calls src 17 dst 16 dlci 100 cid 9 state ACTIVE *Mar 1 03:02:08.727:ccswvofr:callID 17 dlci 100 cid 9 state ACTIVE event O/G REL *Mar 1 03:02:08.735:ccswvofr:callID 17 dlci 100 cid 9 state RELEASE event I/C RELCOMP *Mar 1 03:02:08.735:ccswvofr_store_call_history_entry:cause=22 tcause=22 cause_text=no circuit. 3640_vofr(config-voiceport)# CALL SETUP (outgoing): *Mar 1 03:03:22.651:ccswvofr:callID 23 dlci -1 cid -1 state NULL event O/G SETUP *Mar 1 03:03:22.651:ccswvofr_out_callinit_setup:callID 23 using dlci 100 cid 10 *Mar 1 03:03:22.659:ccswvofr:callID 23 dlci 100 cid 10 state O/G INIT event I/C PROC


DB-301

Debug Commands debug ccswvoice vofr-debug

*Mar 1 03:03:22.667:ccswvofr:callID 23 dlci 100 cid 10 state O/G PROC event I/C CONN ccfrf11_caps_ind:codec(preferred) = 0

Related Commands

Command

Description

debug cch323

Displays the ccfrf11 function calls during call setup and teardown.

debug ccsw voice vo-debug


debug vtsp session



DB-302

May 2008

Debug Commands debug ccswvoice vofr-session

debug ccswvoice vofr-session To display the ccswvoice function calls during call setup and teardown, use the debug ccswvoice vofr-session command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccswvoice vofr-session no debug ccswvoice vofr-session

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)XG

This command was introduced on the Cisco 2600 and Cisco 3600 series routers.

12.0(4)T


12.0(7)XK

This command was implemented on the Cisco MC3810 networking device.

12.1(2)T


12.2SX


Usage Guidelines

Use this command to show the state transitions of the cisco-switched-vofr state machine as a call is processed, and when attempting to troubleshoot a VoFR call that uses the “cisco-switched” session protocol.

Examples

The following shows sample output from the debug ccswvoice vofr-session command: Router# debug ccswvoice vofr-session CALL TEARDOWN: 3640_vofr(config-voiceport)# *Mar 1 02:58:13.203:ccswvofr:callID 14 dlci 100 cid 8 state ACTIVE event O/G REL *Mar 1 02:58:13.215:ccswvofr:callID 14 dlci 100 cid 8 state RELEASE event I/C RELCOMP 3640_vofr(config-voiceport)# CALL SETUP (outgoing): *Mar 1 02:59:46.551:ccswvofr:callID 17 dlci -1 cid -1 state NULL event O/G SETUP *Mar 1 02:59:46.559:ccswvofr:callID 17 dlci 100 cid 9 state O/G INIT event I/C PROC *Mar 1 02:59:46.567:ccswvofr:callID 17 dlci 100 cid 9 state O/G PROC event I/C CONN 3640_vofr(config-voiceport)#


DB-303

Debug Commands debug ccswvoice vofr-session

Related Commands

Command

Description

debug cch323



Displays events that occur during RSVP setup.

debug vtsp session



DB-304

May 2008

Debug Commands debug ccswvoice vo-session

debug ccswvoice vo-session To display the first 10 bytes (including header) of selected VoFR subframes for the interface, use the debug ccswvoice vo-session command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ccswvoice vo-session no debug ccswvoice vo-session

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(1)MA

This command was introduced on the Cisco MC3810 networking device.

12.0(7)XK

This command was implemented on the Cisco 3600 series router.

12.1(2)T


12.2SX


Usage Guidelines

Use this command to show the state transitions of the cisco-switched-vo state machine as a call is processed. This command should be used when attempting to troubleshoot a Vo call that uses the “cisco-switched” session protocol.

Examples

The following shows sample output from the debug ccswvoice vo-session command: Router# debug ccswvoice vo-session 2w2d: 2w2d: 2w2d: 2w2d: 2w2d: 2w2d:

Related Commands

ccswvoice: ccswvoice: ccswvoice: ccswvoice: ccswvoice: ccswvoice:

callID callID callID callID callID callID

529919 529919 529919 529919 529919 529919

pvcid pvcid pvcid pvcid pvcid pvcid

-1 cid -1 state NULL event O/G SETUP 1 cid 11 state O/G INIT event I/C PROC 1 cid 11 state O/G PROC event I/C ALERT 1 cid 11 state O/G ALERT event I/C CONN 1 cid 11 state ACTIVE event O/G REL 1 cid 11 state RELEASE event I/C RELCOMP

Command

Description

debug ccswvoice vo-debug

Displays detailed debugging information related to ccswvoice function calls during call setup and teardown.


DB-305

Debug Commands debug cdapi

debug cdapi To display information about the Call Distributor Application Programming Interface (CDAPI), use the debug cdapi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdapi {detail | events} no debug cdapi {detail | events}

Syntax Description

detail

Displays when applications register or become unregistered with CDAPI, when calls are added or deleted from the CDAPI routing table, and when CDAPI messages are created and freed.

events

Displays the events passing between CDAPI and an application or signalling stack.

Defaults

Debugging output is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(6)T


12.1(5)XM2


12.3(2)T

This command was integrated into Cisco IOS Release 12.3(2)T. This command was enhanced to show V.110 call types.

12.3(4)T

This command was enhanced to show V.120 call types.

12.2(33)SRA


12.2SX


Usage Guidelines

The detail keyword is useful for determining if messages are being lost (or not freed). It is also useful for determining the size of the raw messages passed between CDAPI and other applications to ensure that the correct number of bytes is being passed. The events keyword is useful for determining if certain ISDN messages are not being received by an application and if calls are not being directed to an application. The following bandwidths are supported: •

56 kbps

•

64 kbps


DB-306

May 2008


Examples

The following Media Gateway Control Protocol (MGCP) packet received example shows V.110 call debugging output for the debug cdapi detail command. In this example, the modem is not yet in STEADY_STATE. Router# debug cdapi detail Sep 26 19:12:25.327:MGCP Packet received from 10.0.44.109:2427CRCX 6318 s7/ds1-0/24 MGCP 1.0 C:111 M:nas/data L:b:64, nas/bt:v.110, nas/cdn:234567 R:nas/au, nas/ax,nas/of, nas/crq X:101 Sep 26 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0 Sep 26 19:12:25.327:CDAPI Se7/1:23:cdapi_add_entry_callRoutingTbl() Sep 26 19:12:25.327: Added entry for call 0x7017 for application CSM Sep 26 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, router# Raw Length = 0 Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0 Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959 Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0 Sep 26 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960 Sep 26 19:12:25.331:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 ---> Sep 26 19:12:25.331:200 6318 I:64524608

Alert

Sep 26 19:12:25.339:CDAPI:cdapi_crea router#te_msg():CDAPI Pool Count:959, Raw Length = 0 Sep 26 19:12:25.339:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0 Sep 26 19:12:25.339:CDAPI:cdapi_free_msg():CDAPI Pool Count:960 router# Sep 26 19:12:33.223:MGCP Packet received from 10.0.44.109:2427DLCX 6319 s7/ds1-0/24 MGCP 1.0 Sep 26 19:12:33.223:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = Sep 26 19:12:33.223:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, Raw Length = Sep 26 19:12:33.223:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg Sep 26 19:12:33.223:CDAPI:cdapi_free_msg():CDAPI Pool Count:959 Sep 26 19:12:33.227:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, Raw router# Length = 0 Sep 26 19:12:33.227:CDAPI Se7/1:23:cdapi_del_entry_callRoutingTbl() Sep 26 19:12:33.227: Deleted entry for call 0x7017 Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():CDAPI Pool Count:959 Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg Sep 26 19:12:33.227:CDAPI:cdapi_free_msg():CDAPI Pool Count:960 Sep 26 19:12:33.227:send_mgcp_msg, MGCP Packet sent router#to 10.0.44.109:2427 --->

0 0 = 0x0

= 0x0 = 0x0

Sep 26 19:12:33.227:200 6319 OK

The following partial example shows V.120 call debugging output for the debug cdapi detail command: Router# debug cdapi detail May 14 19:12:25.327:MGCP Packet received from 10.0.44.109:2427CRCX 6318 s7/ds1-0/24 MGCP 1.0 C:111 M:nas/data L:b:64, nas/bt:v.120, nas/cdn:234567 R:nas/au, nas/ax,nas/of, nas/crq


DB-307


X:101 May 14 19:12:25.327:CDAPI:cdapi_create_msg():CDAPI Pool Count:959, Raw Length = 0 May 14 19:12:25.327:CDAPI Se7/1:23:cdapi_add_entry_callRoutingTbl() May 14 19:12:25.327: Added entry for call 0x7017 for application CSM May 14 19:12:25.331:CDAPI:cdapi_create_msg():CDAPI Pool Count:958, router# Raw Length = 0 May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0 May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:959 May 14 19:12:25.331:CDAPI:cdapi_free_msg():Raw Length = 0, freeRaw = 1, Raw Msg = 0x0 May 14 19:12:25.331:CDAPI:cdapi_free_msg():CDAPI Pool Count:960 May 14 19:12:25.331:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 ---> . . .

The following MGCP packet received example shows V.120 call debugging output for the debug cdapi events command: Router# debug cdapi events Sep 26 19:14:39.027:MGCP Packet received from 10.0.44.109:2427CRCX 6322 s7/ds1-0/24 MGCP 1.0 C:111 M:nas/data L:b:64, nas/bt:v.120, nas/cdn:234567 R:nas/au, nas/ax,nas/of, nas/crq X:101 Sep 26 19:14:39.027:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONNECT_IND to CSM call = 0x7017 Sep 26 19:14:39.027: From Appl/Stack = XCSP Sep 26 19:14:39.027: Call Type = V.120 Sep 26 19:14:39.027: B Channel = 23 Sep 26 19:14:39.027: dslId = 0 Sep 26 19:14:39.027: Idb = 0 Sep router#26 19:14:39.027: BChanIdb = 64519A14 Sep 26 19:14:39.027: Handle = 63CB8DF4 Sep 26 19:14:39.027: RPA = 6388506C Sep 26 19:14:39.027: Cause = 0 Sep 26 19:14:39.027: ApplCause = 0 Sep 26 19:14:39.027: ApplSpecData = 0 Sep 26 19:14:39.027: Calling Party Number = Sep 26 19:14:39.027: Called Party Number = 234567 Sep 26 19:14:39.027: Overlap = 0 Sep 26 19:14:39.027:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONNECT_RESP to XCSP call = 0x7017 Sep 26 19:14:39.027: From Appl router#/Stack = CSM Sep 26 19:14:39.027: Call Type = MODEM Sep 26 19:14:39.027: B Channel = 23 Sep 26 19:14:39.027: dslId = 0 Sep 26 19:14:39.027: Idb = 0 Sep 26 19:14:39.027: BChanIdb = 64519A14 Sep 26 19:14:39.027: Handle = 63CB8DF4 Sep 26 19:14:39.027: RPA = 0 Sep 26 19:14:39.027: Cause = 0 Sep 26 19:14:39.027: ApplCause = 0 Sep 26 19:14:39.027: ApplSpecData = 0 Sep 26 19:14:39.027: Overlap = 0 Sep 26 19:14:39.031:send_mgcp_msg, MGCP Pa router#cket sent to 10.0.44.109:2427 ---> Sep 26 19:14:39.031:200 6322 I:64524608

Alert


DB-308

May 2008


Sep 26 19:14:39.039:Se7/0:23 CDAPI:TX -> CDAPI_MSG_CONN_ACT_REQ to XCSP call = 0x7017 Sep 26 19:14:39.039: From Appl/Stack = CSM Sep 26 19:14:39.039: Call Type = MODEM Sep 26 19:14:39.039: B Channel = 23 Sep 26 19:14:39.039: dslId = 0 Sep 26 19:14:39.039: Idb = 0 Sep 26 19:14:39.039: BChanIdb = 64519A14 Sep 26 19:14:39.039: Handle = 63CB8DF4 Sep 26 19:14:39.039: R router#PA = 0 Sep 26 19:14:39.039: Cause = 0 Sep 26 19:14:39.039: ApplCause = 0 Sep 26 19:14:39.039: ApplSpecData = 0 Sep 26 19:14:39.039: Overlap = 0 router# Sep 26 19:14:48.959:MGCP Packet received from 10.0.44.109:2427DLCX 6323 s7/ds1-0/24 MGCP 1.0 Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_DISCONNECT_IND to CSM call = 0x7017 Sep 26 19:14:48.963: From Appl/Stack = XCSP Sep 26 19:14:48.963: Call Type = V.120 Sep 26 19:14:48.963: B Channel = 23 Sep 26 19:14:48.963: dslId = 0 Sep 26 19:14:48.963: Idb = 0 Sep 26 19:14:48.963: BChanIdb = 64519A14 Sep 26 19:14:48.963: Handle = 63CB8DF4 Sep 26 19:14 router#:48.963: RPA = 6388506C Sep 26 19:14:48.963: Cause = 0 Sep 26 19:14:48.963: ApplCause = 0 Sep 26 19:14:48.963: ApplSpecData = 0 Sep 26 19:14:48.963: Overlap = 0 Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_SUBTYPE_RELEASE_REQ to XCSP call = 0x7017 Sep 26 19:14:48.963: From Appl/Stack = CSM Sep 26 19:14:48.963: Call Type = MODEM Sep 26 19:14:48.963: B Channel = 23 Sep 26 19:14:48.963: dslId = 0 Sep 26 19:14:48.963: Idb = 0 Sep 26 19:14:48 router#.963: BChanIdb = 64519A14 Sep 26 19:14:48.963: Handle = 63CB8DF4 Sep 26 19:14:48.963: RPA = 0 Sep 26 19:14:48.963: Cause = 0 Sep 26 19:14:48.963: ApplCause = 1 Sep 26 19:14:48.963: ApplSpecData = 0 Sep 26 19:14:48.963: Overlap = 0 Sep 26 19:14:48.963:Se7/0:23 CDAPI:TX -> CDAPI_MSG_SUBTYPE_REL_COMP_IND to CSM call = 0x7017 Sep 26 19:14:48.963: From Appl/Stack = XCSP Sep 26 19:14:48.963: Call Type = V.120 Sep 26 19:14:48.963: B Channel = 23 Sep 26 19: router#14:48.963: dslId = 0 Sep 26 19:14:48.963: Idb = 0 Sep 26 19:14:48.963: BChanIdb = 64519A14 Sep 26 19:14:48.963: Handle = 63CB8DF4 Sep 26 19:14:48.963: RPA = 6388506C Sep 26 19:14:48.963: Cause = 0 Sep 26 19:14:48.963: ApplCause = 0 Sep 26 19:14:48.963: ApplSpecData = 0 Sep 26 19:14:48.963: Overlap = 0


DB-309


Sep 26 19:14:48.963:send_mgcp_msg, MGCP Packet sent to 10.0.44.109:2427 ---> Sep 26 19:14:48.963:200 6323 OK


Related Commands

debug cdapi Field Descriptions

Field

Description

L:b:64, nas/bt

The bearer type parameter includes v.110 and v.120 for V.110 and V.120 calls.

Call Type

Call types are V.110, V.120, and modem.

Command

Description

debug mgcp packet

Displays the MGCP signaling message received and sent to the called agent.

debug voip rawmsg



DB-310

May 2008

Debug Commands debug cdma pdsn a10 ahdlc

debug cdma pdsn a10 ahdlc To display debug messages for Asynchronous High-Level Data Link Control (AHDLC), use the debug cdma pdsn a10 ahdlc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn a10 ahdlc [errors | events ] no debug cdma pdsn a10 ahdlc [errors | events ]

Syntax Description

errors

(Optional) Displays details of AHDLC packets in error.

events

(Optional) Displays AHDLC events.

Defaults

If the command is entered without any optional keywords, all of the types of debug information are enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XC


12.2(8)BY

Keywords were made optional.

12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn a10 ahdlc command: Router# debug cdma pdsn a10 ahdlc errors ahdlc error packet display debugging is on Router# debug cdma pdsn a10 ahdlc events ahdlc events display debugging is on Router# *Jan 1 00:18:30:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up *Jan 1 00:18:30:*****OPEN AHDLC***** *Jan 1 00:18:30: ahdlc_mgr_channel_create *Jan 1 00:18:30: ahdlc_mgr_allocate_available_channel: *Jan 1 00:18:30:ahdlc:tell h/w open channel 9 from engine 0


DB-311

Debug Commands debug cdma pdsn a10 gre

debug cdma pdsn a10 gre To display debug messages for A10 Generic Routing Encapsulation (GRE) interface errors, events, and packets, use the debug cdma pdsn a10 gre command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn a10 gre [errors | events | packets] [tunnel-key key] no debug cdma pdsn a10 gre [errors | events | packets]

Syntax Description

errors

(Optional) Displays A10 GRE errors.

events

(Optional) Displays A10 GRE events.

packets

(Optional) Displays transmitted or received A10 GRE packets.

tunnel-key key

(Optional) Specifies the GRE key.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.2(8)BY

The tunnel-key keyword was added and the existing keywords were made optional.

12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn a10 gre events tunnel-key command: Router# debug cdma pdsn a10 gre events tunnel-key 1 Router# show debug CDMA: CDMA PDSN A10 GRE events debugging is on for tunnel key 1 PDSN# *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1

04:00:57.847:CDMA-GRE:CDMA-Ix1 (GRE/CDMA) created with src 5.0.0.2 dst 0.0.0.0 04:00:57.847:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1 04:00:59.863:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1 04:00:59.863:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1 04:01:01.879:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1 04:01:01.879:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1


DB-312

May 2008

Debug Commands debug cdma pdsn a10 gre

*Mar *Mar

1 04:01:03.899:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1 1 04:01:03.899:CDMA-GRE:(in) found session 5.0.0.2-4.0.0.1-1


DB-313

Debug Commands debug cdma pdsn a10 ppp

debug cdma pdsn a10 ppp To display debug messages for A10 Point-to-Point protocol (PPP) interface errors, events, and packets, use the debug cdma pdsn a10 ppp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn a10 ppp [errors | events | packets] no debug cdma pdsn a10 ppp [errors | events | packets]

Syntax Description

errors

(Optional) Displays A10 PPP errors.

events

(Optional) Displays A10 PPP events.

packets

(Optional) Displays transmitted or received A10 PPP packets.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.2(8)BY


12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn a10 ppp command: Router# debug cdma pdsn a10 ppp errors CDMA PDSN A10 errors debugging is on Router# debug cdma pdsn a10 ppp events CDMA PDSN A10 events debugging is on Router# debug cdma pdsn a10 ppp packets CDMA PDSN A10 packet debugging is on Router# show debug *Jan 1 00:13:09:CDMA-PPP:create_va tunnel=CDMA-Ix1 virtual-template template=Virtual-Template2 ip_enabled=1 *Jan 1 00:13:09:CDMA-PPP:create_va va=Virtual-Access1 *Jan 1 00:13:09:CDMA-PPP:clone va=Virtual-Access1 subif_state=1 hwidb->state=0 *Jan 1 00:13:09: linestate=1 ppp_lineup=0 *Jan 1 00:13:09:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up *Jan 1 00:13:09:CDMA-PPP:clone va=Virtual-Access1 subif_state=1 hwidb->state=4


DB-314

May 2008

Debug Commands debug cdma pdsn a10 ppp

*Jan *Jan

1 00:13:09: linestate=0 ppp_lineup=0 1 00:13:09:*****OPEN AHDLC*****


DB-315

Debug Commands debug cdma pdsn a11

debug cdma pdsn a11 To display debug messages for A11 interface errors, events, and packets, use the debug cdma pdsn a11 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn a11 [errors | events | packets ] [mnid] no debug cdma pdsn a11 [errors | events | packets ]

Syntax Description

errors

(Optional) Displays A11 protocol errors.

events

(Optional) Displays A11 events.

packets

(Optional) Displays transmitted or received packets.

mnid

(Optional) Specifies the ID of the mobile station.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.2(8)BY

The mnid argument was added and the existing keywords were made optional.

12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn a11 commands: Router# debug cdma pdsn a11 errors CDMA PDSN A11 errors debugging is on Router# show debug 1d21h:CDMA-RP:(in) rp_msgs, code=1, status=0 1d21h:CDMA-RP:(enqueue req) type=1 homeagent=5.0.0.2 coaddr=4.0.0.1 1d21h: id=0xBEF750F0-0xBA53E0F lifetime=65535 1d21h:CDMA-RP:len=8, 00-00-00-00-00-00-00-F1 convert to 00000000000001 (14 digits), type=IMSI 1d21h:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1 1d21h: lifetime=65535 id=BEF750F0-BA53E0F imsi=00000000000001 1d21h:CDMA-RP:(req) rp_req_create, 5.0.0.2-4.0.0.1-1 imsi=00000000000001 1d21h:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=65535


DB-316

May 2008


1d21h:CDMA-RP:(out) setup_rp_out_msg, ha=5.0.0.2 coa=4.0.0.1 key=1 1d21h:%LINK-3-UPDOWN:Interface Virtual-Access2000, changed state to up 1d21h:CDMA-RP:ipmobile_visitor add/delete=1, mn=8.0.2.132, ha=7.0.0.2 1d21h:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access2000, changed state to up Router# debug cdma pdsn a11 packets events Router# show debug CDMA: CDMA PDSN A11 packet debugging is on for mnid 000000000000001 CDMA PDSN A11 events debugging is on for mnid 000000000000001 Router# *Mar 1 03:15:32.507:CDMA-RP:len=8, 01-00-00-00-00-00-00-10 convert to 000000000000001 (15 digits), type=IMSI *Mar 1 03:15:32.511:CDMA-RP:extension type=38, len=0 *Mar 1 03:15:32.511:CDMA-RP:extension type=38, len=0 *Mar 1 03:15:32.511:CDMA-RP:extension type=38, len=0 *Mar 1 03:15:32.511:CDMA-RP:extension type=32, len=20 *Mar 1 03:15:32.511: 00 00 01 00 EE 1F FC 43 0A 7D F9 36 29 C2 BA 28 *Mar 1 03:15:32.511: 5A 64 D5 9C *Mar 1 03:15:32.511:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1 *Mar 1 03:15:32.511: lifetime=1800 id=AF3BFE55-69A109D IMSI=000000000000001 *Mar 1 03:15:32.511:CDMA-RP:(req) rp_req_create, ha=5.0.0.2, coa=4.0.0.1, key=1 IMSI=000000000000001 *Mar 1 03:15:32.511:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=1800 *Mar 1 03:15:32.511:CDMA-RP:(out) Setup RP out message, ha=5.0.0.2 coa=4.0.0.1 key=1 *Mar 1 03:15:38.555:CDMA-RP:simple ip visitor added, mn=9.2.0.1, ha=0.0.0.0 Router# *Mar 1 03:15:54.755:CDMA-RP:len=8, 01-00-00-00-00-00-00-10 convert to 000000000000001 (15 digits), type=IMSI *Mar 1 03:15:54.755:CDMA-RP:extension type=38, len=0 *Mar 1 03:15:54.755:CDMA-RP:extension type=32, len=20 *Mar 1 03:15:54.755: 00 00 01 00 EA 9C C6 4C BA B9 F9 B6 DD C4 19 76 *Mar 1 03:15:54.755: 51 5A 56 45 *Mar 1 03:15:54.755:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1 *Mar 1 03:15:54.755: lifetime=0 id=AF3BFE6B-4616E475 IMSI=000000000000001 *Mar 1 03:15:54.755:CDMA-RP:(req) rp_req_lifetime_zero 5.0.0.2-4.0.0.1-1 *Mar 1 03:15:54.755: IMSI=000000000000001 *Mar 1 03:15:54.755:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=0 *Mar 1 03:15:54.755:CDMA-RP:(out) Setup RP out message, ha=5.0.0.2 coa=4.0.0.1 key=1 Router# debug cdma pdsn a11 event mnid 000000000000001 Router# show debug CDMA: CDMA PDSN A11 events debugging is on for mnid 000000000000001 Router# *Mar 1 03:09:34.339:CDMA-RP:len=8, 01-00-00-00-00-00-00-10 convert to 000000000000001 (15 digits), type=IMSI *Mar 1 03:09:34.339:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1 *Mar 1 03:09:34.339: lifetime=1800 id=AF3BFCEE-DC9FC751 IMSI=000000000000001 *Mar 1 03:09:34.339:CDMA-RP:(req) rp_req_create, ha=5.0.0.2, coa=4.0.0.1, key=1 IMSI=000000000000001 *Mar 1 03:09:34.339:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=1800 *Mar 1 03:09:34.339:CDMA-RP:(out) Setup RP out message, ha=5.0.0.2 coa=4.0.0.1 key=1 *Mar

1 03:09:40.379:CDMA-RP:simple ip visitor added, mn=9.2.0.1, ha=0.0.0.0


DB-317


Router# close the session Router# *Mar 1 03:10:00.575:CDMA-RP:len=8, 01-00-00-00-00-00-00-10 convert to 000000000000001 (15 digits), type=IMSI *Mar 1 03:10:00.575:CDMA-RP:(req) process_rp_req, homeagent=5.0.0.2 coaddr=4.0.0.1 *Mar 1 03:10:00.575: lifetime=0 id=AF3BFD09-18040319 IMSI=000000000000001 *Mar 1 03:10:00.575:CDMA-RP:(req) rp_req_lifetime_zero 5.0.0.2-4.0.0.1-1 *Mar 1 03:10:00.575: IMSI=000000000000001 *Mar 1 03:10:00.575:CDMA-RP:(out) rp_reply session=5.0.0.2-4.0.0.1-1, lifetime=0 *Mar 1 03:10:00.575:CDMA-RP:(out) Setup RP out message, ha=5.0.0.2 coa=4.0.0.1 key=1 Router# debug cdma pdsn a11 packet mnid 000000000000001 Router# show debug CDMA: CDMA PDSN A11 packet debugging is on for mnid 000000000000001 Router# *Mar 1 *Mar 1 *Mar 1 *Mar 1 *Mar 1 *Mar 1

03:13:37.803:CDMA-RP:extension 03:13:37.803:CDMA-RP:extension 03:13:37.803:CDMA-RP:extension 03:13:37.803:CDMA-RP:extension 03:13:37.803: 00 00 01 03:13:37.803: 15 BF 5B

type=38, type=38, type=38, type=32, 00 A8 5B 57

*Mar *Mar *Mar *Mar

03:13:51.575:CDMA-RP:extension 03:13:51.575:CDMA-RP:extension 03:13:51.575: 00 00 01 03:13:51.579: DC 0A B0

type=38, len=0 type=32, len=20 00 58 77 E5 59 67 B5 62 15 17 52 83 6D 5B

1 1 1 1

len=0 len=0 len=0 len=20 30 0D 4E 2B 83 FE 18 C6 9D C2


DB-318

May 2008

Debug Commands debug cdma pdsn accounting flow

debug cdma pdsn accounting flow To display debug messages for accounting flow, use the debug cdma pdsn accounting flow command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn accounting flow no debug cdma pdsn accounting flow

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XC


12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn accounting flow command: Router# debug cdma pdsn accounting flow CDMA PDSN flow based accounting debugging is on pdsn-6500# 01:59:40:CDMA-SM:cdma_pdsn_flow_acct_upstream sess id 1 flow type 0 bytes 100 addr 20.20.20.1 01:59:40:CDMA-SM:cdma_pdsn_flow_acct_downstream sess id 1 flow type 0 bytes 100 addr 20.20.20.1


DB-319

Debug Commands debug cdma pdsn accounting time-of-day

debug cdma pdsn accounting time-of-day To display the timer value, use the debug cdma pdsn accounting time-of-day command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn accounting time-of-day no debug cdma pdsn accounting time-of-day

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn accounting time-of-day command: Router# debug cdma pdsn accounting time-of-day CDMA PDSN accounting time-of-day debugging is on Feb 15 19:13:23.634:CDMA-TOD:Current timer expiring in 22 seconds Feb 15 19:13:24.194:%SYS-5-CONFIG_I:Configured from console by console Router# Feb 15 19:13:45.635:CDMA-TOD:Timer expired...Rearming timer Feb 15 19:13:45.635:CDMA-TOD:Gathering session info Feb 15 19:13:45.635:CDMA-TOD:Found 0 sessions


DB-320

May 2008

Debug Commands debug cdma pdsn accounting

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

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn accounting command: Router# debug cdma pdsn accounting CDMA PDSN accounting debugging is on Router# *Jan 1 00:15:32:CDMA/ACCT:null vaccess in session_start *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[9] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[44] len:[3] 01 Processing Y1 *Jan 1 00:15:32:CDMA/ACCT: Setup airlink record received *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[12] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[41] len:[6] 00 00 00 02 CDMA/ACCT: Processing Y2 *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[9] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[42] len:[3] 12 CDMA/ACCT: Processing Y3 *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1F] len:[17] 30 30 30 30 30 30 30 30 30 30 30 30 30 30 32 Processing A1 *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[12] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[9] len:[6] 04 04 04 05 Processing D3 *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[14] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[10] len:[8] 00 00 04 04 04 05 Processing D4 *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[9] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[44] len:[3] 02 Processing Y1 *Jan 1 00:15:32:CDMA/ACCT: Start airlink record received *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[12]


DB-321

Debug Commands debug cdma pdsn accounting

*Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[41] len:[6] 00 00 00 02 CDMA/ACCT: Processing Y2 *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[9] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[42] len:[3] 13 CDMA/ACCT: Processing Y3 *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[10] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[11] len:[4] 00 02 Processing E1 *Jan 1 00:15:32:CDMA/ACCT: Current Attribute type:0x[1A] len:[10] *Jan 1 00:15:32:CDMA/ACCT: VSA Vid:5535 type:[12] len:[4] 00 F1 Processing F1


DB-322

May 2008

Debug Commands debug cdma pdsn cluster

debug cdma pdsn cluster To display the error messages, event messages, and packets received, use the debug cdma pdsn cluster command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn cluster {message [error | events | packets] redundancy [error | events | packets ]} no debug cdma pdsn cluster {message [error | events | packets] redundancy [error | events | packets ]}

Syntax Description

message

Displays cluster messages for errors, events and packets received.

redundancy

Displays redundancy information for errors, events, and sent or received packets.

error

Displays either cluster or redundancy error messages.

events

Displays either all cluster or all redundancy events.

packets

Displays all transmitted or received cluster or redundancy packets.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.3(4)T


12.2SX


Usage Guidelines

This debug is only allowed on PDSN c6-mz images, and helps to monitor prepaid information.

Examples

The following is sample output from the debug cdma pdsn cluster command: Router# debug cdma pdsn cluster ? message redundancy

Debug PDSN cluster controller messages Debug PDSN cluster controller redundancy


DB-323

Debug Commands debug cdma pdsn ipv6

debug cdma pdsn ipv6 To display IPV6 error or event messages, use the debug cdma pdsn IPV6 command in privileged EXEC mode. To disable debug messages, use the no form of this command. debug cdma pdsn ipv6 no debug cdma pdsn ipv6

Syntax Description

There are no arguments or keywords for this command.

Defaults


Command History

Release

Modification

12.3(14)YX


12.4(11)T


12.2SX


Usage Guidelines

The following example illustrates the debug cdma pdsn ipv6 command: Router# debug cdma pdsn ipv6


DB-324

May 2008

Debug Commands debug cdma pdsn prepaid

debug cdma pdsn prepaid To display debug messages about prepaid flow, use the debug cdma pdsn prepaid command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn prepaid no debug cdma pdsn prepaid

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)BY


12.3(4)T


12.2SX


Usage Guidelines

This debug is only allowed on PDSN c6-mz images, and helps to monitor prepaid information.

Examples

The following is sample output from the debug cdma pdsn prepaid command: Router# debug cdma pdsn prepaid *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.391: 00:09:38.395: 00:09:38.395: 00:09:38.395: 00:09:38.395: 00:09:38.395: 00:09:38.395: 00:09:38.395: 00:09:38.395:

CDMA-PREPAID: Initialized the authorization request CDMA-PREPAID: Added username into A-V list CDMA-PREPAID: Added CLID into A-V list CDMA-PREPAID: Added session id for prepaid CDMA-PREPAID: Added correlation id into A-V list CDMA-PREPAID: Added auth reason for prepaid into A-V list CDMA-PREPAID: Added USER_ID for prepaid CDMA-PREPAID: Added service id for prepaid CDMA-PREPAID: Built prepaid VSAs CDMA-PREPAID: Sent the request to AAA CDMA-PREPAID: Auth_reason: CRB_RSP_PEND_INITIAL_QUOTA CDMA-PREPAID: Received prepaid response: status 2 CDMA-PREPAID: AAA authorised parms being processed CDMA-PREPAID: Attr in Grp Prof: crb-entity-type (0x4B000000) CDMA/PREPAID: AAA_AT_CRB_ENTITY_TYPE (0x4B000000) CDMA/PREPAID: entity type returns 1 CDMA-PREPAID: Attr in Grp Prof: crb-duration (0x4B000000) CDMA/PREPAID: AAA_AT_CRB_DURATION (0x4B000000) CDMA/PREPAID: duration returns 120


DB-325

Debug Commands debug cdma pdsn prepaid

*Mar *Mar *Mar

1 00:09:38.395: CDMA-PREPAID: Retrieved attributes successfully 1 00:09:38.395: CDMA-PREPAID: Reset duration to 120, mn 9.3.0.1 1 00:09:38.395: CDMA-PREPAID: : Started duration timer for 120 sec


DB-326

May 2008

Debug Commands debug cdma pdsn qos

debug cdma pdsn qos To display debug messages about quality of service features, use the debug cdma pdsn qos command in privileged EXEC mode. To disable debug messages, use the no form of this command. debug cdma pdsn qos no debug cdma pdsn qos

Syntax Description

There are no arguments or keywords for this command.

Defaults

There are no default values for this command.

Command History

Release

Modification

12.3(8)XW


12.4(11)T


12.2SX


Examples

There are currently no sample outputs for this command.


DB-327

Debug Commands debug cdma pdsn resource-manager

debug cdma pdsn resource-manager To display debug messages that help you monitor the resource-manager information, use the debug cdma pdsn resource-manager command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn resource-manager [error | events] no debug cdma pdsn resource-manager [error | events]

Syntax Description

errors

Displays Packet Data Service node (PDSN) resource manager errors.

events

Displays PDSN resource manager events.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)BY


12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pds resource-manager command: Router# debug cdma pdsn resource-manager errors events

CDMA PDSN resource manager errors CDMA PDSN resource manager events


DB-328

May 2008

Debug Commands debug cdma pdsn selection

debug cdma pdsn selection To display debug messages for the intelligent Packet Data Serving Node (PDSN) selection feature, use the debug cdma pdsn selection command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn selection {errors | events | packets} no debug cdma pdsn selection {errors | events | packets}

Syntax Description

errors

Displays PDSN selection errors.

events

Displays PDSN selection events.

packets

Displays transmitted or received packets.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn selection command with the keyword events specified: Router# debug cdma pdsn selection events CDMA PDSN Router# 00:27:46: 00:27:46: 00:27:46: 00:27:46: 00:27:46: 00:27:46: 00:27:46: 00:27:46: 00:27:47: 00:27:47: 00:27:47: 00:27:47: 00:27:47: 00:27:47:

selection events debugging is on CDMA-PSL: Message(IN) pdsn 51.4.2.40 interface 70.4.2.40 Keepalive 10 Count 0 Capacity 16000 Weight 0 Hostname 11 7206-PDSN-2 CDMA-PSL: Reset keepalive, pdsn 51.4.2.40 current 10 new 10 CDMA-PSL: Message processed, pdsn 51.4.2.40 tsize 0 pendings 0 CDMA-PSL: Send KEEPALIVE, len 32 CDMA-PSL: Message(OUT) dest 224.0.0.11 Keepalive 10 Count 1 Capacity 16000 Weight 0


DB-329

Debug Commands debug cdma pdsn selection

00:27:47: Hostname 11 7206-PDSN-1 00:27:47: CDMA-PSL: RRQ sent, s=70.4.1.40 (FastEthernet0/1), d=224.0.0.11


DB-330

May 2008

Debug Commands debug cdma pdsn service-selection

debug cdma pdsn service-selection To display debug messages for service selection, use the debug cdma pdsn service-selection command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn service-selection no debug cdma pdsn service-selection

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn service-selection command: Router# debug cdma pdsn service-selection CDMA PDSN service provisioning debugging is on Router# 1d02h:%LINK-3-UPDOWN:Interface Virtual-Access3, changed state to up 1d02h:Vi3 CDMA-SP:user_class=1, ms_ipaddr_req=1, apply_acl=0 1d02h:Vi3 CDMA-SP:Adding simple ip flow, user=bsip, mn=6.0.0.2, 1d02h:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access3, changed state to up


DB-331

Debug Commands debug cdma pdsn session

debug cdma pdsn session To display debug messages for Session Manager errors, events, and packets, use the debug cdma pdsn session command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdma pdsn session [errors | events ] no debug cdma pdsn session [errors | events ]

Syntax Description

errors

(Optional) Displays session protocol errors.

events

(Optional) Displays session events.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XS


12.2(8)BY


12.3(4)T


12.2SX


Examples

The following is sample output from the debug cdma pdsn session command: Router# debug cdma pdsn session events CDMA PDSN session events debugging is on Router# debug cdma pdsn session errors CDMA PDSN session errors debugging is on Router# show debug CDMA: CDMA PDSN session events debugging is on CDMA PDSN session errors debugging is on Router# *Jan 1 00:22:27:CDMA-SM:create_session 5.5.5.5-4.4.4.5-2 *Jan 1 00:22:27:CDMA-SM:create_tunnel 5.5.5.5-4.4.4.5 *Jan 1 00:22:27:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up *Jan 1 00:22:29:CDMA-SM:create_flow mn=0.0.0.0, ha=8.8.8.8 [email protected] *Jan 1 00:22:30:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access1, changed state to up


DB-332

May 2008

Debug Commands debug cdp ip

debug cdp ip To enable debug output for the IP routing information that is carried and processed by the Cisco Discovery Protocol (CDP), use the debug cdp ip command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdp ip no debug cdp ip

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

CDP is a media- and protocol-independent device-discovery protocol that runs on all Cisco routers. You can use the debug cdp ip command to determine the IP network prefixes CDP is advertising and whether CDP is correctly receiving this information from neighboring routers. Use the debug cdp ip command with the debug ip routing command to debug problems that occur when on-demand routing (ODR) routes are not installed in the routing table at a hub router. You can also use the debug cdp ip command with the debug cdp packet and debug cdp adjacency commands along with encapsulation-specific debug commands to debug problems that occur in the receipt of CDP IP information.

Examples

The following is sample output from the debug cdp ip command. This example shows the transmission of IP-specific information in a CDP update. In this case, three network prefixes are being sent, each with a different network mask. Router# debug cdp ip CDP-IP: Writing prefix 172.1.69.232.112/28 CDP-IP: Writing prefix 172.19.89.0/24 CDP-IP: Writing prefix 11.0.0.0/8

In addition to these messages, you might see the following messages: •

This message indicates that CDP is attempting to install the prefix 172.16.1.0/24 into the IP routing table: CDP-IP: Updating prefix 172.16.1.0/24 in routing table

•

This message indicates a protocol error occurred during an attempt to decode an incoming CDP packet: CDP-IP: IP TLV length (3) invalid

•

This message indicates the receipt of the IP prefix 172.16.1.0/24 from a CDP neighbor connected via Ethernet interface 0/0. The neighbor IP address is 10.0.01. CDP-IP: Reading prefix 172.16.1.0/24 source 10.0.0.1 via Ethernet0/0


DB-333

Debug Commands debug cdp ip

Related Commands

Command

Description

debug ip routing

Displays information on RIP routing table updates and route cache updates.


DB-334

May 2008

Debug Commands debug cdp

debug cdp To enable debugging of the Cisco Discovery Protocol (CDP), use the debug cdp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cdp {packets | adjacency | events} no debug cdp {packets | adjacency | events}

Syntax Description

packets

Enables packet-related debugging output.

adjacency

Enables adjacency-related debugging output.

events

Enables output related to error messages, such as detecting a bad checksum.

Command Modes

Privileged EXEC

Usage Guidelines

Use debug cdp commands to display information about CDP packet activity, activity between CDP neighbors, and various CDP events.

Examples

The following is sample output from debug cdp packets, debug cdp adjacency, and debug cdp events commands: Router# debug cdp packets CDP packet info debugging is on Router# debug cdp adjacency CDP neighbor info debugging is on Router# debug cdp events CDP events debugging is on CDP-PA: Packet sent out on Ethernet0 CDP-PA: Packet received from gray.cisco.com on interface Ethernet0 CDP-AD: Deleted table entry for violet.cisco.com, interface Ethernet0 CDP-AD: Interface Ethernet2 coming up CDP-EV: Encapsulation on interface Serial2 failed


DB-335

Debug Commands debug cef

debug cef To enable the display of information about Cisco Express Forwarding events, use the debug cef command in privileged EXEC mode. To disable the display of Cisco Express Forwarding events, use the no form of this command. debug cef {all | assert | background | broker | consistency-check | elog | epoch | fib [attached export | subblock] | hardware {notification | queries} | hash | high-availability | interest | interface | iprm | issu | loadinfo | memory | non-ip | path [extension | list | scope ]] | subtree context | switching background | table | xdr} no debug cef {all | assert | background | broker | consistency-check | elog | epoch | fib [attached export | subblock] | hardware {notification | queries} | hash | high-availability | interest | interface | iprm | issu | loadinfo | memory | non-ip | path [extension | list | scope ]] | subtree context | switching background | table | xdr}

Syntax Description

all

Displays debug messages for all Cisco Express Forwarding events.

assert

Displays debug messages for Cisco Express Forwarding assert events.

background

Displays debug messages for Cisco Express Forwarding background events.

broker

Displays debug messages for Cisco Express Forwarding broker events.

consistency-check

Displays debug messages for Cisco Express Forwarding consistency checker events.

elog

Displays debug messages for Cisco Express Forwarding elog events.

epoch

Displays debug messages for Cisco Express Forwarding epoch events.

fib [attached export | subblock]

Displays debug messages for Cisco Express Forwarding Forwarding Information Base entry events.

hardware {notification | queries}

Displays debug messages for Cisco Express Forwarding hardware API notifications or hardware API queries.

hash

Displays debug messages for Cisco Express Forwarding load-balancing hash algorithms.

high-availability

Displays debug messages for Cisco Express Forwarding high availability events.

interest

Displays debug messages for Cisco Express Forwarding interest list events.

interface

Displays debug messages for Cisco Express Forwarding interface events.

iprm

Displays debug messages for Cisco Express Forwarding IP rewrite manager events. (This keyword is not available in Cisco IOS Release 12.2(33)SRA.)

issu

Displays debug messages for Cisco Express Forwarding In Service Software Upgrade (ISSU) events.


DB-336

May 2008


loadinfo

Displays debug messages for Cisco Express Forwarding loadinfo events.

memory

Displays debug messages for Cisco Express Forwarding memory events.

non-ip

Displays debug messages for Cisco Express Forwarding non-IP entry events.

path [extension | list | scope]

Displays debug messages for Cisco Express Forwarding path events.

subtree context

Displays debug messages for Cisco Express Forwarding subtree context events.

switching background

Displays debug messages for Cisco Express Forwarding switching background events.

table

Displays debug messages for Cisco Express Forwarding table events.

xdr

Displays debug messages for Cisco Express Forwarding External Data Representation (XDR) events.

Defaults

Debugging information about Cisco Express Forwarding events is not displayed.

Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

Examples

Modification

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX


Because debugging output is assigned high priority in the CPU process, you should use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, you should use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

The following is sample output from the debug cef all command: Router# debug cef all 06:23:38: HW-API: Counter poll: Label[label=implicit-null] 06:23:38: HW-API: Counter poll: Label[label=implicit-null]


DB-337


06:23:38: HW-API: Counter poll: Label[label=implicit-null] 06:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-rib-ios scanner' expired, callin g 0x40FA03FC, context 0x00010003) 06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-rib-ios scanner' with delay 60000 06:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-ios-rib scanner' expired, callin g 0x40FA03FC, context 0x00010004) 06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-ios-rib scanner' with delay 60000 06:23:43: FIBbg: Timer 'FIB checkers: IPv6 scan-ios-rib scanner' expired, callin g 0x40FA03FC, context 0x00020004) 06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv6 scan-ios-rib scanner' with delay 60000 06:23:43: FIBbg: Timer 'FIB checkers: IPv4 scan-rp-lc scanner' expired, calling 0x40FA03FC, context 0x00010002) 06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-rp-lc scanner' with d elay 60000 06:23:43: FIBbg: Timer 'FIB checkers: IPv6 scan-rp-lc scanner' expired, calling 0x40FA03FC, context 0x00020002) 06:23:43: FIBbg: Restarting timer 'FIB checkers: IPv6 scan-rp-lc scanner' with d elay 60000 06:23:48: HW-API: Counter poll: Label[label=implicit-null] 06:23:48: HW-API: Counter poll: Label[label=implicit-null] 06:23:48: HW-API: Counter poll: Label[label=implicit-null] 06:23:58: HW-API: Counter poll: Label[label=implicit-null] 06:24:06: FIBtable: IPv4: Event modified, 0.0.0.0/0, vrf Default, 1 path, flags 00420005 06:24:06: FIBpath: Configuring IPv4 path 444B2AB0 from rib (idb=NULL, gw=9.1.41. 1, gw_table=0, rr=1) and host prefix 0.0.0.0 06:24:06: FIBpath: Configured recursive-nexthop 9.1.41.1[0] 444B2AB0 path 06:24:06: FIBfib: [v4-0.0.0.0/0 (44AAC750)] Mod type - null 06:24:06: FIBtable: IPv4: Event up, default, 0.0.0.0/0, vrf Default, 1 path, fla gs 00420005 06:24:06: FIBtable: IPv4: Adding route for 0.0.0.0/0 but route already exists. T rying modify. 06:24:06: FIBpath: Configuring IPv4 path 444B2AA0 from rib (idb=NULL, gw=9.1.41. 1, gw_table=0, rr=1) and host prefix 0.0.0.0sh ip 06:24:06: FIBpath: Configured recursive-nexthop 9.1.41.1[0] 444B2AA0 path 06:24:06: FIBfib: [v4-0.0.0.0/0 (44AAC750)] Mod type - null vrf 06:24:07: FIBbg: Timer 'FIB checkers: IPv4 scan-hw-sw scanner' expired, calling 0x40FA03FC, context 0x00010005) 06:24:07: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-hw-sw scanner' with d elay 60000 06:24:07: FIBbg: Timer 'FIB checkers: IPv4 scan-sw-hw scanner' expired, calling 0x40FA03FC, context 0x00010006) 06:24:07: FIBbg: Restarting timer 'FIB checkers: IPv4 scan-sw-hw scanner' with d elay 60000 Name Default RD Interfaces red 1:1 Ethernet4/0/5


DB-338

May 2008


Related Commands

Command

Description

cef table consistency-check

Enables Cisco Express Forwarding consistency checker table values by type and parameter.

clear cef table

Clears the Cisco Express Forwarding tables.

clear ip cef inconsistency

Clears Cisco Express Forwarding inconsistency statistics and records found by the Cisco Express Forwarding consistency checkers.

debug ip cef table

Enables the collection of events that affect entries in the Cisco Express Forwarding tables.

show cef table consistency-check Displays Cisco Express Forwarding consistency checker table values. show ip cef inconsistency

Displays Cisco Express Forwarding IP prefix inconsistencies.


DB-339

Debug Commands debug cellular driver

debug cellular driver To debug the Cisco IOS driver for the cellular interface, use the debug cellular driver command in EXEC mode. debug cellular slot/wic_slot/port driver {crcdump | errdump | errors}

Syntax Description

slot/wic_slot/port

Numeric values that indicate the router slot, WAN interface card (WIC) slot, and port.

crcdump

CRC error details.

errdump

Other error details.

errors

Errors debugging.

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

12.4(11)XV


12.4(15)T


12.2SX


Usage Guidelines

Use this command for debugging purposes only.

Related Commands

Command

Description

debug cellular messages async

Debugs cellular async.

debug cellular messages data

Prints Cisco IOS data path debug messages.

debug cellular firmware

Displays Cisco IOS firmware information.

debug cellular messages management

Prints management path messages, such as CnS.

debug cellular messages dm

Prints diagnostics monitor (DM) messages from the Qualcomm CDMA chipset.

debug cellular messages virt-con

Redirects the Nios II console driver messages to display them in the Cisco IOS router console environment.


DB-340

May 2008

Debug Commands debug cellular firmware

debug cellular firmware To see the Cisco IOS firmware information, use the debug cellular firmware command in EXEC mode. debug cellular slot/wic_slot/port firmware

Syntax Description

slot/wic_slot/port

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

12.4(11)XV


12.4(15)T


12.2SX



Usage Guidelines


Related Commands

Command

Description





debug cellular driver

Debugs the Cisco IOS driver.








DB-341

Debug Commands debug cellular messages all

debug cellular messages all To print all Cisco IOS driver debug messages, use the debug cellular messages all command in EXEC mode. debug cellular slot/wic_slot/port messages all

Syntax Description

slot/wic_slot/port

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

12.4(11)XV


12.4(15)T


12.2SX



Usage Guidelines


Related Commands

Command

Description
















DB-342

May 2008

Debug Commands debug cellular messages async

debug cellular messages async To debug cellular async, use the debug cellular messages async command in EXEC mode. debug cellular slot/wic_slot/port messages async

Syntax Description

slot/wic_slot/port

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

12.4(11)XV


12.4(15)T


12.2SX



Usage Guidelines


Related Commands

Command

Description

debug cellular messages all

Prints all Cisco IOS driver debug messages.














DB-343

Debug Commands debug cellular messages data

debug cellular messages data To print Cisco IOS data path debug messages, use the debug cellular messages data command in EXEC mode. show cellular slot/wic_slot/port messages data

Syntax Description

slot/wic_slot/port

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

12.4(11)XV


12.4(15)T


12.2SX



Usage Guidelines


Related Commands

Command

Description
















DB-344

May 2008

Debug Commands debug cellular messages dm

debug cellular messages dm To print Diagnostics Monitor (DM) messages from the Qualcomm CDMA chipset, use the debug cellular messages dm command in EXEC mode. debug cellular slot/wic_slot/port messages dm

Syntax Description

slot/wic_slot/port

Command Default

There is no default for this command.

Command Modes

EXEC

Command History

Release

Modification

12.4(11)XV


12.4(15)T


12.2SX



Usage Guidelines


Related Commands

Command

Description
















DB-345

Debug Commands debug cellular messages management

debug cellular messages management To print management path messages, such as CnS, use the debug cellular messages management command in EXEC mode. debug cellular slot/wic_slot/port messages management

Syntax Description

slot/wic_slot/port

Command Default

None

Command Modes

EXEC

Command History

Release

Modification

12.4(11)XV


12.4(15)T


12.2SX



Usage Guidelines


Related Commands

Command

Description














DB-346

May 2008

Debug Commands debug cellular messages virt-con

debug cellular messages virt-con To redirect the Nios II console driver messages to display them in the Cisco IOS router console environment, use the debug cellular virt-con command in EXEC mode. debug cellular slot/wic_slot/port virt-con {clear | disable | dump-data-structs | log | monitor | wrapper-on | wrapper-off}

Syntax Description

slot/wic_slot/port


clear

(Optional) Clears all virtual console debug log messages.

disable

(Optional) Disables virtual console real-time debug monitoring.

dump-data-structurs

(Optional) Dumps virtual console data structures.

log

(Optional) Displays virtual console messages from the debug log.

monitor

(Optional) Enables monitoring of real-time virtual console debug messages.

wrapper-on

(Optional) Disables wraparound for virtual console log messages.

wrapper-off

(Optional) Enables wraparound for virtual console log messages.

Command Default

There is no default for this command.

Command Modes

EXEC

Command History

Release

Modification

12.4(11)XV


12.4(15)T


12.2SX


Usage Guidelines


Related Commands

Command

Description












DB-347

Debug Commands debug cellular messages virt-con

Command

Description






DB-348

May 2008

Debug Commands debug cem ls errors

debug cem ls errors To debug connection errors or null data structures, use the debug cem ls errors command in privileged EXEC mode. To disable this form of debugging, use the no form of this command. debug cem ls errors no debug cem ls errors

Syntax Description


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(33)SRC


Usage Guidelines

Use the show debug command to see debug information.

Examples

The following command turns on CEM local switching error debugging: Router# debug cem ls errors

Related Commands

Command

Description

debug cem ls events

Enables debugging of events relating to CEM local switching.


DB-349

Debug Commands debug cem ls events

debug cem ls events To debug CEM local switching events, use the debug cem ls events command in privileged EXEC mode. To disable this form of debugging, use the no form of this command. debug cem ls events no debug cem ls events

Syntax Description


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(33)SRC


Usage Guidelines

Use the show debug command to see debug information.

Examples

The following command turns on debugging for CEM local switching events. Router# debug cem ls events

Related Commands

Command

Description

debug cem ls errors

Enables debugging of connection errors or null data structures.


DB-350

May 2008

Debug Commands debug ces-conn

debug ces-conn To display information from circuit emulation service (CES) clients, use the debug ces-conn command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ces-conn [all | errors | events] no debug ces-conn

Syntax Description

all

(Optional) Displays all error and event information.

errors

(Optional) Displays only error information.

events

(Optional) Displays only event information.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)XM

This command is supported on Cisco 3600 series routers.

12.2(4)T


12.2SX


Examples

The following example shows debug output for a CES connection: Router# debug ces-conn all CES all debugging is on Router# Router# configure terminal Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)# connect conn1 t1 3/0 1 atm1/0 1/100 Router(config-ces-conn)# exit Router(config)# *Mar 6 18:32:27:CES_CLIENT:vc QoS parameters are PCR = 590, CDV = 5000, CAS_ENABLED = 1,partial fill = 0, multiplier = 8,cbr rate = 64, clock recovery = 0,service_type = 3, error method = 0,sdt_size = 196, billing count = 0 *Mar 6 18:32:27:CES_CLIENT:attempt 1 to activate segment>


DB-351

Debug Commands debug channel events

debug channel events To display processing events on Cisco 7000 series routers that occur on the channel adapter interfaces of all installed adapters, use the debug channel events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug channel events no debug channel events

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T


12.2(33)SRA


12.2SX


Usage Guidelines

This command displays CMCC adapter events that occur on the Channel Interface Processor (CIP) or Channel Port Adapter (CPA) and is useful for diagnosing problems in an IBM channel attach network. It provides an overall picture of the stability of the network. In a stable network, the debug channel events command does not return any information. If the command generates numerous messages, the messages can indicate the possible source of the problems. To observe the statistic message (cip_love_letter) sent every 10 seconds, use the debug channel love command. When configuring or making changes to a router or interface that supports IBM channel attach, enable the debug channel 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 sample output is from the debug channel events command: Router# debug channel events Channel3/0: Channel3/0: Channel3/0: Channel3/0:

cip_reset(), state administratively down cip_reset(), state up sending nodeid sending command for vc 0, CLAW path C700, device C0

The following line indicates that the CIP is being reset to an administrative down state: Channel3/0: cip_reset(), state administratively down

The following line indicates that the CIP is being reset to an administrative up state: Channel3/0: cip_reset(), state up


DB-352

May 2008

Debug Commands debug channel events

The following line indicates that the node ID is being sent to the CIP. This information is the same as the “Local Node” information under the show extended channel slot/port subchannels command. The CIP needs to send this information to the host mainframe. Channel3/0: sending nodeid

The following line indicates that a Common Link Access for Workstations (CLAW) subchannel command is being sent from the Route Processor (RP) to the CIP. The value vc 0 indicates that the CIP will use virtual circuit number 0 with this device. The virtual circuit number also shows up when you use the debug channel packets command. Channel3/0: sending command for vc 0, CLAW path C700, device C0

The following is a sample output that is generated by the debug channel events command when a CMPC+ IP TG connection is activated with the host: 1d05h:Channel4/2:Received route UP for tg (768) 1d05h:Adding STATIC ROUTE for vc:768

The following is a sample output from the debug channel events command when a CMPC+ IP TG connection is deactivated: 1d05h:Channel4/2:Received route DOWN for tg (768) 1d05h:Deleting STATIC ROUTE for vc:768

Related Commands

Command

Description

debug channel ilan

Displays CIP love letter events.

debug channel packets

Displays per-packet debugging output.


DB-353

Debug Commands debug channel ilan

debug channel ilan To display messages relating to configuration and bridging using Cisco Mainframe Channel Connection (CMCC) internal LANs and to help debug source-route bridging (SRB) problems related to CMCC internal LANs, use the debug channel ilan command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug channel ilan no debug channel ilan

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.0(3)


12.2(33)SRA


12.2SX


Usage Guidelines

The debug channel ilan command displays events related to CMCC internal LANs. This command is useful for debugging problems associated with CMCC internal LAN configuration. It is also useful for debugging problems related to SRB packet flows through internal LANs.

Examples

The following is sample output from the debug channel ilan command: Router# debug channel ilan Channel internal LANs debugging is on

The following line indicates that a packet destined for the CMCC via a configured internal MAC adapter configured on an internal LAN was dropped because the Logical Link Control (LLC) end station in Cisco IOS software did not exist: CIP ILAN(Channel3/2-Token): Packet dropped - NULL LLC

The following line indicates that a packet destined for the CMCC via a configured internal MAC adapter configured on an internal LAN was dropped because the CMCC had not yet acknowledged the internal MAC adapter configuration command: Channel3/2: ILAN Token-Ring 3 - CIP internal MAC adapter not acknowledged DMAC(4000.7000.0001) SMAC(0c00.8123.0023)


DB-354

May 2008

Debug Commands debug channel ilan

Related Commands

Command

Description

debug channel events

Displays processing that occurs on the channel adapter interfaces of all installed adapters.

debug source bridge

Displays information about packets and frames transferred across a source-route bridge.


DB-355

Debug Commands debug channel love

debug channel love To display Channel Interface Processor (CIP) love letter events, use the debug channel love command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug channel love no debug channel love

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command displays CIP love letter events (an operating status or configuration message) that occur on the CIP interface processor and is useful for diagnosing problems in an IBM channel attach network. It provides an overall picture of the stability of the network. In a stable network, the debug channel love command returns a statistic message (cip_love_letter) that is sent every 10 seconds. This command is valid for the Cisco 7000 series routers only.

Examples

The following is sample output from the debug channel love command: Router# debug channel love Channel3/1: love letter received, bytes 3308 Channel3/0: love letter received, bytes 3336 cip_love_letter: received ll, but no cip_info

The following line indicates that data was received on the CIP: Channel3/1: love letter received, bytes 3308

The following line indicates that the interface is enabled, but there is no configuration for it. It does not normally indicate a problem, just that the Route Processor (RP) got statistics from the CIP but has no place to store them. cip_love_letter: received ll, but no cip_info

Related Commands

Command

Description

debug channel events

Displays processing that occurs on the channel adapter interfaces of all installed adapters.

debug channel packets

Displays per-packet debugging output.


DB-356

May 2008

Debug Commands debug channel packets

debug channel packets To display per-packet debugging output, use the debug channel packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug channel packets no debug channel packets

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug channel packets command displays all process-level Channel Interface Processor (CIP) packets for both outbound and inbound packets. The output reports information when a packet is received or a transmission is attempted. You will need to disable fast switching and autonomous switching to obtain debugging output. This command is useful for determining whether packets are received or sent correctly. This command is valid for the Cisco 7000 series routers only.

Examples

The following is sample output from the debug channel packets command: Router# debug channel packets (Channel3/0)-out size = 104, vc = 0000, type = 0800, src 172.24.0.11, dst 172.24.1.58 (Channel3/0)-in size = 48, vc = 0000, type = 0800, src 172.24.1.58, dst 172.24.15.197 (Channel3/0)-in size = 48, vc = 0000, type = 0800, src 172.24.1.58, dst 172.24.15.197 (Channel3/0)-out size = 71, vc = 0000, type = 0800, src 172.24.15.197, dst 172.24.1.58 (Channel3/0)-in size = 44, vc = 0000, type = 0800, src 172.24.1.58, dst 172.24.15.197


debug channel packets Field Descriptions

Field

Description

(Channel3/0)

Interface slot and port.

in/out

“In” is a packet from the mainframe to the router. “Out” is a packet from the router to the mainframe.

size =

Number of bytes in the packet, including internal overhead.

vc =

Value from 0 to 511 that maps to the claw interface configuration command. This information is from the MAC layer.

type =

Encapsulation type in the MAC layer. The value 0800 indicates an IP datagram.

src

Origin, or source, of the packet, as opposed to the previous hop address.

dst

Destination of the packet, as opposed to the next-hop address.


DB-357

Debug Commands debug clns esis events

debug clns esis events To display uncommon End System-to-Intermediate System (ES-IS) events, including previously unknown neighbors, neighbors that have aged out, and neighbors that have changed roles (ES-IS, for example), use the debug clns esis events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug clns esis events no debug clns esis events

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug clns esis events command: Router# debug clns esis events ES-IS: ISH from aa00.0400.2c05 (Ethernet1), HT 30 ES-IS: ESH from aa00.0400.9105 (Ethernet1), HT 150 ES-IS: ISH sent to All ESs (Ethernet1): NET 49.0001.AA00.0400.6904.00, HT 299, HLEN 20

The following line indicates that the router received a hello packet (ISH) from the IS at MAC address aa00.0400.2c05 on Ethernet interface 1. The hold time (or number of seconds to consider this packet valid before deleting it) for this packet is 30 seconds. ES-IS: ISH from aa00.0400.2c05 (Ethernet1), HT 30

The following line indicates that the router received a hello packet (ESH) from the ES at MAC address aa00.0400.9105 on the Ethernet interface 1. The hold time is 150 seconds. ES-IS: ESH from aa00.0400.9105 (Ethernet1), HT 150

The following line indicates that the router sent an IS hello packet on the Ethernet interface 0 to all ESs on the network. The network entity title (NET) address of the router is 49.0001.0400.AA00.6904.00; the hold time for this packet is 299 seconds; and the header length of this packet is 20 bytes. ES-IS: ISH sent to All ESs (Ethernet1): NET 49.0001.AA00.0400.6904.00, HT 299, HLEN 20


DB-358

May 2008

Debug Commands debug clns esis packets

debug clns esis packets To enable display information on End System-to-Intermediate System (ES-IS) packets that the router has received and sent, use the debug clns esis packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug clns esis packets no debug clns esis packets

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug clns esis packets command: Router# debug clns esis packets ES-IS: ISH sent to All ESs (Ethernet0): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 33 ES-IS: ISH sent to All ESs (Ethernet1): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34 ES-IS: ISH from aa00.0400.6408 (Ethernet0), HT 299 ES-IS: ISH sent to All ESs (Tunnel0): NET 47.0005.80ff.ef00.0000.0001.5940.1600.O906.4023.00, HT 299, HLEN 34 IS-IS: ESH from 0000.0c00.bda8 (Ethernet0), HT 300

The following line indicates that the router has sent an IS hello packet on Ethernet interface 0 to all ESs on the network. This hello packet indicates that the NET of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length. ES-IS: ISH sent to All ESs (Ethernet0): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 33

The following line indicates that the router has sent an IS hello packet on Ethernet interface 1 to all ESs on the network. This hello packet indicates that the NET of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length. ES-IS: ISH sent to All ESs (Ethernet1): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34

The following line indicates that the router received a hello packet on Ethernet interface 0 from an intermediate system, aa00.0400.6408. The hold time for this packet is 299 seconds. ES-IS: ISH from aa00.0400.6408 (Ethernet0), HT 299

The following line indicates that the router has sent an IS hello packet on Tunnel interface 0 to all ESs on the network. This hello packet indicates that the NET of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length. ES-IS: ISH sent to All ESs (Tunnel0): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34


DB-359

Debug Commands debug clns esis packets

The following line indicates that on Ethernet interface 0, the router received a hello packet from an end system with an SNPA of 0000.0c00.bda8. The hold time for this packet is 300 seconds. IS-IS: ESH from 0000.0c00.bda8 (Ethernet0), HT 300


DB-360

May 2008

Debug Commands debug clns events

debug clns events To display Connectionless Network Service (CLNS) events that are occurring at the router, use the debug clns events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug clns events no debug clns events

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug clns events command: Router# debug clns events CLNS: Echo PDU received on Ethernet3 from 39.0001.2222.2222.2222.00! CLNS: Sending from 39.0001.3333.3333.3333.00 to 39.0001.2222.2222.2222.00 via 2222.2222.2222 (Ethernet3 0000.0c00.3a18) CLNS: Forwarding packet size 117 from 39.0001.2222.2222.2222.00 to 49.0002.0001.AAAA.AAAA.AAAA.00 via 49.0002 (Ethernet3 0000.0c00.b5a3) CLNS: RD Sent on Ethernet3 to 39.0001.2222.2222.2222.00 @ 0000.0c00.3a18, redirecting 49.0002.0001.AAAA.AAAA.AAAA.00 to 0000.0c00.b5a3

The following line indicates that the router received an echo protocol data unit (PDU) on Ethernet interface 3 from source network service access point (NSAP) 39.0001.2222.2222.2222.00. The exclamation point at the end of the line has no significance. CLNS: Echo PDU received on Ethernet3 from 39.0001.2222.2222.2222.00!

The following lines indicate that the router at source NSAP 39.0001.3333.3333.3333.00 is sending a CLNS echo packet to destination NSAP 39.0001.2222.2222.2222.00 via an IS with system ID 2222.2222.2222. The packet is being sent on Ethernet interface 3, with a MAC address of 0000.0c00.3a18. CLNS: Sending from 39.0001.3333.3333.3333.00 to 39.0001.2222.2222.2222.00 via 2222.2222.2222 (Ethernet3 0000.0c00.3a18)

The following lines indicate that a CLNS echo packet 117 bytes in size is being sent from source NSAP 39.0001.2222.2222.2222.00 to destination NSAP 49.0002.0001.AAAA.AAAA.AAAA.00 via the router at NSAP 49.0002. The packet is being forwarded on the Ethernet interface 3, with a MAC address of 0000.0c00.b5a3. CLNS: Forwarding packet size 117 from 39.0001.2222.2222.2222.00 to 49.0002.0001.AAAA.AAAA.AAAA.00 via 49.0002 (Ethernet3 0000.0c00.b5a3)


DB-361

Debug Commands debug clns events

The following lines indicate that the router sent a redirect packet on the Ethernet interface 3 to the NSAP 39.0001.2222.2222.2222.00 at MAC address 0000.0c00.3a18 to indicate that NSAP 49.0002.0001.AAAA.AAAA.AAAA.00 can be reached at MAC address 0000.0c00.b5a3. CLNS: RD Sent on Ethernet3 to 39.0001.2222.2222.2222.00 @ 0000.0c00.3a18, redirecting 49.0002.0001.AAAA.AAAA.AAAA.00 to 0000.0c00.b5a3


DB-362

May 2008

Debug Commands debug clns igrp packets

debug clns igrp packets To display debugging information on all ISO-IGRP routing activity, use the debug clns igrp packets privileged EXEC command. The no form of this command disables debugging output. debug clns igrp packets no debug clns igrp packets

Syntax Description


Examples

The following is sample output from the debug clns igrp packets command: Router# debug clns igrp packets ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP: ISO-IGRP:

Hello sent on Ethernet3 for DOMAIN_green1 Received hello from 39.0001.3333.3333.3333.00, (Ethernet3), ht 51 Originating level 1 periodic update Advertise dest: 2222.2222.2222 Sending update on interface: Ethernet3 Originating level 2 periodic update Advertise dest: 0001 Sending update on interface: Ethernet3 Received update from 3333.3333.3333 (Ethernet3) Opcode: area Received level 2 adv for 0001 metric 1100 Opcode: station Received level 1 adv for 3333.3333.3333 metric 1100

The following line indicates that the router is sending a hello packet to advertise its existence in the DOMAIN_green1 domain: ISO-IGRP: Hello sent on Ethernet3 for DOMAIN_green1

The following line indicates that the router received a hello packet from a certain network service access point (NSAP) on Ethernet interface 3. The hold time for this information is 51 seconds. ISO-IGRP: Received hello from 39.0001.3333.3333.3333.00, (Ethernet3), ht 51

The following lines indicate that the router is generating a Level 1 update to advertise reachability to destination NSAP 2222.2222.2222 and that it is sending that update to all systems that can be reached through Ethernet interface 3: ISO-IGRP: Originating level 1 periodic update ISO-IGRP: Advertise dest: 2222.2222.2222 ISO-IGRP: Sending update on interface: Ethernet3

The following lines indicate that the router is generating a Level 2 update to advertise reachability to destination area 1 and that it is sending that update to all systems that can be reached through Ethernet interface 3: ISO-IGRP: Originating level 2 periodic update ISO-IGRP: Advertise dest: 0001 ISO-IGRP: Sending update on interface: Ethernet3

The following lines indicate that the router received an update from NSAP 3333.3333.3333 on Ethernet interface 3. This update indicated the area that the router at this NSAP could reach.


DB-363

Debug Commands debug clns igrp packets

ISO-IGRP: Received update from 3333.3333.3333 (Ethernet3) ISO-IGRP: Opcode: area

The following lines indicate that the router received an update advertising that the source of that update can reach area 1 with a metric of 1100. A station opcode indicates that the update included system addresses. ISO-IGRP: Received level 2 adv for 0001 metric 1100 ISO-IGRP: Opcode: station


DB-364

May 2008

Debug Commands debug clns packet

debug clns packet To display information about packet receipt and forwarding to the next interface, use the debug clns packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug clns packet no debug clns packet

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug clns packet command: Router# debug clns packet CLNS: Forwarding packet size 157 from 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.00 STUPI-RBS to 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00 via 1600.8906.4017 (Ethernet0 0000.0c00.bda8) CLNS: Echo PDU received on Ethernet0 from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00! CLNS: Sending from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00 to 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00 via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)

In the following lines, the first line indicates that a Connectionless Network Service (CLNS) packet of size 157 bytes is being forwarded. The second line indicates the network service access point (NSAP) and system name of the source of the packet. The third line indicates the destination NSAP for this packet. The fourth line indicates the next hop system ID, interface, and subnetwork point of attachment (SNPA) of the router interface used to forward this packet. CLNS: Forwarding packet size 157 from 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.00 STUPI-RBS to 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00 via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)

In the following lines, the first line indicates that the router received an echo protocol data unit (PDU) on the specified interface from the source NSAP. The second line indicates which source NSAP is used to send a CLNS packet to the destination NSAP, as shown on the third line. The fourth line indicates the next hop system ID, interface, and SNPA of the router interface used to forward this packet. CLNS: Echo PDU received on Ethernet0 from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00! CLNS: Sending from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00 to 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00 via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)


DB-365

Debug Commands debug clns routing

debug clns routing To display debugging information for all Connectionless Network Service (CLNS) routing cache updates and activities involving the CLNS routing table, use the debug clns routing command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug clns routing no debug clns routing

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug clns routing command: Router# debug clns routing CLNS-RT: CLNS-RT: CLNS-RT: CLNS-RT:

cache increment:17 Add 47.0023.0001.0000.0000.0003.0001 to prefix table, next hop 1920.3614.3002 Aging cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06 Deleting cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06

The following line indicates that a change to the routing table has resulted in an addition to the fast-switching cache: CLNS-RT: cache increment:17

The following line indicates that a specific prefix route was added to the routing table, and indicates the next hop system ID to that prefix route. In other words, when the router receives a packet with the prefix 47.0023.0001.0000.0000.0003.0001 in the destination address of that packet, it forwards that packet to the router with the MAC address 1920.3614.3002. CLNS-RT: Add 47.0023.0001.0000.0000.0003.0001 to prefix table, next hop 1920.3614.3002

The following lines indicate that the fast-switching cache entry for a certain network service access point (NSAP) has been invalidated and then deleted: CLNS-RT: Aging cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06 CLNS-RT: Deleting cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06


DB-366

May 2008

Debug Commands debug cls message

debug cls message To display information about Cisco Link Services (CLS) messages, use the debug cls message command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cls message no debug cls message

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug cls message command displays the primitives (state), selector, header length, and data size.

Examples

The following is sample output from the debug cls message command. For example, CLS-->DLU indicates the direction of the flow that is described by the status. From CLS to dependent logical unit (DLU), a request was established to the connection endpoint. The header length is 48 bytes, and the data size is 104 bytes. Router# debug cls message (FRAS Daemon:CLS-->DLU): ID_STN.Ind to uSAP: 0x607044C4 sel: LLC hlen: 40, (FRAS Daemon:CLS-->DLU): ID_STN.Ind to uSAP: 0x6071B054 sel: LLC hlen: 40, (FRAS Daemon:DLU-->SAP): REQ_OPNSTN.Req to pSAP: 0x608021F4 sel: LLC hlen: (FRAS Daemon:CLS-->DLU): REQ_OPNSTN.Cfm(NO_REMOTE_STN) to uCEP: 0x607FFE84

dlen: 54 dlen: 46 48, dlen: 104 sel: LLC hlen: 48, dlen: 104

The status possibilities include the following: enabled, disabled, request open station, open station, close station, activate SA, deactivate service access point (SAP), XID, exchange identification (XID) station, connect station, signal station, connect, disconnect, connected, data, flow, unnumbered data, modify SAP, test, activate ring, deactivate ring, test station, and unnumbered data station.

Related Commands

Command

Description

debug fras error

Displays information about FRAS protocol errors.

debug fras message

Displays general information about FRAS messages.

debug fras state

Displays information about FRAS data-link control state changes.


DB-367

Debug Commands debug cls vdlc

debug cls vdlc To display information about Cisco Link Services (CLS) Virtual Data Link Control (VDLC), use the debug cls vdlc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cls vdlc no debug cls vdlc

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug cls message command displays primitive state transitions, selector, and source and destination MAC and service access points (SAPs). Also use the show cls command to display additional information on CLS VDLC.

Caution

Examples

Use the debug cls vdlc command with caution because it can generate a substantial amount of output.

The following messages are sample output from the debug cls vdlc command. In the following scenario, the systems network architecture (SNA) service point—also called native service point (NSP)—is setting up two connections through VDLC and data-link switching (DLSw): one from NSP to VDLC and one from DLSw to VDLC. VDLC joins the two. The NSP initiates a connection from 4000.05d2.0001 as follows: VDLC: Req Open Stn Req PSap 0x7ACE00, port 0x79DF98 4000.05d2.0001(0C)->4000.1060.1000(04)

In the next message, VDLC sends a test station request to DLSw for destination address 4000.1060.1000. VDLC: Send UFrame E3: 4000.05d2.0001(0C)->4000.1060.1000(00)

In the next two messages, DLSw replies with test station response, and NSP goes to a half-open state. NSP is waiting for the DLSw connection to VDLC. VDLC: Sap to Sap TEST_STN_RSP VSap 0x7B68C0 4000.1060.1000(00)->4000.05d2.0001(0C) VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPENING->VDLC_HALF_OPEN

The NSP sends an exchange identification (XID) and changes state as follows: VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_HALF_OPEN->VDLC_XID_RSP_PENDING VDLC: CEP to SAP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04) via bridging SAP (DLSw)


DB-368

May 2008

Debug Commands debug cls vdlc

In the next several messages, DLSw initiates its connection, which matches the half-open connection with NSP: VDLC: Req Open Stn Req PSap 0x7B68C0, port 0x7992A0 4000.1060.1000(04)->4000.05d2.0001(0C) VDLC: two-way connection established VDLC: 4000.1060.1000(04)->4000.05d2.0001(0C): VDLC_IDLE->VDLC_OPEN

In the following messages, DLSw sends an XID response, and the NSP connection goes from the state XID Response Pending to Open. The XID exchange follows: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC: VDLC:

CEP to CEP ID_RSP 4000.1060.1000(04)->4000.05d2.0001(0C) 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPEN 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPEN->VDLC_XID_RSP_PENDING CEP to CEP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04) CEP to CEP ID_RSP 4000.1060.1000(04)->4000.05d2.0001(0C) 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPEN 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPEN->VDLC_XID_RSP_PENDING CEP to CEP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04) CEP to CEP ID_RSP 4000.1060.1000(04)->4000.05d2.0001(0C) 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPEN 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPEN->VDLC_XID_RSP_PENDING CEP to CEP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04) CEP to CEP ID_RSP 4000.1060.1000(04)->4000.05d2.0001(0C) 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPEN 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPEN->VDLC_XID_RSP_PENDING CEP to CEP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04)

When DLSw is ready to connect, the front-end processor (FEP) sends a set asynchronous balanced mode extended (SABME) command as follows: VDLC: CEP to CEP CONNECT_REQ 4000.1060.1000(04)->4000.05d2.0001(0C) VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPEN

In the following messages, NSP accepts the connection and sends an unnumbered acknowledgment (UA) to the FEP: VDLC: CEP to CEP CONNECT_RSP 4000.05d2.0001(0C)->4000.1060.1000(04) VDLC: FlowReq QUENCH OFF 4000.1060.1000(04)->4000.05d2.0001(0C)

The following messages show the data flow: VDLC: VDLC: . . . VDLC: VDLC:

Related Commands

DATA 4000.1060.1000(04)->4000.05d2.0001(0C) DATA 4000.05d2.0001(0C)->4000.1060.1000(04)

DATA 4000.1060.1000(04)->4000.05d2.0001(0C) DATA 4000.05d2.0001(0C)->4000.1060.1000(04)

Command

Description

debug cls message

Displays information about CLS messages.


DB-369

Debug Commands debug cme-xml

debug cme-xml To generate debug messages for the Cisco Unified CallManager Express XML application, use the debug cme-xml command in privileged EXEC mode. To disable debugging, use the no form of the command. debug cme-xml no debug cme-xml

Syntax Description


Command Modes

Privileged EXEC

Command History

Cisco IOS Release

Modification

12.4(4)XC


12.4(9)T


12.2SX


Usage Guidelines

The show fb-its-log command displays the contents of the XML event table.

Examples

The following example shows the progress of an XML request that has been sent to Cisco Unified CallManager Express: Router# debug cme-xml *Aug *Aug *Aug *Aug *Aug *Aug *Aug *Aug *Aug *Aug *Aug *Aug

Related Commands

5 5 5 5 5 5 5 5 5 5 5 5

06:27:25.727: 06:27:25.727: 06:27:25.727: 06:27:25.727: 06:27:25.727: 06:27:25.727: 06:27:25.727: 06:27:25.727: 06:27:25.731: 06:27:25.731: 06:27:25.731: 06:27:25.731:

CME got a raw XML message. doc 0x63DB85E8, doc->doc_type 3, req 0x655FDCD0 CME extracted a XML document Response buffer 0x63DCFD58, len = 4096 First Tag ID SOAP_HEADER_TAG_ID 58720257 First Attribute ID SOAP_ENV_ATTR 50331649 cme_xml_process_soap_header cme_xml_process_soap_body cme_xml_process_axl cme_xml_process_request cme_xml_process_ISgetGlobal CME XML sent 811 bytes response.

Command

Description

show fb-its-log

Displays Cisco Unified CallManager Express XML API information.


DB-370

May 2008

Debug Commands debug cns config

debug cns config To turn on debugging messages related to the Cisco Networking Services (CNS) Configuration Agent, use the debug cns config command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cns config {agent | all | connection | notify} no debug cns config {agent | all | connection | notify}

Syntax Description

agent

Displays debugging messages related to the CNS configuration agent.

all

Displays all debugging messages.

connection

Displays debugging messages related to configuration connections.

notify

Displays debugging messages related to CNS configurations.

Defaults


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(2)T


12.0(18)ST


12.2(8)T

This command was implemented on the Cisco 2600 and Cisco 3600 series.

12.2(33)SRA


12.2(33)SB


Usage Guidelines

Use this command to turn on or turn off debugging messages related to the CNS Configuration Agent.

Examples

In the following example, debugging messages are enabled for CNS configuration processes: Router# debug cns config all 00:04:09: 00:04:09: 00:04:09: 00:04:09: 00:04:09: server 00:04:09: 00:04:09: 00:04:09: 00:04:09: 00:04:09:

config_id_get: entered config_id_get: Invoking cns_id_mode_get() config_id_get: cns_id_mode_get() returned INTERNAL config_id_get: successful exit cns_config_id=minna1,cns_config_id_len=6 cns_establish_connect_intf(): The device is already connected with the config cns_initial_config_agent(): connecting with port 80 pull_config() entered cns_config_id(): returning config_id=minna1 Message finished 150 readend %CNS-4-NOTE: SUCCESSFUL_COMPLETION


DB-371

Debug Commands debug cns config

-Process= "CNS Initial Configuration Agent", ipl= 0, pid= 82 00:04:10: %SYS-5-CONFIG_I: Configured from console by console

Related Commands

Command

Description

cns config cancel

Cancels a CNS configuration.

cns config initial

Starts the initial CNS Configuration Agent.

cns config partial

Starts the partial CNS Configuration Agent.

cns config retrieve

Gets the configuration of a routing device using CNS.

debug cns event

Displays information on CNS events.

debug cns exec

Displays information on CNS management.

debug cns xml-parser

Displays information on the CNS XML parser.

show cns config

Displays information about the CNS Configuration Agent.


DB-372

May 2008

Debug Commands debug cns event

debug cns event To turn on debugging messages related to the Cisco Networking Services (CNS) Event Gateway, use the debug cns event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cns event {agent | all | connection | subscriber} no debug cns event {agent | all | connection | subscriber}

Syntax Description

agent

Displays debugging messages related to the event agent.

all


connection

Displays debugging messages related to event connections.

subscriber

Displays debugging messages related to subscribers.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)T


12.0(18)ST

This command was integrated into the Cisco IOS Release 12.0(18)ST.

12.2(8)T

This command was implemented on Cisco 2600 series and Cisco 3600 series routers.

12.2(31)SB2

This command was integrated into Cisco IOS Release 12.2(31)SB2.

12.2SX


Usage Guidelines

Use this command to turn on or turn off debugging messages related to the CNS Event Gateway.

Examples

In the following example, debugging messages about all CNS Events are enabled: Router# debug cns event all 00:09:14: -Process= 00:09:14: 00:09:14: 00:09:14: 00:09:14:

%CNS-4-NOTE: SUCCESSFUL_COMPLETION "CNS Initial Configuration Agent", ipl= 0, pid= 82 event_agent():event_agent starting .. event_agent_open_connection(): attempting socket connect to Primary Gateway event_agent_open_connection():cns_socket_connect() succeeded:return_code=0 event_agent_open_connection():timeout_len=1:ka_total_timeout =0: total_timeout=0 00:09:14: event_id_get: entered 00:09:14: event_id_get: Invoking cns_id_mode_get()


DB-373

Debug Commands debug cns exec

debug cns exec To display debugging messages about Cisco Networking Services (CNS) exec agent services, use the debug cns exec command in privileged EXEC mode. To disable debugging output, use the no or undebug form of this command. debug cns exec {agent | all | decode | messages} no debug cns exec {agent | all | decode | messages} undebug cns exec {agent | all | decode | messages}

Syntax Description

agent

Displays debugging messages related to the exec agent.

all


decode

Displays debugging messages related to image agent connections.

messages

Displays debugging output related to messages generated by exec agent services.

Defaults

Debugging output is disabled.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(1)


12.2(25)S


12.2(33)SRA


12.2(33)SB


Usage Guidelines

Use the debug cns exec command to troubleshoot CNS exec agent services.

Examples

The following example shows a debugging message for the CNS exec agent when a response has been posted to HTTP: Router# debug cns exec agent 4d20h: CNS exec agent: response posted

Related Commands

Command

Description

cns exec

Configures CNS Exec Agent services.


DB-374

May 2008

Debug Commands debug cns image

debug cns image To display debugging messages about Cisco Networking Services (CNS) image agent services, use the debug cns image command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cns image {agent | all | connection | error} no debug cns image {agent | all | connection | error}

Syntax Description

agent

Displays debugging messages related to the image agent.

all


connection

Displays debugging messages related to image agent connections.

error

Displays debugging messages related to errors generated by image agent services.

Defaults

If no keyword is specified, all debugging messages are displayed.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(1)


12.2(31)SB2


Usage Guidelines

12.2(33)SRB


12.2(33)SB


Use the debug cns image command to troubleshoot CNS image agent services.


DB-375

Debug Commands debug cns management

debug cns management To display information about Cisco Networking Services (CNS) management, use the debug cns management command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cns management {snmp | xml} no debug cns management {snmp | xml}

Syntax Description

snmp

Displays debugging messages related to nongranular Simple Network Management Protocol (SNMP) encapsulated CNS-management events.

xml

Displays debugging messages related to granular eXtensible Markup Language (XML) encapsulated CNS-management events.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)T


12.2SX


Examples

In the following example, debugging messages about SNMP- and XML-encapsulated CNS-management events are enabled: Router# debug cns management snmp Router# debug cns management xml Router# show debugging CNS Management (SNMP Encapsulation) debugging is on CNS Management (Encap XML) debugging is on Router# show running-config | include cns cns mib-access encapsulation snmp cns mib-access encapsulation xml cns notifications encapsulation snmp cns notifications encapsulation xml cns event 10.1.1.1 11011 Router# 00:12:50: Enqueued a notification in notif_q 00:12:50: ea_produce succeeded Subject:cisco.cns.mibaccess:notification Message Length:385 00:12:50: Trap sent via CNS Transport Mapping. Router# 00:13:31: Response sent via CNS Transport Mapping. Router# 00:14:38: Received a request 00:14:38: ea_produce succeeded Subject:cisco.cns.mibaccess:response Message Length:241


DB-376

May 2008

Debug Commands debug cns management

Related Commands

Command

Description

cns event

Configures the CNS event gateway, which provides CNS event services to Cisco IOS clients.

debug cns config

Displays information on CNS configurations.

debug cns xml-parser

Displays information on the CNS XML parser.

show debugging


show running-config

Displays the current running configuration.


DB-377

Debug Commands debug cns xml

debug cns xml To turn on debugging messages related to the Cisco Networking Services (CNS) eXtensible Markup Language (XML) parser, use the debug cns xml command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cns xml {all | decode | dom | parser} no debug cns xml {all | decode | dom | parser}

Syntax Description

all

Displays all CNS debugging.

decode

Reports usage of common XML decoding library functions by applications and reports the decoded contents.

dom

Displays failures in the Document Object Model (DOM) infrastructure messages tree built by the XML parser.

parser

Displays failures and progress of the parsing of an XML message by the XML parser.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(2)T

This command was introduced. This command replaces the debug cns xml-parser command.

12.2(33)SRA


12.2SX


12.2(33)SB


Examples

In the following example, debugging messages for the CNS XML parser are enabled: Router# debug cns xml parser 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05:

Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering

tag tag tag tag tag tag tag tag tag tag tag tag tag tag tag


DB-378

May 2008

Debug Commands debug cns xml

00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: -Process=

Related Commands

Registering tag Registering tag Registering tag Registering tag Registering tag Registering tag Registering tag Registering tag Pushing tag on to stack open tag is Pushing tag on to stack open tag is Popping tag off stack close tag is Pushing tag on to stack open tag is Popping tag off stack close tag is Popping tag off stack close tag is %CNS-4-NOTE: SUCCESSFUL_COMPLETION "CNS Initial Configuration Agent", ipl= 0, pid= 96

Command

Description

cns event

Configures the CNS Event Gateway.

show cns event

Displays information about the CNS Event Agent.


DB-379

Debug Commands debug cns xml-parser

debug cns xml-parser Note

Effective with Cisco IOS Release 12.3(2)T, the debug cns xml-parser command is replaced by the debug cns xml command. See the debug cns xml command for more information. To turn on debugging messages related to the Cisco Networking Services (CNS) eXtensible Markup Language (XML) parser, use the debug cns xml-parser command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cns xml-parser no debug cns xml-parser

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)T


12.0(18)ST


12.2(8)T

This command was implemented on the Cisco 2600 and Cisco 3600 series.

12.3(2)T

This command was replaced by the debug cns xml command.

12.2SX


Examples

In the following example, debugging messages for the CNS XML parser are enabled: Router# debug cns xml-parser 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05:

Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering Registering

tag tag tag tag tag tag tag tag tag tag tag tag tag tag tag tag tag


DB-380

May 2008

Debug Commands debug cns xml-parser

00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:05: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: 00:12:06: -Process=

Related Commands

Registering tag Registering tag Registering tag Registering tag Registering tag Registering tag Pushing tag on to stack open tag is Pushing tag on to stack open tag is Popping tag off stack close tag is Pushing tag on to stack open tag is Popping tag off stack close tag is Popping tag off stack close tag is %CNS-4-NOTE: SUCCESSFUL_COMPLETION "CNS Initial Configuration Agent", ipl= 0, pid= 96

Command

Description

cns event

Configures the CNS Event Gateway.

show cns event

Displays information about the CNS Event Agent.


DB-381

Debug Commands debug compress

debug compress To debug compression, enter the debug compress command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug compress no debug compress

Syntax Description


Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

10.0


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command to display output from the compression and decompression configuration you made. Live traffic must be configured through the Cisco 2600 access router with a data compression Advanced Interface Module (AIM) installed for this command to work.

Examples

The following example is output from the debug compress command, which shows that compression is taking place on a Cisco 2600 access router using data compression AIM hardware compression is configured correctly: Router# debug compress COMPRESS debugging is on Router#compr-in:pak:0x810C6B10 npart:0 size:103 pak:0x810C6B10 start:0x02406BD4 size:103 npart:0 compr-out:pak:0x8118C8B8 stat:0x00000000 npart:1 size:71 lcb:0xED pak:0x8118C8B8 start:0x0259CD3E size:71 npart:1 mp:0x8118A980 start:0x0259CD3E size:71 decmp-in:pak:0x81128B78 start:0x0255AF44 size:42 npart:1 hdr:0xC035 pak:0x81128B78 start:0x0255AF44 size:42 npart:1 mp:0x81174480 start:0x0255AF44 size:42 decmp-out:pak:0x8118C8B8 start:0x025B2C42 size:55 npart:1 stat:0 pak:0x8118C8B8 start:0x025B2C42 size:55 npart:1 mp:0x8118B700 start:0x025B2C42 size:55


DB-382

May 2008

Debug Commands debug compress


Related Commands

debug compress Field Descriptions

Field

Description

compr-in

Indicates that a packet needs to be compressed.

compr-out

Indicates completion of compression of packet.

decmp-in

Indicates receipt of a compressed packet that needs to be decompressed.

decmp-out

Indicates completion of decompression of a packet.

pak:0x810C6B10

Provides the address in memory of a software structure that describes the compressed packet.

start:0x02406BD4 size:103 npart:0

The “npart:0” indicates that the packet is contained in a single, contiguous area of memory. The start address of the packet is 0x02406bd4 and the size of the packet is 103.

start:0x0259CD3E size:71 npart:1

The “npart:1” indicates that the packet is contained in 1 or more regions of memory. The start address of the packet is 0x0259CD3E and the size of the packet is 71.

mp:0x8118A980 start:0x0259CD3e size:71

Describes one of these regions of memory.

mp:0x8118A980

Provides the address of a structure describing this region.

start 0x0259CD3E

Provides the address of the start of this region.

Command

Description

debug frame-relay

Displays debugging information about the packets that are received on a Frame Relay interface.

debug ppp


show compress

Displays compression statistics.

show diag

Displays hardware information including DRAM, SRAM, and the revision-level information on the line card.


DB-383

Debug Commands debug condition application voice

debug condition application voice To display debugging messages for only the specified VoiceXML application, use the debug condition application voice command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug condition application voice application-name no debug condition application voice application-name

Syntax Description

application-name

Defaults

If this command is not configured, debugging messages are enabled for all VoiceXML applications.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T

This command was introduced for the Cisco 3640, Cisco 3660, Cisco AS5300, Cisco AS5350, and Cisco AS5400.

12.2SX


Usage Guidelines

Name of the VoiceXML application for which you want to display all enabled debugging messages.

•

This command filters debugging output only for the debug vxml and debug http client commands, except that it does not filter output for the debug vxml error, debug vxml background, debug http client error, or debug http client background commands. It does not filter messages for any other debug commands such as the debug voip ivr command or the debug voice ivr command.

•

This command filters debugging output for all VoiceXML applications except the application named in the command. When this command is configured, the gateway displays debugging messages only for the specified VoiceXML application.

•

To filter debugging output with this command, the element must be enabled in the VoiceXML document. For more information about the element, refer to the Cisco VoiceXML Programmer’s Guide.

•

To see debugging output for VoiceXML applications, you must first configure global debug commands such as the debug vxml command or the debug http client command. If no global debug commands are turned on, you do not see debugging messages even if the debug condition application voice command is configured and the element is enabled in the VoiceXML document.

•

This command can be configured multiple times to display output for more than one application.

•

To see which debug conditions have been set, use the show debug condition command.


DB-384

May 2008

Debug Commands debug condition application voice

Examples

The following example disables debugging output for all applications except the myapp1 application, if the element is enabled in the VoiceXML documents that are executed by myapp1: Router# debug condition application voice myapp1

Related Commands

Command

Description

debug http client

Displays debugging messages for the HTTP client.

debug vxml

Displays debugging messages for VoiceXML features.

show debug condition

Displays the debugging conditions that have been enabled for VoiceXML application.


DB-385

Debug Commands debug condition glbp

debug condition glbp To display debugging messages about Gateway Load Balancing Protocol (GLBP) conditions, use the debug condition glbp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug condition glbp interface-type interface-number group [forwarder] no debug condition glbp interface-type interface-number group [forwarder]

Syntax Description

interface-type

Interface type for which output is displayed.

interface-number

Interface number for which output is displayed.

group

GLBP group number in the range from 0 to 1023.

forwarder

(Optional) Number in the range from 1 to 255 used to identify a virtual MAC address.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(14)S


12.2(15)T


12.2(17b)SXA

This command was integrated into Cisco IOS Release 12.2(17b)SXA.

12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug condition glbp command: Router# debug condition glbp fastethernet 0/0 10 1 Condition 1 set 5d23h: Fa0/0 GLBP10.1 Debug: Condition 1, glbp Fa0/0 GLBP10.1 triggered, count 1

Related Commands

Command

Description

debug glbp errors

Displays debugging messages about GLBP errors.

debug glbp events

Displays debugging messages about GLBP events.

debug glbp packets

Displays debugging messages about GLBP packets.

debug glbp terse

Displays a limited range of debugging messages about GLBP errors, events, and packets.


DB-386

May 2008

Debug Commands debug condition interface

debug condition interface To limit output for some debug commands on the basis of the interface, virtual circuit (VC), or VLAN, use the debug condition interface command in privileged EXEC mode. To remove the interface condition and reset the interface so that it must be triggered by a condition, use the no form of this command. debug condition interface interface-type interface-number [dlci dlci] [vc {vci | vpi/vci}] [vlan-id vlan-id] no debug condition interface interface-type interface-number [dlci dlci] [vc {vci | vpi/vci}] [vlan-id vlan-id]

Syntax Description

interface-type interface-number

Interface type and number. No space is required between the interface type and number. Some interfaces require a slash between the type and number.

dlci dlci

(Optional) If the interface to be debugged is a Frame Relay-encapsulated interface, specifies the data-link connection identifier (DLCI).

vc {vci | vpi/vci}

(Optional) If the interface to be debugged is an ATM-encapsulated interface, specifies the virtual channel identifier (VCI) or virtual path identifier/virtual channel identifier (VPI/VCI) pair. (The slash is required.)

vlan-id vlan-id

(Optional) If the interface to be debugged is ATM, Ethernet, Fast Ethernet, or Gigabit Ethernet, specifies the VLAN ID.

Defaults

All debugging messages for enabled debug commands are displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(28)S

The dlci and vc keywords were added for additional Frame Relay and ATM functionality.

12.2(25)S


12.2(27)SBC

This command was integrated into Cisco IOS Release 12.2(27)SBC.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB, and the ability to filter debug output on the basis of VLAN ID was added.

12.4(9)T


12.2SX



DB-387


Usage Guidelines

Use this command to restrict the debugging output for some commands on the basis of an interface or virtual circuit. When you enter this command, debugging output is turned off for all interfaces except the specified interface or virtual circuit. In addition, this command enables conditional debugging to limit output for specific debugging events. Messages are displayed as different interfaces meet specific conditions. The no form of the command has two functions: •

It disables the debug condition interface command for the specified interface. Output is no longer generated for the interface, assuming that the interface meets no other applicable conditions. If the interface meets other conditions that have been set by another debug condition command, debugging output will still be generated for the interface.

•

If some other debug condition command has been enabled, output is stopped for that interface until the condition is met on the interface. You will be asked for confirmation before the last condition or all conditions are removed.

Not all debugging output is affected by the debug condition command. Some commands generate output whenever they are enabled, regardless of whether they meet any conditions. The commands that are affected by the debug condition commands are generally related to dial access functions, where a large amount of output is expected. Output from the following commands is controlled by the debug condition command: •

debug aaa

•

debug atm

•

debug dialer events

•

debug frame-relay

•

debug isdn

•

debug modem

•

debug ppp

One or more ATM-encapsulated interfaces must be enabled, and one or more of the following debug commands must be enabled to use conditional debugging with ATM: •

debug atm arp

•

debug atm counters

•

debug atm errors

•

debug atm events

•

debug atm oam

•

debug atm packet

•

debug atm state

One or more of the following debug commands must be enabled to use conditional debugging with Frame Relay: •

debug frame-relay adjacency

•

debug frame-relay ipc

•

debug frame-relay lmi

•

debug frame-relay packet

•

debug frame-relay pseudowire


DB-388

May 2008


Examples

In the following example, only debug command output related to serial interface 1 is displayed. The condition identifier for this command is 1. Router# debug condition interface serial 1 Condition 1 set

The following example enables an ATM interface, specifies an IP address for the interface, turns on conditional debugging for that interface with a VPI/VCI pair of 255/62610, and verifies that debugging has been enabled: Router> enable Password: Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface ATM 2/0 Router(config-if)# ip address 10.0.0.5 255.255.255.0 Router(config-if)# pvc 255/62610 Router(config-if-atm-vc)# no shutdown Router(config-if)# exit Router(config)# exit 2w3d: %SYS-5-CONFIG_I: Configured from console by console Router# debug atm state ATM VC States debugging is on Router# debug condition interface ATM2/0 vc 255/62610 Condition 1 set 2w3d: ATM VC Debug: Condition 1, atm-vc 255/62610 AT2/0 triggered, count 1 Router# show debug condition Condition 1: atm-vc 255/62610 AT2/0 (1 flags triggered) Flags: ATM VC

In the following example, Frame Relay conditional debugging is enabled on Frame Relay DLCI 105: Router# debug condition interface serial 4/3 dlci 105 Router# debug frame-relay packet

Related Commands

Command

Description

debug condition

Limits output for some debug commands on the basis of specific conditions.


DB-389

Debug Commands debug condition match-list

debug condition match-list To run a filtered debug on a voice call, use the debug condition match-list command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug condition match-list number {exact-match | partial-match} no debug condition match-list number {exact-match | partial-match}

Syntax Description

number

Numeric label that uniquely identifies the match list. Range is 1 to 16. The number for the match list is set using the call filter match-list command.

exact-match

All related debug output is filtered until all conditions in the match list are explicitly met. This is the best choice for most situations because the output is the most concise.

partial-match

No related debug output is filtered until there is a single explicit match failure. As long as zero or more conditions are met, debug output will not be filtered. This choice is useful in debugging call startup problems like digit collection, but is not ideal for many situations because there is much debug output until matches explicitly fail.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Examples

In this output example, the following configuration was used: call filter match-list 1 voice incoming calling-number 8288807 incoming called-number 6560729 incoming port 7/0:D

The following is sample output for the debug condition match-list 1 command. The next several lines match the above conditions. Router# debug condition match-list 1 07:22:19://-1/3C0B9468-15C8-11D4-8013-000A8A389BA8/VTSP:(7/0:D):0:0:0/vtsp_gcfm_incoming_c ond_notify: add incoming port cond success: 7/0:D 07:22:19://-1/3C0B9468-15C8-11D4-8013-000A8A389BA8/VTSP:(7/0:D):0:0:0/vtsp_gcfm_incoming_c ond_notify: add incoming dialpeer tag success:1


DB-390

May 2008

Debug Commands debug condition match-list

07:22:19://-1/3C0B9468-15C8-11D4-8013-000A8A389BA8/VTSP:(7/0:D):0:0:0/vtsp_update_dsm_stre am_mgr_filter_flag: cannot find dsp_stream_mgr_t 07:22:19://-1/3C0B9468-15C8-11D4-8013-000A8A389BA8/VTSP:(7/0:D):0:0:0/vtsp_update_dsm_stre am_mgr_filter_flag: update dsp_stream_mgr_t debug flag 07:22:19: //49/3C0B9468-15C8-11D4-8013-000A8A389BA8/VTSP:(7/0:D):0:0:0/vtsp_insert_cdb: ,cdb 0x6482C518, CallID=49 07:22:19://49/3C0B9468-15C8-11D4-8013-000A8A389BA8/VTSP:(7/0:D):0:0:0/vtsp_do_call_setup_i nd: Call ID=98357, guid=3C0B9468-15C8-11D4-8013-000A8A389BA8


Related Commands

debug condition match-list Field Descriptions

Field

Description

3C0B9468-15C8-11D4-8013-000A8A389BA8

Shows the global unique identifier (GUID).

VTSP:

Identifies the voice telephony service provider (VTSP) module.

(7/0:D):0:0:0

Shows the port name, channel number, DSP slot, and DSP channel number for the VTSP module.

Command

Description

call filter match-list voice Creates a call filter match list for debugging voice calls. debug call filter inout

Displays the debug trace inside the GCFM.

show call filter match-list Displays call filter match lists.


DB-391

Debug Commands debug condition standby

debug condition standby To filter the output of the debug standby command on the basis of interface and Hot Standby Router Protocol (HSRP) group number, use the debug condition standby command in privileged EXEC mode. To remove the specified filter condition, use the no form of this command. debug condition standby interface group-number no debug condition standby interface group-number

Syntax Description

interface

Filters output on the basis of the interface.

group-number

Filters output on the basis of HSRP group number. The range is 0 to 255 for HSRP Version 1 and 0 to 4095 for HSRP Version 2.

Defaults

All debugging messages for the debug standby command aregenerated.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(2)


12.2SX


Usage Guidelines

Use the debug condition standby command to restrict the debug output for the debug standby command. If the debug condition standby command is enabled, output is generated only for the interfaces and HSRP group numbers specified. The interface you specify must be a valid interface capable of supporting HSRP. The group can be any group (0 to 255 for HSRPv1 and 0 to 4095 for HSRPv2). Use the no form of this command to remove the HSRP debug condition. If the last condition is removed, debugging output resumes for all interfaces. You will be asked for confirmation before removing the last condition or all conditions. You can set debug conditions for groups that do not exist, which allows you to capture debug information during the initialization of a new group. You must enable the debug standby command in order for any HSRP debug output to be produced. If you do not configure the debug condition standby command after entering the debug standby command, then debug output is produced for all groups on all interfaces.

Examples

In the following example, the router displays debugging messages only for Ethernet interface 0/0 that are part of HSRP group 23: Router# debug standby


DB-392

May 2008

Debug Commands debug condition standby

HSRP debugging is on Router# debug condition standby ethernet0/0 23 Condition 00:27:39: 00:27:42: 00:27:45: 00:27:48: 00:27:51:

1 set HSRP: HSRP: HSRP: HSRP: HSRP:

Et0/0 Et0/0 Et0/0 Et0/0 Et0/0

Grp Grp Grp Grp Grp

23 23 23 23 23

Hello Hello Hello Hello Hello

out out out out out

10.0.0.1 10.0.0.1 10.0.0.1 10.0.0.1 10.0.0.1

Active Active Active Active Active

pri pri pri pri pri

100 100 100 100 100

vIP vIP vIP vIP vIP

172.16.6.5 172.16.6.5 172.16.6.5 172.16.6.5 172.16.6.5

The following example shows how to remove an HSRP debug condition: Router# no debug condition standby ethernet0/0 23 This condition is the last hsrp condition set. Removing all conditions may cause a flood of debugging messages to result, unless specific debugging flags are first removed. Proceed with removal? [yes/no]: Y Condition 1 has been removed.

Related Commands

Command

Description

debug condition interface

Limits output for some debugging commands based on the interfaces.

debug standby

Displays HSRP state changes.

debug standby errors

Displays error messages related to HSRP.

debug standby events

Displays events related to HSRP.

debug standby events icmp

Displays debugging messages for the HSRP ICMP redirects filter.

debug standby packets

Displays debugging information for packets related to HSRP.


DB-393

Debug Commands debug condition voice-port

debug condition voice-port To limit output for debug commands based on the voice port, use the debug condition voice-port command in privileged EXEC mode. To disable the condition, use the no form of this command. debug condition voice-port port no debug condition voice-port port

Syntax Description

port

Voice port for which you want to display all enabled debugging messages. Note

Port syntax is platform-dependent; type ? to determine.

Command Default

Debugging messages are enabled for all voice ports.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(6)T


12.2SX


Usage Guidelines

Examples

•

This command filters out debugging output for all voice ports except the port specified in the command. When this command is configured, the gateway displays debugging messages only for the specified port.

•

To see debugging output, you must first enable debug commands such as the debug voip application stcapp all command or the debug sccp all command. If no debug commands are turned on, you do not see debugging messages even if the debug condition voice-port command is enabled.

•

This command can be configured multiple times to display output for more than one voice port.

•

To see which debug conditions have been set, use the show debug command.

•

Before disabling conditions, first disable any debugging commands; otherwise output for all ports could flood the logging buffer.

The following example filters debugging output so that only output for ports 2/1 and 2/3 is displayed: Router# debug condition voice-port 2/1 Condition 1 set *Mar 1 22:24:15.102:

Debug: Condition 1, voice-port 2/1 triggered, count 1

Router# debug condition voice-port 2/3 Condition 2 set


DB-394

May 2008

Debug Commands debug condition voice-port

*Mar

1 22:24:24.794:

Debug: Condition 2, voice-port 2/3 triggered, count 2

Router# show debug Condition 1: voice-port 2/1 (1 flags triggered) Flags: voice-port condition Condition 2: voice-port 2/3 (1 flags triggered) Flags: voice-port condition

Related Commands

Command

Description

debug sccp all

Displays debugging information for Simple Client Control Protocol (SCCP).

debug voip application stcapp all

Displays debugging information for the components of the SCCP Telephony Control Application (STCAPP).

debug voip application stcapp port

Enables STCAPP debugging for a specific port.

show debug

Displays the types of debugging and the debugging conditions that are enabled on your router.


DB-395

Debug Commands debug condition xconnect

debug condition xconnect To conditionally filter debug messages related to xconnect configurations, use the debug condition xconnect command in privileged EXEC configuration mode. To disable the filtering of xconnect debug messages, use the no form of this command. debug condition xconnect {fib type | interface type number [dlci | vp number | vc number] | peer ip-address vcid vcid | segment segment-id} no debug condition xconnect {fib type | interface type number [dlci | vp number | vc number] | peer ip-address vcid vcid | segment segment-id}

Syntax Description

fib type

Filters control-plane and data-plane debug messages for the xconnect segment pair specified by matching against the Forwarding Information Base (FIB) Interface Descriptor Block (IDB) information associated with a particular interface on a line card.

interface type number

Filters control-plane and data-plane debug messages for the xconnect segment pair specified by the interface type and number on a Route Processor.

dlci

(Optional) The Frame Relay data-link connection identifier (DLCI) for the xconnect segment pair associated with a Frame Relay segment.

vp number

(Optional) The ATM virtual path (VP) number for the xconnect segment pair associated with an ATM segment.

vc number

(Optional) The ATM virtual circuit (VC) number for the xconnect segment pair associated with an ATM segment.

peer

Filters control-plane and data-plane debug messages for the xconnect segment pair specified by the remote peer IP address and the pseudowire virtual circuit ID (VCID).

ip-address

The IP address of the remote peer router.

vcid vcid

The VCID of the xconnect pseudowire.

segment

Filters data-plane debug messages for the xconnect segment pair specified by a segment ID.

segment-id

The segment ID. The segment ID value can be found in the output of the show ssm id command.

Command Default

Debug messages are not filtered.

Command Modes

Privileged EXEC


DB-396

May 2008


Command History

Release

Modification

12.2(28)SB


12.2SX


Usage Guidelines

Use the debug condition xconnect command to specify conditions for filtering the debug messages displayed by related subscriber service switch (SSS), xconnect, and attachment circuit debug commands.

Examples

The following example sets filter conditions that allow related debug commands to display debug messages for only the xconnect segment pair specified by the remote peer IP address and the pseudowire VCID: debug condition xconnect peer 10.0.0.1 vcid 100

The following example sets filter conditions that allow related debug commands to display debug messages for only the xconnect segment pair specified by the serial interface number and DLCI: debug condition xconnect interface serial 0/0 100

The following example sets filter conditions that allow related debug commands to display debug messages for only the xconnect segment pair specified by the port mode ATM interface number: debug condition xconnect interface atm 0/0

The following example sets filter conditions that allow related debug commands to display debug messages for only the xconnect segment pair specified by the VP mode ATM interface number: debug condition xconnect interface atm 0/0 vp 1

The following example sets filter conditions that allow related debug commands to display debug messages for only the xconnect segment pair specified by the VC mode ATM interface number: debug condition xconnect interface atm 0/0 vc 1/40

The following example finds the segment ID associated with an L2TPv3 xconnect segment pair and sets filter conditions that allow related debug commands to display debug messages for only that xconnect segment pair: Router# show ssm id ! Segment-ID: 8193 Type: L2TPv3[8] ! Router# debug conditional xconnect segment 8193

Related Commands

Command

Description

debug acircuit

Displays errors and events that occur on the attachment circuits.

debug sss aaa authorization event

Displays messages about AAA authorization events that are part of normal call establishment.

debug sss aaa authorization fsm

Displays information about AAA authorization state changes.


DB-397


Command

Description

debug sss error

Displays diagnostic information about errors that may occur during SSS call setup.

debug sss event

Displays diagnostic information about SSS call setup events.

debug sss fsm

Displays diagnostic information about the SSS call setup state.

debug xconnect

Displays debug messages related to an xconnect configuration.

show ssm id

Displays SSM information for switched Layer 2 segments.


DB-398

May 2008

Debug Commands debug condition

debug condition To filter debugging output for certain debug commands on the basis of specified conditions, use the debug condition command in privileged EXEC mode. To remove the specified condition, use the no form of this command. debug condition {called dial-string | caller dial-string | calling tid/imsi string | domain domain-name | ip ip-address | mac-address hexadecimal-MAC-address | portbundle ip ip-address bundle bundle-number | session-id session-number | username username | vcid vc-id} no debug condition {condition-id | all}

Syntax Description

called dial-string

Filters output on the basis of the called party number.

caller dial-string

Filters output on the basis of the calling party number.

calling tid/imsi string

Filters debug messages for general packet radio service (GPRS) tunneling protocol (GTP) processing on the gateway GPRS support node (GGSN) based on the tunnel identifier (TID) or international mobile system identifier (IMSI) in a Packet Data Protocol (PDP) Context Create Request message.

domain domain-name

Filters output on the basis of the specified domain.

ip ip-address

Filters output on the basis of the specified IP address.

mac-address Filters messages on the specified MAC address. hexadecimal-MAC-address portbundle ip IP-address

Filters output on the basis of the port-bundle host key (PBHK) that uniquely identifies the session.

bundle bundle-number

Specifies the port bundle.

session-id session-number

Filters output on the specified Intelligent Service Architecture (ISA) session identifier.

username username

Filters output on the basis of the specified username.

vcid vc-id

Filters output on the basis of the specified VC ID.

condition-id

Removes the condition indicated.

all

Removes all debugging conditions, and conditions specified by the debug condition interface command. Use this keyword to disable conditional debugging and reenable debugging for all interfaces.

Defaults

All debugging messages for enabled protocol-specific debug commands are generated.

Command Modes

Privileged EXEC


DB-399


Command History

Usage Guidelines

Release

Modification

11.3(2)AA


12.0(23)S

This command was integrated into Cisco IOS Release 12.0(23)S. This command was updated with the vcid and ip keywords to support the debugging of Any Transport over MPLS (AToM) messages.

12.2(14)S


12.2(15)T

This command was integrated into Cisco IOS Relese 12.2(15)T.

12.3(2)XB

This command was introduced on the GGSN.

12.3(8)T

The calling keyword and tid/imsi string argument were added.

12.2(28)SB

The ability to filter output on the following conditions was added: domain, MAC address, PBHK, and ISA session ID.

12.2(33)SRA


12.2SX


Use the debug condition command to restrict the debug output for some commands. If any debug condition commands are enabled, output is generated only for interfaces associated with the specified keyword. In addition, this command enables debugging output for conditional debugging events. Messages are displayed as different interfaces meet specific conditions. If multiple debug condition commands are enabled, output is displayed if at least one condition matches. All the conditions do not need to match. The no form of this command removes the debug condition specified by the condition identifier. The condition identifier is displayed after you use a debug condition command or in the output of the show debug condition command. If the last condition is removed, debugging output resumes for all interfaces. You will be asked for confirmation before removing the last condition or all conditions. Not all debugging output is affected by the debug condition command. Some commands generate output whenever they are enabled, regardless of whether they meet any conditions. The following components are supported for Intelligent Service Architecture (ISA) distributed conditional debugging: •

Authentication, authorization, and accounting (AAA) and RADIUS

•

ATM components

•

Feature Manager

•

Policy Manager

•

PPP

•

PPP over Ethernet (PPPoE)

•

Session Manager

•

Virtual Private Dialup Network (VPDN)


DB-400

May 2008


Ensure that you enable TID/IMSI-based conditional debugging by entering debug condition calling before configuring debug gprs gtp and debug gprs charging. In addition, ensure that you disable the debug gprs gtp and debug gprs charging commands using the no debug all command before disabling conditional debugging using the no debug condition command. This will prevent a flood of debugging messages when you disable conditional debugging.

Examples

Example 1

In the following example, the router displays debugging messages only for interfaces that use a username of “user1”. The condition identifier displayed after the command is entered identifies this particular condition. Router# debug condition username user1 Condition 1 set

Example 2

The following example specifies that the router should display debugging messages only for VC 1000: Router# debug condition vcid 1000 Condition 1 set 01:12:32: 1000 Debug: Condition 1, vcid 1000 triggered, count 1 01:12:32: 1000 Debug: Condition 1, vcid 1000 triggered, count 1

The following example enables other debugging commands. These debugging commands will only display information for VC 1000. Router# debug mpls l2transport vc event AToM vc event debugging is on Router# debug mpls l2transport vc fsm AToM vc fsm debugging is on

The following commands shut down the interface on which VC 1000 is established. Router(config)# interface s3/1/0 Router(config-if)# shut

The debugging output shows the change to the interface where VC 1000 is established. 01:15:59: AToM MGR [13.13.13.13, 1000]: Event local down, state changed from established to remote ready 01:15:59: AToM MGR [13.13.13.13, 1000]: Local end down, vc is down 01:15:59: AToM SMGR [13.13.13.13, 1000]: Processing imposition update, vc_handle 6227BCF0, update_action 0, remote_vc_label 18 01:15:59: AToM SMGR [13.13.13.13, 1000]: Imposition Disabled 01:15:59: AToM SMGR [13.13.13.13, 1000]: Processing disposition update, vc_handle 6227BCF0, update_action 0, local_vc_label 755 01:16:01:%LINK-5-CHANGED: Interface Serial3/1/0, changed state to administratively down 01:16:02:%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/1/0, changed state to down

Related Commands

Command

Description




DB-401

Debug Commands debug configuration lock

debug configuration lock To enable debugging of the Cisco IOS configuration lock, use the debug configuration lock command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug configuration lock no debug command lock

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.0(31)S


12.2(33)SRA


12.2SX


12.2(33)SB


Examples

The following is sample output with debug configuration lock enabled (assuming that the feature is enabled using the configuration mode exclusive manual command in global configuration mode): Router# debug configuration lock Session1 from console ========================== Router# configure terminal lock Configuration mode locked exclusively. The lock will be cleared once you exit out of configuration mode using end/exit Enter configuration commands, one per line. End with CNTL/Z. Router(config)# Parser : LOCK REQUEST in EXCLUSIVE mode Parser: - Config. Lock requested by process client Parser: - Config. Lock acquired successfully ! Router(config)#

Session2 VTY (User from session2 is trying to enter single user config (exclusive) config mode) ================================= Router# configure terminal lock Configuration mode locked exclusively by user 'unknown' process '3' from terminal '0'. Please try later. Router#


DB-402

May 2008

Debug Commands debug configuration lock

Session1 from console ======================= Router(config)# Parser : LOCK REQUEST in EXCLUSIVE mode Parser: - Config. Lock requested by process client Parser: - NON_BLOCKING : Config mode locked owner Router(config)# Router(config)# end Router# %SYS-5-CONFIG_I: Configured from console by console Parser: - Config. EXC UnLock requested by user Parser: - Config UNLOCKED ! Router#

Related Commands

Command

Description

configuration mode exclusive

Enables single-user (exclusive) access functionality for the Cisco IOS CLI.

show configuration lock

Displays information about the lock status of the running configuration file during a configuration replace operation.


DB-403

Debug Commands debug confmodem

debug confmodem To display information associated with the discovery and configuration of the modem attached to the router, use the debug confmodem command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug confmodem no debug confmodem

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug confmodem command is used in debugging configurations that use the modem autoconfig command.

Examples

The following is sample output from the debug confmodem command. In the first three lines, the router is searching for a speed at which it can communicate with the modem. The remaining lines show the actual sending of the modem command. Router# debug confmodem TTY4:detection speed(115200) response -----TTY4:detection speed(57600) response -----TTY4:detection speed(38400) response ---OK--TTY4:Modem command: --AT&F&C1&D2S180=3S190=1S0=1-TTY4: Modem configuration succeeded TTY4: Done with modem configuration


DB-404

May 2008

Debug Commands debug conn

debug conn To display information from the connection manager, time-division multiplexing (TDM) and digital signal processor (DSP) clients, use the debug conn command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug conn no debug conn

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)XM

This command is supported on Cisco 3600 series routers.

12.2(4)T

This command is supported on Cisco 2600 series routers and was integrated into Cisco IOS Release 12.2(4)T.

12.2SX


Examples

The following example shows connection manager debugging output: Router# debug conn Connection Manager debugging is on Router# configure terminal Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)# connect conn1 t1 3/0 1 t1 4/0 1 Router(config-tdm-conn)# exit *Mar *Mar *Mar *Mar *Mar

6 6 6 6 6

18:30:59:%CONN TDM:Segment attached to dsx1 18:30:59:%CONN TDM:Parsed segment 1 18:30:59:%CONN TDM:Segment attached to dsx1 18:30:59:%CONN TDM:Parsed segment 2 18:30:59:%CONN:Creating new connection


DB-405

Debug Commands debug conn

Router(config)# *Mar 6 18:31:01:%CONN TDM:Interwork Segments *Mar 6 18:31:01:CONN TDM:Init Segment @ 61C26980 *Mar 6 18:31:01:CONN TDM:Init Segment @ 61C26A44 *Mar 6 18:31:01:%CONN TDM:Activating Segment @ 61C26980 *Mar 6 18:31:01:%CONN:Segment alarms for conn conn1 are 2 *Mar 6 18:31:01:%CONN TDM:Activating Segment @ 61C26A44 *Mar 6 18:31:01:%CONN:Segment alarms for conn conn1 are 0 *Mar 6 18:31:01:%CONN TDM:Connecting Segments *Mar 6 18:31:01:%CONN TDM:MAKING CONNECTION *Mar 6 18:31:01:%CONN:cm_activate_connection, stat = 5 Router(config)#


DB-406

May 2008

Debug Commands debug control-plane

debug control-plane To display debugging output from the control-plane routines, use the debug control plane command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug control-plane [all | host | port-filtering | queue-thresholding | log] no debug control-plane [all | host | port-filtering | queue-thresholding | log]

Syntax Description

all

(Optional) Displays all events on all control-plane interfaces.

host

(Optional) Displays all events on the control-plane host interface.

port-filtering

(Optional) Displays TCP/IP protocol port-filtering events.

queue-thresholding

(Optional) Displays TCP/IP protocol queue-thresholding events.

log

(Optional) Displays control-plane logging events.

Command Default

The default is debugging off.

Command Modes

Privileged EXEC

Command History

Release

Moditication

12.4(4)T


12.4(6)T

The log keyword was added to support control plane logging.

12.2SX


Usage Guidelines

Use the debug control plane command if you want to display the debugging output from the control-plane routines.

Examples

The following example show a display from the debug control-plane command: Router# debug control-plane Control-plane infrastructure events debugging is on Router# cp_receive_classify - marking pak host ingress pak marked cef-exception

The following example shows a display from the debug control-plane command using the port-filtering option: Router# debug control-plane port-filtering TCP/IP Port filtering events debugging is on Dropped UDP dport 1243 sport 62134 saddr 209.165.200.225


DB-407

Debug Commands debug control-plane


Related Commands

debug control plane field descriptions

Field

Description

dport

UPD destination port.

sport

UPD source port.

saddr

Source address of the IP packets.

Command

Description

clear control-plane

Clears packet counters for control-plane interfaces and subinterfaces.

control-plane

Enters control-plane configuration mode, which allows users to associate or modify attributes or parameters that are associated with the control plane of the device.

show control-plane Displays the control plane packet counters for the control plane cef-exception counters CEF-exception subinterface. show control-plane cef-exception features

Displays the configured features for the control plane CEF-exception subinterface.

show control-plane counters

Displays the control-plane packet counters for the aggregate control-plane interface.

show control-plane features

Displays the configured features for the aggregate control-plane interface.

show control-plane host counters

Displays the control plane packet counters for the control plane host subinterface.

show control-plane host features

Displays the configured features for the control plane host subinterface.

show control-plane host open-ports

Displays a list of open TCP/UDP ports that are registered with the port-filter database.

show control-plane transit counters

Displays the control plane packet counters for the control plane transit subinterface.


DB-408

May 2008

Debug Commands debug cops

debug cops To display a one-line summary of each Common Open Policy Service (COPS) message sent from and received by the router, use the debug cops command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cops [detail] no debug cops [detail]

Syntax Description

detail

Defaults

COPS process debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T


12.2(33)SRA


12.2SX


(Optional) Displays additional debug information, including the contents of COPS and Resource Reservation Protocol (RSVP) messages.

Usage Guidelines

To generate a complete record of the policy process, enter this command and, after entering a carriage return, enter the additional command debug ip rsvp policy.

Examples

This first example displays the one-line COPS message summaries, as the router goes through six different events. Router# debug cops COPS debugging is on

Event 1

The router becomes configured to communicate with a policy server: Router# configure terminal Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)# ip rsvp policy cops servers 2.0.0.1 Router(config)# 15:13:45:COPS: Opened TCP connection to 2.0.0.1/3288


DB-409


15:13:45:COPS: ** 15:13:45:COPS OPN 15:13:45:COPS: ** 15:13:45:COPS CAT Router(config)#

SENDING MESSAGE ** message, Client-type:1, Length:28. Handle:[NONE] RECEIVED MESSAGE ** message, Client-type:1, Length:16. Handle:[NONE]

Event 2

The router receives a Path message: 15:13:53:COPS:** SENDING MESSAGE ** 15:13:53:COPS REQ message, Client-type:1, Length:216. Handle:[ 00 00 04 01] 15:13:53:COPS:** RECEIVED MESSAGE ** 15:13:53:COPS DEC message, Client-type:1, Length:104. Handle:[ 00 00 04 01] Router(config)#

Event 3

The router receives a unicast FF Resv message: 15:14:00:COPS:** SENDING MESSAGE ** 15:14:00:COPS REQ message, Client-type:1, Length:148. Handle:[ 00 00 05 01] 15:14:00:COPS:** RECEIVED MESSAGE ** 15:14:00:COPS DEC message, Client-type:1, Length:64. Handle:[ 00 00 05 01] 15:14:00:COPS:** SENDING MESSAGE ** 15:14:00:COPS RPT message, Client-type:1, Length:24. Handle:[ 00 00 05 01] Router(config)#

Event 4

The router receives a Resv tear: 15:14:06:COPS:** SENDING MESSAGE ** 15:14:06:COPS DRQ message, Client-type:1, Length:24. Handle:[ 00 00 05 01] Router(config)#

Event 5

The router receives a Path tear: 15:14:11:COPS:** SENDING MESSAGE ** 15:14:11:COPS DRQ message, Client-type:1, Length:24. Handle:[ 00 00 04 01] Router(config)#

Event 6

The router gets configured to cease communicating with the policy server: Router(config)# no ip rsvp policy cops servers 15:14:23:COPS:** SENDING MESSAGE ** 15:14:23:COPS CC message, Client-type:1, Length:16. Handle:[NONE] 15:14:23:COPS:Closed TCP connection to 2.0.0.1/3288 Router(config)#


DB-410

May 2008


This second example uses the detail keyword to display the contents of the COPS and RSVP messages, and additional debugging information: Router# debug cops detail COPS debugging is on 02:13:29:COPS:** SENDING MESSAGE ** COPS HEADER:Version 1, Flags 0, Opcode 1 (REQ), Client-type:1, Length:216 HANDLE (1/1) object. Length:8. 00 00 21 01 CONTEXT (2/1) object. Length:8. R-type:5. M-type:1 IN_IF (3/1) object. Length:12. Address:10.1.2.1. If_index:4 OUT_IF (4/1) object. Length:12. Address:10.33.0.1. If_index:3 CLIENT SI (9/1) object. Length:168. CSI data: 02:13:29: SESSION type 1 length 12: 02:13:29: Destination 10.33.0.1, Protocol_Id 17, Don't Police , DstPort 44 02:13:29: HOP type 1 length 12:0A010201 02:13:29: :00000000 02:13:29: TIME_VALUES type 1 length 8 :00007530 02:13:29: SENDER_TEMPLATE type 1 length 12: 02:13:29: Source 10.31.0.1, udp_source_port 44 02:13:29: SENDER_TSPEC type 2 length 36: 02:13:29: version=0, length in words=7 02:13:29: Token bucket fragment (service_id=1, length=6 words 02:13:29: parameter id=127, flags=0, parameter length=5 02:13:29: average rate=1250 bytes/sec, burst depth=10000 bytes 02:13:29: peak rate =1250000 bytes/sec 02:13:29: min unit=0 bytes, max unit=1514 bytes 02:13:29: ADSPEC type 2 length 84: 02:13:29: version=0 length in words=19 02:13:29: General Parameters break bit=0 service length=8 02:13:29: IS Hops:1 02:13:29: Minimum Path Bandwidth (bytes/sec):1250000 02:13:29: Path Latency (microseconds):0 02:13:29: Path MTU:1500 02:13:29: Guaranteed Service break bit=0 service length=8 02:13:29: Path Delay (microseconds):192000 02:13:29: Path Jitter (microseconds):1200 02:13:29: Path delay since shaping (microseconds):192000 02:13:29: Path Jitter since shaping (microseconds):1200 02:13:29: Controlled Load Service break bit=0 service length=0 02:13:29:COPS:Sent 216 bytes on socket, 02:13:29:COPS:Message event! 02:13:29:COPS:State of TCP is 4 02:13:29:In read function 02:13:29:COPS:Read block of 96 bytes, num=104 (len=104) 02:13:29:COPS:** RECEIVED MESSAGE ** COPS HEADER:Version 1, Flags 1, Opcode 2 (DEC), Client-type:1, Length:104 HANDLE (1/1) object. Length:8. 00 00 21 01 CONTEXT (2/1) object. Length:8. R-type:1. M-type:1 DECISION (6/1) object. Length:8. COMMAND cmd:1, flags:0 DECISION (6/3) object. Length:56. REPLACEMENT 00 10 0E 01 61 62 63 64 65 66 67 68 69 6A 6B 6C 00 24 0C 02 00 00 00 07 01 00 00 06 7F 00 00 05 44 9C 40 00 46 1C 40 00 49 98 96 80 00 00 00 C8 00 00 01 C8 CONTEXT (2/1) object. Length:8. R-type:4. M-type:1 DECISION (6/1) object. Length:8. COMMAND cmd:1, flags:0 02:13:29:Notifying client (callback code 2) 02:13:29:COPS:** SENDING MESSAGE ** COPS HEADER:Version 1, Flags 1, Opcode 3 (RPT), Client-type:1, Length:24 HANDLE (1/1) object. Length:8. 00 00 21 01 REPORT (12/1) object. Length:8. REPORT type COMMIT (1)


DB-411


02:13:29:COPS:Sent 24 bytes on socket, 02:13:29:Timer for connection entry is zero

To see an example where the debug cops command is used along with the debug ip rsvp policy command, refer to the second example of the debug ip rsvp policy command.

Related Commands

Command

Description

debug ip rsvp policy

Displays debugging messages for RSVP policy processing.


DB-412

May 2008

Debug Commands debug cot

debug cot To display information about the Continuity Test (COT) functionality, use the debug cot command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug cot {api | dsp | queue | detail} no debug cot {api | dsp | queue | detail}

Syntax Description

api

Displays information about the COT application programming interface (API).

dsp

Displays information related to the COT/Digital Signal Processor configuration (DSP) interface. Typical DSP functions include data modems, voice codecs, fax modems and codecs, and low-level signaling such as channel-associated signaling (CAS)/R2.

queue

Display information related to the COT internal queue.

detail

Display information about COT internal detail; summary of the debug cot api, debug cot dsp, and debug cot queue commands.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(7)


12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug cot api command: Router# debug cot api COT API debugging is on 08:29:55: cot_request_handler(): CDB@0x60DEDE14, req(COT_CHECK_TONE_ON): 08:29:55: shelf 0 slot 0 appl_no 1 ds0 1 08:29:55: freqTX 2010 freqRX 1780 key 0xFFF1 duration 60000


debug cot api Field Descriptions

Field

Description

CDB

Internal controller information.

req

Type of COT operation requested.


DB-413


Table 58

debug cot api Field Descriptions (continued)

Field

Description

shelf

Shelf ID of the COT operation request.

slot

Designates the slot number, 1 to 4.

appl-no

Hardware unit that provides the external interface connections from a router to the network.

ds0

Number of the COT operation request.

key

COT operation identifier.

duration

Timeout duration of the COT operation.

freqTX

Requested transmit tone frequency.

freqRX

Requested receive tone frequency.

The following is sample output from the debug cot dsp command: Router# debug cot dsp Router# 00:10:42:COT:DSP (1/1) Allocated 00:10:43:In cot_callback 00:10:43: returned key 0xFFF1, status = 0 00:10:43:COT:Received DSP Q Event 00:10:43:COT:DSP (1/1) Done 00:10:43:COT:DSP (1/1) De-allocated


debug cot dsp Field Descriptions

Field

Description

DSP (1/1) Allocated

Slot and port of the DSP allocated for the COT operation.

Received DSP Q Event

Indicates the COT subsystem received an event from the DSP.

DSP (1/1) Done

Slot and port of the DSP transitioning to IDLE state.

DSP (1/1) De-allocated

Slot and port of the DSP de-allocated after the completion of the COT operation.

The following is sample output from the debug cot queue command: Router# debug cot queue Router# 00:11:26:COT(0x60EBB48C):Adding new request (0x61123DBC) to In Progress Q 00:11:26:COT(0x60EBB48C):Adding COT(0x61123DBC) to the Q head 00:11:27:In cot_callback 00:11:27: returned key 0xFFF1, status = 0


DB-414

May 2008



debug cot api Field Descriptions

Field

Description

COT

Internal COT operation request.

Adding new request

Internal COT operation request queue.

The following is sample output from the debug cot detail command. Router# debug cot detail Router# 00:04:57:cot_request_handler():CDB@0x60EBB48C, req(COT_CHECK_TONE_ON): 00:04:57: 00:04:57:

shelf 0 slot 0 appl_no 1 ds0 1 freqTX 1780 freqRX 2010 key 0xFFF1 duration 1000

00:04:57:COT:DSP (1/0) Allocated 00:04:57:COT:Request Transition to COT_WAIT_TD_ON 00:04:57:COT(0x60EBB48C):Adding new request (0x61123DBC) to In Progress Q 00:04:57:COT(0x60EBB48C):Adding COT(0x61123DBC) to the Q head 00:04:57:COT:Start Duration Timer for Check Tone Request 00:04:58:COT:Received Timer Event 00:04:58:COT:T24 Timer Expired 00:04:58:COT Request@ 0x61123DBC, CDB@ 0x60EBB48C, Params@0x61123E08 00:04:58: request type = COT_CHECK_TONE_ON 00:04:58: shelf 0 slot 0 appl_no 1 ds0 1 00:04:58: duration 1000 key FFF1 freqTx 1780 freqRx 2010 00:04:58: state COT_WAIT_TD_ON_CT 00:04:58: event_proc(0x6093B55C) 00:04:58:Invoke NI2 callback to inform COT request status 00:04:58:In cot_callback 00:04:58: returned key 0xFFF1, status = 0 00:04:58:Return from NI2 callback 00:04:58:COT:Request Transition to IDLE 00:04:58:COT:Received DSP Q Event 00:04:58:COT:DSP (1/0) Done 00:04:58:COT:DSP (1/0) De-allocated

Because the debug cot detail command is a summary of the debug cot api, debug cot dsp, and debug cot queue commands, the field descriptions are the same.


DB-415

Debug Commands debug cpp event

debug cpp event Note

Effective with Release 12.3(4)T, the debug cpp event command is no longer available in Cisco IOS 12.3(T) releases. To display general Combinet Proprietary Protocol (CPP) events, use the debug cpp event command in privileged EXEC mode. The no form of this command disables debugging output. debug cpp event no debug cpp event

Syntax Description


Command History

Release

Modification

11.2


12.3(4)T

This command is no longer available in Cisco IOS 12.(3)T releases.

12.2(33)SRA


12.2SX


Usage Guidelines

CPP allows a router to engage in negotiation over an ISDN B channel to establish connections with a Combinet bridge. The debug cpp event command displays events such as CPP sequencing, group creation, and keepalives.

Examples

One or more of the messages in Table 61 appear when you use the debug cpp event command. Each message begins with the short name of the interface the event occurred on (for example, SERIAL0:1 or BRI0:1) and might contain one or more packet sequence numbers or remote site names. Table 61

debug cpp event Messages

Message

Description

BRI0:1: negotiation complete

Call was set up on the interface (in this example, BRI0:1).

BRI0:1: negotiation timed out

Call timed out.

BRI0:1: sending negotiation packet

Negotiation packet was sent to set up the call.

BRI0:1: out of sequence packet - got 10, Packet was received that was out of sequence. The first range 1 8 number displayed in the message is the sequence number received, and the following numbers are the range of valid sequence numbers.


DB-416

May 2008

Debug Commands debug cpp event

Table 61

Related Commands

debug cpp event Messages (continued)

Message

Description

BRI0:1: Sequence timer expired Lost 11 Trying sequence 12

Timer expired before the packet was received. The first number displayed in the message is the sequence number of the packet that was lost, and the second number is the next sequence number.

BRI0:1: Line Integrity Violation

Router fails to maintain keepalives.

BRI0:1: create cpp group ber19 destroyed cpp group ber19

Dialer group is created on the remote site (in this example, ber19).

Command

Description

debug cpp negotiation

Displays CPP negotiation events.

debug cpp packet

Displays CPP packets.


DB-417

Debug Commands debug cpp negotiation

debug cpp negotiation Note

Effective with Release 12.3(4)T, the debug cpp negotiation command is no longer available in Cisco IOS 12.3T releases. To display Combinet Proprietary Protocol (CPP) negotiation events, use the debug cpp negotiation command in privileged EXEC mode. The no form of this command disables debugging output. debug cpp negotiation no debug cpp negotiation

Syntax Description


Command History

Release

Modification

11.2


12.3(4)T

This command is no longer available in Cisco IOS 12.3T releases.

12.2(33)SRA


12.2SX


Usage Guidelines

CPP allows a router to engage in negotiation over an ISDN B channel to establish connections with a Combinet bridge. The debug cpp negotiation command displays events such as the type of packet and packet size being sent.

Examples

The following is sample output from the debug cpp negotiation command. In this example, a sample connection is shown. Router# debug cpp negotiation %LINK-3-UPDOWN: Interface BRI0: B-Channel 2, changed state to down %LINK-3-UPDOWN: Interface BRI0, changed state to up %SYS-5-CONFIG_I: Configured from console by console %LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up BR0:1:(I) NEG packet - len 77 attempting proto:2 ether id:0040.f902.c7b4 port 1 number:5559876 port 2 number:5559876 origination port:1 remote name:berl9 password is correct

Table 62 describes the significant fields in the display.


DB-418

May 2008

Debug Commands debug cpp negotiation

Table 62

Related Commands

debug CPP negotiation Field Descriptions

Field

Description

BR0:1 (I) NEG packet - len 77

Interface name, packet type, and packet size.

attempting proto:

CPP protocol type.

ether id:

Ethernet address of the destination router.

port 1 number:

ISDN phone number of remote B channel #1.

port 2 number:

ISDN phone number of remote B channel #2.

origination port:

B channel 1 or 2 called.

remote name:

Remote site name to which this call is connecting.

password is correct

Password is accepted so the connection is established.

Command

Description

debug cot

Displays information about the COT functionality.

debug cpp packet

Displays CPP packets.


DB-419

Debug Commands debug cpp packet

debug cpp packet Note

Effective with Release 12.3(4)T, the debug cpp packet command is no longer available in Cisco IOS 12.3T Releases. To display Combinet Proprietary Protocol (CPP) packets, use the debug cpp packet command in privileged EXEC mode. The no form of this command disables debugging output. debug cpp packet no debug cpp packet

Syntax Description


Command History

Release

Modification

11.2


12.3(4)T

This command is no longer available in Cisco IOS 12.3T releases.

12.2(33)SRA


12.2SX


Usage Guidelines

CPP allows a router to engage in negotiation over an ISDN B channel to establish connections with a Combinet bridge. The debug cpp packet command displays the hexadecimal values of the packets.

Examples

The following is sample output from the debug cpp packet command. This example shows the interface name, packet type, packet size, and the hexadecimal values of the packet. Router# debug cpp packet BR0:1:input packet - len 60 00 00 00 00 00 00 00 40 F9 02 C7 B4 08 0.!6 00 01 08 00 06 04 00 02 00 40 F9 02 C7 B4 83 6C A1 02!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 64/66/68 ms BR0:1 output packet - len 116 06 00 00 40 F9 02 C7 B4 00 00 0C 3E 12 3A 08 00 45 00 00 64 00 01 00 00 FF 01 72 BB 83 6C A1 01

Related Commands

Command

Description

debug cot

Displays information about the COT functionality.

debug cpp negotiation

Displays CPP negotiation events.


DB-420

May 2008

Debug Commands debug credentials

debug credentials To set debugging on the credentials service that runs between the Cisco Unified CME CTL provider and CTL client or between the Cisco Unified SRST router and Cisco Unified CallManager, use the debug credentials command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug credentials no debug credentials

Syntax Description


Command Modes

Privileged EXEC

Command History

Cisco IOS Release

Modification

12.3(14)T

This command was introduced for Cisco Unified SRST.

12.4(4)XC

This command was introduced for Cisco Unified CME.

12.4(9)T

This command was integrated into Cisco IOS Release 12.4(9)T for Cisco Unified CME.

12.2SX


Usage Guidelines

Cisco Unified CME

Use this command with Cisco Unified CME phone authentication to monitor a CTL provider as it provides credentials to the CTL client. Cisco Unified SRST

Use this command to monitor Cisco Unified CallManager while it requests certificates from the Cisco Unified SRST router. It sets debugging on the credentials service that runs between the SRST router and Cisco Unified CallManager

Examples

Cisco Unified CME

The following sample output displays the CTL provider establishing a TLS session with the CTL client and providing all the relevant credentials for the services that are running on this router to the CTL client. Router# debug credentials Credentials server debugging is enabled May May May May

25 25 25 25

12:08:17.944: 12:08:17.948: 12:08:18.948: 12:08:19.948:

Credentials Credentials Credentials Credentials

service: service: service: service:

Start TLS Handshake 1 TLS Handshake returns TLS Handshake returns TLS Handshake returns

10.5.43.174 4374 OPSSLReadWouldBlockErr OPSSLReadWouldBlockErr OPSSLReadWouldBlockErr


DB-421

Debug Commands debug credentials

May 25 12:08:20.964: Credentials service: TLS Handshake completes

Cisco Unified SRST

The following is sample output showing the credentials service that runs between the Cisco Unified SRST router and Cisco Unified CallManager. The credentials service provides Cisco Unified CallManager with the certificate from the SRST router. Router# debug credentials Credentials server debugging is enabled Router# May 25 12:08:17.944: Credentials service: May 25 12:08:17.948: Credentials service: May 25 12:08:18.948: Credentials service: May 25 12:08:19.948: Credentials service: May 25 12:08:20.964: Credentials service:

Start TLS Handshake 1 10.5.43.174 4374 TLS Handshake returns OPSSLReadWouldBlockErr TLS Handshake returns OPSSLReadWouldBlockErr TLS Handshake returns OPSSLReadWouldBlockErr TLS Handshake completes


debug credentials Field Descriptions

Field

Description

Start TLS Handshake 1 10.5.43.174 4374

Indicates the beginning of the TLS handshake between the secure Cisco Unified SRST router and Cisco Unified CallManager. In this example, 1 indicates the socket, 10.5.43.174 is the IP address, and 4374 is the port of Cisco Unified CallManager.

TLS Handshake returns Indicates that the handshake is in process. OPSSLReadWouldBlockErr TLS Handshake completes

Related Commands

Indicates that the TLS handshake has finished and that the Cisco Unified CallManager has received the secure Cisco Unified SRST device certificate.

Command

Description

credentials

Enters credentials configuration mode to configure a Cisco Unified CME CTL provider certificate or a Cisco Unified SRST router certificate.

ctl-service admin

Specifies a user name and password to authenticate the CTL client during the CTL protocol.

ip source-address (credentials)

Enables the Cisco Unified CME or SRST router to receive messages through the specified IP address and port.

show credentials

Displays the credentials settings on a Cisco Unified CME or SRST router.

show debugging


trustpoint (credentials)

Specifies the name of the trustpoint to be associated with a Cisco Unified CME CTL provider certificate or with a Cisco Unified SRST router certificate.


DB-422

May 2008

Debug Commands debug crm

debug crm To troubleshoot the Carrier Resource Manager (CRM), use the debug crm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crm [all | default | detail | error [call [informational] | software [informational]] | function | inout] no debug crm

Syntax Description

all

(Optional) Displays all CRM debugging messages.

default

(Optional) Displays detail, error, and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays non-inout information related to call processing, such as call updates or call acceptance checking.

error

(Optional) Displays CRM error messages.

call

(Optional) Displays call processing errors.

informational

(Optional) Displays minor errors and major errors. Without the informational keyword, only major errors are displayed.

software

(Optional) Displays software errors.

function

(Optional) Displays CRM function names and exit points from each function so that call processing can be traced within the CRM subsystem.

inout

(Optional) Displays information from the functions that form the external interfaces of CRM to other modules or subsystems.

Defaults

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.3(8)T

The all, default, detail, error, call, informational, software, function, and inout keywords were added.

12.2SX


Usage Guidelines

Disable console logging and use buffered logging before using the debug crm command. Using the debug crm command generates a large volume of debugs, which can affect router performance.


DB-423


Examples

The following is sample output from the debug crm all command for an incoming ISDN call on a trunk group: Router# debug crm all 01:21:23: //-1/xxxxxxxxxxxx/CRM/crm_send_periodic_update: 01:21:23: //-1/xxxxxxxxxxxx/CRM/print_event: RouteLabel=2023, CarrierType=TDM, EventType=Single RouteLabel Update, EventReason=Both Capacity Update, Max Capacity mask 0x0000001F, Current Capacity Mask 0x0000001F 01:21:23: //-1/xxxxxxxxxxxx/CRM/crm_call_update: Increment the call count CarrierID=2023, TrunkGroupLabel=2023 Update is for TrunkGroupLabel, Mask=0x00000001 01:21:23: //-1/xxxxxxxxxxxx/CRM/crm_call_update: IncomingVoiceCalls=1 Router# 01:21:48: //-1/xxxxxxxxxxxx/CRM/crm_send_periodic_update: 01:21:48: //-1/xxxxxxxxxxxx/CRM/print_event: RouteLabel=2023, CarrierType=TDM, EventType=Single RouteLabel Update, EventReason=Both Capacity Update, Max Capacity mask 0x0000001F, Current Capacity Mask 0x0000001F 01:22:13: //-1/xxxxxxxxxxxx/CRM/crm_send_periodic_update: 01:22:13: //-1/xxxxxxxxxxxx/CRM/print_event: RouteLabel=2023, CarrierType=TDM, EventType=Single RouteLabel Update, EventReason=Both Capacity Update, Max Capacity mask 0x0000001F, Current Capacity Mask 0x0000001F Router# 01:22:18: //-1/xxxxxxxxxxxx/CRM/crm_call_update: Decrement the call count CarrierID=2023, TrunkGroupLabel=2023 Update is for TrunkGroupLabel, Mask=0x00000001 01:22:18: //-1/xxxxxxxxxxxx/CRM/crm_call_update: IncomingVoiceCalls=0


debug crm all Field Descriptions

Field

Description

//-1/xxxxxxxxxxxx/CRM/print_event:

The format of this message is //callid/GUID/CRM/function name: •

CallEntry ID is -1. This indicates that the CallEntry ID is unavailable.

•

GUID is xxxxxxxxxxxxxxxxx. This indicates that the GUID is unavailable.

•

CRM is the module name.

•

The print_event: field shows that the CRM is showing the print event function.

RouteLabel

Either the trunk group label or carrier ID.

CarrierType

Indicates the type of trunk.

EventType

Indicates if a single route or all routes are updated.

EventReason

Shows the reason for this event being sent.


DB-424

May 2008


Related Commands

Command

Description

max-calls

Specifies the maximum number of calls the trunk group can handle.


DB-425

Debug Commands debug crypto ace b2b

debug crypto ace b2b To enable IPSec VPN SPA debugging for a Blade Failure Group, use the debug crypto ace b2b command in privileged EXEC mode. debug crypto ace b2b

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(18)SXE2


12.2(33)SRA


12.2SX


Examples

The following example enables IPSec VPN SPA debugging for a Blade Failure Group: Router# debug crypto ace b2b ACE B2B Failover debugging is on

Related Commands

Command

Description

linecard-group feature card

Assigns a group ID to a Blade Failure Group.

show crypto ace redundancy

Displays information about a Blade Failure Group.

show redundancy linecard-group

Displays the components of a Blade Failure Group.


DB-426

May 2008

Debug Commands debug crypto condition unmatched

debug crypto condition unmatched To display crypto conditional debug messages when context information is unavailable to check against debug conditions, use the debug crypto condition unmatched command in privileged EXEC mode. To disable debugging, use the no form of this command. debug crypto condition unmatched [isakmp | ipsec | engine] no debug crypto condition unmatched [isakmp | ipsec | engine]

Syntax Description

isakmp | ipsec | engine

Defaults

Debug messages that do not have context information to match any debug conditions (filters) will not be printed.

Command Modes

Privileged EXEC

Command History

Release

(Optional) One or more of these keywords can be enabled to display debug messages for the specified areas. If none of these keywords are entered, debug messages for all crypto areas will be shown.

Modification

12.3(2)T


12.2(18)SXD

This command was integrated into Cisco IOS Release 12.2(18)SXD.

12.2SX


Usage Guidelines

After the debug crypto condition command has been enabled, you can use the debug crypto condition unmatched command to define whether the debug output is being printed when no context information is available in the code to check against the debug filters. For example, if the crypto engine’s connection-ID is the filter that the debug conditions are being checked against, the debug crypto condition unmatched command displays debug messages in the early negotiation phase when a connection-ID is unavailable to check against debug conditions.

Examples

The following example shows how to enable debug messages for all crypto-related areas: Router# debug crypto condition unmatched

Related Commands

Command

Description

debug crypto condition

Defines conditional debug filters.

show crypto debug-condition

Displays crypto debug conditions that have already been enabled in the router.


DB-427

Debug Commands debug crypto condition unmatched

Command

Description

show crypto ipsec sa

Displays the settings used by current SAs.

show crypto isakmp sa

Displays all current IKE SAs at a peer.


DB-428

May 2008

Debug Commands debug crypto condition

debug crypto condition To define conditional debug filters, use the debug crypto condition command in privileged EXEC mode. To disable conditional debugging, use the no form of this command. debug crypto condition [connid integer engine-id integer] [flowid integer engine-id integer] [gdoi-group groupname] [isakmp profile profile-name] [fvrf string] [ivrf string] [local ipv4 ip-address] [peer [group string] [hostname string] [ipv4 ipaddress] [subnet subnet mask] [username string]] [spi integer] [reset] [unmatched [engine] [gdoi-group] [ipsec] [isakmp] [username string]] no debug crypto condition [connid integer engine-id integer] [flowid integer engine-id integer] [gdoi-group groupname] [isakmp profile profile-name] [fvrf string] [ivrf string] [local ipv4 ip-address] [peer [group string] [hostname string] [ipv4 ipaddress] [subnet subnet mask] [username string]] [spi integer] [reset] [unmatched [engine] [gdoi-group] [ipsec] [isakmp] [username string]]

Syntax Description

connid integer1

(Optional) Internet Key Exchange (IKE) and IP Security (IPSec) connection ID filter. Valid values range from 1 to 32766.

engine-id integer

(Optional) Crypto engine ID value, which can be retrieved via the show crypto isakmp sa detail command. Valid values are 1, which represents software engines, and 2, which represents hardware engines.

flowid integer

(Optional) IPSec flow-ID filter. Valid values range from 1 to 32766.

gdoi-group groupname

(Optional) Group Domain of Interpretation (GDOI) group filter. •

isakmp profile profile-name

The groupname value is the name of the GDOI group.

(Optional) Filter for Internet Security Association Key Management Protocol (ISAKMP) profile. •

The profile-name value is the name of the ISAKMP profile to be filtered.

fvrf string1

(Optional) Front-door virtual private network (VPN) routing and forwarding (FVRF) filter. The string argument must be the name string of an FVRF instance.

ivrf string1

(Optional) Inside VRF (IVRF) filter. The string argument must be the name string of an IVRF instance.

local ipv4 ip-address

(Optional) IKE local address filter. •

peer

1

The ip-address value is the IP address of the local crypto endpoint.

(Optional) IKE peer filter. At least one of the following keywords and arguments must be used: •

group string—Unity group name filter of the IKE peer.

•

hostname string—Fully qualified domain name (FQDN) host name filter of the IKE peer.

•

ipv4 ipaddress—IP address filter of the IKE peer.

•

subnet subnet mask—Range of IKE peer IP addresses.

•

username string—FQDN username filter of the IKE peer.


DB-429


spi integer1

(Optional) Security policy index (SPI) filter. The integer must be a 32-bit unsigned integer.

reset

(Optional) Deletes all crypto debug filters. It is suggested that you turn off all crypto global debugging before using this keyword; otherwise, your system may be flooded with debug messages.

Note

unmatched

username string

(Optional) Filters all debug messages or only specified debug messages by choosing any of the following keywords: •

engine—Output crypto engine debugs even if no context available.

•

gdoi-group—Output GDOI group debugs even if no match occurs.

•

ipsec—Output IPsec debugs even if no context available.

•

isakmp—Output IKE debugs even if no context available.

(Optional) XAUTH or PKI-aaa username filter.

1. Additional conditional filters (ipv4 address, subnet mask, username, hostname, group, connection-ID, flow-ID, SPI, FVRF, and IVRF) can be specified more than once by repeating the debug crypto condition command with any of the available filters.

Defaults

Crypto conditional debugging is not enabled.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(2)T


12.2(18)SXD


12.4(11)T

The gdoi-group groupname, isakmp profile profile-name, local ipv4 ip-address, unmatched, and username string keywords and arguments were added.

12.2SX

This command is supported in the Cisco IOS 12.2SX family of releases. Support in a specific 12.2SX release is dependent on your feature set, platform, and platform hardware.

Usage Guidelines

Note

Before enabling the debug crypto condition command, you must decide what debug condition types (also known as debug filters) and values will be used. The volume of debug messages is dependent on the number of conditions you define.

Specifying numerous debug conditions may consume CPU cycles and have a negative effect on router performance.


DB-430

May 2008


To begin crypto conditional debugging, you must also enable at least one global crypto debug command—debug crypto isakmp, debug crypto ipsec, and debug crypto engine; otherwise, conditional debugging will not occur. This requirement helps to ensure that the performance of the router will not be impacted when conditional debugging is not being used.

Note

Examples

Debug message filtering for hardware crypto engines is not supported.

The following example shows how to display debug messages when the peer IP address is 10.1.1.1, 10.1.1.2, or 10.1.1.3 and when the connection-ID 2000 of crypto engine 0 is used. This example also shows how to enable global debug crypto CLIs and enable the show crypto debug-condition command to verify conditional settings. Router# debug crypto condition connid 2000 engine-id 1 Router# debug crypto condition peer ipv4 10.1.1.1 Router# debug crypto condition peer ipv4 10.1.1.2 Router# debug crypto condition peer ipv4 10.1.1.3 Router# debug crypto condition unmatched ! Verify crypto conditional settings. Router# show crypto debug-condition Crypto conditional debug currently is turned ON IKE debug context unmatched flag:ON IPsec debug context unmatched flag:ON Crypto Engine debug context unmatched flag:ON IKE peer IP address filters: 10.1.1.1 10.1.1.2 10.1.1.3 Connection-id filters:[connid:engine_id]2000:1, ! Enable global crypto CLIs to start conditional debugging. Router# debug crypto isakmp Router# debug crypto ipsec Router# debug crypto engine

The following example shows how to disable all crypto conditional settings via the reset keyword: Router# Router# Router# Router#

no debug crypto isakmp no debug crypto ipsec no debug crypto engine debug crypto condition reset

! Verify that all crypto conditional settings have been disabled. Router# show crypto debug-condition Crypto conditional debug currently is turned OFF IKE debug context unmatched flag:OFF IPsec debug context unmatched flag:OFF Crypto Engine debug context unmatched flag:OFF


DB-431


Related Commands

Command

Description

show crypto debug-condition

Displays crypto debug conditions that have already been enabled in the router.

show crypto debug-condition unmatched

Displays crypto conditional debug messages when context information is unavailable to check against debug conditions.

show crypto ipsec sa

Displays the settings used by current SAs.

show crypto isakmp sa

Displays all current IKE SAs at a peer.


DB-432

May 2008

Debug Commands debug crypto ctcp

debug crypto ctcp To display information about a Cisco Tunnel Control Protocol (cTCP) session, use the debug crypto ctcp command in privileged EXEC mode. To turn off debugging, use the no form of this command. debug crypto ctcp no debug crypto ctcp

Syntax Description


Command Default

Debugging is turned off.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T


12.2SX


Usage Guidelines

You can use this command if a cTCP session fails to come up.

Examples

The following example shows that debugging has been turned on for a cTCP session: Router# debug crypto ctcp

Related Commands

Command

Description

crypto ctcp

Configures cTCP encapsulation for Easy VPN.


DB-433

Debug Commands debug crypto engine accelerator logs

debug crypto engine accelerator logs To enable logging of commands and associated parameters sent from the virtual private network (VPN) module driver to the VPN module hardware using a debug flag, use the debug crypto engine accelerator logs command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto engine accelerator logs no debug crypto engine accelerator logs

Syntax Description


Defaults

The logging of commands sent from the VPN module driver to the VPN module hardware is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)XC

This command was introduced on the Cisco 1720 and Cisco 1750 routers.

12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug crypto engine accelerator logs command when encryption traffic is sent to the router and a problem with the encryption module is suspected. This command is intended only for Cisco TAC personnel to collect debugging information.

Examples

The debug crypto engine accelerator logs command uses a debug flag to log commands and associated parameters sent from the VPN module driver to the VPN module hardware as follows: Router# debug crypto engine accelerator logs encryption module logs debugging is on

Related Commands

Command

Description

crypto engine accelerator

Enables or disables the crypto engine accelerator if it exists.

show crypto engine accelerator logs

Prints information about the last 32 CGX Library packet processing commands, and associated parameters sent from the VPN module driver to the VPN module hardware.


DB-434

May 2008

Debug Commands debug crypto engine accelerator logs

Command

Description

show crypto engine accelerator sa-database

Prints active (in-use) entries in the platform-specific VPN module database.

show crypto engine configuration

Displays the Cisco IOS crypto engine of your router.


DB-435

Debug Commands debug crypto engine

debug crypto engine To display debugging messages about crypto engines, which perform encryption and decryption, use the debug crypto engine command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto engine no debug crypto engine

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug crypto engine command to display information pertaining to the crypto engine, such as when Cisco IOS software is performing encryption or decryption operations. The crypto engine is the actual mechanism that performs encryption and decryption. A crypto engine can be software or a hardware accelerator. Some platforms can have multiple crypto engines; therefore, the router will have multiple hardware accelerators.

Examples

The following is sample output from the debug crypto engine command. The first sample output shows messages from a router that successfully generates Rivest, Shamir, and Adelma (RSA) keys. The second sample output shows messages from a router that decrypts the RSA key during Internet Key Exchange (IKE) negotiation. Router# debug crypto engine 00:25:13:CryptoEngine0:generate key pair 00:25:13:CryptoEngine0:CRYPTO_GEN_KEY_PAIR 00:25:13:CRYPTO_ENGINE:key process suspended and continued 00:25:14:CRYPTO_ENGINE:key process suspended and continuedcr Router# debug crypto engine 00:27:45:%SYS-5-CONFIG_I:Configured from console by console 00:27:51:CryptoEngine0:generate alg parameter 00:27:51:CRYPTO_ENGINE:Dh phase 1 status:0 00:27:51:CRYPTO_ENGINE:Dh phase 1 status:0 00:27:51:CryptoEngine0:generate alg parameter 00:27:52:CryptoEngine0:calculate pkey hmac for conn id 0


DB-436

May 2008

Debug Commands debug crypto engine

00:27:52:CryptoEngine0:create ISAKMP SKEYID for conn id 1 00:27:52:Crypto engine 0:RSA decrypt with public key 00:27:52:CryptoEngine0:CRYPTO_RSA_PUB_DECRYPT 00:27:52:CryptoEngine0:generate hmac context for conn id 1 00:27:52:CryptoEngine0:generate hmac context for conn id 1 00:27:52:Crypto engine 0:RSA encrypt with private key 00:27:52:CryptoEngine0:CRYPTO_RSA_PRIV_ENCRYPT 00:27:53:CryptoEngine0:clear dh number for conn id 1 00:27:53:CryptoEngine0:generate hmac context for conn id 1 00:27:53:validate proposal 0 00:27:53:validate proposal request 0 00:27:54:CryptoEngine0:generate hmac context for conn id 1 00:27:54:CryptoEngine0:generate hmac context for conn id 1 00:27:54:ipsec allocate flow 0 00:27:54:ipsec allocate flow 0

Related Commands

Command

Description

crypto key generate rsa

Generates RSA key pairs.


DB-437

Debug Commands debug crypto error

debug crypto error To enable error debugging for a crypto area, use the debug crypto error command in privileged EXEC mode. To disable crypto error debugging, use the no form of this command. debug crypto {isakmp | ipsec | engine} error no debug crypto {isakmp | ipsec | engine} error

Syntax Description

isakmp

Debug messages are shown for Internet Key Exchange (IKE)-related error operations only.

ipsec

Debug messages are shown for IP Security (IPSec)-related error operations only.

engine

Debug messages are shown for crypto engine-related error operations only.

Defaults

Crypto error debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(2)T


12.2(18)SXD

This command was integrated into Cisco IOS Release 12.2(!8)SXD.

12.2SX


Usage Guidelines

The debug crypto error command will display only error-related debug messages; that is, an error debug will not be shown if the operation is functioning properly. This command should be used when debug conditions cannot be determined; for example, enable this command when a random, small subset of IKE peers is failing negotiation.

Examples

Note

The global crypto command-line interfaces (CLIs) (the debug crypto isakmp, debug crypto ipsec, and debug crypto engine commands) will override the debug crypto error command. Thus, this command should not be used in conjunction with the global CLIs because you may overwhelm the router.

Note

Debug message filtering for crypto hardware engines is not supported.

The following example shows how to enable IPSec-related error messages:


DB-438

May 2008

Debug Commands debug crypto error

Router# debug crypto error ipsec error


DB-439

Debug Commands debug crypto gdoi

debug crypto gdoi To display information about a Group Domain of Interpretation (GDOI) configuration, use the debug crypto gdoi command in privileged EXEC mode. To disable crypto GDOI debugging, use the no form of this command. debug crypto gdoi [detail | error | event | gm | infra | ks [coop] | packet | replay | terse] no debug crypto gdoi [detail | error | event | gm | infra | ks [coop] | packet | replay | terse]

Syntax Description

detail

(Optional) Displays detailed debug information.

error

(Optional) Displays information about error debugs.

event

(Optional) Displays user-level information.

gm

(Optional) Displays information about group members.

infra

(Optional) Displays information about the GDOI infrastructure.

ks

(Optional) Displays information about key servers.

coop

(Optional) Displays information about cooperative key servers.

packet

(Optional) Displays information about packet-level debugs (administrator-level information).

replay

(Optional) Displays information about the pseudotime stamp that is contained in a packet.

terse

(Optional) Displays lowest-level debugs (message-level information).

Note

The detail, error, event, packet, and terse keywords can be used with the other nonlevel keywords (for example, gm error, infra error, ks coop event, replay error).

Command Default


Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

Modification

12.4(6)T


12.4(11)T

The detail, error, event, gm, infra, ks, coop, packet, replay, and terse keywords were added.

12.2SX


Using this command displays various GDOI debugs. For debugging information for cooperative key servers, use the debug crypto gdoi ks coop command.


DB-440

May 2008


Examples

The following example shows group member registration debug output: Router# debug crypto gdoi 00:00:40: 00:00:40: 10.0.3.1 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 10.0.3.1

GDOI:(0:0:N/A:0):GDOI group diffint %CRYPTO-5-GM_REGSTER: Start registration for group diffint using address %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is ON GDOI:(0:1001:HW:0:3333):beginning GDOI exchange, M-ID of 1167145075 GDOI: Group Number is 3333 GDOI:(0:1001:HW:0:3333):GDOI: GDOI ID sent successfully GDOI:(0:1001:HW:0:3333):processing GDOI SA Payload, message ID + 1167145075 GDOI:(0:1001:HW:0):processing GDOI SA KEK Payload GDOI:(0:0:N/A:0): KEK_ALGORITHM 5 GDOI:(0:0:N/A:0): KEY_LENGTH 24 GDOI:(0:0:N/A:0): KEY_LIFETIME 299 GDOI:(0:0:N/A:0): SIG_HASH_ALG 2 GDOI:(0:0:N/A:0): SIG_ALG 1 GDOI:(0:0:N/A:0): SIG_KEY_LEN 94 GDOI:(0:0:N/A:0): Completed KEK Processing GDOI:(0:1001:HW:0):processing GDOI SA TEK Payload GDOI:(0:1001:HW:0:3333): Completed TEK Processing GDOI:(0:1001:HW:0):processing GDOI SA TEK Payload GDOI:(0:1001:HW:0:3333): Completed TEK Processing GDOI:(0:1001:HW:0:3333):GDOI ACK sent successfully by GM GDOI:received payload type 18 GDOI:(0:1001:HW:0:3333):processing GDOI Seq Payload, message_id 1167145075 GDOI:(0:1001:HW:0:3333):Completed SEQ Processing for seq 0 GDOI:received payload type 17 GDOI:(0:1001:HW:0:3333):processing GDOI KD Payload, message_id 1167145075 GDOI:(0:1001:HW:0:3333):processing GDOI Key Packet, message_id 38649336 GDOI:(0:1001:HW:0:3333):procesing TEK KD: spi is 56165461, spi GDOI:(0:1001:HW:0:3333):TEK Integrity Key 20 bytes GDOI:(0:1001:HW:0:3333):Completed KeyPkt Processing GDOI:(0:1001:HW:0:3333):processing GDOI Key Packet, message_id 38649336 GDOI:(0:1001:HW:0:3333):procesing TEK KD: spi is 56165522, spi GDOI:(0:1001:HW:0:3333):TEK Integrity Key 20 bytes GDOI:(0:1001:HW:0:3333):Completed KeyPkt Processing GDOI:(0:1001:HW:0:3333):processing GDOI Key Packet, message_id 38649336 GDOI:(0:1001:HW:0:3333): Processing KEK KD GDOI:(0:1001:HW:0:3333):KEK Alg Key 32 bytes GDOI:(0:1001:HW:0:3333):KEK Sig Key 94 bytes GDOI:(0:1001:HW:0:3333):Completed KeyPkt Processing %GDOI-5-GM_REGS_COMPL: Registration complete for group diffint using address

enc(config-if)# 00:00:40: GDOI:(0:0:N/A:0):Registration installed 2 new ipsec SA(s) for group diffint.

The following output example shows key server registration debugs: Router# debug crypto gdoi 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40: 00:00:40:

GDOI:(0:1001:HW:0):processing GDOI ID payload, message ID = 1167145075 GDOI:(0:1001:HW:0):The GDOI ID is a Number: 3333 GDOI:(0:0:N/A:0): Adding KEK Policy to the current ks_group GDOI:(0:0:N/A:0):Setting MULTICAST TEK rekey lifetime 30 GDOI:(0:0:N/A:0):Setting MULTICAST TEK rekey lifetime 30 GDOI:(0:1001:HW:0:3333):GDOI SA sent successfully by KS GDOI:(0:1001:HW:0:3333):GDOI KD sent successfully by KS

The following output example shows group member rekey debugs:


DB-441


Router# debug crypto gdoi 00:02:00: GDOI:(0:1002:HW:0):Received Rekey Message! 00:02:00: GDOI:(0:1002:HW:0):Signature Valid! 00:02:00: GDOI:received payload type 18 00:02:00: GDOI:(0:1002:HW:0):processing GDOI Seq Payload, message_id 0 00:02:00: GDOI:(0:1002:HW:0):Completed SEQ Processing for seq 8 00:02:00: GDOI:(0:1002:HW:0):processing GDOI SA Payload, message ID + 0 00:02:00: GDOI:(0:1002:HW:0):processing GDOI SA KEK Payload 00:02:00: GDOI:(0:1002:HW:0): KEK_ALGORITHM 5 00:02:00: GDOI:(0:1002:HW:0): KEY_LENGTH 24 00:02:00: GDOI:(0:1002:HW:0): KEY_LIFETIME 219 00:02:00: GDOI:(0:1002:HW:0): SIG_HASH_ALG 2 00:02:00: GDOI:(0:1002:HW:0): SIG_ALG 1 00:02:00: GDOI:(0:1002:HW:0): Completed KEK Processing 00:02:00: GDOI:(0:1002:HW:0):processing GDOI SA TEK Payload 00:02:00: GDOI:(0:1002:HW:0): Completed TEK Processing 00:02:00: GDOI:(0:1002:HW:0):processing GDOI SA TEK Payload 00:02:00: GDOI:(0:1002:HW:0): Completed TEK Processing 00:02:00: GDOI:received payload type 17 00:02:00: GDOI:(0:1002:HW:0):processing GDOI KD Payload, message_id 0 00:02:00: GDOI:(0:1002:HW:0):processing GDOI Key Packet, message_id 38649336 00:02:00: GDOI:(0:1002:HW:0):procesing TEK KD: spi is 49193284, spi 00:02:00: GDOI:(0:1002:HW:0):TEK Integrity Key 20 bytes 00:02:00: GDOI:(0:1002:HW:0):Completed KeyPkt Processing enc(config-if)# 00:02:00: GDOI:(0:1002:HW:0):processing GDOI Key Packet, message_id 38649336 00:02:00: GDOI:(0:1002:HW:0):procesing TEK KD: spi is 49193345, spi 00:02:00: GDOI:(0:1002:HW:0):TEK Integrity Key 20 bytes 00:02:00: GDOI:(0:1002:HW:0):Completed KeyPkt Processing 00:02:00: GDOI:(0:1002:HW:0):processing GDOI Key Packet, message_id 38649336 00:02:00: GDOI:(0:1002:HW:0): Processing KEK KD 00:02:00: GDOI:(0:1002:HW:0):Completed KeyPkt Processing


DB-442

May 2008

Debug Commands debug crypto ha

debug crypto ha To display crypto high availability debugging information, use the debug crypto ha command in privileged EXEC mode. To disable debugging messages, use the no form of this command. debug crypto ha no debug crypto ha

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(11)T


12.2SX


Examples

The following example is sample output from the debug crypto ha command: Router# debug crypto ha Active router: Router# show debug Cryptographic Subsystem: Crypto High Availability Manager debugging is on vrf-lite-R1# *Sep 28 21:27:50.899:Sending IKE Add SA Message *Sep 28 21:27:50.899:HA Message 0:flags=0x01 len=394 HA_IKE_MSG_ADD_SA (2) *Sep 28 21:27:50.899: ID:04000003 *Sep 28 21:27:50.899: attr HA_IKE_ATT_MY_COOKIE (2) len 8 *Sep 28 21:27:50.899: 9B 1A 76 AA 99 11 1A 1F *Sep 28 21:27:50.899: attr HA_IKE_ATT_HIS_COOKIE (3) len 8 *Sep 28 21:27:50.899: E2 A2 A3 5F 53 1D EA 15 *Sep 28 21:27:50.899: attr HA_IKE_ATT_SRC (4) len 4 *Sep 28 21:27:50.899: 04 00 00 05 *Sep 28 21:27:50.899: attr HA_IKE_ATT_DST (5) len 4 *Sep 28 21:27:50.899: 04 00 00 03 *Sep 28 21:27:50.899: attr HA_IKE_ATT_PEER_PORT (6) len 2 *Sep 28 21:27:50.899: 01 F4 *Sep 28 21:27:50.899: attr HA_IKE_ATT_F_VRF (7) len 1 *Sep 28 21:27:50.899: 00 *Sep 28 21:27:50.899: attr HA_IKE_ATT_INIT_OR_RESP (8) len 1 *Sep 28 21:27:50.899: 00 *Sep 28 21:27:50.899: attr HA_IKE_ATT_NAT_DISCOVERY (9) len 1 *Sep 28 21:27:50.899: 02 *Sep 28 21:27:50.899: attr HA_IKE_ATT_IDTYPE (38) len 1 *Sep 28 21:27:50.899: 01 *Sep 28 21:27:50.899: attr HA_IKE_ATT_PROTOCOL (39) len 1


DB-443

Debug Commands debug crypto ha

*Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep . . .

Related Commands

28 28 28 28 28 28 28 28 28 28 28 28 28 28 28

21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899: 21:27:50.899:

11 attr HA_IKE_ATT_PORT (40) len 2 01 F4 attr HA_IKE_ATT_ADDR (41) len 4 04 00 00 05 attr HA_IKE_ATT_MASK (42) len 4 00 00 00 00 attr HA_IKE_ATT_ID_STR (44) len 4 00 00 00 00 attr HA_IKE_ATT_PEERS_CAPABILITIES (11) len 4 00 00 07 7F attr HA_IKE_ATT_MY_CAPABILITIES (12) len 4 00 00 07 7F attr HA_IKE_ATT_STATE_MASK (13) len 4 00 00 27 FF

Command

Description

debug crypto ipsec ha

Enables debugging messages for IPSec high availability.

debug crypto isakmp ha

Enables debugging messages for ISAKMP high availability.


DB-444

May 2008

Debug Commands debug crypto ipsec client ezvpn

debug crypto ipsec client ezvpn To display information about voice control messages that have been captured by the Voice DSP Control Message Logger and about Cisco Easy VPN remote connections, use the debug crypto ipsec client ezvpn command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto ipsec client ezvpn no debug crypto ipsec client ezvpn

Syntax Description


Defaults


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(4)YA

This command was introduced on Cisco 806, Cisco 826, Cisco 827, and Cisco 828 routers; Cisco 1700 series routers; and Cisco uBR905 and Cisco uBR925 cable access routers.

12.2(13)T


12.3(4)T

This command was expanded to support the Easy VPN Remote feature.

12.2(33)SRA


12.2SX

This command is supported in the Cisco IOS 12.2SX family of releases. Support in a specific 12.2SX release is dependent on your feature set, platform, and platform hardware.

Usage Guidelines

To force the Voice DSP Contol Message Logger to reestablish the virtual private network (VPN) connections, use the clear crypto sa and clear crypto isakmp commands to delete the IPSec security associations and Internet Key Exchange (IKE) connections, respectively.

Examples

The following example shows debugging messages when the Voice DSP Contol Message Logger is turned on and typical debugging messages that appear when the VPN tunnel is created: Router# debug crypto ipsec client ezvpn EzVPN debugging is on router# 00:02:28: EZVPN(hw1): 00:02:28: EZVPN(hw1): 00:02:28: EZVPN(hw1): 00:02:28: EZVPN(hw1): 00:02:28: EZVPN(hw1):

Current State: IPSEC_ACTIVE Event: RESET ezvpn_close New State: CONNECT_REQUIRED Current State: CONNECT_REQUIRED


DB-445


00:02:28: 00:02:28: 00:02:28: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:29: 00:02:30: 00:02:30: 00:02:30: 00:02:30: 00:02:30: 00:02:30: 00:02:30:

EZVPN(hw1): Event: CONNECT EZVPN(hw1): ezvpn_connect_request EZVPN(hw1): New State: READY EZVPN(hw1): Current State: READY EZVPN(hw1): Event: MODE_CONFIG_REPLY EZVPN(hw1): ezvpn_mode_config EZVPN(hw1): ezvpn_parse_mode_config_msg EZVPN: Attributes sent in message: Address: 10.0.0.5 Default Domain: cisco.com EZVPN(hw1): ezvpn_nat_config EZVPN(hw1): New State: SS_OPEN EZVPN(hw1): Current State: SS_OPEN EZVPN(hw1): Event: SOCKET_READY EZVPN(hw1): No state change EZVPN(hw1): Current State: SS_OPEN EZVPN(hw1): Event: MTU_CHANGED EZVPN(hw1): No state change EZVPN(hw1): Current State: SS_OPEN EZVPN(hw1): Event: SOCKET_UP ezvpn_socket_up EZVPN(hw1): New State: IPSEC_ACTIVE

The following example shows the typical display for a VPN tunnel that is reset with the clear crypto ipsec client ezvpn command: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h:

EZVPN: Current State: READY EZVPN: Event: RESET ezvpn_reconnect_request ezvpn_close ezvpn_connect_request EZVPN: New State: READY EZVPN: Current State: READY EZVPN: Event: MODE_CONFIG_REPLY ezvpn_mode_config ezvpn_parse_mode_config_msg EZVPN: Attributes sent in message: DNS Primary: 172.16.0.250 DNS Secondary: 172.16.0.251 NBMS/WINS Primary: 172.16.0.252 NBMS/WINS Secondary: 172.16.0.253 Split Tunnel List: 1 Address : 172.16.0.128 Mask : 255.255.255.128 Protocol : 0x0 Source Port: 0 Dest Port : 0 Split Tunnel List: 2 Address : 172.16.1.128 Mask : 255.255.255.128 Protocol : 0x0 Source Port: 0 Dest Port : 0 Default Domain: cisco.com ezvpn_nat_config EZVPN: New State: SS_OPEN EZVPN: Current State: SS_OPEN EZVPN: Event: SOCKET_READY EZVPN: No state change EZVPN: Current State: SS_OPEN EZVPN: Event: SOCKET_READY EZVPN: No state change EZVPN: Current State: SS_OPEN EZVPN: Event: MTU_CHANGED


DB-446

May 2008


3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h: 3d17h:

EZVPN: EZVPN: EZVPN: EZVPN: EZVPN: EZVPN: EZVPN: EZVPN: EZVPN:

No state change Current State: SS_OPEN Event: SOCKET_UP New State: IPSEC_ACTIVE Current State: IPSEC_ACTIVE Event: MTU_CHANGED No state change Current State: IPSEC_ACTIVE Event: SOCKET_UP

The following example shows the typical display for a VPN tunnel that is removed from the interface with the no crypto ipsec client ezvpn command: 4d16h: 4d16h: 4d16h: 4d16h: 4d16h: 4d16h:

Related Commands

EZVPN: Current State: IPSEC ACTIVE EZVPN: Event: REMOVE INTERFACE CFG ezvpn_close_and_remove ezvpn_close ezvpn_remove EZVPN: New State: IDLE

Command

Description

debug crypto ipsec

Displays debugging messages for generic IPSec events.

debug crypto isakmp

Displays debugging messages for IKE events.


DB-447

Debug Commands debug crypto ipsec ha

debug crypto ipsec ha To enable debugging messages for IP Security (IPSec) high availability, use the debug crypto ipsec ha command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto ipsec ha [detail] [update] no debug crypto ipsec ha [detail] [update]

Syntax Description

detail


update

(Optional) Displays updates for inbound and outbound related data.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(11)T


12.2SX


Examples

The following example is sample output of the debug crypto ipsec ha command for both the active and stanby router: Active Router Router# debug crypto ipsec ha Crypto IPSEC High Availability debugging is on *Sep 29 17:03:01.851:IPSec HA (crypto_ha_ipsec_notify_add_sa):called *Sep 29 17:03:01.851:IPSec HA (crypto_ha_ipsec_notify_add_sa):New IPsec SA added... notifying HA Mgr Standby Router Router# debug crypto ipsec ha Crypto IPSEC High Availability debugging is on vrf-lite-R1# *Sep 29 17:03:01.031:IPSec HA (crypto_ha_ipsec_mgr_recv_add_sas):HA mgr wants to insert the following bundle *Sep 29 17:03:01.031:IPSec HA (crypto_ha_ipsec_mgr_recv_add_sas):This SA Supports DPD *Sep 29 17:03:01.031:IPSec HA (crypto_ha_ipsec_gen_sa):Sending Kei to IPSec num_kei 2 *Sep 29 17:03:01.039:IPSec HA (crypto_ha_ipsec_notify_add_sa):called *Sep 29 17:03:01.039:IPSec HA (crypto_ha_ipsec_notify_add_sa):operation not performed as standby ip 4.0.0.3

The following example is sample debug output with the detail keyword: Active Router


DB-448

May 2008


*Sep 29 17:05:48.803:IPSec HA (crypto_ha_ipsec_mgr_set_state_common):called for vip 4.0.0.3 *Sep 29 17:06:11.655:IPSec HA (crypto_ha_ipsec_mgr_bulk_sync_sas):Bulk sync request from standby for local addr 4.0.0.3 *Sep 29 17:06:44.059:IPSec HA (crypto_ha_ipsec_notify_add_sa):called *Sep 29 17:06:44.059:IPSec HA (crypto_ha_ipsec_notify_add_sa):New IPsec SA added... notifying HA Mgr Standby Router Router# debug crypto ipsec ha detail Crypto IPSEC High Availability Detail debugging is on vrf-lite-R1# *Sep 29 17:06:44.063:IPSec HA (crypto_ha_ipsec_mgr_recv_add_sas):HA mgr wants to insert the following bundle *Sep 29 17:06:44.063:IPSec HA (crypto_ha_ipsec_mgr_recv_add_sas):This SA Supports DPD *Sep 29 17:06:44.063:IPSec HA (crypto_ha_ipsec_gen_sa):Sending Kei to IPSec num_kei 2 *Sep 29 17:06:44.071:IPSec HA (crypto_ha_ipsec_notify_add_sa):called *Sep 29 17:06:44.071:IPSec HA (crypto_ha_ipsec_notify_add_sa):operation not performed as standby ip 4.0.0.3

The following example is sample debug output with the update keyword: Active Router *Sep 29 17:27:30.839:IPSec HA(check_and_send_replay_update):Replay triggered update seq_num 1000 last-sent 0 dir inbound *Sep 29 17:27:30.839:IPSec HA(create_update_struct):Sending inbound update *Sep 29 17:27:30.839:IPSec HA(send_update_struct): Outbound - New KB 0, New replay 0 Inbound - New KB 3998772, New replay 1000 *Sep 29 17:29:30.883:IPSec HA(check_and_send_replay_update):Replay triggered update seq_num 2000 last-sent 1000 dir inbound *Sep 29 17:29:30.883:IPSec HA(create_update_struct):Sending inbound update *Sep 29 17:29:30.883:IPSec HA(send_update_struct): Outbound - New KB 0, New replay 0 Inbound - New KB 3998624, New replay 2000 *Sep 29 17:30:30.899:IPSec HA(check_and_send_replay_update):Replay triggered update seq_num 3000 last-sent 2000 dir inbound *Sep 29 17:30:30.899:IPSec HA(create_update_struct):Sending inbound update *Sep 29 17:30:30.899:IPSec HA(send_update_struct): Outbound - New KB 0, New replay 0 Inbound - New KB 3998476, New replay 3000 *Sep 29 17:32:30.943:IPSec HA(check_and_send_replay_update):Replay triggered update seq_num 4000 last-sent 3000 dir inbound *Sep 29 17:32:30.943:IPSec HA(create_update_struct):Sending inbound update *Sep 29 17:32:30.943:IPSec HA(send_update_struct): Outbound - New KB 0, New replay 0 Inbound - New KB 3998327, New replay 4000 Standby Router *Sep 29 17:27:28.887:IPSec HA(crypto_ha_ipsec_mgr_recv_update_sa):called


DB-449


*Sep 29 17:27:28.887:IPSec HA(crypto_ha_ipsec_mgr_recv_update_sa):UPDATING INBOUND SA:ip = 4.0.0.3, protocol = 50, spi = B8A47EC9, NEW KB LIFE = 3998772, NEW REPLAY WINDOW START = 1000, *Sep 29 17:29:28.915:IPSec HA(crypto_ha_ipsec_mgr_recv_update_sa):called *Sep 29 17:29:28.915:IPSec HA(crypto_ha_ipsec_mgr_recv_update_sa):UPDATING INBOUND SA:ip = 4.0.0.3, protocol = 50, spi = B8A47EC9, NEW KB LIFE = 3998624, NEW REPLAY WINDOW START = 2000, *Sep 29 17:30:28.939:IPSec HA(crypto_ha_ipsec_mgr_recv_update_sa):called *Sep 29 17:30:28.939:IPSec HA(crypto_ha_ipsec_mgr_recv_update_sa):UPDATING INBOUND SA:ip = 4.0.0.3, protocol = 50, spi = B8A47EC9, NEW KB LIFE = 3998476, NEW REPLAY WINDOW START = 3000, *Sep 29 17:32:28.955:IPSec HA(crypto_ha_ipsec_mgr_recv_update_sa):called *Sep 29 17:32:28.955:IPSec HA(crypto_ha_ipsec_mgr_recv_update_sa):UPDATING INBOUND SA:ip = 4.0.0.3, protocol = 50, spi = B8A47EC9, NEW KB LIFE = 3998327, NEW REPLAY WINDOW START = 4000,

Related Commands

Command

Description

debug crypto ha

Displays crypto high availability debugging information.

debug crypto isakmp ha

Enables debugging messages for ISAKMP high availability.


DB-450

May 2008

Debug Commands debug crypto ipsec

debug crypto ipsec To display IP Security (IPSec) events, use the debug crypto ipsec command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto ipsec no debug crypto ipsec

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug crypto ipsec command. In this example, security associations (SAs) have been successfully established. Router# debug crypto ipsec

IPSec requests SAs between 172.21.114.123 and 172.21.114.67, on behalf of the permit ip host 172.21.114.123 host 172.21.114.67 command. It prefers to use the transform set esp-des w/esp-md5-hmac, but it will also consider ah-sha-hmac. 00:24:30: IPSEC(sa_request): , (key eng. msg.) src= 172.21.114.123, dest= 172.21.114.67, src_proxy= 172.21.114.123/255.255.255.255/0/0 (type=1), dest_proxy= 172.21.114.67/255.255.255.255/0/0 (type=1), protocol= ESP, transform= esp-des esp-md5-hmac , lifedur= 120s and 4608000kb, spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x4 00:24:30: IPSEC(sa_request): , (key eng. msg.) src= 172.21.114.123, dest= 172.21.114.67, src_proxy= 172.21.114.123/255.255.255.255/0/0 (type=1), dest_proxy= 172.21.114.67/255.255.255.255/0/0 (type=1)., protocol= AH, transform= ah-sha-hmac , lifedur= 120s and 4608000kb, spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x0.

Internet Key Exchange (IKE) asks for Service Provider Interfaces (SPIs) from IPSec. For inbound security associations, IPSec controls its own SPI space. 00:24:34: IPSEC(key_engine): got a queue event... 00:24:34: IPSEC(spi_response): getting spi 302974012ld for SA from 172.21.114.67 to 172.21.114.123 for prot 3 00:24:34: IPSEC(spi_response): getting spi 525075940ld for SA from 172.21.114.67 to 172.21.114.123 for prot 2

IKE will ask IPSec if it accepts the SA proposal. In this case, it will be the one sent by the local IPSec in the first place: 00:24:34: IPSEC(validate_proposal_request): proposal part #1, (key eng. msg.) dest= 172.21.114.67, src= 172.21.114.123, dest_proxy= 172.21.114.67/255.255.255.255/0/0 (type=1), src_proxy= 172.21.114.123/255.255.255.255/0/0 (type=1), protocol= ESP, transform= esp-des esp-md5-hmac , lifedur= 0s and 0kb, spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x4


DB-451


After the proposal is accepted, IKE finishes the negotiations, generates the keying material, and then notifies IPSec of the new security associations (one security association for each direction). 00:24:35: IPSEC(key_engine): got a queue event...

The following output pertains to the inbound SA. The conn_id value references an entry in the crypto engine connection table. 00:24:35: IPSEC(initialize_sas): , (key eng. msg.) dest= 172.21.114.123, src= 172.21.114.67, dest_proxy= 172.21.114.123/255.255.255.255/0/0 (type=1), src_proxy= 172.21.114.67/255.255.255.255/0/0 (type=1), protocol= ESP, transform= esp-des esp-md5-hmac , lifedur= 120s and 4608000 kb, spi= 0x120F043C(302974012), conn_id= 29, keysize= 0, flags= 0x4

The following output pertains to the outbound SA: 00:24:35: IPSEC(initialize_sas): , (key eng. msg.) src= 172.21.114.123, dest= 172.21.114.67, src_proxy= 172.21.114.123/255.255.255.255/0/0 (type=1), dest_proxy= 172.21.114.67/255.255.255.255/0/0 (type=1), protocol= ESP, transform= esp-des esp-md5-hmac , lifedur= 120s and 4608000kb, spi= 0x38914A4(59315364), conn_id= 30, keysize= 0, flags= 0x4

IPSec now installs the SA information into its SA database. 00:24:35: IPSEC(create_sa): sa created, (sa) sa_dest= 172.21.114.123, sa_prot= 50, sa_spi= 0x120F043C(302974012), sa_trans= esp-des esp-md5-hmac , sa_conn_id= 29 00:24:35: IPSEC(create_sa): sa created, (sa) sa_dest= 172.21.114.67, sa_prot= 50, sa_spi= 0x38914A4(59315364), sa_trans= esp-des esp-md5-hmac , sa_conn_id= 30

The following is sample output from the debug crypto ipsec command as seen on the peer router. In this example, IKE asks IPSec if it will accept an SA proposal. Although the peer sent two proposals, IPSec accepted the first proposal. 00:26:15: IPSEC(validate_proposal_request): proposal part #1, (key eng. msg.) dest= 172.21.114.67, src= 172.21.114.123, dest_proxy= 172.21.114.67/255.255.255.255/0/0 (type=1), src_proxy= 172.21.114.123/255.255.255.255/0/0 (type=1), protocol= ESP, transform= esp-des esp-md5-hmac , lifedur= 0s and 0kb, spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x4

IKE asks for SPIs. 00:26:15: IPSEC(key_engine): got a queue event... 00:26:15: IPSEC(spi_response): getting spi 59315364ld for SA from 172.21.114.123 to 172.21.114.67 for prot 3

IKE does the remaining processing, completing the negotiation and generating keys. It then tells IPSec about the new SAs. 00:26:15: IPSEC(key_engine): got a queue event...


DB-452

May 2008


The following output pertains to the inbound SA: 00:26:15: IPSEC(initialize_sas): , (key eng. msg.) dest= 172.21.114.67, src= 172.21.114.123, dest_proxy= 172.21.114.67/0.0.0.0/0/0 (type=1), src_proxy= 172.21.114.123/0.0.0.0/0/0 (type=1), protocol= ESP, transform= esp-des esp-md5-hmac , lifedur= 120s and 4608000kb, spi= 0x38914A4(59315364), conn_id= 25, keysize= 0, flags= 0x4

The following output pertains to the outbound SA: 00:26:15: IPSEC(initialize_sas): , (key eng. msg.) src= 172.21.114.67, dest= 172.21.114.123, src_proxy= 172.21.114.67/0.0.0.0/0/0 (type=1), dest_proxy= 172.21.114.123/0.0.0.0/0/0 (type=1), protocol= ESP, transform= esp-des esp-md5-hmac , lifedur= 120s and 4608000kb, spi= 0x120F043C(302974012), conn_id= 26, keysize= 0, flags= 0x4

IPSec now installs the SA information into its SA database: 00:26:15: IPSEC(create_sa): sa created, (sa) sa_dest= 172.21.114.67, sa_prot= 50, sa_spi= 0x38914A4(59315364), sa_trans= esp-des esp-md5-hmac , sa_conn_id= 25 00:26:15: IPSEC(create_sa): sa created, (sa) sa_dest= 172.21.114.123, sa_prot= 50, sa_spi= 0x120F043C(302974012), sa_trans= esp-des esp-md5-hmac , sa_conn_id= 26


DB-453

Debug Commands debug crypto ipv6 ipsec

debug crypto ipv6 ipsec To display IP Security (IPSec) events for IPv6 networks, use the debug crypto ipv6 ipsec command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto ipv6 ipsec no debug crypto ipv6 ipsec

Syntax Description


Command Default

Debugging for IPv6 IPSec events is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Usage Guidelines

Use this command to display IPSec events while setting up or removing policy definitions during OSPF configuration.

Examples

The following example enables the display of IPSec events for IPv6 networks: Router# debug crypto ipv6 ipsec

Related Commands

Command

Description

debug crypto engine

Displays debugging messages about crypto engines, which perform encryption and decryption.

debug crypto ipv6 packet

Displays debug messages for IPv6 packets allowing you to see the contents of packets outbound from a Cisco router when the remote node is not a Cisco node.

debug crypto socket

Displays communication between the client and IPSec during policy setup and removal processes.

debug ipv6 ospf authentication

Displays the interaction between OSPF and IPSec, including creation or removal of policies.


DB-454

May 2008

Debug Commands debug crypto ipv6 packet

debug crypto ipv6 packet To display the contents of IPv6 packets, use the debug crypto ipv6 packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto ipv6 packet no debug crypto ipv6 packet

Syntax Description


Command Default

Debugging for IPv6 IPSec packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Usage Guidelines

Consult Cisco Technical Support before using this command. Use this command to display the contents of IPv6 packets. This command is useful when the remote node is not a Cisco device and communication between the Cisco and non-Cisco router cannot be established. This command enables you to look at the contents of the packets outbound from the Cisco router. This command examines the content of every IPv6 packet and may slow network performance.

Examples

This example shows the ouptut of each packet when the debug crypto ipv6 packet command is enabled: Router# debug crypto ipv6 packet Crypto IPv6 IPSEC packet debugging is on Router# *Oct 30 16:57:06.330: IPSECv6:before Encapsulation of IPv6 packet: 0E37A7C0: 6E000000 00285901 0E37A7D0:FE800000 00000000 020A8BFF FED42C1D 0E37A7E0:FF020000 00000000 00000000 00000005 0E37A7F0:03010028 01010104 00000001 8AD80000 0E37A800:00000006 01000013 000A0028 0A0250CF 0E37A810:01010104 0A0250CF *Oct 30 16:57:06.330: IPSECv6:Encapsulated IPv6 packet : 0E37A7B0:6E000000 00403301 FE800000 00000000

n....(Y. ~...........~T,. ................ ...(.........X.. ...........(..PO ......PO

n....@3.~.......


DB-455

Debug Commands debug crypto ipv6 packet

0E37A7C0:020A8BFF FED42C1D FF020000 00000000 0E37A7D0:00000000 00000005 59040000 000022B8 0E37A7E0:0000001A 38AB1ED8 04C1C6FB FF1248CF 0E37A7F0:03010028 01010104 00000001 8AD80000 0E37A800:00000006 01000013 000A0028 0A0250CF 0E37A810:01010104 0A0250CF *Oct 30 16:57:11.914: IPSECv6:Before Decapsulation of IPv6 packet : 0E004A50: 6E000000 00403301 0E004A60:FE800000 00000000 023071FF FE7FE81D 0E004A70:FF020000 00000000 00000000 00000005 0E004A80:59040000 000022B8 00001D88 F5AC68EE 0E004A90:1AC00088 947C6BF2 03010028 0A0250CF 0E004AA0:00000001 E9080000 00000004 01000013 0E004AB0:000A0028 0A0250CF 01010104 01010104 0E004AC0: *Oct 30 16:57:11.914: IPSECv6:Decapsulated IPv6 packet : 0E004A70:6E000000 00285901 FE800000 00000000 0E004A80:023071FF FE7FE81D FF020000 00000000 0E004A90:00000000 00000005 03010028 0A0250CF 0E004AA0:00000001 E9080000 00000004 01000013 0E004AB0:000A0028 0A0250CF 01010104 01010104 0E004AC0: *Oct 30 16:57:16.330: IPSECv6:before Encapsulation of IPv6 packet: 0E003DC0: 6E000000 00285901 0E003DD0:FE800000 00000000 020A8BFF FED42C1D 0E003DE0:FF020000 00000000 00000000 00000005 0E003DF0:03010028 01010104 00000001 8AD80000 0E003E00:00000006 01000013 000A0028 0A0250CF 0E003E10:01010104 0A0250CF *Oct 30 16:57:16.330: IPSECv6:Encapsulated IPv6 packet : 0E003DB0:6E000000 00403301 FE800000 00000000 0E003DC0:020A8BFF FED42C1D FF020000 00000000 0E003DD0:00000000 00000005 59040000 000022B8 0E003DE0:0000001B F8E3C4E2 4CC4B690 DDF32B5C 0E003DF0:03010028 01010104 00000001 8AD80000 0E003E00:00000006 01000013 000A0028 0A0250CF 0E003E10:01010104 0A0250CF

Related Commands

....~T,......... ........Y....."8 ....8+.X.AF{..HO ...(.........X.. ...........(..PO ......PO

n....@3. ~........0q.~.h. ................ Y....."8....u,hn .@...|kr...(..PO ....i........... ...(..PO........

n....(Y.~....... .0q.~.h......... ...........(..PO ....i........... ...(..PO........

n....(Y. ~...........~T,. ................ ...(.........X.. ...........(..PO ......PO

n....@3.~....... ....~T,......... ........Y....."8 ....xcDbLD6.]s+\ ...(.........X.. ...........(..PO ......PO

Command

Description

debug crypto engine

Displays debugging messages about crypto engines, which perform encryption and decryption.

debug crypto ipv6 ipsec

Displays IPSec events for IPv6 networks.

debug crypto socket

Displays communication between the client and IPSec during policy setup and removal processes.


DB-456

May 2008

Debug Commands debug crypto isakmp ha

debug crypto isakmp ha To enable debugging messages for Internet Security Association and Key Management Protocol (ISAKMP) high availability, use the debug crypto isakmp ha command in privileged EXEC mode. To disable debugging messages, use the no form of this command. debug crypto isakmp ha [detail] no debug crypto isakmp ha [detail]

Syntax Description

detail

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(11)T


12.2SX


Examples


The following is sample output for a standby router from the debug crypto isakmp ha command: Active Router no debug message Standby Router Router# debug crypto isakmp ha Crypto ISAKMP High Availability debugging is on vrf-lite-R1# *Sep 28 21:54:41.815:IKE HA:(4.0.0.3) Adding STANDBY IKE SA *Sep 28 21:54:41.843:IKE HA:Create peer struct for local 4.0.0.3 remote 4.0.0.5 & locked *Sep 28 21:54:41.843:IKE HA:IKE SA inserted on standby with src = 4.0.0.5, dst = 4.0.0.3

The following sample output is displayed when the detail keyword is issued. (Note that debug output without issuing the detail keyword is the same as the debug output with the detail keyword.) Active Router Router# debug crypto isakmp ha detail Crypto ISAKMP High Availability detailed debugging is on vrf-lite-R1# *Sep 29 16:59:15.035:IKE HA:IKE SA is already failed over Standby Router Router# debug crypto isakmp ha detail Crypto ISAKMP High Availability detailed debugging is on vrf-lite-R2# *Sep 29 16:59:14.371:IKE HA:(4.0.0.3) Adding STANDBY IKE SA


DB-457

Debug Commands debug crypto isakmp ha

*Sep 29 16:59:14.411:IKE HA:Create peer struct for local 4.0.0.3 remote 4.0.0.5 & locked *Sep 29 16:59:14.411:IKE HA:IKE SA inserted on standby with src = 4.0.0.5, dst = 4.0.0.3

Related Commands

Command

Description

debug crypto ha

Displays crypto high availability debugging information.

debug crypto ipsec ha

Enables debugging messages for IPSec high availability.


DB-458

May 2008

Debug Commands debug crypto isakmp

debug crypto isakmp To display messages about Internet Key Exchange (IKE) events, use the debug crypto isakmp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto isakmp [aaa] no debug crypto isakmp [aaa]

Syntax Description

aaa

Command Modes

Privileged EXEC

Command History

Release

Modifications

11.3 T


12.2(15)T

The aaa keyword was added.

12.2(18)SXD


12.2(33)SRA


12.2SX


Examples

(Optional) Specifies accounting events.

The following is sample output from the debug crypto isakmp command for an IKE peer that initiates an IKE negotiation. First, IKE negotiates its own security association (SA), checking for a matching IKE policy. Router# debug crypto isakmp 20:26:58: 20:26:58: 20:26:58: 20:26:58: 20:26:58: 20:26:58: 20:26:58: 20:26:58:

ISAKMP (8): ISAKMP (8): ISAKMP (8): ISAKMP: ISAKMP: ISAKMP: ISAKMP: ISAKMP (8):

beginning Main Mode exchange processing SA payload. message ID = 0 Checking ISAKMP transform 1 against priority 10 policy encryption DES-CBC hash SHA default group 1 auth pre-share atts are acceptable. Next payload is 0

IKE has found a matching policy. Next, the IKE SA is used by each peer to authenticate the other peer. 20:26:58: 20:26:59: 20:26:59: 20:26:59: 20:26:59: 20:26:59: 20:26:59:

ISAKMP ISAKMP ISAKMP ISAKMP ISAKMP ISAKMP ISAKMP

(8): (8): (8): (8): (8): (8): (8):

SA is doing pre-shared key authentication processing KE payload. message ID = 0 processing NONCE payload. message ID = 0 SKEYID state generated processing ID payload. message ID = 0 processing HASH payload. message ID = 0 SA has been authenticated

Next, IKE negotiates to set up the IP Security (IPSec) SA by searching for a matching transform set. 20:26:59: ISAKMP (8): beginning Quick Mode exchange, M-ID of 767162845


DB-459

Debug Commands debug crypto isakmp

20:26:59: ISAKMP (8): processing SA payload. message ID = 767162845 20:26:59: ISAKMP (8): Checking IPSec proposal 1 20:26:59: ISAKMP: transform 1, ESP_DES 20:26:59: ISAKMP: attributes in transform: 20:26:59: ISAKMP: encaps is 1 20:26:59: ISAKMP: SA life type in seconds 20:26:59: ISAKMP: SA life duration (basic) of 600 20:26:59: ISAKMP: SA life type in kilobytes 20:26:59: ISAKMP: SA life duration (VPI) of 0x0 0x46 0x50 0x0 20:26:59: ISAKMP: authenticator is HMAC-MD5 20:26:59: ISAKMP (8): atts are acceptable.

A matching IPSec transform set has been found at the two peers. Now the IPSec SA can be created (one SA is created for each direction). 20:26:59: ISAKMP 20:26:59: ISAKMP 20:26:59: ISAKMP 20:26:59: ISAKMP 20:26:59: 20:26:59: 20:26:59: 20:26:59: 20:26:59: to 155.0.0.2 20:26:59: 20:26:59: 20:26:59:

(8): processing NONCE payload. message ID = 767162845 (8): processing ID payload. message ID = 767162845 (8): processing ID payload. message ID = 767162845 (8): Creating IPSec SAs inbound SA from 155.0.0.2 to 155.0.0.1 (proxy 155.0.0.2 to 155.0.0.1 ) has spi 454886490 and conn_id 9 and flags 4 lifetime of 600 seconds lifetime of 4608000 kilobytes outbound SA from 155.0.0.1 to 155.0.0.2 (proxy 155.0.0.1 ) has spi 75506225 and conn_id 10 and flags 4 lifetime of 600 seconds lifetime of 4608000 kilobytes

The following is sample output from the debug crypto isakmp command using the aaa keyword: Router# debug crypto isakmp aaa Start Example 01:38:55: ISAKMP AAA: Sent Accounting Message 01:38:55: ISAKMP AAA: Accounting message successful 01:38:55: ISAKMP AAA: Rx Accounting Message 01:38:55: ISAKMP AAA: Adding Client Attributes to Accounting Record 01:38:55: ISAKMP AAA: Accounting Started

Update Example 01:09:55: ISAKMP AAA: Accounting received kei with flags 0x1042 01:09:55: ISAKMP AAA: Updating Stats 01:09:55: Previous in acc (PKTS) IN: 10 OUT: 10 01:09:55: Traffic on sa (PKTS) IN: 176 OUT: 176

Related Commands

Command

Description

crypto isakmp profile

Defines an ISAKMP profile and audits IPSec user sessions.

crypto map (global IPSec)

Enters crypto map configuration mode and creates or modifies a crypto map entry, creates a crypto profile that provides a template for configuration of a dynamically created crypto map, or configures a client accounting list.


DB-460

May 2008

Debug Commands debug crypto key-exchange

debug crypto key-exchange To show Digital Signature Standard (DSS) public key exchange messages, use the debug crypto key-exchange command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto key-exchange no debug crypto key-exchange

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Encryption and authentication are provided by a software service on the router called a crypto engine. The crypto engine performs authentication through DSS public and private keys when a connection is set up. DSS is a means of sending a “signature” at the end of a message that positively identifies the author of the message. The signature cannot be forged or duplicated by others, so whoever received a message with a DSS signature knows exactly who sent the message. If the process of exchanging DSS public keys with a peer router by means of the config crypto key-exchange command is not successful, try to exchange DSS public keys again after enabling the debug crypto key-exchange command to help you diagnose the problem.

Examples

The following is sample output from the debug crypto key-exchange command. The first shows output from the initiating router in a key exchange. The second shows output from the passive router in a key exchange. The number of bytes received should match the number of bytes sent from the initiating side, although the number of messages can be different. Router# debug crypto key-exchange CRYPTO-KE: CRYPTO-KE: CRYPTO-KE: CRYPTO-KE: CRYPTO-KE:

Sent Sent Sent Sent Sent

4 bytes. 2 bytes. 2 bytes. 2 bytes. 64 bytes.

Router# debug crypto key-exchange CRYPTO-KE: CRYPTO-KE: CRYPTO-KE: CRYPTO-KE: CRYPTO-KE: CRYPTO-KE:

Related Commands

Received Received Received Received Received Received

4 bytes. 2 bytes. 2 bytes. 2 bytes. 49 bytes. 15 bytes.

Command

Description

debug crypto sesmgmt

Displays connection setup messages and their flow through the router.


DB-461

Debug Commands debug crypto mib

debug crypto mib To display debug messages for the IP Security (IPsec) MIB subsystem, use the debug crypto mib command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto mib [detail | error] no debug crypto mib [detail | error]

Syntax Description

detail

(Optional) Displays different events as they occur in the IPsec MIB subsystem. Note

error

Because the output for this keyword can be quite long, due consideration should be given to enabling debug crypto mib detail.

(Optional) Displays error events in the MIB agent.

Defaults

Message notification debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Examples

Modification

12.1(4)E


12.2(4)T


12.4(4)T

The detail and error keywords were added.

12.2SX


The following example shows IPsec MIB debug message notification being enabled: Router# debug crypto mib Crypto IPSec Mgmt Entity debugging is on

The following example shows that detailed information about events that are occurring in the subsystem has been requested: Router# debug crypto mib detail

The following example shows that information has been requested about error events in the MIB agent: Router# debug crypto mib error


DB-462

May 2008

Debug Commands debug crypto mib

Related Commands

Command

Description

show crypto mib ipsec flowmib history failure size

Displays the size of the IPSec failure history table.

show crypto mib ipsec flowmib history tunnel size

Displays the size of the IPSec tunnel history table.

show crypto mib ipsec flowmib version

Displays the IPSec Flow MIB version used by the router.


DB-463

Debug Commands debug crypto pki messages

debug crypto pki messages To display debugging messages for the details of the interaction (message dump) between the certification authority (CA) and the router, use the debug crypto pki messages command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto pki messages no debug crypto pki messages

Syntax Description


Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0


12.2(33)SRA


12.2SX


Usage Guidelines

The debug crypto pki messages command displays messages about the actual data being sent and received during public key infrastructure (PKI) transactions. This command is internal for use by Cisco support personnel. You can use the show crypto ca certificates command to display information about your certificate.

Examples

The following is sample output from the debug crypto pki messages command: Router# debug crypto pki messages Fingerprint: 2CFC6265 77BA6496 3AEFCB50 29BC2BF2 00:48:23:Write out pkcs#10 content:274 00:48:23:30 82 01 0E 30 81 B9 02 01 00 30 22 31 20 00:48:23:48 86 F7 0D 01 09 02 16 11 70 6B 69 2D 33 00:48:23:63 6F 2E 63 6F 6D 30 5C 30 0D 06 09 2A 86 00:48:23:01 05 00 03 4B 00 30 48 02 41 00 DD 2C C6 00:48:23:11 E2 81 95 01 6A 80 34 25 10 C4 5F 3D 8B 00:48:23:6C 2D 65 4C B6 A6 B0 02 1C B2 84 C1 C8 AC 00:48:23:30 98 CB 36 A2 47 4E 7E 6F C9 3E B8 26 BE 00:48:23:A0 32 30 10 06 09 2A 86 48 86 F7 0D 01 09 00:48:23:30 1E 06 09 2A 86 48 86 F7 0D 01 09 0E 31 00:48:23:0B 06 03 55 1D 0F 04 04 03 02 05 A0 30 0D 00:48:23:F7 0D 01 01 04 05 00 03 41 00 2C FD 88 2C 00:48:23:5C FD AE 52 8F 2C 13 95 9E 9D 8B A4 C9 48

30 36 48 35 33 A4 15 07 11 06 8A 32

1E 61 86 A5 1C 28 02 31 14 09 13 84

06 2E F7 3F 19 6E 03 03 0F 2A B6 BF

09 63 0D 0F 50 EF 01 13 30 86 81 05

2A 69 01 97 FD 9D 00 01 0D 48 88 03

86 73 01 6C 91 3B 01 63 30 86 EA 49


DB-464

May 2008

Debug Commands debug crypto pki messages

00:48:23:63 27 A3 AC 6D 74 EB 69 E3 06 E9 E4 9F 0A A8 FB 20 F0 02 03 00:48:23:BE 90 57 02 F2 75 8E 0F 16 60 10 6F BE 2B 00:48:23:Enveloped Data ... 00:48:23:30 80 06 09 2A 86 48 86 F7 0D 01 00:48:23:31 80 30 82 01 0F 02 01 00 30 78 00:48:23:04 06 13 02 55 53 31 0B 30 09 06 00:48:23:13 30 11 06 03 55 04 07 13 0A 53 00:48:23:31 15 30 13 06 03 55 04 0A 13 0C 00:48:23:74 65 6D 31 0E 30 0C 06 03 55 04 00:48:23:Signed Data 1382 bytes 00:48:23:30 80 06 09 2A 86 48 86 F7 0D 01 00:48:23:31 0E 30 0C 06 08 2A 86 48 86 F7 00:48:23:2A 86 48 86 F7 0D 01 07 01 A0 80 00:48:23:02 55 53 31 0B 30 09 06 03 55 04 00:48:23:33 34 5A 17 0D 31 30 31 31 31 35 00:48:23:31 20 30 1E 06 09 2A 86 48 86 F7 00:48:23:2D 33 36 61 2E 63 69 73 63 6F 2E 00:48:23:2A 86 48 86 F7 0D 01 01 01 05 00 00:48:23:2C C6 35 A5 3F 0F 97 6C 11 E2 81 00:48:23:3D 8B 33 1C 19 50 FD 91 6C 2D 65 00:48:23:86 F7 0D 01 01 01 05 00 04 40 C6 00:48:23:15 F7 3E 15 6D 71 E1 D0 13 2B 14 00:48:23:EF C2 D6 CB 91 39 19 F8 44 68 0E 00:48:23:3F EC C6 04 A5 D9 7C B1 56 47 3F 00:48:23:00 00 00:48:24:Received pki message:1778 types . . .

Related Commands

07 30 03 61 43 0B

03 6A 55 6E 69 13

A0 31 04 74 73 05

80 0B 08 61 63 49

30 30 13 20 6F 50

80 09 02 43 20 49

02 06 43 72 53 53

01 03 41 75 79 55

00 55 31 7A 73 31

07 0D 24 08 31 0D 63 03 95 4C 24 64 C5 5B

02 02 80 13 38 01 6F 4B 01 B6 36 1B B5 D4

A0 05 04 02 35 09 6D 00 6A A6 D6 0C 84 93

80 05 82 43 34 02 30 30 80 B0 D5 0F 18 00

30 00 02 41 33 16 5C 48 34 02 A6 96 8B 00

80 30 75 31 34 11 30 02 25 1C 92 BF 2D 00

02 80 30 13 5A 70 0D 41 10 B2 80 F9 A4 00

01 06 80 30 30 6B 06 00 C4 84 5D 2E B1 00

01 09 06 11 22 69 09 DD 5F C1 E5 05 CD 00

Command

Description

crypto ca enroll

Obtains the certificate of your router from the CA.

debug crypto pki transactions

Displays debugging messages for the trace of interaction (message type) between the CA and the router.

show crypto ca certificates

Displays information about your certificate, the certificate of the CA, and any RA certificates.


DB-465

Debug Commands debug crypto pki server

debug crypto pki server To enable debugging for a crypto public key infrastructure (PKI) certificate server, use the debug crypto pki server command in privileged EXEC mode. To disable debugging, use the no form of this command. debug crypto pki server no debug crypto pki server

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2(33)SRA


12.2SX


Examples

The following example shows how to enable debugging for a certificate server. This example also contains sample debug messages, which allow users to troubleshoot the various certificate-request-related stages and tasks that are handled by the certificate server. Router# debug crypto pki server Crypto PKI Certificate Server debugging is on Oct 15 19:50:41.003:CRYPTO_CS:old RA cert flag 0x4 Oct 15 19:50:41.003:CRYPTO_CS:new RA cert flag 0x1000C Oct 15 19:50:41.003:CRYPTO_CS:nvram filesystem Oct 15 19:50:41.279:CRYPTO_CS:serial number 0x1 written. Oct 15 19:50:53.383:CRYPTO_CS:created a new serial file. Oct 15 19:50:53.383:CRYPTO_CS:SCEP server started Oct 15 19:50:53.419:%SYS-5-CONFIG_I:Configured from console by console Oct 15 19:50:53.731:CRYPTO_CS:received a SCEP GetCACert request Oct 15 19:50:53.739:CRYPTO_CS:CA certificate sent Oct 15 19:50:54.355:CRYPTO_CS:received a SCEP GetCACert request Oct 15 19:50:54.363:CRYPTO_CS:CA certificate sent Oct 15 19:50:57.791:CRYPTO_CS:received a SCEP request Oct 15 19:50:57.795:CRYPTO_CS:read SCEP:registered and bound service SCEP_READ_DB_8 Oct 15 19:50:57.947:CRYPTO_CS:scep msg type - 19 Oct 15 19:50:57.947:CRYPTO_CS:trans id 3673CE2FF0235A4AE6F26242B00A4BB4 Oct 15 19:50:58.679:CRYPTO_CS:read SCEP:unregistered and unbound service SCEP_READ_DB_8 Oct 15 19:50:58.683:CRYPTO_CS:received an enrollment request Oct 15 19:50:58.691:CRYPTO_CS:request has been authorized, transaction id=3673CE2FF0235A4AE6F26242B00A4BB4 Oct 15 19:50:58.699:CRYPTO_CS:byte 2 in key usage in PKCS#10 is 0x7


DB-466

May 2008

Debug Commands debug crypto pki server

Oct 15 19:50:58.699:CRYPTO_CS:signature Oct 15 19:50:58.699:CRYPTO_CS:key_usage is 1 Oct 15 19:50:58.703:CRYPTO_CS:enrollment request with pendingID 1 sent to the CA Oct 15 19:50:58.707:CRYPTO_CS:write SCEP:registered and bound service SCEP_WRTE_DB_8 Oct 15 19:50:59.531:CRYPTO_CS:write SCEP:unregistered and unbound service SCEP_WRTE_DB_8 ..... Oct 15 19:53:08.403:CRYPTO_CS:CS_RA_REQUEST:save cert in dbase, pending id = 2 Oct 15 19:53:08.403:CRYPTO_CS:enrollment request 2 granted Oct 15 19:53:08.403:CRYPTO_PKI:All enrollment requests completed for trustpoint ra. Oct 15 19:53:08.403:%CRYPTO-6-CERTRET:Certificate received from Certificate Authority Oct 15 19:53:08.403:CRYPTO_PKI:All enrollment requests completed for trustpoint ra. Oct 15 19:53:08.403:CRYPTO_PKI:All enrollment requests completed for trustpoint ra. Oct 15 19:53:08.407:CRYPTO_PKI:All enrollment requests completed for trustpoint ra. Oct 15 19:53:19.623:IPSEC(key_engine):major = 1 Oct 15 19:53:19.623:IPSEC(key_engine):expired_timer:skip ... Oct 15 19:53:35.707:CRYPTO_CS:received a SCEP request Oct 15 19:53:35.711:CRYPTO_CS:read SCEP:registered and bound service SCEP_READ_DB_14 Oct 15 19:53:35.859:CRYPTO_CS:scep msg type - 20 Oct 15 19:53:35.859:CRYPTO_CS:trans id 4D774FFE2F7CA9991A7F6A785E803E77 Oct 15 19:53:36.591:CRYPTO_CS:read SCEP:unregistered and unbound service SCEP_READ_DB_14 Oct 15 19:53:36.595:CRYPTO_CS:received an enrollment request Oct 15 19:53:36.595:CRYPTO_CS:write SCEP:registered and bound service SCEP_WRTE_DB_14 Oct 15 19:53:37.623:CRYPTO_CS:write SCEP:unregistered and unbound service SCEP_WRTE_DB_14 Oct 15 19:53:37.631:CRYPTO_CS:Certificate sent to requestor

Related Commands

Command

Description

crypto pki server

Enables a Cisco IOS certificate server and enters certificate server configuration mode.


DB-467

Debug Commands debug crypto pki transactions

debug crypto pki transactions To display debugging messages for the trace of interaction (message type) between the certification authority (CA) and the router, use the debug crypto pki transactions command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto pki transactions no debug crypto pki transactions

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug crypto pki transactions command to display debugging messages pertaining to public key infrastructure (PKI) certificates. The messages will show status information during certificate enrollment and verification. You can also use the show crypto ca certificates command to display information about your certificate.

Examples

The following example, which authenticates and enrolls a CA, contains sample output for the debug crypto pki transactions command: Router(config)# crypto ca authenticate msca Certificate has the following attributes: Fingerprint:A5DE3C51 AD8B0207 B60BED6D 9356FB00 % Do you accept this certificate? [yes/no]:y Router# debug crypto pki transactions 00:44:00:CRYPTO_PKI:Sending CA Certificate Request: GET /certsrv/mscep/mscep.dll/pkiclient.exe?operation=GetCACert&message=msca HTTP/1.0 00:44:00:CRYPTO_PKI:http connection opened 00:44:01:CRYPTO_PKI:HTTP response header: HTTP/1.1 200 OK


DB-468

May 2008


Server:Microsoft-IIS/5.0 Date:Fri, 17 Nov 2000 18:50:59 GMT Content-Length:2693 Content-Type:application/x-x509-ca-ra-cert Content-Type indicates we have received CA and RA certificates. 00:44:01:CRYPTO_PKI:WARNING:A certificate chain could not be constructed while selecting certificate status 00:44:01:CRYPTO_PKI:WARNING:A certificate chain could not be constructed while selecting certificate status 00:44:01:CRYPTO_PKI:Name:CN = msca-rootRA, O = Cisco System, C = US 00:44:01:CRYPTO_PKI:Name:CN = msca-rootRA, O = Cisco System, C = US 00:44:01:CRYPTO_PKI:transaction GetCACert completed 00:44:01:CRYPTO_PKI:CA certificate received. 00:44:01:CRYPTO_PKI:CA certificate received. Router(config)# crypto ca enroll msca % % Start certificate enrollment .. % Create a challenge password. You will need to verbally provide this password to the CA Administrator in order to revoke your certificate. For security reasons your password will not be saved in the configuration. Please make a note of it. Password: Re-enter password: % The subject name in the certificate will be:Router.cisco.com % Include the router serial number in the subject name? [yes/no]:n % Include an IP address in the subject name? [yes/no]:n Request certificate from CA? [yes/no]:y % Certificate request sent to Certificate Authority % The certificate request fingerprint will be displayed. % The 'show crypto ca certificate' command will also show the fingerprint. Router(config)# 00:44:29:CRYPTO_PKI:transaction PKCSReq completed 00:44:29:CRYPTO_PKI:status: 00:44:29:CRYPTO_PKI:http connection opened 00:44:29:CRYPTO_PKI: received msg of 1924 bytes 00:44:29:CRYPTO_PKI:HTTP response header: HTTP/1.1 200 OK Server:Microsoft-IIS/5.0 Date:Fri, 17 Nov 2000 18:51:28 GMT Content-Length:1778 Content-Type:application/x-pki-message 00:44:29:CRYPTO_PKI:signed attr:pki-message-type: 00:44:29:13 01 33 00:44:29:CRYPTO_PKI:signed attr:pki-status: 00:44:29:13 01 30 00:44:29:CRYPTO_PKI:signed attr:pki-recipient-nonce: 00:44:29:04 10 B4 C8 2A 12 9C 8A 2A 4A E1 E5 15 DE 22 C2 B4 FD 00:44:29:CRYPTO_PKI:signed attr:pki-transaction-id: 00:44:29:13 20 34 45 45 41 44 42 36 33 38 43 33 42 42 45 44 45 39 46 00:44:29:34 38 44 33 45 36 39 33 45 33 43 37 45 39 00:44:29:CRYPTO_PKI:status = 100:certificate is granted 00:44:29:CRYPTO__PKI:All enrollment requests completed. 00:44:29:%CRYPTO-6-CERTRET:Certificate received from Certificate Authority


DB-469


Related Commands

Command

Description

crypto ca authenticate

Authenticates the CA (by getting the certificate of the CA).

crypto ca enroll

Obtains the certificate of your router from the CA.

debug crypto pki messages

Displays debugging messages for details of the interaction (message dump) between the CA and the router.

show crypto ca certificates

Displays information about your certificate, the certificate of the CA, and any RA certificates.


DB-470

May 2008

Debug Commands debug crypto provisioning

debug crypto provisioning To display information about an easy secure device provisioning (SDP) operation, use the debug crypto provisioning command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto provisioning no debug crypto provisioning

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.3(14)T

This command replaced the debug crypto wui command.

12.2SX


Usage Guidelines

For more detailed information about authentication, authorization, and accounting (AAA), use the debug aaa authorization command.

Examples

The following is sample output from the debug crypto provisioning command. The output includes explanations of the process. Router# debug crypto provisioning Petitioner device ! The user starts the Welcome phase. Nov 7 03:15:48.171: CRYPTO_WUI_TTI: received welcome get request. ! The router generates a Rivest, Shamir, and Adelman (RSA) keypair for future enrollment. Nov 7 03:15:48.279: CRYPTO_WUI_TTI: keyhash 'A506BE3B83C6F4B4A6EFCEB3D584AACA' ! The TTI transaction is completed. Nov 7 03:16:10.607: CRYPTO_WUI_TTI: received completion post request. Registrar device !. During the introduction phase, the browser prompts for login information. 06:39:18: CRYPTO_WUI_TTI: received introduction post request. 06:39:18: CRYPTO_WUI_TTI: checking AAA authentication (ipsecca_script_aaalist, ttiuser) ! This happens if the user types in the wrong username or password. 06:39:19: CRYPTO_WUI_TTI: authentication declined by AAA, or AAA server not found - 0x3 06:39:19: CRYPTO_WUI_TTI: aaa query fails!


DB-471

Debug Commands debug crypto provisioning

! The user re-enters login information. 06:39:19: CRYPTO_WUI_TTI: received introduction post request. 06:39:19: CRYPTO_WUI_TTI: checking AAA authentication (ipsecca_script_aaalist, ttiuser) 06:39:20: CRYPTO_WUI_TTI: checking AAA authorization (ipsecca_script_aaalist, ttiuser) ! The login attempt succeeds and authorization information is retrieved from the AAA database. 06:39:21: CRYPTO_WUI_TTI: aaa query ok! ! These attributes are inserted into the configuration template. 06:39:21: CRYPTO_WUI_TTI: building TTI av pairs from AAA attributes 06:39:21: CRYPTO_WUI_TTI: "subjectname" = "CN=user, O=company, C=country" 06:39:21: CRYPTO_WUI_TTI: "$1" = "ntp server 192.0.2.1" 06:39:21: CRYPTO_WUI_TTI: "$2" = "hostname user-vpn" ! The registrar stores this subject name and overrides the subject name in the subsequent enrollment request. 06:39:21: CRYPTO_WUI_TTI: subjectname=CN=user, O=company, C=country ! The registrar stores this key information so that it may be used to automatically grant the subsequent enrollment request. 06:39:21: CRYPTO_WUI_TTI: key_hash=A506BE3B83C6F4B4A6EFCEB3D584AACA

Related Commands

Command

Description

authentication list (tti-registrar)

Authenticates the introducer in an SDP operation.

authorization list (tti-registrar)

Specifies the appropriate authorized fields for the certificate subject name and list of template variables to be expanded into the Cisco IOS CLI snippet that is sent back to the petitioner in an SDP operation.


Displays information on AAA TACACS+ authorization.

template config

Specifies a remote URL for a Cisco IOS CLI configuration template.

template username

Establishes a template username and password to access the configuration template on the file system.


DB-472

May 2008

Debug Commands debug crypto sesmgmt

debug crypto sesmgmt To show connection setup messages and their flow through the router, use the debug crypto sesmgmt command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug crypto sesmgmt no debug crypto sesmgmt

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Encryption and authentication are provided by a software service on the router called a crypto engine. The crypto engine performs authentication through Digital Signature Standard (DSS) public and private keys when a connection is set up. DSS is a means of sending a “signature” at the end of a message that positively identifies the author of the message. The signature cannot be forged or duplicated by others, so whoever receives a message with a DSS signature knows exactly who sent the message. When connections are not completing, use the debug crypto sesmgmt command to follow the progress of connection messages as a first step in diagnosing the problem. You see a record of each connection message as the router discovers it, and can track its progress through the necessary signing, verifying, and encryption session setup operations. Other significant connection setup events, such as the pregeneration of Diffie-Hellman public numbers, are also shown. For information on Diffie-Hellman public numbers, refer to the Cisco IOS Security Configuration Guide. Also use the show crypto connections command to display additional information on connections.

Examples

The following is sample output from the debug crypto sesmgmt command. The first shows messages from a router that initiates a successful connection. The second shows messages from a router that receives a connection. Router# debug crypto sesmgmt CRYPTO: Dequeued a message: Inititate_Connection CRYPTO: DH gen phase 1 status for conn_id 2 slot 0:OK CRYPTO: Signing done. Status:OK CRYPTO: ICMP message sent: s=172.21.114.163, d=172.21.114.162 CRYPTO-SDU: send_nnc_req: NNC Echo Request sent CRYPTO: Dequeued a message: CRM CRYPTO: DH gen phase 2 status for conn_id 2 slot 0:OK CRYPTO: Verify done. Status=OK CRYPTO: Signing done. Status:OK CRYPTO: ICMP message sent: s=172.21.114.163, d=172.21.114.162 CRYPTO-SDU: recv_nnc_rpy: NNC Echo Confirm sent CRYPTO: Create encryption key for conn_id 2 slot 0:OK CRYPTO: Replacing -2 in crypto maps with 2 (slot 0) Router# debug crypto sesmgmt CRYPTO: Dequeued a message: CIM CRYPTO: Verify done. Status=OK


DB-473

Debug Commands debug crypto sesmgmt

CRYPTO: DH gen phase 1 status for conn_id 1 slot 0:OK CRYPTO: DH gen phase 2 status for conn_id 1 slot 0:OK CRYPTO: Signing done. Status:OK CRYPTO: ICMP message sent: s=172.21.114.162, d=172.21.114.163 CRYPTO-SDU: act_on_nnc_req: NNC Echo Reply sent CRYPTO: Create encryption key for conn_id 1 slot 0:OK CRYPTO: Replacing -2 in crypto maps with 1 (slot 0) CRYPTO: Dequeued a message: CCM CRYPTO: Verify done. Status=OK

Related Commands

Command

Description

debug crypto key-exchange

Displays DSS public key exchange messages.


DB-474

May 2008

Debug Commands debug csm neat (New Command)

debug csm neat (New Command) To turn on debugging for all Call Switching Module (CSM) Voice over IP (VoIP) calls, use the debug csm neat command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug csm neat [slot | dspm | dsp | dsp-channel] no debug csm neat [slot | dspm | dsp | dsp-channel]

Syntax Description

slot | dspm | dsp | dsp-channel

Command Modes

Privileged EXEC

Command History

12.4(9)T


12.2SX


Usage Guidelines

Note

(Optional) Identifies the location of a particular digital signal processor (DSP) channel.

The debug csm neat command turns on debugging for all CSM VoIP calls. If no arguments are specified, debugging is enabled for all voice calls.

The debug csm neat command does not display any information if you try to debug ISDN voice calls. To view debugging information about ISDN calls, use the debug cdapi command. The no debug cms neat command turns off debugging information for all voice calls. If the slot, dspm, dsp, or dsp-channel arguments are specified (if the specified DSP channel is engaged in a CSM call), CSM call-related debugging information is turned on for this channel. The no form of this command turns off debugging for that particular channel.

Examples

The following examples show sample output from the debug csm neat command. The following shows that CSM has received an event from ISDN. Router# debug csm neat March 18 04:05:07.052: EVENT_FROM_ISDN::dchan_idb=0x60D7B6B8, call_id=0xCF, ces=0x1 bchan=0x0, event=0x1, cause=0x0


DB-475



debug csm neat Field Descriptions

Field

Description

dchan_idb

Indicates the address of the hardware interface description block (IDB) for the D channel.

call_id

Indicates the call ID assigned by ISDN.

call-id

Indicates the call ID assigned by ISDN

bchan

Indicates the number of the B channel assigned for this call

cause

Indicates the ISDN event cause

The following example shows that CSM has allocated the CSM voice control block for the DSP device on slot 1 port 10 for this call. March 18 04:05:07.052: VDEV_ALLOCATE: slot 1 and port 10 is allocated.

In this example, CSM must first allocate the CSM voice control block to initiate the state machine. After the voice control block has been allocated, CSM obtains from the DSP Resource Manager the actual DSP channel that will be used for the call. At that point, CSM will switch to the actual logical port number. The slot number in this example refers to the physical slot on the Cisco AS5400 access server. The port number is the logical DSP number interpreted as listed in Table 66. Table 66

Logical DSP Numbers

Logical Port

Physical DSP Channel

0

DSPRM 1

DSP 1

DSP channel 1

1

DSPRM 1

DSP 1

DSP channel 2

2

DSPRM 1

DSP 2

DSP channel 1

3

DSPRM 1

DSP 2

DSP channel 2

4

DSPRM 1

DSP 3

DSP channel 1

5

DSPRM 1

DSP 3

DSP channel 2

6

DSPRM 1

DSP 4

DSP channel 1

7

DSPRM 1

DSP 4

DSP channel 2

8

DSPRM 1

DSP 5

DSP channel 1

9

DSPRM 1

DSP 5

DSP channel 2

10

DSPRM 1

DSP 6

DSP channel 1

11

DSPRM 1

DSP 6

DSP channel 2

12

DSPRM 2

DSP 1

DSP channel 1

13

DSPRM 2

DSP 1

DSP channel 2

14

DSPRM 2

DSP 2

DSP channel 1

15

DSPRM 2

DSP 2

DSP channel 2

16

DSPRM 2

DSP 3

DSP channel 1

17

DSPRM 2

DSP 3

DSP channel 2


DB-476

May 2008


Table 66

Logical DSP Numbers (continued)

Logical Port


18

DSPRM 2

DSP 4

DSP channel 1

19

DSPRM 2

DSP 4

DSP channel 2

20

DSPRM 2

DSP 5

DSP channel 1

21

DSPRM 2

DSP 5

DSP channel 2

22

DSPRM 2

DSP 6

DSP channel 1

23

DSPRM 2

DSP 6

DSP channel 2

48

DSPRM 5

DSP 1

DSP channel 1

49

DSPRM 5

DSP 1

DSP channel 2

50

DSPRM 5

DSP 2

DSP channel 1

51

DSPRM 5

DSP 2

DSP channel 2

52

DSPRM 5

DSP 3

DSP channel 1

53

DSPRM 5

DSP 3

DSP channel 2

54

DSPRM 5

DSP 4

DSP channel 1

55

DSPRM 5

DSP 4

DSP channel 2

56

DSPRM 5

DSP 5

DSP channel 1

57

DSPRM 5

DSP 5

DSP channel 2

58

DSPRM 5

DSP 6

DSP channel 1

59

DSPRM 5

DSP 6

DSP channel 2

The following example shows that the function csm_vtsp_init_tdm() has been called with a voice control block of address 0x60B8562C. This function will be called only when the call is treated as a voice call. March 18 04:05:07.052: csm_vtsp_init_tdm (voice_vdev=0x60B8562C)

The following example shows that CSM has obtained a DSP channel from the DSP Resource Manager: March 18 04:05:07.052: csm_vtsp_init_tdm: dsprm_tdm_allocate: tdm slot 1, dspm 2, dsp 5, dsp_channel 1csm_vtsp_init_tdm: dsprm_tdm_allocate: tdm stream 5, channel 9, bank 0, bp_channel 10

Table 67 describes the significant fields shown in the DSP channel initialized TDM display. Table 67

debug csm neat TDM Channel Field Descriptions

Field

Description

TDM slot 1, dspm 2, dsp 5, dsp_channel 1

Indicates the physical DSP channel that will be used for this call.

TDM stream 5, channel 9, bank 0, bp_channel 10

Indicates the on-chip and backplane TDM channel assigned to this DSP channel. Stream 5, channel 9 gives the on-chip TDM channel mapped to the DSP; bank 0, bp_channel 10 means that the backplane stream 0 and backplane channel #1 are assigned to this DSP.


DB-477


The following shows that CSM received an incoming call event from ISDN: March 18 04:05:07.052: EVENT_FROM_ISDN:(00CF): DEV_INCALL at slot 1 and port 20

Slot 1, port 20 means the logical DSP channel 20 (mapped to DSPRM 2, DSP 5, DSP channel 1). The following shows that the DEV_INCALL message been translated into a CSM_EVENT_ISDN_CALL message: March 18 04:05:07.052: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 1, port 20

This message is passed to the CSM central state machine while it is in the CSM_IDLE state and is in the CSM_PROC_IDLE procedure. The logical DSP channel port 20 on slot 1 is used to handle this call. The following shows that CSM has invoked the vtsp_ic_notify() function with a CSM voice call control block 0x60B8562C. March 18 04:05:07.052: vtsp_ic_notify : (voice_vdev= 0x60B8562C)

Inside this function, CSM will send a SETUP INDICATION message to the VTSP. This function will be invoked only if the call is a voice call. The following shows that CSM received a SETUP INDICATION RESPONSE message from the VTSP as an acknowledgment. March 18 04:05:07.056: csm_vtsp_call_setup_resp (vdev_info=0x60B8562C, vtsp_cdb=0x60FCA114)

This means that the VTSP received the CALL SETUP INDICATION message previously sent and has proceeded to process the call. •

vdev_info—Contains the address of the CSM voice data block.

•

vtsp_cdb—Contains the address of the VTSP call control block.

The following shows that CSM received a CALL CONNECT message from the VTSP: March 18 04:05:07.596: csm_vtsp_call_connect (vtsp_cdb=0x60FCA114, voice_vdev=0x60B8562C)

This indicates that the VTSP received a CONNECT message for the call leg initiated to the Internet side. •


•

voice_vdev—Contains the address of the CSM voice data block.

The following shows that while CSM is in the CSM_IC2_RING state, it receives a SETUP INDICATION RESPONSE from the VTSP. This message is translated into CSM_EVENT_MODEM_OFFHOOK and passed to the CSM central state machine. March 18 04:05:07.596: CSM_PROC_IC2_RING: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 20

The following shows that CSM received a CONNECT message from ISDN for the call using the logical DSP channel on slot 1 and port 20: March 18 04:05:07.616: EVENT_FROM_ISDN:(00CF): DEV_CONNECTED at slot 1 and port 20

The following shows that CSM translated the CONNECT event from ISDN into the CSM_EVENT_ISDN_CONNECTED message, which is then passed to the CSM central state machine: March 18 04:05:07.616: CSM_PROC_IC4_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 20

The following shows that CSM received a CALL SETUP REQUEST from the VTSP: May 16 12:22:27.580: csm_vtsp_call_setup_request (vtsp_cdb=0x60FCFA20, vtsp_sdb=0x60DFB608)


DB-478

May 2008


This represents a request to make an outgoing call to the PSTN. •


•

vtsp_sdb—Contains the address of the signalling data block for the signalling interface to be used to send the outgoing call.

The following shows that the physical DSP channel has been allocated for this outgoing call: May 16 12:22:27.580: csm_vtsp_call_setup_request: tdm slot 1, dspm 5, dsp 4, dsp_channel 1

The following shows the on-chip and backplane TDM channel assigned to this DSP channel: May 16 12:22:27.580: csm_vtsp_call_setup_request: tdm stream 5, channel 25, bank 0, bp_channel 27

In this sample output, tdm stream 5, channel 25, bank 0, bp_channel 27 indicates the on-chip and backplane TDM channel assigned to this DSP channel. Stream 5, channel 25 gives the on-chip TDM channel mapped to the DSP; bank 0, bp_channel 27 means that the backplane stream 0 and backplane channel 1 are assigned to this DSP. The following shows the calling number and the called number for this call. May 16 12:22:27.580: csm_vtsp_call_setup_request: calling number: 10001, called number: 30001

The following shows that the CALL SETUP REQUEST from the VTSP has been translated into the ' CSM_EVENT_MODEM_OFFHOOK message and is passed to the CSM central state machine: May 16 12:22:27.580: CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 54

The logical DSP channel number for the DSP (slot 1, port 54) is now displayed, which maps to the physical DSP channel slot 1, dspm 5, dsp 4, dsp_channel 1. The following shows that CSM collected all the digits for dialing out: May 16 12:22:27.580: CSM_PROC_OC3_COLLECT_ALL_DIGIT: CSM_EVENT_GET_ALL_DIGITS at slot 1, port 54

For PRI and for applications that do not require digit collection of outdialing digits (for example, voice calls), the intermediate digit collection states are omitted and the CSM state machine moves to this state directly, pretending that the digit collection has been done. The following shows an information message: March 16 12:22:27.580: CSM_PROC_OC3_COLLECT_ALL_DIGIT: called party num: (30001) at slot 1, port 54

The following shows that CSM attempts to find a free signalling D channel to direct the outgoing call: March 16 12:22:27.580: March 16 12:22:27.580: dchan_idb=0x60E8ACF0) March 16 12:22:27.580: March 16 12:22:27.580: dchan_idb=0x60D7ACB0)

csm_vtsp_check_dchan (voice_vdev=0x60B8562C) csm_vtsp_check_dchan (vtsp requested dchan=0x60D7ACB0, csm_vtsp_check_dchan (voice_vdev=0x60B8562C) csm_vtsp_check_dchan (vtsp requested dchan=0x60D7ACB0,

In the case of voice calls, the free signaling D channel must match the voice interface specified inside the signalling data block (vtsp_sdb) passed from the VTSP. The following shows that CSM has received an event from ISDN:


DB-479


March 16 12:22:27.624: EVENT_FROM_ISDN::dchan_idb=0x60D7ACB0, call_id=0xA121, ces=0x1 bchan=0x1E, event=0x3, cause=0x0

In this sample output: •

dchan_idb—Indicates the address of the hardware IDB for the D channel

•

call_id—Indicates the call id assigned by ISDN

•

bchan—Indicates the number of the B channel assigned for this call

•

cause—Indicates the ISDN event cause

The following shows that CSM has received a CALL PROCEEDING message from ISDN. March 16 12:22:27.624: EVENT_FROM_ISDN:(A121): DEV_CALL_PROC at slot 1 and port 54

The following shows that the CALL PROCEEDING event received from ISDN has been interpreted as a CSM_EVENT_ISDN_BCHAN_ASSIGNED message: *March 16 12:22:27.624: CSM_PROC_OC4_DIALING: CSM_EVENT_ISDN_BCHAN_ASSIGNED at slot 1, port 54

ISDN has assigned a B channel for this outgoing call. This B channel must be on the same PRI span as the signalling D channel allocated previously. The following shows that the csm_vtsp_setup_for_oc function is called: March 16 12:22:27.624: csm_vtsp_setup_for_oc (voice_vdev=0x60B8562C)

This is invoked when an outgoing call initiated by the VTSP receives a response from the ISDN stack. The following shows that ISDN has sent a CONNECT message to CSM indicating that the call leg to the PSTN side has been established: March 16 12:22:28.084: EVENT_FROM_ISDN::dchan_idb=0x60D7ACB0, call_id=0xA121, ces=0x1 bchan=0x1E, event=0x4, cause=0x0 March 16 12:22:28.084: EVENT_FROM_ISDN:(A121): DEV_CONNECTED at slot 1 and port 54

The following shows that while CSM is in the OC5_WAIT_FOR_CARRIER state, it has received the 'CONNECT' message from ISDN and has translated it into the CSM_EVENT_ISDN_CONNECTED message, which is passed to the CSM central state machine: March 16 12:22:28.084: CSM_PROC_OC5_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 54

The following shows that the function vtsp_confirm_oc() has been called: March 16 12:22:28.084: vtsp_confirm_oc : (voice_vdev= 0x60B8562C)

This is invoked after CSM received the CONNECT message from ISDN. CSM sends a confirmation of the CONNECT to the VTSP.


DB-480

May 2008

Debug Commands debug csm tgrm

debug csm tgrm To view Call Switching Module (CSM) trunk group resource manager information, use the debug csm tgrm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug csm tgrm no debug csm tgrm

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2(33)SRA


12.2SX


Usage Guidelines

Disable console logging and use buffered logging before using the debug csm tgrm command. Using the debug csm tgrm command generates a large volume of debugs, which can affect router performance.

Examples

The following is sample output from the debug csm tgrm command. The output shows that the call type is voice, the direction is incoming, and the call is accepted by the CSM. Router# debug csm tgrm

Router# 00:02:25:CSM-TGRM:csm_rx_cas_event_from_neat(EVENT_DIAL_IN) - c(T1 7/1:1:3) call_type=VOICE, dir=INCOMING Router# 00:02:30:CSM-TGRM:csm_proc_ic3_wait_for_res_resp() c(T1 7/1:1:3) VOICE


DB-481

Debug Commands debug csm tgrm


debug csm tgrm Field Descriptions

Field

Description

call_type

Type of call: VOICE or MODEM.

dir

Direction of the call: INCOMING or OUTGOING.


DB-482

May 2008

Debug Commands debug csm voice

debug csm voice To turn on debugging for all Call Switching Module (CSM) Voice over IP (VoIP) calls, use the debug csm voice command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug csm voice [slot | dspm | dsp | dsp-channel] no debug csm voice [slot | dspm | dsp | dsp-channel]

Syntax Description

slot | dspm | dsp | dsp-channel

Command Modes

Privileged EXEC

Usage Guidelines

The debug csm voice command turns on debugging for all CSM VoIP calls. If this command has no keyword specified, then debugging is enabled for all voice calls. Note

(Optional) Identifies the location of a particular digital signal processor (DSP) channel.

The debug csm voice command does not display any information if you try to debug isdn voice calls. To view debugging information about isdn calls, use the debug cdapi command.

The no debug cms voice command turns off debugging information for all voice calls. If the slot | dspm | dsp | dsp-channel argument is specified, then (if the specified DSP channel is engaged in a CSM call) CSM call-related debugging information will be turned on for this channel. The no form of this command turns off debugging for that particular channel.

Examples

The following examples show sample output from the debug csm voice command. The following shows that CSM has received an event from ISDN. Router# debug csm voice Oct 18 04:05:07.052: EVENT_FROM_ISDN::dchan_idb=0x60D7B6B8, call_id=0xCF, ces=0x1 bchan=0x0, event=0x1, cause=0x0

In this example, terms are explained as follows: •

dchan_idb—Indicates the address of the hardware interface description block (IDB) for the D channel

•

call_id—Indicates the call ID assigned by ISDN

•


•


The following shows that CSM has allocated the CSM voice control block for the DSP device on slot 1 port 10 for this call. Oct 18 04:05:07.052: VDEV_ALLOCATE: slot 1 and port 10 is allocated.


DB-483


This AS5300 access server might not be actually used to handle this call. CSM must first allocate the CSM voice control block to initiate the state machine. After the voice control block has been allocated, CSM obtains from the DSP Resource Manager the actual DSP channel that will be used for the call. At that point, CSM will switch to the actual logical port number. The slot number refers to the physical slot on the AS5300 access server. The port number is the logical DSP number interpreted as listed in Table 69. Table 69

Logical DSP Numbers

Logical Port Number


Port 0

DSPRM 1, DSP 1, DSP channel 1

Port 1


Port 2


Port 3


Port 4


Port 5


Port 6


Port 7


Port 8


Port 9


Port 10


Port 11


Port 12


Port 13


Port 14


Port 15


Port 16


Port 17


Port 18


Port 19


Port 20


Port 21


Port 22


Port 23


Port 48


Port 49


Port 50


Port 51


Port 52


Port 53


Port 54



DB-484

May 2008


Table 69

Logical DSP Numbers (continued)

Logical Port Number


Port 55


Port 56


Port 57


Port 58


Port 59


The following shows that the function csm_vtsp_init_tdm() has been called with a voice control block of address 0x60B8562C. This function will be called only when the call is treated as a voice call. Oct 18 04:05:07.052: csm_vtsp_init_tdm (voice_vdev=0x60B8562C)

The following shows that CSM has obtained a DSP channel from the DSP Resource Manager: Oct 18 04:05:07.052: csm_vtsp_init_tdm: dsprm_tdm_allocate: tdm slot 1, dspm 2, dsp 5, dsp_channel 1csm_vtsp_init_tdm: dsprm_tdm_allocate: tdm stream 5, channel 9, bank 0, bp_channel 10

The DSP channel has the following initialized TDM channel information: •

TDM slot 1, dspm 2, dsp 5, dsp_channel 1—Indicates the physical DSP channel that will be used for this call.

•

TDM stream 5, channel 9, bank 0, bp_channel 10—Indicates the on-chip and backplane TDM channel assigned to this DSP channel. Stream 5, channel 9 gives the on-chip TDM channel mapped to the DSP; bank 0, bp_channel 10 means that the backplane stream 0 and backplane channel #1 are assigned to this DSP.

The following shows that CSM has received an incoming call event from ISDN: Oct 18 04:05:07.052: EVENT_FROM_ISDN:(00CF): DEV_INCALL at slot 1 and port 20

Slot 1, port 20 means the logical DSP channel 20 (mapped to DSPRM 2, DSP 5, DSP channel 1). The following shows that the DEV_INCALL message has been translated into a CSM_EVENT_ISDN_CALL message: Oct 18 04:05:07.052: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 1, port 20

This message is passed to the CSM central state machine while it is in the CSM_IDLE state and is in the CSM_PROC_IDLE procedure. The logical DSP channel port 20 on slot 1 is used to handle this call. The following shows that CSM has invoked the vtsp_ic_notify() function with a CSM voice call control block 0x60B8562C. Oct 18 04:05:07.052: vtsp_ic_notify : (voice_vdev= 0x60B8562C)

Inside this function, CSM will send a SETUP INDICATION message to the VTSP. This function will be invoked only if the call is a voice call. The following shows that CSM has received a SETUP INDICATION RESPONSE message from the VTSP as an acknowledgment. Oct 18 04:05:07.056: csm_vtsp_call_setup_resp (vdev_info=0x60B8562C, vtsp_cdb=0x60FCA114)


DB-485


This means that the VTSP has received the CALL SETUP INDICATION message previously sent and has proceeded to process the call. •

vdev_info—Contains the address of the CSM voice data block.

•


The following shows that CSM has received a CALL CONNECT message from the VTSP: Oct 18 04:05:07.596: csm_vtsp_call_connect (vtsp_cdb=0x60FCA114, voice_vdev=0x60B8562C)

This indicates that the VTSP has received a CONNECT message for the call leg initiated to the Internet side. •


•

voice_vdev—Contains the address of the CSM voice data block.

The following shows that while CSM is in the CSM_IC2_RING state, it receives a SETUP INDICATION RESPONSE from the VTSP. This message is translated into CSM_EVENT_MODEM_OFFHOOK and passed to the CSM central state machine. Oct 18 04:05:07.596: CSM_PROC_IC2_RING: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 20

The following shows that CSM has received a CONNECT message from ISDN for the call using the logical DSP channel on slot 1 and port 20: Oct 18 04:05:07.616: EVENT_FROM_ISDN:(00CF): DEV_CONNECTED at slot 1 and port 20

The following shows that CSM has translated the CONNECT event from ISDN into the CSM_EVENT_ISDN_CONNECTED message, which is then passed to the CSM central state machine: Oct 18 04:05:07.616: CSM_PROC_IC4_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 20

The following shows that CSM has received a CALL SETUP REQUEST from the VTSP: May 16 12:22:27.580: csm_vtsp_call_setup_request (vtsp_cdb=0x60FCFA20, vtsp_sdb=0x60DFB608)

This represents a request to make an outgoing call to the PSTN. •


•

vtsp_sdb—Contains the address of the signalling data block for the signalling interface to be used to send the outgoing call.

The following shows that the physical DSP channel has been allocated for this outgoing call: May 16 12:22:27.580: csm_vtsp_call_setup_request: tdm slot 1, dspm 5, dsp 4, dsp_channel 1

The following shows the on-chip and backplane TDM channel assigned to this DSP channel: May 16 12:22:27.580: csm_vtsp_call_setup_request: tdm stream 5, channel 25, bank 0, bp_channel 27

In this sample output, tdm stream 5, channel 25, bank 0, bp_channel 27 indicates the on-chip and backplane TDM channel assigned to this DSP channel. Stream 5, channel 25 gives the on-chip TDM channel mapped to the DSP; bank 0, bp_channel 27 means that the backplane stream 0 and backplane channel 1 are assigned to this DSP. The following shows the calling number and the called number for this call. May 16 12:22:27.580: csm_vtsp_call_setup_request: calling number: 10001, called number: 30001


DB-486

May 2008


The following shows that the CALL SETUP REQUEST from the VTSP has been translated into the ' CSM_EVENT_MODEM_OFFHOOK message and is passed to the CSM central state machine: May 16 12:22:27.580: CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 54

The logical DSP channel number for the DSP (slot 1, port 54) is now displayed, which maps to the physical DSP channel slot 1, dspm 5, dsp 4, dsp_channel 1. The following shows that CSM has collected all the digits for dialing out: May 16 12:22:27.580: CSM_PROC_OC3_COLLECT_ALL_DIGIT: CSM_EVENT_GET_ALL_DIGITS at slot 1, port 54

For PRI and for applications that do not require digit collection of outdialing digits (for example, voice calls), the intermediate digit collection states are omitted and the CSM state machine moves to this state directly, pretending that the digit collection has been done. The following shows an information message: May 16 12:22:27.580: CSM_PROC_OC3_COLLECT_ALL_DIGIT: called party num: (30001) at slot 1, port 54

The following shows that CSM attempts to find a free signalling D channel to direct the outgoing call: May 16 12:22:27.580: csm_vtsp_check_dchan May 16 12:22:27.580: csm_vtsp_check_dchan dchan_idb=0x60E8ACF0) May 16 12:22:27.580: csm_vtsp_check_dchan May 16 12:22:27.580: csm_vtsp_check_dchan dchan_idb=0x60D7ACB0)

(voice_vdev=0x60B8562C) (vtsp requested dchan=0x60D7ACB0, (voice_vdev=0x60B8562C) (vtsp requested dchan=0x60D7ACB0,

In the case of voice calls, the free signaling D channel must match the voice interface specified inside the signalling data block (vtsp_sdb) passed from the VTSP. The following shows that CSM has received an event from ISDN: May 16 12:22:27.624: EVENT_FROM_ISDN::dchan_idb=0x60D7ACB0, call_id=0xA121, ces=0x1 bchan=0x1E, event=0x3, cause=0x0

In this sample output: •

dchan_idb—indicates the address of the hardware IDB for the D channel

•

call_id—Indicates the call id assigned by ISDN

•


•


The following shows that CSM has received a CALL PROCEEDING message from ISDN. May 16 12:22:27.624: EVENT_FROM_ISDN:(A121): DEV_CALL_PROC at slot 1 and port 54

The following shows that the CALL PROCEEDING event received from ISDN has been interpreted as a CSM_EVENT_ISDN_BCHAN_ASSIGNED message: *May 16 12:22:27.624: CSM_PROC_OC4_DIALING: CSM_EVENT_ISDN_BCHAN_ASSIGNED at slot 1, port 54

ISDN has assigned a B channel for this outgoing call. This B channel must be on the same PRI span as the signalling D channel allocated previously.


DB-487


The following shows that the csm_vtsp_setup_for_oc function is called: May 16 12:22:27.624: csm_vtsp_setup_for_oc (voice_vdev=0x60B8562C)

This is invoked when an outgoing call initiated by the VTSP receives a response from the ISDN stack. The following shows that ISDN has sent a CONNECT message to CSM indicating that the call leg to the PSTN side has been established: May 16 12:22:28.084: EVENT_FROM_ISDN::dchan_idb=0x60D7ACB0, call_id=0xA121, ces=0x1 bchan=0x1E, event=0x4, cause=0x0 May 16 12:22:28.084: EVENT_FROM_ISDN:(A121): DEV_CONNECTED at slot 1 and port 54

The following shows that while CSM is in the OC5_WAIT_FOR_CARRIER state, it has received the 'CONNECT' message from ISDN and has translated it into the CSM_EVENT_ISDN_CONNECTED message, which is passed to the CSM central state machine: May 16 12:22:28.084: CSM_PROC_OC5_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 54

The following shows that the function vtsp_confirm_oc() has been called: May 16 12:22:28.084: vtsp_confirm_oc : (voice_vdev= 0x60B8562C)

This is invoked after CSM received the CONNECT message from ISDN. CSM sends a confirmation of the CONNECT to the VTSP.


DB-488

May 2008

Debug Commands debug ctl-client

debug ctl-client To collect debug information about the CTL client, use the debug ctl-client command in privileged EXEC configuration mode. To disable collection of debug information, use the no form of this command. debug ctl-client no debug ctl-client

Syntax Description


Command Default

Collection of CTL client debug information is disabled.

Command Modes

Privileged EXEC

Command History

Cisco IOS Release

Modification

12.4(4)XC


12.4(9)T


12.2SX


Usage Guidelines

This command is used with Cisco Unified CME phone authentication.

Examples

The following example shows debug messages for the CTL client: Router# debug ctl-client 001954: 001955: 001956: 001957: 001958: 001959: 001960: 001961: 001962: 001963: 001964: 001965: 001966:

.Jul .Jul .Jul .Jul .Jul .Jul .Jul .Jul .Jul .Jul .Jul .Jul .Jul

21 21 21 21 21 21 21 21 21 21 21 21 21

18:23:02.136: 18:23:02.272: 18:23:02.276: 18:23:02.276: 18:23:02.280: 18:23:02.280: 18:23:02.284: 18:23:02.284: 18:23:02.288: 18:23:02.288: 18:23:02.292: 18:23:02.424: 18:23:02.640:

ctl_client_create_ctlfile: create_ctl_record: Function 0 Trustpoint cisco1 create_ctl_record: record added for function 0 create_ctl_record: Function 0 Trustpoint sast2 create_ctl_record: record added for function 0 create_ctl_record: Function 1 Trustpoint cisco1 create_ctl_record: record added for function 1 create_ctl_record: Function 3 Trustpoint cisco1 create_ctl_record: record added for function 3 create_ctl_record: Function 4 Trustpoint cisco1 create_ctl_record: record added for function 4 ctl_client_create_ctlfile: Signature length 128 CTL File Created Successfully


DB-489

Debug Commands debug ctunnel

debug ctunnel To display debugging messages for the IP over a Connectionless Network Service (CLNS) Tunnel feature, use the debug ctunnel command in privileged EXEC mode. To disable debugging messages, use the no form of this command. debug ctunnel no debug ctunnel

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)


12.2(33)SRA


12.2SX


Examples

As packets are sent over the virtual interface, the following type of output will appear on the console when the debug ctunnel command is used: Router# debug ctunnel 4d21h: CTunnel1: IPCLNP encapsulated 49.0001.1111.1111.1111.00->49.0001.2222.2222.2222.00 (linktype=7, len=89)


DB-490

May 2008

Debug Commands debug custom-queue

debug custom-queue To enable custom queueing output, use the debug custom-queue command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug custom-queue no debug custom-queue

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is an example of enabling custom queueing output: Router# debug custom-queue Custom output queueing debugging is on

The following is sample output from the debug custom-queue command: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38: 00:27:38:

Related Commands

CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ: CQ:

Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0

output output output output output output output output output output output output output output output output output output output output output

(Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk (Pk

size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q: size/Q:

232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1) 232/1)

Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q

# # # # # # # # # # # # # # # # # # # # #

was was was was was was was was was was was was was was was was was was was was was

Command

Description

debug priority

Enables priority queueing output.

1 1 1 1 2 1 1 1 1 1 1 2 1 1 1 1 1 2 1 1 1

now now now now now now now now now now now now now now now now now now now now now

1 1 1 2 1 1 1 1 1 1 2 1 1 1 1 1 2 1 1 1 1


DB-491

Debug Commands debug dampening

debug dampening To display debug trace information messages for interface dampening, use the debug dampening command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dampening [all | interface] no debug dampening [all | interface]

Syntax Description

all

(Optional) Enables trace debugging for all dampening features.

interface

(Optional) Enables trace debugging for IP event dampening.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(22)S


12.2(13)T


12.2(14)S


12.2(18)SXD


12.2(33)SRA


12.2(31)SB2


12.2SX


Examples

The following sample output is similar to the output that will be displayed when the debug dampening command is entered with the interface keyword. The sample output shows the following information: •

Ethernet interface 1/1 is configured with the IP Event Dampening feature. The half-life period is set to 30 seconds, the reuse threshold to 500, the suppress threshold to 1000, and the restart penalty to 90.

•

The shutdown command and then the no shutdown command was entered on Ethernet interface 1/1. The interface was suppressed and then reused by the IP Event Dampening feature.

Router# debug dampening interface 00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to DOWN 00:07:17:EvD(Ethernet1/1):charge penalty 1000, new accum. penalty 1000, flap count 1 00:07:17:EvD(Ethernet1/1):accum. penalty 1000, now suppressed with a reuse intervals of 30 00:07:17:IF-EvD(Ethernet1/1):update CLNS Routing state to DOWN, interface is suppressed 00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from DOWN to DOWN 00:07:17:IF-EvD(Ethernet1/1):update IP Routing state to DOWN, interface is suppressed 00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from DOWN to UP


DB-492

May 2008

Debug Commands debug dampening

00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to DOWN 00:07:17:EvD(Ethernet1/1):accum. penalty decayed to 1000 after 0 second(s) 00:07:17:EvD(Ethernet1/1):charge penalty 1000, new accum. penalty 2000, flap count 2 00:07:17:EvD(Ethernet1/1):accum. penalty 2000, now suppressed with a reuse intervals of 60 00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from DOWN to UP 00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to DOWN 00:07:17:EvD(Ethernet1/1):accum. penalty decayed to 2000 after 0 second(s) 00:07:17:EvD(Ethernet1/1):charge penalty 1000, new accum. penalty 3000, flap count 3 00:07:17:EvD(Ethernet1/1):accum. penalty 3000, now suppressed with a reuse intervals of 78 00:07:17:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from DOWN to UP 00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP 00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP 00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP 00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP 00:07:17:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP 00:07:20:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to UP 00:07:20:IF-EvD(Ethernet1/1):IP Routing reports state transition from UP to UP 00:07:47:IF-EvD:unsuppress interfaces 00:08:36:IF-EvD:unsuppress interfaces 00:08:36:EvD(Ethernet1/1):accum. penalty decayed to 483 after 79 second(s) 00:08:36:EvD(Ethernet1/1):accum. penalty 483, now unsuppressed 00:08:36:IF-EvD(Ethernet1/1):update IP Routing state to UP, interface is not suppressed 00:08:36:IF-EvD(Ethernet1/1):update CLNS Routing state to UP, interface is not suppressed 00:08:36:IF-EvD(Ethernet1/1):CLNS Routing reports state transition from UP to UP


debug dampening Field Descriptions

Field

Description

... Routing reports state transition Displays the status of the specified interface from the perspective from UP to DOWN of the specified protocol. Interface state changes are displayed. The interface is specified within parentheses. The protocol is specified at the beginning of the message. charge penalty 1000, new accum. Displays the penalty assigned to the flapping interface and amount penalty 1000, flap count 1 of penalty that is added to the accumulated penalty. The interface flap count is also displayed. accum. penalty 1000, now Displays the status of the interface, accumulated penalty, and suppressed with a reuse intervals configured reuse threshold. of 30 update CLNS Routing state to DOWN, interface is suppressed

Displays the status of the specified interface. Interface state changes and suppression status are displayed.

accum. penalty decayed to 1000 after 0 second(s)

Displays the decay rate of the accumulated penalty.

unsuppress interfaces

Indicates that dampened interfaces have been unsuppressed.


DB-493

Debug Commands debug data-store

debug data-store To display persistant storage device (PSD)-related debugging messages for the , use the debug data-store command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug data-store no debug data-store

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)YU


12.4(2)XB

This command was integrated into Cisco IOS Release 12.4(2)XB.

12.4(15)T


12.2SX


Usage Guidelines

Caution

Examples

This command displays PSD-related debugging messages for the GGSN.

Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network flows and fewer users. Debugging during these periods reduces the effect these commands have on other users on the system.

The following example configures a debugging session to check PSD-related parameters: Router# debug data-store


DB-494

May 2008

Debug Commands debug data-store detail

debug data-store detail To display extended details for persistent storage device (PSD)-related debugging information, use the debug data-store detail command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug data-store detail no debug data-store detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)YU


12.4(2)XB


12.4(15)T


12.2SX


Usage Guidelines

Caution

Examples

This command displays PSD-related debugging messages for the GGSN.

Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network flows and fewer users. Debugging during these periods reduces the effect these commands have on other users on the system.

The following example configures a detailed PSD-related debugging session: Router# debug data-store details


DB-495

Debug Commands debug data-store detail

Related Commands

Command

Description

auto-retrieve

Configures the GGSN to automatically initiate a retrieval of G-CDRs from PSDs defined in a PSD server group.

clear data-store statistics

Clears PSD-related statistics.

show data-store

Displays the status of the PSD client and PSD server-related information.

show data-store statistics

Displays statistics related to the PSD client.


DB-496

May 2008

Debug Commands debug dbconn all

debug dbconn all To turn on all debug flags for Database Connection, use the debug dbconn all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dbconn all no debug dbconn all

Syntax Description


Defaults

Debugging is not enabled for Database Connection.

Command Modes

Privileged EXEC

Usage Guidelines

The debug dbconn all command displays debug output for Advanced Program-to-Program Communication (APPC), Database Connection configuration, Distributed Relational Database Architecture (DRDA), error messages, event traces, and TCP. The Database Connection debug flags are appc, config, drda, event, and tcp.

Examples

See the sample output provided for the debug dbconn appc, debug dbconn config, debug dbconn drda, debug dbconn event, and debug dbconn tcp commands.

Related Commands

Command

Description

debug dbconn appc

Displays APPC-related trace or error messages.

debug dbconn config

Displays trace or error messages for Database Connection configuration and control blocks.

debug dbconn drda

Displays error messages and stream traces for DRDA.

debug dbconn event

Displays trace or error messages for CTRC events related to DB2 communications.

debug dbconn tcp

Displays error messages and traces for TCP.


DB-497

Debug Commands debug dbconn appc

debug dbconn appc To display Advanced Program-to-Program Communication (APPC)-related trace or error messages, use the debug dbconn appc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dbconn appc no debug dbconn appc

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

In a router with stable Database Connection, the alias_cp_name field in the trace message should not be blank. There should be no other APPC error message. You can use Advanced Peer-to-Peer Networking (APPN) debug commands with this debug command to track APPN-related errors.

Examples

The following is sample output from the debug dbconn appc command. In a normal situation, only the following message is displayed: DBCONN-APPC: alias_cp_name is "ASH"

The following error messages are displayed if there is a network configuration error or other APPN-related problem: DBCONN-APPC-612C2B28: APPC error: opcode 0x1, primary_rc 0x0003, secondary_rc 0x00000004 DBCONN-APPC-612C2B28: Verb block = DBCONN-APPC-612C2B28: 0001 0200 0003 0000 0000 0004 0020 100C DBCONN-APPC-612C2B28: 610A 828B 0000 0000 0000 0000 0000 0000 DBCONN-APPC-612C2B28: 0000 0000 8014 0003 0000 0000 0000 0000 DBCONN-APPC-612C2B28: D3E4 F6F2 E2E3 C1D9 C4C2 F240 4040 4040 DBCONN-APPC-612C2B28: 4040 4040 4040 4040 4040 4040 4040 4040 DBCONN-APPC-612C2B28: 4040 4040 4040 4040 4040 4040 4040 4040 DBCONN-APPC-612C2B28: 4040 4040 4040 4040 4040 4040 4040 4040 DBCONN-APPC-612C2B28: 4040 4040 4040 4040 0200 0000 0000 0000 DBCONN-APPC-612C2B28: 0000 0000 D4C5 D9D9 C9C5 4040 4040 D7C5 DBCONN-APPC-612C2B28: E3C5 D940 4040 4040 0000 0000 0000 0000 DBCONN-APPC-612C2B28: 00E2 E3C1 D9E6 4BE3 D6D9 C3C8 4040 4040 DBCONN-APPC-612C2B28: 4040 0000 0000 0000 0000 0000 DBCONN-APPC-612C2B28: ALLOCATE verb block = DBCONN-APPC-612C2B28: 0001 0200 0003 0000 0000 0004 0020 100C DBCONN-APPC-612C2B28: 610A 828B 0000 0000 0000 0000 0000 0000 DBCONN-APPC-612C2B28: 0000 0000 8014 0003 0000 0000 0000 0000 DBCONN-APPC-612C2B28: D3E4 F6F2 E2E3 C1D9 C4C2 F240 4040 4040 DBCONN-APPC-612C2B28: 4040 4040 4040 4040 4040 4040 4040 4040 DBCONN-APPC-612C2B28: 4040 4040 4040 4040 4040 4040 4040 4040 DBCONN-APPC-612C2B28: 4040 4040 4040 4040 4040 4040 4040 4040 DBCONN-APPC-612C2B28: 4040 4040 4040 4040 0200 0000 0000 0000


DB-498

May 2008

Debug Commands debug dbconn appc

You can use the debug appn command to obtain more information. The following message is displayed if a database connection is manually cleared and an outstanding APPC verb is pending: DBCONN-APPC-%612C2B28: Canceling pending APPC verb 0x1

Related Commands

Command

Description

debug dbconn all

Turns on all debug flags for Database Connection.

debug dbconn config


debug dbconn drda


debug dbconn event

Displays trace or error messages for Database Connection events.

debug dbconn tcp



DB-499

Debug Commands debug dbconn config

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

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Most of the messages for Database Connection and control blocks do not report any errors. If a connection is inactive and cannot be cleared, use this command with the debug dbconn appc, debug dbconn tcp, and debug appn commands to locate the problem. The alias_cp_name field must match the configured APPN cpname.

Examples

The following is sample output from the debug dbconn config command: Router# debug dbconn config DBCONN-CONFIG: DBCONN-CONFIG: rdbname=STELLA DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG: DBCONN-CONFIG:

alias_cp_name is "ASH " connection 612BDAAC matching server on 198.147.235.5:0 with APPN shutdown; clearing connection 1234abcd created server 612C2720 server 612C2720 (listen 60F72E94) is active server 612C2720 (listen 60F72E94) is active new connection 612BDAAC listen 60F72E94 accepts connection 612BDAAC server 60F74614 takes connection 612BDAAC listen 60F72E94 releases connection 612BDAAC server 60F74614 releases connection 612BDAAC deleting connection 612BDAAC listen 60F72E94 abandons connection 612BDAAC server 612C2720 abandons connection 612BDAAC deleting server 612C2720 daemon 60381738 takes zombie connection 612BDAAC daemon 60381738 releases zombie connection 612BDAAC


DB-500

May 2008

Debug Commands debug dbconn config

Related Commands

Command

Description

debug dbconn all


debug dbconn appc


debug dbconn drda


debug dbconn event

Displays trace or error messages for Database Connection events.

debug dbconn tcp



DB-501

Debug Commands debug dbconn drda

debug dbconn drda To display error messages and stream traces for Distributed Relational Database Architecture (DRDA), use the debug dbconn drda command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dbconn drda no debug dbconn drda

Syntax Description


Defaults

Debugging is not enabled for the dbconn subsystem.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(2)T


12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug dbconn drda command: Router# debug dbconn drda *Jun 30 16:09:32.363: DBCONN-DRDA-62008300: REQDSS, correlator 1 *Jun 30 16:09:32.363: DBCONN-DRDA-62008300: X'1041' *Jun 30 16:09:32.363: DBCONN-DRDA-62008300: length 28, code point X'115E' *Jun 30 16:09:32.363: DBCONN-DRDA-62008300: length 8, code point X'116D' *Jun 30 16:09:32.363: DBCONN-DRDA-62008300: length 15, code point X'115A' (skipping...)

Related Commands

DSS X'006CD0410001', length 108, in chain, OBJECT X'00661041', length 98, code point OBJECT X'0020115E' in COLLECTION X'1041', OBJECT X'000C116D' in COLLECTION X'1041', OBJECT X'0013115A' in COLLECTION X'1041',

Command

Description

debug dbconn all


debug dbconn appc


debug dbconn config



DB-502

May 2008

Debug Commands debug dbconn drda

Command

Description

debug dbconn event


debug dbconn tcp



DB-503

Debug Commands debug dbconn event

debug dbconn event To display trace or error messages for Cisco Transaction Connection (CTRC) events related to DATABASE2 (DB2) communications, use the debug dbconn event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dbconn event no debug dbconn event

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(2)T


12.2(33)SRA


12.2SX


Examples

The following examples display output from the debug dbconn event command in a variety of situations. A normal trace for the debug dbconn event displays as follows: Router# debug dbconn event DBCONN-EVENT: Dispatch to 60FD6C00, from 0, msg 60F754CC, msgid 6468 'dh', buffer 0. DBCONN-EVENT: [*] Post to 61134240(cn), from 60EC5470(tc), msg 611419E4, msgid 0x6372 'cr', buffer 612BF68C. DBCONN-EVENT: Flush events called for pto 61182742, pfrom 61239837. DBCONN-EVENT: Event discarded: to 61182742 (cn), from 61239837(ap), msg 61339273, msgid 0x6372 'cr' buffer 0. DBCONN-EVENT: == Send to 1234abcd, from 22938acd, msg 72618394, msgid 0x6372 'cr', buffer 0.

If the following messages are displayed, contact Cisco technical support personnel: DBCONN-TCPFSM-1234abcd: Cannot occur in state 2 on input 6363 ('cc') DBCONN-APPCFSM-1234abcd: Cannot occur in state 3 on input 6363 ('cc')


DB-504

May 2008

Debug Commands debug dbconn event

Related Commands

Command

Description

debug dbconn all


debug dbconn appc


debug dbconn config

Display trace or error messages for Database Connection configuration and control blocks.

debug dbconn drda


debug dbconn tcp


show debugging

Displays the state of each debugging option.


DB-505

Debug Commands debug dbconn tcp

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

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(2)T


12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug dbconn tcp command: Router# debug dbconn tcp DBCONN-TCP-63528473: tcpdriver_passive_open returned NULL DBCONN-TCP-63528473: (no memory) tcp_reset(63829482) returns 4 DBCONN-TCP: tcp_accept(74625348,&error) returns tcb 63829482, error 4 DBCONN-TCP: (no memory) tcp_reset(63829482) returns 4 DBCONN-TCP-63528473: (open) tcp_create returns 63829482, error = 4 DBCONN-TCP-63528473: tcb_connect(63829482,1.2.3.4,2010) returns 4 DBCONN-TCP-63528473: (open error) tcp_reset(63829482) returns 4 DBCONN-TCP-63528473: tcp_create returns 63829482, error = 4 DBCONN-TCP-63528473: tcb_bind(63829482,0.0.0.0,2001) returns 4 DBCONN-TCP-63528473: tcp_listen(63829482,,) returns 4 DBCONN-TCP-63528473: (errors) Calling tcp_close (63829482)

Related Commands

Command

Description

debug dbconn all


debug dbconn appc



DB-506

May 2008

Debug Commands debug dbconn tcp

Command

Description

debug dbconn config


debug dbconn drda


debug dbconn event


show debugging



DB-507

Debug Commands debug decnet adj

debug decnet adj To display debugging information on DECnet adjacencies, use the debug decnet adj command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug decnet adj no debug decnet adj

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug decnet adj command: Router# debug decnet adj DNET-ADJ: DNET-ADJ: DNET-ADJ: DNET-ADJ: DNET-ADJ: DNET-ADJ: DNET-ADJ: DNET-ADJ: DNET-ADJ: DNET-ADJ: DNET-ADJ:

Level 1 hello from 1.3 sending hellos Sending hellos to all routers on interface Ethernet0, blksize 1498 Level 1 hello from 1.3 1.5 adjacency initializing sending triggered hellos Sending hellos to all routers on interface Ethernet0, blksize 1498 Level 1 hello from 1.3 1.5 adjacency up Level 1 hello from 1.5 1.5 adjacency down, listener timeout

The following line indicates that the router is sending hello messages to all routers on this segment, which in this case is Ethernet 0: DNET-ADJ: Sending hellos to all routers on interface Ethernet0, blksize 1498

The following line indicates that the router has heard a hello message from address 1.5 and is creating an adjacency entry in its table. The initial state of this adjacency will be initializing. DNET-ADJ: 1.5 adjacency initializing

The following line indicates that the router is sending an unscheduled (triggered) hello message as a result of some event, such as new adjacency being heard: DNET-ADJ: sending triggered hellos

The following line indicates that the adjacency with 1.5 is now up, or active: DNET-ADJ: 1.5 adjacency up

The following line indicates that the adjacency with 1.5 has timed out, because no hello message has been heard from adjacency 1.5 in the time interval originally specified in the hello message from 1.5: DNET-ADJ: 1.5 adjacency down, listener timeout


DB-508

May 2008

Debug Commands debug decnet adj

The following line indicates that the router is sending an unscheduled hello message, as a result of some event, such as the adjacency state changing: DNET-ADJ: hello update triggered by state changed in dn_add_adjacency


DB-509

Debug Commands debug decnet connects

debug decnet connects To display debugging information of all connect packets that are filtered (permitted or denied) by DECnet access lists, use the debug decnet connects command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug decnet connects no debug decnet connects

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

When you use connect packet filtering, it may be helpful to use the decnet access-group configuration command to apply the following basic access list: access-list 300 permit 0.0 63.1023 eq any

You can then log all connect packets sent on interfaces to which you applied this list, in order to determine those elements on which your connect packets must be filtered.

Note

Examples

Packet password and account information is not logged in the debug decnet connects message, nor is it displayed by the show access EXEC command. If you specify password or account information in your access list, they can be viewed by anyone with access to the configuration of the router.

The following is sample output from the debug decnet connects command: Router# debug decnet connects DNET-CON: list 300 item #2 matched src=19.403 dst=19.309 on Ethernet0: permitted srcname=“RICK” srcuic=[0,017] dstobj=42 id=“USER”

Table 71 describes significant fields shown in the output. Table 71

debug decnet connects Field Descriptions

Field

Description

DNET-CON:

Indicates that this is a debug decnet connects packet.

list 300 item #2 matched

Indicates that a packet matched the second item in access list 300.

src=19.403

Indicates the source DECnet address for the packet.

dst=19.309

Indicates the destination DECnet address for the packet.

on Ethernet0:

Indicates the router interface on which the access list filtering the packet was applied.

permitted

Indicates that the access list permitted the packet.


DB-510

May 2008

Debug Commands debug decnet connects

Table 71

debug decnet connects Field Descriptions (continued)

Field

Description

srcname = “RICK”

Indicates the originator user of the packet.

srcuic=[0,017]

Indicates the source UIC of the packet.

dstobj=42

Indicates that DECnet object 42 is the destination.

id=“USER”

Indicates the access user.


DB-511

Debug Commands debug decnet events

debug decnet events To display debugging information on DECnet events, use the debug decnet events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug decnet events no debug decnet events

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug decnet events command: Router# debug decnet events DNET: Hello from area 50 rejected - exceeded ‘max area' parameter (45) DNET: Hello from area 50 rejected - exceeded ‘max area' parameter (45)

The following line indicates that the router received a hello message from a router whose area was greater than the max-area parameter with which this router was configured: DNET: Hello from area 50 rejected - exceeded'max area' parameter (45)

The following line indicates that the router received a hello message from a router whose node ID was greater than the max-node parameter with which this router was configured: DNET: Hello from node 1002 rejected - exceeded'max node' parameter (1000)


DB-512

May 2008

Debug Commands debug decnet packet

debug decnet packet To display debugging information on DECnet packet events, use the debug decnet packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug decnet packet no debug decnet packet

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug decnet packet command: Router# debug decnet packet DNET-PKT: src 1.4 dst 1.5 sending to PHASEV DNET-PKT: Packet fwded from 1.4 to 1.5, via 1.5, snpa 0000.3080.cf90, TokenRing0

The following line indicates that the router is sending a converted packet addressed to node 1.5 to Phase V: DNET-PKT: src 1.4 dst 1.5 sending to PHASEV

The following line indicates that the router forwarded a packet from node 1.4 to node 1.5. The packet is being sent to the next hop of 1.5 whose subnetwork point of attachment (MAC address) on that interface is 0000.3080.cf90. DNET-PKT: Packet fwded from 1.4 to 1.5, via 1.5, snpa 0000.3080.cf90, TokenRing0


DB-513

Debug Commands debug decnet routing

debug decnet routing To display all DECnet routing-related events occurring at the router, use the debug decnet routing command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug decnet routing no debug decnet routing

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug decnet routing command: Router# debug decnet routing DNET-RT: DNET-RT: DNET-RT: DNET-RT: DNET-RT: DNET-RT: DNET-RT: DNET-RT: DNET-RT: DNET-RT:

Received level 1 routing from 1.3 on Ethernet0 at 1:16:34 Sending routes Sending normal routing updates on Ethernet0 Sending level 1 routing updates on interface Ethernet0 Level1 routes from 1.5 on Ethernet0: entry for node 5 created route update triggered by after split route pointers in dn_rt_input Received level 1 routing from 1.5 on Ethernet 0 at 1:18:35 Sending L1 triggered routes Sending L1 triggered routing updates on Ethernet0 removing route to node 5

The following line indicates that the router has received a level 1 update on Ethernet interface 0: DNET-RT: Received level 1 routing from 1.3 on Ethernet0 at 1:16:34

The following line indicates that the router is sending its scheduled updates on Ethernet interface 0: DNET-RT: Sending normal routing updates on Ethernet0

The following line indicates that the route will send an unscheduled update on this interface as a result of some event. In this case, the unscheduled update is a result of a new entry created in the routing table of the interface. DNET-RT: route update triggered by after split route pointers in dn_rt_input

The following line indicates that the router sent the unscheduled update on Ethernet 0: DNET-RT: Sending L1 triggered routes DNET-RT: Sending L1 triggered routing updates on Ethernet0

The following line indicates that the router removed the entry for node 5 because the adjacency with node 5 timed out, or the route to node 5 through a next-hop router was disconnected: DNET-RT: removing route to node 5


DB-514

May 2008

Debug Commands debug dhcp redundancy

debug dhcp redundancy To display debugging information about DHCP proxy client redundancy events, use the debug dhcp redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command. debug dhcp redundancy no debug dhcp redundancy

Syntax Description


Command Default

Debugging output is disabled for DHCP redundancy events.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(31)SB2


12.2SX


Examples

The following example displays debug messages regarding DHCP redundancy events. The last line is output when the debug dhcp redundancy command is enabled. The line indicates that the active Route Processor has sent a dynamic lease synchronization message for IP address 10.1.1.1: Router# debug dhcp redundancy *Mar 15 10:32:21: DHCPD: assigned IP address 10.1.1.1 to client *Mar 15 10:32:21: DHCPD: dynamic sync sent for 10.1.1.1

Related Commands

Command

Description

debug ip dhcp server redundancy

Displays debugging information about DHCP server and relay agent redundancy events.


DB-515

Debug Commands debug dhcp

debug dhcp To display debugging information about the Dynamic Host Configuration Protocol (DHCP) client activities and to monitor the status of DHCP packets, use the debug dhcp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dhcp [detail] no debug dhcp [detail]

Syntax Description

detail

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0


12.3(8)T

The output of this command was enhanced to display default static routes.

Usage Guidelines

(Optional) Displays additional debugging information.

12.2(33)SRA


12.2SX


You can also use the debug dhcp command to monitor the subnet allocation and releasing for on-demand address pools. For debugging purposes, the debug dhcp detail command provides the most useful information such as the lease entry structure of the client and the state transitions of the lease entry. The debug output shows the scanned option values from received DHCP messages that are replies to a router request. The values of the op, htype, hlen, hops, server identifier option, xid, secs, flags, ciaddr, yiaddr, siaddr, and giaddr fields of the DHCP packet are shown in addition to the length of the options field.

Examples

The following examples show and explain some of the typical debugging messages you may see when using the debug dhcp detail command. The following sample output shows when a DHCP client sends a DHCPDISCOVER broadcast message to find its local DHCP server: Router# debug dhcp detail 00:07:16:DHCP:DHCP client process started:10 00:07:16:RAC:Starting DHCP discover on Ethernet2 00:07:16:DHCP:Try 1 to acquire address for Ethernet2 00:07:16:%SYS-5-CONFIG_I:Configured from console by console 00:07:19:DHCP:Shutting down from get_netinfo() 00:07:19:DHCP:Attempting to shutdown DHCP Client 00:07:21:DHCP:allocate request 00:07:21:DHCP:new entry. add to queue


DB-516

May 2008


00:07:21:DHCP:SDiscover attempt # 1 for entry:

The first seven lines of the following output show the current values stored in the lease entry structure for the client: 00:07:21:Temp IP addr:0.0.0.0 for peer on Interface:Ethernet2 00:07:21:Temp sub net mask:0.0.0.0 00:07:21: DHCP Lease server:0.0.0.0, state:1 Selecting 00:07:21: DHCP transaction id:582 00:07:21: Lease:0 secs, Renewal:0 secs, Rebind:0 secs 00:07:21: Next timer fires after:00:00:03 00:07:21: Retry count:1 Client-ID:cisco-0010.7b6e.afd8-Et2 00:07:21:DHCP:SDiscover:sending 308 byte length DHCP packet 00:07:21:DHCP:SDiscover 308 bytes 00:07:21: B'cast on Ethernet2 interface from 0.0.0.0

The following output shows the offered addresses and parameters sent to the DHCP client by the DHCP server via a DHCPOFFER message. The messages containing the Scan field indicate the options that were scanned from the received BOOTP packet and the corresponding values: 00:07:23:DHCP:Received a BOOTREP pkt 00:07:23:DHCP:Scan:Message type:DHCP Offer 00:07:23:DHCP:Scan:Server ID Option:10.1.1.1 = A010101 00:07:23:DHCP:Scan:Lease Time:180 00:07:23:DHCP:Scan:Renewal time:90 00:07:23:DHCP:Scan:Rebind time:157 00:07:23:DHCP:Scan:Subnet Address Option:255.255.255.0

The following output shows selected fields in the received BOOTP packet: 00:07:23:DHCP:rcvd pkt source:10.1.1.1, destination: 255.255.255.255 00:07:23: UDP sport:43, dport:44, length:308 00:07:23: DHCP op:2, htype:1, hlen:6, hops:0 00:07:23: DHCP server identifier:10.1.1.1 00:07:23: xid:582, secs:0, flags:8000 00:07:23: client:0.0.0.0, your:10.1.1.2 00:07:23: srvr: 0.0.0.0, gw:0.0.0.0 00:07:23: options block length:60 00:07:23:DHCP Offer Message Offered Address:10.1.1.2 00:07:23:DHCP:Lease Seconds:180 Renewal secs: 90 Rebind secs:157 00:07:23:DHCP:Server ID Option:10.1.1.1 00:07:23:DHCP:offer received from 10.1.1.1

The following output shows when the DHCP client sends a DHCPREQUEST broadcast message to the DHCP server to accept the offered parameters: 00:07:23:DHCP:SRequest attempt # 1 for entry: 00:07:23:Temp IP addr:10.1.1.2 for peer on Interface:Ethernet2 00:07:23:Temp sub net mask:255.255.255.0 00:07:23: DHCP Lease server:10.1.1.1, state:2 Requesting 00:07:23: DHCP transaction id:582 00:07:23: Lease:180 secs, Renewal:0 secs, Rebind:0 secs 00:07:23: Next timer fires after:00:00:02 00:07:23: Retry count:1 Client-ID:cisco-0010.7b6e.afd8-Et2 00:07:23:DHCP:SRequest- Server ID option:10.1.1.1 00:07:23:DHCP:SRequest- Requested IP addr option:10.1.1.2 00:07:23:DHCP:SRequest placed lease len option:180 00:07:23:DHCP:SRequest:326 bytes 00:07:23:DHCP:SRequest:326 bytes 00:07:23: B'cast on Ethernet2 interface from 0.0.0.0


DB-517


The following output shows when the DHCP server sends a DHCPACK message to the client with the full set of configuration parameters: 00:07:23:DHCP:Received a BOOTREP pkt 00:07:23:DHCP:Scan:Message type:DHCP Ack 00:07:23:DHCP:Scan:Server ID Option:10.1.1.1 = A010101 00:07:23:DHCP:Scan:Lease Time:180 00:07:23:DHCP:Scan:Renewal time:90 00:07:23:DHCP:Scan:Rebind time:157 00:07:23:DHCP:Scan:Subnet Address Option:255.255.255.0 00:07:23:DHCP:rcvd pkt source:10.1.1.1, destination: 255.255.255.255 00:07:23: UDP sport:43, dport:44, length:308 00:07:23: DHCP op:2, htype:1, hlen:6, hops:0 00:07:23: DHCP server identifier:10.1.1.1 00:07:23: xid:582, secs:0, flags:8000 00:07:23: client:0.0.0.0, your:10.1.1.2 00:07:23: srvr: 0.0.0.0, gw:0.0.0.0 00:07:23: options block length:60 00:07:23:DHCP Ack Message 00:07:23:DHCP:Lease Seconds:180 Renewal secs: 90 Rebind secs:157 00:07:23:DHCP:Server ID Option:10.1.1.1Interface Ethernet2 assigned DHCP address 10.1.1.2, mask 255.255.255.0 00:07:26:DHCP Client Pooling:***Allocated IP address:10.1.1.2 00:07:26:Allocated IP address = 10.1.1.2 255.255.255.0

The following output shows when a default gateway (option 3) is assigned a static IP address that is the default route and that static routes were added from the DHCP server: *Oct 2 06:22:24: gateway. *Oct 2 06:22:24: *Oct 2 06:22:24: *Oct 2 06:22:24: *Oct 2 06:22:24:

Setting default_gateway to 68.8.8.1 ! This is the option 3 default Adding default route 68.8.8.1 DHCP: Adding static route to 4.3.2.1 255.255.255.255 via 68.8.8.1 DHCP: Adding static route to 1.1.1.1 255.255.255.255 via 68.8.8.1 DHCP: Adding static route to 67.2.2.2 255.255.255.255 via 68.8.8.1

Most fields are self-explanatory; however, fields that may need further explanation are described in Table 72. Table 72

Related Commands

debug dhcp Field Descriptions

Fields

Description

DHCP:Scan:Subnet Address Option:255.255.255.0

Subnet mask option (option 1).

DHCP server identifier:1.1.1.1

Value of the DHCP server ID option (option 54). Note that this is not the same as the siaddr field, which is the server IP address.

srvr:0.0.0.0, gw:0.0.0.0

srvr is the value of the siaddr field. gw is the value of the giaddr field.

Command

Description

debug ip ddns update

Enables debugging for DDNS updates.

debug ip dhcp server

Enables DHCP server debugging.

host (host-list)

Specifies a list of hosts that will receive DDNS updates of A and PTR RRs.

ip ddns update hostname

Enables a host to be used for DDNS updates of A and PTR RRs.


DB-518

May 2008


Command

Description

ip ddns update method Specifies a method of DDNS updates of A and PTR RRs and the maximum interval between the updates. ip dhcp client update dns

Enables DDNS updates of A RRs using the same hostname passed in the hostname and FQDN options by a client.

ip dhcp-client update dns

Enables DDNS updates of A RRs using the same hostname passed in the hostname and FQDN options by a client.

ip dhcp update dns

Enables DDNS updates of A and PTR RRs for most address pools.

ip host-list

Specifies a list of hosts that will receive DDNS updates of A and PTR RRs.

show ip ddns update

Displays information about the DDNS updates.

show ip ddns update method

Displays information about the DDNS update method.

show ip dhcp server pool

Displays DHCP server pool statistics.

show ip host-list

Displays the assigned hosts in a list.

update dns

Dynamically updates a DNS with A and PTR RRs for some address pools.


DB-519

Debug Commands debug dialer events

debug dialer events To display debugging information about the packets received on a dialer interface, use the debug dialer events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dialer events no debug dialer events

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

When dial-on-demand routing (DDR) is enabled on the interface, information concerning the cause of any call (called the Dialing cause) is displayed.

Examples

In the following example, the line of output for an IP packet lists the name of the DDR interface and the source and destination addresses of the packet: Router# debug dialer events Dialing cause: Serial0: ip (s=172.16.1.111 d=172.16.2.22)

The following line of output for a bridged packet lists the DDR interface and the type of packet (in hexadecimal). For information on these packet types, see the “Ethernet Type Codes” appendix of the Cisco IOS Bridging and IBM Networking Command Reference publication. Dialing cause: Serial1: Bridge (0x6005)

Most messages are self-explanatory; however, messages that may need some explanation are described in Table 73. Table 73

debug dialer events Message Descriptions

Message

Description

Dialer0: Already xxx call(s) in progress Number of calls in progress (xxx) exceeds the maximum on Dialer0, dialing not allowed number of calls set on the interface. Dialer0: No free dialer - starting fast idle timer

All the lines in the interface or rotary group are busy, and a packet is waiting to be sent to the destination.

BRI0: rotary group to xxx overloaded (yyy)

Number dialer (xxx) exceeds the load set on the interface (yyy).

BRI0: authenticated host xxx with no matching dialer profile

No dialer profile matches xxx, the Challenge Handshake Authentication Protocol (CHAP) name or remote name of the remote host.


DB-520

May 2008

Debug Commands debug dialer events

Table 73

debug dialer events Message Descriptions (continued)

Message

Description

BRI0: authenticated host xxx with no matching dialer map

No dialer map matches xxx, the CHAP name or remote name of the remote host.

BRI0: Can’t place call, verify configuration

Dialer string or dialer pool on an interface not set.

Table 74 describes the messages that the debug dialer events command can generate for a serial interface used as a V.25bis dialer for DDR. Table 74

debug dialer events Command Message Descriptions for DDR

Message

Description

Serial 0: Dialer result = xxxxxxxxxx Result returned from the V.25bis dialer. It is useful in debugging if calls are failing. On some hardware platforms, this message cannot be displayed due to hardware limitations. Possible values for the xxxxxxxxxx variable depend on the V.25bis device with which the router is communicating. Serial 0: No dialer string defined. Dialing cannot occur.

Packet is received that should cause a call to be placed. However, no dialer string is configured, so dialing cannot occur. This message usually indicates a configuration problem.

Serial 0: Attempting to dial xxxxxxxxxx

Packet has been received that passes the dial-on-demand access lists. That packet causes phone number xxxxxxxxxx to be dialed.

Serial 0: Unable to dial xxxxxxxxxx Phone call to xxxxxxxxxx cannot be placed. This failure might be due to a lack of memory, full output queues, or other problems. Serial 0: disconnecting call

Router hangs up a call.

Serial 0: idle timeout

One of these three messages is displayed when a dialer timer expires. These messages are mostly informational, but are useful for debugging a disconnected call or call failure.

Serial 0: re-enable timeout Serial 0: wait for carrier timeout

Related Commands

Command

Description

debug decnet packet

Displays debugging information about the packets received on a dialer interface.


DB-521

Debug Commands debug dialer forwarding

debug dialer forwarding To display debugging information about the control plane at the home gateway (HGW) for Layer 2 Tunneling Protocol (L2TP) dialout, use the debug dialer forwarding command in privileged EXEC mode. The no form of this command disables debugging output. debug dialer forwarding no debug dialer forwarding

Syntax Description


Defaults

This command is disabled by default.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2 T


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug dialer forwarding command to configure a virtual private dialout network (VPDN) on the HGW and a network access server (NAS) to dial from the HGW to the client. An L2TP tunnel is created between the HGW and the NAS and the packets are forwarded transparently at the NAS.

Examples

The following is sample output from the debug dialer forwarding command for dialing from the HGW to the client.

Note

DDR-FWD is debug dialer forwarding information. (DDR= dial-on-demand routing.) Router# debug dialer forwarding Dialer forwarding events debugging is on Router# ping Protocol [ip]: Target IP address:1.1.1.3 Repeat count [5]:1 Datagram size [100]:


DB-522

May 2008

Debug Commands debug dialer forwarding

Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to 1.1.1.3, timeout is 2 seconds: 1d00h:Vi3 DDR-FWD 83093A60:event [REQUEST] state before [IDLE] 1d00h:Vi3 DDR-FWD 83093A60:VPN Authorization started 1d00h:Vi3 DDR-FWD 83093A60:VPN author result 1 1d00h:Vi3 DDR-FWD 83093A60:event [AUTHOR FOUND] state before [AUTHORIZING] 1d00h:Vi3 DDR-FWD 83093A60:event [FORWARDED] state before [FORWARDING] 1d00h:Vi3 DDR-FWD 83093A60:Connection is up, start LCP now *Mar 2 00:31:33:%LINK-3-UPDOWN:Interface Virtual-Access3, changed state to up. Success rate is 0 percent (0/1) R2604# *Mar 2 00:31:35:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access3, changed state to up Router#

Outgoing call disconnected: Router# 1d00h:Vi3 DDR-FWD 83093A60:event [VPDN DISC] state before [FORWARDED] *Mar 2 00:33:33:%LINK-3-UPDOWN:Interface Virtual-Access3, changed state to down *Mar 2 00:33:34:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access3, changed state to down

Related Commands

Command

Description

debug dialer events

Displays debugging information about events on a dialer interface.


Displays debugging information about packets received on a dialer interface.


DB-523

Debug Commands debug dialer map

debug dialer map To display debugging information about the creation and deletion of dynamic dialer maps, use the debug dialer map command in privileged EXEC mode. The no form of this command disables debugging output. debug dialer map no debug dialer map

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5.1)


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug dialer map command to track large-scale dialout (LSDO) and incoming calls that use dynamic dialer maps. This command shows the whole trace including when the map is created and removed. If an interface is configured for dial-on-demand routing (DDR), and a map to a specified address does not exist, then a dynamic dialer map is created and when the call disconnects, the dialer map is removed.

Note

Examples

Do not configure a dialer string or a dialer map on the incoming interface.

In the following sample output from the debug dialer map command, a dialer map is created when an incoming call is connected and removed when that call is disconnected: Router# debug dialer map Dial on demand dynamic dialer maps debugging is on

Incoming call connected: Router# *Mar 22 12:19:15.597:%LINK-3-UPDOWN:Interface BRI0/0:1, changed state to up *Mar 22 12:19:17.748:BR0/0:1 DDR:dialer_create_dynamic_map map created for 11.0.0.1


DB-524

May 2008

Debug Commands debug dialer map

*Mar 22 12:19:18.734:%LINEPROTO-5-UPDOWN:Line protocol on Interface BRI0/0:1, changed state to up *Mar 22 12:19:21.598:%ISDN-6-CONNECT:Interface BRI0/0:1 is now connected to unknown R2604

Incoming call disconnected: Router# *Mar 22 12:21:15.597:%ISDN-6-DISCONNECT:Interface BRI0/0:1 disconnected from R2604, call lasted 120 seconds *Mar 22 12:21:15.645:%LINK-3-UPDOWN:Interface BRI0/0:1, changed state to down *Mar 22 12:21:15.649:BR0/0:1 DDR:dialer_remove_dynamic_map map 11.0.0.1 removed *Mar 22 12:21:16.647:%LINEPROTO-5-UPDOWN:Line protocol on Interface BRI0/0:1, changed state to down

Related Commands

Command

Description

debug dialer events

Displays debugging information about events on a dialer interface.


Displays debugging information about packets received on a dialer interface.


DB-525

Debug Commands debug dialpeer

debug dialpeer Note

Effective with release 12.3(8)T, the debug dialpeer command is replaced by the debug voip dialpeer command. See the debug voip dialpeer command for more information. To view dial peer information, use the debug dialpeer command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dialpeer no debug dialpeer

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.3(8)T

This command was replaced by the debug voip dialpeer command.

12.2SX


Usage Guidelines

Disable console logging and use buffered logging before using the debug dialpeer command. Using the debug dialpeer command generates a large volume of debugging messages, which can affect router performance.

Examples

The following is sample output for the debug dialpeer command. The output shows the destination pattern configured on the matched dial-peer. Expanded string is the string after applying number translation to the original number. It shows that dial-peer 1311 was an incoming dial-peer match. It also shows that routing label was att1. It shows that dial-peer 5108888 and 111399 are an outgoing dial-peer match. Router# debug dialpeer Router# 00:22:28: Inside dpMatchCore: 00:22:28: destination pattn:5108880101 expanded string:5108880101 00:22:28:MatchNextPeer:Peer 1311 matched 00:22:28: Inside dpMatchCore: 00:22:28: destination pattn:5108880101 expanded string:5108880101


DB-526

May 2008

Debug Commands debug dialpeer

00:22:28: Inside dpMatchCore: 00:22:28: destination pattn:4088880101 expanded string:4088880101 00:22:28: Inside dpMatchCore: 00:22:28: destination pattn:4088880101 expanded string:4088880101 00:22:28: dpAssociateIncomingPeer_T:Matching route label att1 00:22:28: Inside dpMatchCore: 00:22:28: destination pattn:5108880101 expanded string:5108880101 00:22:28: dpAssociateIncomingPeer_T:Matching peer with src route label att1 failed 00:22:28: Inside dpMatchCore: 00:22:28: destination pattn:5108880101 expanded string:5108880101 00:22:28:MatchNextPeer:Peer 1311 matched 00:22:28: Inside dpMatchPeersMoreArg 00:22:28:dpMatchPeersMoreArg:Match Dest. pattern; called (5108880101) 00:22:28: Inside dpMatchCore: 00:22:28: destination pa Router#ttn:5108880101 expanded string:5108880101 00:22:28:MatchNextPeer:Peer 5108888 matched 00:22:28:MatchNextPeer:Peer 111399 matched 00:22:28:dpMatchPeersMoreArg:Result=0 after MATCH_ORIGINATE


debug dialpeer Field Descriptions

Field

Description

destination pattn

Destination pattern configured on the dial peer.

expanded string

The string after applying number translation to the original number.

Match Dest. pattern; called

Indicates that dial-peer match is going to match destination pattern against the called number.

Matching route label

The trunk group label or carrier id that is used for matching a dial peer.

MatchNextPeer

Indicates the dial peer tag that matched.

Result

Indicates the result of dial peer matching algorithm: 0 = Successful 1 = More digits needed for a possible match -1 = No match (match failed) -2 = The digits matched, but the destination address could not be obtained

Related Commands

Command

Description

call-block (dial peer)

Enables blocking of incoming calls on the dial peer.

carrier-id (dial-peer)

Identifies the carrier handling the incoming call.

session target (ENUM)

Specifies the ENUM search table for the target session.

show dial-peer voice

Displays the configuration of the dial peer.

translation-profile (dial-peer)

Assigns a translation profile to the dial peer.

trunkgroup (dial-peer)

Assigns a trunk group to the dial peer.

trunk-group-label (dial-peer)

Identifies the trunk group handling the incoming call.


DB-527

Debug Commands debug diameter

debug diameter To display information about the Diameter Protocol, use the debug diameter command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug diameter [dcca | connection | error | packet | event | fsm | failover] no debug diameter [dcca | connection | error | packet | event | fsm | failover]

Syntax Description

dcca

(Optional) Enables debugging for Diameter-Credit Control Accounting.

connection

(Optional) Enables debugging output for the connection between two Diameter nodes.

error

(Optional) Enables debugging output for Diameter errors.

packet

(Optional) Enables debugging output for Diameter data packets.

event

(Optional) Enables debugging output for Diameter events.

fsm

(Optional) Enables debugging output for the finite state machine.

failover

(Optional) Enables debugging output for Diameter redundancy.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T


12.2SX


Usage Guidelines

Use this command to display information about any of the listed classes of information about the Diameter Protocol.

Examples

The following examples show output from the debug diameter command: Peer configuration and peer connection after a peer is configured Router# debug diameter all *May 9 17:58:14.832: Dia Base: Diameter Peer configured. Allocate connection context. *May 9 17:58:14.832: Dia Base: Allocate the peer connection context 50F63888, handle C000000C *May 9 17:58:14.832: Dia Base: (C000000C): Received peer configuration event *May 9 17:58:14.832: Dia Peer FSM (50F63888): input event START in state CLOSED *May 9 17:58:14.832: Dia Peer FSM (50F63888): Starting Connection timer *May 9 17:58:14.832: Dia Peer FSM (50F63888): event START, state CLOSED-->WAIT_CONN_ACK *May 9 17:58:14.836: Dia Transport: socket 0 - connecting to 9.113.33.6 (3868) *May 9 17:58:14.836: Dia Transport: socket 0 - connection in progress *May 9 17:58:14.836: Dia Transport: socket 0 - local address 9.113.33.5


DB-528

May 2008


(49214) *May 9 17:58:14.836: Dia Transport: socket 0 - resume socket write - nothing to write *May 9 17:58:14.836: Dia Base: (C000000C): Received peer connection event from transport *May 9 17:58:14.836: Dia Peer FSM (50F63888): input event RCV_CONN_ACK in state WAIT_CONN_ACK *May 9 17:58:14.836: Dia Base: Sending diameter message to peer "Unknown" *May 9 17:58:14.836: DIAMETER: CER message, ver=1, len=120, app=0, [2328318322/2328318322] *May 9 17:58:14.836: DIAMETER: Origin-host-name [264] "host" (M) *May 9 17:58:14.836: DIAMETER: Origin-Realm [296] "cisco" (M) *May 9 17:58:14.836: DIAMETER: Host-IP-address [257] 9.113.33.5 (M) *May 9 17:58:14.836: DIAMETER: Vendor-ID [266] 9 (M) *May 9 17:58:14.836: DIAMETER: Product-name [269] "C7200-G8IS-M" *May 9 17:58:14.836: DIAMETER: Auth-Application-ID [258] 4 (M) *May 9 17:58:14.836: DIAMETER: Firmware-Revision [267] 1 50D0B710: 01000078 80000101 00000000 ...x........ 50D0B720: 8AC75172 8AC75172 00000108 4000000C .GQr.GQr....@... 50D0B730: 686F7374 00000128 4000000D 63697363 host...(@...cisc 50D0B740: 6F000000 00000101 4000000E 00010971 [email protected] 50D0B750: 21050000 0000010A 4000000C 00000009 !.......@....... 50D0B760: 0000010D 00000014 43373230 302D4738 ........C7200-G8 50D0B770: 49532D4D 00000102 4000000C 00000004 IS-M....@....... 50D0B780: 0000010B 0000000C 00000001 00 ............. *May 9 17:58:14.836: Dia Base: Request message hash ctx created for [2328318322/2328318322] *May 9 17:58:14.836: Dia Peer FSM (50F63888): Starting CER timer *May 9 17:58:14.836: Dia Peer FSM (50F63888): event RCV_CONN_ACK, state WAIT_CONN_ACK-->WAIT_CEA *May 9 17:58:14.836: Dia Transport: Dia Transport write message event *May 9 17:58:14.836: Dia Transport: socket 0 - complete msg sent *May 9 17:58:14.840: Dia Transport: socket 0 - complete read of 20 bytes *May 9 17:58:14.840: Dia Transport: complete header read from socket 0 *May 9 17:58:14.840: Dia Transport: read msg (172) bytes from socket 0 *May 9 17:58:14.840: Dia Transport: socket 0 complete read of 172 bytes *May 9 17:58:14.840: Dia Base: Diameter message received from the peer "Unknown" *May 9 17:58:14.840: DIAMETER: CEA message, ver=1, len=192, app=0, [2328318322/2328318322] *May 9 17:58:14.840: DIAMETER: Result-code [268] 2001 (M) *May 9 17:58:14.840: DIAMETER: Origin-host-name [264] "diameter2.cisco.com" (M) *May 9 17:58:14.840: DIAMETER: Origin-Realm [296] "cisco.com" (M) *May 9 17:58:14.840: DIAMETER: Host-IP-address [257] 10.77.154.80 (M) *May 9 17:58:14.840: DIAMETER: Vendor-ID [266] 9 (M) *May 9 17:58:14.840: DIAMETER: Product-name [269] "Diameter-Server" *May 9 17:58:14.840: DIAMETER: Supported-Vendor-ID [265] 10415 (M) *May 9 17:58:14.840: DIAMETER: Supported-Vendor-ID [265] 12645 (M) *May 9 17:58:14.840: DIAMETER: Supported-Vendor-ID [265] 9 (M) *May 9 17:58:14.840: DIAMETER: Supported-Vendor-ID [265] 9 (M)


DB-529


*May 9 17:58:14.840: DIAMETER: Auth-Application-ID [258] 4 (M) 65940780: 010000C0 00000101 00000000 ...@........ 65940790: 8AC75172 8AC75172 0000010C 4000000C .GQr.GQr....@... 659407A0: 000007D1 00000108 4000001B 6469616D [email protected] 659407B0: 65746572 322E6369 73636F2E 636F6D00 eter2.cisco.com. 659407C0: 00000128 40000011 63697363 6F2E636F ...(@...cisco.co 659407D0: 6D000000 00000101 4000000E 00010A4D [email protected] 659407E0: 9A500000 0000010A 4000000C 00000009 .P......@....... 659407F0: 0000010D 00000017 4469616D 65746572 ........Diameter 65940800: 2D536572 76657200 00000109 4000000C -Server.....@... 65940810: 000028AF 00000109 4000000C 00003165 ..(/[email protected] 65940820: 00000109 4000000C 00000009 00000109 ....@........... 65940830: 4000000C 00000009 00000102 4000000C @...........@... 65940840: 00000004 00 ..... *May 9 17:58:14.840: Dia Base: Request message hash ctx removed for [2328318322/2328318322] *May 9 17:58:14.840: Dia Base: (C000000C): Received msg event from message i/o *May 9 17:58:14.840: Dia Peer FSM (50F63888): input event RCV_CEA in state WAIT_CEA *May 9 17:58:14.840: Dia Peer FSM (50F63888): Starting Watchdog timer *May 9 17:58:14.840: %DIABASE-4-DIA_PEER_UP: Diameter peer 9.113.33.6 port 3868 TCP UP *May 9 17:58:14.840: Dia Peer FSM (50F63888): event RCV_CEA, state WAIT_CEA-->OPEN

Periodic watch-dog message exchanges *May 9 17:59:14.840: Dia Peer FSM (50F63888): input event TIMEOUT in state OPEN *May 9 17:59:14.840: Dia Base: Sending diameter message to peer "diameter2.cisco.com" *May 9 17:59:14.840: DIAMETER: DWR message, ver=1, len=48, app=0, [2328318323/2328318323] *May 9 17:59:14.840: DIAMETER: Origin-host-name [264] "host" (M) *May 9 17:59:14.840: DIAMETER: Origin-Realm [296] "cisco" (M) 50D0B710: 01000030 80000118 00000000 ...0........ 50D0B720: 8AC75173 8AC75173 00000108 4000000C .GQs.GQs....@... 50D0B730: 686F7374 00000128 4000000D 63697363 host...(@...cisc 50D0B740: 6F000000 FD o...} *May 9 17:59:14.840: Dia Base: Request message hash ctx created for [2328318323/2328318323] *May 9 17:59:14.840: Dia Peer FSM (50F63888): Starting Watchdog timer, [60] left for next timeout*May 9 17:59:14.840: Dia Peer FSM (50F63888): event TIMEOUT, state OPEN-->OPEN *May 9 17:59:14.840: Dia Transport: Dia Transport write message event *May 9 17:59:14.840: Dia Transport: socket 0 - complete msg sent *May 9 17:59:14.840: Dia Transport: socket 0 - complete read of 20 bytes *May 9 17:59:14.840: Dia Transport: complete header read from socket 0 *May 9 17:59:14.840: Dia Transport: read msg (60) bytes from socket 0 *May 9 17:59:14.840: Dia Transport: socket 0 - complete read of 60 bytes *May 9 17:59:14.840: Dia Base: Diameter message received from the peer "diameter2.cisco.com" *May 9 17:59:14.840: DIAMETER: DWA message, ver=1, len=80, app=0, [2328318323/2328318323] *May 9 17:59:14.840: DIAMETER: Result-code [268] 2001 (M) *May 9 17:59:14.840: DIAMETER: Origin-host-name [264] "diameter2.cisco.com" (M)


DB-530

May 2008


*May 9 17:59:14.840: DIAMETER: Origin-Realm [296] "cisco.com" (M) 65940780: 01000050 00000118 00000000 ...P........ 65940790: 8AC75173 8AC75173 0000010C 4000000C .GQs.GQs....@... 659407A0: 000007D1 00000108 4000001B 6469616D [email protected] 659407B0: 65746572 322E6369 73636F2E 636F6D00 eter2.cisco.com. 659407C0: 00000128 40000011 63697363 6F2E636F ...(@...cisco.co 659407D0: 6D000000 00 m.... *May 9 17:59:14.840: Dia Base: Request message hash ctx removed for [2328318323/2328318323] *May 9 17:59:14.840: Dia Base: (C000000C): Received msg event from message i/o *May 9 17:59:14.840: Dia Peer FSM (50F63888): input event RCV_DWA in state OPEN *May 9 17:59:14.840: Dia Peer FSM (50F63888): Starting Watchdog timer *May 9 17:59:14.840: Dia Peer FSM (50F63888): event RCV_DWA, state OPEN-->OPEN

Periodic connection attempt when the peer connection is broken *May 9 18:07:18.472: Dia Transport: socket 0 READ event: UP->CLOSE due to bytes read = 0 *May 9 18:07:18.472: Dia Base: (8600000E): Received peer disconnection event from transport *May 9 18:07:18.472: %DIABASE-4-DIA_PEER_DOWN: Diameter peer 9.113.33.6 port 3868 TCP DOWN *May 9 18:07:18.472: Dia Peer FSM (2068FF44): input event PEER_DISC in state OPEN *May 9 18:07:18.472: Dia Peer FSM (2068FF44): Starting Reconnect timer *May 9 18:07:18.472: Dia Peer FSM (2068FF44): event PEER_DISC, state OPEN-->CLOSED *May 9 18:07:48.472: Dia Peer FSM (2068FF44): input event START in state CLOSED *May 9 18:07:48.472: Dia Peer FSM (2068FF44): Starting Connection timer *May 9 18:07:48.472: Dia Peer FSM (2068FF44): event START, state CLOSED-->WAIT_CONN_ACK *May 9 18:07:48.472: Dia Transport: socket 0 - connecting to 9.113.33.6 (3868) *May 9 18:07:48.472: Dia Transport: socket 0 - connection in progress *May 9 18:07:48.472: Dia Transport: socket 0 - local address 9.113.33.5 (61122) *May 9 18:07:48.472: Dia Transport: socket 0 - CONN_WAIT->CLOSE *May 9 18:07:48.472: Dia Base: (8600000E): Received peer disconnection event from transport *May 9 18:07:48.472: Dia Peer FSM (2068FF44): input event PEER_DISC in state WAIT_CONN_ACK *May 9 18:07:48.472: Dia Peer FSM (2068FF44): Starting Reconnect timer *May 9 18:07:48.472: Dia Peer FSM (2068FF44): event PEER_DISC, state WAIT_CONN_ACK-->CLOSED

Peer disconnection when a peer configuration is removed Ginger(config)#no diameter peer watch Ginger(config)# *May 9 18:05:02.812: Dia Base: Peer unconfigured, start peer disconnection *May 9 18:05:02.812: Dia Base: (C000000C): Received peer unconfiguration event *May 9 18:05:02.812: Dia Peer FSM (50F63888): input event STOP in state OPEN


DB-531


*May 9 18:05:02.812: Dia Base: Sending diameter message to peer "diameter2.cisco.com" *May 9 18:05:02.812: DIAMETER: DPR message, ver=1, len=60, app=0, [2328318329/2328318329] *May 9 18:05:02.812: DIAMETER: Origin-host-name [264] "host" (M) *May 9 18:05:02.816: DIAMETER: Origin-Realm [296] "cisco" (M) *May 9 18:05:02.816: DIAMETER: Peer-disconnect-reason [273] Server-do-not-want-to-talk (M) 653D1810: 0100003C 8000011A ...CLOSING *May 9 18:05:02.816: Dia Transport: Dia Transport write message event *May 9 18:05:02.816: Dia Transport: socket 0 - complete msg sent *May 9 18:05:02.816: Dia Transport: socket 0 - complete read of 20 bytes *May 9 18:05:02.816: Dia Transport: complete header read from socket 0 *May 9 18:05:02.816: Dia Transport: read msg (60) bytes from socket 0 *May 9 18:05:02.816: Dia Transport: socket 0 - complete read of 60 bytes *May 9 18:05:02.816: Dia Base: Diameter message received from the peer "diameter2.cisco.com" *May 9 18:05:02.816: DIAMETER: DPA message, ver=1, len=80, app=0, [2328318329/2328318329] *May 9 18:05:02.816: DIAMETER: Result-code [268] 2001 (M) *May 9 18:05:02.816: DIAMETER: Origin-host-name [264] "diameter2.cisco.com" (M) *May 9 18:05:02.816: DIAMETER: Origin-Realm [296] "cisco.com" (M) 65913A20: 01000050 ...P 65913A30: 0000011A 00000000 8AC75179 8AC75179 .........GQy.GQy 65913A40: 0000010C 4000000C 000007D1 00000108 [email protected].... 65913A50: 4000001B 6469616D 65746572 322E6369 @...diameter2.ci 65913A60: 73636F2E 636F6D00 00000128 40000011 sco.com....(@... 65913A70: 63697363 6F2E636F 6D000000 00 cisco.com.... *May 9 18:05:02.816: Dia Base: Request message hash ctx removed for [2328318329/2328318329] *May 9 18:05:02.816: Dia Base: (C000000C): Received msg event from message i/o *May 9 18:05:02.816: Dia Peer FSM (50F63888): input event RCV_DPA in state CLOSING *May 9 18:05:02.816: Dia Base: (C000000C): Free the peer connection context 50F63888

Related Commands

Command

Description

show diameter peer

Displays Diameter peer configuration information.


DB-532

May 2008

Debug Commands debug dlsw

debug dlsw To enable debugging of data-link switching plus (DLSw+), use the debug dlsw command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dlsw [border-peers [interface interface | ip address ip-address] | core [flow-control messages | state | xid] [circuit-number] | local-circuit circuit-number | peers [interface interface [fast-errors | fast-paks] | ip address ip-address [fast-errors | fast-paks | fst-seq | udp]] | reachability [error | verbose] [sna | netbios] no debug dlsw [border-peers [interface interface | ip address ip-address] | core [flow-control messages | state | xid] [circuit-number] | local-circuit circuit-number | peers [interface interface [fast-errors | fast-paks] | ip address ip-address [fast-errors | fast-paks | fst-seq | udp]] | reachability [error | verbose] [sna | netbios]

Syntax Description

border-peers

(Optional) Enables debugging output for border peer events.

interface interface

(Optional) Specifies a remote peer to debug by a direct interface.

ip address ip-address

(Optional) Specifies a remote peer to debug by its IP address.

core

(Optional) Enables debugging output for DLSw core events.

flow-control

(Optional) Enables debugging output for congestion in the WAN or at the remote end station.

messages

(Optional) Enables debugging output of core messages—specific packets received by DLSw either from one of its peers or from a local medium via the Cisco link services interface.

state

(Optional) Enables debugging output for state changes on the circuit.

xid

(Optional) Enables debugging output for the exchange identification state machine.

circuit-number

(Optional) Specifies the circuit for which you want core debugging output to reduce the output.

local-circuit circuit-number

(Optional) Enables debugging output for circuits performing local conversion. Local conversion occurs when both the input and output data-link connections are on the same local peer and no remote peer exists.

peers

(Optional) Enables debugging output for peer events.

fast-errors

(Optional) Debugs errors for fast-switched packets.

fast-paks

(Optional) Debugs fast-switched packets.

fst-seq

(Optional) Debugs Fast-Sequenced Transport (FST) sequence numbers on fast switched packets.

udp

(Optional) Debugs User Datagram Protocol (UDP) packets.

reachability

(Optional) Enables debugging output for reachability events (explorer traffic). If no options are specified, event-level information is displayed for all protocols.


DB-533


Usage Guidelines

error | verbose

(Optional) Specifies how much reachability information you want displayed. The verbose keyword displays everything, including errors and events. The error keyword displays error information only. If no option is specified, event-level information is displayed.

sna | netbios

(Optional) Specifies that reachability information be displayed for only Systems Network Architecture (SNA) or Network Basic Input/Output System (NetBIOS) protocols. If no option is specified, information for all protocols is displayed.

When you specify no optional keywords, the debug dlsw command enables all available DLSW debugging output. Normally you need to use only the error or verbose option of the debug dlsw reachability command to help identify problems. The error option is recommended for use by customers and provides a subset of the messages from the normal event-level debugging. The verbose option provides a very detailed view of events, and is typically used only by service personnel. To reduce the amount of debug information displayed, use the sna or netbios option with the debug dlsw reachability command if you know that you have an SNA or NetBIOS problem. The DLSw core is the engine that is responsible for the establishment and maintenance of remote circuits. If possible, specifying the index of the specific circuit you want to debug reduces the amount of output displayed. However, if you want to watch a circuit initially come up, do not use the circuit-number option with the core keyword. The core flow-control option provides information about congestion in the WAN or at the remote end station. In these cases, DLSw sends Receiver Not Ready (RNR) frames on its local circuits, slowing data traffic on established sessions and giving the congestion an opportunity to clear. The core state option allows you to see when the circuit changes state. This capability is especially useful for determining why a session cannot be established or why a session is being disconnected. The core XID option allows you to track the exchange identification (XID)-state machine. The router tracks XID commands and responses used in negotiations between end stations before establishing a session.

Examples

The following examples show and explain some of the typical DLSw debugging messages you might see when using the debug dlsw command. The following example enables UDP packet debugging for a specific remote peer: Router# debug dlsw peers ip-address 1.1.1.6 udp

The following message is sample output from the debug dlsw border-peers command: *Mar *Mar *Mar *Mar

10 10 10 10

17:39:56: 17:39:56: 17:40:19: 17:40:22:

CSM: delete group mac cache for group 0 CSM: delete group name cache for group 0 CSM: update group cache for mac 0000.3072.1070, group 10 DLSw: send_to_group_members(): copy to peer 10.19.32.5

The following message is from a router that initiated a TCP connection: DLSw: DLSw: DLSw: DLSw:

START-TPFSM (peer 10.3.8.7(2065)): event:ADMIN-OPEN CONNECTION state:DISCONN dtp_action_a() attempting to connect peer 10.3.8.7(2065) END-TPFSM (peer 10.3.8.7(2065)): state:DISCONN->WAIT_WR Async Open Callback 10.3.8.7(2065) -> 11002


DB-534

May 2008


DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw:

START-TPFSM (peer 10.3.8.7(2065)): event:TCP-WR PIPE OPENED state:WAIT_WR dtp_action_f() start read open timer for peer 10.3.8.7(2065) END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_WR->WAIT_RD passive open 10.3.8.7(11004) -> 2065 START-TPFSM (peer 10.3.8.7(2065)): event:TCP-RD PIPE OPENED state:WAIT_RD dtp_action_g() read pipe opened for peer 10.3.8.7(2065) CapExId Msg sent to peer 10.3.8.7(2065) END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_RD->WAIT_CAP START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP dtp_action_j() cap msg rcvd from peer 10.3.8.7(2065) Recv CapExId Msg from peer 10.3.8.7(2065) Pos CapExResp sent to peer 10.3.8.7(2065) END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->WAIT_CAP START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP dtp_action_j() cap msg rcvd from peer 10.3.8.7(2065) Recv CapExPosRsp Msg from peer 10.3.8.7(2065) END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->WAIT_CAP Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP EXCHANGED state:WAIT_CAP dtp_action_k() cap xchged for peer 10.3.8.7(2065) closing read pipe tcp connection for peer 10.3.8.7(2065) END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->PCONN_WT Processing delayed event:TCP-PEER CONNECTED - prev state:PCONN_WT START-TPFSM (peer 10.3.8.7(2065)): event:TCP-PEER CONNECTED state:PCONN_WT dtp_action_m() peer connected for peer 10.3.8.7(2065) END-TPFSM (peer 10.3.8.7(2065)): state:PCONN_WT->CONNECT START-TPFSM (peer 10.3.8.7(2065)): event:CORE-ADD CIRCUIT state:CONNECT dtp_action_u(), peer add circuit for peer 10.3.8.7(2065) END-TPFSM (peer 10.3.8.7(2065)): state:CONNECT->CONNECT

The following message is from a router that received a TCP connection: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw:

passive open 10.10.10.4(11002) -> 2065 START-TPFSM (peer 10.10.10.4(2065)): event:TCP-RD PIPE OPENED state:DISCONN dtp_action_c() opening write pipe for peer 10.10.10.4(2065) END-TPFSM (peer 10.10.10.4(2065)): state:DISCONN->WWR_RDOP Async Open Callback 10.10.10.4(2065) -> 11004 START-TPFSM (peer 10.10.10.4(2065)): event:TCP-WR PIPE OPENED state:WWR_RDOP dtp_action_i() write pipe opened for peer 10.10.10.4(2065) CapExId Msg sent to peer 10.10.10.4(2065) END-TPFSM (peer 10.10.10.4(2065)): state:WWR_RDOP->WAIT_CAP START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP dtp_action_j() cap msg rcvd from peer 10.10.10.4(2065) Recv CapExId Msg from peer 10.10.10.4(2065) Pos CapExResp sent to peer 10.10.10.4(2065) END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->WAIT_CAP START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP dtp_action_j() cap msg rcvd from peer 10.10.10.4(2065) Recv CapExPosRsp Msg from peer 10.10.10.4(2065) END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->WAIT_CAP Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP EXCHANGED state:WAIT_CAP dtp_action_k() cap xchged for peer 10.10.10.4(2065) END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->PCONN_WT dlsw_tcpd_fini() for peer 10.10.10.4(2065) dlsw_tcpd_fini() closing write pipe for peer 10.10.10.4 START-TPFSM (peer 10.10.10.4(2065)): event:TCP-CLOSE WR PIPE state:PCONN_WT dtp_action_l() close write pipe for peer 10.10.10.4(2065) closing write pipe tcp connection for peer 10.10.10.4(2065) END-TPFSM (peer 10.10.10.4(2065)): state:PCONN_WT->PCONN_WT Processing delayed event:TCP-PEER CONNECTED - prev state:PCONN_WT START-TPFSM (peer 10.10.10.4(2065)): event:TCP-PEER CONNECTED state:PCONN_WT dtp_action_m() peer connected for peer 10.10.10.4(2065) END-TPFSM (peer 10.10.10.4(2065)): state:PCONN_WT->CONNECT


DB-535


DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:CORE-ADD CIRCUIT state:CONNECT DLSw: dtp_action_u(), peer add circuit for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:CONNECT->CONNECT

The following message is from a router that initiated an FST connection: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw:

START-FSTPFSM (peer 10.10.10.4(0)): event:ADMIN-OPEN CONNECTION state:DISCONN dfstp_action_a() attempting to connect peer 10.10.10.4(0) Connection opened for peer 10.10.10.4(0) CapExId Msg sent to peer 10.10.10.4(0) END-FSTPFSM (peer 10.10.10.4(0)): state:DISCONN->WAIT_CAP START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP dfstp_action_e() cap msg rcvd for peer 10.10.10.4(0) Recv CapExPosRsp Msg from peer 10.10.10.4(0) END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->WAIT_CAP START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP dfstp_action_e() cap msg rcvd for peer 10.10.10.4(0) Recv CapExId Msg from peer 10.10.10.4(0) Pos CapExResp sent to peer 10.10.10.4(0) END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->WAIT_CAP Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP EXCHANGED state:WAIT_CAP dfstp_action_f() cap xchged for peer 10.10.10.4(0) END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->CONNECT

The following message is from a router that received an FST connection: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw:

START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP MSG RCVD state:DISCONN dfstp_action_c() cap msg rcvd for peer 10.3.8.7(0) Recv CapExId Msg from peer 10.3.8.7(0) Pos CapExResp sent to peer 10.3.8.7(0) CapExId Msg sent to peer 10.3.8.7(0) END-FSTPFSM (peer 10.3.8.7(0)): state:DISCONN->WAIT_CAP START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP dfstp_action_e() cap msg rcvd for peer 10.3.8.7(0) Recv CapExPosRsp Msg from peer 10.3.8.7(0) END-FSTPFSM (peer 10.3.8.7(0)): state:WAIT_CAP->WAIT_CAP Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP EXCHANGED state:WAIT_CAP dfstp_action_f() cap xchged for peer 10.3.8.7(0) END-FSTPFSM (peer 10.3.8.7(0)): state:WAIT_CAP->CONNECT

The following message is from a router that initiated an LLC2 connection: DLSw-LLC2: Sending enable port ; port no : 0 PEER-DISP Sent : CLSI Msg : ENABLE.Req dlen: 20 DLSw: Peer Received : CLSI Msg : ENABLE.Cfm CLS_OK dlen: 20 DLSw-LLC2 : Sending activate sap for Serial1 - port_id = 887C3C port_type = 7 dgra(UsapID) = 952458 PEER-DISP Sent : CLSI Msg : ACTIVATE_SAP.Req dlen: 60 DLSw: Peer Received : CLSI Msg : ACTIVATE_SAP.Cfm CLS_OK dlen: 60 DLSw Got ActSapcnf back for Serial1 - port_id = 8978204, port_type = 7, psap_id = 0 DLSw: START-LLC2PFSM (peer on interface Serial1): event:ADMIN-OPEN CONNECTION state:DISCONN DLSw: dllc2p_action_a() attempting to connect peer on interface Serial1 PEER-DISP Sent : CLSI Msg : REQ_OPNSTN.Req dlen: 106 DLSw: END-LLC2PFSM (peer on interface Serial1): state:DISCONN->ROS_SENT DLSw: Peer Received : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 106 DLSw: START-LLC2PFSM (peer on interface Serial1): event:CLS-REQOPNSTN.CNF state:ROS_SENT DLSw: dllc2p_action_c() PEER-DISP Sent : CLSI Msg : CONNECT.Req dlen: 16 DLSw: END-LLC2PFSM (peer on interface Serial1): state:ROS_SENT->CON_PEND


DB-536

May 2008


DLSw: Peer Received : CLSI Msg : CONNECT.Cfm CLS_OK dlen: 28 DLSw: START-LLC2PFSM (peer on interface Serial1): event:CLS-CONNECT.CNF state:CON_PEND DLSw: dllc2p_action_e() send capabilities to peer on interface Serial1 PEER-DISP Sent : CLSI Msg : SIGNAL_STN.Req dlen: 8 PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 418 DLSw: CapExId Msg sent to peer on interface Serial1 DLSw: END-LLC2PFSM (peer on interface Serial1): state:CON_PEND->WAIT_CAP DLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 418 DLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial1 DLSw: Recv CapExId Msg from peer on interface Serial1 PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 96 DLSw: Pos CapExResp sent to peer on interface Serial1 DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->WAIT_CAP DLSw: DLSw: DLSw: DLSw: DLSw:

Peer Received : CLSI Msg : DATA.Ind dlen: 96 START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP MSG RCVD state:WAIT_CAP dllc2p_action_k() cap msg rcvd for peer on interface Serial1 Recv CapExPosRsp Msg from peer on interface Serial1 END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->WAIT_CAP

DLSw: DLSw: DLSw: DLSw:

Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP EXCHANGED state:WAIT_CAP dllc2p_action_l() cap xchged for peer on interface Serial1 END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->CONNECT

The following message is from a router that received a Logical Link Control, type 2 (LLC2) connection: DLSw-LLC2: Sending enable port ; port no : 0 PEER-DISP Sent : CLSI Msg : ENABLE.Req dlen: 20 DLSw: Peer Received : CLSI Msg : ENABLE.Cfm CLS_OK dlen: DLSw-LLC2 : Sending activate sap for Serial0 - port_id = port_type = 7 dgra(UsapID) = 93AB34 PEER-DISP Sent : CLSI Msg : ACTIVATE_SAP.Req dlen: 60 DLSw: Peer Received : CLSI Msg : ACTIVATE_SAP.Cfm CLS_OK DLSw Got ActSapcnf back for Serial0 - port_id = 8944700,

20 887C3C

dlen: 60 port_type = 7, psap_id = 0

DLSw: Peer Received : CLSI Msg : CONECT_STN.Ind dlen: 39 DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-CONNECT_STN.IND state:DISCONN DLSw: dllc2p_action_s() conn_stn for peer on interface Serial0 PEER-DISP Sent : CLSI Msg : REQ_OPNSTN.Req dlen: 106 DLSw: END-LLC2PFSM (peer on interface Serial0): state:DISCONN->CONS_PEND DLSw: Peer Received : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 106 DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-REQOPNSTN.CNF state:CONS_PEND DLSw: dllc2p_action_h() send capabilities to peer on interface Serial0 PEER-DISP Sent : CLSI Msg : CONNECT.Rsp dlen: 20 PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 418 DLSw: CapExId Msg sent to peer on interface Serial0 DLSw: END-LLC2PFSM (peer on interface Serial0): state:CONS_PEND->WAIT_CAP DLSw: Peer Received : CLSI Msg : CONNECTED.Ind dlen: 8 DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-CONNECTED.IND state:WAIT_CAP DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAP DLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 418 DLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial0 DLSw: Recv CapExId Msg from peer on interface Serial0 PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 96 DLSw: Pos CapExResp sent to peer on interface Serial0 DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAP


DB-537


DLSw: DLSw: DLSw: DLSw: DLSw:

Peer Received : CLSI Msg : DATA.Ind dlen: 96 START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP MSG RCVD state:WAIT_CAP dllc2p_action_k() cap msg rcvd for peer on interface Serial0 Recv CapExPosRsp Msg from peer on interface Serial0 END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAP


Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP EXCHANGED state:WAIT_CAP dllc2p_action_l() cap xchged for peer on interface Serial0 END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->CONNECT

The following messages occur when a CUR_ex (CANUREACH explorer) frame is received from other peers, and the peer statements or the promiscuous keyword have not been enabled so that the router is not configured correctly: 22:42:44: DLSw: Not promiscuous - Rej conn from 172.20.96.1(2065) 22:42:51: DLSw: Not promiscuous - Rej conn from 172.20.99.1(2065)

In the following messages, the router sends a keepalive message every 30 seconds to keep the peer connected. If three keepalive messages are missed, the peer is torn down. These messages are displayed only if keepalives are enabled (by default, keepalives are disabled): 22:44:03: 22:44:03: 22:44:34: 22:44:34:


Keepalive Keepalive Keepalive Keepalive

Request sent to peer 172.20.98.1(2065) (168243148) Response from peer 172.20.98.1(2065) (168243176) Request sent to peer 172.20.98.1(2065) (168274148) Response from peer 172.20.98.1(2065) (168274172)

The following peer debugging messages indicate that the local peer is disconnecting from the specified remote peer because of missed peer keepalives: 0:03:24: 0:03:24: 0:03:24: 0:03:24:

DLSw: DLSw: DLSW: DLSw:

keepalive failure for peer on interface Serial0 action_d(): for peer on interface Serial0 DIRECT aborting connection for peer on interface Serial0 peer on interface Serial0, old state CONNECT, new state DISCONN

The following peer debugging messages result from an attempt to connect to an IP address that does not have DLSw enabled. The local router attempts to connect in 30-second intervals: 23:13:22: 23:13:22: 23:13:22: 23:13:52: 23:13:52: 23:13:52:

action_a() attempting to connect peer 172.20.100.1(2065) DLSw: CONN: peer 172.20.100.1 open failed, rejected [9] action_a() retries: 8 next conn time: 861232504 action_a() attempting to connect peer 172.20.100.1(2065) DLSw: CONN: peer 172.20.100.1 open failed, rejected [9] action_a() retries: 9 next conn time: 861292536

The following peer debugging messages that indicates a remote peer statement is missing on the router (address 172.20.100.1) to which the connection attempt is sent: 23:14:52: 23:14:52: 23:14:52: 23:14:52: 23:14:52: 23:14:52: 23:14:52:

action_a() attempting to connect peer 172.20.100.1(2065) DLSw: action_a(): Write pipe opened for peer 172.20.100.1(2065) DLSw: peer 172.20.100.1(2065), old state DISCONN, new state WAIT_RD DLSw: dlsw_tcpd_fini() closing connection for peer 172.20.100.1 DLSw: action_d(): for peer 172.20.100.1(2065) DLSw: aborting tcp connection for peer 172.20.100.1(2065) DLSw: peer 172.20.100.1(2065), old state WAIT_RD, new state DISCONN

The following messages show a peer connection opening with no errors or abnormal events: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37:

action_a() attempting to connect peer 172.20.100.1(2065) DLSw: action_a(): Write pipe opened for peer 172.20.100.1(2065) DLSw: peer 172.20.100.1(2065), old state DISCONN, new state WAIT_RD DLSW: passive open 172.20.100.1(17762) -> 2065 DLSw: action_c(): for peer 172.20.100.1(2065) DLSw: peer 172.20.100.1(2065), old state WAIT_RD, new state CAP_EXG


DB-538

May 2008


23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:37: 23:16:38:

DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw: DLSw:

peer 172.20.100.1(2065) conn_start_time set to 861397784 CapExId Msg sent to peer 172.20.100.1(2065) Recv CapExId Msg from peer 172.20.100.1(2065) Pos CapExResp sent to peer 172.20.100.1(2065) action_e(): for peer 172.20.100.1(2065) Recv CapExPosRsp Msg from peer 172.20.100.1(2065) action_e(): for peer 172.20.100.1(2065) peer 172.20.100.1(2065), old state CAP_EXG, new state CONNECT dlsw_tcpd_fini() closing write pipe for peer 172.20.100.1 action_g(): for peer 172.20.100.1(2065) closing write pipe tcp connection for peer 172.20.100.1(2065) peer_act_on_capabilities() for peer 172.20.100.1(2065)

The following two messages show that an information frame is passing through the router: DLSw: dlsw_tr2fct() lmac:c000.a400.0000 rmac:0800.5a29.75fe ls:5 rs:4 i:34 DLSw: dlsw_tr2fct() lmac:c000.a400.0000 rmac:0800.5a29.75fe ls:4 rs:4 i:34

Sample debug DLSw Reachability Messages

The messages in this section are based on the following criteria: •

Reachability is stored in cache. DLSw+ maintains two reachability caches: one for MAC addresses and one for NetBIOS names. Depending on how long entries have been in the cache, they are either fresh or stale.

•

If a router has a fresh entry in the cache for a certain resource, it answers a locate request for that resource without verifying that it is still available. A locate request is typically a TEST frame for MAC addresses or a FIND_NAME_QUERY for NetBIOS.

•

If a router has a stale entry in the cache for a certain resource, it verifies that the entry is still valid before answering a locate request for the resource by sending a frame to the last known location of the resource and waits for a resource. If the entry is a REMOTE entry, the router sends a CUR_ex frame to the remote peer to verify. If the entry is a LOCAL entry, it sends either a TEST frame or a NetBIOS FIND_NAME_QUERY on the appropriate local port.

•

By default, all reachability cache entries remain fresh for 4 minutes after they are learned. For MAC addresses, you can change this time with the dlsw timer sna-verify-interval command. For NetBIOS names, you can change this time with the dlsw timer netbios-verify-interval command.

•

By default, all reachability cache entries age out of the cache 16 minutes after they are learned. For MAC addresses, you can change this time with the dlsw timer sna-cache-timeout command. For NetBIOS names, you can change the time with the dlsw timer netbios-cache-timeout command.

Table 76 describes the debug output indicating that the DLSW router received an SSP message that is flow controlled and should be counted against the window of the sender. Dec 6 11:26:49: CSM: Received SSP CUR csex flags = 80, mac 4000.90b1.26cf, The csex flags = 80 means that this is an CUR_ex (explorer). Dec 5 10:48:33: DLSw: 1620175180 decr r - s:27 so:0 r:27 ro:0

Table 76

debug dlsw Field Descriptions

Field

Description

decr r

Decrement received count.

s

This DLSW router’s granted units for the circuit.

so

0=This DLSW router does not owe a flow control acknowledgment. 1=This router owes a flow control acknowledgment.


DB-539


Table 76

debug dlsw Field Descriptions (continued)

Field

Description

r

Partner’s number of granted units for the circuit.

ro

Indicates whether the partner owes flow control acknowledgment.

The following message shows that DLSW is sending an I frame to a LAN: Dec

5 10:48:33:

DISP Sent : CLSI Msg : DATA.Req

dlen: 1086

The following message shows that DLSW received the I frame from the LAN: Dec

5 10:48:35:

DLSW Received-disp : CLSI Msg : DATA.Ind

dlen: 4

The following messages show that the reachability cache is cleared: Router# clear dlsw rea 23:44:11: 23:44:11: 23:44:11: 23:44:11: 23:44:11:

CSM: CSM: CSM: CSM: CSM:

Clearing CSM cache delete local mac cache for port 0 delete local name cache for port 0 delete remote mac cache for peer 0 delete remote name cash dlsw rea

The next group of messages show that the DLSW reachability cache is added, and that a name query is perform from the router MARIAN: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:11: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12:

CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM:

core_to_csm CLSI_MSG_PROC - port_id 5EFBB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 5EFBB4 update local cache for name MARIAN , port 5EFBB4 Received CLS_UDATA_STN from Core Received netbios frame type A Processing Name Query Netbios Name Query: ws_status = 6 Write to peer 0 ok. Freeing clsi message core_to_csm CLSI_MSG_PROC - port_id 658AB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 658AB4 update local cache for name MARIAN , port 658AB4 Received CLS_UDATA_STN from Core Received netbios frame type A Processing Name Query Netbios Name Query: ws_status = 5 DLXNR_PEND match found.... drop name query Freeing clsi message core_to_csm CLSI_MSG_PROC - port_id 5EFBB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 5EFBB4 update local cache for name MARIAN , port 5EFBB4 Received CLS_UDATA_STN from Core Received netbios frame type A Processing Name Query Netbios Name Query: ws_status = 5 DLXNR_PEND match found.... drop name query Freeing clsi message core_to_csm CLSI_MSG_PROC - port_id 658AB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 658AB4 update local cache for name MARIAN , port 658AB4


DB-540

May 2008


23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:12: 23:45:18: 23:45:18: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38:

CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM:

Received CLS_UDATA_STN from Core Received netbios frame type A Processing Name Query Netbios Name Query: ws_status = 5 DLXNR_PEND match found.... drop name query Freeing clsi message core_to_csm CLSI_MSG_PROC - port_id 5EFBB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 5EFBB4 update local cache for name MARIAN , port 5EFBB4 Received CLS_UDATA_STN from Core Received netbios frame type A Processing Name Query Netbios Name Query: ws_status = 5 DLXNR_PEND match found.... drop name query Freeing clsi message core_to_csm CLSI_MSG_PROC - port_id 658AB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 658AB4 update local cache for name MARIAN , port 658AB4 Received CLS_UDATA_STN from Core Received netbios frame type A Processing Name Query Netbios Name Query: ws_status = 5 DLXNR_PEND match found.... drop name query Freeing clsi message Deleting Reachability cache Deleting DLX NR pending record.... core_to_csm CLSI_MSG_PROC - port_id 5EFBB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 5EFBB4 update local cache for name MARIAN , port 5EFBB4 Received CLS_UDATA_STN from Core Received netbios frame type 8 Write to peer 0 ok. Freeing clsi message core_to_csm CLSI_MSG_PROC - port_id 658AB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 658AB4 update local cache for name MARIAN , port 658AB4 Received CLS_UDATA_STN from Core Received netbios frame type 8 Write to peer 0 ok. Freeing clsi message

The following messages show that the router named MARIAN is added to the network: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38: 23:45:38:

CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM: CSM:

core_to_csm CLSI_MSG_PROC - port_id 5EFBB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 5EFBB4 update local cache for name MARIAN , port 5EFBB4 Received CLS_UDATA_STN from Core Received netbios frame type 8 Write to peer 0 ok. Freeing clsi message core_to_csm CLSI_MSG_PROC - port_id 658AB4 0800.5a30.7a9b passes local mac excl. filter update local cache for mac 0800.5a30.7a9b, port 658AB4 update local cache for name MARIAN , port 658AB4 Received CLS_UDATA_STN from Core Received netbios frame type 8 Write to peer 0 ok. Freeing clsi message


DB-541


In the next group of messages, an attempt is made to add the router named GINGER on the Ethernet interface: 0:07:44: 0:07:44: 0:07:44: 0:07:44: 0:07:44: 0:07:44: 0:07:44:

CSM: CSM: CSM: CSM: CSM: CSM: CSM:

core_to_csm CLSI_MSG_PROC - port_id 658AB4 0004.f545.24e6 passes local mac excl. filter update local cache for mac 0004.f545.24e6, port 658AB4 update local cache for name GINGER , port 658AB4 Received CLS_UDATA_STN from Core Received netbios frame type 8 Write to peer 0 ok.

In the following example, the output from the show dlsw reachability command indicates that GINGER is on the Ethernet interface and MARIAN is on the Token Ring interface: Router# show dlsw reachability DLSw MAC address reachability cache list Mac Addr status Loc. peer/port 0004.f545.24e6 FOUND LOCAL P007-S000 0800.5a30.7a9b FOUND LOCAL P000-S000 P007-S000 DLSw NetBIOS Name reachability cache list NetBIOS Name status Loc. peer/port GINGER FOUND LOCAL P007-S000 MARIAN FOUND LOCAL P000-S000 P007-S000

rif --no rif-06C0.0621.7D00 F0F8.0006.A6FC.005F.F100.0000.0000.0000

rif --no rif-06C0.0621.7D00 --no rif--


DB-542

May 2008

Debug Commands debug dmsp doc-to-fax

debug dmsp doc-to-fax Note

In release 12.3(8)T, the debug dmsp doc-to-fax command is replaced by the debug fax dmsp command. See the debug fax dmsp command for more information. To display debugging messages for the doc Media Service Provider (docMSP) TIFF or text2Fax engine, use the debug dmsp doc-to-fax command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dmsp doc-to-fax [text-to-fax | tiff-reader] no debug dmsp doc-to-fax [text-to-fax | tiff-reader]

Syntax Description

text-to-fax

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

tiff-reader

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

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI

This command was introduced on the Cisco AS5300 access server.

12.3(8)T

This command was replaced by the debug fax dmsp command in the Cisco IOS 12.3T release.

12.2(33)SRA


12.2SX


Examples

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

1 1 1 1

04:58:39.898: 04:58:39.902: 04:58:39.902: 04:58:39.902:

docmsp_call_setup_request: callid=18 docmsp_call_setup_request(): ramp data dir=OFFRAMP, conf dir=SRC docmsp_caps_ind: call id=18, src=17 docmsp_bridge cfid=5, srccid=18, dstcid=17

Jan Jan Jan

1 04:58:39.902: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC, encode out=2 1 04:58:39.902: docmsp_rcv_msp_ev: call id =18, evID = 42 1 04:58:39.902: docmsp_bridge cfid=6, srccid=18, dstcid=15


DB-543

Debug Commands debug dmsp doc-to-fax

Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan

Related Commands

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

04:58:39.902: 04:58:39.902: 04:58:39.902: 04:58:39.902: 04:58:39.922: 04:58:42.082: 04:58:42.082: 04:58:42.082: 04:58:42.102: 04:58:42.106: 04:58:42.106: 04:58:42.122: 04:58:42.126: 04:58:42.126: 04:58:42.142: 04:58:42.146:

docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=DEST, encode out=2 docmsp_process_rcv_data: call id src=0, dst=18 docmsp_generate_page: docmsp_generate_page: new context for Call 18 docmsp_get_msp_event_buffer: docmsp_xmit: call id src=15, dst=18 docmsp_process_rcv_data: call id src=15, dst=18 offramp_data_process: docmsp_xmit: call id src=15, dst=18 docmsp_process_rcv_data: call id src=15, dst=18 offramp_data_process: docmsp_xmit: call id src=15, dst=18 docmsp_process_rcv_data: call id src=15, dst=18 offramp_data_process: docmsp_xmit: call id src=15, dst=18 docmsp_xmit: call id src=15, dst=18

Command

Description

debug dmsp fax-to-doc

Displays debugging messages for doc MPS fax-to-doc.


DB-544

May 2008

Debug Commands debug dmsp fax-to-doc

debug dmsp fax-to-doc Note

In release 12.3(8)T, the debug dmsp fax-to-doc command is replaced by the debug fax dmsp command. See the debug fax dmsp command for more information. To display debugging messages for doc MSP (docMSP) fax-to-doc, use the debug dmsp fax-to-doc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dmsp fax-to-doc [tiff-writer] no debug dmsp fax-to-doc [tiff-writer]

Syntax Description

tiff-writer

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI


12.3(8)T

This command was replaced by the debug fax dmsp command in the Cisco IOS 12.3T release.

12.2(33)SRA


12.2SX


Examples

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

The following is sample output from the debug dmsp fax-to-doc command: Router# debug dmsp fax-to-doc *Oct *Oct *Oct *Oct

16 16 16 16

08:29:54.487: 08:29:54.487: 08:29:54.487: 08:29:54.487:

docmsp_call_setup_request: callid=22 docmsp_call_setup_request(): ramp data dir=OFFRAMP, conf dir=SRC docmsp_caps_ind: call id=22, src=21 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 *Oct *Oct *Oct *Oct

16 16 16 16 16

08:29:54.487: 08:29:54.487: 08:29:54.487: 08:29:54.487: 08:29:54.515:

docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=DEST, encode out=2 docmsp_xmit: call id src=17, dst=22 docmsp_process_rcv_data: call id src=17, dst=22 offramp_data_process: docmsp_get_msp_event_buffer:


DB-545

Debug Commands debug dmsp fax-to-doc

*Oct *Oct *Oct *Oct

Related Commands

16 16 16 16

08:29:56.115: 08:29:56.115: 08:29:56.115: 08:29:56.115:

docmsp_call_setup_request: callid=24 docmsp_call_setup_request(): ramp data dir=ONRAMP, conf dir=DEST docmsp_caps_ind: call id=24, src=20 docmsp_bridge cfid=17, srccid=24, dstcid=20

Command

Description

debug dmsp doc-to-fax

Displays debugging messages for the doc Media Service Provider TIFF or text2Fax engine.


DB-546

May 2008

Debug Commands debug dmvpn

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

condition

(Optional) Specifies conditional debugging based on error level setting.

unmatched

(Optional) Specifies debugging when context information is not available.

peer

(Optional) Specifies information for a specific DMVPN peer.

nbma

(Optional) Displays DMVPN information based on peer mapping nonbroadcast access (NBMA) address.

tunnel

(Optional) Displays DMVPN information based on the peer virtual private network (VPN) address.

ip-address

(Optional) Specifies DMVPN peer IP address.

vrf vrf-name

(Optional) Displays information based on the specified virtual routing forwarding (VRF) name.

interface

(Optional) Displays DMVPN information based on a specific interface.

tunnel number

(Optional) Specifies the tunnel address for a DMVPN peer.

error

(Optional) Enables error level debugging.

detail

(Optional) Enables detail level debugging.

packet

(Optional) Enables packet level debugging.

all

(Optional) Enables all levels of debugging.

nhrp

(Optional) Enables Next Hop Resolution Protocol (NHRP) debugging only.

crypto

(Optional) Enables crypto Internet Key Exchange (IKE) and IPsec debugging only.

tunnel

(Optional) Enables tunnel protection debugging only.

socket

(Optional) Enables crypto secure socket debugging only.

all

(Optional) Enables NHRP, sockets, tunnel protection and crypto debugging.

Command Default

DMVPN debugging is not enabled.

Command Modes

Privileged EXEC


DB-547


Command History

Usage Guidelines

Release

Modification

12.4(9)T


12.2SX


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 DMVPN 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: •

debug crypto ipsec error

•

debug crypto isakmp error

•

debug nhrp error

Detail Level Debugging

When event level debugging is enabled with the debug dmvpn detail command, the following debugging commands are enabled by default: •

debug crypto ipsec

•

debug crypto isakmp

•

debug crypto sockets

•

debug nhrp

•

debug nhrp cache

•

debug nhrp rate

•

debug tunnel protection

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

•

debug nhrp extension

•

debug nhrp packet

Executing debug dmvpn all all with a high number of active sessions, may result in high CPU utilization and large data output.

The following example shows how to enable conditional DMVPN debugging for a specific peer NBMA address:


DB-548

May 2008


Router# debug dmvpn condition peer nbma 192.0.2.1

The following example shows how to enable conditional DMVPN debugging when context is not available to check against debugging conditions: Router# debug dmvpn condition unmatched

The 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

Command

Description

debug nhrp condition

Enables NHRP conditional debugging.

debug nhrp error

Displays NHRP error level debugging information.


DB-549

Debug Commands debug dot11 aaa

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 Descriptionn

accounting

Provides information about 802.11 AAA accounting packets.

authenticator

Provides information about MAC and Extensible Authentication Protocol (EAP) authentication packets. Use the following options to activate authenticator debugging: •

all—Activates debugging for all authenticator packets

•

dispatcher—Activates debugging for authentication request handler packets

•

mac-authen—Activates debugging for MAC authentication packets

•

process—Activates debugging for authenticator process packets

•

rxdata—Activates debugging for EAP over LAN (EAPOL) packets from client devices

•

state-machine—Activates debugging for authenticator state-machine packets

•

txdata—Activates debugging for EAPOL packets sent to client devices

dispatcher

Provides information about 802.11 AAA dispatcher (interface between association and manager) packets.

manager

Provides information about the AAA manager. Use these options to activate AAA manager debugging: •

all—Activates all AAA manager debugging

•

dispatcher—Activates debug information for AAA manager-authenticator dispatch traffic

•

keys—Activates debug information for AAA manager key processing

•

rxdata—Activates debugging for AAA manager packets received from client devices

•

state-machine—Activates debugging for AAA manager state-machine packets

•

supplicant—Activates debugging for Light Extensible Authentication Protocol (LEAP) supplicant packets

•

txdata—Activates debugging for AAA manager packets sent to client devices.


DB-550

May 2008

Debug Commands debug dot11 aaa

Command Default

Debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(4)JA


12.2(15)JA

This command was modified to include the accounting, authenticator, dispatcher, and manager debugging options.

12.4(2)T


12.2SX


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 accounting

Related Commands

Command

Description

debug dot11

Enables debugging of radio functions.

debug dot11 dot11radio Enables radio debug options.


DB-551

Debug Commands debug dot11 cac

debug dot11 cac Use the debug dot11 cac privileged EXEC command to begin debugging of admission control radio functions. Use the no form of this command to stop the debug operation. [no] debug dot11 cac {events | unit}

Note

Syntax Description

This command is not supported on repeaters.

events

Activates debugging of radio admission control events.

unit

Activates verbose debugging of radio admission control events.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)JA


12.2SX


Examples

This example shows how to begin debugging of all admission control radio-related events: SOAP-AP# debug dot11 cac events

This example shows how to begin verbose debugging of all admission control radio-related events: SOAP-AP# debug dot11 cac unit

This example shows how to stop debugging of all admission control radio-related events: SOAP-AP# debug dot11 cac events

This example shows how to stop verbose debugging of all admission control radio-related events: SOAP-AP# no debug dot11 cac unit


DB-552

May 2008

Debug Commands debug dot11 cac

Related Commands

Command

Description

admin-traffic (SSID configuration mode)

Enables CAC admission control for an SSID on the access point.

admit-traffic (QOS Class interface configuration mode)

Configures CAC admission control on the access point.

show debugging

Displays all debug settings and the debug packet headers

show dot11 ids eap

Displays all CAC radio events on the access point.

traffic-stream

Configures CAC traffic data rates and priorities for a radio interface on the access point.


DB-553

Debug Commands debug dot11 dot11radio

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

interface

The radio interface. The 2.4-GHz radio is 0. The 5-GHz radio is 1.

accept-radio-firmware

Configures the access point to disable checking the radio firmware version.

dfs simulate

Configures the access point to simulate radar generation as part of Dynamic Frequency Selection (DFS).

channel

(Optional) Radio channel to move to. Range is 24 to 161.

monitor

Enables RF monitor mode. Use these options to turn on monitor modes:

print

•

ack—Displays ACK packets. ACK packets acknowledge receipt of a signal, information, or packet.

•

address—Displays packets to or from the specified IP address

•

beacon—Displays beacon packets

•

crc—Displays packets with CRC errors

•

lines—Specifies a print line count

•

plcp—Displays Physical Layer Control Protocol (PLCP) packets

•

print—Enables RF monitor printing mode

•

probe—Displays probe packets

•

store—Enables RF monitor storage mode

Enables packet printing. Use these options to turn on packet printing: •

hex—Prints entire packets without formatting

•

if—Prints the in and out interfaces for packets

•

iv—Prints the packet Wired Equivalent Privacy (WEP) IV

•

lines—Prints the line count for the trace

•

mic—Prints the Cisco Message Integrity Check (MIC)

•

plcp—Displays the PLCP

•

printf—Prints using printf instead of buginf

•

raw—Prints without formatting data

•

shortadr—Prints MAC addresses in short form


DB-554

May 2008

Debug Commands debug dot11 dot11radio

stop-on-failure

Configures the access point to not restart when the radio driver fails.

trace

Enables trace mode. Use these options to turn on trace modes:

Command Default


Command Modes

Privileged EXEC

Command History

Release

•

off—Turns off traces

•

print—Enables trace printing

•

store—Enables trace storage

Modification

12.2(4)JA


12.4(2)T


12.2SX


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 crc

Related Commands

Command

Description

debug dot11

Enables debugging of radio functions.

debug dot11 aaa

Enables debugging of dot11 AAA operations.


DB-555

Debug Commands debug dot11 ids

debug dot11 ids Use the debug dot11 ids eap privileged EXEC command to enable debugging for wireless IDS monitoring. Use the no form of the command to disable IDS debugging. [no] debug dot11 ids {eap | cipher-errors}

Note

Syntax Description

This command is not supported on 1400 series bridges.

eap

Activates debugging of IDS authentication events

cipher-errors

Activates debugging of cipher errors detected by IDS

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)JA


12.2SX


Examples

This example shows how to activate wireless IDS debugging for authentication events: SOAP-AP# debug dot11 ids eap

Related Commands

Command

Description

dot11 ids eap attempts

Configures limits on authentication attempts and EAPOL flooding on scanner access points in monitor mode

show debugging


show dot11 ids eap

Displays wireless IDS statistics


DB-556

May 2008

Debug Commands debug dot11 ids mfp

debug dot11 ids mfp Use the debug dot11 ids mfp privileged EXEC command to debug Management Frame Protection (MFP) operations on the access point. [no] debug dot11 ids mfp ap [all] [detectors] [events] [generators] [io] [reporting] | wds [all] [detectors] [events] [generators] [reporting] [statistics] | wlccp

Syntax Description

ap

Debugs MFP events on the access point.

all

Debugs all MFP events.

detectors

Debugs MFP detector key management events.

events

Debugs high level MFP events.

generators

Debugs MFP generator key management events.

io

Debugs MFP IO (generate or detect frame) events.

reporting

Debugs MFP reporting events.

statistics

Debugs MFP WDS statistics received from the detectors.

wds

Debugs MFP WDS events.

wlccp

Debugs MFP WLCCP messages.

Defaults

There are no defaults for this command.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)JA


12.2SX


Examples

This example shows how to debug the MFP detectors on the access point: ap(config)# debug dot11 ids mfp ap detectors

Related Commands

Command

Description

dot11 ids mfp

Configures MFP parameters on the access point.

show dot11 ids mfp

Displays MFP parameters on the access point.


DB-557

Debug Commands debug dot11

debug dot11 Use the debug dot11 privileged EXEC command to begin debugging of radio functions. Use the no form of this command to stop the debug operation. [no] debug dot11 {events | packets | forwarding | mgmt | network-map | syslog | virtual-interface}

Syntax Description

events

Activates debugging of all radio related events

packets

Activates debugging of radio packets received and transmitted

forwarding

Activates debugging of radio forwarded packets

mgmt

Activates debugging of radio access point management activity

network-map

Activates debugging of radio association management network map

syslog

Activates debugging of radio system log

virtual-interface

Activates debugging of radio virtual interfaces

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)JA


12.2SX


Examples

This example shows how to begin debugging of all radio-related events: SOAP-AP# debug dot11 events

This example shows how to begin debugging of radio packets: SOAP-AP# debug dot11 packets

This example shows how to begin debugging of the radio system log: SOAP-AP# debug dot11 syslog

This example shows how to stop debugging of all radio related events: SOAP-AP# no debug dot11 events


DB-558

May 2008

Debug Commands debug dot11

Related Commands

Command

Description

show debugging


show interfaces dot11radio

Displays configuration and status information for the radio interface


DB-559

Debug Commands debug dot1x (EtherSwitch)

debug dot1x (EtherSwitch) To enable debugging of the 802.1x protocol when an Ethernet switch network module is installed, use the debug dot1x command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug dot1x {all | authsm | backend | besm | core | reauthsm} no debug dot1x {all | authsm | backend | besm | core | reauthsm}

Syntax Description

all

Enables debugging of all conditions.

authsm

Enables debugging of the authenticator state machine, which is responsible for controlling access to the network through 802.1x-enabled ports.

backend

Enables debugging of the interaction between the 802.1x process and the router RADIUS client.

besm

Enables debugging of the backend state machine, which is responsible for relaying authentication request between the client and the authentication server.

core

Enables debugging of the 802.1x process, which includes 802.1x initialization, configuration, and the interaction with the port manager module.

reauthsm

Enables debugging of the reauthentication state machine, which manages periodic reauthentication of the client.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(6)EA2


12.2(15)ZJ

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.

12.2(33)SRA


12.2SX


Usage Guidelines

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


DB-560

May 2008

Debug Commands debug dot1x (EtherSwitch)

Related Commands

Command

Description

show debugging

Displays information about the types of debugging that are enabled.

show dot1x

Displays 802.1x statistics, administrative status, and operational status for the router or for the specified interface.


DB-561

Debug Commands debug dot1x

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 [all | errors | events | feature | packets | redundancy | registry | state-machine] no debug dot1x [all | errors | events | feature | packets | redundancy | registry | state-machine]

Syntax Description

all

(Optional) Enables all 802.1X debugging messages.

errors

(Optional) Provides information about all 802.1X errors.

events

(Optional) Provides information about all 802.1X events.

feature

(Optional) Provides information about 802.1X features for switches only.

packets

(Optional) Provides information about all 802.1X packets.

redundancy

(Optional) Provides information about 802.1X redundancy.

registry

(Optional) Provides information about 802.1X registries.

state-machine

(Optional) Provides information regarding the 802.1X state machine.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(11)AX


12.1(14)EA1

The authsm, backend, besm, core, and reauthsm keywords were removed. The errors, events, packets, registry, and state-machine keywords were added.

12.3(2)XA

This command was integrated into Cisco IOS Release 12.3(2)XA.

12.3(4)T


12.3(11)T

The supplicant keyword was added.

12.2(25)SEE

The feature keyword was added for switches only.

12.4(6)T

The redundancy keyword was added. The aaa, process, rxdata, supplicant, txdata, and vlan keywords were deleted.

12.2(33)SRA


12.2SX


Examples

The following is sample output for the debug dot1x command: Router# debug dot1x Router-871#debug dot1x all *Nov 7 13:07:56.872: dot1x-ev:dot1x_mgr_pre_process_eapol_pak: Role determination not required on FastEthernet1.


DB-562

May 2008

Debug Commands debug dot1x

*Nov 7 13:07:56.876: dot1x-packet:dot1x_mgr_process_eapol_pak: queuing an EAPOL pkt on Authenticator Q *Nov 7 13:07:56.876: dot1x-ev:Enqueued the eapol packet to the global authenticator queue *Nov 7 13:07:56.876: dot1x-packet:Received an EAPOL frame on interface FastEthernet1 *Nov 7 13:07:56.876: dot1x-ev:Received pkt saddr =000f.23c4.a401 , daddr = 0180.c200.0003, pae-ether-type = 888e.0202.0000 *Nov 7 13:07:56.876: dot1x-packet:Received an EAPOL-Logoff packet on interface FastEthernet1 *Nov 7 13:07:56.876: EAPOL pak dump rx *Nov 7 13:07:56.876: EAPOL Version: 0x2 type: 0x2 length: 0x0000 *Nov 7 13:07:56.876: dot1x-sm:Posting EAPOL_LOGOFF on Client=82AC85CC *Nov 7 13:07:56.876: dot1x_auth Fa1: during state auth_authenticating, got event 7(eapolLogoff)

The fields in the output are self-explanatory.

Related Commands

Command

Description

clear dot1x

Clears 802.1X interface information.

identity profile default

Creates an identity profile and enters identity profile configuration mode.

show dot1x

Displays details for an identity profile.


DB-563

Debug Commands debug drip event

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


Defaults

Debugging is disabled for DRiP events.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(4)T


12.2(33)SRA


12.2SX


Usage Guidelines

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

Examples

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

DRiP gets a packet from the network: 612B92C0: 612B92D0: 612B92E0: 612B92F0: 612B9300:

01000C00 0300000C 00000C50 01010114 19000001

00000000 00020000 19000020 00000002 04C00064

0C501900 00000100 AAAA0300 00000002 04

0000AAAA 0CCCCCCC 000C0102 00000C50

.........P....** .............LLL ...P... **...... ...............P [email protected].

DRiP gets a packet from the network: Recvd. pak

DRiP recognizes that the VLAN ID it is getting is a new one from the network: 6116C840: 0100 0CCCCCCC 6116C850: 00102F72 CBFB0024 AAAA0300 000C0102 6116C860: 01FF0214 0002E254 00015003 00102F72

...LLL ../rK{.$**...... ......bT..P.../r


DB-564

May 2008

Debug Commands debug drip event

6116C870: C8000010 04C00014 044003EB 14 H....@[email protected]. DRIP : remote update - Never heard of this vlan

DRiP attempts to resolve any conflicts when it discovers a new VLAN. The value action = 1 means to notify the local platform of change in state. DRIP : resolve remote for vlan 20 in VLAN0 DRIP : resolve remote - action = 1

The local platform is notified of change in state: DRIP Change notification active vlan 20

Another new VLAN ID was received in the packet: DRIP : resolve remote for vlan 1003 in Vlan0

No action is required: DRIP : resolve remote - action = 0

Thirty seconds have expired, and DRiP sends its local database entries to all its trunk ports: DRIP : local timer DRIP : transmit on 612B92C0: 01000C00 612B92D0: 0300000C 612B92E0: 00000C50 612B92F0: 01FF0114 612B9300: 19000001

expired 0000.0c50.1900, length = 24 00000000 0C501900 0000AAAA 00020000 00000100 0CCCCCCC 19000020 AAAA0300 000C0102 00000003 00000002 00000C50 04C00064 04

.........P....** .............LLL ...P... **...... ...............P [email protected].


DB-565

Debug Commands debug drip packet

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


Defaults

Debugging is not enabled for DRiP packets.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(4)T


12.2(33)SRA


12.2SX


Usage Guidelines

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

Examples

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

The following type of output is displayed when a packet is entering the router and you use the show debug command: 039E5FC0: 0100 0CCCCCCC 00E0A39B 039E5FD0: AAAA0300 000C0102 01FF0314 039E5FE0: 00008805 00E0A39B 3C000000 039E5FF0: 04C00032 044003EB 0F 039FBD20: 01000C00

3FFB0028 0000A5F6 04C00028 00000010

...LLL.`#.?{.( **............%v .....`#. PendConOut HOST3745: input=ReqOpn.Cnf, PendConOut -> Xid HOST3745: input=Connect.Ind, Xid -> ConnIn HOST3745: input=Connected.Ind, ConnIn -> Connected HOST3745: input=Actpu, Reset -> Active HOST3745-2: input=uActlu, Reset -> upLuActive HOST3745-3: input=uActlu, Reset -> upLuActive

LU HOST3745-253: input=uActlu, Reset -> upLuActive LU HOST3745-254: input=uActlu, Reset -> upLuActive HOST3745: input=PuStopped, Connected -> PendDisc HOST3745: input=Disc.Cnf, PendDisc -> PendClose HOST3745: input=Close.Cnf, PendClose -> Reset HOST3745: input=T2ResetPu, Active -> Reset HOST3745-2: input=uStopLu, upLuActive -> Reset HOST3745-3: input=uStopLu, upLuActive -> Reset

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


DB-580

May 2008

Debug Commands debug dspu state


Related Commands

debug dspu state Field Descriptions

Field

Description

DSPU

Downstream PU debug message.

LS

Link station (LS) event triggered the message.

PU

PU event triggered the message.

LU

LU event triggered the message.

HOST3745-253

Host name or PU name and LU address.

input=input,

Input received by the FSM.

previous-state, -> current-state

Previous state and current new state as seen by the FSM.

Command

Description

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.


DB-581

Debug Commands debug dspu trace

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

name

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:

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

Router# debug dspu trace DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU: DSPU:

LS LS LS LS LU LS LS LU LS LS LU LS LS LU LS LS LU LS

HOST3745 input = 0 ->(1,a1) HOST3745 input = 5 ->(5,a6) HOST3745 input = 7 ->(5,a9) HOST3745 input = 9 ->(5,a28) HOST3745-2 in:0 s:0->(2,a1) HOST3745 input = 19 ->(8,a20) HOST3745 input = 18 ->(8,a17) HOST3745-3 in:0 s:0->(2,a1) HOST3745 input = 19 ->(8,a20) HOST3745 input = 18 ->(8,a17) HOST3745-252 in:0 s:0->(2,a1) HOST3745 input = 19 ->(8,a20) HOST3745 input = 18 ->(8,a17) HOST3745-253 in:0 s:0->(2,a1) HOST3745 input = 19 ->(8,a20) HOST3745 input = 18 ->(8,a17) HOST3745-254 in:0 s:0->(2,a1) HOST3745 input = 19 ->(8,a20)


DB-582

May 2008

Debug Commands debug dspu trace

Table 80 describes significant fields shown in the output. Table 80

debug dspu trace Field Descriptions

Field

Description

7:23:57

Time stamp.

DSPU

Downstream PU debug message.

LS

Link station (LS) event triggered the message.

PU

A PU event triggered the message.

LU

LU event triggered the message.

HOST3745-253

Host name or PU name and LU address.

in:input s:state ->(new-state, String describing the following: action) • input—LU FSM input

input=input -> (new-state,action)

Related Commands

•

state—Current FSM state

•

new-state—New FSM state

•

action—FSM action

String describing the following: •

input—PU or LS FSM input

•

new-state—New PU or LS FSM state

•

action—PU or LS FSM action

Command

Description

debug drip event

Displays debugging messages for DRiP packets.

debug drip packet

Displays information on DSPU packet.

debug dspu state

Displays information on DSPU FSM state changes.


DB-583

Debug Commands debug dss ipx event

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


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug dss ipx event command: Router# debug dss ipx event DSS IPX events debugging is on Router# configure terminal Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)# interface vlan 22 Router(config-if)# ipx access-group 800 out 05:51:36:DSS-feature:dss_ipxcache_version():idb:NULL, reason:42, prefix:0, mask:FFFFFFFF 05:51:36:DSS-feature:dss_ipx_access_group():idb:Vlan22 05:51:36:DSS-feature:dss_ipx_access_list() 05:51:36:DSS-base 05:51:33.834 dss_ipx_invalidate_interface Vl22 05:51:36:DSS-base 05:51:33.834 dss_set_ipx_flowmask_reg 2 05:51:36:%IPX mls flowmask transition from 1 to 2 due to new status of simple IPX access list on interfaces


DB-584

May 2008

Debug Commands debug dss ipx event

Related Commands

Command

Description

debug mls rp

Displays various MLS debugging elements.


DB-585

Debug Commands debug eap

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 | method] [authenticator | peer ] {all | errors | events | packets | sm} no debug eap [all | method] [authenticator | peer ] {all | errors | events | packets | sm}

Syntax Description

all | method

(Optional) Specifies the method to which the debug command refers. •

The all keyword turns on debugging for all EAP methods, including the EAP framework.

•

The method argument turns on debugging for specific methods.

•

This keyword or argument is dynamically linked into the parse chain and is present only if the method itself is present.

•

If this keyword or argument is omitted, the debug command is applied to the EAP framework.

authenticator

(Optional) Limits the scope of the output to only authenticator contexts.

peer

(Optional) Limits the scope of the output to only peer contexts.

all

Debugging is turned on for all debug types.

errors

Displays information about EAP packet errors.

events

Displays information about EAP events.

packets

Turns on packet debugging for the specified method or methods.

sm

Turns on state machine debugging for the specified method or methods.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


Examples

12.4(6)T

The method argument and authenticator and peer keywords were added.

12.2(33)SRA


12.2SX


The following sample output from the debug eap all command shows all EAP information: Router# debug eap all *Nov *Nov *Nov

7 13:05:58.512: EAP-EVENT: Received get canned status from lower layer (0x00000000) 7 13:05:59.460: EAP-EVENT: Received context create from lower layer (0x00000009) 7 13:05:59.460: eap_authen : initial state eap_auth_initialize has enter


DB-586

May 2008

Debug Commands debug eap

*Nov 7 13:05:59.460: EAP-EVENT: Started 'Authenticator Start' timer (1s) for EAP sesion handle 0xD6000008 *Nov 7 13:05:59.460: EAP-EVENT: Allocated new EAP context (handle = 0xD6000008) *Nov 7 13:05:59.464: EAP-EVENT: Started EAP tick timer *Nov 7 13:06:00.488: EAP-EVENT: 'Authenticator Start' timer expired for EAP sesion handle 0xD6000008 *Nov 7 13:06:00.488: eap_authen : during state eap_auth_initialize, got event 21(eapStartTmo) *Nov 7 13:06:00.488: @@@ eap_authen : eap_auth_initialize -> eap_auth_select_action *Nov 7 13:06:00.488: eap_authen : during state eap_auth_select_action, got event 17(eapDecisionPropose) *Nov 7 13:06:00.488: @@@ eap_authen : eap_auth_select_action -> eap_auth_propose_method

Related Commands

Command

Description

debug eou

Displays information about EAPoUDP.


DB-587

Debug Commands debug eigrp fsm

debug eigrp fsm To display debugging information about Enhanced Interior Gateway Routing Protocol (EIGRP) feasible successor metrics (FSMs), 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


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)T


12.4(6)T

Support for IPv6 was added.

12.2(33)SRB


12.2(37)SE

This command was integrated into Cisco IOS Release 12.2(37)SE.

12.2SX


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 fsm DUAL: dual_rcvupdate(): 172.25.166.0 255.255.255.0 via 0.0.0.0 metric 750080/0 DUAL: Find FS for dest 172.25.166.0 255.255.255.0. FD is 4294967295, RD is 42949 67295 found DUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0 DUAL: dual_rcvupdate(): 192.168.4.0 255.255.255.0 via 0.0.0.0 metric 4294967295/ 4294967295 DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216 DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295 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.0 DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0

In 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


DB-588

May 2008

Debug Commands debug eigrp fsm

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 2249216 DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295

The 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.0

The 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.0 DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0


DB-589

Debug Commands debug eigrp neighbor

debug 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

siatimer

(Optional) Stuck-in-active (SIA) timer messages.

static

(Optional) Static routes.

Command Default

Debugging for EIGRP neighbors is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)T


12.4(6)T


12.2(33)SRB


12.2(37)SE


12.2SX


Examples

The following is sample output from the debug eigrp neighbor command: Router# debug eigrp neighbor static EIGRP Static Neighbors debugging is on Router# configure terminal Router(config)# router eigrp 100 Router(config-router)# neighbor 10.1.1.1 e3/1 Router(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/1 Router(config-router)# no neighbor 10.1.1.1 e3/1


DB-590

May 2008

Debug Commands debug eigrp neighbor

Router(config-router)# 22:41:23:EIGRP:Static nbr 10.1.1.1 not in AS 100 Ethernet3/1 dynamic list 22:41:23:EIGRP:Delete static nbr 10.1.1.1 from AS 100 Ethernet3/1 22:41:23:EIGRP:Multicast Hello is enabled on Ethernet3/1!

Related Commands

Command

Description

neighbor

Defines a neighboring router with which to exchange routing information.

show ip eigrp neighbors

Displays EIGRP neighbors.

show ipv6 eigrp neighbors

Displays IPv6 EIGRP neighbors.


DB-591

Debug Commands debug eigrp nsf

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


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(15)T


12.2(28)SB


12.2(33)SRA


12.2SX


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 Enhanced Interior Gateway Routing Protocol (EIGRP) NSF debugging: Router# debug eigrp nsf

Related Commands

Command

Description

timers nsf route-hold

Sets the route-hold timer for NSF-aware routers that run EIGRP.


DB-592

May 2008

Debug Commands debug eigrp notifications

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.

Defaults

Debugging of EIGRP notifications for the L2L3 API interface is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(15)XF


12.4(15)T


12.2SX


Usage Guidelines

Caution

Examples

Consult Cisco technical support before using this command.

Use of debug commands can have severe performance penalties and should be used with extreme caution. For this reason, Cisco recommends that you contact Cisco technical support before enabling a debug command.

The following example displays information about the L2L3 API Interface: Router# debug eigrp notifications rib

Related Commands

Command

Description

eigrp interface

Sets a threshold value to minimize hysteresis in a router-to-radio configuration.

interface vmi

Creates a virtual multipoint interface (VMI) that can be configured and applied dynamically.


DB-593

Debug Commands debug eigrp packet

debug eigrp packet To display debugging information for Enhanced Interior Gateway Routing Protocol (EIGRP) for IPv6 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

SIAquery

(Optional) Displays information about Stuck-in-Active (SIA) query messages.

SIAreply

(Optional) Displays information about SIA reply messages.

ack

(Optional) Displays information about EIGRP acknowledgment packets.

hello

(Optional) Displays information about EIGRP hello packets.

ipxsap

(Optional) Displays information about IPX EIGRP SAP packets.

probe

(Optional) Displays information about EIGRP probe packets.

query

(Optional) Displays information about EIGRP query packets.

reply

(Optional) Displays information about EIGRP reply packets.

request

(Optional) Displays information about EIGRP request packets.

retry

(Optional) Displays information about EIGRP retry packets.

stub

(Optional) Displays information about EIGRP stub packets.

terse

(Optional) Displays information about all EIGRP packets except Hello packets.

update

(Optional) Displays information about EIGRP update packets.

verbose

(Optional) Displays information about all EIGRP packets.

Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

Modification

12.0(7)T


12.4

The keywords were supported.

12.4(6)T


12.2(33)SRB


12.2(37)SE


12.2SX


If a communication session is closing when it should not be, an end-to-end connection problem can be the cause. The debug eigrp packet command is useful for analyzing the messages traveling between the local and remote hosts.


DB-594

May 2008

Debug Commands debug eigrp packet

Note

Examples

Although this command accepts a number of keywords, we don’t recommend their use unless directed by TAC.

The following is sample output from the debug eigrp packet command: Router# debug eigrp packet EIGRP: Sending HELLO on Ethernet0/1 AS 109, Flags 0x0, Seq 0, Ack 0 EIGRP: Sending HELLO on Ethernet0/1 AS 109, Flags 0x0, Seq 0, Ack 0 EIGRP: Sending HELLO on Ethernet0/1 AS 109, Flags 0x0, Seq 0, Ack 0 EIGRP: Received UPDATE on Ethernet0/1 from AS 109, Flags 0x1, Seq 1, Ack 0 EIGRP: Sending HELLO/ACK on Ethernet0/1 to AS 109, Flags 0x0, Seq 0, Ack 1 EIGRP: Sending HELLO/ACK on Ethernet0/1 to AS 109, Flags 0x0, Seq 0, Ack 1 EIGRP: Received UPDATE on Ethernet0/1 from AS 109, Flags 0x0, Seq 2, Ack 0

192.195.78.24, 192.195.78.24, 192.195.78.24, 192.195.78.24,

The output shows transmission and receipt of 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 81 describes the significant fields shown in the display. Table 81

debug eigrp packet Field Descriptions

Field

Description

EIGRP:

EIGRP packet information.

AS n

Autonomous system number.

Flags 0x0

A flag of 1 means the sending router is indicating to the receiving router that this is the first packet it has sent to the receiver. A flag of 2 is a multicast that should be conditionally received by routers that have the conditionally receive (CR) bit set. This bit gets set when the sender of the multicast has previously sent a sequence packet explicitly telling it to set the CR bit.

HELLO

Hello packets are the neighbor discovery packets. They are used to determine whether neighbors are still alive. As long as neighbors receive the hello packets the router is sending, the neighbors validate the router and any routing information sent. If neighbors lose the hello packets, the receiving neighbors invalidate any routing information previously sent. Neighbors also send hello packets.


DB-595

Debug Commands debug eigrp transmit

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

ack

(Optional) Information for acknowledgment (ACK) messages sent by the system.

build

(Optional) Build information messages (messages that indicate that a topology table was either successfully built or could not be built).

detail

(Optional) Additional detail for debug output.

link

(Optional) Information regarding topology table linked-list management.

packetize

(Optional) Information regarding topology table linked-list management.

peerdown

(Optional) Information regarding the impact on packet generation when a peer is down.

sia

(Optional) Stuck-in-active (SIA) messages.

startup

(Optional) Information regarding peer startup and initialization packets that have been transmitted.

strange

(Optional) Unusual events relating to packet processing.

Command Default

Debugging for EIGRP transmittal messages is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1


12.4(6)T


12.2(33)SRB


12.2(37)SE


12.2SX



DB-596

May 2008

Debug Commands debug eigrp transmit

Examples

The following is sample output from the debug eigrp transmit command: Router# debug eigrp transmit EIGRP Transmission Events debugging is on (ACK, PACKETIZE, STARTUP, PEERDOWN, LINK, BUILD, STRANGE, SIA, DETAIL) Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router#(config)# router eigrp 100 Router#(config-router)# network 10.4.9.0 0.0.0.255 Router#(config-router)# 5d22h: DNDB UPDATE 10.0.0.0/8, serno 0 to 1, refcount 0 Router#(config-router)#


DB-597

Debug Commands debug eou

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

all

Displays all EAPoUDP information.

eap

Displays EAPoUDP packets.

errors

Displays information about EAPoUDP packet errors.

events

Displays information about EAPoUDP events.

packets

Displays EAPoUDP packet-related information.

ratelimit

Displays EAPoUDP posture-validation information.

sm

Displays EAPoUDP state machine transitions.

Defaults

If you do not enter any keywords, debugging is turned on for all EAPoUDP messages.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRA


12.2SX


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.15 eou_port= 5566 (hex) *Apr ID=0 *Apr *Apr *Apr

9 19:30:40.790: EAPoUDP (tx) Flags:0 Ver=1 opcode=2 Len=8 MsgId=3839857370 Assoc 9 19:30:40.790: Dumping TLV contents 9 19:30:40.790: TLV M:1 R:0 Type=ASSOCIATION ID Length=4 Association=-1994800267 9 19:30:40.999: EAPoUDP (rx) Flags:128 Ver=1 opcode=2 Len=24 MsgId=3839857370 Assoc


DB-598

May 2008

Debug Commands debug eou

ID=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=12 07167CE0: 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: *Apr 9 19:31:50.048: *Apr 9 19:31:50.048: 14(eouEapSuccess) *Apr 9 19:31:50.048: *Apr 9 19:31:50.052:

Related Commands

@@@ eou_auth 10.0.0.1: eou_eap -> eou_eap eou-ev:10.0.0.1: msg = 24(eventEouEapSuccess) eou_auth 10.0.0.1: during state eou_eap, got event @@@ eou_auth 10.0.0.1: eou_eap -> eou_result eou-ev:Starting RESULT timer 3(10.0.0.1)

Command

Description

debug eap

Displays information about EAP messages.

debug ip admission eapoudp

Displays information about EAPoUDP network admission control events.


DB-599

Debug Commands debug ephone alarm

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


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XT

This command was introduced on the following platforms: Cisco 1750, Cisco 1751, Cisco 2600 series and Cisco 3600 series multiservice routers; and Cisco IAD2420 series Integrated Access Devices (IADs).

12.2(8)T

This command was implemented on the Cisco 3725 and Cisco 3745 routers.

12.2(8)T1

This command was implemented on the Cisco 2600-XM and Cisco 2691 routers.

12.2(11)T

This command was implemented on the Cisco 1760 routers.

12.2SX


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.


DB-600

May 2008

Debug Commands debug ephone alarm

Examples

The following example shows a SkinnyStation alarm message that is sent before the Cisco IP phone registers: Router# debug ephone alarm phone keypad reset CM-closed-TCP CM-bad-state

Related Commands

Command

Description

debug ephone detail

Sets detail debugging for the Cisco IP phone.

debug ephone error

Sets error debugging for the Cisco IP phone.

debug ephone keepalive

Sets keepalive debugging for the Cisco IP phone.

debug ephone loopback

Sets MWI debugging for the Cisco IP phone.

debug ephone pak

Provides voice packet level debugging and prints the contents of one voice packet in every 1024 voice packets.

debug ephone raw

Provides raw low-level protocol debugging display for all SCCP messages.

debug ephone register

Sets registration debugging for the Cisco IP phone.

debug ephone state

Sets state debugging for the Cisco IP phone.

debug ephone statistics

Sets statistics debugging for the Cisco IP phone.

show debugging



DB-601

Debug Commands debug ephone blf

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

mac-address mac-address

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(11)XJ


12.4(15)T


12.2SX


(Optional) Specifies the MAC address of a specific IP phone.

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 blf EPHONE BLF debugging is enabled *Sep *Sep *Sep [16] *Sep *Sep *Sep *Sep *Sep [23] *Sep *Sep *Sep *Sep *Sep [16] *Sep *Sep *Sep *Sep

4 07:18:26.307: skinny_asnl_callback: subID 16 type 4 4 07:18:26.307: ASNL_RESP_NOTIFY_INDICATION 4 07:18:26.307: ephone-1[1]:ASNL notify indication message, feature index 4, subID 4 4 4 4 4

07:18:26.307: 07:18:26.307: 07:18:26.307: 07:18:26.307: 07:18:26.307:

ephone-1[1]:line status 6, subID [16] ephone-1[1]:StationFeatureStatV2Message sent, status 2 skinny_asnl_callback: subID 23 type 4 ASNL_RESP_NOTIFY_INDICATION ephone-2[2]:ASNL notify indication message, feature index 2, subID

4 4 4 4 4

07:18:26.311: 07:18:26.311: 07:18:28.951: 07:18:28.951: 07:18:28.951:

ephone-2[2]:line status 6, subID [23] ephone-2[2]:StationFeatureStatV2Message sent, status 2 skinny_asnl_callback: subID 16 type 4 ASNL_RESP_NOTIFY_INDICATION ephone-1[1]:ASNL notify indication message, feature index 4, subID

4 4 4 4

07:18:28.951: 07:18:28.951: 07:18:28.951: 07:18:28.951:

ephone-1[1]:line status 1, subID [16] ephone-1[1]:StationFeatureStatV2Message sent, status 1 skinny_asnl_callback: subID 23 type 4 ASNL_RESP_NOTIFY_INDICATION


DB-602

May 2008

Debug Commands debug ephone blf

*Sep [23] *Sep *Sep

Related Commands

4 07:18:28.951: ephone-2[2]:ASNL notify indication message, feature index 2, subID 4 07:18:28.951: ephone-2[2]:line status 1, subID [23] 4 07:18:28.951: ephone-2[2]:StationFeatureStatV2Message sent, status 1

Command

Description

blf-speed-dial

Enables BLF monitoring for a speed-dial number on a phone registered to Cisco Unified CME.

presence call-list

Enables BLF monitoring for call lists and directories on phones registered to a Cisco Unified CME router.

show presence global

Displays configuration information about the presence service.

show presence subscription

Displays information about active presence subscriptions.


DB-603

Debug Commands debug ephone ccm-compatible

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

Release

Modification

12.3(7)T


12.2SX


Usage Guidelines

(Optional) Specifies the MAC address of a Cisco IP phone for debugging.

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_dow n:.


DB-604

May 2008

Debug Commands debug ephone ccm-compatible

*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 1 DN 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]:UUT4PH3

Related Commands

Command

Description

debug ephone state

Displays call state information.

show debugging


show ephone

Displays information about registered Cisco IP phones.


DB-605

Debug Commands debug ephone detail

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


mac-address


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YD

This command was introduced on the following platforms: Cisco 2600 series and Cisco 3600 series multiservice routers, and Cisco IAD2420 series Integrated Access Devices (IADs).

12.2(2)XT

This command was implemented on the Cisco 1750 and Cisco 1751 multiservice routers.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 3725 and Cisco 3745 routers.

12.2(8)T1


12.2(11)T


12.2SX


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.


DB-606

May 2008


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.8724 Ephone detail debugging is enabled 1d04h: 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: 5002 1d04h: 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 ON 1d04h: SetCallInfo calling dn 1 dn 1 calling [5001] called [5002] . . 1d04h: ephone-1[1]: Jane calling 1d04h: ephone-1[1]: Jill . . 1d04h: SkinnyUpdateDnState by EFXS_RING_GENERATE for DN 2 to state RINGING . . 1d04h: SkinnyGetCallState for DN 2 CONNECTED .


DB-607


. 1d04h: 1d04h: . . 1d04h: . . 1d04h: . . 1d04h: 1d04h: 1d04h: . . 1d04h: . . 1d04h: . . 1d04h: . . 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: 1d04h: .

Related Commands.

ephone-1[1]:SetLineLamp 3 to ON ephone-1[1]:UpdateCallState DN 1 state 4 calleddn 2

Skinny Call State change for DN 1 CONNECTED

ephone-1[1]:OpenReceive DN 1 codec 4:G711Ulaw64k

duration 10 ms bytes 80

ephone-1[1]:OpenReceiveChannelAck 1.2.172.21 port=20180 ephone-1[1]:Outgoing calling DN 1 Far-ephone-2 called DN 2 SkinnyGetCallState for DN 1 CONNECTED

ephone-1[1]:SetCallState line 3 DN 2 TsOnHook

ephone-1[1]:SetLineLamp 3 to OFF

ephone-1[1]:SetCallState line 1 DN 1 TsOnHook

ephone-1[1]:Clean Up Speakerphone state ephone-1[1]:SpeakerPhoneOnHook ephone-1[1]:Clean up activeline 1 ephone-1[1]:StopTone sent to ephone ephone-1[1]:Clean Up phone offhook state SkinnyGetCallState for DN 1 IDLE called DN -1, calling DN -1 phone -1 ephone-1[1]:SetLineLamp 1 to OFF UnBinding ephone-1 from DN 1 UnBinding called DN 2 from DN 1 ephone-1[1]:ONHOOK ephone-1[1]:SpeakerPhoneOnHook ephone-1[1]:ONHOOK NO activeline

Command

Description

debug ephone alarm

Sets SkinnyStation alarm messages debugging for the Cisco IP phone.

debug ephone error






debug ephone pak


debug ephone raw




debug ephone state




show debugging



DB-608

May 2008

Debug Commands debug ephone extension-assigner

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


Command Default

Debug ephone extension-assigner is disabled.

Command Modes

Privileged EXEC

Command History

Cisco IOS Release

Cisco Product

Modification

12.4(4)XC4

Cisco Unified CME 4.0(3)


12.4(11)XJ

Cisco Unified CME 4.1


12.4(15)T

Cisco Unified CME 4.1


12.2SX

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

phone query—Verifies whether the ephone tag has been assigned a MAC address.

•

phone assign—Binds the MAC address from the caller’s phone to a preexisting ephone template.

•

phone unassign—Removes the MAC address from the ephone tag.

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


DB-609

Debug Commands debug ephone extension-assigner

*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

Command

Description

debug ephone state

Sets state debugging for Cisco IP phones.

debug voip application Displays status messages produced by voice over IP application scripts. script


DB-610

May 2008

Debug Commands debug ephone error

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


mac-address


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YD


12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


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.


DB-611

Debug Commands debug ephone error

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.8724 EPHONE error debugging is enabled socket [2] send ERROR 11 Skinny Socket [2] retry failure

Related Commands

Command

Description

debug ephone alarm


debug ephone detail






debug ephone pak


debug ephone raw




debug ephone state




show debugging



DB-612

May 2008

Debug Commands debug ephone keepalive

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


mac-address


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YD


12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


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.


DB-613

Debug Commands debug ephone keepalive

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.E1A8 EPHONE keepalive debugging is enabled for phone 0030.94C3.E1A8 1d05h: 1d05h: 1d05h: 1d05h: 1d05h: 1d05h: 1d05h: 1d05h: 1d05h: 1d05h:

Related Commands

ephone-1 Set interface FastEthernet0/0 ETHERNET ephone-1[1]:Keepalive socket[1] SEP003094C3E1A8 ephone-1 Set interface FastEthernet0/0 ETHERNET ephone-1[1]:Keepalive socket[1] SEP003094C3E1A8 Skinny Checking for stale sockets ephone-1 Set interface FastEthernet0/0 ETHERNET ephone-1[1]:Keepalive socket[1] SEP003094C3E1A8 ephone-1 Set interface FastEthernet0/0 ETHERNET ephone-1[1]:Keepalive socket[1] SEP003094C3E1A8 Skinny active socket list (3/96): 1 2 4

Command

Description

debug ephone alarm


debug ephone detail


debug ephone error




debug ephone pak


debug ephone raw




debug ephone state




show debugging



DB-614

May 2008

Debug Commands debug ephone loopback

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

Release

Modification

12.2(2)XT

This command was introduced for Cisco IOS Telephony Services (now known as Cisco CallManager Express) Version 2.0 on the Cisco 1750, Cisco 1751, Cisco 2600 series, Cisco 3600 series, and Cisco IAD2420 series.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 3725 and Cisco 3745.

Usage Guidelines


12.2(8)T1

This command was implemented on the Cisco 2600-XM and Cisco 2691.

12.3(4)T


12.2SX


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


DB-615


. . . ephone-dn 14 number 1514 ! ! ephone-dn 42 number 17181.. loopback-dn 43 forward 4 no huntstop ! ! ephone-dn 43 number 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 loopback Mar 7 00:57:25.376:Pass processed call info to special DN 43 chan 1 Mar 7 00:57:25.376:SkinnySetCallInfoLoopback DN 43 state IDLE to DN 42 state IDLE Mar 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 42 Mar 7 00:57:25.376:DN 43 Forward 1514 Mar 7 00:57:25.376:PredictTarget match 1514 DN 14 is idle Mar 7 00:57:25.380:SkinnyUpdateLoopbackState DN 43 state RINGING calledDn -1 Mar 7 00:57:25.380:Loopback DN 42 state IDLE Mar 7 00:57:25.380:Loopback DN 43 calledDN -1 callingDn -1 G711Ulaw64k Mar 7 00:57:25.380:SkinnyUpdateLoopbackState DN 43 to DN 42 signal OFFHOOK Mar 7 00:57:25.380:SetDnCodec Loopback DN 43 codec 4:G711Ulaw64k vad 0 size 160 Mar 7 00:57:25.380:SkinnyDnToneLoopback DN 42 state SIEZE to DN 43 state RINGING Mar 7 00:57:25.380:TONE ON DtInsideDialTone Mar 7 00:57:25.380:SkinnyDnToneLoopback called number = 1911514 Mar 7 00:57:25.380:DN 43 Forward 1514 Mar 7 00:57:25.380:DN 42 from 43 Dial 1514 Mar 7 00:57:25.384:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGING Mar 7 00:57:25.384:TONE OFF Mar 7 00:57:25.384:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGING Mar 7 00:57:25.384:TONE OFF Mar 7 00:57:25.384:SkinnyUpdateLoopbackState DN 42 state ALERTING calledDn -1 Mar 7 00:57:25.384:Loopback DN 43 state RINGING Mar 7 00:57:25.384:Loopback Alerting DN 42 calledDN -1 callingDn -1 G711Ulaw64k Mar 7 00:57:25.388:ephone-5[7]:DisplayCallInfo incoming call Mar 7 00:57:25.388:SkinnyDnToneLoopback DN 42 state ALERTING to DN 43 state RINGING Mar 7 00:57:25.388:TONE ON DtAlertingTone Mar 7 00:57:25.388:SkinnyDnToneLoopback DN 42 to DN 43 deferred alerting by DtAlertingTone Mar 7 00:57:25.388:EFXS_STATE_ONHOOK_RINGING already done for DN 43 chan 1 Mar 7 00:57:25.388:Set prog_ind 0 for DN 42 chan 1 . .


DB-616

May 2008


.

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 RINGING Mar 7 00:57:32.158:TONE OFF Mar 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 160 Mar 7 00:57:32.158:SkinnyUpdateLoopbackState DN 42 state CALL_START calledDn 14 Mar 7 00:57:32.158:Loopback DN 43 state RINGING Mar 7 00:57:32.158:SkinnyUpdateLoopbackState DN 42 to DN 43 deferred alerting by CALL_START already sent Mar 7 00:57:32.158:SetDnCodec reassert defer_start for DN 14 chan 1 Mar 7 00:57:32.158:Delay media until loopback DN 43 is ready Mar 7 00:57:32.158:SkinnyUpdateLoopbackCodec check for DN 14 chan 1 from DN 42 loopback DN 43 Mar 7 00:57:32.158:SkinnyUpdateLoopbackCodec DN chain is 14 1, other=42, lb=43, far=-1 1, final=43 1 Mar 7 00:57:32.158:SkinnyUpdateLoopbackCodec DN 14 chan 1 DN 43 chan 1 codec 4 match Mar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 42 state CONNECTED calledDn 14 Mar 7 00:57:32.162:Loopback DN 43 state RINGING Mar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 42 to DN 43 signal ANSWER Mar 7 00:57:32.162:Loopback DN 42 calledDN 14 callingDn -1 G711Ulaw64k Mar 7 00:57:32.162:Loopback DN 43 calledDN -1 callingDn -1 incoming G711Ulaw64k Mar 7 00:57:32.162:ephone-5[7][SEP000DBDBEF37D]:refreshDisplayLine for line 1 DN 14 chan 1 Mar 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 160 Mar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 state CALL_START calledDn -1 Mar 7 00:57:32.162:Loopback DN 42 state CONNECTED Mar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 has defer_dn 14 chan 1 set Mar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 has defer_dn 14 chan 1: -invoke SkinnyOpenReceive Mar 7 00:57:32.162:SkinnyUpdateLoopbackCodec check for DN 14 chan 1 from DN 42 loopback DN 43 Mar 7 00:57:32.162:SkinnyUpdateLoopbackCodec DN chain is 14 1, other=42, lb=43, far=-1 1, final=43 1 Mar 7 00:57:32.162:SkinnyUpdateLoopbackCodec DN 14 chan 1 DN 43 chan 1 codec 4 match Mar 7 00:57:32.162:SkinnyUpdateLoopbackState DN 43 state CALL_START calledDn -1 Mar 7 00:57:32.162:Loopback DN 42 state CONNECTED Mar 7 00:57:32.454:SkinnyGetDnAddrInfo DN 43 LOOPBACK update media address to 10.0.0.6 25390 from DN 14 Mar 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 Mar Mar Mar Mar Mar Mar Mar

7 7 7 7 7 7 7 7

00:57:39.224:Loopback DN 42 disc reason 16 normal state CONNECTED 00:57:39.224:SkinnyUpdateLoopbackState DN 42 state CALL_END calledDn -1 00:57:39.224:Loopback DN 43 state CONNECTED 00:57:39.224:SkinnyUpdateLoopbackState DN 42 to DN 43 signal ONHOOK 00:57:39.236:SkinnyDnToneLoopback DN 42 state IDLE to DN 43 state IDLE 00:57:39.236:TONE OFF 00:57:39.236:SkinnyDnToneLoopback DN 43 state IDLE to DN 42 state IDLE 00:57:39.236:TONE OFF



DB-617


Table 82

debug ephone loopback Field Descriptions

Field

Description

Called Number

Original called number as presented to the incoming side of the loopback-dn.

Forward

Outgoing number that is expected to be dialed by the outgoing side of the loopback-dn pair.

PredictTarget Match

Extension (ephone-dn) that is anticipated by the loopback-dn to be the far-end termination for the call.

signal OFFHOOK

Indicates that the outgoing side of the loopback-dn pair is going off-hook prior to placing the outbound call leg.

Dial

Outbound side of the loopback-dn that is actually dialing the outbound call leg.

deferred alerting

Indicates that the alerting, or ringing, tone is returning to the original inbound call leg in response to the far-end ephone-dn state.

DN chain

Chain of ephone-dns that has been detected, starting from the far-end that terminates the call. Each entry in the chain indicates an ephone-dn tag and channel number. Entries appear in the following order, from left to right: •

Ephone-dn tag and channel of the far-end call terminator (in this example, ephone-dn 14 is extension 1514).

•

other—Ephone-dn tag of the outgoing side of the loopback.

•

lb—Ephone-dn tag of the incoming side of the loopback.

•

far—Ephone-dn tag and channel of the far-end call originator, or -1 for a nonlocal number.

•

final—Ephone-dn tag for the originator of the call on the incoming side of the loopback. If the originator is not a local ephone-dn, this is set to -1. This number represents the final ephone-dn tag in the chain, looking toward the originator.

codec match

Indicates that there is no codec conflict between the two calls on either side of the loopback-dn.

GetDnAddrInfo

IP address of the IP phone at the final destination extension (ephone-dn), after resolving the chain of ephone-dns involved.

disc_reason

Disconnect cause code, in decimal. These are normal CC_CAUSE code values that are also used in call control API debugging. Common cause codes include the following: •

16—Normal disconnect.

•

17—User busy.

•

19—No answer.

•

28—Invalid number.


DB-618

May 2008


Related Commands

Command

Description

debug ephone pak

Provides voice packet level debugging.

loopback-dn

Configures loopback-dn virtual loopback voice ports used to establish demarcation points for VoIP voice calls and supplementary services.

show ephone

Displays information about registered Cisco IP phones.

show ephone-dn loopback

Displays information for ephone-dns that have been set up for loopback calls.


DB-619

Debug Commands debug ephone message

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

Command Modes

Privileged EXEC

Command History

Cisco IOS Release

Modification

12.4(4)XC


12.4(9)T


12.2SX


Usage Guidelines

(Optional) Displays signaling connection control protocol (SCCP) messages sent and received between ephones in the Cisco Unified CallManager Express (Cisco Unified CME) system.

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 message EPHONE skinny message debugging is enabled *Jul 17 12:12:54.883: Received message from phone 7, SkinnyMessageID = StationKe epAliveMessageID *Jul 17 12:12:54.883: Sending message to phone 7, SkinnyMessageID = StationKe epAliveAckMessageID

The following command disables ephone message debugging: Router# no debug ephone message EPHONE skinny message debugging is disabled


DB-620

May 2008

Debug Commands debug ephone message

Related Commands

Command

Description

debug ephone alarm

Sets SkinnyStation alarm messages debugging for the ephone.

debug ephone detail

Sets detail debugging for the ephone.

debug ephone error

Sets error debugging for the ephone.

debug ephone mwi

Sets MWI debugging for the ephone.

debug ephone pak

Provides voice packet level debugging and displays the contents of one voice packet in every 1024 voice packets.

debug ephone raw



Sets registration debugging for the ephone.

debug ephone state

Sets state debugging for the ephone.


Sets statistics debugging for the ephone.

debug ephone video

Sets video debugging for the ephone.

show debugging


show ephone

Displays information about ephones.


DB-621

Debug Commands debug ephone moh

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

Release

Modification

12.2(2)XT

This command was introduced for Cisco IOS Telephony Services (now known as Cisco CallManager Express) Version 2.0 and Cisco Survivable Remote Site Telephony (SRST) Version 2.0 on the Cisco 1750, Cisco 1751, Cisco 2600 series, Cisco 3600 series, and Cisco IAD2420 series.

12.2(8)T

This command was integrated into Cisco IOS Release 12.2(8)T and implemented on the Cisco 3725 and Cisco 3745.

12.2(8)T1

This command was implemented on the Cisco 2600-XM and Cisco 2691.

12.3(4)T


12.2SX


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 moh Mar Mar Mar Mar Mar

7 7 7 7 7

00:52:33.817:MOH AU file 00:52:33.817:skinny_open_moh_play 00:52:33.825: 2E73 6E64 0000 0018 00:52:33.825: 0000 1F40 0000 0001 00:52:33.825: FFFF FFFF FFFF FFFF

set type to 3 0007 3CCA 0000 0001 FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF


DB-622

May 2008

Debug Commands debug ephone moh

Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar

7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7

00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 00:52:33.825: 00:52:33.825:AU file processing Found .snd 00:52:33.825:AU file data start at 24 end at 474338 00:52:33.825:AU file codec Media_Payload_G711Ulaw64k 00:52:33.825:MOH read file header type AU start 24 end 474338 00:52:33.825:MOH pre-read block 0 at write-offset 0 from 24 00:52:33.833:MOH pre-read block 1 at write-offset 8000 from 8024 00:52:33.845:Starting read server with play-offset 0 write-offset 16000


Related Commands

debug ephone moh Field Descriptions

Field

Description

type

0—invalid 1—raw file 2—wave format file (.wav) 3—AU format (.au) 4—live feed

AU file processing Found .snd

A .snd header was located in the AU file.

AU file data start at, end at

Data start and end file offset within the MOH file, as indicated by the file header.

read file header type

File format found (AU, WAVE, or RAW).

pre-read block, write-offset

Location in the internal MOH buffer to which data is being written, and location from which that data was read in the file.

play-offset, write-offset

Indicates the relative positioning of MOH file read-ahead buffering. Data is normally written from a Flash file into the internal circular buffer, ahead of the location from which data is being played or output.

Command

Description

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.


DB-623

Debug Commands debug ephone mwi

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


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


Usage Guidelines

Note

Examples

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.

Unlike the other related debug ephone commands, the mac-address keyword does not help debug a particular Cisco IP phone.

The following is sample output of the message waiting indication status for the Cisco IOS Telephony Service router: Router# debug ephone mwi


DB-624

May 2008

Debug Commands debug ephone mwi

Related Commands

Command

Description

debug ephone alarm


debug ephone detail


debug ephone error




debug ephone pak


debug ephone raw




debug ephone state




show debugging



DB-625

Debug Commands debug ephone pak

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


mac-address


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YD


12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


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.


DB-626

May 2008


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.8724 EPHONE packet debugging is enabled for phone 0030.94c3.8724 01:29:14: ***ph_xmit_ephone DN 3 tx_pkts 5770 dest=10.2.1.1 orig len=32 pakcopy=0 discards 27 ip_enctype 0 0 last discard: unsupported payload type 01:29:14: to_skinny_duration 130210 offset -30 last -40 seq 0 adj 0 01:29:14: IP: 45B8 003C 0866 0000 3F11 3F90 2800 0001 0A02 0101 01:29:14: TTL 63 TOS B8 prec 5 01:29:14: UDP: 07D0 6266 0028 0000 01:29:14: sport 2000 dport 25190 length 40 checksum 0 01:29:14: RTP: 8012 16AF 9170 6409 0E9F 0001 01:29:14: is_rtp:1 is_frf11:0 vlen:0 delta_t:160 vofr1:0 vofr2:0 scodec:11 rtp_bits:8012 rtp_codec:18 last_bad_payload 19 01:29:14: vencap FAILED 01:29:14: PROCESS SWITCH 01:29:15: %SYS-5-CONFIG_I: Configured from console by console 01:29:34: ***SkinnyPktIp DN 3 10.2.1.1 to 40.0.0.1 pkts 4880 FAST sw 01:29:34: from_skinny_duration 150910 01:29:34: nw 3BBC2A8 addr 3BBC2A4 mac 3BBC2A4 dg 3BBC2C4 dgs 2A 01:29:34: MAC: 1841 0800 01:29:34: IP: 45B8 0046 682E 0000 3E11 E0BD 0A02 0101 2800 0001 01:29:34: TTL 62 TOS B8 prec 5 01:29:34: UDP: 6266 07D0 0032 0000 01:29:34: sport 25190 dport 2000 length 50 checksum 0 01:29:34: RTP: 8012 55FF 0057 8870 3AF4 C394 01:29:34: RTP: rtp_bits 8012 seq 55FF ts 578870 ssrc 3AF4C394 01:29:34: PAYLOAD: 01:29:34: 1409 37C9 54DE 449C 3B42 0446 3AAB 182E 01:29:34: 56BC 5184 58E5 56D3 13BE 44A7 B8C4 01:29:34: 01:29:37: ***ph_xmit_ephone DN 3 tx_pkts 6790 dest=10.2.1.1 orig len=32 pakcopy=0 discards 31 ip_enctype 0 0 last discard: unsupported payload type 01:29:37: to_skinny_duration 153870 offset -150 last -40 seq 0 adj 0 01:29:37: IP: 45B8 003C 0875 0000 3F11 3F81 2800 0001 0A02 0101 01:29:37: TTL 63 TOS B8 prec 5 01:29:37: UDP: 07D0 6266 0028 0000 01:29:37: sport 2000 dport 25190 length 40 checksum 0 01:29:37: RTP: 8012 1AAF 9173 4769 0E9F 0001 01:29:37: is_rtp:1 is_frf11:0 vlen:0 delta_t:160 vofr1:0 vofr2:0

Related Commands

Command

Description

debug ephone alarm


debug ephone detail


debug ephone error






debug ephone raw




debug ephone state



DB-627


Command

Description



show debugging



DB-628

May 2008

Debug Commands debug ephone qov

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

Release

Modification

12.2(15)ZJ2

This command was introduced for Cisco CallManager Express 3.0 and Cisco Survivable Remote Site Telephony (SRST) Version 3.0.

12.3(4)T


12.2SX


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

Lost packets—A report is triggered when two adjacent QOV samples show an increase of four or more lost packets between samples. The report is triggered by an increase of lost packets in a short period of time, not by the total number of lost packets.

•

Jitter and latency—A report is triggered when either jitter or latency exceeds 100 milliseconds.

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.


DB-629

Debug Commands debug ephone qov

Examples

The following sample output describes QOV statistics for a call on ephone 5: Router# debug ephone qov Mar 7 00:54:57.329:ephone-5[7]:QOV DN 14 chan 1 (1514) ref 4 called=1514 calling=8101 Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:Lost 91 Jitter 0 Latency 0 Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:previous Lost 0 Jitter 0 Latency 0 Mar 7 00:54:57.329:ephone-5[7][SEP000DBDBEF37D]:Router sent 1153 pkts, current phone got 1141 received by all (shared) phones 0 Mar 7 00:54:57.329:ephone-5[7]:worst jitter 0 worst latency 0 Mar 7 00:54:57.329:ephone-5[7]:Current phone sent 1233 packets Mar

7 00:54:57.329:ephone-5[7]:Signal Level to phone 3408 (-15 dB) peak 3516 (-15 dB)


debug ephone qov Field Descriptions

Field

Description

Lost

Number of lost packets reported by the IP phone.

Jitter, Latency

The most recent jitter and latency parameters reported by the IP phone.

previous Lost, Jitter, Latency

Values from the previous QOV statistics report that were used as the comparison points against which the current statistics triggered generation of the current report.

Router sent pkts

Number of packets sent by the router to the IP phone. This number is the total for the entire call, even if the call is moved from one phone to another during a call, which can happen with shared lines.

current phone got

Number of packets received by the phone currently terminating the call. This number is the total for the entire call, even if the call is moved from one phone to another during a call, which can happen with shared lines.

worst jitter, worst latency

Highest value reported by the phone during the call.

Current phone sent packets

Number of packets that the current phone claims it sent during the call.

Signal Level to phone

Signal level seen in G.711 voice packet data prior to the sending of the most recent voice packet to the phone. The first number is the raw sample value, converted from G.711 to 16-bit linear format and left-justified. The number in parentheses is the value in decibels (dB), assuming that 32,767 is about +3 dB. Note

Related Commands

This value is meaningful only if the call uses a G.711 codec.

Command

Description

debug ephone alarm

Displays alarm messages for IP phones.


Displays call statistics for IP phones.


DB-630

May 2008

Debug Commands debug ephone raw

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


mac-address


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YD


12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


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.


DB-631

Debug Commands debug ephone raw

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.E1A8 EPHONE raw protocol debugging is enabled for phone 0030.94C3.E1A8 1d05h: skinny socket received 4 bytes on socket [1] 0 0 0 0 1d05h: 1d05h: SkinnyMessageID = 0 1d05h: skinny send 4 bytes 4 0 0 0 0 0 0 0 0 1 0 0 1d05h: socket [1] sent 12 bytes OK (incl hdr) for ephone-(1) 1d06h: skinny socket received 4 bytes on socket [1] 0 0 0 0 1d06h: 1d06h: SkinnyMessageID = 0 1d06h: skinny send 4 bytes 4 0 0 0 0 0 0 0 0 1 0 0 1d06h: socket [1] sent 12 bytes OK (incl hdr) for ephone-(1)

Related Commands

Command

Description

debug ephone alarm


debug ephone detail


debug ephone error






debug ephone pak




debug ephone state




show debugging



DB-632

May 2008

Debug Commands debug ephone register

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


mac-address


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YD


12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


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.


DB-633

Debug Commands debug ephone register

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.8724 Ephone registration debugging is enabled 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: . . . 1d06h: .

Related Commands

New Skinny socket accepted [1] (2 active) sin_family 2, sin_port 50778, in_addr 10.1.0.21 skinny_add_socket 1 10.1.0.21 50778 ephone-(1)[1] StationRegisterMessage (2/3/12) from 10.1.0.21 ephone-(1)[1] Register StationIdentifier DeviceName SEP003094C3E1A8 ephone-(1)[1] StationIdentifier Instance 1 deviceType 7 ephone-1[-1]:stationIpAddr 10.1.0.21 ephone-1[-1]:maxStreams 0 ephone-(1) Allow any Skinny Server IP address 10.1.0.6

ephone-1[1]:RegisterAck sent to ephone 1: keepalive period 30

Command

Description

debug ephone alarm


debug ephone detail


debug ephone error






debug ephone pak


debug ephone raw


debug ephone state




show debugging



DB-634

May 2008

Debug Commands debug ephone sccp-state

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

Cisco IOS Release

Usage Guidelines

(Optional) Specifies the MAC address of a phone.

Modification

12.4(4)XC


12.4(9)T


12.2SX


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.DAB5 EPHONE SCCP state message debugging is enabled for ephones 000B.BEF9.DFB5 *Mar 8 06:38:45.863: 4085254871 unknown *Mar 8 06:38:50.487: *Mar 8 06:38:52.399: *Mar 8 06:38:52.399: TsConnected *Mar 8 06:38:58.415: 4085254871 unknown

%ISDN-6-CONNECT: Interface Serial2/0/0:22 is now connected to ephone-2[13]:SetCallState line 4 DN 60(60) chan 1 ref 100 TsRingIn ephone-2[13]:SetCallState line 4 DN 60(-1) chan 1 ref 100 TsOffHook ephone-2[13]:SetCallState line 4 DN 60(-1) chan 1 ref 100 %ISDN-6-CONNECT: Interface Serial2/0/0:22 is now connected to


DB-635

Debug Commands debug ephone sccp-state

*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 seconds

Related Commands

Command

Description

debug ephone detail

Sets detail debugging for one or all Cisco Unified IP phones.


DB-636

May 2008

Debug Commands debug ephone state

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


mac-address


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YD


12.2(2)XT


12.2(8)T


12.2(8)T1


Usage Guidelines

12.2(11)T

This command was implemented on Cisco 1760 routers.

12.2SX


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.


DB-637

Debug Commands debug ephone state

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.E1A8 EPHONE state debugging is enabled for phone 0030.94C3.E1A8 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h:

Related Commands

ephone-1[1]:OFFHOOK ephone-1[1]:SIEZE on activeline 0 ephone-1[1]:SetCallState line 1 DN 1 TsOffHook ephone-1[1]:Skinny-to-Skinny call DN 1 to DN 2 instance 1 ephone-1[1]:SetCallState line 1 DN 1 TsRingOut ephone-1[1]:Call Info DN 1 line 1 ref 158 called 5002 calling 5001 ephone-1[1]: Jane calling ephone-1[1]: Jill ephone-1[1]:SetCallState line 3 DN 2 TsRingIn ephone-1[1]:Call Info DN 2 line 3 ref 159 called 5002 calling 5001 ephone-1[1]: Jane calling ephone-1[1]: Jill ephone-1[1]:SetCallState line 3 DN 2 TsCallRemoteMultiline ephone-1[1]:SetCallState line 1 DN 1 TsConnected ephone-1[1]:OpenReceive DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 80 ephone-1[1]:OpenReceiveChannelAck 1.2.172.21 port=24010 ephone-1[1]:StartMedia 1.2.172.22 port=24612 DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 80 ephone-1[1]:CloseReceive ephone-1[1]:StopMedia ephone-1[1]:SetCallState line 3 DN 2 TsOnHook ephone-1[1]:SetCallState line 1 DN 1 TsOnHook ephone-1[1]:SpeakerPhoneOnHook ephone-1[1]:ONHOOK ephone-1[1]:SpeakerPhoneOnHook SkinnyReportDnState DN 1 ONHOOK

Command

Description

debug ephone alarm


debug ephone detail


debug ephone error






debug ephone pak


debug ephone raw




debug ephone


show debugging



DB-638

May 2008

Debug Commands debug ephone statistics

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


mac-address


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YD


12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


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.


DB-639

Debug Commands debug ephone statistics

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.E1A8 EPHONE statistics debugging is enabled for phone 0030.94C3.E1A8 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h: 1d06h:

Related Commands

Clear Call Stats for DN 1 call ref 162 Clear Call Stats for DN 1 call ref 162 Clear Call Stats for DN 1 call ref 162 Clear Call Stats for DN 2 call ref 163 ephone-1[1]:GetCallStats line 1 ref 162 DN 1: 5001 ephone-1[1]:Call Stats for line 1 DN 1 5001 ref 162 ephone-1[1]:TX Pkts 0 bytes 0 RX Pkts 0 bytes 0 ephone-1[1]:Pkts lost 4504384 jitter 0 latency 0 ephone-1[1]:Src 0.0.0.0 0 Dst 0.0.0.0 0 bytes 80 vad 0 G711Ulaw64k ephone-1[1]:GetCallStats line 1 ref 162 DN 1: 5001 STATS: DN 1 Packets Sent 0 STATS: DN 2 Packets Sent 0 ephone-1[1]:Call Stats found DN -1 from Call Ref 162 ephone-1[1]:Call Stats for line 0 DN -1 5001 ref 162 ephone-1[1]:TX Pkts 275 bytes 25300 RX Pkts 275 bytes 25300 ephone-1[1]:Pkts lost 0 jitter 0 latency 0

Command

Description

debug ephone alarm


debug ephone detail


debug ephone error






debug ephone pak


debug ephone raw




debug ephone state


show debugging



DB-640

May 2008

Debug Commands debug ephone video

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


Command Default

Debugging is disabled for ephone video.

Command Modes

Privileged EXEC

Command History

Cisco IOS Release

Modification

12.4(4)XC


12.4(9)T


12.2SX


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: tx_idxpref = 3, *Mar 13 16:10:02.703: tx_mpi = 1 *Mar 13 16:10:04.711: *Mar 13 16:10:04.711: *Mar 13 16:10:04.711: *Mar 13 16:10:04.719: chan 1 dn 19

SkinnyVideoCodecMatch_Caps2Caps: match capability: tx_idxcap = 4, rx_idxcap = 0, rx_idxpref = 0, videoBitRate = 7040 ephone-19[1][SEPFFFA00000019]:checkToOpenMultiMedia: dn=19, chan=1 ephone-19[1]:skinnyDP[19].s2s = 0 ephone-19[1]:s2s is not set - hence not video capable ephone-19[1][SEPFFFA00000019]:SkinnyStartMultiMediaTransmission:


DB-641

Debug Commands debug ephone video

*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 == -1 sk3745-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 19

Related Commands

Command

Description

debug ephone alarm

Sets SkinnyStation alarm messages debugging for the ephone.

debug ephone detail

Sets detail debugging for the ephone.

debug ephone error

Sets error debugging for the ephone.

debug ephone message

Sets message debugging for the ephone.

debug ephone mwi

Sets MWI debugging for the ephone.

debug ephone pak

Provides voice packet level debugging and displays the contents of one voice packet in every 1024 voice packets.

debug ephone raw



Sets registration debugging for the ephone.

debug ephone state

Sets state debugging for the ephone.


Sets statistics debugging for the ephone.

show debugging


show ephone

Displays information about registered ephones.


DB-642

May 2008

Debug Commands debug ephone vm-integration

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

Release

Modification

12.3(7)T


12.2SX


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 *Jul *Jul *Jul *Jul *Jul *Jul *Jul *Jul *Jul *Jul

23 23 23 23 23 23 23 23 23 23 23

15:38:03.294:ephone-3[3]:StimulusMessage 15 (1) From ephone 2 15:38:03.294:ephone-3[3]:Voicemail access number pattern check 15:38:03.294:SkinnyGetCallState for DN 3 chan 1 IDLE 15:38:03.294:called DN -1 chan 1, calling DN -1 chan 1 phone -1 s2s:0 15:38:03.294:dn number for dn 3 is 19003 15:38:03.294:Updated number for token 1 is 19003 15:38:03.294:CDN number for dn 3 is 15:38:03.294:Updated number for token 2 is 15:38:03.294:Updated number for token 0 is 15:38:03.294:Update is 219003* 15:38:03.294:New Voicemail number is 19101219003*



DB-643

Debug Commands debug ephone vm-integration

Table 85

Related Commands

debug ephone vm-integration Field Descriptions

Field

Description

token 0

First token that was defined in the pattern.

token 1

Second token that was defined in the pattern.

token 2

Third token that was defined in the pattern.

Command

Description

pattern direct

Configures the DTMF digit pattern forwarding necessary to activate the voice-mail system when a user presses the Messages button on a phone.

pattern ext-to-ext busy

Configures the DTMF digit pattern forwarding necessary to activate the voice-mail system once an internal extension reaches a busy extension and the call is forwarded to voice mail.

pattern ext-to-ext no-answer

Configures the DTMF digit pattern forwarding necessary to activate the voice-mail system once an internal extension fails to connect to an extension and the call is forwarded to voice mail.

pattern trunk-to-ext busy

Configures the DTMF digit pattern forwarding necessary to activate the voice-mail system once an external trunk call reaches a busy extension and the call is forwarded to voice mail.

pattern trunk-to-ext no-answer

Configures the DTMF digit pattern forwarding necessary to activate the voice-mail system when an external trunk call reaches an unanswered extension and the call is forwarded to voice mail.

vm-integration

Enters voice-mail integration configuration mode and enables voice-mail integration with DTMF and analog voice-mail systems.

voicemail

Defines the telephone number that is speed-dialed when the Messages button on a Cisco IP phone is pressed.


DB-644

May 2008

Debug Commands debug errors

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


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 tries

The 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.


DB-645

Debug Commands debug eswilp

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

dot1x

Displays Ethernet Switch with Inline Power (ESWILP) 802.1x debugging messages.

filtermgr

Displays ESWILP filter manager debugging messages.

fltdrv

Displays ESWILP filter driver debugging messages.

igmp

Displays ESWILP Internet Group Management Protocol (IGMP) debugging messages.

port-driver

Displays ESWILP port driver debugging messages.

power-supply

Displays ESWILP power supply information debugging messages.

span

Displays ESWILP Switched Port Analyzer (SPAN) debugging messages.

switch-pm

Displays ESWILP switch port manager debugging messages.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(6)EA2


12.2(15)ZJ

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers. The dot1x, filtermgr, and fltdrv keywords were added.

12.3(4)T


Usage Guidelines

12.2(33)SRA


12.2SX


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


DB-646

May 2008

Debug Commands debug eswilp

Examples

The following example shows debugging messages for the IGMP snooping services on the Ethernet switch network module being displayed: Router# debug eswilp igmp

Related Commands

Command

Description

show debugging



DB-647

Debug Commands debug ethernet cfm all

debug ethernet cfm all To enable all Ethernet connectivity fault management (CFM) debug messages, use the debug ethernet cfm all command in privileged EXEC mode. To disable all Ethernet CFM debug messages, use the no form of this command. debug ethernet cfm all [domain domain-name | level level-id] [vlan vlan-id] no debug ethernet cfm all [domain domain-name | level level-id] [vlan vlan-id]

Syntax Description

domain

(Optional) Indicates that a domain is specified.

domain-name

(Optional) String with a maximum of 154 characters that identifies the specified domain.

level

(Optional) Indicates that a maintenance level is specified.

level-id

(Optional) Integer in the range of 0 to 7 that specifies the maintenance level.

vlan

(Optional) Indicates that a VLAN is specified.

vlan-id

(Optional) Integer in the range of 1 to 4095 that identifies the affected VLAN.

Command Default

All debug commands are enabled.

Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

Modification

12.2(33)SRA


12.4(11)T


12.2SX


This command allows you to conditionally enable debug messages for a specific: •

Maintenance domain

•

Maintenance level

•

Maintenance domain plus VLAN

•

Maintenance level plus VLAN

Additionally, you can filter debug messages by the following: •

Maintenance domain

•

Maintenance level

•

VLAN


DB-648

May 2008

Debug Commands debug ethernet cfm all

•

Combination of maintenance domain and VLAN

•

Combination of maintenance level and VLAN

The output from the debug ethernet cfm all command is a log of activity that shows all Ethernet CFM-related debug messages. Use this command to troubleshoot Ethernet CFM in your network.

Examples

The following example shows output of the debug ethernet cfm all command for the domain named testdomain on VLAN 1010: Router# debug ethernet cfm all domain testdomain vlan 1010 00:01:51: CFM-PKT: Received a cc packet from interface Ethernet1/0 00:01:51: CFM-PKT: cfm packet dump - 104 bytes, interface Ethernet1/0, vlan 3 00:01:51: CFM-PKT: ethernet CFM message dump, dest: 0100.0ccc.ccc1 src: aabb.cc00.0602 Version: 0 Maintenance Level: 1 MsgType: CC(0) Transaction Id: 3042953420 00:01:51: 01 00 0C CC CC C1 AA BB CC 00 06 02 00 5A AA AA 00:01:51: 03 00 00 0C 01 26 00 01 00 08 B5 5F C8 CC 01 00 00:01:51: 29 00 63 73 69 5F 6F 70 65 72 61 74 6F 72 5F 6C 00:01:51: 31 5F 31 5F 33 3A 44 4F 4D 41 49 4E 5F 4F 50 45 00:01:51: 52 41 54 4F 52 5F 4C 31 5F 31 02 00 02 00 3A 03 00:01:51: 00 02 00 4B 04 00 02 00 02 05 00 0B 6D 69 6E 6E 00:01:51: 65 61 70 6F 6C 69 73 00 00:01:51: 00:01:51: CFM-PKT: TLV Service ID 'csi_operator_l1_1_3:DOMAIN_OPERATOR_L1_1' 00:01:51: CFM-PKT: TLV MPID 58 00:01:51: CFM-PKT: TLV LIFETIME 75 00:01:51: CFM-PKT: TLV PORT_STATE 0x2 (DOWN) 00:01:51: CFM-PKT: Received a CC packet with MPID 58, level 1, vlan 3 from interface Ethernet1/0 00:01:51: CFM-EV: Adding new MEP entry for mac aabb.cc00.0602 level 1 svlan 3 00:01:51: CFM-EV: initialize mac elem for slvan table 00:01:51: CFM-EV: Initilize elem in mac table 00:01:51: CFM-EV: Added mac aabb.cc00.0602 at level 1 vlan 3 successfully 00:01:51: CFM-EVT:Inserted rmep in CC db. level 1 vlan 3 mac aabb.cc00.0602 intf Ethernet1/0.2 00:01:51: CFM-PKT: Sending out mep 8 CC message, level 5, vlan 3

Related Commands

Command

Description

debug ethernet cfm diagnostic

Enables low-level diagnostic debugging of Ethernet CFM general or packet-related events.

debug ethernet cfm errors

Enables debugging of Ethernet CFM errors.

debug ethernet cfm events

Enables debugging of Ethernet CFM events.

debug ethernet cfm packets

Enables debugging of Ethernet CFM mesage packets.


DB-649

Debug Commands debug ethernet cfm diagnostic

debug ethernet cfm diagnostic To enable low-level diagnostic debugging of Ethernet connectivity fault management (CFM) general events or packet-related events, use the debug ethernet cfm diagnostic command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug ethernet cfm diagnostic [events | packets] no debug ethernet cfm diagnostic [events | packets]

Syntax Description

events

(Optional) Triggers only events related to debugs.

packets

(Optional) Triggers only packets related to debugs.

Command Default

Diagnostic debugging for both events and packets is enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRA


12.4(11)T


12.2SX


Usage Guidelines

The output from this command is a log of activity. Use this command to troubleshoot Ethernet CFM in your network.

Examples

The following example shows output of the debug ethernet cfm diagnostic command with no options specified: Router# debug ethernet cfm diagnostic 00:05:39: CFM-PKT: Received a cc packet from interface Ethernet1/0 00:05:39: CFM-PKT: cfm packet dump - 101 bytes, interface Ethernet1/0, vlan 2 00:05:39: CFM-PKT: ethernet CFM message dump, dest: 0100.0ccc.ccc6 src: aabb.cc00.0300 Version: 0 Maintenance Level: 6 MsgType: CC(0) Transaction Id: 2183808794 00:05:39: 01 00 0C CC CC C6 AA BB CC 00 03 00 00 57 AA AA 00:05:39: 03 00 00 0C 01 26 00 06 00 08 82 2A 47 1A 01 00 00:05:39: 29 00 63 73 69 5F 70 72 6F 76 69 64 65 72 5F 6C


DB-650

May 2008

Debug Commands debug ethernet cfm diagnostic

00:05:39: 00:05:39: 00:05:39: 00:05:39:

Related Commands

36 56 00 6D

5F 49 02 62

31 44 00 75

5F 45 4B 73

32 3A 44 4F 4D 41 49 4E 5F 50 52 4F 52 5F 4C 36 5F 31 02 un al00 02 00 15 03 04 00 02 00 01 05 00 08 63 6F 6C 75 00

Command

Description

debug ethernet cfm all

Enables all Ethernet CFM debug messages.








DB-651

Debug Commands debug ethernet cfm errors

debug ethernet cfm errors To enable debugging of Ethernet connectivity fault management (CFM) errors, use the debug ethernet cfm errors command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug ethernet cfm errors no debug ethernet cfm errors

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRA


12.4(11)T


12.2SX


Usage Guidelines


Examples

The following example shows output of the debug ethernet cfm errors command: Router# debug ethernet cfm errors 10:46:26: 10:46:26: svlan 2 10:48:55: 10:48:56: 10:48:57:

Related Commands

CFM-ERR: MPID matched with a local MEP!, level 5, svlan 2, mpid 50 CFM-ERR: Received duplicate mpid 50 due to configuration error for level 5, CFM-ERR: Lifetime timer fired for level 4, svlan 2 mac aabb.cc00.0501, mpid 43 CFM-ERR: Lifetime timer fired for level 6, svlan 2 mac aabb.cc00.0300, mpid 21 CFM-ERR: Lifetime timer fired for level 5, svlan 5 mac aabb.cc00.0602, mpid 60

Command

Description




Enables low-level diagnostic debugging of Ethernet CFM general events or packet-related events.


DB-652

May 2008

Debug Commands debug ethernet cfm errors

Command

Description






DB-653

Debug Commands debug ethernet cfm events

debug ethernet cfm events To enable debugging of Ethernet connectivity fault management (CFM) events, use the debug ethernet cfm events command in privileged EXEC mode. To disable debugging, use the no form of this command. debug ethernet cfm events [domain domain-name | level level-id] [vlan vlan-id] no debug ethernet cfm events [domain domain-name | level level-id] [vlan vlan-id]

Syntax Description

domain


domain-name


level


level-id


vlan


vlan-id


Command Default

Event debugging is disabled for all domains and all VLANs.

Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

Modification

12.2(33)SRA


12.4(11)T


12.2SX


This command provides capability to filter debug messages by: •

Maintenance domain

•

Maintenance level

•

VLAN

•


•




DB-654

May 2008

Debug Commands debug ethernet cfm events

Examples

The following example shows output of the debug ethernet cfm events command for the domain named testdomain on VLAN 1010: Router# debug ethernet cfm events domain testdomain vlan 1010 10:48:58: CFM-EV: Adding new MEP entry for mac aabb.cc00.0100 level 5 svlan 5 10:48:58: CFM-EVT:Inserted rmep in CC db. level 5 vlan 5 mac aabb.cc00.0100 intf Ethernet1/0 10:48:59: CFM-EVT: Found remote mep for level 5 svlan 5, mpid 60 10:49:07: CFM-EVT: Found remote mep for level 5 svlan 5, mpid 38

Related Commands

Command

Description










DB-655

Debug Commands debug ethernet cfm packets

debug ethernet cfm packets To enable debugging of Ethernet connectivity fault management (CFM) message packets, use the debug ethernet cfm packets command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug ethernet cfm packets [domain domain-name | level level-id] [vlan vlan-id] no debug ethernet cfm packets [domain domain-name | level level-id] [vlan vlan-id]

Syntax Description

domain


domain-name


level


level-id


vlan


vlan-id


Command Default

Debugging is enabled for all domains and VLANs.

Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

Modification

12.2(33)SRA


12.4(11)T


12.2SX


Use the debug ethernet cfm packets command in privileged EXEC mode to enable debugging of Ethernet CFM message packets. This command provides capability to filter debug messages by: •

Maintenance domain

•

Maintenance level

•

VLAN

•


•




DB-656

May 2008

Debug Commands debug ethernet cfm packets

Examples

The following example shows output of the debug ethernet cfm packets command for the domain named testdomain on VLAN 1010: Router# debug ethernet cfm packets domain testdomain vlan 1010 10:52:50: CFM-PKT: TLV Service ID 'csi_operator_l5_1_5:DOMAIN_OPERATOR_L5_1' 10:52:50: CFM-PKT: TLV MPID 38 10:52:50: CFM-PKT: TLV LIFETIME 75 10:52:50: CFM-PKT: TLV PORT_STATE 0x1 (UP) 10:52:50: CFM-PKT: Received a CC packet with MPID 38, level 5, vlan 5 from interface Ethernet1/0

Related Commands

Command

Description










DB-657

Debug Commands debug ethernet lmi

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

all

All debug messages are to be filtered.

errors

All errors are to be filtered.

events

All events are to be filtered.

packets

All decoded messages are to be filtered.

interface

(Optional) Specifies an interface to use to filter debug messages.

type

(Optional) String that identifies the type of interface. Valid options are the following:

number

•

ethernet—Ethernet IEEE 802.3 interface

•

fastethernet—Fast Ethernet IEEE 802.3 interface

•

gigabitethernet—Gigabit Ethernet IEEE 802.3z interface

(Optional) Integer that identifies the interface.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T


12.2(33)SRB

Support for this command on the Cisco 7600 router was integrated into Cisco IOS Release 12.2(33)SRB.

12.2SX


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.


DB-658

May 2008

Debug Commands debug ethernet lmi

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 all Ethernet Ethernet Ethernet Ethernet

LMI LMI LMI LMI

errors debugging is on packets debugging is on events debugging is on packets hex debugging is on

00:29:32: ELMI Et0/0 EVENT: ce_event: State 0x0, Event 0x4 00:29:32: ELMI Et0/0 EVENT: Old State=0x0, Event=0x4, New State=0x2 00:29:32: ELMI Et0/0 EVENT: Updated Stat Type: ETHER_LMI_ST_LMSG_SENT 00:29:32: ELMI Et0/0 PKT HEX: TX->:0x01750101010202B4B30305000000000400000000000 00:29:32: ELMI Et0/0 PACKET: Outgoing Protocol Version : 0x1 Message : STATUS ENQ (0x75) Report Type : Check Sequence Number : Snd(0xB4), Rcv(0xB3) Data Instance : Value(0x4) 00:29:32: ELMI Et0/0 PKT HEX: RX FAULT2 *Aug 17 14:00:53.732: ether_oam_port Gi2/9: during state FAULT2, got event 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 state SEND_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=0 elapsed_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=0 elapsed_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=0 elapsed_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=0 elapsed_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):


DB-663

Debug Commands debug ethernet oam

*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 00


DB-664

May 2008

Debug Commands debug ethernet service

debug ethernet service To enable debugging of Ethernet customer service instances, use the debug ethernet service command privileged EXEC mode. To disable debugging, use the no form of this command. debug ethernet service {all | api | error | evc [evc-id] | instance [id id | interface type number | qos] | interface type number | microblock | oam-mgr} debug ethernet service {all | api | error | evc | instance | interface | microblock | oam-mgr}

Syntax Description

all

Displays all Ethernet customer-service debug messages.

api

Displays debug messages about the interaction between the Ethernet infrastructure and its clients.

error

Displays Ethernet customer service error messages occurring in the Ethernet infrastructure subsystem.

evc

Displays Ethernet virtual connection (EVC) debug messages.

evc-id

(Optional) String from 1 to 100 characters that identifies an EVC for debugging.

instance

Displays debug messages related to Ethernet customer service instances.

id

(Optional) Displays Ethernet service-instance debug messages for a specific Ethernet service instance ID and interface.

id

(Optional) Integer in the range from 1 to 4294967295 that is the service identifier.

interface

Displays debugging for Ethernet services on all interfaces or on a specified interface. (Optional) When used as an option with the instance keyword, service instance debug messages for the interface are displayed.

type number

Type and number of the physical interface.

qos

Displays debug messages for the Ethernet service quality of service (QoS).

microblock

Displays debug messages for the Ethernet service microblocks.

oam-mgr

Displays debug messages for the Ethernet operations, administration, and maintenance (OAM) manager component of the infrastructure.

Command Default

Ethernet service debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)SEG


12.2(33)SRB


12.2SX



DB-665

Debug Commands debug ethernet service

Usage Guidelines

The debug ethernet service command is useful for troubleshooting. The undebug ethernet service command is the same as the no debug ethernet service command. When you use the evc keyword without specifying an EVC ID, debugging is enabled for all EVCs on the system. When you use the instance keyword without specifying options, debugging for all service instances is enabled. If a service instance ID and interface are specified, only debug messages for the associated service instance are displayed. If only an interface is specified, debug messages for all service instances on that interface only are displayed.

Examples

The following example shows output after issuing the debug ethernet service all command: Router# debug ethernet service all Ethernet service error debugging is on Ethernet service api debugging is on Ethernet service interface debugging is on Ethernet service instance debugging is on Ethernet service instance qos debugging is on Ethernet service evc debugging is on Ethernet service OAM Manager debugging is on

Related Commands

Command

Description

show debugging



DB-666

May 2008

Debug Commands debug event manager

debug 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

action cli

Displays debugging messages about command-line interface (CLI) event messages.

action cns

Displays debugging messages about CNS event messages.

action mail

Displays debugging messages about e-mail event messages.

all


api calls

Displays debugging messages about application programming interface (API) calls.

api errors

Displays debugging messages about API errors.

detector all

Displays all event detector debugging messages.

detector application

Displays debugging messages about the application-specific event detector.

detector cli

Displays debugging messages about the CLI event detector.

detector counter

Displays debugging messages about the counter event detector.

detector interface

Displays debugging messages about the interface counter event detector.

detector ioswdsysmon

Displays debugging messages about the watchdog event detector.

detector none

Displays debugging messages about the none event detector.

detector snmp

Displays debugging messages about the Simple Network Management Protocol (SNMP) event detector.

detector syslog

Displays debugging messages about the syslog event detector.

detector timer

Displays debugging messages about the timer event detector.

metricdir

Displays debugging messages about the EEM metrics event detector.

policydir

Displays debugging messages about the EEM policy director.

server events

Displays debugging messages about the EEM server events.

server scheduling

Displays all debugging messages about the EEM server scheduling events.

tcl cli_library

Displays all debugging messages about the Tool Command Language (Tcl) command-line interface (CLI) library.


DB-667


tcl commands

Displays all debugging messages about the Tcl commands.

tcl smtp_library

Displays all debugging messages about the Tcl Simple Mail Transfer Protocol (SMTP) library.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(26)S


12.3(4)T


12.3(2)XE

This command was integrated into Cisco IOS Release 12.3(2)XE.

12.2(25)S


12.3(14)T

The action cli, action mail, detector all, detector cli, detector none, and metricdir keywords were added.

12.2(28)SB


12.2(18)SXF4

This command was integrated into Cisco IOS Release 12.2(18)SXF4 to support Software Modularity images only.

12.2(33)SRA


12.2(18)SXF5

This command was integrated into Cisco IOS Release 12.2(18)SXF5.

12.2SX


Usage Guidelines

Caution

Examples

Use the debug event manager command to troubleshoot EEM command operations.

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

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 events Debug Embedded Event Manager server events debugging is on Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# event manager applet timer-test Router(config-applet)# event timer countdown time 20 Router(config-applet)# action label1 syslog msg "Test message" Router(config-applet)# end Router# 03:46:55: fh_server: fh_io_msg: received msg 6 from client jobid 11 03:46:55: fh_server: fh_io_msg: handling event register with esid = 23


DB-668

May 2008


03:46:55: fh_msg_send_to_fd: receive a reply msg, minor: 5 03:46:55: fh_server: fh_io_msg: received msg 26 from client jobid 11 03:46:55: fh_msg_send_to_fd: receive a reply msg, minor: 5 03:46:55: %SYS-5-CONFIG_I: Configured from console by console 03:47:15: fd_pulse_hndlr: received a pulse from /dev/fm/fd_timer 03:47:15: fh_msg_send_to_fd: receive a reply msg, minor: 5 03:47:15: fd_pulse_hndlr: received FH_MSG_EVENT_PUBLISH 03:47:15: fh_schedule_callback: fh_schedule_callback: cc=632C0B68 prev_epc=0; epc=63A41670 03:47:15: fh_io_msg: received FH_MSG_API_INIT; jobid=13, processid=82, client=3, job name=EEM Callback Thread 03:47:15: fh_server: fh_io_msg: received msg 10 from client jobid 13 03:47:15: %HA_EM-6-LOG: timer-test: Test message 03:47:15: fh_server: fh_io_msg: received msg 62 from client jobid 13 03:47:15: fh_schedule_callback: fh_schedule_callback: cc=632C0B68 prev_epc=63A41670; epc=0 03:47:15: fh_server: fh_io_msg: received msg 1 from client jobid 13 03:47:15: fh_io_msg: received FH_MSG_API_CLOSE client=3

Table 86 describes some of the significant fields shown in the display. Table 86

debug event manager Field Descriptions

Field

Description

Debug Embedded Event Manager server events debugging

Indicates the type of debugging output and whether the debugging is on or off.

fh_server

Indicates a server event message.

fh_io_msg

Indicates that a message has been sent to, or received from, a client process.

fh_msg_send_to_fd

Indicates that a message has been sent to the event detector.

fd_pulse_hndlr

Indicates that a message has been received by the event detector pulse handler.


DB-669

Debug Commands debug events

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


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 events RESET(4/0): PLIM type is 1, Rate is 100Mbps aip_disable(4/0): state=1 config(4/0) aip_love_note(4/0): asr=0x201 aip_enable(4/0) aip_love_note(4/0): asr=0x4000 aip_enable(4/0): restarting VCs: 7 aip_setup_vc(4/0): vc:1 vpi:1 vci:1 aip_love_note(4/0): asr=0x200 aip_setup_vc(4/0): vc:2 vpi:2 vci:2 aip_love_note(4/0): asr=0x200 aip_setup_vc(4/0): vc:3 vpi:3 vci:3 aip_love_note(4/0): asr=0x200 aip_setup_vc(4/0): vc:4 vpi:4 vci:4 aip_love_note(4/0): asr=0x200 aip_setup_vc(4/0): vc:6 vpi:6 vci:6 aip_love_note(4/0): asr=0x200 aip_setup_vc(4/0): vc:7 vpi:7 vci:7 aip_love_note(4/0): asr=0x200 aip_setup_vc(4/0): vc:11 vpi:11 vci:11 aip_love_note(4/0): asr=0x200


DB-670

May 2008



debug events Field Descriptions

Field

Description

PLIM type

Indicates the interface rate in Mbps. Possible values are:

state

asr

•

1 = TAXI(4B5B) 100 Mbps

•

2 = SONET 155 Mbps

•

3 = E3 34 Mbps

Indicates current state of the ATM Interface Processor (AIP). Possible values are: •

1 = An ENABLE will be issued soon.

•

0 = The AIP will remain shut down.

Defines a bitmask, which indicates actions or completions to commands. Valid bitmask values are: •

0x0800 = AIP crashed, reload may be required.

•

0x0400 = AIP detected a carrier state change.

•

0x0n00 = Command completion status. Command completion status codes are: – n = 8 Invalid physical layer interface module (PLIM) detected – n = 4 Command failed – n = 2 Command completed successfully – n = 1 CONFIG request failed – n = 0 Invalid value

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 100Mbps

The 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=1

The following line indicates that a configuration command has been completed by the AIP: aip_love_note(4/0): asr=0x201

The 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=0x4000

The following line of output indicates that the AIP enable function is restarting all permanent virtual circuits (PVCs) automatically:


DB-671


aip_enable(4/0): restarting VCs: 7

The 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:1 aip_love_note(4/0): asr=0x200


DB-672

May 2008

Debug Commands debug fax dmsp

debug fax dmsp To troubleshoot the fax Document Media Service Provider (DMSP), use the debug fax dmsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fax dmsp [all | default | detail | error [call [informational] | software [informational]] | event | function | inout] no debug fax dmsp

Syntax Description

all

(Optional) Displays all fax DMSP debugging messages.

default

(Optional) Displays fax DMSP error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays fax DMSP background messages.

error

(Optional) Displays fax DMSP error messages.

call


informational


software


event

(Optional) Displays fax DMSP events.

function

(Optional) Displays fax DMSP functions.

inout

(Optional) Displays fax DMSP in/out functions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug dmsp doc-to-fax and debug dmsp fax-to-doc commands.

12.2SX


Examples

The following is sample output from the debug fax dmsp all command: Router# debug fax dmsp all 2d07h: //70/67D6061D8012/DMSP/docmsp_call_setup_request: ramp data dir=ONRAMP, conf dir=DEST 2d07h: //70/67D6061D8012/DMSP/docmsp_caps_ind: cid(0x46), srcCallID(0x44) 2d07h: //70/67D6061D8012/DMSP/docmsp_bridge: conf id(0x33), srcCallID(0x46), dstCallID(0x44),


DB-673

Debug Commands debug fax dmsp

ramp data dir=ONRAMP, conf dir=DEST, encode out=1 2d07h: //70/67D6061D8012/DMSP/docmsp_bridge: Bridge done 2d07h: //70/67D6061D8012/DMSP/docmsp_bridge: conf id(0x34), srcCallID(0x46), dstCallID(0x45), ramp data dir=ONRAMP, conf dir=SRC, encode out=1 2d07h: //70/67D6061D8012/DMSP/docmsp_bridge: Bridge done 2d07h: //70/67D6061D8012/DMSP/docmsp_xmit: srcCallID(0x44), dstCallID(0x46), direction=0 2d07h: //68/67D6061D8012/DMSP/docmsp_process_rcv_data: evID=0, proto_flag=3, srcCallID(0x44), dstCallID(0x46) 2d07h: //70/67D6061D8012/DMSP_ON/docmsp_tiff_writer_data_process: START_OF_CONNECTION 2d07h: //70/67D6061D8012/DMSP_ON/docmsp_tiff_writer_data_process: START_OF_FAX_PAGE 2d07h: //70/67D6061D8012/DMSP_ON/docmsp_tiff_writer_get_buffer_callback: tiff_segment=0x63A88ECC 2d07h: //70/67D6061D8012/DMSP_ON/docmsp_tiff_writer_get_buffer_callback: tiff_segment=0x63D58944 2d07h: //70/67D6061D8012/DMSP/docmsp_process_rcv_data: Done


debug fax dmsp Field Descriptions

Field

Description

//70/67D6061D8012/DMSP/ docmsp_call_setup_request:

The format of this message is //callid/GUID/DMSP/function name: •

CallEntry ID is 70. This indicates a unique call leg.

•

GUID is 67D6061D8012. This identifies the call.

•

DMSP is the module name.

•

The docmsp_call_setup_request field shows that the DMSP is requesting a call setup.

ramp data dir

Indicates if the data direction is on-ramp or off-ramp.

conf dir

Indicates if the data is from the source or destination.

docmsp_bridge:

Indicates that the DMSP is setting up a bridge to the destination.

docmsp_xmit:

Indicates that the DMSP is transmitting.

docmsp_process_rcv_data:

Indicates that the DMSP is starting the process to receive data.

docmsp_tiff_writer_data_process:

Indicates the process that is being started.

docmsp_tiff_writer_get_buffer_ callback:

Indicates the segment for the DMSP TIFF writer get_buffer_callback parameter.


DB-674

May 2008

Debug Commands debug fax fmsp

debug fax fmsp To troubleshoot the Fax Media Service Provider (FMSP), use the debug fax fmsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fax fmsp [all | default | detail | error [call [informational] | software [informational]] | event | function | inout | receive | send] no debug fax fmsp

Syntax Description

all

(Optional) Displays all fax FMSP debugging messages.

default

(Optional) Displays fax FMSP error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays fax FMSP background messages.

error

(Optional) Displays fax FMSP error messages.

call


informational


software


event

(Optional) Displays fax FMSP events.

function

(Optional) Displays fax FMSP functions.

inout

(Optional) Displays fax FMSP in/out functions.

receive

(Optional) Receives T.30 or T.38 debugs.

send

(Optional) Sends T.30 or T.38 debugs.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug fmsp receive and debug fmsp send commands.

12.2SX


Examples

The following is sample output from the debug fax fmsp all command: Router# debug fax fmsp all 2d08h: //76/90A52CB88014/FMSP/faxmsp_call_setup_request: session(0x63A8A474), vdbPtr(0x62CA45A8),data dir=ONRAMP, conf dir=DEST 2d08h: //76/90A52CB88014/FMSP/faxmsp_bridge:


DB-675


confID(0x38), srcCID(0x4C), dstCID(0x4B) 2d08h: //76/90A52CB88014/FMSP/faxmsp_bridge: ramp data dir=ONRAMP, conf dir=DEST 2d08h: //76/90A52CB88014/FMSP/faxmsp_bridge: Explicit caps ind. done; Wait for registry cap ind 2d08h: //76/90A52CB88014/FMSP/faxmsp_caps_ind: per_bridge_info(0x63D52FD8), cap_ind_state(0x6) 2d08h: //76/90A52CB88014/FMSP/faxmsp_caps_ind[1617]: 2d08h: //76/90A52CB88014/FMSP/faxmsp_caps_ack: direction=0, srcCID(0x4B), dstCID(0x0) 2d08h: //76/90A52CB88014/FMSP/faxmsp_codec_download_done: per_bridge_info(0x63D52FD8), application_data(0x63C54698), state(0x2), direction=2 2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer: event(0x402897C0), bufferBegin(0x63A86B5C), dataBegin(0x402897EC) 2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer: event(0x40289B50), bufferBegin(0x63C55794), dataBegin(0x40289B7C) 2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer: event(0x40851E58), bufferBegin(0x63D4EAE4), dataBegin(0x40851E84) 2d08h: //76/90A52CB88014/FMSP/faxmsp_xmit: srcCallID(0x4B), dstCallID(0x4C) 2d08h: //76/90A52CB88014/FMSP/faxmsp_xmit[1813]: 2d08h: //76/90A52CB88014/FMSP/faxmsp_process_rcv_data: state(0x1), evID=918065, evProtoFlag=2 2d08h: //76/90A52CB88014/FMSP/t38_rx_buffer: t38 rx msg dump (size=6): 00 00 01 00 00 00 2d08h: //76/90A52CB88014/FMSP/faxmsp_process_rcv_data[1994]: 2d08h: //76/90A52CB88014/FMSP/fax2_phaseB_receive: CSI_PACKET(8881111) DIS_PACKET(speed=5, resolution=1, encoding=1) 2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer: event(0x40289690), bufferBegin(0x63A7E798), dataBegin(0x402896BC) 2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer: event(0x4028858C), bufferBegin(0x63B89AC0), dataBegin(0x402885B8) 2d08h: //76/90A52CB88014/FMSP/t38_tx_command: t38 tx msg dump (size=47): 00 04 2A C0 04 80 00 16 FF C0 02 8C 8C 8C 8C 1C 1C 1C 04 04 04 04 04 04 04 04 04 04 04 04 04 28 00 09 FF C8 01 00 77 1F 01 01 19 80 40 00 00 2d08h: //76/90A52CB88014/FMSP/fax2_phaseB_receive: fax2_response_receive, PROCESSING


debug fax fmsp all Field Descriptions

Field

Description

//76/90A52CB88014/FMSP/ faxmsp_call_setup_request:

The format of this message is //callid/GUID/FMSP/function name •


•

GUID is 90A52CB88014. This identifies the call.

•

FMSP is the module name.

•

The faxmsp_call_setup_request field shows that the FMSP is requesting a call setup.

ramp data dir

Indicates if the data direction is on-ramp or off-ramp.

conf dir

Indicates if the data is from the source or destination.


DB-676

May 2008


Table 89

debug fax fmsp all Field Descriptions (continued)

Field

Description

faxmsp_bridge:

Indicates that the FMSP is setting up a bridge to the destination.

faxmsp_xmit:

Indicates that the FMSP is transmitting data.

faxmsp_process_rcv_data:

Indicates that the FMSP is beginning the process to receive data.

t38_rx_buffer:

Shows the contents of the T.38 transmit buffer.

t38_tx_command:

Shows the T.38 transmit command.


DB-677

Debug Commands debug fax foip

debug fax foip To troubleshoot fax mail, use the debug fax foip command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fax foip [all | default | detail | error [call [informational] | software [informational]] | event | function | inout] no debug fax foip

Syntax Description

all

(Optional) Displays all fax mail debugging messages.

default

(Optional) Displays fax mail error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays fax mail background messages.

error

(Optional) Displays fax mail error messages.

call


informational


software


event

(Optional) Displays fax mail events.

function

(Optional) Displays fax mail functions.

inout

(Optional) Displays fax mail in/out functions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug foip off-ramp and debug foip on-ramp commands.

12.2SX


Examples

The following is sample output from the debug fax foip all command: Router# debug fax foip all 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_call_handoff: Authentication: Id: 0 Method: IVR or unknown Status: SUCCESS Enabled: FALSE


DB-678

May 2008


Template: List: fax MailtoAddress: Calling Oct3A=0x0 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_vtsp_fmsp: Begin Conferencing VTSP and FMSP 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_vtsp_fmsp[887]: 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_change_state: Old State=0, New State=1 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_call_handoff[2953]: 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_validate_context[930]: 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_created: VTSP and FMSP Are Conferenced; Waiting for FMSP Call Detail Event 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_change_state: Old State=1, New State=2 2d07h: %ISDN-6-CONNECT: Interface Serial2:30 is now connected to unknown 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_validate_context[930]: 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_msp_event: 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: Prepare MSPI Call Setup Request 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: Envelope [email protected] 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: Envelope [email protected] 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: RFC822 To Comment=dileung 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: Faxmail Subject=hagar-c5300-bw12 subject line here 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: Disposition Notification= 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: Originator TSI=RFC822 From Comment= 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: Auth/Account ID: `0' 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi: Call Setup Request To MSPI 2d07h: //37/67E715B7800A/FOIP_ON/lapp_on_setup_mspi[748]: 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_fmsp_dmsp: Starting Conference with FMSP and DMSP 2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_fmsp_dmsp: Tiff File Created; Time=2003:06:05 22:46:48


debug fax foip all Field Descriptions

Field

Description

//35/67E715B7800A/FOIP_ON/ lapp_on_call_handoff:

The format of this message is //callid/GUID/FOIP_ON/function name:

lapp_on_conference_vtsp_fmsp:

•


•

GUID is 67E715B7800A. This identifies the call.

•

FOIP_ON identifies the fax mail onramp call leg. FOIP_OFF would identify an offramp call leg.

•

The lapp_on_call_handoff field shows that the fax mail is initiating a call handoff.

Indicates that fax mail is starting a conference for VTSP and FMSP.


DB-679


Table 90

debug fax foip all Field Descriptions (continued)

Field

Description

lapp_on_change_state

Indicates that the fax mail is changing state.

lapp_on_conference_created

Indicates that the conference is working properly between the VTSP and FMSP.

lapp_on_setup_mspi:

Indicates that fax mail is displaying an MPSI event.

lapp_on_conference_fmsp_dmsp:

Indicates that fax mail is starting a conference for FMSP and DMSP.


DB-680

May 2008

Debug Commands debug fax mmoip aaa

debug fax mmoip aaa To display output relating to authentication, authorization, and accounting (AAA) services using multimedia mail over IP (MMoIP) for the Store and Forward Fax feature, use the debug fax mmoip aaa command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fax mmoip aaa [all | default | error [call [informational] | software [informational]] | inout] no debug fax mmoip aaa

Syntax Description

all

(Optional) Displays all MMoIP AAA debugging messages.

default

(Optional) Displays MMoIP AAA error and inout information. This option also runs if no keywords are added.

error

(Optional) Displays MMoIP AAA error messages.

call


informational


software


inout

(Optional) Displays MMoIP AAA in/out functions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug mmoip aaa command.

12.2SX


Examples

The following example shows output from the debug fax mmoip aaa all command for an onramp fax connection: Router# debug fax mmoip aaa all 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: UID=3 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: fax_account_id_origin=NONE_ID 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: [email protected], Length=39 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: fax_pages=0 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:


DB-681

Debug Commands debug fax mmoip aaa

fax_connect_speed=disable bps 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: fax_mdn_flag=FALSE 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: fax_auth_status=USER NOT AUTHENTICATED 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: email_server_address=172.19.140.112 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: email_server_ack_flag=TRUE 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: gateway_id=Router.cisco.com 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: call_type=Fax Receive 16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp: abort_cause=10


debug fax mmoip aaa all Field Descriptions

Field

Description

//3/D9242FD08002/ MMOIP_AAA_ON/ mmoip_aaa_accounting_onramp

The format of this message is //callid/GUID/module name/function name: •


•

GUID is D9242FD08002. This identifies the call.

•

MMOIP_AAA_ON identifies the fax mail onrampMMOIP AAA call leg. MMOIP_AAA_OFF would identify the offramp call leg.

•

The mmoip_aaa_accounting_onramp field shows that the accounting for an onramp fax is active.

fax_msg_id=00012003151904623 @Router.cisco.com

Displays the fax message ID.

gateway_id=Router.cisco.com

Displays the name of the router.

call_type=Fax Receive

Indicates that the fax is being received.


DB-682

May 2008

Debug Commands debug fax mspi

debug fax mspi To troubleshoot the fax Mail Service Provider Interface (MSPI), use the debug fax mspi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fax mspi [all | default | detail | error [call [informational] | software [informational]] | event | function | inout] no debug fax mspi

Syntax Description

all

(Optional) Displays all fax MSPI debugging messages.

default

(Optional) Displays fax MSPI error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays fax MSPI background messages.

error

(Optional) Displays fax MSPI error messages.

call


informational


software


event

(Optional) Displays fax MSPI events.

function

(Optional) Displays fax MSPI functions.

inout

(Optional) Displays fax MSPI in/out functions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug mspi receive and debug mspi send commands.

12.2SX


Examples

The following is sample output from the debug fax mspi all command: Router# debug fax mspi all Router# 2d07h: %ISDN-6-CONNECT: Interface Serial2:30 is now connected to unknown 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_call_setup_request: Outgoing Peer Tag=22 Envelope [email protected] Envelope [email protected]


DB-683


Mime Outer Type=2 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_check_connect: MMccb(Count=0) 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_check_connect: SMTP Connected To The Server ! 2d07h: //41/ACF704FA800B/MSPI/mspi_bridge: MMccb(State=CONNECTED, Type=Onramp), Destination Call Id=0x2A 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=0), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=1), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=2), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=3), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_onramp_buff_finished_callback: MMccb(Call State=CONFERENCED, Buffer Count=9) 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_onramp_buff_finished_callback: MMccb(Call State=CONFERENCED, Buffer Count=8) 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_onramp_buff_finished_callback: MMccb(Call State=CONFERENCED, Buffer Count=7) 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_onramp_buff_finished_callback: 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=0), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=1), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=2), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=3), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=4), Source Call 2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit: MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=5), Source Call Router#

Id=0x2A Id=0x2A Id=0x2A Id=0x2A

Id=0x2A Id=0x2A Id=0x2A Id=0x2A Id=0x2A Id=0x2A


debug fax mspi all Field Descriptions

Field

Description

/41/ACF704FA800B/MSPI_ON/mspi_ call_setup_request:



•

GUID is ACF704FA800B. This identifies the call.

•

MSPI_ON identifies the fax mail onramp MSPI call leg. MSPI_OFF would identify the offramp call leg.

•

The mspi_call_setup_request field shows that the MSPI is requesting a call setup.

Outgoing Peer Tag=22

Indicates the unique dial peer tag.

Envelope [email protected]

Indicates the sender of the fax mail message.

Envelope [email protected]

Indicates the receiver of the fax mail message.

mspi_xmit:

Indicates that the MSPI is transmitting data.


DB-684

May 2008


Table 92

debug fax mspi all Field Descriptions (continued)

Field

Description

State=CONFERENCED

Describes the MPSI state.

Type=Onramp

Describes whether the fax is on-ramp or off-ramp.

Buffer Count=0

Indicates the buffer count.

Source Call Id=0x2A

Identifies the source call ID.


DB-685

Debug Commands debug fax mta

debug fax mta To troubleshoot the fax Mail Transfer Agent (MTA), use the debug fax mta command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fax mta [all | default | detail | error [call [informational] | software [informational]] | event | function | inout] no debug fax mta

Syntax Description

all

(Optional) Displays all fax MTA debugging messages.

default

(Optional) Displays fax MTA error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays fax MTA background messages.

error

(Optional) Displays fax MTA error messages.

call


informational


software


event

(Optional) Displays fax MTA events.

function

(Optional) Displays fax MTA functions.

inout

(Optional) Displays fax MTA in/out functions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug mta receive all, debug mta send all, and debug mta send rcpt-to commands.

12.2SX


Examples

The following is sample output from the debug fax mta all command: Router# debug fax mta all 2d07h: %ISDN-6-CONNECT: Interface Serial2:30 is now connected to unknown 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_new_context_guid[2177]: 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_open: [email protected], [email protected] 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_open[1868]: 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_add_headers:


DB-686

May 2008


from_comment= 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_work_routine: socket 0 readable for first time 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 220 vip2-das.cisco.com ESMTP Sendmail 8.9.3/8.9.3; Thu, 5 Jun 2003 23:24:54 -0700 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln: (C)S: EHLO Router.cisco.com 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write: return code=0 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-vip2-das.cisco.com Hello [172.19.140.108], pleased to meet you 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-EXPN 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-VERB 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-8BITMIME 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-SIZE 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-DSN 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-ONEX 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-ETRN 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250-XUSR 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250 HELP 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln: (C)S: MAIL FROM: 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write: return code=0 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250 ... Sender ok 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln: (C)S: RCPT TO: 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write: return code=0 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 250 ... Recipient ok 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write: return code=0 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln: (C)R: 354 Enter mail, end with "." on a line by itself 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln: (C)S: Received: by Router.cisco.com for (with Cisco NetWorks); Thu, 05 Jun 2003 23:11:09 +0000 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write: return code=0 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln: (C)S: To: "jdoe" 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write: return code=0 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln: (C)S: Message-ID: 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write: return code=0 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln: (C)S: Date: Thu, 05 Jun 2003 23:11:09 +0000 2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write: return code=0


DB-687



debug fax mta all Field Descriptions

Field

Description

//-1/CEB9FA0B800E/SMTPC/ esmtp_client_engine_open:


CallEntry ID is -1. This indicates that a call leg has not been identified.

•

GUID is CEB9FA0B800E. This identifies the call.

•

SMTPC is the module name.

•

The esmtp_client_engine_open field shows that the fax mail client engine is opening a session.

[email protected]

Indicates the sender of the fax mail message.

[email protected]

Indicates the receiver of the fax mail message.

esmtp_client_engine_writeln:

Indicates that the fax mail client engine is writing data.

esmtp_client_engine_getln:

Indicates that the fax mail client engine is receiving data.


DB-688

May 2008

Debug Commands debug fax relay t30

debug fax relay t30 To display debugging messages for T.30 real-time fax, use the debug fax relay t30 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fax relay t30 {all | calling-number string | called-number string} no debug fax relay t30

Syntax Description

all

Enables debugging for all incoming and outgoing calls.

calling-number

Enables debugging for incoming numbers that begin with a specified string of digits.

called-number

Enables debugging for outgoing numbers that begin with a specified string of digits.

string

Digits that specify the incoming or outgoing number.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB1

The debug fax relay t30 command was introduced on Cisco AS5350, Cisco AS5400, and Cisco AS5850 access servers.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T for the Cisco AS5350, Cisco AS5400, and Cisco AS5850 access servers.

12.2SX


Usage Guidelines

The incoming or outgoing numbers must be a valid E.164 destination. The period symbol (.) as a wildcard should not be used. Instead of a wildcard, leave the space blank to indicate that any numbers can be valid. There are no limits to the number of debug entries. The number entered generates a match if the calling or called number matches up to the final number of the debug entry. For example, the 408555 entry would match 408555, 4085551, 4085551212, or any other number starting with 408555.

Examples

The following command enables debugging for any incoming calls that start with 408555: Router# debug fax relay t30 calling-number 408555 Debugging fax relay t30 from 408555


DB-689

Debug Commands debug fax relay t30

The following command enables debugging for any calls received to a number starting with 555-1212: Router# debug fax relay t30 called-number 4155551212 Debugging fax relay t30 to 4155551212

The following command displays all debug entries: Router# debug fax relay t30 all Debugging fax relay t30 from 408555 Debugging fax relay t30 to 4155551212


DB-690

May 2008

Debug Commands debug fddi smt-packets

debug fddi smt-packets To display information about Station Management (SMT) frames received by the router, use the debug fddi smt-packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fddi smt-packets no debug fddi smt-packets

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug fddi smt-packets command. In this example, an SMT frame has been output by FDDI 1/0. The SMT frame is a next station addressing (NSA) neighbor information frame (NIF) request frame with the parameters as shown. Router# debug fddi smt-packets SMT O: Fddi1/0, FC=NSA, DA=ffff.ffff.ffff, SA=00c0.eeee.be04, class=NIF, type=Request, vers=1, station_id=00c0.eeee.be04, len=40 - code 1, len 8 -- 000000016850043F - code 2, len 4 -- 00010200 - code 3, len 4 -- 00003100 - code 200B, len 8 -- 0000000100000000


debug fddi smt-packets Field Descriptions

Field

Description

SMT O

SMT frame was sent from FDDI interface 1/0. Also, SMT I indicates that an SMT frame was received on the FDDI interface 1/0.

Fddi1/0

Interface associated with the frame.

FC

Frame control byte in the MAC header.

DA, SA

Destination and source addresses in FDDI form.

class

Frame class. Values can be echo frame (ECF), neighbor information frame (NIF), parameter management frame (PMF), request denied frame (RDF), status information frame (SIF), and status report frame (SRF).

type

Frame type. Values can be Request, Response, and Announce.

vers

Version identification. Values can be 1 or 2.

station_id

Station identification.


DB-691

Debug Commands debug fddi smt-packets

Table 94

debug fddi smt-packets Field Descriptions (continued)

Field

Description

len

Packet size.

code 1, len 8 -000000016850043F

Parameter type X’0001—upstream neighbor address (UNA), parameter length in bytes, and parameter value. SMT parameters are described in the SMT specification ANSI X3T9.


DB-692

May 2008

Debug Commands debug filesystem

debug filesystem To enable ATA ROM monitor library (monlib) debugging messages, use the debug filesystem command in privileged EXEC mode. To disable ATA monlib debugging messages, use the no form of this command. debug filesystem {disk0 | disk1} no debug filesystem {disk0 | disk1}

Syntax Description

disk0

Selects disk 0 as the disk on which to enable or disable debugging.

disk1

Selects disk 1 as the disk on which to enable or disable debugging.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(7)T


12.2(25)S


12.2(33)SRA


12.2SX


Usage Guidelines

The debug filesystem command enables the display of ATA monlib debugging messages during boot operations. To display the debugging messages when ROMMON accesses the PCMCIA disk, the ROMMON must have disk support. In other words, if a dev command is entered in ROMMON mode, the output should display the supported disks as shown in the following example: rommon 1> dev Devices in device table: id name bootflash: boot flash slot0: PCMCIA slot 0 slot1: PCMCIA slot 1 disk0: PCMCIA slot 0 disk1: PCMCIA slot 1 eprom: eprom

Examples

The following example shows how to enable ATA monlib debugging messages on disk 0, reboot the router to view ATA monlib debugging messages, and then disable ATA monlib debugging messages: Router# debug filesystem disk0 rommon 1> boot disk0:c7200-is-mz.123-5.7.PI3a Initializing ATA monitor library.......


DB-693


ATA_read_sector:dev = 0 ATA_data_xfer:1:dev = 0, command = 32, nsecs = 8, sector = 3, cyl_low = 0, cyl_high = 0, head = 171 ATA_read_sector:dev = 0, retval = 0 dfs_openfile:Using monlib version 2 dfs_openfile:Using version info 1 dfs_openfile:finding file.. /c7200-is-mz.123-5.7.PI3a ATA_read_sector:dev = 0 ATA_data_xfer:1:dev = 0, command = 32, nsecs = 1, sector = 15, cyl_low = 0, cyl_high = 0, head = 163 ATA_read_sector:dev = 0, retval = 0 ATA_read_sector:dev = 0 ATA_data_xfer:1:dev = 0, command = 32, nsecs = 128, sector = 35, cyl_low = 0, cyl_high = 0, head = 171 ATA_read_sector:dev = 0, retval = 0 dfs_openfile:opened file.. /c7200-is-mz.123-5.7.PI3a with fd = 0 DFSLIB_read:reading file.. fd = 0, byte_count = 4 DFSLIB_read:read from.. fd = 0, byte_count = 4, retval = 4 DFSLIB_read:reading file.. fd = 0, byte_count = 52 DFSLIB_read:read from.. fd = 0, byte_count = 52, retval = 52 DFSLIB_read:reading file.. fd = 0, byte_count = 40 DFSLIB_read:read from.. fd = 0, byte_count = 40, retval = 40 . . . DFSLIB_read:reading file.. fd = 0, byte_count = 40 DFSLIB_read:read from.. fd = 0, byte_count = 40, retval = 40 DFSLIB_read:reading file.. fd = 0, byte_count = 19539160 ATA_read_sector:dev = 0 ATA_data_xfer:1:dev = 0, command = 32, nsecs = 1, sector = 15, cyl_low = 0, cyl_high = 0, head = 163 ATA_read_sector:dev = 0, retval = 0 ATA_read_sector:dev = 0 . . . ATA_read_sector:dev = 0 ATA_data_xfer:1:dev = 0, command = 32, nsecs = 19, sector = 1, cyl_low = 38, cyl_high = 0, head = 169 ATA_read_sector:dev = 0, retval = 0 DFSLIB_read:read from.. fd = 0, byte_count = 19539160, retval = 19539160 Self decompressing the image :##################################################################### ########################################################################################## ########## ############################################################### [OK] Router# no debug filesystem disk0


debug filesystem Field Descriptions

Field

Description

dev =

The number of the device being accessed.

command =

The operation that is being executed.

nsecs =

The number of sectors on the device.

sector =

The starting sector.

cyl_low =, cyl_high =

The starting cylinder, low and high.


DB-694

May 2008


Table 95

debug filesystem Field Descriptions (continued)

Field

Description

head =

The head number.

retval =

The status of the operation being executed.


DB-695

Debug Commands debug flow exporter

debug flow exporter To enable debugging output for Flexible NetFlow flow exporters, use the debug flow exporter command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug flow exporter [[name] exporter-name] [error] [event] [packets number] no debug flow exporter [[name] exporter-name] [error] [event] [packets number]

Syntax Description

name exporter-name

(Optional) The name of a flow exporter that you previously configured.

error

(Optional) Enables debugging for flow exporter errors.

event

(Optional) Enables debugging for flow exporter events.

packets

(Optional) Enables packet level debugging for flow exporters.

number

(Optional) Configures the number of packets to debug for packet level debugging of flow exporters.

Command Default

Debugging output for Flexible NetFlow flow exporters is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T


12.2(31)SB2


12.2SX


Usage Guidelines

You must have already enabled traffic monitoring with Flexible NetFlow using an exporter before you can use the debug flow exporter command.

Examples

The following example indicates that a flow exporter packet has been queued for process send:

Router# debug flow exporter May 21 21:29:12.603: FLOW EXP: Packet queued for process send

Related Commands

Command

Description

clear flow exporter

Clears the Flexible NetFlow statistics for exporters.

debug flow exporter

Enables debugging output for Flexible NetFlow flow exporters.


DB-696

May 2008

Debug Commands debug flow exporter

Command

Description

destination

Configures an export destination for Flexible NetFlow flow exporters.

dscp

Configure optional DSCP parameters for Flexible NetFlow flow exporters.

flow exporter

Creates a Flexible NetFlow flow exporter.

export-protocol

Configures the export protocol version for Flexible NetFlow flow exporters.

option

Configure options for Flexible NetFlow flow exporters.

show flow exporter

Displays Flexible NetFlow flow exporter status and statistics.

source

Configures the source IP address interface for Flexible NetFlow flow exporters.

template

Configures the template resend timeout for Flexible NetFlow flow exporters.

transport

Configures the transport protocol for Flexible NetFlow flow exporters.

ttl

Configures the TTL value for Flexible NetFlow flow exporters.


DB-697

Debug Commands debug flow monitor

debug flow monitor To enable debugging output for Flexible NetFlow flow monitors, use the debug flow monitor command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug flow monitor [error] [{[name] monitor-name [cache] [error] [packets packets]}] no debug flow monitor [error] [{[name] monitor-name [cache] [error] [packets packets]}]

Syntax Description

name monitor-name

(Optional) The name of a flow monitor that you previously configured.

cache

(Optional) Enables debugging for the flow monitor cache.

error

(Optional) Enables debugging for flow monitor errors.

packets

(Optional) Enables packet level debugging for flow monitors.

packets

(Optional) The number of packets to debug for packet-level debugging of flow monitors.

Command Default

Debugging output for Flexible NetFlow flow monitors is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T


12.2(31)SB2


12.2SX


Usage Guidelines

You must have already enabled traffic monitoring with Flexible NetFlow before you can use the debug flow monitor command.

Examples

The following example shows that the cache for FLOW-MONITOR-1 was deleted:

Router# debug flow monitor FLOW-MONITOR-1 cache May 21 21:53:02.839: FLOW MON: 'FLOW-MONITOR-1' deleted cache

Related Commands

Command

Description

cache

Configures flow cache parameters for Flexible NetFlow flow monitors.

clear flow monitor

Clears the Flexible NetFlow flow monitor.

debug flow monitor

Enables debugging output for Flexible NetFlow flow monitors.


DB-698

May 2008

Debug Commands debug flow monitor

Command

Description

exporter

Specifies a flow exporter for Flexible NetFlow flow monitors.

flow monitor

Creates a Flexible NetFlow flow monitor.

protocol-distribution

Configures the collection of protocol distribution statistics for Flexible NetFlow flow monitors.

record

Configures a flow record a for Flexible NetFlow flow monitor.

show flow monitor

Displays Flexible NetFlow flow monitor status and statistics.

size-distribution

Configures the collection of size distribution statistics for Flexible NetFlow flow monitors.


DB-699

Debug Commands debug flow record

debug flow record To enable debugging output for Flexible NetFlow flow records, use the debug flow record command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug flow record [[name] record-name | netflow-original] | netflow ipv4 record [peer] | options {{exporter-statistics | interface-table | sampler-table} [detailed | error]}] no debug flow record [[name] record-name | netflow-original] | netflow ipv4 record [peer] | options {{exporter-statistics | interface-table | sampler-table} [detailed | error]}]

Syntax Description

name record-name

(Optional) The name of a flow record that you previously configured.

netflow-original

(Optional) Traditional IPv4 input NetFlow with origin autonomous systems.

netflow ipv4 record

(Optional) The name of the NetFlow predefined record that you want to run debugging on. See Table 96.

peer

(Optional) Includes peer information for the NetFlow predefined records that support the peer keyword. Note

The peer keyword is not supported for every type of NetFlow predefined record. See Table 96.

options

(Optional) Includes information on other flow record options.

exporter-statistics

(Optional) Information on the flow exporter statistics.

interface-table

(Optional) Information on the interface tables.

sampler-table

(Optional) Information on the sampler tables.

detailed

(Optional) Show detailed information.

error

(Optional) Only show errors.

Command Default

Debugging output for Flexible NetFlow flow records is disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T


12.2(31)SB2


12.2SX



DB-700

May 2008


Usage Guidelines

You must have already enabled traffic monitoring with Flexible NetFlow before you can use the debug flow record command. Keywords and Descriptions for the record Argument

Table 96 describes the keywords and descriptions for the record argument. Table 96

Keywords and Descriptions for the record Argument

as

Autonomous system record.

as-tos

Autonomous systems and TOS record.

bgp-nexthop-tos

BGP next-hop and TOS record.

destination-prefix

Destination Prefix record.

destination-prefix-tos

Destination Prefix and TOS record.

original-input

Traditional IPv4 input NetFlow.

original-output

Traditional IPv4 output NetFlow.

prefix

Source and Destination Prefixes record.

prefix-port

Prefix Port record. Note

The peer keyword is not available for this record.

prefix-tos

Prefix TOS record.

protocol-port

Protocol Ports record. Note

protocol-port-tos


Protocol Port and TOS record. Note


source-prefix

Source AS and Prefix record.

source-prefix-tos

Source Prefix and TOS record.

Examples

There are no examples available for this command.

Related Commands

Command

Description

collect counter

Configures the counters as a non-key field and collect the counter values.

collect flow

Configures flow identifying fields as a non-key fields and collect their values.

collect interface

Configure the input and/or output interface as a non-key field and collect the values.

collect ipv4

Configures an IPv4 field as a non-key field and collect the value in it.

collect routing

Configures a routing attribute as a non-key field and collect the value of the field.

collect timestamp

Configures the timestamp fields as a non-key field and collect the values.

collect transport

Configures a transport layer field as a non-key field and collect the values.

debug flow record

Enables debugging output for Flexible NetFlow flow records.


DB-701


Command

Description

flow record

Create a Flexible NetFlow flow record.

match flow

Configures one or more of the flow fields as key fields.

match interface

Configures the direction that traffic flows in respect to an interface (interface field) as a key field.

match ipv4

Configures one or more of the IPv4 fields as a key field.

match routing

Configures one or more of the routing fields as a key field.

match timestamp

Configures a timestamp field as a key field.

match transport

Configures one or more of the transport fields as a key field.

show flow record

Displays Flexible NetFlow flow record status and statistics.


DB-702

May 2008

Debug Commands debug flow-sampler

debug flow-sampler To enable debugging output for NetFlow sampler activity, use the debug flow-sampler command in privileged EXEC mode. To disable debugging output for NetFlow sampler activity, use the no form of this command. debug flow-sampler {class-based | events | ipc | match} no debug flow-sampler {class-based | events | ipc | match}

Syntax Description

class-based

Displays debug messages for class-based NetFlow samplers.

events

Displays debug messages when a NetFlow sampler map is added, deleted, or applied to an interface.

ipc

Displays NetFlow sampler-related debug messages for interprocess communications (IPC) between the route processor and line cards.

match

Displays debug messages when a packet is sampled (is matched with a NetFlow sampler).

Command Default

Debugging output for NetFlow sampler activity is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(2)T


12.2(18)S


12.0(26)S


12.3(4)T

The class-based keyword was added.

12.2(27)SBC


12.2(33)SRA


12.2SX


Usage Guidelines

Because debugging output is assigned high priority in the CPU process, you should use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, you should use debug commands during periods of lower network traffic and fewer users. Debugging during these periods reducess the likelihood that increased debug command processing overhead will affect system use.

Examples

The following is sample output from the debug flow-sampler events command:


DB-703

Debug Commands debug flow-sampler

Router# debug flow-sampler events Flow sampler events debugging is on Router# configure terminal Router(config# no flow-sampler mysampler2 Router(config)# 5d00h: Flow: Sampler mysampler2 detached from FastEthernet0/1 5d00h: Flow: Sampler mysampler2 deleted

The following is sample output from the debug flow-sampler match command: Router# debug flow-sampler match Flow sampler Router# 4d23h: Flow: Router# 4d23h: Flow: Router# 4d23h: Flow: Router# 4d23h: Flow:

match debugging is on Packet matched sampler mysampler1 on interface FastEthernet0/0 Packet matched sampler mysampler1 on interface FastEthernet0/0 Packet matched sampler mysampler1 on interface FastEthernet0/0 Packet matched sampler mysampler1 on interface FastEthernet0/0


Related Commands

debug flow-sampler Field Descriptions

Field

Description

Sampler

Name of the NetFlow sampler.

id

Unique ID of the NetFlow sampler.

packets matched

Number of packets matched (sampled) for the NetFlow sampler.

mode

NetFlow sampling mode.

sampling interval is

NetFlow sampling interval (in packets).

Command

Description

flow-sampler

Enables a Random Sampled NetFlow sampler.

flow-sampler-map

Defines a Random Sampled NetFlow sampler map.

ip flow-export

Enables the export of NetFlow data to a collector.

mode (flow sampler map) Specifies a Random Sampled NetFlow sampling mode and sampling rate. netflow-sampler

Enables a class-based NetFlow sampler.

show flow-sampler

Displays attributes (including mode, sampling rate, and number of sampled packets) of one or all Random Sampled NetFlow samplers.

show ip flow export

Displays the statistics for the NetFlow data export.


DB-704

May 2008

Debug Commands debug fm private-hosts

debug fm private-hosts To enable debug messages for the Private Hosts feature manager, use the debug fm private-hosts command in privileged EXEC mode. debug fm private-hosts {all | vmr | unusual | events}

Syntax Description

all

Enable debug messages for all Private Hosts errors and events.

vmr

Enable debug messages for the Multicast VLAN Registration (MVR) feature.

unusual

Enable debug messages for unexpected Private Hosts behavior.

events

Enable debug messages for Private Hosts events.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRB


12.2SX


Examples

The following example shows sample command output: Router# debug fm fm private-hosts fm private-hosts fm private-hosts Router#

Related Commands

private-hosts all vmr debugging is on unusual debugging is on events debugging is on

Command

Description

debug private-hosts

Enables debug messages for Private Hosts.


DB-705

Debug Commands debug fmsp receive

debug fmsp receive Note

Effective with release 12.3(8)T, the debug fmsp receive command is replaced by the debug fax fmsp command. See the debug fax fmsp command for more information. To display debugging messages for Fax Media Services Provider (FMSP) receive, use the debug fmsp receive command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fmsp receive [t30 | t38] no debug fmsp receive [t30 | t38]

Syntax Description

t30

(Optional) Specifies the T.30 fax protocol.

t38


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI


12.2(8)T

This command was implemented on the Cisco 1751 access routers, Cisco 3725 access routers, and Cisco 3745 access routers.

12.2(13)T

Support for this command was implemented in Cisco 7200 series images.

12.3(8)T

This command was replaced by the debug fax fmsp command.

Examples

12.2(33)SRA


12.2SX


The following is sample output from the debug fmsp receive command: Router# debug fmsp receive *Oct 16 08:31:33.243: faxmsp_call_setup_request: call id=28 *Oct 16 08:31:33.243: faxmsp_call_setup_request: ramp data dir=ONRAMP, conf dir=DEST *Oct 16 08:31:33.243: faxmsp_bridge(): cfid=19, srccid=28, dstcid=27 *Oct 16 08:31:33.243: faxmsp_bridge(): ramp data dir=ONRAMP, conf dir=DEST *Oct 16 08:31:33.243: faxmsp_bridge(): Explicit caps ind. done; will wait for registry caps ind


DB-706

May 2008

Debug Commands debug fmsp receive

Related Commands

*Oct *Oct *Oct *Oct *Oct

16 16 16 16 16

08:31:33.243: 08:31:33.243: 08:31:33.279: 08:31:33.279: 08:31:33.283:

*Oct *Oct caps *Oct *Oct *Oct *Oct *Oct *Oct *Oct

16 08:31:33.283: 16 08:31:33.283: ind 16 08:31:33.283: 16 08:31:33.283: 16 08:31:33.635: 16 08:31:33.635: 16 08:31:33.643: 16 08:31:33.643: 16 08:31:33.643:

faxmsp_caps_ind: call id=28, src=27 faxmsp_caps_ack: call id src=27 faxmsp_call_setup_request: call id=29 faxmsp_call_setup_request: ramp data dir=OFFRAMP, conf dir=SRC faxmsp_bridge(): cfid=20, srccid=29, dstcid=26 faxmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC faxmsp_bridge(): Explicit caps ind. done; will wait for registry faxmsp_caps_ind: call id=29, src=26 faxmsp_caps_ack: call id src=26 faxmsp_codec_download_done: call id=29 faxmsp_codec_download_done: call id=28 faxmsp_xmit: callid src=26, dst=29 faxmsp_xmit: callid src=27, dst=28 faxmsp_process_rcv_data: call id src=26, dst=29

Command

Description

debug fmsp send

Displays debugging messages for FMSP send.


DB-707

Debug Commands debug fmsp send

debug fmsp send Note

Effective with release 12.3(8)T, the debug fmsp send command is replaced by the debug fax fmsp command. See the debug fax fmsp command for more information. To display debugging messages for Fax Media Services Provider (FMSP) send, use the debug fmsp send command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug fmsp send [t30 | t38] no debug fmsp send [t30 | t38]

Syntax Description

t30


t38


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI


12.2(8)T


12.2(13)T

This feature was implemented on the Cisco 7200 series routers.

12.3(8)T

This command was replaced by the debug fax fmsp command.

Examples

12.2(33)SRA


12.2SX


The following is sample output from the debug fmsp send command: Router# debug fmsp send Jan Jan Jan

1 05:02:56.782: faxmsp_call_setup_request: call id=21 1 05:02:56.782: faxmsp_call_setup_request: ramp data dir=OFFRAMP, conf dir=SRC 1 05:02:56.782: faxmsp_bridge(): cfid=7, srccid=21, dstcid=20

Jan Jan ind Jan Jan Jan

1 05:02:56.782: faxmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC 1 05:02:56.782: faxmsp_bridge(): Explicit caps ind. done; will wait for registry caps 1 05:02:56.782: faxmsp_caps_ind: call id=21, src=20 1 05:02:56.782: faxmsp_caps_ack: call id src=20 1 05:02:57.174: faxmsp_codec_download_done: call id=21


DB-708

May 2008

Debug Commands debug fmsp send

Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan

Related Commands

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

05:02:57.174: 05:02:57.178: 05:02:57.178: 05:02:57.178: 05:02:57.182: 05:02:57.182: 05:03:01.814: 05:03:01.814: 05:03:01.814: 05:03:02.802: 05:03:02.802: 05:03:02.822: 05:03:02.822: 05:03:02.854: 05:03:02.854:

faxMsp_tx_buffer callID=21 faxMsp_tx_buffer callID=21 faxMsp_tx_buffer callID=21 faxMsp_tx_buffer callID=21 faxmsp_xmit: callid src=20, dst=21 faxmsp_process_rcv_data: call id src=20, faxmsp_xmit: callid src=20, dst=21 faxmsp_process_rcv_data: call id src=20, faxMsp_tx_buffer callID=21 faxmsp_xmit: callid src=20, dst=21 faxmsp_process_rcv_data: call id src=20, faxmsp_xmit: callid src=20, dst=21 faxmsp_process_rcv_data: call id src=20, faxmsp_xmit: callid src=20, dst=21 faxmsp_process_rcv_data: call id src=20,

dst=21 dst=21

dst=21 dst=21 dst=21

Command

Description

debug fax relay t30

Displays debugging messages for FMSP receive.


DB-709

Debug Commands debug foip off-ramp

debug foip off-ramp Note

Effective with release 12.3(8)T, the debug foip off-ramp command is replaced by the debug fax foip command. See the debug fax foip command for more information. To display debugging messages for off-ramp fax mail, use the debug foip off-ramp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug foip off-ramp no debug foip off-ramp

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI


12.2(8)T

This command was introduced on the Cisco 1751 access routers, Cisco 3725 access routers, and Cisco 3745 access routers.

12.2(13)T


12.3(8)T

This command was replaced by the debug fax foip command.

12.2SX


Examples

The following is sample output from the debug foip off-ramp command: Router# debug foip off-ramp Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan

1 1 1 1 1 1 1 1 1 1 1 1 1

02:31:17.539: 02:31:17.539: 02:31:17.543: 02:31:17.543: 02:31:22.867: 02:31:22.867: 02:31:22.867: 02:31:22.867: 02:31:22.867: 02:31:22.867: 02:31:22.867: 02:31:30.931: 02:31:30.931:

lapp off: CC_EV_CALL_HANDOFF, cid(0xB) loffHandoff: called number=5271714, callid=0xB loffSetupPeer: cid1(0xB) destPat(5271714),matched(1),pref(5),tag(20),encap(1) lapp off: CC_EV_CALL_CONNECTED, cid(0xC) st=CALL_SETTING cid(0xB,0x0,0x0,0xC),cfid(0x0,0x0,0x0) loffConnected loffFlushPeerTagQueue cid(11) peer list: (empty) lapp off: CC_EV_CONF_CREATE_DONE, cid(0xC), cid2(0xD), cfid(0x1) st=CONFERENCING3 cid(0xB,0x0,0xD,0xC),cfid(0x0,0x0,0x1) loffConfDone3 lapp off: CC_EV_FROM_FMSP_ON_CALL_DETAIL, cid(0xD) st=WAIT_SESS_INFO cid(0xB,0x0,0xD,0xC),cfid(0x0,0x0,0x1)


DB-710

May 2008

Debug Commands debug foip off-ramp

Jan Jan Jan Jan Jan

Related Commands

1 1 1 1 1

02:31:30.931: loffSessionInfo 02:31:30.931: encd=2, resl=2, spd=26, min_scan_len=0, csid= 4085271714 02:31:30.931: lapp off: CC_EV_CONF_CREATE_DONE, cid(0xD), cid2(0xE), cfid(0x2) 02:31:30.931: st=CONFERENCING2 cid(0xB,0xE,0xD,0xC),cfid(0x0,0x2,0x1) 02:31:30.931: loffConfDone2

Command

Description

debug foip on-ramp

Displays debugging messages for on-ramp fax mail.


DB-711

Debug Commands debug foip on-ramp

debug foip on-ramp Note

Effective with release 12.3(8)T, the debug foip on-ramp command is replaced by the debug fax foip command. See the debug fax foip command for more information. To display debugging messages for on-ramp fax mail, use the debug foip on-ramp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug foip on-ramp no debug foip on-ramp

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI


12.2(8)T

This command was introduced on the Cisco 1751 access routers, Cisco 3725 access routers, and Cisco 3745 access routers.

12.2(13)T


12.3(8)T

This command was replaced by the debug fax foip command.

12.2SX


Examples

The following is sample output from the debug foip on-ramp command: Router# debug foip on-ramp *Oct 16 08:07:01.947: CID(11), DISP(0) *Oct 16 08:07:01.947: *Oct 16 08:07:01.947: *Oct 16 08:07:01.947: *Oct 16 08:07:01.947: *Oct 16 08:07:01.947: *Oct 16 08:07:01.947: *Oct 16 08:07:01.947: *Oct 16 08:07:01.951: *Oct 16 08:07:01.951: CID(11), DISP(0) *Oct 16 08:07:01.951:

lapp_on_application: Incoming Event: (15 = CC_EV_CALL_HANDOFF), lapp_on_call_handoff: Authentication enabled = FALSE lapp_on_call_handoff: Authentication ID = 0 lapp_on_call_handoff: Authentication ID source = IVR or unknown lapp_on_call_handoff: Authentication status = SUCCESS lapp_on_call_handoff: Accounting enabled = FALSE lapp_on_call_handoff: Accounting method list = fax lapp_on_conference_vtsp_fmsp: Begin conferencing VTSP and FMSP... lapp_on_change_state: old state(0) new state(1) lapp_on_application: Incoming Event: (29 = CC_EV_CONF_CREATE_DONE), lapp_on_application: Current call state = 1


DB-712

May 2008

Debug Commands debug foip on-ramp

*Oct 16 08:07:01.951: lapp_on_conference_created: The VTSP and the FMSP are conferenced *Oct 16 08:07:01.951: lapp_on_conference_created: Wait for FMSP call detail event

Related Commands

Command

Description

debug foip off-ramp

Displays debugging messages for off-ramp fax mail.


DB-713

Debug Commands debug fpm event

debug fpm event To display protocol information from the designated protocol header description field (PHDF), use the debug fpm event command in privileged EXEC mode. To disable debugging messages, use the no form of this command. debug fpm event no debug fpm event

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(4)T


12.2(18)ZY

This command was integrated into Cisco IOS Release 12.2(18)ZY on the Catalyst 6500 series of switches equipped with the Programmable Intelligent Services Accelerator (PISA).

12.2SX


Examples

The following sample output is from the debug fpm event command: Router# debug fpm event *Jun 21 09:22:21.607: policy-classification-inline(): matches class: class-default *Jun 21 09:22:21.607: packet-access-control(): policy-map: fpm-policy, dir: input, match. retval: 0x0, ip-flags: 0x80000000


DB-714

May 2008

Debug Commands debug frame-relay adjacency

debug frame-relay adjacency To display information pertaining to an adjacent node that has one or more Frame Relay permanent virtual circuit (PVC) bundles, use the debug frame-relay adjacency command in privileged EXEC mode. To stop displaying the adjacent node information, use the no form of this command. debug frame-relay adjacency {pvc [dlci] | vc-bundle [vc-bundle-name]} no debug frame-relay adjacency {pvc [dlci] | vc-bundle [vc-bundle-name]}

Syntax Description

pvc

Displays information regarding the adjacent PVC only.

dlci

(Optional) Data-link connection identifier for a specific PVC.

vc-bundle

Displays information regarding the adjacent PVC bundle and its members.

vc-bundle-name

(Optional) Name of the PVC bundle.

Defaults

No default behaviors or values.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T


12.2(28)SB


12.2SX


Usage Guidelines

Note

Use this command to monitor adjacency activity and status for an adjacent node.

Debug messages that are prefixed with “FR_ADJ” (instead of “FR-ADJ”) indicate serious failures in the Frame Relay PVC bundle performance. Contact the Cisco Technical Assistance Center (TAC) if you see debugging messages with this prefix.


DB-715

Debug Commands debug frame-relay adjacency

Examples

The following sample output from the debug frame-relay adjacency vc-bundle command shows PVC bundle “MP-4-dynamic” going down. Each bundle member PVC is marked for removal from the CEF adjacency table, and then the adjacency for the PVC bundle itself is marked for removal. The adjacencies are actually removed from the table later when a background clean-up process runs. Router# debug frame-relay adjacency vc-bundle MP-4-dynamic 00:46:35: 00:46:35: 00:46:35: 00:46:35: 00:46:35: 00:46:35: 00:46:35: 00:46:35: 00:46:35:

Related Commands

FR-ADJ: FR-ADJ: FR-ADJ: FR-ADJ: FR-ADJ: FR-ADJ: FR-ADJ: FR-ADJ: FR-ADJ:

vcb vcb vcb vcb vcb vcb vcb vcb vcb

MP-4-dynamic: MP-4-dynamic: MP-4-dynamic: MP-4-dynamic: MP-4-dynamic: MP-4-dynamic: MP-4-dynamic: MP-4-dynamic: MP-4-dynamic:

ip ip ip ip ip ip ip ip ip

10.2.2.2: 10.2.2.2: 10.2.2.2: 10.2.2.2: 10.2.2.2: 10.2.2.2: 10.2.2.2: 10.2.2.2: 10.2.2.2:

member 400: removing member 401: removing member 402: removing member 403: removing member 404: removing member 405: removing member 406: removing member 407: removing removing primary adj

adj adj adj adj adj adj adj adj

Command

Description

debug frame-relay vc-bundle

Displays information pertaining to all the PVC bundles configured on the router.


DB-716

May 2008

Debug Commands debug frame-relay callcontrol

debug frame-relay callcontrol To display Frame Relay Layer 3 (network layer) call control information, use the debug frame-relay callcontrol command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug frame-relay callcontrol no debug frame-relay callcontrol

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug frame-relay callcontrol command is used specifically for observing FRF.4/Q.933 signalling messages and related state changes. The FRF.4/Q.933 specification describes a state machine for call control. The signalling code implements the state machine. The debug statements display the actual event and state combinations. The Frame Relay switched virtual circuit (SVC) signalling subsystem is an independent software module. When used with the debug frame-relay networklayerinterface command, the debug frame-relay callcontrol command provides a better understanding of the call setup and teardown sequence. The debug frame-relay networklayerinterface command provides the details of the interactions between the signalling subsystem on the router and the Frame Relay subsystem.

Examples

State changes can be observed during a call setup on the calling party side. The debug frame-relay networklayerinterface command shows the following state changes or transitions: STATE_NULL -> STATE_CALL_INITIATED -> STATE_CALL_PROCEEDING->STATE_ACTIVE

The following messages are samples of output generated during a call setup on the calling side: 6d20h: U0_SetupRequest: Serial0 6d20h: L3SDL: Ref: 1, Init: STATE_NULL, Rcvd: SETUP_REQUEST, Next: STATE_CALL_INITIATED 6d20h: U1_CallProceeding: Serial0 6d20h: L3SDL: Ref: 1, Init: STATE_CALL_INITIATED, Rcvd: MSG_CALL_PROCEEDING, Next: STATE_CALL_PROCEEDING 6d20h: U3_Connect: Serial0 6d20h: L3SDL: Ref: 1, Init: STATE_CALL_PROCEEDING, Rcvd: MSG_CONNECT, Next: STATE_ACTIVE 6d20h:

The following messages are samples of output generated during a call setup on the called party side. Note the state transitions as the call goes to the active state: STATE_NULL -> STATE_CALL_PRESENT-> STATE_INCOMING_CALL_PROCEEDING->STATE_ACTIVE 1w4d: U0_Setup: Serial2/3 1w4d: L3SDL: Ref: 32769, Init: STATE_NULL, Rcvd: MSG_SETUP, Next: STATE_CALL_PRESENT 1w4d: L3SDL: Ref: 32769, Init: STATE_CALL_PRESENT, Rcvd: MSG_SETUP, Next: STATE_INCOMING_CALL_PROC 1w4d: L3SDL: Ref: 32769, Init: STATE_INCOMING_CALL_PROC, Rcvd: MSG_SETUP, Next: STATE_ACTIVE


DB-717

Debug Commands debug frame-relay callcontrol

Table 98 explains the possible call states. Table 98

Frame Relay Switched Virtual Circuit Call States

Call State

Description

Null

No call exists.

Call Initiated

User has requested the network to establish a call.

Outgoing Call Proceeding

User has received confirmation from the network that the network has received all call information necessary to establish the call.

Call Present

User has received a request to establish a call but has not yet responded.

Incoming Call Proceeding

User has sent acknowledgment that all call information necessary to establish the call has been received (for an incoming call).

Active

On the called side, the network has indicated that the calling user has been awarded the call. On the calling side, the remote user has answered the call.

Related Commands

Disconnect Request

User has requested that the network clear the end-to-end call and is waiting for a response.

Disconnect Indication

User has received an invitation to disconnect the call because the network has disconnected the call.

Release Request

User has requested that the network release the call and is waiting for a response.

Command

Description

debug fax relay t30

Displays debugging information about the packets that are received on a Frame Relay interface.

debug frame-relay networklayerinterface

Displays NLI information.


DB-718

May 2008

Debug Commands debug frame-relay end-to-end keepalive

debug frame-relay end-to-end keepalive To display debug messages for the Frame Relay End-to-End Keepalive feature, use the debug frame-relay end-to-end keepalive command. Use the no form of this command to disable the display of debug messages. debug frame-relay end-to-end keepalive {events | packet} no debug frame-relay end-to-end keepalive {events | packet}

Syntax Description

Command History

events

Displays keepalive events.

packet

Displays keepalive packets sent and received.

Release

Modification

12.0(5)T


12.2(33)SRA


12.2SX


Usage Guidelines

We recommend that both commands be enabled.

Examples

The following examples show typical output from the debug frame-relay end-to-end keepalive packet command. The following example shows output for an outgoing request packet: EEK (o, Serial0.1 DLCI 200): 1 1 1 3 2 4 3

The seven number fields that follow the colon signify the following: Field

Description

first (example value = 1)

Information Element (IE) type.

second (example value = 1)

IE length.

third (example value = 1)

Report ID. 1 = request, 2 = reply.

fourth (example value = 3)

Next IE type. 3 = LIV ID (Keepalive ID).

fifth (example value = 2)

IE length. (This IE is a Keepalive IE.)

sixth (example value = 4)

Send sequence number.

seventh (example value = 3)

Receive sequence number.


DB-719

Debug Commands debug frame-relay end-to-end keepalive

The following example shows output for an incoming reply packet: EEK (i, Serial0.1 DLCI 200): 1 1 2 3 2 4 4

The seven number fields that follow the colon signify the following: Field

Description

first (example value = 1)

Information Element (IE) type.

second (example value = 1)

IE length.

third (example value = 2)

Report ID. 1 = request, 2 = reply.

fourth (example value = 3)

Next IE type. 3 = LIV ID (Keepalive ID).

fifth (example value = 2)

IE length. (This IE is a Keepalive IE.)

sixth (example value = 4)

Send sequence number.

seventh (example value = 4)

Receive sequence number.

The following example shows typical output from the debug frame-relay end-to-end keepalive events command: EEK SUCCESS (request, Serial0.2 DLCI 400) EEK SUCCESS (reply, Serial0.1 DLCI 200) EEK sender timeout (Serial0.1 DLCI 200)


DB-720

May 2008

Debug Commands debug frame-relay events

debug frame-relay events To display debugging information about Frame Relay Address Resolution Protocol (ARP) replies on networks that support a multicast channel and use dynamic addressing, use the debug frame-relay events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug frame-relay events no debug frame-relay events

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3


12.0(23)S

This command was integrated into Cisco IOS Release 12.0(23)S for the Frame Relay over MPLS feature.

12.2(14)S


12.2(15)T


12.2(33)SRA


12.2SX


Usage Guidelines

Note

Examples

This command is useful for identifying the cause of end-to-end connection problems during the installation of a Frame Relay network or node.

Because the debug frame-relay events command does not generate much output, you can use it at any time, even during periods of heavy traffic, without adversely affecting other users on the system.

The following is sample output from the debug frame-relay events command: Router# debug frame-relay events Serial2(i): Serial2(i): Serial2(i): Serial2(i): Serial2(i): Serial2(i):

reply reply reply reply reply reply

rcvd rcvd rcvd rcvd rcvd rcvd

172.16.170.26 172.16.170.28 172.16.170.34 172.16.170.38 172.16.170.41 172.16.170.65

126 128 134 144 228 325


DB-721


As the output shows, the debug frame-relay events command returns one specific message type. The first line, for example, indicates that IP address 172.16.170.26 sent a Frame Relay ARP reply; this packet was received as input on serial interface 2. The last field (126) is the data-link connection identifier (DLCI) to use when communicating with the responding router. For Frame Relay over MPLS, the following is sample output for the debug frame-relay events command. The command output shows the status of the VCs. Router# debug frame-relay events Frame Relay events debugging is on

This example shows the messages that are displayed when you shut the core-facing interface on a provider edge (PE) router: 04:40:38:%SYS-5-CONFIG_I: Configured from console by consolenf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface hssi2/0 Router(config-if)# shut 04:40:43:%OSPF-5-ADJCHG: Process 10, Nbr 12.12.12.12 on Hssi2/0 from FULL to DOWN, Neighbor Down: Interface down or detached 04:40:43: FRoMPLS [12.12.12.12, 100]: PW pvc_status set INACTIVE 04:40:43: FRoMPLS [12.12.12.12, 100]: Setting pw segment DOWN 04:40:43: FRoMPLS [12.12.12.12, 100]: Setting connection DOWN 04:40:43: FRoMPLS [12.12.12.12, 101]: PW pvc_status set INACTIVE 04:40:43: FRoMPLS [12.12.12.12, 101]: Setting pw segment DOWN 04:40:43: FRoMPLS [12.12.12.12, 101]: Setting connection DOWN 04:40:45:%LINK-5-CHANGED: Interface Hssi2/0, changed state to administratively down 04:40:46:%LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi2/0, changed state to down

This example shows the messages that are displayed when you enable the core-facing interface on a PE router: Router(config-if)# no shut 04:40:56:%LINK-3-UPDOWN: Interface Hssi2/0, changed state to up 04:40:57:%LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi2/0, changed state to up 04:41:06:%OSPF-5-ADJCHG: Process 10, Nbr 12.12.12.12 on Hssi2/0 from LOADING to FULL, Loading Done 04:41:19: FRoMPLS [12.12.12.12, 100]: PW pvc_status set ACTIVE 04:41:19: FRoMPLS [12.12.12.12, 100]: Setting pw segment UP 04:41:19: FRoMPLS [12.12.12.12, 101]: PW pvc_status set ACTIVE 04:41:19: FRoMPLS [12.12.12.12, 101]: Setting pw segment UP

This example shows the messages that are displayed when you shut the edge-facing interface on a PE router: Router(config)# interface pos4/0 Router(config-if)# shut 04:42:50: FRoMPLS [12.12.12.12, 100]: acmgr_circuit_down 04:42:50: FRoMPLS [12.12.12.12, 100]: Setting connection DOWN 04:42:50: FRoMPLS [12.12.12.12, 100]: PW pvc_status set INACTIVE 04:42:52:%LINK-5-CHANGED: Interface POS4/0, changed state to administratively down 04:42:53:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS4/0, changed state to down

This example shows the messages that are displayed when you enable the edge-facing interface on a PE router: Router(config)# interface pos4/0 Router(config-if)# no shut 04:43:20:%LINK-3-UPDOWN: Interface POS4/0, changed state to up


DB-722

May 2008


c72-33-2(config-if)# 04:43:20: FRoMPLS [12.12.12.12, 04:43:20: FRoMPLS [12.12.12.12, 04:43:20: FRoMPLS [12.12.12.12, 04:43:20: FRoMPLS [12.12.12.12,

100]: 100]: 100]: 100]:

Local up, sending acmgr_circuit_up PW nni_pvc_status set ACTIVE PW pvc_status set ACTIVE Setting pw segment UP


DB-723

Debug Commands debug frame-relay foresight

debug frame-relay foresight To observe Frame Relay traces relating to traffic shaping with router ForeSight enabled, use the debug frame-relay foresight command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug frame-relay foresight no debug frame-relay foresight

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output that shows the display message returned in response to the debug frame-relay foresight command: Router# debug frame-relay foresight FR rate control for DLCI 17 due to ForeSight msg

This message indicates the router learned from the ForeSight message that data-link connection identifier (DLCI) 17 is now experiencing congestion. The output rate for this circuit should be slowed down, and in the router this DLCI is configured to adapt traffic shaping in response to foresight messages.

Related Commands

Command

Description

show frame-relay pvc

Displays statistics about PVCs for Frame Relay interfaces.


DB-724

May 2008

Debug Commands debug frame-relay fragment

debug frame-relay fragment To display information related to Frame Relay fragmentation on a permanent virtual circuit (PVC), use the debug frame-relay fragment command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug frame-relay fragment [event | interface type number dlci] no debug frame-relay fragment [event | interface type number dlci]

Syntax Description

event

(Optional) Displays event or error messages related to Frame Relay fragmentation.

interface

(Optional) Displays fragments received or sent on the specified interface.

type

(Optional) The interface type for which you wish to display fragments received or sent.

number

(Optional) The Interface number.

dlci

(Optional) The data-link connection identifier (DLCI) value of the PVC for which you wish to display fragments received or sent.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)XG


12.2(33)SRA


12.2SX


Usage Guidelines

This command will display event or error messages related to Frame Relay fragmentation; it is only enabled at the PVC level on the selected interface. This command is not supported on the Cisco MC3810 networking device for fragments received by a PVC configured via the voice-encap command.

Examples

The following is sample output from the debug frame-relay fragment command: Router# debug frame-relay fragment interface serial 0/0 109 This may severely impact network performance. You are advised to enable 'no logging console debug'. Continue?[confirm] Frame Relay fragment/packet debugging is on Displaying fragments/packets on interface Serial0/0 dlci 109 only

Serial0/0(i): dlci 109, rx-seq-num 126, exp_seq-num 126, BE bits set, frag_hdr 04 C0 7E


DB-725

Debug Commands debug frame-relay fragment

Serial0/0(o): dlci 109, tx-seq-num 82, BE bits set, frag_hdr 04 C0 52

The following is sample output from the debug frame-relay fragment event command: Router# debug frame-relay fragment event This may severely impact network performance. You are advised to enable 'no logging console debug'. Continue?[confirm] Frame Relay fragment event/errors debugging is on Frame-relay reassembled packet is greater than MTU size, packet dropped on serial 0/0 dlci 109 Unexpected B bit

frame rx on serial0/0 dlci 109, dropping pending segments

Rx an out-of-sequence packet on serial 0/0 dlci 109, seq_num_received 17 seq_num_expected 19

Related Commands

Command

Description

debug ccfrf11 session


debug ccsip all


debug ccsw voice vofr-session


debug voice vofr

Displays Cisco trunk and FRF.11 trunk call setup attempts; shows which dial peer is used in the call setup.

debug vpm error

Displays the behavior of the Holst state machine.

debug vtsp port

Displays the behavior of the VTSP state machine.

debug vtsp vofr subframe



DB-726

May 2008

Debug Commands debug frame-relay hqf

debug frame-relay hqf To display debug messages for Frame Relay (FR) hierarchical queueing framework (HQF) events, use the debug frame-relay hqf command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug frame-relay hqf no debug frame-relay hqf

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug frame-relay hqf command to track which quality of service (QoS) features are being used on an interface. QoS for a given FR interface changes depending on the commands being used.

Note

You cannot configure weighted fair queueing (WFQ) with HQF; they are mutually exclusive.

To use HQF on an interface, you must complete the following tasks: •

Install an interface level service policy without legacy queueing or payload compression.

•

Attach a Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC) service policy to a permanent virtual circuit (PVC) with no legacy restrictions. This task is accomplished by adding a service policy to a frame map class. A valid MQC service policy shapes all traffic via the class default and has a child policy to support any further traffic classification, as shown in the following example: policy-map llq class voice priority 32 policy-map shape1 class class-default shape average 96000 service-policy llq policy-map shape2 class class-default shape average 128000 service-policy llq map-class frame-relay mqc-class1


DB-727

Debug Commands debug frame-relay hqf

service-policy output shape1 map-class frame-relay mqc-class2 service-policy output shape2 interface serial4/0 encapsulation frame-relay frame-relay class mqc-class1 N, Type: Called Party, length: 11, 0x7009 0x9331 0x3233 0x3435 0x3637 0x386E Dir: U --> N, Type: Called Party Subaddr, length: 4, 0x7102 0xA000 Dir: U --> N, Type: Low Lyr Comp, length: 5, 0x7C03 0x88A0 0xCE65 Dir: U --> N, Type: User to User, length: 4, 0x7E02 0x0000

Table 99 explains the information elements shown in the example. Table 99

Related Commands

Information Elements in a Setup Message

Information Element

Description

Prot Disc

Protocol discriminator.

Call Ref

Call reference.

Message type

Message type such as setup, connect, and call proceeding.

Bearer Capability

Coding format such as data type, and Layer 2 and Layer 3 protocols.

DLCI

Data-link connection identifier.

Link Lyr Core

Link-layer core quality of service (QoS) requirements.

Calling Party

Type of source number (X121/E164) and the number.

Calling Party Subaddr

Subaddress that originated the call.

Called Party

Type of destination number (X121/E164) and the number.

Called Party Subaddr

Subaddress of the called party.

Low Lyr Comp

Coding format, data type, and Layer 2 and Layer 3 protocols intended for the end user.

User to User

Information between end users.

Command

Description

debug frame-relay callcontrol

Displays Frame Relay Layer 3 (network layer) call control information.


DB-731

Debug Commands debug frame-relay ip tcp header-compression

debug frame-relay ip tcp header-compression To display debugging information about TCP/IP header compression on Frame Relay interfaces, use the debug frame-relay ip tcp header-compression command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug frame-relay ip tcp header-compression no debug frame-relay ip tcp header-compression

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

10.0


12.2(33)SRA


12.4(9)T

This command was modified to display debugging output for control protocol frames for Frame Relay Forum Implementation Agreement (FRF) .20.

12.4(11)T

This command was modified to display debugging output for Enhanced Compressed Real-Time Transport Protocol (ECRTP).

12.2SX


Usage Guidelines

The debug frame-relay ip tcp header-compression command shows the control packets that are passed to initialize IP header compression (IPHC) on a permanent virtual circuit (PVC). For Cisco IPHC, typically two packets are passed: one sent and one received per PVC. (Inverse Address Resolution Protocol (InARP) packets are sent on PVCs that do not have a mapping defined between a destination protocol address and the data-link connection identifier (DLCI) or Frame Relay PVC bundle that connects to the destination address.) For FRF .20 IPHC, typically four packets are passed per PVC. Debug messages are displayed only if the IPHC control protocol is renegotiated (for an interface or PVC state change or for a configuration change).


DB-732

May 2008


Examples

The following is sample output from the debug frame-relay ip tcp header-compression command when Cisco IPHC (not FRF .20 IPHC) is configured in the IPHC profile: Router# debug frame-relay ip tcp header-compression *Nov 14 09:22:07.991: InARP REQ: Tx compr_flags 43 *Nov 14 09:22:08.103: InARP RSP: Rx compr_flags: 43

The following is sample output from the debug frame-relay ip tcp header-compression command when FRF .20 IPHC (without either Real-time Transport Protocol (RTP) or ECRTP) is configured in the IPHC profile: Router# debug frame-relay ip tcp header-compression FRF20(DLCI 16): Rxed Request, state 0 : ident 0, tot len 19, conf_opts FE, len 15 negotiation codes 1, version 1 Par: IPV4, len 12, TCP_SPACE 16, NON_TCP_SPACE 0, F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 : ident 0, tot len 19, conf_opts FE, len 15 negotiation codes 1, version 1 Par: IPV4, len 12, TCP_SPACE 16, NON_TCP_SPACE 0, F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 0 : ident 3, tot len 19, conf_opts FE, len 15 negotiation codes 0, version 1 Par: IPV4, len 12, TCP_SPACE 16, NON_TCP_SPACE 0, F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 : ident 3, tot len 19, conf_opts FE, len 15 negotiation codes 0, version 1 Par: IPV4, len 12, TCP_SPACE 16, NON_TCP_SPACE 0, F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 FRF20(DLCI 16): STARTING IPHC

FRF20(DLCI 16): Txed Ack, state 0

FRF20(DLCI 16): Txed Request, state

FRF20(DLCI 16): Rxed Ack, state 2

*Nov 14 09:18:37.019:

The following is sample output from the debug frame-relay ip tcp header-compression command when FRF .20 IPHC and RTP are configured in the IPHC profile: Router# debug frame-relay ip tcp header-compression FRF20(DLCI 16): Txed Request, state 1 : ident 0, tot len 21, conf_opts FE, len 17 negotiation codes 1, version 1 Par: IPV4, len 14, TCP_SPACE 16, NON_TCP_SPACE 16, F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 01:33:06: Subopt: rtp enabled

The following is sample output from the debug frame-relay ip tcp header-compression command when FRF .20 IPHC and ECRTP are configured in the IPHC profile: Router# debug frame-relay ip tcp header-compression FRF20(DLCI 16): Txed Request, state 1 : ident 0, tot len 21, conf_opts FE, len 17 negotiation codes 1, version 1 Par: IPV4, len 14, TCP_SPACE 16, NON_TCP_SPACE 16, F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 01:33:06: Subopt: ecrtp enabled


DB-733



debug frame-relay ip tcp header-compression Field Descriptions

Field

Description

InARP REQ: Tx

Indicates that an InARP request was sent or received. Following are the possible values:

InARP RSP: Rx

compr_flags: 43

•

InARP REQ Tx—An InARP request was sent.

•

InARP REQ Rx—An InARP request was received.

Indicates that an InARP response was sent or received. Following are the possible values: •

InARP REQ Tx—An InARP response was sent.

•

InARP REQ Rx—An InARP response was received.

Compression flags that Frame Relay peers use to negotiate Cisco IPHC options. It consists of a bit mask, and the number is displayed in hexadecimal format. Following are the bits: •

0x0001—TCP IPHC

•

0x0002—RTP IPHC

•

0x0004—Passive TCP compression

•

0x0008—Passive RTP compression

•

0x0040—Frame Relay IPHC options

FRF20(DLCI 16)

Indicates that the DLCI for this packet is configured with FRF .20 IPHC.

Txed Request

Direction of the IPHC control protocol message. Following are the possible values: •

Txed Request

•

Txed Ack

•

Rxed Request

•

Rxed Ack

Txed (transmitted) or Rxed (received) indicates the message direction, and Request or Ack (acknowledgement) indicates the message type. A peer sends a request indicating its configuration, and the other peer replies with an acknowledgement indicating its configuration. The lowest configuration value of this two-frame exchange sets the parameters in one direction. This means that typically four frames are exchanged in total: two Request/Ack pairs, with each pair negotiating the parameters in one direction.


DB-734

May 2008


Table 100

debug frame-relay ip tcp header-compression Field Descriptions (continued)

Field

Description

state 1

State of the FRF .20 IPHC protocol request. Following are the possible values: 0—FRF20_DISABLED. FRF .20 is disabled (because of an inactive PVC, an interface that is down, or a configuration mismatch). 1—FRF20_REQ_SENT. An FRF .20 control protocol request has been sent. 2—FRF20_REQ_RXED. An FRF .20 control protocol request has been received. 3—FRF20_WAIT_REQ. An FRF .20 control protocol request has been sent and acknowledged, and the local end is waiting for a request from the peer. 4—FRF20_OPERATIONAL. The FRF .20 control protocol is successfully negotiated, and frames can be compressed.

ident 0

Identifier. This is the transaction number used to correlate an FRF .20 control protocol request with an acknowledgement. This number is the same in messages that correspond to each other.

tot len 21

Sum (in bytes) of the lengths of the following: •

All parameters

•

Negotiation codes

•

Identifier

•

Suboptions for each parameter set (IPV4 or IPV6)

conf_opts FE

Type of PPP parameter (expressed in hexadecimal). For FRF .20, the only possible value is FE (254 in decimal).

len 17

Total length of all parameters (in bytes).

negotiation codes 1

Negotiation state with the peer. Following are the possible values: •

0—Reply with response only.

•

1—Reply with response and initiate request.

With a response only, sending a response frame completes the negotiation. With a response and initiate request, the local peer also must send a request. version 1

Version of the FRF .20 control protocol.

Par

List of parameters and values.

IPV4

Datagram type. The value is always IPV4, because Cisco IPHC does not support IPv6.

len 14

Total length (in bytes) of all parameters starting with IP type and ending with associated suboptions (if any). The value is greater than or equal to 12 depending on the suboptions.

TCP_SPACE 16

Maximum value of a TCP context identifier (CID) in the space of context identifiers allocated for TCP. Range: 3–255. Default value: 16. A value of zero means that TCP headers are not being compressed.


DB-735


Table 100

debug frame-relay ip tcp header-compression Field Descriptions (continued)

Field

Description

NON_TCP_SPACE 16 Maximum value of a context identifier (CID) in the space of context identifiers allocated for non-TCP. Range: 3–1000. Cisco routers do not support the maximum value (65535) of the FRF .20 specification. Default value: 16. A value of zero means that non-TCP headers are not being compressed. These context identifiers are carried in COMPRESSED_NON_TCP, COMPRESSED_UDP and COMPRESSED_RTP packet headers. F_MAX_PERIOD 256 Largest number of compressed non-TCP headers that can be sent without sending a full header. Range: 1–65535. Default value: 256. A value of zero indicates infinity, which means that the number of consecutive COMPRESSED_NON_TCP headers is unlimited. F_MAX_TIME 5

Maximum time interval (in seconds) between full (uncompressed) headers. Range: 1–255. Default value: 5. A value of zero indicates infinity (meaning that no full headers will be transmitted).

MAX_HEADER 168

Largest header size (in bytes) that can be compressed. Range: 60–168. Cisco routers do not support the full range of values (60–65535) of the FRF .20 specification. Default value: 168.

01:33:06

Timestamp of the debug command output.

Subopt

Compression suboptions that are enabled. The value is either rtp or ecrtp.


DB-736

May 2008

Debug Commands debug frame-relay lapf

debug frame-relay lapf To display Frame Relay switched virtual circuit (SVC) Layer 2 information, use the debug frame-relay lapf command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug frame-relay lapf no debug frame-relay lapf

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use the debug frame-relay lapf command to troubleshoot the data-link control portion of Layer 2 that runs over data-link connection identifier (DLCI) 0. Use this command only if you have a problem bringing up Layer 2. You can use the show interface serial command to determine the status of Layer 2. If it shows a Link Access Procedure, Frame Relay (LAPF) state of down, Layer 2 has a problem.

Examples

The following is sample output from the debug frame-relay lapf command. In this example, a line being brought up indicates an exchange of set asynchronous balanced mode extended (SABME) and unnumbered acknowledgment (UA) commands. A SABME is initiated by both sides, and a UA is the response. Until the SABME gets a UA response, the line is not declared to be up. The p/f value indicates the poll/final bit setting. TX means send, and RX means receive. Router# debug frame-relay lapf Router: Router: Router: Router: Router: Router: Router: Router:

*LAPF *LAPF *LAPF *LAPF *LAPF *LAPF *LAPF *LAPF

Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0 Serial0

TX -> SABME Cmd p/f=1 Enter state 5 RX RR Rsp p/f=1, RX RR Rsp p/f=1, RX AUTHORIZING] on event [REQUEST PPP REGEN] 06:24:02: GPRS:1011111111500001:Got VPN authorization info 06:24:02: GPRS:1011111111500001:got event [AUTHOR SUCCESS] in state [AUTHORIZING] 06:24:02: PPP-REGEN state counters: pending counter is 1 06:24:02: State[IDLE] counter is 0 06:24:02: State[AUTHORIZING] counter is 0 06:24:02: State[VPDN CONNECTING] counter is 1 06:24:02: State[PPP NEGOTIATING] counter is 0 06:24:02: State[PPP CONNECTED] counter is 0 06:24:02: State[PPP TERMINATING] counter is 0 06:24:02: GPRS:1011111111500001:state [AUTHORIZING->VPDN CONNECTING] on event [AUTHOR SUCCESS] 06:24:02: GPRS:1011111111500001:Author succeeded, establishing the tunnel 06:24:02: GPRS:1011111111500001:Create/Clone vaccess to negotiate PPP 06:24:02: GPRS:1011111111500001:no need to set NS ppp_config 06:24:02: GPRS:1011111111500001:MS no static IP addr. Get one via IPCP 06:24:02: GPRS:1011111111500001:VPDN to inform PPP regen: CONNECTED 06:24:02: GPRS:1011111111500001:got event [VPDN CONNECTED] in state [VPDN CONNECTING] 06:24:02: PPP-REGEN state counters: pending counter is 1 06:24:02: State[IDLE] counter is 0 06:24:02: State[AUTHORIZING] counter is 0 06:24:02: State[VPDN CONNECTING] counter is 0 06:24:02: State[PPP NEGOTIATING] counter is 1 06:24:02: State[PPP CONNECTED] counter is 0 06:24:02: State[PPP TERMINATING] counter is 0 06:24:02: GPRS:1011111111500001:state [VPDN CONNECTING->PPP NEGOTIATING] on event [VPDN CONNECTED] 06:24:02: GPRS:1011111111500001:Start PPP negotiations on vaccess 06:24:02: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up


DB-799

Debug Commands debug gprs gtp ppp-regeneration

06:24:02: GPRS:1011111111500001:IPCP is up 06:24:02: GPRS:1011111111500001:LNS allocates 10.100.1.1 for MS 06:24:02: GPRS:1011111111500001:IP addr 10.100.1.1 is negotiated for MS 06:24:02: GPRS:1011111111500001:PPP connected 06:24:02: GPRS:1011111111500001:got event [PPP NEGOTIATED] in state [PPP NEGOTIATING] 06:24:02: PPP-REGEN state counters: pending counter is 0 06:24:02: State[IDLE] counter is 0 06:24:02: State[AUTHORIZING] counter is 0 06:24:02: State[VPDN CONNECTING] counter is 0 06:24:02: State[PPP NEGOTIATING] counter is 0 06:24:02: State[PPP CONNECTED] counter is 1 06:24:02: State[PPP TERMINATING] counter is 0 06:24:02: GPRS:1011111111500001:state [PPP NEGOTIATING->PPP CONNECTED] on event [PPP NEGOTIATED] 06:24:02: GPRS:1011111111500001:PPP succeeded negotiation, session established 06:24:02: GPRS:1011111111500001:Session timer stopped 06:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

Example 2

The following example displays both details and events related to PPP regeneration processing after clearing PDP contexts on the GGSN: Router# clear gprs gtp pdp-context all 06:28:05: PPP-REGEN state counters: pending counter is 0 06:28:05: State[IDLE] counter is 0 06:28:05: State[AUTHORIZING] counter is 0 06:28:05: State[VPDN CONNECTING] counter is 0 06:28:05: State[PPP NEGOTIATING] counter is 0 06:28:05: State[PPP CONNECTED] counter is 1 06:28:05: State[PPP TERMINATING] counter is 0 06:28:05: GPRS:1011111111500001:PPP regen current state PPP CONNECTED 06:28:05: GPRS:1011111111500001:GTP disconnecting the PPP regen session 06:28:05: GPRS:Processing PPP regen reqQ 06:28:05: GPRS:1011111111500001:Processing Disconnect PPP regen from reqQ 06:28:05: GPRS:1011111111500001:got event [CANCEL REGEN'ED PPP] in state [PPP CONNECTED] 06:28:05: PPP-REGEN state counters: pending counter is 1 06:28:05: State[IDLE] counter is 0 06:28:05: State[AUTHORIZING] counter is 0 06:28:05: State[VPDN CONNECTING] counter is 0 06:28:05: State[PPP NEGOTIATING] counter is 0 06:28:05: State[PPP CONNECTED] counter is 0 06:28:05: State[PPP TERMINATING] counter is 1 06:28:05: GPRS:1011111111500001:state [PPP CONNECTED->PPP TERMINATING] on event [CANCEL REGEN'ED PPP] 06:28:05: GPRS:1011111111500001:Cancel request after VPND tunnel is up 06:28:05: PPP-REGEN state counters: pending counter is 1 06:28:05: State[IDLE] counter is 0 06:28:05: State[AUTHORIZING] counter is 0 06:28:05: State[VPDN CONNECTING] counter is 0 06:28:05: State[PPP NEGOTIATING] counter is 0 06:28:05: State[PPP CONNECTED] counter is 0 06:28:05: State[PPP TERMINATING] counter is 1 06:28:05: GPRS:1011111111500001:PPP down 06:28:05: GPRS:1011111111500001:got event [PPP FAILED] in state [PPP TERMINATING] 06:28:05: PPP-REGEN state counters: pending counter is 1 06:28:05: State[IDLE] counter is 1 06:28:05: State[AUTHORIZING] counter is 0 06:28:05: State[VPDN CONNECTING] counter is 0 06:28:05: State[PPP NEGOTIATING] counter is 0 06:28:05: State[PPP CONNECTED] counter is 0 06:28:05: State[PPP TERMINATING] counter is 0


DB-800

May 2008

Debug Commands debug gprs gtp ppp-regeneration

06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:05: 06:28:06: to down

GPRS:1011111111500001:state [PPP TERMINATING->IDLE] on event [PPP FAILED] GPRS:1011111111500001:LCP went down GPRS:1011111111500001:VPDN disconnect GPRS:1011111111500001:got event [CLEANUP CONTEXT] in state [IDLE] GPRS:1011111111500001:state [IDLE->IDLE] on event [CLEANUP CONTEXT] GPRS:1011111111500001:Freeing context structure GPRS:1011111111500001:VPDN handle invalid, no need to free it GPRS:1011111111500001:remove PPP regen context from Vi2 GPRS:1011111111500001:Session timer stopped PPP-REGEN state counters: pending counter is 0 State[IDLE] counter is 0 State[AUTHORIZING] counter is 0 State[VPDN CONNECTING] counter is 0 State[PPP NEGOTIATING] counter is 0 State[PPP CONNECTED] counter is 0 State[PPP TERMINATING] counter is 0 GPRS:1011111111500001:PPP regen context 0x633F196C released %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state


DB-801

Debug Commands debug gprs gtp

debug gprs gtp To display information about the GPRS Tunneling Protocol (GTP), use the debug gprs gtp privileged EXEC command. To disable debugging output, use the no form of this command. debug gprs gtp {events | messages | packets} no debug gprs gtp {events | messages | packets}

Syntax Description

events

Displays events related to GTP processing on the GGSN.

messages

Displays GTP signaling messages that are sent between the SGSN and GGSN.

packets

Displays GTP packets that are sent between the SGSN and GGSN.

Defaults


Command History

Release

Modification

12.1(1)GA


12.1(5)T


12.2(4)MX

This command was incorporated in Cisco IOS Release 12.2(4)MX, and the ppp {details | events} option was added.

12.2(8)YD

This command was incorporated in Cisco IOS Release 12.2(8)YD.

12.2(8)YW

This command was incorporated in Cisco IOS Release 12.2(8)YW.

12.3(2)XB

This command was incorporated in Cisco IOS Release 12.3(2)XB.

Usage Guidelines

Caution

Examples

12.3(8)XU

This command was incorporated in Cisco IOS Release 12.3(8)XU.

12.3(11)YJ

This command was incorporated in Cisco IOS Release 12.3(11)YJ.

12.3(14)YQ

This command was incorporated in Cisco IOS Release 12.3(14)YQ.

12.2SX


This command is useful for system operators and development engineers if problems are encountered with communication between the GGSN and the SGSN using GTP.

Because the debug gprs gtp command generates a significant amount of output, use it only when traffic on the GPRS network is low, so other activity on the system is not adversely affected.

The following example enables the display of events related to GTP processing on the GGSN: Router# debug gprs gtp events


DB-802

May 2008


The following example enables the display of GTP signaling messages: Router# debug gprs gtp messages

The following example enables the display of GTP packets sent between the SGSN and GGSN: Router# debug gprs gtp packets

The following example enables the display of GTP PPP events between the SGSN and GGSN: Router# debug gprs gtp ppp events

The following example enables the display of detailed GTP PPP debug output along with GTP PPP events between the SGSN and GGSN: Router# debug gprs gtp ppp details Router# debug gprs gtp ppp events

The following debug examples provide sample output for a create PDP context request, delete PDP context request, and clear PDP context using PPP regeneration on the GGSN. The first three examples show output related to debug events messaging only. The last three examples show output while both debug events and details are enabled on the GGSN. Example 1 Example 2 Example 3 *Mar 1 00:04:50.083: GPRS:1111110000000000:GTP disconnecting the PPP regen session *Mar 1 00:04:50.083: GPRS:1111110000000000:Processing Disconnect PPP regen from reqQ *Mar 1 00:04:50.083: GPRS:1111110000000000:got event [CANCEL REGEN'ED PPP] in state [PPP CONNECTED] *Mar 1 00:04:50.083: GPRS:1111110000000000:state [PPP CONNECTED->PPP TERMINATING] on event [CANCEL REGEN'ED PPP] *Mar 1 00:04:50.083: GPRS:1111110000000000:Cancel request after VPND tunnel is up *Mar 1 00:04:50.087: GPRS:1111110000000000:PPP down *Mar 1 00:04:50.087: GPRS:1111110000000000:got event [PPP FAILED] in state [PPP TERMINATING] *Mar 1 00:04:50.091: GPRS:1111110000000000:state [PPP TERMINATING->IDLE] on event [PPP FAILED] *Mar 1 00:04:50.091: GPRS:1111110000000000:PPP failed negotiation *Mar 1 00:04:50.091: GPRS:1111110000000000:got event [CLEANUP CONTEXT] in state [IDLE] *Mar 1 00:04:50.091: GPRS:1111110000000000:VPDN to inform PPP regen: DISCONNECTED *Mar 1 00:04:50.091: GPRS:1111110000000000:got event [VPDN DISCONNECTED] in state [IDLE] *Mar 1 00:04:50.091: GPRS:1111110000000000:state [IDLE->IDLE] on event [CLEANUP CONTEXT] *Mar 1 00:04:50.091: GPRS:1111110000000000:Freeing context structure *Mar 1 00:04:50.091: %LINK-3-UPDOWN: Interface Virtual-Access4, changed state to down *Mar 1 00:04:51.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access4, changed state to down

Example 4 *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1 1 1 1 1

00:05:21.083: PPP-REGEN state counters: pending counter is 0 00:05:21.083: State[IDLE] counter is 0 00:05:21.083: State[AUTHORIZING] counter is 0 00:05:21.083: State[VPDN CONNECTING] counter is 0 00:05:21.083: State[PPP NEGOTIATING] counter is 0 00:05:21.083: State[PPP CONNECTED] counter is 0 00:05:21.083: State[PPP TERMINATING] counter is 0 00:05:21.087: PPP-REGEN state counters: pending counter is 1 00:05:21.087: State[IDLE] counter is 1 00:05:21.087: State[AUTHORIZING] counter is 0


DB-803


*Mar 1 00:05:21.087: State[VPDN CONNECTING] counter is 0 *Mar 1 00:05:21.087: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:05:21.087: State[PPP CONNECTED] counter is 0 *Mar 1 00:05:21.087: State[PPP TERMINATING] counter is 0 *Mar 1 00:05:21.087: GPRS:1111110000000000:Authen: PAP username: [email protected] *Mar 1 00:05:21.087: GPRS:1111110000000000:Session timer started *Mar 1 00:05:21.087: GPRS:1111110000000000:Processing Initiate PPP regen from reqQ *Mar 1 00:05:21.087: GPRS:1111110000000000:got event [REQUEST PPP REGEN] in state [IDLE] *Mar 1 00:05:21.087: PPP-REGEN state counters: pending counter is 1 *Mar 1 00:05:21.087: State[IDLE] counter is 0 *Mar 1 00:05:21.087: State[AUTHORIZING] counter is 1 *Mar 1 00:05:21.087: State[VPDN CONNECTING] counter is 0 *Mar 1 00:05:21.087: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:05:21.087: State[PPP CONNECTED] counter is 0 *Mar 1 00:05:21.087: State[PPP TERMINATING] counter is 0 *Mar 1 00:05:21.087: GPRS:1111110000000000:state [IDLE->AUTHORIZING] on event [REQUEST PPP REGEN] *Mar 1 00:05:21.087: GPRS:1111110000000000:Got VPN authorization info *Mar 1 00:05:21.087: GPRS:1111110000000000:got event [AUTHOR SUCCESS] in state [AUTHORIZING] *Mar 1 00:05:21.087: PPP-REGEN state counters: pending counter is 1 *Mar 1 00:05:21.087: State[IDLE] counter is 0 *Mar 1 00:05:21.087: State[AUTHORIZING] counter is 0 *Mar 1 00:05:21.087: State[VPDN CONNECTING] counter is 1 *Mar 1 00:05:21.087: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:05:21.087: State[PPP CONNECTED] counter is 0 *Mar 1 00:05:21.087: State[PPP TERMINATING] counter is 0 *Mar 1 00:05:21.087: GPRS:1111110000000000:state [AUTHORIZING->VPDN CONNECTING] on event [AUTHOR SUCCESS] *Mar 1 00:05:21.087: GPRS:1111110000000000:Author succeeded, establishing the tunnel *Mar 1 00:05:21.087: GPRS:1111110000000000:Create/Clone vaccess to negotiate PPP *Mar 1 00:05:21.091: GPRS:1111110000000000:MS no static IP addr. Get one via IPCP *Mar 1 00:05:21.127: GPRS:1111110000000000:VPDN to inform PPP regen: CONNECTED *Mar 1 00:05:21.127: GPRS:1111110000000000:got event [VPDN CONNECTED] in state [VPDN CONNECTING] *Mar 1 00:05:21.127: PPP-REGEN state counters: pending counter is 1 *Mar 1 00:05:21.127: State[IDLE] counter is 0 *Mar 1 00:05:21.127: State[AUTHORIZING] counter is 0 *Mar 1 00:05:21.127: State[VPDN CONNECTING] counter is 0 *Mar 1 00:05:21.127: State[PPP NEGOTIATING] counter is 1 *Mar 1 00:05:21.127: State[PPP CONNECTED] counter is 0 *Mar 1 00:05:21.127: State[PPP TERMINATING] counter is 0 *Mar 1 00:05:21.127: GPRS:1111110000000000:state [VPDN CONNECTING->PPP NEGOTIATING] on event [VPDN CONNECTED] *Mar 1 00:05:21.127: GPRS:1111110000000000:Start PPP negotiations on vaccess *Mar 1 00:05:21.131: %LINK-3-UPDOWN: Interface Virtual-Access5, changed state to up *Mar 1 00:05:22.135: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access5, changed state to up *Mar 1 00:05:23.143: GPRS:1111110000000000:IPCP is up *Mar 1 00:05:23.143: GPRS:1111110000000000:LNS allocates 10.10.1.187 for MS *Mar 1 00:05:23.143: GPRS:1111110000000000:IP addr 10.10.1.187 is negotiated for MS *Mar 1 00:05:23.143: GPRS:1111110000000000:DNS - Primary: 10.3.0.1 Secondary: 0.0.0.0 NetBios - Primary: 0.0.0.0, Secondary: 0.0.0.0 *Mar 1 00:05:23.143: GPRS:1111110000000000:PPP connected *Mar 1 00:05:23.143: GPRS:1111110000000000:got event [PPP NEGOTIATED] in state [PPP NEGOTIATING] *Mar 1 00:05:23.143: PPP-REGEN state counters: pending counter is 0 *Mar 1 00:05:23.143: State[IDLE] counter is 0 *Mar 1 00:05:23.143: State[AUTHORIZING] counter is 0 *Mar 1 00:05:23.143: State[VPDN CONNECTING] counter is 0 *Mar 1 00:05:23.143: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:05:23.143: State[PPP CONNECTED] counter is 1 *Mar 1 00:05:23.143: State[PPP TERMINATING] counter is 0


DB-804

May 2008


*Mar event *Mar *Mar

1 00:05:23.143: GPRS:1111110000000000:state [PPP NEGOTIATING->PPP CONNECTED] on [PPP NEGOTIATED] 1 00:05:23.143: GPRS:1111110000000000:PPP succeeded negotiation, session established 1 00:05:23.143: GPRS:1111110000000000:Session timer stopped

Example 5 *Mar 1 00:05:52.399: PPP-REGEN state counters: pending counter is 0 *Mar 1 00:05:52.399: State[IDLE] counter is 0 *Mar 1 00:05:52.399: State[AUTHORIZING] counter is 0 *Mar 1 00:05:52.399: State[VPDN CONNECTING] counter is 0 *Mar 1 00:05:52.399: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:05:52.399: State[PPP CONNECTED] counter is 1 *Mar 1 00:05:52.399: State[PPP TERMINATING] counter is 0 *Mar 1 00:05:52.399: GPRS:1111110000000000:PPP regen current state PPP CONNECTED *Mar 1 00:05:52.399: GPRS:1111110000000000:GTP disconnecting the PPP regen session *Mar 1 00:05:52.399: GPRS:1111110000000000:Processing Disconnect PPP regen from reqQ *Mar 1 00:05:52.399: GPRS:1111110000000000:got event [CANCEL REGEN'ED PPP] in state [PPP CONNECTED] *Mar 1 00:05:52.399: PPP-REGEN state counters: pending counter is 1 *Mar 1 00:05:52.399: State[IDLE] counter is 0 *Mar 1 00:05:52.399: State[AUTHORIZING] counter is 0 *Mar 1 00:05:52.399: State[VPDN CONNECTING] counter is 0 *Mar 1 00:05:52.399: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:05:52.399: State[PPP CONNECTED] counter is 0 *Mar 1 00:05:52.399: State[PPP TERMINATING] counter is 1 *Mar 1 00:05:52.399: GPRS:1111110000000000:state [PPP CONNECTED->PPP TERMINATING] on event [CANCEL REGEN'ED PPP] *Mar 1 00:05:52.399: GPRS:1111110000000000:Cancel request after VPND tunnel is up *Mar 1 00:05:52.403: GPRS:1111110000000000:PPP down *Mar 1 00:05:52.403: GPRS:1111110000000000:got event [PPP FAILED] in state [PPP TERMINATING] *Mar 1 00:05:52.407: PPP-REGEN state counters: pending counter is 1 *Mar 1 00:05:52.407: State[IDLE] counter is 1 *Mar 1 00:05:52.407: State[AUTHORIZING] counter is 0 *Mar 1 00:05:52.407: State[VPDN CONNECTING] counter is 0 *Mar 1 00:05:52.407: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:05:52.407: State[PPP CONNECTED] counter is 0 *Mar 1 00:05:52.407: State[PPP TERMINATING] counter is 0 *Mar 1 00:05:52.407: GPRS:1111110000000000:state [PPP TERMINATING->IDLE] on event [PPP FAILED] *Mar 1 00:05:52.407: GPRS:1111110000000000:PPP failed negotiation *Mar 1 00:05:52.407: GPRS:1111110000000000:got event [CLEANUP CONTEXT] in state [IDLE] *Mar 1 00:05:52.407: GPRS:1111110000000000:VPDN to inform PPP regen: DISCONNECTED *Mar 1 00:05:52.407: GPRS:1111110000000000:got event [VPDN DISCONNECTED] in state [IDLE] *Mar 1 00:05:52.407: GPRS:1111110000000000:state [IDLE->IDLE] on event [CLEANUP CONTEXT] *Mar 1 00:05:52.407: GPRS:1111110000000000:Freeing context structure *Mar 1 00:05:52.407: GPRS:1111110000000000:Session timer stopped *Mar 1 00:05:52.407: PPP-REGEN state counters: pending counter is 0 *Mar 1 00:05:52.407: State[IDLE] counter is 0 *Mar 1 00:05:52.407: State[AUTHORIZING] counter is 0 *Mar 1 00:05:52.407: State[VPDN CONNECTING] counter is 0 *Mar 1 00:05:52.407: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:05:52.407: State[PPP CONNECTED] counter is 0 *Mar 1 00:05:52.407: State[PPP TERMINATING] counter is 0 *Mar 1 00:05:52.407: GPRS:1111110000000000:PPP regen context 0x6219F4BC released *Mar 1 00:05:52.407: GPRS:GTP-PPP-REGEN context magic(0x619D4FBC) invalid *Mar 1 00:05:52.407: %LINK-3-UPDOWN: Interface Virtual-Access5, changed state to down *Mar 1 00:05:53.399: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access5, changed state to downExample 6 *Mar *Mar

1 00:06:34.907: PPP-REGEN state counters: pending counter is 0 1 00:06:34.907: State[IDLE] counter is 0


DB-805


*Mar 1 00:06:34.907: State[AUTHORIZING] counter is 0 *Mar 1 00:06:34.907: State[VPDN CONNECTING] counter is 0 *Mar 1 00:06:34.907: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:06:34.907: State[PPP CONNECTED] counter is 1 *Mar 1 00:06:34.907: State[PPP TERMINATING] counter is 0 *Mar 1 00:06:34.907: GPRS:1111110000000000:PPP regen current state PPP CONNECTED *Mar 1 00:06:34.907: GPRS:1111110000000000:GTP disconnecting the PPP regen session *Mar 1 00:06:34.907: GPRS:1111110000000000:Processing Disconnect PPP regen from reqQ *Mar 1 00:06:34.907: GPRS:1111110000000000:got event [CANCEL REGEN'ED PPP] in state [PPP CONNECTED] *Mar 1 00:06:34.907: PPP-REGEN state counters: pending counter is 1 *Mar 1 00:06:34.907: State[IDLE] counter is 0 *Mar 1 00:06:34.907: State[AUTHORIZING] counter is 0 *Mar 1 00:06:34.907: State[VPDN CONNECTING] counter is 0 *Mar 1 00:06:34.907: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:06:34.907: State[PPP CONNECTED] counter is 0 *Mar 1 00:06:34.907: State[PPP TERMINATING] counter is 1 *Mar 1 00:06:34.907: GPRS:1111110000000000:state [PPP CONNECTED->PPP TERMINATING] on event [CANCEL REGEN'ED PPP] *Mar 1 00:06:34.907: GPRS:1111110000000000:Cancel request after VPND tunnel is up *Mar 1 00:06:34.911: GPRS:1111110000000000:PPP down *Mar 1 00:06:34.911: GPRS:1111110000000000:got event [PPP FAILED] in state [PPP TERMINATING] *Mar 1 00:06:34.915: PPP-REGEN state counters: pending counter is 1 *Mar 1 00:06:34.915: State[IDLE] counter is 1 *Mar 1 00:06:34.915: State[AUTHORIZING] counter is 0 *Mar 1 00:06:34.915: State[VPDN CONNECTING] counter is 0 *Mar 1 00:06:34.915: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:06:34.915: State[PPP CONNECTED] counter is 0 *Mar 1 00:06:34.915: State[PPP TERMINATING] counter is 0 *Mar 1 00:06:34.915: GPRS:1111110000000000:state [PPP TERMINATING->IDLE] on event [PPP FAILED] *Mar 1 00:06:34.915: GPRS:1111110000000000:PPP failed negotiation *Mar 1 00:06:34.915: GPRS:1111110000000000:got event [CLEANUP CONTEXT] in state [IDLE] *Mar 1 00:06:34.915: GPRS:1111110000000000:VPDN to inform PPP regen: DISCONNECTED *Mar 1 00:06:34.915: GPRS:1111110000000000:got event [VPDN DISCONNECTED] in state [IDLE] *Mar 1 00:06:34.915: GPRS:1111110000000000:state [IDLE->IDLE] on event [CLEANUP CONTEXT] *Mar 1 00:06:34.915: GPRS:1111110000000000:Freeing context structure *Mar 1 00:06:34.915: GPRS:1111110000000000:Session timer stopped *Mar 1 00:06:34.915: PPP-REGEN state counters: pending counter is 0 *Mar 1 00:06:34.915: State[IDLE] counter is 0 *Mar 1 00:06:34.915: State[AUTHORIZING] counter is 0 *Mar 1 00:06:34.915: State[VPDN CONNECTING] counter is 0 *Mar 1 00:06:34.915: State[PPP NEGOTIATING] counter is 0 *Mar 1 00:06:34.915: State[PPP CONNECTED] counter is 0 *Mar 1 00:06:34.915: State[PPP TERMINATING] counter is 0 *Mar 1 00:06:34.915: GPRS:1111110000000000:PPP regen context 0x62196E10 released *Mar 1 00:06:34.915: GPRS:GTP-PPP-REGEN context magic(0x619D4FBC) invalid *Mar 1 00:06:34.915: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to down *Mar 1 00:06:35.907: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to down


DB-806

May 2008

Debug Commands debug gprs radius

debug gprs radius To display information about Remote Access Dial-In User Service (RADIUS) processing on the GGSN, use the debug gprs radius privileged EXEC command. To disable debugging output, use the no form of this command. debug gprs radius no debug gprs radius

Syntax Description


Defaults


Command History

Release

Modification

12.2(4)MX


12.2(8)YD

This command was incorporated in Cisco IOS Release 12.2(8)YD.

12.2(8)YW

This command was incorporated in Cisco IOS Release 12.2(8)YW.

12.3(2)XB

This command was incorporated in Cisco IOS Release 12.3(2)XB.

12.3(8)XU

This command was incorporated in Cisco IOS Release 12.3(8)XU.

12.3(11)YJ

This command was incorporated in Cisco IOS Release 12.3(11)YJ.

12.3(14)YQ


12.2SX


Usage Guidelines

Caution

Examples

This command is useful for system operators and development engineers if problems are encountered with communication between a RADIUS server and the GGSN.

Because the debug gprs radius command generates a significant amount of output, use it only when traffic on the GPRS network is low, so other activity on the system is not adversely affected.

The following example enables the display of debug messages related to RADIUS processing on the GGSN: Router# debug gprs radius


DB-807

Debug Commands debug gprs redundancy

debug gprs redundancy To display debug messages, errors, events, or packets related to GTP session redundancy (GTP-SR), use the debug gprs redundancy privileged EXEC command. To disable debugging output, use the no form of this command. debug gprs redundancy [debug | errors | events | packets] no debug gprs redundancy [debug | errors | events | packets]

Syntax Description

Command History

debug

Displays debug messages related to GTP-SR.

errors

Displays errors related to GTP-SR.

events

Displays events related to GTP-SR.

packets

Displays packets related to GTP-SR packets.

Release

Modification

12.3(11)YJ


12.3(14)YQ


12.4(9)T


12.2SX


Usage Guidelines

This command displays debug level messages, errors, events, or packets for GTP-SR. It is useful for system operators and development engineers if problems are encountered with communication between the two GGSNs configured as an redundant pair and on which GTP-SR is enabled.

Examples

Example 1.

The following sample outputs is for a GGSN failover and switchover of Standby to Active. There is no PDP context involved in this debug collection. Active GGSN: Router-a#show gprs redundancy GPRS redundancy is enabled and Unit-Status is Standby Redundancy Transport Infrastructure status Redundancy Infrastructure state: Peer Redundancy Infrastructure state: GGSN Redundancy system up since: Time of last switchover: Total Number of Switchovers:

STANDBY HOT ACTIVE 21:29:21 EDT Aug 19 2000 never 2

GPRS Redundancy Statistics Last cleared: never CheckPointed-From-Active Statistics


DB-808

May 2008


Total Number of Messages: Number of Context Setup messages: Number of Context Modify messages: Number of Context Remove messages: Number of Path Setup messages: Number of Path Modify messages: Number of Path Remove messages: Number of CGF Ready messages: Number of CGF Modify messages: Number of CGF Remove messages: Number of Internal State messages:

129 19 3 19 34 5 34 1 0 0 7

Router-a#debug gprs redundancy GPRS CF packets debugging is on GPRS CF events debugging is on GPRS CF errors debugging is on GPRS CF debug debugging is on Router-a# Router-a# Router-a# MWAM 10/2: 000064: Jun 1 2006 18:19:00.975 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1100 Grp 51 state Standby -> Active MWAM 10/2: 000065: Jun 1 2006 18:19:00.975 EDT: GTP-SR: RF_Status=403-RF_STATUS_MAINTENANCE_ENABLE RFState=9-ACTIVE-FAST operand=0 RFPeerState=13-ACTIVE MWAM 10/2: 000066: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=200-RF_PROG_ACTIVE_FAST RFState=9-ACTIVE-FAST operand=0 RFPeerState=13-ACTIVE MWAM 10/2: 000067: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active Fast MWAM 10/2: 000068: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=201-RF_PROG_ACTIVE_DRAIN RFState=10-ACTIVE-DRAIN operand=0 RFPeerState=13-ACTIVE MWAM 10/2: 000069: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active Drain MWAM 10/2: 000070: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=202-RF_PROG_ACTIVE_PRECONFIG RFState=11-ACTIVE_PRECONFIG operand=0 RFPeerState=13-ACTIVE MWAM 10/2: 000071: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active PreConfig MWAM 10/2: 000072: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=203-RF_PROG_ACTIVE_POSTCONFIG RFState=12-ACTIVE_POSTCONFIG operand=0 RFPeerState=13-ACTIVE MWAM 10/2: 000073: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active PostConfig MWAM 10/2: 000074: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=204-RF_PROG_ACTIVE RFState=13-ACTIVE operand=0 RFPeerState=13-ACTIVE MWAM 10/2: 000075: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active MWAM 10/2: 000076: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Start of the Standby-to-Active transition MWAM 10/2: 000077: Jun 1 2006 18:19:00.979 EDT: GTP_SR: Old State Standby,Event Active Fast Received, New State Active MWAM 10/2: 000078: Jun 1 2006 18:19:00.979 EDT: GTP-SR:Context Type OWN, Handler Sync, Context Event OWN Ready, Context Sub Event No Sub Event MWAM 10/2: 000079: Jun 1 2006 18:19:00.979 EDT: GTP-SR:State of Redundancy Context is Initialized MWAM 10/2: 000080: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Event OWN Ready, Sub Event No Sub Event MWAM 10/2: 000081: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Removing element from state-list Initialized, final count 2 MWAM 10/2: 000082: Jun 1 2006 18:19:00.979 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 2 MWAM 10/2: 000083: Jun 1 2006 18:19:00.979 EDT: GTP-SR:Context Type CGF, Handler Sync, Context Event CGF Ready, Context Sub Event No Sub Event MWAM 10/2: 000084: Jun 1 2006 18:19:00.979 EDT: GTP-SR:State of Redundancy Context is Initialized


DB-809


MWAM 10/2: 000085: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Event CGF Ready, Sub Event No Sub Event MWAM 10/2: 000086: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Removing element from state-list Initialized, final count 1 MWAM 10/2: 000087: Jun 1 2006 18:19:00.979 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 3 MWAM 10/2: 000088: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Invalid shdb 0x0 MWAM 10/2: 000089: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Transition CG 10.0.250.114 to (state 0) MWAM 10/2: 000090: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Invalid shdb 0x0 MWAM 10/2: 000091: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Transition CG 10.0.250.115 to (state 0) MWAM 10/2: 000092: Jun 1 2006 18:19:00.983 EDT: GTP-SR: SHDB AVL tree cleanup to start in 10 sec MWAM 10/2: 000093: Jun 1 2006 18:19:00.983 EDT: GTP-SR: Completion of Standby-to-Active transition MWAM 10/2: 000094: Jun 1 2006 18:19:00.983 EDT: GTP-SR: Chkpt Status Flow Off Indication MWAM 10/2: 000095: Jun 1 2006 18:19:00.987 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.301 Grp 51 state Standby -> Active MWAM 10/2: 000096: Jun 1 2006 18:19:00.987 EDT: GTP-SR: RF_Status=400-RF_STATUS_PEER_PRESENCE RFState=13-ACTIVE operand=0 RFPeerState=13-ACTIVE MWAM 10/2: 000097: Jun 1 2006 18:19:00.987 EDT: GTP-SR: zero elements to move to other list MWAM 10/2: 000098: Jun 1 2006 18:19:00.987 EDT: GTP-SR: zero elements to move to other list MWAM 10/2: 000099: Jun 1 2006 18:19:00.987 EDT: GTP-SR: RF_Status=401-RF_STATUS_PEER_COMM RFState=13-ACTIVE operand=0 RFPeerState=1-DISABLED MWAM 10/2: 000100: Jun 1 2006 18:19:01.107 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1151 Grp 51 state Standby -> Active MWAM 10/2: 000101: Jun 1 2006 18:19:01.155 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.250 Grp 51 state Standby -> Active MWAM 10/2: 000102: Jun 1 2006 18:19:01.295 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1101 Grp 51 state Standby -> Active MWAM 10/2: 000103: Jun 1 2006 18:19:01.355 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1251 Grp 51 state Standby -> Active MWAM 10/2: 000104: Jun 1 2006 18:19:01.451 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1201 Grp 51 state Standby -> Active MWAM 10/2: 000105: Jun 1 2006 18:19:01.459 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.220 Grp 51 state Standby -> Active Router-2# MWAM 10/2: 000106: Jun 1 2006 18:19:10.983 EDT: GTP-SR: SHDB AVL tree cleanup has 3 nodes removed, 0 leftover Router-a# Router-a# Router-a# MWAM 10/2: 000107: Jun 1 2006 18:20:25.947 EDT: GTP-SR: Chkpt Status Flow Off Indication MWAM 10/2: 000108: Jun 1 2006 18:20:25.947 EDT: GTP-SR: RF_Status=400-RF_STATUS_PEER_PRESENCE RFState=13-ACTIVE operand=1 RFPeerState=1-DISABLED MWAM 10/2: 000109: Jun 1 2006 18:20:25.947 EDT: GTP-SR: RF_Status=401-RF_STATUS_PEER_COMM RFState=13-ACTIVE operand=1 RFPeerState=1-DISABLED MWAM 10/2: 000110: Jun 1 2006 18:20:25.947 EDT: GTP-SR: RF_Event=300-RF_PROG_PLATFORM_SYNC RFState=13-ACTIVE operand=0 RFPeerState=0-UNKNOWN MWAM 10/2: 000111: Jun 1 2006 18:20:25.947 EDT: GTP-SR: Received RF Progression Platform Sync MWAM 10/2: 000112: Jun 1 2006 18:20:53.899 EDT: GTP-SR: RF_Event=102-RF_PROG_STANDBY_CONFIG RFState=13-ACTIVE operand=0 RFPeerState=5-STANDBY COLD-CONFIG MWAM 10/2: 000113: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Received RF Progression Standby Config MWAM 10/2: 000114: Jun 1 2006 18:20:53.899 EDT: GTP-SR: RF_Event=103-RF_PROG_STANDBY_FILESYS RFState=13-ACTIVE operand=0 RFPeerState=6-STANDBY COLD-FILESYS MWAM 10/2: 000115: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Received RF Progression Stadnby Filesys


DB-810

May 2008


MWAM 10/2: 000116: Jun 1 2006 18:20:53.899 EDT: GTP-SR: RF_Event=104-RF_PROG_STANDBY_BULK RFState=13-ACTIVE operand=0 RFPeerState=7-STANDBY COLD-BULK MWAM 10/2: 000117: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Received RF Progression Standby Bulk MWAM 10/2: 000118: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Active GGSN sending Bulk Sync finished Msg MWAM 10/2: 000119: Jun 1 2006 18:20:53.899 EDT: GTP-SR: packing csg_path vaddr: 10.0.250.91 MWAM 10/2: 000120: Jun 1 2006 18:20:53.899 EDT: GTP-SR: packing csg_path port: 4386 MWAM 10/2: 000121: Jun 1 2006 18:20:53.899 EDT: GTP-SR: packing csg_path state: 1 MWAM 10/2: 000122: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Ckpt Message was sucessfully sent MWAM 10/2: 000123: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 2 MWAM 10/2: 000124: Jun 1 2006 18:20:53.899 EDT: GTP-SR: adding element in state-list Synched, final count 1 MWAM 10/2: 000125: Jun 1 2006 18:20:53.899 EDT: GTP-SR: sync next charging id 0x1C0AA436, local rsn 0x6B76EBDE MWAM 10/2: 000126: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Packing Pair Boot time 21:29:21 EDT Aug 19 2000 MWAM 10/2: 000127: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Packing Switcover Count 3 MWAM 10/2: 000128: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Packing local restart_count 21 MWAM 10/2: 000129: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Ckpt Message was sucessfully sent MWAM 10/2: 000130: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 1 MWAM 10/2: 000131: Jun 1 2006 18:20:53.899 EDT: GTP-SR: adding element in state-list Synched, final count 2 MWAM 10/2: 000132: Jun 1 2006 18:20:53.899 EDT: GTP-SR: sync cgf gw 10.0.250.114, operatemode NOT ACTIVE, nextseq 0x7530 MWAM 10/2: 000133: Jun 1 2006 18:20:53.899 EDT: GTP-SR: sync cgf gw 10.0.250.115, operatemode NOT ACTIVE, nextseq 0x7530 MWAM 10/2: 000134: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Ckpt Message was sucessfully sent MWAM 10/2: 000135: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 0 MWAM 10/2: 000136: Jun 1 2006 18:20:53.899 EDT: GTP-SR: adding element in state-list Synched, final count 3 MWAM 10/2: 000137: Jun 1 2006 18:20:53.899 EDT: GTP-SR:Active took time of 0 msec to transfer data for bulk sync MWAM 10/2: 000138: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Empty list to sync MWAM 10/2: 000139: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Redundancy RF Event Received is Standby Bulk Sync End MWAM 10/2: 000140: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Redundancy Event is Invalid MWAM 10/2: 000141: Jun 1 2006 18:20:53.899 EDT: GTP-SR: RF_Event=105-RF_PROG_STANDBY_HOT RFState=13-ACTIVE operand=0 RFPeerState=8-STANDBY HOT MWAM 10/2: 000142: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Received RF Progression Standby Hot Router-b Router-b#show gprs redundancy GPRS redundancy is enabled and Unit-Status is Active Redundancy Transport Infrastructure status Redundancy Infrastructure state: Peer Redundancy Infrastructure state: GGSN Redundancy system up since: Time of last switchover: Total Number of Switchovers:

ACTIVE STANDBY HOT 21:29:21 EDT Aug 19 2000 3

GPRS Redundancy Statistics Last cleared: never CheckPointed-To-Standby Statistics Total Number of Messages: Number of Context Setup messages:

3 0


DB-811


Number Number Number Number Number Number Number Number Number

of of of of of of of of of

Context Modify messages: Context Remove messages: Path Setup messages: Path Modify messages: Path Remove messages: CGF Ready messages: CGF Modify messages: CGF Remove messages: Internal State messages:

0 0 0 0 0 1 0 0 1

Example 2

The following sample outputs is for PDP context setup, prepaid user traffic, and then PDP context teardown. The debug is given for both Active and Standby GGSN. There is no GGSN switchover. Active GGSN: Router-a#debug gprs redundancy GPRS CF packets debugging is on GPRS CF events debugging is on GPRS CF errors debugging is on GPRS CF debug debugging is on Router-a#show gprs redundancy GPRS redundancy is enabled and Unit-Status is Active Redundancy Transport Infrastructure status Redundancy Infrastructure state: Peer Redundancy Infrastructure state: GGSN Redundancy system up since: Time of last switchover: Total Number of Switchovers:

ACTIVE STANDBY HOT 21:29:21 EDT Aug 19 2000 4

GPRS Redundancy Statistics Last cleared: never CheckPointed-To-Standby Statistics Total Number of Messages: Number of Context Setup messages: Number of Context Modify messages: Number of Context Remove messages: Number of Path Setup messages: Number of Path Modify messages: Number of Path Remove messages: Number of CGF Ready messages: Number of CGF Modify messages: Number of CGF Remove messages: Number of Internal State messages: Router-a# MWAM 10/2: 000073: Aug 24 2000 23:18:55.947 (0x24D2FC3C) is (0x3A000001) MWAM 10/2: 000074: Aug 24 2000 23:18:55.963 context MWAM 10/2: 000075: Aug 24 2000 23:18:55.963 Initialized, final count 2 MWAM 10/2: 000076: Aug 24 2000 23:18:55.963 context MWAM 10/2: 000077: Aug 24 2000 23:18:55.963 Initialized, final count 3 MWAM 10/2: 000078: Aug 24 2000 23:18:55.963 Context Event Path Setup, Context Sub Event

3 0 0 0 0 0 0 1 0 0 1

EDT: GTP-SR:pdpmcb handle for pdpmcb EDT: GTP-SR: Need to allocate redundancy EDT: GTP-SR: adding element in state-list EDT: GTP-SR: Need to allocate redundancy EDT: GTP-SR: adding element in state-list EDT: GTP-SR:Context Type No Sub Event

Path, Handler Sync,


DB-812

May 2008


MWAM 10/2: 000079: Aug 24 2000 23:18:55.963 Initialized MWAM 10/2: 000080: Aug 24 2000 23:18:55.963 Sub Event MWAM 10/2: 000081: Aug 24 2000 23:18:55.963 Initialized, final count 2 MWAM 10/2: 000082: Aug 24 2000 23:18:55.963 Dynamic Sync Ready, final count 1 MWAM 10/2: 000083: Aug 24 2000 23:18:55.963 context MWAM 10/2: 000084: Aug 24 2000 23:18:55.963 Initialized, final count 3 MWAM 10/2: 000085: Aug 24 2000 23:18:55.963 Context Event Path Setup, Context Sub Event MWAM 10/2: 000086: Aug 24 2000 23:18:55.963 Initialized MWAM 10/2: 000087: Aug 24 2000 23:18:55.963 Sub Event MWAM 10/2: 000088: Aug 24 2000 23:18:55.963 Initialized, final count 2 MWAM 10/2: 000089: Aug 24 2000 23:18:55.963 Dynamic Sync Ready, final count 2 MWAM 10/2: 000090: Aug 24 2000 23:18:55.963 MWAM 10/2: 000091: Aug 24 2000 23:18:55.963 port 2123 MWAM 10/2: 000092: Aug 24 2000 23:18:55.963 port 2123 MWAM 10/2: 000093: Aug 24 2000 23:18:55.963 MWAM 10/2: 000094: Aug 24 2000 23:18:55.963 MWAM 10/2: 000095: Aug 24 2000 23:18:55.963 pathcb->restart_count_remote 1 MWAM 10/2: 000096: Aug 24 2000 23:18:55.963 create: allowed: 63, packed: 23 MWAM 10/2: 000097: Aug 24 2000 23:18:55.963 MWAM 10/2: 000098: Aug 24 2000 23:18:55.963 Dynamic Sync Ready, final count 1 MWAM 10/2: 000099: Aug 24 2000 23:18:55.963 Synched, final count 4 MWAM 10/2: 000100: Aug 24 2000 23:18:55.963 MWAM 10/2: 000101: Aug 24 2000 23:18:55.963 port 2152 MWAM 10/2: 000102: Aug 24 2000 23:18:55.963 port 2152 MWAM 10/2: 000103: Aug 24 2000 23:18:55.967 MWAM 10/2: 000104: Aug 24 2000 23:18:55.967 MWAM 10/2: 000105: Aug 24 2000 23:18:55.967 pathcb->restart_count_remote 0 MWAM 10/2: 000106: Aug 24 2000 23:18:55.967 create: allowed: 63, packed: 23 MWAM 10/2: 000107: Aug 24 2000 23:18:55.967 MWAM 10/2: 000108: Aug 24 2000 23:18:55.967 Dynamic Sync Ready, final count 0 MWAM 10/2: 000109: Aug 24 2000 23:18:55.967 Synched, final count 5 MWAM 10/2: 000110: Aug 24 2000 23:18:55.967 MWAM 10/2: 000111: Aug 24 2000 23:18:55.967 MWAM 10/2: 000112: Aug 24 2000 23:19:01.583 ID 4 username 100000000000000 on APN ms-apn MWAM 10/2: 000113: Aug 24 2000 23:19:01.583 context MWAM 10/2: 000114: Aug 24 2000 23:19:01.583 Initialized, final count 3 MWAM 10/2: 000115: Aug 24 2000 23:19:01.583 Initialized, final count 2

EDT: GTP-SR:State of Redundancy Context is EDT: GTP-SR: Event Path Setup, Sub Event No EDT: GTP-SR: Removing element from state-list EDT: GTP-SR: adding element in state-list EDT: GTP-SR: Need to allocate redundancy EDT: GTP-SR: adding element in state-list EDT: GTP-SR:Context Type Path, Handler Sync, No Sub Event EDT: GTP-SR:State of Redundancy Context is EDT: GTP-SR: Event Path Setup, Sub Event No EDT: GTP-SR: Removing element from state-list EDT: GTP-SR: adding element in state-list EDT: GTP-SR:packing pathcb->gtpv 1 EDT: GTP-SR:Local IP address 166.11.0.11, and EDT: GTP-SR:Remote IP address 10.10.50.3, and EDT: GTP-SR:packing pathcb->num_data_socks 0 EDT: GTP-SR:packing pathcb->flags 9 EDT: GTP-SR:packing EDT: GTP-SR: Different lengths during path EDT: GTP-SR: Ckpt Message was sucessfully sent EDT: GTP-SR: Removing element from state-list EDT: GTP-SR: adding element in state-list EDT: GTP-SR:packing pathcb->gtpv 1 EDT: GTP-SR:Local IP address 166.11.0.11, and EDT: GTP-SR:Remote IP address 10.10.50.3, and EDT: GTP-SR:packing pathcb->num_data_socks 0 EDT: GTP-SR:packing pathcb->flags 8 EDT: GTP-SR:packing EDT: GTP-SR: Different lengths during path EDT: GTP-SR: Ckpt Message was sucessfully sent EDT: GTP-SR: Removing element from state-list EDT: GTP-SR: adding element in state-list EDT: GTP-SR: Empty list to sync EDT: GTP-SR: Empty list to sync EDT: GTP-SR: Creating red context for category EDT: GTP-SR: Need to allocate redundancy EDT: GTP-SR: adding element in state-list EDT: GTP-SR: Removing element from state-list


DB-813


MWAM 10/2: 000116: Aug 24 2000 23:19:01.583 EDT: GTP-SR: adding element in state-list Synched, final count 6 MWAM 10/2: 000117: Aug 24 2000 23:19:01.583 EDT: GPRS:0100000000000050:shdb 0x95000008 created for category 4 (handle 0xD0000001) MWAM 10/2: 000118: Aug 24 2000 23:19:01.591 EDT: GTP-SR: Don't checkpoint QP4QR Clear for Create/Update after a Quota Push Resp MWAM 10/2: 000119: Aug 24 2000 23:19:01.591 EDT: GTP-SR:Context Type PDP, Handler Sync, Context Event Context Setup, Context Sub Event No Sub Event MWAM 10/2: 000120: Aug 24 2000 23:19:01.591 EDT: GTP-SR:State of Redundancy Context is Initialized MWAM 10/2: 000121: Aug 24 2000 23:19:01.591 EDT: GTP-SR: Event Context Setup, Sub Event No Sub Event MWAM 10/2: 000122: Aug 24 2000 23:19:01.591 EDT: GTP-SR: Removing element from state-list Initialized, final count 1 MWAM 10/2: 000123: Aug 24 2000 23:19:01.591 EDT: GTP-SR: adding element in state-list Dynamic Sync Ready, final count 1 MWAM 10/2: 000124: Aug 24 2000 23:19:01.591 EDT: GTP-SR: for pdpmcb: 221 bytes to be packed MWAM 10/2: 000125: Aug 24 2000 23:19:01.591 EDT: GTP-SR: pdpmcb bitmap = 14346 MWAM 10/2: 000126: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->user-name 91100000000000000 MWAM 10/2: 000127: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->msisdn 9101000000000000F000 MWAM 10/2: 000128: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->selection_mode 0 MWAM 10/2: 000129: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->remove_staticIP 0 MWAM 10/2: 000130: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->llcframenum 0 MWAM 10/2: 000131: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->idle_timeout 3600 MWAM 10/2: 000132: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->session_timeout 0 MWAM 10/2: 000133: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpmcb_handle 973078529 MWAM 10/2: 000134: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->shdb 2080374789 MWAM 10/2: 000135: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing apn_name ms-apn MWAM 10/2: 000136: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing apnvalue ms-apn MWAM 10/2: 000137: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->teid 4194305 MWAM 10/2: 000138: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->imsi 01000000000000F0 MWAM 10/2: 000139: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.static_addr_allocated 0 MWAM 10/2: 000140: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.dynamic_addr_allocated 1 MWAM 10/2: 000141: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.dynamic_addr_requested 1 MWAM 10/2: 000142: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.addr_source 3 MWAM 10/2: 000143: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.allocated_prefix_len 16 MWAM 10/2: 000144: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.aggregate_prefix_len 16 MWAM 10/2: 000145: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.pdp_type_org 1 MWAM 10/2: 000146: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.pdp_type_num 33 MWAM 10/2: 000147: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.addrlen 6 MWAM 10/2: 000148: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb-ggsn_addr_si 166.11.0.11 MWAM 10/2: 000149: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb-ggsn_addr_data 166.11.0.11 MWAM 10/2: 000150: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->msisdn_len 9nGTP-SR:packing aaa charging profile index -1, MWAM 10/2: 000151: Aug 24 2000 23:19:01.591 EDT: GTP-SR:pdpmcb encoded len_t 0 MWAM 10/2: 000152: Aug 24 2000 23:19:01.591 EDT: GTP-SR: pdpcb bitmap = 0 MWAM 10/2: 000153: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_cntl_remote 1 MWAM 10/2: 000154: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_data_local 4194306


DB-814

May 2008


MWAM 10/2: 000155: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_data_remote 1000 MWAM 10/2: 000156: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->tid 0100000000000050 MWAM 10/2: 000157: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing naspi = 5 MWAM 10/2: 000158: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->internal_flags 9175041 MWAM 10/2: 000159: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->mnrgflag 0 MWAM 10/2: 000160: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->open_cdr_sent 0 MWAM 10/2: 000161: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->charging_reserved 0 MWAM 10/2: 000162: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->pri 1 MWAM 10/2: 000163: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fastswitchable 0 MWAM 10/2: 000164: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb-sgsn_addr_sig 10.10.50.3 MWAM 10/2: 000165: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb-sgsn_addr_data 10.10.50.3 MWAM 10/2: 000166: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->sequence_sig 1 MWAM 10/2: 000167: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_sig_up 0 MWAM 10/2: 000168: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_data1_up 0 MWAM 10/2: 000169: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_sig_down 0 MWAM 10/2: 000170: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_data1_down 0 MWAM 10/2: 000171: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_data2 0 MWAM 10/2: 000172: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->cause 128 MWAM 10/2: 000173: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->restart_count 0 MWAM 10/2: 000174: Aug 24 2000 23:19:01.591 EDT: GTP-SR: packing pdpcb->create_time Aug 24 2000 23:18:56 MWAM 10/2: 000175: Aug 24 2000 23:19:01.591 EDT: GTP-SR: packing pdpcb->last_access_time Aug 24 2000 23:18:56 MWAM 10/2: 000176: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->gtpv1_qos_req.qos_profile 152109353l MWAM 10/2: 000177: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->gtpv1_qos_neg.qos_profile 152109353l MWAM 10/2: 000178: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_cntl_remote 1 MWAM 10/2: 000179: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_data_local 4194306 MWAM 10/2: 000180: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_data_remote 1000 MWAM 10/2: 000181: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->charging_id 471179447 MWAM 10/2: 000182: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->cdr_recseqnum 0 MWAM 10/2: 000183: Aug 24 2000 23:19:01.591 EDT: GTP-SR: packing of pdpcb->reorder_required FF MWAM 10/2: 000184: Aug 24 2000 23:19:01.591 EDT: GPRS:0100000000000050: GTP-SR: Successfully pack PDP MWAM 10/2: 000185: Aug 24 2000 23:19:01.591 EDT: GTP-SR: rulebase ID MS packed MWAM 10/2: 000186: Aug 24 2000 23:19:01.591 EDT: GTP-SR: cc_session ccfh 0 failover_supported 1 reqnum 1 packed MWAM 10/2: 000187: Aug 24 2000 23:19:01.591 EDT: GTP-SR: cc_session dest_host ips-clcis1.cisco.com dest_realm cisco.com packed MWAM 10/2: 000188: Aug 24 2000 23:19:01.591 EDT: GTP-SR: category ID 4 packed: MWAM 10/2: 000189: Aug 24 2000 23:19:01.591 EDT: GTP-SR: sync data len 164 MWAM 10/2: 000190: Aug 24 2000 23:19:01.591 EDT: GTP-SR: active shdb 0x95000008 MWAM 10/2: 000191: Aug 24 2000 23:19:01.591 EDT: GTP-SR: CSG session ID 27599459844129 MWAM 10/2: 000192: Aug 24 2000 23:19:01.591 EDT: GTP-SR: chrg last svc rec seqnum 0 MWAM 10/2: 000193: Aug 24 2000 23:19:01.591 EDT: GTP-SR: category state AUTHORIZED MWAM 10/2: 000194: Aug 24 2000 23:19:01.591 EDT: GTP-SR: category state trigger flags 0x3 MWAM 10/2: 000195: Aug 24 2000 23:19:01.591 EDT: GTP-SR: category sub flags 0x0 MWAM 10/2: 000196: Aug 24 2000 23:19:01.591 EDT: GTP-SR: sync flag 0x0 MWAM 10/2: 000197: Aug 24 2000 23:19:01.591 EDT: GTP-SR: quotas included MWAM 10/2: 000198: Aug 24 2000 23:19:01.591 EDT: GTP-SR: last req timestamp 0 MWAM 10/2: 000199: Aug 24 2000 23:19:01.591 EDT: GTP-SR: last req seqnum 0 MWAM 10/2: 000200: Aug 24 2000 23:19:01.595 EDT: GTP-SR: Ckpt Message was sucessfully sent


DB-815


MWAM 10/2: 000201: Aug 24 2000 23:19:01.595 EDT: GTP-SR: Removing element from state-list Dynamic Sync Ready, final count 0 MWAM 10/2: 000202: Aug 24 2000 23:19:01.595 EDT: GTP-SR: adding element in state-list Synched, final count 7 MWAM 10/2: 000203: Aug 24 2000 23:19:01.595 EDT: GTP-SR: Empty list to sync MWAM 10/2: 000204: Aug 24 2000 23:19:03.939 EDT: GTP-SR:Context Type PDP, Handler Sync, Context Event Context Setup, Context Sub Event No Sub Event MWAM 10/2: 000205: Aug 24 2000 23:19:03.939 EDT: GTP-SR:State of Redundancy Context is Synched MWAM 10/2: 000206: Aug 24 2000 23:19:03.939 EDT: GTP-SR: Event Context Setup, Sub Event No Sub Event MWAM 10/2: 000207: Aug 24 2000 23:19:04.463 EDT: GTP-SR: Checkpoint SGSN init deletion via a category before final MCB deletion MWAM 10/2: 000208: Aug 24 2000 23:19:04.463 EDT: GTP-SR:Context Type Category, Handler Update, Context Event Category update, Context Sub Event No Sub Event MWAM 10/2: 000209: Aug 24 2000 23:19:04.463 EDT: GTP-SR:State of Redundancy Context is Synched MWAM 10/2: 000210: Aug 24 2000 23:19:04.463 EDT: GTP-SR: Event Category update, Sub Event No Sub Event MWAM 10/2: 000211: Aug 24 2000 23:19:04.463 EDT: GTP-SR: MCB internal flags 0x5802 packed MWAM 10/2: 000212: Aug 24 2000 23:19:04.463 EDT: GTP-SR: cc_session reqnum 1 packed MWAM 10/2: 000213: Aug 24 2000 23:19:04.463 EDT: GTP-SR: category ID 4 packed: MWAM 10/2: 000214: Aug 24 2000 23:19:04.463 EDT: GTP-SR: sync data len 52 MWAM 10/2: 000215: Aug 24 2000 23:19:04.463 EDT: GTP-SR: active shdb 0x95000008 MWAM 10/2: 000216: Aug 24 2000 23:19:04.463 EDT: GTP-SR: CSG session ID 27599459844129 MWAM 10/2: 000217: Aug 24 2000 23:19:04.463 EDT: GTP-SR: chrg last svc rec seqnum 0 MWAM 10/2: 000218: Aug 24 2000 23:19:04.463 EDT: GTP-SR: category state PENDING_SERVICE_STOP MWAM 10/2: 000219: Aug 24 2000 23:19:04.463 EDT: GTP-SR: category state trigger flags 0x3 MWAM 10/2: 000220: Aug 24 2000 23:19:04.463 EDT: GTP-SR: category sub flags 0x0 MWAM 10/2: 000221: Aug 24 2000 23:19:04.463 EDT: GTP-SR: sync flag 0xA MWAM 10/2: 000222: Aug 24 2000 23:19:04.463 EDT: GTP-SR: quotas not included MWAM 10/2: 000223: Aug 24 2000 23:19:04.463 EDT: GTP-SR: last req timestamp 0 MWAM 10/2: 000224: Aug 24 2000 23:19:04.463 EDT: GTP-SR: last req seqnum 0 MWAM 10/2: 000225: Aug 24 2000 23:19:04.463 EDT: GTP-SR: Different lengths during category sync: allowed 188, packed 56 MWAM 10/2: 000226: Aug 24 2000 23:19:04.463 EDT: GTP-SR: Ckpt Message was sucessfully sent MWAM 10/2: 000227: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Checkpoint final MCB deletion after sending a CCR Final MWAM 10/2: 000228: Aug 24 2000 23:19:04.467 EDT: GTP-SR:Context Type PDP, Handler Delete, Context Event Context Remove, Context Sub Event No Sub Event MWAM 10/2: 000229: Aug 24 2000 23:19:04.467 EDT: GTP-SR:State of Redundancy Context is Synched MWAM 10/2: 000230: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Event Context Remove, Sub Event No Sub Event MWAM 10/2: 000231: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Checkpoint final MCB deletion MWAM 10/2: 000232: Aug 24 2000 23:19:04.467 EDT: GTP-SR:Context Type PDP, Handler Delete, Context Event Context Remove, Context Sub Event No Sub Event MWAM 10/2: 000233: Aug 24 2000 23:19:04.467 EDT: GTP-SR:State of Redundancy Context is Synched MWAM 10/2: 000234: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Event Context Remove, Sub Event No Sub Event MWAM 10/2: 000235: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Different lengths during PDP delete: allowed: 40, packed: 0 MWAM 10/2: 000236: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Ckpt Message was sucessfully sent MWAM 10/2: 000237: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Removing element from state-list Synched, final count 6 MWAM 10/2: 000238: Aug 24 2000 23:19:04.467 EDT: GTP-SR: adding element in state-list Delete, final count 1 MWAM 10/2: 000239: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Removing element from state-list Delete, final count 0 MWAM 10/2: 000240: Aug 24 2000 23:19:04.467 EDT: GTP-SR: No redundancy context for sending a down event to standby


DB-816

May 2008


MWAM 10/2: 000241: Aug 24 2000 23:19:04.471 EDT: GTP-SR: Removing element from state-list Synched, final count 5 Router-a# Router-a#

Standby GGSN: Router-b#debug gprs redundancy GPRS CF packets debugging is on GPRS CF events debugging is on GPRS CF errors debugging is on GPRS CF debug debugging is on Router-b#sh gprs redun GPRS redundancy is enabled and Unit-Status is Standby Redundancy Transport Infrastructure status Redundancy Infrastructure state: Peer Redundancy Infrastructure state: GGSN Redundancy system up since: Time of last switchover: Total Number of Switchovers:

STANDBY HOT ACTIVE 21:29:21 EDT Aug 19 2000 never 4

GPRS Redundancy Statistics Last cleared: never CheckPointed-From-Active Statistics Total Number of Messages: Number of Context Setup messages: Number of Context Modify messages: Number of Context Remove messages: Number of Path Setup messages: Number of Path Modify messages: Number of Path Remove messages: Number of CGF Ready messages: Number of CGF Modify messages: Number of CGF Remove messages: Number of Internal State messages: Router-b# MWAM 10/2: 000065: Jun 1 2006 Create Redundancy Context MWAM 10/2: 000066: Jun 1 2006 MWAM 10/2: 000067: Jun 1 2006 context MWAM 10/2: 000068: Jun 1 2006 Initialized, final count 4 MWAM 10/2: 000069: Jun 1 2006 org_len=63, len=63 MWAM 10/2: 000070: Jun 1 2006 8 4B MWAM 10/2: 000071: Jun 1 2006 0 0 MWAM 10/2: 000072: Jun 1 2006 0 0 MWAM 10/2: 000073: Jun 1 2006 0 MWAM 10/2: 000074: Jun 1 2006 MWAM 10/2: 000075: Jun 1 2006 port 2123 MWAM 10/2: 000076: Jun 1 2006 port 2123

3 0 0 0 0 0 0 1 0 0 1

18:28:06.591 EDT: GTP-SR: Redundancy RF Event Received is 18:28:06.591 EDT: GTP-SR: Redundancy Event is Path Setup 18:28:06.591 EDT: GTP-SR: Need to allocate redundancy 18:28:06.591 EDT: GTP-SR: adding element in state-list 18:28:06.591 EDT: GTP-SR Packet Dump: Len for dump: 18:28:06.591 EDT:

1

0

0

0

0

0

0

0

9

1

A6 B

0

B

18:28:06.591 EDT:

A

A

32 3

8

4B 1

0

0

0

0

0

0

0

18:28:06.591 EDT:

0

0

0

0

0

0

0

0

0

0

0

0

0

0

18:28:06.595 EDT:

0

0

0

0

0

0

0

0

0

0

0

0

0

0

18:28:06.595 EDT: GTP-SR: un-packing u_path->gtpv 1 18:28:06.595 EDT: GTP-SR: Local IP address 166.11.0.11, and 18:28:06.595 EDT: GTP-SR: Remote IP address 10.10.50.3, and


DB-817


MWAM 10/2: 000077: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->num_data_socks 0 MWAM 10/2: 000078: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->flags 9 MWAM 10/2: 000079: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing restart_count_remote 1 MWAM 10/2: 000080: Jun 1 2006 18:28:06.595 EDT: GTP-SR:Context Type Path, Handler Sync, Context Event Path Setup, Context Sub Event No Sub Event MWAM 10/2: 000081: Jun 1 2006 18:28:06.595 EDT: GTP-SR:State of Redundancy Context is Initialized MWAM 10/2: 000082: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Event Path Setup, Sub Event No Sub Event MWAM 10/2: 000083: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Removing element from state-list Initialized, final count 3 MWAM 10/2: 000084: Jun 1 2006 18:28:06.595 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 2 MWAM 10/2: 000085: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Redundancy RF Event Received is Create Redundancy Context MWAM 10/2: 000086: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Redundancy Event is Path Setup MWAM 10/2: 000087: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Need to allocate redundancy context MWAM 10/2: 000088: Jun 1 2006 18:28:06.595 EDT: GTP-SR: adding element in state-list Initialized, final count 4 MWAM 10/2: 000089: Jun 1 2006 18:28:06.595 EDT: GTP-SR Packet Dump: Len for dump: org_len=63, len=63 MWAM 10/2: 000090: Jun 1 2006 18:28:06.595 EDT: 1 0 0 0 0 0 0 0 8 1 A6 B 0 B 8 68 MWAM 10/2: 000091: Jun 1 2006 18:28:06.595 EDT: A A 32 3 8 68 0 0 0 0 0 0 0 0 0 0 MWAM 10/2: 000092: Jun 1 2006 18:28:06.595 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MWAM 10/2: 000093: Jun 1 2006 18:28:06.595 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MWAM 10/2: 000094: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->gtpv 1 MWAM 10/2: 000095: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Local IP address 166.11.0.11, and port 2152 MWAM 10/2: 000096: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Remote IP address 10.10.50.3, and port 2152 MWAM 10/2: 000097: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->num_data_socks 0 MWAM 10/2: 000098: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->flags 8 MWAM 10/2: 000099: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing restart_count_remote 0 MWAM 10/2: 000100: Jun 1 2006 18:28:06.595 EDT: GTP-SR:Context Type Path, Handler Sync, Context Event Path Setup, Context Sub Event No Sub Event MWAM 10/2: 000101: Jun 1 2006 18:28:06.595 EDT: GTP-SR:State of Redundancy Context is Initialized MWAM 10/2: 000102: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Event Path Setup, Sub Event No Sub Event MWAM 10/2: 000103: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Removing element from state-list Initialized, final count 3 MWAM 10/2: 000104: Jun 1 2006 18:28:06.595 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 3 MWAM 10/2: 000105: Jun 1 2006 18:28:12.223 EDT: GTP-SR: Redundancy RF Event Received is Create Redundancy Context MWAM 10/2: 000106: Jun 1 2006 18:28:12.223 EDT: GTP-SR: Redundancy Event is Context Setup MWAM 10/2: 000107: Jun 1 2006 18:28:12.223 EDT: GTP-SR: Need to allocate redundancy context MWAM 10/2: 000108: Jun 1 2006 18:28:12.223 EDT: GTP-SR: adding element in state-list Initialized, final count 4 MWAM 10/2: 000109: Jun 1 2006 18:28:12.223 EDT: GTP-SR Packet Dump: Len for dump: org_len=755, len=128 MWAM 10/2: 000110: Jun 1 2006 18:28:12.223 EDT: 1 1 39 31 31 30 30 30 30 30 30 30 30 30 30 30 MWAM 10/2: 000111: Jun 1 2006 18:28:12.223 EDT: 30 30 30 0 0 0 0 91 1 0 0 0 0 0 0 F0


DB-818

May 2008


MWAM 10/2: 0 0 MWAM 10/2: 63 69 73 MWAM 10/2: 0 0 MWAM 10/2: F0 B 1 MWAM 10/2: 0 0 MWAM 10/2: 6 0 MWAM 10/2:

000112: Jun

1 2006 18:28:12.223 EDT:

0

0

0

000113: Jun

1 2006 18:28:12.223 EDT:

000114: Jun

1 2006 18:28:12.227 EDT:

000115: Jun

1 2006 18:28:12.227 EDT:

000116: Jun

1 2006 18:28:12.227 EDT:

0

1

0

0

0

0

0

0

0

0

000117: Jun

1 2006 18:28:12.227 EDT:

0

0

0

1

1

0

0

0

3

10 10 1

000118: Jun

1 2006 18:28:12.227 EDT:

C0 23 1 63 6F 0 0

0

0

0

0

8

0

5

7C 0

E

10 0

0

0

0

0

0

63 69 73 63 6F 31 31 31 0

40 0

5

1

0 1

0 0

8 0

0 0

0 0

0

0 0

0

0 0

0

0

21 0

...

MWAM 10/2: 000119: Jun 1 2006 18:28:12.231 EDT: GTP-SR:pdpmcb handle for pdpmcb (0x24AA0CCC) is (0x41000001) MWAM 10/2: 000120: Jun 1 2006 18:28:12.231 EDT: GTP-SR: un-packing # of PDPs packed = 1 MWAM 10/2: 000121: Jun 1 2006 18:28:12.231 EDT: GTP-SR: un-packing pdpmcb->user-name 91100000000000000 MWAM 10/2: 000122: Jun 1 2006 18:28:12.231 EDT: GTP-SR: un-packing pdpmcb->msisdn 9101000000000000F000 MWAM 10/2: 000123: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->selection_mode 0 MWAM 10/2: 000124: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->remove_staticIP 0 MWAM 10/2: 000125: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->llcframenum 0 MWAM 10/2: 000126: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->idle_timeout 3600 MWAM 10/2: 000127: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->session_timeout 0 MWAM 10/2: 000128: Jun 1 2006 18:28:12.235 EDT: GTP-SR: pdpmcb bitmap = 30730 MWAM 10/2: 000129: Jun 1 2006 18:28:12.235 EDT: GTP-SR: apn name is ms-apn MWAM 10/2: 000130: Jun 1 2006 18:28:12.235 EDT: GTP-SR: packing pdpmcb->teid 4194305 MWAM 10/2: 000131: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->imsi 01000000000000F0 MWAM 10/2: 000132: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.pdp_addr 11.1.0.1 MWAM 10/2: 000133: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.static_addr_allocated 0 MWAM 10/2: 000134: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.dynamic_addr_allocated 1 MWAM 10/2: 000135: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.dynamic_addr_requested 1 MWAM 10/2: 000136: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.addr_source 3 MWAM 10/2: 000137: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.allocated_prefix_len 16 MWAM 10/2: 000138: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.aggregate_prefix_len 16 MWAM 10/2: 000139: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.pdp_type_org 1 MWAM 10/2: 000140: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.pdp_type_num 33 MWAM 10/2: 000141: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.addrlen 6 MWAM 10/2: 000142: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.dhcp_addr 0.0.0.0 MWAM 10/2: 000143: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb-ggsn_addr_si 166.11.0.11 MWAM 10/2: 000144: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb-ggsn_addr_data 166.11.0.11 MWAM 10/2: 000145: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->msisdn_len 9 MWAM 10/2: 000146: Jun 1 2006 18:28:12.247 EDT: GTP-SR: Got teid=4194305, as requested


DB-819


MWAM 10/2: 000147: Jun 1 2006 18:28:12.247 EDT: GTP-SR: un-packing pdpcb->gtpv1_qos_req.qos_profile 152109353l MWAM 10/2: 000148: Jun 1 2006 18:28:12.247 EDT: GTP-SR: un-packing pdpcb->gtpv1_qos_neg.qos_profile 152109353l MWAM 10/2: 000149: Jun 1 2006 18:28:12.247 EDT: GTP-SR: un-packing pdpcb bitmap = 0 MWAM 10/2: 000150: Jun 1 2006 18:28:12.247 EDT: GTP-SR: un-packing pdpcb->tid0100000000000050 MWAM 10/2: 000151: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing nsapi = 5 MWAM 10/2: 000152: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->internal_flags 9175041 MWAM 10/2: 000153: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->mnrgflag 0 MWAM 10/2: 000154: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->open_cdr_sent 0 MWAM 10/2: 000155: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->charging_reserved 0 MWAM 10/2: 000156: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->pri 1 MWAM 10/2: 000157: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->fastswitchable 0 MWAM 10/2: 000158: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb-sgsn_addr_sig 10.10.50.3 MWAM 10/2: 000159: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb-sgsn_addr_data 10.10.50.3 MWAM 10/2: 000160: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->sequence_sig 1 MWAM 10/2: 000161: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_sig_up 0 MWAM 10/2: 000162: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_data1_up 0 MWAM 10/2: 000163: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_sig_down 0 MWAM 10/2: 000164: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_data1_down 0 MWAM 10/2: 000165: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_data2 0 MWAM 10/2: 000166: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->cause 128 MWAM 10/2: 000167: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->restart_count 0 MWAM 10/2: 000168: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->create_time Apr 13 2006 01:25:25 MWAM 10/2: 000169: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->last_access_time Apr 13 2006 01:25:25 MWAM 10/2: 000170: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->teid_cntl_remote 1 MWAM 10/2: 000171: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->teid_data_local 4194306 MWAM 10/2: 000172: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->teid_data_remote 1000 MWAM 10/2: 000173: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->charging_id 471179447 MWAM 10/2: 000174: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->cdr_recseqnum 0 MWAM 10/2: 000175: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->reorder_required FF MWAM 10/2: 000176: Jun 1 2006 18:28:12.251 EDT: GTP-SR: We wanted teid 4194306, and got 4194306 MWAM 10/2: 000177: Jun 1 2006 18:28:12.251 EDT: GTP-SR: Got teid 4194306 as requested MWAM 10/2: 000178: Jun 1 2006 18:28:12.251 EDT: pdp_create_by_tid on standby:tid 100000050, pdp 24A90B24 MWAM 10/2: 000179: Jun 1 2006 18:28:12.251 EDT: GPRS:0100000000000050: GTP-SR: Successfully unpack PDP MWAM 10/2: 000180: Jun 1 2006 18:28:12.251 EDT: GTP-SR: rulebase ID MS unpacked MWAM 10/2: 000181: Jun 1 2006 18:28:12.251 EDT: GTP-SR: cc_session ccfh 0 failover_supported 1 reqnum 1 packed MWAM 10/2: 000182: Jun 1 2006 18:28:12.251 EDT: GTP-SR: new cc_session dest_host ips-clcis1.cisco.com unpacked MWAM 10/2: 000183: Jun 1 2006 18:28:12.251 EDT: GTP-SR: new cc_session dest_realm cisco.com unpacked


DB-820

May 2008


MWAM 10/2: 000184: Jun 1 2006 18:28:12.251 EDT: GTP-SR: Unpacking 1 categories MWAM 10/2: 000185: Jun 1 2006 18:28:12.251 EDT: GTP-SR: Unpacking category of ID 4 MWAM 10/2: 000186: Jun 1 2006 18:28:12.255 EDT: GTP-SR: Creating red context for category ID 4 username 100000000000000 on APN ms-apn MWAM 10/2: 000187: Jun 1 2006 18:28:12.255 EDT: GTP-SR: Need to allocate redundancy context MWAM 10/2: 000188: Jun 1 2006 18:28:12.255 EDT: GTP-SR: adding element in state-list Initialized, final count 5 MWAM 10/2: 000189: Jun 1 2006 18:28:12.255 EDT: GTP-SR: Removing element from state-list Initialized, final count 4 MWAM 10/2: 000190: Jun 1 2006 18:28:12.255 EDT: GTP-SR: adding element in state-list Synched, final count 1 MWAM 10/2: 000191: Jun 1 2006 18:28:12.255 EDT: GPRS:0100000000000050:shdb 0xC6000008 created for category 4 (handle 0xDE000001) MWAM 10/2: 000192: Jun 1 2006 18:28:12.255 EDT: GTP-SR: red context installed for the new category (shdb: active 0x95000008, standby 0xC6000008) MWAM 10/2: 000193: Jun 1 2006 18:28:12.255 EDT: GTP-SR: new category ID 4 unpacked: MWAM 10/2: 000194: Jun 1 2006 18:28:12.255 EDT: GTP-SR: sync data len 164 MWAM 10/2: 000195: Jun 1 2006 18:28:12.255 EDT: GTP-SR: active shdb 0x95000008 MWAM 10/2: 000196: Jun 1 2006 18:28:12.255 EDT: GTP-SR: CSG session ID 27599459844129 MWAM 10/2: 000197: Jun 1 2006 18:28:12.255 EDT: GTP-SR: chrg last svc rec seqnum 0 MWAM 10/2: 000198: Jun 1 2006 18:28:12.255 EDT: GTP-SR: category state AUTHORIZED MWAM 10/2: 000199: Jun 1 2006 18:28:12.255 EDT: GTP-SR: category state trigger flags 0x3 MWAM 10/2: 000200: Jun 1 2006 18:28:12.255 EDT: GTP-SR: category sub flags 0x0 MWAM 10/2: 000201: Jun 1 2006 18:28:12.255 EDT: GTP-SR: sync flag 0x0 MWAM 10/2: 000202: Jun 1 2006 18:28:12.255 EDT: GTP-SR: quotas included MWAM 10/2: 000203: Jun 1 2006 18:28:12.255 EDT: GTP-SR: last req timestamp 0 MWAM 10/2: 000204: Jun 1 2006 18:28:12.255 EDT: GTP-SR: last req seqnum 0 MWAM 10/2: 000205: Jun 1 2006 18:28:12.255 EDT: GTP-SR: address received from active with radius source is MWAM 10/2: 000206: Jun 1 2006 18:28:12.259 EDT: GTP-SR:Context Type PDP, Handler Sync, Context Event Context Setup, Context Sub Event No Sub Event MWAM 10/2: 000207: Jun 1 2006 18:28:12.259 EDT: GTP-SR:State of Redundancy Context is Initialized MWAM 10/2: 000208: Jun 1 2006 18:28:12.259 EDT: GTP-SR: Event Context Setup, Sub Event No Sub Event MWAM 10/2: 000209: Jun 1 2006 18:28:12.259 EDT: GTP-SR: Removing element from state-list Initialized, final count 3 MWAM 10/2: 000210: Jun 1 2006 18:28:12.259 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 4 MWAM 10/2: 000211: Jun 1 2006 18:28:15.091 EDT: GTP-SR: Redundancy RF Event Received is Update Redundancy Context MWAM 10/2: 000212: Jun 1 2006 18:28:15.091 EDT: GTP-SR: Redundancy Event is Category update MWAM 10/2: 000213: Jun 1 2006 18:28:15.091 EDT: GTP-SR: red context found (active shdb 0x95000008, standby shdb 0xC6000008) MWAM 10/2: 000214: Jun 1 2006 18:28:15.091 EDT: GTP-SR Packet Dump: Len for dump: org_len=188, len=128 MWAM 10/2: 000215: Jun 1 2006 18:28:15.091 EDT: 7C 0 0 5 0 0 58 2 0 0 0 1 0 34 34 0 MWAM 10/2: 000216: Jun 1 2006 18:28:15.091 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 95 MWAM 10/2: 000217: Jun 1 2006 18:28:15.091 EDT: 0 0 8 0 0 19 1A 0 0 0 21 0 0 0 0 0 MWAM 10/2: 000218: Jun 1 2006 18:28:15.091 EDT: 0 0 9 0 0 0 3 0 0 A 0 0 0 0 0 0 MWAM 10/2: 000219: Jun 1 2006 18:28:15.091 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MWAM 10/2: 000220: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MWAM 10/2: 000221: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0


DB-821


MWAM 10/2: 000222: Jun 0 0 MWAM 10/2: 000223: Jun

1 2006 18:28:15.095 EDT: 1 2006 18:28:15.095 EDT:

0

0

0

0

0

0

0

0

0

0

0

0

0

0

...

MWAM 10/2: 000224: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category found with handle 0xDE000001 shdbs: active 0x95000008 standby 0xC6000008 (MCB shdbs: active 0x7C000005, standby 0xC6000008) MWAM 10/2: 000225: Jun 1 2006 18:28:15.095 EDT: GTP-SR: MCB internal flags 0x5802 unpacked MWAM 10/2: 000226: Jun 1 2006 18:28:15.095 EDT: GTP-SR: cc_session reqnum 1 unpacked and installed MWAM 10/2: 000227: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Unpacking category of ID 4 MWAM 10/2: 000228: Jun 1 2006 18:28:15.095 EDT: GTP-SR: sync obj created in prep for MCB deletion MWAM 10/2: 000229: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category ID 4 unpacked: MWAM 10/2: 000230: Jun 1 2006 18:28:15.095 EDT: GTP-SR: sync data len 52 MWAM 10/2: 000231: Jun 1 2006 18:28:15.095 EDT: GTP-SR: active shdb 0x95000008 MWAM 10/2: 000232: Jun 1 2006 18:28:15.095 EDT: GTP-SR: CSG session ID 27599459844129 MWAM 10/2: 000233: Jun 1 2006 18:28:15.095 EDT: GTP-SR: chrg last svc rec seqnum 0 MWAM 10/2: 000234: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category state PENDING_SERVICE_STOP MWAM 10/2: 000235: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category state trigger flags 0x3 MWAM 10/2: 000236: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category sub flags 0x0 MWAM 10/2: 000237: Jun 1 2006 18:28:15.095 EDT: GTP-SR: sync flag 0xA MWAM 10/2: 000238: Jun 1 2006 18:28:15.095 EDT: GTP-SR: quotas not included MWAM 10/2: 000239: Jun 1 2006 18:28:15.095 EDT: GTP-SR: last req timestamp 0 MWAM 10/2: 000240: Jun 1 2006 18:28:15.095 EDT: GTP-SR: last req seqnum 0 MWAM 10/2: 000241: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Redundancy RF Event Received is Redundancy Context Delete MWAM 10/2: 000242: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Redundancy Event is Context Remove MWAM 10/2: 000243: Jun 1 2006 18:28:15.095 EDT: GTP-SR Packet Dump: Len for dump: org_len=40, len=40 MWAM 10/2: 000244: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MWAM 10/2: 000245: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MWAM 10/2: 000246: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 MWAM 10/2: 000247: Jun 1 2006 18:28:15.095 EDT: GPRS:GTP-SR: Deleting v1 MCB on the standby MWAM 10/2: 000248: Jun 1 2006 18:28:15.095 EDT: GPRS:0100000000000050:GTP-SR: Deleting v1 PDP on the standby MWAM 10/2: 000249: Jun 1 2006 18:28:15.095 EDT: GTP-SR: MCB deletion sync obj deleted MWAM 10/2: 000250: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Removing element from state-list Synched, final count 0 MWAM 10/2: 000251: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 3 MWAM 10/2: 000252: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Redundancy RF Event Received is Redundancy Context Delete MWAM 10/2: 000253: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Redundancy Event is Path Remove MWAM 10/2: 000254: Jun 1 2006 18:29:15.103 EDT: GTP-SR:Context Type Path, Handler Delete, Context Event Path Remove, Context Sub Event No Sub Event MWAM 10/2: 000255: Jun 1 2006 18:29:15.103 EDT: GTP-SR:State of Redundancy Context is Bulk Synch Ready MWAM 10/2: 000256: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Event Path Remove, Sub Event No Sub Event MWAM 10/2: 000257: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 2 MWAM 10/2: 000258: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Redundancy RF Event Received is Redundancy Context Delete MWAM 10/2: 000259: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Redundancy Event is Path Remove MWAM 10/2: 000260: Jun 1 2006 18:29:15.103 EDT: GTP-SR:Context Type Path, Handler Delete, Context Event Path Remove, Context Sub Event No Sub Event


DB-822

May 2008


MWAM 10/2: Bulk Synch MWAM 10/2: Sub Event MWAM 10/2: Bulk Synch

Related Commands

000261: Jun Ready 000262: Jun

1 2006 18:29:15.103 EDT: GTP-SR:State of Redundancy Context is 1 2006 18:29:15.103 EDT: GTP-SR: Event Path Remove, Sub Event No

000263: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Removing element from state-list Ready, final count 1

Command

Description

clear gprs redundancy statistics

Clears statistics related to GTP-SR.

gprs redundancy

Enables GTP-SR on a GGSN.

gprs redundancy Configures the window size used to determine when the CDR record charging sync-window sequence number needs to be synchronized to the Standby GGSN. cdr rec-seqnum gprs redundancy Configures the window size used to determine when the GTP’ sequence charging sync-window number needs to be synchronized to the Standby GGSN. gtpp seqnum show gprs redundancy

Displays statistics related to GTP-SR.


DB-823

Debug Commands debug gvrp

debug gvrp To display GVRP debugging information, use the debug gvrp command in privileged EXEC mode. To disable debugging outpu, use the no form of this command. debug gvrp {all | config | error | event | ha | packets | switch} no debug gvrp

Syntax Description

all

(Optional) Enables all levels of debugging

config

(Optional) Displays user configuration.

error

(Optional) Enables error level debugging.

event ha packets

(Optional) Enables packet level debugging.

switch

(Optional) Enables switch level debugging.

Command Default

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRB


Usage Guidelines

Conditional interface debugging can be used to limit the debugging output messages related to an interface.

Examples

The following example shows how to enable all levels of debugging: debug gvrp all

Related Commands

Command

Description

show gvrp interface

Displays details of the adininstrative and operational GVRP states of all or one particular .1Q trunk port in the device.

show gvrp summary

Displays the GVRP configuration at the device leve.


DB-824

May 2008

Debug Commands debug h225 asn1

debug h225 asn1 To display ASN1 contents of RAS and Q.931 messages, use the debug h255 asn1 privileged EXEC command. The no form of this command disables debugging output. debug h255 asn1 no debug h255 asn1

Syntax Description


Command History

Release

Modification

11.3(2)NA


12.0(3)T


12.2SX


Usage Guidelines

Caution

Examples

This command slows down the system considerably. Connections may time out.

Example 1

The following output shows two proxy call scenarios. A trace is collected on the gatekeeper with ASN1 turned on. The call is being established. Router# debug h225 asn1 H.225 ASN1 Messages debugging is on Router#24800006 03C00030 00300036 00380041 00450037 00430030 00300030 00300030 00300030 00310140 0F007000 74006500 6C003200 33004000 7A006F00 6E006500 32002E00 63006F00 6D020180 AAAA4006 00700074 0065006C 00320031 0033401E 0000015F C8490FB4 B9D111BF AF0060B0 00E94500 value RasMessage ::= admissionRequest : { requestSeqNum 7, callType pointToPoint : NULL, endpointIdentifier "0068AE7C00000001", destinationInfo { h323-ID : "[email protected]" }, srcInfo { e164 : "7777", h323-ID : "ptel213" }, bandWidth 7680, callReferenceValue 1,


DB-825


conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H, activeMC FALSE, answerCall FALSE } value RasMessage ::= admissionConfirm : { requestSeqNum 7, bandWidth 7680, callModel direct : NULL, destCallSignalAddress ipAddress : { ip '65000001'H, port 1720 }, irrFrequency 30 } 29000006 401E0000 65000001 06B8001D 2480001D 03C00030 00300036 00380041 00390036 00300030 00300030 00320140 0F007000 74006500 6C003200 33004000 32002E00 63006F00 6D014006 00700074 0065006C 00320031 C8490FB4 B9D111BF AF0060B0 00E94540 value RasMessage ::= admissionRequest : { requestSeqNum 30, callType pointToPoint : NULL, endpointIdentifier "0068A96000000002", destinationInfo { h323-ID : "[email protected]" }, srcInfo { h323-ID : "ptel213" }, bandWidth 640, callReferenceValue 1, conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H, activeMC FALSE, answerCall TRUE } value ACFnonStandardInfo ::= { srcTerminalAlias { e164 : "7777", h323-ID : "ptel213" }, dstTerminalAlias { h323-ID : "[email protected]" }, dstProxyAlias { h323-ID : "px2" }, dstProxySignalAddress { ip '66000001'H, port 1720 } } C00203AA AA800600 70007400 65006C00 32003100 3301800F 00320033 0040007A 006F006E 00650032 002E0063 006F006D 32660000 0106B8

00300030 00300030 7A006F00 6E006500 00334002 8000015F

00700074 0065006C 01800200 70007800


DB-826

May 2008


value RasMessage ::= admissionConfirm : { requestSeqNum 30, bandWidth 7680, callModel direct : NULL, destCallSignalAddress ipAddress : { ip '66000001'H, port 1720 }, irrFrequency 30, nonStandardData { nonStandardIdentifier h221NonStandard : { t35CountryCode 181, t35Extension 0, manufacturerCode 18 }, data 'C00203AAAA8006007000740065006C00320031003301800F007000740065006C003200 ...'H } } 2980001D 401E0000 66000001 06B8001D 40B50000 1247C002 03AAAA80 06007000 74006500 6C003200 31003301 800F0070 00740065 006C0032 00330040 007A006F 006E0065 0032002E 0063006F 006D0180 02007000 78003266 00000106 B8 24C0001E 03C00030 00300036 00380041 00390036 00300030 00300030 00300030 00300030 00320140 0F007000 74006500 6C003200 33004000 7A006F00 6E006500 32002E00 63006F00 6D006600 000106B8 020180AA AA400600 70007400 65006C00 32003100 33401E00 00435FC8 490FB4B9 D111BFAF 0060B000 E94500 value RasMessage ::= admissionRequest : { requestSeqNum 31, callType pointToPoint : NULL, endpointIdentifier "0068A96000000002", destinationInfo { h323-ID : "[email protected]" }, destCallSignalAddress ipAddress : { ip '66000001'H, port 1720 }, srcInfo { e164 : "7777", h323-ID : "ptel213" }, bandWidth 7680, callReferenceValue 67, conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H, activeMC FALSE, answerCall FALSE } value RasMessage ::= admissionConfirm : { requestSeqNum 31, bandWidth 7680, callModel direct : NULL, destCallSignalAddress ipAddress : { ip '66000001'H, port 1720


DB-827


}, irrFrequency 30 }

Example 2

The following output shows two proxy call scenarios. A trace is collected on the source proxy with ASN1 turned on. The call is being torn down Router# debug h225 asn1 H.225 ASN1 Messages debugging is on Router# value H323-UserInformation ::= { h323-uu-pdu { h323-message-body setup : { protocolIdentifier { 0 0 8 2250 0 1 }, sourceAddress { h323-ID : "ptel213" }, sourceInfo { terminal { }, mc FALSE, undefinedNode FALSE }, destinationAddress { h323-ID : "[email protected]" }, activeMC FALSE, conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H, conferenceGoal create : NULL, callType pointToPoint : NULL, sourceCallSignalAddress ipAddress : { ip '3200000C'H, port 1720 } } } } value RasMessage ::= admissionRequest : { requestSeqNum 30, callType pointToPoint : NULL, endpointIdentifier "0068A96000000002", destinationInfo { h323-ID : "[email protected]" }, srcInfo { h323-ID : "ptel213" }, bandWidth 640, callReferenceValue 1, conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H,


DB-828

May 2008


activeMC FALSE, answerCall TRUE } 2480001D 03C00030 00300036 00380041 00390036 00300030 00300030 00300030 00300030 00320140 0F007000 74006500 6C003200 33004000 7A006F00 6E006500 32002E00 63006F00 6D014006 00700074 0065006C 00320031 00334002 8000015F C8490FB4 B9D111BF AF0060B0 00E94540 2980001D 401E0000 66000001 06B8001D 40B50000 1247C002 03AAAA80 06007000 74006500 6C003200 31003301 800F0070 00740065 006C0032 00330040 007A006F 006E0065 0032002E 0063006F 006D0180 02007000 78003266 00000106 B8 value RasMessage ::= admissionConfirm : { requestSeqNum 30, bandWidth 7680, callModel direct : NULL, destCallSignalAddress ipAddress : { ip '66000001'H, port 1720 }, irrFrequency 30, nonStandardData { nonStandardIdentifier h221NonStandard : { t35CountryCode 181, t35Extension 0, manufacturerCode 18 }, data 'C00203AAAA8006007000740065006C00320031003301800F007000740065006C003200 ...'H } } C00203AA AA800600 70007400 65006C00 32003100 3301800F 00700074 0065006C 00320033 0040007A 006F006E 00650032 002E0063 006F006D 01800200 70007800 32660000 0106B8 value ACFnonStandardInfo ::= { srcTerminalAlias { e164 : "7777", h323-ID : "ptel213" }, dstTerminalAlias { h323-ID : "[email protected]" }, dstProxyAlias { h323-ID : "px2" }, dstProxySignalAddress { ip '66000001'H, port 1720 } } value RasMessage ::= admissionRequest : { requestSeqNum 31, callType pointToPoint : NULL, endpointIdentifier "0068A96000000002", destinationInfo {


DB-829


h323-ID : "[email protected]" }, destCallSignalAddress ipAddress : { ip '66000001'H, port 1720 }, srcInfo { e164 : "7777", h323-ID : "ptel213" }, bandWidth 7680, callReferenceValue 67, conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H, activeMC FALSE, answerCall FALSE } 24C0001E 03C00030 00300036 00380041 00390036 00300030 00300030 00320140 0F007000 74006500 6C003200 33004000 32002E00 63006F00 6D006600 000106B8 020180AA AA400600 32003100 33401E00 00435FC8 490FB4B9 D111BFAF 0060B000 2900001E 401E0000 66000001 06B8001D value RasMessage ::= admissionConfirm : { requestSeqNum 31, bandWidth 7680, callModel direct : NULL, destCallSignalAddress ipAddress : { ip '66000001'H, port 1720 }, irrFrequency 30 } value H323-UserInformation ::= { h323-uu-pdu { h323-message-body callProceeding : { protocolIdentifier { 0 0 8 2250 0 1 }, destinationInfo { gateway { protocol { h323 : { } } }, mc FALSE, undefinedNode FALSE } } } } 01000600 08914A00 01088001 2800 value H323-UserInformation ::= { h323-uu-pdu {

00300030 00300030 7A006F00 6E006500 70007400 65006C00 E94500


DB-830

May 2008


h323-message-body setup : { protocolIdentifier { 0 0 8 2250 0 1 }, sourceAddress { h323-ID : "ptel213" }, sourceInfo { vendor { vendor { t35CountryCode 181, t35Extension 0, manufacturerCode 18 } }, gateway { protocol { h323 : { } } }, mc FALSE, undefinedNode FALSE }, destinationAddress { h323-ID : "[email protected]" }, destCallSignalAddress ipAddress : { ip '66000001'H, port 1720 }, activeMC FALSE, conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H, conferenceGoal create : NULL, callType pointToPoint : NULL, sourceCallSignalAddress ipAddress : { ip '65000001'H, port 1720 }, remoteExtensionAddress h323-ID : "[email protected]" } } } 00B80600 08914A00 01014006 00700074 0065006C 00320031 40012800 01400F00 70007400 65006C00 32003300 40007A00 2E006300 6F006D00 66000001 06B8005F C8490FB4 B9D111BF 0E070065 00000106 B822400F 00700074 0065006C 00320033 00650032 002E0063 006F006D value H323-UserInformation ::= { h323-uu-pdu { h323-message-body callProceeding : { protocolIdentifier { 0 0 8 2250 0 1 },

00332800 6F006E00 AF0060B0 0040007A

B5000012 65003200 00E94500 006F006E


DB-831


destinationInfo { gateway { protocol { h323 : { } } }, mc FALSE, undefinedNode FALSE } } } } value H323-UserInformation ::= { h323-uu-pdu { h323-message-body alerting : { protocolIdentifier { 0 0 8 2250 0 1 }, destinationInfo { mc FALSE, undefinedNode FALSE } } } } value H323-UserInformation ::= { h323-uu-pdu { h323-message-body alerting : { protocolIdentifier { 0 0 8 2250 0 1 }, destinationInfo { mc FALSE, undefinedNode FALSE } } } } 03000600 08914A00 010000 value H323-UserInformation ::= { h323-uu-pdu { h323-message-body connect : { protocolIdentifier { 0 0 8 2250 0 1 }, h245Address ipAddress : { ip '66000001'H, port 11011 }, destinationInfo { gateway {


DB-832

May 2008


protocol { h323 : { } } }, mc FALSE, undefinedNode FALSE }, conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H } } } value H323-UserInformation ::= { h323-uu-pdu { h323-message-body connect : { protocolIdentifier { 0 0 8 2250 0 1 }, h245Address ipAddress : { ip '65000001'H, port 11007 }, destinationInfo { gateway { protocol { h323 : { } } }, mc FALSE, undefinedNode FALSE }, conferenceID '5FC8490FB4B9D111BFAF0060B000E945'H } } } 02400600 08914A00 01006500 00012AFF 08800128 005FC849 0FB4B9D1 11BFAF00 60B000E9 45

Example 3 The following output shows two proxy call scenarios. A trace is collected on a destination router where both destination proxy and destination Gatekeeper coexist. Both RAS and H.225 traces are enabled for one complete call. px2# RASLib::RASRecvData: successfully rcvd message of length 80 from 40.0.0.33:1585 RASLib::RASRecvData: LRQ rcvd from [40.0.0.33:1585] on sock [6880372] RASlib::ras_sendto: msg length 111 sent to 40.0.0.33 RASLib::RASSendLCF: LCF sent to 40.0.0.33 H225Lib::h225TAccept: TCP connection accepted from 101.0.0.1:11002 on socket [2] H225Lib::h225TAccept: Q.931 Call State is initialized to be [Null]. Hex representation of the received TPKT 030000A60802008005040488988CA56C0591373737377E008D0500B8060008914A000101400


DB-833


6007000740065006C0032003100332800B50000124001280001400F007000740065006C00320 0330040007A006F006E00650032002E0063006F006D006600000106B8003DC8490FB4B9D111B FAF0060B000E945000E07006500000106B822400F007000740065006C003200330040007A006 F006E00650032002E0063006F006D H225Lib::h225RecvData: Q.931 SETUP received from socket [2] H225Lib::h225RecvData: State changed to [Call Present]. RASlib::ras_sendto: msg length 119 sent to 102.0.0.1 RASLib::RASSendARQ: ARQ sent to 102.0.0.1 RASLib::RASRecvData: successfully rcvd message of length 119 from 102.0.0.1:24999 RASLib::RASRecvData: ARQ rcvd from [102.0.0.1:24999] on sock [0x68FC74] RASlib::ras_sendto: msg length 16 sent to 70.0.0.31 RASLib::RASSendACF: ACF sent to 70.0.0.31 RASLib::RASRecvData: successfully rcvd message of length 16 from 102.0.0.1:1719 RASLib::RASRecvData: ACF rcvd from [102.0.0.1:1719] on sock [0x67E6A4] RASlib::ras_sendto: msg length 119 sent to 102.0.0.1 RASLib::RASSendARQ: ARQ sent to 102.0.0.1 RASLib::RASRecvData: successfully rcvd message of length 119 from 102.0.0.1:24999 RASLib::RASRecvData: ARQ rcvd from [102.0.0.1:24999] on sock [0x68FC74] RASlib::ras_sendto: msg length 16 sent to 70.0.0.31 RASLib::RASSendACF: ACF sent to 70.0.0.31 RASLib::RASRecvData: successfully rcvd message of length 16 from 102.0.0.1:1719 RASLib::RASRecvData: ACF rcvd from [102.0.0.1:1719] on sock [0x67E6A4] Hex representation of the CALL PROCEEDING TPKT to send. 0300001B08028080027E000F050100060008914A00010880012800 H225Lib::h225CallProcRequest: Q.931 CALL PROCEEDING sent from socket [2]. Call state remains unchanged (Q.931 FSM simplified for H.225.0) H225Lib::h225TConn: connect in progress on socket [4] H225Lib::h225TConn: Q.931 Call State is initialized to be [Null]. Hex representation of the SETUP TPKT to send. 030000A50802008005040388C0A56C0591373737377E008D0500B8060008914A00010140060 07000740065006C0032003100332800B50000124001280001400F007000740065006C0032003 30040007A006F006E00650032002E0063006F006D005A00000D06B8003DC8490FB4B9D111BFA F0060B000E945000E07006600000106B822400F007000740065006C003200330040007A006F0 06E00650032002E0063006F006D H225Lib::h225SetupRequest: Q.931 SETUP sent from socket [4] H225Lib::h225SetupRequest: Q.931 Call State changed to [Call Initiated]. RASLib::RASRecvData: successfully rcvd message of length 123 from 90.0.0.13:1700 RASLib::RASRecvData: ARQ rcvd from [90.0.0.13:1700] on sock [0x68FC74] RASlib::ras_sendto: msg length 16 sent to 90.0.0.13 RASLib::RASSendACF: ACF sent to 90.0.0.13 Hex representation of the received TPKT 0300001808028080027E000C050100060008914A00010200 H225Lib::h225RecvData: Q.931 CALL PROCEEDING received from socket [4] Hex representation of the received TPKT 0300001808028080017E000C050300060008914A00010200 H225Lib::h225RecvData: Q.931 ALERTING received from socket [4] H225Lib::h225RecvData: Q.931 Call State changed to [Call Delivered]. Hex representation of the ALERTING TPKT to send. 0300001808028080017E000C050300060008914A00010000 H225Lib::h225AlertRequest: Q.931 ALERTING sent from socket [2]. Call state changed to [Call Received]. Hex representation of the received TPKT 0300003508028080070404889886A57E0023050240060008914A0001005A00000D06A402003 DC8490FB4B9D111BFAF0060B000E945 H225Lib::h225RecvData: Q.931 CONNECT received from socket [4] H225Lib::h225RecvData: Q.931 Call State changed to [Active]. Hex representation of the CONNECT TPKT to send. 030000370802808007040388C0A57E0026050240060008914A000100660000012AFC0880012 8003DC8490FB4B9D111BFAF0060B000E945 H225Lib::h225SetupResponse: Q.931 CONNECT sent from socket [2] H225Lib::h225SetupResponse: Q.931 Call State changed to [Active]. RASlib::ras_sendto: msg length 108 sent to 102.0.0.1 RASLib::RASSendIRR: IRR sent to 102.0.0.1 RASLib::RASRecvData: successfully rcvd message of length 108 from 102.0.0.1:24999


DB-834

May 2008


RASLib::RASRecvData: IRR rcvd from [102.0.0.1:24999] on sock [0x68FC74] RASLib::RASRecvData: successfully rcvd message of length 101 from 90.0.0.13:1700 RASLib::RASRecvData: IRR rcvd from [90.0.0.13:1700] on sock [0x68FC74] Hex representation of the received TPKT 0300001A080280805A080280107E000A050500060008914A0001 H225Lib::h225RecvData: Q.931 RELEASE COMPLETE received from socket [2] H225Lib::h225RecvData: Q.931 Call State changed to [Null]. RASlib::ras_sendto: msg length 55 sent to 102.0.0.1 RASLib::RASSendDRQ: DRQ sent to 102.0.0.1 H225Lib::h225RecvData: no connection on socket [2] RASLib::RASRecvData: successfully rcvd message of length 55 from 102.0.0.1:24999 RASLib::RASRecvData: DRQ rcvd from [102.0.0.1:24999] on sock [0x68FC74] RASlib::ras_sendto: msg length 3 sent to 70.0.0.31 RASLib::RASSendDCF: DCF sent to 70.0.0.31 Hex representation of the RELEASE COMPLETE TPKT to send. 0300001A080280805A080280107E000A050500060008914A0001 H225Lib::h225TerminateRequest: Q.931 RELEASE COMPLETE sent from socket [2]. Call state changed to [Null]. H225Lib::h225TClose: TCP connection from socket [2] closed RASlib::ras_sendto: msg length 55 sent to 102.0.0.1 RASLib::RASSendDRQ: DRQ sent to 102.0.0.1 RASLib::RASRecvData: successfully rcvd message of length 3 from 102.0.0.1:1719 RASLib::RASRecvData: DCF rcvd from [102.0.0.1:1719] on sock [0x67E6A4] RASLib::RASRecvData: successfully rcvd message of length 55 from 102.0.0.1:24999 RASLib::RASRecvData: DRQ rcvd from [102.0.0.1:24999] on sock [0x68FC74] RASlib::ras_sendto: msg length 3 sent to 70.0.0.31 RASLib::RASSendDCF: DCF sent to 70.0.0.31 RASLib::RASRecvData: successfully rcvd message of length 3 from 102.0.0.1:1719 RASLib::RASRecvData: DCF rcvd from [102.0.0.1:1719] on sock [0x67E6A4] Hex representation of the RELEASE COMPLETE TPKT to send. 0300001A080280805A080280107E000A050500060008914A0001 H225Lib::h225TerminateRequest: Q.931 RELEASE COMPLETE sent from socket [4]. Call state changed to [Null]. H225Lib::h225TClose: TCP connection from socket [4] closed RASLib::RASRecvData: successfully rcvd message of length 55 from 90.0.0.13:1700 RASLib::RASRecvData: DRQ rcvd from [90.0.0.13:1700] on sock [0x68FC74] RASlib::ras_sendto: msg length 3 sent to 90.0.0.13 RASLib::RASSendDCF: DCF sent to 90.0.0.13


DB-835

Debug Commands debug h225 events

debug h225 events To display Q.931 events, use the debug h225 events privileged EXEC command. The no form of this command disables debugging output. debug h225 events no debug h255 events

Syntax Description


Command History

Release

Modification

11.3(2)NA


12.0(3)T


12.2SX


Examples

The following are sample output from the debug h225 events command. Example 1

The following output shows two proxy call scenarios. A trace is collected on the source proxy with H.225 turned on. The call is being established. Router# debug h225 events H.225 Event Messages debugging is on Router# H225Lib::h225TAccept: TCP connection accepted from 50.0.0.12:1701 on socket [2] H225Lib::h225TAccept: Q.931 Call State is initialized to be [Null]. Hex representation of the received TPKT 0300007408020001050404889886A56C0580373737377E005B0500B0060008914A000101400 6007000740065006C003200310033020001400F007000740065006C003200330040007A006F0 06E00650032002E0063006F006D004EC8490FB4B9D111BFAF0060B000E945000C07003200000 C06B8 H225Lib::h225RecvData: Q.931 SETUP received from socket [2] H225Lib::h225RecvData: State changed to [Call Present]. Hex representation of the CALL PROCEEDING TPKT to send. 0300001B08028001027E000F050100060008914A00010880012800 H225Lib::h225CallProcRequest: Q.931 CALL PROCEEDING sent from socket [2]. Call state remains unchanged (Q.931 FSM simplified for H.225.0) H225Lib::h225TConn: connect in progress on socket [4] H225Lib::h225TConn: Q.931 Call State is initialized to be [Null]. Hex representation of the SETUP TPKT to send. 030000A60802008405040488988CA56C0591373737377E008D0500B8060008914A000101400 6007000740065006C0032003100332800B50000124001280001400F007000740065006C00320 0330040007A006F006E00650032002E0063006F006D006600000106B8004EC8490FB4B9D111B FAF0060B000E945000E07006500000106B822400F007000740065006C003200330040007A006 F006E00650032002E0063006F006D H225Lib::h225SetupRequest: Q.931 SETUP sent from socket [4] H225Lib::h225SetupRequest: Q.931 Call State changed to [Call Initiated]. Hex representation of the received TPKT 0300001B08028084027E000F050100060008914A00010880012800


DB-836

May 2008


H225Lib::h225RecvData: Q.931 CALL PROCEEDING received from socket [4] Hex representation of the received TPKT 0300001808028084017E000C050300060008914A00010000 H225Lib::h225RecvData: Q.931 ALERTING received from socket [4] H225Lib::h225RecvData: Q.931 Call State changed to [Call Delivered]. Hex representation of the ALERTING TPKT to send. 0300001808028001017E000C050300060008914A00010000 H225Lib::h225AlertRequest: Q.931 ALERTING sent from socket [2]. Call state changed to [Call Received]. Hex representation of the received TPKT 030000370802808407040388C0A57E0026050240060008914A000100660000012AFF0880012 8004EC8490FB4B9D111BFAF0060B000E945 H225Lib::h225RecvData: Q.931 CONNECT received from socket [4] H225Lib::h225RecvData: Q.931 Call State changed to [Active]. Hex representation of the CONNECT TPKT to send. 0300003808028001070404889886A57E0026050240060008914A000100650000012AFC08800 128004EC8490FB4B9D111BFAF0060B000E945 H225Lib::h225SetupResponse: Q.931 CONNECT sent from socket [2] H225Lib::h225SetupResponse: Q.931 Call State changed to [Active].

Example 2

The following output shows two proxy call scenarios. A trace is collected on the source proxy with H.225 turned on. The call is being torn down. Router# debug h225 events H.225 Event Messages debugging is on Router# Hex representation of the received TPKT 0300001A080200015A080200907E000A050500060008914A0001 H225Lib::h225RecvData: Q.931 RELEASE COMPLETE received from socket [2] H225Lib::h225RecvData: Q.931 Call State changed to [Null]. H225Lib::h225RecvData: no connection on socket [2] Hex representation of the RELEASE COMPLETE TPKT to send. 0300001A080280015A080280107E000A050500060008914A0001 H225Lib::h225TerminateRequest: Q.931 RELEASE COMPLETE sent from socket [2]. Call state changed to [Null]. H225Lib::h225TClose: TCP connection from socket [2] closed Hex representation of the RELEASE COMPLETE TPKT to send. 0300001A080280845A080280107E000A050500060008914A0001 H225Lib::h225TerminateRequest: Q.931 RELEASE COMPLETE sent from socket [4]. Call state changed to [Null]. H225Lib::h225TClose: TCP connection from socket [4] closed


DB-837

Debug Commands debug h225

debug h225 To display additional information about the actual contents of H.225 Registration, Admission, and Status Protocol (RAS) messages, use the debug h225 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug h225 {asn1 | events} no debug h225

Syntax Description

asn1

Indicates that only the Abstract Syntax Notation One (ASN.1) contents of any H.225 message sent or received will be displayed.

events

Indicates that key Q.931 events that occur when placing an H.323 call from one gateway to another will be displayed.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2


12.2(2)XB1


12.2(11)T


12.2SX


Usage Guidelines

Both versions of the debug h225 command display information about H.225 messages. H.225 messages are used to exchange RAS information between gateways and gatekeepers as well as to exchange Q.931 information between gateways. The debug h225 events command displays key Q.931 events that occur when placing an H.323 call from one gateway to another. Q.931 events are carried in H.225 messages. This command enables you to monitor Q.931 state changes such as setup, alert, connected, and released.

Note

Although the debug information includes the hexadecimal output of the entire H.225 message, only the key state changes are decoded. The debug h225 asn1 command displays the ASN.1 contents of any H.225 message sent or received that contains ASN.1 content. Not all H.225 messages contain ASN.1 content. Some messages contain both Q.931 information and ASN.1 information; if you enter this command, only ASN.1 information will be displayed.


DB-838

May 2008


Examples

The following sample output for the debug h225 events command shows a call being placed from gateway GW13 to gateway GW14. Before the call was placed, the gateway exchanged RAS messages with the gatekeeper. Because RAS messages do not contain Q.931 information, these messages do not appear in this output. Router# debug h225 events H.225 Event Messages debugging is on Router# *Mar 2 02:47:14.689: H225Lib::h225TConn:connect in progress on socket [2] *Mar 2 02:47:14.689: H225Lib::h225TConn:Q.931 Call State is initialized to be [Null]. *Mar 2 02:47:14.697:Hex representation of the SETUP TPKT to send.0300004D080200DC05040380C0A36C0991313323313333303070099131342331343330307E00260500800 60008914A000102004B1F5E5D8990006C0000000005BF7454000C0700000000000000 *Mar 2 02:47:14.701: *Mar 2 02:47:14.701: H225Lib::h225SetupRequest:Q.931 SETUP sent from socket [2] *Mar 2 02:47:14.701: H225Lib::h225SetupRequest:Q.931 Call State changed to [Call Initiated]. *Mar 2 02:47:14.729:Hex representation of the received TPKT03000021080280DC013401017E0012050340060008914A000100000109350E2B28 *Mar 2 02:47:14.729: *Mar 2 02:47:14.729: H225Lib::h225RecvData:Q.931 ALERTING received from socket [2] *Mar 2 02:47:14.729: H225Lib::h225RecvData:Q.931 Call State changed to [Call Delivered]. *Mar 2 02:47:17.565:Hex representation of the received TPKT03000034080280DC07040380C0A37E0023050240060008914A0001000109350E2B2802004B1F5E5D899000 6C0000000005BF7454 *Mar 2 02:47:17.569: *Mar 2 02:47:17.569: H225Lib::h225RecvData:Q.931 CONNECT received from socket [2] *Mar 2 02:47:17.569: H225Lib::h225RecvData:Q.931 Call State changed to [Active]. *Mar 2 02:47:23.273:Hex representation of the received TPKT0300001A080280DC5A080280107E000A050500060008914A0001 *Mar 2 02:47:23.273: *Mar 2 02:47:23.273: H225Lib::h225RecvData:Q.931 RELEASE COMPLETE received from socket [2] *Mar 2 02:47:23.273: H225Lib::h225RecvData:Q.931 Call State changed to [Null]. *Mar 2 02:47:23.293:Hex representation of the RELEASE COMPLETE TPKT to send.0300001A080200DC5A080280107E000A050500060008914A0001 *Mar 2 02:47:23.293: *Mar 2 02:47:23.293: H225Lib::h225TerminateRequest:Q.931 RELEASE COMPLETE sent from socket [2]. Call state changed to [Null]. *Mar 2 02:47:23.293: H225Lib::h225TClose:TCP connection from socket [2] closed

The following output shows the same call being placed from gateway GW13 to gateway GW14 using the debug h225 asn1 command. The output is very long, but you can track the following information: •

The admission request to the gatekeeper.

•

The admission confirmation from the gatekeeper.

•

The ASN.1 portion of the H.225/Q.931 setup message from the calling gateway to the called gateway.

•

The ASN.1 portion of the H.225/Q.931 setup response from the called gateway, indicating that the call has proceeded to alerting state.

•

The ASN.1 portion of the H.225/Q.931 message from the called gateway, indicating that the call has been connected.

•

The ASN.1 portion of the H.225/Q.931 message from the called gateway, indicating that the call has been released.


DB-839


•

The ANS.1 portion of the H.225 RAS message from the calling gateway to the gatekeeper, informing it that the call has been disengaged.

•

The ASN.1 portion of the H.225 RAS message from the gatekeeper to the calling gateway, confirming the disengage request.

•

The ASN.1 portion of the H.225/Q.931 release complete message sent from the called gateway to the calling gateway.

Router# debug h225 asn1 H.225 ASN1 Messages debugging is on Router# value RasMessage ::= admissionRequest : *Mar 2 02:48:18.445: { *Mar 2 02:48:18.445: requestSeqNum 03320, *Mar 2 02:48:18.445: callType pointToPoint :NULL, *Mar 2 02:48:18.445: callModel direct :NULL, *Mar 2 02:48:18.445: endpointIdentifier "60D6BA4C00000001", *Mar 2 02:48:18.445: destinationInfo *Mar 2 02:48:18.445: { *Mar 2 02:48:18.445: e164 :"14#14300" *Mar 2 02:48:18.445: }, *Mar 2 02:48:18.449: srcInfo *Mar 2 02:48:18.449: { *Mar 2 02:48:18.449: e164 :"13#13300" *Mar 2 02:48:18.449: }, *Mar 2 02:48:18.449: bandWidth 0640, *Mar 2 02:48:18.449: callReferenceValue 0224, *Mar 2 02:48:18.449: conferenceID '4B1F5E5D899000720000000005C067A4'H, *Mar 2 02:48:18.449: activeMC FALSE, *Mar 2 02:48:18.449: answerCall FALSE *Mar 2 02:48:18.449: } *Mar 2 02:48:18.449:25800CF7 00F00036 00300044 00360042 00410034 00430030 00300030 00300030 00300030 00310103 80470476 33010380 46046633 40028000 E04B1F5E 5D899000 72000000 0005C067 A400 29000CF7 40028000 0109350E 06B80077 value RasMessage ::= admissionConfirm : *Mar 2 02:48:18.469: { *Mar 2 02:48:18.469: requestSeqNum 03320, *Mar 2 02:48:18.469: bandWidth 0640, *Mar 2 02:48:18.469: callModel direct :NULL, *Mar 2 02:48:18.469: destCallSignalAddress ipAddress : *Mar 2 02:48:18.469: { *Mar 2 02:48:18.469: ip '0109350E'H, *Mar 2 02:48:18.469: port 01720 *Mar 2 02:48:18.469: }, *Mar 2 02:48:18.469: irrFrequency 0120 *Mar 2 02:48:18.473: } *Mar 2 02:48:18.473:value H323-UserInformation ::= *Mar 2 02:48:18.481:{ *Mar 2 02:48:18.481: h323-uu-pdu *Mar 2 02:48:18.481: { *Mar 2 02:48:18.481: h323-message-body setup : *Mar 2 02:48:18.481: { *Mar 2 02:48:18.481: protocolIdentifier { 0 0 8 2250 0 1 }, *Mar 2 02:48:18.481: sourceInfo *Mar 2 02:48:18.481: { *Mar 2 02:48:18.481: terminal *Mar 2 02:48:18.481: { *Mar 2 02:48:18.481: },


DB-840

May 2008


*Mar 2 02:48:18.481: mc FALSE, *Mar 2 02:48:18.481: undefinedNode FALSE *Mar 2 02:48:18.481: }, *Mar 2 02:48:18.481: activeMC FALSE, *Mar 2 02:48:18.481: conferenceID '4B1F5E5D899000720000000005C067A4'H, *Mar 2 02:48:18.481: conferenceGoal create :NULL, *Mar 2 02:48:18.485: callType pointToPoint :NULL, *Mar 2 02:48:18.485: sourceCallSignalAddress ipAddress : *Mar 2 02:48:18.485: { *Mar 2 02:48:18.485: ip '00000000'H, *Mar 2 02:48:18.485: port 00 *Mar 2 02:48:18.485: } *Mar 2 02:48:18.485: } *Mar 2 02:48:18.485: } *Mar 2 02:48:18.485:} *Mar 2 02:48:18.485:00800600 08914A00 0102004B 1F5E5D89 90007200 00000005 C067A400 0C070000 00000000 00 value H323-UserInformation ::= *Mar 2 02:48:18.525:{ *Mar 2 02:48:18.525: h323-uu-pdu *Mar 2 02:48:18.525: { *Mar 2 02:48:18.525: h323-message-body alerting : *Mar 2 02:48:18.525: { *Mar 2 02:48:18.525: protocolIdentifier { 0 0 8 2250 0 1 }, *Mar 2 02:48:18.525: destinationInfo *Mar 2 02:48:18.525: { *Mar 2 02:48:18.525: mc FALSE, *Mar 2 02:48:18.525: undefinedNode FALSE *Mar 2 02:48:18.525: }, *Mar 2 02:48:18.525: h245Address ipAddress : *Mar 2 02:48:18.525: { *Mar 2 02:48:18.525: ip '0109350E'H, *Mar 2 02:48:18.525: port 011050 *Mar 2 02:48:18.525: } *Mar 2 02:48:18.525: } *Mar 2 02:48:18.525: } *Mar 2 02:48:18.525:} *Mar 2 02:48:18.525:value H323-UserInformation ::= *Mar 2 02:48:22.753:{ *Mar 2 02:48:22.753: h323-uu-pdu *Mar 2 02:48:22.753: { *Mar 2 02:48:22.753: h323-message-body connect : *Mar 2 02:48:22.753: { *Mar 2 02:48:22.753: protocolIdentifier { 0 0 8 2250 0 1 }, *Mar 2 02:48:22.753: h245Address ipAddress : *Mar 2 02:48:22.753: { *Mar 2 02:48:22.753: ip '0109350E'H, *Mar 2 02:48:22.753: port 011050 *Mar 2 02:48:22.753: }, *Mar 2 02:48:22.753: destinationInfo *Mar 2 02:48:22.753: { *Mar 2 02:48:22.753: terminal *Mar 2 02:48:22.753: { *Mar 2 02:48:22.753: }, *Mar 2 02:48:22.757: mc FALSE, *Mar 2 02:48:22.757: undefinedNode FALSE *Mar 2 02:48:22.757: }, *Mar 2 02:48:22.757: conferenceID '4B1F5E5D899000720000000005C067A4'H *Mar 2 02:48:22.757: } *Mar 2 02:48:22.757: } *Mar 2 02:48:22.757:} *Mar 2 02:48:22.757:value H323-UserInformation ::= *Mar 2 02:48:27.109:{


DB-841


*Mar 2 02:48:27.109: h323-uu-pdu *Mar 2 02:48:27.109: { *Mar 2 02:48:27.109: h323-message-body releaseComplete : *Mar 2 02:48:27.109: { *Mar 2 02:48:27.109: protocolIdentifier { 0 0 8 2250 0 1 } *Mar 2 02:48:27.109: } *Mar 2 02:48:27.109: } *Mar 2 02:48:27.109:} *Mar 2 02:48:27.109:value RasMessage ::= disengageRequest : *Mar 2 02:48:27.117: { *Mar 2 02:48:27.117: requestSeqNum 03321, *Mar 2 02:48:27.117: endpointIdentifier "60D6BA4C00000001", *Mar 2 02:48:27.117: conferenceID '4B1F5E5D899000720000000005C067A4'H, *Mar 2 02:48:27.121: callReferenceValue 0224, *Mar 2 02:48:27.121: disengageReason normalDrop :NULL *Mar 2 02:48:27.121: } *Mar 2 02:48:27.121:3C0CF81E 00360030 00440036 00420041 00340043 00300030 00300030 00300030 00300031 4B1F5E5D 89900072 00000000 05C067A4 00E020 400CF8 value RasMessage ::= disengageConfirm : *Mar 2 02:48:27.133: { *Mar 2 02:48:27.133: requestSeqNum 03321 *Mar 2 02:48:27.133: } *Mar 2 02:48:27.133:value H323-UserInformation ::= *Mar 2 02:48:27.133:{ *Mar 2 02:48:27.133: h323-uu-pdu *Mar 2 02:48:27.133: { *Mar 2 02:48:27.133: h323-message-body releaseComplete : *Mar 2 02:48:27.133: { *Mar 2 02:48:27.133: protocolIdentifier { 0 0 8 2250 0 1 } *Mar 2 02:48:27.133: } *Mar 2 02:48:27.133: } *Mar 2 02:48:27.133:} *Mar 2 02:48:27.133:05000600 08914A00 01


DB-842

May 2008


debug h245 asn1 To display Abstract Syntax Notation One (ASN.1) contents of H.245 messages, use the debug h245 asn1 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug h245 asn1 no debug h245 asn1

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(2)NA


12.0(3)T


12.2SX


Usage Guidelines

Caution

This command slows the system down considerably. Connections may time out.


DB-843


debug h245 events To display H.245 events, use the debug h245 events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug h245 events no debug h245 events

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(2)NA


12.0(3)T


12.2SX



DB-844

May 2008

Debug Commands debug h245 srtp

debug h245 srtp To display H.245 Secure Real-Time Transport Protocol (SRTP) messages, use the debug h245 srtp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug h245 srtp no debug h245 srtp

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(6)T1


12.2SX


Usage Guidelines

To reduce the system impact of the output that this command generates, use the debug h245 srtp command during times of minimal system traffic. To reduce system overhead and redirect logging to an internal buffer, use the logging buffered command. Use the debug h225 asn1 command to display Abstract Syntax Notation One (ASN.1) contents of H.225 messages. Use the debug h245 asn1 command to display ASN.1 contents of H.245 messages. The output from the debug h245 srtp command is primarily used by Cisco technical personnel. See the “Examples” section for an explanation of selected fields.

Examples

The following example displays SRTP messages exchanged during H.225 and H.245 signaling: Router# debug h245 srtp H.245 SRTP Messages debugging is on SY3725_1# 000072: Mar 16 16:46:38.237: //-1/xxxxxxxxxxxx/H323/cch323_post_call_setup_request: cch323_post_call_setup_request:1015: SRTP added to ev for stream:SRTP_TX_STREAM. 000073: Mar 16 16:46:38.237: //-1/xxxxxxxxxxxx/H323/cch323_dump_srtp_caps: crypto_bm=0x1, codec_bm=0xB. 000074: Mar 16 16:46:38.237: //-1/xxxxxxxxxxxx/H323/cch323_dump_srtp_media_params:

The following lines show SRTP media parameters: ssrc_sel=0x0,


DB-845


srtp_ssrc=0x0, crypto_services=0x0, crypto_suite=0x0, master_key_len=0x0, master_salt_len=0x0, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000075: Mar 16 16:46:38.237: //-1/xxxxxxxxxxxx/H323/cch323_dump_srtp_sess_params:

The following lines show SRTP session parameters: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x0, encryptedsrtp=0x0, encryptedsrtcp=0x0, fecorder=0x0, windowsizehint=0x0 000076: Mar 16 16:46:38.237: cch323_post_call_setup_request:993: callID = 0x4PeercallID = 0x3params->incomingCallid = 0x3srtp_params_caps = 0x0i=1 000077: Mar 16 16:46:38.237: //-1/xxxxxxxxxxxx/H323/cch323_post_call_setup_request: cch323_post_call_setup_request:1021: SRTP NOT added to ev 000078: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_set_srtp_call: ../voip/cch323/gw/os/src/h323_gw_dialpeer.c:cch323_set_srtp_call:3420: SRTP configuration:

The following lines show SRTP configuration. Fields having a value set to 1 show that SRTP is enabled. peer->voice_peer_tag = 101, ccb->srtp_call = 1, ccb->srtp_fallback = 1, ccb->srtp_transparent = 1 000079: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_get_caps_chn_info: Local[TX] SRTP Info:../voip/cch323/gw/src/cch323_h245_iwf_util.c:cch323_get_caps_chn_info:148 000080: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_dump_srtp_caps:

The following lines show SRTP capabilities: crypto_bm=0x1, codec_bm=0xB. 000081: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x0, crypto_suite=0x0, master_key_len=0x0, master_salt_len=0x0, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000082: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_dump_srtp_sess_params: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x0, encryptedsrtp=0x0, encryptedsrtcp=0x0, fecorder=0x0, windowsizehint=0x0 000083: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_get_caps_chn_info: Remote[RX] SRTP Info:../voip/cch323/gw/src/cch323_h245_iwf_util.c:cch323_get_caps_chn_info:151 000084: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_dump_srtp_caps:


DB-846

May 2008


The following line shows SRTP capability for the DSP, indicated by the crypto_bm field. A value of 0x0 indicates the DSP is not SRTP capable. crypto_bm=0x0, codec_bm=0x0. 000085: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x0, crypto_suite=0x0, master_key_len=0x0, master_salt_len=0x0, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000086: Mar 16 16:46:38.241: //4/CCB23DEA8003/H323/cch323_dump_srtp_sess_params: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x0, encryptedsrtp=0x0, encryptedsrtcp=0x0, fecorder=0x0, windowsizehint=0x0 000087: Mar 16 16:46:38.245: //4/CCB23DEA8003/H323/cch323_build_local_encoded_fastStartOLCs: ../voip/cch323/gw/src/cch323_h245_util.c:cch323_build_local_encoded_fastStartOLCs:1518: OGW: generating Keys. 000088: Mar 16 16:46:38.245: //4/CCB23DEA8003/H323/cch323_generate_srtp_info: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_generate_srtp_info:31: Entry 000089: Mar 16 16:46:38.245: //4/CCB23DEA8003/H323/cch323_generate_srtp_info: Generated SRTP info:../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_generate_srtp_info:83 000090: Mar 16 16:46:38.245: //4/CCB23DEA8003/H323/cch323_dump_srtp_caps: crypto_bm=0x1, codec_bm=0xB. 000091: Mar 16 16:46:38.245: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000092: Mar 16 16:46:38.245: //4/CCB23DEA8003/H323/cch323_dump_srtp_sess_params: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x18, encryptedsrtp=0x1, encryptedsrtcp=0x1, fecorder=0x0, windowsizehint=0x40 000093: Mar 16 16:46:38.245: //4/CCB23DEA8003/H323/cch323_generate_srtp_info: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_generate_srtp_info:86: Exit 000094: Mar 16 16:46:38.249: //4/CCB23DEA8003/H323/cch323_generate_srtp_info: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_generate_srtp_info:31: Entry 000095: Mar 16 16:46:38.249: //4/CCB23DEA8003/H323/cch323_generate_srtp_info: Generated SRTP info:../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_generate_srtp_info:83 000096: Mar 16 16:46:38.249: //4/CCB23DEA8003/H323/cch323_dump_srtp_caps: crypto_bm=0x0, codec_bm=0x0. 000097: Mar 16 16:46:38.249: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0,


DB-847


crypto_services=0x3, crypto_suite=0x0, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000098: Mar 16 16:46:38.249: //4/CCB23DEA8003/H323/cch323_dump_srtp_sess_params: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x18, encryptedsrtp=0x1, encryptedsrtcp=0x1, fecorder=0x0, windowsizehint=0x40 000099: Mar 16 16:46:38.249: //4/CCB23DEA8003/H323/cch323_generate_srtp_info: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_generate_srtp_info:86: Exit 000100: Mar 16 16:46:38.249: //4/CCB23DEA8003/H323/build_fastStart_OLCs: FWD OLC SRTP params:../voip/cch323/gw/src/cch323_h245_util.c:build_fastStart_OLCs:1403 000101: Mar 16 16:46:38.249: //4/CCB23DEA8003/H323/build_fastStart_OLCs: RVR OLC SRTP Params:../voip/cch323/gw/src/cch323_h245_util.c:build_fastStart_OLCs:1417 000102: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_build_olc_for_ccapi: ../voip/cch323/gw/src/cch323_h245_util.c:cch323_build_olc_for_ccapi:1690: WE ARE OGW.

The following lines show the outgoing gateway sending SRTP capabilities: 000103: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_build_olc_for_ccapi: Local SRTP Info:../voip/cch323/gw/src/cch323_h245_util.c:cch323_build_olc_for_ccapi:1779 000104: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_dump_srtp_caps: crypto_bm=0x1, codec_bm=0xB. 000105: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000106: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_dump_srtp_sess_params: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x18, encryptedsrtp=0x1, encryptedsrtcp=0x1, fecorder=0x0, windowsizehint=0x40

The following lines show that the gateway has received SRTP capabilities from the remote end: 000107: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_build_olc_for_ccapi: Remote SRTP Info:../voip/cch323/gw/src/cch323_h245_util.c:cch323_build_olc_for_ccapi:1783 000108: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_dump_srtp_caps: crypto_bm=0x1, codec_bm=0x1.


DB-848

May 2008


000109: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000110: Mar 16 16:46:38.301: //4/CCB23DEA8003/H323/cch323_dump_srtp_sess_params: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x18, encryptedsrtp=0x1, encryptedsrtcp=0x1, fecorder=0x0, windowsizehint=0x40 000111: Mar 16 16:46:38.305: //4/CCB23DEA8003/H323/h323_common_setup_rtcp_parameters: ../voip/cch323/gw/os/src/h323_gw_rtpapi.c:h323_common_setup_rtcp_parameters:378:olc->rtcp_ session.srtp_services:3 000112: Mar 16 16:46:38.305: vtsp_call_ssrc_update: updated ssrc=0x5227F02 000113: Mar 16 16:46:38.305: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:369: Entry 000114: Mar 16 16:46:38.305: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:416: TX [Local] SRTP Info . 000115: Mar 16 16:46:38.305: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000116: Mar 16 16:46:38.305: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:448: RX [Remote] SRTP Info . 000117: Mar 16 16:46:38.305: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000118: Mar 16 16:46:38.305: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: % SRTP Library session creation, id:0x80000002, context:0x653E0CF8, num_context=2, rtp:0x653D2CF4, rtp_session:0x66D79B00 000119: Mar 16 16:46:38.305: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:514: Exit


DB-849


000120: Mar 16 16:46:38.313: //4/CCB23DEA8003/H323/h323_common_setup_rtcp_parameters: ../voip/cch323/gw/os/src/h323_gw_rtpapi.c:h323_common_setup_rtcp_parameters:378:olc->rtcp_ session.srtp_services:3 000121: Mar 16 16:46:38.313: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:369: Entry 000122: Mar 16 16:46:38.313: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:416: TX [Local] SRTP Info . 000123: Mar 16 16:46:38.313: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000124: Mar 16 16:46:38.313: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:448: RX [Remote] SRTP Info . 000125: Mar 16 16:46:38.313: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000126: Mar 16 16:46:38.313: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: % SRTP Library session update with 2 keysid:0x80000002 context:0x653E0CF8 000127: Mar 16 16:46:38.313: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:514: Exit 000128: Mar 16 16:46:38.317: //4/CCB23DEA8003/H323/h323_common_setup_rtcp_parameters: ../voip/cch323/gw/os/src/h323_gw_rtpapi.c:h323_common_setup_rtcp_parameters:378:olc->rtcp_ session.srtp_services:3 000129: Mar 16 16:46:38.317: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:369: Entry 000130: Mar 16 16:46:38.317: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:416: TX [Local] SRTP Info . 000131: Mar 16 16:46:38.317: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000132: Mar 16 16:46:38.317: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:448: RX [Remote] SRTP Info .


DB-850

May 2008


000133: Mar 16 16:46:38.317: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000134: Mar 16 16:46:38.317: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: % SRTP Library session update with 2 keysid:0x80000002 context:0x653E0CF8 000135: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_setup_srtp_session: ../voip/cch323/gw/os/src/h323_gw_srtpapi.c:cch323_setup_srtp_session:514: Exit 000136: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_h245_cap_ind: Updated CCB(0x66D8D2D4) with TCS Remote SRTP Info: 000137: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_dump_srtp_caps: crypto_bm=0x1, codec_bm=0xB. 000138: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000139: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_dump_srtp_sess_params: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x18, encryptedsrtp=0x1, encryptedsrtcp=0x1, fecorder=0x0, windowsizehint=0x40 000140: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_update_tcs_nonstd_info: cch323_update_tcs_nonstd_info:5800: Posting TCS SRTP caps to other callleg. 000141: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_dump_srtp_caps: crypto_bm=0x1, codec_bm=0xB. 000142: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_dump_srtp_media_params: ssrc_sel=0x0, srtp_ssrc=0x0, crypto_services=0x3, crypto_suite=0x1, master_key_len=0x10, master_salt_len=0xE, master_key=0xxxxxxxxxxxxxxxxx, master_salt=0xxxxxxxxxxxxxxx 000143: Mar 16 16:46:38.321: //4/CCB23DEA8003/H323/cch323_dump_srtp_sess_params: lifetime=0x0, mki=0x, mki_length=0x0, kdr=0x18, encryptedsrtp=0x1, encryptedsrtcp=0x1,


DB-851


fecorder=0x0, windowsizehint=0x40 000144: Mar 16 16:46:38.325: //4/CCB23DEA8003/H323/cch323_h245_cap_ind: cch323_h245_cap_ind:360 cch323_update_tcs_nonstd_info failed

Related Commands

Command

Description

debug h225 asn1

Displays ASN.1 contents of H.225 messages.

debug h245 asn1

Displays ASN.1 contents of H.245 messages.

logging buffered

Enables system message logging to a local buffer.

srtp (voice)

Enables secure calls globally.

srtp (dial-peer)

Enables secure calls for a specific dial peer.


DB-852

May 2008

Debug Commands debug h323-annexg

debug h323-annexg To display all pertinent Annex G messages that have been transmitted and received, use the debug h323-annexg command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug h323-annexg {asn1 | errors | events | inout} no debug h323-annexg

Syntax Description.

asn1

Displays the Annex G ASN.1 messages.

errors

Displays the Annex G error messages encountered during processing.

events

Displays the Annex G events received from the state machine.

inout

(Optional) This functionality is not yet implemented.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XA


12.2(4)T


12.2(2)XB1


12.2(11)T


12.2SX


Examples

The following is sample output from the debug h323-annexg events command: Router# debug h323-annexg events Aug 16 14:03:40.983:be_process:BE QUEUE_EVENT (minor 73) wakeup Aug 16 14:03:40.983:be_sm:Received event BE_EV_DO_QUERY Aug 16 14:03:40.983: nxg_recv_msg:Rcvd dscrptrIDCnfrmtn from 172.18.195.46:2099 [320] Aug 16 14:03:41.531: nxg_recv_msg:Rcvd descriptorConfirmation from 172.18.195.46:2099 [321] Aug 16 14:03:41.539:handle_descriptor_cfm:Descriptor from neighbor 172.18.195.46 unchanged, TTL is 60 Seconds


DB-853

Debug Commands debug h323-annexg

Related Commands

Command

Description

emulate

Displays all pertinent Annex E messages that have been transmitted and received.


DB-854

May 2008

Debug Commands debug hccp timing

debug hccp timing To display debug messages for the timing of HCCP events, use the debug hccp timing command in privileged EXEC mode. To disable the debug message output, use the no form of this command. debug hccp timing [if-config] no debug hccp timing [if-config]

Syntax Description

if-config

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3a)EC


12.2(4)XF1, 12.2(4)BC1

Support was added for the N+1 (1:n) RF Switch with the Cisco uBR10012 router.

12.2(11)BC1

Support was added for the N+1 (1:n) RF Switch with the Cisco uBR7246VXR router.

12.2(15)BC1

The if-config option was added.

12.2SX


(Optional) Displays debugging messages showing the timing of the reconfiguration of cable interfaces during HCCP redundancy operations.

Usage Guidelines

You must activate the debug hccp events command before the debug hccp timing command will generate any debug message output.

Examples

The following example shows typical output for the debug hccp timing command: Router# debug hccp events Router# debug hccp timing HCCP timing measurement debugging is on May May May May May May May May May May May May

31 31 31 31 31 31 31 31 31 31 31 31

10:21:07.609 10:21:07.609 10:21:08.705 10:21:08.705 10:21:08.773 10:21:08.793 10:21:10.730 10:21:10.730 10:21:10.734 10:21:10.774 10:21:10.774 10:21:10.774

HCCP HCCP HCCP HCCP HCCP HCCP HCCP HCCP HCCP HCCP HCCP HCCP

P is busy. Deactivating 1 6 P is busy. Deactivating 2 6 hwif_goingdown for Cable8/1/0. Deactivate 1 6 hwif_goingdown for Cable8/1/1. Deactivate 2 6 2 6 Working: become standby - 68 msec 1 6 Working: become standby - 20 msec 1 1 Working: turn on "uc" - 8 msec 1 1 Working: turn on "nru" - 0 msec 1 1 Working: become active - 4 msec 2 1 Working: turn on "uc" - 52 msec 2 1 Working: turn on "nru" - 0 msec 2 1 Working: become active - 0 msec


DB-855


May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May May

31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31

10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:12.350 10:21:13.726 10:21:13.790 10:21:14.422 10:21:14.422 10:21:14.438 10:21:14.702 10:21:14.702 10:21:16.078 10:21:16.078 10:21:16.078 10:21:16.599 10:21:16.599 10:21:17.014 10:21:17.014 10:21:17.593 10:21:17.593 10:21:18.112 10:21:18.112 10:21:18.331 10:21:18.331 10:21:18.331 10:21:18.331 10:21:18.331 10:21:19.691 10:21:20.112 10:21:20.112 10:21:20.112 10:21:20.112 10:21:20.112

HCCP hwif_goingdown for Cable5/1/0. Deactivate 1 1 HCCP hwif_goingdown for Cable5/1/0. Deactivate 1 6 HCCP hwif_goingdown for Cable5/1/0. Deactivate 1 3 HCCP hwif_goingdown for Cable5/1/0. Deactivate 1 2 HCCP hwif_goingdown for Cable5/1/0. Deactivate 1 5 HCCP hwif_goingdown for Cable5/1/0. Deactivate 1 4 HCCP hwif_goingdown for Cable5/1/1. Deactivate 2 1 HCCP hwif_goingdown for Cable5/1/1. Deactivate 2 3 HCCP hwif_goingdown for Cable5/1/1. Deactivate 2 6 HCCP hwif_goingdown for Cable5/1/1. Deactivate 2 2 HCCP hwif_goingdown for Cable5/1/1. Deactivate 2 4 HCCP hwif_goingdown for Cable5/1/1. Deactivate 2 5 HCCP 1 1 Protect: turn off "uc" - 1972 msec HCCP 2 1 Protect: turn off "uc" - 2036 msec HCCP 1 1 Protect: turn off "nru" - 696 msec HCCP 1 1 Protect: unload config (if) - 0 msec HCCP 1 1 Protect: unload config (subif) - 16 msec HCCP 1 1 Protect: unload config (ds) - 264 msec HCCP 1 1 Protect: become standby - 0 msec HCCP 2 1 Protect: turn off "nru" - 2288 msec HCCP 2 1 Protect: unload config (if) - 0 msec HCCP 2 1 Protect: unload config (subif) - 0 msec HCCP 2 1 Protect: unload config (ds) - 520 msec HCCP 2 1 Protect: become standby - 0 msec HCCP: P missed hello ack in LEARN state and is locked. Deactivate 4 1 HCCP 4 1 Protect: turn off "rfswitch" - 52 msec HCCP 3 1 Working: turn on "rfswitch" - 0 msec HCCP 3 1 Working: become active - 0 msec HCCP 1 1 Protect: load config (if) - 0 msec HCCP 1 1 Protect: load config (subif) - 4 msec HCCP 1 1 Protect: load config (ds) - 100 msec HCCP 2 1 Working: turn off "rfswitch" - 0 msec HCCP 2 Cable5/0/1 Protect: resolve conflict Learn->Teach HCCP 2 1 Protect: load config (if) - 0 msec HCCP 2 1 Protect: load config (subif) - 0 msec HCCP 2 1 Protect: load config (ds) - 76 msec HCCP 2 1 Protect: turn on "rfswitch" - 48 msec HCCP 2 1 Protect: become active - 0 msec HCCP 2 1 Protect: load config (ds) - 76 msec HCCP 2 1 Protect: turn on "rfswitch" - 48 msec HCCP 2 1 Protect: become active - 0 msec

The following example shows typical output for the debug hccp timing if-config command: Router# debug hccp events Router# debug hccp timing if-config HCCP Timing measurements messages of (UN)LOAD IF config CLI is on HCCP 1 1 Working: unload config (ds) - 112 msec HCCP 1 1 Protect: load config (ds) - 123 msec HCCP 1 1 Protect: load config (chnl set freq) - 35 msec

Related Commands

Command

Description

debug hccp authentication

Displays authentication debug messages for HCCP groups.

debug hccp channel-switch

Displays debug messages related to an RF or channel switch that is being used for HCCP N+1 (1:n) redundancy.

debug hccp events

Displays debug messages for all HCCP group interaction.


DB-856

May 2008


Command

Description

debug hccp inter-db

Displays debug messages for the inter-database events during HCCP operations.

debug hccp plane

Displays debug messages for HCCP-related messages sent between the router’s control plane and data backplane.

debug hccp sync

Displays debug messages for HCCP synchronization messages.


DB-857

Debug Commands debug hpi

debug hpi Note

Effective with release 12.3(8)T, the debug hpi command is replaced by the debug voip hpi command. See the debug voip hpi command for more information. To enable debugging for Host Port Interface (HPI) message events, use the debug hpi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug hpi {all | buffer size | capture | command | destination url | detail | error | notification | response | stats} no debug hpi {all | buffer size | capture | command | destination url | detail | error | notification | response | stats}

Syntax Description

all

Enables all HPI debug options (command, detail, error, notification, and response).

buffer size

Sets the maximum amount of memory (in bytes) that the capture system allocates for its buffers when it is active. Valid size range is from 0 to 9000000. Default is 0.

capture

Displays HPI capture.

command

Displays commands that are being sent to the 54x DSP.

destination url

Turns capture on if it was off and sends the output to the specified URL. If capture was previously enabled for a different URL, the existing URL is closed, the new URL is opened, and output is sent to the new URL.

detail

Displays additional detail for the HPI debugs that are enabled.

error

Displays any HPI errors.

notification

Displays notification messages sent that are from the 54x DSP (for example, tone detection notification).

response

Displays responses (to commands) that are sent by the 54x DSP (for example, responses to statistic requests).

stats

Displays HPI statistics.

Defaults

This command is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)XM

This command was introduced on the Cisco AS5300 and Cisco AS5800.

12.2(2)T

This command was implemented on the Cisco 1700, Cisco 2600 series, Cisco 3600 series, and the Cisco MC3810. The stats keyword was added.


DB-858

May 2008

Debug Commands debug hpi

Usage Guidelines

Release

Modification

12.2(10), 12.2(11)T

This command was implemented on the Cisco 827, Cisco 2400, Cisco 7200 series, and Cisco CVA 120. The following keywords were added: buffer, capture, and destination.

12.3(8)T

This command was replaced by the debug voip hpi command.

12.2SX


This command enables debugging for HPI message events, which are used to communicate with digital signal processors (DSPs). When used with the Voice DSP Contol Message Logger feature, the debug hpi buffer command sets the maximum amount of memory (in bytes) that the capture system can allocate for its buffers when it is active. The debug hpi capture destination url command turns capture on if it was off and sends the output to the given URL. If capture was previously enabled for a different URL, the existing URL is closed, the new URL is opened, and output is sent to the new URL. When you use the no debug hpi capture command, the capture option is turned off if it was on, any open files are closed, and any allocated memory is released. Use the debug hpi all command to view gateway DSP modem relay termination codes. The DSP-to-host messages for the modem relay termination indicate to the host the modem relay session termination time, physical or link layer, and other probable causes for disconnection. On receiving this indication from the DSP, the host can disconnect the call or place the channel in the modem passthrough state. When this command is used on a Cisco AS5300 during a calling session, the Cisco AS5300 displays the following information (of severity 6 whereas ordinary debug information is severity 7) on the screen by default: 2w6d:%ISDN-6-DISCONNECT:Interface Serial0:18 disconnected from 22022 , call lasted 12 seconds 2w6d:%ISDN-6-DISCONNECT:Interface Serial1:9 disconnected from 32010 , call lasted 14 seconds 2w6d:%ISDN-6-CONNECT:Interface Serial3:2 is now connected to 52003 2w6d:%ISDN-6-CONNECT:Interface Serial2:11 is now connected to 42002

To disable this default information on the Cisco AS5300 and to block the display of the debug hpi capture and show voice hpi capture commands, set the login console to a severity lower than 6.

Examples

The following example turns on the debug output from capture routines: Router# debug hpi capture HPI Capture/Logger debugging is on

Related Commands

Command

Description

show voice hpi capture

Verifies capture status and statistics.


DB-859

Debug Commands debug http client cookie

debug http client cookie To display debugging traces for cookie-related processes, including sending, receiving, validating, storing, and expiring a cookie, use the debug http client cookie command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug http client cookie no debug http client cookie

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Examples

The following sample output from the debug http client cookie command shows that a cookie is being received and stored: Router# debug http client cookie *May 6 23:23:41.995: //38//HTTPC:/httpc_decode_msgheader: received cookie:TestCookieX=username; path=/; domain=.cisco.com URL:http://rtsp-ws.cisco.com/cookie.php *May 6 23:23:41.995: //38//HTTPC:/httpc_decode_msgheader: received cookie:TestCookieY=password; expires=Thu, 06-May-04 22:30:47 GMT; path=/; domain=.cisco.com URL:http://rtsp-ws.cisco.com/cookie.php *May 6 23:23:41.995: //38//HTTPC:/httpc_cookie_store: validating cookie:TestCookieX=username; path=/; domain=.cisco.com *May 6 23:23:41.995: //38//HTTPC:/httpc_cookie_store: store cookie:TestCookieX=username path=/ domain=.cisco.com *May 6 23:23:41.995: //38//HTTPC:/httpc_cookie_store: rtsp-7#validating cookie:TestCookieY=password; expires=Thu, 06-May-04 22:30:47 GMT; path=/; domain=.cisco.com *May 6 23:23:41.995: //38//HTTPC:/httpc_cookie_store: store cookie:TestCookieY=password path=/ domain=.cisco.com *May 6 23:23:41.995: //38//HTTPC:/httpc_process_response: TestCookieY=password path=/ domain=.cisco.com TestCookieX=username path=/ domain=.cisco.com

Related Commands

Command

Description

http client cache memory

Configures the memory limits for the HTTP client cache.

http client cache refresh

Configures the refresh time for the HTTP client cache.


DB-860

May 2008

Debug Commands debug http client cookie

Command

Description

http client cookie

Enables the HTTP client to send and receive cookies.

show http client cookie

Displays cookies that are being stored by the HTTP client.


DB-861

Debug Commands debug http client

debug http client To display debugging messages for the HTTP client, use the debug http client command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug http client {all | api | background | cache | error | main | msg | socket} no debug http client {all | api | background | cache | error | main | msg | socket}

Syntax Description

all

Displays all debugging messages for the HTTP client.

api

Displays debugging information for the HTTP client application programming interface (API) process.

background

Displays background messages.

cache

Displays debugging information for the HTTP client cache module.

error

Displays the HTTP client error messages.

main

Displays debugging information for the HTTP client main process.

msg

Displays the HTTP client messages.

socket

Displays the HTTP client socket messages.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB

This command was introduced on the Cisco AS5300, Cisco AS5350, and Cisco AS5400.

12.2(11)T

This command was implemented on the Cisco 3640 and Cisco 3660, and the background keyword was added.

12.2SX


Usage Guidelines

Note

The output of this command is effected by the debug condition application voice command. If the debug condition application voice command is configured and the element is enabled in the VoiceXML document, debugging output is limited to the VoiceXML application named in the debug condition application voice command.

We recommend that you log output from the debug http client msg and debug http client socket commands to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.


DB-862

May 2008


Examples

The following is sample output from the debug http client api command: Router# debug http client api HTTP Client API Process debugging is on *Jan 3 10:58:48.609: httpc_send_ev: event sent to HTTP Client: *Jan 3 10:58:48.609: method (GET), url (http://serverX.com/vxml/test/prompts/9.au) *Jan 3 10:58:48.609: callback (61008E78), argp (63590DB4), sid (0), timeout (60), retries (2) *Jan 3 10:58:48.609: httpc_free: app freeing response data(626FA608) *Jan 3 10:58:59.353: httpc_send_ev: event sent to HTTP Client: *Jan 3 10:58:59.353: method (GET), url (http://1.7.100.1/vxml/test/dropoffRecord) *Jan 3 10:58:59.353: callback (61008E78), argp (6393B684), sid (0), timeout (60), retries (0) *Jan 3 10:58:59.369: httpc_free: app freeing response data(626F9348) *Jan 3 10:59:45.033: httpc_send_ev: event sent to HTTP Client: *Jan 3 10:59:45.033: method (POST), url (http://rtsp-ws/dropoffAppend.php?append=&disconnect=1) *Jan 3 10:59:45.033: callback (60FE9064), argp (63448820), sid (7179), timeout (0), retries (0) *Jan 3 10:59:57.369: httpc_free: app freeing response data(626F9340)

The following is sample output from the debug http client cache command: Router# debug http client cache HTTP Client Cache Module debugging is on *Jan 3 11:53:52.817: httpc_cache_rsp_return: cache(626F8E50)URL:http://serverX.com/vxml/test/root.vxml *Jan 3 11:53:52.829: httpc_cache_entry_free: cache(626F8B30)URL:http://serverX.com/vxml/test/getPhoneInfo.vxml?ani=1234567&dnis=7654321 *Jan 3 11:53:52.837: httpc_cache_entry_free: cache(626F9710)URL:http://1.7.100.1/vxml/test/engine.vxml?flow=iso *Jan 3 11:53:52.853: httpc_cache_rsp_return: cache(626F8B30)URL:http://1.7.100.1/vxml/test/root.vxml *Jan 3 11:53:52.873: httpc_cache_rsp_return: cache(626F9030)URL:http://1.7.100.1/vxml/test/getExtension.vxml *Jan 3 11:53:59.517: httpc_cache_entry_free: cache(626F9170)URL:http://1.7.100.1/vxml/test/checkExtension.vxml?extension=1234&attempt=1 *Jan 3 11:53:59.545: httpc_cache_rsp_return: cache(626F9A30)URL:http://1.7.100.1/vxml/test/dropoff.vxml *Jan 3 11:54:10.361: httpc_cache_rsp_return: cache(626F9DF0)URL:http://serverX.com/vxml/test/init.vxml *Jan 3 11:54:10.361: httpc_cache_rsp_return: cache(626FA430)URL:http://1.7.100.1/vxml/test/dropoffRecord *Jan 4 00:20:23.474: httpc_cache_store: entry(http://ServerY.com/vxml/init.vxml) size(10114 bytes) is too large to cache.

The following is sample output from the debug http client main command: Router# debug http client main HTTP Client Main Process debugging is on *Jan 3 11:56:05.885: httpc_get, url: http://serverX.com/vxml/test/root.vxml *Jan 3 11:56:05.889: httpc_msg_send, sid: 0, method: 83951618 *Jan 3 11:56:05.889: httpc_enqueue_wmsg, sid: 0, method: 83951618 *Jan 3 11:56:05.893: httpc_process_write_queue, socket writeble fd: 0, process enqueued msg, sid: 0, method: 83951618 *Jan 3 11:56:05.893: httpc_msg_write, sid: 0, method: 83951618 *Jan 3 11:56:05.901: HTTPC_MSG_COMPLETE: rsp_code(304),msg(62C9C25C)URL:http://serverX.com/vxml/test/root.vxml, fd(0)


DB-863


*Jan 3 11:56:05.901: httpc_process_redirect_rsp: msg(62C9C25C)URL:http://serverX.com/vxml/test/root.vxml, response code HTTPC_NOT_MODIFIED_304 *Jan 3 11:56:05.913: httpc_get, url: http://serverX.com/vxml/test/getPhoneInfo.vxml?ani=1234567&dnis=7654321 *Jan 3 11:56:05.917: httpc_msg_send, sid: 0, method: 65538 *Jan 3 11:56:05.917: httpc_enqueue_wmsg, sid: 0, method: 65538 *Jan 3 11:56:05.917: httpc_process_write_queue, socket writeble fd: 1, process enqueued msg, sid: 0, method: 65538 *Jan 3 11:56:05.917: httpc_msg_write, sid: 0, method: 65538 *Jan 3 11:56:05.925: HTTPC_MSG_COMPLETE: rsp_code(200),msg(62CB5824)URL:http://serverX.com/vxml/test/getPhoneInfo.vxml?ani=1234567& dnis=7654321, fd(1) *Jan 3 11:56:05.929: httpc_get, url: http://1.7.100.1/vxml/test/engine.vxml?flow=iso *Jan 3 11:56:05.929: httpc_msg_send, sid: 0, method: 65538 *Jan 3 11:56:05.929: httpc_enqueue_wmsg, sid: 0, method: 65538 *Jan 3 11:56:05.929: httpc_process_free_rsp: User returns noncache response (626F9670) *Jan 3 11:56:05.929: httpc_process_write_queue, socket writeble fd: 1, process enqueued msg, sid: 0, method: 65538 *Jan 3 11:56:05.929: httpc_msg_write, sid: 0, method: 65538 *Jan 3 11:56:05.937: HTTPC_MSG_COMPLETE: rsp_code(200),msg(62CB03AC)URL:http://1.7.100.1/vxml/test/engine.vxml?flow=iso, fd(1)

The following is sample output from the debug http client msg command: Router# debug http client msg HTTP Client: HTTP Client Messages debugging is on *Jan 1 05:07:30.534: HTTP Client write buffer fd(0): GET /vxml/abcdefg/test/init.vxml HTTP/1.1 Host: c5300-2 Content-Type: application/x-www-form-urlencoded Connection: Keep-Alive Accept: text/vxml; level = 1, text/plain, text/html, audio/basic User-Agent: Cisco-IOS-C5300/12.2(20010829:180555) VoiceXML/1.0 *Jan 1 05:07:30.538: about to send data to socket 0 : first 263 bytes of data: 62397130: 62397140: 2F76786D 6C2F6162 63646566 62397150: 73742F69 6E69742E 76786D6C 62397160: 502F312E 310D0A48 6F73743A 62397170: 30302D32 0D0A436F 6E74656E 62397180: 70653A20 6170706C 69636174 62397190: 782D7777 772D666F 726D2D75 623971A0: 636F6465 640D0A43 6F6E6E65 623971B0: 6E3A204B 6565702D 416C6976 623971C0: 63636570 743A2074 6578742F 623971D0: 3B206C65 76656C20 3D20312C 623971E0: 742F706C 61696E2C 20746578 623971F0: 6D6C2C20 61756469 6F2F6261 62397200: 0A557365 722D4167 656E743A 62397210: 636F2D49 4F532D43 35333030 62397220: 32283230 30313038 32393A31 62397230: 35292056 6F696365 584D4C2F 62397240: 0A0D0A00 *Jan 1 05:07:30.546: read data from first 400 bytes of data:

47455420 672F7465 20485454 20633533 742D5479 696F6E2F 726C656E 6374696F 650D0A41 76786D6C 20746578 742F6874 7369630D 20436973 2F31322E 38303535 312E300D

GET /vxml/abcdefg/te st/init.vxml HTT P/1.1..Host: c53 00-2..Content-Ty pe: application/ x-www-form-urlen coded..Connectio n: Keep-Alive..A ccept: text/vxml ; level = 1, tex t/plain, text/ht ml, audio/basic. .User-Agent: Cis co-IOS-C5300/12. 2(20010829:18055 5) VoiceXML/1.0. ....

socket 0 :


DB-864

May 2008


628DE8F0: 48545450 2F312E31 20323030 HTTP/1.1 200 628DE900: 204F4B0D 0A446174 653A2046 72692C20 OK..Date: Fri, 628DE910: 33312041 75672032 30303120 30373A30 31 Aug 2001 07:0 628DE920: 363A3335 20474D54 0D0A5365 72766572 6:35 GMT..Server 628DE930: 3A204170 61636865 2F312E33 2E313120 : Apache/1.3.11 628DE940: 28556E69 78292041 70616368 654A5365 (Unix) ApacheJSe 628DE950: 72762F31 2E300D0A 4C617374 2D4D6F64 rv/1.0..Last-Mod 628DE960: 69666965 643A2057 65642C20 3233204D ified: Wed, 23 M 628DE970: 61792032 30303120 31353A35 333A3233 ay 2001 15:53:23 628DE980: 20474D54 0D0A4554 61673A20 22323430 GMT..ETag: "240 628DE990: 37642D31 39322D33 62306264 63663322 7d-192-3b0bdcf3" 628DE9A0: 0D0A4163 63657074 2D52616E 6765733A ..Accept-Ranges: 628DE9B0: 20627974 65730D0A 436F6E74 656E742D bytes..Content628DE9C0: 4C656E67 74683A20 3430320D 0A4B6565 Length: 402..Kee 628DE9D0: 702D416C 6976653A 2074696D 656F7574 p-Alive: timeout 628DE9E0: 3D352C20 6D61783D 31300D0A 436F6E6E =5, max=10..Conn 628DE9F0: 65637469 6F6E3A20 4B656570 2D416C69 ection: Keep-Ali 628DEA00: 76650D0A 436F6E74 656E742D 54797065 ve..Content-Type 628DEA10: 3A207465 78742F76 786D6C0D 0A0D0A3C : text/vxml....< 628DEA20: 3F786D6C 20766572 73696F6E 3D22312E ?xml version="1. 628DEA30: 30223F3E 0A3C7678 6D6C2076 65727369 0"?>.. . < 628DEA70: 626C6F63 6B3E0A20 20202020 203C212D block>. -->


DB-865


The following is sample output from the debug http client socket command: Router# debug http client socket HTTP Client Sockets debugging is on *Jan 3 11:32:38.353: port(80) *Jan 3 11:32:38.377: port(80) *Jan 3 11:32:38.381: *Jan 3 11:32:38.389: port(80) *Jan 3 11:32:38.393: *Jan 3 11:32:38.397: port(80) *Jan 3 11:32:40.361: *Jan 3 11:32:40.413: *Jan 3 11:40:43.557:

httpc_process_read_ev: HTTPC SOCK_PENDING --> SOCK_CONNECTED fd(0) httpc_process_read_ev: HTTPC SOCK_PENDING --> SOCK_CONNECTED fd(1) httpc_socket_cleanup: fd(1) httpc_process_read_ev: HTTPC SOCK_PENDING --> SOCK_CONNECTED fd(1) httpc_socket_cleanup: fd(1) httpc_process_read_ev: HTTPC SOCK_PENDING --> SOCK_CONNECTED fd(1) httpc_socket_cleanup: fd(0) httpc_socket_cleanup: fd(1) httpc socket_connect failed fd(2)

The following is sample output from the debug http client error command: Router# debug http client error HTTP Client Error debugging is on *Jan 3 12:07:40.209: HTTPC URL:http://serverX.com/vxml/test.vxml, Server rsp_code(404), fd(0) *Jan 3 12:08:01.677: HTTPC SOCK_FAIL() - msg(62CA5FB4)URL:http://serverX/vxml/test.vxml *Jan 3 12:08:01.677: httpc_free: NULL pointer argument *Jan 3 12:08:01.677: HTTPC URL:http://serverX/vxml/test.vxml, MSG_XMIT_ERROR, fd(-1) Jan 3 23:44:06 PDT: HTTPC URL:http://serverY.com:9000/ivr/sid-351/dropoffDeposit?pri=0&disconnect=1, TIMEOUT(60000 msec), fd(-1) Jan 3 23:44:07 PDT: HTTPC msg timeout waiting for rsp - fd(21) Jan 3 23:44:07 PDT: httpc_free: NULL pointer argument Jan 4 02:45:07 PDT: HTTPC msg timeout waiting for rsp - fd(0) Jan 4 02:45:07 PDT: HTTPC URL:http://rtsp-ws/dropoffAppend.php?append=&disconnect=1, TIMEOUT(10000 msec), fd(-1) Jan 4 02:46:07 PDT: httpc_msg_read: URL(http://1.7.100.1/vxml/root.vxml) - msg length not available.Failed to parse message body. Jan 4 02:46:07 PDT: httpc_msg_read: ERROR - DECODE Jan 4 02:46:08 PDT: HTTPC bad message read - fd(6), conp(632A93B4), msg(63280794)URL:http://1.7.100.1/vxml/test/root.vxml, len(1611) Jan 4 02:46:08 PDT: First 400 bytes read from socket: 6241D9C0: 6241D9D0: 6241D9E0: 6241D9F0: 6241DA00: 6241DA10: 6241DA20: 6241DA30: 6241DA40: 6241DA50:

6D6C2076 3F3E0A3C 3D22312E 65727479 6E672220 2F3E0A20 616D653D 6C75653D 726F7065

65727369 76786D6C 30223E0A 206E616D 76616C75 203C7072 2274696D 22333073 72747920

6F6E3D22 20766572 0A20203C 653D2263 653D2273 6F706572 656F7574 222F3E0A 6E616D65

3C3F78 312E3022 73696F6E 70726F70 61636869 61666522 7479206E 22207661 20203C70 3D226665

... . .
. .. . . < 6241DAF0: 76617220 6E616D65 3D226861 6E646C65 var name="handle 6241DB00: 22206578 70723D22 74727565 222F3E0A " expr="true"/>. 6241DB10: 0A20203C 63617463 68206576 656E743D . . *Apr 7 12:40:05.983: Mica Modem(1/0): State Transition to Steady State *Apr 7 12:40:05.983: Mica Modem(1/3): State Transition to Steady State+++ OK ath *Apr 7 12:40:09.167: Mica Modem(1/0): State Transition to Steady State Escape *Apr 7 12:40:10.795: Mica Modem(1/0): State Transition to Terminating *Apr 7 12:40:10.795: Mica Modem(1/3): State Transition to Terminating *Apr 7 12:40:11.755: Mica Modem(1/3): State Transition to Idle *Apr 7 12:40:11.755: Mica Modem(1/3): Went onhook


DB-1507

Debug Commands debug modem csm

*Apr 7 12:40:11.755: CSM_PROC_IC5_OC6_CONNECTED: CSM_EVENT_MODEM_ONHOOK at slot 1, port 3 *Apr 7 12:40:11.755: VDEV_DEALLOCATE: slot 1 and port 3 is deallocated *Apr 7 12:40:11.759: neat msg at slot 0: (0/0): Tx LOOP_OPEN (ABCD=0101) *Apr 7 12:40:11.767: neat msg at slot 0: (1/0): Rx LOOP_OPEN (ABCD=0101) *Apr 7 12:40:12.087: neat msg at slot 0: (1/0): Tx LOOP_OPEN (ABCD=0101) *Apr 7 12:40:12.091: neat msg at slot 0: (0/0): Rx LOOP_OPEN (ABCD=0101) *Apr 7 12:40:12.111: CSM_RX_CAS_EVENT_FROM_NEAT:(A001): EVENT_CALL_IDLE at slot 1 and port 0 *Apr 7 12:40:12.111: CSM_PROC_IC5_OC6_CONNECTED: CSM_EVENT_DSX0_DISCONNECTED at slot 1, port 0 *Apr 7 12:40:12.111: Mica Modem(1/0): Link Terminate(0x6) *Apr 7 12:40:12.779: Mica Modem(1/3): State Transition to Terminating *Apr 7 12:40:12.839: Mica Modem(1/3): State Transition to Idle *Apr 7 12:40:13.495: Mica Modem(1/0): State Transition to Idle *Apr 7 12:40:13.495: Mica Modem(1/0): Went onhook *Apr 7 12:40:13.495: CSM_PROC_IC6_OC8_DISCONNECTING: CSM_EVENT_MODEM_ONHOOK at slot 1, port 0 *Apr 7 12:40:13.495: VDEV_DEALLOCATE: slot 1 and port 0 is deallocated Router#disc Closing connection to 1.19.36.7 [confirm] Router# *Apr 7 12:40:18.783: Mica Modem(1/0): State Transition to Terminating *Apr 7 12:40:18.843: Mica Modem(1/0): State Transition to Idle Router#

The MICA technologies modem goes through the following internal link states when the call comes in: •

Call Setup

•

Off Hook

•

Connect

•

Link

•

Trainup

•

EC Negotiation

•

Steady State

The following section describes the CSM activity for an incoming call. When a voice call comes in, CSM is informed of the incoming call. This allocates the modem and sends the Call Setup message to the MICA modem. The Call_Proc message is sent through D channel. The modem sends an offhook message to CSM by sending the state change to Call Setup. The D channel then sends a CONNECT message. When the CONNECT_ACK message is received, the Link initiate message is sent to the MICA modem and it negotiates the connection with the remote modem. In the following debug examples, a modem on slot 1, port 13 is allocated. It goes through its internal states before it is in Steady State and answers the call. Router# debug modem csm Modem Management Call Switching Module debugging is on *May 13 15:01:00.609: MODEM_REPORT:dchan_idb=0x60D437F8, call_id=0xE, ces=0x1 bchan=0x12, event=0x1, cause=0x0 *May 13 15:01:00.609: VDEV_ALLOCATE: slot 1 and port 13 is allocated. *May 13 15:01:00.609: MODEM_REPORT(000E): DEV_INCALL at slot 1 and port 13 *May 13 15:01:00.609: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 1, port 13 *May 13 15:01:00.609: Mica Modem(1/13): Configure(0x0) *May 13 15:01:00.609: Mica Modem(1/13): Configure(0x0) *May 13 15:01:00.609: Mica Modem(1/13): Configure(0x6) *May 13 15:01:00.609: Mica Modem(1/13): Call Setup *May 13 15:01:00.661: Mica Modem(1/13): State Transition to Call Setup *May 13 15:01:00.661: Mica Modem(1/13): Went offhook


DB-1508

May 2008


*May 13 15:01:00.661: CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 13 *May 13 15:01:00.661: MODEM_REPORT:dchan_idb=0x60D437F8, call_id=0xE, ces=0x1 bchan=0x12, event=0x4, cause=0x0 *May 13 15:01:00.661: MODEM_REPORT(000E): DEV_CONNECTED at slot 1 and port 13 *May 13 15:01:00.665: CSM_PROC_IC3_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 13 *May 13 15:01:00.665: Mica Modem(1/13): Link Initiate *May 13 15:01:00.693: Mica Modem(1/13): State Transition to Connect *May 13 15:01:01.109: Mica Modem(1/13): State Transition to Link *May 13 15:01:09.433: Mica Modem(1/13): State Transition to Trainup *May 13 15:01:11.541: Mica Modem(1/13): State Transition to EC Negotiating *May 13 15:01:12.501: Mica Modem(1/13): State Transition to Steady State

The following section describes the status of CSM when a call is connected. The show modem csm x/y command is similar to AS5200 access server. For an active incoming analog call, the modem_status and csm_status should be VDEV_STATUS_ACTIVE_CALL and CSM_IC4_CONNECTED, respectively. Router# show modem csm 1/13 MODEM_INFO: slot 1, port 13, unit 0, modem_mask=0x0000, modem_port_offset=0 tty_hwidb=0x60D0BCE0, modem_tty=0x60B6FE7C, oobp_info=0x00000000, modem_pool=0x60ADC998 modem_status(0x0002):VDEV_STATUS_ACTIVE_CALL. csm_state(0x0204)=CSM_IC4_CONNECTED, csm_event_proc=0x600C6968, current call thru PRI line invalid_event_count=0, wdt_timeout_count=0 wdt_timestamp_started is not activated wait_for_dialing:False, wait_for_bchan:False pri_chnl=TDM_PRI_STREAM(s0, u0, c18), modem_chnl=TDM_MODEM_STREAM(s1, c13) dchan_idb_start_index=0, dchan_idb_index=0, call_id=0x000E, bchan_num=18 csm_event=CSM_EVENT_ISDN_CONNECTED, cause=0x0000 ring_indicator=0, oh_state=0, oh_int_enable=0, modem_reset_reg=0 ring_no_answer=0, ic_failure=0, ic_complete=1 dial_failure=0, oc_failure=0, oc_complete=0 oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0 remote_link_disc=0, stat_busyout=0, stat_modem_reset=0 oobp_failure=0 call_duration_started=1d02h, call_duration_ended=00:00:00, total_call_duration=00:00:00 The calling party phone number = 4085552400 The called party phone number = 4085551400 total_free_rbs_timeslot = 0, total_busy_rbs_timeslot = 0, total_dynamic_busy_rbs_timeslot = 0, total_static_busy_rbs_timeslot = 0, min_free_modem_threshold = 6

The following section describes the CSM activity for an outgoing call. For MICA modems, the dial tone is not required to initiate an outbound call. Unlike in the AS5200, the digit collection step is not required. The dialed digit string is sent to the CSM in the outgoing request to the CSM. CSM signals the D channel to generate an outbound voice call, and the B channel assigned is connected to the modem and the CSM. The modem is ordered to connect to the remote side with a CONNECT message, and by sending a link initiate message, the modem starts to train.


DB-1509


Router# debug modem csm Modem Management Call Switching Module debugging is on Router# debug isdn q931 ISDN Q931 packets debugging is on *May 15 12:48:42.377: Mica Modem(1/0): Rcvd Dial String(5552400) *May 15 12:48:42.377: CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 0 *May 15 12:48:42.377: CSM_PROC_OC3_COLLECT_ALL_DIGIT: CSM_EVENT_GET_ALL_DIGITS at slot 1, port 0 *May 15 12:48:42.377: CSM_PROC_OC3_COLLECT_ALL_DIGIT: called party num: (5552400) at slot 1, port 0 *May 15 12:48:42.381: process_pri_call making a voice_call. *May 15 12:48:42.381: ISDN Se0:23: TX -> SETUP pd = 8 callref = 0x0011 *May 15 12:48:42.381: Bearer Capability i = 0x8090A2 *May 15 12:48:42.381: Channel ID i = 0xE1808397 *May 15 12:48:42.381: Called Party Number i = 0xA1, '5552400' *May 15 12:48:42.429: ISDN Se0:23: RX HANGUP dropping DTR, hanging up Modem: HANGUP->IDLE restoring DTR DSR came up


DB-1534

May 2008

Debug Commands debug mpls adjacency

debug mpls adjacency To display changes to label switching entries in the adjacency database, use the debug mpls adjacency command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls adjacency no debug mpls adjacency

Usage Guidelines


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.1(3)T

This command was modified to reflect new MPLS IETF terminology and CLI command syntax.

12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug mpls adjacency command to monitor when entries are updated in or added to the adjacency database.

Examples

The following is sample output from the debug mpls adjacency command: Router# debug mpls adjacency TAG ADJ: add 10.10.0.1, Ethernet0/0/0 TAG ADJ: update 10.10.0.1, Ethernet0/0/0

Table 212 describes the significant fields shown in the sample display. Table 212

debug mpls adjacency Field Description

Field

Description

add

Adding an entry to the database.

update

Updating the MAC address for an existing entry.


DB-1535

Debug Commands debug mpls adjacency

Table 212

debug mpls adjacency Field Description (continued)

Field

Description

10.10.0.1

Address of neighbor TSR.

Ethernet0/0/0

Connecting interface.


DB-1536

May 2008

Debug Commands debug mpls atm-cos

debug mpls atm-cos To display ATM label virtual circuit (VC) bind or request activity that is based on the configuration of a Quality of Service (QoS) map, use the debug mpls atm-cos command in privileged EXEC mode. debug mpls atm-cos [bind | request]

Syntax Description

bind

(Optional) Specifies debug information about bind responses for a VC path.

request

(Optional) Specifies debug information about bind requests for a VC path.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


Examples

12.0(10)ST

This command was modified to reflect MPLS IETF syntax and terminology.

12.2(2)T

This command was incorporated into Cisco IOS Release 12.2(2)T.

12.2(33)SRA


12.2SX


The following command sequence demonstrates how to obtain sample output from the debug mpls atm-cos command. First, display the Multiprotocol Label Switching (MPLS) forwarding table to see which prefixes are associated with a single label VC (LVC), as shown below: Router# show mpls forwarding Local tag 26 27 28 29 30 31 32 33 34 35 36 37 38

Outgoing tag or VC 28 Pop tag 27 30 Pop tag 2/34 Pop tag Pop tag Pop tag 2/36 35 36 37 37

Prefix or Tunnel Id 17.17.17.17/32 11.11.11.11/32 16.16.16.16/32 92.0.0.0/8 95.0.0.0/8 10.10.10.10/32 14.14.14.14/32 90.0.0.0/8 96.0.0.0/8 96.0.0.0/8 93.0.0.0/8 12.12.12.12/32 15.15.15.15/32 18.18.18.18/32

Bytes tag switched 0 1560 0 0 2600 0 0 0 0 0 0 0 0 0

Outgoing interface PO6/0 PO6/0 PO6/0 PO6/0 PO6/0 AT2/0.1 Fa5/0 Fa5/0 Fa5/0 AT2/0.1 PO6/0 PO6/0 PO6/0 Fa5/0

Next Hop point2point point2point point2point point2point point2point point2point 91.0.0.1 91.0.0.1 91.0.0.1 point2point point2point point2point point2point 91.0.0.1


DB-1537

Debug Commands debug mpls atm-cos

39 40

39 40

97.0.0.0/8 98.0.0.0/8

540 0

PO6/0 PO6/0

point2point point2point

Second, enable debugging of request and bind events, as shown in the command sequence below: Router# debug mpls atm-cos ? bind request

Bind response for VC path Requests for VC binds path

Router# debug mpls atm-cos request ATM TAGCOS VC requests debugging is on Router# debug mpls atm-cos bind ATM TAGCOS Bind response debugging is on

Third, configure an MPLS ATM subinterface for multi-VC mode. The corresponding request and bind events are displayed, as shown below: Router# conf terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# int a2/0.1 Router(config-subif)# mpls atm multi-vc Router(config-subif)# end Router# 19:59:14:%SYS-5-CONFIG_I:Configured from console by console Router# 19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, available 19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, standard 19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, premium 19:59:24:TAGCOS-REQ:vc request 10.10.10.10/32, control 19:59:24:TAGCOS-REQ:vc request 96.0.0.0/8, available 19:59:24:TAGCOS-REQ:vc request 96.0.0.0/8, standard 19:59:24:TAGCOS-REQ:vc request 96.0.0.0/8, premium 19:59:24:TAGCOS-REQ:vc request 96.0.0.0/8, control TAGCOS-REQ/TCATM:11.11.11.11/32,len=4352,band=1099528405504,class=0x700 TAGCOS-REQ/TCATM:12.12.12.12/32,len=4352,band=2199040033280,class=0x700 TAGCOS-REQ/TCATM:13.13.13.13/32,len=4352,band=3298551661056,class=0x700 TAGCOS-REQ/TCATM:14.14.14.14/32,len=4352,band=4398063288832,class=0x700 TAGCOS-REQ/TCATM:15.15.15.15/32,len=4352,band=5497574916608,class=0x700 TAGCOS-REQ/TCATM:16.16.16.16/32,len=4352,band=6597086544384,class=0x700 TAGCOS-REQ/TCATM:17.17.17.17/32,len=4352,band=7696598172160,class=0x700 TAGCOS-REQ/TCATM:18.18.18.18/32,len=4352,band=8796109799936,class=0x700 TAGCOS-REQ/TCATM:90.0.0.0/8,len=768,band=3940649674539009,class=0x2 TAGCOS-REQ/TCATM:91.0.0.0/8,len=768,band=3940649674604545,class=0x2 TAGCOS-REQ/TCATM:92.0.0.0/8,len=768,band=3940649674670081,class=0x2 TAGCOS-REQ/TCATM:93.0.0.0/8,len=768,band=3940649674735617,class=0x2 TAGCOS-REQ/TCATM:94.0.0.0/8,len=768,band=3940649674801153,class=0x2 TAGCOS-REQ/TCATM:95.0.0.0/8,len=768,band=3940649674866689,class=0x2 TAGCOS-REQ/TCATM:97.0.0.0/8,len=768,band=3940649674932225,class=0x2 TAGCOS-REQ/TCATM:98.0.0.0/8,len=768,band=3940649674997761,class=0x2 TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=41 - control 41,41,41,41 TAGCOS-BIND:binding_ok 10.10.10.10/32, Inform TFIB pidx=0, in_tag=31, idx=0x80000000 TAGCOS-BIND:binding_ok 96.0.0.0/8,VCD=42 - control 42,42,42,42 TAGCOS-BIND:binding_ok 96.0.0.0/8, Inform TFIB pidx=1, in_tag=34, idx=0x80000001 TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=43 - premium 43,43,43,41 TAGCOS-BIND:binding_ok 96.0.0.0/8,VCD=44 - premium 44,44,44,42 TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=45 - standard 45,45,43,41 TAGCOS-BIND:binding_ok 96.0.0.0/8,VCD=46 - standard 46,46,44,42 TAGCOS-BIND:binding_ok 10.10.10.10/32,VCD=47 - available 47,45,43,41 TAGCOS-BIND:binding_ok 96.0.0.0/8,VCD=48 - available 48,46,44,42


DB-1538

May 2008

Debug Commands debug mpls atm-ldp api

debug mpls atm-ldp api To display information about the virtual channel identifier (VCI) allocation of label virtual circuits (LVCs), label-free requests, and cross-connect requests, use the debug mpls atm-ldp api command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls atm-ldp api no debug mpls atm-ldp api

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST

This command was modified to reflect MPLS IETF command syntax and terminology.

12.0(14)ST


12.1(2)T


12.1(8a)E

This command was integrated into Cisco IOS Release 12.1(8a)E.

12.2(2)T


12.2(4)T


Usage Guidelines

12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX


Use the debug mpls atm-ldp api command in conjunction with the debug mpls atm-ldp routes and debug mpls atm-ldp states command to display more complete information about an LVC.


DB-1539

Debug Commands debug mpls atm-ldp api

Examples

The following shows sample output from the debug mpls atm-ldp api command: Router# debug mpls atm-ldp api Tailend Router Free label Req 167.50.0.0 on ATM0/0.2 VPI/VCI 1/674 TAGATM_API: received label free request interface: ATM0/0.2 dir: in vpi: 1 vci: 674 TAGATM_API: completed label free interface: ATM0/0.2 vpi: 1 vci: 674 result: TAGATM_OK


Related Commands

debug mpls atm-ldp api Field Descriptions

Field

Description

TAGATM_API

Subsystem that displays the message.

interface

Interface used by the driver to allocate or free VPI/VCI resources.

dir

Direction of the VC: •

In—Input or receive VC

•

Out—Output VC

vpi

Virtual path identifier.

vci

Virtual channel identifier.

result

The return error code from the driver API.

Command

Description

debug mpls atm-ldp states

Displays information about LVC state transitions as they occur.


DB-1540

May 2008

Debug Commands debug mpls atm-ldp failure

debug mpls atm-ldp failure To display failure information about the LC-ATM, use the debug mpls atm-ldp failure command in privileged EXEC mode. To disable this feature, use the no form of the command. debug mpls atm-ldp failure no debug mpls atm-ldp failure

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)T


12.0(21)ST

This command was integrated into Cisco IOS 12.0(21)ST.

12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug mpls atm-ldp failure command to display failure information about the LC-ATM. This command is useful for determining failure cases. This command displays only failure information, unlike the debug mpls atm-ldp api command, which displays all API events.

Examples

This section shows sample output from the debug mpls atm-ldp failure command. The following failure message displays during a race condition where the LC-ATM attempts to allocate label virtual circuits (LVCs) on an interface where MPLS has been disabled: Router# debug mpls atm-ldp failure TAGATM_API_FAILURE: allocate_tag_req on ATM1/0/0 tagsw not enabled

The following failure message displays when the LC-ATM fails to deallocate the output leg LVC of a cross connect: Router# debug mpls atm-ldp failure


DB-1541

Debug Commands debug mpls atm-ldp failure

TAGATM_API_FAILURE: connDeAllocateHalfLeg returned false interface: ATM1/0/0 vpi: 1 vci: 48

The following failure message displays when a cross connect cannot be installed on the switching fabric. The result code is also provided. Router# debug mpls atm-ldp failure TAGATM_API_FAILURE: setup_xconn_req InstallSvcXconn failed result

The following message displays when attempts to establish a cross connect fail. The result describes the reason for the failure. Router# debug mpls atm-ldp failure TCATM-4-XCONNECT_FAILED: 10.254.13.237/32 for ATM0/1/2 ATM1/0/0 TAGATM_API: x-conn setup request completed input interface: ATM0/1/2 vpi: 1 vci: 48 output interface: ATM1/0/0 vpi: 2 vci: 2038 result = TAGATM_FAIL Xconnect setup response for 10.254.13.215: failure, 8

The following message displays when attempts to remove a cross connect fail. The result describes why the cross connect cannot be removed. Router# debug mpls atm-ldp failure TCATM-4-XCONNECT_REMOVE_FAILED: Remove XConnect API failed for ATM1/0/12 1/894 -> ATM1/0/13 1/528 TAGATM_API: x-conn remove request completed input interface: ATM1/0/12 vpi: 1 vci: 894 output interface: ATM1/0/13 vpi: 1 vci: 528 result = TAGATM_FAIL

Related Commands

Command

Description

debug mpls atm-ldp api

Displays all driver API events.


DB-1542

May 2008

Debug Commands debug mpls atm-ldp routes

debug mpls atm-ldp routes To display information about the state of the routes for which virtual circuit identifier (VCI) requests are being made, use the debug mpls atm-ldp routes command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls atm-ldp routes no debug mpls atm-ldp routes

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Command

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


Usage Guidelines

12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX


When there are many routes and system activities (that is, shutting down interfaces, learning new routes, and so forth), the debug mpls atm-ldp routes command displays extensive information that might interfere with system timing. Most commonly, this interference affects normal label distribution protocol (LDP) operation. To avoid this problem, you can increase the LDP hold time by means of the mpls ldp holdtime command.


DB-1543

Debug Commands debug mpls atm-ldp routes

Examples

The following shows sample output from the debug mpls atm-ldp routes command: Router# debug mpls atm-ldp routes CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0 tcatmFindRouteTags,153.7.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0 AddNewRoute,153.7.0.0/16,idb=ATM0/0.2 CleanupRoutes,153.7.0.0/16 CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0 tcatmFindRouteTags,153.8.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0 AddNewRoute,153.8.0.0/16,idb=ATM0/0.2 CleanupRoutes,153.8.0.0/16 CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0 tcatmFindRouteTags,153.9.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0 AddNewRoute,153.9.0.0/16,idb=ATM0/0.2 CleanupRoutes,153.9.0.0/16 CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0 tcatmFindRouteTags,153.10.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0 AddNewRoute,153.10.0.0/16,idb=ATM0/0.2 CleanupRoutes,153.10.0.0/16 CleanupRoutes,not deleting route of idb ATM0/0.2,rdbIndex 0 tcatmFindRouteTags,153.11.0.0/16,idb=ATM0/0.2,nh=134.111.102.98,index=0 AddNewRoute,153.11.0.0/16,idb=ATM0/0.2 CleanupRoutes,153.11.0.0/16


debug mpls atm-ldp routes Field Descriptions

Field

Description

CleanupRoutes

Cleans up the routing table after a route has been deleted.

not deleting route of idb The route cleanup event has not removed the specified route. ATM0/0.2

Related Commands

rdbIndex

Index identifying the route.

tcatmFindRouteTags

Request a VC for the route.

idb

The internal descriptor for an interface.

nh

Next hop for the route.

index

Identifier for the route.

AddNewRoute

Action of adding routes for a prefix or address.

Command

Description

mpls ldp holdtime

Changes the time an LDP session is maintained in the absence of LDP messages from the session peer.


DB-1544

May 2008

Debug Commands debug mpls atm-ldp states

debug mpls atm-ldp states To display information about label virtual circuit (LVC) state transitions as they occur, use the debug mpls atm-ldp states command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls atm-ldp states no debug mpls atm-ldp states

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


Usage Guidelines

12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX


When there are many routes and system activities (such as shutting down interfaces, learning new routes, and so forth), the debug mpls atm-ldp states command outputs extensive information that might interfere with system timing. Most commonly, this interference affects normal label distribution protocol (LDP) operation. To avoid this problem, you should increase the LDP hold time by means of the mpls ldp holdtime command.


DB-1545

Debug Commands debug mpls atm-ldp states

Examples

The following shows sample output from the debug mpls atm-ldp states command: Router# debug mpls atm-ldp states Transit Transit Transit Transit Transit Transit Transit

Output 166.35.0.0 VPI/VCI 1/67 Input 166.35.0.0 VPI/VCI 1/466 Input 166.35.0.0 VPI/VCI 1/466 Input 166.35.0.0 VPI/VCI 1/466 Input 166.35.0.0 VPI/VCI 1/466 Input 166.35.0.0 VPI/VCI 1/466 Input 166.35.0.0 VPI/VCI 1/466

Active -> XmitRelease NoPath Active -> ApiWaitParentLoss ParentLoss ApiWaitParentLoss -> ParentWait ApiSuccess ParentWait -> XmitWithdraw NoPath XmitWithdraw -> XmitWithdraw Transmit XmitWithdraw -> NonExistent Release NonExistent -> NonExistent ApiSuccess


Related Commands

debug mpls atm-ldp states Field Descriptions

Field

Description

Transit Output

Output side of an LVC.

VPI/VCI

VC value.

Transit Input

Input side of an LVC.

Command

Description

mpls ldp holdtime

Changes the time an LDP session is maintained in the absence of LDP messages from the session peer.


DB-1546

May 2008

Debug Commands debug mpls checkpoint label-binding

debug mpls checkpoint label-binding To display the events for the checkpoint label bindings of Multiprotocol Label Switching (MPLS) applications running on the router, use the debug mpls checkpoint label-binding command in privileged EXEC mode. To disable the display of these events, use the no form of this command. debug mpls checkpoint label-binding no debug mpls checkpoint label-binding

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB

This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series router.

12.2(33)SRA


12.2SX


Usage Guidelines

Use this command with caution. The command displays the events for every label binding.

Examples

The following example shows the output when you issue the command on the standby Route Processor: Router# debug mpls checkpoint label-binding MPLS Label Binding Checkpoint debugging is on 3d17h: mpls_lbl_bind_chkpt: client ID 13 up, total client 1 3d17h: mpls_lbl_bind_chkpt: msg rx for 1D, vers 0, type 1 action 56, len 0, state 4, peer 13 3d17h: mpls_lbl_bind_chkpt: post msg type 1 3d17h: mpls_lbl_bind_chkpt: msg rx for 1D, vers 0, type 1 action 56, len 0, state 4, peer 13 3d17h: mpls_lbl_bind_chkpt: post msg type 1 3d17h: mpls_lbl_bind_chkpt: msg rx for 1D, vers 0, type 1 action 56, len 0, state 4, peer 13 3d17h: mpls_lbl_bind_chkpt: post msg type 1 3d17h: mpls_lbl_bind_chkpt: appl_id 13, KEY 000C800018888200 3d17h: mpls_chkpt_db: AVL insert successful, Key 000C800018888200 action Add, label 19 3d17h: mpls_lbl_bind_chkpt: appl_id 13, KEY 000C800013200080 3d17h: mpls_chkpt_db: AVL insert successful, Key 000C800013200080 action Add, label 20


DB-1547

Debug Commands debug mpls checkpoint label-binding

3d17h: 3d17h: 3d17h: 3d17h: 3d17h: action 3d17h: 3d17h:

Related Commands

mpls_lbl_bind_chkpt: appl_id 13, KEY 000C8000138383838200 mpls_chkpt_db: AVL insert successful, Key 000C8000138383838200 action Add, label 21 Stby RP OR CF peer not ready, don't send msg mpls_lbl_bind_chkpt: client ID 13 down, total client 0 mpls_lbl_bind_chkpt: msg rx for 1D, vers 0, type 1 56, len 2, state 4, peer 13 mpls_lbl_bind_chkpt: post msg type 1 mpls_lbl_bind_chkpt: appl_id 13, KEY action NSF unconfig, appl id 13

Command

Description

debug ip bgp vpnv4 checkpoint

Display the events for the VRF checkpointing system between the active and standby Route Processors.


DB-1548

May 2008

Debug Commands debug mpls events

debug mpls events To display information about significant Multiprotocol Label Switching (MPLS) events, use the debug mpls events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls events no debug mpls events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command to monitor significant MPLS events.

Examples

The following is sample output from the debug mpls events command: Router# debug mpls events MPLS events debugging is on TAGSW: Unbound IP address, 155.0.0.55, from Router ID TAGSW: Bound IP address, 199.44.44.55, to Router ID


DB-1549

Debug Commands debug mpls ip iprm cef

debug mpls ip iprm cef To display debugging information for interactions between Cisco Express Forwarding and the Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM), use the debug mpls ip iprm cef command in privileged EXEC mode. To disable the display of these events, use the no form of this command. debug mpls ip iprm cef [table {all | table-id} | vrf vrf-name | acl acl-name | prefix-list prefix-list-name] no debug mpls ip iprm cef

Syntax Description

table

(Optional) Displays the debugging information for one or more routing tables.

all

Displays debugging information for all routing tables.

table-id

The ID of the routing table for which you want to display debugging information. Table 0 is the default or global routing table.

vrf

(Optional) Displays debugging information for the VPN routing and forwarding (VRF) instance you specify.

vrf-name

The name of the VRF instance. You can find VRF names with the show ip vrf command.

acl

(Optional) Displays debugging information for the access control list (ACL) you specify.

acl-name

The name of the ACL. You can find ACL names with the show ip access-list command.

prefix-list

(Optional) Displays debugging information for the prefix list you specify.

prefix-list-name

The name of the prefix list. You can find prefix list names with the show ip prefix-list command.

Defaults

Debugging is not enabled. If you do not supply an optional keyword, all the debugging events are displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX



DB-1550

May 2008

Debug Commands debug mpls ip iprm cef

Usage Guidelines

This command limits the debug output to the IPRM interactions with Cisco Express Forwarding.

Examples

In the following example, IPRM events related to Cisco Express Forwarding are displayed. Cisco 7500 Series Example Router# debug mpls ip iprm cef IPRM CEF interaction debugging is on for global routing table iprm: prefix deleted: 10.0.0.44/32(glbl) iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38002 iprm: announce prefix local labels: lcatm; trans #94; 10.0.0.44/32(glbl); 0 labels; flags 0x0 ... iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38000 iprm: announce prefix local labels: lcatm; trans #97; 10.0.0.44/32(glbl); 0 labels; flags 0x0 iprm: get path labels: 10.0.0.44/32(glbl); nh 59.0.0.55(glbl), Et4/0/1; trans #97; recurs tree change iprm: announce prefix local labels: ldp; trans #97; 10.0.0.44/32(glbl); 1 label; flags 0x0 iprm: lab 21, ltbl 0 iprm: announce path labels: ldp; trans #97; 10.0.0.44/32(glbl); 0 labels; flags 0x0 iprm: path: nh 59.0.0.55(glbl), Et4/0/1

Cisco 10000 Series Example Router# debug mpls ip iprm cef IPRM CEF interaction debugging is on for global routing table iprm: prefix deleted: 10.0.0.44/32(glbl) iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38002 ... iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38000 iprm: get path labels: 10.0.0.44/32(glbl); nh 59.0.0.55(glbl), GigabitEthernet4/0/0; trans #97; recurs tree change iprm: announce prefix local labels: ldp; trans #97; 10.0.0.44/32(glbl); 1 label; flags 0x0 iprm: lab 21, ltbl 0 iprm: announce path labels: ldp; trans #97; 10.0.0.44/32(glbl); 0 labels; flags 0x0 iprm: path: nh 59.0.0.55(glbl), GigabitEthernet4/0/0

See the field descriptions for the debug mpls ip iprm command for an explanation of the fields displayed in the output.

Related Commands

Command

Description

debug mpls ip iprm events

Displays events related to the MPLS IPRM.

debug mpls ip iprm ldm

Displays debugging information for interactions between the IP LDMs and the MPLS IPRM.

debug mpls ip iprm mfi

Displays debugging information for interactions between the MFI and the MPLS IPRM.


DB-1551

Debug Commands debug mpls ip iprm events

debug mpls ip iprm events To display events related to the Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM), use the debug mpls ip iprm events command in privileged EXEC mode. To disable the display of these events, use the no form of this command. debug mpls ip iprm events no debug mpls ip iprm events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX


Examples

See the command page for debug mpls ip iprm for sample command output. See the command page for debug mpls ip iprm for an explanation of the fields displayed in the output.

Related Commands

Command

Description

debug mpls ip iprm cef Displays debugging information for interactions between Cisco Express Forwarding and the IPRM. debug mpls ip iprm ldm

Displays debugging information for interactions between the LDMs and the MPLS IPRM.




DB-1552

May 2008

Debug Commands debug mpls ip iprm ldm

debug mpls ip iprm ldm To display debugging information for interactions between the IP Label Distribution Modules (LDMs) and the Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM), use the debug mpls ip iprm ldm command in privileged EXEC mode. To disable the display of this information, use the no form of this command. debug mpls ip iprm ldm [bgp | lcatm | ldp | vpnv4 | 6pe | table {all | table-id} | vrf vrf-name | acl acl-name | prefix-list prefix-list-name] no debug mpls ip iprm ldm Cisco 10000 Series Routers

debug mpls ip iprm ldm [bgp | ldp | vpnv4 | table {all | table-id} | vrf vrf-name | acl acl-name | prefix-list prefix-list-name] no debug mpls ip iprm ldm

Syntax Description

bgp

(Optional) Displays Border Gateway Protocol (BGP) events.

lcatm

(Optional) Displays Label Controlled ATM (LC-ATM) events. Note

ldp

(Optional) Displays Label Distribution Protocol (LDP) events.

vpnv4

(Optional) Displays Virtual Private Network (VPNv4) events.

6pe

(Optional) Displays IPv6 over MPLS events. Note

Defaults

Applies to Cisco 7000 series routers only.

Applies to Cisco 7000 series routers only.

table

(Optional) Displays debugging information for one or more routing tables.

all

(Optional) Displays debugging information for all routing tables.

table-id

(Optional) Specifies the routing table for which you want to display debugging information. Table 0 is the default or global routing table.

vrf

(Optional) Displays debugging information for the VPN routing and forwarding (VRF) instance you specify.

vrf-name

(Optional) The name of the VRF instance. You can find VRF names with the show ip vrf command.

acl


acl-name

(Optional) The name of the ACL. You can find ACL names with the show ip access-list command.

prefix-list


prefix-list-name

(Optional) The name of the prefix list. You can find prefix list names with the show ip prefix-list command.

Debugging is not enabled. If you do not supply an optional keyword, all the debugging events are displayed.


DB-1553

Debug Commands debug mpls ip iprm ldm

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX


Examples

See the debug mpls ip iprm command page for sample output and an explanation of the fields displayed in the output.

Related Commands

Command

Description

debug mpls ip iprm cef Displays debugging information for interactions between Cisco Express Forwarding and the IPRM. debug mpls ip iprm events

Displays debugging information about events related to the MPLS IPRM.




DB-1554

May 2008

Debug Commands debug mpls ip iprm mfi

debug mpls ip iprm mfi To display debugging information for interactions between the Multiprotocol Label Switching (MPLS) Forwarding Infrastructure (MFI) and the MPLS IP Rewrite Manager (IPRM), use the debug mpls ip iprm mfi command in privileged EXEC mode. To disable the display of this information, use the no form of this command. debug mpls ip iprm mfi [table {all | table-id} | vrf vrf-name | acl acl-name | prefix-list prefix-list-name] no debug mpls ip iprm mfi

Syntax Description

table

(Optional) Displays debugging information for one or more routing tables.

all

(Optional) Displays debugging information for all routing tables.

table-id

(Optional) Displays debugging information for the routing table you specify. Table 0 is the default or global routing table.

vrf

(Optional) Displays debugging information for the VPN Routing and Forwarding (VRF) instance you specify.

vrf-name

(Optional) The name of the VRF instance. You can find VRF names with the show ip vrf command.

acl


acl-name

(Optional) The name of the ACL. You can find ACL names with the show ip access-list command.

prefix-list


prefix-list-name

(Optional) The name of the prefix list. You can find prefix list names with the show ip prefix-list command.

Defaults

Debugging is not enabled. If you enable debugging but do not supply an optional keyword, all the debugging events are displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX



DB-1555


Examples

The command in the following example displays MFI events. Cisco 7500 Series Example Router# debug mpls ip iprm mfi IPRM MFI interaction debugging is on for global routing table iprm: delete mfi rewrite: 10.0.0.44/32(glbl) . . . iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 mois iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label info iprm: omit rewrite create: 10.0.0.44/32(glbl) . . . iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 mois iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label info iprm: lcl lab 21, ltbl 0, ldp iprm: path lab -, nh 59.0.0.55(glbl), Et4/0/1; ldp iprm: create mfi rewrite 10.0.0.44/32(glbl) passed: 2 fpis/1 mois iprm: fpi[0] IV4, owner IPRM; 10.0.0.44/32; glbl iprm: fpi[1] LBL, owner LDP; 21, ltbl 0 iprm: moi[0] PKT, flags 0x8; lab label-no-label; nh 59.0.0.55; nh if Et4/0/1 (nsf)

Cisco 10000 Series Example Router# debug mpls ip iprm mfi IPRM MFI interaction debugging is on for global routing table iprm: delete mfi rewrite: 10.0.0.44/32(glbl) . . . iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 mois iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label info iprm: omit rewrite create: 10.0.0.44/32(glbl) . . . iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 mois iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label info iprm: lcl lab 21, ltbl 0, ldp iprm: path lab -, nh 59.0.0.55(glbl), GigabitEthernet4/0/0; ldp iprm: create mfi rewrite 10.0.0.44/32(glbl) passed: 2 fpis/1 mois iprm: fpi[0] IV4, owner IPRM; 10.0.0.44/32; glbl iprm: fpi[1] LBL, owner LDP; 21, ltbl 0 iprm: moi[0] PKT, flags 0x8; lab label-no-label; nh 59.0.0.55; nh if GigabitEthernet4/0/0 (nsf)

See the debug mpls ip iprm command page for an explanation of the fields displayed in the output.


DB-1556

May 2008


Related Commands

Command

Description

debug mpls ip iprm cef Displays debugging information for interactions between Cisco Express Forwarding and the MPLS IPRM . debug mpls ip iprm events





DB-1557

Debug Commands debug mpls ip iprm

debug mpls ip iprm To display debugging information for the Multiprotocol Label Switching (MPLS) IP Rewrite Manager (IPRM), use the debug mpls ip iprm command in privileged EXEC mode. To disable the display of this information, use the no form of this command. debug mpls ip iprm no debug mpls ip iprm

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX


Usage Guidelines

This command displays all output related to IPRM.

Examples

The command in the following examples display all IPRM debugging for the global routing table. Cisco 7500 Series Example Router# debug mpls ip iprm IPRM debugging is on for global routing table iprm: prefix deleted: 10.0.0.44/32(glbl) iprm: delete mfi rewrite: 10.0.0.44/32(glbl) ... iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38002 iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 mois iprm: announce prefix local labels: lcatm; trans #80; 10.0.0.44/32(glbl); 0 labels; flags 0x0 iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label info iprm: omit rewrite create: 10.0.0.44/32(glbl)


DB-1558

May 2008


iprm: discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38000 iprm: get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 mois iprm: announce prefix local labels: lcatm; trans #81; 10.0.0.44/32(glbl); 0 labels; flags 0x0 iprm: get path labels: 10.0.0.44/32(glbl); nh 59.0.0.55(glbl), Et4/0/1; trans #81; recurs tree change iprm: ldm get path labels: 10.0.0.44/32(glbl), ldp; flags 0x8000 iprm: announce prefix local labels: ldp; trans #81; 10.0.0.44/32(glbl); 1 label; flags 0x0 iprm: lab 21, ltbl 0 iprm: announce path labels: ldp; trans #81; 10.0.0.44/32(glbl); 0 labels; flags 0x0 iprm: path: nh 59.0.0.55(glbl), Et4/0/1 iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label info iprm: lcl lab 21, ltbl 0, ldp iprm: path lab -, nh 59.0.0.55(glbl), Et4/0/1; ldp iprm: create mfi rewrite 10.0.0.44/32(glbl) passed: 2 fpis/1 mois iprm: fpi[0] IV4, owner IPRM; 10.0.0.44/32; glbl iprm: fpi[1] LBL, owner LDP; 21, ltbl 0 iprm: moi[0] PKT, flags 0x8; lab label-no-label; nh 59.0.0.55; nh if Et4/0/1 (nsf)

Cisco 10000 Series Example Router# debug mpls ip iprm IPRM debugging is on for global routing table iprm: iprm: ... iprm: iprm:

prefix deleted: 10.0.0.44/32(glbl) delete mfi rewrite: 10.0.0.44/32(glbl)

iprm: iprm: iprm: iprm:

update mfi rewrite: 10.0.0.44/32(glbl); prefix label info omit rewrite create: 10.0.0.44/32(glbl) discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38000 get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 mois

discover prefix labels: 10.0.0.44/32(glbl); recurs tree change; ctxt 0x38002 get mfi rewrite 10.0.0.44/32(glbl) obtained: 0 fpis/0 mois

iprm: get path labels: 10.0.0.44/32(glbl); nh 59.0.0.55(glbl), GigabitEthernet4/0/0; trans #81; recurs tree change iprm: ldm get path labels: 10.0.0.44/32(glbl), ldp; flags 0x8000 iprm: announce prefix local labels: ldp; trans #81; 10.0.0.44/32(glbl); 1 label; flags 0x0 iprm: lab 21, ltbl 0 iprm: announce path labels: ldp; trans #81; 10.0.0.44/32(glbl); 0 labels; flags 0x0 iprm: path: nh 59.0.0.55(glbl), GigabitEthernet4/0/0 iprm: update mfi rewrite: 10.0.0.44/32(glbl); prefix label info iprm: lcl lab 21, ltbl 0, ldp iprm: path lab -, nh 59.0.0.55(glbl), GigabitEthernet4/0/0; ldp iprm: create mfi rewrite 10.0.0.44/32(glbl) passed: 2 fpis/1 mois iprm: fpi[0] IV4, owner IPRM; 10.0.0.44/32; glbl iprm: fpi[1] LBL, owner LDP; 21, ltbl 0 iprm: moi[0] PKT, flags 0x8; lab label-no-label; nh 59.0.0.55; nh if GigabitEthernet4/0/0 (nsf)

Table 216 describes the significant fields shown in the display. The field descriptions also apply to the output of following debug commands: •

debug mpls ip iprm cef

•



DB-1559


•


•


Table 216

debug mpls ip iprm Field Descriptions

Field

Description

discover prefix labels

The prefix labels that the IP LDM discovered.

announce prefix local labels announce path labels

IP LDMs pass prefix incoming (local) and outgoing (path) labels to IPRM by announcing the labels.

mfi rewrite

The information required by MPLS Forwarding Infrastructure (MFI) to create forwarding data structures for an MPLS forwarding equivalence class (FEC). For IP over MPLS a prefix is an MPLS FEC. An MFI rewrite includes a set of forwarding path identifier (FPI) and MPLS output information (MOI) elements.

fpi

Forwarding path identifier, which is required to locate MPLS forwarding information for a FEC. IP over MPLS deals with several types of FPIs, including IPv4 (IV4), IPv6 (IV6), and label (LBL) FPIs.

Note

The Cisco 10000 series router does not support IPv6.

moi

MPLS output information. For IP over MPLS, there is a MOI for each prefix path. The MOI includes the next hop (nh), outgoing interface (nh if), and outgoing label. IP over MPLS handles several types of MOIs, including packet (PKT) and ATM (ATM).

get/create/update MFI rewrite

The process IPRM uses to read (get) or update (create/update) an MFI rewrite.

recurs tree change

Recursion tree change. Cisco Express Forwarding notifies IPRM when the recursion tree (see below) for a prefix changes. IPRM responds by performing label discovery (see above).

recursion tree

A prefix known to Cisco Express Forwarding can have one or more paths (routes). Each is either a terminal path with a next hop and an outgoing interface or a recursive path with a next hop and no outgoing interface. The next hop for a recursive path typically matches a prefix known to Cisco Express Forwarding. That prefix also has one or more paths. The IP recursion tree for prefix P is a tree rooted at P's Cisco Express Forwarding entry with one of more path descendants. Terminal paths are leaf nodes in P's recursion tree and recursive paths are nonleaf nodes, each of which points to the Cisco Express Forwarding entry for its next hop.

glbl

The global (default) routing table.

ctxt

Context. Information used by IPRM when it performs label discovery.

flags

Information passed between IPRM and other components.

trans #

Transaction number used to identify an ongoing label discovery.


DB-1560

May 2008


Table 216

Related Commands

debug mpls ip iprm Field Descriptions (continued)

Field

Description

ltbl

Label table.

nsf

Nonstop forwarding.

Command

Description

debug mpls ip iprm cef Displays debugging information for interactions between Cisco Express Forwarding and the IPRM. debug mpls ip iprm events



Displays debugging information for interactions between the LDMs and the MPLS IPRM.




DB-1561

Debug Commands debug mpls l2transport checkpoint

debug mpls l2transport checkpoint To enable the display of Any Transport over MPLS (AToM) events when AToM is configured for nonstop forwarding/stateful switchover (NSF/SSO) and Graceful Restart, use the debug mpls l2transport checkpoint command in privileged EXEC mode. To disable the display of these messages, use the no form of this command. debug mpls l2transport checkpoint no debug mpls l2transport checkpoint

Syntax Description


Defaults

Debugging of the AToM NSF/SSO and Graceful Restart feature is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2SX


Usage Guidelines

Use debug commands with care. They use a significant amount of CPU time and can affect system performance.

Examples

In the following example, the output shows that NSF/SSO and Graceful Restart synchronize the data between the active and backup Route Processors after an AToM virtual circuit (VC) is created. (Both the debug mpls l2transport checkpoint and the debug acircuit checkpoint commands are enabled in this example.) The debug mpls l2transport checkpoint command is enabled on the active RP: Router# debug mpls l2transport checkpoint Router# debug acircuit checkpoint Router# show debug AToM HA: AToM checkpointing events and errors debugging is on AC HA: Attachment Circuit Checkpoint debugging is on Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface Fa5/1/1.2


DB-1562

May 2008

Debug Commands debug mpls l2transport checkpoint

Router(config-subif)# xconnect 10.55.55.2 1002 pw-class mpls AToM HA [10.55.55.2, 1002]: Build provision msg, SSM sw/seg 8192/8194 [0x2000/0x2002] PW i d 9216 [0x2400] local label 21 AC HA: Dynamic Sync. Event:4 Sw:8192[2000] Se:16385[4001] AToM HA: CF sync send complete AC HA CF: Sync send complete. Code:0

On the standby Route Processor, the following messages indicate that it receives checkpointing data: AC HA [10.55.55.2, 1002]: Add to WaitQ. Flags:1 AToM HA [105.55.55.2, 1002]: Received 32-byte provision version 1 CF message AC HA CF: ClientId:89, Entity:0 Length:40 AToM HA [10.55.55.2, 1002]: Process chkpt msg provision [1], ver 1 AToM HA [10.55.55.2, 1002]: Reserved SSM sw/seg 8192/8194 [0x2000/0x2002] PW id 9216 [0x24 00] AC HA: Process Msg:35586. Ptr:44CBFD90. Val:0 AC HA: Sync. Event:4 CktType:4 Sw:8192[2000] Se:16385[4001] AC HA [10.55.55.2, 1002]: Remove from WaitQ. Flags:1[OK][OK]

During a switchover from the active to the backup Route Processor, the debug messages look similar to the following: %HA-5-MODE: Operating mode is hsa, configured mode is sso. AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Opr:5, St:STANDBY HO T, PSt:ACTIVE AToM HA: CID 84, Seq 715, Status RF_STATUS_OPER_REDUNDANCY_MODE_CHANGE, Op 5, State STANDB Y HOT, Peer ACTIVE AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_PRESENCE, Opr:0, St:STANDBY HOT, PSt:ACTIVE AToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_PRESENCE, Op 0, State STANDBY HOT, Peer AC TIVE AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_PEER_COMM, Opr:0, St:STANDBY HOT, PSt:DISABLED AToM HA: CID 84, Seq 715, Status RF_STATUS_PEER_COMM, Op 0, State STANDBY HOT, Peer DISABL ED %HA-2-CUTOVER_NOTICE: Cutover initiated. Cease all console activity until system restarts. %HA-2-CUTOVER_NOTICE: Do not add/remove RSPs or line cards until switchover completes. %HA-2-CUTOVER_NOTICE: Deinitializing subsystems... %OIR-6-REMCARD: Card removed from slot 4, interfaces disabled %OIR-6-REMCARD: Card removed from slot 5, interfaces disabled %OIR-6-REMCARD: Card removed from slot 9, interfaces disabled %HA-2-CUTOVER_NOTICE: Reinitializing subsystems... %HA-2-CUTOVER_NOTICE: System preparing to restart... %HA-5-NOTICE: Resuming initialization... AC HA RF: CId:83, Seq:710, Sta:RF_STATUS_REDUNDANCY_MODE_CHANGE, Opr:7, St:STANDBY HOT, PS t:DISABLED . . . %LDP-5-GR: LDP restarting gracefully. Preserving forwarding state for 250 seconds. AC HA RF: CId:83, Seq:710, Sta:RF_PROG_ACTIVE, Opr:0, St:ACTIVE, PSt:DISABLED AToM HA: CID 84, Seq 715, Event RF_PROG_ACTIVE, Op 0, State ACTIVE, Peer DISABLED AC HA: Process Msg:35588. Ptr:0. Val:0 AC HA: Switchover: Standby->Active AC HA RF: Reconciling

Related Commands

Command

Description

debug acircuit checkpoint

Enables the display of AToM attachment circuit events when AToM is configured for NSF/SSO and Graceful Restart.


DB-1563

Debug Commands debug mpls l2transport fast-reroute

debug mpls l2transport fast-reroute To enable the display of Fast Reroute debugging information, use the debug mpls l2transport fast-reroute command in privileged EXEC mode. To stop the display of these messages, use the no form of this command. debug mpls l2transport fast-reroute no debug mpls l2transport fast-reroute

Syntax Description


Defaults

Debugging of the fast reroute feature is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(25)S


12.2(33)SRA


12.2SX


Usage Guidelines

This command does not display output on platforms where AToM Fast Reroute is implemented in the forwarding code. This command does not display output for the Cisco 7500 (both RP and VIP) series routers, 7200 series routers, and Cisco 12000 series route processor. The command does display output on Cisco 10720 Internet router line cards and Cisco 12000 series line cards.

Examples

In the following example, the primary link is disabled, which causes the backup tunnel (Tu1) to become the primary path. Router# execute-on slot 3 debug mpls l2transport fast-reroute ========= Line Card (Slot 3) ========= AToM fast reroute debugging is on SLOT 3:Sep 16 17:58:56.346: AToM SMGR: Processing TFIB FRR event for 1.4.0.1 SLOT 3:Sep 16 17:58:56.346: AToM SMGR: Finished processing TFIB FRR event for 1.4.0.1 SLOT 3:Sep 16 17:58:56.346: AToM SMGR: Processing TFIB FRR event for Tunnel41 SLOT 3:Sep 16 17:58:56.346: AToM SMGR: Finished processing TFIB FRR event for Tunnel41 Sep 16 17:58:58.342: %LINK-3-UPDOWN: Interface POS0/0, changed state to down Sep 16 17:58:58.342: %OSPF-5-ADJCHG: Process 1, Nbr 1.0.0.1 on POS0/0 from FULL to DOWN, Neighbor Down: Interface down or detached Sep 16 17:58:59.342: %LINEPROTO-5-UPDOWN: Line protocol on Interface POS0/0, changed state to down


DB-1564

May 2008

Debug Commands debug mpls l2transport fast-reroute

Related Commands

Command

Description

show mpls traffic-eng fast-reroute database

Displays the contents of the Fast Reroute database.


DB-1565

Debug Commands debug mpls l2transport ipc

debug mpls l2transport ipc To display the interprocessor communication (IPC) messages exchanged between distributed platforms, such as the Cisco 12000 series router and the Cisco 7500 series routers, use the debug mpls l2transport ipc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls l2transport ipc no debug mpls l2transport ipc

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(23)S


12.2(14)S


12.2(15)T


12.2(33)SRA


12.2SX


Usage Guidelines

You can issue this command either from the line card or the route processor to log Any Transport over MPLS (AToM) updates to or from line cards. This command applies only to platforms that support distributed mode.

Examples

The following is sample output from the debug mpls l2transport ipc command: Router# debug mpls l2transport ipc AToM ipc debugging is on *May 27 23:56:04.699 UTC: *May 27 23:56:04.699 UTC: 255 *May 27 23:56:04.699 UTC: interface *May 27 23:56:04.699 UTC: slot 255 *May 27 23:56:04.699 UTC: all linecards *May 27 23:56:04.699 UTC: 255 *May 27 23:56:04.699 UTC: interface *May 27 23:56:04.699 UTC: 255

AToM SMGR: Repopulating line card 255 AToM SMGR [17.17.17.17, 1101]: Sending Imposition update to slot AToM SMGR [17.17.17.17, 1101]: Imposition being done on ingress AToM SMGR [17.17.17.17, 1101]: Sending disposition update to AToM SMGR [17.17.17.17, 1101]: Distributing disposition info to AToM SMGR [17.17.17.17, 701]: Sending Imposition update to slot AToM SMGR [17.17.17.17, 701]: Imposition being done on ingress AToM SMGR [17.17.17.17, 701]: Sending disposition update to slot


DB-1566

May 2008

Debug Commands debug mpls l2transport ipc

*May 27 23:56:04.699 all linecards *May 27 23:56:04.699 255 *May 27 23:56:04.699 interface *May 27 23:56:04.699 slot 255 *May 27 23:56:04.699 all linecards

UTC: AToM SMGR [17.17.17.17, 701]: Distributing disposition info to UTC: AToM SMGR [17.17.17.17, 1201]: Sending Imposition update to slot UTC: AToM SMGR [17.17.17.17, 1201]: Imposition being done on ingress UTC: AToM SMGR [17.17.17.17, 1201]: Sending disposition update to UTC: AToM SMGR [17.17.17.17, 1201]: Distributing disposition info to


DB-1567

Debug Commands debug mpls l2transport packet

debug mpls l2transport packet To display information about the status of Any Transport over MPLS (AToM) switched packets, use the debug mpls l2transport packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls l2transport packet {data | error} no debug mpls l2transport packet {data | error}

Syntax Description

data

Displays (in hex) the AToM switched packets for imposition and disposition. This can help validate that packets are flowing between the customer edge (CE) routers. Also, you can display the packets to check the format of the data or the data itself.

error

Displays AToM switching errors, such as the reason that packets cannot be switched. This can help identify why data is not being transported.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(23)S


12.2(14)S


12.2(15)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command sparingly because the command output can be overwhelming. For platforms that support distributed switching, the command displays output only for packets switched by the central route processor module. Packets switched autonomously by the linecards are not displayed. For example, packets switched by Versatile Interface Processors (VIPs) on the Cisco 7500 router are not displayed.

Examples

The following is sample output from the debug mpls l2transport packet commands for a PPP over MPLS configuration: Router# debug mpls l2transport packet data AToM packet data debugging is on Router# debug mpls l2transport packet error AToM packet errors debugging is on Router# show debug


DB-1568

May 2008


AToM: AToM packet data debugging is on AToM packet errors debugging is on *Mar 24 *Mar 24 are 0 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24

23:29:30.495: ATOM-PPP Switching: check features failed. 23:29:30.495: ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits 23:29:30.495: 23:29:30.495: 23:29:30.495: 23:29:30.495: 23:29:30.495: 23:29:30.495: 23:29:30.495: 23:29:30.495: 23:29:30.495: 23:29:30.495: 23:29:30.499: 23:29:31.835: 23:29:31.835: 23:29:31.835:

0F 00 88 47 00 01 00 FD C0 01 01 01 66 51 88 B4 CE 73 23 30 00 04 3C 61 49 84 D8 33 17 8C 86 69 39 98 CD E2 DE 72 35 88 09 E7 F2 73 CC 06 DC 38 49 E5 31 00 A0 E8 28 21 E4 21 69 28 D8 60 A3 62 B1 60 ATOM-L2 Switching FF 03 00 FD C0 04 FF FF FB 14 B0 00

*Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 are 0 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 are 0 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 are 0 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 are 0 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 are 0

23:29:49.423: 23:29:49.423: 23:29:49.423: 23:29:49.435: 23:29:49.435:

ATOM-L2 Switching Disposition Packet data: FF 03 C0 21 01 11 00 0F 03 05 C2 23 05 05 06 5F 23 35 D4 ATOM-PPP Switching: check features failed. ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits

23:29:49.435: 23:29:49.435: 23:29:49.435: 23:29:49.435: 23:29:49.435:

0F 00 88 C0 21 01 E5 ATOM-PPP ATOM-PPP

23:29:49.435: 23:29:49.435: 23:29:49.435: 23:29:49.443: 23:29:49.443: 23:29:49.443: 23:29:49.447: 23:29:49.447: 23:29:49.447: 23:29:49.451: 23:29:49.451:

0F 00 88 47 00 01 10 FF 00 01 61 02 00 15 00 00 C0 21 02 11 00 0F 03 05 C2 23 05 05 06 5F 23 35 D4 ATOM-L2 Switching Disposition Packet data: FF 03 C0 21 02 2F 00 0F 03 05 C2 23 05 05 06 5F CC 5F E5 ATOM-L2 Switching Disposition Packet data: FF 03 C2 23 01 D0 00 1C 10 45 59 13 1A 92 FD 93 01 A2 CF B6 FB 3A 04 46 93 63 65 32 2D 67 73 72 ATOM-PPP Switching: check features failed. ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits

23:29:49.451: 23:29:49.451: 23:29:49.451: 23:29:49.455: 23:29:49.455:

0F 00 88 C2 23 01 B4 C0 73 ATOM-PPP ATOM-PPP

23:29:49.455: 23:29:49.455: 23:29:49.455: 23:29:49.463: 23:29:49.463: 23:29:49.463: 23:29:49.463: 23:29:49.463: 23:29:49.471: 23:29:49.471:

0F 00 88 47 00 01 10 FF 00 01 61 02 00 22 00 00 C2 23 02 D0 00 1C 10 56 4A 32 5B 99 55 D5 CF 44 FC D3 D9 3F CC 8C A8 63 65 31 2D 67 73 72 ATOM-L2 Switching Disposition Packet data: FF 03 C2 23 02 F5 00 1C 10 45 84 E4 E5 DD C0 5F FD 2F 37 63 9A 3D 03 7B B9 63 65 32 2D 67 73 72 ATOM-L2 Switching Disposition Packet data: FF 03 C2 23 03 D0 00 04 ATOM-PPP Switching: check features failed. ATOM-PPP Switching (Fast) Imposition Packet data: experimental bits

10 FF 00 01 C0 4B 41 73 39 00 00 40 83 C0 00 06 F2 60 00 11 02 49 B8 E9 0C 60 61 3A 6F 33 66 83 6D 14 88 06 A6 2D 26 8A A5 80 Disposition 8A 57 FF FF

51 F4 00 00 9E 9D 1A 09 E3 45

02 00 88 06 80 0D 4D C8 21 82

00 01 03 94 00 C6 C6 CA 80 02

00 00 02 CC 50 53 71 20 C3 B6

00 02 00 A7 08 A1 01 05 31 FC

00 CC 70 23 08 DC 4C 12 E4 39

Packet data: FF FF FF FF FF FF

47 00 01 10 FF 00 01 61 02 00 15 00 00 2F 00 0F 03 05 C2 23 05 05 06 5F CC 5F Switching: check features failed. Switching (Fast) Imposition Packet data: experimental bits

47 00 01 10 FF 00 01 61 02 00 22 00 00 F5 00 1C 10 F1 98 35 3F 79 F2 1A 15 10 D7 B1 9F 2A 63 65 31 2D 67 73 72 Switching: check features failed. Switching (Fast) Imposition Packet data: experimental bits


DB-1569


*Mar 24 *Mar 24 *Mar 24 *Mar 24 are 0 *Mar 24 *Mar 24 *Mar 24

23:29:49.471: 23:29:49.471: 23:29:49.471: 23:29:49.471:

0F 00 88 C2 23 03 ATOM-PPP ATOM-PPP

47 00 01 10 FF 00 01 61 02 00 0A 00 00 F5 00 04 Switching: check features failed. Switching (Fast) Imposition Packet data: experimental bits

23:29:49.471: 0F 00 88 47 00 01 10 FF 00 01 61 02 00 10 00 00 23:29:49.471: 80 21 01 0B 00 0A 03 06 78 01 01 78 23:29:49.475: ATOM-PPP Switching: check features failed.


DB-1570

May 2008

Debug Commands debug mpls l2transport signaling

debug mpls l2transport signaling To display information about the Any Transport over MPLS (AToM) signaling protocol, use the debug mpls l2transport signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls l2transport signaling {event | message} no debug mpls l2transport signaling {event | message}

Syntax Description

event

Displays AToM signaling events.

message

Displays AToM signaling status messages.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(23)S


12.2(14)S


12.2(15)T


12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug mpls l2transport signaling command: Router# debug mpls l2transport signaling event AToM LDP event debugging is on Router# debug mpls l2transport signaling message AToM LDP message debugging is on Router# show debugging AToM: AToM LDP event debugging is on AToM LDP message debugging is on *Mar 24 23:10:55.611: *Mar 24 23:10:55.611: *Mar 24 23:10:56.063: *Mar 24 23:10:56.583: state to up

AToM LDP [9.9.9.9]: Allocate LDP instance AToM LDP [9.9.9.9]: Opening session, 1 clients %SYS-5-CONFIG_I: Configured from console by console %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/0, changed


DB-1571

Debug Commands debug mpls l2transport signaling

*Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 *Mar 24 vc type *Mar 24 vc type

23:11:00.539: 23:11:00.539: 23:11:00.539: 23:11:00.539: 23:11:00.539: 23:11:00.539: 7, cbit 1, vc 23:11:00.539: 7, cbit 1, vc

AToM LDP [9.9.9.9]: Session is up AToM LDP [9.9.9.9]: Peer address change, add 1.1.1.100 AToM LDP [9.9.9.9]: Peer address change, add 46.1.1.6 AToM LDP [9.9.9.9]: Peer address change, add 9.9.9.9 AToM LDP [9.9.9.9]: Peer address change, add 57.1.1.6 AToM LDP [9.9.9.9]: Sending label mapping msg id 50, group id 6, vc label 21, status 0, mtu 1500 AToM LDP [9.9.9.9]: Received label mapping msg, id 113 id 50, group id 6, vc label 21, status 0, mtu 1500


DB-1572

May 2008

Debug Commands debug mpls l2transport vc

debug mpls l2transport vc To display information about the status of the Any Transport over MPLS (AToM) virtual circuits (VCs), use thedebug mpls l2transport vc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls l2transport vc {event | fsm | ldp | sss | status {event | fsm}} no debug mpls l2transport vc {event | fsm | ldp | sss | status {event | fsm}}

Syntax Description

event

Displays AToM event messages about the VCs.

fsm

Displays debug information related to the finite state machine (FSM).

ldp

Displays debug information related to the Label Distribution Protocol (LDP).

sss

Displays debug information related to the subscriber service switch (SSS).

status

Displays debug information related to the status of the VCs.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.0(23)S


12.2(14)S


12.2(15)T


12.0(25)S


12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2SX


12.2(33)SRC

The command was updated to include the ldp, sss, and status keywords as part of the MPLS Pseudowire Status Signaling feature.

Usage Guidelines

You can issue this command from the line card or the route processor.

Examples

The following is sample output from the debug mpls l2transport vc commands: Router# debug mpls l2transport vc event AToM vc event debugging is on Router# debug mpls l2transport vc fsm AToM vc fsm debugging is on


DB-1573


Router# show debugging AToM: AToM vc event debugging is on AToM vc fsm debugging is on *Mar 24 23:17:24.371: AToM MGR [10.9.9.9, 50]: Event provision, state changed from idle to provisioned *Mar 24 23:17:24.371: AToM MGR [10.9.9.9, 50]: Provision vc *Mar 24 23:17:24.371: AToM SMGR [10.9.9.9, 50]: Requesting VC create, vc_handle 61A09930 *Mar 24 23:17:24.371: AToM MGR [10.9.9.9, 50]: Event local up, state changed from provisioned to local standby *Mar 24 23:17:24.371: AToM MGR [10.9.9.9, 50]: Update local vc label binding *Mar 24 23:17:24.371: AToM SMGR [10.9.9.9, 50]: sucessfully processed create request *Mar 24 23:17:24.875: %SYS-5-CONFIG_I: Configured from console by console *Mar 24 23:17:25.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial3/0, changed state to up *Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Event ldp up, state changed from local standby to local ready *Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Advertise local vc label binding *Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Event remote up, state changed from local ready to establishing *Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Remote end up *Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Event remote validated, state changed from establishing to established *Mar 24 23:17:28.567: AToM MGR [10.9.9.9, 50]: Validate vc, activating data plane *Mar 24 23:17:28.567: AToM SMGR [10.9.9.9, 50]: Processing imposition update, vc_handle 61A09930, update_action 3, remote_vc_label 21 *Mar 24 23:17:28.567: AToM SMGR [10.9.9.9, 50]: Imposition Programmed, Output Interface: PO5/0 *Mar 24 23:17:28.567: AToM SMGR [10.9.9.9, 50]: Processing disposition update, vc_handle 61A09930, update_action 3, local_vc_label 22 *Mar 24 23:17:28.571: AToM SMGR: Processing TFIB event for 10.9.9.9 *Mar 24 23:17:28.571: AToM SMGR [10.9.9.9, 50]: Imposition Programmed, Output Interface: PO5/0

The following is sample output of MPLS Pseudowire Status Signaling messages from the debug mpls l2transport vc status event and debug mpls l2transport vc status fsm commands: Router# debug mpls l2transport vc status event Router# debug mpls l2transport vc status fsm

*Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb

26 26 26 26 26 26 26 26 26 26 26 26 26 26 26

14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.543: 14:03:42.551:

AToM AToM AToM AToM AToM AToM AToM AToM AToM AToM AToM AToM AToM AToM AToM

MGR MGR MGR MGR MGR MGR MGR MGR MGR MGR MGR MGR MGR MGR MGR

[10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9, [10.9.9.9,

100]: 100]: 100]: 100]: 100]: 100]: 100]: 100]: 100]: 100]: 100]: 100]: 100]: 100]: 100]:

Receive SSS STATUS(UP) AC status UP S:Evt local up, LndRru->LnuRru S:Evt local ready, LnuRru->LruRru S:Act send label(UP) Send label(UP) Local AC : UP Dataplane: no fault Overall : no fault Remote label is ready S:Evt remote ready in LruRru S:Evt remote up in LruRru S:Evt dataplane clear fault in LruRru S:Evt dataplane clear fault in LruRru S:Evt dataplane clear fault in LruRru


DB-1574

May 2008


The status codes in the messages, such as S: and LruRru, indicate the staus of the local and remote routers. The following list translates the status codes: L—local router R—remote router r or n—ready (r) or not ready (n) u or d— up (u) or down (d) status The output also includes these values: D—Dataplane S—Local shutdown


DB-1575

Debug Commands debug mpls ldp advertisements

debug mpls ldp advertisements To display information about the advertisement of labels and interface addresses to label distribution protocol (LDP) peers, use the debug mpls ldp advertisements command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp advertisements [peer-acl acl] [prefix-acl acl] no debug mpls ldp advertisements [peer-acl acl] [prefix-acl acl]

Syntax Description

peer-acl acl

(Optional) Limits the displayed advertisements to those for LDP peers permitted by the access control list (acl).

prefix-acl acl

(Optional) Limits the displayed advertisements to those for prefixes permitted by the access control list (acl).

Defaults

Displays information about advertisements to all LDP peers for all prefixes.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX



DB-1576

May 2008


Usage Guidelines

Use this command to monitor the label and address advertisements to LDP peers. Use the peer-acl or prefix-acl options separately or together to limit the information display to specific LDP peers and/or specific prefixes.

Note

Examples

This command monitors advertisement of non-LC-ATM labels (generic labels) only. Use the debug mpls atm-ldp command to monitor LC-ATM activity.

The following shows sample output from the debug mpls ldp advertisements command: Router# debug mpls ldp advertisements tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon: tagcon:

peer peer peer peer peer peer peer peer peer peer peer peer peer peer peer peer peer peer peer

144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0 144.0.0.44:0

(pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp (pp

0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC): 0x60E105BC):

advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise advertise

130.77.0.33 133.0.0.33 34.0.0.33 103.0.0.33 35.0.0.33 38.0.0.33 34.0.0.0/8, label 3 (#2) 203.0.7.7/32, label 24 (#4) 35.0.0.0/8, label 3 (#8) 103.0.0.0/8, label 3 (#10) 138.1.0.0/16, label 26 (#14) 155.0.0.55/32, label 27 (#16) 38.0.0.0/8, label 3 (#18) 212.10.1.0/24, label 30 (#24) 59.0.0.0/8, label 32 (#28) 144.0.0.44/32, label 33 (#30) 106.0.0.0/8, label 34 (#32) 133.0.0.33/32, label 3 (#34) 45.0.0.0/8, label 39 (#36)


debug mpls ldp advertisements Field Descriptions

Field

Description

tagcon:

Identifies the source of the message as the label control subsystem.

peer a.b.c.d:e

LDP identifier of the peer to which the advertisement was targeted.

(pp 0xnnnnnnnn)

Identifier for the data structure used to represent the peer at the label distribution level. Useful for correlating debug output.

advertise X

Identifies what was advertised to the peer—either an interface address (“a.b.c.d”) or label binding (“a.b.c.d/m, label t (#n)”).

(#n)

For a label binding advertisement, the sequence number of the label information base (LIB) modification that made it necessary to advertise the label.


DB-1577


Related Commands

Command

Description

debug mpls ldp bindings

Displays information about changes to the LIB used to keep track of label bindings learned from LDP peers through LDP downstream label distribution.

show mpls ip binding

Displays specified information about label bindings learned by LDP.

show mpls ldp neighbor

Displays the status of LDP sessions.


DB-1578

May 2008

Debug Commands debug mpls ldp autoconfig

debug mpls ldp autoconfig To enable the display of events related to Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP), use the debug mpls ldp autoconfig command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp autoconfig [interface interface] no debug mpls ldp autoconfig [interface interface]

Syntax Description

interface interface

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(30)S


12.3(14)T


Examples

(Optional) Enables the display of autoconfiguration events for the specified interface.

12.2(28)SB

This command was integrated into Cisco IOS Releases 12.2(28)SB.

12.0(32)SY

This command was updated to display IS-IS information.

12.2(33)SRA


12.2SX


In the following example, the display of events related to MPLS LDP Autoconfiguration are enabled: Router# debug mpls ldp autoconfig 00:06:06: LDP-AC: OSPF area 1 [flags 0x8, handle 0x1030110]:: 00:06:06: LDP-AC: OSPF area 1 [flags 0x8, handle 0x1030110]:: enable request for Serial2/0 00:06:06: LDP-AC: OSPF area 1 [flags 0xA, handle 0x1030110]:: to Serial2/0 00:06:06: LDP-AC: OSPF area 1 [flags 0xA, handle 0x1030110]:: enable request on Serial2/0 00:06:06: LDP-AC: OSPF area 1 [flags 0x8, handle 0x1030110]:: enable request for Tunnel1 00:06:06: LDP-AC: OSPF area 1 [flags 0xA, handle 0x1030110]:: to Tunnel1 00:06:06: LDP-AC: OSPF area 1 [flags 0xA, handle 0x1030110]:: enable request on Tunnel1 00:06:06: LDP-AC: Enabling LDP on interface Serial2/0 00:06:06: LDP-AC: Enabling LDP on interface Tunnel1

Adding record Received Adding record Enqueued LDP Received Adding record Enqueued LDP


DB-1579

Debug Commands debug mpls ldp autoconfig

The following example shows events associated when an IS-IS instance, ISIS-1, is configured for autoconfiguration: Router# debug mpls ldp autoconfig 07:49:02: LDP-AC: ISIS level 1-2 [flags 0x8, 07:49:02: LDP-AC: ISIS level 1-2 [flags 0x8, for Et0/0; area/level=1 07:49:02: LDP-AC: ISIS level 1-2 [flags 0xA, 07:49:02: LDP-AC: ISIS level 1-2 [flags 0xA, request on Et0/0 07:49:02: LDP-AC: ISIS level 1-2 [flags 0x8, for Et0/0; area/level=1 07:49:02: LDP-AC: ISIS level 1-2 [flags 0x8, for Et0/0; area/level=2 07:49:02: LDP-AC: ISIS level 1-2 [flags 0x8, for Et0/0; area/level=2 07:49:02: LDP-AC: Enabling LDP autoconfig on

Note

Related Commands

handle 0x1AADBE0]:: Adding record handle 0x1AADBE0]:: Received enable request handle 0x1AADBE0]:: Adding record to Et0/0 handle 0x1AADBE0]:: Enqueued LDP enable handle 0x1AADBE0]:: Received enable request handle 0x1AADBE0]:: Received enable request handle 0x1AADBE0]:: Received enable request interface Et0/0

MPLS LDP Autoconfiguration for IS-IS is supported only in Cisco IOS Release 12.0(32)SY.

Command

Description

mpls ldp autoconfig

Enables LDP on all interfaces that belong to an OSPF area.

show mpls ldp discovery

Displays information about interfaces configured for LDP.


DB-1580

May 2008

Debug Commands debug mpls ldp backoff

debug mpls ldp backoff To display information about the label distribution protocol (LDP) backoff mechanism parameters, use the debug mpls ldp backoff command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp backoff no debug mpls ldp backoff

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(10)ST


12.1(2)T


12.1(8a)E


12.0(22)S


12.2(14)S


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command to monitor backoff parameters configured for LDP sessions.

Examples

The following shows sample output from the debug mpls ldp backoff command: Router# debug mpls ldp backoff LDP session establishment backoff debugging is on Router# Jan Jan Jan Jan Jan Jan Jan Jan

6 6 6 6 6 6 6 6

22:31:13.012: 22:31:13.824: 22:31:17.848: 22:31:18.220: 22:31:21.908: 22:31:22.980: 22:31:25.724: 22:31:26.944:

ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp:

Backoff Backoff Backoff Backoff Backoff Backoff Backoff Backoff

peer peer peer peer peer peer peer peer

ok: ok: ok: ok: ok: ok: ok: ok:

12.12.12.12:0; 12.12.12.12:1; 12.12.12.12:0; 12.12.12.12:1; 12.12.12.12:0; 12.12.12.12:1; 12.12.12.12:0; 12.12.12.12:1;

backing backing backing backing backing backing backing backing

off; off; off; off; off; off; off; off;

threshold/count threshold/count threshold/count threshold/count threshold/count threshold/count threshold/count threshold/count

8/6 8/6 8/6 8/6 8/6 8/6 8/7 8/7


DB-1581

Debug Commands debug mpls ldp backoff

Jan Jan Jan Jan Jan Jan

6 6 6 6 6 6

22:31:30.140: 22:31:31.932: 22:31:35.028: 22:31:35.788: 22:31:39.332: 22:31:39.640:

ldp: ldp: ldp: ldp: ldp: ldp:

Backoff peer ok: 12.12.12.12:0; backing off; Backoff peer ok: 12.12.12.12:1; backing off; Backoff peer ok: 12.12.12.12:0; backing off; Backoff peer ok: 12.12.12.12:1; backing off; Update backoff rec: 12.12.12.12:0, threshold Update backoff rec: 12.12.12.12:1, threshold

threshold/count threshold/count threshold/count threshold/count = 8, tbl ents 2 = 8, tbl ents 2

8/7 8/7 8/7 8/7


Related Commands

debug mpls ldp backoff Field Descriptions

Field

Description

ldp

Identifies the Label Distribution Protocol.

Backoff peer ok: a.b.c.d:n

Identifies the LDP peer for which a session is being delayed because of a failure to establish a session due to incompatible configuration.

backing off;

Indicates that a session setup attempt failed and the LSR is delaying its next attempt (that is, is backing off).

threshold/count x/y

Identifies a set threshold (x) and a count (y) that represents the time that has passed since the last attempt to set up a session with the peer. The count is incremented every 15 seconds until it reaches the threshold. When the count equals the threshold, a fresh attempt is made to set up an LDP session with the peer.

Update backoff rec

Indicates that the backoff period is over and that it is time for another attempt to set up an LDP session.

threshold = x

Indicates the backoff time of x*15 seconds, for the next LDP session attempt with the peer.

tbl ents 2

Indicates unsuccessful attempts to set up an LDP session with two different LDP peers. In this example, attempts to set up sessions with LDP peers 12.12.12.12:0 and 12.12.12.12:1 are failing.

Command

Description

mpls ldp backoff

Configures session setup delay parameters for the LDP backoff mechanism.

show mpls ldp backoff Displays information about the configured session setup backoff parameters and any potential LDP peers with which session setup attempts are being throttled.


DB-1582

May 2008

Debug Commands debug mpls ldp bindings

debug mpls ldp bindings To display information about addresses and label bindings learned from Label Distribution Protocol (LDP) peers by means of LDP downstream unsolicited label distribution, use the debug mpls ldp bindings command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp bindings [filter] [peer-acl acl] [prefix-acl acl] no debug mpls ldp bindings [filter] [peer-acl acl] [prefix-acl acl]

Syntax Description

filter

(Optional) Display information about LDP local label allocation filtering.

peer-acl acl

(Optional) Limits the displayed binding information to that learned from LDP peers permitted by the access control list (acl).

prefix-acl acl

(Optional) Limits the displayed binding information to that learned for prefixes permitted by the access control list (acl).

Command Default

Displays information about all bindings learned from all LDP peers.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

11.1CT


12.0(10)ST

This command was modified to correspond to MPLS Internet Engineering Task Force (IETF) command syntax and terminology.

12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX



DB-1583


Usage Guidelines

Note

Examples

Release

Modification

12.2(33)SRC

The filter keyword was added and the output of the command was updated to display information about LDP local label allocation filtering.

12.2(33)SB


Use this command to monitor label bindings and label switch router (LSR) addresses learned from LDP peers.

This command monitors non-LC-ATM labels (generic labels) only. Use the debug mpls atm-ldp states command to monitor LC-ATM activity.

The following is sample output from the debug mpls ldp bindings command: Router# debug mpls ldp bindings tagcon:tibent(10.34.0.0/8):created; find route tags request tagcon:tibent(10.34.0.0/8):label 3 (#2) assigned tagcon:tibent(10.0.7.7/32):created; find route tags request tagcon:tibent(10.0.7.7/32):label 24 (#4) assigned tagcon:tibent(10.0.0.44/32):created; find route tags request tagcon:tibent(10.0.0.44/32):label 33 (#30) assigned tagcon:tibent(10.106.0.0/8):created; find route tags request tagcon:tibent(10.106.0.0/8):label 34 (#32) assigned tagcon:tibent(10.0.0.33/32):created; find route tags request tagcon:tibent(10.0.0.33/32):label 3 (#34) assigned tagcon:tibent(10.45.0.0/8):created; find route tags request tagcon:tibent(10.45.0.0/8):label 39 (#36) assigned tagcon:Assign peer id; 10.0.0.44:0:id 0 tagcon:10.0.0.44:0:10.0.0.44 added to addrldp ident map tagcon:10.0.0.44:0:10.34.0.44 added to addrldp ident map tagcon:10.0.0.44:0:10.45.0.44 added to addrldp ident map tagcon:tibent(10.0.0.44/32):rem label 3 from 10.0.0.44:0 added tagcon:tibent(10.34.0.0/8):label 3 from 10.0.0.44:0 added tagcon:tibent(10.45.0.0/8):label 3 from 10.0.0.44:0 added tagcon:tibent(10.107.0.0/8):created; remote label learned tagcon:tibent(10.107.0.0/8):label 55 from 10.0.0.44:0 added tagcon:tibent(10.0.7.7/32):label 209 from 10.0.0.44:0 added tagcon:tibent(10.0.0.33/32):label 207 from 10.0.0.44:0 added


debug mpls ldp bindings Field Descriptions

Field

Description

tagcon:


tibent(network/mask)

Destination that has a label binding change.

created; reason

An LIB entry has been created for the specified destination for the indicated reason.

rem label ...

Describes a change to the label bindings for the specified destination. The change is for a label binding learned from the specified LDP peer.


DB-1584

May 2008


Table 219

debug mpls ldp bindings Field Descriptions (continued)

Field

Description

lcl label ...

Describes a change to a locally assigned (incoming) label for the specified destination.

(#n)

Sequence number of the modification to the LIB corresponding to the local label change.

a.b.c.d:n: e.f.g.h added The address e.f.g.h has been added to the set of addresses associated with to addrldp ident map LDP identifier a.b.c.d:n. The following is output from the debug mpls ldp bindings command when LDP local label allocation filtering is configured: Router# debug mpls ldp %SYS-5-CONFIG_I: Configured from console by console Router# debug mpls ldp bindings filter LDP Local Label Filtering changes debugging is on Router# configure terminal Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)# mpls ldp label Router(config-ldp-lbl)# allocate global host-routes Router(config-ldp-lbl)# LDP LLAF: Enqueued work item to walk tib for all tables LDP LLAF: Withdraw local label for 10.10.7.0 LDP LLAF: Withdraw local label for 10.10.8.0 LDP LLAF: Withdraw local label for 10.10.9.0 Router(config-ldp-lbl)# LDP LLAF: announce zero local and path labels: 10.10.7.0 LDP LLAF: announce zero local and path labels: 10.10.8.0 LDP LLAF: announce zero local and path labels: 10.10.9.0 Router(config-ldp-lbl)# Router(config-ldp-lbl)# no allocate global host-routes Router(config-ldp-lbl)# LDP LLAF: Enqueued work item to walk tib for all tables tib: get path labels: 10.1.1.1/32, tableid: 0, Et1/0, nh 10.10.7.2 LDP LLAF: 10.1.1.1 accepted, absence of filtering config tagcon: announce labels for: 10.1.1.1/32; nh 10.10.7.2, Et1/0, inlabel 17, outlabel imp-null (from 10.1.1.1:0), get path labels tib: get path labels: 10.2.2.2/32, tableid: 0, Et2/0, nh 10.10.8.2 LDP LLAF: 10.2.2.2 accepted, absence of filtering config tagcon: announce labels for: 10.2.2.2/32; nh 10.10.8.2, Et2/0, inlabel 16, outlabel imp-null (from 10.2.2.2:0), get path labels tib: get path labels: 10.10.7.0/24, tableid: 0, Et1/0, nh 0.0.0.0 LDP LLAF: 10.10.7.0 accepted, absence of filtering config tagcon: tibent(10.10.7.0/24): label 1 (#20) assigned tagcon: announce labels for: 10.10.7.0/24; nh 0.0.0.0, Et1/0, inlabel imp-null, outlabel unknown (from 0.0.0.0:0), get path labels tib: get path labels: 10.10.8.0/24, tableid: 0, Et2/0, nh 0.0.0.0 LDP LLAF: 10.10.8.0 accepted, absence of filtering config tagcon: tibent(10.10.8.0/24): label 1 (#21) assigned


DB-1585


tagcon: announce labels for: 10.10.8.0/24; nh 0.0.0.0, Et2/0, inlabel imp-null, outlabel unknown (from 0.0.0.0:0), get path labels tib: get path labels: 10.10.9.0/24, tableid: 0, Et1/0, nh 10.10.7.2 LDP LLAF: 10.10.9.0 accepted, absence of filtering config tagcon: tibent(10.10.9.0/24): label 22 (#22) assigned tagcon: announce labels for: 10.10.9.0/24; nh 10.10.7.2, Et1/0, inlabel 22, outlabel imp-null (from 10.1.1.1:0), get path labels . . . Router(config-ldp-lbl)# no mpls ldp label Router(config-ldp-lbl)# end Router# no debug mpls ldp bindings filter


debug mpls ldp bindings Field Descriptions with LDP Local Label Allocation Filtering

Field

Description

LDP LLAF

Indicates that the messages apply to LDP local label allocation filtering.

Withdraw local label for Prefix 10.10.7.0 is not in the global routing table. LDP withdraws the label 10.10.7.0 and does not assign a local labels. announce zero local and LDP does not announce local and path label for prefix 10.10.7.0. path labels: 10.10.7.0 tagcon: announce labels The label control subsystem announces the next hop (nh) and labels for the for: named prefix.

Related Commands

tib: get path labels:

LDP LIB searches for the routing and forwarding path for the named prefix.

LDP LLAF: 10.1.1.1 accepted;

LDP accepts the prefix. The prefix was found in the global table (or accepted by the prefix list, if a prefix list was named as a filter).

tibent(network/mask)

Destination that has a label binding change.

Command

Description

debug mpls atm-ldp states

Displays information about label virtual circuit (lvc) state transitions as they occur.

show mpls ldp bindings

Displays the contents of the LIB.


DB-1586

May 2008

Debug Commands debug mpls ldp checkpoint

debug mpls ldp checkpoint Note

Effective with Cisco IOS Release 12.2(33)SRA, the debug mpls ldp checkpoint command is replaced by the debug mpls vpn ha command. See the debug mpls vpn ha command for more information. To enable the display of Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) checkpoint debugging information, use the debug mpls ldp checkpoint command in privileged EXEC mode. To disable the display of MPLS LDP checkpoint debugging information, use the no form of this command. debug mpls ldp checkpoint no debug mpls ldp checkpoint

Syntax Description


Defaults

Debugging of MPLS LDP checkpointing is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


12.2(33)SRA

This command was replaced by the debug mpls vpn ha command.

12.2SX


Usage Guidelines

The following examples show sample output from the debug mpls ldp checkpoint command: Sample Output on the Active Route Processor or PRE Router# debug mpls ldp checkpoint LDP Checkpointing events and errors debugging LDP-CF: 0:3.3.3.3/32,20:: checkpointing local LDP-CF: 0:3.3.3.3/32,20:: changing checkpoint LDP-CF: 0:3.3.3.3/32,20:: changing checkpoint LDP-CF: received CF send-ack LDP-CF: 0:3.3.3.3/32,20:: changing checkpoint

is on binding state from none to add-send state from add-send to add-wait state from add-wait to added


DB-1587

Debug Commands debug mpls ldp checkpoint

Sample Output on the Backup Route Processor or PRE Router# debug mpls ldp checkpoint LDP-CF: received 16-byte CF message: client 28 [0], ver 1, type 1 LDP-CF: 0:3.3.3.3/32,20:: adding checkpointed local binding

Table 221 describes the significant fields in the sample display shown above. Table 221

Related Commands

debug mpls ldp checkpoint Command Field Descriptions

Field

Description

0:3.3.3.3/32,20::

The table ID, prefix, prefix length, and label of the checkpointed label binding.

Command

Description

show mpls ldp checkpoint

Displays information about the LDP checkpoint system on the active route processor.


DB-1588

May 2008

Debug Commands debug mpls ldp graceful-restart

debug mpls ldp graceful-restart To display debugging information for Multiprotocol (MPLS) Label Distribution Protocol (LDP) Stateful Switchover (SSO) Nonstop Forwarding (NSF) Support and Graceful Restart, use the debug mpls ldp graceful-restart command in privileged EXEC mode. To disable the display of this debugging information, use the no form of this command. debug mpls ldp graceful-restart no debug mpls ldp graceful-restart

Syntax Description


Defaults

The display of debugging information is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(29)S


12.3(14)T


12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX


Usage Guidelines

This command shows events and errors related to LDP Graceful Restart.

Examples

The following example shows sample output from the debug mpls ldp graceful-restart command. The output shows that a session was lost. The status message show the events that happen during recovery of the bindings. Router# debug mpls ldp graceful-restart LDP LDP LDP LDP LDP LDP LDP

GR: GR: GR: GR: GR: GR: GR:

GR session 10.110.0.10:0:: lost down nbr 10.110.0.10:0:: created [1 total] GR session 10.110.0.10:0:: bindings retained down nbr 10.110.0.10:0:: added all 7 addresses [7 total] down nbr 10.110.0.10:0:: state change (None -> Reconnect-Wait) down nbr 10.110.0.10:0:: reconnect timer started [120000 msecs] down nbr 10.110.0.10:0:: added to bindings task queue [1 entries]


DB-1589


LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10) LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0 LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0 LDP GR: Tagcon querying for up to 12 bindings update tasks LDP GR: down nbr 10.110.0.10:0:: requesting bindings MARK for {10.110.0.10:0, 1} LDP GR: down nbr 10.110.0.10:0:: removed from bindings task queue [0 entries] LDP GR: Requesting 1 bindings update tasks [0 left in queue] LDP GR: 2.0.0.0/8:: updating binding from 10.110.0.10:0, inst 1:: marking stale; LDP GR: 10.2.0.0/16:: updating binding from 10.110.0.10:0, inst 1:: marking stale; LDP GR: 14.0.0.14/32:: updating binding from 10.110.0.10:0, inst 1:: marking stale; LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10) LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0 LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0 LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10) LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0 LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0 LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10) LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0 LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0 LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10) LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0 LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0 LDP GR: searching for down nbr record (10.110.0.10:0, 10.2.0.10) LDP GR: search for down nbr record (10.110.0.10:0, 10.2.0.10) returned 10.110.0.10:0 LDP GR: Added FT Sess TLV (Rconn 120000, Rcov 120000) to INIT msg to 10.110.0.10:0 LDP GR: Received FT Sess TLV from 10.110.0.10:0 (fl 0x1, rs 0x0, rconn 120000, rcov 120000) LDP GR: GR session 10.110.0.10:0:: allocated instance, 2 LDP GR: GR session 10.110.0.10:0:: established LDP GR: GR session 10.110.0.10:0:: found down nbr 10.110.0.10:0 LDP GR: down nbr 10.110.0.10:0:: reconnect timer stopped LDP GR: down nbr 10.110.0.10:0:: state change (Reconnect-Wait -> Recovering) LDP GR: down nbr 10.110.0.10:0:: recovery timer started [120000 msecs] %LDP-5-GR: GR session 10.110.0.10:0 (inst. 2): starting graceful recovery %LDP-5-NBRCHG: LDP Neighbor 10.110.0.10:0 is UP LDP GR: 2.0.0.0//8:: refreshing stale binding from 10.110.0.10:0, inst 1 -> inst 2 LDP GR: 10.43.0.0//16:: refreshing stale binding from 10.110.0.10:0, inst 1 -> inst 2 LDP GR: down nbr 10.110.0.10:0:: recovery timer expired %LDP-5-GR: GR session 10.110.0.10:0 (inst. 2): completed graceful recovery LDP GR: down nbr 10.110.0.10:0:: destroying record [0 left] LDP GR: down nbr 10.110.0.10:0:: state change (Recovering -> Delete-Wait) LDP GR: down nbr 10.110.0.10:0:: added to bindings task queue [1 entries] LDP GR: Tagcon querying for up to 12 bindings update tasks LDP GR: down nbr 10.110.0.10:0:: requesting bindings DEL for {10.110.0.10:0, 1} LDP GR: down nbr 10.110.0.10:0:: removed from bindings task queue [0 entries] LDP GR: Requesting 1 bindings update tasks [0 left in queue] LDP GR: GR session 10.110.0.10:0:: released instance, 1

The debug output is formatted in three general ways. •

LDP GR: GR session 10.110.0.10:0:: found down nbr 10.110.0.10:0

•

down nbr 10.110.0.10:0:: removed from bindings task queue [0 entries]

•

LDP GR: 2.0.0.0/8:: updating binding from 10.110.0.10:0, inst 1:: marking stale;


DB-1590

May 2008


Table 222 describes the fields for the debug command output. :

Table 222

Related Commands

debug mpls ldp graceful-restart Command Field Descriptions

Field

Description

LDP GR

Identifies LDP Graceful Restart application

GR session 10.110.0.10:0

ID of the LDP session that is enabled for Graceful Restart.

found down nbr 10.110.0.10:0

Describes the event that is happening to that LDP session.

down nbr 10.110.0.10:0::

Identifies the Down Neighbor record, which logs the state of a recently lost Graceful Restart session.

removed from bindings task queue [0 entries]

Describes the event that is happening to the recently lost Graceful Restart session.

2.0.0.0/8::

Identifies the Forwarding Equivalence Class (FEC) associated with the remote label binding being modified. The FEC identifies the Label Information Base (LIB) entry.

updating binding

Lists the operation being performed on the remote label binding.

10.110.0.10:0, inst 1:: marking stale;

Identifies the LDP session during which the remote label binding was learned.

Command

Description

show mpls ldp graceful-restart

Displays a summary of the LDP Graceful Restart status.


DB-1591

Debug Commands debug mpls ldp igp sync

debug mpls ldp igp sync To enable the display of events related to the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP)-Interior Gateway Protocol (IGP) Synchronization feature, use the debug mpls ldp igp sync command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp igp sync [interface interface] [peer acl] no debug mpls ldp igp sync [interface interface] [peer acl]

Syntax Description

interface interface

(Optional) Enables the display of LDP-IGP Synchronization events for the specified interface.

peer acl

(Optional) Enables the display of LDP-IGP Synchronization events for the specified peer access control list (ACL).

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(30)S


Examples

12.3(14)T


12.0(32)S

The command output was modified to display events related to the delay timer on interfaces running Open Shortest Path First (OSPF) processes, if the delay timer is configured.

12.0(32)SY

The command output was modified to display events related to synchronization on interfaces running Intermediate System-to-Intermediate System (IS-IS) processes.

12.4(12)


12.2(33)SB


The following example shows events related to MPLS LDP-IGP Synchronization on interfaces running OSPF: Router# debug mpls ldp igp sync LDP-SYNC: infinite) LDP-SYNC: LDP-SYNC:

Et0/0, OSPF 1: notify status (required, not achieved, no delay, holddown internal status (achieved, timer running) E1/0, 10.0.0.1: Adj being deleted, sync_achieved goes down E1/0, OSPF 1: notify status (required, not achieved, delay, holddown infinite)

LDP-SYNC: Et0/0: Session already up and interface address advertised, sync_achieved comes up. LDP-SYNC: Et0/0, OSPF 1: notify status (required, achieved, no delay, holddown infinite)

The following example shows events associated when an IS-IS instance, ISIS-1, is configured for Synchronization: Router# debug mpls ldp igp sync


DB-1592

May 2008


07:59:27: LDP-SYNC: Et0/0, OSPF 1: notify status (required, not achieved, no delay, holddown infinite) internal status (achieved, timer running) 07:59:27: LDP-SYNC: Enqueue request req_type 0 IGP ISIS ISIS-1 interface none. 07:59:27: LDP-SYNC: ISIS ISIS-1: SYNC enabled, added to global tree, informed IGP. 07:59:27: LDP-SYNC: Enqueue request req_type 3 IGP ISIS ISIS-1 interface Et0/0. 07:59:27: LDP-SYNC: Enqueue request req_type 3 IGP ISIS ISIS-1 interface Et0/0. 07:59:27: LDP-SYNC: Et0/0, ISIS ISIS-1: Added to per-interface IGP list. 07:59:27: LDP-SYNC: Et0/0: Enabled for SYNC by IGP 07:59:27: LDP-SYNC: Et0/0, ISIS ISIS-1: notify status (required, not achieved, delay, holddown infinite) 07:59:27: LDP-SYNC: Et0/0, ISIS ISIS-1: Ignore IGP enable-interface request: already enabled.


debug mpls ldp igp sync Field Descriptions

Field

Description

sync_achieved

The first line of the output for an interface shows the status of the MPLS LDP-IGP Synchronization in relation to the status of the interface.

notify status

The notify status shows the following MPLS LDP-IGP Synchronization information for each interface:

internal status

•

If LDP-IGP Synchronization is required.

•

If LDP-IGP Synchronization has been achieved.

•

If the IGP should wait for LDP Synchronization to be achieved.

•

The length of time the IGP should wait for the LDP Synchronization to be achieved.

The internal status displays LDP internal synchronization status and the state of the timer. The internal status can be achieved or not achieved. The timer state can be running or not running.

The following example shows events associated with MPLS LDP-IGP Synchronization on interfaces running OSPF when you have configured a delay timer: Router# debug mpls ldp igp sync *Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: notify status (required, not achieved, no delay, holddown infinite) internal status (achieved, timer running) ! *Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Sync disabled by IGP. Stop delay timer *Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: TAGSW subblock destroyed. Stop delay timer *Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Sync down. Stop delay timer *Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Delay notifying IGP of sync achieved for 60 seconds *Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Delay timer expired, notify IGP of sync achieved *Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Delay timer expired but sync is no longer required won't notify IGP of sync achieved *Jan 3 04:38:49.571: LDP-SYNC: Et0/0, OSPF 1: Delay timer expired but sync is down won't notify IGP of sync achieved


DB-1593


Related Commands

Command

Description

mpls ldp sync

Enables LDP-IGP Synchronization on all interfaces that belong to an OSPF process or IS-IS process.

show mpls ldp igp sync

Displays information about interfaces configured for LDP-IGP Synchronization.


DB-1594

May 2008

Debug Commands debug mpls ldp messages

debug mpls ldp messages To display specific information (such as message type, source, and destination) regarding label distribution protocol (LDP) messages sent to and received from LDP peers, use the debug mpls ldp messages command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp messages {sent | received} [all] [peer-acl acl] no debug mpls ldp messages {sent | received} [all] [peer-acl acl]

Syntax Description

sent

Displays LDP messages sent to LDP peers permitted by the access control list (acl).

received

Displays LDP messages received from LDP peers permitted by the access control list (acl).

all

(Optional) Displays all LDP messages sent to and received from LDP peers (including periodic KeepAlive messages) permitted by the access control list (acl).

peer-acl acl

(Optional) Limits the messages displayed for LDP peers in accordance with the access control list (acl).

Defaults

All messages sent (for sent keyword) or received (for received keyword) are displayed except for periodic KeepAlive messages.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S



DB-1595


Release

Modification

12.2(33)SRA


12.2SX


Usage Guidelines

LDP requires periodic transmission of KeepAlive messages. If you do not specify the all option, periodic KeepAlive messages are not displayed.

Examples

The following shows sample output from the debug mpls ldp messages received command: Router# debug mpls ldp messages received Router# debug mpls ldp messages sent ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp: ldp:

Rcvd Sent Sent Rcvd Sent Sent Sent Sent Rcvd Rcvd Rcvd Rcvd Rcvd Rcvd Rcvd Rcvd Rcvd

init msg from 144.0.0.44 (pp 0x0) init msg to 144.0.0.44:0 (pp 0x0) keepalive msg to 144.0.0.44:0 (pp 0x0) keepalive msg from 144.0.0.44:0 (pp 0x0) address msg to 144.0.0.44:0 (pp 0x610F00E0) label mapping msg to 144.0.0.44:0 (pp 0x610F00E0) label mapping msg to 144.0.0.44:0 (pp 0x610F00E0) label mapping msg to 144.0.0.44:0 (pp 0x610F00E0) address msg from 144.0.0.44:0 (pp 0x610F00E0) label mapping msg from 144.0.0.44:0 (pp 0x610F00E0) label mapping msg from 144.0.0.44:0 (pp 0x610F00E0) label mapping msg from 144.0.0.44:0 (pp 0x610F00E0) label mapping msg from 144.0.0.44:0 (pp 0x610F00E0) label mapping msg from 144.0.0.44:0 (pp 0x610F00E0) label mapping msg from 144.0.0.44:0 (pp 0x610F00E0) label mapping msg from 144.0.0.44:0 (pp 0x610F00E0) label mapping msg from 144.0.0.44:0 (pp 0x610F00E0)


debug mpls ldp messages received Field Descriptions

Field

Description

ldp:

Identifies the source of the displayed information as LDP.

Rcvd xxx msg

Type of message received or sent.

Sent xxx msg from a.b.c.d

Host that sent the message. Used in the early stages of the opening of an LDP session, when the LDP identifier is not yet known.

from a.b.c.d:e

LDP identifier of the peer that sent the message or to which the message was sent.

to a.b.c.d:e (pp 0xnnnnnnnn)

Identifies the data structure used to represent the peer at the label distribution level. Useful for correlating debug output.


DB-1596

May 2008


Related Commands

Command

Description

debug mpls ldp session Displays the contents of LDP messages sent to and received from LDP peers. io


DB-1597

Debug Commands debug mpls ldp peer state-machine

debug mpls ldp peer state-machine To display information about state transitions for label distribution protocol (LDP) sessions, use the debug mpls ldp peer state-machine command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp peer state-machine no debug mpls ldp peer state-machine

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


Usage Guidelines

12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX


LDP manages peer sessions by means of two coupled state machines: •

A low-level state machine that deals with session establishment and shutdown

•

A high-level state machine that deals with setting up and shutting down label advertisement


DB-1598

May 2008

Debug Commands debug mpls ldp peer state-machine

Use the debug mpls ldp session state-machine command to monitor the lower-level session state machine. Use the debug mpls ldp peer state-machine command to monitor the higher-level session state machine.

Examples

The following shows sample output from the debug mpls ldp peer state-machine command: Router# debug mpls ldp peer state-machine tagcon: start session TCP timers for 144.0.0.44:0 (pp 0x610EEC84) tagcon: Enqueue peer up work for 144.0.0.44:0 (pp 0x610EEC84) tagcon: peer 144.0.0.44:0 (pp 0x610EEC84): Event unsol open unsol op pdg -> estab tagcon: Send initial advertisements to peer 144.0.0.44:0 tagcon: Initial address advertisement to peer 144.0.0.44:0 tagcon: Initial label advertisement to peer 144.0.0.44:0 ... tagcon: peer 144.0.0.44:0 (pp 0x610EEC84): Event down estab -> destroyed tagcon: peer 144.0.0.44:0 (pp 0x610EEC84): Event cleanup done destroyed -> non-ex


Related Commands

debug mpls ldp peer state-machine Field Descriptions

Field

Description

tagcon:


a.b.c.d:e

LDP identifier of the peer for the session with the state change.

(pp 0xnnnnnnnn)

Address of the data structure used to represent the peer at the label distribution level. This address is useful for correlating debug output.

Event E

Event causing the state change.

s1 -> s2

State of the LDP session has changed from state s1 to state s2.

Command

Description

debug mpls ldp session Displays information about LDP messages sent to or received from LDP io peers. show mpls ldp neighbor

Displays the status of LDP sessions.


DB-1599

Debug Commands debug mpls ldp prev-label

debug mpls ldp prev-label To display debug information when a local label binding associated with a prefix is withdrawn and freed, use the debug mpls ldp prev-label command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls ldp prev-label [prefix-acl acl [peer-acl acl] no debug mpls lad prev-label [prefix-acl acl [peer-acl acl]

Syntax Description

prefix-acl acl

(Optional) Limits the displayed binding information to that allocated for prefixes permitted by a prefix access control list (ACL).

peer-acl acl

(Optional) Limits the displayed binding withdraw information to those Label Distribution Protocol (LDP) peers permitted by a peer ACL.

Command Default

Debugging of previous local label binding changes is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(21)ST


12.2(8)T


12.2(14)S


12.2SX


Usage Guidelines

Use this command to monitor LDP information when a local label binding associated with a prefix is withdrawn and freed. LDP withdraws a previously advertised label before advertising a new label. If you enter the debug mpls ldp prev-label command without an optional keyword and argument, the command displays output for all previous label binding changes. Use the prefix-acl acl or peer-acl acl keywords and arguments to limit the output to prefixes defined by the respective ACLs.

Examples

The following is sample output from the debug mpls ldp prev-label command: Router# debug mpls ldp prev-label tagcon: tagcon: tagcon: tagcon: tagcon:

Changing state to WITHDRAWN for prefix=10.0.1.1, label31 Creating prev_lbl_info for prefix=10.0.1.1, label31 noroute hold timer expired for 10.0.1.1/255.255.255.255, tag withdrawn, seqno 47 tibent(10.0.1.1/32): label 32 from 10.0.0.2:0 removed Deleting prev label info for prefix = 10.0.1.1, tag = 31


DB-1600

May 2008

Debug Commands debug mpls ldp prev-label


Related Commands

debug mpls ldp prev-label Field Descriptions

Field

Description

tagcon:


Changing state to WITHDRAWN

Describes the label binding change; in this case, the label is to be withdrawn.

for prefix=10.0.1.1

The prefix (10.0.1.1) from which the local label binding is to be withdrawn and freed.

label31

The local label binding (31) that is to be withdrawn from the prefix.

tibent(10.0.1.1/32)

The hostname, network, and mask for the destination that has a label binding change.

Command

Description

debug mpls ldp bindings

Displays information about addresses and label bindings learned from LDP peers by means of LDP downstream unsolicited label distribution.


DB-1601

Debug Commands debug mpls ldp session io

debug mpls ldp session io To display the contents of label distribution protocol (LDP) messages sent to and received from LDP peers, use the debug mpls ldp session io command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp session io [all] [peer-acl acl] no debug mpls ldp session io [all] [peer-acl acl]

Syntax Description

all

(Optional) Includes the contents of periodic KeepAlive messages in the displayed message output to LDP peers.

peer-acl acl

(Optional) Limits the displayed message output to those LDP peers permitted by the access control list (acl).

Defaults

Displays the contents of LDP messages sent and received except for periodic KeepAlive messages.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX


Usage Guidelines

Displays the contents of all messages sent and received except for periodic KeepAlive messages.


DB-1602

May 2008


Examples

The following shows sample output from the debug mpls ldp session io command: Router# debug mpls ldp session io all ldp: Rcvd init msg from 144.0.0.44 (pp 0x0) ldp: LDP init msg: PDU hdr: LDP Id: 144.0.0.44:0; Msg Contents: 0x00 0x01 0x00 0x20 0x90 0x00 0x00 0x2C 0x00 0x00 0x02 0x00 0x00 0x16 0x00 0x10 0x21 0x05 0x00 0x00 0x0E 0x00 0x01 0x00 0xB4 0x00 0x00 0x00 0x00 0x85 0x00 0x21 0x00 0x00 ldp: Sent init msg to 144.0.0.44:0 (pp 0x0) ldp: LDP init msg: PDU hdr: LDP Id: 133.0.0.33:0; Msg Contents: 0x00 0x01 0x00 0x20 0x85 0x00 0x00 0x21 0x00 0x00 0x02 0x00 0x00 0x16 0x00 0x06 0x32 0x05 0x00 0x00 0x0E 0x00 0x01 0x00 0xB4 0x00 0x00 0x00 0x00 0x90 0x00 0x2C 0x00 0x00 ldp: Sent keepalive msg to 144.0.0.44:0 (pp 0x0) ldp: LDP keepalive msg: PDU hdr: LDP Id: 133.0.0.33:0; Msg Contents: 0x00 0x01 0x00 0x0E 0x85 0x00 0x00 0x21 0x00 0x00 0x02 0x01 0x00 0x04 0x00 0x06 0x33 ldp: Rcvd keepalive msg from 144.0.0.44:0 (pp 0x0) ldp: LDP keepalive msg: PDU hdr: LDP Id: 144.0.0.44:0; Msg Contents: 0x00 0x01 0x00 0x0E 0x90 0x00 0x00 0x2C 0x00 0x00 0x02 0x01 0x00 0x04 0x00 0x10 0x22 ldp: Sent address msg to 144.0.0.44:0 (pp 0x610ECDD0) ldp: LDP address msg: PDU hdr: LDP Id: 133.0.0.33:0; Msg Contents: 0x00 0x01 0x00 0x34 0x85 0x00 0x00 0x21 0x00 0x00 0x03 0x00 0x00 0x2A 0x00 0x06 0x34 0x01 0x01 0x00 0x22 0x00 0x01 0x02 0x00 0x00 0xA3 0x82 0x42 0x00 0x82 0x4D 0x00 0x21 0x85 0x00 0x00 0x21 0x22 0x00 0x00 0x21 0x67 0x00 0x00 0x23 0x00 0x00 0x21 0x26 0x00 0x00 0x21 ldp: Sent label mapping msg to 144.0.0.44:0 (pp 0x610ECDD0) ldp: LDP label mapping msg: PDU hdr: LDP Id: 133.0.0.33:0; Msg Contents: 0x00 0x01 0x00 0x22 0x85 0x00 0x00 0x21 0x00 0x00 0x04 0x00 0x00 0x18 0x00 0x06 0x36 0x01 0x00 0x00 0x08 0x02 0x00 0x01 0x20 0xCB 0x00 0x07 0x07 0x02 0x00 0x04 0x00 0x00 0x00 0x18 ldp: Rcvd address msg from 144.0.0.44:0 (pp 0x610ECDD0) ldp: LDP address msg: PDU hdr: LDP Id: 144.0.0.44:0; Msg Contents: 0x00 0x01 0x00 0x24 0x90 0x00 0x00 0x2C 0x00 0x00 0x03 0x00 0x00 0x1A 0x00 0x10 0x23 0x01 0x01 0x00 0x12 0x00 0x01 0x90 0x00 0x00 0x2C 0x02 0x00 0x00 0x22 0x00 0x00 0x2C 0x2D 0x00 0x00 0x2C ldp: Rcvd label mapping msg from 144.0.0.44:0 (pp 0x610ECDD0) ldp: LDP label mapping msg: PDU hdr: LDP Id: 144.0.0.44:0; Msg Contents: 0x00 0x01 0x00 0x22 0x90 0x00 0x00 0x2C 0x00 0x00 0x04 0x00 0x00 0x18 0x00 0x10 0x24 0x01 0x00 0x00 0x08 0x02 0x00 0x01 0x20 0x90 0x00 0x00 0x2C 0x02 0x00 0x04 0x00 0x00 0x00 0x03

0x00 0x00

0x00 0x00

0x00

0x00

0x00 0x21 0x21

0x00 0x00

0x00 0xA4

0x00 0x00


debug mpls ldp session io Field Descriptions

Field

Description

ldp:

Identifies the source of the message as LDP.

Rcvd xxx msg

Indicates that a message of the specified type has been received.

from a.b.c.d

Host to which the message has been sent. Used in the early stages of the opening of an LDP session when the LDP identifier is not yet known.

Sent xxx msg

Indicates that a message of the specified type has been sent.

to a.b.c.d

Host to which the message has been sent. Used in the early stages of the opening of an LDP session when the LDP identifier is not yet known.

to a.b.c.d:e

LDP identifier of the peer to which the message has been sent.


DB-1603


Table 227

Related Commands

debug mpls ldp session io Field Descriptions (continued)

Field

Description

(pp 0xnnnnnnnn)

Identifies the data structure used to represent the peer at the label distribution level. Useful for correlating debug output.

LDP xxx msg

Type of message that has been sent.

PDU hdr: LDP Id: a.b.c.d:e

LDP identifier of the sender included in the LDP protocol data unit (PDU) header.

Msg contents: 0xnn ... 0xnn

Contents of the message represented as a sequence of bytes.

Command

Description

debug mpls ldp session Displays information about state transitions for LDP sessions. state-machine


DB-1604

May 2008

Debug Commands debug mpls ldp session protection

debug mpls ldp session protection To enable the display of events related to MPLS LDP Session Protection, use the debug mpls ldp session protection command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp session protection [peer-acl acl] no debug mpls ldp session protection [peer-acl acl]

Syntax Description

peer-acl acl

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(30)S


12.3(14)T


12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX


Examples

(Optional) Enables the display of events for the peers whose router IDs are listed in the access control list.

In the following example, the display of events related to MPLS LDP-IGP Synchronization are enabled: Router# debug mpls ldp session protection

Related Commands

Command

Description

clear mpls ldp neighbor

Forcibly resets an LDP session.


Displays the contents of the LDP.


DB-1605

Debug Commands debug mpls ldp session state-machine

debug mpls ldp session state-machine To display information about state transitions for label distribution protocol (LDP) sessions, use the debug mpls ldp session state-machine command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp session state-machine [peer-acl acl] no debug mpls ldp session state-machine [peer-acl acl]

Syntax Description

peer-acl acl

Defaults


Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

(Optional) Limits the displayed information to that for LDP peers permitted by the access control list (acl).

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX


LDP manages peer sessions by means of two coupled-state machines: •

A low-level state machine that deals with session establishment and shutdown

•

A high-level state machine that deals with setting up and shutting down label advertisement


DB-1606

May 2008

Debug Commands debug mpls ldp session state-machine

Use the debug mpls ldp session state-machine command to monitor the lower-level session state machine. Use the debug mpls ldp peer state-machine command to monitor the higher-level session state machine.

Examples

The following shows sample output from the debug mpls ldp session state-machine command: Router# debug mpls ldp session state-machine ldp: ptcl_adj:144.0.0.44(0x610EED30): Non-existent -> Role pasv ldp: create ptcl_adj: tp = 0x610EED30, ipaddr = 144.0.0.44 ldp: ptcl_adj:144.0.0.44(0x610EED30): Event: Xport opened; Role pasv -> Role pasv ldp: ptcl_adj:34.0.0.44(0x610EED30): Event: Rcv Init; Role pasv -> Init rcvd pasv ldp: ptcl_adj:34.0.0.44(0x610EED30): Event: Rcv KA; Init rcvd pasv -> Oper ldp: ptcl_adj:unknown(0x610EED30): Event: Xport closed; Oper -> Non-existent


Related Commands

debug mpls ldp session state-machine Field Descriptions

Field

Description

ldp:


ptcl_adj:a.b.c.d

Identifies the network address of the LDP peer.

(0xnnnnnnnn)

Identifies the data structure used to represent the peer at the protocol level. Useful for correlating debug output.

Event: E

Event that caused the state transition.

s1 -> s2

State of the LDP session has changed from state s1 to state s2.

Command

Description

debug mpls ldp peer state-machine

Displays information about state transitions for LDP sessions.


DB-1607

Debug Commands debug mpls ldp targeted-neighbors

debug mpls ldp targeted-neighbors To display information about the target neighbor mechanism, use the debug mpls ldp targeted-neighbors command in privileged EXEC mode. This mechanism establishes label distribution protocol (LDP) adjacencies to peers that are not directly adjacent, such as peers at either end of a tunnel. To disable this feature, use the no form of this command. debug mpls ldp targeted-neighbors no debug mpls ldp targeted-neighbors

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


Usage Guidelines

12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX


Platforms that are not directly connected may engage in LDP label distribution (for example, to support two-level labeling across an LSP tunnel).


DB-1608

May 2008

Debug Commands debug mpls ldp targeted-neighbors

An LDP session between nondirectly connected label switch routers (LSRs) is called a targeted session and is supported by LDP extended discovery which uses targeted Hello messages sent to specific IP addresses. An LSR (Router 1) attempting to initiate an LDP targeted session with another LSR (Router 2) sends targeted Hello messages sent to a specific IP address of Router 2. If the configuration of Router 2 permits it to respond to targeted Hello messages from Router 1, it does so, and the LDP session can be established. In this situation, Router 1 is said to be an active LSR for the targeted session because it initiated the targeted Hello messages; Router 2 is said to be a passive LSR for the session because it responded to them. As with LDP sessions between two directly connected LSRs, it is possible for a targeted session to be the result of multiple discovery activities which are targeted to different IP addresses for the same LSR. In addition, it is possible for both LSRs in a targeted session to be active and for both to be passive. The debug messages enabled by debug mpls ldp targeted-neighbors report activity relating to targeted sessions.

Examples

The following shows sample output from the debug mpls ldp targeted-neighbors command: Router# debug mpls ldp targeted-neighbors ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr: ldp-trgtnbr:

144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44 144.0.0.44

Req active allocated Set peer start; flags 0x0 Defer peer cleanup; cleancnt 1 Set peer finished; flags 0xF ref count incremented to 1 Release active; ref count decremented to 0 Clear peer start; flags 0xF Undefer cleanup start; clearcnt 0, flags 0xC Undefer cleanup finish; clearcnt 0, flags 0x8 Clear peer finished; flags 0x8 freed


Related Commands

debug mpls ldp targeted-neighbors Field Descriptions

Field

Description

ldp-trgtnbr:

Identifies this as an LDP targeted neighbor debug statement.

144.0.0.44

IP address for the targeted neighbor.

Command

Description


Displays the status of LDP protocol sessions.


DB-1609

Debug Commands debug mpls ldp transport connections

debug mpls ldp transport connections To display information about the Transmission Control Protocol (TCP) connections used to support label distribution protocol (LDP) sessions, use the debug mpls ldp transport connections command in privileged EXEC mode. To disable this feature, use the no form of this command. debug mpls ldp transport connections [peer-acl acl] [interface interface] no debug mpls ldp transport connections [peer-acl acl] [interface interface]

Syntax Description

peer-acl acl


interface interface

(Optional) Limits the displayed information to that for the specified interface.

Defaults

Display information about LDP TCP connection activity for all peers and all interfaces.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX



DB-1610

May 2008

Debug Commands debug mpls ldp transport connections

Usage Guidelines

Use this command to monitor LDP activity relating to the establishment of the transport (TCP) connection for LDP sessions. When two devices establish a TCP connection for an LDP session, the device with the larger transport address plays an active role and the other plays a passive role. The active device attempts to establish a TCP connection to the well-known LDP port at the passive device. The passive device waits for the connection to the well-known port to be established.

Examples

The following shows sample output from the debug mpls ldp transport connections command: Router# debug mpls ldp transport connections Debug output at active peer: ldp: ldp: ldp: ldp: ldp:

Opening listen port 646 for 144.0.0.44, 34.0.0.44 Open LDP listen TCB 0x60E105BC; lport = 646; fhost = 144.0.0.44 Add listen TCB to list; tcb 0x60E105BC; addr 144.0.0.44 Incoming ldp conn 133.0.0.33:646 144.0.0.44:11042 create ptcl_adj: tp = 0x610ECD64, ipaddr = 144.0.0.44

Debug output at passive peer: ldp: Opening ldp conn; adj 0x60BAC33C, 144.0.0.44 133.0.0.33 ldp: ldp conn is up; adj 0x60BAC33C, 144.0.0.44:11042 133.0.0.33:646


Related Commands

debug mpls ldp transport connections Field Descriptions

Field

Description

ldp:


adj 0xnnnnnnnn

Identifies the data structure used to represent the peer at the transport level. Useful for correlating debug output.

a.b.c.d -> p.q.r.s

Indicates a TCP connection between a.b.c.d and p.q.r.s.

a.b.c.d:x -> p.q.r.s:y

Indicates a TCP connection between a.b.c.d, port x and p.q.r.s, port y.

Command

Description

debug mpls ldp transport events

Prints information about the events related to the LDP peer discovery mechanism.


DB-1611

Debug Commands debug mpls ldp transport events

debug mpls ldp transport events To display information about events related to the label distribution protocol (LDP) peer discovery mechanism, use the debug mpls ldp transport events command in privileged EXEC mode. This mechanism is used to determine the devices with which you wish to establish LDP sessions. To disable this feature, use the no form of this command. debug mpls ldp transport events [peer-acl acl] [interface] no debug mpls ldp transport events [peer-acl acl] [interface]

Syntax Description

peer-acl acl


interface

(Optional) Limits the displayed information to that for the specified interface.

Defaults

Displays information about LDP discovery activity for all peers and all interfaces.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.0(10)ST


12.0(14)ST


12.1(2)T


12.1(8a)E


12.2(2)T


12.2(4)T


12.2(8)T


12.0(21)ST


12.0(22)S


12.0(23)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2SX



DB-1612

May 2008


Usage Guidelines

Use this command to monitor LDP discovery activity. This command might generate a great deal of output. Use the peer-acl option or interface option, or both, to limit the output to peers or interfaces of interest.

Note

Examples

The command includes all of the output generated by the debug mpls ldp transport connection command.

The following shows sample output from the debug mpls ldp transport events command: Router# debug mpls ldp transport events ldp: enabling ldp on Ethernet1/1/1 ldp: Set intf id: intf 0x611D684C, Ethernet1/1/1, not lc-atm, intf_id 0 ldp: Set intf id: intf 0x617C5638, ATM0/0.2, not lc-atm, intf_id 0 ldp: Send ldp hello; ATM3/0.1, src/dst 8.1.1.1/224.0.0.2, inst_id 1, tcatm ldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt ldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0 ldp: Rcvd ldp hello; Ethernet1/1/1, from 10.105.0.9 (7.1.1.1:0), intf_id 0, ldp: ldp Hello from 10.105.0.9 (7.1.1.1:0) to 224.0.0.2, opt 0xC ldp: New adj 0x617C5EBC from 10.105.0.9 (7.1.1.1:0), Ethernet1/1/1 ldp: Opening ldp conn; adj 0x617C5EBC, 8.1.1.1 7.1.1.1 ldp: ldp conn is up; adj 0x617C5EBC, 8.1.1.1:11013 7.1.1.1:646 ldp: Send ldp hello; ATM3/0.1, src/dst 8.1.1.1/224.0.0.2, inst_id 1, tcatm ldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt ldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0 ldp: Rcvd ldp hello; Ethernet1/1/1, from 10.105.0.9 (7.1.1.1:0), intf_id 0, ... ldp: Send ldp hello; Ethernet1/1/1, src/dst 138.1.0.88/224.0.0.2, inst_id 0 ldp: Send ldp hello; ATM3/0.1, src/dst 8.1no tag ip .0.2, inst_id 1, tcatm ldp: disabling ldp on Ethernet1/1/1 ldp: Hold timer expired for adj 0x617C5EBC, will close conn ldp: Closing ldp conn 8.1.1.1:11013 7.1.1.1:646, adj 0x617C5EBC ldp: Adjacency 0x617C5EBC, 10.105.0.9 timed out ldp: Adj 0x617C5EBC; state set to closed ldp: Rcvd ldp hello; ATM3/0.1, from 203.0.7.7 (203.0.7.7:2), intf_id 1, opt ldp: Ignore Hello from 10.105.0.9, Ethernet1/1/1; no intf

0x8, tcatm opt 0xC

0x8, tcatm opt 0xC

0x8, tcatm


debug mpls ldp transport events Field Descriptions

Field

Description

ldp:


adj 0xnnnnnnnn

Identifies the data structure used to represent the peer at the transport level. Useful for correlating debug output.

a.b.c.d (p.q.r.s:n)

Network address and LDP identifier of the peer.


DB-1613


Table 231

Related Commands

debug mpls ldp transport events Field Descriptions

Field

Description

intf_id

Interface identifier (non-zero for LC-ATM interfaces; 0 otherwise).

opt 0xn

Bits that describe options in the LDP discovery Hello packet: •

0x1—Targeted Hello option

•

0x2—Send targeted Hello option

•

0x4—Transport address option

•

0x8—LDP Hello message (as opposed to TDP Hello message)

Command

Description

debug mpls ldp transport connections

Displays information about the TCP connections used to support LDP sessions.

show mpls ldp discovery

Displays the status of the LDP discovery process.


DB-1614

May 2008

Debug Commands debug mpls lfib cef

debug mpls lfib cef To print detailed information about label rewrites being created, resolved, and deactivated as Cisco Express Forwarding (CEF) routes are added, changed, or removed, use the debug mpls lfib cef command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls lfib cef no debug mpls lfib cef

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.1(3)T

This command was modified to reflect new MPLS IETF terminology and CLI syntax.

12.2(33)SRA


12.2SX


Usage Guidelines

Several lines of output are produced for each route placed into the label-forwarding information base (LFIB). If your router has thousands of labeled routes, be careful about issuing this command. When label switching is first enabled, each of these routes is placed into the LFIB, and several lines of output are displayed for each route.

Examples

The following is sample output from the debug mpls lfib cef command: Router# debug mpls lfib cef Cisco Express Forwarding related TFIB services debugging is on tagcon: tc_ip_rtlookup fail on 10.0.0.0/8:subnet_lookup failed TFIB: route tag chg 10.7.0.7/32,idx=1,inc=Withdrn,outg=Withdrn,enabled=0x2 TFIB: fib complete delete: prefix=10.7.0.7/32,inc tag=26,delete_info=1 TFIB: deactivate tag rew for 10.7.0.7/32,index=0 TFIB: set fib rew: pfx 10.7.0.7/32,index=0,add=0,tag_rew->adj=Ethernet2/3 TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parent TFIB: fib scanner start:needed:1,unres:0,mac:0,loadinfo:0 TFIB: resolve tag rew,prefix=10.7.0.7/32,no tag_info,no parent TFIB: fib upd loadinf 10.100.100.100/32,tag=Tun_hd,fib no loadin,tfib no loadin


DB-1615


TFIB: fib check cleanup for 10.100.100.100/32,index=0,return_value=0 TFIB: fib_scanner_end TFIB: create dynamic entry for 10.11.0.11/32 TFIB: call find_route_tags,dist_method=1,next_hop=10.93.0.11,Et2/3 TFIB: route tag chg 10.11.0.11/32,idx=0,inc=26,outg=Unkn,enabled=0x3 TFIB: create tag info 10.11.0.11/32,inc tag=26,has no info TFIB: resolve tag rew,prefix=10.11.0.11/32,has tag_info,no parent TFIB: finish fib res 10.11.0.11/32:index 0,parent outg tag no parent TFIB: fib upd loadinf 10.11.0.11/32,tag=26,fib no loadin,tfib no loadin TFIB: set fib rew: pfx 10.11.0.11/32,index=0,add=1,tag_rew->adj=Ethernet2/3 tagcon: route_tag_change for: 10.250.0.97/32 intag 33, outtag 28, nexthop tsr 10.11.0.11:0 TFIB: route tag chg 10.250.0.97/32,idx=0,inc=33,outg=28,enabled=0x3 TFIB: deactivate tag rew for 10.250.0.97/32,index=0 TFIB: set fib rew: pfx 10.250.0.97/32,index=0,add=0,tag_rew->adj=Ethernet2/3 TFIB: create tag info 10.250.0.97/32,inc tag=33,has old info On VIP: TFIB: route tag chg 10.13.72.13/32,idx=0,inc=34,outg=Withdrn,enabled=0x3 TFIB: deactivate tag rew for 10.13.72.13/32,index=0 TFIB: set fib rew: pfx 10.13.72.13/32,index=0,add=0,tag_rew->adj= TFIB: create tag info 10.13.72.13/32,inc tag=34,has old info TFIB: resolve tag rew,prefix=10.13.72.13/32,has tag_info,no parent TFIB: finish fib res 10.13.72.13/32:index 0,parent outg tag no parent TFIB: set fib rew: pfx 10.100.100.100/32,index=0,add=0,tag_rew->adj= TFIB: create tag info 10.100.100.100/32,inc tag=37,has old info TFIB: resolve tag rew,prefix=10.100.100.100/32,has tag_info,no parent TFIB: finish fib res 10.100.100.100/32:index 0,parent outg tag no parent TFIB: fib upd loadinf 10.100.100.100/32,tag=37,fib no loadin,tfib no loadin

Table 232 lists the significant fields shown in the display. See Table 234 for a description of special labels that appear in the output of this debug command. Table 232

debug mpls lfib cef Field Descriptions

Field

Description

tagcon

The name of the subsystem issuing the debug output (Label Control).

LFIB

The name of the subsystem issuing the debug output.

tc_ip_rtlookup fail on x.y.w.z/m: subnet_lookup failed

The destination with IP address and mask shown is not in the routing table.

route tag chg x.y.w.z/m

Request to create the LFIB entry for the specified prefix/mask.

idx=-1

The index within the FIB entry of the path whose LFIB entry is being created. The parameter –1 means all paths for this FIB entry.

inc=s

Incoming label of the entry being processed.

outg=s

Outgoing label of the entry being processed.

enabled=0xn

Bit mask indicating the types of label switching currently enabled: •

0x1 = dynamic

•

0x2 = TSP tunnels

•

0x3 = both

fib complete delete

Indicates that the FIB entry is being deleted.

prefix=x.y.w.z/m

A destination prefix.

delete_info=1

Indicates that label_info is also being deleted.


DB-1616

May 2008


Table 232

debug mpls lfib cef Field Descriptions (continued)

Field

Description

deactivate tag rew for x.y.w.z/m

Indicates that label rewrite for specified prefix is being deleted.

index=n

Index of path in the FIB entry being processed.

set fib rew: pfx x.y.w.z/m

Indicates that label rewrite is being installed or deleted from the FIB entry for the specified destination for label imposition purposes.

add=0

Indicates that label rewrite is being deleted from the FIB (no longer imposing labels).

tag_rew->adj=s

Adjacency of label rewrite for label imposition.

resolve tag rew,prefix=x.y.w.z/m

Indicates that the FIB route to the specified prefix is being resolved.

no tag_info

Indicates that there is no label_info for the destination (destination not labeled).

no parent

Indicates that the route is not recursive.

fib scanner start

Indicates that the periodic scan of the FIB has started.

needed:1

Indicates that the LFIB needs the FIB to be scanned.

unres:n

Indicates the number of unresolved TFIB entries.

mac:n

Indicates the number of TFIB entries missing MAC strings.

loadinfo:n

Indicates whether the nonrecursive accounting state has changed and whether the loadinfo information in the LFIB needs to be adjusted.

fib upd loadinf x.y.w.z/m

Indicates that a check for nonrecursive accounting is being made and that the LFIB loadinfo information for the specified prefix is being updated.

tag=s

Incoming label of entry.

fib no loadin

Indicates that the corresponding FIB entry has no loadinfo.

tfib no loadin

Indicates that the LFIB entry has no loadinfo.

fib check cleanup for x.y.w.z/m

Indicates that a check is being made on the LFIB entry for the specified destination to determine if rewrite needs to be removed from the LFIB.

return_value=x

If x is 0, indicates that no change has occurred in the LFIB entry. If x is 1, there was a change.

fib_scanner_end

Indicates that the FIB scan has come to an end.

create dynamic entry for Indicates that the LFIB has been enabled and that an LFIB entry is being x.y.w.z/m created for the specified destination. call find_route_tags

Indicates that the labels for that destination are being requested.

dist_method=n

Identifies the label distribution method—TDP, TC-ATM, and so on.

next_hop=x.y.z.w

Identifies the next hop for the destination.

interface name

Identifies the outgoing interface for the destination.

create tag info

Indicates that a label_info data structure is being created for the destination.

has no info

Indicates that the destination does not already have label_info.

finish fib re x.y.z.w/m

Indicates that the LFIB entry for the specified route is being completed.


DB-1617


Table 232

Related Commands

debug mpls lfib cef Field Descriptions (continued)

Field

Description

parent outg tag s

If recursive, specifies the outgoing label of the route through which it is recursive (the parent). If not recursive, s = “no parent.”

tagcon: route_tag_change for: x.y.z.w/m

Indicates that label control is notifying LFIB that labels are available for the specified destination.

intag s

Identifies the incoming label for the destination.

outtag s

Identifies the outgoing label for the destination.

nexthop tsr x.y.z.w.i

Identifies the TDP ID of the next hop that sent the tag.

Command

Description

debug mpls lfib lsp

Prints detailed information about label rewrites being created and deleted as LSP tunnels are added or removed.

debug mpls lfib state

Traces what happens when label switching is enabled or disabled.

debug mpls lfib struct

Traces the allocation and freeing of LFIB-related data structures, including the LFIB itself, label rewrites, and label_info data.


DB-1618

May 2008

Debug Commands debug mpls lfib enc

debug mpls lfib enc To print detailed information about label encapsulations while label rewrites are created or updated and placed in the label-forwarding information base (LFIB), use the debug mpls lfib enc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls lfib enc no debug mpls lfib enc

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.1(3)T


12.2(33)SRA


12.2SX


Usage Guidelines

Several lines of output are produced for each route placed into the LFIB. If your router has thousands of labeled routes, issue this command with care. When label switching is first enabled, each of these routes is placed into the LFIB and a label encapsulation is created. The command output shows you on which adjacency the label rewrite is being created and the labels assigned.

Examples

The following is sample output from the debug mpls lfib enc command. This example shows the encapsulations for three routes that have been created and placed into the LFIB. Router# debug mpls lfib enc TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB:

finish res:inc tag=28,outg=Imp_null,next_hop=10.93.72.13,Ethernet4/0/3 update_mac, mac_length = 14,addr=10.93.72.13,idb=Ethernet4/0/3 get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7 get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79 encaps:inc=28,outg=Imp_null,idb:Ethernet4/0/3,sizes 14,14,1504,type 0 finish res:inc tag=30,outg=27,next_hop=10.93.72.13,Ethernet4/0/3 get ip adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=7 get tag adj: addr=10.93.72.13,is_p2p=0,fibidb=Ethernet4/0/3,linktype=79 encaps:inc=30,outg=27,idb:Ethernet4/0/3,sizes 14,18,1500,type 0 finish res:inc tag=30,outg=10,next_hop=0.0.0.0,ATM0/0.1


DB-1619


TFIB: get ip adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=7 TFIB: get tag adj: addr=0.0.0.0,is_p2p=1,fibidb=ATM0/0.1,linktype=79 TFIB: encaps:inc=30,outg=10,idb:ATM0/0,sizes 4,8,4470,type 1


debug mpls lfib enc Field Descriptions

Field

Description

TFIB

Identifies the source of the message as the LFIB subsystem.

finish res

Identifies that the LFIB resolution is being finished.

inc tag=x or inc=x

An incoming (local) label for the LFIB entry is being created. Labels can be numbers or special values.

outg=y

An outgoing (remote) label for the LFIB entry is being created.

next_hop=a.b.c.d

IP address of the next hop for the destination.

interface

The outgoing interface through which a packet will be sent.

get ip adj

Identifies that the IP adjacency to use in the LFIB entry is being determined.

get tag adj

Identifies that the label switching adjacency to use for the LFIB entry is being determined.

addr = a.b.c.d

The IP address of the adjacency.

is_p2p=x

If x is 1, this is a point-to-point adjacency. If x is 0, it is not.

fibidb = s

Indicates the interface of the adjacency.

linktype = x

The link type of the adjacency, as follows:

sizes x,y,z

•

7 = LINK_IP

•

79 = LINK_TAG

Indicates the following values:

type = x

•

x = length of macstring

•

y = length of tag encapsulation

•

z = tag MTU

Tag encapsulation type, as follows: •

0 = normal

•

1 = TCATM

•

2 = TSP tunnel

idb:s

Indicates the outgoing interface.

update_mac

Indicates that the macstring of the adjacency is being updated.

Table 234 describes the special labels, which sometimes appear in the debug output, and their meanings. Table 234

Special Labels Appearing in debug Command Output

Special Label

Meaning

Unassn—Inital value

No label assigned yet.

Unused

This destination does not have a label (for example, a BGP route).


DB-1620

May 2008


Table 234

Related Commands

Special Labels Appearing in debug Command Output (continued)

Special Label

Meaning

Withdrn

The label for this destination has been withdrawn.

Unkn

This destination should have a label, but it is not yet known.

Get_res

A recursive route that will get a label when resolved.

Exp_null

Explicit null label—used over TC-ATM.

Imp_null

Implicit null label—for directly connected routes.

Tun_hd

Identifies head of TSP tunnel.

Command

Description

debug mpls lfib cef

Prints detailed information about label rewrites being created, resolved, and deactivated as CEF routes are added, changed, or removed.

debug mpls lfib lsp







DB-1621

Debug Commands debug mpls lfib fast-reroute database

debug mpls lfib fast-reroute database To enable debugging information about changes to the fast reroute database, use the debug mpls lfib fast-reroute database command in privileged EXEC command. To disable debugging output, use to no form of this command. debug mpls lfib fast-reroute database no debug mpls lfib fast-reroute database

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(10)ST


12.2(33)SRA


12.2SX


Usage Guidelines

Because using debug commands can use a great deal of bandwidth on your system, use caution when enabling the debug mpls lfib fast-reroute database command.

Examples

The following example displays debugging output for in Fast Reroute processing: Router# debug mpls lfib fast-reroute database LFIB-FRR:Clear headend FRR info for Tunnel1 LFIB-FRR:FRR info for Tunnel1 changed LFIB-FRR:update headend FRR info for 10.8.0.1/32 LFIB-FRR:item B13D94 [Tu1] (group PO0/0->Tu4000):destroying entry for 10.8.0.1/32... [514 left] LFIB-FRR:item B13D94 [Tu1]:removed from name tree LFIB-FRR:item B13D94 [Tu1]:removed from group PO0/0->Tu4000 tree %LINK-5-CHANGED:Interface Tunnel1, changed state to administratively down LFIB-FRR:Clear headend FRR info for Tunnel1 LFIB-FRR:FRR info for Tunnel1 changed LFIB-FRR:Clear headend FRR info for Tunnel1 LFIB-FRR:FRR info for Tunnel1 changed LFIB-FRR:Set headend FRR info for Tunnel1 {main=PO0/0,backup=Tu4000,label=18} LFIB-FRR:FRR info for Tunnel1 changed %SYS-5-CONFIG_I:Configured from console by console LFIB-FRR:update headend FRR info for 10.8.0.1/32


DB-1622

May 2008

Debug Commands debug mpls lfib fast-reroute database

LFIB-FRR:item B13D94 [Tu1]:inserted in name tree LFIB-FRR:item B13D94 [Tu1]:inserted in group PO0/0->Tu4000 tree LFIB-FRR:item B13D94 [Tu1] (group PO0/0->Tu4000):full entry created for 10.8.0.1/32 [total 515] LFIB-FRR:update headend FRR info for 10.8.0.1/32 LFIB-FRR:item B13D94 [Tu1] (group PO0/0->Tu4000):updating entry for 10.8.0.1/32... LFIB-FRR:item B13D94 [Tu1] (group PO0/0->Tu4000):... updated %LINK-3-UPDOWN:Interface Tunnel1, changed state to up LFIB-FRR:update headend FRR info for 10.43.0.0/16 LFIB-FRR:item B04C2C [Tu486]:inserted in name tree LFIB-FRR:item B04C2C [Tu486]:inserted in group PO0/0->Tu4000 tree LFIB-FRR:item B04C2C [Tu486] (group PO0/0->Tu4000):full entry created for 10.43.0.0/16 [total 516] LFIB-FRR:update headend FRR info for 10.43.0.0/16 LFIB-FRR:item B04BB4 [Tu481]:inserted in name tree LFIB-FRR:item B04BB4 [Tu481]:inserted in group PO0/0->Tu4000 tree LFIB-FRR:item B04BB4 [Tu481] (group PO0/0->Tu4000):full entry created for 10.43.0.0/16 [total 517] LFIB-FRR:update headend FRR info for 10.2.0.0/16 LFIB-FRR:item B04B3C [Tu486]:inserted in name tree LFIB-FRR:item B04B3C [Tu486]:inserted in group PO0/0->Tu4000 tree LFIB-FRR:item B04B3C [Tu486] (group PO0/0->Tu4000):full entry created for 10.2.0.0/16 [total 518] LFIB-FRR:update headend FRR info for 10.2.0.0/16 LFIB-FRR:item B04AC4 [Tu481]:inserted in name tree LFIB-FRR:item B04AC4 [Tu481]:inserted in group PO0/0->Tu4000 tree

Related Commands

Command

Description

debug mpls traffic-eng Displays debugging information about fast reroute events. tunnels fast-reroute events debug mpls traffic-eng Displays debugging information about the rerouting of traffic from tunnels fast-reroute link-protected interfaces to backup tunnels. reroutes


DB-1623

Debug Commands debug mpls lfib fast-reroute events

debug mpls lfib fast-reroute events To display debugging information about fast reroute events, use the debug mpls lfib fast-reroute events command in privileged EXEC command. To disable debugging output, use to no form of this command. debug mpls lfib fast-reroute events no debug mpls lfib fast-reroute events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(10)ST


12.2(33)SRA


12.2SX


Usage Guidelines

Because using debug commands can use a great deal of bandwidth on your system, use caution when enabling the debug mpls lfib fast-reroute events command.

Examples

The following example reports on the rerouting of traffic to a backup tunnel because of a change of state at a link-protected physical interface. Router# debug mpls lfib fast-reroute events LFIB-FRR:enqueued interface DOWN event for PO0/0 (Up) LFIB-FRR:discarded interface DOWN event for PO0/0 (Up) LFIB-FRR:processing interface DOWN event for PO0/0 (Up) LFIB-FRR:group PO0/0->Tu4000:output if fixup:Backup(Tu4000) -> Backup(Tu4000)

Note

The state given in parentheses reflects what the FRR database currently understands to be the state of the physical interface. This may or may not be the same as the event state reported earlier on that same display line.


DB-1624

May 2008

Debug Commands debug mpls lfib fast-reroute events

Related Commands

Command

Description

debug mpls traffic-eng Displays debugging information about changes to the fast reroute database. tunnels fast-reroute database debug mpls traffic-eng Displays debugging information about the rerouting of traffic from tunnels fast-reroute link-protected interfaces to backup tunnels. reroutes


DB-1625

Debug Commands debug mpls lfib fast-reroute reroutes

debug mpls lfib fast-reroute reroutes To enable debugging information about the rerouting of protected Label Forwarding Information Base (LFIB) entries between the primary and backup outgoing interfaces, use the debug mpls lfib fast-reroute reroutes command in privileged EXEC command. To disable debugging output, use to no form of this command. debug mpls lfib fast-reroute reroutes no debug mpls lfib fast-reroute reroutes

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(10)ST


12.2(33)SRA


12.2SX


Usage Guidelines

Because using debug commands can use a great deal of bandwidth on your system, use caution when enabling the debug mpls lfib fast-reroute reroutes command. The output of this command increases in proportion to the number of tunnels that utilize fast reroute.

Examples

The following example reports the results of reroute attempts: Router# debug mpls lfib fast-reroute reroutes LFIB-FRR:item LFIB-FRR:item LFIB-FRR:item LFIB-FRR:item LFIB-FRR:item LFIB-FRR:item LFIB-FRR:item LFIB-FRR:item LFIB-FRR:item LFIB-FRR:item

B0E844 B0E8BC B0E934 B0E9AC B0EA24 B0EA9C B0EB14 B0EB8C B0EC04 B0EC7C

[Tu139]:output [Tu138]:output [Tu387]:output [Tu137]:output [Tu136]:output [Tu135]:output [Tu384]:output [Tu134]:output [Tu133]:output [Tu132]:output

if if if if if if if if if if

fixup, fixup, fixup, fixup, fixup, fixup, fixup, fixup, fixup, fixup,

Main(PO0/0) Main(PO0/0) Main(PO0/0) Main(PO0/0) Main(PO0/0) Main(PO0/0) Main(PO0/0) Main(PO0/0) Main(PO0/0) Main(PO0/0)

-> -> -> -> -> -> -> -> -> ->

Backup(Tu4000), Backup(Tu4000), Backup(Tu4000), Backup(Tu4000), Backup(Tu4000), Backup(Tu4000), Backup(Tu4000), Backup(Tu4000), Backup(Tu4000), Backup(Tu4000),

succeeded succeeded succeeded succeeded succeeded succeeded succeeded succeeded succeeded succeeded


DB-1626

May 2008

Debug Commands debug mpls lfib fast-reroute reroutes

Related Commands

Command

Description

debug mpls traffic-eng Displays debugging information about changes to the fast reroute database. tunnels fast-reroute database debug mpls traffic-eng Displays debugging information about fast reroute events. tunnels fast-reroute events


DB-1627

Debug Commands debug mpls lfib lsp

debug mpls lfib lsp To print detailed information about label rewrites being created and deleted as label-switched path (LSP) tunnels are added or removed, use the debug mpls lfib lsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls lfib lsp no debug mpls lfib lsp

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.1(3)T


Examples

12.2(33)SRA


12.2SX


The following is sample output from the debug mpls lfib lsp command: Router# debug mpls lfib lsp TSP-tunnel related TFIB services debugging is on TFIB: tagtun,next hop=10.93.72.13,inc=35,outg=1,idb=Et4/0/3 TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7 TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo TFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=7,nh=10.93.72.13 TFIB: tagtun,next hop=10.92.0.7,inc=36,outg=1,idb=Et4/0/2 TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6 TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no old loadinfo TFIB: tagtun tag chg linec,fiblc=0,in tg=36,o tg=1,if=6,nh=10.92.0.7 TFIB: tagtun_delete, inc = 36 tagtun tag del linec,itag=12 TFIB: tagtun_delete, inc = 35 tagtun tag del linec,itag=12 TFIB: tagtun,next hop=10.92.0.7,inc=35,outg=1,idb=Et4/0/2 TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6 TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no old loadinfo TFIB: tagtun tag chg linec,fiblc=0,in tg=35,o tg=1,if=6,nh=10.92.0.7


DB-1628

May 2008


On VIP: TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7 TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7 TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no TFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6 TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6 TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.93.72.13,if=7 TFIB: tsptunnel:next hop=10.93.72.13,inc=35,outg=Imp_null,if_number=7 TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no TFIB: tagtun chg msg,in tg=36,o tg=1,nh=10.92.0.7,if=6 TFIB: tsptunnel:next hop=10.92.0.7,inc=36,outg=Imp_null,if_number=6 TFIB: tsptun update loadinfo:tag=36,loadinfo_reqd=0,no new loadinfo,no TFIB: tagtun chg msg,in tg=35,o tg=1,nh=10.92.0.7,if=6 TFIB: tsptunnel:next hop=10.92.0.7,inc=35,outg=Imp_null,if_number=6 TFIB: tsptun update loadinfo:tag=35,loadinfo_reqd=0,no new loadinfo,no

old loadinfo

old loadinfo

old loadinfo

old loadinfo

old loadinfo

Table 235 describes the significant fields shown in the sample display. Table 235

debug mpls lfib lsp Field Descriptions

Field

Description

tagtun

Name of routine entered.

next hop=x.y.z.w

Next hop for the tunnel being created.

inc=x

Incoming label for this hop of the tunnel being created.

outg=x

Outgoing label (1 means Implicit Null label).

idb=s

Outgoing interface for the tunnel being created.

if_number=7

Interface number of the outgoing interface.

tsptunnel

Name of the routine entered.

tsptun update loadinfo

The procedure being performed.

tag=x

Incoming label of the LFIB slot whose loadinfo is being updated.

loadinfo_reqd=x

Indicates whether a loadinfo is expected for this entry (non-recursive accounting is on).

no new loadinfo

No change required in loadinfo.

no old loadinfo

No previous loadinfo available.

tagtun tag chg linec

Line card is being informed of the TSP tunnel.

fiblc=x

Indicates which line card is being informed (0 means all).

in tg=x

Indicates the incoming label of new TSP tunnel.

o tg=x

Indicates the outgoing label of new TSP tunnel.

if=x

Indicates the outgoing interface number.

nh=x.y.w.z

Indicates the next hop IP address.

tagtun_delete

Indicates that a procedure is being performed: delete a TSP tunnel.

tagtun tag del linec

Informs the line card of the TSP tunnel deletion.

tagtun chg msg

Indicates that the line card has received a message to create a TSP tunnel.


DB-1629


Related Commands

Command

Description

debug mpls lfib cef







DB-1630

May 2008

Debug Commands debug mpls lfib state

debug mpls lfib state To trace what happens when label switching is enabled or disabled, use the debug mpls lfib state command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls lfib state no debug mpls lfib state

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.1(3)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command when you wish to trace what happens to the label-forwarding information base (LFIB) when you issue the mpls ip or the mpls tsp-tunnel command.

Examples

The following is sample output from the debug mpls lfib state command: Router# debug mpls lfib state TFIB enable/disable state debugging is on TFIB: Upd tag sb 6(status:0xC1,tmtu:1500,VPI:1-1 VC=0/32,et:0/0/0),lc 0x0 TFIB: intf status chg: idb=Et4/0/2,status=0xC1,oldstatus=0xC3 TFIB: interface dyntag change,change in state to Ethernet4/0/2 TFIB: enable entered, table exists,enabler type=0x2 TFIB: enable, TFIB already enabled, types now 0x3,returning TFIB: enable entered, table exists,enabler type=0x1 TFIB: disable entered, table exists,type=0x1 TFIB: cleanup: tfib[32] still non-0 On linecard only: TFIB: disable lc msg recvd, type=0x1 TFIB: Ethernet4/0/1 fibidb subblock message received


DB-1631


TFIB: enable lc msg recvd, type=0x1 TFIB: Tunnel301 set encapfix to 0x6016A97C


debug mpls lfib state Field Descriptions

Field

Description

LFIB

Identifies the source of the message as the LFIB subsystem.

Upd tag sb x

Indicates that the status of the “xth” label switching sub-block is being updated, where x is the interface number. There is a label switching sub-block for each interface on which label switching has been enabled.

(status:0xC1,tmtu:1500, VPI:1-1VC=0/32, et:0/0/0),lc 0x0)

Identifies the values of the fields in the label switching sub-block, as follows: •

status byte

•

maximum transmission unit (tmtu)

•

range of ATM VPs

•

control VP

•

control VC (if this is a TC-ATM interface)

•

encapsulation type (et)

•

encapsulation information

•

tunnel interface number (lc)

•

line card number to which the update message is being sent (0 means all line cards)

intf status chg

Indicates that there was an interface status change.

idb=Et4/0/2

Identifies the interface whose status changed.

status=0xC1

Indicates the new status bits in the label switching sub-block of the idb.

oldstatus=0xC3

Indicates the old status bits before the change.

interface dyntag change, change in state to Ethernet4/0/2

Indicates that there was a change in the dynamic label status for the particular interface.

enable entered

Indicates that the code that enables the LFIB was invoked.

TFIB already enabled

Indicates that the LFIB was already enabled when this call was made.

table exists

Indicates that an LFIB table had already been allocated in a previous call.

cleanup: tfib[x] still non-0

Indicates that the LFIB is being deleted, but that slot x is still active.

disable lc mesg recvd, type=0x1

Indicates that a message to disable label switching type 1 (dynamic) was received by the line card.

disable entered, table exists,type=0x1

Indicates that a call to disable dynamic label switching was issued.

Ethernet4/0/1 fibidb subblock message received

Indicates that a message giving fibidb status change was received on the line card.


DB-1632

May 2008


Table 236

debug mpls lfib state Field Descriptions (continued)

Field

Description

enable lc msg recvd,type=0x1

Indicates that the line card received a message to enable label switching type 1 (dynamic).

Tunnel301 set encapfix to 0x6016A97C

Shows that fibidb Tunnel301 on the line card received an encapsulation fixup.

types now 0x3, returning Shows the value of the bitmask indicating the type of label switching enabled on the interface, as follows:

Related Commands

•

0x1—means dynamic label switching

•

0x2—means tsp-tunnels

•

0x3—means both

Command

Description

debug mpls lfib cef


debug mpls lfib lsp





DB-1633

Debug Commands debug mpls lfib struct

debug mpls lfib struct To trace the allocation and freeing of label-forwarding information base (LFIB)-related data structures, such as the LFIB itself, label rewrites, and label_info data, use the debug mpls lfib struct command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls lfib struct no debug mpls lfib struct

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

11.1CT


12.1(3)T


Examples

12.2(33)SRA


12.2SX


The following is sample output from the debug mpls lfib struct command: Router# debug mpls lfib struct TFIB data structure changes debugging is on TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB:

delete tag rew, incoming tag 32 remove from tfib,inc tag=32 set loadinfo,tag=32,no old loadinfo,no new loadinfo TFIB not in use. Checking for entries. cleanup: tfib[0] still non-0 remove from tfib,inc tag=Tun_hd set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo TFIB freed. enable, TFIB allocated, size 4024 bytes, maxtag = 500 create tag rewrite: inc Tun_hd,outg Unkn add to tfib at Tun_hd, first in circular list, mac=0,enc=0 delete tag rew, incoming tag Tun_hd remove from tfib,inc tag=Tun_hd set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo create tag rewrite: inc Tun_hd,outg Unkn add to tfib at Tun_hd, first in circular list, mac=0,enc=0 create tag rewrite: inc 26,outg Unkn


DB-1634

May 2008

Debug Commands debug mpls lfib struct

TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB: TFIB:

add to tfib at 26, first in circular list, mac=0,enc=0 add to tfib at 27, added to circular list, mac=0,enc=0 delete tag rew, incoming tag Tun_hd remove from tfib,inc tag=Tun_hd set loadinfo,tag=Exp_null,no old loadinfo,no new loadinfo add to tfib at 29, added to circular list, mac=4,enc=8 delete tag rew, incoming tag 29 remove from tfib,inc tag=29


debug mpls lfib struct Field Descriptions

Field

Description

TFIB

The subsystem issuing the message.

delete tag rew

A label rewrite is being freed.

remove from tfib

A label rewrite is being removed from the LFIB.

inc tag=s

The incoming label of the entry being processed.

set loadinfo

The loadinfo field in the LFIB entry is being set (used for nonrecursive accounting).

tag=s

The incoming label of the entry being processed.

no old loadinfo

The LFIB entry did not have a loadinfo before.

no new loadinfo

The LFIB entry should not have a loadinfo now.

TFIB not in use. Checking for entries.

Label switching has been disabled and the LFIB is being freed up.

cleanup: tfib[x] still non-0

The LFIB is being checked for any entries in use, and entry x is the lowest numbered slot still in use.

TFIB freed

The LFIB table has been freed.

enable, TFIB allocated, Label switching has been enabled and an LFIB of x bytes has been allocated. size x bytes, maxtag = y The largest legal label is y.

Related Commands

create tag rewrite

A label rewrite is being created.

inc s

The incoming label.

outg s

The outgoing label.

add to tfib at s

A label rewrite has been placed in the LFIB at slots.

first in circular list

This LFIB slot had been empty and this is the first rewrite in the list.

mac=0,enc=0

Length of the MAC string and total encapsulation length, including labels.

added to circular list

A label rewrite is being added to an LFIB slot that already had an entry. This rewrite is being inserted in the circular list.

Command

Description

debug mpls lfib cef


debug mpls lfib lsp





DB-1635

Debug Commands debug mpls lspv

debug mpls lspv To display information related to the MPLS LSP Ping/Traceroute feature, use the debug mpls lspv command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls lspv [tlv] [error] [event] [ipc] [packet [data | error]] [path-discovery] [multipath] [all] no debug mpls lspv

Syntax Description

tlv

(Optional) Displays Multiprotocol Label Switching (MPLS) echo packet type, length, values (TLVs) information as it is being coded and decoded.

error

(Optional) Displays error conditions encountered during MPLS echo request and echo reply encoding and decoding. See Table 223.

event

(Optional) Displays MPLS echo request and reply send and receive event information.

ipc

(Optional) Interprocess communication. Displays debug information regarding communication between the Route Processor and line cards.

packet data

(Optional) Displays detailed debug information for the MPLS echo packets sent and received. This output is seen only on the originating router and the router generating the reply.

packet error

(Optional) Displays packet errors for MPLS echo request and reply. No output is expected for this command.

path-discovery

(Optional) Provides information regarding LSP traceroute path discovery operations.

multipath

(Optional) Displays multipath information.

all

(Optional) Enables all the command keywords.

Command Default

MPLS LSP debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(27)S


12.4(6)T

The following keywords were added: ipc, path-discovery, multipath, and all.

12.2(28)SB

This command was integrated into Cisco IOS Release 12.28(SB) and implemented on the Cisco 10000 series router.

12.0(32)SY

This command was integrated into Cisco IOS Release 12.0(32)SY.

12.2(33)SRA


12.4(11)T


12.2(31)SB2



DB-1636

May 2008


Usage Guidelines

Release

Modification

12.2(33)SXH


12.2SX


Use this command to monitor activity associated with the ping mpls and the trace mpls commands. Table 238 lists the messages displayed by the debug mpls lspv error command and the reason for each error message. Table 238

Messages Displayed by the debug mpls lspv error Command

Message

Reason Why Message Is Displayed

Echo reply discarded because not An echo reply message is sent because the IP header indicates that routable the packet has the Router Alert set and the packet is not routable.

Examples

UDP checksum error, packet discarded

A packet is received on the port being used by Label Switched Path Verification (LSPV) and there is a checksum error on the packet.

Invalid echo message type

An MPLS echo packet with an invalid echo message type (neither a request nor a reply) is received.

Illegal Action

The state machine that drives the LSPV software detects an invalid condition.

The following is sample output from the ping mpls command when LSPV event debugging is enabled: Router# debug mpls lspv event LSPV event debugging is on Router# ping mpls ipv4 10.131.159.252/32 repeat 1 Sending 1, 100-byte MPLS Echos to 10.131.159.252/32, timeout is 2 seconds, send interval is 0 msec:

Codes: '!' - success, 'Q' - request not transmitted, '.' - timeout, 'U' - unreachable, 'R' - downstream router but not target

Type escape sequence to abort. ! Success rate is 100 percent (1/1), round-trip min/avg/max = 48/48/48 ms Router# *Dec 31 19:31:15.366: LSPV: waiting for 2 seconds *Dec 31 19:31:15.366: LSPV: sender_handle: 2000002D, Event Echo Requests Start, [Idle->Waiting for Echo Reply] *Dec 31 19:31:15.414: LSPV: sender_handle: 2000002D, Event Echo Reply Received, [Waiting for Echo Reply->Waiting for Interval] *Dec 31 19:31:15.466: LSPV: sender_handle: 2000002D, Event Echo Requests Cancel, [Waiting for Interval->Idle]


DB-1637


Router# undebug all All possible debugging has been turned off

The following is sample output from the ping mpls command when LSPV TLV debugging is enabled: Router# debug mpls lspv tlv LSPV tlv debugging is on Router# ping mpls ipv4 10.131.159.252/32 repeat 1 Sending 1, 100-byte MPLS Echos to 10.131.159.252/32, timeout is 2 seconds, send interval is 0 msec:

Codes: '!' - success, 'Q' - request not transmitted, '.' - timeout, 'U' - unreachable, 'R' - downstream router but not target Type escape sequence to abort. ! Success rate is 100 percent (1/1), round-trip min/avg/max = 40/40/40 ms Router# *Dec 31 19:32:32.566: LSPV: Echo Hdr encode: version 1, msg type 1, reply mode 2 , return_code 0, return_subcode 0, sender handle 9400002E, sequence number 1, timestamp sent 14:32:32 EST Wed Dec 31 2003, timestamp rcvd 19:00:00 EST Thu Dec 31 1899 *Dec 31 19:32:32.566: LSPV: IPV4 FEC encode: destaddr 10.131.159.252/32 *Dec 31 19:32:32.566: LSPV: Pad TLV encode: type 1, size 18, pattern 0xABCD *Dec 31 19:32:32.606: LSPV: Echo Hdr decode: version 1, msg type 2, reply mode 2, return_code 3, return_subcode 0, sender handle 9400002E, sequence number 1, timestamp sent 14:32:32 EST Wed Dec 31 2003, timestamp rcvd 14:32:32 EST Wed Dec 31 2003 Router# undebug all All possible debugging has been turned off

The following is sample output from the trace mpls multipath command when LSPV multipath debugging is on: Router# debug mpls lspv multipath multipath information debugging is on Router# trace mpls multipath ipv4 10.5.5.5/32 Starting LSP Multipath Traceroute for 10.5.5.5/32 Codes: '!' - success, 'Q' - request not sent, '.' - timeout, 'L' - labeled output interface, 'B' - unlabeled output interface, 'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch, 'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry, 'P' - no rx intf label prot, 'p' - premature termination of LSP, 'R' - transit router, 'I' - unknown upstream index, 'X' - unknown return code, 'x' - return code 0 Type escape sequence to abort. LL *Aug 30 20:39:03.719: LSPV: configuring bitmask multipath, base 0x7F000000, bitmapsize 32, start 0x7F000000, numbits 32 *Aug 30 20:39:03.719: LSPV: multipath info: info_length 4, bitmapsize 32, multipath_length 8, start 127.0.0.0, base 127.0.0.0, numbits 32


DB-1638

May 2008


*Aug 30 20:39:03.719: LSPV: multipath info: info_length 4, bitmapsize 32, multipath_length 8, start 127.0.0.0, base 127.0.0.0, numbits 32 *Aug 30 20:39:03.719: LSPV: getnext bit_cursor 0, index 0, mask 0x80000000 *Aug 30 20:39:03.719: LSPV: next addr 127.0.0.1 *Aug 30 20:39:03.719: LSPV: multipath info: datagramsize 8 *Aug 30 20:39:03.719: 7F 00 00 00 FF FF FF FF *Aug 30 20:39:04.007: LSPV: multipath info: ! Path 0 found, output interface Et1/0 source 10.2.3.2 destination 127.0.0.1 Paths (found/broken/unexplored) (1/0/0) Echo Request (sent/fail) (3/0) Echo Reply (received/timeout) (3/0) Total Time Elapsed 924 ms Router# *Aug 30 20:39:04.007: 7F 00 00 00 FF FF FF FF *Aug 30 20:39:04.007: LSPV: ds map convert: rtr_id A030404, mtu 1500 intf_addr 10.3.4.4 hashkey 8, multipath length 8, info 2130706432 *Aug 30 20:39:04.007: LSPV: multipath info: hashkey type 8, base 0x7F000000, bitmapsize 32, info0 0xFFFFFFFF *Aug 30 20:39:04.007: LSPV: multipath info: info_length 4, bitmapsize 32, multipath_length 8, start 127.0.0.1, base 127.0.0.1, numbits 32 *Aug 30 20:39:04.007: LSPV: getnext bit_cursor 0, index 0, mask 0x80000000 *Aug 30 20:39:04.007: LSPV: next addr 127.0.0.1 *Aug 30 20:39:04.007: LSPV: multipath info: datagramsize 8 *Aug 30 20:39:04.007: 7F 00 00 00 FF FF FF FF *Aug 30 20:39:04.299: LSPV: multipath info: datagramsize 8 *Aug 30 20:39:04.299: 7F 00 00 00 FF FF FF FF *Aug 30 20:39:04.299: LSPV: ds map convert: rtr_id A040505, mtu 1504 intf_addr 10.4.5.5 hashkey 8, multipath length 8, info 2130706432 *Aug 30 20:39:04.299: LSPV: multipath info: hashkey type 8, base 0x7F000000, bitmapsize 32, info0 0xFFFFFFFF *Aug 30 20:39:04.299: LSPV: multipath info: info_length 4, bitmapsize 32, multipath_length 8, start 127.0.0.1, base 127.0.0.1, numbits 32 *Aug 30 20:39:04.299: LSPV: getnext bit_cursor 0, index 0, mask 0x80000000 *Aug 30 20:39:04.299: LSPV: next addr 127.0.0.1 *Aug 30 20:39:04.299: LSPV: multipath info: datagramsize 8 *Aug 30 20:39:04.299: 7F 00 00 00 FF FF FF FF Router# undebug all multipath information debugging is off

Related Commands

Command

Description

ping mpls

Checks MPLS LSP connectivity.

trace mpls

Discovers MPLS LSP routes that packets will actually take when traveling to their destinations.


DB-1639

Debug Commands debug mpls netflow

debug mpls netflow To display debug messages for MPLS egress NetFlow accounting, use the debug mpls netflow command in user EXEC mode. To disable debugging output, use the no form of this command. debug mpls netflow no debug mpls netflow

Syntax Description


Defaults


Command Modes

EXEC

Command History

Release

Modification

12.0(10)ST


12.1(5)T


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

Here is sample output from the debug mpls netflow command: Router# Router# debug mpls ? adjacency MPLS adjacency database events atm-cos MPLS Controlled ATM CoS atm-ldp MPLS ATM LDP events MPLS events ldp Label Distribution Protocol lfib MPLS Forwarding Information Base services netflow MPLS Egress NetFlow Accounting packets MPLS packets tagcon MPLS/Tag control process traffic-eng MPLS Traffic Engineering debug Router# debug mpls netflow MPLS Egress NetFlow debugging is on Router# Router# Router# 4d00h:Egress flow:entry created, dest 3.3.3.3/32, src 34.0.0.1/8 Router#


DB-1640

May 2008


Router# 4d00h:Egress flow:entry created, dest 3.3.3.3/32, src 42.42.42.42/32 Router# conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)# int eth1/4 Router(config-if)# no mpls netflow egress Router(config-if)# 4d00h:MPLS output feature change, trigger TFIB scan 4d00h:tfib_scanner_walk, prefix 5.5.5.5/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 2.0.0.0/8, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 3.3.3.3/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 40.40.40.40/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 50.50.50.50/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 100.100.100.100/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 180.1.1.0/24, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 190.1.1.0/24, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 2.0.0.0/8, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 4.4.4.4/32, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 40.40.40.40/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 50.50.50.50/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 177.1.1.0/24, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 180.1.1.0/24, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 190.1.1.0/24, rewrite flow flag 1 Router(config-if)# Router(config-if)# mpls netflow egress Router(config-if)# 4d00h:Interface refcount with output feature enabled = 2 4d00h:MPLS output feature change, trigger TFIB scan 4d00h:tfib_scanner_walk, prefix 5.5.5.5/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 2.0.0.0/8, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 3.3.3.3/32, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 40.40.40.40/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 50.50.50.50/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 100.100.100.100/32, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 180.1.1.0/24, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 190.1.1.0/24, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 2.0.0.0/8, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 4.4.4.4/32, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 40.40.40.40/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 50.50.50.50/32, rewrite flow flag 0 4d00h:tfib_scanner_walk, prefix 177.1.1.0/24, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 180.1.1.0/24, rewrite flow flag 1 4d00h:tfib_scanner_walk, prefix 190.1.1.0/24, rewrite flow flag 1 4d00h:Egress flow:entry created, dest 3.3.3.3/32, src 42.42.42.42/32 Router(config-if)# Router(config-if)# end Router# show run int eth1/4 Building configuration... Current configuration: ! interface Ethernet1/4 ip vrf forwarding vpn1 ip address 180.1.1.1 255.255.255.0 no ip directed-broadcast mpls netflow egress end Router# Router# 4d00h:%SYS-5-CONFIG_I:Configured from console by console Router#


DB-1641


Note

Related Commands

Flow flag 1 prefixes are reachable through this interface; therefore, MPLS egress NetFlow accounting is applied to all packets going out the destination prefix. Flow flag 0 prefixes are not reachable through this interface; therefore, MPLS egress NetFlow accounting is not applied to any packets going out the destination prefix.

Command

Description

show debug

Displays active debug output.


DB-1642

May 2008

Debug Commands debug mpls packets

debug mpls packets To display Multiprotocol Label Switching (MPLS) labeled packets switched by the host router, use the debug mpls packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls packets [interface] no debug mpls packets [interface]

Syntax Description

interface

Defaults

The debug output displays all labeled packets, regardless of the interface.

Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

Note

Examples

(Optional) The interface or subinterface name.

Modification

11.1CT


12.1(3)T

This command was modified for new MPLS terminology and syntax.

12.2(25)S

The command ouput was enhanced to display MPLS high availability information.

12.2(28)SB


12.2(33)SRA


12.2(33)SXH


12.2SX


The optional interface parameter restricts the display to only those packets received or sent on the indicated interface or subinterface.

Use this command with care because it generates output for every packet processed. Furthermore, enabling this command causes fast and distributed label switching to be disabled for the selected interfaces. To avoid adversely affecting other system activity, use this command only when traffic on the network is at a minimum.

The following is sample output from the debug mpls packets command: Router# debug mpls packets


DB-1643

Debug Commands debug mpls packets

TAG: Hs3/0: recvd: CoS=0, TTL=254, Tag(s)=27 TAG: Hs0/0: xmit: (no tag) TAG: Hs0/0: recvd: CoS=0, TTL=254, Tag(s)=30 TAG: Hs3/0: xmit: CoS=0, TTL=253, Tag(s)=27


debug mpls packets Field Descriptions

Field

Description

Hs0/0

The identifier for the interface on which the packet was received or sent.

recvd

Packet received.

xmit

Packet transmitted.

CoS

Class of Service field from the packet label header.

TTL

Time to live field from the packet label header.

(no tag)

Last label was popped off the packet and sent unlabeled.

Tag(s)

A list of labels on the packet, ordered from the top of the stack to the bottom.

Cisco 10000 Series Example

The following is sample output from the debug mpls packets command: Router# debug mpls packets Gi6/0/0: rx: Len 118 Stack {30 6 255} - ipv4 data Gi6/1/1: tx: Len 118 Stack {22 6 254} - ipv4 data

Related Commands

Command

Description

show mpls forwarding-table

Displays the contents of the MPLS forwarding table.


DB-1644

May 2008

Debug Commands debug mpls static binding

debug mpls static binding To display information related to static binding events, use the debug mpls static binding command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls static binding [vrf vpn-name] no debug mpls static binding [vrf vpn-name]

Syntax Description

vrf vpn-name (Optional)

Defaults


Command Modes

Privileged EXEC

Command History

Release

Displays information only for the specified VPN routing and forwarding instance (vpn-name).

Modification

12.0(23)S


12.0(26)S

This command was incorporated into Cisco IOS Release 12.0(26)S. You can enable debug only for a VRF.

12.3(14)T


12.2(33)SXH


12.2SX


12.2(33)SB


Usage Guidelines

Use the debug mpls static binding command to troubleshoot problems related to MPLS static labels or VRF aware MPLS static labels. If you specify the vrf keyword, debug is enabled only for a specified VRF.

Examples

The following is sample output from the debug mpls static binding command: Router# debug mpls static binding vrf vpn100 MPLS Static label bindings debugging is on 00:15:13: 00:15:13: 00:15:13: 00:15:13: 00:15:13: 00:15:18: 00:15:18:

mpls: mpls: mpls: mpls: mpls: mpls: mpls:

Add remote static binding: 10.0.0.0/8; label 0; nexthop 172.16.0.8:0 Add static label binding for 10.0.0.0/8 Add static label binding for 10.0.0.1/8 Add remote static binding: 10.0.0.1/8; label 2607; nexthop 172.17.0.66:0 Add static label binding for 172.18.0.0/16 Periodic static label adjust Static label update: 10.0.0.0/8


DB-1645

Debug Commands debug mpls static binding

00:15:18: 00:15:18: 00:15:18: 00:15:18: 00:15:18: 00:15:18: 00:15:18: 00:15:18: 00:15:28: 00:15:28: 00:15:28: 00:15:28: 00:15:28: 00:15:28: 00:15:28: 00:15:28: 00:15:28: 00:15:38: 00:15:38: 00:15:38:

Related Commands

Add remote label: nexthop: 172.16.0.8:0; label: 0 mpls: Periodic static label adjust mpls: Static label update: 10.0.0.1/8 Waiting for withdrawal of dynamic local label 55 Add remote label: nexthop: 172.17.0.66:0; label: 2607 mpls: Periodic static label adjust mpls: Static label update: 172.18.0.0/16 Waiting for withdrawal of dynamic local label 17 mpls: Periodic static label adjust mpls: Periodic static label adjust mpls: Static label update: 10.0.0.1/8 Local label 55 added to tib Signal route tag change, in label 55;out label 8388611; nh 192.168.44.77 mpls: Periodic static label adjust mpls: Static label update: 172.18.0.0/16 Local label 17 added to tib Signal route tag change, in label 17;out label 8388611; nh 192.168.44.66 mpls: Periodic static label adjust mpls: Periodic static label adjust mpls: Periodic static label adjust

Command

Description

mpls static binding ipv4 vrf

Binds a prefix to a local label.

show debug



DB-1646

May 2008

Debug Commands debug mpls traffic-eng areas

debug mpls traffic-eng areas To print information about traffic engineering area configuration change events, use the debug mpls traffic-eng areas command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng areas no debug mpls traffic-eng areas

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)ST


12.1(3)T


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, information is printed about traffic engineering area configuration change events: Router# debug mpls traffic-eng areas TE-AREAS:isis level-1:up event TE-PCALC_LSA:isis level-1


DB-1647

Debug Commands debug mpls traffic-eng autoroute

debug mpls traffic-eng autoroute To print information about automatic routing over traffic engineering tunnels, use the debug mpls traffic-eng autoroute command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng autoroute no debug mpls traffic-eng autoroute

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)ST


12.1(3)T


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, information is printed about automatic routing over traffic engineering tunnels: Router# debug mpls traffic-eng autoroute TE-Auto:announcement that destination 0001.0000.0003.00 has 1 tunnels Tunnel1 (traffic share 333, nexthop 10.112.0.12)


DB-1648

May 2008

Debug Commands debug mpls traffic-eng auto-tunnel backup

debug mpls traffic-eng auto-tunnel backup To print system information about traffic engineering backup autotunnels, use the debug mpls traffic-eng auto-tunnel backup command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng auto-tunnel backup [all | events | state] no debug mpls traffic-eng auto-tunnel backup [all | events | state]

Syntax Description

all

(Optional) Enables all backup autotunnel debugging output.

events

(Optional) Prints backup autotunnel system events.

state

(Optional) Prints the system state of backup autotunnels.

Command Default

Debugging output for backup autotunnels is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(32)S


12.4(11)T


12.2(33)SRB


12.2SX


Examples

In the following example, debugging information is printed about the system state of backup autotunnels: Router# debug mpls traffic-eng auto-tunnel backup state

Related Commands

Command

Description

debug mpls traffic-eng auto-tunnel primary

Prints system information about traffic engineering primary tunnels.

debug mpls traffic-eng tunnels events

Prints information about traffic engineering tunnel management system events.

mpls traffic-eng auto-tunnel backup

Automatically builds NHOP and NNHOP backup tunnels.

show ip explicit-paths

Displays the configured IP explicit paths.

show mpls traffic-eng tunnels

Shows information about tunnels.


DB-1649

Debug Commands debug mpls traffic-eng auto-tunnel primary

debug mpls traffic-eng auto-tunnel primary To print system information about traffic engineering primary autotunnels, use the debug mpls traffic-eng auto-tunnel primary command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng auto-tunnel primary [all | events | state] no debug mpls traffic-eng auto-tunnel primary [all | events | state]

Syntax Description

all

(Optional) Enables all primary autotunnel debugging output.

events

(Optional) Prints primary autotunnel system events.

state

(Optional) Prints the system state of primary autotunnels.

Command Default

Debugging output for primary autotunnels is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(32)S


12.4(11)T


12.2(33)SRB


12.2SX


Examples

In the following example, debugging information is printed about system events of primary autotunnels: Router# debug mpls traffic-eng auto-tunnel primary events

*Feb 6 18:12:57.871: TE_AUTO_TUN: primary CLI command: interface tunnel3000 no logging event link-status ip unnumbered Loopback0 tunnel destination 192.168.1.1 tunnel mode mpls traffic-eng end

In the following example, debugging information is printed about the system state of primary autotunnels: Router# debug mpls traffic-eng auto-tunnel primary state Samplefor debug mpls traffic-eng auto-tunnel primary state: *Feb 6 18:11:44.363: TE_AUTO_TUN: Didn't find protected Up Tunnel3000 to router id 192.168.1.1 out POS2/0


DB-1650

May 2008

Debug Commands debug mpls traffic-eng auto-tunnel primary

Sample for debug mpls traffic-eng auto-tunnel backup events (this is one log that prints on multiple lines): *Feb 6 18:19:04.303: TE_AUTO_TUN: CLI command: ip explicit-path name __dynamic_tunnel4000 index 1 next-address 192.168.1.2

Related Commands

Command

Description

debug mpls traffic-eng auto-tunnel backup

Prints system information about traffic engineering backup autotunnels.

debug mpls traffic-eng tunnels events

Prints information about traffic engineering tunnel management system events.

mpls traffic-eng auto-tunnel primary config

Enables IP processing without an explicit address.

show ip explicit-paths

Displays the configured IP explicit paths.

show mpls traffic-eng tunnels

Shows information about tunnels.


DB-1651

Debug Commands debug mpls traffic-eng forwarding-adjacency

debug mpls traffic-eng forwarding-adjacency To display debug messages for traffic engineering (TE) forwarding-adjacency events, use the debug mpls traffic-eng forwarding-adjacency command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng forwarding-adjacency no debug mpls traffic-eng forwarding-adjacency

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(15)S


12.0(16)ST


12.2(18)S


12.2(18)SXD

This command was integrated into Cisco IOS Release 12.2(18)SX.

12.2(27)SBC.


12.2(28)SB


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug mpls traffic-eng forwarding-adjacency command to troubleshoot any problems that occur after you configure the tunnel mpls traffic-eng forwarding-adjacency command.

Examples

The following is sample output from the debug mpls traffic-eng forwarding-adjacency command: Router# debug mpls traffic-eng forwarding-adjacency MPLS traffic-eng debugging is on


DB-1652

May 2008

Debug Commands debug mpls traffic-eng forwarding-adjacency

With a tunnel configured, the following output appears: interface Tunnel0 ip unnumbered Loopback0 no ip directed-broadcast tunnel destination 192.168.1.7 tunnel mode mpls traffic-eng tunnel mpls traffic-eng forwarding-adjacency tunnel mpls traffic-eng priority 7 7 tunnel mpls traffic-eng path-option 10 dynamic end

When the tunnel comes up, it generates the following debug output: *Oct *Oct *Oct

Related Commands

2 12:27:07.846:TE-Auto:announcement that destination 0168.0001.0007.00 has 1 tunnels 2 12:27:07.846: Tunnel0 (traffic share 142857, nexthop 192.168.1.7) 2 12:27:07.846: (flags: Forward-Adjacency, holdtime 0)

Command

Description

show debug


show mpls traffic-eng forwarding-adjacency

Displays TE tunnels being advertised as links in an IGP network.

tunnel mpls traffic-eng Advertises a TE tunnel as a link in an IGP network. forwarding-adjacency


DB-1653

Debug Commands debug mpls traffic-eng ha sso

debug mpls traffic-eng ha sso To display debugging output for Multiprotocol Label Switching (MPLS) traffic engineering high availability (HA) activities during the graceful switchover from an active Route Processor (RP) to a redundant standby RP, use the debug mpls traffic-eng ha sso command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng ha sso {auto-tunnel | errors | link-management {events | standby | recovery | checkpoint} | tunnel {events | standby | recovery}} no debug mpls traffic-eng ha sso {auto-tunnel | errors | link-management {events | standby | recovery | checkpoint} | tunnel {events | standby | recovery}}

Syntax Description

auto-tunnel

Displays information about autotunnel activity during the MPLS traffic engineering stateful switchover (SSO) process.

errors

Displays errors encountered during the MPLS traffic engineering SSO process.

link-management

Displays information about link management activity during the MPLS traffic engineering SSO process.

events

Displays significant events that occur during the MPLS traffic engineering SSO process.

standby

Displays information about the standby behavior during the MPLS traffic engineering SSO process.

recovery

Displays information about recovery activity during the MPLS traffic engineering SSO process.

checkpoint

Display information about checkpointing activities during the MPLS traffic engineering SSO process. Checkpointing occurs when a message is sent and acknowledged.

tunnel

Displays information about tunnel activity during the MPLS traffic engineering SSO process.

Command Default

Debugging is disabled until you issue this command with one or more keywords.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRA


12.2(33)SRB


12.2SX



DB-1654

May 2008


Usage Guidelines

This command displays debugging output about the SSO process for MPLS traffic engineering tunnels, autotunnels, and link management systems. The SSO process occurs when the active router becomes unavailable and system control and routing protocol execution is transferred from the now inactive RP to the redundant standby RP, thus providing uninterrupted network services.

Examples

The following is sample output from the debug mpls traffic-eng ha sso command when you enabled debugging keywords to monitor the SSO process for tunnels and link management systems as the standby router becomes active: Router# debug mpls traffic-eng ha sso link-management events MPLS traffic-eng SSO link management events debugging is on Router# debug mpls traffic-eng ha sso link-management recovery MPLS traffic-eng SSO link management recovery debugging is on Router# debug mpls traffic-eng ha sso link-management standby MPLS traffic-eng SSO link management standby behavior debugging is on Router# debug mpls traffic-eng ha sso link-management checkpoint MPLS traffic-eng SSO link management checkpointed info debugging is on Router# debug mpls traffic-eng ha sso tunnel standby MPLS traffic-eng SSO tunnel standby behavior debugging is on Router# debug mpls traffic-eng ha sso tunnel recovery MPLS traffic-eng SSO tunnel head recovery debugging is on Router# debug mpls traffic-eng ha sso tunnel events MPLS traffic-eng SSO events for tunnel heads debugging is on Router# debug mpls traffic-eng ha sso errors MPLS traffic-eng SSO errors debugging is on Router# show debug MPLS TE: MPLS traffic-eng MPLS traffic-eng MPLS traffic-eng MPLS traffic-eng MPLS traffic-eng MPLS traffic-eng MPLS traffic-eng MPLS traffic-eng Router#

10.0.0.9 Tu10 [61] 10.0.0.3 *May 12 20:03:38.079: TSPVIF_HA_EVENT: updated 7600-1_t10 state; action = add; result = success *May 12 20:03:38.079: TSPVIF_HA_EVENT: 7600-1_t10 fully recovered; rewrite refreshed *May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying CBTS bundle about Router_t10 *May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying RSVP HA to remove lsp_info using key 10.0.0.3->10.0.0.9 Tu10 [61] 10.0.0.3 *May 12 20:03:38.079: RRR_HA: Received notification recovery has ended. Notify IGP to flood. *May 12 20:03:38.079: TSPVIF_HA_EVENT: Received notification recovery has ended *May 12 20:03:38.079: TSPVIF_HA_STANDBY: prevent verifying setups; IGP has not converged *May 12 20:03:38.083: TSPVIF_HA_STANDBY: preventing new setups; reason: IGP recovering *May 12 20:03:38.083: TSPVIF_HA_STANDBY: prevent verifying setups; IGP has not converged *May 12 20:03:38.083: TSPVIF_HA_STANDBY: preventing new setups; reason: IGP recovering *May 12 20:03:38.083: RRR_HA_STATE: IGP flood prevented during IGP recovery 7600-1# *May 12 20:03:47.723: RRR_HA: Received notification that RIB table 0 has converged. *May 12 20:03:47.723: RRR_HA: Received notification all RIBs have converged. Notify IGP to flood. *May 12 20:03:47.723: RRR_HA_STATE: Told not to wait for IGP convergence *May 12 20:03:47.723: RRR_HA_INFO: update flooded system info; action = add; result = success


DB-1656

May 2008


*May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: result = success *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: (GigabitEthernet3/2) *May 12 20:03:47.723: *May 12 20:03:47.723 *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: Router# *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.723: *May 12 20:03:47.727: *May 12 20:03:47.727: *May 12 20:03:47.727: *May 12 20:03:47.727: *May 12 20:03:47.727: *May 12 20:03:47.727: *May 12 20:03:47.727: *May 12 20:03:47.727: success Router#

LM System key:: Flooding Protocol: ospf IGP Area ID: 0 LM Flood Data:: LSA Valid flags: 0x0 Node LSA flag: 0x0 IGP System ID: 10.0.0.3 MPLS TE Router ID: 10.0.0.3 Flooded links: 1 TLV length: 0 (bytes) Fragment id: 0 rrr_ha_lm_get_link_info_size: link size: 212 bytes; num TLVs: 0 rrr_ha_sizeof_lm_link_info: link size: 212 bytes; num TLVs: 0 RRR_HA_INFO: update flooded link[0] info; action = add; RRR HA Checkpoint Info Buffer:: Info Handle: 0x490BB1C8 Max Size: 212 Info Size: 212 Info Write Pointer: 0x490BB29C LM Link key:: Flooding Protocol: ospf IGP Area ID: 0

Link ID: 0

Ifnumber: 5 Link Valid Flags: 0x193B Link Subnet Type: Broadcast Local Intfc ID: 0 Neighbor Intf ID: 0 Link IP Address: 10.0.3.1 Neighbor IGP System ID: 10.0.3.2 Neighbor IP Address: 10.0.0.0 IGP Metric: 1 TE Metric: 1 Physical Bandwidth: 1000000 kbits/sec Res. Global BW: 3000 kbits/sec Res. Sub BW: 0 kbits/sec Upstream::

Reservable Bandwidth[0]: Reservable Bandwidth[1]: Reservable Bandwidth[2]: Reservable Bandwidth[3]: Reservable Bandwidth[4]: Reservable Bandwidth[5]: Reservable Bandwidth[6]: Reservable Bandwidth[7]: Downstream::

Global Pool ----------0 0 0 0 0 0 0 0

Sub Pool ---------0 0 0 0 0 0 0 0

Global Pool ----------3000 3000 3000 3000 3000 3000 3000 2900

Sub Pool ---------0 0 0 0 0 0 0 0

kbits/sec kbits/sec kbits/sec kbits/sec kbits/sec kbits/sec kbits/sec kbits/sec

Reservable Bandwidth[0]: kbits/sec Reservable Bandwidth[1]: kbits/sec Reservable Bandwidth[2]: kbits/sec Reservable Bandwidth[3]: kbits/sec Reservable Bandwidth[4]: kbits/sec Reservable Bandwidth[5]: kbits/sec Reservable Bandwidth[6]: kbits/sec Reservable Bandwidth[7]: kbits/sec Affinity Bits: 0x0 Protection Type: Capability 0, Working Priority 0 Number of TLVs: 0 RRR_HA: Updated flood state for ospf area 0 with 1 links); result =

The following example shows how to turn off debugging: Router# no debug mpls traffic-eng ha sso link-management events MPLS traffic-eng SSO link management events debugging is off


DB-1657


Router# no debug mpls traffic-eng ha sso link-management recovery MPLS traffic-eng SSO link management recovery debugging is off Router# no debug mpls traffic-eng ha sso link-management standby MPLS traffic-eng SSO link management standby behavior debugging is off Router# no debug mpls traffic-eng ha sso link-management checkpoint MPLS traffic-eng SSO link management checkpointed info debugging is off Router# no debug mpls traffic-eng ha sso tunnel standby MPLS traffic-eng SSO tunnel standby behavior debugging is off Router# no debug mpls traffic-eng ha sso tunnel recovery MPLS traffic-eng SSO tunnel head recovery debugging is off Router# no debug mpls traffic-eng ha sso tunnel events MPLS traffic-eng SSO events for tunnel heads debugging is off Router# no debug mpls traffic-eng ha errors MPLS traffic-eng SSO errors debugging is off

Related Commands

Command

Description

debug ip rsvp high-availability

Displays debugging output for RSVP HA activities that improve the accessibility of network resources.

debug ip rsvp sso

Displays debugging output for RSVP activities during the graceful switchover from an active RP to a redundant RP.


DB-1658

May 2008

Debug Commands debug mpls traffic-eng link-management admission-control

debug mpls traffic-eng link-management admission-control To print information about traffic engineering label-switched path (LSP) admission control on traffic engineering interfaces, use the debug mpls traffic-eng link-management admission-control command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management admission-control [detail] [acl-number] no debug mpls traffic-eng link-management admission-control [detail]

Syntax Description

detail

(Optional) Prints detailed debugging information.

acl-number

(Optional) Uses the specified access list to filter the debugging information. Prints information only for those LSPs that match the access list.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)S


12.1(3)T

This command was integrated into Cisco IOS Release 12.1(3)T, and the detail keyword and the acl-number argument were added.

12.0(10)ST


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, information is printed about traffic engineering LSP admission control on traffic engineering interfaces: Router# debug mpls traffic-eng link-management admission-control TE-LM-ADMIT:tunnel 10.106.0.6 TE-LM-ADMIT:tunnel 10.106.0.6 TE-LM-ADMIT:tunnel 10.106.0.6 TE-LM-ADMIT:tunnel 10.106.0.6 TE-LM-ADMIT:Admission control on link Ethernet4/0/1 [reason TE-LM-ADMIT:tunnel 10.106.0.6 TE-LM-ADMIT:tunnel 10.106.0.6 TE-LM-ADMIT:Admission control on link Ethernet4/0/1 [reason

1_10002:created [total 4] 1_10002: “None” -> “New” 1_10002: “New” -> “Admitting 2nd Path Leg” 1_10002: “Admitting 2nd Path Leg” -> “Path Admitted” has granted Path query for 10.106.0.6 1_10002 (10.112.0.12) 0] 1_10002: “Path Admitted” -> “Admitting 1st Resv Leg” 1_10002: “Admitting 1st Resv Leg” -> “Resv Admitted” has granted Resv query for 10.106.0.6 1_10002 (10.112.0.12) 0]


DB-1659

Debug Commands debug mpls traffic-eng link-management advertisements

debug mpls traffic-eng link-management advertisements To print information about resource advertisements for traffic engineering interfaces, use the debug mpls traffic-eng link-management advertisements command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management advertisements [detail] [acl-number] no debug mpls traffic-eng link-management advertisements [detail] [acl-number]

Syntax Description

detail


acl-number

(Optional) Uses the specified access list to filter the debugging information.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)S


12.1(3)T

This command was integrated into Cisco IOS Release 12.1(3)T. The detail keyword and the acl-number argument were added.

12.0(10)ST


12.2(28)SB


Examples

12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about resource advertisements for traffic engineering interfaces: Router# debug mpls traffic-eng link-management advertisements detail TE-LM-ADV:area isis level-1:IGP announcement:link Et4/0/1:info changed TE-LM-ADV:area isis level-1:IGP msg:link Et4/0/1:includes subnet type (2), described nbrs (1) TE-LM-ADV:area isis level-1:IGP announcement:link Et4/0/1:info changed TE-LM-ADV:area isis level-1:IGP msg:link Et4/0/1:includes subnet type (2), described nbrs (1) TE-LM-ADV:LSA:Flooding manager received message:link information change (Et4/0/1) TE-LM-ADV:area isis level-1:*** Flooding node information *** System Information:: Flooding Protocol: ISIS Header Information:: IGP System ID: 0001.0000.0001.00 MPLS TE Router ID: 10.106.0.6


DB-1660

May 2008

Debug Commands debug mpls traffic-eng link-management advertisements

Flooded Links: 1 Link ID:: 0 Link IP Address: 10.1.0.6 IGP Neighbor: ID 0001.0000.0001.02 Admin. Weight: 10 Physical Bandwidth: 10000 kbits/sec Max Reservable BW: 5000 kbits/sec Downstream:: Reservable Bandwidth[0]: 5000 kbits/sec Reservable Bandwidth[1]: 2000 kbits/sec Reservable Bandwidth[2]: 2000 kbits/sec Reservable Bandwidth[3]: 2000 kbits/sec Reservable Bandwidth[4]: 2000 kbits/sec Reservable Bandwidth[5]: 2000 kbits/sec Reservable Bandwidth[6]: 2000 kbits/sec Attribute Flags: 0x00000000


debug mpls traffic-eng link-management advertisements Field Descriptions

Field

Description

Flooding Protocol

Interior Gateway Protocol (IGB) that is flooding information for this area.

IGP System ID

Identification that IGP flooding uses in this area to identify this node.

MPLS TE Router ID

MPLS traffic engineering router ID.

Flooded Links

Number of links that are flooded in this area.

Link ID

Index of the link that is being described.

Link IP Address

Local IP address of this link.

IGP Neighbor

IGP neighbor on this link.

Admin. Weight

Administrative weight associated with this link.

Physical Bandwidth

Link’s bandwidth capacity (in kbps).

Max Reservable BW

Maximum amount of bandwidth that is currently available for reservation at this priority.

Reservable Bandwidth

Amount of bandwidth that is available for reservation.

Attribute Flags

Attribute flags of the link being flooded.


DB-1661

Debug Commands debug mpls traffic-eng link-management bandwidth-allocation

debug mpls traffic-eng link-management bandwidth-allocation To print detailed information about bandwidth allocation for traffic engineering label-switched paths (LSPs), use the debug mpls traffic-eng link-management bandwidth-allocation command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management bandwidth-allocation [detail] [acl-number] no debug mpls traffic-eng link-management bandwidth-allocation [detail] [acl-number]

Syntax Description

detail


acl-number

(Optional) Uses the specified access list to filter the debugging information. Prints information only for those LSPs that match the access list.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)S


12.1(3)T

This command was integrated into Cisco IOS Release 12.1(3)T. The detail keyword and the acl-number argument were added.

12.0(10)ST


12.2(28)SB


Examples

12.2(33)SRA


12.2SX


In the following example, information is printed about bandwidth allocation for traffic engineering LSPs: Router# debug mpls traffic-eng link-management bandwidth-allocation TE-LM-BW:tunnel Et4/0/1 TE-LM-BW:tunnel TE-LM-BW:tunnel Et4/0/1 TE-LM-BW:tunnel

10.106.0.6 1_10002:requesting Downstream bw hold (3000000 bps [S]) on link 10.106.0.6 1_10002:Downstream bw hold request succeeded 10.106.0.6 1_10002:requesting Downstream bw lock (3000000 bps [S]) on link 10.106.0.6 1_10002:Downstream bw lock request succeeded×_„Rs


DB-1662

May 2008

Debug Commands debug mpls traffic-eng link-management bandwidth-allocation

Related Commands

Command

Description

debug mpls traffic-eng link-management admission-control

Prints information about traffic engineering LSP admission control on traffic engineering interfaces.

debug mpls traffic-eng link-management errors

Prints information about errors encountered during any traffic engineering link management procedure.


DB-1663

Debug Commands debug mpls traffic-eng link-management errors

debug mpls traffic-eng link-management errors To print information about errors encountered during any traffic engineering link management procedure, use the debug mpls traffic-eng link-management errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management errors [detail] no debug mpls traffic-eng link-management errors [detail]

Syntax Description

detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Examples


Modification

12.1(3)T


12.0(10)ST


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about errors encountered during a traffic engineering link management procedure: Router# debug mpls traffic-eng link-management errors detail 00:04:48 TE-LM-ROUTING: link Et1/1/1: neighbor 0010.0000.0012.01: add to IP peer db failed

Related Commands

Command

Description

debug mpls traffic-eng link-management admission-control

Prints information about traffic engineering LSP admission control on traffic engineering interfaces.

debug mpls traffic-eng link-management advertisements

Prints information about resource advertisements for traffic engineering interfaces.

debug mpls traffic-eng link-management bandwidth-allocation

Prints information about bandwidth allocation for traffic engineering LSPs.


DB-1664

May 2008

Debug Commands debug mpls traffic-eng link-management errors

Command

Description

debug mpls traffic-eng link-management events Prints information about traffic engineering link management system events. debug mpls traffic-eng link-management igp-neighbors

Prints information about changes to the link management databases of IGP neighbors.

debug mpls traffic-eng link-management links

Prints information about traffic engineering link management interface events.


DB-1665

Debug Commands debug mpls traffic-eng link-management events

debug mpls traffic-eng link-management events To print information about traffic engineering link management system events, use the debug mpls traffic-eng link-management events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management events [detail] no debug mpls traffic-eng link-management events [detail]

Syntax Description

detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Examples


Modification

12.0(5)S


12.1(3)T

This command was integrated into Cisco IOS Release 12.1(3)T and the detail keyword was added.

12.0(10)ST


12.2(28)SB


12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about traffic engineering link management system events: Router# debug mpls traffic-eng link-management events detail TE-LM-EVENTS:stopping MPLS TE Link Management process TE-LM-EVENTS:MPLS TE Link Management process dying now


DB-1666

May 2008

Debug Commands debug mpls traffic-eng link-management igp-neighbors

debug mpls traffic-eng link-management igp-neighbors To print information about changes to the link management database of Interior Gateway Protocol (IGP) neighbors, use the debug mpls traffic eng link-management igp-neighbors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management igp-neighbors [detail] no debug mpls traffic-eng link-management igp-neighbors [detail]

Syntax Description

detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Examples


Modification

12.0(5)S


12.1(3)T


12.0(10)ST


12.2(28)SB


12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about changes to the link management database of IGP neighbors: Router# debug mpls traffic-eng link-management igp-neighbors detail TE-LM-NBR:link AT0/0.2:neighbor 0001.0000.0002.00:created (isis level-1, 10.42.0.10, Up)[total 2]

Related Commands

Command

Description

debug mpls traffic-eng link-management events

Prints information about traffic engineering-related ISIS events.


DB-1667

Debug Commands debug mpls traffic-eng link-management links

debug mpls traffic-eng link-management links To print information about traffic engineering link management interface events, use the debug mpls traffic-eng link-management links command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management links [detail] no debug mpls traffic-eng link-management links [detail]

Syntax Description

detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Examples


Modification

12.0(5)S


12.1(3)T


12.0(10)ST


12.2(28)SB


12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about traffic engineering link management interface events: Router# debug mpls traffic-eng link-management links detail TE-LM-LINKS:link AT0/0.2:RSVP enabled TE-LM-LINKS:link AT0/0.2:increasing RSVP bandwidth from 0 to 5000000 TE-LM-LINKS:link AT0/0.2:created [total 2] TE-LM-LINKS:Binding MPLS TE LM Admission Control as the RSVP Policy Server on ATM0/0.2 TE-LM-LINKS:Bind attempt succeeded TE-LM-LINKS:link AT0/0.2:LSP tunnels enabled


DB-1668

May 2008

Debug Commands debug mpls traffic-eng link-management preemption

debug mpls traffic-eng link-management preemption To print information about traffic engineering label-switched path (LSP) preemption, use the debug mpls traffic-eng link-management preemption command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management preemption [detail] no debug mpls traffic-eng link-management preemption [detail]

Syntax Description

detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Examples


Modification

12.1(3)T


12.2(28)SB


12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about traffic engineering LSP preemption: Router# debug mpls traffic-eng link-management preemption detail TE-LM-BW:preempting Downstream bandwidth, 1000000, for tunnel 10.106.0.6 2_2 TE-LM-BW:building preemption list to get bandwidth, 1000000, for tunnel 10.106.0.6 2_2 (priority 0) TE-LM-BW:added bandwidth, 3000000, from tunnel 10.106.0.6 1_2 (pri 1) to preemption list TE-LM-BW:preemption list build to get bw, 1000000, succeeded (3000000) TE-LM-BW:preempting bandwidth, 1000000, using plist with 1 tunnels TE-LM-BW:tunnel 10.106.0.6 1_2:being preempted on AT0/0.2 by 10.106.0.6 2_2 TE-LM-BW:preemption of Downstream bandwidth, 1000000, succeeded


DB-1669

Debug Commands debug mpls traffic-eng link-management routing

debug mpls traffic-eng link-management routing To print information about traffic engineering link management routing resolutions that can be performed to help Resource Reservation Protocol (RSVP) interpret explicit route objects, use the debug mpls traffic-eng link-management routing command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng link-management routing [detail] no debug mpls traffic-eng link-management routing [detail]

Syntax Description

detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Examples


Modification

12.0(5)S


12.1(3)T


12.0(10)ST


12.2(28)SB


12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about traffic engineering link management routing resolutions that can be performed to help RSVP interpret explicit route objects: Router# debug mpls traffic-eng link-management routing detail TE-LM-ROUTING:route options to 10.42.0.10:building list (w/ nhop matching) TE-LM-ROUTING:route options to 10.42.0.10:adding {AT0/0.2, 10.42.0.10} TE-LM-ROUTING:route options to 10.42.0.10:completed list has 1 links

Related Commands

Command

Description

debug ip rsvp

Prints information about RSVP signalling events.


DB-1670

May 2008

Debug Commands debug mpls traffic-eng load-balancing

debug mpls traffic-eng load-balancing To print information about unequal cost load balancing over traffic engineering tunnels, use the debug mpls traffic-eng load-balancing command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng load-balancing no debug mpls traffic-eng load-balancing

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)ST


12.1(3)T


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, information is printed about unequal cost load balancing over traffic engineering tunnels: Router# debug mpls traffic-eng load-balancing TE-Load:10.210.0.0/16, 2 routes, loadbalancing based on MPLS TE bandwidth TE-Load:10.200.0.0/16, 2 routes, loadbalancing based on MPLS TE bandwidth


DB-1671

Debug Commands debug mpls traffic-eng lsd-client

debug mpls traffic-eng lsd-client To display the Application Programming Interface (API) messages sent to the Label Switching Database (LSD) from the Traffic Engineering (TE) client, use the debug mpls traffic-eng lsd-client command in privileged EXEC mode. To disable the display of these messages, use the no form of this command. debug mpls traffic-eng lsd-client no debug mpls traffic-eng lsd-client

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


Examples

12.2(33)SRA


12.2(33)SXH


12.2SX


The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and enable TE globally: 00:10:23: TE-LSD-CLIENT: register with LSD OK; conn_id = 23, recov time = 60000 s 00:10:23: TE-LSD-CLIENT: LSD is now up

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and disable TE globally: 00:09:50: TE-LSD-CLIENT: unregister LSD client; result = OK; conn_id 23

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and enable TE on specific interfaces on Cisco 7500 series routers: 00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Ethernet1/0; status = OK 00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Serial2/0; status = OK 00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Serial3/0; status = OK

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and disable TE on specific interfaces on Cisco 7500 series routers: 00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Ethernet1/0; status = OK


DB-1672

May 2008


00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Serial2/0; status = OK 00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Serial3/0; status = OK

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and enable TE on specific interfaces on Cisco 10000 series routers: 00:10:23: TE-LSD-CLIENT: enabled TE LSD client on GigabitEthernet1/0/0; status = OK 00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Serial2/0/0; status = OK 00:10:23: TE-LSD-CLIENT: enabled TE LSD client on Serial3/0/0; status = OK

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and disable TE on specific interfaces on Cisco 10000 series routers: 00:09:50: TE-LSD-CLIENT: disabled TE LSD client on GigabitEthernet1/0/0; status = OK 00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Serial2/0/0; status = OK 00:09:50: TE-LSD-CLIENT: disabled TE LSD client on Serial3/0/0; status = OK

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command, allocate labels on tunnel midpoints, and create tunnel midpoint rewrites on Cisco 7500 series routers: 00:14:04: TE-LSD-CLIENT: label alloc OK; label = 16, conn_id = 23 00:14:04: TE-LSD-CLIENT: Create TE mid rewrite for 10.100.100.100 1 [5], Result: OK 00:14:04: In: Serial3/0, 16 Out: Serial2/0, 3

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command, allocate labels on tunnel midpoints, and create tunnel midpoint rewrites on a Cisco 10000 series router: 00:14:04: TE-LSD-CLIENT: label alloc OK; label = 16, conn_id = 23 00:14:04: TE-LSD-CLIENT: Create TE mid rewrite for 10.100.100.100 1 [5], Result: OK 00:14:04: In: Serial3/0/0, 16 Out: Serial2/0/0, 3

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command, free labels on tunnel midpoints, and delete tunnel midpoints on a Cisco 7500 series router: 00:13:13: TE-LSD-CLIENT: Delete TE mid rewrite for iou-100_t1, Result: OK 00:13:13: In: Serial3/0, 16 Out: Serial2/0, 1 00:13:13: TE-LSD-CLIENT: free label 16 result = OK; conn_id = 23

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command, free labels on tunnel midpoints, and delete tunnel midpoints on a Cisco 10000 series router: 00:13:13: TE-LSD-CLIENT: Delete TE mid rewrite for iou-100_t1, Result: OK 00:13:13: In: Serial3/0/0, 16 Out: Serial2/0/0, 1 00:13:13: TE-LSD-CLIENT: free label 16 result = OK; conn_id = 23

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and create tunnel headend rewrites on a Cisco 7500 series router: 00:09:10: TE-LSD-CLIENT: Create TE he rewrite for iou-100_t1, Result = OK 00:09:10: tun_inst: 7 Out: Serial3/0, 16 Dest: 10.0.0.2 ps_flags: 0x60003

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and create tunnel headend rewrites on a Cisco 10000 series router: 00:09:10: TE-LSD-CLIENT: Create TE he rewrite for iou-100_t1, Result = OK 00:09:10: tun_inst: 7 Out: Serial3/0/0, 16 Dest: 10.0.0.2 ps_flags: 0x60003

The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and delete tunnel headend rewrites on a Cisco 7500 series router: 00:09:15: TE-LSD-CLIENT: Delete TE he rewrite for iou-100_t1, Result: OK 00:09:15: tun_inst: 7 Out: Serial3/0, 16 ps_flags: 0x60003


DB-1673


The following messages are displayed when you issue the debug mpls traffic-eng lsd-client command and delete tunnel headend rewrites on a Cisco 10000 series router: 00:09:15: TE-LSD-CLIENT: Delete TE he rewrite for iou-100_t1, Result: OK 00:09:15: tun_inst: 7 Out: Serial3/0/0, 16 ps_flags: 0x60003

Related Commands

Command

Description








DB-1674

May 2008

Debug Commands debug mpls traffic-eng path

debug mpls traffic-eng path To print information about traffic engineering path calculation, use the debug mpls traffic-eng path command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng path {num | lookup | spf | verify} no debug mpls traffic-eng path {num | lookup | spf | verify}

Syntax Description

num

Prints path calculation information only for the local tunneling interface with unit number num.

lookup

Prints information for path lookups.

spf

Prints information for shortest path first (SPF) calculations.

verify

Prints information for path verifications.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)ST


12.1(3)T


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, information is printed about the calculation of the traffic engineering path: Router# debug mpls traffic-eng path lookup TE-PCALC:Tunnel1000 Path Setup to 10.110.0.10:FULL_PATH TE-PCALC:bw 0, min_bw 0, metric:0 TE-PCALC:setup_pri 0, hold_pri 0 TE-PCALC:affinity_bits 0x0, affinity_mask 0xFFFF TE-PCALC_PATH:create_path_hoplist:ip addr 10.42.0.6 unknown.


DB-1675

Debug Commands debug mpls traffic-eng process-restart

debug mpls traffic-eng process-restart To display information about process restarts for reporting to your technical support representative, use the debug mpls traffic-eng process-restart command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng process-restart no debug mpls traffic-eng process-restart

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SXH


12.2SX


Usage Guidelines

If you report a problem and the show mpls traffic-eng process-restart iprouting displays abnormal results, your technical support representative might ask you to issue the debug mpls traffic-eng process-restart command, then perform an IP routing process restart and capture the output for analysis.

Examples

The following example shows partial output from an IP routing process restart: Router# debug mpls traffic-eng process-restart 02:24:22: 02:24:22: 02:24:22: 02:24:22: 02:24:22: 02:24:22: 02:24:22: 02:24:22: 02:24:22: 02:24:22: 02:24:22:

SM: ---TE ION Process Restart 0x78EF9050: process restart (3) SM: NORM (1) --> AWAIT-CFG (3) TE ION Restart timer started, proc_idx:0 delay:120000 SM: ---TE ION Process Restart 0x78EF9050: process cfg replay start (4) SM: AWAIT-CFG (3) --> CFG (4) TE ION Restart timer started, proc_idx:0 delay:300000 SM: ---TE ION Process Restart 0x78EF9050: reg invoke succeeded (2) SM: CFG (4) --> CFG (4) SM: ---TE ION Process Restart 0x78EF9050: process cfg replay done (5) SM: CFG (4) --> SYNC (5) TE ION Restart timer started, proc_idx:0 delay:900000

The output shows typical process restart information that your technical support representative might request if you report a problem after an IP process restart. The information displayed can vary, depending on the conditions that caused the restart.


DB-1676

May 2008

Debug Commands debug mpls traffic-eng process-restart

Related Commands

Command

Description

show mpls traffic-eng process-restart iprouting

Displays the status of IP routing and MPLS traffic engineering synchronization after an IP routing process restarts.


DB-1677

Debug Commands debug mpls traffic-eng topology change

debug mpls traffic-eng topology change To print information about traffic engineering topology change events, use the debug mpls traffic-eng topology change command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng topology change no debug mpls traffic-eng topology change

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)ST


12.1(3)T


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, information is printed about traffic engineering topology change events: Router# debug mpls traffic-eng topology change TE-PCALC_LSA:NODE_CHANGE_UPDATE isis level-1 link flags:LINK_CHANGE_BW system_id:0001.0000.0001.00, my_ip_address:10.42.0.6 nbr_system_id:0001.0000.0002.00, nbr_ip_address 10.42.0.10


DB-1678

May 2008

Debug Commands debug mpls traffic-eng topology lsa

debug mpls traffic-eng topology lsa To print information about traffic engineering topology link state advertisement (LSA) events, use the debug mpls traffic-eng topology lsa command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng topology lsa no debug mpls traffic-eng topology lsa

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)ST


12.1(3)T


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, information is printed about traffic engineering topology LSA events: Router# debug mpls traffic-eng topology lsa TE-PCALC_LSA:node_lsa_add:Received a LSA:flags 0x1 ! IGP Id:0001.0000.0001.00, MPLS TE Id:10.106.0.6 is VALID has 2 links (frag_id 0) link[0 ]:Nbr IGP Id:0001.0000.0001.02 frag_id 0, Intf Address:0.0.0.0 admin_weight:10, attribute_flags:0x0 link[1 ]:Nbr IGP Id:0001.0000.0002.00 frag_id 0, Intf Address:10.42.0.6, Nbr Intf Address:10.42.0.10 admin_weight:100, attribute_flags:0x0 TE-PCALC_LSA:(isis level-1):Received lsa:


DB-1679

Debug Commands debug mpls traffic-eng topology lsa

IGP Id:0001.0000.0001.00, MPLS TE Id:10.106.0.6 Router Node id 8 link[0 ]:Nbr IGP Id:0001.0000.0002.00, nbr_node_id:9, gen:114 frag_id 0, Intf Address:10.42.0.6, Nbr Intf Address:10.42.0.10 admin_weight:100, attribute_flags:0x0 physical_bw:155520 (kbps), max_reservable_bw:5000 (kbps) allocated_bw reservable_bw allocated_bw reservable_bw ----------------------------------------------bw[0]:0 5000 bw[1]:3000 2000 bw[2]:0 2000 bw[3]:0 2000 bw[4]:0 2000 bw[5]:0 2000 bw[6]:0 2000 bw[7]:0 2000


DB-1680

May 2008

Debug Commands debug mpls traffic-eng tunnels errors

debug mpls traffic-eng tunnels errors To print information about errors encountered during any traffic engineering tunnel management procedure, use the debug mpls traffic-eng tunnels errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng tunnels errors [detail] no debug mpls traffic-eng tunnels errors [detail]

Syntax Description

detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Examples


Modification

12.1(3)T


12.0(10)ST


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about errors encountered during a traffic engineering tunnel management procedure: Router# debug mpls traffic-eng tunnels errors 00:04:14: LSP-TUNNEL-SIG: Tunnel10012[1]: path verification failed (unprotected) [Can’t use link 10.12.4.4 on node 10.0.0.4]


DB-1681

Debug Commands debug mpls traffic-eng tunnels events

debug mpls traffic-eng tunnels events To print information about traffic engineering tunnel management system events, use the debug mpls traffic-eng tunnels events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng tunnels events [detail] no debug mpls traffic-eng tunnels events [detail]

Syntax Description

detail

Defaults


Command Modes

Privileged EXEC

Command History

Release

Examples


Modification

12.0(5)S


12.1(3)T


12.0(10)ST


12.2(28)SB


12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about traffic engineering tunnel management system events: Router# debug mpls traffic-eng tunnels events detail LSP-TUNNEL:received event:interface admin. down [Ethernet4/0/1] LSP-TUNNEL:posting action(s) to all-tunnels: check static LSPs LSP-TUNNEL:scheduling pending actions on all-tunnels LSP-TUNNEL:applying actions to all-tunnels, as follows: check static LSPs


DB-1682

May 2008

Debug Commands debug mpls traffic-eng tunnels labels

debug mpls traffic-eng tunnels labels To print information about Multiprotocol Label Switching (MPLS) label management for traffic engineering tunnels, use the debug mpls traffic-eng tunnels labels command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng tunnels labels [detail] [acl-number] no debug mpls traffic-eng tunnels labels [detail] [acl-number]

Syntax Description

detail


acl-number

(Optional) Uses the specified access list to filter the debugging information. Prints information only about traffic engineering tunnels that match the access list.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)S


12.1(3)T


12.0(10)ST


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, detailed debugging information is printed about MPLS label management for traffic engineering tunnels: Router# debug mpls traffic-eng tunnels labels detail LSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:fabric PROGRAM request LSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:programming label 16 on output interface ATM0/0.2 LSP-TUNNEL-LABELS:descriptor 71FA64:continuing “Program” request LSP-TUNNEL-LABELS:descriptor 71FA64:set “Interface Point Out State” to, allocated LSP-TUNNEL-LABELS:# of resource points held for “default” interfaces:2 LSP-TUNNEL-LABELS:descriptor 71FA64:set “Fabric State” to, enabled LSP-TUNNEL-LABELS:descriptor 71FA64:set “Fabric Kind” to, default (LFIB) LSP-TUNNEL-LABELS:descriptor 71FA64:set “Fabric State” to, set LSP-TUNNEL-LABELS:tunnel 10.106.0.6 1 [2]:fabric PROGRAM reply


DB-1683

Debug Commands debug mpls traffic-eng tunnels labels

To restrict output to information about a single tunnel, you can configure an access list and supply it to the debug command. Configure the access list as follows: Router(config-ext-nacl)# permit udp host scr_address host dst_address eq tun intfc

For example, if tunnel 10012 has destination 10.0.0.11 and source 10.0.0.4, as determined by the show mpls traffic-eng tunnels command, the following access list could be configured and added to the debug command: Router(config-ext-nacl)# permit udp host 10.0.0.4 10.0.0.11 eq 10012


DB-1684

May 2008

Debug Commands debug mpls traffic-eng tunnels reoptimize

debug mpls traffic-eng tunnels reoptimize To print information about traffic engineering tunnel reoptimizations, use the debug mpls traffic-eng tunnels reoptimize command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng tunnels reoptimize [detail] [acl-number] no debug mpls traffic-eng tunnels reoptimize [detail] [acl-number]

Syntax Description

detail


acl-number

(Optional) Uses the specified access list to filter the debugging information. Prints information about only those traffic engineering tunnel reoptimizations that match the access list.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)S


12.1(3)T


12.0(10)ST


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, detailed debugging information is printed about traffic engineering tunnel reoptimizations that match access list number 101: Router# debug mpls traffic-eng tunnels reoptimize detail 101 LSP-TUNNEL-REOPT:Tunnel1 LSP-TUNNEL-REOPT:Tunnel1 LSP-TUNNEL-REOPT:Tunnel1 LSP-TUNNEL-REOPT:Tunnel1 LSP-TUNNEL-REOPT:Tunnel1 LSP-TUNNEL-REOPT:Tunnel1 LSP-TUNNEL-REOPT:Tunnel1 LSP-TUNNEL-REOPT:Tunnel1 LSP-TUNNEL-REOPT:Tunnel1

curr option 2 (0x6175CF8C), activate new option 2 new path:option 2 [10002], weight 20 old path:option 2 [2], weight 110 [10002] set as reopt path option 2 [10002] installing as current [2] removed as current [2] set to delayed clean [10002] removed as reopt [10002] set to current


DB-1685

Debug Commands debug mpls traffic-eng tunnels signalling

debug mpls traffic-eng tunnels signalling To print information about traffic engineering tunnel signalling operations, use the debug mpls traffic-eng tunnels signalling command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng tunnels signalling [detail] [acl-number] no debug mpls traffic-eng tunnels signalling [detail] [acl-number]

Syntax Description

detail


acl-number

(Optional) Uses the specified access list to filter the debugging information. Prints information about only those traffic engineering tunnel signalling operations that match the access list.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)S


12.1(3)T


12.0(10)ST


12.2(28)SB


Examples

12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about traffic engineering tunnel signalling operations that match access list number 101: Router# debug mpls traffic-eng tunnels signalling detail 101 LSP-TUNNEL-SIG:tunnel Tunnel1 [2]:RSVP head-end open LSP-TUNNEL-SIG:tunnel Tunnel1 [2]:received Path NHOP CHANGE LSP-TUNNEL-SIG:Tunnel1 [2]:first hop change:0.0.0.0 --> 10.1.0.10 LSP-TUNNEL-SIG:received ADD RESV request for tunnel 10.106.0.6 1 [2] LSP-TUNNEL-SIG:tunnel 10.106.0.6 1 [2]:path next hop is 10.1.0.10 (Et4/0/1) LSP-TUNNEL-SIG:Tunnel1 [2] notified of new label information LSP-TUNNEL-SIG:sending ADD RESV reply for tunnel 10.106.0.6 1 [2]


DB-1686

May 2008

Debug Commands debug mpls traffic-eng tunnels state

debug mpls traffic-eng tunnels state To print information about state maintenance for traffic engineering tunnels, use the debug mpls traffic-eng tunnels state command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng tunnels state [detail] [acl-number] no debug mpls traffic-eng tunnels state [detail] [acl-number]

Syntax Description

detail


acl-number

(Optional) Uses the specified access list to filter the debugging information. Prints information about state maintenance for traffic engineering tunnels that match the access list.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.0(10)ST


12.0(22)S


12.2(28)SB


12.2(33)SRA


12.2SX


Examples

In the following example, detailed debugging information is printed about state maintenance for traffic engineering tunnels that match access list number 99: Router# debug mpls traffic-eng tunnels state detail 99 LSP-TUNNEL:tunnel 10.106.0.6 1 [2]: “Connected” -> “Disconnected” LSP-TUNNEL:Tunnel1 received event:LSP has gone down LSP-TUNNEL:tunnel 10.106.0.6 1 [2]: “Disconnected” -> “Dead” LSP-TUNNEL-SIG:Tunnel1:changing state from up to down LSP-TUNNEL:tunnel 10.106.0.6 1 [2]: “Dead” -> “Connected”


DB-1687

Debug Commands debug mpls traffic-eng tunnels timers

debug mpls traffic-eng tunnels timers To print information about traffic engineering tunnel timer management, use the debug mpls traffic-eng tunnels timers command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls traffic-eng tunnels timers [detail] [acl-number] no debug mpls traffic-eng tunnels timers [detail] [acl-number]

Syntax Description

detail


acl-number

(Optional) Uses the specified access list to filter the debugging information. Prints information about traffic engineering tunnel timer management that matches the access list.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)S


12.1(3)T


12.0(10)ST


12.2(28)SB


Examples

12.2(33)SRA


12.2SX


In the following example, detailed debugging information is printed about traffic engineering tunnel timer management: Router# debug mpls traffic-eng tunnels timers detail LSP-TUNNEL-TIMER:timer fired for Action Scheduler LSP-TUNNEL-TIMER:timer fired for Tunnel Head Checkup


DB-1688

May 2008

Debug Commands debug mpls vpn ha

debug mpls vpn ha To enable the display of Virtual Private Network (VPN) high availability (HA) debugging information, use the debug mpls vpn ha command in privileged EXEC mode. To disable the display of VPN HA debugging information, use the no form of this command. debug mpls vpn ha no debug mpls vpn ha

Syntax Description


Defaults

VPN HA debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRA


12.2SX


Usage Guidelines

The following example shows sample output from the debug mpls vpn ha command: Router# debug mpls vpn ha VPN HA debugging is on.


DB-1689

Debug Commands debug mpls xtagatm cross-connect

debug mpls xtagatm cross-connect To display requests and responses for establishing and removing cross-connects on the controlled ATM switch, use the debug mpls xtagatm cross-connect command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls xtagatm cross-connect no debug mpls xtagatm cross-connect

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(4)T

This command was updated to reflect the Multiprotocol Label Switching (MPLS) Internet Engineering Task Force (IETF) terminology.

Usage Guidelines

Note

Examples

12.2(33)SRA


12.2SX


This command monitors requests to establish or remove cross-connects from XmplsATM interfaces to the Virtual Switch Interface (VSI) master, as well as the VSI master responses to these requests.

Use this command with care, because it generates output for each cross-connect operation performed by the label switch controller (LSC). In a network configuration with many label virtual circuits (LVCs), the volume of output generated can interfere with system timing and the proper operation of other router functions. Use this command only in situations in which the LVC setup or teardown rate is low.

The following is sample output from the debug mpls xtagatm cross-connect command: Router# debug mpls xtagatm cross-connect XTagATM: cross-conn request; SETUP, userdata 0x17, userbits 0x1, prec 7 0xC0100 (Ctl-If) 1/32 0xC0200 (XTagATM0) 0/32 XTagATM: cross-conn response; DOWN, userdata 0x60CDCB5C, userbits 0x2, result OK 0xC0200 1/37 --> 0xC0300 1/37


DB-1690

May 2008

Debug Commands debug mpls xtagatm cross-connect


Field

Description

XTagATM

The source of the debugging message as an XmplsATM interface.

cross-conn

An indicator that the debugging message pertains to a cross-connect setup or teardown operation.

request

A request from an XmplsATM interface to the VSI master to set up or tear down a cross-connect.

response

Response from the VSI master to an XmplsATM interface that a cross-connect was set up or removed.

SETUP

A request for the setup of a cross-connect.

TEARDOWN

A request for the teardown of a cross-connect.

UP

The cross-connect is established.

DOWN

The cross-connect is not established.

userdata, userbits

Values passed with the request that are returned in the corresponding fields in the matching response.

prec

The precedence for the cross-connect.

result

The status of the completed request.

0xC0100 (Ctl-If) 1/32

Information about the interface: •

One endpoint of the cross-connect is on the interface whose logical interface number is 0xC0100.

•

The interface is the VSI control interface.

•

The virtual path identifier (VPI) value at this endpoint is 1.

•

The virtual channel identifier (VCI) value at this end of the cross-connect is 32.

The type of cross-connect (unidirectional or bidirectional).

0xC0200 (XTagATM0) 0/32

Information about the interface:

->

Related Commands

debug mpls xtagatm cross-connect Field Descriptions

•

The other endpoint of the cross-connect is on the interface whose logical interface number is 0xC0200.

•

The interface is associated with XmplsATM interface 0.

•

The VPI value at this endpoint is 0.

•

The VCI value at this end of the cross-connect is 32.

The response pertains to a unidirectional cross-connect.

Command

Description

show xtagatm cross-connect

Displays information about remotely connected ATM switches.


DB-1691

Debug Commands debug mpls xtagatm errors

debug mpls xtagatm errors To display information about error and abnormal conditions that occur on XmplsATM interfaces, use the debug mpls xtagatm errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls xtagatm errors no debug mpls xtagatm errors

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(4)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug mpls xtagatm errors command to display information about abnormal conditions and events that occur on XmplsATM interfaces.

Examples

The following is sample output from the debug mpls xtagatm errors command: Router# debug mpls xtagatm errors XTagATM VC: XTagATM0 1707 2/352 (ATM1/0 1769 3/915): Cross-connect setup failed NO_RESOURCES

This message indicates a failed attempt to set up a cross-connect for a terminating a virtual circuit (VC) on XmplsATM0. The reason for the failure was a lack of resources on the controlled ATM switch.


DB-1692

May 2008

Debug Commands debug mpls xtagatm events

debug mpls xtagatm events To display information about major events that occur on XmplsATM interfaces, not including events for specific XmplsATM virtual circuits (VCs) and switch cross-connects, use the debug mpls xtagatm events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls xtagatm events no debug mpls xtagatm events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Command

Modification

12.0(5)T


12.2(4)T


12.2(33)SRA


12.2SX


Usage Guidelines

Examples

Use the debug mpls xtagatm events command to monitor major events that occur on XmplsATM interfaces. This command monitors events that pertain only to XmplsATM interfaces as a whole and does not include any events that pertain to individual XmplsATM VCs or individual switch cross-connects. The specific events that are monitored when the debug mpls xtagatm events command is in effect include the following: •

Receiving asynchronous notifications that the VSI master sent through the external ATM application programming interface (ExATM API) to an XmplsATM interface.

•

Resizing of the table that is used to store switch cross-connect information. This table is resized automatically as the number of cross-connects increases.

•

Marking of XmplsATM VCs as stale when an XmplsATM interface shuts down, thereby ensuring that the stale interfaces are refreshed before new XmplsATM VCs can be created on the interface.

The following is sample output from the debug mpls xtagatm events command: Router# debug mpls xtagatm events


DB-1693

Debug Commands debug mpls xtagatm events

XTagATM: XTagATM: XTagATM: XTagATM:

desired cross-connect table size set to 256 ExATM API intf event Up, port 0xA0100 (None) ExATM API intf event Down, port 0xA0100 (None) marking all VCs stale on XTagATM0


debug mpls xtagatm events Field Descriptions

Field

Description

XTagATM

The source of the debugging message.

desired cross-connect table size set to 256

The table of cross-connect information has been set to hold 256 entries. A single cross-connect table is shared among all XmplsATM interfaces. The cross-connect table is automatically resized as the number of cross-connects increases.

ExATM API

The information in the debug output pertains to an asynchronous notification sent by the Virtual Switch Interface (VSI) master to the XmplsATM driver.

event Up/Down

The specific event that was sent by the VSI master to the XmplsATM driver.

port 0xA0100 (None)

The event pertains to the VSI interface whose logical interface number is 0xA0100, and that this logical interface is not bound to an XmplsATM interface.

marking all VCs stale on XTagATM0

All existing XmplsATM VCs on interface XmplsATM0 are marked as stale, and that XmplsATM0 remains down until all of these VCs are refreshed.


DB-1694

May 2008

Debug Commands debug mpls xtagatm vc

debug mpls xtagatm vc To display information about events that affect individual XmplsATM terminating virtual circuits (VCs), use the debug mpls xtagatm vc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpls xtagatm vc no debug mpls xtagatm vc

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(4)T


12.2(33)SRA


12.2SX


Usage Guidelines

Note

Examples

Use the debug mpls xtagatm vc command to display detailed information about all events that affect individual XmplsATM terminating VCs.

Use this command with care, because it results in extensive output when many XmplsATM VCs are set up or torn down. This output can interfere with system timing and normal operation of other router functions. Use the debug mpls xtagatm vc command only when a few XmplsATM VCs are created or removed.

The following is sample output from the debug mpls xtagatm vc command: Router# debug mpls xtagatm vc XTagATM XTagATM XTagATM XTagATM

VC: VC: VC: VC:

XTagATM1 XTagATM1 XTagATM1 XTagATM0

18 18 19 43

0/32 0/32 1/33 0/32

(ATM1/0 (ATM1/0 (ATM1/0 (ATM1/0

0 0/0): Setup, Down 88 1/32): Complete, 0 0/0): Setup, Down 67 1/84): Teardown,

--> UpPend UpPend --> Up --> UpPend Up --> DownPend



DB-1695

Debug Commands debug mpls xtagatm vc

Table 243

debug mpls xtagatm vc Field Descriptions

Field

Description

XTagATM VC

The source of the debugging message.

XTagATM

The particular XmplsATM interface number for the terminating VC.

vcd vpi/vci

The virtual circuit descriptor (VCD) and virtual path identifier/virtual channel identifier (VPI/VCI) values for the terminating VC.

(ctl-if vcd vpi/vci)

The control interface, the VCD, and the VPI and VCI values for the private VC corresponding to the XmplsATM VC on the control interface.

Setup, Complete, Teardown

The name of the event that occurred for the indicated VC.

oldstate -> newstate

The state of the terminating VC before and after the processing of the event.


DB-1696

May 2008

Debug Commands debug mpoa client

debug mpoa client To display Multiprotocol over ATM (MPOA) client debug information, use the debug mpoa client command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpoa client {all | data | egress | general | ingress | keep-alives | platform-specific} [name mpc-name] no debug mpoa client {all | data | egress | general | ingress | keep-alives | platform-specific} [name mpc-name]

Syntax Description

all

Displays debugging information for all MPC activity.

data

Displays debugging information for data plane activity only. This option applies only to routers.

egress

Displays debugging information for egress functionality only.

general

Displays general debugging information only.

ingress

Displays debugging information for ingress functionality only.

keep-alives

Displays debugging information for keep-alive activity only.

platform-specific

Displays debugging information for specific platforms only. This option applies only to the Catalyst 5000 series ATM module.

name mpc-name

(Optional) Specifies the name of the MPC with the specified name.

Defaults

Debugging is turned on for all MPOA Clients (MPCs).

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3


12.2(33)SRA


12.2SX


Examples

The following shows how to turn on debugging for the MPC ip_mpc: ATM# debug mpoa client all name ip_mpc

Related Commands

Command

Description

debug mpoa server

Displays information about the MPOA server.


DB-1697

Debug Commands debug mpoa server

debug mpoa server To display information about the Multiprotocol over ATM (MPOA) server, use the debug mpoa server command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mpoa server [name mps-name] no debug mpoa server [name mps-name]

Syntax Description

name mps-name

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3


12.2(33)SRA


12.2SX


(Optional) Specifies the name of an MPOA server.

Usage Guidelines

The debug mpoa server command optionally limits the output only to the specified MPOA Server (MPS).

Examples

The following turns on debugging only for the MPS named ip_mps: Router# debug mpoa server name ip_mps


DB-1698

May 2008

Debug Commands debug mrcp

debug mrcp To display debugging messages for Media Resource Control Protocol (MRCP) operations, use the debug mrcp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mrcp {all | api | detail | error | pmh | session | socket | state} no debug mrcp {all | api | detail | error | pmh | session | socket | state}

Syntax Description

all

Displays all MRCP debugging messages.

api

Displays messages between the application and the MRCP stack.

detail

Displays detailed MRCP version 2 (MRCP v2) debugging messages.

error

Displays MRCP error messages.

pmh

Displays protocol message handler (PMH) messages.

session

Displays messages about active MRCP sessions.

socket

Displays MRCP v2 socket debugging messages

state

Displays Finite State Machine (FSM) messages.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T

This command was introduced on the Cisco 3640, Cisco 3660, Cisco AS5300, Cisco AS5350, and Cisco AS5400.

12.4(15)T

This command was modified to support MRCP v2. The detail and socket keywords were added.

12.2SX


Examples

The following example shows output from the debug mrcp api command: Router# debug mrcp api

The first four lines show Real Time Streaming Protocol (RTSP) socket commands for Text-To-Speech (TTS) operations: *Apr *Apr *Apr *Apr

17 17 17 17

16:31:16.323:mrcp_add_param:param:Kill-On-Barge-In: 16:31:16.323:mrcp_add_param:param:Speech-Language: 16:31:16.323:mrcp_add_param:param:Logging-Tag: 16:31:16.323:mrcp_add_param:param:Content-Base:

*Apr 17 16:31:16.323:mrcp_create_session:same host/port


DB-1699


*Apr *Apr *Apr *Apr *Apr

17 17 17 17 17

16:31:16.323:mrcp_associate_call 5 10 16:31:16.323:mrcp_associate_call 5 10 16:31:16.323:mrcp_synth_speak 5 16:31:16.323:mrcp_add_param:param:Content-Base: 16:31:16.323:mrcp_recognizer_define_grammar 5

The following lines show RTSP socket commands for Automatic Speech Recognition (ASR) operations: *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr

17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17

16:31:16.323:mrcp_add_param:param:Confidence-Threshold: 16:31:16.323:mrcp_add_param:param:Sensitivity-Level: 16:31:16.323:mrcp_add_param:param:Speed-Vs-Accuracy: 16:31:16.323:mrcp_add_param:param:Dtmf-Interdigit-Timeout: 16:31:16.323:mrcp_add_param:param:Dtmf-Term-Timeout: 16:31:16.323:mrcp_add_param:param:Dtmf-Term-Char: 16:31:16.323:mrcp_add_param:param:No-Input-Timeout: 16:31:16.323:mrcp_add_param:param:Logging-Tag: 16:31:16.327:mrcp_add_param:param:Content-Base: 16:31:16.327:mrcp_add_param:param:Recognizer-Start-Timers: 16:31:16.327:mrcp_recognizer_start 5 16:31:26.715:mrcp_add_param:param:Kill-On-Barge-In: 16:31:26.715:mrcp_add_param:param:Speech-Language: 16:31:26.715:mrcp_add_param:param:Logging-Tag: 16:31:26.715:mrcp_add_param:param:Content-Base: 16:31:26.715:mrcp_synth_speak 5 16:31:30.451:mrcp_destroy_session 5 type:SYNTHESIZER 16:31:30.451:mrcp_destroy_session 5 type:RECOGNIZER

The following examples show output from the debug mrcp error command: Router# debug mrcp error

This output shows an error when the response from the server is incorrect: *May *May

9 20:29:09.936:Response from 10.1.2.58:554 failed 9 20:29:09.936:MRCP/1.0 71 422 COMPLETE

This output shows an error when the RTSP connection to the server fails: *May

9 20:29:09.936:Connecting to 10.1.2.58:554 failed

This output shows an error when the recognize request comes out of sequence: *May

9 20:29:09.936:act_idle_recognize:ignoring old recognize request

The following example shows output from the debug mrcp pmh command: Router# debug mrcp pmh *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr

17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17

16:32:51.777:param:Kill-On-Barge-In: true 16:32:51.777:param:Speech-Language: en-US 16:32:51.777:param:Logging-Tag: 14:14 16:32:51.777:param:Content-Base: http://server-asr/ 16:32:51.777:param:Content-Base: http://server-asr/ 16:32:51.777:param:Confidence-Threshold: 50 16:32:51.781:param:Sensitivity-Level: 50 16:32:51.781:param:Speed-Vs-Accuracy: 50 16:32:51.781:param:Dtmf-Interdigit-Timeout: 10000 16:32:51.781:param:Dtmf-Term-Timeout: 10000 16:32:51.781:param:Dtmf-Term-Char: # 16:32:51.781:param:No-Input-Timeout: 10000 16:32:51.781:param:Logging-Tag: 14:14 16:32:51.781:param:Content-Base: http://server-asr/ 16:32:51.781:param:Recognizer-Start-Timers: false 16:32:51.877:GRAMMAR-CONTENT-HEADER 16:32:51.877:Content-Type:application/grammar+xml


DB-1700

May 2008


Content-Id:[email protected] Content-Length:356 *Apr 17 16:32:51.885:GRAMMAR-CONTENT-HEADER *Apr 17 16:32:51.885:Content-Type:text/uri-list Content-Length:30 *Apr 17 16:32:51.885:Total-Length=365 *Apr 17 16:32:51.885:@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ *Apr 17 16:32:51.885:RECOGNIZE 20 MRCP/1.0 Confidence-Threshold:50 Sensitivity-Level:50 Speed-Vs-Accuracy:50 Dtmf-Interdigit-Timeout:10000 Dtmf-Term-Timeout:10000 Dtmf-Term-Char:# No-Input-Timeout:10000 Logging-Tag:14:14 Content-Base:http://server-asr/ Recognizer-Start-Timers:false *Apr 17 16:32:51.885:Content-Type:text/uri-list Content-Length:30 *Apr 17 16:32:51.885:session:[email protected] *Apr 17 16:32:51.885:@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ *Apr 17 16:32:51.889:SPEECH-MARKUP-TYPE-HEADER *Apr 17 16:32:51.889:Content-Type:application/synthesis+ssml Content-Length:126 *Apr 17 16:32:51.889:Total-Length=313 *Apr 17 16:32:51.889:@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ *Apr 17 16:32:51.889:SPEAK 18 MRCP/1.0 Kill-On-Barge-In:true Speech-Language:en-US Logging-Tag:14:14 Content-Base:http://server-asr/ *Apr 17 16:32:51.889:Content-Type:application/synthesis+ssml Content-Length:126 *Apr 17 16:32:51.889: Who do you want speak to?? Joe, Carl, Alex?. And I am extending the length of the text *Apr 17 16:32:51.889:@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ *Apr Apr *Apr *Apr *Apr *Apr Apr *Apr *Apr *Apr *Apr Apr *Apr *Apr *Apr *Apr Apr

17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17

16:32:51.925:mrcp_pmh_parse_response:Length:28 16:32:51.925:mrcp_pmh_get_request_line:Line:MRCP/1.0 19 200 COMPLETE 16:32:51.925:Request-tag:19 resp-code:200 Status:COMPLETE 16:32:51.925:No Of Properties:0 16:32:51.925:mrcp_process_recog_response: 16:32:51.933:mrcp_pmh_parse_response:Length:31 16:32:51.933:mrcp_pmh_get_request_line:Line:MRCP/1.0 20 200 IN-PROGRESS 16:32:51.933:Request-tag:20 resp-code:200 Status:IN-PROGRESS 16:32:51.933:No Of Properties:0 16:32:51.933:mrcp_process_recog_response: 16:32:53.413:mrcp_pmh_parse_response:Length:31 16:32:53.413:mrcp_pmh_get_request_line:Line:MRCP/1.0 18 200 IN-PROGRESS 16:32:53.413:Request-tag:18 resp-code:200 Status:IN-PROGRESS 16:32:53.413:No Of Properties:0 16:32:53.413:mrcp_process_synth_response: 16:33:01.685:mrcp_pmh_parse_response:Length:100 16:33:01.689:mrcp_pmh_get_event_line:Line:SPEAK-COMPLETE 18 COMPLETE MRCP/1.0


DB-1701


*Apr 17 16:33:01.689:Request-tag:18 resp-code:200 Status:COMPLETE *Apr 17 16:33:01.689:No Of Properties:2 *Apr 17 16:33:01.689:mrcp_process_synth_events: *Apr 17 16:33:01.689: COMPLETION-CAUSE:1 *Apr 17 16:33:01.689:mrcp_send_synth_app_response: *Apr 17 16:33:01.689:mrcp_pmh_parse_response:Length:61 Apr 17 16:33:01.689:mrcp_pmh_get_event_line:Line:START-OF-SPEECH 20 IN-PROGRESS MRCP/1.0 *Apr 17 16:33:01.689:Request-tag:20 resp-code:200 Status:IN-PROGRESS *Apr 17 16:33:01.689:No Of Properties:1 *Apr 17 16:33:01.689:mrcp_process_recog_events: *Apr 17 16:33:02.653:mrcp_pmh_parse_response:Length:815 Apr 17 16:33:02.653:mrcp_pmh_get_event_line:Line:RECOGNITION-COMPLETE 20 COMPLETE MRCP/1.0 *Apr 17 16:33:02.653:Request-tag:20 resp-code:200 Status:COMPLETE *Apr 17 16:33:02.653:No Of Properties:2 *Apr 17 16:33:02.653:mrcp_process_recog_events: *Apr 17 16:33:02.653: COMPLETION-CAUSE:0 *Apr 17 16:33:02.653:mrcp_send_recog_app_response: *Apr 17 16:33:02.661:param:Kill-On-Barge-In: true *Apr 17 16:33:02.661:param:Speech-Language: en-US *Apr 17 16:33:02.661:param:Logging-Tag: 14:14 *Apr 17 16:33:02.661:param:Content-Base: http://server-asr/ *Apr 17 16:33:02.665:SPEECH-MARKUP-TYPE-HEADER *Apr 17 16:33:02.665:Content-Type:application/synthesis+ssml Content-Length:57 *Apr 17 16:33:02.665:Total-Length=243 *Apr 17 16:33:02.665:@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ *Apr 17 16:33:02.665:SPEAK 22 MRCP/1.0 Kill-On-Barge-In:true Speech-Language:en-US Logging-Tag:14:14 Content-Base:http://server-asr/ *Apr 17 16:33:02.665:Content-Type:application/synthesis+ssml Content-Length:57 *Apr 17 16:33:02.665: You have joe mails *Apr 17 16:33:02.665:@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ *Apr Apr *Apr *Apr *Apr *Apr Apr *Apr *Apr *Apr *Apr *Apr

17 17 17 17 17 17 17 17 17 17 17 17

16:33:02.833:mrcp_pmh_parse_response:Length:31 16:33:02.833:mrcp_pmh_get_request_line:Line:MRCP/1.0 22 200 IN-PROGRESS 16:33:02.833:Request-tag:22 resp-code:200 Status:IN-PROGRESS 16:33:02.833:No Of Properties:0 16:33:02.833:mrcp_process_synth_response: 16:33:06.382:mrcp_pmh_parse_response:Length:98 16:33:06.382:mrcp_pmh_get_event_line:Line:SPEAK-COMPLETE 22 COMPLETE MRCP/1.0 16:33:06.382:Request-tag:22 resp-code:200 Status:COMPLETE 16:33:06.382:No Of Properties:2 16:33:06.382:mrcp_process_synth_events: 16:33:06.382: COMPLETION-CAUSE:0 16:33:06.382:mrcp_send_synth_app_response:

The following example shows output from the debug mrcp session command: Router# debug mrcp session *Apr *Apr *Apr *Apr *Apr *Apr *Apr

17 17 17 17 17 17 17

16:34:07.851:mrcp_create_session: 16:34:07.851:mrcp_create_session:New SCB creation 16:34:07.851:mrcp_create_svr_session_url: 16:34:07.851:mrcp_create_session: 16:34:07.851:mrcp_create_session:Already an SCB is created for this call 16:34:07.851:mrcp_process_events:event:LIB_CONNECT SYNTHESIZERCONN-STATUS=0 16:34:07.855:mrcp_process_events:event:SPEAK SYNTHESIZER


DB-1702

May 2008


*Apr 17 16:34:07.855:mrcp_process_events:event:SPEAK defered *Apr 17 16:34:07.855:mrcp_process_events:event:LIB_CONNECT RECOGNIZERCONN-STATUS=0 *Apr 17 16:34:07.855:mrcp_process_events:event:DEFINE_GRAMMAR RECOGNIZER *Apr 17 16:34:07.855:mrcp_process_events:event:DEFINE_GRAMMAR defered *Apr 17 16:34:07.855:mrcp_process_events:event:LIB_CONNECT RECOGNIZERCONN-STATUS=0 *Apr 17 16:34:07.855:mrcp_process_events:event:RECOGNIZE RECOGNIZER *Apr 17 16:34:07.855:mrcp_process_events:event:RECOGNIZE defered *Apr 17 16:34:07.855:mrcp_response_handler:status=RTSPLIB_STATUS_SERVER_CONNECTED *Apr 17 16:34:07.855:mrcp_process_events:event:LIB_CONNECTED SYNTHESIZERCONN-STATUS=4 *Apr 17 16:34:07.947:mrcp_response_handler:status=RTSPLIB_STATUS_RTP_RECORD_SETUP *Apr 17 16:34:07.947:mrcp_process_events:event:RECOG_RTP_SETUP RECOGNIZER *Apr 17 16:34:07.947:mrcp_process_defered_events:event:DEFINE_GRAMMAR *Apr 17 16:34:07.947:mrcp_process_defered_events:event:RECOGNIZECONN-STATUS=2 *Apr 17 16:34:07.971:mrcp_response_handler:status=RTSPLIB_STATUS_RECORD_ASSOCIATED *Apr 17 16:34:07.971:mrcp_response_handler:status=RTSPLIB_STATUS_RTP_PLAY_SETUP *Apr 17 16:34:07.975:mrcp_process_events:event:RECOGNIZER_ASSOCIATED RECOGNIZER *Apr 17 16:34:07.975:mrcp_process_events:event:SYNTH_RTP_SETUP SYNTHESIZER *Apr 17 16:34:07.975:mrcp_process_defered_events:event:SPEAKCONN-STATUS=1 *Apr 17 16:34:07.975:mrcp_response_handler:status=RTSPLIB_STATUS_PLAY_ASSOCIATED *Apr 17 16:34:07.975:mrcp_process_events:event:SYNTHESIZER_ASSOCIATED SYNTHESIZER *Apr 17 16:34:08.007:mrcp_response_handler:status=RTSPLIB_STATUS_RESP_OK *Apr 17 16:34:08.019:mrcp_response_handler:status=RTSPLIB_STATUS_RESP_OK *Apr 17 16:34:08.059:mrcp_response_handler:status=RTSPLIB_STATUS_RESP_OK *Apr 17 16:34:17.611:mrcp_response_handler:status=RTSPLIB_STATUS_RESP_OK *Apr 17 16:34:17.611:mrcp_response_handler:status=RTSPLIB_STATUS_RESP_OK *Apr 17 16:34:17.611:mrcp_process_events:event:SPEECH_COMPLETE SYNTHESIZER *Apr 17 16:34:17.611:mrcp_process_events:event:START_OF_SPEECH RECOGNIZER *Apr 17 16:34:18.575:mrcp_response_handler:status=RTSPLIB_STATUS_RESP_OK *Apr 17 16:34:18.575:mrcp_process_events:event:RECOGNITION_COMPLETE RECOGNIZER *Apr 17 16:34:18.583:mrcp_process_events:event:SPEAK SYNTHESIZER *Apr 17 16:34:18.587:mrcp_response_handler:status=RTSPLIB_STATUS_PLAY_ASSOCIATED *Apr 17 16:34:18.587:mrcp_process_events:event:SYNTHESIZER_ASSOCIATED SYNTHESIZER *Apr 17 16:34:18.763:mrcp_response_handler:status=RTSPLIB_STATUS_RESP_OK *Apr 17 16:34:22.279:mrcp_response_handler:status=RTSPLIB_STATUS_RESP_OK *Apr 17 16:34:22.283:mrcp_process_events:event:SPEECH_COMPLETE SYNTHESIZER *Apr 17 16:34:22.307:mrcp_process_events:event:LIB_DESTROY SYNTHESIZERCONN-STATUS=12 *Apr 17 16:34:22.311:mrcp_process_events:event:LIB_DESTROY RECOGNIZERCONN-STATUS=12 *Apr 17 16:34:22.311:mrcp_response_handler:status=RTSPLIB_STATUS_CLEANUP *Apr 17 16:34:22.315:mrcp_free_fsm: *Apr 17 16:34:22.315:mrcp_free_scb: *Apr 17 16:34:22.315:mrcp_create_session_history:scb=0x62C712F4 *Apr 17 16:34:22.315:mrcp_insert_session_history_record:current=0x62999544, callID=0x12 *Apr 17 16:34:22.315:mrcp_insert_session_history_record:count = 3 *Apr 17 16:34:22.315:mrcp_insert_session_history_record:starting history record deletion_timer of 10 minutes

The following example shows output from the debug mrcp state command: Router# debug mrcp state *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr

17 17 17 17 17 17 17 17

16:35:25.141:mrcp_add_synthesizer_fsm:adding synthesizer fsm 16:35:25.141:mrcp_add_connection_fsm:adding connection fsm 16:35:25.141:mrcp_add_rtpsetup_fsm:adding rtpsetup fsm 16:35:25.145:hash_get: key=7 16:35:25.145:mrcp_add_recognizer_fsm:adding recognizer fsm 16:35:25.145:mrcp_add_connection_fsm:adding connection fsm 16:35:25.145:mrcp_add_rtpsetup_fsm:adding rtpsetup fsm 16:35:25.145:mrcp_fsm_execute:type=SYNTHESIZER

The following lines show the gateway connecting to the TTS server: *Apr 17 16:35:25.145: curr[CONNECT_IDLE] next[CONNECTING] action=610B8FD00 *Apr 17 16:35:25.145:act_idle_libconnect

ev-id[LIB_CONNECT]


DB-1703


*Apr 17 16:35:25.145:mrcp_shortcut_connection_fsm *Apr 17 16:35:25.149:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:25.149: curr[CONNECTING] ev-id[LIB_CONNECT_PENDING] next[CONNECTING] action=610B90F80 *Apr 17 16:35:25.149:act_connecting_libpending *Apr 17 16:35:25.149:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:25.149: curr[CONNECTING] ev-id[LIB_CONNECT] next[CONNECTING] action=610B8D480 *Apr 17 16:35:25.149:act_connectfsm_error *Apr 17 16:35:25.149:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:25.149: curr[CONNECTING] ev-id[LIB_CONNECT]

The following lines show the gateway successfully connected to the TTS server: next[CONNECTING] action=610B8D480 *Apr 17 16:35:25.149:act_connectfsm_error *Apr 17 16:35:25.149:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:25.149: curr[CONNECTING] ev-id[LIB_CONNECTED] next[CONNECTED] action=610B913C0 *Apr 17 16:35:25.149:act_connecting_libconnected *Apr 17 16:35:25.149:act_rtpsetupfsm_libdescribed *Apr 17 16:35:25.237:mrcp_fsm_execute:type=RESOURCE_NONE *Apr 17 16:35:25.237: curr[RTP_IDLE] ev-id[RECOG_RTP_SETUP] next[RTP_RECOG_SETUP_DONE] action=610B94F40 *Apr 17 16:35:25.237:act_idle_recog_rtpsetup *Apr 17 16:35:25.237:mrcp_fsm_execute:type=RECOGNIZER *Apr 17 16:35:25.237: curr[RECOG_IDLE] ev-id[DEFINE_GRAMMAR] next[RECOG_IDLE] action=610B99340 *Apr 17 16:35:25.237:act_idle_define_grammar: *Apr 17 16:35:25.237:hash_add: key=31 *Apr 17 16:35:25.237:mrcp_fsm_execute:type=RECOGNIZER *Apr 17 16:35:25.237: curr[RECOG_IDLE] ev-id[RECOGNIZE] next[RECOG_ASSOCIATING] action=610B98400 *Apr 17 16:35:25.237:act_idle_recognize: *Apr 17 16:35:25.245:mrcp_fsm_execute:type=RECOGNIZER *Apr 17 16:35:25.245: curr[RECOG_ASSOCIATING] ev-id[RECOGNIZER_ASSOCIATED] next[RECOGNIZING] action=610B9AB40 *Apr 17 16:35:25.245:act_associating_recognizer_associated: *Apr 17 16:35:25.249:hash_add: key=32 *Apr 17 16:35:25.249:mrcp_fsm_execute:type=RESOURCE_NONE *Apr 17 16:35:25.249: curr[RTP_IDLE] ev-id[SYNTH_RTP_SETUP] next[RTP_SYNTH_SETUP_DONE] action=610B93D40 *Apr 17 16:35:25.249:act_idle_synth_rtpsetup *Apr 17 16:35:25.249:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:25.249: curr[SYNTH_IDLE] ev-id[SPEAK] next[SYNTH_ASSOCIATING] action=610BA5540 *Apr 17 16:35:25.249:act_idle_speak *Apr 17 16:35:25.249:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:25.249: curr[SYNTH_ASSOCIATING] ev-id[SYNTHESIZER_ASSOCIATED]

The following lines show the TTS server performing speech synthesis: *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr

next[SPEAKING] action=610BA7B40 17 16:35:25.249:act_associating_speak_associated 17 16:35:25.249:hash_add: key=30 17 16:35:25.285:hash_get: key=31 17 16:35:25.285:hash_delete: key=31 17 16:35:25.293:hash_get: key=32 17 16:35:25.293:hash_get: key=30 17 16:35:32.805:hash_get: key=30 17 16:35:32.805:hash_delete: key=30 17 16:35:32.805:mrcp_fsm_execute:type=SYNTHESIZER 17 16:35:32.805: curr[SPEAKING] ev-id[SPEECH_COMPLETE] next[SYNTH_IDLE] action=610BAA680


DB-1704

May 2008


*Apr *Apr *Apr *Apr

17 16:35:32.805:act_speaking_speech_complete 17 16:35:32.809:hash_get: key=32 17 16:35:32.809:mrcp_fsm_execute:type=RECOGNIZER 17 16:35:32.809: curr[RECOGNIZING] ev-id[START_OF_SPEECH] next[RECOGNIZING] action=610B9F3C0 *Apr 17 16:35:32.809:act_recognizing_start_of_speech *Apr 17 16:35:33.781:hash_get: key=32 *Apr 17 16:35:33.781:hash_delete: key=32 *Apr 17 16:35:33.781:mrcp_fsm_execute:type=RECOGNIZER *Apr 17 16:35:33.781: curr[RECOGNIZING] ev-id[RECOGNITION_COMPLETE] next[RECOGNIZED] action=610B9D240 *Apr 17 16:35:33.781:act_recognizing_recognition_complete: *Apr 17 16:35:33.789:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:33.789: curr[SYNTH_IDLE] ev-id[SPEAK] next[SYNTH_ASSOCIATING] action=610BA5540 *Apr 17 16:35:33.789:act_idle_speak *Apr 17 16:35:33.793:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:33.793: curr[SYNTH_ASSOCIATING] ev-id[SYNTHESIZER_ASSOCIATED] next[SPEAKING] action=610BA7B40 *Apr 17 16:35:33.793:act_associating_speak_associated *Apr 17 16:35:33.793:hash_add: key=34 *Apr 17 16:35:33.949:hash_get: key=34 *Apr 17 16:35:37.221:hash_get: key=34 *Apr 17 16:35:37.221:hash_delete: key=34 *Apr 17 16:35:37.221:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:37.221: curr[SPEAKING] ev-id[SPEECH_COMPLETE] next[SYNTH_IDLE] action=610BAA680 *Apr 17 16:35:37.221:act_speaking_speech_complete *Apr 17 16:35:37.245:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:37.249: curr[CONNECTED] ev-id[LIB_DESTROY] next[CONNECTED] action=610B8DD00 *Apr 17 16:35:37.249:act_connected_libdestroy *Apr 17 16:35:37.249:mrcp_fsm_execute:type=SYNTHESIZER *Apr 17 16:35:37.249: curr[CONNECTED] ev-id[LIB_DESTROY] next[CONNECTED] action=610B8DD00 *Apr 17 16:35:37.249:act_connected_libdestroy

The following example shows output from the debug mrcp detail command: Router# debug mrcp detail *Sep 1 21:37:53.652: //68//MRCP:/mrcpv2_allocate_scb: scb=0xC07318C8, root_scb=0x661BDD54 *Sep 1 21:37:53.708: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=FALSE;TotalLength=165 *Sep 1 21:37:53.708: //-1//MRCP:/MRCPV2_ADD_HEADER: TotalLength=87 *Sep 1 21:37:53.708: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=TRUE;TotalLength=535: MRCP/2.0 535 DEFINE-GRAMMAR 1 Channel-Identifier: 0000251844F8ACAD@speechrecog : Speech-Language: en-US Content-Base: http://http-server1/php/ : Content-Type: application/srgs+xml Content-Id: [email protected] Content-Length: 290 :


DB-1705


one two *Sep 1 21:37:53.708: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=FALSE;TotalLength=160 *Sep 1 21:37:53.708: //-1//MRCP:/MRCPV2_ADD_HEADER: TotalLength=82 *Sep 1 21:37:53.708: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=TRUE;TotalLength=499: MRCP/2.0 499 RECOGNIZE 2 Channel-Identifier: 0000251844F8ACAD@speechrecog : Speech-Language: en-US Confidence-Threshold: 0.50 Sensitivity-Level: 0.50 Speed-Vs-Accuracy: 0.50 Dtmf-Interdigit-Timeout: 10000 Dtmf-Term-Timeout: 0 Dtmf-Term-Char: # No-Input-Timeout: 20000 N-Best-List-Length: 1 Logging-Tag: 68:68 Content-Base: http://http-server1/php/ Media-Type: audio/basic Start-Input-Timers: false : Content-Type: text/uri-list Content-Length: 31 : session:[email protected] : MRCP/2.0 80 1 200 COMPLETE Channel-Identifier: 0000251844F8ACAD@speechrecog : MRCP/2.0 83 2 200 IN-PROGRESS Channel-Identifier: 0000251844F8ACAD@speechrecog

*Sep 1 21:37:57.404: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=FALSE;TotalLength=169 *Sep 1 21:37:57.404: //-1//MRCP:/MRCPV2_ADD_HEADER_CR: TotalLength=93 *Sep 1 21:37:57.404: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=TRUE;TotalLength=93: MRCP/2.0 93 START-INPUT-TIMERS 3 Channel-Identifier: 0000251844F8ACAD@speechrecog : MRCP/2.0 80 3 200 COMPLETE Channel-Identifier: 0000251844F8ACAD@speechrecog : MRCP/2.0 148 START-OF-INPUT 2 IN-PROGRESS Channel-Identifier: 0000251844F8ACAD@speechrecog Proxy-Sync-Id: 0F1F813000000148 Input-Type: speech : MRCP/2.0 589 RECOGNITION-COMPLETE 2 COMPLETE Channel-Identifier: 0000251844F8ACAD@speechrecog


DB-1706

May 2008


Proxy-Sync-Id: 0F1F813000000148 Completion-Cause: 000 success Content-Type: application/nlsml+xml Content-Length: 369 one one one *Sep 1 21:37:59.588: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=FALSE;TotalLength=165 *Sep 1 21:37:59.588: //-1//MRCP:/MRCPV2_ADD_HEADER: TotalLength=87 *Sep 1 21:37:59.588: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=TRUE;TotalLength=566: MRCP/2.0 566 DEFINE-GRAMMAR 1 Channel-Identifier: 00001FEC44F8AA93@speechrecog : Speech-Language: en-US Content-Base: http://http-server1/php/ : Content-Type: application/srgs+xml Content-Id: [email protected] Content-Length: 321 : three four one *Sep 1 21:37:59.588: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=FALSE;TotalLength=160 *Sep 1 21:37:59.588: //-1//MRCP:/MRCPV2_ADD_HEADER: TotalLength=82 *Sep 1 21:37:59.588: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=TRUE;TotalLength=499: MRCP/2.0 499 RECOGNIZE 2 Channel-Identifier: 00001FEC44F8AA93@speechrecog : Speech-Language: en-US Confidence-Threshold: 0.50 Sensitivity-Level: 0.50 Speed-Vs-Accuracy: 0.50 Dtmf-Interdigit-Timeout: 10000 Dtmf-Term-Timeout: 0 Dtmf-Term-Char: # No-Input-Timeout: 10000 N-Best-List-Length: 1


DB-1707


Logging-Tag: 68:68 Content-Base: http://http-server1/php/ Media-Type: audio/basic Start-Input-Timers: false : Content-Type: text/uri-list Content-Length: 31 : session:[email protected] : MRCP/2.0 80 1 200 COMPLETE Channel-Identifier: 00001FEC44F8AA93@speechrecog : MRCP/2.0 83 2 200 IN-PROGRESS Channel-Identifier: 00001FEC44F8AA93@speechrecog

*Sep 1 21:38:00.044: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=FALSE;TotalLength=169 *Sep 1 21:38:00.044: //-1//MRCP:/MRCPV2_ADD_HEADER_CR: TotalLength=93 *Sep 1 21:38:00.044: //-1//MRCP:/MRCPV2_ADD_REQUEST_LINE: IsFinal=TRUE;TotalLength=93: MRCP/2.0 93 START-INPUT-TIMERS 3 Channel-Identifier: 00001FEC44F8AA93@speechrecog : MRCP/2.0 80 3 200 COMPLETE Channel-Identifier: 00001FEC44F8AA93@speechrecog : MRCP/2.0 148 START-OF-INPUT 2 IN-PROGRESS Channel-Identifier: 00001FEC44F8AA93@speechrecog Proxy-Sync-Id: 0925248800000011 Input-Type: speech : MRCP/2.0 589 RECOGNITION-COMPLETE 2 COMPLETE Channel-Identifier: 00001FEC44F8AA93@speechrecog Proxy-Sync-Id: 0925248800000011 Completion-Cause: 000 success Content-Type: application/nlsml+xml Content-Length: 369 one one one

The following example shows output from the debug mrcp socket command: Router# debug mrcp socket


DB-1708

May 2008


*Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_tcp_socket_connect: Socket=0,Dest=10.1.2.201:51001 *Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_connect_to_server: SocketConnectStatus[MRCPV2_SOCK_CONNECT_PENDING(2)], SocketId=0, ServerSession=0xC0732278, Dest=10.1.2.201:51001 *Sep 1 21:52:58.392: //-1//MRCP:/mrcpv2_handle_socket_read: Before Execute: Socket=0, SocketStatus=MRCPV2_SOCK_CONNECT_PENDING(2) *Sep 1 21:52:58.392: //-1//MRCP:/mrcpv2_handle_socket_read: After Execute: Socket=0, SocketStatus=MRCPV2_SOCK_CONNECTED(1) *Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send: (Socket:0 Length:87) 600 bytes of data *Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send: Buffer Sent Successfully; fd=0, Sent=87 *Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send: (Socket:0 Length:64) 600 bytes of data *Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send: Buffer Sent Successfully; fd=0, Sent=64 *Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send: (Socket:0 Length:94) 600 bytes of data *Sep 1 21:52:58.392: //74//MRCP:/mrcpv2_partial_socket_send: Buffer Sent Successfully; fd=0, Sent=94

Related Commands

Command

Description

show mrcp client session active

Displays information about active MRCP sessions.

show mrcp client session history

Displays information about past MRCP sessions.

show mrcp client statistics hostname

Displays statistics about MRCP sessions.


DB-1709

Debug Commands debug mspi receive

debug mspi receive Note

Effective with release 12.3(8)T, the debug mspi receive command is replaced by the debug fax mspi command. See the debug fax mspi command for more information. To display debugging messages for the receiving mail Service Provider Interface (MSPI), use the debug mspi receive command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mspi receive no debug mspi receive

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI

This command was introduced on the Cisco AS5300 universal access server.

12.1(5)T


12.2(4)T

This command was implemented on the Cisco 1750 access router.

12.3(8)T

This command was replaced by the debug fax mspi command.

12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug mspi receive command: Router# debug mspi receive Jan 1 ph#in: Jan 1 Jan 1 Jan 1 Jan 1 Jan 1 Jan 1 Jan 1 Jan 1 Jan 1 Dec 31

05:09:33.890: mspi_tel_num_trans: from: Radhika, fax=5271714 ph#dial: 5271714 05:09:33.890: incoming destPat(5271714), matched(7), tag(22) 05:09:33.890: out destPat(5......), tag(20), dgt strip enabled 05:09:33.890: mspi_off_new_rcpt: envlp_to [[email protected]], 30 05:09:33.890: tel_numb_dial: 5271714, subaddr:[], cover page 05:09:39.122: mspi_offramp_rfc822_header: msgType=0 05:09:39.122: envlp_from: [Radhika], 8 05:09:39.122: mspi_off_put_buff: ignore mime type=1, st=CONNECTING, len=0 05:09:39.122: moff_save_buffer: cid=0x1F, mime=9, len=4 05:09:39.122: offramp disabled receiving! 21:09:44.078: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 5271714


DB-1710

May 2008

Debug Commands debug mspi receive

Jan 1 05:09:52.154: Jan 1 05:09:52.154: Jan 1 05:09:52.154: Jan 1 05:09:52.154: offramp rcpt enabled Jan 1 05:09:54.126: Jan 1 05:09:54.134:

Related Commands

mspi_bridge: cid=0x1F, dst cid=0x22, data dir=OFFRAMP, conf dir=DEST mspi_offramp_send_buffer: cid=0x1F, mime=9 buffer with only CR/LF - set buff_len=0 mspi_offramp_send_buffer: cid=0x1F, mime=9 rx BUFF_END_OF_PART, mspi_offramp_send_buffer: cid=0x1F, mime=11 mspi_offramp_send_buffer: cid=0x1F, mime=11

Command

Description

debug mspi send

Displays debugging messages for MSPI send.


DB-1711

Debug Commands debug mspi send

debug mspi send Note

Effective with Cisco IOS Release 12.3(8)T, the debug mspi send command is replaced by the debug fax mspi command. See the debug fax mspi command for more information. To display debugging messages for the sending mail Service Provider Interface (MSPI), use the debug mspi send command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mspi send no debug mspi send

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI

This command was introduced on the Cisco AS5300 universal access server.

12.1(5)T


12.2(4)T

This command was introduced on the Cisco 1750 access router.

12.3(8)T

This command was replaced by the debug fax mspi command.

12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug mspi send command: Router# debug mspi send *Oct 16 08:40:27.515: dir=DEST *Oct 16 08:40:29.143: *Oct 16 08:40:29.147: *Oct 16 08:40:29.147: *Oct 16 08:40:30.147: *Oct 16 08:40:30.147: *Oct 16 08:40:30.147: *Oct 16 08:40:38.995:

mspi_bridge: cid=0x21, dst cid=0x26, data dir=OFFRAMP, conf mspi_setup_req: for cid=0x27 [email protected] [email protected] mspi_chk_connect: cid=0x27, cnt=0, SMTP connected to the server ! mspi_bridge: cid=0x27, dst cid=0x28, data dir=ONRAMP, conf dir=SRC mspi_xmit: cid=0x27, st=CONFERENCED, src_cid=0x28, buf cnt=0


DB-1712

May 2008

Debug Commands debug mspi send

Related Commands

Command

Description

debug mspi receive

Displays debugging messages for MSPI receive.


DB-1713

Debug Commands debug mta receive all

debug mta receive all Note

Effective with release 12.3(8)T, the debug mta receiv all command is replaced by the debug fax mta command. See the debug fax mta command for more information. To show output relating to the activity on the Simple Mail Transfer Protocol (SMTP) server, use the debug mta receive all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mta receive all no debug mta receive all

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T


Examples

12.1(5)T


12.2(4)T


12.2(8)T


12.2(13)T


12.3(8)T

This command was replaced by the debug fax mta command.

12.2(33)SRA


12.2SX


The following example shows the messages exchanged (for example, the handshake) between the e-mail server and the off-ramp gateway: Router# debug mta receive all Jan Jan Jan Jan

1 1 1 1

05:07:41.314: 05:07:43.354: 05:07:45.386: 05:07:47.426:

esmtp_server_work: esmtp_server_work: esmtp_server_work: esmtp_server_work:

calling calling calling calling

helo mail rcpt data


DB-1714

May 2008

Debug Commands debug mta receive all

Jan 1 05:07:49.514: (S)R: 'Content-Type: multipart/mixed; boundary="------------11F7CD9D2EB3E8B8D5627C62"' Jan 1 05:07:49.514: (S)R: '' Jan 1 05:07:49.514: esmtp_server_engine_new_part: Jan 1 05:07:49.514: (S)R: 'Content-Type: text/plain; charset=us-ascii' Jan 1 05:07:49.514: (S)R: 'Content-Transfer-Encoding: 7bit' Jan 1 05:07:49.514: (S)R: '' Jan 1 05:07:49.514: esmtp_server_engine_new_part: Jan 1 05:07:49.514: esmtp_server_work: freeing temp header Jan 1 05:07:49.514: (S)R: 'Content-Type: image/tiff; name="DevTest.8.1610.tif"' Jan 1 05:07:49.514: (S)R: 'Content-Transfer-Encoding: base64' Jan 1 05:07:49.514: (S)R: 'Content-Disposition: inline; filename="DevTest.8.1610.tif"' Jan 1 05:07:49.514: (S)R: '' Jan 1 05:07:49.514: esmtp_server_engine_update_recipient_status: status=6 Jan 1 05:07:49.514: esmtp_server_engine_new_part: Jan 1 05:07:49.518: esmtp_server_work: freeing temp header Jan 1 05:08:03.014: esmtp_server_engine_update_recipient_status: status=7 Jan 1 05:08:04.822: esmtp_server_engine_update_recipient_status: status=6 Jan 1 05:08:33.042: esmtp_server_engine_update_recipient_status: status=7 Jan 1 05:08:34.906: esmtp_server_engine_getline: Unexpected end of file on socket 1 Jan 1 05:08:34.906: esmtp_server_work: error occurred with ctx=0x61FFF710, socket=1

Related Commands

Command

Description

debug mta send all

Displays output for all the on-ramp client connections.


DB-1715

Debug Commands debug mta send all

debug mta send all Note

Effective with release 12.3(8)T, the debug mta send all command is replaced by the debug fax mta command. See the debug fax mta command for more information. To display output for all of the on-ramp client connections, use the debug mta send all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mta send all no debug mta send all

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T


12.2(4)T


12.2(8)T


12.2(13)T


12.3(8)T

This command was replaced by the debug fax mta command.

12.2(33)SRA


12.2SX


Examples

The following example shows the messages exchanged (for example, the handshake) between the e-mail server and the on-ramp gateway: Router# debug mta send all *Oct 16 09:04:13.055: esmtp_client_engine_open: [email protected], [email protected] *Oct 16 09:04:13.055: esmtp_client_engine_add_headers: from_comment= *Oct 16 09:04:13.111: esmtp_client_work: socket 0 attempting to connect to IP address 171.71.154.56 *Oct 16 09:04:13.111: esmtp_client_work: socket 0 readable for first time *Oct 16 09:04:13.135: esmtp_client_work: socket 0 readable for first time


DB-1716

May 2008

Debug Commands debug mta send all

*Oct 16 09:04:13.135: (C)R: 220 madeup.abccompany.com ESMTP Sendmail 8.8.4-Cisco.1/8.6.5 ready at Wed, 27 Sep 2000 11:45:46 -0700 (PDT) *Oct 16 09:04:13.135: (C)S: EHLO mmoip-c.cisco.com *Oct 16 09:04:13.183: (C)R: 250-madeup.abccompany.com Hello [172.22.95.16], pleased to meet you *Oct 16 09:04:13.183: (C)R: 250-EXPN *Oct 16 09:04:13.183: (C)R: 250-VERB

Related Commands

Command

Description

debug mta send rcpt-to

Displays output for a specific on-ramp SMTP client connection during an e-mail transmission.


DB-1717

Debug Commands debug mta send rcpt-to

debug mta send rcpt-to Note

Effective with release 12.3(8)T, the debug mta send rcpt-to command is no longer available in Cisco IOS. To display output for a specific on-ramp Simple Mail Transfer Protocol (SMTP) client connection during an e-mail transmission, use the debug mta send rcpt-to command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mta send rcpt-to string no debug mta send rcpt-to string

Syntax Description

string

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T


12.2(4)T


12.2(8)T


12.2(13)T


12.3(8)T

This command was removed and is no longer available in Cisco IOS software.

Examples

E-mail address.

12.2(33)SRA


12.2SX


The following example shows debugging information displayed when the debug mta send rcpt-to command has been enabled and the SMTP client is sending an e-mail message: Router# debug mta send rcpt-to 5551212 Router# socket 0 attempting to connect to IP address 100.00.00.00 socket 0 readable for first time - let's try to read it R:220 madeup.abc.com ESMTP Sendmail 8.8.4-abc.1/8.6.5 ready at Tue, 6 Apr 1999 13:35:39 -0700 (PDT) S:EHLO mmoip-c.abc.com R:250-quisp.cisco.com Hello [100.00.00.00], pleased to meet you


DB-1718

May 2008

Debug Commands debug mta send rcpt-to

R:250-EXPN R:250-VERB R:250-8BITMIME R:250-SIZE R:250-DSN R:250-ETRN R:250-XUSR R:250 HELP S:MAIL FROM: RET=HDRS R:250 ... Sender ok S:RCPT TO: NOTIFY=SUCCESS ORCPT=rfc822;testing@ R:250 ... Recipient ok R:354 Enter mail, end with "." on a line by itself S:Received:(Cisco Powered Fax System) by mmoip-c.cisco.com for (with Cisco NetWorks); Fri, 17 Oct 1997 14:54:27 +0800 S:To: S:Message-ID: S:Date:Fri, 17 Oct 1997 14:54:27 +0800 S:Subject:mmoip-c subject here S:X-Mailer:IOS (tm) 5300 Software (C5300-IS-M) S:MIME-Version:1.0 S:Content-Type:multipart/mixed; S: boundary="yradnuoB=_000E1997145426826.mmoip-ccisco.com" S:From:"Test User" S:--yradnuoB=_000E1997145426826.mmoip-ccisco.com S:Content-ID: S:--yradnuoB=_000E1997145426826.mmoip-ccisco.com-Sending terminating dot ...(socket=0) S:. R:250 NAA09092 Message accepted for delivery S:QUIT R:221 [email protected] closing connection Freeing SMTP ctx at 0x6121D454 returned from work_routine, context freed

Related Commands

Command

Description

debug mta send all

Displays output for all the on-ramp client connections.


DB-1719

Debug Commands debug mwi relay errors

debug mwi relay errors To debug message waiting indication (MWI) relay errors, use the debug mwi relay errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mwi relay errors no debug mwi relay errors

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


Usage Guidelines

The debug mwi relay errors command provides a debug monitor display of any error messages, when MWI Relay Server (Cisco IOS Telephony Server) is trying to do MWI Relay to extensions on remote Cisco IOS Telephony Service (ITS).

Examples

The following examples show errors when MWI Relay Server tries to do an MWI Relay to extension 7004, but location of 7004 is not known to the MWI Relay Server: Router# debug mwi relay errors mwi-relay error info debugging is on 01:46:48: MWI-APP: mwi_notify_status: No ClientID (7004) registered


DB-1720

May 2008

Debug Commands debug mwi relay errors

Related Commands

Command

Description

debug ephone mwi

Sets MWI debugging for the Cisco IOS Telephony Service router.

debug mwi relay events

Sets MWI relay events debugging for the Cisco IOS Telephony Service router.


DB-1721

Debug Commands debug mwi relay events

debug mwi relay events To set message waiting indication (MWI) relay events debugging, use the debug mwi relay events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug mwi relay events no debug mwi relay events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XT


12.2(8)T


12.2(8)T1


12.2(11)T


12.2SX


Usage Guidelines

The debug mwi relay events command provides a debug monitor display of events, when MWI Relay Server (Cisco IOS Telephony Server) is trying to do MWI Relay to extensions on remote Cisco IOS Telephony Services (ITS).

Examples

The following debugging messages are shown when the MWI Relay server tries to send MWI Information to remote client 7001 and the location of 7001 is known by the MWI Relay Server: Router# debug mwi relay events mwi-relay events info debugging is on 01:45:34: mwi_notify_status: Queued event for mwi_app_queue 01:45:34: MWI-APP: mwi_app_process_event: 01:45:34: MWI-APP: mwi_app_process_event: MWI Event for ClientID(7001)@(1.8.17.22)


DB-1722

May 2008

Debug Commands debug mwi relay events

Related Commands

Command

Description

debug ephone mwi

Sets MWI debugging for the Cisco IOS Telephony Service router.

debug mwi relay errors

Sets MWI relay errors debugging for the Cisco IOS Telephony Service router.


DB-1723

Debug Commands debug ncia circuit

debug ncia circuit To display circuit-related information between the native client interface architecture (NCIA) server and client, use the debug ncia circuit command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ncia circuit [error | event | flow-control | state] no debug ncia circuit [error | event | flow-control | state]

Syntax Description

error

(Optional) Displays the error situation for each circuit.

event

(Optional) Displays the packets received and sent for each circuit.

flow-control

(Optional) Displays the flow control information for each circuit.

state

(Optional) Displays the state changes for each circuit.

Command Modes

Privileged EXEC (#)

Usage Guidelines

NCIA is an architecture developed by Cisco for accessing Systems Network Architecture (SNA) applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones. You cannot enable debugging output for a particular client or particular circuit.

Caution

Examples

Do not enable the debug ncia circuit command during normal operation because this command generates a substantial amount of output messages and could slow down the router.

The following is sample output from the debug ncia circuit error command. In this example, the possible errors are displayed. The first error message indicates that the router is out of memory. The second message indicates that the router has an invalid circuit control block. The third message indicates that the router is out of memory. The remaining messages identify errors related to the finite state machine. Router# debug ncia circuit error NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA:

ncia_circuit_create memory allocation fail ncia_send_ndlc: invalid circuit control block send_ndlc: fail to get buffer for ndlc primitive xxx ncia circuit fsm: Invalid input ncia circuit fsm: Illegal state ncia circuit fsm: Illegal input ncia circuit fsm: Unexpected input ncia circuit fsm: Unknown error rtn code

The following is sample output from the debug ncia circuit event command. In this example, a session startup sequence is displayed. Router# debug ncia circuit event NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_START_DL, Len: 24, tmac: 4000.1060.1000,


DB-1724

May 2008


tsap: 4, csap 8, oid: 8A91E8, tid 0, lfs 16, ws 1 NCIA: create circuit: saddr 4000.1060.1000, ssap 4, daddr 4000.3000.0003, dsap 8 sid: 8B09A8 NCIA: send NDLC_DL_STARTED to client 10.2.20.3 for ckt: 8B09A8 NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_DL_STARTED, Len: 2,4 tmac: 4000.1060.1000, tsap: 4, csap 8, oid: 8A91E8, tid 8B09A8, lfs 16, ws 1 NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8B09A8, FC 0x81 NCIA: send NDLC_XID_FRAME to client 10.2.20.3 for ckt: 8B09A8 NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8A91E8, FC 0xC1 NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 18, sid: 8B09A8, FC 0xC1 NCIA: send NDLC_CONTACT_STN to client 10.2.20.3 for ckt: 8B09A8 NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_CONTACT_STN, Len: 12, sid: 8A91E8, FC 0xC1 NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_STN_CONTACTED, Len: 12, sid: 8B09A8, FC 0xC1 NCIA: send NDLC_INFO_FRAME to client 10.2.20.3 for ckt: 8B09A8 NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_INFO_FRAME, Len: 30, sid: 8A91E8, FC 0xC1


debug ncia circuit event Field Descriptions

Field

Description

IN

Incoming message from client.

OUT

Outgoing message to client.

Ver_Id

NDLC version ID.

MsgType

NDLC message type.

Len

NDLC message length.

tmac

Target MAC.

tsap

Target SAP.

csap

Client SAP.

oid

Origin ID.

tid

Target ID.

lfs

Largest frame size flag.

ws

Window size.

saddr

Source MAC address.

ssap

Source SAP.

daddr

Destination MAC address.

dsap

Destination SAP.

sid

Session ID.

FC

Flow control flag.

In the following messages, an NDLC_START_DL messages is received from a client to start a data-link session: NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_START_DL, Len: 24, tmac: 4000.1060.1000, tsap: 4, csap 8, oid: 8A91E8, tid 0, lfs 16, ws 1 NCIA: create circuit: saddr 4000.1060.1000, ssap 4, daddr 4000.3000.0003, dsap 8 sid: 8B09A8

The next two messages indicate that an NDLC_DL_STARTED message is sent to a client. The server informs the client that a data-the link session is started.


DB-1725


NCIA: send NDLC_DL_STARTED to client 10.2.20.3 for ckt: 8B09A8 NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_DL_STARTED, Len: 2,4 tmac: 4000.1060.1000, tsap: 4, csap 8, oid: 8A91E8, tid 8B09A8, lfs 16, ws 1

In the following two messages, an NDLC_XID_FRAME message is received from a client, and the client starts an XID exchange: NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8B09A8, FC 0x81 NCIA: send NDLC_XID_FRAME to client 10.2.20.3 for ckt: 8B09A8

In the following two messages, an NDLC_XID_FRAME message is sent from a client, and an DLC_XID_FRAME message is received from a client: NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8A91E8, FC 0xC1 NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 18, sid: 8B09A8, FC 0xC1

The next two messages show that an NDLC_CONTACT_STN message is sent to a client: NCIA: send NDLC_CONTACT_STN to client 10.2.20.3 for ckt: 8B09A8 NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_CONTACT_STN, Len: 12, sid: 8A91E8, FC 0xC1

In the following message, an NDLC_STN_CONTACTED message is received from a client. The client informs the server that the station has been contacted. NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_STN_CONTACTED, Len: 12, sid: 8B09A8, FC 0xC1

In the last two messages, an NDLC_INFO_FRAME is sent to a client, and the server sends data to the client: NCIA: send NDLC_INFO_FRAME to client 10.2.20.3 for ckt: 8B09A8 NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_INFO_FRAME, Len: 30, sid: 8A91E8, FC 0xC1

The following is sample output from the debug ncia circuit flow-control command. In this example, the flow control in a session startup sequence is displayed: Router# debug ncia circuit flow-control NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA:

no flow control in NDLC_DL_STARTED frame receive Increment Window Op for circuit 8ADE00 ncia_flow_control_in FC 0x81, IW 1 GP 2 CW 2, Client IW 1 grant client more packet by sending Repeat Window Op ncia_flow_control_out FC: 0xC1, IW 1 GP 2 CW 2, Client IW receive FCA for circuit 8ADE00 receive Increment Window Op for circuit 8ADE00 ncia_flow_control_in FC 0xC1, IW 1 GP 5 CW 3, Client IW 1 grant client more packet by sending Repeat Window Op ncia_flow_control_out FC: 0xC1, IW 1 GP 5 CW 3, Client IW receive FCA for circuit 8ADE00 receive Increment Window Op for circuit 8ADE00 ncia_flow_control_in FC 0xC1, IW 1 GP 9 CW 4, Client IW 1 grant client more packet by sending Repeat Window Op ncia_flow_control_out FC: 0xC1, IW 1 GP 8 CW 4, Client IW reduce ClientGrantPacket by 1 (Granted: 8) receive FCA for circuit 8ADE00 receive Increment Window Op for circuit 8ADE00

GP 0 CW 1 1 GP 2 CW 2

GP 2 CW 2 1 GP 5 CW 3

GP 5 CW 3 1 GP 9 CW 4



DB-1726

May 2008


Table 245

debug ncia circuit flow-control Field Descriptions

Field

Description

IW

Initial window size.

GP

Granted packet number.

CW

Current window size.

The following is sample output from the debug ncia circuit state command. In this example, a session startup sequence is displayed: Router# debug ncia circuit state NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA:

pre-server fsm: event CONN_OPENED pre-server fsm: event NDLC_PRIMITIVES server event: WAN - STDL state: CLSOED ncia server fsm action 32 circuit state: CLOSED -> START_DL_RCVD server event: DLU - TestStn.Rsp state: START_DL_RCVD ncia server fsm action 17 circuit state: START_DL_RCVD -> DL_STARTED_SND pre-server fsm: event NDLC_PRIMITIVES server event: WAN - XID state: DL_STARTED_SND ncia server fsm action 33 circuit state: DL_STARTED_SND -> DL_STARTED_SND server event: DLU - ReqOpnStn.Req state: DL_STARTED_SND ncia server fsm action 33 circuit state: DL_STARTED_SND -> OPENED server event: DLU - Id.Rsp state: OPENED ncia server fsm action 11 circuit state: OPENED -> OPENED pre-server fsm: event NDLC_PRIMITIVES server event: WAN - XID state: OPENED ncia server fsm action 33 circuit state: OPENED -> OPENED server event: DLU - Connect.Req state: OPENED ncia server fsm action 6 circuit state: OPENED -> CONNECT_PENDING pre-server fsm: event NDLC_PRIMITIVES server event: WAN - CONR state: CONNECT_PENDING ncia server fsm action 33 --> CLS_CONNECT_CNF sets NciaClsBusy circuit state: CONNECT_PENDING -> CONNECTED server event: DLU - Flow.Req (START) state: CONNECTED ncia server fsm action 25 --> unset NciaClsBusy circuit state: CONNECTED -> CONNECTED server event: DLU - Data.Rsp state: CONNECTED ncia server fsm action 8 circuit state: CONNECTED -> CONNECTED


debug ncia circuit state Field Descriptions

Field

Description

WAN

Event from WAN (client).


DB-1727


Table 246

Related Commands

debug ncia circuit state Field Descriptions (continued)

Field

Description

DLU

Event from upstream module—dependent logical unit (DLU).

ADMIN

Administrative event.

TIMER

Timer event.

Command

Description


Enables debugging of DLSw+.

debug ncia client

Displays debug information for all NCIA client processing that occurs in the router.

debug ncia server

Displays debug information for the NCIA server and its upstream software modules.


DB-1728

May 2008

Debug Commands debug ncia client

debug ncia client To display debug information for all native client interface architecture (NCIA) client processing that occurs in the router, use the debug ncia client command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ncia client [ip-address | error [ip-address] | event [ip-address] | message [ip-address]] no debug ncia client [ip-address | error [ip-address] | event [ip-address] | message [ip-address]]

Syntax Description

ip-address

(Optional) The remote client IP address.

error

(Optional) Triggers the recording of messages only when errors occur. The current state and event of an NCIA client are normally included in the message. If you do not specify an IP address, the error messages are logged for all active clients.

event

(Optional) Triggers the recording of messages that describe the current state and event—and sometimes the action that just completed—for the NCIA client. If you do not specify an IP address, the messages are logged for all active clients.

message

(Optional) Triggers the recording of messages that contain up to the first 32 bytes of data in a TCP packet sent to or received from an NCIA client. If you do not specify an IP address, the messages are logged for all active clients.

Command Modes

Privileged EXEC (#)

Usage Guidelines

NCIA is an architecture developed by Cisco for accessing Systems Network Architecture (SNA) applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones. Use the debug ncia client error command to see only certain error conditions that occur. Use the debug ncia client event command to determine the sequences of activities that occur while an NCIA client is in different processing states. Use the debug ncia client message command to see only the first 32 bytes of data in a TCP packet sent to or received from an NCIA client. The debug ncia client command can be used in conjunction with the debug ncia server and debug ncia circuit commands to get a complete picture of NCIA activity.

Examples

The following is sample output from the debug ncia client command. Following the example is a description of each sample output message. Router# debug ncia client NCIA: NCIA: NCIA: NCIA: NCIA:

Passive open 10.2.20.123(1088) -> 1973 index for client hash queue is 27 number of element in client hash queue 27 is 1 event PASSIVE_OPEN, state NCIA_CLOSED for client 10.2.20.123 Rcvd msg type NDLC_CAP_XCHG in tcp packet for client 10.2.20.123


DB-1729

Debug Commands debug ncia client

NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA:

First 17 byte of data rcvd: 811200110000000000000400050104080C Sent msg type NDLC_CAP_XCHG in tcp packet to client 10.2.20.123 First 17 byte of data sent: 811200111000000010000400050104080C event CAP_CMD_RCVD, state NCIA_CAP_WAIT, for client 10.2.20.123, cap xchg cmd sent Rcvd msg type NDLC_CAP_XCHG in tcp packet for client 10.2.20.123 First 17 byte of data rcvd: 811200111000000010000000050104080C event CAP_RSP_RCVD, state NCIA_CAP_NEG for client 10.2.20.123

NCIA: NCIA: NCIA: NCIA: NCIA:

Rcvd msg type NDLC_PEER_TEST_REQ in tcp packet for client 10.2.20.123 First 4 byte of data rcvd: 811D0004 event KEEPALIVE_RCVD, state NCIA_OPENED for client 10.2.20.123 Sent msg type NDLC_PEER_TEST_RSP in tcp packet to client 10.2.20.123 First 4 byte of data sent: 811E0004IA

NCIA: NCIA: NCIA: NCIA: NCIA: NCIA:

event TIME_OUT, state NCIA_OPENED, for client 10.2.20.123, keepalive_count = 0 Sent msg type NDLC_PEER_TEST_REQ, in tcp packet to client 10.2.20.123 First 4 byte of data sent: 811D0004 Rcvd msg type NDLC_PEER_TEST_RSP in tcp packet for client 10.2.20.123 First 4 byte of data rcvd: 811E0004 event KEEPALIVE_RSP_RCVD, state NCIA_OPENED for client 10.2.20.123

NCIA: Error, event PASIVE_OPEN, state NCIA_OPENED, for client 10.2.20.123, should not have occurred. NCIA: Error, active_open for pre_client_fsm while client 10.2.20.123 is active or not configured, registered.

Messages in lines 1 through 12 show the events that occur when a client connects to the router (the NCIA server). These messages show a passive_open process. Messages in lines 13 to 17 show the events that occur when a TIME_OUT event is detected by a client PC workstation. The workstation sends an NDLC_PEER_TEST_REQ message to the NCIA server, and the router responds with an NDLC_PEER_TEST_RSP message. Messages in lines 18 to 23 show the events that occur when a TIME_OUT event is detected by the router (the NCIA server). The router sends an NDLC_PEER_TEST_REQ message to the client PC workstation, and the PC responds with an NDLC_PEER_TEST_RSP message. When you use the debug ncia client message command, the messages shown on lines 6, 8, 11, 14, 17, 20, and 22 are output in addition to other messages not shown in this example. When you use the debug ncia client error command, the messages shown on lines 24 and 25 are output in addition to other messages not shown in this example.

Related Commands

Command

Description

debug ncia circuit


debug ncia server

Displays debug information for the NCIA server and its upstream software modules.


DB-1730

May 2008

Debug Commands debug ncia server

debug ncia server To display debug information for the native client interface architecture (NCIA) server and its upstream software modules, use the debug ncia server command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ncia server no debug ncia server

Syntax Description


Command Modes

Privileged EXEC (#)

Usage Guidelines

NCIA is an architecture developed by Cisco for accessing Systems Network Architecture (SNA) applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones. The debug ncia server command displays all Cisco Link Services (CLS) messages between the NCIA server and its upstream modules, such as data-link switching (DLSw) and downstream physical units (DSPUs). Use this command when a problem exists between the NCIA server and other software modules within the router. You cannot enable debugging output for a particular client or particular circuit.

Examples

The following is sample output from the debug ncia server command. In this example, a session startup sequence is displayed. Following the example is a description of each group of sample output messages. Router# debug ncia server NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA: NCIA:

send CLS_TEST_STN_IND to DLU Receive TestStn.Rsp send CLS_ID_STN_IND to DLU Receive ReqOpnStn.Req send CLS_REQ_OPNSTN_CNF to DLU Receive Id.Rsp send CLS_ID_IND to DLU Receive Connect.Req send CLS_CONNECT_CNF to DLU Receive Flow.Req Receive Data.Req send CLS_DATA_IND to DLU send CLS_DISC_IND to DLU Receive Disconnect.Rsp

In the following messages, the client is sending a test message to the host and the test message is received by the host: NCIA: send CLS_TEST_STN_IND to DLU NCIA: Receive TestStn.Rsp


DB-1731

Debug Commands debug ncia server

In the next message, the server is sending an exchange identification (XID) message to the host: NCIA: send CLS_ID_STN_IND to DLU

In the next two messages, the host opens the station and the server responds: NCIA: Receive ReqOpnStn.Req NCIA: send CLS_REQ_OPNSTN_CNF to DLU

In the following two messages, the client is performing an XID exchange with the host: NCIA: Receive Id.Rsp NCIA: send CLS_ID_IND to DLU

In the next group of messages, the host attempts to establish a session with the client: NCIA: Receive Connect.Req NCIA: send CLS_CONNECT_CNF to DLU NCIA: Receive Flow.Req

In the next two messages, the host sends data to the client: NCIA: Receive Data.Req NCIA: send CLS_DATA_IND to DLU

In the last two messages, the client closes the session: NCIA: send CLS_DISC_IND to DLU NCIA: Receive Disconnect.Rsp

Related Commands

Command

Description


Enables debugging of DLSw+.

debig mcoa circuit

Displays circuit-related information between the NCIA server and client.

debug ncia client



DB-1732

May 2008

Debug Commands debug netbios error

debug netbios error To display information about Network Basic Input/Output System (NetBIOS) protocol errors, use the debug netbios error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug netbios error no debug netbios error

Syntax Description


Command Modes

Privileged EXEC (#)

Usage Guidelines

For complete information on the NetBIOS process, use the debug netbios packet command along with the debug netbios error command.

Examples

The following is sample output from the debug netbios error command. This example shows that an illegal packet has been received on the asynchronous interface. Router# debug netbios error Async1 nbf Bad packet

Related Commands

Command

Description

debug netbios-name-cache

Displays name caching activities on a router.

debug netbios packet

Displays general information about NetBIOS packets.


DB-1733

Debug Commands debug netbios packet

debug netbios packet To display general information about Network Basic Input/Output System (NetBIOS) packets, use the debug netbios packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug netbios packet no debug netbios packet

Syntax Description


Command Modes

Privileged EXEC (#)

Usage Guidelines

For complete information on the NetBIOS process, use the debug netbios error command along with the debug netbios packet command.

Examples

The following is sample output from the debug netbios packet and debug netbios error commands. This example shows the Logical Link Control (LLC) header for an asynchronous interface followed by the NetBIOS information. For additional information on the NetBIOS fields, refer to IBM LAN Technical Reference IEEE 802.2. Router# debug netbios packet Async1 (i) U-format UI C_R=0x0 (i) NETBIOS_ADD_NAME_QUERY Resp_correlator= 0x6F 0x0 Src name=CS-NT-1 Async1 (i) U-format UI C_R=0x0 (i) NETBIOS_ADD_GROUP_QUERY Resp_correlator= 0x6F 0x0 Src name=COMMSERVER-WG Async1 (i) U-format UI C_R=0x0 (i) NETBIOS_ADD_NAME_QUERY Resp_correlator= 0x6F 0x0 Src name=CS-NT-1 Ethernet0 (i) U-format UI C_R=0x0 (i) NETBIOS_DATAGRAM Length= 0x2C 0x0 Dest name=COMMSERVER-WG Src name=CS-NT-3

Related Commands

Command

Description

debug netbios error

Displays information about NetBIOS protocol errors.

debug netbios-name-cache

Displays name caching activities on a router.


DB-1734

May 2008

Debug Commands debug netbios-name-cache

debug netbios-name-cache To display name caching activities on a router, use the debug netbios-name-cache command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug netbios-name-cache no debug netbios-name-cache

Syntax Description


Command Modes

Privileged EXEC (#)

Usage Guidelines

Examine the display to diagnose problems in Network Basic Input/Output System (NetBIOS) name caching.

Examples

The following is sample output from the debug netbios-name-cache command: Router# debug netbios-name-cache NETBIOS: L checking name ORINDA, vrn=0 NetBIOS name cache table corrupted at offset 13 NetBIOS name cache table corrupted at later offset, at location 13 NETBIOS: U chk name=ORINDA, addr=1000.4444.5555, idb=TR1, vrn=0, type=1 NETBIOS: U upd name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1 NETBIOS: U add name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1 NETBIOS: U no memory to add cache entry. name=ORINDA,addr=1000.4444.5555 NETBIOS: Invalid structure detected in netbios_name_cache_ager NETBIOS: flushed name=ORINDA, addr=1000.4444.5555 NETBIOS: expired name=ORINDA, addr=1000.4444.5555 NETBIOS: removing entry. name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0 NETBIOS: Tossing ADD_NAME/STATUS/NAME/ADD_GROUP frame NETBIOS: Lookup Failed -- not in cache NETBIOS: Lookup Worked, but split horizon failed NETBIOS: Could not find RIF entry NETBIOS: Cannot duplicate packet in netbios_name_cache_proxy

Note

The sample display is a composite output. Debugging output that you actually see would not necessarily occur in this sequence. Table 247 describes the significant fields shown in the display. Table 247

debug netbios-name-cache Field Descriptions

Field

Description

NETBIOS

NetBIOS name caching debugging output.

L, U

L means lookup; U means update.

addr=1000.4444.5555

MAC address of machine being looked up in NetBIOS name cache.


DB-1735


Table 247

debug netbios-name-cache Field Descriptions (continued)

Field

Description

idb=TR1

Indicates that the name of machine was learned from Token Ring interface number 1; idb is into interface data block.

vrn=0

Packet comes from virtual ring number 0. This packet actually comes from a real Token Ring interface, because virtual ring number 0 is not valid.

type=1

Indicates the way that the router learned about the specified machine. The possible values are as follows: •

1—Learned from traffic

•

2—Learned from a remote peer

•

4—Statically entered via the configuration of the router

With the first line of output, the router declares that it has examined the NetBIOS name cache table for the machine name ORINDA and that the packet that prompted the lookup came from virtual ring 0. In this case, this packet comes from a real interface—virtual ring number 0 is not valid. NETBIOS: L checking name ORINDA, vrn=0

The following two lines indicate that an invalid NetBIOS entry exists and that the corrupted memory was detected. The invalid memory will be removed from the table; no action is needed. NetBIOS name cache table corrupted at offset 13 NetBIOS name cache table corrupted at later offset, at location 13

The following line indicates that the router attempted to check the NetBIOS cache table for the name ORINDA with MAC address 1000.4444.5555. This name was obtained from Token Ring interface 1. The type field indicates that the name was learned from traffic. NETBIOS: U chk name=ORINDA, addr=1000.4444.5555, idb=TR1, vrn=0, type=1

The following line indicates that the NetBIOS name ORINDA is in the name cache table and was updated to the current value: NETBIOS: U upd name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1

The following line indicates that the NetBIOS name ORINDA is not in the table and must be added to the table: NETBIOS: U add name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1

The following line indicates that there was insufficient cache buffer space when the router tried to add this name: NETBIOS: U no memory to add cache entry. name=ORINDA,addr=1000.4444.5555

The following line indicates that the NetBIOS ager detects an invalid memory in the cache. The router clears the entry; no action is needed. NETBIOS: Invalid structure detected in netbios_name_cache_ager

The following line indicates that the entry for ORINDA was flushed from the cache table: NETBIOS: flushed name=ORINDA, addr=1000.4444.5555


DB-1736

May 2008


The following line indicates that the entry for ORINDA timed out and was flushed from the cache table: NETBIOS: expired name=ORINDA, addr=1000.4444.5555

The following line indicates that the router removed the ORINDA entry from its cache table: NETBIOS: removing entry. name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0

The following line indicates that the router discarded a NetBIOS packet of type ADD_NAME, STATUS, NAME_QUERY, or ADD_GROUP. These packets are discarded when multiple copies of one of these packet types are detected during a certain period of time. NETBIOS: Tossing ADD_NAME/STATUS/NAME/ADD_GROUP frame

The following line indicates that the system could not find a NetBIOS name in the cache: NETBIOS: Lookup Failed -- not in cache

The following line indicates that the system found the destination NetBIOS name in the cache, but located on the same ring from which the packet came. The router will drop this packet because the packet should not leave this ring. NETBIOS: Lookup Worked, but split horizon failed

The following line indicates that the system found the NetBIOS name in the cache, but the router could not find the corresponding RIF. The packet will be sent as a broadcast frame. NETBIOS: Could not find RIF entry

The following line indicates that no buffer was available to create a NetBIOS name cache proxy. A proxy will not be created for the packet, which will be forwarded as a broadcast frame. NETBIOS: Cannot duplicate packet in netbios_name_cache_proxy

Related Commands

Command

Description

debug netbios error

Displays information about NetBIOS protocol errors.

debug netbios packet

Displays general information about NetBIOS packets.


DB-1737

Debug Commands debug netconf

debug netconf To enable debugging of network configuration protocol (NETCONF) sessions, use the debug netconf command in privileged EXEC mode. To turn off NETCONF debugging, use the no form of this command. debug netconf {all | error} no debug netconf {all | error}

Syntax Description

all

Enables debugging of NETCONF sessions, including NETCONF errors.

error

Enables debugging of NETCONF errors.

Command Default

NETCONF debugging is not enabled.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(33)SRA


12.4(9)T


12.2SX


12.2(33)SB


Usage Guidelines

The debug netconf command issues debug information only when an operational error has happened. In most situations, the NETCONF notifications sent between the NETCONF Network Manager and the client are sufficient to diagnose most NETCONF problems. To view Extensible Markup Language (XML) parsing errors when using NETCONF over SSHv2, you must also configure the debug cns xml all command.

Examples

The following example shows how to enable debugging of all NETCONF sessions: Router# debug netconf 00:14:03: 00:14:03: 00:14:03: 00:14:03: 00:14:03: 00:14:03: 00:14:03: 00:14:03: 00:14:13:

NETCONF-ERROR: could not find user1 NETCONF-ERROR: could not find tftp://samplelocation/samplefile NETCONF: locking 1 by session 646B7038 NETCONF: locking 2 by session 646B7038 NETCONF: locking 1 by session 646B7038 NETCONF-ERROR: invalid session unlock attempt NETCONF: locking 1 by session 646B7038 NETCONF-ERROR: lock already active NETCONF-ERROR: lock time 1 expired closing session 646B7038


DB-1738

May 2008

Debug Commands debug netconf


Related Commands

debug netconf Field Descriptions

Field

Description

NETCONF-ERROR: could not find user1

NETCONF could not find the specified username.

NETCONF-ERROR: could not find tftp://samplelocation/samplefile

NETCONF could not find the specified file path.

NETCONF: locking 1 by session 646B7038

This user is locking NETCONF.

NETCONF-ERROR: invalid session unlock attempt

Another user is trying to unlock NETCONF without first acquiring the lock.

NETCONF-ERROR: lock already active

Another user is trying to lock NETCONF while it is currently locked.

NETCONF-ERROR: lock time 1 expired closing session 646B7038

A locked NETCONF session has been idle longer than the time configured by the netconf lock-time command. The locked NETCONF session is closed.

Command

Description

clear netconf

Clears NETCONF statistics counters, NETCONF sessions, and frees associated resources and locks.

debug cns xml

Turns on debugging messages related to the CNS XML parser.

netconf lock-time

Specifies the maximum time a NETCONF configuration lock is in place without an intermediate operation.

netconf max-sessions

Specifies the maximum number of concurrent NETCONF sessions allowed.

netconf ssh

Enables NETCONF over SSHv2.

show netconf

Displays NETCONF statistics counters and session information.


DB-1739

Debug Commands debug nextport vsmgr detail

debug nextport vsmgr detail To turn on debugging for NextPort voice services, use the debug nextport vsmgr detail command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug nextport vsmgr detail no debug nextport vsmgr detail

Syntax Description


Defaults


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(2)XB


12.3(4)T


12.3(14)T

T.38 fax relay call statistics were made available to Call Detail Records (CDRs) through Vendor-Specific Attributes (VSAs) and added to the call log.

12.2SX


Usage Guidelines

This command debugs digital signal processor (DSP) message exchanges between applications and the DSP.

Examples

The following examples turn on debugging for NextPort voice services: debug nextport vsmgr detail Command on the Originating Gateway Router# debug nextport vsmgr detail NextPort Voice Service Manager: NP Voice Service Manager Detail debugging is on . . . May 7 21:09:49.135 UTC: vsm(1/2): np_vsmgr_voice_state_change() May 7 21:09:49.195 UTC: vsm(1/2): np_vsmgr_voice_state_change() May 7 21:09:49.291 UTC: vsm(1/2): np_vsmgr_voice_state_change() May 7 21:09:51.191 UTC: vsm(1/2): np_vsmgr_voice_state_change() May 7 21:09:51.331 UTC: vsm(1/2): np_vsmgr_voice_state_change()

-

state state state state state

IDLE IDLE ACTIVE IDLE ACTIVE


DB-1740

May 2008


May 7 21:09:51.803 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF Received May 7 21:09:51.803 UTC: request_id = 0x01, request_type = 0x0F May 7 21:09:51.803 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 4 num_sig_packets 0 num_cn_packets 1 transmit_duration 8FC end_point_detection 0 May 7 21:09:51.803 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 4 num_sig_packets 0 num_cn_packets 1 receive_duration 8FC voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0 May 7 21:09:51.803 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 0 min_playout_delay 0 max_playout_delay 0 clock offset 0 May 7 21:09:51.803 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0 May 7 21:09:53.231 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF Received May 7 21:09:53.231 UTC: request_id = 0x01, request_type = 0x0F May 7 21:09:53.231 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 1E num_sig_packets 0 num_cn_packets 1 transmit_duration E92 end_point_detection 0 May 7 21:09:53.231 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 4 num_sig_packets 0 num_cn_packets 1 receive_duration E92 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0 May 7 21:09:53.231 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 5A min_playout_delay 5A max_playout_delay 5A clock offset 19778906 May 7 21:09:53.231 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0 May 7 21:09:56.055 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF Received May 7 21:09:56.055 UTC: request_id = 0x01, request_type = 0x0F May 7 21:09:56.055 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 23 num_sig_packets 0 num_cn_packets 2 transmit_duration 19A0 end_point_detection BB8 May 7 21:09:56.055 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 8A num_sig_packets 0 num_cn_packets 1 receive_duration 19A0 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 1 May 7 21:09:56.055 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 3C min_playout_delay 3C max_playout_delay 64 clock offset 197788E4 May 7 21:09:56.055 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x1 endpt_det_error 0x0 May 7 21:09:56.855 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLE May 7 21:09:57.907 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVE May 7 21:09:57.907 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 2 timestamp 68137565 fr-entered (20ms) May 7 21:09:57.907 UTC: chan_id [3/1:D] np_vsmgr_fax_relay_link_info_response: May 7 21:10:15.047 UTC: np_fax_relay_t30_decode : Tx Direction May 7 21:10:15.067 UTC: FARELAY_INIT_HS_MOD : 0xC May 7 21:10:51.579 UTC: FAX_RELAY_DATA_PUMP_STATS(1/2) - valid:0x3FFC1F55 state_code:0x0 level:0x18 phase_jitter:0x5 freq_offset:0x0 eqm:0x7FFE jit_depth:0x230 jit_buf_ov:0x0 tx_paks:0x626 rx_pkts:0x5A inv_pkts:0x0 oos_pkts:0x0 hs_mod:0x8 init_hs_mod:0xC tx_pgs:0x1 rx_pgs:0x0 ecm:0x1 nsf_country:0x0 nsf_manuf_len:0x20 nsf_manuf:0031B8EE80C48511DD0D0000DDDD0000DDDD000000000000000022ED00B0A400 encap:0x1 pkt_loss_con:0x0 May 7 21:10:52.463 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLE May 7 21:10:52.463 UTC: vsm(1/2): np_vsmgr_voice_state_change - NULL DSP Interface Handle

debug nextport vsmgr detail Command on the Terminating Gateway Router# debug nextport vsmgr detail NextPort Voice Service Manager: NP Voice Service Manager Detail debugging is on . . Router# May 7 21:09:51.179 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLE May 7 21:09:51.263 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVE May 7 21:09:51.303 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLE


DB-1741


May 7 21:09:51.443 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVE May 7 21:09:51.467 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF Received May 7 21:09:51.467 UTC: request_id = 0x01, request_type = 0x0F May 7 21:09:51.467 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 0 num_sig_packets 0 num_cn_packets 0 transmit_duration 0 end_point_detection 0 May 7 21:09:51.467 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 0 num_sig_packets 0 num_cn_packets 0 receive_duration 0 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0 May 7 21:09:51.467 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 0 min_playout_delay 0 max_playout_delay 0 clock offset 0 May 7 21:09:51.467 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0 May 7 21:09:53.787 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF Received May 7 21:09:53.787 UTC: request_id = 0x01, request_type = 0x0F May 7 21:09:53.787 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets 19 num_sig_packets 0 num_cn_packets 1 transmit_duration 910 end_point_detection 0 May 7 21:09:53.787 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 1F num_sig_packets 0 num_cn_packets 2 receive_duration 910 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0 May 7 21:09:53.787 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 5A min_playout_delay 5A max_playout_delay 5A clock offset 68877C4 May 7 21:09:53.787 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0 May 7 21:09:56.571 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF Received May 7 21:09:56.571 UTC: request_id = 0x01, request_type = 0x0F May 7 21:09:56.571 UTC: VOICE_TRANSMIT_STATS(1/2): num_voice_packets A5 num_sig_packets 0 num_cn_packets 1 transmit_duration 13F6 end_point_detection 0 May 7 21:09:56.571 UTC: VOICE_RECEIVE_STATS(1/2): num_voice_packets 30 num_sig_packets 0 num_cn_packets 2 receive_duration 13F6 voice_receive_duration 7D0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0 May 7 21:09:56.571 UTC: VOICE_PLAYOUT_DELAY_STATS(1/2): curr_playout_delay 64 min_playout_delay 5A max_playout_delay 64 clock offset 68877D4 May 7 21:09:56.571 UTC: VOICE_PLAYOUT_ERROR(1/2): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0 May 7 21:09:56.807 UTC: VOICE_DET_STATUS_CHANGE_NTF(1/2): detector mask: 1 timestamp 791687D5 May 7 21:09:56.855 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLE May 7 21:09:57.911 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVE May 7 21:09:57.911 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 2 timestamp 65325022 fr-entered (20ms) May 7 21:09:57.911 UTC: chan_id [3/1:D (6)] np_vsmgr_fax_relay_link_info_response: May 7 21:10:15.043 UTC: np_fax_relay_t30_decode : Rx Direction May 7 21:10:15.107 UTC: FARELAY_INIT_HS_MOD : 0x8 May 7 21:10:51.376 UTC: FAX_RELAY_DET_STATUS_CHANGE: slot: 1 port: 2 detector mask 0x2 May 7 21:10:51.404 UTC: FAX_RELAY_DATA_PUMP_STATS(1/2) - valid:0x3FFC1F55 state_code:0x1 level:0x18 phase_jitter:0x0 freq_offset:0x0 eqm:0x7FFE jit_depth:0x39E jit_buf_ov:0x0 tx_paks:0x5A rx_pkts:0x626 inv_pkts:0x0 oos_pkts:0x0 hs_mod:0x8 init_hs_mod:0x8 tx_pgs:0x0 rx_pgs:0x1 ecm:0x1 nsf_country:0x0 nsf_manuf_len:0x20 nsf_manuf:0031B8EE80C48511DD0D0000DDDD0000DDDD000000000000000022ED00B0A400 encap:0x1 pkt_loss_con:0x0 May 7 21:10:52.288 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 2 timestamp 65760060 fr-end May 7 21:10:52.304 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLE May 7 21:10:52.388 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state ACTIVE May 7 21:10:52.416 UTC: np_vsmgr_dispatch_voice_rsp(1/2): VOICE_LINK_INFO_RSP_NTF Received May 7 21:10:52.416 UTC: request_id = 0x05, request_type = 0x30 May 7 21:10:52.416 UTC: VOICE_LEVELS_STATS(1/2): tx_power FF7E tx_mean FF7F rx_power FDBD rx_mean FB48 bnl FD81 erl FD acom 1EA tx_act 1 rx_act 0 May 7 21:10:52.440 UTC: vsm(1/2): np_vsmgr_voice_state_change() - state IDLE May 7 21:10:52.440 UTC: vsm(1/2): np_vsmgr_voice_state_change - NULL DSP Interface Handle


DB-1742

May 2008


Related Commands

Command

Description

debug dspapi detail

Displays details of the DSP API message events with debugging enabled.

voicecap entry

Creates a voicecap on NextPort platforms.

voicecap configure

Applies a voicecap on NextPort platforms.


DB-1743

Debug Commands debug nhrp condition

debug nhrp condition To enable Next Hop Resolution Protocol (NHRP) conditional debugging, use the debug nhrp condition command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug nhrp condition {[peer {nbma | tunnel} ip-address] [interface {tunnel number}] [vrf vrf-name]} no debug nhrp condition {[peer {nbma | tunnel} ip-address] [interface {tunnel number}] [vrf vrf-name]}

Syntax Description

peer

(Optional) Specifies an NHRP peer.

nbma

(Optional) Specifies mapping nonbroadcast access (NBMA).

tunnel

(Optional) Specifies a tunnel.

ip-address

(Optional) Specifies the IP address for the NHRP peer.

interface

(Optional) Displays NHRP information based on a specific interface.

tunnel number

(Optional) Specifies tunnel address for NHRP peer.

vrf vrf-name

(Optional) Specifies debugging information for sessions related to the specified virtual routing forwarding (VRF) configuration.

Command Default

Conditional NHRP debugging is not enabled.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(9)T


12.2SX


Examples

The following example shows how to enable conditional NHRP debugging for a specific tunnel: Router# debug nhrp condition peer tunnel 192.0.2.1

Related Commands

Command

Description

debug dmvpn

Displays DMVPN session debugging information.

debug nhrp error

Displays NHRP error level debugging information.


DB-1744

May 2008

Debug Commands debug nhrp error

debug nhrp error To display Next Hop Resolution Protocol (NHRP) error level debugging information, use the debug nhrp error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug nhrp error no debug nhrp error

Syntax Description


Command Default

Error level NHRP debugging is not enabled.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(9)T


12.2SX


Examples

The following example shows how to enable error level debugging for NHRP: Router# debug nhrp error NHRP errors debugging is on

Related Commands

Command

Description

debug dmvpn

Displays DMVPN session debugging information.

debug nhrp condition

Enables NHRP conditional debugging.


DB-1745

Debug Commands debug nhrp extension

debug nhrp extension To display the extensions portion of a NHRP packet, use the debug nhrp extension privileged EXEC command. The no form of this command disables debugging output. debug nhrp extension no debug nhrp extension

Syntax Description


Examples

The following is sample output from the debug nhrp extension command: Router# debug nhrp extension NHRP extension processing debugging is on Router# Forward Transit NHS Record Extension(4): (C-1) code: no error(0) prefix: 0, mtu: 9180, hd_time: 7200 addr_len: 20(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0 client NBMA: 47.0091810000000002ba08e101.525354555354.01 client protocol: 135.206.58.54 Reverse Transit NHS Record Extension(5): Responder Address Extension(3): (C) code: no error(0) prefix: 0, mtu: 9180, hd_time: 7200 addr_len: 20(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0 client NBMA: 47.0091810000000002ba08e101.525354555355.01 client protocol: 135.206.58.55 Forward Transit NHS Record Extension(4): (C-1) code: no error(0) prefix: 0, mtu: 9180, hd_time: 7200 addr_len: 20(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0 client NBMA: 47.0091810000000002ba08e101.525354555354.01 client protocol: 135.206.58.54 Reverse Transit NHS Record Extension(5): Responder Address Extension(3): Forward Transit NHS Record Extension(4): Reverse Transit NHS Record Extension(5):


DB-1746

May 2008

Debug Commands debug nhrp options

debug nhrp options To display information about NHRP option processing, use the debug nhrp options privileged EXEC command. The no form of this command disables debugging output. debug nhrp options no debug nhrp options

Syntax Description


Usage Guidelines

Use this command to show you whether there are problems or error situations with NHRP option processing (for example, unknown options).

Examples

The following is sample output from the debug nhrp options command: Router# debug nhrp options NHRP-OPT: MASK 4 NHRP-OPT-MASK: FFFFFFFF NHRP-OPT: NETID 4 NHRP-OPT: RESPONDER 4 NHRP-OPT: RECORD 0 NHRP-OPT: RRECORD 0


Related Commands

debug nhrp options Field Descriptions

Field

Descriptions

NHRP-OPT

NHRP options debugging output.

MASK 4

Number of bytes of information in the destination prefix option.

NHRP-OPT-MASK

Contents of the destination prefix option.

NETID

Number of bytes of information in the subnetwork identifier option.

RESPONDER

Number of bytes of information in the responder address option.

RECORD

Forward record option.

RRECORD

Reverse record option.

Command

Description

debug nhrp

Displays information about NHRP activity.

debug nhrp packet

Displays a dump of NHRP packets.


DB-1747

Debug Commands debug nhrp packet

debug nhrp packet To display a dump of NHRP packets, use the debug nhrp packet privileged EXEC command. The no form of this command disables debugging output. debug nhrp packet no debug nhrp packet

Syntax Description


Examples

The following is sample output from the debug nhrp packet command: Router# debug nhrp packet NHRP activity debugging is on Router# NHRP: Send Purge Request via ATM3/0.1, packet size: 72 src: 135.206.58.55, dst: 135.206.58.56 (F) afn: NSAP(3), type: IP(800), hop: 255, ver: 1 shtl: 20(NSAP), sstl: 0(NSAP) (M) flags: "reply required", reqid: 2 src NBMA: 47.0091810000000002ba08e101.525354555355.01 src protocol: 135.206.58.55, dst protocol: 135.206.58.56 (C-1) code: no error(0) prefix: 0, mtu: 9180, hd_time: 0 addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0 client protocol: 135.206.58.130 NHRP: Receive Purge Reply via ATM3/0.1, packet size: 72 (F) afn: NSAP(3), type: IP(800), hop: 254, ver: 1 shtl: 20(NSAP), sstl: 0(NSAP) (M) flags: "reply required", reqid: 2 src NBMA: 47.0091810000000002ba08e101.525354555355.01 src protocol: 135.206.58.55, dst protocol: 135.206.58.56 (C-1) code: no error(0) prefix: 0, mtu: 9180, hd_time: 0 addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 4, pref: 0 client protocol: 135.206.58.130


DB-1748

May 2008

Debug Commands debug nhrp rate

debug nhrp rate To display information about NHRP traffic rate limits, use the debug nhrp rate privileged EXEC command. The no form of this command disables debugging output. debug nhrp rate no debug nhrp rate

Syntax Description


Usage Guidelines

Use this command to verify that the traffic is consistent with the setting of the NHRP commands (such as ip nhrp use and ip max-send commands).

Examples

The following is sample output from the debug nhrp rate command: Router# debug nhrp rate NHRP-RATE: NHRP-RATE: NHRP-RATE: NHRP-RATE:

Sending initial request Retransmitting request (retrans ivl 2) Retransmitting request (retrans ivl 4) Ethernet1: Used 3


Related Commands

debug nhrp rate Field Descriptions

Field

Descriptions

NHRP-RATE

NHRP rate debugging output.

Sending initial request

First time an attempt was made to send an NHRP packet to a particular destination.

Retransmitting request

Indicates that the NHRP packet was re-sent, and shows the time interval (in seconds) to wait before the NHRP packet is re-sent again.

Ethernet1:

Interface over which the NHRP packet was sent.

Used 3

Number of packets sent out of the default maximum five (in this case, three were sent).

Command

Description

debug nhrp

Displays information about NHRP activity.

debug nhrp options

Displays information about NHRP option processing


DB-1749

Debug Commands debug nhrp

debug nhrp To display information about Next Hop Resolution Protocol (NHRP) activity, use the debug nhrp privileged EXEC command. The no form of this command disables debugging output. debug nhrp no debug nhrp

Syntax Description


Usage Guidelines

Use this command when some nodes on a TCP/IP or IPX network are not responding. Output from the command shows whether the router is sending or receiving NHRP packets.

Examples

The following is sample output from the debug nhrp command: Router# debug nhrp NHRP: Cache update 172.19.145.57 None NHRP: Sent request src 172.19.145.56 dst 255.255.255.255 NHRP M: id 0 src 172.19.145.56 dst 172.19.145.57 NHRP: Encapsulation succeeded. MAC addr ffff.ffff.ffff. NHRP: O 86 bytes out Ethernet1 dest 255.255.255.255 NHRP: Recv reply Size 64 NHRP M: id 0 src 172.19.145.56 dst 172.19.145.57 NHRP: Cache update 172.19.145.57 0000.0c14.59d3.


debug nhrp Field Descriptions

Field

Descriptions

NHRP and NHRP M

NHRP debugging output and mandatory header debugging output.

Cache update

NHRP cache is being revised.

Sent request src

NHRP request packet was sent from the specified source address. NHRP packet was sent to the specified destination address.

dst id

Sequence number of the packet.

src

Sequence number of the source address.

dst

Sequence number of the destination address.

Encapsulation succeeded.

NHRP packet was encapsulated.

MAC addr

Link-layer address used as the destination address for the NHRP packet.


DB-1750

May 2008

Debug Commands debug nhrp

Table 251

debug nhrp Field Descriptions (continued)

Field

Descriptions

O 86 bytes out

Size of the NHRP packet (in this case, the output was 86 bytes). Interface that the packet was sent out on, and the network-layer destination address.

Ethernet1 dest Recv reply Size

Related Commands

Indicates receipt of an NHRP reply packet and the size of the packet excluding the link-layer header.

Command

Description

debug nhrp options

Displays information about NHRP option processing.

debug nhrp packet

Displays a dump of NHRP packets.


DB-1751

Debug Commands debug ntp

debug ntp To display debugging messages for Network Time Protocol (NTP) features, use the debug ntp command. To disable debugging output, use the no form of this command. debug ntp {adjust | authentication | events | loopfilter | packets | params | refclock | select | sync | validity} no debug ntp {adjust | authentication | events | loopfilter | packets | params | refclock | select | sync | validity}

Syntax Description

adjust

Displays debugging information on NTP clock adjustments.

authentication

Displays debugging information on NTP authentication.

events

Displays debugging information on NTP events.

loopfilter

Displays debugging information on NTP loop filters.

packets

Displays debugging information on NTP packets.

params

Displays debugging information on NTP clock parameters.

refclock

Displays debugging information on NTP reference clocks.

select

Displays debugging information on NTP clock selection.

sync

Displays debugging information on NTP clock synchronization.

validity

Displays debugging information on NTP peer clock validity.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.02 T

This command was introduced in a release prior to Cisco IOS Release 12.1.

Related Commands

12.2(33)SRA


12.2SX


Command

Description

ntp refclock

Configures an external clock source for use with NTP services.


DB-1752

May 2008

Debug Commands debug oam

debug oam To display operation and maintenance (OAM) events, use the debug oam command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug oam no debug oam

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug oam command: Router# debug oam 4/0(O): VCD:0x0 DM:0x300 *OAM Cell* Length:0x39 0000 0300 0070 007A 0018 0100 0000 05FF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF FF6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A00 0000


debug oam Field Descriptions

Field

Description

0000

Virtual circuit designator (VCD) Special OAM indicator.

0300

Descriptor MODE bits for the ATM Interface Processor (AIP).

0

GFC (4 bits).

07

Virtual path identifier (VPI) (8 bits).

0007

Virtual channel identifier (VCI )(16 bits).

A

Payload type field (PTI) (4 bits).

00

Header Error Correction (8 bits).

1

OAM Fault mangement cell (4 bits).

8

OAM LOOPBACK indicator (4 bits).

01

Loopback indicator value, always 1 (8 bits).

00000005

Loopback unique ID, sequence number (32 bits).

FF6A

Fs and 6A required in the remaining cell, per UNI3.0.


DB-1753

Debug Commands debug oer api

debug oer api To display Optimized Edge Routing (OER) application interface debugging information, use the debug oer api command in privileged EXEC mode. To stop the display of OER application interface debugging information, use the no form of this command. debug oer api [detail] no debug oer api

Syntax Description

detail

Command Default

Detailed OER application interface debugging messages are not displayed.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(15)T


12.2SX


Usage Guidelines

Caution

Examples

(Optional) Displays detailed application interface debugging information.

The debug oer api command is used to display messages about any configured OER application interface providers or host devices. The OER application interface defines the mode of communication and messaging between applications and the network for the purpose of optimizing the traffic associated with the applications. A provider is defined as an entity outside the network in which the router configured as an OER master controller exists, for example, an ISP, or a branch office of the same company. The provider has one or more host devices running one or more applications that use the OER application interface to communicate with an OER master controller. A provider must be registered with an OER master controller before an application on a host device can interface with OER. Use the api provider command to register the provider, and use the host-address command to configure a host device. After registration, a host device in the provider network can initiate a session with an OER master controller. The application interface provides an automated method for networks to be aware of applications and provides application-aware performance routing.

When the detail keyword is entered, the amount of detailed output to be displayed can utilize a considerable amount of system resources. Use the detail keyword with caution in a production network.

The following example enables the display of OER application interface debugging messages and the output shows that an OER policy failed due to a prefix that is not found: Router# debug oer api


DB-1754

May 2008

Debug Commands debug oer api

OER api debugging is on *May 26 01:04:07.278: OER session id 1, requies2 *May 26 01:04:07.278: OER *May 26 01:04:07.278: OER SrcMask 0.0.0.0 *May 26 01:04:07.278: OER Sport_max 0 Dport_mi0 *May 26 01:04:07.278: OER *May 26 01:04:07.278: OER *May 26 01:04:07.278: OER request id 22, sequence0 *May 26 01:04:07.278: OER

API: Data set id received 5, data set len 9, host ip 10.3.3.3, API: Received get current policy, session id 1 request id 22 API: Recvd Appl with Prot 256 DSCP 0 SrcPrefix 0.0.0.0/0 API:

DstPrefix 10.2.0.0/24 DstMask 255.255.255.0 Sport_min 0

API: get prefix policy failed - prefix not found API: Get curr policy cmd received. rc 0 API: Received send status response, status 0, session id 1, API: rc for data set 0

Table 253 describes the significant fields shown in the display. The content of the debugging messages depends on the commands that are subsequently entered at the router prompt. Table 253

Related Commands

debug oer api Field Descriptions

Field

Description

OER api debugging is on

Shows that application interface debugging is enabled.

OER API

Displays an OER application interface message.

Command

Description

api provider

Registers an application interface provider with an OER master controller and enters OER master controller application interface provider configuration mode.

host-address

Configures information about a host device used by an application interface provider to communicate with an OER master controller.

oer

Enables an OER process and configures a router as an OER border router or as an OER master controller.

show oer api provider

Displays information about application interface providers registered with OER.


DB-1755

Debug Commands debug oer api client

debug oer api client To display Optimized Edge Routing (OER) application programming interface (API) client debugging information for master controller and border router communication, use the debug oer api client command in privileged EXEC mode. To stop the display of OER debugging information, use the no form of this command. debug oer api client [detail] no debug oer api client [detail]

Syntax Description

detail

Command Default

No debugging messages are enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(6)T


12.2(33)SRB


12.2SX


(Optional) Displays detailed information.

Usage Guidelines

The debug oer api client command can be entered on a master controller. This command is used to display messages about a configured OER API client. When the detail keyword is entered, the amount of detailed output to be displayed can utilize a considerable amount of system resources. Use the detail keyword with caution in a production network.

Examples

The following example enables the display of OER API client debugging messages: Router# debug oer api client API Client debugging enabled

Related Commands

Command

Description

oer



DB-1756

May 2008

Debug Commands debug oer border active-probe

debug oer border active-probe To display debugging information for active probes configured on the local border router, use the debug oer border active-probe command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command. debug oer border active-probe no debug oer border active-probe

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer border active-probe command is entered on a master controller. This command is used to display the status and results of active probes that are configured on the local border router.

Examples

The following example enables the display of active-probe debug information on a border router: Router# debug oer border active-probe *May 4 23:47:45.633: OER BR ACTIVE PROBE: Attempting to retrieve Probe Statistics. probeType = echo, probeTarget = 10.1.5.1, probeTargetPort = 0 probeSource = Default, probeSourcePort = 0, probeNextHop = Default probeIfIndex = 13 *May 4 23:47:45.633: OER BR ACTIVE PROBE: Completed retrieving Probe Statistics. probeType = echo, probeTarget = 10.1.5.1, probeTargetPort = 0 probeSource = Default, probeSourcePort = 0, probeNextHop = 10.30.30.2 probeIfIndex = 13, SAA index = 15 *May 4 23:47:45.633: OER BR ACTIVE PROBE: Completions 11, Sum of rtt 172, Max rtt 36, Min rtt 12 *May 4 23:47:45.693: OER BR ACTIVE PROBE: Attempting to retrieve Probe Statistics. probeType = echo, probeTarget = 10.1.4.1, probeTargetPort = 0 probeSource = Default, probeSourcePort = 0, probeNextHop = Default


DB-1757

Debug Commands debug oer border active-probe

probeIfIndex = 13 *May 4 23:47:45.693: OER BR ACTIVE PROBE: Completed retrieving Probe Statistics. probeType = echo, probeTarget = 10.1.4.1, probeTargetPort = 0 probeSource = Default, probeSourcePort = 0, probeNextHop = 10.30.30.2 probeIfIndex = 13, SAA index = 14


Related Commands

debug oer border active-probe Field Descriptions

Field

Description

OER BR ACTIVE PROBE:

Indicates debugging information for OER active probes on a border router.

Statistics

The heading for OER active probe statistics.

probeType

The active probe type. The active probe types that can be displayed are ICMP, TCP, and UDP.

probeTarget

The target IP address of the active probe.

probeTargetPort

The target port of the active probe.

probeSource

The source IP address of the active probe. Default is displayed for a locally generated active probe.

probeSourcePort

The source port of the active probe.

probeNextHop

The next hop for the active probe.

probeIfIndex

The active probe source interface index.

SAA index

The IP SLAs collection index number.

Command

Description

oer



DB-1758

May 2008

Debug Commands debug oer border learn

debug oer border learn To display debugging information about learned prefixes on the local border router, use the debug oer border learn command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command. debug oer border learn [top number] no debug oer border learn [top number]

Syntax Description

top number

Command Default


Command Modes

Privileged EXEC

Command History

Release

(Optional) Displays debugging information about the top delay or top throughput prefixes. The number of top delay or throughput prefixes can be specified. The range of prefixes that can be specified is a number from 1 to 65535.

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer border learn command is entered on a border router. This command is used to display debugging information about prefixes learned on the local border router.

Examples

The following example enables the display of active-probe debug information on a border router: Router# debug oer border learn *May 4 22:51:31.971: OER BR LEARN: Reporting prefix 1: 10.1.5.0, throughput 201 *May 4 22:51:31.971: OER BR LEARN: Reporting 1 throughput learned prefixes *May 4 22:51:31.971: OER BR LEARN: State change, new STOPPED, old STARTED, reason Stop Learn



DB-1759

Debug Commands debug oer border learn

Table 255

Related Commands

debug oer border learn Field Descriptions

Field

Description

OER BR LEARN:

Indicates debugging information for the OER border router learning process.

Command

Description

oer



DB-1760

May 2008

Debug Commands debug oer border routes

debug oer border routes To display debugging information for OER controlled or monitored routes on the local border router, use the debug oer border routes command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command. debug oer border routes {bgp | static} no debug oer border routes {bgp | static}

Syntax Description

bgp

Displays debugging information for only BGP routes.

static

Displays debugging information for only static routes.

Command Default

No debugging is enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

Examples

The debug oer border routes command is entered on a border router. This command is used to display the debugging information about OER controlled or monitored routes on the local border router.

The following example enables the display of active-probe debug information on a border router: Router# debug oer border routes *May *May *May *May

4 4 4 4

22:35:53.239: 22:35:53.239: 22:35:53.239: 22:35:53.239:

OER OER OER OER

BGP: BGP: BGP: BGP:

Control exact prefix 10.1.5.0/24 Walking the BGP table for 10.1.5.0/24 Path for 10.1.5.0/24 is now under OER control Setting prefix 10.1.5.0/24 as OER net#



DB-1761

Debug Commands debug oer border routes

Table 256

Related Commands

debug oer border routes Field Descriptions

Field

Description

OER BR BGP:

Indicates debugging information for OER controlled BGP routes.

OER BR STATIC:

Indicates debugging information for OER controlled Static routes. (Not displayed in the example output.)

Command

Description

oer



DB-1762

May 2008

Debug Commands debug oer border traceroute reporting

debug oer border traceroute reporting To display debugging information for traceroute probes on the local border router, use the debug oer border traceroute reporting command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command. debug oer border traceroute reporting [detail] no debug oer border traceroute reporting [detail]

Syntax Description

detail

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2(33)SRB


12.2SX


(Optional) Displays detailed traceroute debug information.

Usage Guidelines

The debug oer border traceroute reporting command is entered on a border router. This command is used to display the debugging information about traceroute probes sourced on the local border router.

Examples

The following example enables the display of active-probe debug information on a border router: Router# debug oer border traceroute reporting May 19 03:46:23.807: OER BR TRACE(det): Received start message: msg1 458776, msg2 1677787648, if index 19, host addr 100.1.2.1, flags 1, max ttl 30, protocol 17, probe delay 0 May 19 03:46:26.811: OER BR TRACE(det): Result msg1 458776, msg2 1677787648 num hops 30 sent May 19 03:47:20.919: OER BR TRACE(det): Received start message: msg1 524312, msg2 1677787648, if index 2, host addr 100.1.2.1, flags 1, max ttl 30, protocol 17, probe delay 0 May 19 03:47:23.923: OER BR TRACE(det): Result msg1 524312, msg2 1677787648 num hops 3 sent



DB-1763

Debug Commands debug oer border traceroute reporting

Table 257

Related Commands

debug oer border traceroute reporting Field Descriptions

Field

Description

OER BR TRACE:

Indicates border router debugging information for traceroute probes.

Command

Description

oer



DB-1764

May 2008

Debug Commands debug oer border

debug oer border To display general OER border router debugging information, use the debug oer border command in privileged EXEC mode. To stop the display of OER debugging information, use the no form of this command. debug oer border no debug oer border

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer border command is entered on a border router. This command is used to display debugging information about the OER border process, controlled routes and monitored prefixes.

Examples

The following example displays general OER debugging information: Router# debug oer border *May *May

4 22:32:33.695: OER BR: Process Message, msg 4, ptr 33272128, value 4 22:32:34.455: OER BR: Timer event, 0

140


debug oer border Field Descriptions

Field

Description

OER BR:

Indicates debugging information for OER Border process.


DB-1765

Debug Commands debug oer border

Related Commands

Command

Description

oer



DB-1766

May 2008

Debug Commands debug oer cc

debug oer cc To display OER communication control debugging information for master controller and border router communication, use the debug oer cc command in privileged EXEC mode. To stop the display of OER debugging information, use the no form of this command. debug oer cc [detail] no debug oer cc [detail]

Syntax Description

detail

Command Default


Command Modes

Privileged EXEC

Command History

Release


Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer cc command can be entered on a master controller on a border router. This command is used to display messages exchanged between the master controller and the border router. These messages include control commands, configuration commands, and monitoring information. Enabling this command will cause very detailed output to be displayed and can utilize a considerable amount of system resources. This command should be enabled with caution in a production network.

Examples

The following example enables the display of OER communication control debugging messages: Router# debug oer cc *May

4 23:03:22.527: OER CC: ipflow prefix reset received: 10.1.5.0/24


debug oer cc Field Descriptions

Field

Description

OER CC:

Indicates debugging information for OER communication messages.


DB-1767

Debug Commands debug oer cc

Related Commands

Command

Description

oer



DB-1768

May 2008

Debug Commands debug oer master border

debug oer master border To display debugging information for OER border router events on an OER master controller, use the debug oer master border command in privileged EXEC mode. To stop border router event debugging, use the no form of this command. debug oer master border [ip-address] no debug oer master border

Syntax Description

ip-address

Command Default


Command Modes

Privileged EXEC

Command History

Release

(Optional) Specifies the IP address of a border router.

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer master border command is entered on a master controller. The output displays information related to the events or updates from one or more border routers.

Examples

The following example shows the status of 2 border routers. Both routers are up and operating normally. Router# debug oer master border OER Master Border Router debugging is on Router# 1d05h: OER MC BR 10.4.9.7: BR I/F update, status 0, rx bw 100000, time, tx ld 0, rx ld 0, rx rate tx bytes 5016033 1d05h: OER MC BR 10.4.9.7: BR I/F update, status 0, rx bw 100000, time, tx ld 0, rx ld 0, rx rate x bytes 1028907 1d05h: OER MC BR 10.4.9.6: BR I/F update, status 0, rx bw 100000, time, tx ld 0, rx ld 0, rx rate x bytes 1027912 1d05h: OER MC BR 10.4.9.6: BR I/F update, status 0, rx bw 100000, time, tx ld 0, rx ld 0, rx rate tx bytes 5013993

UP, line 1 index 1, tx bw 10000 0 rx bytes 3496553, tx rate 0, UP, line 1 index 2, tx bw 10000 0 rx bytes 710149, tx rate 0, t UP, line 1 index 2, tx bw 10000 0 rx bytes 743298, tx rate 0, t UP, line 1 index 1, tx bw 10000 0 rx bytes 3491383, tx rate 0,



DB-1769

Debug Commands debug oer master border

Table 260

Related Commands

debug oer master border Field Descriptions

Field

Description

OER MC BR ip-address:

Indicates debugging information for a border router process. The ip-address identifies the border router.

Command

Description

oer



DB-1770

May 2008

Debug Commands debug oer master collector

debug oer master collector To display data collection debugging information for OER monitored prefixes, use the debug oer master collector command in privileged EXEC mode. To disable the display of this debugging information, use the no form of this command. debug oer master collector {active-probes [detail [trace]] | netflow} no debug oer master collector {active-probes [detail [trace]] | netflow}

Syntax Description

active-probes

Displays aggregate active probe results for a given prefix on all border routers that are executing the active probe.

detail

(Optional) Displays the active probe results from each target for a given prefix on all border routers that are executing the active probe.

trace

(Optional) Displays aggregate active probe results and historical statistics for a given prefix on all border routers that are executing the active probe.

netflow

Displays information about the passive (NetFlow) measurements received by the master controller for prefixes monitored from the border router.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer master collector command is entered on a master controller. The output displays data collection information for monitored prefixes.

Examples

debug oer master collector active-probes Example

The following example displays aggregate active probe results for the 10.1.0.0/16 prefix on all border routers that are configured to execute this active probe: Router# debug oer master collector active-probes *May 4 22:34:58.221: OER MC APC: Probe Statistics Gathered for prefix 10.1.0.0/16 on all exits,notifying the PDP *May 4 22:34:58.221: OER MC APC: Summary Exit Data (pfx 10.1.0.0/16, bdr 10.2.2.2, if 13, nxtHop Default):savg delay 13, lavg delay 14, sinits 25, scompletes 25


DB-1771


*May 4 22:34:58.221: OER MC APC: Summary Prefix Data: (pfx 10.1.0.0/16) sloss 0, lloss 0, sunreach 25, lunreach 25, savg raw delay 15, lavg raw delay 15, sinits 6561, scompletes 6536, linits 6561, lcompletes 6536 *May 4 22:34:58.221: OER MC APC: Active OOP check done


debug oer master collector active-probes Field Descriptions

Field

Description

OER MC APC:

Indicates debugging information for active probes from the r OER master collector.

debug oer master collector active-probes detail Example

The following example displays aggregate active probe results from each target for the 10.1.0.0/16 prefix on all border routers that are configured to execute this active probe: Router# debug oer master collector active-probes detail *May 4 22:36:21.945: OER MC APC: Rtrv Probe Stats: BR 10.2.2.2, Type echo, Tgt 10.1.1.1,TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13 *May 4 22:36:22.001: OER MC APC: Remote stats received: BR 10.2.2.2, Type echo, Tgt 10.15.1, TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13 *May 4 22:36:22.313: OER MC APC: Perf data point (pfx 10.1.0.0/16, bdr 10.2.2.2, if 13, xtHop Default): avg delay 20, loss 0, unreach 0, initiations 2, completions 2, delay sum40, ldelay max 20, ldelay min 12 *May 4 22:36:22.313: OER MC APC: Perf data point (pfx 10.1.0.0/16, bdr 10.2.2.2, if 13, xtHop Default): avg delay 20, loss 0, unreach 0, initiations 2, completions 2, delay sum40, ldelay max 20, ldelay min 12 *May 4 22:36:22.313: OER MC APC: Probe Statistics Gathered for prefix 10.1.0.0/16 on al exits, notifying the PDP *May 4 22:36:22.313: OER MC APC: Active OOP check done


debug oer master collector active-probes detail Field Descriptions

Field

Description

OER MC APC:


debug oer master collector active-probes detail trace Example

The following example displays aggregate active probe results and historical statistics from each target for the 10.1.0.0/16 prefix on all border routers that are configured to execute this active probe: Router# debug oer master collector active-probes detail trace *May 4 22:40:33.845: OER MC APC: Rtrv Probe Stats: BR 10.2.2.2, Type echo, Tgt 10.1.5.1, TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13 *May 4 22:40:33.885: OER MC APC: Remote stats received: BR 10.2.2.2, Type echo, Tgt 10.1.5.1, TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13 *May 4 22:40:34.197: OER MC APC: Remote stats received: BR 10.2.2.2, Type echo, Tgt 10.1.2.1, TgtPt 0, Src Default, SrcPt 0, NxtHp Default, Ndx 13 *May 4 22:40:34.197: OER MC APC: Updating Probe (Type echo Tgt 10.1.2.1 TgtPt 0) Total Completes 1306, Total Attempts 1318 *May 4 22:40:34.197: OER MC APC: All stats gathered for pfx 10.1.0.0/16 Accumulating Stats *May 4 22:40:34.197: OER MC APC: Updating Curr Exit Ref (pfx 10.1.0.0/16,


DB-1772

May 2008


bdr 10.2.2.2, if 13, nxtHop Default) savg delay 17, lavg delay 14, savg loss 0, lavg loss 0, savg unreach 0, lavg unreach 0 *May 4 22:40:34.197: OER MC APC: Probe Statistics Gathered for prefix 10.1.0.0/16 on all exits, notifying the PDP *May 4 22:40:34.197: OER MC APC: Active OOP check done


debug oer master collector active-probes detail trace Field Descriptions

Field

Description

OER MC APC:


debug oer master collector netflow Example

The following example displays passive monitoring results for the 10.1.5.0/24 prefix: Router# debug oer master collector netflow *May 4 22:31:45.739: OER MC NFC: Rcvd egress update from BR 10.1.1.2 prefix 10.1.5.0/24 Interval 75688 delay_sum 0 samples 0 bytes 20362 pkts 505 flows 359 pktloss 1 unreach 0 *May 4 22:31:45.739: OER MC NFC: Updating exit_ref; BR 10.1.1.2 i/f Et1/0, s_avg_delay 655, l_avg_delay 655, s_avg_pkt_loss 328, l_avg_pkt_loss 328, s_avg_flow_unreach 513, l_avg_flow_unreach 513 *May 4 22:32:07.007: OER MC NFC: Rcvd ingress update from BR 10.1.1.3 prefix 10.1.5.0/24 Interval 75172 delay_sum 42328 samples 77 bytes 22040 pkts 551 flows 310 pktloss 0 unreach 0


Related Commands

debug oer master collector netflow Field Descriptions

Field

Description

OER MC NFC:

Indicates debugging information for the OER master collector from passive monitoring (NetFlow).

Command

Description

oer



DB-1773

Debug Commands debug oer master cost-minimization

debug oer master cost-minimization To display debugging information for cost-based optimization policies, use the debug oer master cost-minimization command in privileged EXEC mode. To disable the display of this debugging information, use the no form of this command. debug oer master cost-minimization [detail] no debug oer master cost-minimization [detail]

Syntax Description

detail

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2(33)SRB


12.2SX



Usage Guidelines

The debug oer master cost-minimization command is entered on a master controller. The output displays debugging information for cost-minimization policies.

Examples

The following example displays detailed cost optimization policy debug information: Router# debug oer master cost-minimization detail OER Master cost-minimization Detail debugging is on *May 14 00:38:48.839: OER MC COST: Momentary target utilization for exit 10.1.1.2 i/f Ethernet1/0 nickname ISP1 is 7500 kbps, time_left 52889 secs, cumulative 16 kb, rollup period 84000 secs, rollup target 6000 kbps, bw_capacity 10000 kbps *May 14 00:38:48.839: OER MC COST: Cost OOP check for border 10.1.1.2, current util: 0 target util: 7500 kbps *May 14 00:39:00.199: OER MC COST: ISP1 calc separate rollup ended at 55 ingress Kbps *May 14 00:39:00.199: OER MC COST: ISP1 calc separate rollup ended at 55 egress bytes *May 14 00:39:00.199: OER MC COST: Target utilization for nickname ISP1 set to 6000, rollups elapsed 4, rollups left 24 *May 14 00:39:00.271: OER MC COST: Momentary target utilization for exit 10.1.1.2 i/f Ethernet1/0 nickname ISP1 is 7500 kbps, time_left 52878 secs, cumulative 0 kb, rollup period 84000 secs, rollup target 6000 kbps, bw_capacity 10000 kbps *May 14 00:39:00.271: OER MC COST: Cost OOP check for border 10.1.1.2, current util: 0 target util: 7500 kbps


DB-1774

May 2008

Debug Commands debug oer master cost-minimization


Related Commands

debug oer master cost-minimization detail Field Descriptions

Field

Description

OER MC COST:

Indicates debugging information for cost-based optimization on the master controller.

Command

Description

cost-minimization

Configures cost-based optimization policies on a master controller.

oer


show oer master cost-minimization

Displays the status of cost-based optimization policies.


DB-1775

Debug Commands debug oer master exit

debug oer master exit To display debug event information for OER managed exits, use the debug oer master exit command in privileged EXEC mode. To stop the display of debug event information, use the no form of this command. debug oer master exit [detail] no debug oer master exit [detail]

Syntax Description

detail

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Displays detailed OER managed exit information.

Usage Guidelines

The debug oer master exit command is entered on a master controller. This command is used to display debugging information for master controller exit selection processes.

Examples

The following example shows output form the debug oer master exit command, entered with the detail keyword: Router# debug oer master exit detail *May *May *May *May *May check *May check *May check

4 4 4 4 4

11:26:51.539: 11:26:52.195: 11:26:55.515: 11:29:14.987: 11:29:35.467:

OER OER OER OER OER

MC MC MC MC MC

EXIT: EXIT: EXIT: EXIT: EXIT:

10.1.1.1, intf Fa4/0 INPOLICY 10.2.2.3, intf Se2/0 INPOLICY 10.1.1.2, intf Se5/0 INPOLICY 7 kbps should be moved from 10.1.1.1, intf Fa4/0 10.1.1.1, intf Fa4/0 in holddown state so skip OOP

4 11:29:35.831: OER MC EXIT: 10.2.2.3, intf Se2/0 in holddown state so skip OOP 4 11:29:39.455: OER MC EXIT: 10.1.1.2, intf Se5/0 in holddown state so skip OOP


DB-1776

May 2008

Debug Commands debug oer master exit


Related Commands

debug oer master exit detail Field Descriptions

Field

Description

OER MC EXIT:

Indicates OER master controller exit event.

Command

Description

oer



DB-1777

Debug Commands debug oer master learn

debug oer master learn To display debug information for OER master controller learning events, use the debug oer master learn command in privileged EXEC mode. To stop the display of debug information, use the no form of this command. debug oer master learn no debug oer master learn

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer master learn command is entered on a master controller. This command is used to display debugging information for master controller learning events.

Examples

The following example shows output from the debug oer master learn command. The output an shows OER Top Talker debug events. The master controller is enabling prefix learning for new border router process: Router# debug oer master learn 06:13:43: OER MC LEARN: Enable type 3, state 0 06:13:43: OER MC LEARN: OER TTC: State change, new RETRY, old DISABLED, reason TT start 06:13:43: OER MC LEARN: OER TTC: State change, new RETRY, old DISABLED, reason TT start request 06:13:43: OER MC LEARN: OER TTC: State change, new RETRY, old DISABLED, reason T T start request 06:14:13: OER MC LEARN: TTC Retry timer expired 06:14:13: OER MC LEARN: OER TTC: State change, new STARTED, old RETRY, reason At least one BR started 06:14:13: %OER_MC-5-NOTICE: Prefix Learning STARTED 06:14:13: OER MC LEARN: MC received BR TT status as enabled 06:14:13: OER MC LEARN: MC received BR TT status as enabled 06:19:14: OER MC LEARN: OER TTC: State change, new WRITING DATA, old STARTED, reason Updating DB


DB-1778

May 2008

Debug Commands debug oer master learn

06:19:14: OER MC LEARN: OER TTC: State change, new SLEEP, old WRITING DATA, reason Sleep state


Related Commands

debug oer master learn Field Descriptions

Field

Description

OER MC LEARN:

Indicates OER master controller learning events.

Command

Description

oer



DB-1779

Debug Commands debug oer master prefix

debug oer master prefix To display debug events related to prefix processing on an OER master controller, use the debug oer master prefix command in privileged EXEC mode. To disable the display of debug information, use the no form of this command. debug oer master prefix [prefix | appl] [detail] no debug oer master prefix [prefix | appl] [detail]

Syntax Description

prefix

(Optional) Specifies a single prefix or prefix range. The prefix address and mask are entered with this argument.

appl

(Optional) Displays information about prefixes used by applications monitored and controlled by an OER master controller.

detail

(Optional) Displays detailed OER prefix processing information.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer master prefix command is entered on a master controller. This command displays debugging information related to prefix monitoring and processing.

Examples

The following example shows the master controller searching for the target of an active probe after the target has become unreachable. Router# debug oer master prefix OER Master Prefix debugging is on 06:01:28: OER MC PFX 10.4.9.0/24: left assigned and running 06:01:38: OER MC PFX 10.4.9.0/24: 06:02:59: OER MC PFX 10.4.9.0/24: left assigned and running 06:03:08: OER MC PFX 10.4.9.0/24: 06:04:29: OER MC PFX 10.4.9.0/24: left assigned and running 06:04:39: OER MC PFX 10.4.9.0/24:

APC last target deleted for prefix, no targets APC Attempting to probe all exits APC last target deleted for prefix, no targets APC Attempting to probe all exits APC last target deleted for prefix, no targets APC Attempting to probe all exits


DB-1780

May 2008

Debug Commands debug oer master prefix

06:05:59: OER MC PFX 10.4.9.0/24: APC last target deleted for prefix, no targets left assigned and running 06:06:09: OER MC PFX 10.4.9.0/24: APC Attempting to probe all exits


Related Commands

debug oer master prefix Field Descriptions

Field

Description

OER MC PFX ip-address:

Indicates debugging information for OER monitored prefixes. The ip-address identifies the prefix.

Command

Description

oer



DB-1781

Debug Commands debug oer master prefix-list

debug oer master prefix-list To display debug events related to prefix-list processing on an OER master controller, use the debug oer master prefix-list command in privileged EXEC mode. To disable the display of debug information, use the no form of this command. debug oer master prefix-list list-name [detail] no debug oer master prefix-list list-name

Syntax Description

list-name

Specifies a single prefix or prefix range. The prefix address and mask are entered with this argument.

detail

(Optional) Displays detailed OER prefix-list processing information.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(11)T


12.2(33)SRB


12.2SX


Usage Guidelines

Examples

The debug oer master prefix-list command is entered on a master controller. This command displays debugging information related to prefix-list processing.

The following example shows output from the debug oer master prefix-list command. Router# debug oer master prefix-list 23:02:16.283: OER 23:02:16.283: OER 23:02:16.283: OER TRUE 23:02:16.283: OER 23:02:16.283: OER 23:02:16.283: OER 50%, notify TRUE 23:02:16.283: OER 23:02:16.283: OER 23:02:16.283: OER

MC PFX 10.1.5.0/24: Check PASS REL loss: loss 0, policy 10%, notify TRUE MC PFX 10.1.5.0/24: Passive REL loss in-policy MC PFX 10.1.5.0/24: Check PASS REL delay: delay 124, policy 50%, notify MC PFX 10.1.5.0/24: Passive REL delay in policy MC PFX 10.1.5.0/24: Prefix not OOP MC PFX 10.1.5.0/24: Check PASS REL unreachable: unreachable 0, policy MC PFX 10.1.5.0/24: Passive REL unreachable in-policy MC PFX 10.1.5.0/24: Check PASS REL loss: loss 0, policy 10%, notify TRUE MC PFX 10.1.5.0/24: Passive REL loss in policy


DB-1782

May 2008

Debug Commands debug oer master prefix-list


Related Commands

debug oer master prefix-list Field Descriptions

Field

Description

OER MC PFX ip-address:

Indicates debugging information for OER monitored prefixes. The ip-address identifies the prefix.

Command

Description

oer



DB-1783

Debug Commands debug oer master process

debug oer master process To display debug information about the OER master controller process, use the debug oer master process command in privileged EXEC mode. To stop displaying debug information, use the no form of this command. debug oer master process no debug oer master process

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2(33)SRB


12.2SX


Usage Guidelines

The debug oer master process command is entered on a master controller.

Examples

The following sample debug output for a master controller process: Router# debug oer master process 01:12:00: OER MC PROCESS: Main msg type 15, ptr 0, value 0


Related Commands

debug oer master process Field Descriptions

Field

Description

OER MC PROCESS:

Indicates a master controller master process debugging message.

Command

Description

oer



DB-1784

May 2008

Debug Commands debug oer master process


DB-1785

Debug Commands debug oer master traceroute reporting

debug oer master traceroute reporting To display debug information about traceroute probes, use the debug oer master traceroute reporting command in privileged EXEC mode. To stop displaying debug information, use the no form of this command. debug oer master traceroute reporting [detail] no debug oer master traceroute reporting [detail]

Syntax Description

detail

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2(33)SRB


12.2SX



Usage Guidelines

The debug oer master traceroute reporting command is entered on a master controller. This command is used to display traceroute events on a master controller.

Examples

The following sample debug output for a master controller process: Router# debug oer master traceroute reporting detail *May 12 18:55:14.239: OER MC TRACE: sent start message msg1 327704, msg2 167838976, if index 2, host add 10.1.5.2, flags 1, max ttl 30, protocol 17 *May 12 18:55:16.003: OER MC TRACE: sent start message msg1 393240, msg2 167838976, if index 2, host add 10.1.5.2, flags 1, max ttl 30, protocol 17 master# *May 12 18:55:17.303: OER MC TRACE: Received result: msg_id1 327704, prefix 10.1.5.0/24, hops 4, flags 1 *May 12 18:55:19.059: OER MC TRACE: Received result: msg_id1 393240, prefix 10.1.5.0/24, hops 4, flags 1



DB-1786

May 2008

Debug Commands debug oer master traceroute reporting

Table 271

Related Commands

debug oer master traceroute reporting detail Field Descriptions

Field

Description

OER MC PROCESS:

Indicates master controller debugging information for traceroute probes.

Command

Description

oer



DB-1787

Debug Commands debug packet

debug packet To display per-packet debugging output, use the debug packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug packet [interface number [vcd vcd-number] | vc vpi/vci | vc-name] no debug packet [interface number [vcd vcd-number] | vc vpi/vci | vc-name]

Syntax Description

interface number

(Optional) interface or subinterface number.

vcd vcd-number

(Optional) Number of the virtual circuit designator (VCD).

vc vpi/vci

(Optional) Virtual path identifier (VPI) and virtual channel identifier (VCI) numbers of the VC.

vc-name

(Optional) Name of the PVC or SVC.

Defaults

Debugging for packets is disabled by default.

Command Modes

Privileged EXEC

Command History

Release

Modification

9.21


12.2(13)T

Support for Apollo Domain and Banyan VINES was removed.

Usage Guidelines

12.2(33)SRA


12.2SX


The debug packet command displays all process-level packets for both outbound and inbound packets. This command is useful for determining whether packets are being received and sent correctly. The output reports information online when a packet is received or a transmission is attempted. For sent packets, the information is displayed only after the protocol data unit (PDU) is entirely encapsulated and a next hop VC is found. If information is not displayed, the address translation probably failed during encapsulation. When a next hop VC is found, the packet is displayed exactly as it will be presented on the wire. Having a display indicates that the packets are properly encapsulated for transmission. For received packets, information is displayed for all incoming frames. The display can show whether the sending station properly encapsulates the frames. Because all incoming frames are displayed, this information is useful when performing back-to-back testing and corrupted frames cannot be dropped by an intermediary switch. The debug packet command also displays the initial bytes of the actual PDU in hexadecimal. This information can be decoded only by qualified support or engineering personnel.


DB-1788

May 2008


Caution

Examples

Because the debug packet command generates a substantial amount of output for every packet processed, use it only when traffic on the network is low so other activity on the system is not adversely affected.

The following is sample output from the debug packet command: Router# debug packet 2/0.5(I): VCD:0x9 VCI:0x23 Type:0x0 SAP:AAAA CTL:03 OUI:000000 TYPE:0800 Length0x70 4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000 A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105


debug packet Field Descriptions

Field

Description

2/0.5

Indicates the subinterface that generated this packet.

(I)

Indicates a receive packet. (O) indicates an output packet.

VCD: 0xn

Indicates the virtual circuit associated with this packet, where n is some value.

DM: 0xnnnn

Indicates the descriptor mode bits on output only, where nnnn is a hexadecimal value.

TYPE:n

Displays the encapsulation type for this packet.

Length:n

Displays the total length of the packet including the headers.

The following two lines of output are the binary data, which are the contents of the protocol data unit (PDU) before encapsulation: 4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000 A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105

The following is sample output from the debug packet command: Router# debug packet Ethernet0: Unknown ARPA, src 0000.0c00.6fa4, dst ffff.ffff.ffff, type 0x0a0 data 00000c00f23a00000c00ab45, len 60 Serial3: Unknown HDLC, size 64, type 0xaaaa, flags 0x0F00 Serial2: Unknown PPP, size 128 Serial7: Unknown FRAME-RELAY, size 174, type 0x5865, DLCI 7a Serial0: compressed TCP/IP packet dropped


DB-1789



debug packet Field Descriptions

Field

Description

Ethernet0

Name of the Ethernet interface that received the packet.

Unknown

Network could not classify this packet. Examples include packets with unknown link types.

ARPA

Packet uses ARPA-style encapsulation. Possible encapsulation styles vary depending on the media command mode (MCM) and encapsulation style. Ethernet (MCM)—Encapsulation Style: •

ARP

•

ETHERTALK

•

ISO1

•

ISO3

•

LLC2

•

NOVELL-ETHER

•

SNAP

FDDI (MCM)—Encapsulation Style: •

ISO1

•

ISO3

•

LLC2

•

SNAP

Frame Relay—Encapsulation Style: •

BRIDGE

•

FRAME-RELAY


DB-1790

May 2008


Table 273

debug packet Field Descriptions (continued)

Field

Description

ARPA (continued)

Serial (MCM)—Encapsulation Style: •

BFEX25

•

BRIDGE

•

DDN-X25

•

DDNX25-DCE

•

ETHERTALK

•

FRAME-RELAY

•

HDLC

•

HDH

•

LAPB

•

LAPBDCE

•

MULTI-LAPB

•

PPP

•

SDLC-PRIMARY

•

SDLC-SECONDARY

•

SLIP

•

SMDS

•

STUN

•

X25

•

X25-DCE

Token Ring (MCM)—Encapsulation Style: •

3COM-TR

•

ISO1

•

ISO3

•

MAC

•

LLC2

•

NOVELL-TR

•

SNAP

•

VINES-TR

src 0000.0c00.6fa4

MAC address of the node generating the packet.

dst.ffff.ffff.ffff

MAC address of the destination node for the packet.

type 0x0a0

Packet type.

data...

First 12 bytes of the datagram following the MAC header.

len 60

Length of the message (in bytes) that the interface received from the wire.

size 64

Length of the message (in bytes) that the interface received from the wire. Equivalent to the len field.


DB-1791


Table 273

debug packet Field Descriptions (continued)

Field

Description

flags 0x0F00

HDLC or PP flags field.

DLCI 7a

The DLCI number on Frame Relay.

compressed TCP/IP TCP header compression is enabled on an interface and the packet is not HDLC packet dropped or X25.


DB-1792

May 2008

Debug Commands debug pad

debug pad To display debugging messages for all packet assembler/disassembler (PAD) connections, use the debug pad command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug pad no debug pad

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0

This command was introduced in a release prior to Cisco IOS Release 12.0.

12.2(33)SRA


12.2SX


Examples

Use the debug pad command to gather information to forward to the Cisco Technical Assistance Center (TAC) to assist in troubleshooting a problem that involves PAD connections. The following example shows output of the debug pad and debug x25 event commands for an incoming PAD call destined for a terminal line. The incoming PAD call is rejected by the terminal line because the selected network closed user group (CUG) has not been subscribed to by the caller: Router# debug pad Router# debug x25 event Serial1/1:X.25 I R1 Call (16) 8 lci 8 From (7):2001534 To (9):200261150 Facilities:(2) Closed User Group (basic):99 Call User Data (4):0x01000000 (pad) pad_svc_announce:destination matched 1 PAD:incoming call to 200261150 on line 130 CUD length 4 !PAD130:Incoming Call packet, Closed User Group (CUG) service protection, selected network CUG not subscribed PAD:CUG service protection Cause:11 Diag:65 Serial1/1:X.25 O R1 Clear (5) 8 lci 8 Cause 0, Diag 65 (DTE originated/Facility code not allowed) Serial1/1:X.25 I R1 Clear Confirm (3) 8 lci 8


DB-1793

Debug Commands debug pad

The following example shows the output of the debug pad command for an outgoing PAD call initiated from a terminal line with a subscribed CUG that bars outgoing access: !PAD130:Outgoing Call packet, Closed User Group - CUG service validation, selected CUG !bars outgoing access PAD130:Closing connection to . In 0/0, out 0/0


DB-1794

May 2008

Debug Commands debug piafs events

debug piafs events To check the debugging messages for Personal Handyphone Internet Access Forum Standard (PIAFS) calls, use the debug piafs events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug piafs events no debug piafs events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)T

This command was introduced on Cisco 803, Cisco 804, and Cisco 813 routers.

12.2SX


Usage Guidelines

The debug piafs events command provides debugging information for the PIAFS calls on the router, including the inband negotiation process.

Examples

The debug piafs events command was configured to provide the following information for PIAFS calls: Router# debug piafs events 02:16:39:PIAFS events debugging is on 02:16:167516180371:PIAFS: RX CDAPI :CDAPI_MSG_CONNECT_RESP 02:16:167503765504:PIAFS: TX -> CDAPI :CDAPI_MSG_CONN_ACTIVE_REQ 02:16:167503724544:PIAFS: RX CDAPI :CDAPI_MSG_CONN_ACTIVE_REQ

The CDAPI in the router transmits a connection active request to the switch.

RX reason BAP - Multilink bundle overloaded BAP laudrup: sending StatusInd, id 2, len 44 on Virtual-Access1 to remote BAP Virtual-Access1: received StatusRsp, id 2, len 1 BAP laudrup: StatusRsp, id 2, ACK


debug ppp bap Field Descriptions

Field

Description

BAP Virtual-Access1:

Identifier of the virtual access interface in use.

group “laudrup”

Name of the BACP group.

sending CallReq

Action initiated; in this case, sending a call request.

on BRI3:1 to remote

Physical interface being used.

BAP laudrup: attempt1 to dial 19995776677 Call initiated, number being dialed, and physical interface being used. on BRI3 ---> reason BAP - Multilink bundle overloaded

Reason for initiating the BACP call.

BAP laudrup: sending StatusInd, id 2, len 44 Details about the sent message: It was a status on Virtual-Access1 to remote indication message, had identifier 2, had a BACP datagram length 44, and was sent on virtual access interface 1. You can display information about the virtual access interface by using the show interfaces virtual-access EXEC command. (The length shown at the end of each negotiated option includes the 2-byte type and length header.) The debug ppp bap event command might show state transitions and protocol actions, in addition to the basic debug ppp bap command. The following is sample output from the debug ppp bap event command: Router# debug ppp bap event BAP laudrup: Idle --> AddWait BAP laudrup: AddWait --> AddPending BAP laudrup: AddPending --> Idle


DB-1812

May 2008

Debug Commands debug ppp bap

The following is sample output from the debug ppp bap event command: Router# debug ppp bap event Peer does not support a message type No response to a particular request No response to all request retransmissions Not configured to initiate link addition Expected action by peer has not occurred Exceeded number of retries No links available to call out Unable to provide phone numbers for callback Maximum number of links in the group Minimum number of links in the group Unable to process link addition at present Unable to process link removal at present Not configured/unable to initiate link removal Link addition completed notification Link addition failed notification Determination of location of the group config Link with specified discriminator not in group Link removal failed Call failure with status Failed to dial specified number Discarding retransmission Unable to find received identifier Received StatusInd when no call pending Discarding message with no phone delta Unable to send message in particular state Received a zero identifier Request has precedence

The error messages displayed might be added to the basic output when the debug ppp bap error command is used. Because the errors are very rare, you might never see these messages. Router# debug ppp bap error Unable to find appropriate request for received response Invalid message type of queue Received request is not part of the group Add link attempt failed to locate group Remove link attempt failed to locate group Unable to inform peer of link addition Changing of precedence cannot locate group Received short header/illegal length/short packet Invalid configuration information length Unable to NAK incomplete options Unable to determine current number of links No interface list to dial on Attempt to send invalid data Local link discriminator is not in group Received response type is incorrect for identifier


DB-1813


The messages displayed might be added to the basic output when the debug ppp bap negotiation command is used: Router# debug ppp bap negotiation BAP BAP BAP BAP BAP BAP BAP BAP BAP

laudrup: laudrup: laudrup: laudrup: laudrup: laudrup: laudrup: laudrup: laudrup:

adding link speed 64 kbps for type 0x1 len 5 adding reason "User initiated addition", len 25 CallRsp, id 4, ACK link speed 64 kbps for types 0x1, len 5 (ACK) phone number "1: 0 2: ", len 7 (ACK) adding call status 0, action 0 len 4 adding 1 phone numbers "1: 0 2: " len 7 adding reason "Successfully added link", len 25 StatusRsp, id 4, ACK

Additional negotiation messages might also be displayed for the following: Received BAP message Sending message Decode individual options for send/receive Notification of invalid options

The following shows additional reasons for a particular BAP action that might be displayed in an “adding reason” line of the debug ppp bap negotiation command output: "Outgoing add request has precedence" "Outgoing remove request has precedence" "Unable to change request precedence" "Unable to determine valid phone delta" "Attempting to add link" "Link addition is pending" "Attempting to remove link" "Link removal is pending" "Precedence of peer marked CallReq for no action" "Callback request rejected due to configuration" "Call request rejected due to configuration" "No links of specified type(s) available" "Drop request disallowed due to configuration" "Discriminator is invalid" "No response to call requests" "Successfully added link" "Attempt to dial destination failed" "No interfaces present to dial out" "No dial string present to dial out" "Mandatory options incomplete" "Load has not exceeded threshold" "Load is above threshold" "Currently attempting to dial destination" "No response to CallReq from race condition"


DB-1814

May 2008


Table 281 describes the reasons for a BACP Negotiation Action. Table 281

Explanation of Reasons for BACP Negotiation Action

Reason

Explanation

“Outgoing add request has precedence”

Received a CallRequest or CallbackRequest while we were waiting on a CallResponse or CallbackResponse to a sent request. We are the favored peer from the initial BACP negotiation, so we are issuing a NAK to our peer request.

“Outgoing remove request has precedence”

Received a LinkDropQueryRequest while waiting on a LinkDropQueryResponse to a sent request. We are the favored peer from the initial BACP negotiation, therefore we are issuing a NAK to our peer request.

“Unable to change request precedence”

Received a CallRequest, CallbackRequest, or LinkDropQueryRequest while waiting on a LinkDropQueryResponse to a sent request. Our peer is deemed to be the favored peer from the initial BACP negotiation and we were unable to change the status of our outgoing request in response to the favored request, so we are issuing a NAK. (This is an internal error and should never be seen.)

“Unable to determine valid phone delta”

Received a CallRequest from our peer but are unable to provide the required phone delta for the response, so we are issuing a NAK. (This is an internal error and should never be seen.)

“Attempting to add link”

Received a LinkDropQueryRequest while attempting to add a link; a NAK is issued.

“Link addition is pending”

Received a LinkDropQueryRequest, CallRequest, or CallbackRequest while attempting to add a link as the result of a previous operation; a NAK is issued in the response.

“Attempting to remove link”

Received a CallRequest or CallbackRequest while attempting to remove a link; a NAK is issued.

“Link removal is pending”

Received a CallRequest, CallbackRequest, or LinkDropQueryRequest while attempting to remove a link as the result of a previous operation; a NAK is issued in the response.

“Precedence of peer marked CallReq Received an ACK to a previously unfavored CallRequest; we for no action” are issuing a CallStatusIndication to inform our peer that there will be no further action on our part as per this response. “Callback request rejected due to configuration”

Received a CallbackRequest but we are configured not to accept them; a REJect is issued to our peer.

“Call request rejected due to configuration”

Received a CallRequest but we are configured not to accept them; a REJect is issued to our peer.

“No links of specified type(s) available”

We received a CallRequest but no links of the specified type and speed are available; a NAK is issued.

“Drop request disallowed due to configuration”

Received a LinkDropQueryRequest but we are configured not to accept them; a NAK is issued to our peer.


DB-1815


Table 281

Explanation of Reasons for BACP Negotiation Action (continued)

Reason

Explanation

“Discriminator is invalid”

Received a LinkDropQueryRequest but the local link discriminator is not contained within the bundle; a NAK is issued.

“No response to call requests”

After no response to our CallRequest message, a CallStatusIndication is sent to the peer informing that no more action will be taken on behalf of this operation.

“Successfully added link”

Sent as part of the CallStatusIndication informing our peer that we successfully completed the addition of a link to the bundle as the result of the transmission of a CallRequest or the reception of a CallbackRequest.

“Attempt to dial destination failed”

Sent as part of the CallStatusIndication informing our peer that we failed in an attempt to add a link to the bundle as the result of the transmission of a CallRequest or the reception of a CallbackRequest. The retry field with the CallStatusIndication informs the peer of our intentions.

“No interfaces present to dial out”

There are no available interfaces to dial out on to attempt to add a link to the bundle, and we will not retry the dial attempt.

“No dial string present to dial out”

We do not have a dial string to dial out with to attempt to add a link to the bundle, and we are not going to retry the dial attempt. (This is an internal error and should never be seen.)

“Mandatory options incomplete”

Received a CallRequest, CallbackRequest, LinkDropQueryRequest, or CallStatusIndication and the mandatory options are not present, so a NAK is issued in the response. (A CallStatusResponse is an ACK, however).

“Load has not exceeded threshold”

Received a CallRequest or CallbackRequest but we are issuing a NAK in the response. We are monitoring the load of the bundle, and so we determine when links should be added to the bundle.

“Load is above threshold”

Received a LinkDropQueryRequest but we are issuing a NAK in the response. We are monitoring the load of the bundle, and so we determine when links should be removed from the bundle.

“Currently attempting to dial destination”

Received a CallbackRequest which is a retransmission of one that we previously ACK’d and are dialing the number suggested in the request. We are issuing an ACK because we did so previously, even though our peer never saw the previous response.

“No response to CallReq from race condition”

We issued a CallRequest but failed to receive a response, and we are issuing a CallStatusIndication to inform our peer of our intention not to proceed with the operation.


DB-1816

May 2008

Debug Commands debug ppp multilink events

debug ppp multilink events To display information about events affecting multilink groups established for Bandwidth Allocation Control Protocol (BACP), use the debug ppp multilink events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ppp multilink events no debug ppp multilink events

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Caution

Examples

Do not use this command when memory is scarce or in very high traffic situations.

The following is sample output from the debug ppp multilink events command: Router# debug ppp multilink events MLP laudrup: established BAP group 4 on Virtual-Access1, physical BRI3:1 MLP laudrup: removed BAP group 4

Other event messages include the following: Unable to find bundle for BAP group identifier Unable to find physical interface to start BAP Unable to create BAP group Attempt to start BACP when inactive or running Attempt to start BACP on non-MLP interface Link protocol has gone down, removing BAP group Link protocol has gone down, BAP not running or present


debug ppp multilink events Field Descriptions

Field

Description

MLP laudrup

Name of the multilink group.

established BAP group 4

Internal identifier. The same identifiers are used in the show ppp bap group command output.

Virtual-Access1

Dynamic access interface number.

physical BRI3:1

Bundle was established from a call on this interface.

removed BAP group 4

When the bundle is removed, the associated BACP group (with its ID) is also removed.


DB-1817

Debug Commands debug ppp multilink fragments

debug ppp multilink fragments To display information about individual multilink fragments and important multilink events, use the debug ppp multilink fragments command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ppp multilink fragments no debug ppp multilink fragments

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Caution

Examples

The debug ppp multilink fragments command has some memory overhead and should not be used when memory is scarce or in very high traffic situations.

The following is sample output from the debug ppp multilink fragments command when used with the ping EXEC command. The debug output indicates that a multilink PPP packet on interface BRI 0 (on the B channel) is an input (I) or output (O) packet. The output also identifies the sequence number of the packet and the size of the fragment. Router# debug ppp multilink fragments Router# ping 7.1.1.7 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 7.1.1.7, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 32/34/36 ms Router# 2:00:28: MLP BRI0: B-Channel 1: O seq 80000000: size 58 2:00:28: MLP BRI0: B-Channel 2: O seq 40000001: size 59 2:00:28: MLP BRI0: B-Channel 2: I seq 40000001: size 59 2:00:28: MLP BRI0: B-Channel 1: I seq 80000000: size 58 2:00:28: MLP BRI0: B-Channel 1: O seq 80000002: size 58 2:00:28: MLP BRI0: B-Channel 2: O seq 40000003: size 59 2:00:28: MLP BRI0: B-Channel 2: I seq 40000003: size 59 2:00:28: MLP BRI0: B-Channel 1: I seq 80000002: size 58 2:00:28: MLP BRI0: B-Channel 1: O seq 80000004: size 58 2:00:28: MLP BRI0: B-Channel 2: O seq 40000005: size 59 2:00:28: MLP BRI0: B-Channel 2: I seq 40000005: size 59 2:00:28: MLP BRI0: B-Channel 1: I seq 80000004: size 58 2:00:28: MLP BRI0: B-Channel 1: O seq 80000006: size 58 2:00:28: MLP BRI0: B-Channel 2: O seq 40000007: size 59 2:00:28: MLP BRI0: B-Channel 2: I seq 40000007: size 59 2:00:28: MLP BRI0: B-Channel 1: I seq 80000006: size 58


DB-1818

May 2008

Debug Commands debug ppp multilink fragments

2:00:28: 2:00:28: 2:00:28: 2:00:28:

MLP MLP MLP MLP

BRI0: BRI0: BRI0: BRI0:

B-Channel B-Channel B-Channel B-Channel

1: 2: 2: 1:

O O I I

seq seq seq seq

80000008: 40000009: 40000009: 80000008:

size size size size

58 59 59 58


DB-1819

Debug Commands debug ppp multilink negotiation

debug ppp multilink negotiation Note

Effective with release 11.3, the debug ppp multilink negotiation command is not available in Cisco IOS software. To display information about events affecting multilink groups established controlled by Bandwidth Allocation Control Protocol (BACP), use the debug ppp multilink negotiation command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ppp multilink negotiation no debug ppp multilink negotiation

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3

This command was removed and is not available in Cisco IOS software.

12.2SX


Usage Guidelines

Caution

Examples

Do not use this command when memory is scarce or in very high traffic situations.

The following sample output shows Link Control Protocol (LCP) and Network Control Program (NCP) messages that might appear in debug ppp multilink negotiation command. These messages show information about PPP negotiations between the multilink peers. Router# debug ppp multilink negotiation ppp: sending CONFREQ, type = 23 (CI_LINK_DISCRIMINATOR), value = 0xF PPP BRI3:1: received config for type = 23 (LINK_DISCRIMINATOR) value = 0xA acked Router# debug ppp multilink negotiation ppp: sending CONFREQ, type = 1 (CI_FAVORED_PEER), value = 0x647BD090 PPP Virtual-Access1: received CONFREQ, type 1, value = 0x382BBF5 (ACK) PPP Virtual-Access1: BACP returning CONFACK ppp: config ACK received, type = 1 (CI_FAVORED_PEER), value = 0x647BD090 PPP Virtual-Access1: BACP up


DB-1820

May 2008

Debug Commands debug ppp multilink negotiation


debug ppp multilink negotiation Field Descriptions

Field

Description

sending CONFREQ, type = 23 Sending a configuration request and the value of the (CI_LINK_DISCRIMINATOR), value = 0xF link discriminator. Each peer assigns a discriminator value to identify a specific link. The values are significant to each peer individually but do not have to be shared. PPP BRI3:1:

Physical interface being used.

CI_FAVORED_PEER

When the PPP NCP negotiation occurs over the first link in a bundle, the BACP peers use a Magic Number akin to that used by LCP to determine which peer should be favored when both implementations send a request at the same time. The peer that negotiated the higher number is deemed to be favored. That peer should issue a negative acknowledgment to its unfavored peer, which in turn should issue a positive acknowledgment, if applicable according to other link considerations.

PPP Virtual-Access1: BACP returning CONFACK

Returning acknowledgment that BACP is configured.

PPP Virtual-Access1: BACP up

Indicating that the BACP NCP is open.


DB-1821

Debug Commands debug ppp redundancy

debug ppp redundancy To debug PPP synchronization on the networking device, use the debug ppp redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command. debug ppp redundancy [detailed | event] no debug ppp redundancy [detailed | event]

Syntax Description

detailed

(Optional) Displays detailed debug messages related to specified PPP redundancy events.

event

(Optional) Displays information about protocol actions and transitions between action states (pending, waiting, idle) on the link.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(22)S

This command was introduced on the Cisco 7500, 10000, and 12000 series Internet routers.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S on Cisco 7500 series routers.

12.2(20)S

Support was added for the Cisco 7304 router. The Cisco 7500 series router is not supported in Cisco IOS Release 12.2(20)S.

12.2(28)SB


12.2(33)SRA


12.2SX


Examples

The following example displays detailed debug messages related to specified PPP redundancy events: Router# debug ppp redundancy detailed


DB-1822

May 2008

Debug Commands debug ppp

debug ppp To display information on traffic and exchanges in an internetwork implementing the Point-to-Point Protocol (PPP), use the debug ppp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ppp {packet | negotiation | error | authentication | compression | cbcp} no debug ppp {packet | negotiation | error | authentication | compression | cbcp}

Syntax Description

packet

Displays PPP packets being sent and received. (This command displays low-level packet dumps.)

negotiation

Displays PPP packets sent during PPP startup, where PPP options are negotiated.

error

Displays protocol errors and error statistics associated with PPP connection negotiation and operation.

authentication

Displays authentication protocol messages, including Challenge Authentication Protocol (CHAP) packet exchanges and Password Authentication Protocol (PAP) exchanges.

compression

Displays information specific to the exchange of PPP connections using Microsoft Point-to-Point Compression (MPPC). This command is useful for obtaining incorrect packet sequence number information where MPPC compression is enabled.

cbcp

Displays protocol errors and statistics associated with PPP connection negotiations using Microsoft Callback (MSCB).

Command Modes

Privileged EXEC

Usage Guidelines

Use the debug ppp command when trying to find the following: •

The Network Control Protocols (NCPs) that are supported on either end of a PPP connection

•

Any loops that might exist in a PPP internetwork

•

Nodes that are (or are not) properly negotiating PPP connections

•

Errors that have occurred over the PPP connection

•

Causes for CHAP session failures

•

Causes for PAP session failures

•

Information specific to the exchange of PPP connections using the Callback Control Protocol (CBCP), used by Microsoft clients

•

Incorrect packet sequence number information where MPPC compression is enabled

Refer to Internet RFCs 1331, 1332, and 1333 for details concerning PPP-related nomenclature and protocol information.

Caution

The debug ppp compression command is CPU-intensive and should be used with caution. This command should be disabled immediately after debugging.


DB-1823


Examples

The following is sample output from the debug ppp packet command as seen from the Link Quality Monitor (LQM) side of the connection. This example depicts packet exchanges under normal PPP operation. Router# debug ppp packet PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP PPP

Serial4(o): lcp_slqr() state Serial4(i): pkt type 0xC025, Serial4(i): lcp_rlqr() state Serial4(i): pkt type 0xC021, Serial4: I LCP ECHOREQ(9) id Serial4: input(C021) state = Serial4: O LCP ECHOREP(A) id Serial4(o): lcp_slqr() state Serial4(i): pkt type 0xC025, Serial4(i): lcp_rlqr() state Serial4(i): pkt type 0xC021, Serial4: I LCP ECHOREQ(9) id Serial4: input(C021) state = Serial4: O LCP ECHOREP(A) id Serial4(o): lcp_slqr() state Serial4(i): pkt type 0xC025, Serial4(i): lcp_rlqr() state Serial4(i): pkt type 0xC021, Serial4: I LCP ECHOREQ(9) id Serial4: input(C021) state = Serial4: O LCP ECHOREP(A) id Serial4(o): lcp_slqr() state Serial4(i): pkt type 0xC025, Serial4(i): lcp_rlqr() state Serial4(i): pkt type 0xC021, Serial4: I LCP ECHOREQ(9) id Serial4: input(C021) state = Serial4: O LCP ECHOREP(A) id Serial4(o): lcp_slqr() state Serial4(i): pkt type 0xC025, Serial4(i): lcp_rlqr() state Serial4(i): pkt type 0xC021, Serial4: I LCP ECHOREQ(9) id Serial4: input(C021) state = Serial4: O LCP ECHOREP(A) id Serial4(o): lcp_slqr() state

= OPEN magic = D21B4, len datagramsize 52 = OPEN magic = D3454, len datagramsize 16 3 (C) magic D3454 OPEN code = ECHOREQ(9) id 3 (C) magic D21B4 = OPEN magic = D21B4, len datagramsize 52 = OPEN magic = D3454, len datagramsize 16 4 (C) magic D3454 OPEN code = ECHOREQ(9) id 4 (C) magic D21B4 = OPEN magic = D21B4, len datagramsize 52 = OPEN magic = D3454, len datagramsize 16 5 (C) magic D3454 OPEN code = ECHOREQ(9) id 5 (C) magic D21B4 = OPEN magic = D21B4, len datagramsize 52 = OPEN magic = D3454, len datagramsize 16 6 (C) magic D3454 OPEN code = ECHOREQ(9) id 6 (C) magic D21B4 = OPEN magic = D21B4, len datagramsize 52 = OPEN magic = D3454, len datagramsize 16 7 (C) magic D3454 OPEN code = ECHOREQ(9) id 7 (C) magic D21B4 = OPEN magic = D21B4, len

= 48 = 48

= 3 len = 12 = 48 = 48

= 4 len = 12 = 48 = 48

= 5 len = 12 = 48 = 48

= 6 len = 12 = 48 = 48

= 7 len = 12 = 48


debug ppp packet Field Descriptions

Field

Description

PPP

PPP debugging output.

Serial4

Interface number associated with this debugging information.

(o), O

Packet was detected as an output packet.

(i), I

Packet was detected as an input packet.

lcp_slqr()

Procedure name; running LQM, send a Link Quality Report (LQR).

lcp_rlqr()

Procedure name; running LQM, received an LQR.

input (C021)

Router received a packet of the specified packet type (in hexadecimal notation). A value of C025 indicates packet of type LQM.

state = OPEN

PPP state; normal state is OPEN.


DB-1824

May 2008


Table 284

debug ppp packet Field Descriptions (continued)

Field

Description

magic = D21B4

Magic Number for indicated node; when output is indicated, this is the Magic Number of the node on which debugging is enabled. The actual Magic Number depends on whether the packet detected is indicated as I or O.

datagramsize 52

Packet length including header.

code = ECHOREQ(9)

Identifies the type of packet received. Both forms of the packet, string and hexadecimal, are presented.

len = 48

Packet length without header.

id = 3

ID number per Link Control Protocol (LCP) packet format.

pkt type 0xC025

Packet type in hexadecimal notation; typical packet types are C025 for LQM and C021 for LCP.

LCP ECHOREQ(9)

Echo Request; value in parentheses is the hexadecimal representation of the LCP type.

LCP ECHOREP(A)

Echo Reply; value in parentheses is the hexadecimal representation of the LCP type.

To elaborate on the displayed output, consider the partial exchange. This sequence shows that one side is using ECHO for its keepalives and the other side is using LQRs. Router# debug ppp packet PPP PPP PPP PPP PPP PPP PPP PPP

Serial4(o): lcp_slqr() state Serial4(i): pkt type 0xC025, Serial4(i): lcp_rlqr() state Serial4(i): pkt type 0xC021, Serial4: I LCP ECHOREQ(9) id Serial4: input(C021) state = Serial4: O LCP ECHOREP(A) id Serial4(o): lcp_slqr() state

= OPEN magic = D21B4, len datagramsize 52 = OPEN magic = D3454, len datagramsize 16 3 (C) magic D3454 OPEN code = ECHOREQ(9) id 3 (C) magic D21B4 = OPEN magic = D21B4, len

= 48 = 48

= 3 len = 12 = 48

The first line states that the router with debugging enabled has sent an LQR to the other side of the PPP connection: PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48

The next two lines indicate that the router has received a packet of type C025 (LQM) and provides details about the packet: PPP Serial4(i): pkt type 0xC025, datagramsize 52 PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48

The next two lines indicate that the router received an ECHOREQ of type C021 (LCP). The other side is sending ECHOs. The router on which debugging is configured for LQM but also responds to ECHOs. PPP Serial4(i): pkt type 0xC021, datagramsize 16 PPP Serial4: I LCP ECHOREQ(9) id 3 (C) magic D3454

Next, the router is detected to have responded to the ECHOREQ with an ECHOREP and is preparing to send out an LQR: PPP Serial4: O LCP ECHOREP(A) id 3 (C) magic D21B4 PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48


DB-1825


The following is sample output from the debug ppp negotiation command. This is a normal negotiation, where both sides agree on Network Control Program (NCP) parameters. In this case, protocol type IP is proposed and acknowledged. Router# debug ppp negotiation ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8 ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 3D56CAC ppp: received config for type = 4 (QUALITYTYPE) acked ppp: received config for type = 5 (MAGICNUMBER) value = 3D567F8 acked (ok) PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5 ppp: config ACK received, type = 4 (CI_QUALITYTYPE), value = C025 ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 3D56CAC ppp: ipcp_reqci: returning CONFACK. (ok) PPP Serial4: state = ACKSENT fsm_rconfack(8021): rcvd id 4

Table 285 describes significant fields shown in the display. Table 285

debug ppp negotiation Field Descriptions

Field

Description

ppp


sending CONFREQ

Router sent a configuration request.

type = 4 (CI_QUALITYTYPE)

Type of LCP configuration option that is being negotiated and a descriptor. A type value of 4 indicates Quality Protocol negotiation; a type value of 5 indicates Magic Number negotiation.

value = C025/3E8

For Quality Protocol negotiation, indicates NCP type and reporting period. In the example, C025 indicates LQM; 3E8 is a hexadecimal value translating to about 10 seconds (in hundredths of a second).

value = 3D56CAC

For Magic Number negotiation, indicates the Magic Number being negotiated.

received config

Receiving node has received the proposed option negotiation for the indicated option type.

acked

Acknowledgment and acceptance of options.

state = ACKSENT

Specific PPP state in the negotiation process.

ipcp_reqci

IPCP notification message; sending CONFACK.

fsm_rconfack (8021)

Procedure fsm_rconfack processes received CONFACKs, and the protocol (8021) is IP.

The first two lines indicate that the router is trying to bring up LCP and will use the indicated negotiation options (Quality Protocol and Magic Number). The value fields are the values of the options themselves. C025/3E8 translates to Quality Protocol LQM. 3E8 is the reporting period (in hundredths of a second). 3D56CAC is the value of the Magic Number for the router. ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8 ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 3D56CAC


DB-1826

May 2008


The next two lines indicate that the other side negotiated for options 4 and 5 as requested and acknowledged both. If the responding end does not support the options, a CONFREJ is sent by the responding node. If the responding end does not accept the value of the option, a Configure-Negative-Acknowledge (CONFNAK) is sent with the value field modified. ppp: received config for type = 4 (QUALITYTYPE) acked ppp: received config for type = 5 (MAGICNUMBER) value = 3D567F8 acked (ok)

The next three lines indicate that the router received a CONFAK from the responding side and displays accepted option values. Use the rcvd id field to verify that the CONFREQ and CONFACK have the same ID field. PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5 ppp: config ACK received, type = 4 (CI_QUALITYTYPE), value = C025 ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 3D56CAC

The next line indicates that the router has IP routing enabled on this interface and that the IPCP NCP negotiated successfully: ppp: ipcp_reqci: returning CONFACK.

In the last line, the state of the router is listed as ACKSENT. PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5\

The following is sample output from when the debug ppp packet and debug ppp negotiation commands are enabled at the same time.


DB-1827


router# debug ppp negotiation router# debug ppp packet

This field shows a decimal representation of the Magic Number.

This field shows a decimal representation of the NCP value. This field shows a decimal representation of the reporting period.

This exchange represents a successful PPP negotiation for support of NCP type IPCP.

S2877

ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8 ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = D4C64 PPP Serial4: O LCP CONFREQ(1) id 4 (12) QUALITYTYPE (8) 192 37 0 0 3 232 MAGICNUMBER (6) 0 13 76 100 PPP Serial4(i): pkt type 0xC021, datagramsize 22 PPP Serial4: I LCP CONFREQ(1) id 4 (12) QUALITYTYPE (8) 192 37 0 0 3 232 MAGICNUMBER (6) 0 13 84 240 PPP Serial4: input(C021) state = REQSENT code = CONFREQ(1) id = 4 len = 18 ppp: received config for type = 4 (QUALITYTYPE) acked ppp: received config for type = 5 (MAGICNUMBER) value = D54F0 acked PPP Serial4: O LCP CONFACK(2) id 4 (12) QUALITYTYPE (8) 192 37 0 0 3 232 MAGICNUMBER (6) 0 13 84 240 (ok) PPP Serial4(i): pkt type 0xC021, datagramsize 22 PPP Serial4: I LCP CONFACK(2) id 4 (12) QUALITYTYPE (8) 192 37 0 0 3 232 MAGICNUMBER (6) 0 13 76 100 PPP Serial4: input(C021) state = ACKSENT code = CONFACK(2) id = 4 len = 18 PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 4 ppp: config ACK received, type = 4 (CI_QUALITYTYPE), value = C025 ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = D4C64 ipcp: sending CONFREQ, type = 3 (CI_ADDRESS), Address = 2.1.1.2 PPP Serial4: O IPCP CONFREQ(1) id 3 (10) Type3 (6) 2 1 1 2 PPP Serial4: I IPCP CONFREQ(1) id 3 (10) Type3 (6) 2 1 1 1 PPP Serial4(i): pkt type 0x8021, datagramsize 14 PPP Serial4: input(8021) state = REQSENT code = CONFREQ(1) id = 3 len = 10 ppp Serial4: Negotiate IP address: her address 2.1.1.1 (ACK) ppp: ipcp_reqci: returning CONFACK. PPP Serial4: O IPCP CONFACK(2) id 3 (10) Type3 (6) 2 1 1 1 (ok) PPP Serial4: I IPCP CONFACK(2) id 3 (10) Type3 (6) 2 1 1 2 PPP Serial4: input(8021) state = ACKSENT code = CONFACK(2) id = 3 len = 10 PPP Serial4: state = ACKSENT fsm_rconfack(8021): rcvd id 3 ipcp: config ACK received, type = 3 (CI_ADDRESS), Address = 2.1.1.2 PPP Serial4(o): lcp_slqr() state = OPEN magic = D4C64, len = 48 PPP Serial4(i): pkt type 0xC025, datagramsize 52 PPP Serial4(i): lcp_rlqr() state = OPEN magic = D54F0, len = 48 PPP Serial4(i): pkt type 0xC025, datagramsize 52 PPP Serial4(i): lcp_rlqr() state = OPEN magic = D54F0, len = 48 PPP Serial4(o): lcp_slqr() state = OPEN magic = D4C64, len = 48

The following is sample output from the debug ppp negotiation command when the remote side of the connection is unable to respond to LQM requests: Router# debug ppp negotiation ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp:

sending sending sending sending sending sending sending sending sending sending sending sending sending sending sending

CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ,

type type type type type type type type type type type type type type type

= = = = = = = = = = = = = = =

4 5 4 5 4 5 4 5 4 5 4 5 4 5 4

(CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE),

value value value value value value value value value value value value value value value

= = = = = = = = = = = = = = =

C025/3E8 44B7010 C025/3E8 44B7010 C025/3E8 44B7010 C025/3E8 44B7010 C025/3E8 44B7010 C025/3E8 44B7010 C025/3E8 44B7010 C025/3E8


DB-1828

May 2008


ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp: ppp:

sending sending sending sending sending sending sending sending sending

CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ, CONFREQ,

type type type type type type type type type

= = = = = = = = =

5 4 5 4 5 4 5 4 5

(CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER), (CI_QUALITYTYPE), (CI_MAGICNUMBER),

value value value value value value value value value

= = = = = = = = =

44B7010 C025/3E8 44B7010 C025/3E8 44B7010 C025/3E8 44B7010 C025/3E8 44C1488

The following is sample output when no response is detected for configuration requests (with both the debug ppp negotiation and debug ppp packet commands enabled): Router# debug ppp negotiation Router# debug ppp packet ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = PPP Serial4: O LCP CONFREQ(1) id 14 (12) QUALITYTYPE (8) MAGICNUMBER (6) 4 77 253 200 ppp: TIMEout: Time= 44E0980 State= 3 ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = PPP Serial4: O LCP CONFREQ(1) id 15 (12) QUALITYTYPE (8) MAGICNUMBER (6) 4 77 253 200 ppp: TIMEout: Time= 44E1828 State= 3 ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = PPP Serial4: O LCP CONFREQ(1) id 16 (12) QUALITYTYPE (8) MAGICNUMBER (6) 4 77 253 200 ppp: TIMEout: Time= 44E27C8 State= 3 ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = PPP Serial4: O LCP CONFREQ(1) id 17 (12) QUALITYTYPE (8) MAGICNUMBER (6) 4 77 253 200 ppp: TIMEout: Time= 44E3768 State= 3

C025/3E8 44DFDC8 192 37 0 0 3 232

C025/3E8 44DFDC8 192 37 0 0 3 232

C025/3E8 44DFDC8 192 37 0 0 3 232

C025/3E8 44DFDC8 192 37 0 0 3 232

The following is sample output from the debug ppp error command. These messages might appear when the Quality Protocol option is enabled on an interface that is already running PPP. Router# debug ppp error PPP Serial3(i): rlqr receive failure. successes = 15 PPP: myrcvdiffp = 159 peerxmitdiffp = 41091 PPP: myrcvdiffo = 2183 peerxmitdiffo = 1714439 PPP: threshold = 25 PPP Serial4(i): rlqr transmit failure. successes = 15 PPP: myxmitdiffp = 41091 peerrcvdiffp = 159 PPP: myxmitdiffo = 1714439 peerrcvdiffo = 2183 PPP: l->OutLQRs = 1 LastOutLQRs = 1 PPP: threshold = 25 PPP Serial3(i): lqr_protrej() Stop sending LQRs. PPP Serial3(i): The link appears to be looped back.


DB-1829



debug ppp error Field Descriptions

Field

Description

PPP


Serial3(i)

Interface number associated with this debugging information; indicates that this is an input packet.

rlqr receive failure

Request to negotiate the Quality Protocol option is not accepted.

myrcvdiffp = 159

Number of packets received over the time period.

peerxmitdiffp = 41091

Number of packets sent by the remote node over this period.

myrcvdiffo = 2183

Number of octets received over this period.

peerxmitdiffo = 1714439

Number of octets sent by the remote node over this period.

threshold = 25

Maximum error percentage acceptable on this interface. This percentage is calculated by the threshold value entered in the ppp quality number interface configuration command. A value of 100 – number (100 minus number) is the maximum error percentage. In this case, a number of 75 was entered. This means that the local router must maintain a minimum 75 percent non-error percentage, or the PPP link will be considered down.

OutLQRs = 1

Local router’s current send LQR sequence number.

LastOutLQRs = 1

The last sequence number that the remote node side has seen from the local node.

The following is sample output from the debug ppp authentication command. Use this command to determine why an authentication fails. Router# debug ppp authentication Serial0: Unable to authenticate. No name received from peer Serial0: Unable to validate CHAP response. USERNAME pioneer not found. Serial0: Unable to validate CHAP response. No password defined for USERNAME pioneer Serial0: Failed CHAP authentication with remote. Remote message is Unknown name Serial0: remote passed CHAP authentication. Serial0: Passed CHAP authentication with remote. Serial0: CHAP input code = 4 id = 3 len = 48


DB-1830

May 2008


In general, these messages are self-explanatory. Fields that can show optional output are outlined in Table 287. Table 287

debug ppp authentication Field Descriptions

Field

Description

Serial0

Interface number associated with this debugging information and CHAP access session in question.

USERNAME pioneer not found.

The name pioneer in this example is the name received in the CHAP response. The router looks up this name in the list of usernames that are configured for the router.

Remote message is Unknown name

The following messages can appear:

code = 4

•

No name received to authenticate

•

Unknown name

•

No secret for given name

•

Short MD5 response received

•

MD compare failed

Specific CHAP type packet detected. Possible values are as follows: •

1—Challenge

•

2—Response

•

3—Success

•

4—Failure

id = 3

ID number per LCP packet format.

len = 48

Packet length without header.

The following shows sample output from the debug ppp command using the cbcp keyword. This output depicts packet exchanges under normal PPP operation where the Cisco access server is waiting for the remote PC to respond to the MSCB request. The router also has debug ppp negotiation and service timestamps msec commands enabled. Router# debug ppp cbcp Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec

17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17

00:48:11.302: 00:48:11.306: 00:48:11.310: 00:48:11.314: 00:48:13.342: 00:48:13.346: 00:48:13.346: 00:48:13.350: 00:48:15.370: 00:48:15.374: 00:48:15.374: 00:48:15.378: 00:48:17.398: 00:48:17.402: 00:48:17.406: 00:48:17.406: 00:48:19.426: 00:48:19.430: 00:48:19.430:

As8 MCB: User mscb Callback Number - Client ANY Async8 PPP: O MCB Request(1) id 1 len 9 Async8 MCB: O 1 1 0 9 2 5 0 1 0 As8 MCB: O Request Id 1 Callback Type Client-Num As8 MCB: Timeout in state WAIT_RESPONSE Async8 PPP: O MCB Request(1) id 2 len 9 Async8 MCB: O 1 2 0 9 2 5 0 1 0 As8 MCB: O Request Id 2 Callback Type Client-Num As8 MCB: Timeout in state WAIT_RESPONSE Async8 PPP: O MCB Request(1) id 3 len 9 Async8 MCB: O 1 3 0 9 2 5 0 1 0 As8 MCB: O Request Id 3 Callback Type Client-Num As8 MCB: Timeout in state WAIT_RESPONSE Async8 PPP: O MCB Request(1) id 4 len 9 Async8 MCB: O 1 4 0 9 2 5 0 1 0 As8 MCB: O Request Id 4 Callback Type Client-Num As8 MCB: Timeout in state WAIT_RESPONSE Async8 PPP: O MCB Request(1) id 5 len 9 Async8 MCB: O 1 5 0 9 2 5 0 1 0

delay 0

delay 0

delay 0

delay 0


DB-1831


Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec

17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17 17

00:48:19.434: 00:48:21.454: 00:48:21.458: 00:48:21.462: 00:48:21.462: 00:48:23.482: 00:48:23.486: 00:48:23.490: 00:48:23.490: 00:48:25.510: 00:48:25.514: 00:48:25.514: 00:48:25.518: 00:48:26.242: 00:48:26.246: 00:48:26.250: 00:48:26.254: 00:48:26.258: 00:48:26.262: 00:48:26.266: 00:48:26.270: 00:48:26.270: 00:48:26.390: 00:48:26.390: 00:48:26.394: 00:48:26.402:

As8 MCB: O Request Id 5 Callback Type Client-Num delay 0 As8 MCB: Timeout in state WAIT_RESPONSE Async8 PPP: O MCB Request(1) id 6 len 9 Async8 MCB: O 1 6 0 9 2 5 0 1 0 As8 MCB: O Request Id 6 Callback Type Client-Num delay 0 As8 MCB: Timeout in state WAIT_RESPONSE Async8 PPP: O MCB Request(1) id 7 len 9 Async8 MCB: O 1 7 0 9 2 5 0 1 0 As8 MCB: O Request Id 7 Callback Type Client-Num delay 0 As8 MCB: Timeout in state WAIT_RESPONSE Async8 PPP: O MCB Request(1) id 8 len 9 Async8 MCB: O 1 8 0 9 2 5 0 1 0 As8 MCB: O Request Id 8 Callback Type Client-Num delay 0 As8 PPP: I pkt type 0xC029, datagramsize 18 Async8 PPP: I MCB Response(2) id 8 len 16 Async8 MCB: I 2 8 0 10 2 C C 1 32 34 39 32 36 31 As8 MCB: Received response As8 MCB: Response CBK-Client-Num 2 12 12, addr 1-2492613 Async8 PPP: O MCB Ack(3) id 9 len 16 Async8 MCB: O 3 9 0 10 2 C C 1 32 34 39 32 36 31 As8 MCB: O Ack Id 9 Callback Type Client-Num delay 12 As8 MCB: Negotiated MCB with peer As8 LCP: I TERMREQ [Open] id 4 len 8 (0x00000000) As8 LCP: O TERMACK [Open] id 4 len 4 As8 MCB: Peer terminating the link As8 MCB: Initiate Callback for mscb at 2492613 using Async

33

0

33

0

The following is sample output from the debug ppp compression command with service timestamps enabled and shows a typical PPP packet exchange between the router and Microsoft client where the MPPC header sequence numbers increment correctly: Router# debug ppp compression 00:04:14: 00:04:14: 00:04:14: 00:04:14: 00:04:14:

BR0:1 BR0:1 BR0:1 BR0:1 BR0:1

MPPC: MPPC: MPPC: MPPC: MPPC:

Decomp Decomp Decomp Decomp Decomp

-

hdr/exp_cc# hdr/exp_cc# hdr/exp_cc# hdr/exp_cc# hdr/exp_cc#

0x2003/0x0003 0x2004/0x0004 0x2005/0x0005 0x2006/0x0006 0x2007/0x0007


debug ppp compression Field Descriptions

Field

Description

interface

Interface enabled with MPPC.

Decomp - hdr/

Decompression header and bit settings.

exp_cc#

Expected coherency count.

0x2003

Received sequence number.

0x0003

Expected sequence number.


DB-1832

May 2008


The following shows sample output from debug ppp negotiation and debug ppp error commands, which can be used to troubleshoot initial PPP negotiation and setup errors. This example shows a virtual interface (virtual interface 1) during normal PPP operation and CCP negotiation. Router# debug ppp negotiation error Vt1 PPP: Unsupported or un-negotiated protocol. Link arp VPDN: Chap authentication succeeded for p5200 Vi1 PPP: Phase is DOWN, Setup Vi1 VPDN: Virtual interface created for [email protected] Vi1 VPDN: Set to Async interface Vi1 PPP: Phase is DOWN, Setup Vi1 VPDN: Clone from Vtemplate 1 filterPPP=0 blocking Vi1 CCP: Re-Syncing history using legacy method %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up Vi1 PPP: Treating connection as a dedicated line Vi1 PPP: Phase is ESTABLISHING, Active Open Vi1 LCP: O CONFREQ [Closed] id 1 len 25 Vi1 LCP: ACCM 0x000A0000 (0x0206000A0000) Vi1 LCP: AuthProto CHAP (0x0305C22305) Vi1 LCP: MagicNumber 0x000FB69F (0x0506000FB69F) Vi1 LCP: PFC (0x0702) Vi1 LCP: ACFC (0x0802) Vi1 VPDN: Bind interface direction=2 Vi1 PPP: Treating connection as a dedicated line Vi1 LCP: I FORCED CONFREQ len 21 Vi1 LCP: ACCM 0x000A0000 (0x0206000A0000) Vi1 LCP: AuthProto CHAP (0x0305C22305) Vi1 LCP: MagicNumber 0x12A5E4B5 (0x050612A5E4B5) Vi1 LCP: PFC (0x0702) Vi1 LCP: ACFC (0x0802) Vi1 VPDN: PPP LCP accepted sent & rcv CONFACK Vi1 PPP: Phase is AUTHENTICATING, by this end Vi1 CHAP: O CHALLENGE id 1 len 27 from "l_4000" Vi1 CHAP: I RESPONSE id 20 len 37 from "[email protected]" Vi1 CHAP: O SUCCESS id 20 len 4 Vi1 PPP: Phase is UP Vi1 IPCP: O CONFREQ [Closed] id 1 len 10 Vi1 IPCP: Address 15.2.2.3 (0x03060F020203) Vi1 CCP: O CONFREQ [Not negotiated] id 1 len 10 Vi1 CCP: MS-PPC supported bits 0x00000001 (0x120600000001) Vi1 IPCP: I CONFREQ [REQsent] id 1 len 34 Vi1 IPCP: Address 0.0.0.0 (0x030600000000) Vi1 IPCP: PrimaryDNS 0.0.0.0 (0x810600000000) Vi1 IPCP: PrimaryWINS 0.0.0.0 (0x820600000000) Vi1 IPCP: SecondaryDNS 0.0.0.0 (0x830600000000) Vi1 IPCP: SecondaryWINS 0.0.0.0 (0x840600000000) Vi1 IPCP: Using the default pool Vi1 IPCP: Pool returned 11.2.2.5 Vi1 IPCP: O CONFREJ [REQsent] id 1 len 16 Vi1 IPCP: PrimaryWINS 0.0.0.0 (0x820600000000) Vi1 IPCP: SecondaryWINS 0.0.0.0 (0x840600000000) Vi1 CCP: I CONFREQ [REQsent] id 1 len 15 Vi1 CCP: MS-PPC supported bits 0x00000001 (0x120600000001) Vi1 CCP: Stacker history 1 check mode EXTENDED (0x1105000104) Vi1 CCP: Already accepted another CCP option, rejecting this STACKER Vi1 CCP: O CONFREJ [REQsent] id 1 len 9 Vi1 CCP: Stacker history 1 check mode EXTENDED (0x1105000104) Vi1 IPCP: I CONFACK [REQsent] id 1 len 10 Vi1 IPCP: Address 15.2.2.3 (0x03060F020203) Vi1 CCP: I CONFACK [REQsent] id 1 len 10 Vi1 CCP: MS-PPC supported bits 0x00000001 (0x120600000001) Vi1 CCP: I CONFREQ [ACKrcvd] id 2 len 10 Vi1 CCP: MS-PPC supported bits 0x00000001 (0x120600000001)


DB-1833


Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1 Vi1

CCP: O CONFACK [ACKrcvd] id 2 len 10 CCP: MS-PPC supported bits 0x00000001 (0x120600000001) CCP: State is Open IPCP: I CONFREQ [ACKrcvd] id 2 len 22 IPCP: Address 0.0.0.0 (0x030600000000) IPCP: PrimaryDNS 0.0.0.0 (0x810600000000) IPCP: SecondaryDNS 0.0.0.0 (0x830600000000) IPCP: O CONFNAK [ACKrcvd] id 2 len 22 IPCP: Address 11.2.2.5 (0x03060B020205) IPCP: PrimaryDNS 171.69.1.148 (0x8106AB450194) IPCP: SecondaryDNS 171.69.2.132 (0x8306AB450284) IPCP: I CONFREQ [ACKrcvd] id 3 len 22 IPCP: Address 11.2.2.5 (0x03060B020205) IPCP: PrimaryDNS 171.69.1.148 (0x8106AB450194) IPCP: SecondaryDNS 171.69.2.132 (0x8306AB450284) IPCP: O CONFACK [ACKrcvd] id 3 len 22 IPCP: Address 11.2.2.5 (0x03060B020205) IPCP: PrimaryDNS 171.69.1.148 (0x8106AB450194) IPCP: SecondaryDNS 171.69.2.132 (0x8306AB450284) IPCP: State is Open IPCP: Install route to 11.2.2.5


DB-1834

May 2008

Debug Commands debug pppatm redundancy

debug pppatm redundancy To debug PPP over ATM (PPPoA) redundancy events on a dual route processor, high availablity (HA) system and display Cluster Control Manager (CCM) events and messages, use the debug pppatm redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command. debug pppatm redundancy no debug pppatm redundancy

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(31)SB2


12.2SX


Usage Guidelines

Note

The CCM provides the capability to facilitate and synchronize session bring up on the standby processor of a dual route processor HA system. Use the debug pppatm redundancy command to display CCM events and messages for PPPoA sessions on HA systems.

The debug pppatm redundancy command does not display output on the active processor during normal synchronization, that is, the command displays output on the active processor only during an error condition. This command is used only by Cisco engineers for internal debugging of CCM processes.

Examples

The following is sample output for the debug pppatm redundancy command from a Cisco 10000 Series router standby processor. No field descriptions are provided because command output is used for Cisco internal debugging purposes only. Router# debug pppatm redundancy *Dec 3 02:58:40.784: PPPATM HA: [14000001]: Received the first SHDB *Dec 3 02:58:40.784: PPPATM HA: [14000001]: Base hwidb not created > yet, queuing SHDB *Dec 3 02:58:40.784: PPPATM HA: [14000001]: Requesting base vaccess creation


DB-1835

Debug Commands debug pppatm

debug pppatm To enable debug reports for PPP over ATM (PPPoA) events, errors, and states, either globally or conditionally, on an interface or virtual circuit (VC), use the debug pppatm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug pppatm {event | error | state} [interface atm interface-number [subinterface-number]] vc {[vpi/vci]vci | virtual-circuit-name} no debug pppatm {event | error | state} [interface atm interface-number [subinterface-number] vc {[vpi/]vci | virtual-circuit-name}

Syntax Description

event

PPPoA events.

error

PPPoA errors.

state

PPPoA state.

interface atm interface-number [subinterface-number]

(Optional) Specifies a particular ATM interface by interface number and optionally a subinterface number separated by a period.

vc [vpi/]vci virtual-circuit-name

(Optional) Virtual circuit (VC) keyword followed by a virtual path identifier (VPI), virtual channel identifier (VCI), and VC name. A slash mark is required after the VPI.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T


12.2(28)SB


12.2SX


Usage Guidelines

Each specific PPPoA debug report must be requested on a separate command line; see the “Examples” section.

Examples

The following is example output of a PPPoA session with event, error, and state debug reports enabled on ATM interface 1/0.10: Router# debug pppatm event interface atm1/0.10 Router# debug pppatm error interface atm1/0.10 Router# debug pppatm state interface atm1/0.10


DB-1836

May 2008

Debug Commands debug pppatm

00:03:08: 00:03:08: 00:03:08: 00:03:08: 00:03:08: 00:03:08: 00:03:08: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:16: 00:03:27: 00:03:27: 00:03:27: 00:03:27: 00:03:27: 00:03:27: 00:03:27: 00:03:27:

PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM: PPPATM:

ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10 ATM1/0.10

0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101 0/101

[1], [1], [1], [1], [1], [0], [0], [0], [0], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2], [2],

Event Event Event Event Event State Event Event Event Event Event Event Event Event Event Event Event Event State Event State Event State Event Event Event Event Event Event Event State

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Clear Session Disconnecting AAA gets dynamic attrs AAA gets dynamic attrs SSS Cleanup DOWN Up Pending Up Dequeued Processing Up Access IE allocated Set Pkts to SSS AAA gets retrived attrs AAA gets nas port details AAA gets dynamic attrs AAA gets dynamic attrs AAA unique id allocated No AAA method list set SSS Request NAS_PORT_POLICY_INQUIRY SSS Msg Received = 1 PPP_START PPP Msg Received = 1 LCP_NEGOTIATION PPP Msg Received = 4 HW Switch support FORW = 0 Access IE get nas port AAA gets dynamic attrs AAA gets dynamic attrs PPP Msg Received = 5 Set Pkts to SSS FORWARDED


Related Commands

debug pppatm Field Descriptions

Field

Description

Event

Reports PPPoA events for use by Cisco engineering technical assistance personnel.

State

Reports PPPoA states for use by Cisco engineering technical assistance personnel.

Command

Description

atm pppatm passive

Places an ATM subinterface into passive mode.

show pppatm summary

Displays PPPoA session counts.


DB-1837

Debug Commands debug pppoe redundancy

debug pppoe redundancy To debug PPP over Ethernet (PPPoE) redundancy events on a dual route processor high availablity (HA) system and display Cluster Control Manager (CCM) events and messages, use the debug pppoe redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command. debug pppoe redundancy no debug ppp redundancy

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(31)SB2


12.2SX


Usage Guidelines

The CCM provides the capability to facilitate and synchronize session bring up on the standby processor of a dual route processor HA system.Use the debug pppoe redundancy command to display CCM events and messages for PPPoE sessions. This command is used only by Cisco engineers for internal debugging of CCM processes.

Examples

The following is sample output for the debug pppoe redundancy command from a Cisco 10000 Series router active processor. No field descriptions are provided because command output is used for Cisco internal debugging purposes only. Router# debug pppoe redundancy Nov Nov Nov Nov Nov Nov Nov Nov Nov Nov Nov Nov Nov Nov

22 22 22 22 22 22 22 22 22 22 22 22 22 22

17:21:11.327: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351: 17:21:11.351:

PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE PPPoE

HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008] HA[0xBE000008]

9: 9: 9: 9: 9: 9: 9: 9: 9: 9: 9: 9: 9: 9:

Session ready to sync data code = PADR, length = 58 code = SESSION ID, length = 2 code = SWITCH HDL, length = 4 code = SEGMENT HDL, length = 4 code = PHY SWIDB DESC, length = 20 code = VACCESS DESC, length = 28 Sync collection for ready events code = PADR, length = 58 code = SESSION ID, length = 2 code = SWITCH HDL, length = 4 code = SEGMENT HDL, length = 4 code = PHY SWIDB DESC, length = 20 code = VACCESS DESC, length = 28


DB-1838

May 2008

Debug Commands debug pppoe redundancy

The following is sample output for the debug pppoe redundancy command from a Cisco 10000 Series router standby processor: Router# debug pppoe redundancy Nov 22 17:21:11.448: PPPoE HA[0x82000008]: Recreating session: retrieving data Nov 22 17:21:11.464: PPPoE HA[0x82000008] 9: Session ready to sync data


DB-1839

Debug Commands debug pppoe

debug pppoe To display debugging information for PPP over Ethernet (PPPoE) sessions, use the debug pppoe command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug pppoe {data | errors | events | packets} [rmac remote-mac-address | interface type number [vc {[vpi/]vci | vc-name}] [vlan vlan-id]] no debug pppoe {data | errors | events | packets} [rmac remote-mac-address | interface type number [vc {[vpi/]vci | vc-name}] [vlan vlan-id]]

Syntax Description

data

Displays data packets of PPPoE sessions.

errors

Displays PPPoE protocol errors that prevent a session from being established, or displays errors that cause an established session to be closed.

events

Displays PPPoE protocol messages about events that are part of normal session establishment or shutdown.

packets

Displays each PPPoE protocol packet that is exchanged.

rmac remote-mac-address

(Optional) Remote MAC address. Debugging information for PPPoE sessions sourced from this address will be displayed.

interface type number

(Optional) Interface for which PPPoE session debugging information will be displayed.

vc

(Optional) Displays debugging information for PPPoE sessions for a specific permanent virtual circuit (PVC).

vpi/

(Optional) ATM network virtual path identifier (VPI) for the PVC. In the absence of the slash (/) and a vpi value, the vpi value defaults to 0.

vci

(Optional) ATM network virtual channel identifier (VCI) for the PVC.

vc-name

(Optional) Name of the PVC.

vlan vlan-id

(Optional) IEEE 802.1Q VLAN identifier.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T

This command was introduced. This command replaces the debug vpdn pppoe-data, debug vpdn pppoe-error, debug vpdn pppoe-events, and debug vpdn pppoe-packet commands available in previous Cisco IOS releases.

12.2(15)T

This command was modified to display debugging information on a per-MAC address, per-interface, and per-VC basis.

12.3(2)T

The vlan vlan-id keyword and argument were added.

12.3(7)XI3

This command was integrated into Cisco IOS Release 12.3(7)XI3.


DB-1840

May 2008


Examples

Release

Modification

12.2(28)SB


12.2SX


The following examples show sample output from the debug pppoe command: Router# debug pppoe events interface atm1/0.10 vc 101 PPPoE protocol events debugging is on Router# 00:41:55:PPPoE 0:I PADI R:00b0.c2e9.c470 L:ffff.ffff.ffff 0/101 ATM1/0.10 00:41:55:PPPoE 0:O PADO, R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.10 00:41:55:PPPoE 0:I PADR R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.10 00:41:55:PPPoE :encap string prepared 00:41:55:[3]PPPoE 3:Access IE handle allocated 00:41:55:[3]PPPoE 3:pppoe SSS switch updated 00:41:55:[3]PPPoE 3:AAA unique ID allocated 00:41:55:[3]PPPoE 3:No AAA accounting method list 00:41:55:[3]PPPoE 3:Service request sent to SSS 00:41:55:[3]PPPoE 3:Created R:0001.c9f0.0c1c L:00b0.c2e9.c470 0/101 ATM1/0.10 00:41:55:[3]PPPoE 3:State REQ_NASPORT Event MORE_KEYS 00:41:55:[3]PPPoE 3:O PADS R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.10 00:41:55:[3]PPPoE 3:State START_PPP Event DYN_BIND 00:41:55:[3]PPPoE 3:data path set to PPP 00:41:57:[3]PPPoE 3:State LCP_NEGO Event PPP_LOCAL 00:41:57:PPPoE 3/SB:Sent vtemplate request on base Vi2 00:41:57:[3]PPPoE 3:State CREATE_VA Event VA_RESP 00:41:57:[3]PPPoE 3:Vi2.1 interface obtained 00:41:57:[3]PPPoE 3:State PTA_BIND Event STAT_BIND 00:41:57:[3]PPPoE 3:data path set to Virtual Acess 00:41:57:[3]PPPoE 3:Connected PTA Router# debug pppoe errors interface atm1/0.10 PPPoE protocol errors debugging is on Router# 00:44:30:PPPoE 0:Max session count(1) on mac(00b0.c2e9.c470) reached. 00:44:30:PPPoE 0:Over limit or Resource low. R:00b0.c2e9.c470 L:ffff.ffff.ffff 0/101 ATM1/0.10


debug pppoe Field Descriptions

Field

Description

PPPoE

PPPoE debug message header.

0:

PPPoE session ID.

I PADI

Incoming PPPoE Active Discovery Initiation packet.

R:

Remote MAC address.

L:

Local MAC address.

0/101

Virtual path identifier (VPI)/virtual channel identifier (VCI) of the PVC.


DB-1841


Table 290

Related Commands

debug pppoe Field Descriptions (continued)

Field

Description

ATM1/0.10

Interface type and number.

O PADO

Outgoing PPPoE Active Discovery Offer packet.

I PADR

Incoming PPPoE Active Discovery Request packet.

[3]

Unique user session ID. The same ID is used for identifying sessions across different applications such as PPPoE, PPP, Layer 2 Tunneling Protocol (L2TP), and Subscriber Service Switch (SSS). The same session ID appears in the output for the show pppoe session, show sss session, and show vpdn session commands.

PPPoE 3

PPPoE session ID.

Created

PPPoE session is created.

O PADS

Outgoing PPPoE Active Discovery Session-confirmation packet.

Connected PTA

PPPoE session is established.

Max session count(1) on mac(00b0.c2e9.c470) reached

PPPoE session is rejected because of per-MAC session limit.

Command

Description

encapsulation aal5autoppp virtual-template

Enables PPPoA/PPPoE autosense.

pppoe enable

Enables PPPoE sessions on an Ethernet interface or subinterface.

protocol pppoe (ATM VC)

Enables PPPoE sessions to be established on PVCs.

show pppoe session

Displays information about active PPPoE sessions.

show sss session

Displays Subscriber Service Switch session status.

show vpdn session

Displays session information about L2TP, L2F protocol, and PPPoE tunnels in a VPDN.


DB-1842

May 2008

Debug Commands debug presence

debug presence To display debugging information about the presence service, use the debug presence command in privileged EXEC mode. To disable debugging messages, use the no form of this command. debug presence {all | asnl | errors | event | info | timer | trace | xml} no debug presence {all | asnl | errors | event | info | timer | trace | xml}

Syntax Description

all

Displays all presence debugging messages.

asnl

Displays trace event logs in the Application Subscribe Notify Layer (ASNL).

errors

Displays presence error messages.

event

Displays presence event messages.

info

Displays general information about presence service.

timer

Displays presence timer information.

trace

Displays a trace of all presence activities.

xml

Displays messages related to the eXtensible Markup Language (XML) parser for presence service.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(11)XJ


12.2SX


Examples

The following example shows output from the debug presence asnl command: Router# debug presence asnl *Sep 4 07:15:24.295: *Sep 4 07:15:24.295: send NOTIFY *Sep 4 07:15:24.295: *Sep 4 07:15:24.299: *Sep 4 07:15:24.299: *Sep 4 07:15:24.299: *Sep 4 07:15:24.299: send NOTIFY *Sep 4 07:15:24.299: *Sep 4 07:15:24.299: *Sep 4 07:15:24.299: *Sep 4 07:15:24.299: *Sep 4 07:15:24.299: send NOTIFY *Sep 4 07:15:24.299: *Sep 4 07:15:24.299:

//PRESENCE:[17]:/presence_get_sccp_status: line is closed //PRESENCE:[17]:/presence_handle_line_update: line status changes, //PRESENCE:[17]:/presence_set_line_status: new line status [busy ] //PRESENCE:[17]:/presence_asnl_callback: type [5] //PRESENCE:[17]:/presence_asnl_callback: ASNL_RESP_NOTIFY_DONE //PRESENCE:[24]:/presence_get_sccp_status: line is closed //PRESENCE:[24]:/presence_handle_line_update: line status changes, //PRESENCE:[24]:/presence_set_line_status: new line status [busy ] //PRESENCE:[24]:/presence_asnl_callback: type [5] //PRESENCE:[24]:/presence_asnl_callback: ASNL_RESP_NOTIFY_DONE //PRESENCE:[240]:/presence_get_sccp_status: line is closed //PRESENCE:[240]:/presence_handle_line_update: line status changes, //PRESENCE:[240]:/presence_set_line_status: new line status [busy ] //PRESENCE:[766]:/presence_get_sccp_status: line is closed


DB-1843


*Sep 4 07:15:24.299: send NOTIFY *Sep 4 07:15:24.299: *Sep 4 07:15:24.359: *Sep 4 07:15:24.359: *Sep 4 07:15:24.811: *Sep 4 07:15:24.811: *Sep 4 07:15:26.719: *Sep 4 07:15:26.719: send NOTIFY *Sep 4 07:15:26.719: *Sep 4 07:15:26.719: *Sep 4 07:15:26.719: *Sep 4 07:15:26.719: *Sep 4 07:15:26.719: send NOTIFY *Sep 4 07:15:26.719: *Sep 4 07:15:26.723: *Sep 4 07:15:26.723:

//PRESENCE:[766]:/presence_handle_line_update: line status changes, //PRESENCE:[766]:/presence_set_line_status: new line status [busy ] //PRESENCE:[766]:/presence_asnl_callback: type [5] //PRESENCE:[766]:/presence_asnl_callback: ASNL_RESP_NOTIFY_DONE //PRESENCE:[240]:/presence_asnl_callback: type [5] //PRESENCE:[240]:/presence_asnl_callback: ASNL_RESP_NOTIFY_DONE //PRESENCE:[17]:/presence_get_sccp_status: line is open //PRESENCE:[17]:/presence_handle_line_update: line status changes, //PRESENCE:[17]:/presence_set_line_status: new line status [idle ] //PRESENCE:[17]:/presence_asnl_callback: type [5] //PRESENCE:[17]:/presence_asnl_callback: ASNL_RESP_NOTIFY_DONE //PRESENCE:[24]:/presence_get_sccp_status: line is open //PRESENCE:[24]:/presence_handle_line_update: line status changes, //PRESENCE:[24]:/presence_set_line_status: new line status [idle ] //PRESENCE:[24]:/presence_asnl_callback: type [5] //PRESENCE:[24]:/presence_asnl_callback: ASNL_RESP_NOTIFY_DONE

The following example shows output from the debug presence event command: Router# debug presence event *Sep *Sep code *Sep code *Sep code *Sep code *Sep *Sep code *Sep code *Sep code *Sep code

4 07:16:02.715: 4 07:16:02.723: [29] 4 07:16:02.723: [29] 4 07:16:02.791: [17] 4 07:16:02.791: [17] 4 07:16:04.935: 4 07:16:04.943: [29] 4 07:16:04.943: [29] 4 07:16:04.995: [17] 4 07:16:04.999: [17]

//PRESENCE:[0]:/presence_sip_line_update: SIP nothing to update //PRESENCE:[17]:/presence_handle_notify_done: sip stack response //PRESENCE:[24]:/presence_handle_notify_done: sip stack response //PRESENCE:[240]:/presence_handle_notify_done: sip stack response //PRESENCE:[766]:/presence_handle_notify_done: sip stack response //PRESENCE:[0]:/presence_sip_line_update: SIP nothing to update //PRESENCE:[17]:/presence_handle_notify_done: sip stack response //PRESENCE:[24]:/presence_handle_notify_done: sip stack response //PRESENCE:[240]:/presence_handle_notify_done: sip stack response //PRESENCE:[766]:/presence_handle_notify_done: sip stack response

The following example shows output from the debug presence info command: Router# debug presence info *Sep 4 07:16:20.887: //PRESENCE:[17]:/presence_handle_line_update: get line status from ccvdbPtr *Sep 4 07:16:20.887: //PRESENCE:[17]:/presence_get_sccp_status: dn_tag 2 *Sep 4 07:16:20.887: //PRESENCE:[16]:/presence_start_element_handler: line 1: unknown element *Sep 4 07:16:20.887: //PRESENCE:[16]:/presence_start_element_handler: line 1: unknown element *Sep 4 07:16:20.887: //PRESENCE:[16]:/presence_start_element_handler: line 1: unknown element *Sep 4 07:16:20.887: //PRESENCE:[16]:/presence_start_element_handler: line 1: unknown element *Sep 4 07:16:20.887: //PRESENCE:[16]:/presence_start_element_handler: line 1: unknown element


DB-1844

May 2008


*Sep 4 07:16:20.887: //PRESENCE:[16]:/presence_start_element_handler: line 1: unknown element *Sep 4 07:16:20.887: //PRESENCE:[16]:/presence_start_element_handler: line 1: unknown element *Sep 4 07:16:20.887: *Sep 4 07:16:20.887: ccvdbPtr *Sep 4 07:16:20.887: *Sep 4 07:16:20.891: element

//PRESENCE:[0]:/presence_asnl_free_resp: //PRESENCE:[24]:/presence_handle_line_update: get line status from //PRESENCE:[24]:/presence_get_sccp_status: dn_tag 2 //PRESENCE:[23]:/presence_start_element_handler: line 1: unknown

The following example shows output from the debug presence timer command: Router# debug presence timer *Sep 3600 *Sep 3600 *Sep 607 *Sep 602 *Sep 3600 *Sep 3600 *Sep 605 *Sep 600

4 07:16:41.271: //PRESENCE:[17]:/presence_asnl_notify_body_handler: expires time 4 07:16:41.271: //PRESENCE:[24]:/presence_asnl_notify_body_handler: expires time 4 07:16:41.271: //PRESENCE:[240]:/presence_asnl_notify_body_handler: expires time 4 07:16:41.275: //PRESENCE:[766]:/presence_asnl_notify_body_handler: expires time 4 07:16:43.331: //PRESENCE:[17]:/presence_asnl_notify_body_handler: expires time 4 07:16:43.331: //PRESENCE:[24]:/presence_asnl_notify_body_handler: expires time 4 07:16:43.331: //PRESENCE:[240]:/presence_asnl_notify_body_handler: expires time 4 07:16:43.331: //PRESENCE:[766]:/presence_asnl_notify_body_handler: expires time

The following example shows output from the debug presence trace command: Router# debug presence trace *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep *Sep

4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

07:16:56.191: 07:16:56.191: 07:16:56.191: 07:16:56.191: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.199: 07:16:56.203: 07:16:56.203: 07:16:56.203: 07:16:59.743: 07:16:59.743: 07:16:59.743: 07:16:59.743:

//PRESENCE:[17]:/presence_line_update: //PRESENCE:[24]:/presence_line_update: //PRESENCE:[240]:/presence_line_update: //PRESENCE:[766]:/presence_line_update: //PRESENCE:[17]:/presence_get_node_by_subid: //PRESENCE:[17]:/presence_handle_line_update: //PRESENCE:[17]:/presence_get_sccp_status: //PRESENCE:[17]:/presence_asnl_notify_body_handler: //PRESENCE:[24]:/presence_get_node_by_subid: //PRESENCE:[24]:/presence_handle_line_update: //PRESENCE:[24]:/presence_get_sccp_status: //PRESENCE:[24]:/presence_asnl_notify_body_handler: //PRESENCE:[240]:/presence_get_node_by_subid: //PRESENCE:[240]:/presence_handle_line_update: //PRESENCE:[240]:/presence_get_sccp_status: //PRESENCE:[240]:/presence_asnl_notify_body_handler: //PRESENCE:[766]:/presence_get_node_by_subid: //PRESENCE:[766]:/presence_handle_line_update: //PRESENCE:[766]:/presence_get_sccp_status: //PRESENCE:[766]:/presence_asnl_notify_body_handler: //PRESENCE:[17]:/presence_line_update: //PRESENCE:[24]:/presence_line_update: //PRESENCE:[240]:/presence_line_update: //PRESENCE:[766]:/presence_line_update:


DB-1845


The following example shows output from the debug presence trace command: Router# debug presence trace *Sep 4 07:17:17.351: //PRESENCE:[17]:/presence_xml_encode: *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_presence: keyword = presence *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_person: keyword = person *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_generic: keyword = Closed *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_activities: keyword = activities *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_otp: keyword = On-the-phone *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_tuple: keyword = tuple *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_status: keyword = status *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_generic: keyword = Closed *Sep 4 07:17:17.355: //PRESENCE:[17]:/xml_encode_otp: keyword = On-the-phone *Sep 4 07:17:17.355: Closed Closed

Related Commands

Command

Description

presence

Enables presence service on the router and enters presence configuration mode.

presence enable

Allows the router to accept incoming presence requests.

show presence global

Displays configuration information about the presence service.

show presence subscription

Displays information about active presence subscriptions.


DB-1846

May 2008

Debug Commands debug priority

debug priority To display priority queueing output, use the debug priority command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug priority no debug priority

Syntax Description


Command Modes

Privileged EXEC

Examples

The following example shows how to enable priority queueing output: Router# debug priority Priority output queueing debugging is on

The following is sample output from the debug priority command when the Frame Relay PVC Interface Priority Queueing (FR PIPQ) feature is configured on serial interface 0: Router# debug priority 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0 00:49:05:PQ:Serial0

Related Commands

dlci 100 -> high output (Pk size/Q 24/0) dlci 100 -> high output (Pk size/Q 24/0) dlci 100 -> high output (Pk size/Q 24/0) dlci 200 -> medium output (Pk size/Q 24/1) dlci 300 -> normal output (Pk size/Q 24/2) dlci 400 -> low output (Pk size/Q 24/3)

Command

Description

debug custom-queue

Displays custom queueing output.


DB-1847

Debug Commands debug private-hosts

debug private-hosts To enable debug messages for the Private Hosts feature, use the debug private-hosts command in privileged EXEC mode. debug private-hosts {all | events | acl | api}

Syntax Description

all

Enable debug messages for all Private Hosts errors and events.

events

Enable debug messages for issues related to Private Hosts events.

acl

Enable debug messages for issues and events related to ACLs.

api

Enable debug messages for issues related to the application programming interface.

Defaults

This command has no default settings.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRB


12.2SX


Examples

The following example shows sample command output: Router# debug private-hosts private-hosts private-hosts Router#

Related Commands

private-hosts all events debugging is on api debugging is on acl debugging is on

Command

Description

debug fm private-hosts Enables debug messages for the Private Hosts feature manager.


DB-1848

May 2008

Debug Commands debug proxy h323 statistics

debug proxy h323 statistics To enable proxy RTP statistics, use the debug proxy h323 statistics command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug proxy h323 statistics no debug proxy h323 statistics

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(2)NA


12.2SX


Usage Guidelines

Enter the show proxy h323 detail-call EXEC command to see the statistics.


DB-1849

Debug Commands debug pvcd

debug pvcd To display the permanent virtual circuit (PVC) Discovery events and Interim Local Management Interface (ILMI) MIB traffic used when discovering PVCs, use the debug pvcd command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug pvcd no debug pvcd

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command is primarily used by Cisco technical support representatives.

Examples

The following is sample output from the debug pvcd command: Router# debug pvcd PVCD: PVCD enabled w/ Subif PVCD(2/0): clearing event queue PVCD: 2/0 Forgetting discovered PVCs... PVCD: Removing all dynamic PVCs on 2/0 PVCD: Restoring MIXED PVCs w/ default parms on 2/0 PVCD: Marking static PVCs as UNKNWN on 2/0 PVCD: Marking static PVC 0/50 as UNKNWN on 2/0 ... PVCD: Trying to discover PVCs on 2/0... PVCD: pvcd_discoverPVCs PVCD: pvcd_ping PVCD: fPortEntry.5.0 = 2 PVCD: pvcd_getPeerVccTableSize PVCD: fLayerEntry.5.0 = 13 PVCD:end allocating VccTable size 13 PVCD: pvcd_getPeerVccTable PVCD:******* 2/0: getNext on fVccEntry = NULL TYPE/VALUE numFileds = 19 numVccs = 13 PVCD: Creating Dynamic PVC 0/33 on 2/0 PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/33: DYNAMIC PVCD: After _create_pvc() VC 0/33: DYNAMIC0/33 on 2/0 : UBR PCR = -1 PVCD: Creating Dynamic PVC 0/34 on 2/0 PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/34: DYNAMIC PVCD: After _create_pvc() VC 0/34: DYNAMIC0/34 on 2/0 : UBR PCR -1 PVCD: Creating Dynamic PVC 0/44 on 2/0 PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/44: DYNAMIC PVCD: After _create_pvc() VC 0/44: DYNAMIC0/44 on 2/0 : UBR PCR = -1 PVCD: PVC 0/50 with INHERITED_QOSTYPE PVCD: _oi_state_change ( 0/50, 1 = ILMI_VC_UP ) PVCD: Creating Dynamic PVC 0/60 on 2/0 PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/60: DYNAMIC PVCD: After _create_pvc() VC 0/60: DYNAMIC0/60 on 2/0 : UBR PCR = -1 PVCD: Creating Dynamic PVC 0/80 on 2/0


DB-1850

May 2008

Debug Commands debug pvcd

PVCD(2/0): Before _update_inheritance() and _create_pvc() VC 0/80: DYNAMIC PVCD: After _create_pvc() VC 0/80: DYNAMIC0/80 on 2/0 : UBR PCR = -1 PVCD: Creating Dynamic PVC 0/99 on 2/0


DB-1851

Debug Commands debug pvdm2dm

debug pvdm2dm To view contents of packets flowing through PVDMII-xxDM digital modem devices, use the debug pvdm2dm command in privileged EXEC mode. To disable debug activity, use the no form of this command. debug pvdm2dm packet / no debug pvdm2dm

Syntax Description

packet

Debugs packets

modem

Debugs modem packets

pvdm

Debugs PVDM packets

slot

Router slot for pvdms/modems

port

Modem number

pvdm slot

PVDM number

Command Default

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T


12.2SX


Usage Guidelines

To debug the contents of modem packets for a specific modem, use the following command: •

debug pvdm2dm packet modem /

By removing the specific modem number at the end, one can enable packet debugging for all the modems available on the router: •

debug pvdm2dm packet modem

The following command enables packet debugging for all packets flowing through a particular PVDMII-xxDM device: •

debug pvdm2dm packet pvdm /

The following command enables debugging of packets flowing through any PVDMII-xxDM device: •

debug pvdm2dm packet pvdm

The following command enables debugging of packets flowing through any PVDMII-xxDM device and any PVDMII-xxDM-based modem channel:


DB-1852

May 2008

Debug Commands debug pvdm2dm

•

debug pvdm2dm packet

To see what debug flags are set, and to view the contents of debugged packets, use the show debugging command.

Examples

The following example sets debugging for a specific modem. The following show debugging command displays the debug flag that is set, and gives a typical printout for one debugged packet: Router# debug pvdm2dm packet modem 0/322 Router# show debugging PVDM2 DM: Modem 0/322 packet debugging is on Router# May 24 17:35:16.318: pvdm2_dm_tx_dsp_pak_common: bay 0, dsp 0 May 24 17:35:16.318: pvdm2_dm_dump_pak_hex: pak: 43E1F6FC size 8 May 24 17:35:16.318: 00 08 00 00 00 1C 00 00 May 24 17:35:16.322:

The following example sets debugging for all PVDMII-xxDM modems available on the router. Router# debug pvdm2dm packet Router# show debugging PVDM2 DM: Modem 0/322 packet debugging Modem 0/323 packet debugging Modem 0/324 packet debugging . . . Modem 0/355 packet debugging Modem 0/356 packet debugging Modem 0/357 packet debugging Router#

is on is on is on

is on is on is on

The following example sets debugging for a particular PVDMII-xxDM device. Router# debug pvdm2dm packet pvdm 0/0 Router# show debugging PVDM2 DM: PVDM2 0/0 packet debugging is on Router#

The following example sets debugging for all PVDMII-xxDM devices in the router. Router# debug pvdm2dm packet Router# show debugging PVDM2 DM: PVDM2 0/0 packet debugging PVDM2 0/1 packet debugging PVDM2 0/2 packet debugging Router#

pvdm

is on is on is on

In all of these examples, the output describing the debugged packets is similar to that of the first example, except that the packet contents will vary.

Related Commands

Command

Description

show debugging

Displays information about the type of debugging enabled for your router.


DB-1853

Debug Commands debug pxf atom

debug pxf atom To display debug messages relating to Parallel eXpress Forwarding (PXF) Any Transport over MPLS (AToM), use the debug pxf atom command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf atom [ac | mpls] no debug pxf atom [ac | mpls]

Syntax Description

ac

(Optional) Displays AToM information related to attachment circuit (AC) events.

mpls

(Optional) Displays AToM information related to MPLS Forwarding Infrastructure (MFI) events.

Command Default

Disabled (debugging is not enabled).

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF AToM AC events debug messages: Router# debug pxf atom ac PXF ATOM AC debugging is on

Related Commands

Command

Description

show mpls l2transport Displays information about AToM virtual circuits (VCs) that have been enabled to route Layer 2 packets on a router, including platform-independent AToM status and capabilities of a particular interface. show mpls l2transport Displays information about AToM VCs that are enabled to route Layer 2 vc packets on a router. show pxf cpu atom

Displays PXF AToM information for an interface or VCCI.

show pxf cpu mpls label

Displays PXF forwarding information for a label.

show pxf cpu statistics Displays PXF CPU AToM statistics. atom


DB-1854

May 2008

Debug Commands debug pxf backwalks

debug pxf backwalks To display debug messages relating to Parallel eXpress Forwarding (PXF) backwalk requests, use the debug pxf backwalks command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf backwalks no debug pxf backwalks

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF backwalk requests debug messages: Router# debug pxf backwalks PXF BACKWALK debugging is on

Related Commands

Command

Description

show pxf cpu statistics Displays PXF CPU backwalk requests statistics. backwalk


DB-1855

Debug Commands debug pxf bba

debug pxf bba To display debug messages relating to Parallel eXpress Forwarding (PXF) Broadband Access Aggregation (BBA) features, use the debug pxf bba command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf bba [ac sh_counter | ac sh_error | ac sh event | elog | l2f startstop debug | l2x fh error | l2x fh event | l2x sh counter | l2x sh error | l2x sh event | lt sh error | lt sh event] no debug pxf bba [ac sh_counter | ac sh_error | ac sh event | elog | l2f startstop debug | l2x fh error | l2x fh event | l2x sh counter | l2x sh error | l2x sh event | lt sh error | lt sh event]

Syntax Description

ac_sh_counter

(Optional) Displays attachment circuit (AC) segment counters.

ac_sh_error

(Optional) Displays AC segment errors.

ac_sh_event

(Optional) Displays AC segment events.

elog

(Optional) Displays event logging messages.

l2f_startstop_debug

(Optional) Displays Layer 2 Forwarding (L2F) tunneling events.

l2x_fh_error

(Optional) Displays L2F/L2TP (L2x) feature errors.

l2x_fh_event

(Optional) Displays L2x feature events.

l2x_sh_counter

(Optional) Displays L2x segment counters.

l2x_sh_error

(Optional) Displays L2x segment errors.

l2x_sh_event

(Optional) Displays L2x segment events.

lt_sh_error

(Optional) Displays LT segment errors.

lt_sh_event

(Optional) Displays LT segment events.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display AC segment counters debug messages: Router# debug pxf bba ac_sh_counter AC segment counters debugging is on *Jan 19 13:18:26.698: c10k_get_ac_segment_counters: pppox vcci 2709 rx pkts = 0 rx byte = 0 tx pkts = 0 tx bytes = 0 *Jan 19 13:18:26.698: c10k_get_ac_segment_counters: pppox vcci 2709 tx drop pkts


DB-1856

May 2008

Debug Commands debug pxf bba

= 0 tx *Jan 19 rx byte *Jan 19 = 0 tx *Jan 19 rx byte *Jan 19 = 0 tx *Jan 19 rx byte . . .

drop bytes = 0 13:18:26.698: c10k_get_ac_segment_counters: = 0 tx pkts = 0 tx bytes = 0 13:18:26.698: c10k_get_ac_segment_counters: drop bytes = 0 13:18:36.698: c10k_get_ac_segment_counters: = 0 tx pkts = 0 tx bytes = 0 13:18:36.698: c10k_get_ac_segment_counters: drop bytes = 0 13:18:36.698: c10k_get_ac_segment_counters: = 0 tx pkts = 0 tx bytes = 0

pppox vcci 2710 rx pkts = 0 pppox vcci 2710 tx drop pkts pppox vcci 2709 rx pkts = 0 pppox vcci 2709 tx drop pkts pppox vcci 2710 rx pkts = 0

The following example shows how to display L2F tunneling debug messages: Router# debug pxf bba l2f_startstop_debug L2F feature debugging is on *Jan 20 12:04:18.976: hwcnts.rx_pkts :0 hwcnts.rx_bytes :0 hwcnts.tx_pkts :0 hwcnts.tx_bytes: 0 hwcnts.tx_drop_pkts :0 hwcnts.tx_drop_bytes: 0 pcntrs->rx_pkts: 0 pcntrs->rx_bytes: 0 pcntrs->tx_pkts: 0 pcntrs->tx_bytes: 0 pcntrs->tx_drop_pkts: 0 pcntrs->tx_drop_bytes: 0 *Jan 20 12:04:18.976: hwcnts.rx_pkts :0 hwcnts.rx_bytes :0 hwcnts.tx_pkts :0 hwcnts.tx_bytes: 0 hwcnts.tx_drop_pkts :0 hwcnts.tx_drop_bytes: 0 pcntrs->rx_pkts: 0 pcntrs->rx_bytes: 0 pcntrs->tx_pkts: 0 pcntrs->tx_bytes: 0 pcntrs->tx_drop_pkts: 0 pcntrs->tx_drop_bytes: 0 . . .

Related Commands

Command

Description

show pxf cpu bba

Displays PXF CPU (RP) BBA information.


DB-1857

Debug Commands debug pxf cef

debug pxf cef To display debug messages relating to Parallel eXpress Forwarding (PXF) Cisco Express Forwarding (CEF), use the debug pxf cef command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf cef [fibroot | rpf] no debug pxf cef [fibroot | rpf]

Syntax Description

fibroot

Displays PXF CEF Forwarding Information Base (FIB) root information.

rpf

Displays PXF CEF Reverse Path Forwarding (RPF) information.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF CEF debug messages: Router# debug pxf cef PXF CEF debugging is on

Related Commands

Command

Description

show ip cef

Displays summary information about the FIB entries.

show pxf cpu cef

Displays PXF CPU memory usage, CEF, and External Column Memory (XCM) information.


DB-1858

May 2008

Debug Commands debug pxf dma

debug pxf dma To display debug messages relating to Parallel eXpress Forwarding (PXF) direct memory access (DMA) operations, use the debug pxf dma command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf dma no debug pxf dma

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(7)XI


12.2(31)SB


12.2SX


Examples

The following example shows how to display PXF DMA ASIC debug messages: Router# debug pxf dma PXF DMA *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4 *Jan 4

ASIC debugging is on 08:05:06.314: get ftbb 08:05:06.814: get ftbb 08:05:07.314: get ftbb 08:05:07.814: get ftbb 08:05:08.314: get ftbb 08:05:08.814: get ftbb 08:05:09.314: get ftbb 08:05:09.814: get ftbb 08:05:10.314: get ftbb 08:05:10.814: get ftbb 08:05:11.314: get ftbb 08:05:11.814: get ftbb 08:05:12.314: get ftbb 08:05:12.814: get ftbb 08:05:13.314: get ftbb 08:05:13.814: get ftbb 08:05:14.314: get ftbb 08:05:14.814: get ftbb 08:05:14.982: Entering 08:05:14.982: Packet 08:05:14.982: Header

reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 reg: slot 3, subslot 1 c10k_cobalt_send. decode: datagramstart 0x0A0301BE length 76 decode: Chan 0, VCCI 2515


DB-1859

Debug Commands debug pxf dma

*Jan *Jan *Jan . . .

Related Commands

4 08:05:14.982: 4 08:05:14.982: 4 08:05:14.982:

Header decode: flags 0x0001 c10k_cobalt_send: Checked the idb state. c10k_cobalt_send: Checked the FromRP Q count.

Command

Description

show pxf dma

Displays the current state of the DMA buffers, error counters, and registers on the PXF.


DB-1860

May 2008

Debug Commands debug pxf iedge

debug pxf iedge To display debug messages relating to Parallel eXpress Forwarding (PXF) Intelligent Edge (iEdge) operations, use the debug pxf iedge command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf iedge [stats] no debug pxf iedge [stats]

Syntax Description

stats

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

(Optional) Includes PXF iEdge statistics in the output.

The following example shows how to display PXF iEdge debug messages: Router# debug pxf iedge iEdge Feature Debug debugging is on

Related Commands

Command

Description

show pxf cpu iedge

Displays PXF iEdge information for an interface or policy.


DB-1861

Debug Commands debug pxf ipv6

debug pxf ipv6 To display debug messages relating to Parallel eXpress Forwarding (PXF) IPv6 provisioning, use the debug pxf ipv6 command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf ipv6 [acl | fib | hash] no debug pxf ipv6 [acl | fib | hash]

Syntax Description

acl

(Optional) Displays PXF IPv6 access control list (ACL) information.

fib

(Optional) Displays PXF Forwarding Information Base (FIB) information.

hash

(Optional) Displays PXF IPv6 hash information.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF IPv6 ACL debug messages: Router# debug pxf ipv6 acl PXF IPV6 ACL debugging is on

Related Commands

Command

Description

show ipv6 interface

Displays IPv6 interface settings.

show ipv6 route

Displays IPv6 routing table contents.

show pxf cpu ipv6

Displays PXF CPU IPv6 statistics.


DB-1862

May 2008

Debug Commands debug pxf l2less-error

debug pxf l2less-error To display debug messages relating to Parallel eXpress Forwarding (PXF) Layer 2 Less (L2less) drop packet errors, use the debug pxf l2less-error command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf l2less-error no debug pxf l2less-error

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(7)XI


12.2SX


Usage Guidelines

The Route Processor (RP) uses the L2less packet handler to handle tunneling encapsulated packets that do not have the original IP and Layer 2 information associated with them. The L2less handler takes the packet with a specific header, updates the statistics (interface packet and byte counts), and enqueues the packet to the IP input queue.

Examples

The following example shows how to display PXF L2less drop packet errors debug messages: Router# debug pxf l2less-error PXF l2less-error debugging is on

Related Commands

Command

Description

show pxf statistics

Displays chassis-wide, summary PXF statistics.


DB-1863

Debug Commands debug pxf microcode

debug pxf microcode To display debug message relating to Parallel eXpress Forwarding (PXF) microcode operations, use the debug pxf microcode command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf microcode no debug pxf microcode

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(7)XI


12.2SX


Examples

The following example shows how to display PXF microcode debug messages: Router# debug pxf microcode PXF microcode debugging is on

Related Commands

Command

Description

microcode reload

Reloads the Cisco IOS image from a line card on a Cisco router.

show pxf microcode

Displays identifying information for the microcode currently loaded on the PXF.


DB-1864

May 2008

Debug Commands debug pxf mnode

debug pxf mnode To display debug messages relating to Parallel eXpress Forwarding (PXF) multiway node (mnode) operations, use the debug pxf mnode command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf mnode no debug pxf mnode

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Usage Guidelines

The mnodes are used in the multiway tree (Mtrie) library. Each mnode has a number of buckets that point to lower level mnodes or to multiway leaves (mleaves). The mleaves can be null leaves which indicate empty buckets.

Examples

The following example shows how to display PXF mnode debug messages: Router# debug pxf mnode PXF MNODE debugging is on

Related Commands

Command

Description

show pxf cpu cef

Displays PXF CPU memory usage, Cisco Express Forwarding, and XCM information.


DB-1865

Debug Commands debug pxf mpls

debug pxf mpls To display debug messages relating to Parallel eXpress Forwarding (PXF) Multiprotocol Label Switching (MPLS) operations, use the debug pxf mpls command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf mpls [csc {event | stats} | lspv] no debug pxf mpls [csc {event | stats} | lspv]

Syntax Description

csc {event | stats}

(Optional) Displays PXF Cisco Signaling Controller (CSC) events and statistics.

lspv

Displays Link State Path Vector (LSPV) debug messages from the PXF MPLS Label Switched Path (LSP) Ping/Traceroute feature.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF MPLS CSC statistics debug messages: Router# debug pxf mpls csc stats PXF MPLS CSC STATS debugging is on

Related Commands

Command

Description

ping mpls

Checks MPLS LSP connectivity.

show mpls interfaces

Displays information about the interfaces that have been configured for label switching.

show pxf cpu mpls

Displays PXF MPLS (FIB) entry information.

trace mpls

Discovers MPLS LSP routes that packets will take when traveling to their destinations.


DB-1866

May 2008

Debug Commands debug pxf mroute

debug pxf mroute To display debug messages relating to Parallel eXpress Forwarding (PXF) multicast route (mroute) operations, use the debug pxf mroute command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf mroute [mdb | mdt | midb | punt] no debug pxf mroute [mdb | mdt | midb | punt]

Syntax Description

mdb

(Optional) Displays PXF multicast descriptor block (MDB) event messages.

mdt

(Optional) Displays PXF multicast distribution tree (MDT) messages.

midb

(Optional) Displays PXF multicast interface descriptor block (MIDB) messages.

punt

(Optional) Displays PXF multicast punted packets information.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF multicast distribution tree (MDT) debug messages: Router# debug pxf mroute mdt PXF mroute mdt creation debugging is on

Related Commands

Command

Description

clear ip mroute

Deletes entries from the IP multicast routing table.

show ip mroute

Displays the contents of the IP multicast routing table.

show pxf cpu mroute

Displays PXF multicast routing information for a particular group or range of groups.


DB-1867

Debug Commands debug pxf multilink

debug pxf multilink To display debug messages relating to Parallel eXpress Forwarding (PXF) multilink operations, use the debug pxf multilink command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf multilink [all | atm | frame-relay | frfl2 | lfi | ppp | queue | rates] no debug pxf multilink [all | atm | frame-relay | frfl2 | lfi | ppp | queue | rates]

Syntax Description

all

(Optional) Displays all PXF multilink messages.

atm

(Optional) Displays PXF multilink ATM messages.

frame-relay

(Optional) Displays PXF multilink Frame Relay messages.

frf12

(Optional) Displays PXF Frame Relay Forum FRF.12-based fragmentation information on Frame Relay permanent virtual circuits (PVCs).

lfi

(Optional) Displays PXF Link Fragmentation and Interleaving (LFI) messages.

ppp

(Optional) Displays PXF multilink PPP messages.

queue

(Optional) Displays PXF multilink queue messages.

rates

(Optional) Displays PXF multilink queue rate messages.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF multilink ATM debug messages: Router# debug pxf multilink atm Router#

Related Commands

Command

Description

frame-relay fragment

Enables fragmentation of Frame Relay frames on a Frame Relay map class.

show ppp multilink

Displays bundle information for the MLP bundles.

show pxf statistics



DB-1868

May 2008

Debug Commands debug pxf netflow

debug pxf netflow To enable debugging of NetFlow Parallel eXpress Forwarding (PXF )operations, use the debug pxf netflow command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf netflow {records | time} no debug pxf netflow {records | time}

Syntax Description

records

Displays NetFlow PXF records information.

time

Displays NetFlow PXF time synchronization information.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(7)XI


12.2SX


Examples

The following example enables NetFlow PXF records debugging: Router# debug pxf netflow records PXF netflow records debugging is on Router#

Related Commands

Command

Description

show pxf netflow

Displays NetFlow PXF counters information.


DB-1869

Debug Commands debug pxf pbr

debug pxf pbr To display debug messages relating to Parallel eXpress Forwarding (PXF) policy-based routing (PBR), use the debug pxf pbr command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf pbr [sacl | trace] no debug pxf pbr [sacl | trace]

Syntax Description

sacl

(Optional) Displays PXF PBR super access control list (ACL) messages.

trace

(Optional) Displays PXF PBR trace information.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF PBR trace debug messages: Router# debug pxf pbr trace PXF PBR Trace debugging is on

Related Commands

Command

Description

show pxf cpu pbr action

Displays the PBR actions configured on the PXF for all PBR route maps.


DB-1870

May 2008

Debug Commands debug pxf qos

debug pxf qos To display debug messages relating to Parallel eXpress Forwarding (PXF) quality of service (QoS) operations, use the debug pxf qos command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf qos [ipc | trace] no debug pxf qos [ipc | trace]

Syntax Description

ipc

(Optional) Displays PXF QoS interprocess communication (IPC) information.

trace

(Optional) Displays PXF QoS trace information

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2S


12.2SX


Examples

The following example shows how to display PXF QoS IPC debug messages: Router# debug pxf qos trace PXF QoS IPC Events debugging is on Router# *Apr 30 *Apr 30 *Apr 30 *Apr 30 *Apr 30 *Apr 30 . . .

Related Commandss

23:23:44: 23:23:44: 23:23:44: 23:23:44: 23:23:44: 23:23:44:

c10k_bandwidth_notification_handler: cmdtype=4 event=0x30 acA c10k_priority_notification_handler: cmdtype=4 event=0x30 actA c10k_bandwidth_notification_handler: cmdtype=4 event=0x30 acA c10k_bandwidth_notification_handler: cmdtype=4 event=0x30 acA c10k_priority_notification_handler: cmdtype=4 event=0x30 actA c10k_bandwidth_notification_handler: cmdtype=4 event=0x30 acA

Command

Description

show pxf cpu qos

Displays External Column Memory (XCM) contents related to a particular policy.

show pxf statistics

Displays chassis–wide, summary PXF statistics.


DB-1871

Debug Commands debug pxf stats

debug pxf stats To display debug messages relating to Parallel eXpress Forwarding (PXF) statistics collector events, use the debug pxf stats command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf stats no debug pxf stats

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(7)XI


12.2SX


Examples

The following example shows how to display PXF statistics debug messages: Router# debug pxf stats PXF hardware statistics debugging is on

Related Commands

Command

Description

clear pxf

Clears PXF counters and statistics.

show pxf cpu statistics Displays PXF CPU statistics. show pxf statistics



DB-1872

May 2008

Debug Commands debug pxf subblocks

debug pxf subblocks To display debug messages relating to Parallel eXpress Forwarding (PXF) bridged subinterfaces (encapsulation types), use the debug pxf subblocks command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug pxf subblocks no debug pxf subblocks

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(7)XI


12.2SX


Examples

The following example shows how to display PXF bridged subinterfaces (encapsulation type) debug messages: Router# debug pxf subblocks PXF hardware subblock debugging is on

Related Commands

Command

Description

show pxf cpu statistics Displays PXF CPU statistics. show pxf cpu subblocks

Displays PXF CPU statistics for bridged subinterfaces (encapsulation types).


DB-1873

Debug Commands debug pxf tbridge

debug pxf tbridge To enable debugging of Parallel eXpress Forwarding (PXF) transparent bridging, use the debug pxf tbridge command in privileged EXEC mode. To disable debugging for the PXF transparent bridge, use the no form of this command. debug pxf tbridge no debug pxf tbridge

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2(31)SB

This command was integrated into Cisco IOS Release 12.2(31)SB and implemented on the Cisco 10000 series router.

12.2SX


Examples

The following sample output from the debug pxf tbridge command shows that the Bridge Group Virtual Interface (BVI) 100 has been removed from the Software Mac-address Filter (SMF) table: Router# debug pxf tbridge *Feb 8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: Deleting BVI entry 100 from SMF table. *Feb 8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: BVI 100 ICM programming *Feb 8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: Successfully removed SMF entry for bvi 100 *Feb 8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: Deleting BVI entry 100 from SMF table. *Feb 8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: BVI 100 ICM programming *Feb 8 18:39:04.710: rpmxf_tbridge_add_remove_bvi_from_smf: Successfully removed SMF entry for bvi 100 *Feb 8 18:39:05.178: %SYS-5-CONFIG_I: Configured from console by vty0 (CROI_MASTER_000A004B) *Feb 8 18:39:06.710: %LINK-5-CHANGED: Interface BVI100, changed state to administratively down *Feb 8 18:39:07.710:%LINEPROTO-5-UPDOWN: Line protocol on Interface BVI100, changed state to down

The following sample output from the debug pxf tbridge command shows that BVI is configured and that the SMF entry has been updated:


DB-1874

May 2008

Debug Commands debug pxf tbridge

Router# debug pxf tbridge *Feb 8 18:39:16.398: Note: A random mac address of 0000.0ceb.c0f8 has been chosen for BVI in bridge group 100 since there is no mac address associated with the selected interface. *Feb 8 18:39:16.398: Ensure that this address is unique. *Feb 8 18:39:16.398: rpmxf_tbridge_smf_update: SMF update for Switch1.1: BVI 100 Mac Address 0000.0ceb.c0f8 *Feb 8 18:39:16.398: rpmxf_tbridge_smf_update: BVI 100 ICM programming *Feb 8 18:39:16.398: rpmxf_tbridge_smf_update: Successfully updated SMF entry for bvi 100 *Feb 8 18:39:16.398: rpmxf_tbridge_smf_update: SMF update for Switch1.1: BVI 100 Mac Address 0000.0ceb.c0f8 *Feb 8 18:39:16.398: rpmxf_tbridge_smf_update: BVI 100 ICM programming *Feb 8 18:39:16.398: rpmxf_tbridge_smf_update: Successfully updated SMF entry for bvi 100 *Feb 8 18:39:16.886: %SYS-5-CONFIG_I: Configured from console by vty0 (CROI_MASTER_000A004B) *Feb 8 18:39:18.394: %LINK-3-UPDOWN: Interface BVI100, changed state to up *Feb 8 18:39:19.394: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI100, changed state to up

Related Commands

Command

Description

show pxf cpu statistics

Displays PXF CPU statistics for a configured router.

show pxf cpu subblock

Displays PXF CPU subblocks for a bridged subinterface.

show pxf cpu tbridge

Displays PXF CPU statistics for transparent bridging.

show pxf statistics



DB-1875

Debug Commands debug qllc error

debug qllc error To display quality link line control (QLLC) errors, use the debug qllc error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug qllc error no debug qllc error

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command helps you track down errors in the QLLC interactions with X.25 networks. Use the debug qllc error command in conjunction with the debug x25 all command to see the connection. The data shown by this command only flows through the router on the X.25 connection. Some forms of this command can generate a substantial amount of output and network traffic.

Examples

The following is sample output from the debug qllc error command: Router# debug qllc error %QLLC-3-GENERRMSG: qllc_close - bad qllc pointer Caller 00407116 Caller 00400BD2 QLLC 4000.1111.0002: NO X.25 connection. Discarding XID and calling out

The following line indicates that the QLLC connection was closed: %QLLC-3-GENERRMSG: qllc_close - bad qllc pointer Caller 00407116 Caller 00400BD2

The following line shows the virtual MAC address of the failed connection: QLLC 4000.1111.0002: NO X.25 connection. Discarding XID and calling out


DB-1876

May 2008

Debug Commands debug qllc event

debug qllc event To enable debugging of quality link line control (QLLC) events, use the debug qllc event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug qllc event no debug qllc event

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use the debug qllc event command to display primitives that might affect the state of a QLLC connection. An example of these events is the allocation of a QLLC structure for a logical channel indicator when an X.25 call has been accepted with the QLLC call user data. Other examples are the receipt and transmission of LAN explorer and exchange identification (XID) frames.

Examples

The following is sample output from the debug qllc event command: Router# debug qllc event QLLC: allocating new qllc lci 9 QLLC: tx POLLING TEST, da 4001.3745.1088, sa 4000.1111.0001 QLLC: rx explorer response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040 QLLC: gen NULL XID, da c001.3745.1088, sa 4000.1111.0001, rif 0830.1A91.1901.A040, dsap 4, ssap 4 QLLC: rx XID response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040

The following line indicates that a new QLLC data structure has been allocated: QLLC: allocating new qllc lci 9

The following lines show transmission and receipt of LAN explorer or test frames: QLLC: tx POLLING TEST, da 4001.3745.1088, sa 4000.1111.0001 QLLC: rx explorer response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040

The following lines show XID events: QLLC: gen NULL XID, da c001.3745.1088, sa 4000.1111.0001, rif 0830.1A91.1901.A040, dsap 4, ssap 4 QLLC: rx XID response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040


DB-1877

Debug Commands debug qllc packet

debug qllc packet To display quality link line control (QLLC) events and QLLC data packets, use the debug qllc packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug qllc packet no debug qllc packet

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command helps you to track down errors in the QLLC interactions with X.25 networks. The data shown by this command only flows through the router on the X25 connection. Use the debug qllc packet command in conjunction with the debug x25 all command to see the connection and the data that flows through the router.

Examples

The following is sample output from the debug qllc packet command: Router# debug qllc packet 14:38:05: 14:38:07: 14:38:07: 14:38:08: 14:38:08: 14:38:08: 14:38:08: 14:38:12: 14:38:12:

Serial2/5 Serial2/6 Serial2/6 Serial2/6 Serial2/6 Serial2/6 Serial2/6 Serial2/5 Serial2/5

QLLC QLLC QLLC QLLC QLLC QLLC QLLC QLLC QLLC

I: I: O: I: I: O: I: I: O:

Data Data Data Data Data Data Data Data Data

Packet.-RSP Packet.-RSP Packet. 128 Packet.-RSP Packet.-RSP Packet. 128 Packet.-RSP Packet.-RSP Packet. 128

9 bytes. 112 bytes. bytes. 9 bytes. 112 bytes. bytes. 9 bytes. 112 bytes. bytes.

The following lines indicate that a packet was received on the interfaces: 14:38:05: Serial2/5 QLLC I: Data Packet.-RSP 9 bytes. 14:38:07: Serial2/6 QLLC I: Data Packet.-RSP 112 bytes.

The following lines show that a packet was sent on the interfaces: 14:38:07: Serial2/6 QLLC O: Data Packet. 128 bytes. 14:38:12: Serial2/5 QLLC O: Data Packet. 128 bytes.


DB-1878

May 2008

Debug Commands debug qllc state

debug qllc state To enable debugging of quality link line control (QLLC) events, use the debug qllc state command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug qllc state no debug qllc state

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use the debug qllc state command to show when the state of a QLLC connection has changed. The typical QLLC connection goes from states ADM to SETUP to NORMAL. The NORMAL state indicates that a QLLC connection exists and is ready for data transfer.

Examples

The following is sample output from the debug qllc state command: Router# debug qllc state Serial2 QLLC O: QSM-CMD Serial2: X25 O D1 DATA (5) Q 8 lci 9 PS 4 PR 3 QLLC: state ADM -> SETUP Serial2: X25 I D1 RR (3) 8 lci 9 PR 5 Serial2: X25 I D1 DATA (5) Q 8 lci 9 PS 3 PR 5 Serial2 QLLC I: QUA-RSPQLLC: addr 00, ctl 73 QLLC: qsetupstate: recvd qua rsp QLLC: state SETUP -> NORMAL

The following line indicates that a QLLC connection attempt is changing state from ADM to SETUP: QLLC: state ADM -> SETUP

The following line indicates that a QLLC connection attempt is changing state from SETUP to NORMAL: QLLC: state SETUP -> NORMAL


DB-1879

Debug Commands debug qllc timer

debug qllc timer To display quality link line control (QLLC) timer events, use the debug qllc timer command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug qllc timer no debug qllc timer

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The QLLC process periodically cycles and checks status of itself and its partner. If the partner is not found in the desired state, an LAPB primitive command is re-sent until the partner is in the desired state or the timer expires.

Examples

The following is sample output from the debug qllc timer command: Router# debug qllc timer 14:27:24: 14:27:34: 14:27:44: 14:27:54:

Qllc Qllc Qllc Qllc

timer timer timer timer

lci lci lci lci

257, 257, 257, 257,

state state state state

ADM retry count 0 Caller 00407116 Caller 00400BD2 NORMAL retry count 0 NORMAL retry count 1 NORMAL retry count 1

The following line of output shows the state of a QLLC partner on a given X.25 logical channel identifier: 14:27:24: Qllc timer lci 257, state ADM retry count 0 Caller 00407116 Caller 00400BD2

Other messages are informational and appear every ten seconds.


DB-1880

May 2008

Debug Commands debug qllc x25

debug qllc x25 To display X.25 packets that affect a quality link line control (QLLC) connection, use the debug qllc x25 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug qllc x25 no debug qllc x25

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command is helpful to track down errors in the QLLC interactions with X.25 networks. Use the debug qllc x25 command in conjunction with the debug x25 events or debug x25 all commands to see the X.25 events between the router and its partner.

Examples

The following is sample output from the debug qllc x25 command: Router# debug qllc x25 15:07:23: 15:07:23: 15:07:34: 15:07:35:

QLLC QLLC QLLC QLLC

X25 X25 X25 X25

notify notify notify notify

lci lci lci lci

257 257 257 257

event event event event

1 5 3 Caller 00407116 Caller 00400BD2 4


debug qllc x25 Field Descriptions

Field

Description

15:07:23

Displays the time of day.

QLLC X25 notify 257

Indicates that this is a QLLC X25 message.

event

Indicates the type of event, n. Values for n can be as follows: •

1—Circuit is cleared

•

2—Circuit has been reset

•

3—Circuit is connected

•

4—Circuit congestion has cleared

•

5—Circuit has been deleted


DB-1881

Debug Commands debug qos ha

debug qos ha To debug quality of service (QoS) information on the networking device, use the debug qos ha command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command. debug qos ha [detail] no debug qos ha [detail]

Syntax Description

detail

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(25)S


12.2(28)SB


(Optional) Displays detailed debug messages related to specified QoS information.

12.2(33)SRA


12.2SX


Usage Guidelines

Use to determine that QoS in running properly on your networking device.

Examples

The following example enables QoS debugging: Router# debug qos ha


DB-1882

May 2008

Debug Commands debug radius accounting

debug radius accounting To enable debugging of RADIUS accounting collection, use the debug radius accounting command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug radius accounting no debug radius accounting

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Examples

The following example enables debugging of RADIUS accounting collection: Router# debug radius accounting Radius Radius Radius Radius Radius Radius Radius Radius Radius

Related Commands

protocol debugging is on protocol brief debugging is off protocol verbose debugging is off packet hex dump debugging is off packet protocol (authentication) debugging is off packet protocol (accounting) debugging is on packet retransmission debugging is off server fail-over debugging is off elog debugging is off

Command

Description

debug event-manager

Enables debugging of the event manager.

debug voice statistics

Enables debugging of voice statistics.


DB-1883

Debug Commands debug radius local-server

debug radius local-server To control the display of debug messages for the local authentication server, use the debug radius local-server command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug radius local-server {client | error | packets} no debug radius local-server {client | error | packets}

Syntax Description

client

Displays error messages about failed client authentications.

error

Displays error messages about the local authentication server.

packets

Displays the content of the RADIUS packets that are sent and received.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)JA

This command was introduced on Cisco Aironet Access Point 1200 and Cisco Aironet Access Point 1100.

12.3(11)T

This command was implemented on the following platforms: Cisco 2600XM, Cisco 2691, Cisco 2811, Cisco 2821, Cisco 2851, Cisco 3700, and Cisco 3800 series routers.

12.4(6)T


12.2SX


Usage Guidelines

Use this command to control the display of debug messages for the local authentication server.

Examples

The following command shows how to display messages regarding failed client authentication: Router# debug radius local-server client

Related Commands

Command

Description

clear radius local-server

Clears the statistics display or unblocks a user.

show radius local-server statistics Displays statistics for a local network access server. ssid

Specifies up to 20 SSIDs to be used by a user group.


DB-1884

May 2008

Debug Commands debug radius local-server

Command

Description

user

Authorizes a user to authenticate using the local authentication server.

vlan

Specifies a VLAN to be used by members of a user group.


DB-1885

Debug Commands debug radius

debug radius To display information associated with RADIUS, use the debug radius command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug radius [brief | hex] no debug radius [brief | hex]

Syntax Description

brief

(Optional) Displays abbreviated debug output.

hex

(Optional) Displays debugging output in hexadecimal notation.

Defaults

Debugging output in ASCII format is enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.2(1)T


12.2(11)T

The brief and hex keywords were added. The default output format became ASCII rather than hexadecimal.

12.2(33)SRA


12.2SX


Usage Guidelines

RADIUS is a distributed security system that secures networks against unauthorized access. Cisco supports RADIUS under the authentication, authorization, and accounting (AAA) security system. When RADIUS is used on the router, you can use the debug radius command to display detailed debugging and troubleshooting information in ASCII format. Use the debug radius brief command for abbreviated output displaying client/server interaction and minimum packet information. Use the debug radius hex command to display packet dump information that has not been truncated in hex format.

Examples

The following is sample output from the debug radius command: Router# debug radius Radius protocol debugging is on Radius packet hex dump debugging is off Router# 00:02:50: RADIUS: ustruct sharecount=3 00:02:50: Radius: radius_port_info() success=0 radius_nas_port=1 00:02:50: RADIUS: Initial Transmit ISDN 0:D:23 id 0 10.0.0.1:1824, Accounting-Request, len 358 00:02:50: RADIUS: NAS-IP-Address [4] 6 10.0.0.0


DB-1886

May 2008


00:02:50: RADIUS: Vendor, Cisco [26] 19 VT=02 TL=13 ISDN 0:D:23 00:02:50: RADIUS: NAS-Port-Type [61] 6 Async 00:02:50: RADIUS: User-Name [1] 12 "4085554206" 00:02:50: RADIUS: Called-Station-Id [30] 7 "52981" 00:02:50: RADIUS: Calling-Station-Id [31] 12 "4085554206" 00:02:50: RADIUS: Acct-Status-Type [40] 6 Start 00:02:50: RADIUS: Service-Type [6] 6 Login 00:02:50: RADIUS: Vendor, Cisco [26] 27 VT=33 TL=21 h323-gw-id=5300_43. 00:02:50: RADIUS: Vendor, Cisco [26] 55 VT=01 TL=49 h323-incoming-conf-id=8F3A3163 B4980003 0 29BD0 00:02:50: RADIUS: Vendor, Cisco [26] 31 VT=26 TL=25 h323-call-origin=answer 00:02:50: RADIUS: Vendor, Cisco [26] 32 VT=27 TL=26 h323-call-type=Telephony 00:02:50: RADIUS: Vendor, Cisco [26] 57 VT=25 TL=51 h323-setup-time=*16:02:48.681 PST Fri Dec 31 1999 00:02:50: RADIUS: Vendor, Cisco [26] 46 VT=24 TL=40 h323-conf-id=8F3A3163 B4980003 0 29BD0 00:02:50: RADIUS: Acct-Session-Id [44] 10 "00000002" 00:02:50: RADIUS: Delay-Time [41] 6 0 00:02:51: RADIUS: Received from id 0 1.7.157.1:1824, Accounting-response, len 20 00:02:51: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4085274206 00:03:01: RADIUS: ustruct sharecount=3 00:03:01: Radius: radius_port_info() success=0 radius_nas_port=1 00:03:01: RADIUS: Initial Transmit ISDN 0:D:23 id 1 1.7.157.1:1823, Access-Request, len 171 00:03:01: RADIUS: NAS-IP-Address [4] 6 10.0.0.0 00:03:01: RADIUS: Vendor, Cisco [26] 19 VT=02 TL=13 ISDN 0:D:23 00:03:01: RADIUS: NAS-Port-Type [61] 6 Async 00:03:01: RADIUS: User-Name [1] 8 "123456" 00:03:01: RADIUS: Vendor, Cisco [26] 46 VT=24 TL=40 h323-conf-id=8F3A3163 B4980003 0 29BD0 00:03:01: RADIUS: Calling-Station-Id [31] 12 "4085554206" 00:03:01: RADIUS: User-Password [2] 18 * 00:03:01: RADIUS: Vendor, Cisco [26] 36 VT=01 TL=30 h323-ivr-out=transactionID:0 00:03:01: RADIUS: Received from id 1 1.7.157.1:1823, Access-Accept, len 115 00:03:01: RADIUS: Service-Type [6] 6 Login 00:03:01: RADIUS: Vendor, Cisco [26] 29 VT=101 TL=23 h323-credit-amount=45 00:03:01: RADIUS: Vendor, Cisco [26] 27 VT=102 TL=21 h323-credit-time=33 00:03:01: RADIUS: Vendor, Cisco [26] 26 VT=103 TL=20 h323-return-code=0 00:03:01: RADIUS: Class [25] 7 6C6F63616C 00:03:01: RADIUS: saved authorization data for user 62321E14 at 6233D258 00:03:13: %ISDN-6-DISCONNECT: Interface Serial0:22 disconnected from 4085274206, call lasted 22 seconds 00:03:13: RADIUS: ustruct sharecount=2 00:03:13: Radius: radius_port_info() success=0 radius_nas_port=1 00:03:13: RADIUS: Sent class "local" at 6233D2C4 from user 62321E14 00:03:13: RADIUS: Initial Transmit ISDN 0:D:23 id 2 1.7.157.1:1824, Accounting-Request, len 775 00:03:13: RADIUS: NAS-IP-Address [4] 6 10.0.0.0 00:03:13: RADIUS: Vendor, Cisco [26] 19 VT=02 TL=13 ISDN 0:D:23 00:03:13: RADIUS: NAS-Port-Type [61] 6 Async 00:03:13: RADIUS: User-Name [1] 8 "123456" 00:03:13: RADIUS: Called-Station-Id [30] 7 "52981" 00:03:13: RADIUS: Calling-Station-Id [31] 12 "4085274206" 00:03:13: RADIUS: Acct-Status-Type [40] 6 Stop 00:03:13: RADIUS: Class [25] 7 6C6F63616C 00:03:13: RADIUS: Undebuggable [45] 6 00000001 00:03:13: RADIUS: Service-Type [6] 6 Login 00:03:13: RADIUS: Vendor, Cisco [26] 27 VT=33 TL=21 h323-gw-id=5300_43. 00:03:13: RADIUS: Vendor, Cisco [26] 55 VT=01 TL=49 h323-incoming-conf-id=8F3A3163 B4980003 0 29BD0 00:03:13: RADIUS: Vendor, Cisco [26] 31 VT=26 TL=25 h323-call-origin=answer 00:03:13: RADIUS: Vendor, Cisco [26] 32 VT=27 TL=26 h323-call-type=Telephony 00:03:13: RADIUS: Vendor, Cisco [26] 57 VT=25 TL=51 h323-setup-time=*16:02:48.681 PST Fri Dec 31 1999


DB-1887


00:03:13: RADIUS: Vendor, Cisco [26] 59 VT=28 TL=53 h323-connect-time=*16:02:48.946 PST Fri Dec 31 1999 00:03:13: RADIUS: Vendor, Cisco [26] 62 VT=29 TL=56in=0 00:03:13: RADIUS: Vendor, Cisco [26] 23 VT=01 TL=17 pre-bytes-out=0 00:03:13: RADIUS: Vendor, Cisco [26] 21 VT=01 TL=15 pre-paks-in=0 00:03:13: RADIUS: Vendor, Cisco [26] 22 VT=01 TL=16 pre-paks-out=0 00:03:13: RADIUS: Vendor, Cisco [26] 22 VT=01 TL=16 nas-rx-speed=0 00:03:13: RADIUS: Vendor, Cisco [26] 22 VT=01 TL=16 nas-tx-speed=0 00:03:13: RADIUS: Delay-Time [41] 6 0 00:03:13: RADIUS: Received from id 2 1.7.157.1:1824, Accounting-response, len 20 h323-disconnect-time=*16:03:11.306 PST Fri Dec 31 1999 00:03:13: RADIUS: Vendor, Cisco [26] 32 VT=30 TL=26 h323-disconnect-cause=10 00:03:13: RADIUS: Vendor, Cisco [26] 28 VT=31 TL=22 h323-voice-quality=0 00:03:13: RADIUS: Vendor, Cisco [26] 46 VT=24 TL=40 h323-conf-id=8F3A3163 B4980003 0 29BD0 00:03:13: RADIUS: Acct-Session-Id [44] 10 "00000002" 00:03:13: RADIUS: Acct-Input-Octets [42] 6 0 00:03:13: RADIUS: Acct-Output-Octets [43] 6 88000 00:03:13: RADIUS: Acct-Input-Packets [47] 6 0 00:03:13: RADIUS: Acct-Output-Packets [48] 6 550 00:03:13: RADIUS: Acct-Session-Time [46] 6 22 00:03:13: RADIUS: Vendor, Cisco [26] 30 VT=01 TL=24 subscriber=RegularLine 00:03:13: RADIUS: Vendor, Cisco [26] 35 VT=01 TL=29 h323-ivr-out=Tariff:Unknown 00:03:13: RADIUS: Vendor, Cisco [26] 22 VT=01 TL=16 pre-bytes-

The following is sample output from the debug radius brief command: Router# debug radius brief Radius protocol debugging is on Radius packet hex dump debugging is off Radius protocol in brief format debugging is on 00:05:21: RADIUS: Initial Transmit ISDN 0:D:23 id 6 10.0.0.1:1824, Accounting-Request, len 358 00:05:21: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4085274206 00:05:26: RADIUS: Retransmit id 6 00:05:31: RADIUS: Tried all servers. 00:05:31: RADIUS: No valid server found. Trying any viable server 00:05:31: RADIUS: Tried all servers. 00:05:31: RADIUS: No response for id 7 00:05:31: RADIUS: Initial Transmit ISDN 0:D:23 id 8 10.0.0.0:1823, Access-Request, len 171 00:05:36: RADIUS: Retransmit id 8 00:05:36: RADIUS: Received from id 8 1.7.157.1:1823, Access-Accept, len 115 00:05:47: %ISDN-6-DISCONNECT: Interface Serial0:22 disconnected from 4085274206, call lasted 26 seconds 00:05:47: RADIUS: Initial Transmit ISDN 0:D:23 id 9 10.0.0.1:1824, Accounting-Request, len 775 00:05:47: RADIUS: Received from id 9 1.7.157.1:1824, Accounting-response, len 20

The following example shows debug radius hex output: Router# debug radius hex Radius protocol debugging is on Radius packet hex dump debugging is on Router# 17:26:52: RADIUS: ustruct sharecount=3 17:26:52: Radius: radius_port_info() success=0 radius_nas_port=1 17:26:52: RADIUS: Initial Transmit ISDN 0:D:23 id 10 10.0.0.1:1824, Accounting-Request, len 361 17:26:52: Attribute 4 6 01081D03 17:26:52: Attribute 26 19 00000009020D4953444E20303A443A3233 17:26:52: Attribute 61 6 00000000 17:26:52: Attribute 1 12 34303835323734323036


DB-1888

May 2008


17:26:52: Attribute 30 7 3532393831 17:26:52: Attribute 31 12 34303835323734323036 17:26:52: Attribute 40 6 00000001 17:26:52: Attribute 6 6 00000001 17:26:52: Attribute 26 27 000000092115683332332D67772D69643D353330305F34332E 17:26:52: Attribute 26 57 000000090133683332332D696E636F6D696E672D636F6E662D69643D3846334133313633204234393830303046 20302033424537314238 17:26:52: Attribute 26 31 000000091A19683332332D63616C6C2D6F726967696E3D616E73776572 17:26:52: Attribute 26 32 000000091B1A683332332D63616C6C2D747970653D54656C6570686F6E79 17:26:52: Attribute 26 56 000000091932683332332D73657475702D74696D653D2A30393A32363A35322E3838302050535420536174204A 616E20312032303030 17:26:52: Attribute 26 48 00000009182A683332332D636F6E662D69643D3846334133313633204234393830303046203020334245373142 38 17:26:52: Attribute 44 10 3030303030303035 17:26:52: Attribute 41 6 00000000 17:26:52: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4085274206 17:26:52: RADIUS: Received from id 10 10.0.0.1:1824, Accounting-response, len 20 17:27:01: RADIUS: ustruct sharecount=3 17:27:01: Radius: radius_port_info() success=0 radius_nas_port=1 17:27:01: RADIUS: Initial Transmit ISDN 0:D:23 id 11 10.0.0.0:1823, Access-Request, len 173 17:27:01: Attribute 4 6 01081D03 17:27:01: Attribute 26 19 00000009020D4953444E20303A443A3233 17:27:01: Attribute 61 6 00000000 17:27:01: Attribute 1 8 313233343536 17:27:01: Attribute 26 48 00000009182A683332332D636F6E662D69643D3846334133313633204234393830303046203020334245373142 38 17:27:01: Attribute 31 12 34303835323734323036 17:27:01: Attribute 2 18 C980D8D0E9A061B3D783C61AA6F27214 17:27:01: Attribute 26 36 00000009011E683332332D6976722D6F75743D7472616E73616374696F6E49443A33 17:27:01: RADIUS: Received from id 11 1.7.157.1:1823, Access-Accept, len 115 17:27:01: Attribute 6 6 00000001 17:27:01: Attribute 26 29 000000096517683332332D6372656469742D616D6F756E743D3435 17:27:01: Attribute 26 27 000000096615683332332D6372656469742D74696D653D3333 17:27:01: Attribute 26 26 000000096714683332332D72657475726E2D636F64653D30 17:27:01: Attribute 25 7 6C6F63616C 17:27:01: RADIUS: saved authorization data for user 61AA0698 at 6215087C 17:27:09: %ISDN-6-DISCONNECT: Interface Serial0:22 disconnected from 4085554206, call lasted 17 seconds 17:27:09: RADIUS: ustruct sharecount=2 17:27:09: Radius: radius_port_info() success=0 radius_nas_port=1 17:27:09: RADIUS: Sent class "local" at 621508E8 from user 61AA0698 17:27:09: RADIUS: Initial Transmit ISDN 0:D:23 id 12 1.7.157.1:1824, Accounting-Request, len 776 17:27:09: Attribute 4 6 01081D03 17:27:09: Attribute 26 19 00000009020D4953444E20303A443A3233 17:27:09: Attribute 61 6 00000000 17:27:09: Attribute 1 8 313233343536 17:27:09: Attribute 30 7 3532393831 17:27:09: Attribute 31 12 34303835323734323036 17:27:09: Attribute 40 6 00000002 17:27:09: Attribute 25 7 6C6F63616C 17:27:09: Attribute 45 6 00000001 17:27:09: Attribute 6 6 00000001 17:27:09: Attribute 26 27 000000092115683332332D67772D69643D353330305F34332E


DB-1889


17:27:09: Attribute 26 57 000000090133683332332D696E636F6D696E672D636F6E662D69643D3846334133313633204234393830303046 20302033424537314238 17:27:09: Attribute 26 31 000000091A19683332332D63616C6C2D6F726967696E3D616E73776572 17:27:09: Attribute 26 32 000000091B1A683332332D63616C6C2D747970653D54656C6570686F6E79 17:27:09: Attribute 26 56 000000091932683332332D73657475702D74696D653D2A30393A32363A35322E3838302050535420536174204A 616E20312032303030 17:27:09: Attribute 26 58 000000091C34683332332D636F6E6E6563742D74696D653D2A30393A32363A35322E3930372050535420536174 204A616E20312032303030 17:27:09: Attribute 26 61 000000091D37683332332D646973636F6E6E6563742D74696D653D2A30393A32373A31302E3133372050535420 536174204A616E20312032303030 17:27:09: Attribute 26 32 000000091E1A683332332D646973636F6E6E6563742D63617573653D3130 17:27:09: Attribute 26 28 000000091F16683332332D766F6963652D7175616C6974793D30 17:27:09: Attribute 26 48 00000009182A683332332D636F6E662D69643D3846334133313633204234393830303046203020334245373142 38 17:27:09: Attribute 44 10 3030303030303035 17:27:09: Attribute 42 6 00000000 17:27:09: Attribute 43 6 00012CA0 17:27:09: Attribute 47 6 00000000 17:27:09: Attribute 48 6 000001E1 17:27:09: Attribute 46 6 00000011 17:27:09: Attribute 26 30 000000090118737562736372696265723D526567756C61724C696E65 17:27:09: Attribute 26 35 00000009011D683332332D6976722D6F75743D5461726966663A556E6B6E6F776E 17:27:09: Attribute 26 22 0000000901107072652D62797465732D696E3D30 17:27:09: Attribute 26 23 0000000901117072652D62797465732D6F75743D30 17:27:09: Attribute 26 21 00000009010F7072652D70616B732D696E3D30 17:27:09: Attribute 26 22 0000000901107072652D70616B732D6F75743D30 17:27:09: Attribute 26 22 0000000901106E61732D72782D73706565643D30 17:27:09: Attribute 26 22 0000000901106E61732D74782D73706565643D30 17:27:09: Attribute 41 6 00000000 17:27:09: RADIUS: Received from id 12 10.0.0.1:1824, Accounting-response, len 20

Related Commands

Command

Description

debug aaa accounting



Displays information on AAA/TACACS+ authentication.


DB-1890

May 2008

Debug Commands debug radius-proxy

debug radius-proxy To display debugging messages for Intelligent Service Gateway (ISG) RADIUS proxy functionality, use the debug radius-proxy command in privileged EXEC mode. To disable debugging, use the no form of this command. debug radius-proxy {events | errors} no debug radius-proxy {events | errors}

Syntax Description

events

Displays debug messages related to ISG RADIUS proxy events.

errors

Displays debug messages related to ISG RADIUS proxy errors.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(31)SB2


12.2SX


Usage Guidelines

Caution

Examples

See the following caution before using debug commands.

Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, only use debug commands to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network flows and fewer users.

The following example shows output for the debug radius-proxy command with the events keyword: Router# debug radius-proxy events *Nov 7 *Nov 7 *Nov 7 *Nov 7 Name:aa *Nov 7 *Nov 7 *Nov 7 *Nov 7 *Nov 7

07:53:11.411: 07:53:11.411: 07:53:11.411: 07:53:11.411:

RP-EVENT: RP-EVENT: RP-EVENT: RP-EVENT:

Parse Parse Parse Found

Request: Request: Request: matching

Username = 12345679@cisco Caller ID = 12345679@cisco NAS id = localhost context for user Caller ID:12345679@cisco

07:53:11.411: 07:53:11.411: 07:53:11.411: 07:53:11.411: 07:53:11.411:

RP-EVENT: RP-EVENT: RP-EVENT: RP-EVENT: RP-EVENT:

Received event client Access-Request in state activated User Caller ID:12345679@cisco Name:12 re-authenticating Forwarding Request to method list (handle=1979711512) Sending request to server group EAP State changed activated --> wait for Access-Response


DB-1891

Debug Commands debug ras

debug ras To display the types and addressing of Registration, Admission and Status (RAS) messages sent and received, use the debug ras command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ras no debug ras

Syntax Description

This command has arguments or keywords.

Defaults

This command is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2


12.2(2)XB1

This command was implemented on the Cisco AS5850 universal access router.

12.2(11)T


12.2SX


Usage Guidelines

Use the debug ras command to display the types and addressing of RAS messages sent and received. The debug output lists the message type using mnemonics defined in International Telecommunications Union-Telecommunication (ITU-T) specification H.225.

Examples

In the following output, gateway GW13.cisco.com sends a RAS registration request (RRQ) message to gatekeeper GK15.cisco.com at IP address 10.9.53.15. GW13.cisco.com then receives a registration confirmation (RCF) message from the gatekeeper. If there is no response, it could mean that the gatekeeper is offline or improperly addressed. If you receive a reject (RRJ) message, it could mean that the gatekeeper is unable to handle another gateway or that the registration information is incorrect. Router# debug ras *Mar 13 19:53:34.231: *Mar 13 19:53:34.231: *Mar 13 19:53:34.247: *Mar 13 19:53:34.251:

RASlib::ras_sendto:msg length 105 from 10.9.53.13:8658 to 10.9.53.15:1719 RASLib::RASSendRRQ:RRQ (seq# 36939) sent to 10.9.53.15 RASLib::RASRecvData:successfully rcvd message of length 105 from 10.9.53.15:1719 RASLib::RASRecvData:RCF (seq# 36939) rcvd from [10.9.53.15:1719] on sock [0x6168356C]


DB-1892

May 2008

Debug Commands debug redundancy (RP)

debug redundancy (RP) To enable the display of events for troubleshooting dual Route Processors (RPs), use the debug redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command. debug redundancy {ehsa | errors | fsm | kpa | msg | progression | status | timer} no debug redundancy {ehsa | errors | fsm | kpa | msg | progression | status | timer}

Syntax Description

ehsa

Displays redundancy facility (RF) enhanced high system availability (EHSA) information.

errors

Displays RF errors.

fsm

Displays RF feasible successor metrics (FSM) events.

kpa

Displays RF keepalive events.

msg

Displays RF messaging events.

progression

Displays RF progression events.

status

Displays RF status events.

timer

Displays RF timer events.

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)AA


Examples

12.0(15)ST

This command was introduced on Cisco 10000 series Internet routers.

12.0(22)S

This command was introduced on Cisco 7500, 10000, and 12000 series Internet routers.

12.2(18)S

This command was integrated into Cisco IOS Release 12.2(18)S on Cisco 7500 series routers.

12.2(20)S

Support was added for the Cisco 7304 router. The Cisco 7500 series router is not supported in Cisco IOS Release 12.2(20)S.

12.2(28)SB

Support for this command was integrated into Cisco IOS Release 12.2(28)SB.

12.2(33)SRA


12.2SX


The following example enables debugging information for RF keepalive events: Router# debug redundancy kpa


DB-1893

Debug Commands debug redundancy as5850

debug redundancy as5850 To enable specific redundancy-related debug options, use the debug redundancy as5850 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug redundancy as5850 {fsm | lines | master | mode | rf-client} no debug redundancy as5850

Syntax Description

fsm

Finite-state-machine events.

lines

Hardware lines.

master

Master (active rather than standby) route-switch-controller (RSC).

mode

RSC’s mode: classic-split or handover-split.

rf-client

Redundancy-related client-application information.

Defaults

This command is disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB1


12.2(11)T


12.2SX


Usage Guidelines

Use the master form of the command to view redundancy-related debug entries. All debug entries continue to be logged even if you do not specify an option here, and you can always use the show redundancy debug-log command to view them.

Examples

The output from this command consists of event announcements that can be used by authorized troubleshooting personnel.

Related Commands

Command

Description

show redundancy debug-log

Displays up to 256 debug entries.


DB-1894

May 2008

Debug Commands debug registry

debug registry To turn on the debugging output for registry events or errors when Cisco IOS Software Modularity software is running, use the debug registry command in privileged EXEC mode. To turn off debugging output, use the no form of this command or the undebug command. debug registry {events | errors} [process-name | pid] no debug registry {events | errors} [process-name | pid]

Syntax Description

events

Displays debugging messages about registry event messages.

errors

Displays debugging messages about registry error messages.

process-name

(Optional) Process name.

pid

(Optional) Process ID. Number in the range from 1 to 4294967295.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(18)SXF4

This command was introduced to support Software Modularity images.

12.2SX


Usage Guidelines

Caution

Examples

Use the debug registry command to troubleshoot Software Modularity registry operations.

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

The following example turns on debugging messages for Software Modularity registry events for the TCP process: Router# debug registry events tcp.proc Debug registry events debugging is on

The following example turns on debugging messages for Software Modularity registry errors: Router# debug registry errors Debug registry errors debugging is on


DB-1895

Debug Commands debug resource policy notification

debug resource policy notification To trace the Embedded Resource Manager (ERM) notification activities for resources using the ERM feature, use the debug resource policy notification command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug resource policy notification [owner resource-owner-name] no debug resource policy notification [owner resource-owner-name]

Syntax Description

owner resource-owner-name

Command Default

Disabled

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(14)T


12.2(33)SRB


12.2SX


12.2(33)SB


Examples

(Optional) Specifies the name of the resource owner (RO).

The following example shows different instances of the debug resource policy notification command: Router# debug resource policy notification Enabled notif. debugs on all owners

When a threshold is violated, the following messages are displayed: *Mar 3 09:50:44.081: Owner: 'memory' initiated a notification: *Mar 3 09:50:44.081: %SYS-4-RESMEMEXCEED: Resource user usrr1 has exceeded the Major memory threshold Pool: Processor Used: 42932864 Threshold :42932860 *Mar 3 09:50:46.081: Notification from Owner: 'memory' is dispatched for User: 'usrr1' (ID: 0x10000B9) *Mar 3 09:50:46.081: %SYS-4-RESMEMEXCEED: Resource user usrr1 has exceeded the Major memory threshold Pool: Processor Used: 42932864 Threshold :42932860 Router# no debug resource manager notification Disabled notif. debugs on all owners Router# debug resource manager notification owner cpu


DB-1896

May 2008

Debug Commands debug resource policy notification

Enabled notif. debugs on owner 'cpu' Router# no debug resource manager notification owner cpu Disabled notif. debugs on owner 'cpu' Router# debug resource manager notification owner memory Enabled notif. debugs on owner 'memory' Router# no debug resource manager notification owner memory Disabled notif. debugs on owner 'memory' Router# debug resource manager notification owner Buffer Enabled notif. debugs on owner 'Buffer' Router# no debug resource manager notification owner Buffer Disabled notif. debugs on owner 'Buffer' Router# no debug resource manager notification owner Buffer Disabled notif. debugs on owner 'Buffer'

Related Commands

Command

Description

debug resource policy registration

Displays the resource policy registration debug information for the ERM resources.


DB-1897

Debug Commands debug resource policy registration

debug resource policy registration To trace the Embedded Resource Manager (ERM) registration activities for resources using the ERM feature, use the debug resource policy registration command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug resource policy registration no debug resource policy registration

Syntax Description


Command Default

Disabled

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.3(14)T


12.2(33)SRB


12.2SX


12.2(33)SB


Examples

The following example shows output from the debug resource policy registration command: Router# debug resource policy registration Registrations debugging is on

When a Resource User (RU) is created, the following message is displayed: *Mar 3 09:35:58.304: resource_user_register: RU: ruID: 0x10000B8, rutID: 0x1, rg_ID: 0x0 name: usrr1

When an RU is deleted, the following message is displayed: *Mar 3 09:41:09.500: resource_user_unregister: RU: ruID: 0x10000B8, rutID: 0x1, rg_ID: 0x0 name: usrr1

Related Commands

Command

Description

debug resource policy notification

Displays the resource policy notification debug information for the ERM resources.


DB-1898

May 2008

Debug Commands debug resource-pool

debug resource-pool To see and trace resource pool management activity, use the debug resource-pool command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug resource-pool no debug resource-pool

Syntax Description


Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XI


12.2(33)SRA


12.2SX


Usage Guidelines

Enter the debug resource-pool command to see and trace resource pool management activity. Table 292 describes the resource pooling states. Table 292

Resource Pooling States

State

Description

RM_IDLE

No call activity.

RM_RES_AUTHOR

Call waiting for authorization, message sent to authentication, authorization, and accounting (AAA).

RM_RES_ALLOCATING

Call authorized, resource-grp-mgr allocating.

RM_RES_ALLOCATED

Resource allocated, connection acknowledgment sent to signalling state. Call should get connected and become active.

RM_AUTH_REQ_IDLE

Signalling module disconnected call while in RM_RES_AUTHOR. Waiting for authorization response from AAA.

RM_RES_REQ_IDLE

Signalling module disconnected call while in RM_RES_ALLOCATING. Waiting for resource allocation response from resource-group manager.


DB-1899


Table 292

Resource Pooling States (continued)

State

Description

RM_DNIS_AUTHOR

An intermediate state before proceeding with Route Processor Module (RPM) authorization.

RM_DNIS_AUTH_SUCCEEDED Dialed number identification service (DNIS) authorization succeeded. RM_DNIS_RES_ALLOCATED

DNIS resource allocated.

RM_DNIS_AUTH_REQ_IDLE

DNIS authorization request idle.

RM_DNIS_AUTHOR_FAIL

DNIS authorization failed.

RM_DNIS_RES_ALLOC_SUCC ESS

DNIS resource allocation succeeded.

RM_DNIS_RES_ALLOC_FAIL

DNIS resource allocation failed.

RM_DNIS_RPM_REQUEST

DNIS resource pool management requested.

You can use the resource pool state to isolate problems. For example, if a call fails authorization in the RM_RES_AUTHOR state, investigate further with AAA authorization debugs to determine whether the problem lies in the resource-pool manager, AAA, or dispatcher.

Examples

The following example shows different instances where you can use the debug resource-pool command: Router# debug resource-pool RM general debugging is on Router# show debug General OS: AAA Authorization debugging is on Resource Pool: resource-pool general debugging is on Router # Router #ping 21.1.1.10 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 21.1.1.10, timeout is 2 seconds: *Jan 8 00:10:30.358: RM state:RM_IDLE event:DIALER_INCALL DS0:0:0:0:1 *Jan 8 00:10:30.358: RM: event incoming call /* An incoming call is received by RM */ *Jan 8 00:10:30.358: RM state:RM_DNIS_AUTHOR event:RM_DNIS_RPM_REQUEST DS0:0:0:0:1 /* Receives an event notifying to proceed with RPM authorization while in DNIS authorization state */ *Jan *Jan

8 00:10:30.358: RM:RPM event incoming call 8 00:10:30.358: RPM profile cp1 found

/* A customer profile "cp1" is found the local database */

matching for the incoming call, in

*Jan 8 00:10:30.358: RM state:RM_RPM_RES_AUTHOR event:RM_RPM_RES_AUTHOR_SUCCESS DS0:0:0:0:1


DB-1900

May 2008


/* Resource authorization success event received while in authorization state*/

resource

*Jan 8 00:10:30.358: Allocated resource from res_group isdn1 *Jan 8 00:10:30.358: RM:RPM profile "cp1", allocated resource "isdn1" successfully *Jan 8 00:10:30.358: RM state:RM_RPM_RES_ALLOCATING event:RM_RPM_RES_ALLOC_SUCCESS DS0:0:0:0:1 /* Resource allocation sucess event received while attempting to allocate a resource */ *Jan 8 00:10:30.358: Se0:1 AAA/ACCT/RM: doing resource-allocated (local) (nothing to do) *Jan 8 00:10:30.366: %LINK-3-UPDOWN: Interface Serial0:1, changed state to up *Jan 8 00:10:30.370: %LINK-3-UPDOWN: Interface Serial0:1, changed state to down *Jan 8 00:10:30.570: Se0:1 AAA/ACCT/RM: doing resource-update (local) cp1 (nothing to do) *Jan 8 00:10:30.578: %LINK-3-UPDOWN: I.nterface Serial0:0, changed state to up *Jan 8 00:10:30.582: %DIALER-6-BIND: Interface Serial0:0 bound to profile Dialer0... Success rate is 0 percent (0/5) Router # *Jan 8 00:10:36.662: %ISDN-6-CONNECT: Interface Serial0:0 is now connected to 71017 *Jan 8 00:10:52.990: %DIALER-6-UNBIND: Interface Serial0:0 unbound from profile Dialer0 *Jan 8 00:10:52.990: %ISDN-6-DISCONNECT: Interface Serial0:0 disconnected from 71017 , call lasted 22 seconds *Jan 8 00:10:53.206: %LINK-3-UPDOWN: Interface Serial0:0, changed state to down *Jan 8 00:10:53.206: %ISDN-6-DISCONNECT: Interface Serial0:1 disconnected from unknown , call lasted 22 seconds *Jan 8 00:10:53.626: RM state:RM_RPM_RES_ALLOCATED event:DIALER_DISCON DS0:0:0:0:1 /* Received Disconnect event from signalling stack has a resource allocated. */ *Jan

for a call which

8 00:10:53.626: RM:RPM event call drop

/* RM processing the disconnect event */ *Jan 8 00:10:53.626: Deallocated resource from res_group isdn1 *Jan 8 00:10:53.626: RM state:RM_RPM_DISCONNECTING event:RM_RPM_DISC_ACK DS0:0:0:0:1 /* An intermediate state while the DISCONNECT event is being processed by external servers, before RM goes back into IDLE state. */


debug resource-pool Field Descriptions

Field

Description

RM state:RM_IDLE

Resource manager state that displays no active calls.

RM state:RM_RES_AUTHOR

Resource authorization state.


DB-1901


Table 293

debug resource-pool Field Descriptions (continued)

Field

Description

RES_AUTHOR_SUCCESS DS0: shelf:slot:port:channel

Actual physical resource that is used

Allocated resource from res_group

Physical resource group that accepts the call.

RM profile , allocated resource

Specific customer profile and resource group names used to accept the call.

RM state: RM_RES_ALLOCATING

Resource manager state that unifies a call with a physical resource.


DB-1902

May 2008

Debug Commands debug rif

debug rif To display information on entries entering and leaving the routing information field (RIF) cache, use the debug rif command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rif no debug rif

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

In order to use the debug rif command to display traffic source-routed through an interface, fast switching of source route bridging (SRB) frames must first be disabled with the no source-bridge route-cache interface configuration command.

Examples

The following is sample output from the debug rif command: router# debug rif

Non-SDLLC or non-LocalAck entry

RIF: U chk da=9000.5a59.04f9,sa=0110.2222.33c1 [4880.3201.00A1.0050] type 8 on static/remote/0 RIF: U chk da=0000.3080.4aed,sa=0000.0000.0000 [] type 8 on TokenRing0/0 RIF: U add 1000.5a59.04f9 [4880.3201.00A1.0050] type 8 RIF: L checking da=0000.3080.4aed, sa=0000.0000.0000 RIF: rcvd TEST response from 9000.5a59.04f9 RIF: U upd da=1000.5a59.04f9,sa=0110.2222.33c1 [4880.3201.00A1.0050] RIF: rcvd XID response from 9000.5a59.04f9 SR1: sent XID response to 9000.5a59.04f9 S2559

SDLLC or Local-Ack entry

The first line of output is an example of a RIF entry for an interface configured for SDLC Logical Link Control (SDLLC) or Local-Ack. Table 294 describes significant fields shown in the display. Table 294

debug rif Field Descriptions

Field

Description

RIF:

This message describes RIF debugging output.

U chk

Update checking. The entry is being updated; the timer is set to zero (0).

da=9000.5a59.04f9

Destination MAC address.

sa=0110.2222.33c1

Source MAC address. This field contains values of zero (0000.0000.0000) in a non-SDLLC or non-Local-Ack entry.


DB-1903


Table 294

debug rif Field Descriptions (continued)

Field

Description

[4880.3201.00A1.0050]

RIF string. This field is blank (null RIF) in a non-SDLLC or non-Local-Ack entry.

type 8

Possible values follow:

on static/remote/0

•

0—Null entry

•

1—This entry was learned from a particular Token Ring port (interface)

•

2—Statically configured

•

4—Statically configured for a remote interface

•

8—This entry is to be aged

•

16—This entry (which has been learned from a remote interface) is to be aged

•

32—This entry is not to be aged

•

64—This interface is to be used by LAN Network Manager (and is not to be aged)

This route was learned from a real Token Ring port, in contrast to a virtual ring.

The following line of output is an example of a RIF entry for an interface that is not configured for SDLLC or Local-Ack: RIF: U chk da=0000.3080.4aed,sa=0000.0000.0000 [] type 8 on TokenRing0/0

Notice that the source address contains only zero values (0000.0000.0000), and that the RIF string is null ([ ]). The last element in the entry indicates that this route was learned from a virtual ring, rather than a real Token Ring port. The following line shows that a new entry has been added to the RIF cache: RIF: U add 1000.5a59.04f9 [4880.3201.00A1.0050] type 8

The following line shows that a RIF cache lookup operation has taken place: RIF: L checking da=0000.3080.4aed, sa=0000.0000.0000

The following line shows that a TEST response from address 9000.5a59.04f9 was inserted into the RIF cache: RIF: rcvd TEST response from 9000.5a59.04f9

The following line shows that the RIF entry for this route has been found and updated: RIF: U upd da=1000.5a59.04f9,sa=0110.2222.33c1 [4880.3201.00A1.0050]

The following line shows that an XID response from this address was inserted into the RIF cache: RIF: rcvd XID response from 9000.5a59.04f9

The following line shows that the router sent an XID response to this address: SR1: sent XID response to 9000.5a59.04f9


DB-1904

May 2008


Table 295 explains the other possible lines of debug rif command output. Table 295

Related Commands

Additional debug rif Field Descriptions

Field

Description

RIF: L Sending XID for

Router/bridge wanted to send a packet to address but did not find it in the RIF cache. It sent an XID explorer packet to determine which RIF it should use. The attempted packet is dropped.

RIF: L No buffer for XID to

Similar to the previous description; however, a buffer in which to build the XID packet could not be obtained.

RIF: U remote rif too small

Packet’s RIF was too short to be valid.

RIF: U rej too big

Packet’s RIF exceeded the maximum size allowed and was rejected. The maximum size is 18 bytes.

RIF: U upd interface

RIF entry for this router/bridge’s interface has been updated.

RIF: U ign interface update

RIF entry that would have updated an interface corresponding to one of this router’s interfaces.

RIF: U add

RIF entry for address has been added to the RIF cache.

RIF: U no memory to add rif for

No memory to add a RIF entry for address.

RIF: removing rif entry for

RIF entry for address has been forcibly removed.

RIF: flushed

RIF entry for address has been removed because of a RIF cache flush.

RIF: expired

RIF entry for address has been aged out of the RIF cache.

Command

Description

debug list

Filters debugging information on a per-interface or per-access list basis.


DB-1905

Debug Commands debug route-map ipc

debug route-map ipc To display a summary of the one-way Inter-process Communications (IPC) messages set from the route processor (RP) to the Versatile Interface Processor (VIP) about NetFlow policy routing when distributed Cisco Express Forwarding (dCEF) is enabled, use the debug route-map ipc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug route-map ipc no debug route-map ipc

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T


12.2(33)SRA


12.2SX


Usage Guidelines

This command is especially helpful for policy routing with dCEF switching. This command displays a summary of one-way IPC messages from the RP to the VIP about NetFlow policy routing. If you execute this command on the RP, the messages are shown as “Sent.” If you execute this command on the VIP console, the IPC messages are shown as “Received.”

Examples

The following is sample output from the debug route-map ipc command executed at the RP: Router# debug route-map ipc Routemap related IPC debugging is on Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip cef distributed Router(config)#^Z Router# RM-IPC: RM-IPC: RM-IPC: RM-IPC: RM-IPC: RM-IPC:

Clean routemap config in slot 0 Sent clean-all-routemaps; len 12 Download all policy-routing related routemap config to slot 0 Sent add routemap test(seq:10); n_len 5; len 17 Sent add acl 1 of routemap test(seq:10); len 21 Sent add min 10 max 300 of routemap test(seq:10); len 24


DB-1906

May 2008

Debug Commands debug route-map ipc

RM-IPC: RM-IPC: RM-IPC: RM-IPC: RM-IPC: RM-IPC:

Sent Sent Sent Sent Sent Sent

add add add add add add

preced 1 of routemap test(seq:10); len 17 tos 4 of routemap test(seq:10); len 17 nexthop 50.0.0.8 of routemap test(seq:10); len 20 default nexthop 50.0.0.9 of routemap test(seq:10); len 20 interface Ethernet0/0/3(5) of routemap test(seq:10); len 20 default interface Ethernet0/0/2(4) of routemap test(seq:10); len 20

The following is sample output from the debug route-map ipc command executed at the VIP: VIP-Slot0# debug route-map ipc Routemap related IPC debugging is on VIP-Slot0# RM-IPC: Rcvd RM-IPC: Rcvd RM-IPC: Rcvd RM-IPC: Rcvd RM-IPC: Rcvd RM-IPC: Rcvd RP-IPC: Rcvd RP-IPC: Rcvd RM-IPC: Rcvd RM-IPC: Rcvd

clean-all-routemaps; len 12 add routemap test(seq:10); n_len 5; len 17 add acl 1 of routemap test(seq:10); len 21 add min 10 max 300 of routemap test(seq:10); len 24 add preced 1 of routemap test(seq:10); len 17 add tos 4 of routemap test(seq:10); len 17 add nexthop 50.0.0.8 of routemap test(seq:10); len 20 add default nexthop 50.0.0.9 of routemap test(seq:10); len 20 add interface Ethernet0/3 of routemap tes; len 20 add default interface Ethernet0/2 of routemap test(seq:10); len 20


DB-1907

Debug Commands debug rpms-proc preauth

debug rpms-proc preauth To enable diagnostic reporting of preauthentication information, use the debug rpms-proc preauth command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rpms-proc preauth {all | h323 | sip} no debug rpms-proc preauth {all | h323 | sip}

Syntax Description

all

Provides information for all calls.

h323

Provides information for H.323 calls.

sip

Provides information for Session Initiation Protocol (SIP) calls.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Examples

The following example shows debugging output for two calls. The first is a leg 3 SIP call, and the second is a leg 3 H.323 call: Router# debug rpms-proc preauth all All RPMS Process preauth tracing is enabled Feb 10 14:00:07.236: Entering rpms_proc_print_preauth_req Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb

10 10 10 10 10 10 10 10 10 10 10 10 10 10 10

14:00:07.236: Request = 0 14:00:07.236: Preauth id = 8 14:00:07.236: EndPt Type = 1 14:00:07.236: EndPt = 192.168.80.70 14:00:07.236: Resource Service = 1 14:00:07.236: Call_origin = answer 14:00:07.236: Call_type = voip 14:00:07.236: Calling_num = 2220001 14:00:07.236: Called_num = 1120001 14:00:07.236: Protocol = 1 14:00:07.236:rpms_proc_create_node:Created node with preauth_id = 8 14:00:07.236:rpms_proc_send_aaa_req:uid got is 19 14:00:07.240:rpms_proc_preauth_response:Context is for preauth_id 8, aaa_uid 19 14:00:07.240:rpms_proc_preauth_response:Deleting Tree node for preauth id 8 uid 19 14:00:07.284: Entering rpms_proc_print_preauth_req

Feb 10 14:00:07.284: Request = 0


DB-1908

May 2008


Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb

10 10 10 10 10 10 10 10 10 10 10 10 10

14:00:07.284: Preauth id = 9 14:00:07.284: EndPt Type = 1 14:00:07.284: EndPt = 192.168.81.102 14:00:07.284: Resource Service = 1 14:00:07.284: Call_origin = answer 14:00:07.284: Call_type = voip 14:00:07.284: Calling_num = 2210001 14:00:07.284: Called_num = 1#1110001 14:00:07.284: Protocol = 0 14:00:07.288:rpms_proc_create_node:Created node with preauth_id = 9 14:00:07.288:rpms_proc_send_aaa_req:uid got is 21 14:00:07.300:rpms_proc_preauth_response:Context is for preauth_id 9, aaa_uid 21 14:00:07.300:rpms_proc_preauth_response:Deleting Tree node for preauth id 9 uid 21

The following example shows the output for a single leg 3 H.323 call: Router# debug rpms-proc preauth h323 RPMS Process H323 preauth tracing is enabled Feb 10 14:04:57.867: Entering rpms_proc_print_preauth_req Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb

10 10 10 10 10 10 10 10 10 10 10 10 10 10

14:04:57.867: Request = 0 14:04:57.867: Preauth id = 10 14:04:57.867: EndPt Type = 1 14:04:57.867: EndPt = 192.168.81.102 14:04:57.867: Resource Service = 1 14:04:57.867: Call_origin = answer 14:04:57.867: Call_type = voip 14:04:57.867: Calling_num = 2210001 14:04:57.867: Called_num = 1#1110001 14:04:57.867: Protocol = 0 14:04:57.867:rpms_proc_create_node:Created node with preauth_id = 10 14:04:57.867:rpms_proc_send_aaa_req:uid got is 25 14:04:57.875:rpms_proc_preauth_response:Context is for preauth_id 10, aaa_uid 25 14:04:57.875:rpms_proc_preauth_response:Deleting Tree node for preauth id 10 uid 25

The following example shows output for a single leg 3 SIP call: Router# debug rpms-proc preauth sip RPMS Process SIP preauth tracing is enabled Feb 10 14:08:02.880: Entering rpms_proc_print_preauth_req Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb

10 10 10 10 10 10 10 10 10 10 10 10 10 10

14:08:02.880: Request = 0 14:08:02.880: Preauth id = 11 14:08:02.880: EndPt Type = 1 14:08:02.880: EndPt = 192.168.80.70 14:08:02.880: Resource Service = 1 14:08:02.880: Call_origin = answer 14:08:02.880: Call_type = voip 14:08:02.880: Calling_num = 2220001 14:08:02.880: Called_num = 1120001 14:08:02.880: Protocol = 1 14:08:02.880:rpms_proc_create_node:Created node with preauth_id = 11 14:08:02.880:rpms_proc_send_aaa_req:uid got is 28 14:08:02.888:rpms_proc_preauth_response:Context is for preauth_id 11, aaa_uid 28 14:08:02.888:rpms_proc_preauth_response:Deleting Tree node for preauth id 11 uid 28


DB-1909



debug rpms-proc preauth Field Descriptions

Field

Description

Request


Preauth id


EndPt Type

Call Origin End Point Type—1 for IP address, 2 for Interzone ClearToken (IZCT) value.

EndPt


Resource Service


Call_origin

Answer.

Call_type


Calling_num

Calling party number (calling line identification, or CLID).

Called_num

Called party number (dialed number identification service, or DNIS).

Protocol


function reports



DB-1910

May 2008

Debug Commands debug rtpspi all

debug rtpspi all To debug all Routing Table Protocol (RTP) security parameter index (SPI) errors, sessions, and in/out functions, use the debug rtpspi all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtpspi all no debug rtpspi all

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK

This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620).

12.2(33)SRA


12.2SX


Usage Guidelines Caution

Examples

Be careful when you use this command because it can result in console flooding and reduced voice quality.

The following example shows a debug trace for RTP SPI errors, sessions, and in/out functions on a gateway: Router# debug rtpspi all RTP SPI Error, Session and function in/out tracings are enabled. *Mar *Mar *Mar *Mar

1 1 1 1

00:38:59.381:rtpspi_allocate_rtp_port:Entered. 00:38:59.381:rtpspi_allocate_rtp_port:allocated RTP port 16544 00:38:59.381:rtpspi_allocate_rtp_port:Success. port = 16544. Leaving. 00:38:59.381:rtpspi_call_setup_request:entered. Call Id = 5, dest = 0.0.0.0; callInfo: final dest flag = 0, rtp_session_mode = 0x2, local_ip_addrs = 0x5000001,remote_ip_addrs = 0x0, local rtp port = 16544, remote rtp port = 0


DB-1911


*Mar *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1 1

00:38:59.381:rtpspi_call_setup_request:spi_info copied for rtpspi_app_data_t. 00:38:59.385:rtpspi_call_setup_request:leaving 00:38:59.385:rtpspi_call_setup() entered 00:38:59.385:rtpspi_initialize_ccb:Entered 00:38:59.385:rtpspi_initialize_ccb:leaving 00:38:59.385:rtpspi_call_setup:rtp_session_mode = 0x2 00:38:59.385:rtpspi_call_setup:mode = CC_CALL_NORMAL. destianation number = 0.0.0.0 *Mar 1 00:38:59.385:rtpspi_call_setup:Passed local_ip_addrs=0x5000001 *Mar 1 00:38:59.385:rtpspi_call_setup:Passed local_rtp_port = 16544 *Mar 1 00:38:59.385:rtpspi_call_setup:Saved RTCP Session = 0x1AF57E0 *Mar 1 00:38:59.385:rtpspi_call_setup:Passed remote rtp port = 0. *Mar 1 00:38:59.389:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=0, rem ip=0x0 *Mar 1 00:38:59.389:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2 *Mar 1 00:38:59.389:rtpspi_start_rtcp_session:Starting RTCP session. Local IP addr = 0x5000001, Remote IP addr = 0x0, Local RTP port = 16544, Remote RTP port = 0, mode = 0x2 *Mar 1 00:38:59.389:rtpspi_start_rtcp_session:RTP Session creation Success. *Mar 1 00:38:59.389:rtpspi_call_setup:RTP Session creation Success. *Mar 1 00:38:59.389:rtpspi_call_setup:calling cc_api_call_connected() *Mar 1 00:38:59.389:rtpspi_call_setup:Leaving. *Mar 1 00:38:59.393:rtpspi_bridge:entered. conf id = 1, src i/f = 0x1859E88, dest i/f = 0x1964EEC, src call id = 5, dest call id = 4 call info = 0x1919140, xmit fn = 0xDA7494, tag = 0 *Mar 1 00:38:59.393:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2 *Mar 1 00:38:59.393:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494, dstIF=0x1964EEC, dstCallID=4, voip_mode=0x2, rtp_mode=0x2, ssrc_status=0 *Mar 1 00:38:59.393:rtpspi_bridge:Calling cc_api_bridge_done() for 5(0x1AF5400) and 4(0x0). *Mar 1 00:38:59.393:rtpspi_bridge:leaving. *Mar 1 00:38:59.397:rtpspi_caps_ind:Entered. vdb = 0x1859E88 call id = 5, srcCallId = 4 *Mar 1 00:38:59.397:rtpspi_caps_ind:caps from VTSP:codec=0x83FB, codec_bytes=0x50, fax rate=0x7F, vad=0x3 modem=0x0 *Mar 1 00:38:59.397:rtpspi_get_rtcp_session_parameters():CURRENT VALUES: dstIF=0x1964EEC, dstCallID=4, current_seq_num=0x0 *Mar 1 00:38:59.397:rtpspi_get_rtcp_session_parameters():NEW VALUES: dstIF=0x1964EEC, dstCallID=4, current_seq_num=0x261C *Mar 1 00:38:59.397:rtpspi_caps_ind:Caps Used:codec=0x1, codec bytes=80, fax rate=0x1, vad=0x1, modem=0x1, dtmf_relay=0x1, seq_num_start=0x261D *Mar 1 00:38:59.397:rtpspi_caps_ind:calling cc_api_caps_ind(). *Mar 1 00:38:59.397:rtpspi_caps_ind:Returning success *Mar 1 00:38:59.397:rtpspi_caps_ack:Entered. call id = 5, srcCallId = 4 *Mar 1 00:38:59.397:rtpspi_caps_ack:leaving. *Mar 1 00:38:59.618:rtpspi_call_modify:entered. call-id=5, nominator=0x7, params=0x18DD440 *Mar 1 00:38:59.618:rtpspi_call_modify:leaving *Mar 1 00:38:59.618:rtpspi_do_call_modify:Entered. call-id = 5 *Mar 1 00:38:59.622:rtpspi_do_call_modify:Remote RTP port changed. New port=16432 *Mar 1 00:38:59.622:rtpspi_do_call_modify:Remote IP addrs changed. New IP addrs=0x6000001 *Mar 1 00:38:59.622:rtpspi_do_call_modify:new mode 2 is the same as the current mode *Mar 1 00:38:59.622:rtpspi_do_call_modify:Starting new RTCP session. *Mar 1 00:38:59.622:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=16432, rem ip=0x6000001 *Mar 1 00:38:59.622:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2 *Mar 1 00:38:59.622:rtpspi_start_rtcp_session:Removing old RTCP session. *Mar 1 00:38:59.622:rtpspi_start_rtcp_session:Starting RTCP session. Local IP addr = 0x5000001, Remote IP addr = 0x6000001, Local RTP port = 16544, Remote RTP port = 16432, mode = 0x2 *Mar 1 00:38:59.622:rtpspi_start_rtcp_session:RTCP Timer creation Success. (5)*(5000) *Mar 1 00:38:59.622:rtpspi_start_rtcp_session:RTP Session creation Success. *Mar 1 00:38:59.622:rtpspi_do_call_modify:RTP Session creation Success. *Mar 1 00:38:59.622:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0 *Mar 1 00:38:59.626:rtpspi_do_call_modify:success. leaving


DB-1912

May 2008


*Mar 1 00:39:05.019:rtpspi_call_modify:entered. call-id=5, nominator=0x7, params=0x18DD440 *Mar 1 00:39:05.019:rtpspi_call_modify:leaving *Mar 1 00:39:05.019:rtpspi_do_call_modify:Entered. call-id = 5 *Mar 1 00:39:05.019:rtpspi_do_call_modify:New remote RTP port = old rtp port = 16432 *Mar 1 00:39:05.019:rtpspi_do_call_modify:New remote IP addrs = old IP addrs = 0x6000001 *Mar 1 00:39:05.019:rtpspi_do_call_modify:Mode changed. new = 3, old = 2 *Mar 1 00:39:05.019:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3 *Mar 1 00:39:05.023:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494, dstIF=0x1964EEC, dstCallID=4, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2 *Mar 1 00:39:05.023:rtpspi_do_call_modify:RTCP Timer start. *Mar 1 00:39:05.023:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0 *Mar 1 00:39:05.023:rtpspi_do_call_modify:success. leaving *Mar 1 00:40:13.786:rtpspi_bridge_drop:entered. src call-id=5, dest call-id=4, tag=0 *Mar 1 00:40:13.786:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3 *Mar 1 00:40:13.786:rtpspi_modify_rtcp_session_parameters():xmit fn=0x0, dstIF=0x0, dstCallID=0, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2 *Mar 1 00:40:13.786:rtpspi_bridge_drop:leaving *Mar 1 00:40:13.790:rtpspi_call_disconnect:entered. call-id=5, cause=16, tag=0 *Mar 1 00:40:13.790:rtpspi_call_disconnect:leaving. *Mar 1 00:40:13.790:rtpspi_do_call_disconnect:Entered. call-id = 5 *Mar 1 00:40:13.790:rtpspi_do_call_disconnect:calling rtpspi_call_cleanup(). call-id=5 *Mar 1 00:40:13.794:rtpspi_call_cleanup:entered. ccb = 0x1AF5400, call-id=5, rtp port = 16544 *Mar 1 00:40:13.794:rtpspi_call_cleanup:releasing ccb cache. RTP port=16544 *Mar 1 00:40:13.794:rtpspi_store_call_history_entry():Entered. *Mar 1 00:40:13.794:rtpspi_store_call_history_entry():Leaving. *Mar 1 00:40:13.794:rtpspi_call_cleanup:RTCP Timer Stop. *Mar 1 00:40:13.794:rtpspi_call_cleanup:deallocating RTP port 16544. *Mar 1 00:40:13.794:rtpspi_free_rtcp_session:Entered. *Mar 1 00:40:13.794:rtpspi_free_rtcp_session:Success. Leaving *Mar 1 00:40:13.794::rtpspi_call_cleanup freeing ccb (0x1AF5400) *Mar 1 00:40:13.794:rtpspi_call_cleanup:leaving *Mar 1 00:40:13.794:rtpspi_do_call_disconnect:leaving

Related Commands

Command

Description

debug rtpspi errors

Debugs RTP SPI errors.

debug rtpspi inout

Debugs RTP SPI in/out functions.

debug rtpspi send-nse

Triggers the RTP SPI to send a triple redundant NSE.

debug sgcp errors

Debugs SGCP errors.

debug sgcp events

Debugs SGCP events.

debug sgcp packet

Debugs SGCP packets.

debug vtsp send-nse

Sends and debugs a triple redundant NSE from the DSP to a remote gateway.


DB-1913

Debug Commands debug rtpspi errors

debug rtpspi errors To debug Routing Table Protocol (RTP) security parameter index (SPI) errors, use the debug rtpspi errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtpspi errors no debug rtpspi errors

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK

This command was introduced on the Cisco MC3810 device and Cisco 3600 series routers (except the Cisco 3620).

12.2(33)SRA


12.2SX



Examples


This example shows a debug trace for RTP SPI errors on two gateways. The following example shows the debug trace on the first gateway: Router# debug rtpspi errors 00:54:13.272:rtpspi_do_call_modify:new mode 2 is the same as the current mode 00:54:18.738:rtpspi_do_call_modify:New remote RTP port = old rtp port = 16452 00:54:18.738:rtpspi_do_call_modify:New remote IP addrs = old IP addrs = 0x6000001

The following example shows the debug trace on the second gateway: Router# debug rtpspi errors 00:54:08:rtpspi_process_timers:


DB-1914

May 2008

Debug Commands debug rtpspi errors

00:54:08:rtpspi_process_timers:Timer 00:54:08:rtpspi_process_timers:Timer 00:54:08:rtpspi_process_timers: 00:54:08:rtpspi_process_timers:Timer 00:54:08:rtpspi_process_timers:Timer 00:54:08:rtpspi_process_timers: 00:54:08:rtpspi_process_timers:Timer 00:54:08:rtpspi_process_timers:Timer 00:54:09:rtpspi_process_timers: 00:54:09:rtpspi_process_timers:Timer 00:54:09:rtpspi_process_timers:Timer 00:54:09:rtpspi_process_timers: 00:54:09:rtpspi_process_timers:Timer 00:54:09:rtpspi_process_timers:Timer

Related Commands

0x1A5AF9C expired. expired for callID 0x3 0x1A5AF9C expired. expired for callID 0x3 0x1A5AF9C expired. expired for callID 0x3 0x1A5AFBC expired. expired for callID 0x3 0x1A5B364 expired. expired for callID 0x3

Command

Description

debug rtpspi all

Debugs all RTP SPI errors, sessions, and in/out functions.

debug rtpspi inout




debug sgcp errors

Debugs SGCP errors.

debug sgcp events

Debugs SGCP events.

debug sgcp packet


debug vtsp send-nse



DB-1915

Debug Commands debug rtpspi inout

debug rtpspi inout To debug Routing Table Protocol (RTP) security parameter index (SPI) in/out functions, use the debug rtpspi inout command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtpspi inout no debug rtpspi inout

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK

This command was introduced on the Cisco MC3810 device and Cisco 3600 series routers (except the Cisco 3620 device).

12.2(33)SRA


12.2SX



Examples


The following example shows a debug trace for RTP SPI in/out functions on a gateway: Router# debug rtpspi inout *Mar *Mar *Mar

*Mar *Mar *Mar *Mar

1 00:57:24.565:rtpspi_allocate_rtp_port:Entered. 1 00:57:24.565:rtpspi_allocate_rtp_port:Success. port = 16520. Leaving. 1 00:57:24.565:rtpspi_call_setup_request:entered. Call Id = 9, dest = 0.0.0.0; callInfo: final dest flag = 0, rtp_session_mode = 0x2, local_ip_addrs = 0x5000001,remote_ip_addrs = 0x0, local rtp port = 16520, remote rtp port = 0 1 00:57:24.565:rtpspi_call_setup_request:spi_info copied for rtpspi_app_data_t. 1 00:57:24.565:rtpspi_call_setup_request:leaving 1 00:57:24.569:rtpspi_call_setup() entered 1 00:57:24.569:rtpspi_initialize_ccb:Entered


DB-1916

May 2008

Debug Commands debug rtpspi inout

*Mar 1 00:57:24.569:rtpspi_initialize_ccb:leaving *Mar 1 00:57:24.569:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=0, rem ip=0x0 *Mar 1 00:57:24.569:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2 *Mar 1 00:57:24.569:rtpspi_call_setup:Leaving. *Mar 1 00:57:24.573:rtpspi_bridge:entered. conf id = 3, src i/f = 0x1859E88, dest i/f = 0x1964EEC, src call id = 9, dest call id = 8 call info = 0x1919140, xmit fn = 0xDA7494, tag = 0 *Mar 1 00:57:24.573:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2 *Mar 1 00:57:24.573:rtpspi_bridge:leaving. *Mar 1 00:57:24.573:rtpspi_caps_ind:Entered. vdb = 0x1859E88 call id = 9, srcCallId = 8 *Mar 1 00:57:24.577:rtpspi_caps_ind:Returning success *Mar 1 00:57:24.577:rtpspi_caps_ack:Entered. call id = 9, srcCallId = 8 *Mar 1 00:57:24.577:rtpspi_caps_ack:leaving. *Mar 1 00:57:24.818:rtpspi_call_modify:entered. call-id=9, nominator=0x7, params=0x18DD440 *Mar 1 00:57:24.818:rtpspi_call_modify:leaving *Mar 1 00:57:24.818:rtpspi_do_call_modify:Entered. call-id = 9 *Mar 1 00:57:24.818:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=16396, rem ip=0x6000001 *Mar 1 00:57:24.822:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2 *Mar 1 00:57:24.822:rtpspi_do_call_modify:success. leaving *Mar 1 00:57:30.296:rtpspi_call_modify:entered. call-id=9, nominator=0x7, params=0x18DD440 *Mar 1 00:57:30.296:rtpspi_call_modify:leaving *Mar 1 00:57:30.300:rtpspi_do_call_modify:Entered. call-id = 9 *Mar 1 00:57:30.300:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3 *Mar 1 00:57:30.300:rtpspi_do_call_modify:success. leaving *Mar 1 00:58:39.055:rtpspi_bridge_drop:entered. src call-id=9, dest call-id=8, tag=0 *Mar 1 00:58:39.055:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3 *Mar 1 00:58:39.055:rtpspi_bridge_drop:leaving *Mar 1 00:58:39.059:rtpspi_call_disconnect:entered. call-id=9, cause=16, tag=0 *Mar 1 00:58:39.059:rtpspi_call_disconnect:leaving. *Mar 1 00:58:39.059:rtpspi_do_call_disconnect:Entered. call-id = 9 *Mar 1 00:58:39.059:rtpspi_call_cleanup:entered. ccb = 0x1AF5400, call-id=9, rtp port = 16520 *Mar 1 00:58:39.059:rtpspi_store_call_history_entry():Entered. *Mar 1 00:58:39.059:rtpspi_store_call_history_entry():Leaving. *Mar 1 00:58:39.059:rtpspi_free_rtcp_session:Entered. *Mar 1 00:58:39.059:rtpspi_free_rtcp_session:Success. Leaving *Mar 1 00:58:39.063:rtpspi_call_cleanup:leaving *Mar 1 00:58:39.063:rtpspi_do_call_disconnect:leaving

Related Commands

Command

Description

debug rtpspi all


debug rtpspi errors




debug sgcp errors

Debugs SGCP errors.

debug sgcp events

Debugs SGCP events.

debug sgcp packet


debug vtsp send-nse



DB-1917

Debug Commands debug rtpspi send-nse

debug rtpspi send-nse To trigger the Routing Table Protocol (RTP) security parameter index (SPI) software module to send a triple redundant NSE, use the debug rtpspi send-nse command in privileged EXEC mode. To disable this action, use the no form of the command. debug rtpspi send-nse call-ID NSE-event-ID no debug rtpspi send-nse call-ID NSE-event-ID

Syntax Description

call-ID

Specifies the call ID of the active call. The valid range is from 0 to 65535.

NSE-event-ID

Specifies the NSE Event ID. The valid range is from 0 to 255.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK

This command was introduced on the Cisco MC3810 device and Cisco 3600 series routers (except the Cisco 3620 router).

12.2(33)SRA


12.2SX


Examples

The following example shows the RTP SPI software module set to send an NSE: Router# debug rtpspi send-nse

Related Commands

Command

Description

debug rtpspi all


debug rtpspi errors


debug rtpspi inout


debug sgcp errors

Debugs SGCP errors.

debug sgcp events

Debugs SGCP events.

debug sgcp packet


debug vtsp send-nse



DB-1918

May 2008

Debug Commands debug rtpspi session

debug rtpspi session To debug all Routing Table Protocol (RTP) security parameter index (SPI) sessions, use the debug rtpspi session command in privileged EXEC mode. To disable debugging, use the no form of this command. debug rtpspi session no debug rtpspi session

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK

This command was introduced on the Cisco MC3810 device and Cisco 3600 series routers (except the Cisco 3620 router).

12.2(33)SRA


12.2SX


Examples

The following example shows a debug trace for RTP SPI sessions on a gateway: Router# debug rtpspi session *Mar *Mar *Mar

1 01:01:51.593:rtpspi_allocate_rtp_port:allocated RTP port 16406 1 01:01:51.593:rtpspi_call_setup:rtp_session_mode = 0x2 1 01:01:51.593:rtpspi_call_setup:mode = CC_CALL_NORMAL. destianation number = 0.0.0.0 *Mar 1 01:01:51.593:rtpspi_call_setup:Passed local_ip_addrs=0x5000001 *Mar 1 01:01:51.593:rtpspi_call_setup:Passed local_rtp_port = 16406 *Mar 1 01:01:51.593:rtpspi_call_setup:Saved RTCP Session = 0x1AFDFBC *Mar 1 01:01:51.593:rtpspi_call_setup:Passed remote rtp port = 0. *Mar 1 01:01:51.598:rtpspi_start_rtcp_session:Starting RTCP session. Local IP addr = 0x5000001, Remote IP addr = 0x0, Local RTP port = 16406, Remote RTP port = 0, mode = 0x2 *Mar 1 01:01:51.598:rtpspi_start_rtcp_session:RTP Session creation Success. *Mar 1 01:01:51.598:rtpspi_call_setup:RTP Session creation Success. *Mar 1 01:01:51.598:rtpspi_call_setup:calling cc_api_call_connected() *Mar 1 01:01:51.598:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494, dstIF=0x1964EEC, dstCallID=10, voip_mode=0x2, rtp_mode=0x2, ssrc_status=0 *Mar 1 01:01:51.598:rtpspi_bridge:Calling cc_api_bridge_done() for 11(0x1AF5400) and 10(0x0). *Mar 1 01:01:51.602:rtpspi_caps_ind:caps from VTSP:codec=0x83FB, codec_bytes=0x50, fax rate=0x7F, vad=0x3 modem=0x0 *Mar 1 01:01:51.602:rtpspi_get_rtcp_session_parameters():CURRENT VALUES: dstIF=0x1964EEC, dstCallID=10, current_seq_num=0x0


DB-1919

Debug Commands debug rtpspi session

*Mar 1 01:01:51.602:rtpspi_get_rtcp_session_parameters():NEW VALUES: dstIF=0x1964EEC, dstCallID=10, current_seq_num=0xF1E *Mar 1 01:01:51.602:rtpspi_caps_ind:Caps Used:codec=0x1, codec bytes=80, fax rate=0x1, vad=0x1, modem=0x1, dtmf_relay=0x1, seq_num_start=0xF1F *Mar 1 01:01:51.602:rtpspi_caps_ind:calling cc_api_caps_ind(). *Mar 1 01:01:51.822:rtpspi_do_call_modify:Remote RTP port changed. New port=16498 *Mar 1 01:01:51.822:rtpspi_do_call_modify:Remote IP addrs changed. New IP addrs=0x6000001 *Mar 1 01:01:51.822:rtpspi_do_call_modify:Starting new RTCP session. *Mar 1 01:01:51.822:rtpspi_start_rtcp_session:Removing old RTCP session. *Mar 1 01:01:51.822:rtpspi_start_rtcp_session:Starting RTCP session. Local IP addr = 0x5000001, Remote IP addr = 0x6000001, Local RTP port = 16406, Remote RTP port = 16498, mode = 0x2 *Mar 1 01:01:51.822:rtpspi_start_rtcp_session:RTCP Timer creation Success. (5)*(5000) *Mar 1 01:01:51.826:rtpspi_start_rtcp_session:RTP Session creation Success. *Mar 1 01:01:51.826:rtpspi_do_call_modify:RTP Session creation Success. *Mar 1 01:01:51.826:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0 *Mar 1 01:01:57.296:rtpspi_do_call_modify:Mode changed. new = 3, old = 2 *Mar 1 01:01:57.296:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494, dstIF=0x1964EEC, dstCallID=10, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2 *Mar 1 01:01:57.296:rtpspi_do_call_modify:RTCP Timer start. *Mar 1 01:01:57.296:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0 *Mar 1 01:03:06.108:rtpspi_modify_rtcp_session_parameters():xmit fn=0x0, dstIF=0x0, dstCallID=0, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2 *Mar 1 01:03:06.112:rtpspi_do_call_disconnect:calling rtpspi_call_cleanup(). call-id=11 *Mar 1 01:03:06.112:rtpspi_call_cleanup:releasing ccb cache. RTP port=16406 *Mar 1 01:03:06.112:rtpspi_call_cleanup:RTCP Timer Stop. *Mar 1 01:03:06.112:rtpspi_call_cleanup:deallocating RTP port 16406. *Mar 1 01:03:06.112::rtpspi_call_cleanup freeing ccb (0x1AF5400)

Related Commands

Command

Description

debug rtpspi all


debug rtpspi errors


debug rtpspi inout




debug sgcp errors

Debugs SGCP errors.

debug sgcp events

Debugs SGCP events.

debug sgcp packet


sgcp

Starts and allocates resources for the SCGP daemon.

debug vtsp send-nse



DB-1920

May 2008

Debug Commands debug rtr error

debug rtr error Note

Effective with Cisco IOS Release 12.2(31)SB2, the debug rtr error command is replaced by the debug ip sla monitor error command. Effective with Cisco IOS Release 12.2(33)SRB, the debug rtr error command is replaced by the debug ip sla error command. See the debug ip sla monitor error and debug ip sla error commands for more information. To enable debugging output of Cisco IOS IP Service Level Agreements (SLAs) operation run-time errors, use the debug rtr error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtr error [operation-number] no debug rtr error [operation-number]

Syntax Description

operation-number

Command Modes

Privileged EXEC

Command History

Release

Modification

11.2


12.0(5)T


12.3(14)T

This command was replaced by the debug ip sla monitor error command.

12.2(31)SB2

This command was replaced by the debug ip sla monitor error command.

12.2(33)SRB

This command was replaced by the debug ip sla error command.

12.2SX


Usage Guidelines

Note

(Optional) Identification number of the operation for which debugging output is to be enabled.

The debug rtr error command displays run-time errors. When an operation number other than 0 is specified, all run-time errors for that operation are displayed when the operation is active. When the operation number is 0, all run-time errors relating to the IP SLAs scheduler process are displayed. When no operation number is specified, all run-time errors for all active operations configured on the router are displayed.

Use the debug rtr error command before using the debug rtr trace command because the debug rtr error command generates a lesser amount of debugging output.


DB-1921

Debug Commands debug rtr error

Examples

The following is sample output from the debug rtr error command. The output indicates failure because the target is not there or because the responder is not enabled on the target. All debugging output for IP SLAs (including the output from the debug rtr trace command) has the format shown in Table 297. Router# debug rtr error May May May May May May May May May May May

5 5 5 5 5 5 5 5 5 5 5

05:00:35.483: 05:01:35.003: 05:02:34.527: 05:03:34.039: 05:04:33.563: 05:05:33.099: 05:06:32.596: 05:07:32.119: 05:08:31.643: 05:09:31.167: 05:10:30.683:

control control control control control control control control control control control

message message message message message message message message message message message

failure:1 failure:1 failure:1 failure:1 failure:1 failure:1 failure:1 failure:1 failure:1 failure:1 failure:1


debug rtr error Field Descriptions

Field

Description

RTR 1

Number of the operation generating the message.

Error Return Code

Message identifier indicating the error type (or error itself).

LU0 RTR Probe 1

Name of the process generating the message.

in echoTarget on call luReceive

Supplemental messages that pertain to the message identifier.

LuApiReturnCode of InvalidHandle - invalid host name or API handle

Related Commands

Command

Description

debug rtr trace

Traces the execution of an IP SLAs operation.


DB-1922

May 2008

Debug Commands debug rtr mpls-lsp-monitor

debug rtr mpls-lsp-monitor Note

Effective with Cisco IOS Release 12.2(31)SB2, the debug rtr mpls-lsp-monitor command is replaced by the debug ip sla monitor mpls-lsp-monitor command. Effective with Cisco IOS Release 12.2(33)SRB, the debug rtr mpls-lsp-monitor command is replaced by the debug ip sla mpls-lsp-monitor command. See the debug ip sla monitor mpls-lsp-monitor and debug ip sla mpls-lsp-monitor commands for more information. To enable debugging output for the IP Service Level Agreements (SLAs) label switched path (LSP) Health Monitor, use the debug rtr mpls-lsp-monitor command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtr mpls-lsp-monitor [operation-number] no debug rtr mpls-lsp-monitor [operation-number]

Syntax Description

operation-number

Command Default

Debug is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(27)SBC


12.2(33)SRA


12.2(31)SB2

This command was replaced by the debug ip sla monitor mpls-lsp-monitor command.

12.2(33)SRB

This command was replaced by the debug ip sla mpls-lsp-monitor command.

12.2SX


Examples

(Optional) Number of the LSP Health Monitor operation for which the debugging output will be displayed.

The following is sample output from the debug rtr mpls-lsp-monitor command. This output shows that three VPNs associated with router 10.10.10.8 (red, blue, and green) were discovered and that this information was added to the LSP Health Monitor scan queue. Also, since router 10.10.10.8 is a newly discovered Border Gateway Protocol (BGP) next hop neighbor, a new IP SLAs operation for router 10.10.10.8 (Probe 100005) is being created and added to the LSP Health Monitor multioperation schedule. Even though router 10.10.10.8 belongs to three VPNs, only one IP SLAs operation is being created. Router# debug rtr mpls-lsp-monitor


DB-1923

Debug Commands debug rtr mpls-lsp-monitor

SAA MPLSLM debugging for all entries is on *Aug 19 19:59: SAA MPLSLM(1):Next hop 10.10.10.8 added in AddQ *Aug 19 19:59: SAA MPLSLM(1):Next hop 10.10.10.8 added in AddQ *Aug 19 19:59: SAA MPLSLM(1):Next hop 10.10.10.8 added in AddQ *Aug 19 19:59: SAA MPLSLM(1):Adding vrf red into tree entry 10.10.10.8 *Aug 19 19:59: SAA MPLSLM(1):Adding Probe 100005 *Aug 19 19:59: SAA MPLSLM(1):Adding ProbeID 100005 to tree entry 10.10.10.8 (1) *Aug 19 19:59: SAA MPLSLM(1):Adding vrf blue into tree entry 10.10.10.8 *Aug 19 19:59: SAA MPLSLM(1):Duplicate in AddQ 10.10.10.8 *Aug 19 19:59: SAA MPLSLM(1):Adding vrf green into tree entry 10.10.10.8 *Aug 19 19:59: SAA MPLSLM(1):Duplicate in AddQ 10.10.10.8 *Aug 19 19:59: SAA MPLSLM(1):Added Probe(s) 100005 will be scheduled after 26 secs over schedule period 60

Related Commands

Command

Description

rtr mpls-lsp-monitor

Begins configuration for an IP SLAs LSP Health Monitor operation and enters SAA MPLS configuration mode.


DB-1924

May 2008

Debug Commands debug rtr trace

debug rtr trace Note

Effective with Cisco IOS Release 12.2(31)SB2, the debug rtr trace command is replaced by the debug ip sla monitor trace command. Effective with Cisco IOS Release 12.2(33)SRB, the debug rtr trace command is replaced by the debug ip sla trace command. See the debug ip sla monitor trace and debug ip sla trace commands for more information. To trace the execution of a Cisco IOS IP Service Level Agreements (SLAs) operation, use the debug rtr trace command in privileged EXEC mode. To disable trace debugging output, use the no form of this command. debug rtr trace [operation-number] no debug rtr trace [operation-number]

Syntax Description:

operation-number

Command Modes

Privileged EXEC

Command History

Release

Modification

11.2


12.0(5)T


12.3(14)T

This command was replaced by the debug ip sla monitor trace command.

12.2(31)SB2

This command was replaced by the debug ip sla monitor trace command.

12.2(33)SRB

This command was replaced by the debug ip sla trace command.

12.2SX


Usage Guidelines

(Optional) Identification number of the operation for which debugging output is to be enabled.

When an operation number other than 0 is specified, execution for that operation is traced. When the operation number is 0, the IP SLAs scheduler process is traced. When no operation number is specified, all active operations are traced. The debug rtr trace command also enables debug rtr error command for the specified operation. However, the no debug rtr trace command does not disable the debug rtr error command. You must manually disable the command by using the no debug rtr error command. All debuggng output (including debug rtr error command output) has the format shown in the debug rtr error command output example.


DB-1925

Debug Commands debug rtr trace

Note

Examples

The debug rtr trace command can generate a large number of debug messages. First use the debug rtr error command, and then use the debug rtr trace on a per-operation basis.

The following is sample output from the debug rtr trace command. In this example, an operation is traced through a single operation attempt: the setup of a connection to the target, and the attempt at an echo to calculate UDP packet response time. Router# debug rtr trace Router# RTR 1:Starting An Echo Operation - IP RTR Probe 1 May 5 05:25:08.584:rtt hash insert :3.0.0.3 3383 May 5 05:25:08.584:source=3.0.0.3(3383) dest-ip=5.0.0.1(9) May 5 05:25:08.588:sending control msg: May 5 05:25:08.588: Ver:1 ID:51 Len:52 May 5 05:25:08.592:cmd:command:RTT_CMD_UDP_PORT_ENABLE, ip:5.0.0.1, port:9, duration:5000 May 5 05:25:08.607:receiving reply May 5 05:25:08.607: Ver:1 ID:51 Len:8 May 5 05:25:08.623:local delta:8 May 5 05:25:08.627:delta from responder:1 May 5 05:25:08.627:received bytes and responseTime = 3 (ms) May 5 05:25:08.631:rtt hash remove:3.0.0.3 3383RTR 1:Starting An Echo Operation - IP RTR Probe 1 May 5 05:26:08.104:rtt hash insert :3.0.0.3 2974 May 5 05:26:08.104:source=3.0.0.3(2974) dest-ip=5.0.0.1(9) May 5 05:26:08.108:sending control msg: May 5 05:26:08.108: Ver:1 ID:52 Len:52 May 5 05:26:08.112:cmd:command:RTT_CMD_UDP_PORT_ENABLE, ip:5.0.0.1, port:9, duration:5000 May 5 05:26:08.127:receiving reply May 5 05:26:08.127: Ver:1 ID:52 Len:8 May 5 05:26:08.143:local delta:8 May 5 05:26:08.147:delta from responder:1 May 5 05:26:08.147:received bytes and responseTime = 3 (ms) May 5 05:26:08.151:rtt hash remove:3.0.0.3 2974RTR 1:Starting An Echo Operation - IP RTR Probe 1

Related Commands

Command

Description

debug rtr error

Enables debugging output of IP SLAs operation run-time errors.


DB-1926

May 2008

Debug Commands debug rtsp all

debug rtsp all To display all related information about the Real Time Streaming Protocol (RTSP) data, use the debug rtsp all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtsp all no debug rtsp all

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(11)T

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660, Cisco AS5350, Cisco AS5400, Cisco AS5850, Cisco AS5300, Cisco AS5800, and Cisco MC3810.

12.2SX


Usage Guidelines

We recommend that you log output from the debug rtsp all command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following example shows debugging output for the debug rtsp all command. The show debug command shows which RTSP modules are traced. Router# debug rtsp all All RTSP client debugging is on Router# show debug RTSP: RTSP RTSP RTSP RTSP RTSP

client client client client client

Protocol Error debugging is on Protocol Message Handler debugging is on API debugging is on socket debugging is on session debugging is on


DB-1927


Router# Router#!call initiated Router# *Mar 11 03:14:23.471: //-1//RTSP:/rtsp_get_new_scb: *Mar 11 03:14:23.471: //-1//RTSP:/rtsp_initialize_scb: *Mar 11 03:14:23.471: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5FE6C *Mar 11 03:14:23.471: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F0D4 context=0x6345042C *Mar 11 03:14:23.471: //-1//RTSP:/rtsp_get_new_scb: *Mar 11 03:14:23.471: //-1//RTSP:/rtsp_initialize_scb: *Mar 11 03:14:23.471: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5D874 *Mar 11 03:14:23.471: //-1//RTSP:/rtsp_api_create_session: evh=0x6155F204 context=0x6345046C *Mar 11 03:14:23.471: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A59FB8 *Mar 11 03:14:23.471: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A59FB8 *Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A59FB8 *Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5A304 *Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A5A304 *Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5A304 *Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5A650 *Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_handle_req_set_params: msg=0x63A5A650 *Mar 11 03:14:23.475: //166//RTSP:LP:RS45:/rtsp_api_handle_req_set_params: *Mar 11 03:14:23.475: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5A650 *Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_request: msg=0x63A5A99C *Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_handle_req_set_params: msg=0x63A5A99C *Mar 11 03:14:23.475: //166//RTSP:LP:RS46:/rtsp_api_handle_req_set_params: *Mar 11 03:14:23.475: //-1//RTSP:RS46:/rtsp_api_free_msg_buffer: msg=0x63A5A99C Router# Router#!call answered Router# Router#!digits dialed Router# Router#!call terminated Router# *Mar 11 03:14:51.603: //-1//RTSP:RS45:/rtsp_api_request: msg=0x63A5ACE8 *Mar 11 03:14:51.603: //-1//RTSP:RS46:/rtsp_api_request: msg=0x63A5B034 *Mar 11 03:14:51.607: //-1//RTSP:RS45:/rtsp_control_process_msg: *Mar 11 03:14:51.607: //166//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 0 *Mar 11 03:14:51.607: //166//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY *Mar 11 03:14:51.607: //166//RTSP:/rtsp_session_cleanup: *Mar 11 03:14:51.607: //-1//RTSP:/rtsplib_free_svr_session: *Mar 11 03:14:51.607: //-1//RTSP:/rtsplib_stop_timer: timer(0x638D5DDC) stops *Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: scb=0x63A5FE6C, callID=0xA6 *Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: No streams in session control block *Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5FE6C *Mar 11 03:14:51.611: //-1//RTSP:RS45:/rtsp_api_free_msg_buffer: msg=0x63A5ACE8 *Mar 11 03:14:51.611: //-1//RTSP:RS46:/rtsp_control_process_msg: *Mar 11 03:14:51.611: //166//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 0 *Mar 11 03:14:51.611: //166//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY *Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup: *Mar 11 03:14:51.611: //-1//RTSP:/rtsplib_free_svr_session: *Mar 11 03:14:51.611: //-1//RTSP:/rtsplib_stop_timer: timer(0x63A60110) stops *Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: scb=0x63A5D874, callID=0xA6 *Mar 11 03:14:51.611: //166//RTSP:/rtsp_create_session_history: No streams in session control block *Mar 11 03:14:51.611: //166//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5D874 *Mar 11 03:14:51.611: //-1//RTSP:RS46:/rtsp_api_free_msg_buffer: msg=0x63A5B034


DB-1928

May 2008



Related Commands

debug rtsp all Field Descriptions

Field

Description

//-1/

Indicates that the CallEntry ID for the module is unavailable.

//166/

Identifies the CallEntry ID.

RTSP:

Identifies the RTSP module.

rtsp_function name

Identifies the function name.

Command

Description

debug rtsp api

Displays debugging output for the RTSP client API.

debug rtsp error

Displays error message for RTSP data.

debug rtsp pmh

Displays debugging messages for the PMH.

debug rtsp socket

Displays debugging output for the RTSP client socket data.

voice call debug

Allows configuration of the voice call debugging output.


DB-1929

Debug Commands debug rtsp api

debug rtsp api To display information about the Real Time Streaming Protocol (RTSP) application programming interface (API) messages passed down to the RTSP client, use the debug rtsp api command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtsp api no debug rtsp api

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(11)T


12.2SX


Usage Guidelines

We recommend that you log output from the debug rtsp api command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following example shows output from the debug rtsp api command: Router# debug rtsp api RTSP client API debugging is on Router# !call initiated *Mar 11 03:04:41.699: context=0x6345088C *Mar 11 03:04:41.699: context=0x634508CC *Mar 11 03:04:41.699: *Mar 11 03:04:41.699: *Mar 11 03:04:41.699: *Mar 11 03:04:41.699:

//-1//RTSP:/rtsp_api_create_session: evh=0x6155F0D4 //-1//RTSP:/rtsp_api_create_session: evh=0x6155F204 //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A59FB8 //-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A59FB8 //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A59FB8 //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5A304


DB-1930

May 2008

Debug Commands debug rtsp api

*Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

11 11 11 11 11 11 11 11 11 11

03:04:41.699: 03:04:41.699: 03:04:41.703: 03:04:41.703: 03:04:41.703: 03:04:41.703: 03:04:41.703: 03:04:41.703: 03:04:41.703: 03:04:41.703:

//-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A5A304 //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5A304 //-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5A650 //-1//RTSP:RS35:/rtsp_api_handle_req_set_params: msg=0x63A5A650 //146//RTSP:LP:RS35:/rtsp_api_handle_req_set_params: //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5A650 //-1//RTSP:RS36:/rtsp_api_request: msg=0x63A5A99C //-1//RTSP:RS36:/rtsp_api_handle_req_set_params: msg=0x63A5A99C //146//RTSP:LP:RS36:/rtsp_api_handle_req_set_params: //-1//RTSP:RS36:/rtsp_api_free_msg_buffer: msg=0x63A5A99C

Router!call answered Router#!digits dialed Router#!call terminated *Mar *Mar *Mar *Mar

11 11 11 11

03:05:15.367: 03:05:15.367: 03:05:15.367: 03:05:15.367:

//-1//RTSP:RS35:/rtsp_api_request: msg=0x63A5ACE8 //-1//RTSP:RS36:/rtsp_api_request: msg=0x63A5B034 //-1//RTSP:RS35:/rtsp_api_free_msg_buffer: msg=0x63A5ACE8 //-1//RTSP:RS36:/rtsp_api_free_msg_buffer: msg=0x63A5B034


Related Commands

debug rtsp api Field Descriptions

Field

Description

//-1/


//146/


RTSP:


rtsp_function name


Command

Description

debug rtsp error


debug rtsp pmh


debug rtsp socket


voice call debug



DB-1931

Debug Commands debug rtsp client

debug rtsp client Note

Effective with Release 12.3(4), the debug rtsp cleint command is replaced by the debug rtsp session command. See the debug rtsp session command for more information. To display client information and stream information for the stream that is currently active for the Real Time Streaming Protocol (RTSP) client, use the debug rtsp client command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtsp client no debug rtsp client

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.3(4)T

This command was replaced by the debug rtsp session command.

12.2SX


Usage Guidelines

We recommend that you log output from the debug rtsp client command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Related Commands

Command

Description

debug rtsp api


debug rtsp error


debug rtsp pmh


debug rtsp socket


voice call debug



DB-1932

May 2008

Debug Commands debug rtsp client session

debug rtsp client session Note

Effective with Release 12.3(4), the debug rtsp cleint session command is replaced by the debug rtsp session command. See the debug rtsp session command for more information. To display debug messages about the Real Time Streaming Protocol (RTSP) client or the current session, use the debug rtsp command. To disable debugging output, use the no form of this command. debug rtsp [client | session] no debug rtsp [client | session]

Syntax Description

client

(Optional) Displays client information and stream information for the stream that is currently active.

session

(Optional) Displays cumulative information about the session, packet statistics, and general call information such as call ID, session ID, individual RTSP stream URLs, packet statistics, and play duration.

Defaults


Command History

Release

Modification

12.1(3)T


12.3(4)T

This command was replaced by the debug rtsp session command.

12.2SX


Examples

The following example displays the debug messages of the RTSP session: Router# debug rtsp session RTSP client session debugging is on router# Jan 1 00:08:36.099:rtsp_get_new_scb: Jan 1 00:08:36.099:rtsp_initialize_scb: Jan 1 00:08:36.099:rtsp_control_process_msg: Jan 1 00:08:36.099:rtsp_control_process_msg:received MSG request of TYPE 0 Jan 1 00:08:36.099:rtsp_set_event: Jan 1 00:08:36.099:rtsp_set_event:api_req_msg_type=RTSP_API_REQ_PLAY Jan 1 00:08:36.103:rtsp_set_event:url:[rtsp://rtsp-cisco.cisco.com:554/en_welcome.au] Jan 1 00:08:36.103:rtsp_process_async_event:SCB=0x62128F08 Jan 1 00:08:36.103:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_IDLE rtsp_event = RTSP_EV_PLAY_OR_REC Jan 1 00:08:36.103:act_idle_event_play_or_rec_req: Jan 1 00:08:36.103:rtsp_resolve_dns: Jan 1 00:08:36.103:rtsp_resolve_dns:IP Addr = 1.13.79.6:


DB-1933


Jan Jan Jan Jan Jan Jan Jan

1 1 1 1 1 1 1

Jan Jan Jan Jan Jan

1 1 1 1 1

00:08:36.103:rtsp_connect_to_svr: 00:08:36.103:rtsp_connect_to_svr:socket=0, connection_state = 2 00:08:36.103:rtsp_start_timer:timer (0x62128FD0)starts - delay (10000) 00:08:36.107:rtsp_control_main:SOCK= 0 Event=0x1 00:08:36.107:rtsp_stop_timer:timer(0x62128FD0) stops 00:08:36.107:rtsp_process_async_event:SCB=0x62128F08 00:08:36.107:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_IDLE rtsp_event = RTSP_EV_SVR_CONNECTED 00:08:36.107:act_idle_event_svr_connected: 00:08:36.107:rtsp_control_main:SOCK= 0 Event=0x1 00:08:36.783:rtsp_control_main:SOCK= 0 Event=0x1 00:08:36.783:rtsp_process_async_event:SCB=0x62128F08 00:08:36.783:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_READY rtsp_event = RTSP_EV_SVR_DESC_OR_ANNOUNCE_RESP 00:08:36.783:act_ready_event_desc_or_announce_resp:

Jan 1 Jan 1 00:08:36.783:act_ready_event_desc_or_announce_resp:RTSP_STATUS_DESC_OR_ANNOUNCE_RESP_OK Jan 1 00:08:37.287:rtsp_control_main:SOCK= 0 Event=0x1 Jan 1 00:08:37.287:rtsp_process_async_event:SCB=0x62128F08 Jan 1 00:08:37.287:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_READY rtsp_event = RTSP_EV_SVR_SETUP_RESP Jan 1 00:08:37.287:act_ready_event_setup_resp: Jan 1 00:08:37.287:act_ready_event_setup_resp:Remote RTP Port=13344 Jan 1 00:08:37.287:rtsp_rtp_stream_setup:scb=0x62128F08, callID=0x7 record=0 Jan 1 00:08:37.287:rtsp_rtp_stream_setup:Starting RTCP session. Local IP addr = 1.13.79.45, Remote IP addr = 1.13.79.6, Local RTP port = 18748, Remote RTP port = 13344 CallID=8 Jan 1 00:08:37.291:xmit_func = 0x0 vdbptr = 0x61A0FC98 Jan 1 00:08:37.291:rtsp_control_main:CCAPI Queue Event Jan 1 00:08:37.291:rtsp_rtp_associate_done:ev=0x62070E08, callID=0x7 Jan 1 00:08:37.291:rtsp_rtp_associate_done:scb=0x62128F08 Jan 1 00:08:37.291:rtsp_rtp_associate_done:callID=0x7, pVdb=0x61F4FBC8, Jan 1 00:08:37.291: spi_context=0x6214145C Jan 1 00:08:37.291: disposition=0, playFunc=0x60CA2238, Jan 1 00:08:37.291: codec=0x5, vad=0, mediaType=6, Jan 1 00:08:37.291: stream_assoc_id=1 Jan 1 00:08:37.291:rtsp_rtp_modify_session:scb=0x62128F08, callID=0x7 Jan 1 00:08:37.291:rtsp_process_async_event:SCB=0x62128F08 Jan 1 00:08:37.291:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_READY rtsp_event = RTSP_EV_ASSOCIATE_DONE Jan 1 00:08:37.291:act_ready_event_associate_done: Jan 1 00:08:37.291:rtsp_get_stream: Jan 1 00:08:37.783:rtsp_control_main:SOCK= 0 Event=0x1 Jan 1 00:08:37.783:rtsp_process_async_event:SCB=0x62128F08 Jan 1 00:08:37.783:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_READY rtsp_event = RTSP_EV_SVR_PLAY_OR_REC_RESP Jan 1 00:08:37.783:act_ready_event_play_or_rec_resp: Jan 1 00:08:37.783:rtsp_start_timer:timer (0x62128FB0)starts - delay (4249) rtsp-5# Jan 1 00:08:42.035:rtsp_process_timer_events: Jan 1 00:08:42.035:rtsp_process_timer_events:PLAY OR RECORD completed Jan 1 00:08:42.035:rtsp_process_async_event:SCB=0x62128F08 Jan 1 00:08:42.035:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_PLAY_OR_REC rtsp_event = RTSP_EV_PLAY_OR_REC_TIMER_EXPIRED Jan 1 00:08:42.035:act_play_event_play_done: Jan 1 00:08:42.035:act_play_event_play_done:elapsed play time = 4249 total play time = 4249 Jan 1 00:08:42.035:rtsp_send_teardown_to_svr: Jan 1 00:08:42.487:rtsp_control_main:SOCK= 0 Event=0x1 Jan 1 00:08:42.487:rtsp_process_async_event:SCB=0x62128F08 Jan 1 00:08:42.487:rtsp_process_async_event:rtsp_state = RTSP_SES_STATE_PLAY_OR_REC rtsp_event = RTSP_EV_SVR_TEARDOWN_RESP Jan 1 00:08:42.487:act_play_event_teardown_resp: Jan 1 00:08:42.487:rtsp_server_closed:


DB-1934

May 2008


Jan 1 00:08:42.487:rtsp_send_resp_to_api: Jan 1 00:08:42.487:rtsp_send_resp_to_api:sending RESP=RTSP_STATUS_PLAY_COMPLETE Jan 1 00:08:42.491:rtsp_rtp_teardown_stream:scb=0x62128F08, callID=0x7 Jan 1 00:08:42.491:rtsp_rtp_stream_cleanup:scb=0x62128F08, callID=0x7 Jan 1 00:08:42.491:rtsp_update_stream_stats:scb=0x62128F08, stream=0x61A43350, Jan 1 00:08:42.491:call_info=0x6214C67C, callID=0x7 Jan 1 00:08:42.491:rtsp_update_stream_stats:rx_bytes = 25992 Jan 1 00:08:42.491:rtsp_update_stream_stats:rx_packetes = 82 Jan 1 00:08:42.491:rtsp_reinitialize_scb: Jan 1 00:08:42.503:rtsp_control_process_msg: Jan 1 00:08:42.503:rtsp_control_process_msg:received MSG request of TYPE 0 Jan 1 00:08:42.503:rtsp_set_event: Jan 1 00:08:42.503:rtsp_set_event:api_req_msg_type=RTSP_API_REQ_DESTROY Jan 1 00:08:42.503:rtsp_session_cleanup: Jan 1 00:08:42.503:rtsp_create_session_history:scb=0x62128F08, callID=0x7 Jan 1 00:08:42.503:rtsp_insert_session_history_record:current=0x6214BDC8, callID=0x7 Jan 1 00:08:42.503:rtsp_insert_session_history_record:count = 3 Jan 1 00:08:42.503:rtsp_insert_session_history_record:starting history record deletion_timer of10 minutes Jan 1 00:08:42.503:rtsp_session_cleanup:deleting session:scb=0x62128F08 Router#

Related Commands

Command

Description

debug rtsp all


debug rtsp pmh


debug rtsp socket



DB-1935

Debug Commands debug rtsp error

debug rtsp error To display error information about the Real-Time Streaming Protocol (RTSP) client, use the debug rtsp error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtsp error no debug rtsp error

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(11)T


12.2SX


Usage Guidelines

We recommend that you log output from the debug rtsp error command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Related Commands

Command

Description

debug rtsp api


debug rtsp pmh


debug rtsp socket


voice call debug



DB-1936

May 2008

Debug Commands debug rtsp pmh

debug rtsp pmh To display debugging information about the Protocol Message Handler (PMH), use the debug rtsp pmh command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtsp pmh no debug rtsp pmh

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(11)T


12.2SX


Usage Guidelines

We recommend that you log output from the debug rtsp pmh command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Related Commands

Command

Description

debug rtsp api


debug rtsp error


debug rtsp socket


voice call debug



DB-1937

Debug Commands debug rtsp session

debug rtsp session To display client information and stream information for the stream that is currently active for the Real Time Streaming Protocol (RTSP) client, use the debug rtsp session command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtsp session no debug rtsp session

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(11)T


12.3(4)T

This command replaces the debug rtsp client command and the debug rtsp client session command.

12.2SX


Usage Guidelines

We recommend that you log output from the debug rtsp session command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following example shows the display of the debugging messages of the RTSP session: Router# debug rtsp session RTSP client session debugging is on Router# Router#!call initiated Router# *Mar 11 03:09:58.123: //-1//RTSP:/rtsp_get_new_scb: *Mar 11 03:09:58.123: //-1//RTSP:/rtsp_initialize_scb: *Mar 11 03:09:58.123: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5FE6C *Mar 11 03:09:58.123: //-1//RTSP:/rtsp_get_new_scb:


DB-1938

May 2008

Debug Commands debug rtsp session

*Mar 11 03:09:58.123: //-1//RTSP:/rtsp_initialize_scb: *Mar 11 03:09:58.123: //-1//RTSP:/rtsplib_init_svr_session: 0x63A5D874 Router# Router#!call answered Router# Router#!digits dialed Router# Router#!call terminated Router# *Mar 11 03:10:38.139: //-1//RTSP:RS41:/rtsp_control_process_msg: *Mar 11 03:10:38.139: //158//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 0 *Mar 11 03:10:38.139: //158//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY *Mar 11 03:10:38.139: //158//RTSP:/rtsp_session_cleanup: *Mar 11 03:10:38.139: //-1//RTSP:/rtsplib_free_svr_session: *Mar 11 03:10:38.139: //-1//RTSP:/rtsplib_stop_timer: timer(0x638D5DDC) stops *Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: scb=0x63A5FE6C, callID=0x9E *Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: No streams in session control block *Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5FE6C *Mar 11 03:10:38.143: //-1//RTSP:RS42:/rtsp_control_process_msg: *Mar 11 03:10:38.143: //158//RTSP:/rtsp_control_process_msg: received MSG request of TYPE 0 *Mar 11 03:10:38.143: //158//RTSP:/rtsp_set_event: api_req_msg_type=RTSP_API_REQ_DESTROY *Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup: *Mar 11 03:10:38.143: //-1//RTSP:/rtsplib_free_svr_session: *Mar 11 03:10:38.143: //-1//RTSP:/rtsplib_stop_timer: timer(0x63A60110) stops *Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: scb=0x63A5D874, callID=0x9E *Mar 11 03:10:38.143: //158//RTSP:/rtsp_create_session_history: No streams in session control block *Mar 11 03:10:38.143: //158//RTSP:/rtsp_session_cleanup: deleting session: scb=0x63A5D874


Related Commands

debug rtsp session Field Descriptions

Field

Description

//-1/


//158/


RTSP:


rtsp_function name


Command

Description

debug rtsp api


debug rtsp error


debug rtsp pmh


debug rtsp socket


voice call debug



DB-1939

Debug Commands debug rtsp socket

debug rtsp socket To display debugging messages about the packets received or sent on the TCP or User Datagram Protocol (UDP) sockets, use the debug rtsp socket command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtsp socket no debug rtsp socket

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(11)T


12.2SX


Usage Guidelines

Note

Related Commands

Each Real-Time Streaming Protocol (RTSP) session has a TCP port for control and a UDP (RTP) port for delivery of data. The control connection (TCP socket) is used to exchange a set of messages (request from the RTSP client and the response from the server) for displaying a prompt. The debug rtsp socket command enables the user to debug the message exchanges being done on the TCP control connection.

We recommend that you log output from the debug rtsp socket command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Command

Description

debug rtsp api


debug rtsp error


debug rtsp pmh


voice call debug



DB-1940

May 2008

Debug Commands debug rtsp

debug rtsp To show the status of the Real-Time Streaming Protocol (RTSP) client or server, use the debug rtsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rtsp type [all | api | error | pmh | session | socket] [no] debug rtsp type [all | api | pmh | session | socket]

Syntax Description

type

Type of debug messages to display. The keywords are as follows: •

all—(Optional) Displays debug output for all clients or servers.

•

api—(Optional) Displays debug output for the client or server API.

•

error—(Optional) Displays errors when they are errors otherwise no output is displayed.

•

pmh—(Optional) Displays debug output for the Protocol Message Handler (PMH).

•

session—(Optional) Displays debug output for the client or server session.

•

socket—(Optional) Displays debug output for the client or server socket data.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660 series; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.

12.2SX


Examples

The following is sample output that displays when the debug rtsp command is entered with the api keyword: Router# debug rtsp api


DB-1941

Debug Commands debug rtsp

! RTSP client API debugging is on ! Jan 1 00:23:15.775:rtsp_api_create_session:sess_id=0x61A07C78,evh=0x60D6E62C context=0x61A07B28 Jan 1 00:23:15.775:rtsp_api_request:msg=0x61C2B10C Jan 1 00:23:15.775:rtsp_api_handle_req_set_params:msg=0x61C2B10C Jan 1 00:23:15.775:rtsp_api_free_msg_buffer:msg=0x61C2B10C Jan 1 00:23:15.775:rtsp_api_request:msg=0x61C293CC Jan 1 00:23:15.775:rtsp_api_handle_req_set_params:msg=0x61C293CC Jan 1 00:23:15.775:rtsp_api_free_msg_buffer:msg=0x61C293CC Jan 1 00:23:15.775:rtsp_api_request:msg=0x61C2970C Jan 1 00:23:15.775:rtsp_api_handle_req_set_params:msg=0x61C2970C Jan 1 00:23:15.775:rtsp_api_free_msg_buffer:msg=0x61C2970C ! Jan 1 00:23:15.775:rtsp_api_request:msg=0x61C29A4C ! Jan 1 00:23:22.099:rtsp_api_free_msg_buffer:msg=0x61C29A4C Jan 1 00:23:22.115:rtsp_api_request:msg=0x61C2A40C Jan 1 00:23:22.115:rtsp_api_free_msg_buffer:msg=0x61C2A40C

Related Commands

Command

Description

debug rtsp api

Displays debug output for the RTSP client API.

debug rtsp client session

Displays debug output for the RTSP client data.

debug rtsp socket

Displays debug output for the RTSP client socket data.


DB-1942

May 2008

Debug Commands debug rudpv1

debug rudpv1 For debug information for Reliable User Datagram Protocol (RUDP), use the debug rudpv1 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug rudpv1 {application | performance | retransmit | segment | signal | state | timer | transfer} no debug rudpv1{application | performance | retransmit | segment | signal | state | timer | transfer}

Syntax Description

application

Application debugging.

performance

Performance debugging.

retransmit

Retransmit/soft reset debugging.

segment

Segment debugging.

signal

Signals sent to applications.

state

State transitions.

timer

Timer debugging.

transfer

Transfer state information.

Defaults

Debugging for rudpv1 is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T


12.2(4)T


12.2(2)XB

This command was implemented on the Cisco AS5350 and Cisco AS5400 universal gateways.

Usage Guidelines

12.2(2)XB1


12.2(8)T

This command was implemented on Cisco IAD2420 series integrated access devices (IADs).

12.2(11)T

This command was implemented on the Cisco AS5350, Cisco AS5400, and Cisco AS5850 platforms.

12.2(33)SRA


12.2SX


Use this command only during times of low traffic.


DB-1943


Examples

The following is sample output from the debug rudpv1 application command: Router# debug rudpv1 application Rudpv1:Turning application debugging on *Jan 1 00:20:38.271:Send to appl (61F72B6C), *Jan 1 00:20:48.271:Send to appl (61F72B6C), *Jan 1 00:20:58.271:Send to appl (61F72B6C), *Jan 1 00:21:08.271:Send to appl (61F72B6C), *Jan 1 00:21:18.271:Send to appl (61F72B6C), *Jan 1 00:21:28.271:Send to appl (61F72B6C), *Jan 1 00:21:38.271:Send to appl (61F72B6C), *Jan 1 00:21:48.275:Send to appl (61F72B6C), *Jan 1 00:21:58.275:Send to appl (61F72B6C), *Jan 1 00:22:08.275:Send to appl (61F72B6C), *Jan 1 00:22:18.275:Send to appl (61F72B6C), *Jan 1 00:22:28.275:Send to appl (61F72B6C), *Jan 1 00:22:38.275:Send to appl (61F72B6C), *Jan 1 00:22:48.279:Send to appl (61F72B6C), *Jan 1 00:22:58.279:Send to appl (61F72B6C), *Jan 1 00:23:08.279:Send to appl (61F72B6C), *Jan 1 00:23:18.279:Send to appl (61F72B6C), *Jan 1 00:23:28.279:Send to appl (61F72B6C),

seq seq seq seq seq seq seq seq seq seq seq seq seq seq seq seq seq seq

12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

The following is sample output from the debug rudpv1 performance command: Router# debug rudpv1 performance Rudpv1:Turning performance debugging on corsair-f# *Jan 1 00:44:27.299: *Jan 1 00:44:27.299:Rudpv1 Sent:Pkts 11, Data Bytes 236, *Jan 1 00:44:27.299:Rudpv1 Rcvd:Pkts 10, Data Bytes 237, *Jan 1 00:44:27.299:Rudpv1 Discarded:0, Retransmitted 0 *Jan 1 00:44:27.299: *Jan 1 00:44:37.299: *Jan 1 00:44:37.299:Rudpv1 Sent:Pkts 11, Data Bytes 236, *Jan 1 00:44:37.299:Rudpv1 Rcvd:Pkts 10, Data Bytes 237, *Jan 1 00:44:37.299:Rudpv1 Discarded:0, Retransmitted 0 *Jan 1 00:44:37.299: *Jan 1 00:44:47.299: *Jan 1 00:44:47.299:Rudpv1 Sent:Pkts 11, Data Bytes 236, *Jan 1 00:44:47.299:Rudpv1 Rcvd:Pkts 11, Data Bytes 236, *Jan 1 00:44:47.299:Rudpv1 Discarded:0, Retransmitted 0 *Jan 1 00:44:47.299:

Data Pkts 9 Data Pkts 9



The following is sample output from the debug rudpv1 retransmit command: Router# debug rudpv1 retransmit Rudpv1:Turning retransmit/softreset debugging on *Jan 1 00:52:59.799:Retrans timer, set to ack 199 *Jan 1 00:52:59.903:Retrans timer, set to ack 200 *Jan 1 00:53:00.003:Retrans timer, set to ack 201 *Jan 1 00:53:00.103:Retrans timer, set to ack 202 *Jan 1 00:53:00.203:Retrans timer, set to ack 203 *Jan 1 00:53:00.419:Retrans timer, set to ack 97 *Jan 1 00:53:00.503:Retrans handler fired, 203 *Jan 1 00:53:00.503:Retrans:203:205: *Jan 1 00:53:00.503: *Jan 1 00:53:00.607:Retrans timer, set to ack 207 *Jan 1 00:53:00.907:Retrans timer, set to ack 210 *Jan 1 00:53:01.207:Retrans handler fired, 210 *Jan 1 00:53:01.207:Retrans:210:211:212:


DB-1944

May 2008


*Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan

1 1 1 1 1 1 1 1 1 1 1 1 1 1

00:53:01.207: 00:53:01.207:Retrans timer, set to ack 213 00:53:01.311:Retrans timer, set to ack 214 00:53:01.419:Retrans timer, set to ack 98 00:53:01.611:Retrans timer, set to ack 215 00:53:01.711:Retrans timer, set to ack 218 00:53:01.811:Retrans timer, set to ack 219 00:53:01.911:Retrans timer, set to ack 220 00:53:02.011:Retrans timer, set to ack 221 00:53:02.311:Retrans handler fired, 221 00:53:02.311:Retrans:221: 00:53:02.311: 00:53:02.311:Retrans timer, set to ack 222 00:53:02.415:Retrans timer, set to ack 225

The following is sample output from the debug rudpv1 segment command: Router# debug rudpv1 segment Rudpv1:Turning segment debugging on *Jan 1 00:41:36.359:Rudpv1: (61F72DAC) *Jan 1 00:41:36.359:Rudpv1: (61F72DAC) *Jan 1 00:41:36.459:Rudpv1: (61F72DAC) *Jan 1 00:41:36.459:Rudpv1: (61F72DAC) *Jan 1 00:41:36.459:Rudpv1: (61F72DAC) *Jan 1 00:41:36.559:Rudpv1: (61F72DAC) *Jan 1 00:41:36.559:Rudpv1: (61F72DAC) *Jan 1 00:41:36.659:Rudpv1: (61F72DAC) *Jan 1 00:41:36.659:Rudpv1: (61F72DAC) *Jan 1 00:41:36.759:Rudpv1: (61F72DAC) *Jan 1 00:41:36.759:Rudpv1: (61F72DAC) *Jan 1 00:41:36.859:Rudpv1: (61F72DAC) *Jan 1 00:41:36.859:Rudpv1: (61F72DAC) *Jan 1 00:41:36.959:Rudpv1: (61F72DAC) *Jan 1 00:41:36.959:Rudpv1: (61F72DAC) *Jan 1 00:41:36.959:Rudpv1: (61F72DAC) *Jan 1 00:41:36.963:Rudpv1: (61F72DAC) *Jan 1 00:41:36.963:Rudpv1: (61F72DAC) *Jan 1 00:41:37.051:Rudpv1: (61F72B6C) *Jan 1 00:41:37.051:Rudpv1: (61F72B6C) *Jan 1 00:41:37.059:Rudpv1: (61F72DAC) *Jan 1 00:41:37.063:Rudpv1: (61F72DAC) *Jan 1 00:41:37.263:Rudpv1: (61F72DAC) *Jan 1 00:41:37.363:Rudpv1: (61F72DAC) *Jan 1 00:41:37.363:Rudpv1: (61F72DAC) *Jan 1 00:41:37.363:Rudpv1: (61F72DAC) *Jan 1 00:41:37.363:Rudpv1: (61F72DAC) *Jan 1 00:41:37.363:Rudpv1: (61F72DAC) *Jan 1 00:41:37.363:Rudpv1: (61F72DAC) *Jan 1 00:41:37.363:Rudpv1: (61F72DAC) *Jan 1 00:41:37.367:Rudpv1: (61F72DAC) *Jan 1 00:41:37.463:Rudpv1: (61F72DAC) *Jan 1 00:41:37.463:Rudpv1: (61F72DAC) *Jan 1 00:41:37.563:Rudpv1: (61F72DAC) *Jan 1 00:41:37.563:Rudpv1: (61F72DAC)

Rcvd Send Rcvd Rcvd Send Rcvd Send Rcvd Send Rcvd Send Rcvd Send Rcvd Rcvd Send Send Rcvd Send Rcvd Rcvd Send Rcvd Send Rcvd Rcvd Send Send Send Send Rcvd Rcvd Send Rcvd Send

ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK ACK

61..198 (32) 199..61 (32) 62..199 (8) 62..199 (32) 200..62 (32) 63..200 (32) 201..63 (32) 64..201 (32) 202..64 (32) 65..202 (32) 203..65 (32) 66..202 (32) 204..66 (32) 67..202 (32) EAK 68..202 (9) 203..67 (32) 205..67 (32) 68..204 (8) NUL 118..96 (8) 97..118 (8) 68..205 (32) 206..68 (32) 70..206 (32) EAK 207..68 (9) 71..206 (32) 69..206 (32) 207..71 (8) 207..71 (32) 208..71 (32) 209..71 (32) 72..209 (8) 72..209 (32) 210..72 (32) 73..210 (32) 211..73 (32)


DB-1945


The following is sample output from the debug rudpv1 signal command: Router# debug rudpv1 signal Rudpv1:Turning signal debugging on *Jan 1 00:39:59.551:Rudpv1:Sent CONN_FAILED to connID 61F72DAC, sess 33 *Jan 1 00:39:59.551: *Jan 1 00:39:59.551:Rudpv1:Sent CONN_TRANS_STATE to connID 61F72B6C, sess 34 *Jan 1 00:39:59.551: *Jan 1 00:39:59.551:Rudpv1:Sent CONN_TRANS_STATE to connID 61F72DAC, sess 33 *Jan 1 00:39:59.551: *Jan 1 00:39:59.551:Rudpv1:Sent CONN_OPEN to connID 61F72B6C, sess 34 *Jan 1 00:39:59.551:Rudpv1:Sent AUTO_RESET to connID 61F72DAC, sess 33 *Jan 1 00:39:59.551: *Jan 1 00:40:00.739:%LINK-5-CHANGED:Interface FastEthernet0, changed state to administratively down *Jan 1 00:40:01.739:%LINEPROTO-5-UPDOWN:Line protocol on Interface FastEthernet0, changed state to down *Jan 1 00:40:04.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33 *Jan 1 00:40:04.551: *Jan 1 00:40:05.051:Rudpv1:Clearing conn rec values, index 2, connid 61F72DAC *Jan 1 00:40:10.051:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33 *Jan 1 00:40:10.051: *Jan 1 00:40:10.551:Rudpv1:Clearing conn rec values, index 2, connid 61F72DAC *Jan 1 00:40:15.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33 *Jan 1 00:40:15.551: *Jan 1 00:40:16.051:Rudpv1:Clearing conn rec values, index 2, connid 61F72DAC *Jan 1 00:40:21.051:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33 *Jan 1 00:40:21.051: *Jan 1 00:40:21.551:Rudpv1:Clearing conn rec values, index 2, connid 61F72DAC *Jan 1 00:40:25.587:%LINK-3-UPDOWN:Interface FastEthernet0, changed state to up *Jan 1 00:40:26.551:Rudpv1:Sent CONN_RESET to connID 61F72DAC, sess 33 *Jan 1 00:40:26.551: *Jan 1 00:40:26.587:%LINEPROTO-5-UPDOWN:Line protocol on Interface FastEthernet0, changed state to up *Jan 1 00:40:27.051:Rudpv1:Clearing conn rec values, index 2, connid 61F72DAC *Jan 1 00:40:28.051:Rudpv1:Sent CONN_OPEN to connID 61F72DAC, sess 33

The following is sample output from the debug rudpv1 state command: Router# debug rudpv1 state Rudpv1:Turning state debugging on *Jan 1 00:38:37.323:Rudpv1: (61F72DAC) State Change:OPEN -> CONN_FAILURE *Jan 1 00:38:37.323:Rudpv1: (61F72B6C) State Change:OPEN -> TRANS_STATE *Jan 1 00:38:37.323:Rudpv1: (61F72DAC) State Change:CONN_FAILURE -> TRANS_STATE *Jan 1 00:38:37.323:Rudpv1: (61F72B6C) State Change:TRANS_STATE -> OPEN *Jan 1 00:38:37.323:Rudpv1: (61F72DAC) State Change:TRANS_STATE -> SYN_SENT *Jan 1 00:38:37.455:%LINK-5-CHANGED:Interface FastEthernet0, changed state to administratively down *Jan 1 00:38:38.451:%LINEPROTO-5-UPDOWN:Line protocol on Interface FastEthernet0, changed state to down *Jan 1 00:38:42.323:Rudpv1: (61F72DAC) State Change:SYN_SENT -> CLOSED *Jan 1 00:38:42.823:Rudpv1: (61F72DAC) State Change:INACTIVE -> SYN_SENT


DB-1946

May 2008


*Jan 1 00:38:47.823:Rudpv1: (61F72DAC) State *Jan 1 00:38:48.323:Rudpv1: (61F72DAC) State *Jan 1 00:38:53.323:Rudpv1: (61F72DAC) State *Jan 1 00:38:53.823:Rudpv1: (61F72DAC) State *Jan 1 00:38:56.411:%LINK-3-UPDOWN:Interface to up *Jan 1 00:38:57.411:%LINEPROTO-5-UPDOWN:Line FastEthernet0, changed state to up *Jan 1 00:38:57.823:Rudpv1: (61F72DAC) State

Change:SYN_SENT -> CLOSED Change:INACTIVE -> SYN_SENT Change:SYN_SENT -> CLOSED Change:INACTIVE -> SYN_SENT FastEthernet0, changed state protocol on Interface Change:SYN_SENT -> OPEN

The following is sample output from the debug rudpv1 timer command: Router# debug rudpv1 timer Rudpv1:Turning timer debugging on *Jan 1 00:53:40.647:Starting Retrans timer for connP = 61F72B6C, delay = 300 *Jan 1 00:53:40.647:Stopping SentList timer for connP = 61F72B6C *Jan 1 00:53:40.747:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:40.747:Stopping Retrans timer for connP = 61F72B6C *Jan 1 00:53:40.747:Starting Retrans timer for connP = 61F72B6C, delay = 300 *Jan 1 00:53:40.747:Stopping SentList timer for connP = 61F72B6C *Jan 1 00:53:40.847:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:40.847:Stopping Retrans timer for connP = 61F72B6C *Jan 1 00:53:40.847:Starting Retrans timer for connP = 61F72B6C, delay = 300 *Jan 1 00:53:40.847:Stopping SentList timer for connP = 61F72B6C *Jan 1 00:53:40.947:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:40.947:Stopping Retrans timer for connP = 61F72B6C *Jan 1 00:53:40.947:Starting Retrans timer for connP = 61F72B6C, delay = 300 *Jan 1 00:53:40.947:Stopping SentList timer for connP = 61F72B6C *Jan 1 00:53:41.047:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:41.147:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:41.151:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:41.151:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:41.151:Stopping Retrans timer for connP = 61F72B6C *Jan 1 00:53:41.151:Starting SentList timer for connP = 61F72B6C, delay = 300 *Jan 1 00:53:41.419:Timer Keepalive (NullSeg) triggered for conn = 61F72DAC *Jan 1 00:53:41.419:Starting Retrans timer for connP = 61F72DAC, delay = 300 *Jan 1 00:53:41.419:Stopping SentList timer for connP = 61F72DAC *Jan 1 00:53:41.419:Starting NullSeg timer for connP = 61F72DAC, delay = 1000 *Jan 1 00:53:41.419:Stopping Retrans timer for connP = 61F72DAC *Jan 1 00:53:41.451:Timer SentList triggered for conn = 61F72B6C *Jan 1 00:53:41.451:Starting SentList timer for connP = 61F72B6C, delay = 300 *Jan 1 00:53:41.451:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:41.451:Stopping SentList timer for connP = 61F72B6C *Jan 1 00:53:41.551:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:41.551:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:41.551:Starting NullSeg timer for connP = 61F72B6C, delay = 1000 *Jan 1 00:53:41.551:Starting NullSeg timer for connP = 61F72B6C, delay = 1000

The following is sample output from the debug rudpv1 transfer command: Router# debug rudpv1 transfer Rudpv1:Turning transfer debugging on *Jan 1 00:37:30.567:Rudpv1:Send TCS, connId 61F72B6C, old connId 61F72DAC *Jan 1 00:37:30.567:Rudpv1:Initiate transfer state, old conn 61F72DAC to new conn 61F72B6C *Jan 1 00:37:30.567:Rudpv1:Old conn send window 51 .. 52 *Jan 1 00:37:30.567:Rudpv1:New conn send window 255 .. 2 *Jan 1 00:37:30.567:Rudpv1:Rcvd TCS 142, next seq 142 *Jan 1 00:37:30.567:Rudpv1:Rcv'ing trans state, old conn 61F72DAC to new conn 61F72B6C *Jan 1 00:37:30.567:Rudpv1:Seq adjust factor 148 *Jan 1 00:37:30.567:Rudpv1:New rcvCur 142


DB-1947


*Jan 1 00:37:30.567:Rudpv1:Send transfer state, old conn 61F72DAC to new conn 61F72B6C *Jan 1 00:37:30.567:Rudpv1:Send TCS, connId 61F72B6C, old connId 61F72DAC, seq adjust 208, indication 0 *Jan 1 00:37:30.567:Rudpv1:Transfer seg 51 to seg 3 on new conn *Jan 1 00:37:30.567:Rudpv1:Finishing transfer state, old conn 61F72DAC to new conn 61F72B6C *Jan 1 00:37:30.567:Rudpv1:Send window 2 .. 4

Related Commands

Command

Description

clear rudpv1 statistics

Clears RUDP statistics and failure counters.

show rudpv1

Displays RUDP failures, parameters, and statistics.


DB-1948

May 2008

Debug Commands debug saa apm

debug saa apm Note

Effective with Cisco IOS Release 12.3(14)T, the debug saa apm command is replaced by the debug ip sla monitor apm command. See the debug ip sla monitor apm command for more information. To enable debugging output for Cisco IOS IP Service Level Agreements (SLAs) Application Performance Monitor (APM) operations, use the debug saa apm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug saa apm no debug saa apm

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)T


12.3(14)T

This command was replaced by the debug ip sla monitor apm command.

12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug saa apm command: Router# debug saa apm Router# configure terminal Router(config)# saa apm operation 123 start ftp://apm/config/iptv.cf 21:40:27: 21:40:29: 21:40:30: 21:40:32: 21:40:32: 21:40:32: 21:40:32: 21:40:32: 21:40:32: 21:40:32: 21:40:32: 21:40:37: 21:40:37: 21:40:37: 21:40:38: 21:40:38: 21:40:38:

SAA-APM-123: downloading file (apm/config/iptv.cf) of size (534) SAA-APM-123: downloading file (apm/scheduler/master.sch) of size (2500) SAA-APM-123: downloading file (apm/scripts/iptv.scr) of size (1647) SAA-APM-123: downloading file (apm/data/iptv.dat) of size (118) SAA-APM-123: sending APM_CAPABILITIES_REQUEST message sending control msg: Ver: 1 ID: 29 Len: 48 SAA-APM-123: apm_engine version: major, minor SAA-APM-123: sending APM_SCRIPT_DNLD message sending control msg: Ver: 1 ID: 30 Len: 148 SAA-APM-123: sending APM_SCRIPT_DNLD_STATUS message sending control msg: Ver: 1 ID: 31 Len: 148 SAA-APM-123: starting the operation SAA-APM-123: sending APM_SCRIPT_START message sending control msg:


DB-1949

Debug Commands debug saa apm

21:40:38: 21:40:41: . . . 21:49:42: 21:55:13: 21:55:13: 21:55:13: 21:55:13:

Ver: 1 ID: 32 Len: 148 SAA-APM: 0,2144,0

SAA-APM-123: waiting for ageout timer to expire SAA-APM-123: sending APM_SCRIPT_DONE message sending control msg: Ver: 1 ID: 42 Len: 148 SAA-APM-123: operation done

Router(config)# no saa apm 21:55:13: 21:55:13: 21:55:13: 21:55:13:

SAA-APM-123: sending APM_SCRIPT_DONE message sending control msg: Ver: 1 ID: 42 Len: 148 SAA-APM-123: operation done


DB-1950

May 2008

Debug Commands debug saa slm

debug saa slm Note

Effective with Cisco IOS Release 12.3(14)T, the debug saa slm command is replaced by the debug ip sla monitor slm command. See the debug ip sla monitor slm command for more information. To enable debugging output of detailed event messages for Cisco IOS IP Service Level Agreements (SLAs) Service Level Monitoring (SLM) Asynchronous Transfer Mode (ATM) operations, use the debug saa slm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug saa slm no debug saa slm

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.3(14)T

This command was replaced by the debug ip sla monitor slm command.

12.2(33)SRA


12.2SX


Usage Guidelines

Note

Examples

IP SLAs SLM ATM performance statistics cannot be retrieved from Cisco IOS devices using Simple Network Management Protocol (SNMP). The IP SLAs SLM ATM feature was designed to provide data by responding to extensible markup language (XML) requests.

This command may generate a large number of debugging messages.

In the following example, debugging is enabled for the IP SLAs SLM ATM feature and the IP SLAs XML feature for the purposes of debugging the XML requests and responses: debug saa slm debug saa xml


DB-1951

Debug Commands debug saa slm

Related Commands

Command

Description

debug saa xml

Enables debugging output of XML requests and responses for IP SLAs operations.


DB-1952

May 2008

Debug Commands debug saa xml

debug saa xml Note

Effective with Cisco IOS Release 12.3(14)T, the debug saa xml command is replaced by the debug ip sla monitor xml command. See the debug ip sla monitor xml command for more information. To enable debugging output of eXtensible Markup Language (XML) requests and responses for Cisco IOS IP Service Level Agreements (SLAs) operations, use the debug saa xml command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug saa xml no debug saa xml

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.3(14)T

This command was replaced by the debug ip sla monitor xml command.

12.2(33)SRA


12.2SX


Examples

In the following example, debugging is enabled for the IP SLAs SLM ATM feature and the IP SLAs eXtensible Markup Language (XML) feature for the purposes of debugging the XML requests and responses: debug saa slm debug saa xml

Related Commands

Command

Description

debug saa slm

Enables debugging output of detailed event messages for IP SLAs SLM ATM operations.


DB-1953

Debug Commands debug sampler

debug sampler To enable debugging output for Flexible NetFlow samplers, use the debug sampler command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sampler [[name] sampler-name [detailed] [error] | [name] sampler-name sampling samples] no debug sampler [[name] sampler-name [detailed] [error] | [name] sampler-name sampling samples]

Syntax Description

name sampler-name

(Optional) The name of a sampler that you previously configured.

sampling

(Optional) Enables debugging for sampling.

samples

(Optional) Number of Samples to debug.

detailed

(Optional) Enables detailed debugging for sampler elements.

error

(Optional) Enables debugging for sampler errors.

Command Default

Debugging output for Flexible NetFlow samplers is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(9)T


12.2(31)SB2


12.2SX


Usage Guidelines

You must have already enabled traffic monitoring with Flexible NetFlow using a sampler before you can use the debug sampler command.

Examples

The following output shows that the debug process obtained the ID for the sampler named SAMPLER-1:

Router# debug sampler detailed *Oct 28 04:14:30.883: Sampler: Sampler(SAMPLER-1: flow monitor NFC-DC-PHOENIX (ip,Et1/0,O) get ID succeeded:1 *Oct 28 04:14:30.971: Sampler: Sampler(SAMPLER-1: flow monitor NFC-DC-PHOENIX (ip,Et0/0,I) get ID succeeded:1


DB-1954

May 2008

Debug Commands debug sampler

Related Commands

Command

Description

clear sampler

Clears the Flexible NetFlow sampler statistics.

debug sampler

Enables debugging output for Flexible NetFlow samplers.

mode

Configures a packet interval for a Flexible NetFlow sampler.

sampler

Creates a Flexible NetFlow Sampler

show sampler

Displays Flexible NetFlow sampler status and statistics.


DB-1955

Debug Commands debug satellite firmware

debug satellite firmware To enable debugging output for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) firmware, use the debug satellite firmware command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug satellite firmware {all | level number | option} no debug satellite firmware

Syntax Description

all

Displays all satellite firmware events.

level number

Satellite debug level. The debug level affects what information is displayed for subsequently entered debug satellite firmware commands. See Table 301.

option

One of the following options. See Table 301. •

bb—Satellite backbone events

•

buf—Satellite buffer events

•

en—Satellite firmware encryption events

•

ip—Satellite IP events

•

rbcp—Satellite RBCP events

•

rpa—Satellite Remote Page Acceleration (RPA) events

•

sat—Satellite inbound and outbound packet statistics

•

tcp—Satellite TCP events

•

trc—Satellite backbone traces

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Usage Guidelines

The output from this command is generally useful for diagnostic tasks performed by technical support. The level number affects which debug messages the system displays for subsequently entered debug satellite firmware commands. Table 301 describes what each command option displays at each debug level.


DB-1956

May 2008


Note

Table 301

Level 3 debugging produces significant amounts of output that may negatively impact the performance of both the NM-1VSAT-GILAT network module and the router. When you enter debug level 3, a warning message and confirmation prompt appear.

debug satellite firmware Command Level Options

Option

Level 1 Output

Level 2 Output

Level 3 Output

bb

Backbone link information

Frame statistics for the backbone link to the hub

—

buf

Buffer information

Buffer owners

—

en

Satellite firmware-based encryption events

—

—

ip

IP statistics

—

Driver transmission statistics

rbcp

Number of transmitted and received RBCP messages

—

Satellite Control Protocol (SCP) message summaries

rpa

RPA statistics

Tunnel connect and disconnect events

—

tcp

TCP statistics

TCP connection information

TCP statistics and TCP connection information

sat

Inbound and outbound packet statistics



trc

—

—

Backbone receive and transmit traces

Examples

This section provides the following sample output for the debug satellite firmware command: •

Sample Output for the debug satellite firmware all Command, page 1958

•

Sample Output for the bb Option at Level 1, page 1958

•

Sample Output for the bb Option at Level 2, page 1959

•

Sample Output for the buf Option at Level 1, page 1959

•

Sample Output for the buf Option at Level 2, page 1959

•

Sample Output for the ip Option at Level 1, page 1960

•

Sample Output for the rbcp Option at Level 1, page 1960

•

Sample Output for the rpa Option at Level 1, page 1960

•

Sample Output for the rpa Option at Level 2, page 1960

•

Sample Output for the sat Option at All Levels, page 1961

•

Sample Output for the tcp Option at Level 1, page 1961

•


•


•

Sample Output for the trc Option at Level 3, page 1962


DB-1957


Sample Output for the debug satellite firmware all Command

The following example shows all satellite firmware events and statistics: Router# debug satellite firmware all 2d06h: Satellite2/0 buffers 4856 min 4486 list_str 683798 list_end 6885c8 emp 686030 fil 685de0 start 6885c8 end fb4fe8 2d06h: Satellite2/0 TCP stats: NetRXBytes=223 NetTXBytes=4775126 NetRxPkts=104213 ToIOSPkts=104166 2d06h: Satellite2/0 SAT stats: OUTbound_pkts=114131, INbound_pkts=182347 2d06h: Satellite2/0 RBCP statistics: TXcount=975 RXCount=975 2d06h: Satellite2/0 RPA stats: ToTunnel=0 FromTunnel=0 TunnelGets=0 TunnelNotGets=0 BlksUsed=0 BlksIn-Use=0 Max=300 2d06h: Satellite2/0 EN: RX encrypted bytes received = 0 RX: compressed=0 -> Uncompressed=0 TX: compressed=0 -> Uncompressed=0 2d06h: Satellite2/0 BB 6 LINK state=INFO_STATE Status = 0x79, LOW NOT READY, HI PRI READY RSP Q free=230, Max HI=228, Max LOW=224, Max DG=232 IN RA mode Curr DG BW=50000, HighDG BW=100000, Curr BW=98094 MaxDG BW=1250000, Max BW=2500000 PD Queue lengths: q_wtog=0, q_wtos=57, q_wtos_high=0, q_defrag=d DG Queue lengths: q_dg_wtos=0, q_dg_wtos_hi=0, q_dg_defrag=0 Congestion Levels: TX LOCAL = 7, TX NET = 0 2d06h: Satellite2/0 IP stats: ToIOS_Pkts=234193, ToIOS_Bytes=183444492 FromIOS_Pkts=143 From_IOS_Bytes=12204 2d06h: Satellite2/0 NO Trace at levels 1 or 2 2d06h: Satellite2/0 NO Trace at levels 1 or 2

Sample Output for the bb Option at Level 1

The following example shows backbone link information: Router# debug satellite firmware level 1 Router# debug satellite firmware bb satellite BackBone events debugging is on Router# 2d06h: Satellite2/0 BB 6 LINK state=INFO_STATE Status = 0x79, LOW NOT READY, HI PRI READY RSP Q free=240, Max HI=228, Max LOW=224, Max DG=232 IN RA mode Curr DG BW=50000, HighDG BW=100000, Curr BW=96188


DB-1958

May 2008


MaxDG BW=1250000, Max BW=2500000 PD Queue lengths: q_wtog=0, q_wtos=95, q_wtos_high=0, q_defrag=d DG Queue lengths: q_dg_wtos=0, q_dg_wtos_hi=0, q_dg_defrag=0 Congestion Levels: TX LOCAL = 7, TX NET = 0 2d06h: Satellite2/0 BB 6 LINK state=INFO_STATE Status = 0x7b, LOW READY, HI PRI READY RSP Q free=27, Max HI=228, Max LOW=224, Max DG=232 IN RA mode Curr DG BW=50000, HighDG BW=100000, Curr BW=92376 MaxDG BW=1250000, Max BW=2500000 PD Queue lengths: q_wtog=0, q_wtos=24, q_wtos_high=0, q_defrag=d DG Queue lengths: q_dg_wtos=0, q_dg_wtos_hi=0, q_dg_defrag=0 Congestion Levels: TX LOCAL = 4, TX NET = 0

Sample Output for the bb Option at Level 2

The following example shows frame statistics for the backbone link to the hub: Router# debug satellite firmware level 2 Router# debug satellite firmware bb satellite BackBone events debugging is on Router# 2d06h: Satellite2/0 BB link statistics Frame Type # Received # Transmitted --------------------------------INFORMATION 00096238 00184811 UNNUMBERED 00000000 00000067 RETRANSMITTED 00000000 00000000 POLLS 00000000 00000000 ACKS 00006640 00000455 NAKS 00000000 00000000 PACKS 00000000 00000000 UA 00000001 00000000 SABME 00000000 00000001 DISC 00000000 00000000

Sample Output for the buf Option at Level 1

The following example shows buffer information: Router# debug satellite firmware level 1 Router# debug satellite firmware buf *May 13 15:58:54.498:Satellite1/0 buffers 4951 min 4945 list_str 681858 list_end 686688 emp 683abc fil 6839e8 start 686688 end fb30a8

Sample Output for the buf Option at Level 2

The following example shows buffer owners: Router# debug satellite firmware level 2 Router# debug satellite firmware buf *May 13 15:59:13.438:Satellite1/0 inuse 49 free 4951 Trace byte 1 Trace byte = 0x169 Count = 49 Trace byte 2


DB-1959


Trace byte = 0 buffers 0 buffers 0 buffers 0 buffers

0x 0 Count = 49 with BB Rel only with in lower layer set with do not transmit set on BB retransmit queues

Sample Output for the ip Option at Level 1

The following example shows IP statistics: Router# debug satellite firmware level 1 Router# debug satellite firmware ip *Nov 7 08:27:56.440: Satellite3/0 IP stats: ToIOS_Pkts=0, ToIOS_Bytes=0 FromIOS_Pkts=84751 From_IOS_Bytes=5941124

Sample Output for the rbcp Option at Level 1

The following example shows the number of RBCP messages transmitted and received since the most recent reset of the Cisco IOS software on the router or the VSAT software on the NM-1VSAT-GILAT network module: Router# debug satellite firmware level 1 Router# debug satellite firmware rbcp RBCP statistics:TXcount=301154 RXCount=301155

Sample Output for the rpa Option at Level 1

The following example shows RPA statistics: Router# debug satellite firmware level 1 Router# debug satellite firmware rpa *Nov 7 08:27:13.488:Satellite3/0 RPA stats:ToTunnel=0 FromTunnel=0 TunnelGets=0 TunnelNotGets=0 BlksUsed=0 BlksIn-Use=0 Max=400

Sample Output for the rpa Option at Level 2

The following example shows a tunnel being disconnected: Router# debug satellite firmware level 2 Router# debug satellite firmware rpa *May 13 18:27:59.779:Satellite1/0 RPA Tunnel DOWN RPA:InitTunnelConn Successful locIP e000006 locPort RemPort 9876 RPA Tunnel DOWN RPA:InitTunnelConn Successful locIP e000006 locPort RemPort 9876 RPA Tunnel DOWN RPA:InitTunnelConn Successful locIP e000006 locPort RemPort 9876 RPA Tunnel DOWN RPA:InitTunnelConn Successful locIP e000006 locPort RemPort 9876 RPA Tunnel DOWN RPA:InitTunnelConn Successful locIP e000006 locPort RemPort 9876

1090, RemIP c0a80186,

1091, RemIP c0a80186,

1092, RemIP c0a80186,

1093, RemIP c0a80186,

1094, RemIP c0a80186,


DB-1960

May 2008


Sample Output for the sat Option at All Levels

The following example shows inbound and outbound packet statistics. Note that for all levels, the debug output is the same for the sat option. Router# debug satellite firmware level 1 Router# debug satellite firmware sat satellite related trace events debugging is on Router# 1d16h: Satellite2/0 SAT stats: OUTbound_pkts=25660796, INbound_pkts=3235932 1d16h: Satellite2/0 SAT stats: OUTbound_pkts=25660800, INbound_pkts=3235934 1d16h: Satellite2/0 SAT stats: OUTbound_pkts=25660803, INbound_pkts=3235934 1d16h: Satellite2/0 SAT stats: OUTbound_pkts=25660803, INbound_pkts=3235934

Sample Output for the tcp Option at Level 1

The following example shows TCP statistics: Router# debug satellite firmware level 1 Router# debug satellite firmware tcp satellite tcp events debugging is on Router# 2d06h: Satellite2/0 TCP stats: NetRXBytes=631292 NetTXBytes=4009436 NetRxPkts=49244 ToIOSPkts=49246 2d06h: Satellite2/0 TCP stats: NetRXBytes=1154356 NetTXBytes=4086106 NetRxPkts=49621 ToIOSPkts=49629


The following example shows the TCP connections: Router# debug satellite firmware level 2 Router# debug satellite firmware tcp satellite tcp events debugging is on Router# 2d06h: Satellite2/0 TCP connections: ID=48, locIP=192.168.107.2 remIP=172.25.1.2, locP=2962, remP=21 state=17 iosQ=0 ID=49, locIP=192.168.107.2 remIP=172.25.1.2, locP=2963, remP=20 state=17 iosQ=0 ID=58, locIP=192.168.107.2 remIP=172.25.1.28, locP=2972, remP=21 state=17 iosQ=0 ID=59, locIP=192.168.107.2 remIP=172.25.1.28, locP=2973, remP=20 state=17 iosQ=7 2d06h: ID=48, ID=49, ID=60,

Satellite2/0 TCP connections: locIP=192.168.107.2 remIP=172.25.1.2, locP=2962, remP=21 state=17 iosQ=0 locIP=192.168.107.2 remIP=172.25.1.2, locP=2963, remP=20 state=7 iosQ=0 locIP=192.168.107.2 remIP=172.25.1.28, locP=2974, remP=21 state=3 iosQ=0


The following example shows TCP statistics and connections: Router# debug satellite firmware level 3 Output may be extensive and affect performance. Continue? [yes]: yes Router# debug satellite firmware tcp satellite tcp events debugging is on


DB-1961


Router# 2d06h: Satellite2/0 TCP stats: NetRXBytes=279 NetTXBytes=9436111 NetRxPkts=64991 ToIOSPkts=64999 2d06h: ID=48, ID=49, ID=62,


2d06h: Satellite2/0 TCP stats: NetRXBytes=382 NetTXBytes=9582924 NetRxPkts=64993 ToIOSPkts=65001 2d06h: ID=48, ID=49, ID=62,


Sample Output for the trc Option at Level 3

The following example shows detailed receive and transmit traces for the backbone link: Router# debug satellite firmware level 3 Output may be extensive and affect performance. Continue? [yes]: yes Router# debug satellite firmware trc satellite BackBone trace debugging is on Router# 2d06h: Satellite2/0 strrec 0, rec 0, count 256, trc 1a6dd78, str 1a5c600, end 1a 74600 count 4096, emp 1a6dd78, fil 1a6d8b0, lnknum=6 0 xmt 6 len 951 9 pd con 0 PF 3 ns 169 nr 15 a c12 0 0.000 1 xmt 6 len 951 9 pd con 0 PF 3 ns 170 nr 15 a c12 0 0.010 2 xmt 6 len 951 9 pd con 0 PF 3 ns 171 nr 15 a c12 0 0.010 3 xmt 6 len 951 9 pd con 0 PF 3 ns 172 nr 15 a c12 0 0.010 4 xmt 6 len 951 9 pd con 0 PF 3 ns 173 nr 15 a c12 0 0.030 5 xmt 6 len 2d06h: Satellite2/0 951 2d06h: Satellite2/0 9 pd con 0 PF 3 ns 174 nr 15 a c12 0 0.010 6 xmt 6 len 951 9 pd con 0 PF 3 ns 175 nr 15 a c12 0 0.010 7 xmt 6 len 951 9 pd con 0 PF 3 ns 176 nr 15 a c12 0 0.010 8 xmt 6 len 951 9 pd con 0 PF 3 ns 177 nr 15 a c12 0 0.010 9 xmt 6 len 951 9 pd con 0 PF 3 ns 178 nr 15 a c12 0 0.010 10 xmt 6 len 951 9 pd con 0 PF 3 ns 179 nr 15 a c12 0 0.010 11 xmt 6 len 951 9 pd con 0 PF 3 ns 180 nr 15 a c12 0 0.010

Related Commands

Command

Description

debug satellite

Enables debugging output for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT).


DB-1962

May 2008

Debug Commands debug satellite

debug satellite To enable debugging output for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the debug satellite command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug satellite {all | errors | events | hsrp | rbcp} no debug satellite {all | errors | events | hsrp | rbcp}

Syntax Description

all

Displays all types of satellite debug information.

errors

Displays debug information for satellite error events.

events

Displays debug information for software events.

hsrp

Displays debug information for satellite Hot Standby Router Protocol (HSRP) events.

rbcp

Displays debug information for satellite Router Blade Control Protocol (RBCP) messages.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Usage Guidelines

The debug satellite errors command is useful for catching unusual conditions when troubleshooting unexpected behavior. Because this command typically generates very little output, you can enter the debug satellite errors command every time you troubleshoot satellite network connectivity.

Examples

This section provides the following examples: •

Sample Output for the debug satellite rbcp Command, page 1964

•

Sample Output for the debug satellite events Command, page 1964

•

Sample Output for the debug satellite hsrp Command, page 1964

•

Combined Sample Output for the debug satellite hsrp and debug standby Commands, page 1965


DB-1963


Sample Output for the debug satellite rbcp Command

Every 2 minutes, the NM-1VSAT-GILAT network module sends the router an RBCP message requesting any updates to the routing table. The following example shows how to monitor the route-update messages: Router# debug satellite rbcp ...

The NM-1VSAT-GILAT network module requests IP route information: *May 16 09:18:54.475:Satellite1/0 RBCP Request

msg Recd:IPROUTE_REQ(0x22)

The Cisco IOS software acknowledges that it received the message from the NM-1VSAT-GILAT network module: *May 16 09:18:54.475:Satellite1/0 RBCP Response msg Sent:IPROUTE_REQ(0x22)

The Cisco IOS software sends the IP route information to the NM-1VSAT-GILAT network module: *May 16 09:18:54.475:Satellite1/0 RBCP Request

msg Sent:IPROUTE_UPD(0x23)

The NM-1VSAT-GILAT network module acknowledges that it received the routing update from the Cisco IOS software: *May 16 09:18:54.475:Satellite1/0 RBCP Response msg Recd:IPROUTE_UPD(0x23)

Sample Output for the debug satellite events Command

The following example shows how to monitor the periodic heartbeats that the NM-1VSAT-GILAT network module sends to the Cisco IOS software: Router# debug satellite events satellite major software events debugging is on .Dec 16 12:57:52.108:Satellite1/0 FSM transition .Dec 16 12:58:08.888:Satellite1/0 FSM transition .Dec 16 12:58:25.664:Satellite1/0 FSM transition .Dec 16 12:58:42.440:Satellite1/0 FSM transition

LINK_UP-->LINK_UP, LINK_UP-->LINK_UP, LINK_UP-->LINK_UP, LINK_UP-->LINK_UP,

ev=got_heartbeat ev=got_heartbeat ev=got_heartbeat ev=got_heartbeat

Sample Output for the debug satellite hsrp Command

The following example shows the debug satellite hsrp command messages that appear when the active router is forced to standby status because the HSRP-tracked satellite interface is shut down: Router# configure terminal Enter configuration commands, one per line.

End with CNTL/Z.

Router(config)# interface satellite 1/0 Router(config-if)# shutdown Router(config-if)# end Router# 01:03:48:%SYS-5-CONFIG_I:Configured from console by console 01:03:49:%LINK-5-CHANGED:Interface Satellite1/0, changed state to administratively down 01:03:50:%LINEPROTO-5-UPDOWN:Line protocol on Interface Satellite1/0, changed state to down 01:04:22:%HSRP-6-STATECHANGE:FastEthernet0/0 Grp 1 state Active -> Speak 01:04:22:HSRP-sat:IPred group grp-x update state ACTIVE --> SPEAK 01:04:22:Satellite1/0 HSRP-sat:fsm crank ACTIVE-->STANDBY 01:04:22:Satellite1/0 HSRP-sat:send standby msg STANDBY 01:04:32:HSRP-sat:IPred group grp-x update state SPEAK --> STANDBY 01:04:32:Satellite1/0 HSRP-sat:fsm crank STANDBY-->STANDBY 01:04:32:Satellite1/0 HSRP-sat:send standby msg STANDBY 01:04:42:Satellite1/0 HSRP-sat:send standby msg STANDBY 01:04:52:Satellite1/0 HSRP-sat:standby msg STANDBY deferred, not in operational state 01:05:02:Satellite1/0 HSRP-sat:standby msg STANDBY deferred, not in operational state 01:05:12:Satellite1/0 HSRP-sat:standby msg STANDBY deferred, not in operational state


DB-1964

May 2008


01:05:22:Satellite1/0 HSRP-sat:standby msg STANDBY deferred, not in operational state 01:05:32:Satellite1/0 HSRP-sat:standby msg STANDBY not sent, already in state 01:06:47:%VSAT-5-STANDBY_MODE:Satellite1/0 module configured for standby mode 01:09:32:Satellite1/0 HSRP-sat:fsm crank STANDBY-->STANDBY-UP

Combined Sample Output for the debug satellite hsrp and debug standby Commands

The following example shows HSRP-related debug output for both the router and the NM-1VSAT-GILAT network module when the router goes from standby to active state because the HSRP-tracked satellite interface is reenabled: Router# show debugging SATCOM: satellite HSRP events debugging is on HSRP: HSRP Errors debugging is on HSRP Events debugging is on HSRP Packets debugging is on

The satellite interface is reenabled: Router# configure terminal Router(config)# interface satellite 1/0 Router(config-if)# no shutdown Router(config-if)# end Router#

The effective HSRP priority of the router changes as the tracked satellite interface comes up: 02:14:37:HSRP:Fa0/0 02:14:39:HSRP:Fa0/0 02:14:39:HSRP:Fa0/0 02:14:39:HSRP:Fa0/0 02:14:39:HSRP:Fa0/0 Router#

Grp API Grp Grp Grp

1 Hello in 10.123.96.2 Active pri 90 vIP 10.123.96.100 10.1.0.6 is not an HSRP address 1 Hello out 10.123.96.3 Standby pri 90 vIP 10.123.96.100 1 Track 1 object changed, state Down -> Up 1 Priority 90 -> 100

The router changes from standby to active state because its priority is now highest in the hot standby group, and preemption is enabled: 02:14:40:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Active pri 90 vIP 10.123.96.100 02:14:40:HSRP:Fa0/0 Grp 1 Standby:h/Hello rcvd from lower pri Active router (90/10.123.96.2) 02:14:40:HSRP:Fa0/0 Grp 1 Active router is local, was 10.123.96.2 02:14:40:HSRP:Fa0/0 Grp 1 Standby router is unknown, was local 02:14:40:HSRP:Fa0/0 Redirect adv out, Active, active 1 passive 3 02:14:40:HSRP:Fa0/0 Grp 1 Coup out 10.123.96.3 Standby pri 100 vIP 10.123.96.100 02:14:40:HSRP:Fa0/0 Grp 1 Standby -> Active 02:14:40:%HSRP-6-STATECHANGE:FastEthernet0/0 Grp 1 state Standby -> Active

The HSRP status of the satellite interface also changes from standby to active state because the service-module ip redundancy command was previously entered to link the HSRP status of the satellite interface to the primary HSRP interface, Fast Ethernet 0/0. 02:14:40:HSRP:Fa0/0 Grp 1 Redundancy "grp-x" state Standby -> Active 02:14:40:HSRP-sat:IPred group grp-x update state STANDBY --> ACTIVE 02:14:40:Satellite1/0 HSRP-sat:fsm crank STANDBY-UP-->ACTIVE-COND 02:14:40:HSRP:Fa0/0 Redirect adv out, Active, active 1 passive 2 02:14:40:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.100 02:14:40:HSRP:Fa0/0 REDIRECT adv in, Passive, active 0, passive 2, from 10.123.96.2 02:14:40:HSRP:Fa0/0 REDIRECT adv in, Passive, active 0, passive 1, from 10.123.96.15 02:14:40:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Speak pri 90 vIP 10.123.96.100


DB-1965


Line protocols come up, and HSRP states become fully active: 02:14:41:%LINK-3-UPDOWN:Interface Satellite1/0, changed state to up 02:14:42:%LINEPROTO-5-UPDOWN:Line protocol on Interface Satellite1/0, changed state to up 02:14:43:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.100 02:14:43:HSRP:Fa0/0 Grp 1 Redundancy group grp-x state Active -> Active 02:14:43:HSRP-sat:IPred group grp-x update state ACTIVE --> ACTIVE 02:14:43:Satellite1/0 HSRP-sat:fsm crank ACTIVE-COND-->ACTIVE-COND 02:14:43:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Speak pri 90 vIP 10.123.96.100 02:14:46:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.100 02:14:46:HSRP:Fa0/0 Grp 1 Redundancy group grp-x state Active -> Active 02:14:46:HSRP-sat:IPred group grp-x update state ACTIVE --> ACTIVE 02:14:46:Satellite1/0 HSRP-sat:fsm crank ACTIVE-COND-->ACTIVE-COND 02:14:46:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Speak pri 90 vIP 10.123.96.100 02:14:49:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.100 02:14:49:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Speak pri 90 vIP 10.123.96.100 02:14:50:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Standby pri 90 vIP 10.123.96.100 02:14:50:HSRP:Fa0/0 Grp 1 Standby router is 10.123.96.2 02:14:51:Satellite1/0 HSRP-sat:send standby msg ACTIVE 02:14:52:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.100 02:14:53:HSRP:Fa0/0 Grp 1 Hello in 10.123.96.2 Standby pri 90 vIP 10.123.96.100 02:14:55:HSRP:Fa0/0 Grp 1 Hello out 10.123.96.3 Active pri 100 vIP 10.123.96.100

Related Commands

Command

Description

debug satellite firmware

Enables debugging output for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) firmware.

debug standby

Displays all HSRP errors, events, and packets.


DB-1966

May 2008

Debug Commands debug sccp config

debug sccp config To enable Skinny Client Control Protocol (SCCP) event debugging, use the debug sccp config command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sccp config {all | errors | events | parser} no debug sccp config {all | errors | events | parser}

Syntax Description

all

Displays all SCCP auto-config debug trace.

errors

Displays SCCP auto-config errors.

events

Displays SCCP auto-config events.

parser

Displays SCCP auto-config parser.

Command Default

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)XY

This command was introduced on the Communication Media Module.

12.3(14)T


12.4(3)


12.2SX


Examples

The following example shows the debug sccp config command used to enable SCCP event debugging and to display SCCP auto-configuration events: Router# debug sccp config events ... Feb 8 02:17:31.119: mp_auto_cfg_request(req_id=2, prof=995, ccm_group_id=0) Feb 8 02:17:31.123: mp_auto_cfg_is_up: SCCP auto-config is enabled & registered ...


DB-1967

Debug Commands debug sccp config


Related Commands

debug sccp config Field Descriptions

Field

Description

prof=995

Indicates the profile ID. If generated by media processor auto-configuration, profile IDs are preceded by 99.

SCCP auto-config is enabled & registered

Indicates the registration of sccp when auto-config is complete.

Command

Description

auto-config

Enables auto-configuration or enters auto-config application configuration mode for the SCCP application.

debug auto-config

Enables debugging for auto-configuration applications.

show auto-config

Displays the current status of auto-configuration applications.


DB-1968

May 2008

Debug Commands debug sccp

debug sccp To display debugging information for Simple Client Control Protocol (SCCP) and its related applications (transcoding and conferencing), use the debug sccp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sccp {all | errors | events | packets | parser} no debug sccp

Syntax Description

all

All SCCP debug-trace information.

errors

SCCP errors.

events

SCCP events.

packets

SCCP packets.

parser

SCCP parser and builder.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(5)YH

This command was introduced on the Cisco VG200.

12.2(13)T

This command was implemented on the Cisco 2600 series, Cisco 3620, Cisco 3640, Cisco 3660, and Cisco 3700 series.

12.2SX


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 and conferencing digital signal processor (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 sccp events command: Router# debug sccp events Skinny Client Control Protocol events debugging is on *Mar count *Mar *Mar *Mar *Mar count

1 0 1 1 1 1 0

00:46:29: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, 00:46:29: 00:46:29: 00:46:29: 00:46:30:

sccp_keepalive: send keepalive id 0, len 4 sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4 sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256 sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2,


DB-1969


*Mar 1 00:46:30: sccp_keepalive: send keepalive id 0, len 4 *Mar 1 00:46:30: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:30: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256 *Mar 1 00:46:37: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0 *Mar 1 00:46:37: sccp_keepalive: send keepalive id 0, len 4 *Mar 1 00:46:37: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4 *Mar 1 00:46:37: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256 *Mar 1 00:46:37: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0 *Mar 1 00:46:37: sccp_keepalive: send keepalive id 0, len 4 *Mar 1 00:46:38: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:38: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256 *Mar 1 00:46:43: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:43: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 28, offset 36, msg_id 261 *Mar 1 00:46:43: xapp_open_receive_chnl: SCCP orc_msg - 6248FC8C, appl - 6248FC10 *Mar 1 00:46:43: xapp_search_for_chnl_rec: sess_id 27, conn_id 2769 *Mar 1 00:46:43: xapp_add_chnl_rec: chnl 631142BC *Mar 1 00:46:43: xapp_add_sess_rec: Add sess_rec (63114360) record *Mar 1 00:46:43: xapp_open_receive_chnl: stat 0, eve 0, sid 27, cid 2769, codec 1, pkt-period 20 *Mar 1 00:46:43: xapp_open_chnl_request: chnl_rec 631142BC *Mar 1 00:46:43: xapp_open_chnl_request: chnl_rec 631142BC, sess_id 27, conn_id 2769, cstate 0, nstate 1 *Mar 1 00:46:43: xapp_dequeue_and_process_dspf_events: chnl_rec 631142BC, state 1, eve_id 1 *Mar 1 00:46:43: xapp_open_chnl_success: chnl_rec 631142BC *Mar 1 00:46:43: xapp_open_chnl_success: chnl_rec 631142BC, sess_id 27, conn_id 2769, cstate 1, nstate 2, lc_ipaddr 10.10.1.1, lport 21066 *Mar 1 00:46:43: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:43: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 28, offset 36, msg_id 261 *Mar 1 00:46:43: xapp_open_receive_chnl: SCCP orc_msg - 6248FC8C, appl - 6248FC10 *Mar 1 00:46:43: xapp_search_for_chnl_rec: sess_id 27, conn_id 2785 *Mar 1 00:46:43: xapp_add_chnl_rec: chnl 631142E4 *Mar 1 00:46:43: xapp_open_receive_chnl: stat 0, eve 0, sid 27, cid 2785, codec 1, pkt-period 20 *Mar 1 00:46:43: xapp_open_chnl_request: chnl_rec 631142E4 *Mar 1 00:46:43: xapp_open_chnl_request: chnl_rec 631142E4, sess_id 27, conn_id 2785, cstate 0, nstate 1 *Mar 1 00:46:43: xapp_dequeue_and_process_dspf_events: chnl_rec 631142E4, state 1, eve_id 1 *Mar 1 00:46:43: xapp_open_chnl_success: chnl_rec 631142E4 *Mar 1 00:46:43: xapp_open_chnl_success: chnl_rec 631142E4, sess_id 27, conn_id 2785, cstate 1, nstate 2, lc_ipaddr 10.10.1.1, lport 25706 *Mar 1 00:46:43: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:43: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 44, offset 52, msg_id 138 *Mar 1 00:46:43: xapp_start_media_transmission: SCCP stmt_msg - 6248FC8C, appl - 6248FC10 *Mar 1 00:46:43: xapp_search_for_chnl_rec: sess_id 27, conn_id 2769 *Mar 1 00:46:43: xapp_start_media_transmission: chnl_rec 631142BC, stat 2, sid 27, cid 2769, ripaddr 10.10.1.5, rport 32148, codec 1, pkt-period 20, pre 11, silen 16777500, mfpp 1 *Mar 1 00:46:43: xapp_modify_chnl_request: chnl_rec 631142BC *Mar 1 00:46:43: xapp_modify_chnl_request: chnl_rec 631142BC, sess_id 27, conn_id 2769, cstate 2, nstate 2 *Mar 1 00:46:43: xapp_dequeue_and_process_dspf_events: chnl_rec 631142BC, state 2, eve_id 4 *Mar 1 00:46:43: xapp_modify_chnl_success: chnl_rec 631142BC, sess_id 27, conn_id 2769, cstate 2 *Mar 1 00:46:43: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:43: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 44, offset 52, msg_id 138 *Mar 1 00:46:43: xapp_start_media_transmission: SCCP stmt_msg - 6248FC8C, appl - 6248FC10 *Mar 1 00:46:43: xapp_search_for_chnl_rec: sess_id 27, conn_id 2785


DB-1970

May 2008


*Mar 1 00:46:43: xapp_start_media_transmission: chnl_rec 631142E4, stat 2, sid 27, cid 2785, ripaddr 10.10.1.7, rport 16422, codec 1, pkt-period 20, pre 11, silen 16777501, mfpp 1 *Mar 1 00:46:43: xapp_modify_chnl_request: chnl_rec 631142E4 *Mar 1 00:46:43: xapp_modify_chnl_request: chnl_rec 631142E4, sess_id 27, conn_id 2785, cstate 2, nstate 2 *Mar 1 00:46:43: xapp_dequeue_and_process_dspf_events: chnl_rec 631142E4, state 2, eve_id 4 *Mar 1 00:46:43: xapp_modify_chnl_success: chnl_rec 631142E4, sess_id 27, conn_id 2785, cstate 2 *Mar 1 00:46:44: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0 *Mar 1 00:46:44: sccp_keepalive: send keepalive id 0, len 4 *Mar 1 00:46:45: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4 *Mar 1 00:46:45: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256 *Mar 1 00:46:45: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0 *Mar 1 00:46:45: sccp_keepalive: send keepalive id 0, len 4 *Mar 1 00:46:46: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:46: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256 *Mar 1 00:46:47: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:47: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 28, offset 36, msg_id 261 *Mar 1 00:46:47: xapp_open_receive_chnl: SCCP orc_msg - 6248FC8C, appl - 6248FC10 *Mar 1 00:46:47: xapp_search_for_chnl_rec: sess_id 27, conn_id 2817 *Mar 1 00:46:47: xapp_add_chnl_rec: chnl 6311430C *Mar 1 00:46:47: xapp_open_receive_chnl: stat 0, eve 0, sid 27, cid 2817, codec 1, pkt-period 20 *Mar 1 00:46:47: xapp_open_chnl_request: chnl_rec 6311430C *Mar 1 00:46:47: xapp_open_chnl_request: chnl_rec 6311430C, sess_id 27, conn_id 2817, cstate 0, nstate 1 *Mar 1 00:46:47: xapp_dequeue_and_process_dspf_events: chnl_rec 6311430C, state 1, eve_id 1 *Mar 1 00:46:47: xapp_open_chnl_success: chnl_rec 6311430C *Mar 1 00:46:47: xapp_open_chnl_success: chnl_rec 6311430C, sess_id 27, conn_id 2817, cstate 1, nstate 2, lc_ipaddr 10.10.1.1, lport 16730 *Mar 1 00:46:47: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:47: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 44, offset 52, msg_id 138 *Mar 1 00:46:47: xapp_start_media_transmission: SCCP stmt_msg - 6248FC8C, appl - 6248FC10 *Mar 1 00:46:47: xapp_search_for_chnl_rec: sess_id 27, conn_id 2817 *Mar 1 00:46:47: xapp_start_media_transmission: chnl_rec 6311430C, stat 2, sid 27, cid 2817, ripaddr 10.10.1.6, rport 18160, codec 1, pkt-period 20, pre 11, silen 16777502, mfpp 1 *Mar 1 00:46:47: xapp_modify_chnl_request: chnl_rec 6311430C *Mar 1 00:46:47: xapp_modify_chnl_request: chnl_rec 6311430C, sess_id 27, conn_id 2817, cstate 2, nstate 2 *Mar 1 00:46:47: xapp_dequeue_and_process_dspf_events: chnl_rec 6311430C, state 2, eve_id 4 *Mar 1 00:46:47: xapp_modify_chnl_success: chnl_rec 6311430C, sess_id 27, conn_id 2817, cstate 2 *Mar 1 00:46:52: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0 *Mar 1 00:46:52: sccp_keepalive: send keepalive id 0, len 4 *Mar 1 00:46:52: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4 *Mar 1 00:46:52: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256 *Mar 1 00:46:53: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0 *Mar 1 00:46:53: sccp_keepalive: send keepalive id 0, len 4 *Mar 1 00:46:54: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 *Mar 1 00:46:54: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256 *Mar 1 00:46:59: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0 *Mar 1 00:46:59: sccp_keepalive: send keepalive id 0, len 4 *Mar 1 00:47:00: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4 *Mar 1 00:47:00: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256


DB-1971


*Mar count *Mar *Mar *Mar *Mar count *Mar *Mar *Mar *Mar count *Mar *Mar *Mar *Mar count *Mar *Mar *Mar *Mar count *Mar *Mar *Mar *Mar count *Mar *Mar *Mar *Mar count *Mar *Mar *Mar *Mar count *Mar *Mar *Mar *Mar count *Mar *Mar *Mar

Related Commands

1 0 1 1 1 1 0 1 1 1 1 0 1 1 1 1 0 1 1 1 1 0 1 1 1 1 0 1 1 1 1 0 1 1 1 1 0 1 1 1 1 0 1 1 1

00:47:01: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, 00:47:01: 00:47:01: 00:47:01: 00:47:07:

sccp_keepalive: send keepalive id 0, len 4 sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256 sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1,

00:47:07: 00:47:07: 00:47:07: 00:47:08:


00:47:08: 00:47:09: 00:47:09: 00:47:14:


00:47:14: 00:47:15: 00:47:15: 00:47:16:


00:47:16: 00:47:16: 00:47:16: 00:47:22:


00:47:22: 00:47:22: 00:47:22: 00:47:23:


00:47:23: 00:47:24: 00:47:24: 00:47:29:


00:47:29: 00:47:30: 00:47:30: 00:47:31:


00:47:31: sccp_keepalive: send keepalive id 0, len 4 00:47:31: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84 00:47:31: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256

Command

Description

debug frame-relay vc-bundle

Sets debugging levels for the DSP-farm service.

dspfarm (DSP farm)

Enables DSP-farm service.

sccp

Enables SCCP and its associated transcoding and conferencing applications.

show sccp

Displays the SCCP configuration information and current status.


DB-1972

May 2008

Debug Commands debug sccp keepalive

debug sccp keepalive To display granular debugging information by Cisco Call Manager (CCM) group for Simple Client Control Protocol (SCCP) and its related applications (transcoding and conferencing), use the debug sccp keepalive command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sccp keepalive [identifier] no debug sccp keepalive

Syntax Description

identifier

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(5)T


12.4(20)T

The output for this command was modified to identify which CCM the keepalives are being sent to and received from to help users distinguish which devices have proper connectivity and which do not. Prior to this modification there was no information as to which devices keepalive messages were being exchanged between.

Examples

Requests that only keepalive traffic from a specific CCM be reported, for more granular debugging.

The following example shows output from the debug sccp keepalive command: Router# debug sccp keepalive Skinny Client Control Protocol keepalive messages debugging is on May May May May May May May May May May May May

18 18 18 18 18 18 18 18 18 18 18 18

13:53:39.242 13:53:39.242 13:53:39.570 13:53:39.570 13:54:09.243 13:54:09.243 13:54:09.571 13:54:09.571 13:54:39.243 13:54:39.243 13:54:39.571 13:54:39.571

EDT: EDT: EDT: EDT: EDT: EDT: EDT: EDT: EDT: EDT: EDT: EDT:

SCCP:send SCCP:rcvd SCCP:send SCCP:rcvd SCCP:send SCCP:rcvd SCCP:send SCCP:rcvd SCCP:send SCCP:rcvd SCCP:send SCCP:rcvd

KeepAliveMessage to KeepAliveAckMessage KeepAliveMessage to KeepAliveAckMessage KeepAliveMessage to KeepAliveAckMessage KeepAliveMessage to KeepAliveAckMessage KeepAliveMessage to KeepAliveAckMessage KeepAliveMessage to KeepAliveAckMessage

ccm identifier 1 from ccm identifier ccm identifier 2 from ccm identifier ccm identifier 1 from ccm identifier ccm identifier 2 from ccm identifier ccm identifier 1 from ccm identifier ccm identifier 2 from ccm identifier

1 2 1 2 1 2


DB-1973

Debug Commands debug sccp keepalive

Related Commands

Command

Description

debug sccp

Displays debugging information for SCCP and its related applications (transcoding and conferencing).

sccp

Enables SCCP and its associated transcoding and conferencing applications.


DB-1974

May 2008

Debug Commands debug sdlc local-ack

debug sdlc local-ack To display information on the local acknowledgment feature, use the debug sdlc local-ack command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sdlc local-ack [number] no debug sdlc local-ack [number]

Syntax Description

number

Command Modes

Privileged EXEC

Usage Guidelines

You can select the frame types you want to monitor; the frame types correspond to bit flags. You can select 1, 2, 4, or 7, which is the decimal value of the bit flag settings. If you select 1, the octet is set to 00000001. If you select 2, the octet is set to 0000010. If you select 4, the octet is set to 00000100. If you want to select all frame types, select 7; the octet is 00000111. The default is 7 for all events. Table 303 defines these bit flags. Table 303

Caution

(Optional) Frame-type that you want to monitor. See the “Usage Guidelines” section.

debug sdlc local-ack Debugging Levels

Debug Command

Meaning

debug sdlc local-ack 1

Only U-Frame events


Only I-Frame events


Only S-Frame events


All Synchronous Data Link Control (SDLC) Local-Ack events (default setting)

Because using this command is processor intensive, it is best to use it after hours, rather than in a production environment. It is also best to use this command by itself, rather than in conjunction with other debugging commands.


DB-1975

Debug Commands debug sdlc local-ack

Examples

The following is sample output from the debug sdlc local-ack command: router# debug sdlc local-ack 1 SLACK (Serial3): Input = Network, LinkupRequest SLACK (Serial3): Old State = AwaitSdlcOpen SLACK (Serial3): Output

= SDLC, SNRM

SLACK (Serial3): Input = SDLC, UA SLACK (Serial3): Old State = AwaitSdlcOpen SLACK (Serial3): Output

New State = AwaitSdlcOpen

New State = Active

= Network, LinkResponse

S2560

Group of associated operations

The first line shows the input to the SDLC local acknowledgment state machine: SLACK (Serial3): Input

= Network, LinkupRequest


debug sdlc local-ack Field Descriptions

Field

Description

SLACK

SDLC local acknowledgment feature is providing the information.

(Serial3):

Interface type and unit number reporting the event.

Input = Network

Source of the input.

LinkupRequest

Op code. A LinkupRequest is an example of possible values.

The second line shows the change in the SDLC local acknowledgment state machine. In this case the AwaitSdlcOpen state is an internal state that has not changed while this display was captured. SLACK (Serial3): Old State = AwaitSdlcOpen

New State = AwaitSdlcOpen

The third line shows the output from the SDLC local acknowledgment state machine: SLACK (Serial3): Output

= SDLC, SNRM


DB-1976

May 2008

Debug Commands debug sdlc packet

debug sdlc packet To display packet information on Synchronous Data Link Control (SDLC) frames received and sent by any router serial interface involved in supporting SDLC end station functions, use the debug sdlc packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sdlc packet [max-bytes] no debug sdlc packet [max-bytes]

Syntax Description

max-bytes

Command Modes

Privileged EXEC

Usage Guidelines

This command requires intensive CPU processing; therefore, we recommend not using it when the router is expected to handle normal network loads, such as in a production environment. Instead, use this command when network response is noncritical. We also recommend that you use this command by itself, rather than in conjunction with other debug commands.

Examples

The following is sample output from the debug sdlc packet command with the packet display limited to 20 bytes of data:

(Optional) Limits the number of bytes of data that are printed to the display.

Router# debug sdlc packet 20 Serial3 SDLC Output 00000 C3842C00 02010010 019000C5 C5C5C5C5 Cd.........EEEEE 00010 C5C5C5C5 EEEE Serial3 SDLC Output 00000 C3962C00 02010011 039020F2 Co.........2 Serial3 SDLC Output 00000 C4962C00 0201000C 039020F2 Do.........2 Serial3 SDLC Input 00000 C491 Dj


DB-1977

Debug Commands debug sdlc

debug sdlc To display information on Synchronous Data Link Control (SDLC) frames received and sent by any router serial interface involved in supporting SDLC end station functions, use the debug sdlc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sdlc no debug sdlc

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines Note

Examples

Because the debug sdlc command can generate many messages and alter timing in the network node, use it only when instructed by authorized support personnel.

The following is sample output from the debug sdlc command: Router# debug sdlc SDLC: Sending Serial3: SDLC Serial3: SDLC Serial3: SDLC SDLC: Sending Serial3: SDLC Serial3: SDLC Serial3: SDLC

RR at location 4 O (12495952) C2 CONNECT (2) RR P/F 6 I (12495964) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0] T [C2] 12496064 CONNECT 12496064 0 RR at location 4 O (12496064) C2 CONNECT (2) RR P/F 6 I (12496076) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0] T [C2] 12496176 CONNECT 12496176 0

The following line of output indicates that the router is sending a Receiver Ready packet at location 4 in the code: SDLC: Sending RR at location 4

The following line of output describes a frame output event: Serial1/0: SDLC O 04 CONNECT (285) IFRAME P/F 6


DB-1978

May 2008



debug sdlc Field Descriptions for a Frame Output Event

Field

Description

Serial1/0

Interface type and unit number reporting the frame event.

SDLC

Protocol providing the information.

O

Command mode of frame event. Possible values are as follows: •

I—Frame input

•

O—Frame output

•

T—T1 timer expired

04

SDLC address of the SDLC connection.

CONNECT

State of the protocol when the frame event occurred. Possible values are as follows: •

CONNECT

•

DISCONNECT

•

DISCSENT (disconnect sent)

•

ERROR (FRMR frame sent)

•

REJSENT (reject frame sent)

•

SNRMSENT (SNRM frame sent)

•

USBUSY

•

THEMBUSY

•

BOTHBUSY

(285)

Size of the frame (in bytes).

IFRAME

Frame type name. Possible values are as follows: •

DISC—Disconnect

•

DM—Disconnect mode

•

FRMR—Frame reject

•

IFRAME—Information frame

•

REJ—Reject

•

RNR—Receiver not ready

•

RR—Receiver ready

•

SIM—Set Initialization mode command

•

SNRM—Set Normal Response Mode

•

TEST—Test frame

•

UA—Unnumbered acknowledgment

•

XID—EXchange ID


DB-1979


Table 305

debug sdlc Field Descriptions for a Frame Output Event (continued)

Field

Description

P/F

Poll/Final bit indicator. Possible values are as follows:

6

•

F—Final (printed for Response frames)

•

P—Poll (printed for Command frames)

•

P/F—Poll/Final (printed for RR, RNR, and REJ frames, which can be either Command or Response frames)

Receive count; range: 0 to 7.

The following line of output describes a frame input event: Serial1/0: SDLC I 02 CONNECT (16) IFRAME P 7 0,[VR: 7 VS: 0]


debug sdlc Field Descriptions for a Frame Input Event

Field

Description

02

SDLC address.

IFRAME

Traffic engineering type.

P

Poll bit P is on.

VR: 7

Receive count; range: 0 to 7.

VS: 0

Send count; range: 0 to 7.

The following line of output describes a frame timer event: Serial1/0: SDLC T 02 CONNECT 0x9CB69E8 P 0


debug sdlc Field Descriptions for a Timer Event

Field

Description

Serial1/0

Interface type and unit number reporting the frame event.

SDLC

Protocol providing the information.

T

Timer has expired.

02

SDLC address of this SDLC connection.


DB-1980

May 2008


Table 307

Related Commands

debug sdlc Field Descriptions for a Timer Event (continued)

Field

Description

CONNECT

State of the protocol when the frame event occurred. Possible values are as follows: •

BOTHBUSY

•

CONNECT

•

DISCONNECT

•

DISCSENT (disconnect sent)

•

ERROR (FRMR frame sent)

•

REJSENT (reject frame sent)

•

SNRMSENT (SNRM frame sent)

•

THEMBUSY

•

USBUSY

0x9CB69E8

Top timer.

0

Retry count; default: 0.

Command

Description

debug list

Filters debugging information on a per-interface or per-access list basis.


DB-1981

Debug Commands debug serial interface

debug serial interface To display information on a serial connection failure, use the debug serial interface command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug serial interface no debug serial interface

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

If the show interface serial EXEC command shows that the line and protocol are down, you can use the debug serial interface command to isolate a timing problem as the cause of a connection failure. If the keepalive values in the mineseq, yourseen, and myseen fields are not incrementing in each subsequent line of output, there is a timing or line problem at one end of the connection.

Caution

Although the debug serial interface command typically does not generate a substantial amount of output, nevertheless use it cautiously during production hours. When Switched Multimegabit Data Service (SMDS) is enabled, for example, it can generate considerable output. The output of the debug serial interface command can vary, depending on the type of WAN configured for an interface: Frame Relay, High-Level Data Link Control (HDL) , High-Speed Serial Interface (HSSI), SMDS, or X.25. The output also can vary depending on the type of encapsulation configured for that interface. The hardware platform also can affect debug serial interface output.

Examples

The following sections show and describe sample debug serial interface output for various configurations. Debug Serial Interface for Frame Relay Encapsulation

The following message is displayed if the encapsulation for the interface is Frame Relay (or HDLC) and the router attempts to send a packet containing an unknown packet type: Illegal serial link type code xxx

Debug Serial Interface for HDLC

The following is sample output from the debug serial interface command for an HDLC connection when keepalives are enabled. This output shows that the remote router is not receiving all the keepalives the router is sending. When the difference in the values in the myseq and mineseen fields exceeds three, the line goes down and the interface is reset.


DB-1982

May 2008


router# debug serial interface Serial1: Serial1: Serial1: Serial1: Serial1: Serial1: Serial1: Serial1:

3 missed keepalives; line goes down and interface is reset

myseq myseq myseq myseq myseq myseq myseq myseq

636119, 636120, 636121, 636122, 636123, 636124, 636125, 636126,

mineseen mineseen mineseen mineseen mineseen mineseen mineseen mineseen

636119, 636120, 636121, 636122, 636123, 636124, 636125, 636126,

yourseen yourseen yourseen yourseen yourseen yourseen yourseen yourseen

515032, 515033, 515034, 515035, 515036, 515037, 515038, 515039,

line line line line line line line line

up up up up up up up up

Serial1: HDLC myseq 636127, mineseen 636127, yourseen 515040, line up Serial1: HDLC myseq 636128, mineseen 636127, yourseen 515041, line up Serial1: HDLC myseq 636129, mineseen 636129, yourseen 515042, line up Serial1: Serial1: Serial1: Serial1: Serial1: Serial1: Serial1:

HDLC HDLC HDLC HDLC HDLC HDLC HDLC

myseq myseq myseq myseq myseq myseq myseq

636130, 636131, 636132, 636133, 636127, 636128, 636129,

mineseen mineseen mineseen mineseen mineseen mineseen mineseen

636130, 636130, 636130, 636130, 636127, 636127, 636129,

yourseen yourseen yourseen yourseen yourseen yourseen yourseen

515043, 515044, 515045, 515046, 515040, 515041, 515042,

line line line line line line line

up up up down up up up

S2561

1 missed keepalive

HDLC HDLC HDLC HDLC HDLC HDLC HDLC HDLC


debug serial interface Field Descriptions for HDLC

Field

Description

Serial 1

Interface through which the serial connection is taking place.

HDLC

Serial connection is an HDLC connection.

myseq 636119

Myseq counter increases by one each time the router sends a keepalive packet to the remote router.

mineseen 636119

Value of the mineseen counter reflects the last myseq sequence number the remote router has acknowledged receiving from the router. The remote router stores this value in its yourseen counter and sends that value in a keepalive packet to the router.

yourseen 515032

Yourseen counter reflects the value of the myseq sequence number the router has received in a keepalive packet from the remote router.

line up

Connection between the routers is maintained. Value changes to “line down” if the values of the myseq and myseen fields in a keepalive packet differ by more than three. Value returns to “line up” when the interface is reset. If the line is in loopback mode, (“looped”) appears after this field.

Table 309 describes additional error messages that the debug serial interface command can generate for HDLC.


DB-1983


Table 309

debug serial interface Error Messages for HDLC

Field

Description

Illegal serial link type code , PC = 0xnnnnnn

Router attempted to send a packet containing an unknown packet type.

Illegal HDLC serial type code , PC = 0xnnnnn

Unknown packet type is received.

Serial 0: attempting to restart

Interface is down. The hardware is then reset to correct the problem, if possible.

Serial 0: Received bridge packet Bridge packet is received over a serial interface configured for sent to HDLC, and bridging is not configured on that interface. Debug Serial Interface for HSSI

On an HSSI interface, the debug serial interface command can generate the following additional error message: HSSI0: Reset from 0xnnnnnnn

This message indicates that the HSSI hardware has been reset. The 0xnnnnnnn variable is the address of the routine requesting that the hardware be reset; this value is useful only to development engineers. Debug Serial Interface for ISDN Basic Rate

Table 310 describes error messages that the debug serial interface command can generate for ISDN Basic Rate. Table 310

debug serial interface Error Messages for ISDN Basic Rate

Message

Description

BRI: D-chan collision

Collision on the ISDN D channel has occurred; the software will retry transmission.

Received SID Loss of Frame Alignment int.

ISDN hardware has lost frame alignment. This usually indicates a problem with the ISDN network.

Unexpected IMP int: ipr = 0xnn

ISDN hardware received an unexpected interrupt. The 0xnn variable indicates the value returned by the interrupt register.

BRI(d): RX Frame Length Violation. Any of these messages can be displayed when a receive error occurs on one of the ISDN channels. The (d) indicates which Length=n channel it is on. These messages can indicate a problem with BRI(d): RX Nonoctet Aligned Frame the ISDN network connection. BRI(d): RX Abort Sequence BRI(d): RX CRC Error BRI(d): RX Overrun Error BRI(d): RX Carrier Detect Lost BRI0: Reset from 0xnnnnnnn

BRI hardware has been reset. The 0xnnnnnnn variable is the address of the routine that requested that the hardware be reset; it is useful only to development engineers.


DB-1984

May 2008


Table 310

debug serial interface Error Messages for ISDN Basic Rate (continued)

Message

Description

Any of these messages can be displayed if the ISDN hardware is not in the proper state. The hardware is then reset. If the message is displayed constantly, it usually indicates a BRI(d): Bad state in SCONs scon1=x hardware problem. scon2 =x scon3=x

BRI(d): Bad state in SCMs scm1=x scm2=x scm3=x

BRI(d): Bad state ub SCR; SCR=x BRI(d): Illegal packet encapsulation=n

Packet is received, but the encapsulation used for the packet is not recognized. The interface might be misconfigured.

Debug Serial Interface for an MK5025 Device

Table 311 describes the additional error messages that the debug serial interface command can generate for an MK5025 device. Table 311

debug serial interface Error Messages for an MK5025 Device

Message

Description

MK5(d): Reset from 0xnnnnnnnn

Hardware has been reset. The 0xnnnnnnn variable is the address of the routine that requested that the hardware be reset; it is useful only to development engineers.

MK5(d): Illegal packet encapsulation=n

Packet is received, but the encapsulation used for the packet is not recognized. Interface might be misconfigured.

MK5(d): No packet available for packet realignment

Serial driver attempted to get a buffer (memory) and was unable to do so.

MK5(d): Bad state in CSR0=(x)

This message is displayed if the hardware is not in the proper state. The hardware is reset. If this message is displayed constantly, it usually indicates a hardware problem.

MK5(d): New serial state=n

Hardware has interrupted the software. It displays the state that the hardware is reporting.

MK5(d): DCD is down.

If the interrupt indicates that the state of carrier has changed, one of these messages is displayed to indicate the current state of DCD.

MK5(d): DCD is up.

Debug Serial Interface for SMDS Encapsulation

When encapsulation is set to SMDS, the debug serial interface command displays SMDS packets that are sent and received, and any error messages resulting from SMDS packet transmission. The error messages that the debug serial interface command can generate for SMDS follow. The following message indicates that a new protocol requested SMDS to encapsulate the data for transmission. SMDS is not yet able to encapsulate the protocol. SMDS: Error on Serial 0, encapsulation bad protocol = x

The following message indicates that SMDS was asked to encapsulate a packet, but no corresponding destination E.164 SMDS address was found in any of the static SMDS tables or in the ARP tables: SMDS send: Error in encapsulation, no hardware address, type = x


DB-1985


The following message indicates that a protocol such as Connectionless Network Service (CLNS) or IP has been enabled on an SMDS interface, but the corresponding multicast addresses have not been configured. The n variable displays the link type for which encapsulation was requested. SMDS: Send, Error in encapsulation, type=n

The following messages can occur when a corrupted packet is received on an SMDS interface. The router expected x, but received y. SMDS: Invalid packet, Reserved NOT ZERO, x y SMDS: Invalid packet, TAG mismatch x y SMDS: Invalid packet, Bad TRAILER length x y

The following messages can indicate an invalid length for an SMDS packet: SMDS: SMDS: SMDS: SMDS:

Invalid Invalid Invalid Invalid

packet, packet, packet, packet,

Bad Bad Bad Bad

BA length x header extension length x header extension type x header extension value x

The following messages are displayed when the debug serial interface command is enabled: Interface Serial 0 Sending SMDS L3 packet: SMDS: dgsize:x type:0xn src:y dst:z

If the debug serial interface command is enabled, the following message can be displayed when a packet is received on an SMDS interface, but the destination SMDS address does not match any on that interface: SMDS: Packet n, not addressed to us


DB-1986

May 2008

Debug Commands debug serial lead-transition

debug serial lead-transition To activate the leads status transition debug capability for all capable ports, use the debug serial lead-transition command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug serial lead-transition no debug serial lead-transition

Syntax Description


Defaults

Debugging is not turned on.

Command Modes

Privileged EXEC

Command History

Release

Modification

Release 12.2(15)ZJ

This command was introduced on the following platforms: Cisco 2610XM, Cisco 2611XM, Cisco 2620XM, Cisco 2621XM, Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745 routers.

Release 12.3(2)T


12.2SX


Usage Guidelines

Caution

Examples

To control which port is to be reported and therefore reduce the risk of flooding the console screen with debug information, enter the debug condition interface serial slot/port command after using the debug serial lead-transition command to set the condition.

To avoid having the debug message flood the console screen with debug information, use these commands only when traffic on the IP network is low, so other activity on the system is not adversely affected.

The following example shows the serial control leads reported for slot 1, port 1: Router# debug serial lead-transition Router# debug condition interface serial 1/1 *Mar *Mar

1 00:17:15.040:slot(1) Port(1):DSR/DTR is Deasserted 1 00:17:15.040:slot(1) Port(1):CTS/RTS is Deasserted

*Mar

1 00:17:47.955:slot(1) Port(1):DCD/Local Loop is Deasserted


DB-1987

Debug Commands debug serial lead-transition

*Mar *Mar

1 00:17:47.955:slot(1) Port(1):DSR/DTR is Deasserted 1 00:17:47.955:slot(1) Port(1):CTS/RTS is Deasserted

Router# no shut down serial 1/1 *Mar *Mar

1 00:16:52.298:slot(1) Port(1):DSR/DTR is Asserted 1 00:16:52.298:slot(1) Port(1):CTS/RTS is Asserted

*Mar *Mar *Mar

1 00:16:31.648:slot(1) Port(1):DCD/Local Loop is Asserted 1 00:16:31.648:slot(1) Port(1):DSR/DTR is Asserted 1 00:16:31.648:slot(1) Port(1):CTS/RTS is Asserted

Table 312 describes significant fields shown in the displays. Table 312

Related Commands

debug serial lead-transition Field Descriptions

Field

Description

DSR/DTR is Asserted/Deasserted

The DSR or DTE signal is activated or inactivated.

CTS/RTS is Asserted/Deasserted

The CTS or RTS signal is activated or inactivated.

DCD/Local Loop is Asserted/Deasserted

The DCD or Local Loopback signal is activated or inactivated.

Command

Description

debug condition interface serial

Enables conditional debugging on a serial interface.


DB-1988

May 2008

Debug Commands debug serial packet

debug serial packet To display more detailed serial interface debugging information than you can obtain using the debug serial interface command, use the debug serial packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug serial packet no debug serial packet

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug serial packet command generates output that is dependent on the type of serial interface and the encapsulation running on that interface. The hardware platform also can impact debug serial packet output. The debug serial packet command displays output for only Switched Multimegabit Data Service (SMDS) encapsulations.

Examples

The following is sample output from the debug serial packet command when SMDS is enabled on the interface: Router# debug serial packet Interface Serial2 Sending SMDS L3 packet: SMDS Header: Id: 00 RSVD: 00 BEtag: EC Basize: 0044 Dest:E18009999999FFFF Src:C12015804721FFFF Xh:04030000030001000000000000000000 SMDS LLC: AA AA 03 00 00 00 80 38 SMDS Data: E1 19 01 00 00 80 00 00 0C 00 38 1F 00 0A 00 80 00 00 0C 01 2B 71 SMDS Data: 06 01 01 0F 1E 24 00 EC 00 44 00 02 00 00 83 6C 7D 00 00 00 00 00 SMDS Trailer: RSVD: 00 BEtag: EC Length: 0044

As the output shows, when encapsulation is set to SMDS, the debug serial packet command displays the entire SMDS header (in hexadecimal notation), and some payload data on transmit or receive. This information is useful only when you have an understanding of the SMDS protocol. The first line of the output indicates either Sending or Receiving.


DB-1989

Debug Commands debug service-module

debug service-module To display debugging information that monitors the detection and clearing of network alarms on the integrated channel service unit/data service unit (CSU/DSU) modules, use the debug service-module command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug service-module no debug service-module

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use this command to enable and disable debug logging for the serial 0 and serial 1 interfaces when an integrated CSU/DSU is present. This command enables debugging on all interfaces. Network alarm status can also be viewed through the use of the show service-module command.

Note

Examples

The debug output varies depending on the type of service module installed in the router.

The following is sample output from the debug service-module command: Router# debug service-module SERVICE_MODULE(1): SERVICE_MODULE(1): SERVICE_MODULE(0): SERVICE_MODULE(0): SERVICE_MODULE(0):

loss of signal ended after duration 00:05:36 oos/oof ended after duration 01:05:14 Unit has no clock detects loss of signal loss of signal ended after duration 00:00:33


DB-1990

May 2008

Debug Commands debug sgbp dial-bids

debug sgbp dial-bids To display large-scale dial-out negotiations between the primary network access server (NAS) and alternate NASs, use the debug sgbp dial-bids command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sgbp dial-bids no debug sgbp dial-bids

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use this command only when the sgbp dial-bids command has been configured.

Examples

The following is sample output from the debug sgbp dial-bids command: Router# debug sgbp dial-bids *Jan 1 00:25:03.643: SGBP-RES: New bid add request: 4B0 8 2 1 DAC0 1 1 This indicates a new dialout bid has started. *Jan 1 00:25:03.643: SGBP-RES: Sent Discover message to ID 7B09B71E 49 bytes The bid request has been sent. *Jan 1 00:25:03.647: SGBP-RES: Received Message of 49 length: *Jan 1 00:25:03.647: SGBP-RES: header 5 30 0 31 2 0 0 2D 0 0 0 0 0 0 0 3 0 0 0 1 1E AF 3A 41 7B 9 B7 1E 3 2 C 6 0 0 DA C0 D 4 0 0 E 3 1 F 3 1 *Jan 1 00:25:03.647: *Jan 1 00:25:03.647: SGBP RES: Scan: Message type: Offer *Jan 1 00:25:03.647: SGBP RES: Scan: Len is 45 *Jan 1 00:25:03.647: SGBP RES: Scan: Transaction ID: 3 *Jan 1 00:25:03.647: SGBP RES: Scan: Message ID: 1 *Jan 1 00:25:03.647: SGBP RES: Scan: Client ID: 1EAF3A41 *Jan 1 00:25:03.651: SGBP RES: Scan: Server ID: 7B09B71E *Jan 1 00:25:03.651: SGBP RES: Scan: Resource type 8 length 21 *Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port Media type: ISDN *Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port Min BW: 56000 *Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port Num Links: 0 *Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port User class: 1 *Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port Priority: 1 *Jan 1 00:25:03.651: SGBP-RES: received 45 length Offer packet *Jan 1 00:25:03.651: SGBP-RES: Offer from 7B09B71E for Transaction 3 accepted *Jan 1 00:25:03.651: SGBP RES: Server is uncongested. Immediate win An alternate network access server has responded and won the bid. *Jan 1 00:25:03.651: SGBP-RES: Bid Succeeded handle 7B09B71E Server-id 4B0 *Jan 1 00:25:03.651: SGBP-RES: Sent Dial-Req message to ID 7B09B71E 66 bytes The primary network access server has asked the alternate server to dial. *Jan 1 00:25:04.651: SGBP-RES: QScan: Purging entry *Jan 1 00:25:04.651: SGBP-RES: deleting entry 6112E204 1EAF3A41 from list...

8

15

B


DB-1991

Debug Commands debug sgbp error

debug sgbp error To display debugging messages about routing problems between members of a stack group, use the debug sgbp error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sgbp error no debug sgbp error

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.2(9)


12.2(33)SRA


12.2SX


Usage Guidelines

Note

Examples

Enter the debug sgbp error command to enable the display of debugging messages about routing problems between members of a stack group.

In unusual cases you may see debugging messages that are not documented on this command reference page. These debugging messages are intended for expert diagnostic interpretation by the Cisco Technical Assistance Center (TAC).

One common configuration error is setting a source IP address for a stack member that does not match the locally defined IP address for the same stack member. The following debugging output shows the error message that results from this misconfiguration: Systema# debug sgbp error %SGBP-7-DIFFERENT - systemb's addr 10.1.1.2 is different from hello's addr 10.3.4.5

This error means that the source IP address of the Stack Group Bidding Protocol (SGBP) hello message received from systemb does not match the IP address configured locally for systemb (through the sgbp member command). Correct this configuration error by going to systemb and checking for multiple interfaces by which the SGBP hello can send the message. Another common error message is: Systema# debug sgbp error %SGBP-7-MISCONF, Possible misconfigured member routerk (10.1.1.6)


DB-1992

May 2008

Debug Commands debug sgbp error

This error message means that routerk is not defined locally, but is defined on another stack member. Correct this configuration error by defining routerk across all members of the stack group using the sgbp member command. The following error message indicates that an SGBP peer is leaving the stack group: Systema# debug sgbp error %SGBP-7-LEAVING:Member systemc leaving group stack1

This error message indicates that the peer systemc is leaving the stack group. Systemc could be leaving the stack group intentionally, or a connectivity problem may exist. The following error message indicates that an SGBP event was detected from an unknown peer: Systema# debug sgbp error %SGBP-7-UNKNOWPEER:Event 0x10 from peer at 172.21.54.3

An SGBP event came from a network host that was not recognizable as an SGBP peer. Check to see if a network media error could have corrupted the address, or if peer equipment is malfunctioning to generate corrupted packets. Depending on the network topology and firewall of your network, SGBP packets from a nonpeer host could indicate probing and attempts to breach security.

Note

Related Commands

If there is a chance your network is under attack, obtain knowledgeable assistance from TAC.

Command

Description

debug sgbp hellos

Displays debugging messages for authentication between stack group members.

sgbp group

Defines a named stack group and makes this router a member of that stack group.

sgbp member

Specifies the hostname and IP address of a router or access server that is a peer member of a stack group.

show sgbp

Displays the status of the stack group members.

username

Establishes a username-based authentication system.


DB-1993

Debug Commands debug sgbp hellos

debug sgbp hellos To display debugging messages for authentication between stack members, use the debug sgbp hellos command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sgbp hellos no debug sgbp hellos

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.2(9)


12.2(33)SRA


12.2SX


Usage Guidelines

Note

Examples

Use the debug sgbp hellos command to enable the display of debugging messages for authentication between routers configured as members of a stack group.

In unusual cases you may see debugging messages that are not documented on this command reference page. These debugging messages are intended for expert diagnostic interpretation by the Cisco Technical Assistance Center (TAC).

The following output from the debug sgbp hellos command shows systema sending a successful Challenge Handshake Authentication Protocol (CHAP) challenge to and receiving a response from systemb. Similarly, systemb sends out a challenge and receives a response from systema. systema# debug sgbp hellos %SGBP-7-CHALLENGE: Send Hello Challenge to systemb group stack1 %SGBP-7-CHALLENGED: Hello Challenge message from member systemb (10.1.1.2) %SGBP-7-RESPONSE: Send Hello Response to systemb group stack1 %SGBP-7-CHALLENGE: Send Hello Challenge to systemb group stack1 %SGBP-7-RESPONDED: Hello Response message from member systemb (10.1.1.2) %SGBP-7-AUTHOK: Send Hello Authentication OK to member systemb (10.1.1.2) %SGBP-7-INFO: Addr = 10.1.1.2 Reference = 0xC347DF7 %SGBP-5-ARRIVING: New peer event for member systemb

This debug output is self-explanatory. If authentication fails, you may see one of the following messages in your debug output: %SGBP-7-AUTHFAILED - Member systemb failed authentication


DB-1994

May 2008

Debug Commands debug sgbp hellos

This error message means that the remote systemb password for the stack group does not match the password defined on systema. To correct this error, make sure that both systema and systemb have the same password defined using the username command. %SGBP-7-NORESP -Fail to respond to systemb group stack1, may not have password.

This error message means that systema does not have a username or password defined. To correct this error, define a common group password across all stack members using the username command.

Related Commands

Command

Description

debug sgbp error

Displays debugging messages about routing problems between members of a stack group.

sgbp group

Defines a named stack group and makes this router a member of that stack group.

sgbp member

Specifies the hostname and IP address of a router or access server that is a peer member of a stack group.

show sgbp

Displays the status of the stack group members.

username

Establishes a username-based authentication system.


DB-1995

Debug Commands debug sgcp errors

debug sgcp errors To debug Simple Gateway Control Protocol (SGCP) errors, use the debug sgcp errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sgcp errors [endpoint string] no debug sgcp errors

Syntax Description

endpoint string

(Optional) Specifies the endpoint string if you want to debug SGCP errors for a specific endpoint. On the Cisco MC3810 router, the endpoint string syntax takes the following forms: •

DS1 endpoint: DS1-slot/port

•

POTS endpoint: aaln/slot/port

On the Cisco 3600 router, the endpoint string syntax takes the following forms: •

DS1 endpoint: slot/subunit/DS1-ds1 number/ds0 number

•

POTS endpoint: aaln/slot/subunit/port

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T

This command was introduced on the Cisco AS5300 access server in a private release that was not generally available.

12.0(7)XK

Support for this command was extended to the Cisco MC3810 and the Cisco 3600 series routers (except for the Cisco 3620). Also, the endpoint keyword was added.

12.2SX


Examples

The following example shows the debugging of SGCP errors being enabled: Router# debug sgcp errors Simple Gateway Control Protocol errors debugging is on no errors since call went through successfully.


DB-1996

May 2008

Debug Commands debug sgcp errors

The following example shows a debug trace for SGCP errors on a specific endpoint: Router# debug sgcp errors endpoint DS1-0/1 End point name for error debug:DS1-0/1 (1) 00:08:41:DS1 = 0, DS0 = 1 00:08:41:Call record found 00:08:41:Enable error end point debug for (DS1-0/1)

Related Commands

Command

Description

debug rtpspi all


debug rtpspi errors


debug rtpspi inout




debug sgcp events

Debugs SGCP events.

debug sgcp packet


debug vtsp send-nse



DB-1997

Debug Commands debug sgcp events

debug sgcp events To debug Simple Gateway Control Protocol (SGCP) events, use the debug sgcp events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sgcp events [endpoint string] no debug sgcp events

Syntax Description

endpoint string

(Optional) Specifies the endpoint string if you want to debug SGCP errors for a specific endpoint. On the Cisco MC3810 router, the endpoint string syntax takes the following forms: •


•


On the Cisco 3600 router, the endpoint string syntax takes the following forms: •


•


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T

This command was introduced on the Cisco AS5300 access server in a private release that was not generally available.

12.0(7)XK

Support for this command was extended to the Cisco MC3810 and the Cisco 3600 series routers (except for the Cisco 3620 router). Also, the endpoint keyword was added.

12.2SX


Examples

The following example shows a debug trace for SGCP events on a specific endpoint: Router# debug sgcp events endpoint DS1-0/1 End point name for event debug:DS1-0/1 (1) 00:08:54:DS1 = 0, DS0 = 1 00:08:54:Call record found 00:08:54:Enable event end point debug for (DS1-0/1)


DB-1998

May 2008


The following example shows a debug trace for all SGCP events on a gateway: Router# debug sgcp events *Mar

1 01:13:31.035:callp :19196BC, state :0, call ID :-1, event :23

*Mar 1 01:13:31.035:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msg NTFY send to ipaddr=1092E01 port=2427 *Mar 1 01:13:31.039:Push msg into SGCP wait ack queue* (1)[25] *Mar 1 01:13:31.039:Timed Out interval [1]:(2000) *Mar 1 01:13:31.039:Timed Out interval [1]:(2000)(0):E[25] *Mar 1 01:13:31.075:Removing msg : NTFY 25 ds1-1/13@mc1 SGCP 1.1 X:358258758 O:hd *Mar

1 01:13:31.075:Unqueue msg from SGCP wait ack q** (0)[25]DS1 = 1, DS0 = 13

*Mar *Mar

1 01:13:31.091:callp :19196BC, vdbptr :1964EEC, state :1 1 01:13:31.091:Checking ack (trans ID 237740140) :

*Mar *Mar

1 01:13:31.091:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8 1 01:13:31.091:is_capability_ok:supported signal=0x426C079C, signal2=0x80003, event=0x6003421F, event2=0x3FD requested signal=0x0, signal2=0x0, event=0x20000004, event2=0xC *Mar 1 01:13:31.091:Same digit map is download (ds1-1/13@mc1) *Mar

1 01:13:31.091:R:requested trans_id (237740140)

*Mar *Mar

1 01:13:31.091:process_signal_ev:seizure possible=1, signal mask=0x4, mask2=0x0 1 01:13:32.405:SGCP Session Appl:ignore CCAPI event 10

*Mar

1 01:13:32.489:callp :19196BC, state :1, call ID :16, event :9

*Mar

1 01:13:32.610:SGCP Session Appl:ignore CCAPI event 10

*Mar


*Mar


*Mar


*Mar


*Mar


*Mar


*Mar


*Mar


*Mar


*Mar


*Mar


*Mar


*Mar



DB-1999


*Mar


*Mar


*Mar 1 01:13:33.742:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msg NTFY send to ipaddr=1092E01 port=2427 *Mar 1 01:13:33.742:Push msg into SGCP wait ack queue* (1)[26] *Mar 1 01:13:33.742:Timed Out interval [1]:(2000) *Mar 1 01:13:33.742:Timed Out interval [1]:(2000)(0):E[26] *Mar 1 01:13:33.786:Removing msg : NTFY 26 ds1-1/13@mc1 SGCP 1.1 X:440842371 O:k0, 4081037, s0 *Mar


*Mar *Mar


*Mar *Mar

1 01:13:33.802:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8 1 01:13:33.802:is_capability_ok:supported signal=0x426C079C, signal2=0x80003, event=0x6003421F, event2=0x3FD requested signal=0x0, signal2=0x0, event=0x4, event2=0x0 *Mar 1 01:13:33.802:R:requested trans_id (698549528) *Mar *Mar

1 01:13:33.802:set_up_voip_call_leg:peer_addr=0, peer_port=0. 1 01:13:33.806:call_setting_crcx:Enter CallProceeding state rc = 0, call_id=16

*Mar


*Mar 1 01:13:33.810:callp :1AF5798, state :2, call ID :17, event :8 call_pre_bridge! *Mar *Mar

1 01:13:33.810:send_oc_create_ack:seizure_possiblle=1, ack-lready-sent=0, ack_send=0 1 01:13:33.814:callp :1AF5798, state :4, call ID :17, event :28

*Mar *Mar

1 01:13:33.814:Call Connect:Raw Msg ptr=0x1995360, no-offhook=0; call-id=17 1 01:13:33.814:SGCP Session Appl:ignore CCAPI event 37

*Mar 1 01:13:33.947:callp :19196BC, state :5, call ID :16, event :32 process_nse_on_orig DS1 = 1, DS0 = 13 *Mar *Mar


*Mar *Mar

1 01:13:34.007:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8 1 01:13:34.007:is_capability_ok:supported signal=0x426C079C, signal2=0x80003, event=0x6003421F, event2=0x3FD requested signal=0x0, signal2=0x0, event=0x4, event2=0x0 *Mar 1 01:13:34.007:R:requested trans_id (123764791) *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1

01:13:34.007:process_signal_ev:seizure possible=1, signal mask=0x0, mask2=0x0 01:13:34.007:modify_connection:echo_cancel=1. 01:13:34.007:modify_connection:vad=0. 01:13:34.007:modify_connection:peer_addr=6000001, peer_port=0->16500. 01:13:34.007:modify_connection:conn_mode=2. 01:13:34.011:callp :19196BC, state :5, call ID :16, event :31

*Mar 1 01:13:34.011:callp :1AF5798, state :5, call ID :17, event :31 process_nse_event


DB-2000

May 2008


*Mar


*Mar 1 01:13:34.051:call_id=16, ignore_ccapi_ev:ignore 19 for state 5 DS1 = 1, DS0 = 13 *Mar *Mar


*Mar *Mar

1 01:13:39.497:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8 1 01:13:39.497:is_capability_ok:supported signal=0x426C079C, signal2=0x80003, event=0x6003421F, event2=0x3FD requested signal=0x8, signal2=0x0, event=0x4, event2=0x0 *Mar 1 01:13:39.497:R:requested trans_id (553892443) *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1

01:13:39.497:process_signal_ev:seizure possible=1, signal mask=0x0, mask2=0x0 01:13:39.497:modify_connection:echo_cancel=1. 01:13:39.497:modify_connection:vad=0. 01:13:39.497:modify_connection:peer_addr=6000001, peer_port=16500->16500. 01:13:39.497:modify_connection:conn_mode=3. 01:13:39.497:callp :19196BC, state :5, call ID :16, event :31

*Mar

1 01:13:39.501:callp :1AF5798, state :5, call ID :17, event :31

*Mar 1 01:14:01.168:Removing ack (trans ID 237740140) : 200 237740140 OK

*Mar 1 01:14:03.883:Removing ack (trans ID 698549528) : 200 698549528 OK I:7 v=0 c=IN IP4 5.0.0.1 m=audio 16400 RTP/AVP 0

*Mar 1 01:14:04.087:Removing ack (trans ID 123764791) : 200 123764791 OK I:7 v=0 c=IN IP4 5.0.0.1 m=audio 16400 RTP/AVP 0

*Mar 1 01:14:09.573:Removing ack (trans ID 553892443) : 200 553892443 OK I:7 v=0 c=IN IP4 5.0.0.1 m=audio 16400 RTP/AVP 0 *Mar


*Mar 1 01:14:48.091:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msg NTFY send to ipaddr=1092E01 port=2427 *Mar 1 01:14:48.091:Push msg into SGCP wait ack queue* (1)[27] *Mar 1 01:14:48.091:Timed Out interval [1]:(2000) *Mar 1 01:14:48.091:Timed Out interval [1]:(2000)(0):E[27] *Mar 1 01:14:48.128:Removing msg :


DB-2001


NTFY 27 ds1-1/13@mc1 SGCP 1.1 X:97849341 O:hu *Mar


*Mar *Mar


*Mar *Mar

1 01:14:48.212:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8 1 01:14:48.212:is_capability_ok:supported signal=0x426C079C, signal2=0x80003, event=0x6003421F, event2=0x3FD requested signal=0x4, signal2=0x0, event=0x0, event2=0x0 *Mar 1 01:14:48.212:delete_call:callp:19196BC, call ID:16 *Mar 1 01:14:48.212:sgcp delete_call:Setting disconnect_by_dlcx to 1 *Mar 1 01:14:48.216:callp :1AF5798, state :6, call ID :17, event :29 *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1

01:14:48.216:Call disconnect:Raw Msg ptr = 0x0, call-id=17 01:14:48.216:disconnect_call_leg O.K. call_id=17 01:14:48.216:SGCP:Call disconnect:No need to send onhook 01:14:48.216:Call disconnect:Raw Msg ptr = 0x19953B0, call-id=16 01:14:48.216:disconnect_call_leg O.K. call_id=16 01:14:48.220:callp :1AF5798, state :7, call ID :17, event :13

*Mar

1 01:14:48.220:Processing DLCX signal request :4, 0, 0

*Mar 13

1 01:14:48.220:call_disconnected:call_id=17, peer 16 is not idle yet.DS1 = 1, DS0 =

*Mar *Mar


*Mar *Mar

1 01:14:48.272:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8 1 01:14:48.272:is_capability_ok:supported signal=0x426C079C, signal2=0x80003, event=0x6003421F, event2=0x3FD requested signal=0x0, signal2=0x0, event=0x8, event2=0x0 *Mar 1 01:14:48.272:R:requested trans_id (75540355) *Mar *Mar

1 01:14:48.272:process_signal_ev:seizure possible=1, signal mask=0x4, mask2=0x0 1 01:14:49.043:callp :19196BC, state :7, call ID :16, event :27

*Mar *Mar

1 01:14:49.043:process_call_feature:Onhook event 1 01:14:49.043:callp :19196BC, state :7, call ID :16, event :13

*Mar 1 01:15:18.288:Removing ack (trans ID 79307869) : 250 79307869 OK *Mar 1 01:15:18.344:Removing ack (trans ID 75540355) : 200 75540355 OK


DB-2002

May 2008


Related Commands

Command

Description

debug rtpspi all


debug rtpspi errors


debug rtpspi inout




debug sgcp errors

Debugs SGCP errors.

debug sgcp packet


debug vtsp send-nse



DB-2003

Debug Commands debug sgcp packet

debug sgcp packet To debug the Simple Gateway Control Protocol (SGCP), use the debug sgcp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sgcp packet [endpoint string] no debug sgcp packet

Syntax Description

endpoint string

(Optional) Specifies the endpoint string if you want to debug SGCP errors for a specific endpoint. On the Cisco MC3810, the endpoint string syntax takes the following forms: •


•


On the Cisco 3600, the endpoint string syntax takes the following forms: •


•


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T

This command was introduced on the Cisco AS5300 in a private release that was not generally available.

12.0(7)XK

Support for this command was extended to the Cisco MC3810 and the Cisco 3600 series routers (except for the Cisco 3620). Also, the endpoint keyword was added.

12.2SX


Examples

The following example shows a debug trace for SGCP packets on a specific endpoint: Router# debug sgcp packet endpoint DS1-0/1 End point name for packet debug:DS1-0/1 (1) 00:08:14:DS1 = 0, DS0 = 1 00:08:14:Enable packet end point debug for (DS1-0/1)


DB-2004

May 2008


The following example shows a debug trace for all SGCP packets on a gateway: Router# debug sgcp packet *Mar 1 01:07:45.204:SUCCESS:Request ID string building is OK *Mar 1 01:07:45.204:SUCCESS:Building SGCP Parameter lines is OK *Mar 1 01:07:45.204:SUCCESS:SGCP message building OK *Mar 1 01:07:45.204:SUCCESS:END of building *Mar 1 01:07:45.204:SGCP Packet sent ---> NTFY 22 ds1-1/13@mc1 SGCP 1.1 X:550092018 O:hd 200 180932866 OK NTFY 23 ds1-1/13@mc1 SGCP 1.1 X:362716780 O:k0, 4081037, s0 200 938694984 OK I:6 v=0 c=IN IP4 5.0.0.1 m=audio 16538 RTP/AVP 0 200 779665338 OK I:6 v=0 c=IN IP4 5.0.0.1 m=audio 16538 RTP/AVP 0


DB-2006

May 2008


200 177780432 OK I:6 v=0 c=IN IP4 5.0.0.1 m=audio 16538 RTP/AVP 0 NTFY 24 ds1-1/13@mc1 SGCP 1.1 X:519556004 O:hu 250 865375036 OK 200 254959796 OK

Related Commands

Command

Description

debug rtpspi all


debug rtpspi errors


debug rtpspi inout




debug sgcp errors

Debugs SGCP errors.

debug sgcp events

Debugs SGCP events.

debug vtsp send-nse



DB-2008

May 2008

Debug Commands debug sgcp

debug sgcp To debug the Simple Gateway Control Protocol (SGCP), use the debug sgcp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sgcp {errors | events | packet} no debug sgcp {errors | events | packet}

Syntax Description

errors

Displays debug information about SGCP errors.

events

Displays debug information about SGCP events.

packet

Displays debug information about SGCP packets.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.0(7)T

Support for this command was extended to the Cisco uBR924 cable access router.

12.2SX


Examples

See the following examples to enable and disable debugging at the specified level: Router# debug sgcp errors Simple Gateway Control Protocol errors debugging is on Router# no debug sgcp errors Simple Gateway Control Protocol errors debugging is off Router# Router# debug sgcp events Simple Gateway Control Protocol events debugging is on Router# no debug sgcp events Simple Gateway Control Protocol events debugging is off Router# Router# debug sgcp packet Simple Gateway Control Protocol packets debugging is on Router# no debug sgcp packet Simple Gateway Control Protocol packets debugging is off


DB-2009

Debug Commands debug sgcp

Router#

Related Commands

Command

Description

sgcp

Starts and allocates resources for the SCGP daemon.


DB-2010

May 2008

Debug Commands debug shared-line

debug shared-line To display debugging information about shared lines on SIP phones, use the debug shared-line command in privileged EXEC mode. To disable debugging messages, use the no form of this command. debug shared-line {all | errors | events | info} no debug shared-line {all | errors | events | info}

Syntax Description

all

Displays all shared-line debugging messages.

errors

Displays shared-line error messages.

events

Displays shared-line event messages

info

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(6th)T


12.2SX


Usage Guidelines

Examples

The following example shows output from the debug presence all command: Router# debug shared-line all

Related Commands

Command

Description

shared-line

Enables a directory number to be shared by multiple SIP phones.

show shared-line

Displays information about shared lines on SIP phones.

show voice register dn Displays all configuration information associated with a specific voice register dn.


DB-2011

Debug Commands debug smrp all

debug smrp all To display information about Simple Multicast Routing Protocol (SMRP) activity, use the debug smrp all privileged EXEC command. The no form of this command disables debugging output. debug smrp all no debug smrp all

Syntax Description


Command History

10.0


12.2(13)T

This command is no longer supported in Cisco IOS Mainline releases or in Technology-based (T-train) releases. It might continue to appear in 12.2S-family releases.

12.2SX


Usage Guidelines

Because the debug smrp all command displays all SMRP debugging output, it is processor intensive and should not be enabled when memory is scarce or in very high traffic situations. For general debugging, use the debug smrp all command and turn off excessive transactions with the no debug smrp transaction command. This combination of commands will display various state changes and events without displaying every transaction packet. For debugging a specific feature such as a routing problem, use the debug smrp route and debug smrp transaction commands to learn if packets are sent and received and which specific routes are affected. The show smrp traffic EXEC command is highly recommended as a troubleshooting method because it displays the SMRP counters. For examples of the type of output you may see, refer to each of the commands listed in the “Related Commands” section.

Related Commands

Command

Description

debug smrp group

Displays information about SMRP group activity.

debug smrp mcache

Displays information about SMRP multicast fast-switching cache entries.

debug smrp neighbor

Displays information about SMRP neighbor activity.

debug smrp port

Displays information about SMRP port activity.

debug smrp route

Displays information about SMRP routing activity.

debug smrp transaction

Displays information about SMRP transactions.


DB-2012

May 2008

Debug Commands debug smrp group

debug smrp group To display information about SMRP group activity, use the debug smrp group privileged EXEC command. The no form of this command disables debugging output. debug smrp group no debug smrp group

Syntax Description


Command History

10.0


12.2(13)T


12.2SX


Usage Guidelines

The debug smrp group command displays information when a group is created or deleted and when a forwarding entry for a group is created, changed, or deleted. For more information, refer to the show smrp group command described in the Cisco IOS AppleTalk and Novell IPX Command Reference.

Examples

The following is sample output from the debug smrp group command showing a port being created and deleted on group AT 20.34. (AT signifies that this is an AppleTalk network group.) Router# debug smrp group SMRP: Group AT 20.34, created on port 20.1 by 20.2 SMRP: Group AT 20.34, deleted on port 20.1

Table 313 lists the messages that may be generated with the debug smrp group command concerning the forwarding table. Table 313

debug smrp group Message Descriptions

Messages

Descriptions

Group , deleted on port

Group entry was deleted from the group table for the specified port.

Group , forward state changed from state to state

State of the group changed. States are join, forward, and leave.

Group , deleted forward entry

Group was deleted from the forwarding table.

Group , created on port by

Group entry was created in the table for the specified port.


DB-2013

Debug Commands debug smrp group

Table 313

debug smrp group Message Descriptions (continued)

Messages

Descriptions

Group , added by to the group

Secondary router has added this group to its group table.

Group , discard join Discard Join Group request if the router is not the primary router on request from , not the local connected network or if it is not the port parent of the route. responsible Group , join request Request to join the group was received. from Group , forward is found

Forward entry for the group was found in the forwarding table.

Group , forward state is already joining, ignored

Request to join the group is in progress, so the second request was discarded.

Group , no forward Forward entry for the group was not found in the forwarding table. found Group , join request Request to join the group was discarded because the parent port is not discarded, fw discarded, fwd available. parent port not operational Group , created forward entry - parent child

Forward entry was created in the forwarding table for the parent and child address.

Group , creator no longer up on

Group creator has not been heard from for a specified time and is deemed no longer available.

Group , pruning duplicate path on

Duplicate path was removed. If we are forwarding and we are a child port, and our port parent address is not pointing to our own port address, we are in a duplicate path.

Group , member no Group member has not been heard from for a specified time and is longer up on deemed no longer available. Group , no more child ports in forward entry

Related Commands

Command

Forward entry for group no longer has any child ports. As a result, the forward entry is no longer necessary.

Description

debug sgbp dial-bids Displays large-scale dial-out negotiations between the primary NAS and alternate NASs.


DB-2014

May 2008

Debug Commands debug smrp mcache

debug smrp mcache To display information about SMRP multicast fast-switching cache entries, use the debug smrp mcache privileged EXEC command. The no form of this command disables debugging output. debug smrp mcache no debug smrp mcache

Syntax Description


Command History

10.0


12.2(13)T


12.2SX


Usage Guidelines

Use the show smrp mcache EXEC command (described in the Cisco IOS AppleTalk and Novell IPX Command Reference to display the entries in the SMRP multicast cache, and use the debug smrp mcache command to learn whether the cache is being populated and invalidated.

Examples

The following is sample output from the debug smrp mcache command. In this example, the cache is created and populated for group AT 11.124. (AT signifies that this is an AppleTalk network group.) Router# debug smrp mcache SMRP: Cache created SMRP: Cache populated for group AT 11.124 mac - 090007400b7c00000c1740d9 net - 001fef7500000014ff020a0a0a SMRP: Forward cache entry created for group AT 11.124 SMRP: Forward cache entry validated for group AT 11.124 SMRP: Forward cache entry invalidated for group AT 11.124 SMRP: Forward cache entry deleted for group AT 11.124


DB-2015

Debug Commands debug smrp mcache

Table 314 lists all the messages that can be generated with the debug smrp mcache command concerning the multicast cache. Table 314

debug smrp mcache Message Descriptions

Messages

Descriptions

Cache populated for group

SMRP packet was received on a parent port that has fast switching enabled. As a result, the cache was created and the MAC and network headers were stored for all child ports that have fast switching enabled. Use the show smrp port appletalk EXEC command with the optional interface type and number to display the switching path.

Cache memory allocated

Memory was allocated for the multicast cache.

Forward cache entry created/deleted for group

Forward cache entry for the group was added to or deleted from the cache.

Forward cache entry validated Forward cache entry is validated and is now ready for fast switching. for group Forward cache entry invalidated for group

Related Commands

Cache entry is invalidated because some change (such as port was shut down) occurred to one of the ports.

Command

Description

debug sgbp dial-bids

Displays large-scale dial-out negotiations between the primary NAS and alternate NASs.


DB-2016

May 2008

Debug Commands debug smrp neighbor

debug smrp neighbor To display information about SMRP neighbor activity, use the debug smrp neighbor privileged EXEC command. The no form of this command disables debugging output. debug smrp neighbor no debug smrp neighbor

Syntax Description


Command History

10.0


12.2(13)T


12.2SX


Usage Guidelines

The debug smrp neighbor command displays information when a neighbor operating state changes. A neighbor is an adjacent router. For more information, refer to the show smrp neighbor EXEC command described in the Cisco IOS AppleTalk and Novell IPX Command Reference.

Examples

The following is sample output from the debug smrp neighbor command. In this example, the neighbor on port 30.02 has changed state from normal operation to secondary operation. Router# debug smrp neighbor SMRP: Neighbor 30.2, state changed from “normal op” to “secondary op”

Table 315 lists all the messages that can be generated with the debug smrp neighbor command concerning the neighbor table. Table 315

debug smrp neighbor Message Descriptions

Messages

Descriptions

Neighbor , state changed from state to state

State of the neighbor changed. States are primary operation, secondary operation, normal operation, primary negotiation, secondary negotiation, and down.

Neighbor , neighbor added/deleted

Neighbor was added to or removed from the neighbor table.

SMRP neighbor up/down

Neighbor is available for service or unavailable.

Neighbor , no longer up

Neighbor is unavailable because it has not been heard from for a specified duration.


DB-2017

Debug Commands debug smrp neighbor

Related Commands

Command

Description




DB-2018

May 2008

Debug Commands debug smrp port

debug smrp port To display information about SMRP port activity, use the debug smrp port privileged EXEC command. The no form of this command disables debugging output. debug smrp port no debug smrp port

Syntax Description


Command History

10.0


12.2(13)T


12.2SX


Usage Guidelines

The debug smrp port command displays information when a port operating state changes. For more information, refer to the show smrp port command described in the Cisco IOS AppleTalk and Novell IPX Command Reference.

Examples

The following is sample output from the debug smrp port command. In this example, port 30.1 has changed state from secondary negative to secondary operation to primary negative: Router# debug smrp port SMRP: Port 30.1, state changed from "secondary neg" to "secondary op" SMRP: Port 30.1, secondary router changed from 0.0 to 30.1 SMRP: Port 30.1, state changed from "secondary op" to "primary neg"

Table 316 lists all the messages that can be generated with the debug smrp port command concerning the port table. Table 316

debug smrp port Message Descriptions

Messages

Descriptions

Port , port created/deleted

Port entry was added to or removed from the port table.

Port , line protocol changed to state

Line protocol for the port is up or down.


DB-2019

Debug Commands debug smrp port

Table 316

debug smrp port Message Descriptions (continued)

Messages

Descriptions

Port , state changed State of the port changed. States are primary operation, from state to state secondary operation, normal operation, primary negotiation, secondary negotiation, and down. Port , primary/secondary router changed from to

Related Commands

Primary or secondary port address of the router changed.

Command

Description




DB-2020

May 2008

Debug Commands debug smrp route

debug smrp route To display information about SMRP routing activity, use the debug smrp route privileged EXEC command. The no form of this command disables debugging output. debug smrp route no debug smrp route

Syntax Description


Command History

10.0


12.2(13)T


12.2SX


Usage Guidelines

For more information, refer to the show smrp route EXEC command described in the Cisco IOS AppleTalk and Novell IPX Command Reference.

Examples

The following is sample output from the debug smrp route command. In this example, poison notification is received from port 30.2. Poison notification is the receipt of a poisoned route on a nonparent port. Router# debug smrp route SMRP: Route AT 20-20, poison notification from 30.2 SMRP: Route AT 30-30, poison notification from 30.2

Table 317 lists all the messages that can be generated with the debug smrp route command concerning the routing table. In Table 317, the term route does not refer to an address but rather to a network range. Table 317

debug smrp route Message Descriptions

Messages

Descriptions

Route address, deleted/created Route entry was removed from or added to the routing table. as local network Route address, from address has invalid distance value

Route entry from the specified address has an incorrect distance value and was ignored.

Route address, unknown route Route entry received from the specified address is bad and was poisoned by address ignored ignored. Route address, created via address - hop number tunnel number

New route entry added to the routing table with the specified number of hops and tunnels.


DB-2021

Debug Commands debug smrp route

Table 317

debug smrp route Message Descriptions (continued)

Messages

Descriptions

Route address, from address overlaps existing route

Route entry received from the specified address overlaps an existing route and was ignored.

Route address, poisoned by address

Route entry has been poisoned by neighbor. Poisoned routes have distance of 255.

Route address, poison notification from address

Poisoned route is received from a nonparent port.

Route address, worsened by parent address

Distance to the route has worsened (become higher), received from the parent neighbor.

Route address, improved via Distance to the route has improved (become lower), received from a address - number -> number neighbor. hop, number -> number tunnel

Related Commands

Route address, switched to address - higher address than address

Tie condition exists, and because this router had the highest network address, it was used to forward the packet.

Route address, parent port changed address -> address

Parent port address change occurred. The parent port address of a physical network segment determines which router should handle Join Group and Leave Group requests.

SMRP bad distance vector

Packet has an invalid distance vector and was ignored.

Route address, has been poisoned

Route has been poisoned. Poisoned routes are purged from the routing table after a specified time.

Command

Description




DB-2022

May 2008

Debug Commands debug smrp transaction

debug smrp transaction To display information about SMRP transactions, use the debug smrp transaction privileged EXEC command. The no form of this command disables debugging output. debug smrp transaction no debug smrp transaction

Syntax Description


Examples

The following is sample output from the debug smrp transaction command. In this example, a secondary node request is sent out to all routers on port 30.1. Router# debug smrp transaction SMRP: SMRP: SMRP: SMRP:

Transaction Transaction Transaction Transaction

for for for for

port port port port

30.1, 30.1, 30.1, 30.1,

secondary secondary secondary secondary

node node node node

request request request request

(seq (seq (seq (seq

8435) 8435) 8435) 8435)

sent sent sent sent

to to to to

all all all all

routers routers routers routers

Table 318 lists all the messages that can be generated with the debug smrp route command. Table 318

debug smrp Transaction Message Descriptions

Messages

Descriptions

Transaction for port address, packet-type command-type (grp/sec number) sent to/received from address

Port message concerning a packet or command was sent to or received from the specified address.

Transaction for group address on port address, (seq number) sent to/received from address

Group message for a specified port was sent to or received from the specified address.

Unrecognized transaction for port address

Unrecognized message was received and ignored by the port.

Discarded incomplete request

Incomplete message was received and ignored.

Response in wrong state in HandleRequest

Message was received with the wrong state and was ignored.

SMRP bad packet type

SMRP packet was received with a bad packet type and was ignored.

Packet discarded, Bad Port ID Packet was received with a bad port ID and was ignored. Packet discarded, Check Packet failed

Related Commands

Packet was received with a failed check packet and was ignored.

Command

Description




DB-2023

Debug Commands debug snasw dlc

debug snasw dlc To display frame information entering and leaving the Systems Network Architecture (SNA) switch in real time to the console, use the debug snasw dlc command in privileged EXEC mode. debug snasw dlc detail

Syntax Description

detail

Defaults

By default, a one-line description of the frame is displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(6)T


12.2(33)SRA


12.2SX


Indicates that in addition to a one-line description of the frame being displayed, an entire hexadecimal dump of the frame will follow.


Examples

The debug snasw dlc command displays the same trace information available via the snasw dlctrace command. The snasw dlctrace command is the preferred method for gathering this trace information because it is written to a capture buffer instead of directly to the console. The debug snasw dlc command should only be used when it is certain that the output will not cause excessive data to be output to the console.

The following shows sample output from the debug snasw dlc command: Router# debug snasw dlc Sequence Number Link 343 344 345 346 347 348 349

MVSD MVSD @I000002 MVSD @I000002 @I000002 @I000002

Size of ISR/ SNA BTU HPR Description of frame In Out Out Out In In In

sz:134 sz:12 sz:18 sz:273 sz:9 sz:12 sz:29

ISR ISR ISR ISR ISR ISR ISR

fmh5 DLUR Rq ActPU NETA.APPNRA29 +Rsp IPM slctd nws:0008 Rq ActPU fmh5 TOPOLOGY UPDATE +Rsp Data +Rsp IPM slctd nws:0002 +Rsp ActPU


DB-2024

May 2008

Debug Commands debug snasw dlc

350 351 352 353 354

Related Commands

MVSD MVSD MVSD MVSD @I000002

Out In In Out Out

sz:115 sz:12 sz:88 sz:108 sz:27

ISR ISR ISR ISR ISR

fmh5 DLUR +Rsp ActPU +Rsp IPM slctd nws:0007 fmh5 DLUR Rq ActLU NETA.MARTLU1 fmh5 REGISTER Rq ActLU NETA.MARTLU1

Command

Description

snasw dlcfilter

Filters frames traced by the snasw dlctrace or debug snasw dlc command.

snasw dlctrace

Captures trace frames entering and leaving the SNA Switching Services feature.


DB-2025

Debug Commands debug snasw ips

debug snasw ips To display internal signal information between the Systems Network Architecture (SNA) switch and the console in real time, use the debug snasw ips command in privileged EXEC mode. debug snasw dlc

Syntax Description


Defaults

By default, a one-line description of the interprocess signal is displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(6)T


12.2(33)SRA


12.2SX



Examples

The debug snasw ips command displays the same trace information available via the snasw ipstrace command. Output from this debug command can be large. The snasw ipstrace command is the preferred method for gathering this trace information because it is written to a capture buffer instead of directly to the console. The debug snasw ips command should only be used when it is certain that the output will not cause excessive data to be output to the console. The debug snasw dlc command displays the same trace information available via the snasw dlctrace command.

The following is an example of the debug snasw ips command output: Router# debug snasw ips Sequence Number Signal Name 11257 11258 11259 11260 11261 11262 11263 11264

: : : : : : : :

Sending Process

Receiving Process

Queue

DEALLOCATE_RCB : --(0) -> RM(2130000) Q 4 RCB_DEALLOCATED : RM(2130000) -> PS(22E0000) Q 2 RCB_DEALLOCATED : --(0) -> PS(22E0000) Q 2 VERB_SIGNAL : PS(22E0000) -> DR(20F0000) Q 2 FREE_SESSION : --(0) -> RM(2130000) Q 2 BRACKET_FREED : RM(2130000) -> HS(22FB0001) Q 2 BRACKET_FREED : --(0) -> HS(22FB0001) Q 2 VERB_SIGNAL : --(0) -> DR(20F0000) Q 2


DB-2026

May 2008

Debug Commands debug snasw ips

11265 : DLC_MU : DLC(2340000) -> PC(22DD0001) Q 2 11266 : DLC_MU : --(0) -> PC(22DD0001) Q 2

Related Commands

Command

Description

snasw ipstrace

Captures interprocess signal information between Switching Services components.


DB-2027

Debug Commands debug snmp bulkstat

debug snmp bulkstat To enable debugging messages for the SNMP Bulk Statistics feature, use the debug snmp bulkstat command in privileged EXEC mode. To disable debugging messages for this feature, use the no form of this command. debug snmp bulkstat no debug snmp bulkstat

Syntax Description


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.0(24)S


12.3(2)T


12.2(25)S


12.2(33)SRA


12.2(33)SXH


12.2SX


12.2(33)SB


Usage Guidelines

This command is intended primarily for Cisco support personnel. Debugging output for the Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature) includes messages for data collection, local file generation, and transfer attempts.

Examples

In the following example, debugging command output is enabled for the Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature). Note that the references to a VFile indicate a local bulk statistics file, usually followed by the filename. The filename uses the format specified-filename_device-name_date_time-stamp. Router# debug snmp bulkstat 00:17:38:BULKSTAT-DC:Poll timer fired for ifmib 00:17:38:BULKSTAT-DC:In pollDataGroup 00:17:38:BULKSTAT-DC:creating new file vfile:IfMIB_objects_ios108_030307_101119739 00:17:38:BULKSTAT-DC:Too small state buffer for ifmib 102 00:17:38:BULKSTAT-DC:Increased buffer state to 1024 00:17:38:BULKSTAT-DC:Interface type data group 00:17:38:BULKSTAT-DC:polling done 00:18:38:BULKSTAT-DC:Poll timer fired for ifmib


DB-2028

May 2008


00:18:38:BULKSTAT-DC:In pollDataGroup 00:18:38:BULKSTAT-DC:Interface type data group 00:18:38:BULKSTAT-DC:polling done 00:19:26: BULKSTAT-DC:Collection timer fired for IfMIB_objects 00:19:26:BULKSTAT-TP:Transfer request for vfile:IfMIB_objects_ios108_030307_101119739 00:19:30:BULKSTAT-TP:written vfile IfMIB_objects_ios108_030307_101119739 00:19:30:BULKSTAT-TP:retained vfile vfile:IfMIB_objects_ios108_030307_101119739 00:19:38:BULKSTAT-DC:Poll timer fired for ifmib 00:19:38:BULKSTAT-DC:In pollDataGroup 00:19:38:BULKSTAT-DC:creating new file vfile:IfMIB_objects_ios108_030307_101319739 00:19:38:BULKSTAT-DC:Interface type data group 00:19:38:BULKSTAT-DC:polling done 00:20:38:BULKSTAT-DC:Poll timer fired for ifmib 00:20:38:BULKSTAT-DC:In pollDataGroup 00:20:38:BULKSTAT-DC:Interface type data group 00:20:38:BULKSTAT-DC:polling done 00:21:38:BULKSTAT-DC:Poll timer fired for ifmib 00:21:38:BULKSTAT-DC:In pollDataGroup 00:21:38:BULKSTAT-DC:Interface type data group 00:21:38:BULKSTAT-DC:polling done 00:22:26: BULKSTAT-DC:Collection timer fired for IfMIB_objects 00:22:26:BULKSTAT-TP:Transfer request for vfile:IfMIB_objects_ios108_030307_101319739 00:22:26:BULKSTAT-TP:written vfile IfMIB_objects_ios108_030307_101319739 00:22:26:BULKSTAT-TP:retained vfile vfile:IfMIB_objects_ios108_030307_101319739 00:22:38:BULKSTAT-DC:Poll timer fired for ifmib 00:22:38:BULKSTAT-DC:In pollDataGroup 00:22:38:BULKSTAT-DC:creating new file vfile:IfMIB_objects_ios108_030307_101619739 00:22:38:BULKSTAT-DC:Interface type data group 00:22:38:BULKSTAT-DC:polling done 00:23:38:BULKSTAT-DC:Poll timer fired for ifmib 00:23:38:BULKSTAT-DC:In pollDataGroup 00:23:38:BULKSTAT-DC:Interface type data group 00:23:38:BULKSTAT-DC:polling done 00:24:38:BULKSTAT-DC:Poll timer fired for ifmib 00:24:38:BULKSTAT-DC:In pollDataGroup 00:24:38:BULKSTAT-DC:Interface type data group 00:24:38:BULKSTAT-DC:polling done 00:25:26: BULKSTAT-DC:Collection timer fired for IfMIB_objects 00:25:26:BULKSTAT-TP:Transfer request for vfile:IfMIB_objects_ios108_030307_101619739 00:25:26:BULKSTAT-TP:written vfile IfMIB_objects_ios108_030307_101619739 00:25:26:BULKSTAT-TP:retained vfile vfile:IfMIB_objects_ios108_030307_101619739 00:25:38:BULKSTAT-DC:Poll timer fired for ifmib 00:25:38:BULKSTAT-DC:In pollDataGroup 00:25:38:BULKSTAT-DC:creating new file vfile:IfMIB_objects_ios108_030307_101919739 00:25:38:BULKSTAT-DC:Interface type data group 00:25:38:BULKSTAT-DC:polling done 00:26:38:BULKSTAT-DC:Poll timer fired for ifmib 00:26:38:BULKSTAT-DC:In pollDataGroup 00:26:38:BULKSTAT-DC:Interface type data group


DB-2029


00:26:38:BULKSTAT-DC:polling done

Related Commands

Command

Description

show snmp mib bulkstat transfer Displays the transfer status of files generated by the Periodic MIB Data Collection and Transfer Mechanism. snmp mib bulkstat transfer

Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.


DB-2030

May 2008

Debug Commands debug snmp packet

debug snmp packet To display information about every Simple Network Management Protocol (SNMP) packet sent or received by the router, use the debug snmp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug snmp packet no debug snmp packet

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug snmp packet command. In this example, the router receives a get-next request from the host at 172.16.63.17 and responds with the requested information. Router# debug snmp packet SNMP: Packet received via UDP from 172.16.63.17 on Ethernet0 SNMP: Get-next request, reqid 23584, errstat 0, erridx 0 sysUpTime = NULL TYPE/VALUE system.1 = NULL TYPE/VALUE system.6 = NULL TYPE/VALUE SNMP: Response, reqid 23584, errstat 0, erridx 0 sysUpTime.0 = 2217027 system.1.0 = Cisco Internetwork Operating System Software system.6.0 = SNMP: Packet sent via UDP to 172.16.63.17

Based on the kind of packet sent or received, the output may vary. For get-bulk requests, a line similar to the following is displayed: SNMP: Get-bulk request, reqid 23584, nonrptr 10, maxreps 20

For traps, a line similar to the following is displayed: SNMP: V1 Trap, ent 1.3.6.1.4.1.9.1.13, gentrap 3, spectrap 0



DB-2031

Debug Commands debug snmp packet

Table 319

debug snmp packet Field Descriptions

Field

Description

Get-next request

Indicates what type of SNMP protocol data unit (PDU) the packet is. Possible types are as follows: •

Get request

•

Get-next request

•

Response

•

Set request

•

V1 Trap

•

Get-bulk request

•

Inform request

•

V2 Trap

Depending on the type of PDU, the rest of this line displays different fields. The indented lines following this line list the MIB object names and corresponding values. reqid

Request identification number. This number is used by the SNMP manager to match responses with requests.

errstat

Error status. All PDU types other than response will have an errstat of 0. If the agent encounters an error while processing the request, it will set errstat in the response PDU to indicate the type of error.

erridx

Error index. This value will always be 0 in all PDUs other than responses. If the agent encounters an error, the erridx will be set to indicate which varbind in the request caused the error. For example, if the agent had an error on the second varbind in the request PDU, the response PDU will have an erridx equal to 2.

nonrptr

Nonrepeater value. This value and the maximum repetition value are used to determine how many varbinds are returned. Refer to RFC 1905 for details.

maxreps

Maximum repetition value. This value and the nonrepeater value are used to determine how many varbinds are returned. Refer to RFC 1905 for details.

ent

Enterprise object identifier. Refer to RFC 1215 for details.

gentrap

Generic trap value. Refer to RFC 1215 for details.

spectrap

Specific trap value. Refer to RFC 1215 for details.


DB-2032

May 2008

Debug Commands debug snmp requests

debug snmp requests To display information about every Simple Network Management Protocol (SNMP) request made by the SNMP manager, use the debug snmp requests command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug snmp requests no debug snmp requests

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug snmp requests command: Router# debug snmp requests SNMP Manager API: request dest: 171.69.58.33.161, community: public retries: 3, timeout: 30, mult: 2, use session rtt userdata: 0x0


debug snmp requests Field Descriptions

Field

Description

SNMP Manager API

Indicates that the router sent an SNMP request.

dest

Destination of the request.

community

Community string sent with the request.

retries

Number of times the request has been re-sent.

timeout

Request timeout, or how long the router will wait before resending the request.

mult

Timeout multiplier. The timeout for a re-sent request will be equal to the previous timeout multiplied by the timeout multiplier.

use session rtt

Indicates that the average round-trip time of the session should be used in calculating the timeout value.

userdata

Internal Cisco IOS software data.


DB-2033

Debug Commands debug snmp sync

debug snmp sync To debug Simple Network Management Protocol (SNMP) synchronization and faults in synchronization, use the debug snmp sync command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command. debug snmp sync no debug snmp sync

Syntax Description


Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(22)S


12.2(18)S


12.2(33)SRA


12.2(31)SB2


12.2SX


Usage Guidelines

The debug snmp sync command can be used to debug SNMP synchronization and faults in synchronization. The standby Route Processor (RP) may sometimes reset as a result of synchronization faults. If the fault occurs when SNMP activities such as SNMP sets are in progress, enter the debug snmp sync command to identify whether a synchronization fault caused the reset. SNMP synchronizations (dynamic and bulk) are performed only if the router is configured to be in stateful switchover (SSO) mode.

Examples

The following example enables debugging of SNMP synchronization activity: Router# debug snmp sync

Related Commands

Command

Description

debug snmp packets

Displays information about every SNMP packet sent or received by the networking device.

mode

Configures the redundancy mode of operation.


DB-2034

May 2008

Debug Commands debug sntp adjust

debug sntp adjust To display information about Simple Network Time Protocol (SNTP) clock adjustments, use the debug sntp adjust command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sntp adjust no debug sntp adjust

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug sntp adjust command when an offset to the time reported by the configured NTP server is calculated. The offset indicates the difference between the router time and the actual time (as kept by the server) and is displayed in milliseconds. The clock time is then successfully changed to the accurate time by adding the offset to the current router time. Router# debug sntp adjust Delay calculated, offset 3.48 Clock slewed.

The following is sample output from the debug sntp adjust command when an offset to the time reported by a broadcast server is calculated. Because the packet is a broadcast packet, no transmission delay can be calculated. However, in this case, the offset is too large, so the clock is reset to the correct time. Router# debug sntp adjust No delay calculated, offset 11.18 Clock stepped.


DB-2035

Debug Commands debug sntp packets

debug sntp packets To display information about Simple Network Time Protocol (SNTP) packets sent and received, use the debug sntp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sntp packets no debug sntp packets

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug sntp packets command when a message is received: Router# debug sntp packets Received SNTP packet from 172.16.186.66, length 48 leap 0, mode 1, version 3, stratum 4, ppoll 1024 rtdel 00002B00, rtdsp 00003F18, refid AC101801 (172.16.24.1) ref B7237786.ABF9CDE5 (23:28:06.671 UTC Tue May 13 1997) org 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900) rec 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900) xmt B7237B5C.A7DE94F2 (23:44:28.655 UTC Tue May 13 1997) inp AF3BD529.810B66BC (00:19:53.504 UTC Mon Mar 1 1993)

The following is sample output from the debug sntp packets command when a message is sent: Router# debug sntp packets Sending SNTP packet to 172.16.25.1 xmt AF3BD455.FBBE3E64 (00:16:21.983 UTC Mon Mar 1 1993)


debug sntp packets Field Descriptions

Field

Description

length

Length of the SNTP packet.

leap

Indicates if a leap second will be added or subtracted.

mode

Indicates the mode of the router relative to the server sending the packet.

version

SNTP version number of the packet.

stratum

Stratum of the server.

ppoll

Peer polling interval.

rtdel

Total delay along the path to the root clock.

rtdsp

Dispersion of the root path.

refid

Address of the server that the router is currently using for synchronization.


DB-2036

May 2008

Debug Commands debug sntp packets

Table 321

debug sntp packets Field Descriptions (continued)

Field

Description

ref

Reference time stamp.

org

Originate time stamp. This value indicates the time the request was sent by the router.

rec

Receive time stamp. This value indicates the time the request was received by the SNTP server.

xmt

Transmit time stamp. This value indicates the time the reply was sent by the SNTP server.

inp

Destination time stamp. This value indicates the time the reply was received by the router.


DB-2037

Debug Commands debug sntp select

debug sntp select To display information about Simple Network Time Protocol (SNTP) server selection, use the debug sntp select command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sntp select no debug sntp select

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug sntp select command. In this example, the router will synchronize its time to the server at 172.16.186.66. Router# debug sntp select SNTP: Selected 172.16.186.66


DB-2038

May 2008

Debug Commands debug source bridge

debug source bridge To display information about packets and frames transferred across a source-route bridge, use the debug source bridge command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug source bridge no debug source bridge

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug source bridge command for peer bridges using TCP as a transport mechanism. The remote source-route bridging (RSRB) network configuration has ring 2 and ring 1 bridged together through remote peer bridges. The remote peer bridges are connected via a serial line and use TCP as the transport mechanism. Router# debug source bridge RSRB: RSRB: RSRB: RSRB: RSRB: RSRB: RSRB: RSRB:

remote explorer to 5/192.108.250.1/1996 srn 2 [C840.0021.0050.0000] Version/Ring XReq sent to peer 5/192.108.250.1/1996 Received version reply from 5/192.108.250.1/1996 (version 2) DATA: 5/192.108.250.1/1996 Ring Xchg Rep, trn 2, vrn 5, off 18, len 10 added bridge 1, ring 1 for 5/192.108.240.1/1996 DATA: 5/192.108.250.1/1996 Explorer trn 2, vrn 5, off 18, len 69 DATA: 5/192.108.250.1/1996 Forward trn 2, vrn 5, off 0, len 92 DATA: forward Forward srn 2, br 1, vrn 5 to peer 5/192.108.250.1/1996

The following line indicates that a remote explorer frame has been sent to IP address 192.108.250.1 and, like all RSRB TCP connections, has been assigned port 1996. The bridge belongs to ring group 5. The explorer frame originated from ring 2. The routing information field (RIF) descriptor has been generated by the local station and indicates that the frame was sent out via bridge 1 onto virtual ring 5. RSRB: remote explorer to 5/192.108.250.1/1996 srn 2 [C840.0021.0050.0000]

The following line indicates that a request for remote peer information has been sent to IP address 192.108.250.1, TCP port 1996. The bridge belongs to ring group 5. RSRB: Version/Ring XReq sent to peer 5/192.108.250.1/1996

The following line is the response to the version request previously sent. The response is sent from IP address 192.108.250.1, TCP port 1996. The bridge belongs to ring group 5. RSRB: Received version reply from 5/192.108.250.1/1996 (version 2)

The following line is the response to the ring request previously sent. The response is sent from IP address 192.108.250.1, TCP port 1996. The target ring number is 2, virtual ring number is 5, the offset is 18, and the length of the frame is 10 bytes. RSRB: DATA: 5/192.108.250.1/1996 Ring Xchg Rep, trn 2, vrn 5, off 0, len 10


DB-2039

Debug Commands debug source bridge

The following line indicates that bridge 1 and ring 1 were added to the source-bridge table for IP address 192.108.250.1, TCP port 1996: RSRB: added bridge 1, ring 1 for 5/192.108.250.1/1996

The following line indicates that a packet containing an explorer frame came across virtual ring 5 from IP address 192.108.250.1, TCP port 1996. The packet is 69 bytes in length. This packet is received after the Ring Exchange information was received and updated on both sides. RSRB: DATA: 5/192.108.250.1/1996 Explorer trn 2, vrn 5, off 18, len 69

The following line indicates that a packet containing data came across virtual ring 5 from IP address 192.108.250.1 over TCP port 1996. The packet is being placed on the local target ring 2. The packet is 92 bytes in length. RSRB: DATA: 5/192.108.250.1/1996 Forward trn 2, vrn 5, off 0, len 92

The following line indicates that a packet containing data is being forwarded to the peer that has IP address 192.108.250.1 address belonging to local ring 2 and bridge 1. The packet is forwarded via virtual ring 5. This packet is sent after the Ring Exchange information was received and updated on both sides. RSRB: DATA: forward Forward srn 2, br 1, vrn 5 to peer 5/192.108.250.1/1996

The following is sample output from the debug source bridge command for peer bridges using direct encapsulation as a transport mechanism. The RSRB network configuration has ring 1 and ring 2 bridged together through peer bridges. The peer bridges are connected via a serial line and use TCP as the transport mechanism. Router# debug source bridge RSRB: RSRB: RSRB: RSRB: RSRB:

remote explorer to 5/Serial1 srn 1 [C840.0011.0050.0000] Version/Ring XReq sent to peer 5/Serial1 Received version reply from 5/Serial1 (version 2) IFin: 5/Serial1 Ring Xchg, Rep trn 0, vrn 5, off 0, len 10 added bridge 1, ring 1 for 5/Serial1

The following line indicates that a remote explorer frame was sent to remote peer Serial1, which belongs to ring group 5. The explorer frame originated from ring 1. The RIF descriptor 0011.0050 was generated by the local station and indicates that the frame was sent out via bridge 1 onto virtual ring 5. RSRB: remote explorer to 5/Serial1 srn 1 [C840.0011.0050.0000]

The following line indicates that a request for remote peer information was sent to Serial1. The bridge belongs to ring group 5. RSRB: Version/Ring XReq sent to peer 5/Serial1

The following line is the response to the version request previously sent. The response is sent from Serial 1. The bridge belongs to ring group 5 and the version is 2. RSRB: Received version reply from 5/Serial1 (version 2)

The following line is the response to the ring request previously sent. The response is sent from Serial1. The target ring number is 2, virtual ring number is 5, the offset is 0, and the length of the frame is 39 bytes. RSRB: IFin: 5/Serial1 Ring Xchg Rep, trn 2, vrn 5, off 0, len 39

The following line indicates that bridge 1 and ring 1 were added to the source-bridge table for Serial1: RSRB: added bridge 1, ring 1 for 5/Serial1


DB-2040

May 2008

Debug Commands debug source error

debug source error To display source-route bridging (SRB) errors, use the debug source error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug source error no debug source error

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug source error command displays some output also found in the debug source bridge output. See the debug source bridge command for other possible output.

Examples

In all of the following examples of debug source error command messages, the variable number is the Token Ring interface. For example, if the line of output starts with SRB1, the output relates to the Token Ring 1 interface. SRB indicates a source-route bridging message. RSRB indicates a remote source-route bridging message. SRTLB indicates a source-route translational bridging (SR/TLB) message. In the following example, a packet of protocol protocol-type was dropped: SRBnumber drop: Routed protocol protocol-type

In the following example, an Address Resolution Protocol (ARP) packet was dropped. ARP is defined in RFC 826. SRBnumber drop:TYPE_RFC826_ARP

In the following example, the current Cisco IOS version does not support Qualified Logical Link Control (QLLC). Reconfigure the router with an image that has the IBM feature set. RSRB: QLLC not supported in version version Please reconfigure.

In the following example, the packet was dropped because the outgoing interface of the router was down: RSRB IF: outgoing interface not up, dropping packet

In the following example, the router received an out-of-sequence IP sequence number in a Fast Sequenced Transport (FST) packet. FST has no recovery for this problem like TCP encapsulation does. RSRB FST: bad sequence number dropping.

In the following example, the router was unable to locate the virtual interface: RSRB: couldn't find virtual interface

In the following example, the TCP queue of the peer router is full. TCPD indicates that this is a TCP debug. RSRB TCPD: tcp queue full for peer


DB-2041

Debug Commands debug source error

In the following example, the router was unable to send data to the peer router. A result of 1 indicates that the TCP queue is full. A result of —1 indicates that the RSRB peer is closed. RSRB TCPD: tcp send failed for peer result

In the following example, the routing information identifier (RII) was not set in the explorer packet going forward. The packet will not support SRB, so it is dropped. vrforward_explorer - RII not set

In the following example, a packet sent to a virtual bridge in the router did not include a routing information field (RIF) to tell the router which route to use: RSRB: no RIF on packet sent to virtual bridge

The following example indicates that the RIF did not contain any information or the length field was set to zero: RSRB: RIF length of zero sent to virtual bridge

The following message occurs when the local service access point (LSAP) is out of range. The variable lsap-out is the value, type is the type of RSRB peer, and state is the state of the RSRB peer. VRP: rsrb_lsap_out = lsap-out, type = type, state = state

In the following message, the router is unable to find another router with which to exchange bridge protocol data units (BPDUs). BPDUs are exchanged to set up the spanning tree and determine the forwarding path. RSRB(span): BPDU's peer not found

Related Commands

Command

Description

debug source bridge

Displays information about packets and frames transferred across a source-route bridge.

debug source event

Displays information on SRB activity.


DB-2042

May 2008

Debug Commands debug source event

debug source event To display information on source-route bridging (SRB) activity, use the debug source event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug source event no debug source event

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Some of the output from the debug source bridge and debug source error commands is identical to the output of this command.

Note

Examples

In order to use the debug source event command to display traffic source-routed through an interface, you first must disable fast switching of SRB frames with the no source bridge route-cache interface configuration command.

The following is sample output from the debug source event command: Router# debug source event RSRB0: forward (srn 5 [0800.3201.00A1.0050] RSRB0: forward (srn 5 [0800.3201.00A1.0050] RSRB0: forward (srn 5 [0800.3201.00A1.0050] RSRB0: forward (srn 5 [0800.3201.00A1.0050] RSRB0: forward (srn 5 [0800.3201.00A1.0050]

bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9


debug source event Field Descriptions

Field

Description

RSRB0:

Indication that this routing information field (RIF) cache entry is for the Token Ring interface 0, which has been configured for remote source-route bridging (SRB). (SRB1, in contrast, would indicate that this RIF cache entry is for Token Ring 1, configured for SRB.)

forward

Forward (normal data) packet, in contrast to a control packet containing proprietary Cisco bridging information.

srn 5

Ring number of the source ring of the packet.


DB-2043


Table 322

debug source event Field Descriptions (continued)

Field

Description

bn 1

Bridge number of the bridge this packet traverses.

trn 10

Ring number of the target ring of the packet.

src: 8110.2222.33c1

Source address of the route in this RIF cache entry.

dst: 1000.5a59.04f9

Destination address of the route in this RIF cache entry.

[0800.3201.00A1.0050]

RIF string in this RIF cache entry.

In the following example messages, SRBnumber or RSRBnumber denotes a message associated with interface Token Ring number. A number of 99 denotes the remote side of the network. SRBnumber: no path, s: source-MAC-addr d: dst-MAC-addr rif: rif

In the preceding example, a bridgeable packet came in on interface Token Ring number but there was nowhere to send it. This is most likely a configuration error. For example, an interface has source bridging turned on, but it is not connected to another source bridging interface or a ring group. In the following example, a bridgeable packet has been forwarded from Token Ring number to the target ring. The two interfaces are directly linked. SRBnumber: direct forward (srn ring bn bridge trn ring)

In the following examples, a proxy explorer reply was not generated because the address could not be reached from this interface. The packet came from the node with the first address. SRBnumber: SRBnumber: SRBnumber: SRBnumber: SRBnumber: SRBnumber:

br br br br br br

dropped dropped dropped dropped dropped dropped

proxy proxy proxy proxy proxy proxy

XID, address for address, wrong vring (rem) TEST, address for address, wrong vring (rem) XID, address for address, wrong vring (local) TEST, address for address, wrong vring (local) XID, address for address, no path TEST, address for address, no path

In the following example, an appropriate proxy explorer reply was generated on behalf of the second address. It is sent to the first address. SRBnumber: br sent proxy XID, address for address[rif] SRBnumber: br sent proxy TEST, address for address[rif]

The following example indicates that the broadcast bits were not set, or that the routing information indicator on the packet was not set: SRBnumber: illegal explorer, s: source-MAC-addr d: dst-MAC-addr rif: rif

The following example indicates that the direction bit in the RIF field was set, or that an odd packet length was encountered. Such packets are dropped. SRBnumber: bad explorer control, D set or odd

The following example indicates that a spanning explorer was dropped because the spanning option was not configured on the interface: SRBnumber: span dropped, input off, s: source-MAC-addr d: dst-MAC-addr rif: rif

The following example indicates that a spanning explorer was dropped because it had traversed the ring previously: SRBnumber: span violation, s: source-MAC-addr d: dst-MAC-addr rif: rif


DB-2044

May 2008


The following example indicates that an explorer was dropped because the maximum hop count limit was reached on that interface: SRBnumber: max hops reached - hop-cnt, s: source-MAC-addr d: dst-MAC-addr rif: rif

The following example indicates that the ring exchange request was sent to the indicated peer. This request tells the remote side which rings this node has and asks for a reply indicating which rings that side has. RSRB: sent RingXreq to ring-group/ip-addr

The following example indicates that a message was sent to the remote peer. The label variable can be AHDR (active header), PHDR (passive header), HDR (normal header), or DATA (data exchange), and op can be Forward, Explorer, Ring Xchg, Req, Ring Xchg, Rep, Unknown Ring Group, Unknown Peer, or Unknown Target Ring. RSRB: label: sent op to ring-group/ip-addr

The following example indicates that the remote bridge and ring pair were removed from or added to the local ring group table because the remote peer changed: RSRB: removing bn bridge rn ring from ring-group/ip-addr RSRB: added bridge bridge, ring ring for ring-group/ip-addr

The following example shows miscellaneous remote peer connection establishment messages: RSRB: RSRB: RSRB: RSRB: RSRB:

peer ring-group/ip-addr closed [last state n] passive open ip-addr(remote port) -> local port CONN: opening peer ring-group/ip-addr, attempt n CONN: Remote closed ring-group/ip-addr on open CONN: peer ring-group/ip-addr open failed, reason[code]

The following example shows that an explorer packet was propagated onto the local ring from the remote ring group: RSRBn: sent local explorer, bridge bridge trn ring, [rif]

The following messages indicate that the RSRB code found that the packet was in error: RSRBn: ring group ring-group not found RSRBn: explorer rif [rif] not long enough

The following example indicates that a buffer could not be obtained for a ring exchange packet (this is an internal error): RSRB: couldn’t get pak for ringXchg

The following example indicates that a ring exchange packet was received that had an incorrect length (this is an internal error): RSRB: XCHG: req/reply badly formed, length pak-length, peer peer-id

The following example indicates that a ring entry was removed for the peer; the ring was possibly disconnected from the network, causing the remote router to send an update to all its peers. RSRB: removing bridge bridge ring ring from peer-id ring-type

The following example indicates that a ring entry was added for the specified peer; the ring was possibly added to the network, causing the other router to send an update to all its peers. RSRB: added bridge bridge, ring ring for peer-id


DB-2045


The following example indicates that no memory was available to add a ring number to the ring group specified (this is an internal error): RSRB: no memory for ring element ring-group

The following example indicates that memory was corrupted for a connection block (this is an internal error): RSRB: CONN: corrupt connection block

The following example indicates that a connector process started, but that there was no packet to process (this is an internal error): RSRB: CONN: warning, no initial packet, peer: ip-addr peer-pointer

The following example indicates that a packet was received with a version number different from the one pre-sent on the router: RSRB: IF New version. local=local-version, remote=remote-version,pak-op-code peer-id

The following example indicates that a packet with a bad op code was received for a direct encapsulation peer (this is an internal error): RSRB: IFin: bad op op-code (op code string) from peer-id

The following example indicates that the virtual ring header will not fit on the packet to be sent to the peer (this is an internal error): RSRB: vrif_sender, hdr won't fit

The following example indicates that the specified peer is being opened. The retry count specifies the number of times the opening operation is attempted. RSRB: CONN: opening peer peer-id retry-count

The following example indicates that the router, configured for FST encapsulation, received a version reply to the version request packet it had sent previously: RSRB: FST Rcvd version reply from peer-id (version version-number)

The following example indicates that the router, configured for FST encapsulation, sent a version request packet to the specified peer: RSRB: FST Version Request. op = opcode, peer-id

The following example indicates that the router received a packet with a bad op code from the specified peer (this is an internal error): RSRB: FSTin: bad op opcode (op code string) from peer-id

The following example indicates that the TCP connection between the router and the specified peer is being aborted: RSRB: aborting ring-group/peer-id (vrtcpd_abort called)

The following example indicates that an attempt to establish a TCP connection to a remote peer timed out: RSRB: CONN: attempt timed out

The following example indicates that a packet was dropped because the ring group number in the packet did not correlate with the ring groups configured on the router: RSRBnumber: ring group ring-group not found


DB-2046

May 2008

Debug Commands debug span

debug span To display information on changes in the spanning-tree topology when debugging a transparent bridge, use the debug span command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug span no debug span

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command is useful for tracking and verifying that the spanning-tree protocol is operating correctly.

Examples

The following is sample output from the debug span command for an IEEE bridge protocol data unit (BPDU) packet: Router# debug span ST: Ether4 0000000000000A080002A02D6700000000000A080002A02D6780010000140002000F00

The following is sample output from the debug span command: ST: Ether4 0000000000000A080002A02D6700000000000A080002A02D6780010000140002000F00 A B C D E F G H I J K L M N O


debug span Field Descriptions—IEEE BPDU Packet

Field

Description

ST:

Indication that this is a spanning tree packet.

Ether4

Interface receiving the packet.

(A) 0000

Indication that this is an IEEE BPDU packet.

(B) 00

Version.

(C) 00

Command mode:

(D) 00

(E) 000A

•

00 indicates config BPDU.

•

80 indicates the Topology Change Notification (TCN) BPDU.

Topology change acknowledgment: •

00 indicates no change.

•

80 indicates a change notification.

Root priority.


DB-2047


Table 323

debug span Field Descriptions—IEEE BPDU Packet (continued)

Field

Description

(F) 080002A02D67

Root ID.

(G) 00000000

Root path cost (0 means the sender of this BPDU packet is the root bridge).

(H) 000A

Bridge priority.

(I) 080002A02D67

Bridge ID.

(J) 80

Port priority.

(K) 01

Port Number 1.

(L) 0000

Message age in 256ths of a second (0 seconds, in this case).

(M) 1400

Maximum age in 256ths of a second (20 seconds, in this case).

(N) 0200

Hello time in 256ths of a second (2 seconds, in this case).

(O) 0F00

Forward delay in 256ths of a second (15 seconds, in this case).

The following is sample output from the debug span command for a DEC BPDU packet: Router# debug span ST: Ethernet4 E1190100000200000C01A2C90064008000000C0106CE0A01050F1E6A

The following is sample output from the debug span command: E1 19 01 00 0002 00000C01A2C9 0064 0080 00000C0106CE 0A 01 05 0F 1E 6A A B C D E F G H I J K L M N O


debug span Field Descriptions for a DEC BPDU Packet

Field

Description

ST:

Indication that this is a spanning tree packet.

Ethernet4

Interface receiving the packet.

(A) E1

Indication that this is a DEC BPDU packet.

(B) 19

Indication that this is a DEC hello packet. Possible values are as follows: •

0x19—DEC Hello

•

0x02—TCN

(C) 01

DEC version.

(D) 00

Flag that is a bit field with the following mapping: •

1—TCN

•

2—TCN acknowledgment

•

8—Use short timers

(E) 0002

Root priority.

(F) 00000C01A2C9

Root ID (MAC address).


DB-2048

May 2008


Table 324

debug span Field Descriptions for a DEC BPDU Packet (continued)

Field

Description

(G) 0064

Root path cost (translated as 100 in decimal notation).

(H) 0080

Bridge priority.

(I) 00000C0106CE

Bridge ID.

(J) 0A

Port ID (in contrast to interface number).

(K) 01

Message age (in seconds).

(L) 05

Hello time (in seconds).

(M) 0F

Maximum age (in seconds).

(N) 1E

Forward delay (in seconds).

(O) 6A

Not applicable.


DB-2049

Debug Commands debug spanning-tree

debug spanning-tree To debug spanning-tree activities, use the debug spanning-tree command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug spanning-tree {all | backbonefast | bpdu | bpdu-opt | config | etherchannel | events | exceptions | general | pvst+ | root | snmp | uplinkfast} no debug spanning-tree {all | backbonefast | bpdu | bpdu-opt | config | etherchannel | events | exceptions | general | pvst+ | root | snmp | uplinkfast}

Syntax Description

all

Displays all spanning-tree debugging messages.

backbonefast

Displays debugging messages for BackboneFast events.

bpdu

Displays debugging messages for spanning-tree Bridge Protocol Data Units (BPDUs).

bpdu-opt

Displays debugging messages for optimized BPDU handling.

config

Displays debugging messages for spanning-tree configuration changes.

etherchannel

Displays debugging messages for EtherChannel support.

events

Displays debugging messages for spanning-tree topology events.

exceptions

Displays debugging messages for spanning-tree exceptions.

general

Displays debugging messages for general spanning-tree activity.

pvst+

Displays debugging messages for per-VLAN Spanning Tree Plus (PVST+) events.

root

Displays debugging messages for spanning-tree root events.

snmp

Displays debugging messages for spanning-tree Simple Network Management Protocol (SNMP) handling.

uplinkfast

Displays debugging messages for UplinkFast events.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(6)EA2


12.2(15)ZJ

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.

12.3(4)T



DB-2050

May 2008

Debug Commands debug spanning-tree

Release

Modification

12.2(33)SRA


12.2SX


Usage Guidelines

The undebug spanning-tree command is the same as the no debug spanning-tree command.

Related Commands

Command

Description

show debugging


show spanning-tree

Displays spanning-tree state information.


DB-2051

Debug Commands debug ss7 mtp1

debug ss7 mtp1 Note

Use this command only if told to do so by your Cisco representative. To initiate Signaling System 7 (SS7) Message Transfer Part Level 1 (MTP1) debugging, enter the debug ss7 mtp1 command in global configuration mode during a low-traffic period. To disable debugging output, use the no form of this command. debug ss7 mtp1 [mtp2 | ipc | link-state | oir | rx | scc-regs | siram | tdm-info | tx] no debug ss7 mtp1

Syntax Description

mtp2

(Optional) Initiates SS7 MTP2 debugging.

ipc

(Optional) Initiates SS7 MTP1 debugging for HOST/FW IPC.

link-state

(Optional) Initiates SS7 MTP1 debugging for link-state transitions.

oir

(Optional) Initiates SS7 MTP1 trunk dial feature card (DFC) online insertion and removal (OIR) debugging.

rx

(Optional) Initiates SS7 MTP1 debugging for receive events. Not used in Release 12.2(11)T.

scc-regs

(Optional) Initiates SS7 MTP1 debugging for SCC registers. Not used in Release 12.2(11)T.

siram

(Optional) Initiates SS7 MTP1 debugging for siram values. Not used in Release 12.2(11)T.

tdm-info

(Optional) Initiates SS7 MTP1 debugging for time-division multiplexing (TDM) information.

tx

(Optional) Initiates SS7 MTP1 debugging for transmission events. Not used in Release 12.2(11)T.

Defaults

Debug is disabled.

Command Modes

Global configuration

Command History

Release

Modification

12.2(11)T

This command was introduced on the Cisco AS5350 and Cisco AS5400 Signaling Link Terminal (SLT).

12.2SX



DB-2052

May 2008


Usage Guidelines

Examples

The following debug commands are not used in this release: •

debug ss7 mtp1 rx

•

debug ss7 mtp1 tx

•

debug ss7 mtp1 scc-regs

•

debug ss7 mtp1 siram

To turn on message tracing between the host processor and the trunk firmware for each trunk card inserted, use the debug ss7 mtp1 ipc command. For example, there is a digital link in slot 7, trunk 0, channel-group 0 (therefore, timeslot 1). When you enter show ss7 mtp1 links, the following output is displayed: Router# show ss7 mtp1 links SS7 MTP1 Links [num = 1, platform max = 4]:

interface --------7/0:0

session type SCC state ------------digital 7/3 STOPPED

channel ------0

Notice that the link is stopped in this example. Enter the following commands: Router# debug ss7 mtp1 ipc Router# configure terminal Router(config)# interface serial 7/0:0 Router(config-if)# no shutdown Router(config-if)# end

You would see trace output similar to the following: 00:01:27:from Trunk(7):TRUNK_SERIAL_STOP(3), link_type=2 00:01:27:from Trunk(7):TRUNK_SERIAL_START(3), link_type=2

In this case, the output means that for the SS7 link that is using SCC3 on the trunk card in slot 7 (link 7/0:0), the host processor has told the board firmware to STOP then START. To show low-level (MTP1) state changes for the internal state-machine implemented for each SS7 link, use the debug ss7 mtp1 link-state command. The following output shows the different MTP1 states link Serial 7/0:0 goes through during shutdown, no shutdown, and debug. For example, if you stopped the SS7 link 7/0:0 (shutdown), then restarted it (no shutdown), you could see MTP1 state changes by enabling debugging, as follows: Router# debug ss7 mtp1 link-state Router# configure terminal Router(config)# interface serial 7/0:0 Router(config-if)# shutdown 01:02:20:%TRUNK_SERIAL-3-STATE_GENERIC: At ../src-7k-as5400/as5400_ss7_link.c:511 [Serial7/0:0]:STOP: STARTED -> STOP_PENDING ss7_link_ll_stop 7/0:0:Tx shadow ring has 0 unsent buffers 01:02:20:%TRUNK_SERIAL-3-STATE_GENERIC: At ../src-7k-as5400/as5400_ss7_link.c:1010 [Serial7/0:0]: FW_STOPPED: STOP_PENDING -> STOPPED


DB-2053


Now restart the link: Router(config-if)# no shutdown 01:02:26:ss7_link_start:slot=7/SCCport=3 current state is STOPPED 01:02:26:%TRUNK_SERIAL-3-STATE_GENERIC: At ../src-7k-as5400/as5400_ss7_link.c:1417 [Serial7/0:0]: START: STOPPED -> START_PENDING 01:02:26:%TRUNK_SERIAL-3-STATE_GENERIC: At ../src-7k-as5400/as5400_ss7_link.c:1164 [Serial7/0:0]: STOP_START: START_PENDING -> STOP_START_PENDING ss7_link_ll_stop 7/0:0:Tx shadow ring has 0 unsent buffers 01:02:26:%TRUNK_SERIAL-3-STATE_GENERIC: At ../src-7k-as5400/as5400_ss7_link.c:1010 [Serial7/0:0]: FW_STOPPED: STOP_START_PENDING -> START_PENDING 01:02:26:%TRUNK_SERIAL-3-STATE_GENERIC: At ../src-7k-as5400/as5400_ss7_link.c:1234 [Serial7/0:0]: FW_STARTED: START_PENDING -> STARTED

To show detailed information about how TDM timeslots on the DFC trunk card on the host backplane are allocated and deallocated based on link configuration activity, use the debug ss7 mtp1 tdm-info command. For example, if you wanted to create a digital SS7 link on timeslot 1 of trunk 0 for an 8PRI board in slot 7, and you would like to see traces of the TDM resources allocated, you would enable TDM debugging using the debug ss7 mtp1 tdm-info command then create the new SS7 link as described above, as in the following example: Router# debug ss7 mtp1 tdm-info Router# configure terminal Router(config)# controller t1 7/0 Router(config-controller)# channel-group 0 timeslots 1 Router(config-controller)# exit Router(config)# interface serial 7/0:0 Router(config-if)# encapsulation ss7

Due to the debug flag, the following information is displayed: 05:26:55: ss7_link_flink_tdm_setup:card type for slot 7 is T1 8PRI 05:26:55: ds0-side BEFORE call to tdm_allocate_bp_ts() slot = 7 unit = 0 (trunk) channel = 4 stream = 0 group = 0 05:26:55: scc-side BEFORE call to tdm_allocate_bp_ts() slot = 7 unit = 29 channel = 3 (SCC-port) stream = 3 group = 0 05:26:55: 05:26:55:TDM(PRI:0x28002000):Close PRI framer st0 ch4 05:26:55:> 05:26:55:scc-side AFTER call to tdm_allocate_bp_ts() bp_channel = 4


DB-2054

May 2008


bp_stream = 0 bp_ts->bp_stream bp_ts->bp_channel bp_ts->vdev_slot bp_ts->vdev_channel

bp_ts->vdev_slot *->channel.

= = = =

0 4 7 3

= 7 should be same as the CLI slot, and bp_ts->vdev_channel = 3should be

When you later remove the SS7 link, other information is displayed showing how resources are cleaned up.

Related Commands

Command

Description

debug ss7 sm

Displays debugging messages for an SS7 Session Manager.


DB-2055


debug ss7 mtp2 To trace backhaul Signaling System 7 (SS7) Message Transfer Part Level 2 (MTP2 ) message signaling units (MSUs), enter the debug ss7 mtp2 command in global configuration mode during a low-traffic period. To disable debugging output, use the no form of this command. debug ss7 mtp2 [aerm | backhaul | cong | iac | lsc | lssu | msu | packet [all] | rcv | suerm | timer | txc][channel] no debug ss7 mtp2

Syntax Description

aerm

(Optional) Initiates alignment Error Rate Monitor events.

backhaul

(Optional) Initiates trace backhaul control messages. The channel argument represents a logical channel number. Valid values are from 0 to 3.

cong

(Optional) Initiates congestion Control events.

iac

(Optional) Initiates initial Alignment Control events.

lsc

(Optional) Initiates Link State Control events.

lssu

(Optional) Initiates trace backhaul LSSU messages.

msu

(Optional) Initiates trace backhaul MSU messages (use during low traffic only).

packet [all]

(Optional) Initiates low-level MTP2 packet tracing. If you do not specify a channel number or enter the all keyword, the command displays information for channel 0.

rcv

(Optional) Displays information about SS7 MTP2 receiver state machine events and transitions.

suerm

(Optional) Displays information about SS7 MTP2 Signal Unit Error Rate Monitor (SUERM) state machine events and transitions.

timer

(Optional) Displays information about SS7 MTP2 timer starts and stops.

txc

(Optional) Displays information about SS7 MTP2 transmit state machine events and transitions.

channel

(Optional) The channel argument represents a logical channel number. Valid values are from 0 to 3.

Defaults

Debug is disabled.

Command Modes

Global configuration


DB-2056

May 2008


Command History

Release

Modification

12.0(7)XR


12.1(1)T


12.2(11)T

This command was implemented on the Cisco AS5350 and Cisco AS5400 Cisco Signaling Link Terminal (SLT).

12.2SX


Usage Guidelines

If you do not specify a channel number with each keyword, the command displays information for channel 0.

Examples

The following is sample output from the debug ss7 mtp2 aerm command. See the MTP2 specification tables for details: Router# debug ss7 mtp2 aerm 0 *Mar *Mar

8 08:59:30.991:itu2AERM_Start chnl=0 MTP2AERM_IDLE 8 08:59:35.070:itu2AERM_Stop chnl=0 MTP2AERM_MONITORING

The following is an example of debug ss7 mtp2 backhaul command output for channel 0: Router# debug ss7 mtp2 backhaul 0 *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

03:08:04.433: 03:08:04.433: 03:08:08.721: 03:08:10.311: 03:08:10.311: 03:08:20.440: 03:08:20.444: 03:08:24.719: 03:08:36.438: 03:08:36.438: 03:08:40.312: 03:08:40.312: 03:08:40.721: 03:08:52.444: 03:08:52.444: 03:08:56.719: 03:09:08.438: 03:09:08.438:

MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2: MTP2:

send send rcvd rcvd send send send rcvd send send rcvd send rcvd send send rcvd send send

Disc Ind ch=0 reason=0x14-T2 expired waiting for SIO LSC Ind ch=0 event=0x8-lost link alignment cause=0x0 Conn Req - Normal ch=0 Statistics Req-Send&Reset ch=0 Stats Cfm ch=0 Disc Ind ch=0 reason=0x14-T2 expired waiting for SIO LSC Ind ch=0 event=0x8-lost link alignment cause=0x0 Conn Req - Normal ch=0 Disc Ind ch=0 reason=0x14-T2 expired waiting for SIO LSC Ind ch=0 event=0x8-lost link alignment cause=0x0 Statistics Req-Send&Reset ch=0 Stats Cfm ch=0 Conn Req - Normal ch=0 Disc Ind ch=0 reason=0x14-T2 expired waiting for SIO LSC Ind ch=0 event=0x8-lost link alignment cause=0x0 Conn Req - Normal ch=0 Disc Ind ch=0 reason=0x14-T2 expired waiting for SIO LSC Ind ch=0 event=0x8-lost link alignment cause=0x0

The following is an example of debug ss7 mtp2 cong command output. See the MTP2 specification tables for details: Router# debug ss7 mtp2 cong 0 *Mar 8 09:10:56.219:itu2CongestionOnset chnl=0 MTP2CONGESTION_IDLE *Mar 8 09:10:59.332:itu2CongestionAbatement chnl=0 MTP2CONGESTION_ACTIVE *Mar 8 09:11:01.143:itu2CongestionAbatement chnl=0 MTP2CONGESTION_IDLE


DB-2057


The following is an example of debug ss7 mtp2 iac command output. See the MTP2 specification tables for details: Router# debug ss7 mtp2 iac 0 *Mar *Mar *Mar *Mar *Mar

8 8 8 8 8

09:17:58.367:itu2IAC_Start chnl=0 MTP2IAC_IDLE 09:17:58.739:itu2IAC_Rcvd_SIO chnl=0 MTP2IAC_NOT_ALIGNED 09:17:58.739:itu2IAC_Rcvd_SIN chnl=0 MTP2IAC_ALIGNED 09:17:58.739:itu2IAC_Rcvd_SIN chnl=0 MTP2IAC_PROVING 09:18:02.814:itu2IAC_T4_TMO chnl=0 MTP2IAC_PROVING

The following is an example of debug ss7 mtp2 lsc command output. See the MTP2 specification tables for details: Router# debug ss7 mtp2 lsc 0 *Mar 8 09:20:21.105:itu2LSC_Rcvd_SIOS chnl=0 MTP2LSC_INSERVICE *Mar 8 09:20:21.121:itu2LSC_Retrieve_BSNT chnl=0 MTP2LSC_OOS *Mar 8 09:20:22.058:itu2LSC_SetEmergency chnl=0 MTP2LSC_OOS *Mar 8 09:20:22.058:itu2LSC_Start chnl=0 MTP2LSC_OOS *Mar 8 09:20:33.785:itu2LSC_AlignmentNotPossible chnl=0 MTP2LSC_INITIAL_ALIGNMENT *Mar 8 09:20:38.758:itu2LSC_SetEmergency chnl=0 MTP2LSC_OOS *Mar 8 09:20:38.758:itu2LSC_Start chnl=0 MTP2LSC_OOS *Mar 8 09:20:44.315:itu2LSC_Rcvd_SIO chnl=0 MTP2LSC_INITIAL_ALIGNMENT *Mar 8 09:20:44.315:itu2LSC_Rcvd_SIO chnl=0 MTP2LSC_INITIAL_ALIGNMENT *Mar 8 09:20:44.319:itu2LSC_Rcvd_SIE chnl=0 MTP2LSC_INITIAL_ALIGNMENT *Mar 8 09:20:44.319:itu2LSC_Rcvd_SIE chnl=0 MTP2LSC_INITIAL_ALIGNMENT *Mar 8 09:20:48.397:itu2LSC_AlignmentComplete chnl=0 MTP2LSC_INITIAL_ALIGNMENT

The following is an example of debug ss7 mtp2 msu command output for channel 2. The output for this command can slow traffic under busy conditions, so enter it when there is low traffic. See the MTP2 specification tables for details about the command output: Router# debug ss7 mtp2 msu 2 *Mar *Mar

Caution

1 01:01:12.447: MTP2: send MSU Ind 1 01:01:12.455: MTP2: rcvd MSU Req

ch=2 ch=2

len=25 len=252

Use this command only for testing problems in a controlled environment. This command can generate significant amounts of output. If there is any significant amount of traffic flow when you issue the command, the processor may slow down so much that RUDP connections fail. This command is recommended for field support personnel only, and is not recommended for use without prior recommendation from Cisco. The following is an example of debug ss7 mtp2 packet command output for channel 0: Router# debug ss7 mtp2 packet 0 *Mar 1 00:53:00.052: MTP2 incoming trace enabled on channel 0. *Mar 1 00:53:00.052: MTP2 outgoing trace enabled on channel 0. *Mar 1 00:53:07.220: ---- Incoming Rudp msg (20 bytes) ---SM_msg_type 0x00008000 protocol_type 0x0001 msg_ID 0x0001 msg_type 0x0044 channel_ID 0x0000 bearer_ID 0x0000 length 0x0004 data 0x00000001


DB-2058

May 2008


*Mar 1 00:53:07.224: ---- Outgoing Rudp msg (132 bytes) ---SM_msg_type 0x00008000 protocol_type 0x0001 msg_ID 0x0001 msg_type 0x0045 channel_ID 0x0000 bearer_ID 0x0000 length 0x0074 data 0x0000001E 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000002 0x00000000 0x00008317 0x00000000 0x00000002 0x00000000 0x00000008 0x009B5C97 0x00000000 0x0032A2A7 0x0000061C 0x000000BF 0x00000000 0x00000000 0x00000006 0x00000000 0x000000ED *Mar 1 00:53:11.343: ---- Outgoing Rudp msg (41 bytes) ---SM_msg_type 0x00008000 protocol_type 0x0001 msg_ID 0x0000 msg_type 0x0011 channel_ID 0x0000 bearer_ID 0x0000 length 0x0019 data 0x8201190A 0x03190A00 0x11F01122 0x33445566 0x778899AA 0xBBCCDDEE *Mar 1 00:53:11.351: ---- Incoming Rudp msg (41 bytes) ---SM_msg_type 0x00008000 protocol_type 0x0001 msg_ID 0x0001 msg_type 0x0010 channel_ID 0x0000 bearer_ID 0x0000 length 0x0019 data 0xB203190A 0x01190A00 0x21F01122 0x33445566 0x778899AA 0xBBCCDDEE *Mar 1 00:53:13.739: ---- Incoming Rudp msg (27 bytes) ---SM_msg_type 0x00008000 protocol_type 0x0001 msg_ID 0x0001 msg_type 0x0010 channel_ID 0x0000 bearer_ID 0x0000 length 0x000B data 0x9503190A 0x01190A00

The following is an example of debug ss7 mtp2 rcv command output. See the MTP2 specification tables for details: Router# debug ss7 mtp2 rcv 0 *Mar *Mar *Mar

*Mar

*Mar

8 09:22:35.160:itu2RC_Stop chnl=0 MTP2RC_INSERVICE 8 09:22:35.164:itu2RC_Start chnl=0 MTP2RC_IDLE 8 09:22:52.565:BSNR not in window bsnr=2 bibr=0x80 fsnr=66 fibr=0x80 fsnf=0 fsnl=127 fsnt=127 8 09:22:52.569:BSNR not in window bsnr=2 bibr=0x80 fsnr=66 fibr=0x80 fsnt=127

fsnf=0

fsnl=127

fsnx=0

fsnx=0

8 09:22:52.569:AbnormalBSN_flag == TRUE


DB-2059


*Mar *Mar

8 09:22:52.569:itu2RC_Stop chnl=0 MTP2RC_INSERVICE 8 09:22:57.561:itu2RC_Start chnl=0 MTP2RC_IDLE

The following is an example of debug ss7 mtp2 suerm command output. See the MTP2 specification tables for details: Router# debug ss7 mtp2 suerm 0 *Mar *Mar

Caution

8 09:33:51.108:itu2SUERM_Stop chnl=0 MTP2SUERM_MONITORING 8 09:34:00.155:itu2SUERM_Start chnl=0 MTP2SUERM_IDLE

Use this command only for testing problems in a controlled environment. This command can generate significant amounts of output. If there is any significant amount of traffic flow when you issue the command, the processor may slow down so much that RUDP connections fail. This command is recommended for field support personnel only, and is not recommended for use without prior recommendation from Cisco. The following is an example of debug ss7 mtp2 timer command output for channel 0: Router# debug ss7 mtp2 timer 0 *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

Caution

1 1 1 1 1 1 1 1 1 1 1 1

01:08:13.738: 01:08:13.762: 01:08:13.786: 01:08:13.810: 01:08:43.819: 01:08:43.843: 01:08:48.603: 01:08:48.627: 01:09:13.784: 01:09:13.808: 01:09:13.885: 01:09:13.909:

Timer Timer Timer Timer Timer Timer Timer Timer Timer Timer Timer Timer

T7 T7 T7 T7 T7 T7 T7 T7 T7 T7 T7 T7

(ex (ex (ex (ex (ex (ex (ex (ex (ex (ex (ex (ex

delay) delay) delay) delay) delay) delay) delay) delay) delay) delay) delay) delay)

Start Stop Start Stop Start Stop Start Stop Start Stop Start Stop

chnl=0 chnl=0 chnl=0 chnl=0 chnl=0 chnl=0 chnl=0 chnl=0 chnl=0 chnl=0 chnl=0 chnl=0

Use this command only for testing problems in a controlled environment. This command can generate significant amounts of output. If there is any significant amount of traffic flow when you issue the command, the processor may slow down so much that RUDP connections fail. This command is recommended for field support personnel only, and is not recommended for use without prior recommendation from Cisco. The following is an example of debug ss7 mtp2 txc command output for channel 2. The transmission control is functioning and updating backward sequence numbers (BSNs). See the MTP2 specification for details: Router# debug ss7 mtp2 txc 2 *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1 1 1 1 1 1 1

01:10:13.831: 01:10:13.831: 01:10:13.831: 01:10:13.839: 01:10:13.863: 01:10:13.863: 01:10:23.603: 01:10:23.627: 01:10:23.627: 01:10:23.631: 01:10:23.631: 01:10:23.635:

itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_PDU2xmit chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_PDU2xmit chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE


DB-2060

May 2008


*Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1

01:10:43.900: 01:10:43.900: 01:10:43.900: 01:10:43.908: 01:10:43.928: 01:10:43.932:

itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_PDU2xmit chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVICE itu2TXC_bsn_update chnl=2 MTP2TXC_INSERVIC

The following MTP2 specification tables explain codes that appear in the command output. Backhaul Debug Event Codes

Description

0x0

Local processor outage

0x1

Local processor outage recovered

0x2

Entered a congested state

0x3

Exited a congested state

0x4

Physical layer up

0x5

Physical layer down

0x7

Protocol error (see cause code)

0x8

Link alignment lost

0x9

Retransmit buffer full

0xa

Retransmit buffer no longer full

0xc

Remote entered congestion

0xd

Remote exited congestion

0xe

Remote entered processor outage

0xf

Remote exited processor outage

Backhaul Debug Cause Codes

Description

0x0

Cause unknown—default

0x1

Management initiated

0x2

Abnormal BSN (backward sequence number)

0x3

Abnormal FIB (Forward Indicator Bit)

0x4

Congestion discard

Backhaul Debug Reason Codes

Description

0x0

Layer management request

0x1

SUERM (Signal Unit Error Monitor) failure

0x2

Excessively long alignment period

0x3

T7 timer expired

0x4

Physical interface failure

0x5

Two or three invalid BSNs


DB-2061


Related Commands

Backhaul Debug Reason Codes

Description

0x6

Two or three invalid FIBs

0x7

LSSU (Link Status Signal Unit) condition

0x13

SIOs (Service Information Octets) received in Link State Control (LSC)

0x14

Timer T2 expired waiting for SIO

0x15

Timer T3 expired waiting for SIE/SIN

0x16

SIO received in initial alignment control (IAC)

0x17

Proving period failure

0x18

Timer T1 expired waiting for FISU (Fill-In Signal Unit)

0x19

SIN received in the in-service state

0x20

CTS lost

0x25

No resources

Command

Description

debug ss7 sm

Displays debugging messages for an SS7 Session Manager.


DB-2062

May 2008

Debug Commands debug ss7 sm

debug ss7 sm To display debugging messages for an Signaling System 7 (SS7) Session Manager, use the debug ss7 sm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ss7 sm [session session-id | set | timer] no debug ss7 sm session

Syntax Description

session

(Optional) Sets Session Manager session debug.

session-id

(Optional) Specifies a session ID number from 0 to 3.

set

(Optional) Sets Session Manager debug.

timer

(Optional) Sets Session Manager timer debug.

Defaults

Debug is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XR and 12.1(1)T


12.1(1)T


12.2(11)T

This command replaces the debug ss7 sm session command. This command was modified with the session, set, and timer keywords. This command was also modified to support up to four Session Manager sessions.

12.2SX


Usage Guidelines

Use this command to watch the Session Manager and Reliable User Data Protocol (RUDP) sessions. The Session Manager is responsible for establishing the RUDP connectivity to the Virtual Switch Controller (VSC). Support for up to four Session Manager sessions was added. Session Manager sessions are now numbered 0 to 3. This feature changes the CLI syntax, and adds sessions 2 and 3.

Examples

The following is an example of debug ss7 sm command output using the session keyword. The Session Manager has established the connection (RUDP_CONN_OPEN_SIG) for session 3. Router# debug ss7 sm session 3 *Mar *Mar

8 09:37:52.119:SM:rudp signal RUDP_SOFT_RESET_SIG, session = 3 8 09:37:58.129:SM:rudp signal RUDP_CONN_RESET_SIG, session = 3


DB-2063

Debug Commands debug ss7 sm

*Mar *Mar

8 09:37:58.129:SM:Opening session[0] to 10.5.0.4:8060 8 09:37:58.137:SM:rudp signal RUDP_CONN_OPEN_SIG, session = 3

The following is an example of debug ss7 sm session command output for session 0. The Session Manager has established the connection (RUDP_CONN_OPEN_SIG): Router# debug ss7 sm session 0 *Mar *Mar *Mar *Mar

Related Commands

8 8 8 8

09:37:52.119:SM:rudp signal RUDP_SOFT_RESET_SIG, session = 0 09:37:58.129:SM:rudp signal RUDP_CONN_RESET_SIG, session = 0 09:37:58.129:SM:Opening session[0] to 10.5.0.4:8060 09:37:58.137:SM:rudp signal RUDP_CONN_OPEN_SIG, session = 0

Command

Description

encapsulation ss7

Assigns a channel group and selects the DS0 time slots desired for SS7 links.


DB-2064

May 2008

Debug Commands debug sse

debug sse To display information for the silicon switching engine (SSE) processor, use the debug sse command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sse no debug sse

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use the debug sse command to display statistics and counters maintained by the SSE.

Examples

The following is sample output from the debug sse command: Router# debug sse SSE: SSE: SSE: SSE: SSE: SSE: SSE: SSE: SSE: SSE:

IP number of cache entries changed 273 274 bridging enabled interface Ethernet0/0 icb 0x30 addr 0x29 status 0x21A040 protos 0x11 interface Ethernet0/1 icb 0x33 addr 0x29 status 0x21A040 protos 0x11 interface Ethernet0/2 icb 0x36 addr 0x29 status 0x21A040 protos 0x10 interface Ethernet0/3 icb 0x39 addr 0x29 status 0x21A040 protos 0x11 interface Ethernet0/4 icb 0x3C addr 0x29 status 0x21A040 protos 0x10 interface Ethernet0/5 icb 0x3F addr 0x29 status 0x21A040 protos 0x11 interface Hssi1/0 icb 0x48 addr 0x122 status 0x421E080 protos 0x11 cache update took 316ms, elapsed 320ms

The following line indicates that the SSE cache is being updated due to a change in the IP fast-switching cache: SSE: IP number of cache entries changed 273 274

The following line indicates that bridging functions were enabled on the SSE: SSE: bridging enabled

The following lines indicate that the SSE is now loaded with information about the interfaces: SSE: SSE: SSE: SSE: SSE: SSE: SSE:

interface interface interface interface interface interface interface

Ethernet0/0 Ethernet0/1 Ethernet0/2 Ethernet0/3 Ethernet0/4 Ethernet0/5 Hssi1/0 icb

icb 0x30 addr 0x29 status 0x21A040 protos 0x11 icb 0x33 addr 0x29 status 0x21A040 protos 0x11 icb 0x36 addr 0x29 status 0x21A040 protos 0x10 icb 0x39 addr 0x29 status 0x21A040 protos 0x11 icb 0x3C addr 0x29 status 0x21A040 protos 0x10 icb 0x3F addr 0x29 status 0x21A040 protos 0x11 0x48 addr 0x122 status 0x421E080 protos 0x11

The following line indicates that the SSE took 316 ms of processor time to update the SSE cache. The value of 320 ms represents the total time elapsed while the cache updates were performed. SSE: cache update took 316ms, elapsed 320ms


DB-2065

Debug Commands debug ssg ctrl-errors

debug ssg ctrl-errors To display all error messages for control modules, use the debug ssg ctrl-errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg ctrl-errors no debug ssg ctrl-errors

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)DC

This command was introduced on the Cisco 6400 node route processor.

12.2(4)B

This command was integrated into Cisco IOS Release 12.2(4)B.

12.2(8)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command to show error messages for the control modules. These modules include all those that manage the user authentication and service login and logout (RADIUS, PPP, Subblock, and Accounting). An error message is the result of an error detected during normal execution.

Examples

The following output is generated by using the debug ssg ctrl-errors command when a host logs in to and logs out of a service: Router# debug ssg ctrl-errors Mar 29 13:51:30 [192.168.5.1.15.21] 59:00:15:38:%VPDN-6-AUTHORERR:L2F NAS LowSlot6 cannot locate a AAA server for Vi6 user User1 Mar 29 13:51:31 [192.168.5.1.15.21] 60:00:15:39:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access6, changed state to down

Related Commands

Command

Description

debug ssg ctrl-events

Displays all event messages for control modules.

debug ssg ctrl-packets

Displays packet contents handled by control modules.


DB-2066

May 2008

Debug Commands debug ssg ctrl-events

debug ssg ctrl-events To display all event messages for control modules, use the debug ssg ctrl-events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg ctrl-events no debug ssg ctrl-events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)DC


12.2(4)B


12.2(8)T


12.2(33)SRA


12.2SX


Usage Guidelines

This command displays event messages for the control modules, which include all modules that manage the user authentication and service login and logout (RADIUS, PPP, Subblock, and Accounting). An event message is an informational message generated during normal execution.

Examples

The following output is generated by the debug ssg ctrl-events command when a host logs in to a service: Router# debug ssg ctrl-events Mar 16 16:20:30 [192.168.6.1.7.141] 799:02:26:51:SSG-CTL-EVN:Service logon is accepted. Mar 16 16:20:30 [192.168.6.1.7.141] 800:02:26:51:SSG-CTL-EVN:Send cmd 11 to host 172.16.6.13. dst=192.168.100.24:36613

Related Commands

Command

Description

debug ssg ctrl-packets

Displays packet contents handled by control modules.

ssg local-forwarding

Displays all error messages for control modules.


DB-2067

Debug Commands debug ssg ctrl-packets

debug ssg ctrl-packets To display packet contents handled by control modules, use the debug ssg ctrl-packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg ctrl-packets no debug ssg ctrl-packets

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)DC


12.2(4)B


12.2(8)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use this command to show packet messages for the control modules. These modules include all those that manage the user authentication and service login and logout (RADIUS, PPP, Subblock, and Accounting). A packet message displays the contents of a package.

Examples

The following output is generated by using the debug ssg ctrl-packets command when a host logs out of a service: Router# debug ssg ctrl-packets Mar Mar Mar Mar

16 16 16 16

16:23:38 16:23:38 16:23:39 16:23:39

[192.168.6.1.7.141] [192.168.6.1.7.141] [192.168.6.1.7.141] [192.168.6.1.7.141]

968:02:30:00:SSG-CTL-PAK:Received Packet: 980:02:30:00:SSG-CTL-PAK:Sent packet: 991:02:30:00:SSG-CTL-PAK: 992:Received Packet:


DB-2068

May 2008

Debug Commands debug ssg ctrl-packets

Related Commands

Command

Description

debug ssg ctrl-events

Displays all event messages for control modules.

ssg local-forwarding

Enables NRP-SSG to forward packets locally.


DB-2069

Debug Commands debug ssg data

debug ssg data To display all data-path packets, use the debug ssg data command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg data no debug ssg data

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)DC


12.2(4)B


12.2(8)T


12.2(33)SRA


12.2SX


Usage Guidelines

The debug ssg data command shows packets for the data modules. These modules include all those that forward data packets (Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), tunneling, fast switching, IP stream, and multicast).

Examples

The following output is generated by using the debug ssg data command when a host logs in to and out of a service: Router# debug ssg data Mar 29 13:45:16 [192.168.5.1.15.21] 45:00:09:24: SSG-DATA:PS-UP-SetPakOutput=1(Vi6:172.16.5.50->199.199.199.199) Mar 29 13:45:16 [192.168.5.1.15.21] 46:00:09:24: SSG-DATA:PS-DN-SetPakOutput=1(Fa0/0/0:171.69.2.132->172.16.5.50) Mar 29 13:45:16 [192.168.5.1.15.21] 47:00:09:24: SSG-DATA:FS-UP-SetPakOutput=1(Vi6:172.16.5.50->171.69.43.34) Mar 29 13:45:16 [192.168.5.1.15.21] 48:00:09:24:


DB-2070

May 2008

Debug Commands debug ssg data

Related Commands

Command

Description

debug ssg data-nat

Displays all data-path packets for NAT processing.


DB-2071

Debug Commands debug ssg data-nat

debug ssg data-nat To display all data-path packets for Network Address Translation (NAT) processing, use the debug ssg data-nat command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg data-nat no debug ssg data-nat

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)DC


12.2(4)B


12.2(8)T


12.2(33)SRA


12.2SX


Usage Guidelines

The debug ssg data-nat command displays packets for the data modules. These modules include all those that forward NAT data packets.

Examples

The following output is generated by using the debug ssg data-nat command when a host logs in to and out of a service: Router# debug ssg data-nat Mar 29 13:43:14 [192.168.5.1.15.21] 199.199.199.199->171.69.2.132 Mar 29 13:43:14 [192.168.5.1.15.21] 171.69.2.132->199.199.199.199 Mar 29 13:43:30 [192.168.5.1.15.21] 199.199.199.199->171.69.2.132 Mar 29 13:43:30 [192.168.5.1.15.21] 171.69.2.132->199.199.199.199

35:00:07:21:SSG-DATA:TranslateIP Dst 36:00:07:21:SSG-DATA:TranslateIP Src 39:00:07:38:SSG-DATA:TranslateIP Dst 40:00:07:38:SSG-DATA:TranslateIP Src


DB-2072

May 2008

Debug Commands debug ssg data-nat

Related Commands

Command

Description

debug ssg data

Displays all data-path packets.


DB-2073

Debug Commands debug ssg dhcp

debug ssg dhcp To enable the display of control errors and events related to Service Selection Gateway (SSG) Dynamic Host Configuration Protocol (DHCP), use the debug ssg dhcp command in privileged EXEC mode. To stop debugging, use the no form of this command. debug ssg dhcp{error | event} [ip-address] no debug ssg dhcp{error | event} [ip-address]

Syntax Description

error

Enables the display of SSG-DHCP control error information.

event

Enables the display of SSG-DHCP control events information.

ip-address

(Optional) Limits the display of information to the specified IP address.

Command Default

Displays SSG-DHCP information for all IP addresses.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Examples

SSG DHCP Event Messages

The following example shows user login events when DHCP intercept is enabled using the ssg intercept dhcp command. debug ssg dhcp 01:01:03: DHCPD: remote id 020a000005010101100000000000 01:01:03: DHCPD: circuit id 00000000 01:01:03: SSG-DHCP-EVN: DHCP-DISCOVER event received. SSG-dhcp awareness feature enabled 01:01:03: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d30.3030.632e.3331.6561.2e61.3963.312d.4661.302f.31 on interface FastEthernet1/0. 01:01:03: DHCPD: Seeing if there is an internally specified pool class: 01:01:03: DHCPD: htype 1 chaddr 000c.31ea.a9c1 01:01:03: DHCPD: remote id 020a000005010101100000000000 01:01:03: DHCPD: circuit id 00000000 01:01:03: SSG-DHCP-EVN: Get pool name called for 000c.31ea.a9c1. No hostobject 01:01:03: SSG-DHCP-EVN: Get pool class called, class name = 01:01:03: DHCPD: No internally specified class returned 01:01:03: DHCPD: Sending DHCPOFFER to client 0063.6973.636f.2d30.3030.632e.3331.6561.2e61.3963.312d.4661.302f.31 (5.1.1.2). 01:01:03: DHCPD: child pool: 5.1.1.0 / 255.255.255.0 (Default-pool) 01:01:03: DHCPD: pool Default-pool has no parent.


DB-2074

May 2008

Debug Commands debug ssg dhcp

01:01:03: DHCPD: child pool: 5.1.1.0 / 255.255.255.0 (Default-pool) 01:01:03: DHCPD: pool Default-pool has no parent. 01:01:03: DHCPD: child pool: 5.1.1.0 / 255.255.255.0 (Default-pool) 01:01:03: DHCPD: pool Default-pool has no parent. 01:01:03: DHCPD: broadcasting BOOTREPLY to client 000c.31ea.a9c1. 01:01:03: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.632e.3331.6561.2e61.3963.312d.4661.302f.31. 01:01:03: DHCPD: Sending notification of ASSIGNMENT: 01:01:03: DHCPD: address 5.1.1.2 mask 255.255.255.0 01:01:03: DHCPD: htype 1 chaddr 000c.31ea.a9c1 01:01:03: DHCPD: lease time remaining (secs) = 180 01:01:03: SSG-DHCP-EVN:5.1.1.2: IP address notification received. 01:01:03: SSG-DHCP-EVN:5.1.1.2: HostObject not present 01:01:03: DHCPD: No default domain to append - abort update 01:01:03: DHCPD: Sending DHCPACK to client 0063.6973.636f.2d30.3030.632e.3331.6561.2e61.3963.312d.4661.302f.31 (5.1.1.2). 01:01:03: DHCPD: child pool: 5.1.1.0 / 255.255.255.0 (Default-pool) 01:01:03: DHCPD: pool Default-pool has no parent. 01:01:03: DHCPD: child pool: 5.1.1.0 / 255.255.255.0 (Default-pool) 01:01:03: DHCPD: pool Default-pool has no parent. 01:01:03: DHCPD: child pool: 5.1.1.0 / 255.255.255.0 (Default-pool) 01:01:03: DHCPD: pool Default-pool has no parent. 01:01:03: DHCPD: broadcasting BOOTREPLY to client 000c.31ea.a9c1.

SSG DHCP Error Messages

The following example shows user login errors when a user tries to log into two different services that require IP addresses to be assigned from different pools. debug ssg dhcp error 01:21:58: SSG-CTL-EVN: Checking maximum service count. 01:21:58: SSG-CTL-EVN: Service logon is accepted. 01:21:58: SSG-CTL-EVN: Activating the ConnectionObject. 01:21:58: SSG-DHCP-ERR:6.2.1.2: DHCP pool name of this service is different from, already logged in service DHCP pool name 01:21:58: SSG-CTL-EVN: Connection Activation Failed for host 6.2.1.2

users

01:21:58: SSG-CTL-EVN: Send cmd 11 to host S6.2.1.2. dst=10.76.86.90:42412 01:21:58: SSG-CTL-PAK: Sent packet: 01:21:58: RADIUS: id= 0, code= Access-Reject, len= 79

Related Commands

Command

Description

ssg intercept dhcp

Configures SSG to assign IP addresses from a user’s ISP.


DB-2075

Debug Commands debug ssg errors

debug ssg errors To display all error messages for the system modules, use the debug ssg errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg errors no debug ssg errors

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)DC


12.2(4)B


12.2(8)T


12.2(33)SRA


12.2SX


Usage Guidelines

The debug ssg errors command displays error messages for the system modules, which include the basic Cisco IOS and other support modules (such as Object Model, Timeout, and Initialization). An error message is the result of an error detected during normal execution.

Examples

The following output is generated by using the debug ssg errors command when a PPP over Ethernet (PPPoE) client logs in with an incorrect password: Router# debug ssg errors Mar 16 08:46:20 [192.168.6.1.7.141] 225:00:16:06:SSG:SSGDoAccounting: reg_invoke_do_acct returns FALSE

Related Commands

Command

Description

debug ssg events

Displays event messages for system modules.

debug ssg packets

Displays packet contents handled by system modules.


DB-2076

May 2008

Debug Commands debug ssg events

debug ssg events To display event messages for system modules, use the debug ssg events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg events no debug ssg events

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)DC


12.2(4)B


12.2(8)T


12.2(33)SRA


12.2SX


Usage Guidelines

The debug ssg events command displays event messages for the system modules, which include the basic Cisco IOS modules and other support modules (such as Object Model, Timeout, and Initialization). An event message is an informational message that appears during normal execution.

Examples

The following output is generated by using the debug ssg events command when a PPP over Ethernet (PPPoE) client logs in with the username “username” and the password “cisco”: Router# debug ssg events Mar 16 08:39:39 [192.168.6.1.7.141] 167:00:09:24:%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up Mar 16 08:39:39 [192.168.6.1.7.141] 168:00:09:25:%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up Mar 16 08:39:40 [192.168.6.1.7.141] 169:00:09:26:%VPDN-6-AUTHORERR:L2F NAS LowSlot7 cannot locate a AAA server for Vi3 user username Mar 16 08:39:40 [192.168.6.1.7.141] 170:HostObject::HostObject:size = 256 Mar 16 08:39:40 [192.168.6.1.7.141] 171:HostObject::Reset Mar 16 08:39:40 [192.168.6.1.7.141] 172:Service List: Mar 16 08:39:40 [192.168.6.1.7.141] 175:Service = isp-1


DB-2077

Debug Commands debug ssg events

Related Commands

Command

Description

debug ssg error

Displays all error messages for the system modules.

debug ssg packets

Displays packet contents handled by system modules.


DB-2078

May 2008

Debug Commands debug ssg packets

debug ssg packets Note

Effective with Release 12.2(13)T, the debug ssg packets command is replaced by the debug ssg tcp-redirect command. See the debug ssg tcp-redirect command for more information. To display packet contents handled by system modules, use the debug ssg packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg packets no debug ssg packets

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)DC


12.2(4)B


12.2(8)T


12.2(13)T

This command was replaced by the debug ssg tcp-redirect command.

12.2(33)SRA


12.2SX


Usage Guidelines

The debug ssg packets command displays packet messages for the system modules, which include the basic Cisco IOS and other support modules (such as Object Model, Timeout, Initialization). A packet message displays the contents of a package.

Examples

The following output is generated by using the debug ssg packets command when a user is running a Telnet session to 192.168.250.12 and pinging 192.168.250.11: Router# debug ssg packets 19:46:03:SSG-DATA:PS-UP-SetPakOutput=1(Vi2:172.16.17.71->192.168.250.12) 19:46:03:SSG-DATA:PS-UP-SetPakOutput=1(Vi2:172.16.17.71->192.168.250.12) 19:46:03:SSG-DATA:PS-UP-SetPakOutput=1(Vi3:172.16.17.72->192.168.250.12) 19:46:03:SSG-DATA:PS-UP-SetPakOutput=1(Vi2:172.16.17.71->192.168.250.12) 19:46:03:SSG-DATA:PS-UP-SetPakOutput=1(Vi2:172.16.17.71->192.168.250.12)


DB-2079

Debug Commands debug ssg packets

19:46:03:SSG-DATA:PS-UP-SetPakOutput=1(Vi2:172.16.17.71->192.168.250.12) 19:46:03:SSG-DATA:PS-UP-SetPakOutput=1(Vi3:172.16.17.72->192.168.250.11)

Related Commands

Command

Description

debug ssg errors

Displays all error messages for the system modules.

debug ssg events

Displays event messages for system modules.


DB-2080

May 2008

Debug Commands debug ssg port-map

debug ssg port-map To display debugging messages for port-mapping, use the debug ssg port-map command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg port-map {events | packets} no debug ssg port-map {events | packets}

Syntax Description

events

Displays messages for port-map events: create and remove.

packets

Displays port-map packet contents and port address translations.

Defaults

This command is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)B

This command was introduced on the Cisco 6400 series.

12.2(2)XB


12.2(13)T


12.2(33)SRA


12.2SX


Usage Guidelines

This command displays debugging messages for the creation of port maps.

Examples

Using the debug ssg port-map command generates the following output when a subscriber logs in to a service: Router# debug ssg port-map events SSG port-map events debugging is on Router# show debug SSG: SSG port-map events debugging is on Router# 00:46:09:SSG-PMAP:Changing state of port-bundle 70.13.60.3:65 from FREE to RESERVED 00:46:09:SSG-PMAP:Changing state of port-bundle 70.13.60.3:65 from RESERVED to INUSE 00:46:10:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access2, changed state to up Router# 00:46:25:SSG-PMAP:Allocating new port-mapping:[41481040] for port-bundle 70.13.60.3:65


DB-2081

Debug Commands debug ssg port-map

00:46:29:SSG-PMAP:Allocating 00:46:31:SSG-PMAP:Allocating 00:46:31:SSG-PMAP:Allocating 00:46:31:SSG-PMAP:Allocating

new new new new

port-mapping:[41491041] port-mapping:[41501042] port-mapping:[41511043] port-mapping:[41521044]

for for for for

port-bundle port-bundle port-bundle port-bundle

70.13.60.3:65 70.13.60.3:65 70.13.60.3:65 70.13.60.3:65

Router# debug ssg port-map packets SSG port-map packets debugging is on Router# 00:51:55:SSG-PMAP:forwarding non-TCP packet 00:51:55:SSG-PMAP:forwarding packet 00:51:55:SSG-PMAP:forwarding non-TCP packet 00:51:55:SSG-PMAP:forwarding packet 00:51:55:SSG-PMAP:forwarding non-TCP packet 00:52:06:SSG-PMAP:srcip:70.13.6.100 srcport:8080 dstip:70.13.60.3 dstport:1044 00:52:06:SSG-PMAP:TCP flags:5011 Seq no:1162897784 Ack no:-1232234715 00:52:06:SSG-PMAP:received TCP-FIN packet 00:52:10:SSG-PMAP:cef:packet bound for default n/w 00:52:10:SSG-PMAP:Checking port-map ACLs 00:52:10:SSG-PMAP:Port-map ACL check passed 00:52:10:SSG-PMAP:cef:punting TCP-SYN packet to process 00:52:10:SSG-PMAP:packet bound for default n/w 00:52:10:SSG-PMAP:fast:punting TCP-SYN packet to process 00:52:10:SSG-PMAP:packet bound for default n/w 00:52:10:SSG-PMAP:translating source address from 10.3.6.1 to 70.13.60.3 00:52:10:SSG-PMAP:translating source port from 4158 to 1040 00:52:10:SSG-PMAP:srcip:70.13.6.100 srcport:8080 dstip:70.13.60.3 dstport:1040 00:52:10:SSG-PMAP:TCP flags:6012 Seq no:1186352744 Ack no:-1232047701 00:52:10:SSG-PMAP:translating destination address from 70.13.60.3 to 10.3.6.1 00:52:10:SSG-PMAP:translating destination port from 1040 to 4158

Related Commands

Command

Description

show ssg port-map ip

Displays information on a particular port bundle.

show ssg port-map status

Displays information on port bundles.


DB-2082

May 2008

Debug Commands debug ssg tcp-redirect

debug ssg tcp-redirect To turn on debug information for the Service Selection Gateway (SSG) Transport Control Protocol (TCP) Redirect for Services feature, use the debug ssg tcp-redirect command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg tcp-redirect {packet | error | event} no debug ssg tcp-redirect {packet | error | event}

Syntax Description

packet

Displays redirection information and any changes made to a packet when it is due for redirection.

error

Displays any SSG TCP redirect errors.

event

Displays any major SSG TCP redirect events or state changes.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(4)B


12.2(2)XB

This command was integrated in Cisco IOS Release 12.2(2)XB.

12.2(13)T

This command was integrated into Cisco IOS Release 12.2(13)T. This command replaces the debug ssg packets command.

12.2(33)SRA


12.2SX


Usage Guidelines

Use this command to turn on debug information for the SSG TCP Redirect for Services feature. Use the packet keyword to display redirection information and any changes made to a packet when it is due for redirection. Use the error keyword to display any SSG TCP redirect errors. Use the event keyword to display any major SSG TCP redirect events or state changes.

Examples

The following example shows how to display redirection information and any changes made to a packet when it is due for redirection: Router# debug ssg tcp-redirect packet

Direction of the packet “-Up” indicates upstream packets from an SSG user, while “-Down” indicates downstream packets sent to a user: 07:13:15:SSG-REDIR-PKT:-Up:unauthorised user at 111.0.0.2 redirected to 9.2.36.253,8080


DB-2083


07:13:15:SSG-REDIR-PKT:-Down:TCP-RST Rxd for user at 111.0.0.2, port 11114 07:13:15:SSG-REDIR-PKT:-Down:return remap for user at 111.0.0.2 redirected from 9.2.36.25

The following example shows how to display any SSG TCP redirect errors: Router# debug ssg tcp-redirect error 07:15:20:SSG-REDIR-ERR:-Up:Packet from 172.0.0.2:11114 has different destination from stored connection

The following example shows how to display any major SSG TCP redirect events or state changes: Router# debug ssg tcp-redirect event

Upstream packets from users are redirected: 06:45:51:SSG-TCP-REDIR:-Up:created new remap entry for unauthorised user at 172.16.0.2 06:45:51: Redirect server set to 10.2.36.253,8080 06:45:51: Initial src/dest port mapping 1109423 06:45:51:SSG-REDIR-EVT: Freeing tcp-remap connections 06:46:21:SSG-REDIR-EVT:Host at 111.0.0.2, connection port 11094 timed out 06:46:21:SSG-REDIR-EVT: Unauthenticated user remapping for 172.16.0.2 removed

A host is being activated: 06:54:09:SSG-REDIR-EVT:- New Host at 172.16.0.2 set for default initial captivation 06:54:09:SSG-REDIR-EVT:- New Host at 172.16.0.2 set for default advertising captivation

Initial captivation begins: 06:59:32:SSG-REDIR-EVT:-Up:initial captivate got packet at start of connection (from 111.0.0.2) 06:59:32:SSG-REDIR-EVT:-Up:user at 111.0.0.2 starting initial captivation 06:59:32:SSG-REDIR-EVT:- Up:created new redirect connection and server for user at 111.0.0.2 06:59:32: Redirect server set to 10.64.131.20,8000 06:59:32: Initial src/dest port mapping 1110980 06:59:48:SSG-REDIR-EVT:-Up:initial captivate got packet at start of connection (from 111.0.0.2) 06:59:48:SSG-REDIR-EVT:-Up:initial captivate timed out for user at 172.16.0.2 06:59:48:SSG-REDIR-EVT:Removing server 10.64.131.20:8000 for host 172.16.0.2

Advertising captivation begins: 06:59:48:SSG-REDIR-EVT:Removing redirect map for host 172.16.0.2 06:59:48:SSG-REDIR-EVT:-Up:advert captivate got packet at start of connection (from 111.0.0.2) 06:59:48:SSG-REDIR-EVT:-Up:user at 111.0.0.2 starting advertisement captivation 06:59:48:SSG-REDIR-EVT:- Up:created new redirect connection and server for user at 111.0.0.2 06:59:48: Redirect server set to 10.64.131.20,8000 06:59:48: Initial src/dest port mapping 1111080

Related Commands

Command

Description

show ssg tcp-redirect group

Displays information about the captive portal groups and the networks associated with the captive portal groups.

show tcp-redirect mappings

Displays information about the TCP redirect mappings for hosts within your system.


DB-2084

May 2008


Command

Description

ssg enable

Enables SSG.

ssg tcp-redirect

Enables SSG TCP redirect and enters SSG-redirect mode.


DB-2085

Debug Commands debug ssg transparent login

debug ssg transparent login To display all the Service Selection Gateway (SSG) transparent login control events or errors, use the debug ssg transparent login command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug ssg transparent login {errors | events} [ip-address] no debug ssg transparent login {errors | events} [ip-address]

Syntax Description

errors

Displays any SSG transparent login errors.

events

Displays significant SSG transparent login events or state changes.

ip-address

(Optional) Displays events or errors for a specified IP address.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1a)BW


12.3(3)B


12.3(7)T


12.2SX


Usage Guidelines

Use this command when troubleshooting SSG for problems related to transparent autologon users.

Examples

The following examples show sample output from the debug ssg transparent login command. The output is self-explanatory. Unidentified (NR) User Example *Jan 15 12:34:47.847:SSG-TAL-EVN:100.0.0.2 *Jan 15 12:34:47.847:SSG-TAL-EVN:100.0.0.2 *Jan 15 12:34:47.847:SSG-TAL-EVN:100.0.0.2 *Jan 15 12:35:09.711:SSG-TAL-EVN:100.0.0.2 *Jan 15 12:35:09.711:SSG-TAL-EVN:100.0.0.2 unidentified *Jan 15 12:35:09.711:%SSG-5-SSG_TAL_NR:SSG might be down or overloaded. *Jan 15 12:35:09.711:SSG-TAL-EVN:100.0.0.2

:Added entry successfully :Attempting authorization :Attempting to send authorization request :Authorization response received :Authorization timedout. User statechanged to TAL :No response from AAA server. AAA server :Start SP/NR entry timeout timer for 10 mins

Transparent Pass-Through (TP) User Example *Jan *Jan *Jan *Jan

15 15 15 15

12:40:39.875:SSG-TAL-EVN:100.0.0.2 12:40:39.875:SSG-TAL-EVN:100.0.0.2 12:40:39.875:SSG-TAL-EVN:100.0.0.2 12:40:39.879:SSG-TAL-EVN:100.0.0.2

:Added entry successfully :Attempting authorization :Attempting to send authorization request :Authorization response received


DB-2086

May 2008

Debug Commands debug ssg transparent login

*Jan *Jan *Jan *Jan *Jan

15 15 15 15 15

12:40:39.879:SSG-TAL-EVN:100.0.0.2 12:40:39.879:SSG-TAL-EVN:100.0.0.2 12:40:39.879:SSG-TAL-EVN:100.0.0.2 12:40:39.879:SSG-TAL-EVN:100.0.0.2 12:40:39.879:SSG-TAL-EVN:100.0.0.2

:Parsing profile for TP attribute :TP attribute found - Transparent user :Stop SP/NR timer :Idle timer started for 0 secs :Session timer started for 0 secs

Suspect User (SP) Example *Jan 15 *Jan 15 *Jan 15 *Jan 15 *Jan 15 changed *Jan 15

12:43:25.363:SSG-TAL-EVN:10.10.10.10 12:43:25.363:SSG-TAL-EVN:10.10.10.10 12:43:25.363:SSG-TAL-EVN:10.10.10.10 12:43:25.939:SSG-TAL-EVN:10.10.10.10 12:43:25.939:SSG-TAL-EVN:10.10.10.10 to suspect 12:43:25.939:SSG-TAL-EVN:10.10.10.10

:Added entry successfully :Attempting authorization :Attempting to send authorization request :Authorization response received :Access reject from AAA server. Userstate :Start SP/NR entry timeout timer for 60 mins

Clear All Users Example

The following is sample output for the debug ssg transparent login command when used after all transparent autologon users have been cleared by using the clear ssg user transparent all command. *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan

Related Commands

15 15 15 15 15 15 15 15 15 15 15 15

12:47:08.943:SSG-TAL-EVN:10.10.10.10 :Entry removed 12:47:08.943:SSG-TAL-EVN:10.10.10.10 :Stop SP/NR timer 12:47:08.943:SSG-TAL-EVN:10.10.10.10 :Stop Idle timer 12:47:08.943:SSG-TAL-EVN:10.10.10.10 :Stop session timer 12:47:08.943:SSG-TAL-EVN:10.11.11.11 :Entry removed 12:47:08.943:SSG-TAL-EVN:10.11.11.11 :Stop SP/NR timer 12:47:08.943:SSG-TAL-EVN:10.11.11.11 :Stop Idle timer 12:47:08.943:SSG-TAL-EVN:10.11.11.11 :Stop session timer 12:47:08.943:SSG-TAL-EVN:10.0.0.2 :Entry removed 12:47:08.943:SSG-TAL-EVN:10.0.0.2 :Stop SP/NR timer 12:47:08.943:SSG-TAL-EVN:10.0.0.2 :Stop Idle timer 12:47:08.943:SSG-TAL-EVN:10.0.0.2 :Stop session timer

Command

Description

ssg login transparent

Enables the SSG Transparent Autologon feature.


DB-2087

Debug Commands debug ssm

debug ssm To display diagnostic information about the Segment Switching Manager (SSM) for switched Layer 2 segments, use the debug ssm command in privileged EXEC mode. To disable debugging, use the no form of this command. debug ssm {cm errors | cm events | fhm errors | fhm events | sm errors | sm events | sm counters | xdr} no debug ssm {cm errors | cm events | fhm errors | fhm events | sm errors | sm events | sm counters | xdr}

Syntax Description

cm errors

Displays Connection Manager (CM) errors.

cm events

Displays CM events.

fhm errors

Displays Feature Handler Manager (FHM) errors.

fhm events

Displays FHM events.

sm errors

Displays Segment Handler Manager (SM) errors.

sm events

Displays SM events.

sm counters

Displays SM counters.

xdr

Displays external data representation (XDR) messages related to traffic sent across the backplane between Router Processors and line cards.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(26)S


Usage Guidelines

12.2(25)S

This command was integrated to Cisco IOS Release 12.2(25)S.

12.2(28)SB


12.2(33)SRA


12.4(11)T


12.2(33)SXH


12.2SX


The SSM manages the data-plane component of the Layer 2 Virtual Private Network (L2VPN) configuration. The CM tracks the connection-level errors and events that occur on an xconnect. The SM tracks the per-segment events and errors on the xconnect. Use the debug ssm command to troubleshoot problems in bringing up the data plane. This command is generally used only by Cisco engineers for internal debugging of SSM processes.


DB-2088

May 2008


Examples

The following example shows sample output for the debug ssm xdr command: Router# debug ssm xdr SSM xdr debugging is on 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d: 2w5d:

SSM XDR: [4096] deallocate segment, len 16 SSM XDR: [8193] deallocate segment, len 16 %LINK-3-UPDOWN: Interface FastEthernet2/1, changed state %LINK-3-UPDOWN: Interface FastEthernet2/1, changed state SSM XDR: [4102] provision segment, switch 4101, len 106 SSM XDR: [4102] update segment status, len 17 SSM XDR: [8199] provision segment, switch 4101, len 206 SSM XDR: [4102] update segment status, len 17 %SYS-5-CONFIG_I: Configured from console by console %LINK-3-UPDOWN: Interface FastEthernet2/1, changed state SSM XDR: [4102] update segment status, len 17 %LINK-3-UPDOWN: Interface FastEthernet2/1, changed state SSM XDR: [4102] deallocate segment, len 16 SSM XDR: [8199] deallocate segment, len 16 SSM XDR: [4104] provision segment, switch 4102, len 106 SSM XDR: [4104] update segment status, len 17 SSM XDR: [8201] provision segment, switch 4102, len 206 SSM XDR: [4104] update segment status, len 17 SSM XDR: [4104] update segment status, len 17 %SYS-5-CONFIG_I: Configured from console by console

to down to up

to down to up

The following example shows the events that occur on the segment manager when an Any Transport over MPLS (AToM) virtual circuit (VC) configured for Ethernet over MPLS is shut down and then enabled: Router# debug ssm sm events SSM Connection Manager events debugging is on Router(config)# interface fastethernet 0/1/0.1 Router(config-subif)# shutdown 09:13:38.159: 09:13:38.159: 09:13:38.159: 09:13:38.159: 09:13:38.159: 09:13:38.159: 09:13:38.159: 09:13:38.159:

SSM SSM SSM SSM SSM SSM SSM SSM

SM: SM: SM: SM: SM: SM: SM: SM:

[SSS:AToM:36928] event Unprovison segment [SSS:Ethernet Vlan:4146] event Unbind segment [SSS:AToM:36928] free segment class [SSS:AToM:36928] free segment [SSS:AToM:36928] event Free segment last segment class freed [SSS:Ethernet Vlan:4146] segment ready [SSS:Ethernet Vlan:4146] event Found segment data

Router(config-subif)# no shutdown 09:13:45.815: 09:13:45.815: 09:13:45.815: 09:13:45.815: 09:13:45.815: 09:13:45.815:

SSM SM: [SSS:AToM:36929] event Provison segment label_oce_get_label_bundle: flags 14 label 16 SSM SM: [SSS:AToM:36929] segment ready SSM SM: [SSS:AToM:36929] event Found segment data SSM SM: [SSS:AToM:36929] event Bind segment SSM SM: [SSS:Ethernet Vlan:4146] event Bind segment

The following example shows the events that occur on the CM when an AToM VC configured for Ethernet over MPLS is shut down and then enabled: Router(config)# interface fastethernet 0/1/0.1 Router(config-subif)# shutdown 09:17:20.179: SSM CM: [AToM] unprovision segment, id 36929 09:17:20.179: SSM CM: CM FSM: state Open - event Free segment 09:17:20.179: SSM CM: [SSS:AToM:36929] unprovision segment 1


DB-2089


09:17:20.179: 09:17:20.179: 09:17:20.179: 09:17:20.179: 09:17:20.179:

SSM SSM SSM SSM SSM

CM: CM: CM: CM: CM:

[SSS:AToM] shQ request send unprovision complete event [SSS:Ethernet Vlan:4146] unbind segment 2 [SSS:Ethernet Vlan] shQ request send ready event SM msg event send unprovision complete event SM msg event send ready event

Router(config-subif)# no shutdown 09:17:35.879: 09:17:35.879: 09:17:35.879: 09:17:35.879: 09:17:35.879: 09:17:35.879: 09:17:35.883: 09:17:35.883:

SSM SSM SSM SSM SSM SSM SSM SSM

CM: CM: CM: CM: CM: CM: CM: CM:

Query AToM to Ethernet Vlan switching, enabled [AToM] provision second segment, id 36930 CM FSM: state Down - event Provision segment [SSS:AToM:36930] provision segment 2 [AToM] send client event 6, id 36930 [SSS:AToM] shQ request send ready event SM msg event send ready event [AToM] send client event 3, id 36930

The following example shows the events that occur on the CM and SM when an AToM VC is provisioned and then unprovisioned: Router# debug ssm cm events SSM Connection Manager events debugging is on Router# debug ssm sm events SSM Segment Manager events debugging is on Router# configure terminal Router(config)# interface ethernet1/0 Router(config-if)# xconnect 10.55.55.2 101 pw-class mpls 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34: 16:57:34:

SSM CM: provision switch event, switch id 86040 SSM CM: [Ethernet] provision first segment, id 12313 SSM CM: CM FSM: state Idle - event Provision segment SSM CM: [SSS:Ethernet:12313] provision segment 1 SSM SM: [SSS:Ethernet:12313] event Provison segment SSM CM: [SSS:Ethernet] shQ request send ready event SSM CM: SM msg event send ready event SSM SM: [SSS:Ethernet:12313] segment ready SSM SM: [SSS:Ethernet:12313] event Found segment data SSM CM: Query AToM to Ethernet switching, enabled SSM CM: [AToM] provision second segment, id 16410 SSM CM: CM FSM: state Down - event Provision segment SSM CM: [SSS:AToM:16410] provision segment 2 SSM SM: [SSS:AToM:16410] event Provison segment SSM CM: [AToM] send client event 6, id 16410 label_oce_get_label_bundle: flags 14 label 19 SSM CM: [SSS:AToM] shQ request send ready event SSM CM: SM msg event send ready event SSM SM: [SSS:AToM:16410] segment ready SSM SM: [SSS:AToM:16410] event Found segment data SSM SM: [SSS:AToM:16410] event Bind segment SSM SM: [SSS:Ethernet:12313] event Bind segment SSM CM: [AToM] send client event 3, id 16410

Router# configure terminal Router(config)# interface e1/0 Router(config-if)# no xconnect 16:57:26: 16:57:26: 16:57:26: 16:57:26:

SSM SSM SSM SSM

CM: CM: CM: SM:

[Ethernet] unprovision segment, id 16387 CM FSM: state Open - event Free segment [SSS:Ethernet:16387] unprovision segment 1 [SSS:Ethernet:16387] event Unprovison segment


DB-2090

May 2008


16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26: 16:57:26:

Related Commands

SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM

CM: CM: SM: CM: SM: SM: SM: SM: CM: CM: CM: SM: CM: CM: CM: SM: CM: CM: SM: SM: SM: SM:

[SSS:Ethernet] shQ request send unprovision complete event [SSS:AToM:86036] unbind segment 2 [SSS:AToM:86036] event Unbind segment SM msg event send unprovision complete event [SSS:Ethernet:16387] free segment class [SSS:Ethernet:16387] free segment [SSS:Ethernet:16387] event Free segment last segment class freed unprovision switch event, switch id 12290 [SSS:AToM] shQ request send unready event SM msg event send unready event [SSS:AToM:86036] event Unbind segment [AToM] unprovision segment, id 86036 CM FSM: state Down - event Free segment [SSS:AToM:86036] unprovision segment 2 [SSS:AToM:86036] event Unprovison segment [SSS:AToM] shQ request send unprovision complete event SM msg event send unprovision complete event [SSS:AToM:86036] free segment class [SSS:AToM:86036] free segment [SSS:AToM:86036] event Free segment last segment class freed

Command

Description

show ssm

Displays SSM information for switched Layer 2 segments.


DB-2091

Debug Commands debug sss aaa authorization event

debug sss aaa authorization event To display messages about authentication, authorization, and accounting (AAA) authorization events that are part of normal call establishment, use the debug sss aaa authorization event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sss aaa authorization event no debug sss aaa authorization event

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T


12.2(28)SB


12.2SX


Examples

The following is sample output of several Subscriber Service Switch (SSS) debug commands including the debug sss aaa authorization event command. The reports from these commands should be sent to technical personnel at Cisco Systems for evaluation. Router# Router# Router# Router# Router# SSS: SSS SSS SSS SSS SSS

debug debug debug debug debug

sss sss sss sss sss

event error state aaa authorization event aaa authorization fsm

events debugging is on error debugging is on fsm debugging is on AAA authorization event debugging is on AAA authorization FSM debugging is on

*Mar 4 21:33:18.248: SSS INFO: Element type *Mar 4 21:33:18.248: SSS INFO: Element type *Mar 4 21:33:18.248: SSS INFO: Element type *Mar 4 21:33:18.248: SSS INFO: Element type *Mar 4 21:33:18.248: SSS INFO: Element type *Mar 4 21:33:18.248: SSS INFO: Element type *Mar 4 21:33:18.248: SSS MGR [uid:7]: Event wait-for-req to wait-for-auth

is Access-Type, long value is 3 is Switch-Id, long value is -1509949436 is Nasport, ptr value is 6396882C is AAA-Id, long value is 7 is AAA-ACCT_ENBL, long value is 1 is AccIe-Hdl, ptr value is 78000006 service-request, state changed from


DB-2092

May 2008

Debug Commands debug sss aaa authorization event

*Mar 4 21:33:18.248: SSS MGR [uid:7]: Handling Policy Authorize (1 pending sessions) *Mar 4 21:33:18.248: SSS PM [uid:7]: Need the following key: Unauth-User *Mar 4 21:33:18.248: SSS PM [uid:7]: Received Service Request *Mar 4 21:33:18.248: SSS PM [uid:7]: Event , State: initial-req to need-init-keys *Mar 4 21:33:18.248: SSS PM [uid:7]: Policy reply - Need more keys *Mar 4 21:33:18.248: SSS MGR [uid:7]: Got reply Need-More-Keys from PM *Mar 4 21:33:18.248: SSS MGR [uid:7]: Event policy-or-mgr-more-keys, state changed from wait-for-auth to wait-for-req *Mar 4 21:33:18.248: SSS MGR [uid:7]: Handling More-Keys event *Mar 4 21:33:20.256: SSS INFO: Element type is Unauth-User, string value is [email protected] *Mar 4 21:33:20.256: SSS INFO: Element type is AccIe-Hdl, ptr value is 78000006 *Mar 4 21:33:20.256: SSS INFO: Element type is AAA-Id, long value is 7 *Mar 4 21:33:20.256: SSS INFO: Element type is Access-Type, long value is 0 *Mar 4 21:33:20.256: SSS MGR [uid:7]: Event service-request, state changed from wait-for-req to wait-for-auth *Mar 4 21:33:20.256: SSS MGR [uid:7]: Handling Policy Authorize (1 pending sessions) *Mar 4 21:33:20.256: SSS PM [uid:7]: Received More Initial Keys *Mar 4 21:33:20.256: SSS PM [uid:7]: Event , State: need-init-keys to check-auth-needed *Mar 4 21:33:20.256: SSS PM [uid:7]: Handling Authorization Check *Mar 4 21:33:20.256: SSS PM [uid:7]: Event , State: check-auth-needed to authorizing *Mar 4 21:33:20.256: SSS PM [uid:7]: Handling AAA service Authorization *Mar 4 21:33:20.256: SSS PM [uid:7]: Sending authorization request for 'example.com' *Mar 4 21:33:20.256: SSS AAA AUTHOR [uid:7]:Event , state changed from idle to authorizing *Mar 4 21:33:20.256: SSS AAA AUTHOR [uid:7]:Authorizing key xyz.com *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:AAA request sent for key example.com *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Received an AAA pass *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Event , state changed from authorizing to complete *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Found service info for key example.com *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Event , state changed from complete to terminal *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Free request *Mar 4 21:33:20.264: SSS PM [uid:7]: Event , State: authorizing to end *Mar 4 21:33:20.264: SSS PM [uid:7]: Handling Service Direction *Mar 4 21:33:20.264: SSS PM [uid:7]: Policy reply - Forwarding *Mar 4 21:33:20.264: SSS MGR [uid:7]: Got reply Forwarding from PM *Mar 4 21:33:20.264: SSS MGR [uid:7]: Event policy-start-service-fsp, state changed from wait-for-auth to wait-for-service *Mar 4 21:33:20.264: SSS MGR [uid:7]: Handling Connect-Forwarding-Service event *Mar 4 21:33:20.272: SSS MGR [uid:7]: Event service-fsp-connected, state changed from wait-for-service to connected *Mar 4 21:33:20.272: SSS MGR [uid:7]: Handling Forwarding-Service-Connected event

Related Commands

Command

Description



debug sss error

Displays diagnostic information about errors that may occur during Subscriber Service Switch call setup.

debug sss event

Displays diagnostic information about Subscriber Service Switch call setup events.

debug sss fsm

Displays diagnostic information about the Subscriber Service Switch call setup state.


DB-2093

Debug Commands debug sss aaa authorization fsm

debug sss aaa authorization fsm To display information about authentication, authorization, and accounting (AAA) authorization state changes, use the debug sss aaa authorization fsm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sss aaa authorization fsm no debug sss aaa authorization fsm

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T


12.2(28)SB


12.2SX


Examples

The following example shows how to enter this command. See the “Examples” section of the debug sss aaa authorization event command page for an example of output. Router# debug sss aaa authorization fsm

Related Commands

Command

Description



debug sss error


debug sss event


debug sss fsm



DB-2094

May 2008

Debug Commands debug sss error

debug sss error To display diagnostic information about errors that may occur during Subscriber Service Switch (SSS) call setup, use the debug sss error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sss error no debug sss error

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T


12.2(28)SB


12.2SX


Examples

The following example shows how to enter this command. See the “Examples” section of the debug ssg transparent login command page for an example of output. Router# debug sss error

Related Commands

Command

Description





debug sss event


debug sss fsm



DB-2095

Debug Commands debug sss event

debug sss event To display diagnostic information about Subscriber Service Switch (SSS) call setup events, use the debug sss event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sss event no debug sss event

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T


12.2(28)SB


12.2SX


Examples

The following example shows how to enter this command. See the “Examples” section of the debug sss aaa authorization eventcommand page for an example of output. Router# debug sss event

Related Commands

Command

Description





debug sss error


debug sss fsm



DB-2096

May 2008

Debug Commands debug sss fsm

debug sss fsm To display diagnostic information about the Subscriber Service Switch (SSS) call setup state, use the debug sss fsm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sss fsm no debug sss fsm

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T


12.2(28)SB


12.2SX


Examples

The following example shows how to enter this command. See the “Examples” section of the debug sss aaa authorization event command page for an example of output. Router# debug sss fsm

Related Commands

Command

Description





debug sss error


debug sss event

Displays diagnostic information about the Subscriber Service Switch call setup events.


DB-2097

Debug Commands debug standby errors

debug standby errors To display error messages related to Host Standby Router Protocol (HSRP), use the debug standby errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug standby errors no debug standby errors

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1


12.2(33)SRA


12.2SX


Usage Guidelines

You can filter the debug output using interface and HSRP group conditional debugging. To enable interface conditional debugging, use the debug condition interface command. To enable HSRP conditional debugging, use the debug condition standby command.

Examples

The following example enables the display of HSRP errors: Router# debug standby errors HSRP Errors debugging is on.

Related Commands

Command

Description

debug condition standby

Filters the output of the debug standby command on the basis of HSRP group number.

debug standby









DB-2098

May 2008

Debug Commands debug standby events icmp

debug standby events icmp To display debugging messages for the Hot Standby Router Protocol (HSRP) Internet Control Message Protocol (ICMP) redirects filter, use the debug standby events icmp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug standby events icmp no debug standby events icmp

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


12.2(33)SRA


12.2SX


Usage Guidelines

This command helps you determine whether HSRP is filtering an outgoing ICMP redirect message.

Examples

The following is sample output from the debug standby events icmp command: Router# debug standby events icmp 10:35:20: SB: changing ICMP redirect sent to 20.0.0.4 for dest 30.0.0.2 10:35:20: SB: gw 20.0.0.2 -> 20.0.0.12, src 20.0.0.11 10:35:20: SB: Use HSRP virtual address 20.0.0.11 as ICMP src

If the router being redirected to is passive (HSRP enabled but no active groups), the following debugging message is displayed: 10:41:22: SB: ICMP redirect not sent to 20.0.0.4 for dest 40.0.0.3 10:41:22: SB: 20.0.0.3 does not contain an active HSRP group

If HSRP could not uniquely determine the gateway used by the host, then the following message is displayed: 10:43:08: SB: ICMP redirect not sent to 20.0.0.4 for dest 30.0.0.2 10:43:08: SB: could not uniquely determine IP address for mac 00d0.bbd3.bc22


DB-2099

Debug Commands debug standby events icmp

The following messages are also displayed if the debug ip icmp command is enabled, in which case the message prefix is changed: 10:39:09: 10:39:09: 10:39:09: 10:39:09:

Related Commands

ICMP: HSRP changing redirect sent to 20.0.0.4 for dest 30.0.0.2 ICMP: gw 20.0.0.2 -> 20.0.0.12, src 20.0.0.11 ICMP: Use HSRP virtual address 20.0.0.11 as ICMP src ICMP: redirect sent to 20.0.0.4 for dest 30.0.0.2, use gw 20.0.0.12

Command

Description

debug ip icmp

Displays information on ICMP transactions.


DB-2100

May 2008

Debug Commands debug standby events neighbor

debug standby events neighbor To display Hot Standby Router Protocol (HSRP) Bidirectional Forwarding Detection (BFD) peering events, use the debug standby events neighbor command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug standby events neighbor no debug standby events neighbor

Syntax Description


Command Default

HSRP neighbor debugging output is not displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(11)T


12.2SX


Usage Guidelines


Examples

In this example, two HSRP routers are configured as neighbors, supporting BFD peering with the debug standby events neighbor command configured. The following example shows the debug output that appears when an additional HSRP group is added to Router A: Router A RouterA# debug standby event neighbor HSRP Events debugging is on (neighbor) *Oct 3 02:57:48.587: HSRP: Fa2/0 Grp 2 Standby router is local 01:03:49: %HSRP-5-STATECHANGE: FastEthernet2/0 Grp 2 state Speak -> Standby *Oct 3 02:57:49.087: HSRP: Fa2/0 Grp 2 Active router is local *Oct 3 02:57:49.087: HSRP: Fa2/0 Grp 2 Standby router is unknown, was local 01:03:50: %HSRP-5-STATECHANGE: FastEthernet2/0 Grp 2 state Standby -> Active

Router B RouterB# debug standby event neighbor


DB-2101

Debug Commands debug standby events neighbor

HSRP Events debugging is on (neighbor) *Oct 3 10:00:28.503: HSRP: Fa2/0 Grp 2 Active router is 10.0.0.1 (no local config) *Oct 3 10:00:28.503: HSRP: Fa2/0 Nbr 10.0.0.1 active for group 2

The following example shows the debug output when an additional HSRP group is added to Router B: Router B *Oct 3 10:02:28.067: HSRP: Fa2/0 Nbr 10.0.0.1 no longer active for group 2 (Disabled) *Oct 3 10:02:28.503: HSRP: Fa2/0 Grp 2 Active router is 10.0.0.1 *Oct 3 10:02:28.503: HSRP: Fa2/0 Nbr 10.0.0.1 active for group 2 *Oct 3 10:02:48.071: HSRP: Fa2/0 Grp 2 Standby router is local 00:44:28: %HSRP-5-STATECHANGE: FastEthernet2/0 Grp 2 state Speak -> Standby

Router A *Oct *Oct

3 03:00:08.655: HSRP: Fa2/0 Grp 2 Standby router is 10.0.0.2 3 03:00:08.655: HSRP: Fa2/0 Nbr 10.0.0.2 standby for group 2

The following is sample debug output showing a possible network outage (the loss of signal between the ports of Router A and B): Router B *Oct 3 10:09:07.651: HSRP: Fa2/0 Grp 1 Active router is local, was 10.0.0.1 *Oct 3 10:09:07.651: HSRP: Fa2/0 Nbr 10.0.0.1 no longer active for group 1 (Standby) *Oct 3 10:09:07.651: HSRP: Fa2/0 Grp 1 Standby router is unknown, was local 00:50:48: %HSRP-5-STATECHANGE: FastEthernet2/0 Grp 1 state Standby -> Active *Oct 3 10:09:08.959: HSRP: Fa2/0 Grp 2 Active router is local, was 10.0.0.1 *Oct 3 10:09:08.959: HSRP: Fa2/0 Nbr 10.0.0.1 no longer active for group 2 (Standby) *Oct 3 10:09:08.959: HSRP: Fa2/0 Nbr 10.0.0.1 Was active or standby - start passive holddown *Oct 3 10:09:08.959: HSRP: Fa2/0 Grp 2 Standby router is unknown, was local 00:50:49: %HSRP-5-STATECHANGE: FastEthernet2/0 Grp 2 state Standby -> Active

Related Commands

Command

Description

debug bfd

Displays debugging messages about BFD.

debug condition

Limits the output for some debug commands based on specified conditions.


Limits the debugging output of HSRP state changes.

show bfd neighbor

Displays a line-by-line listing of existing BFD adjacencies.

show standby

Displays HSRP information.

show standby neighbors Displays information about HSRP neighbors. standby bfd all-interfaces

Reenables HSRP BFD peering on all interfaces if it has been disabled.

standby ip

Activates HSRP.


DB-2102

May 2008

Debug Commands debug standby events

debug standby events To display events related to Hot Standby Router Protocol (HSRP), use the debug standby events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug standby events [all | api | ha | internal | protocol | redundancy | terse | track] [detail] no debug standby events [all | ha | internal | protocol | redundancy | terse | track] [detail]

Syntax Description

all

(Optional) All HSRP events.

api

(Optional) HSRP application programming interface (API) events.

ha

(Optional) High availability (HA) events.

internal

(Optional) Internal HSRP events.

protocol

(Optional) HSRP protocol events.

redundancy

(Optional) HSRP redundancy events.

terse

(Optional) Specifies all HSRP packets, except hellos and advertisements.

track

(Optional) HSRP tracking events.

detail

(Optional) Detailed debugging information.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1


12.2(8)T

The api keyword was added.

12.4(4)T

The ha keyword was added.

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2SX


Usage Guidelines


Examples

The following example shows how to enable the debugging of the active and standby Route Processors (RPs) on an active RP console. The HSRP group is configured on the active RP, and the HSRP state is active. Router# debug standby events ha


DB-2103

Debug Commands debug standby events

!Active RP *Apr 27 04:13:47.755: *Apr 27 04:13:47.855: *Apr 27 04:13:57.755: *Apr 27 04:13:57.855: *Apr 27 04:14:07.755: *Apr 27 04:14:07.755: *Apr 27 04:14:07.863: *Apr 27 04:14:07.867: !Standby RP

HSRP: HSRP: HSRP: HSRP: HSRP: HSRP: HSRP: HSRP:

Et0/0/1 CF Sync Et0/0/1 CF Sync Et0/0/1 Et0/0/1 CF Sync CF Sync

*Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr

HSRP: HSRP: HSRP: HSRP: HSRP: HSRP: HSRP: HSRP:

RF CF client 32, entity Et0/0/1 Grp 101 RF sync RF CF client 32, entity Et0/0/1 Grp 101 RF sync RF CF client 32, entity RF CF client 32, entity Et0/0/1 Grp 101 RF sync Et0/0/1 Grp 101 RF sync

27 27 27 27 27 27 27 27

04:11:21.011: 04:11:21.011: 04:11:31.011: 04:11:31.011: 04:11:41.071: 04:11:41.071: 04:11:41.071: 04:11:41.071:

Grp 101 send ok Grp 101 send ok Grp 101 Grp 101 send ok send ok

RF Encode state Listen into sync buffer RF Encode state Speak into sync buffer RF Encode state Standby into sync buffer RF Encode state Active into sync buffer

0 got state 0 got state 0 got 0 got state state

msg len 24 Init -> Listen msg len 24 Listen -> Speak msg len 24 msg len 24 Speak -> Standby Standby -> Active


Related Commands

debug standby events Field Descriptions

Field

Description

RF

Redundancy facility—Internal mechanism that makes Stateful Switchover (SSO) work.

CF

Checkpoint facility—Internal mechanism that makes SSO work.

Command

Description


Limits output for some debug commands on the basis of the interface, VC, or VLAN.



debug standby









DB-2104

May 2008

Debug Commands debug standby packets

debug standby packets To display debugging information for packets related to Hot Standby Router Protocol (HSRP), use the debug standby packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug standby packets [advertise | all | terse | coup | hello | resign] [detail] no debug standby packet [advertise | all | terse | coup | hello | resign] [detail]

Syntax Description

advertise

(Optional) Specifies HSRP advertisement packets.

all

(Optional) Specifies all HSRP packets.

terse

(Optional) Specifies all HSRP packets, except hellos and advertisements.

coup

(Optional) Specifies HSRP coup packets.

hello

(Optional) Specifies HSRP hello packets.

resign

(Optional) Specifies HSRP resign packets.

detail

(Optional) Specifies HSRP packets in detail.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1


12.2

The advertise keyword was added.

12.2(33)SRA


12.2SX


Usage Guidelines

Note


HSRP advertisement packets are packets that are related to HSRP interfaces. Other packet types, including, hello, coup, and resign packets relate to an HSRP group.


DB-2105

Debug Commands debug standby packets

Examples

The following example show how to enable the display of all HSRP packets: Router# debug standby packets all HSRP Packets debugging is on.

Related Commands

Command

Description





debug standby






debug standby events icmp Displays debugging messages for the HSRP ICMP redirects filter.


DB-2106

May 2008

Debug Commands debug standby

debug standby To display Hot Standby Router Protocol (HSRP) state changes, use the debug standby command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug standby [terse] no debug standby [terse]

Syntax Description

terse

Command Modes

Privileged EXEC

Command History

Release

Modification

10.0


12.2SX


(Optional) Displays a limited range of HSRP errors, events, and packets.

Usage Guidelines

The debug standby command displays Hot Standby Protocol state changes and debugging information regarding transmission and receipt of Hot Standby Protocol packets. Use this command to determine whether hot standby routers recognize one another and take the proper actions.

Examples

The following is sample output from the debug standby command: Router# debug standby SB: Ethernet0 state Virgin -> Listen SB: Starting up hot standby process SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB: Ethernet0 state Listen -> Speak SB:Ethernet0 Hello out 192.168.72.20 Speak pri 100 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello out 192.168.72.20 Speak pri 100 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello out 192.168.72.20 Speak pri 100 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB: Ethernet0 state Speak -> Standby SB:Ethernet0 Hello out 192.168.72.20 Standby pri 100 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello out 192.168.72.20 Standby pri 100 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello out 192.168.72.20 Standby pri 100 hel 3 hol 10 ip 192.168.72.29 SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29 SB: Ethernet0 Coup out 192.168.72.20 Standby pri 100 hel 3 hol 10 ip 192.168.72.29 SB: Ethernet0 state Standby -> Active


DB-2107

Debug Commands debug standby

SB:Ethernet0 SB:Ethernet0 SB:Ethernet0 SB:Ethernet0 SB:Ethernet0

Hello Hello Hello Hello Hello

out 192.168.72.20 Active pri 100 hel 3 hol in 192.168.72.21 Speak pri 90 hel 3 hol 10 out 192.168.72.20 Active pri 100 hel 3 hol in 192.168.72.21 Speak pri 90 hel 3 hol 10 out 192.168.72.20 Active pri 100 hel 3 hol

10 ip 10 ip 10

ip 192.168.72.29 192.168.72.29 ip 192.168.72.29 192.168.72.29 ip 192.168.72.29


debug standby Field Descriptions

Field

Description

SB

Abbreviation for “standby.”

Ethernet0

Interface on which a Hot Standby packet was sent or received.

Hello in

Hello packet received from the specified IP address.

Hello out

Hello packet sent from the specified IP address.

pri

Priority advertised in the hello packet.

hel

Hello interval advertised in the hello packet.

hol

Hold-down interval advertised in the hello packet.

ip address

Hot Standby group IP address advertised in the hello packet.

state

Transition from one state to another.

Coup out address

Coup packet sent by the router from the specified IP address.

The following line indicates that the router is initiating the Hot Standby Protocol. The standby ip interface configuration command enables Hot Standby. SB: Starting up hot standby process

The following line indicates that a state transition occurred on the interface: SB: Ethernet0 state Listen -> Speak

Related Commands

Command

Description












DB-2108

May 2008

Debug Commands debug stun packet

debug stun packet To display information on packets traveling through the serial tunnel (STUN) links, use the debug stun packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug stun packet [group] [address] no debug stun packet [group] [address]

Syntax Description

group

(Optional) A decimal integer assigned to a group. Using this option limits output to packets associated with the specified STUN group.

address

(Optional) The output is further limited to only those packets containing the specified STUN address. The address argument is in the appropriate format for the STUN protocol running for the specified group.

Command Modes

Privileged EXEC

Usage Guidelines

Because using this command is processor intensive, it is best to use it after regular business hours, rather than in a production environment. It is also best to turn this command on by itself, rather than use it in conjunction with other debug commands.

Examples

The following is sample output from the debug stun packet command: router# debug stun packet

X2 type of packet

X3 type of packet

STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN STUN

sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc: sdlc:

0:00:04 0:00:04 0:00:01 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00 0:00:00

Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3 Serial3

NDI: NDI: SDI: SDI: SDI: SDI: SDI: SDI: SDI: SDI: SDI: SDI: SDI: SDI: NDI: SDI: SDI: SDI: SDI: SDI:

(0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008) (0C2/008)

U: U: U: S: S: S: S: S: S: S: S: S: S: S: I: I: S: S: S: S:

SNRM SNRM UA RR RR RR RR RR RR RR RR RR RR RR

RR RR RR RR

PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1 PF:1

NR:000 NR:000 NR:000 NR:000 NR:000 NR:000 NR:000 NR:000 NR:000 NR:000 NR:000 NR:000 NR:001 NR:001 NR:001 NR:001 NR:001

NS:000 NS:000

S2563

X1 type of packet


DB-2109

Debug Commands debug stun packet

The following line describes an X1 type of packet: STUN sdlc: 0:00:04 Serial3

NDI: (0C2/008) U: SNRM

PF:1

Table 327 describes the significant fields in this line of debug stun packet output. Table 327

debug stun packet Field Descriptions

Field

Description

STUN sdlc:

Indication that the STUN feature is providing the information.

0:00:04

Time elapsed since receipt of the previous packet.

Serial3

Interface type and unit number reporting the event.

NDI:

Type of cloud separating the Synchronous Data Link Control (SDL) end nodes. Possible values are as follows: •

NDI—Network input

•

SDI—Serial link

0C2

SDLC address of the SDLC connection.

008

Modulo value of 8.

U: SNRM

Frame type followed by the command or response type. In this case it is an Unnumbered frame that contains a Set Normal Response Mode (SNRM) command. The possible frame types are as follows:

PF:1

•

I—Information frame

•

S—Supervisory frame. The possible commands and responses are: RR (Receive Ready), RNR (Receive Not Ready), and REJ (Reject).

•

U—Unnumbered frame. The possible commands are: UI (Unnumbered Information), SNRM, DISC/RD (Disconnect/Request Disconnect), SIM/RIM, XID Exchange Identification), TEST. The possible responses are UA (unnumbered acknowledgment), DM (Disconnected Mode), and FRMR (Frame Reject Mode)

Poll/Final bit. Possible values are as follows: •

0—Off

•

1—On

The following line of output describes an X2 type of packet: STUN sdlc: 0:00:00 Serial3

SDI: (0C2/008) S: RR

PF:1 NR:000

All the fields in the previous line of output match those for an X1 type of packet, except the last field, which is additional. NR:000 indicates a receive count of 0; the range for the receive count is 0 to 7. The following line of output describes an X3 type of packet: STUN sdlc: 0:00:00 Serial3

SDI: (0C2/008) S:I PF:1 NR:000 NS:000

All fields in the previous line of output match those for an X2 type of packet, except the last field, which is additional. NS:000 indicates a send count of 0; the range for the send count is 0 to 7.


DB-2110

May 2008

Debug Commands debug subscriber aaa authorization

debug subscriber aaa authorization To display diagnostic information about authentication, authorization, and accounting (AAA) authorization of Intelligent Service Gateway (ISG) subscriber sessions, use the debug subscriber aaa authorization command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug subscriber aaa authorization {event | fsm} no debug sss aaa authorization {event | fsm}

Syntax Description

event

Display information about AAA authorization events that occur during ISG session establishment.

fsm

Display information about AAA authorization state changes for ISG subscriber sessions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX


Examples

The following is sample output of several debug subscriber commands, including the debug subscriber aaa authorization command. The reports from these commands should be sent to technical personnel at Cisco Systems for evaluation. Router# Router# Router# Router# Router#

debug debug debug debug debug

subscriber subscriber subscriber subscriber subscriber

event error state aaa authorization event aaa authorization fsm

SSS: SSS SSS SSS SSS SSS

events debugging is on error debugging is on fsm debugging is on AAA authorization event debugging is on AAA authorization FSM debugging is on

*Mar *Mar *Mar *Mar *Mar

4 4 4 4 4

21:33:18.248: 21:33:18.248: 21:33:18.248: 21:33:18.248: 21:33:18.248:

SSS SSS SSS SSS SSS

INFO: INFO: INFO: INFO: INFO:

Element Element Element Element Element

type type type type type

is is is is is

Access-Type, long value is 3 Switch-Id, long value is -1509949436 Nasport, ptr value is 6396882C AAA-Id, long value is 7 AAA-ACCT_ENBL, long value is 1


DB-2111

Debug Commands debug subscriber aaa authorization

*Mar 4 21:33:18.248: SSS INFO: Element type is AccIe-Hdl, ptr value is 78000006 *Mar 4 21:33:18.248: SSS MGR [uid:7]: Event service-request, state changed from wait-for-req to wait-for-auth *Mar 4 21:33:18.248: SSS MGR [uid:7]: Handling Policy Authorize (1 pending sessions) *Mar 4 21:33:18.248: SSS PM [uid:7]: Need the following key: Unauth-User *Mar 4 21:33:18.248: SSS PM [uid:7]: Received Service Request *Mar 4 21:33:18.248: SSS PM [uid:7]: Event , State: initial-req to need-init-keys *Mar 4 21:33:18.248: SSS PM [uid:7]: Policy reply - Need more keys *Mar 4 21:33:18.248: SSS MGR [uid:7]: Got reply Need-More-Keys from PM *Mar 4 21:33:18.248: SSS MGR [uid:7]: Event policy-or-mgr-more-keys, state changed from wait-for-auth to wait-for-req *Mar 4 21:33:18.248: SSS MGR [uid:7]: Handling More-Keys event *Mar 4 21:33:20.256: SSS INFO: Element type is Unauth-User, string value is [email protected] *Mar 4 21:33:20.256: SSS INFO: Element type is AccIe-Hdl, ptr value is 78000006 *Mar 4 21:33:20.256: SSS INFO: Element type is AAA-Id, long value is 7 *Mar 4 21:33:20.256: SSS INFO: Element type is Access-Type, long value is 0 *Mar 4 21:33:20.256: SSS MGR [uid:7]: Event service-request, state changed from wait-for-req to wait-for-auth *Mar 4 21:33:20.256: SSS MGR [uid:7]: Handling Policy Authorize (1 pending sessions) *Mar 4 21:33:20.256: SSS PM [uid:7]: Received More Initial Keys *Mar 4 21:33:20.256: SSS PM [uid:7]: Event , State: need-init-keys to check-auth-needed *Mar 4 21:33:20.256: SSS PM [uid:7]: Handling Authorization Check *Mar 4 21:33:20.256: SSS PM [uid:7]: Event , State: check-auth-needed to authorizing *Mar 4 21:33:20.256: SSS PM [uid:7]: Handling AAA service Authorization *Mar 4 21:33:20.256: SSS PM [uid:7]: Sending authorization request for 'xyz.com' *Mar 4 21:33:20.256: SSS AAA AUTHOR [uid:7]:Event , state changed from idle to authorizing *Mar 4 21:33:20.256: SSS AAA AUTHOR [uid:7]:Authorizing key xyz.com *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:AAA request sent for key xyz.com *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Received an AAA pass *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Event , state changed from authorizing to complete *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Found service info for key xyz.com *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Event , state changed from complete to terminal *Mar 4 21:33:20.260: SSS AAA AUTHOR [uid:7]:Free request *Mar 4 21:33:20.264: SSS PM [uid:7]: Event , State: authorizing to end *Mar 4 21:33:20.264: SSS PM [uid:7]: Handling Service Direction *Mar 4 21:33:20.264: SSS PM [uid:7]: Policy reply - Forwarding *Mar 4 21:33:20.264: SSS MGR [uid:7]: Got reply Forwarding from PM *Mar 4 21:33:20.264: SSS MGR [uid:7]: Event policy-start-service-fsp, state changed from wait-for-auth to wait-for-service *Mar 4 21:33:20.264: SSS MGR [uid:7]: Handling Connect-Forwarding-Service event *Mar 4 21:33:20.272: SSS MGR [uid:7]: Event service-fsp-connected, state changed from wait-for-service to connected *Mar 4 21:33:20.272: SSS MGR [uid:7]: Handling Forwarding-Service-Connected event

Related Commands

Command

Description

debug sss error


debug sss event


debug sss fsm



DB-2112

May 2008

Debug Commands debug subscriber error

debug subscriber error To display diagnostic information about errors that may occur during Intelligent Service Gateway (ISG) subscriber session setup, use the debug subscriber error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug subscriber error no debug subscriber error

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX


Examples

The following sample output for the debug subscriber error command indicates that the session is stale since the session handle has already been destroyed. Router# debug subscriber error *Sep 20 22:39:49.455: SSS MGR: Session handle [EF000002] destroyed already

Related Commands

Command

Description



debug sss event


debug sss fsm



DB-2113

Debug Commands debug subscriber event

debug subscriber event To display diagnostic information about Intelligent Service Gateway (ISG) subscriber session setup events, use the debug subscriber event command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug subscriber event no debug subscriber event

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX


Examples

The following sample output for the debug subscriber event commands indicates that the system has determined that the session should be locally terminated. The local termination module determines that an interface description block (IDB) is not required for this session, and it sets up the data plane for packet switching. Router# debug subscriber event *Sep 20 *Sep 20 *Sep 20 service *Sep 20 service *Sep 20

Related Commands

22:21:08.223: SSS MGR [uid:2]: Handling Connect Local Service action 22:21:08.223: SSS LTERM [uid:2]: Processing Local termination request 22:21:08.223: SSS LTERM [uid:2]: L3 session - IDB not required for setting up 22:21:08.223: SSS LTERM [uid:2]: Interface already present or not required for 22:21:08.223: SSS LTERM [uid:2]: Segment provision successful

Command

Description



debug sss error


debug sss fsm



DB-2114

May 2008

Debug Commands debug subscriber feature

debug subscriber feature To display diagnostic information about the installation and removal of Intelligent Service Gateway (ISG) features on Intelligent Service Gateway (ISG) subscriber sessions, use the debug subscriber feature command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug subscriber feature {all | detail | error | event | name name-of-feature {detail | error | event | packet} | packet [detail | full]} no debug subscriber feature {all | detail | error | event | name name-of-feature {detail | error | event | packet} | packet [detail | full]}

Syntax Description

all

Displays information about all features.

detail

The detail keyword can be used in one of the following three ways: •

If used with no other keywords, displays detailed information about all features

•

If a feature name is specified with the name name-of-feature keyword and argument, displays detailed information about the specific feature. The detail keyword can be used with the following name-of-feature values: – accounting – compression – modem-on-hold – policing – traffic-classification

•

If used with the packet keyword, displays a partial dump of packets as ISG features are being applied to the packets.

error

Displays information about errors for all features or a specified feature.

event

Displays information about events for all features or a specified feature.

name

Displays information about a specific feature.


DB-2115


name-of-feature

packet

full

Name of the ISG feature. Possible values are the following: •

access-list

•

accounting

•

compression

•

filter

•

idle-timer

•

interface-config

•

ip-config

•

l4redirect

•

modem-on-hold

•

policing

•

portbundle

•

prepaid-idle

•

session-timer

•

static-routes

•

time-monitor

•

traffic-classification

•

volume-monitor

Displays information about packets as ISG features are being applied to the packets. If a feature name is specified with the name name-of-feature keyword and argument, packet information about the specific feature is displayed. The packet keyword can be used with the following name-of-feature values: •

access-list

•

l4redirect

•

policing

•

portbundle

(Optional) Displays a full dump of a packet as ISG features are being applied to it.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX



DB-2116

May 2008


Examples

The following sample output for the debug subscriber feature command indicates that the idle timeout feature has been successfully installed on the inbound segment. Router# debug subscriber feature event *Sep 20 22:28:57.903: SSF[myservice/uid:6/Idle Timeout]: Group feature install *Sep 20 22:28:57.903: SSF[uid:6/Idle Timeout]: Adding feature to inbound segment(s)


DB-2117

Debug Commands debug subscriber fsm

debug subscriber fsm To display diagnostic information about Intelligent Service Gateway (ISG) subscriber session state change, use the debug subscriber fsm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug subscriber fsm no debug subscriber fsm

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX


Examples

The following sample output for the debug subscriber fsm command indicates that the session has been disconnected by the client, and the system is cleaning up the session by disconnecting the network service and removing any installed features. Router# debug subscriber fsm *Sep 20 22:35:10.495: SSS MGR [uid:5]: Event client-disconnect, state changed from connected to disconnecting-fsp-feat


DB-2118

May 2008

Debug Commands debug subscriber packet

debug subscriber packet To display information about packets as they traverse the subscriber service switch (SSS) path, use the debug subscriber packet command in privileged EXEC mode. To disable debugging, use the no form of this command. debug subscriber packet {detail | error | event | full} no debug subscriber packet {detail | error | event | full}

Syntax Description

detail

Displays a partial dump of packets as they traverse the SSS path.

error

Displays any packet-switching errors that occur when a packet traverses the SSS path.

event

Displays packet-switching events that occur when a packet traverses the SSS path.

full

Displays a full dump of packets as they traverse the SSS path.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX


Examples

The following example show sample output for the debug subscriber packet command with the full keyword. This output is for a PPPoE session configured with forwarding. SSS Switch: Pak encap size, old: 60, new: 24 SSS Switch: Pak 0285C458 sz 66 encap 14 *Feb 9 15:47:13.659: 000000 AA BB CC 00 0B 01 *Feb 9 15:47:13.659: 000008 CC 00 0C 01 08 00 *Feb 9 15:47:13.659: 000010 00 34 00 28 00 00 *Feb 9 15:47:13.659: 000018 F2 9D AC 12 B8 E7 *Feb 9 15:47:13.659: 000020 B8 E6 06 A5 06 A5 *Feb 9 15:47:13.659: 000028 00 00 C0 01 02 00 *Feb 9 15:47:13.659: 000030 00 01 00 18 00 00 *Feb 9 15:47:13.659: 000038 2E B3 FF 03 C2 23 *Feb 9 15:47:13.659: 000040 00 04 SSS Switch: Pak encap size, old: 60, new: 24 SSS Switch: Pak 0285C458 sz 72 encap 14 *Feb 9 15:47:13.691: 000000 AA BB CC 00 0B 01 *Feb 9 15:47:13.691: 000008 CC 00 0C 01 08 00 *Feb 9 15:47:13.691: 000010 00 3A 00 2A 00 00 *Feb 9 15:47:13.691: 000018 F2 95 AC 12 B8 E7 *Feb 9 15:47:13.691: 000020 B8 E6 06 A5 06 A5 *Feb 9 15:47:13.691: 000028 00 00 C0 01 02 00 *Feb 9 15:47:13.691: 000030 00 01 00 1E 00 00 *Feb 9 15:47:13.691: 000038 2E B3 FF 03 80 21

AA 45 FE AC 00 00 FC 03

BB 00 11 12 20 02 A7 01

D....... ......N. .4.(.... ........ ....... ........ ........ .....#.. ..

AA 45 FE AC 00 00 FC 01

BB 00 11 12 26 02 A7 01

D....... ......N. .:.*.... ........ .......& ........ ........ .....!..


DB-2119

Debug Commands debug subscriber packet

*Feb 9 15:47:13.691: 000040 00 0A 03 06 3A 3A SSS Switch: Pak encap size, old: 24, new: 46 SSS Switch: Pak 027A5BE8 sz 36 encap 18 *Feb 9 15:47:13.691: 000000 AA BB CC 00 0B 00 *Feb 9 15:47:13.691: 000008 CC 00 0A 00 81 00 *Feb 9 15:47:13.691: 000010 88 64 11 00 00 01 *Feb 9 15:47:13.691: 000018 80 21 01 01 00 0A *Feb 9 15:47:13.691: 000020 00 00 00 00 SSS Switch: Pak encap size, old: 60, new: 24 SSS Switch: Pak 0285C458 sz 72 encap 14 *Feb 9 15:47:13.691: 000000 AA BB CC 00 0B 01 *Feb 9 15:47:13.691: 000008 CC 00 0C 01 08 00 *Feb 9 15:47:13.691: 000010 00 3A 00 2C 00 00 *Feb 9 15:47:13.691: 000018 F2 93 AC 12 B8 E7 *Feb 9 15:47:13.691: 000020 B8 E6 06 A5 06 A5 *Feb 9 15:47:13.691: 000028 00 00 C0 01 02 00 *Feb 9 15:47:13.691: 000030 00 01 00 1E 00 00 *Feb 9 15:47:13.691: 000038 2E B3 FF 03 80 21 *Feb 9 15:47:13.691: 000040 00 0A 03 06 09 00

Related Commands

3A 3A

....::::

AA 01 00 03

BB 41 0C 06

D....... .......a .dN..... .!...... ....

AA 45 FE AC 00 00 FC 03 00

BB 00 11 12 26 02 A7 01 1F

D....... ......N. .:.,.... ........ .......& ........ ........ .....!.. ........

Command

Description

debug subscriber feature

Displays diagnostic information about the installation and removal of ISG features on subscriber sessions.


DB-2120

May 2008

Debug Commands debug subscriber policy

debug subscriber policy To display diagnostic information about policy execution related to Intelligent Service Gateway (ISG) subscriber sessions, use the debug subscriber policy command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug subscriber policy {all | detail | error | event | fsm | prepaid | {condition | idmgr | profile | push | rule | service} [detail | error | event] | dpm [error | event] | webportal {detail | error | event}} no debug subscriber policy {all | detail | error | event | fsm | prepaid | {condition | idmgr | profile | push | rule | service} [detail | error | event] | dpm [error | event] | webportal {detail | error | event}}

Syntax Description

all

Displays information about all policies.

detail

Displays detailed information about all policies or the specified type of policy.

error

Displays policy execution errors for all policies or the specified type of policy.

event

Displays policy execution events for all policies or the specified type of policy.

fsm

Displays information about state changes during policy execution.

prepaid

Displays information about ISG prepaid policy execution.

condition

Displays information related to the evaluation of ISG control class maps.

idmgr

Displays information about policy execution related to identity.

profile

Displays information about the policy manager subscriber profile database.

push

Displays policy information about dynamic updates to subscriber profiles from policy servers.

rule

Displays information about control policy rules.

service

Displays policy information about service profile database events for subscriber sessions.

dpm

Displays information about Dynamic Host Configuration Protocol (DHCP) in relation to subscriber sessions.

webportal

Displays policy information about the web portal in relation to subscriber sessions.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX



DB-2121

Debug Commands debug subscriber policy

Examples

The following example shows sample output for the debug subscriber policy command with the events keyword. This output indicates the creation of a new session. “Updated key list” indicates important attributes and information associated with the session. *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 0 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 0 *Feb 7 *Feb 7 Request *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7 *Feb 7

18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519:

SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS

PM PM PM PM PM PM PM PM PM PM PM PM PM PM

[0413FC58]: Create [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]:

context 0413FC58 Authen status update; is now "unauthen" Updated NAS port for AAA ID 14 Updated key list: Access-Type = 15 (IP) Protocol-Type = 4 (IP) Media-Type = 2 (IP) IP-Address = 10.0.0.2 (0A000002) IP-Address-VRF = IP 10.0.0.2:0 source-ip-address = 037FBB78 Mac-Address = aabb.cc00.6500 Final = 1 (YES) Authen-Status = 1 (Unauthenticated) Nasport = PPPoEoE: slot 0 adapter 0 port

18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519:

SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS

PM PM PM PM PM PM PM PM PM PM PM

[uid:4][0413FC58]: Updated key list: [uid:4][0413FC58]: Access-Type = 15 (IP) [uid:4][0413FC58]: Protocol-Type = 4 (IP) [uid:4][0413FC58]: Media-Type = 2 (IP) [uid:4][0413FC58]: IP-Address = 10.0.0.2 (0A000002) [uid:4][0413FC58]: IP-Address-VRF = IP 10.0.0.2:0 [uid:4][0413FC58]: source-ip-address = 037FBB78 [uid:4][0413FC58]: Mac-Address = aabb.cc00.6500 [uid:4][0413FC58]: Final = 1 (YES) [uid:4][0413FC58]: Authen-Status = 1 (Unauthenticated) [uid:4][0413FC58]: Nasport = PPPoEoE: slot 0 adapter 0 port

18:58:24.519: SSS PM [uid:4][0413FC58]: Session-Handle = 486539268 (1D000004) 18:58:24.519: SSS PM [uid:4][0413FC58]: SM Policy invoke - Service Selection 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.519: 18:58:24.523: 18:58:24.523:

SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS

PM PM PM PM PM PM PM PM PM PM PM

[uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]: [uid:4][0413FC58]:

Access type IP Access type IP: final key Received Service Request Handling Authorization Check SIP [IP] can NOT provide more keys SIP [IP] can NOT provide more keys Handling Default Service Providing Service Policy reply - Local Terminate SM Policy invoke - Apply Config Success Handling Apply Config; SUCCESS


DB-2122

May 2008

Debug Commands debug subscriber service

debug subscriber service To display diagnostic information about the service profile database in an Intelligent Service Gateway (ISG), use the debug subscriber service command in privileged EXEC mode. To disable debugging, use the no form of this command. debug subscriber service no debug subscriber service

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX


Usage Guidelines

Use the debug subscriber service command to diagnose problems with service profiles or service policy maps.

Examples

The following example shows sample output for the debug subscriber service command. This output indicates that a service logon has occurred for the service “prep_service”. *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb 1->0 *Feb

7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7

18:52:31.067: 18:52:31.067: 18:52:31.067: 18:52:31.067: 18:52:31.067: 18:52:31.127: 18:52:31.127: 18:52:31.127: 18:52:31.127: 18:52:31.127: 18:52:31.127: 18:52:31.127: 18:52:31.127: 18:52:31.127: 18:52:31.131: 18:52:31.131: 18:52:31.131: 18:52:31.131: 18:52:31.131: 18:52:31.131: 18:52:31.131:

SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM SVM

[prep_service]: needs downloading [D6000000/prep_service]: allocated version 1 [D6000000/prep_service]: [8A000002]: client queued [D6000000/prep_service]: [PM-Download:8A000002] locked 0->1 [D6000000/prep_service]: [AAA-Download:040DD9D0] locked 0->1 [D6000000/prep_service]: TC feature info found [D0000001/prep_service]: added child [D6000000/prep_service]: [TC-Child:040DD130] locked 0->1 [D0000001/CHILD/prep_service]: [TC-Parent:040DD1A8] locked 0->1 [D6000000/prep_service]: TC flow feature info not found [D6000000/prep_service]: downloaded first version [D6000000/prep_service]: [8A000002]: client download ok [D6000000/prep_service]: [SVM-to-client-msg:8A000002] locked 0->1 [D6000000/prep_service]: [AAA-Download:040DD9D0] unlocked 1->0 [D6000000/prep_service]: alloc feature info [D6000000/prep_service]: [SVM-Feature-Info:040E2E80] locked 0->1 [D6000000/prep_service]: has Policy info [D6000000/prep_service]: [PM-Info:0416BAB0] locked 0->1 [D6000000/prep_service]: populated client [D6000000/prep_service]: [PM-Download:8A000002] unlocked 1->0 [D6000000/prep_service]: [SVM-to-client-msg:8A000002] unlocked

7 18:52:31.131: SVM [D6000000/prep_service]: [PM-Service:040E31E0] locked 0->1


DB-2123

Debug Commands debug subscriber service

*Feb 7 18:52:31.131: 0->1 *Feb 7 18:52:31.131: *Feb 7 18:52:31.131: 1->0 *Feb 7 18:52:31.139: *Feb 7 18:52:31.139: 0->1 *Feb 7 18:52:31.159: *Feb 7 18:52:31.159: unlocked 1->0 *Feb 7 18:52:31.159: 1->0

SVM [D0000001/CHILD/prep_service]: [SM-SIP-Apply:D0000001] locked SVM [D6000000/prep_service]: [FM-Bind:82000002] locked 0->1 SVM [D6000000/prep_service]: [SVM-Feature-Info:040E2E80] unlocked SVM [D0000001/CHILD/prep_service]: alloc feature info SVM [D0000001/CHILD/prep_service]: [SVM-Feature-Info:040E2E80] locked SVM [D0000001/CHILD/prep_service]: [FM-Bind:2C000003] locked 0->1 SVM [D0000001/CHILD/prep_service]: [SVM-Feature-Info:040E2E80] SVM [D0000001/CHILD/prep_service]: [SM-SIP-Apply:D0000001] unlocked


DB-2124

May 2008

Debug Commands debug subscriber testing

debug subscriber testing To display diagnostic information for Intelligent Service Gateway (ISG) simulator testing, use the debug subscriber testing command in privileged EXEC mode. To disable debugging, use the no form of this command. debug subscriber testing no debug subscriber testing

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(28)SB


12.2SX


Examples

The following example shows the configuration of the debug subscriber testing command: Router# debug subscriber testing


DB-2125

Debug Commands debug sw56

debug sw56 To display debugging information for switched 56K services, use the debug sw56 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug sw56 no debug sw56

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3T


12.2(33)SRA


12.2SX



DB-2126

May 2008

Debug Commands debug syscon perfdata

debug syscon perfdata To display messages related to performance data collection, use the debug syscon perfdata command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug syscon perfdata no debug syscon perfdata

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command is primarily useful to your technical support representative.

Examples

The following is sample output from the debug syscon perfdata command. In this example, the CallFail poll group is configured and applied to shelf 1111. The system determines when the next polling cycle should occur and polls the shelf at the appropriate time. The data is stored in the file CallFail.891645120, and an older file is deleted. Router# debug syscon perfdata PERF: PERF: PERF: PERF: PERF: PERF: PERF: PERF: PERF:

Applying 'CallFail' to shelf 1111 Setting up objects for SNMP polling: 'CallFail', shelf 1111 year hours mins secs msecs = 1998 15 11 1 5 Start 'CallFail' timer, next cycle in 0 mins, 59 secs Timer event: CallFail, 4 minutes Polling 'CallFail', shelf 1111, pc 60AEFDF0 SNMP resp: Type 6, 'CallFail', shelf 1111, error_st 0 Logged polled data to disk0:/performance/shelf-1111/CallFail.891645120 Deleted disk0:/performance/shelf-1111/CallFail.891637469


DB-2127

Debug Commands debug syscon sdp

debug syscon sdp To display messages related to the Shelf Discovery Protocol (SDP), use the debug syscon sdp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug syscon sdp no debug syscon sdp

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use this command to display information about SDP packets exchanged between the shelf and the system controller.

Examples

The following sample output from the debug syscon sdp command shows the system controller discovering a managed shelf. In the first few lines, the system controller receives a hello packet from shelf 99 at 172.23.66.106. The system controller responds with a hello packet. When the shelf sends another hello packet, the system controller resets the timer and sends another packet. Syscon# debug syscon sdp SYSCTLR: Hello packet received via UDP from 172.23.66.106 %SYSCTLR-6-SHELF_ADD: Shelf 99 discovered located at address 172.23.66.106 Hello packet sent to the RS located at 172.23.66.106 SYSCTLR: Hello packet received via UDP from 172.23.66.106 Timer for shelf 99 updated, shelf is alive Hello packet sent to the RS located at 172.23.66.106

The following sample output from the debug syscon sdp command shows the shelf contacting the system controller. The shelf sends a hello packet to the system controller at 172.23.66.111. The system controller responds with the autoconfiguration commands. The remaining lines show the Hello packets were exchanged between the shelf and the system controller. Shelf# debug syscon sdp SYSCTLR: Hello packet sent to the SYSCTLR at 172.23.66.111 SYSCTLR: Command packet received from SYSCTLR Feb 24 17:24:16.713: %SHELF-6-SYSCTLR_ESTABLISHED: Configured via system controller located at 172.23.66.111 SYSCTLR: Rcvd HELLO from SYSCTLR at 172.23.66.111 SYSCTLR: Hello packet sent to the SYSCTLR at 172.23.66.111 SYSCTLR: Rcvd HELLO from SYSCTLR at 172.23.66.111


DB-2128

May 2008

Debug Commands debug syslog-server

debug syslog-server To display information about the syslog server process, use the debug syslog-server command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug syslog-server no debug syslog-server

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command outputs a message every time the syslog server receives a message. It also displays information about subfile creation, removal, and renaming. Use this command when subfiles are not being created as configured or data is not being written to subfiles. This command is also useful for detecting syslog file size mismatches.

Examples

The following is sample output from the debug syslog-server command. The sample output shows when the following command has been added to the configuration: logging syslog-server 10 3 syslogs

This example shows the files being created. Use the dir disk0:/syslogs.dir command to display the contents of the newly created directory. Router# debug syslog-server SYSLOG_SERVER:Syslog file syslogs SYSLOG_SERVER:Directory disk0:/syslogs.dir created. SYSLOG_SERVER:Syslog file syslogs created successfully.

When a syslog message is received, the router checks to determine if the current file will be too large when the new data is added. In this example, two messages are added to the file. SYSLOG_SERVER: Configured size : 10240 bytes Current size : 0 bytes Data size : 68 bytes New size : 68 bytes SYSLOG_SERVER: Wrote 68 bytes successfully. SYSLOG_SERVER: Configured size : 10240 bytes Current size : 68 bytes Data size : 61 bytes New size : 129 bytes SYSLOG_SERVER: Wrote 61 bytes successfully.



DB-2129

Debug Commands debug syslog-server

Table 328

debug syslog-server Field Descriptions

Field

Description

Configured size

Maximum subfile size, as set in the logging syslog-server command.

Current size

Size of the current subfile before the new message is added.

Data size

Size of the syslog message.

New size

Size of the current subfile after the syslog message is added.

The following output indicates that the current file is too full to fit the next syslog message. The oldest subfile is removed, and the remaining files are renamed. A new file is created and opened for writing syslog messages. SYSLOG_SERVER:Last archive subfile disk0:/syslogs.dir/syslogs.2 removed. SYSLOG_SERVER: Subfile disk0:/syslogs.dir/syslogs.1 renamed as disk0:/syslogs.dir/syslogs.2. SYSLOG_SERVER:subfile disk0:/syslogs.dir/syslogs.cur renamed as disk0:/syslogs.dir/syslogs.1. SYSLOG_SERVER:Current subfile disk0:/syslogs.dir/syslogs.cur has been opened.


DB-2130

May 2008

Debug Commands debug tacacs events

debug tacacs events To display information from the TACACS+ helper process, use the debug tacacs events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug tacacs events no debug tacacs events

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

Use the debug tacacs events command only in response to a request from service personnel to collect data when a problem has been reported.

Caution

Use the debug tacacs events command with caution because it can generate a substantial amount of output. The TACACS protocol is used on routers to assist in managing user accounts. TACACS+ enhances the TACACS functionality by adding security features and cleanly separating out the authentication, authorization, and accounting (AAA) functionality.

Examples

The following is sample output from the debug tacacs events command. In this example, the opening and closing of a TCP connection to a TACACS+ server are shown, and the bytes read and written over the connection and the TCP status of the connection: Router# debug tacacs events %LINK-3-UPDOWN: Interface Async2, changed state to up 00:03:16: TAC+: Opening TCP/IP to 192.168.58.104/1049 timeout=15 00:03:16: TAC+: Opened TCP/IP handle 0x48A87C to 192.168.58.104/1049 00:03:16: TAC+: periodic timer started 00:03:16: TAC+: 192.168.58.104 req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (ESTAB) expire=14 AUTHEN/START/SENDAUTH/CHAP queued 00:03:17: TAC+: 192.168.58.104 ESTAB 3BD868 wrote 46 of 46 bytes 00:03:22: TAC+: 192.168.58.104 CLOSEWAIT read=12 wanted=12 alloc=12 got=12 00:03:22: TAC+: 192.168.58.104 CLOSEWAIT read=61 wanted=61 alloc=61 got=49 00:03:22: TAC+: 192.168.58.104 received 61 byte reply for 3BD868 00:03:22: TAC+: req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (CLOSEWAIT) expire=9 AUTHEN/START/SENDAUTH/CHAP processed 00:03:22: TAC+: periodic timer stopped (queue empty) 00:03:22: TAC+: Closing TCP/IP 0x48A87C connection to 192.168.58.104/1049 00:03:22: TAC+: Opening TCP/IP to 192.168.58.104/1049 timeout=15 00:03:22: TAC+: Opened TCP/IP handle 0x489F08 to 192.168.58.104/1049 00:03:22: TAC+: periodic timer started 00:03:22: TAC+: 192.168.58.104 req=3BD868 id=299214410 ver=192 handle=0x489F08 (ESTAB) expire=14 AUTHEN/START/SENDPASS/CHAP queued


DB-2131


00:03:23: TAC+: 192.168.58.104 ESTAB 3BD868 wrote 41 of 41 bytes 00:03:23: TAC+: 192.168.58.104 CLOSEWAIT read=12 wanted=12 alloc=12 got=12 00:03:23: TAC+: 192.168.58.104 CLOSEWAIT read=21 wanted=21 alloc=21 got=9 00:03:23: TAC+: 192.168.58.104 received 21 byte reply for 3BD868 00:03:23: TAC+: req=3BD868 id=299214410 ver=192 handle=0x489F08 (CLOSEWAIT) expire=13 AUTHEN/START/SENDPASS/CHAP processed 00:03:23: TAC+: periodic timer stopped (queue empty)

The TACACS messages are intended to be self-explanatory or for consumption by service personnel only. However, the messages shown are briefly explained in the following text. The following message indicates that a TCP open request to host 192.168.58.104 on port 1049 will time out in 15 seconds if it gets no response: 00:03:16: TAC+: Opening TCP/IP to 192.168.58.104/1049 timeout=15

The following message indicates a successful open operation and provides the address of the internal TCP “handle” for this connection: 00:03:16: TAC+: Opened TCP/IP handle 0x48A87C to 192.168.58.104/1049

The following message indicates that a TACACS+ request has been queued: 00:03:16: TAC+: 192.168.58.104 req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (ESTAB) expire=14 AUTHEN/START/SENDAUTH/CHAP queued

The message identifies the following: •

Server that the request is destined for

•

Internal address of the request

•

TACACS+ ID of the request

•

TACACS+ version number of the request

•

Internal TCP handle the request uses (which will be zero for a single-connection server)

•

TCP status of the connection—which is one of the following: – CLOSED – LISTEN – SYNSENT – SYNRCVD – ESTAB – FINWAIT1 – FINWAIT2 – CLOSEWAIT – LASTACK – CLOSING – TIMEWAIT

•

Number of seconds until the request times out

•

Request type

The following message indicates that all 46 bytes were written to address 192.168.58.104 for request 3BD868: 00:03:17: TAC+: 192.168.58.104 ESTAB 3BD868 wrote 46 of 46 bytes


DB-2132

May 2008


The following message indicates that 12 bytes were read in reply to the request: 00:03:22: TAC+: 192.168.58.104 CLOSEWAIT read=12 wanted=12 alloc=12 got=12

The following message indicates that 49 more bytes were read, making a total of 61 bytes in all, which is all that was expected: 00:03:22: TAC+: 192.168.58.104 CLOSEWAIT read=61 wanted=61 alloc=61 got=49

The following message indicates that a complete 61-byte reply has been read and processed for request 3BD868: 00:03:22: TAC+: 192.168.58.104 received 61 byte reply for 3BD868 00:03:22: TAC+: req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (CLOSEWAIT) expire=9 AUTHEN/START/SENDAUTH/CHAP processed

The following message indicates that the TACACS+ server helper process switched itself off when it had no more work to do: 00:03:22: TAC+: periodic timer stopped (queue empty)

Related Commands

Command

Description






Displays information on AAA/TACACS+ authorization.

debug sw56

Displays debugging information for switched 56K services.


DB-2133

Debug Commands debug tacacs

debug tacacs To display information associated with TACACS, use the debug tacacs command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug tacacs no debug tacacs

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

TACACS is a distributed security system that secures networks against unauthorized access. Cisco supports TACACS under the authentication, authorization, and accounting (AAA) security system. Use the debug aaa authentication command to get a high-level view of login activity. When TACACS is used on the router, you can use the debug tacacs command for more detailed debugging information.

Examples

The following is sample output from the debug aaa authentication command for a TACACS login attempt that was successful. The information indicates that TACACS+ is the authentication method used. Router# debug aaa authentication 14:01:17: 14:01:17: 14:01:17: 14:01:17:

AAA/AUTHEN (567936829): Method=TACACS+ TAC+: send AUTHEN/CONT packet TAC+ (567936829): received authen response status = PASS AAA/AUTHEN (567936829): status = PASS

The following is sample output from the debug tacacs command for a TACACS login attempt that was successful, as indicated by the status PASS: Router# debug tacacs 14:00:09: 14:00:09: 14:00:09: 14:00:09: 14:00:10: 14:00:10: 14:00:10: 14:00:10: 14:00:14: 14:00:14: 14:00:14: 14:00:14: 14:00:14:

TAC+: Opening TCP/IP connection to 192.168.60.15 using source 10.116.0.79 TAC+: Sending TCP/IP packet number 383258052-1 to 192.168.60.15 (AUTHEN/START) TAC+: Receiving TCP/IP packet number 383258052-2 from 192.168.60.15 TAC+ (383258052): received authen response status = GETUSER TAC+: send AUTHEN/CONT packet TAC+: Sending TCP/IP packet number 383258052-3 to 192.168.60.15 (AUTHEN/CONT) TAC+: Receiving TCP/IP packet number 383258052-4 from 192.168.60.15 TAC+ (383258052): received authen response status = GETPASS TAC+: send AUTHEN/CONT packet TAC+: Sending TCP/IP packet number 383258052-5 to 192.168.60.15 (AUTHEN/CONT) TAC+: Receiving TCP/IP packet number 383258052-6 from 192.168.60.15 TAC+ (383258052): received authen response status = PASS TAC+: Closing TCP/IP connection to 192.168.60.15


DB-2134

May 2008

Debug Commands debug tacacs

The following is sample output from the debug tacacs command for a TACACS login attempt that was unsuccessful, as indicated by the status FAIL: Router# debug tacacs 13:53:35: TAC+: Opening TCP/IP connection to 192.168.60.15 using source 192.48.0.79 13:53:35: TAC+: Sending TCP/IP packet number 416942312-1 to 192.168.60.15 (AUTHEN/START) 13:53:35: TAC+: Receiving TCP/IP packet number 416942312-2 from 192.168.60.15 13:53:35: TAC+ (416942312): received authen response status = GETUSER 13:53:37: TAC+: send AUTHEN/CONT packet 13:53:37: TAC+: Sending TCP/IP packet number 416942312-3 to 192.168.60.15 (AUTHEN/CONT) 13:53:37: TAC+: Receiving TCP/IP packet number 416942312-4 from 192.168.60.15 13:53:37: TAC+ (416942312): received authen response status = GETPASS 13:53:38: TAC+: send AUTHEN/CONT packet 13:53:38: TAC+: Sending TCP/IP packet number 416942312-5 to 192.168.60.15 (AUTHEN/CONT) 13:53:38: TAC+: Receiving TCP/IP packet number 416942312-6 from 192.168.60.15 13:53:38: TAC+ (416942312): received authen response status = FAIL 13:53:40: TAC+: Closing TCP/IP connection to 192.168.60.15

Related Commands

Command

Description






DB-2135

Debug Commands debug tag-switching atm-cos

debug tag-switching atm-cos The debug tag-switching atm-cos command is replaced by the debug mpls atm-cos command. See the debug mpls atm-cos command for more information.


DB-2136

May 2008

Debug Commands debug tag-switching atm-tdp api

debug tag-switching atm-tdp api The debug tag-switching atm-tdp api command is replaced by the debug mpls atm-ldp api command. See the debug mpls atm-ldp api command for more information.


DB-2137

Debug Commands debug tag-switching atm-tdp routes

debug tag-switching atm-tdp routes The debug tag-switching atm-tdp routes command is replaced by the debug mpls atm-ldp routes command. See the debug mpls atm-ldp routes command for more information.


DB-2138

May 2008

Debug Commands debug tag-switching atm-tdp states

debug tag-switching atm-tdp states The debug tag-switching atm-tdp states command is replaced by the debug mpls atm-ldp states command. See the debug mpls atm-ldp states command for more information.


DB-2139

Debug Commands debug tag-switching tdp advertisements

debug tag-switching tdp advertisements The debug tag-switching tdp advertisements command is replaced by the debug mpls ldp advertisements command. See the debug mpls ldp advertisements command for more information.


DB-2140

May 2008

Debug Commands debug tag-switching tdp bindings

debug tag-switching tdp bindings The debug tag-switching tdp bindings command is replaced by the debug mpls ldp bindings command. See the debug mpls ldp bindings command for more information.


DB-2141

Debug Commands debug tag-switching tdp directed-neighbors

debug tag-switching tdp directed-neighbors The debug tag-switching tdp directed-neighbors command is replaced by the debug mpls ldp targeted-neighbors command. See the debug mpls ldp targeted-neighbors command for more information.


DB-2142

May 2008

Debug Commands debug tag-switching tdp peer state-machine

debug tag-switching tdp peer state-machine The debug tag-switching tdp peer state-machine command is replaced by the debug mpls ldp peer state-machine command. See the debug mpls ldp peer state-machine command for more information.


DB-2143

Debug Commands debug tag-switching tdp pies received

debug tag-switching tdp pies received The debug tag-switching tdp pies received command is replaced by the debug mpls ldp session io command. See the debug mpls ldp session io command for more information.


DB-2144

May 2008

Debug Commands debug tag-switching tdp pies sent

debug tag-switching tdp pies sent The debug tag-switching tdp pies sent command is replaced by the debug mpls ldp messages command. See the debug mpls ldp messages command for more information.


DB-2145

Debug Commands debug tag-switching tdp session io

debug tag-switching tdp session io The debug tag-switching tdp session io command is replaced by the debug mpls ldp session io command. See the debug mpls ldp session io command for more information


DB-2146

May 2008

Debug Commands debug tag-switching tdp session state-machine

debug tag-switching tdp session state-machine The debug tag-switching tdp session state-machine command is replaced by the debug mpls ldp session state-machine command. See the debug mpls ldp session state-machine command for more information.


DB-2147

Debug Commands debug tag-switching tdp transport connections

debug tag-switching tdp transport connections The debug tag-switching tdp transport connections command is replaced by the debug mpls ldp tranport connections command. See the debug mpls ldp transport connections command for more information.


DB-2148

May 2008

Debug Commands debug tag-switching tdp transport events

debug tag-switching tdp transport events The debug tag-switching tdp transport events command is replaced by the debug mpls ldp tranport events command. See the debug mpls ldp transport events command for more information.


DB-2149

Debug Commands debug tag-switching tdp transport timers

debug tag-switching tdp transport timers To print information about events that restart the “hold” timers that are part of the TDP discovery mechanism, use the debug tag-switching tdp transport timers command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug tag-switching tdp transport timers no debug tag-switching tdp transport timers

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

TDP sessions are supported by data structures and state machines at three levels: •

Transport—The transport level establishes and maintains TCP connections used to support TDP sessions.

•

Protocol—The protocol level implements the TDP session setup protocol. The construction and parsing of TDP PDUs and PIEs occur at this level.

•

Tag distribution—The tag distribution level uses TDP sessions to exchange tags with TDP peer devices.

The debug tag-switching tdp transport command provides visibility of activity at the transport level, the debug tag-switching tdp session command at the protocol level, and the debug tag-switching tdp peer command at the tag distribution level.

Examples

The following is sample output from the debug tag-switching tdp transport timers command: Router# debug tag-switching tdp transport timers tdp: tdp: tdp: tdp: tdp: tdp:

Start Start Start Start Start Start

holding holding holding holding holding holding

timer; timer; timer; timer; timer; timer;

adj adj adj adj adj adj

0x60D5BC10, 0x60EA9360, 0x60D5BC10, 0x60EA9360, 0x60D5BC10, 0x60EA9360,

200.26.0.4 10.105.0.9 200.26.0.4 10.105.0.9 200.26.0.4 10.105.0.9


debug tag-switching tdp transport timers Field Descriptions

Field

Description

tdp

Identifies the source of the message as TDP.

adj 0xnnnnnnnn

Identifies the data structure used to represent the peer device at the transport level.

a.b.c.d

Network address of the peer device.


DB-2150

May 2008

Debug Commands debug tag-switching tdp transport timers

Related Commands

Command

Description

debug tag-switching tdp transport events

Prints information about the events related to the TDP peer discovery mechanism, which is used to determine the devices with which to establish TDP sessions.


DB-2151

Debug Commands debug tag-switching xtagatm cross-connect

debug tag-switching xtagatm cross-connect The debug tag-switching xtagatm cross-connect command is replaced by the debug mpls xtagatm cross-connect command. See the debug mpls xtagatm cross-connect command for more information.


DB-2152

May 2008

Debug Commands debug tag-switching xtagatm errors

debug tag-switching xtagatm errors The debug tag-switching xtagatm errors command is replaced by the debug mpls xtagatm errors command. See the debug mpls xtagatm errors command for more information.


DB-2153

Debug Commands debug tag-switching xtagatm events

debug tag-switching xtagatm events The debug tag-switching xtagatm events command is replaced by the debug mpls xtagatm events command. See the debug mpls xtagatm events command for more information.


DB-2154

May 2008

Debug Commands debug tag-switching xtagatm vc

debug tag-switching xtagatm vc The debug tag-switching xtagatm vc command is replaced by the debug mpls xtagatm vc command. See the debug mpls xtagatm vc command for more information.


DB-2155

Debug Commands debug tag-template event

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

Syntax Description


Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(6)T


12.2SX


Examples

The following example shows that the tag application on a session is to be displayed: Router# debug tag-template event

Related Commands

Command

Description

show epm sessions ip

Displays whether tag policies have been applied.


DB-2156

May 2008

Debug Commands debug tarp events

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

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

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

Examples

The following is sample output from the debug tarp events and debug tarp packets commands after the tarp resolve command was used to determine the network service access point (NSAP) address for the TARP target identifier (TID) named artemis. Router# debug tarp events Router# debug tarp packets Router# tarp resolve artemis Type escape sequence to abort. Sending TARP type 1 PDU, timeout 15 seconds... NET corresponding to TID artemis is 49.0001.1111.1111.1111.00 *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

1 1 1 1 1 1 1 1

*Mar

1


1 1 1 1 1 1 1

00:43:59: TARP-PA: Propagated TARP packet, type 1, out on Ethernet0 00:43:59: Lft = 100, Seq = 11, Prot type = 0xFE, URC = TRUE 00:43:59: Ttid len = 7, Stid len = 8, Prot addr len = 10 00:43:59: Destination NSAP: 49.0001.1111.1111.1111.00 00:43:59: Originator's NSAP: 49.0001.3333.3333.3333.00 00:43:59: Target TID: artemis 00:43:59: Originator's TID: cerd 00:43:59: TARP-EV: Packet not propagated to 49.0001.4444.4444.4444.00 on interface Ethernet0 (adjacency is not in UP state) 00:43:59: TARP-EV: No route found for TARP static adjacency 55.0001.0001.1111.1111.1111.1111.1111.1111.1111.00 - packet not sent 00:43:59: TARP-PA: Received TARP type 3 PDU on interface Ethernet0 00:43:59: Lft = 100, Seq = 5, Prot type = 0xFE, URC = TRUE 00:43:59: Ttid len = 0, Stid len = 7, Prot addr len = 10 00:43:59: Packet sent/propagated by 49.0001.1111.1111.1111.af 00:43:59: Originator's NSAP: 49.0001.1111.1111.1111.00 00:43:59: Originator's TID: artemis 00:43:59: TARP-PA: Created new DYNAMIC cache entry for artemis

Table 330 describes the significant fields shown in display.


DB-2157

Debug Commands debug tarp events

Table 330

Related Commands

debug tarp events Field Descriptions—tarp resolve Command

Field

Descriptions

Sending TARP type 1 PDU

Protocol data unit (PDU) requesting the NSAP of the specified TID.

timeout

Number of seconds the router will wait for a response from the Type 1 PDU. The timeout is set by the tarp t1-response-timer command.

NET corresponding to

NSAP address (in this case, 49.0001.1111.1111.1111.00) for the specified TID.

*Mar 1 00:43:59

Debug time stamp.

TARP-PA: Propagated

TARP packet: A Type 1 PDU was sent out on Ethernet interface 0.

Lft

Lifetime of the PDU (in hops).

Seq

Sequence number of the PDU.

Prot type

Protocol type of the PDU.

URC

Update remote cache bit.

Ttid len

Destination TID length.

Stid len

Source TID length.

Prot addr len

Protocol address length (bytes).

Destination NSAP

NSAP address that the PDU is being sent to.

Originator’s NSAP

NSAP address that the PDU was sent from.

Target TID

TID that the PDU is being sent to.

Originator’s TID

TID that the PDU was sent from.

TARP-EV: Packet not propagated

TARP event: The Type 1 PDU was not propagated on Ethernet interface 0 because the adjacency is not up.

TARP-EV: No route found

TARP event: The Type 1 PDU was not sent because no route was available.

TARP-PA: Received TARP

TARP packet: A Type 3 PDU was received on Ethernet interface 0.

Packet sent/propagated by

NSAP address of the router that sent or propagated the PDU.

TARP-PA: Created new DYNAMIC cache entry

TARP packet: A dynamic entry was made to the local TID cache.

Command

Description

debug tarp packets

Displays general information on TARP packets received, generated, and propagated on the router.


DB-2158

May 2008

Debug Commands debug tarp packets

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

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

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

Examples

The following is sample output from the debug tarp packet command after the tarp query command was used to determine the TARP target identifier (TID) for the NSAP address 49.0001.3333.3333.3333.00: Router# debug tarp packets Router# debug tarp events Router# tarp query 49.0001.3333.3333.3333.00 Type escape sequence to abort. Sending TARP type 5 PDU, timeout 40 seconds... TID corresponding to NET 49.0001.3333.3333.3333.00 is cerdiwen *Mar 2 03:10:11: TARP-PA: Originated TARP packet, type 5, to destination 49.0001.3333.3333.3333.00 *Mar 2 03:10:11: TARP-PA: Received TARP type 3 PDU on interface Ethernet0 *Mar 2 03:10:11: Lft = 100, Seq = 2, Prot type = 0xFE, URC = TRUE *Mar 2 03:10:11: Ttid len = 0, Stid len = 8, Prot addr len = 10 *Mar 2 03:10:11: Packet sent/propagated by 49.0001.3333.3333.3333.af *Mar 2 03:10:11: Originator's NSAP: 49.0001.3333.3333.3333.00 *Mar 2 03:10:11: Originator's TID: cerdiwen *Mar 2 03:10:11: TARP-PA: Created new DYNAMIC cache entry for cerdiwen


debug tarp packets Field Descriptions—tarp query Command

Field

Descriptions

Sending TARP type 5 PDU

Protocol data unit (PDU) requesting the TID of the specified NSAP.

timeout

Number of seconds the router will wait for a response from the Type 5 PDU. The timeout is set by the tarp arp-request-timer command.


DB-2159

Debug Commands debug tarp packets

Table 331

Related Commands

debug tarp packets Field Descriptions—tarp query Command (continued)

Field

Descriptions

TID corresponding to NET

TID (in this case cerdiwen) for the specified NSAP address.

*Mar 2 03:10:11

Debug time stamp.

TARP-PA: Originated TARP packet

TARP packet: A Type 5 PDU was sent.

TARP P-A: Received TARP

TARP packet: A Type 3 PDU was received.

Lft

Lifetime of the PDU (in hops).

Seq

Sequence number of the PDU.

Prot type

Protocol type of the PDU.

URC

The update remote cache bit.

Ttid len

Destination TID length.

Stid len

Source TID length.

Prot addr len

Protocol address length (in bytes).

Packet sent/propagated

NSAP address of the router that sent or propagated the PDU.

Originator’s NSAP

NSAP address that the PDU was sent from.

Originator’s TID

TID that the PDU was sent from.

TARP-PA: Created new DYNAMIC cache entry

TARP packet: A dynamic entry was made to the local TID cache.

Command

Modification

debug tarp events

Displays information on TARP activity.


DB-2160

May 2008

Debug Commands debug tbridge virtual-port

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(2)T


12.2SX


Examples

The following is sample output from the debug tbridge virtual-port command: Router# debug tbridge virtual-port Transparent Bridging Virtual Port Events debugging is on Router# vBridge-Port: Received packet (vLAN 100) on FastEthernet0/0 matches with lw-vLAN range. Set packet input interface to vBridgePort2/1.


debug tbridge virtual-port Field Descriptions

Field

Description

vBridge-Port

Identifies the message as a Transparent Bridging Virtual Port debug message.

vLAN 100

The VLAN ID of the packet.

vBridgePort2/1

The interface the packet is to be bridged to.


DB-2161

Debug Commands debug tcam_mgr

debug tcam_mgr To debug the ternary content addressable memory (TCAM) manager, use the debug tcam_mgr command in privileged EXEC configuration mode. debug tcam_mgr {error | event | profile} no debug tcam_mgr {error | event | profile}

Syntax Description

error

Enables debug messages related to TCAM manager errors.

event

Enables debug messages for TCAM manager events.

profile

Enables debug messages about the amount of time it takes to add and remove entries from the TCAM regions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0 S


12.2(20)S2

This command was integrated into Cisco IOS Release 12.2(20)S2.

12.2SX


Usage Guidelines

Caution

Examples

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

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

The following example enables TCAM manager event debug messages. It shows the messages associated with shutting down and restarting an interface on the the 4-Port 10/100 Fast Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 4 of the Cisco 7304 router: Router# debug tcam_mgr event TCAM Manager Events debugging is on Router# conf t Enter configuration commands, one per line.

End with CNTL/Z.


DB-2162

May 2008

Debug Commands debug tcam_mgr

Router(config)# int fast 4/0/0 Router(config-if)# shut Router(config-if)# 4d01h: %LINK-5-CHANGED: Interface FastEthernet4/0/0, changed state to administratively down 4d01h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/0/0, changed state to down Router(config-if)# Router(config-if)# no shut Router(config-if)# 4d01h: Freeing VC at 0 from mask at 0 4d01h: Freeing VC at 1 from mask at 0 4d01h: Freeing VC at 0 from mask at 8 4d01h: Found Mbu at offset 0 index 0 4d01h: Allocated mbu at offset 0 index 0, vc_index 0 region 0 4d01h: Found Mbu at offset 0 index 0 4d01h: Allocated mbu at offset 0 index 0, vc_index 1 region 0 4d01h: Found Mbu at offset 0 index 1 4d01h: Allocated mbu at offset 0 index 1, vc_index 0 region 0 4d01h: %LINK-3-UPDOWN: Interface FastEthernet4/0/0, changed state to up 4d01h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet4/0/0, changed state to up


DB-2163

Debug Commands debug tccs signaling

debug tccs signaling To see information about the transparent Common Channel Signaling (CCS) connection, use the debug tccs signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug tccs signaling no debug tccs signaling

Syntax Description


Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK


12.1(2)T

This command was integrated into Release 12.1(2)T and Release 12.1(2)T.

12.2SX


Usage Guidelines

Caution

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

Examples

•

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

•

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

The following shows sample output from the command on both the originating and terminating sides: Router# debug tccs signaling TCCS Domain packet debugging is on mazurka-4# 01:37:12: 1 tccs packets received from the port. 01:37:12: 1 tccs packets received from the nework. 01:37:12: tx_tccs_fr_pkt:pkt rcvd from network->tx_start


DB-2164

May 2008

Debug Commands debug tccs signaling

01:37:12: tx_tccs_fr_pkt: dlci=37, cid=100, payld-type =0, payld-length=162, cid_type=424 01:37:12: datagramsize=26 01:37:12: [0] A4 40 C0 0 01:37:12: [4] 86 86 86 86 01:37:12: [8] 86 86 86 86 01:37:12: [12] 86 86 86 86 01:37:12: [16] 86 86 86 86 01:37:12: [20] 86 86 86 86 01:37:12: [24] 86 86 11 48 01:37:12: 2 tccs packets received from the port. 01:37:12: 1 tccs packets received from the nework. 01:37:12: pri_tccs_rx_intr:from port->send_sub_channel 01:37:12: tccs_db->vcd = 37, tccs_db->cid = 100 01:37:12: pak->datagramsize=25 01:37:12: [0] A4 40 C0 0 01:37:12: [4] 42 43 43 43 01:37:12: [8] 43 43 43 43 01:37:12: [12] 43 43 43 43 01:37:12: [16] 43 43 43 43 01:37:12: [20] 43 43 43 43 01:37:12: [24] 43 43 43 0 Router# debug tccs signaling 00:53:26: 00:53:26: 00:53:26: 00:53:26: 00:53:26: 00:53:26: 00:53:26: 00:53:27: 00:53:27: 00:53:27: 00:53:27: 00:53:27: 00:53:27: 00:53:27: 00:53:28: 00:53:28: 00:53:28: 00:53:28: 00:53:28: 00:53:28: 00:53:28: 00:53:29: 00:53:29:

61 tccs packets received from the port. 53 tccs packets received from the nework. pri_tccs_rx_intr:from port->send_sub_channel tccs_db->vcd = 37, tccs_db->cid = 100 pak->datagramsize=7 [0] A4 40 C0 0 [4] 0 1 7F 64 62 tccs packets received from the port. 53 tccs packets received from the nework. pri_tccs_rx_intr:from port->send_sub_channel tccs_db->vcd = 37, tccs_db->cid = 100 pak->datagramsize=7 [0] A4 40 C0 0 [4] 0 1 7F 64 63 tccs packets received from the port. 53 tccs packets received from the nework. pri_tccs_rx_intr:from port->send_sub_channel tccs_db->vcd = 37, tccs_db->cid = 100 pak->datagramsize=7 [0] A4 40 C0 0 [4] 0 1 7F 64 64 tccs packets received from the port. 53 tccs packets received from the nework.


DB-2165

Debug Commands debug tdm

debug tdm To display time-division multiplexing (TDM) bus connection information each time a connection is made on Cisco AS5300 access servers, use the debug tdm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug tdm [api | detail | dynamic | pri | test | tsi | vdev] no debug tdm [api | detail | dynamic | pri | test | tsi | vdev]

Syntax Description

api

(Optional) Displays a debugging message whenever the TDM subsystem application programming interface (API) is invoked from another subsystem.

detail

(Optional) Displays detailed messages (i.e., trace messages) whenever the TDM software executes.

dynamic

(Optional) Displays TDM debugging information whenever a backplane timeslot is allocated or deallocated.

pri

(Optional) Routes modem back-to-back connections from the modem-to-PRI board to modem board. By default, the modem back-to-back connections route from modem board to motherboard to modem board.

test

(Optional) Simulates the failure of allocating a TDM timeslot. Verifies that the software and TDM hardware recover from the failure.

tsi

(Optional) Displays debugging information about the TSI Chip MT8980/MT90820 driver.

vdev

(Optional) TDM per voice device debug slot and port number (that is, 0/1). Displays debugging information whenever a modem board TDM connection is made.

Command Modes

Privileged EXEC

Usage Guidelines

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

Examples

The following examples show the turning on of the debug option, performing a modem call, and turning off the debug option: Router# debug tdm api TDM API debugging is on Router# 23:16:04: TDM(vdev reg: 0x3C500100/PRI reg: 0x3C400100): two way connection requested. 23:16:04: TDM(reg: 0x3C500100): Close connection to STo8, channel 1 23:16:04: TDM(reg: 0x3C500100): Connect STi4, channel 1 to STo8, channel 1 23:16:04: TDM(reg: 0x3C500100): Close connection to STo4, channel 1 23:16:04: TDM(reg: 0x3C500100): Connect STi8, channel 1 to STo4, channel 1 23:16:04: TDM(reg: 0x3C400100): Close connection to STo12, channel 31 23:16:04: TDM(reg: 0x3C400100): Close connection to STo8, channel 31


DB-2166

May 2008


23:16:04: 23:16:04: 23:18:22: 23:18:22: 23:18:22: 23:18:22: 23:18:22: 23:18:22: 23:18:22: 23:18:22: 23:18:22: 23:18:22: 23:18:22: 23:18:22:

TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg: TDM(reg:

0x3C400100): 0x3C400100): 0x3C500100): 0x3C500100): 0x3C500100): 0x3C500100): 0x3C500100): 0x3C500100): 0x3C400100): 0x3C400100): 0x3C400100): 0x3C400100): 0x3C400100): 0x3C400100):

Connect STi12, channel 31 to STo4, channel 1 Connect STi4, channel 1 to STo12, channel 31 default RX connection requested. Close connection to STo8, channel 1 default TX connection requested. Close connection to STo4, channel 1 Close connection to STo8, channel 1 Close connection to STo4, channel 1 default RX connection requested. Close connection to STo4, channel 1 Connect STi12, channel 31 to STo8, channel 31 default TX connection requested. Close connection to STo12, channel 31 Connect STi8, channel 31 to STo12, channel 31

Router# no debug tdm api TDM API debugging is off Router# debug tdm detail TDM Detail Debug debugging is on router_2#show tdm pool

Dynamic Backplane Timeslot Pool Grp ST Ttl/Free Req(Cur/Ttl/Fail) Queues(Free/Used) Pool Ptr 0 0-3 128 128 0 0 0 0x60CB6B30 0x60CB6B30 0x60CB6B28 1 4-7 128 128 0 3 0 0x60CB6B40 0x60CB6B40 0x60CB6B2C Router# Router# no debug tdm detail TDM Detail Debug debugging is off Router# debug tdm dynamic TDM Dynamic BP Allocation debugging is on Router# 23:30:16: tdm_allocate_bp_ts(), slot# 1, chan# 3 23:30:16: TDM(reg: 0x3C500100): Open Modem RX ST8, CH3 to BP ST4 CH3 23:30:16: TDM(reg: 0x3C500100): Open Modem TX ST8, CH3 to BP ST4 CH3 23:30:16: TDM Backplane Timeslot Dump @ 0x60E6D244, tdm_free_bptsCount[1] = 127 vdev_slot : 0x01 bp_stream : 0x04 vdev_channel : 0x03 bp_channel : 0x03 freeQueue : 0x60CB6B40 23:30:16: TDM(PRI:0x3C400100):Close PRI framer st12 ch31 23:30:16: TDM(PRI:0x3C400100):Close HDLC controller st8 ch31 23:30:43: tdm_deallocate_bp_ts(), slot# 1, chan# 3 23:30:43: TDM(reg: 0x3C500100):Close Modem RX ST8, CH3 to BP ST4 CH3 23:30:43: TDM(reg: 0x3C500100):Close Modem TX ST8, CH3 to BP ST4 CH3 23:30:43: TDM Backplane Timeslot Dump @ 0x60E6D244, tdm_free_bptsCount[1] = 128 vdev_slot : 0x01 bp_stream : 0x04 vdev_channel : 0x03 bp_channel : 0x03 freeQueue : 0x60CB6B40 Router# Router# no debug tdm dynamic TDM Dynamic BP Allocation debugging is off Router# debug tdm pri TDM connectvia PRI feature board debugging is on Router# no debug tdm pri TDM connectvia PRI feature board debugging is off Router# debug tdm test TDM Unit Test debugging is on 23:52:01: Bad tdm_allocate_bp_ts() call, simulating error condition for vdev in slot 1 port 5


DB-2167


Router# no debug tdm test TDM Unit Test debugging is off Router# debug tdm tsi TDM TSI debugging is on Router# 23:56:40: MT90820(reg: 0x3C500100): 23:56:40: MT90820(reg: 0x3C500100): 23:56:40: MT90820(reg: 0x3C500100): 23:56:40: MT90820(reg: 0x3C500100): 23:56:40: MT90820(reg: 0x3C400100): 23:56:40: MT90820(reg: 0x3C400100): 23:56:40: MT90820(reg: 0x3C400100): 23:56:40: MT90820(reg: 0x3C400100): 23:57:03: MT90820(reg: 0x3C500100): 23:57:03: MT90820(reg: 0x3C500100): 23:57:03: MT90820(reg: 0x3C500100): 23:57:03: MT90820(reg: 0x3C500100): 23:57:03: MT90820(reg: 0x3C400100): 23:57:03: MT90820(reg: 0x3C400100): 23:57:03: MT90820(reg: 0x3C400100): 23:57:03: MT90820(reg: 0x3C400100): Router#

Close connection to STi8, channel 9 Connect STi4, channel 10 to STo8, channel 9 Close connection to STi4, channel 10 Connect STi8, channel 9 to STo4, channel 10 Close connection to STi12, channel 31 Close connection to STi8, channel 31 Connect STi12, channel 31 to STo4, channel 10 Connect STi4, channel 10 to STo12, channel 31 Close connection to STi8, channel 9 Close connection to STi4, channel 10 Close connection to STi8, channel 9 Close connection to STi4, channel 10 Close connection to STi4, channel 10 Connect STi12, channel 31 to STo8, channel 31 Close connection to STi12, channel 31 Connect STi8, channel 31 to STo12, channel 31

Router# no debug tdm tsi TDM TSI debugging is off Router# debug tdm vdev ? Slot/port number (i.e. 0/1) Router# debug tdm vdev 1/8 Enabling TDM debug for voice device in slot 0 port 1 Router# 23:55:00: TDM(vdev reg: 0x3C500100/PRI reg: 0x3C400100): two way connection requested. 23:55:00: tdm_allocate_bp_ts(), slot# 1, chan# 8 23:55:00: TDM(reg: 0x3C500100): Open Modem RX ST8, CH8 to BP ST4 CH9 23:55:00: TDM(reg: 0x3C500100): Open Modem TX ST8, CH8 to BP ST4 CH9 23:55:00: TDM Backplane Timeslot Dump @ 0x60E6D2D4, tdm_free_bptsCount[1] = 127 vdev_slot : 0x01 bp_stream : 0x04 vdev_channel : 0x08 bp_channel : 0x09 freeQueue : 0x60CB6B40 23:55:00: TDM(PRI:0x3C400100):Close PRI framer st12 ch31 23:55:00: TDM(PRI:0x3C400100):Close HDLC controller st8 ch31 23:55:31: TDM(reg: 0x3C500100): default RX connection requested. 23:55:31: TDM(reg: 0x3C500100): default TX connection requested. 23:55:31: tdm_deallocate_bp_ts(), slot# 1, chan# 8 23:55:31: TDM(reg: 0x3C500100):Close Modem RX ST8, CH8 to BP ST4 CH9 23:55:31: TDM(reg: 0x3C500100):Close Modem TX ST8, CH8 to BP ST4 CH9 23:55:31: TDM Backplane Timeslot Dump @ 0x60E6D2D4, tdm_free_bptsCount[1] = 128 vdev_slot : 0x01 bp_stream : 0x04 vdev_channel : 0x08 bp_channel : 0x09 freeQueue : 0x60CB6B40 Router# Router# no debug tdm vdev 1/8 Disabling TDM debug for voice device in slot 0 port 1 Router#


DB-2168

May 2008

Debug Commands debug telco-return msg

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

Syntax Description


Defaults

Debugging for telco-return messages is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XI


12.2SX


Examples

The following is sample output from the debug cable telco-return msg command: ubr7223# debug cable telco-return msg CMTS telco-return msg debugging is on


DB-2169

Debug Commands debug telnet

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

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

8.1


12.2(33)SRA


12.2SX


Examples

The following is sample output from the debug telnet command: Router# debug telnet *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct *Oct

28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28

21:31:12.035:Telnet1/00:1 1 251 1 21:31:12.035:TCP1/00:Telnet sent WILL ECHO (1) 21:31:12.035:Telnet1/00:2 2 251 3 21:31:12.035:TCP1/00:Telnet sent WILL SUPPRESS-GA (3) 21:31:12.035:Telnet1/00:4 4 251 0 21:31:12.035:TCP1/00:Telnet sent WILL BINARY (0) 21:31:12.035:Telnet1/00:40000 40000 253 0 21:31:12.035:TCP1/00:Telnet sent DO BINARY (0) 21:31:12.035:Telnet1/00:10000000 10000000 253 31 21:31:12.035:TCP1/00:Telnet sent DO WINDOW-SIZE (31) 21:31:12.035:TCP1/00:Telnet received WILL TTY-TYPE (24) 21:31:12.035:TCP1/00:Telnet sent DO TTY-TYPE (24) 21:31:12.035:Telnet1/00:Sent SB 24 1 21:31:12.035:TCP1/00:Telnet received WILL TTY-SPEED (32) (refused) 21:31:12.035:TCP1/00:Telnet sent DONT TTY-SPEED (32) 21:31:12.035:TCP1/00:Telnet received DO SUPPRESS-GA (3) 21:31:12.035:TCP1/00:Telnet received WILL SUPPRESS-GA (3) 21:31:12.035:TCP1/00:Telnet sent DO SUPPRESS-GA (3) 21:31:12.035:TCP1/00:Telnet received DO ECHO (1) 21:31:12.035:TCP1/00:Telnet received DO BINARY (0) 21:31:12.035:TCP1/00:Telnet received WILL BINARY (0) 21:31:12.059:TCP1/00:Telnet received WILL COMPORT (44) 21:31:12.059:TCP1/00:Telnet sent DO COMPORT (44) 21:31:12.059:TCP1/00:Telnet received DO COMPORT (44) 21:31:12.059:TCP1/00:Telnet sent WILL COMPORT (44) 21:31:12.059:TCP1/00:Telnet received WONT WINDOW-SIZE (31)


DB-2170

May 2008


*Oct 28 21:31:12.059:TCP1/00:Telnet sent DONT WINDOW-SIZE (31) *Oct 28 21:31:12.059:Telnet1/00:recv SB 24 0 *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 10 TTY1/00:Telnet COMPORT rcvd bad suboption:0xA/0x1E *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 1 *Oct 28 21:31:12.091:Telnet_CP-1/00 baudrate index 0 *Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 101 X.dctBXctBXctBX`W`P`> *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 2 *Oct 28 21:31:12.091:Telnet_CP-1/00 datasize index 8 8 *Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 102X.dctBXctBXctBX`W`P`> *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 3 *Oct 28 21:31:12.091:Telnet_CP-1/00 parity index 1 0 *Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 103 X.dctBXctBXctBX`W`P`> *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 4 *Oct 28 21:31:12.091:Telnet_CP-1/00 stopbits index 1 *Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 104 X.dctBXctBXctBX`W`P`> *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 5 *Oct 28 21:31:12.091:Telnet_CP-1/00 HW flow on *Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 105 X.dctBXctBXctBX`W`P`> *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 11 nTTY1/00:Telnet COMPORT rcvd ba d suboption:0xB/0xEE *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 5 *Oct 28 21:31:12.091:Telnet_CP-1/00 unimplemented option 0x10 *Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 105 *Oct 28 21:31:12.091:Telnet1/00:recv SB 44 5 *Oct 28 21:31:12.091:Telnet_CP-1/00 DTR on *Oct 28 21:31:12.091:Telnet1/00:Sent SB 44 105X.dctBXctBXctBX`W`P`> *Oct 28 21:31:12.091:TCP1/00:Telnet received WONT WINDOW-SIZE (31) *Oct 28 21:31:12.099:Telnet1/00:Sent SB 44 107 3 *Oct 28 21:31:12.099:COMPORT1/00:sending notification 0x33


debug telnet Field Descriptions

Field

Description

Telnet1/00: 1 1 251 1

Untranslated decimal option negotiations that are sent. 1/00 denotes the line number that the Telnet server is operating on.

TCP1/00:

Symbolically decoded option negotiations. 1/00 denotes the line number that the Telnet server is operating on. Telnet option negotiations are defined in the following RFCs: •

RFC 854—Telnet Protocol Specification

•

RFC 856—Telnet Binary Transmission

•

RFC 858—Telnet Suppress Go Ahead Option

•

RFC 1091—Telnet Terminal-Type Option

•

RFC 1123, sec. 3—Requirements for Internet Hosts—Application and Support

•

RFC 2217—Telnet Com Port Control Option


DB-2171


Related Commands

Command

Description

debug ip tcp transactions

Displays information on significant TCP transactions such as state changes, retransmissions, and duplicate packets.

debug modem

Displays modem line activity on an access server.


DB-2172

May 2008

Debug Commands debug text-to-fax

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T


12.2SX


Examples

The following debug output shows the off-ramp text-to-fax conversion. Router# debug text-to-fax Text to fax debugging is on Router#6d03h: text2fax_data_handler: START_OF_CONNECTION 6d03h: text2fax_data_handler: new_context 6d03h: text2fax_data_handler: resolution: fine 6d03h: text2fax_data_handler: buffer size: 50 6d03h: text2fax_put_buffer: START_OF_FAX_PAGE 6d03h: text2fax_put_buffer: START_OF_FAX_PAGE 6d03h: text2fax_put_buffer: END_OF_FAX_PAGE. Dial now ...if not in progress 6d03h: 6d03h: 6d03h: 6d03h: 6d03h: 6d03h: 6d03h: 6d03h:

text2fax_data_handler: START_OF_DATA text2fax_data_handler: END_OF_DATA text2fax_data_handler: Dispose context text2fax_data_handler: START_OF_CONNECTION text2fax_data_handler: END_OF_CONNECTION %FTSP-6-FAX_CONNECT: Transmission %FTSP-6-FAX_DISCONNECT: Transmission %LINK-3-UPDOWN: Interface Serial1:22, changed state to down


DB-2173

Debug Commands debug tftp

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

Syntax Description


Command Modes

Privileged EXEC

Examples

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

msclock msclock msclock msclock msclock msclock

0x292B4; 0x2A63C; 0x2A6DC; 0x2A6DC; 0x2A6DC; 0x2A6E4;

Sending write request (retry 0), socket_id 0x301DA8 Sending write request (retry 1), socket_id 0x301DA8 Received ACK for block 0, socket_id 0x301DA8 Received ACK for block 0, socket_id 0x301DA8 Sending block 1 (retry 0), socket_id 0x301DA8 Received ACK for block 1, socket_id 0x301DA8

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

debug tftp Field Descriptions

Message

Description

TFTP:

TFTP packet.

msclock 0x292B4;

Internal timekeeping clock (in milliseconds).

Sending write request (retry 0)

TFTP operation.

socket_id 0x301DA8

Unique memory address for the socket for the TFTP connection.


DB-2174

May 2008

Debug Commands debug tgrep error

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines

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

Examples

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

: : : :

Process Process Process Process

socket socket socket socket

event event event event

has has has has

an an an an

invalid invalid invalid invalid

fd fd fd fd

to to to to

work work work work

on on on on

After the errors are reported, the open dump begins. The ITAD is identified in the dump. ------------------------ OPEN DUMP BEGINS -----------------------0x1 0xFFFFFFFF 0x0 0xFFFFFFB4 0x0 0x0 0x4 0x58 0x6 0x7 0xFFFFFF98 0xFFFFFFA9 0x0 0xC 0x0 0x1 0x0 0x8 0x0 0x2 0x0 0x4 0x0 0x0 0x0 0x3 Version

:1


DB-2175

Debug Commands debug tgrep error

Hold Time My ITAD TRIP ID

:180 :1112 :101161129

Option Paramater #1 Param Type: Capability Length 8 Cap Code :Send Receive Capability Cap Len :4 Send Rec Cap: RCV ONLY MODE -->All route types supported ------------------------ OPEN DUMP ENDS ------------------------

The “We already have connection with such itad/tripid combo in progress” message appears when an error occurs where two location servers with the same ITAD and TripID initiate a TRIP connection to the gateway. We already have connection with such itad/tripid combo in progress NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet Errors : Process socket event has an invalid fd to work on Error: Active connection to the nbr failed NBR:16.1.1.203 Errors : Process socket event has an invalid fd to work on Errors : Process socket event has an invalid fd to work on NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet Errors : Process socket event has an invalid fd to work on Errors : Process socket event has an invalid fd to work on NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet Errors : Process socket event has an invalid fd to work on

Related Commands

Command

Description

debug tgrep events

Turns on debugging for main events occurring throughout the subsystem.

debug tgrep fsm

Turns on debugging for FSM activity.

debug tgrep io

Turns on debugging for detailed socket level activities.

debug tgrep messages

Turns on debugging for the movement of TGREP messages.

debug tgrep msgdump

Turns on debugging for the dump of the details of TGREP messages.

debug tgrep timer-event

Turns on debugging for events that are related to the timer.

debug tgrep timers

Turns on debugging for timer activity.

debug tgrep tripr

Turns on debugging for the TRIP Reporter.

debug voip eddri

Turns on debugging for the EDDRI.


DB-2176

May 2008

Debug Commands debug tgrep events

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines

There is always a performance penalty when using debug commands.

Examples

The following example shows output from the debug tgrep events command: tgrep-gw-1-02#Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time


debug tgrep events Field Descriptions

Field

Description

Received a TGREP_UPD_TIMER timeout

This event shows that a TGREP update timer timeout event occurred.

The bulkSyncQ size is 0 at this time

This event indicates the size of bulk sync queue.

The tgrepQ size is 0 at this time

This event indicates the size of TGREP queue.


DB-2177

Debug Commands debug tgrep events

Related Commands

Command

Description

debug tgrep error

Turns on debugging for any errors in functioning.

debug tgrep fsm


debug tgrep io




debug tgrep msgdump




debug tgreptimers


debug tgrep tripr


debug voip eddri



DB-2178

May 2008

Debug Commands debug tgrep fsm

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines


Examples

The following shows sample output from the debug tgrep fsm command: Generic routes combined : 0x61FA38B4, 13 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x2 0x0 0x9 0x0 0x5 0x0 0x0 0x0 0x3 0x6D 0x63 0x69 ----------------------------------+++++++++++++++++++++++++++++++++++++ NEXT HOP SERVER : 0x61FA38C1, 10 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x3 0x0 0x6 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x0 ----------------------------------+++++++++++++++++++++++++++++++++++++ AD RD PATH : 0x61FA38CB, 10 bytes ++++++++++++++++++++Getting a major event 4 on I/O

Here, a write event occurs. Note how the finite state machine details each step of the writing process. Received a TRIP_IO_WRITEQ_BOOLEAN event 313 The peer connection check for fd 1 is success Writing some pending stuff first NBR:14.1.1.210 Moving ahead with more reading rc = 4 -->Starting regular write for nbr NBR:14.1.1.210


DB-2179


The queuesize before we start is 1 Selected primary socket for NBR:14.1.1.210 The peer connection check for fd 1 is success Dequeued 1 message (left 0) for NBR:14.1.1.210 for writing to socket A socket has gulped all that we fed it NBR:14.1.1.210 -- 92 bytes Dequeued 0 message (left 0) for NBR:14.1.1.210 for writing to socket Wrote out the whole socket buffer or Q in 2 attempts NBR:14.1.1.210 rc 4 was NBR:14.1.1.210 Starting keepalive timer after writing something Getting a major event 512 on I/O Received an event on a socket for some nbr Received Mask event of 0x1 for fd 1 Looking for fd match on nbr NBR:14.1.1.210

Now a read event occurs. After this event, the total number of TRIP messages read is displayed. Recieved READ_EVENT for nbr NBR:14.1.1.210 Read 3 bytes from that network for nbr NBR:14.1.1.210 +++++++++++++++++++++++++++++++++++++ This is what we READ : 0x63E79090, 3 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x3 0x4 ----------------------------------NBR:14.1.1.210 Re-starting hold timer after a message is read tmsg malloc total memory allocated is 95 Allocated another buffer for TRIP message TRIP Messages Read so far 1 +++++++++++++++++++++++++++++++++++++ Enqueing this tmsg : 0x691D09DC, 3 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x3 0x4 ----------------------------------Enqueuing a message into the ReadQ of nbr: NBR:14.1.1.210 Read -1 bytes from that network for nbr NBR++++++++++++++++++ 0x0 0x4 0x0 0x6 0x2 0x1 0x0 0x0 0x4 0xFFFFFFD2 -----------------------------------

Statistics for available circuits, total circuits, and call success rate are displayed. +++++++++++++++++++++++++++++++++++++ AD RD PATH : 0x61FA38D5, 10 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x5 0x0 0x6 0x2 0x1 0x0 0x0 0x4 0xFFFFFFD2 ----------------------------------+++++++++++++++++++++++++++++++++++++ LOCAL PREF : 0x61FA38DF, 8 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x7 0x0 0x4 0x0 0x0 0x0 0x5 ----------------------------------+++++++++++++++++++++++++++++++++++++ Available Ckts : 0x61FA38E7, 8 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0xF 0x0 0x4 0x0 0x0 0x0 0x17 ----------------------------------+++++++++++++++++++++++++++++++++++++ TOTAL CIRCUITS : 0x61FA38EF, 8 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x10 0x0 0x4 0x0 0x0 0x0 0x17 ----------------------------------+++++++++++++++++++++++++++++++++++++


DB-2180

May 2008


CALL SUCCESS RATE : 0x61FA38F7, 12 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x11 0x0 tgrep-gw-1-02# tgrep-gw-1-02#und al:14.1.1.210 Getting a major event 512 on I/O Errors : Process socket event has an invalid fd to work on l 0x8 0x0 0x0 0x0 0x78 0x0 0x0 0x0 0x7F ----------------------------------+++++++++++++++++++++++++++++++++++++ PREFIX_ATTRIBUTE : 0x61FA3903, 64 bytes ++++++++++++++++++++++++++++++++++++++

The prefix is shown here in hex format. 0x0 0x12 0x0 0x3C 0x0 0x4 0x31 0x31 0x32 0x38 0x0 0x4 0x31 0x31 0x32 0x37 0x0 0x4 0x31 0x31 0x32 0x36 0x0 0x4 0x31 0x31 0x32 0x35 0x0 0x4 0x31 0x31 0x32 0x34 0x0 0x4 0x31 0x31 0x32 0x33 0x0 0x4 0x31 0x31 0x32 0x32 0x0 0x5 0x39 0x39 0x39 0x39 0x39 0x0 0x9 0x31 0x32 0x33 0x34 0x35 0x36

Related Commands

Command

Description

debug tgrep error


debug tgrep events


debug tgrep io




debug tgrep msgdump




debug tgrep timers


debug tgrep tripr


debug voip eddri



DB-2181

Debug Commands debug tgrep io

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines


Examples

The following shows sample output from the debug tgrep io command: Dispatching a TRIP_EV_NBR_IO_ASYNC_RESET to I/O for NBR:16.1.1.202 Dispatching a TRIP_EV_NBR_IO_ASYNC_RESET to I/O for NBR:16.1.1.203 A socket has gulped all that we fed it NBR:16.1.1.202 -- 5 bytes Closing all the fds for NBR:16.1.1.202 NBR:16.1.1.202 is not eligible to write, no non(-1) fd yet NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet A Socket error has caused a write failure NBR:16.1.1.203 errno 13 Closing all the fds for NBR:16.1.1.203 NBR:16.1.1.202 is not eligible to write, no non(-1) fd yet NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet

At this point, the connection is initiated. Going to initiate a connect to 16.1.1.202 Called a socket_connect with errno 11, confirmation later Initiated a Async connect call for nbr NBR:16.1.1.202 fd 1 Received Mask event of 0x1 for fd 1 Recieved WRITE_EVENT for nbr NBR:16.1.1.202 Only Active Open Succeeded Post connect succeeded for the nbr NBR:16.1.1.202, fd 1 A socket has gulped all that we fed it NBR:16.1.1.202 -- 29 bytes Wrote out the whole socket buffer or Q in 2 attempts NBR:16.1.1.202 rc 4 was NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet


DB-2182

May 2008


Received Mask event of 0x1 for fd 1 Recieved READ_EVENT for nbr NBR:16.1.1.202 Read -1 bytes from that network for nbr NBR:16.1.1.202 Received Mask event of 0x1 for fd 1 Recieved READ_EVENT for nbr NBR:16.1.1.202 Read 3 bytes from that network for nbr NBR:16.1.1.202 Read -1 bytes from that network for nbr NBR:16.1.1.202

Errors begin to appear here. Errors : Process socket event has an invalid fd to work on Received Mask event of 0x1 for fd 1 Recieved READ_EVENT for nbr NBR:16.1.1.202 Read 29 bytes from that network for nbr NBR:16.1.1.202 Read -1 bytes from that network for nbr NBR:16.1.1.202 Errors : Process socket event has an invalid fd to work on

After the errors are detected, a dump occurs. The Internet Telephony Administrative Domain (ITAD) and Telephony Routing over IP (TRIP) ID are displayed. ------------------------ OPEN DUMP BEGINS -----------------------0x1 0xFFFFFFFF 0x0 0xFFFFFFB4 0x0 0x0 0x4 0x58 0x6 0x7 0xFFFFFF98 0xFFFFFFA9 0x0 0xC 0x0 0x1 0x0 0x8 0x0 0x2 0x0 0x4 0x0 0x0 0x0 0x3 Version Hold Time My ITAD TRIP ID

:1 :180 :1112 :101161129

Option Paramater #1 Param Type: Capability Length 8 Cap Code :Send Receive Capability Cap Len :4 Send Rec Cap: RCV ONLY MODE -->All route types supported ------------------------ OPEN DUMP ENDS -----------------------Doing fd reassignment for nbr NBR:16.1.1.202 Moving ahead with more reading rc = 4 A socket has gulped all that we fed it NBR:16.1.1.202 -- 3 bytes Wrote out the whole socket buffer or Q in 2 attempts NBR:16.1.1.202 rc 4 was NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet Received Mask event of 0x1 for fd 1 Recieved READ_EVENT for nbr NBR:16.1.1.202 Read 3 bytes from that network for nbr NBR:16.1.1.202 Read -1 bytes from that network for nbr NBR:16.1.1.202 Moving ahead with more reading rc = 4 A socket has gulped all that we fed it NBR:16.1.1.202 -- 598 bytes Wrote out the whole socket buffer or Q in 2 attempts NBR:16.1.1.202 rc 4 was NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet Errors : Process socket event has an invalid fd to work on Received Mask event of 0x1 for fd 1 Recieved READ_EVENT for nbr NBR:16.1.1.202 Read 3 bytes from that network for nbr NBR:16.1.1.202 Read -1 bytes from that network for nbr NBR:16.1.1.202 Errors : Process socket event has an invalid fd to work on Received Mask event of 0x1 for fd 1 Recieved READ_EVENT for nbr NBR:16.1.1.202 Read 15 bytes from that network for nbr NBR:16.1.1.202


DB-2183


Read -1 bytes from that network for nbr NBR:16.1.1.202 Errors : Process socket event has an invalid fd to work on Going to initiate a connect to 16.1.1.203 Called a socket_connect with errno 11, confirmation later Initiated a Async connect call for nbr NBR:16.1.1.203 fd 2 Received Mask event of 0x1 for fd 2 Recieved WRITE_EVENT for nbr NBR:16.1.1.203 The Active connect never succeeded, no passive yet, resetting NBR:16.1.1.203 Error: Active connection to the nbr failed NBR:16.1.1.203 A Socket error has caused a write failure NBR:16.1.1.203 errno 13 Closing all the fds for NBR:16.1.1.203 Post connect succeeded for the nbr NBR:16.1.1.203, fd -1 Moving ahead with more reading rc = 4 NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet Errors : Process socket event has an invalid fd to work on Going to initiate a connect to 16.1.1.203 Called a socket_connect with errno 11, confirmation later Initiated a Async connect call for nbr NBR:16.1.1.203 fd 2 Received Mask event of 0x1 for fd 2

Errors continue to occur. Note that the router still attempts to write, but the connection is not active. Recieved WRITE_EVENT for nbr NBR:16.1.1.203 The Active connect never succeeded, no passive yet, resetting NBR:16.1.1.203 Error: Active connection to the nbr failed NBR:16.1.1.203 A Socket error has caused a write failure NBR:16.1.1.203 errno 13 Closing all the fds for NBR:16.1.1.203 Post connect succeeded for the nbr NBR:16.1.1.203, fd -1 Moving ahead with more reading rc = 4 NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet Errors : Process socket event has an invalid fd to work on Received Mask event of 0x1 for fd 1 Recieved READ_EVENT for nbr NBR:16.1.1.202 Read 3 bytes from that network for nbr NBR:16.1.1.202 Read -1 bytes from that network for nbr NBR:16.1.1.202 Errors : Process socket event has an invalid fd to work on Going to initiate a connect to 16.1.1.203 Called a socket_connect with errno 11, confirmation later Initiated a Async connect call for nbr NBR:16.1.1.203 fd 2 Received Mask event of 0x1 for fd 2 Recieved WRITE_EVENT for nbr NBR:16.1.1.203 The Active connect never succeeded, no passive yet, resetting NBR:16.1.1.203 Error: Active connection to the nbr failed NBR:16.1.1.203 A Socket error has caused a write failure NBR:16.1.1.203 errno 13 Closing all the fds for NBR:16.1.1.203 Post connect succeeded for the nbr NBR:16.1.1.203, fd -1 Moving ahead with more reading rc = 4 NBR:16.1.1.203 is not eligible to write, no non(-1) fd yet Errors : Process socket event has an invalid fd to work on

Related Commands

Command

Description

debug tgrep error


debug tgrep events


debug tgrep fsm




debug tgrep msgdump



DB-2184

May 2008


Command

Description



debug tgrep timers


debug tgrep tripr


debug voip eddri



DB-2185

Debug Commands debug tgrep messages

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines


Examples

The following shows sample output from the debug tgrep messages command: tgrep-gw(config-tgrep)#Received an OPEN NBR:14.1.1.210 ------------------------ OPEN DUMP BEGINS -----------------------0x1 0x0 0x0 0xFFFFFFB4 0x0 0x0 0x0 0x19 0x0 0x0 0x45 0x67 0x0 0x0 Version Hold Time My ITAD TRIP ID

:1 :180 :25 :17767

No optional parameters -- hence all route types supported. Send-Recv capability in effect ------------------------ OPEN DUMP ENDS ------------------------

After the dump occurs, the TRGREP messages are displayed. In this case, keepalive messages are being received by this gateway. Enqueued a Keepalive for NBR:14.1.1.210


DB-2186

May 2008

Debug Commands debug tgrep messages

Received an KEEPALIVE NBR:14.1.1.210 Received Keepalive for NBR:14.1.1.210 Received an KEEPALIVE NBR:14.1.1.210

Related Commands

Command

Description

debug tgrep error


debug tgrep events


debug tgrep fsm


debug tgrep io


debug tgrep msgdump




debug tgrep timers


debug tgrep tripr


debug voip eddri



DB-2187

Debug Commands debug tgrep msgdump

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines


Examples

The following shows sample output from the debug tgrep msgdump command: tgrep-gw-1-02#Received an KEEPALIVE NBR:14.1.1.210 +++++++++++++++++++++++++++++++++++++ TMSG datagramstart : 0x69188648, 150 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0xFFFFFF96 0x2 0x0 0x1 0x0 0x0 0x0 0x2 0x0 0x9 0x0 0x5 0x0 0x0 0x0 0x3 0x6D 0x63 0x69 0x0 0x3 0x0 0x6 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x0 0x0 0x4 0x0 0x6 0x2 0x1 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x5 0x0 0x6 0x2 0x1 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x7 0x0 0x4 0x0 0x0 0x0 0x5 0x0 0xF 0x0 0x4 0x0 0x0 0x0 0x16 0x0 0x10 0x0 0x4 0x0 0x0 0x0 0x17 0x0 0x11 0x0 0x8 0x0 0x0 0x0 0x74 0x0 0x0 0x0


DB-2188

May 2008


0x7B 0x0 0x12 0x0 0x3C 0x0 0x4 0x31 0x31 0x32 0x38 0x0 0x4 0x31 0x31 0x32 0x37 0x0 0x4 0x31 0x31 0x32 0x36 0x0 0x4 0x31 0x31 0x32 0x35 0x0 0x4 0x31 0x31 0x32 0x34 0x0 0x4 0x31 0x31 0x32 0x33 0x0 0x4 0x31 0x31 0x32 0x32 0x0 0x5 0x39 0x39 0x39 0x39 0x39 0x0 0x9 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39

After each event occurs, a dump of the message appears. The entire dump of each keepalive is being displayed. ----------------------------------Received an KEEPALIVE NBR:14.1.1.210 +++++++++++++++++++++++++++++++++++++ TMSG datagramstart : 0x691B0CA0, 92 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0x5C 0x2 0x0 0x1 0x0 0x0 0x0 0x2 0x0 0xF 0x0 0x3 0x0 0x0 0x0 0x9 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 0x0 0x3 0x0 0x6 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x0 0x0 0x4 0x0 0x6 0x2 0x1 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x5 0x0 0x6 0x2 0x1 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x7 0x0 0x4 0x0 0x0 0x0 0x5 0x0 0xF 0x0 0x4 0x0 0x0 0x0 0x17 0x0 0x10 0x0 0x4 0x0 0x0 0x0 0x17 0x0 0x11 0x0 0x8 0x0 0x0 0x0 0x75 0x0 0x0 0x0 0x78 ----------------------------------+++++++++++++++++++++++++++++++++++++ TMSG datagramstart : 0x691885EC, 150 bytes ++++++++++++++++++++++++++++++++++++++ 0x0 0xFFFFFF96 0x2 0x0 0x1 0x0 0x0 0x0 0x2 0x0 0x9 0x0 0x5 0x0 0x0 0x0 0x3 0x6D 0x63 0x69 0x0 0x3 0x0 0x6 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x0 0x0 0x4 0x0 0x6 0x2 0x1 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x5 0x0 0x6 0x2 0x1 0x0 0x0 0x4 0xFFFFFFD2 0x0 0x7 0x0 0x4 0x0 0x0 0x0 0x5 0x0 0xF 0x0 0x4 0x0 0x0 0x0 0x16 0x0 0x10 0x0 0x4 0x0 0x0 0x0 0x17 0x0 0x11 0x0 0x8 0x0 0x0 0x0 0x75 0x0 0x0 0x0 0x7C 0x0 0x12 0x0 0x3C 0x0 0x4 0x31 0x31 0x32


DB-2189


0x38 0x0 0x4 0x31 0x31 0x32 0x37 0x0 0x4 0x31 0x31 0x32 0x36 0x0 0x4 0x31 0x31 0x32 0x35 0x0 0x4 0x31 0x31 0x32 0x34 0x0 0x4 0x31 0x31 0x32 0x33 0x0 0x4 0x31 0x31 0x32 0x32 0x0 0x5 0x39 0x39 0x39 0x39 0x39 0x0 0x9 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 ----------------------------------Received an KEEPALIVE NBR:14.1.1.210 Received an KEEPALIVE NBR:14.1.1.210

Related Commands

Command

Description

debug tgrep error


debug tgrep events


debug tgrep fsm


debug tgrep io






debug tgrep timers


debug tgrep tripr


debug voip eddri



DB-2190

May 2008

Debug Commands debug tgrep timer-event

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines


Examples

The following shows sample output from the debug tgrep timer-event command: Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry

The Telephony Routing over IP (TRIP) timer registers timeouts until the next event occurs. Here, the timers are reset. Entering trip_reset_nbr_timers to reset timers Starting the CONNECT timer for nbr NBR:16.1.1.202 for value of 30 seconds Stopping hold timer and keepalive timer while resetting NBR:16.1.1.202 Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time


DB-2191


Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry

Timeouts are again reported until the next event. Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry

Here, the TRIP neighbor is cleared, which causes the timer to reset. Router#clear trip nei * Router#Entering trip_reset_nbr_timers to reset timers Starting the CONNECT timer for nbr NBR:16.1.1.202 for value of 30 seconds Stopping hold timer and keepalive timer while resetting NBR:16.1.1.202 Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 3 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry IO_CONNECT TIMER for nbr NBR:16.1.1.202 has expired NBR:16.1.1.202 -Restarting the connect timer NBR:16.1.1.202 starting the holder timer after post connect with large value ------------------------ OPEN DUMP BEGINS -----------------------0x1 0xFFFFFFFF 0x0 0xFFFFFFB4 0x0 0x0 0x4 0x58 0x6 0x7


DB-2192

May 2008


0xFFFFFF98 0xFFFFFFA9 0x0 0xC 0x0 0x1 0x0 0x8 0x0 0x2 0x0 0x4 0x0 0x0 0x0 0x3 Version Hold Time My ITAD TRIP ID

:1 :180 :1112 :101161129

Option Paramater #1 Param Type: Capability Length 8 Cap Code :Send Receive Capability Cap Len :4 Send Rec Cap: RCV ONLY MODE -->All route types supported ------------------------ OPEN DUMP ENDS -----------------------NBR:16.1.1.202 Starting keepalive timer after writing something NBR:16.1.1.202 Re-starting hold timer after a message is read Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPNBR:16.1.1.202 Starting keepalive timer after writing so mething NBR:16.1.1.202 Re-starting hold timer after a message is read D timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIIO_CONNECT TIMER for nbr NBR:16.1.1.202 has expired NBR:16.1.1.202 -Stopping the connect timer, no need anymore MER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry NBR:16.1.1.202 Re-starting hold timer after a message is read


DB-2193


Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry

Related Commands

Command

Description

debug tgrep error


debug tgrep events


debug tgrep fsm


debug tgrep io




debug tgrep msgdump


debug tgrep timers


debug tgrep tripr


debug voip eddri



DB-2194

May 2008

Debug Commands debug tgrep timers

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines


Examples

The following shows sample output from the debug tgrep timers command: tgrep-gw-1-02#Received a TGREP_UPD_TIMER timeout The bulkSyncQ size is 0 at this time The tgrepQ size is 0 at this time Restarting the router UPD timer after expiry


debug tgrep timers Field Descriptions

Field

Description

Received a TGREP_UPD_TIMER timeout

This indicates that a timeout was received.

The bulkSyncQ size is 0 at this time

This indicates the size of the bulk sync queue.

The tgrepQ size is 0 at this time

This indicates the size of the TGREP queue.

Restarting the router UPD timer after This indicates that the timer has been reset. expiry


DB-2195

Debug Commands debug tgrep timers

Related Commands

Command

Description

debug tgrep error


debug tgrep events


debug tgrep fsm


debug tgrep io




debug tgrep msgdump




debug tgrep tripr


debug voip eddri



DB-2196

May 2008

Debug Commands debug tgrep tripr

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines

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

Examples

The following shows sample output from the debug tgrep tripr command: 20:51:11: tripr_build_triprtr_prefix_destination_ev 1 advertise 0x2prefix 1128 addrFam 4 20:51:11: tripr_build_triprtr_prefix_destination_ev 20:51:11: tripr_build_triprtr_prefix_destination_ev 20:51:11: 20:51:11: -------------------------------20:51:11: attrib 0x4002 20:51:11: ******* REACHABLE ROUTE ****** 20:51:11: TRIP_AF_E164 1128 20:51:11: ac: 22 20:51:11: 20:51:11: ======================================= 20:51:11: tripr_build_triprtr_prefix_destination_ev 1 advertise 0x27prefix 123456789 addrFam 4 20:51:11: tripr_build_triprtr_prefix_destination_ev 20:51:11: tripr_build_triprtr_prefix_destination_ev

: got the ev id 1 reason 64 num_prefix ac 22 tc 23 ac_avg 22 csr success 0 total 0

: got the ev id 1 reason 64 num_prefix ac 22 tc 23 ac_avg 22 csr success 117 total 120


DB-2197


20:51:11: tg mci cc mci 20:51:11: tripr_build_triprtr_prefix_destination_ev 20:51:11: 20:51:11: -------------------------------20:51:11: attrib 0x1C002 20:51:11: ******* REACHABLE ROUTE ****** 20:51:11: TRIP_AF_E164 123456789 20:51:11: csr: tot 120 succ 117 20:51:11: ac: 22tc: 23 20:51:11: 20:51:11: ======================================= 20:51:11: tripr_build_triprtr_prefix_destination_ev 1 advertise 0x27prefix 99999 addrFam 4 20:51:11: tripr_build_triprtr_prefix_destination_ev 20:51:11: tripr_build_triprtr_prefix_destination_ev 20:51:11: tg mci cc mci 20:51:11: tripr_build_triprtr_prefix_destination_ev 20:51:11: 20:51:11: -------------------------------20:51:11: attrib 0x1C002 20:51:11: ******* REACHABLE ROUTE ****** 20:51:11: TRIP_AF_E164 99999 20:51:11: csr: tot 0 succ 0 20:51:11: ac: 22tc: 23 20:51:11: 20:51:11: =======================================

tg mci cic 0 carrier mci

: got the ev id 1 reason 64 num_prefix ac 22 tc 23 ac_avg 22 csr success 0 total 0 tg mci cic 0 carrier mci


DB-2198

May 2008


Table 337 describes the significant fields in the display. Table 337

debug tgrep tripr Field Descriptions

Field

Description

ev id

This field can contain the following entries:

reason: (for a prefix family event)

•

1—Prefix regular event

•

2—Trunk group regular event

•

3—Carrier regular event

•

4—Prefix sync event

•

5—Trunk group sync event

•

6—Carrier sync event

•

7—Null sync event

This field can contain the following entries: •

1—Prefix down

•

2—Prefix up

•

4—Prefix trunk group attribute changed

•

8—Prefix available circuits changed

•

16—Prefix total circuits changed

•

32—Prefix CSR changed

•

64—Prefix AC interesting point

•

128—Prefix carrier attributes changed

•

256—Prefix stop advertise configured

•

512—Prefix start advertise configured


DB-2199


Table 337

debug tgrep tripr Field Descriptions (continued)

Field

Description

reason: (for a trunk group family event)

This field can contain the following entries:

reason: (for a carrier family event)

Related Commands

•

1—Trunk group down

•

2—Trunk group up

•

4—Trunk group prefix attribute changed

•

8—Trunk group available circuits changed

•

16—Trunk group total circuits changed

•

32—Trunk group CSR changed

•

64—Trunk group AC interesting point

•

128—Trunk group stop advertise configured

•

256—Trunk group start advertise configured

This field can contain the following entries: •

1—Carrier down

•

2—Carrier up

•

4—Carrier prefix attribute changed

•

8—Carrier available circuits changed

•

16—Carrier total circuits changed

•

32—Carrier CSR changed

•

64—Carrier AC interesting point

•

128—Carrier stop advertise configured

•

256—Carrier start advertise configured

Command

Description

debug tgrep error


debug tgrep events


debug tgrep fsm


debug tgrep io


debug tgrep messsages


debug tgrep msgdump




debug tgrep timers


debug voip eddri



DB-2200

May 2008

Debug Commands debug tgrm

debug tgrm To display debugging messages for all trunk groups, use the debug tgrm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug tgrm [all | default | detail | error [call [informational] | software [informational]] | function | inout | service] no debug tgrm

Syntax Description

all

(Optional) Displays all TGRM debugging messages.

default

(Optional) Displays detail, error, and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays non-inout information related to call processing, such as call updates or call acceptance checking.

error

(Optional) Displays TGRM error messages.

call


informational


software


function

(Optional) Displays TGRM functions.

inout

(Optional) Displays information from the functions that form the external interfaces of TGRM to other modules or subsystems.

service

(Optional) Displays TGRM services.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)T


Usage Guidelines

12.2(2)XB1


12.2(11)T


12.3(8)T

The all, default, detail, error, call, informational, software, function, inout, and service keywords were added to this command.

12.2SX


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


DB-2201


Caution

Examples

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

The following is sample output from the debug tgrm all command for an incoming CAS call on a trunk group that is rejected because of the max-calls command: Router# debug tgrm all 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_accept_call: Timeslot=11, CallType=Voice, CallDirection=Incoming, Slot=2, SubUnit=1, Port=1, DS0-Group=1 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_member_core: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_trunk_member: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_trunk_member: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_member_trunk_internal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_member_core: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_trunk_member: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_trunk_member: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_equal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_channel_active: Trunk=2/1:1 (TG 211), Timeslot=11, CallType=Voice, CallDirection=Incoming 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_channel_delete: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_trunk_channel_delete_queue: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_call_count_update: CallDirection=Incoming, Increment call count 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_call_count_update_no_crm: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_call_count_update_no_crm: CountType=TGRM_COUNT_VOICE, CallDirection=Incoming, Increment call count Updated values: CallCount=1, FreeTimeslots=23 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_call_count_update_crm: CallType=Voice, CallDirection=Incoming, Increment the call count 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: TG 211 found 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info: TG 211 found 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_status: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: TG 211 found 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_allow_call: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_allow_call: TG 211; CallType=Voice CallDirection=Incoming 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_allow_call: Call denied; CallType=Voice CallDirection=Incoming; MaxAllowed=0 Current=1 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_accept_call: Call Rejected; Reason - Maximum voice calls exceeded 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info_internal: TG 211 found 03:53:56: //-1/xxxxxxxxxxxx/TGRM/tgrm_tg_info: TG 211 found


DB-2202

May 2008



debug tgrm all Field Descriptions

Field

Description

//-1/xxxxxxxxxxxx/TGRM/ tgrm_accept_call:



•

GUID is xxxxxxxxxxxx. This indicates that the GUID information is unavailable.

•

TGRM is the module name.

•

The tgrm_accept_call field shows that the trunk group is accepting a call.

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

Shows information about the call, including timeslot, call type and direction, and port information.

tgrm_trunk_channel_active:

Shows information for the active trunk group, including the port, timeslot, and call type and direction.

Trunk=2/1:1 (TG 211), Timeslot=11, CallType=Voice, CallDirection=Incoming tgrm_tg_call_count_update: CallDirection=Incoming, Increment call count tgrm_tg_call_count_update_no_crm: CountType=TGRM_COUNT_VOICE, CallDirection=Incoming, Increment call count

Indicates that the call counter for the trunk group has been incremented. Indicates that the call counter for the trunk group has been updated outside of the Carrier Resource Manager (CRM). This field contains more data than a call counter increment message that uses the CRM.

Updated values: CallCount=1, FreeTimeslots=23 tgrm_allow_call:

Shows that a call was allowed on the 2/1:1 trunk.

TG 211; CallType=Voice CallDirection=Incoming tgrm_allow_call:

Shows that a call on the trunk group was denied.

Call denied; CallType=Voice CallDirection=Incoming; MaxAllowed=0 Current=1 tgrm_accept_call: Call Rejected; Reason - Maximum voice calls exceeded

Shows that a call was rejected on this trunk group due to a maximum number of voice calls being received.


DB-2203

Debug Commands debug tidp

debug tidp To configure a networking device to process and display Threat Information Distribution Protocol (TIDP) debug messages, use the debug tidp command in privileged EXEC mode. To stop debug messages from being processed and displayed, use the no form of this command. debug tidp {errors | events | packets | registration | test} no debug tidp {errors | events | packets | registration | test}

Syntax Description

errors

Displays debug error messages.

events

Displays general events.

packets

Displays packet information.

registration

Displays registration information.

test

Enables the TIDP test CLI, which allows you to use the tidp test command.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(6)T


12.2SX


Usage Guidelines

The test keyword is entered to enable the TIDP test CLI, which allows you to send test messages between TIDP peers. This command must be enabled on the sender and receiver. The registration keyword is entered to enable debug messages related to TIDP peer registration. This command is useful for troubleshooting peer registration problems and authentication/encryption key mismatches. The packets keyword is entered to enable debug messages related to general TIDP communication problems. The errors keyword is entered to enable debug messages that display information about unexpected error conditions. The events keyword is entered to enable debug messages that display information about general TIDP transactions and events.

Examples

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


DB-2204

May 2008


Router# debug tidp errors TIDP errors debugging is on Router# 01:23:04: %TIDP-4-AUTHFAIL: Message from 10.1.1.3 failed authentication 01:44:53: %TIDP-5-REGFAIL: Failed to register to peer 10.1.1.2, group 10


debug tidp errors Field Descriptions

Field

Description

TIDP errors debugging is on

TIDP error debugging has been enabled.

TIDP-4-AUTHFAIL: Message from 10.1.1.3 failed authentication

TIDP failed to authenticate a message from the 10.1.1.3 peer.

TIDP-5-REGFAIL: Failed to register to TIDP failed to register the 10.1.1.2 peer in group 10. peer 10.1.1.2, group 10 The following example is sample output from the debug tidp command entered with the events keyword: Router# debug tidp events TIDP events debugging is on 00:07:49: 00:10:16: 00:11:13: 00:12:25: 00:13:31: 00:14:46: 00:15:38: 00:22:12:

TIDP: TIDP: TIDP: TIDP: TIDP: TIDP: TIDP: TIDP:

New key set KEY_1 added New authentication receive key added New authentication send key added New group added - 10 New peer 10.1.1.2 added to group 10 Registration interval changed from (min: 4294967295, max: 42949) Source-ip changed from 0.0.0.0 to 10.1.1.1 TIDP enabled


debug tidp events Field Descriptions

Field

Description

TIDP events debugging is on

TIDP event debugging has been enabled.

TIDP: New key set RED added

Key-set RED has been configured.

TIDP: New authentication receive key added

A receive authentication key has been configured.

TIDP: New authentication send key added

A send authentication key has been configured.

TIDP: New group added - 10

TIDP group 10 was created.

TIDP: New peer 10.1.1.2 added to group 10

The 10.1.1.2 peer was added to group 10.

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

The registration interval has been manually configured.


DB-2205


Table 340

debug tidp events Field Descriptions (continued)

Field

Description

TIDP: Source-ip changed from 0.0.0.0 to 10.1.1.1

The TIDP source interface has been configured.

TIDP: TIDP enabled

TIDP has been enabled.

The following example is sample output from the debug tidp command entered with the packets keyword: Router# debug tidp packets TIDP packets debugging is on 00:14:01: 00:14:01: 00:14:31: 00:14:31:

TIDP: TIDP: TIDP: TIDP:

tidp_build_conx connecting tidp_build_conx connecting tidp_complete_conx connect tidp_complete_conx connect

to 10.1.1.2, fd 1 to 10.1.1.4, fd 4 failed to 10.1.1.2, fd 1 failed to 10.1.1.4, fd 4


debug tidp packets Field Descriptions

Field

Description

TIDP: tidp_build_conx connecting to 10.1.1.2, fd 1

TIDP is attempting to connect the 10.1.1.2 peer.

TIDP: tidp_complete_conx connect failed to 10.1.1.2, fd 1

TIDP failed to connect to the 10.1.1.2 peer.

The following example is sample output from the debug tidp command entered with the registration keyword: Router# debug tidp registration TIDP registration debugging is on 00:36:13: TIDP: tidp_process_reg_msg Registered to 10.1.1.3, grp 10 00:39:46: TIDP: tidp_clear_conx Deregistered peer 10.1.1.4, grp 10


debug tidp registration Field Descriptions

Field

Description

TIDP: tidp_process_reg_msg Registered to 10.1.1.3, grp 10

TIDP successfully registered the 10.1.1.3 peer.

TIDP: tidp_clear_conx Deregistered peer 10.1.1.4, grp 10

TIDP successfully deregistered the 10.1.1.4 peer.

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


DB-2206

May 2008


Sender (10.1.1.1) Router1# debug tidp test TIDP test debugging is on Router1# test tidp send group 10 peer 10.1.1.2 Unicast_Test_Message

Receiver (10.1.1.2) Router2# debug tidp test TIDP test debugging is on Router2# 03:36:03: TIDP msg from 10.1.1.1, group 10: 'Unicast_Test_Message'


Related Commands

debug tidp test Field Descriptions

Field

Description

TIDP test debugging is on

TIDP test debugging CLI has been enabled.

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

TIDP test message printed in the console of the receiving peer.

Command

Description

test tidp

Sends test messages to a TIDP group or peer.


DB-2207

Debug Commands debug tiff reader

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

Syntax Description


Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T


12.2SX


Examples

The following debug example displays information about the off-ramp TIFF reader. Router# debug tiff reader *Jan 1 18:59:13.683: tiff_reader_data_handler: new context *Jan 1 18:59:13.683: tiff_reader_data_handler: resolution: standard *Jan 1 18:59:13.683: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() ENGINE_START/DONE gggg(pl 616E9994) *Jan 1 18:59:13.691: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.699: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) *Jan 1 18:59:13.703: tiff_reader_put_buffer: START_OF_FAX_PAGEi>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.711: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.719: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.727: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.735: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.743: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg


DB-2208

May 2008

Debug Commands debug tiff reader

*Jan 1 18:59:13.751: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.759: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.767: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.775: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.787: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.795: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.803: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.811: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.819: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.827: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.835: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.843: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.851: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.863: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.871: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.879: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.887: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.895: tiff_reader_data_handler: buffer size: 1524 *Jan 1 18:59:13.903: tiff_reader_data_handler: buffer size: 1524i>> tiff_reader_engine() case FAX_EBUFFER pppp(pl 616E9994) i>> tiff_reader_engine() case FAX_EBUFFER gggg *Jan 1 18:59:13.907: tiff_reader_data_handler: buffer size: 311i>> tiff_r_finish() END_OF_FAX_PAGE pppp *Jan 1 18:59:13.907: progress *Jan 1 18:59:13.907: *Jan 1 18:59:13.907: *Jan 1 18:59:13.907:

Related Commands

tiff_reader_put_buffer: END_OF_FAX_PAGE. Dial now ...if not in tiff_reader_data_handler: END_OF_DATA tiff_reader_data_handler: BUFF_END_OF_PART tiff_reader_data_handler: Dispose context

Command

Description

debug tiff writer

Displays output about the on-ramp TIFF writer.


DB-2209

Debug Commands debug tiff writer

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

Syntax Description


Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)T


12.2SX


Examples

The following debug example shows information about the off-ramp TIFF writer. Router# debug tiff writer *Jan 1 18:54:59.419: tiff_writer_data_process: START_OF_CONNECTION 18:55:10: %FTSP-6-FAX_CONNECT: Reception *Jan 1 18:55:14.903: tiff_writer_data_process: START_OF_FAX_PAGE *Jan 1 18:55:14.903: tiff_writer_data_process: tiff file created = 2000:01:01 18:55:14 18:55:21: %FTSP-6-FAX_DISCONNECT: Reception *Jan 1 18:55:19.039: tiff_writer_data_process: END_OF_CONNECTION or ABORT_CONNECTION *Jan 1 18:55:19.039: tiff_writer_put_buffer: END_OF_FAX_PAGE *Jan 1 18:55:19.039: send TIFF_PAGE_READY *Jan 1 18:55:19.039: send TIFF_PAGE_READY 18:55:21: %LINK-3-UPDOWN: Interface Serial2:0, changed state to down

Related Commands

Command

Description

debug tiff reader

Displays output about the on-ramp TIFF reader.


DB-2210

May 2008

Debug Commands debug time-range ipc

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

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)T


12.2(28)SB


12.2SX


Examples

The following is sample output from the debug time-range ipc command. In the following example, the time ranges sent to the line card are monitored: Router# debug time-range ipc 00:14:19:TRANGE-IPC:Sent Time-range t1 ADD to all slots 00:15:22:TRANGE-IPC:Sent Time-range t1 ADD to all slots

In the following example, the time ranges deleted from the line card are monitored: Router# debug time-range ipc 00:15:42:TRANGE-IPC:Sent Time-range t1 DEL to all slots 00:15:56:TRANGE-IPC:Sent Time-range t1 DEL to all slots

Related Commands

Command

Description

show time-range ipc

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


DB-2211

Debug Commands debug tms consumer

debug tms consumer To enable the generation of debugging messages on a TIDP Based Mitigation Services (TMS) consumer, use the debug tms consumer command in privileged EXEC mode. To stop the processing and generation of debug messages, use the no form of this command. debug tms consumer {all | errors [details] | events [details] | feature-interface | packet | protocol | xml [detail | error | event]} no debug tms consumer {all | errors [details] | events [details] | feature-interface | packet | protocol | xml [detail | error | event]}

Syntax Description

all

Enables the generation of most forms of the TMS consumer debugging messages. Note

errors

XML error debugging messages are not processed when this form of this command is enabled.

Enables the generation of TMS error debugging messages.

details

(Optional) Enables the generation of detailed debugging messages.

events

Enables the generation of TMS event debugging messages.

feature-interface

Enables the generation of TMS debugging messages for ACL drop enforcement actions, or redirect enforcement actions (enabled by OER).

packet

Enables the generation of TMS packet debugging messages.

protocol

Enables the generation of TMS protocol debugging messages.

xml

Enables the generation of XML (Threat Information Message) debugging messages.

detail

(Optional) Enables the generation of detailed XML debugging messages.

error

(Optional) Enables the generation of XML error debugging messages.

event

(Optional) Enables the generation of XML event debugging messages.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(6)T


12.2SX


Usage Guidelines

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


DB-2212

May 2008


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

Examples

Event Debugging Example

The following is sample output from the debug tms consumer command entered with the events keyword: Router# debug tms consumer events TMS consumer event debugging is on *Feb 27 21:27:18: TMS_EVE_CO:start timer Controller=10.1.1.1 period=180 *Feb 27 21:27:18: TMS_EVE:Posting a message for the service layer *Feb 27 21:27:18: TMS_EVE_CO:Processing Reg messsage from ctrl=10.1.1.1 group=10 *Feb 27 21:27:18: TMS_EVE_CO:Processing Reg response from ctrl=10.1.1.1 group=10 *Feb 27 21:27:18: TMS_EVE_CO:start timer Controller=10.1.1.1 period=120


debug tms consumer events Field Descriptions

Field

Description

TMS_EVE_CO

Event information for a TMS consumer follows.

Feature-Interface Debugging Example

The following is sample output from the debug tms consumer command entered with the feature-interface keyword: Router# debug tms consumer feature-interface TMS consumer feature-interface debugging is on *Feb 27 21:28:12: TMS_FI_CO:OER:Policy Add client 2 pol id 12 tag 5000 nxthop 172.16.1.1 *Feb 27 21:28:12: TMS_FI_CO:OERCB:ctx C type 2 values 0 *Feb 27 21:28:12: TMS_FI_CO:OERCB:return code rcvd rc 1 *Feb 27 21:28:12: TMS_FI_CO:OERCB:Threat (1, 1, 1) grpid 10 ctrlip 10.1.1.1 statflags 0 pol state 1 *Feb 27 21:28:12: TMS_FI_CO:OERCB:Prefix create client 2 id 12 src 0.0.0.0 0.0.0.0 dst 192.168.8.0 255.255.255.0 proto 6 0 - 0, 10 - 2000 grant TRUE exact TRUE *Feb 27 21:28:12: TMS_FI_CO:OERCB:ctx C type 2 values 0 *Feb 27 21:28:12: TMS_FI_CO:OERCB:return code rcvd rc 1 *Feb 27 21:28:12: TMS_FI_CO:OERCB:Threat (1, 1, 1) grpid 10 ctrlip 10.1.1.1 statflags 0 pol state 3 *Feb 27 21:28:12: TMS_FI_CO:OERCB:Prefix create success with rc = 1 *Feb 27 21:28:13: TMS_FI_CO:ACL:CB3: acl 66886028 item 669C9F98 type 3 ADD *Feb 27 21:28:13: TMS_FI_CO:ACL:CB1: acl 66886028 modified. *Feb 27 21:28:13: TMS_FI_CO:ACL:CB3: acl 66886098 item 669CA0E0 type 3 ADD *Feb 27 21:28:13: TMS_FI_CO:ACL:CB1: acl 66886098 modified.


debug tms consumer feature-interface Field Descriptions

Field

Description

TMS_FI_CO

Information for a TMS feature-interface function follows.


DB-2213


Table 345

debug tms consumer feature-interface Field Descriptions (continued)

Field

Description

OER

Information for a redirect enforcement action follows.

ACL

Information for an ACL drop enforcement action follows.

Packet Debugging Example

The following is sample output from the debug tms consumer command entered with the packet keyword: Router# debug tms consumer packet TMS consumer packets debugging is on *Feb 27 00:00:38: TMSCONS:out:Type(6)HeartBeat Req trans-id 15698 len 16 *Feb 27 00:00:38: tms_flags 8 msg_flags 0 reason 0 *Feb 27 00:00:38: TLVs: *Feb 27 00:00:38: TMSCONS:in:Type(6)HeartBeat Req trans-id 158 len 16 *Feb 27 00:00:38: tms_flags 0 msg_flags 0 reason 0 *Feb 27 00:00:38: TLVs:


debug tms consumer packet Field Descriptions

Field

Description

TMSCONS

Information for a TMS consumer message follows.

TLVs

Information about the TMS packet format follows.

Protocol Debugging Example

The following is sample output from the debug tms consumer command entered with the protocol keyword: Router# debug tms consumer protocol TMS consumer protocol debugging is on *Feb 27 21:27:18: TMS_PRO_CO:Sending RegReq ctrl=10.1.1.1 group=10 *Feb 27 21:27:18: TMS_PRO_CO:RegResp recvd controller 10.1.1.1 group 10 *Feb 27 21:27:18: TMS_PRO_CO:Sending Resync request for ctrl=10.1.1.1 group=10 *Feb 27 21:27:18: TMS_PRO_CO:Resync response recvd controller 10.1.1.1, group 10 *Feb 27 21:27:18: TMS_PRO_CO:Processing Resync response from Controller=10.1.1.1on Group=10 *Feb 27 21:28:12: TMS_PRO_CO:Threat msg recvd controller 10.1.1.1, Group 10 *Feb 27 21:28:12: TMS_PRO_CO:Processing Threat request from Controller=10.1.1.1on Group=10 *Feb 27 21:28:12: TMS_PRO_CO:msg:NewThreat (1,1,1) in grp 10 ctrl 10.1.1.1 *Feb 27 21:28:58: TMS_PRO_CO:Heartbeat msg recvd controller 10.1.1.1, Group 10


debug tms consumer protocol Field Descriptions

Field

Description

TMS_PRO_CO

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


DB-2214

May 2008


XML Error Debugging Example

The following is sample output from the debug tms consumer command entered with the xml and error keywords: Router# debug tms consumer xml error TMS consumer xml error debugs debugging is on *Feb 27 21:28:12: TMS_XML_EVE:Decoding threat info *Feb 27 21:28:12: TMS_XML_EVE:Found threat info *Feb 27 21:28:12: TMS_XML_EVE:Found ERR *Feb 27 21:28:12: TMS_XML_EVE:name is name, value is tc2 *Feb 27 21:28:12: Decoded Threat desc TLV: *Feb 27 21:28:12: Threat name = NAME: *Feb 27 21:28:12: Threat text = THREATTEXT: *Feb 27 21:28:12: Mitigation text = mitigationtext: *Feb 27 21:28:12: Threat classes : [ tc2 ] *Feb 27 21:28:12: ERR: *Feb 27 21:28:12: ASR = 5, SFR = 20, TFR = 40, ARR = 30 PD = 50 *Feb 27 21:28:12: TMS_XML_EVE:Decoding primtive *Feb 27 21:28:12: TMS-XML: Decoded primitive TLV *Feb 27 21:28:12: Prim type = 2 *Feb 27 21:28:12: Primitive = redirect *Feb 27 21:28:12: TMS_XML_EVE:Decoding parameter *Feb 27 21:28:12: TMS_XML_EVE:CNS PARSER : Node is 129 tag = parameter *Feb 27 21:28:12: TMS_XML_EVE:Found parameter *Feb 27 21:28:12: TMS_XML_EVE:CNS PARSER : Node is 130 tag = redirect *Feb 27 21:28:12: TMS_XML_EVE:parameter : Found redirect *Feb 27 21:28:12: TMS_XML_EVE:Found nexthop in redirect *Feb 27 21:28:12: TMS_XML:Decoded Parameter TLV *Feb 27 21:28:12: Parameter type = 1 *Feb 27 21:28:12: Redirect addr = 172.16.1.1 *Feb 27 21:28:12: TMS_XML_EVE:Decoding match criteria *Feb 27 21:28:12: TMS-XML: Decoded match crt TLV : *Feb 27 21:28:12: Src addr : 0.0.0.0 , Src mask : 0.0.0.0 *Feb 27 21:28:12: Dest addr : 192.168.8.0 , Dest mask : 255.255.255.0 *Feb 27 21:28:12: Protocol : 6 *Feb 27 21:28:12: Src port - Start : 0, End : 0 *Feb 27 21:28:12: Dest port - Start : 10, End : 2000


Related Commands

debug tms consumer xml error Field Descriptions

Field

Description

TMS_XML_EVE

Information for XML message event debugging follows.

TMS_XML

Information for XML message debugging follows.

TMS-XML

Threat information for XML message debugging follows.

Command

Description

debug tms controller

Enables the generation of debugging messages on a TMS controller.


DB-2215

Debug Commands debug tms controller

debug tms controller To enable the generation of debugging messages on a TIDP Based Mitigation Services (TMS) controller, use the debug tms controller command in privileged EXEC mode. To stop the processing and generation of debug messages, use the no form of this command. debug tms controller {all | errors [details] | events [details] | feature-interface | packet | protocol | xml [detail | error | event]} no debug tms controller {all | errors [details] | events [details] | feature-interface | packet | protocol | xml [detail | error | event]}

Syntax Description

all

Enables the generation of most forms of the TMS consumer debugging messages. Note

errors

XML error debugging messages are not processed when this form of this command is enabled.

Enables the generation of TMS error debugging messages.

details

(Optional) Enables the generation of detailed debugging messages.

events

Enables the generation of TMS event debugging messages.

packet

Enables the generation of TMS packet debugging messages.

protocol

Enables the generation of TMS protocol debugging messages.

xml

Enables the generation of XML (Threat Information Message) debugging messages.

detail

(Optional) Enables the generation of detailed XML debugging messages.

error

(Optional) Enables the generation of XML error debugging messages.

event

(Optional) Enables the generation of XML event debugging messages.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(6)T


12.2SX


Usage Guidelines

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


DB-2216

May 2008


Examples

Event Debugging Example

The following is sample output from the debug tms controller command entered with the events keyword: Router# debug tms controller events TMS controller events debugging is on *Feb 27 10:12:42: TMS_EVE_CN:Timer expired group=10 *Feb 27 10:12:42: TMS_EVE_CN:Start timer: Group=10, *Feb 27 10:12:42: TMS_EVE:Posting a message for the *Feb 27 10:12:42: TMS_EVE_CN:Data packet recvd from *Feb 27 10:13:34: TMS_EVE:Posting a message for the *Feb 27 10:13:34: TMS_EVE_CN:Data packet recvd from *Feb 27 10:13:34: TMS_EVE_CN:Start timer: Group=10, *Feb 27 10:13:34: TMS_EVE:Posting a message for the *Feb 27 10:13:34: TMS_EVE_CN:Data packet recvd from

period=120 service layer DL layer service layer DL layer period=120 service layer DL layer


debug tms controller events Field Descriptions

Field

Description

TMS_EVE_CN

Information for a TMS controller event message follows.

Packet Debugging Example

The following is sample output from the debug tms controller command entered with the packets keyword: Router# debug tms controller packet TMS controller packets debugging is on TMS controller packets debugging is on *Feb 27 10:13:34: TMSCTRL:in:Type(1)Registration Req trans-id 15685 len 16 *Feb 27 10:13:34: tms_flags 8 msg_flags 1 reason 0 *Feb 27 10:13:34: TLVs: *Feb 27 10:13:34: TMSCTRL:out:Type(1)Registration Resp trans-id 15685 len 16 *Feb 27 10:13:34: tms_flags 1 msg_flags 1 reason 1 *Feb 27 10:13:34: TLVs: *Feb 27 10:13:34: TMSCTRL:in:Type(4)Resync/Audit Req trans-id 15686 len 16 *Feb 27 10:13:34: tms_flags 8 msg_flags 1 reason 0 *Feb 27 10:13:34: TLVs: *Feb 27 10:13:34: TMSCTRL:out:Type(4)Resync/Audit Resp trans-id 15686 len 24 *Feb 27 10:13:34: tms_flags 1 msg_flags 0 reason 0 *Feb 27 10:13:34: TLVs: Summary(514,8)


debug tms controller packet Field Descriptions

Field

Description

TMSCTRL

Information for a TMS controller message follows.

TLVs

Information about the TMS packet format follows.

Protocol Debugging Example

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


DB-2217


Router# debug tms controller protocol TMS controller protocol debugging is on *Feb 27 10:13:34: TMS_PRO_CN:Registration request recvd consumer 10.1.1.2, group 10 *Feb 27 10:13:34: TMS_PRO_CN:Sending Reg resp to cons=10.1.1.2 group=10 *Feb 27 10:13:34: TMS_PRO_CN:Resync request recvd consumer 10.1.1.2, group 10 *Feb 27 10:13:34: TMS_PRO_CN:Received Resync Req Group=10 *Feb 27 10:13:34: TMS_PRO_CN:Sending Resync resp for cons=10.1.1.2 group=10 ntids=0


debug tms controller protocol Field Descriptions

Field

Description

TMS_PRO_CN

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

XML Debugging Example

The following is sample output from the debug tms controller command entered with the xml keyword: Router# debug tms controller xml TMS controller xml debugs debugging is on *Feb 27 10:13:45: TMS_XML_CN:Found tag threat in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag threat_info in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag primitive in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag parameter in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag tcdf in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag threat in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag threat_info in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag parameter in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag primitive in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag tcdf in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag threat in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag threat_info in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag parameter in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag primitive in threat file *Feb 27 10:13:45: TMS_XML_CN:Found tag tcdf in threat file *Feb 27 10:13:45: TMS_XML_EVE:Decoding threat tag *Feb 27 10:13:45: TMS_XML_EVE:Found threat *Feb 27 10:13:45: TMS_XML_EVE:Decoded threat TLV - threat id : 1, owner id : 1, version : 1 *Feb 27 10:13:45: TMS_XML_EVE:Decoding threat info *Feb 27 10:13:45: TMS_XML_EVE:Found threat info *Feb 27 10:13:45: TMS_XML_EVE:Found ERR *Feb 27 10:13:45: TMS_XML_EVE:name is name, value is tc2 *Feb 27 10:13:45: Decoded Threat desc TLV: *Feb 27 10:13:45: Threat name = NAME: *Feb 27 10:13:45: Threat text = THREATTEXT: *Feb 27 10:13:45: Mitigation text = mitigationtext: *Feb 27 10:13:45: Threat classes : [ tc2 ] *Feb 27 10:13:45: ERR: *Feb 27 10:13:45: ASR = 5, SFR = 20, TFR = 40, ARR = 30 PD = 50 *Feb 27 10:13:45: TMS_XML_EVE:Decoding primtive *Feb 27 10:13:45: TMS_XML_EVE:Found primtive *Feb 27 10:13:45: TMS-XML: Decoded primitive TLV *Feb 27 10:13:45: Prim type = 2 *Feb 27 10:13:45: Primitive = redirect *Feb 27 10:13:45: TMS_XML_EVE:Decoding parameter *Feb 27 10:13:45: TMS_XML_EVE:CNS PARSER : Node is 129 tag = parameter *Feb 27 10:13:45: TMS_XML_EVE:Found parameter


DB-2218

May 2008


*Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb *Feb 1

27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27

10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45: 10:13:45:

TMS_XML_EVE:CNS PARSER : Node is 130 tag = redirect TMS_XML_EVE:parameter : Found redirect TMS_XML_EVE:Found nexthop in redirect TMS_XML:Decoded Parameter TLV Parameter type = 1 Redirect addr = 172.16.1.1 TMS_XML_EVE:Decoding match criteria TMS-XML: Decoded match crt TLV : Src addr : 0.0.0.0 , Src mask : 0.0.0.0 Dest addr : 192.168.8.0 , Dest mask : 255.255.255.0 Protocol : 6 Src port - Start : 0, End : 0 Dest port - Start : 10, End : 2000 TMS_EVE_CN:Threat (1,1,1) allocated. TMS_EVE_CN:Threat (1,1,1) added to LoadDB. TMS_XML_CN:Threat (1,1,1) Loaded into LoadDB TMS_XML_EVE:Decoding threat tag TMS_XML_EVE:Found threat TMS_XML_EVE:Decoded threat TLV - threat id : 2, owner id : 1, version :


Related Commands

debug tms controller xml Field Descriptions

Field

Description

TMS_XML_EVE

Information for XML message event debugging follows.

TMS_XML_CN

Controller information for XML message debugging follows.

TMS-XML

Threat information for XML message debugging follows.

Command

Description

debug tms consumer

Enables the generation of debugging messages on a TMS consumer.


DB-2219

Debug Commands debug token ring

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

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command reports several lines of information for each packet sent or received and is intended for low traffic, detailed debugging. The Token Ring interface records provide information regarding the current state of the ring. These messages are only displayed when the debug token events command is enabled. The debug token ring command invokes verbose Token Ring hardware debugging. This includes detailed displays as traffic arrives and departs the unit.

Caution

Examples

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

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

Interface is alive, phys. addr 5000.1234.5678 in: MAC: acfc: 0x1105 Dst: c000.ffff.ffff Src: 5000.1234.5678 bf: 0x45 in: riflen 0, rd_offset 0, llc_offset 40 out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00 out: LLC: AAAA0300 00009000 00000100 AAC00000 00000802 50001234 ln: 28 in: MAC: acfc: 0x1140 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x09 in: LLC: AAAA0300 00009000 00000100 AAC0B24A 4B4A6768 74732072 ln: 28 in: riflen 0, rd_offset 0, llc_offset 14 out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00 out: LLC: AAAA0300 00009000 00000100 D1D00000 FE11E636 96884006 ln: 28 in: MAC: acfc: 0x1140 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x09 in: LLC: AAAA0300 00009000 00000100 D1D0774C 4DC2078B 3D000160 ln: 28 in: riflen 0, rd_offset 0, llc_offset 14 out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00 out: LLC: AAAA0300 00009000 00000100 F8E00000 FE11E636 96884006 ln: 28

Table 353 describes the significant fields shown in the second line of output.


DB-2220

May 2008

Debug Commands debug token ring

Table 353

debug token ring Field Descriptions

Message

Description

TR0:

Name of the interface associated with the Token Ring event.

in:

Indication of whether the packet was input to the interface (in) or output from the interface (out).

MAC:

Type of packet, as follows: •

MAC—Media Access Control

•

LLC—Link Level Control

acfc: 0x1105

Access Control, Frame Control bytes, as defined by the IEEE 802.5 standard.

Dst: c000.ffff.ffff

Destination address of the frame.

Src: 5000.1234.5678

Source address of the frame.

bf: 0x45

Bridge flags for internal use by technical support staff.

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


Message

Description

TR0:


in:


riflen 0

Length of the routing information field (RIF) in bytes.

rd_offset 0

Offset (in bytes) of the frame pointing to the start of the RIF field.

llc_offset 40

Offset in the frame pointing to the start of the LLC field.

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


Message

Description

TR0:


out:


LLC:

Type of frame, as follows: •

MAC—Media Access Control

•

LLC—Link Level Control

AAAA0300

This and the octets that follow it indicate the contents (hex) of the frame.

ln: 28

The length of the information field (in bytes).


DB-2221

Debug Commands debug topology

debug topology To enable debugging for topology related events, use the debug topology command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug topology {accounting | all | cache | db | event | ha | interface | locking | sb | state | topoid | vrf} no debug topology {accounting | all | cache | db | event | ha | interface | locking | sb | state | topoid | vrf}

Syntax Description

accounting

Enables debugging for topology accounting.

all

Enables debugging for all topology routing events.

cache

Enables debugging for topology ID cache activity.

db

Enables debugging for topology DB events.

event

Enables debugging for topology notification events.

ha

Enables debugging for topology High Availability (HA) events.

interface

Enables debugging for topology interface association.

locking

Enables debugging for topology client locking activity.

sb

Enables debugging for topology sub-block.

state

Enables debugging for topology state change events.

topoid

Enables debugging for topology ID management events.

vrf

Enables debugging for topology VRF association.

Command Default

Debugging output for topology related events is disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(33)SRB


12.2SX


Examples

The following example shows how to enable debugging for topology HA events: Router# debug topology ha


DB-2222

May 2008

Debug Commands debug topology

Related Commands

Command

Description

show topology

Displays status and configuration information for topologies configured with MTR.


DB-2223

Debug Commands debug track

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

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(15)T


12.3(8)T

The output was enhanced to include the track-list objects.

12.2(25)S


12.2(28)SB


12.2(33)SRA


12.2SX


Usage Guidelines

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

Examples

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

26 26 26 26

19:56:23.247:Track:100 Adding interface object 19:56:23.247:Track:Initialise 19:56:23.247:Track:100 New interface Et0/2, ip routing Down 19:56:23.247:Track:Starting process

The following example shows that object number 100 is being tracked and that the state of IP routing on Ethernet interface 0/2 has changed and is back up: Router# debug track Feb 26 19:56:41.247:Track:100 Change #2 interface Et0/2, ip routing Down->Up 00:15:07:%LINK-3-UPDOWN:Interface Ethernet0/2, changed state to up 00:15:08:%LINEPROTO-5-UPDOWN:Line protocol on Interface Ethernet0/2, changed state to up


DB-2224

May 2008

Debug Commands debug track

Related Commands

Command

Description

show track

Displays tracking information.


DB-2225

Debug Commands debug tsp

debug tsp Note

Effective with release 12.3(8)T, the debug tsp command is replaced by the debug voip tsp command. See the debug voip tsp command for more information. To display information about the telephony service provider (TSP), use the debug tsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug tsp {all | call | error | port} no debug tsp {all | call | error | port}

Syntax Description

all

Enables all TSP debugging (except statistics).

call

Enables call debugging.

error

Error debugging.

port

Port debugging.

Defaults

Disabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(6)T


12.3(8)T

This command was replaced by the debug voip tsp command.

12.2SX


Examples

The following shows sample output from the debug tsp all command: Router# debug tsp all 01:04:12:CDAPI TSP RX ===> callId=(32 ), Msg=(CDAPI_MSG_CONNECT_IND,1 ) Sub=(CDAPI_MSG_SUBTYPE_NULL,0 )cdapi_tsp_connect_ind 01:04:12:TSP CDAPI:cdapi_free_msg returns 1 01:04:13:tsp_process_event:[0:D, 0.1 , 3] tsp_cdapi_setup_ack tsp_alert 01:04:13:tsp_process_event:[0:D, 0.1 , 5] tsp_alert_ind 01:04:13:tsp_process_event:[0:D, 0.1 , 10] 01:04:14:tsp_process_event:[0:D, 0.1 , 10] 01:04:17:CDAPI TSP RX ===> callId=(32 ), Msg=(CDAPI_MSG_DISCONNECT_IND,7 ) Sub=(CDAPI_MSG_SUBTYPE_NULL,0 )cdapi_tsp_disc_ind 01:04:17:TSP CDAPI:cdapi_free_msg returns 1 01:04:17:tsp_process_event:[0:D, 0.1 , 27] cdapi_tsp_release_indtsp_disconnet_tdm 01:04:17:tsp_process_event:[0:D, 0.4 , 7] cdapi_tsp_release_comp


DB-2226

May 2008

Debug Commands debug tsp

Related Commands

Command

Description

debug track

Displays information about the telephony service provider.

debug voip rawmsg



DB-2227

Debug Commands debug tunnel rbscp

debug tunnel rbscp To turn on the debugging output for Rate Based Satellite Control Protocol (RBSCP) tunnels, use the debug tunnel rbscp command in privileged EXEC mode. To turn off debugging output, use the no form of this command. debug tunnel rbscp [ack_split | detail | msg | rto | state | window] no debug tunnel rbscp [ack_split | detail | msg | rto | state | window]

Syntax Description

ack_split

(Optional) Displays debugging messages about RBSCP ACK splitting.

detail

(Optional) Displays detailed debugging messages about RBSCP.

msg

(Optional) Displays debugging messages about the RBSCP messages.

rto

(Optional) Displays debugging messages about RBSCP round-trip times (RTTs) and retransmission timeouts (RTOs).

state

(Optional) Displays debugging messages about the RBSCP states.

window

(Optional) Displays debugging messages about RBSCP window stuffing.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(7)T


12.2SX


Usage Guidelines

Caution

Examples

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

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

The following example turns on debugging messages about RBSCP messages: Router# debug tunnel rbscp msg Tunnel RBSCP message debugging is on router# *Mar 1 05:36:01.435: handling FWD_TSN: sequence=20h, tsn=0h *Mar 1 05:36:03.371: rbscp_output_a_fwdtsn: tsn=0h, seq=Dh, for_hb=1 *Mar 1 05:36:10.835: handling FWD_TSN: sequence=21h, tsn=0h *Mar 1 05:36:12.771: rbscp_output_a_fwdtsn: tsn=0h, seq=Eh, for_hb=1 *Mar 1 05:36:20.235: handling FWD_TSN: sequence=22h, tsn=0h *Mar 1 05:36:22.171: rbscp_output_a_fwdtsn: tsn=0h, seq=Fh, for_hb=1


DB-2228

May 2008

Debug Commands debug tunnel rbscp

Note

The debug output will vary depending on what the router is configured to do after the debug command is entered. Table 356 describes the significant fields shown in the display. Table 356

debug tunnel rbscp msg Field Descriptions

Field

Description

handling FWD_TSN

The router has received and is processing a FWD_TSN message from a peer with a sequence number of 20 hex and a Transport Sequence Number (TSN) of 0 hex.

rbscp_output_a_fwdtsn

The router is sending a FWD_TSN message to the peer with a TSN of 0 hex, a sequence number of 0D hex and it is for a heartbeat (equivalent of a keepalive).

The following example turns on debugging messages about RBSCP round-trip times and retransmission timeouts: Router# debug tunnel rbscp rto Tunnel RBSCP RTT/RTO debugging is on router# *Mar 1 05:36:50.927: update_rtt: cur_rtt:549 ms:548 delay:0 *Mar 1 05:36:50.927: New RTT est:549 RTO:703 *Mar 1 05:37:00.327: update_rtt: cur_rtt:549 ms:548 delay:0 *Mar 1 05:37:00.327: New RTT est:549 RTO:703 *Mar 1 05:37:09.727: update_rtt: cur_rtt:549 ms:548 delay:0 *Mar 1 05:37:09.727: New RTT est:549 RTO:703


Related Commands

debug tunnel rbscp rto Field Descriptions

Field

Description

update rtt: curr rtt

Displays the updated, previous, and current RTT, in milliseconds, and a number that represents the amount of additional delay from queuing.

New RTT est

Displays the estimated new RTT, in milliseconds.

RTO

Displays the new retransmission timeout, in milliseconds.

Command

Description

show rbscp

Displays state and statistical information about RBSCP tunnels.


DB-2229

Debug Commands debug tunnel route-via

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

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(11)T


12.2SX


Examples

The following sample output of debug tunnel route-via command displays the outgoing interface for the tunnel transport. Router# debug tunnel route-via Tunnel route-via debugging is on *May 22 11:54:34.803: TUN-VIA: Tunnel0 candidate route-via Ethernet0/0, next hop 10.73.2.1 *May 22 11:54:34.803: TUN-VIA: Tunnel0 route-via action is forward Router# no debug tunnel route-via undebug tunnel route-via Tunnel route-via debugging is off

Related Commands

Command

Description

show interface tunnel

Displays information about the physical output tunnel interface.

tunnel route-via

Specifies the outgoing interface of the tunnel transport.


DB-2230

May 2008

Debug Commands debug txconn all

debug txconn all To turn on all debug flags for Cisco Transaction Connection (CTRC) communications with the Customer Information Control System (CICS), use the debug txconn all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug txconn all no debug txconn all

Syntax Description


Defaults

Debugging is not enabled for the txconn subsystem.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)XN


12.2(33)SRA


12.2SX


Examples

The following example shows the immediate output of the debug txconn all command. For examples of specific debugging messages, see the examples provided for the debug txconn appc, debug txconn config, debug txconn data, debug txconn event, debug txconn tcp, and debug txconn timer commands. Router# debug txconn all All possible TXConn debugging has been turned on

Related Commands

Command

Description

debug snasw

Displays debugging information related to SNA Switching Services.

debug txconn appc

Displays APPC-related trace or error messages for communications with CICS.

debug txconn config

Displays trace or error messages for CTRC configuration and control blocks for CICS communications.

debug txconn data

Displays CICS client and host data being handled by CTRC, in hexadecimal notation.

debug txconn event

Displays trace or error messages for CTRC events related to CICS communications.


DB-2231

Debug Commands debug txconn all

debug txconn tcp

Displays error messages or traces for TCP/IP communications with CICS.

debug txconn timer

Displays performance information related to CICS communications.

show debugging



DB-2232

May 2008

Debug Commands debug txconn appc

debug txconn appc To display Advanced Program-to-Program Communication (APPC)-related trace or error messages for communications with the Customer Information Control System (CICS), use the debug txconn appc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug txconn appc no debug txconn appc

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)XN


12.2(33)SRA


12.2SX


Examples

The following shows sample APPC debugging output from the debug txconn appc command: Router# debug txconn appc 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05: 01:18:05:

TXCONN-APPC-622ADF38: Verb block = TXCONN-APPC-622ADF38: 0001 0200 0300 0000 0400 0000 0000 0000 TXCONN-APPC-622ADF38: 0000 00FC 0000 0000 0000 0000 0000 0000 TXCONN-APPC-622ADF38: 0000 0000 0840 0007 0000 0000 0000 0000 TXCONN-APPC-622ADF38: 7BC9 D5E3 C5D9 4040 07F6 C4C2 4040 4040 TXCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 4040 TXCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 4040 TXCONN-APPC-622ADF38: 4040 4040 4040 4040 4040 4040 4040 4040 TXCONN-APPC-622ADF38: 4040 4040 4040 4040 0000 0000 0000 0000 TXCONN-APPC-622ADF38: 0000 0000 0000 0000 0000 0000 0000 0000 TXCONN-APPC-622ADF38: 0000 0000 0000 0000 0000 0000 0000 0000 TXCONN-APPC-622ADF38: 00E2 E3C1 D9E6 4BC7 C1E9 C5D3 D3C5 4040 TXCONN-APPC-622ADF38: 4040 0000 0000 0000 0000 0000 TXCONN-APPC-621E5730: Verb block = TXCONN-APPC-621E5730: 0001 0200 0300 0000 0400 0000 0000 0000 TXCONN-APPC-621E5730: 0000 00FD 0000 0000 0000 0000 0000 0000 TXCONN-APPC-621E5730: 0000 0000 0840 0007 0000 0000 0000 0000 TXCONN-APPC-621E5730: C9C2 D4D9 C4C2 4040 07F6 C4C2 4040 4040 TXCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 4040 TXCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 4040 TXCONN-APPC-621E5730: 4040 4040 4040 4040 4040 4040 4040 4040 TXCONN-APPC-621E5730: 4040 4040 4040 4040 0000 0000 0000 0000


DB-2233

Debug Commands debug txconn appc

01:18:05: 01:18:05: 01:18:05: 01:18:05:

Related Commands

TXCONN-APPC-621E5730: TXCONN-APPC-621E5730: TXCONN-APPC-621E5730: TXCONN-APPC-621E5730:

0000 0000 00E2 4040

0000 0000 E3C1 0000

0000 0000 D9E6 0000

0000 0000 4BE2 0000

0000 0000 E3C5 0000

0000 0000 0000 0000 0000 0000 D3D3 C140 4040 0000

Command

Description

debug snasw


debug txconn all

Displays all CTRC debugging information related to communications with CICS.

debug txconn config

Displays trace or error messages for CTRC configuration and control blocks for CICS communications.

debug txconn data


debug txconn event


debug txconn tcp


debug txconn timer


show debugging



DB-2234

May 2008

Debug Commands debug txconn config

debug txconn config To display trace or error messages for Cisco Transaction Connection (CTRC) configuration and control blocks for Customer Information Control System (CICS) communications, use the debug txconn config command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug txconn config no debug txconn config

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)XN


12.2(33)SRA


12.2SX


Examples

The following shows sample output from the debug txconn config command: Router# debug txconn config 22:11:37: 22:11:37: 22:11:37: 22:11:44: 22:11:44: 22:11:44: 22:11:48: 22:11:53: 22:11:54:

TXCONN-CONFIG: TXCONN-CONFIG: TXCONN-CONFIG: TXCONN-CONFIG: TXCONN-CONFIG: TXCONN-CONFIG: TXCONN-CONFIG: TXCONN-CONFIG: TXCONN-CONFIG:

deleting transaction 61FCE414 deleting connection 61FB5CB0 server 62105D6C releases connection 61FB5CB0 new connection 61FB64A0 server 6210CEB4 takes connection 61FB64A0 new transaction 61E44B9C deleting transaction 61E44B9C new transaction 61E44B9C deleting transaction 61E44B9C


DB-2235

Debug Commands debug txconn config

Related Commands

Command

Description

debug snasw


debug txconn all

Displays all CTRC debugging information related to communications with CICS.

debug txconn appc

Displays APPC-related trace or error messages for communications with CICS.

debug txconn data


debug txconn event


debug txconn tcp


debug txconn timer


show debugging



DB-2236

May 2008

Debug Commands debug txconn data

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

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)XN


12.2(33)SRA


12.2SX


Examples

The following shows selected output from the debug txconn data command when a connection is established, data is received from the client via TCP/IP, data is sent to the client, and then the connection is closed. Router# debug txconn data TXConn DATA debugging is on 00:04:50: 00:04:50: 00:04:50: 00:04:50: 00:06:27: 00:06:53:

TXConn(62197464) TXConn(62197464) TXConn(62197464) TXConn(62197464) TXConn(62197464) TXConn(62175024)

Created State(0) MsgID(0) -> nextState(1) Client->0000 003A 0000 0002 000B 90A0 Received LL 58 for session(0 0 2). Client nextState(1) TXTrans(id:62197910 conn:62197464 addr:2) conversationType(mapped) syncLevel(1) TXTrans(id:62197910 conn:62197464 addr:2) TPName CCIN TXTrans(id:62197910 conn:62197464 addr:2) apDataLength(32) GDSID(12FF)


DB-2237

Debug Commands debug txconn data

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

The following lines show output when data is received from the host: 00:05:01: TXTrans(id:62197910 conn:62197464 addr:2) Class-driver activated *Dec 22 06:18:38.683:Host: 1 *Dec 22 06:18:38.683:Address: 19 *Dec 22 06:18:38.683:Manufacturer: AKS *Dec 22 06:18:38.683:Product: eToken Pro 4254 *Dec 22 06:18:38.683:Serial Number: *Dec 22 06:18:39.383:Control Transfer Device Handle:0x3010000 Direction:0x0 Request:0x1 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0 *Dec 22 06:18:39.383:Control Transfer Device Handle:0x3010000 Direction:0x80 Request:0x81 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0 *Dec 22 06:18:39.407:Control Transfer Device Handle:0x3010000 Direction:0x0 Request:0x3 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0 *Dec 22 06:18:39.407:Control Transfer Device Handle:0x3010000 Direction:0x80 Request:0 my3825#x83 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0


DB-2247

Debug Commands debug usb driver

*Dec 22 06:18:39.503:Control Transfer Device Handle:0x3010000 Direction:0x0 Request:0x2 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0 *Dec 22 06:18:39.507:Control Transfer Device Handle:0x3010000 Direction:0x80 Request:0x82 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0 *Dec 22 06:18:39.507:%USB_TOKEN_FILESYS-6-USB_TOKEN_INSERTED:USB Token device inserted:usbtoken1. *Dec 22 06:18:39.515:Control Transfer Device Handle:0x3010000 Direction:0x0 Request:0x6 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0 *Dec 22 06:18:39.515:%USB_TOKEN_FILESYS-6-REGISTERING_WITH_IFS:Registering USB Token File System usbtoken1:might take a while... *Dec 22 06:18:39.515:Control Transfer Device Handle:0x3010000 Direction:0x80 Request:0x86 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0 *Dec 22 06:18:39.543:Control Transfer Device Handle:0x3010000 Direction:0x0 Request:0x6 Type:0x40 Recipient:0x0 ValueDesc:0x0 ValueIndex:0x0 Index:0x0 . . .


DB-2248

May 2008

Debug Commands debug v120 event

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

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

V.120 is an ITU specification that allows for reliable transport of synchronous, asynchronous, or bit transparent data over ISDN bearer channels. For complete information on the V.120 process, use the debug v120 packet command along with the debug v120 event command. V.120 events are activity events rather than error conditions.

Examples

The following is sample output from the debug v120 event command of V.120 starting up and stopping. Also included is the interface that V.120 is running on (BR 0) and where the V.120 configuration parameters are obtained from (default). Router# debug v120 event 0:01:47: BR0:1-v120 started - Setting default V.120 parameters 0:02:00: BR0:1:removing v120

Related Commands

Command

Description

debug v120 packet

Displays general information on all incoming and outgoing V.120 packets.


DB-2249

Debug Commands debug v120 packet

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

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug v120 packet command shows every packet on the V.120 session. You can use this information to determine whether incompatibilities exist between Cisco’s V.120 implementation and other vendors’ V.120 implementations. V.120 is an ITU specification that allows for reliable transport of synchronous, asynchronous, or bit transparent data over ISDN bearer channels. For complete information on the V.120 process, use the debug v120 events command along with the debug v120 packet command.

Examples

The following is sample output from the debug v120 packet command for a typical session startup: Router# debug v120 packet 0:03:27: BR0:1: I SABME:lli 256 C/R 0 P/F=1 0:03:27: BR0:1: O UA:lli 256 C/R 1 P/F=1 0:03:27: BR0:1: O IFRAME:lli 256 C/R 0 N(R)=0 N(S)=0 P/F=0 len 43 0x83 0xD 0xA 0xD 0xA 0x55 0x73 0x65 0x72 0x20 0x41 0x63 0x63 0x65 0x73 0x73 0:03:27: BR0:1: I RR:lli 256 C/R 1 N(R)=1 P/F=0 0:03:28: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=0 P/F=0 len 2 0x83 0x63 0:03:28: BR0:1: O RR:lli 256 C/R 1 N(R)=1 P/F=0 0:03:29: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=1 P/F=0 len 2 0x83 0x31 0:03:29: BR0:1: O RR:lli 256 C/R 1 N(R)=2 P/F=0 %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to up 0:03:31: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=2 P/F=0 len 2 0x83 0x55 0:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=3 P/F=0 len 3 0x83 0x31 0x6F 0:03:32: BR0:1: O RR:lli 256 C/R 1 N(R)=3 P/F=0 0:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=4 P/F=0 len 2 0x83 0x73 0:03:32: BR0:1: O RR:lli 256 C/R 1 N(R)=5 P/F=0 0:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=5 P/F=0 len 2 0x83 0xA 0:03:32: BR0:1: O IFRAME:lli 256 C/R 0 N(R)=6 N(S)=1 P/F=0 len 9 0x83 0xD 0xA 0x68 0x65 0x66 0x65 0x72 0x3E


DB-2250

May 2008

Debug Commands debug v120 packet

Table 358 describes the significant fields in the display. Table 358

Related Commands

debug v120 packet Field Descriptions

Field

Descriptions

BR0:1

Interface number associated with this debugging information.

I/O

Packet going into or out of the interface.

SABME, UA, IFRAME, RR

V120 packet type: •

SABME—Set asynchronous balanced mode, extended

•

US—Unnumbered acknowledgment

•

IFRAME—Information frame

•

RR—Receive ready

lli 256

Logical link identifier number.

C/R 0

Command or response.

P/F=1

Poll final.

N(R)=0

Number received.

N(S)=0

Number sent.

len 43

Number of data bytes in the packet.

0x83

Up to 16 bytes of data.

Command

Description

debug tarp events

Displays information on TARP activity.


DB-2251

Debug Commands debug vg-anylan

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

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

This command could create a substantial amount of command output.

Examples

The following is sample output from the debug vg-anylan command: Router# debug vg-anylan %HP100VG-5-LOSTCARR: HP100VG(2/0), lost carrier

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

debug vg-anylan Message Descriptions

Message

Description

Action

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

Lost carrier debug message. The VG controller detects that the link to the hub is down due to cable, hub, or VG controller problem.

Check, repair, or replace the cable or hub. If you determine that the cable and hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.

%HP100VG-5-CABLEE Bad cable error messages. RR: HP100VG(2/0), cable Cable did not pass training.1 error, training failed

%HP100VG-5-NOCABL E: HP100VG(2/0), no tone detected, check cable, hub

Check, repair, or replace the cable or hub. If you determine that the cable and hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.

No cable attached error Check, repair, or replace the cable or message. The VG MAC cannot hub. If you determine that the cable and hear tones from the hub.1 hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.


DB-2252

May 2008

Debug Commands debug vg-anylan

Table 359

debug vg-anylan Message Descriptions (continued)

Message

Description

Action

HP100VG-1-FAIL: HP100VG(2/0), Training Fail - unable to login to the hub

Training to the VG network failed. Login to the hub rejected by the hub.1

Take action based on the following error messages:

%HP100VG-1-DUPMAC : HP100VG(2/0), A duplicate MAC address has been detected

•

%HP100VG-1-DUPMAC: HP100VG(2/0), A duplicate MAC address has been detected.

•

HP100VG-1-LANCNF: HP100VG(2/0), Configuration is not compatible with the network.

•

%HP100VG-1-ACCESS: HP100VG(2/0), Access to network is not allowed.

Duplicate MAC address on the Check the router configuration to make sure that no duplicate MAC address is same VG network. Two VG configured. devices on the same LAN segment have the same MAC address.

%HP100VG-1-LANCNF: Configuration of the router is not compatible to the network. HP100VG(2/0), Configuration is not compatible with the network

Check that the configuration of the hub for Frame Format, Promiscuous, and Repeater bit indicates the proper configuration.

%HP100VG-1-ACCESS: Access to the VG network is HP100VG(2/0), Access to denied by the hub. network is not allowed

Check the configuration of the hub.

%HP100VG-3-NOTHP10 Could not find the 100VG PCI Make sure the 100VG-AnyLAN port 0VG: Device reported device on a 100VG-AnyLAN adapter is properly seated in the slot. port adapter. Otherwise repair or replace the 0x5101A 100VG-AnyLAN port adapter. %HP100VG-1-DISCOVE No 100VG interface detected R: Only found 0 interfaces on a 100VG-AnyLAN port adapter in a slot. on bay 2, shutting down bay

Make sure the 100VG-AnyLAN port adapter is properly seated in the slot. Otherwise repair or replace the 100VG-AnyLAN port adapter.

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


DB-2253

Debug Commands debug video vicm

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

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)XK


12.0(6)T


12.2SX


Examples

The following shows sample output when you use the debug video vicm command. Comments are enclosed in asterisks (*). Router# debug video vicm Video ViCM FSM debugging is on ***** Starting Video call ***** Router# SVC HANDLE in rcvd:0x80001B: 00:42:55:ViCM - current state = Idle, Codec Ready 00:42:55:ViCM - current event = SVC Setup 00:42:55:ViCM - new state = Call Connected 00:42:55:ViCM - current state = Call Connected 00:42:55:ViCM - current event = SVC Connect Ack 00:42:55:ViCM - new state = Call Connected *****Video Call Disconnecting***** Router# 00:43:54:ViCM - current state = Call Connected 00:43:54:ViCM - current event = SVC Release 00:43:54:ViCM - new state = Remote Hangup


DB-2254

May 2008

Debug Commands debug video vicm

00:43:54:ViCM - current state = Remote Hangup 00:43:54:ViCM - current event = SVC Release Complete 00:43:54:ViCM - new state = Remote Hangup mc3810_video_lw_periodic:Codec is not ready mc3810_video_lw_periodic:sending message 00:43:55:ViCM - current state = Remote Hangup 00:43:55:ViCM - current event = DTR Deasserted 00:43:55:ViCM - new state = Idle mc3810_video_lw_periodic:Codec is ready mc3810_video_lw_periodic:sending message 00:43:55:ViCM - current state = Idle 00:43:55:ViCM - current event = DTR Asserted 00:43:55:ViCM - new state = Idle, Codec Ready


DB-2255

Debug Commands debug vlan packet

debug vlan packet To display general information on virtual LAN (VLAN) packets that the router received but is not configured to support, use the debug vlan packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vlan packet no debug vlan packet

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug vlan packet command displays only packets with a VLAN identifier that the router is not configured to support. This command allows you to identify other VLAN traffic on the network. Virtual LAN packets that the router is configured to route or switch are counted and indicated when you use the show vlans command.

Examples

The following is sample output from the debug vlan packet output. In this example, a VLAN packet with a VLAN ID of 1000 was received on FDDI interface 0 and this interface was not configured to route or switch this VLAN packet: Router# debug vlan packet vLAN: IEEE 802.10 packet bearing vLAN ID 1000 received on interface Fddi0 which is not configured to route/switch ID 1000.


DB-2256

May 2008

Debug Commands debug vmi

debug vmi To display debugging output for virtual multipoint interfaces (VMIs), use the debug vmi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vmi {error | multicast | neighbor | packet | pppoe} no debug vmi {error | multicast | neighbor | packet | pppoe}

Syntax Description

error

Displays errors received on the interface.

multicast

Displays information about multicast packets going in or out on the interface.

neighbor

Displays information about neighbor relationships causing the VMI interface to go up or down.

packet

Displays information about packets going in or out on the VMI interface.

pppoe

Displays information about the flows between PPPoE and the VMI interface that trigger the creation of a neighbor relationship.

Defaults

Debugging is disabled by default.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(15)XF

This command was introduced to support Mobile Adhoc Networking.

12.4(15)T


12.2SX


Examples

Debug Output with VMI Interface Working Propoerly

The following is sample output from the debug vmi command when the VMI interface is working correctly: Router# debug vmi neighbor Jan 6 07:01:54.601: Jan 6 07:01:54.605: Jan 6 07:01:54.605: Jan 6 07:01:54.605: Jan 6 07:01:54.605: Jan 6 07:01:54.605: nbr->IPv4linkPtr = 0 Jan 6 07:01:54.605: Jan 6 07:01:54.605:

%LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up vmi_create_neighbor: event=VMI_PPPOE_IPV4_UP, addr=10.3.3.2 vmi_create_neighbor: V4-- nbr=0, key=::4.3.3.2 vmi_create_neighbor: V6-- nbr=0, key=:: vmi_create_neighbor: VMI_PPPOE_IPV4_UP -- neighbor addr=0 vmi_nbr_add: Begin. nbr=8381D104 nbr->IPv6linkPtr = 0, VMI: Begin dump of Neighbor RBTree VMI: vmiLink_t(838368E0),key=::10.3.3.2,V4


DB-2257


Jan 6 07:01:54.605: Jan 6 07:01:54.605: Jan 6 07:01:54.605: Jan 6 07:01:54.605: Jan 6 07:01:54.609: Jan 6 07:01:54.609: to up Jan 6 07:01:54.609: Jan 6 07:01:54.609: Jan 6 07:01:54.609: Jan 6 07:01:54.617: adjacency Jan 6 07:01:55.601: changed state to up

VMI: nbr addresses: :: 10.3.3.2 mtu=1484,insertAttempts=0 0,neighbor_up_deferred=FALSE VMI: NO L2 STRUCT FOUND VMI: End dump of Neighbor RBTree vmi1 new nbr ::/10.3.3.2 %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state vmi_create_route_tbl_entry: Interface up on vmi1 vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.2 vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.2 %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.2 (vmi1) is up: new %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2,

Debug Output for Periodic Status Update

The following is sample output from the debug vmi command for a periodic status update: Router# debug vmi neighbor Jan Jan Jan Jan

6 6 6 6

07:02:24.609: vmi_nbr_calculate_load: load=0, nbr ::/10.3.3.2 07:02:24.609: cur_tx_bytes = 776, old_tx_bytes = 0, tx_delta = 776 07:02:24.609: msec_clock_diff = 30004, clock_diff = 30, rate = 102400000 07:02:24.609: max_traffic = 2207566340

Debug Output Showing Loss of a Neighbor Node

The following is sample output from the debug vmi command when the loss of a neighbor is reported: Router# debug vmi neighbor Jan 6 07:02:33.781: vmi_destroy_neighbor: Delete route 10.3.3.2 returned RC_IPROUTEDEL_DB Jan 6 07:02:33.781: vmi_destroy_neighbor: VMI_IPV4 nbr=8381D104 Jan 6 07:02:33.781: vmi_nbr_delete: deleting V4 linkPtr=838368E0, nbr=8381D104 Jan 6 07:02:33.781: vmiFreeNeighbor: Freeing nbr=8381D104 Jan 6 07:02:33.781: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state to down Jan 6 07:02:33.781: vmi_hwif_goingdown: called for vmi1 Jan 6 07:02:33.781: vmi_hwif_goingdown: No corresponding VMI interface found for vmi1 Jan 6 07:02:33.785: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.2 (vmi1) is down: igrp2 peer state - DOWN Jan 6 07:02:33.793: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down Jan 6 07:02:34.793: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down Jan 6 07:02:35.785: %LINK-5-CHANGED: Interface vmi1, changed state to administratively down

The following example shows the status of a VMI peer relationship: Router# debug vmi neighbor Jan 6 07:03:37.737: Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.769: nbr->IPv4linkPtr = 0 Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.769:

%LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up vmi_create_neighbor: event=VMI_PPPOE_IPV4_UP, addr=10.3.3.1 vmi_create_neighbor: V4-- nbr=0, key=::10.3.3.1 vmi_create_neighbor: V6-- nbr=0, key=:: vmi_create_neighbor: VMI_PPPOE_IPV4_UP -- neighbor addr=0 vmi_nbr_add: Begin. nbr=7004A304 nbr->IPv6linkPtr = 0, VMI: Begin dump of Neighbor RBTree VMI: vmiLink_t(70EF96A8),key=::10.3.3.1,V4 VMI: nbr addresses: :: 10.3.3.1 mtu=1484,insertAttempts=0 0,neighbor_up_deferred=FALSE


DB-2258

May 2008


Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.769: to up Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.769: Jan 6 07:03:37.781: adjacency Jan 6 07:03:38.737: changed state to up Jan 6 07:04:07.769: Jan 6 07:04:07.769: Jan 6 07:04:07.769: Jan 6 07:04:07.769:

VMI: NO L2 STRUCT FOUND VMI: End dump of Neighbor RBTree vmi1 new nbr ::/10.3.3.1 %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state vmi_create_route_tbl_entry: Interface up on vmi1 vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.1 vmi_send_neighbor_up_indicators: MANET_LINK_UP on 10.3.3.1 %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.1 (vmi1) is up: new %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, vmi_nbr_calculate_load: load=0, nbr ::/10.3.3.1 cur_tx_bytes = 640, old_tx_bytes = 0, tx_delta = 640 msec_clock_diff = 30000, clock_diff = 30, rate = 102400000 max_traffic = 57600

Jan 6 07:04:16.953: vmi_destroy_neighbor: Delete route 10.3.3.1 returned RC_IPROUTEDEL_DB Jan 6 07:04:16.953: vmi_destroy_neighbor: VMI_IPV4 nbr=7004A304 Jan 6 07:04:16.953: vmi_nbr_delete: deleting V4 linkPtr=70EF96A8, nbr=7004A304 Jan 6 07:04:16.953: vmiFreeNeighbor: Freeing nbr=7004A304 Jan 6 07:04:16.953: %LINEPROTO-5-UPDOWN: Line protocol on Interface vmi1, changed state to down Jan 6 07:04:16.957: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.3.3.1 (vmi1) is down: igrp2 peer state - DOWN Jan 6 07:04:16.961: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down Jan 6 07:04:17.953: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

Related Commands

Command

Description

eigrp interface

Sets a threshold value to minimize hysteresis in a router-to-radio configuration.

interface vmi

Creates a virtual multipoint interface (VMI) that can be configured and applied dynamically.

mode bypass

Enables Virtual Multipoint Interfaces (VMI) to support multicast traffic

physical interface

Creates a physical subinterface to be associated with the Virtual Multipoint Interfaces (VMI) on a router


DB-2259

Debug Commands debug voice aaa asnl

debug voice aaa asnl To display debugging messages for gateway authentication, authorization, and accounting (AAA) Application Subscribe/Notify Layer (ASNL), use the debug voice aaa asnl command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice aaa asnl no debug voice aaa asnl

Syntax Description


Defaults

Debugging of AAA ASNL is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Usage Guidelines

The debug voice aaa asnl command is a subset of the debug voice aaa command. It displays only events and error information related to the Accounting Server Connectivity Failure and Recovery Detection feature.

Examples

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


DB-2260

May 2008

Debug Commands debug voice aaa asnl


debug voice aaa asnl Field Descriptions

Field

Description

acct_rec_type

Accounting record type: START (1), UPDATE (2), STOP (3), ACCT_ON (4).

Accounting Probe UID

ID of the accounting probe record.

Method List Name

Method list name.


DB-2261

Debug Commands debug voice all

debug voice all To display debugging information for all components of the Voice Call Manager, use the debug voice all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice all [slot/port] no debug voice all [slot/port]

Syntax Description

slot/port

Command Modes

Privileged EXEC

Usage Guidelines

This command is valid on the Cisco MC3810 only.

Examples

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

Related Commands

Command

Description

debug voice eecm

Displays debugging information for the Voice End-to-End Call Manager.

debug voice protocol

Displays debugging information for the Voice Line Protocol State machine.

debug voice signaling

Displays debugging information for the voice port signaling.

debug voice tdsm

Displays debugging information for the voice tandem switch.

debug voice ccapi

Debugs the call control API.

(Optional) The slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed. If the slot and port are not entered, debugging information for all voice ports is displayed.


DB-2262

May 2008

Debug Commands debug voice cp

debug voice cp To display debugging information for the Voice Call Processing State Machine, use the debug voice cp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice cp [slot/port] no debug voice cp [slot/port]

Syntax Description

slot/port

Command Modes

Privileged EXEC

Usage Guidelines


Examples

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

(Optional) The slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.

Router# debug voice cp 1/1 Voice Call Processing State Machine debugging is on 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1:

CPD( ), idle gets event seize_ind CPD( ), idle gets event dsp_ready CPD( ), idle ==> collect CPD(in), collect gets event digit CPD(in), collect gets event digit CPD(in), collect gets event digit CPD(in), collect gets event digit CPD(in), collect gets event addr_done CPD(in), collect ==> request CPD(in), request gets event call_proceeding CPD(in), request ==> in_wait_answer CPD(in), in_wait_answer gets event call_accept CPD(in), in_wait_answer gets event call_answered CPD(in), in_wait_answer ==> connected CPD(in), connected gets event peer_onhook CPD(in), connected ==> disconnect_wait CPD(in), disconnect_wait gets event idle_ind CPD(in), disconnect_wait ==> idle


DB-2263

Debug Commands debug voice cp

Related Commands

Command

Description

debug voice all

Displays debugging information for all components of the Voice Call Manager.

debug voice eecm



Displays debugging information for the Voice Line protocol State machine.



debug voice tdsm



DB-2264

May 2008

Debug Commands debug voice dsp crash-dump

debug voice dsp crash-dump To display debugging information for the crash dump feature, use the debug voice dsp crash-dump command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice dsp crash-dump [details | keepalives] no debug voice dsp crash-dump [details | keepalives]

Syntax Description

details

(Optional) Displays debugging information for the crash dump feature details. There is no debug output until there is one DSP crash. When the crash dump feature is turned on, the detailed debug messages are displayed.

keepalives

(Optional) Displays debugging information for the crash dump feature keepalives. Confirms that a crash dump file has been written to the specified destination.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Usage Guidelines

Caution

DSP resource management (DSPRM) sends a debug message to the console that confirms that a crash dump file has been written to the specified destination.

Enabling this debug feature adds extra time for the DSP to recover. The keepalive and detail keywords produce large volumes of output and should not be used except under the direction of a Cisco engineer. You can also use the undebug all command to disable debugging output.

Examples

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

8 03:42:19.505:Got back DSP status 0x12 0x0 for dsp 9 slot 1 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 10 slot 1 8 03:42:19.509:Got back DSP status 0x12 0x0 for dsp 11 slot 1


DB-2265

Debug Commands debug voice dsp crash-dump

*Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar *Mar

8 8 8 8 8 8 8 8 8

03:42:19.509:Got back DSP status 0x12 03:42:19.509:Got back DSP status 0x12 03:42:19.509:Got back DSP status 0x12 03:42:21.509:status cleared done, dsp 03:42:21.513:status cleared done, dsp 03:42:21.513:status cleared done, dsp 03:42:21.513:status cleared done, dsp 03:42:21.513:status cleared done, dsp 03:42:21.513:status cleared done, dsp

0x0 for dsp 12 slot 1 0x0 for dsp 13 slot 1 0x0 for dsp 14 slot 1 9 slot 1 10 slot 1 11 slot 1 12 slot 1 13 slot 1 14 slot 1

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

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

Related Commands

Command

Description

show voice dsp crash-dump

Displays voice dsp crash dump information.

voice dsp crash-dump

Enables the crash dump feature and specifies the destination file and the file limit.


DB-2266

May 2008

Debug Commands debug voice eecm

debug voice eecm To display debugging information for the Voice End-to-End Call Manager, use the debug voice eecm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice eecm [slot/port] no debug voice eecm [slot/port]

Syntax Description

slot/port

Command Modes

Privileged EXEC

Usage Guidelines


Examples

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

(Optional) Slot and port number of the voice port. If the slot and port arguments are entered, only debugging information for that voice port is displayed.

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

Related Commands

3 7 0 2

Command

Description

debug voice all






debug voice tdsm


debug voice ccapi



DB-2267

Debug Commands debug voice enum

debug voice enum To view voice telephone number mapping (ENUM) information, use the debug voice enum command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice enum {detail | summary} no debug voice enum {detail | summary}

Syntax Description

detail

Displays detailed output.

summary

Displays summary output.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Usage Guidelines

Disable console logging and use buffered logging before using the debug voice enum command. Using the debug voice enum command generates a large volume of debugs, which can affect router performance.

Examples

The following is sample output from the debug voice enum detail command. The output shows the match number as 5108891234, ENUM table as 10. Rule 1 in table 10 matched the pattern and after applying the replacement rule, the resulting string is 5108891234. The ENUM query is sent out for the domain 4.3.2.1.9.8.8.0.1.5.e164.cisco.com. The output then shows the matching Naming Authority Pointer (NAPTR) records obtained in the response. The records are then processed and the final URLs (contact lists) are shown toward the end. Router# debug voice enum detail enum_resolve_domain:match_num 5108891234 table_indx 10 enum_resolve_domain:rule 1 result string 5108891234 generate_enum_search_string :search string 4.3.2.1.9.8.8.0.1.5.e164.cisco.com enum_dns_query:name = 4.3.2.1.9.8.8.0.1.5.e164.cisco.com type = 35, ns_server = 0 order 100 pref 10 service sip+E2U flag U regexp /^.*$/sip:[email protected]/ replacement order 200 pref 10 service h323+E2U flag U regexp /^.*$/h323:[email protected]/ replacement num_elem = 2 NAPTR Record :order 100 pref 10 service sip+E2U


DB-2268

May 2008


flags U regexp /^.*$/sip:[email protected]/ replacement NAPTR Record :order 200 pref 10 service h323+E2U flags U regexp /^.*$/h323:[email protected]/ replacement decode_naptr_record :re_string ^.*$ decode_naptr_record :re_substitution_string sip:[email protected] decode_naptr_record :re_flags_string U_FLAG case, stopping query new_e164_user sip:[email protected] decode_naptr_record :re_string ^.*$ decode_naptr_re tahoe13#cord :re_substitution_string h323:[email protected] decode_naptr_record :re_flags_string U_FLAG case, stopping query new_e164_user h323:[email protected] contact_list : sip:[email protected] contact_list : h323:[email protected] enum_resolve_domain:contact_list 64558450

A sample output of the debug voice enum summary command is shown below. The output shows the matching number, the ENUM table used and the rule in the table that matched the number along with the resulting string. Note that this output is a subset of the output from debug voice enum detail command. Router# debug voice enum summary enum_resolve_domain:match_num 5108891234 table_indx 10 enum_resolve_domain:rule 1 result string 5108891234

Table 361 provides an alphabetical listing of the debug voice enum command fields and a description of each field. Table 361

debug voice enum Field Descriptions

Field

Description

contact_list

Final list of URLs that the gateway will try to contact as an attempt to place the call.

flag

Flag value of a NAPTR record as defined in RFC 2915.

match_num

Number to be used for matching against the ENUM match table.

name

Fully qualified domain name sent out to DNS server.

ns_server

Address of the DNS server. If 0, the Domain Name System (DNS) server configured on the gateway is used.

num_elem

Number of records received in the response.

order

Order in the record, as defined in RFC 2915.

pref

Preference of the record, as defined in RFC 2915.

regexp

Regular expression of the record, as defined in RFC 2915.

replacement

Replacement string of the record, as defined in RFC 2915.


DB-2269


Table 361

debug voice enum Field Descriptions (continued)

Field

Description

re_flags_string

Flag indicating whether matching and replacement should be case sensitive: •

i = Case insensitive

•

otherwise = Case sensitive

re_string

The first part of the regexp, delimited by "/". This is used to match the incoming string. Refer to RFC 2915.

re_substitution_string

The second part of regexp, delimited by "/".

result string

String that results when match_num is taken through the ENUM match table for a match. This string will be used to form a fully qualified domain name (FQDN).

rule

Rule number that matched match_num in the enum match table.

search string

String sent out to the DNS server.

service

Service field of the NAPTR record. Refer to RFC 2915.

table_indx

Index of the ENUM match table picked for this call.

type

Type of record requested in the query: 35 = NAPTR 33 = DNS Service (SRV)

Related Commands

Command

Description

rule (ENUM configuration)

Defines the rule pattern for an ENUM match table.

show voice enum-match-table

Displays the ENUM match table rules.

test enum

Tests the ENUM match table rules.

voice enum-match-table

Initiates the ENUM match table definition.


DB-2270

May 2008

Debug Commands debug voice h221

debug voice h221 To debug telephony call control information, use the debug voice h221 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice h221 [all | default | error [call [informational] | software [informational]] | function | individual | inout | raw [decode]] no debug voice h221

Syntax Description

all

(Optional) Enables all H.221 debugging, except the raw option.

default

(Optional) Activates function, inout, error call, and software debugging.

error

(Optional) Enables H.221 call error and software error debugging.

error [call]

(Optional) Enables H.221 major call processing error debugs related to the H.221 subsystem.

error [call [informational]]

(Optional) Enables H.221 major and informational call processing error debugs related to the H.221 subsystem.

error [software]

(Optional) Enables H.221 major software error debugs related to the H.221 subsystem.

error [software [informational]]

(Optional) Enables H.221 major and informational software error debugs related to the H.221 subsystem.

function

(Optional) Enables procedure tracing.

individual

(Optional) Activates individual H.221 debugging.

inout

(Optional) Enables subsystem inout debugging.

raw

(Optional) Displays raw BAS messages.

raw [decode]

(Optional) Decodes raw BAS data.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(11)T


12.2SX


Usage Guidelines

Note

This command enables debugging for H.221 message events (voice telephony call control information).

This command provides the same results as the debug voip h221 command.


DB-2271

Debug Commands debug voice h221

Caution

We recommend that you log the output from the debug voice h221 all command to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway. Use the debug voice h221 individual x command, (where x is an index number for a debug category), to activate a single debug, selected by index number instead of entering a group of debug commands. See Table 362 for a list of debug categories and corresponding index numbers. Table 362

Examples

Indexes and Categories for the debug voice h221 individual command

Index Number

Debug Category

1, 2, 30, 31, 32

Secondary number exchange

5, 6, 14, 15, 16, 22

Audio mode/caps

7, 10, 12, 13, 17, 28

Video mode/caps

8, 9, 23

B-channel mode/caps

11, 24, 33

Miscellaneous command exchange

18

Bandwidth calculations

19, 20, 21

DSP configuration

3, 4, 25, 27, 42, 43

General caps/internal

26

Non-standard caps/command

29

Loop request

34, 35, 36, 37, 38, 39, 40, 41

BAS squelch

The raw keyword displays the raw BAS information coming from or to the DSP. It is displayed in a hexadecimal octet format. The decode option decodes the BAS information into a readable English format. The following is sample output from the debug voice h221 raw decode command: BAS=81:1 BAS=82:1 BAS=84:1 BAS=85:1 BAS=F9:1 BAS=02:0 BAS=0A:0 BAS=8A:1 BAS=8A:BAS=8A:BAS=8A:-

Related Commands

0 0 0 0 1 0 0 0 -

0 0 0 0 1 0 0 0 -

0 0 0 0 1 0 0 0 -

0 0 0 0 1 0 1 1 -

0 0 1 1 0 0 0 0 -

0 1 0 0 0 1 1 1 -

1: 0: 0: 1: 1: 0: 0: -: -: -: 0:

AUDIO CAPS=g711 a-law AUDIO CAPS=g711 u-law AUDIO CAPS=g722 48k AUDIO CAPS=g728 H.242 MBE start indication H.242 MBE length=2 H.242 MBE type=H.263 caps Always 1 H.263 MPI=1 H.263 FORMAT=h.263_cif No additional options

Command

Description

debug voip ccapi

Enables debugging for the call control application programming interface (CCAPI) contents.

debug voip rtp

Enables debugging for Real-Time Transport Protocol (RTP) named event packets.


DB-2272

May 2008

Debug Commands debug voice protocol

debug voice protocol To display debugging information for the Voice Line protocol State machine, use the debug voice protocol command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice protocol [slot/port] no debug voice protocol [slot/port]

Syntax Description

slot/port

Command Modes

Privileged EXEC

Command History


Usage Guidelines

In the debugging display, the following abbreviations are used for the different signaling protocols:

Examples


•

LFXS—FXS trunk loop start protocol

•

LFXO—FXO trunk loop start protocol

•

GFXS—FXS trunk ground start protocol

•

GFXO—FXO trunk ground start protocol

•

E&M—E&M trunk protocol

The following is sample output from the debug voice protocol command: Router# debug voice protocol Voice Line protocol State machine debugging is on 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/1: 1/2: 1/2: 1/2: 1/2: 1/2:

LFXS( ), idle gets event offhook LFXS( ), idle ==> seize LFXS(in), seize gets event ready LFXS(in), seize ==> dial_tone LFXS(in), dial_tone gets event digit LFXS(in), dial_tone ==> collect LFXS(in), collect gets event digit LFXS(in), collect gets event digit LFXS(in), collect gets event digit LFXS(in), collect gets event addr_done LFXS(in), collect ==> call_progress LFXS( ), idle gets event seize LFXS( ), idle ==> ringing LFXS(out), ringing gets event dial_tone LFXS(out), ringing gets event offhook LFXS(out), ringing ==> connected


DB-2273

Debug Commands debug voice protocol

1/1: 1/1: 1/2: 1/2: 1/2: 1/2: 1/1: 1/2: 1/2: 1/2: 1/2: 1/2: 1/2: 1/1: 1/1: 1/2: 1/2:

Related Commands

LFXS(in), call_progress gets event answer LFXS(in), call_progress ==> connected LFXS(out), connected gets event onhook LFXS(out), connected ==> disconnect_wait LFXS(out), disconnected_wait gets event disconnect LFXS(out), disconnect_wait ==> cpc LFXS(in), connected gets event disconnect LFXS(out), connected ==> cpc LFXS(out), cpc gets event offhook LFXS(out), cpc gets event timer1 LFXS(out), cpc ==> cpc_recover LFXS(out), cpc gets event timer1 LFXS(out), cpc_recover ==> offhook_wait LFXS(in), offhook_wait gets event onhook LFXS(in), offhook_wait ==> idle LFXS(out), offhook_wait gets event onhook LFXS(out), offhook_wait ==> idle

Command

Description

debug voice all


debug voice eecm




debug voice tdsm


debug voice ccapi



DB-2274

May 2008

Debug Commands debug voice register errors

debug voice register errors To display debug information on voice register module errors during registration in a Cisco Unified CallManager Express (Cisco Unified CME) or Cisco Unified Session Initiation Protocol (SIP) Survivable Remote Site Telephony (SRST) environment, use the debug voice register errors command in privileged EXEC mode. To disable debugging, use the no form of the command. debug voice register errors no debug voice register errors

Syntax Description

This command has no arguments or keywords

Command Default

Disabled

Command Modes

Privileged EXEC mode

Command History

Cisco IOS Release

Modification

12.2(15)ZJ

This command was introduced for Cisco SIP SRST 3.0

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T for Cisco SIP SRST 3.0.

12.4(4)T

This command was added to Cisco Unified CME 3.4 and Cisco SIP SRST 3.4.

12.2SX


Usage Guidelines

Registration errors include failure to match pools or any internal errors that happen during registration.

Examples

Cisco Unified CME

The following is sample output for this command for a registration request with authentication enabled: … *May 6 18:07:26.971: VOICE_REG_POOL: Register request for (4901) from (10.5.49.83) *May 6 18:07:26.971: VOICE_REG_POOL: key(9499C07A000036A3) added to nonce table *May 6 18:07:26.975: VOICE_REG_POOL: Contact doesn't match any pools *May 6 18:07:26.975: //4/89D7750A8005/SIP/Error/ccsip_spi_register_incoming_registration: Registration Authorization failed with authorization header= …

If there are no voice register pools configured for a particular registration request, the message “Contact doesn’t match any pools” is displayed. When authentication is enabled and if the phone requesting registration cannot be authenticated, the message “Registration Authorization failed with authorization header” is displayed.


DB-2275

Debug Commands debug voice register errors

Cisco Unified SIP SRST

The following is sample output from this command: Router# debug voice register errors *Apr *Apr *Apr *Apr *Apr

22 22 22 22 22

11:52:54.523 11:52:54.539 11:52:54.539 11:52:54.559 11:53:04.559

PDT: PDT: PDT: PDT: PDT:

VOICE_REG_POOL: VOICE_REG_POOL: VOICE_REG_POOL: VOICE_REG_POOL: VOICE_REG_POOL:

Contact doesn't match any pools Register request for (33015) from (10.2.152.39) Contact doesn't match any pools. Register request for (33017) from (10.2.152.39) Maximum registration threshold for pool(3) hit

If there are no voice register pools configured for a particular registration request, the message “Contact doesn’t match any pools” is displayed. If the max registrations command is configured, when registration requests reach the maximum limit, the “Maximum registration threshold for pool (x) hit” message is displayed for the particular pool. Table 363 describes the significant fields shown in the display. Table 363

debug voice register errors Field Descriptions

Field

Description

Contact (doesn’t match any pools)

Contact refers to the location of the SIP devices and the IP address.

key (MAC address)

Unique MAC address of a locally available individual SIP phone used to support a degree of authentication in Cisco Unified CME.

Register request for (telephone number) The unique key for each registration is the telephone number. from (IP address). Registration Authorization (failed with Registration Authorization message is displayed when authorization header) authenticate command is configured in Cisco Unified CME.

Related Commands

Command

Description

debug voice register events

Displays debug information on voice register module events during SIP phone registrations in a Cisco Unified CME or Cisco Unified SIP SRST environment.


DB-2276

May 2008

Debug Commands debug voice register events

debug voice register events To display debug information on voice register module events during Session Initiation Protocol (SIP) phone registrations in a Cisco Unified CallManager Express (Cisco Unified CME) or Cisco Unified SIP Survivable Remote Site Telephony (SRST) environment, use the debug voice register events command in privileged EXEC mode. To disable debugging, use the no form of this command. debug voice register events no debug voice register events

Syntax Description


Command Default

Disabled

Command Modes

Privileged EXEC mode

Command History

Cisco IOS Release

Modification

12.2(15)ZJ

This command was introduced for Cisco SIP SRST 3.0

12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T for Cisco SIP SRST 3.0.

12.4(4)T

This command was added to Cisco CME 3.4 and Cisco SIP SRST 3.4.

12.2SX


Usage Guidelines

Using the debug voice register events command should suffice to view registration activity. Registration activity includes matching of pools, registration creation, and automatic creation of dial peers. For more details and error conditions, you can use the debug voice register errors command. Cisco Unified CME The following example shows output from this command: *May 6 18:07:27.223: VOICE_REG_POOL: Register request for (4901) from (1.5.49.83) *May 6 18:07:27.223: VOICE_REG_POOL: Contact matches pool 1 number list 1 *May 6 18:07:27.223: VOICE_REG_POOL: key(4901) contact(10.5.49.83) add to contact table *May 6 18:07:27.223: VOICE_REG_POOL: No entry for (4901) found in contact table *May 6 18:07:27.223: VOICE_REG_POOL: key(4901) contact(10.5.49.83) added to contact tableVOICE_REG_POOL pool->tag(1), dn->tag(1), submask(1) *May 6 18:07:27.223: VOICE_REG_POOL: Creating param container for dial-peer 40001. *May 6 18:07:27.223: VOICE_REG_POOL: Created dial-peer entry of type 0 *May 6 18:07:27.223: VOICE_REG_POOL: Registration successful for 4901, registration id is 2 ...


DB-2277


The phone number 4901 associated with voice register pool 1, voice register dn 1, registered successfully. A dynamic normal (type 0) VoIP dial peer has been created for entry 4901. The dial peer can be verified using the show voice register dial-peers and show sip-ua status registrar commands. Cisco Unified SIP SRST

The following is sample output from this command: Router# debug voice register events Apr 22 10:50:21.731 Apr 22 10:50:21.731 table Apr 22 10:50:21.731 Apr 22 10:50:21.731 updated Apr 22 10:50:21.731 Apr 22 10:50:21.731 id is 257

PDT: VOICE_REG_POOL: Contact matches pool 1 PDT: VOICE_REG_POOL: key(91011) contact(192.168.0.2) add to contact PDT: VOICE_REG_POOL: key(91011) exists in contact table PDT: VOICE_REG_POOL: contact(192.168.0.2) exists in contact table, ref PDT: VOICE_REG_POOL: Created dial-peer entry of type 1 PDT: VOICE_REG_POOL: Registration successful for 91011, registration

The phone number 91011 registered successfully, and type 1 is reported in the debug, which means that there is a preexisting VoIP dial peer. Apr 22 10:50:38.119 Apr 22 10:50:38.119 Apr 22 10:50:38.123 table Apr 22 10:50:38.123 Apr 22 10:50:38.123 updated Apr 22 10:50:38.123 Apr 22 10:50:38.123 id is 258

PDT: VOICE_REG_POOL: Register request for (91021) from (192.168.0.3) PDT: VOICE_REG_POOL: Contact matches pool 2 PDT: VOICE_REG_POOL: key(91021) contact(192.168.0.3) add to contact PDT: VOICE_REG_POOL: key(91021) exists in contact table PDT: VOICE_REG_POOL: contact(192.168.0.3) exists in contact table, ref PDT: VOICE_REG_POOL: Created dial-peer entry of type 1 PDT: VOICE_REG_POOL: Registration successful for 91021, registration

A dynamic VoIP dial peer has been created for entry 91021. The dial peer can be verified using the show voice register dial-peers and show sip-ua status registrar commands. Apr 22 10:51:08.971 Apr 22 10:51:08.971 Apr 22 10:51:08.971 table Apr 22 10:51:08.971 Apr 22 10:51:08.975 table Apr 22 10:51:08.979 Apr 22 10:51:08.979 id is 259 Apr 22 10:51:09.019 Apr 22 10:51:09.019 Apr 22 10:51:09.019 table Apr 22 10:51:09.019 Apr 22 10:51:09.023 table Apr 22 10:51:09.027 Apr 22 10:51:09.027 id is 260 Apr 22 10:51:09.071 Apr 22 10:51:09.071 Apr 22 10:51:09.071 table Apr 22 10:51:09.071 Apr 22 10:51:09.075 table Apr 22 10:51:09.079

PDT: VOICE_REG_POOL: Register request for (95021) from (10.2.161.50) PDT: VOICE_REG_POOL: Contact matches pool 3 PDT: VOICE_REG_POOL: key(95021) contact(10.2.161.50) add to contact PDT: VOICE_REG_POOL: No entry for (95021) found in contact table PDT: VOICE_REG_POOL: key(95021) contact(10.2.161.50) added to contact PDT: VOICE_REG_POOL: Created dial-peer entry of type 0 PDT: VOICE_REG_POOL: Registration successful for 95021, registration PDT: VOICE_REG_POOL: Register request for (95012) from (10.2.161.50) PDT: VOICE_REG_POOL: Contact matches pool 3 PDT: VOICE_REG_POOL: key(95012) contact(10.2.161.50) add to contact PDT: VOICE_REG_POOL: No entry for (95012) found in contact table PDT: VOICE_REG_POOL: key(95012) contact(10.2.161.50) added to contact PDT: VOICE_REG_POOL: Created dial-peer entry of type 0 PDT: VOICE_REG_POOL: Registration successful for 95012, registration PDT: VOICE_REG_POOL: Register request for (95011) from (10.2.161.50) PDT: VOICE_REG_POOL: Contact matches pool 3 PDT: VOICE_REG_POOL: key(95011) contact(10.2.161.50) add to contact PDT: VOICE_REG_POOL: No entry for (95011) found in contact table PDT: VOICE_REG_POOL: key(95011) contact(10.2.161.50) added to contact PDT: VOICE_REG_POOL: Created dial-peer entry of type 0


DB-2278

May 2008


Apr 22 10:51:09.079 PDT: VOICE_REG_POOL: Registration successful for 95011, registration id is 261 Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: Register request for (95500) from (10.2.161.50) Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: Contact matches pool 3 Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: key(95500) contact(10.2.161.50) add to contact table Apr 22 10:51:09.123 PDT: VOICE_REG_POOL: No entry for (95500) found in contact table Apr 22 10:51:09.127 PDT: VOICE_REG_POOL: key(95500) contact(10.2.161.50) added to contact table Apr 22 10:51:09.131 PDT: VOICE_REG_POOL: Created dial-peer entry of type 0 Apr 22 10:51:09.131 PDT: VOICE_REG_POOL: Registration successful for 95500, registration id is 262 *Apr 22 11:52:54.523 PDT: VOICE_REG_POOL: Contact doesn't match any pools *Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Register request for (33015) from (10.2.152.39) *Apr 22 11:52:54.539 PDT: VOICE_REG_POOL: Contact doesn't match any pools *Apr 22 11:52:54.559 PDT: VOICE_REG_POOL: Register request for (33017) from (10.2.152.39)


debug voice register events Field Descriptions

Field

Description

Contact

Indicates the location of the SIP devices and may indicate the IP address.

contact table

The table that maintains the location of the SIP devices.

key

The phone number is used as the unique key to maintain registrations of SIP devices.

multiple contact

More than one registration matches the same phone number.

no entry

The incoming registration was not found.

type 0

Normal dial peer.

type 1

Existing normal dial peer.

type 2

Proxy dial peer.

type 3

Existing proxy dial peer.

type 4

Dial-plan dial peer.

type 5

Existing dial-plan dial peer.

type 6

Alias dial peer.

type 7

Existing alias dial peer.

un-registration successful

The incoming unregister was successful.

Register request/registration id number The internal unique number for each registration; useful for debugging particular registrations.

Related Commands

Command

Description

debug voice register errors

Displays debug information on voice register module errors during registration in a Cisco Unified CME or Cisco Unified SIP SRST environment.


DB-2279


Command

Description

show sip-ua status registrar

Displays all the SIP endpoints that are currently registered with the contact address.

show voice register dial-peers

Displays details of Cisco Unified SIP SRST configuration and of all dynamically created VoIP dial peers.


DB-2280

May 2008

Debug Commands debug voice signaling

debug voice signaling To display debugging information for the voice port signaling, use the debug voice signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice signaling [slot/port] no debug voice signaling [slot/port]

Syntax Description

slot/port

Command Modes

Privileged EXEC

Usage Guidelines


Examples

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


Router# debug voice signaling 1/1: 1/2: 1/2: 1/2: 1/2: 1/2: 1/2: 1/2: 1/2: 1/2: 1/2: 1/2: 1/1: 1/2: 1/2: 1/1: 1/1: 1/2: 1/1: 1/1: 1/2: 1/1: 1/1: 1/2: 1/1: 1/2: 1/1: 1/2: 1/1: 1/2:

TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU, TIU,

report_local_hook=1 set ring cadence=1 ringer on ringer off ringer on report_local_hook=1 turning off ringer due to SW ringtrip ringer off set ring cadence=0 ringer off set reverse battery=1 set reverse battery=1 report_local_hook=0 set reverse battery=0 set loop disabled=1 set reverse battery=0 set loop disabled=1 report_local_hook=1 report_lead_gnd grounded=1 report_lead_gnd grounded=0 set loop disabled=0 set loop disabled=0 report_local_hook=0 report_local_hook=0 report_local_hook=1 report_local_hook=1 report_local_hook=0 report_local_hook=0 set reverse battery=0 set reverse battery=0


DB-2281

Debug Commands debug voice signaling

Related Commands

Command

Description

debug voice all


debug voice eecm




debug voice tdsm

Display debugging information for the voice tandem switch.

debug voice ccapi



DB-2282

May 2008

Debug Commands debug voice source-group

debug voice source-group To view voice source group information, use the debug voice source-group command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice source-group no debug voice source-group

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Usage Guidelines

Disable console logging and use buffered logging before using the debug voice source-group command. Using the debug voice source-group command generates a large volume of debugs, which can affect router performance.

Examples

A sample output of the debug voice source-group command is shown below. The output shows that the hash table key for source ip group is 1. 00:30:49:SIPG:sipg_get() - idString=0x63BE1C28, hashkey=1 00:30:49:SIPG:sipg_find_key - hashkey=1,idstring=0x63BE1C28


debug voice source-group Field Descriptions

Field

Description

hashkey

Hash table index of the source IP group.

idString

Value of the pointer to the source IP group name, which is used to make sure that it is not null.


DB-2283

Debug Commands debug voice source-group

Related Commands

Command

Description

carrier-id (voice source group)

Specifies the carrier handling incoming source VoIP calls (for carrier ID routing).

show voice source-group

Displays the details of one or more source IP groups.

test source-group

Tests the definition of a source IP group.

translation-profile (source group)

Associates a translation profile with the source IP group.

trunk-group-label (voice source group)

Specifies the trunk group handling incoming source VoIP calls (for trunk group label routing).

voice source-group

Initiates the source IP group definition.


DB-2284

May 2008

Debug Commands debug voice statistics

debug voice statistics To enable debugging of voice statistics, use the debug voice statistics command in privileged EXEC mode. To disable the debugging, use the no form of this command. debug voice statistics {csr | core | accounting} no debug voice statistics {csr | core | accounting}

Syntax Description

csr

Signaling voice call statistics records collection is debugged.

core

Generic statistics collection is debugged.

accounting

Voice accounting CSR collection is debugged.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Examples

The following example shows the collection of records that is occurring in between intervals: Router# debug voice statistics accounting vstats_timer_handle_interval_event():Between Intervals! 04:52:37: vstats_acct_interval_end: interval_tag = 4 04:52:37: vstats_acct_interval_end: pushing out, tag=3 04:52:37: vstats_acct_clean_history_stats: 04:52:37: vstats_acct_clean_history_stats: stats (tag=3) not to be deleted 04:52:37: vstats_acct_clean_history_stats: stats (tag=2) not to be deleted 04:52:37: vstats_acct_create_empty_stats: 04:52:37: vstats_acct_create_new_rec_list: 04:52:37: vstats_acct_create_new_rec_list: add acct rec: methodlist=h323, acct-criteria=2 04:52:37: vstats_acct_create_new_rec: 04:52:37: vstats_acct_add_rec_entry: 04:52:37: vstats_acct_add_stats_entry: 04:52:37: vstat_push_driver_file_open():Cannot open ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z. errno=65540=Unknown error 65540 vstat_push_drv_activate_ftp_file_tx():open file (ftp://sgcp:sgcp@jeremy-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z)=(ftp://sgcp:sg cp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162000Z)failed! vstats_push_api_push_formatted_text():Start CMD error!

The following example shows a voice call going through the gateway: Router# debug voice statistics csr 04:55:07: EM: Notify the producer not to produce


DB-2285


04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07:

RADIUS(00000019): Storing nasport 0 in rad_db RADIUS(00000019): Config NAS IP: 0.0.0.0 RADIUS(00000019): sending RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.203 RADIUS(00000019): Send Accounting-Request to 1.6.10.203:1646 id 21645/49,len 496 RADIUS: authenticator C5 B8 AA 2E C3 AF 02 93 - 45 0B AE E5 B6 B2 99 1F RADIUS: Acct-Session-Id [44] 10 "00000020" RADIUS: Vendor, Cisco [26] 57 RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:30.994 UTC Thu Feb 13 2003" RADIUS: Vendor, Cisco [26] 27 RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW." RADIUS: Vendor, Cisco [26] 56 RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002 B935C142" RADIUS: Vendor, Cisco [26] 31 RADIUS: h323-call-origin [26] 25 "h323-call-origin=answer" RADIUS: Vendor, Cisco [26] 32 RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony" RADIUS: Vendor, Cisco [26] 65 RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7 800E0002 B935C142" RADIUS: Vendor, Cisco [26] 30 RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine" RADIUS: Vendor, Cisco [26] 35 RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11" RADIUS: Vendor, Cisco [26] 32 RADIUS: Cisco AVpair [1] 26 "calling-party-category=9" RADIUS: Vendor, Cisco [26] 33 RADIUS: Cisco AVpair [1] 27 "transmission-medium-req=0" RADIUS: User-Name [1] 4 "22" RADIUS: Acct-Status-Type [40] 6 Start [1] RADIUS: NAS-Port-Type [61] 6 Async [0] RADIUS: Vendor, Cisco [26] 20 RADIUS: cisco-nas-port [2] 14 "ISDN 6/0:D:1" RADIUS: NAS-Port [5] 6 0 RADIUS: Calling-Station-Id [31] 4 "22" RADIUS: Called-Station-Id [30] 4 "11" RADIUS: Service-Type [6] 6 Login [1] RADIUS: NAS-IP-Address [4] 6 1.6.43.101 RADIUS: Acct-Delay-Time [41] 6 0 RADIUS(0000001A): Config NAS IP: 0.0.0.0 RADIUS(0000001A): sending RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.203 RADIUS(0000001A): Send Accounting-Request to 1.6.10.203:1646 id 21645/50, len427 RADIUS: authenticator E4 98 06 8C 48 63 4F AA - 56 4F 40 12 33 F0 F5 99 RADIUS: Acct-Session-Id [44] 10 "00000021" RADIUS: Vendor, Cisco [26] 57 RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:31.006 UTC Thu Feb 13 2003" RADIUS: Vendor, Cisco [26] 27 RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW." RADIUS: Vendor, Cisco [26] 56 RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002 B935C142" RADIUS: Vendor, Cisco [26] 34 RADIUS: h323-call-origin [26] 28 "h323-call-origin=originate" RADIUS: Vendor, Cisco [26] 27 RADIUS: h323-call-type [27] 21 "h323-call-type=VoIP" RADIUS: Vendor, Cisco [26] 65 RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7 800E0002 B935C142" RADIUS: Vendor, Cisco [26] 30 RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"


DB-2286

May 2008


04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07:

RADIUS: Vendor, Cisco [26] 30 RADIUS: Cisco AVpair [1] 24 "session-protocol=cisco" RADIUS: Vendor, Cisco [26] 35 RADIUS: Cisco AVpair [1] 29 "gw-rxd-cdn=ton:0,npi:0,#:11" RADIUS: User-Name [1] 4 "22" RADIUS: Acct-Status-Type [40] 6 Start [1] RADIUS: Calling-Station-Id [31] 4 "22" RADIUS: Called-Station-Id [30] 4 "11" RADIUS: Service-Type [6] 6 Login [1]

04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:07: 04:55:08: 04:55:08: 04:55:08: 04:55:09: 04:55:09: 04:55:09: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:10: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13:

RADIUS: NAS-IP-Address [4] 6 1.6.43.101 RADIUS: Acct-Delay-Time [41] 6 0 EM: No consumer registered for event type NEWINFO EM: Notify the producer not to produce EM: No consumer registered for event type NEWINFO EM: Notify the producer not to produce RADIUS: no sg in radius-timers: ctx 0x65BAB1BC sg 0x0000 RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/50 RADIUS: acct-delay-time for 403963FC (at 403965A1) now 1 RADIUS: no sg in radius-timers: ctx 0x65ADB8EC sg 0x0000 RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/49 RADIUS: acct-delay-time for 40389BFC (at 40389DE6) now 1 RADIUS: no sg in radius-timers: ctx 0x65BAB1BC sg 0x0000 RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/51 RADIUS: acct-delay-time for 403963FC (at 403965A1) now 2 RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.105 RADIUS: Received from id 21645/53 1.8.159.105:1645, Accounting-response, len 20 RADIUS: authenticator 57 EF DD 90 0F 88 76 EA - A5 3D A7 44 0D 90 66 16 vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x1 acct_rsp_status=1 callid= 26, incoming=0, leg=2 vstats_acct_rsp_handler: last acct msg not sent yet. methodlist: h323 RADIUS: no sg in radius-timers: ctx 0x65ADB8EC sg 0x0000 RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/52 RADIUS: acct-delay-time for 40389BFC (at 40389DE6) now 2 RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.105 RADIUS: Received from id 21645/54 1.8.159.105:1645, Accounting-response, len 20 RADIUS: authenticator 97 88 6C BA DA 22 E7 5E - 73 EC 21 C6 36 1B 93 18 vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x1 acct_rsp_status=callid= 25, incoming=1, leg=1 vstats_acct_rsp_handler: last acct msg not sent yet. methodlist: h323 RADIUS(0000001A): Config NAS IP: 0.0.0.0 RADIUS(0000001A): sending RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.203 RADIUS(0000001A): Send Accounting-Request to 1.6.10.203:1646 id 21645/55, len885 RADIUS: authenticator F8 4F F1 30 7E 8B 5B 46 - EF AE 17 2D 5C BA 36 E5 RADIUS: Acct-Session-Id [44] 10 "00000021" RADIUS: Vendor, Cisco [26] 57 RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:31.006 UTC Thu Feb 13 2003" RADIUS: Vendor, Cisco [26] 27 RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW." RADIUS: Vendor, Cisco [26] 56 RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002 B935C142" RADIUS: Vendor, Cisco [26] 34 RADIUS: h323-call-origin [26] 28 "h323-call-origin=originate" RADIUS: Vendor, Cisco [26] 27 RADIUS: h323-call-type [27] 21 "h323-call-type=VoIP" RADIUS: Vendor, Cisco [26] 65 RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7 800E0002 B935C142" RADIUS: Vendor, Cisco [26] 30 RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine" RADIUS: Vendor, Cisco [26] 30

04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13:


DB-2287


04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13:

RADIUS: Cisco AVpair RADIUS: Vendor, Cisco RADIUS: Cisco AVpair RADIUS: Vendor, Cisco RADIUS: h323-connect-time Thu Feb 13 2003" 04:55:13: RADIUS: Acct-Input-Octets 04:55:13: RADIUS: Acct-Output-Octets 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13:

[1] [26] [1] [26] [28]

24 35 29 59 53

"session-protocol=cisco"

[42] [43]

6 6

2241 81

"gw-rxd-cdn=ton:0,npi:0,#:11" "h323-connect-time=*16:22:31.046 UTC

RADIUS: Acct-Input-Packets [47] 6 113 RADIUS: Acct-Output-Packets [48] 6 5 RADIUS: Acct-Session-Time [46] 6 5 RADIUS: Vendor, Cisco [26] 62 RADIUS: h323-disconnect-tim[29] 56 "h323-disconnect-time=*16:22:36.070 UTC Thu Feb 13 2003" RADIUS: Vendor, Cisco [26] 32 RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10" RADIUS: Vendor, Cisco [26] 38 RADIUS: h323-remote-address[23] 32 "h323-remote-address=14.0.0.110" RADIUS: Vendor, Cisco [26] 24 RADIUS: Cisco AVpair [1] 18 "release-source=1" RADIUS: Vendor, Cisco [26] 29 RADIUS: h323-voice-quality [31] 23 "h323-voice-quality=-1" RADIUS: Vendor, Cisco [26] 57 RADIUS: Cisco AVpair [1] 51 "alert-timepoint=*16:22:31.030 UTC Thu Feb 13 2003" RADIUS: Vendor, Cisco [26] 39 RADIUS: Cisco AVpair [1] 33 "remote-media-address=14.0.0.110" RADIUS: Vendor, Cisco [26] 44 RADIUS: Cisco AVpair [1] 38 "gw-final-xlated-cdn=ton:0,npi:0,#:11" RADIUS: Vendor, Cisco [26] 44 RADIUS: Cisco AVpair [1] 38 "gw-final-xlated-cgn=ton:0,npi:1,#:22" RADIUS: User-Name [1] 4 "22" RADIUS: Acct-Status-Type [40] 6 Stop [2] RADIUS: Calling-Station-Id [31] 4 "22" RADIUS: Called-Station-Id [30] 4 "11" RADIUS: Service-Type [6] 6 Login [1] RADIUS: NAS-IP-Address [4] 6 1.6.43.101 RADIUS: Acct-Delay-Time [41] 6 0 RADIUS(00000019): Using existing nas_port 0 RADIUS(00000019):Config NAS IP: 0.0.0.0 RADIUS(00000019):sending RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.6.10.203 RADIUS(00000019): Send Accounting-Request to 1.6.10.203:1646 id 21645/56, len766 RADIUS: authenticator 61 60 EB 92 29 5C DE B4 - CE 40 1C AB E3 A1 C8 F7 RADIUS: Acct-Session-Id [44] 10 "00000020" RADIUS: Vendor, Cisco [26] 57 RADIUS: h323-setup-time [25] 51 "h323-setup-time=*16:22:30.994 UTC Thu Feb 13 2003" RADIUS: Vendor, Cisco [26] 27 RADIUS: h323-gw-id [33] 21 "h323-gw-id=5400-GW." RADIUS: Vendor, Cisco [26] 56 RADIUS: Conf-Id [24] 50 "h323-conf-id=2F4ED2E3 3EA611D7 800E0002 B935C142" RADIUS: Vendor, Cisco [26] 31 RADIUS: h323-call-origin [26] 25 "h323-call-origin=answer" RADIUS: Vendor, Cisco [26] 32 RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony" RADIUS: Vendor, Cisco [26] 65 RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=2F4ED2E3 3EA611D7 800E0002 B935C142" RADIUS: Vendor, Cisco [26] 30 RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine" RADIUS: Vendor, Cisco [26] 35


DB-2288

May 2008


04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13:

RADIUS: Cisco AVpair RADIUS: Vendor, Cisco RADIUS: Cisco AVpair RADIUS: Vendor, Cisco RADIUS: Cisco AVpair RADIUS: Vendor, Cisco RADIUS: h323-connect-time Feb 13 2003" 04:55:13: RADIUS: Acct-Input-Octets 04:55:13: RADIUS: Acct-Output-Octets 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:13: 04:55:14: 04:55:14: 04:55:14: 04:55:14: 04:55:14: 04:55:14: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15: 04:55:15:

[1] [26] [1] [26] [1] [26] [28]

29 32 26 33 27 59 53

"gw-rxd-cdn=ton:0,npi:0,#:11"

[42] [43]

6 6

81 2241

"calling-party-category=9" "transmission-medium-req=0" "h323-connect-time=*16:22:31.046 UTC Thu

RADIUS: Acct-Input-Packets [47] 6 5 RADIUS: Acct-Output-Packets [48] 6 113 RADIUS: Acct-Session-Time [46] 6 5 RADIUS: Vendor, Cisco [26] 62 RADIUS: h323-disconnect-tim[29] 56 "h323-disconnect-time=*16:22:36.064 UTC Thu Feb 13 2003" RADIUS: Vendor, Cisco [26] 32 RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10" RADIUS: Vendor, Cisco [26] 35 RADIUS: Cisco AVpair [1] 29 "h323-ivr-out=Tariff:Unknown" RADIUS: Vendor, Cisco [26] 24 RADIUS: Cisco AVpair [1] 18 "release-source=1" RADIUS: Vendor, Cisco [26] 28 RADIUS: h323-voice-quality [31] 22 "h323-voice-quality=0" RADIUS: User-Name [1] 4 "22" RADIUS: Acct-Status-Type [40] 6 Stop [2] RADIUS: NAS-Port-Type [61] 6 Async [0] RADIUS: Vendor, Cisco [26] 20 RADIUS: cisco-nas-port [2] 14 "ISDN 6/0:D:1" RADIUS: NAS-Port [5] 6 0 RADIUS: Calling-Station-Id [31] 4 "22" RADIUS: Called-Station-Id [30] 4 "11" RADIUS: Service-Type [6] 6 Login [1] RADIUS: NAS-IP-Addres [4] 6 1.6.43.101 RADIUS: Acct-Delay-Time [41] 6 0 RADIUS: no sg in radius-timers: ctx 0x65BAB070 sg 0x0000 RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/55 RADIUS: acct-delay-time for 40553934 (at 40553CA3) now 1 RADIUS: no sg in radius-timers: ctx 0x65BA8284 sg 0x0000 RADIUS: Retransmit to (1.6.10.203:1645,1646) for id 21645/56 RADIUS: acct-delay-time for 405546C4 (at 405549BC) now 1 RADIUS: no sg in radius-timers: ctx 0x65BAB070 sg 0x0000 RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/57 RADIUS: acct-delay-time for 40553934 (at 40553CA3) now 2 RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 1.8.159.105 RADIUS: no sg in radius-timers: ctx 0x65BA8284 sg 0x0000 RADIUS: Fail-over to (1.8.159.105:1645,1645) for id 21645/58 RADIUS: acct-delay-time for 405546C4 (at 405549BC) now 2 RADIUS/ENCODE: Best Local IP-Address 1.6.43.101 for Radius-Server 10.8.159.105 RADIUS: Received from id 21645/59 1.8.159.105:1645, Accounting-response, len 20 RADIUS: authenticator B1 C4 5E FC DB FA 74 A4 - 05 E2 34 52 1A 11 26 06 vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x4 acct_rsp_status=1 callid= 26, incoming=0, leg=2 vstats_acct_rsp_handler: increment since-reset counter vstats_acct_rsp_handler: increment interval counter RADIUS: Received from id 21645/60 10.8.159.105:1645, Accounting-response, len 20 RADIUS: authenticator 0E 70 74 2F E5 D8 EE 98 - B9 C0 DA 66 74 ED 84 77 vstats_acct_rsp_handler: methodlist=h323, rsp_type=0x4 acct_rsp_status=1 callid= 25, incoming=1, leg=1 vstats_acct_rsp_handler: increment since-reset counter vstats_acct_rsp_handler: increment interval counter


DB-2289


The following example shows the collection of records that is in between intervals: Router# debug voice statistics accounting Translating "abc-pc"...domain server (255.255.255.255) vstats_timer_handle_interval_event():Between Intervals! 04:57:37: vstats_acct_interval_end: interval_tag = 5 04:57:37: vstats_acct_interval_end: pushing out, tag=4 04:57:37: vstats_acct_clean_history_stats: 04:57:37: vstats_acct_clean_history_stats: stats (tag=4) not to be deleted 04:57:37: vstats_acct_clean_history_stats: stats (tag=3) not to be deleted 04:57:37: vstats_acct_clean_history_stats: stats (tag=2) not to be deleted 04:57:37: vstats_acct_create_empty_stats: 04:57:37: vstats_acct_create_new_rec_list: 04:57:37: vstats_acct_create_new_rec_list: add acct rec: methodlist=h323, acct-criteria=2 04:57:37: vstats_acct_create_new_rec: 04:57:37: vstats_acct_add_rec_entry: 04:57:37: vstats_acct_add_stats_entry: 04:57:37: vstat_push_driver_file_open():Can not open ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z. errno=65540=Unknown error 65540 vstat_push_drv_activate_ftp_file_tx():open file (ftp://sgcp:sgcp@abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z)=(ftp://sgcp:sgcp@ abc-pc:21//ftp_files/vstats.5400-GW.2003-02-13T162500Z) failed! vstats_push_api_push_formatted_text():Start CMD error!

Related Commands

Command

Description

debug event-manager

Enables debugging of the event manager.


DB-2290

May 2008

Debug Commands debug voice tdsm

debug voice tdsm To display debugging information for the voice tandem switch, use the debug voice tdsm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice tdsm [slot/port] no debug voice tdsm [slot/port]

Syntax Description

slot/port

Command Modes

Privileged EXEC

Usage Guidelines


Examples

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


Router# debug voice tdsm Voice tandem switch debugging is on -1/-1: TDSM(out), ref= -1, state NULL gets event OUT_SETUP 1/1: TDSM(in), ref=6, state CALL_INITIATED gets event IN_CALLPROC 1/1: TDSM(in), ref=6, state OUTG_CALLPROC gets event IN_ALERTING 1/1: TDSM(in), ref=6, state CALL_DELIVERED gets event IN_CONNECT 1/1: TDSM(out),ref=6, state CALL_ACTIVE send out conn. ack 1/1: TDSM(out),ref=6, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK 1/1: TDSM(in), ref=6, state RELEASE_REQ gets event IN_REL_COMP, cause REMOTE_ONHOOK -1/-1: TDSM(in), ref=-1, state NULL gets event IN_SETUP -1/-1: TDSM(out), ref=6, state INC_CALLPROC gets event OUT_ALERTING 1/1: TDSM(out),ref=6, state CALL_RECEIVED gets event OUT_CONNECT 1/1: TDSM(in), ref-6, state CONNECT_REQ gets event IN_CONN_ACK 1/1: TDSM(out),ref-6, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK 1/1: TDSM(in), ref=6, state RELEASE_REQ gets event IN_REL_COMP, cause REMOTE_ONHOOK -1/-1:TDSM(out), ref=-1, state NULL gets event OUT_SETUP 1/1: TDSM(in), ref=7, state CALL_INITIATED gets event IN_CALLPROC 1/1: TDSM(in), ref=7, state OUTG_CALLPROC gets event IN_ALERTING 1/1: TDSM(in), ref=7, state CALL_DELIVERED gets event IN_CONNECT 1/1: TDSM(out),ref=7, state CALL_ACTIVE send out conn.ack 1/1: TDSM(out),ref=7, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK -1/-1: TDSM(in), ref=-1, state NULL gets event IN_SETUP -1/-1: TDSM(out), ref=7, state INC_CALLPROC gets event OUT_ALERTING 1/1: TDSM(out),ref=7. state CALL_RECEIVED gets event OUT_CONNECT 1/1: TDSM(in), ref=7, state CONNECT_REQ gets event IN_CONN_ACK 1/1: TDSM(in), ref=7, state CALL_ACTIVE send out release, cause LOCAL_ONHOOK 1/1: TDSM(in), ref=7, state RELEASE_REQ gets event IN_REL_COMP, cause REMOTE_ONHOOK -1/-1: TDSM(out), ref=-1, state NULL gets event OUT_SETUP 1/1: TDSM(in), ref=8, state CALL_INITIATED gets event IN_CALLPROC 1/1: TDSM(in), ref=8, state OUTG_CALLPROC gets event IN_ALERTINGbug all


DB-2291

Debug Commands debug voice tdsm

Related Commands

Command

Description

debug voice all


debug voice eecm






debug voice ccapi



DB-2292

May 2008

Debug Commands debug voice translation

debug voice translation To view voice translation rule information, use the debug voice translation command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice translation no debug voice translation

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Usage Guidelines

Disable console logging and use buffered logging before using the debug voice translation command. Using the debug voice translation command generates a large volume of debugs, which can affect router performance.

Examples

Sample output from the debug voice translation command is shown below. The output shows the details of the original number following “regxrule_profile_translate”. Following “regxrule_profile_match”, the output shows that rule 1 in the translation rule 1001 was a match; then the details of the SED substitution are shown. Then the output shows the details of the translated number following “regxrule_profile_translate”. In this example, because there was no called number or redirect number translation configured on the translation profile, corresponding errors were generated with a message that no match was found. Following “regxrule_dp_translate”, the output indicates that there is no translation profile for outgoing direction, then it prints the numbers sent to the outgoing SPI. Router# 00:51:56:regxrule_get_profile_from_trunkgroup:Voice port 0x64143DA8 does not belong to any trunk group 00:51:56:regxrule_get_profile_from_trunkgroup:Voice port 0x64143DA8 does not belong to any trunk group 00:51:56:regxrule_stack_pop_RegXruleNumInfo:stack=0x63DECAF4; count=1 00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=0


DB-2293


00:51:56:regxrule_profile_translate:number=4088880101 type=unknown plan=unknown numbertype=calling 00:51:56:regxrule_profile_match:Matched with rule 1 in ruleset 1001 00:51:56:regxrule_profile_match:Matched with rule 1 in ruleset 1001 00:51:56:sed_subst:Successful substitution; pattern=4088880101 matchPattern=^.* replacePattern=5551212 replaced pattern=5551212 00:51:56:regxrule_subst_num_type:Match Type = none, Replace Type = none Input Type = unknown 00:51:56:regxrule_subst_num_plan:Match Plan = none, Replace Plan = none Input Plan = unknown 00:51:56:regxrule_profile_translate:xlt_number=5551212 xlt_type=unknown xlt_plan=unknown 00:51:56:regxrule_profile_translate:number= type=UNKNOWN plan=UNKNOWN numbertype=redirect-called 00:51:56:regxrule_get_RegXrule:Invalid translation ruleset tag=0 00:51:56:regxrule_profile_match:Error:ruleset for redirect-called number not found 00:51:56:regxrule_profile_translate:No match:number= type=UNKNOWN plan=UNKNOWN 00:51:56:regxrule_profile_translate:number=5108880101 type=unknown plan=unknown numbertype=called 00:51:56:regxrule_get_RegXrule:Invalid translation ruleset tag=0 00:51:56:regxrule_profile_match:Error:ruleset for called number not found 00:51:56:regxrule_profile_translate:No match:number=5108880101 type=unknown plan=unknown 00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=1 00:51:56:regxrule_dp_translate:No profile found in peer 5108888 for outgoing direction 00:51:56:regxrule_dp_translate:calling_number=5551212 calling_octet=0x0 called_number=5108880101 called_octet=0x80 redirect_number= redirect_type=4294967295 redirect_plan=4294967295 00:51:56:regxrule_stack_pop_RegXruleNumInfo:stack=0x63DECAF4; count=2 00:51:56:regxrule_stack_push_RegXruleNumInfo:stack=0x63DECAF4; count=1

Table 366 provides an alphabetical listing of the debug voice translation command fields and a description of each field. Table 366

debug voice translation Field Descriptions

Field

Description

called_number

Called number dialed number identification service (DNIS).

called_octet

Octect3 of called IE.

calling_number

Calling number automatic number identifier (ANI).

calling_octect

Octect3 of calling IE.

count

Number of elements in the translation stack.

Input Plan

Numbering plan of the input.

Input Type

Numbering type of the input.

matchPattern

Regular exp used for matching.

Match Plan

Numbering plan in the translation rule.

Match Type

Numbering type in the translation rule.

number

Incoming number for translation.

numbertype

Type of number: calling, called, or redirect.

pattern

Input string to the regular expression for matching.

plan

Numbering plan.

redirect_number

Redirect number.

redirect_plan

Numbering plan in the redirect number.


DB-2294

May 2008


Table 366

Related Commands

debug voice translation Field Descriptions (continued)

Field

Description

redirect_type

Numbering type in the redirect number.

replaced pattern

Final string after applying replacement rule of translation rule.

replacePattern

Replacement pattern in the translation rule.

Replace Plan

Replacement numbering plan in the translation rule.

Replace Type

Replacement numbering type in the translation rule.

stack

Value of the translation rule stack.

tag

Tag of the translation rule.

type

Numbering type in the translation rule.

xlt_number

Number after translation.

xlt_plan

Numbering plan after translation.

xlt_type

Numbering type after translation.

Command

Description

rule (voice translation-rule)

Defines the translation rule parameters for matching and replacing call number patterns.

show voice translation-rule

Displays a voice translation rule.

test voice translation-rule

Tests a voice translation rule.

voice translation-rule

Initiates the translation rule definition.


DB-2295

Debug Commands debug voice uri

debug voice uri To display debugging messages for uniform resource identifier (URI) voice classes, use the debug voice uri command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice uri no debug voice uri

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(4)T


12.2SX


Usage Guidelines

Use this command to see which URI voice class and dial peer is matched for a Session Initiation Protocol (SIP) or telephone (TEL) URI.

Examples

The following examples show output from the debug voice uri command. Comments are imbedded in the examples. Router# debug voice uri

Output Showing Failed Match of Voice URI Class

The following output displays when an outbound dial peer match fails for the URL sip:[email protected]?Subject=sip_e164_headers_plus.tcl&AccountInfo=12345&Priority=Urgent *Jul 11 05:20:44.759:vuri_match_class:tag (767)

The first dial peer in the list is 767, which contains the destination uri 767 command. 767 is a TELURI class, so it does not match the above URL. *Jul 11 05:20:44.759:vuri_match_class:tag (766)

The next dial peer, 766, contains the destination uri 766 command. *Jul 11 05:20:44.759:vuri_match_class_sip:sip:[email protected]?Subject=sip_e164_headers_plus.tc l&AccountInfo=12345&Priority=Urgent did not match pattern


DB-2296

May 2008


766 is a SIP URI class and contains only the pattern command. The regex does not match the pattern, so there is no match. *Jul 11 05:20:44.759:vuri_match_class:tag (999)

The next dial peer, 999, contains the destination uri 999 command. *Jul 11 05:20:44.759:vuri_match_class_sip:Match with phone context *Jul 11 05:20:44.759:vuri_match_class_sip:input ()

If the phone context command is not present in the URI class, it is skipped. *Jul 11 05:20:44.759:vuri_match_class_sip:Match with host *Jul 11 05:20:44.759:vuri_match_class_sip:input (sip.tgw.com)

If the host command is not present in the URI class, it is skipped. *Jul 11 05:20:44.759:vuri_match_class_sip:Match with user-id *Jul 11 05:20:44.759:vuri_match_class_sip:input (9991234)

Try to match with the user-id portion of the URL, which is 9991234. *Jul 11 05:20:44.759:vuri_match_class_sip:Match failed

The configured pattern, however, is “driver” and it is not a match. Output Showing Successful Match of Voice URI Class

The following debugging output is displayed when an outbound dial peer match is done for the URL sip:[email protected]: *Jul 11 06:06:30.119:vuri_match_class:tag (767)

The first dial peer in the list is 767 and it contains the destination uri 767 command. 767 is a TEL URI class, so it does not match with the above URL. *Jul 11 06:06:30.119:vuri_match_class:tag (766)

The next dial peer, 766, contains the destination uri 766 command. Verify if the URL matches URI class 766. *Jul 11 06:06:30.119:vuri_match_class_sip:sip:[email protected] did not match pattern

The URL does not match with the pattern command. *Jul 11 06:06:30.119:vuri_match_class:tag (999)

The next dial peer, 999, contains the destination uri 999 command. *Jul 11 06:06:30.119:vuri_match_class_sip:Match with phone context *Jul 11 06:06:30.119:vuri_match_class_sip:input ()

If the phone context command is not configured, it is skipped. *Jul 11 06:06:30.119:vuri_match_class_sip:Match with host *Jul 11 06:06:30.119:vuri_match_class_sip:input (cisco.com)

If the host command is not configured under the class, it is skipped. *Jul 11 06:06:30.119:vuri_match_class_sip:Match with user-id *Jul 11 06:06:30.119:vuri_match_class_sip:input (driver)

If the user-id command is not configured, the user-id portion from the URL is “driver.” *Jul 11 06:06:30.119:vuri_match_class_sip:driver matched; match length (6)

There is a match with the configured pattern. The number of characters that matched is 6.


DB-2297


Related Commands

Command

Description

destination uri

Specifies the voice class used to match the dial peer to the destination URI for an outgoing call.

incoming uri

Specifies the voice class that a VoIP dial peer uses to match the URI of an incoming call.

show dialplan incall uri

Displays which dial peer is matched for a specific URI in an incoming call.

show dialplan uri

Displays which outbound dial peer is matched for a specific destination URI.

voice class uri

Creates or modifies a voice class for matching dial peers to a SIP or TEL URI.


DB-2298

May 2008

Debug Commands debug voice vofr

debug voice vofr To show Cisco trunk and FRF.11 trunk call setup attempts and to show which dial peer is used in the call setup, use the debug voice vofr command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voice vofr no debug voice vofr

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)XG


12.2SX


Usage Guidelines

This command applies to Cisco trunks and FRF.11 trunks only; it does not apply to switched calls. This command applies to VoFR, VoATM, and VoHDLC dial peers on the Cisco MC3810 device.

Examples

The following example shows sample output from the debug voice vofr command for a Cisco trunk: Router# debug voice vofr 1d05h: 1/1:VOFR, unconf ==> pending_start 1d05h: 1/1:VOFR,create VOFR 1d05h: 1/1:VOFR,search dial-peer 7100 preference 0 1d05h: 1/1:VOFR, pending_start ==> start 1d05h: 1/1:VOFR, 1d05h:voice_configure_perm_svc: 1d05h:dial-peer 7100 codec = G729A payload size = 30 vad = off dtmf relay = on seq num = off 1d05h:voice-port 1/1 codec = G729A payload size = 30 vad = off dtmf relay = on seq num = off 1d05h: 1/1:VOFR,SIGNAL-TYPE = cept 1d05h:init_frf11 tcid 0 master 0 signaltype 2 1d05h:Going Out Of Service on tcid 0 with sig state 0001 1d05h: 1/1:VOFR, start get event idle 1d05h: 1/1:VOFR, start get event 1d05h: 1/1:VOFR, start get event set up 1d05h: 1/1:VOFR, start ==> pending_connect 1d05h: 1/1:VOFR, pending_connect get event connect 1d05h: 1/1:VOFR, pending_connect ==> connect 1d05h: 1/1:VOFR,SIGNAL-TYPE = cept 1d05h:init_frf11 tcid 0 master 1 signaltype 2 1d05h:start_vofr_polling on port 0 signaltype 2


DB-2299

Debug Commands debug voice vofr

The following example shows sample output from the debug voice vofr command for an FRF.11 trunk: Router# debug voice vofr 1d05h: 1/1:VOFR,search dial-peer 7200 preference 2 1d05h: 1/1:VOFR,SIGNAL-TYPE = cept 1d05h:Launch Voice Trunk:signal-type 2 1d05h:calculated bandwidth = 10, coding = 6, size = 30 1d05h:%Voice-port 1/1 is down. 1d05h: 1/1:VOFR, pending_start get event idle 1d05h:Codec Type = 6 Payload Size = 30 Seq# off 1d05h:%Voice-port 1/1 is up. 1d05h:init_frf11 tcid 0 master 1 signaltype 2 1d05h:status OK :cid = 100 1d05h: 1/1:VOFR, 1d05h:start FRF11 1d05h: 1/1:VOFR, pending_start ==> frf11 1d05h: 1/1:VOFR,SIGNAL-TYPE = cept

Related Commands

Command

Description

debug ccfrf11 session


debug ccsip all


debug ccswvoice vofr-session


debug frame-relay fragment

Displays information related to Frame Relay fragmentation on a PVC.

debug vpm error

Displays the behavior of the Holst state machine.

debug vtsp port

Displays the behavior of the VTSP state machine.

debug vtsp vofr subframe



DB-2300

May 2008

Debug Commands debug voip aaa

debug voip aaa To enable debugging messages for gateway authentication, authorization, and accounting (AAA) to be sent to the system console, use the debug voip aaa command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip aaa no debug voip aaa

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2


12.2(2)XB

This command was implemented on the Cisco AS5850 in the Cisco IOS Release 12.2(2)XB.

12.2(11)T


12.2SX


Examples

The following is sample output from the debug voip aaa command: Router# debug voip aaa VoIP AAA debugging is enabled Router# show debug voip aaa: voip aaa debugging is on


DB-2301

Debug Commands debug voip ais

debug voip ais To enable debugging of the application information system (AIS) database, use the debug voip ais command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip ais no debug voip ais

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Examples

The following is sample output from the debug voip ais command: Router# debug voip ais voip AIS debugging is on Router# *Jul 18 22:18:30.947: ais_appinst_create_record: new app inst record is created for sid=10, app_name=generic, stats:avail, elog:avail *Jul 18 22:18:30.947: ais_appinst_insert_record_to_active: app inst sid=A is inserted to active tree *Jul 18 22:18:30.963: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au *Jul 18 22:18:30.963: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245 *Jul 18 22:18:30.963: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC) Router# *Jul 18 22:18:46.468: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au *Jul 18 22:18:46.468: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245 *Jul 18 22:18:46.468: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC) Router# *Jul 18 22:18:51.520: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au *Jul 18 22:18:51.520: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245 *Jul 18 22:18:51.520: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC) Router# *Jul 18 22:18:56.573: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au


DB-2302

May 2008

Debug Commands debug voip ais

*Jul 18 22:18:56.573: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245 *Jul 18 22:18:56.573: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC) Router# *Jul 18 22:19:01.625: ais_be_server_get_record_from_url: Incoming url = tftp://172.19.139.245/audio/ch_welcome.au *Jul 18 22:19:01.625: ais_be_server_get_record_from_url: Found server name or ip = 172.19.139.245 *Jul 18 22:19:01.625: ais_be_server_get_record_from_url: AIS BE server record located (6644ECCC) *Jul 18 22:19:01.949: propagate_history_stats: stats for app inst 10 is propagated to application (generic) and gateway level *Jul 18 22:19:01.949: ais_appinst_move_record_active_to_history: session record (sid=A) is moved to history repository

Related Commands

Command

Description

call application event-log

Enables event logging for voice application instances.

call application stats

Enables statistics collection for voice applications.

debug voip event-log

Enables debugging of the event log module.


DB-2303

Debug Commands debug voip application stcapp all

debug voip application stcapp all To display debugging information for the components of the SCCP Telephony Control Application (STCAPP), use the debug voip application stcapp all command in privileged EXEC mode. To disable debugging display, use the no form of this command. debug voip application stcapp all no debug voip application stcapp all

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.4(4)T

Command output was enhanced to display codec capabilities for modem transport.

12.2SX


Usage Guidelines

The debug voip application stcapp all command provides debugging output for all the STCAPP debug commands compiled into one display.

Examples

The following is sample output from the debug voip application stcapp all command showing device modem transport capability: Router# debug voip application stcapp all *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan

11 11 11 11 11 11 11 11 11 11 11 11 11

12:24:18.443: 12:24:18.443: 12:24:18.443: 12:24:18.443: 12:24:18.443: 12:24:18.443: 12:24:18.443: 12:24:18.443: 12:24:18.443: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447:

stcapp_start stcapp process started stcapp_init_symphony CCAPI successfully initialized stcapp_init_rtp stcapp_vp_shut stcapp_port_up_down RTP successfully brought in service stcapp_create_dcbs_from_dialpeers 1/1/0: stcapp_create_device 1/1/0: Endpoint base name generated->AN0D65D8DD40280 1/1/0: New dialpeer id: 999110 1/1/0: Analog device is ready to be registered

The following lines show the codec subtype, which indicates the modem transport method; 0=None, 1=V.150.1 (modem relay), and 2=VBD (modem pass-through): *Jan 11 12:24:18.447: 1/1/0:

reg caps including codec=5 (g711ulaw) subtype=2


DB-2304

May 2008


*Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan with *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan

11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 CM 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11

12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447: 12:24:18.447:

1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0: 1/1/0:

reg caps including codec=1 (g729ar8) subtype=2 reg caps including codec=5 (g711ulaw) subtype=1 reg caps including codec=1 (g729ar8) subtype=1 reg caps including codec=5 (g711ulaw) subtype=0 reg caps including codec=6 (g711alaw) subtype=0 reg caps including codec=1 (g729ar8) subtype=0 reg caps including codec=2 (g726r16) subtype=0 reg caps including codec=3 (g726r24) subtype=0 reg caps including codec=4 (g726r32) subtype=0 reg caps including codec=7 (g728) subtype=0 reg caps including codec=8 (g723r63) subtype=0 reg caps including codec=9 (g723r53) subtype=0 reg caps including codec=12 (g729br8) subtype=0 reg caps including codec=14 (g723ar63) subtype=0 reg caps including codec=15 (g723ar53) subtype=0 Device: AN0D65D8DD40280 Id: 7 successfully registered

12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.651: 12:24:18.651: 12:24:18.651: 12:24:18.651: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.455: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.647: 12:24:18.651: 12:24:18.651: 12:24:18.651: 12:24:18.651: 12:24:18.651:

==> Received event:STCAPP_DC_EV_DEVICE_REGISTER_DONE 1/1/0: Device State:OOS 1/1/0: stcapp_dev_default_eh 1/1/0: New State = INIT ==> Received event:STCAPP_DC_EV_DEVICE_CAP_REQ 1/1/0: Device State:INIT 1/1/0: stcapp_cap_req_eh 1/1/0: Sending dcDeviceHeadsetStatus for devID:7 1/1/0: Sending dcDeviceButtonTemplateReq for devID:7 1/1/0: No state change ==> Received event:STCAPP_DC_EV_DEVICE_BUTTON_TEMP_RES 1/1/0: Device State:INIT 1/1/0: stcapp_button_templ_res_eh 1/1/0: Sending dcDeviceLineStatReq for devID:7 1/1/0: No state change ==> Received event:STCAPP_DC_EV_DEVICE_FORWARD_STAT_RES 1/1/0: Device State:INIT 1/1/0: stcapp_forward_stat_res_eh 1/1/0: lineNumber: 1 1/1/0: forwardAllActive: 0 1/1/0: forwardBusyActive: 0 1/1/0: forwardNoAnswerActive: 0 1/1/0: ForwardAllDirNumber: 1/1/0: No state change ==> Received event:STCAPP_DC_EV_DEVICE_LINE_STAT_RES 1/1/0: Device State:INIT 1/1/0: stcapp_cap_req_eh 1/1/0: Sending dcDeviceHeadsetStatus for devID:7 1/1/0: Sending dcDeviceButtonTemplateReq for devID:7 1/1/0: No state change ==> Received event:STCAPP_DC_EV_DEVICE_BUTTON_TEMP_RES 1/1/0: Device State:INIT 1/1/0: stcapp_button_templ_res_eh 1/1/0: Sending dcDeviceLineStatReq for devID:7 1/1/0: No state change ==> Received event:STCAPP_DC_EV_DEVICE_FORWARD_STAT_RES 1/1/0: Device State:INIT 1/1/0: stcapp_forward_stat_res_eh 1/1/0: lineNumber: 1 1/1/0: forwardAllActive: 0 1/1/0: forwardBusyActive: 0 1/1/0: forwardNoAnswerActive: 0 1/1/0: ForwardAllDirNumber: 1/1/0: No state change ==> Received event:STCAPP_DC_EV_DEVICE_LINE_STAT_RES 1/1/0: Device State:INIT 1/1/0: stcapp_line_stat_eh


DB-2305


*Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan

11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11

12:24:18.651: 12:24:18.651: 12:24:18.651: 12:24:18.651: 12:24:18.651: 12:24:18.651: 12:24:18.823: 12:24:18.827: 12:24:18.827: 12:24:18.827: 12:24:18.827: 12:24:18.827: 12:24:18.827: 12:24:18.827: 12:24:18.827: 12:24:18.827: 12:24:18.827: 12:24:18.827:

1/1/0: lineNumber: 1 1/1/0: lineDirNumber: 5902 1/1/0: display name: 5902 1/1/0: Sending dcDeviceRegAvailableLines for devID:7 1/1/0: Sending dcDeviceDateTimeReq for devID:7 1/1/0: No state change ==> Received event:STCAPP_DC_EV_DEVICE_DEFINE_DATE_TIME_RES 1/1/0: Device State:INIT 1/1/0: stcapp_define_date_time_eh 1/1/0: New State = IS ==> Received event:STCAPP_DC_EV_DEVICE_DISPLAY_PROMPT_STATUS 1/1/0: Device State:IS 1/1/0: stcapp_display_prompt_status_eh 1/1/0: lineNumber: 0 1/1/0: call reference: 0 1/1/0: promptStatus: Your current options 1/1/0: device control type: 3 1/1/0: No state change

The following is sample output from the debug voip application stcapp all command during call setup. The following lines show the voice gateway beginning call setup: *Jan 9 06:48:06.947: ==> Received event:STCAPP_CC_EV_CALL_SETUP_IND (evId:CC_EV_CALL_SETUP_IND) for CallId: 5 *Jan 9 06:48:06.947: 1/0/0: Call State:IDLE *Jan 9 06:48:06.947: 1/0/0: stcapp_setup_ind_eh *Jan 9 06:48:06.947: 1/0/0: Acquired CCB 0x66F12558 for device id:4 *Jan 9 06:48:06.947: 1/0/0: Voice Setup: callID:5, vdb_ptr:66CA57B4

The voice gateway notifies the Cisco CallManager of the endpoint device (phone) in the offhook condition: *Jan 9 06:48:06.947: 1/0/0: *Jan 9 06:48:06.947: 1/0/0: *Jan 9 06:48:06.947: 1/0/0: *Jan 9 06:48:06.955: 1/0/0: STCAPP_DC_EV_DEVICE_SET_RINGER

Sending StationOffHook to CallManager Sending ccCallSetupAck to Symphony for voice call id:5 New State = OFFHOOK No line (line=0) found... most likely old Call Ref: event

The following lines show that the Cisco CallManager acknowledged the offhook condition: *Jan 9 06:48:06.955: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_OFFHOOK (evID:DC_EV_DEVICE_CALL_STATE_OFFHOOK) *Jan 9 06:48:06.955: 1/0/0: Call State:OFFHOOK *Jan 9 06:48:06.955: 1/0/0: stcapp_cs_offhook_eh *Jan 9 06:48:06.955: 1/0/0: No state change

The voice gateway receives the Cisco CallManager notification to send dial tone to the phone: *Jan 9 06:48:06.955: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE) *Jan 9 06:48:06.955: 1/0/0: Call State:OFFHOOK *Jan 9 06:48:06.955: 1/0/0: stcapp_start_tone_eh

The voice gateway generates dial tone and prepares to collect dialed digits: *Jan *Jan *Jan

9 06:48:06.955: 1/0/0: 9 06:48:06.955: 1/0/0: 9 06:48:06.955: 1/0/0:

Sending ccGenerateTone(8(0x8)) Sending ccCallReportDigits No state change


DB-2306

May 2008


Related Commands

Command

Description

debug voip application stcapp error

Displays STCAPP error log contents.

debug voip application stcapp events

Traces STCAPP call flow events.

debug voip application stcapp functions

Displays STCAPP entry and exit function calls for all voice ports.


Displays debugging information for the components of the STCAPP for a specified port.


DB-2307

Debug Commands debug voip application stcapp buffer-history

debug voip application stcapp buffer-history To enable event logging for SCCP Telephony Control Application (STCAPP) analog voice ports, use the debug voip application stcapp buffer-history command in privileged EXEC mode. To disable event logging, use the no form of this command. debug voip application stcapp buffer-history {all | port port} no debug voip application stcapp buffer-history {all | port port}

Syntax Description

all

Enables logging for all analog voice ports.

port port

Enables logging for only the specified analog voice port. Note

Port syntax is platform-dependent; type ? to determine.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(2)T


12.2SX


Usage Guidelines

This command enables logging of call flow events and device events, including registering and unregistering. You can use the event log to help troubleshoot performance problems and isolate faults related to analog endpoints. To display the records in the event log, use the show sctapp buffer-history command. A maximum of 2000 records are saved for each analog port. The event log uses a circular buffer that stores the 2000 most recent records. To clear the buffer, you can disable logging with the no debug voip application stcapp buffer-history command. The event log uses approximately 64 KB of memory for each port, or approximately 1.5 MB of memory if logging is enabled for all 24 ports.

Note

Examples

The debug voip application stcapp all command has no impact on event logging. Enabling or disabling STCAPP debug output is separate from the event logging feature.

The following example enables event logging for analog port 2/3. To display the events, you must use the show sctapp buffer-history command. Router# debug voip application stcapp buffer-history port 2/3 stcapp buffer-history logging for port 2/3 is on


DB-2308

May 2008

Debug Commands debug voip application stcapp buffer-history

Related Commands

Command

Description


Displays debug output for all the debug commands for the STCAPP compiled into one display.








Displays STCAPP debug output for a specific port.

show stcapp buffer-history

Displays event logs for STCAPP analog voice ports.


DB-2309

Debug Commands debug voip application stcapp error

debug voip application stcapp error To troubleshoot the SCCP Telephony Control Application (STCAPP) error log contents, use the debug voip application stcapp error command in privileged EXEC mode. To disable STCAPP error debugging, use the no form of this command. debug voip application stcapp error no debug voip application stcapp error

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Usage Guidelines

The debug voip application stcapp error command traces application error logs. STCAPP error logs are generated during normal call processing, when there are insufficient resources, or when there are problems in the underlying application code. This command shows error events or unexpected behavior in system software. Usually no events are generated.

Examples

The following example shows the error log contents when STCAPP debugging is enabled: Router# debug voip application stcapp error STCAPP error debugging is on Router# *Jan 9 06:54:07.583: stcapp_process_queue_events:ERROR:STCAPP_DCB_ACCESS_ERR from state machine

Related Commands

Command

Description








Displays debug information for the components of the STCAPP for a specified port.


DB-2310

May 2008

Debug Commands debug voip application stcapp events

debug voip application stcapp events To trace SCCP Telephony Control Application (STCAPP) call flow events, use the debug voip application stcapp events command in privileged EXEC mode. To disable STCAPP event call traces, use the no form of this command. debug voip application stcapp events no debug voip application stcapp events

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Usage Guidelines

Use this command to debug call flow events for all ports controlled by the STCAPP.

Examples

The following example displays call teardown and disconnect events: Router# debug voip application stcapp events

The following lines show the application running on the voice gateway receiving notice to stop dial tone generation, following the onhook condition of the endpoint device (phone): *Jan 9 06:48:55.011: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE) *Jan 9 06:48:55.011: 1/0/1: Call State:REM_ONHOOK_PEND *Jan 9 06:48:55.011: 1/0/1: stcapp_stop_tone_eh *Jan 9 06:48:55.011: 1/0/1: Sending ccGenerateTone(NULL) *Jan 9 06:48:55.015: 1/0/1: No state change

The application takes no additional action to process the uninteresting event. *Jan 9 06:48:55.015: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE) *Jan 9 06:48:55.015: 1/0/1: Call State:REM_ONHOOK_PEND *Jan 9 06:48:55.015: 1/0/1: Uninteresting event

The application receives the call disconnect notice and proceeds to tear down the telephony call leg. *Jan 9 06:48:58.903: ==> Received event:STCAPP_CC_EV_CALL_DISCONNECTED (evId:CC_EV_CALL_DISCONNECTED) for CallId: 6 *Jan 9 06:48:58.903: 1/0/1: Call State:REM_ONHOOK_PEND *Jan 9 06:48:58.903: 1/0/1: stcapp_loc_onhook_eh *Jan 9 06:48:58.903: 1/0/1: Sending StationOnHook to CallManager


DB-2311

Debug Commands debug voip application stcapp events

*Jan *Jan *Jan *Jan *Jan *Jan *Jan *Jan

Related Commands

9 9 9 9 9 9 9 9

06:48:58.903: 06:48:58.903: 06:48:58.903: 06:48:58.903: 06:48:58.903: 06:48:58.903: 06:48:58.903: 06:48:58.903:

1/0/1: stcapp_call_cleanup 1/0/1: stcapp_set_ring_mode 1/0/1: SCCP ring mode:1 1/0/1: Invoking Feature:33. Mode:0 for callid:6 1/0/1: stcapp_disconnect_call_leg 1/0/1: Sending ccCallDisconnect for call id:6 1/0/1: CCB 0x65CF3EC4 unlinked 1/0/1: New State = IDLE

Command

Description










DB-2312

May 2008

Debug Commands debug voip application stcapp functions

debug voip application stcapp functions To debug SCCP Telephony Control Application (STCAPP) functions, use the debug voip application stcapp functions command in privileged EXEC mode. To disable STCAPP function debugging, use the no form of this command. debug voip application stcapp functions no debug voip application stcapp functions

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Usage Guidelines

Use this command to display STCAPP entry and exit function calls for all voice ports.

Examples

The following example displays function calls for STCAPP ports 1/0/0 and 1/0/1: Router# debug voip application stcapp functions STCAPP function debugging is *Jan 9 06:55:27.583: 1/0/0: *Jan 9 06:55:27.591: 1/0/0: *Jan 9 06:55:27.591: 1/0/0: *Jan 9 06:55:27.591: 1/0/0: *Jan 9 06:55:28.923: 1/0/0: *Jan 9 06:55:28.927: 1/0/0: *Jan 9 06:55:29.063: 1/0/0: *Jan 9 06:55:29.203: 1/0/0: *Jan 9 06:55:29.343: 1/0/0: *Jan 9 06:55:29.355: 1/0/0: *Jan 9 06:55:29.359: 1/0/0: *Jan 9 06:55:29.359: 1/0/0: *Jan 9 06:55:29.359: 1/0/0: *Jan 9 06:55:29.359: 1/0/1: *Jan 9 06:55:29.359: 1/0/1:

on stcapp_setup_ind_eh stcapp_cs_offhook_eh stcapp_start_tone_eh stcapp_report_digits_done_eh stcapp_digit_end_eh stcapp_stop_tone_eh stcapp_digit_end_eh stcapp_digit_end_eh stcapp_digit_end_eh stcapp_cs_proceed_eh stcapp_proceed_call_info_eh stcapp_start_tone_eh stcapp_proceed_call_info_eh stcapp_cs_ringin_eh stcapp_call_info_eh


DB-2313

Debug Commands debug voip application stcapp functions

Related Commands

Command

Description










DB-2314

May 2008

Debug Commands debug voip application stcapp port

debug voip application stcapp port To enable SCCP Telephony Control Application (STCAPP) debugging for a specific port, use the debug voip application stcapp port command in privileged EXEC mode. To disable specific STCAPP port debugging, use the no form of this command. debug voip application stcapp port port-number no debug voip application stcapp port port-number

Syntax Description

port-number

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.4(4)T

Command output was enhanced to display the modem transport method.

12.2SX


Number of the port on the interface. See the appropriate platform manual or online help for port numbers on your networking device.

Usage Guidelines

Use this command to display debugging information for the components of the STCAPP for a specific port.

Examples

The following example displays information on a modem-relay call: Router# debug voip application stcapp port 1/1/0

*Jan 11 12:37:48.631: ==> Received event:STCAPP_CC_EV_CALL_SETUP_IND (evId:CC_EV_CALL_SETUP_IND) for CallId: 326 *Jan 11 12:37:48.631: 1/1/0: Call State:IDLE *Jan 11 12:37:48.631: 1/1/0: stcapp_setup_ind_eh *Jan 11 12:37:48.631: 1/1/0: stcapp_get_ccb *Jan 11 12:37:48.631: 1/1/0: dcb->lcb[line_inst - 1].num_ccbs=0 *Jan 11 12:37:48.631: 1/1/0: Acquired CCB 0x65D932B8 for device id:7 *Jan 11 12:37:48.631: 1/1/0: num_ccbs++, num_ccbs=1 *Jan 11 12:37:48.631: 1/1/0: Voice Setup: callID:326, vdb_ptr:666581AC *Jan 11 12:37:48.631: 1/1/0: Sending StationOffHook to CallManager *Jan 11 12:37:48.631: 1/1/0: Sending ccCallSetupAck to Symphony for voice call id:326 *Jan 11 12:37:48.631: 1/1/0: New State = OFFHOOK *Jan 11 12:37:48.643: 1/1/0: No line (line=0) found... most likely old Call Ref: event STCAPP_DC_EV_DEVICE_SET_RINGER *Jan 11 12:37:48.643: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_OFFHOOK (evID:DC_EV_DEVICE_CALL_STATE_OFFHOOK) *Jan 11 12:37:48.643: 1/1/0: Call State:OFFHOOK


DB-2315


*Jan 11 12:37:48.643: 1/1/0: stcapp_cs_offhook_eh *Jan 11 12:37:48.643: 1/1/0: call_ref=16777250 *Jan 11 12:37:48.643: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:48.643: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:48.643: 1/1/0: Using call_ref 0 to get ccb=0x65D932B8 *Jan 11 12:37:48.643: 1/1/0: No state change *Jan 11 12:37:48.643: ==> Received event:STCAPP_DC_EV_DEVICE_DISPLAY_PROMPT_STATUS *Jan 11 12:37:48.643: 1/1/0: Device State:IS *Jan 11 12:37:48.643: 1/1/0: stcapp_display_prompt_status_eh *Jan 11 12:37:48.643: 1/1/0: lineNumber: 1 *Jan 11 12:37:48.643: 1/1/0: call reference: 16777250 *Jan 11 12:37:48.643: 1/1/0: promptStatus: Enter Number *Jan 11 12:37:48.643: 1/1/0: No state change *Jan 11 12:37:48.643: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE) *Jan 11 12:37:48.643: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:48.643: 1/1/0: stcapp_start_tone_eh *Jan 11 12:37:48.643: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:48.643: 1/1/0: call_ref=16777250, ccb=0x65D932B8, tone=8(0x8) *Jan 11 12:37:48.643: 1/1/0: Sending ccGenerateTone(8(0x8)) *Jan 11 12:37:48.643: 1/1/0: Sending ccCallReportDigits *Jan 11 12:37:48.643: 1/1/0: No state change *Jan 11 12:37:48.643: ==> Received event:STCAPP_CC_EV_CALL_REPORT_DIGITS_DONE (evId:CC_EV_CALL_REPORT_DIGITS_DONE) for CallId: 326 *Jan 11 12:37:48.647: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:48.647: 1/1/0: stcapp_report_digits_done_eh *Jan 11 12:37:48.647: 1/1/0: No state change *Jan 11 12:37:52.643: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_BEGIN (evId:CC_EV_CALL_DIGIT_BEGIN) for CallId: 326 *Jan 11 12:37:52.643: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:52.643: 1/1/0: Uninteresting event *Jan 11 12:37:52.683: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_END (evId:CC_EV_CALL_DIGIT_END) for CallId: 326 *Jan 11 12:37:52.683: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:52.683: 1/1/0: stcapp_digit_end_eh *Jan 11 12:37:52.683: 1/1/0: Digit received is (5) *Jan 11 12:37:52.683: 1/1/0: Sending StationKeypadButton(5) to CallManager *Jan 11 12:37:52.683: 1/1/0: No state change *Jan 11 12:37:52.687: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE) *Jan 11 12:37:52.687: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:52.687: 1/1/0: stcapp_stop_tone_eh *Jan 11 12:37:52.687: 1/1/0: call_ref=16777250 *Jan 11 12:37:52.687: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:52.687: 1/1/0: Sending ccGenerateTone(NULL) *Jan 11 12:37:52.687: 1/1/0: No state change *Jan 11 12:37:52.775: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_BEGIN (evId:CC_EV_CALL_DIGIT_BEGIN) for CallId: 326 *Jan 11 12:37:52.775: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:52.775: 1/1/0: Uninteresting event *Jan 11 12:37:52.823: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_END (evId:CC_EV_CALL_DIGIT_END) for CallId: 326 *Jan 11 12:37:52.823: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:52.823: 1/1/0: stcapp_digit_end_eh *Jan 11 12:37:52.823: 1/1/0: Digit received is (8) *Jan 11 12:37:52.823: 1/1/0: Sending StationKeypadButton(8) to CallManager *Jan 11 12:37:52.823: 1/1/0: No state change *Jan 11 12:37:52.923: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_BEGIN (evId:CC_EV_CALL_DIGIT_BEGIN) for CallId: 326 *Jan 11 12:37:52.923: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:52.923: 1/1/0: Uninteresting event *Jan 11 12:37:52.963: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_END (evId:CC_EV_CALL_DIGIT_END) for CallId: 326 *Jan 11 12:37:52.963: 1/1/0: Call State:OFFHOOK


DB-2316

May 2008


*Jan 11 12:37:52.963: 1/1/0: stcapp_digit_end_eh *Jan 11 12:37:52.963: 1/1/0: Digit received is (0) *Jan 11 12:37:52.963: 1/1/0: Sending StationKeypadButton(0) to CallManager *Jan 11 12:37:52.963: 1/1/0: No state change *Jan 11 12:37:53.063: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_BEGIN (evId:CC_EV_CALL_DIGIT_BEGIN) for CallId: 326 *Jan 11 12:37:53.063: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:53.063: 1/1/0: Uninteresting event *Jan 11 12:37:53.103: ==> Received event:STCAPP_CC_EV_CALL_DIGIT_END (evId:CC_EV_CALL_DIGIT_END) for CallId: 326 *Jan 11 12:37:53.103: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:53.103: 1/1/0: stcapp_digit_end_eh *Jan 11 12:37:53.103: 1/1/0: Digit received is (2) *Jan 11 12:37:53.103: 1/1/0: Sending StationKeypadButton(2) to CallManager *Jan 11 12:37:53.103: 1/1/0: No state change *Jan 11 12:37:53.235: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_PROCEED (evID:DC_EV_DEVICE_CALL_STATE_PROCEED) *Jan 11 12:37:53.235: 1/1/0: Call State:OFFHOOK *Jan 11 12:37:53.235: 1/1/0: stcapp_cs_proceed_eh *Jan 11 12:37:53.235: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:53.235: 1/1/0: Sending ccCallProceeding for voice call id:326 *Jan 11 12:37:53.235: 1/1/0: Stopping the initial and inter digit timer! *Jan 11 12:37:53.235: 1/1/0: New State = PROCEEDING *Jan 11 12:37:53.235: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO) *Jan 11 12:37:53.235: 1/1/0: Call State:PROCEEDING *Jan 11 12:37:53.235: 1/1/0: stcapp_proceed_call_info_eh *Jan 11 12:37:53.235: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:53.239: 1/1/0: No state change *Jan 11 12:37:53.239: ==> Received event:STCAPP_DC_EV_DEVICE_START_TONE (evID:DC_EV_DEVICE_START_TONE) *Jan 11 12:37:53.239: 1/1/0: Call State:PROCEEDING *Jan 11 12:37:53.239: 1/1/0: stcapp_start_tone_eh *Jan 11 12:37:53.239: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:53.239: 1/1/0: call_ref=16777250, ccb=0x65D932B8, tone=1(0x1) *Jan 11 12:37:53.239: 1/1/0: Sending ccCallAlert(signal:1) for voice call id:326 *Jan 11 12:37:53.239: 1/1/0: No state change *Jan 11 12:37:53.239: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_RINGOUT (evID:DC_EV_DEVICE_CALL_STATE_RINGOUT) *Jan 11 12:37:53.239: 1/1/0: Call State:PROCEEDING *Jan 11 12:37:53.239: 1/1/0: stcapp_set_call_state_eh *Jan 11 12:37:53.239: 1/1/0: call_ref=16777250, call_state=2 *Jan 11 12:37:53.239: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:53.239: 1/1/0: No state change *Jan 11 12:37:53.239: ==> Received event:STCAPP_DC_EV_DEVICE_DISPLAY_PROMPT_STATUS *Jan 11 12:37:53.239: 1/1/0: Device State:IS *Jan 11 12:37:53.239: 1/1/0: stcapp_display_prompt_status_eh *Jan 11 12:37:53.239: 1/1/0: lineNumber: 1 *Jan 11 12:37:53.239: 1/1/0: call reference: 16777250 *Jan 11 12:37:53.239: 1/1/0: promptStatus: Ring Out *Jan 11 12:37:53.239: 1/1/0: No state change *Jan 11 12:37:53.239: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO) *Jan 11 12:37:53.239: 1/1/0: Call State:PROCEEDING *Jan 11 12:37:53.239: 1/1/0: stcapp_proceed_call_info_eh *Jan 11 12:37:53.239: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:53.239: 1/1/0: No state change *Jan 11 12:37:56.635: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE) *Jan 11 12:37:56.635: 1/1/0: Call State:PROCEEDING *Jan 11 12:37:56.635: 1/1/0: stcapp_stop_tone_eh *Jan 11 12:37:56.635: 1/1/0: call_ref=16777250 *Jan 11 12:37:56.635: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:56.639: 1/1/0: Sending ccGenerateTone(NULL)


DB-2317


*Jan 11 12:37:56.639: 1/1/0: No state change *Jan 11 12:37:56.639: ==> Received event:STCAPP_DC_EV_MEDIA_OPEN_RCV_CHNL (evID:DC_EV_MEDIA_OPEN_RCV_CHNL) *Jan 11 12:37:56.639: 1/1/0: Call State:PROCEEDING *Jan 11 12:37:56.639: 1/1/0: stcapp_open_rcv_chnl_eh *Jan 11 12:37:56.639: 1/1/0: call_ref=16777250 *Jan 11 12:37:56.639: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:56.639: 1/1/0: stcapp_set_up_voip_leg *Jan 11 12:37:56.639: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:56.639: 1/1/0: Codec: 5 ptime :20, codecbytes: 160

The following line indicates the modem transport method that will be used: *Jan 11 12:37:56.639: 1/1/0:

CCM directive -> enabling modem relay

The following lines show modem-relay parameters: *Jan 11 12:37:56.639: 1/1/0: MR parms: sprt_retries=10, sprt_latency=250, sprt_rx_v14_pb_hold_time=32, sprt_tx_v14_hold_time=12, sprt_tx_v14_hold_count=22, gw_xid=1, dictsize=1024, stringlen=16, compressdir=3, sse_red_interval=16, sse_red_pkt_count=2, sse_t1=2100, sse_retries=5 *Jan 11 12:37:56.639: 1/1/0: Info provided to RTPSPI - sess_mode 2, desired_qos 0, codec 5, pkt_period 20, lr_port 17180 *Jan 11 12:37:56.639: 1/1/0: Sending ccIFCallSetupRequest for voip leg *Jan 11 12:37:56.639: 1/1/0: ccIFCallSetRequest returned voip call id:327 *Jan 11 12:37:56.639: 1/1/0: Sending dcDeviceOpenReceiveChannelAck *Jan 11 12:37:56.639: 1/1/0: ORChnlAck Info: codec:5, loc_port:17180, chnl_id:16777521 *Jan 11 12:37:56.639: 1/1/0: New State = CONNECTING *Jan 11 12:37:56.643: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_CONNECTED (evID:DC_EV_DEVICE_CALL_STATE_CONNECTED) *Jan 11 12:37:56.643: 1/1/0: Call State:CONNECTING *Jan 11 12:37:56.643: 1/1/0: stcapp_set_call_state_eh *Jan 11 12:37:56.643: 1/1/0: call_ref=16777250, call_state=6 *Jan 11 12:37:56.643: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:56.643: 1/1/0: No state change *Jan 11 12:37:56.643: ==> Received event:STCAPP_DC_EV_DEVICE_DISPLAY_PROMPT_STATUS *Jan 11 12:37:56.643: 1/1/0: Device State:IS *Jan 11 12:37:56.643: 1/1/0: stcapp_display_prompt_status_eh *Jan 11 12:37:56.643: 1/1/0: lineNumber: 1 *Jan 11 12:37:56.643: 1/1/0: call reference: 16777250 *Jan 11 12:37:56.643: 1/1/0: promptStatus: Connected *Jan 11 12:37:56.643: 1/1/0: No state change *Jan 11 12:37:56.643: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO) *Jan 11 12:37:56.643: 1/1/0: Call State:CONNECTING *Jan 11 12:37:56.643: 1/1/0: stcapp_conn_call_info_eh *Jan 11 12:37:56.647: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:56.647: 1/1/0: stcapp_call_info_eh::caller_name= *Jan 11 12:37:56.647: 1/1/0: Irrelevant CALL_INFO message is ignore! *Jan 11 12:37:56.647: 1/1/0: No state change *Jan 11 12:37:56.647: ==> Received event:STCAPP_DC_EV_DEVICE_STOP_TONE (evID:DC_EV_DEVICE_STOP_TONE) *Jan 11 12:37:56.647: 1/1/0: Call State:CONNECTING *Jan 11 12:37:56.647: 1/1/0: stcapp_stop_tone_eh *Jan 11 12:37:56.647: 1/1/0: call_ref=16777250 *Jan 11 12:37:56.647: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:56.647: 1/1/0: Sending ccGenerateTone(NULL) *Jan 11 12:37:56.647: 1/1/0: No state change *Jan 11 12:37:56.647: ==> Received event:STCAPP_DC_EV_MEDIA_OPEN_XMT_CHNL (evID:DC_EV_MEDIA_OPEN_XMT_CHNL) *Jan 11 12:37:56.647: 1/1/0: Call State:CONNECTING *Jan 11 12:37:56.647: 1/1/0: stcapp_start_media_eh *Jan 11 12:37:56.647: 1/1/0: call_ref=16777250


DB-2318

May 2008


*Jan 11 12:37:56.647: 1/1/0: stcapp_get_ccb_ptr *Jan 11 12:37:56.647: 1/1/0: New State = ACTIVE_PENDING *Jan 11 12:37:56.647: ==> Received event:STCAPP_CC_EV_CALL_CONNECTED (evId:CC_EV_CALL_CONNECTED) for CallId: 327 *Jan 11 12:37:56.647: 1/1/0: Call State:ACTIVE_PENDING *Jan 11 12:37:56.647: 1/1/0: stcapp_call_connected_eh *Jan 11 12:37:56.647: 1/1/0: stcapp_create_conference *Jan 11 12:37:56.647: 1/1/0: Sending ccConferenceCreate to Symphony *Jan 11 12:37:56.651: 1/1/0: Conference created. voice call id:326, voip call id:327 *Jan 11 12:37:56.651: 1/1/0: No state change *Jan 11 12:37:56.651: ==> Received event:STCAPP_CC_EV_CONF_CREATE_DONE (evId:CC_EV_CONF_CREATE_DONE) for CallId: 326 *Jan 11 12:37:56.651: 1/1/0: Call State:ACTIVE_PENDING *Jan 11 12:37:56.651: 1/1/0: stcapp_active_pending_eh *Jan 11 12:37:56.651: 1/1/0: Sending ccCallModify for voice call id:326 *Jan 11 12:37:56.651: 1/1/0: codec=5, vad=0 *Jan 11 12:37:56.651: 1/1/0: Stopping the initial and inter digit timer! *Jan 11 12:37:56.651: 1/1/0: Sending ccCallModify for voip call id:327 *Jan 11 12:37:56.651: 1/1/0: Updated SMT info to RTPSPI - sess_mode:3,desired_qos:0, codec:5, pkt_period:20,rem_port:18968 vad:0 ip_tos:4 *Jan 11 12:37:56.655: 1/1/0: No state change *Jan 11 12:37:56.655: ==> Received event:STCAPP_CC_EV_VOICE_MODE_DONE (evId:CC_EV_VOICE_MODE_DONE) for CallId: 326 *Jan 11 12:37:56.655: 1/1/0: Call State:ACTIVE_PENDING *Jan 11 12:37:56.655: 1/1/0: Uninteresting event *Jan 11 12:37:56.655: ==> Received event:STCAPP_CC_EV_CALL_REPORT_DIGITS_DONE (evId:CC_EV_CALL_REPORT_DIGITS_DONE) for CallId: 326 *Jan 11 12:37:56.655: 1/1/0: Call State:ACTIVE_PENDING *Jan 11 12:37:56.655: 1/1/0: Uninteresting event *Jan 11 12:37:56.655: ==> Received event:STCAPP_CC_EV_CALL_MODIFY_DONE (evId:CC_EV_CALL_MODIFY_DONE) for CallId: 326 *Jan 11 12:37:56.655: 1/1/0: Call State:ACTIVE_PENDING *Jan 11 12:37:56.655: 1/1/0: stcapp_default_eh *Jan 11 12:37:56.655: 1/1/0: call_ref=0, call_state=0 *Jan 11 12:37:56.655: 1/1/0: New State = ACTIVE *Jan 11 12:37:56.655: ==> Received event:STCAPP_CC_EV_CALL_MODIFY_DONE (evId:CC_EV_CALL_MODIFY_DONE) for CallId: 327 *Jan 11 12:37:56.655: 1/1/0: Call State:ACTIVE *Jan 11 12:37:56.655: 1/1/0: Uninteresting event *Jan 11 12:37:59.963: ==> Received event:STCAPP_CC_EV_CALL_FEATURE_OFFHOOK (evId:CC_EV_CALL_FEATURE) for CallId: 326 *Jan 11 12:37:59.963: 1/1/0: Call State:ACTIVE *Jan 11 12:37:59.963: 1/1/0: stcapp_call_feature_eh *Jan 11 12:37:59.963: 1/1/0: lcb->num_ccbs = 1 *Jan 11 12:37:59.963: 1/1/0: No CC_FEATURE match! *Jan 11 12:37:59.967: 1/1/0: No state change... call remaining

The following example displays information on STCAPP controlled foreign exchange station (FXS) port 1/0/1 during call setup: Router# debug voip application stcapp port 1/0/1 stcapp port debugging is on

The following lines show the voice gateway receiving notification from the Cisco CallManager of an incoming call: *Jan 9 06:57:24.403: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_STATE_RINGIN (evID:DC_EV_DEVICE_CALL_STATE_RINGIN) *Jan 9 06:57:24.403: 1/0/1: Call State:IDLE *Jan 9 06:57:24.403: 1/0/1: stcapp_cs_ringin_eh *Jan 9 06:57:24.407: 1/0/1: Acquired CCB 0x66C0A428 for device id:3


DB-2319


The next lines show the new call processing state for the port: *Jan 9 06:57:24.407: 1/0/1: New State = RINGIN *Jan 9 06:57:24.407: ==> Received event:STCAPP_DC_EV_DEVICE_CALL_INFO (evID:DC_EV_DEVICE_CALL_INFO) *Jan 9 06:57:24.407: 1/0/1: Call State:RINGIN *Jan 9 06:57:24.407: 1/0/1: stcapp_call_info_eh

The next lines show the application sending a call setup request for the telephony leg: *Jan 9 06:57:24.407: *Jan 9 06:57:24.407: *Jan 9 06:57:24.407: CdPN:7702CgPN:7701 *Jan 9 06:57:24.407:

1/0/1: stcapp_set_up_voice_leg 1/0/1: Sending ccIFCallSetupRequest for voice leg 1/0/1: ccIFCallSetRequest returned voice call id:22. 1/0/1:

No state change

The next lines show the application invoking the ringing state: *Jan 9 06:57:24.407: ==> Received event:STCAPP_DC_EV_DEVICE_SET_RINGER (evID:DC_EV_DEVICE_SET_RINGER) *Jan 9 06:57:24.407: 1/0/1: Call State:RINGIN *Jan 9 06:57:24.407: 1/0/1: stcapp_set_ringer_eh *Jan 9 06:57:24.407: 1/0/1: stcapp_set_ring_mode *Jan 9 06:57:24.407: 1/0/1: SCCP ring mode:2 *Jan 9 06:57:24.407: 1/0/1: Invoking Feature:12. Mode:0 for callid:22 *Jan 9 06:57:24.407: 1/0/1: No state change

Related Commands

Command

Description










DB-2320

May 2008

Debug Commands debug voip application

debug voip application To display all application debug messages, use the debug voip application command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip application [accounting | all | callfeature | callsetup | core | datastruct | digitcollect | error | linking | media [packet | state] | oodrefer | redirect | script | session | settlement | states | supplementary-service | tclcommands] no debug voip application [accounting | all | callfeature | callsetup | core | datastruct | digitcollect | error | linking | media [packet | state] | oodrefer | redirect | script | session | settlement | states | supplementary-service | tclcommands]

Syntax Description

Command Modes

accounting

(Optional) Displays Voice over IP (VoIP) accounting messages.

all

(Optional) Displays all application debug messages.

callfeature

(Optional) Displays call feature debugs.

callsetup

(Optional) Displays the call setup being processed.

core

(Optional) Displays debug messages for the Application Framework (AFW) core libraries.

datastruct

(Optional) Displays debug messages for AFW data structures.

digitcollect

(Optional) Displays digits collected during the call.

error

(Optional) Displays application errors.

linking

(Optional) Displays script linking debugs.

media

(Optional) Displays debug traces for application media events.

oodrefer

(Optional) Displays debug messages for the Out-of-Dialog REFER (OOD-R) feature.

redirect

(Optional) Displays call redirection handler debugs.

script

(Optional) Displays script debugs.

session

(Optional) Displays default session application debugs.

settlement

(Optional) Displays debug messages for application settlement activities.

states

(Optional) Displays debug traces for application states.

supplementary-service

(Optional) Provides application layer tracing related to the processing of supplementary services requests.

tclcommands

(Optional) Displays debug messages for Tool Command Language (Tcl) commands used in application scripts.

Privileged EXEC


DB-2321


Command History

Usage Guidelines

Release

Modification

12.2(15)ZJT


12.3(4)T

This command was integrated into Cisco IOS Release 12.3(4)T. This command replaces the debug voip ivr applib, debug voip ivr callsetup, debug voip ivr digitcollect, debug voip ivr redirect, and debug voip ivr supplementary-service commands.

12.3(7)T

Reporting of H.450 capabilities was introduced.

12.4(4)T

The callfeature keyword was added.

12.4(4)XC

The accounting keyword was added.

12.4(9)T

The accounting keyword was integrated into Cisco IOS Release 12.4(9)T

12.4(11)XJ

The oodrefer keyword was added.

12.4(15)T

The oodrefer keyword was integrated into Cisco IOS Release 12.4(15)T.

12.2SX


If you do not use any keywords, the debug voip application command displays application programming interface (API) libraries being processed. The debug voip application all command differs from the debug voip ivr all command. The debug voip application all command enables all application framework debugs. The debug voip ivr all command enables both Application Framework Session debugs and interactive voice response (IVR) debugs.

Examples

The following is sample output from the debug voip application callsetup command: Router# debug voip application callsetup ivr call setup debugging is on Router# *Mar 7 22:08:40.032://7//APPL:/afsSettlementValidateCall:target=, tokenp=0x0 *Mar 7 22:08:41.864://-1//PCM :LP:HN23A698CC:HN23A691A4:/InitiateCallSetup:Mode 1 RedirectMode 6 Incoming leg[-1] AlertTime -1 Destinations(1) [ 405 ] *Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/InitiateCallSetup:Destination 0 guid :231D511B.1A5F11CC.800BB191.E9DE175D *Mar 7 22:08:41.868: incoming_guid :00000000.00000000.00000000.00000000 *Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNInitiate:Destination[405] *Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNMatchDialPeer: *Mar 7 22:08:41.868: src carrier id:, tgt carrier id: *Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNQueuePeers:Matched peers(1) *Mar 7 22:08:41.868://-1//PCM :HN23A698D0:/DNSetupPeer: Destination 0x6221092C *Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSetupPeer:dialpeer tags for Rotary = 400 *Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSetupPeer: *Mar 7 22:08:41.872:Destination SetupPeer cid(-1), destPat(405), match(2), prefix(), peer(630D95B0) *Mar 7 22:08:41.872://-1//PCM :HN23A698D0:/DNSettlementMatrixCheck:retcode=1 cid(-1) trans=0x0, provider=0 No settle-call present *Mar 7 22:08:41.940://8//PCM :/DNHandler:(DN_SETTING[2])--(CC_EV_CALL_PROCEEDING[25])--IGNORED-->>(DN_SETTING[2]) *Mar 7 22:08:41.940://8//PCM :/CS_Setting_PROCEED:


DB-2322

May 2008


*Mar 7 22:08:41.940://8//PCM :/CSPopLegAndWait: *Mar 7 22:08:41.940://8//PCM :/CallSetupHandler:(CS_SETTING[0]) -----(CS_EV_PROCEEDING[3])------->>>(CS_SETTING[0]) *Mar 7 22:08:41.948://-1//PCM :HN23A698CC:/CSInterceptEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING) *Mar 7 22:08:41.948://8//PCM :/CSInterceptEvent:(CS_SETTING[0]) intercepting CS_EV_PROGRESS leg 8 (Mask=12) *Mar 7 22:08:41.948://-1//PCM :HN23A698CC:/CSInterceptEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING) *Mar 7 22:08:41.952://-1//PCM :HN23A698CC:/CallSetupContinueEvent:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_SETTING) *Mar 7 22:08:41.956://8//PCM :/CS_CutProgress: *Mar 7 22:08:41.956://8//PCM :/CSPopLegAndWait: *Mar 7 22:08:41.956://8//PCM :/CallSetupContinueEvent:(CS_SETTING[0]) -----(CS_EV_PROGRESS[15])------->>>(CS_CONFEDALERT[5]) *Mar 7 22:08:41.956://-1//PCM :HN23A698CC:/CallSetupHandleQueueEvents: *Mar 7 22:08:41.956://8//PCM :/CallSetupContinueEvent: *** Leaving function ***CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_CONFEDALERT) *Mar 7 22:08:43.864://8//PCM :/CS_ConfedAlert_CONNECTED:no of Destinations:1 *Mar 7 22:08:43.864://-1//PCM :HN23A698CC:/CSDiscReturnAndEmptyLegALL: *Mar 7 22:08:43.864://8//PCM :/CSPopLegAndWait: *Mar 7 22:08:43.864://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup[0x6320B998] handlercount=1 Waits=1 #Objects=2 (CS_CONFED) *Mar 7 22:08:43.864:CallSetupDump:CallSetup[0x6320B998] State:CS_CONFED[3] #Handler=1 #Waits=1#Objects=2 *Mar 7 22:08:43.864:All Destinations: *Mar 7 22:08:43.864:DestinationDump:Destination[0x6221092C]:DN_SETTING[2] Holding[0] Leg[8] *Mar 7 22:08:43.864:settlement_in_use:0 settlement_transaction:0x0 settlement_provider:0 settlement_type:0 settlement_callvalid:1 busyRotary:0 *Mar 7 22:08:43.864:WaitList of Destinations:{HAN[DN_HAND ][CS_HAND ]( )} *Mar 7 22:08:43.868:Handler Tree{HAN[CS_HAND ][AFS_HAND]( HAN[DN_HAND][CS_HAND ][FALSE] [UC=1 ]LEG[8 ][CS_HAND ][LEG_OUTCONNECTED(8)][Cause(0)][UC=1 ])} *Mar 7 22:08:43.868:{HAN[DN_HAND ][CS_HAND ]( )} *Mar 7 22:08:43.868: *Mar 7 22:08:43.868:Handler Tree Trace *Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNCleanup:Terminate=TRUE Status DN_SUCCESS Leg[8] *Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNSettlementCleanup:cid(-1) trans=0x0, provider=0 *Mar 7 22:08:43.868://-1//PCM :HN23A698D0:/DNSetFree: *Mar 7 22:08:43.868://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup[0x6320B998] handlercount=0 #Waits=0 #Objects=1 (CS_CONFED) *Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CSReturnIFDone: decoupled extern connection *Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CSReturnIFDone:CallSetup Returning(ls_000 Status CS_ACTIVE) *Mar 7 22:08:43.872://8//PCM :/CallSetupHandler:(CS_CONFEDALERT[5]) -----(CS_EV_CONNECTED[5])------->>>(CS_CONFED[3]) *Mar 7 22:08:43.872://-1//PCM :HN23A698CC:/CallSetupCleanup:Terminate=FALSE *Mar 7 22:08:43.876://-1//PCM :HN23A698CC:/CallSetupCleanup:State CS_CONFED

The following is sample output from the debug voip application digitcollect command: Router# debug voip application digitcollect ivr digit collect debugging is on Router# *Mar 7 22:09:08.108://9//DCM :/DigitCollect:DialPlan=TRUE AbortKey= TermKey=# NumPatts=0 Enable=FALSE InterruptPrompt=FALSE maxDigits=0 DialPlanTerm=FALSE *Mar 7 22:09:08.108://9//APPL:/AppTypeAheadGetDigit:no chars in buffer. *Mar 7 22:09:08.112://9//DCM :/act_DCRunning_RDone:callid=9 Enable succeeded.enable=0 matchDialplan=1 numPatterns=0matchDialplanTerm=0 *Mar 7 22:09:11.428://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.--*Mar 7 22:09:11.428://9//APPL:/AppTypeAheadEvent:Passing, not enabled.---


DB-2323


*Mar 7 22:09:11.428://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 4 Tone Mode 0 *Mar 7 22:09:11.428://9//DCM :/DCTreatDigit: *Mar 7 22:09:11.428://-1//DCM :HN23A6FF50:/DCTreatDigit: *Mar 7 22:09:11.428: src carrier id:, tgt carrier id: *Mar 7 22:09:11.428://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype *Mar 7 22:09:11.676://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.--*Mar 7 22:09:11.676://9//APPL:/AppTypeAheadEvent:Passing, not enabled.--*Mar 7 22:09:11.676://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 0 Tone Mode 0 *Mar 7 22:09:11.676://9//DCM :/DCTreatDigit: *Mar 7 22:09:11.680://-1//DCM :HN23A6FF50:/DCTreatDigit: *Mar 7 22:09:11.680: src carrier id:, tgt carrier id: *Mar 7 22:09:11.680://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype *Mar 7 22:09:11.908://9//APPL:/AppVcrControlEvent:VCR Control, not enabled.--*Mar 7 22:09:11.908://9//APPL:/AppTypeAheadEvent:Passing, not enabled.--*Mar 7 22:09:11.908://9//DCM :/act_DCRunning_Digit::pLeg 9 Digit 5 Tone Mode 0 *Mar 7 22:09:11.908://9//DCM :/DCTreatDigit: *Mar 7 22:09:11.908://-1//DCM :HN23A6FF50:/DCTreatDigit: *Mar 7 22:09:11.908: src carrier id:, tgt carrier id: *Mar 7 22:09:11.908://-1//DCM :HN23A6FF50:/DCTreatDigit:Match single infotype *Mar 7 22:09:11.912://9//DCM :/act_DCRunning_RDone:callid=9 Reporting disabled. *Mar 7 22:09:11.912://-1//DCM :HN23A6FF50:/DigitCollectComplete:Status 4=DC_MATCHED_DIALPLAN. Digits=405 *Mar 7 22:09:11.916://-1//DCM :HN23A6FF50:/DCHandlerCleanup:

The following is sample output from the debug voip application session command: Router# debug voip application session applib session debugging is on *Apr 4 23:57:08.054://-1//APPL:HN04B2BC78:LG35:/AFS_CALLSETUPIND:Calling #(4155550154), Called #(52984), peer_tag(1) *Apr 4 23:57:08.054://-1//APPL:HN04B2BC78:LG35:/afsSetupCall:Called #(52984) *Apr 4 23:57:08.058://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLINIT)--(CC_EV_CALL_SETUP_IND)->>(CONTACTINGDEST) *Apr 4 23:57:08.466://-1//APPL:HN04B2BC78:LG36:/AFS_ContactingDest_ALERT: *Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:LG36:/AFS_ContactingDest_ALERT:inID(35), outID(36), outbnd peer_tag(6), prog_ind(8) *Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:LG36:/afsMsgHandler:(CONTACTINGDEST)--(CC_EV_CALL_ALERT )-->>(CONFINGALERT) *Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:CN11:/AFS_ConfingAlert_CREATEDONE: {HAN[AFS_HAND][NULL ]( LEG[35 ][AFS_HAND][LEG_INCALERTING(4)][Cause(0)][UC=1 ]HAN[CS_HAND][AFS_HAND][FALSE] [UC=1 ]LEG[36 ][CS_HAND ][LEG_OUTINIT(6)][Cause(0)][UC=1 ]CON[11 ][AFS_HAND][CONNECTION_CONFED(2)] [UC=1 ])} *Apr 4 23:57:08.470://-1//APPL:HN04B2BC78:CN11:/afsMsgHandler:(CONFINGALERT)--(CC_EV_CONF_CREATE_ DONE)-->>(CONFEDALERT) *Apr 4 23:57:08.478://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CONFEDALERT)--(CC_EV_VOICE_MODE_DO NE)-->>(CONFEDALERT) *Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:HN04B2BC78:/AFS_ConfedAlert_SETUPDONE: *Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:HN04B2BC78:/afsAppHandlerCleanup:CS_HAND *Apr 4 23:57:24.162://-1//APPL:HN04B2BC78:/afsMsgHandler:(CONFEDALERT)--(APP_EV_CALLSETUP_DONE)->>(CALLACTIVE) *Apr 4 23:57:24.182://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLACTIVE)--(CC_EV_VOICE_MODE_DON E)-->>(CALLACTIVE) *Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:LG35:/AFS_DISCONNECT: *Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CALLACTIVE)--(CC_EV_CALL_DISCONNEC TED)-->>(CALLDISCONNECT) *Apr 4 23:57:34.838://-1//APPL:/afsCallProcess: [HANDLERDONE_EVENT_END]


DB-2324

May 2008


*Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:/afsHNDCleanup:Terminate TRUE Terminated FALSE{HAN[AFS_HAND][NULL ]( LEG[35 ][AFS_HAND][LEG_INCCONNECTED(5)][Cause(16)][UC=1 ]LEG[36 ][AFS_HAND][LEG_OUTCONNECTED(8)][Cause(0)][UC=1 ]CON[11 ][AFS_HAND][CONNECTION_CONFED(2)] [UC=1 ])} *Apr 4 23:57:34.838://-1//APPL:HN04B2BC78:CN11:/afsMsgHandler:(CC_EV_CONF_DESTROY_DONE) *Apr 4 23:57:34.854://-1//APPL:HN04B2BC78:LG35:/afsMsgHandler:(CC_EV_CALL_DISCONNECT_DONE) *Apr 4 23:57:34.862://-1//APPL:HN04B2BC78:LG36:/afsMsgHandler:(CC_EV_CALL_DISCONNECT_DONE) *Apr 4 23:57:34.862://-1//APPL:/afsCallProcess: [HANDLERDONE_EVENT_END] *Apr 4 23:57:34.862://-1//APPL:HN04B2BC78:/afsHNDCleanup:Terminate TRUE Terminated TRUE{HAN[AFS_HAND][NULL ]( )} *Apr 4 23:57:34.862://-1//APPL:HN04B32530:/afsFreeHND:Hndlr returned to the free queue

The following sample output shows an inbound call on a system with H.450.2, H.450.3, and H.450.12 capabilities enabled: Router# debug voip application supplementary-service supplementary service debugging is on Jan 21 01:12:21.433://-1//APPL:/SSProcessH450CommonInfoEvent: CI_INFORM featureList=0xC0000000 featureValue[0][0] featureControl=0x0 Jan 21 01:12:21.433://-1//APPL:/AppStoreCommonInfoToLeg:Leg peer_tag=8100 Jan 21 01:12:21.433://-1//APPL:/AppStoreCommonInfoToLeg:Received ciInform, store ss_support=0xE000 to leg. Jan 21 01:12:21.433://-1//APPL:/AppPrepareCommonInfo:Not voip dialpeer, no common info sent. Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfoRequestReceived:Leg peer_tag=8100 Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfo:Global H450_2=1 H450_3=1 H450_12_ADV=1 H450_12_USAGE=1 Jan 21 01:12:21.437://-1//APPL:/AppPrepareCommonInfoContent:SS_CI ss_evt=18 featureList=0xC0000000 featureValues=[0][0][0][0] featureControl=0x0

Table 367 describes the significant fields shown in the displays above. Table 367

debug voip application Field Descriptions

Field

Description

Called #

Called # may not appear in the initial /AFS_CALLSETUPIND message; it appears later in the /afsSetupCall message.

peer_tag

Dial peer tag.

/afsFreeHND

Verifies that the application completed properly.

H450_2

A value of 0 indicates that H.450.2 capabilities are disabled. A value of 1 indicates that H.450.2 capabilities are enabled.

H450_3

A value of 0 indicates that H.450.3 capabilities are disabled. A value of 1 indicates that H.450.3 capabilities are enabled.

H450_12_ADV= 0 and H450_12_USAGE = 0

H.450.12 capabilities are disabled.

H450_12_ADV= 1 and H450_12_USAGE = 0

H.450.12 capabilities are enabled in advertise-only mode.

H450_12_ADV= 1 and H450_12_USAGE = 1

H.450.12 capabilities are enabled.


DB-2325


The following is sample output from the debug voip application accounting command: Router# debug voip application accounting *Jan 6 19:34:22.535: //-1//Dest:/DestSetup: *Jan 6 19:34:22.535: :DestSetup iw inc guid is 0-0-0-0 *Jan 6 19:34:22.535: //-1//Dest:/DestSetup: *Jan 6 19:34:22.535: :DestSetup iw guid is 45AB9E05-7E2211DA-8088D216-195F6285 *Jan 6 19:34:22.535: :DestSetup iw guid is 45AB9E05-7E2211DA-8088D216-195F6285 *Jan 6 19:34:22.539: //-1//Dest:/DestSetup: *Jan 6 19:34:22.539: :DestSetup setup inc guid is 0-0-0-0 *Jan 6 19:34:22.539: //-1//Dest:/DestSetup: *Jan 6 19:34:22.539: :DestSetup setup guid is 45AB9E05-7E2211DA-8088D216-195F6285 *Jan 6 19:34:45.667: //-1//Dest:/DestSetup: *Jan 6 19:34:45.667: :DestSetup iw inc guid is 0-0-0-0 *Jan 6 19:34:45.667: //-1//Dest:/DestSetup: *Jan 6 19:34:45.671: :DestSetup iw guid is 527B07DA-7E2211DA-808DD216-195F6285 *Jan 6 19:34:45.671: :DestSetup iw guid is 527B07DA-7E2211DA-808DD216-195F6285 *Jan 6 19:34:45.671: //-1//Dest:/DestSetup: *Jan 6 19:34:45.671: :DestSetup setup inc guid is 0-0-0-0 *Jan 6 19:34:45.671: //-1//Dest:/DestSetup: *Jan 6 19:34:45.671: :DestSetup setup guid is 527B07DA-7E2211DA-808DD216-195F6285 *Jan 6 19:35:04.975: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 45AB9E05 7E2211DA 8088D216 195F6285, SetupTime *19:34:22.535 UTC Fri Jan 6 2006, PeerAddress 1011011007, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *19:34:25.135 UTC Fri Jan 6 2006, DisconnectTime *19:35:04.975 UTC Fri Jan 6 2006, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0 *Jan 6 19:35:04.991: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 527B07DA 7E2211DA 808DD216 195F6285, SetupTime *19:34:43.861 UTC Fri Jan 6 2006, PeerAddress 1011011007, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *19:34:46.451 UTC Fri Jan 6 2006, DisconnectTime *19:35:04.991 UTC Fri Jan 6 2006, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0 *Jan 6 19:36:05.627: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 45AB9E05 7E2211DA 8088D216 195F6285, SetupTime *19:34:22.377 UTC Fri Jan 6 2006, PeerAddress 1011011006, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *19:34:25.137 UTC Fri Jan 6 2006, DisconnectTime *19:36:05.627 UTC Fri Jan 6 2006, CallOrigin 2, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0 *Jan 6 19:36:05.631: %VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId 527B07DA 7E2211DA 808DD216 195F6285, SetupTime *19:34:45.671 UTC Fri Jan 6 2006, PeerAddress 1011011008, PeerSubAddress , DisconnectCause 10 , DisconnectText normal call clearing (16), ConnectTime *19:34:46.451 UTC Fri Jan 6 2006, DisconnectTime *19:36:05.631 UTC Fri Jan 6 2006, CallOrigin 1, ChargedUnits 0, InfoType 2, TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0 *Jan 6 19:36:12.287: %IPPHONE-6-UNREGISTER_NORMAL: ephone-6:SEP111100011006 IP:10.3.32.56 Socket:1 DeviceType:Phone has unregistered normally. *Jan 6 19:36:12.287: %IPPHONE-6-UNREGISTER_NORMAL: ephone-7:SEP111100011007 IP:10.3.32.56 Socket:2 DeviceType:Phone has unregistered normally. *Jan 6 19:36:12.295: %IPPHONE-6-UNREGISTER_NORMAL: ephone-8:SEP111100011008 IP:10.3.32.56 Socket:3 DeviceType:Phone has unregistered normally. *Jan 6 19:36:13.227: %SYS-5-CONFIG_I: Configured from console by console

The following is sample output from the debug voip application oodrefer command: Router# debug voip application oodrefer Aug 22 18:16:21.625: //-1//AFW_:/C_ServiceThirdParty_Event_Handle: Aug 22 18:16:21.625: //-1//AFW_:/AFW_ThirdPartyCC_New: Aug 22 18:16:21.625: //-1//AFW_:EE461DC520000:/C_PackageThirdPartyCC_NewReq: ThirdPartyCC module listened by TclModule_45F39E28_0_91076048 Aug 22 18:16:21.625: //-1//AFW_:EE461DC520000:/OCOpen_SetupRequest: Refer Dest1: 1011, Refer Dest2: 1001; ReferBy User: root


DB-2326

May 2008


Aug 22 18:16:21.693: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1: Aug 22 18:16:21.693: //-1//AFW_:/Third_Party_CC_Send_Notify: Third_Party_CC_Send_Notify: sending notify respStatus=2, final=FALSE, failureCause=16 Aug 22 18:16:21.693: //-1//AFW_:/Third_Party_CC_Send_Notify: AppNotify successful! Aug 22 18:16:26.225: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1: Aug 22 18:16:26.229: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_1: Aug 22 18:16:26.249: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_2: Aug 22 18:16:29.341: //-1//AFW_:EE461DC520000:/OCHandle_SignalEvent_2: Aug 22 18:16:29.341: //-1//AFW_:/Third_Party_CC_Send_Notify: Third_Party_CC_Send_Notify: sending notify respStatus=4, final=TRUE, failureCause=16 Aug 22 18:16:29.341: //-1//AFW_:/Third_Party_CC_Send_Notify: AppNotify successful! Aug 22 18:16:29.349: //-1//AFW_:EE461DC520000:/OCHandle_Handoff: BAG contains: Aug 22 18:16:29.349: LEG[895 ][LEG_INCCONNECTED(5)][Cause(0)] Aug 22 18:16:29.349: CON[7 ][CONNECTION_CONFED(2)] {LEG[895 ][LEG_INCCONNECTED(5)][Cause(0)],LEG[896 ][LEG_OUTCONNECTED(10)][Cause(0)]} Aug 22 18:16:29.349: LEG[896 ][LEG_OUTCONNECTED(10)][Cause(0)] Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/OCAnyState_IgnoreEvent: Event Ignored Aug 22 18:16:29.365: //-1//AFW_:/C_ServiceThirdParty_Event_Handle: Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/C_ServiceThirdParty_Event_Handle: Received event APP_EV_NOTIFY_DONE[174] in Main Loop Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/OCAnyState_IgnoreEvent: Event Ignored Aug 22 18:16:29.365: //-1//AFW_:/C_ServiceThirdParty_Event_Handle: Aug 22 18:16:29.365: //-1//AFW_:EE461DC520000:/C_ServiceThirdParty_Event_Handle: Received event APP_EV_NOTIFY_DONE[174] in Main Loop Aug 22 18:16:29.369: //-1//AFW_:EE461DC520000:/OCHandle_SubscribeCleanup: Aug 22 18:16:29.369: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner: Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/OCClosing_AnyEvent: Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner: Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/OCClosing_AnyEvent: Aug 22 18:16:29.453: //-1//AFW_:EE461DC520000:/Third_Party_CC_Cleaner:

Related Commands

Command

Description

debug voip ivr all

Displays all IVR and application framework messages.

supplementary-service h450.2 (dial-peer) Enables H.450.2 capabilities for call transfers for an individual dial peer. supplementary-service h450.2 (voice-service)

Globally enables H.450.2 capabilities for call transfers.

supplementary-service h450.3 (dial-peer) Enables H.450.3 capabilities for call forwarding for an individual dial peer. supplementary-service h450.3 (voice-service)

Globally enables H.450.3 capabilities for call forwarding.

supplementary-service h450.12 (dial-peer)

Enables H.450.12 capabilities for an individual dial peer.

supplementary-service h450.12 (voice-service)

Globally enables H.450.12 capabilities.


DB-2327

Debug Commands debug voip application vxml

debug voip application vxml To troubleshoot a VoiceXML application, use the debug voip application vxml command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip application vxml [all | application | background | default | error [call [informational] | software [informational]] | event | function | grammar | gtd | inout | log | puts | ssml | trace | warning] no debug voip application vxml

Syntax Description

all

(Optional) Displays all VoiceXML debugging messages.

application

(Optional) Displays VoiceXML application states information.

background

(Optional) Displays VoiceXML background messages.

default

(Optional) Displays output for all of the following keywords: •

application

•

background

•

error

•

event

•

gtd

•

inout

•

puts

•

trace

•

warning

This option is also available if no keywords are added. error

(Optional) Displays VoiceXML errors.

call


informational


software


event

(Optional) Displays VoiceXML asynchronous events.

function

(Optional) Displays VoiceXML functions.

grammar

(Optional) Enables syntax checking of XML grammar by the VoiceXML interpreter and displays syntax debugging messages.

gtd

(Optional) Displays VoiceXML generic transparency descriptors.

inout

(Optional) Displays VoiceXML in/out functions.

log

(Optional) Displays the results of the VoiceXML tag.

puts

(Optional) Displays the results of VoiceXML and tags. Note

In Cisco IOS Release 12.4(6th)T and later releases, the puts keyword is obsolete. Use the log keyword instead.


DB-2328

May 2008


ssml

(Optional) Enables syntax checking of Speech Synthesis Markup Language (SSML) by the VoiceXML interpreter and displays syntax debugging messages.

trace

(Optional) Displays a trace of all activities for the current VoiceXML document.

warning

(Optional) Displays VoiceXML warning messages.

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug vxml command.

12.4(15)T

The puts keyword was obsoleted. The log keyword was added to replace it.

12.2SX


Usage Guidelines

If this debug encounters a fetch failure when using an HTTP interface, an error.badfetch.http.response code message is displayed. The values for the response code are shown in Table 368. Table 368

error.badfetch.http Response Codes

Response Code

Description

0

No response from HTTP server

400

Bad request

401

Unauthorized

402

Payment required

403

Forbidden

404

Not found

405

Method not allowed

406

Not acceptable

407

Proxy authentication required

408

Request timeout

409

Conflict

410

Gone

411

Length required

412

Precondition failed

413

Request entity too large


DB-2329


Table 368

Examples

error.badfetch.http Response Codes

Response Code

Description

414

Request-URI too large

415

Unsupported media type

416

Requested range not satisfiable

417

Expectation failed

500

Internal server error

501

Not implemented

502

Bad gateway

503

Service unavailable

504

Gateway timeout

505

Version not supported

The following is sample output from the debug voip application vxml all command if there is an HTTP badfetch error call: Router# debug voip application vxml all Aug

7 04:53:03.003: //-1/000000000000/VAPP:/vapp_evt_handler: State VAPP_ACTIVE got event CC_EV_CALL_SETUP_IND Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_driver: pInterp[6383BA48]: Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_driver: evtID: 29 vapp record state: 0 Aug 7 04:53:03.003: //-1/000000000000/VAPP:/vapp_evt_setup: Aug Aug

7 04:53:03.003: //-1//VAPP:/vapp_incoming_callblock: 7 04:53:03.003: vapp_incoming_callblock:

Before the incoming call block data comes in, the CallEntry ID is -1, which indicates that the call leg had not been identified. In the next excerpt, the call leg is shown as 1 and the GUID is also assigned. Aug

7 04:53:03.003: //1/71E56a9AF8002/VAPP:/vapp_evt_setup: VXML call. GTD should be saved Aug 7 04:53:03.003: //1/71E569AF8002/VAPP:/vapp_load_or_run_script: Aug 7 04:53:03.003: //1/71E569AF8002/VAPP:/vapp_load_or_run_script:

The next excerpt show script-specific information. Aug 7 04:53:03.007: The VXML Script with len=1519 starts: ------------------------------------ status=10 Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_start: vxmlhandle=6372E9BC vapphandle=6383BA48 status=0 async_status=10 Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_vapp_terminate: vapp_status=0 ref_count 0 Aug 7 04:53:03.739: //1/71E569AF8002/VAPP:/vapp_terminate: Aug 7 04:53:03.739: //1/71E569AF8002/VXML:/vxml_destroy: Enter Aug 7 04:53:03.739: //-1//VXML:/vxml_gtd_delete_callback: New ref-count = 0

Related Commands

Command

Description

debug condition application voice

Displays debugging messages for only the specified VoiceXML application.

debug http client

Displays debugging messages for the HTTP client.

debug voip ivr

Displays debugging messages for VoIP IVR interactions.


DB-2333

Debug Commands debug voip avlist

debug voip avlist To troubleshoot the attribute value list (AVLIST) contents, use the debug voip avlist command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip avlist [all | default | detail | error [call [informational] | software [informational]] | inout] no debug voip avlist

Syntax Description

all

(Optional) Displays all AVLIST debugging messages.

default

(Optional) Displays AVLIST error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays AVLIST background messages.

error

(Optional) Displays AVLIST error messages.

call


informational


software


inout

(Optional) Displays AVLIST in/out functions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Usage Guidelines

The debug voip avlist command does not support call debug filtering.

Examples

Output is primarily used by TAC.


DB-2334

May 2008

Debug Commands debug voip ccapi error

debug voip ccapi error To trace error logs in the call control application programming interface (CCAPI), use the debug voip ccapi error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip ccapi error no debug voip ccapi error

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T

This command was implemented on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3660, Cisco AS5350, Cisco AS5400, Cisco AS5850, Cisco AS5300, Cisco AS5800, and Cisco MC3810.

12.2SX


Usage Guidelines

The debug voip ccapi error command traces the error logs in the call control API. Error logs are generated during normal call processing, when there are insufficient resources, or when there are problems in the underlying network-specific code, the higher call session application, or the call control API itself. This debug command shows error events or unexpected behavior in system software. In most cases, no events will be generated.

Note

Related Commands

We recommend that you log output from the debug voip ccapi error command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Command

Description

debug voip ccapi inout

Traces the execution path through the CCAPI.

voice call debug

Allows configuration of the voice call debug output.


DB-2335

Debug Commands debug voip ccapi inout

debug voip ccapi inout To trace the execution path through the call control application programming interface (CCAPI), use the debug voip ccapi inout command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip ccapi inout no debug voip ccapi inout

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Usage Guidelines

The debug voip ccapi inout command traces the execution path through the call control API, which serves as the interface between the call session application and the underlying network-specific software. You can use the output from this command to understand how calls are being handled by the voice gateway. This command shows how a call flows through the system. Using this debug level, you can see the call setup and teardown operations performed on both the telephony and network call legs.

Note

Examples

We recommend that you log output from the debug voip ccapi inout command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

The following example shows the call setup indicated and accepted by the voice gateway: Router# debug voip ccapi inout *Mar 1 15:35:53.588: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructTDUsrContainer: usrContainer[0x638C1BF0], magic[FACE0FFF] *Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer: container=0x638C1BF0, tagID=6, dataSize=16, instID=-1,modifier=1 *Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject: tdObject[0x638BC1AC], nxtElem[0x0], magic[0xFACE0FFF] tagID[6], dataLen[16], modif[1]


DB-2336

May 2008


*Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer: Adding tdObject[0x638BC1AC] instID[-1] into container[0x638C1BF0] *Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDUtilAddDataToUsrContainer: container=0x638C1BF0, tagID=5, dataSize=276, instID=-1,modifier=1 *Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructInstanceTDObject: tdObject[0x63401148], nxtElem[0x0], magic[0xFACE0FFF] tagID[5], dataLen[276], modif[1] *Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToContainer: Adding tdObject[0x63401148] instID[-1] into container[0x638C1BF0]

In the following lines, the call control API (CCAPI) receives the call setup. The called number is 34999, and the calling number is 55555. The calling number matches dial peer 10002. *Mar 1 15:35:53.592: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields: *Mar 1 15:35:53.592: cc_api_call_setup_ind: *Mar 1 15:35:53.592: cisco-username= *Mar 1 15:35:53.596: ----- ccCallInfo IE subfields ----*Mar 1 15:35:53.596: cisco-ani=55555 *Mar 1 15:35:53.596: cisco-anitype=0 *Mar 1 15:35:53.596: cisco-aniplan=0 *Mar 1 15:35:53.596: cisco-anipi=0 *Mar 1 15:35:53.596: cisco-anisi=0 *Mar 1 15:35:53.596: dest=34999 *Mar 1 15:35:53.596: cisco-desttype=0 *Mar 1 15:35:53.596: cisco-destplan=0 *Mar 1 15:35:53.596: cisco-rdn= *Mar 1 15:35:53.596: cisco-rdntype=-1 *Mar 1 15:35:53.596: cisco-rdnplan=-1 *Mar 1 15:35:53.596: cisco-rdnpi=-1 *Mar 1 15:35:53.596: cisco-rdnsi=-1 *Mar 1 15:35:53.596: cisco-redirectreason=-1 *Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: (vdbPtr=0x637EC1E0, callInfo={called=34999,called_oct3=0x80,calling=55555,calling_oct3=0x80,calling_oct3a=0x0, calling_xlated=false,subscriber_type_str=RegularLine,fdest=1, peer_tag=10002, prog_ind=0,callingIE_present 1, src_route_label=, tgt_route_label= clid_transparent=0},callID=0x637B4278) *Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: *Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: type 13 , prot 0 *Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir: *Mar 1 15:35:53.596: ccCheckClipClir: calling number is: "55555", calling oct3a is: 0x0 *Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir: *Mar 1 15:35:53.596: Calling Party number is User Provided *Mar 1 15:35:53.596: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir: *Mar 1 15:35:53.596: Leaving ccCheckClipClir calling number is: "55555" calling oct3 is: 0x80 calling oct3a is: 0x0

In the next line, 44 is the CallEntry ID. *Mar 0

1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Increment call volume:

*Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: current call volume: 1 *Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: entry's incoming TRUE. *Mar 1 15:35:53.600: //44/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: is_incoming is TRUE *Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDConstructHashProfileTab: profileTable[0x6380E11C], numBuckets[11], numEntries[0] *Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager: Invoking necessary profileTable updaters... *Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: Updating profileTable[0x6380E11C] with objects in container[0x638C1BF0]


DB-2337


*Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: obtained key[5] for the tag[6] *Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: profileTable[0x6380E11C], tdObject[0x638BC1AC] *Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtUpdateProfileTabFromContainer: obtained key[0] for the tag[5] *Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtAddObjectToProfileBucket: profileTable[0x6380E11C], tdObject[0x63401148] *Mar 1 15:35:53.600: //-1/xxxxxxxxxxxx/CCAPI/ccTDPvtProfileTableBuildManager: *Mar 1 15:35:53.600: ccTDUtilDumpAllElemInProfileTab: profileTable[0x6380E11C], numBuckets[11], numEntries[2] *Mar 1 15:35:53.600: Bucket { 0 } ------>0x63401148[0x0,t-5,l-276,d-0x63401168, m-1,u-56153,g-FACE0FFF] *Mar 1 15:35:53.604: *Mar 1 15:35:53.604: Bucket { 5 } ------>0x638BC1AC[0x0,t-6,l-16,d-0x638BC1CC,m-1,u-56153,g-FACE0FFF] *Mar 1 15:35:53.604: *Mar 1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDUsrContainer: Container[0x638C1BF0] *Mar 1 15:35:53.604: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: not the VoIP or MMoIP *Mar 1 15:35:53.608: //-1/xxxxxxxxxxxx/CCAPI/cc_process_call_setup_ind: (event= 0x63073AA0)

In the next line, 45F2AAE28044 is the GUID. The tag 10002 entry shows that the incoming dial peer matched the CallEntry ID. *Mar 1 15:35:53.608: //44/45F2AAE28044/CCAPI/cc_process_call_setup_ind: >>>>CCAPI handed cid 44 with tag 10002 to app "DEFAULT" *Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(24=CC_EV_CALL_SETUP_IND), cid(44), disp(0) *Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(SSA_EV_CALL_SETUP_IND), cid(44), disp(0) *Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/SSAPP:-1:-1/ssaCallSetupInd:

The next line shows CallEntry ID in hexadecimal form, 0x2C (44 in decimal). The CallID and GUID numbers have been identified. The incoming dial-peer is 10002. *Mar 1 15:35:53.608: //44/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2C, context=0x634A430C) *Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44), st(SSA_CS_MAPPING),oldst(0), ev(24)ev->e.evCallSetupInd.nCallInfo.finalDestFlag = 1 *Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: src route label=, tgt route label= tg_label_flag 0x0 *Mar 1 15:35:53.608: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: finalDest cllng(55555), clled(34999) tgt_route_label()tg_label_flag 0x0 *Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaCallSetupInd: cid(44), st(SSA_CS_CALL_SETTING),oldst(0), ev(24)dpMatchPeersMoreArg result= 0

For CallEntry ID 44, two dial-peer tags (10001 and 20002) were matched with called number 34999. *Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaDebugPeers: ssaSetupPe er cid(44) peer list: tag(10001) called number (34999) tag(20002) called number (34999) *Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaSetupPeer: dialpeer tags in rotary= 10001 20002


DB-2338

May 2008


The next line shows that 5 digits were matched for this dial peer and no prefix was added. The encapType (2) entry indicates a VoIP call. *Mar 1 15:35:53.612: //44/45F2AAE28044/SSAPP:10002:-1/ssaSetupPeer: cid(44), de stPat(34999), matched(5), prefix(), peer(637B0984), peer->encapType (2) *Mar 1 15:35:53.612: //-1/xxxxxxxxxxxx/CCAPI/cc_can_gateway: Call legs: In=6, O ut=1

The next line shows the voice gateway sending out a call-proceeding message to the incoming call leg with progress indicator of 0x0. *Mar 1 15:35:53.612: //44/xxxxxxxxxxxx/CCAPI/ccCallProceeding: (callID=0x2C, pr og_ind=0x0)

The next line shows the voice gateway sending out the call-setup request to the outgoing call leg. The dial-peer is 10001 with the incoming CallEntry ID being 0x2C. *Mar 1 15:35:53.612: //44/xxxxxxxxxxxx/CCAPI/ccCallSetupRequest: (Inbound call = 0x2C, outbound peer =10001, dest=, params=0x63085D80 mode=0, *callID=0x63086314, prog_ind = 0callingIE_pres ent 1) *Mar *Mar *Mar *Mar

1 1 1 1

15:35:53.612: 15:35:53.612: 15:35:53.612: 15:35:53.616:

//44/45F2AAE28044/CCAPI/ccCallSetupRequest: ccCallSetupRequest numbering_type 0x80 //44/45F2AAE28044/CCAPI/ccCallSetupRequest: ccCallSetupRequest: calling number is:55555

*Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: calling oct3a is:0x0 *Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir: *Mar 1 15:35:53.616: ccCheckClipClir: calling number is: "55555", calling oct3a is: 0x0 *Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir: *Mar 1 15:35:53.616: Calling Party number is User Provided *Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/ccCheckClipClir: *Mar 1 15:35:53.616: Leaving ccCheckClipClir calling number is: "55555" calling oct3 is: 0x80 calling oct3a is: 0x0 *Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: after ccCheckC lipClir - calling oct3a is:0x0

The next line shows that all digits are passed. *Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: dest pattern 3 4999, called 34999, digit_strip 0 *Mar 1 15:35:53.616: //44/45F2AAE28044/CCAPI/ccCallSetupRequest: *Mar 1 15:35:53.616: callingNumber=55555, calledNumber=34999, redirectNumber= d isplay_info= calling_oct3a=0 *Mar 1 15:35:53.616: accountNumber=, finalDestFlag=1, guid=45f2.aae2.1571.11cc.8044.95f5.fabb.6b0f *Mar 1 15:35:53.616: peer_tag=10001 *Mar 1 15:35:53.616: //-1/xxxxxxxxxxxx/CCAPI/cc_api_display_ie_subfields: *Mar 1 15:35:53.616: ccCallSetupRequest: *Mar 1 15:35:53.616: cisco-username= *Mar 1 15:35:53.616: ----- ccCallInfo IE subfields ----*Mar 1 15:35:53.616: cisco-ani=55555 *Mar 1 15:35:53.616: cisco-anitype=0 *Mar 1 15:35:53.616: cisco-aniplan=0 *Mar 1 15:35:53.616: cisco-anipi=0 *Mar 1 15:35:53.616: cisco-anisi=0 *Mar 1 15:35:53.620: dest=34999 *Mar 1 15:35:53.620: cisco-desttype=0


DB-2339



1 1 1 1 1 1 1

15:35:53.620: 15:35:53.620: 15:35:53.620: 15:35:53.620: 15:35:53.620: 15:35:53.620: 15:35:53.620:

cisco-destplan=0 cisco-rdn= cisco-rdntype=-1 cisco-rdnplan=-1 cisco-rdnpi=-1 cisco-rdnsi=-1 cisco-redirectreason=-1

*Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: (vdbP tr=0x62EC61A4, dest=, callParams={called=34999,called_oct3=0x80, calling=55555,calling_oct3=0x80, calling_oct3a= 0x0, calling_xlated=false, subscriber_type_str =RegularLine, fdest=1, voice_peer_tag=10001},mode=0x0) *Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: *Mar 1 15:35:53.620: ccIFCallSetupRequestPrivate: src route label tgt route label tg_label_flag 0x0 *Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: vdbPtr type = 1 *Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: *Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: (vdbPtr=0x62EC61A4, dest=, callParams={called=34999, called_oct3 0x80, calling=55555,calling_oct3 0x80, calling_oct3a 0x0, calling_xlated=false, fdest=1, voice_pee r_tag=10001}, mode=0x0, xltrc=-5) *Mar 1 15:35:53.620: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: In the next line, outgoing CallEntry ID 45 is bound to the same GUID 45F2AAE28044. *Mar 1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: not incoming entry *Mar 1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: entry's incoming FALSE. *Mar 1 15:35:53.620: //45/45F2AAE28044/CCAPI/cc_insert_call_entry: is_incoming is FALSE *Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/ccSaveDialpeerTag: (callID=0x2C, dialpeer_tag=10001) *Mar 1 15:35:53.624: //45/xxxxxxxxxxxx/CCAPI/ccCallSetContext: (callID=0x2D, context=0x634A537C) 0x2D (decimal 45 is the second call leg ID). *Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/ccCallReportDigits: (callID=0x2C, enable=0x0)

The voice gateway informs the incoming call leg that digits were forwarded. *Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_report_digits_done: (vdbPtr=0x637EC1E0, callID=0x2C, disp=0) *Mar 1 15:35:53.624: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(54=CC_EV_CALL_ REPORT_DIGITS_DONE), cid(44), disp(0) *Mar 1 15:35:53.624: //44/45F2AAE28044/SS Router#APP:10002:-1/ssaTraceSct: cid(44)st(SSA_CS_CALL_SETTING)ev(SSA_EV_CALL_RE PORT_DIGITS_DONE) oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(1)fDest(1) *Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaTraceSct: -cid2(45)st2 (SSA_CS_CALL_SETTING)oldst2(SSA_CS_MAPPING) *Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaDebugPeers: ssaReportDigitsDone cid(44) peer list: tag(20002) called number (34999) *Mar 1 15:35:53.624: //44/45F2AAE28044/SSAPP:10002:-1/ssaReportDigitsDone: call id=44 Reporting disabled. *Mar 1 15:35:53.628: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data: data_mode=0x10082 *Mar 1 15:35:53.628: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_ic_leg_obtained_numbers: callID=0x2D


DB-2340

May 2008


The next two lines shows the IP address of the terminating gateway and that the terminating gateway is reached through Ethernet port 0/0. *Mar 1 15:35:53.628: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: remote IP is 171.69.85.111 *Mar 1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: hwidb is Ethernet0/0 *Mar 1 15:35:53.632: //-1/xxxxxxxxxxxx/CCAPI/cc_incr_if_call_volume: create entry in list: 1 *Mar 1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagI D[1] of callID[45] *Mar 1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45] *Mar 1 15:35:53.636: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetInstanceCount: For tagID[2] of callID[45] *Mar 1 15:35:53.636: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45]

The next line shows that the voice gateway received a call proceeding message from the terminating gateway, and then the following line shows that the voice gateway received a call alert from the terminating gateway. *Mar 1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding: (vdbPtr=0x62EC61A4, callID=0x2D, prog_ind=0x0) *Mar 1 15:35:53.740: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_alert: (vdbPtr=0x62EC61A4, callID=0x2D, prog_ind=0x0, sig_ind=0x1) *Mar 1 15:35:53.744: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(21=CC_EV_CALL_PROCEEDING), cid(45), disp(0) *Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS _CALL_SETTING)ev(SSA_EV_CALL_PROCEEDING) oldst(SSA_CS_MAPPING)cfid(-1)csize(0)in(0)fDest(0) *Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA_CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING) *Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaCallProc: *Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C) *Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaIgnore: cid(45), st(SSA_CS _CALL_SETTING),oldst(1), ev(21) *Mar 1 15:35:53.744: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(7=CC_EV_CALL_ALERT), cid(45), disp(0) *Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS _CALL_SETTING)ev(SSA_EV_CALL_ALERT) oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0) *Mar 1 15:35:53.744: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA _CS_CALL_SETTING)oldst2(SSA_CS_CALL_SETTING) *Mar 1 15:35:53.744: //44/45F2AAE28044/SSAPP:10002:-1/ssaAlert: *Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C) Router#

The voice gateway forwarded a call alert to the originating gateway. *Mar 1 15:35:53.744: //44/xxxxxxxxxxxx/CCAPI/ccCallAlert: (callID=0x2C, prog_ind=0x0, sig_ind=0x1) Router#

The phone is answered at the called number. Router#!call answered Router#


DB-2341


The voice gateway receives a connect message from the terminating gateway. *Mar 1 15:36:05.016: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_connected: (vdbPtr=0x6 2EC61A4, callID=0x2D), prog_ind = 0 *Mar 1 15:36:05.016: //45/45F2AAE28044/CCAPI/cc_api_call_connected: setting callEntry->connected to TRUE

The next line shows that the call accounting starts. The leg_type=False message means this is for an outgoing call. The line that follows shows that AAA accounting is not configured. *Mar 1 15:36:05.016: //45/45F2AAE28044/CCAPI/cc_api_call_connected: calling accounting start for callID=45 leg_type=0 *Mar 1 15:36:05.020: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=0x 2D, accounting=0 *Mar 1 15:36:05.020: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(8=CC_EV_CALL_CONNECTED), cid(45), disp(0) *Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS _ALERT_RCVD)ev(SSA_EV_CALL_CONNECTED) oldst(SSA_CS_CALL_SETTING)cfid(-1)csize(0)in(0)fDest(0) *Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA _CS_ALERT_RCVD)oldst2(SSA_CS_CALL_SETTING) *Mar 1 15:36:05.020: //45/45F2AAE28044/SSAPP:0:-1/ssaConnect: *Mar 1 15:36:05.020: //44/xxxxxxxxxxxx/CCAPI/ccGetDialpeerTag: (callID=0x2C)

The next lines show a conference being set up between the two call legs 0x2C and 0x2D. Bridge complete messages are sent to both the terminating and originating gateways. *Mar 1 15:36:05.020: //44/xxxxxxxxxxxx/CCAPI/ccConferenceCreate: (confID=0x6308 6424, callID1=0x2C, callID2=0x2D, tag=0x0) *Mar 1 15:36:05.020: //45/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done: (confID=0x15, srcIF=0x62EC61A4, srcCallID=0x2D, dstCallID=0x2C, disposition=0, tag=0x0) *Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done: (confID=0x15, srcIF=0x637EC1E0, srcCallID=0x2C, dstCallID=0x2D, disposition=0, tag=0x0)

Here, the voice gateway sets up negotiating capability with the originating telephony leg. *Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (dstVdbPtr=0x62EC 61A4, dstCallId=0x2D, srcCallId=0x2C, caps={codec=0x2887F, fax_rate=0xBF, vad=0x3, modem=0x2 codec_bytes=0, signal_type=3}) *Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0, initial 60,min 40, max 300) *Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(29=CC_EV_CONF_ CREATE_DONE), cid(44), disp(0) *Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: cid(44)st(SSA_CS_CONFERENCING)ev(SSA_EV_CONF_CREATE_DONE) oldst(SSA_CS_CALL_SETTING)cfid(21)csize(2)in(1)fDest(1) *Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2 (SSA_CS_CONFERENCING)oldst2(SSA_CS_ALERT_RCVD) *Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaConfCreateDone: *Mar 1 15:36:05.024: //44/xxxxxxxxxxxx/CCAPI/ccCallConnect: (callID=0x2C), prog _ind = 0 *Mar 1 15:36:05.024: //44/45F2AAE28044/CCAPI/ccCallConnect: setting callEntry-> connected to TRUE *Mar 1 15:36:05.024: //44/45F2AAE28044/SSAPP:10002:21/ssaDebugPeers: ssaFlushPeerTagQueue cid(44) peer list: tag(20002) called number (34999) *Mar 1 15:36:05.028: //-1/xxxxxxxxxxxx/CCAPI/cc_process_notify_bridge_done: (event=0x63067FC0)


DB-2342

May 2008


The voice gateway sets up negotiating capability with the terminating VoIP leg. *Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (dstVdbPtr=0x637E C1E0, dstCallId=0x2C, srcCallId=0x2D, caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0 codec_bytes=20, signal_type=2}) *Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ind: (Playout: mode 0, initial 60,min 40, max 300)

The capabilities are acknowledged for both call legs. *Mar 1 15:36:05.028: //45/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x637E C1E0, dstCallId=0x2C, srcCallId=0x2D, caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0 codec_bytes=20, signal_type=2, seq_num_start=2944}) *Mar 1 15:36:05.028: //44/xxxxxxxxxxxx/CCAPI/cc_api_caps_ack: (dstVdbPtr=0x62EC 61A4, dstCallId=0x2D, srcCallId=0x2C, caps={codec=0x4, fax_rate=0x2, vad=0x2, modem=0x0 codec_bytes=20, signal_type=2, seq_num_start=2944}) *Mar 1 15:36:05.032: *Mar 1 15:36:05.032: =634A430C *Mar 1 15:36:05.032: _MODE_DONE), cid(44), *Mar 1 15:36:05.032: Router#

//44/xxxxxxxxxxxx/CCAPI/cc_api_voice_mode_event: callID=0x2C //44/45F2AAE28044/CCAPI/cc_api_voice_mode_event: Call Pointer //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(52=CC_EV_VOICE disp(0) //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct:

Router# cid(44)st(SSA_CS_ACTIVE)ev(SSA_EV_VOICE_MODE_DONE) oldst(SSA_CS_CONFERENCING)cfid(21)csize(2)in(1)fDest(1) *Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2 (SSA_CS_ACTIVE)oldst2(SSA_CS_ALERT_RCVD) *Mar 1 15:36:05.032: //44/45F2AAE28044/SSAPP:10002:21/ssaIgnore: cid(44), st(SS A_CS_ACTIVE),oldst(5), ev(52) Router# Router#! digit punched Router#

The phone at the terminating gateway enters digit 1. *Mar 1 15:36:11.204: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPtr=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D, digit=1, digit_begin_flags=0x0, rtp_timestamp=0x0 rtp_expiration=0x0, dest_mask=0x2) *Mar 1 15:36:11.504: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr= 0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D, digit=1,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), digit_tone_mode=0

The phone at the terminating gateway enters digit 2. *Mar 1 15:36:11.604: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin: (dstVdbPt r=0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D, digit=2, digit_begin_flags=0x0, rtp_timestamp=0x0 rtp_expiration=0x0, dest_mask=0x2) *Mar 1 15:36:11.904: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end: (dstVdbPtr= 0x637EC1E0, dstCallId=0x2C, srcCallId=0x2D, digit=2,duration=300,xruleCallingTag=0,xruleCalledTag=0, dest_mask=0x2), digit_tone_mode=0 Router# Router# *Mar 1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer: Calling the callback, ccTimerctx - 0x628B6330 *Mar 1 15:36:14.476: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart: ccTimerctx - 0x628B6330 Router#


DB-2343


Router# !call hung up Router#

The user at the terminating gateway hangs up the call.

The voice gateway receives a disconnect message from the terminating gateway. The cause code is 0x10 which is normal call clearing. *Mar 1 15:36:22.916: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnected: (vdbPtr= 0x62EC61A4, callID=0x2D, cause=0x10) *Mar 1 15:36:22.920: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(11=CC_EV_CALL_ DISCONNECTED), cid(45), disp(0) *Mar 1 15:36:22.920: //45/45F2AAE28044/SSAPP:0:21/ssaTraceSct: cid(45)st(SSA_CS _ACTIVE)ev(SSA_EV_CALL_DISCONNECTED) oldst(SSA_CS_ALERT_RCVD)cfid(21)csize(2)in(0)fDest(0) *Mar 1 15:36:22.920: //45/45F2AAE28044/SSAPP:0:21/ssaTraceSct: -cid2(44)st2(SSA _CS_ACTIVE)oldst2(SSA_CS_ACTIVE) *Mar 1 15:36:22.920: ssa: Disconnected cid(45) state(5) cause(0x10)

The voice gateway begins tearing down the conference and dropping the bridge. *Mar 1 15:36:22.920: //-1/xxxxxxxxxxxx/CCAPI/ccConferenceDestroy: (confID=0x15, tag=0x0) *Mar 1 15:36:22.920: //45/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done: (confID=0 x15, srcIF=0x62EC61A4, srcCallID=0x2D, dstCallID=0x2C, disposition=0 tag=0x0) *Mar 1 15:36:22.920: //44/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done: (confID=0 x15, srcIF=0x637EC1E0, srcCallID=0x2C, dstCallID=0x2D, disposition=0 tag=0x0) *Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(30=CC_EV_CONF_ DESTROY_DONE), cid(44), disp(0) *Mar 1 15:36:22.924: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: cid(44)st(SSA_CS_CONF_DESTROYING)ev(SSA_EV_CONF_DESTROY_DONE) oldst(SSA_CS_ACTIVE)cfid(21)csize(2)in(1)fDest(1) *Mar 1 15:36:22.924: //44/45F2AAE28044/SSAPP:10002:21/ssaTraceSct: -cid2(45)st2 (SSA_CS_CONF_DESTROYING)oldst2(SSA_CS_ACTIVE) *Mar 1 15:36:22.924: //45/45F2AAE28044/SSAPP:0:-1/ssaConfDestroyDone: *Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: (callID=0x2C, cause=0x10 tag=0x0)

The voice gateway stops call accounting on the incoming call, indicated by the leg_type=True message. The cause code is then set for the originating leg. *Mar 1 15:36:22.924: //44/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounting start for callID=44 leg_type=1 *Mar 1 15:36:22.924: //44/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause = 0x0, new_cause = 0x10 *Mar 1 15:36:22.924: //44/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=0x2C) *Mar 1 15:36:22.924: //45/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: (callID=0x2D, cause=0x10 tag=0x0)

The voice gateway stops call accounting for the outgoing call, indicated by the leg_type=False message. The cause code is verified for the terminating leg. *Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: calling accounting start for callID=45 leg_type=0 *Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: existing_cause = 0x10, new_cause = 0x10 *Mar 1 15:36:22.924: //45/45F2AAE28044/CCAPI/ccCallDisconnect: using the existing_cause 0x10 *Mar 1 15:36:22.928: //45/xxxxxxxxxxxx/CCAPI/cc_api_get_transfer_info: (callID=0x2D) *Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_api_icpif: expect factor = 0 *Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/g113_calculate_impairment: (delay=79, loss=0), Io=0 Iq=0 Idte=0 Idd=0 Ie=10 Itot=10 *Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: the remote IP is 171.69.85.111 *Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: hwidb is Ethernet0/0


DB-2344

May 2008


*Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: reduce callnum of entry: 0, voip: 0, mmoip: 0 *Mar 1 15:36:22.932: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: remove an entry *Mar 1 15:36:22.932: //45/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbPtr=0x62EC61A4, callID=0x2D, disp=0, tag=0x0) *Mar 1 15:36:22.932: //45/45F2AAE28044/CCAPI/ccTDPvtProfileTableObjectAccessManager: No profileTable set for callID[45] *Mar 1 15:36:22.936: //45/xxxxxxxxxxxx/CCAPI/ccTDUtilGetDataByRef: No tdObject found in profileTable for tagID[6] of callID[45] *Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: not incoming entry *Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's incoming FALSE. *Mar 1 15:36:22.936: //45/45F2AAE28044/CCAPI/cc_delete_call_entry: is_incoming is FALSE *Mar 1 15:36:22.940: //45/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(12=CC_EV_CALL_ DISCONNECT_DONE), cid(45), disp(0) *Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: cid(45)st(SSA_CS _DISCONNECTING)ev(SSA_EV_CALL_DISCONNECT_DONE) oldst(SSA_CS_ACTIVE)cfid(-1)csize(2)in(0)fDest(0) *Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaTraceSct: -cid2(44)st2(SSA _CS_DISCONNECTING)oldst2(SSA_CS_CONF_DESTROYING) *Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaDisconnectDone: *Mar 1 15:36:22.940: //45/45F2AAE28044/SSAPP:0:-1/ssaAAA_CheckAccounting: accounting generation enabled *Mar 1 15:36:22.940: //45/xxxxxxxxxxxx/CCAPI/ccCallSetAAA_Accounting: callID=0x2D, accounting=0 *Mar 1 15:36:22.944: //-1/xxxxxxxxxxxx/CCAPI/cc_decr_if_call_volume: not the VoIP or MMoIP *Mar 1 15:36:22.948: //44/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnect_done: (vdbPtr=0x637EC1E0, callID=0x2C, disp=0, tag=0x0) *Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: ccFreeRawMsg Info(0x6307595C) *Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: Decrement call volume counter 1 *Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: current call volume: 0 *Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: entry's incoming TRUE. *Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: is_incoming is TRUE *Mar 1 15:36:22.948: //44/45F2AAE28044/CCAPI/cc_delete_call_entry: Deleting profileTable[0x6380E11C] *Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructTDHashProfileTab: Destructor Profile Table (0x6380E11C) *Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdObject[0x63401148] tagID[5] *Mar 1 15:36:22.948: //-1/xxxxxxxxxxxx/CCAPI/ccTDDestructInstanceTDObject: tdObject[0x638BC1AC] tagID[6] *Mar 1 15:36:22.956: //44/xxxxxxxxxxxx/SSAPP:-1:-1/sess_appl: ev(12=CC_EV_CALL_ DISCONNECT_DONE), cid(44), disp(0) *Mar 1 15:36:22.956: //44/45F2AAE28044/SSAPP:10002:-1/ssaTraceSct: cid(44)st(SSA_CS_DISCONNECTING)ev(SSA_EV_CALL_DISCONNECT_DONE) oldst(SSA_CS_CONF_DESTROYING)cfid(-1)csize(1)in(1)fDest(1) Router# *Mar 1 15:36:22.956: //44/45F2AAE28044/SSAPP:10002:-1/ssaDisconnectDone:

Related Commands

Command

Description

debug voip ccapi error

Traces error logs in the CCAPI.

voice call debug



DB-2345

Debug Commands debug voip ccapi

debug voip ccapi To troubleshoot the call control application programming interface (CCAPI) contents, use the debug voip ccapi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip ccapi [all | default | detail | error [call [informational] | software [informational]] | individual range | inout | function | protoheaders | service] no debug voip ccapi

Syntax Description

all

(Optional) Displays all CCAPI debugging messages.

default

(Optional) Displays CCAPI error and inout information. This option also runs if no keywords are added.

detail

(Optional) Displays CCAPI background messages.

error

(Optional) Displays CCAPI error messages. The debug voip ccapi error command traces the error logs in the call control API. Error logs are generated during normal call processing, if there are insufficient resources, or if there are problems in the underlying network-specific code, the higher call session application, or the call control API itself. This debug command shows error events or unexpected behavior in system software. Usually no events will be generated.

call


informational


software


individual

(Optional) Enables individual CCAPI debug outputs.

range

For the individual keyword, the range is an integer value from 1 to 146. For specific range values, see Table 369.

inout

(Optional) Displays CCAPI in/out functions. The debug voip ccapi inout command traces the execution path through the call control API, which serves as the interface between the call session application and the underlying network-specific software. You can use the output from this command to understand how calls are being handled by the router. This command shows how a call flows through the system. Using this debug level, you can see the call setup and teardown operations performed on both the telephony and network call legs.

function

(Optional) Displays CCAPI function tracing.

protoheaders

(Optional) Displays CCAPI protocol headers passing information.

service

(Optional) Logs debug messages that are not call related.


DB-2346

May 2008


Table 369

CCAPI Individual Debug Values

Value

CCAPI Debug Function

1

CC_IDMSG_API_DISPLAY_IES

2

CC_IDMSG_SETUP_IND_COMM_2

3


4


5

CC_IDMSG_ALERT_IND_5

6

CC_IDMSG_ALERT_IND_6

7

CC_IDMSG_CONNECT_IND_7

8

CC_IDMSG_CONNECT_IND_8

9

CC_IDMSG_RECONNECT_IND_9

10

CC_IDMSG_DISCONNECTED_IND_10

11


12


13

CC_IDMSG_DISCONNECT_DONE_IND_13

14


15


16

CC_IDMSG_PRE_DISC_CAUSE_16

17

CC_IDMSG_PRE_DISC_CAUSE_17

18

CC_IDMSG_DIGIT_BEGIN_IND_18

19

CC_IDMSG_DIGIT_END_IND_19

20

CC_IDMSG_DIGIT_END_IND_20

21

CC_IDMSG_DIGIT_END_NO_TERM_21

22

CC_IDMSG_TONE_IND_22

23

CC_IDMSG_FEATURE_IND_23

24

CC_IDMSG_MODIFY_DONE_IND_24

25

CC_IDMSG_MODIFY_MODE_DONE_IND_25

26

CC_IDMSG_INBAND_MSG_RCVD_IND_26

27

CC_IDMSG_INBAND_MSG_DONE_IND_27

28

CC_IDMSG_UPD_CALL_INFO_IND_28

29

CC_IDMSG_GEN_NTK_ALERT_EVENT_29

30

CC_IDMSG_VOICE_MODE_EVENT_30

31

CC_IDMSG_VOICE_MODE_EVENT_31

32

CC_IDMSG_DIALING_COMPLETE_IND_32

33

CC_IDMSG_DIGITS_DONE_IND_33

34

CC_IDMSG_DIGITS_DONE_IND_34

35

CC_IDMSG_VBD_XMIT_DONE_IND_35

36

CC_IDMSG_FWD_SETUP_IND_36


DB-2347


Table 369

CCAPI Individual Debug Values (continued)

Value


37

CC_IDMSG_RSVP_DONE_IND_37

38

CC_IDMSG_AUDIT_RSP_IND_38

39

CC_IDMSG_XFR_STATUS_IND_39

40

CC_IDMSG_XFR_STATUS_IND_40

41

CC_IDMSG_XFR_DONE_IND_41

42


43


44

CC_IDMSG_TGT_CID_ACTIVE_RCD_44

45

CC_IDMSG_MODIFY_MEDIA_IND_45

46

CC_IDMSG_MODIFY_MEDIA_ACK_IND_46

47

CC_IDMSG_MODIFY_MEDIA_REJ_IND_47

48

CC_IDMSG_MODEM_CALL_START_IND_48

49

CC_IDMSG_MODEM_CALL_DONE_IND_49

50

CC_IDMSG_ACCT_STATUS_IND_50

51

CC_IDMSG_NW_STATUS_IND_51

52

CC_IDMSG_DESTINFO_IND_52

53

CC_IDMSG_LOOPBACK_DONE_IND_53

54

CC_IDMSG_RT_PACKET_STATS_IND_54

55

CC_IDMSG_CUT_PROGRESS_IND_55

56

CC_IDMSG_CUT_PROGRESS_IND_56

57

CC_IDMSG_PROCEEDING_IND_57

58

CC_IDMSG_FACILITY_IND_58

59

CC_IDMSG_INFO_IND_59

60

CC_IDMSG_PROGRESS_IND_60

61

CC_IDMSG_USERINFO_IND_61

62

CC_IDMSG_DISC_PROG_IND_62

63

CC_IDMSG_DISC_PROG_IND_63

64

CC_IDMSG_PING_DONE_IND_64

65

CC_IDMSG_COT_TEST_DONE_IND_65

66

CC_IDMSG_PROCESS_DONE_IND_66

67

CC_IDMSG_ASSOCIATED_IND_67

68

CC_IDMSG_SUSPEND_IND_68

69

CC_IDMSG_SUSPEND_ACK_IND_69

70

CC_IDMSG_SUSPEND_REJ_IND_70

71

CC_IDMSG_RESUME_IND_71

72

CC_IDMSG_RESUME_ACK_IND_72


DB-2348

May 2008


Table 369


Value


73

CC_IDMSG_RESUME_REJ_IND_73

74

CC_IDMSG_IF_SETUP_REQ_PRIV_74

75

CC_IDMSG_IF_SETUP_REQ_PRIV_75

76

CC_IDMSG_IF_ALLOCATE_DSP_76

77

CC_IDMSG_CONNECT_77

78

CC_IDMSG_CONNECT_78

79

CC_IDMSG_PING_79

80

CC_IDMSG_DISCONNECT_80

81


82


83

CC_IDMSG_ALERT_83

84

CC_IDMSG_ALERT_84

85

CC_IDMSG_CUT_PROGRESS_85

86


87


88

CC_IDMSG_DISC_PROG_88

89

CC_IDMSG_DISC_PROG_89

90

CC_IDMSG_SET_PEER_90

91

CC_IDMSG_SET_PEER_91

92

CC_IDMSG_PROCEEDING_92

93

CC_IDMSG_SETUP_REQ_93

94


95


96


97


98


99


100


101


102

CC_IDMSG_SETUP_ACK_102

103

CC_IDMSG_FACILITY_103

104

CC_IDMSG_TRANSFER_REQ_104

105

CC_IDMSG_GET_CONSULT_ID_105

106

CC_IDMSG_FORWARD_TO_106

107

CC_IDMSG_INFO_107

108

CC_IDMSG_NOTIFY_108


DB-2349


Table 369


Value


109

CC_IDMSG_PROGRESS_109

110

CC_IDMSG_PRE_DISC_110

111

CC_IDMSG_PRE_DISC_111

112

CC_IDMSG_USER_INFO_112

113

CC_IDMSG_MODIFY_113

114

CC_IDMSG_DIGIT_114

115

CC_IDMSG_DIGIT_DIAL_115

116

CC_IDMSG_DIGIT_DIAL_STOP_116

117

CC_IDMSG_FEATURE_117

118

CC_IDMSG_FEATURE_ENABLE_118

119

CC_IDMSG_ASSOCIATE_STREAM_119

120

CC_IDMSG_ASSOCIATE_STREAM_120

121

CC_IDMSG_DISASSOCIATE_STREAM_121

122

CC_IDMSG_DISASSOCIATE_STREAM_122

123

CC_IDMSG_GENERATE_TONE_INFO_123

124

CC_IDMSG_SET_DIGIT_TIMEOUTS_124

125

CC_IDMSG_SET_DIGIT_TIMEOUTS_125

126

CC_IDMSG_SUSPEND_126

127

CC_IDMSG_SUSPEND_ACK_127

128

CC_IDMSG_SUSPEND_REJ_128

129

CC_IDMSG_RESUME_129

130

CC_IDMSG_RESUME_ACK_130

131

CC_IDMSG_RESUME_REJ_131

132

CC_IDMSG_UPDATE_REDIRECT_NUM_132

133

CC_IDMSG_BABBLER_AUDIT_133

134

CC_IDMSG_CONFERENCE_CREATE_134

135


136


137

CC_IDMSG_CONFERENCE_DESTROY_137

138


139


140

CC_IDMSG_LOOPBACK_140

141

CC_IDMSG_COT_TEST_141

142

CC_IDMSG_HANDOFF_142

143

CC_IDMSG_APP_RETURN_143

144

CC_IDMSG_T38_FAX_START_144


DB-2350

May 2008


Table 369


Value


145

CC_IDMSG_T38_FAX_DONE_145

146

CC_IDMSG_CALL_PREEMPT_IND_146

Command Default


Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(6)NA2


12.2(11)T


12.3(8)T

The all, default, detail, call, informational, software, individual, function, protoheaders, and service keywords were added.

12.4(4)XC

The range for the individual keyword was extended to 146, to include logs for call preemption indication information.

12.4(9)T


12.2SX


Examples

The following examples show output for variations of the debug voip ccapi command: •

debug voip ccapi detail on the Originating Gateway: Example, page 2352

•

debug voip ccapi detail on the Terminating Gateway: Example, page 2353

•

debug voip ccapi inout on the Originating Gateway: Example, page 2355

•

debug voip ccapi service on the Terminating Gateway: Example, page 2359

•

debug voip ccapi individual 146 on the Originating Gateway: Example, page 2359

For these examples, the topology shown in Figure 1 is used. Network Topology for debug voip ccapi Output Examples

T1 PRI

PSTN

FXS

V Cisco 3745 originating gateway

VoIP network

V Cisco 3660 terminating gateway

103302

Figure 1


DB-2351


debug voip ccapi detail on the Originating Gateway: Example Router# debug voip ccapi detail voip ccapi detail debugging is on Router# *Apr 18 20:35:35.779: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common: Interface Type=13, Protocol=0 *Apr 18 20:35:35.779: //-1/ABCE697D8005/CCAPI/ccCheckClipClir: Calling Party Number Is User Provided *Apr 18 20:35:35.779: //11/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=TRUE) *Apr 18 20:35:35.779: //11/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Total Call Count=1

The following event shows that the CallEntry ID 11 is used for the incoming call leg. *Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry: Incoming=TRUE, Call Id=11 *Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_setupind_registration_lookup: Matching Parameters; Called Number=83103, Call Transfer Consult Id= *Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_setupind_registration_lookup: No Matching Node *Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/ccCheckClipClir: Calling Party Number Is User Provided *Apr 18 20:35:35.779: //12/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=FALSE)

The following event shows that the incoming call leg with CallEntry ID 11 is bound to the outgoing call leg with CallEntry ID 12. *Apr 18 20:35:35.779: //11/ABCE697D8005/CCAPI/cc_peer_bind: Bind=TRUE, Binder Call Id=11, Bindee Call Id=12

The next event shows that CallEntry ID 12 is used for the outgoing call leg. *Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry: Incoming=FALSE, Call Id=12 *Apr 18 20:35:35.779: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data: data_mode=0x10082

The next event shows an IP address for a remote device on the outgoing call leg, which indicates that this is the VoIP call leg. *Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_incr_if_call_volume: Remote IP Address=172.16.13.81, Hwidb=FastEthernet0/0 *Apr 18 20:35:35.779: //12/ABCE697D8005/CCAPI/cc_incr_if_call_volume: Total Call Count=1, Voip Call Count=1, MMoip Call Count=0 *Apr 18 20:35:35.795: //11/ABCE697D8005/CCAPI/ccCallGetContext: Context=0x652C0168, Call Id=11 *Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect: Start Calling Accounting; Call Entry(Incoming=TRUE) *Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect: Cause Value=16, Call Entry(Disconnect Cause=16) *Apr 18 20:36:31.419: //11/ABCE697D8005/CCAPI/ccCallDisconnect: Call Entry(Disconnect Cause=16)


DB-2352

May 2008


At this point, the CallEntry ID changes as the call accounting process begins. The accounting data is sent over the outgoing call leg. The GUID, which identifies the unique call, remains the same. *Apr 18 20:36:31.419: //12/ABCE697D8005/CCAPI/ccCallDisconnect: Start Calling Accounting; Call Entry(Incoming=FALSE) *Apr 18 20:36:31.419: //12/ABCE697D8005/CCAPI/ccCallDisconnect: Cause Value=16, Call Entry(Disconnect Cause=0)

The change of the CallEntry ID indicates that the call is using the incoming call leg, which is the POTS call leg in this case. *Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/ccCallGetVoipFlag: Data Bitmask=0x1, Call Id=11 *Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/ccCallGetVoipFlag: Flag=FALSE *Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry: Incoming=TRUE *Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry: ccFreeRawMsgInfo=0x63FF8198 *Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry: Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=TRUE) *Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry: Total Call Count=0 *Apr 18 20:36:31.423: //11/ABCE697D8005/CCAPI/cc_delete_call_entry: Deleting profileTable[0x64F44700]

The next line shows the impairment calculation. This is the only CCAPI debug command that shows impairment. *Apr 18 20:36:31.423: //-1/ABCE697D8005/CCAPI/g113_calculate_impairment: (delay=91(ms), loss=0%), Io=0 Iq=0 Idte=0 Idd=2 Ie=10 Itot=12 *Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/ccCallGetVoipFlag: Data Bitmask=0x1, Call Id=12 *Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/ccCallGetVoipFlag: Flag=FALSE *Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_decr_if_call_volume: Remote IP Address=172.16.13.81, Hwidb=FastEthernet0/0 *Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_decr_if_call_volume: Total Call Count=0, Voip Call Count=0, MMoip Call Count=0 *Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry: Incoming=FALSE *Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_call_entry: Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=FALSE) *Apr 18 20:36:31.423: //12/ABCE697D8005/CCAPI/cc_delete_call_entry: Deleting profileTable[0x652E3310] *Apr 18 20:36:31.427: //12/xxxxxxxxxxxx/CCAPI/cc_get_call_entry: Call Entry Is Not Found

debug voip ccapi detail on the Terminating Gateway: Example Router# debug voip ccapi detail voip ccapi detail debugging is on Router# *May 1 18:58:26.251: //-1/xxxxxxxxxxxx/CCAPI/cc_api_supported_data: data_mode=0x10082 *May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry: Call Entry Is Not Found *May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common: Interface Type=0, Protocol=1 *May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/ccCheckClipClir: Calling Party Number Is User Provided


DB-2353


The following line shows the attributes of the calling number: *May 1 18:58:26.255: //-1/ABCE697D8005/CCAPI/cc_api_call_setup_ind_common: After Number Translation Checking: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed), Called Number=3600(TON=Unknown, NPI=Unknown) *May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=TRUE) *May 1 18:58:26.255: //8/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Total Call Count=1 *May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry: Incoming=TRUE, Call Id=8

The following line shows the IP address of the originating gateway: *May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_incr_if_call_volume: Remote IP Address=172.16.13.175, Hwidb=FastEthernet0/0 *May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_incr_if_call_volume: Total Call Count=1, Voip Call Count=1, MMoip Call Count=0 *May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_setupind_registration_lookup: Matching Parameters; Called Number=3600, Call Transfer Consult Id= *May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/cc_setupind_registration_lookup: No Matching Node *May 1 18:58:26.255: //8/ABCE697D8005/CCAPI/ccCheckClipClir: Calling Party Number Is User Provided *May 1 18:58:26.259: //9/xxxxxxxxxxxx/CCAPI/cc_insert_call_entry: Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=FALSE) *May 1 18:58:26.259: //8/ABCE697D8005/CCAPI/cc_peer_bind: Bind=TRUE, Binder Call Id=8, Bindee Call Id=9 *May 1 18:58:26.259: //9/ABCE697D8005/CCAPI/cc_insert_guid_pod_entry: Incoming=FALSE, Call Id=9 *May 1 18:58:26.259: //9/ABCE697D8005/CCAPI/cc_set_voice_port_value: CC_IF_TELEPHONY: Echo=0, Playout=0 *May 1 18:58:26.263: //9/ABCE697D8005/CCAPI/ccCallGetContext: Context=0x64B6BB5C, Call Id=9 *May 1 18:59:21.871: //8/ABCE697D8005/CCAPI/ccCallDisconnect: Start Calling Accounting; Call Entry(Incoming=TRUE) *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallDisconnect: Cause Value=16, Call Entry(Disconnect Cause=16) *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallDisconnect: Call Entry(Disconnect Cause=16) *May 1 18:59:21.875: //9/ABCE697D8005/CCAPI/ccCallDisconnect: Start Calling Accounting; Call Entry(Incoming=FALSE) *May 1 18:59:21.875: //9/ABCE697D8005/CCAPI/ccCallDisconnect: Cause Value=16, Call Entry(Disconnect Cause=0)

The next line shows the impairment calculation. This is the only CCAPI debug command that shows impairment. *May 1 18:59:21.875: //-1/ABCE697D8005/CCAPI/g113_calculate_impairment: (delay=99(ms), loss=0%), Io=0 Iq=0 Idte=0 Idd=2 Ie=10 Itot=12 *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallGetVoipFlag: Data Bitmask=0x1, Call Id=8 *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/ccCallGetVoipFlag: Flag=FALSE *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_decr_if_call_volume: Remote IP Address=172.16.13.175, Hwidb=FastEthernet0/0 *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_decr_if_call_volume: Total Call Count=0, Voip Call Count=0, MMoip Call Count=0 *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry:


DB-2354

May 2008


Incoming=TRUE *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry: ccFreeRawMsgInfo=0x644EB850 Router# *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry: Total Call Count=1, Call Entry(Call Count On=FALSE, Incoming Call=TRUE) *May 1 18:59:21.875: //8/ABCE697D8005/CCAPI/cc_delete_call_entry: Total Call Count=0 *May 1 18:59:21.879: //8/ABCE697D8005/CCAPI/cc_delete_call_entry: Deleting profileTable[0x64B78600] *May 1 18:59:21.879: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry: Call Entry Is Not Found *May 1 18:59:21.879: //8/xxxxxxxxxxxx/CCAPI/cc_get_call_entry: Call Entry Is Not Found Router# *May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/ccCallGetVoipFlag: Data Bitmask=0x1, Call Id=9 *May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/ccCallGetVoipFlag: Flag=FALSE *May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_api_call_disconnect_done: Prefix Is Not Defined From Peer; Peer=3600, Called Number=3600 *May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_guid_pod_entry: Incoming=FALSE *May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_call_entry: Total Call Count=0, Call Entry(Call Count On=FALSE, Incoming Call=FALSE) *May 1 18:59:24.587: //9/ABCE697D8005/CCAPI/cc_delete_call_entry: Deleting profileTable[0x6453F228]

debug voip ccapi inout on the Originating Gateway: Example Router# debug voip ccapi inout voip ccapi inout debugging is on Router# *Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/cc_api_display_ie_subfields: cc_api_call_setup_ind_common: acme-username= ----- ccCallInfo IE subfields ----acme-ani=4085550111 acme-anitype=2 acme-aniplan=1 acme-anipi=0 acme-anisi=1 dest=83103 acme-desttype=0 acme-destplan=0 acme-rdn= acme-rdntype=-1 acme-rdnplan=-1 acme-rdnpi=-1 acme-rdnsi=-1 acme-redirectreason=-1

The following lines show information about the calling and called numbers. The network presentation indicator (NPI) shows the type of transmission. The Incoming Dial-Peer field shows that the incoming dial peer has been matched. *Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/cc_api_call_setup_ind_common: Interface=0x64F26F10, Call Info( Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed), Called Number=83103(TON=Unknown, NPI=Unknown), Calling Translated=FALSE, Subsriber Type Str=RegularLine, FinalDestinationFlag=TRUE,


DB-2355


Incoming Dial-peer=1, Progress Indication=NULL(0), Calling IE Present=TRUE, Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1 *Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/ccCheckClipClir: In: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed) *Apr 18 20:42:19.347: //-1/9C5A9CA88009/CCAPI/ccCheckClipClir: Out: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed)

In the following event, the call leg is established. The CallEntry ID field changes from -1 to 19. *Apr 18 20:42:19.347: //19/9C5A9CA88009/CCAPI/cc_api_call_setup_ind_common: Set Up Event Sent; Call Info(Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed), Called Number=83103(TON=Unknown, NPI=Unknown)) *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_process_call_setup_ind: Event=0x63FF4730 *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetContext: Context=0x652A9858 *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_process_call_setup_ind: >>>>CCAPI handed cid 19 with tag 1 to app "Default" *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallProceeding: Progress Indication=NULL(0) *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest: Destination=, Calling IE Present=TRUE, Mode=0, Outgoing Dial-peer=3600, Params=0x652AA4A8, Progress Indication=NULL(0) *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCheckClipClir: In: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed) *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCheckClipClir: Out: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed) *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest: Destination Pattern=360., Called Number=3600, Digit Strip=FALSE *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccCallSetupRequest: Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed), Called Number=3600(TON=Unknown, NPI=Unknown), Redirect Number=, Display Info= Account Number=, Final Destination Flag=TRUE, Guid=9C5A9CA8-5243-11D6-8009-00059A3A15A0, Outgoing Dial-peer=3600 *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/cc_api_display_ie_subfields: ccCallSetupRequest: cisco-username= ----- ccCallInfo IE subfields ----cisco-ani=4085550111 cisco-anitype=2 cisco-aniplan=1 cisco-anipi=0 cisco-anisi=1 dest=3600 cisco-desttype=0 cisco-destplan=0 cisco-rdn= cisco-rdntype=-1 cisco-rdnplan=-1 cisco-rdnpi=-1 cisco-rdnsi=-1 cisco-redirectreason=-1


DB-2356

May 2008


In the following lines, the outgoing dial peer is matched: *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccIFCallSetupRequestPrivate: Interface=0x63EAF24C, Interface Type=1, Destination=, Mode=0x0, Call Params(Calling Number=4085550111(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed), Called Number=3600(TON=Unknown, NPI=Unknown), Calling Translated=FALSE, Subsriber Type Str=RegularLine, FinalDestinationFlag=TRUE, Outgoing Dial-peer=3600, Call Count On=FALSE, Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=) *Apr 18 20:42:19.351: //20/9C5A9CA88009/CCAPI/ccIFCallSetupRequestPrivate: SPI Call Setup Request Is Success; Interface Type=1, FlowMode=1 *Apr 18 20:42:19.351: //20/9C5A9CA88009/CCAPI/ccCallSetContext: Context=0x652AA458 *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag: Outgoing Dial-peer=3600 *Apr 18 20:42:19.351: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag: Outgoing Dial-peer=3600 *Apr 18 20:42:19.367: //20/9C5A9CA88009/CCAPI/cc_api_call_proceeding: Interface=0x652F6388, Progress Indication=NULL(0)

The following lines show call progress. The progress and signal indications are shown. *Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/cc_api_call_cut_progress: Interface=0x652F6388, Progress Indication=INBAND(8), Signal Indication=SIGNAL RINGBACK(1), Cause Value=0 *Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/cc_api_call_cut_progress: Call Entry(Responsed=TRUE) *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccCallCutProgress: Progress Indication=INBAND(8), Signal Indication=SIGNAL RINGBACK(1), Cause Value=0 Voice Call Send Alert=FALSE, Call Entry(AlertSent=FALSE) *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccCallCutProgress: Call Entry(Responsed=TRUE)

The following lines show the tone generation information: *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccGenerateToneInfo: Stop Tone On Digit=FALSE, Tone=Null, Tone Direction=Network, Params=0x0, Call Id=19 *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccConferenceCreate: Conference Id=0x652F723C, Call Id1=19, Call Id2=20, Tag=0x0 *Apr 18 20:42:19.371: //20/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done: Conference Id=0x6, Source Interface=0x63EAF24C, Source Call Id=20, Destination Call Id=19, Disposition=0x0, Tag=0x0 *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/ccConferenceCreate: Call Entry(Conference Id=0x6, Destination Call Id=20) *Apr 18 20:42:19.371: //20/9C5A9CA88009/CCAPI/ccConferenceCreate: Call Entry(Conference Id=0x6, Destination Call Id=19) *Apr 18 20:42:19.371: //19/xxxxxxxxxxxx/CCAPI/cc_api_bridge_done: Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19, Destination Call Id=20, Disposition=0x0, Tag=0x0 *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_generic_bridge_done: Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19, Destination Call Id=20, Disposition=0x0, Tag=0x0 *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_api_caps_ind: Destination Interface=0x63EAF24C, Destination Call Id=20, Source Call Id=19, Caps(Codec=0x2887F, Fax Rate=0xBF, Vad=0x3, Modem=0x2, Codec Bytes=0, Signal Type=3) *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_api_caps_ind: Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms), Playout Max=300(ms), Fax Nom=300(ms)) *Apr 18 20:42:19.371: //19/9C5A9CA88009/CCAPI/cc_process_notify_bridge_done: Conference Id=0x6, Call Id1=19, Call Id2=20


DB-2357


*Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ind: Destination Interface=0x64F26F10, Destination Call Id=19, Source Call Id=20, Caps(Codec=0x4, Fax Rate=0x1, Vad=0x2, Modem=0x2, Codec Bytes=20, Signal Type=2) *Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ind: Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms), Playout Max=300(ms), Fax Nom=300(ms))

The following lines show codec information: *Apr 18 20:42:19.375: //20/9C5A9CA88009/CCAPI/cc_api_caps_ack: Destination Interface=0x64F26F10, Destination Call Id=19, Source Call Id=20, Caps(Codec=g729r8(0x4), Fax Rate=FAX_RATE_NONE(0x1), Vad=ON(0x2), Modem=ON(0x2), Codec Bytes=20, Signal Type=2, Seq Num Start=6872) *Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_caps_ack: Destination Interface=0x63EAF24C, Destination Call Id=20, Source Call Id=19, Caps(Codec=g729r8(0x4), Fax Rate=FAX_RATE_NONE(0x1), Vad=ON(0x2), Modem=ON(0x2), Codec Bytes=20, Signal Type=2, Seq Num Start=6872) *Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_voice_mode_event: Call Id=19 *Apr 18 20:42:19.375: //19/9C5A9CA88009/CCAPI/cc_api_voice_mode_event: Call Entry(Context=0x652A9858)

The following lines show progress indication information. In this case, the event shows that the destination is not ISDN. *Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/cc_api_call_connected: Interface=0x652F6388, Data Bitmask=0x0, Progress Indication=DESTINATION IS NON ISDN(2), Connection Handle=0 *Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/cc_api_call_connected: Call Entry(Connected=TRUE, Responsed=TRUE, Retry Count=0) *Apr 18 20:42:26.855: //19/9C5A9CA88009/CCAPI/ccCallConnect: Progress Indication=DESTINATION IS NON ISDN(2), Data Bitmask=0x0 *Apr 18 20:42:26.855: //19/9C5A9CA88009/CCAPI/ccCallConnect: Call Entry(Connected=TRUE, Responsed=TRUE) *Apr 18 20:42:26.855: //20/9C5A9CA88009/CCAPI/ccSaveDialpeerTag: Incoming Dial-peer=1 *Apr 18 20:42:26.859: //19/9C5A9CA88009/CCAPI/ccSaveDialpeerTag: Outgoing Dial-peer=3600 *Apr 18 20:42:26.859: //20/9C5A9CA88009/CCAPI/ccCallFeature: Feature Type=24, Call Id=20

This event shows that the call is disconnected. *Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnected: Cause Value=16, Interface=0x64F26F10, Call Id=19 *Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnected: Call Entry(Responsed=TRUE, Cause Value=16, Retry Count=0) *Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccConferenceDestroy: Conference Id=0x6, Tag=0x0 *Apr 18 20:43:16.795: //20/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done: Conference Id=0x6, Source Interface=0x63EAF24C, Source Call Id=20, Destination Call Id=19, Disposition=0x0, Tag=0x0 *Apr 18 20:43:16.795: //19/xxxxxxxxxxxx/CCAPI/cc_api_bridge_drop_done: Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19, Destination Call Id=20, Disposition=0x0, Tag=0x0 *Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_generic_bridge_done: Conference Id=0x6, Source Interface=0x64F26F10, Source Call Id=19, Destination Call Id=20, Disposition=0x0, Tag=0x0 *Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccCallDisconnect: Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=16) *Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/ccCallDisconnect: Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16) *Apr 18 20:43:16.795: //19/9C5A9CA88009/CCAPI/cc_api_get_transfer_info:


DB-2358

May 2008


Transfer Number Is Null *Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/ccCallDisconnect: Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0) *Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/ccCallDisconnect: Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16) *Apr 18 20:43:16.795: //20/9C5A9CA88009/CCAPI/cc_api_get_transfer_info: Transfer Number Is Null *Apr 18 20:43:16.803: //20/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done: Disposition=0, Interface=0x652F6388, Tag=0x0, Call Id=20, Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0) *Apr 18 20:43:16.803: //20/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done: Call Disconnect Event Sent *Apr 18 20:43:16.803: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done: Disposition=0, Interface=0x64F26F10, Tag=0x0, Call Id=19, Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0) *Apr 18 20:43:16.803: //19/9C5A9CA88009/CCAPI/cc_api_call_disconnect_done: Call Disconnect Event Sent

debug voip ccapi service on the Terminating Gateway: Example Router# debug voip ccapi service voip ccapi service debugging is on *May 1 19:08:41.803: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search: Searching Node; Called Number=3600, Call Transfer Consult Id=

This debug shows noncall related events. In this case, information about the timer is shown. *May 1 19:08:48.027: //-1/xxxxxxxxxxxx/CCAPI/cc_handle_periodic_timer: Calling The Callback, ccTimerctx=0x63B368C0 *May 1 19:08:48.027: //-1/xxxxxxxxxxxx/CCAPI/ccTimerStart: ccTimerctx=0x63B368C0 *May 1 19:10:08.615: //-1/xxxxxxxxxxxx/CCAPI/cc_api_icpif: ExpectFactor=0xA

debug voip ccapi individual 146 on the Originating Gateway: Example

This debug shows the preemption tone timer getting initiated. *Aug 24 18:28:16.919: //18958/B37648B6AF48/CCAPI/cc_api_call_preempt_ind: PreemptionToneTimer=10(s)


DB-2359

Debug Commands debug voip confmsp

debug voip confmsp To display debugging information from the Conference Media Service Provider (CONFMSP) and its related applications, use the debug voip confmsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip confmsp no debug voip confmsp

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Examples

The following is sample output from the debug voip confmsp command: Router# debug voip confmsp CONFMSP debugging is on . . . 00:06:44:confmsp_setup_request:callID (6), 00:06:44:confmsp_setup_request:conf structure (63DD27E4) created, 00:06:44:confmsp_bridge:confID(4), callIDs(6,5) xmitFunc 61D46D4C, dstIF 64912880 00:06:44:confmsp_bridge:confID(4), callIDs(6,5) event queued 00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING 00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1 00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1 00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP, event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE 00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE 00:06:44:confmsp_connect_response:found conf (63DD27E4) dsmp ret is 1 00:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE, event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 65241B34 00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE, event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED 00:06:44:confmsp_bridge:confID(5), callIDs(6,7) xmitFunc 61D46D4C, dstIF 64912880 00:06:44:confmsp_bridge:confID(5), callIDs(6,7) event queued 00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING 00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1 00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1


DB-2360

May 2008


00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP, event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE 00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE 00:06:44:confmsp_connect_response:found conf (6358A338) dsmp ret is 1 00:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE, event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 63588E70 00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE, event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED 00:06:44:confmsp_bridge:confID(6), callIDs(6,8) xmitFunc 61D46D4C, dstIF 64912880 00:06:44:confmsp_bridge:confID(6), callIDs(6,8) event queued 00:06:44:confmsp_act_bridge: state = CONFMSP_STATE_SETUP, event=EV_CONFMSP_BRIDGING 00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1 00:06:44:confmsp_act_bridge:codec 1, codec_bytes 160, vad 1 00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_SETUP, event:EV_CONFMSP_BRIDGING, next_state:CONFMSP_STATE_CONNECT_CONFEREE 00:06:44:confmsp_get_dsmp_req_status:condition to be returned FALSE 00:06:44:confmsp_connect_response:found conf (6358CE50) dsmp ret is 1 00:06:44:confmsp_act_bridge_success: state = CONFMSP_STATE_CONNECT_CONFEREE, event=EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS confmsp_caps_ind:context = 63DD2524 00:06:44:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECT_CONFEREE, event:EV_CONFMSP_CNFRE_CONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_CONNECTED 00:07:28:confmsp_bdrop:confID(4), callIDs(6,5) 00:07:28:confmsp_bdrop:confID(4), callIDs(6,5) event queued 00:07:28:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP 00:07:28:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED, event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE 00:07:28:confmsp_get_dsmp_req_status:condition to be returned FALSE 00:07:28:confmsp_disconnect_response:found conf (63DD27E4) 00:07:28:confmsp_connect_response:found conf (63DD27E4) dsmp ret is 10 00:07:28:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE, event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS 00:07:28:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE, event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED 00:07:28:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED, event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NO_STATE_CHANGE 00:07:29:confmsp_bdrop:confID(6), callIDs(6,8) 00:07:29:confmsp_bdrop:confID(6), callIDs(6,8) event queued 00:07:29:confmsp_bdrop:confID(5), callIDs(6,7) 00:07:29:confmsp_bdrop:confID(5), callIDs(6,7) event queued 00:07:29:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP 00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED, event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE 00:07:29:confmsp_get_dsmp_req_status:condition to be returned FALSE 00:07:29:confmsp_act_bdrop: state = CONFMSP_STATE_CONNECTED, event=EV_CONFMSP_BRIDGEDROP 00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_CONNECTED, event:EV_CONFMSP_BRIDGEDROP, next_state:CONFMSP_STATE_DISCONNECT_CONFEREE 00:07:29:confmsp_get_dsmp_req_status:condition to be returned FALSE 00:07:29:confmsp_disconnect_response:found conf (6358CE50) 00:07:29:confmsp_connect_response:found conf (6358CE50) dsmp ret is 10 00:07:29:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE, event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS 00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE, event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED


DB-2361


00:07:29:confmsp_act_terminate: state = CONFMSP_STATE_BRIDGE_DROPPED, event=CNFSM_LAMBDA_EVENT 00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED, event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NULL_STATE 00:07:29:confmsp_free_conf:freeing 6358CE50 00:07:29:confmsp_disconnect_response:found conf (6358A338) 00:07:29:confmsp_connect_response:found conf (6358A338) dsmp ret is 10 00:07:29:confmsp_act_bdrop_success: state = CONFMSP_STATE_DISCONNECT_CONFEREE, event=EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS 00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_DISCONNECT_CONFEREE, event:EV_CONFMSP_CNFRE_DISCONNECT_RESP_SUCCESS, next_state:CONFMSP_STATE_BRIDGE_DROPPED 00:07:29:confmsp_act_terminate: state = CONFMSP_STATE_BRIDGE_DROPPED, event=CNFSM_LAMBDA_EVENT 00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED, event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NULL_STATE 00:07:29:confmsp_free_conf:freeing 6358A338 00:07:29:confmsp_disconnect:callID (6) 00:07:29:confmsp_disconnect:callID (6) event queued 00:07:29:confmsp_act_disconnected: state = CONFMSP_STATE_BRIDGE_DROPPED, event=EV_CONFMSP_DISCONNECT 00:07:29:CNFSM:cur_container:confmsp container, cur_state:CONFMSP_STATE_BRIDGE_DROPPED, event:EV_CONFMSP_DISCONNECT, next_state:CNFSM_NULL_STATE 00:07:29:confmsp_free_conf:freeing 63DD27E4


DB-2362

May 2008

Debug Commands debug voip dcapi

debug voip dcapi To debug the device control application programming interface (DCAPI), use the debug voip dcapi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip dcapi [error | inout] no debug voip dcapi [error | inout]

Syntax Description

error

(Optional) Displays error logs in the DCAPI.

inout

(Optional) Displays the execution path through the DCAPI.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Usage Guidelines

The debug voip dcapi error command traces the error logs in the DCAPI, which is the software layer that interfaces the SCCP Telephony Control Application (STCAPP) with the Cisco CallManager using the Skinny Client Control Protocol (SCCP). Error logs are generated during normal call processing when there are insufficient resources, or when there are problems in the device control API. This debug command shows error events or unexpected behavior in system software. The debug voip dcapi inout command shows how a call executes through the software. This command traces the execution path through the DCAPI during communications with the SCCP service provider interface (SPI) and the call control API (CCAPI) that controls the physical voice port. You can use the output from this command to understand how devices are being handled by the APIs and to see the call setup and teardown operations performed on the telephony call leg.

Examples

Following is sample output from the debug voip dcapi inout command during call setup: Router# debug voip dcapi inout *Jan 27 16:26:23.957: dc_api_device_set_ringer_res: Set Ringer message success *Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_stop_tone_res: *Jan 27 16:26:23.957: dc_api_device_stop_tone_res: Stop Tone message success *Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_media_open_rcv_channel: *Jan 27 16:26:23.957: dc_api_media_open_rcv_channel: evt DC_EV_MEDIA_OPEN_RCV_CHNL is successsfully enqueued to app *Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_stop_tone_res: *Jan 27 16:26:23.957: dc_api_device_stop_tone_res: Stop Tone message success


DB-2363

Debug Commands debug voip dcapi

*Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_call_state_res: *Jan 27 16:26:23.957: dc_api_device_call_state_res: Call State message success *Jan 27 16:26:23.957: //-1/xxxxxxxxxxxx/CCAPI/dc_api_device_call_info_res:


Related Commands

debug voip dcapi Field Descriptions

Field

Description

nn:nn:nn:

Timestamp time in hours (military format), minutes, and seconds that indicates when the DCAPI event occurred.

dc_api_message:

The DCAPI event in which the SCCP SPI translation occurred.

Command

Description


Debugs STCAPP events.


Debugs STCAPP functions.


DB-2364

May 2008

Debug Commands debug voip dialpeer

debug voip dialpeer To display information about the voice dial peers, use the debug voip dialpeer command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip dialpeer [all | default | detail | error [call [informational] | software [informational]] | | function | inout] no debug voip dialpeer

Syntax Description

all

(Optional) Displays all dialpeer debugging messages.

default

(Optional) Displays dialpeer inout and error debugging messages. This option also runs if no keywords are added.

detail

(Optional) Displays detailed dialpeer information.

error

(Optional) Displays dialpeer error messages.

call


informational


software

(Optional) Displays software processing errors.

function

(Optional) Displays dialpeer functions.

inout

(Optional) Displays dialpeer in/out functions.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug dialpeer command.

12.2SX


Usage Guidelines

Disable console logging and use buffered logging before using the debug voip dialpeer command. Using the debug voip dialpeer command generates a large volume of debugging messages, which can affect router performance.

Examples

The following examples show output for variations of the debug voip dialpeer command: •

debug voip dialpeer detail on the Originating Gateway, page 2366

•

debug voip dialpeer inout on the Terminating Gateway, page 2367


DB-2365


For these examples, the topology shown in Figure 2 is used. Network Topology for debug voip dialpeer Output Examples

T1 PRI

PSTN

FXS


VoIP network

V Cisco 3660 terminating gateway

103302

Figure 2

debug voip dialpeer detail on the Originating Gateway Router# debug voip dialpeer detail voip dialpeer detail debugging is on Router#

The following event identifies the called number: *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore: Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=83103 *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype: Is Incoming=TRUE, Number Expansion=FALSE *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore: Dial String=83103, Expanded String=83103, Calling Number= Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

The following event identifies the incoming dial peer and shows that it has been matched: *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer: Result=Success(0); Incoming Dial-peer=1 Is Matched *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore: Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=83103 *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype: Is Incoming=TRUE, Number Expansion=FALSE *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore: Dial String=83103, Expanded String=83103, Calling Number= Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_FAX *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore: Result=-1 *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore: Match Rule=DP_MATCH_ANSWER; Calling Number=4085550111 *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype: Is Incoming=TRUE, Number Expansion=FALSE *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore: Dial String=, Expanded String=, Calling Number=4085550111T Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_FAX *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore: Result=-1 *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore: Match Rule=DP_MATCH_ORIGINATE; Calling Number=4085550111 *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchPeertype: Is Incoming=TRUE, Number Expansion=FALSE *Apr 18 21:07:35.291: //-1/xxxxxxxxxxxx/DPM/dpMatchCore: Dial String=, Expanded String=, Calling Number=4085550111T Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_FAX *Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/dpMatchCore: Result=-1


DB-2366

May 2008


The following event shows the number expansion. This is the only dial peer debug command that shows the number expansion. *Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/dpMatchCore: Dial String=83103, Expanded String=3600, Calling Number= Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH

The next few lines show matching for the outgoing dial peer. These lines show the matching sequence if the first match is not available. *Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer: Result=Success(0); Outgoing Dial-peer=3600 Is Matched *Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer: Result=Success(0); Outgoing Dial-peer=36 Is Matched *Apr 18 21:07:35.295: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer: Result=Success(0); Outgoing Dial-peer=360 Is Matched *Apr 18 21:07:35.295: //-1/23ED4B1B8010/DPM/dpMatchCore: Dial String=83103, Expanded String=3600, Calling Number= Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH

debug voip dialpeer inout on the Terminating Gateway Router# debug voip dialpeer inout voip dialpeer inout debugging is on

The following event shows the calling and called numbers: *May 1 19:32:11.731: //-1/6372E2598012/DPM/dpAssociateIncomingPeerCore: Calling Number=4085550111, Called Number=3600, Voice-Interface=0x0, Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE, Peer Info Type=DIALPEER_INFO_SPEECH

The following event shows the incoming dial peer: *May 1 19:32:11.731: //-1/6372E2598012/DPM/dpAssociateIncomingPeerCore: Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=100 *May 1 19:32:11.731: //-1/6372E2598012/DPM/dpAssociateIncomingPeerCore: Calling Number=4085550111, Called Number=3600, Voice-Interface=0x0, Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE, Peer Info Type=DIALPEER_INFO_SPEECH *May 1 19:32:11.731: //-1/6372E2598012/DPM/dpAssociateIncomingPeerCore: Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=100 *May 1 19:32:11.735: //-1/6372E2598012/DPM/dpMatchPeersCore: Calling Number=, Called Number=3600, Peer Info Type=DIALPEER_INFO_SPEECH *May 1 19:32:11.735: //-1/6372E2598012/DPM/dpMatchPeersCore: Match Rule=DP_MATCH_DEST; Called Number=3600 *May 1 19:32:11.735: //-1/6372E2598012/DPM/dpMatchPeersCore: Result=Success(0) after DP_MATCH_DEST *May 1 19:32:11.735: //-1/6372E2598012/DPM/dpMatchPeersMoreArg: Result=SUCCESS(0)

The following event shows the matched dial peers in the order of priority: List of Matched Outgoing Dial-peer(s): 1: Dial-peer Tag=3600 2: Dial-peer Tag=36

Related Commands

Command

Description

call-block (dial peer)

Enables blocking of incoming calls on the dial peer.

carrier-id (dial-peer)

Identifies the carrier handling the incoming call.


DB-2367


Command

Description

session target (ENUM)

Specifies the ENUM search table for the target session.

show dial-peer voice

Displays the configuration of the dial peer.

translation-profile (dial-peer)

Assigns a translation profile to the dial peer.

trunkgroup (dial-peer)

Assigns a trunk group to the dial peer.

trunk-group-label (dial-peer)

Identifies the trunk group handling the incoming call.


DB-2368

May 2008

Debug Commands debug voip dsm

debug voip dsm To troubleshoot the DSP stream manager (DSM) subsystem, use the debug voip dsm command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip dsm [all | dsp | error | rtp | session | stats | tone | vofr] no debug voip dsm

Syntax Description

all

(Optional) Displays all DSM debugging messages.

dsp

(Optional) Enables a digital signal processor (DSP) message trace.

error

(Optional) Displays DSM error messages.

rtp

(Optional) Enables Real-Time Protocol (RTP) debugging on DSM.

session

(Optional) Enables session debugging.

stats

(Optional) Displays DSM statistics.

tone

(Optional) Displays tone debugging.

vofr

(Optional) Enables Voice over Frame Relay (VoFR) debugging on the VPM.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug vtsp dsp command.

12.3(14)T

The vofr keyword is no longer available in Cisco IOS Release 12.3(14)T.

12.2SX


Usage Guidelines

To debug VoIP calls, use this command in conjunction with debug voip vtsp command and debug voip dsmp commands. All the related information for media processing is now available by using Distributed Stream Media Processor (DSMP). DSM is responsible for creating streams and issuing connections between them.

Examples

The following examples show output for variations of the debug voip dsm command: •

debug voip dsm session on the Originating Gateway, page 2370

•

debug voip dsm stats on the Terminating Gateway, page 2372

•

debug voip dsm Session of a VoIP Call in Transition to Connected State and in Transition from Connected to Disconnected State, page 2372


DB-2369


For these examples, the topology shown in Figure 3 is used. Network Topology for debug voip dsm Examples

T1 PRI

PSTN

FXS

V

VoIP network

Cisco 3745 originating gateway

V

103302

Figure 3

Cisco 3660 terminating gateway

debug voip dsm session on the Originating Gateway Router# debug voip dsm session DSP Stream Manager session debugging is on *Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:0:0/dsm_start_basic_sm: . *Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:8:4/dsm_start_basic_sm: dsp resource manager opened. ret 4 *Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:8:4/dsm_open_voice_and_set_params: . *Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:8:4/set_playout_dmgr: playout default

The following event shows the echo cancellation setting: *Apr 18 21:15:39.679: //-1/44A507668015/DSM:(2/1:23):0:8:4/dsm_dsp_echo_canceller_control: echo_cancel: 1 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsp_stream_mgr_play_tone: . *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_INIT E:E_DSM_CC_GEN_TONE] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_gen_tone: Tone is not on, ignoring *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_INIT] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_INIT E:E_DSM_CC_BRIDGE] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_bridge: .

The following event indicates that modem relay is not supported on the specified port, which is port 2/1:23: *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_bridge: Modem Relay NOT Supported on this end-point/voice-port. disabling it... *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGING] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGING E:E_DSM_CC_CAPS_IND] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: . *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDT 121],FaxRelay[122],CASsig[123],ClearChan[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: dtmf relay: mode=1, codec=1 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: Modem Relay NOT Supported on this end-point/voice-port disabling it... *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_


DB-2370

May 2008


em_redundancy 0, payload 103, modem_relay 0, gw-xid 0 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20, FaxRate 1, FaxBytes 20, FaxNsf 0xAD0051 SignalType 2 DtmfRelay 1, Modem 2, SeqNumStart 0x5A1 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: FORKING Parameters are forking mask: 0, simple_forking dec_mask: 0, complex_forking_codec_mask 0 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ind: playout: [ mode:1,init:60, min:40, max:200]. data_mode *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGING] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGING E:E_DSM_CC_CAPS_ACK] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ack: . *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ack: passthrough: cap_modem_proto 4, cap_modem_codec 1, cap dem_redundancy 0, payload 103, modem_relay 0, gw-xid 0 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_caps_ack: Named Telephone Event payload rcv 101, tx 101 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_switch_codec: Required codec is 16, current dsp codec is -1 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_switch_codec: codec = 16 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_PENDING_CODEC_SWITCH] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_PENDING_CODEC_SWITCH E:E_DSM_DS_PEND_SUCCESS] *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_act_pend_codec_success: . *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_open_voice_and_set_params: *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/set_playout_dmgr: playout default

The following event shows the echo cancellation setting: *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_dsp_echo_canceller_control: echo_cancel: 1

The following event shows that the codec has changed: *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_setup_stream_after_switch_codec_succ: codec change success *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_add_fork: . *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: add_fork=0 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_get_xmit_info_node: . *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: xmit func is 61A7CDC4, context is 64F42DA0 peer_c _id: 44, stream_count: 1, update_flag 0 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: The stream bit-mask is 1 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: The stream type is 0 *Apr 18 21:15:39.695: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_fork_info: The logical ssrc is 64 for stream 0 *Apr 18 21:15:39.699: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_update_stream_count: *Apr 18 21:15:39.699: g711_voice_count=0 g711_avt_count = 0 g711_voice_avt_count = 0 complex_voice_count = 1 complex_avt_count = 0 complex_voice_avt_count = 0 *Apr 18 21:15:39.699: //43/44A507668015/DSM:(2/1:23):0:8:4/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED]


DB-2371


debug voip dsm stats on the Terminating Gateway Router# debug voip dsm stats DSP Stream Manager stats debugging is on

The following event shows that the DSM is requesting statistics: *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_CC_REQ_PACK_STAT] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_cc_stats_req: . *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_cc_stats_req: -1->dmgr=0x645461E0, stats_reqs=0

The following events show statistics for DSM transmission, reception, delay, and errors: *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_DSP_GET_TX] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: . *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: -4->dmgr=0x645461E0,stats_reqs=3 *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_DSP_GET_RX] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: . *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: -4->dmgr=0x645461E0,stats_reqs=2 *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_DSP_GET_VP_DELAY] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: . *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: -4->dmgr=0x645461E0,stats_reqs=1 *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [B SM: R:FSM_OK -> S:S_DSM_BRIDGED] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_exec: [Feat SM: S:NONE B SM: S:S_DSM_BRIDGED E:E_DSM_DSP_GET_VP_ERROR] *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: . Router# *May 1 19:40:09.775: //43/7EE6F84B8016/DSM:(4/0/0):-1:1:1/dsm_act_packet_stats_res: -4->dmgr=0x645461E0,stats_reqs=0

debug voip dsm Session of a VoIP Call in Transition to Connected State and in Transition from Connected to Disconnected State

The following is sample output from the debug voip dsm command, with Cisco IOS Release 12.3(14)T software, when a VoIP call is in transition to the connected state: Router# debug voip dsm *Jun 8 20:10:33.205: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_create: . *Jun 8 20:10:33.209: //28/6F1FA7868003/DSM:(2/0:23):-1/set_echo_canceller_data: echo_cancel: 1 *Jun 8 20:10:33.209: //28/6F1FA7868003/DSM:(2/0:23):-1/set_echo_canceller_data: echo_flags: 55, echo_len: 512 *Jun 8 20:10:33.217: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_reserve_resource_cb: . *Jun 8 20:10:33.217: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_set_elog_enable: .


DB-2372

May 2008


*Jun 8 20:10:33.477: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_reinit_platform_info: . *Jun 8 20:10:33.477: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_reserve_resource_cb: . *Jun 8 20:10:33.485: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_bridge: . *Jun 8 20:10:33.485: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_bridge: *Jun 8 20:10:33.485: dsp_stream_mgr_bridge, src_call_id 28, dst_call_id 27 *Jun 8 20:10:33.485: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_bridge: creating packet streams *Jun 8 20:10:33.489: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_insert_conn_array_entry: dmgr->connArr.count = 2 *Jun 8 20:10:33.489: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_do_caps_ind: . *Jun 8 20:10:33.493: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_cap_ind_ack: src_call_id = 28, dst_call_id = 27, is_cap_ack = 1 *Jun 8 20:10:33.493: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_cap_ind_ack: src_call_id = 28, dst_call_id = 27, is_cap_ack = 0 *Jun 8 20:10:33.493: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_ind_negotiation: Caps in caps indication: *Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: playout: [ mode:1,init:60, min:40, max:250]. data_mode:0 *Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[123],ClearC han[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0] *Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_modem_redundancy 1, payload 100, modem_relay 0, gw-xid 0 *Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20, FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051 SignalType 2 DtmfRelay 1, Modem 2, SeqNumStart 0x0 *Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_ind_negotiation: Caps after caps negotiation: *Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: playout: [ mode:1,init:60, min:40, max:250]. data_mode:0 *Jun 8 20:10:33.497: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[123],ClearC han[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0] *Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_modem_redundancy 1, payload 100, modem_relay 0, gw-xid 0 *Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20, FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051 SignalType 2 DtmfRelay 1, Modem 2, SeqNumStart 0x0 *Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_cap_ind_ack: packet streams already created during bridging *Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_ind_negotiation: Caps in caps indication: *Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: playout: [ mode:1,init:60, min:40, max:250]. data_mode:0 *Jun 8 20:10:33.501: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[123],ClearC han[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0] *Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_modem_redundancy 1, payload 100, modem_relay 0, gw-xid 0 *Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20, FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051 SignalType 2 DtmfRelay 1, Modem 2, SeqNumStart 0x0 *Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_ind_negotiation: Caps after caps negotiation:


DB-2373


*Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: playout: [ mode:1,init:60, min:40, max:250]. data_mode:0 *Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: RTP PT:NTE[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[123],ClearC han[125],PCMu[0],PCMa[8]Codec[4], TxDynamicPayload[0], RxDynamicPayload[0] *Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_caps_dump: passthrough: cap_modem_proto 4,cap_modem_codec 1, cap_modem_redundancy 1, payload 100, modem_relay 0, gw-xid 0 *Jun 8 20:10:33.505: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_debug_caps_encap: Encap 1, Vad 2, Codec 0x4, CodecBytes 20, FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051 SignalType 2 DtmfRelay 1, Modem 2, SeqNumStart 0x0 *Jun 8 20:10:33.509: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_connect_cb: . *Jun 8 20:10:36.229: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_req_stats: . *Jun 8 20:10:36.233: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: . *Jun 8 20:10:38.265: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_req_stats: . *Jun 8 20:10:38.269: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: . *Jun 8 20:10:43.481: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_req_stats: . *Jun 8 20:10:43.489: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: .

The following is sample output from the debug voip dsm command, with Cisco IOS Release 12.3(14)T software, when a VoIP call is in transition from connected to the disconnected state: Router# debug voip dsm *Jun 8 20:12:14.701: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_req_stats: . *Jun 8 20:12:14.705: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: . *Jun 8 20:12:18.721: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_bridge_drop: *Jun 8 20:12:18.721: dsp_stream_mgr_bridge_drop, src_call_id 28, dst_call_id 27 *Jun 8 20:12:18.721: //28/6F1FA7868003/DSM:(2/0:23):-1/dsm_delete_conn_array_entry: dmgr->connArr.count = 0 *Jun 8 20:12:18.737: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_stats_cb: . *Jun 8 20:12:18.765: //28/6F1FA7868003/DSM:(2/0:23):-1/dsp_stream_mgr_destroy: . *Jun 8 20:12:18.765: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmapi_accept_modem_passthrough_session: : dmgr: 6561C520, active sessions 0, max sessions: 16 rejected sessions till now: 0 *Jun 8 20:12:18.769: //28/6F1FA7868003/DSM:(2/0:23):-1/dsmp_dsmapi_reserve_resource_cb: .

Related Commands

Command

Description

debug voip dsmp

Displays debugging information from the DSMP and its related applications.

debug voip vtsp

Displays information about the VTSP.


DB-2374

May 2008

Debug Commands debug voip dsmp

debug voip dsmp To display debugging information from the Distributed Stream Media Processor (DSMP) and its related applications, use the debug voip dsmp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip dsmp [all | default | error | event | function | individual | inout | rtp | session | stats | tone | vofr] no debug voip dsmp

Syntax Description

all

(Optional) Enables all DSMP debugging (except stats).

default

(Optional) Activates inout, error, and event debugging.

error

(Optional) Enables DSMP error debugging.

event

(Optional) Enables state machine debugging.

function


individual

(Optional) Enables individual DSMP debugging.

inout


rtp

(Optional) Enables Real-Time Protocol (RTP) debugging on DSMP.

session

(Optional) Enables session debugging.

stats

(Optional) Enables DSMP statistics debugging.

tone

(Optional) Enables tone debugging.

vofr

(Optional) Enables Voice over Frame Relay (VoFR) debugging on the VPM.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.3(14)T

The all, default, error, event, function, individual, inout, rtp, session, stats, tone, and vofr keywords were added to the command.

12.2SX


Usage Guidelines

To debug VoIP calls, use this command in conjunction with debug voip vtsp command and debug voip dsm commands. All the related information for media processing is now available by using DSMP. DSM is responsible for creating streams and issuing connections between them.

Examples

The following is sample output from the debug voip dsmp command for transcoding call: Router# debug voip dsmp


DB-2375


Syslog logging:enabled (11 messages dropped, 2 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) Console logging:disabled Monitor logging:level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging:level debugging, 236 messages logged, xml disabled, filtering disabled Logging Exception size (4096 bytes) Count and timestamp logging messages:disabled Trap logging:level informational, 25 message lines logged Log Buffer (3000000 bytes): 00:10:18:dsmpAddStream:: 00:10:18:dsmpAddStream:: 00:10:18:dsmpAddStream:: 00:10:18:dsmpAddStream:: 00:10:18:dsmpConnectXcodeBinderReq 00:10:18:dsmp_process_event: 00:10:18:dsmp_process_event:evt->requestType = E_DSMP_CC_XCODE_REQ 00:10:18:dsmpxc_act_alloc_rsc::state = S_DSMPXC_INITIAL event = E_DSMP_CC_XCODE_REQ 00:10:18:dsp_ret = 4 (if failed, cause = 0) 00:10:18:dsp_intf = 0x63DD21D8 00:10:18:dsmp_set_state_var:message to DSP successful,ret::4 00:10:18:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_INITIAL, event:E_DSMP_CC_XCODE_REQ, next_state:S_DSMPXC_RSC_ALLOCING 00:10:18:dsmp_is_ret_succ:: 00:10:18:dsmpxc_act_init_rsc::state = S_DSMPXC_RSC_ALLOCING event = CNFSM_LAMBDA_EVENT 00:10:18:dsmp_set_state_var:message to DSP successful,ret::4 00:10:18:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_RSC_ALLOCING, event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_RSC_INITING 00:10:18:dsmp_is_ret_succ:: 00:10:18:dsmpxc_act_open_rsc::state = S_DSMPXC_RSC_INITING event = CNFSM_LAMBDA_EVENT 00:10:18:dsmp_set_state_var:message to DSP successful,ret::4 00:10:18:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_RSC_INITING, event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_RSC_OPENING 00:10:18:dsmp_is_ret_succ:: 00:10:18:dsmpxc_act_program_rsc::state = S_DSMPXC_RSC_OPENING event = CNFSM_LAMBDA_EVENT 00:10:18:dsmp_set_state_var:message to DSP successful,ret::4 00:10:18:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_RSC_OPENING, event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_XCODE_PEND 00:10:18:CNFSM:new_container:xcoding_container 00:10:18:dsmp_is_ret_succ:: 00:10:18:dsmpxc_act_succ_conn_req::state = S_DSMPXC_XCODE_PEND event = CNFSM_LAMBDA_EVENT 00:10:18:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE_PEND, event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_XCODE 00:10:18:no_stream_in_session Router# clear log Clear logging buffer [confirm] Router# Router# clear logsh logg Syslog logging:enabled (11 messages dropped, 2 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) Console logging:disabled Monitor logging:level debugging, 0 messages logged, xml disabled, filtering disabled


DB-2376

May 2008


Buffer logging:level debugging, 274 messages logged, xml disabled, filtering disabled Logging Exception size (4096 bytes) Count and timestamp logging messages:disabled Trap logging:level informational, 25 message lines logged Log Buffer (3000000 bytes): 00:10:50:dsmpDeleteStream 00:10:50:dsmpDeleteStream 00:10:50:dsmpDeleteStream 00:10:50:dsmpDeleteStream 00:10:50:dsmp_process_event: 00:10:50:dsmp_process_event:evt->requestType = E_DSMP_CC_DELETE_STREAM 00:10:50:dsmpxc_act_delete_stream::state = S_DSMPXC_XCODE event = E_DSMP_CC_DELETE_STREAM 00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE, event:E_DSMP_CC_DELETE_STREAM, next_state:CNFSM_NO_STATE_CHANGE 00:10:50:no_stream_in_session 00:10:50:dsmp_process_event:evt->requestType = E_DSMP_CC_DELETE_STREAM 00:10:50:dsmpxc_act_delete_stream::state = S_DSMPXC_XCODE event = E_DSMP_CC_DELETE_STREAM 00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE, event:E_DSMP_CC_DELETE_STREAM, next_state:CNFSM_NO_STATE_CHANGE 00:10:50:no_stream_in_session 00:10:50:dsmp_process_event:evt->requestType = E_DSMP_CC_DELETE_STREAM 00:10:50:dsmpxc_act_delete_stream::state = S_DSMPXC_XCODE event = E_DSMP_CC_DELETE_STREAM 00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE, event:E_DSMP_CC_DELETE_STREAM, next_state:CNFSM_NO_STATE_CHANGE 00:10:50:no_stream_in_session 00:10:50:dsmp_process_event:evt->requestType = E_DSMP_CC_DELETE_STREAM 00:10:50: dsmpxc_act_delete_stream::state = S_DSMPXC_XCODE event = E_DSMP_CC_DELETE_STREAM 00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE, event:E_DSMP_CC_DELETE_STREAM, next_state:CNFSM_NO_STATE_CHANGE 00:10:50:no_stream_in_session 00:10:50:dsmpxc_act_stop_rsc::state = S_DSMPXC_XCODE event = CNFSM_LAMBDA_EVENT 00:10:50:dsmp_set_state_var:message to DSP successful,ret::4 00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_XCODE, event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_CLOSING 00:10:50:dsmp_is_ret_succ:: 00:10:50:dsmpxc_act_dealloc_rsc::state = S_DSMPXC_CLOSING event = CNFSM_LAMBDA_EVENT 00:10:50:dsmp_set_state_var:message to DSP successful,ret::4 00:10:50:CNFSM:cur_container:xcoding_container, cur_state:S_DSMPXC_CLOSING, event:CNFSM_LAMBDA_EVENT, next_state:S_DSMPXC_STILL_CLOSING 00:10:50:CNFSM:new_container:xcoder_container 00:10:50:dsmp_is_ret_succ:: 00:10:50:dsmpxc_act_start_timer::state = S_DSMPXC_STILL_CLOSING event = CNFSM_LAMBDA_EVENT 00:10:50:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_STILL_CLOSING, event:CNFSM_LAMBDA_EVENT, next_state:CNFSM_NO_STATE_CHANGE 00:10:50:dsmp_process_event:evt->requestType = E_DSMP_DSPRM_CLOSE_COMPLETE 00:10:50:dsmpxc_act_terminate::state = S_DSMPXC_STILL_CLOSING event = E_DSMP_DSPRM_CLOSE_COMPLETE 00:10:50:dsmpxc_act_terminate Removing the program based stream = 1 00:10:50:CNFSM:cur_container:xcoder_container, cur_state:S_DSMPXC_STILL_CLOSING, event:E_DSMP_DSPRM_CLOSE_COMPLETE, next_state:CNFSM_NULL_STATE 00:10:50:dsmp_free_session 00:10:50:dsmp_process_event:


DB-2377


The following is sample output from the debug voip dsmp command, with Cisco IOS Release 12.3(14)T software, when a VoIP call is in transition to the connected state: Router# debug voip dsmp *May 22 04:12:17.775: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: callID = 24, confID = -1, streamType = TDM, streamDir = INPUT, ownerContext = 0x0000000C, codec = 0x0, fax_modem_type =0, XmitFn = 0x00000000, multicastStreamDtmfType = 0 *May 22 04:12:17.775: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: streamID = 2 *May 22 04:12:17.779: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: callID = 24, confID = -1, streamType = TDM, streamDir = OUTPUT, ownerContext = 0x0000000C, codec = 0x0, fax_modem_type =0, XmitFn = 0x00000000, multicastStreamDtmfType = 0 *May 22 04:12:17.779: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: streamID = 3 *May 22 04:12:17.779: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpReserveGwResource: sIdLegInput1 = 2, sIdLegOutput1 = 3, requesterCallID = 24, respFunc = 0x61CD1EE0 *May 22 04:12:17.787: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_new_or_existing_gw_session: created a new session = 0x657EEE20 *May 22 04:12:17.787: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_enlist_stream: Stream 2 is enlisted, total = 1 *May 22 04:12:17.787: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_enlist_stream: Stream 3 is enlisted, total = 2 *May 22 04:12:17.787: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_exec: [state:S_DSMP_INITIAL, event:E_DSMP_CC_RESERVE_RESOURCE_REQ] *May 22 04:12:17.791: CNFSM: cur_container:rsc_main_container, cur_state:S_DSMP_INITIAL, event:E_DSMP_CC_RESERVE_RESOURCE_REQ *May 22 04:12:17.791: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_gw_act_alloc_rsc: *May 22 04:12:17.791: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_decide_pgm_based_stm: *May 22 04:12:17.791: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:17.791: CNFSM: new_container:rsc_allocating_container *May 22 04:12:17.791: CNFSM: next_state:S_DSMP_RSC_ALLOCATING *May 22 04:12:17.791: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_alloc_succ: *May 22 04:12:17.791: CNFSM: next_state:S_DSMP_RSC_ALLOCATED *May 22 04:12:18.047: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpReserveGwResource: sIdLegInput1 = 2, sIdLegOutput1 = 3, requesterCallID = 24, respFunc = 0x61CD1EE0 *May 22 04:12:18.047: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_RESERVE_RESOURCE_REQ] *May 22 04:12:18.051: CNFSM: cur_container:rsc_allocating_container, cur_state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_RESERVE_RESOURCE_REQ *May 22 04:12:18.051: CNFSM: new_container:rsc_main_container *May 22 04:12:18.051: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_reopen: *May 22 04:12:18.051: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:18.051: CNFSM: history stored state: S_DSMP_RSC_ALLOCATED, container: rsc_allocating_container *May 22 04:12:18.051: CNFSM: updated current container: rsc_main_container *May 22 04:12:18.051: CNFSM: next_state:S_DSMP_RSC_REOPENING *May 22 04:12:18.051: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_alloc_succ: *May 22 04:12:18.051: CNFSM: restoring history state: S_DSMP_RSC_ALLOCATED *May 22 04:12:18.055: CNFSM: restoring history container: rsc_allocating_container *May 22 04:12:18.055: CNFSM: new_container:rsc_allocating_container *May 22 04:12:18.055: CNFSM: next_state:S_DSMP_RSC_ALLOCATED *May 22 04:12:18.055: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpStopPlay: sIdLegOutput = 3 *May 22 04:12:18.059: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_STOP_PLAY_REQ] *May 22 04:12:18.059: CNFSM: cur_container:rsc_allocating_container, cur_state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_STOP_PLAY_REQ *May 22 04:12:18.059: CNFSM: new_container:rsc_main_container *May 22 04:12:18.059: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_ignore: *May 22 04:12:18.059: CNFSM: next_state:CNFSM_NO_STATE_CHANGE *May 22 04:12:18.063: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: callID = 23, confID = 12, streamType = PACKET, streamDir = INPUT, ownerContext = 0x0000000C, codec = 0x1, fax_modem_type =0, XmitFn = 0x6158E1F8, multicastStreamDtmfType = -1 *May 22 04:12:18.067: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: streamID = 1


DB-2378

May 2008


*May 22 04:12:18.067: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: callID = 23, confID = 12, streamType = PACKET, streamDir = OUTPUT, ownerContext = 0x0000000C, codec = 0x1, fax_modem_type =0, XmitFn = 0x6158E1F8, multicastStreamDtmfType = -1 *May 22 04:12:18.067: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpAddStream: streamID = 4 *May 22 04:12:18.071: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpUpdateRtpMode: sId = 1, callID = 24, mode = 1 *May 22 04:12:18.071: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpModifyReq: sIdLegInput = 1, sIdLegOutput = 4, callID = 24 *May 22 04:12:18.075: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpConnectGwBinderReq: sIdLegInputTdm1=2, sIdLegOutputPak1=4, sIdLegInputPak2=1, sIdLegOutputTdm2=3, Call Id=24 *May 22 04:12:18.075: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpModifyReq: sIdLegInput = 2, sIdLegOutput = 3, callID = 24FORKING Parameters are forking mask: 7, simple_forking_codec_mask: 327679, complex_forking_codec_mask 327679 *May 22 04:12:18.075: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_process_event: No session is associated to the streams. *May 22 04:12:18.075: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_caps: *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_packet_stream_caps: *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: CALL_ERROR; DSMP Session Is NULL *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:exit@2908 *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: CALL_ERROR; DSMP Session Is NULL *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:exit@2908 *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: CALL_ERROR; DSMP Session Is NULL *May 22 04:12:18.079: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:exit@2908 *May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: *May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: CALL_ERROR; DSMP Session Is NULL *May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write:exit@2908 *May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_packet_stream_caps: *May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps: *May 22 04:12:18.083: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps:exit@385 *May 22 04:12:18.087: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps: *May 22 04:12:18.087: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps:exit@385 *May 22 04:12:18.087: //-1/F401BFC88006/DSMP:():-1/dsmp_enlist_stream: Stream 1 is enlisted, total = 3 *May 22 04:12:18.087: //-1/F401BFC88006/DSMP:():-1/dsmp_enlist_stream: Stream 4 is enlisted, total = 4 *May 22 04:12:18.087: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_CONNECT_REQ] *May 22 04:12:18.091: CNFSM: cur_container:rsc_allocating_container, cur_state:S_DSMP_RSC_ALLOCATED, event:E_DSMP_CC_CONNECT_REQ *May 22 04:12:18.091: //-1/F401BFC88006/DSMP:():-1/dsmp_is_req_not_in_proc_dsp_ready: *May 22 04:12:18.091: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_init: *May 22 04:12:18.091: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:18.091: CNFSM: history stored state: S_DSMP_RSC_ALLOCATED, container: rsc_allocating_container *May 22 04:12:18.091: CNFSM: new_container:rsc_main_container *May 22 04:12:18.095: CNFSM: next_state:S_DSMP_RSC_INITING *May 22 04:12:18.095: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_decide_pgm_based_stm: *May 22 04:12:18.095: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_init_succ: pgm_base_stm_id = 1, service_id = 26, codec =4 *May 22 04:12:18.095: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:18.099: CNFSM: next_state:S_DSMP_RSC_OPENING *May 22 04:12:18.099: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_open_succ:


DB-2379


*May 22 04:12:18.099: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: *May 22 04:12:18.099: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_static_params: *May 22 04:12:18.099: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_static_params: servic_type=1 base stream=1 tdm_caps=0x6557E454 pkt_caps=0x6557EC3C *May 22 04:12:18.099: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_static_params: *May 22 04:12:18.103: ip_tones = 0, pstn_tones = 0 *May 22 04:12:18.103: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_conf_static_params: voice detection disabled *May 22 04:12:18.103: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_conf_static_params: silence detection disabled *May 22 04:12:18.103: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:18.107: CNFSM: next_state:S_DSMP_RSC_STATIC_CONF *May 22 04:12:18.107: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_start_service: *May 22 04:12:18.107: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:18.107: CNFSM: next_state:S_DSMP_RSC_STARTING *May 22 04:12:18.107: //-1/F401BFC88006/DSMP:():-1/dsmp_act_rsc_start_succ: *May 22 04:12:18.107: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_dynamic_params: *May 22 04:12:18.111: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_dynamic_params: servic_type=1 base stream=1 *May 22 04:12:18.111: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: *May 22 04:12:18.111: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: *May 22 04:12:18.111: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_leg_voice_elog_write: *May 22 04:12:18.111: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_detector_params: *May 22 04:12:18.115: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:18.115: CNFSM: next_state:S_DSMP_RSC_DYNAMIC_CONF *May 22 04:12:18.115: CNFSM: new_container:rsc_running_container *May 22 04:12:18.115: CNFSM: next_state:S_DSMP_MCAST_CHECK *May 22 04:12:18.115: //-1/F401BFC88006/DSMP:():-1/dsmp_is_mcast: *May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_mcast:exit@1487 *May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_not_mcast: *May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_mcast: *May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_mcast:exit@1487 *May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_not_mcast:exit@1500 *May 22 04:12:18.119: CNFSM: next_state:S_DSMP_DTMF_FSK_MODE_CHECK *May 22 04:12:18.119: //-1/F401BFC88006/DSMP:():-1/dsmp_is_fsk_or_dtmf: *May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_diagnostic: *May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_diagnostic:exit@1587 *May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_not_dtmf_fsk: *May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_fsk_or_dtmf: *May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_diagnostic: *May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_diagnostic:exit@1587 *May 22 04:12:18.123: //-1/F401BFC88006/DSMP:():-1/dsmp_is_not_dtmf_fsk:exit@1600 *May 22 04:12:18.127: CNFSM: next_state:S_DSMP_NOT_DTMF_FSK *May 22 04:12:18.127: //-1/F401BFC88006/DSMP:():-1/dsmp_is_simple_voice: *May 22 04:12:18.127: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_get_stm_service_type: *May 22 04:12:18.127: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_simple_voice_start: *May 22 04:12:18.127: //-1/F401BFC88006/DSMP:():-1/dsmp_connect_req_done: *May 22 04:12:18.127: //-1/F401BFC88006/DSMP:():-1/dsmp_enlist_connection: Connection is added, enlisted LegIn: 2, enlisted LegOut: 4 *May 22 04:12:18.131: //-1/F401BFC88006/DSMP:():-1/dsmp_enlist_connection: Connection is added, enlisted LegIn: 1, enlisted LegOut: 3 *May 22 04:12:18.131: CNFSM: new_container:simple_voice_container *May 22 04:12:18.131: CNFSM: next_state:S_DSMP_VC_RUNNING *May 22 04:12:18.131: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_MODIFY_REQ] *May 22 04:12:18.135: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_MODIFY_REQ *May 22 04:12:18.135: CNFSM: new_container:rsc_running_container *May 22 04:12:18.135: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_save_modify_caps: *May 22 04:12:18.135: //-1/F401BFC88006/DSMP:():-1/dsmp_save_modify_caps: *May 22 04:12:18.135: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_packet_stream_caps:


DB-2380

May 2008


*May 22 04:12:18.139: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_packet_stream_caps: *May 22 04:12:18.139: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps: *May 22 04:12:18.139: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_save_modify_tdm_stream_caps: *May 22 04:12:18.139: //-1/F401BFC88006/DSMP:():-1/dsmp_save_stream_detectors: *May 22 04:12:18.139: CNFSM: history stored state: S_DSMP_VC_RUNNING, container: simple_voice_container *May 22 04:12:18.139: CNFSM: updated current container: rsc_running_container *May 22 04:12:18.143: CNFSM: next_state:S_DSMP_MODIFY_CAPS_SAVED *May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_modify_to_modem_passthru: *May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_static_params_changed: *May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_modify_to_modem_passthru: *May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_dynamic_params_changed: *May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_is_modify_to_modem_passthru: *May 22 04:12:18.143: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_dynamic_params_changed: *May 22 04:12:18.147: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_dynamic_params: *May 22 04:12:18.147: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_dynamic_params: servic_type=1 base stream=1 *May 22 04:12:18.147: //-1/F401BFC88006/DSMP:():-1/dsmp_conf_detector_params: *May 22 04:12:18.147: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_conf_detector_params: fax: 1 *May 22 04:12:18.147: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmp_conf_detector_params: modem: 1 *May 22 04:12:18.151: CNFSM: restoring history state: S_DSMP_VC_RUNNING *May 22 04:12:18.151: CNFSM: restoring history container: simple_voice_container *May 22 04:12:18.151: CNFSM: new_container:simple_voice_container *May 22 04:12:18.151: CNFSM: next_state:S_DSMP_VC_RUNNING *May 22 04:12:18.163: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpUpdateRtpMode: sId = 1, callID = 24, mode = 3 *May 22 04:12:18.163: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpUpdateRtpMode: sId = 1, callID = 24, mode = 3 *May 22 04:12:30.947: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpUpdateRtpMode: sId = 1, callID = 24, mode = 3

The following is sample output from the debug voip dsmp command, with Cisco IOS Release 12.3(14)T software, when a VoIP call is in transition from connected to the disconnected state: Router# debug voip dsmp *May 22 04:12:30.951: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDisconnectGwBinder: sIdLegInputTdm1 = 2, sIdLegOutputPak1 = 4, sIdLegInputPak2 = 1, sIdLegOutputTdm2 = 3 requesterCallID = 24 *May 22 04:12:30.951: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDeleteStream: streamID = 1, callID = 23, ownerContext = 0x00000000 *May 22 04:12:30.951: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDeleteStream: streamID = 4, callID = 23, ownerContext = 0x00000000 *May 22 04:12:30.951: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_DISCONNECT] *May 22 04:12:30.955: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_DISCONNECT *May 22 04:12:30.955: CNFSM: new_container:rsc_running_container *May 22 04:12:30.955: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_cc_disconnect: *May 22 04:12:30.955: //-1/F401BFC88006/DSMP:():-1/dsmp_delist_connection: Connection is delisted, delisted LegIn: 2, delisted LegOut: 4, total conn_count is = 1 *May 22 04:12:30.955: //-1/F401BFC88006/DSMP:():-1/dsmp_delist_connection: Connection is delisted, delisted LegIn: 1, delisted LegOut: 3, total conn_count is = 0 *May 22 04:12:30.955: CNFSM: next_state:CNFSM_NO_STATE_CHANGE *May 22 04:12:30.955: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM] *May 22 04:12:30.959: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM *May 22 04:12:30.959: CNFSM: new_container:rsc_running_container *May 22 04:12:30.959: CNFSM: new_container:rsc_main_container *May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/dsmp_not_last_stream: *May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream: *May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_not_last_stream: *May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB: *May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams:


DB-2381


*May 22 04:12:30.959: CNFSM: next_state:CNFSM_NO_STATE_CHANGE *May 22 04:12:30.959: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM] *May 22 04:12:30.959: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM *May 22 04:12:30.963: CNFSM: new_container:rsc_running_container *May 22 04:12:30.963: CNFSM: new_container:rsc_main_container *May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/dsmp_not_last_stream: *May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream: *May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_not_last_stream: *May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB: *May 22 04:12:30.963: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams: *May 22 04:12:30.963: CNFSM: next_state:CNFSM_NO_STATE_CHANGE *May 22 04:12:30.967: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpStopPlay: sIdLegOutput = 3 *May 22 04:12:30.975: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_STOP_PLAY_REQ] *May 22 04:12:30.975: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_STOP_PLAY_REQ *May 22 04:12:30.975: CNFSM: new_container:rsc_running_container *May 22 04:12:30.975: CNFSM: new_container:rsc_main_container *May 22 04:12:30.975: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_ignore: *May 22 04:12:30.975: CNFSM: next_state:CNFSM_NO_STATE_CHANGE *May 22 04:12:31.011: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpStopPlay: sIdLegOutput = 3 *May 22 04:12:31.011: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDeleteStream: streamID = 2, callID = 24, ownerContext = 0x0000000C *May 22 04:12:31.011: //-1/xxxxxxxxxxxx/DSMP:():-1/dsmpDeleteStream: streamID = 3, callID = 24, ownerContext = 0x0000000C *May 22 04:12:31.015: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_STOP_PLAY_REQ] *May 22 04:12:31.015: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_CC_STOP_PLAY_REQ *May 22 04:12:31.015: CNFSM: new_container:rsc_running_container *May 22 04:12:31.015: CNFSM: new_container:rsc_main_container *May 22 04:12:31.015: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_ignore: *May 22 04:12:31.015: CNFSM: next_state:CNFSM_NO_STATE_CHANGE *May 22 04:12:31.015: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM] *May 22 04:12:31.015: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM *May 22 04:12:31.019: CNFSM: new_container:rsc_running_container *May 22 04:12:31.019: CNFSM: new_container:rsc_main_container *May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/dsmp_not_last_stream: *May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream: *May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_not_last_stream: *May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB: *May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams: *May 22 04:12:31.019: CNFSM: next_state:CNFSM_NO_STATE_CHANGE *May 22 04:12:31.019: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM] *May 22 04:12:31.019: CNFSM: cur_container:simple_voice_container, cur_state:S_DSMP_VC_RUNNING, event:E_DSMP_DELETE_STREAM *May 22 04:12:31.019: CNFSM: new_container:rsc_running_container *May 22 04:12:31.023: CNFSM: new_container:rsc_main_container *May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_not_last_stream: *May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream: *May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_is_last_stream: *May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_stop: *May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB: *May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams: *May 22 04:12:31.023: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:31.023: CNFSM: history stored state: S_DSMP_VC_RUNNING, container: simple_voice_container *May 22 04:12:31.023: CNFSM: updated current container: rsc_main_container


DB-2382

May 2008


*May 22 04:12:31.027: CNFSM: new_container:rsc_closing_container *May 22 04:12:31.027: CNFSM: next_state:S_DSMP_RSC_STOPPING *May 22 04:12:31.027: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_rsc_stopping_close: *May 22 04:12:31.027: //-1/F401BFC88006/DSMP:():-1/dsmp_set_state_var: Message to DSP is successful *May 22 04:12:31.027: CNFSM: next_state:S_DSMP_DSPMGR_CLOSING *May 22 04:12:31.027: //-1/F401BFC88006/DSMP:():-1/dsmp_exec: [state:S_DSMP_DSPMGR_CLOSING, event:E_DSMP_DSPRM_CLOSE_COMPLETE] *May 22 04:12:31.027: CNFSM: cur_container:rsc_closing_container, cur_state:S_DSMP_DSPMGR_CLOSING, event:E_DSMP_DSPRM_CLOSE_COMPLETE *May 22 04:12:31.027: //-1/F401BFC88006/DSMP:():-1/dsmp_gw_act_dspmgr_closing_complete: *May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB: *May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams: *May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/remove_stream_from_DB: *May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/process_software_multicast_streams: *May 22 04:12:31.031: CNFSM: next_state:CNFSM_NULL_STATE *May 22 04:12:31.031: //-1/F401BFC88006/DSMP:():-1/dsmp_free_session:

Related Commands

Command

Description

debug voip dsm

Displays debugging information from the DSM subsystem.

debug voip vtsp

Displays information about the VTSP.


DB-2383

Debug Commands debug voip dspapi

debug voip dspapi To troubleshoot the digital signal processor (DSP) application programming interface (API), use the debug voip dspapi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip dspapi [all | command | default | detail | error [call [informational] | software [informational]] | function | inout | notification | response] no debug voip dspapi

Syntax Description

all

(Optional) Displays all DSP API debugging messages.

command

(Optional) Displays DSP API commands.

default

(Optional) Displays DSP API detail, error, and inout debugging messages. This option also runs if no keywords are added.

detail

(Optional) Displays detailed information about commands sent to the DSP. This command is used in conjunction with other debug voip dspapi commands to show additional details when you use the command, notification, and response keywords.

error

(Optional) Displays DSP API errors.

call


informational


software


function

(Optional) Displays DSP API functions.

inout

(Optional) Displays output for the command, notification, and response keywords.

notification

(Optional) Displays DSP API notification messages.

response

(Optional) Displays DSP API response messages.

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug dspapi command.

12.3(14)T


12.2SX



DB-2384

May 2008


Usage Guidelines

Caution

Examples

DSP API message events used to communicate with DSPs are intended for use with Connexant (NextPort) and Texas Instruments (54x) DSPs.

This command severely impacts performance and should be used only for single-call debug capture.

The following examples show output for variations of the debug voip dspapi command: •

debug voip dspapi Command on the Originating Gateway, page 2385

•

debug voip dspapi inout on the Terminating Gateway, page 2386

•

debug voip dspapi Command Displaying T.38 fax Relay Statistics on the Terminating Gateway, page 2388

For these examples, the topology shown in Figure 4 is used. Network Topology for debug voip dspapi Examples

T1 PRI

PSTN

FXS

V

VoIP network

Cisco 3745 originating gateway

V

103302

Figure 4


debug voip dspapi Command on the Originating Gateway Router# debug voip dspapi command voip dspapi command debugging is ON Router# *Apr 18 21:33:48.347: //-1/CD89F6A78020/DSPAPI/[2/1:23]/dsp_init: *Apr 18 21:33:48.347: //-1/CD89F6A78020/DSPAPI/[2/1:23]/dsp_voice_config_params: *Apr 18 21:33:48.347: 9 parameters

The following lines show encapsulation settings, jitter, inband signaling, echo cancellation, gain, and other quality of service (QoS) settings: [0] ENCAP RTP: Tx SSRC=0, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0 IFP payload type=122, SID support=1, TSE payload=101, Sequence number start=0 Redundancy=0, ClearChannel payload type=0, Fax payload type=0 Alaw PCM switchover=0, MuLAW PCM switchover=0 DTMF payload type=0, NTE receive payload type=101 Dynamic payload=0, Codec=g711ulaw [1] PO_JITTER: mode=2 initial=60(ms) max=200(ms) min=40(ms) fax_nom=300(ms) [2] INBAND_SIG: mode=0x1 enable [3] ECHO_CANCEL: Flags=0x37, Echo length=64(ms) [4] IDLE_CODE_DET: Enable=0, Code=0x0, Duration=6000(ms) [5] GAIN: Input=0.0(dB), Output=0.0(dB) [6] CNG: 1 [7] INFO_FIELD_SIZE: 160 bytes [8] DIGIT_RELAY: 2 *Apr 18 21:33:48.359: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_voice_get_capabilities: *Apr 18 21:33:48.359: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_stop_service: NONE (0) *Apr 18 21:33:48.359: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_open_service:


DB-2385


G729IETF (25) *Apr 18 21:33:48.359: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_voice_config_params:

The following lines show settings for encapsulation, packet suppression, and voice activity detection (VAD): *Apr 18 21:33:48.359: 3 parameters [0] ENCAP RTP: Tx SSRC=64, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0 IFP payload type=122, SID support=19, TSE payload=101, Sequence number start=3238 Redundancy=0, ClearChannel payload type=125, Fax payload type=122 Alaw PCM switchover=8, MuLAW PCM switchover=0 DTMF payload type=121, NTE receive payload type=101 Dynamic payload=0, Codec=g729r8 [1] PAK_SUPPRESS: 0 [2] VAD: Enable=1, Threshold=-38(dBm) . . . *Apr 18 21:33:48.363: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_start_service: G729IETF (25) *Apr 18 21:33:48.363: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_voice_config_params: *Apr 18 21:33:48.363: 1 parameter [0] VAD: Enable=1, Threshold=-38(dBm) *Apr 18 21:33:50.867: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_query_info: Request ID=1, Reset Flag=FALSE Q:PO_Delay PO_Error TX RX . . . *Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_query_info: Request ID=5, Reset Flag=TRUE Q:Error *Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_query_info: Request ID=5, Reset Flag=TRUE Q:Levels *Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_inband_tone_off: *Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_stop_service: G729IETF (25) *Apr 18 21:34:15.031: //66/CD89F6A78020/DSPAPI/[2/1:23:66]/dsp_close_service: G729IETF (25)

debug voip dspapi inout on the Terminating Gateway Router# debug voip dspapi inout voip dspapi inout debugging is ON *May *May *May

1 19:59:15.579: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_init: 1 19:59:15.579: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_config_params: 1 19:59:15.579: 9 parameters

The following lines show encapsulation settings, jitter, inband signalling, echo cancellation, gain, and other quality of service (QoS) settings: [0] ENCAP RTP: Tx SSRC=0, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0 IFP payload type=122, SID support=1, TSE payload=101, Sequence number start=0 Redundancy=0, ClearChannel payload type=0, Fax payload type=0 Alaw PCM switchover=0, MuLAW PCM switchover=0 DTMF payload type=0, NTE receive payload type=101 Dynamic payload=0, Codec=g711ulaw [1] PO_JITTER: mode=2 initial=60(ms) max=200(ms) min=40(ms) fax_nom=300(ms) [2] INBAND_SIG: mode=0x1 enable [3] ECHO_CANCEL: Flags=0x17, Echo length=8(ms) [4] IDLE_CODE_DET: Enable=0, Code=0x0, Duration=6000(ms) [5] GAIN: Input=0.0(dB), Output=-6550.6(dB) [6] CNG: 1


DB-2386

May 2008


[7] INFO_FIELD_SIZE: 160 bytes [8] DIGIT_RELAY: 2 . . *May *May

1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_get_capabilities: 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_stop_service: NONE (0) *May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_open_service: G729IETF (25) *May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_config_params: *May 1 19:59:15.587: 3 parameters [0] ENCAP RTP: Tx SSRC=0, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0 IFP payload type=122, SID support=19, TSE payload=101, Sequence number start=2977 Redundancy=0, ClearChannel payload type=125, Fax payload type=122 Alaw PCM switchover=8, MuLAW PCM switchover=0 DTMF payload type=121, NTE receive payload type=101 Dynamic payload=0, Codec=g729r8 [1] PAK_SUPPRESS: 0 [2] VAD: Enable=1, Threshold=-38(dBm) *May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_idle_service: G729IETF (25) *May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_config_params: *May 1 19:59:15.587: 3 parameters [0] INFO_FIELD_SIZE: 20 bytes [1] ENCAP RTP: Tx SSRC=64, Rx SSRC=0, Tx VPXCC=0, Rx VPXCC=0 IFP payload type=122, SID support=19, TSE payload=101, Sequence number start=2977 Redundancy=0, ClearChannel payload type=125, Fax payload type=122 Alaw PCM switchover=8, MuLAW PCM switchover=0 DTMF payload type=121, NTE receive payload type=101 Dynamic payload=0, Codec=g729r8 [2] DIGIT_RELAY: 2 *May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_start_service: G729IETF (25) *May 1 19:59:15.587: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_voice_config_params: *May 1 19:59:15.587: 1 parameter [0] VAD: Enable=1, Threshold=-38(dBm) *May 1 19:59:15.591: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_inband_tone_on: Tone ID=1, Direction=2, Num frequencies=2 Frequency(hz): a=440 b=480, Amplitude(dB): a=-16.0 b=-16.0 Cadence1(ms): ON=2000 OFF=4000 Cadence2(ms): ON=0 OFF=0 Cadence3(ms): ON=0 OFF=0 Cadence4(ms): ON=0 OFF=0 Frequency(hz): a2=25667 b2=51816 a3=0 b3=1 a4=24596 b4=52484 ITO option group: 1 *May 1 19:59:17.195: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_inband_tone_off: 01:19:04: %PS-3-MULTFAIL: There is more than one failure with the Power System 1; please resolve problems immediately

The following statistics repeat for each DSP query. The transmit (tx) and receive (rx) statistics show number of packets, comfort noise settings, duration, and packet status. *May

1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_query_info: Request ID=1, Reset Flag=FALSE Q:PO_Delay PO_Error TX RX *May 1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_tx_stats: Request ID=1, Packets: Voice=113, Signaling=0, ComfortNoise=1 TX duration=2460(ms): Voice=2260(ms), FAX=0(ms) *May 1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_rx_stats: Request ID=1, Packets: Voice=33, Signalling=0, ComfortNoise=1 RX duration=840(ms): Voice=640(ms), FAX=0(ms) Packets: Bad Sequence=0, Bad Protocol=0, Late=0, Early=1 *May 1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_playout_delay_stats: Request ID=1, Current=70(ms), MIN=70(ms), MAX=70(ms) Clock offset=80(ms), Inter arrival jitter=67082420(ms)


DB-2387


*May

1 19:59:18.051: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_playout_error_stats: Request ID=1 Concealment: Predictive=0(ms), Interpolative=0(ms), Silence=0(ms) Retro Memory update=0(ms), Buffer overflow=10(ms) Talkspurt endpoint detection errors=0 *May 1 19:59:19.827: //67/2BA0E0758024/DSPAPI/[4/0/0 (67)]/dsp_query_info: Request ID=1, Reset Flag=FALSE Q:PO_Delay PO_Error TX RX . . .

debug voip dspapi Command Displaying T.38 fax Relay Statistics on the Terminating Gateway

This output shows the fax relay statistics. Router# debug voip dspapi voip dspapi debugging is ON . . . May 7 21:32:16.472 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_playout_error_stats: Request ID=1 Concealment: Predictive=0(ms), Interpolative=0(ms), Silence=0(ms) Retro Memory update=0(na)(ms), Buffer overflow=0(ms) Talkspurt endpoint detection errors=0 May 7 21:32:18.996 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_query_info: Request ID=1, Reset Flag=FALSE Q:PO_Delay PO_Error TX RX May 7 21:32:18.996 UTC: np_vsmgr_dispatch_voice_rsp(1/3): VOICE_LINK_INFO_RSP_NTF Received May 7 21:32:18.996 UTC: request_id = 0x01, request_type = 0x0F May 7 21:32:18.996 UTC: VOICE_TRANSMIT_STATS(1/3): num_voice_packets 36 num_sig_packets 0 num_cn_packets 1 transmit_duration AD2 end_point_detection 0 May 7 21:32:18.996 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_tx_stats: Request ID=1, Packets: Voice=54, Signaling=0, ComfortNoise=1 TX duration=2770(ms): Voice=0(ms), FAX=0(na)(ms) May 7 21:32:18.996 UTC: VOICE_RECEIVE_STATS(1/3): num_voice_packets 20 num_sig_packets 0 num_cn_packets 2 receive_duration AD2 voice_receive_duration 0 num_pos_packets 0 num_bph_packets 0 num_late_packets 0 num_early_packets 0 May 7 21:32:18.996 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_rx_stats: Request ID=1, Packets: Voice=32, Signalling=0, ComfortNoise=2 RX duration=2770(ms): Voice=0(ms), FAX=0(na)(ms) Packets: Bad Sequence=0, Bad Protocol=0, Late=0, Early=0 May 7 21:32:18.996 UTC: VOICE_PLAYOUT_DELAY_STATS(1/3): curr_playout_delay 5A min_playout_delay 5A max_playout_delay 5A clock offset 2F07E72 May 7 21:32:19.000 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_playout_delay_stats: Request ID=1, Current=90(ms), MIN=90(ms), MAX=90(ms) Clock offset=49315442(ms), Inter arrival jitter=0(na)(ms) May 7 21:32:19.000 UTC: VOICE_PLAYOUT_ERROR(1/3): pred_conceal 0x0 inter_conceal 0x0 silence_conceal 0x0 buffer_overflow 0x0 endpt_det_error 0x0 May 7 21:32:19.000 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_playout_error_stats: Request ID=1 Concealment: Predictive=0(ms), Interpolative=0(ms), Silence=0(ms) Retro Memory update=0(na)(ms), Buffer overflow=0(ms) Talkspurt endpoint detection errors=0 May 7 21:32:21.456 UTC: VOICE_DET_STATUS_CHANGE_NTF(1/3): detector mask: 1 timestamp 51709BF8 May 7 21:32:21.456 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_voice_det_status_change: Status=1, Timestamp=1366334456, Tone ID=0, Trigger=TRUE May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_voice_config_params: May 7 21:32:21.464 UTC: 1 parameter [0] PAK_SUPPRESS: 1 May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_stop_service: G729IETF (26)


DB-2388

May 2008


May

7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_config_params: 1 parameters May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_open_service: FAX_RELAY (27) May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending: Call is not PENDING May 7 21:32:21.464 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_set_call_pending: Set PENDING state May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_query_link_info: Request ID=0, Group ID=1 May 7 21:32:21.504 UTC: vsm(1/3): np_vsmgr_voice_state_change() - state IDLE May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending: Call is PENDING May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_reset_call_pending: Reset PENDING state May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_call_status: Status=PENDING_SUCCESS May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_config_params: 11 parameters May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_start_service: FAX_RELAY (27) May 7 21:32:21.504 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_set_call_pending: Set PENDING state May 7 21:32:22.556 UTC: vsm(1/3): np_vsmgr_voice_state_change() - state ACTIVE May 7 21:32:22.556 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending: Call is PENDING May 7 21:32:22.556 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_reset_call_pending: Reset PENDING state May 7 21:32:22.556 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_call_status: Status=PENDING_SUCCESS May 7 21:32:22.564 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 3 timestamp 76082770 fr-entered (20ms) May 7 21:32:22.564 UTC: chan_id [3/1:D (8)] np_vsmgr_fax_relay_link_info_response: May 7 21:32:29.712 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x4 May 7 21:32:30.436 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x2 May 7 21:32:30.784 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x1 May 7 21:32:33.936 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x42 May 7 21:32:34.280 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x41 May 7 21:32:39.676 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x21 May 7 21:32:39.676 UTC: np_fax_relay_t30_decode : Rx Direction May 7 21:32:39.736 UTC: FARELAY_INIT_HS_MOD : 0x8 May 7 21:33:10.385 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x7D May 7 21:33:13.073 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x31 May 7 21:33:15.217 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_t30_decode: T30 msg : 0x5F May 7 21:33:16.073 UTC: FAX_RELAY_DET_STATUS_CHANGE: slot: 1 port: 3 detector mask 0x2 May 7 21:33:16.073 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_det_status: Status=2, Timestamp=716372818 May 7 21:33:16.073 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_query_info: Request ID=5, Reset Flag=FALSE Q:FaxRelay May 7 21:33:16.097 UTC: FAX_RELAY_DATA_PUMP_STATS(1/3) - valid:0x3FFC1F55 state_code:0x1 level:0x18 phase_jitter:0x0 freq_offset:0x0 eqm:0x7FFE jit_depth:0x38B jit_buf_ov:0x0 tx_paks:0x5A rx_pkts:0x62C inv_pkts:0x0 oos_pkts:0x0 hs_mod:0x8 init_hs_mod:0x8 tx_pgs:0x0 rx_pgs:0x1 ecm:0x1 nsf_country:0x0 nsf_manuf_len:0x20 nsf_manuf:0031B8EE80C48511DD0D0000DDDD0000DDDD000000000000000022ED00B0A400 encap:0x1 pkt_loss_con:0x0


DB-2389


May

7 21:33:16.097 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_fax_relay_stats: Request ID=5, MAX jitter depth=907, MAX net RX qdepth=0(na) Jitter buffer overflow=0, Net RX qoverflow=0(na) Packets: TX=90 TX drops=0(na) Packets: RX=1580 RX loss=0(na), RX invalid=0, RX OOSequence=0 HS modulation=8, Pages: TX=0 RX=1 MAX TX In qdepth=0(na), MAX RX Out qdepth=0(na) MAX HS buffer usage=0(na), TX In qoverflow=0(na), RX Out qoverflow=0(na) FAX: State=1, level=24, Phase jitter=0, Frequency offset=0, EQM=32766 Initial HS modulation=8, Fax Direction=2, ECM Enabled=1 NSF Countery Code=0, nsf_manuf_code[32]=0031 Encapsulation Protocol=1, Pkt Loss Conceal=0 May 7 21:33:16.101 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_stop_service: FAX_RELAY (27) May 7 21:33:16.101 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_open_service: G729IETF (26) May 7 21:33:16.101 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending: Call is not PENDING May 7 21:33:16.101 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_set_call_pending: Set PENDING state May 7 21:33:16.985 UTC: FAX_RELAY_LINK_INFO_RSP_NTF: slot 1 port 3 timestamp 76518179 fr-end May 7 21:33:17.001 UTC: vsm(1/3): np_vsmgr_voice_state_change() - state IDLE May 7 21:33:17.001 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_is_call_pending: Call is PENDING May 7 21:33:17.001 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_reset_call_pending: Reset PENDING state May 7 21:33:17.001 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_call_status: Status=PENDING_SUCCESS May 7 21:33:17.001 UTC: //8/D6635DD58005/DSPAPI/[1/0:3]/dsp_voice_config_params: May 7 21:33:17.001 UTC: 4 parameters . . .

Related Commands

Command

Description

debug voip hpi

Enables debugging for HPI message events.


DB-2390

May 2008

Debug Commands debug voip eddri

debug voip eddri To turn on debugging for the event dispatcher and data repository interface (EDDRI), use the debug voip eddri command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip eddri {event | timers | prefix | all} no debug voip eddri {event | timers | prefix | all}

Syntax Description

event

Turns on debugging for EDDRI events.

timers

Turns on debugging for EDDRI timers.

prefix

Turns on debugging for the prefix database.

all

Turns on debugging all EDDRI activities.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(1)


12.2SX


Usage Guidelines

There is always a performance penalty when using debug commands. The EDDRI notifies TGREP when an attribute changes on some subsystems. EDDRI interacts with the dial peer subsystem, the trunk group subsystems, call control API (CCAPI) subsystem and the customer relationship management (CRM) subsystem to notify changes in particular attributes. EDDRI is responsible for creating the prefix database.

Examples

The following example shows sample output from the debug voip eddri command: 21:00:53: 21:00:53: 21:00:53: 21:00:53:

eddri_interesting_ac_pt: new AC_curr 22 FD_curr -5 SD_curr -5 eddri_interesting_ac_pt: percent trigger diff 4 eddri_interesting_ac_pt: Interesting Point eddri_send_prefix_event_to_clients : reason 0x40 num_prefix 1

With the send prefix event the available circuits value and the triggers for reporting are updated. 21:00:53: eddri_send_prefix_event_to_clients attr 0xFF ev_id 1 qid 0x64209230 reason 0x40 eddri_dequeue_event : dequeue event 21:00:53: eddri_interesting_ac_pt : tc 23 IAC 22 lwm 5 hwm 50 pct_trigger 2 oneMinusW 933


DB-2391

Debug Commands debug voip eddri

21:00:53: 21:00:53: 21:00:53: 21:00:53: 21:00:53:

Related Commands

eddri_interesting_ac_pt: old AC_curr 23 FD_curr 0 SD_curr 0 eddri_interesting_ac_pt: new AC_curr 22 FD_curr -5 SD_curr -5 eddri_interesting_ac_pt: percent trigger diff 4 eddri_interesting_ac_pt: Interesting Point eddri_send_prefix_event_to_clients : reason 0x40 num_prefix 1

Command

Description

debug tgrep error


debug tgrep events


debug tgrep fsm


debug tgrep io




debug tgrep msgdump




debug tgrep timers


debug tgrep tripr


show voice eddri prefix

Shows applicable prefixes for the EDDRI.


DB-2392

May 2008

Debug Commands debug voip enum

debug voip enum To view Voice over IP (VoIP) telephone number mapping (ENUM) information, use the debug voip enum command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip enum {detail | summary} no debug voip enum {detail | summary}

Syntax Description

detail

Displays detailed output.

summary

Displays summary output.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Usage Guidelines

Disable console logging and use buffered logging before using the debug voip enum command. Using the debug voip enum command generates a large volume of debugs, which can affect router performance.

Examples

The following shows sample output from the debug voip enum detail command: The output shows the match number as 5108891234, enum table as 10. Rule 1 in table 10 matched the pattern and after applying the replacement rule, the resulting string is 5108891234. The enum query is sent out for the domain 4.3.2.1.9.8.8.0.1.5.e164.cisco.com. The output then shows the matching Naming Authority Pointer (NAPTR) records obtained in the response. The records are then processed and the final URLs (contact lists) are shown toward the end. Router# debug voip enum detail enum_resolve_domain:match_num 5108891234 table_indx 10 enum_resolve_domain:rule 1 result string 5108891234 generate_enum_search_string :search string 4.3.2.1.9.8.8.0.1.5.e164.cisco.com enum_dns_query:name = 4.3.2.1.9.8.8.0.1.5.e164.cisco.com type = 35, ns_server = 0 order 100 pref 10 service sip+E2U flag U regexp /^.*$/sip:[email protected]/ replacement order 200 pref 10 service h323+E2U flag U regexp /^.*$/h323:[email protected]/ replacement


DB-2393


num_elem = 2 NAPTR Record :order 100 pref 10 service sip+E2U flags U regexp /^.*$/sip:[email protected]/ replacement NAPTR Record :order 200 pref 10 service h323+E2U flags U regexp /^.*$/h323:[email protected]/ replacement decode_naptr_record :re_string ^.*$ decode_naptr_record :re_substitution_string sip:[email protected] decode_naptr_record :re_flags_string U_FLAG case, stopping query new_e164_user sip:[email protected] decode_naptr_record :re_string ^.*$ decode_naptr_re tahoe13#cord :re_substitution_string h323:[email protected] decode_naptr_record :re_flags_string U_FLAG case, stopping query new_e164_user h323:[email protected] contact_list : sip:[email protected] contact_list : h323:[email protected] enum_resolve_domain:contact_list 64558450

A sample output of the debug voip enum summary command is shown below. The output shows the matching number, the enum table used and the rule in the table that matched the number along with the resulting string. Note that this output is a subset of the output from debug voip enum detail command. Router# debug voip enum summary enum_resolve_domain:match_num 5108891234 table_indx 10 enum_resolve_domain:rule 1 result string 5108891234

Table 371 provides an alphabetical listing of the debug voip enum command fields and a description of each field. Table 371

debug voip enum Field Descriptions

Field

Description

contact_list

Final list of URLs that the gateway will try to contact as an attempt to place the call.

flag

Flag value of a NAPTR record as defined in RFC 2915.

match_num

Number to be used for matching against the enum match table.

name

Fully qualified domain name sent out to Domain Name System (DNS) server

ns_server

Address of the DNS server. If 0, the DNS server configured on the gateway is used.

num_elem

Number of records received in the response.

order

Order in the record, as defined in RFC 2915.

pref

Preference of the record, as defined in RFC 2915.

regexp

Regular expression of the record, as defined in RFC 2915.

replacement

Replacement string of the record, as defined in RFC 2915.


DB-2394

May 2008


Table 371

debug voip enum Field Descriptions (continued)

Field

Description

re_flags_string

Flag indicating whether matching and replacement should be case sensitive: •

i = Case insensitive

•

otherwise = Case sensitive

re_string

The first part of the regexp, delimited by “/”. This is used to match the incoming string. Refer to RFC 2915.

re_substitution_string

The second part of regexp, delimited by “/”.

result string

String that results when match_num is taken through the enum match table for a match. This string will be used to form a FQDN.

rule

Rule number that matched match_num in the enum match table.

search string

String sent out to the DNS server.

service

Service field of the NAPTR record. Refer to RFC 2915.

table_indx

Index of the enum match table picked for this call.

type

Type of record requested in the query: 35 = NAPTR 33 = DNS Service (SRV)

Related Commands

Command

Description

rule (ENUM configuration)

Defines the rule pattern for an ENUM match table.

show voice enum-match-table

Displays the ENUM match table rules.

test enum

Tests the ENUM match table rules.

voice enum-match-table

Initiates the ENUM match table definition.


DB-2395

Debug Commands debug voip event-log

debug voip event-log To enable debugging of the event log module, use the debug voip event-log command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip event-log no debug voip event-log

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Examples

The following is sample output from the debug voip event-log command: Router# debug voip event-log voip event-log debugging is on Router# *Jul 18 22:22:45.417: voice_elog_open: ctx_id=1F, size=4, url= *Jul 18 22:22:45.417: lock_elog, ctx_id=1F, refcnt=1 *Jul 18 22:22:45.417: voice_elog_write: *Jul 18 22:22:45.417: elog_write_local: message (len=143) written to elog: 1F:1058566965:584:INFO: Call setup indication received, called = 4085550198, calling = 52927, echo canceller = enable, direct inward dialing 3953 bytes left *Jul 18 22:22:45.417: voice_elog_write: *Jul 18 22:22:45.417: elog_write_local: message (len=38) written to elog: 1F:1058566965:585:INFO: Dialpeer = 1 3915 bytes left *Jul 18 22:22:45.421: voice_elog_open: ctx_id=B, size=4, url= *Jul 18 22:22:45.421: lock_elog, ctx_id=B, refcnt=1 *Jul 18 22:22:45.421: voice_elog_write: *Jul 18 22:22:45.421: elog_write_local: message (len=114) written to elog: B:1058566965:586:INFO: Session started for App-type = generic, URL = tftp://demo/scripts/master/generic.vxml 3982 bytes left *Jul 18 22:22:45.421: voice_elog_write: *Jul 18 22:22:45.421: elog_write_local: message (len=69) written to elog: B:1058566965:587:INFO: Incoming Telephony call received, LegID = 1F 3913 bytes left *Jul 18 22:22:45.421: voice_elog_write: *Jul 18 22:22:45.421: elog_write_local: message (len=89) written to elog: B:1058566965:588:INFO: LegID = 1F: Calling = 4085550198, called = 52927, dial peer = 1 3824 bytes left *Jul 18 22:22:45.421: voice_elog_write: *Jul 18 22:22:45.421: elog_write_local: message (len=66) written to elog: B:1058566965:589:INFO: LegID = 1F: Leg State = LEG_INCCONNECTED 3758 bytes left *Jul 18 22:22:45.433: voice_elog_write: *Jul 18 22:22:45.437: elog_write_local: message (len=42) written to elog:


DB-2396

May 2008

Debug Commands debug voip event-log

1F:1058566965:590:INFO: Digit collection 3873 bytes left *Jul 18 22:22:45.437: voice_elog_write: *Jul 18 22:22:45.437: elog_write_local: message (len=57) written to elog: 1F:1058566965:591:INFO: Call connected using codec None 3816 bytes left *Jul 18 22:22:45.437: voice_elog_write: *Jul 18 22:22:45.437: elog_write_local: message (len=85) written to elog: B:1058566965:592:INFO: Playing prompt #1: tftp://172.19.139.245/audio/ch_welcome.au 3673 bytes left Router# *Jul 18 22:22:55.942: voice_elog_write: *Jul 18 22:22:55.942: elog_write_local: message (len=51) written to elog: B:1058566975:593:ERR : Prompt play setup failure. 3622 bytes left *Jul 18 22:22:55.942: voice_elog_write: *Jul 18 22:22:55.942: elog_write_local: message (len=65) written to elog: B:1058566975:594:INFO: Script received event = "error.badfetch" 3557 bytes left *Jul 18 22:22:56.918: voice_elog_write: *Jul 18 22:22:56.918: elog_write_local: message (len=98) written to elog: 1F:1058 Router# 566976:595:INFO: Inform application call disconnected (cause = normal call clearing (16)) 3718 bytes left *Jul 18 22:22:56.918: voice_elog_write: *Jul 18 22:22:56.918: elog_write_local: message (len=78) written to elog: B:1058566976:596:INFO: Script received event = "telephone.disconnect.hangup" 3479 bytes left *Jul 18 22:22:56.922: voice_elog_write: *Jul 18 22:22:56.922: elog_write_local: message (len=89) written to elog: B:1058566976:597:INFO: LegID = 1F: Call disconnected, cause = normal call clearing (16) 3390 bytes left *Jul 18 22:22:56.922: voice_elog_write: *Jul 18 22:22:56.922: elog_write_local: message (len=79) written to elog: 1F:1058566976:598:INFO: Call disconnected (cause = normal call clearing (16)) 3639 bytes left *Jul 18 22:22:56.930: voice_elog_write: *Jul 18 22:22:56.930: elog_write_local: message (len=39) written to elog: 1F:1058566976:599:INFO: Call released 3600 bytes left *Jul 18 22:22:56.930: voice_elog_close, ctx_id=1F voice_elog_close, ctx_id=19 *Jul 18 22:22:56.930: unlock_elog, ctx_id=19, refcnt=0 *Jul 18 22:22:56.930: delete_elog, ctx_id=19 *Jul 18 22:22:56.930: voice_elog_write: *Jul 18 22:22:56.930: elog_write_local: message (len=59) written to elog: B:1058566976:600:INFO: Session done, terminating cause = 3331 bytes left *Jul 18 22:22:56.930: voice_elog_close, ctx_id=B

Related Commands

Command

Description

call application event-log

Enables event logging for voice application instances.

debug voip ais

Enables debugging of the AIS database.


DB-2397

Debug Commands debug voip h221

debug voip h221 To debug telephony call control information, use the debug voip h221 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip h221 [all | default | error [call [informational] | software [informational]] | function | individual | inout | raw [decode]] no debug voip h221

Syntax Description

all

(Optional) Enables all H.221 debugging, except the raw option.

default

(Optional) Activates function, inout, error call, and software debugging.

error

(Optional) Enables H.221 call error and software error debugging.

error [call]

(Optional) Enables H.221 major call processing error debugs related to the H.221 subsystem.

error [call [informational]]

(Optional) Enables H.221 major and informational call processing error debugs related to the H.221 subsystem.

error [software]

(Optional) Enables H.221 major software error debugs related to the H.221 subsystem.

error [software [informational]]

(Optional) Enables H.221 major and informational software error debugs related to the H.221 subsystem.

function


individual

(Optional) Activates individual H.221 debugging.

inout


raw

(Optional) Displays raw BAS messages.

raw [decode]

(Optional) Decodes raw BAS data.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.4(11)T


12.2SX


Usage Guidelines

Note

This command enables debugging for H.221 message events (voice telephony call control information).

This command provides the same results as the debug voice h221 command.


DB-2398

May 2008

Debug Commands debug voip h221

Caution

We recommend that you log the output from the debug voip h221 all command to a buffer, rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway. Use the debug voip h221 individual x command, (where x is an index number for a debug category), to activate a single debug, selected by index number instead of entering a group of debug commands. See Table 372 for a list of debug categories and corresponding index numbers. Table 372

Examples

Indexes and Categories for the debug voip h221 individual command

Index Number

Debug Category

1, 2, 30, 31, 32

Secondary number exchange

5, 6, 14, 15, 16, 22

Audio mode/caps

7, 10, 12, 13, 17, 28

Video mode/caps

8, 9, 23

B-channel mode/caps

11, 24, 33

Miscellaneous command exchange

18

Bandwidth calculations

19, 20, 21

DSP configuration

3, 4, 25, 27, 42, 43

General caps/internal

26

Non-standard caps/command

29

Loop request

34, 35, 36, 37, 38, 39, 40, 41

BAS squelch

The raw keyword displays the raw BAS information coming from or to the DSP. It is displayed in a hexadecimal octet format. The decode option decodes the BAS information into a readable English format. The following is sample output from the debug voip h221 raw decode command: BAS=81:1 BAS=82:1 BAS=84:1 BAS=85:1 BAS=F9:1 BAS=02:0 BAS=0A:0 BAS=8A:1 BAS=8A:BAS=8A:BAS=8A:-

Related Commands

0 0 0 0 1 0 0 0 -

0 0 0 0 1 0 0 0 -

0 0 0 0 1 0 0 0 -

0 0 0 0 1 0 1 1 -

0 0 1 1 0 0 0 0 -

0 1 0 0 0 1 1 1 -

1: 0: 0: 1: 1: 0: 0: -: -: -: 0:

AUDIO CAPS=g711 a-law AUDIO CAPS=g711 u-law AUDIO CAPS=g722 48k AUDIO CAPS=g728 H.242 MBE start indication H.242 MBE length=2 H.242 MBE type=H.263 caps Always 1 H.263 MPI=1 H.263 FORMAT=h.263_cif No additional options

Command

Description

debug voip ccapi

Enables debugging for the call control application programming interface (CCAPI) contents.

debug voip rtp

Enables debugging for Real-Time Transport Protocol (RTP) named event packets.


DB-2399

Debug Commands debug voip hpi

debug voip hpi To enable debugging for Host Port Interface (HPI) message events, use the debug voip hpi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip hpi [all | command | default | detail | error [call [informational] | software [informational]] | function | inout | notification | response | stats | checker] no debug voip hpi

Syntax Description

all

(Optional) Displays all HPI debugging messages.

command

(Optional) Displays commands that are being sent to the 54x DSP.

default

(Optional) Displays HPI detail, error, and inout debugging messages and also runs if no keywords are added.

detail

(Optional) Displays detailed information about commands for the HPI. This command is used in conjunction with other debug voip hpi commands to show additional details when you use the command, notification, and response keywords.

error

(Optional) Displays HPI error messages.

call


informational

(Optional) Displays minor and major errors. Without the informational keyword, only major errors are displayed.

software


function

(Optional) Displays HPI functions.

inout

(Optional) Displays the output for the command, notification, response, and stats keywords.

notification

(Optional) Displays notification messages that are sent from the 54x DSP (for example, tone detection notification).

response

(Optional) Displays responses to commands that are sent by the 54x DSP (for example, responses to statistic requests).

stats

(Optional) Displays HPI statistics.

checker

(Optional) Displays HPI checker operations.

Defaults


Command Modes

Privileged EXEC


DB-2400

May 2008


Command History

Usage Guidelines

Release

Modification

12.3(8)T

This command replaces the debug hpi command.

12.3(14)T

The checker keyword was added.

12.2SX


This command enables debugging for HPI message events, which are used to communicate with digital signal processors (DSPs). Use the debug voip hpi all command to view gateway DSP modem relay termination codes. The DSP-to-host messages for the modem relay termination indicate to the host the modem relay session termination time, physical or link layer, and other probable causes for disconnection. On receiving this indication from the DSP, the host can disconnect the call or place the channel in the modem passthrough state.

Examples

The following is sample output from the debug voip hpi all command for an incoming ISDN call: Router# debug voip hpi all 01:28:44: //-1/xxxxxxxxxxxx/HPI/[]/hpi_dspmgr_open:

The following event shows that the HPI has identified the call, as shown by the GUID, but the call leg has not been specified, as shown by the -1 value in the CallEntry ID: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_dspmgr_open: Allocated DSP resource: dsp_intf=0x64AF0EEC hpi_cdb=0x64ACED34 ret=1 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_dspmgr_open: Exit Line # 9411 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_init: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_init: Open channel 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_init: Packet details: Packet Length (16), Channel Id (1), Packet Id (74) ALawULawSelect=A Law Associated SignalingChannel (128) Timeslot=0 SerialPort=0 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_voice_config_params:

For each packet-related event, information about the packet is shown following the event. The following two events show the Real-Time Protocol (RTP) packet: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_encap_config: RTP information 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_encap_config: Packet details: Packet Length (38), Channel Id (1), Packet Id (92) TransportProtocol=2 t_ssrc=0x00 r_ssrc=0x00 t_vpxcc=0x0 r_vpxcc=0x0 sid_support=0 tse_payload=101 seq_num=0x0 redundancy=0 cc_payload_type=0 fax_payload_type=0 alaw_pcm_switchover=0 mulaw_pcm_switchover=0 dtmf_payload_type=0 nte_rcv_payload_type=101 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_set_playout_config: Packet details: Packet Length (18), Channel Id (1), Packet Id (76)


DB-2401


Mode=1, Initial=60, Min=40, Max=200, fax_nom=300 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_inband_sig: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_fax_enable: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_fax_enable: Enable FAX 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_fax_enable: Packet details: Packet Length (8), Channel Id (1), Packet Id (67) 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_echo_cancel: Packet details: Packet Length (14), Channel Id (1), Packet Id (66) flags=0x00000B00, Threshold=-21, SuppressorCoverage=7 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_idle_code_det: Packet details: Packet Length (14), Channel Id (1), Packet Id (116) Enable (FALSE), Code=0x00000000, Duration (6000 ms) 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_set_gain: Packet details: Packet Length (12), Channel Id (1), Packet Id (91) Gain: In=0, Out=0 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/caplog_hpi_msg_log: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_cng_config: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_info_field_size_config: 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_digit_relay_config: Exit Line # 4162 01:28:44: //-1/3FE022AC8009/HPI/[2/0:23]/hpi_dspmgr_update_callid:

At this point, the HPI identifies the call leg, as shown by the CallEntry ID changing from -1 to 11. 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_voice_get_capabilities: Exit Line # 5073 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_stop_service: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_idle_service: Packet details: Packet Length (8), Channel Id (1), Packet Id (68) 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_open_service: Setting codec g729r8 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_set_codec: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_dsprm_callback: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_voice_config_params: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_digit_relay_config: Exit Line # 4162

The RTP packet is shown again, but now more information is available, such as payload types. The packet ID identifies this as the same RTP packet shown earlier. 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_encap_config: RTP information 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_encap_config: Packet details: Packet Length (38), Channel Id (1), Packet Id (92) TransportProtocol=2 t_ssrc=0x040 r_ssrc=0x00 t_vpxcc=0x0 r_vpxcc=0x0 sid_support=1 tse_payload=101 seq_num=0x13D3 redundancy=0 cc_payload_type=125 fax_payload_type=122 alaw_pcm_switchover=8 mulaw_pcm_switchover=0 dtmf_payload_type=121 nte_rcv_payload_type=101 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_pak_suppress: Stop packet suppression 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_pak_suppress:


DB-2402

May 2008


Packet details: Packet Length (10), Channel Id (1), Packet Id (106) Mode=1 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_vad_enable: Packet details: Packet Length (18), Channel Id (1), Packet Id (78) VAD=1 (ON): Threshold=-38, VADTime=250 Aggressive=0, Noise=-62 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_init: Open channel 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_init: Packet details: Packet Length (16), Channel Id (1), Packet Id (74) ALawULawSelect=A Law Associated SignalingChannel (128) Timeslot=0 SerialPort=0 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_voice_config_params: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_encap_config: RTP information 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_encap_config: Packet details: Packet Length (38), Channel Id (1), Packet Id (92) TransportProtocol=2 t_ssrc=0x040 r_ssrc=0x00 t_vpxcc=0x0 r_vpxcc=0x0 sid_support=1 tse_payload=101 seq_num=0x13D3 redundancy=0 cc_payload_type=125 fax_payload_type=122 alaw_pcm_switchover=8 mulaw_pcm_switchover=0 dtmf_payload_type=121 nte_rcv_payload_type=101 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_set_playout_config: Packet details: Packet Length (18), Channel Id (1), Packet Id (76) Mode=1, Initial=60, Min=40, Max=200, fax_nom=300 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_inband_sig:

In the following several events, fax is enabled. Packets for echo cancellation, gain, voice activity detection (VAD), and other parameters appear. 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_fax_enable: Enable FAX 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_fax_enable: Packet details: Packet Length (8), Channel Id (1), Packet Id (67) 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_echo_cancel: Packet details: Packet Length (14), Channel Id (1), Packet Id (66) flags=0x00000B00, Threshold=-21, SuppressorCoverage=7 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_idle_code_det: Packet details: Packet Length (14), Channel Id (1), Packet Id (116) Enable (FALSE), Code=0x00000000, Duration (6000 ms) 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_set_gain: Packet details: Packet Length (12), Channel Id (1), Packet Id (91) Gain: In=0, Out=0 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_cng_config: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_info_field_size_config: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_digit_relay_config: Exit Line # 4162 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_start_service:


DB-2403


01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_voice_mode: Packet details: Packet Length (28), Channel Id (1), Packet Id (73) CodingType=20, Voice FieldSize (20), VAD Flag (250), EchoLength=512, ComfortNoise=1, inband_detect=0x00000001, DigitRelay=2, AGC Flag=0, ECAN TestGroup=0, ECAN TestNumber=0, DynamicPayload=0 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_idle_code_det: Packet details: Packet Length (14), Channel Id (1), Packet Id (116) Enable (FALSE), Code=0x00000000, Duration (6000 ms) 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_start_service: Exit Line # 2816 01:28:44: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_send_data_to_dsp: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_info:

Transmit and receive events are shown, along with packet information. 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_tx: Packet details: Packet Length (10), Channel Id (1), Packet Id (86) ResetFlag (0x00000000) 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_rx: Packet details: Packet Length (10), Channel Id (1), Packet Id (87) ResetFlag (0x00000000) 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_pd: Playout delay 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_pd: Packet details: Packet Length (10), Channel Id (1), Packet Id (83) ResetFlag (0x00000000) 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_pe: Playout error 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_pe: Packet details: Packet Length (10), Channel Id (1), Packet Id (84) ResetFlag (0x00000000) 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_query_info: Exit Line # 6578 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_message: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log:

Statistics for each of the events are displayed. 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_query_tx: Got TX stats Packet details: Packet Length (36), Channel Id (1), Packet Id (199) TX Packets (87), Signaling Packets (0) ComfortNoise Packets (0) Transmit Duration (1750) Voice Transmit Duration (1750), FAX Transmit Duration (0) 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_message: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_query_rx: Got RX stats Packet details: Packet Length (120), Channel Id (1), Packet Id (200)


DB-2404

May 2008


RX Packets (5): Signaling (0), ComfortNoise (1) Receive Duration (1750): Voice (70) FAX (0) Packet Counts: OOSequence (0), Bad header (0), Late (1), Early (0) 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_message: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_query_pd: Got Playout Delay stats... Packet details: Packet Length (24), Channel Id (1), Packet Id (196) RX Delay: CurrentEstimate=69 Low WaterMark (69) High WaterMark (70) Clock Offset (-279863943) 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_message: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/caplog_hpi_msg_log: 01:28:46: //11/3FE022AC8009/HPI/[2/0:23:11]/hpi_receive_query_pe: Got Playout Error stats Packet details: Packet Length (32), Channel Id (1), Packet Id (197) Predictive Concealment Duration (0) Interpolative Concealment Duration (0) Silence Concealment Duration (0) Retroactive Memory Update (0) Buffer overflow discard duration (10) Talkspurt Detection Errors (0)

The following sample output from the debug voip hpi checker command helps verify the operations of the HPI checker: Router# debug voip hpi checker *May 19 06:30:53.532: hpi [] DSP [0/0x0] S_HPI_CLOSED(0) E_HPI_DSPRM_OPEN/SET_CODEC(54) *May 19 06:30:53.532: hpi [] DSP [0/0x0] -> S_HPI_CLOSED(0) *May 19 06:30:53.620: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_CLOSED(0) E_HPI_DSP_OPEN_VOICE_CHANNEL(11) *May 19 06:30:53.620: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1) *May 19 06:30:53.620: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSPRM_OPEN/SET_CODEC(54) *May 19 06:30:53.620: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1) *May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_ENC_CONFIG(29) *May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1) *May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_SET_VOICE_PLAYOUT_DELAY(13) *May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1) *May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_IDLE_CODE_CONTROL (50) *May 19 06:30:53.624: hpi [2/0:23 (22)] DSP [0/0x0] -> S_HPI_IDLE(1) *May 19 06:30:53.624: hpi [2/0:23 (22)] *May 19 06:30:53.624: hpi [2/0:23 (22)] *May 19 06:30:53.624: hpi [2/0:23 (22)] E_HPI_DSP_GEN_PACKET_CONTROL(41) *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] E_HPI_DSP_ECHO_CANCELLER_CONTROL(3) *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] E_HPI_DSP_DIGIT_RELAY(22) *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] E_HPI_DSP_VAD_ENABLE(15) *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.632: hpi [2/0:23 (22)] E_HPI_DSP_GEN_PACKET_CONTROL(41)

DSP [0/0x0] S_HPI_IDLE(1) E_HPI_DSP_VOICE_MODE(10) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP DSP DSP DSP

[0/0x0] [0/0x0] [0/0x0] [0/0x0]

-> S_HPI_VOICE(2) S_HPI_VOICE(2) E_HPI_DSP_SET_GAINS(28) -> S_HPI_VOICE(2) S_HPI_VOICE(2)

DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2)


DB-2405


*May 19 06:30:53.632: hpi [2/0:23 (22)] *May 19 06:30:53.632: hpi [2/0:23 (22)] E_HPI_DSP_INBAND_DETECTOR_CONTROL(45) *May 19 06:30:53.632: hpi [2/0:23 (22)] *May 19 06:30:53.636: hpi [2/0:23 (22)] E_HPI_DSP_INBAND_DETECTOR_CONTROL(45) *May 19 06:30:53.636: hpi [2/0:23 (22)] *May 19 06:30:53.624: hpi [2/0:23 (22)] *May 19 06:30:53.624: hpi [2/0:23 (22)] *May 19 06:30:53.624: hpi [2/0:23 (22)] E_HPI_DSP_GEN_PACKET_CONTROL(41) *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] E_HPI_DSP_ECHO_CANCELLER_CONTROL(3) *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] E_HPI_DSP_DIGIT_RELAY(22) *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.628: hpi [2/0:23 (22)] E_HPI_DSP_VAD_ENABLE(15) *May 19 06:30:53.628: hpi [2/0:23 (22)] *May 19 06:30:53.632: hpi [2/0:23 (22)] E_HPI_DSP_GEN_PACKET_CONTROL(41) *May 19 06:30:53.632: hpi [2/0:23 (22)] *May 19 06:30:53.632: hpi [2/0:23 (22)] E_HPI_DSP_INBAND_DETECTOR_CONTROL(45) *May 19 06:30:53.632: hpi [2/0:23 (22)] *May 19 06:30:53.636: hpi [2/0:23 (22)] E_HPI_DSP_INBAND_DETECTOR_CONTROL(45) *May 19 06:30:53.636: hpi [2/0:23 (22)]

DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2)

*May 19 06:30:56.512: hpi [2/0:23 (22)] E_HPI_DSP_GET_TX_STAT(23) *May 19 06:30:56.512: hpi [2/0:23 (22)] *May 19 06:30:56.512: hpi [2/0:23 (22)] E_HPI_DSP_GET_RX_STAT(24) *May 19 06:30:56.512: hpi [2/0:23 (22)] *May 19 06:30:56.512: hpi [2/0:23 (22)] E_HPI_DSP_GET_VOICE_PLAYOUT_DELAY(20) *May 19 06:30:56.512: hpi [2/0:23 (22)] *May 19 06:30:56.512: hpi [2/0:23 (22)] E_HPI_DSP_GET_VOICE_PLAYOUT_ERROR(21) *May 19 06:30:56.512: hpi [2/0:23 (22)] *May 19 06:30:59.384: hpi [2/0:23 (22)] E_HPI_DSP_GET_TX_STAT(23) *May 19 06:30:59.384: hpi [2/0:23 (22)] *May 19 06:30:59.384: hpi [2/0:23 (22)] E_HPI_DSP_GET_RX_STAT(24) *May 19 06:30:59.384: hpi [2/0:23 (22)] *May 19 06:30:59.384: hpi [2/0:23 (22)] E_HPI_DSP_GET_VOICE_PLAYOUT_DELAY(20) *May 19 06:30:59.384: hpi [2/0:23 (22)] *May 19 06:30:59.384: hpi [2/0:23 (22)] E_HPI_DSP_GET_VOICE_PLAYOUT_ERROR(21) *May 19 06:30:59.384: hpi [2/0:23 (22)] *May 19 06:31:06.524: hpi [2/0:23 (22)] E_HPI_DSP_GEN_PACKET_CONTROL(41) *May 19 06:31:06.524: hpi [2/0:23 (22)] *May 19 06:31:06.532: hpi [2/0:23 (22)] E_HPI_DSP_GET_LEVELS(26) *May 19 06:31:06.536: hpi [2/0:23 (22)]

DSP [0/0x0] S_HPI_VOICE(2)

DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP DSP DSP DSP

[0/0x0] [0/0x0] [0/0x0] [0/0x0]

-> S_HPI_VOICE(2) S_HPI_IDLE(1) E_HPI_DSP_VOICE_MODE(10) -> S_HPI_VOICE(2) S_HPI_VOICE(2)

DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP DSP DSP DSP

[0/0x0] [0/0x0] [0/0x0] [0/0x0]

-> S_HPI_VOICE(2) S_HPI_VOICE(2) E_HPI_DSP_SET_GAINS(28) -> S_HPI_VOICE(2) S_HPI_VOICE(2)

DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2)

DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2) DSP [0/0x0] S_HPI_VOICE(2) DSP [0/0x0] -> S_HPI_VOICE(2)


DB-2406

May 2008


*May 19 06:31:06.536: hpi [2/0:23 E_HPI_DSP_GET_ERROR_STAT(0) *May 19 06:31:06.536: hpi [2/0:23 *May 19 06:31:06.572: hpi [2/0:23 *May 19 06:31:06.572: hpi [2/0:23 *May 19 06:31:06.572: hpi [2/0:23 E_HPI_DSP_CLOSE_VOICE_CHANNEL(12) *May 19 06:31:06.572: hpi [2/0:23 *May 19 06:31:06.576: hpi [2/0:23 *May 19 06:31:06.576: hpi [2/0:23

Related Commands

(22)] DSP [0/0x0] S_HPI_VOICE(2) (22)] (22)] (22)] (22)]

DSP DSP DSP DSP

[0/0x0] [0/0x0] [0/0x0] [0/0x0]

-> S_HPI_VOICE(2) S_HPI_VOICE(2) E_HPI_DSP_IDLE_MODE(5) -> S_HPI_IDLE(1) S_HPI_IDLE(1)

(22)] DSP [0/0x0] -> S_HPI_CLOSED(0) (22)] DSP [0/0x0] -> S_HPI_CLOSED(0) (22)] DSP [0/0x0] -> S_HPI_CLOSED(0)

Command

Description

show voice hpi capture

Verifies capture status and statistics.


DB-2407

Debug Commands debug voip ipipgw

debug voip ipipgw To turn on debugging for the Cisco Multiservice IP-to-IP Gateway (IPIPGW), use the debug voip ipipgw command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip ipipgw no debug voip ipipgw

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(13)T3


12.2SX


Examples

The following example shows debugging output from a Cisco IPIPGW: Aug 8 15:24:30.626 EDT: cch323_build_early_fastStart_cap_response: ccb-remote_fastStart=0x63C20630 Aug 8 15:24:30.626 EDT: cch323_build_early_fastStart_cap_response:symm_mask=1,tempOtherCodec=5,templocalCodec=5,au dioFastStartArray=0x63C1299C The following line shows fast start response beginning for the inbound leg of the IP-to-IP call: Aug 8 15:24:30.626 EDT: cch323_build_early_fastStart_cap_response: Assuming ipipgw on inbound leg. Aug 8 15:24:30.626 EDT: Function: cch323_build_olc_for_ccapi, Line: 1198, audioFastStartArray=0x63C1299C Aug 8 15:24:30.626 EDT: cch323_build_olc_for_ccapi: channel_info ptr=0x63C203F0, ccb ptr=0x63C18580 The following lines indicate the inbound call leg will send the channel information to the outbound call leg (not yet created): Aug

8 15:24:30.626 EDT: cch323_build_olc_for_ccapi: Channel Information: Logical Channel Number (fwd/rev): 1 Channel address (fwd/rev): 0x10C0C27 RTP Channel (fwd/rev): 19362 RTCP Channel (fwd/rev): 19363 QoS Capability (fwd/rev): 0


DB-2408

May 2008


Aug

Symmetric Audio Cap Mask: 0x1 Symmetric Audio Codec Bytes: 160 Flow Mode: 0 Silence Suppression: 0 8 15:24:30.626 EDT: cch323_build_olc_for_ccapi:NumOfElements = 1 idx = 1

The following line indicates the inbound call leg is set to work in IP-to-IP mode (0xF0): Aug

8 15:24:30.630 EDT: cch323_set_h245_state_mc_mode_incoming: h245 state m/c mode=0xF0

The following line indicates flow mode for incoming call leg is set to FLOW_THROUGH (incoming callid = 35). At this point Session Application opens the outbound leg. Some output is omitted here. Aug Aug

8 15:24:30.630 EDT: cch323_media_flow_mode: IPIPGW(35):Flow Mode=1 8 15:24:30.630 EDT: cch323_set_h245_state_mc_mode_outgoing:call_spi_mode = 1

The following line indicates the outbound call leg is set to work in IP-to-IP mode (0xF0): Aug 8 15:24:30.630 Aug 8 15:24:30.630 Aug 8 15:24:30.630 Aug 8 15:24:30.630 pref mask=FFFFFFFF Aug 8 15:24:30.630 codec(bytes)=5(160)

EDT: EDT: EDT: EDT:

cch323_set_h245_state_mc_mode_outgoing: h245 state m/c mode=0xF0 cch323_get_peer_info line 1022: cch323_get_peer_info line 1026: cch323_set_pref_codec_list:IPIPGW(36):peer channel present: dp

EDT: cch323_set_pref_codec_list:IPIPGW(36):first preferred

The following line indicates the outbound call leg is set to FLOW_THROUGH (outbound callid = 36): Aug 8 15:24:30.630 EDT: cch323_get_peer_info: Flow Mode set to FLOW_THROUGH for callId 36 Aug 8 15:24:30.642 EDT: cch323_build_local_encoded_fastStartOLCs: state_mc_mode=0xF0 on outbound leg. Aug 8 15:24:30.642 EDT: cch323_build_local_encoded_fastStartOLCs:srcAddress = 0x10C0C30, h245_lport = 0, flow mode = 1, minimum_qos=0 Aug 8 15:24:30.642 EDT: cch323_generic_open_logical_channel: IPIPGW: current codec = 5:160:160.

The following line indicates the IPIPGW received fast start response from the remote (called party) entity of the outbound call leg: Aug 8 15:24:30.658 EDT: Function: cch323_receive_fastStart_cap_response Line: 2800 Aug 8 15:24:30.658 EDT: Function: cch323_build_olc_for_ccapi, Line: 1198, audioFastStartArray=0x63C1259C Aug 8 15:24:30.658 EDT: cch323_build_olc_for_ccapi: channel_info ptr=0x63C12738, ccb ptr=0x631A4D68 Aug 8 15:24:30.658 EDT: cch323_build_olc_for_ccapi: Channel Information: Logical Channel Number (fwd/rev): 1 Channel address (fwd/rev): 0x10C0C28 RTP Channel (fwd/rev): 19128 RTCP Channel (fwd/rev): 19129 QoS Capability (fwd/rev): 0 Symmetric Audio Cap Mask: 0x1 Symmetric Audio Codec Bytes: 160 Flow Mode: 0 Silence Suppression: 0 Aug 8 15:24:30.658 EDT: cch323_build_olc_for_ccapi:NumOfElements = 1 idx = 1 Aug 8 15:24:30.658 EDT: Function: cch323_do_open_channel_ind Line: 1080 Aug 8 15:24:30.658 EDT: Function: cch323_open_channel_ind Line: 1132

The following lines indicates the outbound call leg (36) sends the channel response back to the inbound call leg (35) via CCAPI: Aug 8 15:24:30.658 EDT: cch323_receive_fastStart_cap_response: callID 0x24(36), audioFastStartArray = 0x0. Aug 8 15:24:30.658 EDT: cch323_peer_channel_ind: IPIPGW:### chn info coming in chn_ind()


DB-2409


Aug 8 15:24:30.658 EDT: cch323_peer_channel_ind: IPIPGW(35):giving event to Fast start logic. Aug 8 15:24:30.658 EDT: Function: cch323_do_open_channel Line: 5557 Aug 8 15:24:30.658 EDT: cch323_do_open_channel: line:5566, ccb->status=0x4000000 Aug 8 15:24:30.658 EDT: cch323_do_open_channel:srcAddress = 0x10C0C30, h245_lport = 18308, minimum_qos=0 Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: Start... Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: selectCodec=5, codec_mask=1, configured_codecBytes=160 forward_codecBytes=160, reverse_codecBytes=160, audioFastStartArray=0x63C1299C Aug 8 15:24:30.658 EDT: cch323_prepare_fastStart_cap_response line 2138 Aug 8 15:24:30.658 EDT: cch323_prepare_fastStart_cap_response: callID 0x23(35), audioFastStartArray = 0x0. Aug 8 15:24:30.658 EDT: cch323_prepare_fastStart_cap_response, ccb->local_fastStart=0x63C183C0, srcAddr=0x10C0C30, lport=18308, rport=19362, rc=1 Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: local_fastStart=0x63C183C0, negotiated_codec=5, negotiated_codec_bytes=160 Aug 8 15:24:30.658 EDT: cch323_build_fastStart_cap_response: Received peer cap info. Notify RAS state machine (possible BRQ).

Outbound leg, at this point, has prepared the fast start response to be sent to the originating (calling party). This is sent in the next outgoing call control message (such as ALERT or PROGRESS): Aug Aug Aug Aug Aug

8 8 8 8 8

15:24:30.658 15:24:30.658 15:24:30.674 15:24:30.674 15:24:30.678

EDT: EDT: EDT: EDT: EDT:

cch323_build_fastStart_cap_response: Done. cch323_do_open_channel: line:5644, ccb->status=0x4004200 cch323_h245_connection_sm: state = 0 event=5 ccb=63C18580 cch323_h245_connection_sm: listen state=0 cch323_h245_cap_ind: IPIPGW(35): masks au=0x1 data=0xC uinp=0x32.

The following line indicates the inbound call leg (35) received capability set (CAPSET) message: Aug 8 15:24:30.678 EDT: cch323_run_h245_cap_in_sm:IPIPGW(35): got incoming CAPSET msg. Aug 8 15:24:30.678 EDT: cch323_do_transparent_cap_ind: IPIPGW(35):mask sent to other leg=1

The following lines show the inbound call leg (35) forwarding the TCS to the outbound leg and waiting for the response of the outbound call leg (TCSACK or TCSREJ): Aug sent Aug peer

8 15:24:30.678 EDT: cch323_run_h245_cap_in_sm:IPIPGW(35):suppressTCS: our TCS will be based on peer. 8 15:24:30.678 EDT: cch323_h245_cap_notify:IPIPGW(35):not xmiting CAPSACK: wait for to ack.

Aug 8 15:24:30.678 EDT: cch323_caps_ind: IPIPGW(36):setting the mask to new : current mask=0x4FFFF new mask=0x1. Aug 8 15:24:30.678 EDT: cch323_caps_ind: IPIPGW(36): ExtendedCapsPresent Aug 8 15:24:30.678 EDT: cch323_set_dtmf_relay_mask: IPIPGW(36): extract dtmf-caps from caps struct Aug 8 15:24:30.678 EDT: cch323_set_dtmf_relay_mask: IPIPGW(36): After extracting dtmf-caps from caps structccb->user_caps.user_input_bit_mask[0x1C]

The following line shows the outbound leg sending the TCS to the called party. No codec filter is configured on outbound dial-peer (FFFFFFFF): Aug 8 15:24:30.678 caps:5:1:FFFFFFFF Aug 8 15:24:30.678 Aug 8 15:24:30.678 Aug 8 15:24:30.678 Aug 8 15:24:30.678 Aug 8 15:24:30.678 machine. Aug 8 15:24:30.678

EDT: cch323_prepare_preferred_codec_list: IPIPGW(36):munging EDT: EDT: EDT: EDT: EDT:

cch323_prepare_preferred_codec_list: IPIPGW(36):final mask=1 cch323_peer_caps_ind_common:IPIPGW(36):starting 245 via tunnel cch323_h245_connection_sm: state = 0 event=1 ccb=631A4D68 cch323_h245_connection_sm: listen state=0 cch323_h245_start_cap_sm: IPIPGW(36): starting the cap/msd

EDT: cch323_send_generic_caps: IPIPGW: audiomask raw =0x1.


DB-2410

May 2008


Aug 8 15:24:30.678 EDT: cch323_set_pref_codec_list:IPIPGW(36):first preferred codec(bytes)=21(0)

The following line shows the outbound leg forwarding the TCS over H.225 tunnel (starting H.245 via tunnel): Aug 8 15:24:30.678 EDT: cch323_send_generic_caps: IPIPGW:[trans]audio mask after operation=0x1.

The following lines show master-slave determination events passing from inbound to outbound and vice versa: Aug 8 Aug 8 Aug 8 Aug 8 Aug 8 Aug 8 Aug 8 Aug 8 Aug 8 leg=1

15:24:30.678 15:24:30.678 15:24:30.678 15:24:30.678 15:24:30.678 15:24:30.678 15:24:30.678 15:24:30.678 15:24:30.678

EDT: EDT: EDT: EDT: EDT: EDT: EDT: EDT: EDT:

cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MSD cch323_h245_connection_sm: state = 0 event=5 ccb=63C18580 cch323_h245_connection_sm: listen state=0 cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MS_IND cch323_h245_connection_sm: state = 2 event=5 ccb=631A4D68 cch323_h245_connection_sm: listen state=0 cch323_h245_cap_ind: IPIPGW(36): masks au=0x1 data=0xC uinp=0x32. cch323_run_h245_cap_in_sm:IPIPGW(36): got incoming CAPSET msg. cch323_do_transparent_cap_ind: IPIPGW(36):mask sent to other

The following lines show the outbound leg forwarding the TCS to the other leg and waiting for its response (TCSACK or TCSREJ): Aug 8 15:24:30.678 EDT: cch323_run_h245_cap_in_sm:IPIPGW(36):suppressTCS: our TCS will be sent based on peer. Aug 8 15:24:30.678 EDT: cch323_h245_cap_notify:IPIPGW(36):not xmiting CAPSACK: wait for peer to ack. Aug 8 15:24:30.678 EDT: cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MSD Aug 8 15:24:30.678 EDT: cch323_caps_ind: IPIPGW(35):setting the mask to new : current mask=0x4FFFF new mask=0x1. Aug 8 15:24:30.682 EDT: cch323_caps_ind: IPIPGW(35): ExtendedCapsPresent Aug 8 15:24:30.682 caps struct Aug 8 15:24:30.682 dtmf-caps from caps Aug 8 15:24:30.682 caps:21:1:FFFFFFFF Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 machine. Aug 8 15:24:30.682 Aug 8 15:24:30.682 codec(bytes)=21(0)

EDT: cch323_set_dtmf_relay_mask: IPIPGW(35): extract dtmf-caps from EDT: cch323_set_dtmf_relay_mask: IPIPGW(35): After extracting structccb->user_caps.user_input_bit_mask[0x1C] EDT: cch323_prepare_preferred_codec_list: IPIPGW(35):munging EDT: EDT: EDT: EDT: EDT:

cch323_prepare_preferred_codec_list: IPIPGW(35):final mask=1 cch323_peer_caps_ind_common:IPIPGW(35):starting 245 via tunnel cch323_h245_connection_sm: state = 0 event=1 ccb=63C18580 cch323_h245_connection_sm: listen state=0 cch323_h245_start_cap_sm: IPIPGW(35): starting the cap/msd

EDT: cch323_send_generic_caps: IPIPGW: audiomask raw =0x1. EDT: cch323_set_pref_codec_list:IPIPGW(35):first preferred

The following line shows the inbound call leg sending the TCS to the calling party: Aug 8 15:24:30.682 operation=0x1. Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 leg.

EDT: cch323_send_generic_caps: IPIPGW:[trans]audio mask after EDT: EDT: EDT: EDT: EDT: EDT: EDT: EDT:

cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MSD cch323_h245_connection_sm: state = 2 event=5 ccb=631A4D68 cch323_h245_connection_sm: listen state=0 cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MS_IND cch323_h245_connection_sm: state = 2 event=5 ccb=631A4D68 cch323_h245_connection_sm: listen state=0 cch323_run_h245_cap_out_sm: IPIPGW(36): got caps ack. cch323_run_h245_cap_out_sm:IPIPGW(36): sending caps ack to other


DB-2411


Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 state mc. Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug 8 15:24:30.682 Aug Aug Aug

EDT: Function: cch323_do_caps_ack Line: 1116 EDT: cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MSD EDT: cch323_peer_caps_ack: IPIPGW(35):sending caps resp event to CAP EDT: EDT: EDT: EDT:

cch323_h245_connection_sm: state = 2 event=5 ccb=631A4D68 cch323_h245_connection_sm: listen state=0 cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MS_CFM cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MS_DET_RSP

8 15:24:30.686 EDT: cch323_h245_connection_sm: state = 2 event=5 ccb=63C18580 8 15:24:30.686 EDT: cch323_h245_connection_sm: listen state=0 8 15:24:30.686 EDT: cch323_run_h245_cap_out_sm: IPIPGW(35): got caps ack.

The following line shows the inbound leg informing the outbound leg of the TCSACK: Aug 8 15:24:30.686 leg. Aug 8 15:24:30.686 Aug 8 15:24:30.686 state mc. Aug 8 15:24:30.686 Aug 8 15:24:30.686

EDT: cch323_run_h245_cap_out_sm:IPIPGW(35): sending caps ack to other EDT: Function: cch323_do_caps_ack Line: 1116 EDT: cch323_peer_caps_ack: IPIPGW(36):sending caps resp event to CAP EDT: cch323_h245_connection_sm: state = 2 event=5 ccb=63C18580 EDT: cch323_h245_connection_sm: listen state=0

The following lines show that master-slave determination procedures are completed on both call legs: Aug Aug

8 15:24:30.686 EDT: cch323_run_passthru_msd: IPIPGW(35):event = H245_EVENT_MS_CFM 8 15:24:30.686 EDT: cch323_run_passthru_msd: IPIPGW(36):event = H245_EVENT_MS_DET_RSP


DB-2412

May 2008

Debug Commands debug voip ivr

debug voip ivr Note

The debug voip ivr command is replaced by the debug voip application command. See the debug voip application command for more information.


DB-2413

Debug Commands debug voip ivr all

debug voip ivr all Note

The debug voip ivr all command is replaced by the debug voip application all command. See the debug voip application all command for more information.


DB-2414

May 2008

Debug Commands debug voip ivr applib

debug voip ivr applib Note

The debug voip ivr applib command is replaced by the debug voip application core command. See the debug voip application core command for more information.


DB-2415

Debug Commands debug voip ivr callsetup

debug voip ivr callsetup Note

The debug voip ivr callset command is replaced by the debug voip application callset command. See the debug voip application callset command for more information.


DB-2416

May 2008

Debug Commands debug voip ivr digitcollect

debug voip ivr digitcollect Note

The debug voip ivr digitcollect command is replaced by the debug voip application digitcollect command. See the debug voip application digitcollect command for more information.


DB-2417

Debug Commands debug voip ivr dynamic

debug voip ivr dynamic Note

The debug voip ivr dynamic command is replaced by the debug voip application media state command. See the debug voip application media state command for more information.


DB-2418

May 2008

Debug Commands debug voip ivr error

debug voip ivr error Note

The debug voip ivr error command is replaced by the debug voip application error command. See the debug voip application error command for more information.


DB-2419

Debug Commands debug voip ivr redirect

debug voip ivr redirect Note

The debug voip ivr redirect command is replaced by the debug voip application redirect command. See the debug voip application redirect command for more information.


DB-2420

May 2008

Debug Commands debug voip ivr script

debug voip ivr script Note

The debug voip ivr script command is replaced by the debug voip application script command. See the debug voip application script command for more information.


DB-2421

Debug Commands debug voip ivr settlement

debug voip ivr settlement Note

The debug voip ivr settlement command is replaced by the debug voip application settlement command. See the debug voip application settlement command for more information.


DB-2422

May 2008

Debug Commands debug voip ivr states

debug voip ivr states Note

The debug voip ivr states command is replaced by the debug voip application media state command. See the debug voip application media state command for more information.


DB-2423

Debug Commands debug voip ivr supplementary-service

debug voip ivr supplementary-service Note

The debug voip ivr supplementary-service command is replaced by the debug voip application supplementary-service command. See the debug voip application supplementary-service command for more information.


DB-2424

May 2008

Debug Commands debug voip ivr tclcommands

debug voip ivr tclcommands Note

The debug voip ivr tclcommands command is replaced by the debug voip application tclcommands command. See the debug voip application tclcommands command for more information.


DB-2425

Debug Commands debug voip profile fax

debug voip profile fax To enable a set of debug commands for fax applications, use the debug voip profile fax command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip profile fax [mail | relay [ application | signaling]] no debug voip profile fax

Syntax Description

mail

Enables the following set of debugs for an onramp or offramp fax mail call: •

debug csm voice

•

debug fax dmsp all

•

debug fax fmsp all

•

debug fax foip all

•

debug fax mmoip aaa all

•

debug fax mspi all

•

debug fax mta all

•

debug isdn q931

•

debug voip application all

•

debug voip application vxml all

•

debug voip ccapi all

•

debug voip dsm all

•

debug voip dspapi all

•

debug voip hpi all

•

debug voip ivr all

•

debug voip vtsp all


DB-2426

May 2008


The following debug commands are enabled for access servers with MICA modem cards: •

debug fax fmsp all

•

debug fax mmoip aaa

•

debug fax mta all

•

debug isdn q931

•


•


•


•

debug voip dsm all

•


•

debug voip hpi all

•

debug voip ivr all

•

debug voip vtsp all

The following debug options are enabled for access servers with universal port dial feature cards: •

debug fax dmsp all

•

debug fax fmsp all

•

debug fax foip all

•

debug fax mspi all

•


•

debug voip ivr all

relay

Enables the debug fax relay t30 all-level-1 and the sets specified by either the application or signaling keyword.

application

Enables the following set of debugs for fax relay applications: •


•


•


•

debug voip dialpeer all

•

debug voip ivr all


DB-2427


signaling

Defaults


Command Modes

Privileged EXEC

Enables the following set of debugs for fax relay signaling: •

debug cch323 all

•

debug ccsip error

•


•

debug cdapi detail

•

debug cdapi events

•

debug csm voice

•

debug gtd error

•

debug gtd events

•

debug h225 asn1

•

debug h225 events

•

debug h225 q931

•

debug h245 events

•

debug h245 asn1

•

debug isdn q931

•

debug mgcp errors

•

debug mgcp events

•

debug mgcp media

•

debug mgcp packets

•

debug mgcp voipcac

•

debug rtpspi all

•


•

debug voip dsm all

•


•

debug voip hpi all

•

debug voip rawmsg

•

debug voip tsp all

•

debug voip vtsp all


DB-2428

May 2008


Command History

Usage Guidelines

Caution

Release

Modification

12.3(8)T


12.2SX


The debug voip profile fax command can be used to use a set of debug commands at one time. Because this command generates a large amount of messages, router performance can be affected.

The debug voip profile fax command generates debug messages from many VoIP components. The number of messages can impact the performance of your router. This command should only be used during low traffic periods.

Examples

Output has been omitted due to its large volume.

Related Commands

Command

Description

debug voip profile help

Displays the sets of commands supported by the debug voip profile commands.

debug voip profile modem

Enables a set of debug commands for modem applications.

debug voip profile voice

Enables a set of debug commands for voice.


DB-2429

Debug Commands debug voip profile help

debug voip profile help To display the sets of debug commands supported by the debug voip profile commands, use the debug voip profile help command in privileged EXEC mode. debug voip profile help

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Usage Guidelines

The debug voip profile help command displays the sets of debug commands supported by the debug voip profile commands. It does not display any debug output.

Examples

The following is sample output from the debug voip profile help command: Router# debug voip profile help "debug voip profile modem relay signaling" includes: debug csm voice debug isdn q931 debug cdapi detail debug cdapi events debug voip dspapi all debug voip hpi all debug voip vtsp all debug voip tsp all debug voip ccapi all debug cch323 all debug ccsip error debug ccsip messages debug mgcp errors debug mgcp events debug mgcp media debug mgcp packets debug mgcp voipcac debug voip dsm all "debug voip profile voice application" includes: debug voip dialpeer all debug voip ccapi all debug voip ivr all debug voip application all debug voip application vxml all


DB-2430

May 2008


"debug voip profile [ voice | modem pass-through ] signaling" includes: debug csm voice debug isdn q931 debug cdapi detail debug cdapi events debug h225 asn1 debug h225 events debug h225 q931 debug h245 events debug h245 asn1 debug voip dspapi all debug voip hpi all debug voip vtsp all debug voip tsp all debug voip ccapi all debug cch323 all debug rtpspi all debug ccsip error debug ccsip messages debug mgcp errors debug mgcp events debug mgcp media debug mgcp packets debug mgcp voipcac debug voip rawmsg debug gtd error debug gtd events debug voip dsm all "debug voip profile fax mail" includes: debug csm voice debug isdn q931 debug voip dspapi all debug voip hpi all debug voip vtsp all debug voip ccapi all debug voip ivr all debug voip application all debug voip application vxml all debug fmail client debug fmail server debug fax mta all debug fax receive all debug fax send all debug text-to-fax debug tiff reader debug tiff writer debug fax mmoip aaa debug voip dsm all "debug voip profile fax relay application" includes: debug voip dialpeer all debug voip ccapi all debug voip ivr all debug voip application all debug voip application vxml all "debug voip profile fax relay signaling" includes: debug csm voice debug isdn q931 debug cdapi detail debug cdapi events debug h225 asn1


DB-2431


debug debug debug debug debug debug debug debug debug debug debug debug debug debug debug debug debug debug debug debug debug

Related Commands

h225 events h225 q931 h245 events h245 asn1 voip dspapi all voip hpi all voip vtsp all voip tsp all voip ccapi all cch323 all rtpspi all ccsip error ccsip messages mgcp errors mgcp events mgcp media mgcp packets mgcp voipcac voip rawmsg gtd error gtd events

Command

Description

debug voip profile fax

Enables a set of debug commands for fax applications.






DB-2432

May 2008

Debug Commands debug voip profile modem

debug voip profile modem To enable a set of debug commands for modem applications, use the debug voip profile modem command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip profile modem [pass-through signaling | relay signaling] no debug voip profile modem

Syntax Description

pass-through signaling Enables the following set of debugs for modem pass-through signaling: •

debug cch323 all

•

debug ccsip error all

•


•

debug cdapi detail

•

debug cdapi events

•

debug csm voice

•

debug gtd error

•

debug gtd events

•

debug h225 asn1

•

debug h225 events

•

debug h225 q931

•

debug isdn q931

•

debug mgsp errors all

•

debug mgcp events

•

debug mgcp media

•

debug mgcp packets

•

debug mgcp voipcac

•

debug rtpspi all

•


•

debug voip dsm all

•

debug voip rawmsg

•

debug voip tsp all

•

debug voip vtsp all

•

debug vpm all


DB-2433


relay signaling

Enables the following set of debugs for modem relay signaling: •


•

debug voip vtsp all

•

debug cch323 all

•

debug ccsip error

•

debug ccsip messages all

•

debug mgcp all

•

debug mgcp events

•

debug mgcp media

•

debug mgcp packets

•

debug mgcp voipcac all

•

debug isdn q931

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Usage Guidelines

Caution

Examples

The debug voip profile modem command can be used to use a set of debug commands at one time. Because this command causes a large amount of messages to be generated, router performance can be affected.

The debug voip profile modem command generates debug messages from many VoIP components, which generates a large number of debug messages. The number of messages can affect the performance of your router. This command should only be used during low traffic periods.



DB-2434

May 2008


Related Commands

Command

Description








DB-2435

Debug Commands debug voip profile voice

debug voip profile voice To enable a set of debug commands for voice, use the debug voip profile voice command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip profile voice [application | signaling] no debug voip profile voice

Syntax Description

application

signaling

Enables the following set of debugs for voice applications: •

debug voip applib

•


•


•

debug voip ivr all

Enables the following set of debugs for voice signaling: •

debug cch323 all

•

debug ccsip error all

•


•

debug cdapi detail

•

debug cdapi events

•

debug csm voice

•

debug gtd error

•

debug gtd events

•

debug h225 asn1

•

debug h225 events

•

debug h225 q931

•

debug isdn q931

•

debug mgsp errors all

•

debug mgcp events

•

debug mgcp media

•

debug mgcp packets

•

debug mgcp voipcac

•

debug rtpspi all

•


•

debug voip dsm all

•

debug voip rawmsg

•

debug voip tsp all

•

debug voip vtsp all

•

debug vpm all


DB-2436

May 2008

Debug Commands debug voip profile voice

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Usage Guidelines

Caution

The debug voip profile voice command can be used to use a set of debug commands at one time. Because this command causes a large amount of messages to be generated, router performance can be affected.

The debug voip profile voice command generates debug messages from many VoIP components, which generates a large number of debug messages. The number of messages can impact the performance of your router. This command should only be used during low traffic periods.

Examples


Related Commands

Command

Description








DB-2437

Debug Commands debug voip rawmsg

debug voip rawmsg To display the raw message owner, length, and pointer, use the debug voip rawmsg command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip rawmsg [detail] no debug voip rawmsg [detail]

Syntax Description

detail

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

(Optional) Prints the contents of the raw message in hexadecimal.

Modification

12.0(6)T


12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300 and Cisco AS5800; and on the Cisco MC3810 multiservice access concentrators.

12.2SX


Usage Guidelines

We recommend that you log output from the debug voip rawmsg command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following is sample output from the debug voip rawmsg command: Router# debug voip rawmsg voip rawmsg debugging is on Router# *Mar 1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al loc from 1, Length 18 Body 638E0C5

These debug messages show that a raw message is allocated for this call. The pointer to the memory location for this raw message is 63075164. *Mar 1 01:16:25.155: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL OCATED: ptr is 63075164, owner is 1, length is 18, msg is 638E0C54, type is 0, p rotocol id is 0


DB-2438

May 2008


The call control API (CCAPI) gets a setup indicator. It has no information about the callid (-1) and GUID (xxxxxxxxxxxx). *Mar

1 01:16:25.159: //-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind:

*Mar 1 01:16:25.159: Raw Message MaMa is TSP owner is CCAPI, length is 77, ptr is 63075164, type is 0, protocol id is 2

The SSAPP at this stage knows about the CallEntry ID (30) but not about GUID (xxxxxxxxx) or the dial-peer (-1). *Mar 1 01:16:25.163: //30/xxxxxxxxxxxx/SSAPP:-1:-1/ssaCallSetupInd: *Mar 1 01:16:25.163: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr is 63075164, type is 0, protocol id is 2

The SSAPP learns about the GUID (34C457CD802F) and also learns the incoming dial peer (10002). *Mar 1 01:16:25.163: //30/34C457CD802F/SSAPP:10002:-1/ssaSetupPeer: *Mar 1 01:16:25.163: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr is 63075164, type is 0, protocol id is 2

The CCAPI gets the call proceeding for CallEntry ID 30. CCAPI still does not have a GUID (xxxxxxxxxxx). *Mar

1 01:16:25.163: //30/xxxxxxxxxxxx/CCAPI/ccCallProceeding:

A new raw message buffer is created and the previous one is released. *Mar 1 01:16:25.163: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al loc from 10, Length 77 Body 0 *Mar 1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL OCATED: ptr is 630751EC, owner is 10, length is 77, msg is 638E0F0C, type is 0, protocol id is 0 *Mar 1 01:16:25.167: //30/34C457CD802F/SSAPP:10002:-1/ssaSetupPeer: *Mar 1 01:16:25.167: ssaSetupPeer: Saved rawmsgpp 630751EC len 77 IAM, GCI,34c457cd14f911cc802f95f5fabb6b0f?)??p?34999 *Mar 1 01:16:25.167: //30/xxxxxxxxxxxx/CCAPI/ccCallSetupRequest: *Mar 1 01:16:25.167: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr is 63075164, type is 0, protocol id is 2 *Mar 1 01:16:25.167: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate: *Mar 1 01:16:25.167: Raw Message MaMa is TSP owner is SSAPP, length is 77, ptr is 63075164, type is 0, protocol id is 2

The SSAPP gets a message indicating the digits were passed along the VoIP call leg to the terminating gateway. The CallEntry ID is 30, GUID is 34C457CD802F and the incoming dial peer is 10002. *Mar

1 01:16:25.167: //30/34C457CD802F/SSAPP:10002:-1/ssaReportDigitsDone:

The old raw message 63075164 was freed. The new one is 630751EC. *Mar 1 01:16:25.179: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Router#Raw Message FREED: ptr is 63075164, owner is 3, length is 4D, msg is 638E 0DB0, type is 0, protocol id is 2

CCAPI got a call proceeding on the second call leg (31); it has no information about the GUID (xxxxxxxxx). *Mar

1 01:16:25.223: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_proceeding:

CCAPI got a call alert on the second call leg (31); still no information about the GUID (xxxxxxxxx). *Mar

1 01:16:25.227: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_alert:


DB-2439


The alert is sent to the first call leg (30), GUID 34C457CD802F. *Mar 1 01:16:25.227: //30/34C457CD802F/SSAPP:10002:-1/ssaAlert: *Mar 1 01:16:25.227: //30/xxxxxxxxxxxx/CCAPI/ccCallAlert: The call is answered at this point and the CCAPI gets a call connect for the second call leg (CallEntry ID is 31; GUID is xxxxxxxxx). *Mar

1 01:16:40.975: //31/xxxxxxxxxxxx/CCAPI/cc_api_call_connected:

The call connect is sent to the first call leg (30), GUID 34C457CD802F. *Mar *Mar

1 01:16:40.975: //30/34C457CD802F/SSAPP:10002:-1/ssaConnect: 1 01:16:40.975: //30/xxxxxxxxxxxx/CCAPI/ccCallConnect:

The current raw message (ptr 630751EC) is released; a new one will be proclaimed when needed. *Mar 1 01:16:40.975: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREE D: ptr is 630751EC, owner is 10, length is 4D, msg is 638E0F0C, type is 0, protocol id is 2

A new raw message (ptr 63075274) is proclaimed. *Mar 1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: VoIP Raw Msg Al loc from 1, Length 4 Body 638E1068 *Mar 1 01:17:04.007: //-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo: Raw Message ALL OCATED: ptr is 63075274, owner is 1, length is 4, msg is 638E1068, type is 0, protocol id is 0

The call terminates now. CCAPI detects a call disconnect from the first call leg (30) with no GUID (xxxxxxxxx). *Mar 1 01:17:04.007: //30/xxxxxxxxxxxx/CCAPI/cc_api_call_disconnected: *Mar 1 01:17:04.007: Raw Message MaMa is TSP owner is CCAPI, length is 4, ptr i s 63075274, type is 0, protocol id is 2

The disconnect is sent to the first call leg (30), GUID (34C457CD802F). *Mar 1 01:17:04.011: //30/34C457CD802F/SSAPP:10002:14/ssaDisconnected: *Mar 1 01:17:04.011: Raw Message MaMa is TSP owner is SSAPP, length is 4, ptr i s 63075274, type is 0, protocol id is 2

The CCAPI disconnects both call legs (incoming 30 and outgoing 31). *Mar 1 01:17:04.011: //30/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: *Mar 1 01:17:04.011: //31/xxxxxxxxxxxx/CCAPI/ccCallDisconnect: *Mar 1 01:17:04.011: Raw Message MaMa is TSP owner is SSAPP, length is 4, ptr i s 63075274, type is 0, protocol id is 2

The raw message is released. *Mar 1 01:17:04.015: //-1/xxxxxxxxxxxx/CCAPI/ccFreeRawMsgInfo: Raw Message FREE D: ptr is 63075274, owner is 3, length is 4, msg is 638E1068, type is 0, protocol id is 2

The following example shows output when you use the debug voip rawmsg detail command. This example shows that the CCAPI layer received an indication for call setup. The detailed raw message dumps the hex of the message. This output is used to track down data pointing to different variables within the software modules. Router# debug voip rawmsg detail *Mar 6 17:03:24.169://-1/xxxxxxxxxxxx/CCAPI/ccAllocRawMsgInfo:VoIP Raw Msg Al loc from 5, Length 0 Body 0 *Mar 6 17:03:24.173://-1/xxxxxxxxxxxx/CCAPI/cc_api_call_setup_ind: *Mar 6 17:03:24.173:Raw Message MaMa is CCAPI owner is CCAPI, length is 59, ptr is 63045C14, type is 0, protocol id is 18 *Mar 6 17:03:24.173:Raw Message is :1C 39 9E 01 00 03 67 74 64 00 00 00 2E 49


DB-2440

May 2008


41 4D 2C 0D 0A 47 43 49 2C 35 33 39 61 30 35 39 64 31 39 36 62 31 31 63 63 38 3 9 30 63 39 30 37 65 31 65 31 37 35 61 34 37 0D 0A 0D 0A

Related Commands

Command

Description

debug cdapi

Displays information about the call distributor application programming interface.

debug tsp


voice call debug



DB-2441

Debug Commands debug voip rtcp

debug voip rtcp To enable debugging for Real-Time Transport Control Protocol (RTCP) packets, use the debug voip rtcp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip rtcp {error | packet | session} no debug voip rtcp

Syntax Description

error

Prints out a trace for error cases.

packet

Provides debug output for RTCP packets.

session

Provides all session debug information.

Defaults

Debugging for RTCP packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)T


12.2(11)T

This command was implemented on the Cisco AS5300, Cisco AS5400, and Cisco AS5850.

12.2(15)T

This command was implemented on the Cisco 1751 and Cisco 1760.

12.2SX


Usage Guidelines

When used without a keyword, this command turns on debugging for all events. This command severely impacts performance; use with caution.

Examples

The following is sample output from the debug voip rtcp command: Router# debug voip rtcp 1w0d: voip_rtcp_create_session: callID=37, dstCallID=36 laddr=172.19.169.85, lp0 1w0d: voip_rtcp_get_cname: [email protected] 1w0d: voip_rtcp_send_event: event=EV_NEW 1w0d: voip_rtcp_new: rtcp_interval=1893 Router# 1w0d: voip_rtcp_send_event: event=EV_STATS 1w0d: voip_rtcp_stats_req: rtcp_interval=3448 1w0d: voip_rtcp_stats_req:delay=45 lost_packets=0 rtt=0 Router# 1w0d: recv: 1w0d: SR: ssrc=0x1272A94D sr_ntp_h=0xAF44E045 sr_ntp_l=0xA6CE39C sr_timestamp=02 1w0d: SDES: ssrc=0x1272A94D name=1 len=19 [email protected]


DB-2442

May 2008

Debug Commands debug voip rtcp

1w0d: rtcp_round_trip_delay: ssrc=0x1D86A955 Router# 1w0d: voip_rtcp_send_event: event=EV_STATS 1w0d: voip_rtcp_stats_req: rtcp_interval=6394 1w0d: voip_rtcp_stats_req:delay=40 lost_packets=0 rtt=0 1w0d: recv: 1w0d: SR: ssrc=0x1272A94D sr_ntp_h=0xAF44E047 sr_ntp_l=0xFFB007F6 sr_timestamp=6 1w0d: SDES: ssrc=0x1272A94D name=1 len=19 [email protected] 1w0d: rtcp_round_trip_delay: ssrc=0x1D86A955 Router# 1w0d: voip_rtcp_remove_ccb 1w0d: voip_rtcp_send_event: event=EV_DESTROY 1w0d: voip_rtcp_destroy_idle 1w0d: voip_rtcp_close_session 1w0d: Cleaning up sess=62F95F58, sp=19544, dp=17130


DB-2443

Debug Commands debug voip rtp

debug voip rtp To enable debugging for Real-Time Transport Protocol (RTP) named event packets, use the debug voip rtp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip rtp {error | session [conference | dtmf-relay | event | multicast | named-event [payload-type] | nse | text-relay] | packet [callid id-number packet-number | remote-ip ip-address remote-port port-number packet-number]} no debug voip rtp

Syntax Description

error

Prints out a trace for error cases.

session

Provides all session debug information. If used with a keyword, supplies more specific debug information according to the keywords used.

conference

(Optional) Provides debug information for conference packets.

dtmf-relay

(Optional) Provides debug information for dual-tone multifrequency (DTMF) packets.

event

(Optional) Enables VoIP RTP session generic event debugging trace.

multicast

(Optional) Provides debug information for multicast packets.

named-event

(Optional) Provides debug information for named telephony event (NTE) packets.

nse

(Optional) Provides debug information for named signaling events (NSEs).

text-relay

(Optional) Provides debug information for text-relay packets.

packet

Enables VoIP RTP packet debugging trace.

callid id-number packet-number

(Optional) Provides debug information for a specific call ID number (obtained by using the show voip rtp connections command). The packet-number argument specifies the number of packets to trace so that the display is not flooded.

remote-ip ip-address remote-port port-number packet-number

(Optional) Provides debug information for a remote IP address and RTP port number. The packet-number argument specifies the number of packets to trace so that the display is not flooded.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(2)XB


12.2(8)T


12.4(4)XC

This command was implemented on the Cisco AS5300, Cisco AS5400, and Cisco AS5850.

12.2(15)T

This command was implemented on the Cisco 1751 and Cisco 1760.


DB-2444

May 2008

Debug Commands debug voip rtp

Release

Modification

12.4(6)T

The text-relay keyword was added.

12.2SX


Usage Guidelines

This command severely impacts performance and should be used only for single-call debug capture.

Examples

The following example shows debugging output for the debug voip rtp session named-event command. The example is for a gateway that sends digits 1, 2, 3, then receives digits 9,8,7. The payload type, event ID, and additional packet payload are shown in each log. The first three packets indicate the start of the tone (initial packet and two redundant). The last three packets indicate the end of the tone (initial packet and two redundant). The packets in between are refresh packets that are sent every 50 milliseconds (without redundancy). Router# debug voip rtp session named-event 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:29: 00:09:30: 00:09:30: 00:09:30: 00:09:30: 00:09:30: 00:09:30: 00:09:30: 00:09:31: 00:09:31: 00:09:31: 00:09:31: 00:09:31: 00:09:31: 00:09:31: 00:09:31: 00:09:31: 00:09:31: 00:09:31:

>> >> >> >> >> >> >> >> >> >> >>

Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99 Pt:99

Evt:1 Evt:1 Evt:1 Evt:1 Evt:1 Evt:1 Evt:1 Evt:1 Evt:1 Evt:2 Evt:2 Evt:2 Evt:2 Evt:2 Evt:2 Evt:2 Evt:2 Evt:2 Evt:3 Evt:3 Evt:3 Evt:3 Evt:3 Evt:3 Evt:3 Evt:3 Evt:3 Evt:3 Evt:9 Evt:9 Evt:9 Evt:9 Evt:9 Evt:9 Evt:9 Evt:9 Evt:9 Evt:9 Evt:8

Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:83 Pkt:83 Pkt:83 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:83 Pkt:83 Pkt:83 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:03 Pkt:83 Pkt:83 Pkt:83 Pkt:02 Pkt:02 Pkt:02 Pkt:02 Pkt:02 Pkt:02 Pkt:02 Pkt:82 Pkt:82 Pkt:82 Pkt:02

00 00 00 01 03 04 04 04 04 00 00 00 01 03 04 05 05 05 00 00 00 01 03 04 06 06 06 06 00 00 00 01 03 04 06 06 06 06 00

00 00 00 90 20 B0 C8 C8 C8 00 00 00 90 20 B0 18 18 18 00 00 00 90 20 B0 40 80 80 80 00 00 00 90 20 B0 40 58 58 58 00

success 200 101 http://www.myauthority.com 5552222 1.14.115.51


DB-2459

Debug Commands debug voip settlement network

PD94bWwgdmVyc2lvbj0xLjA/PjxNZXNzYWdlIG1lc3NhZ2VJZD0iMSIgcmFuZG9tPSIxODM0OSI+PFRva2VuSW5mbz 48U291cmNlSW5mbyB0eXBlPSJlMTY0Ij41NTUxMTExPC9Tb3VyY2VJbmZvPjxEZXN0aW5hdGlvbkluZm8gdHlwZT0i ZTE2NCI+NTU1MjIyMjwvRGVzdGluYXRpb25JbmZvPjxDYWxsSWQ+PCFbQ0RBVEFbMV1dPjwvQ2FsbElkPjxWYWxpZE FmdGVyPjE5OTgtMTItMDhUMjA6MDQ6MFo8L1ZhbGlkQWZ0ZXI+PFZhbGlkVW50aWw+MTk5OS0xMi0zMVQyMzo1OTo1 OVo8L1ZhbGlkVW50aWw+PFRyYW5zYWN0aW9uSWQ+MTAxPC9UcmFuc2FjdGlvbklkPjxVc2FnZURldGFpbD48QW1vdW 50PjE0NDAwPC9BbW91bnQ+PEluY3JlbWVudD4xPC9JbmNyZW1lbnQ+PFNlcnZpY2UvPjxVbml0PnM8L1VuaXQ+PC9V c2FnZURldGFpbD48L1Rva2VuSW5mbz48L01lc3NhZ2U+ 60 1 s 1999-01-20T01:59:54Z 1999-01-20T02:09:54Z 1000 1 --bar Content-Type:application/pkcs7-signature Content-Length:31 This is your response signature --bar--


DB-2460

May 2008

Debug Commands debug voip settlement security

debug voip settlement security To show all the tracing related to security, such as Secure Socket Layer (SSL) or Secure Multipurpose Internet Mail Extensions (S/MIME), enter the debug voip settlement security command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip settlement security no debug voip settlement security

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1


12.2SX


Examples

Not available because of security issues.


DB-2461

Debug Commands debug voip settlement ssl

debug voip settlement ssl To display information about the Secure Socket Layer (SSL) connection, use the debug voip settlement ssl command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip settlement ssl no debug voip settlement ssl

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Usage Guidelines

For complete information about the SSL connection, use the debug voip settlement ssl command if you see one of the following errors generated from the debug voip settlement error command. 14400:OSP 14410:OSP 14420:OSP 14430:OSP 14440:OSP 14450:OSP 14460:OSP 14470:OSP 14480:OSP 14490:OSP 14495:OSP 14496:OSP 14497:OSP 14498:OSP 14499:OSP

Examples

SSL SSL SSL SSL SSL SSL SSL SSL SSL SSL SSL SSL SSL SSL SSL

error error error error error error error error error error error error error error error

-

failed to allocate memory. failed to initialize the context. failed to retrieve the version. failed to initialize the session. failed to attach the socket. handshake failed. failed to close SSL. failed to read from SSL. failed to write to SSL. could not get certificate. no root certificate found. failed to set the private key. failed to parse the private key. failed to add certificates. failed to add DN.

The following example shows the debug output when the SSL is making a good connection to the Open Settlement Protocol server: *May 15 11:53:42.871:OSP: *May 15 11:53:42.871:OSPPSSLConnect:****** SSL HANDSHAKE SUCCEED !!**** retry=2

When the SSL connection is closed, the following message appears:


DB-2462

May 2008

Debug Commands debug voip settlement ssl

*May 15 11:57:42.541:OSP:osp_ssl_close:OSPPSSLClose succeed

The following are possible output trace messages: osp_ssl_callback_add_session:session not found, add it. osp_ssl_callback_add_session:session found, but not equal, delete old one osp_ssl_callback_add_session:Copy new session data osp_ssl_callback_add_session:session found and equal. no add osp_ssl_callback_get_session:No Session exist osp_ssl_callback_get_session:Session found, copy to sslref length=756 osp_ssl_callback_delete_session:session not found

These messages do not indicate an error but indicate the result of the operation. To display actual error messages, enter the debug voip settlement error command.


DB-2463

Debug Commands debug voip settlement transaction

debug voip settlement transaction To see all the attributes of the transactions on the settlement gateway, use the debug voip settlement transaction in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip settlement transaction no debug voip settlement transaction

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(4)XH1


12.2SX


Examples

The following is sample output from the originating gateway: 00:44:54:OSP:OSPPTransactionNew:trans=0, err=0 00:44:54:OSP:osp_authorize:authorizing trans=0, err=0 router> 00:45:05:OSP:stop_settlement_ccapi_accounting:send report for callid=7, trans =0, calling=5710868, called=15125551212, curr_Dest=1 00:45:05:OSP:OSPPTransactionDelete:deleting trans=0

The following is sample output from the terminating gateway: 00:44:40:OSP:OSPPTransactionNew:trans=0, err=0 00:44:40:OSP:osp_validate:validated trans=0, error=0, authorised=1


DB-2464

May 2008

Debug Commands debug voip tsp

debug voip tsp To display information about the telephony service provider (TSP), use the debug voip tsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip tsp [all | default | error [call [informational] | software [informational]] | event | function | individual range | inout | rose] no debug voip tsp

Syntax Description

all

(Optional) Displays all TSP debugging messages.

default

(Optional) Displays TSP inout, error, and event debugging messages. This option also runs if no keywords are added.

error

(Optional) Displays TSP error messages.

call

(Optional) Displays TSP call-related debugs not generated by other TSP debug options.

informational


software


event

(Optional) Displays TSP events.

function

(Optional) Displays TSP functions.

individual

(Optional) Enables individual TSP debugs.

range


inout

(Optional) Displays TSP function entry/exit debugs.

rose

(Optional) Enables the remote operations service element. This debug displays information about ISDN-related elements.

Table 373

TSP Individual Debug Values

Value

TSP Debug Function

1

INDIVIDUAL_TSP_DEBUG_TDM_HAIRPIN_CONNECT_001

2

INDIVIDUAL_TSP_DEBUG_TDM_HAIRPIN_DISCONNECT_002

3

INDIVIDUAL_TSP_DEBUG_CCRAWMSG_ENCAP_003

4

INDIVIDUAL_TSP_DEBUG_CDAPI_FORM_MSG_BASIC_SS_INFO_004

5

INDIVIDUAL_TSP_DEBUG_CDAPI_FORM_MSG_005

6

INDIVIDUAL_TSP_DEBUG_CDAPI_FORM_MSG_006

7

INDIVIDUAL_TSP_DEBUG_CDAPI_SEND_MSG_007

8

INDIVIDUAL_TSP_DEBUG_CDAPI_SEND_MSG_008

9

INDIVIDUAL_TSP_DEBUG_CDAPI_SEND_INFO_MSG_009

10

INDIVIDUAL_TSP_DEBUG_ALLOC_CDB_010

11

INDIVIDUAL_TSP_DEBUG_DEALLOC_CDB_011


DB-2465


Table 373

TSP Individual Debug Values (continued)

Value

TSP Debug Function

12

INDIVIDUAL_TSP_DEBUG_CONNECT_IND_012

13

INDIVIDUAL_TSP_DEBUG_CONNECT_IND_EXIT_013

14


15


16


17


18

INDIVIDUAL_TSP_DEBUG_CDAPI_SETUP_ACK_018

19

INDIVIDUAL_TSP_DEBUG_CDAPI_PROCEEDING_019

20

INDIVIDUAL_TSP_DEBUG_CDAPI_ALERT_020

21

INDIVIDUAL_TSP_DEBUG_CDAPI_CONNECT_021

22

INDIVIDUAL_TSP_DEBUG_CDAPI_INFO_022

23

INDIVIDUAL_TSP_DEBUG_CDAPI_PROGRESS_023

24

INDIVIDUAL_TSP_DEBUG_CDAPI_FACILITY_024

25

INDIVIDUAL_TSP_DEBUG_CDAPI_FACILITY_025

26

INDIVIDUAL_TSP_DEBUG_CDAPI_PRE_CONN_DISC_REQ_026

27

INDIVIDUAL_TSP_DEBUG_CDAPI_DISC_PROG_IND_027

28

INDIVIDUAL_TSP_DEBUG_CDAPI_DISCONNECT_REQ_028

29

INDIVIDUAL_TSP_DEBUG_CDAPI_DISCONNECT_REQ_029

30

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_SS_RESP_030

31

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_INFO_IND_031

32

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_PROCEEDING_032

33

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_ALERT_033

34

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_ALERT_EXIT_034

35

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_ALERT_EXIT_035

36

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_PROGRESS_036

37

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_INFO_037

38

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_CONNECT_038

39

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_CONNECT_CONF_039

40

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_DISC_PROG_IND_040

41

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_PROG_IND_PROGRESS_041

42

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RELEASE_IND_042

43

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RELEASE_IND_EXIT_043

44

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RELEASE_COMP_044

45

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RELEASE_COMP_CLEAR_045

46

INDIVIDUAL_TSP_DEBUG_SETUP_REQ_EXIT_046

47



DB-2466

May 2008


Table 373

TSP Individual Debug Values (continued)

Value

TSP Debug Function

48


49

INDIVIDUAL_TSP_DEBUG_TSP_SET_TRANSFER_INFO_049

50

INDIVIDUAL_TSP_DEBUG_TSP_CALL_VOICE_CUT_THROUGH_050

51


52


53


54

INDIVIDUAL_TSP_DEBUG_TSP_MAIN_054

55

INDIVIDUAL_TSP_DEBUG_DO_GLOBAL_END_TO_END_DISC_055

56

INDIVIDUAL_TSP_DEBUG_TSP_CDAPI_MSG_DUMP_056

57

INDIVIDUAL_TSP_DEBUG_TSP_COT_TIMER_START_057

58

INDIVIDUAL_TSP_DEBUG_TSP_COT_TIMER_STOP_058

59

INDIVIDUAL_TSP_DEBUG_TSP_COT_RESULT_059

60

INDIVIDUAL_TSP_DEBUG_TSP_COT_DONE_060

61

INDIVIDUAL_TSP_DEBUG_TSP_COT_TIMEOUT_061

62

INDIVIDUAL_TSP_DEBUG_TSP_COT_REQ_062

63

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_COT_SETUP_ACK_063

64

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RCV_COT_MSG_064

65

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RCV_COT_MSG_065

66

INDIVIDUAL_TSP_DEBUG_TSP_CDAPI_PUT_CAUSE_IE_066

67

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_SETUP_ACK_067

68

INDIVIDUAL_TSP_DEBUG_CDAPI_TSP_RCV_MSG_068

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug tsp command.

12.2SX



DB-2467


Examples

The following is sample output from the debug voip tsp command: Router# debug voip tsp Apr

4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_voice_call_check:Query#9 Overlap=FALSE, Called Number=222, Calling Number=4321

*Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 Peer Search Type=Voice *Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 Matched Incoming Dialpeer With=Port, Peer=299 *Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 DID=TRUE *Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 Incoming Dial-peer=SUCCESS *Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_check_call_type:Query#9 Matched Outgoing Dialpeer=221 *Apr 4 2002 14:04:11.034 UTC://-1/xxxxxxxxxxxx/TSP:():-1/FFFF/tsp_voice_call_check:Query#9 Call Type=VOICE, Result=ACCEPT


debug voip tsp dialpeer Field Descriptions

Field

Description

//-1/xxxxxxxxxxxx/TSP:():-1/FFFF/ tsp_voice_call_check:

The format of this message is //callid/GUID/DMSP/function name:

Called Number=222, Calling Number=4321

•


•

GUID is xxxxxxxxxxxx. This indicates that the call has not been specified.

•

TSP:():-1/FFFF is the module name and module-specific parameters.

•

The tsp_voice_call_check field shows that the accounting for an onramp fax is active.

Shows the calling and called numbers for the call.

Matched Incoming Dialpeer With=Port, Shows that the incoming dial peer was matched and Peer=299 identifies the dial peer.

Related Commands

DID=TRUE

Indicates that the call is a direct-inward dial (DID) call.

Matched Outgoing Dialpeer=221

Shows that the outgoing dial peer was matched and identifies the dial peer.

Command

Description

debug track


debug voip rawmsg



DB-2468

May 2008

Debug Commands debug voip vtsp

debug voip vtsp To display information about the voice telephony service provider (VTSP), use the debug voip vtsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip vtsp [all | default | error | event | function | individual range | inout | session | tone] no debug voip vtsp

Syntax Description

all

(Optional) Displays all VTSP debugging messages.

default

(Optional) Displays VTSP inout, error, and event debugging messages. This option also runs if no keywords are added.

error

(Optional) Displays VTSP error messages.

event

(Optional) Displays VTSP events.

function

(Optional) Displays VTSP functions.

individual

(Optional) Enables individual VTSP debugs.

range


inout

(Optional) Displays VTSP function entry/exit debugs.

session

(Optional) Traces how the router interacts with the digital signal processor (DSP) based on the signaling indications from the signaling stack and requests from the application.

tone

(Optional) Displays the VTSP messages showing the types of tones generated by the Voice over IP (VoIP) gateway.

Table 375

VTSP Individual Debug Values

Value

VTSP Debug Function

1

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_PEND_DEFER_001

2

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_WAIT_PEND_SUCCESS_002

3

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_WAIT_PEND_FAIL_003

4

INDIVIDUAL_VTSP_DEBUG_TDM_HPM_COMPLETE_004

5

INDIVIDUAL_VTSP_DEBUG_TDM_HPM_COMPLETE_EXIT_005

6

INDIVIDUAL_VTSP_DEBUG_TDM_HPM_CHECK_006

7

INDIVIDUAL_VTSP_DEBUG_TDM_HPM_CHECK_EXIT_007

8

INDIVIDUAL_VTSP_DEBUG_GENERATE_DISC_008

9

INDIVIDUAL_VTSP_DEBUG_GENERATE_DISC_EXIT_009

10

INDIVIDUAL_VTSP_DEBUG_SETUP_IND_ACK_010

11

INDIVIDUAL_VTSP_DEBUG_SETUP_IND_ACK_EXIT_011

12

INDIVIDUAL_VTSP_DEBUG_PROCEEDING_012

13

INDIVIDUAL_VTSP_DEBUG_PRE_CON_DISCONNECT_013

14

INDIVIDUAL_VTSP_DEBUG_PRE_CON_DISCONNECT_EXIT_014


DB-2469


Table 375

VTSP Individual Debug Values (continued)

Value

VTSP Debug Function

15

INDIVIDUAL_VTSP_DEBUG_SET_DIGIT_TIMEOUTS_015

16

INDIVIDUAL_VTSP_DEBUG_CONNECT_016

17

INDIVIDUAL_VTSP_DEBUG_LOOPBACK_017

18

INDIVIDUAL_VTSP_DEBUG_RING_NOAN_TIMER_018

19

INDIVIDUAL_VTSP_DEBUG_ALERT_CONNECT_019

20

INDIVIDUAL_VTSP_DEBUG_PRE_CON_DISC_REL_EXIT_020

21

INDIVIDUAL_VTSP_DEBUG_HOST_DISC_CLEANUP_021

22

INDIVIDUAL_VTSP_DEBUG_HOST_DISC_CLEANUP_EXIT_022

23

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_023

24

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_EXIT_024

25

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_EXIT_025

26

INDIVIDUAL_VTSP_DEBUG_CONNECT_DIAL_026

27

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_DIAL_027

28

INDIVIDUAL_VTSP_DEBUG_PRE_DISC_CAUSE_028

29

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_CONNECT_029

30

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_PEND_FAIL_030

31

INDIVIDUAL_VTSP_DEBUG_SETUP_REQ_DISC_031

32

INDIVIDUAL_VTSP_DEBUG_RELEASE_TIMEOUT_032

33

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_PROCEEDING_EXIT_033

34

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_PROCEEDING_EXIT_034

35

INDIVIDUAL_VTSP_DEBUG_PEND_RELEASE_IND_035

36

INDIVIDUAL_VTSP_DEBUG_PEND_RELEASE_IND_EXIT_036

37

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_NO_DSP_CHAN_037

38

INDIVIDUAL_VTSP_DEBUG_DISCONNECT_NO_DSP_CHAN_EXIT_038

39

INDIVIDUAL_VTSP_DEBUG_CALL_FEATURE_IND_039

40

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_PROGRESS_040

41

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_ALERT_041

42

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_ALERT_EXIT_042

43

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_FIRST_PROGRESS_043

44

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_FIRST_PROGRESS_EXIT_044

45

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_FIRST_PROGRESS_EXIT_045

46

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_PROG_PROCEEDING_046

47

INDIVIDUAL_VTSP_DEBUG_PROCEEDING_R2_PEND_DIAL_047

48

INDIVIDUAL_VTSP_DEBUG_ALERT_R2_PEND_DIAL_048

49

INDIVIDUAL_VTSP_DEBUG_CONN_R2_PEND_DIAL_049

50

INDIVIDUAL_VTSP_DEBUG_SETUP_R2_PEND_DIAL_050


DB-2470

May 2008


Table 375


Value

VTSP Debug Function

51

INDIVIDUAL_VTSP_DEBUG_R2_PEND_DIAL_ALL_051

52

INDIVIDUAL_VTSP_DEBUG_INFO_IND_052

53

INDIVIDUAL_VTSP_DEBUG_ALERT_053

54

INDIVIDUAL_VTSP_DEBUG_ALERT_EXIT_054

55

INDIVIDUAL_VTSP_DEBUG_PROGRESS_055

56

INDIVIDUAL_VTSP_DEBUG_DISC_PROG_IND_056

57

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_DISC_PI_IND_057

58

INDIVIDUAL_VTSP_DEBUG_INFO_058

59

INDIVIDUAL_VTSP_DEBUG_FEATURE_059

60

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_ALERT_NO_TIMEOUT_060

61

INDIVIDUAL_VTSP_DEBUG_SETUP_PEND_ALERT_NO_TIMEOUT_EXIT_061

62

INDIVIDUAL_VTSP_DEBUG_CALL_FEATURE_ENABLE_062

63

INDIVIDUAL_VTSP_DEBUG_XCCSM_COT_TEST_DONE_063

64

INDIVIDUAL_VTSP_DEBUG_XCCSM_COT_TEST_TIMEOUT_064

65

INDIVIDUAL_VTSP_DEBUG_XCCSM_COT_TEST_065

66

INDIVIDUAL_VTSP_DEBUG_CALL_FEATURE_066

67

INDIVIDUAL_VTSP_DEBUG_TCSM_COT_TEST_DONE_067

68

INDIVIDUAL_VTSP_DEBUG_TCSM_COT_TEST_TIMEOUT_068

69

INDIVIDUAL_VTSP_DEBUG_TCSM_ACT_COT_TEST_069

70

INDIVIDUAL_VTSP_DEBUG_PLAY_BUSY_TIMER_START_070

71

INDIVIDUAL_VTSP_DEBUG_PLAY_BUSY_TIMER_STOP_071

72

INDIVIDUAL_VTSP_DEBUG_RING_NOAN_TIMER_START_072

73

INDIVIDUAL_VTSP_DEBUG_RING_NOAN_TIMER_STOP_073

74

INDIVIDUAL_VTSP_DEBUG_VTSP_TIMER_074

75

INDIVIDUAL_VTSP_DEBUG_VTSP_TIMER_STOP_075

76

INDIVIDUAL_VTSP_DEBUG_VTSP_ALLOCATE_CDB_076

77

INDIVIDUAL_VTSP_DEBUG_VTSP_DO_CALL_SETUP_IND_077

78

INDIVIDUAL_VTSP_DEBUG_VTSP_DO_CALL_SETUP_IND_EXIT_078

79

INDIVIDUAL_VTSP_DEBUG_VTSP_REQUEST_CALL_079

80

INDIVIDUAL_VTSP_DEBUG_VTSP_REQUEST_CALL_EXIT_080

81

INDIVIDUAL_VTSP_DEBUG_VTSP_REALLOC_CDB_081

82

INDIVIDUAL_VTSP_DEBUG_VTSP_OG_CALL_REQ_EXIT_082

83

INDIVIDUAL_VTSP_DEBUG_VTSP_FREE_CDB_083

84

INDIVIDUAL_VTSP_DEBUG_TGRM_DISC_REL_084

85

INDIVIDUAL_VTSP_DEBUG_VTSP_CC_CALL_DISCONNECTED_085

86

INDIVIDUAL_VTSP_DEBUG_SIGO_BDROP_086


DB-2471


Table 375


Value

VTSP Debug Function

87

INDIVIDUAL_VTSP_DEBUG_SIGO_PRE_CON_DISCONNECT_087

88

INDIVIDUAL_VTSP_DEBUG_SIGO_PROCEEDING_088

89

INDIVIDUAL_VTSP_DEBUG_SIGO_GENERATE_DISC_089

90

INDIVIDUAL_VTSP_DEBUG_SIGO_ALERT_090

91

INDIVIDUAL_VTSP_DEBUG_SIGO_ALERT_CONNECT_091

92

INDIVIDUAL_VTSP_DEBUG_SIGO_SETUP_PEND_CONNECT_092

93

INDIVIDUAL_VTSP_DEBUG_DO_SIGO_CALL_SETUP_REQ_093

94

INDIVIDUAL_VTSP_DEBUG_DO_SIGO_CALL_SETUP_REQ_SESSION_094

95

INDIVIDUAL_VTSP_DEBUG_DSM_MEDIA_EVENT_CB_095

96

INDIVIDUAL_VTSP_DEBUG_DSM_PEER_EVENT_CB_096

97

INDIVIDUAL_VTSP_DEBUG_DSM_FEATURE_NOTIFY_CB_097

98

INDIVIDUAL_VTSP_DEBUG_DSM_BRIDGE_CHECK_CB_098

99

INDIVIDUAL_VTSP_DEBUG_DSM_BRIDGE_STATUS_EXIT_099

100

INDIVIDUAL_VTSP_DEBUG_DSM_SET_FAX_FEAT_EXIT_100

101

INDIVIDUAL_VTSP_DEBUG_DS_DO_DIAL_101

102

INDIVIDUAL_VTSP_DEBUG_DS_DIALING_DEFAULT_102

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T

This command replaces the debug vtsp command.

12.3(14)T


12.2SX


Examples

The following examples show output for variations of the debug voip vtsp command: •

debug voip vtsp event on the Terminating Gateway, page 2473

•

debug voip vtsp function on the Originating Gateway, page 2473

•

debug voip vtsp inout on the Originating Gateway, page 2474

•

debug voip vtsp tone on the Originating Gateway, page 2476


DB-2472

May 2008


•

debug voip vtsp Displaying T.38 Fax Relay Statistics on the Originating Gateway, page 2476

For these examples, the topology shown in Figure 5 is used. Network Topology for debug voip vtsp Examples

T1 PRI

PSTN

FXS


VoIP network

V

103302

Figure 5


debug voip vtsp event on the Terminating Gateway Router# debug voip vtsp event voip vtsp event debugging is on *May 1 20:03:47.703: //-1/xxxxxxxxxxxx/VTSP:(4/0/0):-1:-1:-1/vtsp_process_event: [state:INVALID STATE MACHINE, event:E_CC_SETUP_REQ]

At the setup request, the CallEntry ID and GUID are set. The remainder of the output follows the progress of the call. *May 1 20:03:47.707: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_SETUP_REQUEST, event:E_TSP_PROCEEDING] *May 1 20:03:47.707: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_SETUP_REQ_PROC, event:E_TSP_PROGRESS] *May 1 20:03:49.955: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_SETUP_REQ_PROC, event:E_TSP_CONNECT] *May 1 20:03:49.959: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_CONNECT, event:E_CC_FEATURE] *May 1 20:04:14.851: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_CONNECT, event:E_CC_DISCONNECT] *May 1 20:04:14.855: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_WAIT_STATS, event:E_VTSP_DSM_STATS_COMPLETE] *May 1 20:04:15.759: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_WAIT_RELEASE, event:E_TSP_CALL_FEATURE_IND] *May 1 20:04:15.811: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_WAIT_RELEASE, event:E_TSP_CALL_FEATURE_IND] *May 1 20:04:15.811: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:1:1/vtsp_process_event: [state:S_WAIT_RELEASE, event:E_TSP_DISCONNECT_CONF] *May 1 20:04:15.811: //78/CDDFE7FF8029/VTSP:(4/0/0):-1:-1:-1/vtsp_process_event: [state:S_CLOSE_DSPRM, event:E_VTSP_DSM_CLOSE_COMPLETE]

debug voip vtsp function on the Originating Gateway Router# debug voip vtsp function voip vtsp function debugging is on *Apr 18 21:48:25.671: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_do_call_setup_ind:

At the setup request, the CallEntry ID and GUID are set. The call setup functions are shown. *Apr 18 21:48:25.671: //-1/D87794B9802B/VTSP:(2/1:23):0:-1:-1/vtsp_do_normal_call_setup_ind: *Apr 18 21:48:25.671: //-1/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_indicate_call: *Apr 18 21:48:25.675: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_insert_cdb: *Apr 18 21:48:25.675: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_proceeding:


DB-2473


*Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_progress: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_bridge_check_cb: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_bridge_check_cb:exit@1066 *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_bridge_status_cb: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_save_fax_config: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_set_fax_feat_param: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_feature_notify_cb: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_reactivate_ringback: *Apr 18 21:48:25.687: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_reactivate_ringback:exit@871 *Apr 18 21:48:27.451: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb:

At this point, the ringback to the caller has occurred and the next event shows a connection. *Apr *Apr *Apr *Apr *Apr *Apr

18 18 18 18 18 18

21:48:28.635: 21:48:29.003: 21:48:34.059: 21:48:36.587: 21:48:36.587: 21:48:36.587:

//88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_connect: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_generate_disc: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_cc_call_disconnected: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_bridge_status_cb:

The next event shows the call disconnect. There are several VTSP functions that follow the call disconnection to release and terminate the call. *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr *Apr

18 18 18 18 18 18 18 18 18

21:48:36.587: 21:48:36.587: 21:48:36.587: 21:48:36.595: 21:48:36.595: 21:48:36.595: 21:48:36.595: 21:48:36.595: 21:48:36.595:

//88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_disconnect: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_save_fax_config: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_set_fax_feat_param: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_dsm_dsp_stats_complete: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/act_wrelease_release: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_do_call_history: //88/D87794B9802B/VTSP:(2/1:23):0:8:4/vtsp_dsm_closed_cb: //88/D87794B9802B/VTSP:(2/1:23):0:-1:-1/act_terminate: //-1/D87794B9802B/VTSP:(2/1:23):0:-1:-1/vtsp_free_cdb:

debug voip vtsp inout on the Originating Gateway Router# debug voip vtsp inout voip vtsp inout debugging is on *Apr 18 21:48:59.239: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_allocate_cdb: CDB=0x65289878 *Apr 18 21:48:59.239: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_do_call_setup_ind: Event=E_TSP_SETUP_IND Progress Indication=0, CarrierIDCode=, Info Trans Capability=0, Source Carrier ID=, tg_label_flag=0

The following two events show the calling number, called number, and related parameters: *Apr 18 21:48:59.239: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_do_call_setup_ind: Calling Number=4085550111, TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed CLIR=FALSE, CLID Transparent=FALSE, Null Originating Calling Number=FALSE, Calling Translated=FALSE *Apr 18 21:48:59.239: //-1/xxxxxxxxxxxx/VTSP:(2/1:23):-1:-1:-1/vtsp_do_call_setup_ind: Called Number=83103, TON=Unknown, NPI=Unknown *Apr 18 21:48:59.239: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_insert_cdb: *Apr 18 21:48:59.243: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_proceeding: Progress Indication=0 *Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_progress: Progress Indication=8 *Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_timer_stop:


DB-2474

May 2008


Timer Stop Time=538706

The following event shows fax parameters associated with the call: *Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_save_fax_config: Fax Relay=DISABLED - 'fax rate disabled' set (dial-peer) Primary Fax Protocol=IGNORE_FAX_RELAY, Fallback Fax Protocol=IGNORE_FAX_RELAY Fax Parameters Set By=Dialpeer, Peer=3600 *Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_CAPS_IND *Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_CAPS_ACK *Apr 18 21:48:59.255: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_feature_notify_cb: Feature ID=0, Feature Status=1

The following event shows the call connection: *Apr 18 21:49:03.779: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_connect: Progress Indication=2 *Apr 18 21:49:03.779: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_ring_noan_timer_stop: Timer Stop Time=539158 Router#

The following event shows the call disconnect: *Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_generate_disc: Cause Value=16 *Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_ring_noan_timer_stop: Timer Stop Time=541374

The following event shows that it was the calling party that initiated the call disconnect: *Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_set_release_source: Release Direction=PSTN, Release Source=Calling Party-PSTN *Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_timer: Timer Start Time=541374, Timer Value=15000(ms) *Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_generate_disc: Return Code=0 *Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_disconnect: Cause Value=16, Previous Cause Value=16 *Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_ring_noan_timer_stop: Timer Stop Time=541374 *Apr 18 21:49:25.943: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_dsm_save_fax_config: Fax Relay=DISABLED - 'fax rate disabled' set (dial-peer) Primary Fax Protocol=IGNORE_FAX_RELAY, Fallback Fax Protocol=IGNORE_FAX_RELAY Fax Parameters Set By=Dialpeer, Peer=3600 *Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_dsm_dsp_stats_complete: *Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_timer: Timer Start Time=541375, Timer Value=60000(ms)

The following two events show the call being released and the timer stopping: *Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/act_wrelease_release: *Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_play_busy_timer_stop: Timer Stop Time=541375 *Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:8:4/vtsp_timer_stop: Timer Stop Time=541375 *Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:-1:-1/act_terminate: *Apr 18 21:49:25.951: //90/EC79A754802C/VTSP:(2/1:23):0:-1:-1/vtsp_timer_stop: Timer Stop Time=541375 *Apr 18 21:49:25.951: //-1/EC79A754802C/VTSP:(2/1:23):0:-1:-1/vtsp_free_cdb: CDB=0x65289878 Router#


DB-2475


debug voip vtsp tone on the Originating Gateway Router# debug voip vtsp tone voip vtsp tone debugging is on

This output shows a wrong number dialed in the two-stage call to see the tone generated by the router. *Apr 18 21:52:26.595: //98/657C0B9C8030/VTSP:(2/1:23):0:8:4/act_pre_con_disconnect: [Number Unobtainable]-Tone Played In Direction [Network]

debug voip vtsp Displaying T.38 Fax Relay Statistics on the Originating Gateway

This output shows the fax relay statistics. Router# debug voip vtsp VTSP: debug debug debug debug

voip voip voip voip

vtsp vtsp vtsp vtsp

event error error inout

is ON (filter is OFF) software is ON call is ON (filter is OFF) is ON (filter is OFF)

May

7 21:37:35.322 UTC: //-1/xxxxxxxxxxxx/VTSP:(3/1:D):-1:-1:-1/vtsp_allocate_cdb: CDB=0x63088050 May 7 21:37:35.322 UTC: //-1/xxxxxxxxxxxx/VTSP:(3/1:D):-1:-1:-1/vtsp_do_call_setup_ind: Event=E_TSP_SETUP_IND Progress Indication=3, CarrierIDCode=, Info Trans Capability=16, Source Carrier ID=, tg_label_flag=0 May 7 21:37:35.322 UTC: //-1/xxxxxxxxxxxx/VTSP:(3/1:D):-1:-1:-1/vtsp_do_call_setup_ind: Called Number=41021, TON=National, NPI=ISDN May 7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_timer: Timer Start Time=1019501, Timer Value=180000(ms) May 7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_insert_cdb: May 7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_SETUP_IND_PEND, event:E_VTSP_DSM_OPEN_SUCCESS] May 7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_setup_ind_pend_success: May 7 21:37:35.326 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_realloc_cdb: CDB=0x63088050 May 7 21:37:35.326 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_insert_cdb: May 7 21:37:35.326 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer: Timer Start Time=1019501, Timer Value=180000(ms) May 7 21:37:35.330 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_SETUP_INDICATED, event:E_CC_PROCEEDING] May 7 21:37:35.330 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_proceeding: Progress Indication=0 May 7 21:37:35.330 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop: Timer Stop Time=1019502 May 7 21:37:35.394 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_PROCEEDING, event:E_CC_ALERT] May 7 21:37:35.394 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_alert: Progress Indication=0, Signal Indication=1, Setup Progress Indication=3 May 7 21:37:35.394 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop: Timer Stop Time=1019508 May 7 21:37:35.398 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_alert: Progress Indication=0, Tone= May 7 21:37:37.422 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config: Fax Relay=ENABLED Primary Fax Protocol=T38_FAX_RELAY, Fallback Fax Protocol=NONE_FAX_RELAY Fax Parameters Set By=Dialpeer, Peer=2 May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config: LS Red=0, HS Red=0 May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_ALERTING, event:E_CC_DO_CAPS_IND]


DB-2476

May 2008


May

7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_CAPS_IND May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_ALERTING, event:E_CC_CAPS_IND] May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_CAPS_ACK May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_ALERTING, event:E_CC_SERVICE_MSG] May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_service_msg_down: May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop: Timer Stop Time=1019711 May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_ALERTING, event:E_CC_CONNECT] May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_alert_connect: Progress Indication=0 May 7 21:37:37.426 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop: Timer Stop Time=1019711 May 7 21:37:37.598 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_feature_notify_cb: Feature ID=0, Feature Status=1 May 7 21:37:37.598 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_feature_notify_cb: Feature ID=0, Feature Status=1 May 7 21:37:44.123 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_MC_LOCAL_DNLD_DONE May 7 21:37:44.123 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_SET_FAX_MODE May 7 21:37:44.123 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_MC_LOCAL_DNLD_DONE May 7 21:37:44.123 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_SET_FAX_MODE May 7 21:38:02.911 UTC: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x6040A40C reading 0x1 May 7 21:38:02.911 UTC: %ALIGN-3-TRACE: -Traceback= 6040A40C 60409198 603F8338 603F85F8 613EA398 619B369C 619B40BC 613DFEE4 May 7 21:38:02.915 UTC: %ALIGN-3-TRACE: -Traceback= 6040A54C 60409198 603F8338 603F85F8 613EA398 619B369C 619B40BC 613DFEE4 May 7 21:38:37.483 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_CONNECT, event:E_CC_CAPS_IND] May 7 21:38:37.483 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_peer_event_cb: Event=E_DSM_CC_CAPS_ACK May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_CONNECT, event:E_TSP_DISCONNECT_IND] May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_generate_disc: Cause Value=16 May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop: Timer Stop Time=1025735 May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop: Timer Stop Time=1025735 May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_set_release_source: Release Direction=PSTN, Release Source=Calling Party-PSTN May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer: Timer Start Time=1025735, Timer Value=15000(ms) May 7 21:38:37.663 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_generate_disc: Return Code=0 May 7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_CONNECT, event:E_CC_DISCONNECT] May 7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_disconnect: Cause Value=16, Previous Cause Value=16 May 7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_ring_noan_timer_stop: Timer Stop Time=1025735 May 7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config: Fax Relay=ENABLED Primary Fax Protocol=T38_FAX_RELAY, Fallback Fax Protocol=NONE_FAX_RELAY Fax Parameters Set By=Dialpeer, Peer=2 May 7 21:38:37.667 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_dsm_save_fax_config:


DB-2477


LS Red=0, HS Red=0 7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_WAIT_STATS, event:E_VTSP_DSM_STATS_COMPLETE] May 7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_dsm_dsp_stats_complete: May 7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer: Timer Start Time=1025738, Timer Value=60000(ms) May 7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_WAIT_RELEASE, event:E_TSP_DISCONNECT_CONF] May 7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/act_wrelease_release: May 7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_play_busy_timer_stop: Timer Stop Time=1025738 May 7 21:38:37.691 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_timer_stop: Timer Stop Time=1025738 May 7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: [state:S_CLOSE_DSPRM, event:E_VTSP_DSM_STATS_COMPLETE] May 7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:0:0/vtsp_process_event: Unexpected EVENT [E_VTSP_DSM_STATS_COMPLETE] Received For STATE [S_CLOSE_DSPRM]; Previous STATE [0.17 ] May 7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_process_event: [state:S_CLOSE_DSPRM, event:E_VTSP_DSM_CLOSE_COMPLETE] May 7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/act_terminate: May 7 21:38:37.695 UTC: //9/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_timer_stop: Timer Stop Time=1025738 May 7 21:38:37.695 UTC: //-1/96A4C0C48006/VTSP:(3/1:D):0:-1:-1/vtsp_free_cdb: CDB=0x63088050 May

Related Commands

Command

Description

debug voip dsm

Displays information about the DSM.

show debug

Displays which debug commands are enabled.

voice call debug



DB-2478

May 2008

Debug Commands debug voip xcodemsp

debug voip xcodemsp To display debugging information from the Transcoding Media Service Processor and its related applications, use the debug voip xcodemsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug voip xcodemsp no debug voip xcodemsp

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(8)T


12.2SX


Examples

The following is sample output from the debug voip xcodemsp command: Router# debug voip xcodemsp XCODEMSP debugging is on Router# Router# *Jul 8 *Jul 8 *Jul 8 *Jul 8 *Jul 8 *Jul 8 *Jul 8 *Jul 8 *Jul 8 *Jul 8 *Jul 8 *Jul 8 Router# Router# Router# sess_id 16777223 16777223

18:36:53: 18:36:53: 18:36:53: 18:36:53: 18:36:53: 18:36:53: 18:36:53: 18:36:53: 18:36:53: 18:36:53: 18:36:53: 18:36:53:

xcmsp_call_setup_request: xcmsp_call_setup_request: xcmsp_bridge: xc_add_streams: xc_add_streams: stream id xc_add_streams: stream id xcmsp_bridge: xc_add_streams: xc_add_streams: stream id xc_add_streams: stream id xc_connect_bridges: xcmsp_dsmp_response

show sccp connections conn_id stype mode 16777905 16777921

codec

xcode sendrecv g711a xcode sendrecv g729ab

callID 20, rscID 1 srvcDef.srvc_id 2

1 added 2 added

5 added 6 added

ripaddr

rport sport

1.4.177.1 1.4.177.5

16628 18870 31318 18146

Total number of active session(s) 1, and connection(s) 2 Router# *Jul 8 18:37:22: xcmsp_bridge_drop:


DB-2479

Debug Commands debug voip xcodemsp

*Jul *Jul *Jul *Jul *Jul *Jul *Jul *Jul

8 8 8 8 8 8 8 8

18:37:22: 18:37:22: 18:37:22: 18:37:22: 18:37:22: 18:37:22: 18:37:22: 18:37:22:

xcmsp_bridge_drop: deleting stream id 5 xcmsp_bridge_drop: deleting stream id 6 xcmsp_dsmp_response xcmsp_dsmp_response: DSMP_DISCONNECTED xcmsp_bridge_drop: xcmsp_bridge_drop: deleting stream id 1 xcmsp_bridge_drop: deleting stream id 2 xcmsp_call_disconnect:


DB-2480

May 2008

Debug Commands debug vpdn pppoe-data

debug vpdn pppoe-data Note

Effective with Cisco IOS Release 12.2(13)T, the debug vpdn pppoe-data command is replaced by the debug pppoe command. See the debug pppoe command for more information. To display data packets of PPP over Ethernet (PPPoE) sessions, use the debug vpdn pppoe-data command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpdn pppoe-data no debug vpdn pppoe-data

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T


12.2(13)T

This command was replaced by the debug pppoe command.

12.2SX


Usage Guidelines

Examples

The debug vpdn pppoe-data command displays a large number of debug messages and should generally be used only on a debug chassis with a single active session.

The following is sample output from the debug vpdn pppoe-data command: Router# debug vpdn pppoe-data 6d20h:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up 6d20h:PPPoE:OUT contiguous pak, size 19 FF 03 C0 21 01 01 00 0F 03 05 C2 23 05 05 06 D3 FF 2B DA 6d20h:PPPoE:IN particle pak, size 1240 C0 21 01 01 00 0A 05 06 39 53 A5 17 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6d20h:PPPoE:OUT contiguous pak, size 14 FF 03 C0 21 02 01 00 0A 05 06 39 53 A5 17 6d20h:PPPoE:OUT contiguous pak, size 19 FF 03 C0 21 01 02 00 0F 03 05 C2 23 05 05 06 D3


DB-2481


FF 2B DA 6d20h:PPPoE:IN particle pak, size 1740 C0 21 02 02 00 0F 03 DA 00 80 C2 00 07 00 C2 EB 10 38 88 64 11 6d20h:PPPoE:OUT contiguous pak, size 30 FF 03 C2 23 01 06 00 EE 91 0A B0 01 CB 89

05 C2 23 05 05 06 D3 FF 2B 00 00 10 7B 01 2C D9 00 B0 00

1A 10 99 1E 6E 8F 8C F2 C6 68 13 47 61 6E 67 61

6d20h:PPPoE:IN particle pak, size 3840 C2 23 02 06 00 24 10 E6 84 FF 3A A4 49 19 CE D7 AC D7 D5 96 CC 23 B3 41 6B 61 73 68 40 63 69 73 63 6F 2E 63 6F 6D 00 00 6d20h:PPPoE:OUT contiguous pak, size 8 FF 03 C2 23 03 06 00 04 6d20h:PPPoE:OUT contiguous pak, size 14 FF 03 80 21 01 01 00 0A 03 06 65 65 00 66 6d20h:PPPoE:IN particle pak, size 1240 80 21 01 01 00 0A 03 06 00 00 00 00 49 19 CE D7 AC D7 D5 96 CC 23 B3 41 6B 61 73 68 40 63 69 73 63 6F 2E 63 6F 6D 00 00 6d20h:PPPoE:OUT contiguous pak, size 14 FF 03 80 21 03 01 00 0A 03 06 65 65 00 67 6d20h:PPPoE:IN particle pak, size 1240 80 21 02 01 00 0A 03 06 65 65 00 66 00 04 AA AA 03 00 80 C2 00 07 00 00 00 10 7B 01 2C D9 00 B0 C2 EB 10 38 88 64 11 00 6d20h:PPPoE:IN particle pak, size 1240 80 21 01 02 00 0A 03 06 65 65 00 67 49 19 CE D7 AC D7 D5 96 CC 23 B3 41 6B 61 73 68 40 63 69 73 63 6F 2E 63 6F 6D 00 00 6d20h:PPPoE:OUT contiguous pak, size 14 FF 03 80 21 02 02 00 0A 03 06 65 65 00 67 6d20h:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access1, changed state to up 6d20h:PPPoE:OUT contiguous pak, size 16 FF 03 C0 21 09 01 00 0C D3 FF 2B DA 4C 4D 49 A4 6d20h:PPPoE:IN particle pak, size 1440 C0 21 0A 01 00 0C 39 53 A5 17 4C 4D 49 A4 AA AA 03 00 80 C2 00 07 00 00 00 10 7B 01 2C D9 00 B0 C2 EB 10 38 88 64 11 00 6d20h:PPPoE:IN particle pak, size 1440 C0 21 09 01 00 0C 39 53 A5 17 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00



DB-2482

May 2008


Table 376

Related Commands

debug vpdn pppoe-data Field Descriptions

Field

Descriptions

6d20h:%LINK-3-UPDOWN:Interface Virtual-Access1, changed state to up

Virtual access interface 1 came up.

6d20h:PPPoE:OUT

The host delivered a PPPoE session packet to the access concentrator.

6d20h:PPPoE:IN

The access concentrator received a PPPoE session packet.

6d20h:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access1, changed state to up

Line protocol is up; the line can be used.

contiguous pak, size 19

Size 19 contiguous packet.

particle pak, size 1240

Size 1240 particle packet.

Command

Description

debug pppoe

Displays debugging information for PPPoE sessions.

debug vpdn pppoe-error

Displays PPPoE protocol errors that prevent a session from being established or errors that cause an established session to be closed.

debug vpdn pppoe-events


debug vpdn pppoe-packet

Displays each PPPoE protocol packet exchanged.

protocol (VPDN)

Specifies the L2TP that the VPDN subgroup will use.

show vpdn

Displays information about active L2F protocol tunnel and message identifiers in a VPDN.

vpdn enable

Enables virtual private dialup networking on the router and informs the router to look for tunnel definitions in a local database and on a remote authorization server (home gateway), if one is present.


DB-2483

Debug Commands debug vpdn pppoe-error

debug vpdn pppoe-error Note

Effective with Cisco IOS Release 12.2(13)T, the debug vpdn pppoe-error command is replaced by the debug pppoe command. See the debug pppoe command for more information. To display PPP over Ethernet (PPPoE) protocol errors that prevent a session from being established or errors that cause an established sessions to be closed, use the debug vpdn pppoe-error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpdn pppoe-error no debug vpdn pppoe-error

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T


12.2(13)T


12.2SX


Examples

The following is a full list of error messages displayed by the debug vpdn pppoe-error command: PPPOE:pppoe_acsys_err cannot grow packet PPPoE:Cannot find PPPoE info PPPoE:Bad MAC address:00b0c2eb1038 PPPOE:PADI has no service name tag PPPoE:pppoe_handle_padi cannot add AC name/Cookie. PPPoE:pppoe_handle_padi cannot grow packet PPPoE:pppoe_handle_padi encap failed PPPoE cannot create virtual access. PPPoE cannot allocate session structure. PPPoE cannot store session element in tunnel. PPPoE cannot allocate tunnel structure. PPPoE cannot store tunnel PPPoE:VA221:No Session, Packet Discarded PPPOE:Tried to shutdown a null session PPPoE:Session already open, closing PPPoE:Bad cookie:src_addr=00b0c2eb1038 PPPoE:Max session count on mac elem exceeded:mac=00b0c2eb1038 PPPoE:Max session count on vc exceeded:vc=3/77 PPPoE:Bad MAC address - dropping packet PPPoE:Bad version or type - dropping packet



DB-2484

May 2008


Table 377

debug vpdn pppoe-error Field Descriptions

Field

Descriptions

PPPOE:pppoe_acsys_err cannot grow packet Asynchronous PPPoE packet initialization error. PPPoE:Cannot find PPPoE info

The access concentrator sends a PADO to the host.

PPPoE:Bad MAC address:00b0c2eb1038

The host was unable to identify the Ethernet MAC address.

PPPOE:PADI has no service name tag

PADI requires a service name tag.

PPPoE:pppoe_handle_padi cannot add AC name/Cookie.

pppoe_handle_padi could not append AC name.

PPPoE:pppoe_handle_padi cannot grow packet

pppoe_handle_padi could not append packet.

PPPoE:pppoe_handle_padi encap failed

pppoe_handle_padi could not specify PPPoE on ATM encapsulation.

PPPoE cannot create virtual access.

PPPoE session unable to verify virtual access interface.

PPPoE cannot allocate session structure.

PPPoE session unable to allocate Stage Protocol.

PPPoE cannot store session element in tunnel.

PPPoE tunnel cannot allocate session element.

PPPoE cannot allocate tunnel structure.

PPPoE tunnel unable to allocate Stage Protocol.

PPPoE cannot store tunnel

PPPoE configuration settings unable to initialize a tunnel.

PPPoE:VA221:No Session, Packet Discarded No sessions created. All packets dropped. PPPOE:Tried to shutdown a null session

Null session shutdown.

PPPoE:Session already open, closing

PPPoE session already open.

PPPoE:Bad cookie:src_addr=00b0c2eb1038 PPPoE session unable to append new cookie. PPPoE:Max session count on mac elem exceeded:mac=00b0c2eb1038

The maximum number of sessions exceeded the Ethernet MAC address.

PPPoE:Max session count on vc exceeded:vc=3/77

The maximum number of sessions exceeded the PVC connection.

PPPoE:Bad MAC address - dropping packet The host was unable to identify the MAC address. Packet dropped. PPPoE:Bad version or type - dropping packet The host was unable to identify the encapsulation type.

Related Commands

Command

Description

debug pppoe


debug vpdn pppoe-data






protocol (VPDN)



DB-2485


Command

Description

show vpdn


vpdn enable

Enables virtual private dialup networking on the router and informs the router to look for tunnel definitions in a local database and on a remote authorization server (home gateway), if one is pre-sent.


DB-2486

May 2008

Debug Commands debug vpdn pppoe-events

debug vpdn pppoe-events Note

Effective with Cisco IOS Release 12.2(13)T, the debug vpdn pppoe-events command is replaced by the debug pppoe command. See the debug pppoe command for more information. To display PPP over Ethernet (PPPoE) protocol messages about events that are part of normal session establishment or shutdown, use the debug vpdn pppoe-events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpdn pppoe-events no debug vpdn pppoe-events

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T


12.2(13)T


12.2SX


Examples

The following is sample output from the debug vpdn pppoe-events command: 1w5d:IN PADI from PPPoE tunnel 1w5d:OUT PADO from PPPoE tunnel 1w5d:IN PADR from PPPoE tunnel 1w5d:PPPoE:VPN session created. 1w5d:%LINK-3-UPDOWN:Interface Virtual-Access2, changed state to up 1w5d:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access2, changed state to up


debug vpdn pppoe-events Field Descriptions

Field

Descriptions

1w5d:IN PADI from PPPoE tunnel

The access concentrator receives an Active Discovery Initiation (PADI) packet from the PPPoE tunnel.

1w5d:OUT PADO from PPPoE tunnel

The access concentrator sends an Active Discovery Offer (PADO) to the host.


DB-2487

Debug Commands debug vpdn pppoe-events

Table 378

debug vpdn pppoe-events Field Descriptions (continued)

Field

Descriptions

1w5d:IN PADR from PPPoE tunnel

The host sends a single Active Discovery Request (PADR) to the access concentrator that it has chosen.

Related Commands

1w5d:PPPoE:VPN session created.

The access concentrator receives the PADR packet and creates a virtual private network (VPN) session.

1w5d:%LINK-3-UPDOWN:Interface Virtual-Access2, changed state to up

Virtual access interface 2 came up.

1w5d:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access2, changed state to up

Line protocol is up. The line can be used.

Command

Description

debug pppoe








protocol (VPDN)


show vpdn


vpdn enable



DB-2488

May 2008

Debug Commands debug vpdn pppoe-packet

debug vpdn pppoe-packet Note

Effective with Cisco IOS Release 12.2(13)T, the debug vpdn pppoe-packet command is replaced by the debug pppoe command. See the debug pppoe command for more information. To display each PPP over Ethernet (PPPoE) protocol packet exchanged, use the debug vpdn pppoe-packet command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpdn pppoe-packet no debug vpdn pppoe-packet

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)T


12.2(13)T


12.2SX


Usage Guidelines

The debug vpdn pppoe-packet command displays a large number of debug messages and should generally only be used on a debug chassis with a single active session.

Examples

The following is sample output from the debug vpdn pppoe-packet command: PPPoE control packets debugging is on 1w5d:PPPoE:discovery packet contiguous pak, size 74 FF FF FF FF FF FF 00 10 7B 00 00 00 04 01 01 00 00 00 00 00 00 00 00 00 00 00 00 1w5d:OUT PADO from PPPoE tunnel contiguous pak, size 74 00 01 09 00 AA AA 03 00 80 7B 01 2C D9 00 90 AB 13 BC 00 20 01 01 00 00 01 02 00 1w5d:PPPoE:discovery packet contiguous pak, size 74 00 90 AB 13 BC A8 00 10 7B 00 00 00 20 01 01 00 00 01 01 04 00 10 B7 4B 86 5B 90

01 2C D9 88 63 11 09 00 00 00 00 00 00 00 00 00 00 00 00 00 ...

C2 00 07 00 00 00 10 A8 88 63 11 07 00 00 04 41 67 6E 69 01 ...

01 2C D9 88 63 11 19 02 00 04 41 67 6E 69 A5 EF 11 64 A9 BA ...


DB-2489

Debug Commands debug vpdn pppoe-packet


Related Commands

debug vpdn pppoe-packet Field Descriptions

Field

Descriptions

PPPoE control packets debugging is on

PPPoE debugging of packets is enabled.

1w5d:PPPoE:discovery packet

The host performs a discovery to initiate a PPPoE session.

1w5d:OUT PADO from PPPoE tunnel

The access concentrator sends a PADO to the host.

1w5d:PPPoE:discovery packet

The host performs a discovery to initiate a PPPoE session.

contiguous pak, size 74

Size 74 contiguous packet.

Command

Description

debug pppoe








protocol (VPDN)


show vpdn


vpdn enable



DB-2490

May 2008

Debug Commands debug vpdn

debug vpdn To troubleshoot Layer 2 Forwarding (L2F) or Layer 2 Tunnel Protocol (L2TP) virtual private dialup network (VPDN) tunneling events and infrastructure, use the debug vpdn command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpdn {call {event | fsm} | authorization {error | event} | error | event [disconnect] | l2tp sequencing | l2x data | l2x errors | l2x events | l2x packets | message | packet [detail | errors] | sss {error | event | fsm}} no debug vpdn {call {event | fsm} | authorization {error | event} | error | event [disconnect] | l2tp sequencing | l2x data | l2x errors | l2x events | l2x packets | message | packet [detail | errors] | sss {error | event | fsm}}

Syntax Description

authorization error

Displays authorization errors.

authorization event

Displays authorization events.

call event

Displays significant events in the VPDN call manager.

call fsm

Displays significant events in the VPDN call manager finite state machine (fsm).

error

Displays VPDN errors.

event

Displays VPDN events.

disconnect

(Optional) Displays VPDN disconnect events.

l2tp sequencing

Displays significant events related to L2TP sequence numbers such as mismatches, resend queue flushes, and drops.

l2x data

Displays errors that occur in data packets.

l2x errors

Displays errors that occur in protocol-specific conditions.

l2x events

Displays events resulting from protocol-specific conditions.

l2x packets

Displays detailed information about control packets in protocol-specific conditions.

message

Displays VPDN interprocess messages.

packet

Displays information about VPDN packets.

detail

(Optional) Displays detailed packet information, including packet dumps.

errors

(Optional) Displays errors that occur in packet processing.

sss error

Displays debug information about VPDN Subscriber Service Switch (SSS) errors.

sss event

Displays debug information about VPDN SSS events.

sss fsm

Displays debug information about the VPDN SSS fsm.

Command Modes

Privileged EXEC

Command History

0S Release

Modification

12.0(23)S



DB-2491


12.0(31)S

The output was enhanced to display messages about control channel authentication events.

S Release

Modification

12.2(22)S


12.2(27)SBC

Support for enhanced display of messages about control channel authentication events was added in Cisco IOS Release 12.2(27)SBC.

12.2(28)SB

Support for the display of messages about congestion avoidance events was added in Cisco IOS Release 12.2(28)SB.

T Release

Modification

11.2


12.0(5)T

Support was added for L2TP debugging messages. The l2tp sequencing and error keywords were added. The l2f errors, l2f events, and l2f packets keywords were changed to l2x errors, l2x events, and l2x packets.

12.2(4)T

Support was added for the message and call {event | fsm} keywords.

12.2(11)T

Support was added for the detail keyword.

12.2(13)T

Support was added for the sss {error | event | fsm} keywords.

12.4(15)T

Support was added for the authorization {error | event} keywords.

Usage Guidelines

Note that the debug vpdn packet and debug vpdn packet detail commands generate several debug operations per packet. Depending on the L2TP traffic pattern, these commands may cause the CPU load to increase to a high level that impacts performance.

Examples

This section contains the following examples: •

Debugging VPDN Events on a NAS—Normal L2F Operations

•

Debugging VPDN Events on the Tunnel Server—Normal L2F Operations

•

Debugging VPDN Events on the NAS—Normal L2TP Operations

•

Debugging VPDN Events on the Tunnel Server—Normal L2TP Operations

•

Debugging Protocol-Specific Events on the NAS—Normal L2F Operations

•

Debugging Protocol-Specific Events on the Tunnel Server—Normal L2F Operations

•

Displaying L2TP Congestion Avoidance Settings

•

Debugging Errors on the NAS—L2F Error Conditions

•

Debugging L2F Control Packets for Complete Information

•

Debugging an L2TPv3 Xconnect Session—Normal Operations

•

Debugging Control Channel Authentication Events

Debugging VPDN Events on a NAS—Normal L2F Operations

The network access server (NAS) has the following VPDN configuration: vpdn-group 1 request-dialin protocol l2f domain cisco.com initiate-to ip 172.17.33.125


DB-2492

May 2008


username nas1 password nas1

The following is sample output from the debug vpdn event command on a NAS when an L2F tunnel is brought up and Challenge Handshake Authentication Protocol (CHAP) authentication of the tunnel succeeds: Router# debug vpdn event %LINK-3-UPDOWN: Interface Async6, changed state to up *Mar 2 00:26:05.537: looking for tunnel -- cisco.com -*Mar 2 00:26:05.545: Async6 VPN Forwarding... *Mar 2 00:26:05.545: Async6 VPN Bind interface direction=1 *Mar 2 00:26:05.553: Async6 VPN vpn_forward_user [email protected] is forwarded %LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up *Mar 2 00:26:06.289: L2F: Chap authentication succeeded for nas1.

The following is sample output from the debug vpdn event command on a NAS when the L2F tunnel is brought down normally: Router# debug vpdn event %LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down %LINK-5-CHANGED: Interface Async6, changed state to reset *Mar 2 00:27:18.865: Async6 VPN cleanup *Mar 2 00:27:18.869: Async6 VPN reset *Mar 2 00:27:18.873: Async6 VPN Unbind interface %LINK-3-UPDOWN: Interface Async6, changed state to down

Table 380 describes the significant fields shown in the two previous displays. The output describes normal operations when an L2F tunnel is brought up or down on a NAS. Table 380

debug vpdn event Field Descriptions for the NAS

Field

Description

Asynchronous interface coming up

%LINK-3-UPDOWN: Interface Async6, changed state to up

Asynchronous interface 6 came up.

looking for tunnel -- cisco.com --

Domain name is identified.

Async6 VPN Forwarding... Async6 VPN Bind interface direction=1

Tunnel is bound to the interface. These are the direction values: •

1—From the NAS to the tunnel server

•

2—From the tunnel server to the NAS

Async6 VPN vpn_forward_user [email protected] is forwarded

Tunnel for the specified user and domain name is forwarded.

%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up

Line protocol is up.

L2F: Chap authentication succeeded for nas1.

Tunnel was authenticated with the tunnel password nas1.


DB-2493


Table 380

debug vpdn event Field Descriptions for the NAS (continued)

Field

Description

Virtual access interface coming down

%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down

Normal operation when the virtual access interface is taken down.

Async6 VPN cleanup

Normal cleanup operations performed when the line or virtual access interface goes down.

Async6 VPN reset Async6 VPN Unbind interface

Debugging VPDN Events on the Tunnel Server—Normal L2F Operations

The tunnel server has the following VPDN configuration, which uses nas1 as the tunnel name and the tunnel authentication name. The tunnel authentication name might be entered in a user’s file on an authentication, authorization, and accounting (AAA) server and used to define authentication requirements for the tunnel. vpdn-group 1 accept-dialin protocol l2f virtual-template 1 terminate-from hostname nas1

The following is sample output from the debug vpdn event command on the tunnel server when an L2F tunnel is brought up successfully: Router# debug vpdn event L2F: Chap authentication succeeded for nas1. Virtual-Access3 VPN Virtual interface created for [email protected] Virtual-Access3 VPN Set to Async interface Virtual-Access3 VPN Clone from Vtemplate 1 block=1 filterPPP=0 %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up Virtual-Access3 VPN Bind interface direction=2 Virtual-Access3 VPN PPP LCP accepted sent & rcv CONFACK %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up

The following is sample output from the debug vpdn event command on a tunnel server when an L2F tunnel is brought down normally: Router# debug vpdn event %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to down Virtual-Access3 VPN cleanup Virtual-Access3 VPN reset Virtual-Access3 VPN Unbind interface Virtual-Access3 VPN reset %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to down

Table 381 describes the fields shown in two previous outputs. The output describes normal operations when an L2F tunnel is brought up or down on a tunnel server.


DB-2494

May 2008


Table 381

debug vpdn event Field Descriptions for the Tunnel Server

Field

Description

Tunnel coming up

L2F: Chap authentication succeeded for nas1.

PPP CHAP authentication status for the tunnel named nas1.

Virtual-Access3 VPN Virtual interface created for [email protected]

Virtual access interface was set up on the tunnel server for the user [email protected].

Virtual-Access3 VPN Set to Async interface Virtual access interface 3 was set to asynchronous for character-by-character transmission. Virtual-Access3 VPN Clone from Vtemplate Virtual template 1 was applied to virtual access 1 block=1 filterPPP=0 interface 3. %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up

Link status is set to up.

Virtual-Access3 VPN Bind interface direction=2

Tunnel is bound to the interface. These are the direction values: •

1—From the NAS to the tunnel server

•

2—From the tunnel server to the NAS

Virtual-Access3 VPN PPP LCP accepted sent & rcv CONFACK

PPP link control protocol (LCP) configuration settings (negotiated between the remote client and the NAS) were copied to the tunnel server and acknowledged.

%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up

Line protocol is up; the line can be used.

Tunnel coming down

%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to down

Virtual access interface is coming down.

Virtual-Access3 VPN cleanup

Router is performing normal cleanup operations when a virtual access interface used for an L2F tunnel comes down.

Virtual-Access3 VPN reset Virtual-Access3 VPN Unbind interface Virtual-Access3 VPN reset %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to down

Line protocol is down for virtual access interface 3; the line cannot be used.


DB-2495


Debugging VPDN Events on the NAS—Normal L2TP Operations

The following is sample output from the debug vpdn event command on the NAS when an L2TP tunnel is brought up successfully: Router# debug vpdn event 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:17: 20:19:18: 20:19:18: 20:19:18: 20:19:19: up

L2TP: I SCCRQ from ts1 tnl 8 L2X: Never heard of ts1 Tnl 7 L2TP: New tunnel created for remote ts1, address 172.21.9.4 Tnl 7 L2TP: Got a challenge in SCCRQ, ts1 Tnl 7 L2TP: Tunnel state change from idle to wait-ctl-reply Tnl 7 L2TP: Got a Challenge Response in SCCCN from ts1 Tnl 7 L2TP: Tunnel Authentication success Tnl 7 L2TP: Tunnel state change from wait-ctl-reply to established Tnl 7 L2TP: SM State established Tnl/Cl 7/1 L2TP: Session FS enabled Tnl/Cl 7/1 L2TP: Session state change from idle to wait-for-tunnel Tnl/Cl 7/1 L2TP: New session created Tnl/Cl 7/1 L2TP: O ICRP to ts1 8/1 Tnl/Cl 7/1 L2TP: Session state change from wait-for-tunnel to wait-connect Tnl/Cl 7/1 L2TP: Session state change from wait-connect to established Vi1 VPDN: Virtual interface created for [email protected] Vi1 VPDN: Set to Async interface Vi1 VPDN: Clone from Vtemplate 1 filterPPP=0 blocking %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up Vi1 VPDN: Bind interface direction=2 Vi1 VPDN: PPP LCP accepting rcv CONFACK %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to

Debugging VPDN Events on the Tunnel Server—Normal L2TP Operations

The following is sample output from the debug vpdn event command on the tunnel server when an L2TP tunnel is brought up successfully: Router# debug vpdn event 20:47:33: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:35: 20:47:36:

%LINK-3-UPDOWN: Interface Async7, changed state to up As7 VPDN: Looking for tunnel -- cisco.com -As7 VPDN: Get tunnel info for cisco.com with NAS nas1, IP 172.21.9.13 As7 VPDN: Forward to address 172.21.9.13 As7 VPDN: Forwarding... As7 VPDN: Bind interface direction=1 Tnl/Cl 8/1 L2TP: Session FS enabled Tnl/Cl 8/1 L2TP: Session state change from idle to wait-for-tunnel As7 8/1 L2TP: Create session Tnl 8 L2TP: SM State idle Tnl 8 L2TP: Tunnel state change from idle to wait-ctl-reply Tnl 8 L2TP: SM State wait-ctl-reply As7 VPDN: [email protected] is forwarded Tnl 8 L2TP: Got a challenge from remote peer, nas1 Tnl 8 L2TP: Got a response from remote peer, nas1 Tnl 8 L2TP: Tunnel Authentication success Tnl 8 L2TP: Tunnel state change from wait-ctl-reply to established Tnl 8 L2TP: SM State established As7 8/1 L2TP: Session state change from wait-for-tunnel to wait-reply As7 8/1 L2TP: Session state change from wait-reply to established %LINEPROTO-5-UPDOWN: Line protocol on Interface Async7, changed state to up


DB-2496

May 2008


Debugging Protocol-Specific Events on the NAS—Normal L2F Operations

The following is sample output from the debug vpdn l2x events command on the NAS when an L2F tunnel is brought up successfully: Router# debug vpdn l2x events %LINK-3-UPDOWN: Interface Async6, changed state to up *Mar 2 00:41:17.365: L2F Open UDP socket to 172.21.9.26 *Mar 2 00:41:17.385: L2F_CONF received *Mar 2 00:41:17.389: L2F Removing resend packet (type 1) *Mar 2 00:41:17.477: L2F_OPEN received *Mar 2 00:41:17.489: L2F Removing resend packet (type 2) *Mar 2 00:41:17.493: L2F building nas2gw_mid0 %LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up *Mar 2 00:41:18.613: L2F_OPEN received *Mar 2 00:41:18.625: L2F Got a MID management packet *Mar 2 00:41:18.625: L2F Removing resend packet (type 2) *Mar 2 00:41:18.629: L2F MID synced NAS/HG Clid=7/15 Mid=1 on Async6

The following is sample output from the debug vpdn l2x events command on a NAS when an L2F tunnel is brought down normally: Router# debug vpdn l2x events %LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down %LINK-5-CHANGED: Interface Async6, changed state to reset *Mar 2 00:42:29.213: L2F_CLOSE received *Mar 2 00:42:29.217: L2F Destroying mid *Mar 2 00:42:29.217: L2F Removing resend packet (type 3) *Mar 2 00:42:29.221: L2F Tunnel is going down! *Mar 2 00:42:29.221: L2F Initiating tunnel shutdown. *Mar 2 00:42:29.225: L2F_CLOSE received *Mar 2 00:42:29.229: L2F_CLOSE received *Mar 2 00:42:29.229: L2F Got closing for tunnel *Mar 2 00:42:29.233: L2F Removing resend packet *Mar 2 00:42:29.233: L2F Closed tunnel structure %LINK-3-UPDOWN: Interface Async6, changed state to down *Mar 2 00:42:31.793: L2F Closed tunnel structure *Mar 2 00:42:31.793: L2F Deleted inactive tunnel

Table 382 describes the fields shown in the displays. Table 382

debug vpdn l2x-events Field Descriptions—NAS

Field

Descriptions

Tunnel coming up


Asynchronous interface came up normally.

L2F Open UDP socket to 172.21.9.26

L2F opened a User Datagram Protocol (UDP) socket to the tunnel server IP address.

L2F_CONF received

L2F_CONF signal was received. When sent from the tunnel server to the NAS, an L2F_CONF indicates the tunnel server's recognition of the tunnel creation request.


DB-2497


Table 382

debug vpdn l2x-events Field Descriptions—NAS (continued)

Field

Descriptions

L2F Removing resend packet (type ...)

Removing the resend packet for the L2F management packet. There are two resend packets that have different meanings in different states of the tunnel.

L2F_OPEN received

L2F_OPEN management message was received, indicating that the tunnel server accepted the NAS configuration of an L2F tunnel.

L2F building nas2gw_mid0

L2F is building a tunnel between the NAS and the tunnel server, using the multiplex ID (MID) MID0.

%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up

Line protocol came up. Indicates whether the software processes that handle the line protocol regard the interface as usable.

L2F_OPEN received

L2F_OPEN management message was received, indicating that the tunnel server accepted the NAS configuration of an L2F tunnel.

L2F Got a MID management packet

MID management packets are used to communicate between the NAS and the tunnel server.

L2F MID synced NAS/HG Clid=7/15 Mid=1 L2F synchronized the client IDs on the NAS and the on Async6 tunnel server, respectively. A MID is assigned to identify this connection in the tunnel. Tunnel coming down


Line protocol came down. Indicates whether the software processes that handle the line protocol regard the interface as usable.

%LINK-5-CHANGED: Interface Async6, changed state to reset

Interface was marked as reset.

L2F_CLOSE received

NAS received a request to close the tunnel.

L2F Destroying mid

Connection identified by the MID is being taken down.

L2F Tunnel is going down!

Advisory message about impending tunnel shutdown.

L2F Initiating tunnel shutdown.

Tunnel shutdown has started.

L2F_CLOSE received

NAS received a request to close the tunnel.

L2F Got closing for tunnel

NAS began tunnel closing operations.

%LINK-3-UPDOWN: Interface Async6, changed state to down

Asynchronous interface was taken down.

L2F Closed tunnel structure

NAS closed the tunnel.

L2F Deleted inactive tunnel

Now-inactivated tunnel was deleted.


DB-2498

May 2008


Debugging Protocol-Specific Events on the Tunnel Server—Normal L2F Operations

The following is sample output from the debug vpdn l2x events command on a tunnel server when an L2F tunnel is created: Router# debug vpdn l2x events L2F_CONF received L2F Creating new tunnel for nas1 L2F Got a tunnel named nas1, responding L2F Open UDP socket to 172.21.9.25 L2F_OPEN received L2F Removing resend packet (type 1) L2F_OPEN received L2F Got a MID management packet %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up

The following is sample output from the debug vpdn l2x events command on a tunnel server when the L2F tunnel is brought down normally: Router# debug vpdn l2x events L2F_CLOSE received L2F Destroying mid L2F Removing resend packet (type 3) L2F Tunnel is going down! L2F Initiating tunnel shutdown. %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down L2F_CLOSE received L2F Got closing for tunnel L2F Removing resend packet L2F Removing resend packet L2F Closed tunnel structure L2F Closed tunnel structure L2F Deleted inactive tunnel %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to down


debug vpdn l2x-events Field Descriptions—Tunnel Server

Field

Description

Tunnel coming up

L2F_CONF received

L2F configuration is received from the NAS. When sent from a NAS to a tunnel server, the L2F_CONF is the initial packet in the conversation.

L2F Creating new tunnel for nas1

Tunnel named nas1 is being created.

L2F Got a tunnel named nas1, responding

Tunnel server is responding.

L2F Open UDP socket to 172.21.9.25

Opening a socket to the NAS IP address.

L2F_OPEN received

L2F_OPEN management message was received, indicating the NAS is opening an L2F tunnel.

L2F Removing resend packet (type 1)

Removing the resend packet for the L2F management packet. The two resend packet types have different meanings in different states of the tunnel.


DB-2499


Table 383

debug vpdn l2x-events Field Descriptions—Tunnel Server (continued)

Field

Description

L2F Got a MID management packet

L2F MID management packets are used to communicate between the NAS and the tunnel server.

%LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up

Tunnel server is bringing up virtual access interface 1 for the L2F tunnel.

%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up

Line protocol is up. The line can be used.

Tunnel coming down

L2F_CLOSE received

NAS or tunnel server received a request to close the tunnel.

L2F Destroying mid

Connection identified by the MID is being taken down.

L2F Removing resend packet (type 3)

Removing the resend packet for the L2F management packet. There are two resend packets that have different meanings in different states of the tunnel.

L2F Tunnel is going down!

Router is performing normal operations when a tunnel is coming down.

L2F Initiating tunnel shutdown. %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down

The virtual access interface is coming down.

L2F_CLOSE received

Router is performing normal cleanup operations when the tunnel is being brought down.

L2F Got closing for tunnel L2F Removing resend packet L2F Removing resend packet L2F Closed tunnel structure L2F Closed tunnel structure L2F Deleted inactive tunnel %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to down

Line protocol is down; virtual access interface 1 cannot be used.

Displaying L2TP Congestion Avoidance Settings

The following partial example of the debug vpdn l2x events command is useful for monitoring a network running the L2TP Congestion Avoidance feature. The report shows that the congestion window (CWND) window has been reset to 1 because of packet retransmissions: Router# . . . *Jul 15 *Jul 15 *Jul 15 *Jul 15

debug vpdn l2x events

19:02:57.963: 19:02:57.963: 19:02:57.963: 19:02:57.963:

Tnl Tnl Tnl Tnl

47100 47100 47100 47100

L2TP: L2TP: L2TP: L2TP:

Congestion Control event received is retransmission Congestion Window size, Cwnd 1 Slow Start threshold, Ssthresh 2 Remote Window size, 500


DB-2500

May 2008


*Jul 15 19:02:57.963: *Jul 15 19:03:01.607:

Tnl 47100 L2TP: Control channel retransmit delay set to 4 seconds Tnl 47100 L2TP: Update ns/nr, peer ns/nr 2/5, our ns/nr 5/2

The following partial example shows that traffic has been restarted with L2TP congestion avoidance throttling traffic: Router# debug vpdn l2x . . . *Jul 15 14:45:16.123: *Jul 15 14:45:16.123: *Jul 15 14:45:16.131: acknowledgement *Jul 15 14:45:16.131: *Jul 15 14:45:16.131: *Jul 15 14:45:16.131: *Jul 15 14:45:16.131:

events

Tnl 30597 L2TP: Control channel retransmit delay set to 2 seconds Tnl 30597 L2TP: Tunnel state change from idle to wait-ctl-reply Tnl 30597 L2TP: Congestion Control event received is positive Tnl Tnl Tnl Tnl

30597 30597 30597 30597

L2TP: L2TP: L2TP: L2TP:

Congestion Window size, Cwnd 2 Slow Start threshold, Ssthresh 500 Remote Window size, 500 Congestion Ctrl Mode is Slow Start

Table 384 briefly describes the sigificant fields shown in the displays. See RFC 2661 for more details about the information in the reports for L2TP congestion avoidance. Table 384

debug vpdn l2x-events Field Descriptions—L2TP Congestion Avoidance

Field

Description

Control channel retransmit delay set to ...

Indicates the current value set for the retransmit delay.

Tunnel state...

Indicates the tunnel’s current Control Connection State, per RFC 2661.

Congestion Control event received is...

Indicates the received congestion control event. •

Retransmission—Indicates packet retransmission has been detected in the resend queue.

•

Positive acknowledgement—Indicates that a packet was received and acknowledged by the peer tunnel endpoint.

Congestion Window size, Cwnd 2

Current size of the congestion window (Cwnd).

Slow Start threshold, Ssthresh 500

Current value of the slow start threshold (Ssthresh).

Remote Window size, 500

Size of the advertised receive window configured on the remote peer with the l2tp tunnel receive-window command.

Congestion Ctrl Mode is...

Indicates if the router is operating in Slow Start or Congestion Avoidance mode.

Update ns/nr, peer ns/nr 2/5, our ns/nr 5/2

See RFC 2661.

Debugging Errors on the NAS—L2F Error Conditions

The following is sample output from the debug vpdn error command on a NAS when the L2F tunnel is not set up: Router# debug vpdn error %LINEPROTO-5-UPDOWN: Line protocol on Interface Async1, changed state to down %LINK-5-CHANGED: Interface Async1, changed state to reset %LINK-3-UPDOWN: Interface Async1, changed state to down %LINK-3-UPDOWN: Interface Async1, changed state to up


DB-2501


%LINEPROTO-5-UPDOWN: Line protocol on Interface Async1, changed state to up VPDN tunnel management packet failed to authenticate VPDN tunnel management packet failed to authenticate


debug vpdn error Field Descriptions for the NAS

Field

Description


Line protocol on the asynchronous interface went down.

%LINK-5-CHANGED: Interface Async1, changed state to reset

Asynchronous interface 1 was reset.

%LINK-3-UPDOWN: Interface Async1, changed state to down

Link from asynchronous interface 1 link went down and then came back up.

%LINK-3-UPDOWN: Interface Async1, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface Async1, changed state to up

Line protocol on the asynchronous interface came back up.

VPDN tunnel management packet failed to authenticate

Tunnel authentication failed. This is the most common VPDN error. Note

Verify the password for the NAS and the tunnel server name.

If you store the password on an AAA server, you can use the debug aaa authentication command. The following is sample output from the debug vpdn l2x errors command: Router# debug vpdn l2x errors %LINK-3-UPDOWN: Interface Async1, changed state to up L2F Out of sequence packet 0 (expecting 0) L2F Tunnel authentication succeeded for cisco.com L2F Received a close request for a non-existent mid L2F Out of sequence packet 0 (expecting 0) L2F packet has bogus1 key 1020868 D248BA0F L2F packet has bogus1 key 1020868 D248BA0F


debug vpdn l2x-errors Field Descriptions

Field

Description


The line protocol on the asynchronous interface came up.

L2F Out of sequence packet 0 (expecting 0)

Packet was expected to be the first in a sequence starting at 0, but an invalid sequence number was received.

L2F Tunnel authentication succeeded for cisco.com

Tunnel was established from the NAS to the tunnel server, cisco.com.


DB-2502

May 2008


Table 386

debug vpdn l2x-errors Field Descriptions (continued)

Field

Description

L2F Received a close request for Multiplex ID was not used previously; cannot close the tunnel. a non-existent mid L2F Out of sequence packet 0 (expecting 0)

Packet was expected to be the first in a sequence starting at 0, but an invalid sequence number was received.

L2F packet has bogus1 key 1020868 D248BA0F

Value based on the authentication response given to the peer during tunnel creation. This packet, in which the key does not match the expected value, must be discarded.

L2F packet has bogus1 key 1020868 D248BA0F

Another packet was received with an invalid key value. The packet must be discarded.

Debugging L2F Control Packets for Complete Information

The following is sample output from the debug vpdn l2x packets command on a NAS. This example displays a trace for a ping command. Router# debug vpdn l2x packets L2F SENDING (17): D0 1 1 10 0 0 0 4 0 11 0 0 81 94 E1 A0 4 L2F header flags: 53249 version 53249 protocol 1 sequence 16 mid 0 cid 4 length 17 offset 0 key 1701976070 L2F RECEIVED (17): D0 1 1 10 0 0 0 4 0 11 0 0 65 72 18 6 5 L2F SENDING (17): D0 1 1 11 0 0 0 4 0 11 0 0 81 94 E1 A0 4 L2F header flags: 53249 version 53249 protocol 1 sequence 17 mid 0 cid 4 length 17 offset 0 key 1701976070 L2F RECEIVED (17): D0 1 1 11 0 0 0 4 0 11 0 0 65 72 18 6 5 L2F header flags: 57345 version 57345 protocol 2 sequence 0 mid 1 cid 4 length 32 offset 0 key 1701976070 L2F-IN Output to Async1 (16): FF 3 C0 21 9 F 0 C 0 1D 41 AD FF 11 46 87 L2F-OUT (16): FF 3 C0 21 A F 0 C 0 1A C9 BD FF 11 46 87 L2F header flags: 49153 version 49153 protocol 2 sequence 0 mid 1 cid 4 length 32 offset 0 key -2120949344 L2F-OUT (101): 21 45 0 0 64 0 10 0 0 FF 1 B9 85 1 0 0 3 1 0 0 1 8 0 62 B1 0 0 C A8 0 0 0 0 0 11 E E0 AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD L2F header flags: 49153 version 49153 protocol 2 sequence 0 mid 1 cid 4 length 120 offset 3 key -2120949344 L2F header flags: 49153 version 49153 protocol 2 sequence 0 mid 1 cid 4 length 120 offset 3 key 1701976070 L2F-IN Output to Async1 (101): 21 45 0 0 64 0 10 0 0 FF 1 B9 85 1 0 0 1 1 0 0 3 0 0 6A B1 0 0 C A8 0 0 0 0 0 11 E E0 AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD AB CD


debug vpdn l2x-packets Field Descriptions

Field

Description

L2F SENDING (17)

Number of bytes being sent. The first set of “SENDING”...“RECEIVED” lines displays L2F keepalive traffic. The second set displays L2F management data.

L2F header flags:

Version and flags, in decimal.


DB-2503


Table 387

debug vpdn l2x-packets Field Descriptions (continued)

Field

Description

version 53249

Version.

protocol 1

Protocol for negotiation of the point-to-point link between the NAS and the tunnel server is always 1, indicating L2F management.

sequence 16

Sequence numbers start at 0. Each subsequent packet is sent with the next increment of the sequence number. The sequence number is thus a free running counter represented modulo 256. There is a distinct sequence counter for each distinct MID value.

mid 0

MID, which identifies a particular connection within the tunnel. Each new connection is assigned a MID currently unused within the tunnel.

cid 4

Client ID used to assist endpoints in demultiplexing tunnels.

length 17

Size in octets of the entire packet, including header, all fields pre-sent, and payload. Length does not reflect the addition of the checksum, if pre-sent.

offset 0

Number of bytes past the L2F header at which the payload data is expected to start. If it is 0, the first byte following the last byte of the L2F header is the first byte of payload data.

key 1701976070

Value based on the authentication response given to the peer during tunnel creation. During the life of a session, the key value serves to resist attacks based on spoofing. If a packet is received in which the key does not match the expected value, the packet must be silently discarded.

L2F RECEIVED (17)

Number of bytes received.

L2F-IN Otput to Async1 (16)

Payload datagram. The data came in to the VPDN code.

L2F-OUT (16):

Payload datagram sent out from the VPDN code to the tunnel.

L2F-OUT (101)

Ping payload datagram. The value 62 in this line is the ping packet size in hexadecimal (98 in decimal). The three lines that follow this line show ping packet data.

Debugging an L2TPv3 Xconnect Session—Normal Operations

The following example shows output from the debug vpdn l2x events command for an L2TP version 3 (L2TPv3) xconnect session on an Ethernet interface: Router# debug vpdn l2x events 23:31:18: L2X: l2tun session [1669204400], event [client request], old state [open], new state [open] 23:31:18: L2X: L2TP: Received L2TUN message 23:31:18: Tnl/Sn58458/28568 L2TP: Session state change from idle to wait-for-tunnel 23:31:18: Tnl/Sn58458/28568 L2TP: Create session 23:31:18: Tnl58458 L2TP: SM State idle 23:31:18: Tnl58458 L2TP: O SCCRQ 23:31:18: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds 23:31:18: Tnl58458 L2TP: Tunnel state change from idle to wait-ctl-reply 23:31:18: Tnl58458 L2TP: SM State wait-ctl-reply 23:31:18: Tnl58458 L2TP: I SCCRP from router 23:31:18: Tnl58458 L2TP: Tunnel state change from wait-ctl-reply to established 23:31:18: Tnl58458 L2TP: O SCCCN to router tnlid 8012


DB-2504

May 2008


23:31:18: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds 23:31:18: Tnl58458 L2TP: SM State established 23:31:18: Tnl/Sn58458/28568 L2TP: O ICRQ to router 8012/0 23:31:18: Tnl/Sn58458/28568 L2TP: Session state change from wait-for-tunnel to wait-reply 23:31:19: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds 23:31:20: %LINK-3-UPDOWN: Interface Ethernet2/1, changed state to up 23:31:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet2/1, changed state to up 23:31:25: L2X: Sending L2TUN message 23:31:25: Tnl/Sn58458/28568 L2TP: O ICCN to router 8012/35149 23:31:25: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds 23:31:25: Tnl/Sn58458/28568 L2TP: Session state change from wait-reply to established 23:31:25: L2X: l2tun session [1669204400], event [server response], old state [open], new state [open] 23:31:26: Tnl58458 L2TP: Control channel retransmit delay set to 1 seconds

Debugging Control Channel Authentication Events

The following debug messages show control channel authentication failure events in Cisco IOS Release 12.0(31)S: Router# debug vpdn l2x events ! Tnl41855 L2TP: Per-Tunnel auth counter, Overall Failed, now 1 Tnl41855 L2TP: Tunnel auth counter, Overall Failed, now 219 !

Related Commands

Command

Description



debug acircuit

Displays events and failures related to attachment circuits.

debug pppoe

Display debugging information for PPPoE sessions.




Displays PPPoE protocol errors that prevent a session from being established or errors that cause an established sessions to be closed.





debug xconnect

Displays errors and events related to an xconnect configuration.


DB-2505

Debug Commands debug vpm all

debug vpm all To enable all voice port module (VPM) debugging, use the debug vpm all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm all no debug vpm all

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

11.3(1)T

This command was introduced for the Cisco 3600 series.

12.0(7)XK

This command was updated for the Cisco 2600, Cisco 3600, and Cisco MC3810 series devices.

12.1(2)T


12.2SX


Usage Guidelines

Use the debug vpm all command to enable the complete set of VPM debugging commands: debug vpm dsp, debug vpm error, debug vpm port, debug vpm spi, and debug vpm trunk_sc. Execution of no debug all will turn off all port level debugging. It is usually a good idea to turn off all debugging and then enter the debug commands you are interested in one by one. This will help to avoid confusion about which ports you are actually debugging.

Examples

For sample outputs, refer to the documentation of the other debup vpm commands.

Related Commands

Command

Description

debug vpm port

Limits the debug vpm all command to a specified port.

show debug


debug vpm error

Enables DSP error tracing.

debug vpm voaal2 all

Enables the display of trunk conditioning supervisory component trace information.


DB-2506

May 2008

Debug Commands debug vpm dsp

debug vpm dsp To show messages from the digital signal processor (DSP) on the voice port module VPM) to the router, use the debug vpm dsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm dsp no debug vpm dsp

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug vpm dsp command shows messages from the DSP on the VPM to the router; this command can be useful if you suspect that the VPM is not functional. It is a simple way to check if the VPM is responding to off-hook indications and to evaluate timing for signaling messages from the interface.

Examples

The following output shows the DSP time stamp and the router time stamp for each event. For SIG_STATUS, the state value shows the state of the ABCD bits in the signaling message. This sample shows a call coming in on an FXO interface. The router waits for ringing to terminate before accepting the call. State=0x0 indicates ringing; state 0x4 indicates not ringing. ssm_dsp_message: SEND/RESP_SIG_STATUS: state=0x0 timestamp=58172 systime=40024 ssm_dsp_message: SEND/RESP_SIG_STATUS: state=0x4 timestamp=59472 systime=40154 ssm_dsp_message: SEND/RESP_SIG_STATUS: state=0x4 timestamp=59589 systime=40166

The following output shows the digits collected: vcsm_dsp_message: vcsm_dsp_message: vcsm_dsp_message: vcsm_dsp_message: vcsm_dsp_message:

MSG_TX_DTMF_DIGIT: MSG_TX_DTMF_DIGIT: MSG_TX_DTMF_DIGIT: MSG_TX_DTMF_DIGIT: MSG_TX_DTMF_DIGIT:

digit=4 digit=1 digit=0 digit=0 digit=0

This shows the disconnect indication and the final call statistics reported by the DSP (which are then populated in the call history table): ssm_dsp_message: SEND/RESP_SIG_STATUS: state=0xC timestamp=21214 systime=42882 vcsm_dsp_message: MSG_TX_GET_TX_STAT: num_tx_pkts=1019 num_signaling_pkts=0 num_comfort_noise_pkts=0 transmit_durtation=24150 voice_transmit_duration=20380 fax_transmit_duration=0


DB-2507

Debug Commands debug vpm error

debug vpm error To enable digital signal processor (DSP) error tracing in voice port modules (VPMs), use the debug vpm error command in privileged EXEC mode. To disable DSP error tracing, use the no form of this command. debug vpm error no debug vpm error

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK

This command was introduced on the Cisco 2600, 3600, and MC3810 series devices.

12.1(2)T


12.2SX


Usage Guidelines

Execution of no debug all will turn off all port level debugging. You should turn off all debugging and then enter the debug commands you are interested in one by one. This will help avoid confusion about which ports you are actually debugging.

Examples

The following example shows debug vpm error messages for Cisco 2600 or Cisco 3600 series router or a Cisco MC3810 series concentrator: Router# debug vpm error 00:18:37:[1:0.1, FXSLS_NULL, E_DSP_SIG_0100] -> ERROR:INVALID INPUT Router#

The following example turns off debug vpm error debugging messages: Router# no debug vpm error

Related Commands

Command

Description

debug vpm all

Enables all VPM debugging.


DB-2508

May 2008

Debug Commands debug vpm error

debug vpm port

Limits the debug vpm error command to a specified port.

show debug



DB-2509

Debug Commands debug vpm port

debug vpm port To observe the behavior of the Holst state machine, use the debug vpm port command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm port [slot-number| subunit-number | port] no debug vpm port [slot-number | subunit-number | port]

Syntax Description

slot-number

(Optional) Specifies the slot number in the Cisco router where the voice interface card is installed. Valid entries are from 0 to 3, depending on the router being used and the slot where the voice interface card has been installed.

subunit-number

(Optional) Specifies the subunit on the voice interface card where the voice port is located. Valid entries are 0 or 1.

port

(Optional) Specifies the voice port. Valid entries are 0 or 1.

Command Modes

Privileged EXEC

Command History

Release

Usage Guidelines

Modification

11.3(1)


12.2SX


This command is not supported on Cisco 7200 series routers or on the Cisco MC3810. Use this command to limit the debug output to a particular port. The debug output can be quite voluminous for a single channel. A 12-port box might create problems. Use this debug command with any or all of the other debug modes. Execution of no debug vpm all will turn off all port level debugging. We recommend that you turn off all debugging and then enter the debug commands you are interested in one by one. This process helps to avoid confusion about which ports you are actually debugging.

Examples

The following is sample output from the debug vpm port 1/1/0 command during trunk establishment after the no shutdown command has been executed on the voice port: Router# debug vpm port 1/1/0 *Mar 1 03:21:39.799: htsp_process_event: [1/1/0, 0.1 , 2]act_down_inserve *Mar 1 03:21:39.807: htsp_process_event: [1/1/0, 0.0 , 14] act_go_trunkhtsp_trunk_createhtsp_trunk_sig_linkfxols_trunk *Mar 1 03:21:39.807: htsp_process_event: [1/1/0, 1.0 , 1]trunk_offhookfxols_trunk_down *Mar 1 03:21:39.807: dsp_sig_encap_config: [1/1/0] packet_len=28 channel_id=128 packet_id=42 transport_protocol=1 playout_delay=100 signaling_mode=0 t_ssrc=0 r_ssrc=0 t_vpxcc=0 r_vpxcc=0 *Mar 1 03:21:39.811: dsp_set_sig_state: [1/1/0] packet_len=12


DB-2510

May 2008

Debug Commands debug vpm port

channel_id=128 packet_id=39 state=0xC timestamp=0x0 *Mar 1 03:21:39.811: trunk_offhook: Trunk Retry Timer Enabled *Mar 1 03:22:13.095: htsp_process_event: [1/1/0, 1.1, 39]act_trunk_setuphtsp_setup_ind *Mar 1 03:22:13.095: htsp_process_event: [1/1/0, 1.2 , 8] *Mar 1 03:22:13.099: hdsprm_vtsp_codec_loaded_ok: G726 firmware needs download *Mar 1 03:22:13.103: dsp_download: p=0x60E73844 size=34182 (t=1213310):39 FA 6D *Mar 1 03:22:13.103: htsp_process_event: [1/1/0, 1.2 , 6]act_trunk_proc_connect *Mar 1 03:22:13.191: dsp_receive_packet: MSG_TX_RESTART_INDICATION: code=0 t=1213319 *Mar 1 03:22:13.191: dsp_download: p=0x60EA8924 size=6224 (t=1213319): 8 55 AE *Mar 1 03:22:13.207: dsp_receive_packet: MSG_TX_RESTART_INDICATION: code=0 t=1213320 *Mar 1 03:22:13.207: htsp_process_event: [1/1/0, 1.3 , 11] trunk_upfxols_trunk_up *Mar 1 03:22:13.207: dsp_set_sig_state: [1/1/0] packet_len=12 channel_id=128 packet_id=39 state=0x4 timestamp=0x0 *Mar 1 03:22:13.207: dsp_sig_encap_config: [1/1/0] packet_len=28 channel_id=128 packet_id=42 transport_protocol=3 playout_delay=100 headerbytes = 0xA0

Note in the above display that “transport_protocol = 3” indicates Voice-over-Frame Relay. Also note that the second line of the display indicates that a shutdown/no shutdown command sequence was executed on the voice port.

Related Commands

Command

Description


Enables debugging of all VPM areas.

debug vpm dsp

Shows messages from the DSP on the VPM to the router.

debug vpm signal

Collects debug information only for signaling events.

debug vpm spi

Displays information about how each network indication and application request is handled.


DB-2511

Debug Commands debug vpm signal

debug vpm signal To collect debug information only for signaling events, use the debug vpm signal command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm signal no debug vpm signal

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug vpm signal command collects debug information only for signaling events. This command can also be useful in resolving problems with signaling to a PBX.

Examples

The following output shows that a ring is detected, and that the router waits for the ringing to stop before accepting the call: ssm_process_event: ssm_process_event: ssm_process_event: ssm_process_event:

[1/0/1, [1/0/1, [1/0/1, [1/0/1,

0.2, 0.7, 0.3, 0.3,

15] fxols_onhook_ringing 19] fxols_ringing_not 6] 19] fxols_offhook_clear

The following output shows that the call is connected: ssm_process_event: [1/0/1, 0.3, 4] fxols_offhook_proc ssm_process_event: [1/0/1, 0.3, 8] fxols_proc_voice ssm_process_event: [1/0/1, 0.3, 5] fxols_offhook_connect

The following output confirms a disconnect from the switch and release with higher layer code: ssm_process_event: [1/0/1, 0.4, 27] fxols_offhook_disc ssm_process_event: [1/0/1, 0.4, 33] fxols_disc_confirm ssm_process_event: [1/0/1, 0.4, 3] fxols_offhook_release


DB-2512

May 2008

Debug Commands debug vpm signaling

debug vpm signaling To see information about the voice port module signaling, use the debug vpm signaling command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm signaling no debug vpm signaling

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK


12.1(2)T

This command was integrated into Release 12.1(2)T.

12.2SX


Examples

The following is sample output from the debug vpm signaling command: Router# debug vpm signaling 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55: 01:52:55:

[1:1.1, S_TRUNK_BUSYOUT, E_HTSP_OUT_BUSYOUT] htsp_timer - 0 msec [1:1.1, S_TRUNK_PEND, E_HTSP_EVENT_TIMER] htsp_timer_stop htsp_setup_ind htsp_timer - 2000 msec [1:1.1, S_TRUNK_PROC, E_HTSP_SETUP_ACK] htsp_timer_stop htsp_timer - 20000 msec [1:6.6, S_TRUNK_PROC, E_HTSP_SETUP_ACK] htsp_timer_stop htsp_timer - 20000 msec [1:1.1, S_TRUNK_PROC, E_HTSP_VOICE_CUT_THROUGH] %HTSP-5-UPDOWN: Trunk port(channel) [1:1.1] is up


DB-2513

Debug Commands debug vpm spi

debug vpm spi To trace how the voice port module security parameter index (SPI) interfaces with the call control application programming interface (API), use the debug vpm spi command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm spi no debug vpm spi

Syntax Description


Command Modes

Privileged EXEC

Usage Guidelines

The debug vpm spi command traces how the voice port module SPI interfaces with the call control API. This debug command displays information about how each network indication and application request is handled. This debug level shows the internal workings of the voice telephony call state machine.

Examples

The following output shows that the call is accepted and presented to a higher layer code: dsp_set_sig_state: [1/0/1] packet_len=14 channel_id=129 packet_id=39 state=0xC timestamp=0x0 vcsm_process_event: [1/0/1, 0.5, 1] act_up_setup_ind

The following output shows that the higher layer code accepts the call, requests addressing information, and starts DTMF and dial-pulse collection. It also shows that the digit timer is started. vcsm_process_event: [1/0/1, 0.6, 11] act_setup_ind_ack dsp_voice_mode: [1/0/1] packet_len=22 channel_id=1 packet_id=73 coding_type=1 voice_field_size=160 VAD_flag=0 echo_length=128 comfort_noise=1 fax_detect=1 dsp_dtmf_mode: [1/0/1] packet_len=12 channel_id=1 packet_id=65 dtmf_or_mf=0 dsp_CP_tone_on: [1/0/1] packet_len=32 channel_id=1 packet_id=72 tone_id=3 n_freq=2 freq_of_first=350 freq_of_second=440 amp_of_first=4000 amp_of_second=4000 direction=1 on_time_first=65535 off_time_first=0 on_time_second=65535 off_time_second=0 dsp_digit_collect_on: [1/0/1] packet_len=22 channel_id=129 packet_id=35 min_inter_delay=550 max_inter_delay=3200 mim_make_time=18 max_make_time=75 min_brake_time=18 max_brake_time=75 vcsm_timer: 46653

The following output shows the collection of digits one by one until the higher level code indicates it has enough. The input timer is restarted with each digit and the device waits in idle mode for connection to proceed. vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digit dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71 vcsm_timer: 47055 vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digit dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71 vcsm_timer: 47079 vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digit dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71


DB-2514

May 2008

Debug Commands debug vpm spi

vcsm_timer: 47173 vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digit dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71 vcsm_timer: 47197 vcsm_process_event: [1/0/1, 0.7, 25] act_dcollect_digit dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71 vcsm_timer: 47217 vcsm_process_event: [1/0/1, 0.7, 13] act_dcollect_proc dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71 dsp_digit_collect_off: [1/0/1] packet_len=10 channel_id=129 packet_id=36 dsp_idle_mode: [1/0/1] packet_len=10 channel_id=1 packet_id=68

The following output shows that the network voice path cuts through: vcsm_process_event: [1/0/1, 0.8, 15] act_bridge vcsm_process_event: [1/0/1, 0.8, 20] act_caps_ind vcsm_process_event: [1/0/1, 0.8, 21] act_caps_ack dsp_voice_mode: [1/0/1] packet_len=22 channel_id=1 packet_id=73 coding_type=6 voice_field_size=20 VAD_flag=1 echo_length=128 comfort_noise=1 fax_detect=1

The following output shows that the called-party end of the connection is connected: vcsm_process_event: [1/0/1, 0.8, 8] act_connect

The following output shows the voice quality statistics collected periodically: vcsm_process_event: [1/0/1, 0.13, 17] dsp_get_rx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=87 reset_flag=0 vcsm_process_event: [1/0/1, 0.13, 28] vcsm_process_event: [1/0/1, 0.13, 29] vcsm_process_event: [1/0/1, 0.13, 32] vcsm_process_event: [1/0/1, 0.13, 17] dsp_get_rx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=87 reset_flag=0 vcsm_process_event: [1/0/1, 0.13, 28] vcsm_process_event: [1/0/1, 0.13, 29] vcsm_process_event: [1/0/1, 0.13, 32] vcsm_process_event: [1/0/1, 0.13, 17] dsp_get_rx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=87 reset_flag=0 vcsm_process_event: [1/0/1, 0.13, 28] vcsm_process_event: [1/0/1, 0.13, 29] vcsm_process_event: [1/0/1, 0.13, 32]

The following output shows that the disconnection indication is passed to higher-level code. The call connection is torn down, and final call statistics are collected: vcsm_process_event: [1/0/1, 0.13, 4] act_generate_disc vcsm_process_event: [1/0/1, 0.13, 16] act_bdrop dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71 vcsm_process_event: [1/0/1, 0.13, 18] act_disconnect dsp_get_levels: [1/0/1] packet_len=10 channel_id=1 packet_id=89 vcsm_timer: 48762 vcsm_process_event: [1/0/1, 0.15, 34] act_get_levels dsp_get_tx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=86 reset_flag=1 vcsm_process_event: [1/0/1, 0.15, 31] act_stats_complete dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71 dsp_digit_collect_off: [1/0/1] packet_len=10 channel_id=129 packet_id=36 dsp_idle_mode: [1/0/1] packet_len=10 channel_id=1 packet_id=68 vcsm_timer: 48762 dsp_set_sig_state: [1/0/1] packet_len=14 channel_id=129 packet_id=39 state=0x4 timestamp=0x0 vcsm_process_event: [1/0/1, 0.16, 5] act_wrelease_release dsp_CP_tone_off: [1/0/1] packet_len=10 channel_id=1 packet_id=71 dsp_idle_mode: [1/0/1] packet_len=10 channel_id=1 packet_id=68 dsp_get_rx_stats: [1/0/1] packet_len=12 channel_id=1 packet_id=87 reset_flag=1


DB-2515

Debug Commands debug vpm trunk_sc

debug vpm trunk_sc To enable the display of trunk conditioning supervisory component trace information, use the debug vpm trunk_sc command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm trunk_sc no debug vpm trunk_sc

Syntax Description


Defaults

Trunk conditioning supervisory component trace information is not displayed.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK

This command was introduced on the Cisco 2600, Cisco 3600, and Cisco MC3810 series devices.

12.1(2)T


12.2SX


Usage Guidelines

Use the debug vpm port command with the slot-number/subunit-number/port argument to limit the debug vpm trunk_sc debug output to a particular port. If you do not use the debug vpm port command, the debug vpm trunk_sc displays output for all ports. Execution of the no debug all command will turn off all port level debugging. It is usually a good idea to turn off all debugging and then enter the debug commands you are interested in one by one. This process helps avoid confusion about which ports you are actually debugging.

Examples

The following example shows debug vpm trunk_sc messages for port 1/0/0 on a Cisco 2600 or Cisco 3600 series router: Router# debug vpm trunk_sc Router# debug vpm port 1/0/0

The following example shows debug vpm trunk_sc messages for port 1/1 on a Cisco MC3810 device: Router# debug vpm trunk_sc Router# debug vpm port 1/1


DB-2516

May 2008

Debug Commands debug vpm trunk_sc

The following example turns off debug vpm trunk_sc debugging messages: Router# no debug vpm trunk_sc

Related Commands

Command

Description

debug vpm all

Enables all VPM debugging

debug vpm port

Limits the debug vpm trunk_sc command to a specified port.

show debug



DB-2517

Debug Commands debug vpm voaal2 all

debug vpm voaal2 all To display type 1 (voice) and type 3 (control) ATM Adaptation Layer type 2 (AAL2) packets sent to and received from the domain-specific part (DSP), use the debug vpm voaal2 all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm voaal2 all {all_dsp | from_dsp | to_dsp} no debug vpm voaal2 all

Syntax Description

all_dsp

Displays messages to and from the DSP.

from_dsp

Displays messages from the DSP.

to_dsp

Displays messages to the DSP.

Defaults

Debugging for display of AAL2 packets is not enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)XA


12.1(2)T


12.2(2)T

Support for this command was integrated on the Cisco 7200 series.

12.2SX


Usage Guidelines

Do not enter this debug command on a system carrying live traffic. Continuous display of AAL2 type 1 (voice) packets results in high CPU utilization and loss of console access to the system. Calls will be dropped and trunks may go down. For AAL2 debugging, use the debug vpm voaal2 type3 debug command and identify a specific type 3 (control) packet type.

Examples

The following is sample output from the debug vpm voaal2 all command, where the example selection is to display channel-associated switching (CAS) packets sent to and from the DSP: Router# debug vpm voaal2 all all_dsp *Jan 9 20:10:36.965:TYPE 3, len = 8, cid = 34, uui = 24 :TO_DSP *Jan 9 20:10:36.965:CAS redundancy = 3, timestamp = 10270, signal = 0 - 22 13 12 E8 1E 0 E 15 *Jan 9 20:10:41.617:TYPE 3, len = 8, cid = 34, uui = 24 :FROM_DSP *Jan 9 20:10:41.617:CAS redundancy = 3, timestamp = 980, signal = 0


DB-2518

May 2008

Debug Commands debug vpm voaal2 all

- 22 13 12 C3 D4 0 F 87 *Jan 9 20:10:41.965:TYPE 3, len = 8, cid = 34, uui = 24 :TO_DSP *Jan 9 20:10:41.965:CAS redundancy = 3, timestamp = 10270, signal = 0 - 22 13 12 E8 1E 0 E 15 *Jan 9 20:10:46.621:TYPE 3, len = 8, cid = 34, uui = 24 :FROM_DSP *Jan 9 20:10:46.621:CAS redundancy = 3, timestamp = 980, signal = 0 - 22 13 12 C3 D4 0 F 87 .... *Jan 9 20:10:57.101:TYPE 1, len = 43, cid = 34, uui = 8- 22 9D 1 CC FC C7 3E 22 23 FE DF F8 DE 1C FF E5 12 22 43 EC 2E 9E CC DE A7 EF 14 E3 F1 2C 2D BC 1B FC FE D7 E1 1F 2F ED 11 FC 1F *Jan 9 20:10:57.105:TYPE 3, len = 9, cid = 34, uui = 24 :FROM_DSP *Jan 9 20:10:57.105:DIALED DIGITS redundancy = 0, timestamp = 940, digitcode = 1 - 22 17 3 3 AC 1 1 8 E5 *Jan 9 20:10:57.113:TYPE 1, len = 43, cid = 34, uui = 10- 22 9D 4B 3F 1F 11 FC CD CC BE B7 E2 F3 32 2E 1F F9 DA CC BF 12 F1 37 31 11 2C FE 9D DA D2 E1 C7 4A 34 3F FA 21 AD CC 1F EE 16 E1 *Jan 9 20:10:57.113:TYPE 3, len = 9, cid = 34, uui = 24 :FROM_DSP *Jan 9 20:10:57.113:DIALED DIGITS redundancy = 1, timestamp = 940, digitcode = 1 - 22 17 3 43 AC 1 1 B 12 *Jan 9 20:10:57.121:TYPE 1, len = 43, cid = 34, uui = 12- 22 9D 95 F1 1E E1 DF 1E 21 31 21 1D D9 EB BB DF 22 17 13 12 1F 58 FF ED ED E1 4D B7 3E 3F 21 F3 8E FD EF DF F4 12 E4 32 FE B4 D8 -

Related Commands

Command

Description

debug vpm voaal2 type1

Displays type 1 (voice) AAL2 packets sent to and received from the DSP.


Displays type 3 (control) AAL2 packets sent to and received from the DSP.

show debug



DB-2519

Debug Commands debug vpm voaal2 type1

debug vpm voaal2 type1 To display type 1 (voice) ATM Adaptation Layer type 2 (AAL2) packets sent to and received from the domain-specific part (DSP), use the debug vpm voaal2 type1 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm voaal2 type1 {all_dsp | from_dsp | to_dsp} no debug vpm voaal2 type1

Syntax Description

all_dsp


from_dsp


to_dsp


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)XA


12.1(2)T


12.2(2)T

Support for this command was implemented on the Cisco 7200 series.

12.2SX


Usage Guidelines

Do not enter this debug command on a system carrying live traffic. Continuous display of AAL2 type 1 (voice) packets results in high CPU utilization and loss of console access to the system. Calls will be dropped and trunks may go down. For AAL2 debugging, use the debug vpm voaal2 type 3 command and identify a specific type 3 (control) packet type.

Examples

The following is sample output from the debug vpm voaal2 type1 command:

Note

The display of voice packets on a live system will continue indefinitely. The debugging output cannot be interrupted, because console access will be lost. Router# debug vpm voaal2 type1 all_dsp TYPE 1, len = 43, cid = 17, uui = 15- 11 9D E6 1B 52 9D 95 9B DB 1D 14 1C 5F 9C 95 9C EA 1C 15 1B 74 9C 94 9D 6B 1C 14 1D E4 9B 94 9D 5B 1B 14


DB-2520

May 2008


1D D7 9B 94 9D 50 1B 14 TYPE 1, len = 43, cid = 22, uui = 15- 16 9D ED 1D 14 1B 53 9D 94 9C DB 1D 14 1C 5F 9C 95 9C EB 1C 14 1C 78 9D 94 9D 6F 1C 14 1E E4 9B 94 9D 5B 1B 14 1D D7 9B 94 9E 52 TYPE 1, len = 43, cid = 12, uui = 14- C 9D D1 29 AB 96 96 A9 2B 16 16 2A AA 96 96 AB 2A 16 17 2B A9 96 97 AC 28 16 17 2C A8 96 97 AD 27 15 17 2E A7 97 97 AE 26 16 17 TYPE 1, len = 43, cid = 34, uui = 14- 22 9D DF D7 31 20 19 15 14 15 19 1E 2C 60 AF 9F 99 96 94 95 99 9F AD EC 2F 1F 1A 15 14 15 19 1F 2E ED AD 9F 99 96 93 95 99 9F AF TYPE 1, len = 43, cid = 12, uui = 15- C 9D F4 2F A5 96 97 AF 25 15 18 31 A4 95 98 B3 23 15 18 33 A3 95 98 B5 22 15 18 37 A2 95 98 B7 21 15 18 39 A0 95 99 BB 21 14 19 TYPE 1, len = 43, cid = 34, uui = 15- 22 9D FA 5D 2D 1E 19 15 14 15 1A 21 31 D9 AC 9E 98 95 94 95 9A A4 B3 52 2B 1D 18 14 14 16 1B 22 36 CA AA 9D 98 94 94 96 9B A4 B6 -

Related Commands

Command

Description

debug vpm all


debug vpm voaal2 all

Displays type 1 (voice) and type 3 (control) AAL2 packets sent to and received from the DSP.



show debug



DB-2521


debug vpm voaal2 type3 To display type 3 (control) ATM Adaptation Layer type 2 (AAL2) packets sent to and received from the domain-specific part (DSP), use the debug vpm voaal2 type3 command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vpm voaal2 type3 {alarms | alltype3 | cas | dialed | faxrelay | state}{all_dsp | from_dsp | to_dsp} no debug vpm voaal2 type3

Syntax Description

alarms

Displays type 3 alarm packets.

alltype3

Displays all type 3 packets.

cas

Displays type 3 channel-associated switching (CAS) packets.

dialed

Displays type 3 dialed digit packets.

faxrelay

(Not supported) Displays type 3 fax relay packets.

state

Displays type 3 user state packets.

all_dsp


from_dsp


to_dsp


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(1)XA


12.1(2)T


12.2(2)T

Support for this command was implemented on the Cisco 7200 series.

12.2SX


Usage Guidelines

This is the preferred debug command for displaying specific types of control packets. It is usually preferable to specify a particular type of control packet rather than use the alltype3 to avoid excessive output display and CPU utilization.

Examples

The following is sample output from the debug vpm voaal2 type3 command, where the example selection is to display messages to and from the DSP:


DB-2522

May 2008


Router# debug vpm voaal2 type3 all_dsp 00:43:02:TYPE 3, len = 8, cid = 58, uui = 24 :TO_DSP 00:43:02:CAS redundancy = 3, timestamp = 10484, signal = 0 - 3A 13 18 E8 F4 0 C DA 00:43:02:TYPE 3, len = 8, cid = 93, uui = 24 :FROM_DSP 00:43:02:CAS redundancy = 3, timestamp = 6528, signal = 0 - 5D 13 1E D9 80 0 F 33 00:43:02:TYPE 3, len = 8, cid = 102, uui = 24 :FROM_DSP 00:43:02:CAS redundancy = 3, timestamp = 5988, signal = 0 - 66 13 4 D7 64 0 F DF 00:43:02:TYPE 3, len = 8, cid = 194, uui = 24 :FROM_DSP 00:43:02:CAS redundancy = 3, timestamp = 6212, signal = 0 - C2 13 10 D8 44 0 F AC 00:43:02:TYPE 3, len = TYPE 3, len = 8, cid = redundancy = 3, times - 5C 13 5 D9 E4 0 C 1F

8, cid = 92, uui = 24 :FROM_DSP 66, uui = 24 :TO_DSP:43:00:CAS signal = 0 -

00:43:02:TYPE 3, len = 8, cid = 40, uui = 24 :TO_DSP 00:43:02:CAS redundancy = 3, timestamp = 8658, signal = 0 - 28 13 7 E1 D2 0 E 79 00:43:02:TYPE 3, len = 8, cid = 137, uui = 24 :FROM_DSP 00:43:02:CAS redundancy = 3, timestamp = 6836, signal = 0 - 89 13 B DA B4 0 E 78 -

Related Commands

Command

Description


Displays type 1 (voice) AAL2 packets sent to and received from the DSP.



show debug



DB-2523

Debug Commands debug vrrp all

debug vrrp all To display debugging messages for Virtual Router Redundancy Protocol (VRRP) errors, events, and state transitions, use the debug vrrp all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vrrp all no debug vrrp all

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(18)ST


12.0(22)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2(31)SB2


12.2SX


Examples

The following is sample output for the debug vrrp all command: Router# debug vrrp all 00:15:30: %IP-4-DUPADDR: Duplicate address 10.18.0.2 on Ethernet1/0, sourced by 0000.5e00.0101 May 22 18:41:54.447: VRRP: Grp 1 Advertisement Primary address 10.18.0.2 different from ours 10.18.0.1 May 22 18:41:57.443: VRRP: Grp 1 Advertisement Primary address 10.18.0.2 different from ours 10.18.0.1 May 22 18:42:00.443: VRRP: Grp 1 Advertisement Primary address 10.18.0.2 different from ours 10.18.0.1 May 22 18:48:41.521: VRRP: Grp 1 Event - Advert higher or equal priority May 22 18:48:44.521: VRRP: Grp 1 Event - Advert higher or equal priority May 22 18:48:47.521: VRRP: Grp 1 Event - Advert higher or equal priority May 22 18:53:23.390: VRRP: Grp 1 changing to V_STATE_INIT May 22 18:54:26.143: VRRP: Grp 1 changing to V_STATE_BACKUP May 22 18:54:35.755: VRRP: Grp 1 changing to V_STATE_MASTER May 22 18:53:23.390: VRRP: Grp 1 changing to V_STATE_INIT May 22 18:54:26.143: VRRP: Grp 1 changing to V_STATE_BACKUP


DB-2524

May 2008

Debug Commands debug vrrp all

May 22 18:54:35.755: VRRP: Grp 1 changing to V_STATE_MASTER

Related Commands

Command

Description

debug vrrp error

Displays debugging messages about VRRP error conditions.

debug vrrp events

Displays debugging messages about VRRP events.

debug vrrp state

Displays debugging messages about the VRRP state transitions.


DB-2525

Debug Commands debug vrrp authentication

debug vrrp authentication To display debugging messages for Virtual Router Redundancy Protocol (VRRP) Message Digest 5 (MD5) authentication, use the debug vrrp authentication command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vrrp authentication no debug vrrp authentication

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(14)T


12.2SX


Examples

The following sample output shows that MD5 authentication is enabled on one router but not the other: Router# debug vrrp authentication VRRP: Grp 1 Advertisement from 172.24.1.1 has incorrect authentication type 0 expected 254

The following sample output shows that the MD5 key IDs and key strings differ on each router: Router# debug vrrp authentication VRRP: Grp 1 recalculate MD5 digest: "3n};oHp8_)_7-C" VRRP: Grp 1 received MD5 digest: "_M_^uMiWo^|t?t2m" VRRP: Grp 1 Advertisement from 172.24.1.1 has FAILED MD5 authentication

The following sample output shows that the text authentication strings differ on each router: Router# debug vrrp authentication VRRP: Grp 1 Advertisement from 172.24.1.1 has FAILED TEXT authentication

Related Commands

Command

Description

debug vrrp error


debug vrrp events


debug vrrp state



DB-2526

May 2008

Debug Commands debug vrrp error

debug vrrp error To display debugging messages about Virtual Router Redundancy Protocol (VRRP) error conditions, use the debug vrrp error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vrrp error no debug vrrp error

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(18)ST


12.0(22)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2(31)SB2


12.2SX


Examples

The following is sample output from the debug vrrp error command: Router# debug vrrp error 00:15:30: %IP-4-DUPADDR: Duplicate address 10.18.0.2 on Ethernet1/0, sourced by 0000.5e00.0101 May 22 18:41:54.447: VRRP: Grp 1 Advertisement Primary address 10.18.0.2 different from ours 10.18.0.1 May 22 18:41:57.443: VRRP: Grp 1 Advertisement Primary address 10.18.0.2 different from ours 10.18.0.1 May 22 18:42:00.443: VRRP: Grp 1 Advertisement Primary address 10.18.0.2 different from ours 10.18.0.1

In the example, the error being observed is that the router has a virtual address of 10.18.0.1 for group 1, but it received a virtual address of 10.18.0.2 for group 1 from another router on the same LAN.

Related Commands

Command

Description

debug vrrp all

Displays debugging messages for VRRP errors, events, and state transitions.


DB-2527

Debug Commands debug vrrp events

debug vrrp events To display debugging messages about Virtual Router Redundancy Protocol (VRRP) events that are occurring, use the debug vrrp events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vrrp events no debug vrrp events

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(18)ST


12.0(22)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2(31)SB2


12.2SX


Examples

The following is sample output from the debug vrrp events command: Router# debug vrrp events May 22 18:48:41.521: VRRP: Grp 1 Event - Advert higher or equal priority May 22 18:48:44.521: VRRP: Grp 1 Event - Advert higher or equal priority May 22 18:48:47.521: VRRP: Grp 1 Event - Advert higher or equal priority

In the example, the event being observed is that the router received an advertisement from another router for group 1 that has a higher or equal priority to itself.

Related Commands

Command

Description

debug vrrp all



DB-2528

May 2008

Debug Commands debug vrrp ha

debug vrrp ha To display debugging messages for Virtual Router Redundancy Protocol (VRRP) high availability, use the debug vrrp ha command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vrrp ha no debug vrrp ha

Syntax Description


Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.2(33)SRC


12.2(33)SB


Examples

The following examples for the debug vrrp ha command display the syncing of VRRP state information from the Active RP to the Standby RP. The following sample output displays two VRRP state changes on the Active RP: Router# . . . *Nov 14 *Nov 14 *Nov 14 *Nov 14

debug vrrp ha

11:36:50.272 11:36:50.272 11:36:53.884 11:36:53.884

UTC: UTC: UTC: UTC:

VRRP: Gi3/2 Grp 42 RF Encode state Backup into sync buffer %VRRP-6-STATECHANGE: Gi3/2 Grp 42 state Init -> Backup VRRP: Gi3/2 Grp 42 RF Encode state Master into sync buffer %VRRP-6-STATECHANGE: Gi3/2 Grp 42 state Backup -> Master

The following sample output displays two VRRP state changes on the Standby RP: Router# debug vrrp ha . . . *Nov 14 11:36:50.392 UTC: STDBY: VRRP: Gi3/2 Grp 42 RF sync state Init -> Backup *Nov 14 11:36:53.984 UTC: STDBY: VRRP: Gi3/2 Grp 42 RF sync state Backup -> Master

Related Commands

Command

Description

debug vrrp error


debug vrrp events


debug vrrp state



DB-2529

Debug Commands debug vrrp packets

debug vrrp packets To display summary information about Virtual Router Redundancy Protocol (VRRP) packets being sent or received, use the debug vrrp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vrrp packets no debug vrrp packets

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(18)ST


12.0(22)S


12.2(13)T


12.2(14)S


12.2SX


12.2(33)SRA


12.2(31)SB2


12.2SX


Examples

The following is sample output from the debug vrrp packets command. The output is on the master virtual router; the router for group 1 is sending an advertisement with a checksum of 6BE7. Router# debug vrrp packets VRRP Packets debugging is on May 22 18:51:03.220: VRRP: Grp 1 sending Advertisement checksum 6BE7 May 22 18:51:06.220: VRRP: Grp 1 sending Advertisement checksum 6BE7

In the following example, the router with physical address 10.18.0.3 is advertising a priority of 105 for VRRP group 1: Router# debug vrrp packets VRRP Packets debugging is on May 22 18:51:09.222: VRRP: Grp 1 Advertisement priority 105, ipaddr 10.18.0.3 May 22 18:51:12.222: VRRP: Grp 1 Advertisement priority 105, ipaddr 10.18.0.3


DB-2530

May 2008

Debug Commands debug vrrp state

debug vrrp state To display debugging messages about the state transitions occurring for Virtual Router Redundancy Protocol (VRRP) groups, use the debug vrrp state command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vrrp state no debug vrrp state

Syntax Description


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(18)ST


12.0(22)S


12.2(13)T


12.2(14)S


12.2(33)SRA


12.2(31)SB2


12.2SX


Examples

The following is sample output from the debug vrrp state command: Router# debug vrrp state May 22 18:53:23.390: VRRP: Grp 1 changing to V_STATE_INIT May 22 18:54:26.143: VRRP: Grp 1 changing to V_STATE_BACKUP May 22 18:54:35.755: VRRP: Grp 1 changing to V_STATE_MASTER

Related Commands

Command

Description

debug vrrp all



DB-2531

Debug Commands debug vsi api

debug vsi api To display information on events associated with the external ATM application programming interface (API) interface to the Virtual Switch Interface (VSI) master, use the debug vsi api command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vsi api no debug vsi api

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug vsi api command to monitor the communication between the VSI master and the XmplsATM component regarding interface changes and cross-connect requests.

Examples

The following is sample output from the debug vsi api command: Router# debug vsi api VSI_M: vsi_exatm_conn_req: 0x000C0200/1/35 -> 0x000C0100/1/50 desired state up, status OK VSI_M: vsi_exatm_conn_resp: 0x000C0200/1/33 -> 0x000C0100/1/49 curr state up, status OK


debug vsi api Command Field Descriptions

Field

Description

vsi_exatm_conn_req

The type of connection request (connect or disconnect) that was submitted to the VSI master.

0x000C0200

The logical interface identifier of the primary endpoint, in hexadecimal form.


DB-2532

May 2008

Debug Commands debug vsi api

Table 388

debug vsi api Command Field Descriptions (continued)

Field

Description

1/35

The virtual path identifier (VPI) and virtual channel identifier (VCI) of the primary endpoint.

->

The type of traffic flow. A right arrow (->) indicates unidirectional traffic flow (from the primary endpoint to the secondary endpoint). A bidirectional arrow () indicates bidirectional traffic flow.

0x000C0100

Logical interface identifier of the secondary endpoint.

1/50

VPI and VCI of the secondary endpoint.

desired state

The status of a connect request. Up indicates a connect request; Down indicates a disconnect request.

status (in vsi_exatm_conn_req output)

The status of a request. One of following status indications appears: OK INVALID_ARGS NONEXIST_INTF TIMEOUT NO_RESOURCES FAIL OK means only that the request is successfully queued for transmission to the switch; it does not indicate completion of the request.


DB-2533

Debug Commands debug vsi errors

debug vsi errors To display information about errors encountered by the Virtual Switch Interface (VSI) master, use the debug vsi errors command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vsi errors [interface interface [slave number]] no debug vsi errors [interface interface [slave number]]

Syntax Description

interface interface

(Optional) Specifies the interface number.

slave number

(Optional) Specifies the slave number (beginning with 0).

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(33)SRA


12.2SX


Usage Guidelines

Use the debug vsi errors command to display information about errors encountered by the VSI master when parsing received messages, as well as information about unexpected conditions encountered by the VSI master. If the interface parameter is specified, output is restricted to errors associated with the indicated VSI control interface. If the slave number is specified, output is further restricted to errors associated with the session with the indicated slave.

Note

Slave numbers are the same as the session numbers discussed under the show controllers vsi session command. Multiple commands that specify slave numbers allow multiple slaves to be debugged immediately. For example, the following commands display errors associated with sessions 0 and 1 on control interface atm2/0, but for no other sessions. Router# debug vsi errors interface atm2/0 slave 0 Router# debug vsi errors interface atm2/0 slave 1

Some errors are not associated with any particular control interface or session. Messages associated with these errors are printed, regardless of the interface or slave options currently in effect.


DB-2534

May 2008

Debug Commands debug vsi errors

Examples

The following is sample output from the debug vsi errors command: Router# debug vsi errors VSI Master: parse error (unexpected param-group contents) in GEN ERROR RSP rcvd on ATM2/0:0/51 (slave 0) errored section is at offset 16, for 2 bytes: 01.01.00.a0 00.00.00.00 00.12.00.38 00.10.00.34 *00.01*00.69 00.2c.00.00 01.01.00.80 00.00.00.08 00.00.00.00 00.00.00.00 00.00.00.00 0f.a2.00.0a 00.01.00.00 00.00.00.00 00.00.00.00 00.00.00.00 00.00.00.00


debug vsi errors Field Descriptions

Field

Description

parse error

An error was encountered during the parsing of a message received by the VSI master.

unexpected param-group contents

The type of parsing error. In this case, a parameter group within the message contained invalid data.

GEN ERROR RSP

The function code in the header of the error message.

ATM2/0

The control interface on which the error message was received.

0/51

The virtual path identifier (VPI) or virtual channel identifier (VCI) of the virtual circuit (VC) (on the control interface) on which the error message is received.

slave

Number of the session on which the error message is received.

offset

The number of bytes between the start of the VSI header and the start of that portion of the message in error.

bytes

Length of the error section.

00.01.00.a0 [...]

The entire error message, as a series of hexadecimal bytes. Note that the error section is between asterisks (*).


DB-2535

Debug Commands debug vsi events

debug vsi events To display information about events that affect entire sessions, as well as events that affect only individual connections, use the debug vsi events command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vsi events [interface interface [slave number]] no debug vsi events [interface interface [slave number]]

Syntax Description

interface interface

(Optional) The interface number.

slave number

(Optional) The slave number (beginning with zero).

Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(33)SRA


12.2SX


Usage Guidelines

Note

Use the debug vsi events command to display information about events associated with the per-session state machines of the Virtual Switch Interface (VSI) master, as well as the per-connection state machines. If you specify an interface, the output is restricted to events associated with the indicated VSI control interface. If you specify the slave number, output is further restricted to events associated with the session with the indicated slave.

Slave numbers are the same as the session numbers discussed under the show controllers vsi session command. Multiple commands that specify slave numbers allow multiple slaves to be debugged at once. For example, the following commands restrict output to events associated with sessions 0 and 1 on control interface atm2/0, but for no other sessions. Output associated with all per-connection events are displayed, regardless of the interface or slave options currently in effect. Router# debug vsi events interface atm2/0 slave 0 Router# debug vsi events interface atm2/0 slave 1


DB-2536

May 2008

Debug Commands debug vsi events

Examples

The following is sample output from the debug vsi events command: Router# debug vsi events VSI Master: conn 0xC0200/1/37->0xC0100/1/51: CONNECTING -> UP VSI Master(session 0 on ATM2/0): event CONN_CMT_RSP, state ESTABLISHED -> ESTABLISHED VSI Master(session 0 on ATM2/0): event KEEPALIVE_TIMEOUT, state ESTABLISHED -> ESTABLISHED VSI Master(session 0 on ATM2/0): event SW_GET_CNFG_RSP, state ESTABLISHED -> ESTABLISHED debug vsi packets


debug vsi events Field Descriptions

Field

Description

conn

The event applies to a particular connection.

0xC0200

Logical interface identifier of the primary endpoint, in hexadecimal form.

1/37

The virtual path identifier (VPI) or virtual channel identifier (VCI) of the primary endpoint.

->

The type of traffic flow. A right arrow (->) indicates unidirectional traffic flow (from the primary endpoint to the secondary endpoint). A bidirectional arrow () indicates bidirectional traffic flow.

0xC0100

Logical interface identifier of the secondary endpoint.

1/51

VPI or VCI of the secondary endpoint.

->

is a mnemonic for the state of the connection before the event occurred. represents the state of the connection after the event occurred.

session

The number of the session with which the event is associated.

ATM2/0

The control interface associated with the session.

event

The event that has occurred. This includes mnemonics for the function codes of received messages (for example, CONN_CMT_RSP), as well as mnemonics for other events (for example, KEEPALIVE_TIMEOUT).

state ->

Mnemonics for the session states associated with the transition triggered by the event. is a mnemonic for the state of the session before the event occurred; is a mnemonic for the state of the session after the event occurred.


DB-2537

Debug Commands debug vsi packets

debug vsi packets To display a one-line summary of each Virtual Switch Interface (VSI) message sent and received by the label switch controller (LSC), use the debug vsi packets command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vsi packets [interface interface [slave number]] no debug vsi packets [interface interface [slave number]]

Syntax Description

interface interface


slave number


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(33)SRA


12.2SX


Usage Guidelines

Note

If you specify an interface, output is restricted to messages sent and received on the indicated VSI control interface. If you specify a slave number, output is further restricted to messages sent and received on the session with the indicated slave.

Slave numbers are the same as the session numbers discussed under the show controllers vsi session command. Multiple commands that specify slave numbers allow multiple slaves to be debugged at once. For example, the following commands restrict output to messages received on atm2/0 for sessions 0 and 1, but for no other sessions. Router# debug vsi packets interface atm2/0 slave 0 Router# debug vsi packets interface atm2/0 slave 1

Examples

The following is sample output from the debug vsi packets command: Router# debug vsi packets VSI master(session 0 on ATM2/0): sent msg SW GET CNFG CMD on 0/51


DB-2538

May 2008


VSI master(session 0 on ATM2/0): rcvd msg SW GET CNFG RSP on 0/51 VSI master(session 0 on ATM2/0): sent msg SW GET CNFG CMD on 0/51 VSI master(session 0 on ATM2/0): rcvd msg SW GET CNFG RSP on 0/51


DB-2539



debug vsi packets Field Descriptions

Field

Description

session

Session number identifying a particular VSI slave. Numbers begin with zero. See the show controllers vsi session command.

ATM2/0

Identifier for the control interface on which the message is sent or received.

sent

The message is sent by the VSI master.

rcvd

The message is received by the VSI master.

msg

The function code from the message header.

0/51

The virtual path identifier (VPI) or virtual channel identifier (VCI) of the virtual circuit (VC) (on the control interface) on which the message is sent or received.


DB-2540

May 2008

Debug Commands debug vsi param-groups

debug vsi param-groups To display the first 128 bytes of each Virtual Switch Interface (VSI) message sent and received by the Multiprotocol Label Switching (MPLS) label switch controller (LSC) (in hexadecimal form), use the debug vsi param-groups command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vsi param-groups [interface interface [slave number]] no debug vsi param-groups [interface interface [slave number]]

Note

Syntax Description

param-groups stands for parameter groups. A parameter group is a component of a VSI message.

interface interface


slave number


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(5)T


12.2(33)SRA


12.2SX


Usage Guidelines

This command is most commonly used with the debug vsi packets command to monitor incoming and outgoing VSI messages. If you specify an interface, output is restricted to messages sent and received on the indicated VSI control interface. If you specify a slave, output is further restricted to messages sent and received on the session with the indicated slave.

Note

Slave numbers are the same as the session numbers discussed under the show controllers vsi session command. Multiple commands that specify slave numbers allow multiple slaves to be debugged at once. For example, the following commands restrict output for messages received on atm2/0 for sessions 0 and 1, but for no other sessions:


DB-2541

Debug Commands debug vsi param-groups

Router# debug vsi param-groups interface atm2/0 slave 0 Router# debug vsi param-groups interface atm2/0 slave 1

Examples

The following is sample output from the debug vsi param-groups command: Router# debug vsi param-groups Outgoing VSI 01.02.00.80 Incoming VSI 01.02.00.81 00.01.00.00 00.00.00.09 00.01.0f.a0 42.50.58.2d Outgoing VSI 01.02.00.80 Incoming VSI 01.02.00.81 00.01.00.00 00.00.00.09 00.01.0f.a0 42.50.58.2d

msg of 12 bytes (not including encap): 00.00.95.c2 00.00.00.00 msg of 72 bytes (not including encap): 00.00.95.c2 00.0f.00.3c 00.10.00.08 00.00.00.00 01.00.00.08 00.00.00.09 01.10.00.20 01.01.01.00 0c.08.80.00 00.13.00.15 00.0c.01.00 00.00.00.00 56.53.49.31 msg of 12 bytes (not including encap): 00.00.95.c3 00.00.00.00 msg of 72 bytes (not including encap): 00.00.95.c3 00.0f.00.3c 00.10.00.08 00.00.00.00 01.00.00.08 00.00.00.09 01.10.00.20 01.01.01.00 0c.08.80.00 00.13.00.15 00.0c.01.00 00.00.00.00 56.53.49.31


debug vsi param-groups Field Descriptions

Field

Description

Outgoing

The message is sent by the VSI master.

Incoming

The message is received by the VSI master.

bytes

Number of bytes in the message, starting at the VSI header, and excluding the link layer encapsulation.

01.02...

The first 128 bytes of the message, in hexadecimal form.


DB-2542

May 2008

Debug Commands debug vtemplate subinterface

debug vtemplate subinterface To display debug messages relating to virtual access subinterfaces, use the debug vtemplate subinterface command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtemplate subinterface no debug vtemplate subinterface

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(8)B


12.2(13)T


12.2(15)B


12.2(28)SB


12.2(31)SB


12.2SX


Usage Guidelines

Examples

The debug messages are displayed if you configure virtual templates with commands that are incompatible with virtual access subinterfaces.

The following example shows how to display virtual access subinterface debug messages: Router# debug vtemplate subinterface Virtual Template subinterface debugging is on Router# Router# Sep 19 15:09:41.989:VT[Vt11]:Config prevents subinterface creation carrier-delay 45 ip rtp priority 2000 2010 500



DB-2543

Debug Commands debug vtemplate subinterface

Table 393

Related Commands

debug vtemplate subinterface Field Descriptions

Field

Description

VT

Indicates that this is a debug virtual template subinterface message.

[Vt11]:

Indicates that this message concerns virtual template 11.

Config prevents subinterface creation

Indicates that this virtual template cannot support the creation of virtual access subinterfaces.

carrier-delay 45 ip rtp priority 2000 2010 500

These are the commands that make the virtual template incompatible with subinterfaces.

Command

Description

test virtual-template subinterface

Tests a virtual template to determine if it can support virtual access subinterfaces.

virtual-template subinterface

Enables the creation of virtual access subinterfaces.


DB-2544

May 2008

Debug Commands debug vtemplate

debug vtemplate To display cloning information for a virtual access interface from the time it is cloned from a virtual template to the time the virtual access interface comes down when the call ends, use the debug vtemplate command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtemplate no debug vtemplate

Syntax Description


Command Modes

Privileged EXEC

Examples

The following is sample output from the debug vtemplate command when a virtual access interface comes up. The virtual access interface is cloned from virtual template 1. Router# debug vtemplate VTEMPLATE Reuse vaccess8, New Recycle queue size:50 VTEMPLATE set default vaccess8 with no ip address Virtual-Access8 VTEMPLATE hardware address 0000.0c09.ddfd VTEMPLATE vaccess8 has a new cloneblk vtemplate, now it has vtemplate VTEMPLATE undo default settings vaccess8 VTEMPLATE ************* CLONE VACCESS8 ***************** VTEMPLATE Clone from vtemplate1 to vaccess8 interface Virtual-Access8 no ip address encap ppp ip unnumbered Ethernet0 no ip mroute-cache fair-queue 64 256 0 no cdp enable ppp authentication chap end %LINK-3-UPDOWN: Interface Virtual-Access8, changed state to up %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access8, changed state to up

The following is sample output from the debug vtemplate command when a virtual access interface goes down. The virtual interface is uncloned and returns to the recycle queue. Router# debug vtemplate %LINK-3-UPDOWN: Interface Virtual-Access8, changed state to down VTEMPLATE Free vaccess8 %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access8, changed state to down VTEMPLATE clean up dirty vaccess queue, size:1


DB-2545


VTEMPLATE Found a dirty vaccess8 clone with vtemplate VTEMPLATE ************ UNCLONE VACCESS8 ************** VTEMPLATE Unclone to-be-freed vaccess8 command#7 interface Virtual-Access8 default ppp authentication chap default cdp enable default fair-queue 64 256 0 default ip mroute-cache default ip unnumbered Ethernet0 default encap ppp default ip address end VTEMPLATE set default vaccess8 with no ip address VTEMPLATE remove cloneblk vtemplate from vaccess8 with vtemplate VTEMPLATE Add vaccess8 to recycle queue, size=51


debug vtemplate Field Descriptions

Field

Description

VTEMPLATE Reuse vaccess8, New Recycle Virtual access interface 8 is reused; the current queue size is 50. queue size:50 VTEMPLATE set default vaccess8 with no ip address Virtual-Access8 VTEMPLATE hardware address 0000.0c09.ddfd

MAC address of virtual interface 8.

VTEMPLATE vaccess8 has a new cloneblk vtemplate, now it has vtemplate

Recording that virtual access interface 8 is cloned from the virtual interface template.

VTEMPLATE undo default settings vaccess8 Removing the default settings. VTEMPLATE ************* CLONE VACCESS8 ********** *******

Banner: Cloning is in progress on virtual access interface 8.

VTEMPLATE Clone from vtemplate1 to vaccess8

Specific configuration commands in virtual interface template 1 that are being applied to the virtual access interface 8.

interface Virtual-Access8 no ip address encap ppp ip unnumbered Ethernet0 no ip mroute-cache fair-queue 64 256 0 no cdp enable ppp authentication chap end %LINK-3-UPDOWN: Interface Virtual-Access8, changed state to up

Link status: The link is up.

%LINEPROTO-5-UPDOWN: Line protocol Line protocol status: The line protocol is up. on Interface Virtual-Access8, changed state to up


DB-2546

May 2008


Table 394

debug vtemplate Field Descriptions (continued)

Field

Description

%LINK-3-UPDOWN: Interface Virtual-Access8, changed state to down

Link status: The link is down.

VTEMPLATE Free vaccess8

Freeing virtual access interface 8.

%LINEPROTO-5-UPDOWN: Line protocol Line protocol status: The line protocol is down. on Interface Virtual-Access8, changed state to down VTEMPLATE clean up dirty vaccess queue, size:1

Access queue cleanup is proceeding and the template is being uncloned.

VTEMPLATE Found a dirty vaccess8 clone with vtemplate VTEMPLATE ************ UNCLONE VACCESS8 ************** VTEMPLATE Unclone to-be-freed vaccess8 command#7

Specific configuration commands to be removed from the virtual access interface 8.

interface Virtual-Access8 default ppp authentication chap default cdp enable default fair-queue 64 256 0 default ip mroute-cache default ip unnumbered Ethernet0 default encap ppp default ip address end VTEMPLATE set default vaccess8 with no ip Default is set again. address VTEMPLATE remove cloneblk vtemplate from vaccess8 with vtemplate

Removing the record of cloning from a virtual interface template.

VTEMPLATE Add vaccess8 to recycle queue, Virtual access interface is added to the recycle queue. size=51


DB-2547

Debug Commands debug vtsp all

debug vtsp all To show debugging information for all debug vtsp commands, use the debug vtsp all command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtsp all no debug vtsp all

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T

This command was introduced on the Cisco AS5300.

12.0(7)XK

This command was first supported on the Cisco 2600, Cisco 3600 and Cisco MC3810 series.

12.1(2)T


12.2(11)T

The new debug header was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, and Cisco 3640. and Cisco 3660; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following universal access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.

12.2SX


Usage Guidelines

The debug vtsp all command enables the following debug vtsp commands: debug vtsp session, debug vtsp error, and debug vtsp dsp. For more information or sample output, see the individual commands. Execution of the no debug vtsp all command will turn off all VTSP-level debugging. You should turn off all debugging and then enter the debug commands you are interested in one by one. This process helps avoid confusion about which ports you are actually debugging.

Caution

Using this command can severely impact network performance and prevent any faxes from succeeding.


DB-2548

May 2008


Examples

The following example shows the debug vtsp all command on a Cisco 3640 modular access router: Router# debug vtsp all Voice telephony call control all debugging is on

At this point, the VTSP is not aware of anything. The format of this message is //callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number: •

CallEntry ID is -1.

•

GUID is xxxxxxxxxx.

•

The voice port is blank.

•

Channel ID is -1.

•

DSP ID is -1.

•

DSP channel ID is -1.

*Mar

1 08:23:10.869: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate:

The original and the translated calling number are the same (55555) and the original and the translated called number are the same (888545). These numbers are often the same because if a translation rule is applied, it will be on the dial peers or the ports, both of which comes later than these VTSP messages in the Cisco IOS code execution. *Mar 1 08:23:10.869: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: calling_number(original)= calling_number(xlated)=55555 called_number(original)= called_number(xlated)=888545 redirectNumber(original)= redirectNumber(xlated)=

The VTSP got a call setup indicator from the TSP layer with called number 888545 and calling number 55555. There is no awareness of the CallEntry ID (-1) or the GUID (xxxxxxxxxxxx). *Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind: (sdb=0x634C90EC, tdm_info=0x0, tsp_info=0x63083950, calling_number=55555 calling_oct3 = 0x80, called_number=888545 called_oct3 = 0x80, oct3a=0x0): peer_tag=10002 *Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind : ev.clg.clir is 0 ev.clg.clid_transparent is 0 ev.clg.null_orig_clg is 0 ev.clg.calling_translated is false *Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind: . *Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_allocate_cdb: ,cdb 0x635FC480 *Mar 1 08:23:10.873: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind: *Mar 1 08:23:10.873: source route label


CallEntry ID is -1.

•

GUID is D2F6429A8A8A.

•

The voice port is 1/0:23 where 23 indicates D channel.

•

The T1 channel is still unknown at this point (-1).

•

The digital signal processor (DSP) is 0.

•

The DSP channel is 4.


DB-2549


*Mar 1 08:23:10.873: //-1/D2F6429A8A8A/VTSP:(1/0:23):-1:0:4/vtsp_do_call_setup_ ind: Call ID=101002, guid=635FCB08

The VTSP learns about the B channel (changed from -1 to 22), and the CallEntry ID is still unknown (-1). *Mar 1 08:23:10.873: //-1/D2F6429A8A8A/VTSP:(1/0:23):22:0:4/vtsp_do_call_setup_ind: type=0, under_spec=1615186336, name=, id0=23, id1=0, id2=0, calling=55555,called=888545 subscriber=RegularLinevtsp_do_call_setup_ind: redirect DN = reason = -1 *Mar 1 08:23:10.877: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_normal_call_setup_ind: .

The VTSP learns the CallEntry ID. The format of this message is //callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number: •

CallEntry ID is 899 (changed from -1 to 899)

•

GUID is D2F6429A8A8A

•

The voice port is 1/0:23 where 23 indicates D channel

•

The T1 channel is 22

•

The DSP is 12

•

The DSP channel is 4

*Mar 1 08:23:10.877: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_insert_cdb:,cdb 0x635FC480, CallID=899 *Mar 1 08:23:10.877: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_open_voice_and_set_params: .

In the following outputs, VTSP sets some of the voice parameters for this call: •

Modem capability

•

Playout delay

•

Dial-peer tag 10003

•

Digit timeouts

*Mar 1 08:23:10.877: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: cap_modem_proto 0 *Mar 1 08:23:10.881: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_playout_cdb:playout default *Mar 1 08:23:10.881: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_dsp_echo_canceller_control: echo_cancel: 1 *Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_save_dialpeer_tag: tag = 10003 *Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_report_digit_control: vtsp_report_digit_control: enable=0: *Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_report_digit_control: digit reporting disabled *Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_digit_timeouts: : vtsp_get_digit_timeouts

VTSP sends out a call-proceeding message to the POTS leg. *Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event:vtsp:[1/0:23:899, S_SETUP_INDICATED, E_CC_PROCEEDING] *Mar 1 08:23:10.885: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_proceeding: . *Mar 1 08:23:10.941: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag = 10003


DB-2550

May 2008


*Mar 1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag = 10003

VTSP sends out an alerting to the POTS leg; the phone is ringing at this time. *Mar 1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_PROCEEDING, E_CC_ALERT] *Mar 1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_alert: . *Mar 1 08:23:10.949: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3019095 *Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_dialpeer_tag: tag = 10003

The phone gets answered here, a bridge is now set up between the two call legs. *Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_ALERTING, E_CC_BRIDGE] *Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_bridge: .

The call is now connected. *Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_ALERTING, E_CC_CONNECT] *Mar 1 08:23:18.769: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_alert_connect: . *Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 3019877

The VTSP received a capabilities indication event from the CCAPI. The VTSP needs to be aware of this because it handles the DSPs. *Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_CAPS_IND] *Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: . *Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: RTP PT:NTE[101],NTEtx[101],NSE[100],FaxInd[96],FaxAck[97],CiscoDTMF[121],FaxRelay[122],CASsig[ 123],ClearChan[125],PCMu[0],PCMa[8]Codec[4],TxDynamicPayload[0], RxDynamicPayload[0] *Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: dtmf relay: mode=32, codec=1 *Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: passthrough: cap_modem_proto 0, cap_modem_codec 0, cap_modem_redundancy 0, payload100, modem_relay 0, gw-xid=0 *Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: Encap 1, Vad 2, Codec 0x4, CodecBytes 20, FaxRate 2, FaxBytes 20, FaxNsf 0xAD0051 SignalType 2 DtmfRelay 32, Modem 0, SeqNumStart 0x1343 *Mar 1 08:23:18.773: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: *Mar 1 08:23:18.777: FORKING Parameters are forking mask: 0, simple_forking_codec_mask: 0, complex_forking_codec_mask 0 *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ind: [ mode:0,init:60, min:40, max:200]

The VTSP received events regarding capabilities acknowledged from the call control API (CCAPI). *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_CAPS_ACK] *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: . *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: passthrough: cap_modem_proto 0, cap_modem_codec 0, cap_modem_redundancy 0, payload100, modem_relay 0, gw-xid=0 *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_caps_ack: Named Telephone Event payload: rcv 101, tx 101 *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_switch_codec: *Mar 1 08:23:18.777: DTMF Relay in act_switch_codec is 32 *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_dsp_encap_config:


DB-2551


*Mar 1 08:23:18.777: set_dsp_encap_config: logical ssrc 40 *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: cap_modem_proto 0 *Mar 1 08:23:18.777: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_switch_codec: codec = 16 *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3019878 *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, SP_PENDING_CODEC_SWITCH, E_DSPRM_PEND_SUCCESS] *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_pend_codec_success: . *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3019878 *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_open_voice_and_set_params: . *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_dsp_encap_config: *Mar 1 08:23:18.781: set_dsp_encap_config: logical ssrc 40 *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_proto_from_cdb: cap_modem_proto 0 *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/set_playout_cdb:playout default *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_dsp_echo_canceller_control: echo_cancel: 1 *Mar 1 08:23:18.781: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_add_fork: *Mar 1 08:23:18.785: vtsp_add_fork *Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info: *Mar 1 08:23:18.785: vtsp_update_fork_info: add_fork=0 *Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_xmit_info_node: *Mar 1 08:23:18.785: vtsp_get_xmit_info_node *Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info: *Mar 1 08:23:18.785: vtsp_update_fork_info xmit func is 60FC43F0, context is 635BC51Cpeer_call_id: 900, stream_count: 1, update_flag 0 Router# *Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info: *Mar 1 08:23:18.785: The stream bit-mask is 1 *Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info: *Mar 1 08:23:18.785: The stream type is 0 *Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_fork_info: *Mar 1 08:23:18.785: The logical ssrc is 64 for stream 0 *Mar 1 08:23:18.785: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_update_stream_count: *Mar 1 08:23:18.785: g711_voice_count=0 g711_avt_count = 0 g711_voice_avt_count = 0 complex_voice_count = 1 complex_avt_count = 0 complex_voice_avt_count = 0

A digit begin event was detected while in the connect state. Digit 1 is dialed outbound on the POTS legs. *Mar 1 08:23:26.745: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_call_digit_begin: vtsp_call_digit_begin: digit=1, digit_begin_flags=0x0, rtp_timestamp=0, rtp_expiration=0 *Mar 1 08:23:26.745: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_DIGIT_BEGIN] *Mar 1 08:23:26.745: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_digit_begin:act_digit_begin *Mar 1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_call_digit_end: vtsp_call_digit_end: digit=1, duration=300

A digit end event was detected while in the connect state. The total duration of the digit was 300 ms. *Mar 1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_DIGIT_END,] *Mar 1 08:23:27.045: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_digit_end: act_digit_end


DB-2552

May 2008


The call is hung up at this point, VTSP receives a bridge drop event from the CCAPI. *Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_BRIDGE_DROP] *Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_remove_stream_node: *Mar 1 08:23:39.393: vtsp_remove_stream_node *Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_get_xmit_info_node: *Mar 1 08:23:39.393: vtsp_get_xmit_info_node *Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_remove_stream_node: *Mar 1 08:23:39.393: Stream count is 1 in function vtsp_remove_stream_node *Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_bdrop: . *Mar 1 08:23:39.393: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_is_record_active: *Mar 1 08:23:39.393: vtsp_is_record_active: false

VTSP gets a disconnect event from the CCAPI. *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CONNECT, E_CC_DISCONNECT] *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_disconnect: .

Following the disconnect event from the CCAPI, the timers are stopped. *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 3021940 *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_pcm_tone_detect_timer_stop: 3021940 *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_pcm_switchover_timer_stop: 3021940 *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_cm_detect_timer_stop: 3021940 *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_relay_mode_timer_stop: 3021940 *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_modem_relay_stats_timer_stop: 3021940 *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021940 *Mar 1 08:23:39.397: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_disconnect: cdb 0x635FC480, cause 0x10 *Mar 1 08:23:39.401: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021940

Statistics are collected for the DSP. *Mar 1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_WAIT_STATS, E_DSP_GET_ERROR] *Mar 1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_get_error: . *Mar 1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_print_error_stats: rx_dropped=0 tx_dropped=0 *Mar 1 08:23:39.405: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_print_error_stats: rx_control=55 tx_control=18 tx_control_dropped=0 dsp_mode_channel_1=0 dsp_mode_channel_2=0c[0]=0c[1]=2c[2]=6c[3]=87c[4]=83c[5]=84c[6]=106c[7]=78c[8]=0c[9]=32639 c[10]=32639c[11]=32639c[12]=32639c[13]=32639c[14]=32639c[15]=32639 *Mar 1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021941 *Mar 1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021941 *Mar 1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_WAIT_STATS, E_DSP_GET_LEVELS] *Mar 1 08:23:39.409: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_get_levels: . *Mar 1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_stats_complete: . *Mar 1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021941 *Mar 1 08:23:39.413: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_ring_noan_timer_stop: 3021941 *Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer: 3021942


DB-2553


The VTSP received a disconnect confirmation from the TSP layer. *Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_WAIT_RELEASE, E_TSP_DISCONNECT_CONF] *Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_wrelease_release: . *Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_play_busy_timer_stop: *Mar 1 08:23:39.417: vtsp_play_busy_timer_stop: 3021942 *Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_timer_stop:3021942 *Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history: . *Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history: *Mar 1 08:23:39.417: vtsp_do_call_history : src carrier id *Mar 1 08:23:39.417: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history: *Mar 1 08:23:39.421: vtsp_do_call_history : tgt carrier id *Mar 1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_do_call_history: CoderRate 16

DSP resource manager updates the state. *Mar 1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_process_event: vtsp:[1/0:23:899, S_CLOSE_DSPRM, E_DSPRM_CLOSE_COMPLETE] *Mar 1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/act_terminate: . *Mar 1 08:23:39.421: //899/D2F6429A8A8A/VTSP:(1/0:23):22:12:4/vtsp_free_cdb: ,cdb 0x635FC4803

Related Commands

Command

Description

debug vtsp port

Limits VTSP debug output to a specific voice port.

show debug


voice call debug



DB-2554

May 2008

Debug Commands debug vtsp dsp

debug vtsp dsp To show messages from the digital signal processor (DSP) to the universal access server or router, use the debug vtsp dsp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtsp dsp no debug vtsp dsp

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T

This command was introduced on the Cisco AS5300 series access servers.

12.0(7)XK

This command was implemented on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810 multiservice access concentrators.

12.1(2)T


12.2(11)T


12.2SX


Usage Guidelines

On Cisco AS5300 Series Access Servers

The debug vtsp dsp command shows messages from the DSP on the voice feature card (VFC) to the router; this command can be useful if you suspect that the VFC is not functional. It is a simple way to check if the VFC is responding to off-hook indications. On Cisco 2600, 3600, MC3810 Series

The debug vtsp dsp command shows messages from the DSP to the router.


DB-2555

Debug Commands debug vtsp dsp

Note

Examples

We recommend that you log output from the debug vtsp dsp command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

The following example shows the VTSP DSP usage on a Cisco 3640 modular access router: Router# debug vtsp dsp Voice telephony call control dsp debugging is on Router# *Mar 1 01:05:18.539: //12/A76D98838014/VTSP:(1/0:23):22:14:2/vtsp_dsp_echo_canceller_control: echo_cancel: 1


Related Commands

debug vtsp dsp Field Descriptions

Field

Descriptions

//12

CallEntry ID.

/A76D98838014

GUID.

1/0:23

Controller 1/0, D channel.

:22

B-channel number. This can also be found using the show voice call summary command.

:14

DSP number. This can also be found using the show voice dsp command.

:2

Channel number on the DSP. This can also be found using the show voice dsp command.

echo_cancel: 1

Echo cancel is on.

Command

Description

debug vpm all


debug vtsp port


show debug


voice call debug



DB-2556

May 2008

Debug Commands debug vtsp error

debug vtsp error To display processing errors in the voice telephony service provider (VTSP), use the debug vtsp error command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtsp error no debug vtsp error

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)XK


12.1(2)T


12.2(11)T


12.2SX


Usage Guidelines

Note

Related Commands

The debug vtsp error command can be used to check for mismatches in interface capabilities.

We recommend that you log output from the debug vtsp error command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Command

Description

debug vpm all


debug vtsp port


show debug


voice call debug



DB-2557

Debug Commands debug vtsp event

debug vtsp event To display the state of the gateway and the call events, use the debug vtsp event command in privileged EXEC mode. To display the machine state during voice telephony service provider (VTSP) event processing, use the no form of this command. debug vtsp event no debug vtsp event

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T

This command was introduced on the Cisco AS5300 universal access servers.

12.0(7)XK


12.1(2)T


12.2(11)T


12.2SX


Usage Guidelines

Note

The debug vtsp event command can be used to enable state machine debugging.

We recommend that you log output from the debug vtsp event command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.


DB-2558

May 2008


Examples

The following shows sample output from the debug vtsp event command: Router# debug vtsp event Voice Telephony event debugging is on

The following events are seen when the call is set up. *Mar 1 22:20:39.138: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_SETUP_INDICATED, event: E_CC_PROCEEDING]

When the phone starts ringing, the ALERT event appears. *Mar 1 22:20:39.202: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_PROCEEDING, event: E_CC_ALERT] Router#

As soon as the call is answered, the bridge comes up and the CONNECT event appears. *Mar 1 22:20:47.798: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_ALERTING, event: E_CC_BRIDGE] *Mar 1 22:20:47.802: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_ALERTING, event: E_CC_CONNECT]

The capabilities are exchanged as soon as the connection occurs. *Mar 1 22:20:47.802: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_CAPS_IND] *Mar 1 22:20:47.802: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_CAPS_ACK] *Mar 1 22:20:47.802: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:SP_PENDING_CODEC_SWITCH, event: E_DSPRM_PEND_SUCCESS]

The following debug outputs are regularly seen as the call progresses. The outputs indicate that collection of Tx/Rx/Delay/Error statistics is occurring. *Mar 1 22:20:49.470: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_REQ_PACK_STAT] *Mar 1 22:20:49.482: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_TX] *Mar 1 22:20:49.482: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_RX] *Mar 1 22:20:49.486: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_VP_DELAY] *Mar 1 22:20:49.486: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_VP_ERROR] *Mar 1 22:20:51.638: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_REQ_PACK_STAT] *Mar 1 22:20:51.638: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_TX] *Mar 1 22:20:51.638: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_RX] *Mar 1 22:20:51.642: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_VP_DELAY] *Mar 1 22:20:51.642: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_DSP_GET_VP_ERROR] Router#

When digits are passed during the conversation, the digit begin and digit end events are seen. *Mar 1 22:21:01.542: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DIGIT_BEGIN] *Mar 1 22:21:01.842: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DIGIT_END,]


DB-2559


*Mar 1 22:21:01.962: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DIGIT_BEGIN] *Mar 1 22:21:02.262: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DIGIT_END,] Router#

Once the call is hung up from one side, the bridge_drop and the disconnect events appear. *Mar 1 22:21:10.834: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_TSP_DISCONNECT_IND] *Mar 1 22:21:10.838: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_BRIDGE_DROP] *Mar 1 22:21:10.838: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CONNECT, event: E_CC_DISCONNECT]

Following the disconnect event, the signaling state becomes S_WAIT_STATS, during which the DSP stats are collected. *Mar 1 22:21:10.842: [state:S_WAIT_STATS, *Mar 1 22:21:10.846: [state:S_WAIT_STATS, *Mar 1 22:21:10.854: [state:S_WAIT_STATS,

//72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: event: E_DSP_GET_ERROR] //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: event: E_DSP_GET_LEVELS] //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: event: E_DSP_GET_TX]

The conference is torn down and the DSP is released. *Mar 1 22:21:10.854: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_WAIT_RELEASE, event: E_TSP_DISCONNECT_CONF] *Mar 1 22:21:10.858: //72/D14258FE806E/VTSP:(1/0:23):22:14:2/vtsp_process_event: [state:S_CLOSE_DSPRM, event: E_DSPRM_CLOSE_COMPLETE]

Related Commands

Command

Description

debug vpm all


debug vtsp error

Displays processing errors in the VTSP.

debug vtsp port


show debug


voice call debug



DB-2560

May 2008

Debug Commands debug vtsp port

debug vtsp port To observe the behavior of the voice telephony service provider (VTSP) state machine on a specific voice port, use the debug vtsp port command in privileged EXEC mode. To disable debugging output, use the no form of this command. For Cisco 2600 and Cisco 3600 Series with Analog Voice Ports

debug vtsp port slot/subunit/port no debug vtsp port slot/subunit/port For Cisco 2600 and Cisco 3600 Series with Digital Voice Ports (With T1 Packet Voice Trunk Network Modules)

debug vtsp port slot/port:ds0-group no debug vtsp port slot/port:ds0-group For Cisco MC3810 Series with Analog Voice Ports

debug vtsp port slot/port no debug vtsp port slot/port For Cisco MC3810 Series with Digital Voice Ports

debug vtsp port slot/port no debug vtsp port slot/ds0-group

Syntax Description

slot/subunit/port

•

slot specifies a router slot in which a voice network module (NM) is installed. Valid entries are router slot numbers for the specific platform.

•

subunit specifies a voice interface card (VIC) where the voice port is located. Valid entries are 0 and 1. (The VIC fits into the voice network module.)

•

port specifies an analog voice port number. Valid entries are 0 and 1.

For the Cisco 2600 and Cisco 3600 Series with Digital Voice Ports

slot/port:ds0-group Debugs the digital voice port you specify with the slot/port:ds0-group designation. •

slot specifies a router slot in which the packet voice trunk network module (NM) is installed. Valid entries are router slot numbers for the specific platform.

•

port specifies a T1 or E1 physical port in the voice WAN interface card (VWIC). Valid entries are 0 and 1. (One VWIC fits in an NM.)

•

ds0-group specifies a T1 or E1 logical port number. Valid entries are 0 to 23 for T1 and 0 to 30 for E1.


DB-2561


For the Cisco MC3810 Series with Analog Voice Ports

slot/port

Debugs the analog voice port you specify with the slot/port designation. •

slot is the physical slot in which the analog voice module (AVM) is installed. The slot is always 1 for analog voice ports in the Cisco MC3810 series.

•

port specifies an analog voice port number. Valid entries are 1 to 6.

For the Cisco MC3810 Series with Digital Voice Ports

slot:ds0-group

Debugs the digital voice port you specify with the slot:ds0-group designation. •

slot specifies the module (and controller). Valid entries are 0 for the MFT (controller 0) and 1 for the DVM (controller 1).

•

ds0-group specifies a T1 or E1 logical voice port number. Valid entries are 0 to 23 for T1 and 0 to 30 for E1.

Defaults

Debug VTSP commands are not limited to a specific port.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)XG

This command was introduced on Cisco 2600 and Cisco 3600 series routers.

12.0(3)T


12.0(7)XK


12.1(2)T


12.2(11)T


12.2SX


Usage Guidelines

Use the debug vtsp port command to limit the debug output to a specific voice port. The debug output can be quite voluminous for a single channel. The entire VTSP debug output from a platform with 12 voice ports might create problems. Use this debug command with any or all of the other debug modes.


DB-2562

May 2008


Execution of no debug vtsp all will turn off all VTSP-level debugging. It is usually a good idea to turn off all debugging and then enter the debug commands you are interested in one by one. This will help to avoid confusion about which ports you are actually debugging.

Note

Related Commands

We recommend that you log output from the debug vtsp port command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Command

Description

debug vpm all


show debug


voice call debug



DB-2563

Debug Commands debug vtsp rtp

debug vtsp rtp To show the voice telephony service provider (VTSP) Real-Time Protocol (RTP) packet debugging, use the debug vtsp rtp command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtsp rtp {both | from-dsp | to-dsp} {payload payload-type codec} no debug vtsp rtp

Syntax Description

both

Displays packets that are both sent and received from the digital signal processor (DSP).

from-dsp

Displays packets received from the DSP.

to-dsp

Displays packets sent to the DSP.

payload

(Optional) Specifies a specific type of payload.

payload-type

(Optional) Valid payload types are as follows:

codec

•

all—All packets are displayed. No codec is specified.

•

equal-to—Packets in payloads equal to the specified codec are displayed.

•

greater-than—Packets in payloads greater than the specified codec are displayed.

•

less-than—Packets in payloads less than the specified codec are displayed.

•

other-than—Packets in payloads other than the specified codec are displayed.

•

other-than-fax-and—Packets in payloads other than fax relay and the specified codec are displayed.

•

other-than-silence-and—Packets in payloads other than silence and the specified codec are displayed.

(Optional) If a codec needs to be specified for the payload type, valid codecs are as follows: •

0 to 123—Custom value of the payload.

•

g711alaw—G.711 alaw 64000 bps.

•

g711ulaw—G.711 ulaw 64000 bps.

•

g723.1—G.723.1.

•

g726—G.726.

•

g728—G.728.

•

g729a—G.729a.

Defaults


Command Modes

Privileged EXEC


DB-2564

May 2008

Debug Commands debug vtsp rtp

Command History

Release

Modification

12.0(3)T


12.0(7)XK

This command was first supported on the Cisco 2600, Cisco 3600, and MC3810 series devices.

12.1(2)T


12.2(11)T


12.2SX


Usage Guidelines

We recommend that you log output from the debug vtsp rtp command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Examples

The following example shows the VTSP RTP debugging: Router# debug vtsp rtp both pay all Voice telephony RTP Packet debugging enabled for payloads of all types of packets from and to DSP

The following line shows the payload from the DSP (telephony leg) to the IP leg: *Mar 1 01:10:05.687: //20/4DD959B48020/VTSP:(1/0:23):22:14:2/vtsp_print_rtp_header: s=DSP d=VoIP payload 0x12 ssrc 0x40 sequence 0x19E3 timestamp 0xCCDCE092

The following line shows the payload from the IP leg to the DSP (telephony leg): *Mar 1 01:10:05.699: //20/4DD959B48020/VTSP:(1/0:23):22:14:2/vtsp_print_rtp_header: s=VoIP d=DSP payload 0x12 ssrc 0xAF0534E3 sequence 0x92A timestamp 0x6BE50

Related Commands

Command

Description

debug vtsp dsp

Shows messages from the DSP.

voice call debug



DB-2565

Debug Commands debug vtsp send-nse

debug vtsp send-nse To trigger the voice telephony service provider (VTSP) software module to send a triple redundant network services engine (NSE), use the debug vtsp send-nse command in privileged EXEC mode. To disable this action, use the no form of this command. debug vtsp send-nse no debug vtsp send-nse

Syntax Description


Defaults


Command Modes

Privileged EXEC

Command History

Release

Modification

12.2(11)T


12.2SX


Usage Guidelines

We recommend that you log output from the debug vtsp send-nse command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Related Commands

Command

Description

debug rtpspi all


debug rtpspi errors


debug rtpspi inout




debug sgcp errors

Debugs SGCP errors.

debug sgcp events

Debugs SGCP events.

debug sgcp packet


voice call debug



DB-2566

May 2008

Debug Commands debug vtsp session

debug vtsp session To trace how the router interacts with the digital signal processor (DSP) based on the signaling indications from the signaling stack and requests from the application, use the debug vtsp session command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtsp session no debug vtsp session

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T


12.0(7)XK

This command was implemented on the Cisco 2600, Cisco 3600 and Cisco MC3810 series.

12.2(11)T


12.2SX


Usage Guidelines

The debug vtsp session command traces how the router interacts with the DSP based on the signaling indications from the signaling stack and requests from the application. This debug command displays information about how each network indication and application request is handled, signaling indications, and DSP control messages. This debug level shows the internal workings of the voice telephony call state machine.

Note

We recommend that you log output from the debug vtsp send-nse command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.


DB-2567


Examples

The following shows sample output from the debug vtsp session command: Router# debug vtsp session Voice telephony call control session debugging is on


CallEntry ID is -1.

•

GUID is xxxxxxxxxx.

•

The voice port is blank.

•

Channel ID is -1.

•

DSP ID is -1.

•

DSP channel ID is -1.

*Mar

2 01:20:43.225: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: .

The original and the translated calling number are the same (55555) and the original and the translated called number are the same (888545). These numbers are often the same because if a translation rule is applied, it will be on the dial peers or the ports both of which comes later than these VTSP messages in the Cisco IOS code execution. *Mar 2 01:20:43.225: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: calling_number(original)= calling_number(xlated)=55555 called_number(original)= called_number(xlated)=888545 redirectNumber(original)= redirectNumber(xlated)=

The VTSP got a call setup indicator from the TSP layer with called number 888545 and calling number 55555. There is no awareness of the CallEntry ID (-1) or the GUID (xxxxxxxxxxxx). *Mar 2 01:20:43.225: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind: (sdb=0x637AA6C0, tdm_info=0x0, tsp_info=0x630B6050, calling_number=55555 calling_oct3 = 0x80, called_number=888545 called_oct3 = 0x80, oct3a=0x0): peer_tag=10002 *Mar 2 01:20:43.225: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind: ev.clg.clir is 0 ev.clg.clid_transparent is 0 ev.clg.null_orig_clg is 0 ev.clg.calling_translated is false *Mar 2 01:20:43.229: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind: . *Mar 2 01:20:43.229: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_allocate_cdb: ,cdb 0x637B2A68 *Mar 2 01:20:43.229: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_call_setup_ind: *Mar 2 01:20:43.229: source route label

At this point, the VTSP is not aware of the anything. The format of this message is //callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number: •

CallEntry ID is -1.

•

GUID is F90073EB8080.

•


•

The T1 channel is still unknown at this point (-1).

•

The DSP is 0.

•



DB-2568

May 2008


*Mar 2 01:20:43.229: //-1/F90073EB8080/VTSP:(1/0:23):-1:0:2/vtsp_do_call_setup_ind: Call ID=98432, guid=637B43F4

The VTSP learns that the B channel used changed from -1 to 22. *Mar 2 01:20:43.229: //-1/F90073EB8080/VTSP:(1/0:23):22:0:2/vtsp_do_call_setup_ind: type=0, under_spec=1615186336, name=, id0=23, id1=0, id2=0, calling=55555,called=888545 subscriber=RegularLinevtsp_do_call_setup_ind: redirect DN = reason = -1 *Mar 2 01:20:43.229: //-1/xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_normal_call_setup_ind: .

The VTSP learns the CallEntry ID. The format of this message is //callid/GUID/VTSP:(voice-port):T1-channel_number:DSP_number:DSP_channel_number: •

CallEntry ID is 84 (changed from -1 to 84).

•

GUID is F90073EB8080.

•


•

The T1 channel is 22.

•

The DSP is 14.

•


*Mar 2 01:20:43.233: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_insert_cdb: ,cdb 0x637B2A68, CallID=84 *Mar 2 01:20:43.233: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_open_voice_and_set_params: .

In the following outputs VTSP sets some of the voice parameters for this call: •

Modem capability

•

Playout-delay

•

Dial-peer tag = 10003

•

Digit-timeouts

*Mar 2 01:20:43.233: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_modem_proto_from_cdb: cap_modem_proto 0 *Mar 2 01:20:43.233: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/set_playout_cdb: playout default *Mar 2 01:20:43.237: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_save_dialpeer_tag: tag = 10003 *Mar 2 01:20:43.237: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_report_digit_control: vtsp_report_digit_control: enable=0: *Mar 2 01:20:43.237: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_report_digit_control: digit reporting disabled *Mar 2 01:20:43.237: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_get_digit_timeouts: : vtsp_get_digit_timeouts

The VTSP sends out a call-proceeding message to the POTS leg. *Mar 2 01:20:43.241: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_process_event: vtsp:[1/0:23:84, S_SETUP_INDICATED, E_CC_PROCEEDING] *Mar 2 01:20:43.241: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/act_proceeding: . Router# *Mar 2 01:20:43.297: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_get_dialpeer_tag: tag = 10003 *Mar 2 01:20:43.301: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_get_dialpeer_tag: tag = 10003


DB-2569


VTSP sends out an alerting to the POTS leg; the phone is ringing now. *Mar 2 01:20:43.301: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_process_event: vtsp:[1/0:23:84, S_PROCEEDING, E_CC_ALERT] *Mar 2 01:20:43.301: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/act_alert: . *Mar 2 01:20:43.301: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_timer_stop: 9124331 Router# *Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_get_dialpeer_tag: tag = 10003

The phone gets answered here, and a bridge is now set up between the two call legs. *Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_process_event: vtsp:[1/0:23:84, S_ALERTING, E_CC_BRIDGE] *Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/act_bridge: .

The call is now connected. *Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_process_event: vtsp:[1/0:23:84, S_ALERTING, E_CC_CONNECT] *Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/act_alert_connect: . *Mar 2 01:20:52.289: //84/F90073EB8080/VTSP:(1/0:23):22:14:2/vtsp_ring_noan_timer_stop: 9125229

Related Commands

Command

Description

debug vpm all


debug vtsp port


show debug



DB-2570

May 2008

Debug Commands debug vtsp stats

debug vtsp stats To debug periodic statistical-information-request messages sent and received from the digital signal processor (DSP) during a call, use the debug vtsp stats command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtsp stats no debug vtsp stats

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T


12.0(7)XK

This command was implemented on the Cisco 2600, Cisco 3600 and Cisco MC3810 series.

12.2(11)T


12.2SX


Usage Guidelines

Note

The debug vtsp stats command generates a collection of DSP statistics for generating Real-Time Transport Protocol (RTCP) packets and a collection of other statistical information.

We recommend that you log output from the debug vtsp stats command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.


DB-2571

Debug Commands debug vtsp stats

Related Commands

Command

Description

debug vpm all


debug vtsp port


show debug


voice call debug



DB-2572

May 2008

Debug Commands debug vtsp tone

debug vtsp tone To display debugging messages showing the types of tones generated by the Voice over IP (VoIP) gateway, use the debug vtsp tone command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtsp tone no debug vtsp tone

Syntax Description


Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.1(3)XI


12.1(5)T


12.2(11)T


12.2SX


Usage Guidelines

We recommend that you log output from the debug vtsp tone command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Related Commands

Command

Description

debug vtsp dsp

Shows messages from the DSP on the modem to the router.

debug vtsp session

Traces how the router interacts with the DSP, based on the signaling indications from the signaling stack and requests from the application.

voice call debug



DB-2573

Debug Commands debug vtsp vofr subframe

debug vtsp vofr subframe To display the first 10 bytes (including header) of selected Voice over Frame Relay (VoFR) subframes for the interface, use the debug vtsp vofr subframe command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vtsp vofr subframe payload [from-dsp] [to-dsp] no debug vtsp vofr subframe

Syntax Description

payload

Number used to selectively display subframes of a specific payload. Payload types are: 0: Primary Payload 1: Annex-A 2: Annex-B 3: Annex-D 4: All other payloads 5: All payloads

Caution

Options 0 and 5 can cause network instability.

from-dsp

Displays only the subframes received from the digital signal processor (DSP).

to-dsp

Displays only the subframes going to the DSP.

Defaults

Disabled

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)XG, 12.0(4)T

This command was introduced on the Cisco 2600 and Cisco 3600 series.

12.0(7)XK


12.1(2)T


12.2(11)T


12.2SX



DB-2574

May 2008

Debug Commands debug vtsp vofr subframe

Usage Guidelines

Each debug output displays the first 10 bytes of the FRF.11 subframe, including header bytes. The from-dsp and to-dsp options can be used to limit the debugs to a single direction. If not specified, debugs are displayed for subframes when they are received from the DSP and before they are sent to the DSP. Use extreme caution in selecting payload options 0 and 6. These options may cause network instability.

Note

Related Commands

We recommend that you log output from the debug vtsp vofr subframe command to a buffer rather than sending the output to the console; otherwise, the size of the output could severely impact the performance of the gateway.

Command

Description

debug vpm all


debug vtsp port


show debug


voice call debug



DB-2575

Debug Commands debug vtsp

debug vtsp Note

Effective with release 12.3(8)T, the debug vtsp command is replaced by the debug voip dsm and debug voip vtsp commands. See the debug voip dsm and debug voip vtsp commands for more information. To display the state of the gateway and the call events, use the debug vtsp command in privileged EXEC mode. To display the machine state during voice telephony service provider (VTSP) event processing, use the no form of the command. debug vtsp {all | dsp | error | event | session | stats | tone | rtp} no debug vtsp {all | dsp | error | event | session | stats | tone | rtp}

Note

Syntax Description

The debug vtsp command with the event keyword must be turned on before the voice call debug command can be used.

all

All VTSP debugging except stats, tone, and event is enabled.

dsp

Digital signal processor (DSP) message trace is enabled.

error

VTSP error debugging is enabled.

event

State machine debugging is enabled.

session

Session debugging is enabled.

stats

Statistics debugging is enabled.

tone

Tone debugging is enabled.

rtp

Real-Time Transport Protocol (RTP) debugging is enabled.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(3)T


12.0(7)XK

This command was introduced on the Cisco 2600 series router, Cisco 3600 series router, and MC3810 multiservice access concentrators.

12.1(2)T


12.2(11)T

The enhancement of debug capabilities, which affects this command by adding a single call identification header, for Cisco voice gateways was added to the following Cisco routers: Cisco 2600 series, Cisco 3620, Cisco 3640, and Cisco 3660 series; on the following universal gateways: Cisco AS5350, Cisco AS5400, and Cisco AS5850; on the following access servers: Cisco AS5300, and Cisco AS5800; and, on the Cisco MC3810 multiservice access concentrators.


DB-2576

May 2008


Examples

Release

Modification

12.3(8)T

This command was replaced by the debug voip vtsp command.

12.2SX


The following is sample output for a Cisco AS5300 and Cisco 3640 when the debug vtsp all command is entered: Cisco AS5300 Access Server Router# debug vtsp all ! Voice telephony call control all debugging is on ! 00:10:53: %SYS-5-CONFIG_I: Configured from console by console 00:10:54: %SYS-5-CONFIG_I: Configured from console by console ! 00:11:09: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: 00:11:09: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: 00:11:09: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind: 00:11:09: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind:

Cisco 3640 Router 3640-orig# debug vtsp all ! Voice telephony call control all debugging is on ! 3640-orig# show debug Voice Telephony session debugging is on Voice Telephony dsp debugging is on Voice Telephony error debugging is on ! 20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_apply_voiceport_xrule: 20:58:16: vtsp_tsp_apply_voiceport_xrule: vtsp_sdb 0x63797720; called_number 0x6294E0F0 called_oct3 128 20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_apply_voiceport_xrule: 20:58:16: vtsp_tsp_apply_voiceport_xrule: No called number translation rule configured 20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: . 20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_do_regxrule_translate: calling_number(original)= calling_number(xlated)=8880000 called_number(original)= called_number(xlated)=8881111 redirectNumber(original)= redirectNumber(xlated)= 20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_call_setup_ind: (sdb=0x63797720, tdm_info=0x0, tsp_info=0x63825254, calling_number=8880000 calling_oct3 = 0x0, called_number=8881111 called_oct3 = 0x80, oct3a=0 3640-orig#x80): peer_tag=70


DB-2577


20:58:16: //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:():-1:-1:-1/vtsp_tsp_fill_setup_ind: ev.clg.clir is 0 ev.clg.clid_transparent is 0 ev.clg.null_orig_clg is 0 ev.clg.calling_translated is false //-1/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/VTSP:(3/0:23):-1:0:0/vtsp_do_call_setup_ind: Call ID=101123, guid=63EB9AC8


Related Commands

debug vtsp all Field Descriptions

Field

Description

VTSP:():-1:-1:-1

Identifies the VTSP module, port name, channel number, DSP slot, and DSP channel number.

vtsp_tsp_apply_voiceport_xrule:

Identifies a function name.

called_number

Identifies a called number.

called

Identifies the date the call was made.

peer_tag

Identifies the dial peer number.

guid

Identifies the GUID (hexadecimal address).

Command

Description

debug voip ccapi


voice call debug

Debugs a voice call by displaying a full GUID or header.


DB-2578

May 2008

Debug Commands debug vwic-mft firmware controller

debug vwic-mft firmware controller To display debug output from the multiflex (MFT) Voice/WAN interface card (VWIC) controller firmware, use the debug vwic-mft firmware controller command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vwic-mft firmware controller {t1 | e1} slot/port {alarm | all | config | fdl | loopback | register display | status} no debug vwic-mft firmware controller {t1 | e1} slot/port {alarm | all | config | fdl | loopback | register display | status}

Syntax Description

t1

Displays debugging messages for T1 channels.

e1

Displays debugging messages for E1 channels.

slot

Slot number. Refer to the appropriate hardware manual for slot information.

port

Port number. Refer to the appropriate hardware manual for port information. The slash mark is required between the slot argument and the port argument.

alarm

Displays firmware alarm messages.

all

Displays all debugging messages about the MFT VWIC.

config

Displays firmware output messages about configuration change messages sent by the Cisco IOS software.

fdl

Displays firmware output messages when select facilities data link (FDL) events occur.

loopback

Displays firmware output messages when select loopback events occur.

register display

Displays a full framer register value table.

status

Displays current attributes enabled for the specified controller.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.3(6)


12.3(7)T


12.2SX


Usage Guidelines

Use the debug vwic-mft firmware controller command in privileged EXEC mode to provide firmware-level information for VWICs when information is required beyond the Cisco IOS T1 and E1 controller statistics. The physical-layer information generated by this command includes alarm conditions, line status, controller issues, and register settings, all of which can be used to help troubleshoot MFT VWIC problems.


DB-2579


All the debugging keywords, except register display, enable debugging on both ports of a 2-port card. For example, if T1 0/0 and T1 0/1 are two ports on a 2-port MFT card and any of the keywords except register display is enabled, debugging output will be generated for both ports because they share a common firmware system. The Cisco 1- and 2-port T1/E1 multiflex VWICs support voice and data applications in Cisco 2600, Cisco 3600, and Cisco 3700 series multiservice routers. The multiflex VWIC combines WAN interface card and voice interface card functionality.

Caution

Examples

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

The following sample output displays firmware output about alarm messages for an MFT VWIC installed in slot 0. Router# debug vwic-mft firmware controller e1 0/0 alarm vwic-mft firmware output messages for wic slot set to: Alarm Router# *Mar 4 13:58:14.702: E1T1 0/1 FW: alm1:0e p:01 ALOS LOS LOF *Mar 4 13:58:15.194: E1T1 0/1 FW: CERR: 00 *Mar 4 13:58:15.194: E1T1 0/1 FW: MERR: 00 *Mar 4 13:58:15.194: E1T1 0/1 FW: FERR: 00

Note

The output will vary depending on what the router is configured to do after the debug command is entered. Table 397 describes the significant fields shown in the display. Table 397

debug vwic-mft firmware controller alarm Field Descriptions

Field

Description

vwic-mft firmware output messages Acknowledges that the command has been entered and for wic slot set to indicates the current state. *Mar 4 13:58:14.702: E1T1 0/1 FW Time-stamp preface that shows that this is a firmware (FW) message. Note

The port numbers reported here may differ from the numbers configured using the Cisco IOS software because the error is being reported from the second port where debugging has been enabled by the alarm keyword on a 2-port MFT card.

alm1:0e

Actual value of the alarm status register.

p:01

Port number of the local VWIC port that is reporting the condition. Value is either 0 or 1 for each port. Note

The output shows two port numbers; this is an example of the debugging being enabled for both ports on a 2-port MFT card.


DB-2580

May 2008


Table 397

debug vwic-mft firmware controller alarm Field Descriptions (continued)

Field

Description

ALOS LOS LOF

Shorthand value of current alarm conditions defined in the register. One of the following: •

AIS—Receive Alarm Indication Signal

•

ALOS—Receive Analog Loss of Signal

•

LOF—Receive Loss of Frame Alignment

•

LOS—Receive Loss of Signal

•

MYEL—Receive Multiframe Yellow Alarm

•

YEL—Receive Yellow Alarm

Register value showing the actual value of the alarm status register.

Related Commands

CERR

Status of the error status register; cyclical redundancy check (CRC) block error.

MERR

Status of the error status register; multiframe alignment signal (MFAS) pattern error (E1 only).

FERR

Status of the error status register; framing error.

show controllers e1

Displays information about E1 links.

show controllers t1

Displays information about T1 links.


DB-2581

Debug Commands debug vxml

debug vxml Note

Effective with release 12.3(8)T, the debug vxml command is replaced by the debug voip application vxml command. See the debug voip application vxml command for more information. To display debugging messages for VoiceXML features, use the debug vxml command in privileged EXEC mode. To disable debugging output, use the no form of this command. debug vxml [all | application | background | error | event | grammar | puts | ssml | trace | warning] no debug vxml [all | application | background | error | event | grammar | puts | ssml | trace | warning]

Syntax Description

all

(Optional) Displays all VoiceXML debugging messages.

application

(Optional) Displays VoiceXML application states information.

background

(Optional) Displays VoiceXML background messages.

error

(Optional) Displays VoiceXML application error messages.

event

(Optional) Displays VoiceXML asynchronous events.

grammar

(Optional) Enables syntax checking of XML grammar by the VoiceXML interpreter and displays syntax debugging messages.

puts

(Optional) Displays the results of VoiceXML and