cisco ios debug command reference 12.2

Cisco IOS Debug Command ReferenceRelease 12.2

Corporate 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 526-4100

Customer Order Number: DOC-7812254= Text Part Number: 78-12254-01

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 UCBs 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. AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All Thats Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other brands, names, or trademarks mentioned in this document or Web site 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. (0102R) Cisco IOS Debug Command Reference Copyright 2001, Cisco Systems, Inc. All rights reserved.

C O N T E N T S

About Cisco IOS Software Documentation Using Cisco IOS Software Using Debug Commands1 7 xiii

v

Conditionally Triggered Debugging Debug Commands Appendixes Index13

Cisco IOS Debug Command Reference

iii

Contents


iv

About Cisco IOS Software DocumentationThis chapter discusses the objectives, audience, organization, and conventions of Cisco IOS software documentation. It also provides sources for obtaining documentation from Cisco Systems.

Documentation ObjectivesCisco IOS software documentation describes the tasks and commands necessary to configure and maintain Cisco networking devices.

AudienceThe Cisco IOS software documentation set is intended primarily for users who configure and maintain Cisco networking devices (such as routers and switches) but who may not be familiar with the tasks, the relationship between tasks, or the Cisco IOS software commands necessary to perform particular tasks. The Cisco IOS software documentation set is also intended for those users experienced with Cisco IOS software who need to know about new features, new configuration options, and new software characteristics in the current Cisco IOS software release.

Documentation OrganizationThe Cisco IOS software documentation set consists of documentation modules and master indexes. In addition to the main documentation set, there are supporting documents and resources.

Documentation ModulesThe Cisco IOS documentation modules consist of configuration guides and corresponding command reference publications. Chapters in a configuration guide describe protocols, configuration tasks, and Cisco IOS software functionality and contain comprehensive configuration examples. Chapters in a command reference publication provide complete Cisco IOS command syntax information. Use each configuration guide in conjunction with its corresponding command reference publication.


v

About Cisco IOS Software Documentation Documentation Organization

Figure 1 shows the Cisco IOS software documentation modules.

Note

The abbreviations (for example, FC and FR) next to the book icons are page designators, which are defined in a key in the index of each document to help you with navigation. The bullets under each module list the major technology areas discussed in the corresponding books.

Figure 1

Cisco IOS Software Documentation ModulesIPC IP1RCisco IOS IP Command Reference, Volume 1 of 3: Addressing and Services

FC

Cisco IOS Configuration Fundamentals Configuration Guide

Cisco IOS IP Configuration Guide

P2C

Cisco IOS AppleTalk and Novell IPX Configuration Guide

P3C

IP3RCisco IOS AppleTalk and Novell IPX Command Reference

Cisco IOS Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Configuration Guide Cisco IOS Apollo Domain, Banyan VINES, DECnet, ISO CLNS, and XNS Command Reference

FR

Cisco IOS Configuration Fundamentals Command Reference

IP2R

Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols

Cisco IOS IP Command Reference, Volume 3 of 3: Multicast

P2R

P3R

Module FC/FR: Cisco IOS User Interfaces File Management System Management

Module IPC/IP1R/IP2R/IP3R: IP Addressing and Services IP Routing Protocols IP Multicast

Module P2C/P2R: AppleTalk Novell IPX

Module P3C/P3R: Apollo Domain Banyan VINES DECnet ISO CLNS XNS

WC

Cisco IOS Wide-Area Networking Configuration Guide

IC

Cisco IOS Interface Configuration Guide

MWC

Cisco IOS Mobile Wireless Configuration Guide

SC

Cisco IOS Security Configuration Guide

WR

Cisco IOS Wide-Area Networking Command Reference

IR

Cisco IOS Interface Command Reference

MWR

Cisco IOS Mobile Wireless Command Reference

SR

Cisco IOS Security Command Reference

Module WC/WR: ATM Broadband Access Frame Relay SMDS X.25 and LAPB

Module IC/IR: LAN Interfaces Serial Interfaces Logical Interfaces

Module MWC/MWR: General Packet Radio Service

Module SC/SR: AAA Security Services Security Server Protocols Traffic Filtering and Firewalls IP Security and Encryption Passwords and Privileges Neighbor Router Authentication IP Security Options Supported AV Pairs


vi

47953


DC

Cisco IOS Dial Technologies Configuration Guide

TC

Cisco IOS Terminal Services Configuration Guide

BC

Cisco IOS Bridging and IBM Networking Configuration Guide

B1RCisco IOS Dial Technologies Command Reference Cisco IOS Terminal Services Command Reference Cisco IOS Bridging and IBM Networking Command Reference, Volume 1 of 2

B2RCisco IOS Bridging and IBM Networking Command Reference, Volume 2 of 2

DR

TR

