ATM Conditional Debug Support
Available Languages
Table Of Contents
Prerequisites for ATM Conditional Debug Support
Restrictions for ATM Conditional Debug Support
Information About ATM Conditional Debug Support
ATM Debugging Extended to the Virtual Circuit Level
How to Configure Conditional Debugging on ATM Interfaces
Enabling Debugging for the ATM Interface
Verifying ATM Conditional Debug Support
Configuration Examples for ATM Conditional Debug Support
Enabling Debugging for a Specific ATM Interface and VPI/VCI Pair: Example
Enabling Debugging for a Specific VCI: Example
Feature Information for ATM Conditional Debug Support
ATM Conditional Debug Support
First Published: May 7, 2004Last Updated: November 20, 2009Most ATM debugging commands are implemented either at the system level or at the interface level. The ATM Conditional Debug Support feature uses the debug condition interface command for debugging to be limited specifically to an ATM interface, to a virtual channel identifier (VCI), or to a virtual path identifier/virtual channel identifier (VPI/VCI) pair.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for ATM Conditional Debug Support" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for ATM Conditional Debug Support
•
•
•
•
•
Prerequisites for ATM Conditional Debug Support
Before you can use the ATM Conditional Debug Support feature, one or more ATM-encapsulated interfaces must be enabled, and one or more of the following debug commands must be enabled:
•
•
•
•
•
•
•
Restrictions for ATM Conditional Debug Support
•
•
Information About ATM Conditional Debug Support
Before using the ATM Conditional Debug Support feature, you should understand the following concept:
•
ATM Debugging Extended to the Virtual Circuit Level
The ATM debug commands are implemented either at the interface level or at the system level. The debug command output at these levels is not very useful when the user is interested in a particular set of VCs.
The Cisco IOS software has the infrastructure to support conditional debugging based on various filters that are set at the command-line interface (CLI). The conditional debugging infrastructure can filter out or suppress unwanted messages from the output of any existing debug command. The ATM Conditional Debug Support feature extends the support of this infrastructure to enable conditional debugging at the ATM VC level by extending the debug condition interface command with keywords that address specific virtual circuits. This feature can be implemented on top of conventional debugging, so that backward compatibility is ensured and at the same time applications can take advantage of conditional debugging where required. However, the extended debug condition interface command has priority over the older version of the command; that is, a debug condition setting using the older debug condition interface command will be discarded as soon as a new debug condition is enabled on a virtual circuit.
How to Configure Conditional Debugging on ATM Interfaces
The following sections describe how to configure an ATM PVC for conditional debugging and enable debugging for the ATM interface:
•
•
Enabling Debugging for the ATM Interface
The task in this section enables conditional debugging on a set of specified interfaces. For information on configuring an ATM interface, refer to the documents listed in the "Additional References" section.
Prerequisites
You must turn on ATM debugging and specify the conditions (interface, VCI, or VPI/VCI pair) for the ATM Conditional Debug Support feature to work.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Verifying ATM Conditional Debug Support
To verify that the ATM Conditional Debug Support feature is working correctly, perform this task.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Configuration Examples for ATM Conditional Debug Support
This section provides the following configuration example:
•
•
Enabling Debugging for a Specific ATM Interface and VPI/VCI Pair: Example
The following example enables an ATM interface, specifies an IP address for the interface, enables conditional debugging for that interface with a VPI/VCI pair of 255/62610, and verifies that debugging has been enabled:
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 2/0Router(config-if)# ip address 209.165.201.2 255.255.255.0Router(config-if)# pvc 255/62610Router(config-if-atm-vc)# no shutdownRouter(config-if)# exitRouter(config)# exitRouter#2w3d: %SYS-5-CONFIG_I: Configured from console by consoleRouter# debug atm stateATM VC States debugging is onRouter# debug condition interface atm 2/0 vc 255/62610Condition 1 setRouter#2w3d: ATM VC Debug: Condition 1, atm-vc 255/62610 AT2/0 triggered, count 1Router# show debug conditionCondition 1: atm-vc 255/62610 AT2/0 (1 flags triggered)Flags: ATM VC
Enabling Debugging for a Specific VCI: Example
The following example shows how to enable conditional debugging on a specific VCI. Note that when you enable conditional debugging on a specific VCI alone, the VPI value is automatically set to "0".
Router# debug condition interface atm 1/0 vc 4335Condition 1 setRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface atm 1/0Router(config-if)# pvc 4335Router(config-if-atm-vc)# endRouter#*Jul 12 21:46:52.487: atmdx_setup_vc(ATM1/0): vc=5, vpi=0, vci=4335, config_status=0*Jul 12 21:46:52.487: atmdx_setup_cos(ATM1/0): vc=5, wred_name=, max_q=0*Jul 12 21:46:52.487: ATM VC Debug: Condition 1, atm-vc 0/4335 AT1/0 triggered, count 1*Jul 12 21:46:52.487: ATM1/0 Current Active VC count 4*Jul 12 21:46:52.487: ATM VC notification event 0*Jul 12 21:46:52.487: atmdx_platform_set_vc_state(ATM1/0): Setting the VC 5 state to UP*Jul 12 21:46:52.487: ATM: PVC activated, ATM1/0 VCD 5 (0/4335)*Jul 12 21:46:52.487: ATM VC notification event 2*Jul 12 21:46:52.487: %SYS-5-CONFIG_I: Configured from console by consoleRouter# show atm vcCodes: DN - DOWN, IN - INACTIVEVCD / Peak Av/Min BurstInterface Name VPI VCI Type Encaps SC Kbps Kbps Cells St1/0 1 0 16 PVC ILMI UBR 149760 UP1/0.10 4 0 100 PVC SNAP UBR 149760 UP1/0 5 0 4335 PVC SNAP UBR 149760 UP1/0.1 one 1 40 PVC SNAP UBR 149760 UP1/0 2 3 100 PVC-A SNAP VBR 1000 1000 0 IN4/ima1 1 23 34 PVC SNAP UBR 0 INAdditional References
The following sections provide references related to the ATM Conditional Debug Support feature.
Related Documents
ATM commands: complete command syntax, defaults, command mode, command history, usage guidelines, and examples.
Conditionally triggered debugging
"Conditionally Triggered Debugging" chapter in the Cisco IOS Debug Command Reference
Configuring ATM
Cisco IOS commands
Standards
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for ATM Conditional Debug Support
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 Feature Information for ATM Conditional Debug Support
ATM Conditional Debug Support
12.0(28)S
12.2(27)SBC
12.2(28)SB
12.2(33)SRE
15.0(1)MATM Conditional Debug Support feature allows debugging to be limited specifically to an ATM interface, to a VCI or to a VPI/VCI pair.
The following section provides information about this feature:
•
The following command was modified:
debug condition interface.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, 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, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, 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. (0908R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2004-2009 Cisco Systems, Inc. All rights reserved.
Feedback