Module DC/DR: Preparing for Dial Access Modem and Dial Shelf Configuration and Management ISDN Configuration Signalling Configuration Dial-on-Demand Routing Configuration Dial-Backup Configuration Dial-Related Addressing Services Virtual Templates, Profiles, and Networks PPP Configuration Callback and Bandwidth Allocation Configuration Dial Access Specialized Features Dial Access Scenarios

Module TC/TR: ARA LAT NASI Telnet TN3270 XRemote X.28 PAD Protocol Translation

Module BC/B1R: Transparent Bridging SRB Token Ring Inter-Switch Link Token Ring Route Switch Module RSRB DLSw+ Serial Tunnel and Block Serial Tunnel LLC2 and SDLC IBM Network Media Translation SNA Frame Relay Access NCIA Client/Server Airline Product Set

Module BC/B2R: DSPU and SNA Service Point SNA Switching Services Cisco Transaction Connection Cisco Mainframe Channel Connection CLAW and TCP/IP Offload CSNA, CMPC, and CMPC+ TN3270 Server

VC

Cisco IOS Voice, Video, and Fax Configuration Guide

QC

Cisco IOS Quality of Service Solutions Configuration Guide

XC

Cisco IOS Switching Services Configuration Guide

VR

Cisco IOS Voice, Video, and Fax Command Reference

QR

Cisco IOS Quality of Service Solutions Command Reference

XR

Cisco IOS Switching Services Command Reference

Module VC/VR: Voice over IP Call Control Signalling Voice over Frame Relay Voice over ATM Telephony Applications Trunk Management Fax, Video, and Modem Support

Module QC/QR: Packet Classification Congestion Management Congestion Avoidance Policing and Shaping Signalling Link Efficiency Mechanisms

Module XC/XR: Cisco IOS Switching Paths NetFlow Switching Multiprotocol Label Switching Multilayer Switching Multicast Distributed Switching Virtual LANs LAN Emulation


47954

vii


Master IndexesTwo master indexes provide indexing information for the Cisco IOS software documentation set: an index for the configuration guides and an index for the command references. Individual books also contain a book-specific index. The master indexes provide a quick way for you to find a command when you know the command name but not which module contains the command. When you use the online master indexes, you can click the page number for an index entry and go to that page in the online document.

Supporting Documents and ResourcesThe following documents and resources support the Cisco IOS software documentation set:

Cisco IOS Command Summary (two volumes)This publication explains the function and syntax of the Cisco IOS software commands. For more information about defaults and usage guidelines, refer to the Cisco IOS command reference publications. Cisco IOS System Error MessagesThis publication lists and describes Cisco IOS system error messages. Not all system error messages indicate problems with your system. Some are purely informational, and others may help diagnose problems with communications lines, internal hardware, or the system software. Cisco IOS Debug Command ReferenceThis publication 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, and sample output. Dictionary of Internetworking Terms and AcronymsThis Cisco publication compiles and defines the terms and acronyms used in the internetworking industry. New feature documentationThe Cisco IOS software documentation set documents the mainline release of Cisco IOS software (for example, Cisco IOS Release 12.2). New software features are introduced in early deployment releases (for example, the Cisco IOS T release train for 12.2, 12.2(x)T). Documentation for these new features can be found in standalone documents called feature modules. Feature module documentation describes new Cisco IOS software and hardware networking functionality and is available on Cisco.com and the Documentation CD-ROM. Release notesThis documentation describes system requirements, provides information about new and changed features, and includes other useful information about specific software releases. See the section Using Software Release Notes in the chapter Using Cisco IOS Software for more information. Caveats documentationThis documentation provides information about Cisco IOS software defects in specific software releases. RFCsRFCs are standards documents maintained by the Internet Engineering Task Force (IETF). Cisco IOS software documentation references supported RFCs when applicable. The full text of referenced RFCs may be obtained on the World Wide Web at http://www.rfc-editor.org/. MIBsMIBs are used for network monitoring. For lists of supported MIBs by platform and release, and to download MIB files, see the Cisco MIB website on Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.


viii

About Cisco IOS Software Documentation Document Conventions

Document ConventionsWithin Cisco IOS software documentation, the term router is generally used to refer to a variety of Cisco products (for example, routers, access servers, and switches). Routers, access servers, and other networking devices that support Cisco IOS software are shown interchangeably within examples. These products are used only for illustrative purposes; that is, an example that shows one product does not necessarily indicate that other products are not supported. The Cisco IOS documentation set uses the following conventions: Convention ^ or Ctrl Description The ^ and Ctrl symbols represent the Control key. For example, the key combination ^D or Ctrl-D means hold down the Control key while you press the D key. Keys are indicated in capital letters but are not case sensitive. A string is a nonquoted set of characters shown in italics. For example, when setting an SNMP community string to public, do not use quotation marks around the string or the string will include the quotation marks. Command syntax descriptions use the following conventions: Convention boldface italics [x] | [x | y] {x | y} Description Boldface text indicates commands and keywords that you enter literally as shown. Italic text indicates arguments for which you supply values. Square brackets enclose an optional element (keyword or argument). A vertical line indicates a choice within an optional or required set of keywords or arguments. Square brackets enclosing keywords or arguments separated by a vertical line indicate an optional choice. Braces enclosing keywords or arguments separated by a vertical line indicate a required choice. Nested sets of square brackets or braces indicate optional or required choices within optional or required elements. For example: Convention [x {y | z}] Description Braces and a vertical line within square brackets indicate a required choice within an optional element. Examples use the following conventions: Conventionscreen boldface screen

string

Description Examples of information displayed on the screen are set in Courier font. Examples of text that you must enter are set in Courier bold font. Angle brackets enclose text that is not printed to the screen, such as passwords.


ix

About Cisco IOS Software Documentation Obtaining Documentation

Convention ! [ ]

Description An exclamation point at the beginning of a line indicates a comment line. (Exclamation points are also displayed by the Cisco IOS software for certain processes.) Square brackets enclose default responses to system prompts. The following conventions are used to attract the attention of the reader:

Caution

Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Note

Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.

Timesaver

Means the described action saves time. You can save time by performing the action described in the paragraph.

Obtaining DocumentationThe following sections provide sources for obtaining documentation from Cisco Systems.

World Wide WebThe most current Cisco documentation is available on the World Wide Web at the following website: http://www.cisco.com Translated documentation is available at the following website: http://www.cisco.com/public/countries_languages.html

Documentation CD-ROMCisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering DocumentationCisco documentation can be ordered in the following ways:

Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:


x

About Cisco IOS Software Documentation Documentation Feedback

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store: http://www.cisco.com/go/subscription Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation FeedbackIf you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. You can e-mail your comments to [email protected]. To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address: Cisco Systems, Inc. Document Resource Connection 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments.

Obtaining Technical AssistanceCisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.comCisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco. Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available. Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco. To access Cisco.com, go to the following website: http://www.cisco.com


xi

About Cisco IOS Software Documentation Obtaining Technical Assistance

Technical Assistance CenterThe Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC WebsiteIf you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website: http://www.cisco.com/tac P3 and P4 level problems are defined as follows:

P3Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue. P4You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions. To register for Cisco.com, go to the following website: http://www.cisco.com/register/ If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website: http://www.cisco.com/tac/caseopen

Contacting TAC by TelephoneIf you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml P1 and P2 level problems are defined as follows:

P1Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available. P2Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.


xii

Using Cisco IOS SoftwareThis chapter provides helpful tips for understanding and configuring Cisco IOS software using the command-line interface (CLI). It contains the following sections:

Understanding Command Modes Getting Help Using the no and default Forms of Commands Saving Configuration Changes Filtering Output from the show and more Commands Identifying Supported Platforms

For an overview of Cisco IOS software configuration, refer to the Cisco IOS Configuration Fundamentals Configuration Guide. For information on the conventions used in the Cisco IOS software documentation set, see the chapter About Cisco IOS Software Documentation located at the beginning of this book.

Understanding Command ModesYou use the CLI to access Cisco IOS software. Because the CLI is divided into many different modes, the commands available to you at any given time depend on the mode you are currently in. Entering a question mark (?) at the CLI prompt allows you to obtain a list of commands available for each command mode. When you log in to the CLI, you are in user EXEC mode. User EXEC mode contains only a limited subset of commands. To have access to all commands, you must enter privileged EXEC mode, normally by using a password. From privileged EXEC mode you can issue any EXEC commanduser or privileged modeor you can enter global configuration mode. Most EXEC commands are one-time commands. For example, show commands show important status information, and clear commands clear counters or interfaces. The EXEC commands are not saved when the software reboots. Configuration modes allow you to make changes to the running configuration. If you later save the running configuration to the startup configuration, these changed commands are stored when the software is rebooted. To enter specific configuration modes, you must start at global configuration mode. From global configuration mode, you can enter interface configuration mode and a variety of other modes, such as protocol-specific modes. ROM monitor mode is a separate mode used when the Cisco IOS software cannot load properly. If a valid software image is not found when the software boots or if the configuration file is corrupted at startup, the software might enter ROM monitor mode.


xiii

Using Cisco IOS Software Getting Help

Table 1 describes how to access and exit various common command modes of the Cisco IOS software. It also shows examples of the prompts displayed for each mode.Table 1 Accessing and Exiting Command Modes

Command Mode User EXEC Privileged EXEC Global configuration

Access Method Log in. From user EXEC mode, use the enable EXEC command. From privileged EXEC mode, use the configure terminal privileged EXEC command. From global configuration mode, specify an interface using an interface command. From privileged EXEC mode, use the reload EXEC command. Press the Break key during the first 60 seconds while the system is booting.

PromptRouter> Router#

Exit Method Use the logout command. To return to user EXEC mode, use the disable command. To return to privileged EXEC mode from global configuration mode, use the exit or end command, or press Ctrl-Z. To return to global configuration mode, use the exit command. To return to privileged EXEC mode, use the end command, or press Ctrl-Z.

Router(config)#

Interface configuration

Router(config-if)#

ROM monitor

>

To exit ROM monitor mode, use the continue command.

For more information on command modes, refer to the Using the Command-Line Interface chapter in the Cisco IOS Configuration Fundamentals Configuration Guide.

Getting HelpEntering a question mark (?) at the CLI prompt displays a list of commands available for each command mode. You can also get a list of keywords and arguments associated with any command by using the context-sensitive help feature. To get help specific to a command mode, a command, a keyword, or an argument, use one of the following commands: Commandhelp abbreviated-command-entry?

Purpose Provides a brief description of the help system in any command mode. Provides a list of commands that begin with a particular character string. (No space between command and question mark.) Completes a partial command name. Lists all commands available for a particular command mode. Lists the keywords or arguments that you must enter next on the command line. (Space between command and question mark.)

abbreviated-command-entry ? command ?


xiv


Example: How to Find Command OptionsThis section provides an example of how to display syntax for a command. The syntax can consist of optional or required keywords and arguments. To display keywords and arguments for a command, enter a question mark (?) at the configuration prompt or after entering part of a command followed by a space. The Cisco IOS software displays a list and brief description of available keywords and arguments. For example, if you were in global configuration mode and wanted to see all the keywords or arguments for the arap command, you would type arap ?. The symbol in command help output stands for carriage return. On older keyboards, the carriage return key is the Return key. On most modern keyboards, the carriage return key is the Enter key. The symbol at the end of command help output indicates that you have the option to press Enter to complete the command and that the arguments and keywords in the list preceding the symbol are optional. The symbol by itself indicates that no more arguments or keywords are available and that you must press Enter to complete the command. Table 2 shows examples of how you can use the question mark (?) to assist you in entering commands. The table steps you through configuring an IP address on a serial interface on a Cisco 7206 router that is running Cisco IOS Release 12.0(3).Table 2 How to Find Command Options

CommandRouter> enable Password: Router#

Comment Enter the enable command and password to access privileged EXEC commands. You are in privileged EXEC mode when the prompt changes to Router#. Enter the configure terminal privileged EXEC command to enter global configuration mode. You are in global configuration mode when the prompt changes to Router(config)#. Enter interface configuration mode by specifying the serial interface that you want to configure using the interface serial global configuration command. Enter ? to display what you must enter next on the command line. In this example, you must enter the serial interface slot number and port number, separated by a forward slash. You are in interface configuration mode when the prompt changes toRouter(config-if)#.

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#

Router(config)# interface serial ? Serial interface number Router(config)# interface serial 4 ? / Router(config)# interface serial 4/ ? Serial interface number Router(config)# interface serial 4/0 Router(config-if)#


xv


Table 2

How to Find Command Options (continued)

CommandRouter(config-if)# ? Interface configuration commands: . . . ip Interface Internet Protocol config commands keepalive Enable keepalive lan-name LAN Name command llc2 LLC2 Interface Subcommands load-interval Specify interval for load calculation for an interface locaddr-priority Assign a priority group logging Configure logging for interface loopback Configure internal loopback on an interface mac-address Manually set interface MAC address mls mls router sub/interface commands mpoa MPOA interface configuration commands mtu Set the interface Maximum Transmission Unit (MTU) netbios Use a defined NETBIOS access list or enable name-caching no Negate a command or set its defaults nrzi-encoding Enable use of NRZI encoding ntp Configure NTP . . . Router(config-if)# Router(config-if)# ip ? Interface IP configuration subcommands: access-group Specify access control for packets accounting Enable IP accounting on this interface address Set the IP address of an interface authentication authentication subcommands bandwidth-percent Set EIGRP bandwidth limit broadcast-address Set the broadcast address of an interface cgmp Enable/disable CGMP directed-broadcast Enable forwarding of directed broadcasts dvmrp DVMRP interface commands hello-interval Configures IP-EIGRP hello interval helper-address Specify a destination address for UDP broadcasts hold-time Configures IP-EIGRP hold time . . . Router(config-if)# ip

Comment Enter ? to display a list of all the interface configuration commands available for the serial interface. This example shows only some of the available interface configuration commands.

Enter the command that you want to configure for the interface. This example uses the ip command. Enter ? to display what you must enter next on the command line. This example shows only some of the available interface IP configuration commands.


xvi

Using Cisco IOS Software Using the no and default Forms of Commands

Table 2

How to Find Command Options (continued)

CommandRouter(config-if)# ip address ? A.B.C.D IP address negotiated IP Address negotiated over PPP Router(config-if)# ip address

Comment Enter the command that you want to configure for the interface. This example uses the ip address command. Enter ? to display what you must enter next on the command line. In this example, you must enter an IP address or the negotiated keyword. A carriage return () is not displayed; therefore, you must enter additional keywords or arguments to complete the command.

Router(config-if)# ip address 172.16.0.1 ? A.B.C.D IP subnet mask Router(config-if)# ip address 172.16.0.1

Enter the keyword or argument you want to use. This example uses the 172.16.0.1 IP address. Enter ? to display what you must enter next on the command line. In this example, you must enter an IP subnet mask. A is not displayed; therefore, you must enter additional keywords or arguments to complete the command.

Router(config-if)# ip address 172.16.0.1 255.255.255.0 ? secondary Make this IP address a secondary address Router(config-if)# ip address 172.16.0.1 255.255.255.0

Enter the IP subnet mask. This example uses the 255.255.255.0 IP subnet mask. Enter ? to display what you must enter next on the command line. In this example, you can enter the secondary keyword, or you can press Enter. A is displayed; you can press Enter to complete the command, or you can enter another keyword.

Router(config-if)# ip address 172.16.0.1 255.255.255.0 Router(config-if)#

In this example, Enter is pressed to complete the command.

Using the no and default Forms of CommandsAlmost every configuration command has a no form. In general, use the no form to disable a function. Use the command without the no keyword to reenable a disabled function or to enable a function that is disabled by default. For example, IP routing is enabled by default. To disable IP routing, use the no ip routing command; to reenable IP routing, use the ip routing command. The Cisco IOS software command reference publications provide the complete syntax for the configuration commands and describe what the no form of a command does. Configuration commands also can have a default form, which returns the command settings to the default values. Most commands are disabled by default, so in such cases using the default form has the same result as using the no form of the command. However, some commands are enabled by default and


xvii

Using Cisco IOS Software Saving Configuration Changes

have variables set to certain default values. In these cases, the default form of the command enables the command and sets the variables to their default values. The Cisco IOS software command reference publications describe the effect of the default form of a command if the command functions differently than the no form.

Saving Configuration ChangesUse the copy system:running-config nvram:startup-config command to save your configuration changes to the startup configuration so that the changes will not be lost if the software reloads or a power outage occurs. For example:Router# copy system:running-config nvram:startup-config Building configuration...

It might take a minute or two to save the configuration. After the configuration has been saved, the following output appears:[OK] Router#

On most platforms, this task saves the configuration to NVRAM. On the Class A Flash file system platforms, this task saves the configuration to the location specified by the CONFIG_FILE environment variable. The CONFIG_FILE variable defaults to NVRAM.

Filtering Output from the show and more CommandsIn Cisco IOS Release 12.0(1)T and later releases, you can search and filter the output of show and more commands. This functionality is useful if you need to sort through large amounts of output or if you want to exclude output that you need not see. To use this functionality, enter a show or more command followed by the pipe character (|); one of the keywords begin, include, or exclude; and a regular expression on which you want to search or filter (the expression is case-sensitive): command | {begin | include | exclude} regular-expression The output matches certain lines of information in the configuration file. The following example illustrates how to use output modifiers with the show interface command when you want the output to include only lines in which the expression protocol appears:Router# show interface | include protocol FastEthernet0/0 is up, line protocol is up Serial4/0 is up, line protocol is up Serial4/1 is up, line protocol is up Serial4/2 is administratively down, line protocol is down Serial4/3 is administratively down, line protocol is down

For more information on the search and filter functionality, refer to the Using the Command-Line Interface chapter in the Cisco IOS Configuration Fundamentals Configuration Guide.


xviii

Using Cisco IOS Software Identifying Supported Platforms

Identifying Supported PlatformsCisco IOS software is packaged in feature sets consisting of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release. To identify the set of software images available in a specific release or to find out if a feature is available in a given Cisco IOS software image, see the following sections:

Using Feature Navigator Using Software Release Notes

Using Feature NavigatorFeature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a particular set of features and which features are supported in a particular Cisco IOS image. Feature Navigator is available 24 hours a day, 7 days a week. To access Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, e-mail the Contact Database Administration group at [email protected]. If you do not have an account on Cisco.com, go to http://www.cisco.com/register and follow the directions to establish an account. To use Feature Navigator, you must have a JavaScript-enabled web browser such as Netscape 3.0 or later, or Internet Explorer 4.0 or later. Internet Explorer 4.0 always has JavaScript enabled. To enable JavaScript for Netscape 3.x or Netscape 4.x, follow the instructions provided with the web browser. For JavaScript support and enabling instructions for other browsers, check with the browser vendor. Feature Navigator is updated when major Cisco IOS software releases and technology releases occur. You can access Feature Navigator at the following URL: http://www.cisco.com/go/fn

Using Software Release NotesCisco IOS software releases include release notes that provide the following information:

Platform support information Memory recommendations Microcode support information Feature set tables Feature descriptions Open and resolved severity 1 and 2 caveats for all platforms

Release notes are intended to be release-specific for the most current release, and the information provided in these documents may not be cumulative in providing information about features that first appeared in previous releases.


xix

Using Cisco IOS Software Identifying Supported Platforms


xx

Using Debug CommandsThis chapter explains how you use debug commands to diagnose and resolve internetworking problems. Specifically, it covers the following topics:

Entering debug commands Using the debug ? command Using the debug all command Generating debug command output Redirecting debug and error message output

Caution

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 CommandsAll 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 at : 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 Alternately, you can enter the undebug form of the command in privileged EXEC mode: undebug isdn q931


1

Using Debug Commands Using the debug ? Command

To display the state of each debugging option, enter the following at the command line in privileged EXEC mode: show debugging

Using the debug ? CommandTo list and see a brief description of all the debugging command options, enter the following command in privileged EXEC mode at the command line: debug ? Not all debugging commands listed in the debug ? output are described in this document. Commands are included here based on the 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 CommandTo 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 OutputEnabling 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


2

Using Debug Commands Redirecting debug and Error Message Output

The router continues to generate such output until you enter the corresponding no debug command (in this case, the no debug modem command). 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 OutputBy 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 LoggingTo 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


3


Setting the Message Logging LevelsYou can set the logging levels when logging messages to the following devices:

Console Monitor Syslog server

Table 3 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 3 Message Logging Keywords and Levels

Level 0 1 2 3 4 5 6 7

Keyword emergencies alerts critical errors warnings notification informational debugging

Description System is unusable. Immediate action is needed. Critical conditions exist. Error conditions exist. Warning conditions exist. Normal, but significant, conditions exist. Informational messages. Debugging messages.

Syslog Definition LOG_EMERG LOG_ALERT LOG_CRIT LOG_ERR LOG_WARNING LOG_NOTICE LOG_INFO LOG_DEBUG

Limiting the Types of Logging Messages Sent to the ConsoleTo 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. The level argument is one of the logging keywords listed in Table 3. 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


4


Logging Messages to an Internal BufferThe 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 MonitorTo 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. The level argument is one of the logging keywords listed in Table 3. 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 ServerTo log messages to the syslog server host, use the logging router configuration command. The full syntax of this command follows: logging ip-address no logging ip-address


5


The logging command identifies a syslog server host 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 command deletes the syslog server with the specified address from the list of syslogs.

Limiting Messages to a Syslog ServerTo limit the number of messages sent to the 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. The level argument is one of the keywords listed in Table 3. To send logging messages to a syslog server, specify its host address with the logging command. The default trap level is informational. The no logging trap command disables logging to syslog servers. The current software generates four categories of syslog messages:

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 DaemonTo 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 3 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.log


6

Conditionally Triggered DebuggingWhen 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 only want to see debugging messages 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 message 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 {events | packets} debug isdn {q921 | q931} debug modem {oob | trace} debug ppp {all | authentication | chap | error | negotiation | multilink events | packet}

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. Enabling Protocol-Specific debug Commands Enabling Conditional Debugging Commands Specifying Multiple Conditions

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


7

Conditionally Triggered Debugging Enabling Protocol-Specific debug Commands

Enabling Protocol-Specific debug CommandsTo 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 show debugging debug protocol no debug protocol Purpose Determines which types of debugging are enabled. Enables the desired debugging commands. 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 CommandsIf 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 only display messages 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 InterfaceTo disable debugging messages for all interfaces except one, use the following command in privileged EXEC mode: Command debug condition interface interface Purpose 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 interface command.


8

Conditionally Triggered Debugging Enabling Conditional Debugging Commands

Displaying Messages for Multiple InterfacesTo enable debugging messages for multiple interfaces, use the following commands in privileged EXEC mode: Command debug condition interface interface debug condition interface interface Purpose Disables debugging messages for all interfaces except one. Enables debugging messages for additional interfaces. Repeat this task 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 ConditionsThe 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, then 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 debug condition {username username | called dial-string | caller dial-string} Purpose Enables conditional debugging. The router will display only messages for interfaces that meet this condition.

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


9

Conditionally Triggered Debugging Specifying Multiple Conditions

Specifying Multiple ConditionsTo limit debugging messages based on more than one condition, use the following commands in privileged EXEC mode as needed: Command debug condition {username username | called dial-string | caller dial-string} debug condition {username username | called dial-string | caller dial-string} 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 ExamplesIn 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 *Mar *Mar state *Mar *Mar *Mar *Mar 1 00:04:41.647: 1 00:04:41.715: 1 00:04:42.963: to up 1 00:04:43.271: 1 00:04:43.271: 1 00:04:43.279: 1 00:04:43.283: %LINK-3-UPDOWN: Interface Serial0, changed state to up Se0 Debug: Condition 4, username cisco triggered, count 2 %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed Vi1 Debug: Condition 3, interface Vt1 triggered, count 1 %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up Vi1 Debug: Condition 4, username cisco triggered, count 2 Vi1 Debug: Condition 1, interface Se0 triggered, count 3


10

Conditionally Triggered Debugging Conditionally Triggered Debugging Configuration Examples

*Mar 1 00:04:44.039: %IP-4-DUPADDR: Duplicate address 172.27.32.114 on Ethernet 0, sourced by 00e0.1e3e.2d41 *Mar 1 00:04:44.283: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up *Mar 1 00:04:54.667: %LINK-3-UPDOWN: Interface Serial1, changed state to up *Mar 1 00:04:54.731: Se1 Debug: Condition 4, username cisco triggered, count 2 *Mar 1 00:04:54.735: Vi1 Debug: Condition 2, interface Se1 triggered, count 4 *Mar 1 00:04:55.735: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up

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)


11

Conditionally Triggered Debugging Conditionally Triggered Debugging Configuration Examples


12

Debug CommandsThis 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. 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. Thus, 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.


13

Debug Commands debug aaa accounting

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

Syntax Description

This command has no arguments or keywords.

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 debug aaa authentication debug aaa authorization debug radius debug tacacs

Description Displays information on accountable events as they occur. Displays information on AAA/TACACS+ authorization. Displays information associated with the RADIUS. Displays information associated with the TACACS.


14

Debug Commands debug aaa authentication

debug aaa authenticationTo display information on AAA/Terminal Access Controller Access Control System Plus (TACACS+) authentication, use the debug aaa authentication privileged EXEC command. To disable debugging command, use the no form of the command. debug aaa authentication no debug aaa authentication

Syntax Description


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


15

Debug Commands debug aaa authorization

debug aaa authorizationTo display information on AAA/TACACS+ authorization, use the debug aaa authorization privileged EXEC command. To disable debugging output, use the no form of the command. debug aaa authorization no debug aaa authorization

Syntax Description


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 4 describes AV pairs associated with the debug aaa authorization command that may show up in the debug output.Table 4 Attribute Value Pairs for Authorization

Attribute Value service=arap service=shell service=ppp service=slip

Description Authorization for the ARA protocol is being requested. Authorization for EXEC startup and command authorization is being requested. Authorization for PPP is being requested. Authorization for SLIP is being requested.


16


Table 4

Attribute Value Pairs for Authorization (continued)

Attribute Value protocol=lcp protocol=ip protocol=ipx protocol=atalk protocol=vines protocol=unknown cmd=x

Description Authorization for LCP is being requested (lower layer of PPP). Used with service=slip and service=slip to indicate which protocol layer is being authorized. Used with service=ppp to indicate which protocol layer is being authorized. Used with service=ppp or service=arap to indicate which protocol layer is being authorized. Used with service=ppp for VINES over PPP. Used for undefined or unsupported conditions. 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. 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. 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. Used with service=ppp and protocol=ip. Contains an IP input access list for SLIP or PPP/IP. For example, inacl=2. Used with service=ppp and protocol=ip. Contains an IP output access list for SLIP or PPP/IP. For example, outacl=4. 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. 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. Used with service=arap. The number of minutes before an ARA session disconnects. For example, timeout=60. Used with service=shell and cmd=NULL. Specifies an autocommand to be executed at EXEC startup. For example, autocmd=telnet yxz.com. 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. 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.

cmd-arg=x

acl=x

inacl=x outacl=x addr=x

routing=x

timeout=x autocmd=x noescape=x

nohangup=x


17


Table 4

Attribute Value Pairs for Authorization (continued)

Attribute Value priv-lvl=x

Description 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. Used with service=arap. Specifies an AppleTalk zonelist for ARA. For example, zonelist=5. Used with service=ppp and protocol=ip. Specifies the name of a local pool from which to get the address of the remote host.

zonelist=x addr-pool=x


18

Debug Commands debug aaa pod

debug aaa podTo display debug messages related to POD packets, use the debug aaa pod privileged EXEC command. 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 History

Release 12.1(3)T

Modification This command was introduced.

Examples

The following example shows output from a successful POD request when the show debug command is used.Router# debug aaa pod AAA POD packet processing debugging is on Router# show debug General OS: AAA POD packet processing debugging is on Router# *Jul 9 16:04:32.271:POD:10.100.1.34 request queued *Jul 9 16:04:32.271:POD:10.100.1.34 user 0.0.0.0 sessid 0x0 key 0xA5AFA004 *Jul 9 16:04:32.271:POD: Line User IDB Session Id Key *Jul 9 16:04:32.271:POD:Skip Se0:21 meklund 0.0.0.0 0x0 0x0 *Jul 9 16:04:32.271:POD:KILL Se0:22 meklund 0.0.0.0 0x60000020 0xA5AFA004 *Jul 9 16:04:32.271:POD:Sending ACK to 10.100.1.34/1812 --Interface Se0:22 was killed because the pod request contained a key of 0xA5AFA004 and pod was configured with the command aaa pod server port 1812 auth-type any server-key mykey

Related Commands

Command aaa pod server

Description Enables the POD feature.


19

Debug Commands debug alps ascu

debug alps ascuTo enable debugging for ALPS ASCUs, use the debug alps ascu privileged EXEC command. To disable debugging, 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 packet detail all format {ipars | router | both}

Displays ASCU events or protocol errors. Displays sent or received packets. Displays all ASCU protocol events. Enables event, packet, and detail debugging. Specifies how to display ASCU addresses and the hexadecimal data in the debug output:

iparsDisplays the IPARS hexadecimal output, only. routerDisplays the router hexadecimal output, only. bothDisplays 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 ascu id (Optional) Enables debugging on a specified interface. Applies only to the event, packet, detail, and all keywords. (Optional) Enables debugging for a specified ASCU.

Defaults

Debugging is off.

Command History

Release 11.3(6)T 12.0(1) 12.0(5)T 12.1(2)T

Modification This command was introduced for limited availability. This command was available for general release. This command was modified. The format, ipars, router, and both keywords were added. The output for this command was modified to include IPARS and router formats.

Usage Guidelines

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.


20


Note

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.

Note

To log messages to an internal buffer, use the logging buffered global configuration command. To display the state of logging (syslog), use the show logging privileged EXEC command. For information on these commands and other commands used to customize logs, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals Command Reference.

Examples

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: ALPS ASCU: 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 Tx ALC DATA MSG (14 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6 Tx ALC POLL MSG (3 bytes + CCC + 0 pad bytes) to ascu 42 on i/f Serial6


21


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

The following output is from the debug alps ascu packet command, showing all packets sent or received in both format for ASCU 42 on interface Serial6:Router# debug alps ascu packet Serial6 42


22


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


23

Debug Commands debug alps circuit event

debug alps circuit eventTo enable event debugging for ALPS circuits, use the debug alps circuit event privileged EXEC command. To disable debugging, use the no form of this command. debug alps circuit event [name] no debug alps circuit event [name]

Syntax Description

name

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

Defaults

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

Command History

Release 11.3 T


Usage Guidelines

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 alps-ccpe# debug alps circuit event RTP_AX25 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: Event= DISABLE: Event= ENABLE: 200.100.40.2 Event= RETRY_TIMEOUT: Event= CKT_OPEN_CFM:


24

Debug Commands debug alps peer

debug alps peerTo enable event or packet debugging for ALPS peers, use the debug alps peer privileged EXEC command. To disable debugging, 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 packet ip-address

Specifies debugging for an event. Specifies debugging for a packet. (Optional) Remote peer IP address.

Defaults

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

Command History

Release 11.3(6)T 12.0(1) 12.0(5)T

Modification This command was introduced for limited availability. This command was available for general release. The packet keyword was added. The format for the output was modified for consistency.

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 output is from the debug alps peer packet command:Router# debug alps peer packet ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) 040A5320: 01 00001241 040A5330:45546B5F 6F4F7757 67477B5B 51 ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) 04000550: 01000012 4145546B 5F6F4F77 04000560:5767477B 5B51 ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) 0409F6E0: 01 00001241 45546B5F 0409F6F0:6F4F7757 67477B5B 51 ALPS PEER:Peer (10.227.50.106, MATIP_A_CKT-1) 04000680: 01000012 4145546B 04000690:5F6F4F77 5767477B 5B51 - TX Peer Data Msg (18 bytes)

- RX Peer Data Msg (18 bytes)

- TX Peer Data Msg (18 bytes)

- RX Peer Data Msg (18 bytes)


25

Debug Commands debug alps peer event

debug alps peer eventTo enable event debugging for ALPS peers, use the debug alps peer event privileged EXEC command. To disable debugging, use the no form of this command. debug alps peer event ipaddr no debug alps peer event ipaddr

Syntax Description

ipaddr

(Optional) Peer IP address.

Defaults

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

Command History

Release 11.3 T


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 event command:Router# debug alps peer event ALPS PEER: FSM - Peer 200.100.25.2, Event ALPS_CLOSED_IND, State OPENED ALPS PEER: peer 200.100.25.2 closed - closing peer circuits. ALPS PEER: Promiscuous peer created for 200.100.25.2 ALPS PEER: TCP Listen - passive open 200.100.25.2(11003) -> 10000 ALPS PEER: FSM - Peer 200.100.25.2, Event ALPS_OPEN_IND, State DISCONN ALPS PEER: peer 200.100.25.2 opened OK.


26

Debug Commands debug alps snmp

debug alps snmpTo enable debugging for ALPS SNMP agents, use the debug alps snmp privileged EXEC command. To disable debugging, 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 History

Release 11.3(6)T 12.0(1)T 12.0(5)T 12.1(2)T

Modification This command was introduced for limited availability. This command was available for general release. This command was added to the documentation. The output for this command was modified to reflect MIB and SNMP changes.

Examples

The following output is from the de